From dhcwg-bounces@ietf.org  Fri Apr  1 16:01:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17073
	for <dhcwg-web-archive@ietf.org>; Fri, 1 Apr 2005 16:01:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTNu-0005ur-6I
	for dhcwg-web-archive@ietf.org; Fri, 01 Apr 2005 16:08:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHSen-00026g-5c; Fri, 01 Apr 2005 15:22:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHSej-00025F-JJ; Fri, 01 Apr 2005 15:22:13 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05427;
	Fri, 1 Apr 2005 15:22:09 -0500 (EST)
Message-Id: <200504012022.PAA05427@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 01 Apr 2005 15:22:09 -0500
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-proxyserver-opt-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

--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		: DHCP Option for Proxy Server Configuration
	Author(s)	: S. Balasubramanian, et al.
	Filename	: draft-ietf-dhc-proxyserver-opt-03.txt
	Pages		: 10
	Date		: 2005-4-1
	
This document defines a new Dynamic Host Configuration Protocol
   (DHCP) option, which can be used to configure the TCP/IP host's
   Proxy Server configuration for standard protocols like HTTP, FTP,
   NNTP, SOCKS, Gopher, SLL and etc. Proxy Server provides controlled
   and efficient access to the Internet by access control mechanism
   for different types of user requests and caching frequently accessed
   information (Web pages and possibly files that might have been
   downloaded using FTP and other protocols).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-proxyserver-opt-03.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-proxyserver-opt-03.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-proxyserver-opt-03.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: <2005-4-1154924.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-proxyserver-opt-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dhc-proxyserver-opt-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-1154924.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From dhcwg-bounces@ietf.org  Fri Apr  1 16:42:45 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24796
	for <dhcwg-web-archive@ietf.org>; Fri, 1 Apr 2005 16:42:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHU26-0000Wo-Iu
	for dhcwg-web-archive@ietf.org; Fri, 01 Apr 2005 16:50:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTlj-0008S1-5z; Fri, 01 Apr 2005 16:33:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTlh-0008Rt-3x; Fri, 01 Apr 2005 16:33:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23413;
	Fri, 1 Apr 2005 16:33:27 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTt5-0008Op-T5; Fri, 01 Apr 2005 16:41:08 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j31LWa617637;
	Fri, 1 Apr 2005 13:32:36 -0800 (PST)
Message-Id: <200504012132.j31LWa617637@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 01 Apr 2005 13:32:36 -0800
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] RFC 4030 on The Authentication Suboption for the Dynamic
	Host Configuration Protocol (DHCP) Relay Agent Option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027


--NextPart


A new Request for Comments is now available in online RFC libraries.


        RFC 4030

        Title:      The Authentication Suboption for the
                    Dynamic Host Configuration Protocol (DHCP)
                    Relay Agent Option
        Author(s):  M. Stapp, T. Lemon
        Status:     Standards Track
        Date:       March 2005
        Mailbox:    mjs@cisco.com, Ted.Lemon@nominum.com
        Pages:      15
        Characters: 34332
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-dhc-auth-suboption-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4030.txt


The Dynamic Host Configuration Protocol (DHCP) Relay Agent Information
Option (RFC 3046) conveys information between a DHCP Relay Agent and a
DHCP server.  This specification defines an authentication suboption
for that option, containing a keyed hash in its payload.  The
suboption supports data integrity and replay protection for relayed
DHCP messages.

This document is a product of the Dynamic Host Configuration Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050401133107.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4030

--OtherAccess
Content-Type: Message/External-body; name="rfc4030.txt"; site="ftp.isi.edu";
	access-type="anon-ftp"; directory="in-notes"

Content-Type: text/plain
Content-ID: <050401133107.RFC@RFC-EDITOR.ORG>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--



From dhcwg-bounces@ietf.org  Tue Apr  5 09:11:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18596
	for <dhcwg-web-archive@ietf.org>; Tue, 5 Apr 2005 09:11:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIny5-0000rh-Kk
	for dhcwg-web-archive@ietf.org; Tue, 05 Apr 2005 09:19:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DInon-0005lj-4h; Tue, 05 Apr 2005 09:10:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DInom-0005kS-8w
	for dhcwg@megatron.ietf.org; Tue, 05 Apr 2005 09:10:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18419
	for <dhcwg@ietf.org>; Tue, 5 Apr 2005 09:10:06 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DInwv-0000pK-5x
	for dhcwg@ietf.org; Tue, 05 Apr 2005 09:18:34 -0400
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 05 Apr 2005 06:09:59 -0700
X-IronPort-AV: i="3.91,152,1110182400"; 
	d="txt'?scan'208"; a="625780077:sNHT45881484"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j35D9pgE028011
	for <dhcwg@ietf.org>; Tue, 5 Apr 2005 06:09:52 -0700 (PDT)
Received: from [161.44.65.247] ([161.44.65.247])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQJ16568;
	Tue, 5 Apr 2005 09:09:55 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Content-Type: multipart/mixed; boundary="=-Qu3zFT+ohF0sCnRxYwdW"
Date: Tue, 05 Apr 2005 09:09:58 -0400
Message-Id: <1112706598.5756.47.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b
Subject: [dhcwg] Minutes from March WG meeting
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594


--=-Qu3zFT+ohF0sCnRxYwdW
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I've attached draft minutes from the March WG meeting.  Please let me
know if you have any additions or corrections.  I plan to send the
minutes off for publication at the end of the day on 2005-04-07.

- Ralph


--=-Qu3zFT+ohF0sCnRxYwdW
Content-Disposition: attachment; filename=minutes.txt
Content-Type: text/plain; name=minutes.txt; charset=UTF-8
Content-Transfer-Encoding: 7bit

Minutes from dhc WG meeting at IETF 62.

Thanks to John Schnizlein for taking notes from which these minutes
were composed.

3315id-for-v4 as requirement for other WG specifications? Ted Lemon
-------------------------------------------------------------------
Ted Lemon asked that the WG discuss the use of the client-identifier
option, as defined in draft-ietf-dhc-3315id-for-v4-04.txt, in future
specifications that involve DHCP.  In particular, the specification
for DHCP for IP-over-infiniband,
draft-ietf-ipoib-dhcp-over-infiniband-09.txt, explicitly references
the definitions for the client-identifier option from RFC 2132, rather
than the new format defined in draft-ietf-dhc-3315id-for-v4-04.txt.

Because draft-ietf-dhc-3315id-for-v4-04.txt formally updates the DHCP
specification and deprecates other formats for the client-identifier,
there is no need for the dhc WG to take any specific action.  The dhc
WG chairs will go the ipoib WG to insist that the deprecated formats
for the client-identifier not be mentioned in
draft-ietf-ipoib-dhcp-over-infiniband-09.txt.

SMTP Option for DHCPv6                             Martin Stiemerling
---------------------------------------------------------------------
draft-cadar-dhc-dhcpv6-opt-smtp-00.txt defines the equivalent of the
DHCPv4 SMTP server option for DHCPv6.  Ted Lemon said that the DHCPv4
option is unused and can be used to mount a denial of service attack.
Stig Venaas said there is no evidence any e-mail clients use the
DHCPv4 option.  Ted said that it's not likely to be a good idea for a
host to use the local SMTP server when roaming.  Mark Andrews
expressed that the option sounds like a good idea but the security
issues need to be addressed.

Christian will ask on an SMTP-related mailing list about whether the
SMTP option is useful.  The WG will then reconsider whether to take on
the draft as a WG work item.

Source Address Selection Policy option for DHCPv6  T. Fujisaki
--------------------------------------------------------------
Fujisaki gave a short presentation about the option in
draft-hirotaka-dhc-source-address-selection-opt-01.txt, which
configurees the policy table for address selection in RFC 3484.  Stig
said the option looks useful and might even be extended to destination
address selection.  Alain Durand said that a policy global to the host
won't be adequate because it may be application-dependent.  Margaret
Wasserman said that RFC 3484 says the table should be configurable,
and it makes sense to carry thin-s configuration in DHCP, but the work
on the option should be in the ipv6 WG.

Fujisaki will rewrite
draft-hirotaka-dhc-source-address-selection-opt-01.txt to define the
option to carry only the RFC 3484 table configuration bits; a pointer
to RFC 3484 will motivate need for selection table and this option.
Fujisaki will take the edited draft to the ipv6 WG for review.

DHCPv6 Relay agent RADIUS Attribute Option         Wing Cheong Lau
------------------------------------------------------------------
Thomas Narten asked the WG to consider the criteria for RADIUS
attributes that may be carried in the relay agent option defined in
draft-ietf-dhc-v6-relay-radius-00.txt.


DHCPv6 Options for Fast Handovers                  Takeshi Ogawa
----------------------------------------------------------------
The author presented this draft at the mobopts IRTF WG, but there was
no time for discussion.  Consensus is that this draft should belong to
a MIP-related WG.

Service-Oriented Address Assignment using DHCP     Syam Madanapalli
-------------------------------------------------------------------
Madanapalli summarized the mechanism in
draft-ietf-dhc-soa-option-00.txt and
draft-syam-dhc-soav4-option-00.txt as automating the process of
assigning anycast addresses to services.  The mechanism is based on
the premise that some services will be provided through an anycast
address.  These addresses would be assigned dynamically on demand from
the providing server, rather than using a well-known address.

Ralph Droms asked how different kinds and types of services would be
defined.  Madanapalli responded that a draft defining the service
descriptions needs to be written.  Stig Venaas said that anycast
wouldn't work when a client needs to choose a specific web server.
Also, anycast has routing implications; how would anycast routing
information be injected into the routing protocols?

Margaret Wasserman found these options and the concepts confusing:
addresses are assigned to interfaces, not services.  Ralph responded
that the mechanism in these drafts enables application services to be
assigned an anycast address for the anycast-enabled service; the
concept is similar to MADCAP assignment of multicast addresses.

Thomas Narten asked who is the customer for these options?  Droms
asked if there is a document that describes the anycast service
framework in more detail to provide a context for these options.
Alain Durand said that this is a very complex area; how does the
server know its role in asking for an anycast address?

The WG consensus is to wait for an overall framework paper and
specific customers before proceeding.


Relay Agent Options                                Bernie Volz
--------------------------------------------------------------
Bernie Volz described draft-volz-dhc-dhcpv6-remoteid-00.txt and
draft-volz-dhc-dhcpv6-subid-00.txt as IPv6 version of the equivalent
DHCPv4 relay agent option sub-options.  The WG consensus was to accept
these two drafts as WG work items.

The WG then discussed forwarding DHCPv6 prefix delegation (DHCPv6-PD)
through relay agents.  The key issue is injecting routing information
about delegated prefixes if the delegation is not done at the router to
which the requesting router is attached.  A couple of alternatives
were discussed: edge router acts as DHCPv6-PD requesting router to
internal DHCP server and then acts as delegating router to customer
requesting router; new relay agent option allows delegating server to
inform edge router of delegation in message carrying delegation to
requesting router.  Ted Lemon asked what happens if the edge router
reboots and loses the information about delegated prefixes.  Someone
answered that the link to the CPE requesting router would flap and it
would re-request the prefix delegation.  David Hankins expressed a
preference for using a real routing protocol like BGP.  Discussion to
continue on the WG mailing list.


Zone Suffix Option for DHCPv6                      Renxiang Yan
---------------------------------------------------------------
Renxiang Yan was unable to attend the WG meeting.  Droms presented
some slides from an updated draft and explained that the server sends
a domain to which the client prepends its host name to form an FQDN.
No WG action taken at this time.


DHCP: IPv4 and IPv6 Dual-Stack Issues
-------------------------------------
Droms asked for WG consensus that draft-ietf-dhc-dual-stack-02.txt is
ready for WG last call.  Alain Durand said that the more general
problem is really a multi-homed host problem rather than just
IPv4-IPv6.  The WG agreed that there is a multi-homed host problem,
but there may be simplifying assumptions in the IPv4-IPv6 case so that
considering this draft is a way to make progress.  Consensus at the
meeting was that the draft is ready for WG last call.

Resolving the IPv4 and IPv6 Dual-Stack Issues      Tim Chown
------------------------------------------------------------
WG was asked what are the next steps in resolving the dual stack
issues listed in draft-ietf-dhc-dual-stack-02.txt.  One conclusion
from draft-ietf-dhc-dual-stack-02.txt is that IPv4 configuration
should not be added to DHCPv6; rather, DHCPv4 and DHCPv6 should be
kept separate, with the assumption that a single admin can keep the
servers in sync.

Droms asked what the scope of the next document might be.  Ted Lemon
said that he doesn't think there is a protocol solution.  Another
comment was that how to handle configuration of merging is a hard
problem.  Tim Chown suggested limiting the scope of a next document to
the scenario in which both the DHCPv4 and DHCPv6 services are managed
in the same admin domain.  Dave Thaler said that there are two
separate problems: (1) in absence of external input, how should
information from different DHCP services be merged? (2) how does the
DHCP service administrator resolve loss of information. The WG can
help with (2).  Alain Durand said that the first step is to determine
if the information comes from the same domain and is, therefore,
mergeable.  Margaret Wasserman said that merging the list of DNS server
is not as easy as it might seem - think about a client where one of
its interfaces is in a split-DNS environment.  The WG will continue to
work on this issue.

RFC3118 Delayed DHCP Authentication Using EAP      Alper Yegin
--------------------------------------------------------------
Alper Yegin gave a presentation on
draft-yegin-eap-boot-rfc3118-01.txt, which uses RFC 3118
authentication with a shared key derived from the EAP authentication
step.  This mechanism would use a new relay agent suboption to push
the key to the DHCP server, and a new option in authentication
mechanisms (PANA, AVP; 802.1x TBD) to push the key to the client.
draft-yegin-eap-boot-rfc3118-01.txt is a derivative of an earlier
EAP-DHCP authentication by Yegin, which was not picked up as a WG work
item because of technical concerns.  Yegin will rewrite
draft-yegin-eap-boot-rfc3118-01.txt to describe DHCP authentication
independent of PANA, PPP or 802.1x, and include an appendix showing a
specific implementation (preferably 802.1x).


--=-Qu3zFT+ohF0sCnRxYwdW
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--=-Qu3zFT+ohF0sCnRxYwdW--



From dhcwg-bounces@ietf.org  Wed Apr  6 08:40:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06816
	for <dhcwg-web-archive@ietf.org>; Wed, 6 Apr 2005 08:40:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJ9xk-0006CY-Q2
	for dhcwg-web-archive@ietf.org; Wed, 06 Apr 2005 08:48:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJ9oB-0000sm-ST; Wed, 06 Apr 2005 08:38:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJ9oA-0000sg-Vp
	for dhcwg@megatron.ietf.org; Wed, 06 Apr 2005 08:38:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06750
	for <dhcwg@ietf.org>; Wed, 6 Apr 2005 08:38:57 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJ9wV-00067o-Rf
	for dhcwg@ietf.org; Wed, 06 Apr 2005 08:47:37 -0400
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 06 Apr 2005 05:38:49 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j36Cck3S025338
	for <dhcwg@ietf.org>; Wed, 6 Apr 2005 05:38:47 -0700 (PDT)
Received: from che-vpn-cluster-2-212.cisco.com
	(che-vpn-cluster-2-212.cisco.com [10.86.242.212])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQK03038;
	Wed, 6 Apr 2005 08:38:45 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Content-Type: text/plain
Date: Wed, 06 Apr 2005 08:38:46 -0400
Message-Id: <1112791126.26048.22.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Reminder - request for input on WG meeting minutes
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit

Reminder - please review the WG meeting minutes and reply with any
additions or corrections by tomorrow, 2005-04-07.

For the record, who was the Jabber scribe?

- Ralph



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


From dhcwg-bounces@ietf.org  Wed Apr  6 10:09:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14859
	for <dhcwg-web-archive@ietf.org>; Wed, 6 Apr 2005 10:09:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJBLq-0000AB-Io
	for dhcwg-web-archive@ietf.org; Wed, 06 Apr 2005 10:17:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJBBk-0007TW-JP; Wed, 06 Apr 2005 10:07:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJBBi-0007TR-7n
	for dhcwg@megatron.ietf.org; Wed, 06 Apr 2005 10:07:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14563
	for <dhcwg@ietf.org>; Wed, 6 Apr 2005 10:07:20 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJBK4-00006Q-0B
	for dhcwg@ietf.org; Wed, 06 Apr 2005 10:16:01 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 06 Apr 2005 10:07:12 -0400
Received: from [68.50.86.232] (che-vpn-cluster-1-144.cisco.com [10.86.240.144])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j36E791j021434; 
	Wed, 6 Apr 2005 10:07:10 -0400 (EDT)
In-Reply-To: <1112791126.26048.22.camel@localhost.localdomain>
References: <1112791126.26048.22.camel@localhost.localdomain>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <28E3391E-A6A5-11D9-89BD-00112473A260@cisco.com>
Content-Transfer-Encoding: 7bit
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [WARNING: A/V UNSCANNABLE] [dhcwg] Reminder - request for input
	on WG meeting minutes
Date: Wed, 6 Apr 2005 10:07:06 -0400
To: Ralph Droms <rdroms@cisco.com>
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

What did you attach to this email that made Cisco's spam detector go 
wild?

John

On Apr 6, 2005, at 8:38 AM, Ralph Droms wrote:

> Reminder - please review the WG meeting minutes and reply with any
> additions or corrections by tomorrow, 2005-04-07.
>
> For the record, who was the Jabber scribe?
>
> - 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


From dhcwg-bounces@ietf.org  Wed Apr  6 11:13:53 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22555
	for <dhcwg-web-archive@ietf.org>; Wed, 6 Apr 2005 11:13:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJCMV-0002hF-E3
	for dhcwg-web-archive@ietf.org; Wed, 06 Apr 2005 11:22:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJC5Y-0005A5-QJ; Wed, 06 Apr 2005 11:05:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJC5U-00058r-G7; Wed, 06 Apr 2005 11:05:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20942;
	Wed, 6 Apr 2005 11:04:58 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJCDr-00028m-Ri; Wed, 06 Apr 2005 11:13:39 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DJC5T-0000O2-Vu; Wed, 06 Apr 2005 11:04:59 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DJC5T-0000O2-Vu@newodin.ietf.org>
Date: Wed, 06 Apr 2005 11:04:59 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: 'Information Refresh Time Option for DHCPv6' to
 Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Dynamic Host Configuration WG to 
consider the following document:

- 'Information Refresh Time Option for DHCPv6'
   <draft-ietf-dhc-lifetime-03.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-04-20.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-dhc-lifetime-03.txt


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


From dhcwg-bounces@ietf.org  Wed Apr  6 11:22:35 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25118
	for <dhcwg-web-archive@ietf.org>; Wed, 6 Apr 2005 11:22:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJCUv-0003Vj-UJ
	for dhcwg-web-archive@ietf.org; Wed, 06 Apr 2005 11:31:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJC59-00056P-FI; Wed, 06 Apr 2005 11:04:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJC54-00055A-Ke; Wed, 06 Apr 2005 11:04:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20894;
	Wed, 6 Apr 2005 11:04:32 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJCDR-00028F-Vi; Wed, 06 Apr 2005 11:13:14 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DJC53-00008Q-Qi; Wed, 06 Apr 2005 11:04:33 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DJC53-00008Q-Qi@newodin.ietf.org>
Date: Wed, 06 Apr 2005 11:04:33 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: 'Node-Specific Client Identifiers for DHCPv4' to
 Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Dynamic Host Configuration WG to 
consider the following document:

- 'Node-Specific Client Identifiers for DHCPv4'
   <draft-ietf-dhc-3315id-for-v4-04.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-04-20.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-dhc-3315id-for-v4-04.txt


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


From dhcwg-bounces@ietf.org  Wed Apr  6 21:12:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29817
	for <dhcwg-web-archive@ietf.org>; Wed, 6 Apr 2005 21:12:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJLhg-0004PH-6E
	for dhcwg-web-archive@ietf.org; Wed, 06 Apr 2005 21:21:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJLXy-000707-J4; Wed, 06 Apr 2005 21:11:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJLXx-000702-HJ
	for dhcwg@megatron.ietf.org; Wed, 06 Apr 2005 21:11:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29642
	for <dhcwg@ietf.org>; Wed, 6 Apr 2005 21:10:59 -0400 (EDT)
From: peter_blatherwick@mitel.com
Received: from smtp.mitel.com ([216.191.234.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJLgP-0004NQ-QH
	for dhcwg@ietf.org; Wed, 06 Apr 2005 21:19:46 -0400
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP id BB8B7200F8
	for <dhcwg@ietf.org>; Wed,  6 Apr 2005 21:10:51 -0400 (EDT)
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new,
	port 10124) with LMTP id 09350-05-3 for <dhcwg@ietf.org>;
	Wed,  6 Apr 2005 21:10:51 -0400 (EDT)
Received: from kanmta01.mitel.com (kanmta01 [134.199.37.58])
	by smtp.mitel.com (Postfix) with ESMTP id 4605C200F4
	for <dhcwg@ietf.org>; Wed,  6 Apr 2005 21:10:51 -0400 (EDT)
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFC426C0AC.C765ED44-ON85256FDC.000400D3-85256FDC.00067EDB@mitel.com>
Date: Wed, 6 Apr 2005 21:12:48 -0400
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.12 |February 13,
	2003) at 04/06/2005 09:10:47 PM,
	Serialize complete at 04/06/2005 09:10:47 PM
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Subject: [dhcwg] Process for responding to RFC 3942,
	DHCPv4 Options Reclassification
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0112351945=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

This is a multipart message in MIME format.
--===============0112351945==
Content-Type: multipart/alternative;
	boundary="=_alternative 00067ED885256FDC_="

This is a multipart message in MIME format.
--=_alternative 00067ED885256FDC_=
Content-Type: text/plain; charset="us-ascii"

Hi, 

I'm sure this must be a multiple repeat question, but I have not managed 
to find a good answer by searching.  So here goes.... 

I'm trying to determine what the process is supposed to be to register our 
currently used vendor-specific DHCP options, so that they are not 
overridden pre-emptively as a result of RFC 3942.  The RFC itself is not 
very specific, other than both IETF and IANA need to be notified. 

The specific text at hand is:
"
   2. Vendors that currently use one or more of the reclassified options
      have 6 months following this RFC's publication date to notify the
      DHC WG and IANA that they are using particular options numbers and
      agree to document that usage in an RFC.  IANA will move these
      options from the "Unavailable" to "Tentatively Assigned" state.
"

More specifically, the questions are:

1. What needs to be submitted to this WG to describe what options we are 
currently using.  I assume we should list which specific options, and 
approximate purpose.  Is there other information required?  Should this be 
in the form of an I-D (it appears so). 

2. How to get this same information to IANA so that the currently used 
options are assured to be put in "Tentatively Assigned" and reserved from 
standardization until the end of the 18 month moratorium period?  Is this 
also covered by the I-D to this WG as above, or is there something else? 
How ids this confirmed? 

3. When, exactly, is the end of the registration period?  The RFC states 6 
months from RFC issue, and is dated November 2004 (it was very late 
November I believe), so is the end date beginning of May, end of May, end 
of June, or what? 

Apologies in advance  for the newbie questions.... 

Cheers,
Peter Blatherwick



--=_alternative 00067ED885256FDC_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Hi, </font>
<br>
<br><font size=2 face="sans-serif">I'm sure this must be a multiple repeat question, but I have not managed to find a good answer by searching. &nbsp;So here goes.... </font>
<br>
<br><font size=2 face="sans-serif">I'm trying to determine what the process is supposed to be to register our currently used vendor-specific DHCP options, so that they are not overridden pre-emptively as a result of RFC 3942. &nbsp;The RFC itself is not very specific, other than both IETF and IANA need to be notified. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">The specific text at hand is:</font>
<br><font size=2 face="sans-serif">&quot;</font>
<br><font size=2 face="Courier New">&nbsp; &nbsp;2. Vendors that currently use one or more of the reclassified options</font>
<br><font size=2 face="Courier New">&nbsp; &nbsp; &nbsp; have 6 months following this RFC's publication date to notify the</font>
<br><font size=2 face="Courier New">&nbsp; &nbsp; &nbsp; DHC WG and IANA that they are using particular options numbers and</font>
<br><font size=2 face="Courier New">&nbsp; &nbsp; &nbsp; agree to document that usage in an RFC. &nbsp;IANA will move these</font>
<br><font size=2 face="Courier New">&nbsp; &nbsp; &nbsp; options from the &quot;Unavailable&quot; to &quot;Tentatively Assigned&quot; state.</font>
<br><font size=2 face="sans-serif">&quot;</font>
<br>
<br><font size=2 face="sans-serif">More specifically, the questions are:</font>
<br>
<br><font size=2 face="sans-serif">1. What needs to be submitted to this WG to describe what options we are currently using. &nbsp;I assume we should list which specific options, and approximate purpose. &nbsp;Is there other information required? &nbsp;Should this be in the form of an I-D (it appears so). &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">2. How to get this same information to IANA so that the currently used options are assured to be put in &quot;Tentatively Assigned&quot; and reserved from standardization until the end of the 18 month moratorium period? &nbsp;Is this also covered by the I-D to this WG as above, or is there something else? &nbsp;How ids this confirmed? &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">3. When, exactly, is the end of the registration period? &nbsp;The RFC states 6 months from RFC issue, and is dated November 2004 (it was very late November I believe), so is the end date beginning of May, end of May, end of June, or what? &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Apologies in advance &nbsp;for the newbie questions.... &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Cheers,</font>
<br><font size=2 face="sans-serif">Peter Blatherwick</font>
<br>
<br>
<br>
--=_alternative 00067ED885256FDC_=--


--===============0112351945==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============0112351945==--



From dhcwg-bounces@ietf.org  Thu Apr  7 08:20:11 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15474
	for <dhcwg-web-archive@ietf.org>; Thu, 7 Apr 2005 08:20:11 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJW86-00083o-1w
	for dhcwg-web-archive@ietf.org; Thu, 07 Apr 2005 08:29:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJVxv-0005z7-FY; Thu, 07 Apr 2005 08:18:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJVxu-0005yH-1W
	for dhcwg@megatron.ietf.org; Thu, 07 Apr 2005 08:18:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15327
	for <dhcwg@ietf.org>; Thu, 7 Apr 2005 08:18:28 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJW6R-0007z2-5f
	for dhcwg@ietf.org; Thu, 07 Apr 2005 08:27:20 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 07 Apr 2005 05:18:19 -0700
X-IronPort-AV: i="3.92,83,1112598000"; 
	d="scan'208"; a="246933545:sNHT28850664"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j37CIDZV003011;
	Thu, 7 Apr 2005 05:18:14 -0700 (PDT)
Received: from volzw2k (che-vpn-cluster-2-173.cisco.com [10.86.242.173])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQK91406;
	Thu, 7 Apr 2005 08:18:12 -0400 (EDT)
Message-Id: <200504071218.AQK91406@flask.cisco.com>
From: "Bernie Volz" <volz@cisco.com>
To: <peter_blatherwick@mitel.com>
Subject: RE: [dhcwg] Process for responding to RFC 3942,
	DHCPv4 Options Reclassification
Date: Thu, 7 Apr 2005 08:18:11 -0400
Organization: Cisco
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcU7DtITKrqb0fUvTDuFfdUeZWZ9aQAW6Fzg
In-reply-to: <OFC426C0AC.C765ED44-ON85256FDC.000400D3-85256FDC.00067EDB@mitel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: 7bit

Hi:
 
An email is fine to notify the DHC WG (dhcwg@ietf.org) and IANA
(iana@iana.org <mailto:iana@iana.org> ). Just include the option number(s)
and brief information about what it is used for -- the full details should
be documented in the Internet-Draft. An example is
http://www.ietf.org/mail-archive/web/dhcwg/current/msg04726.html.

I've been assuming that we would use the end of May (May 31st) as the
deadline to compile the list of Tentatively Assigned options since the RFC
came out late in November and I'd rather err on giving people a bit more
time.

I will be working with IANA to make sure that the list of tentatively
assigned options is produced after the deadline.
 
Hope that answers your questions.
 
- Bernie

________________________________

	From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On
