RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt-imap-00.txt

"Cristian Cadar" <Cristian.Cadar@netlab.nec.de> Wed, 09 March 2005 09:06 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 EAA00082 for <dhcwg-web-archive@ietf.org>; Wed, 9 Mar 2005 04:06:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8xBz-0000SE-9X for dhcwg-web-archive@ietf.org; Wed, 09 Mar 2005 04:09:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8x90-00016J-1T; Wed, 09 Mar 2005 04:06:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D8x8w-000168-Id for dhcwg@megatron.ietf.org; Wed, 09 Mar 2005 04:06:15 -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 EAA00034 for <dhcwg@ietf.org>; Wed, 9 Mar 2005 04:06:12 -0500 (EST)
Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D8xBV-0000RO-Fz for dhcwg@ietf.org; Wed, 09 Mar 2005 04:08:53 -0500
Received: from europa.office (europa.office [10.1.1.2]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 2C49815100; Wed, 9 Mar 2005 10:09:12 +0100 (CET)
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
Subject: RE: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt-imap-00.txt
Date: Wed, 09 Mar 2005 10:06:03 +0100
Message-ID: <F0DC7B6021F256408935B31D97FC727EA5A555@europa.office>
Thread-Topic: [dhcwg]Commentsondraft-cadar-dhc-dhcpv6-opt-email-00.txt/draft-cadar-dhc-opt-imap-00.txt
Thread-Index: AcUkLppJ8Jt8Y0QGS1K8CjNHWEb7lwAVeX7w
From: Cristian Cadar <Cristian.Cadar@netlab.nec.de>
To: Bernie Volz <volz@cisco.com>, Van Aken Dirk <Dirk.VanAken@thomson.net>, Ted Lemon <mellon@fugue.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: quoted-printable
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: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable

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