CDNI Media Type Registration
draft-ietf-cdni-media-type-00

The information below is for an old version of the document
Document Type Active Internet-Draft (cdni WG)
Last updated 2015-08-17
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
CDNI                                                               K. Ma
Internet-Draft                                                  Ericsson
Intended status: Informational                           August 17, 2015
Expires: February 18, 2016

                      CDNI Media Type Registration
                     draft-ietf-cdni-media-type-00

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 .

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 18, 2016.

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

Ma                      Expires February 18, 2016               [Page 1]
Internet-Draft               CDNI Media Type                 August 2015

   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.

Table of Contents

   1.  Introduction and Scope  . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  CDNI Media Type . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  CDNI Payload Type Parameter Registry  . . . . . . . . . .   4
   3.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgment . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction and Scope

   The CDNI working group is developing a set of protocols to enable the
   interconnection of multiple CDNs to a CDN federation, as discussed in
   [RFC6770].  The CDNI protocol suite consists of multiple HTTP-based
   interfaces, many of which transfer various json encoded payloads.
   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 aims, this document defines a single new media type
   for CDNI that includes a required payload-type parameter.  A separate
   registry of CDNI payload-type parameter values 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 names may also be used as references for
   other purposes (e.g., referencing CDNI metadata objects from CDNI
   capability advertisement objects).

2.  IANA Considerations

   This section contains the CDNI media type registration request for
   IANA, as well as the payload-type parameter registry definition for
   IANA.

Ma                      Expires February 18, 2016               [Page 2]
Internet-Draft               CDNI Media Type                 August 2015

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
         CDNI Payload Type Parameter Registry (Section 2.2) defined
         below.

   Optional parameters: none

   Encoding considerations:
Show full document text