draft-ietf-teas-rsvp-te-srlg-collect-07.txt   draft-ietf-teas-rsvp-te-srlg-collect-08.txt 
TEAS Working Group F. Zhang, Ed. TEAS 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 February 16, 2017 Telefonica Global CTO Expires February 24, 2017 Telefonica Global CTO
M. Hartley M. Hartley
Z. Ali Z. Ali
Cisco Cisco
C. Margaria C. Margaria
August 16, 2016 August 24, 2016
RSVP-TE Extensions for Collecting SRLG Information RSVP-TE Extensions for Collecting SRLG Information
draft-ietf-teas-rsvp-te-srlg-collect-07 draft-ietf-teas-rsvp-te-srlg-collect-08
Abstract Abstract
This document provides extensions for the Resource ReserVation This document provides extensions for the Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE), including GMPLS, to support Protocol-Traffic Engineering (RSVP-TE), including GMPLS, to support
automatic collection of Shared Risk Link Group (SRLG) information for automatic collection of Shared Risk Link Group (SRLG) information for
the TE link formed by a Label Switched Path (LSP). the TE link formed by a Label Switched Path (LSP).
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 November 26, 2016. This Internet-Draft will expire on February 24, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 11, line 45 skipping to change at page 11, line 45
for further study. for further study.
7. Security Considerations 7. Security Considerations
This document builds on the mechanisms defined in [RFC3473], which This document builds on the mechanisms defined in [RFC3473], which
also discusses related security measures. In addition, [RFC5920] also discusses related security measures. In addition, [RFC5920]
provides an overview of security vulnerabilities and protection provides an overview of security vulnerabilities and protection
mechanisms for the GMPLS control plane. The procedures defined in mechanisms for the GMPLS control plane. The procedures defined in
this document permit the transfer of SRLG data between layers or this document permit the transfer of SRLG data between layers or
domains during the signaling of LSPs, subject to policy at the layer domains during the signaling of LSPs, subject to policy at the layer
or domain boundary. It is recommended that domain/layer boundary or domain boundary. As described in section 5.3 and section 6.1,
policies take the implications of releasing SRLG information into local policy as specified by the network operator will explicitly
consideration and behave accordingly during LSP signaling. mandate the processing of information at domain or layer boundaries.
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 the Attribute IANA has created a registry and manages the space of the Attribute
bit flags of the Attribute Flags TLV, as described in section 11.3 of bit flags of the Attribute Flags TLV, as described in section 11.3 of
RFC 5420 [RFC5420], in the "Attribute Flags" section of the "Resource RFC 5420 [RFC5420], in the "Attribute Flags" section of the "Resource
Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters" Reservation Protocol-Traffic Engineering (RSVP-TE) Parameters"
registry located in http://www.iana.org/assignments/rsvp-te- registry located in http://www.iana.org/assignments/rsvp-te-
parameters". parameters".
 End of changes. 5 change blocks. 
7 lines changed or deleted 7 lines changed or added

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