Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 30 Sep 2010 14:03:46 -0700
Message-ID: <9FA16888AD1BF64ABCE6C2532CCEB98A0BCEF277@xmb-sjc-219.amer.cisco.com>
In-Reply-To: <34ADB643-73EC-407C-8BFC-D703FABAC1AD@network-heretics.com>
Thread-Topic: [ietf-types] Registration Of media types application/cdmi-*
Thread-Index: Actd4Uk+qljdEpcRS7eb/IKuKaXcMgDANUcw
References: <9FA16888AD1BF64ABCE6C2532CCEB98A0BB2ACB2@xmb-sjc-219.amer.cisco.com>
 <jfai96d4ebud62rjns4cn4758bnf7miji4@hive.bjoern.hoehrmann.de>
 <9FA16888AD1BF64ABCE6C2532CCEB98A0BB2AEE1@xmb-sjc-219.amer.cisco.com>
 <322785A3-9374-4079-83CA-5AB85395BAED@network-heretics.com>
 <9FA16888AD1BF64ABCE6C2532CCEB98A0BC06D10@xmb-sjc-219.amer.cisco.com>
 <34ADB643-73EC-407C-8BFC-D703FABAC1AD@network-heretics.com>
From: "Krishna Sankar (ksankar)" <ksankar@cisco.com>
To: <ietf-types@ietf.org>
Subject: Re: [ietf-types] Registration Of media types application/cdmi-*
Precedence: list

Agreed and corrected.
----------------------------
6.  IANA Considerations

   This memo includes a request to IANA to register the following media
   types :

   o  application/cdmi-domain

   o  application/cdmi-capability

   o  application/cdmi-container

   o  application/cdmi-object and

   o  application/cdmi-queue

6.1.  Media Type application/cdmi-capability

   Type name: application

   Subtype name: cdmi-capability

   Required parameters: none

   Optional parameters: none

   Encoding considerations: Assumes that the representation is always
   UTF-8, as defined in [RFC3629] and any "charset" MIME parameter will
   be ignored.  The primary transport is HTTP and a base64 encoding is
   appropriate when transporting such objects over other transports like
   email.

   Security considerations: See Section 7 of draft-cdmi-mediatypes-02

   Interoperability considerations: none

   Published specification: draft-cdmi-mediatypes-02

   Applications that use this media type: Implementations of the Cloud
   Data Management Interface (CDMI) defined by the Storage Networking
   Industry Association (SNIA)

   Additional information:

      Magic number(s): none

      File extension(s): none

      Macintosh file type code(s): none

   Person and email address to contact for further information: Arnold
   Jones arnold.jones@snia.org

   Intended usage: COMMON

   Restrictions on usage: none

   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org

   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org

6.2.  Media Type application/cdmi-container

   Type name: application

   Subtype name: cdmi-container

   Required parameters: none

   Optional parameters: none

   Encoding considerations: Assumes that the representation is always
   UTF-8, as defined in [RFC3629] and any "charset" MIME parameter will
   be ignored.  The primary transport is HTTP and a base64 encoding is
   appropriate when transporting such objects over other transports like
   email.

   Security considerations: See Section 7 of draft-cdmi-mediatypes-02

   Interoperability considerations: none

   Published specification: draft-cdmi-mediatypes-02

   Applications that use this media type: Implementations of the Cloud
   Data Management Interface (CDMI) defined by the Storage Networking
   Industry Association (SNIA)

   Additional information:

      Magic number(s): none

      File extension(s): none

      Macintosh file type code(s): none

   Person and email address to contact for further information: Arnold
   Jones arnold.jones@snia.org

   Intended usage: COMMON

   Restrictions on usage: none

   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org

   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org

