February 2005 - Ietf-types

Media Type "text/csv": new draft (-02) and Last Call
by Yakov Shafranovich 23 Mar '05

23 Mar '05

I posted a new draft (-02) with minor ABNF corrections. The new draft can be found in the IETF repository: http://www.ietf.org/internet-drafts/draft-shafranovich-mime-csv-02.txt The HTML version, a diff of changes and all previous versions can be found here: http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime… http://www.shaftek.org/publications/drafts/mime-csv/rfcdiff-01-to-02.html http://www.shaftek.org/publications/drafts/mime-csv/ Scott Hollenbeck (APP AD) has reviewed my draft and initiated a Last Call on it which is expected to last about four weeks. Yakov

2 1

Scripting Media Types
by Bjoern Hoehrmann 22 Feb '05

22 Feb '05

Hi, A new Internet-Draft is available from the online Internet-Drafts directories. This memo describes media types for the ECMAScript and JavaScript programming languages. http://www.ietf.org/internet-drafts/draft-hoehrmann-script-types-01.txt http://www.websitedev.de/ietf/draft-hoehrmann-script-types-01.txt Please send comments to the ietf-types mailing list, refer to http://www.alvestrand.no/mailman/listinfo/ietf-types for details. If no major issues arise, I'll ask the IESG to consider the document for publication as Informational RFC in about two weeks. Thanks, -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

7 30

Media Type "text/csv", new draft (-01)
by Yakov Shafranovich 17 Feb '05

17 Feb '05

I spend some time working in a new draft for this MIME type taking into accounts comments from this list and others. In particular: 1. I removed the "text/comma-separated-values" type and only left one MIME type "text/csv". 2. I changed the definitions to follow the CRLF convention for the "text" type for linebreaks. 3. Significant changes in ABNF grammar with a lot of help from Dave Crocker. 4. The CSV format has been moved to the normative part of the document. I would appreciate comments and suggestions on the new draft. Until it posts into the IETF repository, it can be found here: http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime… http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime… An HTML list of changes is here: http://www.shaftek.org/publications/drafts/mime-csv/rfcdiff-00-to-01.html Thanks, Yakov

1 0

Discount generic drugs
by Vickie Magee 14 Feb '05

14 Feb '05

1 0

Seeking co-moderators(s) of the ietf-types list
by Harald Tveit Alvestrand 10 Feb '05

10 Feb '05

Hello, Bill Carpenter, who has long co-moderated the ietf-types list along with me, has asked to drop out of the role. At the same time, two events have emphasized the need for a co-moderator: - A couple of requests and comments got severely delayed in the moderator queue - I've scheduled a vacation for the month of April Together, these things clearly indicate that someone needs to be on hand to moderate the list - both when I'm here and when I'm gone. The lists run on Mailman, behind a spam filter, and with an ancillary script that deletes the more obvious spam from the queue. Still, there's spam coming through - unfortunately. Volunteers? thanks in advance! Harald

4 5

Media Types 'text/csv' and 'text/comma-separated-values'
by Yakov Shafranovich 08 Feb '05

08 Feb '05

Hi all, I noticed that the MIME registration tree has an entry for 'text/tab-separated-values' but for some reason doesn't have any registration for 'text/comma-separated-values' or 'text/csv. I have been reviewing some of the stuff out there and so far have seen the following being used: application/csv text/csv text/comma-separated-values text/x-csv I was wondering if there would be any value to formally register two of the CSV types being used from the text tree (text/csv and text/comma-separated-values). I put together a small draft which hasn't posted to the ID repository yet. A copy should be available here: http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime… Yakov

3 5

Discount generic drugs
by Tim Mckinley 07 Feb '05

07 Feb '05

1 0

Updated Registration of media type "application/nss"
by Mike Hammer 04 Feb '05

04 Feb '05

