RE: [dhcwg] Items of the new wg charter

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Wed, 11 September 2002 17:37 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18116 for <dhcwg-archive@odin.ietf.org>; Wed, 11 Sep 2002 13:37:18 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g8BHcWq31551 for dhcwg-archive@odin.ietf.org; Wed, 11 Sep 2002 13:38:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHcWv31548 for <dhcwg-web-archive@optimus.ietf.org>; Wed, 11 Sep 2002 13:38:32 -0400
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18096 for <dhcwg-web-archive@ietf.org>; Wed, 11 Sep 2002 13:36:48 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHWSv30796; Wed, 11 Sep 2002 13:32:28 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHV4v30730 for <dhcwg@optimus.ietf.org>; Wed, 11 Sep 2002 13:31:04 -0400
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17751 for <dhcwg@ietf.org>; Wed, 11 Sep 2002 13:29:19 -0400 (EDT)
Received: from mr7.exu.ericsson.se (mr7u3.ericy.com [208.237.135.122]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id g8BHUwj19276; Wed, 11 Sep 2002 12:30:59 -0500 (CDT)
Received: from eamrcnt760.exu.ericsson.se (eamrcnt760.exu.ericsson.se [138.85.133.38]) by mr7.exu.ericsson.se (8.11.3/8.11.3) with ESMTP id g8BHUwA14756; Wed, 11 Sep 2002 12:30:58 -0500 (CDT)
Received: by eamrcnt760.exu.ericsson.se with Internet Mail Service (5.5.2656.59) id <QZT804FA>; Wed, 11 Sep 2002 12:30:58 -0500
Message-ID: <F9211EC7A7FED4119FD9005004A6C8700A6708DF@eamrcnt723.exu.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "Bound, Jim" <Jim.Bound@hp.com>, BINET David FTRD/DMI/CAE <david.binet@rd.francetelecom.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Items of the new wg charter
Date: Wed, 11 Sep 2002 12:30:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C259B8.FC5AAA50"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>

Some of this work likely overlaps the PANA WG and may be more appropriate in there?

DHCP is the Dynamic Host Configuration Protocol and has focused on configuration of clients - not authorizing users. (We've viewed the user authorization as happening AFTER the address was assigned.)

In light of todays world in which most clients are really associated with a single user, it is likely time for the WG to revisit this? But, this would require discussions within the WG, with the ADs, and with other WGs responsible for authentication issues (AAA, PANA, ...)?

We must also remember there are systems that aren't associated with specific users - and they need addresses and configuration information as well. And, this would fundamentally impact when addresses are assigned and released, since a user logout could require an address release.

- Bernie

-----Original Message-----
From: Bound, Jim [mailto:Jim.Bound@hp.com]
Sent: Wednesday, September 11, 2002 11:29 AM
To: BINET David FTRD/DMI/CAE; dhcwg@ietf.org
Subject: RE: [dhcwg] Items of the new wg charter


My view is we MUST deal with Mobility in all IETF working groups.  For those that write code and build this stuff you know from the initial mobile code we have had to put in for mobile v4/v6, tcp wireless (pilc wg), et al that mobile greatly affects our IP stack, APIs, and ISV applications paradigms.  It is now inherent in the infrastructure. Of course it has to be in our vision with the dhc working group.  Unfortuneately I  as one person appear to be unable to communciate with ADs in the IETF so I suggest others they may respect more go beat on them and work with Ralph to get this included.  It is complete error in dhc to not have this in our charter.

/jim

> -----Original Message-----
> From: BINET David FTRD/DMI/CAE 
> [mailto:david.binet@rd.francetelecom.com]
> Sent: Wednesday, September 11, 2002 2:56 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Items of the new wg charter
> 
> 
> Hi,
> 
> There were some internet drafts dealing with the deployment 
> of DHCP protocol in new envrironments, such as roaming/mobile 
> clients and xdsl access. These drafts were, as far as I know, 
> draft-ietf-dhc-aaa-ra-00.txt, 
> draft-ietf-dhc-enhance-requirements-00.txt, 
> draft-ietf-dhc-aaa-requirements-00.txt. All these drafts have 
> expired and it seems that there is no such working item in 
> the next charter of the working group, discussed during the 
> last meeting in Yokohama.
> 
> Does it mean that the working group considers that it is not 
> an important item even if some ISPs consider DHCP protocol (+ 
> improvements) as an alternative or a complement to PPP for 
> their services ? Or does this work is handled by another 
> working group ?
> 
> David Binet
>  
> 
> 
> _______________________________________________
> 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