<?xml version="1.0" encoding="US-ASCII"?> encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="4"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?> [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>

<rfc category="std" xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-cdni-additional-footprint-types-11" updates='8008' ipr="trust200902"> number="9388" submissionType="IETF" category="std" consensus="true" updates="8008" obsoletes="" ipr="trust200902" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sortRefs="true" version="3">

  <!-- xml2rfc v2v3 conversion 3.16.0 -->
  <front>
    <title abbrev="CDNI Additional Footprint Types">
              Content Types">Content Delivery Network Interconnection (CDNI) Footprint Types: Country Subdivision Code and Footprint Union
        </title> Union</title>
    <seriesInfo name="RFC" value="9388"/>
    <author fullname="Nir B. Sopher" initials="N." surname="Sopher">
            <organization>
                Qwilt
            </organization>
      <organization>Qwilt</organization>
      <address>
        <postal>
                    <street>
                        6, Ha'harash
                    </street>
                    <city>
                        Hod HaSharon
                    </city>
                    <region>
                    </region>
                    <code>
                        4524079
                    </code>
                    <country>
                        Israel
                    </country>
          <street>6, Ha'harash</street>
          <city>Hod HaSharon</city>
          <region></region>
          <code>4524079</code>
          <country>Israel</country>
        </postal>
                <email>
                    nir@apache.org
                </email>
        <email>nir@apache.org</email>
      </address>
    </author>
    <author fullname="Sanjay Mishra" initials="S." surname="Mishra">
      <organization>Verizon</organization>
      <address>
        <postal>
          <street>13100 Columbia Pike</street>
          <city>Silver Spring</city>
          <region>MD</region>
          <code>20904</code>

          <country>USA</country>
          <country>United States of America</country>
        </postal>

        <phone></phone>
        <phone/>
        <email>sanjay.mishra@verizon.com</email>
      </address>
    </author>
    <date /> year="2023" month="July"/>
     <area>art</area>
     <workgroup>cdni</workgroup>

    <abstract>
      <t>
Open Caching architecture is a use case of Content Delivery Networks Network
Interconnection (CDNI) in which the commercial Content Delivery Network (CDN)
is the upstream CDN (uCDN) and the ISP caching layer serves as the downstream
CDN (dCDN). This document supplements the CDNI Metadata Footprint Types defined in RFC 8006.
                The Footprint Types defined in this document can be 8006 defines footprint types that are used for Footprint footprint
objects as part of the Metadata interface (MI) defined in RFC 8006 and (MI). The footprint types are also
used for the Footprint &amp; Capabilities Advertisement interface (FCI) as defined
in RFC 8008. By defining the This document defines two new footprint union Footprint Type, types. The first
footprint type defined is an ISO 3166-2 country subdivision code. Defining this document updates country
subdivision code improves granularity for delegation as compared to the ISO 3166-1 country
code footprint type defined in RFC 8008, allowing an 8006.  The ISO 3166-2 country subdivision
code is also added as a new entity domain type in the "ALTO Entity Domain
Types" registry defined in Section 7.4 of RFC 9241. The second footprint
type defines a footprint union to aggregate footprint objects. This allows for
additive semantic semantics over the narrowing semantics defined in Appendix B of
RFC 8008.
                This document also supplements 8008 and therefore updates RFC 9241 with relevant ALTO entity domain types. 8008. The defined Footprint Types two new footprint types are derived from based on the
requirements raised by Open Caching but are also applicable to CDNI use cases
in general.
      </t>
    </abstract>

        <note title="Requirements Language">
          <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
      "MAY", and "OPTIONAL" in this document are to be interpreted as
      described in BCP 14 <xref target="RFC2119"></xref>
              <xref target="RFC8174"></xref> when, and only when, they
      appear in all capitals, as shown here.</t>
        </note>

  </front>
  <middle>
    <section title="Introduction">
            <t>
                The numbered="true" toc="default">
      <name>Introduction</name>
      <t>The Streaming Video Technology Alliance <xref target="SVTA" format="default" />
      format="default"/> is a global association that works to solve streaming
      video challenges in an effort to improve end-user experience and
      adoption. The Open Caching Working Group <xref target="OCWG" format="default" />
      format="default"/> of the SVTA is focused on the delegation of video
      delivery requests from commercial Content Delivery Networks (CDNs) to a
      caching layer at the ISP's network.  Open Caching architecture is a
      specific use case of Content Delivery Networks Network Interconnection (CDNI)
      where the commercial CDN is the upstream CDN (uCDN) and the ISP caching
      layer is the downstream CDN (dCDN).  The <xref target="OC-RR"> Open target="OC-RR"
      format="default">"Open Caching Request Routing Specification </xref> Functional Specification"</xref>
      defines the Request Routing process and the interfaces that are required
      for its provisioning.  This document defines and registers CDNI
      Footprint and Capabilities objects <xref target="RFC8008" />
      format="default"/> that are required for Open Caching Request Routing.
      </t>
            <t>
                For
      <t>For consistency with other CDNI documents documents, this document follows the
      CDNI convention of uCDN (upstream CDN) using "uCDN" and dCDN (downstream CDN) "dCDN" to represent the commercial CDN and ISP
      caching
                layer layer, respectively.
      </t>
            <t>
                This
      <t>This document registers two CDNI Metadata Footprint Types (section 7.2 of
                <xref footprint types (<xref
      target="RFC8006" />) sectionFormat="of" section="7.2"/>) for the defined
      objects:
                <list style="symbols">
                    <t>
                        Subdivision Code Footprint Type
      </t>
      <ul spacing="normal">
        <li>Country subdivision code footprint type (e.g., for a dCDN advertising a
        footprint that is specific to a State state in the USA)
                    </t>
                    <t>
                        Union Footprint Type United States of
        America)</li>
        <li>Footprint union footprint type (for a dCDN advertising a footprint
        that consists of a group built from multiple Footprints Types, footprint types, e.g.,
        both IPv4 and IPv6 client subnets)
                    </t>
                </list>
            </t> subnets)</li>
      </ul>
      <section anchor="terminology" title="Terminology">
                <t>
                    The numbered="true" toc="default">
        <name>Terminology</name>
        <t>The following terms are used throughout this document:
                    <list style="symbols">
                        <t>
                            CDN - Content document:</t>
        <dl spacing="normal" newline="false">
          <dt>CDN:</dt>
	  <dd>Content Delivery Network
                        </t>
                    </list>
                </t>
                <t>
                    Additionally, Network</dd>
        </dl>
        <t>Additionally, this document reuses the terminology defined in <xref
        target="RFC6707" />, format="default"/>, <xref target="RFC7336" />,
        format="default"/>, <xref target="RFC8006" />, format="default"/>, and
        <xref target="RFC8008" />. format="default"/>.  Specifically, we use the
        following CDNI acronyms:
                    <list style="symbols">
                        <t>
                            uCDN, dCDN - Upstream abbreviations:
        </t>
        <dl spacing="normal" newline="false">
          <dt>uCDN:</dt>
	  <dd>upstream CDN and Downstream (see <xref target="RFC7336" format="default"/>)</dd>
	  <dt>dCDN:</dt>
	  <dd>downstream CDN respectively (see <xref target="RFC7336" />
                            )
                        </t>
                    </list>
	  format="default"/>)</dd>
	</dl>

      </section>
      <section anchor="requirements-lang" numbered="true" toc="default">
      <name>Requirements Language</name>
        <t>
    The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
    "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
    NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
    "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
    "<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are
    to be interpreted as described in BCP&nbsp;14 <xref target="RFC2119"/>
    <xref target="RFC8174"/> when, and only when, they appear in all capitals,
    as shown here.
        </t>
    </section>
    </section>
    <section anchor="cdni-metadata-additional-footprint-types" title="CDNI numbered="true" toc="default">
      <name>CDNI Metadata Additional Footprint Types">
            <t>
                Section 5 of <xref Types</name>
      <t><xref target="RFC8008" /> sectionFormat="of" section="5"/> describes the
      Footprint &amp; Capabilities Advertisement interface (FCI) Capability
      Advertisement Object, object, which includes an array of CDNI Footprint Objects. footprint
      objects. Each such object has a footprint-type footprint type and a footprint-value, footprint value, as
      described in section 4.2.2.2 of <xref target="RFC8006" />. sectionFormat="of"
      section="4.2.2.2"/>.  This document defines additional footprint types,
      beyond those mentioned in CDNI metadata <xref target="RFC8006" />.
      format="default"/>.
      </t>
      <section anchor="cdni-metadata-subdivisioncode-footprint-type" title="CDNI numbered="true" toc="default">
        <name>CDNI Metadata Subdivision Code "subdivisioncode" Footprint Type">
                <t>
                    Section 4.3.8 of <xref Type</name>
        <t><xref target="RFC8006" /> sectionFormat="of" section="4.3.8"/>
        specifies the "Country Code" "countrycode" footprint type for listing <xref target="ISO3166-1"/>
        target="ISO3166-1" format="default"/> alpha-2 codes. Using Footprint Objects footprint
        objects of this type, one can define an FCI Capability Advertisement Object
        object footprint constraint that matches a specific country.
                    Herein is defined  This
        document defines the subdivisioncode "subdivisioncode" simple data type, type as well as a
        footprint type type, allowing the dCDN to define constraints matching that match
        geographic areas with better granularity, specifically using the <xref target="ISO3166-2"/> Country Subdivision
        target="ISO3166-2" format="default"/> country subdivision codes.
        </t>
        <section anchor="cdni-metadata-subdivisioncode-data-type" title="CDNI numbered="true" toc="default">
          <name>CDNI Metadata Subdivision Code "subdivisioncode" Data Type">
                    <t>
                        The Type</name>
          <t>The "subdivisioncode" data type specified in <xref
          target="cdni-metadata-subdivisioncode-data-type-description" />,
          format="default"/> describes a country specific country-specific subdivision using an
          a code as defined in <xref target="ISO3166-2"/> code. target="ISO3166-2" format="default"/>.  The data type
          is added to the list of data types described in section 4.3 of <xref
          target="RFC8006" /> sectionFormat="of" section="4.3"/> that are used as
          properties of CDNI Metadata objects.
          </t>
          <section anchor="cdni-metadata-subdivisioncode-data-type-description" title="CDNI numbered="true" toc="default">
            <name>CDNI Metadata Subdivision Code "subdivisioncode" Data Type Description">
                        <t>
                        An Description</name>
            <t>An <xref target="ISO3166-2"/> target="ISO3166-2" format="default"/> code in
            lowercase. Each code consists of two parts separated by a hyphen.
            As per <xref target="ISO3166-2"/>, target="ISO3166-2" format="default"/>, the first part
            is the <xref target="ISO3166-1"/> target="ISO3166-1" format="default"/> code of the country,
            country and the second part is a string of up to three
            alphanumeric characters.
            </t>
                        <t>
                            <list style="empty">
                                <t>
                                    Type: String
                                </t>
                                <t>
                                    Example Subdivision Codes:
                                </t>
                                <t>"ca-on"</t>
                                <t>"us-ny"</t>
                            </list>
                        </t>
            <dl spacing="normal" newline="false">
              <dt>Type:</dt>
	      <dd>String</dd>
              <dt>Example country subdivision codes:</dt>
              <dd><ul>
		<li>"ca-on"</li>
		<li>"us-ny"</li>
              </ul></dd>
	    </dl>
          </section>
        </section>
        <section anchor="cdni-metadata-subdivisioncode-footprint-type-description" title="CDNI numbered="true" toc="default">
          <name>CDNI Metadata Subdivision Code "subdivisioncode" Footprint Type Description">
                    <t>
                        The
          Description</name>
          <t>The "subdivisioncode" simple data type specified in <xref
          target="cdni-metadata-subdivisioncode-data-type" />, format="default"/>
          is added to the data types listed as footprint types in section 4.2.2.2 of <xref
          target="RFC8006" />. sectionFormat="of" section="4.2.2.2"/>.
          </t>
                    <t>
                        Below
          <t><xref target="subdivision-code-footprint" format="default"/> is
          an example using a footprint object of type "subdivisioncode".  The Footprint Object
          footprint object in this example creates a constraint matching that matches
          clients in the
                        states state of either New Jersey and or New York, USA (ISO <xref target="ISO3166-2"/>
          target="ISO3166-2" format="default"/> codes "US-NJ" and "US-NY" "US-NY",
          respectively).
          </t>

          <figure title="Illustration anchor="subdivision-code-footprint">
            <name>Illustration of subdivision-code footprint advertisement">
                        <artwork>
