IETF Logo Mail Archive

RE: [dhcwg] Stateless DHCPv6 service

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Tue, 13 May 2003 18:51 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 OAA24174 for <dhcwg-archive@odin.ietf.org>; Tue, 13 May 2003 14:51:08 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DIHHT18365 for dhcwg-archive@odin.ietf.org; Tue, 13 May 2003 14:17:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DIHHB18359 for <dhcwg-web-archive@optimus.ietf.org>; Tue, 13 May 2003 14:17:17 -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 OAA24157 for <dhcwg-web-archive@ietf.org>; Tue, 13 May 2003 14:50:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fet8-0006kq-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 14:52:34 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Fet8-0006kn-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 14:52:34 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DIB3B17982; Tue, 13 May 2003 14:11:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DHtHB16271 for <dhcwg@optimus.ietf.org>; Tue, 13 May 2003 13:55:17 -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 OAA23551 for <dhcwg@ietf.org>; Tue, 13 May 2003 14:28:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FeXq-0006bv-00 for dhcwg@ietf.org; Tue, 13 May 2003 14:30:34 -0400
Received: from imr2.ericy.com ([198.24.6.3]) by ietf-mx with esmtp (Exim 4.12) id 19FeXp-0006bm-00 for dhcwg@ietf.org; Tue, 13 May 2003 14:30:33 -0400
Received: from mr5.exu.ericsson.se (mr5att.ericy.com [138.85.224.141]) by imr2.ericy.com (8.12.9/8.12.9) with ESMTP id h4DIUlnS001272; Tue, 13 May 2003 13:30:47 -0500 (CDT)
Received: from eamrcnt761.exu.ericsson.se (eamrcnt761.exu.ericsson.se [138.85.133.39]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h4DIUl2V009103; Tue, 13 May 2003 13:30:47 -0500 (CDT)
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <KZ62855L>; Tue, 13 May 2003 13:30:47 -0500
Message-ID: <A1DDC8E21094D511821C00805F6F706B067F5DAE@eamrcnt715.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: 'Peter Barany' <pbarany@nortelnetworks.com>, "'juha.wiljakka@nokia.com'" <juha.wiljakka@nokia.com>, rdroms@cisco.com
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] Stateless DHCPv6 service
Date: Tue, 13 May 2003 13:28:41 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3197D.7A94D90C"
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>

It can send a single Reply with the 2 options.

-----Original Message-----
From: Peter Barany [mailto:pbarany@nortelnetworks.com]
Sent: Thursday, May 08, 2003 4:53 PM
To: 'juha.wiljakka@nokia.com'; rdroms@cisco.com
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] Stateless DHCPv6 service



Hi, 

A question: If a DHCPV6 client sends an Information-Request message containing, for example, the DNS resolver option, SIP server option, and NTP server option and the DHCPv6 server can only return 2 of the 3 configuration options (due to policy reasons, administrative reasons, etc.), does the DHCPv6 spec (and the stateless DHCPv6 spec) allow the DHCPv6 server to send a Reply message with 2 of the 3? Or does it have to send a Reply with the status code "UnspecFail"? If so, this means that the DHCPv6 client should send 3 separate Information-Request messages? Thanks.

Regards, 

Pete 

-----Original Message----- 
From: juha.wiljakka@nokia.com [ mailto:juha.wiljakka@nokia.com <mailto:juha.wiljakka@nokia.com> ] 
Sent: Monday, April 14, 2003 6:41 AM 
To: rdroms@cisco.com 
Cc: dhcwg@ietf.org 
Subject: RE: [dhcwg] Stateless DHCPv6 service 


Hi, Ralph! 

This document looks good, I personally support starting wglc for it. 

By the way, are you going to mention other options than DNS and Time Configuration Options? I think this would also be useful:

http://www.ietf.org/internet-drafts/draft-ietf-sip-dhcpv6-01.txt <http://www.ietf.org/internet-drafts/draft-ietf-sip-dhcpv6-01.txt>  

Best Regards, 
                  -Juha W.- 

-----Original Message----- 
From: ext Ralph Droms [ mailto:rdroms@cisco.com <mailto:rdroms@cisco.com> ] 
Sent: 06 April, 2003 16:07 
To: dhcwg@ietf.org 
Subject: [dhcwg] Stateless DHCPv6 service 


Now that the DHCPv6 base specification is at PS, and the DNS and time configuration option specs have passed WG last call, I have published "A Guide to Implementing Stateless DHCPv6 Service" as a dhc WG document, draft-ietf-dhc-dhcpv6-stateless-00.txt.

This revision of the document has been reviewed by Pekka Savola and Christian Huitema, and includes changes based on their input.  Based on the interest in this specification, I would like to progress it quickly.  Unless there are objections, I will start a WG last call for the specification in a week or so.

- Ralph 

_______________________________________________ 
dhcwg mailing list 
dhcwg@ietf.org 
https://www1.ietf.org/mailman/listinfo/dhcwg <https://www1.ietf.org/mailman/listinfo/dhcwg>  
_______________________________________________ 
dhcwg mailing list 
dhcwg@ietf.org 
https://www1.ietf.org/mailman/listinfo/dhcwg <https://www1.ietf.org/mailman/listinfo/dhcwg>

v2.23.0 | Report a Bug | By Email