RSVP ASSOCIATION Object Extensions
RFC 6780
Document | Type | RFC - Proposed Standard (October 2012) | |
---|---|---|---|
Authors | Lou Berger , François Le Faucheur , Ashok Narayanan | ||
Last updated | 2015-10-14 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
IESG | Responsible AD | Adrian Farrel | |
Send notices to | (None) |
RFC 6780
"Unknown object C-Type" error. This error will propagate to the ingress node for standard error processing. Operators wishing to use a function supported by a particular association type should ensure that the type is supported on any node that is expected to act on the association. 6. Security Considerations A portion of this document reviews procedures defined in [RFC4872] and [RFC4873] and does not define new procedures. As such, no new security considerations are introduced in this portion of the document. Section 3 defines broader usage of the ASSOCIATION object, but does not fundamentally expand on the association function that was previously defined in [RFC4872] and [RFC4873]. Section 4 increases the number of bits that are carried in an ASSOCIATION object (by 32), and similarly does not expand on the association function that was previously defined. This broader definition does allow for additional information to be conveyed, but this information is not fundamentally different from the information that is already carried Berger, et al. Standards Track [Page 14] RFC 6780 RSVP Extensions October 2012 in RSVP. Therefore, there are no new risks or security considerations introduced by this document. For a general discussion on MPLS- and GMPLS-related security issues, including RSVP's chain of trust security model, see the MPLS/GMPLS security framework [RFC5920]. 7. IANA Considerations IANA has assigned new values for namespaces defined in this document and they are summarized in this section. 7.1. IPv4 and IPv6 Extended ASSOCIATION Objects Per this document, IANA has assigned two new C-Types (which are defined in Section 3.1) for the existing ASSOCIATION object in the "Class Names, Class Numbers, and Class Types" section of the "Resource Reservation Protocol (RSVP) Parameters" registry located at http://www.iana.org/assignments/rsvp-parameters: 199 ASSOCIATION [RFC4872] Class Types or C-Types 3 Type 3 IPv4 Extended Association [RFC6780] 4 Type 4 IPv6 Extended Association [RFC6780] 7.2. Resource Sharing Association Type This document also broadens the potential usage of the Resource Sharing Association Type defined in [RFC4873]. As such, IANA has updated the reference of the Resource Sharing Association Type included in the associated registry. Per this document, IANA has also corrected the duplicate usage of '(R)' in this registry. In particular, the "Association Type" registry found at http://www.iana.org/assignments/gmpls-sig-parameters/ has been updated as follows: OLD: 2 Resource Sharing (R) [RFC4873] NEW: 2 Resource Sharing (S) [RFC4873][RFC6780] There are no other IANA considerations introduced by this document. Berger, et al. Standards Track [Page 15] RFC 6780 RSVP Extensions October 2012 8. Acknowledgments Valuable comments and input were received from Dimitri Papadimitriou, Fei Zhang, and Adrian Farrel. We thank Subha Dhesikan for her contribution to the early work on sharing of resources across RSVP reservations. 9. References 9.1. Normative References [RFC2205] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. [RFC4872] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou, Ed., "RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery", RFC 4872, May 2007. [RFC4873] Berger, L., Bryskin, I., Papadimitriou, D., and A. Farrel, "GMPLS Segment Recovery", RFC 4873, May 2007. [RFC5511] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications", RFC 5511, April 2009. 9.2. Informative References [RFC2207] Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC Data Flows", RFC 2207, September 1997. [RFC3175] Baker, F., Iturralde, C., Le Faucheur, F., and B. Davie, "Aggregation of RSVP for IPv4 and IPv6 Reservations", RFC 3175, September 2001. Berger, et al. Standards Track [Page 16] RFC 6780 RSVP Extensions October 2012 [RFC4860] Le Faucheur, F., Davie, B., Bose, P., Christou, C., and M. Davenport, "Generic Aggregate Resource ReSerVation Protocol (RSVP) Reservations", RFC 4860, May 2007. [RFC5003] Metz, C., Martini, L., Balus, F., and J. Sugimoto, "Attachment Individual Identifier (AII) Types for Aggregation", RFC 5003, September 2007. [RFC5389] Rosenberg, J., Mahy, R., Matthews, P., and D. Wing, "Session Traversal Utilities for NAT (STUN)", RFC 5389, October 2008. [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS Networks", RFC 5920, July 2010. [RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile (MPLS-TP) Identifiers", RFC 6370, September 2011. [RFC6689] Berger, L., "Usage of the RSVP ASSOCIATION Object", RFC 6689, July 2012. Authors' Addresses Lou Berger LabN Consulting, L.L.C. Phone: +1-301-468-9228 EMail: lberger@labn.net Francois Le Faucheur Cisco Systems Greenside, 400 Avenue de Roumanille Sophia Antipolis 06410 France EMail: flefauch@cisco.com Ashok Narayanan Cisco Systems 300 Beaver Brook Road Boxborough, MA 01719 United States EMail: ashokn@cisco.com Berger, et al. Standards Track [Page 17]