draft-ietf-ccamp-lsp-attribute-ro-03.txt   draft-ietf-ccamp-lsp-attribute-ro-04.txt 
CCAMP C. Margaria, Ed. CCAMP C. Margaria, Ed.
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Standards Track G. Martinelli Intended status: Standards Track G. Martinelli
Expires: August 17, 2014 Cisco Expires: January 4, 2015 Cisco
S. Balls S. Balls
B. Wright B. Wright
Metaswitch Metaswitch
February 13, 2014 July 03, 2014
LSP Attribute in ERO LSP Attribute in ERO
draft-ietf-ccamp-lsp-attribute-ro-03 draft-ietf-ccamp-lsp-attribute-ro-04
Abstract Abstract
RFC5420 extends RSVP-TE to specify or record generic attributes which RFC5420 extends RSVP-TE to specify or record generic attributes which
apply to the whole of the path of an LSP. This document proposes an apply to the whole of the path of an LSP. This document proposes an
extension to the RSVP ERO and RRO objects to allow it to specify or extension to the RSVP ERO and RRO objects to allow it to specify or
record generic attributes which apply to a given hop. record generic attributes which apply to a given hop.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 August 17, 2014. This Internet-Draft will expire on January 4, 2015.
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 18 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Contributing Authors . . . . . . . . . . . . . . . . . . 3 1.1. Contributing Authors . . . . . . . . . . . . . . . . . . 3
1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Specifying Hop Attribute . . . . . . . . . . . . . . . . . . 3 3. Specifying Hop Attribute . . . . . . . . . . . . . . . . . . 3
3.1. ERO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . . 3 3.1. ERO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . . 3
3.2. HOP Attributes TLVs . . . . . . . . . . . . . . . . . . . 4 3.2. HOP Attributes TLVs . . . . . . . . . . . . . . . . . . . 4
3.3. Procedures . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Procedures . . . . . . . . . . . . . . . . . . . . . . . 5
4. Recording Hop attribute . . . . . . . . . . . . . . . . . . . 5 4. Recording Hop attribute . . . . . . . . . . . . . . . . . . . 6
4.1. RRO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . . 5 4.1. RRO_HOP_ATTRIBUTE subobject . . . . . . . . . . . . . . . 6
4.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.1. Subobject presence rule . . . . . . . . . . . . . . . 6 4.2.1. Subobject presence rule . . . . . . . . . . . . . . . 7
4.2.2. Reporting Compliance with ERO Hop Attributes . . . . 6 4.2.2. Reporting Compliance with ERO Hop Attributes . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5.1. ERO LSP Attribute Subobject . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. RRO LSP Attribute Subobject . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.3. Existing LSP Attribute TLVs . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 5.3.1. Attribute Flags . . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 5.3.2. Service ID TLV . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched
Paths (LSPs) can be route-constrained by making use of the Explicit Paths (LSPs) can be route-constrained by making use of the Explicit
Route (ERO) object and related sub-objects as defined in [RFC3209], Route (ERO) object and related sub-objects as defined in [RFC3209],
[RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520] and [RFC5553]. [RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520] and [RFC5553].
Several documents have identified the need for attributes that can be Several documents have identified the need for attributes that can be
targeted at specific hops in the path of an LSP, including [RFC6163], targeted at specific hops in the path of an LSP, including [RFC6163],
[I-D.ietf-ccamp-wson-signaling], [I-D.ietf-ccamp-wson-signaling],
skipping to change at page 7, line 7 skipping to change at page 7, line 28
To report that an ERO Hop attribute has been considered, or to report To report that an ERO Hop attribute has been considered, or to report
an additional attribute, an LSR MAY add a RRO_HOP_ATTRIBUTE subobject an additional attribute, an LSR MAY add a RRO_HOP_ATTRIBUTE subobject
with the HOP Attribute TLV which describes the attribute to be with the HOP Attribute TLV which describes the attribute to be
reported. The requirement to report compliance MUST be specified in reported. The requirement to report compliance MUST be specified in
the document that defines the usage of an Hop attribute. [[CREF2: the document that defines the usage of an Hop attribute. [[CREF2:
This is not the most efficient encoding, a more efficient encoding This is not the most efficient encoding, a more efficient encoding
would use a bit field ala RFC5420 --Ed.]] would use a bit field ala RFC5420 --Ed.]]
5. IANA Considerations 5. IANA Considerations
TBD once a final approach has been chosen. 5.1. ERO LSP Attribute Subobject
IANA is requested to make the following subobject allocations from
the "EXPLICIT_ROUTE Subobject Type" registry.
Sub-object type TBA
Name ERO HOP Attribute
Reference This document
5.2. RRO LSP Attribute Subobject
IANA is requested to make the following subobject allocations from
the "RECORD_ROUTE Subobject Type" registry.
Sub-object type TBA
Name RRO HOP Attribute
Reference This document
5.3. Existing LSP Attribute TLVs
IANA is request to add the following information for each TLV in the
RSVP TLV type identifier registry.
o Whether allowed on LSP attribute ERO subobject
The existing registry is modified for existing TLVs.
5.3.1. Attribute Flags
The new TLV type definition is as follow
o TLV Type = 1
o TLV Name = Attribute Flags TLV
o Allowed on LSP_ATTRIBUTES object
o Allowed on LSP_REQUIRED_ATTRIBUTES object
o Allowed on LSP attribute ERO subobject
5.3.2. Service ID TLV
The new TLV type definition is as follow
o TLV Type = 2
o TLV Name = Attribute Flags TLV
o Allowed on LSP_ATTRIBUTES object
o Not allowed on LSP_REQUIRED_ATTRIBUTES object
o ? on LSP attribute ERO subobject
6. Security Considerations 6. Security Considerations
None. None.
7. Acknowledgments 7. Acknowledgments
The authors would like to thanks Lou Berger for his directions and The authors would like to thanks Lou Berger for his directions and
Attila Takacs for inspiring this Attila Takacs for inspiring this
[I-D.kern-ccamp-rsvpte-hop-attributes]. The authors also thanks Dirk [I-D.kern-ccamp-rsvpte-hop-attributes]. The authors also thanks Dirk
skipping to change at page 8, line 21 skipping to change at page 9, line 49
Support", RFC 5553, May 2009. Support", RFC 5553, May 2009.
8.2. Informative References 8.2. Informative References
[I-D.ali-ccamp-rc-objective-function-metric-bound] [I-D.ali-ccamp-rc-objective-function-metric-bound]
Ali, Z., Swallow, G., Filsfils, C., Fang, L., Kumaki, K., Ali, Z., Swallow, G., Filsfils, C., Fang, L., Kumaki, K.,
Kunze, R., Ceccarelli, D., and X. Zhang, "Resource Kunze, R., Ceccarelli, D., and X. Zhang, "Resource
ReserVation Protocol-Traffic Engineering (RSVP-TE) ReserVation Protocol-Traffic Engineering (RSVP-TE)
Extension for Signaling Objective Function and Metric Extension for Signaling Objective Function and Metric
Bound", draft-ali-ccamp-rc-objective-function-metric- Bound", draft-ali-ccamp-rc-objective-function-metric-
bound-04 (work in progress), October 2013. bound-05 (work in progress), February 2014.
[I-D.dong-ccamp-rsvp-te-mpls-tp-li-lb] [I-D.dong-ccamp-rsvp-te-mpls-tp-li-lb]
Dong, J., Chen, M., and Z. Li, "GMPLS RSVP-TE Extensions Dong, J., Chen, M., and Z. Li, "GMPLS RSVP-TE Extensions
for Lock Instruct and Loopback", draft-dong-ccamp-rsvp-te- for Lock Instruct and Loopback", draft-dong-ccamp-rsvp-te-
mpls-tp-li-lb-05 (work in progress), December 2012. mpls-tp-li-lb-05 (work in progress), December 2012.
[I-D.ietf-ccamp-wson-signaling] [I-D.ietf-ccamp-wson-signaling]
Bernstein, G., Xu, S., Lee, Y., Martinelli, G., and H. Bernstein, G., Xu, S., Lee, Y., Martinelli, G., and H.
Harai, "Signaling Extensions for Wavelength Switched Harai, "Signaling Extensions for Wavelength Switched
Optical Networks", draft-ietf-ccamp-wson-signaling-06 Optical Networks", draft-ietf-ccamp-wson-signaling-07
(work in progress), July 2013. (work in progress), March 2014.
[I-D.kern-ccamp-rsvpte-hop-attributes] [I-D.kern-ccamp-rsvpte-hop-attributes]
Kern, A. and A. Takacs, "Encoding of Attributes of LSP Kern, A. and A. Takacs, "Encoding of Attributes of LSP
intermediate hops using RSVP-TE", draft-kern-ccamp-rsvpte- intermediate hops using RSVP-TE", draft-kern-ccamp-rsvpte-
hop-attributes-00 (work in progress), October 2009. hop-attributes-00 (work in progress), October 2009.
[RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for [RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for
GMPLS and Path Computation Element (PCE) Control of GMPLS and Path Computation Element (PCE) Control of
Wavelength Switched Optical Networks (WSONs)", RFC 6163, Wavelength Switched Optical Networks (WSONs)", RFC 6163,
April 2011. April 2011.
Authors' Addresses Authors' Addresses
Cyril Margaria (editor) Cyril Margaria (editor)
Juniper Juniper
200 Somerset Corporate Boulevard, , Suite 4001
Bridgewater, NJ 08807
USA
Email: cmargaria@juniper.net Email: cmargaria@juniper.net
Giovanni Martinelli Giovanni Martinelli
Cisco Cisco
via Philips 12 via Philips 12
Monza 20900 Monza 20900
IT IT
Phone: +39 039 209 2044 Phone: +39 039 209 2044
Email: giomarti@cisco.com Email: giomarti@cisco.com
Steve Balls Steve Balls
Metaswitch Metaswitch
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
UJ UJ
Phone: +44 208 366 1177 Phone: +44 208 366 1177
Email: steve.balls@metaswitch.com Email: steve.balls@metaswitch.com
Ben Wright Ben Wright
 End of changes. 12 change blocks. 
20 lines changed or deleted 80 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/