<![CDATA[ Country Subdivision Code Footprint
            Advertisement</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
{
  "capabilities": [
    {
      "capability-type": <CDNI capability object type>,
      "capability-value": <CDNI capability object>,
      "footprints": [
          {
              "footprint-type": "subdivisioncode",
              "footprint-value": ["us-nj", "us-ny"]
          }
      ]
    }
  ]
}
]]>
                        </artwork>
]]></artwork>
          </figure>

        </section>
      </section>
      <section anchor="cdni-metadata-footprint-union-footprint-type" title="CDNI numbered="true" toc="default">
        <name>CDNI Metadata "footprintunion" Footprint Union Footprint Type">
                <t>
                    As Type</name>
        <t>As described in section 5 of <xref target="RFC8008" />, sectionFormat="of"
        section="5"/>, the FCI Capability Advertisement Object object includes an
        array of CDNI Footprint Objects. footprint objects.  Appendix B of <xref target="RFC8008" />
        format="default"/> specifies the semantics of a for Footprint Objects array as a multiple, additive, Advertisement
        such that multiple footprint constraints. constraints are additive.  This implies
        that the advertisement of different footprint types narrows the dCDN's
        candidacy cumulatively.
        </t>
                <t>
                    Sections 4.3.5
        <t>Sections <xref target="RFC8006" section="4.3.5"
        sectionFormat="bare"/> and 4.3.6 of <xref target="RFC8006" /> section="4.3.6"
        sectionFormat="bare"/> of <xref target="RFC8006"/> specify the "IPv4CIDR" "ipv4cidr" and "IPv6CIDR" the "ipv6cidr" footprint types, respectively, for listing IP
        unscoped address blocks. Using Footprint Objects footprint objects of these types, one
        can define FCI Capability Advertisement Object object footprint constraints
        that match either IPv4 or IPv6 clients. However, clients, but not both. This is due to the described "narrowing"
        semantic of the Footprint Objects array, as described in Appendix B of
        <xref target="RFC8008" />, format="default"/>, that prevents the usage of these
        objects together to create a footprint constraint that matches IPv4
        clients together with IPv6 clients.
        </t>
                <t>
                    Below

        <t><xref target="fig2" format="default"/> is an example for an attempt at creating attempting
        to create an object matching that matches IPv4 clients of subnet "192.0.2.0/24", "192.0.2.0/24"
        as well as IPv6 clients of subnet "2001:db8::/32".  Such a definition
        results in an empty list of clients, as the constraints are additives
        and a client address cannot be both IPv4 and IPv6.
        </t>

        <figure title="Example anchor="fig2">
          <name>Example of narrowing semantic illustrating advertisement Narrowing Semantic Illustrating Advertisement of a null footprint">
                    <artwork>
