Hi,
Attached are three MIME types for prelimiary community review before
registration. Any feedback would be most welcome.
I understand the new 'Media Type Specifications and Registration
Procedures' [1], which obsoletes RFC 2048, is in effect even though no
new RFC number has been assigned.
The MIME types are specified in the following:
ITU-T Rec. X.891 | ISO/IEC 24824-1 (Fast Infoset) [2]
ITU-T Rec. X.892 | ISO/IEC 24824-2 (Fast Web Services) [3]
both of which are Final Committee Drafts under ballot in ISO. The ballot
finishes on the 1st Feb 2005.
If there are any changes required as a result of review then i can
incorporate these into an ISO ballot comment.
I plan to sumbit the MIME types to IANA (iana at iana.org) in about 2 weeks
time.
Thanks,
Paul.
[1] http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-01.txt
[2]
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41327&scopelist=PROGRAMME
[3]
http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=41328&scopelist=PROGRAMME
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109
-------------- next part --------------
MIME media type name:
application
MIME subtype name:
soap+fastinfoset
Required parameters:
None.
Optional parameters:
"action": This parameter shall be used to identify the intent of the W3C SOAP
message infoset as specified for the "action" parameter of the W3C SOAP 1.2
"application/soap+xml" MIME media type (see W3C SOAP 1.2 Part 2, Appendix A). The
value of the "action" parameter shall be an absolute URI-reference as specified in
IETF RFC 2396. No restriction shall be placed on the specificity of the URI or that
it is resolvable.
Encoding considerations:
This media type is used to identify W3C SOAP message infosets serialized as fast
infoset documents as specified in ITU-T Rec. X.892 | ISO/IEC 24824-2.
Use of this MIME media type will require additional specification if used on
transports that do not provide 8-bit binary transparency. (For the purposes of
Fast Web Services, ITU-T Rec. X.892 | ISO/IEC 24824-2, this media type is always
used with HTTP as the transport mechanism, and no further specification is needed.)
Security considerations:
Because W3C SOAP message infosets can carry application defined data whose
semantics is independent from that of any MIME wrapper (or context within which the
MIME wrapper is used), one should not expect to be able to understand the semantics
of the W3C SOAP message infoset based on the semantics of the MIME wrapper alone.
Therefore, whenever using the "application/soap+fastinfoset" media type, it is
strongly recommended that the security implications of the context within which the
W3C SOAP message infoset is used is fully understood. The security implications are
likely to involve the specific SOAP binding to an underlying protocol as well as
the application-defined semantics of the data carried in the W3C SOAP message
infoset.
Interoperability considerations:
There are no known interoperability issues.
Published specification:
ITU-T Rec. X.892 | ISO/IEC 24824-2
Applications which use this media type:
No known applications that use this media type.
Additional information:
Magic number(s):
A W3C SOAP message infoset serialized as a fast infoset document may begin
with one of the following byte sequences:
- a byte sequence that corresponds to a UTF-8 encoded XML declaration of the
string "<?xml version='1.0' encoding='finf'", the first five bytes of which
are hexadecimal 3C 3F 78 6D 6C;
- a byte sequence that corresponds to a UTF-8 encoded XML declaration of the
string "<?xml version='1.1' encoding='finf'", the first five bytes of which
are also hexadecimal 3C 3F 78 6D 6C;
- a byte sequence of hexadecimal E0 00 00 01.
File extension(s):
W3C SOAP message infosets serialized as fast infoset documents are not
required or expected to be stored as files.
Person & email address to contact for further information:
ITU-T ASN.1 Rapporteur (contact via tsb at itu.int)
ISO/IEC JTC1/SC6 ASN.1 Rapporteur (contact via secretariat at jtc1sc06.org)
Intended usage:
COMMON
Author/Change controller:
Joint ITU-T | ISO/IEC balloting procedures in accordance with ITU-T Rec. A.23
Collaboration with the International Organization for Standardization (ISO) and the
International Electrotechnical Commission (IEC) on information technology, Annex A
and ISO/IEC JTC1 Directives, Annex K.
-------------- next part --------------
MIME media type name:
application
MIME subtype name:
fastinfoset
Required parameters:
None.
Optional parameters:
None.
Encoding considerations:
XML infosets encoded as fast infoset documents will result in the production of
binary data. This MIME media type may require further encoding on transports not
capable of handling binary data.
Security considerations:
Because XML infosets encoded as fast infoset documents can carry application
defined data whose semantics is independent from that of any MIME wrapper (or
context within which the MIME wrapper is used), one should not expect to be able to
understand the semantics of the fast infoset document based on the semantics of the
MIME wrapper alone. Therefore, whenever using the "application/fastinfoset" media
type, it is strongly recommended that the security implications of the context
within which the fast infoset document is used is fully understood.
Interoperability considerations:
There are no known interoperability issues.
Published specification:
ITU-T Rec. X.891 | ISO/IEC 24824-1
Applications which use this media type:
No known applications currently use this media type.
Additional information:
Magic number(s):
A fast infoset document may begin with one of the following byte sequences:
- a byte sequence that corresponds to a UTF-8 encoded XML declaration of the
string "<?xml version='1.0' encoding='finf'", the first five bytes of which
are hexadecimal 3C 3F 78 6D 6C;
- a byte sequence that corresponds to a UTF-8 encoded XML declaration of the
string "<?xml version='1.1' encoding='finf'", the first five bytes of which
are also hexadecimal 3C 3F 78 6D 6C;
- a byte sequence of hexadecimal E0 00 00 01.
File extension(s):
*.finf
Person & email address to contact for further information:
ITU-T ASN.1 Rapporteur (contact via tsb at itu.int)
ISO/IEC JTC1/SC6 ASN.1 Rapporteur (contact via secretariat at jtc1sc06.org)
Intended usage:
COMMON
Author/Change controller:
Joint ITU-T | ISO/IEC balloting procedures in accordance with ITU-T Rec. A.23
Collaboration with the International Organization for Standardization (ISO) and the
International Electrotechnical Commission (IEC) on information technology, Annex A
and ISO/IEC JTC1 Directives, Annex K.
-------------- next part --------------
MIME media type name:
application
MIME subtype name:
fastsoap
Required parameters:
None.
Optional parameters:
"action": This parameter shall be used to identify the intent of the ASN.1 SOAP
message as specified for the "action" parameter of the W3C SOAP 1.2
"application/soap+xml" MIME media type (see W3C SOAP 1.2 Part 2, Appendix A). The
value of the "action" parameter shall be an absolute URI-reference as specified in
IETF RFC 2396. No restriction shall be placed on the specificity of the URI or that
it is resolvable.
Encoding considerations:
This media type is used to identify content that is a value of the ASN.1 Envelope
type specified in the ASN1SOAP module of ITU-T Rec. X.892 | ISO/IEC 24824-2,
encoded using Basic Aligned Packed Encoding Rule specified in ITU-T Rec. X.691 |
ISO/IEC 8825-2.
Use of this MIME media type will require additional specification if used on
transports that do not provide 8-bit binary transparency. (For the purposes of
Fast Web Services, ITU-T Rec. X.892 | ISO/IEC 24824-2, this media type is always
used with the Basic Aligned Packed Encoding Rule and with HTTP as the transport
mechanism, and no further specification is needed.)
Security considerations:
Because ASN.1 SOAP messages can carry application-defined data whose semantics is
independent from that of any MIME wrapper (or context within which the MIME wrapper
is used), one should not expect to be able to understand the semantics of the ASN.1
SOAP message based on the semantics of the MIME wrapper alone. Therefore, whenever
using the "application/fastsoap" media type, it is strongly recommended that the
security implications of the context within which the ASN.1 SOAP message is used is
fully understood. The security implications are likely to involve the specific
ASN.1 SOAP binding to an underlying protocol as well as the application-defined
semantics of the data carried in the ASN.1 SOAP message.
Interoperability considerations:
There are no known interoperability issues.
Published specification:
ITU-T Rec. X.892 | ISO/IEC 24824-2
Applications which use this media type:
No known applications that use this media type.
Additional information:
File extension(s):
ASN.1 SOAP messages are not required or expected to be stored as files.
Person & email address to contact for further information:
ITU-T ASN.1 Rapporteur (contact via tsb at itu.int)
ISO/IEC JTC1/SC6 ASN.1 Rapporteur (contact via secretariat at jtc1sc06.org)
Intended usage:
COMMON
Author/Change controller:
Joint ITU-T | ISO/IEC balloting procedures in accordance with ITU-T Rec. A.23
Collaboration with the International Organization for Standardization (ISO) and the
International Electrotechnical Commission (IEC) on information technology, Annex A
and ISO/IEC JTC1 Directives, Annex K.