RFC 4910 on Robust XML Encoding Rules (RXER) for Abstract Syntax Notation One (ASN.1)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A new Request for Comments is now available in online RFC libraries.



        

        RFC 4910



        Title:      Robust XML Encoding Rules (RXER) 

                    for Abstract Syntax Notation One (ASN.1) 

        Author:     S. Legg, D. Prager

        Status:     Experimental

        Date:       July 2007

        Mailbox:    steven.legg@eb2bcom.com, 

                    dap@austhink.com

        Pages:      80

        Characters: 182175

        Updates/Obsoletes/SeeAlso:   None



        I-D Tag:    draft-legg-xed-rxer-07.txt



        URL:        http://www.rfc-editor.org/rfc/rfc4910.txt



This document defines a set of Abstract Syntax Notation One (ASN.1)

encoding rules, called the Robust XML Encoding Rules or RXER,

that produce an Extensible Markup Language (XML) representation

for values of any given ASN.1 data type.

Rules for producing a canonical RXER encoding are also defined.  This memo defines an Experimental Protocol for the Internet community.





EXPERIMENTAL: 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.



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-REQUEST@IETF.ORG.  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.



Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 



help: ways_to_get_rfcs. For example:



        To: rfc-info@RFC-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-Manager@RFC-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-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC

Authors, for further information.





The RFC Editor Team

USC/Information Sciences Institute



...





_______________________________________________

IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux