draft-ietf-mpls-upstream-label-03.txt   draft-ietf-mpls-upstream-label-04.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Y. Rekhter Category: Standards Track
Expiration Date: August 2008 Y. Rekhter
Juniper Networks Juniper Networks
E. Rosen E. Rosen
Cisco Systems, Inc. Cisco Systems, Inc.
November 2007 February 22, 2008
MPLS Upstream Label Assignment and Context-Specific Label Space MPLS Upstream Label Assignment and Context-Specific Label Space
draft-ietf-mpls-upstream-label-03.txt draft-ietf-mpls-upstream-label-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 2, line 23 skipping to change at page 2, line 23
6 Distributing Upstream-Assigned Labels ................. 6 6 Distributing Upstream-Assigned Labels ................. 6
7 Upstream Neighbor Label Space ......................... 6 7 Upstream Neighbor Label Space ......................... 6
8 Context Label on LANs ................................. 9 8 Context Label on LANs ................................. 9
9 Usage of Upstream-Assigned Labels ..................... 10 9 Usage of Upstream-Assigned Labels ..................... 10
10 IANA Considerations ................................... 10 10 IANA Considerations ................................... 10
11 Security Considerations ............................... 10 11 Security Considerations ............................... 10
12 Acknowledgements ...................................... 11 12 Acknowledgements ...................................... 11
13 References ............................................ 11 13 References ............................................ 11
13.1 Normative References .................................. 11 13.1 Normative References .................................. 11
13.2 Informative References ................................ 11 13.2 Informative References ................................ 11
14 Author Information .................................... 11 14 Author's Address ...................................... 11
15 Intellectual Property Statement ....................... 12 15 Intellectual Property Statement ....................... 12
16 Copyright Notice ...................................... 12 16 Copyright Notice ...................................... 12
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
skipping to change at page 11, line 19 skipping to change at page 11, line 19
13. References 13. References
13.1. Normative References 13.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.
[RFC2119] "Key words for use in RFCs to Indicate Requirement [RFC2119] "Key words for use in RFCs to Indicate Requirement
[MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, [MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter,
draft-ietf-mpls-multicast-encaps-06.txt draft-ietf-mpls-multicast-encaps-07.txt
13.2. Informative References 13.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-05.txt draft-ietf-l3vpn-2547bis-mcast-06.txt
[RFC3353] D. Ooms, et. al., "Overview of IP Multicast in a Multi- [RFC3353] D. Ooms, et. al., "Overview of IP Multicast in a Multi-
Protocol Label Switching (MPLS) Environment.", August 2002. Protocol Label Switching (MPLS) Environment.", August 2002.
[RFC3032] E. Rosen, et. al., "MPLS Label Stack Encoding", January [RFC3032] E. Rosen, et. al., "MPLS Label Stack Encoding", January
2001. 2001.
14. Author Information 14. 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
Email: rahul@juniper.net Email: rahul@juniper.net
Yakov Rekhter Yakov Rekhter
Juniper Networks Juniper Networks
1194 North Mathilda Ave. 1194 North Mathilda Ave.
skipping to change at page 12, line 35 skipping to change at page 12, line 35
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 ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
16. Copyright Notice 16. Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
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. 8 change blocks. 
8 lines changed or deleted 9 lines changed or added

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