Behalf Of peter_blatherwick@mitel.com
	Sent: Wednesday, April 06, 2005 9:13 PM
	To: dhcwg@ietf.org
	Subject: [dhcwg] Process for responding to RFC 3942,DHCPv4 Options
Reclassification
	
	
	
	Hi, 
	
	I'm sure this must be a multiple repeat question, but I have not
managed to find a good answer by searching.  So here goes.... 
	
	I'm trying to determine what the process is supposed to be to
register our currently used vendor-specific DHCP options, so that they are
not overridden pre-emptively as a result of RFC 3942.  The RFC itself is not
very specific, other than both IETF and IANA need to be notified.   
	
	The specific text at hand is: 
	" 
	   2. Vendors that currently use one or more of the reclassified
options 
	      have 6 months following this RFC's publication date to notify
the 
	      DHC WG and IANA that they are using particular options numbers
and 
	      agree to document that usage in an RFC.  IANA will move these 
	      options from the "Unavailable" to "Tentatively Assigned"
state. 
	" 
	
	More specifically, the questions are: 
	
	1. What needs to be submitted to this WG to describe what options we
are currently using.  I assume we should list which specific options, and
approximate purpose.  Is there other information required?  Should this be
in the form of an I-D (it appears so).   
	
	2. How to get this same information to IANA so that the currently
used options are assured to be put in "Tentatively Assigned" and reserved
from standardization until the end of the 18 month moratorium period?  Is
this also covered by the I-D to this WG as above, or is there something
else?  How ids this confirmed?   
	
	3. When, exactly, is the end of the registration period?  The RFC
states 6 months from RFC issue, and is dated November 2004 (it was very late
November I believe), so is the end date beginning of May, end of May, end of
June, or what?   
	
	Apologies in advance  for the newbie questions....   
	
	Cheers, 
	Peter Blatherwick 
	
	
	


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


From dhcwg-bounces@ietf.org  Thu Apr  7 09:56:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24469
	for <dhcwg-web-archive@ietf.org>; Thu, 7 Apr 2005 09:56:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJXdJ-0003S8-L3
	for dhcwg-web-archive@ietf.org; Thu, 07 Apr 2005 10:05:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJXLB-0007L5-UD; Thu, 07 Apr 2005 09:46:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJXLA-0007Kz-Ba
	for dhcwg@megatron.ietf.org; Thu, 07 Apr 2005 09:46:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23519
	for <dhcwg@ietf.org>; Thu, 7 Apr 2005 09:46:34 -0400 (EDT)
From: peter_blatherwick@mitel.com
Received: from smtp.mitel.com ([216.191.234.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJXTg-00032I-En
	for dhcwg@ietf.org; Thu, 07 Apr 2005 09:55:27 -0400
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP
	id 27CB620110; Thu,  7 Apr 2005 09:46:23 -0400 (EDT)
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new,
	port 10124) with LMTP
	id 26202-02-3; Thu,  7 Apr 2005 09:46:22 -0400 (EDT)
Received: from kanmta01.mitel.com (kanmta01 [134.199.37.58])
	by smtp.mitel.com (Postfix) with ESMTP
	id 94C5B20109; Thu,  7 Apr 2005 09:46:22 -0400 (EDT)
To: "Bernie Volz" <volz@cisco.com>
Subject: RE: [dhcwg] Process for responding to RFC 3942,DHCPv4 Options
	Reclassification
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFC44DE065.5A0E9833-ON85256FDC.004AF933-85256FDC.004BA7A8@mitel.com>
Date: Thu, 7 Apr 2005 09:48:23 -0400
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.12 |February 13,
	2003) at 04/07/2005 09:46:20 AM,
	Serialize complete at 04/07/2005 09:46:20 AM
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 65bc4909d78e8b10349def623cf7a1d1
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1785391876=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 83e9494d829b08cc3f644ef6ac1b9bd4

This is a multipart message in MIME format.
--===============1785391876==
Content-Type: multipart/alternative;
	boundary="=_alternative 004BA7A485256FDC_="

This is a multipart message in MIME format.
--=_alternative 004BA7A485256FDC_=
Content-Type: text/plain; charset="us-ascii"

Thanks Bernie, that's what we needed, 

I will put that email together (we work with a lot of partners, so a bit 
easier said than done ;-)    I'm not sure it would be useful to document 
full details in an I-D, since we are currently looking at moving away from 
our vendor specific scheme; likely to use options 60/43 or 124/125 
approach instead.  We know we have been naughty on this (like many others 
;-).   Will do the I-D if it is needed -- please let us know once I can 
get the email step done. 

May I suggest a good step would be to put the compiled list out on this 
email list when completed, so the group can check for any slips.

Cheers,
Peter







"Bernie Volz" <volz@cisco.com>
07.04.05 08:18

 
        To:     <peter_blatherwick@mitel.com>
        cc:     <dhcwg@ietf.org>
        Subject:        RE: [dhcwg] Process for responding to RFC 3942,DHCPv4 Options 
Reclassification


Hi:
 
An email is fine to notify the DHC WG (dhcwg@ietf.org) and IANA
(iana@iana.org <mailto:iana@iana.org> ). Just include the option number(s)
and brief information about what it is used for -- the full details should
be documented in the Internet-Draft. An example is
http://www.ietf.org/mail-archive/web/dhcwg/current/msg04726.html.

I've been assuming that we would use the end of May (May 31st) as the
deadline to compile the list of Tentatively Assigned options since the RFC
came out late in November and I'd rather err on giving people a bit more
time.

I will be working with IANA to make sure that the list of tentatively
assigned options is produced after the deadline.
 
Hope that answers your questions.
 
- Bernie

________________________________

                 From: dhcwg-bounces@ietf.org 
[mailto:dhcwg-bounces@ietf.org] On
Behalf Of peter_blatherwick@mitel.com
                 Sent: Wednesday, April 06, 2005 9:13 PM
                 To: dhcwg@ietf.org
                 Subject: [dhcwg] Process for responding to RFC 
3942,DHCPv4 Options
Reclassification
 
 
 
                 Hi, 
 
                 I'm sure this must be a multiple repeat question, but I 
have not
managed to find a good answer by searching.  So here goes.... 
 
                 I'm trying to determine what the process is supposed to 
be to
register our currently used vendor-specific DHCP options, so that they are
not overridden pre-emptively as a result of RFC 3942.  The RFC itself is 
not
very specific, other than both IETF and IANA need to be notified. 
 
                 The specific text at hand is: 
                 " 
                    2. Vendors that currently use one or more of the 
reclassified
options 
                       have 6 months following this RFC's publication date 
to notify
the 
                       DHC WG and IANA that they are using particular 
options numbers
and 
                       agree to document that usage in an RFC.  IANA will 
move these 
                       options from the "Unavailable" to "Tentatively 
Assigned"
state. 
                 " 
 
                 More specifically, the questions are: 
 
                 1. What needs to be submitted to this WG to describe what 
options we
are currently using.  I assume we should list which specific options, and
approximate purpose.  Is there other information required?  Should this be
in the form of an I-D (it appears so). 
 
                 2. How to get this same information to IANA so that the 
currently
used options are assured to be put in "Tentatively Assigned" and reserved
from standardization until the end of the 18 month moratorium period?  Is
this also covered by the I-D to this WG as above, or is there something
else?  How ids this confirmed? 
 
                 3. When, exactly, is the end of the registration period? 
The RFC
states 6 months from RFC issue, and is dated November 2004 (it was very 
late
November I believe), so is the end date beginning of May, end of May, end 
of
June, or what? 
 
                 Apologies in advance  for the newbie questions.... 
 
                 Cheers, 
                 Peter Blatherwick 
 
 
 




--=_alternative 004BA7A485256FDC_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">Thanks Bernie, that's what we needed, &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">I will put that email together (we work with a lot of partners, so a bit easier said than done ;-) &nbsp; &nbsp;I'm not sure it would be useful to document full details in an I-D, since we are currently looking at moving away from our vendor specific scheme; likely to use options 60/43 or 124/125 approach instead. &nbsp;We know we have been naughty on this (like many others ;-). &nbsp; Will do the I-D if it is needed -- please let us know once I can get the email step done. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">May I suggest a good step would be to put the compiled list out on this email list when completed, so the group can check for any slips.</font>
<br>
<br><font size=2 face="sans-serif">Cheers,</font>
<br><font size=2 face="sans-serif">Peter</font>
<br>
<br>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>&quot;Bernie Volz&quot; &lt;volz@cisco.com&gt;</b></font>
<p><font size=1 face="sans-serif">07.04.05 08:18</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; &nbsp; &nbsp; &nbsp;&lt;peter_blatherwick@mitel.com&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; &nbsp; &nbsp; &nbsp;&lt;dhcwg@ietf.org&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; &nbsp; &nbsp; &nbsp;RE: [dhcwg] Process for responding to RFC 3942,DHCPv4 Options Reclassification</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Hi:<br>
 <br>
An email is fine to notify the DHC WG (dhcwg@ietf.org) and IANA<br>
(iana@iana.org &lt;mailto:iana@iana.org&gt; ). Just include the option number(s)<br>
and brief information about what it is used for -- the full details should<br>
be documented in the Internet-Draft. An example is<br>
http://www.ietf.org/mail-archive/web/dhcwg/current/msg04726.html.<br>
<br>
I've been assuming that we would use the end of May (May 31st) as the<br>
deadline to compile the list of Tentatively Assigned options since the RFC<br>
came out late in November and I'd rather err on giving people a bit more<br>
time.<br>
<br>
I will be working with IANA to make sure that the list of tentatively<br>
assigned options is produced after the deadline.<br>
 <br>
Hope that answers your questions.<br>
 <br>
- Bernie<br>
<br>
________________________________<br>
<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On<br>
Behalf Of peter_blatherwick@mitel.com<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Sent: Wednesday, April 06, 2005 9:13 PM<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; To: dhcwg@ietf.org<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Subject: [dhcwg] Process for responding to RFC 3942,DHCPv4 Options<br>
Reclassification<br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Hi, <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; I'm sure this must be a multiple repeat question, but I have not<br>
managed to find a good answer by searching. &nbsp;So here goes.... <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; I'm trying to determine what the process is supposed to be to<br>
register our currently used vendor-specific DHCP options, so that they are<br>
not overridden pre-emptively as a result of RFC 3942. &nbsp;The RFC itself is not<br>
very specific, other than both IETF and IANA need to be notified. &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; The specific text at hand is: <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &quot; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2. Vendors that currently use one or more of the reclassified<br>
options <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; have 6 months following this RFC's publication date to notify<br>
the <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; DHC WG and IANA that they are using particular options numbers<br>
and <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; agree to document that usage in an RFC. &nbsp;IANA will move these <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; options from the &quot;Unavailable&quot; to &quot;Tentatively Assigned&quot;<br>
state. <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &quot; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; More specifically, the questions are: <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1. What needs to be submitted to this WG to describe what options we<br>
are currently using. &nbsp;I assume we should list which specific options, and<br>
approximate purpose. &nbsp;Is there other information required? &nbsp;Should this be<br>
in the form of an I-D (it appears so). &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2. How to get this same information to IANA so that the currently<br>
used options are assured to be put in &quot;Tentatively Assigned&quot; and reserved<br>
from standardization until the end of the 18 month moratorium period? &nbsp;Is<br>
this also covered by the I-D to this WG as above, or is there something<br>
else? &nbsp;How ids this confirmed? &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3. When, exactly, is the end of the registration period? &nbsp;The RFC<br>
states 6 months from RFC issue, and is dated November 2004 (it was very late<br>
November I believe), so is the end date beginning of May, end of May, end of<br>
June, or what? &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Apologies in advance &nbsp;for the newbie questions.... &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Cheers, <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Peter Blatherwick <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <br>
<br>
</font>
<br>
<br>
--=_alternative 004BA7A485256FDC_=--


--===============1785391876==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1785391876==--



From dhcwg-bounces@ietf.org  Fri Apr  8 08:52:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14070
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 08:52:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJt6s-0003Zp-CW
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 09:01:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJsvN-0003q6-2c; Fri, 08 Apr 2005 08:49:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJsvL-0003pu-Mo
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 08:49:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13743
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 08:49:22 -0400 (EDT)
Received: from cpc4-cmbg4-4-0-cust135.cmbg.cable.ntl.com ([81.108.205.135]
	helo=thekelleys.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJt46-0003Sa-Oi
	for dhcwg@ietf.org; Fri, 08 Apr 2005 08:58:27 -0400
Received: from central ([192.168.0.4] helo=[127.0.0.1])
	by thekelleys.org.uk with esmtp (Exim 3.35 #1 (Debian))
	id 1DJsvC-0007Ck-00
	for <dhcwg@ietf.org>; Fri, 08 Apr 2005 13:49:14 +0100
Message-ID: <42567D63.4060002@thekelleys.org.uk>
Date: Fri, 08 Apr 2005 13:47:31 +0100
From: Simon Kelley <simon@thekelleys.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
X-Accept-Language: en
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] An enhancement for DHCPINFORM?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

I just started thinking about using DHCP for automatic configuration of
proxy addresses and I've hit a problem and come up with a solution.

The problem is this: suppose I want to use DHCPINFORM to get
configuration information for an non-privileged, user space application;
a good example would be a web browser doing WPAD via DHCP.

In principle this is easy, the application determines the address of the
DHCP server used to configure its host and and sends a UDP packet
containing a DHCPINFORM with the relevant "requested option" to port 68
of the DHCP server. The server returns the requested information to port
67 of the client and it now has the correct configuration information.

The problem is with use of port 67. A non-privileged application cannot
bind port 67 so it must be set-uid root or moral equivalent. Even then,
a DHCP client is likely to have port 67 bound for the purpose of lease
renewals, so an application cannot use it.

The proposed solution to this to define one the MBZ bits in the header
flags as "honour source address". If this bit is set, then the DHCP
server will not reply to the address in ciaddr and port 67, but instead
use the source address and port of the UDP packet carrying the
DHCPINFORM. Now, a user application can set this bit in a DHCPINFORM
sent from a non-privilged UDP socket, bound to an ephemeral port, and
the answer will be send back to the same socket.

This change is completely backwards compatible and very simple (it would
take about ten lines of code in dnsmasq, the DHCP server I'm most
familiar with, for example.)

Assuming nobody trashes this proposal for flaws which I've not seen, how 
would I go about getting it debated and accepted into the standard? I'm 
happy to write it up formally (as an RFC?) and follow the procedures, 
but I'm pretty hazy as to what those procedures are.

Cheers,

Simon.










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


From dhcwg-bounces@ietf.org  Fri Apr  8 11:14:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01729
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:11:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJv1L-0006BR-WC
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:03:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJuqV-00074w-TA; Fri, 08 Apr 2005 10:52:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJuqT-0006t9-GP
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 10:52:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27985
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 10:52:21 -0400 (EDT)
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJuyH-0004Pa-1c
	for dhcwg@ietf.org; Fri, 08 Apr 2005 11:00:34 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 17044481; Fri, 08 Apr 2005 16:51:22 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
Date: Fri, 8 Apr 2005 16:32:57 +0200
User-Agent: KMail/1.6.2
References: <42567D63.4060002@thekelleys.org.uk>
In-Reply-To: <42567D63.4060002@thekelleys.org.uk>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200504081632.57157.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

On Friday 08 April 2005 14:47, Simon Kelley wrote:
> I just started thinking about using DHCP for automatic configuration of
> proxy addresses and I've hit a problem and come up with a solution.

<snip>

> The proposed solution to this to define one the MBZ bits in the header
> flags as "honour source address". If this bit is set, then the DHCP
> server will not reply to the address in ciaddr and port 67, but instead
> use the source address and port of the UDP packet carrying the
> DHCPINFORM. Now, a user application can set this bit in a DHCPINFORM
> sent from a non-privilged UDP socket, bound to an ephemeral port, and
> the answer will be send back to the same socket.

Our DHCP server responds to the source port you're originating from, 
regardless of whether it's the "valid" port 68. (I think you mean port 68 in 
the above excerpt, that's the port the client should use)

I know there are others on this list that don't think that is appropriate 
behavior, but I personally felt like it was a reasonable enough thing to do. 
Besides, you can override that behavior at the server.

If you want to introduce a flag that says "honor the source address", then 
basically you're entrusting the client to not misuse that (such as a 
user-mode application trying to spoof another node). There's no difference 
between entrusting that to the client using a flag, or simply having the 
server respond to the port the query originated from. Either way, you're 
trusting the client.

