Content Delivery Network Interconnection (CDNI) Media Type Registration
RFC 7736
|
| Document |
Type |
|
RFC - Informational
(December 2015; No errata)
|
|
Last updated |
|
2015-12-23
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
François Le Faucheur
|
|
Shepherd write-up |
|
Show
(last changed 2015-09-29)
|
| IESG |
IESG state |
|
RFC 7736 (Informational)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Barry Leiba
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
IANA OK - Actions Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
Internet Engineering Task Force (IETF) K. Ma
Request for Comments: 7736 Ericsson
Category: Informational December 2015
ISSN: 2070-1721
Content Delivery Network Interconnection (CDNI) Media Type Registration
Abstract
This document defines the standard media type used by the Content
Delivery Network Interconnection (CDNI) protocol suite, including the
registration procedure and recommended usage of the required payload-
type parameter.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
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.
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 (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Ma Informational [Page 1]
RFC 7736 CDNI Media Type December 2015
Table of Contents
1. Introduction and Scope . . . . . . . . . . . . . . . . . . . 2
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
2.1. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . 3
2.2. CDNI Payload-Types Parameters Registry . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 6
4. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Normative References . . . . . . . . . . . . . . . . . . 6
4.2. Informative References . . . . . . . . . . . . . . . . . 6
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction and Scope
The Content Delivery Network Interconnection (CDNI) working group is
developing a set of protocols to enable the interconnection of
multiple content delivery networks (CDNs), as discussed in [RFC6770].
The CDNI protocol suite consists of multiple HTTP-based interfaces,
many of which transfer various payloads encoded in JSON (JavaScript
Object Notation) [RFC7159]. The main interfaces (i.e., CDNI Control
interface, CDNI Footprint & Capabilities Advertisement interface,
CDNI Request Routing Redirection interface, CDNI Metadata interface,
and CDNI Logging interface) are described in [RFC7336]. It is
desirable to be able to indicate the type of object carried in the
HTTP entity-body without having to register separate media types for
each CDNI object. To accomplish this aim, this document defines a
single new media type for CDNI that includes a required payload-type
parameter. A separate registry of CDNI payload-type parameters is
also defined. CDNI protocol specifications may register interface-
specific payload types, specifying the payload encoding and parsing
semantics for that message (e.g., JSON serialization for a CDNI
metadata object). The same payload-type parameter may also be used
as references for other purposes (e.g., referencing CDNI metadata
objects from CDNI capability advertisement objects).
Ma Informational [Page 2]
RFC 7736 CDNI Media Type December 2015
2. IANA Considerations
This section contains the CDNI media type registration as well as the
payload-type parameter registry definition for IANA.
2.1. CDNI Media Type
Type name: application
Subtype name: cdni
Required parameters:
ptype
The required parameter "ptype" describes the type of CDNI
message contained in the message payload, as registered in the
"Content Delivery Network Interconnection (CDNI) Parameters"
registry (Section 2.2) defined below.
Optional parameters: none
Encoding considerations:
Show full document text