I've attached an IETF draft XML Encryption media-type registration; please
publish it. Also, this email serves to instantiate the two week discussion
period on "ietf-types(_at_)iana(_dot_)org" .
The expected course of advancement for this specification is:
1. Publication of an IETF Draft as specified:
ftp://ftp.ietf.org/ietf/1id-guidelines.txt
2. I will notify the security and application area directors.
3. Request publication as an Informational RFC as specified:
ftp://ftp.isi.edu/in-notes/rfc-editor/instructions2authors.txt
4. Ensure IANA is aware of the publication and posts the registration as
specified:
ftp://ftp.isi.edu/in-notes/rfc2048.txt
The changes in this specification since the last version [1] discussed on
"ietf-xml-mime(_at_)imc(_dot_)org" include:
1. There is no redundant type parameter for the encrypted object.
2. The type only applies to XML instances in which a XML Encryption element
is the root document.
3. Non-normative examples are enumerated for addressing the description of
documents in which XML Encryption elements occur as non-root nodes, " XML
documents which contain XENC element types in places other than the root
element can be described using facilities such as [XML-schema] or
[StLaurent]."
[1] http://lists.w3.org/Archives/Public/xml-encryption/2002May/0040.html
Thank you.
--
Joseph Reagle Jr. http://www.w3.org/People/Reagle/
W3C Policy Analyst mailto:reagle(_at_)w3(_dot_)org
IETF/W3C XML-Signature Co-Chair http://www.w3.org/Signature/
W3C XML Encryption Chair http://www.w3.org/Encryption/2001/
draft-reagle-xenc-mediatype-00.txt
Description: Text document