draft-ietf-cdni-media-type-06.txt   rfc7736.txt 
CDNI K. Ma Internet Engineering Task Force (IETF) K. Ma
Internet-Draft Ericsson Request for Comments: 7736 Ericsson
Intended status: Informational October 13, 2015 Category: Informational December 2015
Expires: April 15, 2016 ISSN: 2070-1721
CDNI Media Type Registration Content Delivery Network Interconnection (CDNI) Media Type Registration
draft-ietf-cdni-media-type-06
Abstract Abstract
This document defines the standard media type used by the Content This document defines the standard media type used by the Content
Delivery Network Interconnection (CDNI) protocol suite, including the Delivery Network Interconnection (CDNI) protocol suite, including the
registration procedure and recommended usage of the required payload- registration procedure and recommended usage of the required payload-
type parameter . type parameter.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This document is not an Internet Standards Track specification; it is
provisions of BCP 78 and BCP 79. published for informational purposes.
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 http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on April 15, 2016. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7736.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 2 1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 2 2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 3
2.2. CDNI Payload Type Parameter Registry . . . . . . . . . . 4 2.2. CDNI Payload-Types Parameters Registry . . . . . . . . . 5
3. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
3.1. Normative References . . . . . . . . . . . . . . . . . . 5 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Informative References . . . . . . . . . . . . . . . . . 6 4.1. Normative References . . . . . . . . . . . . . . . . . . 6
Appendix A. Acknowledgment . . . . . . . . . . . . . . . . . . . 6 4.2. Informative References . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction and Scope 1. Introduction and Scope
The Content Delivery Network Interconnection (CDNI) working group is The Content Delivery Network Interconnection (CDNI) working group is
developing a set of protocols to enable the interconnection of developing a set of protocols to enable the interconnection of
multiple content delivery networks (CDNs), as discussed in [RFC6770]. multiple content delivery networks (CDNs), as discussed in [RFC6770].
The CDNI protocol suite consists of multiple HTTP-based interfaces, The CDNI protocol suite consists of multiple HTTP-based interfaces,
many of which transfer various JSON (JavaScript Object Notation) many of which transfer various payloads encoded in JSON (JavaScript
encoded payloads [RFC7159]. The main interfaces (i.e., CDNI Control Object Notation) [RFC7159]. The main interfaces (i.e., CDNI Control
interface, CDNI Footprint & Capabilities Advertisement interface, interface, CDNI Footprint & Capabilities Advertisement interface,
CDNI Request Routing Redirection interface, CDNI Metadata interface, CDNI Request Routing Redirection interface, CDNI Metadata interface,
and CDNI Logging interface) are described in [RFC7336]. It is and CDNI Logging interface) are described in [RFC7336]. It is
desirable to be able to indicate the type of object carried in the desirable to be able to indicate the type of object carried in the
HTTP entity-body without having to register separate media types for HTTP entity-body without having to register separate media types for
each CDNI object. To accomplish this aim, this document defines a each CDNI object. To accomplish this aim, this document defines a
single new media type for CDNI that includes a required payload-type single new media type for CDNI that includes a required payload-type
parameter. A separate registry of CDNI payload-type parameters is parameter. A separate registry of CDNI payload-type parameters is
also defined. CDNI protocol specifications may register interface- also defined. CDNI protocol specifications may register interface-
specific payload-types, specifying the payload encoding and parsing specific payload types, specifying the payload encoding and parsing
semantics for that message (e.g., JSON serialization for a CDNI semantics for that message (e.g., JSON serialization for a CDNI
metadata object). The same payload-type parameter may also be used metadata object). The same payload-type parameter may also be used
as references for other purposes (e.g., referencing CDNI metadata as references for other purposes (e.g., referencing CDNI metadata
objects from CDNI capability advertisement objects). objects from CDNI capability advertisement objects).
2. IANA Considerations 2. IANA Considerations
This section contains the CDNI media type registration request for This section contains the CDNI media type registration as well as the
IANA, as well as the payload-type parameter registry definition for payload-type parameter registry definition for IANA.
IANA.
2.1. CDNI Media Type 2.1. CDNI Media Type
Type name: application Type name: application
Subtype name: cdni Subtype name: cdni
Required parameters: Required parameters:
ptype ptype
The required parameter "ptype" describes the type of CDNI The required parameter "ptype" describes the type of CDNI
message contained in the message payload, as registered in the message contained in the message payload, as registered in the
CDNI Payload Type Parameter Registry (Section 2.2) defined "Content Delivery Network Interconnection (CDNI) Parameters"
below. registry (Section 2.2) defined below.
Optional parameters: none Optional parameters: none
Encoding considerations: Encoding considerations:
The CDNI protocol suite includes interfaces with encoded messages The CDNI protocol suite includes interfaces with encoded messages
which may be 8bit or binary, as well as generic logging that may be 8bit or binary, as well as generic logging information
information which may be 7bit or binary. that may be 7bit or binary.
Security considerations: Security considerations:
CDNI interfaces that return encoded data may be (mis)interpreted CDNI interfaces that return encoded data may be (mis)interpreted
if parsed by non-CDNI or non-compliant CDNI implementations. In if parsed by non-CDNI or non-compliant CDNI implementations. In
addition, CDNI logging information is likely to transfer large addition, CDNI logging information is likely to transfer large
amounts of data which may overload unexpecting clients. The amounts of data that may overload unexpecting clients. The
individual CDNI interface specifications provide more detailed individual CDNI interface specifications provide more detailed
analysis of security and privacy concerns, and define the analysis of security and privacy concerns, and define the
requirements for authentication, authorization, confidentiality, requirements for authentication, authorization, confidentiality,
integrity, and privacy for each interface. integrity, and privacy for each interface.
The application/cdni media type is a generic media type to be used The application/cdni media type is a generic media type to be used
by multiple CDNI interfaces for transporting different types of by multiple CDNI interfaces for transporting different types of
control and logging information. Proper validation of message control and logging information. Proper validation of message
data requires parsing and understanding the ptype parameter and data requires parsing and understanding the ptype parameter and
the associated data encoding. Failure to properly validate the associated data encoding. Failure to properly validate
payloads may allow data extrusion under the auspices of the payloads may allow data extrusion under the auspices of the
application/cdni media type. application/cdni media type.
Interoperability considerations: Interoperability considerations:
The required ptype field is intended to fully describe the The required ptype field is intended to fully describe the
structure and parsing of CDNI messages, as enforced by the ptype structure and parsing of CDNI messages, as enforced by the ptype
registry designated expert. registry designated expert.
Published specification: RFCthis [RFC Editor: Please replace this Published specification: RFC 7736
with the published RFC number for this document.]
Applications that use this media type: Applications that use this media type:
CDNI is intended for use between interconnected CDNs for sharing CDNI is intended for use between interconnected CDNs for sharing
configuration and logging data, as well as for issuing content configuration and logging data, as well as for issuing content
management and redirection requests. management and redirection requests.
Fragment identifier considerations: N/A Fragment identifier considerations: N/A
Additional information: N/A Additional information: N/A
skipping to change at page 4, line 34 skipping to change at page 5, line 5
This media type is intended only for use in CDNI protocol message This media type is intended only for use in CDNI protocol message
exchanges. exchanges.
Author: IETF CDNI working group Author: IETF CDNI working group
Change controller: IETF CDNI working group Change controller: IETF CDNI working group
Provisional registration: no Provisional registration: no
2.2. CDNI Payload Type Parameter Registry 2.2. CDNI Payload-Types Parameters Registry
The IANA is requested to create a new "CDNI Payload Type" registry, IANA has created a new "CDNI Payload Types" subregistry within the
in a new category called "Content Delivery Networks Interconnection "Content Delivery Network Interconnection (CDNI) Parameters"
(CDNI) Parameters". The "CDNI Payload Type" namespace defines the registry. The "CDNI Payload Types" namespace defines the valid
valid values for the required "ptype" parameter of the "application/ values for the required "ptype" parameter of the "application/cdni"
cdni" media type. The CDNI Payload Type is an ASCII string value, media type. The CDNI payload type is an ASCII string value that
consisting of only visible (printing) characters, but excluding equal consists of only visible (printing) characters but excludes equal
signs (=), double quotes ("), and semicolons (;), and not exceeding signs (=), double quotes ("), and semicolons (;). It will not exceed
256 characters in length. 256 characters in length. The following Augmented Backus-Naur Form
(ABNF) definition of the CDNI payload type is provided for clarity
[RFC5234]
ptype = 1*256(ptype-char) ptype = 1*256(ptype-char)
ptype-char = %x21 / %x23-3A / %x3C / %x3E-7E ptype-char = %x21 / %x23-3A / %x3C / %x3E-7E
; Includes ALPHA, DIGIT, and other printables ; Includes ALPHA, DIGIT, and other printables
; Excludes equal signs (=), double quotes ("), semicolons (;) ; Excludes equal signs (=), double quotes ("), semicolons (;)
Additions to the CDNI Payload Type namespace will conform to the Additions to the "CDNI Payload Types" namespace will be made via
"Specification Required" policy as defined in [RFC5226]. The "Specification Required" as defined in [RFC5226]. The designated
designated expert will verify that new type definitions do not expert will verify that new type definitions do not duplicate
duplicate existing type definitions (in name or functionality), existing type definitions (in name or functionality), prevent
prevent gratuitous additions to the namespace, and prevent any gratuitous additions to the namespace, and prevent any additions to
additions to the namespace which would impair the interoperability of the namespace that would impair the interoperability of CDNI
CDNI implementations. The designated expert will review the implementations. The designated expert will review the
specification, even if it is a Standards Track RFC, to verify that it specification, even if it is a Standards Track RFC, to verify that it
contains the following information: contains the following information:
o The review will verify that the specification contains a o The review will verify that the specification contains a
reasonably defined purpose for the new payload type, where the reasonably defined purpose for the new payload type. A reasonably
purpose is related to an existing or proposed CDNI interface and defined purpose will relate to an existing or proposed CDNI
does not duplicate the functionality of any existing CDNI protocol interface and will not duplicate the functionality of any existing
feature without specifying a rational reason (e.g., updating an CDNI protocol feature without specifying a rational reason (e.g.,
obsolete feature), a method for detecting and handling conflicts updating an obsolete feature), a method for detecting and handling
(e.g., a versioning system with prioritization matrix), and a conflicts (e.g., a versioning system with prioritization matrix),
suggested migration path (e.g., deprecation of the overlapped and a suggested migration path (e.g., deprecation of the
feature, or justification for co-existence). overlapped feature, or justification for co-existence).
o The review will verify that the specification contains information o The review will verify that the specification contains information
as to which CDNI interface the new payload type pertains/affects. as to which CDNI interface the new payload type pertains or
The payload type may be applicable to multiple CDNI interfaces, affects. The payload type may be applicable to multiple CDNI
but the justification for the new payload type will include a interfaces, but the justification for the new payload type will
reasonable relationship to at least one standards track CDNI include a reasonable relationship to at least one Standards Track
interface. CDNI interface.
o The review will verify that the specification contains sufficient o The review will verify that the specification contains sufficient
detail about the data encoding (e.g., JSON serialization for new detail about the data encoding (e.g., JSON serialization for new
CDNI metadata or capability advertisement objects, or ABNF and CDNI metadata or capability advertisement objects, or ABNF and
description for new CDNI logging file formats) to allow senders description for new CDNI logging file formats) to allow senders
and receivers of the new payload type to implement compliant and and receivers of the new payload type to implement compliant and
interoperable payload parsers. interoperable payload parsers.
The registry contains the Payload Type, and the specification The registry contains the payload type and the specification
describing the Payload Type. The registry will initially be describing the payload type. The registry will initially be
unpopulated. unpopulated.
+--------------+---------------+ +--------------+---------------+
| Payload Type | Specification | | Payload Type | Specification |
+--------------+---------------+ +--------------+---------------+
+--------------+---------------+ +--------------+---------------+
3. References 3. Security Considerations
3.1. Normative References See the portion of Section 2.1 labeled "Security considerations".
4. References
4.1. Normative References
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
3.2. Informative References [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
4.2. Informative References
[RFC6770] Bertrand, G., Ed., Stephan, E., Burbridge, T., Eardley, [RFC6770] Bertrand, G., Ed., Stephan, E., Burbridge, T., Eardley,
P., Ma, K., and G. Watson, "Use Cases for Content Delivery P., Ma, K., and G. Watson, "Use Cases for Content Delivery
Network Interconnection", RFC 6770, DOI 10.17487/RFC6770, Network Interconnection", RFC 6770, DOI 10.17487/RFC6770,
November 2012, <http://www.rfc-editor.org/info/rfc6770>. November 2012, <http://www.rfc-editor.org/info/rfc6770>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
2014, <http://www.rfc-editor.org/info/rfc7159>. 2014, <http://www.rfc-editor.org/info/rfc7159>.
[RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed., [RFC7336] Peterson, L., Davie, B., and R. van Brandenburg, Ed.,
"Framework for Content Distribution Network "Framework for Content Distribution Network
Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336, Interconnection (CDNI)", RFC 7336, DOI 10.17487/RFC7336,
August 2014, <http://www.rfc-editor.org/info/rfc7336>. August 2014, <http://www.rfc-editor.org/info/rfc7336>.
Appendix A. Acknowledgment Acknowledgments
This document is the culmination of the efforts of many in the CDNI This document is the culmination of the efforts of many in the CDNI
working group, including (in alphabetical order): Francois Le working group, including (in alphabetical order): Francois Le
Faucheur, Daryl Malas, Rob Murray, Ben Niven-Jenkins, Iuniana Faucheur, Daryl Malas, Rob Murray, Ben Niven-Jenkins, Iuniana
Oprescu, Jon Peterson, and Jan Seedorf. Oprescu, Jon Peterson, and Jan Seedorf.
Author's Address Author's Address
Kevin J. Ma Kevin J. Ma
Ericsson Ericsson
43 Nagog Park 43 Nagog Park
Acton, MA 01720 Acton, MA 01720
USA United States
Phone: +1 978-844-5100 Phone: +1 978-844-5100
Email: kevin.j.ma@ericsson.com Email: kevin.j.ma@ericsson.com
 End of changes. 25 change blocks. 
76 lines changed or deleted 84 lines changed or added

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