draft-ietf-cdni-metadata-05.txt   draft-ietf-cdni-metadata-06.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Intended status: Standards Track G. Watson Intended status: Standards Track G. Watson
Expires: August 18, 2014 Velocix (Alcatel-Lucent) Expires: August 18, 2014 Velocix (Alcatel-Lucent)
M. Caulfield M. Caulfield
K. Leung K. Leung
Cisco Systems Cisco Systems
K. Ma K. Ma
Azuki Systems, Inc. Azuki Systems, Inc.
February 14, 2014 February 14, 2014
CDN Interconnect Metadata CDN Interconnect Metadata
draft-ietf-cdni-metadata-05 draft-ietf-cdni-metadata-06
Abstract Abstract
The CDNI Metadata Interface enables interconnected CDNs to exchange The CDNI Metadata Interface enables interconnected CDNs to exchange
content distribution metadata in order to enable content acquisition content distribution metadata in order to enable content acquisition
and delivery. The CDNI metadata associated with a piece of content and delivery. The CDNI metadata associated with a piece of content
provides a downstream CDN with sufficient information for the provides a downstream CDN with sufficient information for the
downstream CDN to service content requests on behalf of an upstream downstream CDN to service content requests on behalf of an upstream
CDN. This document describes both the core set of CDNI metadata and CDN. This document describes both the core set of CDNI metadata and
the protocol for exchanging that metadata. the protocol for exchanging that metadata.
skipping to change at page 35, line 21 skipping to change at page 35, line 21
cdni" MIME Media Type under the IANA MIME Media Type registry (http:/ cdni" MIME Media Type under the IANA MIME Media Type registry (http:/
/www.iana.org/assignments/media-types/index.html). /www.iana.org/assignments/media-types/index.html).
7.1. GenericMetadata Type Registry 7.1. GenericMetadata Type Registry
CDNI Metadata is distributed as a list of GenericMetadata objects CDNI Metadata is distributed as a list of GenericMetadata objects
which specify a type field and a type-specific value field, as which specify a type field and a type-specific value field, as
described in Section 4.1.7. In order to prevent namespace collisions described in Section 4.1.7. In order to prevent namespace collisions
for GenericMetadata object types a new IANA registry is requested for for GenericMetadata object types a new IANA registry is requested for
"CDNI GenericMetadata Types" namespace. The namespace shall be split "CDNI GenericMetadata Types" namespace. The namespace shall be split
into two partitions: standard and vendor defined. into two partitions: standard and optional.
The standard namespace partition is intended to contain mandatory to The standard namespace partition is intended to contain mandatory to
implement capabilities and MUST conform to the "IETF Review" policy implement capabilities and conforms to the "IETF Review" policy as
as defined in [RFC5226]. The registry SHALL contain the generic defined in [RFC5226]. The registry contains the generic metadata
metadata type name, the RFC number of the specification defining the type name, the RFC number of the specification defining the metadata
metadata type, the version number of the GenericMetadata set to which type, the version number of the GenericMetadata set to which the
the standard capability applies, and boolean values indicating standard capability applies, and boolean values indicating whether or
whether or not the new type is considered mandatory-to-enforce or not the new type is considered mandatory-to-enforce or safe-to-
safe-to-redistribute (as defined in Section 4.1.7). redistribute (as defined in Section 4.1.7).
The following table defines the initial values for the standard The following table defines the initial values for the standard
partition: partition:
+----------------+---------------+---------+------+------+ +----------------+---------------+---------+------+------+
| Type name | Specification | Version | MTE | STR | | Type name | Specification | Version | MTE | STR |
+----------------+---------------+---------+------+------+ +----------------+---------------+---------+------+------+
| SourceMetadata | RFCthis | 1 | true | true | | SourceMetadata | RFCthis | 1 | true | true |
| LocationACL | RFCthis | 1 | true | true | | LocationACL | RFCthis | 1 | true | true |
| TimeWindowACL | RFCthis | 1 | true | true | | TimeWindowACL | RFCthis | 1 | true | true |
skipping to change at page 36, line 5 skipping to change at page 36, line 5
| Auth | RFCthis | 1 | true | true | | Auth | RFCthis | 1 | true | true |
| Cache | RFCthis | 1 | true | true | | Cache | RFCthis | 1 | true | true |
| Grouping | RFCthis | 1 | true | true | | Grouping | RFCthis | 1 | true | true |
+----------------+---------------+---------+------+------+ +----------------+---------------+---------+------+------+
The initial MI version number is set to 1. All of the initial The initial MI version number is set to 1. All of the initial
GenericMetadata types are considered mandatory to implement for GenericMetadata types are considered mandatory to implement for
version 1. The version field should be incremented when new version 1. The version field should be incremented when new
GenericMetadata type sets are added to the registry. GenericMetadata type sets are added to the registry.
The "vendor defined" namespace partition SHOULD conform to the The "optional" namespace partition conforms to the "Expert Review"
"Expert Review" policy as defined in [RFC5226]. The expert review is policy as defined in [RFC5226]. The expert review is intended to
intended to prevent namespace hoarding and to prevent the definition prevent namespace hoarding and to prevent the definition of redundant
of redundant GenericMetadata types. Vendors defining new GenericMetadata types. Vendors defining new GenericMetadata types
GenericMetadata types which conflict with existing GenericMetadata which conflict with existing GenericMetadata types follow the
types SHOULD follow the guidelines for the "Specification Required" guidelines for the "Specification Required" policy as defined in
policy as defined in [RFC5226]. The Version field in the registry [RFC5226]. The Version field in the registry is set to "-1"
MUST be set to "-1" (negative one) for non-standard GenericMetadata (negative one) for non-standard GenericMetadata types.
types.
As with the initial GenericMetadata types defined in Section 4.2, As with the initial GenericMetadata types defined in Section 4.2,
future GenericMetadata type registrations SHOULD specify the future GenericMetadata type registrations will specify the
information necessary for constructing and decoding the information necessary for constructing and decoding the
GenericMetadata object. This information SHOULD include the list of GenericMetadata object. This information includes the list of
properties contained within the GenericMetadata object, and for each properties contained within the GenericMetadata object, and for each
property, the specification should include a description, a type, and property, the specification should include a description, a type, and
whether or not the given property is mandatory to specify. whether or not the given property is mandatory to specify.
Any document which defines a new GenericMetadata type MUST: Any document which defines a new GenericMetadata type MUST:
1. Allocate a new type in the GenericMetadata Type Registry 1. Allocate a new type in the GenericMetadata Type Registry
(Section 7). (Section 7).
2. Define the set of properties associated with the new type. 2. Define the set of properties associated with the new type.
skipping to change at page 36, line 51 skipping to change at page 36, line 50
Some of the initial standard GenericMetadata objects contain Some of the initial standard GenericMetadata objects contain
enumerated types which require registration (i.e., LocationACL enumerated types which require registration (i.e., LocationACL
footprint types, ProtocolACL protocols, and Auth protocols). The footprint types, ProtocolACL protocols, and Auth protocols). The
following sections define the initial values for these following sections define the initial values for these
GenericMetadata type sub-registries. GenericMetadata type sub-registries.
7.1.1.1. Footprint Sub-Registry 7.1.1.1. Footprint Sub-Registry
The "CDNI Metadata Footprint Types" namespace defines the valid The "CDNI Metadata Footprint Types" namespace defines the valid
Footprint object type values used by the Footprint object in Footprint object type values used by the Footprint object in
Section 4.2.2.2. Additions to the Footprint type namespace MUST Section 4.2.2.2. Additions to the Footprint type namespace conform
conform to the "Expert Review" policy as defined in [RFC5226]. The to the "Expert Review" policy as defined in [RFC5226]. The expert
expert review should verify that new type definitions do not review should verify that new type definitions do not duplicate
duplicate existing type definitions and prevent gratuitous additions existing type definitions and prevent gratuitous additions to the
to the namespace. namespace.
The following table defines the initial Footprint type values: The following table defines the initial Footprint type values:
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| Type name | Description | Specification | | Type name | Description | Specification |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| IPv4 | Single IPv4 address | RFCthis | | IPv4 | Single IPv4 address | RFCthis |
| IPv6 | Single IPv6 address | RFCthis | | IPv6 | Single IPv6 address | RFCthis |
| IPv4Range | List of contiguous IPv4 addresses | RFCthis | | IPv4Range | List of contiguous IPv4 addresses | RFCthis |
| | denoted by a start address and an | | | | denoted by a start address and an | |
skipping to change at page 37, line 41 skipping to change at page 37, line 40
| ASN | Autonomous System (AS) Number | RFCthis | | ASN | Autonomous System (AS) Number | RFCthis |
| CountryCode | ISO 3166-1 alpha-2 code | RFCthis | | CountryCode | ISO 3166-1 alpha-2 code | RFCthis |
| DVDRegion | DVD Region code (i.e., integer in | RFCthis | | DVDRegion | DVD Region code (i.e., integer in | RFCthis |
| | the range 0-6). | | | | the range 0-6). | |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
7.1.1.2. Protocol Sub-Registry 7.1.1.2. Protocol Sub-Registry
The "CDNI Metadata Protocols" namespace defines the valid Protocol The "CDNI Metadata Protocols" namespace defines the valid Protocol
object values in Section 4.3.2, used by the SourceMetadata and object values in Section 4.3.2, used by the SourceMetadata and
ProtocolACL objects. Additions to the Protocol namespace MUST ProtocolACL objects. Additions to the Protocol namespace conform to
conform to the "Expert Review" policy as defined in [RFC5226]. The the "Expert Review" policy as defined in [RFC5226]. The expert
expert review should verify that new type definitions do not review should verify that new type definitions do not duplicate
duplicate existing type definitions and prevent gratuitous additions existing type definitions and prevent gratuitous additions to the
to the namespace. namespace.
The following table defines the initial Protocol values: The following table defines the initial Protocol values:
+----------+----------------+---------------------------------------+ +----------+----------------+---------------------------------------+
| Protocol | Description | Specification | | Protocol | Description | Specification |
+----------+----------------+---------------------------------------+ +----------+----------------+---------------------------------------+
| HTTP | Hypertext | RFC2616 | | HTTP | Hypertext | RFC2616 |
| | Transfer | | | | Transfer | |
| | Protocol -- | | | | Protocol -- | |
| | HTTP/1.1 | | | | HTTP/1.1 | |
skipping to change at page 38, line 35 skipping to change at page 38, line 35
| fasp | Aspera fast, | N/A | | fasp | Aspera fast, | N/A |
| | adaptive, | | | | adaptive, | |
| | secure | | | | secure | |
| | protocol | | | | protocol | |
+----------+----------------+---------------------------------------+ +----------+----------------+---------------------------------------+
7.1.1.3. Authentication Sub-Registry 7.1.1.3. Authentication Sub-Registry
The "CDNI Metadata Auth" namespace defines the valid Auth object The "CDNI Metadata Auth" namespace defines the valid Auth object
types used by the Auth object in Section 4.2.6. Additions to the types used by the Auth object in Section 4.2.6. Additions to the
Auth namespace MUST conform to the "Expert Review" policy as defined Auth namespace conform to the "Expert Review" policy as defined in
in [RFC5226]. The expert review should verify that new type [RFC5226]. The expert review should verify that new type definitions
definitions do not duplicate existing type definitions and prevent do not duplicate existing type definitions and prevent gratuitous
gratuitous additions to the namespace. additions to the namespace.
The following table defines the initial Auth type values: The following table defines the initial Auth type values:
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| Type name | Description | Specification | | Type name | Description | Specification |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
| credentials | Simple username and password | RFCthis | | credentials | Simple username and password | RFCthis |
| | authentication as defined by | | | | authentication as defined by | |
| | Section 4.2.6.1. | | | | Section 4.2.6.1. | |
+-------------+-------------------------------------+---------------+ +-------------+-------------------------------------+---------------+
 End of changes. 9 change blocks. 
34 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/