--- 1/draft-ietf-mpls-residence-time-10.txt 2016-07-20 11:16:39.909360798 -0700 +++ 2/draft-ietf-mpls-residence-time-11.txt 2016-07-20 11:16:39.973362397 -0700 @@ -1,25 +1,25 @@ MPLS Working Group G. Mirsky Internet-Draft S. Ruffini Intended status: Standards Track E. Gray -Expires: January 6, 2017 Ericsson +Expires: January 22, 2017 Ericsson J. Drake Juniper Networks S. Bryant Independent A. Vainshtein ECI Telecom - July 5, 2016 + July 21, 2016 Residence Time Measurement in MPLS network - draft-ietf-mpls-residence-time-10 + draft-ietf-mpls-residence-time-11 Abstract This document specifies G-ACh based Residence Time Measurement and how it can be used by time synchronization protocols being transported over MPLS domain. Residence time is the variable part of propagation delay of timing and synchronization messages and knowing what this delay is for each message allows for a more accurate determination of the delay to be @@ -34,21 +34,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference 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 (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -864,60 +864,63 @@ +-------+----------------------------+---------------+ Table 1: New Residence Time Measurement 8.2. New RTM TLV Registry IANA is requested to create sub-registry in Generic Associated Channel (G-ACh) Parameters Registry called "MPLS RTM TLV Registry". 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] . Remaining code points are allocated according to the - table below. This document defines the following new values RTM TLV - type s: + [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 RTM TLV type s: - +-----------+-----------------------------+-------------------------+ + +-----------+-------------------------------+---------------+ | Value | Description | Reference | - +-----------+-----------------------------+-------------------------+ + +-----------+-------------------------------+---------------+ | 0 | Reserved | This document | | 1 | No payload | This document | - | 2 | PTPv2, Ethernet | This document | - | | encapsulation | | + | 2 | PTPv2, Ethernet encapsulation | This document | | 3 | PTPv2, IPv4 Encapsulation | This document | | 4 | PTPv2, IPv6 Encapsulation | This document | | 5 | NTP | This document | - | 6-127 | Reserved | IETF Consensus | - | 128 - 191 | Reserved | First Come First Served | - | 192 - 255 | Reserved | Private Use | - +-----------+-----------------------------+-------------------------+ + | 6-127 | Unassigned | | + | 128 - 191 | Unassigned | | + | 192 - 254 | Private Use | This document | + | 255 | Reserved | This document | + +-----------+-------------------------------+---------------+ Table 2: RTM TLV Type 8.3. New RTM Sub-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 code points in the range 0 through 127 in this registry shall be allocated according to the "IETF Review" procedure as specified in - [RFC5226] . Remaining code points are allocated according to the - table below. This document defines the following new values RTM sub- - TLV types: + [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 RTM sub-TLV types: - +-----------+-------------+-------------------------+ + +-----------+-------------+---------------+ | Value | Description | Reference | - +-----------+-------------+-------------------------+ + +-----------+-------------+---------------+ | 0 | Reserved | This document | | 1 | PTP 2-step | This document | - | 2-127 | Reserved | IETF Consensus | - | 128 - 191 | Reserved | First Come First Served | - | 192 - 255 | Reserved | Private Use | - +-----------+-------------+-------------------------+ + | 2-127 | Unassigned | | + | 128 - 191 | Unassigned | | + | 192 - 254 | Private Use | This document | + | 255 | Reserved | This document | + +-----------+-------------+---------------+ Table 3: RTM Sub-TLV Type 8.4. RTM Capability sub-TLV in OSPFv2 IANA is requested to assign a new type for RTM Capability sub-TLV from OSPFv2 Extended Link TLV Sub-TLVs registry as follows: +-------+----------------+---------------+ | Value | Description | Reference | @@ -951,33 +954,40 @@ | | | TTRIBUTES | ATTRIBUTES | Hop Att | | | | | | | ributes | | +-----+------------+-----------+---------------+---------+----------+ | TBA | RTM_SET | Yes | No | No | This | | 4 | sub-object | | | | document | +-----+------------+-----------+---------------+---------+----------+ Table 6: RTM_SET Sub-object Type 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 | - +-----------+----------------------+-------------------------+ - | 0 | Reserved | | + +-----------+----------------------+---------------+ + | 0 | Reserved | This document | | 1 | IPv4 address | This document | | 2 | IPv6 address | This document | | 3 | Unnumbered interface | This document | - | 4-127 | Reserved | IETF Consensus | - | 128 - 191 | Reserved | First Come First Served | - | 192 - 255 | Reserved | Private Use | - +-----------+----------------------+-------------------------+ + | 4-127 | Unassigned | | + | 128 - 191 | Unassigned | | + | 192 - 254 | Private Use | This document | + | 255 | Reserved | This document | + +-----------+----------------------+---------------+ Table 7: RTM_SET object sub-object types 8.7. RTM_SET Attribute Flag IANA is requested to assign new flag from Attribute Flags registry +-----+--------+-----------+------------+-----+-----+---------------+ | Bit | Name | Attribute | Attribute | RRO | ERO | Reference | | No | | Flags | Flags Resv | | | |