draft-ietf-cdni-media-type-03.txt   draft-ietf-cdni-media-type-04.txt 
CDNI K. Ma CDNI K. Ma
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational September 29, 2015 Intended status: Informational October 4, 2015
Expires: April 1, 2016 Expires: April 6, 2016
CDNI Media Type Registration CDNI Media Type Registration
draft-ietf-cdni-media-type-03 draft-ietf-cdni-media-type-04
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 1, 2016. This Internet-Draft will expire on April 6, 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 3, line 16 skipping to change at page 3, line 16
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 encoded messages
messages which may be 8bit or binary, as well as generic logging 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 encoded data may be (mis)interpreted
(mis)interpreted if parsed by non-CDNI or non-compliant CDNI if parsed by non-CDNI or non-compliant CDNI implementations. In
implementations. In addition, CDNI logging information is likely addition, CDNI logging information is likely to transfer large
to transfer large amounts of data which may overload unexpecting amounts of data which may overload unexpecting clients. The
clients. The individual CDNI interface specifications provide individual CDNI interface specifications provide more detailed
more detailed analysis of security and privacy concerns, and analysis of security and privacy concerns, and define the
define the requirements for authentication, authorization, requirements for authentication, authorization, confidentiality,
confidentiality, integrity, and privacy for each interface. integrity, and privacy for each interface.
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:
 End of changes. 5 change blocks. 
14 lines changed or deleted 14 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/