<![CDATA[
          Null Footprint</name>
          <artwork name="" type="" align="left" alt=""><![CDATA[
{
  "capabilities": [
    {
      "capability-type": <CDNI capability object type>,
      "capability-value": <CDNI capability object>,
      "footprints": [
          {
              "footprint-type": "ipv4cidr",
              "footprint-value": ["192.0.2.0/24"]
          },
          {
              "footprint-type": "ipv6cidr",
              "footprint-value": ["2001:db8::/32"]
          }
      ]
    }
  ]
}
]]>
                    </artwork>
]]></artwork>
        </figure>
                <t>
                    To

        <t>To overcome the described limitation and allow a list of footprint
        constraints that match both IPv4 and IPv6 client subnets, this
        document defines the "footprintunion" footprint type.  This footprint
        type allows the collection of multiple footprint-objects into a
        unified object.
                    Therefore  Therefore, it resolves the above limitation and can be
        particularly applicable to unify semantically related objects, objects: for
        example, an ipv4cidr IPv4 CIDR together with an ipv6cidr IPv6 CIDR or a countrycode country code
        together with a subdivisoncode. country subdivision code.
        </t>
                <t>
                    Note:
        <t>Note: to avoid implementation complexity, a "footprintunion" MUST NOT
        <bcp14>MUST NOT</bcp14> list any "footprintunion" as a value.  As a
        union of unions is simply a union, this syntactic restriction does not
        result with any semantic limitation.
        </t>
        <section anchor="cdni-metadata-footprint-union-data-type" title="CDNI numbered="true" toc="default">
          <name>CDNI Metadata Footprint Union "footprintunion" Data Type">
                    <t>
                        The Type</name>
          <t>The "footprintunion" data type is based on the Footprint Object footprint object
          already defined in
                        section 4.2.2.2 of <xref target="RFC8006" />. sectionFormat="of"
          section="4.2.2.2"/>. The footprint-value footprint value for a "footprintunion"
          object is an array of Footprint footprint objects, where the Footprint footprint objects MUST
          <bcp14>MUST</bcp14> be of any Footprint Type footprint type other than
          "footprintunion".
          </t>
        </section>
        <section anchor="cdni-metadata-footprint-union-footprint-type-description" title="CDNI numbered="true" toc="default">
          <name>CDNI Metadata FootprintUnion "footprintunion" Footprint Type Description">
                    <t>
                        The
          Description</name>
          <t>The "footprintunion" data type specified in <xref
          target="cdni-metadata-footprint-union-data-type" />, format="default"/>
          is added to the data types listed as footprint types in section 4.2.2.2 of <xref
          target="RFC8006" />. sectionFormat="of" section="4.2.2.2"/>.
          </t>
                    <t>
                        Below
          <t><xref target="fig3" format="default"/> is an example using a
          footprint object of type "footprintunion" union combining both IPv4 and IPv6 client subnets.
          </t>

          <figure title="Example anchor="fig3">
            <name>Example of an advertisement Advertisement of footprint union Footprint Union for multiple CIDR footprint types">
                        <artwork>
