draft-ietf-cdni-media-type-05.txt   draft-ietf-cdni-media-type-06.txt 
CDNI K. Ma CDNI K. Ma
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational October 8, 2015 Intended status: Informational October 13, 2015
Expires: April 10, 2016 Expires: April 15, 2016
CDNI Media Type Registration CDNI Media Type Registration
draft-ietf-cdni-media-type-05 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
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 10, 2016. This Internet-Draft will expire on April 15, 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 30 skipping to change at page 2, line 30
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 JSON (JavaScript Object Notation)
encoded payloads [RFC7159]. The main interfaces (i.e., CDNI Control encoded payloads [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 aims, 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
skipping to change at page 3, line 45 skipping to change at page 3, line 45
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 Published specification: RFCthis [RFC Editor: Please replace this
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 36 skipping to change at page 4, line 36
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 Type Parameter Registry
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 in a new category called "Content Delivery Networks Interconnection
required "ptype" parameter of the "application/cdni" media type. The (CDNI) Parameters". The "CDNI Payload Type" namespace defines the
CDNI Payload Type is an ASCII string value, consisting of only valid values for the required "ptype" parameter of the "application/
visible (printing) characters, but excluding equal signs (=), double cdni" media type. The CDNI Payload Type is an ASCII string value,
quotes ("), and semicolons (;), and not exceeding 256 characters in consisting of only visible (printing) characters, but excluding equal
length. signs (=), double quotes ("), and semicolons (;), and not exceeding
256 characters in length.
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 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),
 End of changes. 6 change blocks. 
13 lines changed or deleted 15 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/