From ipoverib-admin@ietf.org Sat Jul 5 20:48:29 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21023 for ; Sat, 5 Jul 2003 20:48:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YxhB-0006eC-73; Sat, 05 Jul 2003 20:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yxgi-0006dw-5g for ipoverib@optimus.ietf.org; Sat, 05 Jul 2003 20:47:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21011 for ; Sat, 5 Jul 2003 20:47:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yxgf-0006cy-00 for ipoverib@ietf.org; Sat, 05 Jul 2003 20:47:29 -0400 Received: from [204.127.198.39] (helo=rwcrmhc13.comcast.net) by ietf-mx with esmtp (Exim 4.12) id 19Yxgf-0006cv-00 for ipoverib@ietf.org; Sat, 05 Jul 2003 20:47:29 -0400 Received: from mobilebill (12-225-210-60.client.attbi.com[12.225.210.60](untrusted sender)) by attbi.com (rwcrmhc13) with SMTP id <20030706004654015000sq3de>; Sun, 6 Jul 2003 00:46:54 +0000 From: "bill" To: "'bill'" , Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt Date: Sat, 5 Jul 2003 17:46:41 -0700 Message-ID: <000a01c34358$144ba270$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.2627 In-Reply-To: <000001c33565$00e236a0$1c02a8c0@mobilebill> 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: , List-Id: IP over InfiniBand WG Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I have received no issues with this draft. Can I get people that have read the architecture draft to ping me or the list and say so. This is the end of the last call for the architecture, encapsulation and link drafts. As soon as possible (hopefully before Vienna) I will contact Thomas and have him get these on the IESG agenda Bill -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of bill Sent: Tuesday, June 17, 2003 11:44 PM To: ipoverib@ietf.org Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt The only major fault that came up in last call of the encapsulation/link drafts was the fact that they referenced the architecture draft that hadn't been updated or put through last call. So with the publication of the architecture draft below I would like to call a working group last call on the architecture. So if you have issues please forward them to the list (or author) by July 4 so we can push these drafts to IESG last call after the upcoming IETF meeting. Thank you Bill Strahm -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, June 09, 2003 4:45 AM To: IETF-Announce: Cc: ipoverib@ietf.org Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over InfiniBand Working Group of the IETF. Title : IP over InfiniBand(IPoIB) Architecture Author(s) : V. Kashyap Filename : draft-ietf-ipoib-architecture-02.txt Pages : 24 Date : 2003-6-6 InfiniBand is a high speed, channel based interconnect between systems and devices. This document presents an overview of the InfiniBand architecture. It further describes the requirements and guidelines for the transmission of IP over InfiniBand. Discussions in this document are applicable to both IPv4 and IPv6 unless explicitly specified. The encapsulation of IP over InfiniBand and the mechanism for IP address resolution on IB fabrics are covered in [IPOIB_MCAST], [IPOIB_ENCAP] and [IPOIB_DHCP]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-02.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-architecture-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipoib-architecture-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib From exim@www1.ietf.org Sat Jul 5 20:48:31 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21038 for ; Sat, 5 Jul 2003 20:48:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YxhE-0006eh-4v for ipoverib-archive@odin.ietf.org; Sat, 05 Jul 2003 20:48:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h660m4OB025579 for ipoverib-archive@odin.ietf.org; Sat, 5 Jul 2003 20:48:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YxhE-0006eU-1n for ipoverib-web-archive@optimus.ietf.org; Sat, 05 Jul 2003 20:48:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21017 for ; Sat, 5 Jul 2003 20:48:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YxhB-0006d5-00 for ipoverib-web-archive@ietf.org; Sat, 05 Jul 2003 20:48:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YxhB-0006d1-00 for ipoverib-web-archive@ietf.org; Sat, 05 Jul 2003 20:48:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YxhB-0006eC-73; Sat, 05 Jul 2003 20:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yxgi-0006dw-5g for ipoverib@optimus.ietf.org; Sat, 05 Jul 2003 20:47:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21011 for ; Sat, 5 Jul 2003 20:47:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yxgf-0006cy-00 for ipoverib@ietf.org; Sat, 05 Jul 2003 20:47:29 -0400 Received: from [204.127.198.39] (helo=rwcrmhc13.comcast.net) by ietf-mx with esmtp (Exim 4.12) id 19Yxgf-0006cv-00 for ipoverib@ietf.org; Sat, 05 Jul 2003 20:47:29 -0400 Received: from mobilebill (12-225-210-60.client.attbi.com[12.225.210.60](untrusted sender)) by attbi.com (rwcrmhc13) with SMTP id <20030706004654015000sq3de>; Sun, 6 Jul 2003 00:46:54 +0000 From: "bill" To: "'bill'" , Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt Date: Sat, 5 Jul 2003 17:46:41 -0700 Message-ID: <000a01c34358$144ba270$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.2627 In-Reply-To: <000001c33565$00e236a0$1c02a8c0@mobilebill> 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: , List-Id: IP over InfiniBand WG Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I have received no issues with this draft. Can I get people that have read the architecture draft to ping me or the list and say so. This is the end of the last call for the architecture, encapsulation and link drafts. As soon as possible (hopefully before Vienna) I will contact Thomas and have him get these on the IESG agenda Bill -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of bill Sent: Tuesday, June 17, 2003 11:44 PM To: ipoverib@ietf.org Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt The only major fault that came up in last call of the encapsulation/link drafts was the fact that they referenced the architecture draft that hadn't been updated or put through last call. So with the publication of the architecture draft below I would like to call a working group last call on the architecture. So if you have issues please forward them to the list (or author) by July 4 so we can push these drafts to IESG last call after the upcoming IETF meeting. Thank you Bill Strahm -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, June 09, 2003 4:45 AM To: IETF-Announce: Cc: ipoverib@ietf.org Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over InfiniBand Working Group of the IETF. Title : IP over InfiniBand(IPoIB) Architecture Author(s) : V. Kashyap Filename : draft-ietf-ipoib-architecture-02.txt Pages : 24 Date : 2003-6-6 InfiniBand is a high speed, channel based interconnect between systems and devices. This document presents an overview of the InfiniBand architecture. It further describes the requirements and guidelines for the transmission of IP over InfiniBand. Discussions in this document are applicable to both IPv4 and IPv6 unless explicitly specified. The encapsulation of IP over InfiniBand and the mechanism for IP address resolution on IB fabrics are covered in [IPOIB_MCAST], [IPOIB_ENCAP] and [IPOIB_DHCP]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-02.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-architecture-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipoib-architecture-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib From ipoverib-admin@ietf.org Wed Jul 9 17:58:33 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24317 for ; Wed, 9 Jul 2003 17:58:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwr-0001UC-8K; Wed, 09 Jul 2003 17:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwO-0001Tm-BT for ipoverib@optimus.ietf.org; Wed, 09 Jul 2003 17:57:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24295 for ; Wed, 9 Jul 2003 17:57:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMwL-00048s-00 for ipoverib@ietf.org; Wed, 09 Jul 2003 17:57:29 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 19aMwK-00048p-00 for ipoverib@ietf.org; Wed, 09 Jul 2003 17:57:28 -0400 Received: from jurassic.eng.sun.com ([129.146.17.55]) by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h69LvR1J029988; Wed, 9 Jul 2003 15:57:27 -0600 (MDT) Received: from taipei (taipei.Eng.Sun.COM [129.146.85.178]) by jurassic.eng.sun.com (8.12.10.Beta0+Sun/8.12.10.Beta0) with SMTP id h69LvRtf839220; Wed, 9 Jul 2003 14:57:27 -0700 (PDT) Message-Id: <200307092157.h69LvRtf839220@jurassic.eng.sun.com> Date: Wed, 9 Jul 2003 14:57:29 -0700 (PDT) From: "H.K. Jerry Chu" Reply-To: "H.K. Jerry Chu" Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt To: bill@strahm.net Cc: ipoverib@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: vZFDVrwdlunX2TKOZwRpXg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 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: , List-Id: IP over InfiniBand WG Discussion List List-Post: List-Help: List-Subscribe: , Bill, I have reviewed this draft and thought it looks ok. One possible issue is that the draft includes quite a bit of discussions on the "rationale" aspect of the current IPoIB design, consequently duplicating many materials from the other IPoIB drafts. Since the draft will be informational only, perhaps this redundancy is not a problem? Jerry ------------------------------------------------------------------------ I have received no issues with this draft. Can I get people that have read the architecture draft to ping me or the list and say so. This is the end of the last call for the architecture, encapsulation and link drafts. As soon as possible (hopefully before Vienna) I will contact Thomas and have him get these on the IESG agenda Bill -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of bill Sent: Tuesday, June 17, 2003 11:44 PM To: ipoverib@ietf.org Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt The only major fault that came up in last call of the encapsulation/link drafts was the fact that they referenced the architecture draft that hadn't been updated or put through last call. So with the publication of the architecture draft below I would like to call a working group last call on the architecture. So if you have issues please forward them to the list (or author) by July 4 so we can push these drafts to IESG last call after the upcoming IETF meeting. Thank you Bill Strahm -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, June 09, 2003 4:45 AM To: IETF-Announce: Cc: ipoverib@ietf.org Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over InfiniBand Working Group of the IETF. Title : IP over InfiniBand(IPoIB) Architecture Author(s) : V. Kashyap Filename : draft-ietf-ipoib-architecture-02.txt Pages : 24 Date : 2003-6-6 InfiniBand is a high speed, channel based interconnect between systems and devices. This document presents an overview of the InfiniBand architecture. It further describes the requirements and guidelines for the transmission of IP over InfiniBand. Discussions in this document are applicable to both IPv4 and IPv6 unless explicitly specified. The encapsulation of IP over InfiniBand and the mechanism for IP address resolution on IB fabrics are covered in [IPOIB_MCAST], [IPOIB_ENCAP] and [IPOIB_DHCP]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-02.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-architecture-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipoib-architecture-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib ------------------------------------------------------------------------ * *References*: o *RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt * + /From:/ "bill" * Prev by Date: *[Ipoverib] I-D ACTION:draft-ietf-ipoib-ibif-mib-05.txt * * Previous by thread: *RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt * * Next by thread: *[Ipoverib] 57th IETF * * Index(es): o *Date* o *Thread* _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib From exim@www1.ietf.org Wed Jul 9 17:58:36 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24334 for ; Wed, 9 Jul 2003 17:58:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwy-0001VD-Ts for ipoverib-archive@odin.ietf.org; Wed, 09 Jul 2003 17:58:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69Lw8Pv005769 for ipoverib-archive@odin.ietf.org; Wed, 9 Jul 2003 17:58:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwy-0001Uy-O6 for ipoverib-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17:58:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24311 for ; Wed, 9 Jul 2003 17:58:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMww-00049A-00 for ipoverib-web-archive@ietf.org; Wed, 09 Jul 2003 17:58:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aMwv-000496-00 for ipoverib-web-archive@ietf.org; Wed, 09 Jul 2003 17:58:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwr-0001UC-8K; Wed, 09 Jul 2003 17:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMwO-0001Tm-BT for ipoverib@optimus.ietf.org; Wed, 09 Jul 2003 17:57:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24295 for ; Wed, 9 Jul 2003 17:57:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMwL-00048s-00 for ipoverib@ietf.org; Wed, 09 Jul 2003 17:57:29 -0400 Received: from brmea-mail-3.sun.com ([192.18.98.34]) by ietf-mx with esmtp (Exim 4.12) id 19aMwK-00048p-00 for ipoverib@ietf.org; Wed, 09 Jul 2003 17:57:28 -0400 Received: from jurassic.eng.sun.com ([129.146.17.55]) by brmea-mail-3.sun.com (8.12.9/8.12.9) with ESMTP id h69LvR1J029988; Wed, 9 Jul 2003 15:57:27 -0600 (MDT) Received: from taipei (taipei.Eng.Sun.COM [129.146.85.178]) by jurassic.eng.sun.com (8.12.10.Beta0+Sun/8.12.10.Beta0) with SMTP id h69LvRtf839220; Wed, 9 Jul 2003 14:57:27 -0700 (PDT) Message-Id: <200307092157.h69LvRtf839220@jurassic.eng.sun.com> Date: Wed, 9 Jul 2003 14:57:29 -0700 (PDT) From: "H.K. Jerry Chu" Reply-To: "H.K. Jerry Chu" Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt To: bill@strahm.net Cc: ipoverib@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: vZFDVrwdlunX2TKOZwRpXg== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 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: , List-Id: IP over InfiniBand WG Discussion List List-Post: List-Help: List-Subscribe: , Bill, I have reviewed this draft and thought it looks ok. One possible issue is that the draft includes quite a bit of discussions on the "rationale" aspect of the current IPoIB design, consequently duplicating many materials from the other IPoIB drafts. Since the draft will be informational only, perhaps this redundancy is not a problem? Jerry ------------------------------------------------------------------------ I have received no issues with this draft. Can I get people that have read the architecture draft to ping me or the list and say so. This is the end of the last call for the architecture, encapsulation and link drafts. As soon as possible (hopefully before Vienna) I will contact Thomas and have him get these on the IESG agenda Bill -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of bill Sent: Tuesday, June 17, 2003 11:44 PM To: ipoverib@ietf.org Subject: RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt The only major fault that came up in last call of the encapsulation/link drafts was the fact that they referenced the architecture draft that hadn't been updated or put through last call. So with the publication of the architecture draft below I would like to call a working group last call on the architecture. So if you have issues please forward them to the list (or author) by July 4 so we can push these drafts to IESG last call after the upcoming IETF meeting. Thank you Bill Strahm -----Original Message----- From: ipoverib-admin@ietf.org [mailto:ipoverib-admin@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, June 09, 2003 4:45 AM To: IETF-Announce: Cc: ipoverib@ietf.org Subject: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP over InfiniBand Working Group of the IETF. Title : IP over InfiniBand(IPoIB) Architecture Author(s) : V. Kashyap Filename : draft-ietf-ipoib-architecture-02.txt Pages : 24 Date : 2003-6-6 InfiniBand is a high speed, channel based interconnect between systems and devices. This document presents an overview of the InfiniBand architecture. It further describes the requirements and guidelines for the transmission of IP over InfiniBand. Discussions in this document are applicable to both IPv4 and IPv6 unless explicitly specified. The encapsulation of IP over InfiniBand and the mechanism for IP address resolution on IB fabrics are covered in [IPOIB_MCAST], [IPOIB_ENCAP] and [IPOIB_DHCP]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipoib-architecture-02.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-architecture-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipoib-architecture-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib ------------------------------------------------------------------------ * *References*: o *RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt * + /From:/ "bill" * Prev by Date: *[Ipoverib] I-D ACTION:draft-ietf-ipoib-ibif-mib-05.txt * * Previous by thread: *RE: [Ipoverib] I-D ACTION:draft-ietf-ipoib-architecture-02.txt * * Next by thread: *[Ipoverib] 57th IETF * * Index(es): o *Date* o *Thread* _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org https://www1.ietf.org/mailman/listinfo/ipoverib