As a side note, the most widely used OS allows any user-mode app to bind to 
privileged ports (last I checked), so it's not like you get any practical 
security by having the server drop datagrams that don't originate from port 
68.

- Bud

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687
mailto:budm@weird-solutions.com

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


From dhcwg-bounces@ietf.org  Fri Apr  8 11:14:35 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01282
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:10:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJv5o-0006sX-F1
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:08:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJuoH-00060o-Tl; Fri, 08 Apr 2005 10:50:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJuho-00042b-0S
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 10:43:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27005
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 10:37:01 -0400 (EDT)
Received: from chimera.incognito.com ([206.172.52.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJuX4-0000GR-QF
	for dhcwg@ietf.org; Fri, 08 Apr 2005 10:32:27 -0400
Received: from [206.172.52.116] (helo=HOMER.incognito.com.)
	by chimera.incognito.com with esmtp (Exim 4.34)
	id 1DJuO5-0002f5-NU; Fri, 08 Apr 2005 07:23:10 -0700
Received: by homer.incognito.com with Internet Mail Service (5.5.2653.19)
	id <GTVFW3B7>; Fri, 8 Apr 2005 07:22:39 -0700
Message-ID: <B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
From: "Kostur, Andre" <akostur@incognito.com>
To: "'Simon Kelley'" <simon@thekelleys.org.uk>, dhcwg@ietf.org
Subject: RE: [dhcwg] An enhancement for DHCPINFORM?
Date: Fri, 8 Apr 2005 07:22:36 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: -5.7 (-----)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1950691867=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab

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.

--===============1950691867==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53C46.69796D70"

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_01C53C46.69796D70
Content-Type: text/plain;
	charset="iso-8859-1"

> I just started thinking about using DHCP for automatic 
> configuration of
> proxy addresses and I've hit a problem and come up with a solution.
> 
> The problem is this: suppose I want to use DHCPINFORM to get
> configuration information for an non-privileged, user space 
> application;
> a good example would be a web browser doing WPAD via DHCP.

[snip.  Nutshell version of proposal: assign one flag bit to have the DHCP
server respond to the source port of the incoming INFORM instead of 67]

A few questions to ponder:

1) Would DNS lookup of SRV records be more appropriate?  Kerberos uses this
mechanism, for example.
2) Does your DHCP client already put the returned data somewhere where your
application could access the information, so you could simply read what your
original response was?  Perhaps a dhcpcd.eth0.leases file (Linux?) or the
registry (Win)
3) Does your DHCP client has some sort of provision where you could ask it
to perform the INFORM on your behalf and return you the data?
4) How much effort is it going to be on the part of the DHCP Relay
implementations to have to remember the source port of the request, and to
match up the response to the right request.  Recall that what would end up
happening (potentially) is that your client application may broadcast the
request (from say port 2000).  This gets picked up by a relay, and it
unicasts to the DHCP server (likely a different port than 2000, probably
either 67 or 68).  The DHCP server would then see this bit set and would be
"forced" to respond to the source port (again: either 67 or 68, depending on
your relay implmenetation.  Most signficantly it will probably not be 2000).
Then the relay would need to have enough memory to recall that this response
is associated with a certain request and look up what the original port
number was.  In addition, it would have to remember this port for a time
since the relay may be relaying to multiple DHCP services and you would want
all potential responses to be forwarded back to the client.

------_=_NextPart_001_01C53C46.69796D70
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [dhcwg] An enhancement for DHCPINFORM?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&gt; I just started thinking about using DHCP for =
automatic </FONT>
<BR><FONT SIZE=3D2>&gt; configuration of</FONT>
<BR><FONT SIZE=3D2>&gt; proxy addresses and I've hit a problem and come =
up with a solution.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The problem is this: suppose I want to use =
DHCPINFORM to get</FONT>
<BR><FONT SIZE=3D2>&gt; configuration information for an =
non-privileged, user space </FONT>
<BR><FONT SIZE=3D2>&gt; application;</FONT>
<BR><FONT SIZE=3D2>&gt; a good example would be a web browser doing =
WPAD via DHCP.</FONT>
</P>

<P><FONT SIZE=3D2>[snip.&nbsp; Nutshell version of proposal: assign one =
flag bit to have the DHCP server respond to the source port of the =
incoming INFORM instead of 67]</FONT></P>

<P><FONT SIZE=3D2>A few questions to ponder:</FONT>
</P>

<P><FONT SIZE=3D2>1) Would DNS lookup of SRV records be more =
appropriate?&nbsp; Kerberos uses this mechanism, for example.</FONT>
<BR><FONT SIZE=3D2>2) Does your DHCP client already put the returned =
data somewhere where your application could access the information, so =
you could simply read what your original response was?&nbsp; Perhaps a =
dhcpcd.eth0.leases file (Linux?) or the registry (Win)</FONT></P>

<P><FONT SIZE=3D2>3) Does your DHCP client has some sort of provision =
where you could ask it to perform the INFORM on your behalf and return =
you the data?</FONT></P>

<P><FONT SIZE=3D2>4) How much effort is it going to be on the part of =
the DHCP Relay implementations to have to remember the source port of =
the request, and to match up the response to the right request.&nbsp; =
Recall that what would end up happening (potentially) is that your =
client application may broadcast the request (from say port =
2000).&nbsp; This gets picked up by a relay, and it unicasts to the =
DHCP server (likely a different port than 2000, probably either 67 or =
68).&nbsp; The DHCP server would then see this bit set and would be =
&quot;forced&quot; to respond to the source port (again: either 67 or =
68, depending on your relay implmenetation.&nbsp; Most signficantly it =
will probably not be 2000).&nbsp; Then the relay would need to have =
enough memory to recall that this response is associated with a certain =
request and look up what the original port number was.&nbsp; In =
addition, it would have to remember this port for a time since the =
relay may be relaying to multiple DHCP services and you would want all =
potential responses to be forwarded back to the client.</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C53C46.69796D70--


--===============1950691867==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1950691867==--



From dhcwg-bounces@ietf.org  Fri Apr  8 11:26:55 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03011
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:26:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvWW-0002yW-Ku
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:35:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJvNF-0007P1-8E; Fri, 08 Apr 2005 11:26:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJvND-0007OV-7M
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 11:26:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02478
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 11:26:16 -0400 (EDT)
Received: from fivedots.coe.psu.ac.th ([202.12.73.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJvV6-0002mS-PW
	for dhcwg@ietf.org; Fri, 08 Apr 2005 11:34:31 -0400
Received: from delta.coe.psu.ac.th ([172.30.0.98] helo=delta.noi.kre.to)
	by fivedots.coe.psu.ac.th with esmtp (Exim 3.36 #1 (Debian))
	id 1DJvM2-00031V-00; Fri, 08 Apr 2005 22:25:06 +0700
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.11/8.11.6) with ESMTP id j38FOvWs010564;
	Fri, 8 Apr 2005 22:24:58 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM? 
In-Reply-To: <42567D63.4060002@thekelleys.org.uk> 
References: <42567D63.4060002@thekelleys.org.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 08 Apr 2005 22:24:56 +0700
Message-ID: <22584.1112973896@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

    Date:        Fri, 08 Apr 2005 13:47:31 +0100
    From:        Simon Kelley <simon@thekelleys.org.uk>
    Message-ID:  <42567D63.4060002@thekelleys.org.uk>

  | The problem is this: suppose I want to use DHCPINFORM to get
  | configuration information for an non-privileged, user space application;
  | a good example would be a web browser doing WPAD via DHCP.

What you're trying to accomplish is a good idea (more applications should
use DHCP derived data for their configuration, where that is possible),
but I don't think you're going about it the right way.

  | The problem is with use of port 67. A non-privileged application cannot
  | bind port 67 so it must be set-uid root or moral equivalent. Even then,
  | a DHCP client is likely to have port 67 bound for the purpose of lease
  | renewals, so an application cannot use it.

Yes, and that's a good thing.   I really don't think it is a great idea
to have every application that needs some config into to go making separate
requests to the DHCP server (and most likely, over and over again, as the
application, or a new instance of it, is started, 30 times a second...)

Rather than modifying DHCP to allow a non-standard port to be used, a
better solution to me seems to be to modify your dhcp client to allow
applications to register interest in particular DHCP options.   Then,
the dhcp server can request those options along with everything else.
If a new request appears, that wasn't known previously, the dhcp client
can decide to make a DHCPINFORM request and get the data - once - after
that, the data just gets refreshed as usual.

That includes, being fetched in advance, before the application starts,
even if that sometimes means that the dhcp client fetches data that no
application happens to need to use (this time).   If an application has
ever requested a DHCP option, the client may as well always fetch that
data (which costs very little) into the future, just in case the application
runs again.

All that is needed then is an API between the application (and applications
in general) and the DHCP client to allow data to be requested, and for the
results to be made available - which isn't something that needs any IETF
action.

kre

ps: I see that Andre Kostur has sent a rather similar reply while I have
been typing this one...


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


From dhcwg-bounces@ietf.org  Fri Apr  8 11:42:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04176
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:42:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvdw-0003Wu-T6
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:43:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJvNR-0007TS-70; Fri, 08 Apr 2005 11:26:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJvNN-0007S5-0z
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 11:26:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02623
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 11:26:25 -0400 (EDT)
Received: from cpc4-cmbg4-4-0-cust135.cmbg.cable.ntl.com ([81.108.205.135]
	helo=thekelleys.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvRc-0002Wi-Co
	for dhcwg@ietf.org; Fri, 08 Apr 2005 11:30:52 -0400
Received: from central ([192.168.0.4] helo=[127.0.0.1])
	by thekelleys.org.uk with esmtp (Exim 3.35 #1 (Debian))
	id 1DJvIf-0007MJ-00; Fri, 08 Apr 2005 16:21:37 +0100
Message-ID: <4256A11C.9000006@thekelleys.org.uk>
Date: Fri, 08 Apr 2005 16:19:56 +0100
From: Simon Kelley <simon@thekelleys.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
X-Accept-Language: en
MIME-Version: 1.0
To: "Kostur, Andre" <akostur@incognito.com>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
References: <B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
In-Reply-To: <B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit


> A few questions to ponder:
Good ones, too.

> 
> 1) Would DNS lookup of SRV records be more appropriate?  Kerberos uses 
> this mechanism, for example.
Possibly, but DHCP does have this functionality too, and it would be 
nice to have it usable. There may well be installations which have the 
ability to configure a DHCP server, but not generate private DNS zones.

> 2) Does your DHCP client already put the returned data somewhere where 
> your application could access the information, so you could simply read 
> what your original response was?  Perhaps a dhcpcd.eth0.leases file 
> (Linux?) or the registry (Win)
All the DHCP clients I know do that for a very common subset of 
configuration (DNS servers, NTP servers, maybe YP servers.) The problem 
is that to build in support for a new service, for example 
http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-dhc-proxyserver-opt-03.txt 
both the clients using the service _and_ the DHCP client have to be 
upgraded. By allowing the clients which need the information to do the 
DHCPINFORM query themselves, collateral changes to the DHCP client are 
avoided.

> 
> 3) Does your DHCP client has some sort of provision where you could ask 
> it to perform the INFORM on your behalf and return you the data?
That's a good second best. The main objection is that on Unix-like 
systems, there is no standardisation of DHCP clients, so a browser (for 
instance) wanting to do that would either have to mandate use with a 
particular DHCP client, or have redundant support for many DHCP clients.

> 
> 4) How much effort is it going to be on the part of the DHCP Relay 
> implementations to have to remember the source port of the request, and 
> to match up the response to the right request.  Recall that what would 
> end up happening (potentially) is that your client application may 
> broadcast the request (from say port 2000).  This gets picked up by a 
> relay, and it unicasts to the DHCP server (likely a different port than 
> 2000, probably either 67 or 68).  The DHCP server would then see this 
> bit set and would be "forced" to respond to the source port (again: 
> either 67 or 68, depending on your relay implmenetation.  Most 
> signficantly it will probably not be 2000).  Then the relay would need 
> to have enough memory to recall that this response is associated with a 
> certain request and look up what the original port number was.  In 
> addition, it would have to remember this port for a time since the relay 
> may be relaying to multiple DHCP services and you would want all 
> potential responses to be forwarded back to the client.
> 

