From exim@www1.ietf.org  Mon Dec  1 15:30:22 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27367
	for <ipoverib-archive@odin.ietf.org>; Mon, 1 Dec 2003 15:30:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQugH-0006zu-JH
	for ipoverib-archive@odin.ietf.org; Mon, 01 Dec 2003 15:30:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1KU5fA026894
	for ipoverib-archive@odin.ietf.org; Mon, 1 Dec 2003 15:30:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQugH-0006zh-Ek
	for ipoverib-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 15:30:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27237
	for <ipoverib-web-archive@ietf.org>; Mon, 1 Dec 2003 15:29:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQugF-0007jx-00
	for ipoverib-web-archive@ietf.org; Mon, 01 Dec 2003 15:30:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQugF-0007js-00
	for ipoverib-web-archive@ietf.org; Mon, 01 Dec 2003 15:30:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQugD-0006z1-VK; Mon, 01 Dec 2003 15:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQug7-0006y6-9g
	for ipoverib@optimus.ietf.org; Mon, 01 Dec 2003 15:29:55 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27208;
	Mon, 1 Dec 2003 15:29:40 -0500 (EST)
Message-Id: <200312012029.PAA27208@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ipoverib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 01 Dec 2003 15:29:40 -0500
Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-ip-over-infiniband-05.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>

--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		: Transmission of IP over InfiniBand
	Author(s)	: V. Kashyap
	Filename	: draft-ietf-ipoib-ip-over-infiniband-05.txt
	Pages		: 19
	Date		: 2003-12-1
	
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 addresse
to InfiniBand multicast addresses.  Additionally this document
defines the setup and configuration of IPoIB links.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipoib-ip-over-infiniband-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-ip-over-infiniband-05.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-ip-over-infiniband-05.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:	<2003-12-1152214.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipoib-ip-over-infiniband-05.txt

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

Content-Type: text/plain
Content-ID:	<2003-12-1152214.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



From exim@www1.ietf.org  Tue Dec  2 18:55:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24820
	for <ipoverib-archive@odin.ietf.org>; Tue, 2 Dec 2003 18:55:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKMC-00017C-N7
	for ipoverib-archive@odin.ietf.org; Tue, 02 Dec 2003 18:55:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2Nt4UD004281
	for ipoverib-archive@odin.ietf.org; Tue, 2 Dec 2003 18:55:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKMC-00016y-JV
	for ipoverib-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 18:55:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24793
	for <ipoverib-web-archive@ietf.org>; Tue, 2 Dec 2003 18:54:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKM9-00061B-00
	for ipoverib-web-archive@ietf.org; Tue, 02 Dec 2003 18:55:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKM8-000617-00
	for ipoverib-web-archive@ietf.org; Tue, 02 Dec 2003 18:55:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKMA-00015y-2t; Tue, 02 Dec 2003 18:55:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARKLq-00015S-7z
	for ipoverib@optimus.ietf.org; Tue, 02 Dec 2003 18:54:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24765
	for <ipoverib@ietf.org>; Tue, 2 Dec 2003 18:54:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKLl-00060T-00
	for ipoverib@ietf.org; Tue, 02 Dec 2003 18:54:37 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARKLk-000601-00
	for ipoverib@ietf.org; Tue, 02 Dec 2003 18:54:36 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB2Ns6UP001209
	for <ipoverib@ietf.org>; Tue, 2 Dec 2003 15:54:06 -0800 (PST)
Received: from Sun.COM (sr1-umpk-06.SFBay.Sun.COM [129.146.11.166])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPA00K8GL26UPB0@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Tue, 02 Dec 2003 15:54:06 -0800 (PST)
Date: Tue, 02 Dec 2003 15:54:06 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
To: ipoverib@ietf.org
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FCD261E.D0858259@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
Content-Transfer-Encoding: 7bit
Subject: [Ipoverib] GID clarifications
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

It seems that certain parts of the 
draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
require clarification. For this discussion, please refer to

1. section 9.1 Link Information says:
"The GID, if formed using the GUID, can be used to unambiguously 
identify an endpoint."

2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
"It is RECOMMENDED that the GID formed by the combination of the
IB subnet prefix and the port's GUID be included in the 
link-layer/hardware address."

Can comment #2 be safely taken to mean that GID index 0 is
being RECOMMENDED? Port GUID seems somewhat ambiguous, since I 
am not sure (after reading IBA 1.1 section 4.1) whether the
term GUID refers only to the manufacturer assigned value that appears
in lower 64 bits of GID index 0, or whether it also includes 
lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
was really intended, the comment should explicitly state so to prevent
confusion. 

