draft-ietf-mpls-extended-admin-group-03.txt   draft-ietf-mpls-extended-admin-group-04.txt 
Network Working Group E. Osborne Network Working Group E. Osborne
Internet-Draft Internet-Draft
Intended status: Standards Track March 6, 2014 Intended status: Standards Track March 20, 2014
Expires: September 7, 2014 Expires: September 21, 2014
Extended Administrative Groups in MPLS-TE Extended Administrative Groups in MPLS-TE
draft-ietf-mpls-extended-admin-group-03 draft-ietf-mpls-extended-admin-group-04
Abstract Abstract
MPLS-TE advertises 32 administrative groups (commonly referred to as MPLS-TE advertises 32 administrative groups (commonly referred to as
"colors" or "link colors") using the Administrative Group sub-TLV of "colors" or "link colors") using the Administrative Group sub-TLV of
the Link TLV. This is defined for OSPFv2 [RFC3630], OSPFv3 [RFC5329] the Link TLV. This is defined for OSPFv2 (RFC3630), OSPFv3 (RFC5329)
and ISIS [RFC5305]. and ISIS (RFC5305).
This document adds a sub-TLV to the IGP TE extensions, "Extended This document adds a sub-TLV to the IGP TE extensions, "Extended
Administrative Group". This sub-TLV provides for additional Administrative Group". This sub-TLV provides for additional
administrative groups (link colors) beyond the current limit of 32. administrative groups (link colors) beyond the current limit of 32.
Requirements Language Requirements Language
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 RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on September 7, 2014. This Internet-Draft will expire on September 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
2. Extended Administrative Groups sub-TLV . . . . . . . . . . . 3 2. Extended Administrative Groups sub-TLV . . . . . . . . . . . 3
2.1. Packet Format . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Packet Format . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Admin group numbering . . . . . . . . . . . . . . . . . . 4 2.2. Admin group numbering . . . . . . . . . . . . . . . . . . 4
2.3. Backward compatability . . . . . . . . . . . . . . . . . 4 2.3. Backward compatability . . . . . . . . . . . . . . . . . 4
2.3.1. AG and EAG coexistence . . . . . . . . . . . . . . . 4 2.3.1. AG and EAG coexistence . . . . . . . . . . . . . . . 4
2.3.2. Desire for unadvertised EAG bits . . . . . . . . . . 5 2.3.2. Desire for unadvertised EAG bits . . . . . . . . . . 5
3. Signaling Extended Administrative Groups in RSVP . . . . . . 5 3. Signaling Extended Administrative Groups in RSVP . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. Normative References . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Do we need more than 32 bits? Do we need more than 32 bits?
The IGP extensions to support MPLS-TE (RFCs 3630 [RFC3630] and 5305 The IGP extensions to support MPLS-TE (RFCs 3630 [RFC3630] and 5305
[RFC5305]) define a link TLV known as Administrative Group (AG) with [RFC5305]) define a link TLV known as Administrative Group (AG) with
a limit of 32 AGs per link. The concept of Administrative Groups a limit of 32 AGs per link. The concept of Administrative Groups
comes from section 6.2 of RFC 2702 [RFC2702], which calls them comes from section 6.2 of RFC 2702 [RFC2702], which calls them
skipping to change at page 6, line 16 skipping to change at page 6, line 16
marked 'y' for Sub-TLVs 22, 141 and 222; this is identical to the marked 'y' for Sub-TLVs 22, 141 and 222; this is identical to the
allocation for the Administrative Group sub-TLV (value 3). In both allocation for the Administrative Group sub-TLV (value 3). In both
registries the first free value should be assigned. As of this registries the first free value should be assigned. As of this
writing, that's 26 in the OSPF registry and 14 in the IS-IS registry. writing, that's 26 in the OSPF registry and 14 in the IS-IS registry.
6. Acknowledgements 6. Acknowledgements
Thanks to Santiago Alvarez, Rohit Gupta, Liem Nguyen, Tarek Saad, and Thanks to Santiago Alvarez, Rohit Gupta, Liem Nguyen, Tarek Saad, and
Robert Sawaya for their review and comments. Robert Sawaya for their review and comments.
7. Normative References 7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
McManus, "Requirements for Traffic Engineering Over MPLS",
RFC 2702, September 1999.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
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, September (TE) Extensions to OSPF Version 2", RFC 3630, September
2003. 2003.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, October 2008. Engineering", RFC 5305, October 2008.
[RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, 7.2. Informative References
"Traffic Engineering Extensions to OSPF Version 3", RFC
5329, September 2008. [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J.
McManus, "Requirements for Traffic Engineering Over MPLS",
RFC 2702, September 1999.
Author's Address Author's Address
Eric Osborne Eric Osborne
Email: eric.osborne@notcom.com Email: eric.osborne@notcom.com
 End of changes. 8 change blocks. 
15 lines changed or deleted 17 lines changed or added

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