(Second try) This email requests that the IESG approve the assignment of the media subtype as described in the registration template below. Reference: draft-freed-media-type-reg-02.txt, January 11, 2005, Media Type Specifications and Registration Procedures, Section 5, Registration Procedures, Section 10, Registration Template. To: ietf-types(a)iana.org Subject: Registration of media type "application/nss" Type name: application Subtype name: nss Required parameters: none Optional parameters: charset Encoding considerations: binary (Note: Data is in US-ASCII range.) Security considerations: NSS has the potential to disclose private customer information and the potential for modification of NSS bodies during message transport to manipulate call setup, mid-call events, or call release. Modification means the addition of an NSS body where none existed, the removal of an NSS body where one existed, or the changing of contents of existing NSS bodies in messages. NSS can reveal information about telephone subscribers that is requested to remain private. Security mechanisms must be provided to meet privacy agreements and regulations. NSS can be deployed as an interdomain signaling mechanism and may be subject to trust relationships and agreements between administrative domains as well as legal requirements in various jurisdictions. NSS can affect routing of telephone calls and associated billing. Security mechanisms must be provided to control fraud, malicious intents, and unintended consequences. Such mechanisms include the ability to selectively filter or map and forward each information element within NSS upon entry or exit of an administrative domain. It is expected that nodes performing such functions will be User Agents, such as gateway nodes or IP-based Application servers acting on behalf of users. Note that RFC 3261 Section 16.6 says: "The proxy MUST NOT add to, modify, or remove the message body." That includes NSS bodies. All information from unauthenticated entities must be validated and authorized before being mapped and forwarded in subsequent signaling messages. Such checks are particularly needed when information is mapped to/from SIP headers. Note, however, that the intent of NSS is to carry data that would be mutually exclusive with the data capable of being carried in SIP headers. When encapsulated by SIP, the integrity and confidentiality of SIP messages containing NSS bodies must be addressed. SIP mandates that Transport Layer Security (TLS) must be supported. The Internet Protocol Security (IPSEC) mechanisms may be used as an alternative on signaling hops between nodes trusted to handle PSTN signaling. TLS and IPSEC are discussed in Section 26 of the Session Initiation Protocol RFC 3261. However, trusted nodes would need to specify and agree on the security suites to be used with IPSEC. See RFC 3324 for discussion on trust domains and related security requirements. When intermediate hops are not trusted, end-to-end integrity and confidentiality may be addressed using S/MIME: RFC 3850, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate Handling", July 2004. RFC 3851, "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification", July 2004. RFC 3852, "Cryptographic Message Syntax (CMS)", July 2004. RFC 3853, "S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)", July 2004. NSS MIME bodies should be secured using S/MIME to mitigate concerns with authentication of the sender, integrity protection during transit, and confidentiality protection from disclosure to unauthorized third parties. NSS endpoints must support S/MIME signatures and should support S/MIME encryption. For H.323-based encapsulation of NSS bodies, the security mechanisms of ITU-T Recommendation H.235, "Security and encryption for H-series (H.323 and other H.245-based) multimedia terminals", August 2003, must be used to provide integrity and confidentiality. NSS consists of well defined message types and parameters. Arbitrary content or directives within field values is not permitted. NSS does not employ "active content." NSS contains fields which instruct whether privacy data such as calling party's number is to be presented or restricted. NSS is used without and is silent about compression. Use of compression in conjunction with NSS does not present any security issues. Interoperability considerations: Compatibility mechanisms are defined in Q.1980.1. Published specification: ITU-T Recommendation Q.1980.1, "The Narrowband Signalling Syntax (NSS) - Syntax Definition", December 2004. Link: http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-Q .1980.1 Applications which use this media type: Applications in PSTN Gateways and call control application servers. Additional Information: Magic numbers: None File Extensions: None Macintosh File Type Codes: None Object Identifiers: {itu-t(0) recommendation(0) q(17) 1980 1} (0.0.17.1980.1) See ITU-T Recommendation H.323 Annex M.4 "Tunneling of Narrowband Signalling Syntax (NSS) for H.323", December 2004. Person to contact for further information: Name: Michael Hammer E-Mail: mhammer(a)cisco.com Intended Usage: COMMON Restrictions on usage: None Author: ITU-T Study Group 11 Change controller: ITU-T Study Group 11 END

1 0

Re: Proposed media type registration: application/wsdl+xml
by David Booth 04 Feb '05

04 Feb '05

