[rfc-dist] RFC 3831 on Transmission of IPv6 Packets over Fibre Channel

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Jul 23 17:45:06 PDT 2004


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


        RFC 3831

        Title:      Transmission of IPv6 Packets over Fibre Channel
        Author(s):  C. DeSanti
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    cds at cisco.com
        Pages:      24
        Characters: 53328
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-imss-ipv6-over-fibre-channel-02.txt

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


This document specifies the way of encapsulating IPv6 packets over
Fibre Channel, and the method of forming IPv6 link-local addresses
and statelessly autoconfigured addresses on Fibre Channel networks.

This document is a product of the Internet and Management Support for
Storage 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 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.echo 
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.


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.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list