I think it would be fine to specify that the flag is only valid in DHCP 
requests which are unicast directly to a DHCP server, so there should be 
no implications for relay agents.

Cheers,

Simon.

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


From dhcwg-bounces@ietf.org  Fri Apr  8 11:45:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04864
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:45:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvoU-0004Mf-47
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:54:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJvd9-00035z-Jb; Fri, 08 Apr 2005 11:42:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJvd7-00034p-Aj
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 11:42:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04304
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 11:42:40 -0400 (EDT)
Received: from cpc4-cmbg4-4-0-cust135.cmbg.cable.ntl.com ([81.108.205.135]
	helo=thekelleys.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvb4-0003Ka-WC
	for dhcwg@ietf.org; Fri, 08 Apr 2005 11:40:40 -0400
Received: from central ([192.168.0.4] helo=[127.0.0.1])
	by thekelleys.org.uk with esmtp (Exim 3.35 #1 (Debian))
	id 1DJvS6-0007NN-00; Fri, 08 Apr 2005 16:31:22 +0100
Message-ID: <4256A365.9080102@thekelleys.org.uk>
Date: Fri, 08 Apr 2005 16:29:41 +0100
From: Simon Kelley <simon@thekelleys.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
X-Accept-Language: en
MIME-Version: 1.0
To: Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
References: <42567D63.4060002@thekelleys.org.uk>
	<200504081632.57157.budm@weird-solutions.com>
In-Reply-To: <200504081632.57157.budm@weird-solutions.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Bud Millwood wrote:
> On Friday 08 April 2005 14:47, Simon Kelley wrote:
> 
>>I just started thinking about using DHCP for automatic configuration of
>>proxy addresses and I've hit a problem and come up with a solution.
> 
> 
> <snip>
> 
>>The proposed solution to this to define one the MBZ bits in the header
>>flags as "honour source address". If this bit is set, then the DHCP
>>server will not reply to the address in ciaddr and port 67, but instead
>>use the source address and port of the UDP packet carrying the
>>DHCPINFORM. Now, a user application can set this bit in a DHCPINFORM
>>sent from a non-privilged UDP socket, bound to an ephemeral port, and
>>the answer will be send back to the same socket.
> 
> 
> Our DHCP server responds to the source port you're originating from, 
> regardless of whether it's the "valid" port 68. (I think you mean port 68 in 
> the above excerpt, that's the port the client should use)
I do mean port 68, my mistake.
> 
> I know there are others on this list that don't think that is appropriate 
> behavior, but I personally felt like it was a reasonable enough thing to do. 
> Besides, you can override that behavior at the server.

I guess it's valid unless there  DHCP clients out there which _don't_ 
set the source port in the UDP headers if their requests to 68, or if 
such clients are RFC non-compliant.

> 
> If you want to introduce a flag that says "honor the source address", then 
> basically you're entrusting the client to not misuse that (such as a 
> user-mode application trying to spoof another node). There's no difference 
> between entrusting that to the client using a flag, or simply having the 
> server respond to the port the query originated from. Either way, you're 
> trusting the client.

It may be useful to be able to make a DHCPINFORM query on behalf of 
another node, I'm not sure.


Cheers,

Simon.

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


From dhcwg-bounces@ietf.org  Fri Apr  8 11:48:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05177
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 11:48:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJvrR-0004WA-BY
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 11:57:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJvcv-000307-9Y; Fri, 08 Apr 2005 11:42:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJvct-0002zF-7y
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 11:42:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04133
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 11:42:26 -0400 (EDT)
Received: from chimera.incognito.com ([206.172.52.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJvf2-0003YS-Uf
	for dhcwg@ietf.org; Fri, 08 Apr 2005 11:44:47 -0400
Received: from [206.172.52.116] (helo=HOMER.incognito.com.)
	by chimera.incognito.com with esmtp (Exim 4.34)
	id 1DJvW3-0002oS-AW; Fri, 08 Apr 2005 08:35:28 -0700
Received: by homer.incognito.com with Internet Mail Service (5.5.2653.19)
	id <GTVFW31Z>; Fri, 8 Apr 2005 08:34:57 -0700
Message-ID: <B34580038487494C8B7F36DA06160B870125CEA8@homer.incognito.com>
From: "Kostur, Andre" <akostur@incognito.com>
To: "'Simon Kelley'" <simon@thekelleys.org.uk>
Subject: RE: [dhcwg] An enhancement for DHCPINFORM?
Date: Fri, 8 Apr 2005 08:34:54 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: -5.8 (-----)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1728481593=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78

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.

--===============1728481593==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C53C50.8353BAC0"

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_01C53C50.8353BAC0
Content-Type: text/plain;
	charset="iso-8859-1"

> > 4) How much effort is it going to be on the part of the DHCP Relay 
> > implementations to have to remember the source port of the 
> request, and 
> > to match up the response to the right request.  Recall that 
> what would 
> > end up happening (potentially) is that your client application may 
> > broadcast the request (from say port 2000).  This gets 
> picked up by a 
> > relay, and it unicasts to the DHCP server (likely a 
> different port than 
> > 2000, probably either 67 or 68).  The DHCP server would 
> then see this 
> > bit set and would be "forced" to respond to the source port (again: 
> > either 67 or 68, depending on your relay implmenetation.  Most 
> > signficantly it will probably not be 2000).  Then the relay 
> would need 
> > to have enough memory to recall that this response is 
> associated with a 
> > certain request and look up what the original port number was.  In 
> > addition, it would have to remember this port for a time 
> since the relay 
> > may be relaying to multiple DHCP services and you would want all 
> > potential responses to be forwarded back to the client.
> > 
> 
> I think it would be fine to specify that the flag is only 
> valid in DHCP 
> requests which are unicast directly to a DHCP server, so 
> there should be 
> no implications for relay agents.

As you have mentioned in your response to my other points, your application
may not know where your DHCP server is (your application has no access to
the original lease data), so it may have no alternative than to broadcast
your INFORM.  So your INFORMs would end up passing through a relay, and
we're still in the same boat.

Also in certain environments, you may not be able to unicast to the DHCP
server directly, you may be required to pass through a relay to reach the
server.  Through various feats of handwaving, your DHCP client may not ever
know who the DHCP server really is....

------_=_NextPart_001_01C53C50.8353BAC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [dhcwg] An enhancement for DHCPINFORM?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>&gt; &gt; 4) How much effort is it going to be on the =
part of the DHCP Relay </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; implementations to have to remember the =
source port of the </FONT>
<BR><FONT SIZE=3D2>&gt; request, and </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to match up the response to the right =
request.&nbsp; Recall that </FONT>
<BR><FONT SIZE=3D2>&gt; what would </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; end up happening (potentially) is that =
your client application may </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; broadcast the request (from say port =
2000).&nbsp; This gets </FONT>
<BR><FONT SIZE=3D2>&gt; picked up by a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; relay, and it unicasts to the DHCP server =
(likely a </FONT>
<BR><FONT SIZE=3D2>&gt; different port than </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 2000, probably either 67 or 68).&nbsp; The =
DHCP server would </FONT>
<BR><FONT SIZE=3D2>&gt; then see this </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; bit set and would be &quot;forced&quot; to =
respond to the source port (again: </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; either 67 or 68, depending on your relay =
implmenetation.&nbsp; Most </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; signficantly it will probably not be =
2000).&nbsp; Then the relay </FONT>
<BR><FONT SIZE=3D2>&gt; would need </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; to have enough memory to recall that this =
response is </FONT>
<BR><FONT SIZE=3D2>&gt; associated with a </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; certain request and look up what the =
original port number was.&nbsp; In </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; addition, it would have to remember this =
port for a time </FONT>
<BR><FONT SIZE=3D2>&gt; since the relay </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; may be relaying to multiple DHCP services =
and you would want all </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; potential responses to be forwarded back =
to the client.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think it would be fine to specify that the =
flag is only </FONT>
<BR><FONT SIZE=3D2>&gt; valid in DHCP </FONT>
<BR><FONT SIZE=3D2>&gt; requests which are unicast directly to a DHCP =
server, so </FONT>
<BR><FONT SIZE=3D2>&gt; there should be </FONT>
<BR><FONT SIZE=3D2>&gt; no implications for relay agents.</FONT>
</P>

<P><FONT SIZE=3D2>As you have mentioned in your response to my other =
points, your application may not know where your DHCP server is (your =
application has no access to the original lease data), so it may have =
no alternative than to broadcast your INFORM.&nbsp; So your INFORMs =
would end up passing through a relay, and we're still in the same =
boat.</FONT></P>

<P><FONT SIZE=3D2>Also in certain environments, you may not be able to =
unicast to the DHCP server directly, you may be required to pass =
through a relay to reach the server.&nbsp; Through various feats of =
handwaving, your DHCP client may not ever know who the DHCP server =
really is....</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C53C50.8353BAC0--


--===============1728481593==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1728481593==--



From dhcwg-bounces@ietf.org  Fri Apr  8 12:19:49 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08796
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 12:19:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJwLp-0006VK-AH
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 12:28:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJwCu-0007zg-S8; Fri, 08 Apr 2005 12:19:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJwCu-0007yc-3u
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 12:19:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08777
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 12:19:38 -0400 (EDT)
Received: from fivedots.coe.psu.ac.th ([202.12.73.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJwLd-0006Ua-Jb
	for dhcwg@ietf.org; Fri, 08 Apr 2005 12:28:46 -0400
Received: from delta.coe.psu.ac.th ([172.30.0.98] helo=delta.noi.kre.to)
	by fivedots.coe.psu.ac.th with esmtp (Exim 3.36 #1 (Debian))
	id 1DJwCf-0003Xu-00; Fri, 08 Apr 2005 23:19:29 +0700
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.11/8.11.6) with ESMTP id j38GJK1B018972;
	Fri, 8 Apr 2005 23:19:21 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM? 
In-Reply-To: <4256A11C.9000006@thekelleys.org.uk> 
References: <4256A11C.9000006@thekelleys.org.uk>
	<B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 08 Apr 2005 23:19:20 +0700
Message-ID: <18861.1112977160@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: dhcwg@ietf.org, "Kostur, Andre" <akostur@incognito.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d

    Date:        Fri, 08 Apr 2005 16:19:56 +0100
    From:        Simon Kelley <simon@thekelleys.org.uk>
    Message-ID:  <4256A11C.9000006@thekelleys.org.uk>

  | That's a good second best. The main objection is that on Unix-like 
  | systems, there is no standardisation of DHCP clients, so a browser (for 
  | instance) wanting to do that would either have to mandate use with a 
  | particular DHCP client, or have redundant support for many DHCP clients.

You're planning on (suggesting) standardising something new.   Why not
standardise that (the DHCP client to application interface), instead of
a new DHCP option bit (or a new way of operating DHCP servers)?
Is it really that much harder to deal with POSIX instead of IETF?

The result would be much better - and could provide all that's necessary
to ask for an option, and get the result, without the DHCP client needing
to have any idea at all what any of it means - which avoids the problem of
needing to upgrade the DHCP client to get any new data (which currently
is really only required so the DHCP client knows what to do with the new
data when it arrives - requesting something new should not require client
upgrades, if it does, the client is already deficient and needs upgrading).

kre


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


From dhcwg-bounces@ietf.org  Fri Apr  8 13:09:56 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14047
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 13:09:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJx8L-0000Z6-2G
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 13:19:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJwrq-0001Cx-HZ; Fri, 08 Apr 2005 13:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJwrp-0001Cs-Mj
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 13:02:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13601
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 13:01:58 -0400 (EDT)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJx0b-0000Az-SC
	for dhcwg@ietf.org; Fri, 08 Apr 2005 13:11:07 -0400
Received: from [192.168.2.3] (dsl093-162-226.tus1.dsl.speakeasy.net
	[66.93.162.226]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 22FE35688B;
	Fri,  8 Apr 2005 10:01:48 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
In-Reply-To: <42567D63.4060002@thekelleys.org.uk>
References: <42567D63.4060002@thekelleys.org.uk>
Mime-Version: 1.0 (Apple Message framework v728)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F1C5BAF8-E57D-4CC2-AF8B-BC7E1B8E308F@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
Date: Fri, 8 Apr 2005 09:59:40 -0700
To: Simon Kelley <simon@thekelleys.org.uk>
X-Mailer: Apple Mail (2.728)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

It's arguably a bug in your DHCP client if you can't already get this  
information somehow.   There's no technical reason why it's not  
possible.   So I'd encourage you to pursue that solution before  
trying to write a new standard - it's something you can do yourself,  
and therefore more likely to produce fruit than a standards change,  
which requires that all DHCP server vendors change their code.


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


From dhcwg-bounces@ietf.org  Fri Apr  8 13:12:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14346
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 13:12:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJxAl-0000iM-OC
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 13:21:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJx18-0001iz-N1; Fri, 08 Apr 2005 13:11:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJx16-0001ir-H8
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 13:11:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14282
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 13:11:33 -0400 (EDT)
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJx9t-0000bo-1R
	for dhcwg@ietf.org; Fri, 08 Apr 2005 13:20:42 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 90DE7B240B; Fri,  8 Apr 2005 10:11:19 -0700 (PDT)
Date: Fri, 8 Apr 2005 10:11:19 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
Message-ID: <20050408171119.GB93017@isc.org>
References: <B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
	<4256A11C.9000006@thekelleys.org.uk>
Mime-Version: 1.0
In-Reply-To: <4256A11C.9000006@thekelleys.org.uk>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1101003383=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d


--===============1101003383==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="nVMJ2NtxeReIH9PS"
Content-Disposition: inline


--nVMJ2NtxeReIH9PS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 08, 2005 at 04:19:56PM +0100, Simon Kelley wrote:
> All the DHCP clients I know do that for a very common subset of=20
> configuration (DNS servers, NTP servers, maybe YP servers.) The problem=
=20
> is that to build in support for a new service, for example=20
> http://www.ietf.cnri.reston.va.us/internet-drafts/draft-ietf-dhc-proxyser=
ver-opt-03.txt=20
> both the clients using the service _and_ the DHCP client have to be=20
> upgraded. By allowing the clients which need the information to do the=20
> DHCPINFORM query themselves, collateral changes to the DHCP client are=20
> avoided.

how would the got-by-INFORM values be expired as changes are made?  do
you intend to track this with the dhcp client's lease times?  what if you
roam between networks and that cache data becomes invalid?

i think there could be advantages to asking applications make such
requests through a layer the dhcp client controls - it could make
informs for new options, and remember to put it on the requested
options list in future renewals or reboots.

> I think it would be fine to specify that the flag is only valid in DHCP=
=20
> requests which are unicast directly to a DHCP server, so there should be=
=20
> no implications for relay agents.

then you're back to redundant support for multiple dhcp clients in
order to divine what the dhcp server's ip address is.

--=20
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--nVMJ2NtxeReIH9PS
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iD8DBQFCVrs1cXeLeWu2vmoRAkBNAKCqAak8mxadg4OzNiq65doo5kzcLACgplds
nLp4KJZn/6br6ixzZtq52yw=
=/9LP
-----END PGP SIGNATURE-----

--nVMJ2NtxeReIH9PS--


--===============1101003383==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1101003383==--



From dhcwg-bounces@ietf.org  Fri Apr  8 13:22:31 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15469
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 13:22:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJxKU-0001G0-Gf
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 13:31:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJxBU-0006KB-Ns; Fri, 08 Apr 2005 13:22:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJxBT-0006Jt-24
	for dhcwg@megatron.ietf.org; Fri, 08 Apr 2005 13:22:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15446
	for <dhcwg@ietf.org>; Fri, 8 Apr 2005 13:22:16 -0400 (EDT)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJxKF-0001FU-UI
	for dhcwg@ietf.org; Fri, 08 Apr 2005 13:31:25 -0400
Received: from [192.168.2.3] (dsl093-162-226.tus1.dsl.speakeasy.net
	[66.93.162.226]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id C480F56881;
	Fri,  8 Apr 2005 10:22:08 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
In-Reply-To: <18861.1112977160@munnari.OZ.AU>
References: <4256A11C.9000006@thekelleys.org.uk>
	<B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
	<18861.1112977160@munnari.OZ.AU>
Mime-Version: 1.0 (Apple Message framework v728)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5282F2B2-483C-47DB-BEDA-6937A1E1BBC5@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM? 
Date: Fri, 8 Apr 2005 10:20:00 -0700
To: Robert Elz <kre@munnari.OZ.AU>
X-Mailer: Apple Mail (2.728)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Cc: "Kostur, Andre" <akostur@incognito.com>, dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

On Apr 8, 2005, at 9:19 AM, Robert Elz wrote:
> You're planning on (suggesting) standardising something new.   Why not
> standardise that (the DHCP client to application interface),  
> instead of
> a new DHCP option bit (or a new way of operating DHCP servers)?
> Is it really that much harder to deal with POSIX instead of IETF?

Robert wins the prize here for the best suggestion so far.   :')



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


From dhcwg-bounces@ietf.org  Fri Apr  8 15:41:52 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00261
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 15:41:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJzVM-0000Jr-On
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 15:51:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJz6b-0007rr-PY; Fri, 08 Apr 2005 15:25:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJz6Y-0007rP-Mi; Fri, 08 Apr 2005 15:25:22 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26117;
	Fri, 8 Apr 2005 15:25:21 -0400 (EDT)
Message-Id: <200504081925.PAA26117@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 08 Apr 2005 15:25:21 -0400
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dhcpv6-remoteid-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2

--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		: DHCPv6 Relay Agent Remote ID Option
	Author(s)	: B. Volz
	Filename	: draft-ietf-dhc-dhcpv6-remoteid-00.txt
	Pages		: 6
	Date		: 2005-4-8
	
This memo defines a new Relay Agent Remote-ID option for the Dynamic
   Host Configuration Protocol for IPv6 (DHCPv6).  This option is the
   DHCPv6 equivalent for the Dynamic Host Configuration Protocol for
   IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified
   in RFC 3046.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-remoteid-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-dhcpv6-remoteid-00.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-dhcpv6-remoteid-00.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: <2005-4-8155844.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-dhcpv6-remoteid-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dhc-dhcpv6-remoteid-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-8155844.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From dhcwg-bounces@ietf.org  Fri Apr  8 15:57:38 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05978
	for <dhcwg-web-archive@ietf.org>; Fri, 8 Apr 2005 15:57:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJzkd-0002nj-6D
	for dhcwg-web-archive@ietf.org; Fri, 08 Apr 2005 16:06:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJz6m-0007wY-6T; Fri, 08 Apr 2005 15:25:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJz6i-0007vy-Dr; Fri, 08 Apr 2005 15:25:32 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26147;
	Fri, 8 Apr 2005 15:25:31 -0400 (EDT)
Message-Id: <200504081925.PAA26147@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Fri, 08 Apr 2005 15:25:30 -0400
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dhcpv6-subid-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db

--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		: DHCPv6 Relay Agent Subscriber-ID Option
	Author(s)	: B. Volz
	Filename	: draft-ietf-dhc-dhcpv6-subid-00.txt
	Pages		: 6
	Date		: 2005-4-8
	
This memo defines a new Relay Agent Subscriber-ID option for the
   Dynamic Host Configuration Protocol for IPv6 (DHCPv6).  The option
   allows a DHCPv6 relay agent to associate a stable "Subscriber-ID"
   with DHCPv6 client messages in a way that is independent of the
   client and of the underlying physical network infrastructure.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-subid-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-dhcpv6-subid-00.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-dhcpv6-subid-00.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: <2005-4-8155855.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-dhcpv6-subid-00.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-dhc-dhcpv6-subid-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-8155855.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From dhcwg-bounces@ietf.org  Sun Apr 10 10:59:12 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25357
	for <dhcwg-web-archive@ietf.org>; Sun, 10 Apr 2005 10:59:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DKe3I-0002AP-UK
	for dhcwg-web-archive@ietf.org; Sun, 10 Apr 2005 11:08:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DKdrF-0001ra-4B; Sun, 10 Apr 2005 10:56:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DKdrD-0001q0-JR
	for dhcwg@megatron.ietf.org; Sun, 10 Apr 2005 10:56:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25187
	for <dhcwg@ietf.org>; Sun, 10 Apr 2005 10:56:13 -0400 (EDT)
Received: from cpc4-cmbg4-4-0-cust135.cmbg.cable.ntl.com ([81.108.205.135]
	helo=thekelleys.org.uk) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DKe0O-00024X-D5
	for dhcwg@ietf.org; Sun, 10 Apr 2005 11:05:45 -0400
Received: from desk.thekelleys.org.uk ([192.168.0.3] helo=thekelleys.org.uk)
	by thekelleys.org.uk with esmtp (Exim 3.35 #1 (Debian))
	id 1DKdqx-0001Qo-00; Sun, 10 Apr 2005 15:55:59 +0100
Message-ID: <42593E9C.3040402@thekelleys.org.uk>
Date: Sun, 10 Apr 2005 15:56:28 +0100
From: Simon Kelley <simon@thekelleys.org.uk>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB;
	rv:1.6) Gecko/20040413 Debian/1.6-5
X-Accept-Language: en
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] An enhancement for DHCPINFORM?
References: <4256A11C.9000006@thekelleys.org.uk>
	<B34580038487494C8B7F36DA06160B870125CEA3@homer.incognito.com>
	<18861.1112977160@munnari.OZ.AU>
	<5282F2B2-483C-47DB-BEDA-6937A1E1BBC5@nominum.com>
In-Reply-To: <5282F2B2-483C-47DB-BEDA-6937A1E1BBC5@nominum.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, "Kostur, Andre" <akostur@incognito.com>,
        Robert Elz <kre@munnari.OZ.AU>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 2.6 (++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

Ted Lemon wrote:
> On Apr 8, 2005, at 9:19 AM, Robert Elz wrote:
> 
>> You're planning on (suggesting) standardising something new.   Why not
>> standardise that (the DHCP client to application interface),  instead of
>> a new DHCP option bit (or a new way of operating DHCP servers)?
>> Is it really that much harder to deal with POSIX instead of IETF?
> 
> 
> Robert wins the prize here for the best suggestion so far.   :')
> 
> 
> 

Agreed: this looks like my best option. I'm not sure about POSIX, but I 
found that the people at freedesktop.org are starting to think along 
these lines. The NetworkManager project is playing in the correct space, 
and I guess that eventually they will get around to supplying a set of 
methods to query arbitrary network configuration over the D-bus.

Clearly, this is likely to happen before a DHCP server spec change could 
be made and rolled out to  a substantial proportion of the world's DHCP 
servers. I shall take my stall over there and see where I can help.

In the meantime, I would suggest that there's nothing to be lost (except 
one bit in the flags field) in adopting my suggestion, next time the 
DHCP spec is updated. Please remember me then!

Thanks for all the helpful suggestions.

Cheers,

Simon.




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


From dhcwg-bounces@ietf.org  Mon Apr 11 11:17:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21438
	for <dhcwg-web-archive@ietf.org>; Mon, 11 Apr 2005 11:17:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL0oj-0002Ti-QG
	for dhcwg-web-archive@ietf.org; Mon, 11 Apr 2005 11:27:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL0Wc-0000D0-6U; Mon, 11 Apr 2005 11:08:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL0WX-0000CX-Bq; Mon, 11 Apr 2005 11:08:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20622;
	Mon, 11 Apr 2005 11:08:22 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL0fw-0002CY-A7; Mon, 11 Apr 2005 11:18:08 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1DL0WW-0000jv-I2; Mon, 11 Apr 2005 11:08:24 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1DL0WW-0000jv-I2@newodin.ietf.org>
Date: Mon, 11 Apr 2005 11:08:24 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: 'Vendor-Specific Information Suboption for the
 DHCP Relay Agent Option' to Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f

The IESG has received a request from the Dynamic Host Configuration WG to 
consider the following document:

- 'Vendor-Specific Information Suboption for the DHCP Relay Agent Option '
   <draft-ietf-dhc-vendor-suboption-00.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-04-25.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-suboption-00.txt


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


From dhcwg-bounces@ietf.org  Mon Apr 11 15:16:03 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11094
	for <dhcwg-web-archive@ietf.org>; Mon, 11 Apr 2005 15:16:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DL4Xd-0001tB-DL
	for dhcwg-web-archive@ietf.org; Mon, 11 Apr 2005 15:25:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DL4Gb-00052E-Nn; Mon, 11 Apr 2005 15:08:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DL4Ga-00051n-Iw
	for dhcwg@megatron.ietf.org; Mon, 11 Apr 2005 15:08:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09931
	for <dhcwg@ietf.org>; Mon, 11 Apr 2005 15:08:02 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DL4Pq-0001f1-BZ
	for dhcwg@ietf.org; Mon, 11 Apr 2005 15:17:49 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 11 Apr 2005 15:07:52 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3BJ7njI006689; 
	Mon, 11 Apr 2005 15:07:50 -0400 (EDT)
Received: from [161.44.65.241] ([161.44.65.241])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQN36070;
	Mon, 11 Apr 2005 15:07:48 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Content-Type: text/plain
Date: Mon, 11 Apr 2005 15:07:53 -0400
Message-Id: <1113246473.15042.46.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: Stig Venaas <Stig.Venaas@uninett.no>
Subject: [dhcwg] dhc WG last call on <draft-ietf-dhc-ddns-resolution-08.txt>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit


This message announces a WG last call on "Resolution of DNS
Name Conflicts among DHCP Clients"
<draft-ietf-dhc-ddns-resolution-08.txt>.  The last call will
conclude at 1700 EST (USA) on 2005-04-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.  Lack of discussion does not represent positive
support.  If there is no expression of support for
acceptance during the WG last call, the document will not be
advanced to the IESG.

There are options in DHCP that can be used for transmitting
information about updating DNS. However, these do not
explicitly control updating the name to address and address
to name mappings maintained in the DNS, as performed by
hosts acting as DHCP clients and servers.
draft-ietf-dhc-ddns-resolution-08.txt describes techniques
for the resolution of DNS name conflicts among DHCP clients
and servers.  This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-ddns-
resolution-08.txt

- Ralph Droms 


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


From dhcwg-bounces@ietf.org  Wed Apr 13 11:47:06 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07566
	for <dhcwg-web-archive@ietf.org>; Wed, 13 Apr 2005 11:47:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLkEv-0002Ra-GE
	for dhcwg-web-archive@ietf.org; Wed, 13 Apr 2005 11:57:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLjtW-0006tD-GO; Wed, 13 Apr 2005 11:35:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLjtV-0006qx-OG
	for dhcwg@megatron.ietf.org; Wed, 13 Apr 2005 11:35:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06605
	for <dhcwg@ietf.org>; Wed, 13 Apr 2005 11:34:59 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLk3B-000261-1T
	for dhcwg@ietf.org; Wed, 13 Apr 2005 11:45:10 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 13 Apr 2005 08:34:51 -0700
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3DFYl7T014331
	for <dhcwg@ietf.org>; Wed, 13 Apr 2005 08:34:47 -0700 (PDT)
Received: from [161.44.65.241] ([161.44.65.241])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQP01756;
	Wed, 13 Apr 2005 11:34:47 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Content-Type: text/plain
Date: Wed, 13 Apr 2005 11:34:53 -0400
Message-Id: <1113406494.5559.12.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] [Fwd: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt]
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

FYI, for those interested in IPv6 DHCP/RA interaction...

- Ralph

-------- Forwarded Message --------
> From: Brian Haberman <brian@innovationslab.net>
> To: IPv6 WG <ipv6@ietf.org>
> Subject: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
> Date: Wed, 13 Apr 2005 10:09:12 -0400
> This starts a 2 week IPv6 WG Last Call for advancing:
> 
> 	Title		: Considerations on M and O Flags of IPv6 Router Advertisement
> 	Author(s)	: S. Park, et al.
> 	Filename	: draft-ietf-ipv6-ra-mo-flags-01.txt
> 	Pages	: 13
> 	Date		: 2005-3-30
> 	
> as a Proposed Standard.  Substantive comments should be directed
> to the mailing list.  Editorial comments can be sent to the document
> editor.  This Last Call will end on April 27, 2005.
> 
> Regards,
> Bob & Brian
> IPv6 WG co-chairs
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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


From dhcwg-bounces@ietf.org  Wed Apr 13 16:00:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28633
	for <dhcwg-web-archive@ietf.org>; Wed, 13 Apr 2005 16:00:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLoCN-0001R8-B6
	for dhcwg-web-archive@ietf.org; Wed, 13 Apr 2005 16:10:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLnnR-000559-67; Wed, 13 Apr 2005 15:45:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLnnN-00054S-48; Wed, 13 Apr 2005 15:45:05 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27147;
	Wed, 13 Apr 2005 15:45:03 -0400 (EDT)
Message-Id: <200504131945.PAA27147@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 13 Apr 2005 15:45:03 -0400
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dna-ipv4-11.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87

--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		: Detection of Network Attachment (DNA) in IPv4
	Author(s)	: B. Aboba
	Filename	: draft-ietf-dhc-dna-ipv4-11.txt
	Pages		: 17
	Date		: 2005-4-13
	
The time required to detect movement (or lack of movement) between
   subnets, and to obtain (or continue to use) a valid IPv4
   configuration may be significant as a fraction of the total handover
   latency in moving between points of attachment.  This document
   specifies a procedure for optimizing the detection of network
   attachment and IPv4 configuration in order to decrease the handover
   latency in moving between points of attachment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dna-ipv4-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-dna-ipv4-11.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-dna-ipv4-11.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: <2005-4-13162012.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-dna-ipv4-11.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-dhc-dna-ipv4-11.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-4-13162012.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From dhcwg-bounces@ietf.org  Fri Apr 15 08:28:04 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25303
	for <dhcwg-web-archive@ietf.org>; Fri, 15 Apr 2005 08:28:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMQ5k-00046c-Ur
	for dhcwg-web-archive@ietf.org; Fri, 15 Apr 2005 08:38:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMPim-0008KM-H3; Fri, 15 Apr 2005 08:14:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMPil-0008Jq-0s
	for dhcwg@megatron.ietf.org; Fri, 15 Apr 2005 08:14:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23746
	for <dhcwg@ietf.org>; Fri, 15 Apr 2005 08:14:42 -0400 (EDT)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMPso-0003Xk-Mx
	for dhcwg@ietf.org; Fri, 15 Apr 2005 08:25:15 -0400
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 331241 for dhcwg@ietf.org;
	Fri, 15 Apr 2005 08:11:17 -0400
Mime-Version: 1.0
Message-Id: <p0620071dbe855f5c64d3@[192.168.2.2]>
Date: Fri, 15 Apr 2005 08:13:22 -0400
To: dhcwg@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Subject: [dhcwg] AD Review of draft-ietf-dhc-bcmc-options-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672


Hi All,

I have completed my AD Review of draft-ietf-dhc-bcmc-options-00.txt. 
I have several questions on this document, and there are several 
issues that will need to be resolved before the document is ready for 
review by the IESG.

I'll be on vacation for the next week (April 16th-24th), so I won't 
respond over the next several days.  But, perhaps the WG can reach 
some agreement on how to address the issues that I have listed below.

IMO, this document did not received adequate review by the WG before 
submission, and I would really appreciate it some members of this WG 
could review the document and see if there are other issues that I 
failed to catch.

Thanks,
Margaret

---

General Comments:

The editorial level of this document is not very high.  There are
several places where there are tense conflicts and/or strange wording.
I've marked some of them below, but not all of them.  It might be good
to have someone take a quick editing pass at this document while you
are making changes to address my other comments below.  That would
likely speed up other parts of the process.

Ralph and Stig, this document seems to violate the I-D guidelines in
several places (lines over 80 characters, use of non-example domain
names).  Could you please do a nits check and send the violations to
the authors.  I've marked the violations that I notice, but I may not
have caught all of them.  It would be good if the next version
complies with the I-D guidelines.  See:

http://www.ietf.org/ietf/1id-guidelines.html

Some of the issues I've marked below may be the result of a quick
merger of the IPv4 document and the IPv6 document.  There are places
where the document says IPv4-specific or IPv6-specific things where it
isn't clear to me why the text would not apply to the other version.
Also, there is duplication of text in some places.

Specific Comments (marked with >>):

Abstract

    This document defines new options for Broadcast and Multicast Service
    controller discovery in an IP network.  Broadcast service is being
    developed for 3G wireless networks.  Users of the service interact

>>  You need to expand the 3G acronym and make it clearer to which 3G
    networks you are referring.  Maybe "third generation (3G) cellular
    telephone networks" ?

    with a controller in the network to derive informations that are

>>  s/informations that are/information that is

>>  Does the user (a human being) really interact with the server?
    Or is the interaction handled automatically by the MN or MT
    device?

    required to receive broadcast service.  Dynamic Host Configuration
    Protocol can be used to configure the controller IPv4 addresses or
    fully qualified domain names in the user's devices.  This document
    defines the related options and option codes.

>>  I think that you mean that DHCPv4 or DHCPv6 may be used to configure
>>  a user's device to access a particular broadcast controller.  However
>>  the sentence is ambiguous, as it could also mean that DHCP is used
>>  to configure the IPv4 address of the broadcast controller _and_ to
>>  configure the broadcast controller's domain name on the user's
>>  device.
>>
>>  Why just an IPv4 address or domain name?  What about an IPv6 address?

    While DHCP offers necessary mechanisms for device configuration, it
    lacks the information elements required to configure a mobile device
    to support BCMCS.  This memo is an effort to define the extensions
    needed for DHCP to provide necessary configuration information to a
    mobile device in a BCMCS network.

>>  s/this memo is an effort to define/this memo defines

    DHCP is being used in 3GPP2, for example, to assist with the
    discovery of the BCMCS Controller in a mobile operators IP network.

>>  s/mobile operators/mobile operator's

    The BCMCS includes a controller component that is responsible for
    managing the service via interaction with the users and other network
    entities.

>>  Does the BCMCS really interact with the users?  Or with the mobile
>>  terminal, for instance?  We have several documents in the IETF
>>  context that describe the 3GPP architecture, and it might make sense
>>  to use more precise terminology from that architecture here.  If
>>  the terminology differs between 3GPP and 3GPP2, then a terminology
>>  section might be called for in this draft, so that more precise
>>  terms can be used.

    In order to allow the users to discover the broadcast controllers,
    the clients request for appropriate option codes from the DHCP
    servers using Parameter Request List option.  The DHCP servers need
    to return the corresponding configuration options that carry either
    broadcast and multicast service controller's IP address or fully
    qualified domain name based on configuration.  The motivation for
    this document is to define the necessary options and option codes.

>>  s/The motivation for this document is to define/This document defines/

    The user interacts with the Controller to request for
    broadcast/multicast program information from the network (e.g.,

>>  s/to request for/to request

    scheduled time, multicast IP address, port numbers).  The User may
    also be authenticated by the Controller while downloading the
    relevant program security related information (such as encryption
    key).  These interactions happen via HTTP and XML.  There may be more
    than one controller in the network.  The user should discover the
    appropriate controller to request the relevant program information.
    For details of Broadcast and Multicast Service operation in 3GPP2,
    see [BCMCS].

>>  What do you mean by "the user should discover the appropriate
>>  controller to request the relevant program information"?  Does
>>  the actual user (a human being) get a list of broadcast controllers
>>  to choose from?  How would he/she be expected to make that choice?

4.  Broadcast Service Controller Options

    This section defines the configuration option for the controller of
    Broadcast Service.  The Configuration Option contains the IPv4
    address or of the IPv4 address or the fully qualified domain names of
    the broadcast service controller.

>>  "the IPv4 address or of the IPv4 address" ??

    Clients MUST support compression according to the encoding in Section
    4.1.4 of "Domain Names - Implementation And Specification [RFC1035].

    Since the domain names are supposed to be different domains,
    compression will likely have little effect, however.

>>  Why make it a MUST to support something that will have little effect?

    The DHCP option for this encoding has the following format:


            Code  Len   FQDN(s) of Broadcast Controller
          +-----+-----+-----+-----+-----+-----+-----+--
          | TBD |  n  |  s1 |  s2 |  s3 |  s4 | s5  |  ...
          +-----+-----+-----+-----+-----+-----+-----+--


    An example case when two controller domain names e.g.
    bcmc1.carrier1.com, bcmc2.carrier1.com are returned without 
compression will be:

>>  Please eliminate lines over 80 characters long.

>>  You also need to use the correct example domain names (i.e. example.com)
    in examples.  See RFC 2606.  Use of other domain names as examples
    is not allowed in RFCs.

4.3  Broadcast Service Controller IPv4 Address Option

    If the 'enc' byte has a value of 1, the encoding byte is followed by
    a list of IPv4 addresses indicating broadcast controller IPv4
    addresses.

>>  What is the 'enc' byte?  And is this a DHCPv4 or DHCPv6 option?

    The controllers MUST be listed in order of preference.
    Its minimum length is 5, and the length MUST be a multiple of 4 plus
    one.  The DHCP option for this encoding has the following format:

>>  Why would the minimum length by 5?  Why would the length be a
    multiple of 4 plus one?  Are you talking about the value of
    "len" or the overall length of the option?  I may be somewhat
    confused, but I think that "len" will be a multiple of four
    and that the overall length will be a multiple of four plus
    two.

4.4  Broadcast Service Controller IPv6 Address Option

    This DHCPv6 option MUST carry one or more 128-bit IPv6 address(es) of
    the Broadcast Service Controller in a operators network.

>>  Apparently there is an option for IPv6 addresses, so why isn't it
    mentioned in the abstract and introduction?

5.  Consideration for Client Operation for DHCPv6

    A client MAY request either or both of the Broadcast Service
    Controller Domain Name List and the IPv6 Address options in the
    Options Request Option (ORO) as described in [RFC3315].

    If a client receives both the Broadcast Service Controller Domain
    Name List and IPv6 Address options, it SHOULD use the Domain Name
    List option.  In this case, the client MAY use the Broadcast Service
    Controller IPv6 Address option only if, no server in the Broadcast
    Service Controller Domain Name List can be resolved or reached.

>>  s/only if, no/only if no/

>>  This wording is strange WRT the RFC 2119 language.  If you should
    do something, it is odd to say that you MAY do something else
    "only if" some other condition...  Are you trying to say that
    the client MUST use the Domain List Option unless no server in
    the Brodcast Service Controller Domain Name list can be resolve
    or reached?  Or are you trying to leave open the possibility that
    the client might decide to use the IP addresses instead of the
    domain names in some other case?

>>  Is there a reason why this is only a consideration for DHCPv6
    clients?

6.  Consideration for Server Operation

[..]

    Client sends in ORO     Domain Name List        IPv6 Address List
    __________________________________________________________________

    Neither option          SHOULD                  MAY
    Domain Name List        MUST                    MAY
    IPv6 Address            MAY                     MUST
    Both options            SHOULD                  MAY

>>  Is this intended only to be considerations for DHCPv6 servers?
    What do DHCPv4 servers do in these cases?  Is it really the case
    that DHCPv6 servers SHOULD send the Domain Name List option when it
    isn't requested by the client?  Why?

7.  Security Considerations

    The security considerations in the base DHCP specs [RFC2131] and
    [RFC3315] apply.  An attacker may change information of the Broadcast
    Service Controller in packets that are in-tranist from DHCP server to
    the MN, if integrity protection is not in place.  In that event, the
    user of the Broadcast service may be diverted to a rogue broadcast
    service controller.  In the absence of a mutual authentication
    procedure between MN and the Broadcast controller, the MN may receive
    wrong or fraudulent information about Broadcast Service.

>>  So what is required to prevent this?  Is implementation of specific
    security features a MUST for this specification?  Or is it presumed
    to be safe to use this option in networks with certain properties?

8.  IANA Considerations

    The option code for Broadcast Service Controller options MUST be
    assigned by IANA.

>>  I think that there are four option codes that need to be assigned,
    and you should be specific about what they are.  You also need to
    specify the registries in which they should be assigned.

10  Normative References

    [BCMCS]    3GPP2, www.3gpp2.org, "X.S0022, Broadcast and Multicast
               Service in  cdma2000 Wireless IP Network.", February 2005.

>>  I can't find this document.  Both X.S0021 and X.S0023 are listed on
    the web site, but not X.S0022.  Where do I find it?

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


From dhcwg-bounces@ietf.org Wed Apr 20 23:51:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOSiY-0004g7-Gb; Wed, 20 Apr 2005 23:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOSiX-0004g2-AM
	for dhcwg@megatron.ietf.org; Wed, 20 Apr 2005 23:51:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27372
	for <dhcwg@ietf.org>; Wed, 20 Apr 2005 23:51:03 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOStr-00024t-26
	for dhcwg@ietf.org; Thu, 21 Apr 2005 00:02:49 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 21 Apr 2005 00:02:03 -0400
X-IronPort-AV: i="3.92,118,1112587200"; 
	d="scan'208"; a="45502080:sNHT26417824"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3L3opdr016747; 
	Wed, 20 Apr 2005 23:50:51 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Wed, 20 Apr 2005 23:50:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Apr 2005 23:50:49 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB211713F0@xmb-rtp-20a.amer.cisco.com>
Thread-Topic: Request DHC WG Last Call on draft-ietf-dhc-dhcpv6-subid-00.txt &
	draft-ietf-dhc-dhcpv6-remoteid-00.txt
Thread-Index: AcVGJU6SDY0NgSyQRd6C53DRUerdAg==
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 21 Apr 2005 03:50:50.0783 (UTC)
	FILETIME=[4F48C2F0:01C54625]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
Cc: Stig Venaas <Stig.Venaas@uninett.no>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: [dhcwg] Request DHC WG Last Call on
	draft-ietf-dhc-dhcpv6-subid-00.txt &
	draft-ietf-dhc-dhcpv6-remoteid-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

I'd like to request a DHC WG Last Call on
draft-ietf-dhc-dhcpv6-subid-00.txt &
draft-ietf-dhc-dhcpv6-remoteid-00.txt. As these are DHCPv6 equivalents
for existing DHCPv4 relay agent options, they are (I believe) fairly
straight forward options.

Please let the DHC WG chairs (& WG) know if you have any objections to
Last Calling these drafts.

- Bernie

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



From dhcwg-bounces@ietf.org Tue Apr 26 11:13:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQRl7-0001Xj-AM; Tue, 26 Apr 2005 11:13:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQRl6-0001Xb-MB; Tue, 26 Apr 2005 11:13:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16780;
	Tue, 26 Apr 2005 11:13:54 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQRxX-0006xA-V7; Tue, 26 Apr 2005 11:26:50 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 26 Apr 2005 11:25:53 -0400
X-IronPort-AV: i="3.92,132,1112587200"; 
	d="scan'208"; a="46141947:sNHT27184592"
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3QFDhRQ019885; 
	Tue, 26 Apr 2005 11:13:43 -0400 (EDT)
Received: from [161.44.65.172] ([161.44.65.172])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQV53702;
	Tue, 26 Apr 2005 11:13:42 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org, ipv6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Tue, 26 Apr 2005 11:16:40 -0400
Message-Id: <1114528600.6278.16.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA16780
Cc: 
Subject: [dhcwg] [Fwd: Re: IPv6 WG Last
	Call:draft-ietf-ipv6-ra-mo-flags-01.txt]
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Forwarded to include dhc WG in conversation about M/O flags.

- Ralph

-------- Forwarded Message --------
> From: JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinmei@isl.=
rdc.toshiba.co.jp>
> To: Pekka Savola <pekkas@netcore.fi>
> Cc: IPv6 WG <ipv6@ietf.org>
> Subject: Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
> Date: Tue, 26 Apr 2005 17:18:24 +0900
> >>>>> On Fri, 22 Apr 2005 16:30:02 +0300 (EEST),=20
> >>>>> Pekka Savola <pekkas@netcore.fi> said:
>=20
> >> 2. allow a host to fall-back to Information Configuration Behaviour =
in
> >> such a case.  This is not 100% compliant with the DHCPv6
> >> specification, though.
> >>=20
> >> 3. make small updates on the DHCPv6 specifications (RFC3315 and
> >> RFC3736) to help mitigate or avoid the problematic scenario.
> > [...]
> >> Ideally, I think resolution 3 is the way to go and should be include=
d
> >> in this document (we'll then need to DHCPv6 updates at the dhc wg, o=
f
> >> course).  But if it's too tough, resolution 2 can be a workaround wi=
th
> >> careful wording.
>=20
> > I think the DHC WG should be part of the resolution of this issue=20
> > whether it's 2 or 3.  In particular, we should get their permission t=
o=20
> > say that implementations can do 2) if they want to, and can then mayb=
e=20
> > just refer to DHC WG (or some initial document) for 3).
>=20
> I agree in that we should make consensus on this with dhc folks.
> (Should we continue this discussion copying the dhc list?)
>=20
> Meanwhile, after re-reading the DHCPv6 specification, I thought I had
> not 100% correct about compliance with the DHCPv6 spec.  As far as I
> understand it, RFC3315 does not prohibit the client from performing
> Information-request/Reply exchanges in parallel with
> Solicit/Advertise/Request/Reply/... exchanges.  So, for example, the
> following behavior should be valid in terms of RFC3315:
>=20
>   - the client starts Host Configuration Behaviour
>     (Solicit/Advertise/... exchanges)
>   - unfortunately, it does not get any responses for a while
>   - the client then starts Information Configuration Behaviour *in
>     parallel with* Host Configuration Behaviour
>   - if there is a DHCPv6 server that only implements/enables the
>     RFC3736 subset (i.e., Information Configuration Behaviour), the
>     client will at least get other configuration information
>=20
> However, this approach will cause additional issues:
>=20
>   + this approach may break the sense of RFC2462 (not bis), since it
>     does not seem to expect Host/Information Configuration Behaviour
>     can take place simultaneously.  For example, it says in Section
>     5.5.3:
>=20
>       If the value of OtherConfigFlag changes from FALSE to TRUE, the
>       host should invoke the stateful autoconfiguration protocol,
>       requesting information (excluding addresses if ManagedFlag is
>                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>       set to FALSE).
>       ^^^^^^^^^^^^
>     I personally think we can accept the change in the sense as a part
>     of clarification with the reality of concrete protocol
>     specifications.
>=20
>   + if, for example, full-service DHCPv6 servers are just temporarily
>     down when the client starts Host Configuration Behaviour, the
>     client will eventually get configuration information from both
>     Host Configuration Behaviour and Information Configuration
>     Behaviour and will face the issue about how to integrate or
>     prioritize the two sets of information (there may even be
>     inconsistency between those).
>=20
>     I personally think this is not a big issue in this context,
>     though: this is actually a general issue of what the client should
>     do when it has multiple configuration sources (e.g., when a client
>     tries to run DHCP on multiple interfaces or over different
>     protocols (IPv4 and IPv6)).  So, I think it is acceptable for the
>     mo-flags document just to mention this issue as one form of the
>     general issue and should be handled in the context of DHCP
>     standardization (likely at the dhc wg).
>=20
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba Corp.
> 					jinmei@isl.rdc.toshiba.co.jp
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Tue Apr 26 13:55:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQUHm-00080b-LV; Tue, 26 Apr 2005 13:55:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQUHj-0007zp-D1; Tue, 26 Apr 2005 13:55:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00575;
	Tue, 26 Apr 2005 13:55:46 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQUUE-000315-6f; Tue, 26 Apr 2005 14:08:42 -0400
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 26 Apr 2005 13:55:39 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3QHtaRQ009309; 
	Tue, 26 Apr 2005 13:55:36 -0400 (EDT)
Received: from [161.44.65.172] ([161.44.65.172])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AQV62772;
	Tue, 26 Apr 2005 13:55:35 -0400 (EDT)
From: Ralph Droms <rdroms@cisco.com>
To: IPv6 WG <ipv6@ietf.org>, dhcwg@ietf.org
In-Reply-To: <Pine.LNX.4.61.0504221622100.14579@netcore.fi>
References: <caab0e1b8f9a111b72c4a53df125c31a@innovationslab.net>
	<y7vhdhzjb8p.wl@ocean.jinmei.org>
	<Pine.LNX.4.61.0504221622100.14579@netcore.fi>
Content-Type: text/plain; charset=UTF-8
Date: Tue, 26 Apr 2005 13:58:32 -0400
Message-Id: <1114538312.6886.17.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2) 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id NAA00575
Cc: 
Subject: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Comments in line...

