[rfc-dist] RFC 4911 on Encoding Instructions for the Robust XML Encoding Rules (RXER)

rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Sat, 14 July 2007 20:26 UTC

From: "rfc-editor at rfc-editor.org"
Date: Sat, 14 Jul 2007 13:26:14 -0700
Subject: [rfc-dist] RFC 4911 on Encoding Instructions for the Robust XML Encoding Rules (RXER)
Message-ID: <20070714202614.3D764DA2B7@bosco.isi.edu>

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

        
        RFC 4911

        Title:      Encoding Instructions for the Robust 
                    XML Encoding Rules (RXER) 
        Author:     S. Legg
        Status:     Experimental
        Date:       July 2007
        Mailbox:    steven.legg at eb2bcom.com
        Pages:      91
        Characters: 178977
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-legg-xed-rxer-ei-04.txt

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

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.


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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...