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>