[dhcwg] Comments to draft-23
Tony Lindström (ERA) <tony.lindstrom@era.ericsson.se> Tue, 26 February 2002 07:49 UTC
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 CAA20140 for <dhcwg-archive@odin.ietf.org>; Tue, 26 Feb 2002 02:49:51 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id CAA24421 for dhcwg-archive@odin.ietf.org; Tue, 26 Feb 2002 02:49:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24180; Tue, 26 Feb 2002 02:40:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA24149 for <dhcwg@optimus.ietf.org>; Tue, 26 Feb 2002 02:40:06 -0500 (EST)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.46]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20033 for <dhcwg@ietf.org>; Tue, 26 Feb 2002 02:40:03 -0500 (EST)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62]) by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with SMTP id g1Q7e4Zc015749 for <dhcwg@ietf.org>; Tue, 26 Feb 2002 08:40:04 +0100 (MET)
Received: FROM esealnt444.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Feb 26 08:40:03 2002 +0100
Received: by esealnt444 with Internet Mail Service (5.5.2653.19) id <F4G9P4J6>; Tue, 26 Feb 2002 08:39:08 +0100
Message-ID: <1254192C94D3D411B8060008C7E6AEEBF9DCEB@esealnt408>
From: "Tony Lindström (ERA)" <tony.lindstrom@era.ericsson.se>
To: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Date: Tue, 26 Feb 2002 08:39:34 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [dhcwg] Comments to draft-23
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Hi, I have some comments on draft-23. In chapter 16.3, second and third bullets mention checks on Client Identifier. In chapter 18.2.2 'Creation and transmission of Advertise messages' Nothing is mention about Client Identifier. I think a paragraph telling that Client Identifier MUST be added is needed. In 'A. Appearance of Options in Message Types' The option RTA is indicated in Advertise, Confirm, Decline, Relese and Reply massege, but according to the option RTA it is stated 'This option MUST only be sent by a client and only in a Solicit, Request, Renew, or Rebind message'. I think the table needs to be updated. In 'B. Appearance of Options in the Options Field of DHCP Messages' The option RTA is indicated as encapsulated to an IAADDR but in the option it says, 'It MUST only appear encapsulated within an Identity association option.' I'm not sure what Client Forw. and Server Forw. mean, but are both relevant to both Client msg and Server msg? (The same comments on 'A. Appearance of Options in Message Types'). In the 'IA Address option' is it possible to move the 'T', 'addr status' and 'prefix length' fields after valid lifetime. I think the handling of the IP address etc. will be easier. Regards, Tony _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Comments to draft-23 Tony Lindström (ERA)