6.3.  Media Type application/cdmi-domain

   Type name: application

   Subtype name: cdmi-domain

   Required parameters: none

   Optional parameters: none

   Encoding considerations: Assumes that the representation is always
   UTF-8, as defined in [RFC3629] and any "charset" MIME parameter will
   be ignored.  The primary transport is HTTP and a base64 encoding is
   appropriate when transporting such objects over other transports like
   email.

   Security considerations: See Section 7 of draft-cdmi-mediatypes-02

   Interoperability considerations: none

   Published specification: draft-cdmi-mediatypes-02

   Applications that use this media type: Implementations of the Cloud
   Data Management Interface (CDMI) defined by the Storage Networking
   Industry Association (SNIA)

   Additional information:

      Magic number(s): none

      File extension(s): none

      Macintosh file type code(s): none

   Person and email address to contact for further information: Arnold
   Jones arnold.jones@snia.org

   Intended usage: COMMON

   Restrictions on usage: none

   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org

   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org

6.4.  Media Type application/cdmi-object

   Type name: application

   Subtype name: cdmi-object

   Required parameters: none

   Optional parameters: none

   Encoding considerations: Assumes that the representation is always
   UTF-8, as defined in [RFC3629] and any "charset" MIME parameter will
   be ignored.  The primary transport is HTTP and a base64 encoding is
   appropriate when transporting such objects over other transports like
   email.

   Security considerations: See Section 7 of draft-cdmi-mediatypes-02

   Interoperability considerations: none

   Published specification: draft-cdmi-mediatypes-02

   Applications that use this media type: Implementations of the Cloud
   Data Management Interface (CDMI) defined by the Storage Networking
   Industry Association (SNIA)

   Additional information:

      Magic number(s): none

      File extension(s): none

      Macintosh file type code(s): none

   Person and email address to contact for further information: Arnold
   Jones arnold.jones@snia.org

   Intended usage: COMMON

   Restrictions on usage: none

   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org

   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org

6.5.  Media Type application/cdmi-queue

   Type name: application

   Subtype name: cdmi-queue

   Required parameters: none

   Optional parameters: none

   Encoding considerations: Assumes that the representation is always
   UTF-8, as defined in [RFC3629] and any "charset" MIME parameter will
   be ignored.  The primary transport is HTTP and a base64 encoding is
   appropriate when transporting such objects over other transports like
   email.

   Security considerations: See Section 7 of draft-cdmi-mediatypes-02

   Interoperability considerations: none

   Published specification: draft-cdmi-mediatypes-02

   Applications that use this media type: Implementations of the Cloud
   Data Management Interface (CDMI) defined by the Storage Networking
   Industry Association (SNIA)

   Additional information:

      Magic number(s): none

      File extension(s): none

      Macintosh file type code(s): none

   Person and email address to contact for further information: Arnold

   Jones arnold.jones@snia.org

   Intended usage: COMMON

   Restrictions on usage: none

   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org

   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org

----------------------------
Cheers
<k/>

From: Keith Moore [mailto:moore@network-heretics.com]=20
Sent: Sunday, September 26, 2010 6:14 PM
To: Krishna Sankar (ksankar)
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Registration Of media types application/cdmi-*

On Sep 26, 2010, at 9:03 PM, Krishna Sankar (ksankar) wrote:


Keith,
	Thanks. Good comments. Corrected.

Thanks, but I have some additional comments. =A0Taking just one of these =
as an example:


6.1. =A0Media Type application/cdmi-capability

=A0=A0Type name: application

=A0=A0Subtype name: cdmi-capability

=A0=A0Required parameters: none
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0****

=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0
=A0=A0Optional parameters: none
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ****


=A0=A0Encoding considerations: The "charset" MIME parameter, if present,
=A0=A0MUST be set to "UTF-8", as defined in [RFC3629]. =A0

You've declared that there are no parameters, either required or =
optional, and then you immediately say that the (nonexistent) charset =
parameter must be set to UTF-8.

Normally application/* types don't have a charset parameter at all. =
=A0charset is a parameter that tends to be used with text/* types. =
=A0RFC 3629 even says (in section 8) "UTF-8 is suitable for use in MIME =
content types under the "text" top-level type."

You can define a charset parameter for your type if you want to do so. =
=A0But if the charset is always going to be UTF-8, I don't see why you =
should bother. =A0Putting a charset parameter there just invites people =
to set it to something other than UTF-8.

Also, if you want to insist that the representation always be in UTF-8, =
the best way to do that would appear to be to simply state that the =
representation is always UTF-8 and that any charset parameter is to be =
ignored.