Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <9FA16888AD1BF64ABCE6C2532CCEB98A0BB2AEE1@xmb-sjc-219.amer.cisco.com>
Date: Wed, 22 Sep 2010 11:47:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <322785A3-9374-4079-83CA-5AB85395BAED@network-heretics.com>
References: <9FA16888AD1BF64ABCE6C2532CCEB98A0BB2ACB2@xmb-sjc-219.amer.cisco.com>
 <jfai96d4ebud62rjns4cn4758bnf7miji4@hive.bjoern.hoehrmann.de>
 <9FA16888AD1BF64ABCE6C2532CCEB98A0BB2AEE1@xmb-sjc-219.amer.cisco.com>
To: Krishna Sankar (ksankar) <ksankar@cisco.com>
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Registration Of media types application/cdmi-*
Precedence: list

1. You claim to be registering application/cdmi-* but the actual subtype =
names in the individual templates don't start with "cdmi-".  Please add =
them.  I think it would be bad if application/capability, =
application/domain, etc. were registered.

2. Re: Encoding considerations.  Normally this would be some =
recommendation about whether to use base64, quoted-printable, or =
whatever, when transporting objects of this type over MIME email.  Your =
type applications don't say anything about that.  Your applications =
supply advice about using a charset parameter, but your proposed types =
don't even define a charset parameter.    Parameters defined for one =
type (say text/plain) do not automatically exist for other types.

I'm just guessing, but perhaps you'd like to say that since objects of =
type application/cdmi-* consist of utf-8 text, base64 encoding is =
appropriate when transporting such objects over email. =20

3. Security considerations.  IANA probably knows enough to supply the =
missing detail, but just in case they miss it :   Type registrations are =
intended to be standalone.  "See Section 7" begs the question "of what?"

On Sep 21, 2010, at 9:42 PM, Krishna Sankar (ksankar) wrote:

> Corrected request for registration and have submitted =
draft-cdmi-mediatypes-00 :
>=20
> Hi all,
>   Would like to register the following media types.  Please send me =
any questions, suggestions, insights and so forth.
>=20
> ---------------------
> 6.  IANA Considerations
>=20
>   This memo includes a request to IANA to register the following media
>   types :
>=20
>   o  application/cdmi-domain
>=20
>   o  application/cdmi-capability
>=20
>   o  application/cdmi-container
>=20
>   o  application/cdmi-object and
>=20
>   o  application/cdmi-queue
>=20
> 6.1.  Media Type application/cdmi-capability
>=20
>   Type name: application
>=20
>   Subtype name: capability
>=20
>   Required parameters: none
>=20
>   Optional parameters: none
>=20
>   Encoding considerations: The "charset" MIME parameter, if present,
>   MUST be set to "UTF-8", as defined in [RFC3629].
>=20
>   Security considerations: See Section 7.
>=20
>   Interoperability considerations: none
>=20
>   Published specification: draft-cdmi-mediatypes-00
>=20
>   Applications that use this media type: Implementations of the Cloud
>   Data Management Interface (CDMI) defined by the Storage Networking
>   Industry Association (SNIA)
>=20
>   Additional information:
>=20
>      Magic number(s): none
>=20
>      File extension(s): none
>=20
>      Macintosh file type code(s): none
>=20
>   Person and email address to contact for further information: Arnold
>   Jones arnold.jones@snia.org
>=20
>   Intended usage: COMMON
>=20
>   Restrictions on usage: none
>=20
>   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
>   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
> 6.2.  Media Type application/cdmi-container
>=20
>   Type name: application
>=20
>   Subtype name: container
>=20
>   Required parameters: none
>=20
>   Optional parameters: none
>=20
>   Encoding considerations: The "charset" MIME parameter, if present,
>   MUST be set to "UTF-8", as defined in [RFC3629].
>=20
>   Security considerations: See Section 7.
>=20
>   Interoperability considerations: none
>=20
>   Published specification: draft-cdmi-mediatypes-00
>=20
>   Applications that use this media type: Implementations of the Cloud
>   Data Management Interface (CDMI) defined by the Storage Networking
>   Industry Association (SNIA)
>=20
>   Additional information:
>=20
>      Magic number(s): none
>=20
>      File extension(s): none
>=20
>      Macintosh file type code(s): none
>=20
>   Person and email address to contact for further information: Arnold
>   Jones arnold.jones@snia.org
>=20
>   Intended usage: COMMON
>=20
>   Restrictions on usage: none
>=20
>   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
>   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
> 6.3.  Media Type application/cdmi-domain
>=20
>   Type name: application
>=20
>   Subtype name: domain
>=20
>   Required parameters: none
>=20
>   Optional parameters: none
>=20
>   Encoding considerations: The "charset" MIME parameter, if present,
>   MUST be set to "UTF-8", as defined in [RFC3629].
>=20
>   Security considerations: See Section 7.
>=20
>   Interoperability considerations: none
>=20
>   Published specification: draft-cdmi-mediatypes-00
>=20
>   Applications that use this media type: Implementations of the Cloud
>   Data Management Interface (CDMI) defined by the Storage Networking
>   Industry Association (SNIA)
>=20
>   Additional information:
>=20
>      Magic number(s): none
>=20
>      File extension(s): none
>=20
>      Macintosh file type code(s): none
>=20
>   Person and email address to contact for further information: Arnold
>   Jones arnold.jones@snia.org
>=20
>   Intended usage: COMMON
>=20
>   Restrictions on usage: none
>=20
>   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
>   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
> 6.4.  Media Type application/cdmi-object
>=20
>   Type name: application
>=20
>   Subtype name: object
>=20
>   Required parameters: none
>=20
>   Optional parameters: none
>=20
>   Encoding considerations: The "charset" MIME parameter, if present,
>   MUST be set to "UTF-8", as defined in [RFC3629].
>=20
>   Security considerations: See Section 7.
>=20
>   Interoperability considerations: none
>=20
>   Published specification: draft-cdmi-mediatypes-00
>=20
>   Applications that use this media type: Implementations of the Cloud
>   Data Management Interface (CDMI) defined by the Storage Networking
>   Industry Association (SNIA)
>=20
>   Additional information:
>=20
>      Magic number(s): none
>=20
>      File extension(s): none
>=20
>      Macintosh file type code(s): none
>=20
>   Person and email address to contact for further information: Arnold
>   Jones arnold.jones@snia.org
>=20
>   Intended usage: COMMON
>=20
>   Restrictions on usage: none
>=20
>   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
>   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
> 6.5.  Media Type application/cdmi-queue
>=20
>   Type name: application
>=20
>   Subtype name: queue
>=20
>   Required parameters: none
>=20
>   Optional parameters: none
>=20
>   Encoding considerations: The "charset" MIME parameter, if present,
>   MUST be set to "UTF-8", as defined in [RFC3629].
>=20
>   Security considerations: See Section 7.
>=20
>   Interoperability considerations: none
>=20
>   Published specification: draft-cdmi-mediatypes-00
>=20
>   Applications that use this media type: Implementations of the Cloud
>   Data Management Interface (CDMI) defined by the Storage Networking
>   Industry Association (SNIA)
>=20
>   Additional information:
>=20
>      Magic number(s): none
>=20
>      File extension(s): none
>=20
>      Macintosh file type code(s): none
>=20
>   Person and email address to contact for further information: Arnold
>   Jones arnold.jones@snia.org
>=20
>   Intended usage: COMMON
>=20
>   Restrictions on usage: none
>=20
>   Author: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
>   Change controller: SNIA Cloud Storage Initiative cloudtwg@snia.org
>=20
> ---------------------
> Cheers & thanks
> <k/>
>=20
> =
--------------------------------------------------------------------------=
----
>        |            |        Krishna Sankar, Distinguished Engineer
>       :|:          :|:       http://doubleclix.wordpress.com/about/
>      :|||:        :|||:      - Cloud Computing, Social Networks
>  ..:|||||||:.....:|||||||:.. - Semantic Social Networking =3D =
DeComplexify - ..
>      Cisco  Systems Inc      - ... Contextualize-Network-Reason & then =
Infer
>      (Ph) 408-853-8475       ksankar@cisco.com
> =
--------------------------------------------------------------------------=
---
> "Not all those who wander are lost ..." -J.R.R.Tolkien
> =
--------------------------------------------------------------------------=
---
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net]=20
> Sent: Tuesday, September 21, 2010 2:59 PM
> To: Krishna Sankar (ksankar)
> Cc: ietf-types@ietf.org
> Subject: Re: [ietf-types] Registration Of media types =
application/cdmi-*
>=20
> * Krishna Sankar (ksankar) wrote:
>>               Would like to register the following media types.
>> Please send me any questions, suggestions, insights and so forth.
>=20
>>  Published specification: draft-cdmi-mediatypes-01
>=20
> I could not find this draft. I also tried my favourite search engine
> with some of the phrases from the templates but came up empty.
> --=20
> Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 =
http://bjoern.hoehrmann.de
> Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 =
http://www.bjoernsworld.de
> 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 =
http://www.websitedev.de/=20
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types
>=20