RFC 4911: Encoding Instructions for the Robust XML Encoding Rules (RXER)
In plain English — editorial summary, not part of the RFC
This document defines encoding instructions that may be used in an Abstract Syntax Notation One (ASN.1) specification to alter how ASN.1 values are encoded by the Robust XML Encoding Rules (RXER) and Canonical Robust XML Encoding Rules (CRXER), for example, to encode a component of an ASN.1 value as an Extensible Markup Language (XML) attribute rather than as a child element. Some of these encoding instructions also affect how an ASN.1 specification is translated into an Abstract Syntax Notation X (ASN.X) specification. Encoding instructions that allow an ASN.1 specification to reference definitions in other XML schema languages are also defined. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC4911
- Published
- July 2007
- Authors
- S. Legg
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 91
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4912Abstract Syntax Notation X (ASN.X)Current
July 2007
- RFC 4910Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1)Current
July 2007
- RFC 4913Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the Generic String Encoding Rules (GSER)Current
July 2007
- RFC 4914Abstract Syntax Notation X (ASN.X) Representation of Encoding Instructions for the XML Encoding Rules (XER)Current
July 2007
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 4792Encoding Instructions for the Generic String Encoding Rules (GSER)Current
January 2007
- RFC 4744Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)Updated
December 2006
- RFC 4743Using NETCONF over the Simple Object Access Protocol (SOAP)Updated
December 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?