From exim@www1.ietf.org  Tue May  4 11:33:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08676
	for <ipoverib-archive@odin.ietf.org>; Tue, 4 May 2004 11:33:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1s1-0004na-0u
	for ipoverib-archive@odin.ietf.org; Tue, 04 May 2004 11:30:09 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i44FU9G1018447
	for ipoverib-archive@odin.ietf.org; Tue, 4 May 2004 11:30:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1oa-0003gp-QX
	for ipoverib-web-archive@optimus.ietf.org; Tue, 04 May 2004 11:26:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08137
	for <ipoverib-web-archive@ietf.org>; Tue, 4 May 2004 11:26:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL1oZ-0002yc-UP
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:26:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL1nZ-0002tI-00
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:25:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL1mb-0002nB-00
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:24:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1hE-0001Xp-TA; Tue, 04 May 2004 11:19:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1d7-0000Fg-QV
	for ipoverib@optimus.ietf.org; Tue, 04 May 2004 11:14:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07541
	for <ipoverib@ietf.org>; Tue, 4 May 2004 11:14:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL1d6-00020u-Vw
	for ipoverib@ietf.org; Tue, 04 May 2004 11:14:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL1cD-0001wE-00
	for ipoverib@ietf.org; Tue, 04 May 2004 11:13:49 -0400
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL1bl-0001qx-00
	for ipoverib@ietf.org; Tue, 04 May 2004 11:13:21 -0400
Received: from mobilebill (c-24-6-192-177.client.comcast.net[24.6.192.177])
          by comcast.net (sccrmhc11) with SMTP
          id <2004050415125001100daroue>; Tue, 4 May 2004 15:12:50 +0000
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Date: Tue, 4 May 2004 08:12:35 -0700
Message-ID: <000501c431ea$3eb8c020$0902a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Subject: [Ipoverib] 60th IETF Meeting in San Diego
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=CLICK_BELOW autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

It is time to start taking scheduling requests for the 60th IETF
meeting.

I would be interested in hearing implementation reports on IPoIB
implementations, MIB updates, DHCP and any other topics that people
would like to present.  There is also an interop test for the end of
August being planned - more details when they are available.

If you have an IPoIB implementation and would like a slot, please
contact me and I will get you time on the schedule

Bill

I am training for my first endurance event... and SAVING lives click
here to find out more!
http://www.teamintraining.org/participant/strahm-163543
 



_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Tue May  4 11:34:42 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08819
	for <ipoverib-archive@odin.ietf.org>; Tue, 4 May 2004 11:34:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1u9-0005Ix-8F
	for ipoverib-archive@odin.ietf.org; Tue, 04 May 2004 11:32:21 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i44FWLeH020386
	for ipoverib-archive@odin.ietf.org; Tue, 4 May 2004 11:32:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1rs-0004a4-KV
	for ipoverib-web-archive@optimus.ietf.org; Tue, 04 May 2004 11:30:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08400
	for <ipoverib-web-archive@ietf.org>; Tue, 4 May 2004 11:29:58 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL1rr-0003Ku-NR
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:29:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL1qu-0003EA-00
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:29:01 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL1q3-00038B-00
	for ipoverib-web-archive@ietf.org; Tue, 04 May 2004 11:28:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1m5-0002VF-Tl; Tue, 04 May 2004 11:24:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL1f2-00010d-8t
	for ipoverib@optimus.ietf.org; Tue, 04 May 2004 11:16:44 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07652
	for <ipoverib@ietf.org>; Tue, 4 May 2004 11:16:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL1f0-0002BJ-O8
	for ipoverib@ietf.org; Tue, 04 May 2004 11:16:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL1eD-00027d-00
	for ipoverib@ietf.org; Tue, 04 May 2004 11:15:54 -0400
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL1dM-0001xI-00
	for ipoverib@ietf.org; Tue, 04 May 2004 11:15:00 -0400
Received: from mobilebill (c-24-6-192-177.client.comcast.net[24.6.192.177])
          by comcast.net (sccrmhc11) with SMTP
          id <2004050415143001100d8ppge>; Tue, 4 May 2004 15:14:30 +0000
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Subject: RE: [Ipoverib] Last Call for DHCP Draft
Date: Tue, 4 May 2004 08:14:14 -0700
Message-ID: <000701c431ea$79e007d0$0902a8c0@mobilebill>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
In-Reply-To: <20040329174740.13983.qmail@webmail-2-2.mesa1.secureserver.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Content-Transfer-Encoding: 7bit
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=CLICK_BELOW autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

In looking over my mail - I realize that I have never officially closed
this WG Last call.  I have received no issues with this draft and will
ask the Margaret (Our IESG AD) to take to the IESG.

Bill

I am training for my first endurance event... and SAVING lives click
here to find out more!
http://www.teamintraining.org/participant/strahm-163543
 