<![CDATA[ Multiple
            Classless Inter-Domain Routing (CIDR) Footprint Types</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
{
  "capabilities": [
    {
      "capability-type": <CDNI capability object type>,
      "capability-value": <CDNI capability object>,
      "footprints": [
        {
          "footprint-type": "footprintunion",
          "footprint-value": [
            {
              "footprint-type": "ipv4cidr",
              "footprint-value": ["192.0.2.0/24"]
            },
            {
              "footprint-type": "ipv6cidr",
              "footprint-value": ["2001:db8::/32"]
            }
          ]
        }
      ]
    }
  ]
}
]]>
                        </artwork>
]]></artwork>
          </figure>
                    <t>
                    The

          <t>The footprint union also enables composing a countrycode and subdivisioncode based of footprint objects.
                    In
          objects based on the example below country code and country subdivision code. In <xref
          target="fig4" format="default"/>, we create a constraint covering
          autonomous system 64496 within the US USA (ISO <xref target="ISO3166-1"/> alpha-2 code "US") "US" as described in <xref target="ISO3166-1"
          format="default"/>) and the Ontario province of
          Canada (ISO <xref target="ISO3166-2"/> code "CA-ON"). "CA-ON" as described in <xref target="ISO3166-2" format="default"/>).
          </t>

          <figure title="Example anchor="fig4">
            <name>Example of an advertisement Advertisement of footprint union Footprint Union for multiple geographical footprint types">
                        <artwork>
