One document matched: draft-narten-canonical-ordering-00.txt

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


	RFC 2469:

        Title:	    A Caution On The Canonical Ordering Of Link-Layer 
		    Addresses
	Author(s):  T. Narten, C. Burton
	Status:     Informational
	Date:       December 1998
        Mailbox:    narten@raleigh.ibm.com, burton@rtp.vnet.ibm.com
	Pages:      5
        Characters: 9948
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-narten-canonical-ordering-00.txt

	        
        URL:        ftp://ftp.isi.edu/in-notes/rfc2469.txt


Protocols such as ARP and Neighbor Discovery have data fields that
contain link-layer addresses. In order to interoperate properly, a
sender setting such a field must insure that the receiver extracts
those bits and interprets them correctly.  In most cases, such fields
must be in "canonical form".  Unfortunately, not all LAN adaptors are
consistent in their use of canonical form, and implementations may
need to explicitly bit swap individual bytes in order to obtain the
correct format.  This document provides information to implementors to
help them avoid the pitfall of using non-canonical forms when
canonical forms are required.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.echo 
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.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <981203163404.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc2469

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc2469.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <981203163404.RFC@RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--