-----Original Message-----
From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf
Of bill@strahm.net
Sent: Monday, March 29, 2004 9:48 AM
To: ipoverib@ietf.org
Subject: [Ipoverib] Last Call for DHCP Draft


Thank you all for helping get the IP Encapsulation drafts to the IESG.
Now that they are in the IESG's hands Jerry and I would like to start
the Working Group Last Call for DHCP over Infiniband.

Please take the next two weeks to review
http://www.ietf.org/internet-drafts/draft-ietf-ipoib-dhcp-over-infiniban
d-06.txt
and return comments to the working group so we can pass this document
off to the IESG as well.

Thank you
Bill & Jerry
IP over IB co-chairs

_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib



_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Thu May  6 13:27:52 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04630
	for <ipoverib-archive@odin.ietf.org>; Thu, 6 May 2004 13:27:52 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLmP9-00049I-N3
	for ipoverib-archive@odin.ietf.org; Thu, 06 May 2004 13:11:27 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46HBRxA015938
	for ipoverib-archive@odin.ietf.org; Thu, 6 May 2004 13:11:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLloG-0005V2-MP
	for ipoverib-web-archive@optimus.ietf.org; Thu, 06 May 2004 12:33:20 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27401
	for <ipoverib-web-archive@ietf.org>; Thu, 6 May 2004 12:33:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLloF-0006hg-6D
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 12:33:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLlkB-0005Gd-00
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 12:29:07 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLlhY-00043a-01
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 12:26:24 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1BLlXp-0001CJ-PX
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 12:16:21 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLkv5-0008Gr-8q; Thu, 06 May 2004 11:36:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLklb-0003IH-5M
	for ipoverib@optimus.ietf.org; Thu, 06 May 2004 11:26:31 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20038;
	Thu, 6 May 2004 11:26:28 -0400 (EDT)
Message-Id: <200405061526.LAA20038@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: ipoverib@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 06 May 2004 11:26:28 -0400
Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-04.txt
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP over InfiniBand Working Group of the IETF.

	Title		: IP over InfiniBand(IPoIB) Architecture
	Author(s)	: V. Kashyap
	Filename	: draft-ietf-ipoib-architecture-04.txt
	Pages		: 24
	Date		: 2004-5-4
	
	InfiniBand is a high speed, channel based interconnect between
        systems and devices.

        This document presents an overview of the InfiniBand
        architecture. It further describes the requirements and
        guidelines for the transmission of IP over InfiniBand.
        Discussions in this document are applicable to both IPv4 and
        IPv6 unless explicitly specified. The encapsulation of IP over
        InfiniBand and the mechanism for IP address resolution on IB
        fabrics are covered in other documents.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ipoib-architecture-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ipoib-architecture-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-5-6113402.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipoib-architecture-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ipoib-architecture-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-5-6113402.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Thu May  6 14:50:23 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10673
	for <ipoverib-archive@odin.ietf.org>; Thu, 6 May 2004 14:50:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnnK-0007cK-Tm
	for ipoverib-archive@odin.ietf.org; Thu, 06 May 2004 14:40:31 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46IeU5j029276
	for ipoverib-archive@odin.ietf.org; Thu, 6 May 2004 14:40:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnh4-0005fT-Ej
	for ipoverib-web-archive@optimus.ietf.org; Thu, 06 May 2004 14:34:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09735
	for <ipoverib-web-archive@ietf.org>; Thu, 6 May 2004 14:33:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnh1-0004ZY-U9
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 14:33:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLng2-00049g-00
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 14:32:59 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnf5-0003k6-00
	for ipoverib-web-archive@ietf.org; Thu, 06 May 2004 14:31:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnYN-0001u3-1s; Thu, 06 May 2004 14:25:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnJk-00044k-GJ
	for ipoverib@optimus.ietf.org; Thu, 06 May 2004 14:09:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08474
	for <ipoverib@ietf.org>; Thu, 6 May 2004 14:09:53 -0400 (EDT)
From: bill@strahm.net
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnJh-0002PQ-VZ
	for ipoverib@ietf.org; Thu, 06 May 2004 14:09:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnIi-0001yj-00
	for ipoverib@ietf.org; Thu, 06 May 2004 14:08:52 -0400
Received: from smtpout-1-1c.secureserver.net ([64.202.165.65])
	by ietf-mx with smtp (Exim 4.12)
	id 1BLnHi-00019w-00
	for ipoverib@ietf.org; Thu, 06 May 2004 14:07:50 -0400
Received: (qmail 14093 invoked from network); 6 May 2004 18:07:27 -0000
Received: from unknown (HELO webmail-2-6.mesa1.secureserver.net) (64.202.166.93)
  by smtpout-1-1c.secureserver.net with SMTP; 6 May 2004 18:07:27 -0000
Received: (qmail 5059 invoked by uid 99); 6 May 2004 18:07:20 -0000
Message-ID: <20040506180720.5058.qmail@webmail-2-6.mesa1.secureserver.net>
Date: Thu,  6 May 2004 11:07:20 -0700
Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-04.txt
To: ipoverib@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

