draft-ietf-ccamp-rsvp-te-srlg-collect-02.txt   draft-ietf-ccamp-rsvp-te-srlg-collect-03.txt 
Network Working Group F. Zhang, Ed. Network Working Group F. Zhang, Ed.
Internet-Draft D. Li Internet-Draft D. Li
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: August 29, 2013 O. Gonzalez de Dios, Ed. Expires: April 04, 2014 O. Gonzalez de Dios, Ed.
Telefonica I+D Telefonica I+D
C. Margaria C. Margaria
Nokia Siemens Networks Nokia Siemens Networks
M. Hartley M. Hartley
Cisco Cisco
February 25, 2013 October 01, 2013
RSVP-TE Extensions for Collecting SRLG Information RSVP-TE Extensions for Collecting SRLG Information
draft-ietf-ccamp-rsvp-te-srlg-collect-02 draft-ietf-ccamp-rsvp-te-srlg-collect-03
Abstract Abstract
This document provides extensions for the Resource ReserVation This document provides extensions for the Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE) to support automatic Protocol-Traffic Engineering (RSVP-TE) to support automatic
collection of Shared Risk Link Group (SRLG) Information for the TE collection of Shared Risk Link Group (SRLG) Information for the TE
link formed by a LSP. link formed by a LSP.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 29, 2013. This Internet-Draft will expire on April 04, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. RSVP-TE Requirements . . . . . . . . . . . . . . . . . . . . . 3 2. RSVP-TE Requirements . . . . . . . . . . . . . . . . . . . . 3
2.1. SRLG Collection Indication . . . . . . . . . . . . . . . . 3 2.1. SRLG Collection Indication . . . . . . . . . . . . . . . 3
2.2. SRLG Collection . . . . . . . . . . . . . . . . . . . . . 3 2.2. SRLG Collection . . . . . . . . . . . . . . . . . . . . . 3
2.3. SRLG Update . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. SRLG Update . . . . . . . . . . . . . . . . . . . . . . . 3
3. RSVP-TE Extensions (Encoding) . . . . . . . . . . . . . . . . 3 3. RSVP-TE Extensions (Encoding) . . . . . . . . . . . . . . . . 3
3.1. SRLG Collection Flag . . . . . . . . . . . . . . . . . . . 4 3.1. SRLG Collection Flag . . . . . . . . . . . . . . . . . . 3
3.2. SRLG sub-object . . . . . . . . . . . . . . . . . . . . . 4 3.2. SRLG sub-object . . . . . . . . . . . . . . . . . . . . . 4
4. Signaling Procedures . . . . . . . . . . . . . . . . . . . . . 5 4. Signaling Procedures . . . . . . . . . . . . . . . . . . . . 5
4.1. SRLG Collection . . . . . . . . . . . . . . . . . . . . . 5 4.1. SRLG Collection . . . . . . . . . . . . . . . . . . . . . 5
4.2. SRLG Update . . . . . . . . . . . . . . . . . . . . . . . 7 4.2. SRLG Update . . . . . . . . . . . . . . . . . . . . . . . 7
5. Manageability Considerations . . . . . . . . . . . . . . . . . 7 5. Manageability Considerations . . . . . . . . . . . . . . . . 7
5.1. Policy Configuration . . . . . . . . . . . . . . . . . . . 7 5.1. Policy Configuration . . . . . . . . . . . . . . . . . . 7
5.2. Coherent SRLG IDs . . . . . . . . . . . . . . . . . . . . 8 5.2. Coherent SRLG IDs . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7.1. RSVP Attribute Bit Flags . . . . . . . . . . . . . . . . . 8 7.1. RSVP Attribute Bit Flags . . . . . . . . . . . . . . . . 8
7.2. ROUTE_RECORD Object . . . . . . . . . . . . . . . . . . . 8 7.2. ROUTE_RECORD Object . . . . . . . . . . . . . . . . . . . 8
7.2.1. SRLG sub-object Flags . . . . . . . . . . . . . . . . 9 7.2.1. SRLG sub-object Flags . . . . . . . . . . . . . . . . 9
7.3. Policy Control Failure Error subcodes . . . . . . . . . . 9 7.3. Policy Control Failure Error subcodes . . . . . . . . . . 9
8. Contributing Authors . . . . . . . . . . . . . . . . . . . . . 10 8. Contributing Authors . . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
10. Normative References . . . . . . . . . . . . . . . . . . . . . 10 10. Normative References . . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
It is important to understand which TE links in the network might be It is important to understand which TE links in the network might be
at risk from the same failures. In this sense, a set of links may at risk from the same failures. In this sense, a set of links may
constitute a 'shared risk link group' (SRLG) if they share a resource constitute a 'shared risk link group' (SRLG) if they share a resource
whose failure may affect all links in the set [RFC4202]. whose failure may affect all links in the set [RFC4202].
On the other hand, as described in [RFC4206] and [RFC6107], H-LSP On the other hand, as described in [RFC4206] and [RFC6107], H-LSP
(Hierarchical LSP) or S-LSP (stitched LSP) can be used for carrying (Hierarchical LSP) or S-LSP (stitched LSP) can be used for carrying
skipping to change at page 4, line 27 skipping to change at page 4, line 11
The rules of the processing of the Attribute Flags TLV are not The rules of the processing of the Attribute Flags TLV are not
changed. changed.
3.2. SRLG sub-object 3.2. SRLG sub-object
This document defines a new RRO sub-object (ROUTE_RECORD sub-object) This document defines a new RRO sub-object (ROUTE_RECORD sub-object)
to record the SRLG information of the LSP. Its format is modeled on to record the SRLG information of the LSP. Its format is modeled on
the RRO sub-objects defined in RFC 3209 [RFC3209]. the RRO sub-objects defined in RFC 3209 [RFC3209].
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 | Flags | | Type | Length | Reserved | Flags |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SRLG ID 1 (4 bytes) | | SRLG ID 1 (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ ...... ~ ~ ...... ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SRLG ID n (4 bytes) | | SRLG ID n (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type Type
The type of the sub-object, to be assigned by IANA, which is The type of the sub-object, to be assigned by IANA, which is
recommended 34. recommended 34.
Length Length
The Length contains the total length of the sub-object in bytes, The Length contains the total length of the sub-object in bytes,
including the Type and Length fields. The Length depends on the including the Type and Length fields. The Length depends on the
skipping to change at page 8, line 31 skipping to change at page 8, line 21
6. Security Considerations 6. Security Considerations
This document does not introduce any additional security issues above This document does not introduce any additional security issues above
those identified in [RFC5920][RFC3209][RFC3473] those identified in [RFC5920][RFC3209][RFC3473]
7. IANA Considerations 7. IANA Considerations
7.1. RSVP Attribute Bit Flags 7.1. RSVP Attribute Bit Flags
IANA has created a registry and manages the space of attributes bit IANA has created a registry and manages the space of attributes bit
flags of Attribute Flags TLV as described in section 11.3 of flags of Attribute Flags TLV, as described in section 11.3 of
[RFC5420]. It is requested that IANA makes assignments from the [RFC5420], in the "Attributes TLV Space" section of the "Resource
Attribute Bit Flags. Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters"
registry located in https://www.iana.org/assignments/rsvp-te-
parameters/rsvp-te-parameters.xhtml. It is requested that IANA makes
assignments from the Attribute Bit Flags.
This document introduces a new Attribute Bit Flag: This document introduces a new Attribute Bit Flag:
o Bit number: TBD (12) o Bit number: TBD (10)
o Defining RFC: this I-D o Defining RFC: this I-D
o Name of bit: SRLG Collection Flag o Name of bit: SRLG Collection Flag
o The meaning of the Attribute Flags TLV on a Path is defined in o The meaning of the SRLG Collection Flag is defined in this I-D
this I-D
7.2. ROUTE_RECORD Object 7.2. ROUTE_RECORD Object
IANA has made the following assignments in the "Class Names, Class IANA has made the following assignments in the "Class Names, Class
Numbers, and Class Types" section of the "RSVP PARAMETERS" registry Numbers, and Class Types" section of the "RSVP PARAMETERS" registry
located at http://www.iana.org/assignments/rsvp-parameters. We located at http://www.iana.org/assignments/rsvp-parameters. We
request that IANA make assignments from the ROUTE_RECORD RFC 3209 request that IANA make assignments from the ROUTE_RECORD RFC 3209
[RFC3209] portions of this registry. [RFC3209] portions of this registry.
This document introduces a new RRO sub-object: This document introduces a new RRO sub-object:
Type Name Reference Type Name Reference
--------- ---------------------- --------- --------- ---------------------- ---------
TBD (34) SRLG sub-object This I-D TBD (34) SRLG sub-object This I-D
7.2.1. SRLG sub-object Flags 7.2.1. SRLG sub-object Flags
It is requested that the IANA ceates a registry to manage the space It is requested that the IANA ceates a registry to manage the space
of bit flags of the SRLG sub-object defined in this document. It is of bit flags of the SRLG sub-object defined in this document. It is
requested that IANA makes assignments from the SRLG sub-object Flags. requested that IANA makes assignments from the SRLG sub-object Flags.
This document introduces two new SRLG sub-object Flags. This document introduces two new SRLG sub-object Flags.
+------------+-------------------+---------------+ +------------+-------------------+---------------+
| Bit Number | Name | Reference | | Bit Number | Name | Reference |
+------------+-------------------+---------------+ +------------+-------------------+---------------+
| 1 | SRLG-list edited | This document | | 1 | SRLG-list edited | This document |
| 2 | Partial SRLG-list | This document | | 2 | Partial SRLG-list | This document |
+------------+-------------------+---------------+ +------------+-------------------+---------------+
7.3. Policy Control Failure Error subcodes 7.3. Policy Control Failure Error subcodes
IANA has made the following assignments in the "Error Codes and IANA has made the following assignments in the "Error Codes and
Globally-Defined Error Value Sub-Codes" section of the "RSVP Globally-Defined Error Value Sub-Codes" section of the "RSVP
PARAMETERS" registry located at PARAMETERS" registry located at http://www.iana.org/assignments/rsvp-
http://www.iana.org/assignments/rsvp-parameters. We request that parameters. We request that IANA make assignments from the Policy
IANA make assignments from the Policy Control Failure Sub-Codes Control Failure Sub-Codes registry.
registry.
This document introduces a new Policy Control Failure Error sub-code: This document introduces a new Policy Control Failure Error sub-code:
o Error sub-code: TBD (108) o Error sub-code: TBD (108)
o Defining RFC: this I-D o Defining RFC: this I-D
o Name of error sub-code: SRLG Recording Rejected o Name of error sub-code: SRLG Recording Rejected
o The meaning of the SRLG Recording Rejected error sub-code is o The meaning of the SRLG Recording Rejected error sub-code is
skipping to change at page 11, line 13 skipping to change at page 10, line 43
February 2011. February 2011.
Authors' Addresses Authors' Addresses
Fatai Zhang (editor) Fatai Zhang (editor)
Huawei Huawei
F3-5-B RD Center F3-5-B RD Center
Bantian, Longgang District, Shenzhen 518129 Bantian, Longgang District, Shenzhen 518129
P.R.China P.R.China
Phone:
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Dan Li Dan Li
Huawei Huawei
F3-5-B RD Center F3-5-B RD Center
Bantian, Longgang District, Shenzhen 518129 Bantian, Longgang District, Shenzhen 518129
P.R.China P.R.China
Phone:
Email: danli@huawei.com Email: danli@huawei.com
Oscar Gonzalez de Dios (editor) Oscar Gonzalez de Dios (editor)
Telefonica I+D Telefonica I+D
Don Ramon de la Cruz Don Ramon de la Cruz
Madrid, 28006 Madrid 28006
Spain Spain
Phone: +34 913328832 Phone: +34 913328832
Email: ogondio@tid.es Email: ogondio@tid.es
Cyril Margaria Cyril Margaria
Nokia Siemens Networks Nokia Siemens Networks
St Martin Strasse 76 St Martin Strasse 76
Munich, 81541 Munich 81541
Germany Germany
Phone: +49 89 5159 16934 Phone: +49 89 5159 16934
Email: cyril.margaria@nsn.com Email: cyril.margaria@nsn.com
Matt Hartley Matt Hartley
Cisco Cisco
Phone:
Email: mhartley@cisco.com Email: mhartley@cisco.com
 End of changes. 20 change blocks. 
61 lines changed or deleted 59 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/