Fwd: [rbridge] I-D Action:draft-ietf-trill-adj-01.txt

---------- Forwarded message ----------
From:  <Internet-Drafts <at> ietf.org>
Date: Sun, Jan 2, 2011 at 10:45 PM
Subject: [rbridge] I-D Action:draft-ietf-trill-adj-01.txt
To: i-d-announce <at> ietf.org
Cc: rbridge <at> postel.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transparent Interconnection of Lots
of Links Working Group of the IETF.

       Title           : RBridges: Adjacency
       Author(s)       : D. Eastlake 3rd, et al.
       Filename        : draft-ietf-trill-adj-01.txt
       Pages           : 26
       Date            : 2011-01-02

The IETF TRILL protocol provides optimal pair-wise data forwarding
without configuration, safe forwarding even during periods of
temporary loops, and support for multipathing of both unicast and
multicast traffic. TRILL accomplishes this by using IS-IS link state
routing and by encapsulating traffic using a header that includes a
hop count. Devices that implement TRILL are called RBridges.

TRILL supports multi-access LAN links that can have multiple end
stations and RBridges attached. This document describes the TRILL LAN
Hello protocol used on such links as regards adjacency, designated
RBridge selection, and MTU procedures, with state machines. There is
no change for IS-IS point-to-point Hellos used on links configured as
point-to-point in TRILL.

Fwd: WG last call on draft-ietf-trill-adj-01.txt

Please send the last call comments to rbridge <at> postel.org.

    Erik

-------- Original Message --------
Subject: WG last call on draft-ietf-trill-adj-01.txt
Date: Mon, 03 Jan 2011 10:53:31 -0800
From: Erik Nordmark <nordmark <at> acm.org>
To: Developing a hybrid router/bridge. <rbridge <at> postel.org>

This starts a two-week WG last call on "RBridges: Adjacency"
<draft-ietf-trill-adj-01.txt>, available at
http://tools.ietf.org/html/draft-ietf-trill-adj-01

The last call ends on 1/17/2011.

Send any comments to the TRILL WG mailing list.

     Erik

Last Call: draft-ietf-isis-ieee-aq (IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging) to Proposed Standard

The IESG has received a request from the IS-IS for IP Internets WG (isis) 
to consider the following document:

- 'IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging '
   <draft-ietf-isis-ieee-aq-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2011-01-18. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isis-ieee-aq-03.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=20343&rfc_flag=0

Please note that this document makes normative reference to ISO/IEC 10589:2002

No IPR declarations have been submitted directly on this I-D.

Last Call: draft-ietf-isis-purge-tlv (Purge Originator Identification TLV for IS-IS) to Proposed Standard

The IESG has received a request from the IS-IS for IP Internets WG (isis) 
to consider the following document:

- 'Purge Originator Identification TLV for IS-IS '
   <draft-ietf-isis-purge-tlv-05.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2011-01-18. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isis-purge-tlv-05.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=20005&rfc_flag=0

Please note that this document makes normative reference to ISO/IEC 10589:2002 and ISO/IEC 10589:1992/ Cor.1:1993

No IPR declarations have been submitted directly on this I-D.

Last Call: draft-ietf-isis-reg-purge (IS-IS Registry Extension for Purges) to Proposed Standard

The IESG has received a request from the IS-IS for IP Internets WG (isis) 
to consider the following document:

- 'IS-IS Registry Extension for Purges '
   <draft-ietf-isis-reg-purge-00.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf <at> ietf.org mailing lists by 2011-01-18. Exceptionally, 
comments may be sent to iesg <at> ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-isis-reg-purge-00.txt

IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=20803&rfc_flag=0

Please note that this document includes a normative reference to ISO/IEC 10589:2002

No IPR declarations have been submitted directly on this I-D.

I-D Action:draft-ietf-isis-bfd-tlv-03.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title           : IS-IS BFD Enabled TLV
	Author(s)       : C. Hopps, L. Ginsberg
	Filename        : draft-ietf-isis-bfd-tlv-03.txt
	Pages           : 8
	Date            : 2011-01-04

This document describes a type-length-value (TLV) for use in the
IS-IS routing protocol that allows for the proper use of the
Bidirectional Forwarding Detection protocol (BFD).  There exist
certain scenarios in which IS-IS will not react appropriately to a
BFD detected forwarding plane failure without use of either this TLV
or some other method.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-bfd-tlv-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Isis-wg mailing list

