RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt-imap-00.txt
"Bernie Volz" <volz@cisco.com> Wed, 09 March 2005 14:39 UTC
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 JAA09001 for <dhcwg-web-archive@ietf.org>; Wed, 9 Mar 2005 09:39:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D92OX-0000xj-6U for dhcwg-web-archive@ietf.org; Wed, 09 Mar 2005 09:42:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D929A-0004ZL-40; Wed, 09 Mar 2005 09:26:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D9297-0004ZD-RX for dhcwg@megatron.ietf.org; Wed, 09 Mar 2005 09:26:46 -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 JAA06892 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 09:26:43 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D92Bj-0000IM-LI for dhcwg@ietf.org; Wed, 09 Mar 2005 09:29:28 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 09 Mar 2005 09:26:37 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 j29EQX1j024616; Wed, 9 Mar 2005 09:26:34 -0500 (EST)
Received: from volzw2k (che-vpn-cluster-2-89.cisco.com [10.86.242.89]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APR09498; Wed, 9 Mar 2005 09:26:31 -0500 (EST)
Message-Id: <200503091426.APR09498@flask.cisco.com>
From: Bernie Volz <volz@cisco.com>
To: 'Cristian Cadar' <Cristian.Cadar@netlab.nec.de>, 'Van Aken Dirk' <Dirk.VanAken@thomson.net>, 'Ted Lemon' <mellon@fugue.com>
Subject: RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt-imap-00.txt
Date: Wed, 09 Mar 2005 09:26:24 -0500
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.5510
In-Reply-To: <F0DC7B6021F256408935B31D97FC727EA5A555@europa.office>
Thread-Index: AcUkLppJ8Jt8Y0QGS1K8CjNHWEb7lwAVeX7wAAvFZEA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
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: 156eddb66af16eef49a76ae923b15b92
Content-Transfer-Encoding: 7bit
Yes, I'm sure a lot of servers implement it since it really isn't an issue for them to do so - it is just one more IP-address list option. - Do you have a requirement for this option? Are you presently using it for DHCPv4 (I don't just mean configuring in the DHCPv4 server, but expecting clients to make use of it)? - Do you know if it is in actual use (again, clients using the values received from a DHCPv4 server) anywhere? - Bernie > -----Original Message----- > From: Cristian Cadar [mailto:Cristian.Cadar@netlab.nec.de] > Sent: Wednesday, March 09, 2005 4:06 AM > To: Bernie Volz; Van Aken Dirk; Ted Lemon > Cc: dhcwg@ietf.org > Subject: RE: > [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft -cadar-dhc-opt-imap-00.txt > > Hi there, > > From my experience I know for sure that you can find the SMTP > option in > the most DHCP servers > for Windows and Unix OS. In my opinion the usage of this option should > be decided by the network administrators. > I don't think that we have a correct survey on how frequently this > option is used in reality. I agree with you that this option is not > heavily used > in comparison with the DNS one for instance, but having this option > among the configurable DHCPv6 options would be an asset in my opinion > than a burden. > > Bernie- we can discuss on the format of this option. > > > Cristian > > -----Original Message----- > From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf > Of Bernie Volz > Sent: Tuesday, March 08, 2005 11:32 PM > To: 'Van Aken Dirk'; 'Ted Lemon'; Cristian Cadar > Cc: dhcwg@ietf.org > Subject: RE: > [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft -cadar-dhc > -opt-imap-00.txt > > In preparing for IETF-62 I dug up this old discussion and I > second Ted's > question. I really don't see this as something coming from DHCP -- it > really is specific to the user, not the client, and isn't really > access-point specific (as most DHCP information is). > > As we have DHCPv4 options (69 for SMTP and 70 for POP3), I would first > ask how widely used are these options? Are they supported by any > clients? Are they configured in any DHCPv4 servers? > > If the answer is that they are heavily used, I'm all for adopting them > for DHCPv6. But if the answer is that they're basically never > used, why > do you now feel they'll be used for DHCPv6? > > Perhaps at the Thursday AM DHC WG session you can address this usage > question as that might gave the WG important information as to whether > these options are warranted for DHCPv6 or not. > > Also, if we were to consider these options, how about a more general > format so we don't need a new option for every application that comes > along? > > For example, you could define a "default application server option" > which would be formatted as: > well-known-service-port-number (2 bytes) > length or number of addresses to follow (1 or 2 bytes) > ipv6 addresses > And this could repeat. Now we have one option into which we can bundle > up all of the servers and when someone else comes along wanting to > provide clients the addresses for server foo, no new option need be > written (and implemented). > > Well, just an idea ... It does complicate the configuration at the > servers and parsing at the clients. > > > If we do move forward with your work, I'd like to see more > explicit text > around ORO requirements. I think this option *MUST* be > requested in the > ORO receive from the client before a server would return it. > > - Bernie > > > -----Original Message----- > > From: dhcwg-bounces@ietf.org > [mailto:dhcwg-bounces@ietf.org] On Behalf > > > Of Van Aken Dirk > > Sent: Sunday, August 01, 2004 2:50 PM > > To: Ted Lemon; Cristian Cadar > > Cc: dhcwg@ietf.org > > Subject: RE: [dhcwg] > > Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar- > > dhc-opt-imap-00.txt > > > > Hello Ted, Cristian, > > > > See some comments inline. > > > > Best regards - Dirk > > > > > -----Original Message----- > > > From: dhcwg-bounces@ietf.org > > > [mailto:dhcwg-bounces@ietf.org]On Behalf Of Ted Lemon > > > Sent: vrijdag 30 juli 2004 18:33 > > > To: Cristian Cadar > > > Cc: dhcwg@ietf.org > > > Subject: Re: [dhcwg] Comments > > > ondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt- > > > imap-00.txt > > > > > > I guess my first question about this is why? > > > > I assume to come closer to zero-config of hosts and applications I > > would say. > > > > > Why would you want a client to trust the DHCP server to > > tell you what IMAP server to > > > contact? > > > > Is this not true for all options that are returned by a server ? > > > > > What if you wind up talking to a rogue server, or roam to a > > > different network? These don't seem like things that are > > > location-dependent - they seem like things that you want to > > configure > > > on the client and not change as the client moves around. > > > > True, but on the other hand from the perspective of a system admin, > > he/she must use two methods for host/application > configuration. That > > is, a DHCP server for a first set of parameters and scripts or even > > manual config for other parameters. > > > > > > > > > > > _______________________________________________ > > > dhcwg mailing list > > > dhcwg@ietf.org > > > https://www1.ietf.org/mailman/listinfo/dhcwg > > > > > > > _______________________________________________ > > dhcwg mailing list > > dhcwg@ietf.org > > https://www1.ietf.org/mailman/listinfo/dhcwg > > > > _______________________________________________ > dhcwg 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
- RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Cristian Cadar
- RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Bernie Volz
- RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Cristian Cadar
- Re: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Ted Lemon
- RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Cristian Cadar
- Re: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-e… Ted Lemon
- Re: Re: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-o… Daniel Park
- RE: Re:[dhcwg]Commentsondraft-cadar-dhc-dhcpv6-op… Bernie Volz