Vivek has made a few clarifying chagnes around the phrases that IPv6 addresses are used as IB addresses that the
IESG asked for.

Please look this over and make any comments  by next Thursday (May 13th) so it can be resubmitted back to the
IESG for approval

Bill Strahm
co-chair
> -------- Original Message --------
> Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-04.txt
> From: Internet-Drafts@ietf.org
> Date: Thu, May 06, 2004 8:26 am
> To: i-d-announce@ietf.org
> Cc: ipoverib@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP over InfiniBand Working Group of
> the IETF.
>
> 	Title		: IP over InfiniBand(IPoIB) Architecture
> 	Author(s)	: V. Kashyap
> 	Filename	: draft-ietf-ipoib-architecture-04.txt
> 	Pages		: 24
> 	Date		: 2004-5-4
>
> 	InfiniBand is a high speed, channel based interconnect between
>         systems and devices.
>
>         This document presents an overview of the InfiniBand
>         architecture. It further describes the requirements and
>         guidelines for the transmission of IP over InfiniBand.
>         Discussions in this document are applicable to both IPv4 and
>         IPv6 unless explicitly specified. The encapsulation of IP over
>         InfiniBand and the mechanism for IP address resolution on IB
>         fabrics are covered in other documents.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-04.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-ipoib-architecture-04.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-ipoib-architecture-04.txt".
>
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>

_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Tue May 18 00:34:46 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28945
	for <ipoverib-archive@odin.ietf.org>; Tue, 18 May 2004 00:34:46 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPwID-0007J5-8O
	for ipoverib-archive@odin.ietf.org; Tue, 18 May 2004 00:33:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4I4XTHR028087
	for ipoverib-archive@odin.ietf.org; Tue, 18 May 2004 00:33:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPwGX-0006yg-6t
	for ipoverib-web-archive@optimus.ietf.org; Tue, 18 May 2004 00:31:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28837
	for <ipoverib-web-archive@ietf.org>; Tue, 18 May 2004 00:31:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BPwGU-0006Wv-Kg
	for ipoverib-web-archive@ietf.org; Tue, 18 May 2004 00:31:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BPwFe-0006Ao-00
	for ipoverib-web-archive@ietf.org; Tue, 18 May 2004 00:30:50 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BPwEy-0005oV-00
	for ipoverib-web-archive@ietf.org; Tue, 18 May 2004 00:30:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPw85-0004kg-FH; Tue, 18 May 2004 00:23:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BPqdT-00057B-Oy
	for ipoverib@optimus.ietf.org; Mon, 17 May 2004 18:31:03 -0400
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09520
	for <ipoverib@odin.ietf.org>; Mon, 17 May 2004 18:30:59 -0400 (EDT)
Received: from nobody by optimus.ietf.org with local (Exim 4.20)
	id 1BPqN3-00032x-Sp; Mon, 17 May 2004 18:14:05 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>,
        ipoib mailing list <ipoverib@ietf.org>,
        ipoib chair <jerry.chu@sun.com>, ipoib chair <bill@strahm.net>
Message-Id: <E1BPqN3-00032x-Sp@optimus.ietf.org>
Date: Mon, 17 May 2004 18:14:05 -0400
Subject: [Ipoverib] Document Action: 'IP over InfiniBand(IPoIB) Architecture' to
 Informational RFC
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

The IESG has approved the following document:

- 'IP over InfiniBand(IPoIB) Architecture '
   <draft-ietf-ipoib-architecture-04.txt> as an Informational RFC

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

The IESG contact persons are Margaret Wasserman and Thomas Narten.

Technical Summary

InfiniBand is a high speed, channel based interconnect between
systems and devices.

This document presents an overview of the InfiniBand
architecture. It further describes the requirements and
guidelines for the transmission of IP over InfiniBand.
Discussions in this document are applicable to both IPv4 and
IPv6 unless explicitly specified. The encapsulation of IP over
fabrics are covered in [IPOIB_ENCAP] and [IPOIB_DHCP].
 
Working Group Summary
 
This document is a work item of the IPOIB WG.
 
Protocol Quality
 
 This document was reviewed for the IESG by Margaret Wasserman.


_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Sun May 23 15:39:50 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02572
	for <ipoverib-archive@odin.ietf.org>; Sun, 23 May 2004 15:39:50 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRylk-00086t-4r
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 15:36:24 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4NJaO8J031176
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 15:36:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRyj2-0007kS-Ec
	for ipoverib-web-archive@optimus.ietf.org; Sun, 23 May 2004 15:33:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02272
	for <ipoverib-web-archive@ietf.org>; Sun, 23 May 2004 15:33:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRyj1-000553-0U
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 15:33:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRyi2-0004oj-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 15:32:34 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRyh2-0004VE-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 15:31:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRyeb-00076I-7o; Sun, 23 May 2004 15:29:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BRybI-0006hf-NV
	for ipoverib@optimus.ietf.org; Sun, 23 May 2004 15:25:36 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01970
	for <ipoverib@ietf.org>; Sun, 23 May 2004 15:25:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BRybH-00032e-E5
	for ipoverib@ietf.org; Sun, 23 May 2004 15:25:35 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BRyaJ-0002nU-00
	for ipoverib@ietf.org; Sun, 23 May 2004 15:24:36 -0400
