--- 1/draft-ietf-mpls-residence-time-08.txt	2016-04-28 23:15:54.026920091 -0700
+++ 2/draft-ietf-mpls-residence-time-09.txt	2016-04-28 23:15:54.082921493 -0700
@@ -1,25 +1,25 @@
 
 MPLS Working Group                                             G. Mirsky
 Internet-Draft                                                S. Ruffini
 Intended status: Standards Track                                 E. Gray
 Expires: October 30, 2016                                       Ericsson
                                                                 J. Drake
                                                         Juniper Networks
                                                                S. Bryant
-                                                           Cisco Systems
+                                                             Independent
                                                            A. Vainshtein
                                                              ECI Telecom
                                                           April 28, 2016
 
                Residence Time Measurement in MPLS network
-                   draft-ietf-mpls-residence-time-08
+                   draft-ietf-mpls-residence-time-09
 
 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
@@ -555,22 +555,22 @@
    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
    outgoing Resv message before forwarding it upstream.  If the
    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
    forwarded upstream.  Otherwise, the I flag MUST be cleared (0).
 
    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
    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
-   the calculation of the residence time.  An ingress node MAY choose to
+   indicates that some RTM nodes along the LSP could be included in the
+   calculation of the residence time.  An ingress node MAY choose to
    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
    to policy processing (e.g., as may happen between providers) or RRO
    is limited due to size constraints .  Such changes affect the core
    assumption of the method to control processing of RTM packets.  RTM
    SHOULD NOT be used if it is not guaranteed that RRO contains complete
    information.
 
@@ -1170,17 +1170,17 @@
    Ericsson
 
    Email: eric.gray@ericsson.com
 
    John Drake
    Juniper Networks
 
    Email: jdrake@juniper.net
 
    Stewart Bryant
-   Cisco Systems
+   Independent
 
-   Email: stbryant@cisco.com
+   Email: stewart.bryant@gmail.com
    Alexander Vainshtein
    ECI Telecom
 
    Email: Alexander.Vainshtein@ecitele.com