draft-ietf-ccamp-automesh-01.txt   draft-ietf-ccamp-automesh-02.txt 
Networking Working Group JP. Vasseur (Editor) Networking Working Group JP. Vasseur, Ed.
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Expires: August 9, 2006 JL. Leroux (Editor) Intended status: Standards Track JL. Leroux, Ed.
France Telecom Expires: March 4, 2007 France Telecom
S. Yasukawa S. Yasukawa
NTT NTT
S. Previdi S. Previdi
P. Psenak P. Psenak
Cisco Systems, Inc Cisco Systems, Inc
P. Mabbey P. Mabbey
Comcast Comcast
February 5, 2006 August 31, 2006
Routing extensions for discovery of Multiprotocol (MPLS) Label Switch Routing extensions for discovery of Multiprotocol (MPLS) Label Switch
Router (LSR) Traffic Engineering (TE) mesh membership Router (LSR) Traffic Engineering (TE) mesh membership
draft-ietf-ccamp-automesh-02.txt
draft-ietf-ccamp-automesh-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 44 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 9, 2006. This Internet-Draft will expire on March 4, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
The set up of a full mesh of Multi-Protocol Label Switching (MPLS) The set up of a full mesh of Multi-Protocol Label Switching (MPLS)
Traffic Engineering (TE) Label Switched Path (LSP) among a set of Traffic Engineering (TE) Label Switched Paths (LSP) among a set of
Label Switch Routers (LSR) is common deployment scenario of MPLS Label Switch Routers (LSR) is common deployment scenario of MPLS
Traffic Engineering either for bandwidth optimization, bandwidth Traffic Engineering either for bandwidth optimization, bandwidth
guarantees or fast rerouting with MPLS Fast Reroute. Such deployment guarantees or fast rerouting with MPLS Fast Reroute. Such deployment
may require the configuration of potentially a large number of TE may require the configuration of potentially a large number of TE
LSPs (on the order of the square of the number LSRs). This document LSPs (on the order of the square of the number LSRs). This document
specifies IGP routing extensions for ISIS and OSPF so as to provide specifies IGP routing extensions for ISIS and OSPF so as to provide
an automatic discovery of the set of LSRs members of a mesh in order an automatic discovery of the set of LSRs members of a mesh in order
to automate the creation of such mesh. to automate the creation of such mesh.
Requirements Language Requirements Language
skipping to change at page 3, line 14 skipping to change at page 3, line 14
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. TE Mesh-Group . . . . . . . . . . . . . . . . . . . . . . . . 5 3. TE Mesh-Group . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Description . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Description . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Required Information . . . . . . . . . . . . . . . . . . . 5 3.2. Required Information . . . . . . . . . . . . . . . . . . . 5
4. TE-MESH-GROUP TLV formats . . . . . . . . . . . . . . . . . . 5 4. TE-MESH-GROUP TLV formats . . . . . . . . . . . . . . . . . . 5
4.1. OSPF TE-MESH-GROUP TLV format . . . . . . . . . . . . . . 5 4.1. OSPF TE-MESH-GROUP TLV format . . . . . . . . . . . . . . 5
4.2. IS-IS TE-MESH-GROUP TLV format . . . . . . . . . . . . . . 8 4.2. IS-IS TE-MESH-GROUP sub-TLV format . . . . . . . . . . . . 8
5. Elements of procedure . . . . . . . . . . . . . . . . . . . . 10 5. Elements of procedure . . . . . . . . . . . . . . . . . . . . 10
5.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. ISIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.2. ISIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Backward compatibility . . . . . . . . . . . . . . . . . . . . 12 6. Backward compatibility . . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. Normative References . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Terminology 1. Terminology
Terminology used in this document Terminology used in this document
LSR: Label Switch Router. LSR: Label Switch Router.
TE LSP: Traffic Engineering Label Switched Path. TE LSP: Traffic Engineering Label Switched Path.
TE LSP head-end: head/source of the TE LSP. TE LSP head-end: head/source of the TE LSP.
skipping to change at page 5, line 10 skipping to change at page 5, line 10
of TE LSPs is implementation specific and outside the scope of this of TE LSPs is implementation specific and outside the scope of this
document. document.
Routing extensions have been defined in [I-D.ietf-ospf-cap] and Routing extensions have been defined in [I-D.ietf-ospf-cap] and
[I-D.ietf-isis-caps] in order to advertise router capabilities. This [I-D.ietf-isis-caps] in order to advertise router capabilities. This
document specifies IGP (OSPF and IS-IS) TE Mesh Group TLVs allowing document specifies IGP (OSPF and IS-IS) TE Mesh Group TLVs allowing
for the automatic discovery of a TE LSP mesh members, to be carried for the automatic discovery of a TE LSP mesh members, to be carried
in the OSPF Router Information LSA [I-D.ietf-ospf-cap] and ISIS in the OSPF Router Information LSA [I-D.ietf-ospf-cap] and ISIS
Router Capability TLV [I-D.ietf-isis-caps]. The routing extensions Router Capability TLV [I-D.ietf-isis-caps]. The routing extensions
specified in this document provide the ability to signal multiple TE specified in this document provide the ability to signal multiple TE
mesh groups. An LSR may belong to one or more TE mesh-group(s). mesh groups. An LSR may belong to more than one TE mesh-group.
3. TE Mesh-Group 3. TE Mesh-Group
3.1. Description 3.1. Description
A TE mesh-group is defined as a group of LSRs that are connected by a A TE mesh-group is defined as a group of LSRs that are connected by a
full mesh of TE LSPs. Routing extensions are specified in this full mesh of TE LSPs. Routing extensions are specified in this
document allowing for dynamic discovery of the TE mesh-group members. document allowing for dynamic discovery of the TE mesh-group members.
Procedures are also specified for a member to join and leave a TE Procedures are also specified for a member to join and leave a TE
mesh-group. mesh-group.
skipping to change at page 5, line 32 skipping to change at page 5, line 32
3.2. Required Information 3.2. Required Information
This document specifies a TE-MESH-GROUP TLV that indicates the set of This document specifies a TE-MESH-GROUP TLV that indicates the set of
TE mesh-group(s) an LSR belongs to. For each TE mesh-group TE mesh-group(s) an LSR belongs to. For each TE mesh-group
membership announced by an LSR, the TE-MESH-GROUP TLV advertises the membership announced by an LSR, the TE-MESH-GROUP TLV advertises the
following information: following information:
- A mesh-group number identifying the TE mesh-group the LSR belongs - A mesh-group number identifying the TE mesh-group the LSR belongs
to. to.
- A Tail-end address (used as TE LSP tail-end address by other LSRs - A Tail-end address (used as the TE LSP tail-end address by other
belonging to the same mesh-group). LSRs belonging to the same mesh-group).
- A Tail-end name: string used to ease the TE-LSP naming. - A Tail-end name: string used to ease the TE-LSP naming.
4. TE-MESH-GROUP TLV formats 4. TE-MESH-GROUP TLV formats
4.1. OSPF TE-MESH-GROUP TLV format 4.1. OSPF TE-MESH-GROUP TLV format
the OSPF TE-MESH-GROUP TLV (advertised in an OSPF router information the OSPF TE-MESH-GROUP TLV (advertised in an OSPF router information
LSA defined in [I-D.ietf-ospf-cap]) has the following format: LSA defined in [I-D.ietf-ospf-cap]) has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
skipping to change at page 6, line 29 skipping to change at page 6, line 29
Length: length of the value field in octets Length: length of the value field in octets
The format of the OSPF TE-MESH-GROUP TLV is the same as the TLV The format of the OSPF TE-MESH-GROUP TLV is the same as the TLV
format used by the Traffic Engineering Extensions to OSPF format used by the Traffic Engineering Extensions to OSPF
(see[RFC3630]). The TLV is padded to four-octet alignment; padding (see[RFC3630]). The TLV is padded to four-octet alignment; padding
is not included in the length field (so a three octet value would is not included in the length field (so a three octet value would
have a length of three, but the total size of the TLV would be eight have a length of three, but the total size of the TLV would be eight
octets). Nested TLVs are also 32-bit aligned. Unrecognized types octets). Nested TLVs are also 32-bit aligned. Unrecognized types
are ignored. All types between 32768 and 65535 are reserved for are ignored. All types between 32768 and 65535 are reserved for
vendor-specific extensions. All other undefined type codes are vendor-specific extensions. All other undefined type codes are
reserved for future assignment by IANA. The TE-MESH-GROUP TLV is reserved for future assignment by IANA.
used to advertise the desire of an LSR to join/leave a given TE mesh-
group. No sub-TLV is currently defined for the TE-mesh-group TLV. The TE-MESH-GROUP TLV is used to advertise the desire of an LSR to
join/leave a given TE mesh-group. No sub-TLV is currently defined
for the TE-mesh-group TLV.
The TE-MESH-GROUP TLV has the following format: The TE-MESH-GROUP TLV has the following format:
TYPE: To be assigned by IANA (Suggested Value: 3) TYPE: To be assigned by IANA (Suggested Value: 3)
LENGTH: Variable LENGTH: Variable
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| mesh-group-number | | mesh-group-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail-end IPv4 address | | Tail-end IPv4 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Name length | Tail-end name (NULL padded display string) | | Name length | Tail-end name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2 - TE-MESH-GROUP TLV format (IPv4 Address) Figure 2 - OSPF TE-MESH-GROUP TLV format (IPv4 Address)
TYPE: To be assigned by IANA (Suggested Value: 4) TYPE: To be assigned by IANA (Suggested Value: 4)
LENGTH: Variable LENGTH: Variable
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| mesh-group-number | | mesh-group-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Tail-end IPv6 address | | Tail-end IPv6 address |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Name length | Tail-end name (NULL padded display string) | | Name length | Tail-end name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3 - TE-MESH-GROUP TLV format (IPv6 Address) Figure 3 - OSPF TE-MESH-GROUP TLV format (IPv6 Address)
For each TE mesh-group announced by the LSR, the TE-MESH-GROUP TLV For each TE mesh-group announced by the LSR, the TE-MESH-GROUP TLV
comprises: comprises:
- A mesh-group-number that identifies the mesh-group number - A mesh-group-number that identifies the mesh-group number
- A Tail-end address: an IPv4 or IPv6 IP address to be used as a - A Tail-end address: an IPv4 or IPv6 IP address to be used as a
tail-end TE LSP address by other LSRs belonging to the same mesh- tail-end TE LSP address by other LSRs belonging to the same mesh-
group group
- A Tail-end name: a variable length field used to facilitate the TE - A Tail-end name: a variable length field used to facilitate the TE
LSP identification. The Name length field indicates the length of LSP identification. The Name length field indicates the length of
the display string before padding, in bytes. the display string before padding, in bytes.
4.2. IS-IS TE-MESH-GROUP TLV format 4.2. IS-IS TE-MESH-GROUP sub-TLV format
The IS-IS TE-MESH-GROUP TLV (advertised in the IS-IS CAPABILITY TLV The IS-IS TE-MESH-GROUP sub-TLV (advertised in the IS-IS CAPABILITY
defined in [I-D.ietf-isis-caps] ) is composed of 1 octet for the TLV defined in [I-D.ietf-isis-caps] ) is composed of 1 octet for the
type, 1 octet specifying the TLV length and a value field. The type, 1 octet specifying the TLV length and a value field. The
format of the TE-MESH-GROUP TLV is identical to the TLV format used format of the TE-MESH-GROUP sub-TLV is identical to the TLV format
by the Traffic Engineering Extensions for IS-IS [RFC3784]. The TE- used by the Traffic Engineering Extensions for IS-IS [RFC3784]. The
MESH-GROUP TLV is used to advertise the desire of an LSR to join/ TE-MESH-GROUP sub-TLV is used to advertise the desire of an LSR to
leave a given TE mesh-group. No sub-TLV is currently defined for the join/leave a given TE mesh-group. No sub-TLV is currently defined
TE-MESH-GROUP TLV. for the TE-MESH-GROUP sub-TLV.
The TE-MESH-GROUP TLV has the following format: The ISIS TE-MESH-GROUP sub-TLV has the following format:
TYPE: To be assigned by IANA (Suggested value: 3). TYPE: To be assigned by IANA (Suggested value: 3).
LENGTH: Variable LENGTH: Variable
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| mesh-group-number | | mesh-group-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tail-end IPv4 address | | Tail-end IPv4 address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Name length | Tail-end name (NULL padded display string) | | Name length | Tail-end name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4 - TE-MESH-GROUP TLV format (IPv4 Address) Figure 4 - ISIS TE-MESH-GROUP sub-TLV format (IPv4 Address)
TYPE: To be assigned by IANA (Suggested Value: 4) TYPE: To be assigned by IANA (Suggested Value: 4)
LENGTH: Variable LENGTH: Variable
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| mesh-group-number | | mesh-group-number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
| Tail-end IPv6 address | | Tail-end IPv6 address |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Name length | Tail-end name (NULL padded display string) | | Name length | Tail-end name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// // // //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5 - TE-MESH-GROUP TLV format (IPv6 Address) Figure 5 - ISIS TE-MESH-GROUP sub-TLV format (IPv6 Address)
For each TE mesh-group announced by the LSR, the TE-MESH-GROUP TLV The OSPF TE-MESH-GROUP TLV and the ISIS TE-MESH-GROUP sub-TLV may
comprises: contain one or more mesh-group entries where each entry correspond to
a TE mesh-group and is made of the following fields:
- A mesh-group-number that identifies the mesh-group number - A mesh-group-number that identifies the mesh-group number,
- A Tail-end address: an IPv4 or IPv6 IP address to be used as a - A Tail-end address: an IPv4 or IPv6 IP address to be used as a
tail-end TE LSP address by other LSRs belonging to the same mesh- tail-end TE LSP address by other LSRs belonging to the same mesh-
group group,
- A Tail-end name: a variable length field used to facilitate the TE - A Tail-end name: a variable length field used to facilitate the TE
LSP identification. The Name length field indicates the length of LSP identification. The Name length field indicates the length of
the display string before padding, in bytes. the display string before padding, in bytes.
5. Elements of procedure 5. Elements of procedure
The TE-MESH-GROUP TLV is carried within the OSPF Routing Information The OSPF TE-MESH-GROUP TLV is carried within the OSPF Routing
LSA or ISIS Router capability TLV. As such, elements of procedure Information LSA and the TE-MESH-GROUP sub-TLV is caried within the
are inherited from those defined in [I-D.ietf-ospf-cap] and ISIS Router capability TLV. As such, elements of procedure are
inherited from those defined in [I-D.ietf-ospf-cap] and
[I-D.ietf-isis-caps] for OSPF and ISIS respectively. Specifically, a [I-D.ietf-isis-caps] for OSPF and ISIS respectively. Specifically, a
router MUST originate a new LSA/LSP whenever the content of this router MUST originate a new LSA/LSP whenever the content of this
information changes, or whenever required by regular routing information changes, or whenever required by regular routing
procedure (e.g. refresh). The TE-MESH-GROUP TLV is OPTIONAL and must procedure (e.g. refresh). The TE-MESH-GROUP TLV is OPTIONAL and MUST
at most appear once in a OSPF Router Information LSA or ISIS Router at most appear once in a OSPF Router Information LSA or ISIS Router
Capability TLV. Capability TLV. If the OSPF TE-MESH-GROUP TLV occurs more than once
within the OSPF Router Information LSA, only the first instance is
processed, subsequent TLV(s) will be silently ignored. Similarly, If
the ISIS TE-MESH-GROUP sub-TLV occurs more than once within the ISIS
Router capability TLV, only the first instance is processed,
subsequent TLV(s) will be silently ignored.
5.1. OSPF 5.1. OSPF
The TE-MESH-GROUP TLV is advertised within an OSPF Router Information The TE-MESH-GROUP TLV is advertised within an OSPF Router Information
opaque LSA (opaque type of 4, opaque ID of 0) as defined in opaque LSA (opaque type of 4, opaque ID of 0) as defined in
[I-D.ietf-ospf-cap]. [I-D.ietf-ospf-cap].
A router MUST originate a new OSPF router information LSA whenever A router MUST originate a new OSPF router information LSA whenever
the content of the any of the advertised TLV changes or whenever the content of the any of the advertised TLV changes or whenever
required by the regular OSPF procedure (LSA refresh (every required by the regular OSPF procedure (LSA refresh (every
skipping to change at page 11, line 14 skipping to change at page 11, line 19
group profile: group profile:
- If the MPLS TE mesh-group is contained within a single area (all - If the MPLS TE mesh-group is contained within a single area (all
the LSRs of the mesh-group are contained within a single area), the the LSRs of the mesh-group are contained within a single area), the
TE-MESH-GROUP TLV MUST be generated within a Type 10 Router TE-MESH-GROUP TLV MUST be generated within a Type 10 Router
Information LSA; Information LSA;
- If the MPLS TE mesh-group spans multiple OSPF areas, the TE mesh- - If the MPLS TE mesh-group spans multiple OSPF areas, the TE mesh-
group TLV MUST be generated within a Type 11 router information LSA. group TLV MUST be generated within a Type 11 router information LSA.
It is expected that the number of mesh-groups and consequently the It is expected that the number of mesh-groups be very limited (to at
number of TE-MESH-GROUP TLVs advertised within a Routing Information most 10 or so). Moreover, TE mesh-group membership is fairly static
LSA will be very limited (to at most 10 or so). Moreover, TE mesh- and should not change frequently.
group membership is fairly static and should not change frequently.
5.2. ISIS 5.2. ISIS
The TE-MESH-GROUP TLV is advertised within the IS-IS Router The TE-MESH-GROUP sub-TLV is advertised within the IS-IS Router
CAPABILITY TLV defined in [I-D.ietf-isis-caps]. An IS-IS router MUST CAPABILITY TLV defined in [I-D.ietf-isis-caps]. An IS-IS router MUST
originate a new IS-IS LSP whenever the content of the any of the originate a new IS-IS LSP whenever the content of the any of the
advertised sub-TLV changes or whenever required by regular IS-IS advertised sub-TLV changes or whenever required by regular IS-IS
procedure (LSP refresh). If an LSR desires to join or leave a procedure (LSP refresh). If an LSR desires to join or leave a
particular TE mesh group, it MUST originate a new LSP comprising the particular TE mesh group, it MUST originate a new LSP comprising the
refreshed ISIS Router capability TLV comprising the updated TE-MESH- refreshed ISIS Router capability TLV comprising the updated TE-MESH-
GROUP TLV. In the case of a join, a new entry will be added to the GROUP sub-TLV. In the case of a join, a new entry will be added to
TE-MESH-GROUP TLV; conversely, if the LSR leaves a mesh-group the the TE-MESH-GROUP sub-TLV; conversely, if the LSR leaves a mesh-group
corresponding entry will be deleted to the TE-MESH-GROUP TLV. Note the corresponding entry will be deleted from the TE-MESH-GROUP sub-
that both operations can be performed in the context of a single TLV. Note that both operations can be performed in the context of a
refresh. An implementation SHOULD be able to detect any change to a single refresh. An implementation SHOULD be able to detect any
previously received TE-MESH-GROUP TLV from a specific LSR. change to a previously received TE-MESH-GROUP sub-TLV from a specific
LSR.
If the flooding scope of an MPLS Traffic Engineering capability is If the flooding scope of an MPLS Traffic Engineering capability is
limited to an IS-IS level/area, the TLV MUST not be leaked across limited to an IS-IS level/area, the sub-TLV MUST not be leaked across
level/area and the S flag of the Router CAPABILITY TLV MUST be level/area and the S flag of the Router CAPABILITY TLV MUST be
cleared. Conversely, if the flooding scope of an MPLS Traffic cleared. Conversely, if the flooding scope of an MPLS Traffic
Engineering capability is the entire routing domain, the TLV MUST be Engineering capability is the entire routing domain, the TLV MUST be
leaked across IS-IS levels/areas, and the S flag of the Router leaked across IS-IS levels/areas, and the S flag of the Router
CAPABILITY TLV MUST be set. In both cases the flooding rules CAPABILITY TLV MUST be set. In both cases the flooding rules
specified in [I-D.ietf-isis-caps] apply. specified in [I-D.ietf-isis-caps] apply.
As specified in [I-D.ietf-isis-caps], a router may generate multiple As specified in [I-D.ietf-isis-caps], a router may generate multiple
IS-IS Router CAPABILITY TLVs within an IS-IS LSP with different IS-IS Router CAPABILITY TLVs within an IS-IS LSP with different
flooding scopes. flooding scopes.
It is expected that the number of mesh groups and consequently the It is expected that the number of TE mesh-groups will be very limited
number of TE-MESH-GROUP TLV advertised within an ISIS Router (to at most 10 or so). Moreover, TE mesh-group membership is fairly
Capability TLV will be very limited (to at most 10 or so). Moreover, static and should not change frequently.
TE mesh-group membership is fairly static and should not change
frequently.
6. Backward compatibility 6. Backward compatibility
The TE-MESH-GROUP TLVs defined in this document do not introduce any The TE-MESH-GROUP TLVs defined in this document do not introduce any
interoperability issue. For OSPF, a router not supporting the TE- interoperability issue. For OSPF, a router not supporting the TE-
MESH-GROUP TLV SHOULD just silently ignore the TLV as specified in MESH-GROUP TLV SHOULD just silently ignore the TLV as specified in
[RFC2370]. For IS-IS a router not supporting the TE-MESH-GROUP TLV [RFC2370]. For IS-IS a router not supporting the TE-MESH-GROUP sub-
SHOULD just silently ignore the TLV. TLV SHOULD just silently ignore the sub-TLV.
7. IANA Considerations 7. IANA Considerations
OSPF OSPF
IANA will assign new OSPF TLV code-point for the newly defined TE- IANA will assign new OSPF TLV code-point for the newly defined TE-
MESH-GROUP TLVs carried within the Router Information LSA. MESH-GROUP TLVs carried within the Router Information LSA.
TE-MESH-GROUP TLV (IPv4) (suggested value=3) TE-MESH-GROUP TLV (IPv4) (suggested value=3)
TE-MESH-GROUP TLV (IPv6) (suggested value=4) TE-MESH-GROUP TLV (IPv6) (suggested value=4)
ISIS ISIS
IANA will assign new ISIS TLV code-point for the newly defined TE- IANA will assign new ISIS TLV code-point for the newly defined TE-
MESH-GROUP TLVs carried within the ISIS Router Capability TLV. MESH-GROUP sub-TLVs carried within the ISIS Router Capability TLV.
TE-MESH-GROUP TLV (IPv4) (suggested value=3) TE-MESH-GROUP TLV (IPv4) (suggested value=3)
TE-MESH-GROUP TLV (IPv6) (suggested value=4) TE-MESH-GROUP TLV (IPv6) (suggested value=4)
8. Security Considerations 8. Security Considerations
No new security issues are raised in this document. No new security issues are raised in this document.
9. Acknowledgements 9. Acknowledgements
We would like to thank Dean Cheng, Adrian Farrel, Yannick Le Louedec We would like to thank Dean Cheng, Adrian Farrel, Yannick Le Louedec,
and Dave Ward for their useful comments. Dave Ward, Les Ginsberg and Stephen Nadas for their useful comments.
10. References
10.1. Normative References 10. Normative References
[I-D.ietf-isis-caps] [I-D.ietf-isis-caps]
Vasseur, J., "IS-IS Extensions for Advertising Router Vasseur, J., "IS-IS Extensions for Advertising Router
Information", draft-ietf-isis-caps-06 (work in progress), Information", draft-ietf-isis-caps-06 (work in progress),
January 2006. January 2006.
[I-D.ietf-ospf-cap] [I-D.ietf-ospf-cap]
Lindem, A., "Extensions to OSPF for Advertising Optional Lindem, A., "Extensions to OSPF for Advertising Optional
Router Capabilities", draft-ietf-ospf-cap-08 (work in Router Capabilities", draft-ietf-ospf-cap-08 (work in
progress), December 2005. progress), December 2005.
skipping to change at page 13, line 35 skipping to change at page 13, line 35
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
September 2003. September 2003.
[RFC3784] Smit, H. and T. Li, "Intermediate System to Intermediate [RFC3784] Smit, H. and T. Li, "Intermediate System to Intermediate
System (IS-IS) Extensions for Traffic Engineering (TE)", System (IS-IS) Extensions for Traffic Engineering (TE)",
RFC 3784, June 2004. RFC 3784, June 2004.
10.2. Informative References
[OSPF-TE] Katz, et al., RFC 3630, "Traffic Engineering (TE)
Extensions to OSPF Version 2", September 2003.
[PCE-DISCO]
J.L Le Roux, JP Vasseur et al,
draft-ietf-pce-disco-proto-igp (work in progress)., "IGP
protocol extensions for Path Computation Element (PCE)
Discovery", May .
Authors' Addresses Authors' Addresses
JP Vasseur (Editor) JP Vasseur (editor)
Cisco Systems, Inc Cisco Systems, Inc
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
Email: jpv@cisco.com Email: jpv@cisco.com
JL Le Roux (editor)
JL Le Roux (Editor)
France Telecom France Telecom
2, Avenue Pierre-Marzin 2, Avenue Pierre-Marzin
Lanion, 22307 Lanion, 22307
FRANCE FRANCE
Email: jeanlouis.leroux@francetelecom.com Email: jeanlouis.leroux@francetelecom.com
Seisho Yasukawa Seisho Yasukawa
NTT NTT
9-11, Midori-Cho 3-Chome 9-11, Midori-Cho 3-Chome
skipping to change at page 15, line 4 skipping to change at page 14, line 35
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
Peter Psenak Peter Psenak
Cisco Systems, Inc Cisco Systems, Inc
Pegasus Park DE Kleetlaan 6A Pegasus Park DE Kleetlaan 6A
Diegmen, 1831 Diegmen, 1831
BELGIUM BELGIUM
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
Paul Mabbey Paul Mabbey
Comcast Comcast
USA USA
Email: Email:
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 16, line 29 skipping to change at page 15, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 46 change blocks. 
102 lines changed or deleted 94 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/