draft-ietf-mpls-rsvp-upstream-04.txt   draft-ietf-mpls-rsvp-upstream-05.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: January 2010 Expiration Date: September 2010
J. L. Le Roux J. L. Le Roux
France Telecom France Telecom
July 12, 2009 March 08, 2010
MPLS Upstream Label Assignment for RSVP-TE MPLS Upstream Label Assignment for RSVP-TE
draft-ietf-mpls-rsvp-upstream-04.txt draft-ietf-mpls-rsvp-upstream-05.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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.
Copyright and License Notice Copyright and License Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
skipping to change at page 2, line 31 skipping to change at page 2, line 35
Table of Contents Table of Contents
1 Specification of requirements ......................... 3 1 Specification of requirements ......................... 3
2 Introduction .......................................... 3 2 Introduction .......................................... 3
3 RSVP-TE Upstream Label Assignment Capability .......... 3 3 RSVP-TE Upstream Label Assignment Capability .......... 3
4 Distributing Upstream-Assigned Labels in RSVP-TE ...... 4 4 Distributing Upstream-Assigned Labels in RSVP-TE ...... 4
4.1 Procedures ............................................ 5 4.1 Procedures ............................................ 5
5 RSVP-TE Tunnel Identifier Exchange .................... 5 5 RSVP-TE Tunnel Identifier Exchange .................... 5
6 RSVP-TE Point-to-Multipoint LSPs on a LAN ............. 7 6 RSVP-TE Point-to-Multipoint LSPs on a LAN ............. 7
7 IANA Considerations ................................... 8 7 IANA Considerations ................................... 8
8 Acknowledgements ...................................... 8 8 Security Considerations ............................... 8
9 References ............................................ 9 9 Acknowledgements ...................................... 9
9.1 Normative References .................................. 9 10 References ............................................ 9
9.2 Informative References ................................ 9 10.1 Normative References .................................. 9
10 Author's Address ...................................... 10 10.2 Informative References ................................ 9
11 Author's Address ...................................... 10
1. Specification of requirements 1. Specification of requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
This document describes procedures for distributing upstream-assigned This document describes procedures for distributing upstream-assigned
labels [RFC5331] for Resource Reservation Protocol with Traffic labels [RFC5331] for Resource Reservation Protocol with Traffic
skipping to change at page 8, line 33 skipping to change at page 8, line 33
This document defines four new TLVs in the IF_ID RSVP_HOP object This document defines four new TLVs in the IF_ID RSVP_HOP object
[RFC3471]: [RFC3471]:
- RSVP-TE P2MP LSP TLV - RSVP-TE P2MP LSP TLV
- LDP P2MP LSP TLV - LDP P2MP LSP TLV
- IP Multicast Tunnel TLV - IP Multicast Tunnel TLV
- MPLS Context Label TLV - MPLS Context Label TLV
IANA is requested to assign the type values of these TLVs. IANA is requested to assign the type values of these TLVs.
8. Acknowledgements 8. Security Considerations
The security considerations discussed in RFC 5331 and RFC 5332 apply
to this document.
More detailed discussion of security issues that are relevant in the
context of MPLS and GMPLS, including security threats, related
defensive techniques, and the mechanisms for detection and reporting,
are discussed in "Security Framework for MPLS and GMPLS Networks
[MPLS-SEC].
9. Acknowledgements
Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and
Thomas Morin for their comments. Thomas Morin for their comments.
9. References 10. References
9.1. Normative References 10.1. Normative References
[RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon, [RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon,
RFC 3031. RFC 3031.
[RFC5331] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream Label [RFC5331] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream Label
Assignment and Context Specific Label Space", draft-ietf-mpls- Assignment and Context Specific Label Space", draft-ietf-mpls-
upstream-label-05.txt upstream-label-05.txt
[RFC5332] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, draft-ietf- [RFC5332] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, draft-ietf-
mpls-codepoint-08.txt mpls-codepoint-08.txt
skipping to change at page 9, line 36 skipping to change at page 9, line 41
Switching (GMPLS) Signaling - Resource ReserVation Protocol-Traffic Switching (GMPLS) Signaling - Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC 3471 January Switching (GMPLS) Signaling Functional Description", RFC 3471 January
2003. 2003.
[RFC5063] A. Satyanarayana et. al., "Extensions to GMPLS Resource [RFC5063] A. Satyanarayana et. al., "Extensions to GMPLS Resource
Reservation Protocol (RSVP) Graceful Restart", RFC5063 Reservation Protocol (RSVP) Graceful Restart", RFC5063
9.2. Informative References 10.2. Informative References
[MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs", [MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs",
draft-ietf-l3vpn-2547bis-mcast-06.txt draft-ietf-l3vpn-2547bis-mcast-06.txt
[RFC4875] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], [RFC4875] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors],
"Extensions to RSVP-TE for Point to Multipoint TE LSPs", RFC 4875 "Extensions to RSVP-TE for Point to Multipoint TE LSPs", RFC 4875
10. Author's Address [MPLS-SEC] L. fang, ed, "Security Framework for MPLS and GMPLS
Networks", draft-ietf-mpls-mpls-and-gmpls-security-framework-07.txt
11. Author's Address
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
1194 North Mathilda Ave. 1194 North Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Phone: +1-408-936-2720 Phone: +1-408-936-2720
Email: rahul@juniper.net Email: rahul@juniper.net
Jean-Louis Le Roux Jean-Louis Le Roux
France Telecom France Telecom
 End of changes. 12 change blocks. 
19 lines changed or deleted 38 lines changed or added

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