RE: [dhcwg] Re: WG last call on <draft-ietf-dhc-isnsoption-04.txt > (Reminder!)
"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Sun, 23 February 2003 03:01 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20104 for <dhcwg-archive@odin.ietf.org>; Sat, 22 Feb 2003 22:01:22 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1N39BU25907 for dhcwg-archive@odin.ietf.org; Sat, 22 Feb 2003 22:09:11 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1N39Bp25904 for <dhcwg-web-archive@optimus.ietf.org>; Sat, 22 Feb 2003 22:09:11 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20057 for <dhcwg-web-archive@ietf.org>; Sat, 22 Feb 2003 22:00:50 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1N376p25351; Sat, 22 Feb 2003 22:07:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1N32Mp25059 for <dhcwg@optimus.ietf.org>; Sat, 22 Feb 2003 22:02:22 -0500
Received: from imr2.ericy.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19929 for <dhcwg@ietf.org>; Sat, 22 Feb 2003 21:54:01 -0500 (EST)
Received: from mr5.exu.ericsson.se (mr5att.ericy.com [138.85.224.141]) by imr2.ericy.com (8.11.3/8.11.3) with ESMTP id h1N2vkb18037; Sat, 22 Feb 2003 20:57:46 -0600 (CST)
Received: from eamrcnt760.exu.ericsson.se (eamrcnt760.exu.ericsson.se [138.85.133.38]) by mr5.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id h1N2vkp12309; Sat, 22 Feb 2003 20:57:46 -0600 (CST)
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <W7Y6MDRQ>; Sat, 22 Feb 2003 20:57:45 -0600
Message-ID: <A1DDC8E21094D511821C00805F6F706B05552E5F@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Franco Travostino' <travos@nortelnetworks.com>, Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org, ips@ece.cmu.edu
Subject: RE: [dhcwg] Re: WG last call on <draft-ietf-dhc-isnsoption-04.txt > (Reminder!)
Date: Sat, 22 Feb 2003 20:56:06 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2DAE7.1BE6095A"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Yes, this is a good point and something we should make clear in all
future options drafts. Minor changes to the Abstract and Introduction
should fix this.
Abstract
This document describes the DHCP option to allow iSNS clients using
DHCP[ for IPv4] to automatically discover the location of the iSNS server. iSNS
...
1. Introduction
The Dynamic Host Configuration Protocol [for IPv4 | [DHCP]] provides a framework for
passing configuration information to hosts.
However, anyone attempting to implement this for DHCPv6 or studying this
carefully would notice:
- No reference to the DHCPv6 specification (there is to the DHCPv4 spec)
- Option numbers and lengths are only 8 bits (not the 16 of DHCPv6)
I support this draft (even without the above changes).
- Bernie
-----Original Message-----
From: Franco Travostino [mailto:travos@nortelnetworks.com]
Sent: Friday, February 21, 2003 2:05 PM
To: Ralph Droms; dhcwg@ietf.org; ips@ece.cmu.edu
Subject: [dhcwg] Re: WG last call on <draft-ietf-dhc-isnsoption-04.txt>
(Reminder!)
I support the draft.
An observation regarding IPv4 vs IPv6. Other DHCP documents make it clear
that they are talking about IPv4 use (e.g., rfc 3361, ""Dynamic Host
Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation
Protocol (SIP) Servers""). If there is an agreed-upon style for defining
applicability, it should be used here as well.
-franco
At 01:23 PM 2/20/2003, Ralph Droms wrote:
>Reminder and note: there has been not response to this WG last
>call. Please review draft-ietf-dhc-isnsoption-04.txt and reply with
>comments. If you recommend the document for advancement without revision,
>please respond with a quick acknowledgment. No response will be
>interpreted as a lack of support for advancing the document.
>
>-----
>
>This message announces a WG last call on "DHCP Options for Internet
>Storage Name Service" <draft-ietf-dhc-isnsoption-04.txt>. The last call
>will conclude on Friday, 2/21.
>
>Note that this is a parallel WG last call in the dhc and ips WGs.
>
>draft-ietf-dhc-isnsoption-04.txt defines a new DHCP option for discovery
>of the location and role of iSNS Protocol servers in iSCSI and iFCP
>devices. The draft is available at
>http://www.ietf.org/internet-drafts/draft-ietf-dhc-isnsoption-04.txt
>
>- Ralph Droms
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg
- RE: [dhcwg] Re: WG last call on <draft-ietf-dhc-i… Bernie Volz (EUD)