Browse Prior Art Database

Common Elements of Generic String Encoding Rules (GSER) Encodings (RFC3642)

IP.com Disclosure Number: IPCOM000020037D
Original Publication Date: 2003-Oct-01
Included in the Prior Art Database: 2003-Oct-21
Document File: 14 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Legg: AUTHOR

Abstract

The Generic String Encoding Rules (GSER) describe a human readable text encoding for an Abstract Syntax Notation One (ASN.1) value of any ASN.1 type. Specifications making use of GSER may wish to provide an equivalent Augmented Backus-Naur Form (ABNF) description of the GSER encoding for a particular ASN.1 type as a convenience for implementors. This document supports such specifications by providing equivalent ABNF for the GSER encodings for ASN.1 types that commonly occur in Lightweight Directory Access Protocol (LDAP) syntaxes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group S. Legg

Request for Comments: 3642 Adacel Technologies

Category: Informational October 2003

Common Elements of Generic String Encoding Rules (GSER) Encodings

Status of this Memo

This memo provides information for the Internet community. It does

not specify an Internet standard of any kind. Distribution of this

memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

The Generic String Encoding Rules (GSER) describe a human readable

text encoding for an Abstract Syntax Notation One (ASN.1) value of

any ASN.1 type. Specifications making use of GSER may wish to

provide an equivalent Augmented Backus-Naur Form (ABNF) description

of the GSER encoding for a particular ASN.1 type as a convenience for

implementors. This document supports such specifications by

providing equivalent ABNF for the GSER encodings for ASN.1 types that

commonly occur in Lightweight Directory Access Protocol (LDAP)

syntaxes.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2

2. Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . 2

3. Separators . . . . . . . . . . . . . . . . . . . . . . . . . . 2

4. ASN.1 Built-in Types . . . . . . . . . . . . . . . . . . . . . 2

5. ASN.1 Restricted String Types. . . . . . . . . . . . . . . . . 7

6. Directory ASN.1 Types. . . . . . . . . . . . . . . . . . . . . 9

7. Security Considerations. . . . . . . . . . . . . . . . . . . . 10

8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10

8.1. Normative References . . . . . . . . . . . . . . . . . . 10

8.2. Informative References . . . . . . . . . . . . . . . . . 11

9. Intellectual Property Notice . . . . . . . . . . . . . . . . . 12

10. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 12

11. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 13

Legg Informational [Page 1]

RFC 3642 Common Elements of GSER Encodings October 2003

1. Introduction

The Generic String Encoding Rules (GSER) [7] define a human readable

text encoding, based on ASN.1 [8] value notation, for an ASN.1 value

of any ASN.1 type. Specifications making use of GSER may wish to

provide a non-normative equivalent ABNF [3] description of the GSER

encoding for a particular ASN.1 type as a convenience for

implementors unfamiliar with ASN.1. This document supports such

specifications by providing equivalent ABNF for the GSER encodings

for ASN.1 types that commonly occur in LDAP [10] or X.500 [11]

attribute and assertion syntaxes, as well as equivalent ABNF for the

GSER encodings for the ASN.1 built-in types.

The ABNF given in this document does not replace or alter GSER in any

way. If there is a discrepancy between the ABNF specified here and

the encoding defined by GSER [7], then GSER is to be taken as

definitive.

2. Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are

to be interp...