--- 1/draft-ietf-ospf-te-link-attr-reuse-05.txt	2018-11-09 04:13:36.863324076 -0800
+++ 2/draft-ietf-ospf-te-link-attr-reuse-06.txt	2018-11-09 04:13:36.903325018 -0800
@@ -1,28 +1,28 @@
 
 LSR Working Group                                         P. Psenak, Ed.
 Internet-Draft                                       Cisco Systems, Inc.
 Intended status: Standards Track                               A. Lindem
-Expires: April 20, 2019                                      L. Ginsberg
+Expires: May 13, 2019                                        L. Ginsberg
                                                            Cisco Systems
                                                            W. Henderickx
                                                                    Nokia
                                                              J. Tantsura
                                                           Nuage Networks
                                                               H. Gredler
                                                             RtBrick Inc.
                                                                 J. Drake
                                                         Juniper Networks
-                                                        October 17, 2018
+                                                        November 9, 2018
 
            OSPF Link Traffic Engineering (TE) Attribute Reuse
-               draft-ietf-ospf-te-link-attr-reuse-05.txt
+               draft-ietf-ospf-te-link-attr-reuse-06.txt
 
 Abstract
 
    Various link attributes have been defined in OSPF in the context of
    the MPLS Traffic Engineering (TE) and GMPLS.  Many of these link
    attributes can be used for applications other than MPLS Traffic
    Engineering or GMPLS.  This document defines how to distribute such
    attributes in OSPFv2 and OSPFv3 for applications other than MPLS
    Traffic Engineering or GMPLS.
 
@@ -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 https://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 April 20, 2019.
+   This Internet-Draft will expire on May 13, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -82,22 +82,22 @@
    4.  Reused TE link attributes . . . . . . . . . . . . . . . . . .   6
      4.1.  Shared Risk Link Group (SRLG) . . . . . . . . . . . . . .   6
      4.2.  Extended Metrics  . . . . . . . . . . . . . . . . . . . .   7
      4.3.  Traffic Engineering Metric  . . . . . . . . . . . . . . .   8
      4.4.  Administrative Group  . . . . . . . . . . . . . . . . . .   8
    5.  Advertisement of Application Specific Values  . . . . . . . .   8
    6.  Maximum Link Bandwidth  . . . . . . . . . . . . . . . . . . .  11
    7.  Local Interface IPv6 Address Sub-TLV  . . . . . . . . . . . .  12
    8.  Remote Interface IPv6 Address Sub-TLV . . . . . . . . . . . .  12
    9.  Deployment Considerations . . . . . . . . . . . . . . . . . .  12
-   10. Attribute Advertisements and Enablement . . . . . . . . . . .  12
-   11. Backward Compatibility  . . . . . . . . . . . . . . . . . . .  13
+   10. Attribute Advertisements and Enablement . . . . . . . . . . .  13
+   11. Backward Compatibility  . . . . . . . . . . . . . . . . . . .  14
    12. Security Considerations . . . . . . . . . . . . . . . . . . .  14
    13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
      13.1.  OSPFv2 . . . . . . . . . . . . . . . . . . . . . . . . .  14
      13.2.  OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . .  15
    14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  16
    15. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
      15.1.  Normative References . . . . . . . . . . . . . . . . . .  16
      15.2.  Informative References . . . . . . . . . . . . . . . . .  17
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18
 
@@ -400,27 +400,29 @@
    |                      Link Attribute sub-sub-TLVs              |
    +-                                                             -+
    |                            ...                                |
 
    where:
 
       Type: TBD21 (OSPFv2), TBD22 (OSPFv3)
 
       Length: variable
 
-      SABML: Standard Application Bit-Mask Length.  If the Standard
-      Application Bit-Mask is not present, the Standard Application Bit-
-      Mask Length MUST be set to 0.
+      SABML: Standard Application Bit-Mask Length.  It MUST be a
+      multiple of 4 bytes.  If the Standard Application Bit-Mask is not
+      present, the Standard Application Bit-Mask Length MUST be set to
+      0.
 
-      UDABML: User Defined Application Bit-Mask Length.  If the User
-      Defined Application Bit-Mask is not present, the User Defined
-      Application Bit-Mask Length MUST be set to 0.
+      UDABML: User Defined Application Bit-Mask Length.  It MUST be a
+      multiple of 4 bytes.  If the User Defined Application Bit-Mask is
+      not present, the User Defined Application Bit-Mask Length MUST be
+      set to 0.
 
       Standard Application Bit-Mask: Optional set of bits, where each
       bit represents a single standard application.  Bits are defined in
       [I-D.ietf-isis-te-app], which also request a new IANA "Link
       Attribute Applications" registry under "Interior Gateway Protocol
       (IGP) Parameters" for them.  The bits are repeated here for
       informational purpose:
 
          Bit-0: RSVP Traffic Engineering