[rfc-dist] RFC 3697 on IPv6 Flow Label Specification

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Tue, 02 Mar 2004 15:30:18 -0800


--NextPart


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


        RFC 3697

        Title:      IPv6 Flow Label Specification
        Author(s):  J. Rajahalme, A. Conta, B. Carpenter, S. Deering
        Status:     Standards Track
        Date:       March 2004
        Mailbox:    jarno.rajahalme@nokia.com, aconta@txc.com,
                    brc@zurich.ibm.com
        Pages:      9
        Characters: 21296
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipv6-flow-label-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3697.txt


This document specifies the IPv6 Flow Label field and the minimum
requirements for IPv6 source nodes labeling flows, IPv6 nodes
forwarding labeled packets, and flow state establishment methods.
Even when mentioned as examples of possible uses of the flow labeling,
more detailed requirements for specific use cases are out of scope for
this document.

The usage of the Flow Label field enables efficient IPv6 flow
classification based only on IPv6 main header fields in fixed
positions.

This document is a product of the IP Version 6 Working Group of the
IETF.

This is now a Proposed Standard Protocol.

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-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 Sandy Ginoza
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: <040302152901.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3697

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

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

--OtherAccess--
--NextPart--