RFC 4792: Encoding Instructions for the Generic String Encoding Rules (GSER)
In plain English — editorial summary, not part of the RFC
Abstract Syntax Notation One (ASN.1) defines a general framework for annotating types in an ASN.1 specification with encoding instructions that alter how values of those types are encoded according to ASN.1 encoding rules. This document defines the supporting notation for encoding instructions that apply to the Generic String Encoding Rules (GSER) and, in particular, defines an encoding instruction to provide a machine-processable representation for the declaration of a GSER ChoiceOfStrings type. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4792
- Published
- January 2007
- Authors
- S. Legg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 3641
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4911Encoding Instructions for the Robust XML Encoding Rules (RXER)Current
July 2007
- RFC 4912Abstract Syntax Notation X (ASN.X)Current
July 2007
- RFC 4515Lightweight Directory Access Protocol (LDAP): String Representation of Search FiltersCurrent
June 2006
- RFC 4514Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished NamesCurrent
June 2006
- RFC 4510Lightweight Directory Access Protocol (LDAP): Technical Specification Road MapCurrent
June 2006
- RFC 5480Elliptic Curve Cryptography Subject Public Key InformationUpdated
March 2009
- RFC 4055Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) ProfileUpdated
June 2005
- RFC 3642Common Elements of Generic String Encoding Rules (GSER) EncodingsCurrent
October 2003
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?