Received: from nwkea-mail-2.sun.com ([192.18.42.14])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BRyZl-0002SL-00
	for ipoverib@ietf.org; Sun, 23 May 2004 15:24:01 -0400
Received: from jurassic.eng.sun.com ([129.146.89.50])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i4NJNUtF009950;
	Sun, 23 May 2004 12:23:30 -0700 (PDT)
Received: from taipei (taipei.SFBay.Sun.COM [129.146.85.178])
	by jurassic.eng.sun.com (8.13.0.Beta2+Sun/8.13.0.Beta2) with SMTP id i4NJNSjJ335194;
	Sun, 23 May 2004 12:23:28 -0700 (PDT)
Message-Id: <200405231923.i4NJNSjJ335194@jurassic.eng.sun.com>
Date: Sun, 23 May 2004 12:22:08 -0700 (PDT)
From: "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>
Reply-To: "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>
To: ipoverib@ietf.org
Cc: daniel.cassiday@sun.com, narten@us.ibm.com, bill@strahm.net,
        margaret@thingmagic.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 4ewQA1KP/kb/kMoDBDox3Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6_33 SunOS 5.10 sun4u sparc 
Subject: [Ipoverib] please read: Clarification on GUID's universal/local bit
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

A question was raised during the IESG review of the encapsulation
and multicast draft

http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-infiniband-06.txt

regarding the use of GUID as an interface identifier.

IPv6 spec (RFC2373 and RFC3513) requires, when an interface identifier
is derived from an IEEE EUI-64 identifier, that the universal/local bit to
be inverted. The following is quoted from RFC3513:

"Modified EUI-64 format interface identifiers are formed by inverting
the "u" bit (universal/local bit in IEEE EUI-64 terminology) when
forming the interface identifier from IEEE EUI-64 identifiers.	In
the resulting Modified EUI-64 format the "u" bit is set to one (1) to
indicate global scope, and it is set to zero (0) to indicate local
scope."

IBA spec Vol1 Release 1.1 Nov 6, 2002, section 4.1 states

EUI-64: IEEE defined 64-bit identifier...


*	The universal/local bit in IEEE EUI-64 shall be set to one to
	indicate global scope or set to zero to indicate local scope.
	The manufacturer assigns an EUI-64 with global scope set. A SM
	may assign additional EUI-64 with local scope indicated.

According to Dan Cassiday, the IBTA LWG chair, the above paragraph
clearly implies that a GUID has the universal/local bit inverted already
from an EUI-64 identifier, and thus can be readily used as an IPv6
interface identifier.

I'd like to hear, especially from those IB hardware manufacturers,
if the above is consistent with your implementation. That is, the
GUIDs you provide will have universal/local bit set to 1.

Separately if you think the IBA spec should be made more clear above
the relation between GUID and EUI-64, you should submit your suggestion
to IBTA.

Thank you,

Jerry

IPoIB WG co-chair

jerry.chu@sun.com
Sr. Staff Engineer
Solaris Networking & Security Technology
Sun Microsystems, Inc.
(650) 786-5146


_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Sun May 23 22:34:36 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21028
	for <ipoverib-archive@odin.ietf.org>; Sun, 23 May 2004 22:34:36 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS5DU-0008Rl-F0
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 22:29:29 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4O2TS79032469
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 22:29:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS588-0007sK-Nq
	for ipoverib-web-archive@optimus.ietf.org; Sun, 23 May 2004 22:23:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20676
	for <ipoverib-web-archive@ietf.org>; Sun, 23 May 2004 22:23:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS585-0005Br-G2
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 22:23:53 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS578-0004wd-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 22:22:56 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS56k-0004hk-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 22:22:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS50S-0006sZ-Gd; Sun, 23 May 2004 22:16:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS4nu-0004Iu-Sb
	for ipoverib@optimus.ietf.org; Sun, 23 May 2004 22:03:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19975
	for <ipoverib@ietf.org>; Sun, 23 May 2004 22:02:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS4nr-0007W4-P6
	for ipoverib@ietf.org; Sun, 23 May 2004 22:02:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS4mm-0007EE-00
	for ipoverib@ietf.org; Sun, 23 May 2004 22:01:53 -0400