This proposed media type registration was previously sent to ietf-types(a)iana.org on 04-Oct-2004: http://eikenes.alvestrand.no/pipermail/ietf-types/2004-October/000438.html The only comment received (which was sent privately) was a suggested change to the contact information to read: [[ Person & email address to contact for further information: World Wide Web Consortium <web-human(a)w3.org> ]] The version below reflects the above-mentioned change. ---------------------------------------------------------- The proposed registration below is for a media type "application/wsdl+xml" for use with WSDL 2.0 documents. The registration will be requested on behalf of the W3C Web Services Description Working Group. WSDL 2.0 documents are used to describe Web services. The specification of the WSDL 2.0 language itself is available at http://www.w3.org/TR/wsdl20 . This media type definition appears in http://www.w3.org/TR/wsdl20#ietf-draft , which will be updated as necessary. (The version below is the most recent.) This proposed registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA at a later stage. The Last Call period for WSDL 2.0 ends 4 October 2004. However, because of this late notification, the deadline for comments on the media type registration has been extended to 18 October 2004. ======================================================= To: ietf-types(a)iana.org Subject: Registration of media type application/wsdl+xml Type name: application Subtype name: wsdl+xml Required parameters: none Optional parameters: charset This parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in [RFC 3023] ( http://www.ietf.org/rfc/rfc3023.txt ). Encoding considerations: Identical to those of "application/xml" as described in [RFC 3023] ( http://www.ietf.org/rfc/rfc3023.txt ) section 3.2, as applied to the WSDL document infoset. Restrictions on usage: none Security considerations: This media type uses the "+xml" convention. It shares the same security considerations as described in [RFC 3023] ( http://www.ietf.org/rfc/rfc3023.txt ) section 10. Interoperability considerations: There are no known interoperability issues. Published specification: [WSDL 2.0 Core Language] ( http://www.w3.org/TR/wsdl20 ), [WSDL 2.0 Predefined Extensions] ( http://www.w3.org/TR/wsdl20-extensions ), and [WSDL 2.0 Bindings] ( http://www.w3.org/TR/wsdl20-bindings ). Applications which use this media type: No known applications currently use this media type. Additional information: Magic number(s): In general, the same as for application/xml [RFC 3023] ( http://www.ietf.org/rfc/rfc3023.txt ). In particular, the XML root element of the returned object will be <wsdl:description>, where "wsdl" as any namespace prefix that maps to a WSDL 2.0 namespace URI, as defined in [WSDL 2.0 Core Language] ( http://www.w3.org/TR/wsdl20 ). File extension(s): wsdl Macintosh File Type Code(s): WSDL Base URI: As specified in [RFC 3023] ( http://www.ietf.org/rfc/rfc3023.txt ) section 6. Fragment identifiers: As specified in [WSDL 2.0 FragIDs]. Person & email address to contact for further information: World Wide Web Consortium <web-human(a)w3.org> Intended usage: COMMON Author/Change controller: The WSDL 2.0 specification set is a work product of the World Wide Web Consortium's Web Service Description Working Group [WSDL 2.0 WG]. The W3C has change control over these specifications. References: [RFC 3023] IETF "RFC 3023: XML Media Types", M. Murata, S. St. Laurent, D. Kohn, July 1998. (See http://www.ietf.org/rfc/rfc3023.txt .) [WSDL 2.0 Core Language] Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language, R. Chinnici, M. Gudgin, J-J. Moreau, S. Weerawarana, Editors. World Wide Web Consortium, 3 August 2004. This version of the "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language" Specification is available is available at http://www.w3.org/TR/2004/WD-wsdl20-20040803 . The latest version of "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language" is available at http://www.w3.org/TR/wsdl20 . [WSDL 2.0 FragIDs] WSDL 2.0 Fragment Identifiers. This is a subsection of [WSDL 2.0 Core Language] above. The latest version is available at http://www.w3.org/TR/wsdl20/#frag-ids [WSDL 2.0 Predefined Extensions] Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions, M. Gudgin, A. Lewis, and J. Schlimmer, Editors. World Wide Web Consortium, 3 August 2004. This version of the "Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions" Specification is available at http://www.w3.org/TR/2004/WD-wsdl20-extensions-20040803 . The latest version of "Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions" is available at http://www.w3.org/TR/wsdl20-extensions . [WSDL 2.0 Bindings] Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings, H. Haas, P. Le Hégaret, J-J. Moreau, D. Orchard, J. Schlimmer, Editors. World Wide Web Consortium, 3 August 2004. This version of the "Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings" Specification is available at http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803 . The latest version of "Web Services Description Language (WSDL) Version 2.0 Part 3: Bindings" is available at http://www.w3.org/TR/wsdl20-bindings . [WSDL 2.0 WG] The W3C Web Services Description Working Group. Information about this Working Group is available at http://www.w3.org/2002/ws/desc/ [XML 1.0] Extensible Markup Language (XML) 1.0 (Second Edition), T. Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web Consortium, 10 February 1998, revised 6 October 2000. This version of the XML 1.0 Recommendation is http://www.w3.org/TR/2000/REC-xml-20001006 . The latest version of XML 1.0 is available at http://www.w3.org/TR/REC-xml . -------------------- The proposal above was prepared following instructions at http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-01.txt , and further instructions at http://www.w3.org/2002/06/registering-mediatype.html , since this is a media type from W3C. -- David Booth W3C Fellow / Hewlett-Packard

1 0