draft-ietf-mpls-residence-time-10.txt   draft-ietf-mpls-residence-time-11.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: January 6, 2017 Ericsson Expires: January 22, 2017 Ericsson
J. Drake J. Drake
Juniper Networks Juniper Networks
S. Bryant S. Bryant
Independent Independent
A. Vainshtein A. Vainshtein
ECI Telecom ECI Telecom
July 5, 2016 July 21, 2016
Residence Time Measurement in MPLS network Residence Time Measurement in MPLS network
draft-ietf-mpls-residence-time-10 draft-ietf-mpls-residence-time-11
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 January 6, 2017. This Internet-Draft will expire on January 22, 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 19, line 44 skipping to change at page 19, line 44
+-------+----------------------------+---------------+ +-------+----------------------------+---------------+
Table 1: New Residence Time Measurement Table 1: New Residence Time Measurement
8.2. New RTM TLV Registry 8.2. New RTM TLV Registry
IANA is requested to create sub-registry in Generic Associated IANA is requested to create sub-registry in Generic Associated
Channel (G-ACh) Parameters Registry called "MPLS RTM TLV Registry". Channel (G-ACh) Parameters Registry called "MPLS RTM TLV Registry".
All code points in the range 0 through 127 in this registry shall be All code points in the range 0 through 127 in this registry shall be
allocated according to the "IETF Review" procedure as specified in allocated according to the "IETF Review" procedure as specified in
[RFC5226] . Remaining code points are allocated according to the [RFC5226] . Code points in the range 128 through 191 in this registry
table below. This document defines the following new values RTM TLV shall be allocated according to the "First Come First Served"
type s: procedure as specified in [RFC5226]. This document defines the
following new values RTM TLV type s:
+-----------+-----------------------------+-------------------------+ +-----------+-------------------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-----------+-----------------------------+-------------------------+ +-----------+-------------------------------+---------------+
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1 | No payload | This document | | 1 | No payload | This document |
| 2 | PTPv2, Ethernet | This document | | 2 | PTPv2, Ethernet encapsulation | This document |
| | encapsulation | | | 3 | PTPv2, IPv4 Encapsulation | This document |
| 3 | PTPv2, IPv4 Encapsulation | This document | | 4 | PTPv2, IPv6 Encapsulation | This document |
| 4 | PTPv2, IPv6 Encapsulation | This document | | 5 | NTP | This document |
| 5 | NTP | This document | | 6-127 | Unassigned | |
| 6-127 | Reserved | IETF Consensus | | 128 - 191 | Unassigned | |
| 128 - 191 | Reserved | First Come First Served | | 192 - 254 | Private Use | This document |
| 192 - 255 | Reserved | Private Use | | 255 | Reserved | This document |
+-----------+-----------------------------+-------------------------+ +-----------+-------------------------------+---------------+
Table 2: RTM TLV Type Table 2: RTM TLV Type
8.3. New RTM Sub-TLV Registry 8.3. New RTM Sub-TLV Registry
IANA is requested to create sub-registry in MPLS RTM TLV Registry, IANA is requested to create sub-registry in MPLS RTM TLV Registry,
requested in Section 8.2, called "MPLS RTM Sub-TLV Registry". All requested in Section 8.2, called "MPLS RTM Sub-TLV Registry". All
code points in the range 0 through 127 in this registry shall be code points in the range 0 through 127 in this registry shall be
allocated according to the "IETF Review" procedure as specified in allocated according to the "IETF Review" procedure as specified in
[RFC5226] . Remaining code points are allocated according to the [RFC5226] . Code points in the range 128 through 191 in this registry
table below. This document defines the following new values RTM sub- shall be allocated according to the "First Come First Served"
TLV types: procedure as specified in [RFC5226]. . This document defines the
following new values RTM sub-TLV types:
+-----------+-------------+-------------------------+ +-----------+-------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-----------+-------------+-------------------------+ +-----------+-------------+---------------+
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1 | PTP 2-step | This document | | 1 | PTP 2-step | This document |
| 2-127 | Reserved | IETF Consensus | | 2-127 | Unassigned | |
| 128 - 191 | Reserved | First Come First Served | | 128 - 191 | Unassigned | |
| 192 - 255 | Reserved | Private Use | | 192 - 254 | Private Use | This document |
+-----------+-------------+-------------------------+ | 255 | Reserved | This document |
+-----------+-------------+---------------+
Table 3: RTM Sub-TLV Type Table 3: RTM Sub-TLV Type
8.4. RTM Capability sub-TLV in OSPFv2 8.4. RTM Capability sub-TLV in OSPFv2
IANA is requested to assign a new type for RTM Capability sub-TLV IANA is requested to assign a new type for RTM Capability sub-TLV
from OSPFv2 Extended Link TLV Sub-TLVs registry as follows: from OSPFv2 Extended Link TLV Sub-TLVs registry as follows:
+-------+----------------+---------------+ +-------+----------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
skipping to change at page 21, line 44 skipping to change at page 21, line 44
| | | TTRIBUTES | ATTRIBUTES | Hop Att | | | | | TTRIBUTES | ATTRIBUTES | Hop Att | |
| | | | | ributes | | | | | | | ributes | |
+-----+------------+-----------+---------------+---------+----------+ +-----+------------+-----------+---------------+---------+----------+
| TBA | RTM_SET | Yes | No | No | This | | TBA | RTM_SET | Yes | No | No | This |
| 4 | sub-object | | | | document | | 4 | sub-object | | | | document |
+-----+------------+-----------+---------------+---------+----------+ +-----+------------+-----------+---------------+---------+----------+
Table 6: RTM_SET Sub-object Type Table 6: RTM_SET Sub-object Type
IANA requested to create new sub-registry for sub-TLV types of IANA requested to create new sub-registry for sub-TLV types of
RTM_SET sub-object as follows: RTM_SET sub-object. All code points in the range 0 through 127 in
this registry shall be allocated according to the "IETF Review"
procedure as specified in [RFC5226] . Code points in the range 128
through 191 in this registry shall be allocated according to the
"First Come First Served" procedure as specified in [RFC5226]. This
document defines the following new values of RTM_SET object sub-
object types:
+-----------+----------------------+-------------------------+ +-----------+----------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-----------+----------------------+-------------------------+ +-----------+----------------------+---------------+
| 0 | Reserved | | | 0 | Reserved | This document |
| 1 | IPv4 address | This document | | 1 | IPv4 address | This document |
| 2 | IPv6 address | This document | | 2 | IPv6 address | This document |
| 3 | Unnumbered interface | This document | | 3 | Unnumbered interface | This document |
| 4-127 | Reserved | IETF Consensus | | 4-127 | Unassigned | |
| 128 - 191 | Reserved | First Come First Served | | 128 - 191 | Unassigned | |
| 192 - 255 | Reserved | Private Use | | 192 - 254 | Private Use | This document |
+-----------+----------------------+-------------------------+ | 255 | Reserved | This document |
+-----------+----------------------+---------------+
Table 7: RTM_SET object sub-object types Table 7: RTM_SET object sub-object types
8.7. RTM_SET Attribute Flag 8.7. RTM_SET Attribute Flag
IANA is requested to assign new flag from Attribute Flags registry IANA is requested to assign new flag from Attribute Flags registry
+-----+--------+-----------+------------+-----+-----+---------------+ +-----+--------+-----------+------------+-----+-----+---------------+
| Bit | Name | Attribute | Attribute | RRO | ERO | Reference | | Bit | Name | Attribute | Attribute | RRO | ERO | Reference |
| No | | Flags | Flags Resv | | | | | No | | Flags | Flags Resv | | | |
 End of changes. 10 change blocks. 
45 lines changed or deleted 55 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/