On Fri, 2005-04-22 at 16:30 +0300, Pekka Savola wrote:
> On Fri, 22 Apr 2005, JINMEI Tatuya / [ISO-2022-JP] =C2=BF=C3=80=C3=8C=C3=
=80=C3=83=C2=A3=C2=BA=C3=88 wrote:
> [...]
> >  then the host will try the "Host Configuration Behaviour"
> >  (Solicit/Advertise/Request/Reply exchanges), but the server does not
> >  respond to the Solicits.  According to the DHCPv6 specification, the
> >  host will send Solicits eternally, and won't even get other
> >  configuration information such as recursive DNS server addresses.
>=20
> Thanks for bringing up this issue.  I agree we must figure out how to=20
> fix this.
>=20
> > I can think of several possible resolutions:
> >
> > 1. just say that it's host/network administrator's responsibility to
> >   provide consistent parameters/configurations.  In this sense, the
> >   combination of a) and b) above is just a configuration error.
> >   This would be the most lightweight resolution for the authors:-),
> >   but I personally think it's irresponsible.
>=20
> I agree as well.  This is not good enough.

I think it's perfectly reasonable to assume that a configuration
mismatch is admin error and leave it at that - in this case, the RAs are
configured incorrectly, promising that a non-existent address assignment
service is available.

