draft-ietf-ccamp-automesh-03.txt   draft-ietf-ccamp-automesh-04.txt 
Networking Working Group JP. Vasseur, Ed. Networking Working Group JP. Vasseur, Ed.
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Intended status: Standards Track JL. Leroux, Ed. Intended status: Standards Track JL. Leroux, Ed.
Expires: June 11, 2007 France Telecom Expires: July 27, 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
December 8, 2006 January 23, 2007
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-03.txt draft-ietf-ccamp-automesh-04.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 43 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 June 11, 2007. This Internet-Draft will expire on July 27, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2006). Copyright (C) The IETF Trust (2007).
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 Paths (LSP) among a set of Traffic Engineering (TE) Label Switched Paths (LSP) among a set of
Label Switch Routers (LSR) is a common deployment scenario of MPLS Label Switch Routers (LSR) is a 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
skipping to change at page 3, line 22 skipping to change at page 3, line 22
4.2. IS-IS TE-MESH-GROUP sub-TLV format . . . . . . . . . . . . 8 4.2. IS-IS TE-MESH-GROUP sub-TLV format . . . . . . . . . . . . 8
5. Elements of procedure . . . . . . . . . . . . . . . . . . . . 9 5. Elements of procedure . . . . . . . . . . . . . . . . . . . . 9
5.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.2. IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.2. IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6. Backward compatibility . . . . . . . . . . . . . . . . . . . . 12 6. Backward compatibility . . . . . . . . . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.1. OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.2. IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
10. Normative References . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . . . 16
1. Terminology 1. Terminology
Terminology used in this document Terminology used in this document
IGP: Interior Gateway Protocol. IGP: Interior Gateway Protocol.
IGP Area: OSPF area or IS-IS level. IGP Area: OSPF area or IS-IS level.
skipping to change at page 13, line 30 skipping to change at page 13, line 30
LSR X destined to LSR Y to be set up, the same TE Mesh group LSR X destined to LSR Y to be set up, the same TE Mesh group
membership must be configured on both LSRs. Thus such fake membership must be configured on both LSRs. Thus such fake
advertisement could not amplify any DoS attack. advertisement could not amplify any DoS attack.
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,
Dave Ward, Les Ginsberg, Stephen Nadas, Acee Lindem, Dimitri Dave Ward, Les Ginsberg, Stephen Nadas, Acee Lindem, Dimitri
Papadimitriou and Lakshminath Dondeti for their useful comments. Papadimitriou and Lakshminath Dondeti for their useful comments.
10. Normative References 10. References
10.1. 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-09 (work in Router Capabilities", draft-ietf-ospf-cap-09 (work in
progress), October 2006. progress), October 2006.
skipping to change at page 14, line 13 skipping to change at page 14, line 16
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, April 1998.
[RFC2370] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370, [RFC2370] Coltun, R., "The OSPF Opaque LSA Option", RFC 2370,
July 1998. July 1998.
[RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
RFC 2740, December 1999. RFC 2740, December 1999.
10.2. Informative References
[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.
Authors' Addresses Authors' Addresses
skipping to change at page 16, line 7 skipping to change at page 16, line 7
Email: ppsenak@cisco.com Email: ppsenak@cisco.com
Paul Mabbey Paul Mabbey
Comcast Comcast
USA USA
Email: Email:
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 9 change blocks. 
8 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/