Received: from [63.251.237.3] (helo=mtiex01.mti.mtl.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS4lo-0006im-00
	for ipoverib@ietf.org; Sun, 23 May 2004 22:00:52 -0400
Received: by MTIEX01 with Internet Mail Service (5.5.2653.19)
	id <LM67NLFJ>; Sun, 23 May 2004 18:44:11 -0700
Message-ID: <25AE7F432672D511B8DC00B0D0DF11DA02984876@MTIEX01>
From: Diego Crupnicoff <Diego@Mellanox.com>
To: "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>, ipoverib@ietf.org
Cc: daniel.cassiday@sun.com, narten@us.ibm.com, bill@strahm.net,
        margaret@thingmagic.com
Subject: RE: [Ipoverib] please read: Clarification on GUID's universal/loc
	al bit
Date: Sun, 23 May 2004 18:44:10 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C44130.9C31C6C0"
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE 
	autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C44130.9C31C6C0
Content-Type: text/plain

Resending...

> -----Original Message-----
> From: Diego Crupnicoff 
> Sent: Sunday, May 23, 2004 10:12 PM
> To: 'H.K. Jerry Chu'; ipoverib@ietf.org
> Cc: daniel.cassiday@sun.com; narten@us.ibm.com; 
> bill@strahm.net; margaret@thingmagic.com
> Subject: RE: [Ipoverib] please read: Clarification on GUID's 
> universal/local bit
> 
> 
> The IB spec is somewhat problematic on this issue. The spec 
> does state that global scope is obtained by setting the "u" 
> bit, but at the same time defines the IB GUID as an "IEEE 
> EUI-64 identifier" and refers to its spec for details (where 
> global scope is defined to be achieved by clearing the "u" bit).
> 
> We know of deployed IB implementations where the "u" bit in 
> the GUID is cleared.
> 
> The IBTA LWG has discussed this matter but no formal 
> resolution has yet been voted. The LWG is looking for a way 
> to solve the problem without affecting any existing implementation.
> 
> Given the above, I would suggest that IPoIB should define the 
> way to derive an IPv6 interface identifier from an 
> IB-port-GUID without making any assumptions on the value of 
> its "u" bit.
> 
> Thanks,
> 
> Diego
> 
> 
> 
> > -----Original Message-----
> > From: H.K. Jerry Chu [mailto:Jerry.Chu@eng.sun.com]
> > Sent: Sunday, May 23, 2004 4:22 PM
> > To: ipoverib@ietf.org
> > Cc: daniel.cassiday@sun.com; narten@us.ibm.com; 
> > bill@strahm.net; margaret@thingmagic.com
> > Subject: [Ipoverib] please read: Clarification on GUID's 
> > universal/local bit
> > 
> > 
> > A question was raised during the IESG review of the
> > encapsulation and multicast draft
> > 
> > http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-i
> > nfiniband-06.txt
> > 
> > regarding the use of GUID as an interface identifier.
> > 
> > IPv6 spec (RFC2373 and RFC3513) requires, when an interface
> > identifier is derived from an IEEE EUI-64 identifier, that 
> > the universal/local bit to be inverted. The following is 
> > quoted from RFC3513:
> > 
> > "Modified EUI-64 format interface identifiers are formed by
> > inverting the "u" bit (universal/local bit in IEEE EUI-64 
> > terminology) when
> > forming the interface identifier from IEEE EUI-64 
> > identifiers.	In
> > the resulting Modified EUI-64 format the "u" bit is set to 
> > one (1) to indicate global scope, and it is set to zero (0) 
> > to indicate local scope."
> > 
> > IBA spec Vol1 Release 1.1 Nov 6, 2002, section 4.1 states
> > 
> > EUI-64: IEEE defined 64-bit identifier...
> > 
> > 
> > *	The universal/local bit in IEEE EUI-64 shall be set to one to
> > 	indicate global scope or set to zero to indicate local scope.
> > 	The manufacturer assigns an EUI-64 with global scope set. A SM
> > 	may assign additional EUI-64 with local scope indicated.
> > 
> > According to Dan Cassiday, the IBTA LWG chair, the above
> > paragraph clearly implies that a GUID has the universal/local 
> > bit inverted already from an EUI-64 identifier, and thus can 
> > be readily used as an IPv6 interface identifier.
> > 
> > I'd like to hear, especially from those IB hardware
> > manufacturers, if the above is consistent with your 
> > implementation. That is, the GUIDs you provide will have 
> > universal/local bit set to 1.
> > 
> > Separately if you think the IBA spec should be made more
> > clear above the relation between GUID and EUI-64, you should 
> > submit your suggestion to IBTA.
> > 
> > Thank you,
> > 
> > Jerry
> > 
> > IPoIB WG co-chair
> > 
> > jerry.chu@sun.com
> > Sr. Staff Engineer
> > Solaris Networking & Security Technology
> > Sun Microsystems, Inc.
> > (650) 786-5146
> > 
> > 
> > _______________________________________________
> > IPoverIB mailing list
> > IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib
> > 
> 

