Folks, I originally requested this review on 12 April, but just now checked the archives and realized that the message did not appear on the list. I have now subscribed to the list, so hopefully we will get a better result this time! Given the number of media types, please let me know if the usual two week timeline presents a problem. Thanks, Tim Polk ------ Forwarded Message From: "Polk, William T." <william.polk@nist.gov> Date: Mon, 12 Apr 2010 11:35:53 -0400 To: <ietf-types@iana.org> Subject: Request for review of media types in draft-ietf-pkix-tamp Folks, The PKIX WG specification "Trust Anchor Management Protocol (TAMP)", which is available at http://www.ietf.org/id/draft-ietf-pkix-tamp-07.txt, is currently in IESG Evaluation. Unfortunately, this specification includes eleven MIME media types which were never announced on this list. I am now (belatedly) requesting that review. The following excerpt from the Internet-Draft contains the media type registrations for the eleven types present in this document. ---- excerpt from draft-ietf-pkix-tamp-07.txt ------- Internet-Draft TAMP March 2010 Appendix B. MIME Media Type Registrations Eleven MIME media type registrations are provided in this appendix. As noted in Section 2, in all cases TAMP messages are encapsulated within ContentInfo structures. Signed messages are additionally encapsulated within a SignedData structure. B.1. application/tamp-status-query To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-status-query MIME media type name: application MIME subtype name: tamp-status-query Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries a signed request for status information. Integrity protection is discussed in section 4.1. Replay detection is discussed in section 6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests for status information. Additional information: Magic number(s): None File extension(s): .TSQ Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Housley, et al. Expires September 23, 2010 [Page 84] Internet-Draft TAMP March 2010 Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG B.2. application/tamp-status-response To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-status-response MIME media type name: application MIME subtype name: tamp-status-response Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries optionally signed status information. Integrity protection is discussed in section 4.2. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests for status information. Additional information: Magic number(s): None File extension(s): .TSR Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Housley, et al. Expires September 23, 2010 [Page 85] Internet-Draft TAMP March 2010 Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG B.3. application/tamp-update To: ietf-types@iana.org Subject: Registration of MIME media type application/tamp-update MIME media type name: application MIME subtype name: tamp-update Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries a signed trust anchor update message. Integrity protection is discussed in section 4.3. Replay detection is discussed in section 6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update trust anchor information. Additional information: Magic number(s): None File extension(s): .TUR Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Housley, et al. Expires September 23, 2010 [Page 86] Internet-Draft TAMP March 2010 Change controller: IESG B.4. application/tamp-update-confirm To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-update-confirm MIME media type name: application MIME subtype name: tamp-update-confirm Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries an optionally signed TAMP update response. Integrity protection is discussed in section 4.4. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update trust anchor information Additional information: Magic number(s): None File extension(s): .TUC Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 87] Internet-Draft TAMP March 2010 B.5. application/tamp-apex-update To: ietf-types@iana.org Subject: Registration of MIME media type application/tamp-apex-update MIME media type name: application MIME subtype name: tamp-apex-update Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries a signed request to update an apex trust anchor information. Integrity protection is discussed in section 4.5. Replay detection is discussed in section 6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update an apex trust anchor. Additional information: Magic number(s): None File extension(s): .TAU Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 88] Internet-Draft TAMP March 2010 B.6. application/tamp-apex-update-confirm To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-apex-update-confirm MIME media type name: application MIME subtype name: tamp-apex-update-confirm Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries an optionally signed response to an apex update request. Integrity protection is discussed in section 4.6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update an apex trust anchor. Additional information: Magic number(s): None File extension(s): .AUC Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 89] Internet-Draft TAMP March 2010 B.7. application/tamp-community-update To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-community-update MIME media type name: application MIME subtype name: tamp-community-update Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries a signed request to update community membership information. Integrity protection is discussed in section 4.7. Replay detection is discussed in section 6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update community membership. Additional information: Magic number(s): None File extension(s): .TCU Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 90] Internet-Draft TAMP March 2010 B.8. application/tamp-community-update-confirm To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-community-update-confirm MIME media type name: application MIME subtype name: tamp-community-update-confirm Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries an optionally signed response to a community update request. Integrity protection is discussed in section 4.8. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update community membership. Additional information: Magic number(s): None File extension(s): .CUC Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 91] Internet-Draft TAMP March 2010 B.9. application/tamp-sequence-adjust To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-sequence-adjust MIME media type name: application MIME subtype name: tamp-sequence-adjust Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries a signed request to update sequence number information. Integrity protection is discussed in section 4.9. Replay detection is discussed in section 6. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update sequence number information. Additional information: Magic number(s): None File extension(s): .TSA Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 92] Internet-Draft TAMP March 2010 B.10. application/tamp-sequence-adjust-confirm To: ietf-types@iana.org Subject: Registration of MIME media type application/ tamp-sequence-adjust-confirm MIME media type name: application MIME subtype name: tamp-sequence-adjust-confirm Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries an optionally signed sequence number adjust confirmation message. Integrity protection is discussed in section 4.10. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients responding to requests to update sequence number information. Additional information: Magic number(s): None File extension(s): .SAC Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 93] Internet-Draft TAMP March 2010 B.11. application/tamp-error To: ietf-types@iana.org Subject: Registration of MIME media type application/tamp-error MIME media type name: application MIME subtype name: tamp-error Required parameters: None Optional parameters: None Encoding considerations: Binary Security considerations: Carries optionally signed error information collecting during TAMP processing. Integrity protection is discussed in section 4.11. Interoperability considerations: None Published specification: TBD Applications that use this media type: TAMP clients processing TAMP messages. Additional information: Magic number(s): None File extension(s): .TER Macintosh File Type Code(s): Person & email address to contact for further information: Sam Ashmore - srashmo@radium.ncsc.mil Intended usage: COMMON Restrictions on usage: None Author: Sam Ashmore - srashmo@radium.ncsc.mil Change controller: IESG Housley, et al. Expires September 23, 2010 [Page 94] ---- end excerpt from draft-ietf-pkix-tamp-07.txt ------- Thanks, Tim Polk IETF Security Area Director ------ End of Forwarded Message