Network Working Group Request for Comments: 4913 Category: Experimental July 2007

Similar documents
Network Working Group Request for Comments: 4792 Updates: 3641 January 2007 Category: Standards Track

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-00.

Network Working Group Internet-Draft October 27, 2007 Intended status: Experimental Expires: April 29, 2008

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-03.

Network Working Group Internet-Draft January 25, 2006 Expires: July 29, Feed Rank draft-snell-atompub-feed-index-05.txt. Status of this Memo

Network Working Group. Category: Standards Track August Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option

Network Working Group Request for Comments: 4914 Category: Experimental July 2007

Request for Comments: 5179 Category: Standards Track May 2008

Category: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs)

Category: Standards Track June Requesting Attributes by Object Class in the Lightweight Directory Access Protocol (LDAP) Status of This Memo

Request for Comments: 5208 Category: Informational May 2008

Expires: October 9, 2005 April 7, 2005

C. Martin ipath Services February A Policy Control Mechanism in IS-IS Using Administrative Tags

Request for Comments: 4633 Category: Experimental August 2006

Network Working Group. Category: Informational January 2006

Category: Standards Track June 2006

Network Working Group. Category: Standards Track June Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option

Network Working Group Request for Comments: 4424 February 2006 Updates: 4348 Category: Standards Track

Category: Experimental April BinaryTime: An Alternate Format for Representing Date and Time in ASN.1

Category: Standards Track October 2006

Expires in six months 24 October 2004 Obsoletes: RFC , , 3377, 3771

Network Working Group Request for Comments: August Address-Prefix-Based Outbound Route Filter for BGP-4

Network Working Group. Category: Informational April A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)

Network Working Group. Intended status: Standards Track Columbia U. Expires: March 5, 2009 September 1, 2008

Network Working Group. N. Williams Sun Microsystems June 2006

Category: Informational September 2004

Request for Comments: 3934 Updates: 2418 October 2004 BCP: 94 Category: Best Current Practice

Isode Limited March 2008

Request for Comments: 4680 Updates: 4346 September 2006 Category: Standards Track

Network Working Group. Cisco Systems June 2007

Category: Standards Track May Transport Layer Security Protocol Compression Methods

Request for Comments: Category: Standards Track January 2008

Network Working Group. Category: Standards Track Juniper Networks August 2008

Category: Standards Track October Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)

IETF TRUST. Legal Provisions Relating to IETF Documents. February 12, Effective Date: February 15, 2009

IETF TRUST. Legal Provisions Relating to IETF Documents. Approved November 6, Effective Date: November 10, 2008

Category: Standards Track December 2007

Request for Comments: May 2007

Request for Comments: 5010 Category: Standards Track Cisco Systems, Inc. September 2007

Category: Standards Track Cisco Systems, Inc. March 2005

Network Working Group Request for Comments: 3937 Category: Informational October 2004

Request for Comments: K. Norrman Ericsson June 2006

Category: Standards Track Cisco Systems, Inc January The Secure Shell (SSH) Session Channel Break Extension

Network Working Group. February 2005

Updates: 2409 May 2005 Category: Standards Track. Algorithms for Internet Key Exchange version 1 (IKEv1)

Network Working Group. Category: Informational May OSPF Database Exchange Summary List Optimization

Network Working Group Request for Comments: Cisco Systems, Inc. December 2005

Network Working Group. Category: Standards Track July 2007

Intended status: Standards Track August 15, 2008 Expires: February 16, 2009

Request for Comments: 4142 Category: Standards Track Nine by Nine November 2005

Category: Standards Track Microsoft May 2004

Network Working Group Request for Comments: 4869 Category: Informational May Suite B Cryptographic Suites for IPsec. Status of This Memo

Network Working Group. Category: Standards Track Cisco Systems May 2007

Category: Standards Track October 2006

Network Working Group Request for Comments: 5235 January 2008 Obsoletes: 3685 Category: Standards Track