------_=_NextPart_001_01C44130.9C31C6C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Ipoverib] please read: Clarification on GUID's =
universal/local bit</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Resending...</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Diego Crupnicoff </FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Sunday, May 23, 2004 10:12 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: 'H.K. Jerry Chu'; ipoverib@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: daniel.cassiday@sun.com; narten@us.ibm.com; =
</FONT>
<BR><FONT SIZE=3D2>&gt; bill@strahm.net; margaret@thingmagic.com</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: RE: [Ipoverib] please read: =
Clarification on GUID's </FONT>
<BR><FONT SIZE=3D2>&gt; universal/local bit</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The IB spec is somewhat problematic on this =
issue. The spec </FONT>
<BR><FONT SIZE=3D2>&gt; does state that global scope is obtained by =
setting the &quot;u&quot; </FONT>
<BR><FONT SIZE=3D2>&gt; bit, but at the same time defines the IB GUID =
as an &quot;IEEE </FONT>
<BR><FONT SIZE=3D2>&gt; EUI-64 identifier&quot; and refers to its spec =
for details (where </FONT>
<BR><FONT SIZE=3D2>&gt; global scope is defined to be achieved by =
clearing the &quot;u&quot; bit).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; We know of deployed IB implementations where =
the &quot;u&quot; bit in </FONT>
<BR><FONT SIZE=3D2>&gt; the GUID is cleared.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The IBTA LWG has discussed this matter but no =
formal </FONT>
<BR><FONT SIZE=3D2>&gt; resolution has yet been voted. The LWG is =
looking for a way </FONT>
<BR><FONT SIZE=3D2>&gt; to solve the problem without affecting any =
existing implementation.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Given the above, I would suggest that IPoIB =
should define the </FONT>
<BR><FONT SIZE=3D2>&gt; way to derive an IPv6 interface identifier from =
an </FONT>
<BR><FONT SIZE=3D2>&gt; IB-port-GUID without making any assumptions on =
the value of </FONT>
<BR><FONT SIZE=3D2>&gt; its &quot;u&quot; bit.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Diego</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: H.K. Jerry Chu [<A =
HREF=3D"mailto:Jerry.Chu@eng.sun.com">mailto:Jerry.Chu@eng.sun.com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Sunday, May 23, 2004 4:22 PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: ipoverib@ietf.org</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: daniel.cassiday@sun.com; =
narten@us.ibm.com; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bill@strahm.net; =
margaret@thingmagic.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Ipoverib] please read: =
Clarification on GUID's </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; universal/local bit</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; A question was raised during the IESG =
review of the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; encapsulation and multicast draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-i" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-ipoib-i=
p-over-i</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; nfiniband-06.txt</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; regarding the use of GUID as an interface =
identifier.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; IPv6 spec (RFC2373 and RFC3513) requires, =
when an interface</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; identifier is derived from an IEEE EUI-64 =
identifier, that </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the universal/local bit to be inverted. =
The following is </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; quoted from RFC3513:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &quot;Modified EUI-64 format interface =
identifiers are formed by</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; inverting the &quot;u&quot; bit =
(universal/local bit in IEEE EUI-64 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; terminology) when</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; forming the interface identifier from IEEE =
EUI-64 </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
identifiers.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; the resulting Modified EUI-64 format the =
&quot;u&quot; bit is set to </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; one (1) to indicate global scope, and it =
is set to zero (0) </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to indicate local scope.&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; IBA spec Vol1 Release 1.1 Nov 6, 2002, =
section 4.1 states</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; EUI-64: IEEE defined 64-bit =
identifier...</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; *&nbsp;&nbsp; The universal/local bit in =
IEEE EUI-64 shall be set to one to</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &nbsp;&nbsp;&nbsp; indicate global scope =
or set to zero to indicate local scope.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &nbsp;&nbsp;&nbsp; The manufacturer =
assigns an EUI-64 with global scope set. A SM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &nbsp;&nbsp;&nbsp; may assign additional =
EUI-64 with local scope indicated.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; According to Dan Cassiday, the IBTA LWG =
chair, the above</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; paragraph clearly implies that a GUID has =
the universal/local </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bit inverted already from an EUI-64 =
identifier, and thus can </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; be readily used as an IPv6 interface =
identifier.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I'd like to hear, especially from those IB =
hardware</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; manufacturers, if the above is consistent =
with your </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; implementation. That is, the GUIDs you =
provide will have </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; universal/local bit set to 1.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Separately if you think the IBA spec =
should be made more</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; clear above the relation between GUID and =
EUI-64, you should </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; submit your suggestion to IBTA.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thank you,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Jerry</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; IPoIB WG co-chair</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; jerry.chu@sun.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sr. Staff Engineer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Solaris Networking &amp; Security =
Technology</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sun Microsystems, Inc.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; (650) 786-5146</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; IPoverIB mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; IPoverIB@ietf.org <A =
HREF=3D"https://www1.ietf.org/mailman/listinfo/ipoverib" =
TARGET=3D"_blank">https://www1.ietf.org/mailman/listinfo/ipoverib</A></F=
ONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C44130.9C31C6C0--

