From mailnull@www1.ietf.org Thu May 1 10:45:28 2003 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 KAA14663 for ; Thu, 1 May 2003 10:45:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41EpWC15399 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:51:32 -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 h41EpV815396 for ; Thu, 1 May 2003 10:51:31 -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 KAA14623 for ; Thu, 1 May 2003 10:44:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFKr-0002Bx-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:46:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFKr-0002Bu-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:46:57 -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 h41EnV814970; Thu, 1 May 2003 10:49:33 -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 h41EfD812612 for ; Thu, 1 May 2003 10:41:13 -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 KAA13913 for ; Thu, 1 May 2003 10:34:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFB3-00020g-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:49 -0400 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19BFAy-00020O-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:44 -0400 Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h41EahWS018366 for ; Thu, 1 May 2003 10:36:44 -0400 (EDT) Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01095 for ; Thu, 1 May 2003 10:36:43 -0400 (EDT) Message-Id: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> X-Sender: rdroms@funnel.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 May 2003 09:52:19 -0400 To: dhcwg@ietf.org From: Ralph Droms In-Reply-To: References: <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dhcwg] Address selection for Information-request/Reply messages 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: , List-Id: List-Post: List-Help: List-Subscribe: , At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >1. address selection of Information-request/Reply exchanges > >According to the DHCPv6 base spec, the client should send Information >Request messages to the All_DHCP_Relay_Agents_and_Servers multicast >address (FF02::1:2). However, doesn't it make much sense to allow the >client to send the requests to the All_DHCP_Servers multicast address >FF05::1:3? Since the stateless usage assumes the client has obtained >its IPv6 addresses through some other mechanism, I don't see a reason >that the client cannot do so. If we allow this, the client can access >an off-link server without relying on a relay agent, which would help >the deployment. On the other hand, we don't want to require deployment of multicast to enable stateless DHCPv6. One possibility would be to allow the use of All_DHCP_Servers, with an explicit warning that a site that doesn't implement multicast MUST use relay agents AND the relay agents must listen to All_DHCP_Servers (which is a change from the current spec). In fact, it would be important to note that a site MUST NOT both implement multicast and configure relay agents to listen on All_DHCP_Servers, as such a configuration would result in the servers receiving multiple copies of client messages. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 10:49:30 2003 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 KAA14903 for ; Thu, 1 May 2003 10:49:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41EtYT16016 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:55:34 -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 h41EtY816013 for ; Thu, 1 May 2003 10:55:34 -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 KAA14892 for ; Thu, 1 May 2003 10:48:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFOr-0002FU-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:51:05 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFOr-0002FI-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:51:05 -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 h41Err815928; Thu, 1 May 2003 10:53:53 -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 h41EfG812620 for ; Thu, 1 May 2003 10:41:16 -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 KAA13920 for ; Thu, 1 May 2003 10:34:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFB6-00020m-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:52 -0400 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19BFB0-00020Q-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:46 -0400 Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h41EajWS018390 for ; Thu, 1 May 2003 10:36:46 -0400 (EDT) Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01114 for ; Thu, 1 May 2003 10:36:45 -0400 (EDT) Message-Id: <4.3.2.7.2.20030501095650.00b9b090@funnel.cisco.com> X-Sender: rdroms@funnel.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 May 2003 09:58:56 -0400 To: dhcwg@ietf.org From: Ralph Droms In-Reply-To: References: <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dhcwg] When to invoke the stateless DHCPv6 message exchange 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: , List-Id: List-Post: List-Help: List-Subscribe: , At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >3. how to restart the stateless procedure > >It would be useful if we had a guideline where the client should >restart the Information-request/Reply exchanges, particularly when the >client is a nomadic host moving link to link. Section 18.1.2 of the >base specification can be a good example of this. Good point. I'll add text based on the text from 18.1.2 in dhcpv6-28. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 10:50:38 2003 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 KAA14979 for ; Thu, 1 May 2003 10:50:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41Eugd16098 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:56:42 -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 h41Eug816095 for ; Thu, 1 May 2003 10:56:42 -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 KAA14927 for ; Thu, 1 May 2003 10:49:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFPs-0002Fs-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:08 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFPr-0002Fp-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:07 -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 h41Epd815415; Thu, 1 May 2003 10:51:39 -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 h41EfE812616 for ; Thu, 1 May 2003 10:41:14 -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 KAA13916 for ; Thu, 1 May 2003 10:34:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFB4-00020j-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:50 -0400 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19BFAy-00020P-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:44 -0400 Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h41EaiWS018374 for ; Thu, 1 May 2003 10:36:44 -0400 (EDT) Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01102 for ; Thu, 1 May 2003 10:36:43 -0400 (EDT) Message-Id: <4.3.2.7.2.20030501095224.00b99538@funnel.cisco.com> X-Sender: rdroms@funnel.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 May 2003 09:55:35 -0400 To: dhcwg@ietf.org From: Ralph Droms In-Reply-To: References: <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dhcwg] Update of parameters supplied through stateless DHCPv6 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: , List-Id: List-Post: List-Help: List-Subscribe: , At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >2. how to invalidate stale configuration parameters > >The stateless usage does not have the notion of Renew or Rebind. So, >how the client can purge configuration parameters (e.g. DNS addresses) >when they become invalidated? I guess we need a some kind of >"timeout" parameter, which suggests to the client that it refresh the >parameters in a certain period. Bernie responded to this issue: >There are three mechanisms available: > >a. Whenever the client would normally determine that its stateless addresses >are suspect, after confirming them or obtaining new addresses, it can use >Information-Request to obtain new parameters. Note that a client may also >use triggers such as existing address lifetimes expiring (if a prefix is >has expired, it likely means some changes to the networks configuration and >hence doing an Information-Request to obtain updated parameters may be in >order). > >b. The server can send a Reconfigure provided the client has communicated it >is able/willing to support this in the Information-Request. > >c. The client is free to do Information-Requests at times of its choosing >(there is no prohibition against doing this). Of course, the client >should not do this too frequently. > >If someone feels these mechanisms are insufficient, they could always write >a draft that specifies an "Information Lifetime" or "Information Renewal Time" >at which point the client could refresh the information. This option could >specify T1 and T2 times - at T1 the client renews by including the server >identifier option of the server that gave it the configuration parameters, at >T2 it removes this option and any server may respond to the Information-Request. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 10:51:14 2003 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 KAA15010 for ; Thu, 1 May 2003 10:51:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41EvJ316200 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:57:19 -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 h41EvJ816197 for ; Thu, 1 May 2003 10:57:19 -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 KAA14983 for ; Thu, 1 May 2003 10:50:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFQX-0002GS-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:49 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFQX-0002GK-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:52:49 -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 h41Etu816049; Thu, 1 May 2003 10:55:56 -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 h41EfH812624 for ; Thu, 1 May 2003 10:41: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 KAA13923 for ; Thu, 1 May 2003 10:34:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFB7-00020p-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:53 -0400 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19BFB1-00020R-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:36:47 -0400 Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h41EakWS018401; Thu, 1 May 2003 10:36:47 -0400 (EDT) Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01118; Thu, 1 May 2003 10:36:46 -0400 (EDT) Message-Id: <4.3.2.7.2.20030501095907.00b99538@funnel.cisco.com> X-Sender: rdroms@funnel.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 May 2003 10:07:10 -0400 To: dhcwg@ietf.org, ipng@sunroof.eng.sun.com From: Ralph Droms In-Reply-To: References: <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dhcwg] Stateless DHCPv6 == "Other stateful configuration"? 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: , List-Id: List-Post: List-Help: List-Subscribe: , The following comment was posted to the dhcwg mailing list during the WG last call on draft-ietf-dhc-dhcpv6-stateless-00.txt Because the issue touches on RFC 2461 and RFC 2462, I've cross-posted to both the ipv6 and dhc WG mailing lists. Please respond to the dhcwg@ietf.org mailing list - RD At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >4. interaction/consistency with RFC 246[12] > >How the stateless usage is related to the "Other stateful >configuration" of router advertisements defined in RFC 2461 and 2462? >Is the client (host) expected to start the stateless DHCPv6 when it >receives a router advertisement with the "Other stateful >configuration" flag being set? If so, how can we interpret the >"inconsistency" between the "stateless" DHCPv6 usage and the >"stateful" router advertisement flag? Perhaps this is just a matter >of wording. But, if RFC 2461 really intended a "stateful" protocol >(i.e., where a server maintains lease state for the other >configuration parameters), we may need to consider the gap as a >fundamental architecture issue. Well, I guess we first need to agree that draft-ietf-dhc-dhcpv6-stateless-00.txt meets the expectation of "Other stateful configuration" in RFC 2461. I intended draft-ietf-dhc-dhcpv6-stateless-00.txt to be the configuration protocol used when the "Other stateful configuration" flag is set. Is there any objection to explicitly specifying draft-ietf-dhc-dhcpv6-stateless-00.txt for this use? If there is no objection, we'll need to adjust the words to make the connection explicit and avoid confusion... - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 10:53:45 2003 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 KAA15109 for ; Thu, 1 May 2003 10:53:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41Exnk16443 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 10:59:49 -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 h41Exn816440 for ; Thu, 1 May 2003 10:59:49 -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 KAA15087 for ; Thu, 1 May 2003 10:53:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFSt-0002Hh-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:55:15 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BFSs-0002He-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 10:55:14 -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 h41Ew0816295; Thu, 1 May 2003 10:58:00 -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 h41Eff812642 for ; Thu, 1 May 2003 10:41:41 -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 KAA13938 for ; Thu, 1 May 2003 10:35:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BFBW-00021B-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:37:18 -0400 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by ietf-mx with esmtp (Exim 4.12) id 19BFBQ-00020N-00 for dhcwg@ietf.org; Thu, 01 May 2003 10:37:12 -0400 Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h41Eah4c000491 for ; Thu, 1 May 2003 10:36:43 -0400 (EDT) Received: from rdroms-w2k.cisco.com (rtp-vpn2-797.cisco.com [10.82.243.29]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA01092 for ; Thu, 1 May 2003 10:36:42 -0400 (EDT) Message-Id: <4.3.2.7.2.20030430185732.044dbaf0@funnel.cisco.com> X-Sender: rdroms@funnel.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 01 May 2003 09:40:17 -0400 To: dhcwg@ietf.org From: Ralph Droms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [dhcwg] Results of recent WG last calls 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: , List-Id: List-Post: List-Help: List-Subscribe: , Here are the results of some recent last WG last calls: draft-ietf-dhc-suboptions-kdc-serveraddress-03.txt See http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg01968.html for a comment. No other comments about this draft were received during the last call. This draft did not receive enough positive support to be submitted to the IESG. ===== draft-ietf-dhc-dhcpv6-loadb-02.txt No comments about this document were received during the last call. This draft did not receive enough positive support to be submitted to the IESG. ===== draft-ietf-dhc-dhcpv6-interop-01.txt Jinmei-san responded that this draft is ready for submission to the IESG. No other comments about this draft were received during the last call. Although this draft only received one comment during WG last call, it is important to move the draft forward because it should be published before the DHCPv6 specification is published as an RFC. Also, this draft will be published as Informational, rather than as an Internet Standard. Therefore, I will submit the draft to the IESG. ===== draft-ietf-dhc-dhcpv6-stateless-00.txt Jinmei-san posted a comment about the draft that started a discussion thread on the mailing list (see http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg01999.html) There were several comments suggesting that stateless DHCPv6 should not be limited to just the DNS configuration options. I will revise this draft in response to the comments about future extensibility to include other options. The WG should discuss Jinmei-san's other issues before the draft is submitted to the IESG. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 12:20:02 2003 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 MAA20430 for ; Thu, 1 May 2003 12:20:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41GQ8506925 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 12:26:08 -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 h41GQ8806922 for ; Thu, 1 May 2003 12:26: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 MAA20379 for ; Thu, 1 May 2003 12:19:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BGoT-0003UP-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 12:21:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BGoS-0003UM-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 12:21:36 -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 h41GOB806674; Thu, 1 May 2003 12:24:11 -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 h41GCR803786 for ; Thu, 1 May 2003 12:12:27 -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 MAA19650 for ; Thu, 1 May 2003 12:05:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BGbJ-0003K9-00 for dhcwg@ietf.org; Thu, 01 May 2003 12:08:01 -0400 Received: from imr2.ericy.com ([198.24.6.3]) by ietf-mx with esmtp (Exim 4.12) id 19BGbD-0003Ih-00 for dhcwg@ietf.org; Thu, 01 May 2003 12:07:56 -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 h41G7LnZ027852; Thu, 1 May 2003 11:07:21 -0500 (CDT) Received: from eamrcnt760.exu.ericsson.se (eamrcnt760.exu.ericsson.se [138.85.133.38]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h41G7LOV012211; Thu, 1 May 2003 11:07:21 -0500 (CDT) Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id ; Thu, 1 May 2003 11:07:21 -0500 Message-ID: From: "Bernie Volz (EUD)" To: "'Ralph Droms'" , dhcwg@ietf.org Subject: RE: [dhcwg] Results of recent WG last calls Date: Thu, 1 May 2003 11:05:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C30FFB.31293D20" 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: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C30FFB.31293D20 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C30FFB.31293D20" ------_=_NextPart_001_01C30FFB.31293D20 Content-Type: text/plain; charset="ISO-8859-1" Ralph: I support draft-ietf-dhc-dhcpv6-interop-01.txt as I indicated to you in a private email to get an understanding on one issue before posting public support. Don't know if this changes the outcome of the Last-Call, but as I don't think you ever responded to the issue, I forgot to submit my public support. - Bernie -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Thursday, May 01, 2003 9:40 AM To: dhcwg@ietf.org Subject: [dhcwg] Results of recent WG last calls Here are the results of some recent last WG last calls: draft-ietf-dhc-suboptions-kdc-serveraddress-03.txt See http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg01968.html for a comment. No other comments about this draft were received during the last call. This draft did not receive enough positive support to be submitted to the IESG. ===== draft-ietf-dhc-dhcpv6-loadb-02.txt No comments about this document were received during the last call. This draft did not receive enough positive support to be submitted to the IESG. ===== draft-ietf-dhc-dhcpv6-interop-01.txt Jinmei-san responded that this draft is ready for submission to the IESG. No other comments about this draft were received during the last call. Although this draft only received one comment during WG last call, it is important to move the draft forward because it should be published before the DHCPv6 specification is published as an RFC. Also, this draft will be published as Informational, rather than as an Internet Standard. Therefore, I will submit the draft to the IESG. ===== draft-ietf-dhc-dhcpv6-stateless-00.txt Jinmei-san posted a comment about the draft that started a discussion thread on the mailing list (see http://www1.ietf.org/mail-archive/working-groups/dhcwg/current/msg01999.html) There were several comments suggesting that stateless DHCPv6 should not be limited to just the DNS configuration options. I will revise this draft in response to the comments about future extensibility to include other options. The WG should discuss Jinmei-san's other issues before the draft is submitted to the IESG. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C30FFB.31293D20 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] Results of recent WG last calls

Ralph:

I support draft-ietf-dhc-dhcpv6-interop-01.txt as I = indicated to you in a private
email to get an understanding on one issue before = posting public support. Don't know
if this changes the outcome of the Last-Call, but as = I don't think you ever responded
to the issue, I forgot to submit my public = support.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Thursday, May 01, 2003 9:40 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Results of recent WG last = calls


Here are the results of some recent last WG last = calls:

draft-ietf-dhc-suboptions-kdc-serveraddress-03.txt

  See
  http://www1.ietf.org/mail-archive/working-groups/dhcwg= /current/msg01968.html
  for a comment.  No other comments about = this draft
  were received during the last call.

  This draft did not receive enough positive = support
  to be submitted to the IESG.
=3D=3D=3D=3D=3D

draft-ietf-dhc-dhcpv6-loadb-02.txt

  No comments about this document were received = during the last call.

  This draft did not receive enough positive = support
  to be submitted to the IESG.
=3D=3D=3D=3D=3D

draft-ietf-dhc-dhcpv6-interop-01.txt

  Jinmei-san responded that this draft is ready = for submission
  to the IESG.  No other comments about = this draft
  were received during the last call.

  Although this draft only received one comment = during WG
  last call, it is important to move the draft = forward because
  it should be published before the DHCPv6 = specification is
  published as an RFC.  Also, this draft = will be published
  as Informational, rather than as an Internet = Standard.
  Therefore, I will submit the draft to the = IESG.
=3D=3D=3D=3D=3D

draft-ietf-dhc-dhcpv6-stateless-00.txt

  Jinmei-san posted a comment about the draft = that started
  a discussion thread on the mailing list (see = http://www1.ietf.org/mail-archive/working-groups/dhcwg= /current/msg01999.html)

  There were several comments suggesting that = stateless DHCPv6
  should not be limited to just the DNS = configuration
  options.

  I will revise this draft in response to the = comments about
  future extensibility to include other = options.  The WG
  should discuss Jinmei-san's other issues = before the draft
  is submitted to the IESG.

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

  ------_=_NextPart_001_01C30FFB.31293D20-- ------_=_NextPart_000_01C30FFB.31293D20 Content-Type: message/rfc822 Content-Description: RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-interop-01.txt Message-ID: From: "Bernie Volz (EUD)" To: 'Ralph Droms' Subject: RE: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-interop-01.txt Date: Sun, 13 Apr 2003 22:54:58 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_003_01C30FFB.31293D20" ------_=_NextPart_003_01C30FFB.31293D20 Content-Type: text/plain; charset="ISO-8859-1" Ralph: (I did not CC the DHC WG Mailing List.) For issue 1, what happened to the concept of making this similar to a CONFIRM and sending a Not-on-Link? Note that the Reply with IAs with 0 for lifetimes is a rather strong statement for the client to stop using the addresses. Practically, I'm not sure sending a Not-On-Link would be that different. Other than this issue (where it would be good to know that it was considered and rejected), I will support the document. - Bernie -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Friday, April 11, 2003 11:19 AM To: dhcwg@ietf.org Subject: [dhcwg] WG last call on draft-ietf-dhc-dhcpv6-interop-01.txt This message announces a WG last call on "Results from Interoperability Tests of DHCPv6 Implementations" . The last call will conclude on Friday, April 25. Please respond to this WG last call. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. draft-ietf-dhc-dhcpv6-interop-01.txt provides a published record of issues discovered through interoperability testing of independent implementations of DHCPv6 , for review and discussion by the appropriate IETF working groups. This document is being considered for Informational status, and is available as http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-interop-01.txt - Ralph Droms _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_003_01C30FFB.31293D20 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] WG last call on = draft-ietf-dhc-dhcpv6-interop-01.txt

Ralph:

(I did not CC the DHC WG Mailing List.)

For issue 1, what happened to the concept of making = this similar to a
CONFIRM and sending a Not-on-Link? Note that the = Reply with IAs with 0
for lifetimes is a rather strong statement for the = client to stop using
the addresses. Practically, I'm not sure sending a = Not-On-Link would be
that different.

Other than this issue (where it would be good to know = that it was
considered and rejected), I will support the = document.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Friday, April 11, 2003 11:19 AM
To: dhcwg@ietf.org
Subject: [dhcwg] WG last call on = draft-ietf-dhc-dhcpv6-interop-01.txt


This message announces a WG last call on = "Results from
Interoperability Tests of DHCPv6 = Implementations"
<draft-ietf-dhc-dhcpv6-interop-01.txt>.  = The last call will conclude
on Friday, April 25.

Please respond to this WG last call.  If you = support acceptance of the
document without change, respond with a simple = acknowledgment, so that
support for the document can be assessed.

draft-ietf-dhc-dhcpv6-interop-01.txt provides a = published record of
issues discovered through interoperability testing = of independent
implementations of DHCPv6 = <draft-ietf-dhc-dhcpv6-28.txt>, for review
and discussion by the appropriate IETF working = groups.  This document
is being considered for Informational status, and is = available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhc= pv6-interop-01.txt

- Ralph Droms

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

------_=_NextPart_003_01C30FFB.31293D20-- ------_=_NextPart_000_01C30FFB.31293D20-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 15:27:09 2003 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 PAA02856 for ; Thu, 1 May 2003 15:27:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41JXKF18870 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 15:33:20 -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 h41JXK818867 for ; Thu, 1 May 2003 15:33:20 -0400 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 PAA02821 for ; Thu, 1 May 2003 15:26:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41JVE818193; Thu, 1 May 2003 15:31:14 -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 h41JPW816652 for ; Thu, 1 May 2003 15:25: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 PAA01910 for ; Thu, 1 May 2003 15:18:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJc6-0005Yr-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:21:02 -0400 Received: from ip26.coe.tnet.co.th ([203.146.155.26] helo=fuchsia.home) by ietf-mx with esmtp (Exim 4.12) id 19BJbz-0005Xz-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:20:56 -0400 Received: from delta.cs.mu.OZ.AU (delta.ex0.home [192.168.192.22]) by fuchsia.home with ESMTP id h41JIohX003528; Fri, 2 May 2003 02:18:51 +0700 (ICT) Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h41JH9J20091; Fri, 2 May 2003 02:17:11 +0700 (ICT) From: Robert Elz To: Ralph Droms cc: dhcwg@ietf.org Subject: Re: [dhcwg] Address selection for Information-request/Reply messages In-Reply-To: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> References: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> <4.3.2.7.2.20030411113053.042c1cb0@funnel.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 May 2003 02:17:09 +0700 Message-ID: <20089.1051816629@munnari.OZ.AU> 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: , List-Id: List-Post: List-Help: List-Subscribe: , Date: Thu, 01 May 2003 09:52:19 -0400 From: Ralph Droms Message-ID: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> | Infact, it would be important to note that a site MUST NOT both | implement multicast and configure relay agents to listen on | All_DHCP_Servers, as such a configuration would result in the | servers receiving multiple copies of client messages. Surely that happens with relay agents anyway? Any site with half a brain, or more, configures multiple relay agents for redundancy (assuming it also has multiple routers for redundancy of course). If the protocol can't handle multiple copies of messages being delivered to the servers, it badly needs fixing (but I actually doubt it has that defect). kre _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 16:06:04 2003 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 QAA06464 for ; Thu, 1 May 2003 16:06:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41KCEd32275 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 16:12:14 -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 h41KCE832271 for ; Thu, 1 May 2003 16:12:14 -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 QAA06394 for ; Thu, 1 May 2003 16:05:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BKLH-00062u-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 16:07:43 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BKLG-00062p-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 16:07:42 -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 h41K6o829885; Thu, 1 May 2003 16:06:50 -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 h41K0Z828312 for ; Thu, 1 May 2003 16:00:35 -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 PAA05269 for ; Thu, 1 May 2003 15:53:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BKA0-0005w4-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:56:04 -0400 Received: from imr1.ericy.com ([208.237.135.240]) by ietf-mx with esmtp (Exim 4.12) id 19BK9u-0005u3-00 for dhcwg@ietf.org; Thu, 01 May 2003 15:55:59 -0400 Received: from mr5.exu.ericsson.se (mr5u3.ericy.com [208.237.135.124]) by imr1.ericy.com (8.12.9/8.12.9) with ESMTP id h41Jqrat005272; Thu, 1 May 2003 14:52:53 -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 h41JqrNe011136; Thu, 1 May 2003 14:52:53 -0500 (CDT) Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id ; Thu, 1 May 2003 14:52:52 -0500 Message-ID: From: "Bernie Volz (EUD)" To: "'Robert Elz'" , Ralph Droms Cc: dhcwg@ietf.org Subject: RE: [dhcwg] Address selection for Information-request/Reply messa ges Date: Thu, 1 May 2003 14:50:51 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3101A.65602620" 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: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3101A.65602620 Content-Type: text/plain; charset="iso-8859-1" The problem comes about if we change All_DHCP_Servers to include relays to listen for messages on this address. Because now both the relays and the routers would forward messages, and the relays may forward messages forwarded by routers, you could (depending on the number of relays and routers), get a fairly large packet storm. The DHCPv6 protocol will work fine and doesn't break. Though the load placed on the servers and network may not be desireable. That is the point. Bottom line, IMHO, this is a bad idea. We shouldn't have relays listening for All_DHCP_Servers traffic. And, if we don't do that, allowing Information-Request sent directly to All_DHCP_Servers would require site multicast to work and if it doesn't or is disabled, these clients would fail to receive the requested information if the server isn't local. - Bernie -----Original Message----- From: Robert Elz [mailto:kre@munnari.oz.au] Sent: Thursday, May 01, 2003 3:17 PM To: Ralph Droms Cc: dhcwg@ietf.org Subject: Re: [dhcwg] Address selection for Information-request/Reply messages Date: Thu, 01 May 2003 09:52:19 -0400 From: Ralph Droms Message-ID: <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com> | Infact, it would be important to note that a site MUST NOT both | implement multicast and configure relay agents to listen on | All_DHCP_Servers, as such a configuration would result in the | servers receiving multiple copies of client messages. Surely that happens with relay agents anyway? Any site with half a brain, or more, configures multiple relay agents for redundancy (assuming it also has multiple routers for redundancy of course). If the protocol can't handle multiple copies of messages being delivered to the servers, it badly needs fixing (but I actually doubt it has that defect). kre _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C3101A.65602620 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] Address selection for Information-request/Reply = messages

The problem comes about if we change All_DHCP_Servers = to include relays to
listen for messages on this address.

Because now both the relays and the routers would = forward messages, and the
relays may forward messages forwarded by routers, = you could (depending on
the number of relays and routers), get a fairly = large packet storm.

The DHCPv6 protocol will work fine and doesn't break. = Though the load placed
on the servers and network may not be desireable. = That is the point.

Bottom line, IMHO, this is a bad idea. We shouldn't = have relays listening
for All_DHCP_Servers traffic. And, if we don't do = that, allowing Information-Request
sent directly to All_DHCP_Servers would require site = multicast to work and if
it doesn't or is disabled, these clients would fail = to receive the requested
information if the server isn't local.

- Bernie

-----Original Message-----
From: Robert Elz [mailto:kre@munnari.oz.au]
Sent: Thursday, May 01, 2003 3:17 PM
To: Ralph Droms
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Address selection for = Information-request/Reply
messages


    = Date:        Thu, 01 May 2003 = 09:52:19 -0400
    = From:        Ralph Droms = <rdroms@cisco.com>
    Message-ID:  = <4.3.2.7.2.20030501094136.00b8f828@funnel.cisco.com>

  | Infact, it would be important to note that a = site MUST NOT both
  | implement multicast and configure relay = agents to listen on
  | All_DHCP_Servers, as such a configuration = would result in the
  | servers receiving multiple copies of client = messages.

Surely that happens with relay agents = anyway?   Any site with half a brain,
or more, configures multiple relay agents for = redundancy (assuming it also
has multiple routers for redundancy of = course).   If the protocol can't
handle multiple copies of messages being delivered = to the servers, it badly
needs fixing (but I actually doubt it has that = defect).

kre

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

------_=_NextPart_001_01C3101A.65602620-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 22:15:47 2003 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 WAA22135 for ; Thu, 1 May 2003 22:15:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h422M4929889 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 22:22:04 -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 h422M4829886 for ; Thu, 1 May 2003 22:22: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 WAA22132 for ; Thu, 1 May 2003 22:15:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BQ74-0001JM-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 22:17:26 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BQ73-0001JJ-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 22:17:25 -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 h422KY829797; Thu, 1 May 2003 22:20:34 -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 h422HM829678 for ; Thu, 1 May 2003 22:17:22 -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 WAA21969 for ; Thu, 1 May 2003 22:10:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BQ2H-0001H7-00 for dhcwg@ietf.org; Thu, 01 May 2003 22:12:29 -0400 Received: from fep03-mail.bloor.is.net.cable.rogers.com ([66.185.86.73]) by ietf-mx with esmtp (Exim 4.12) id 19BQ2B-0001Gv-00 for dhcwg@ietf.org; Thu, 01 May 2003 22:12:23 -0400 Received: from arthur ([65.50.135.44]) by fep03-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20030502021240.OXDJ6654.fep03-mail.bloor.is.net.cable.rogers.com@arthur> for ; Thu, 1 May 2003 22:12:40 -0400 Message-ID: <001901c31050$50c5e340$2c873241@arthur> From: "Artybuck" To: Date: Thu, 1 May 2003 22:12:42 -0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0015_01C3102E.C9326910" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep03-mail.bloor.is.net.cable.rogers.com from [65.50.135.44] using ID at Thu, 1 May 2003 22:12:29 -0400 Subject: [dhcwg] Remove 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: , List-Id: List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C3102E.C9326910 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0016_01C3102E.C9326910" ------=_NextPart_001_0016_01C3102E.C9326910 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_001_0016_01C3102E.C9326910 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_001_0016_01C3102E.C9326910-- ------=_NextPart_000_0015_01C3102E.C9326910 Content-Type: text/x-vcard; name="Jump On The Buck Wagon.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="Jump On The Buck Wagon.vcf" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit BEGIN:VCARD VERSION:2.1 N:;Jump On The Buck Wagon FN:Jump On The Buck Wagon EMAIL;PREF;INTERNET:artybuck@rogers.com REV:20030502T021242Z END:VCARD ------=_NextPart_000_0015_01C3102E.C9326910-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 1 22:47:15 2003 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 WAA22793 for ; Thu, 1 May 2003 22:47:15 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h422rYp31985 for dhcwg-archive@odin.ietf.org; Thu, 1 May 2003 22:53:34 -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 h422rY831982 for ; Thu, 1 May 2003 22:53:34 -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 WAA22783 for ; Thu, 1 May 2003 22:46:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BQbW-0001T0-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 22:48:54 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BQbW-0001Sx-00 for dhcwg-web-archive@ietf.org; Thu, 01 May 2003 22:48:54 -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 h422pv831888; Thu, 1 May 2003 22:51:58 -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 h422nA831784 for ; Thu, 1 May 2003 22:49:10 -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 WAA22655 for ; Thu, 1 May 2003 22:42:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BQX2-0001RX-00 for dhcwg@ietf.org; Thu, 01 May 2003 22:44:16 -0400 Received: from imr2.ericy.com ([198.24.6.3]) by ietf-mx with esmtp (Exim 4.12) id 19BQWw-0001Qr-00 for dhcwg@ietf.org; Thu, 01 May 2003 22:44:10 -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 h41G3pnZ026949; Thu, 1 May 2003 11:03:51 -0500 (CDT) Received: from eamrcnt760.exu.ericsson.se (eamrcnt760.exu.ericsson.se [138.85.133.38]) by mr5.exu.ericsson.se (8.12.9/8.12.9) with ESMTP id h41G3pOV011279; Thu, 1 May 2003 11:03:51 -0500 (CDT) Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id ; Thu, 1 May 2003 11:03:51 -0500 Message-ID: From: "Bernie Volz (EUD)" To: "'Ralph Droms'" , dhcwg@ietf.org Subject: RE: [dhcwg] Address selection for Information-request/Reply messa ges Date: Thu, 1 May 2003 11:01:48 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C30FFA.F8BB7502" 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: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C30FFA.F8BB7502 Content-Type: text/plain; charset="ISO-8859-1" Personally, I would prefer we leave this as it is. I think there is too great a danger for problems with allowing this because of the risk of misconfiguration. Also, if you allow this for Information-Request, why not allow it also in cases where a client has obtained some addresses from stateless and is using stateful for others. - Bernie -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Thursday, May 01, 2003 9:52 AM To: dhcwg@ietf.org Subject: [dhcwg] Address selection for Information-request/Reply messages At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote: >1. address selection of Information-request/Reply exchanges > >According to the DHCPv6 base spec, the client should send Information >Request messages to the All_DHCP_Relay_Agents_and_Servers multicast >address (FF02::1:2). However, doesn't it make much sense to allow the >client to send the requests to the All_DHCP_Servers multicast address >FF05::1:3? Since the stateless usage assumes the client has obtained >its IPv6 addresses through some other mechanism, I don't see a reason >that the client cannot do so. If we allow this, the client can access >an off-link server without relying on a relay agent, which would help >the deployment. On the other hand, we don't want to require deployment of multicast to enable stateless DHCPv6. One possibility would be to allow the use of All_DHCP_Servers, with an explicit warning that a site that doesn't implement multicast MUST use relay agents AND the relay agents must listen to All_DHCP_Servers (which is a change from the current spec). In fact, it would be important to note that a site MUST NOT both implement multicast and configure relay agents to listen on All_DHCP_Servers, as such a configuration would result in the servers receiving multiple copies of client messages. - Ralph _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C30FFA.F8BB7502 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] Address selection for Information-request/Reply = messages

Personally, I would prefer we leave this as it is. I = think there is too great
a danger for problems with allowing this because of = the risk of misconfiguration.
Also, if you allow this for Information-Request, why = not allow it also in cases
where a client has obtained some addresses from = stateless and is using stateful
for others.

- Bernie

-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Thursday, May 01, 2003 9:52 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Address selection for = Information-request/Reply
messages


At 12:10 AM 4/15/2003 +0900, JINMEI Tatuya / = =3D?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=3D?=3D wrote:

>1. address selection of Information-request/Reply = exchanges
>
>According to the DHCPv6 base spec, the client = should send Information
>Request messages to the = All_DHCP_Relay_Agents_and_Servers multicast
>address (FF02::1:2).  However, doesn't it = make much sense to allow the
>client to send the requests to the = All_DHCP_Servers multicast address
>FF05::1:3?  Since the stateless usage = assumes the client has obtained
>its IPv6 addresses through some other mechanism, = I don't see a reason
>that the client cannot do so.  If we allow = this, the client can access
>an off-link server without relying on a relay = agent, which would help
>the deployment.

On the other hand, we don't want to require = deployment of multicast
to enable stateless DHCPv6.

One possibility would be to allow the use of = All_DHCP_Servers, with
an explicit warning that a site that doesn't = implement multicast
MUST use relay agents AND the relay agents must = listen to
All_DHCP_Servers (which is a change from the current = spec).  In
fact, it would be important to note that a site MUST = NOT both
implement multicast and configure relay agents to = listen on
All_DHCP_Servers, as such a configuration would = result in the
servers receiving multiple copies of client = messages.

- Ralph



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

------_=_NextPart_001_01C30FFA.F8BB7502-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Fri May 2 11:21:07 2003 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 LAA17730 for ; Fri, 2 May 2003 11:21:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42FRfe30403 for dhcwg-archive@odin.ietf.org; Fri, 2 May 2003 11:27:41 -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 h42FRe830400 for ; Fri, 2 May 2003 11:27:40 -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 LAA17701 for ; Fri, 2 May 2003 11:20:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BcMq-0004wV-00 for dhcwg-web-archive@ietf.org; Fri, 02 May 2003 11:22:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BcMp-0004wQ-00 for dhcwg-web-archive@ietf.org; Fri, 02 May 2003 11:22:31 -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 h42FMY830132; Fri, 2 May 2003 11:22:34 -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 h42FIQ829919 for ; Fri, 2 May 2003 11:18:26 -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 LAA17497 for ; Fri, 2 May 2003 11:11:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BcDs-0004t0-00 for dhcwg@ietf.org; Fri, 02 May 2003 11:13:16 -0400 Received: from igor.alcpress.com ([208.151.249.202]) by ietf-mx with esmtp (Exim 4.12) id 19BcDn-0004sd-00 for dhcwg@ietf.org; Fri, 02 May 2003 11:13:11 -0400 Received: from db.panug.org (db.panug.org [208.151.249.203]) by igor.alcpress.com (Postfix) with ESMTP id A0A5F1B18E2 for ; Fri, 2 May 2003 08:11:43 -0700 (PDT) From: Ed Sawicki To: dhcwg@ietf.org Content-Type: text/plain Organization: ALC Message-Id: <1051888376.1161.63.camel@red> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 02 May 2003 08:12:56 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [dhcwg] Option 33 - static routes 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I'm wondering whether I understand DHCP option 33 correctly. If I configure ISC's DHCP server so that network 192.168.0.0 is to have a static route of 192.168.0.1, for example, a DHCP client then has this network in it's routing table: 192.168.0.0 255.255.255.255 instead of this: 192.168.0.0 255.255.255.0 Is this proper operation? -- Ed Sawicki ALC _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Fri May 2 18:47:31 2003 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 SAA06135 for ; Fri, 2 May 2003 18:47:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h42MsF303180 for dhcwg-archive@odin.ietf.org; Fri, 2 May 2003 18:54:15 -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 h42MsE803177 for ; Fri, 2 May 2003 18:54:14 -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 SAA06128 for ; Fri, 2 May 2003 18:47:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BjL4-0000iM-00 for dhcwg-web-archive@ietf.org; Fri, 02 May 2003 18:49:10 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BjL3-0000iI-00 for dhcwg-web-archive@ietf.org; Fri, 02 May 2003 18:49:09 -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 h42MkK802902; Fri, 2 May 2003 18:46:21 -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 h42Mft802667 for ; Fri, 2 May 2003 18:41:55 -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 SAA05838 for ; Fri, 2 May 2003 18:33:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Bj85-0000eR-00 for dhcwg@ietf.org; Fri, 02 May 2003 18:35:45 -0400 Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx with esmtp (Exim 4.12) id 19Bj7z-0000e2-00 for dhcwg@ietf.org; Fri, 02 May 2003 18:35:40 -0400 Date: Fri, 02 May 2003 15:36:40 -0700 From: Alper Yegin To: , pana Message-ID: In-Reply-To: <4.3.2.7.2.20030404054730.042dc4c0@funnel.cisco.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [dhcwg] Bootstraping RFC3118 using PANA 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, [sorry about possible duplicates as this message is cross-posted on two mailing lists..] Assuming the major (or, one of the) problem of RFC3118 is lack of roaming and bootstraping support, we thought PANA could be useful here. http://ietf.org/html.charters/pana-charter.html One idea is to use PANA prior to DHCP to bootstrap a trust relation between the host and the network. Note that PANA can be used even when the host does not have an IP address. Client and network can use any authentication method to authenticate each other. Assuming they use one that generates keying material, this would result in a newly generated trust relation (i.e., PANA SA) between the host and an access network entity (PANA authentication agent - PAA). This would be a by-product of "network access authentication." PANA SA can be used to derive a DHCP SA to be used with RFC3118. This can be accomplished by a mutually-agreed PRF. In its simplest form, DHCP server/agent/proxy can be co-located with PAA, hence keying material is internally made available to DHCP module. This way, RFC3118 can be used as is (unless there are some other problems with it..) Comments? Alper _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Mon May 5 18:38:14 2003 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 SAA20223 for ; Mon, 5 May 2003 18:38:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45MkQZ10538 for dhcwg-archive@odin.ietf.org; Mon, 5 May 2003 18:46:26 -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 h45MkP810535 for ; Mon, 5 May 2003 18:46:25 -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 SAA20199 for ; Mon, 5 May 2003 18:37:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cocf-0001Wk-00 for dhcwg-web-archive@ietf.org; Mon, 05 May 2003 18:39:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cocf-0001Wg-00 for dhcwg-web-archive@ietf.org; Mon, 05 May 2003 18:39:49 -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 h45Mf9810208; Mon, 5 May 2003 18:41:09 -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 h45MT6808618 for ; Mon, 5 May 2003 18:29:06 -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 SAA18932 for ; Mon, 5 May 2003 18:20:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoLf-0001Ni-00 for dhcwg@ietf.org; Mon, 05 May 2003 18:22:15 -0400 Received: from smtp013.mail.yahoo.com ([216.136.173.57]) by ietf-mx with smtp (Exim 4.12) id 19CoKq-0001NC-00 for dhcwg@ietf.org; Mon, 05 May 2003 18:21:24 -0400 Received: from adsl-64-169-89-159.dsl.snfc21.pacbell.net (HELO BarrH63p601) (rbhibbs@pacbell.net@64.169.89.159 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 5 May 2003 22:20:28 -0000 Reply-To: From: "Barr Hibbs" To: Subject: RE: [dhcwg] WG last call on draft-ietf-dhc-unused-optioncodes-02 Date: Mon, 5 May 2003 15:10:25 -0700 Message-ID: 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 IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <4.3.2.7.2.20030430110023.03f6c840@funnel.cisco.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 7bit 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I've reviewed the draft and concur with its proposals. --Barr Hibbs > -----Original Message----- > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of > Ralph Droms > Sent: Wednesday, April 30, 2003 08:04 > To: dhcwg@ietf.org > Subject: [dhcwg] WG last call on draft-ietf-dhc-unused-optioncodes-02 > > > This message announces a WG last call on "Unused DHCP Option > Codes" . The last call > will conclude on Friday, May 16. > > Please respond to this WG last call. If you support acceptance of the > document without change, respond with a simple acknowledgment, so that > support for the document can be assessed. > > Prior to the publication of RFC2489 (which was updated by RFC2939), > several option codes were assigned to proposed DHCP options that > were subsequently never used. This document lists those unused > option codes and will be used to confirm that these option codes > can be reused for other DHCP options in the future. This document > is being considered for publication as Informational, and is available as > http://www.ietf.org/internet-drafts/draft-ietf-dhc-unused-optionco des-02.txt - 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 From mailnull@www1.ietf.org Tue May 6 03:45:28 2003 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 DAA10931 for ; Tue, 6 May 2003 03:45:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h467ros24539 for dhcwg-archive@odin.ietf.org; Tue, 6 May 2003 03:53:50 -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 h467rn824536 for ; Tue, 6 May 2003 03:53:49 -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 DAA10903 for ; Tue, 6 May 2003 03:44:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CxAE-00044K-00 for dhcwg-web-archive@ietf.org; Tue, 06 May 2003 03:47:02 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CxAD-00044B-00 for dhcwg-web-archive@ietf.org; Tue, 06 May 2003 03:47:01 -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 h467lJ824060; Tue, 6 May 2003 03:47:19 -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 h467b5822811 for ; Tue, 6 May 2003 03:37:05 -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 DAA10471 for ; Tue, 6 May 2003 03:27:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cwtn-0003wl-00 for dhcwg@ietf.org; Tue, 06 May 2003 03:30:03 -0400 Received: from tokyo.ccrle.nec.de ([195.37.70.2]) by ietf-mx with esmtp (Exim 4.12) id 19Cwth-0003wE-00 for dhcwg@ietf.org; Tue, 06 May 2003 03:29:57 -0400 Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.9/8.12.8) with ESMTP id h467ThVI072535 for ; Tue, 6 May 2003 09:29:43 +0200 (CEST) Received: from ccrle.nec.de (n-stiemerling.office [10.1.1.109]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id E5D7FA2488 for ; Tue, 6 May 2003 09:22:20 +0200 (CEST) Message-ID: <3EB76468.8050205@ccrle.nec.de> Date: Tue, 06 May 2003 09:29:44 +0200 From: Martin Stiemerling Organization: NEC -- Network Labs Europe User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc3) Gecko/20020619 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dhcwg@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [dhcwg] DHCPv6 Interop tests at IETF 57 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, somebody here interested in some interop tests of DHCPv6 at the upcoming IETF-75 in Vienna? We are interested in doing interoperability testing between different DHCPv6 clients and servers. Cheers Martin -- Martin Stiemerling NEC Europe Ltd. -- Network Laboratories Stiemerling@ccrle.nec.de IPv4: http://www.ccrle.nec.de IPv6: http://www.ipv6.ccrle.nec.de _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Tue May 6 18:09:44 2003 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 SAA11453 for ; Tue, 6 May 2003 18:09:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46MIOY02438 for dhcwg-archive@odin.ietf.org; Tue, 6 May 2003 18:18:24 -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 h46MIO802435 for ; Tue, 6 May 2003 18:18:24 -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 SAA11381 for ; Tue, 6 May 2003 18:09:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DAec-0002xV-00 for dhcwg-web-archive@ietf.org; Tue, 06 May 2003 18:11:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DAeb-0002xS-00 for dhcwg-web-archive@ietf.org; Tue, 06 May 2003 18:11:17 -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 h46MDa802222; Tue, 6 May 2003 18:13:36 -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 h46MAY802119 for ; Tue, 6 May 2003 18:10:34 -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 SAA10613 for ; Tue, 6 May 2003 18:01:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DAX3-0002vE-00 for dhcwg@ietf.org; Tue, 06 May 2003 18:03:29 -0400 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by ietf-mx with esmtp (Exim 4.12) id 19DAX2-0002v9-00 for dhcwg@ietf.org; Tue, 06 May 2003 18:03:28 -0400 Received: from jschnizl-w2k.cisco.com (rtp-vpn2-525.cisco.com [10.82.242.13]) by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h46M3mmb028944; Tue, 6 May 2003 18:03:48 -0400 (EDT) Message-Id: <4.3.2.7.2.20030506172239.02212aa0@wells.cisco.com> X-Sender: jschnizl@wells.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 06 May 2003 18:03:44 -0400 To: Michael Richardson From: John Schnizlein Subject: Re: [dhcwg] DHCP over IKE Cc: dhcwg@ietf.org In-Reply-To: <200304281751.h3SHpqbn006061@marajade.sandelman.ottawa.on.c a> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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: , List-Id: List-Post: List-Help: List-Subscribe: , I see nothing in these drafts to indicate that the proposal accommodates DHCP relay agents in any way. In particular, tunneling DHCP within IKE messages would seem to disable this. Since RFC 3456 does not seem to have the same problem, it seems better to me. John At 01:51 PM 4/28/2003, Michael Richardson wrote: >A number of documents are being proposed in the IPSEC WG. The IPSRA >WG produced a protocol that runs DHCP over an IPsec tunnel, RFC 3456. >Other vendors used a protocol called "Configuration Payload" > >There is a third option being discussed, called "DHCP-over-IKE". > >The documents are draft-ietf-ipsec-dhcp-over-ike-00, as well >as dhcp-over-ike-dhcpd-00.txt and dhcp-over-ike-radius-00.txt > >A discussion thread: >http://www.sandelman.ottawa.on.ca/ipsec/2003/04/msg00053.html _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Wed May 7 07:22:01 2003 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 HAA23982 for ; Wed, 7 May 2003 07:22:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47BUvs05378 for dhcwg-archive@odin.ietf.org; Wed, 7 May 2003 07:30:57 -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 h47BUv805375 for ; Wed, 7 May 2003 07:30:57 -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 HAA23978 for ; Wed, 7 May 2003 07:21:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DN1L-0007La-00 for dhcwg-web-archive@ietf.org; Wed, 07 May 2003 07:23:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DN1K-0007LW-00 for dhcwg-web-archive@ietf.org; Wed, 07 May 2003 07:23: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 h47BQR805190; Wed, 7 May 2003 07:26:27 -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 h47BNS805041 for ; Wed, 7 May 2003 07:23:28 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23565; Wed, 7 May 2003 07:14:01 -0400 (EDT) Message-Id: <200305071114.HAA23565@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: dhcwg@ietf.org, ips@ece.cmu.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Wed, 07 May 2003 07:14:00 -0400 Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-isnsoption-06.txt,.pdf 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: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : The IPv4 DHCP Options for the Internet Storage Name Service Author(s) : C. Monia, J. Tseng, K. Gibbons Filename : draft-ietf-dhc-isnsoption-06.txt,.pdf Pages : 13 Date : 2003-5-6 This document describes the DHCP option to allow Internet Storage Name Service (iSNS) clients to automatically discover the location of the iSNS server through the use of DHCP for IPv4. iSNS provides discovery and management capabilities for Internet SCSI (iSCSI) and Internet Fibre Channel Protocol (iFCP) storage devices in an enterprise-scale IP storage network. iSNS provides intelligent storage management services comparable to those found in Fibre Channel networks, allowing a commodity IP network to function in a similar capacity as a storage area network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-isnsoption-06.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-dhc-isnsoption-06.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-dhc-isnsoption-06.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-6153220.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-isnsoption-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-isnsoption-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-6153220.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Thu May 8 17:03:34 2003 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 RAA11196 for ; Thu, 8 May 2003 17:03:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48LDCu20263 for dhcwg-archive@odin.ietf.org; Thu, 8 May 2003 17:13:12 -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 h48LDB820257 for ; Thu, 8 May 2003 17:13:11 -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 RAA11161 for ; Thu, 8 May 2003 17:03:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DsZe-0006a5-00 for dhcwg-web-archive@ietf.org; Thu, 08 May 2003 17:05:06 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DsZd-0006a0-00 for dhcwg-web-archive@ietf.org; Thu, 08 May 2003 17:05:05 -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 h48L6i818855; Thu, 8 May 2003 17:06:44 -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 h48L1F818322 for ; Thu, 8 May 2003 17:01:15 -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 QAA10587 for ; Thu, 8 May 2003 16:51:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DsO6-0006St-00 for dhcwg@ietf.org; Thu, 08 May 2003 16:53:10 -0400 Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx with esmtp (Exim 4.12) id 19DsO5-0006SL-00 for dhcwg@ietf.org; Thu, 08 May 2003 16:53:09 -0400 Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h48Kr7V25409; Thu, 8 May 2003 15:53:08 -0500 (CDT) Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 8 May 2003 15:53:08 -0500 Message-ID: <1B54FA3A2709D51195C800508BF9386A080B38AD@zrc2c000.us.nortel.com> From: "Peter Barany" To: "'juha.wiljakka@nokia.com'" , rdroms@cisco.com Cc: dhcwg@ietf.org Subject: RE: [dhcwg] Stateless DHCPv6 service Date: Thu, 8 May 2003 15:53:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C315A3.D25A1A5E" 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: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C315A3.D25A1A5E Content-Type: text/plain; charset="iso-8859-1" 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] 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 Best Regards, -Juha W.- -----Original Message----- From: ext Ralph Droms [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 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C315A3.D25A1A5E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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]
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-dhc= pv6-01.txt

Best Regards,
                  -Juha = W.-

-----Original Message-----
From: ext Ralph Droms [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
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

------_=_NextPart_001_01C315A3.D25A1A5E-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Sun May 11 22:48:13 2003 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 WAA17819 for ; Sun, 11 May 2003 22:48:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C2DXk04385 for dhcwg-archive@odin.ietf.org; Sun, 11 May 2003 22:13:33 -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 h4C2DWB04382 for ; Sun, 11 May 2003 22:13:33 -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 WAA17808 for ; Sun, 11 May 2003 22:47:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F3Nl-0004AH-00 for dhcwg-web-archive@ietf.org; Sun, 11 May 2003 22:49:41 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F3Nl-0004AD-00 for dhcwg-web-archive@ietf.org; Sun, 11 May 2003 22:49:41 -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 h4C2BvB04335; Sun, 11 May 2003 22:11:57 -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 h4C28eB04256 for ; Sun, 11 May 2003 22:08:40 -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 WAA17738 for ; Sun, 11 May 2003 22:42:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F3J3-00049L-00 for dhcwg@ietf.org; Sun, 11 May 2003 22:44:49 -0400 Received: from coral.tci.com ([198.178.8.81] helo=peacock.tci.com) by ietf-mx with esmtp (Exim 4.12) id 19F3J2-00049E-00 for dhcwg@ietf.org; Sun, 11 May 2003 22:44:48 -0400 Received: from mms01-relayb.tci.com (mms01-relayb.broadband.att.com [147.191.90.1]) by peacock.tci.com (8.12.9/8.12.9) with ESMTP id h4C2jDPa018111; Sun, 11 May 2003 20:45:13 -0600 (MDT) Received: from 147.191.90.10 by mms01-relayb.tci.com with ESMTP ( Tumbleweed MMS SMTP Relay (MMS v5.5.0)); Sun, 11 May 2003 20:45:02 -0600 Received: by entexchimc03.broadband.att.com with Internet Mail Service ( 5.5.2653.19) id ; Sun, 11 May 2003 20:43:04 -0600 Message-ID: <6732623D2548D61193C90002A5C88DCC0855141C@entmaexch02.broadband.att.com> From: "Woundy, Richard" To: "Ralph Droms" cc: dhcwg@ietf.org Subject: RE: [dhcwg] WG last call on draft-ietf-dhc-relay-agent-auth-00 Date: Sun, 11 May 2003 20:44:35 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) X-WSS-ID: 12A1D5244750458-01-01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Ralph, I generally support this document. But here are some specific comments on the current draft. - The Abstract should refer to IPsec per RFC 2401, not RFC 2041. Also, shouldn't RFC 2401 be included as a normative reference? - Section 5 explains the use of IPsec ESP. It would seems that a normative reference to RFC 2406, "IP Encapsulating Security Payload (ESP)", would be in order. That means that this draft's requirement that "Packet authentication MUST be applied" implies a requirement to support "HMAC with MD5" and "HMAC with SHA-1" per section 5 of RFC 2406. Is that intended? - Some updates may be needed in the "Authors' Addresses" section. ;^) - This might not be a critical flaw, but... only the HMAC-MD5 algorithm is defined for the Relay Agent Option Authentication Sub-option. I notice that in several other IETF contexts (IPsec AH, RFC 2402; IPsec ESP, RFC 2406; SNMPv3 USM, RFC 3414; TLS, RFC 2246), the HMAC-SHA1 keyed hash is also leveraged. The following text from RFC 2104 may help explain why: Note: To the date of writing of this document MD5 and SHA-1 are the most widely used cryptographic hash functions. MD5 has been recently shown to be vulnerable to collision search attacks [Dobb]. This attack and other currently known weaknesses of MD5 do not compromise the use of MD5 within HMAC as specified in this document (see [Dobb]); however, SHA-1 appears to be a cryptographically stronger function. To this date, MD5 can be considered for use in HMAC for applications where the superior performance of MD5 is critical. Note that RFC 2747, "RSVP Cryptographic Authentication", is a good counter-example in that it only defines HMAC-MD5 for the INTEGRITY object, but explains its rationale in section 1 if its RFC. Another counter-example is RFC 2845, "Secret Key Transaction Authentication for DNS (TSIG)" -- but also see . -- Rich -----Original Message----- From: Ralph Droms [mailto:rdroms@cisco.com] Sent: Wednesday, April 30, 2003 12:03 PM To: dhcwg@ietf.org Subject: [dhcwg] WG last call on draft-ietf-dhc-relay-agent-auth-00 This message announces a WG last call on "The Authentication Suboption for the DHCP Relay Agent Option" . The last call will conclude on Friday, May 16. Please respond to this WG last call. If you support acceptance of the document without change, respond with a simple acknowledgment, so that support for the document can be assessed. This specification defines two mechanisms for securing the messages exchanged between a relay agent and a server. The first mechanism defines a new authentication suboption for the Relay Agent Information Option that supports source entity authentication and data integrity for relayed DHCP messages. The authentication suboption contains a cryptographic signature in a payload derived from the option used in DHCP Authentication (RFC 3118). The second mechanism uses IPsec (RFC 2041) to protect messages exchanged between relay agents and servers. This document is being considered for publication as Informational, and is available as http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-agent-auth-00.txt - 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 From mailnull@www1.ietf.org Tue May 13 06:57:04 2003 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 GAA03454 for ; Tue, 13 May 2003 06:57:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DAN3N07757 for dhcwg-archive@odin.ietf.org; Tue, 13 May 2003 06:23: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 h4DAN2B07754 for ; Tue, 13 May 2003 06:23:03 -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 GAA03449 for ; Tue, 13 May 2003 06:56:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FXUL-0001dM-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 06:58:29 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FXUL-0001dD-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 06:58:29 -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 h4DAKxB07601; Tue, 13 May 2003 06:20:59 -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 h4DAHqB07476 for ; Tue, 13 May 2003 06:17:52 -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 GAA03276 for ; Tue, 13 May 2003 06:51:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FXPL-0001ar-00 for dhcwg@ietf.org; Tue, 13 May 2003 06:53:19 -0400 Received: from proxy.force.de ([158.116.254.130]) by ietf-mx with esmtp (Exim 4.12) id 19FXPK-0001ao-00 for dhcwg@ietf.org; Tue, 13 May 2003 06:53:18 -0400 Received: from ex-deu-munich02.force.de (ex-deu-munich02.force.de [10.254.2.10]) by proxy.force.de (8.11.4/8.11.4) with ESMTP id h4DAsPw20000 for ; Tue, 13 May 2003 12:54:26 +0200 (MEST) Received: by ex-deu-munich02.force.de with Internet Mail Service (5.5.2653.19) id ; Tue, 13 May 2003 12:55:05 +0200 Message-ID: <9CFB9DA5261CD611A29B00508B7890484A113B@ex-deu-munich02.force.de> From: "Kholodnyi, Andrei" To: "'dhcwg@ietf.org'" Cc: "Kholodnyi, Andrei" Date: Tue, 13 May 2003 12:55:03 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [dhcwg] What OID to use before it is officially assigned by IANA? 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: , List-Id: List-Post: List-Help: List-Subscribe: , Hi All, Are there any rules what OID to use in Internet-Draft MIBs before it is assigned by IANA? I've implemented dhcp server MIB that is defined in http://www.ietf.org/internet-drafts/draft-ietf-dhc-server-mib-08.txt and want to use it. In draft is written: DESCRIPTION "Initial Version, published as RFC xxxx." -- RFC Editor assigns xxxx and removes this comment ::= { mib-2 TBD } -- IANA will make official assignment What OID should I use?? Regards, Andrei. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Tue May 13 14:51:09 2003 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 ; 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 ; 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 ; 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 ; 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 ; 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 ; Tue, 13 May 2003 13:30:47 -0500 Message-ID: From: "Bernie Volz (EUD)" To: "'Peter Barany'" , "'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: , List-Id: List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C3197D.7A94D90C Content-Type: text/plain; charset="iso-8859-1" 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 ] 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 Best Regards, -Juha W.- -----Original Message----- From: ext Ralph Droms [ 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 _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg ------_=_NextPart_001_01C3197D.7A94D90C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [dhcwg] Stateless DHCPv6 service
It can=20 send a single Reply with the 2 options.
-----Original Message-----
From: Peter Barany=20 [mailto:pbarany@nortelnetworks.com]
Sent: Thursday, May 08, = 2003=20 4:53 PM
To: 'juha.wiljakka@nokia.com';=20 rdroms@cisco.com
Cc: dhcwg@ietf.org
Subject: RE: = [dhcwg]=20 Stateless DHCPv6 service

Hi,

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

Regards,

Pete

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


Hi, Ralph!

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

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

http://www.ietf.org/internet-drafts/draft-ietf-sip-dhcpv6-01.txt=20

Best Regards,=20
                  -Juha = W.-=20

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


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

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

- Ralph

_______________________________________________=20
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.= org/mailman/listinfo/dhcwg=20
_______________________________________________=20
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.= org/mailman/listinfo/dhcwg=20

------_=_NextPart_001_01C3197D.7A94D90C-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Tue May 13 17:49:57 2003 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 RAA00172 for ; Tue, 13 May 2003 17:49:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DLG8t32443 for dhcwg-archive@odin.ietf.org; Tue, 13 May 2003 17:16:08 -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 h4DLG8B32440 for ; Tue, 13 May 2003 17:16: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 RAA00166 for ; Tue, 13 May 2003 17:49:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fhg9-00006D-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 17:51:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Fhg9-00006A-00 for dhcwg-web-archive@ietf.org; Tue, 13 May 2003 17:51:21 -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 h4DL5FB31190; Tue, 13 May 2003 17:05:15 -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 h4DL0wB30802 for ; Tue, 13 May 2003 17:00:58 -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 RAA29922 for ; Tue, 13 May 2003 17:34:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FhRT-00002o-00 for dhcwg@ietf.org; Tue, 13 May 2003 17:36:11 -0400 Received: from smtp012.mail.yahoo.com ([216.136.173.32]) by ietf-mx with smtp (Exim 4.12) id 19FhRS-00002l-00 for dhcwg@ietf.org; Tue, 13 May 2003 17:36:11 -0400 Received: from adsl-64-169-89-159.dsl.snfc21.pacbell.net (HELO BarrH63p601) (rbhibbs@pacbell.net@64.169.89.159 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 13 May 2003 21:37:15 -0000 Reply-To: From: "Barr Hibbs" To: "Kholodnyi, Andrei" , Subject: RE: [dhcwg] What OID to use before it is officially assigned by IANA? Date: Tue, 13 May 2003 14:36:51 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <9CFB9DA5261CD611A29B00508B7890484A113B@ex-deu-munich02.force.de> Content-Transfer-Encoding: 7bit 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit if you choose an OID prior to IANA assignment, you will have to change it later, possibly under awkward circumstances. If you can wait, you should, as the Working Group Last Call period just ended this past Friday, so progress towards becoming an RFC should be relatively quick now. --Barr Hibbs > -----Original Message----- > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of > Kholodnyi, Andrei > Sent: Tuesday, May 13, 2003 03:55 > To: 'dhcwg@ietf.org' > Cc: Kholodnyi, Andrei > Subject: [dhcwg] What OID to use before it is officially assigned by > IANA? > > > Hi All, > > Are there any rules what OID to use in > Internet-Draft MIBs before it is assigned by IANA? > > I've implemented dhcp server MIB that is defined in > http://www.ietf.org/internet-drafts/draft-ietf-dhc-server-mib-08.txt > and want to use it. > > In draft is written: > DESCRIPTION "Initial Version, published as RFC xxxx." > -- RFC Editor assigns xxxx and removes this comment > ::= { mib-2 TBD } -- IANA will make official assignment > > What OID should I use?? > > Regards, > Andrei. > > > _______________________________________________ > 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 From mailnull@www1.ietf.org Fri May 30 07:19:56 2003 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 HAA28787 for ; Fri, 30 May 2003 07:19:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4UBJRP24989 for dhcwg-archive@odin.ietf.org; Fri, 30 May 2003 07:19:27 -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 h4UBJRB24986 for ; Fri, 30 May 2003 07:19:27 -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 HAA28744 for ; Fri, 30 May 2003 07:19:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LhtK-000296-00 for dhcwg-web-archive@ietf.org; Fri, 30 May 2003 07:17:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LhtJ-000291-00 for dhcwg-web-archive@ietf.org; Fri, 30 May 2003 07:17:45 -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 h4UBHMB24892; Fri, 30 May 2003 07:17:22 -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 h4UBDDB24723 for ; Fri, 30 May 2003 07:13:13 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27984; Fri, 30 May 2003 07:13:10 -0400 (EDT) Message-Id: <200305301113.HAA27984@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: dhcwg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Fri, 30 May 2003 07:13:09 -0400 Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-pktc-kerb-tckt-02.txt 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: , List-Id: List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration Working Group of the IETF. Title : PacketCable Security Ticket Control Sub-option for the CableLabs Client Configuration Option Author(s) : P. Duffy Filename : draft-ietf-dhc-pktc-kerb-tckt-02.txt Pages : 7 Date : 2003-5-29 This document defines a new sub-option for the CableLabs Client Configuration (CCC) Option. This new sub-option will be used to direct CableLabs Client Devices (CCDs) to invalidate locally persisted Kerberos tickets. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dhc-pktc-kerb-tckt-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-dhc-pktc-kerb-tckt-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-dhc-pktc-kerb-tckt-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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-29161325.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dhc-pktc-kerb-tckt-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dhc-pktc-kerb-tckt-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-29161325.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg From mailnull@www1.ietf.org Fri May 30 16:41:31 2003 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 QAA27128 for ; Fri, 30 May 2003 16:41:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4UKf4I04310 for dhcwg-archive@odin.ietf.org; Fri, 30 May 2003 16:41:04 -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 h4UKf4B04307 for ; Fri, 30 May 2003 16:41: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 QAA27120 for ; Fri, 30 May 2003 16:41:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lqen-0001GP-00 for dhcwg-web-archive@ietf.org; Fri, 30 May 2003 16:39:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Lqem-0001GM-00 for dhcwg-web-archive@ietf.org; Fri, 30 May 2003 16:39:20 -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 h4UKdNB04187; Fri, 30 May 2003 16:39:23 -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 h4UKa2B03181 for ; Fri, 30 May 2003 16:36:02 -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 QAA26996 for ; Fri, 30 May 2003 16:35:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LqZu-0001EH-00 for dhcwg@ietf.org; Fri, 30 May 2003 16:34:18 -0400 Received: from smtp017.mail.yahoo.com ([216.136.174.114]) by ietf-mx with smtp (Exim 4.12) id 19LqZu-0001E7-00 for dhcwg@ietf.org; Fri, 30 May 2003 16:34:18 -0400 Received: from adsl-64-169-89-159.dsl.snfc21.pacbell.net (HELO BarrH63p601) (rbhibbs@pacbell.net@64.169.89.159 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 May 2003 20:35:57 -0000 Reply-To: From: "Barr Hibbs" To: "Arvanitis Kostas" , Subject: RE: [dhcwg] dhc-server-mib Date: Fri, 30 May 2003 13:27:12 -0700 Message-ID: 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 IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal In-Reply-To: <200305271521.35324.arvanit@ellemedia.com> Content-Transfer-Encoding: 7bit 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: , List-Id: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit > -----Original Message----- > From: Arvanitis Kostas > Sent: Tuesday, May 27, 2003 05:22 > *** Snip! *** > > 1. In the MIB, two notifications are defined, namely > "dhcpv4ServerFreeAddressLow" and "dhcpv4ServerFreeAddressHigh", that deal > with the free address count in shared nets. However, shared nets > are stated > as optional in the MIB, since some DHCP servers may not implement them. > Shouldn't they be named something more specific, such as > "dhcpv4SharedNetFreeAddressLow" and "dhcpv4SharedNetFreeAddressHigh"? > > 2. There are no notifications defined for subnets, although the required > fields exist and are marked as "accessible-for-notify". Shouldn't > there be > "dhcpv4SubnetFreeAddressLow" and "dhcpv4SubnetFreeAddressHigh" > definitions? > This design was based on practical experience with a widely deployed server, in particular an implementation with tens of thousands of clients on thousands of subnets. Basically, trying to track the address counts to the subnet level is both misleading and futile. Most servers of which I'm aware (and certainly the one on which this MIB design was based) do NOT allocate leases by subnet, but rather by shared network Suppose shared network A is composed of 3 subnets. Using some opaque algorithm, leases are assigned, and clients randomly return addresses, eventually leaving a configuration that is largely non-deterministic based on the starting conditions. Shared network A may have 40% free leases, although subnetwork 1 has only 3% free, while subnetwork 2 has 60% free, and subnetwork 3 has 57% free. It's important to only report counts that are significant, and the impending unavailability of free leases on subnetwork 1 does NOT affect the ability of a typical server to hand out addresses for shared network A, so I would argue that reporting counts by the subnet is misleading, as it does not reflect the ability of the server to operate correctly, and futile, because there is no control or action the administrator can take to affect the count. Hope that explanation helps. --Barr _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg