RFC 4792 on Encoding Instructions for the Generic String Encoding Rules (GSER)

Thread: RFC 4792 on Encoding Instructions for the Generic String Encoding Rules (GSER)

Search this list only Search all lists
RFC 4792 on Encoding Instructions for the Generic String Encoding Rules (GSER)
	2007-01-24 20:19:54
A new Request for Comments is now available in online RFC libraries. RFC 4792 Title: Encoding Instructions for the Generic String Encoding Rules (GSER) Author: S. Legg Status: Standards Track Date: January 2007 Mailbox: steven.leggeb2bcom.com Pages: 9 Characters: 17637 Updates: RFC3641 See-Also: I-D Tag: draft-legg-ldap-gser-ei-02.txt URL: http://www.rfc-editor.org/rfc/rfc4792.txt 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] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUESTIETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUESTRFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-infoRFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-infoRFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-ManagerRFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITORRFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ rfc-dist mailing list rfc-distmailman.rfc-editor.org http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org