* 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/