I-D Action:draft-ietf-isis-trill-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title           : TRILL Use of IS-IS
	Author(s)       : A. Banerjee, et al.
	Filename        : draft-ietf-isis-trill-04.txt
	Pages           : 30
	Date            : 2011-01-04

The IETF has standardized the TRILL protocol, which provides
transparent Layer 2 forwarding using encapsulation with a hop count
and IS-IS link state routing. This document specifies the data
formats and code points for the IS-IS extensions to support TRILL.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-trill-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
Isis-wg mailing list
Isis-wg <at> ietf.org
https://www.ietf.org/mailman/listinfo/isis-wg

IS-IS based VPLS for cloud data center networks

Hi all,

Cloud data centers require large L2 network which should not only be able to
support shortest path forwarding and ECMP for maximizing the bandwidth
capacity between servers, but also be able to provide a huge amount of VPN
instances for isolating hundreds of thousands of tenement within the data
centers. VPLS seems as a good option for this requirement. However, BGP and
LDP based VPLS solutions seem a bit heavy-weight and hence not much
acceptable for some cloud data center providers.

So I wonder whether it is reasonable to develop IS-IS based VPLS for those
special cloud data center providers. For example, IS-IS is run between P and
PE routers, and an extended IS-IS TLV is used by PE routers to distribute
their own VPN membership information (e.g., attached VPN instances and
associated VPN labels) among each other. The VPN label will be carried in
the inner MPLS header of L2VPN data packets (e.g., MAC-in-MPLS-in-IP). Note
that the VPN label here now is just used to identify a particular VPN
instance, but not to identify both a particular VPN instance and a
particular ingress PE router as the PW label does. The egress PE router now
could use the source IP address of the outer IP tunnel header in the
received L2VPN data packet to identify the ingress PE router.

Any comment?

Best wishes,
Xiaohu

Re: Last Call: draft-ietf-isis-ieee-aq (IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging) to Proposed Standard

On Tue, 4 Jan 2011, The IESG wrote:
> - 'IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging '
>   <draft-ietf-isis-ieee-aq-03.txt> as a Proposed Standard
...
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-isis-ieee-aq-03.txt

This is an ops-dir review of draft-ietf-isis-ieee-aq-03.

The document provides an overview of IEEE 802.1aq (shortest path Ethernet
bridging using IS-IS) and specifically defines IS-IS codepoints for use.
802.1aq is orthogonal with TRILL wg solutions but both solve somewhat
similar issues, i.e. Ethernet network scaling and load balancing
optimizations.

Secure use of 802.1aq will probably require manual configuration of IS-IS
authentication in each device or IS-IS filtering in client ports.
The draft does not discuss interoperability with traditional Ethernet, i.e.,
how will this work in an environment where all the equipment does not
support it.

I find the document close to ready to publish after minor text improvements
and e.g. definiting how a newly allocated IANA codepoint TLV subspace is to
be managed by IANA.

Some more detailed comments below.

substantial
-----------

Re: IS-IS based VPLS for cloud data center networks

Hi Xu,

If I understand you right, you are talking about a way to use changes
to IS-IS to do Inter Data Center address exchange.

There is something called Overlay Transport Virtualization (OTV),
which seems to do what you are suggesting. That said I know there were
attempts to send addresses instead of doing L2 learning for VPLS,
quite a while back.

Thanks,
Vishwas

On Fri, Jan 7, 2011 at 1:26 AM, Xu Xiaohu <xuxh <at> huawei.com> wrote:
> Hi all,
>
> Cloud data centers require large L2 network which should not only be able to
> support shortest path forwarding and ECMP for maximizing the bandwidth
> capacity between servers, but also be able to provide a huge amount of VPN
> instances for isolating hundreds of thousands of tenement within the data
> centers. VPLS seems as a good option for this requirement. However, BGP and
> LDP based VPLS solutions seem a bit heavy-weight and hence not much
> acceptable for some cloud data center providers.
>
> So I wonder whether it is reasonable to develop IS-IS based VPLS for those
> special cloud data center providers. For example, IS-IS is run between P and
> PE routers, and an extended IS-IS TLV is used by PE routers to distribute
> their own VPN membership information (e.g., attached VPN instances and
> associated VPN labels) among each other. The VPN label will be carried in
> the inner MPLS header of L2VPN data packets (e.g., MAC-in-MPLS-in-IP). Note