_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Sun May 23 23:18:21 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22685
	for <ipoverib-archive@odin.ietf.org>; Sun, 23 May 2004 23:18:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS5wM-0007A8-9g
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 23:15:50 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4O3FoHI027532
	for ipoverib-archive@odin.ietf.org; Sun, 23 May 2004 23:15:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS5sa-0006bE-DG
	for ipoverib-web-archive@optimus.ietf.org; Sun, 23 May 2004 23:11:56 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA22440
	for <ipoverib-web-archive@ietf.org>; Sun, 23 May 2004 23:11:51 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS5sW-0002WH-09
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 23:11:52 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS5qb-0001wm-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 23:09:55 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS5p0-0001en-00
	for ipoverib-web-archive@ietf.org; Sun, 23 May 2004 23:08:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS5f7-0004PP-R5; Sun, 23 May 2004 22:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BS5bB-0003zl-Sh
	for ipoverib@optimus.ietf.org; Sun, 23 May 2004 22:53:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21765
	for <ipoverib@ietf.org>; Sun, 23 May 2004 22:53:53 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BS5b8-0005YL-C1
	for ipoverib@ietf.org; Sun, 23 May 2004 22:53:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BS5aG-0005Gv-00
	for ipoverib@ietf.org; Sun, 23 May 2004 22:53:00 -0400
