draft-ietf-teas-rsvp-te-srlg-collect-04.txt   draft-ietf-teas-rsvp-te-srlg-collect-05.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 September 15, 2016 Telefonica Global CTO Expires October 4, 2016 Telefonica Global CTO
M. Hartley M. Hartley
Z. Ali Z. Ali
Cisco Cisco
C. Margaria C. Margaria
March 15, 2016 April 4, 2016
RSVP-TE Extensions for Collecting SRLG Information RSVP-TE Extensions for Collecting SRLG Information
draft-ietf-teas-rsvp-te-srlg-collect-04 draft-ietf-teas-rsvp-te-srlg-collect-05
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 September 15, 2016. This Internet-Draft will expire on October 4, 2016.
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 5, line 41 skipping to change at page 5, line 41
it being made by the ingress node. it being made by the ingress node.
It may be preferable for the SRLG collection request to be It may be preferable for the SRLG collection request to be
understood by all nodes along the LSP's path, or it may be more understood by all nodes along the LSP's path, or it may be more
important for the LSP to be established successfully even if it important for the LSP to be established successfully even if it
traverses nodes that cannot supply SRLG information or have not traverses nodes that cannot supply SRLG information or have not
implemented the procedures specified in this document. It is implemented the procedures specified in this document. It is
desirable for the ingress node to make the SRLG collection request desirable for the ingress node to make the SRLG collection request
in a manner that best suits its own policy. in a manner that best suits its own policy.
When SRLG collection has been requested by the ingress node, the
egress node reflects this by including the collection request in
the Resv message.
3.2. SRLG Collection 3.2. SRLG Collection
If requested, the SRLG information is collected during the setup If requested, the SRLG information is collected during the setup
of an LSP. SRLG information is for each hop is added to the Path of an LSP. SRLG information is for each hop is added to the Path
RRO during Path message processing. The same information is also RRO during Path message processing. The same information is also
added to the Resv RRO during Resv processing at each hop. The added to the Resv RRO during Resv processing at each hop. The
endpoints of the LSP can make use of the collected SRLG endpoints of the LSP can make use of the collected SRLG
information, for example, for routing, sharing and TE link information, for example, for routing, sharing and TE link
configuration purposes. configuration purposes.
 End of changes. 5 change blocks. 
8 lines changed or deleted 4 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/