view Side-By-Side changes
INTERNET-DRAFT S. Leggdraft-legg-xed-asd-gserei-00.txtdraft-legg-xed-asd-gserei-01.txt eB2Bcom Intended Category: Standards TrackJuly 6,November 11, 2005 Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER) Copyright (C) The Internet Society (2005). Status of this Memo By submitting this Internet-draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. By submitting this Internet-draft, I accept the provisions of Section 3 of BCP 78. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Technical discussion of this document should take place on the XED developers mailing list <xeddev@eb2bcom.com>. Please send editorial comments directly to the editor <steven.legg@eb2bcom.com>. Further information is available on the XED website: www.xmled.info. This Internet-Draft expires on6 January11 May 2006. Abstract Abstract Syntax Notation X (ASN.X) isprimarilyan Extensible Markup Language Legg Expires6 January11 May 2006 [Page 1] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005Language(XML) representation for Abstract Syntax Notation One (ASN.1) specifications. This document specifies the ASN.X representation of encoding instructions for the Generic String Encoding Rules (GSER). Legg Expires6 January11 May 2006 [Page 2] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. EncodingInstructionAssignmentList Translation. . . . . . . . . 4 4. EncodingInstruction Translation. . . . . . . . . . . . . . . . 4 4.1. ChoiceOfStringsInstruction Translation . . . . . . . . . 5 5. Security Considerations. . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations. . . . . . . . . . . . . . . . . . . . . .56 Appendix A. ASN.1 for GSER Encoding Instruction Notation . . . . . 6 Appendix B. ASN.X for GSER Encoding Instruction Notation . . . . .67 Normative References . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .89 Full Copyright Statement . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction Abstract Syntax Notation X (ASN.X) [ASN.X] isprimarilyan Extensible Markup Language (XML)[XML][XML10] representation for Abstract Syntax Notation One (ASN.1) [X.680] specifications. The ASN.X representation for the ASN.1 basic notation [X.680] [X.680-1] is described elsewhere [ASN.X]. The grammar of ASN.1 also permits the application of encoding instructions [X.680-1], through type prefixes and encoding control sections, that modify how abstract values are encoded by nominated encoding rules. The generic notation for type prefixes and encoding control sections is defined by the ASN.1 basic notation, however the notation for specific encoding instructions i.e., the EncodingInstructionAssignmentList and EncodingInstruction productions of the notation, are defined separately for each set of encoding rules using encoding instructions. This document specifies the ASN.X representation for EncodingInstructionAssignmentList and EncodingInstruction as they are defined for the Generic String Encoding Rules (GSER) [GSER][GSEREI]. ASN.X is defined in terms of rules for translating from an ASN.1 specification. This does not preclude an ASN.X document being written directly without a pre-existing ASN.1 specification, however such an ASN.X document is considered valid if and only if there exists in principle an ASN.1 specification which when translated would yield the ASN.X document. By design, an ASN.X document is also the Robust XML Encoding Rules (RXER) [RXER] encoding of an ASN.1 abstract value. The ASN.1 type definitions for such abstract values, insofar as they pertain to the Legg Expires6 January11 May 2006 [Page 3] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 ASN.1 basic notation, are provided elsewhere [ASN.X], however this document provides the ASN.1 type definitions for representing GSER encoding instructions as abstract values. These definitions appear in Appendix A. The ASN.X translation of the ASN.1 module in Appendix A is presented in Appendix B. The General Considerations of the specification for ASN.X [ASN.X] also apply here. 2. Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED" and "MAY" in this document are to be interpreted as described in, BCP 14, RFC 2119 [BCP14]. The key word "OPTIONAL" is exclusively used with its ASN.1 meaning. A reference to an ASN.1 production [X.680] (e.g., Type, NamedType) is a reference to the text in an ASN.1 specification corresponding to that production. The description of the translation of GSER encoding instructions into ASN.X makes use of definitions from the XML Information Set (Infoset) [ISET]. In particular, information item property names are presented per the Infoset, e.g., [local name]. In the sections that follow,the term "element" shall"information item" will betakenabbreviated tomean an Infoset element"item", e.g., "element informationitem and "attribute" shallitem" is abbreviated to "element item". Element items will betakenreferred tomean an Infoset attribute information item. The [namespaceby their [local name]of anyin angle brackets, e.g., "the <type> elementor attribute generated byitem" means thetranslation from an ASN.1 specification has no value unless specified otherwise.element item with the [local name] "type". 3. EncodingInstructionAssignmentList Translation As described in the specification for ASN.X [ASN.X], the translation of an EncodingControlSection for GSER is an element item with the [local name]"encodingControl-GSER"."GSER". The translation of the EncodingInstructionAssignmentList in such an EncodingControlSection determines the content of the<encodingControl-GSER> element.<GSER> element item. The EncodingInstructionAssignmentList for GSER is currently defined to be empty [GSEREI] therefore the [attributes] and [children] of the<encodingControl-GSER><GSER> element item are both empty. 4. EncodingInstruction Translation The translation of an EncodingInstruction for GSER can appear in an EncodingPrefix. The translation for an EncodingPrefix is describedby the specification for ASN.X.Legg Expires6 January11 May 2006 [Page 4] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 by the specification for ASN.X. The translation of an EncodingInstruction for GSER is the translation of the contained ChoiceOfStringsInstruction(the(currently the only defined encoding instruction for GSER). 4.1. ChoiceOfStringsInstruction Translation The translation of a ChoiceOfStringsInstruction is an element item with the [local name] "choiceOfStrings". If the ChoiceOfStringsInstruction has a PrecedenceList then an attribute item with the [local name] "precedence" SHALL be added to the [attributes] of the <choiceOfStrings>element.element item. The [normalized value] of this attribute item is the white space separated list of the RXER encodings [RXER] of the effective names [RXEREI] of the NamedType instances corresponding to the identifiers in the PrecedenceList. Example [GSER:CHOICE-OF-STRINGS PRECEDENCE utf8 visible] CHOICE { visible [RXER:NAME AS "ascii"] VisibleString, utf8 UTF8String } <type xmlns:asn1="http://xmled.info/ns/ASN.1"> <prefixed> <GSER><choiceOfStrings precedence="utf8 ascii"/></GSER> <type> <choice> <element name="ascii" identifier="visible" type="asn1:VisibleString"/> <element name="utf8" type="asn1:UTF8String"/> </choice> </type> </prefixed> </type> 5. Security Considerations The ASN.X translation of a GSER encoding instruction is semantically equivalent to the original GSER encoding instruction. The security considerations that apply to an application built from an original ASN.1 specification with GSER encoding instructions apply equally to an application built from the ASN.X translation of the ASN.1 specification.6. IANA ConsiderationsLegg Expires6 January11 May 2006 [Page 5] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 6. IANA Considerations This document has no actions for IANA. Appendix A. ASN.1 for GSER Encoding Instruction Notation This appendix is normative. GSER-EncodingInstructionNotation { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) xmled(21472) asn1(1) module(0) gser-ei-notation(2) } -- Copyright (C) The Internet Society 2005. This version of -- this ASN.1 module is part of RFC XXXX; see the RFC itself -- for full legal notices. DEFINITIONS RXER INSTRUCTIONS AUTOMATIC TAGS EXTENSIBILITY IMPLIED ::= BEGIN IMPORTS PrecedenceList FROM AbstractSyntaxNotation-X { iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) xmled(21472) asn1(1) module(0) notation(1) } ; GSER-EncodingInstruction ::= [SINGULAR-INSERTIONS] CHOICE { choiceOfStrings GSER-ChoiceOfStringsInstruction } GSER-EncodingInstructionAssignmentList ::= SEQUENCE { } GSER-ChoiceOfStringsInstruction ::= SEQUENCE { precedence [ATTRIBUTE] PrecedenceList OPTIONAL } ENCODING-CONTROL RXER SCHEMA-IDENTITY "http://xmled.info/id/ASN.1/GSER-EncodingInstructionNotation" TARGET-NAMESPACE "http://xmled.info/ns/ASN.1"EXTENSIONS-MARKEDENDAppendix B. ASN.X for GSER Encoding Instruction NotationLegg Expires6 January11 May 2006 [Page 6] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 Appendix B. ASN.X for GSER Encoding Instruction Notation This appendix is non-normative. <?xml version="1.0"?> <asn1:module xmlns:asn1="http://xmled.info/ns/ASN.1" xmlns:asnx="http://xmled.info/ns/ASN.1" name="GSER-EncodingInstructionNotation" identifier="1.3.6.1.4.1.21472.1.0.2" schemaIdentity= "http://xmled.info/id/ASN.1/GSER-EncodingInstructionNotation" xmlns:gser="http://xmled.info/ns/ASN.1" targetNamespace="http://xmled.info/ns/ASN.1"extensibilityImplied="true" extensionsMarked="true"> <!--extensibilityImplied="true"> <annotation> Copyright (C) The Internet Society 2005. This version of this ASN.X module is part of RFC XXXX; see the RFC itself for full legal notices.--></annotation> <import name="AbstractSyntaxNotation-X" identifier="1.3.6.1.4.1.21472.1.0.1" schemaIdentity= "http://xmled.info/id/ASN.1/AbstractSyntaxNotation-X" namespace="http://xmled.info/ns/ASN.1"/> <namedType name="GSER-EncodingInstruction"><type><type insertions="singular"> <choice> <element name="choiceOfStrings" type="gser:GSER-ChoiceOfStringsInstruction"/> </choice> </type> </namedType> <namedType name="GSER-EncodingInstructionAssignmentList"> <type> <sequence/> </type> </namedType> <namedType name="GSER-ChoiceOfStringsInstruction"> <type> <sequence> <optional> <attribute name="precedence" type="asnx:PrecedenceList"/></optional> </sequence> </type>Legg Expires6 January11 May 2006 [Page 7] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 </optional> </sequence> </type> </namedType> </asn1:module> Normative References [BCP14] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [GSER] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1 Types", RFC 3641, October 2003. [GSEREI] Legg, S., "Encoding Instructions for the Generic String Encoding Rules (GSER)", draft-legg-ldap-gser-ei-xx.txt, a work in progress,JulyOctober 2005. [RXER] Legg, S. and D. Prager, "Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1)", draft-legg-xed-rxer-xx.txt, a work in progress,AprilOctober 2005. [RXEREI] Legg, S., "Encoding Instructions for the Robust XML Encoding Rules (RXER)", draft-legg-xed-rxer-ei-xx.txt, a work in progress,AprilOctober 2005. [ASN.X] Legg, S., "Abstract Syntax Notation X (ASN.X)", draft-legg-xed-asd-xx.txt, a work in progress,JulyNovember 2005. [X.680] ITU-T Recommendation X.680 (07/02) | ISO/IEC8824-1:2002,8824-1, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basicnotationnotation. [X.680-1] Draft Amendment1: to1 (to ITU-T Rec. X.680 | ISO/IEC8824-1 [XML]8824-1) Support for EXTENDED-XER. [XML10] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third Edition)", W3C Recommendation, http://www.w3.org/TR/2004/REC-xml-20040204, February 2004.[XMLNS] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", http://www.w3.org/TR/1999/REC-xml-names-19990114, January 1999.[ISET] Cowan, J. and R. Tobin, "XML InformationSet",Set (Second Edition)", W3C Recommendation,http://www.w3.org/TR/2001/REC-xml- infoset-20011024, October 2001. Author's Addresshttp://www.w3.org/TR/2004/REC-xml-infoset-20040204, February 2004. Legg Expires6 January11 May 2006 [Page 8] INTERNET-DRAFT ASN.X: GSER Encoding InstructionsJuly 6,November 11, 2005 Author's Address Dr. Steven Legg eB2Bcom Suite 3, Woodhouse Corporate Centre 935 Station Street Box Hill North, Victoria 3129 AUSTRALIA Phone: +61 3 9896 7830 Fax: +61 3 9896 7801 EMail: steven.legg@eb2bcom.com Full Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any Legg Expires 11 May 2006 [Page 9] INTERNET-DRAFT ASN.X: GSER Encoding Instructions November 11, 2005 copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implementLegg Expires 6 January 2006 [Page 9] INTERNET-DRAFT ASN.X: GSER Encoding Instructions July 6, 2005this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Changes in Draft 01 The <encodingControl-GSER> element has been renamed to <GSER> and now appears as a child element of an <encodingControls> element. An insertion encoding instruction has been added to the ASN.1 for GSER Encoding Instruction Notation to remove extension ambiguity. Legg Expires6 January11 May 2006 [Page 10] ----