> > 2. allow a host to fall-back to Information Configuration Behaviour i=
n
> >   such a case.  This is not 100% compliant with the DHCPv6
> >   specification, though.
> >
> > 3. make small updates on the DHCPv6 specifications (RFC3315 and
> >   RFC3736) to help mitigate or avoid the problematic scenario.
> [...]
> > Ideally, I think resolution 3 is the way to go and should be included
> > in this document (we'll then need to DHCPv6 updates at the dhc wg, of
> > course).  But if it's too tough, resolution 2 can be a workaround wit=
h
> > careful wording.
>=20
> I think the DHC WG should be part of the resolution of this issue=20
> whether it's 2 or 3.  In particular, we should get their permission to=20
> say that implementations can do 2) if they want to, and can then maybe=20
> just refer to DHC WG (or some initial document) for 3).
>=20
> In any case, the solution or workaround should be so that it does not=20
> depend on updating the DHCPv6 server (so that just updating the=20
> client, e.g., to fall back is sufficient).

As was pointed out in a followup, I don't think there is anything in RFC
3315 that precludes a client from initiating an Information-
request/Reply message exchange in parallel with or subsequent to a
Solicit/Advertise/Request/Reply message exchange.

> > COMMENT 2:
> >
> > I believe we should also make consensus on the open issue described i=
n
> > Section 11 (default policy values) before publication.
>=20
> Agreed.
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> -------------------------------------------------------------------- IE=
TF IPv6 working group mailing list ipv6@ietf.org Adminiistrative Requests=
: https://www1.ietf.org/mailman/listinfo/ipv6 ---------------------------=
-----------------------------------------

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



