draft-ietf-cdni-media-type-00.txt   draft-ietf-cdni-media-type-01.txt 
CDNI K. Ma CDNI K. Ma
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational August 17, 2015 Intended status: Informational September 29, 2015
Expires: February 18, 2016 Expires: April 1, 2016
CDNI Media Type Registration CDNI Media Type Registration
draft-ietf-cdni-media-type-00 draft-ietf-cdni-media-type-01
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 .
Requirements Language Requirements Language
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 18, 2016. This Internet-Draft will expire on April 1, 2016.
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
skipping to change at page 2, line 23 skipping to change at page 2, line 23
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 3 2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 3
2.2. CDNI Payload Type Parameter Registry . . . . . . . . . . 4 2.2. CDNI Payload Type Parameter Registry . . . . . . . . . . 4
3. Normative References . . . . . . . . . . . . . . . . . . . . 5 3. Normative References . . . . . . . . . . . . . . . . . . . . 5
Appendix A. Acknowledgment . . . . . . . . . . . . . . . . . . . 6 Appendix A. Acknowledgment . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction and Scope 1. Introduction and Scope
The CDNI working group is developing a set of protocols to enable the The CDNI working group is developing a set of protocols to enable the
interconnection of multiple CDNs to a CDN federation, as discussed in interconnection of multiple CDNs, as discussed in [RFC6770]. The
[RFC6770]. The CDNI protocol suite consists of multiple HTTP-based CDNI protocol suite consists of multiple HTTP-based interfaces, many
interfaces, many of which transfer various json encoded payloads. of which transfer various JSON encoded payloads [RFC7159]. The main
The main interfaces (i.e., CDNI Control interface, CDNI Footprint & interfaces (i.e., CDNI Control interface, CDNI Footprint &
Capabilities Advertisement interface, CDNI Request Routing Capabilities Advertisement interface, CDNI Request Routing
Redirection interface, CDNI Metadata interface, and CDNI Logging Redirection interface, CDNI Metadata interface, and CDNI Logging
interface) are described in [RFC7336]. It is desirable to be able to interface) are described in [RFC7336]. It is desirable to be able to
indicate the type of object carried in the HTTP entity-body without indicate the type of object carried in the HTTP entity-body without
having to register separate media types for each CDNI object. To having to register separate media types for each CDNI object. To
accomplish this aims, this document defines a single new media type accomplish this aims, this document defines a single new media type
for CDNI that includes a required payload-type parameter. A separate for CDNI that includes a required payload-type parameter. A separate
registry of CDNI payload-type parameter values is also defined. CDNI registry of CDNI payload-type parameters is also defined. CDNI
protocol specifications may register interface-specific payload- protocol specifications may register interface-specific payload-
types, specifying the payload encoding and parsing semantics for that types, specifying the payload encoding and parsing semantics for that
message (e.g., json serialization for a CDNI metadata object). The message (e.g., JSON serialization for a CDNI metadata object). The
same payload-type parameter names may also be used as references for same payload-type parameter may also be used as references for other
other purposes (e.g., referencing CDNI metadata objects from CDNI purposes (e.g., referencing CDNI metadata objects from CDNI
capability advertisement objects). 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 request for
IANA, as well as the payload-type parameter registry definition for IANA, as well as the payload-type parameter registry definition for
IANA. IANA.
2.1. CDNI Media Type 2.1. CDNI Media Type
skipping to change at page 3, line 24 skipping to change at page 3, line 24
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 CDNI Payload Type Parameter Registry (Section 2.2) defined
below. below.
Optional parameters: none Optional parameters: none
Encoding considerations: Encoding considerations:
The CDNI protocol suite includes interfaces with json encoded The CDNI protocol suite includes interfaces with JSON encoded
messages which may be 8bit or binary, as well as generic logging messages which may be 8bit or binary, as well as generic logging
information which may be 7bit or binary. information which may be 7bit or binary.
Security considerations: Security considerations:
CDNI interfaces that return json encoded data may be CDNI interfaces that return JSON encoded data may be
(mis)interpreted if parsed by non-CDNI or non-compliant CDNI (mis)interpreted if parsed by non-CDNI or non-compliant CDNI
implementations. In addition, CDNI logging information is likely implementations. In addition, CDNI logging information is likely
to transfer large amounts of data which may overload unexpecting to transfer large amounts of data which may overload unexpecting
clients. The individual CDNI interface specifications provide clients. The individual CDNI interface specifications provide
more detailed analysis of security and privacy concerns, and more detailed analysis of security and privacy concerns, and
define the requirements for authentication, authorization, define the requirements for authentication, authorization,
confidentiality, integrity, and privacy for each interface. confidentiality, integrity, and privacy for each interface.
Interoperability considerations: Interoperability considerations:
skipping to change at page 5, line 9 skipping to change at page 5, line 9
definitions (in name or functionality), prevent gratuitous additions definitions (in name or functionality), prevent gratuitous additions
to the namespace, and prevent any additions to the namespace which to the namespace, and prevent any additions to the namespace which
would impair the interoperability of CDNI implementations. The would impair the interoperability of CDNI implementations. The
expert review will include review of a publicly available written expert review will include review of a publicly available written
specification (preferably an RFC, though an RFC is not required). specification (preferably an RFC, though an RFC is not required).
The expert review will verify the following information is documented The expert review will verify the following information is documented
in the written specification: in the written specification:
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 rhe reasonably defined purpose for the new payload type, where the
purpose is related to an existing or proposed CDNI interface and purpose is related to an existing or proposed CDNI interface and
does not duplicate the functionality of any existing CDNI protocol does not duplicate the functionality of any existing CDNI protocol
feature without specifying a rational reason (e.g., updating an feature without specifying a rational reason (e.g., updating an
obsolete feature), a method for detecting and handling conflicts obsolete feature), a method for detecting and handling conflicts
(e.g., a versioning system with prioritization matrix), and a (e.g., a versioning system with prioritization matrix), and a
suggested migration path (e.g., deprecation of the overlapped suggested migration path (e.g., deprecation of the overlapped
feature, or justification for co-existence). 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/affects.
The payload type may be applicable to multiple CDNI interfaces, The payload type may be applicable to multiple CDNI interfaces,
but the justification for the new payload type will include a but the justification for the new payload type will include a
reasonable relationship to at least one standards track CDNI reasonable relationship to at least one standards track CDNI
interface. 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 value, 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. Normative References 3. Normative References
skipping to change at page 6, line 10 skipping to change at page 6, line 10
[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>.
[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
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
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 Appendix A. Acknowledgment
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
 End of changes. 12 change blocks. 
17 lines changed or deleted 21 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/