--- 1/draft-ietf-cdni-request-routing-extensions-04.txt	2019-08-09 01:13:13.962596350 -0700
+++ 2/draft-ietf-cdni-request-routing-extensions-05.txt	2019-08-09 01:13:13.986596957 -0700
@@ -1,19 +1,19 @@
 
 Network Working Group                                       O. Finkelman
 Internet-Draft                                                     Qwilt
 Intended status: Standards Track                               S. Mishra
-Expires: January 29, 2020                                        Verizon
-                                                           July 28, 2019
+Expires: February 10, 2020                                       Verizon
+                                                          August 9, 2019
 
                     CDNI Request Routing Extensions
-             draft-ietf-cdni-request-routing-extensions-04
+             draft-ietf-cdni-request-routing-extensions-05
 
 Abstract
 
    The Open Caching working group of the Streaming Video Alliance is
    focused on the delegation of video delivery requests from commercial
    CDNs to a caching layer at the ISP.  In that aspect, Open Caching is
    a specific use case of CDNI, where the commercial CDN is the upstream
    CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN).
    The extensions specified in this document to the CDNI Metadata and
    FCI interfaces are derived from requirements raised by Open Caching
@@ -33,21 +33,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 January 29, 2020.
+   This Internet-Draft will expire on February 10, 2020.
 
 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
@@ -208,24 +208,24 @@
    {
      "capabilities": [
        {
          "capability-type": "FCI.RedirectTarget",
          "capability-value": {
              "redirecting-hosts": [
                 "a.service123.ucdn.example.com",
                 "b.service123.ucdn.example.com"
              ],
              "dns-target": {
-                "host": "service123.ucdn.example.dcdn.com"
+                "host": "service123.ucdn.dcdn.example.com"
              },
              "http-target": {
-                 "host": "us-east1.dcdn.com",
+                 "host": "us-east1.dcdn.example.com",
                  "path-prefix": "/cache/1/",
                  "include-redirecting-host": true
              }
          },
          "footprints": [
              <Footprint objects>
          ]
        }
      ]
    }
@@ -242,34 +242,34 @@
 
          Type: Endpoint object as defined in section 4.3.3 of [RFC8006]
          with the limitation that it SHOULD NOT include a port number
          and, in case a port number is present, the uCDN MUST ignore it.
 
          Mandatory-to-Specify: Yes.
 
    The following is an example of DnsTarget object:
 
     {
-       "host": "service123.ucdn.example.dcdn.com"
+       "host": "service123.ucdn.dcdn.example.com"
     }
 
    The following is an example of a DNS query for uCDN address
    "a.service123.ucdn.example.com" and the corresponding CNAME
    redirection response:
 
     Query:
     a.service123.ucdn.example.com:
     type A, class IN
 
     Response:
     a.service123.ucdn.example.com:
-    type CNAME, class IN, cname service123.ucdn.example.dcdn.com
+    type CNAME, class IN, cname service123.ucdn.dcdn.example.com
 
 2.3.  HttpTarget
 
    The HttpTarget object gives the necessary information to construct
    the target Location URI for HTTP redirection.
 
       Property: host
 
          Description: Hostname or IP address and an optional port, i.e.,
          the host and port of the authority component of the URI as
@@ -305,37 +305,37 @@
          URL.
 
          Type: Boolean.
 
          Mandatory-to-Specify: No.  Default value is False.
 
    Example of HttpTarget object with a path-prefix and include-
    redirecting-host:
 
    {
-      "host": "us-east1.dcdn.com",
+      "host": "us-east1.dcdn.example.com",
       "path-prefix": "/cache/1/",
       "include-redirecting-host": true
    }
 
    Example of a HTTP request for content at uCDN host
    "a.service123.ucdn.example.com" and the corresponding HTTP response
    with Location header used for redirecting the client to the dCDN
    using the the http-target in the above example:
 
     Request:
     GET /vod/1/movie.mp4 HTTP/1.1
     Host: a.service123.ucdn.example.com
 
     Response:
     HTTP/1.1 302 Found
-    Location: http://us-east1.dcdn.com/cache/1/
+    Location: http://us-east1.dcdn.example.com/cache/1/
     a.service123.ucdn.example.com/vod/1/movie.mp4
 
 3.  Fallback Target Address Metadata
 
    Open Caching requires that the uCDN provide a fallback target server
    to the dCDN, to be used in cases where the dCDN cannot properly
    handle the request.  To avoid redirect loops, the fallback target
    server's address at the uCDN MUST be differnet from the original uCDN
    address from which the client was redirected to the dCDN.  The uCDN
    MUST avoid further redirection when receiving the client request at