draft-ietf-cdni-media-type-04.txt   draft-ietf-cdni-media-type-05.txt 
CDNI K. Ma CDNI K. Ma
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational October 4, 2015 Intended status: Informational October 8, 2015
Expires: April 6, 2016 Expires: April 10, 2016
CDNI Media Type Registration CDNI Media Type Registration
draft-ietf-cdni-media-type-04 draft-ietf-cdni-media-type-05
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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 April 6, 2016. This Internet-Draft will expire on April 10, 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 19 skipping to change at page 2, line 19
2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 2 2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 2
2.2. CDNI Payload Type Parameter Registry . . . . . . . . . . 4 2.2. CDNI Payload Type Parameter Registry . . . . . . . . . . 4
3. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Normative References . . . . . . . . . . . . . . . . . . 5 3.1. Normative References . . . . . . . . . . . . . . . . . . 5
3.2. Informative References . . . . . . . . . . . . . . . . . 6 3.2. Informative References . . . . . . . . . . . . . . . . . 6
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 Content Delivery Network Interconnection (CDNI) working group is
interconnection of multiple CDNs, as discussed in [RFC6770]. The developing a set of protocols to enable the interconnection of
CDNI protocol suite consists of multiple HTTP-based interfaces, many multiple content delivery networks (CDNs), as discussed in [RFC6770].
of which transfer various JSON encoded payloads [RFC7159]. The main The CDNI protocol suite consists of multiple HTTP-based interfaces,
interfaces (i.e., CDNI Control interface, CDNI Footprint & many of which transfer various JSON (JavaScript Object Notation)
Capabilities Advertisement interface, CDNI Request Routing encoded payloads [RFC7159]. The main interfaces (i.e., CDNI Control
Redirection interface, CDNI Metadata interface, and CDNI Logging interface, CDNI Footprint & Capabilities Advertisement interface,
interface) are described in [RFC7336]. It is desirable to be able to CDNI Request Routing Redirection interface, CDNI Metadata interface,
indicate the type of object carried in the HTTP entity-body without and CDNI Logging interface) are described in [RFC7336]. It is
having to register separate media types for each CDNI object. To desirable to be able to indicate the type of object carried in the
accomplish this aims, this document defines a single new media type HTTP entity-body without having to register separate media types for
for CDNI that includes a required payload-type parameter. A separate each CDNI object. To accomplish this aims, this document defines a
registry of CDNI payload-type parameters is also defined. CDNI single new media type for CDNI that includes a required payload-type
protocol specifications may register interface-specific payload- parameter. A separate registry of CDNI payload-type parameters is
types, specifying the payload encoding and parsing semantics for that also defined. CDNI protocol specifications may register interface-
message (e.g., JSON serialization for a CDNI metadata object). The specific payload-types, specifying the payload encoding and parsing
same payload-type parameter may also be used as references for other semantics for that message (e.g., JSON serialization for a CDNI
purposes (e.g., referencing CDNI metadata objects from CDNI metadata object). The same payload-type parameter may also be used
capability advertisement objects). as references for other purposes (e.g., referencing CDNI metadata
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 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
Type name: application Type name: application
skipping to change at page 3, line 31 skipping to change at page 3, line 31
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 which 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
by multiple CDNI interfaces for transporting different types of
control and logging information. Proper validation of message
data requires parsing and understanding the ptype parameter and
the associated data encoding. Failure to properly validate
payloads may allow data extrusion under the auspices of the
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 Published specification: RFCthis
Applications that use this media type: Applications that use this media type:
skipping to change at page 4, line 36 skipping to change at page 4, line 45
The IANA is requested to create a new "CDNI Payload Type" registry. The IANA is requested to create a new "CDNI Payload Type" registry.
The "CDNI Payload Type" namespace defines the valid values for the The "CDNI Payload Type" namespace defines the valid values for the
required "ptype" parameter of the "application/cdni" media type. The required "ptype" parameter of the "application/cdni" media type. The
CDNI Payload Type is an ASCII string value, consisting of only CDNI Payload Type is an ASCII string value, consisting of only
visible (printing) characters, but excluding equal signs (=), double visible (printing) characters, but excluding equal signs (=), double
quotes ("), and semicolons (;), and not exceeding 256 characters in quotes ("), and semicolons (;), and not exceeding 256 characters in
length. length.
ptype = 1*256(ptype-char) ptype = 1*256(ptype-char)
ptype-char = %x21 / %23-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 Type namespace will conform to the
"Specification Required" policy as defined in [RFC5226]. The "Specification Required" policy as defined in [RFC5226]. The
designated expert will verify that new type definitions do not designated expert will verify that new type definitions do not
duplicate existing type definitions (in name or functionality), duplicate existing type definitions (in name or functionality),
prevent gratuitous additions to the namespace, and prevent any prevent gratuitous additions to the namespace, and prevent any
additions to the namespace which would impair the interoperability of additions to the namespace which would impair the interoperability of
CDNI implementations. The designated expert will review the CDNI implementations. The designated expert will review the
skipping to change at page 5, line 39 skipping to change at page 5, line 47
+--------------+---------------+ +--------------+---------------+
| Payload Type | Specification | | Payload Type | Specification |
+--------------+---------------+ +--------------+---------------+
+--------------+---------------+ +--------------+---------------+
3. References 3. References
3.1. Normative References 3.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[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 3.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,
 End of changes. 7 change blocks. 
29 lines changed or deleted 33 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/