Received: from mail.thingmagic.com ([207.31.248.245] helo=thingmagic.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BS5ZE-0004yx-00
	for ipoverib@ietf.org; Sun, 23 May 2004 22:51:56 -0400
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
  by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
  with ESMTP-TLS id 79235; Sun, 23 May 2004 22:50:52 -0400
Mime-Version: 1.0
X-Sender: margaret@mail.thingmagic.com
Message-Id: <p06020439bcd712250d54@[192.168.2.2]>
In-Reply-To: <25AE7F432672D511B8DC00B0D0DF11DA02984874@MTIEX01>
References: <25AE7F432672D511B8DC00B0D0DF11DA02984874@MTIEX01>
Date: Sun, 23 May 2004 22:51:36 -0400
To: Diego Crupnicoff <Diego@Mellanox.com>,
        "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>, ipoverib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: RE: [Ipoverib] please read: Clarification on GUID's universal/loc
 	al bit
Cc: daniel.cassiday@sun.com, narten@us.ibm.com, bill@strahm.net
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Hi Diego,

At 5:56 PM -0700 5/23/04, Diego Crupnicoff wrote:
We know of deployed IB implementations where the "u" bit in the GUID 
is cleared.

The IBTA LWG has discussed this matter but no formal resolution has 
yet been voted. The LWG is looking for a way to solve the problem 
without affecting any existing implementation.

Given the above, I would suggest that IPoIB should define the way to 
derive an IPv6 interface identifier from an IB-port-GUID without 
making any assumptions on the value of its "u" bit.

Given the apparent ambiguity in the IB specification, there are only 
two things that I can think of to do in this situation:

(1) Ask the IBTA to clarify their specification, with the hope that 
vendors will  update their implementations to match the clarified 
value.  It seems unlikely, though, that this is a practical choice if 
vendors have already shipped hardware that has burned-in values with 
different interpretations of the "u" bit.

-or-

(2) Accept that we cannot tell, by looking at an IB GUID, whether it 
is of global or local scope.  In this case, the conservative choice 
would be to treat all IB GUIDs as if they are of local scope, always 
clearing the "u" bit in the IPv6 IID, regardless of how the bit is 
set in the IB GUID.

There is a potential downside to choice (2):  If we do come up with 
mechanisms that can take advantage of the fact that some IIDs are 
globally unique (to simplify routing, host identification, etc.), 
those mechanisms would not work on IB nodes.  However, I can't think 
of any other practical choice.

What do others think we should do here?

Margaret


_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



From exim@www1.ietf.org  Mon May 24 09:13:33 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04063
	for <ipoverib-archive@odin.ietf.org>; Mon, 24 May 2004 09:13:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSFBJ-00056B-RP
	for ipoverib-archive@odin.ietf.org; Mon, 24 May 2004 09:07:54 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4OD7rDn019599
	for ipoverib-archive@odin.ietf.org; Mon, 24 May 2004 09:07:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSF0N-0003jB-8O
	for ipoverib-web-archive@optimus.ietf.org; Mon, 24 May 2004 08:56:35 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03053
	for <ipoverib-web-archive@ietf.org>; Mon, 24 May 2004 08:56:32 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSF0L-0004UT-BA
	for ipoverib-web-archive@ietf.org; Mon, 24 May 2004 08:56:33 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSEzT-0004Cb-00
	for ipoverib-web-archive@ietf.org; Mon, 24 May 2004 08:55:40 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSEyz-0003tj-00
	for ipoverib-web-archive@ietf.org; Mon, 24 May 2004 08:55:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSEpB-0002Hv-Bg; Mon, 24 May 2004 08:45:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSEdx-0008PR-4D
	for ipoverib@optimus.ietf.org; Mon, 24 May 2004 08:33:25 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01926
	for <ipoverib@ietf.org>; Mon, 24 May 2004 08:33:22 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSEdw-0005Dl-0i
	for ipoverib@ietf.org; Mon, 24 May 2004 08:33:24 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSEdB-0004wE-00
	for ipoverib@ietf.org; Mon, 24 May 2004 08:32:38 -0400
Received: from [63.251.237.3] (helo=mtiex01.mti.mtl.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSEcN-0004VA-00
	for ipoverib@ietf.org; Mon, 24 May 2004 08:31:47 -0400
Received: by MTIEX01 with Internet Mail Service (5.5.2653.19)
	id <LM67NL9X>; Mon, 24 May 2004 05:15:04 -0700
Message-ID: <25AE7F432672D511B8DC00B0D0DF11DA02984878@MTIEX01>
From: Diego Crupnicoff <Diego@Mellanox.com>
To: Margaret Wasserman <margaret@thingmagic.com>,
        "H.K. Jerry Chu"
	 <Jerry.Chu@eng.sun.com>, ipoverib@ietf.org
Cc: daniel.cassiday@sun.com, narten@us.ibm.com, bill@strahm.net
Subject: RE: [Ipoverib] please read: Clarification on GUID's universal/loc
	 al bit
Date: Mon, 24 May 2004 05:14:53 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C44188.B87E0200"
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>,
	<mailto:ipoverib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C44188.B87E0200
Content-Type: text/plain

Hi Margaret,

> (2) Accept that we cannot tell, by looking at an IB GUID, whether it 
> is of global or local scope.  In this case, the conservative choice 
> would be to treat all IB GUIDs as if they are of local scope, always 
> clearing the "u" bit in the IPv6 IID, regardless of how the bit is 
> set in the IB GUID.

I think it may actually be safe to assume that the IB GUID in question is
__always__ globally unique (regardless of the value in its "u" bit). The IB
spec says: 

"The manufacturer assigns an EUI-64 __with_global_scope_set__"

The IPv6 IID can therefore be based on this manufacturer assigned GUID which
is __required__ by the IB spec to be one with global scope. The mechanism
for building the IPv6 IID could then be as simple as taking the IB mfg
assigned GUID and set (if it was not already so) its "u" bit (i.e. ignore
the interpretation that the vendor may have given to the IB spec).

To close the loop, the IBTA would have to explicitly forbid the use of the
same 63 bit combination with two different values for the u bit as two valid
globally unique GUIDs. I can't speak for the entire IBTA but it looks to me
that this would be acceptable. Furthermore, it is my understanding that the
definition of locally unique IB GUIDs would then be irrelevant to the ipoib
spec.

Does it make sense?

Thanks,

Diego

------_=_NextPart_001_01C44188.B87E0200
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Ipoverib] please read: Clarification on GUID's =
universal/loc al bit</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Margaret,</FONT>
</P>

<P><FONT SIZE=3D2>&gt; (2) Accept that we cannot tell, by looking at an =
IB GUID, whether it </FONT>
<BR><FONT SIZE=3D2>&gt; is of global or local scope.&nbsp; In this =
case, the conservative choice </FONT>
<BR><FONT SIZE=3D2>&gt; would be to treat all IB GUIDs as if they are =
of local scope, always </FONT>
<BR><FONT SIZE=3D2>&gt; clearing the &quot;u&quot; bit in the IPv6 IID, =
regardless of how the bit is </FONT>
<BR><FONT SIZE=3D2>&gt; set in the IB GUID.</FONT>
</P>

<P><FONT SIZE=3D2>I think it may actually be safe to assume that the IB =
GUID in question is __always__ globally unique (regardless of the value =
in its &quot;u&quot; bit). The IB spec says: </FONT></P>

<P><FONT SIZE=3D2>&quot;The manufacturer assigns an EUI-64 =
__with_global_scope_set__&quot;</FONT>
</P>

<P><FONT SIZE=3D2>The IPv6 IID can therefore be based on this =
manufacturer assigned GUID which is __required__ by the IB spec to be =
one with global scope. The mechanism for building the IPv6 IID could =
then be as simple as taking the IB mfg assigned GUID and set (if it was =
not already so) its &quot;u&quot; bit (i.e. ignore the interpretation =
that the vendor may have given to the IB spec).</FONT></P>

<P><FONT SIZE=3D2>To close the loop, the IBTA would have to explicitly =
forbid the use of the same 63 bit combination with two different values =
for the u bit as two valid globally unique GUIDs. I can't speak for the =
entire IBTA but it looks to me that this would be acceptable. =
Furthermore, it is my understanding that the definition of locally =
unique IB GUIDs would then be irrelevant to the ipoib spec.</FONT></P>

<P><FONT SIZE=3D2>Does it make sense?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Diego</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C44188.B87E0200--

_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib



