draft-ietf-mpls-residence-time-08.txt   draft-ietf-mpls-residence-time-09.txt 
MPLS Working Group G. Mirsky MPLS Working Group G. Mirsky
Internet-Draft S. Ruffini Internet-Draft S. Ruffini
Intended status: Standards Track E. Gray Intended status: Standards Track E. Gray
Expires: October 30, 2016 Ericsson Expires: October 30, 2016 Ericsson
J. Drake J. Drake
Juniper Networks Juniper Networks
S. Bryant S. Bryant
Cisco Systems Independent
A. Vainshtein A. Vainshtein
ECI Telecom ECI Telecom
April 28, 2016 April 28, 2016
Residence Time Measurement in MPLS network Residence Time Measurement in MPLS network
draft-ietf-mpls-residence-time-08 draft-ietf-mpls-residence-time-09
Abstract Abstract
This document specifies G-ACh based Residence Time Measurement and This document specifies G-ACh based Residence Time Measurement and
how it can be used by time synchronization protocols being how it can be used by time synchronization protocols being
transported over MPLS domain. transported over MPLS domain.
Residence time is the variable part of propagation delay of timing Residence time is the variable part of propagation delay of timing
and synchronization messages and knowing what this delay is for each and synchronization messages and knowing what this delay is for each
message allows for a more accurate determination of the delay to be message allows for a more accurate determination of the delay to be
skipping to change at page 13, line 11 skipping to change at page 13, line 11
255. The node MUST add RTM_SET sub-TLV with the same address it used 255. The node MUST add RTM_SET sub-TLV with the same address it used
in RRO sub-object at the beginning of the RTM_SET TLV in associated in RRO sub-object at the beginning of the RTM_SET TLV in associated
outgoing Resv message before forwarding it upstream. If the outgoing Resv message before forwarding it upstream. If the
calculated TTL value been set to 255, as described above, then the I calculated TTL value been set to 255, as described above, then the I
flag in node RTM_SET TLV MUST be set to 1 before Resv message flag in node RTM_SET TLV MUST be set to 1 before Resv message
forwarded upstream. Otherwise, the I flag MUST be cleared (0). forwarded upstream. Otherwise, the I flag MUST be cleared (0).
The ingress node MAY inspect the I bit flag received in each RTM_SET The ingress node MAY inspect the I bit flag received in each RTM_SET
TLV contained in the LSP_ATTRIBUTES object of a received Resv TLV contained in the LSP_ATTRIBUTES object of a received Resv
message. Presence of the RTM_SET TLV with I bit field set to 1 message. Presence of the RTM_SET TLV with I bit field set to 1
indicates that some RTM nodes along the LSP could been included in indicates that some RTM nodes along the LSP could be included in the
the calculation of the residence time. An ingress node MAY choose to calculation of the residence time. An ingress node MAY choose to
resignal the LSP to include all RTM nodes or simply notify the user resignal the LSP to include all RTM nodes or simply notify the user
via a management interface. via a management interface.
There are scenarios when some information is removed from an RRO due There are scenarios when some information is removed from an RRO due
to policy processing (e.g., as may happen between providers) or RRO to policy processing (e.g., as may happen between providers) or RRO
is limited due to size constraints . Such changes affect the core is limited due to size constraints . Such changes affect the core
assumption of the method to control processing of RTM packets. RTM assumption of the method to control processing of RTM packets. RTM
SHOULD NOT be used if it is not guaranteed that RRO contains complete SHOULD NOT be used if it is not guaranteed that RRO contains complete
information. information.
skipping to change at page 26, line 42 skipping to change at page 26, line 42
Ericsson Ericsson
Email: eric.gray@ericsson.com Email: eric.gray@ericsson.com
John Drake John Drake
Juniper Networks Juniper Networks
Email: jdrake@juniper.net Email: jdrake@juniper.net
Stewart Bryant Stewart Bryant
Cisco Systems Independent
Email: stbryant@cisco.com Email: stewart.bryant@gmail.com
Alexander Vainshtein Alexander Vainshtein
ECI Telecom ECI Telecom
Email: Alexander.Vainshtein@ecitele.com Email: Alexander.Vainshtein@ecitele.com
 End of changes. 5 change blocks. 
6 lines changed or deleted 6 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/