RE: [dhcwg] Last call on two DHCPv6 docs
"Vijayabhaskar A K" <vijayak@india.hp.com> Tue, 07 May 2002 12:58 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 IAA05867 for <dhcwg-archive@odin.ietf.org>; Tue, 7 May 2002 08:58:17 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id IAA22449 for dhcwg-archive@odin.ietf.org; Tue, 7 May 2002 08:58:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA22356; Tue, 7 May 2002 08:56:11 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA22328 for <dhcwg@optimus.ietf.org>; Tue, 7 May 2002 08:56:10 -0400 (EDT)
Received: from atlrel8.hp.com (atlrel8.hp.com [156.153.255.206]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05751 for <dhcwg@ietf.org>; Tue, 7 May 2002 08:56:01 -0400 (EDT)
Received: from hpuxsrv.india.hp.com (hpuxsrv.india.hp.com [15.10.45.132]) by atlrel8.hp.com (Postfix) with ESMTP id 62D9BA00430; Tue, 7 May 2002 08:55:30 -0400 (EDT)
Received: from nt4147 (nt4147.india.hp.com [15.10.41.47]) by hpuxsrv.india.hp.com with SMTP (8.8.6 (PHNE_17135)/8.8.6 SMKit7.02) id SAA28660; Tue, 7 May 2002 18:20:22 +0530 (IST)
Reply-To: vijayak@india.hp.com
From: Vijayabhaskar A K <vijayak@india.hp.com>
To: 'Ralph Droms' <rdroms@cisco.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Last call on two DHCPv6 docs
Date: Tue, 07 May 2002 18:27:21 +0530
Message-ID: <002401c1f5c6$ba758c00$2f290a0f@india.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <4.3.2.7.2.20020507052110.0373c8c0@funnel.cisco.com>
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit
The Domain Name Server option MUST appear only in the following messages: Solicit, Advertise, Request, Confirm, Renew, Rebind, Information-Request, Reply. The Domain Search List option MUST appear only in the following messages: Solicit, Advertise, Request, Confirm, Renew, Rebind, Information-Request, Reply. Do these options really need to appear in all the above mesg types? Because, for all the messages originating from client, ORO option filled with DNS server/ Domain Search list option number will do. If there are muliple options the client is requesting, this will save some bytes also, if ORO is used for this. I feel that only in Reply message, this is needed. > -----Original Message----- > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of > Ralph Droms > Sent: Tuesday, May 07, 2002 3:01 PM > To: dhcwg@ietf.org > Subject: [dhcwg] Last call on two DHCPv6 docs > > > These two docs were originally part of the DHCPv6 draft that > went through > WG last call: > > draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt > draft-ietf-dhc-dhcpv6-opt-dstm-01.txt > > Unless there is an objection by 5PM Wed, 5/8, I will request > IETF last call > on these docs. > > - Ralph Droms > > > > _______________________________________________ > dhcwg mailing list > dhcwg@ietf.org > https://www1.ietf.org/mailman/listinfo/dhcwg > _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Last call on two DHCPv6 docs Ralph Droms
- RE: [dhcwg] Last call on two DHCPv6 docs Vijayabhaskar A K
- RE: [dhcwg] Last call on two DHCPv6 docs Bernie Volz (EUD)