--- 1/draft-ietf-ospf-ospfv3-segment-routing-extensions-22.txt	2019-01-09 02:13:08.415831949 -0800
+++ 2/draft-ietf-ospf-ospfv3-segment-routing-extensions-23.txt	2019-01-09 02:13:08.455832908 -0800
@@ -1,19 +1,19 @@
 
 Open Shortest Path First IGP                              P. Psenak, Ed.
 Internet-Draft                                       Cisco Systems, Inc.
 Intended status: Standards Track                         S. Previdi, Ed.
-Expires: July 6, 2019                                         Individual
-                                                         January 2, 2019
+Expires: July 13, 2019                                        Individual
+                                                         January 9, 2019
 
                  OSPFv3 Extensions for Segment Routing
-          draft-ietf-ospf-ospfv3-segment-routing-extensions-22
+          draft-ietf-ospf-ospfv3-segment-routing-extensions-23
 
 Abstract
 
    Segment Routing (SR) allows a flexible definition of end-to-end paths
    within IGP topologies by encoding paths as sequences of topological
    sub-paths, called "segments".  These segments are advertised by the
    link-state routing protocols (IS-IS and OSPF).
 
    This draft describes the OSPFv3 extensions required for Segment
    Routing with MPLS data plane.
@@ -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 July 6, 2019.
+   This Internet-Draft will expire on July 13, 2019.
 
 Copyright Notice
 
    Copyright (c) 2019 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
@@ -271,21 +271,23 @@
          For the address family IPv4 unicast, the prefix itself is
          encoded as a 32-bit value.  The default route is represented by
          a prefix of length 0.
 
          For the address family IPv6 unicast, the prefix, encoded as an
          even multiple of 32-bit words, padded with zeroed bits as
          necessary.  This encoding consumes ((PrefixLength + 31) / 32)
          32-bit words.
 
          Prefix encoding for other address families is beyond the scope
-         of this specification.
+         of this specification.  Prefix encoding for other address
+         families can be defined in the future standard-track IETF
+         specifications.
 
    The range represents the contiguous set of prefixes with the same
    prefix length as specified by the Prefix Length field.  The set
    starts with the prefix that is specified by the Address Prefix field.
    The number of prefixes in the range is equal to the Range size.
 
    If the OSPFv3 Extended Prefix Range TLVs advertising the exact same
    range appears in multiple LSAs of the same type, originated by the
    same OSPFv3 router, the LSA with the numerically smallest Instance ID
    MUST be used and subsequent instances of the OSPFv3 Extended Prefix