draft-ietf-mpls-residence-time-07.txt   draft-ietf-mpls-residence-time-08.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 9, 2016 Ericsson Expires: October 30, 2016 Ericsson
J. Drake J. Drake
Juniper Networks Juniper Networks
S. Bryant S. Bryant
Cisco Systems Cisco Systems
A. Vainshtein A. Vainshtein
ECI Telecom ECI Telecom
April 7, 2016 April 28, 2016
Residence Time Measurement in MPLS network Residence Time Measurement in MPLS network
draft-ietf-mpls-residence-time-07 draft-ietf-mpls-residence-time-08
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 1, line 45 skipping to change at page 1, line 45
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 October 9, 2016. This Internet-Draft will expire on October 30, 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 12, line 22 skipping to change at page 12, line 22
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: RTM_SET TLV format Figure 6: RTM_SET TLV format
Type value (TBA5) will be assigned by IANA from its Attributes TLV Type value (TBA5) will be assigned by IANA from its Attributes TLV
Space sub-registry. Space sub-registry.
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. including the Type and Length fields.
The I flag MUST be set to 0 if the node identified in the Value field The I bit flag indicates whether the downstream RTM capable node
was able to find downstream RTM node and calculate distance to it. along the LSP is present in the RRO.
If the node failed to find the downstream RTM node, then the I flag
MUST be set to 1.
Reserved field must be zeroed on initiation and ignored on receipt. Reserved field must be zeroed on initiation and ignored on receipt.
The content of an RTM_SET TLV is a series of variable-length sub- The content of an RTM_SET TLV is a series of variable-length sub-
TLVs. Only a single RTM_SET can be present in the LSP_ATTRIBUTES TLVs. Only a single RTM_SET can be present in the LSP_ATTRIBUTES
object. The sub-TLVs are defined in Section 4.7.1 below. object. The sub-TLVs are defined in Section 4.7.1 below.
The following processing procedures apply to every RTM capable node The following processing procedures apply to every RTM capable node
along the LSP that in this paragraph is referred as node for sake of along the LSP that in this paragraph is referred as node for sake of
brevity. Each node MUST examine Resv message whether RTM_SET brevity. Each node MUST examine Resv message whether RTM_SET
skipping to change at page 13, line 7 skipping to change at page 13, line 5
downstream node with reachable RTM capable interface. If the node downstream node with reachable RTM capable interface. If the node
cannot find matching ID in RRO, then it MUST try to use ID of the cannot find matching ID in RRO, then it MUST try to use ID of the
next node in the RTM_SET until it finds the match or reaches the end next node in the RTM_SET until it finds the match or reaches the end
of RTM_SET TLV. If match have been found, then the calculated value of RTM_SET TLV. If match have been found, then the calculated value
is used by the node as TTL value in outgoing label to reach the next is used by the node as TTL value in outgoing label to reach the next
RTM capable node on the LSP. Otherwise, the TTL value MUST be set to RTM capable node on the LSP. Otherwise, the TTL value MUST be set to
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
field 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. forwarded upstream. Otherwise, the I flag MUST be cleared (0).
The ingress node MAY inspect values of I field in the received Resv The ingress node MAY inspect the I bit flag received in each RTM_SET
message that has RTM_SET Attribute Flag in the LSP_ATTRIBUTES object TLV contained in the LSP_ATTRIBUTES object of a received Resv
set. Presence of the RTM_SET TLV with I field set to 1 indicates message. Presence of the RTM_SET TLV with I bit field set to 1
that not all RTM nodes along the LSP could been included in the indicates that some RTM nodes along the LSP could been included in
calculation of the residence time. Re-signaling of the path MAY be the calculation of the residence time. An ingress node MAY choose to
performed. resignal the LSP to include all RTM nodes or simply notify the user
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.
4.7.1. RTM_SET Sub-TLVs 4.7.1. RTM_SET Sub-TLVs
 End of changes. 7 change blocks. 
16 lines changed or deleted 15 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/