From dhcwg-bounces@ietf.org Tue Apr 26 14:17:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQUd3-000230-7U; Tue, 26 Apr 2005 14:17:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQUd1-00022K-S0; Tue, 26 Apr 2005 14:17:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02340;
	Tue, 26 Apr 2005 14:17:46 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DQUpV-0003ax-G4; Tue, 26 Apr 2005 14:30:43 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3QIHX828714;
	Tue, 26 Apr 2005 21:17:33 +0300
Date: Tue, 26 Apr 2005 21:17:33 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <1114538312.6886.17.camel@localhost.localdomain>
Message-ID: <Pine.LNX.4.61.0504262111110.28111@netcore.fi>
References: <caab0e1b8f9a111b72c4a53df125c31a@innovationslab.net>
	<y7vhdhzjb8p.wl@ocean.jinmei.org>
	<Pine.LNX.4.61.0504221622100.14579@netcore.fi>
	<1114538312.6886.17.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: dhcwg@ietf.org, IPv6 WG <ipv6@ietf.org>
Subject: [dhcwg] Re: IPv6 WG Last Call:draft-ietf-ipv6-ra-mo-flags-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

On Tue, 26 Apr 2005, Ralph Droms wrote:
>>> I can think of several possible resolutions:
>>>
>>> 1. just say that it's host/network administrator's responsibility to
>>>   provide consistent parameters/configurations.  In this sense, the
>>>   combination of a) and b) above is just a configuration error.
>>>   This would be the most lightweight resolution for the authors:-),
>>>   but I personally think it's irresponsible.
>>
>> I agree as well.  This is not good enough.
>
> I think it's perfectly reasonable to assume that a configuration
> mismatch is admin error and leave it at that - in this case, the RAs are
> configured incorrectly, promising that a non-existent address assignment
> service is available.

That would be consistent if the presence of M-flag would only trigger 
DHCPv6 for address assignment, but DHCPv6 would not be used to 
configure anything else at all unless O-flag was also appropriately 
set.

Then the DHCPv6 and DHCPv6-lite would function in a similar fashion 
from the network administrator's perspective.

So, IMHO, either we must require O flag always for Information 
Configuration (whether DHCPv6 full or lite) or support the 
administrators who can't make out the subtle difference about the 
appropriate configuration of the flags.  For that, guidance for full 
DHCPv6 implementers to also try emulating DHCPv6 lite would probably 
be sufficient.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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



From dhcwg-bounces@ietf.org Sat May 07 14:02:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DUTdZ-0001Rb-Aa; Sat, 07 May 2005 14:02:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DNsd7-0007C9-Ut
	for dhcwg@megatron.ietf.org; Tue, 19 Apr 2005 09:19:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08555
	for <dhcwg@ietf.org>; Tue, 19 Apr 2005 09:19:03 -0400 (EDT)
Received: from bay16-f18.bay16.hotmail.com ([65.54.186.68] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNso4-0006cz-O9
	for dhcwg@ietf.org; Tue, 19 Apr 2005 09:30:26 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Tue, 19 Apr 2005 06:18:47 -0700
Message-ID: <BAY16-F18BCC82F35168A2B1DCDADFD2A0@phx.gbl>
Received: from 61.49.109.37 by by16fd.bay16.hotmail.msn.com with HTTP;
	Tue, 19 Apr 2005 13:18:46 GMT
X-Originating-IP: [61.49.109.37]
X-Originating-Email: [wangwenhao025@hotmail.com]
X-Sender: wangwenhao025@hotmail.com
From: "Wang Steven" <wangwenhao025@hotmail.com>
To: margaret@thingmagic.com
Date: Tue, 19 Apr 2005 21:18:46 +0800
Mime-Version: 1.0
Content-Type: text/plain; charset=gb2312; format=flowed
X-OriginalArrivalTime: 19 Apr 2005 13:18:47.0084 (UTC)
	FILETIME=[518426C0:01C544E2]
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id JAA08555
X-Mailman-Approved-At: Sat, 07 May 2005 14:02:46 -0400
Cc: dhcwg@ietf.org
Subject: [dhcwg] back up dhcp server
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Hello, Margaret:

I want to set up one backup dhcp server, which may not work simultaneousl=
y=20
with master server. Only after the master server is down,or I made some=20
configurations, the backup server will work. Here the communication betwe=
en=20
two servers may be not required.

Has such a mechanism be fulfilled in DHCP protocol or current OS? My serv=
er=20
may be of Redhat or SLES. If it is fulfilled, where do you think i should=
=20
get more details about that?

Thanks a lot for any response!

Steven Wang

_________________________________________________________________
=C3=E2=B7=D1=CF=C2=D4=D8 MSN Explorer:   http://explorer.msn.com/lccn/ =20


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



