draft-ietf-teas-lsp-attribute-ro-04.txt   draft-ietf-teas-lsp-attribute-ro-05.txt 
TEAS C. Margaria, Ed. TEAS C. Margaria, Ed.
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Standards Track G. Martinelli Intended status: Standards Track G. Martinelli
Expires: September 5, 2015 Cisco Expires: September 24, 2015 Cisco
S. Balls S. Balls
B. Wright B. Wright
Metaswitch Metaswitch
March 04, 2015 March 23, 2015
LSP Attribute in ERO LSP Attribute in ERO
draft-ietf-teas-lsp-attribute-ro-04 draft-ietf-teas-lsp-attribute-ro-05
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 a Label Switched Path (LSP). This apply to the whole of the path of a Label Switched Path (LSP). This
document defines an extension to the RSVP Explicit Route Object (ERO) document defines an extension to the RSVP Explicit Route Object (ERO)
and Record Route Object (RRO) objects to allow it to specify or and Record Route Object (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 38 skipping to change at page 1, line 38
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 5, 2015. This Internet-Draft will expire on September 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 3, line 21 skipping to change at page 3, line 21
of generic per-Hop attributes. of generic per-Hop attributes.
1.1. Requirements Language 1.1. 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].
2. ERO Hop Attributes Subobject 2. ERO Hop Attributes Subobject
The ERO Hop Attributes subobject MAY be carried in the ERO or SERO The ERO Hop Attributes subobject is OPTIONAL. If used it is carried
object if they are present. The subobject uses the standard format in the ERO or SERO. The subobject uses the standard format of an ERO
of an ERO subobject. subobject.
2.1. Encoding 2.1. Encoding
The length is variable and content is a list of HOP Attributes TLVs The length is variable and content is a list of HOP Attributes TLVs
defined in Section 2.2. The size of the ERO sub-object limits the defined in Section 2.2. The size of the ERO sub-object limits the
size of the attribute TLV to 250 bytes. The typical size of size of the attribute TLV to 250 bytes. The typical size of
currently defined and forthcoming LSP_ATTRIBUTE TLVs applicable to a currently defined and forthcoming LSP_ATTRIBUTE TLVs applicable to a
specific hop (WSON_SIGNALING, Objective Function (OF) and Metric) is specific hop (WSON_SIGNALING, Objective Function (OF) and Metric) is
not foreseen to exceed this limit. not foreseen to exceed this limit.
skipping to change at page 3, line 48 skipping to change at page 3, line 48
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L| Type | Length | Reserved |R| |L| Type | Length | Reserved |R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// Attributes TLVs // // Attributes TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The L, Type and Length parameters are as defined in [RFC3209] The L, Type and Length parameters are as defined in [RFC3209]
Section 4.3.3. The L bit MUST be set to 0. The Type for the ERO Hop Section 4.3.3. The L bit MUST be set to 0. The Type for the ERO Hop
Attributes subobject is TBA by IANA. The attributes TLV are encoded Attributes subobject is TBA-1 by IANA. The attributes TLV are
as defined in Section 2.2. encoded as defined in Section 2.2.
Reserved Reserved, MUST be set to 0 when the subobject is inserted Reserved Reserved, MUST be set to 0 when the subobject is inserted
in the ERO, MUST NOT be changed when a node processes the ERO and in the ERO, MUST NOT be changed when a node processes the ERO and
MUST be ignored on the node addressed by the preceding ERO MUST be ignored on the node addressed by the preceding ERO
subobjects. subobjects.
R This bit reflects the LSP_REQUIRED_ATTRIBUTE and LSP_ATTRIBUTE R This bit reflects the LSP_REQUIRED_ATTRIBUTE and LSP_ATTRIBUTE
semantic defined in [RFC5420]. When set it indicates required hop semantic defined in [RFC5420]. When set it indicates required hop
attributes to be processed by the node. When cleared, it attributes to be processed by the node. When cleared, it
indicates that the hop attributes are not required as described in indicates that the hop attributes are not required as described in
Section 2.3. Section 2.3.
Attributes TLVs The TLVs as defined in Section 2.2. Attributes TLVs The TLVs as defined in Section 2.2.
2.2. HOP Attributes TLVs 2.2. HOP Attributes TLVs
ERO Attributes carried by the new objects defined in this document ERO Attributes carried by the new objects defined in this document
are encoded within TLVs. One or more TLVs MAY be present in each are encoded within TLVs. Each object MAY contain one or more TLVs.
object. There are no ordering rules for TLVs, and interpretation There are no ordering rules for TLVs, and interpretation SHOULD NOT
SHOULD NOT be placed on the order in which TLVs are received. The be placed on the order in which TLVs are received. The TLV format is
TLV format is defined in [RFC5420] Section 3. defined in [RFC5420] Section 3.
The Attribute Flags TLV defined in [RFC5420] MAY be carried in an ERO The Attribute Flags TLV defined in [RFC5420] are carried in an ERO
Hop Attributes Subobject. Flags set in the an Attribute Flags TLV Hop Attributes Subobject. Flags set in the an Attribute Flags TLV
[RFC5420] carried in an ERO Hop Attributes Subobject SHALL be [RFC5420] carried in an ERO Hop Attributes Subobject SHALL be
interpreted in the context of the received ERO. Only a subset of interpreted in the context of the received ERO. Only a subset of
defined flags are defined as valid for use in Attribute Flags TLV defined flags are defined as valid for use in Attribute Flags TLV
carried in an ERO Hop Attributes Subobject. Invalid flags SHALL be carried in an ERO Hop Attributes Subobject. Invalid flags SHALL be
silently ignored. Unknown flags SHOULD trigger the generation of a silently ignored. Unknown flags SHOULD trigger the generation of a
PathErr with Error Code "Unknown Attributes Bit" as defined in PathErr with Error Code "Unknown Attributes Bit" as defined in
[RFC5420] Section 5.2. The set of valid flags are defined in [RFC5420] Section 5.2. The set of valid flags are defined in
Section 4.3. Section 4.3.
skipping to change at page 6, line 23 skipping to change at page 6, line 23
Attributes Subobject. The processing of the Hop attribute TLVs Attributes Subobject. The processing of the Hop attribute TLVs
SHOULD be described in the documents defining them. SHOULD be described in the documents defining them.
3. RRO Hop Attributes Subobject 3. RRO Hop Attributes Subobject
In some cases it is important to determine if an OPTIONAL Hop In some cases it is important to determine if an OPTIONAL Hop
attribute has been processed by a node. attribute has been processed by a node.
3.1. Encoding 3.1. Encoding
The RRO Hop Attributes subobject MAY be carried in the RECORD_ROUTE The RRO Hop Attributes subobject is OPTIONAL. If used it is carried
object if it is present. The subobject uses the standard format of in the RECORD_ROUTE object. The subobject uses the standard format
an RRO subobject. of an RRO subobject.
The RRO Hop Attributes subobject is defined as follows: The RRO Hop Attributes subobject is defined as follows:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | | Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
// Attributes TLVs // // Attributes TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Type and Length parameters are as defined in [RFC3209] The Type and Length parameters are as defined in [RFC3209]
Section 4.4.1. The Type for the RRO Hop Attributes subobject is TBA Section 4.4.1. The Type for the RRO Hop Attributes subobject is
by IANA. The attributes TLV are encoded as defined in Section 2.2. TBA-2 by IANA. The attributes TLV are encoded as defined in
Section 2.2.
Reserved Reserved, MUST be set to 0 when the subobject is inserted Reserved Reserved, MUST be set to 0 when the subobject is inserted
in the RRO, MUST NOT be changed when a node process the RRO and in the RRO, MUST NOT be changed when a node process the RRO and
MUST be ignored on the node addressed by the preceding RRO MUST be ignored on the node addressed by the preceding RRO
subobjects. subobjects.
Attributes TLVs The processed or additional HOP Attributes, using Attributes TLVs The processed or additional HOP Attributes, using
the format defined in Section 2.2. the format defined in Section 2.2.
3.2. Procedures 3.2. Procedures
skipping to change at page 7, line 24 skipping to change at page 7, line 24
such subobjects SHOULD be forwarded unmodified by transit LSRs. such subobjects SHOULD be forwarded unmodified by transit LSRs.
It is noted that a node (e.g., a domain edge node) MAY edit the RRO It is noted that a node (e.g., a domain edge node) MAY edit the RRO
to prune/modify the RRO, including the RRO Hop Attribute subobject to prune/modify the RRO, including the RRO Hop Attribute subobject
before forwarding due to confidentiality policy or other reasons (for before forwarding due to confidentiality policy or other reasons (for
instance RRO size reduction). instance RRO size reduction).
3.2.2. Reporting Compliance with ERO Hop Attributes 3.2.2. Reporting Compliance with ERO Hop Attributes
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 Attributes an additional attribute, an LSR can add a RRO Hop Attributes
subobject with the HOP Attribute TLV which describes the attribute to subobject with the HOP Attribute TLV which describes the attribute to
be reported. The requirement to report compliance MUST be specified be reported. The requirement to report compliance MUST be specified
in the document that defines the usage of a Hop attribute. in the document that defines the usage of a Hop attribute.
3.2.3. Compatibility with RRO Attributes subobject 3.2.3. Compatibility with RRO Attributes subobject
The RRO Hop Attributes subobject extends the capability of the RRO The RRO Hop Attributes subobject extends the capability of the RRO
Attributes subobject defined in [RFC5420] Section 7.2 by allowing the Attributes subobject defined in [RFC5420] Section 7.2 by allowing the
node to report the attribute value. The mechanism defined in this node to report the attribute value. The mechanism defined in this
document is compatible with the RRO Attributes subobject using the document is compatible with the RRO Attributes subobject using the
skipping to change at page 7, line 48 skipping to change at page 7, line 48
LSP_REQUIRED_ATTRIBUTES objects, a node SHOULD use the RRO Attributes LSP_REQUIRED_ATTRIBUTES objects, a node SHOULD use the RRO Attributes
subobject to report processing of those attributes. subobject to report processing of those attributes.
For LSP attributes signaled in the ERO Hop Attributes subobject and For LSP attributes signaled in the ERO Hop Attributes subobject and
not in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES objects, if a not in the LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES objects, if a
node desires to report the attributes, it SHOULD use the RRO Hop node desires to report the attributes, it SHOULD use the RRO Hop
Attributes subobject and SHOULD NOT use the RRO Attributes subobject. Attributes subobject and SHOULD NOT use the RRO Attributes subobject.
Ingress nodes not supporting the RRO Hop Attributes subobject will Ingress nodes not supporting the RRO Hop Attributes subobject will
drop the information, as described in [RFC3209] Section 4.4.5. drop the information, as described in [RFC3209] Section 4.4.5.
A node MAY use the RRO Hop Attribute to report an LSP Attribute A node can use the RRO Hop Attribute to report an LSP Attribute
signaled in LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES only if the signaled in LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES only if the
following conditions are met: following conditions are met:
The Attribute and its corresponding flag is allowed on both the The Attribute and its corresponding flag is allowed on both the
LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES and LSP Hop Attributes LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES and LSP Hop Attributes
subobject. subobject.
The document defining this Attribute specify this specific The document defining this Attribute specify this specific
behavior. behavior.
skipping to change at page 8, line 25 skipping to change at page 8, line 25
IANA manages the "RSVP PARAMETERS" registry located at IANA manages the "RSVP PARAMETERS" registry located at
http://www.iana.org/assignments/rsvp-parameters/rsvp-parameters.xml. http://www.iana.org/assignments/rsvp-parameters/rsvp-parameters.xml.
We request IANA to make an allocation in the Sub-object type 20 We request IANA to make an allocation in the Sub-object type 20
EXPLICIT_ROUTE - Type 1 Explicit Route registry. EXPLICIT_ROUTE - Type 1 Explicit Route registry.
This document introduces a new ERO sub-object: This document introduces a new ERO sub-object:
Value Description Reference Value Description Reference
------ ----------------- ------------------------ ------ ----------------- ------------------------
TBA Hop Attributes This document, Section 2 TBA-1 Hop Attributes This document, Section 2
4.2. RRO LSP Attribute Subobject 4.2. RRO LSP Attribute Subobject
IANA manages the "RSVP PARAMETERS" registry located at IANA manages the "RSVP PARAMETERS" registry located at
http://www.iana.org/assignments/rsvp-parameters/rsvp-parameters.xml. http://www.iana.org/assignments/rsvp-parameters/rsvp-parameters.xml.
We request IANA to make an allocation in the Sub-object type 21 We request IANA to make an allocation in the Sub-object type 21
ROUTE_RECORD - Type 1 Route Record registry. We request the value to ROUTE_RECORD - Type 1 Route Record registry. We request the value to
be the same as Section 4.1. be the same as Section 4.1.
This document introduces a new RRO sub-object: This document introduces a new RRO sub-object:
Value Description Reference Value Description Reference
------ ----------------- ------------------------ ------ ----------------- ------------------------
TBA Hop Attributes This document, Section 3 TBA-2 Hop Attributes This document, Section 3
4.3. Existing Attribute Flags 4.3. Existing Attribute Flags
IANA manages the "Attribute Flags" registry as part of the "RSVP-TE IANA manages the "Attribute Flags" registry as part of the "RSVP-TE
PARAMETERS" registry located at http://www.iana.org/assignments/rsvp- PARAMETERS" registry located at http://www.iana.org/assignments/rsvp-
te-parameters/rsvp-te-parameters.xml. A new column in the registry te-parameters/rsvp-te-parameters.xml. A new column in the registry
is introduced by this document. This column indicates if the flag is is introduced by this document. This column indicates if the flag is
permitted to be used in an Attribute Flags TLV carried in the ERO Hop permitted to be used in an Attribute Flags TLV carried in the ERO Hop
Attributes Subobject. The column uses the heading "ERO" and the Attributes Subobject. The column uses the heading "ERO" and the
registry is to be updated as follows: registry is to be updated as follows:
skipping to change at page 13, line 26 skipping to change at page 13, line 26
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-05 (work in progress), February 2014. bound-05 (work in progress), February 2014.
[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-09 Optical Networks", draft-ietf-ccamp-wson-signaling-10
(work in progress), September 2014. (work in progress), March 2015.
[I-D.ietf-teas-rsvp-te-li-lb] [I-D.ietf-teas-rsvp-te-li-lb]
Dong, J., Chen, M., Li, Z., and D. Ceccarelli, "GMPLS Dong, J., Chen, M., Li, Z., and D. Ceccarelli, "GMPLS
RSVP-TE Extensions for Lock Instruct and Loopback", draft- RSVP-TE Extensions for Lock Instruct and Loopback", draft-
ietf-teas-rsvp-te-li-lb-04 (work in progress), February ietf-teas-rsvp-te-li-lb-05 (work in progress), March 2015.
2015.
[I-D.ietf-teas-rsvp-te-srlg-collect] [I-D.ietf-teas-rsvp-te-srlg-collect]
Zhang, F., Dios, O., Li, D., Margaria, C., Hartley, M., Zhang, F., Dios, O., Li, D., Margaria, C., Hartley, M.,
and Z. Ali, "RSVP-TE Extensions for Collecting SRLG and Z. Ali, "RSVP-TE Extensions for Collecting SRLG
Information", draft-ietf-teas-rsvp-te-srlg-collect-00 Information", draft-ietf-teas-rsvp-te-srlg-collect-00
(work in progress), December 2014. (work in progress), December 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-
 End of changes. 16 change blocks. 
27 lines changed or deleted 27 lines changed or added

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