draft-ietf-ccamp-rsvp-te-srlg-collect-05.txt   draft-ietf-ccamp-rsvp-te-srlg-collect-06.txt 
Network Working Group F. Zhang, Ed. Network Working Group F. Zhang, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track O. Gonzalez de Dios, Ed. Intended status: Standards Track O. Gonzalez de Dios, Ed.
Expires: January 5, 2015 Telefonica Global CTO Expires: February 1, 2015 Telefonica Global CTO
D. Li D. Li
Huawei Huawei
C. Margaria C. Margaria
M. Hartley M. Hartley
Z. Ali Z. Ali
Cisco Cisco
July 4, 2014 July 31, 2014
RSVP-TE Extensions for Collecting SRLG Information RSVP-TE Extensions for Collecting SRLG Information
draft-ietf-ccamp-rsvp-te-srlg-collect-05 draft-ietf-ccamp-rsvp-te-srlg-collect-06
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
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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 January 5, 2015. This Internet-Draft will expire on February 1, 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 8, line 11 skipping to change at page 8, line 11
belong to the same operator, or to several coordinated administrative belong to the same operator, or to several coordinated administrative
groups. Ensuring the aforementioned coherence of SRLG IDs is beyond groups. Ensuring the aforementioned coherence of SRLG IDs is beyond
the scope of this document. the scope of this document.
Further scenarios, where coherence in the SRLG IDs cannot be Further scenarios, where coherence in the SRLG IDs cannot be
guaranteed are out of the scope of the present document and are left guaranteed are out of the scope of the present document and are left
for further study. for further study.
7. Security Considerations 7. Security Considerations
This document does not introduce any additional security issues above This document builds on the mechanisms defined in [RFC3473], which
those identified in [RFC5920][RFC3209][RFC3473] also discusses related security measures. In addition, [RFC5920]
provides an overview of security vulnerabilities and protection
mechanisms for the GMPLS control plane. The procedures defined in
this document permit the transfer of SRLG data between layers or
domains during the signaling of LSPs, subject to policy at the layer
or domain boundary. It is recommended that domain/layer boundary
policies take the implications of releasing SRLG information into
consideration and behave accordingly during LSP signaling.
8. IANA Considerations 8. IANA Considerations
8.1. RSVP Attribute Bit Flags 8.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], in the "Attributes TLV Space" section of the "Resource [RFC5420], in the "Attributes TLV Space" section of the "Resource
Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters" Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters"
registry located in https://www.iana.org/assignments/rsvp-te- registry located in https://www.iana.org/assignments/rsvp-te-
parameters/rsvp-te-parameters.xhtml. It is requested that IANA makes parameters/rsvp-te-parameters.xhtml. It is requested that IANA makes
assignments from the Attribute Bit Flags. 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 (10) o Bit number: TBD (early allocation requested)
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 SRLG Collection Flag is defined in this I-D. o The meaning of the SRLG Collection Flag is defined in this I-D.
8.2. ROUTE_RECORD Object 8.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 (early SRLG sub-object This I-D
allocation
requested)
8.3. Policy Control Failure Error subcodes 8.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 http://www.iana.org/assignments/rsvp- PARAMETERS" registry located at http://www.iana.org/assignments/rsvp-
parameters. We request that IANA make assignments from the Policy parameters. We request that IANA make assignments from the Policy
Control Failure Sub-Codes registry. Control Failure Sub-Codes 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 (early allocation requested)
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
defined in this I-D defined in this I-D
9. Acknowledgements 9. Acknowledgements
skipping to change at page 10, line 34 skipping to change at page 10, line 39
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
Email: zhangfatai@huawei.com Email: zhangfatai@huawei.com
Oscar Gonzalez de Dios (editor) Oscar Gonzalez de Dios (editor)
Telefonica Global CTO Telefonica Global CTO
Don Ramon de la Cruz Distrito Telefonica, edificio sur, Ronda de la Comunicacion 28045
Madrid 28006 Madrid 28050
Spain Spain
Phone: +34 913328832 Phone: +34 913129647
Email: oscar.gonzalezdedios@telefonica.com Email: oscar.gonzalezdedios@telefonica.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
Email: danli@huawei.com Email: danli@huawei.com
Cyril Margaria Cyril Margaria
SabenerStr. 44 Suite 4001, 200 Somerset Corporate Blvd.
Munich 81547 Bridgewater, NJ 08807
Germany US
Phone: +49 89 5159 16934
Email: cyril.margaria@gmail.com Email: cyril.margaria@gmail.com
Matt Hartley Matt Hartley
Cisco Cisco
Email: mhartley@cisco.com Email: mhartley@cisco.com
Zafar Ali Zafar Ali
Cisco Cisco
 End of changes. 14 change blocks. 
19 lines changed or deleted 27 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/