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

"Alper Yegin" <alper.yegin@yegin.org> Mon, 05 March 2007 10:05 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 1HOA4l-0006fO-5I; Mon, 05 Mar 2007 05:05:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOA4j-0006al-R9 for dhcwg@ietf.org; Mon, 05 Mar 2007 05:05:49 -0500
Received: from mout.perfora.net ([217.160.230.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOA4i-0008VY-Kz for dhcwg@ietf.org; Mon, 05 Mar 2007 05:05:49 -0500
Received: from [85.97.177.66] (helo=IBM52A5038A94F) by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis), id 0MKp2t-1HOA4T1NIq-0006Bv; Mon, 05 Mar 2007 05:05:47 -0500
From: Alper Yegin <alper.yegin@yegin.org>
To: ric@cisco.com, 'Yoshihiro Ohba' <yohba@tari.toshiba.com>
Subject: RE: [dhcwg] draft-pruss-dhcp-auth-dsl-00.txt
Date: Mon, 05 Mar 2007 12:05:27 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcdeynYIw7Ey1I72Sx2WYIhxNNhLdAAQch/g
In-reply-to: <45EB7A1E.2030705@cisco.com>
Message-ID: <0MKp2t-1HOA4T1NIq-0006Bv@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net login:abf7a4bb310ea4dfc9b6841113e2970f
X-Provags-ID2: V01U2FsdGVkX180KPeBYCWllDi2C7HzbtcCZbfhrZaTiu3bjlK rnV3WlyyMvYdyd+lw1A7QvASiRJUpFNk3fQQzecCqjd7lZKV33 ehR+V0eqJE0PKCn99bMYQ==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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 think the elegance of approach a) verses b1-7) is pretty clear,

I just see this as DHCP giving birth to L3 version of PPP (one protocol does
all).

I think IAB draft "Principles of Internet Host Configuration" is pretty
clear on such an approach:

2.5.  Configuration is Not Access Control

   Network access authentication is a distinct problem from Internet
   host configuration.  Network access authentication is best handled
   independently of the configuration mechanisms in use for the Internet
   and higher layers.

   For example, attempting to control access by requiring authentication
   in order to obtain configuration parameters (such as an IP address)
   has little value if the user can manually configure the host.  Having
   an Internet (or higher) layer protocol authenticate clients is
   appropriate to prevent resource exhaustion of a scarce resource on
   the server, but not for preventing rogue hosts from obtaining access
   to a link.  Note that client authentication is not required for
   Stateless DHCPv6 [RFC3736] since it does not result in allocation of
   any limited resources on the server.


Alper



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