RE: [dhcwg] draft-pruss-dhcp-auth-dsl-00.txt

"MORAND Lionel RD-CORE-ISS" <lionel.morand@orange-ftgroup.com> Tue, 06 March 2007 10:13 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOWfh-0008QI-8h; Tue, 06 Mar 2007 05:13:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOWff-0008GZ-0s for dhcwg@ietf.org; Tue, 06 Mar 2007 05:13:27 -0500
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOWfb-0006Lq-OO for dhcwg@ietf.org; Tue, 06 Mar 2007 05:13:26 -0500
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Mar 2007 11:12:52 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] draft-pruss-dhcp-auth-dsl-00.txt
Date: Tue, 06 Mar 2007 11:12:26 +0100
Message-ID: <7DBAFEC6A76F3E42817DF1EBE64CB026045B67BE@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] draft-pruss-dhcp-auth-dsl-00.txt
Thread-Index: AcdfclT5ldDHiBqfQpOkTVduVYnX3QAX4Tlw
From: MORAND Lionel RD-CORE-ISS <lionel.morand@orange-ftgroup.com>
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, Richard Pruss <ric@cisco.com>
X-OriginalArrivalTime: 06 Mar 2007 10:12:52.0571 (UTC) FILETIME=[00490AB0:01C75FD8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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>
Errors-To: dhcwg-bounces@ietf.org

I will be also interested by the answer to this question ;)
Beyond never-ending discussions on optional alternative possible potential solutions for access authentication, it would be very helpful to understand where we are going, what should be done and what should not be done in this area within IETF.

I have a specific question about the network configuration chosen as working assumption:

why do you consider a DHCP server in the NAS while typical dsl network configurations rely on a DHCP relay agent in the NAS and an external DHCP server (distinct from the NAS) in DHCP-based environment?
Could the proposed DHCP-based CHAP authentication work if the DHCP server is not in the NAS? 

BR,

Lionel


> -----Message d'origine-----
> De : Yoshihiro Ohba [mailto:yohba@tari.toshiba.com] 
> Envoyé : lundi 5 mars 2007 23:02
> À : Richard Pruss
> Cc : dhcwg@ietf.org; Yoshihiro Ohba
> Objet : Re: [dhcwg] draft-pruss-dhcp-auth-dsl-00.txt
> 
> A direct question is, how does your draft fit Section 2.5 of 
> draft-aboba-ip-config-00.txt?
> 
> Yoshihiro Ohba
> 
> _______________________________________________
> 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