<![CDATA[ Multiple
            Geographical Footprint Types</name>
            <artwork name="" type="" align="left" alt=""><![CDATA[
{
  "capabilities": [
    {
      "capability-type": <CDNI capability object type>,
      "capability-value": <CDNI capability object>,
      "footprints": [
        {
          "footprint-type": "asn",
          "footprint-value": ["as64496"]
        },
        {
          "footprint-type": "footprintunion",
          "footprint-value": [
            {
              "footprint-type": "countrycode",
              "footprint-value": ["us"]
            },
            {
              "footprint-type": "subdivisioncode",
              "footprint-value": ["ca-on"]
            }
          ]
        }
      ]
    }
  ]
}
]]>
                        </artwork>
]]></artwork>
          </figure>

        </section>
      </section>
    </section>
    <section anchor="cdni-metadata-alto-property-map-service-entity" title="ALTO numbered="true" toc="default">
      <name>ALTO Property Map Service Entity">
                <t>
                   Section 6 of <xref Entity</name>
      <t><xref target="RFC9241" /> sectionFormat="of" section="6"/> describes how
      to represent footprint objects as entities in the ALTO property map. The
      approach is to represent the "footprint-type" footprint type as an entity domain type
      of the ALTO entity, entity and the footprint value as its domain-specific
      identifier. <xref target="RFC9241" /> format="default"/> further refers to
      the representation of footprint objects of types "asn" and
      "countrycode". Here Here, we extend this definition to the "subdivisioncode" footprint-type.
      footprint type.
      </t>
      <section anchor="cdni-metadata-subdivisioncode-alto-property-map-service-entity-domain" title="SUBDIVISIONCODE Domain">
                <t>
                    The numbered="true" toc="default">
        <name>SUBDIVISIONCODE Domain</name>

        <t>The SUBDIVISIONCODE domain associates property values that defines define codes for the names of the principal subdivisions.
        </t>
        <section anchor="cdni-metadata-subdivisioncode-alto-property-map-service-entity-domain-type" title="Entity numbered="true" toc="default">
          <name>Entity Domain Type"> Type</name>
          <t>
                    The entity domain type of the SUBDIVISIONCODE domain is "subdivisioncode" (in lowercase).
          </t>
        </section>
        <section anchor="cdni-metadata-subdivisioncode-alto-property-map-service-entity-domain-identifiers" title="Domain-Specific numbered="true" toc="default">
          <name>Domain-Specific Entity Identifiers">
                <t>
                    The Identifiers</name>
          <t>The entity identifier of an entity in a SUBDIVISIONCODE is
          encoded as an alpha-2 <xref target="ISO3166-1"/> Country Code, target="ISO3166-1" format="default"/>
          country code, followed by a separator and up to three alphanumeric
          characters.
          </t>
        </section>
        <section anchor="cdni-metadata-subdivisioncode-alto-property-map-service-entity-hierarchy-and-inheritance" title="Hierarchy numbered="true" toc="default">
          <name>Hierarchy and Inheritance"> Inheritance</name>
          <t> There is no hierarchy or inheritance for properties associated
          with country subdivision codes.
          </t>
        </section>
      </section>
    </section>
    <section anchor="IANA" title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <section anchor="IANA.cdni.metadata.footprint.types" title="CDNI numbered="true" toc="default">
        <name>CDNI Metadata Footprint Types">
                <t>
                    Section 7.2 of <xref Types</name>
        <t><xref target="RFC8006" /> sectionFormat="of" section="7.2"/> specifies
        the "CDNI Metadata Footprint Types" subregistry within the "Content
        Delivery Network Interconnection (CDNI) Parameters" registry.
        </t>
                <t>
                    This
        <t>This document requests the registration of the registers two additional Footprint Types footprint types in that subregistry as
        defined in Sections <xref
        target="cdni-metadata-subdivisioncode-footprint-type" />
        format="counter"/> and <xref
        target="cdni-metadata-footprint-union-footprint-type" />
                    :
        format="counter"/>:
        </t>
                <texttable>
                    <ttcol align="left">

        <table align="center">
	  <name>Additions to the CDNI Metadata Footprint Type
                    </ttcol>
                    <ttcol align="left">
                        Description
                    </ttcol>
                    <ttcol Types Subregistry</name>
          <thead>
            <tr>
              <th align="left">Footprint Type</th>
              <th align="left">Description</th>
              <th align="left">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">subdivisioncode</td>
              <td align="left">
                        Reference
                    </ttcol>
                    <c>
                        subdivisioncode
                    </c>
                    <c>
                        <xref target="ISO3166-2"/>
                ISO 3166-2 country
                subdivision code: alpha-2 country code, followed by a hyphen-minus,
                hyphen-minus and up to 3 characters from A-Z;0-9 as a code
                within the country.
                    </c>
                    <c>
                        RFCthis
                    </c>
                    <c>
                        footprintunion
                    </c>
                    <c>
                        A country</td>
              <td align="left">RFC 9388</td>
            </tr>
            <tr>
              <td align="left">footprintunion</td>
              <td align="left">A combination of other Footprint Objects
                    </c>
                    <c>
                        RFCthis
                    </c>
                </texttable>
                <t>
                    [RFC Editor: Please replace RFCthis with the published RFC
                    number for this document.]
                </t> footprint objects</td>
              <td align="left">RFC 9388</td>
            </tr>
          </tbody>
        </table>

      </section>
      <section anchor="IANA.ALTO.entity.domain.types" title="ALTO numbered="true" toc="default">
        <name>ALTO Entity Domain Types">
                <t>
                    Section 12.3 of <xref Types</name>
        <t><xref target="RFC9240" /> sectionFormat="of" section="12.3"/> creates
        the "ALTO Entity Domain Types" subregistry within the "Application-Layer Traffic Optimization (ALTO) Protocol" registry.
        </t>
                <t>
                    This
        <t>This document requests the registration of registers an additional ALTO
        Entity Domain Types: Type within that subregistry:
        </t>
                <texttable>
                    <ttcol align="left">
                        Identifier
                    </ttcol>
                     <ttcol align="left">
        <table align="center">
	  <name>Additions to the ALTO Entity Domain Types Subregistry</name>
          <thead>
            <tr>
              <th align="left">Identifier</th>
              <th align="left">Entity Identifier Encoding
                    </ttcol>
                     <ttcol align="left">
                       Hierarchy and Inheritance
                    </ttcol>
                    <ttcol align="left">
                        Media Encoding</th>
              <th align="left">Hierarchy and Inheritance</th>
              <th align="left">Media Type of Defining Resource
                    </ttcol>
                    <ttcol align="left">
                        Mapping Resource</th>
              <th align="left">Mapping to ALTO Address Type
                    </ttcol>
                    <c>
                        subdivisioncode
                    </c>
                    <c>
                        See RFCthis, Type</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td align="left">subdivisioncode</td>
              <td align="left">See RFC 9388, <xref target="cdni-metadata-subdivisioncode-alto-property-map-service-entity-domain-identifiers" />
                    </c>
                    <c>
                        None
                    </c>
                    <c>
                        None
                    </c>
                    <c>
                        false
                    </c>

                </texttable>
                <t>
                    [RFC Editor: Please replace RFCthis with the published RFC
                    number for this document.]
                </t>
              format="default"/>
              </td>
              <td align="left">None</td>
              <td align="left">None</td>
              <td align="left">false</td>
            </tr>
          </tbody>
        </table>

      </section>
    </section>
    <section anchor="Security" title="Security Considerations">
            <t>
                This numbered="true" toc="default">
      <name>Security Considerations</name>

      <t>This specification is in accordance with the CDNI Metadata and the CDNI Request Routing:
                Footprint "<xref target="RFC8006" format="title"/>" and Capabilities Semantics. "<xref target="RFC8008" format="title"/>". As such, it
      is subject to the security and confidentiality considerations as defined
      in Section 8 of <xref target="RFC8006" /> sectionFormat="of" section="8"/> and in Section 7 of <xref
      target="RFC8008" /> sectionFormat="of" section="7"/>, respectively.
      </t>
    </section>
        <section anchor="Acknowledgements" title="Acknowledgements">
            <t>
                The authors would like to express their gratitude to Ori Finkelman and
                Kevin J. Ma for their guidance and reviews throughout the development of this
                document. We would also like to thank all the Area Directors for their review and feedback in improving this document.
            </t>
        </section>
  </middle>
  <back>
        <references title="Normative References">
            <?rfc include="reference.RFC.2119"?>
            <?rfc include="reference.RFC.8006"?>
            <?rfc include="reference.RFC.8008"?>
            <?rfc include="reference.RFC.8174"?>
            <?rfc include="reference.RFC.9240"?>
            <?rfc include="reference.RFC.9241"?>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8006.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8008.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9240.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9241.xml"/>

        <reference anchor="ISO3166-1" target="https://www.iso.org/standard/72482.html">
          <front>
                <title>
                    Codes
            <title>Codes for the representation of names of countries and their subdivisions -- Part 1: Country code
                </title> code</title>
            <author>
              <organization>ISO</organization>
            </author>
            <date month="08" year="2020"/>
          </front>
          <seriesInfo name="ISO" value="3166-1:2020"/>
          <seriesInfo name="Edition" value="4"/>
        </reference>

        <reference anchor="ISO3166-2" target="https://www.iso.org/standard/72483.html">
          <front>
                <title>
                    Codes
            <title>Codes for the representation of names of countries and their subdivisions -- Part 2: Country subdivision code
                </title> code</title>
            <author>
              <organization>ISO</organization>
            </author>
            <date month="08" year="2020"/>
          </front>
          <seriesInfo name="ISO" value="3166-2:2020"/>
          <seriesInfo name="Edition" value="4"/>
        </reference>
      </references>

        <references title="Informative References">
            <?rfc include="reference.RFC.6707"?>
            <?rfc include="reference.RFC.7336"?>

      <references>
        <name>Informative References</name>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6707.xml"/>
        <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7336.xml"/>

        <reference anchor="SVTA" target="https://www.svta.org/">
          <front>
                    <title>
                        Streaming
            <title>Streaming Video Technology Alliance Home Page
                    </title>
                    <author />
                    <date /> Alliance</title>
            <author>
	      <organization>SVTA</organization>
	      </author>
            <date/>
          </front>
        </reference>

        <reference anchor="OCWG" target="https://opencaching.svta.org/">
          <front>
                    <title>
                        Open Caching Home Page
                    </title>
                    <author />
                    <date />
            <title>Open Caching</title>
            <author>
              <organization>SVTA</organization>
              </author>
            <date/>
          </front>
        </reference>

        <reference anchor="OC-RR" target="https://www.svta.org/product/open-cache-request-routing-functional-specification/">
          <front>
                    <title>
                        Open
            <title>Open Caching - Request Routing Functional Specification
                    </title>
            Specification</title>
            <author initials="O." surname="Finkelman" fullname="Ori Finkelman" role="editor">
                        <organization>
                            Qwilt
                        </organization>
              <organization>Qwilt</organization>
            </author>
            <author initials="J." surname="Hofmann" fullname="Jason Hofmann">
                        <organization>
                            Limelight Networks
                        </organization> initials="B." surname="Zurat" fullname="Bill Zurat">
              <organization>Disney Streaming Services</organization>
            </author>
            <author initials="D." surname="Sahar" fullname="Dan Sahar">
              <organization>Qwilt</organization>
            </author>
            <author initials="E." surname="Klein" fullname="Eric Klein">
                        <organization>
                            Disney Streaming Services
                        </organization>
              <organization>SiriusXM</organization>
            </author>
            <author initials="S." surname="Mishra" fullname="Sanjay Mishra">
                        <organization>
                            Verizon
                        </organization> initials="J." surname="Hofmann" fullname="Jason Hofmann">
              <organization>Limelight Networks</organization>
            </author>
            <author initials="K." initials="K.J." surname="Ma" fullname="Kevin J. Ma">
                        <organization>
                            Disney Streaming Services
                        </organization>
              <organization>Ericsson</organization>
            </author>
            <author initials="D." surname="Sahar" fullname="Dan Sahar">
                        <organization>
                            Qwilt
                        </organization> initials="M." surname="Stock" fullname="Matt Stock">
              <organization>Viasat</organization>
            </author>
            <author initials="B." surname="Zurat" fullname="Bill Zurat">
                        <organization>
                            Disney Streaming Services
                        </organization> initials="S." surname="Mishra" fullname="Sanjay Mishra">
              <organization>Verizon</organization>
	    </author>
            <author initials="Y." surname="Gressel" fullname="Yoav Gressel">
              <organization>Qwilt</organization>
	    </author>
            <date day="15" month="January" year="2021" /> year="2021"/>
          </front>
          <seriesInfo name="Version" value="2.0" /> value="2.0"/>
        </reference>

      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>The authors would like to express their gratitude to <contact
      fullname="Ori Finkelman"/> and <contact fullname="Kevin J. Ma"/> for
      their guidance and reviews throughout the development of this
      document. We would also like to thank all the Area Directors for their
      review and feedback in improving this document.
      </t>
    </section>

  </back>

</rfc>