Network Working Group. February Media Gateway Control Protocol (MGCP) Redirect and Reset Package

Request for Comments: 4715 Category: Informational NTT November 2006

Category: Standards Track Cisco H. Tschofenig Nokia Siemens Networks August 2008

Category: Best Current Practice February Early IANA Allocation of Standards Track Code Points

Network Working Group Request for Comments: 5138 Category: Informational February 2008

Network Working Group. BCP: 131 July 2007 Category: Best Current Practice

Network Working Group Request for Comments: 4573 Category: Standard Track July MIME Type Registration for RTP Payload Format for H.

Network Working Group Request for Comments: 4143 Category: Standards Track Brandenburg November 2005

February T11 Network Address Authority (NAA) Naming Format for iscsi Node Names

Network Working Group Request for Comments: Cisco Systems, Inc. June 2006

Request for Comments: 4393 Category: Standards Track March MIME Type Registrations for 3GPP2 Multimedia Files

Jabber, Inc. August 20, 2004

Category: Experimental June 2006

Request for Comments: 4571 Category: Standards Track July 2006

Network Working Group Request for Comments: 4162 Category: Standards Track KISA August 2005

Request for Comments: 3861 Category: Standards Track August 2004

Request for Comments: 5115 Category: Standards Track UCL January Telephony Routing over IP (TRIP) Attribute for Resource Priority

Network Working Group Request for Comments: A. Zinin Alcatel-Lucent March 2007

Request for Comments: 3905 Category: Informational September A Template for IETF Patent Disclosures and Licensing Declarations

Network Working Group. Updates: 5228 January 2008 Category: Standards Track

Category: Standards Track March Extensible Provisioning Protocol (EPP) Transport Over TCP

Network Working Group Request for Comments: 4432 March 2006 Category: Standards Track

Network Working Group. Category: Informational October 2005

Network Working Group. Category: Standards Track June 2005

Request for Comments: 3968 Updates: 3427 December 2004 BCP: 98 Category: Best Current Practice

Request for Comments: 4759 Category: Standards Track Neustar Inc. L. Conroy Roke Manor Research November 2006

vcard Extensions for Instant Messaging (IM)

Category: Standards Track Juniper Networks E. Rosen Cisco Systems, Inc. August MPLS Upstream Label Assignment and Context-Specific Label Space

Network Working Group. Category: Informational SPARTA, Inc. S. Crocker Shinkuro Inc. S. Krishnaswamy SPARTA, Inc. August 2007

Network Working Group Request for Comments: 4242 Category: Standards Track University of Southampton B. Volz Cisco Systems, Inc.

Network Working Group Request for Comments: 4603 Category: Informational Cisco Systems July Additional Values for the NAS-Port-Type Attribute

Request for Comments: 5079 Category: Standards Track December Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)

Request for Comments: 4315 December 2005 Obsoletes: 2359 Category: Standards Track. Internet Message Access Protocol (IMAP) - UIDPLUS extension

Network Working Group Request for Comments: 4147 Category: Informational August Proposed Changes to the Format of the IANA IPv6 Registry

September The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry. Status of This Memo

Network Working Group. Category: Standards Track Samsung S. Kumar Tech Mahindra Ltd S. Madanapalli Samsung May 2008

HIIT L. Eggert Nokia April Host Identity Protocol (HIP) Registration Extension

Category: Standards Track LabN Consulting, LLC July 2008

Request for Comments: 4509 Category: Standards Track May Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)

Request for Comments: January 2007

Network Working Group. J. Lee Samsung Electronics T. Iwata Nagoya University August 2006

Network Working Group Request for Comments: December 2004

Category: Standards Track Redback Networks June 2008

Request for Comments: 4255 Category: Standards Track SPARTA January Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints

Category: Informational Woven Systems May 2008

Transcription:

Network Working Group S. Legg Request for Comments: 4913 eb2bcom Category: Experimental July 2007 Status of This Memo Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER) This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract Abstract Syntax Notation X (ASN.X) is an Extensible Markup Language (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). Table of Contents 1. Introduction...2 2. Conventions...2 3. EncodingInstructionAssignmentList Translation...3 4. EncodingInstruction Translation...3 4.1. ChoiceOfStringsInstruction Translation...3 5. Security Considerations...4 6. Normative References...4 Appendix A. ASN.1 for GSER Encoding Instruction Notation...6 Appendix B. ASN.X for GSER Encoding Instruction Notation...7 Legg Experimental [Page 1]

1. Introduction Abstract Syntax Notation X (ASN.X) [ASN.X] is an Extensible Markup Language (XML) [XML10][XML11] 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 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 EncodingInstruction and EncodingInstructionAssignmentList 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 module being written directly without a pre-existing ASN.1 module; however, such an ASN.X module is considered valid if and only if there exists, in principle, an ASN.1 module that when translated would yield the ASN.X module. By design, an ASN.X module is also the Robust XML Encoding Rules (RXER) [RXER] encoding of an ASN.1 value. The ASN.1 type definitions for such values, insofar as they pertain to the 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. Legg Experimental [Page 2]

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) [INFOSET]. In particular, information item property names follow the Infoset convention of being shown in square brackets, e.g., [local name]. Literal values of Infoset properties are enclosed in double quotes; however, the double quotes are not part of the property values. In the sections that follow, "information item" will be abbreviated to "item", e.g., "element information item" is abbreviated to "element item". Element items will be referred to by their [local name] in angle brackets, e.g., "the <type> element item" means the 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] "GSER". The translation of the EncodingInstructionAssignmentList in such an EncodingControlSection determines the content of the <GSER> element item. The EncodingInstructionAssignmentList for GSER is currently defined to be empty [GSEREI]; therefore, the [attributes] and [children] of the <GSER> element item are both empty. 4. EncodingInstruction Translation The translation of an EncodingInstruction for GSER can appear in the translation of an EncodingPrefix. The translation for an EncodingPrefix is described by the specification for ASN.X. The translation of an EncodingInstruction for GSER is the translation of the ChoiceOfStringsInstruction in the EncodingInstruction (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 an AlternativesPrecedence, then an attribute item with the [local name] "precedence" SHALL be added to the [attributes] of the <choiceofstrings> element item. The [normalized value] of this attribute item is the white space separated list of qualified names for the expanded names [XMLNS10] of Legg Experimental [Page 3]

the NamedType instances (see [RXEREI]) corresponding to the identifiers nested in the PrecedenceList in the AlternativesPrecedence. Example [GSER:CHOICE-OF-STRINGS PRECEDENCE utf8 visible] CHOICE { visible [RXER:NAME "ascii"] VisibleString, utf8 UTF8String } <type xmlns:asnx="urn:ietf:params:xml:ns:asnx"> <prefixed> <GSER><choiceOfStrings precedence="utf8 ascii"/></gser> <type> <choice> <element name="ascii" identifier="visible" type="asnx:visiblestring"/> <element name="utf8" type="asnx:utf8string"/> </choice> </prefixed> 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. See the main specification for ASN.X [ASN.X] for security considerations related to ASN.X modules. 6. Normative References [BCP14] [GSER] [GSEREI] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. Legg, S., "Generic String Encoding Rules (GSER) for ASN.1 Types", RFC 3641, October 2003. Legg, S., "Encoding Instructions for the Generic String Encoding Rules (GSER)", RFC 4792, January 2007. Legg Experimental [Page 4]

[RXER] [RXEREI] Legg, S. and D. Prager, "Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1)", RFC 4910, July 2007. Legg, S., "Encoding Instructions for the Robust XML Encoding Rules (RXER)", RFC 4911, July 2007. [ASN.X] Legg, S., "Abstract Syntax Notation X (ASN.X)", RFC 4912, July 2007. [X.680] ITU-T Recommendation X.680 (07/02) ISO/IEC 8824-1, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation. [X.680-1] ITU-T Recommendation X.680 (2002) Amendment 1 (10/03) ISO/IEC 8824-1:2002/Amd 1:2004, Support for EXTENDED-XER. [XML10] [XML11] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth Edition)", W3C Recommendation, http://www.w3.org/tr/2006/rec-xml-20060816, August 2006. Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., Yergeau, F., and J. Cowan, "Extensible Markup Language (XML) 1.1 (Second Edition)", W3C Recommendation, http://www.w3.org/tr/2006/rec-xml11-20060816, August 2006. [XMLNS10] Bray, T., Hollander, D., Layman, A., and R. Tobin, "Namespaces in XML 1.0 (Second Edition)", W3C Recommendation, http://www.w3.org/tr/2006/rec-xml-names-20060816, August 2006. [INFOSET] Cowan, J. and R. Tobin, "XML Information Set (Second Edition)", W3C Recommendation, http://www.w3.org/tr/2004/rec-xml-infoset-20040204, February 2004. Legg Experimental [Page 5]

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) asnx(1) module(0) gser-ei-notation(2) } -- Copyright (C) The IETF Trust (2007). This version of -- this ASN.1 module is part of RFC 4913; see the RFC itself -- for full legal notices. -- -- Regarding this ASN.1 module or any portion of it, the author -- makes no guarantees and is not responsible for any damage -- resulting from its use. The author grants irrevocable permission -- to anyone to use, modify, and distribute it in any way that does -- not diminish the rights of anyone else to use, modify, and -- distribute it, provided that redistributed derivative works do -- not contain misleading author or version information. -- Derivative works need not be licensed under similar terms. 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) asnx(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 "urn:oid:1.3.6.1.4.1.21472.1.0.2" Legg Experimental [Page 6]

END TARGET-NAMESPACE "urn:ietf:params:xml:ns:asnx" PREFIX "asnx" Appendix B. ASN.X for GSER Encoding Instruction Notation This appendix is non-normative. <?xml version="1.0"?> <asnx:module xmlns:asnx="urn:ietf:params:xml:ns:asnx" name="gser-encodinginstructionnotation" identifier="1.3.6.1.4.1.21472.1.0.2" schemaidentity="urn:oid:1.3.6.1.4.1.21472.1.0.2" targetnamespace="urn:ietf:params:xml:ns:asnx" targetprefix="asnx" extensibilityimplied="true"> <annotation> Copyright (C) The IETF Trust (2007). This version of this ASN.X module is part of RFC 4913; see the RFC itself for full legal notices. Regarding this ASN.X module or any portion of it, the author makes no guarantees and is not responsible for any damage resulting from its use. The author grants irrevocable permission to anyone to use, modify, and distribute it in any way that does not diminish the rights of anyone else to use, modify, and distribute it, provided that redistributed derivative works do not contain misleading author or version information. Derivative works need not be licensed under similar terms. </annotation> <import name="abstractsyntaxnotation-x" identifier="1.3.6.1.4.1.21472.1.0.1" schemaidentity="urn:oid:1.3.6.1.4.1.21472.1.0.1" namespace="urn:ietf:params:xml:ns:asnx"/> <namedtype name="gser-encodinginstruction"> <type> <choice insertions="singular"> <element name="choiceofstrings" type="asnx:gser-choiceofstringsinstruction"/> </choice> </namedtype> <namedtype name="gser-encodinginstructionassignmentlist"> <type> Legg Experimental [Page 7]

<sequence/> </namedtype> <namedtype name="gser-choiceofstringsinstruction"> <type> <sequence> <optional> <attribute name="precedence" type="asnx:precedencelist"/> </optional> </sequence> </namedtype> </asnx:module> 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 Legg Experimental [Page 8]

Full Copyright Statement Copyright (C) The IETF Trust (2007). 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, THE IETF TRUST 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 copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Legg Experimental [Page 9]