RFC 4391 on Transmission of IP over InfiniBand (IPoIB)

rfc-editor@rfc-editor.org Fri, 07 April 2006 17:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRv1b-0002TU-4Q; Fri, 07 Apr 2006 13:45:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FRv10-0000pD-4u; Fri, 07 Apr 2006 13:44:58 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FRume-0005Lo-3j; Fri, 07 Apr 2006 13:30:09 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k37HU787030452; Fri, 7 Apr 2006 10:30:07 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k37HU7rw030451; Fri, 7 Apr 2006 10:30:07 -0700
Date: Fri, 07 Apr 2006 10:30:07 -0700
Message-Id: <200604071730.k37HU7rw030451@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: ipoverib@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4391 on Transmission of IP over InfiniBand (IPoIB)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
Status: O

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

        
        RFC 4391

        Title:      Transmission of IP over InfiniBand 
                    (IPoIB) 
        Author:     J. Chu, V. Kashyap
        Status:     Standards Track
        Date:       April 2006
        Mailbox:    jerry.chu@sun.com, 
                    vivk@us.ibm.com
        Pages:      21
        Characters: 45858
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipoib-ip-over-infiniband-09.txt

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

This document specifies a method for encapsulating and transmitting
IPv4/IPv6 and Address Resolution Protocol (ARP) packets over
InfiniBand (IB).  It describes the link-layer address to be used when
resolving the IP addresses in IP over InfiniBand (IPoIB) subnets.
The document also describes the mapping from IP multicast addresses
to InfiniBand multicast addresses.  In addition, this document
defines the setup and configuration of IPoIB links.  [STANDARDS TRACK]

This document is a product of the IP over InfiniBand
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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.

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

...



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