Request for MIME media type Application/Standards Tree
Name : Adriano Santoni Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it> MIME media type name : application MIME subtype name : timestamped-data Required parameters : None Optional parameters : None Encoding considerations : binary This media type may require encoding on transports not capable of handling binary. Security considerations : See the Security considerations in the published specification. Interoperability considerations : None Published specification :RFC 5544 Applications which use this media : Any application supporting the TimeStampedData format. Additional information : 1. Magic number(s) : None 2. File extension(s) : .TSD 3. Macintosh file type code : None 4. Object Identifiers: None None Person to contact for further information : 1. Name : Adriano Santoni 2. Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it> Intended usage : Common Carries a TimeStampedData envelope, wrapping a file (or a reference to it) with the corresponding temporal evidence. Author/Change controller : Adriano Santoni Actalis S.p.A. adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
Hi, I think that according to section 3.1 of RFC 4288 the change controller should be the IETF or the WG that handled RFC 5544 Roni Even From: ietf-types-bounces@alvestrand.no [mailto:ietf-types-bounces@alvestrand.no] On Behalf Of Adriano.Santoni Sent: Friday, April 09, 2010 9:01 AM To: ietf-types@alvestrand.no Subject: Request for MIME media type Application/Standards Tree Name : Adriano Santoni Email : adriano.santoni@actalis.it MIME media type name : application MIME subtype name : timestamped-data Required parameters : None Optional parameters : None Encoding considerations : binary This media type may require encoding on transports not capable of handling binary. Security considerations : See the Security considerations in the published specification. Interoperability considerations : None Published specification :RFC 5544 Applications which use this media : Any application supporting the TimeStampedData format. Additional information : 1. Magic number(s) : None 2. File extension(s) : .TSD 3. Macintosh file type code : None 4. Object Identifiers: None None Person to contact for further information : 1. Name : Adriano Santoni 2. Email : adriano.santoni@actalis.it Intended usage : Common Carries a TimeStampedData envelope, wrapping a file (or a reference to it) with the corresponding temporal evidence. Author/Change controller : Adriano Santoni Actalis S.p.A. adriano.santoni@actalis.it
Roni, that RFC was not developed within a WG; it was an independent submission. Adriano Il 09/04/2010 11:53, Roni Even ha scritto:
Hi,
I think that according to section 3.1 of RFC 4288 the change controller should be the IETF or the WG that handled RFC 5544
Roni Even
*From:* ietf-types-bounces@alvestrand.no [mailto:ietf-types-bounces@alvestrand.no] *On Behalf Of *Adriano.Santoni *Sent:* Friday, April 09, 2010 9:01 AM *To:* ietf-types@alvestrand.no *Subject:* Request for MIME media type Application/Standards Tree
Name : Adriano Santoni
Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
MIME media type name : application
MIME subtype name : timestamped-data
Required parameters : None
Optional parameters :
None
Encoding considerations : binary
This media type may require encoding on transports not capable of handling binary.
Security considerations :
See the Security considerations in the published specification.
Interoperability considerations :
None
Published specification :RFC 5544
Applications which use this media :
Any application supporting the TimeStampedData format.
Additional information :
1. Magic number(s) : None
2. File extension(s) : .TSD
3. Macintosh file type code : None
4. Object Identifiers: None
None
Person to contact for further information :
1. Name : Adriano Santoni
2. Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
Intended usage : Common
Carries a TimeStampedData envelope, wrapping a file (or a reference to it) with the corresponding temporal evidence.
Author/Change controller : Adriano Santoni Actalis S.p.A.
adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
* Adriano.Santoni wrote:
Name : Adriano Santoni
Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
MIME media type name : application
MIME subtype name : timestamped-data
My reading of RFC 4288 is that you need to include the registration in- formation within a publication of a standards body, in this case RFC 5544 should have included it. Would revising RFC 5544 to include the media type registration be an option here?
Required parameters : None
Optional parameters :
None
Encoding considerations : binary
This media type may require encoding on transports not capable of handling binary.
(There is no need to repeat that here, it's implied by "binary".)
Applications which use this media :
Any application supporting the TimeStampedData format.
Note that the field is named "Applications that use this media type". I would prefer a more specific reference to the kinds of applications in question (do the TimeStampedData-using applications have anything in common?)
Additional information :
1. Magic number(s) : None
2. File extension(s) : .TSD
3. Macintosh file type code : None
4. Object Identifiers: None
None
There appears to be a formatting problem here.
Person to contact for further information :
1. Name : Adriano Santoni
2. Email : adriano.santoni@actalis.it <mailto:adriano.santoni@actalis.it>
The convention is to use Adriano Santoni <adriano.santoni@actalis.it>
Intended usage : Common
This should be all-uppercase, as in "COMMON".
Author/Change controller : Adriano Santoni Actalis S.p.A.
As registrations in the standards tree require IESG approval, this should be "The IESG.". Also, author and change controller are two fields per the template in RFC 4288. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Bjoern, thank you for your comments. I realized that - according to RFC 4288 - I have to write another RFC for this registration, because the already published specification (RFC 5544) was lacking the media type registration. So I am going to post an I-D soon. I agree with all of your remarks, but I am not sure what you mean by the following one: Il 21/04/2010 12:48, Bjoern Hoehrmann ha scritto:
Note that the field is named "Applications that use this media type". I would prefer a more specific reference to the kinds of applications in question (do the TimeStampedData-using applications have anything in common?)
TimeStampedData-using applications are (normally, but not necessarily) digital signature applications, either interactive or unattended. To the extent that this media type is concerned, the only thing they have in common is the need to generate and/or update and/or verify TimeStampedData envelopes. In addition to that, the file association (based on the registered file extension) would allow desktop managers (under Windows, Linux, ecc) to automatically open such files with the proper application by just double-clicking on the icon. In addition to that, a media type would allow those envelopes to be exchanged via HTTP and e-email messages in a way that would allow browsers and email client to "know" how to deal with such content. So, what you suggest me to write in reply to "Applications which use this media:" ? Adriano
* Adriano.Santoni wrote:
Il 21/04/2010 12:48, Bjoern Hoehrmann ha scritto:
Note that the field is named "Applications that use this media type". I would prefer a more specific reference to the kinds of applications in question (do the TimeStampedData-using applications have anything in common?)
TimeStampedData-using applications are (normally, but not necessarily) digital signature applications, either interactive or unattended. To the extent that this media type is concerned, the only thing they have in common is the need to generate and/or update and/or verify TimeStampedData envelopes. In addition to that, the file association (based on the registered file extension) would allow desktop managers (under Windows, Linux, ecc) to automatically open such files with the proper application by just double-clicking on the icon. In addition to that, a media type would allow those envelopes to be exchanged via HTTP and e-email messages in a way that would allow browsers and email client to "know" how to deal with such content.
So, what you suggest me to write in reply to "Applications which use this media:" ?
I haven't looked at TimeStampedData in that much detail, if there is no better classification as the one your template had, then that one is fine. Generally the field should give people an idea like "Oh, this is for network management" or "Oh, this is for Office applications", or "Ah, a graphics format". Quite possibly the type here escapes this kind of classification. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
participants (3)
-
Adriano.Santoni -
Bjoern Hoehrmann -
Roni Even