Also, to make things simple, is it reasonable to REQUIRE implementations
to always use GID index 0 (maybe this depends on whether existing
implementations all use GID0 only)? The reason this might be 
interesting is that when a node receives a packet without a GRH 
(whereby it already knows the sender's LID and QPN), it can possibly 
reverse lookup the sender's LID to identify the sender's GID index 
0 and concatenate the sender's QPN to figure out the sender's link 
address. Thus, a receiver can always figure out the sender's address, 
even when a GRH is not present. This would be similar to ethernet, 
where a receiver can always determine a sender's address, and thus
is more DLPIv2 (unitdata_indication) friendly.

Regarding comment #1, what does "unambiguously identify an endpoint"
mean? GIDs are unique in the subnet; and if an IP link contains
members in multiple IBA subnets, the subnet prefixes will disambiguate
which endport is being referred. 

Thanks.

Kanoj

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



From exim@www1.ietf.org  Wed Dec  3 14:24:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00017
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 14:24:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcbX-0007cK-16
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 14:24:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3JO7Xf029276
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 14:24:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcbW-0007c7-Sn
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 14:24:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29979
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 14:23:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcbU-0006sP-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:24:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcbT-0006sM-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:24:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcbQ-0007bq-Sw; Wed, 03 Dec 2003 14:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcbA-0007bU-Ah
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 14:23:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29969;
	Wed, 3 Dec 2003 14:23:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcb4-0006sB-00; Wed, 03 Dec 2003 14:23:38 -0500
Received: from e33.co.us.ibm.com ([32.97.110.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcb2-0006rH-00; Wed, 03 Dec 2003 14:23:36 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e33.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id hB3JMwJh328876;
	Wed, 3 Dec 2003 14:22:58 -0500
Received: from d03nm122.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id hB3JMnFX068314;
	Wed, 3 Dec 2003 12:22:50 -0700
To: Kanoj.Sarcar@Sun.COM
Cc: ipoverib@ietf.org, ipoverib-admin@ietf.org
MIME-Version: 1.0
Subject: Re: [Ipoverib] GID clarifications
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OF7EAC22AC.1E3035C0-ON88256DF1.005FEB6B-88256DF1.006A7D1D@us.ibm.com>
From: Vivek Kashyap <vivk@us.ibm.com>
Date: Wed, 3 Dec 2003 11:22:45 -0800
X-MIMETrack: Serialize by Router on D03NM122/03/M/IBM(Release 6.0.2CF2HF92 | October 15, 2003) at
 12/03/2003 12:22:49,
	Serialize complete at 12/03/2003 12:22:49
Content-Type: multipart/alternative; boundary="=_alternative 006A7D1788256DF1_="
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>

This is a multipart message in MIME format.
--=_alternative 006A7D1788256DF1_=
Content-Type: text/plain; charset="us-ascii"

Kanoj,

The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed 
using this GUID, the CA's GUID or some other value. Any GID is unique in 
the IB fabric however only by using the port's GUID/EUI-64 identifier can 
one uniquely identify the port. The other GID's, as noted, can be applied 
to other ports too - though not concurrently. The GID formed using the 
EUI-64 identifier is the 'GID at index 0'. I've made note of your comment 
and can clarify further as needed.

wrt, using only GID at index 0 as in the MAC address, there have been 
proponents of using the other GIDs (non EUI-64 GID).

Vivek
--
Vivek Kashyap
Linux Technology Center, IBM
vivk@us.ibm.com 
kashyapv@us.ibm.com 
Ph: 503 578 3422 T/L: 775 3422





Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Sent by: ipoverib-admin@ietf.org
12/02/2003 03:54 PM
Please respond to Kanoj.Sarcar

 
        To:     ipoverib@ietf.org
        cc: 
        Subject:        [Ipoverib] GID clarifications



Hi,

It seems that certain parts of the 
draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
require clarification. For this discussion, please refer to

1. section 9.1 Link Information says:
"The GID, if formed using the GUID, can be used to unambiguously 
identify an endpoint."

2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
"It is RECOMMENDED that the GID formed by the combination of the
IB subnet prefix and the port's GUID be included in the 
link-layer/hardware address."

Can comment #2 be safely taken to mean that GID index 0 is
being RECOMMENDED? Port GUID seems somewhat ambiguous, since I 
am not sure (after reading IBA 1.1 section 4.1) whether the
term GUID refers only to the manufacturer assigned value that appears
in lower 64 bits of GID index 0, or whether it also includes 
lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
was really intended, the comment should explicitly state so to prevent
confusion. 

Also, to make things simple, is it reasonable to REQUIRE implementations
to always use GID index 0 (maybe this depends on whether existing
implementations all use GID0 only)? The reason this might be 
interesting is that when a node receives a packet without a GRH 
(whereby it already knows the sender's LID and QPN), it can possibly 
reverse lookup the sender's LID to identify the sender's GID index 
0 and concatenate the sender's QPN to figure out the sender's link 
address. Thus, a receiver can always figure out the sender's address, 
even when a GRH is not present. This would be similar to ethernet, 
where a receiver can always determine a sender's address, and thus
is more DLPIv2 (unitdata_indication) friendly.

Regarding comment #1, what does "unambiguously identify an endpoint"
mean? GIDs are unique in the subnet; and if an IP link contains
members in multiple IBA subnets, the subnet prefixes will disambiguate
which endport is being referred. 

Thanks.

Kanoj

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



--=_alternative 006A7D1788256DF1_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Kanoj,</font>
<br>
<br><font size=2 face="sans-serif">The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed using this GUID, the CA's GUID or some other value. Any GID is unique in the IB fabric however only by using the port's GUID/EUI-64 identifier can one uniquely identify the port. The other GID's, as noted, can be applied to other ports too - though not concurrently. The GID formed using the EUI-64 identifier is the 'GID at index 0'. I've made note of your comment and can clarify further as needed.</font>
<br>
<br><font size=2 face="sans-serif">wrt, using only GID at index 0 as in the MAC address, there have been proponents of using the other GIDs (non EUI-64 GID).</font>
<br>
<br><font size=2 face="sans-serif">Vivek<br>
--<br>
Vivek Kashyap<br>
Linux Technology Center, IBM<br>
vivk@us.ibm.com <br>
kashyapv@us.ibm.com <br>
Ph: 503 578 3422 T/L: 775 3422<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Kanoj Sarcar &lt;Kanoj.Sarcar@Sun.COM&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: ipoverib-admin@ietf.org</font>
<p><font size=1 face="sans-serif">12/02/2003 03:54 PM</font>
<br><font size=1 face="sans-serif">Please respond to Kanoj.Sarcar</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;ipoverib@ietf.org</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;[Ipoverib] GID clarifications</font>
<br></table>
<br>
<br>
<br><font size=2 face="Courier New">Hi,<br>
<br>
It seems that certain parts of the <br>
draft-ietf-ipoib-ip-over-infiniband-05.txt draft might<br>
require clarification. For this discussion, please refer to<br>
<br>
1. section 9.1 Link Information says:<br>
&quot;The GID, if formed using the GUID, can be used to unambiguously <br>
identify an endpoint.&quot;<br>
<br>
2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:<br>
&quot;It is RECOMMENDED that the GID formed by the combination of the<br>
IB subnet prefix and the port's GUID be included in the <br>
link-layer/hardware address.&quot;<br>
<br>
Can comment #2 be safely taken to mean that GID index 0 is<br>
being RECOMMENDED? Port GUID seems somewhat ambiguous, since I <br>
am not sure (after reading IBA 1.1 section 4.1) whether the<br>
term GUID refers only to the manufacturer assigned value that appears<br>
in lower 64 bits of GID index 0, or whether it also includes <br>
lower 64 bits of SM assigned GIDs at higher indices. If GID index 0<br>
was really intended, the comment should explicitly state so to prevent<br>
confusion. <br>
<br>
Also, to make things simple, is it reasonable to REQUIRE implementations<br>
to always use GID index 0 (maybe this depends on whether existing<br>
implementations all use GID0 only)? The reason this might be <br>
interesting is that when a node receives a packet without a GRH <br>
(whereby it already knows the sender's LID and QPN), it can possibly <br>
reverse lookup the sender's LID to identify the sender's GID index <br>
0 and concatenate the sender's QPN to figure out the sender's link <br>
address. Thus, a receiver can always figure out the sender's address, <br>
even when a GRH is not present. This would be similar to ethernet, <br>
where a receiver can always determine a sender's address, and thus<br>
is more DLPIv2 (unitdata_indication) friendly.<br>
<br>
Regarding comment #1, what does &quot;unambiguously identify an endpoint&quot;<br>
mean? GIDs are unique in the subnet; and if an IP link contains<br>
members in multiple IBA subnets, the subnet prefixes will disambiguate<br>
which endport is being referred. <br>
<br>
Thanks.<br>
<br>
Kanoj<br>
<br>
_______________________________________________<br>
IPoverIB mailing list<br>
IPoverIB@ietf.org<br>
https://www1.ietf.org/mailman/listinfo/ipoverib<br>
</font>
<br>
<br>
--=_alternative 006A7D1788256DF1_=--

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



From exim@www1.ietf.org  Wed Dec  3 14:32:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00319
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 14:32:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcjD-0007ps-Ks
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 14:32:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3JW3cj030114
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 14:32:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcjD-0007pd-GX
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 14:32:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00285
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 14:31:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcjA-0006zz-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:32:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARcjA-0006zw-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:32:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARcjC-0007p0-6R; Wed, 03 Dec 2003 14:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARciU-0007nf-UY
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 14:31:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00248
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 14:31:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARciS-0006y4-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 14:31:16 -0500
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARciR-0006xX-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 14:31:15 -0500
Received: from h-68-164-159-164.snvacaid.dynamic.covad.net ([68.164.159.164] helo=oemcomputer)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1ARci8-0000eI-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 11:30:56 -0800
Message-ID: <003101c3b9d4$4ad0a960$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ipoverib@ietf.org>
References: <3FCD261E.D0858259@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
Date: Wed, 3 Dec 2003 11:33:11 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Kanoj Sarcar" <Kanoj.Sarcar@Sun.COM>
> To: <ipoverib@ietf.org>
> Sent: Tuesday, December 02, 2003 3:54 PM
> Subject: [Ipoverib] GID clarifications
...
> Regarding comment #1, what does "unambiguously identify an endpoint"
> mean? GIDs are unique in the subnet; and if an IP link contains
> members in multiple IBA subnets, the subnet prefixes will disambiguate
> which endport is being referred.
...

I guess the logical conclusion is that this is incompatible with any
kind of NAT, or management from outside of a NAT-ed network.
(This may well be a feature rather than a bug, but I wanted to be
sure.)

Randy



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



From exim@www1.ietf.org  Wed Dec  3 14:53:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01219
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 14:53:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARd3a-0000Un-Fg
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 14:53:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3Jr6HM001903
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 14:53:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARd3Z-0000Uc-Bx
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 14:53:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01157
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 14:52:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARd3W-0007Il-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:53:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARd3W-0007Ii-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 14:53:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARd3V-0000U6-F2; Wed, 03 Dec 2003 14:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARd3C-0000Te-Pc
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 14:52:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01147
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 14:52:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARd39-0007IU-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 14:52:39 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARd38-0007IO-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 14:52:38 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id hB3JqZPj020838
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 12:52:35 -0700 (MST)
Received: from Sun.COM (sr1-umpk-06.SFBay.Sun.COM [129.146.11.166])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPC00BUU4JMUK70@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Wed, 03 Dec 2003 11:52:34 -0800 (PST)
Date: Wed, 03 Dec 2003 11:52:34 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Vivek Kashyap <vivk@us.ibm.com>
Cc: ipoverib@ietf.org, ipoverib-admin@ietf.org
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FCE3F02.F25BFC15@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: 
 <OF7EAC22AC.1E3035C0-ON88256DF1.005FEB6B-88256DF1.006A7D1D@us.ibm.com>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Vivek Kashyap wrote:
> 
> Kanoj,
> 
> The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed using this GUID, the CA's GUID or some other value. Any GID is unique in the IB fabric however only by using the port's GUID/EUI-64 identifier can one uniquely identify the port. The other GID's, as noted, can be applied to other ports too - though not concurrently. The GID formed using the EUI-64 identifier is the 'GID at index 0'. I've made note of your comment and can clarify further as needed.
> 
> wrt, using only GID at index 0 as in the MAC address, there have been proponents of using the other GIDs (non EUI-64 GID).
> 
> Vivek

Vivek,

Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer assigned and 
SM assigned values are required to be EUI-64 compliant (they differ only in u/l bits). 
Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID is its EUI-64 
identifier" might be confusing. Saying "GUID using manufacturer assigned EUI-64 identifier" 
or better "GID index 0" removes all confusion. I think we agree on the intent, I just
want to make sure if you use the term GUID, you do specifically define what you mean
by it.

Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
 
1. SM assigned GIDs are not that popular (anymore?)
2. it allows determination of sender's ipoib address, thus allowing (receiver side)
implementations to be dlpiv2 conformant?

Thanks.

Kanoj
  


> --
> Vivek Kashyap
> Linux Technology Center, IBM
> vivk@us.ibm.com
> kashyapv@us.ibm.com
> Ph: 503 578 3422 T/L: 775 3422
> 
>     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>                                                                                                                         
>     Sent by: ipoverib-admin@ietf.org                                                                                                                            
>                                                                                                                                                                 
>     12/02/2003 03:54 PM                                                                                                                                         
>     Please respond to Kanoj.Sarcar
> 
> Hi,
> 
> It seems that certain parts of the
> draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> require clarification. For this discussion, please refer to
> 
> 1. section 9.1 Link Information says:
> "The GID, if formed using the GUID, can be used to unambiguously
> identify an endpoint."
> 
> 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
> "It is RECOMMENDED that the GID formed by the combination of the
> IB subnet prefix and the port's GUID be included in the
> link-layer/hardware address."
> 
> Can comment #2 be safely taken to mean that GID index 0 is
> being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
> am not sure (after reading IBA 1.1 section 4.1) whether the
> term GUID refers only to the manufacturer assigned value that appears
> in lower 64 bits of GID index 0, or whether it also includes
> lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
> was really intended, the comment should explicitly state so to prevent
> confusion.
> 
> Also, to make things simple, is it reasonable to REQUIRE implementations
> to always use GID index 0 (maybe this depends on whether existing
> implementations all use GID0 only)? The reason this might be
> interesting is that when a node receives a packet without a GRH
> (whereby it already knows the sender's LID and QPN), it can possibly
> reverse lookup the sender's LID to identify the sender's GID index
> 0 and concatenate the sender's QPN to figure out the sender's link
> address. Thus, a receiver can always figure out the sender's address,
> even when a GRH is not present. This would be similar to ethernet,
> where a receiver can always determine a sender's address, and thus
> is more DLPIv2 (unitdata_indication) friendly.
> 
> Regarding comment #1, what does "unambiguously identify an endpoint"
> mean? GIDs are unique in the subnet; and if an IP link contains
> members in multiple IBA subnets, the subnet prefixes will disambiguate
> which endport is being referred.
> 
> Thanks.
> 
> Kanoj
> 
> _______________________________________________
> 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  Wed Dec  3 17:08:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11871
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 17:08:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfAF-00074o-8h
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 17:08:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3M87Mc027190
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 17:08:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfAE-00074R-Sf
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 17:08:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11811
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 17:07:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfAC-0002xZ-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:08:04 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfAB-0002xW-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:08:03 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1ARfAB-0007ou-VI
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:08:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfAA-00072N-3v; Wed, 03 Dec 2003 17:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARf9v-0006vz-6a
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 17:07:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11757
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 17:07:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARf9s-0002wd-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 17:07:44 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARf9s-0002vQ-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 17:07:44 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hB3LiG127596
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 16:44:16 -0500
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Subject: RE: [Ipoverib] GID clarifications
Date: Wed, 3 Dec 2003 14:06:49 -0800
Message-ID: <01e101c3b9e9$c0ef69a0$f5d912c0@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: <003101c3b9d4$4ad0a960$7f1afea9@oemcomputer>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I don't think this is the case - NAT is completely contained within
Layer 3.  It does not do any layer 2 munging as far as I can tell.  I
believe the comment was in relationship to IB subnets (you have to be
very careful - as they only differ by a letter)

Kanoj correct me if I am wrong

Bill

-----Original Message-----
From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf
Of Randy Presuhn
Sent: Wednesday, December 03, 2003 11:33 AM
To: ipoverib@ietf.org
Subject: Re: [Ipoverib] GID clarifications


Hi -

> From: "Kanoj Sarcar" <Kanoj.Sarcar@Sun.COM>
> To: <ipoverib@ietf.org>
> Sent: Tuesday, December 02, 2003 3:54 PM
> Subject: [Ipoverib] GID clarifications
...
> Regarding comment #1, what does "unambiguously identify an endpoint" 
> mean? GIDs are unique in the subnet; and if an IP link contains 
> members in multiple IBA subnets, the subnet prefixes will disambiguate

> which endport is being referred.
...

I guess the logical conclusion is that this is incompatible with any
kind of NAT, or management from outside of a NAT-ed network. (This may
well be a feature rather than a bug, but I wanted to be
sure.)

Randy



_______________________________________________
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  Wed Dec  3 17:26:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12821
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 17:26:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfRb-0007bI-Q3
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 17:26:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3MQ3d8029213
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 17:26:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfRb-0007aq-Kp
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 17:26:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12799
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 17:25:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfRX-0003Md-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:25:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfRX-0003Ma-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:25:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfRY-0007aH-E5; Wed, 03 Dec 2003 17:26:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfR7-0007Zo-0Q
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 17:25:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12790
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 17:25:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfR3-0003MN-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 17:25:29 -0500
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfR3-0003MK-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 17:25:29 -0500
Received: from h-68-164-92-95.snvacaid.dynamic.covad.net ([68.164.92.95] helo=oemcomputer)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1ARfQu-0001ef-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 14:25:21 -0800
Message-ID: <011701c3b9ec$a81e8a20$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ipoverib@ietf.org>
References: <01e101c3b9e9$c0ef69a0$f5d912c0@mobilebill>
Subject: Re: [Ipoverib] GID clarifications
Date: Wed, 3 Dec 2003 14:27:37 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

...
> I don't think this is the case - NAT is completely contained within
> Layer 3.  It does not do any layer 2 munging as far as I can tell.  I
> believe the comment was in relationship to IB subnets (you have to be
> very careful - as they only differ by a letter)
...

Thanks for the clarification.  I'm happy as long as whatever
shows up in the MIB is sufficiently unique to prevent confusion.
For example, consider what could happen when mutiple
enterprises outsource their network management to the
same provider.  The management systems need to be able to
tell whether a given idententifier refers to the same or different
systems, particularly if the relationships between the enterprises
potentially involve shared facilities.

Randy



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



From exim@www1.ietf.org  Wed Dec  3 17:29:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12908
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 17:29:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfUV-0007jZ-7F
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 17:29:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3MT3TN029723
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 17:29:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfUV-0007jK-3b
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 17:29:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12867
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 17:28:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfUS-0003Nz-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:29:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfUS-0003Nw-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 17:29:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfUT-0007j4-BC; Wed, 03 Dec 2003 17:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARfTt-0007gy-8d
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 17:28:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12852;
	Wed, 3 Dec 2003 17:28:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfTq-0003NS-00; Wed, 03 Dec 2003 17:28:22 -0500
Received: from e33.co.us.ibm.com ([32.97.110.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARfTo-0003NI-00; Wed, 03 Dec 2003 17:28:21 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e33.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id hB3MRlJh365144;
	Wed, 3 Dec 2003 17:27:48 -0500
Received: from DYN319477.beaverton.ibm.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id hB3MRkFY074752;
	Wed, 3 Dec 2003 15:27:47 -0700
Date: Wed, 3 Dec 2003 14:27:57 -0800 (Pacific Standard Time)
From: Vivek Kashyap <kashyapv@us.ibm.com>
To: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
cc: Vivek Kashyap <vivk@us.ibm.com>, <ipoverib@ietf.org>,
        <ipoverib-admin@ietf.org>
Subject: Re: [Ipoverib] GID clarifications
In-Reply-To: <3FCE3F02.F25BFC15@Sun.COM>
Message-ID: <Pine.WNT.4.44.0312031410310.728-100000@w-vkashyap95.des.sequent.com>
X-X-Sender: kashyapv@imap.linux.ibm.com
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>

Yes, the port's GUID is the manufacturer assigned EUI-64 id for the port. It is
probably better to use the IBA term 'portGUID'.

Vivek

On Wed, 3 Dec 2003, Kanoj Sarcar wrote:

> Vivek Kashyap wrote:
> >
> > Kanoj,
> >
> > The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed using this GUID, the CA's GUID or some other value. Any GID is unique in the IB fabric however only by using the port's GUID/EUI-64 identifier can one uniquely identify the port. The other GID's, as noted, can be applied to other ports too - though not concurrently. The GID formed using the EUI-64 identifier is the 'GID at index 0'. I've made note of your comment and can clarify further as needed.
> >
> > wrt, using only GID at index 0 as in the MAC address, there have been proponents of using the other GIDs (non EUI-64 GID).
> >
> > Vivek
>
> Vivek,
>
> Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer assigned and
> SM assigned values are required to be EUI-64 compliant (they differ only in u/l bits).
> Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID is its EUI-64
> identifier" might be confusing. Saying "GUID using manufacturer assigned EUI-64 identifier"
> or better "GID index 0" removes all confusion. I think we agree on the intent, I just
> want to make sure if you use the term GUID, you do specifically define what you mean
> by it.
>
> Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
>
> 1. SM assigned GIDs are not that popular (anymore?)
> 2. it allows determination of sender's ipoib address, thus allowing (receiver side)
> implementations to be dlpiv2 conformant?
>
> Thanks.
>
> Kanoj
>
>
>
> > --
> > Vivek Kashyap
> > Linux Technology Center, IBM
> > vivk@us.ibm.com
> > kashyapv@us.ibm.com
> > Ph: 503 578 3422 T/L: 775 3422
> >
> >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
> >     Sent by: ipoverib-admin@ietf.org
> >
> >     12/02/2003 03:54 PM
> >     Please respond to Kanoj.Sarcar
> >
> > Hi,
> >
> > It seems that certain parts of the
> > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> > require clarification. For this discussion, please refer to
> >
> > 1. section 9.1 Link Information says:
> > "The GID, if formed using the GUID, can be used to unambiguously
> > identify an endpoint."
> >
> > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
> > "It is RECOMMENDED that the GID formed by the combination of the
> > IB subnet prefix and the port's GUID be included in the
> > link-layer/hardware address."
> >
> > Can comment #2 be safely taken to mean that GID index 0 is
> > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
> > am not sure (after reading IBA 1.1 section 4.1) whether the
> > term GUID refers only to the manufacturer assigned value that appears
> > in lower 64 bits of GID index 0, or whether it also includes
> > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
> > was really intended, the comment should explicitly state so to prevent
> > confusion.
> >
> > Also, to make things simple, is it reasonable to REQUIRE implementations
> > to always use GID index 0 (maybe this depends on whether existing
> > implementations all use GID0 only)? The reason this might be
> > interesting is that when a node receives a packet without a GRH
> > (whereby it already knows the sender's LID and QPN), it can possibly
> > reverse lookup the sender's LID to identify the sender's GID index
> > 0 and concatenate the sender's QPN to figure out the sender's link
> > address. Thus, a receiver can always figure out the sender's address,
> > even when a GRH is not present. This would be similar to ethernet,
> > where a receiver can always determine a sender's address, and thus
> > is more DLPIv2 (unitdata_indication) friendly.
> >
> > Regarding comment #1, what does "unambiguously identify an endpoint"
> > mean? GIDs are unique in the subnet; and if an IP link contains
> > members in multiple IBA subnets, the subnet prefixes will disambiguate
> > which endport is being referred.
> >
> > Thanks.
> >
> > Kanoj
> >
> > _______________________________________________
> > 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
>
>

__

Vivek Kashyap
Linux Technology Center, IBM


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



From exim@www1.ietf.org  Wed Dec  3 18:06:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14204
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 18:06:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARg4N-0000S9-PG
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 18:06:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3N67Or001735
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 18:06:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARg4N-0000Ru-Ln
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 18:06:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14127
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 18:05:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARg4F-0003o5-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 18:05:59 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARg4F-0003o2-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 18:05:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARg4H-0000R5-7M; Wed, 03 Dec 2003 18:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARg3m-0000Qm-E9
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 18:05:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14070
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 18:05:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARg3j-0003nt-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 18:05:27 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARg3i-0003nd-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 18:05:26 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB3N4tUP018019
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 15:04:55 -0800 (PST)
Received: from Sun.COM (sr1-umpk-06.SFBay.Sun.COM [129.146.11.166])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPC00B7SDG7UKB0@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Wed, 03 Dec 2003 15:04:55 -0800 (PST)
Date: Wed, 03 Dec 2003 15:04:55 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Randy Presuhn <randy_presuhn@mindspring.com>
Cc: ipoverib@ietf.org
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FCE6C17.BEF03329@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <01e101c3b9e9$c0ef69a0$f5d912c0@mobilebill>
 <011701c3b9ec$a81e8a20$7f1afea9@oemcomputer>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Randy Presuhn wrote:
> 
> Hi -
> 
> ...
> > I don't think this is the case - NAT is completely contained within
> > Layer 3.  It does not do any layer 2 munging as far as I can tell.  I
> > believe the comment was in relationship to IB subnets (you have to be
> > very careful - as they only differ by a letter)
> ...
> 
> Thanks for the clarification.  I'm happy as long as whatever
> shows up in the MIB is sufficiently unique to prevent confusion.

"Sufficiently unique" seems to be the key point here. If you consider any
GID of any endport in one IBA subnet, or in a set of IBA subnets
all connected by IBA routers, the GID is guaranteed to uniquely
identify the endport (which is what I pointed out originally). 
 
> For example, consider what could happen when mutiple
> enterprises outsource their network management to the
> same provider.  The management systems need to be able to
> tell whether a given idententifier refers to the same or different
> systems, particularly if the relationships between the enterprises
> potentially involve shared facilities.

If the provider is managing two unconnected sets of IBA subnets
(simple example would be a single IBA subnet for A, and a single
IBA subnet for B, not connected to each other), then two different
endports might have the same GID; ie, by looking at the GID, you 
could not decide whether it referred to the endport in A or in B.
This is true in general, but if everyone decided to always used
GID index 0, then all GIDs are guaranteed to be unique (I think I
see what the intent of the statement in the draft was).

As Bill pointed out, NAT probably does not look at macaddress/GID
to make this differentiation. If you believe you have some protocol
or system that needs to differentiate based on the IPoIB macaddress/GID,
you should bring it up to the list; it will add weight to the 
argument that everyone must be required to (as opposed to recommended 
to) use GID index 0.

Thanks. 

Kanoj


> 
> Randy
> 
> _______________________________________________
> 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  Wed Dec  3 18:39:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16207
	for <ipoverib-archive@odin.ietf.org>; Wed, 3 Dec 2003 18:39:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgaK-0001iO-1W
	for ipoverib-archive@odin.ietf.org; Wed, 03 Dec 2003 18:39:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB3Nd8nf006589
	for ipoverib-archive@odin.ietf.org; Wed, 3 Dec 2003 18:39:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgaJ-0001iC-To
	for ipoverib-web-archive@optimus.ietf.org; Wed, 03 Dec 2003 18:39:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16179
	for <ipoverib-web-archive@ietf.org>; Wed, 3 Dec 2003 18:38:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgaD-0004Fc-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 18:39:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARgaC-0004FZ-00
	for ipoverib-web-archive@ietf.org; Wed, 03 Dec 2003 18:39:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARgaD-0001hd-9f; Wed, 03 Dec 2003 18:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARga8-0001hS-EQ
	for ipoverib@optimus.ietf.org; Wed, 03 Dec 2003 18:38:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16175
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 18:38:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARga4-0004FV-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 18:38:52 -0500
Received: from scaup.mail.pas.earthlink.net ([207.217.120.49])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARga4-0004FS-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 18:38:52 -0500
Received: from h-68-164-92-95.snvacaid.dynamic.covad.net ([68.164.92.95] helo=oemcomputer)
	by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1ARga1-0006Xe-00
	for ipoverib@ietf.org; Wed, 03 Dec 2003 15:38:49 -0800
Message-ID: <000a01c3b9f6$ebd7fd00$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ipoverib@ietf.org>
References: <01e101c3b9e9$c0ef69a0$f5d912c0@mobilebill> <011701c3b9ec$a81e8a20$7f1afea9@oemcomputer> <3FCE6C17.BEF03329@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
Date: Wed, 3 Dec 2003 15:40:20 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Kanoj Sarcar" <Kanoj.Sarcar@Sun.COM>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <ipoverib@ietf.org>
> Sent: Wednesday, December 03, 2003 3:04 PM
> Subject: Re: [Ipoverib] GID clarifications


...
> If the provider is managing two unconnected sets of IBA subnets
> (simple example would be a single IBA subnet for A, and a single
> IBA subnet for B, not connected to each other), then two different
> endports might have the same GID; ie, by looking at the GID, you
> could not decide whether it referred to the endport in A or in B.

Now, thinking about a management system that only knows what
it can see through MIBs: how can it know whether A and B are
connected or not?  What happens if they start out unconnected,
and later, due to, for example, a corporate merger, they become
connected?  How do we guarantee that the identifiers for A and B
are unique?  If they are not guaranteed to be unique, does it matter?

> This is true in general, but if everyone decided to always used
> GID index 0, then all GIDs are guaranteed to be unique (I think I
> see what the intent of the statement in the draft was).

This sounds like a safer way to go, but I'm obviously an IB neophyte.

> As Bill pointed out, NAT probably does not look at macaddress/GID
> to make this differentiation. If you believe you have some protocol
> or system that needs to differentiate based on the IPoIB macaddress/GID,
> you should bring it up to the list; it will add weight to the
> argument that everyone must be required to (as opposed to recommended
> to) use GID index 0.

Based on Bill's clarification, I am no longer concerned about NAT.
I am only asking about how the WG intends to manage this stuff
when the identifiers are not globally unique.

Randy



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



From exim@www1.ietf.org  Thu Dec  4 00:08:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28212
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 00:08:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARlid-00072L-1M
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 00:08:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4583W9027045
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 00:08:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARlic-000728-SA
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 00:08:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28161
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 00:07:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARlia-00021J-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 00:08:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARlia-00021E-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 00:08:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARlia-00071d-Qw; Thu, 04 Dec 2003 00:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARliU-00070M-0Z
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 00:07:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28150
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 00:07:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARliR-000215-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 00:07:51 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARliQ-00020k-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 00:07:50 -0500
Received: from phys-hanwk-1 ([129.149.2.111])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB457LUR022652
	for <ipoverib@ietf.org>; Wed, 3 Dec 2003 21:07:21 -0800 (PST)
Received: from endeavour (endeavour.SFBay.Sun.COM [129.149.192.63])
 by hanwk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HPC0097JU88NO@hanwk-mail1.sfbay.sun.com> for ipoverib@ietf.org;
 Wed, 03 Dec 2003 21:07:21 -0800 (PST)
Date: Wed, 03 Dec 2003 21:07:20 -0800 (PST)
From: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Kanoj.Sarcar@Sun.COM, kashyapv@us.ibm.com
Cc: vivk@us.ibm.com, ipoverib@ietf.org, ipoverib-admin@ietf.org
Reply-to: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Message-id: <0HPC0097MU89NO@hanwk-mail1.sfbay.sun.com>
MIME-version: 1.0
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4p_5 SunOS 5.7 sun4u sparc
Content-type: TEXT/plain; charset=us-ascii
Content-MD5: xIopt/G9FU8AkZN6jjs4Tg==
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>


! From: Vivek Kashyap <kashyapv@us.ibm.com>
 
! Yes, the port's GUID is the manufacturer assigned EUI-64 id for the port. It 
is
! probably better to use the IBA term 'portGUID'.

yes, it seems to be sufficient to just reword GUID to something like
"portGUID(EUI-64)".

Note that there is slight ambiguity in the way GID0 is defined in 4.1.1 of
the spec; which is why I dont prefer changing the wording to "GID0" in the rfc.

<snip>
"...This GID is referred to as GID index 0 and is formed by techniques 3(a)
and 3(b) described below."
^^^
 
3(a) talks about how GID0 is formed with default-prefix(fe80)::EUI64
3(b) talks about how GID0 is formed with subnet-prefix::EUI64
3(c) talks about GIDs 1 and above.

So its better to leave the "IB subnet prefix" part of the GID definition in
the rfc(9.1.1) and just reword "GUID" to "portGUID(EUI-64)". That way an
endpoint does provide the GID0 formed with IB subnet prefix when available.
If the IB subnet prefix also happens to be the default-prefix, that's life.

As far as RECOMMENDED vs. MUST, going by the IETF standards, RECOMMENDED is
compelling enough for implementors to follow it blindly, still leaving room
for some clever implementations.

<snip>
3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

thx,
~Ajoy

! 
! Vivek
! 
! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
! 
! > Vivek Kashyap wrote:
! > >
! > > Kanoj,
! > >
! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed 
using this GUID, the CA's GUID or some other value. Any GID is unique in the IB 
fabric however only by using the port's GUID/EUI-64 identifier can one uniquely 
identify the port. The other GID's, as noted, can be applied to other ports too 
- though not concurrently. The GID formed using the EUI-64 identifier is the 
'GID at index 0'. I've made note of your comment and can clarify further as 
needed.
! > >
! > > wrt, using only GID at index 0 as in the MAC address, there have been 
proponents of using the other GIDs (non EUI-64 GID).
! > >
! > > Vivek
! >
! > Vivek,
! >
! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer 
assigned and
! > SM assigned values are required to be EUI-64 compliant (they differ only in 
u/l bits).
! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID is 
its EUI-64
! > identifier" might be confusing. Saying "GUID using manufacturer assigned 
EUI-64 identifier"
! > or better "GID index 0" removes all confusion. I think we agree on the 
intent, I just
! > want to make sure if you use the term GUID, you do specifically define what 
you mean
! > by it.
! >
! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
! >
! > 1. SM assigned GIDs are not that popular (anymore?)
! > 2. it allows determination of sender's ipoib address, thus allowing 
(receiver side)
! > implementations to be dlpiv2 conformant?
! >
! > Thanks.
! >
! > Kanoj
! >
! >
! >
! > > --
! > > Vivek Kashyap
! > > Linux Technology Center, IBM
! > > vivk@us.ibm.com
! > > kashyapv@us.ibm.com
! > > Ph: 503 578 3422 T/L: 775 3422
! > >
! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
! > >     Sent by: ipoverib-admin@ietf.org
! > >
! > >     12/02/2003 03:54 PM
! > >     Please respond to Kanoj.Sarcar
! > >
! > > Hi,
! > >
! > > It seems that certain parts of the
! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
! > > require clarification. For this discussion, please refer to
! > >
! > > 1. section 9.1 Link Information says:
! > > "The GID, if formed using the GUID, can be used to unambiguously
! > > identify an endpoint."
! > >
! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
! > > "It is RECOMMENDED that the GID formed by the combination of the
! > > IB subnet prefix and the port's GUID be included in the
! > > link-layer/hardware address."
! > >
! > > Can comment #2 be safely taken to mean that GID index 0 is
! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
! > > am not sure (after reading IBA 1.1 section 4.1) whether the
! > > term GUID refers only to the manufacturer assigned value that appears
! > > in lower 64 bits of GID index 0, or whether it also includes
! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
! > > was really intended, the comment should explicitly state so to prevent
! > > confusion.
! > >
! > > Also, to make things simple, is it reasonable to REQUIRE implementations
! > > to always use GID index 0 (maybe this depends on whether existing
! > > implementations all use GID0 only)? The reason this might be
! > > interesting is that when a node receives a packet without a GRH
! > > (whereby it already knows the sender's LID and QPN), it can possibly
! > > reverse lookup the sender's LID to identify the sender's GID index
! > > 0 and concatenate the sender's QPN to figure out the sender's link
! > > address. Thus, a receiver can always figure out the sender's address,
! > > even when a GRH is not present. This would be similar to ethernet,
! > > where a receiver can always determine a sender's address, and thus
! > > is more DLPIv2 (unitdata_indication) friendly.
! > >
! > > Regarding comment #1, what does "unambiguously identify an endpoint"
! > > mean? GIDs are unique in the subnet; and if an IP link contains
! > > members in multiple IBA subnets, the subnet prefixes will disambiguate
! > > which endport is being referred.
! > >
! > > Thanks.
! > >
! > > Kanoj
! > >
! > > _______________________________________________
! > > 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
! >
! >
! 
! __
! 
! Vivek Kashyap
! Linux Technology Center, IBM
! 
! 
! _______________________________________________
! 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 Dec  4 03:41:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16206
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 03:41:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARp2o-0008EJ-4Z
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 03:41:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB48f5TU031610
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 03:41:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARp2n-0008De-BW
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 03:41:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16160
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 03:40:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARp2k-0004Vu-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 03:41:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARp2k-0004Vr-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 03:41:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARp2l-0008Cv-5J; Thu, 04 Dec 2003 03:41:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARp1o-0008A9-VQ
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 03:40:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16128;
	Thu, 4 Dec 2003 03:39:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARp1j-0004V4-00; Thu, 04 Dec 2003 03:39:59 -0500
Received: from e33.co.us.ibm.com ([32.97.110.131])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARp1i-0004UX-00; Thu, 04 Dec 2003 03:39:59 -0500
Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32])
	by e33.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id hB48dTJh247830;
	Thu, 4 Dec 2003 03:39:29 -0500
Received: from w-vkashyap95.des.sequent.com (d03av02.boulder.ibm.com [9.17.193.82])
	by westrelay04.boulder.ibm.com (8.12.9/NCO/VER6.6) with ESMTP id hB48dMxb168862;
	Thu, 4 Dec 2003 01:39:28 -0700
Date: Wed, 3 Dec 2003 23:24:21 -0800 (Pacific Standard Time)
From: Vivek Kashyap <kashyapv@us.ibm.com>
To: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
cc: Kanoj.Sarcar@Sun.COM, <vivk@us.ibm.com>, <ipoverib@ietf.org>,
        <ipoverib-admin@ietf.org>
Subject: Re: [Ipoverib] GID clarifications
In-Reply-To: <0HPC0097MU89NO@hanwk-mail1.sfbay.sun.com>
Message-ID: <Pine.WNT.4.44.0312032225510.728-100000@w-vkashyap95.des.sequent.com>
X-X-Sender: kashyapv@imap.linux.ibm.com
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>

Ajoy,

I concur with your suggestions.

Vivek




On Wed, 3 Dec 2003, Ajoy C Siddabathuni wrote:

>
> ! From: Vivek Kashyap <kashyapv@us.ibm.com>
>
> ! Yes, the port's GUID is the manufacturer assigned EUI-64 id for the port. It
> is
> ! probably better to use the IBA term 'portGUID'.
>
> yes, it seems to be sufficient to just reword GUID to something like
> "portGUID(EUI-64)".
>
> Note that there is slight ambiguity in the way GID0 is defined in 4.1.1 of
> the spec; which is why I dont prefer changing the wording to "GID0" in the rfc.
>
> <snip>
> "...This GID is referred to as GID index 0 and is formed by techniques 3(a)
> and 3(b) described below."
> ^^^
>
> 3(a) talks about how GID0 is formed with default-prefix(fe80)::EUI64
> 3(b) talks about how GID0 is formed with subnet-prefix::EUI64
> 3(c) talks about GIDs 1 and above.
>
> So its better to leave the "IB subnet prefix" part of the GID definition in
> the rfc(9.1.1) and just reword "GUID" to "portGUID(EUI-64)". That way an
> endpoint does provide the GID0 formed with IB subnet prefix when available.
> If the IB subnet prefix also happens to be the default-prefix, that's life.
>
> As far as RECOMMENDED vs. MUST, going by the IETF standards, RECOMMENDED is
> compelling enough for implementors to follow it blindly, still leaving room
> for some clever implementations.
>
> <snip>
> 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
>    may exist valid reasons in particular circumstances to ignore a
>    particular item, but the full implications must be understood and
>    carefully weighed before choosing a different course.
>
> thx,
> ~Ajoy
>
> !
> ! Vivek
> !
> ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
> !
> ! > Vivek Kashyap wrote:
> ! > >
> ! > > Kanoj,
> ! > >
> ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed
> using this GUID, the CA's GUID or some other value. Any GID is unique in the IB
> fabric however only by using the port's GUID/EUI-64 identifier can one uniquely
> identify the port. The other GID's, as noted, can be applied to other ports too
> - though not concurrently. The GID formed using the EUI-64 identifier is the
> 'GID at index 0'. I've made note of your comment and can clarify further as
> needed.
> ! > >
> ! > > wrt, using only GID at index 0 as in the MAC address, there have been
> proponents of using the other GIDs (non EUI-64 GID).
> ! > >
> ! > > Vivek
> ! >
> ! > Vivek,
> ! >
> ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer
> assigned and
> ! > SM assigned values are required to be EUI-64 compliant (they differ only in
> u/l bits).
> ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID is
> its EUI-64
> ! > identifier" might be confusing. Saying "GUID using manufacturer assigned
> EUI-64 identifier"
> ! > or better "GID index 0" removes all confusion. I think we agree on the
> intent, I just
> ! > want to make sure if you use the term GUID, you do specifically define what
> you mean
> ! > by it.
> ! >
> ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
> ! >
> ! > 1. SM assigned GIDs are not that popular (anymore?)
> ! > 2. it allows determination of sender's ipoib address, thus allowing
> (receiver side)
> ! > implementations to be dlpiv2 conformant?
> ! >
> ! > Thanks.
> ! >
> ! > Kanoj
> ! >
> ! >
> ! >
> ! > > --
> ! > > Vivek Kashyap
> ! > > Linux Technology Center, IBM
> ! > > vivk@us.ibm.com
> ! > > kashyapv@us.ibm.com
> ! > > Ph: 503 578 3422 T/L: 775 3422
> ! > >
> ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
> ! > >     Sent by: ipoverib-admin@ietf.org
> ! > >
> ! > >     12/02/2003 03:54 PM
> ! > >     Please respond to Kanoj.Sarcar
> ! > >
> ! > > Hi,
> ! > >
> ! > > It seems that certain parts of the
> ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> ! > > require clarification. For this discussion, please refer to
> ! > >
> ! > > 1. section 9.1 Link Information says:
> ! > > "The GID, if formed using the GUID, can be used to unambiguously
> ! > > identify an endpoint."
> ! > >
> ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
> ! > > "It is RECOMMENDED that the GID formed by the combination of the
> ! > > IB subnet prefix and the port's GUID be included in the
> ! > > link-layer/hardware address."
> ! > >
> ! > > Can comment #2 be safely taken to mean that GID index 0 is
> ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
> ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
> ! > > term GUID refers only to the manufacturer assigned value that appears
> ! > > in lower 64 bits of GID index 0, or whether it also includes
> ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
> ! > > was really intended, the comment should explicitly state so to prevent
> ! > > confusion.
> ! > >
> ! > > Also, to make things simple, is it reasonable to REQUIRE implementations
> ! > > to always use GID index 0 (maybe this depends on whether existing
> ! > > implementations all use GID0 only)? The reason this might be
> ! > > interesting is that when a node receives a packet without a GRH
> ! > > (whereby it already knows the sender's LID and QPN), it can possibly
> ! > > reverse lookup the sender's LID to identify the sender's GID index
> ! > > 0 and concatenate the sender's QPN to figure out the sender's link
> ! > > address. Thus, a receiver can always figure out the sender's address,
> ! > > even when a GRH is not present. This would be similar to ethernet,
> ! > > where a receiver can always determine a sender's address, and thus
> ! > > is more DLPIv2 (unitdata_indication) friendly.
> ! > >
> ! > > Regarding comment #1, what does "unambiguously identify an endpoint"
> ! > > mean? GIDs are unique in the subnet; and if an IP link contains
> ! > > members in multiple IBA subnets, the subnet prefixes will disambiguate
> ! > > which endport is being referred.
> ! > >
> ! > > Thanks.
> ! > >
> ! > > Kanoj
> ! > >
> ! > > _______________________________________________
> ! > > 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
> ! >
> ! >
> !
> ! __
> !
> ! Vivek Kashyap
> ! Linux Technology Center, IBM
> !
> !
> ! _______________________________________________
> ! 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
>
>

__

Vivek Kashyap
Linux Technology Center, IBM


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



From exim@www1.ietf.org  Thu Dec  4 14:18:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09490
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 14:18:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyzH-0003gb-Fm
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 14:18:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4JI7ss014165
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 14:18:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyzH-0003gO-C3
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 14:18:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09463
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 14:17:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyzE-0006pp-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 14:18:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyzE-0006pm-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 14:18:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyzC-0003ez-9L; Thu, 04 Dec 2003 14:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARyyn-0003eI-Es
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 14:17:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09453
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 14:17:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyyk-0006pX-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 14:17:34 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARyyj-0006p5-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 14:17:33 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB4JH1UR020929
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 11:17:01 -0800 (PST)
Received: from Sun.COM (sr1-umpk-06.SFBay.Sun.COM [129.146.11.166])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPD007JDXKCGV40@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Thu, 04 Dec 2003 11:17:01 -0800 (PST)
Date: Thu, 04 Dec 2003 11:17:00 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Cc: kashyapv@us.ibm.com, vivk@us.ibm.com, ipoverib@ietf.org,
        ipoverib-admin@ietf.org
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FCF882C.48F735D4@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <0HPC0097MU89NO@hanwk-mail1.sfbay.sun.com>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ajoy C Siddabathuni wrote:
> 
> ! From: Vivek Kashyap <kashyapv@us.ibm.com>
> 
> ! Yes, the port's GUID is the manufacturer assigned EUI-64 id for the port. It
> is
> ! probably better to use the IBA term 'portGUID'.
> 
> yes, it seems to be sufficient to just reword GUID to something like
> "portGUID(EUI-64)".
> 
> Note that there is slight ambiguity in the way GID0 is defined in 4.1.1 of
> the spec; which is why I dont prefer changing the wording to "GID0" in the rfc.
> 
> <snip>
> "...This GID is referred to as GID index 0 and is formed by techniques 3(a)
> and 3(b) described below."
> ^^^
> 
> 3(a) talks about how GID0 is formed with default-prefix(fe80)::EUI64
> 3(b) talks about how GID0 is formed with subnet-prefix::EUI64
> 3(c) talks about GIDs 1 and above.
> 
> So its better to leave the "IB subnet prefix" part of the GID definition in
> the rfc(9.1.1) and just reword "GUID" to "portGUID(EUI-64)". That way an
> endpoint does provide the GID0 formed with IB subnet prefix when available.
> If the IB subnet prefix also happens to be the default-prefix, that's life.
> 

Hi,


> As far as RECOMMENDED vs. MUST, going by the IETF standards, RECOMMENDED is
> compelling enough for implementors to follow it blindly, still leaving room
> for some clever implementations.
> 
> <snip>
> 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
>    may exist valid reasons in particular circumstances to ignore a
>    particular item, but the full implications must be understood and
>    carefully weighed before choosing a different course.

Just to be careful, if a non DLPI system (eg Linux) uses GID1 for the mac
address, the Linux system itself will function perfectly (ignoring whatever
uniqueness problems there might be in choosing GID1 over GID0). The problem
will be that any _other_ DLPI based system on the subnet will possibly not be
able to interact 100% with the Linux box, even though the DLPI system itself 
uses GID0 per the draft recommendations. IE, for the Linux box, the "full
implications" are not local, but have to do with interop.

It seems a bit much to expect non DLPI systems (like Linux) to understand
what impact their using GID1 might have on _other_ DLPI based system. That
is why this issue should be addressed in the draft/rfc.

Thanks.

Kanoj
 
> 
> thx,
> ~Ajoy
> 
> !
> ! Vivek
> !
> ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
> !
> ! > Vivek Kashyap wrote:
> ! > >
> ! > > Kanoj,
> ! > >
> ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be formed
> using this GUID, the CA's GUID or some other value. Any GID is unique in the IB
> fabric however only by using the port's GUID/EUI-64 identifier can one uniquely
> identify the port. The other GID's, as noted, can be applied to other ports too
> - though not concurrently. The GID formed using the EUI-64 identifier is the
> 'GID at index 0'. I've made note of your comment and can clarify further as
> needed.
> ! > >
> ! > > wrt, using only GID at index 0 as in the MAC address, there have been
> proponents of using the other GIDs (non EUI-64 GID).
> ! > >
> ! > > Vivek
> ! >
> ! > Vivek,
> ! >
> ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer
> assigned and
> ! > SM assigned values are required to be EUI-64 compliant (they differ only in
> u/l bits).
> ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID is
> its EUI-64
> ! > identifier" might be confusing. Saying "GUID using manufacturer assigned
> EUI-64 identifier"
> ! > or better "GID index 0" removes all confusion. I think we agree on the
> intent, I just
> ! > want to make sure if you use the term GUID, you do specifically define what
> you mean
> ! > by it.
> ! >
> ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
> ! >
> ! > 1. SM assigned GIDs are not that popular (anymore?)
> ! > 2. it allows determination of sender's ipoib address, thus allowing
> (receiver side)
> ! > implementations to be dlpiv2 conformant?
> ! >
> ! > Thanks.
> ! >
> ! > Kanoj
> ! >
> ! >
> ! >
> ! > > --
> ! > > Vivek Kashyap
> ! > > Linux Technology Center, IBM
> ! > > vivk@us.ibm.com
> ! > > kashyapv@us.ibm.com
> ! > > Ph: 503 578 3422 T/L: 775 3422
> ! > >
> ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
> ! > >     Sent by: ipoverib-admin@ietf.org
> ! > >
> ! > >     12/02/2003 03:54 PM
> ! > >     Please respond to Kanoj.Sarcar
> ! > >
> ! > > Hi,
> ! > >
> ! > > It seems that certain parts of the
> ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> ! > > require clarification. For this discussion, please refer to
> ! > >
> ! > > 1. section 9.1 Link Information says:
> ! > > "The GID, if formed using the GUID, can be used to unambiguously
> ! > > identify an endpoint."
> ! > >
> ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
> ! > > "It is RECOMMENDED that the GID formed by the combination of the
> ! > > IB subnet prefix and the port's GUID be included in the
> ! > > link-layer/hardware address."
> ! > >
> ! > > Can comment #2 be safely taken to mean that GID index 0 is
> ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
> ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
> ! > > term GUID refers only to the manufacturer assigned value that appears
> ! > > in lower 64 bits of GID index 0, or whether it also includes
> ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
> ! > > was really intended, the comment should explicitly state so to prevent
> ! > > confusion.
> ! > >
> ! > > Also, to make things simple, is it reasonable to REQUIRE implementations
> ! > > to always use GID index 0 (maybe this depends on whether existing
> ! > > implementations all use GID0 only)? The reason this might be
> ! > > interesting is that when a node receives a packet without a GRH
> ! > > (whereby it already knows the sender's LID and QPN), it can possibly
> ! > > reverse lookup the sender's LID to identify the sender's GID index
> ! > > 0 and concatenate the sender's QPN to figure out the sender's link
> ! > > address. Thus, a receiver can always figure out the sender's address,
> ! > > even when a GRH is not present. This would be similar to ethernet,
> ! > > where a receiver can always determine a sender's address, and thus
> ! > > is more DLPIv2 (unitdata_indication) friendly.
> ! > >
> ! > > Regarding comment #1, what does "unambiguously identify an endpoint"
> ! > > mean? GIDs are unique in the subnet; and if an IP link contains
> ! > > members in multiple IBA subnets, the subnet prefixes will disambiguate
> ! > > which endport is being referred.
> ! > >
> ! > > Thanks.
> ! > >
> ! > > Kanoj
> ! > >
> ! > > _______________________________________________
> ! > > 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
> ! >
> ! >
> !
> ! __
> !
> ! Vivek Kashyap
> ! Linux Technology Center, IBM
> !
> !
> ! _______________________________________________
> ! 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 Dec  4 17:16:32 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20379
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 17:16:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS1lh-0003t4-Sa
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 17:16:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB4MGHpa014938
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 17:16:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS1lh-0003sp-LV
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 17:16:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20333
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 17:16:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS1le-0002uD-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 17:16:14 -0500
Received: from manatick.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS1ld-0002tK-01
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 17:16:14 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AS1bw-0006Bz-CB
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 17:06:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS1bl-0003Nq-Om; Thu, 04 Dec 2003 17:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS1an-0003Mg-BT
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 17:05:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19819
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 17:04:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS1ak-0002gq-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 17:04:58 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS1aj-0002g5-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 17:04:57 -0500
Received: from phys-hanwk-1 ([129.149.2.111])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB4M4QUR028678
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 14:04:26 -0800 (PST)
Received: from endeavour (endeavour.SFBay.Sun.COM [129.149.192.63])
 by hanwk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HPE00AT75BDQ4@hanwk-mail1.sfbay.sun.com> for ipoverib@ietf.org;
 Thu, 04 Dec 2003 14:04:26 -0800 (PST)
Date: Thu, 04 Dec 2003 14:04:25 -0800 (PST)
From: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Ajoy.Siddabathuni@Sun.COM, Kanoj.Sarcar@Sun.COM
Cc: kashyapv@us.ibm.com, vivk@us.ibm.com, ipoverib@ietf.org,
        ipoverib-admin@ietf.org
Reply-to: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Message-id: <0HPE00AT85BDQ4@hanwk-mail1.sfbay.sun.com>
MIME-version: 1.0
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4p_5 SunOS 5.7 sun4u sparc
Content-type: TEXT/plain; charset=us-ascii
Content-MD5: LZ//ahfmpsOL+RhkAA9lKA==
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>


! > As far as RECOMMENDED vs. MUST, going by the IETF standards, RECOMMENDED is
! > compelling enough for implementors to follow it blindly, still leaving room
! > for some clever implementations.
! > 
! > <snip>
! > 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
! >    may exist valid reasons in particular circumstances to ignore a
! >    particular item, but the full implications must be understood and
! >    carefully weighed before choosing a different course.
! 
! Just to be careful, if a non DLPI system (eg Linux) uses GID1 for the mac
! address, the Linux system itself will function perfectly (ignoring whatever
! uniqueness problems there might be in choosing GID1 over GID0). The problem
! will be that any _other_ DLPI based system on the subnet will possibly not be
! able to interact 100% with the Linux box, even though the DLPI system itself 
! uses GID0 per the draft recommendations. IE, for the Linux box, the "full
! implications" are not local, but have to do with interop.
! 
! It seems a bit much to expect non DLPI systems (like Linux) to understand
! what impact their using GID1 might have on _other_ DLPI based system. That
! is why this issue should be addressed in the draft/rfc.

The analysis provided seems to rely on two assumptions -

1) Linux/non-dlpi systems are free to use GID1 and thus will not interoperate
   with Solaris
2) We expect implementations to interoperate in spite of the fact
   that they willfully deviated from the spec.

Given the current definition of the ipoib pkt format, the issue on hand does 
not necessarily only apply to DLPI systems, any application talking to the ipoib
driver directly (for whatever purposes) would have to deal with src/dst(IB)
address lookup problems; when that information is not provided explicitly by the
driver when passing up pkts. Thus, even Linux and other OSes should be
implementing the rfc by its letter and intent.

Finally, if we were to make a case with such assumptions as above, do we then
reconsider all uses of "RECOMMENDED/SHOULD" in the rfc.

thx,
~Ajoy


! 
! Thanks.
! 
! Kanoj
!  
! > 
! > thx,
! > ~Ajoy
! > 
! > !
! > ! Vivek
! > !
! > ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
! > !
! > ! > Vivek Kashyap wrote:
! > ! > >
! > ! > > Kanoj,
! > ! > >
! > ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be 
formed
! > using this GUID, the CA's GUID or some other value. Any GID is unique in the 
IB
! > fabric however only by using the port's GUID/EUI-64 identifier can one 
uniquely
! > identify the port. The other GID's, as noted, can be applied to other ports 
too
! > - though not concurrently. The GID formed using the EUI-64 identifier is the
! > 'GID at index 0'. I've made note of your comment and can clarify further as
! > needed.
! > ! > >
! > ! > > wrt, using only GID at index 0 as in the MAC address, there have been
! > proponents of using the other GIDs (non EUI-64 GID).
! > ! > >
! > ! > > Vivek
! > ! >
! > ! > Vivek,
! > ! >
! > ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer
! > assigned and
! > ! > SM assigned values are required to be EUI-64 compliant (they differ only 
in
! > u/l bits).
! > ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID 
is
! > its EUI-64
! > ! > identifier" might be confusing. Saying "GUID using manufacturer assigned
! > EUI-64 identifier"
! > ! > or better "GID index 0" removes all confusion. I think we agree on the
! > intent, I just
! > ! > want to make sure if you use the term GUID, you do specifically define 
what
! > you mean
! > ! > by it.
! > ! >
! > ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
! > ! >
! > ! > 1. SM assigned GIDs are not that popular (anymore?)
! > ! > 2. it allows determination of sender's ipoib address, thus allowing
! > (receiver side)
! > ! > implementations to be dlpiv2 conformant?
! > ! >
! > ! > Thanks.
! > ! >
! > ! > Kanoj
! > ! >
! > ! >
! > ! >
! > ! > > --
! > ! > > Vivek Kashyap
! > ! > > Linux Technology Center, IBM
! > ! > > vivk@us.ibm.com
! > ! > > kashyapv@us.ibm.com
! > ! > > Ph: 503 578 3422 T/L: 775 3422
! > ! > >
! > ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
! > ! > >     Sent by: ipoverib-admin@ietf.org
! > ! > >
! > ! > >     12/02/2003 03:54 PM
! > ! > >     Please respond to Kanoj.Sarcar
! > ! > >
! > ! > > Hi,
! > ! > >
! > ! > > It seems that certain parts of the
! > ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
! > ! > > require clarification. For this discussion, please refer to
! > ! > >
! > ! > > 1. section 9.1 Link Information says:
! > ! > > "The GID, if formed using the GUID, can be used to unambiguously
! > ! > > identify an endpoint."
! > ! > >
! > ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
! > ! > > "It is RECOMMENDED that the GID formed by the combination of the
! > ! > > IB subnet prefix and the port's GUID be included in the
! > ! > > link-layer/hardware address."
! > ! > >
! > ! > > Can comment #2 be safely taken to mean that GID index 0 is
! > ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
! > ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
! > ! > > term GUID refers only to the manufacturer assigned value that appears
! > ! > > in lower 64 bits of GID index 0, or whether it also includes
! > ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
! > ! > > was really intended, the comment should explicitly state so to prevent
! > ! > > confusion.
! > ! > >
! > ! > > Also, to make things simple, is it reasonable to REQUIRE 
implementations
! > ! > > to always use GID index 0 (maybe this depends on whether existing
! > ! > > implementations all use GID0 only)? The reason this might be
! > ! > > interesting is that when a node receives a packet without a GRH
! > ! > > (whereby it already knows the sender's LID and QPN), it can possibly
! > ! > > reverse lookup the sender's LID to identify the sender's GID index
! > ! > > 0 and concatenate the sender's QPN to figure out the sender's link
! > ! > > address. Thus, a receiver can always figure out the sender's address,
! > ! > > even when a GRH is not present. This would be similar to ethernet,
! > ! > > where a receiver can always determine a sender's address, and thus
! > ! > > is more DLPIv2 (unitdata_indication) friendly.
! > ! > >
! > ! > > Regarding comment #1, what does "unambiguously identify an endpoint"
! > ! > > mean? GIDs are unique in the subnet; and if an IP link contains
! > ! > > members in multiple IBA subnets, the subnet prefixes will disambiguate
! > ! > > which endport is being referred.
! > ! > >
! > ! > > Thanks.
! > ! > >
! > ! > > Kanoj
! > ! > >
! > ! > > _______________________________________________
! > ! > > 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
! > ! >
! > ! >
! > !
! > ! __
! > !
! > ! Vivek Kashyap
! > ! Linux Technology Center, IBM
! > !
! > !
! > ! _______________________________________________
! > ! 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


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



From exim@www1.ietf.org  Thu Dec  4 19:45:23 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28523
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 19:45:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS45g-0001jS-DW
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 19:45:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB50j4LI006652
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 19:45:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS45g-0001jD-9S
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 19:45:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28490
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 19:44:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS45e-0005nq-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 19:45:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS45e-0005nn-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 19:45:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS45d-0001ii-3m; Thu, 04 Dec 2003 19:45:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS44g-0001i1-JO
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 19:44:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28479
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 19:43:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS44e-0005nP-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 19:44:00 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS44Z-0005nF-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 19:44:00 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id hB50hsPj023393
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 17:43:55 -0700 (MST)
Received: from Sun.COM (sr1-umpk-06.SFBay.Sun.COM [129.146.11.166])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPE007AGCP6GW80@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Thu, 04 Dec 2003 16:43:54 -0800 (PST)
Date: Thu, 04 Dec 2003 16:43:54 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Cc: kashyapv@us.ibm.com, vivk@us.ibm.com, ipoverib@ietf.org,
        ipoverib-admin@ietf.org, Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FCFD4CA.3DBB8D2@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <0HPE00AT85BDQ4@hanwk-mail1.sfbay.sun.com>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ajoy C Siddabathuni wrote:
> 
> ! > As far as RECOMMENDED vs. MUST, going by the IETF standards, RECOMMENDED is
> ! > compelling enough for implementors to follow it blindly, still leaving room
> ! > for some clever implementations.
> ! >
> ! > <snip>
> ! > 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
> ! >    may exist valid reasons in particular circumstances to ignore a
> ! >    particular item, but the full implications must be understood and
> ! >    carefully weighed before choosing a different course.
> !
> ! Just to be careful, if a non DLPI system (eg Linux) uses GID1 for the mac
> ! address, the Linux system itself will function perfectly (ignoring whatever
> ! uniqueness problems there might be in choosing GID1 over GID0). The problem
> ! will be that any _other_ DLPI based system on the subnet will possibly not be
> ! able to interact 100% with the Linux box, even though the DLPI system itself
> ! uses GID0 per the draft recommendations. IE, for the Linux box, the "full
> ! implications" are not local, but have to do with interop.
> !
> ! It seems a bit much to expect non DLPI systems (like Linux) to understand
> ! what impact their using GID1 might have on _other_ DLPI based system. That
> ! is why this issue should be addressed in the draft/rfc.
> 
> The analysis provided seems to rely on two assumptions -
> 

Hi,

> 1) Linux/non-dlpi systems are free to use GID1 and thus will not interoperate
>    with Solaris
> 2) We expect implementations to interoperate in spite of the fact
>    that they willfully deviated from the spec.

"Willfully deviated" might be too strong, given that the working group currently
chooses to allow the flexibility of using other GIDs; what seems to be under
discussion is the relative benefit of allowing that flexibility, if there is a
cost to be paid in terms of interop.

> 
> Given the current definition of the ipoib pkt format, the issue on hand does
> not necessarily only apply to DLPI systems, any application talking to the ipoib
> driver directly (for whatever purposes) would have to deal with src/dst(IB)
> address lookup problems; when that information is not provided explicitly by the
> driver when passing up pkts. Thus, even Linux and other OSes should be
> implementing the rfc by its letter and intent.

Here is the difference between DLPI and nonDLPI systems: on non DLPI systems, if
the os allows raw access to the interface, then programs utilizing the raw
interface must neccesarily be aware of the underlying packet format, and either
deal with sender address not being present, or know how to decipher it from the
packet header. If you took a program that runs on raw Ethernet, there is a very
good chance you will need to modify the program to run on raw IPoIB.

With DLPI, there is an attempt to reduce the media awareness of programs, by
requiring the os to provide some meta information for every packet received
(sender's mac address in this case). In practice, this does not guarantee that 
a program that runs on ethernet will run unmodified on IPoIB, but there is a 
good chance that it might. 

As you point out, determining the sender's address is problematic in either
case (dlpi or non dlpi): in the case of dlpi though, the onus is on the driver
to provide the information (dlpi apps expect it), whereas in non dlpi case, 
programs can choose to solve the problem in their own unique ways.
Using GID0 always is one way to solve the problem for everyone, the other is to require 
using GRH for every packet transmitted, but that has a performance impact and
is thus not desirable.

> 
> Finally, if we were to make a case with such assumptions as above, do we then
> reconsider all uses of "RECOMMENDED/SHOULD" in the rfc.
>

If there is an interop issue, or a case where some established practice or
software breaks (due to an implementation not following recommendation), in my 
opinion, we should think about the item seriously. 

Is there a reason you are opposed to changing the RECOMMENDED to a REQUIRED
in this specific case? Vivek mentioned there was inclination towards allowing
the flexibility, and I generally agree to that; but in this case, curtailing
the flexibility is solving a problem, without creating any new ones I am aware 
of.

Thanks.

Kanoj



> thx,
> ~Ajoy
> 
> !
> ! Thanks.
> !
> ! Kanoj
> !
> ! >
> ! > thx,
> ! > ~Ajoy
> ! >
> ! > !
> ! > ! Vivek
> ! > !
> ! > ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
> ! > !
> ! > ! > Vivek Kashyap wrote:
> ! > ! > >
> ! > ! > > Kanoj,
> ! > ! > >
> ! > ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be
> formed
> ! > using this GUID, the CA's GUID or some other value. Any GID is unique in the
> IB
> ! > fabric however only by using the port's GUID/EUI-64 identifier can one
> uniquely
> ! > identify the port. The other GID's, as noted, can be applied to other ports
> too
> ! > - though not concurrently. The GID formed using the EUI-64 identifier is the
> ! > 'GID at index 0'. I've made note of your comment and can clarify further as
> ! > needed.
> ! > ! > >
> ! > ! > > wrt, using only GID at index 0 as in the MAC address, there have been
> ! > proponents of using the other GIDs (non EUI-64 GID).
> ! > ! > >
> ! > ! > > Vivek
> ! > ! >
> ! > ! > Vivek,
> ! > ! >
> ! > ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, manufacturer
> ! > assigned and
> ! > ! > SM assigned values are required to be EUI-64 compliant (they differ only
> in
> ! > u/l bits).
> ! > ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying "GUID
> is
> ! > its EUI-64
> ! > ! > identifier" might be confusing. Saying "GUID using manufacturer assigned
> ! > EUI-64 identifier"
> ! > ! > or better "GID index 0" removes all confusion. I think we agree on the
> ! > intent, I just
> ! > ! > want to make sure if you use the term GUID, you do specifically define
> what
> ! > you mean
> ! > ! > by it.
> ! > ! >
> ! > ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given that
> ! > ! >
> ! > ! > 1. SM assigned GIDs are not that popular (anymore?)
> ! > ! > 2. it allows determination of sender's ipoib address, thus allowing
> ! > (receiver side)
> ! > ! > implementations to be dlpiv2 conformant?
> ! > ! >
> ! > ! > Thanks.
> ! > ! >
> ! > ! > Kanoj
> ! > ! >
> ! > ! >
> ! > ! >
> ! > ! > > --
> ! > ! > > Vivek Kashyap
> ! > ! > > Linux Technology Center, IBM
> ! > ! > > vivk@us.ibm.com
> ! > ! > > kashyapv@us.ibm.com
> ! > ! > > Ph: 503 578 3422 T/L: 775 3422
> ! > ! > >
> ! > ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
> ! > ! > >     Sent by: ipoverib-admin@ietf.org
> ! > ! > >
> ! > ! > >     12/02/2003 03:54 PM
> ! > ! > >     Please respond to Kanoj.Sarcar
> ! > ! > >
> ! > ! > > Hi,
> ! > ! > >
> ! > ! > > It seems that certain parts of the
> ! > ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> ! > ! > > require clarification. For this discussion, please refer to
> ! > ! > >
> ! > ! > > 1. section 9.1 Link Information says:
> ! > ! > > "The GID, if formed using the GUID, can be used to unambiguously
> ! > ! > > identify an endpoint."
> ! > ! > >
> ! > ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) says:
> ! > ! > > "It is RECOMMENDED that the GID formed by the combination of the
> ! > ! > > IB subnet prefix and the port's GUID be included in the
> ! > ! > > link-layer/hardware address."
> ! > ! > >
> ! > ! > > Can comment #2 be safely taken to mean that GID index 0 is
> ! > ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
> ! > ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
> ! > ! > > term GUID refers only to the manufacturer assigned value that appears
> ! > ! > > in lower 64 bits of GID index 0, or whether it also includes
> ! > ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 0
> ! > ! > > was really intended, the comment should explicitly state so to prevent
> ! > ! > > confusion.
> ! > ! > >
> ! > ! > > Also, to make things simple, is it reasonable to REQUIRE
> implementations
> ! > ! > > to always use GID index 0 (maybe this depends on whether existing
> ! > ! > > implementations all use GID0 only)? The reason this might be
> ! > ! > > interesting is that when a node receives a packet without a GRH
> ! > ! > > (whereby it already knows the sender's LID and QPN), it can possibly
> ! > ! > > reverse lookup the sender's LID to identify the sender's GID index
> ! > ! > > 0 and concatenate the sender's QPN to figure out the sender's link
> ! > ! > > address. Thus, a receiver can always figure out the sender's address,
> ! > ! > > even when a GRH is not present. This would be similar to ethernet,
> ! > ! > > where a receiver can always determine a sender's address, and thus
> ! > ! > > is more DLPIv2 (unitdata_indication) friendly.
> ! > ! > >
> ! > ! > > Regarding comment #1, what does "unambiguously identify an endpoint"
> ! > ! > > mean? GIDs are unique in the subnet; and if an IP link contains
> ! > ! > > members in multiple IBA subnets, the subnet prefixes will disambiguate
> ! > ! > > which endport is being referred.
> ! > ! > >
> ! > ! > > Thanks.
> ! > ! > >
> ! > ! > > Kanoj
> ! > ! > >
> ! > ! > > _______________________________________________
> ! > ! > > 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
> ! > ! >
> ! > ! >
> ! > !
> ! > ! __
> ! > !
> ! > ! Vivek Kashyap
> ! > ! Linux Technology Center, IBM
> ! > !
> ! > !
> ! > ! _______________________________________________
> ! > ! 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

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



From exim@www1.ietf.org  Thu Dec  4 21:02:04 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01009
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 21:02:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5Hv-0004Bk-A0
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 21:01:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB521lBI016079
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 21:01:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5Hv-0004BG-4k
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 21:01:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00981
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 21:01:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Hs-0006u8-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 21:01:44 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Hs-0006u5-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 21:01:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5HB-0004Ap-Cm; Thu, 04 Dec 2003 21:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5Gs-0004AE-17
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 21:00:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA00968
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 21:00:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Gm-0006sh-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 21:00:36 -0500
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Gl-0006sO-00
	for ipoverib@ietf.org; Thu, 04 Dec 2003 21:00:36 -0500
Received: from phys-hanwk-1 ([129.149.2.111])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id hB5205UR025750
	for <ipoverib@ietf.org>; Thu, 4 Dec 2003 18:00:05 -0800 (PST)
Received: from endeavour (endeavour.SFBay.Sun.COM [129.149.192.63])
 by hanwk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with SMTP id <0HPE00I0CG8550@hanwk-mail1.sfbay.sun.com> for ipoverib@ietf.org;
 Thu, 04 Dec 2003 18:00:05 -0800 (PST)
Date: Thu, 04 Dec 2003 18:00:05 -0800 (PST)
From: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Ajoy.Siddabathuni@Sun.COM, Kanoj.Sarcar@Sun.COM
Cc: kashyapv@us.ibm.com, vivk@us.ibm.com, ipoverib@ietf.org,
        ipoverib-admin@ietf.org, Kanoj.Sarcar@Sun.COM
Reply-to: Ajoy C Siddabathuni <Ajoy.Siddabathuni@Sun.COM>
Message-id: <0HPE00I0EG8550@hanwk-mail1.sfbay.sun.com>
MIME-version: 1.0
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.4p_5 SunOS 5.7 sun4u sparc
Content-type: TEXT/plain; charset=us-ascii
Content-MD5: vtoSiLoCVEs4P41VK68e/w==
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>


! As you point out, determining the sender's address is problematic in either
! case (dlpi or non dlpi): in the case of dlpi though, the onus is on the driver
! to provide the information (dlpi apps expect it), whereas in non dlpi case, 
! programs can choose to solve the problem in their own unique ways.

In either case, if the driver can determine/pass some information about the
pkt's underlying transport(ud qp in this case) hdr details to the app, then
that app will have an easier time figuring out the rest.

! Using GID0 always is one way to solve the problem for everyone, the other is 
to require 
! using GRH for every packet transmitted, but that has a performance impact and
! is thus not desirable.
! 
! > 
! > Finally, if we were to make a case with such assumptions as above, do we 
then
! > reconsider all uses of "RECOMMENDED/SHOULD" in the rfc.
! >
! 
! If there is an interop issue, or a case where some established practice or
! software breaks (due to an implementation not following recommendation), in my 
! opinion, we should think about the item seriously. 

Usually we seriously think about fixing the erring implementation, if it was
meant to interoperate; not go about rewriting specs; that said, in general
flexibility is good, but it is also well understood that going by the rfc's
recommendations will buy you interoperability; and the current wording seems
to be consistent with that.

~Ajoy
 
! Is there a reason you are opposed to changing the RECOMMENDED to a REQUIRED
! in this specific case? Vivek mentioned there was inclination towards allowing
! the flexibility, and I generally agree to that; but in this case, curtailing
! the flexibility is solving a problem, without creating any new ones I am aware 
! of.
! 
! Thanks.
! 
! Kanoj
! 
! 
! 
! > thx,
! > ~Ajoy
! > 
! > !
! > ! Thanks.
! > !
! > ! Kanoj
! > !
! > ! >
! > ! > thx,
! > ! > ~Ajoy
! > ! >
! > ! > !
! > ! > ! Vivek
! > ! > !
! > ! > ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
! > ! > !
! > ! > ! > Vivek Kashyap wrote:
! > ! > ! > >
! > ! > ! > > Kanoj,
! > ! > ! > >
! > ! > ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn can be
! > formed
! > ! > using this GUID, the CA's GUID or some other value. Any GID is unique in 
the
! > IB
! > ! > fabric however only by using the port's GUID/EUI-64 identifier can one
! > uniquely
! > ! > identify the port. The other GID's, as noted, can be applied to other 
ports
! > too
! > ! > - though not concurrently. The GID formed using the EUI-64 identifier is 
the
! > ! > 'GID at index 0'. I've made note of your comment and can clarify further 
as
! > ! > needed.
! > ! > ! > >
! > ! > ! > > wrt, using only GID at index 0 as in the MAC address, there have 
been
! > ! > proponents of using the other GIDs (non EUI-64 GID).
! > ! > ! > >
! > ! > ! > > Vivek
! > ! > ! >
! > ! > ! > Vivek,
! > ! > ! >
! > ! > ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2, 
manufacturer
! > ! > assigned and
! > ! > ! > SM assigned values are required to be EUI-64 compliant (they differ 
only
! > in
! > ! > u/l bits).
! > ! > ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus saying 
"GUID
! > is
! > ! > its EUI-64
! > ! > ! > identifier" might be confusing. Saying "GUID using manufacturer 
assigned
! > ! > EUI-64 identifier"
! > ! > ! > or better "GID index 0" removes all confusion. I think we agree on 
the
! > ! > intent, I just
! > ! > ! > want to make sure if you use the term GUID, you do specifically 
define
! > what
! > ! > you mean
! > ! > ! > by it.
! > ! > ! >
! > ! > ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering given 
that
! > ! > ! >
! > ! > ! > 1. SM assigned GIDs are not that popular (anymore?)
! > ! > ! > 2. it allows determination of sender's ipoib address, thus allowing
! > ! > (receiver side)
! > ! > ! > implementations to be dlpiv2 conformant?
! > ! > ! >
! > ! > ! > Thanks.
! > ! > ! >
! > ! > ! > Kanoj
! > ! > ! >
! > ! > ! >
! > ! > ! >
! > ! > ! > > --
! > ! > ! > > Vivek Kashyap
! > ! > ! > > Linux Technology Center, IBM
! > ! > ! > > vivk@us.ibm.com
! > ! > ! > > kashyapv@us.ibm.com
! > ! > ! > > Ph: 503 578 3422 T/L: 775 3422
! > ! > ! > >
! > ! > ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
! > ! > ! > >     Sent by: ipoverib-admin@ietf.org
! > ! > ! > >
! > ! > ! > >     12/02/2003 03:54 PM
! > ! > ! > >     Please respond to Kanoj.Sarcar
! > ! > ! > >
! > ! > ! > > Hi,
! > ! > ! > >
! > ! > ! > > It seems that certain parts of the
! > ! > ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
! > ! > ! > > require clarification. For this discussion, please refer to
! > ! > ! > >
! > ! > ! > > 1. section 9.1 Link Information says:
! > ! > ! > > "The GID, if formed using the GUID, can be used to unambiguously
! > ! > ! > > identify an endpoint."
! > ! > ! > >
! > ! > ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part c) 
says:
! > ! > ! > > "It is RECOMMENDED that the GID formed by the combination of the
! > ! > ! > > IB subnet prefix and the port's GUID be included in the
! > ! > ! > > link-layer/hardware address."
! > ! > ! > >
! > ! > ! > > Can comment #2 be safely taken to mean that GID index 0 is
! > ! > ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since I
! > ! > ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
! > ! > ! > > term GUID refers only to the manufacturer assigned value that 
appears
! > ! > ! > > in lower 64 bits of GID index 0, or whether it also includes
! > ! > ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID index 
0
! > ! > ! > > was really intended, the comment should explicitly state so to 
prevent
! > ! > ! > > confusion.
! > ! > ! > >
! > ! > ! > > Also, to make things simple, is it reasonable to REQUIRE
! > implementations
! > ! > ! > > to always use GID index 0 (maybe this depends on whether existing
! > ! > ! > > implementations all use GID0 only)? The reason this might be
! > ! > ! > > interesting is that when a node receives a packet without a GRH
! > ! > ! > > (whereby it already knows the sender's LID and QPN), it can 
possibly
! > ! > ! > > reverse lookup the sender's LID to identify the sender's GID index
! > ! > ! > > 0 and concatenate the sender's QPN to figure out the sender's link
! > ! > ! > > address. Thus, a receiver can always figure out the sender's 
address,
! > ! > ! > > even when a GRH is not present. This would be similar to ethernet,
! > ! > ! > > where a receiver can always determine a sender's address, and thus
! > ! > ! > > is more DLPIv2 (unitdata_indication) friendly.
! > ! > ! > >
! > ! > ! > > Regarding comment #1, what does "unambiguously identify an 
endpoint"
! > ! > ! > > mean? GIDs are unique in the subnet; and if an IP link contains
! > ! > ! > > members in multiple IBA subnets, the subnet prefixes will 
disambiguate
! > ! > ! > > which endport is being referred.
! > ! > ! > >
! > ! > ! > > Thanks.
! > ! > ! > >
! > ! > ! > > Kanoj
! > ! > ! > >
! > ! > ! > > _______________________________________________
! > ! > ! > > 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
! > ! > ! >
! > ! > ! >
! > ! > !
! > ! > ! __
! > ! > !
! > ! > ! Vivek Kashyap
! > ! > ! Linux Technology Center, IBM
! > ! > !
! > ! > !
! > ! > ! _______________________________________________
! > ! > ! 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


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



From exim@www1.ietf.org  Thu Dec  4 21:05:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01124
	for <ipoverib-archive@odin.ietf.org>; Thu, 4 Dec 2003 21:05:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5L7-0004Iw-QT
	for ipoverib-archive@odin.ietf.org; Thu, 04 Dec 2003 21:05:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5255UL016540
	for ipoverib-archive@odin.ietf.org; Thu, 4 Dec 2003 21:05:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5L6-0004Hi-9k
	for ipoverib-web-archive@optimus.ietf.org; Thu, 04 Dec 2003 21:05:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01081
	for <ipoverib-web-archive@ietf.org>; Thu, 4 Dec 2003 21:04:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5L3-0006wG-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 21:05:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5L3-0006wD-00
	for ipoverib-web-archive@ietf.org; Thu, 04 Dec 2003 21:05:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5L5-0004HS-9P; Thu, 04 Dec 2003 21:05:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AS5Kz-0004GZ-RJ
	for ipoverib@optimus.ietf.org; Thu, 04 Dec 2003 21:04:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01074;
	Thu, 4 Dec 2003 21:04:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Kx-0006w4-00; Thu, 04 Dec 2003 21:04:55 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AS5Kw-0006vk-00; Thu, 04 Dec 2003 21:04:54 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hB51fS100682;
	Thu, 4 Dec 2003 20:41:28 -0500
From: "bill" <bill@strahm.net>
To: <Kanoj.Sarcar@Sun.COM>,
        "'Ajoy C Siddabathuni'" <Ajoy.Siddabathuni@Sun.COM>
Cc: <kashyapv@us.ibm.com>, <vivk@us.ibm.com>, <ipoverib@ietf.org>,
        <ipoverib-admin@ietf.org>
Subject: RE: [Ipoverib] GID clarifications
Date: Thu, 4 Dec 2003 18:04:16 -0800
Message-ID: <000401c3bad4$17d60180$f5d912c0@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
In-Reply-To: <3FCFD4CA.3DBB8D2@Sun.COM>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Ok, let me ask a few questions to lead us toward concensus

1) Does anyone give a compelling reason to use anything but GID0 for
IPoIB - what is the benefit of doing this ?

2) Does anyone have an implementation that uses anything but GID0 for
IPoIB ?

If I do not hear any counter arguments by next Friday - I would like to
ask for concensus on MUST use GID0

Bill

-----Original Message-----
From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf
Of Kanoj Sarcar
Sent: Thursday, December 04, 2003 4:44 PM
To: Ajoy C Siddabathuni
Cc: kashyapv@us.ibm.com; vivk@us.ibm.com; ipoverib@ietf.org;
ipoverib-admin@ietf.org; Kanoj Sarcar
Subject: Re: [Ipoverib] GID clarifications


Ajoy C Siddabathuni wrote:
> 
> ! > As far as RECOMMENDED vs. MUST, going by the IETF standards, 
> RECOMMENDED is ! > compelling enough for implementors to follow it 
> blindly, still leaving room ! > for some clever implementations. ! >
> ! > <snip>
> ! > 3. SHOULD   This word, or the adjective "RECOMMENDED", mean that
there
> ! >    may exist valid reasons in particular circumstances to ignore a
> ! >    particular item, but the full implications must be understood
and
> ! >    carefully weighed before choosing a different course.
> !
> ! Just to be careful, if a non DLPI system (eg Linux) uses GID1 for
the mac
> ! address, the Linux system itself will function perfectly (ignoring
whatever
> ! uniqueness problems there might be in choosing GID1 over GID0). The
problem
> ! will be that any _other_ DLPI based system on the subnet will
possibly not be
> ! able to interact 100% with the Linux box, even though the DLPI
system itself
> ! uses GID0 per the draft recommendations. IE, for the Linux box, the
"full
> ! implications" are not local, but have to do with interop.
> !
> ! It seems a bit much to expect non DLPI systems (like Linux) to
understand
> ! what impact their using GID1 might have on _other_ DLPI based
system. That
> ! is why this issue should be addressed in the draft/rfc.
> 
> The analysis provided seems to rely on two assumptions -
> 

Hi,

> 1) Linux/non-dlpi systems are free to use GID1 and thus will not
interoperate
>    with Solaris
> 2) We expect implementations to interoperate in spite of the fact
>    that they willfully deviated from the spec.

"Willfully deviated" might be too strong, given that the working group
currently chooses to allow the flexibility of using other GIDs; what
seems to be under discussion is the relative benefit of allowing that
flexibility, if there is a cost to be paid in terms of interop.

> 
> Given the current definition of the ipoib pkt format, the issue on 
> hand does not necessarily only apply to DLPI systems, any application 
> talking to the ipoib driver directly (for whatever purposes) would 
> have to deal with src/dst(IB) address lookup problems; when that 
> information is not provided explicitly by the driver when passing up 
> pkts. Thus, even Linux and other OSes should be implementing the rfc 
> by its letter and intent.

Here is the difference between DLPI and nonDLPI systems: on non DLPI
systems, if the os allows raw access to the interface, then programs
utilizing the raw interface must neccesarily be aware of the underlying
packet format, and either deal with sender address not being present, or
know how to decipher it from the packet header. If you took a program
that runs on raw Ethernet, there is a very good chance you will need to
modify the program to run on raw IPoIB.

With DLPI, there is an attempt to reduce the media awareness of
programs, by requiring the os to provide some meta information for every
packet received (sender's mac address in this case). In practice, this
does not guarantee that 
a program that runs on ethernet will run unmodified on IPoIB, but there
is a 
good chance that it might. 

As you point out, determining the sender's address is problematic in
either case (dlpi or non dlpi): in the case of dlpi though, the onus is
on the driver to provide the information (dlpi apps expect it), whereas
in non dlpi case, 
programs can choose to solve the problem in their own unique ways. Using
GID0 always is one way to solve the problem for everyone, the other is
to require 
using GRH for every packet transmitted, but that has a performance
impact and is thus not desirable.

> 
> Finally, if we were to make a case with such assumptions as above, do 
> we then reconsider all uses of "RECOMMENDED/SHOULD" in the rfc.
>

If there is an interop issue, or a case where some established practice
or software breaks (due to an implementation not following
recommendation), in my 
opinion, we should think about the item seriously. 

Is there a reason you are opposed to changing the RECOMMENDED to a
REQUIRED in this specific case? Vivek mentioned there was inclination
towards allowing the flexibility, and I generally agree to that; but in
this case, curtailing the flexibility is solving a problem, without
creating any new ones I am aware 
of.

Thanks.

Kanoj



> thx,
> ~Ajoy
> 
> !
> ! Thanks.
> !
> ! Kanoj
> !
> ! >
> ! > thx,
> ! > ~Ajoy
> ! >
> ! > !
> ! > ! Vivek
> ! > !
> ! > ! On Wed, 3 Dec 2003, Kanoj Sarcar wrote:
> ! > !
> ! > ! > Vivek Kashyap wrote:
> ! > ! > >
> ! > ! > > Kanoj,
> ! > ! > >
> ! > ! > > The port's GUID is it's EUI-64 identifier. A GID, in turn 
> can be formed ! > using this GUID, the CA's GUID or some other value. 
> Any GID is unique in the IB
> ! > fabric however only by using the port's GUID/EUI-64 identifier can
one
> uniquely
> ! > identify the port. The other GID's, as noted, can be applied to
other ports
> too
> ! > - though not concurrently. The GID formed using the EUI-64
identifier is the
> ! > 'GID at index 0'. I've made note of your comment and can clarify
further as
> ! > needed.
> ! > ! > >
> ! > ! > > wrt, using only GID at index 0 as in the MAC address, there
have been
> ! > proponents of using the other GIDs (non EUI-64 GID).
> ! > ! > >
> ! > ! > > Vivek
> ! > ! >
> ! > ! > Vivek,
> ! > ! >
> ! > ! > Per IBA 1.1 section 4.1 EUI-64 subsection and 4.1.1 item 2,
manufacturer
> ! > assigned and
> ! > ! > SM assigned values are required to be EUI-64 compliant (they
differ only
> in
> ! > u/l bits).
> ! > ! > Thus, all GIDs contain an EUI-64 in the lower 64 bits; thus
saying "GUID
> is
> ! > its EUI-64
> ! > ! > identifier" might be confusing. Saying "GUID using
manufacturer assigned
> ! > EUI-64 identifier"
> ! > ! > or better "GID index 0" removes all confusion. I think we
agree on the
> ! > intent, I just
> ! > ! > want to make sure if you use the term GUID, you do
specifically define
> what
> ! > you mean
> ! > ! > by it.
> ! > ! >
> ! > ! > Regarding MUST vs RECOMMENDED, is it worthwhile reconsidering
given that
> ! > ! >
> ! > ! > 1. SM assigned GIDs are not that popular (anymore?)
> ! > ! > 2. it allows determination of sender's ipoib address, thus
allowing
> ! > (receiver side)
> ! > ! > implementations to be dlpiv2 conformant?
> ! > ! >
> ! > ! > Thanks.
> ! > ! >
> ! > ! > Kanoj
> ! > ! >
> ! > ! >
> ! > ! >
> ! > ! > > --
> ! > ! > > Vivek Kashyap
> ! > ! > > Linux Technology Center, IBM
> ! > ! > > vivk@us.ibm.com
> ! > ! > > kashyapv@us.ibm.com
> ! > ! > > Ph: 503 578 3422 T/L: 775 3422
> ! > ! > >
> ! > ! > >     Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
> ! > ! > >     Sent by: ipoverib-admin@ietf.org
> ! > ! > >
> ! > ! > >     12/02/2003 03:54 PM
> ! > ! > >     Please respond to Kanoj.Sarcar
> ! > ! > >
> ! > ! > > Hi,
> ! > ! > >
> ! > ! > > It seems that certain parts of the
> ! > ! > > draft-ietf-ipoib-ip-over-infiniband-05.txt draft might
> ! > ! > > require clarification. For this discussion, please refer to
> ! > ! > >
> ! > ! > > 1. section 9.1 Link Information says:
> ! > ! > > "The GID, if formed using the GUID, can be used to
unambiguously
> ! > ! > > identify an endpoint."
> ! > ! > >
> ! > ! > > 2. section 9.1.1 Link Layer Address/Hardware Address, part
c) says:
> ! > ! > > "It is RECOMMENDED that the GID formed by the combination of
the
> ! > ! > > IB subnet prefix and the port's GUID be included in the
> ! > ! > > link-layer/hardware address."
> ! > ! > >
> ! > ! > > Can comment #2 be safely taken to mean that GID index 0 is
> ! > ! > > being RECOMMENDED? Port GUID seems somewhat ambiguous, since
I
> ! > ! > > am not sure (after reading IBA 1.1 section 4.1) whether the
> ! > ! > > term GUID refers only to the manufacturer assigned value
that appears
> ! > ! > > in lower 64 bits of GID index 0, or whether it also includes
> ! > ! > > lower 64 bits of SM assigned GIDs at higher indices. If GID
index 0
> ! > ! > > was really intended, the comment should explicitly state so
to prevent
> ! > ! > > confusion.
> ! > ! > >
> ! > ! > > Also, to make things simple, is it reasonable to REQUIRE
> implementations
> ! > ! > > to always use GID index 0 (maybe this depends on whether
existing
> ! > ! > > implementations all use GID0 only)? The reason this might be
> ! > ! > > interesting is that when a node receives a packet without a
GRH
> ! > ! > > (whereby it already knows the sender's LID and QPN), it can
possibly
> ! > ! > > reverse lookup the sender's LID to identify the sender's GID
index
> ! > ! > > 0 and concatenate the sender's QPN to figure out the
sender's link
> ! > ! > > address. Thus, a receiver can always figure out the sender's
address,
> ! > ! > > even when a GRH is not present. This would be similar to
ethernet,
> ! > ! > > where a receiver can always determine a sender's address,
and thus
> ! > ! > > is more DLPIv2 (unitdata_indication) friendly.
> ! > ! > >
> ! > ! > > Regarding comment #1, what does "unambiguously identify an
endpoint"
> ! > ! > > mean? GIDs are unique in the subnet; and if an IP link
contains
> ! > ! > > members in multiple IBA subnets, the subnet prefixes will
disambiguate
> ! > ! > > which endport is being referred.
> ! > ! > >
> ! > ! > > Thanks.
> ! > ! > >
> ! > ! > > Kanoj
> ! > ! > >
> ! > ! > > _______________________________________________
> ! > ! > > 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
> ! > ! >
> ! > ! >
> ! > !
> ! > ! __
> ! > !
> ! > ! Vivek Kashyap
> ! > ! Linux Technology Center, IBM
> ! > !
> ! > !
> ! > ! _______________________________________________
> ! > ! 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

_______________________________________________
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  Fri Dec  5 12:18:18 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14392
	for <ipoverib-archive@odin.ietf.org>; Fri, 5 Dec 2003 12:18:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJae-0003lH-0O
	for ipoverib-archive@odin.ietf.org; Fri, 05 Dec 2003 12:18:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5HI3Pu014453
	for ipoverib-archive@odin.ietf.org; Fri, 5 Dec 2003 12:18:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJad-0003l2-T0
	for ipoverib-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 12:18:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14330
	for <ipoverib-web-archive@ietf.org>; Fri, 5 Dec 2003 12:17:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJac-0005Hc-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 12:18:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJac-0005HY-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 12:18:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJab-0003kj-94; Fri, 05 Dec 2003 12:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASJZq-0003jK-7R
	for ipoverib@optimus.ietf.org; Fri, 05 Dec 2003 12:17:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14263
	for <ipoverib@ietf.org>; Fri, 5 Dec 2003 12:16:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJZo-0005Fl-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 12:17:12 -0500
Received: from palrel10.hp.com ([156.153.255.245])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASJZo-0005FU-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 12:17:12 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel10.hp.com (Postfix) with ESMTP id 26A441C017F1
	for <ipoverib@ietf.org>; Fri,  5 Dec 2003 09:17:06 -0800 (PST)
Received: from mk731915.cup.hp.com ([15.8.80.111])
	by esmail.cup.hp.com (8.11.1/8.8.6) with ESMTP id hB5H8xi17376
	for <ipoverib@ietf.org>; Fri, 5 Dec 2003 09:08:59 -0800 (PST)
Message-Id: <5.1.0.14.2.20031205090714.025915c8@15.13.130.73>
X-Sender: krause@15.13.130.73
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 05 Dec 2003 09:16:07 -0800
To: ipoverib@ietf.org
From: Michael Krause <krause@cup.hp.com>
Subject: RE: [Ipoverib] GID clarifications
In-Reply-To: <000401c3bad4$17d60180$f5d912c0@mobilebill>
References: <3FCFD4CA.3DBB8D2@Sun.COM>
Mime-Version: 1.0
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>

At 06:04 PM 12/4/2003 -0800, bill wrote:
>Ok, let me ask a few questions to lead us toward concensus

As the author of the IB spec for chapter 4, I'll attempt to provide some 
clarifications.

>1) Does anyone give a compelling reason to use anything but GID0 for IPoIB 
>- what is the benefit of doing this ?

Multiple GIDs were provided as a method to:

- Provide traffic segregation between subnets conceptually similar to 
multi-LID usage within a single subnet.

- Provide a method to support software / OS virtualization and device 
sharing via using a unique global identifier independent of the number of 
LIDs assigned (though one can take a similar approach if the LMC value is 
greater than 0.

I will note that there are many OSVs offering or starting to offer 
virtualization services and while some initial implementations may be 
focused on GID 0, this may not hold true in the coming few years.

- Provide a method to constrain out some data flows are routed - local vs. 
non-local subnet access given a GID can use either the default or the SM 
assigned subnet prefix.

>2) Does anyone have an implementation that uses anything but GID0 for IPoIB ?

I believe it would be a mistake to limit support to just GID 0.  IB 
technology was designed to support a diverse set of usage models that will 
evolve over time.  The only potential problem was a DLPI application raw 
level usage model which is (a) somewhat outside of the scope of the IP over 
IB specification and (b) rather limited in terms of usage within the 
industry.  I don't really want to debate the merits of raw DLPI but do 
acknowledge it is in use today on Ethernet and other layer 2 interconnects.

>If I do not hear any counter arguments by next Friday - I would like to 
>ask for concensus on MUST use GID0

Please consider this a counter argument and a vote against such a movement.

Mike


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



From exim@www1.ietf.org  Fri Dec  5 18:10:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01859
	for <ipoverib-archive@odin.ietf.org>; Fri, 5 Dec 2003 18:10:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASP5L-0002Ko-4u
	for ipoverib-archive@odin.ietf.org; Fri, 05 Dec 2003 18:10:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5NA7AW008975
	for ipoverib-archive@odin.ietf.org; Fri, 5 Dec 2003 18:10:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASP5K-0002Kg-UG
	for ipoverib-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 18:10:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01799
	for <ipoverib-web-archive@ietf.org>; Fri, 5 Dec 2003 18:09:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASP5H-00045L-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 18:10:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASP5H-00045I-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 18:10:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASP5H-0002K5-1u; Fri, 05 Dec 2003 18:10:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASP4q-0002JF-Qg
	for ipoverib@optimus.ietf.org; Fri, 05 Dec 2003 18:09:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01745
	for <ipoverib@ietf.org>; Fri, 5 Dec 2003 18:09:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASP4n-00044h-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 18:09:33 -0500
Received: from gw0.infiniconsys.com ([65.219.193.226] helo=mail.infiniconsys.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASP4n-00044G-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 18:09:33 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3BB84.BF4C8876"
Date: Fri, 5 Dec 2003 18:08:51 -0500
Message-ID: <08628CA53C6CBA4ABAFB9E808A5214CB01C4DA13@mercury.infiniconsys.com>
Thread-Topic: DHCP Client-identifier option for DHCPOFFER
Thread-Index: AcO7hHmh2T/+ZZnbTmK/mdcrBM5USw==
From: "Tillier, Fabian" <ftillier@infiniconsys.com>
To: <ipoverib@ietf.org>
Subject: [Ipoverib] DHCP Client-identifier option for DHCPOFFER
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C3BB84.BF4C8876
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello all,

=20

RFC2131, Section 4.3.1, Table 3 indicates that the client identifier
option "MUST NOT" be used in DHCPOFFER messages sent by the server.
Since the DHCPDISCOVER message must have the broadcast flag set, the
DHCPOFFER message will be broadcast back.  How do recipients of
DHCPOFFER tell if they are the intended target?

=20

Thank you,

=20

Fabian

=20

=20


------_=_NextPart_001_01C3BB84.BF4C8876
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hello all,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>RFC2131, Section 4.3.1, Table 3 indicates that the =
client
identifier option &#8220;MUST NOT&#8221; be used in DHCPOFFER messages =
sent by
the server. &nbsp;Since the DHCPDISCOVER message must have the broadcast =
flag
set, the DHCPOFFER message will be broadcast back.&nbsp; How do =
recipients of DHCPOFFER
tell if they are the intended target?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Fabian</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C3BB84.BF4C8876--

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



From exim@www1.ietf.org  Fri Dec  5 18:44:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03443
	for <ipoverib-archive@odin.ietf.org>; Fri, 5 Dec 2003 18:44:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASPcD-0003Tl-Ir
	for ipoverib-archive@odin.ietf.org; Fri, 05 Dec 2003 18:44:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB5Ni582013367
	for ipoverib-archive@odin.ietf.org; Fri, 5 Dec 2003 18:44:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASPcD-0003TW-Al
	for ipoverib-web-archive@optimus.ietf.org; Fri, 05 Dec 2003 18:44:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03421
	for <ipoverib-web-archive@ietf.org>; Fri, 5 Dec 2003 18:43:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASPcA-0004TC-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 18:44:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASPc9-0004T9-00
	for ipoverib-web-archive@ietf.org; Fri, 05 Dec 2003 18:44:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASPc9-0003Ss-33; Fri, 05 Dec 2003 18:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ASPbU-0003SQ-0W
	for ipoverib@optimus.ietf.org; Fri, 05 Dec 2003 18:43:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03401
	for <ipoverib@ietf.org>; Fri, 5 Dec 2003 18:43:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASPbQ-0004Sj-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 18:43:16 -0500
Received: from [63.251.237.3] (helo=mtiex01.mti.mtl.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ASPbQ-0004SW-00
	for ipoverib@ietf.org; Fri, 05 Dec 2003 18:43:16 -0500
Received: by MTIEX01 with Internet Mail Service (5.5.2653.19)
	id <XHYFGWF2>; Fri, 5 Dec 2003 15:33:54 -0800
Message-ID: <25AE7F432672D511B8DC00B0D0DF11DA01D8D933@MTIEX01>
From: Chanan Shamir <Chanan@Mellanox.com>
To: "'Tillier, Fabian'" <ftillier@infiniconsys.com>, ipoverib@ietf.org
Subject: RE: [Ipoverib] DHCP Client-identifier option for DHCPOFFER
Date: Fri, 5 Dec 2003 15:33:53 -0800 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3BB88.3E607100"
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>

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_01C3BB88.3E607100
Content-Type: text/plain;
	charset="iso-8859-1"

Hello Fabian,
 
From RFC 2131 Section 4.1:
The 'xid' field is used by the client to match incoming DHCP messages
   with pending requests.  A DHCP client MUST choose 'xid's in such a
   way as to minimize the chance of using an 'xid' identical to one used
   by another client.


Chanan

-----Original Message-----
From: Tillier, Fabian [mailto:ftillier@infiniconsys.com]
Sent: Friday, December 05, 2003 3:09 PM
To: ipoverib@ietf.org
Subject: [Ipoverib] DHCP Client-identifier option for DHCPOFFER



Hello all,

 

RFC2131, Section 4.3.1, Table 3 indicates that the client identifier option
"MUST NOT" be used in DHCPOFFER messages sent by the server.  Since the
DHCPDISCOVER message must have the broadcast flag set, the DHCPOFFER message
will be broadcast back.  How do recipients of DHCPOFFER tell if they are the
intended target?

 

Thank you,

 

Fabian

 

 


------_=_NextPart_001_01C3BB88.3E607100
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 6.00.2800.1264" name=GENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
	COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV><SPAN class=847503823-05122003><FONT face=Arial color=#0000ff size=2>Hello 
Fabian,</FONT></SPAN></DIV>
<DIV><SPAN class=847503823-05122003><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=847503823-05122003><FONT face=Arial color=#0000ff size=2>From 
RFC 2131 Section 4.1:</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2>The 'xid' field is used by the client 
to match incoming DHCP messages<BR>&nbsp;&nbsp; with pending requests.&nbsp; A 
DHCP client MUST choose 'xid's in such a<BR>&nbsp;&nbsp; way as to minimize the 
chance of using an 'xid' identical to one used<BR>&nbsp;&nbsp; by another 
client.</FONT></DIV><BR>
<P><FONT size=2>Chan<SPAN class=847503823-05122003>an</SPAN></FONT></P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Tillier, Fabian 
  [mailto:ftillier@infiniconsys.com]<BR><B>Sent:</B> Friday, December 05, 2003 
  3:09 PM<BR><B>To:</B> ipoverib@ietf.org<BR><B>Subject:</B> [Ipoverib] DHCP 
  Client-identifier option for DHCPOFFER<BR><BR></FONT></DIV>
  <DIV class=Section1>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hello all,</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">RFC2131, Section 4.3.1, Table 3 
  indicates that the client identifier option "MUST NOT" be used in DHCPOFFER 
  messages sent by the server. &nbsp;Since the DHCPDISCOVER message must have 
  the broadcast flag set, the DHCPOFFER message will be broadcast back.&nbsp; 
  How do recipients of DHCPOFFER tell if they are the intended 
  target?</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thank you,</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Fabian</SPAN></FONT></P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=MsoNormal><FONT face=Arial size=2><SPAN 
  style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C3BB88.3E607100--

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



From exim@www1.ietf.org  Sun Dec  7 23:23:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12779
	for <ipoverib-archive@odin.ietf.org>; Sun, 7 Dec 2003 23:23:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCvH-0003HR-6R
	for ipoverib-archive@odin.ietf.org; Sun, 07 Dec 2003 23:23:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB84N3c8012606
	for ipoverib-archive@odin.ietf.org; Sun, 7 Dec 2003 23:23:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCvG-0003HF-LB
	for ipoverib-web-archive@optimus.ietf.org; Sun, 07 Dec 2003 23:23:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12754
	for <ipoverib-web-archive@ietf.org>; Sun, 7 Dec 2003 23:22:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCvE-0004Bp-00
	for ipoverib-web-archive@ietf.org; Sun, 07 Dec 2003 23:23:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCvE-0004Bl-00
	for ipoverib-web-archive@ietf.org; Sun, 07 Dec 2003 23:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCvE-0003Gu-Np; Sun, 07 Dec 2003 23:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATCvD-0003Ga-B0
	for ipoverib@optimus.ietf.org; Sun, 07 Dec 2003 23:22:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12740
	for <ipoverib@ietf.org>; Sun, 7 Dec 2003 23:22:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCvB-0004BW-00
	for ipoverib@ietf.org; Sun, 07 Dec 2003 23:22:57 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATCvA-0004BT-00
	for ipoverib@ietf.org; Sun, 07 Dec 2003 23:22:56 -0500
Received: from jurassic.eng.sun.com ([129.146.89.50])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id hB84MVPh016478;
	Sun, 7 Dec 2003 21:22:36 -0700 (MST)
Received: from unknown (vpn-129-150-17-52.SFBay.Sun.COM [129.150.17.52])
	by jurassic.eng.sun.com (8.12.10+Sun/8.12.10) with SMTP id hB84MP05800806;
	Sun, 7 Dec 2003 20:22:29 -0800 (PST)
Message-Id: <200312080422.hB84MP05800806@jurassic.eng.sun.com>
Date: Sun, 7 Dec 2003 20:22:33 -0800 (PST)
From: "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>
Reply-To: "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>
Subject: RE: [Ipoverib] GID clarifications
To: ipoverib@ietf.org, krause@cup.hp.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: sjKSkR8L59ZMHf74f0V0iw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.5 SunOS 5.9 sun4u sparc 
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>

Mike,

>At 06:04 PM 12/4/2003 -0800, bill wrote:
>>Ok, let me ask a few questions to lead us toward concensus
>
>As the author of the IB spec for chapter 4, I'll attempt to provide some 
>clarifications.
>
>>1) Does anyone give a compelling reason to use anything but GID0 for IPoIB 
>>- what is the benefit of doing this ?
>
>Multiple GIDs were provided as a method to:
>
>- Provide traffic segregation between subnets conceptually similar to 
>multi-LID usage within a single subnet.

According to IBA 1.0a spec (i don't have 1.1 spec at hand), "A subnet shall
have only one assigned GID prefix at any given time (at GID index 0)."
It seems to me unless a CA port can be simultaneously connected to more
than one IB subnet, the unique subnet prefix plus the default GID prefix
(the link-local 0xFF80 prefix) are the only two possible values to have
for the upper 64 bits of a GID. I wonder what the traffic seggregation
between subnets you have in mind.

>
>- Provide a method to support software / OS virtualization and device 
>sharing via using a unique global identifier independent of the number of 
>LIDs assigned (though one can take a similar approach if the LMC value is 
>greater than 0.
>
>I will note that there are many OSVs offering or starting to offer 
>virtualization services and while some initial implementations may be 
>focused on GID 0, this may not hold true in the coming few years.

Not sure what flavor of "virtualization" you're alluding to. If the
virtualization is achieved through the use of multiple IB partitions,
different IB partitions can safely share the same GID much like
different Ethernet VLAN sharing the same MAC address. I don't see the
need for multiple GIDs.

Perhaps you meant virtualization like the hosting of multiple IP
addressses with the same subnet prefix but different host numbers
on the same NIC, this can be achieved through the use of multiple
locally-assigned EUI-64s in IB, and I agree it is a useful feature
to support.

>
>- Provide a method to constrain out some data flows are routed - local vs. 
>non-local subnet access given a GID can use either the default or the SM 
>assigned subnet prefix.

Note that the draft currently recommends the use of the IB subnet
prefix for the GID in IPoIB. Although the real requirement is that the
GID must be reachable (i.e. routable) at the IB layer from any node
within the scope of the IP link it belongs to, recommending the IB
subnet prefix is less error prone as it continues to work even after
the underlying IP link has been expanded to cover multiple IB subnets. 

>
>>2) Does anyone have an implementation that uses anything but GID0 for IPoIB ?
>
>I believe it would be a mistake to limit support to just GID 0.  IB 
>technology was designed to support a diverse set of usage models that will 
>evolve over time.  The only potential problem was a DLPI application raw 
>level usage model which is (a) somewhat outside of the scope of the IP over 
>IB specification and (b) rather limited in terms of usage within the 
>industry.  I don't really want to debate the merits of raw DLPI but do 
>acknowledge it is in use today on Ethernet and other layer 2 interconnects.
>
>>If I do not hear any counter arguments by next Friday - I would like to 
>>ask for concensus on MUST use GID0
>
>Please consider this a counter argument and a vote against such a movement.

You are opposing requiring GID0, but are you ok with the current wording
of RECOMMENDING the GID formed by the IB subnet prefix and the portGUID
(the one assigned by the manufacturer)?

BTW, I'm confused by the use of GID0 as I thought in IBA spec. it means
the one with the link-local prefix but I thought people wanted to use
the one with the IB subnet prefix.

Jerry

>
>Mike
>
>
>_______________________________________________
>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  Mon Dec  8 09:52:17 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11188
	for <ipoverib-archive@odin.ietf.org>; Mon, 8 Dec 2003 09:52:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMjy-0000kM-Ur
	for ipoverib-archive@odin.ietf.org; Mon, 08 Dec 2003 09:52:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB8Eq2hM002866
	for ipoverib-archive@odin.ietf.org; Mon, 8 Dec 2003 09:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMjy-0000k9-RS
	for ipoverib-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 09:52:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11156
	for <ipoverib-web-archive@ietf.org>; Mon, 8 Dec 2003 09:51:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMjw-0005Fb-00
	for ipoverib-web-archive@ietf.org; Mon, 08 Dec 2003 09:52:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMjw-0005FY-00
	for ipoverib-web-archive@ietf.org; Mon, 08 Dec 2003 09:52:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMjx-0000jf-44; Mon, 08 Dec 2003 09:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATMjG-0000if-He
	for ipoverib@optimus.ietf.org; Mon, 08 Dec 2003 09:51:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11097
	for <ipoverib@ietf.org>; Mon, 8 Dec 2003 09:51:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMjE-0005DM-00
	for ipoverib@ietf.org; Mon, 08 Dec 2003 09:51:16 -0500
Received: from palrel12.hp.com ([156.153.255.237])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATMjD-0005DH-00
	for ipoverib@ietf.org; Mon, 08 Dec 2003 09:51:16 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel12.hp.com (Postfix) with ESMTP id E48721C012B5
	for <ipoverib@ietf.org>; Mon,  8 Dec 2003 06:51:14 -0800 (PST)
Received: from mk731915.cup.hp.com ([15.244.170.65])
	by esmail.cup.hp.com (8.11.1/8.8.6) with ESMTP id hB8Eh4i24631
	for <ipoverib@ietf.org>; Mon, 8 Dec 2003 06:43:04 -0800 (PST)
Message-Id: <5.1.0.14.2.20031208062614.00ae7920@15.13.130.73>
X-Sender: krause@15.13.130.73
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 08 Dec 2003 06:37:53 -0800
To: ipoverib@ietf.org
From: Michael Krause <krause@cup.hp.com>
Subject: RE: [Ipoverib] GID clarifications
In-Reply-To: <200312080422.hB84MP05800806@jurassic.eng.sun.com>
Mime-Version: 1.0
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>

At 08:22 PM 12/7/2003 -0800, H.K. Jerry Chu wrote:
>Mike,
>
> >At 06:04 PM 12/4/2003 -0800, bill wrote:
> >>Ok, let me ask a few questions to lead us toward concensus
> >
> >As the author of the IB spec for chapter 4, I'll attempt to provide some
> >clarifications.
> >
> >>1) Does anyone give a compelling reason to use anything but GID0 for IPoIB
> >>- what is the benefit of doing this ?
> >
> >Multiple GIDs were provided as a method to:
> >
> >- Provide traffic segregation between subnets conceptually similar to
> >multi-LID usage within a single subnet.
>
>According to IBA 1.0a spec (i don't have 1.1 spec at hand), "A subnet shall
>have only one assigned GID prefix at any given time (at GID index 0)."
>It seems to me unless a CA port can be simultaneously connected to more
>than one IB subnet, the unique subnet prefix plus the default GID prefix
>(the link-local 0xFF80 prefix) are the only two possible values to have
>for the upper 64 bits of a GID.

Correct.  One can have either the default or an assigned thus all GID share 
one or the other.

>  I wonder what the traffic seggregation between subnets you have in mind.

The basic idea was one could encode in the lower 64 bits (these are admin 
assigned if not the port EUI64 value) or through a combination of other GRH 
attributes (e.g. TClass, Flow Label, etc.) one could segregate traffic to 
take different paths when passing through a router. The path selection 
would be implemented via selecting an egress port and assigning an 
appropriate next router hop / endnode LID.

> >- Provide a method to support software / OS virtualization and device
> >sharing via using a unique global identifier independent of the number of
> >LIDs assigned (though one can take a similar approach if the LMC value is
> >greater than 0.
> >
> >I will note that there are many OSVs offering or starting to offer
> >virtualization services and while some initial implementations may be
> >focused on GID 0, this may not hold true in the coming few years.
>
>Not sure what flavor of "virtualization" you're alluding to. If the
>virtualization is achieved through the use of multiple IB partitions,
>different IB partitions can safely share the same GID much like
>different Ethernet VLAN sharing the same MAC address. I don't see the
>need for multiple GIDs.

Virtualization is nominally a function of address while partitions are a 
function of segregation enforcement ala 802.1Q.  While one can use 
partitions, they are not seen by the underlying software while a GRH is 
seen thus depending upon how it is implemented, how the remote peer "sees" 
each target peer, etc. a GID is more flexible and may align better with 
application usage.  Please keep in mind I'm explaining how the motivation 
for multiple GID from an IBA perspective.  Now, can one use a single GID 
with multiple P_Key and then have a unique IP-to-QP mapping per resulting 
partition to achieve something similar?  The answer is yes, it is possible 
but that was not the intent of the IBTA when this was first being debated.

>Perhaps you meant virtualization like the hosting of multiple IP
>addressses with the same subnet prefix but different host numbers
>on the same NIC, this can be achieved through the use of multiple
>locally-assigned EUI-64s in IB, and I agree it is a useful feature
>to support.
>
> >
> >- Provide a method to constrain out some data flows are routed - local vs.
> >non-local subnet access given a GID can use either the default or the SM
> >assigned subnet prefix.
>
>Note that the draft currently recommends the use of the IB subnet
>prefix for the GID in IPoIB. Although the real requirement is that the
>GID must be reachable (i.e. routable) at the IB layer from any node
>within the scope of the IP link it belongs to, recommending the IB
>subnet prefix is less error prone as it continues to work even after
>the underlying IP link has been expanded to cover multiple IB subnets.

Agreed.


> >
> >>2) Does anyone have an implementation that uses anything but GID0 for 
> IPoIB ?
> >
> >I believe it would be a mistake to limit support to just GID 0.  IB
> >technology was designed to support a diverse set of usage models that will
> >evolve over time.  The only potential problem was a DLPI application raw
> >level usage model which is (a) somewhat outside of the scope of the IP over
> >IB specification and (b) rather limited in terms of usage within the
> >industry.  I don't really want to debate the merits of raw DLPI but do
> >acknowledge it is in use today on Ethernet and other layer 2 interconnects.
> >
> >>If I do not hear any counter arguments by next Friday - I would like to
> >>ask for concensus on MUST use GID0
> >
> >Please consider this a counter argument and a vote against such a movement.
>
>You are opposing requiring GID0, but are you ok with the current wording
>of RECOMMENDING the GID formed by the IB subnet prefix and the portGUID
>(the one assigned by the manufacturer)?

I can live with RECOMMENDING not with MUST.

>BTW, I'm confused by the use of GID0 as I thought in IBA spec. it means
>the one with the link-local prefix but I thought people wanted to use
>the one with the IB subnet prefix.

GID 0 is just the guaranteed GID to be created via the combination of the 
port GUID (manufacturer assigned GUID) and the subnet prefix.

Mike


>Jerry
>
> >
> >Mike
> >
> >
> >_______________________________________________
> >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


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



From exim@www1.ietf.org  Mon Dec  8 22:06:19 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22529
	for <ipoverib-archive@odin.ietf.org>; Mon, 8 Dec 2003 22:06:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYCL-0003fg-LB
	for ipoverib-archive@odin.ietf.org; Mon, 08 Dec 2003 22:06:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB9365hX014106
	for ipoverib-archive@odin.ietf.org; Mon, 8 Dec 2003 22:06:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYCL-0003fQ-Ep
	for ipoverib-web-archive@optimus.ietf.org; Mon, 08 Dec 2003 22:06:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22496
	for <ipoverib-web-archive@ietf.org>; Mon, 8 Dec 2003 22:05:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYCI-0005pb-00
	for ipoverib-web-archive@ietf.org; Mon, 08 Dec 2003 22:06:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYCH-0005pY-00
	for ipoverib-web-archive@ietf.org; Mon, 08 Dec 2003 22:06:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYCK-0003f5-0E; Mon, 08 Dec 2003 22:06:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ATYCC-0003eI-MK
	for ipoverib@optimus.ietf.org; Mon, 08 Dec 2003 22:05:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22485
	for <ipoverib@ietf.org>; Mon, 8 Dec 2003 22:05:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYC9-0005pK-00
	for ipoverib@ietf.org; Mon, 08 Dec 2003 22:05:53 -0500
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ATYC8-0005pH-00
	for ipoverib@ietf.org; Mon, 08 Dec 2003 22:05:52 -0500
Received: from phys-bos-1.sfbay.sun.com ([129.146.14.23])
	by brmea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id hB935qPj016664
	for <ipoverib@ietf.org>; Mon, 8 Dec 2003 20:05:53 -0700 (MST)
Received: from Sun.COM (sr1-umpk-18.SFBay.Sun.COM [129.146.11.202])
 by bos-mail1.sfbay.sun.com (Sun ONE Messaging Server 6.0 (built Sep 24 2003))
 with ESMTP id <0HPL00AKQXXSFME0@bos-mail1.sfbay.sun.com> for
 ipoverib@ietf.org; Mon, 08 Dec 2003 19:05:52 -0800 (PST)
Date: Mon, 08 Dec 2003 19:05:52 -0800
From: Kanoj Sarcar <Kanoj.Sarcar@Sun.COM>
Subject: Re: [Ipoverib] GID clarifications
To: Michael Krause <krause@cup.hp.com>
Cc: ipoverib@ietf.org
Reply-to: Kanoj.Sarcar@Sun.COM
Message-id: <3FD53C10.13C4B2EF@Sun.COM>
MIME-version: 1.0
X-Mailer: Mozilla 4.79C-CCK-MCD  [en] (X11; U; SunOS 5.9 sun4u)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-Accept-Language: en
References: <5.1.0.14.2.20031208062614.00ae7920@15.13.130.73>
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Michael Krause wrote:
> 
> At 08:22 PM 12/7/2003 -0800, H.K. Jerry Chu wrote:
> >Mike,

Hi,

Michael, thanks for providing the IBTA context about multiple GIDs and path selection.

> >
> > >At 06:04 PM 12/4/2003 -0800, bill wrote:
> > >>Ok, let me ask a few questions to lead us toward concensus
> > >
> > >As the author of the IB spec for chapter 4, I'll attempt to provide some
> > >clarifications.
> > >
> > >>1) Does anyone give a compelling reason to use anything but GID0 for IPoIB
> > >>- what is the benefit of doing this ?
> > >
> > >Multiple GIDs were provided as a method to:
> > >
> > >- Provide traffic segregation between subnets conceptually similar to
> > >multi-LID usage within a single subnet.
> >
> >According to IBA 1.0a spec (i don't have 1.1 spec at hand), "A subnet shall
> >have only one assigned GID prefix at any given time (at GID index 0)."
> >It seems to me unless a CA port can be simultaneously connected to more
> >than one IB subnet, the unique subnet prefix plus the default GID prefix
> >(the link-local 0xFF80 prefix) are the only two possible values to have
> >for the upper 64 bits of a GID.
> 
> Correct.  One can have either the default or an assigned thus all GID share
> one or the other.
> 
> >  I wonder what the traffic seggregation between subnets you have in mind.
> 
> The basic idea was one could encode in the lower 64 bits (these are admin
> assigned if not the port EUI64 value) or through a combination of other GRH
> attributes (e.g. TClass, Flow Label, etc.) one could segregate traffic to
> take different paths when passing through a router. The path selection
> would be implemented via selecting an egress port and assigning an
> appropriate next router hop / endnode LID.

It seems to me that for endports to influence which path to
use for each UD packet, the SM and the endnodes need to exchange 
some information. I was under the impression that SL/VL information 
within a IBA subnet, and additionally Tclass etc between IBA 
subnets, would be sufficient; ie, segregation could be achieved
with just these parameters, and would not need to extend to source
GID. I am not sure whether your use of the word "or" above means
that this is still a viable option.

> 
> > >- Provide a method to support software / OS virtualization and device
> > >sharing via using a unique global identifier independent of the number of
> > >LIDs assigned (though one can take a similar approach if the LMC value is
> > >greater than 0.
> > >
> > >I will note that there are many OSVs offering or starting to offer
> > >virtualization services and while some initial implementations may be
> > >focused on GID 0, this may not hold true in the coming few years.
> >
> >Not sure what flavor of "virtualization" you're alluding to. If the
> >virtualization is achieved through the use of multiple IB partitions,
> >different IB partitions can safely share the same GID much like
> >different Ethernet VLAN sharing the same MAC address. I don't see the
> >need for multiple GIDs.
> 
> Virtualization is nominally a function of address while partitions are a
> function of segregation enforcement ala 802.1Q.  While one can use
> partitions, they are not seen by the underlying software while a GRH is
> seen thus depending upon how it is implemented, how the remote peer "sees"
> each target peer, etc. a GID is more flexible and may align better with
> application usage.  Please keep in mind I'm explaining how the motivation
> for multiple GID from an IBA perspective.  Now, can one use a single GID
> with multiple P_Key and then have a unique IP-to-QP mapping per resulting
> partition to achieve something similar?  The answer is yes, it is possible
> but that was not the intent of the IBTA when this was first being debated.
> 
> >Perhaps you meant virtualization like the hosting of multiple IP
> >addressses with the same subnet prefix but different host numbers
> >on the same NIC, this can be achieved through the use of multiple
> >locally-assigned EUI-64s in IB, and I agree it is a useful feature
> >to support.

At least from the ipoib perspective, it is also possible to 
virtualize based on the QPN (using same Pkey), since that is 
part of the mac address. I do agree that virtualization based on GIDs
is attractive.

> >
> > >
> > >- Provide a method to constrain out some data flows are routed - local vs.
> > >non-local subnet access given a GID can use either the default or the SM
> > >assigned subnet prefix.
> >
> >Note that the draft currently recommends the use of the IB subnet
> >prefix for the GID in IPoIB. Although the real requirement is that the
> >GID must be reachable (i.e. routable) at the IB layer from any node
> >within the scope of the IP link it belongs to, recommending the IB
> >subnet prefix is less error prone as it continues to work even after
> >the underlying IP link has been expanded to cover multiple IB subnets.
> 
> Agreed.
> 
> > >
> > >>2) Does anyone have an implementation that uses anything but GID0 for
> > IPoIB ?
> > >
> > >I believe it would be a mistake to limit support to just GID 0.  IB
> > >technology was designed to support a diverse set of usage models that will
> > >evolve over time.  The only potential problem was a DLPI application raw
> > >level usage model which is (a) somewhat outside of the scope of the IP over
> > >IB specification and (b) rather limited in terms of usage within the
> > >industry.  I don't really want to debate the merits of raw DLPI but do
> > >acknowledge it is in use today on Ethernet and other layer 2 interconnects.
> > >

Note that as has been pointed out, it is also possible for non DLPI apps to
want to know the sender's L2 address (trivially possible on ethernet by looking
at the received packet and picking out the source ethernet address). As you point
out, this might be slightly out of scope, but here's an example that is within
scope: imagine a node A with mac address M1 wants to know what IP address the 
RARP server will assign for a different mac address M2; it can fabricate a RARP 
message and broadcast it out; the RARP server must send the RARP response to M1
and not to M2. For this, the RARP server must be able to determine that the
sender's L2 address is M1. Similarly, an ARP implementation might want to 
determine the sender of an ARP request and validate against the "sender hardware
address" in the ARP message. I can't make a call on how extensive this type
of usage is though.

Thanks.

Kanoj


> > >>If I do not hear any counter arguments by next Friday - I would like to
> > >>ask for concensus on MUST use GID0
> > >
> > >Please consider this a counter argument and a vote against such a movement.
> >
> >You are opposing requiring GID0, but are you ok with the current wording
> >of RECOMMENDING the GID formed by the IB subnet prefix and the portGUID
> >(the one assigned by the manufacturer)?
> 
> I can live with RECOMMENDING not with MUST.
> 
> >BTW, I'm confused by the use of GID0 as I thought in IBA spec. it means
> >the one with the link-local prefix but I thought people wanted to use
> >the one with the IB subnet prefix.
> 
> GID 0 is just the guaranteed GID to be created via the combination of the
> port GUID (manufacturer assigned GUID) and the subnet prefix.
> 
> Mike
> 
> >Jerry
> >
> > >
> > >Mike
> > >
> > >
> > >_______________________________________________
> > >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
> 
> _______________________________________________
> 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  Tue Dec 16 18:09:30 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13030
	for <ipoverib-archive@odin.ietf.org>; Tue, 16 Dec 2003 18:09:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOJM-00037z-50
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 18:09:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGN94Lk012017
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 18:09:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOJL-00037k-Tw
	for ipoverib-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 18:09:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12964
	for <ipoverib-web-archive@ietf.org>; Tue, 16 Dec 2003 18:08:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOJJ-0001QK-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:09:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWOJI-0001QB-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:09:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOJH-0001Q8-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:08:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOJI-00037O-7T; Tue, 16 Dec 2003 18:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOIx-00037B-3N
	for ipoverib@optimus.ietf.org; Tue, 16 Dec 2003 18:08:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12915
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 18:08:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOIu-0001Ph-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:08:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWOIt-0001Pa-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:08:35 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOIt-0001PE-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:08:35 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hBGMil118389
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 17:44:49 -0500
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Date: Tue, 16 Dec 2003 15:07:59 -0800
Message-ID: <000001c3c429$74bea420$f5d912c0@mobilebill>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0001_01C3C3E6.669B6420"
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.1165
Subject: [Ipoverib] IPoIB Meeting minutes
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

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C3C3E6.669B6420
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Please look these over and get changes back

I am sorry I have been late getting these - if there are no objections,
I will publish these Thursday along with the presentations

Bill

------=_NextPart_000_0001_01C3C3E6.669B6420
Content-Type: application/octet-stream;
	name="IPoIBMinutes"
Content-Disposition: attachment;
	filename="IPoIBMinutes"
Content-Transfer-Encoding: quoted-printable

Meeting Minutes IPoIB=0A=
=0A=
Called to Order=0A=
=0A=
Encapsulation draft status - =0A=
ADs have asked to merge the encapsulation draft and the multicast draft. =
 =0A=
Effort is almost complete=0A=
=0A=
MIB status=0A=
Lots of feedback from our MIB doctor Randy P. on the IB MIB drafts - Sean=0A=
is currently working on getting the drafts updated against the feedback=0A=
from Randy.  Will publish ASAP.=0A=
=0A=
There was discussion on 0 basing certain Indexes - historically there =
was an=0A=
adversion to using 0 as an index in a table - this is not the case if =
the =0A=
objects being managed are naturally 0 based.  Will update TCs to reflect =
this.=0A=
=0A=
There was a discussion about how the SMA MIB would work through things =
like=0A=
the Entity MIB - is there a relationship ?=0A=
=0A=
SM MIB presentation=0A=
Topspin and Sun are working on a SM MIB that will complement the SMA =
MIB.  =0A=
The presentation outlines the broad tables that are in this MIB.  There=0A=
was general concensus in the room to push this as a Working Group item - =
will=0A=
confirm on the list=0A=
=0A=
Randy brought up an interesting issue - the objects in the SM MIB mirror =
in =0A=
many cased objects that are on the SMA MIB - something might want to be =
said =0A=
in the Security considerations section about this.=0A=
=0A=
Randy also mentioned the informational topology MIB - would it be =
interesting=0A=
to sort information by topology.=0A=
=0A=
Interop testing=0A=
When the IPoIB draft is published there will be a need to perform interop=0A=
testing to get to draft Standard.  The proposal is to look at the Summer =
IBTA=0A=
Plugfest as a place to perform this testing - will propose it to both =
IBTA and=0A=
the WG list=0A=
=0A=
There will have to be careful design of both test cases - and reporting =
the=0A=
results that will not violate Plugfest NDA type agreements.=0A=

------=_NextPart_000_0001_01C3C3E6.669B6420--


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



From exim@www1.ietf.org  Tue Dec 16 18:26:59 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14229
	for <ipoverib-archive@odin.ietf.org>; Tue, 16 Dec 2003 18:26:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOaH-0003ik-Sh
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 18:26:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBGNQXDd014301
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 18:26:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOaH-0003ia-P9
	for ipoverib-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 18:26:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14178
	for <ipoverib-web-archive@ietf.org>; Tue, 16 Dec 2003 18:26:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOaE-0001xk-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:26:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWOa3-0001xN-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:26:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOa3-0001wy-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 18:26:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOZl-0003gX-KW; Tue, 16 Dec 2003 18:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWOZc-0003gH-0l
	for ipoverib@optimus.ietf.org; Tue, 16 Dec 2003 18:25:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14153
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 18:25:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOZU-0001wS-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:25:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWOZ4-0001wF-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:25:18 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWOZ3-0001va-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 18:25:17 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hBGN1M118508
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 18:01:22 -0500
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Date: Tue, 16 Dec 2003 15:24:34 -0800
Message-ID: <000e01c3c42b$c45ad1f0$f5d912c0@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.1165
Content-Transfer-Encoding: 7bit
Subject: [Ipoverib] IPoIB Meeting minutes
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I didn't like the way that the minutes were mime'd - so here it is as a
simple text e-mail
 - same content, different formatting

Bill

Called to Order

Encapsulation draft status -
ADs have asked to merge the encapsulation draft and the multicast draft.
Effort is almost complete

MIB status
Lots of feedback from our MIB doctor Randy P. on the IB MIB drafts - 
Sean is currently working on getting the drafts updated against the 
feedback from Randy.  Will publish ASAP.

There was discussion on 0 basing certain Indexes - historically there 
was an adversion to using 0 as an index in a table - this is not the 
case if the objects being managed are naturally 0 based.  Will update 
TCs to reflect this.

There was a discussion about how the SMA MIB would work through things 
like the Entity MIB - is there a relationship ?

SM MIB presentation
Topspin and Sun are working on a SM MIB that will complement the SMA 
MIB.  The presentation outlines the broad tables that are in this MIB. 
There was general concensus in the room to push this as a Working Group 
item - will confirm on the list

Randy brought up an interesting issue - the objects in the SM MIB mirror

in many cased objects that are on the SMA MIB - something might want to 
be said in the Security considerations section about this.

Randy also mentioned the informational topology MIB - would it be 
interesting to sort information by topology.

Interop testing
When the IPoIB draft is published there will be a need to perform 
interop testing to get to draft Standard.  The proposal is to look at 
the Summer IBTA Plugfest as a place to perform this testing - will 
propose it to both IBTA and the WG list

There will have to be careful design of both test cases - and reporting 
the results that will not violate Plugfest NDA type agreements.


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



From exim@www1.ietf.org  Tue Dec 16 19:49:33 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16848
	for <ipoverib-archive@odin.ietf.org>; Tue, 16 Dec 2003 19:49:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWPs8-0007sq-84
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 19:49:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBH0n4Pf030298
	for ipoverib-archive@odin.ietf.org; Tue, 16 Dec 2003 19:49:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWPs8-0007sb-3M
	for ipoverib-web-archive@optimus.ietf.org; Tue, 16 Dec 2003 19:49:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16818
	for <ipoverib-web-archive@ietf.org>; Tue, 16 Dec 2003 19:49:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWPs6-0004J7-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 19:49:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWPs4-0004It-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 19:49:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWPs4-0004Iq-00
	for ipoverib-web-archive@ietf.org; Tue, 16 Dec 2003 19:49:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWPs4-0007rF-Il; Tue, 16 Dec 2003 19:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWPri-0007ph-9L
	for ipoverib@optimus.ietf.org; Tue, 16 Dec 2003 19:48:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16808
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 19:48:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWPrg-0004IC-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 19:48:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWPrf-0004I5-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 19:48:35 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWPrf-0004Ho-00
	for ipoverib@ietf.org; Tue, 16 Dec 2003 19:48:35 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hBH0On118782
	for <ipoverib@ietf.org>; Tue, 16 Dec 2003 19:24:49 -0500
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Date: Tue, 16 Dec 2003 16:48:00 -0800
Message-ID: <000201c3c437$6c8b4de0$f5d912c0@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.1165
Content-Transfer-Encoding: 7bit
Subject: [Ipoverib] Charter additions to IPoIB
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There are two deliverables that have been proposed to our charter

One is the long standing DHCP Draft (DHCP over IPoIB)

The other is the proposal from Minnesota to add the SM MIB to the
charter.

Before I go and write a proposed charter to include these - are there
any deep seated objections to including either of these ?

Bill


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



From exim@www1.ietf.org  Wed Dec 17 12:19:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21061
	for <ipoverib-archive@odin.ietf.org>; Wed, 17 Dec 2003 12:19:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWfKD-00057B-1q
	for ipoverib-archive@odin.ietf.org; Wed, 17 Dec 2003 12:19:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBHHJ5Bx019656
	for ipoverib-archive@odin.ietf.org; Wed, 17 Dec 2003 12:19:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWfKC-00056r-Px
	for ipoverib-web-archive@optimus.ietf.org; Wed, 17 Dec 2003 12:19:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21011
	for <ipoverib-web-archive@ietf.org>; Wed, 17 Dec 2003 12:19:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWfKB-0007Ia-00
	for ipoverib-web-archive@ietf.org; Wed, 17 Dec 2003 12:19:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWfK9-0007IS-00
	for ipoverib-web-archive@ietf.org; Wed, 17 Dec 2003 12:19:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWfK9-0007IP-00
	for ipoverib-web-archive@ietf.org; Wed, 17 Dec 2003 12:19:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWfK9-000564-6z; Wed, 17 Dec 2003 12:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AWfJn-00055b-Mc
	for ipoverib@optimus.ietf.org; Wed, 17 Dec 2003 12:18:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21003
	for <ipoverib@ietf.org>; Wed, 17 Dec 2003 12:18:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWfJm-0007IE-00
	for ipoverib@ietf.org; Wed, 17 Dec 2003 12:18:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AWfJl-0007I7-00
	for ipoverib@ietf.org; Wed, 17 Dec 2003 12:18:37 -0500
Received: from palrel13.hp.com ([156.153.255.238])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AWfJl-0007I4-00
	for ipoverib@ietf.org; Wed, 17 Dec 2003 12:18:37 -0500
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164])
	by palrel13.hp.com (Postfix) with ESMTP id D7B1F1C00DFC
	for <ipoverib@ietf.org>; Wed, 17 Dec 2003 09:18:36 -0800 (PST)
Received: from mk731915.cup.hp.com ([15.244.172.133])
	by esmail.cup.hp.com (8.11.1/8.8.6) with ESMTP id hBHHAGS00582
	for <ipoverib@ietf.org>; Wed, 17 Dec 2003 09:10:16 -0800 (PST)
Message-Id: <5.1.0.14.2.20031217084719.029169a8@15.13.130.73>
X-Sender: krause@15.13.130.73
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 17 Dec 2003 08:47:41 -0800
To: <ipoverib@ietf.org>
From: Michael Krause <krause@cup.hp.com>
Subject: Re: [Ipoverib] Charter additions to IPoIB
In-Reply-To: <000201c3c437$6c8b4de0$f5d912c0@mobilebill>
Mime-Version: 1.0
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=none autolearn=no version=2.60

At 04:48 PM 12/16/2003 -0800, bill wrote:
>There are two deliverables that have been proposed to our charter
>
>One is the long standing DHCP Draft (DHCP over IPoIB)
>
>The other is the proposal from Minnesota to add the SM MIB to the
>charter.
>
>Before I go and write a proposed charter to include these - are there
>any deep seated objections to including either of these ?

No.  These have been discussed in the past with most people agreeing they 
should be addressed.

Mike


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



From exim@www1.ietf.org  Sat Dec 20 00:10:35 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11888
	for <ipoverib-archive@odin.ietf.org>; Sat, 20 Dec 2003 00:10:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXZNQ-0002pg-23
	for ipoverib-archive@odin.ietf.org; Sat, 20 Dec 2003 00:10:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBK5A8Z1010884
	for ipoverib-archive@odin.ietf.org; Sat, 20 Dec 2003 00:10:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXZNP-0002pT-On
	for ipoverib-web-archive@optimus.ietf.org; Sat, 20 Dec 2003 00:10:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11856
	for <ipoverib-web-archive@ietf.org>; Sat, 20 Dec 2003 00:10:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXZNN-0000Q4-00
	for ipoverib-web-archive@ietf.org; Sat, 20 Dec 2003 00:10:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXZNL-0000Pw-00
	for ipoverib-web-archive@ietf.org; Sat, 20 Dec 2003 00:10:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXZNL-0000Pt-00
	for ipoverib-web-archive@ietf.org; Sat, 20 Dec 2003 00:10:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXZNK-0002ow-3S; Sat, 20 Dec 2003 00:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AXZNF-0002ob-VR
	for ipoverib@optimus.ietf.org; Sat, 20 Dec 2003 00:09:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11848
	for <ipoverib@ietf.org>; Sat, 20 Dec 2003 00:09:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXZND-0000Pp-00
	for ipoverib@ietf.org; Sat, 20 Dec 2003 00:09:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AXZNC-0000Pi-00
	for ipoverib@ietf.org; Sat, 20 Dec 2003 00:09:54 -0500
Received: from kairos.dsa.uqam.ca ([132.208.43.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AXZNC-0000Pf-00
	for ipoverib@ietf.org; Sat, 20 Dec 2003 00:09:54 -0500
Received: from mobilebill (Kairos.dsa.uqam.ca [132.208.43.57])
	by Kairos.dsa.uqam.ca (8.11.4/8.11.4) with ESMTP id hBK4k3101259
	for <ipoverib@ietf.org>; Fri, 19 Dec 2003 23:46:03 -0500
From: "bill" <bill@strahm.net>
To: <ipoverib@ietf.org>
Date: Fri, 19 Dec 2003 21:09:21 -0800
Message-ID: <000301c3c6b7$6e2e78c0$6501a8c0@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.1165
Content-Transfer-Encoding: 7bit
Subject: [Ipoverib] Meeting in Seoul - Scheduling has started
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Well - there are lots of things to discuss... Of particular interest
would be (in no particular order)

1) Implementation reports
2) readiness for Interoperation - IBTA CIWG report on IPoIB interop
3) MIBs again
4) new business

So are there people with presentations to make on these subjects - or
other subjects ?

I'll send this out again after the new year so it won't get lost in
peoples holiday mail

Bill Strahm


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



