
From root@core3.amsl.com  Wed Jul  1 22:00:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 551FA28C142; Wed,  1 Jul 2009 22:00:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090702050002.551FA28C142@core3.amsl.com>
Date: Wed,  1 Jul 2009 22:00:02 -0700 (PDT)
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action:draft-ietf-dhc-dhcpv6-ldra-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2009 05:00:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.


	Title           : Lightweight DHCPv6 Relay Agent (LDRA)
	Author(s)       : D. Miles, et al.
	Filename        : draft-ietf-dhc-dhcpv6-ldra-00.txt
	Pages           : 15
	Date            : 2009-07-01

This document proposes a Lightweight DHCPv6 Relay Agent (LDRA) that
is used to insert relay agent options in DHCPv6 message exchanges
identifying client-facing interfaces.  The LDRA can be implemented in
existing access nodes (such as DSLAMs and Ethernet switches) that do
not support IPv6 control or routing functions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-ldra-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-dhc-dhcpv6-ldra-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-07-01214607.I-D@ietf.org>


--NextPart--

From budm@weird-solutions.com  Thu Jul  2 04:14:41 2009
Return-Path: <budm@weird-solutions.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99BE83A6D77 for <dhcwg@core3.amsl.com>; Thu,  2 Jul 2009 04:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level: 
X-Spam-Status: No, score=-0.647 tagged_above=-999 required=5 tests=[AWL=-0.463, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3cLjd1Fx8zR8 for <dhcwg@core3.amsl.com>; Thu,  2 Jul 2009 04:14:40 -0700 (PDT)
Received: from cl38.gs02.gridserver.com (cl38.gs02.gridserver.com [64.13.232.47]) by core3.amsl.com (Postfix) with ESMTP id C15C93A67A4 for <dhcwg@ietf.org>; Thu,  2 Jul 2009 04:14:40 -0700 (PDT)
Received: from static-213-115-152-226.sme.bredbandsbolaget.se ([213.115.152.226]:33111 helo=offset.weird.se) by cl38.gs02.gridserver.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.63) (envelope-from <budm@weird-solutions.com>) id 1MMKFh-0002Hx-2u; Thu, 02 Jul 2009 04:14:54 -0700
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Thu, 2 Jul 2009 13:03:50 +0200
User-Agent: KMail/1.9.9
References: <5033E739-18FA-4328-A276-E6D159052AAA@cisco.com> <200903171740.19574.budm@weird-solutions.com> <F2E7FCAE-3E96-400F-8096-3A03D16E29DC@nominum.com>
In-Reply-To: <F2E7FCAE-3E96-400F-8096-3A03D16E29DC@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907021303.51113.budm@weird-solutions.com>
X-Authenticated-User: 39280 budm@broadbandprovisioner.com
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-dhcpv4-vendor-message-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2009 11:14:41 -0000

On Friday 26 June 2009, Ted Lemon wrote:
> Bud, when the wglc came out for the dhcpv4 and dhcpv6 versions of this
> draft, you responded positively to the dhcpv4 version, but not the
> dhcpv6 version.   Was that a deliberate or accidental omission?

Accidental omission, terribly sorry. I'm fine with both drafts.

- Bud

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687

From Ted.Lemon@nominum.com  Thu Jul  2 12:10:16 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 837823A6A91 for <dhcwg@core3.amsl.com>; Thu,  2 Jul 2009 12:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6LSzeoEIXEM for <dhcwg@core3.amsl.com>; Thu,  2 Jul 2009 12:10:15 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by core3.amsl.com (Postfix) with ESMTP id 189C83A697B for <dhcwg@ietf.org>; Thu,  2 Jul 2009 12:10:14 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKSk0GLAXaFIvOMo1pPX4TrRCc8LFiQO1g@postini.com; Thu, 02 Jul 2009 12:10:38 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1D3081B83F2; Thu,  2 Jul 2009 12:10:48 -0700 (PDT)
Received: from uma.here (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Thu, 2 Jul 2009 12:10:35 -0700
Message-ID: <7CC2A89B-54D0-4670-93BC-2E84D85B78A9@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Bud Millwood <budm@weird-solutions.com>
In-Reply-To: <200907021303.51113.budm@weird-solutions.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 2 Jul 2009 12:10:33 -0700
References: <5033E739-18FA-4328-A276-E6D159052AAA@cisco.com> <200903171740.19574.budm@weird-solutions.com> <F2E7FCAE-3E96-400F-8096-3A03D16E29DC@nominum.com> <200907021303.51113.budm@weird-solutions.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-dhcpv4-vendor-message-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2009 19:10:16 -0000

On Jul 2, 2009, at 4:03 AM, Bud Millwood wrote:
> Accidental omission, terribly sorry. I'm fine with both drafts.

Great, thanks for clarifying!


From alper.yegin@yegin.org  Fri Jul  3 01:21:16 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 779B63A6AC0 for <dhcwg@core3.amsl.com>; Fri,  3 Jul 2009 01:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5FQ-6vwIUN53 for <dhcwg@core3.amsl.com>; Fri,  3 Jul 2009 01:21:15 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 86ED13A6B6C for <dhcwg@ietf.org>; Fri,  3 Jul 2009 01:21:15 -0700 (PDT)
Received: from LENOVO (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MMe1P0LOc-000C0x; Fri, 03 Jul 2009 04:21:31 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Richard Pruss'" <ric@cisco.com>
References: <20090325201231.7A5943A6BD6@core3.amsl.com> <C5F02B3C.9F5EA%john_brzozowski@cable.comcast.com> <086b01c9ee53$ea8a53c0$bf9efb40$@yegin@yegin.org> <704F21DF-1F6A-4D78-AF8B-D0F2E9964659@cisco.com>
In-Reply-To: <704F21DF-1F6A-4D78-AF8B-D0F2E9964659@cisco.com>
Date: Fri, 3 Jul 2009 11:21:18 +0300
Message-ID: <018901c9fbb7$423ef920$c6bceb60$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnuZu72ARC4V2dkTYC8ONnTRDzMbwNS6tLg
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX19Zj5Dka85YtyOQ826N3kgwZmQevhkoTpK3Z5X WEkzs2Zu5sJkrmUlQ8PU0ZpGU8Arv2w0TAUQrGxEIlxEwiT4iE +6O9n9kw5jccEdzQy49Rw==
Cc: 'dhc WG' <dhcwg@ietf.org>
Subject: Re: [dhcwg] FW: New Version Notification for draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2009 08:21:16 -0000

I was really wondering about the thoughts of the authors. Since they did the
analysis, they must have considered these points (which were already raised
on the mailing list).


> > - The role of NAS with respect to DHCP is unclear. For some part it
> is
> > acting as a DHCP relay, for others as a DHCP server (as it
> > terminates DHCP
> > messages and generates DHCP messages -- for EAP). Is the NAS playing
> > two
> > distinct DHCP roles within the same DHCP session? How well does that
> > fit
> > DHCP?
> 
> Yes, in Broadband the NAS can be a relay or a server at the operators
> choice.

At the same time for the same DHCP session? I don't think so. There is no
way (barring serious hacks) for a DHCP session be executed between one DHCP
client and multiple DHCP servers. [NAS acting as a relay for some DHCP
client for the duration of a DHCP session, and as a server for other clients
for the duration of a DHCP session is OK -- but that's not same as what is
in your I-D]

> > - NAS (acting as DHCP relay) is inserting DHCP options towards the
> > DHCP
> > client. I'm not aware of DHCP relays inserting options in that
> > direction. To
> > say the least, that breaks the end-to-end security, such as the one
> > using
> > RFC 3118.
> 
> Depends how the keying for RFC 3118 was implemented.  We have a draft
> as you are aware that has the NAS aware of the keys.

I am not aware of any draft that tries to secure this aforementioned broken
model. Please provide us a reference if there is any.

> > - " The client sends a Solicit message with an Option specifying the
> >   session authentication protocol as EAP to the
> >   All_DHCP_Relay_Agents_and_Servers address to find available DHCP
> >   servers.  Any server that can authenticate and address it responds
> >   with a DHCPEAP-REQ message."
> >
> > This is talking about a DHCP server sending a "request" to the DHCP
> > "client", quite the opposite of current DHCP architecture. How well
> > does
> > that fit the state machine?
> 
> Draw the diagram of what you are talking it is so trivially obvious, I
> fail to understand your question.

DHCP "server" sending "requests" is exactly the opposite of the current DHCP
architecture. I'd expect an analysis of impact on DHCP to take this into
account.

> > - According to EAP, the EAP authenticator has to be able to
> > retransmit EAP
> > requests. That means the NAS has to rexmit DHCPEAP-REQ to the DHCP
> > client
> > until it receives a DHCPEAP-RES. How does this fit "DHCP"?
> 
> As specified in the draft and now in multiple implementations.

Again, this does not fit the "clients sending requests in DHCP" model.
You have a server sending requests. Maybe you have a DHCP client in NAS?

> > - EAP re-authentication may be initiated by the network. How would
> > this be
> > handled?
> 
> Really?  Is it a requirement in broadband separate to re-addressing?

I'm talking about "re-authentication", not "re-addressing".
Every AAA architecture supports re-authentication. This is already supported
by the EAP, EAP methods, RADIUS, Diameter. It's an integral part of every
AAA design. You should be able to perform auth, re-auth, termination, etc.
You have to support that.

 
> > It requires the DHCP client to receive an unsolicited DHCP request
> > message from the NAS (a DHCP relay??). "DHCP client receiving a
> > request from
> > relay" sounds quite non-standard to me.
> 
> 
> 
> >
> > - Finally, I wonder how orderly delivery of EAP (as mandated by RFC
> > 3748) is
> > satisfied by this proposed EAP lower layer.
> 
> This is a boring academic point with no relevance to real networking,
> can simply be answered
> with the statement that there is no transport difference between EAP
> running over PPPoE,
> than their is with EAP running over DHCP on an Ethernet network.

This is not an answer. There is no big deal in here anyways. Just put a
sequence number in the EAP-encapsulating DHCP option and be done with it. 

Alper




From huanglu@chinamobile.com  Mon Jul  6 09:24:37 2009
Return-Path: <huanglu@chinamobile.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13C8C28C371 for <dhcwg@core3.amsl.com>; Mon,  6 Jul 2009 09:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.12
X-Spam-Level: ****
X-Spam-Status: No, score=4.12 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULFNdRMfU+Pn for <dhcwg@core3.amsl.com>; Mon,  6 Jul 2009 09:24:36 -0700 (PDT)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.130.253.133]) by core3.amsl.com (Postfix) with ESMTP id D6DB928C365 for <dhcwg@ietf.org>; Mon,  6 Jul 2009 09:24:35 -0700 (PDT)
Received: from DKEEPER007 ([10.1.5.3]) by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1) with SMTP id 2009070700065794-17728 ; Tue, 7 Jul 2009 00:06:57 +0800 
Date: Tue, 7 Jul 2009 00:06:38 +0800
From: "Huanglu" <huanglu@chinamobile.com>
To: "dhcwg" <dhcwg@ietf.org>
Organization: CMCC
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-07-07 00:06:58, Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-07-07 00:25:02, Serialize complete at 2009-07-07 00:25:02
Message-ID: <OF4A0EDCFD.88762635-ON482575EB.0058874D@china.mobile>
Content-Type: multipart/alternative; boundary="=====003_Dragon503738637417_====="
Subject: [dhcwg] Problem Statement for DHCP Relay Agent
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: huanglu@chinamobile.com
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2009 16:24:37 -0000

This is a multi-part message in MIME format.

--=====003_Dragon503738637417_=====
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="gb2312"

Dear all,

We had submitted a problem statement draft which describes two pretty common network scenarios that uses Layer 2 and Layer 3 Relay Agents and their unique requirements where either DHCP server or Relay Agent need more information to handle DHCP messages.

Please check the link:
http://www.ietf.org/internet-drafts/draft-huang-dhc-relay-ps-00.txt

Please reply with any comments. 

Thanks

Best Regards!
Lu Huang

--=====003_Dragon503738637417_=====
Content-Transfer-Encoding: base64
Content-Type: text/html;
	charset="gb2312"

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w
MC42MDAwLjE2ODI1IiBuYW1lPUdFTkVSQVRPUj48L0hFQUQ+DQo8Qk9EWSBiZ0NvbG9yPSNmZmZm
ZmY+DQo8RElWPjxGT05UIGZhY2U9y87M5SBzaXplPTI+RGVhciZuYnNwO2FsbCw8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxGT05UIGZhY2U9y87M5SBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJ
Vj48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPldlIGhhZCBzdWJtaXR0ZWQgYSBwcm9ibGVtIHN0YXRl
bWVudCBkcmFmdCB3aGljaCANCmRlc2NyaWJlcyB0d28gcHJldHR5IGNvbW1vbiBuZXR3b3JrIHNj
ZW5hcmlvcyB0aGF0IHVzZXMgTGF5ZXIgMiBhbmQgTGF5ZXIgMyANClJlbGF5IEFnZW50cyBhbmQg
dGhlaXIgdW5pcXVlIHJlcXVpcmVtZW50cyB3aGVyZSBlaXRoZXIgREhDUCBzZXJ2ZXIgb3IgUmVs
YXkgDQpBZ2VudCBuZWVkIG1vcmUgaW5mb3JtYXRpb24gdG8gaGFuZGxlIERIQ1AgbWVzc2FnZXMu
PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPcvOzOUgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8
L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPlBsZWFzZSBjaGVjayB0aGUgbGluazo8L0ZPTlQ+PC9E
SVY+DQo8RElWPjxBIA0KaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv
ZHJhZnQtaHVhbmctZGhjLXJlbGF5LXBzLTAwLnR4dCI+PEZPTlQgDQpzaXplPTI+aHR0cDovL3d3
dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaHVhbmctZGhjLXJlbGF5LXBzLTAwLnR4
dDwvRk9OVD48L0E+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9y87M5SBzaXplPTI+PC9GT05UPiZu
YnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iIHNpemU9Mj5QbGVh
c2UgcmVwbHkgd2l0aCBhbnkgY29tbWVudHMuIA0KPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBz
aXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhhbmtzPC9GT05U
PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSJUaW1lcyBOZXcgUm9tYW4iIHNpemU9Mj48L0ZPTlQ+
Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9IlRpbWVzIE5ldyBSb21hbiIgc2l6ZT0yPkJl
c3QgUmVnYXJkcyE8QlI+THUgDQpIdWFuZzwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K

--=====003_Dragon503738637417_=====--


From ravikumar.lrk@gmail.com  Tue Jul  7 02:27:27 2009
Return-Path: <ravikumar.lrk@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D7DF3A6E32 for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 02:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CO7ntUy0gGQ5 for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 02:27:26 -0700 (PDT)
Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by core3.amsl.com (Postfix) with ESMTP id E25353A6E2B for <dhcwg@ietf.org>; Tue,  7 Jul 2009 02:27:25 -0700 (PDT)
Received: by wa-out-1112.google.com with SMTP id v27so900528wah.5 for <dhcwg@ietf.org>; Tue, 07 Jul 2009 02:26:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Z5IDl2bghVy3tJzrvSxdRql1SdfqV5t7403wuwCkaxI=; b=PpAqzSYB2jRNDiHowdDaovdY1K2wPXxCtN2/LVr7dmWQmVGf86IvacZiepqw2sPwfR 9pOha7Q2zCXWcCFYKD+oTHCJr61X+m6s6pB0ZH6wktUBx5xihVnZ5b3DCCuCmkSbsa9x Q8Ocxry1AjWHPfWCXkLkzd0SNEqhSRzvUNx0Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bdJgvEPWsrXbKd21/jvPtn5K4yvduZG9vOoKiRvbD6PwZ2BqDbkb18M3BeR+i+voTK //LqbiWY4FHQ1N3oe5K7Wy6caqg6VMB/hmXjVHTMODoeLDiHZJfjDKE8cNXjXCJMkgF0 HppeKXDo8L5hlm64d8ZjCc1hutMeSlE7l04/4=
MIME-Version: 1.0
Received: by 10.115.76.5 with SMTP id d5mr9131300wal.55.1246958455878; Tue, 07  Jul 2009 02:20:55 -0700 (PDT)
Date: Tue, 7 Jul 2009 14:50:55 +0530
Message-ID: <adf2a3a0907070220k728b1502i7e30e8c63056d136@mail.gmail.com>
From: ravi kumar <ravikumar.lrk@gmail.com>
To: DHC WG <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=00163641773fcff4fc046e1a23ab
Subject: [dhcwg] RFC 3315 - Request message
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2009 09:27:27 -0000

--00163641773fcff4fc046e1a23ab
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

RFC 3315 specifies that IA option(s) is included in Request messages sent by
Dhcpv6 client.

Is it necessary for client to include IAAddress option also as part of IANA
option. Is it not enough for client to include just IANA option, with no
IAAddress option in Request message.

regards
Ravi

--00163641773fcff4fc046e1a23ab
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>RFC 3315 specifies that IA option(s) is included in Request messages s=
ent by Dhcpv6 client.</div>
<div>=A0</div>
<div>Is it necessary for client to include IAAddress option also=A0as part =
of=A0IANA option. Is it not enough for client to include just IANA option, =
with no IAAddress option in Request message.</div>
<div>=A0</div>
<div>regards</div>
<div>Ravi</div>

--00163641773fcff4fc046e1a23ab--

From sunseawq@huawei.com  Tue Jul  7 05:49:13 2009
Return-Path: <sunseawq@huawei.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA76E3A6E5D for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 05:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nu2wDWwP3Axe for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 05:49:13 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 3084728C4A7 for <dhcwg@ietf.org>; Tue,  7 Jul 2009 05:48:56 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KME00LS5WVGEE@szxga02-in.huawei.com> for dhcwg@ietf.org; Tue, 07 Jul 2009 20:47:41 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KME00GFSWVG9D@szxga02-in.huawei.com> for dhcwg@ietf.org; Tue, 07 Jul 2009 20:47:40 +0800 (CST)
Received: from w53375 ([10.164.12.38]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KME00822WVGR7@szxml06-in.huawei.com> for dhcwg@ietf.org; Tue, 07 Jul 2009 20:47:40 +0800 (CST)
Date: Tue, 07 Jul 2009 20:47:40 +0800
From: Qin Wu <sunseawq@huawei.com>
To: dhcwg@ietf.org
Message-id: <073e01c9ff01$1d175b90$260ca40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20090706091501.390B228C1E7@core3.amsl.com>
Subject: Re: [dhcwg] I-D Action:draft-wang-dhc-ldn-option-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2009 12:49:13 -0000

Hi, all:
We have posted an I-D draft on local domain name discovery for ERP
(http://www.ietf.org/internet-drafts/draft-wang-dhc-ldn-option-00.txt)
The I-D makes the assumptions of using DHCP mechanism to request local domain name for the peer when the peer does not know the local domain name.
This mechanism can be applicable to the scenario where the full authentication and Re-authentication are utilized together.Also it requires full authentication happens before Re-authentication. In our view, this document provide some new feature from deployment perspective and could be taken as one candiate component in the hokey architecture. 

Look forward to your constructive discussion!

Regards!
-Qin
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Sent: Monday, July 06, 2009 5:15 PM
Subject: I-D Action:draft-wang-dhc-ldn-option-00.txt


>A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> Title           : DHCP Option for Local Domain Name Discovery
> Author(s)       : Y. Wang, W. Wu
> Filename        : draft-wang-dhc-ldn-option-00.txt
> Pages           : 9
> Date            : 2009-07-06
> 
> This document defines the local domain name option for DHCPv4 and
> DHCPv6. This option is used by the Peer (DHCP client) to request
> local domain name described in [RFC5296] which is used to derive the
> local root key, e.g., DSRK defined in [RFC5295].
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-wang-dhc-ldn-option-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


--------------------------------------------------------------------------------


> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>

From root@core3.amsl.com  Tue Jul  7 12:00:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id C81FE28C4E9; Tue,  7 Jul 2009 12:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090707190001.C81FE28C4E9@core3.amsl.com>
Date: Tue,  7 Jul 2009 12:00:01 -0700 (PDT)
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action:draft-ietf-dhc-relay-id-suboption-07.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2009 19:00:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.


	Title           : The DHCPv4 Relay Agent Identifier Suboption
	Author(s)       : M. Stapp
	Filename        : draft-ietf-dhc-relay-id-suboption-07.txt
	Pages           : 7
	Date            : 2009-07-07

This memo defines a new Relay Agent Identifier suboption for the
Dynamic Host Configuration Protocol's (DHCP) Relay Agent Information
option.  The suboption carries a value that uniquely identifies the
relay agent device.  The value may be administratively-configured or
may be generated by the relay agent.  The suboption allows a DHCP
relay agent to include the identifier in the DHCP messages it sends.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-07.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-dhc-relay-id-suboption-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-07-07115659.I-D@ietf.org>


--NextPart--

From mjs@cisco.com  Tue Jul  7 12:08:16 2009
Return-Path: <mjs@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7165228C552 for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 12:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.141
X-Spam-Level: 
X-Spam-Status: No, score=-5.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xp08mjBoVQz for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 12:08:15 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 31D6C28C529 for <dhcwg@ietf.org>; Tue,  7 Jul 2009 12:07:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,363,1243814400"; d="scan'208,217";a="49614063"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 07 Jul 2009 19:07:02 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n67J72o5006133 for <dhcwg@ietf.org>; Tue, 7 Jul 2009 15:07:02 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n67J729M015723 for <dhcwg@ietf.org>; Tue, 7 Jul 2009 19:07:02 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 7 Jul 2009 15:07:01 -0400
Received: from mjs-mac.local ([161.44.70.135]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 7 Jul 2009 15:07:01 -0400
Message-ID: <4A539CD5.5050008@cisco.com>
Date: Tue, 07 Jul 2009 15:07:01 -0400
From: Mark Stapp <mjs@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <20090707190001.C81FE28C4E9@core3.amsl.com>
In-Reply-To: <20090707190001.C81FE28C4E9@core3.amsl.com>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jul 2009 19:07:01.0870 (UTC) FILETIME=[1BEE78E0:01C9FF36]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2411; t=1246993622; x=1247857622; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mjs@cisco.com; z=From:=20Mark=20Stapp=20<mjs@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20I-D=20Action=3Adraft-ietf-dhc -relay-id-suboption-07.txt |Sender:=20 |To:=20dhcwg@ietf.org; bh=yOW/TShotikC0nV7doQh24JdpCRU3IOaMzKOOMIg/WY=; b=ZtGUtvsyQKfMVi5Y0KzL8o2RjZK5rkCr1Fh72+jqb+oRo3MDLo8rOA7Iyu 3zNXdjQPsgKkscTQbHN/nIREdvl90kGy/jslTj+mor7JR3fln7YBbPwtnE+4 5/T0H3zpGO;
Authentication-Results: rtp-dkim-2; header.From=mjs@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Subject: Re: [dhcwg] I-D Action:draft-ietf-dhc-relay-id-suboption-07.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jul 2009 19:08:16 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The -06 version expired while on its way 'up' to the IESG. This -07
version just refreshes its timer; the only change in the text is an
update to the 2009 IETF trust language that was required to get it
published.<br>
<br>
Regards,<br>
Mark<br>
<br>
</tt><br>
<a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> wrote:
<blockquote cite="mid:20090707190001.C81FE28C4E9@core3.amsl.com"
 type="cite">
  <pre wrap="">A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.


	Title           : The DHCPv4 Relay Agent Identifier Suboption
	Author(s)       : M. Stapp
	Filename        : draft-ietf-dhc-relay-id-suboption-07.txt
	Pages           : 7
	Date            : 2009-07-07

This memo defines a new Relay Agent Identifier suboption for the
Dynamic Host Configuration Protocol's (DHCP) Relay Agent Information
option.  The suboption carries a value that uniquely identifies the
relay agent device.  The value may be administratively-configured or
may be generated by the relay agent.  The suboption allows a DHCP
relay agent to include the identifier in the DHCP messages it sends.

A URL for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-07.txt">http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-id-suboption-07.txt</a>

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
  </pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
dhcwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/dhcwg">https://www.ietf.org/mailman/listinfo/dhcwg</a>
  </pre>
</blockquote>
</body>
</html>

From bharat_joshi@infosys.com  Tue Jul  7 20:27:17 2009
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 851C13A6A48 for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 20:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFoxthBwaGwq for <dhcwg@core3.amsl.com>; Tue,  7 Jul 2009 20:27:16 -0700 (PDT)
Received: from KECGATE03.infosys.com (Kecgate03.infosys.com [122.98.10.31]) by core3.amsl.com (Postfix) with ESMTP id C701E3A6AE1 for <dhcwg@ietf.org>; Tue,  7 Jul 2009 20:27:15 -0700 (PDT)
X-TM-IMSS-Message-ID: <7138ea4e000c3c16@KECGATE03.infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by KECGATE03.infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.0) id 7138ea4e000c3c16 ; Wed, 8 Jul 2009 08:56:05 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub04.ad.infosys.com ([10.66.236.44]) with mapi; Wed, 8 Jul 2009 08:57:31 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Wed, 8 Jul 2009 08:54:42 +0530
Thread-Topic: DHCPv4 Relay Chaining
Thread-Index: AQHJ/3ui+aCwEy4ze0iJi1DfhXMJ7w==
Message-ID: <31D55C4D55BEED48A4459EB64567589A0F650BC9D6@BLRKECMBX02.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] DHCPv4 Relay Chaining
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2009 03:27:17 -0000

Hi=20All,

=20=20=20=20=20We=20have=20posted=20a=20new=20revision=20of=20our=20old=
=20draft=20on=20DHCPv4=20Relay=20Chaining.=20We=20decided=20to=20revive=
=20it=20now=20because=20we=20now=20have=20a=20draft=20that=20explain=20th=
e=20Layer=202=20Relay=20Agent=20functionality=20and=20the=20requirements=
=20of=20this=20work=20can=20be=20explained=20easily=20and=20we=20also=20s=
aw=20some=20renewed=20interest=20in=20this=20work=20from=20other=20quarte=
rs=20as=20well.

=20=20=20=20=20Please=20review=20the=20document=20and=20let=20us=20know=
=20your=20comments.=20The=20draft=20is=20available=20at:
http://www.ietf.org/internet-drafts/draft-kurapati-dhc-relay-chaining-dhc=
pv4-02.txt

Thanks,
Bharat
****************=20CAUTION=20-=20Disclaimer=20*****************
This=20e-mail=20contains=20PRIVILEGED=20AND=20CONFIDENTIAL=20INFORMATION=
=20intended=20solely=20
for=20the=20use=20of=20the=20addressee(s).=20If=20you=20are=20not=20the=
=20intended=20recipient,=20please=20
notify=20the=20sender=20by=20e-mail=20and=20delete=20the=20original=20mes=
sage.=20Further,=20you=20are=20not=20
to=20copy,=20disclose,=20or=20distribute=20this=20e-mail=20or=20its=20con=
tents=20to=20any=20other=20person=20and=20
any=20such=20actions=20are=20unlawful.=20This=20e-mail=20may=20contain=20=
viruses.=20Infosys=20has=20taken=20
every=20reasonable=20precaution=20to=20minimize=20this=20risk,=20but=20is=
=20not=20liable=20for=20any=20damage=20
you=20may=20sustain=20as=20a=20result=20of=20any=20virus=20in=20this=20e-=
mail.=20You=20should=20carry=20out=20your=20
own=20virus=20checks=20before=20opening=20the=20e-mail=20or=20attachment.=
=20Infosys=20reserves=20the=20
right=20to=20monitor=20and=20review=20the=20content=20of=20all=20messages=
=20sent=20to=20or=20from=20this=20e-mail=20
address.=20Messages=20sent=20to=20or=20from=20this=20e-mail=20address=20m=
ay=20be=20stored=20on=20the=20
Infosys=20e-mail=20system.
***INFOSYS********=20End=20of=20Disclaimer=20********INFOSYS***

From volz@cisco.com  Fri Jul 10 08:24:54 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B7B328C104 for <dhcwg@core3.amsl.com>; Fri, 10 Jul 2009 08:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.311
X-Spam-Level: 
X-Spam-Status: No, score=-6.311 tagged_above=-999 required=5 tests=[AWL=0.287,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkuae3PljBQs for <dhcwg@core3.amsl.com>; Fri, 10 Jul 2009 08:24:53 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 6FD373A6E57 for <dhcwg@ietf.org>; Fri, 10 Jul 2009 08:24:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,378,1243814400"; d="scan'208,217";a="85365131"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 10 Jul 2009 15:25:20 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n6AFPKQM010374;  Fri, 10 Jul 2009 08:25:20 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6AFPF3t002632; Fri, 10 Jul 2009 15:25:19 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 10 Jul 2009 11:25:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA0172.A22D1426"
Date: Fri, 10 Jul 2009 11:25:18 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210DA6822D@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <adf2a3a0907070220k728b1502i7e30e8c63056d136@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] RFC 3315 - Request message
Thread-Index: Acn+5TiM1XYZIyJTSdyY3ukRgvx89ACjOhAw
References: <adf2a3a0907070220k728b1502i7e30e8c63056d136@mail.gmail.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "ravi kumar" <ravikumar.lrk@gmail.com>, "DHC WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 10 Jul 2009 15:25:19.0508 (UTC) FILETIME=[A2585D40:01CA0172]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7780; t=1247239520; x=1248103520; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20RFC=203315=20-=20Request=20me ssage |Sender:=20; bh=y6kPEgD11bCxjXmn5I5scyDM63pfEiXQthKINrDe3t8=; b=hkFqjYoVspmStZpxBBSAKwBIHCH0LCAfZ0Hu1EGzO+b50Yo4ccyvyYrwx0 FY5YWeE4hLqL1PMeTkYuk+UPFPmgUf6Z957bTiVhM/xqNKgk/XucF4LQpVtp TVcd+H1hzO;
Authentication-Results: sj-dkim-4; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [dhcwg] RFC 3315 - Request message
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2009 15:24:54 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA0172.A22D1426
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

There is no requirement to include IAADDR options in IA_NA options in a
Request.

=20

However:

=20

If the client has addresses it is presently using, it may (should?)
include them.

=20

If the client received an Advertisement, it should include the addresses
from the Advertisement (copy the IAADDR options).=20

=20

If the client wants to request specific values for the preferred and
valid lifetimes, it can include an IAADDR option with a 0::0 address and
the values (some servers may then use them in considering what lifetimes
to assign).

=20

-          Bernie

=20

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of ravi kumar
Sent: Tuesday, July 07, 2009 5:21 AM
To: DHC WG
Subject: [dhcwg] RFC 3315 - Request message

=20

RFC 3315 specifies that IA option(s) is included in Request messages
sent by Dhcpv6 client.

=20

Is it necessary for client to include IAAddress option also as part of
IANA option. Is it not enough for client to include just IANA option,
with no IAAddress option in Request message.

=20

regards

Ravi


------_=_NextPart_001_01CA0172.A22D1426
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1129711194;
	mso-list-type:hybrid;
	mso-list-template-ids:660274026 872974544 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:10;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There is no requirement to include IAADDR options in =
IA_NA
options in a Request.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>However:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If the client has addresses it is presently using, it may
(should?) include them.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If the client received an Advertisement, it should =
include the
addresses from the Advertisement (copy the IAADDR options). =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>If the client wants to request specific values for the =
preferred
and valid lifetimes, it can include an IAADDR option with a 0::0 address =
and
the values (some servers may then use them in considering what lifetimes =
to
assign).<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bernie<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>ravi
kumar<br>
<b>Sent:</b> Tuesday, July 07, 2009 5:21 AM<br>
<b>To:</b> DHC WG<br>
<b>Subject:</b> [dhcwg] RFC 3315 - Request message<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal>RFC 3315 specifies that IA option(s) is included in =
Request
messages sent by Dhcpv6 client.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>Is it necessary for client to include IAAddress =
option
also&nbsp;as part of&nbsp;IANA option. Is it not enough for client to =
include
just IANA option, with no IAAddress option in Request =
message.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>regards<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal>Ravi<o:p></o:p></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01CA0172.A22D1426--

From Ted.Lemon@nominum.com  Mon Jul 13 08:34:51 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6285128C135 for <dhcwg@core3.amsl.com>; Mon, 13 Jul 2009 08:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6y2E+aPbCJvQ for <dhcwg@core3.amsl.com>; Mon, 13 Jul 2009 08:34:50 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by core3.amsl.com (Postfix) with ESMTP id B3AFC28C13F for <dhcwg@ietf.org>; Mon, 13 Jul 2009 08:34:49 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKSltUNltuASV/O8N6sAJX1RowRnIlCOxK@postini.com; Mon, 13 Jul 2009 08:35:20 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C9BD31B82B4 for <dhcwg@ietf.org>; Mon, 13 Jul 2009 08:35:29 -0700 (PDT)
Received: from [10.0.1.107] (64.81.227.56) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Mon, 13 Jul 2009 08:35:17 -0700
Message-ID: <C4591ADE-E808-4D8B-A933-2C63E1B95D9A@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
In-Reply-To: <C630DCE2.A5FF2%john_brzozowski@cable.comcast.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 13 Jul 2009 10:35:15 -0500
References: <C630DCE2.A5FF2%john_brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] Agenda items for IETF75 dhcwg - First Call
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 15:34:51 -0000

On May 13, 2009, at 7:24 PM, John Jason Brzozowski wrote:
> This is the first call for agenda items for the IETF 75 dhcwg  
> meeting in
> Stockholm.  Please send your requests directly to the chairs.

We didn't actually get any specific agenda items in response to this  
call.   Or at least none that landed in my inbox.   Does this mean  
that nobody is expecting to present anything at the DHC meeting at  
IETF75?   Can we free up that meeting slot?

:')

(We are due to send in a draft agenda by Wednesday, and a final agenda  
by Monday, so if you do have agenda items, it's time to send them in  
to us.   Today.)


From root@core3.amsl.com  Mon Jul 13 10:15:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 01A9D28C57F; Mon, 13 Jul 2009 10:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090713171502.01A9D28C57F@core3.amsl.com>
Date: Mon, 13 Jul 2009 10:15:01 -0700 (PDT)
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-leasequery-by-remote-id-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 17:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: DHCPv4 Leasequery by relay agent remote ID
	Author(s)	: P. Kurapati, D. Rao, B. Joshi
	Filename	: draft-ietf-dhc-leasequery-by-remote-id-02.txt
	Pages		: 27
	Date		: 2009-7-13
	
Some Relay Agents extract lease information from the DHCP message
   exchanged between the client and DHCP server.  This lease information
   is used by relay agents for various purposes like antispoofing,
   prevention of flooding.  RFC 4388 defines a mechanism for relay
   agents to retrieve the lease information from the DHCP server as and
   when this information is lost.  Existing leasequery mechanism is data
   driven which means that a relay agent can initiate the leasequery
   only when it starts receiving data from/to the clients.  In certain
   scenarios, this model is not scalable.  This document first looks at
   issues in existing mechanism and then proposes a new query type,
   query by remote ID, to address these issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-leasequery-by-remote-id-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-dhc-leasequery-by-remote-id-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-7-13100921.I-D@ietf.org>


--NextPart--


From root@core3.amsl.com  Mon Jul 13 13:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6DBC328C340; Mon, 13 Jul 2009 13:15:00 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090713201501.6DBC328C340@core3.amsl.com>
Date: Mon, 13 Jul 2009 13:15:01 -0700 (PDT)
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action:draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2009 20:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.


	Title           : DHCPv6 Relay Agent Assignment Notification (RAAN) Option
	Author(s)       : R. Droms, et al.
	Filename        : draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt
	Pages           : 8
	Date            : 2009-07-13

The DHCP Relay Agent Assignment Notification (RAAN) option is sent
from a DHCP server to a DHCP relay agent to inform the relay agent of
IPv6 addresses that have been assigned or IPv6 prefixes that have
been delegated to DHCP clients.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-dhc-dhcpv6-agentopt-delegate-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-07-13130104.I-D@ietf.org>


--NextPart--

From bharat_joshi@infosys.com  Mon Jul 13 20:23:28 2009
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2406C3A6359 for <dhcwg@core3.amsl.com>; Mon, 13 Jul 2009 20:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iXog7a+2vpzW for <dhcwg@core3.amsl.com>; Mon, 13 Jul 2009 20:23:27 -0700 (PDT)
Received: from KECGATE03.infosys.com (Kecgate03.infosys.com [122.98.10.31]) by core3.amsl.com (Postfix) with ESMTP id B70A03A6358 for <dhcwg@ietf.org>; Mon, 13 Jul 2009 20:23:26 -0700 (PDT)
X-TM-IMSS-Message-ID: <901b2c71000f2ed5@KECGATE03.infosys.com>
Received: from blrkechub02.ad.infosys.com ([10.66.236.42]) by KECGATE03.infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.0) id 901b2c71000f2ed5 ; Tue, 14 Jul 2009 08:51:50 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub02.ad.infosys.com ([10.66.236.42]) with mapi; Tue, 14 Jul 2009 08:53:24 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 14 Jul 2009 08:53:23 +0530
Thread-Topic: DHCPv4 Leasequery by relay agent remote ID draft
Thread-Index: AcoEMnHdYKINzwpsTMKU2TUBv/MXHg==
Message-ID: <31D55C4D55BEED48A4459EB64567589A0F6559BCCD@BLRKECMBX02.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] DHCPv4 Leasequery by relay agent remote ID draft
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2009 03:23:28 -0000

Hi All,

    We have published a new revision of DHCPv4 Leasequery by relay agent re=
mote ID' draft. Its available at: http://www.ietf.org/internet-drafts/draft=
-ietf-dhc-leasequery-by-remote-id-02.txt

    Please review the same and let us know your comments.

Thanks,
Bharat

From maxpassion@gmail.com  Wed Jul 15 01:05:59 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7ADDB3A6B22 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 01:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31a2SUZ12IHI for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 01:05:58 -0700 (PDT)
Received: from mail-vw0-f184.google.com (mail-vw0-f184.google.com [209.85.212.184]) by core3.amsl.com (Postfix) with ESMTP id B4A503A684C for <dhcwg@ietf.org>; Wed, 15 Jul 2009 01:05:58 -0700 (PDT)
Received: by vwj14 with SMTP id 14so3384019vwj.29 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 01:04:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=mHrV7sw5410hz2sjrZ1G53LH1VwTdgBaF+ptpWS9/9w=; b=p+Ms9wVvsoU1vabaygXOV7L4qfAiYCHwPt1wy/hSX7PxZ1aloJrGr8sY55j6bGP0qi 2EYu7n62I3qP6QXcDp4LOdUZmDamR2mdgUEHKDqObxUIdQanctDjOrUjkeSQUunmdJh5 gsRSFghJpd6NIWW4EPt4kDKiRlPIyAjfnAdYw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=GW8ue92fQFmYgEO+YMr3O+WD0jIk1tejGdYSDwofU4W76szBx3jF0ME17EchbP02/h gazohQ2KSPYYjFZxIZjfyTF+uGVXm7xtEqjNkN5SOMFraQ2a5nkgnm+i452kVHFRRNAr aq03p43YbqFVH5Ilu+IvAZsqgOEM1NMeI8Ks4=
MIME-Version: 1.0
Received: by 10.220.100.194 with SMTP id z2mr10478676vcn.38.1247644614310;  Wed, 15 Jul 2009 00:56:54 -0700 (PDT)
Date: Wed, 15 Jul 2009 15:56:54 +0800
Message-ID: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix and an IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 08:05:59 -0000

Hi,guys,
  I have a question about whether current DHCPv6 specification could
support assigning an IPv6 prefix and an IPv4 address simultaneously?


BR,
Dapeng Liu

From volz@cisco.com  Wed Jul 15 04:11:04 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 116BB3A68B9 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 04:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.369
X-Spam-Level: 
X-Spam-Status: No, score=-6.369 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w3m6iUE6+eqE for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 04:11:03 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 1DC6F3A6AD0 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 04:11:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAH9UXUqrR7PD/2dsb2JhbAC3BogjkQkFhAmBQg
X-IronPort-AV: E=Sophos;i="4.42,403,1243814400"; d="scan'208";a="177025334"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-3.cisco.com with ESMTP; 15 Jul 2009 11:02:47 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6FB2mpH020223;  Wed, 15 Jul 2009 04:02:48 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6FB2m2b020483; Wed, 15 Jul 2009 11:02:48 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 15 Jul 2009 07:02:47 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 15 Jul 2009 07:02:46 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
Thread-Index: AcoFIzO2VWIBJrmjQtmPA8Z+XwbgvAAGB6NQ
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "liu dapeng" <maxpassion@gmail.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 15 Jul 2009 11:02:47.0942 (UTC) FILETIME=[C9BEE260:01CA053B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1065; t=1247655768; x=1248519768; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Whether=20DHCPv6=20could=20su pport=20assigning=20an=20IPv6=20prefix=20andan=20IPv4=20addr ess=20simultaneously? |Sender:=20; bh=fpsFBO1nqacmgnprfMhGqw4Ey2Mr/TydIgFHXTyJ2aQ=; b=HHoj3cnwokgmtupG0Dq2vIF7mDT2Ky+X/W5ENZPCM8FW/53g/HkMQ4jGaE I7XTV25vJlqPYmxe7aPXuomavazcsgMmSCXLbvYTS2EKH98ImoLTkB5ytwPc lEnycnB69j;
Authentication-Results: sj-dkim-3; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 11:11:04 -0000

Did you really mean IPv4 address?

DHCPv6 only handles IPv6 prefixes and addresses, not IPv4. DHCPv4 is
used for IPv4.

This was discussed when DHCPv6 was being developed, but there was little
practical value to complicating DHCPv6 with supporting IPv4 as well --
after all DHCPv4 was already widely deployed and in use.

Other than saving the 4 messages (2 if rapid commit is used) for a
separate DHCPv4 exchange, why do you see this as being valuable?

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of liu dapeng
Sent: Wednesday, July 15, 2009 3:57 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix
andan IPv4 address simultaneously?

Hi,guys,
  I have a question about whether current DHCPv6 specification could
support assigning an IPv6 prefix and an IPv4 address simultaneously?


BR,
Dapeng Liu
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From tjc@ecs.soton.ac.uk  Wed Jul 15 04:21:30 2009
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DD163A68B9 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 04:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mtyhblRBcJe for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 04:21:29 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by core3.amsl.com (Postfix) with ESMTP id 5E68B3A67A6 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 04:21:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n6FBLTgl013730; Wed, 15 Jul 2009 12:21:29 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk n6FBLTgl013730
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1247656889; bh=H7E+y6uhxedUSeDcDlIdc0ashyc=; h=Date:From:To:Cc:Subject:References:Mime-Version:In-Reply-To; b=vrs120RXyEY7V0Bjm/xghwg3gfE50lf82Me2zPOVRECrNW+RHTziuFxd7QlcYZkXu MncOrygR/yq6FD8Mf17pktHoXgqE4xaqPU8hI2Pn43Dpqz2Ms+XIroLj0rMce9/2qx X76UOL/PX29kJJvp1Ag456t7+GtUitvbH9LdU438=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:21d:9ff:fe22:9fc]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:21e:c9ff:fe2e:e915]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id l6ECLY0448519138FX ret-id none; Wed, 15 Jul 2009 12:21:29 +0100
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n6FBLLeM009315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jul 2009 12:21:21 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id n6FBLLEj019590;  Wed, 15 Jul 2009 12:21:21 +0100
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id n6FBLL11019589; Wed, 15 Jul 2009 12:21:21 +0100
Date: Wed, 15 Jul 2009 12:21:21 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk>
Mail-Followup-To: "Bernie Volz (volz)" <volz@cisco.com>, liu dapeng <maxpassion@gmail.com>, dhcwg@ietf.org
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <20090715112120.GG12615@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: client=relay,forged,no_ptr,ipv6; mail=; rcpt=
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: n6FBLTgl013730
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 11:21:30 -0000

A number of the issues with this, and pros/cons of separate DHCv4/v6
services compared to DHCPv6 serving v4 data were discussed in RFC4477.

http://www.ietf.org/rfc/rfc4477.txt

This explains why the separate server appraoch was preferred (well,
both services could be run from one entity of course, and it would
be prudent to consider managing them consistently and even via a
combined interface).

If that's worth revisiting from 3 years of operational experience, 
any input would be welcome.

Tim

On Wed, Jul 15, 2009 at 07:02:46AM -0400, Bernie Volz (volz) wrote:
> Did you really mean IPv4 address?
> 
> DHCPv6 only handles IPv6 prefixes and addresses, not IPv4. DHCPv4 is
> used for IPv4.
> 
> This was discussed when DHCPv6 was being developed, but there was little
> practical value to complicating DHCPv6 with supporting IPv4 as well --
> after all DHCPv4 was already widely deployed and in use.
> 
> Other than saving the 4 messages (2 if rapid commit is used) for a
> separate DHCPv4 exchange, why do you see this as being valuable?
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of liu dapeng
> Sent: Wednesday, July 15, 2009 3:57 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix
> andan IPv4 address simultaneously?
> 
> Hi,guys,
>   I have a question about whether current DHCPv6 specification could
> support assigning an IPv6 prefix and an IPv4 address simultaneously?
> 
> 
> BR,
> Dapeng Liu
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

-- 
Tim



From behcetsarikaya@yahoo.com  Wed Jul 15 09:02:07 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A0453A69B2 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.126
X-Spam-Level: 
X-Spam-Status: No, score=-2.126 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ohzJD93a0l1 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:02:06 -0700 (PDT)
Received: from n1.bullet.mail.re3.yahoo.com (n1.bullet.mail.re3.yahoo.com [68.142.237.108]) by core3.amsl.com (Postfix) with SMTP id 97A7D3A6947 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:02:06 -0700 (PDT)
Received: from [68.142.237.90] by n1.bullet.mail.re3.yahoo.com with NNFMP; 15 Jul 2009 16:01:33 -0000
Received: from [67.195.9.82] by t6.bullet.re3.yahoo.com with NNFMP; 15 Jul 2009 16:01:33 -0000
Received: from [67.195.9.107] by t2.bullet.mail.gq1.yahoo.com with NNFMP; 15 Jul 2009 16:01:33 -0000
Received: from [127.0.0.1] by omp111.mail.gq1.yahoo.com with NNFMP; 15 Jul 2009 16:01:33 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 278294.93158.bm@omp111.mail.gq1.yahoo.com
Received: (qmail 70227 invoked by uid 60001); 15 Jul 2009 16:01:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1247673693; bh=7pYnYFo5wCbJT7BtSziiXGRdqwKo7/loLk1281h72/Q=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=sWwgkGoIINIf5DfhpiSkzl/aejicAy+F9KyH4ABczkmpFbyR0cKY7sYIk6l3mheNFmCUZAU8XhwybJjeUwHxvtJgd5B1Drd9GTw055b3GKKbSIgVpJZVsG17ZqHWlng7Cpxg/yYsp2jnCWn3tJ90HHwkPR5rXT6ykXEajQg9E/w=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=VbrPFcctsEFoHttYUdwko26umg8A9xo5rNkyj3Sr4fhxQKVpFLW+pfRWYpDuAdRYQssMdAAyIJoJG3cdZ+gCKsx2Drt2vToJUqcXQ+UfZ8Bdw3udw2ULpdajhxh/5LMTcl2rxdLTG2ismD7J9U4PtpQkNwdJfaB6zq7ELMjeOx4=;
Message-ID: <187423.66828.qm@web111415.mail.gq1.yahoo.com>
X-YMail-OSG: xRIjQDUVM1mRaGSj7Re3SWCWd2vCVq2mHRjFyWQYT0CFnjpiFgvP78prH9u5Yb1cGM1leTFFdKrdZwNL2Qh0E8ZtZC2QI4t9VHbIvCSmJYIzBmB0HNIR6TDbW.HmffWCnOS02eMV6gdBy5S0lf_Pt8sF9bj6cQIBj80h3xUMtc8qaoYPRn6dzvpiHggHg_5YrHfM6yq3b6TFMRifllsaBABwo0It9_qvWH9Q_3eNAgViMuzuLRykLU.DL1jzOzeTg97AaJD4ncf.wlM_0gPQ_e4QwAcYEn0tnmgJ3SYzPp.OAiOLYPmHCjzxhtpJQc936XuishaKv0c5tnhYuhN7RzM-
Received: from [206.16.17.212] by web111415.mail.gq1.yahoo.com via HTTP; Wed, 15 Jul 2009 09:01:33 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.289.15
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com>
Date: Wed, 15 Jul 2009 09:01:33 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: liu dapeng <maxpassion@gmail.com>, dhcwg@ietf.org
In-Reply-To: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix and an IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 16:02:07 -0000

Hi Dapeng,=0A=A0 My answer would be yes.=0APlease take a look at http://too=
ls.ietf.org/html/draft-ietf-mip6-hiopt-17=0Athis draft which is in RFC Edit=
or queue defines DHCPv6 options to carry IPv4 address.=0A=0AVice-versa is a=
lso possible, please look at http://tools.ietf.org/id/draft-xia-mext-hioptv=
4-00.txt=A0where we defined DHCPv4 option to carry IPv6 address.=0A=0ARegar=
ds,=0A=0ABehcet=0A=0A=0A=0A----- Original Message ----=0A> From: liu dapeng=
 <maxpassion@gmail.com>=0A> To: dhcwg@ietf.org=0A> Sent: Wednesday, July 15=
, 2009 2:56:54 AM=0A> Subject: [dhcwg] Whether DHCPv6 could support assigni=
ng an IPv6 prefix and an IPv4 address simultaneously?=0A> =0A> Hi,guys,=0A>=
 =A0 I have a question about whether current DHCPv6 specification could=0A>=
 support assigning an IPv6 prefix and an IPv4 address simultaneously?=0A> =
=0A> =0A> BR,=0A> Dapeng Liu=0A> __________________________________________=
_____=0A> dhcwg mailing list=0A> dhcwg@ietf.org=0A> https://www.ietf.org/ma=
ilman/listinfo/dhcwg=0A=0A=0A=0A      


From maxpassion@gmail.com  Wed Jul 15 09:42:29 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A48028C13A for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.16
X-Spam-Level: 
X-Spam-Status: No, score=-2.16 tagged_above=-999 required=5 tests=[AWL=-0.161,  BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M5EiRoH3yNWM for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:42:28 -0700 (PDT)
Received: from mail-vw0-f184.google.com (mail-vw0-f184.google.com [209.85.212.184]) by core3.amsl.com (Postfix) with ESMTP id F17713A6A56 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:42:27 -0700 (PDT)
Received: by vwj14 with SMTP id 14so3638450vwj.29 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:42:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5+57RGk9MjBT3DyEL8iA0odu0bJC+VOAGlRlUEVNhrw=; b=Tsxcob2hxfhGMb4Sg/Aiv8ezVsbgvWWTRx5BTn9O1U2pOUTf3rh9lYVeaZhqTus4HJ iqmgVWd9ZQKct29WQt6ajK3vwEeByzxI5weRfRJaamNZKKYvaYmNyzTgHVRJW7+vqltm de8ymkAMw3f4ExaiShT+f6Sf0exgbuUF6JyQc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QBB4Vi64fo0j7w+enqxvLxpDt8q5AawPkXKV5fjJAFpzgvWLboUh3vXM9qmBMEC1vo T9UhCkpxhiuSAc9yOkvqMXGDYmSLqglzxItKR+1h805/WDnJ39/pFWf28JdSay6DT3wZ EDOtTjyd8waBjcbFPnZRZzgQ5VjIZTvvdMMb8=
MIME-Version: 1.0
Received: by 10.220.97.13 with SMTP id j13mr11310789vcn.35.1247674391216; Wed,  15 Jul 2009 09:13:11 -0700 (PDT)
In-Reply-To: <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <20090715112120.GG12615@login.ecs.soton.ac.uk> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk>
Date: Thu, 16 Jul 2009 00:13:11 +0800
Message-ID: <25e1aaa40907150913x495734f2i81a8a7b9da2f7279@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: tjc@ecs.soton.ac.uk
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 16:42:29 -0000

Thanks Tim, please see inline

2009/7/15, Tim Chown <tjc@ecs.soton.ac.uk>:
> A number of the issues with this, and pros/cons of separate DHCv4/v6
> services compared to DHCPv6 serving v4 data were discussed in RFC4477.
>
> http://www.ietf.org/rfc/rfc4477.txt
>
> This explains why the separate server appraoch was preferred (well,
> both services could be run from one entity of course, and it would
> be prudent to consider managing them consistently and even via a
> combined interface).
>
> If that's worth revisiting from 3 years of operational experience,
> any input would be welcome.

We are exploring an host based IPv4/IPv6 transition mechanism named
PNAT and  we are considering to use DHCPv6 to assign an IPv6 prefix
and an IPv4 address for the host at the same time to facilitate PNAT.
http://www.ietf.org/mail-archive/web/behave/current/msg06206.html

Maybe I could post a draft about the required extention of DHCPv6 and
use it for our discussion.

BR,
Dapeng Liu

> Tim
>
> On Wed, Jul 15, 2009 at 07:02:46AM -0400, Bernie Volz (volz) wrote:
>> Did you really mean IPv4 address?
>>
>> DHCPv6 only handles IPv6 prefixes and addresses, not IPv4. DHCPv4 is
>> used for IPv4.
>>
>> This was discussed when DHCPv6 was being developed, but there was little
>> practical value to complicating DHCPv6 with supporting IPv4 as well --
>> after all DHCPv4 was already widely deployed and in use.
>>
>> Other than saving the 4 messages (2 if rapid commit is used) for a
>> separate DHCPv4 exchange, why do you see this as being valuable?
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
>> Of liu dapeng
>> Sent: Wednesday, July 15, 2009 3:57 AM
>> To: dhcwg@ietf.org
>> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix
>> andan IPv4 address simultaneously?
>>
>> Hi,guys,
>>   I have a question about whether current DHCPv6 specification could
>> support assigning an IPv6 prefix and an IPv4 address simultaneously?
>>
>>
>> BR,
>> Dapeng Liu
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
> --
> Tim
>
>
>

From David_Hankins@isc.org  Wed Jul 15 09:47:51 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 625EC3A6F06 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFqNLxL5L94u for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:47:50 -0700 (PDT)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 763513A6B45 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:47:50 -0700 (PDT)
Received: from david.isc.org (c-67-188-70-48.hsd1.ca.comcast.net [67.188.70.48] (may be forged)) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n6FGkLAO016903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:46:22 -0700
Received: by david.isc.org (Postfix, from userid 10200) id 92ABF16E1BA; Wed, 15 Jul 2009 09:45:57 -0700 (PDT)
Date: Wed, 15 Jul 2009 09:45:57 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20090715164557.GA4526@isc.org>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
In-Reply-To: <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix	andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 16:47:51 -0000

--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 15, 2009 at 07:02:46AM -0400, Bernie Volz (volz) wrote:
> Other than saving the 4 messages (2 if rapid commit is used) for a
> separate DHCPv4 exchange, why do you see this as being valuable?

For awhile I toyed with the idea because DHCPv6's unconfigured
communications model is superior (and because of it, we don't have
worries like non-implementation of udp fragmentation and so forth).

It seems like a complication because this creates now two IPv4
configuration sources and we're already in bad enough shape in
this regard; two IPv6 sources of configuration (RA and DHCPv6), and
two sources of IP-nonspecific configuration state (DHCPv4 and DHCPv6).

The dependency graph is plenty bad enough.

But the final model after an IPv4-capable-DHCPv6 is well deployed
would be for one source of configuration (DHCPv6 only), a net
simplification, and a schedule to retire DHCPv4 without relying on
retiring IPv4 first (or ever).

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFKXgfFcXeLeWu2vmoRAnjoAKC3ufzaF17vgCJ5/z5EJ4DYJja9gACeItQc
MEsqqlZpZ+55i1SSIRv2CQ0=
=GOXq
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--

From maxpassion@gmail.com  Wed Jul 15 09:58:16 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97FB528C14A for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.142
X-Spam-Level: 
X-Spam-Status: No, score=-2.142 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCHXkk05bbIL for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 09:58:15 -0700 (PDT)
Received: from mail-vw0-f184.google.com (mail-vw0-f184.google.com [209.85.212.184]) by core3.amsl.com (Postfix) with ESMTP id C1CE128C118 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:58:15 -0700 (PDT)
Received: by vwj14 with SMTP id 14so3649778vwj.29 for <dhcwg@ietf.org>; Wed, 15 Jul 2009 09:58:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=C6wdT+ymwvMozxGjZ0geFQbjmHERhF+BVydrrQVQ3x0=; b=nv8YYr1Q515sseIFgqnxYsewxgwG2W3nucz2jhAzgem9r11pA/aMxVjCNiALhiwGv+ PRmdDiTnsh0TDtMtXZz59/M/hfDUl4sTVthXeTS9MPKffXOlUFWOv78RGXgIpvlt2GJ9 A60NDlEZwQ8Dv80fOCjyDuoLUJPZvP9apc33o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JkCtbzfaxFR7yQyMchmA/pMEoDY3agzldgCJf6yOkIBWkrv6RoLwnGsWVwHAvhn0mL o2VDnWsZJGoCCMZi+I0vJ9epRSIM37ZsUQz6nPRpxj9oeDl8mSbPt0ZS6frIRz9YUVDU kQaJBnMyqRzlSOL8Z+YD0lbUKBbEP3IVJ7V+w=
MIME-Version: 1.0
Received: by 10.220.72.18 with SMTP id k18mr11153718vcj.83.1247675295918; Wed,  15 Jul 2009 09:28:15 -0700 (PDT)
In-Reply-To: <187423.66828.qm@web111415.mail.gq1.yahoo.com>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <187423.66828.qm@web111415.mail.gq1.yahoo.com>
Date: Thu, 16 Jul 2009 00:28:15 +0800
Message-ID: <25e1aaa40907150928q129f575l7ab8e10345af51fc@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix and an IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 16:58:16 -0000

Hi, Behcet,
   Thank you for your information. But it seems that the extentions
could only be used for MIP6/DSMIP home information discovery. We are
looking for an extention which can be used for PNAT (you can refer my
reply to Tim).

BR,
Dapeng Liu

2009/7/16, Behcet Sarikaya <behcetsarikaya@yahoo.com>:
>
> Hi Dapeng,
>   My answer would be yes.
> Please take a look at http://tools.ietf.org/html/draft-ietf-mip6-hiopt-17
> this draft which is in RFC Editor queue defines DHCPv6 options to carry IPv4
> address.
>
> Vice-versa is also possible, please look at
> http://tools.ietf.org/id/draft-xia-mext-hioptv4-00.txt where we defined
> DHCPv4 option to carry IPv6 address.
>
> Regards,
>
> Behcet
>
>
>
> ----- Original Message ----
>> From: liu dapeng <maxpassion@gmail.com>
>> To: dhcwg@ietf.org
>> Sent: Wednesday, July 15, 2009 2:56:54 AM
>> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix and
>> an IPv4 address simultaneously?
>>
>> Hi,guys,
>>   I have a question about whether current DHCPv6 specification could
>> support assigning an IPv6 prefix and an IPv4 address simultaneously?
>>
>>
>> BR,
>> Dapeng Liu
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>
>
>
>

From Ted.Lemon@nominum.com  Wed Jul 15 10:10:44 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F4253A6999 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 10:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yw1-aJL-eU85 for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 10:10:43 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with ESMTP id 74F7E3A684B for <dhcwg@ietf.org>; Wed, 15 Jul 2009 10:10:43 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKSl4M9fK2gDuP2O2+61MZFRZ/0flrpcqQ@postini.com; Wed, 15 Jul 2009 10:11:16 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E87CA1B8320; Wed, 15 Jul 2009 09:48:50 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 15 Jul 2009 09:48:38 -0700
Message-ID: <2C46F3D8-BE25-49BB-A807-CBAD5C8A46BA@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: liu dapeng <maxpassion@gmail.com>
In-Reply-To: <25e1aaa40907150913x495734f2i81a8a7b9da2f7279@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 15 Jul 2009 11:48:34 -0500
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <20090715112120.GG12615@login.ecs.soton.ac.uk> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk> <25e1aaa40907150913x495734f2i81a8a7b9da2f7279@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: dhcwg <dhcwg@ietf.org>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 17:10:44 -0000

On Jul 15, 2009, at 11:13 AM, liu dapeng wrote:
> We are exploring an host based IPv4/IPv6 transition mechanism named
> PNAT and  we are considering to use DHCPv6 to assign an IPv6 prefix
> and an IPv4 address for the host at the same time to facilitate PNAT.

My question about this is, why not just use DHCPv4 to get the IPv4  
address?


From Ted.Lemon@nominum.com  Wed Jul 15 11:56:20 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48DE73A693A for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 11:56:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.164
X-Spam-Level: 
X-Spam-Status: No, score=-6.164 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eYIiSW4Ws1l for <dhcwg@core3.amsl.com>; Wed, 15 Jul 2009 11:56:19 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by core3.amsl.com (Postfix) with ESMTP id 470AE3A6E7F for <dhcwg@ietf.org>; Wed, 15 Jul 2009 11:56:19 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKSl4mWTp6yarnC7o3xLBj2F2e98Qwk6AX@postini.com; Wed, 15 Jul 2009 11:56:52 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C216C1B831D for <dhcwg@ietf.org>; Wed, 15 Jul 2009 11:27:40 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Wed, 15 Jul 2009 11:27:28 -0700
Message-ID: <CAF88CB7-8DA6-4E5B-A9F0-9E488B1C8CB8@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhcwg WG <dhcwg@ietf.org>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 15 Jul 2009 13:27:24 -0500
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] Draft meeting agenda for Stockholm...
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 18:56:20 -0000

If you have anything you want to add, please contact John or me before  
Friday.


                        DHC WG Agenda - IETF 75
                        0900-1130 2009-07-31
                 (Last revised 2009-07-15 12:51 PM CT)
                 -------------------------------------

Administrivia                              Chairs                10  
minutes
         Agenda bashing; blue sheets; scribe; Jabber scribe
         Draft last call and adoption announcements

DHCP Option for Local Domain Name Discovery
                                            Y. Wang/Q. Wu          5  
minutes
         <draft-wang-dhc-ldn-option-00.txt>

IPv6 via IPv4 Service Provider Networks    M. Townsley/O. Troan   5  
minutes
         <draft-townsley-ipv6-6rd-00.txt>
         Document contains a DHCP option; request for WG review.

DHCPv6 Relay Agent Assignment Notification Option
                                            Chairs                10  
minutes
         <draft-ietf-dhc-dhcpv6-agentopt-delegate-04>
         Review discussion; ready for WG last call?

Authentication Extensions for the Dynamic Host Configuration Protocol
                                            Chairs                10  
minutes
         <draft-pruss-dhcp-auth-dsl-04>
         <draft-brzozowski-dhcp-eap-analysis-01>
                 Current status/discussion

                                                                   
-----------
                                                                  40  
minutes



From Ted.Lemon@nominum.com  Fri Jul 17 08:15:11 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CE003A6925 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 08:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhPauh3Lse+g for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 08:15:11 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by core3.amsl.com (Postfix) with ESMTP id AE1ED3A6A0D for <dhcwg@ietf.org>; Fri, 17 Jul 2009 08:15:10 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKSmCVn/WStJONhqX47OCdInS/oyjiZosF@postini.com; Fri, 17 Jul 2009 08:15:44 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 13FA91B8353 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 08:15:55 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 17 Jul 2009 08:15:42 -0700
Message-ID: <171BA341-AC46-465C-958A-BF266D38EA23@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhcwg WG <dhcwg@ietf.org>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 10:15:39 -0500
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] Reminder: please get any meeting agenda items to us by 5:00 Pacific today.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2009 15:15:11 -0000

Currently there are only four items on the agenda, so if you have  
something don't be shy about it.


From Damien.Neil@nominum.com  Fri Jul 17 12:38:06 2009
Return-Path: <Damien.Neil@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFB083A6EDA for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 12:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w26libldIOaV for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 12:38:06 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id DF8D43A67C2 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 12:38:05 -0700 (PDT)
Received: from source ([64.89.228.228]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKSmDTPwMrzEBQq2SDx/GhVew1XW78n7GX@postini.com; Fri, 17 Jul 2009 12:38:40 PDT
Received: from gtp126191.iol.unh.edu (gtp126191.iol.unh.edu [132.177.126.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by shell-ng.nominum.com (Postfix) with ESMTP id 9B8AA1A8206 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 12:38:38 -0700 (PDT) (envelope-from neild@nominum.com)
Message-Id: <105EED7F-0CE5-4902-AA48-28C785128355@nominum.com>
From: Damien Neil <Damien.Neil@nominum.com>
To: DHC-WG WG <dhcwg@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 15:38:37 -0400
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] Renewing an empty IA
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2009 19:38:06 -0000

A minor question of conforming behavior that came up here:

How should a server handle a Renew message which contains an IA_NA  
that contains no IAADDR options?

              - Damien

From behcetsarikaya@yahoo.com  Fri Jul 17 13:21:29 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83DA628C300 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 13:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THQ9RtSHoqai for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 13:21:28 -0700 (PDT)
Received: from n61.bullet.mail.sp1.yahoo.com (n61.bullet.mail.sp1.yahoo.com [98.136.44.37]) by core3.amsl.com (Postfix) with SMTP id 9465F28C323 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 13:21:25 -0700 (PDT)
Received: from [216.252.122.216] by n61.bullet.mail.sp1.yahoo.com with NNFMP; 17 Jul 2009 20:20:44 -0000
Received: from [67.195.9.83] by t1.bullet.sp1.yahoo.com with NNFMP; 17 Jul 2009 20:20:44 -0000
Received: from [67.195.9.107] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 17 Jul 2009 20:20:44 -0000
Received: from [127.0.0.1] by omp111.mail.gq1.yahoo.com with NNFMP; 17 Jul 2009 20:20:44 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 325092.99361.bm@omp111.mail.gq1.yahoo.com
Received: (qmail 97403 invoked by uid 60001); 17 Jul 2009 20:20:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1247862044; bh=RPTL2kVwqb+6arR3fhp8jyZkKzWiPGTlxvkkiqEOjQY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nAdneo8Bc4U73ipmt/ctijvnXUGckQmECTGHKVrtlHWJPCNUpoiq8LkkkJJFFGZq10XggRoRPQv9Xdi9mfZgb/gU4KMISStm/4gk+5j0GJTxCbZhHw1Yzqc/lZ1VEvUc+JPBuKw0OuBwMRFNv6LU/sH/BDN+wfSkcT0gnk6qrm4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=PwRKFZ4eWEVWSTGyMoCCmj1T+tPFEONVxJQPw147PydMdIlcivXy8ak6Tp7x2Iw6RIiROmCugQIJopwtoBa/UY0pV4/V2h0eG6VvO7d+m8QeDWmFrwOLardhJgFXWDHyT47usZD48xImEgmvJdOcEWx9qmFQ2uOAJEUUs96GvCk=;
Message-ID: <141413.96341.qm@web111402.mail.gq1.yahoo.com>
X-YMail-OSG: Sfp0e1YVM1kMzYSxXn7Qu3ctjinYpvMMSljhhbDJpqYktIBYK3TbVnb6Zpo8TbPHz7qN_87zI8m8nrwnvlMtNvQWiHIgu1OyAzm54.SLm4wpymk0gwztSqYulh9C5xPczR66mtaw087Zv6ykwYZxZV2Se_.xciWUwvviLeDz7oAQGQ2x4BF9tRg.zIjb.J31wjqE.Om31GMeT16lBAy0Qu4327r32GETiWR1A2ymWxGG1ZFn2loIOixasJYOzEBLk39uGAIVWnqQwBinmbjf4LA2u5kD4IKRE6Z0BbfhMXR9BCnsIfjA9IjGUG2Zw8GCGIb8Mkeo5fggmHJO2NOG6oQ-
Received: from [206.16.17.212] by web111402.mail.gq1.yahoo.com via HTTP; Fri, 17 Jul 2009 13:20:44 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.289.15
References: <171BA341-AC46-465C-958A-BF266D38EA23@nominum.com>
Date: Fri, 17 Jul 2009 13:20:44 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhcwg WG <dhcwg@ietf.org>
In-Reply-To: <171BA341-AC46-465C-958A-BF266D38EA23@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dhcwg] Reminder: please get any meeting agenda items to us by 5:00 Pacific today.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2009 20:21:29 -0000

Hi Ted,=0A=A0 I would like to present our draft:=0Ahttp://tools.ietf.org/id=
/draft-xia-mext-hioptv4-00.txt=0AA short slot would do.=0A=0AThanks,=0A=0AB=
ehcet=0A=0A=0A=0A----- Original Message ----=0A> From: Ted Lemon <Ted.Lemon=
@nominum.com>=0A> To: dhcwg WG <dhcwg@ietf.org>=0A> Sent: Friday, July 17, =
2009 10:15:39 AM=0A> Subject: [dhcwg] Reminder: please get any meeting agen=
da items to us by 5:00 Pacific today.=0A> =0A> Currently there are only fou=
r items on the agenda, so if you have something =0A> don't be shy about it.=
=0A> =0A> _______________________________________________=0A> dhcwg mailing=
 list=0A> dhcwg@ietf.org=0A> https://www.ietf.org/mailman/listinfo/dhcwg=0A=
=0A=0A=0A      


From Ted.Lemon@nominum.com  Fri Jul 17 16:54:59 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 150543A6925 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 16:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.49
X-Spam-Level: 
X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CINoDLCEHTVJ for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 16:54:58 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by core3.amsl.com (Postfix) with ESMTP id 2CBC83A69BA for <dhcwg@ietf.org>; Fri, 17 Jul 2009 16:54:57 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKSmEPckPewVqPjiGU2SwsK6BSDqhrq7oS@postini.com; Fri, 17 Jul 2009 16:55:32 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 88EBD1B8338; Fri, 17 Jul 2009 16:55:41 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 17 Jul 2009 16:55:28 -0700
Message-ID: <EBE3ECB1-30C0-4569-AE5A-3BC99BE4E8F4@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
In-Reply-To: <141413.96341.qm@web111402.mail.gq1.yahoo.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 18:55:25 -0500
References: <171BA341-AC46-465C-958A-BF266D38EA23@nominum.com> <141413.96341.qm@web111402.mail.gq1.yahoo.com>
X-Mailer: Apple Mail (2.935.3)
Cc: dhcwg WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Reminder: please get any meeting agenda items to us by 5:00 Pacific today.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2009 23:54:59 -0000

Okay, I've added you to the agenda.

From trac@tools.ietf.org  Fri Jul 17 17:49:07 2009
Return-Path: <trac@tools.ietf.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF2463A6A59 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 17:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6GgdWh+1s6X for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 17:49:06 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:1112:1:214:22ff:fe1f:1e54]) by core3.amsl.com (Postfix) with ESMTP id 50B953A698E for <dhcwg@ietf.org>; Fri, 17 Jul 2009 17:49:06 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1MRy7P-0005fm-PO; Fri, 17 Jul 2009 17:49:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="ascii"
Content-Transfer-Encoding: 7bit
From: "dhc issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.1
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.1, by Edgewall Software
To: john_brzozowski@cable.comcast.com, rdroms@cisco.com
X-Trac-Project: dhc
Date: Sat, 18 Jul 2009 00:49:39 -0000
X-URL: http://tools.ietf.org/wg/dhc/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dhc/trac/ticket/24#comment:5
Message-ID: <066.f287d2f856a9c0db6ad0243da763de2d@tools.ietf.org>
References: <057.4c5c3c9ef825220a23ddf7395bfada48@tools.ietf.org>
X-Trac-Ticket-ID: 24
In-Reply-To: <057.4c5c3c9ef825220a23ddf7395bfada48@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john_brzozowski@cable.comcast.com, rdroms@cisco.com, dhcwg@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] [dhc] #24: Cover sheet for draft-ietf-dhc-relay-id-suboption
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: dhcwg@ietf.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2009 00:49:07 -0000

#24: Cover sheet for draft-ietf-dhc-relay-id-suboption
------------------------------------------+---------------------------------
 Reporter:  rdroms@cisco.com              |        Owner:  john_brzozowski@cable.comcast.com
     Type:  task                          |       Status:  new                              
 Priority:  major                         |    Milestone:                                   
Component:  relay-id-suboption            |      Version:                                   
 Severity:  Waiting for Shepherd Writeup  |   Resolution:                                   
 Keywords:                                |  
------------------------------------------+---------------------------------
Changes (by john_brzozowski@cable.comcast.com):

  * owner:  Ted.Lemon@nominum.com => john_brzozowski@cable.comcast.com


-- 
Ticket URL: <http://trac.tools.ietf.org/wg/dhc/trac/ticket/24#comment:5>
dhc <http://tools.ietf.org/wg/dhc/>


From Ted.Lemon@nominum.com  Fri Jul 17 20:55:10 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6FC6F3A6EF8 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 20:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oInVopmR8+jF for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 20:55:09 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id 722543A6EF3 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 20:55:06 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKSmFHmR0DmuCrlAdjZKwisjRrbut5rLEM@postini.com; Fri, 17 Jul 2009 20:55:09 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CE74F1B8354 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 20:55:16 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 17 Jul 2009 20:55:04 -0700
Message-ID: <908CD1B6-F2B4-414A-84F5-CB62DB82A48E@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
In-Reply-To: <066.f287d2f856a9c0db6ad0243da763de2d@tools.ietf.org>
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 22:55:01 -0500
References: <057.4c5c3c9ef825220a23ddf7395bfada48@tools.ietf.org> <066.f287d2f856a9c0db6ad0243da763de2d@tools.ietf.org>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] [dhc] #24: Cover sheet for draft-ietf-dhc-relay-id-suboption
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2009 03:55:10 -0000

On Jul 17, 2009, at 7:49 PM, dhc issue tracker wrote:
> #24: Cover sheet for draft-ietf-dhc-relay-id-suboption

Does this stuff need to go to the working group mailing list?


From Ted.Lemon@nominum.com  Fri Jul 17 20:59:51 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 935063A6EF3 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 20:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XcYuJiUmcU7 for <dhcwg@core3.amsl.com>; Fri, 17 Jul 2009 20:59:51 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id AA08F3A6EF5 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 20:59:50 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKSmFIrp2nC2IGk8alWbT8xTfTYm/xDICl@postini.com; Fri, 17 Jul 2009 20:59:50 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 182881B8354 for <dhcwg@ietf.org>; Fri, 17 Jul 2009 20:59:54 -0700 (PDT)
Received: from vpna-148.vpn.nominum.com (64.89.227.148) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 17 Jul 2009 20:59:41 -0700
Message-ID: <8C27B013-EEE8-4FB7-929E-D8A946B18C1D@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
In-Reply-To: <908CD1B6-F2B4-414A-84F5-CB62DB82A48E@nominum.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 17 Jul 2009 22:59:38 -0500
References: <057.4c5c3c9ef825220a23ddf7395bfada48@tools.ietf.org> <066.f287d2f856a9c0db6ad0243da763de2d@tools.ietf.org> <908CD1B6-F2B4-414A-84F5-CB62DB82A48E@nominum.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] [dhc] #24: Cover sheet for draft-ietf-dhc-relay-id-suboption
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2009 03:59:51 -0000

On Jul 17, 2009, at 10:55 PM, Ted Lemon wrote:
> Does this stuff need to go to the working group mailing list?

Oops, that was for John.   Sorry.   But maybe it was a good  
question.   Personally I find stuff like this extremely unhelpful, but  
maybe others on the list would find it useful?


From denghui02@gmail.com  Mon Jul 20 08:26:57 2009
Return-Path: <denghui02@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E93028C0E4 for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.872
X-Spam-Level: 
X-Spam-Status: No, score=-1.872 tagged_above=-999 required=5 tests=[AWL=0.127,  BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQcpdm9wFzAC for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:26:54 -0700 (PDT)
Received: from mail-px0-f184.google.com (mail-px0-f184.google.com [209.85.216.184]) by core3.amsl.com (Postfix) with ESMTP id 0491D3A67E5 for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:26:53 -0700 (PDT)
Received: by pxi14 with SMTP id 14so194522pxi.29 for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:26:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EwpwKwX4jp1xe9vzf8DZkTwM4CqkmitpSXy3uh9hu7c=; b=Ka9svoGxOuS0TW0cdrvazPcVKw8PNFwm6qkk83+Id8GLesFYSOd2FV4dXo7CVJY+zX K4AYDiF/8xpChCE42z0Z9YzMk5YUmmXlPQDwjOPs07BV1woEoMIyxL+zAqz5jZBt1cj/ AqM3r7lT5lYY/+jLagcF9AoUFbopmoiBwKVVY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xi8dk7WleDUzJOVh7ndXda7jKW/Pu+tw3PvI8O/Oq8Z8tk6egvo24YVL7u64fuGKhI HM6t3F/hfsQTNtFwf1r8cGhmBv7qNiXadu8fjuAGgP/pnCPbCzuq1S/ZF5DF1gF47s1G WplRfAUFTM9hC/cav6rKZt/hugqVNCnaNJEGw=
MIME-Version: 1.0
Received: by 10.142.229.6 with SMTP id b6mr973173wfh.88.1248103606790; Mon, 20  Jul 2009 08:26:46 -0700 (PDT)
In-Reply-To: <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
Date: Mon, 20 Jul 2009 23:26:46 +0800
Message-ID: <1d38a3350907200826u61c202fep44d8d92d8fa9fc32@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2009 15:26:57 -0000

the scenario is about a dual stack host but only IPv6 access network
is available.

-Hui

2009/7/15 Bernie Volz (volz) <volz@cisco.com>:
> Did you really mean IPv4 address?
>
> DHCPv6 only handles IPv6 prefixes and addresses, not IPv4. DHCPv4 is
> used for IPv4.
>
> This was discussed when DHCPv6 was being developed, but there was little
> practical value to complicating DHCPv6 with supporting IPv4 as well --
> after all DHCPv4 was already widely deployed and in use.
>
> Other than saving the 4 messages (2 if rapid commit is used) for a
> separate DHCPv4 exchange, why do you see this as being valuable?
>
> - Bernie
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of liu dapeng
> Sent: Wednesday, July 15, 2009 3:57 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix
> andan IPv4 address simultaneously?
>
> Hi,guys,
> =A0I have a question about whether current DHCPv6 specification could
> support assigning an IPv6 prefix and an IPv4 address simultaneously?
>
>
> BR,
> Dapeng Liu
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

From denghui02@gmail.com  Mon Jul 20 08:30:04 2009
Return-Path: <denghui02@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA53C28C190 for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRrCLNp+PA5A for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:30:04 -0700 (PDT)
Received: from mail-px0-f184.google.com (mail-px0-f184.google.com [209.85.216.184]) by core3.amsl.com (Postfix) with ESMTP id 7761C28C19A for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:29:58 -0700 (PDT)
Received: by pxi14 with SMTP id 14so195818pxi.29 for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:29:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=m2LUdKBler9AEvqgCfcB5O+1sGvDudmM4lG6gTg+FzQ=; b=bRD+hZ9O8E8znBHmZvhnd6IeSOGSOX4t5JSWPtvvumXg6vrke+xajqHN0T9t0Y2m/7 l//xGzaIYIi5DV43aX1S/9ljNDRJJC91FT5uyllzMONfuaCdjtad5MVZEGQdEfyeKC+N ILHnU1bq7UY0atJ422F1IPbvAPFrBCBcwMGKk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=I3D+ww9VPbhTYTuiI7DaC5JMadoJB8VZSVwDj199bvCwjtpsJX8NZHaweOFjgMapum H4P0Pia9b63rQslD4I2UmA8OkGyWhYy5hXk8IwqmpjTgkd9Qk6Zc2ZtYwaU0ww5+pV62 2YGACMDemaQiDzV2HaJd93+KyLQ1dU8ghMdpg=
MIME-Version: 1.0
Received: by 10.142.76.15 with SMTP id y15mr984412wfa.224.1248103796746; Mon,  20 Jul 2009 08:29:56 -0700 (PDT)
In-Reply-To: <187423.66828.qm@web111415.mail.gq1.yahoo.com>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <187423.66828.qm@web111415.mail.gq1.yahoo.com>
Date: Mon, 20 Jul 2009 23:29:56 +0800
Message-ID: <1d38a3350907200829h5fe1a52eoe626e120f797e8f4@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix and an IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2009 15:30:05 -0000

Haven't this draft got sufficient review from DHCWG since RFC 4477 is
already there?

-Hui

2009/7/16 Behcet Sarikaya <behcetsarikaya@yahoo.com>:
>
> Hi Dapeng,
> =A0 My answer would be yes.
> Please take a look at http://tools.ietf.org/html/draft-ietf-mip6-hiopt-17
> this draft which is in RFC Editor queue defines DHCPv6 options to carry I=
Pv4 address.
>
> Vice-versa is also possible, please look at http://tools.ietf.org/id/draf=
t-xia-mext-hioptv4-00.txt=A0where we defined DHCPv4 option to carry IPv6 ad=
dress.
>
> Regards,
>
> Behcet
>
>
>
> ----- Original Message ----
>> From: liu dapeng <maxpassion@gmail.com>
>> To: dhcwg@ietf.org
>> Sent: Wednesday, July 15, 2009 2:56:54 AM
>> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix a=
nd an IPv4 address simultaneously?
>>
>> Hi,guys,
>> =A0 I have a question about whether current DHCPv6 specification could
>> support assigning an IPv6 prefix and an IPv4 address simultaneously?
>>
>>
>> BR,
>> Dapeng Liu
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

From denghui02@gmail.com  Mon Jul 20 08:36:15 2009
Return-Path: <denghui02@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F7F33A68A1 for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmLHaglx4tCA for <dhcwg@core3.amsl.com>; Mon, 20 Jul 2009 08:36:14 -0700 (PDT)
Received: from mail-px0-f184.google.com (mail-px0-f184.google.com [209.85.216.184]) by core3.amsl.com (Postfix) with ESMTP id 9C7B13A6784 for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:36:14 -0700 (PDT)
Received: by pxi14 with SMTP id 14so198308pxi.29 for <dhcwg@ietf.org>; Mon, 20 Jul 2009 08:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Gyc18lcqFhwko7rVHckNkT7DELnFEurcyMH3yHXFJbI=; b=iHZ6ZMO0Uefk9GjTB27W3zHBIYhnNO82Kfmqf8clRDIF/gq07PS3ECqojI3tKqZ7XH ZLOY/O9f076vBo4hjkHBqjl6dWdhdL3XIa9hBrUrYGYUiSBmSUdfXLUrNJ0IZvyVE2uF 6pnohHFvnS3sB0Zzq4Frj0/vH0ud5yzEajako=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=H8zLqEvv1JXt0tVka2nsgyJO771GjC/ddBtNC9TwcHsuROYRJkvP+GStUkhpKig5l2 Tv6rRFZiV/w1PHzcEFASyj6yCMMLy2Prd45WXqc5+mMCLcTwPeF9XAhIHoDnzWiknccB VFkb3GoinLKPmG1aBb2CAs2ByOtZxbDno/nkM=
MIME-Version: 1.0
Received: by 10.142.147.15 with SMTP id u15mr975254wfd.322.1248104172848; Mon,  20 Jul 2009 08:36:12 -0700 (PDT)
In-Reply-To: <20090715164557.GA4526@isc.org>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <20090715164557.GA4526@isc.org>
Date: Mon, 20 Jul 2009 23:36:12 +0800
Message-ID: <1d38a3350907200836w21972e73r815e97879eeb8a@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "David W. Hankins" <David_Hankins@isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2009 15:36:15 -0000

2009/7/16 David W. Hankins <David_Hankins@isc.org>:
> On Wed, Jul 15, 2009 at 07:02:46AM -0400, Bernie Volz (volz) wrote:
>> Other than saving the 4 messages (2 if rapid commit is used) for a
>> separate DHCPv4 exchange, why do you see this as being valuable?
>
> For awhile I toyed with the idea because DHCPv6's unconfigured
> communications model is superior (and because of it, we don't have
> worries like non-implementation of udp fragmentation and so forth).
>
> It seems like a complication because this creates now two IPv4
> configuration sources and we're already in bad enough shape in
> this regard; two IPv6 sources of configuration (RA and DHCPv6), and
> two sources of IP-nonspecific configuration state (DHCPv4 and DHCPv6).
>
> The dependency graph is plenty bad enough.
>
> But the final model after an IPv4-capable-DHCPv6 is well deployed
> would be for one source of configuration (DHCPv6 only), a net
> simplification, and a schedule to retire DHCPv4 without relying on
> retiring IPv4 first (or ever).
=3D=3D> I agree, this is what we think and then proposed in behave working =
group.

-Hui

>
> --
> David W. Hankins =A0 =A0 =A0 =A0"If you don't do it right the first time,
> Software Engineer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0you'll just have=
 to do it again."
> Internet Systems Consortium, Inc. =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Jack T. =
Hankins
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>

From mayer@ntp.org  Mon Jul 20 10:53:11 2009
Return-Path: <mayer@ntp.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 275343A6B03; Mon, 20 Jul 2009 10:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s04VoIB0JG+z; Mon, 20 Jul 2009 10:53:05 -0700 (PDT)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by core3.amsl.com (Postfix) with ESMTP id F3AD03A69C5; Mon, 20 Jul 2009 10:53:04 -0700 (PDT)
Received: from firewall.antoniuk.lan (mail.antoniuk.md [65.86.158.146]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ntp.org (Postfix) with ESMTP id B4133398CD; Mon, 20 Jul 2009 17:52:50 +0000 (UTC) (envelope-from mayer@ntp.org)
Received: from cust-63-209-234-94.bos-dynamic.gis.net ([63.209.234.94] helo=[10.10.10.101]) by firewall.antoniuk.lan with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <mayer@ntp.org>) id 1MSx2V-0005Qg-0w; Mon, 20 Jul 2009 13:52:39 -0400
Message-ID: <4A64AEDB.4020408@ntp.org>
Date: Mon, 20 Jul 2009 13:52:27 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <AE47D7F85F757B46BDDB9D9366F991C0011C54C2@naeamillez05v.nadsusea.nads.navy.mil> <4A4D3484.8030809@innovationslab.net>
In-Reply-To: <4A4D3484.8030809@innovationslab.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.org
Cc: "Odonoghue, Karen F CIV NSWCDD, W23" <karen.odonoghue@navy.mil>, tictoc@ietf.org, DHCP Working Group <dhcwg@ietf.org>, NTP Working Group <ntpwg@lists.ntp.isc.org>
Subject: Re: [dhcwg] [ntpwg] NTP WG Last Call: draft-ietf-ntp-dhcpv6-ntp-opt-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jul 2009 17:53:11 -0000

Sorry for the delay. I have two issues which I thought had been agreed upon:

Major:
1) That this draft should obsolete RFC 4075 and the "SNTP" option should
be withdrawn and that this will replace it. The rationale for this is
that this draft contains everything that the "SNTP" option contains and
then some so there is no need for both options. There are no
distinguishing characteristics that a client would be required to use an
SNTP server instead of an NTP server and vice versa. From the client's
point of view they are interchangeable.

Minor:
2) The term "NTP Server" can be used interchangably with "SNTP Server"
and NTP Client with SNTP Client.  For example, in Section 3 the first
paragraph should be replaced with:

This option serves as a container for all the information related to one
NTP server or SNTP server.  This option can appear multiple times in a
DHCPv6 message. Each instance of this option is to be considered by the
NTP client or SNTP client as a server to include in its configuration.

These are the only two issues that I have with the document as it now
stands. If these can be addressed then we should be able to move the
document forward.

Danny

Brian Haberman wrote:
> All,
>       This LC ended over a month ago with no comments.  We cannot 
> advance a document to the IESG if there is no support for it (silence is 
> not consensus).  If you support (or object) to the advancement of this 
> document we need to hear it, preferably on the mailing list but 
> privately to the chairs is acceptable.
> 
> Regards,
> Brian
> 
> Odonoghue, Karen F CIV NSWCDD, W23 wrote:
>> All,
>>
>> This message starts a 2-week NTP Working Group Last Call on advancing:
>>
>>        Title     : Network Time Protocol (NTP) Server Option for DHCPv6
>>        Author(s) : R. Gayraud and B. Lourdelet
>>        Filename  : draft-ietf-ntp-dhcpv6-ntp-opt-03.txt
>>        Pages     : 10
>>        Date      : March 6, 2009
>> 	
>> as a Proposed Standard document.  Substantive comments and statements of support or opposition for advancing this document should be directed to the mailing list.  Editorial suggestions can be sent to the document editor.  This last call will end on May 20.
>>
>> Regards,
>> Brian & Karen
>> NTP co-chairs

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From Ted.Lemon@nominum.com  Tue Jul 21 05:34:16 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A49B3A6862 for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 05:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.3
X-Spam-Level: 
X-Spam-Status: No, score=-5.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8ReXVRW4Ssn for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 05:34:10 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id B39A23A67A6 for <dhcwg@ietf.org>; Tue, 21 Jul 2009 05:34:08 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKSmW1iBSu/i106gJmFrYJVBGcRK3jnCCe@postini.com; Tue, 21 Jul 2009 05:34:09 PDT
Received: from webmail.nominum.com (exchange-10.nominum.com [64.89.228.57]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "exchange-10.win.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6C6BD1B817E; Tue, 21 Jul 2009 04:59:13 -0700 (PDT)
Received: from exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) by exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) with mapi; Tue, 21 Jul 2009 04:59:02 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hui Deng <denghui02@gmail.com>, "David W. Hankins" <David_Hankins@isc.org>
Date: Tue, 21 Jul 2009 04:54:28 -0700
Thread-Topic: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
Thread-Index: AcoJT9SBwHvtae/+SD+DbG99FTwqJAAqitwN
Message-ID: <23CEFBAC26A6814695D4872E1CE3B1AC06C143E6@exchange-10.WIN.NOMINUM.COM>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <20090715164557.GA4526@isc.org>, <1d38a3350907200836w21972e73r815e97879eeb8a@mail.gmail.com>
In-Reply-To: <1d38a3350907200836w21972e73r815e97879eeb8a@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix	andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 12:34:16 -0000

> But the final model after an IPv4-capable-DHCPv6 is well deployed
> would be for one source of configuration (DHCPv6 only), a net
> simplification, and a schedule to retire DHCPv4 without relying on
> retiring IPv4 first (or ever).
=3D=3D> I agree, this is what we think and then proposed in behave working =
group.

On the other hand, once IPv6 is deployed, you won't need IPv4 at all anymor=
e, and so having IPv4 options in DHCPv6 would be inappropriate when looked =
at from that perspective.

More to the point, IPv4-capable devices already know how to get IPv4 addres=
ses, so defining a new mechanism for configuring them with IPv4 addresses i=
s likely to create confusion and interoperability problems.

So I persist in asking: why do you prefer to do this in DHCPv6?   If your o=
nly reason is that it makes the protocol look neater in the long run, I thi=
nk that reason is (a) not correct, and (b) not a good reason.

From maxpassion@gmail.com  Tue Jul 21 06:09:19 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 431403A68E9 for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.926
X-Spam-Level: 
X-Spam-Status: No, score=-0.926 tagged_above=-999 required=5 tests=[AWL=0.543,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exfaEQ+e77SS for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:09:18 -0700 (PDT)
Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id 844E63A69A1 for <dhcwg@ietf.org>; Tue, 21 Jul 2009 06:09:18 -0700 (PDT)
Received: by qyk41 with SMTP id 41so2440317qyk.29 for <dhcwg@ietf.org>; Tue, 21 Jul 2009 06:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JsEwKEgv/2ORLPtMtfWAu/eDhRwtwIzv3BIb0OAeLwk=; b=c7B/ghU/fezWNz6cQ+j8mJQSchfuITUYRnf2A4nBBqRM5whZX6SVLfyHizsrilqzAw QaxnF9x5cBVLbj9w5vzaedw4jvB/a76SpPr8tH5WCvVgT31Hoc86tf1Nohp9UzoIwcjB QbZsfeKx6zQuK8n0Oc/+x7tw1lep0mOOvBy3s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nbWsP7vbPgcgPymd84CklQFJVweHN5RkNoGZarTeoOdvLQVe7Zqk3JxG68flvx8JqM hbZL13ksDX0lIQN1t3Wv8bhrFoR7Y/Jqg6l7uh+B8bttev7Ua2c/KYEFuzoPMyfBnaDQ qcDByM54hjti3LYmPTaRangkBgbV8ABsj9Z14=
MIME-Version: 1.0
Received: by 10.220.95.149 with SMTP id d21mr6389155vcn.14.1248181686231; Tue,  21 Jul 2009 06:08:06 -0700 (PDT)
In-Reply-To: <2C46F3D8-BE25-49BB-A807-CBAD5C8A46BA@nominum.com>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <20090715112120.GG12615@login.ecs.soton.ac.uk> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk> <25e1aaa40907150913x495734f2i81a8a7b9da2f7279@mail.gmail.com> <2C46F3D8-BE25-49BB-A807-CBAD5C8A46BA@nominum.com>
Date: Tue, 21 Jul 2009 21:08:06 +0800
Message-ID: <25e1aaa40907210608m7dd1d5f5i969c08f9a662bc19@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dhcwg <dhcwg@ietf.org>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 13:09:19 -0000

2009/7/16, Ted Lemon <Ted.Lemon@nominum.com>:
> On Jul 15, 2009, at 11:13 AM, liu dapeng wrote:
>> We are exploring an host based IPv4/IPv6 transition mechanism named
>> PNAT and  we are considering to use DHCPv6 to assign an IPv6 prefix
>> and an IPv4 address for the host at the same time to facilitate PNAT.
>
> My question about this is, why not just use DHCPv4 to get the IPv4
> address?

The scenario in PNAT is that the host only has IPv6 connectivity, so
can not use DHCPv4.

The IPv4 address and IPv6 prefix is used for synthesizeing an IPv6
address used for the IPv6 host as its IPv6 address.

From maxpassion@gmail.com  Tue Jul 21 06:47:16 2009
Return-Path: <maxpassion@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A42228C2B9 for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:47:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.762
X-Spam-Level: 
X-Spam-Status: No, score=-0.762 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, J_CHICKENPOX_24=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nvi0-nRU3jP for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:47:15 -0700 (PDT)
Received: from mail-qy0-f203.google.com (mail-qy0-f203.google.com [209.85.221.203]) by core3.amsl.com (Postfix) with ESMTP id 7D16D3A6978 for <dhcwg@ietf.org>; Tue, 21 Jul 2009 06:47:15 -0700 (PDT)
Received: by qyk41 with SMTP id 41so2480294qyk.29 for <dhcwg@ietf.org>; Tue, 21 Jul 2009 06:46:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=O56aYbOYFW8JTOlSuigU+QD5Sva78lvVwgYEy+bazUI=; b=Bg8csQZXerldNkQuvlWp6CUuqdeR+L9vUnifap4r0i8IDM8ovURqZ1kStzs6nDmB1b ca7IXh5kKbPEYokIGe943zZRTCt9/23vlh6hNx7x3usiPMHbz5nMQJ0HuT146QLn5UIB AKbJp1uiASvZD5In7oCkpHtiX6+81JOKLZNbs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fuf48qUnYGL0XerpCRjbEaiOji8f3jRxqVQN86o3+Bo7tH4mwM+y+ex2Lu9WoAHWGz soE2Z4xH54zCUoMLCZ/61fdVbSUlLJ+C3xpxkgCe0m7ZkL4rAHirogDk9R47WxaMh9bR m1THIGeKvRh4M68CZVUUm8ZnWeHEXUIdMiZRw=
MIME-Version: 1.0
Received: by 10.220.45.80 with SMTP id d16mr7385154vcf.93.1248184001774; Tue,  21 Jul 2009 06:46:41 -0700 (PDT)
In-Reply-To: <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com>
Date: Tue, 21 Jul 2009 21:46:41 +0800
Message-ID: <25e1aaa40907210646v4668121h78c406c9f043b425@mail.gmail.com>
From: liu dapeng <maxpassion@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 13:47:16 -0000

2009/7/15, Bernie Volz (volz) <volz@cisco.com>:
> Did you really mean IPv4 address?

Yes.  The IPv4 address is used for synthesizeing an IPv6 address
together with the IPv6 prefix in PNAT scenario.

> DHCPv6 only handles IPv6 prefixes and addresses, not IPv4. DHCPv4 is
> used for IPv4.
>
> This was discussed when DHCPv6 was being developed, but there was little
> practical value to complicating DHCPv6 with supporting IPv4 as well --
> after all DHCPv4 was already widely deployed and in use.

DHCPv4 can only be accessed when the host has IPv4 connectivity. In
IPv4/IPv6 transition scenario, the Host may be in an IPv6 only network
as described in the PNAT draft.

In that case, we cannot use DHCPv4 to assign IP address for the host.
Instead, we propose to assign an IPv4 address and an IPv6 prefix to
the host using DHCPv6,  the host then uses the IPv4 address together
with the IPv6 prefix to synthesize an IPv6 address as its source
address.

> Other than saving the 4 messages (2 if rapid commit is used) for a
> separate DHCPv4 exchange, why do you see this as being valuable?
>
> - Bernie
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of liu dapeng
> Sent: Wednesday, July 15, 2009 3:57 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix
> andan IPv4 address simultaneously?
>
> Hi,guys,
>   I have a question about whether current DHCPv6 specification could
> support assigning an IPv6 prefix and an IPv4 address simultaneously?
>
>
> BR,
> Dapeng Liu
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

From tjc@ecs.soton.ac.uk  Tue Jul 21 06:56:44 2009
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 402C028C2B8 for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level: 
X-Spam-Status: No, score=-1.846 tagged_above=-999 required=5 tests=[AWL=-0.377, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UG5uN2i2U-w for <dhcwg@core3.amsl.com>; Tue, 21 Jul 2009 06:56:43 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by core3.amsl.com (Postfix) with ESMTP id B972A28C2AF for <dhcwg@ietf.org>; Tue, 21 Jul 2009 06:56:42 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n6LDpEuo001537;  Tue, 21 Jul 2009 14:51:14 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk n6LDpEuo001537
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1248184274; bh=/WnaBrPl14ILhC2o8Wyvo5t8Fus=; h=Date:From:To:Cc:Subject:References:Mime-Version:In-Reply-To; b=2sGbH3J/vDxc2/xDTMOMoogey/RkKdBhG2s5wGbw50N/hC0vKkGKqL66lOJhlat/c xrC5bkPdz18EmtR6loLPHQq6aLgbFCED2WIYCMoFw53UNuFBlBoeTkf3mVtOtGIFdW M7Ark1FSBscyhAFxioUoiMm6hDoHC44Zkneag/yQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id l6KEpE0448551163rz ret-id none; Tue, 21 Jul 2009 14:51:14 +0100
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n6LDp0s1030286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jul 2009 14:51:00 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id n6LDp0Yn031386;  Tue, 21 Jul 2009 14:51:00 +0100
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id n6LDp0gL031385; Tue, 21 Jul 2009 14:51:00 +0100
Date: Tue, 21 Jul 2009 14:51:00 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Hui Deng <denghui02@gmail.com>
Message-ID: <EMEW3|c0c58ee4c0f55b68b0ea8ccce65e965cl6KEpE03tjc|ecs.soton.ac.uk|5100.GI24319@login.ecs.soton.ac.uk>
Mail-Followup-To: Hui Deng <denghui02@gmail.com>, "David W. Hankins" <David_Hankins@isc.org>, DHC WG <dhcwg@ietf.org>
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <20090715164557.GA4526@isc.org> <1d38a3350907200836w21972e73r815e97879eeb8a@mail.gmail.com> <20090721135100.GI24319@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1d38a3350907200836w21972e73r815e97879eeb8a@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: client=relay,ipv6; mail=; rcpt=
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: n6LDpEuo001537
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2009 13:56:44 -0000

On Mon, Jul 20, 2009 at 11:36:12PM +0800, Hui Deng wrote:
> 2009/7/16 David W. Hankins <David_Hankins@isc.org>:
> > On Wed, Jul 15, 2009 at 07:02:46AM -0400, Bernie Volz (volz) wrote:
> >> Other than saving the 4 messages (2 if rapid commit is used) for a
> >> separate DHCPv4 exchange, why do you see this as being valuable?
> >
> > For awhile I toyed with the idea because DHCPv6's unconfigured
> > communications model is superior (and because of it, we don't have
> > worries like non-implementation of udp fragmentation and so forth).
> >
> > It seems like a complication because this creates now two IPv4
> > configuration sources and we're already in bad enough shape in
> > this regard; two IPv6 sources of configuration (RA and DHCPv6), and
> > two sources of IP-nonspecific configuration state (DHCPv4 and DHCPv6).
> >
> > The dependency graph is plenty bad enough.
> >
> > But the final model after an IPv4-capable-DHCPv6 is well deployed
> > would be for one source of configuration (DHCPv6 only), a net
> > simplification, and a schedule to retire DHCPv4 without relying on
> > retiring IPv4 first (or ever).
> ==> I agree, this is what we think and then proposed in behave working group.

RFC4477 stated reasonably clearly that it was 'current consensus' that was
made in the absence of widespread operational experience.  

The context of RFC 4477 was considering DHCP behaviour/best practice in
a dual-stack network, i.e. IPv4 and IPv6 transport available to the host.
There is some discussion in section 4.2 on obtaining IPv4 addresses
via DHPCv6, and a list of concerns at the time about this approach.  These
may not be so important if there is a specific use case where the potantial
issues are avoided, e.g. no danger of a host getting IPv4 addresses via a 
DHCPv6 option *and* via regular DHCPv4.

The idea of carrying IPv4 address options via DHCPv6 is not new - it was
suggested many years ago as a method for a DSTM host to get an IPv4 address 
to use for its IPv4-in-IPv6 tunnel to an edge router.   I'm sure the draft(s)
associated with that idea are online somewhere - there were implementation(s).

Tim

From mellon@fugue.com  Wed Jul 22 05:16:23 2009
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D40128C3D2 for <dhcwg@core3.amsl.com>; Wed, 22 Jul 2009 05:16:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMxCKZq1LotZ for <dhcwg@core3.amsl.com>; Wed, 22 Jul 2009 05:16:22 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id 7A8C828C3CB for <dhcwg@ietf.org>; Wed, 22 Jul 2009 05:16:22 -0700 (PDT)
Received: from [192.168.0.5] (5add62f3.bb.sky.com [90.221.98.243]) by toccata.fugue.com (Postfix) with ESMTPSA id 082EC34E4195; Wed, 22 Jul 2009 05:19:24 -0700 (MST)
References: <25e1aaa40907150056i3257d032t20e9dfc689fca519@mail.gmail.com> <20090715112120.GG12615@login.ecs.soton.ac.uk> <8E296595B6471A4689555D5D725EBB210DA68F32@xmb-rtp-20a.amer.cisco.com> <EMEW3|85aadd2d1e23c1547f9b35a06708ad29l6ECLY03tjc|ecs.soton.ac.uk|2120.GG12615@login.ecs.soton.ac.uk> <25e1aaa40907150913x495734f2i81a8a7b9da2f7279@mail.gmail.com> <2C46F3D8-BE25-49BB-A807-CBAD5C8A46BA@nominum.com> <25e1aaa40907210608m7dd1d5f5i969c08f9a662bc19@mail.gmail.com>
Message-Id: <74040F19-F4BA-41C8-B04A-325BA0636312@fugue.com>
From: Ted Lemon <mellon@fugue.com>
To: liu dapeng <maxpassion@gmail.com>
In-Reply-To: <25e1aaa40907210608m7dd1d5f5i969c08f9a662bc19@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7A341)
Mime-Version: 1.0 (iPhone Mail 7A341)
Date: Wed, 22 Jul 2009 13:15:18 +0100
Cc: dhcwg <dhcwg@ietf.org>, "tjc@ecs.soton.ac.uk" <tjc@ecs.soton.ac.uk>, Ted Lemon <Ted.Lemon@nominum.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Whether DHCPv6 could support assigning an IPv6 prefix andan IPv4 address simultaneously?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2009 12:16:23 -0000

Okay, this makes sense now--thanks for clarifying!

Sent from my iPhone

On Jul 21, 2009, at 2:08 PM, liu dapeng <maxpassion@gmail.com> wrote:

> 2009/7/16, Ted Lemon <Ted.Lemon@nominum.com>:
>> On Jul 15, 2009, at 11:13 AM, liu dapeng wrote:
>>> We are exploring an host based IPv4/IPv6 transition mechanism named
>>> PNAT and  we are considering to use DHCPv6 to assign an IPv6 prefix
>>> and an IPv4 address for the host at the same time to facilitate  
>>> PNAT.
>>
>> My question about this is, why not just use DHCPv4 to get the IPv4
>> address?
>
> The scenario in PNAT is that the host only has IPv6 connectivity, so
> can not use DHCPv4.
>
> The IPv4 address and IPv6 prefix is used for synthesizeing an IPv6
> address used for the IPv6 host as its IPv6 address.

From yoshihiro.ohba@toshiba.co.jp  Sun Jul 26 15:13:29 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E2E93A684D for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 15:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.489
X-Spam-Level: 
X-Spam-Status: No, score=-1.489 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3XPmdW3KNv0d for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 15:13:28 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 8804B3A6838 for <dhcwg@ietf.org>; Sun, 26 Jul 2009 15:13:28 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6QMDSdt022365 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 07:13:28 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6QMDSi6019632 for dhcwg@ietf.org; Mon, 27 Jul 2009 07:13:28 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id HAA19631; Mon, 27 Jul 2009 07:13:28 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6QMDRpW017418 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 07:13:27 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6QMDRVR029066; Mon, 27 Jul 2009 07:13:27 +0900 (JST)
Received: from [133.199.16.154] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNE00BMSTQFHW60@mail.po.toshiba.co.jp> for dhcwg@ietf.org; Mon, 27 Jul 2009 07:13:27 +0900 (JST)
Date: Sun, 26 Jul 2009 18:13:21 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
To: dhcwg@ietf.org
Message-id: <4A6CD501.7030704@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Subject: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jul 2009 22:13:29 -0000

I have read both documents. Thanks for the authors for both documents 
providing techinical details.

However, I still have an issue with carrying EAP over DHCP. The issue is 
basically a conflict between statefullness of EAP and statelessness of 
DHCP relay agent.

As far as I understand, DHCP relay agent does not maintain a state. On 
the other hand, EAP requires peer and authenticator to maintain a state 
(see RFC 4137). When DHCP relay agent acts EAP authenticator, then the 
relay agent will be no longer a stateless DHCP entity. I think this is 
not discussed in dhcp-eap-analysis draft. Is this an acceptable design 
change for DHCP?  Or please correct me if I am wrong.

Regards,
Yoshihiro Ohba

From ric@cisco.com  Sun Jul 26 22:56:18 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BB2B3A682E for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 22:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rr28P0ZtkwvK for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 22:56:17 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id DC7AB3A69BA for <dhcwg@ietf.org>; Sun, 26 Jul 2009 22:56:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEANfdbEoKS+eh/2dsb2JhbAC4M4gojVMFhA0
X-IronPort-AV: E=Sophos;i="4.43,274,1246838400"; d="scan'208";a="58551588"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 27 Jul 2009 05:56:15 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6R5uEoU016972;  Mon, 27 Jul 2009 13:56:14 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R5uDEG020040; Mon, 27 Jul 2009 05:56:14 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 13:55:30 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 13:55:29 +0800
Message-Id: <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6CD501.7030704@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 15:55:27 +1000
References: <4A6CD501.7030704@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 05:55:29.0565 (UTC) FILETIME=[D892D4D0:01CA0E7E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1119; t=1248674175; x=1249538175; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=SMqWGTXJ3PlaYxnjXiMBfYb1bmKwtojCaw+QGIYMQDY=; b=cBwBIMu3kN7aZ1MP6BZDPz1ayl6ZK5TQ3kjCdWA+qgO3RKDEyISKPHj0EL Y5H2/3LyV8qNiDQSPKMpFm5cEBsQryWeyNAh5Gp+GRWCpKXgmYBCWvZ+0EHP qqxujLTFotBs+gLdncdSzPuiYHC8Zg8Qb7U1O3H7ZAACMWYqU1Paw=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 05:56:18 -0000

Relay's in the broadband architecture have to be stateful to enforce  
DHCP address assignment, so it is not a change to the existing  
architecture.

- Ric

On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:

> I have read both documents. Thanks for the authors for both  
> documents providing techinical details.
>
> However, I still have an issue with carrying EAP over DHCP. The  
> issue is basically a conflict between statefullness of EAP and  
> statelessness of DHCP relay agent.
>
> As far as I understand, DHCP relay agent does not maintain a state.  
> On the other hand, EAP requires peer and authenticator to maintain a  
> state (see RFC 4137). When DHCP relay agent acts EAP authenticator,  
> then the relay agent will be no longer a stateless DHCP entity. I  
> think this is not discussed in dhcp-eap-analysis draft. Is this an  
> acceptable design change for DHCP?  Or please correct me if I am  
> wrong.
>
> Regards,
> Yoshihiro Ohba
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From yoshihiro.ohba@toshiba.co.jp  Sun Jul 26 23:55:29 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A4D128C0EC for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 23:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzajph6v2OUE for <dhcwg@core3.amsl.com>; Sun, 26 Jul 2009 23:55:28 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 93DDC28C0DB for <dhcwg@ietf.org>; Sun, 26 Jul 2009 23:55:28 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6R6tQQn013370; Mon, 27 Jul 2009 15:55:26 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6R6tQaT021979; Mon, 27 Jul 2009 15:55:26 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id RAA21978; Mon, 27 Jul 2009 15:55:26 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6R6tPLd022409; Mon, 27 Jul 2009 15:55:25 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6R6tLSF005625; Mon, 27 Jul 2009 15:55:21 +0900 (JST)
Received: from [133.196.16.131] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNF00HATHW9LN60@mail.po.toshiba.co.jp>; Mon, 27 Jul 2009 15:55:21 +0900 (JST)
Date: Mon, 27 Jul 2009 02:55:15 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6D4F53.2060608@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 06:55:29 -0000

Richard Pruss wrote:
> Relay's in the broadband architecture have to be stateful to enforce 
> DHCP address assignment, so it is not a change to the existing 
> architecture.
As far as I understand, enforcing DHCP address assignment is needed 
*after* DHCP exchanges are done, and therefore the state is maintained 
outside the context of DHCP, which I don't care.  My comment was if DHCP 
relay needs to be stateful in the middle of DHCP exchanges to carry EAP.
 From DHCP point of view, it seems to be a major design change to DHCP.

Regards,
Yoshihiro Ohba

>
> - Ric
>
> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>
>> I have read both documents. Thanks for the authors for both documents 
>> providing techinical details.
>>
>> However, I still have an issue with carrying EAP over DHCP. The issue 
>> is basically a conflict between statefullness of EAP and 
>> statelessness of DHCP relay agent.
>>
>> As far as I understand, DHCP relay agent does not maintain a state. 
>> On the other hand, EAP requires peer and authenticator to maintain a 
>> state (see RFC 4137). When DHCP relay agent acts EAP authenticator, 
>> then the relay agent will be no longer a stateless DHCP entity. I 
>> think this is not discussed in dhcp-eap-analysis draft. Is this an 
>> acceptable design change for DHCP?  Or please correct me if I am wrong.
>>
>> Regards,
>> Yoshihiro Ohba
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>


From ric@cisco.com  Mon Jul 27 00:04:27 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E50628C11D for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVTlTUZgtUaT for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:04:26 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id E25CE28C10C for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:04:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALvubEoKS+eh/2dsb2JhbAC4WogojVMFhA0
X-IronPort-AV: E=Sophos;i="4.43,274,1246838400"; d="scan'208";a="55792734"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-2.cisco.com with ESMTP; 27 Jul 2009 07:04:24 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6R74Oqa001371;  Mon, 27 Jul 2009 15:04:24 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R74MCE009979; Mon, 27 Jul 2009 07:04:24 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:04:02 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:04:02 +0800
Message-Id: <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6D4F53.2060608@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 17:04:00 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 07:04:02.0221 (UTC) FILETIME=[6BE855D0:01CA0E88]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1830; t=1248678264; x=1249542264; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=xwCbXyXl0wUhFAURBU4SVBfsC/LStTlN07b5Pauw+eI=; b=c0qzrE2SCU90vTJj00J14aqdZbAgidScNV/YykJh2OyxfVd1WHc/Z7Cglo K+Nx3Kq2mHhVmNDOvSREgAktgsE69D17y3ZprRH2jljV9azMEDlAOfQzJ3U2 SQK+lmUR2yE2qOVhYJg3kKPkNK4vWgTXrGLKDUvB+l6uYQ6ytGJh4=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:04:27 -0000

On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>> Relay's in the broadband architecture have to be stateful to  
>> enforce DHCP address assignment, so it is not a change to the  
>> existing architecture.
> As far as I understand, enforcing DHCP address assignment is needed  
> *after* DHCP exchanges are done, and therefore the state is  
> maintained outside the context of DHCP, which I don't care.  My  
> comment was if DHCP relay needs to be stateful in the middle of DHCP  
> exchanges to carry EAP.
> From DHCP point of view, it seems to be a major design change to DHCP.

Do you actually have an implementation of broadband DHCP relay  
because  what you are talking makes very little sense?

- Ric


>
> Regards,
> Yoshihiro Ohba
>
>>
>> - Ric
>>
>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>
>>> I have read both documents. Thanks for the authors for both  
>>> documents providing techinical details.
>>>
>>> However, I still have an issue with carrying EAP over DHCP. The  
>>> issue is basically a conflict between statefullness of EAP and  
>>> statelessness of DHCP relay agent.
>>>
>>> As far as I understand, DHCP relay agent does not maintain a  
>>> state. On the other hand, EAP requires peer and authenticator to  
>>> maintain a state (see RFC 4137). When DHCP relay agent acts EAP  
>>> authenticator, then the relay agent will be no longer a stateless  
>>> DHCP entity. I think this is not discussed in dhcp-eap-analysis  
>>> draft. Is this an acceptable design change for DHCP?  Or please  
>>> correct me if I am wrong.
>>>
>>> Regards,
>>> Yoshihiro Ohba
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>>
>>
>


From rdroms@cisco.com  Mon Jul 27 00:26:08 2009
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB4B328C0F7 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.936
X-Spam-Level: 
X-Spam-Status: No, score=-5.936 tagged_above=-999 required=5 tests=[AWL=0.663,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtQYw0u9N-Yx for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:26:07 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id D2C3C28C13D for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:26:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="219403361"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 27 Jul 2009 07:26:09 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n6R7Q9jf011994;  Mon, 27 Jul 2009 00:26:09 -0700
Received: from sjc-vpnasa-546.cisco.com (sjc-vpnasa-546.cisco.com [10.21.106.37]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n6R7Q7t3018311; Mon, 27 Jul 2009 07:26:08 GMT
Message-Id: <8BABA261-DE48-4684-85C8-419591061672@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Richard Pruss <ric@cisco.com>
In-Reply-To: <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 09:26:05 +0200
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2886; t=1248679569; x=1249543569; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=OTD0dzVw58zf2Caz9Hd6YCRRfVNlBnkkaFRvBWSlSEI=; b=SlmqgO36fR/Q7/Iyw429zWtGaDMe8jCAFJzpMM0kiSgNqv5PVZ/WpwfqeJ sBVMJbEc60CwxqBXJvZWXZyBWbqFZ5rtNRsv3sV9Lx5lLZDoJY28GrVELMPW AZWWnxlKW+;
Authentication-Results: sj-dkim-4; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:26:08 -0000

Ric - the question seems sensible to me.

I would consider enforcing the address assignment as a separate  
function of the box that happens to house the DHCP relay agent  
function.  That is, the relay agent extracts the assigned address from  
the DHCPACK and hands it to the address enforcement function.   
Therefore, the relay agent function is not keeping any state.  The  
address enforcement function could just as easily get that address  
assignment information from some other source like CLI or SNMP.

The original purpose of the relay agent option was to hold state for  
the relay agent.  We've tried to maintain that stateless operation  
(but I'm not sure we've strictly enforced the rule) with the  
definition of subsequent relay agent options.

- Ralph

On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:

>
> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>
>> Richard Pruss wrote:
>>> Relay's in the broadband architecture have to be stateful to  
>>> enforce DHCP address assignment, so it is not a change to the  
>>> existing architecture.
>> As far as I understand, enforcing DHCP address assignment is needed  
>> *after* DHCP exchanges are done, and therefore the state is  
>> maintained outside the context of DHCP, which I don't care.  My  
>> comment was if DHCP relay needs to be stateful in the middle of  
>> DHCP exchanges to carry EAP.
>> From DHCP point of view, it seems to be a major design change to  
>> DHCP.
>
> Do you actually have an implementation of broadband DHCP relay  
> because  what you are talking makes very little sense?
>
> - Ric
>
>
>>
>> Regards,
>> Yoshihiro Ohba
>>
>>>
>>> - Ric
>>>
>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>
>>>> I have read both documents. Thanks for the authors for both  
>>>> documents providing techinical details.
>>>>
>>>> However, I still have an issue with carrying EAP over DHCP. The  
>>>> issue is basically a conflict between statefullness of EAP and  
>>>> statelessness of DHCP relay agent.
>>>>
>>>> As far as I understand, DHCP relay agent does not maintain a  
>>>> state. On the other hand, EAP requires peer and authenticator to  
>>>> maintain a state (see RFC 4137). When DHCP relay agent acts EAP  
>>>> authenticator, then the relay agent will be no longer a stateless  
>>>> DHCP entity. I think this is not discussed in dhcp-eap-analysis  
>>>> draft. Is this an acceptable design change for DHCP?  Or please  
>>>> correct me if I am wrong.
>>>>
>>>> Regards,
>>>> Yoshihiro Ohba
>>>> _______________________________________________
>>>> dhcwg mailing list
>>>> dhcwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>
>>>
>>>
>>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Mon Jul 27 00:27:15 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8172628C11D for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.147
X-Spam-Level: 
X-Spam-Status: No, score=-6.147 tagged_above=-999 required=5 tests=[AWL=0.452,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUdLeH38SsJc for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:27:14 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id 6E55F28C0F7 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:27:06 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKSm1Wyoq6fZ0VMzsge0qFPYG87OHn1o1k@postini.com; Mon, 27 Jul 2009 00:27:16 PDT
Received: from webmail.nominum.com (exchange-10.nominum.com [64.89.228.57]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "exchange-10.win.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 94CA51B8329; Mon, 27 Jul 2009 00:27:17 -0700 (PDT)
Received: from exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) by exchange-10.WIN.NOMINUM.COM ([64.89.228.57]) with mapi; Mon, 27 Jul 2009 00:27:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Richard Pruss <ric@cisco.com>, Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
Date: Mon, 27 Jul 2009 00:27:05 -0700
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoOfvqdkilijfxVSo6f4S/D35QSuAACvPrR
Message-ID: <23CEFBAC26A6814695D4872E1CE3B1AC06C143FC@exchange-10.WIN.NOMINUM.COM>
References: <4A6CD501.7030704@toshiba.co.jp>, <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>
In-Reply-To: <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:27:15 -0000

On Sunday, July 26, 2009 10:55 PM, =3DRichard Pruss wrote"=3D=3D=3D=3D
> Relays in the broadband architecture have to be stateful to enforce
> DHCP address assignment, so it is not a change to the existing
> architecture.

Ric, unless I am horribly out of touch with the state of the art (always a =
possibilty), this statement is not in fact true.   It seems that either you=
 are using "relay agent" as a shorthand for something that's more than a re=
lay agent, or else you failed to sufficiently constrain the set of situatio=
ns in which your statement applies.   It's true that *caching* state is com=
mon in relays in a broadband environment, but that doesn't make those relay=
s "stateful" in the usual sense that we mean.=

From ric@cisco.com  Mon Jul 27 00:39:32 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B2053A69FA for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hm1HEEJUVz1c for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:39:31 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 887263A6886 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:39:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAPf2bEoKS+eh/2dsb2JhbAC4YYgojVgFhA0
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="55794404"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-2.cisco.com with ESMTP; 27 Jul 2009 07:39:25 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6R7dOCQ008157;  Mon, 27 Jul 2009 15:39:24 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R7dOfI019416; Mon, 27 Jul 2009 07:39:24 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:39:24 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:39:23 +0800
Message-Id: <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <8BABA261-DE48-4684-85C8-419591061672@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 17:39:21 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 07:39:23.0422 (UTC) FILETIME=[5C3DEBE0:01CA0E8D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3423; t=1248680365; x=1249544365; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=cldGJ4e5tWG7S1w/UuWwyJZi1zevLWwj3ECxdZ/CzsA=; b=d2nFq1egA9u+TqR4Tr846Us0ShpfRmlKaHiRnyAhgtbz3ELrHh/QZ0Cu8O HIy/DrNFKCmJXT2ewGg54UrNMUwGiXZ6YEfkzON4HHhRab55/xzkJNTFgnGa Upx6jZ3mtKf22MXN2L9HJUIGapLNw5cjCde/96uy0oc6Wpvqm2NGg=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:39:32 -0000

Well Ralph,  as you say something else is holding the state and the  
relay agent is simply handing the EAP messages to the AAA  service in  
the relay function... so no the question still makes no sense to me.

The thing that makes no sense is the assertion that the relay agent  
suddenly needs to hold state, beyond what it already does to handle ip  
unnumbered interfaces,
Ric

On 27/07/2009, at 5:26 PM, Ralph Droms wrote:

> Ric - the question seems sensible to me.
>
> I would consider enforcing the address assignment as a separate  
> function of the box that happens to house the DHCP relay agent  
> function.  That is, the relay agent extracts the assigned address  
> from the DHCPACK and hands it to the address enforcement function.   
> Therefore, the relay agent function is not keeping any state.  The  
> address enforcement function could just as easily get that address  
> assignment information from some other source like CLI or SNMP.
>
> The original purpose of the relay agent option was to hold state for  
> the relay agent.  We've tried to maintain that stateless operation  
> (but I'm not sure we've strictly enforced the rule) with the  
> definition of subsequent relay agent options.
>
> - Ralph
>
> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>
>>
>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>
>>> Richard Pruss wrote:
>>>> Relay's in the broadband architecture have to be stateful to  
>>>> enforce DHCP address assignment, so it is not a change to the  
>>>> existing architecture.
>>> As far as I understand, enforcing DHCP address assignment is  
>>> needed *after* DHCP exchanges are done, and therefore the state is  
>>> maintained outside the context of DHCP, which I don't care.  My  
>>> comment was if DHCP relay needs to be stateful in the middle of  
>>> DHCP exchanges to carry EAP.
>>> From DHCP point of view, it seems to be a major design change to  
>>> DHCP.
>>
>> Do you actually have an implementation of broadband DHCP relay  
>> because  what you are talking makes very little sense?
>>
>> - Ric
>>
>>
>>>
>>> Regards,
>>> Yoshihiro Ohba
>>>
>>>>
>>>> - Ric
>>>>
>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>
>>>>> I have read both documents. Thanks for the authors for both  
>>>>> documents providing techinical details.
>>>>>
>>>>> However, I still have an issue with carrying EAP over DHCP. The  
>>>>> issue is basically a conflict between statefullness of EAP and  
>>>>> statelessness of DHCP relay agent.
>>>>>
>>>>> As far as I understand, DHCP relay agent does not maintain a  
>>>>> state. On the other hand, EAP requires peer and authenticator to  
>>>>> maintain a state (see RFC 4137). When DHCP relay agent acts EAP  
>>>>> authenticator, then the relay agent will be no longer a  
>>>>> stateless DHCP entity. I think this is not discussed in dhcp-eap- 
>>>>> analysis draft. Is this an acceptable design change for DHCP?   
>>>>> Or please correct me if I am wrong.
>>>>>
>>>>> Regards,
>>>>> Yoshihiro Ohba
>>>>> _______________________________________________
>>>>> dhcwg mailing list
>>>>> dhcwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>


From ric@cisco.com  Mon Jul 27 00:40:21 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFC913A6BF8 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level: 
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=1.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rgiuZAh9N90 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:40:20 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 44C573A6886 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:40:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAHP2bEoKS+ej/2dsb2JhbAC4Z4gojVYFhA0
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="58557458"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-1.cisco.com with ESMTP; 27 Jul 2009 07:40:19 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6R7eIFn006557;  Mon, 27 Jul 2009 15:40:18 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R7eI2i019681; Mon, 27 Jul 2009 07:40:18 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:40:18 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:40:17 +0800
Message-Id: <DE6F28F9-C9AB-4E69-9DD4-B3D362557B3B@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <23CEFBAC26A6814695D4872E1CE3B1AC06C143FC@exchange-10.WIN.NOMINUM.COM>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 17:40:16 +1000
References: <4A6CD501.7030704@toshiba.co.jp>, <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <23CEFBAC26A6814695D4872E1CE3B1AC06C143FC@exchange-10.WIN.NOMINUM.COM>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 07:40:17.0844 (UTC) FILETIME=[7CAE0F40:01CA0E8D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=932; t=1248680418; x=1249544418; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=RGPSmdPMdb7IvW4Fn8SPZkpePYcg4EVY7ENnv/TQHnk=; b=IbWBL5yAJ7F93qi6VeKzfJJLNNfLBHq4JwhrO5jc9WVCPLlHDnI4atV/Cs 4gVHsCncSEee4+JICqjVMYY2gvhla9DmoDAM7UDMTFsLUg8CW5vWleoacg8z Eko4COeJww+azIKELKilm32uqjjDWVBRZVUxtDOSbo/VjvLDw1ve8=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:40:21 -0000

On 27/07/2009, at 5:27 PM, Ted Lemon wrote:

> On Sunday, July 26, 2009 10:55 PM, =Richard Pruss wrote"====
>> Relays in the broadband architecture have to be stateful to enforce
>> DHCP address assignment, so it is not a change to the existing
>> architecture.
>
> Ric, unless I am horribly out of touch with the state of the art  
> (always a possibilty), this statement is not in fact true.   It  
> seems that either you are using "relay agent" as a shorthand for  
> something that's more than a relay agent, or else you failed to  
> sufficiently constrain the set of situations in which your statement  
> applies.   It's true that *caching* state is common in relays in a  
> broadband environment, but that doesn't make those relays "stateful"  
> in the usual sense that we mean.

Okay I worded that badly the BRAS is state-full for the session, not  
necessarily DHCP relay function in the BRAS,
Ric


From yoshihiro.ohba@toshiba.co.jp  Mon Jul 27 00:50:56 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49AB828C176 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9D2o5W+NZHlF for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:50:54 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 2536A3A6A8B for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:50:53 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6R7oqDI004297; Mon, 27 Jul 2009 16:50:52 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6R7oplh016735; Mon, 27 Jul 2009 16:50:51 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id SAA16734; Mon, 27 Jul 2009 16:50:51 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6R7opbY005758; Mon, 27 Jul 2009 16:50:51 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6R7opeo020693; Mon, 27 Jul 2009 16:50:51 +0900 (JST)
Received: from [133.196.16.131] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNF00H5MKGQLP70@mail.po.toshiba.co.jp>; Mon, 27 Jul 2009 16:50:51 +0900 (JST)
Date: Mon, 27 Jul 2009 03:50:44 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6D5C54.6050904@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:50:56 -0000

Richard Pruss wrote:
> Well Ralph,  as you say something else is holding the state and the 
> relay agent is simply handing the EAP messages to the AAA  service in 
> the relay function... so no the question still makes no sense to me.
This is an incorrect statement. DHCP relay acting EAP authenticator is 
not simply handing EAP messages to the AAA, it needs to maintain a state 
including a retransmission timer to retransmit outstanding EAP-Request 
message (cf. RFC 4137).

Yoshihiro Ohba

>
>
> The thing that makes no sense is the assertion that the relay agent 
> suddenly needs to hold state, beyond what it already does to handle ip 
> unnumbered interfaces,
> Ric
>
> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>
>> Ric - the question seems sensible to me.
>>
>> I would consider enforcing the address assignment as a separate 
>> function of the box that happens to house the DHCP relay agent 
>> function.  That is, the relay agent extracts the assigned address 
>> from the DHCPACK and hands it to the address enforcement function.  
>> Therefore, the relay agent function is not keeping any state.  The 
>> address enforcement function could just as easily get that address 
>> assignment information from some other source like CLI or SNMP.
>>
>> The original purpose of the relay agent option was to hold state for 
>> the relay agent.  We've tried to maintain that stateless operation 
>> (but I'm not sure we've strictly enforced the rule) with the 
>> definition of subsequent relay agent options.
>>
>> - Ralph
>>
>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>
>>>
>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>
>>>> Richard Pruss wrote:
>>>>> Relay's in the broadband architecture have to be stateful to 
>>>>> enforce DHCP address assignment, so it is not a change to the 
>>>>> existing architecture.
>>>> As far as I understand, enforcing DHCP address assignment is needed 
>>>> *after* DHCP exchanges are done, and therefore the state is 
>>>> maintained outside the context of DHCP, which I don't care.  My 
>>>> comment was if DHCP relay needs to be stateful in the middle of 
>>>> DHCP exchanges to carry EAP.
>>>> From DHCP point of view, it seems to be a major design change to DHCP.
>>>
>>> Do you actually have an implementation of broadband DHCP relay 
>>> because  what you are talking makes very little sense?
>>>
>>> - Ric
>>>
>>>
>>>>
>>>> Regards,
>>>> Yoshihiro Ohba
>>>>
>>>>>
>>>>> - Ric
>>>>>
>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>
>>>>>> I have read both documents. Thanks for the authors for both 
>>>>>> documents providing techinical details.
>>>>>>
>>>>>> However, I still have an issue with carrying EAP over DHCP. The 
>>>>>> issue is basically a conflict between statefullness of EAP and 
>>>>>> statelessness of DHCP relay agent.
>>>>>>
>>>>>> As far as I understand, DHCP relay agent does not maintain a 
>>>>>> state. On the other hand, EAP requires peer and authenticator to 
>>>>>> maintain a state (see RFC 4137). When DHCP relay agent acts EAP 
>>>>>> authenticator, then the relay agent will be no longer a stateless 
>>>>>> DHCP entity. I think this is not discussed in dhcp-eap-analysis 
>>>>>> draft. Is this an acceptable design change for DHCP?  Or please 
>>>>>> correct me if I am wrong.
>>>>>>
>>>>>> Regards,
>>>>>> Yoshihiro Ohba
>>>>>> _______________________________________________
>>>>>> dhcwg mailing list
>>>>>> dhcwg@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>
>
>


From ric@cisco.com  Mon Jul 27 00:54:03 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B384D28C148 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySi1krRg4wj6 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:54:02 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 1928628C14D for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:53:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAPb5bEoKS+eh/2dsb2JhbAC4XIgojVsFhA0
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="58557947"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 27 Jul 2009 07:53:44 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6R7rhpe010690;  Mon, 27 Jul 2009 15:53:43 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R7rhfh022847; Mon, 27 Jul 2009 07:53:43 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:53:42 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 15:53:41 +0800
Message-Id: <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6D5C54.6050904@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 17:53:39 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 07:53:42.0079 (UTC) FILETIME=[5C0A94F0:01CA0E8F]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4208; t=1248681223; x=1249545223; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=pRWdkY2ugN5d9GcaiHCiIZDNz//pa0uzbvjxX/xhZjk=; b=oja5/sg/INdvnecGpbnJCJkygJcStTfZs5NqjFCFhs6WuKEnlv5eq3UFvP jpiejO/9QCHAzDIh1yVPysfDkPrvFG+vScw5bg9faIyGPqO9Cr6iY/QD7QJy KGOYQOj4bLrNeMGb5j9qxaCUOfWyOOsJXs0HV7U135uYAm5VtyWAc=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:54:03 -0000

On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>> Well Ralph,  as you say something else is holding the state and the  
>> relay agent is simply handing the EAP messages to the AAA  service  
>> in the relay function... so no the question still makes no sense to  
>> me.
> This is an incorrect statement. DHCP relay acting EAP authenticator  
> is not simply handing EAP messages to the AAA, it needs to maintain  
> a state including a retransmission timer to retransmit outstanding  
> EAP-Request message (cf. RFC 4137).

No mate this is the part you probably missed, EAP is doing that and it  
is a separate function regardless of what it is being carried on ,  
PPP, Ethernet, DHCP here is just transport.

- Ric


>
> Yoshihiro Ohba
>
>>
>>
>> The thing that makes no sense is the assertion that the relay agent  
>> suddenly needs to hold state, beyond what it already does to handle  
>> ip unnumbered interfaces,
>> Ric
>>
>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>
>>> Ric - the question seems sensible to me.
>>>
>>> I would consider enforcing the address assignment as a separate  
>>> function of the box that happens to house the DHCP relay agent  
>>> function.  That is, the relay agent extracts the assigned address  
>>> from the DHCPACK and hands it to the address enforcement  
>>> function.  Therefore, the relay agent function is not keeping any  
>>> state.  The address enforcement function could just as easily get  
>>> that address assignment information from some other source like  
>>> CLI or SNMP.
>>>
>>> The original purpose of the relay agent option was to hold state  
>>> for the relay agent.  We've tried to maintain that stateless  
>>> operation (but I'm not sure we've strictly enforced the rule) with  
>>> the definition of subsequent relay agent options.
>>>
>>> - Ralph
>>>
>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>
>>>>
>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>
>>>>> Richard Pruss wrote:
>>>>>> Relay's in the broadband architecture have to be stateful to  
>>>>>> enforce DHCP address assignment, so it is not a change to the  
>>>>>> existing architecture.
>>>>> As far as I understand, enforcing DHCP address assignment is  
>>>>> needed *after* DHCP exchanges are done, and therefore the state  
>>>>> is maintained outside the context of DHCP, which I don't care.   
>>>>> My comment was if DHCP relay needs to be stateful in the middle  
>>>>> of DHCP exchanges to carry EAP.
>>>>> From DHCP point of view, it seems to be a major design change to  
>>>>> DHCP.
>>>>
>>>> Do you actually have an implementation of broadband DHCP relay  
>>>> because  what you are talking makes very little sense?
>>>>
>>>> - Ric
>>>>
>>>>
>>>>>
>>>>> Regards,
>>>>> Yoshihiro Ohba
>>>>>
>>>>>>
>>>>>> - Ric
>>>>>>
>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>> I have read both documents. Thanks for the authors for both  
>>>>>>> documents providing techinical details.
>>>>>>>
>>>>>>> However, I still have an issue with carrying EAP over DHCP.  
>>>>>>> The issue is basically a conflict between statefullness of EAP  
>>>>>>> and statelessness of DHCP relay agent.
>>>>>>>
>>>>>>> As far as I understand, DHCP relay agent does not maintain a  
>>>>>>> state. On the other hand, EAP requires peer and authenticator  
>>>>>>> to maintain a state (see RFC 4137). When DHCP relay agent acts  
>>>>>>> EAP authenticator, then the relay agent will be no longer a  
>>>>>>> stateless DHCP entity. I think this is not discussed in dhcp- 
>>>>>>> eap-analysis draft. Is this an acceptable design change for  
>>>>>>> DHCP?  Or please correct me if I am wrong.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Yoshihiro Ohba
>>>>>>> _______________________________________________
>>>>>>> dhcwg mailing list
>>>>>>> dhcwg@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> dhcwg mailing list
>>>> dhcwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>
>>
>>
>>
>


From yoshihiro.ohba@toshiba.co.jp  Mon Jul 27 00:59:37 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD9C128C134 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kivxW5HQ6Vn7 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 00:59:36 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 836E328C108 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 00:59:36 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6R7xX32001883; Mon, 27 Jul 2009 16:59:33 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6R7xXkp003634; Mon, 27 Jul 2009 16:59:33 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id SAA03633; Mon, 27 Jul 2009 16:59:33 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6R7xXN6028847; Mon, 27 Jul 2009 16:59:33 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6R7xVoj006168; Mon, 27 Jul 2009 16:59:31 +0900 (JST)
Received: from [133.196.16.131] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNF00HPGKV7LX70@mail.po.toshiba.co.jp>; Mon, 27 Jul 2009 16:59:31 +0900 (JST)
Date: Mon, 27 Jul 2009 03:59:25 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6D5E5D.8070707@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 07:59:37 -0000

Richard Pruss wrote:
>
> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>
>> Richard Pruss wrote:
>>> Well Ralph,  as you say something else is holding the state and the 
>>> relay agent is simply handing the EAP messages to the AAA  service 
>>> in the relay function... so no the question still makes no sense to me.
>> This is an incorrect statement. DHCP relay acting EAP authenticator 
>> is not simply handing EAP messages to the AAA, it needs to maintain a 
>> state including a retransmission timer to retransmit outstanding 
>> EAP-Request message (cf. RFC 4137).
>
> No mate this is the part you probably missed, EAP is doing that and it 
> is a separate function regardless of what it is being carried on , 
> PPP, Ethernet, DHCP here is just transport.

All EAP transport protocols that I know of, including the ones you 
listed above requires to maintain a state to carry EAP message.  There 
is no exception.

Yoshihiro Ohba


>
> - Ric
>
>
>>
>> Yoshihiro Ohba
>>
>>>
>>>
>>> The thing that makes no sense is the assertion that the relay agent 
>>> suddenly needs to hold state, beyond what it already does to handle 
>>> ip unnumbered interfaces,
>>> Ric
>>>
>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>
>>>> Ric - the question seems sensible to me.
>>>>
>>>> I would consider enforcing the address assignment as a separate 
>>>> function of the box that happens to house the DHCP relay agent 
>>>> function.  That is, the relay agent extracts the assigned address 
>>>> from the DHCPACK and hands it to the address enforcement function.  
>>>> Therefore, the relay agent function is not keeping any state.  The 
>>>> address enforcement function could just as easily get that address 
>>>> assignment information from some other source like CLI or SNMP.
>>>>
>>>> The original purpose of the relay agent option was to hold state 
>>>> for the relay agent.  We've tried to maintain that stateless 
>>>> operation (but I'm not sure we've strictly enforced the rule) with 
>>>> the definition of subsequent relay agent options.
>>>>
>>>> - Ralph
>>>>
>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>
>>>>>
>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>> Richard Pruss wrote:
>>>>>>> Relay's in the broadband architecture have to be stateful to 
>>>>>>> enforce DHCP address assignment, so it is not a change to the 
>>>>>>> existing architecture.
>>>>>> As far as I understand, enforcing DHCP address assignment is 
>>>>>> needed *after* DHCP exchanges are done, and therefore the state 
>>>>>> is maintained outside the context of DHCP, which I don't care.  
>>>>>> My comment was if DHCP relay needs to be stateful in the middle 
>>>>>> of DHCP exchanges to carry EAP.
>>>>>> From DHCP point of view, it seems to be a major design change to 
>>>>>> DHCP.
>>>>>
>>>>> Do you actually have an implementation of broadband DHCP relay 
>>>>> because  what you are talking makes very little sense?
>>>>>
>>>>> - Ric
>>>>>
>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>>
>>>>>>> - Ric
>>>>>>>
>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>
>>>>>>>> I have read both documents. Thanks for the authors for both 
>>>>>>>> documents providing techinical details.
>>>>>>>>
>>>>>>>> However, I still have an issue with carrying EAP over DHCP. The 
>>>>>>>> issue is basically a conflict between statefullness of EAP and 
>>>>>>>> statelessness of DHCP relay agent.
>>>>>>>>
>>>>>>>> As far as I understand, DHCP relay agent does not maintain a 
>>>>>>>> state. On the other hand, EAP requires peer and authenticator 
>>>>>>>> to maintain a state (see RFC 4137). When DHCP relay agent acts 
>>>>>>>> EAP authenticator, then the relay agent will be no longer a 
>>>>>>>> stateless DHCP entity. I think this is not discussed in 
>>>>>>>> dhcp-eap-analysis draft. Is this an acceptable design change 
>>>>>>>> for DHCP?  Or please correct me if I am wrong.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Yoshihiro Ohba
>>>>>>>> _______________________________________________
>>>>>>>> dhcwg mailing list
>>>>>>>> dhcwg@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dhcwg mailing list
>>>>> dhcwg@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>
>>>
>>>
>>>
>>
>
>
>


From ric@cisco.com  Mon Jul 27 01:11:02 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EFB23A6C12 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level: 
X-Spam-Status: No, score=-5.799 tagged_above=-999 required=5 tests=[AWL=0.800,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id krOtlnQXRGh4 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:11:01 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id A636C3A6C0F for <dhcwg@ietf.org>; Mon, 27 Jul 2009 01:10:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAIb9bEoKS+eh/2dsb2JhbAC4YIgojWEFhA0
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="58558891"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 27 Jul 2009 08:10:57 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6R8AuGN014226;  Mon, 27 Jul 2009 16:10:56 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R8AY4q026920; Mon, 27 Jul 2009 08:10:56 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 16:10:47 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 16:10:46 +0800
Message-Id: <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6D5E5D.8070707@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 18:10:44 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 08:10:46.0891 (UTC) FILETIME=[BEE07BB0:01CA0E91]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4766; t=1248682257; x=1249546257; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=zXqTBJ55QADIiwkMsx3EWDrTMuEvaabTLhtB9jZlp+0=; b=GwI28rtaOrkMYo7tP7bSdHHqy2aS9qouLYKhAPPIJhloHJ/nVS6vpe/gx+ 466xHTzaAnVu1Rp6PUvmbzZ8x7iYJRf/yDfceq3mm8gBGtEkIqdl5eJpMHCS 8kmnb0NaboRI4GZ9i/TqgPZTNiGCAwCMtEU8mdrb4zY/F2wkLH/zA=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 08:11:02 -0000

On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>>
>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>
>>> Richard Pruss wrote:
>>>> Well Ralph,  as you say something else is holding the state and  
>>>> the relay agent is simply handing the EAP messages to the AAA   
>>>> service in the relay function... so no the question still makes  
>>>> no sense to me.
>>> This is an incorrect statement. DHCP relay acting EAP  
>>> authenticator is not simply handing EAP messages to the AAA, it  
>>> needs to maintain a state including a retransmission timer to  
>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>
>> No mate this is the part you probably missed, EAP is doing that and  
>> it is a separate function regardless of what it is being carried  
>> on , PPP, Ethernet, DHCP here is just transport.
>
> All EAP transport protocols that I know of, including the ones you  
> listed above requires to maintain a state to carry EAP message.   
> There is no exception.
What state?

>
> Yoshihiro Ohba
>
>
>>
>> - Ric
>>
>>
>>>
>>> Yoshihiro Ohba
>>>
>>>>
>>>>
>>>> The thing that makes no sense is the assertion that the relay  
>>>> agent suddenly needs to hold state, beyond what it already does  
>>>> to handle ip unnumbered interfaces,
>>>> Ric
>>>>
>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>
>>>>> Ric - the question seems sensible to me.
>>>>>
>>>>> I would consider enforcing the address assignment as a separate  
>>>>> function of the box that happens to house the DHCP relay agent  
>>>>> function.  That is, the relay agent extracts the assigned  
>>>>> address from the DHCPACK and hands it to the address enforcement  
>>>>> function.  Therefore, the relay agent function is not keeping  
>>>>> any state.  The address enforcement function could just as  
>>>>> easily get that address assignment information from some other  
>>>>> source like CLI or SNMP.
>>>>>
>>>>> The original purpose of the relay agent option was to hold state  
>>>>> for the relay agent.  We've tried to maintain that stateless  
>>>>> operation (but I'm not sure we've strictly enforced the rule)  
>>>>> with the definition of subsequent relay agent options.
>>>>>
>>>>> - Ralph
>>>>>
>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>
>>>>>>
>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>> Richard Pruss wrote:
>>>>>>>> Relay's in the broadband architecture have to be stateful to  
>>>>>>>> enforce DHCP address assignment, so it is not a change to the  
>>>>>>>> existing architecture.
>>>>>>> As far as I understand, enforcing DHCP address assignment is  
>>>>>>> needed *after* DHCP exchanges are done, and therefore the  
>>>>>>> state is maintained outside the context of DHCP, which I don't  
>>>>>>> care.  My comment was if DHCP relay needs to be stateful in  
>>>>>>> the middle of DHCP exchanges to carry EAP.
>>>>>>> From DHCP point of view, it seems to be a major design change  
>>>>>>> to DHCP.
>>>>>>
>>>>>> Do you actually have an implementation of broadband DHCP relay  
>>>>>> because  what you are talking makes very little sense?
>>>>>>
>>>>>> - Ric
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>>
>>>>>>>> - Ric
>>>>>>>>
>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>
>>>>>>>>> I have read both documents. Thanks for the authors for both  
>>>>>>>>> documents providing techinical details.
>>>>>>>>>
>>>>>>>>> However, I still have an issue with carrying EAP over DHCP.  
>>>>>>>>> The issue is basically a conflict between statefullness of  
>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>
>>>>>>>>> As far as I understand, DHCP relay agent does not maintain a  
>>>>>>>>> state. On the other hand, EAP requires peer and  
>>>>>>>>> authenticator to maintain a state (see RFC 4137). When DHCP  
>>>>>>>>> relay agent acts EAP authenticator, then the relay agent  
>>>>>>>>> will be no longer a stateless DHCP entity. I think this is  
>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an  
>>>>>>>>> acceptable design change for DHCP?  Or please correct me if  
>>>>>>>>> I am wrong.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Yoshihiro Ohba
>>>>>>>>> _______________________________________________
>>>>>>>>> dhcwg mailing list
>>>>>>>>> dhcwg@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> dhcwg mailing list
>>>>>> dhcwg@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>


From yoshihiro.ohba@toshiba.co.jp  Mon Jul 27 01:42:12 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAB4728C23A for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:42:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id spPZX0oG6OMa for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:42:11 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 6422328C237 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 01:42:11 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6R8g95i028207; Mon, 27 Jul 2009 17:42:09 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6R8g9Cg016551; Mon, 27 Jul 2009 17:42:09 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id TAA16550; Mon, 27 Jul 2009 17:42:09 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6R8g9Po020435; Mon, 27 Jul 2009 17:42:09 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6R8g8LB012947; Mon, 27 Jul 2009 17:42:08 +0900 (JST)
Received: from [133.196.16.131] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNF00HATMU8LI80@mail.po.toshiba.co.jp>; Mon, 27 Jul 2009 17:42:08 +0900 (JST)
Date: Mon, 27 Jul 2009 04:42:02 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6D685A.7000406@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 08:42:13 -0000

In general, a state on the logical connection between the peer and 
authenticator needs to be maintained by any EAP lower-layer for each EAP 
conversation. Such a state at least includes transport addresses and/or 
port numbers and they are not carried in EAP message.

Yoshihiro Ohba


Richard Pruss wrote:
>
> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>
>> Richard Pruss wrote:
>>>
>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>
>>>> Richard Pruss wrote:
>>>>> Well Ralph,  as you say something else is holding the state and 
>>>>> the relay agent is simply handing the EAP messages to the AAA  
>>>>> service in the relay function... so no the question still makes no 
>>>>> sense to me.
>>>> This is an incorrect statement. DHCP relay acting EAP authenticator 
>>>> is not simply handing EAP messages to the AAA, it needs to maintain 
>>>> a state including a retransmission timer to retransmit outstanding 
>>>> EAP-Request message (cf. RFC 4137).
>>>
>>> No mate this is the part you probably missed, EAP is doing that and 
>>> it is a separate function regardless of what it is being carried on 
>>> , PPP, Ethernet, DHCP here is just transport.
>>
>> All EAP transport protocols that I know of, including the ones you 
>> listed above requires to maintain a state to carry EAP message.  
>> There is no exception.
> What state?
>
>>
>> Yoshihiro Ohba
>>
>>
>>>
>>> - Ric
>>>
>>>
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>>
>>>>>
>>>>> The thing that makes no sense is the assertion that the relay 
>>>>> agent suddenly needs to hold state, beyond what it already does to 
>>>>> handle ip unnumbered interfaces,
>>>>> Ric
>>>>>
>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>
>>>>>> Ric - the question seems sensible to me.
>>>>>>
>>>>>> I would consider enforcing the address assignment as a separate 
>>>>>> function of the box that happens to house the DHCP relay agent 
>>>>>> function.  That is, the relay agent extracts the assigned address 
>>>>>> from the DHCPACK and hands it to the address enforcement 
>>>>>> function.  Therefore, the relay agent function is not keeping any 
>>>>>> state.  The address enforcement function could just as easily get 
>>>>>> that address assignment information from some other source like 
>>>>>> CLI or SNMP.
>>>>>>
>>>>>> The original purpose of the relay agent option was to hold state 
>>>>>> for the relay agent.  We've tried to maintain that stateless 
>>>>>> operation (but I'm not sure we've strictly enforced the rule) 
>>>>>> with the definition of subsequent relay agent options.
>>>>>>
>>>>>> - Ralph
>>>>>>
>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>
>>>>>>>
>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>
>>>>>>>> Richard Pruss wrote:
>>>>>>>>> Relay's in the broadband architecture have to be stateful to 
>>>>>>>>> enforce DHCP address assignment, so it is not a change to the 
>>>>>>>>> existing architecture.
>>>>>>>> As far as I understand, enforcing DHCP address assignment is 
>>>>>>>> needed *after* DHCP exchanges are done, and therefore the state 
>>>>>>>> is maintained outside the context of DHCP, which I don't care.  
>>>>>>>> My comment was if DHCP relay needs to be stateful in the middle 
>>>>>>>> of DHCP exchanges to carry EAP.
>>>>>>>> >From DHCP point of view, it seems to be a major design change 
>>>>>>>> to DHCP.
>>>>>>>
>>>>>>> Do you actually have an implementation of broadband DHCP relay 
>>>>>>> because  what you are talking makes very little sense?
>>>>>>>
>>>>>>> - Ric
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Yoshihiro Ohba
>>>>>>>>
>>>>>>>>>
>>>>>>>>> - Ric
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>
>>>>>>>>>> I have read both documents. Thanks for the authors for both 
>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>
>>>>>>>>>> However, I still have an issue with carrying EAP over DHCP. 
>>>>>>>>>> The issue is basically a conflict between statefullness of 
>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>
>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain a 
>>>>>>>>>> state. On the other hand, EAP requires peer and authenticator 
>>>>>>>>>> to maintain a state (see RFC 4137). When DHCP relay agent 
>>>>>>>>>> acts EAP authenticator, then the relay agent will be no 
>>>>>>>>>> longer a stateless DHCP entity. I think this is not discussed 
>>>>>>>>>> in dhcp-eap-analysis draft. Is this an acceptable design 
>>>>>>>>>> change for DHCP?  Or please correct me if I am wrong.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dhcwg mailing list
>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dhcwg mailing list
>>>>>>> dhcwg@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>



From rdroms@cisco.com  Mon Jul 27 01:47:35 2009
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBBAA28C222 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49J6IBYxqP8u for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 01:47:35 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id C532728C123 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 01:47:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,275,1246838400"; d="scan'208";a="354559326"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 27 Jul 2009 08:47:35 +0000
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6R8lZHX006833;  Mon, 27 Jul 2009 01:47:35 -0700
Received: from sjc-vpnasa-497.cisco.com (sjc-vpnasa-497.cisco.com [10.21.105.243]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n6R8lXu8025081; Mon, 27 Jul 2009 08:47:34 GMT
Message-Id: <8A278ED7-8A77-4D62-9487-55308D4B4B5B@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Richard Pruss <ric@cisco.com>
In-Reply-To: <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 10:47:32 +0200
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3973; t=1248684455; x=1249548455; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=yG/SK78GK3qyYFKl6n835ZeMtjgFeYbsBbw5tzgHlUU=; b=c/f54RVmuPjrIehvclUx8sfv/47jGLh/mqtpWzUyll+LPO6K5SVYn0s3fl rbu6GL2IBHS6BLrkS09XOh26rpoYldBkUK96i0fiTtTvM2kc9revbTfWXFVK X+1n/b1nhh;
Authentication-Results: sj-dkim-3; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 08:47:36 -0000

Ric - my understanding is that the relay agent would have to hold  
state, including the original message from the DHCP client, for each  
of the outstanding message exchanges that have been handed off to the  
EAP function.

I suppose the relay agent could discard the original message and rely  
on the client to retransmit after the EAP-over-DHCP exchange...

- Ralph

On Jul 27, 2009, at 9:39 AM 7/27/09, Richard Pruss wrote:

> Well Ralph,  as you say something else is holding the state and the  
> relay agent is simply handing the EAP messages to the AAA  service  
> in the relay function... so no the question still makes no sense to  
> me.
>
> The thing that makes no sense is the assertion that the relay agent  
> suddenly needs to hold state, beyond what it already does to handle  
> ip unnumbered interfaces,
> Ric
>
> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>
>> Ric - the question seems sensible to me.
>>
>> I would consider enforcing the address assignment as a separate  
>> function of the box that happens to house the DHCP relay agent  
>> function.  That is, the relay agent extracts the assigned address  
>> from the DHCPACK and hands it to the address enforcement function.   
>> Therefore, the relay agent function is not keeping any state.  The  
>> address enforcement function could just as easily get that address  
>> assignment information from some other source like CLI or SNMP.
>>
>> The original purpose of the relay agent option was to hold state  
>> for the relay agent.  We've tried to maintain that stateless  
>> operation (but I'm not sure we've strictly enforced the rule) with  
>> the definition of subsequent relay agent options.
>>
>> - Ralph
>>
>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>
>>>
>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>
>>>> Richard Pruss wrote:
>>>>> Relay's in the broadband architecture have to be stateful to  
>>>>> enforce DHCP address assignment, so it is not a change to the  
>>>>> existing architecture.
>>>> As far as I understand, enforcing DHCP address assignment is  
>>>> needed *after* DHCP exchanges are done, and therefore the state  
>>>> is maintained outside the context of DHCP, which I don't care.   
>>>> My comment was if DHCP relay needs to be stateful in the middle  
>>>> of DHCP exchanges to carry EAP.
>>>> From DHCP point of view, it seems to be a major design change to  
>>>> DHCP.
>>>
>>> Do you actually have an implementation of broadband DHCP relay  
>>> because  what you are talking makes very little sense?
>>>
>>> - Ric
>>>
>>>
>>>>
>>>> Regards,
>>>> Yoshihiro Ohba
>>>>
>>>>>
>>>>> - Ric
>>>>>
>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>
>>>>>> I have read both documents. Thanks for the authors for both  
>>>>>> documents providing techinical details.
>>>>>>
>>>>>> However, I still have an issue with carrying EAP over DHCP. The  
>>>>>> issue is basically a conflict between statefullness of EAP and  
>>>>>> statelessness of DHCP relay agent.
>>>>>>
>>>>>> As far as I understand, DHCP relay agent does not maintain a  
>>>>>> state. On the other hand, EAP requires peer and authenticator  
>>>>>> to maintain a state (see RFC 4137). When DHCP relay agent acts  
>>>>>> EAP authenticator, then the relay agent will be no longer a  
>>>>>> stateless DHCP entity. I think this is not discussed in dhcp- 
>>>>>> eap-analysis draft. Is this an acceptable design change for  
>>>>>> DHCP?  Or please correct me if I am wrong.
>>>>>>
>>>>>> Regards,
>>>>>> Yoshihiro Ohba
>>>>>> _______________________________________________
>>>>>> dhcwg mailing list
>>>>>> dhcwg@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>


From ric@cisco.com  Mon Jul 27 02:27:56 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A70963A6C53 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 02:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjvJMlzfGcel for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 02:27:55 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id CBAC83A6C44 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 02:27:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEADoQbUoKS+ej/2dsb2JhbAC4Q4gojWcFhA0
X-IronPort-AV: E=Sophos;i="4.43,276,1246838400"; d="scan'208";a="58562512"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-1.cisco.com with ESMTP; 27 Jul 2009 09:27:53 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6R9RqHg032517;  Mon, 27 Jul 2009 17:27:52 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6R9KZ6K012224; Mon, 27 Jul 2009 09:27:52 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 17:27:22 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Jul 2009 17:27:21 +0800
Message-Id: <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6D685A.7000406@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 27 Jul 2009 19:27:19 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 27 Jul 2009 09:27:21.0636 (UTC) FILETIME=[718EEE40:01CA0E9C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5615; t=1248686873; x=1249550873; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=2v7kOESSnv5313wfxNA3nsECFIoFMtcGIhX5WcDx3SE=; b=NwZO8HgOe7EgqXCrCS7nYO7R98J1vniZ1Zz3eMNCJ0bK1L08LOn6du0ZH1 9UbIvHmLuYtMwASq9SWj8z4vp7tEX808VE3kkRiHsko9Ldqkp0egvhhFLDaf 0kvrkVD9dSYBG06CK97K2W++KkiafOHh0uP8gyuiD4sJ5KGEQjS64=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 09:27:56 -0000

As I said to Ralph earlier we track transport and port associations  
already to facilitate unnumbered interfaces, so the question was what  
state beyond that.

On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:

>
> In general, a state on the logical connection between the peer and  
> authenticator needs to be maintained by any EAP lower-layer for each  
> EAP conversation. Such a state at least includes transport addresses  
> and/or port numbers and they are not carried in EAP message.
>
> Yoshihiro Ohba
>
>
> Richard Pruss wrote:
>>
>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>
>>> Richard Pruss wrote:
>>>>
>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>
>>>>> Richard Pruss wrote:
>>>>>> Well Ralph,  as you say something else is holding the state and  
>>>>>> the relay agent is simply handing the EAP messages to the AAA   
>>>>>> service in the relay function... so no the question still makes  
>>>>>> no sense to me.
>>>>> This is an incorrect statement. DHCP relay acting EAP  
>>>>> authenticator is not simply handing EAP messages to the AAA, it  
>>>>> needs to maintain a state including a retransmission timer to  
>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>
>>>> No mate this is the part you probably missed, EAP is doing that  
>>>> and it is a separate function regardless of what it is being  
>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>
>>> All EAP transport protocols that I know of, including the ones you  
>>> listed above requires to maintain a state to carry EAP message.   
>>> There is no exception.
>> What state?
>>
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>>>
>>>> - Ric
>>>>
>>>>
>>>>>
>>>>> Yoshihiro Ohba
>>>>>
>>>>>>
>>>>>>
>>>>>> The thing that makes no sense is the assertion that the relay  
>>>>>> agent suddenly needs to hold state, beyond what it already does  
>>>>>> to handle ip unnumbered interfaces,
>>>>>> Ric
>>>>>>
>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>
>>>>>>> Ric - the question seems sensible to me.
>>>>>>>
>>>>>>> I would consider enforcing the address assignment as a  
>>>>>>> separate function of the box that happens to house the DHCP  
>>>>>>> relay agent function.  That is, the relay agent extracts the  
>>>>>>> assigned address from the DHCPACK and hands it to the address  
>>>>>>> enforcement function.  Therefore, the relay agent function is  
>>>>>>> not keeping any state.  The address enforcement function could  
>>>>>>> just as easily get that address assignment information from  
>>>>>>> some other source like CLI or SNMP.
>>>>>>>
>>>>>>> The original purpose of the relay agent option was to hold  
>>>>>>> state for the relay agent.  We've tried to maintain that  
>>>>>>> stateless operation (but I'm not sure we've strictly enforced  
>>>>>>> the rule) with the definition of subsequent relay agent options.
>>>>>>>
>>>>>>> - Ralph
>>>>>>>
>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>
>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>> Relay's in the broadband architecture have to be stateful  
>>>>>>>>>> to enforce DHCP address assignment, so it is not a change  
>>>>>>>>>> to the existing architecture.
>>>>>>>>> As far as I understand, enforcing DHCP address assignment is  
>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the  
>>>>>>>>> state is maintained outside the context of DHCP, which I  
>>>>>>>>> don't care.  My comment was if DHCP relay needs to be  
>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>> >From DHCP point of view, it seems to be a major design  
>>>>>>>>> change to DHCP.
>>>>>>>>
>>>>>>>> Do you actually have an implementation of broadband DHCP  
>>>>>>>> relay because  what you are talking makes very little sense?
>>>>>>>>
>>>>>>>> - Ric
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> - Ric
>>>>>>>>>>
>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>
>>>>>>>>>>> I have read both documents. Thanks for the authors for  
>>>>>>>>>>> both documents providing techinical details.
>>>>>>>>>>>
>>>>>>>>>>> However, I still have an issue with carrying EAP over  
>>>>>>>>>>> DHCP. The issue is basically a conflict between  
>>>>>>>>>>> statefullness of EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>
>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain  
>>>>>>>>>>> a state. On the other hand, EAP requires peer and  
>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When  
>>>>>>>>>>> DHCP relay agent acts EAP authenticator, then the relay  
>>>>>>>>>>> agent will be no longer a stateless DHCP entity. I think  
>>>>>>>>>>> this is not discussed in dhcp-eap-analysis draft. Is this  
>>>>>>>>>>> an acceptable design change for DHCP?  Or please correct  
>>>>>>>>>>> me if I am wrong.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> dhcwg mailing list
>>>>>>>> dhcwg@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
>


From alper.yegin@yegin.org  Mon Jul 27 08:03:05 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF95E28C25E for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 08:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2-ObsBPa52D for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 08:03:04 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 6807E28C256 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 08:03:01 -0700 (PDT)
Received: from LENOVO (dhcp-57aa.meeting.ietf.org [130.129.87.170]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MVRiz143R-00017t; Mon, 27 Jul 2009 11:02:54 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Richard Pruss'" <ric@cisco.com>, "'Yoshihiro Ohba'" <yoshihiro.ohba@toshiba.co.jp>
References: <4A6CD501.7030704@toshiba.co.jp>	<C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>	<4A6D4F53.2060608@toshiba.co.jp>	<270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>	<8BABA261-DE48-4684-85C8-419591061672@cisco.com>	<9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>	<4A6D5C54.6050904@toshiba.co.jp>	<CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>	<4A6D5E5D.8070707@toshiba.co.jp>	<7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>	<4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>
In-Reply-To: <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>
Date: Mon, 27 Jul 2009 18:02:44 +0300
Message-ID: <015e01ca0ecb$4fdacdd0$ef906970$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcoOnI0xR4Jy7LvQQHmzxK1bQQHqSwAGE09A
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX18jZVneuL9PMzjbGlQVFs7TmgQGHM5bMNhKzmZ 6gmVsLFZ0LUYsm0mErd9fXY4rBaA+59/OQa4m74iSbqOotSLAh SaA4jfsVX5O98FJ1f/Zuw==
Cc: 'dhc WG' <dhcwg@ietf.org>, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 15:03:05 -0000

Your DHCP relay, now that it wants to be an EAP lower-layer, has to keep
track of the EAP sessions. For each EAP session, it has to know the
associated DHCP session and AAA (RADIUS, Diameter) session. If you wonder
why so, think of how would the DHCP relay know which host to transmit the
EAP request to when it receives an EAP request from AAA client
implementation? The same "mapping" issue arises for the EAP responses that
are bridged from the EAP peer side to the authentication server side by the
DHCP relay implementation. 

Aside from having to deal with "handles" needed for demultiplexing, sooner
or later key derivation will be needed by the BBF (e.g., for securing DHCP,
L2, etc.) and MSK will also be stored by the EAP lower-layer -- namely your
DHCP relay.

Alper

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Richard Pruss
> Sent: Monday, July 27, 2009 12:27 PM
> To: Yoshihiro Ohba
> Cc: dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
> 
> As I said to Ralph earlier we track transport and port associations
> already to facilitate unnumbered interfaces, so the question was what
> state beyond that.
> 
> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
> 
> >
> > In general, a state on the logical connection between the peer and
> > authenticator needs to be maintained by any EAP lower-layer for each
> > EAP conversation. Such a state at least includes transport addresses
> > and/or port numbers and they are not carried in EAP message.
> >
> > Yoshihiro Ohba
> >
> >
> > Richard Pruss wrote:
> >>
> >> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
> >>
> >>> Richard Pruss wrote:
> >>>>
> >>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
> >>>>
> >>>>> Richard Pruss wrote:
> >>>>>> Well Ralph,  as you say something else is holding the state and
> >>>>>> the relay agent is simply handing the EAP messages to the AAA
> >>>>>> service in the relay function... so no the question still makes
> >>>>>> no sense to me.
> >>>>> This is an incorrect statement. DHCP relay acting EAP
> >>>>> authenticator is not simply handing EAP messages to the AAA, it
> >>>>> needs to maintain a state including a retransmission timer to
> >>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
> >>>>
> >>>> No mate this is the part you probably missed, EAP is doing that
> >>>> and it is a separate function regardless of what it is being
> >>>> carried on , PPP, Ethernet, DHCP here is just transport.
> >>>
> >>> All EAP transport protocols that I know of, including the ones you
> >>> listed above requires to maintain a state to carry EAP message.
> >>> There is no exception.
> >> What state?
> >>
> >>>
> >>> Yoshihiro Ohba
> >>>
> >>>
> >>>>
> >>>> - Ric
> >>>>
> >>>>
> >>>>>
> >>>>> Yoshihiro Ohba
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>> The thing that makes no sense is the assertion that the relay
> >>>>>> agent suddenly needs to hold state, beyond what it already does
> >>>>>> to handle ip unnumbered interfaces,
> >>>>>> Ric
> >>>>>>
> >>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
> >>>>>>
> >>>>>>> Ric - the question seems sensible to me.
> >>>>>>>
> >>>>>>> I would consider enforcing the address assignment as a
> >>>>>>> separate function of the box that happens to house the DHCP
> >>>>>>> relay agent function.  That is, the relay agent extracts the
> >>>>>>> assigned address from the DHCPACK and hands it to the address
> >>>>>>> enforcement function.  Therefore, the relay agent function is
> >>>>>>> not keeping any state.  The address enforcement function could
> >>>>>>> just as easily get that address assignment information from
> >>>>>>> some other source like CLI or SNMP.
> >>>>>>>
> >>>>>>> The original purpose of the relay agent option was to hold
> >>>>>>> state for the relay agent.  We've tried to maintain that
> >>>>>>> stateless operation (but I'm not sure we've strictly enforced
> >>>>>>> the rule) with the definition of subsequent relay agent
> options.
> >>>>>>>
> >>>>>>> - Ralph
> >>>>>>>
> >>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
> >>>>>>>
> >>>>>>>>
> >>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
> >>>>>>>>
> >>>>>>>>> Richard Pruss wrote:
> >>>>>>>>>> Relay's in the broadband architecture have to be stateful
> >>>>>>>>>> to enforce DHCP address assignment, so it is not a change
> >>>>>>>>>> to the existing architecture.
> >>>>>>>>> As far as I understand, enforcing DHCP address assignment is
> >>>>>>>>> needed *after* DHCP exchanges are done, and therefore the
> >>>>>>>>> state is maintained outside the context of DHCP, which I
> >>>>>>>>> don't care.  My comment was if DHCP relay needs to be
> >>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
> >>>>>>>>> >From DHCP point of view, it seems to be a major design
> >>>>>>>>> change to DHCP.
> >>>>>>>>
> >>>>>>>> Do you actually have an implementation of broadband DHCP
> >>>>>>>> relay because  what you are talking makes very little sense?
> >>>>>>>>
> >>>>>>>> - Ric
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Regards,
> >>>>>>>>> Yoshihiro Ohba
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> - Ric
> >>>>>>>>>>
> >>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I have read both documents. Thanks for the authors for
> >>>>>>>>>>> both documents providing techinical details.
> >>>>>>>>>>>
> >>>>>>>>>>> However, I still have an issue with carrying EAP over
> >>>>>>>>>>> DHCP. The issue is basically a conflict between
> >>>>>>>>>>> statefullness of EAP and statelessness of DHCP relay agent.
> >>>>>>>>>>>
> >>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain
> >>>>>>>>>>> a state. On the other hand, EAP requires peer and
> >>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
> >>>>>>>>>>> DHCP relay agent acts EAP authenticator, then the relay
> >>>>>>>>>>> agent will be no longer a stateless DHCP entity. I think
> >>>>>>>>>>> this is not discussed in dhcp-eap-analysis draft. Is this
> >>>>>>>>>>> an acceptable design change for DHCP?  Or please correct
> >>>>>>>>>>> me if I am wrong.
> >>>>>>>>>>>
> >>>>>>>>>>> Regards,
> >>>>>>>>>>> Yoshihiro Ohba
> >>>>>>>>>>> _______________________________________________
> >>>>>>>>>>> dhcwg mailing list
> >>>>>>>>>>> dhcwg@ietf.org
> >>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> dhcwg mailing list
> >>>>>>>> dhcwg@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >>
> >>
> >
> >
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From yoshihiro.ohba@toshiba.co.jp  Mon Jul 27 08:29:50 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 866023A6B0D for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 08:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.789
X-Spam-Level: 
X-Spam-Status: No, score=-2.789 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzD6+4zautD4 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 08:29:49 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 491DE28C1C7 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 08:29:49 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6RFTlOo013023; Tue, 28 Jul 2009 00:29:47 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6RFTlZL018229; Tue, 28 Jul 2009 00:29:47 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id AAA18228; Tue, 28 Jul 2009 00:29:47 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6RFTlTe019307; Tue, 28 Jul 2009 00:29:47 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6RFTkt9026079; Tue, 28 Jul 2009 00:29:46 +0900 (JST)
Received: from [133.199.17.40] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNG00HJK5PMLLA0@mail.po.toshiba.co.jp>; Tue, 28 Jul 2009 00:29:46 +0900 (JST)
Date: Mon, 27 Jul 2009 11:29:39 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6DC7E3.2010001@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 15:29:50 -0000

Richard Pruss wrote:
> As I said to Ralph earlier we track transport and port associations 
> already to facilitate unnumbered interfaces, so the question was what 
> state beyond that.
Beyond that each EAP conversation needs to be mapped to a distinct 
transport and port association, which will require a state maintained by 
DHCP relay.

Yoshihiro Ohba

>
> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>
>>
>> In general, a state on the logical connection between the peer and 
>> authenticator needs to be maintained by any EAP lower-layer for each 
>> EAP conversation. Such a state at least includes transport addresses 
>> and/or port numbers and they are not carried in EAP message.
>>
>> Yoshihiro Ohba
>>
>>
>> Richard Pruss wrote:
>>>
>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>
>>>> Richard Pruss wrote:
>>>>>
>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>> Richard Pruss wrote:
>>>>>>> Well Ralph,  as you say something else is holding the state and 
>>>>>>> the relay agent is simply handing the EAP messages to the AAA  
>>>>>>> service in the relay function... so no the question still makes 
>>>>>>> no sense to me.
>>>>>> This is an incorrect statement. DHCP relay acting EAP 
>>>>>> authenticator is not simply handing EAP messages to the AAA, it 
>>>>>> needs to maintain a state including a retransmission timer to 
>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>
>>>>> No mate this is the part you probably missed, EAP is doing that 
>>>>> and it is a separate function regardless of what it is being 
>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>
>>>> All EAP transport protocols that I know of, including the ones you 
>>>> listed above requires to maintain a state to carry EAP message.  
>>>> There is no exception.
>>> What state?
>>>
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>
>>>>>
>>>>> - Ric
>>>>>
>>>>>
>>>>>>
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The thing that makes no sense is the assertion that the relay 
>>>>>>> agent suddenly needs to hold state, beyond what it already does 
>>>>>>> to handle ip unnumbered interfaces,
>>>>>>> Ric
>>>>>>>
>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>
>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>
>>>>>>>> I would consider enforcing the address assignment as a separate 
>>>>>>>> function of the box that happens to house the DHCP relay agent 
>>>>>>>> function.  That is, the relay agent extracts the assigned 
>>>>>>>> address from the DHCPACK and hands it to the address 
>>>>>>>> enforcement function.  Therefore, the relay agent function is 
>>>>>>>> not keeping any state.  The address enforcement function could 
>>>>>>>> just as easily get that address assignment information from 
>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>
>>>>>>>> The original purpose of the relay agent option was to hold 
>>>>>>>> state for the relay agent.  We've tried to maintain that 
>>>>>>>> stateless operation (but I'm not sure we've strictly enforced 
>>>>>>>> the rule) with the definition of subsequent relay agent options.
>>>>>>>>
>>>>>>>> - Ralph
>>>>>>>>
>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>
>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>> Relay's in the broadband architecture have to be stateful to 
>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to 
>>>>>>>>>>> the existing architecture.
>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is 
>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the 
>>>>>>>>>> state is maintained outside the context of DHCP, which I 
>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be 
>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>> >From DHCP point of view, it seems to be a major design change 
>>>>>>>>>> to DHCP.
>>>>>>>>>
>>>>>>>>> Do you actually have an implementation of broadband DHCP relay 
>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>
>>>>>>>>> - Ric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> - Ric
>>>>>>>>>>>
>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have read both documents. Thanks for the authors for both 
>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>
>>>>>>>>>>>> However, I still have an issue with carrying EAP over DHCP. 
>>>>>>>>>>>> The issue is basically a conflict between statefullness of 
>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>
>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain 
>>>>>>>>>>>> a state. On the other hand, EAP requires peer and 
>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When DHCP 
>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent 
>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this is 
>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an 
>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me if 
>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> dhcwg mailing list
>>>>>>>>> dhcwg@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>


From David.Miles@alcatel-lucent.com.au  Mon Jul 27 16:54:03 2009
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8B3E3A691B for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 16:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-dh0CNqqK68 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 16:54:02 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by core3.amsl.com (Postfix) with ESMTP id 445543A6C45 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 16:53:33 -0700 (PDT)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id n6RNrSET002474; Mon, 27 Jul 2009 18:53:28 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id n6RNrOvx008008; Mon, 27 Jul 2009 18:53:26 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com [135.254.109.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n6RNljwA000687; Tue, 28 Jul 2009 07:47:46 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Jul 2009 07:53:20 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Jul 2009 07:53:19 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <4A6DC7E3.2010001@toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoOzxxEOvuPSMRlTzmpMkUxe6kJcQARGZMg
References: <4A6CD501.7030704@toshiba.co.jp><C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com><4A6D4F53.2060608@toshiba.co.jp><270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com><8BABA261-DE48-4684-85C8-419591061672@cisco.com><9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com><4A6D5C54.6050904@toshiba.co.jp><CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com><4A6D5E5D.8070707@toshiba.co.jp><7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com><4A6D685A.7000406@toshiba.co.jp><6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp>
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: "Yoshihiro Ohba" <yoshihiro.ohba@toshiba.co.jp>, "Richard Pruss" <ric@cisco.com>
X-OriginalArrivalTime: 27 Jul 2009 23:53:20.0181 (UTC) FILETIME=[6B43B650:01CA0F15]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.27
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 23:54:03 -0000

I wish to ask a question for clarification.

I understood the proposal in draft-pruss-auth-dsl was that the DHCP
client was in fact also the EAP supplicant. There is no EAPoL or 802.1x
device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
conversion.

While the EAP/DHCP client on Home Gateway and Server will need to be
aware/stateful with respect to EAP why would this extend to a DHCP
relay? Is this not similar to the case of EAP-Message over RADIUS? A
RADIUS proxy does not need to be aware of the details of the EAP-Message
nor be able to decode them.

In the proposed DHCP message exchange of DISCOVER, DHCPEAP, DHCPOFFER,
ACK I see no requirement for a stateful DHCP relay to support DHCPEAP.
As with other DHCP relayed messages there is sufficient information in
the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
received from the DHCP server to forward this message to the Home
Gateway (operating as DHCP client and EAP supplicant).

d

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Yoshihiro Ohba
Sent: Tuesday, July 28, 2009 1:00 AM
To: Richard Pruss
Cc: dhc WG; Ralph Droms
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
draft-brzozowski-dhcp-eap-analysis-00

Richard Pruss wrote:
> As I said to Ralph earlier we track transport and port associations=20
> already to facilitate unnumbered interfaces, so the question was what=20
> state beyond that.
Beyond that each EAP conversation needs to be mapped to a distinct=20
transport and port association, which will require a state maintained by

DHCP relay.

Yoshihiro Ohba

>
> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>
>>
>> In general, a state on the logical connection between the peer and=20
>> authenticator needs to be maintained by any EAP lower-layer for each=20
>> EAP conversation. Such a state at least includes transport addresses=20
>> and/or port numbers and they are not carried in EAP message.
>>
>> Yoshihiro Ohba
>>
>>
>> Richard Pruss wrote:
>>>
>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>
>>>> Richard Pruss wrote:
>>>>>
>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>> Richard Pruss wrote:
>>>>>>> Well Ralph,  as you say something else is holding the state and=20
>>>>>>> the relay agent is simply handing the EAP messages to the AAA =20
>>>>>>> service in the relay function... so no the question still makes=20
>>>>>>> no sense to me.
>>>>>> This is an incorrect statement. DHCP relay acting EAP=20
>>>>>> authenticator is not simply handing EAP messages to the AAA, it=20
>>>>>> needs to maintain a state including a retransmission timer to=20
>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>
>>>>> No mate this is the part you probably missed, EAP is doing that=20
>>>>> and it is a separate function regardless of what it is being=20
>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>
>>>> All EAP transport protocols that I know of, including the ones you=20
>>>> listed above requires to maintain a state to carry EAP message. =20
>>>> There is no exception.
>>> What state?
>>>
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>
>>>>>
>>>>> - Ric
>>>>>
>>>>>
>>>>>>
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The thing that makes no sense is the assertion that the relay=20
>>>>>>> agent suddenly needs to hold state, beyond what it already does=20
>>>>>>> to handle ip unnumbered interfaces,
>>>>>>> Ric
>>>>>>>
>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>
>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>
>>>>>>>> I would consider enforcing the address assignment as a separate

>>>>>>>> function of the box that happens to house the DHCP relay agent=20
>>>>>>>> function.  That is, the relay agent extracts the assigned=20
>>>>>>>> address from the DHCPACK and hands it to the address=20
>>>>>>>> enforcement function.  Therefore, the relay agent function is=20
>>>>>>>> not keeping any state.  The address enforcement function could=20
>>>>>>>> just as easily get that address assignment information from=20
>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>
>>>>>>>> The original purpose of the relay agent option was to hold=20
>>>>>>>> state for the relay agent.  We've tried to maintain that=20
>>>>>>>> stateless operation (but I'm not sure we've strictly enforced=20
>>>>>>>> the rule) with the definition of subsequent relay agent
options.
>>>>>>>>
>>>>>>>> - Ralph
>>>>>>>>
>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>
>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>> Relay's in the broadband architecture have to be stateful to

>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to=20
>>>>>>>>>>> the existing architecture.
>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is=20
>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the=20
>>>>>>>>>> state is maintained outside the context of DHCP, which I=20
>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be=20
>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>> >From DHCP point of view, it seems to be a major design
change=20
>>>>>>>>>> to DHCP.
>>>>>>>>>
>>>>>>>>> Do you actually have an implementation of broadband DHCP relay

>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>
>>>>>>>>> - Ric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> - Ric
>>>>>>>>>>>
>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I have read both documents. Thanks for the authors for both

>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>
>>>>>>>>>>>> However, I still have an issue with carrying EAP over DHCP.

>>>>>>>>>>>> The issue is basically a conflict between statefullness of=20
>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>
>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain=20
>>>>>>>>>>>> a state. On the other hand, EAP requires peer and=20
>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When DHCP

>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent=20
>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this is=20
>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an=20
>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me if

>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> dhcwg mailing list
>>>>>>>>> dhcwg@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
>

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

From yoshihiro.ohba@toshiba.co.jp  Mon Jul 27 17:27:29 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2BF13A6BCC for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 17:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmGanL594D6q for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 17:27:28 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 756B43A6A7B for <dhcwg@ietf.org>; Mon, 27 Jul 2009 17:27:28 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6S0RLIc028828; Tue, 28 Jul 2009 09:27:21 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6S0RLGB024260; Tue, 28 Jul 2009 09:27:21 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id KAA24259; Tue, 28 Jul 2009 09:27:21 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6S0RLKr001397; Tue, 28 Jul 2009 09:27:21 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6S0RFEI002165; Tue, 28 Jul 2009 09:27:17 +0900 (JST)
Received: from [133.196.16.69] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNG000SBULGNF30@mail.po.toshiba.co.jp>; Tue, 28 Jul 2009 09:27:16 +0900 (JST)
Date: Mon, 27 Jul 2009 20:27:08 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com>
To: MILES DAVID <David.Miles@alcatel-lucent.com.au>
Message-id: <4A6E45DC.5030103@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 00:27:29 -0000

MILES DAVID wrote:
> I wish to ask a question for clarification.
>
> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
> client was in fact also the EAP supplicant. There is no EAPoL or 802.1x
> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
> conversion.
>
>   
DHCP relay is running EAP acting as an EAP authenticator.
> While the EAP/DHCP client on Home Gateway and Server will need to be
> aware/stateful with respect to EAP why would this extend to a DHCP
> relay? Is this not similar to the case of EAP-Message over RADIUS? A
> RADIUS proxy does not need to be aware of the details of the EAP-Message
> nor be able to decode them.
>   
The difference from RADIUS proxy is that the RADIUS proxy is not running 
EAP.
> In the proposed DHCP message exchange of DISCOVER, DHCPEAP, DHCPOFFER,
> ACK I see no requirement for a stateful DHCP relay to support DHCPEAP.
>   
Why? As I commented above, DHCP relay is running EAP acting as an EAP 
authenticator, which will require lower-layer (in this case DHCP relay) 
to maintain a state.
> As with other DHCP relayed messages there is sufficient information in
> the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
> received from the DHCP server to forward this message to the Home
> Gateway (operating as DHCP client and EAP supplicant).
>   
In Figure 3 of draft-pruss, DHCPEAP message does not come from or go to 
the DHCP server.
The DHCP relay in draft-pruss is not relaying DHCPEAP message between 
DHCP client and DHCP server.

Yoshihiro Ohba

> d
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Yoshihiro Ohba
> Sent: Tuesday, July 28, 2009 1:00 AM
> To: Richard Pruss
> Cc: dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
> Richard Pruss wrote:
>   
>> As I said to Ralph earlier we track transport and port associations 
>> already to facilitate unnumbered interfaces, so the question was what 
>> state beyond that.
>>     
> Beyond that each EAP conversation needs to be mapped to a distinct 
> transport and port association, which will require a state maintained by
>
> DHCP relay.
>
> Yoshihiro Ohba
>
>   
>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>
>>     
>>> In general, a state on the logical connection between the peer and 
>>> authenticator needs to be maintained by any EAP lower-layer for each 
>>> EAP conversation. Such a state at least includes transport addresses 
>>> and/or port numbers and they are not carried in EAP message.
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>> Richard Pruss wrote:
>>>       
>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>
>>>>         
>>>>> Richard Pruss wrote:
>>>>>           
>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>             
>>>>>>> Richard Pruss wrote:
>>>>>>>               
>>>>>>>> Well Ralph,  as you say something else is holding the state and 
>>>>>>>> the relay agent is simply handing the EAP messages to the AAA  
>>>>>>>> service in the relay function... so no the question still makes 
>>>>>>>> no sense to me.
>>>>>>>>                 
>>>>>>> This is an incorrect statement. DHCP relay acting EAP 
>>>>>>> authenticator is not simply handing EAP messages to the AAA, it 
>>>>>>> needs to maintain a state including a retransmission timer to 
>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>               
>>>>>> No mate this is the part you probably missed, EAP is doing that 
>>>>>> and it is a separate function regardless of what it is being 
>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>             
>>>>> All EAP transport protocols that I know of, including the ones you 
>>>>> listed above requires to maintain a state to carry EAP message.  
>>>>> There is no exception.
>>>>>           
>>>> What state?
>>>>
>>>>         
>>>>> Yoshihiro Ohba
>>>>>
>>>>>
>>>>>           
>>>>>> - Ric
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>               
>>>>>>>> The thing that makes no sense is the assertion that the relay 
>>>>>>>> agent suddenly needs to hold state, beyond what it already does 
>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>> Ric
>>>>>>>>
>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>
>>>>>>>>> I would consider enforcing the address assignment as a separate
>>>>>>>>>                   
>
>   
>>>>>>>>> function of the box that happens to house the DHCP relay agent 
>>>>>>>>> function.  That is, the relay agent extracts the assigned 
>>>>>>>>> address from the DHCPACK and hands it to the address 
>>>>>>>>> enforcement function.  Therefore, the relay agent function is 
>>>>>>>>> not keeping any state.  The address enforcement function could 
>>>>>>>>> just as easily get that address assignment information from 
>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>
>>>>>>>>> The original purpose of the relay agent option was to hold 
>>>>>>>>> state for the relay agent.  We've tried to maintain that 
>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced 
>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>                   
> options.
>   
>>>>>>>>> - Ralph
>>>>>>>>>
>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>                       
>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful to
>>>>>>>>>>>>                         
>
>   
>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to 
>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>                         
>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is 
>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the 
>>>>>>>>>>> state is maintained outside the context of DHCP, which I 
>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be 
>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>> >From DHCP point of view, it seems to be a major design
>>>>>>>>>>>                       
> change 
>   
>>>>>>>>>>> to DHCP.
>>>>>>>>>>>                       
>>>>>>>>>> Do you actually have an implementation of broadband DHCP relay
>>>>>>>>>>                     
>
>   
>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>
>>>>>>>>>> - Ric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>>>> Regards,
>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>>>> - Ric
>>>>>>>>>>>>
>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>                         
>>>>>>>>>>>>> I have read both documents. Thanks for the authors for both
>>>>>>>>>>>>>                           
>
>   
>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, I still have an issue with carrying EAP over DHCP.
>>>>>>>>>>>>>                           
>
>   
>>>>>>>>>>>>> The issue is basically a conflict between statefullness of 
>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain 
>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and 
>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When DHCP
>>>>>>>>>>>>>                           
>
>   
>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent 
>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this is 
>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an 
>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me if
>>>>>>>>>>>>>                           
>
>   
>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>                           
>>>>>>>>>>>>
>>>>>>>>>>>>                         
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dhcwg mailing list
>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>                     
>>>>>>>>
>>>>>>>>                 
>>>>>>
>>>>>>             
>>>>
>>>>         
>>>       
>>
>>     
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>   


From David.Miles@alcatel-lucent.com.au  Mon Jul 27 18:17:11 2009
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D4CA3A693E for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Qg6Mj9E0tY5 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:17:09 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id A8BC53A6AED for <dhcwg@ietf.org>; Mon, 27 Jul 2009 18:17:09 -0700 (PDT)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n6S1H8nZ023663; Mon, 27 Jul 2009 20:17:08 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id n6S1H5In014818; Mon, 27 Jul 2009 20:17:06 -0500 (CDT)
Received: from sgsinsbhs01.ad4.ad.alcatel.com (sgsinsbhs01.ap.lucent.com [135.254.109.34]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n6S1BPDg008485; Tue, 28 Jul 2009 09:11:26 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 28 Jul 2009 09:17:01 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Jul 2009 09:17:00 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <4A6E45DC.5030103@toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoPGjBysk75Z6svTHqF5WZkADPOqwAAuNgA
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp>
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: "Yoshihiro Ohba" <yoshihiro.ohba@toshiba.co.jp>
X-OriginalArrivalTime: 28 Jul 2009 01:17:01.0255 (UTC) FILETIME=[1C0ECD70:01CA0F21]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 01:17:11 -0000

I had not realized you were referring to Figure 3 - I was referring to a
DHCP relay that may be between the NAS and the client such as those
described as L2 DHCP relays and present in an access node/DSLAM, etc. I
apologies for creating any further confusion there.

If there were a bootp relay or l2 DHCP relay between the NAS and HGW in
figure 2 - it would not need to be stateful. Also, if the NAS were not
forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it would not
need to have new state tables for DHCPEAP.

Figure 3 describes something that is not well-described as a DHCP relay
IMO (which may be your point as well). I would agree that there is state
in this device by its nature and that having a forked EAP and it is a
EAP authenticator.=20

I am interested in the example of figure 2 and less interested in the
deployment model of figure 3. Could it be an option to remove the
split/forked EAP/RADIUS deployment model (which seems to be causing
concern) and look at the model in figure 2?

Thanks

-David

-----Original Message-----
From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]=20
Sent: Tuesday, July 28, 2009 9:57 AM
To: MILES DAVID
Cc: Richard Pruss; dhc WG; Ralph Droms
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
draft-brzozowski-dhcp-eap-analysis-00

MILES DAVID wrote:
> I wish to ask a question for clarification.
>
> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
> client was in fact also the EAP supplicant. There is no EAPoL or
802.1x
> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
> conversion.
>
>  =20
DHCP relay is running EAP acting as an EAP authenticator.
> While the EAP/DHCP client on Home Gateway and Server will need to be
> aware/stateful with respect to EAP why would this extend to a DHCP
> relay? Is this not similar to the case of EAP-Message over RADIUS? A
> RADIUS proxy does not need to be aware of the details of the
EAP-Message
> nor be able to decode them.
>  =20
The difference from RADIUS proxy is that the RADIUS proxy is not running

EAP.
> In the proposed DHCP message exchange of DISCOVER, DHCPEAP, DHCPOFFER,
> ACK I see no requirement for a stateful DHCP relay to support DHCPEAP.
>  =20
Why? As I commented above, DHCP relay is running EAP acting as an EAP=20
authenticator, which will require lower-layer (in this case DHCP relay)=20
to maintain a state.
> As with other DHCP relayed messages there is sufficient information in
> the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
> received from the DHCP server to forward this message to the Home
> Gateway (operating as DHCP client and EAP supplicant).
>  =20
In Figure 3 of draft-pruss, DHCPEAP message does not come from or go to=20
the DHCP server.
The DHCP relay in draft-pruss is not relaying DHCPEAP message between=20
DHCP client and DHCP server.

Yoshihiro Ohba

> d
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Yoshihiro Ohba
> Sent: Tuesday, July 28, 2009 1:00 AM
> To: Richard Pruss
> Cc: dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
> Richard Pruss wrote:
>  =20
>> As I said to Ralph earlier we track transport and port associations=20
>> already to facilitate unnumbered interfaces, so the question was what

>> state beyond that.
>>    =20
> Beyond that each EAP conversation needs to be mapped to a distinct=20
> transport and port association, which will require a state maintained
by
>
> DHCP relay.
>
> Yoshihiro Ohba
>
>  =20
>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>
>>    =20
>>> In general, a state on the logical connection between the peer and=20
>>> authenticator needs to be maintained by any EAP lower-layer for each

>>> EAP conversation. Such a state at least includes transport addresses

>>> and/or port numbers and they are not carried in EAP message.
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>> Richard Pruss wrote:
>>>      =20
>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>
>>>>        =20
>>>>> Richard Pruss wrote:
>>>>>          =20
>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>            =20
>>>>>>> Richard Pruss wrote:
>>>>>>>              =20
>>>>>>>> Well Ralph,  as you say something else is holding the state and

>>>>>>>> the relay agent is simply handing the EAP messages to the AAA =20
>>>>>>>> service in the relay function... so no the question still makes

>>>>>>>> no sense to me.
>>>>>>>>                =20
>>>>>>> This is an incorrect statement. DHCP relay acting EAP=20
>>>>>>> authenticator is not simply handing EAP messages to the AAA, it=20
>>>>>>> needs to maintain a state including a retransmission timer to=20
>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>              =20
>>>>>> No mate this is the part you probably missed, EAP is doing that=20
>>>>>> and it is a separate function regardless of what it is being=20
>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>            =20
>>>>> All EAP transport protocols that I know of, including the ones you

>>>>> listed above requires to maintain a state to carry EAP message. =20
>>>>> There is no exception.
>>>>>          =20
>>>> What state?
>>>>
>>>>        =20
>>>>> Yoshihiro Ohba
>>>>>
>>>>>
>>>>>          =20
>>>>>> - Ric
>>>>>>
>>>>>>
>>>>>>            =20
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>              =20
>>>>>>>> The thing that makes no sense is the assertion that the relay=20
>>>>>>>> agent suddenly needs to hold state, beyond what it already does

>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>> Ric
>>>>>>>>
>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>
>>>>>>>>                =20
>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>
>>>>>>>>> I would consider enforcing the address assignment as a
separate
>>>>>>>>>                  =20
>
>  =20
>>>>>>>>> function of the box that happens to house the DHCP relay agent

>>>>>>>>> function.  That is, the relay agent extracts the assigned=20
>>>>>>>>> address from the DHCPACK and hands it to the address=20
>>>>>>>>> enforcement function.  Therefore, the relay agent function is=20
>>>>>>>>> not keeping any state.  The address enforcement function could

>>>>>>>>> just as easily get that address assignment information from=20
>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>
>>>>>>>>> The original purpose of the relay agent option was to hold=20
>>>>>>>>> state for the relay agent.  We've tried to maintain that=20
>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced=20
>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>                  =20
> options.
>  =20
>>>>>>>>> - Ralph
>>>>>>>>>
>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>
>>>>>>>>>                  =20
>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>
>>>>>>>>>>                    =20
>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>                      =20
>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
to
>>>>>>>>>>>>                        =20
>
>  =20
>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to=20
>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>                        =20
>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is

>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the=20
>>>>>>>>>>> state is maintained outside the context of DHCP, which I=20
>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be=20
>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>> >From DHCP point of view, it seems to be a major design
>>>>>>>>>>>                      =20
> change=20
>  =20
>>>>>>>>>>> to DHCP.
>>>>>>>>>>>                      =20
>>>>>>>>>> Do you actually have an implementation of broadband DHCP
relay
>>>>>>>>>>                    =20
>
>  =20
>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>
>>>>>>>>>> - Ric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                    =20
>>>>>>>>>>> Regards,
>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>
>>>>>>>>>>>                      =20
>>>>>>>>>>>> - Ric
>>>>>>>>>>>>
>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>                        =20
>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
both
>>>>>>>>>>>>>                          =20
>
>  =20
>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
DHCP.
>>>>>>>>>>>>>                          =20
>
>  =20
>>>>>>>>>>>>> The issue is basically a conflict between statefullness of

>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain

>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and=20
>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
DHCP
>>>>>>>>>>>>>                          =20
>
>  =20
>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent=20
>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this is

>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an=20
>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
if
>>>>>>>>>>>>>                          =20
>
>  =20
>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>
>>>>>>>>>>>>                        =20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dhcwg mailing list
>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>                    =20
>>>>>>>>
>>>>>>>>                =20
>>>>>>
>>>>>>            =20
>>>>
>>>>        =20
>>>      =20
>>
>>    =20
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>  =20


From ric@cisco.com  Mon Jul 27 18:25:00 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A11AD3A696E for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.028
X-Spam-Level: 
X-Spam-Status: No, score=-4.028 tagged_above=-999 required=5 tests=[AWL=-1.429, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVdrYm2WzQoR for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:24:59 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 550713A68B9 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 18:24:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAIfwbUoKS+eh/2dsb2JhbAC5d4gojwgFhAyBTWI
X-IronPort-AV: E=Sophos;i="4.43,279,1246838400"; d="scan'208";a="55825216"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-2.cisco.com with ESMTP; 28 Jul 2009 01:24:54 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6S1OroF023722;  Tue, 28 Jul 2009 09:24:53 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6S1OjdN023548; Tue, 28 Jul 2009 01:24:53 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 09:24:23 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 09:24:10 +0800
Message-Id: <F554A392-3545-4755-80B1-BB4D34808C2D@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: MILES DAVID <David.Miles@alcatel-lucent.com.au>
In-Reply-To: <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 11:23:43 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 01:24:16.0035 (UTC) FILETIME=[1F34F730:01CA0F22]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=10579; t=1248744293; x=1249608293; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=d8NXoD9DY8uFTvhBNiD+gGREaM8ZBtDy1ttBm4+aZgY=; b=Avz0VEyEfxOh7O0SgR2fVzt1I/Dc2LVQ1nBvvUClFhPBWYkpFemYK706od b/427ueacw/ia+peVahDGViJbE18kaoB45rij9lkZBKXtWlest3bQByzknJA 1wfdgn3d/sGPCSE4YOeZer7bf/gtKgj5QDbwWq1C9H2+XujRnam1s=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 01:25:00 -0000

I agree with you David, most of the vendors have called that a proxy  
function in our documentation
and it well pre-dates the Auth proposal, I think it originally evolved  
to provide DHCP with a addresses
and other details from AAA.

- Ric

On 28/07/2009, at 11:17 AM, MILES DAVID wrote:

> I had not realized you were referring to Figure 3 - I was referring  
> to a
> DHCP relay that may be between the NAS and the client such as those
> described as L2 DHCP relays and present in an access node/DSLAM,  
> etc. I
> apologies for creating any further confusion there.
>
> If there were a bootp relay or l2 DHCP relay between the NAS and HGW  
> in
> figure 2 - it would not need to be stateful. Also, if the NAS were not
> forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it would  
> not
> need to have new state tables for DHCPEAP.
>
> Figure 3 describes something that is not well-described as a DHCP  
> relay
> IMO (which may be your point as well). I would agree that there is  
> state
> in this device by its nature and that having a forked EAP and it is a
> EAP authenticator.
>
> I am interested in the example of figure 2 and less interested in the
> deployment model of figure 3. Could it be an option to remove the
> split/forked EAP/RADIUS deployment model (which seems to be causing
> concern) and look at the model in figure 2?
>
> Thanks
>
> -David
>
> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
> Sent: Tuesday, July 28, 2009 9:57 AM
> To: MILES DAVID
> Cc: Richard Pruss; dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
> MILES DAVID wrote:
>> I wish to ask a question for clarification.
>>
>> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
>> client was in fact also the EAP supplicant. There is no EAPoL or
> 802.1x
>> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
>> conversion.
>>
>>
> DHCP relay is running EAP acting as an EAP authenticator.
>> While the EAP/DHCP client on Home Gateway and Server will need to be
>> aware/stateful with respect to EAP why would this extend to a DHCP
>> relay? Is this not similar to the case of EAP-Message over RADIUS? A
>> RADIUS proxy does not need to be aware of the details of the
> EAP-Message
>> nor be able to decode them.
>>
> The difference from RADIUS proxy is that the RADIUS proxy is not  
> running
>
> EAP.
>> In the proposed DHCP message exchange of DISCOVER, DHCPEAP,  
>> DHCPOFFER,
>> ACK I see no requirement for a stateful DHCP relay to support  
>> DHCPEAP.
>>
> Why? As I commented above, DHCP relay is running EAP acting as an EAP
> authenticator, which will require lower-layer (in this case DHCP  
> relay)
> to maintain a state.
>> As with other DHCP relayed messages there is sufficient information  
>> in
>> the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
>> received from the DHCP server to forward this message to the Home
>> Gateway (operating as DHCP client and EAP supplicant).
>>
> In Figure 3 of draft-pruss, DHCPEAP message does not come from or go  
> to
> the DHCP server.
> The DHCP relay in draft-pruss is not relaying DHCPEAP message between
> DHCP client and DHCP server.
>
> Yoshihiro Ohba
>
>> d
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On  
>> Behalf
>> Of Yoshihiro Ohba
>> Sent: Tuesday, July 28, 2009 1:00 AM
>> To: Richard Pruss
>> Cc: dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> Richard Pruss wrote:
>>
>>> As I said to Ralph earlier we track transport and port associations
>>> already to facilitate unnumbered interfaces, so the question was  
>>> what
>
>>> state beyond that.
>>>
>> Beyond that each EAP conversation needs to be mapped to a distinct
>> transport and port association, which will require a state maintained
> by
>>
>> DHCP relay.
>>
>> Yoshihiro Ohba
>>
>>
>>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>>
>>>
>>>> In general, a state on the logical connection between the peer and
>>>> authenticator needs to be maintained by any EAP lower-layer for  
>>>> each
>
>>>> EAP conversation. Such a state at least includes transport  
>>>> addresses
>
>>>> and/or port numbers and they are not carried in EAP message.
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>
>>>> Richard Pruss wrote:
>>>>
>>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>
>>>>>> Richard Pruss wrote:
>>>>>>
>>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Richard Pruss wrote:
>>>>>>>>
>>>>>>>>> Well Ralph,  as you say something else is holding the state  
>>>>>>>>> and
>
>>>>>>>>> the relay agent is simply handing the EAP messages to the AAA
>>>>>>>>> service in the relay function... so no the question still  
>>>>>>>>> makes
>
>>>>>>>>> no sense to me.
>>>>>>>>>
>>>>>>>> This is an incorrect statement. DHCP relay acting EAP
>>>>>>>> authenticator is not simply handing EAP messages to the AAA, it
>>>>>>>> needs to maintain a state including a retransmission timer to
>>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>>
>>>>>>> No mate this is the part you probably missed, EAP is doing that
>>>>>>> and it is a separate function regardless of what it is being
>>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>>
>>>>>> All EAP transport protocols that I know of, including the ones  
>>>>>> you
>
>>>>>> listed above requires to maintain a state to carry EAP message.
>>>>>> There is no exception.
>>>>>>
>>>>> What state?
>>>>>
>>>>>
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>
>>>>>>
>>>>>>> - Ric
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Yoshihiro Ohba
>>>>>>>>
>>>>>>>>
>>>>>>>>> The thing that makes no sense is the assertion that the relay
>>>>>>>>> agent suddenly needs to hold state, beyond what it already  
>>>>>>>>> does
>
>>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>>> Ric
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>>
>>>>>>>>>> I would consider enforcing the address assignment as a
> separate
>>>>>>>>>>
>>
>>
>>>>>>>>>> function of the box that happens to house the DHCP relay  
>>>>>>>>>> agent
>
>>>>>>>>>> function.  That is, the relay agent extracts the assigned
>>>>>>>>>> address from the DHCPACK and hands it to the address
>>>>>>>>>> enforcement function.  Therefore, the relay agent function is
>>>>>>>>>> not keeping any state.  The address enforcement function  
>>>>>>>>>> could
>
>>>>>>>>>> just as easily get that address assignment information from
>>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>>
>>>>>>>>>> The original purpose of the relay agent option was to hold
>>>>>>>>>> state for the relay agent.  We've tried to maintain that
>>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced
>>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>>
>> options.
>>
>>>>>>>>>> - Ralph
>>>>>>>>>>
>>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
> to
>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to
>>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>>
>>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment  
>>>>>>>>>>>> is
>
>>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the
>>>>>>>>>>>> state is maintained outside the context of DHCP, which I
>>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be
>>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>>>> From DHCP point of view, it seems to be a major design
>>>>>>>>>>>>
>> change
>>
>>>>>>>>>>>> to DHCP.
>>>>>>>>>>>>
>>>>>>>>>>> Do you actually have an implementation of broadband DHCP
> relay
>>>>>>>>>>>
>>
>>
>>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>>
>>>>>>>>>>> - Ric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> - Ric
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
> both
>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
> DHCP.
>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>> The issue is basically a conflict between statefullness  
>>>>>>>>>>>>>> of
>
>>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not  
>>>>>>>>>>>>>> maintain
>
>>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and
>>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
> DHCP
>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent
>>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this  
>>>>>>>>>>>>>> is
>
>>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an
>>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
> if
>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>>
>>
>


From ric@cisco.com  Mon Jul 27 18:32:49 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42EF33A68D9 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ao38w5Zbuet0 for <dhcwg@core3.amsl.com>; Mon, 27 Jul 2009 18:32:48 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 61CD03A68B9 for <dhcwg@ietf.org>; Mon, 27 Jul 2009 18:32:47 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALLxbUoKS+eh/2dsb2JhbAC6AYgojwgFhAw
X-IronPort-AV: E=Sophos;i="4.43,279,1246838400"; d="scan'208";a="55825492"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-2.cisco.com with ESMTP; 28 Jul 2009 01:32:46 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6S1Wj9C024809;  Tue, 28 Jul 2009 09:32:45 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6S1Wjls024765; Tue, 28 Jul 2009 01:32:45 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 09:32:43 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 09:32:32 +0800
Message-Id: <27FE055C-748B-4598-BDE3-518998C435A2@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <015e01ca0ecb$4fdacdd0$ef906970$@yegin@yegin.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 11:32:05 +1000
References: <4A6CD501.7030704@toshiba.co.jp>	<C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>	<4A6D4F53.2060608@toshiba.co.jp>	<270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>	<8BABA261-DE48-4684-85C8-419591061672@cisco.com>	<9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>	<4A6D5C54.6050904@toshiba.co.jp>	<CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>	<4A6D5E5D.8070707@toshiba.co.jp>	<7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>	<4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <015e01ca0ecb$4fdacdd0$ef906970$@yegin@yegin.org>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 01:32:35.0311 (UTC) FILETIME=[48CC6FF0:01CA0F23]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=7572; t=1248744765; x=1249608765; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=09draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=NPO7q+AlTO5rV75jUGcjcSykgISoXgxeaKTzS5n+4u4=; b=TddwjeZxJjMdIypZoAedjK48g0YWpsu1eMIyOLpgYhxJ+9gtxKuQvmXCAz t0oghYqmoes+UPJbLw5ceT5yY8LYNm9WHQquSXWWOosjJ5el7K0PZQuWgBCz fxJ9n8vlUlQy+bQavrSq5AYyag3dXpozuwhdj8rRB4UkE1GDDq13o=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: 'dhc WG' <dhcwg@ietf.org>, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 01:32:49 -0000

Yes, well as we have so often discussed, it is far simpler to add map  
our existing state in the broadband DHCP on the NAS
to EAP then other proposals and yes over time we would want expand to  
key management to facilitate, policy
control that scales to the millions at the broadband edge.

- Ric

On 28/07/2009, at 1:02 AM, Alper Yegin wrote:

> Your DHCP relay, now that it wants to be an EAP lower-layer, has to  
> keep
> track of the EAP sessions. For each EAP session, it has to know the
> associated DHCP session and AAA (RADIUS, Diameter) session. If you  
> wonder
> why so, think of how would the DHCP relay know which host to  
> transmit the
> EAP request to when it receives an EAP request from AAA client
> implementation? The same "mapping" issue arises for the EAP  
> responses that
> are bridged from the EAP peer side to the authentication server side  
> by the
> DHCP relay implementation.
>
> Aside from having to deal with "handles" needed for demultiplexing,  
> sooner
> or later key derivation will be needed by the BBF (e.g., for  
> securing DHCP,
> L2, etc.) and MSK will also be stored by the EAP lower-layer --  
> namely your
> DHCP relay.
>
> Alper
>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On  
>> Behalf
>> Of Richard Pruss
>> Sent: Monday, July 27, 2009 12:27 PM
>> To: Yoshihiro Ohba
>> Cc: dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> As I said to Ralph earlier we track transport and port associations
>> already to facilitate unnumbered interfaces, so the question was what
>> state beyond that.
>>
>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>
>>>
>>> In general, a state on the logical connection between the peer and
>>> authenticator needs to be maintained by any EAP lower-layer for each
>>> EAP conversation. Such a state at least includes transport addresses
>>> and/or port numbers and they are not carried in EAP message.
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>> Richard Pruss wrote:
>>>>
>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>
>>>>> Richard Pruss wrote:
>>>>>>
>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>> Richard Pruss wrote:
>>>>>>>> Well Ralph,  as you say something else is holding the state and
>>>>>>>> the relay agent is simply handing the EAP messages to the AAA
>>>>>>>> service in the relay function... so no the question still makes
>>>>>>>> no sense to me.
>>>>>>> This is an incorrect statement. DHCP relay acting EAP
>>>>>>> authenticator is not simply handing EAP messages to the AAA, it
>>>>>>> needs to maintain a state including a retransmission timer to
>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>
>>>>>> No mate this is the part you probably missed, EAP is doing that
>>>>>> and it is a separate function regardless of what it is being
>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>
>>>>> All EAP transport protocols that I know of, including the ones you
>>>>> listed above requires to maintain a state to carry EAP message.
>>>>> There is no exception.
>>>> What state?
>>>>
>>>>>
>>>>> Yoshihiro Ohba
>>>>>
>>>>>
>>>>>>
>>>>>> - Ric
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The thing that makes no sense is the assertion that the relay
>>>>>>>> agent suddenly needs to hold state, beyond what it already does
>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>> Ric
>>>>>>>>
>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>
>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>
>>>>>>>>> I would consider enforcing the address assignment as a
>>>>>>>>> separate function of the box that happens to house the DHCP
>>>>>>>>> relay agent function.  That is, the relay agent extracts the
>>>>>>>>> assigned address from the DHCPACK and hands it to the address
>>>>>>>>> enforcement function.  Therefore, the relay agent function is
>>>>>>>>> not keeping any state.  The address enforcement function could
>>>>>>>>> just as easily get that address assignment information from
>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>
>>>>>>>>> The original purpose of the relay agent option was to hold
>>>>>>>>> state for the relay agent.  We've tried to maintain that
>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced
>>>>>>>>> the rule) with the definition of subsequent relay agent
>> options.
>>>>>>>>>
>>>>>>>>> - Ralph
>>>>>>>>>
>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>
>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
>>>>>>>>>>>> to enforce DHCP address assignment, so it is not a change
>>>>>>>>>>>> to the existing architecture.
>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is
>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the
>>>>>>>>>>> state is maintained outside the context of DHCP, which I
>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be
>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>>> From DHCP point of view, it seems to be a major design
>>>>>>>>>>> change to DHCP.
>>>>>>>>>>
>>>>>>>>>> Do you actually have an implementation of broadband DHCP
>>>>>>>>>> relay because  what you are talking makes very little sense?
>>>>>>>>>>
>>>>>>>>>> - Ric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> - Ric
>>>>>>>>>>>>
>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
>>>>>>>>>>>>> both documents providing techinical details.
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
>>>>>>>>>>>>> DHCP. The issue is basically a conflict between
>>>>>>>>>>>>> statefullness of EAP and statelessness of DHCP relay  
>>>>>>>>>>>>> agent.
>>>>>>>>>>>>>
>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain
>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and
>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
>>>>>>>>>>>>> DHCP relay agent acts EAP authenticator, then the relay
>>>>>>>>>>>>> agent will be no longer a stateless DHCP entity. I think
>>>>>>>>>>>>> this is not discussed in dhcp-eap-analysis draft. Is this
>>>>>>>>>>>>> an acceptable design change for DHCP?  Or please correct
>>>>>>>>>>>>> me if I am wrong.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dhcwg mailing list
>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>


From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 01:38:16 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCF8A3A6DC8 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 01:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UF13oQUMNz1f for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 01:38:15 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 2DA443A6DC7 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 01:38:15 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6S8c767016722; Tue, 28 Jul 2009 17:38:07 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6S8c7PX020914; Tue, 28 Jul 2009 17:38:07 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id TAA20911; Tue, 28 Jul 2009 17:38:07 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6S8c7LP012646; Tue, 28 Jul 2009 17:38:07 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6S8c6dH011211; Tue, 28 Jul 2009 17:38:06 +0900 (JST)
Received: from [133.196.16.69] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNH000JEHBINGM0@mail.po.toshiba.co.jp>; Tue, 28 Jul 2009 17:38:06 +0900 (JST)
Date: Tue, 28 Jul 2009 04:37:58 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>
To: MILES DAVID <David.Miles@alcatel-lucent.com.au>
Message-id: <4A6EB8E6.4070800@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 08:38:16 -0000

David,

I don't think "your interest" in Figure 2 more than Figure 3 is the same 
as Broadband Forum's requirements. In TR-101, there is a requirement 
"The Broadband Network Gateway MUST be able to function as a DHCP Relay 
Agent as described in RFC 951 “BOOTP”, RFC 2131”DHCP” and RFC 3046 “DHCP 
Relay Agent Information Option” on selected untrusted interfaces."

It seems to me that if draft-pruss does not support Figure 3, then it 
does not satisfy Broadband Forum's requirements. Please correct me if my 
observation is wrong.

Yoshihiro Ohba


MILES DAVID wrote:
> I had not realized you were referring to Figure 3 - I was referring to a
> DHCP relay that may be between the NAS and the client such as those
> described as L2 DHCP relays and present in an access node/DSLAM, etc. I
> apologies for creating any further confusion there.
>
> If there were a bootp relay or l2 DHCP relay between the NAS and HGW in
> figure 2 - it would not need to be stateful. Also, if the NAS were not
> forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it would not
> need to have new state tables for DHCPEAP.
>
> Figure 3 describes something that is not well-described as a DHCP relay
> IMO (which may be your point as well). I would agree that there is state
> in this device by its nature and that having a forked EAP and it is a
> EAP authenticator. 
>
> I am interested in the example of figure 2 and less interested in the
> deployment model of figure 3. Could it be an option to remove the
> split/forked EAP/RADIUS deployment model (which seems to be causing
> concern) and look at the model in figure 2?
>
> Thanks
>
> -David
>
> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp] 
> Sent: Tuesday, July 28, 2009 9:57 AM
> To: MILES DAVID
> Cc: Richard Pruss; dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
> MILES DAVID wrote:
>   
>> I wish to ask a question for clarification.
>>
>> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
>> client was in fact also the EAP supplicant. There is no EAPoL or
>>     
> 802.1x
>   
>> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
>> conversion.
>>
>>   
>>     
> DHCP relay is running EAP acting as an EAP authenticator.
>   
>> While the EAP/DHCP client on Home Gateway and Server will need to be
>> aware/stateful with respect to EAP why would this extend to a DHCP
>> relay? Is this not similar to the case of EAP-Message over RADIUS? A
>> RADIUS proxy does not need to be aware of the details of the
>>     
> EAP-Message
>   
>> nor be able to decode them.
>>   
>>     
> The difference from RADIUS proxy is that the RADIUS proxy is not running
>
> EAP.
>   
>> In the proposed DHCP message exchange of DISCOVER, DHCPEAP, DHCPOFFER,
>> ACK I see no requirement for a stateful DHCP relay to support DHCPEAP.
>>   
>>     
> Why? As I commented above, DHCP relay is running EAP acting as an EAP 
> authenticator, which will require lower-layer (in this case DHCP relay) 
> to maintain a state.
>   
>> As with other DHCP relayed messages there is sufficient information in
>> the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
>> received from the DHCP server to forward this message to the Home
>> Gateway (operating as DHCP client and EAP supplicant).
>>   
>>     
> In Figure 3 of draft-pruss, DHCPEAP message does not come from or go to 
> the DHCP server.
> The DHCP relay in draft-pruss is not relaying DHCPEAP message between 
> DHCP client and DHCP server.
>
> Yoshihiro Ohba
>
>   
>> d
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
>> Of Yoshihiro Ohba
>> Sent: Tuesday, July 28, 2009 1:00 AM
>> To: Richard Pruss
>> Cc: dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> Richard Pruss wrote:
>>   
>>     
>>> As I said to Ralph earlier we track transport and port associations 
>>> already to facilitate unnumbered interfaces, so the question was what
>>>       
>
>   
>>> state beyond that.
>>>     
>>>       
>> Beyond that each EAP conversation needs to be mapped to a distinct 
>> transport and port association, which will require a state maintained
>>     
> by
>   
>> DHCP relay.
>>
>> Yoshihiro Ohba
>>
>>   
>>     
>>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>>
>>>     
>>>       
>>>> In general, a state on the logical connection between the peer and 
>>>> authenticator needs to be maintained by any EAP lower-layer for each
>>>>         
>
>   
>>>> EAP conversation. Such a state at least includes transport addresses
>>>>         
>
>   
>>>> and/or port numbers and they are not carried in EAP message.
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>
>>>> Richard Pruss wrote:
>>>>       
>>>>         
>>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>         
>>>>>           
>>>>>> Richard Pruss wrote:
>>>>>>           
>>>>>>             
>>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>>
>>>>>>>             
>>>>>>>               
>>>>>>>> Richard Pruss wrote:
>>>>>>>>               
>>>>>>>>                 
>>>>>>>>> Well Ralph,  as you say something else is holding the state and
>>>>>>>>>                   
>
>   
>>>>>>>>> the relay agent is simply handing the EAP messages to the AAA  
>>>>>>>>> service in the relay function... so no the question still makes
>>>>>>>>>                   
>
>   
>>>>>>>>> no sense to me.
>>>>>>>>>                 
>>>>>>>>>                   
>>>>>>>> This is an incorrect statement. DHCP relay acting EAP 
>>>>>>>> authenticator is not simply handing EAP messages to the AAA, it 
>>>>>>>> needs to maintain a state including a retransmission timer to 
>>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>>               
>>>>>>>>                 
>>>>>>> No mate this is the part you probably missed, EAP is doing that 
>>>>>>> and it is a separate function regardless of what it is being 
>>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>>             
>>>>>>>               
>>>>>> All EAP transport protocols that I know of, including the ones you
>>>>>>             
>
>   
>>>>>> listed above requires to maintain a state to carry EAP message.  
>>>>>> There is no exception.
>>>>>>           
>>>>>>             
>>>>> What state?
>>>>>
>>>>>         
>>>>>           
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>
>>>>>>           
>>>>>>             
>>>>>>> - Ric
>>>>>>>
>>>>>>>
>>>>>>>             
>>>>>>>               
>>>>>>>> Yoshihiro Ohba
>>>>>>>>
>>>>>>>>               
>>>>>>>>                 
>>>>>>>>> The thing that makes no sense is the assertion that the relay 
>>>>>>>>> agent suddenly needs to hold state, beyond what it already does
>>>>>>>>>                   
>
>   
>>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>>> Ric
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>>
>>>>>>>>>                 
>>>>>>>>>                   
>>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>>
>>>>>>>>>> I would consider enforcing the address assignment as a
>>>>>>>>>>                     
> separate
>   
>>>>>>>>>>                   
>>>>>>>>>>                     
>>   
>>     
>>>>>>>>>> function of the box that happens to house the DHCP relay agent
>>>>>>>>>>                     
>
>   
>>>>>>>>>> function.  That is, the relay agent extracts the assigned 
>>>>>>>>>> address from the DHCPACK and hands it to the address 
>>>>>>>>>> enforcement function.  Therefore, the relay agent function is 
>>>>>>>>>> not keeping any state.  The address enforcement function could
>>>>>>>>>>                     
>
>   
>>>>>>>>>> just as easily get that address assignment information from 
>>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>>
>>>>>>>>>> The original purpose of the relay agent option was to hold 
>>>>>>>>>> state for the relay agent.  We've tried to maintain that 
>>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced 
>>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>>                   
>>>>>>>>>>                     
>> options.
>>   
>>     
>>>>>>>>>> - Ralph
>>>>>>>>>>
>>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>>
>>>>>>>>>>                   
>>>>>>>>>>                     
>>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>>
>>>>>>>>>>>                     
>>>>>>>>>>>                       
>>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>>                       
>>>>>>>>>>>>                         
>>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
>>>>>>>>>>>>>                           
> to
>   
>>>>>>>>>>>>>                         
>>>>>>>>>>>>>                           
>>   
>>     
>>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to 
>>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>>                         
>>>>>>>>>>>>>                           
>>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment is
>>>>>>>>>>>>                         
>
>   
>>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the 
>>>>>>>>>>>> state is maintained outside the context of DHCP, which I 
>>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be 
>>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>>> >From DHCP point of view, it seems to be a major design
>>>>>>>>>>>>                       
>>>>>>>>>>>>                         
>> change 
>>   
>>     
>>>>>>>>>>>> to DHCP.
>>>>>>>>>>>>                       
>>>>>>>>>>>>                         
>>>>>>>>>>> Do you actually have an implementation of broadband DHCP
>>>>>>>>>>>                       
> relay
>   
>>>>>>>>>>>                     
>>>>>>>>>>>                       
>>   
>>     
>>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>>
>>>>>>>>>>> - Ric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                     
>>>>>>>>>>>                       
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>
>>>>>>>>>>>>                       
>>>>>>>>>>>>                         
>>>>>>>>>>>>> - Ric
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>                         
>>>>>>>>>>>>>                           
>>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
>>>>>>>>>>>>>>                             
> both
>   
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>>>                             
>>   
>>     
>>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
>>>>>>>>>>>>>>                             
> DHCP.
>   
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>>>                             
>>   
>>     
>>>>>>>>>>>>>> The issue is basically a conflict between statefullness of
>>>>>>>>>>>>>>                             
>
>   
>>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not maintain
>>>>>>>>>>>>>>                             
>
>   
>>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and 
>>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
>>>>>>>>>>>>>>                             
> DHCP
>   
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>>>                             
>>   
>>     
>>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent 
>>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this is
>>>>>>>>>>>>>>                             
>
>   
>>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an 
>>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
>>>>>>>>>>>>>>                             
> if
>   
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>>>                             
>>   
>>     
>>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>                         
>>>>>>>>>>>>>                           
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>                     
>>>>>>>>>>>                       
>>>>>>>>>                 
>>>>>>>>>                   
>>>>>>>             
>>>>>>>               
>>>>>         
>>>>>           
>>>>       
>>>>         
>>>     
>>>       
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>>
>>   
>>     
>
>
>
>   


From ric@cisco.com  Tue Jul 28 03:10:22 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E8D43A6886 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 03:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.71
X-Spam-Level: 
X-Spam-Status: No, score=-5.71 tagged_above=-999 required=5 tests=[AWL=0.889,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0AuOVCi9RQi for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 03:10:20 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id A839E3A69D5 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 03:10:19 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEABxrbkoKS+ej/2dsb2JhbAC6O4gnj0AFhAyBTQ
X-IronPort-AV: E=Sophos;i="4.43,282,1246838400"; d="scan'208";a="58614044"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-1.cisco.com with ESMTP; 28 Jul 2009 10:10:18 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6SAAHNg002900;  Tue, 28 Jul 2009 18:10:17 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6SAAHoA013713; Tue, 28 Jul 2009 10:10:17 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 18:10:16 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 18:10:15 +0800
Message-Id: <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6EB8E6.4070800@toshiba.co.jp>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 28 Jul 2009 20:10:12 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 10:10:15.0656 (UTC) FILETIME=[9A34F680:01CA0F6B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12130; t=1248775817; x=1249639817; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=TSFfHb+AVBLV3YJef8hDQdusnh4Jy6TDtWgSqh3cJ3g=; b=ewl8xCssTQXaa+Iophpg4MGF9AU19e2dzi3PRIcXQnzIbHYaFA1mM/VgEY nLXkUewUbc2cojb/EvAFJoe2YOH7DEn7RjAiq0cIuHvTPvbnlI5wb3lp+Oxr 3FHLXc9VRJZh6/jsvF/ouJOYu1Z4gdnFLeocFcpD0G7phbxwmsDjo=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, MILES DAVID <David.Miles@alcatel-lucent.com.au>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 10:10:22 -0000

Oh, for crying in a bucket.

How on earth do you draw this conclusion?

  Can you PANA folks go back to your cave.  We are not about to adopt =20=

PANA so please stop with the noise and this nonsense.

- Ric

On 28/07/2009, at 6:37 PM, Yoshihiro Ohba wrote:

> David,
>
> I don't think "your interest" in Figure 2 more than Figure 3 is the =20=

> same as Broadband Forum's requirements. In TR-101, there is a =20
> requirement "The Broadband Network Gateway MUST be able to function =20=

> as a DHCP Relay Agent as described in RFC 951 =93BOOTP=94, RFC =20
> 2131=94DHCP=94 and RFC 3046 =93DHCP Relay Agent Information Option=94 =
on =20
> selected untrusted interfaces."
>
> It seems to me that if draft-pruss does not support Figure 3, then =20
> it does not satisfy Broadband Forum's requirements. Please correct =20
> me if my observation is wrong.
>
> Yoshihiro Ohba
>
>
> MILES DAVID wrote:
>> I had not realized you were referring to Figure 3 - I was referring =20=

>> to a
>> DHCP relay that may be between the NAS and the client such as those
>> described as L2 DHCP relays and present in an access node/DSLAM, =20
>> etc. I
>> apologies for creating any further confusion there.
>>
>> If there were a bootp relay or l2 DHCP relay between the NAS and =20
>> HGW in
>> figure 2 - it would not need to be stateful. Also, if the NAS were =20=

>> not
>> forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it would =20=

>> not
>> need to have new state tables for DHCPEAP.
>>
>> Figure 3 describes something that is not well-described as a DHCP =20
>> relay
>> IMO (which may be your point as well). I would agree that there is =20=

>> state
>> in this device by its nature and that having a forked EAP and it is a
>> EAP authenticator.
>> I am interested in the example of figure 2 and less interested in the
>> deployment model of figure 3. Could it be an option to remove the
>> split/forked EAP/RADIUS deployment model (which seems to be causing
>> concern) and look at the model in figure 2?
>>
>> Thanks
>>
>> -David
>>
>> -----Original Message-----
>> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp] Sent: =20
>> Tuesday, July 28, 2009 9:57 AM
>> To: MILES DAVID
>> Cc: Richard Pruss; dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> MILES DAVID wrote:
>>
>>> I wish to ask a question for clarification.
>>>
>>> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
>>> client was in fact also the EAP supplicant. There is no EAPoL or
>>>
>> 802.1x
>>
>>> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
>>> conversion.
>>>
>>>
>> DHCP relay is running EAP acting as an EAP authenticator.
>>
>>> While the EAP/DHCP client on Home Gateway and Server will need to be
>>> aware/stateful with respect to EAP why would this extend to a DHCP
>>> relay? Is this not similar to the case of EAP-Message over RADIUS? A
>>> RADIUS proxy does not need to be aware of the details of the
>>>
>> EAP-Message
>>
>>> nor be able to decode them.
>>>
>> The difference from RADIUS proxy is that the RADIUS proxy is not =20
>> running
>>
>> EAP.
>>
>>> In the proposed DHCP message exchange of DISCOVER, DHCPEAP, =20
>>> DHCPOFFER,
>>> ACK I see no requirement for a stateful DHCP relay to support =20
>>> DHCPEAP.
>>>
>> Why? As I commented above, DHCP relay is running EAP acting as an =20
>> EAP authenticator, which will require lower-layer (in this case =20
>> DHCP relay) to maintain a state.
>>
>>> As with other DHCP relayed messages there is sufficient =20
>>> information in
>>> the response ( contains chaddr (IPv4) or peer address (IPv6 relay))
>>> received from the DHCP server to forward this message to the Home
>>> Gateway (operating as DHCP client and EAP supplicant).
>>>
>> In Figure 3 of draft-pruss, DHCPEAP message does not come from or =20
>> go to the DHCP server.
>> The DHCP relay in draft-pruss is not relaying DHCPEAP message =20
>> between DHCP client and DHCP server.
>>
>> Yoshihiro Ohba
>>
>>
>>> d
>>>
>>> -----Original Message-----
>>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On =20
>>> Behalf
>>> Of Yoshihiro Ohba
>>> Sent: Tuesday, July 28, 2009 1:00 AM
>>> To: Richard Pruss
>>> Cc: dhc WG; Ralph Droms
>>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>>> draft-brzozowski-dhcp-eap-analysis-00
>>>
>>> Richard Pruss wrote:
>>>
>>>> As I said to Ralph earlier we track transport and port =20
>>>> associations already to facilitate unnumbered interfaces, so the =20=

>>>> question was what
>>>>
>>
>>
>>>> state beyond that.
>>>>
>>> Beyond that each EAP conversation needs to be mapped to a distinct =20=

>>> transport and port association, which will require a state =20
>>> maintained
>>>
>> by
>>
>>> DHCP relay.
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>>>
>>>>
>>>>> In general, a state on the logical connection between the peer =20
>>>>> and authenticator needs to be maintained by any EAP lower-layer =20=

>>>>> for each
>>>>>
>>
>>
>>>>> EAP conversation. Such a state at least includes transport =20
>>>>> addresses
>>>>>
>>
>>
>>>>> and/or port numbers and they are not carried in EAP message.
>>>>>
>>>>> Yoshihiro Ohba
>>>>>
>>>>>
>>>>> Richard Pruss wrote:
>>>>>
>>>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>
>>>>>>> Richard Pruss wrote:
>>>>>>>
>>>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>
>>>>>>>>>> Well Ralph,  as you say something else is holding the state =20=

>>>>>>>>>> and
>>>>>>>>>>
>>
>>
>>>>>>>>>> the relay agent is simply handing the EAP messages to the =20
>>>>>>>>>> AAA  service in the relay function... so no the question =20
>>>>>>>>>> still makes
>>>>>>>>>>
>>
>>
>>>>>>>>>> no sense to me.
>>>>>>>>>>
>>>>>>>>> This is an incorrect statement. DHCP relay acting EAP =20
>>>>>>>>> authenticator is not simply handing EAP messages to the AAA, =20=

>>>>>>>>> it needs to maintain a state including a retransmission =20
>>>>>>>>> timer to retransmit outstanding EAP-Request message (cf. RFC =20=

>>>>>>>>> 4137).
>>>>>>>>>
>>>>>>>> No mate this is the part you probably missed, EAP is doing =20
>>>>>>>> that and it is a separate function regardless of what it is =20
>>>>>>>> being carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>>>
>>>>>>> All EAP transport protocols that I know of, including the ones =20=

>>>>>>> you
>>>>>>>
>>
>>
>>>>>>> listed above requires to maintain a state to carry EAP =20
>>>>>>> message.  There is no exception.
>>>>>>>
>>>>>> What state?
>>>>>>
>>>>>>
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> - Ric
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The thing that makes no sense is the assertion that the =20
>>>>>>>>>> relay agent suddenly needs to hold state, beyond what it =20
>>>>>>>>>> already does
>>>>>>>>>>
>>
>>
>>>>>>>>>> to handle ip unnumbered interfaces,
>>>>>>>>>> Ric
>>>>>>>>>>
>>>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>>>
>>>>>>>>>>> I would consider enforcing the address assignment as a
>>>>>>>>>>>
>> separate
>>
>>>>>>>>>>>
>>>
>>>>>>>>>>> function of the box that happens to house the DHCP relay =20
>>>>>>>>>>> agent
>>>>>>>>>>>
>>
>>
>>>>>>>>>>> function.  That is, the relay agent extracts the assigned =20=

>>>>>>>>>>> address from the DHCPACK and hands it to the address =20
>>>>>>>>>>> enforcement function.  Therefore, the relay agent function =20=

>>>>>>>>>>> is not keeping any state.  The address enforcement =20
>>>>>>>>>>> function could
>>>>>>>>>>>
>>
>>
>>>>>>>>>>> just as easily get that address assignment information =20
>>>>>>>>>>> from some other source like CLI or SNMP.
>>>>>>>>>>>
>>>>>>>>>>> The original purpose of the relay agent option was to hold =20=

>>>>>>>>>>> state for the relay agent.  We've tried to maintain that =20
>>>>>>>>>>> stateless operation (but I'm not sure we've strictly =20
>>>>>>>>>>> enforced the rule) with the definition of subsequent relay =20=

>>>>>>>>>>> agent
>>>>>>>>>>>
>>> options.
>>>
>>>>>>>>>>> - Ralph
>>>>>>>>>>>
>>>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
>>>>>>>>>>>>>>
>> to
>>
>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change =20=

>>>>>>>>>>>>>> to the existing architecture.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> As far as I understand, enforcing DHCP address =20
>>>>>>>>>>>>> assignment is
>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore =20
>>>>>>>>>>>>> the state is maintained outside the context of DHCP, =20
>>>>>>>>>>>>> which I don't care.  My comment was if DHCP relay needs =20=

>>>>>>>>>>>>> to be stateful in the middle of DHCP exchanges to carry =20=

>>>>>>>>>>>>> EAP.
>>>>>>>>>>>>> >=46rom DHCP point of view, it seems to be a major design
>>>>>>>>>>>>>
>>> change
>>>>>>>>>>>>> to DHCP.
>>>>>>>>>>>>>
>>>>>>>>>>>> Do you actually have an implementation of broadband DHCP
>>>>>>>>>>>>
>> relay
>>
>>>>>>>>>>>>
>>>
>>>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>>>
>>>>>>>>>>>> - Ric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Ric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
>>>>>>>>>>>>>>>
>> both
>>
>>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
>>>>>>>>>>>>>>>
>> DHCP.
>>
>>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>>> The issue is basically a conflict between =20
>>>>>>>>>>>>>>> statefullness of
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not =20
>>>>>>>>>>>>>>> maintain
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and =20
>>>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
>>>>>>>>>>>>>>>
>> DHCP
>>
>>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay =20
>>>>>>>>>>>>>>> agent will be no longer a stateless DHCP entity. I =20
>>>>>>>>>>>>>>> think this is
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an =20
>>>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
>>>>>>>>>>>>>>>
>> if
>>
>>>>>>>>>>>>>>>
>>>
>>>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>
>>>
>>>
>>
>>
>>
>>
>


From denghui02@gmail.com  Tue Jul 28 07:13:32 2009
Return-Path: <denghui02@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74D8E3A6FB3; Tue, 28 Jul 2009 07:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level: 
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=0.339,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jjm9m+moKgMp; Tue, 28 Jul 2009 07:13:31 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by core3.amsl.com (Postfix) with ESMTP id 950FF3A6F9F; Tue, 28 Jul 2009 07:13:31 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 28so10334wff.31 for <multiple recipients>; Tue, 28 Jul 2009 07:13:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=x9T5mgDz7MMCM/lMqBcoeTbmJOnFGn7Pe2sPtAqbAsc=; b=D5W4dliCCEa0PvfRhArlOkDo72Co6PvXozRLbMTvPykpsFqAUsRGSBoiQCJ7bV46oU 7Ywzk3n3V0Sonn7CK4K6SV4z1sRfTvyWG7ZV+pdjHLPEwX0MP6tL7VFhVjWwMrMvzvtT 8rP07J7hmADXCiYaV6GxMzyyCbv4LWYTcSDKw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=UMdc1gIoYnTbrpaGnr7qqWB7IgJXzIuEGsrD83f9Mt8rbhUHr40sGdfxuqSaXPlNvz 131A/ZWxngN4S2TaMCLu3OAQYg6ZT0ydY/CO+Rxgu4peSBwvQfPCNR/lEcJ5jIQg7jOB nZOzhPAp0J/eLPYxwhnrNUfiMID/s5fOnn2rw=
MIME-Version: 1.0
Received: by 10.142.48.7 with SMTP id v7mr984636wfv.122.1248790411405; Tue, 28  Jul 2009 07:13:31 -0700 (PDT)
Date: Tue, 28 Jul 2009 22:13:31 +0800
Message-ID: <1d38a3350907280713h48234e38n6069366b5fa0481d@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: behave@ietf.org, dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Discussion on Host based IPv6 Translation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 14:13:32 -0000

Hello all

Time/Date: 15:10-16:10 Thursday afternoon
Location: Lilla Teatern

The room is located up one flight of steps to the left of the main
entrance-- if you come in the doors at the base of the stairs near the
Big and Little Stage,
you can see the Lilla Teatern entrance if you look up and to the left.

We look forward to seeing you there.

thanks,

-Hui

From mellon@fugue.com  Tue Jul 28 07:56:14 2009
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B966E3A6F17 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 07:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j2mnIjuIrn4X for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 07:56:14 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id 0684C3A6E7B for <dhcwg@ietf.org>; Tue, 28 Jul 2009 07:56:14 -0700 (PDT)
Received: from [130.129.19.232] (dhcp-13e8.meeting.ietf.org [130.129.19.232]) by toccata.fugue.com (Postfix) with ESMTPSA id 14F2134E455D; Tue, 28 Jul 2009 08:00:23 -0700 (MST)
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com>
Message-Id: <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com>
From: Ted Lemon <mellon@fugue.com>
To: Richard Pruss <ric@cisco.com>
In-Reply-To: <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7A341)
Mime-Version: 1.0 (iPhone Mail 7A341)
Date: Tue, 28 Jul 2009 16:56:01 +0200
Cc: dhc WG <dhcwg@ietf.org>, MILES DAVID <David.Miles@alcatel-lucent.com.au>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 14:56:14 -0000

Ric, I get that you are frustrated by this discussion, but for us  
innocent bystanders, it would be helpful if you could respond  
factually, rather than expressing your frustration. Please remember  
that your grasp of what you are trying to do is much greater than  
ours, since we aren't trying to do it.   If you think it's a bad  
question, I'd like to see you say why.


From alan.kavanagh@ericsson.com  Tue Jul 28 08:56:40 2009
Return-Path: <alan.kavanagh@ericsson.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A97063A6DA3 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 08:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9zf40zFle2Y for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 08:56:39 -0700 (PDT)
Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) by core3.amsl.com (Postfix) with ESMTP id 0CCE93A6D23 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 08:56:38 -0700 (PDT)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id n6SFuS08015979; Tue, 28 Jul 2009 10:56:32 -0500
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 28 Jul 2009 10:56:30 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Jul 2009 11:56:30 -0400
Message-ID: <35815C929B41D2479A224FE098A272270798BD02@ecamlmw720.eamcs.ericsson.se>
In-Reply-To: <4A6EB8E6.4070800@toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoPXs9nyNI03WvISmK5wLAD2VQI9AAPKhRg
References: <4A6CD501.7030704@toshiba.co.jp><C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com><4A6D4F53.2060608@toshiba.co.jp><270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com><8BABA261-DE48-4684-85C8-419591061672@cisco.com><9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com><4A6D5C54.6050904@toshiba.co.jp><CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com><4A6D5E5D.8070707@toshiba.co.jp><7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com><4A6D685A.7000406@toshiba.co.jp><6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com><4A6DC7E3.2010001@toshiba.co.jp><986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com><4A6E45DC.5030103@toshiba.co.jp><986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp>
From: "Alan Kavanagh" <alan.kavanagh@ericsson.com>
To: "Yoshihiro Ohba" <yoshihiro.ohba@toshiba.co.jp>, "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
X-OriginalArrivalTime: 28 Jul 2009 15:56:31.0011 (UTC) FILETIME=[F9488F30:01CA0F9B]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 15:56:40 -0000

Ric

Just to understand correctly here, are you saying that the DHCP Relay
Model is no longer needed?=20

Also, just to add to what David Miles has noted on the thread, are we
saying that the supplicant must be in the Home Gateway? How do we handle
the case where some devices will be bridged and not routed through the
HGw?=20

Im not comparing applies and oranges but I would like to understand more
about if this is a one for all model!

Alan=20

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Yoshihiro Ohba
Sent: July 28, 2009 4:38 AM
To: MILES DAVID
Cc: dhc WG; Ralph Droms
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
draft-brzozowski-dhcp-eap-analysis-00

David,

I don't think "your interest" in Figure 2 more than Figure 3 is the same
as Broadband Forum's requirements. In TR-101, there is a requirement
"The Broadband Network Gateway MUST be able to function as a DHCP Relay
Agent as described in RFC 951 "BOOTP", RFC 2131"DHCP" and RFC 3046 "DHCP
Relay Agent Information Option" on selected untrusted interfaces."

It seems to me that if draft-pruss does not support Figure 3, then it
does not satisfy Broadband Forum's requirements. Please correct me if my
observation is wrong.

Yoshihiro Ohba


MILES DAVID wrote:
> I had not realized you were referring to Figure 3 - I was referring to

> a DHCP relay that may be between the NAS and the client such as those=20
> described as L2 DHCP relays and present in an access node/DSLAM, etc.=20
> I apologies for creating any further confusion there.
>
> If there were a bootp relay or l2 DHCP relay between the NAS and HGW=20
> in figure 2 - it would not need to be stateful. Also, if the NAS were=20
> not forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it=20
> would not need to have new state tables for DHCPEAP.
>
> Figure 3 describes something that is not well-described as a DHCP=20
> relay IMO (which may be your point as well). I would agree that there=20
> is state in this device by its nature and that having a forked EAP and

> it is a EAP authenticator.
>
> I am interested in the example of figure 2 and less interested in the=20
> deployment model of figure 3. Could it be an option to remove the=20
> split/forked EAP/RADIUS deployment model (which seems to be causing
> concern) and look at the model in figure 2?
>
> Thanks
>
> -David
>
> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
> Sent: Tuesday, July 28, 2009 9:57 AM
> To: MILES DAVID
> Cc: Richard Pruss; dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and=20
> draft-brzozowski-dhcp-eap-analysis-00
>
> MILES DAVID wrote:
>  =20
>> I wish to ask a question for clarification.
>>
>> I understood the proposal in draft-pruss-auth-dsl was that the DHCP=20
>> client was in fact also the EAP supplicant. There is no EAPoL or
>>    =20
> 802.1x
>  =20
>> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP=20
>> conversion.
>>
>>  =20
>>    =20
> DHCP relay is running EAP acting as an EAP authenticator.
>  =20
>> While the EAP/DHCP client on Home Gateway and Server will need to be=20
>> aware/stateful with respect to EAP why would this extend to a DHCP=20
>> relay? Is this not similar to the case of EAP-Message over RADIUS? A=20
>> RADIUS proxy does not need to be aware of the details of the
>>    =20
> EAP-Message
>  =20
>> nor be able to decode them.
>>  =20
>>    =20
> The difference from RADIUS proxy is that the RADIUS proxy is not=20
> running
>
> EAP.
>  =20
>> In the proposed DHCP message exchange of DISCOVER, DHCPEAP,=20
>> DHCPOFFER, ACK I see no requirement for a stateful DHCP relay to
support DHCPEAP.
>>  =20
>>    =20
> Why? As I commented above, DHCP relay is running EAP acting as an EAP=20
> authenticator, which will require lower-layer (in this case DHCP=20
> relay) to maintain a state.
>  =20
>> As with other DHCP relayed messages there is sufficient information=20
>> in the response ( contains chaddr (IPv4) or peer address (IPv6=20
>> relay)) received from the DHCP server to forward this message to the=20
>> Home Gateway (operating as DHCP client and EAP supplicant).
>>  =20
>>    =20
> In Figure 3 of draft-pruss, DHCPEAP message does not come from or go=20
> to the DHCP server.
> The DHCP relay in draft-pruss is not relaying DHCPEAP message between=20
> DHCP client and DHCP server.
>
> Yoshihiro Ohba
>
>  =20
>> d
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On=20
>> Behalf Of Yoshihiro Ohba
>> Sent: Tuesday, July 28, 2009 1:00 AM
>> To: Richard Pruss
>> Cc: dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and=20
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> Richard Pruss wrote:
>>  =20
>>    =20
>>> As I said to Ralph earlier we track transport and port associations=20
>>> already to facilitate unnumbered interfaces, so the question was=20
>>> what
>>>      =20
>
>  =20
>>> state beyond that.
>>>    =20
>>>      =20
>> Beyond that each EAP conversation needs to be mapped to a distinct=20
>> transport and port association, which will require a state maintained
>>    =20
> by
>  =20
>> DHCP relay.
>>
>> Yoshihiro Ohba
>>
>>  =20
>>    =20
>>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>>
>>>    =20
>>>      =20
>>>> In general, a state on the logical connection between the peer and=20
>>>> authenticator needs to be maintained by any EAP lower-layer for=20
>>>> each
>>>>        =20
>
>  =20
>>>> EAP conversation. Such a state at least includes transport=20
>>>> addresses
>>>>        =20
>
>  =20
>>>> and/or port numbers and they are not carried in EAP message.
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>
>>>> Richard Pruss wrote:
>>>>      =20
>>>>        =20
>>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>>
>>>>>        =20
>>>>>          =20
>>>>>> Richard Pruss wrote:
>>>>>>          =20
>>>>>>            =20
>>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>>
>>>>>>>            =20
>>>>>>>              =20
>>>>>>>> Richard Pruss wrote:
>>>>>>>>              =20
>>>>>>>>                =20
>>>>>>>>> Well Ralph,  as you say something else is holding the state=20
>>>>>>>>> and
>>>>>>>>>                  =20
>
>  =20
>>>>>>>>> the relay agent is simply handing the EAP messages to the AAA=20
>>>>>>>>> service in the relay function... so no the question still=20
>>>>>>>>> makes
>>>>>>>>>                  =20
>
>  =20
>>>>>>>>> no sense to me.
>>>>>>>>>                =20
>>>>>>>>>                  =20
>>>>>>>> This is an incorrect statement. DHCP relay acting EAP=20
>>>>>>>> authenticator is not simply handing EAP messages to the AAA, it

>>>>>>>> needs to maintain a state including a retransmission timer to=20
>>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>>              =20
>>>>>>>>                =20
>>>>>>> No mate this is the part you probably missed, EAP is doing that=20
>>>>>>> and it is a separate function regardless of what it is being=20
>>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>>            =20
>>>>>>>              =20
>>>>>> All EAP transport protocols that I know of, including the ones=20
>>>>>> you
>>>>>>            =20
>
>  =20
>>>>>> listed above requires to maintain a state to carry EAP message. =20
>>>>>> There is no exception.
>>>>>>          =20
>>>>>>            =20
>>>>> What state?
>>>>>
>>>>>        =20
>>>>>          =20
>>>>>> Yoshihiro Ohba
>>>>>>
>>>>>>
>>>>>>          =20
>>>>>>            =20
>>>>>>> - Ric
>>>>>>>
>>>>>>>
>>>>>>>            =20
>>>>>>>              =20
>>>>>>>> Yoshihiro Ohba
>>>>>>>>
>>>>>>>>              =20
>>>>>>>>                =20
>>>>>>>>> The thing that makes no sense is the assertion that the relay=20
>>>>>>>>> agent suddenly needs to hold state, beyond what it already=20
>>>>>>>>> does
>>>>>>>>>                  =20
>
>  =20
>>>>>>>>> to handle ip unnumbered interfaces, Ric
>>>>>>>>>
>>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>>
>>>>>>>>>                =20
>>>>>>>>>                  =20
>>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>>
>>>>>>>>>> I would consider enforcing the address assignment as a
>>>>>>>>>>                    =20
> separate
>  =20
>>>>>>>>>>                  =20
>>>>>>>>>>                    =20
>>  =20
>>    =20
>>>>>>>>>> function of the box that happens to house the DHCP relay=20
>>>>>>>>>> agent
>>>>>>>>>>                    =20
>
>  =20
>>>>>>>>>> function.  That is, the relay agent extracts the assigned=20
>>>>>>>>>> address from the DHCPACK and hands it to the address=20
>>>>>>>>>> enforcement function.  Therefore, the relay agent function is

>>>>>>>>>> not keeping any state.  The address enforcement function=20
>>>>>>>>>> could
>>>>>>>>>>                    =20
>
>  =20
>>>>>>>>>> just as easily get that address assignment information from=20
>>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>>
>>>>>>>>>> The original purpose of the relay agent option was to hold=20
>>>>>>>>>> state for the relay agent.  We've tried to maintain that=20
>>>>>>>>>> stateless operation (but I'm not sure we've strictly enforced

>>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>>                  =20
>>>>>>>>>>                    =20
>> options.
>>  =20
>>    =20
>>>>>>>>>> - Ralph
>>>>>>>>>>
>>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>>
>>>>>>>>>>                  =20
>>>>>>>>>>                    =20
>>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>>
>>>>>>>>>>>                    =20
>>>>>>>>>>>                      =20
>>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>>                      =20
>>>>>>>>>>>>                        =20
>>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
>>>>>>>>>>>>>                          =20
> to
>  =20
>>>>>>>>>>>>>                        =20
>>>>>>>>>>>>>                          =20
>>  =20
>>    =20
>>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to=20
>>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>>                        =20
>>>>>>>>>>>>>                          =20
>>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment=20
>>>>>>>>>>>> is
>>>>>>>>>>>>                        =20
>
>  =20
>>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the=20
>>>>>>>>>>>> state is maintained outside the context of DHCP, which I=20
>>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be=20
>>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>>> >From DHCP point of view, it seems to be a major design
>>>>>>>>>>>>                      =20
>>>>>>>>>>>>                        =20
>> change
>>  =20
>>    =20
>>>>>>>>>>>> to DHCP.
>>>>>>>>>>>>                      =20
>>>>>>>>>>>>                        =20
>>>>>>>>>>> Do you actually have an implementation of broadband DHCP
>>>>>>>>>>>                      =20
> relay
>  =20
>>>>>>>>>>>                    =20
>>>>>>>>>>>                      =20
>>  =20
>>    =20
>>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>>
>>>>>>>>>>> - Ric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                    =20
>>>>>>>>>>>                      =20
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>
>>>>>>>>>>>>                      =20
>>>>>>>>>>>>                        =20
>>>>>>>>>>>>> - Ric
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>                        =20
>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
>>>>>>>>>>>>>>                            =20
> both
>  =20
>>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>>                            =20
>>  =20
>>    =20
>>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
>>>>>>>>>>>>>>                            =20
> DHCP.
>  =20
>>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>>                            =20
>>  =20
>>    =20
>>>>>>>>>>>>>> The issue is basically a conflict between statefullness=20
>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>                            =20
>
>  =20
>>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not=20
>>>>>>>>>>>>>> maintain
>>>>>>>>>>>>>>                            =20
>
>  =20
>>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and=20
>>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
>>>>>>>>>>>>>>                            =20
> DHCP
>  =20
>>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>>                            =20
>>  =20
>>    =20
>>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent=20
>>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this=20
>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>                            =20
>
>  =20
>>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an=20
>>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
>>>>>>>>>>>>>>                            =20
> if
>  =20
>>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>>                            =20
>>  =20
>>    =20
>>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>>                          =20
>>>>>>>>>>>>>>                            =20
>>>>>>>>>>>>>                        =20
>>>>>>>>>>>>>                          =20
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>                    =20
>>>>>>>>>>>                      =20
>>>>>>>>>                =20
>>>>>>>>>                  =20
>>>>>>>            =20
>>>>>>>              =20
>>>>>        =20
>>>>>          =20
>>>>      =20
>>>>        =20
>>>    =20
>>>      =20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>
>>
>>  =20
>>    =20
>
>
>
>  =20

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

From ric@cisco.com  Tue Jul 28 12:37:22 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 209E53A69D5 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 12:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PwsLQ79zWlV for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 12:37:21 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id C62373A677E for <dhcwg@ietf.org>; Tue, 28 Jul 2009 12:37:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAP/vbkoKS+ej/2dsb2JhbAC9VIgnkBgFhBA
X-IronPort-AV: E=Sophos;i="4.43,284,1246838400"; d="scan'208";a="55866493"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-2.cisco.com with ESMTP; 28 Jul 2009 19:37:19 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6SJbJfm006937;  Wed, 29 Jul 2009 03:37:19 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6SJbIqP020813; Tue, 28 Jul 2009 19:37:18 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 03:37:18 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 03:37:17 +0800
Message-Id: <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 05:37:15 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 19:37:18.0030 (UTC) FILETIME=[D11F3EE0:01CA0FBA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1217; t=1248809839; x=1249673839; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=ULt9CIdstA08gt3Z/KLKkLViuq+bDozSYeBmrkaWznQ=; b=gUNati1vSIOSHN9ISYOSj4qF0bohcKMCo+9lDoW/9QgsyL110X/lulkDMy usTm7t1/5j4QXHtMz1+ExnpaKASwcKs95kAdwGDt4wLVh/GHlq+aCxRooaR8 baMquX/uM56WOpwpeevGK0rJkvxE4jrhE3mbkRG7vkzOXZ7Mi1jMg=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, MILES DAVID <David.Miles@alcatel-lucent.com.au>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 19:37:22 -0000

Sorry Ted, he is claiming we do not meet the requirements because we  
vendors call the L3 DHCP relay
function a proxy.   Sinking to a semantic debate on if something is a  
proxy or a relay is a new low.

We do lots of extra things in this L3 edge because we compete on  
features and this L3 Edge does all kind
of things I am sure a pure relay does not, ones I often mention are  
map attributes from AAA and interact with
the local session enforcement and routing mechanisms so that the  
assigned address is the only one the DHCP client can
send and receive traffic on.

It was because DHCP does so much already in the BRAS/NAS that the  
adding a few attributes for authentication
to add to the quality of the decision is a logical choice.

- Ric

On 29/07/2009, at 12:56 AM, Ted Lemon wrote:

> Ric, I get that you are frustrated by this discussion, but for us  
> innocent bystanders, it would be helpful if you could respond  
> factually, rather than expressing your frustration. Please remember  
> that your grasp of what you are trying to do is much greater than  
> ours, since we aren't trying to do it.   If you think it's a bad  
> question, I'd like to see you say why.
>


From ric@cisco.com  Tue Jul 28 13:02:16 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03ECD3A6B9B for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 13:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.69
X-Spam-Level: 
X-Spam-Status: No, score=-5.69 tagged_above=-999 required=5 tests=[AWL=0.909,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jg5g26JsTJ2y for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 13:02:14 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id AE6C13A6AAD for <dhcwg@ietf.org>; Tue, 28 Jul 2009 13:02:13 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAGP1bkoKS+eh/2dsb2JhbAC9LognkBsFhBCBTQ
X-IronPort-AV: E=Sophos;i="4.43,284,1246838400"; d="scan'208";a="58629935"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 28 Jul 2009 20:02:06 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6SK250H015590;  Wed, 29 Jul 2009 04:02:05 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6SK24aw023359; Tue, 28 Jul 2009 20:02:04 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 04:02:04 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 04:02:02 +0800
Message-Id: <FA723206-C178-4C4D-AD1A-496AD644D1D5@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Alan Kavanagh <alan.kavanagh@ericsson.com>
In-Reply-To: <35815C929B41D2479A224FE098A272270798BD02@ecamlmw720.eamcs.ericsson.se>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 06:02:00 +1000
References: <4A6CD501.7030704@toshiba.co.jp><C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com><4A6D4F53.2060608@toshiba.co.jp><270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com><8BABA261-DE48-4684-85C8-419591061672@cisco.com><9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com><4A6D5C54.6050904@toshiba.co.jp><CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com><4A6D5E5D.8070707@toshiba.co.jp><7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com><4A6D685A.7000406@toshiba.co.jp><6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com><4A6DC7E3.2010001@toshiba.co.jp><986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com><4A6E45DC.5030103@toshiba.co.jp><986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <35815C929B41D2479A224FE098A272270798BD02@ecamlmw720.eamcs.ericsson.se>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 20:02:03.0538 (UTC) FILETIME=[468DC720:01CA0FBE]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=13757; t=1248811325; x=1249675325; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=bE9q/e0q6bYoVtpuu1xkLJUhOAgMdeSHCcBIgVyXXS8=; b=BFPUBlJ6AxEcBBQXgF7HJOMqw8uIGpNP6K0KTjYabkqqqPMGiMd80Y/IeT a53VDGfgLS1L+n7R8Glz6E5Od3LWs0MGNTwHDqQg/oQye9tQqvgn7enZxEqy fQpwVdA0OovmaKRg6l0/VW4EO32gOjSs5f/ZpLN5iRrwdUl4TPslo=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, MILES DAVID <David.Miles@alcatel-lucent.com.au>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 20:02:16 -0000

Hi Alan,


On 29/07/2009, at 1:56 AM, Alan Kavanagh wrote:

> Ric
>
> Just to understand correctly here, are you saying that the DHCP Relay
> Model is no longer needed?
>
Nope it is still needed, but most of us including I believe the  
SmartEdge call this DHCP proxy
because it proxies attributes into AAA.

> Also, just to add to what David Miles has noted on the thread, are we
> saying that the supplicant must be in the Home Gateway?
No there is no such limitation in the draft, but realistically this is  
targeted at PPP migration so
places where we use authentication today.

> How do we handle
> the case where some devices will be bridged and not routed through the
> HGw?
This works just fine and we are certainly seeing this being used for  
set-top box network
authentication and IP address allocation, in some very large chaotic  
L2 centric networks.

>
> Im not comparing applies and oranges but I would like to understand  
> more
> about if this is a one for all model!

Totally fun with doing that,
Ric

>
> Alan
>
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Yoshihiro Ohba
> Sent: July 28, 2009 4:38 AM
> To: MILES DAVID
> Cc: dhc WG; Ralph Droms
> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
> David,
>
> I don't think "your interest" in Figure 2 more than Figure 3 is the  
> same
> as Broadband Forum's requirements. In TR-101, there is a requirement
> "The Broadband Network Gateway MUST be able to function as a DHCP  
> Relay
> Agent as described in RFC 951 "BOOTP", RFC 2131"DHCP" and RFC 3046  
> "DHCP
> Relay Agent Information Option" on selected untrusted interfaces."
>
> It seems to me that if draft-pruss does not support Figure 3, then it
> does not satisfy Broadband Forum's requirements. Please correct me  
> if my
> observation is wrong.
>
> Yoshihiro Ohba
>
>
> MILES DAVID wrote:
>> I had not realized you were referring to Figure 3 - I was referring  
>> to
>
>> a DHCP relay that may be between the NAS and the client such as those
>> described as L2 DHCP relays and present in an access node/DSLAM, etc.
>> I apologies for creating any further confusion there.
>>
>> If there were a bootp relay or l2 DHCP relay between the NAS and HGW
>> in figure 2 - it would not need to be stateful. Also, if the NAS were
>> not forking EAP/RADIUS (it was a "classical" bootp/DHCP relay) it
>> would not need to have new state tables for DHCPEAP.
>>
>> Figure 3 describes something that is not well-described as a DHCP
>> relay IMO (which may be your point as well). I would agree that there
>> is state in this device by its nature and that having a forked EAP  
>> and
>
>> it is a EAP authenticator.
>>
>> I am interested in the example of figure 2 and less interested in the
>> deployment model of figure 3. Could it be an option to remove the
>> split/forked EAP/RADIUS deployment model (which seems to be causing
>> concern) and look at the model in figure 2?
>>
>> Thanks
>>
>> -David
>>
>> -----Original Message-----
>> From: Yoshihiro Ohba [mailto:yoshihiro.ohba@toshiba.co.jp]
>> Sent: Tuesday, July 28, 2009 9:57 AM
>> To: MILES DAVID
>> Cc: Richard Pruss; dhc WG; Ralph Droms
>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>> MILES DAVID wrote:
>>
>>> I wish to ask a question for clarification.
>>>
>>> I understood the proposal in draft-pruss-auth-dsl was that the DHCP
>>> client was in fact also the EAP supplicant. There is no EAPoL or
>>>
>> 802.1x
>>
>>> device. The DHCP relay is not performing a EAPoL/802.1x to DHCP
>>> conversion.
>>>
>>>
>>>
>> DHCP relay is running EAP acting as an EAP authenticator.
>>
>>> While the EAP/DHCP client on Home Gateway and Server will need to be
>>> aware/stateful with respect to EAP why would this extend to a DHCP
>>> relay? Is this not similar to the case of EAP-Message over RADIUS? A
>>> RADIUS proxy does not need to be aware of the details of the
>>>
>> EAP-Message
>>
>>> nor be able to decode them.
>>>
>>>
>> The difference from RADIUS proxy is that the RADIUS proxy is not
>> running
>>
>> EAP.
>>
>>> In the proposed DHCP message exchange of DISCOVER, DHCPEAP,
>>> DHCPOFFER, ACK I see no requirement for a stateful DHCP relay to
> support DHCPEAP.
>>>
>>>
>> Why? As I commented above, DHCP relay is running EAP acting as an EAP
>> authenticator, which will require lower-layer (in this case DHCP
>> relay) to maintain a state.
>>
>>> As with other DHCP relayed messages there is sufficient information
>>> in the response ( contains chaddr (IPv4) or peer address (IPv6
>>> relay)) received from the DHCP server to forward this message to the
>>> Home Gateway (operating as DHCP client and EAP supplicant).
>>>
>>>
>> In Figure 3 of draft-pruss, DHCPEAP message does not come from or go
>> to the DHCP server.
>> The DHCP relay in draft-pruss is not relaying DHCPEAP message between
>> DHCP client and DHCP server.
>>
>> Yoshihiro Ohba
>>
>>
>>> d
>>>
>>> -----Original Message-----
>>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On
>>> Behalf Of Yoshihiro Ohba
>>> Sent: Tuesday, July 28, 2009 1:00 AM
>>> To: Richard Pruss
>>> Cc: dhc WG; Ralph Droms
>>> Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
>>> draft-brzozowski-dhcp-eap-analysis-00
>>>
>>> Richard Pruss wrote:
>>>
>>>
>>>> As I said to Ralph earlier we track transport and port associations
>>>> already to facilitate unnumbered interfaces, so the question was
>>>> what
>>>>
>>
>>
>>>> state beyond that.
>>>>
>>>>
>>> Beyond that each EAP conversation needs to be mapped to a distinct
>>> transport and port association, which will require a state  
>>> maintained
>>>
>> by
>>
>>> DHCP relay.
>>>
>>> Yoshihiro Ohba
>>>
>>>
>>>
>>>> On 27/07/2009, at 6:42 PM, Yoshihiro Ohba wrote:
>>>>
>>>>
>>>>
>>>>> In general, a state on the logical connection between the peer and
>>>>> authenticator needs to be maintained by any EAP lower-layer for
>>>>> each
>>>>>
>>
>>
>>>>> EAP conversation. Such a state at least includes transport
>>>>> addresses
>>>>>
>>
>>
>>>>> and/or port numbers and they are not carried in EAP message.
>>>>>
>>>>> Yoshihiro Ohba
>>>>>
>>>>>
>>>>> Richard Pruss wrote:
>>>>>
>>>>>
>>>>>> On 27/07/2009, at 5:59 PM, Yoshihiro Ohba wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Richard Pruss wrote:
>>>>>>>
>>>>>>>
>>>>>>>> On 27/07/2009, at 5:50 PM, Yoshihiro Ohba wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Well Ralph,  as you say something else is holding the state
>>>>>>>>>> and
>>>>>>>>>>
>>
>>
>>>>>>>>>> the relay agent is simply handing the EAP messages to the AAA
>>>>>>>>>> service in the relay function... so no the question still
>>>>>>>>>> makes
>>>>>>>>>>
>>
>>
>>>>>>>>>> no sense to me.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> This is an incorrect statement. DHCP relay acting EAP
>>>>>>>>> authenticator is not simply handing EAP messages to the AAA,  
>>>>>>>>> it
>
>>>>>>>>> needs to maintain a state including a retransmission timer to
>>>>>>>>> retransmit outstanding EAP-Request message (cf. RFC 4137).
>>>>>>>>>
>>>>>>>>>
>>>>>>>> No mate this is the part you probably missed, EAP is doing that
>>>>>>>> and it is a separate function regardless of what it is being
>>>>>>>> carried on , PPP, Ethernet, DHCP here is just transport.
>>>>>>>>
>>>>>>>>
>>>>>>> All EAP transport protocols that I know of, including the ones
>>>>>>> you
>>>>>>>
>>
>>
>>>>>>> listed above requires to maintain a state to carry EAP message.
>>>>>>> There is no exception.
>>>>>>>
>>>>>>>
>>>>>> What state?
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Yoshihiro Ohba
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> - Ric
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The thing that makes no sense is the assertion that the relay
>>>>>>>>>> agent suddenly needs to hold state, beyond what it already
>>>>>>>>>> does
>>>>>>>>>>
>>
>>
>>>>>>>>>> to handle ip unnumbered interfaces, Ric
>>>>>>>>>>
>>>>>>>>>> On 27/07/2009, at 5:26 PM, Ralph Droms wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Ric - the question seems sensible to me.
>>>>>>>>>>>
>>>>>>>>>>> I would consider enforcing the address assignment as a
>>>>>>>>>>>
>> separate
>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>> function of the box that happens to house the DHCP relay
>>>>>>>>>>> agent
>>>>>>>>>>>
>>
>>
>>>>>>>>>>> function.  That is, the relay agent extracts the assigned
>>>>>>>>>>> address from the DHCPACK and hands it to the address
>>>>>>>>>>> enforcement function.  Therefore, the relay agent function  
>>>>>>>>>>> is
>
>>>>>>>>>>> not keeping any state.  The address enforcement function
>>>>>>>>>>> could
>>>>>>>>>>>
>>
>>
>>>>>>>>>>> just as easily get that address assignment information from
>>>>>>>>>>> some other source like CLI or SNMP.
>>>>>>>>>>>
>>>>>>>>>>> The original purpose of the relay agent option was to hold
>>>>>>>>>>> state for the relay agent.  We've tried to maintain that
>>>>>>>>>>> stateless operation (but I'm not sure we've strictly  
>>>>>>>>>>> enforced
>
>>>>>>>>>>> the rule) with the definition of subsequent relay agent
>>>>>>>>>>>
>>>>>>>>>>>
>>> options.
>>>
>>>
>>>>>>>>>>> - Ralph
>>>>>>>>>>>
>>>>>>>>>>> On Jul 27, 2009, at 9:04 AM 7/27/09, Richard Pruss wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> On 27/07/2009, at 4:55 PM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Richard Pruss wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Relay's in the broadband architecture have to be stateful
>>>>>>>>>>>>>>
>> to
>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>>>> enforce DHCP address assignment, so it is not a change to
>>>>>>>>>>>>>> the existing architecture.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> As far as I understand, enforcing DHCP address assignment
>>>>>>>>>>>>> is
>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>> needed *after* DHCP exchanges are done, and therefore the
>>>>>>>>>>>>> state is maintained outside the context of DHCP, which I
>>>>>>>>>>>>> don't care.  My comment was if DHCP relay needs to be
>>>>>>>>>>>>> stateful in the middle of DHCP exchanges to carry EAP.
>>>>>>>>>>>>>> From DHCP point of view, it seems to be a major design
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>> change
>>>
>>>
>>>>>>>>>>>>> to DHCP.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> Do you actually have an implementation of broadband DHCP
>>>>>>>>>>>>
>> relay
>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>> because  what you are talking makes very little sense?
>>>>>>>>>>>>
>>>>>>>>>>>> - Ric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Ric
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 27/07/2009, at 8:13 AM, Yoshihiro Ohba wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have read both documents. Thanks for the authors for
>>>>>>>>>>>>>>>
>> both
>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>>>>> documents providing techinical details.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> However, I still have an issue with carrying EAP over
>>>>>>>>>>>>>>>
>> DHCP.
>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>>>>> The issue is basically a conflict between statefullness
>>>>>>>>>>>>>>> of
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> EAP and statelessness of DHCP relay agent.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> As far as I understand, DHCP relay agent does not
>>>>>>>>>>>>>>> maintain
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> a state. On the other hand, EAP requires peer and
>>>>>>>>>>>>>>> authenticator to maintain a state (see RFC 4137). When
>>>>>>>>>>>>>>>
>> DHCP
>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>>>>> relay agent acts EAP authenticator, then the relay agent
>>>>>>>>>>>>>>> will be no longer a stateless DHCP entity. I think this
>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>
>>
>>
>>>>>>>>>>>>>>> not discussed in dhcp-eap-analysis draft. Is this an
>>>>>>>>>>>>>>> acceptable design change for DHCP?  Or please correct me
>>>>>>>>>>>>>>>
>> if
>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>
>>>
>>>>>>>>>>>>>>> I am wrong.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>> Yoshihiro Ohba
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> dhcwg mailing list
>>>>>>>>>>>> dhcwg@ietf.org
>>>>>>>>>>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 15:39:18 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 973513A6CD5 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 15:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.439
X-Spam-Level: 
X-Spam-Status: No, score=-3.439 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o3vNZBU-SyBl for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 15:39:17 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 935D43A6CC7 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 15:39:17 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6SMd0nB028987; Wed, 29 Jul 2009 07:39:00 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6SMd0oe006488; Wed, 29 Jul 2009 07:39:00 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id HAA06487; Wed, 29 Jul 2009 07:39:00 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6SMd02b025224; Wed, 29 Jul 2009 07:39:00 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6SMcxwF014036; Wed, 29 Jul 2009 07:38:59 +0900 (JST)
Received: from [133.199.16.61] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNI0033ZK8ZN7B0@mail.po.toshiba.co.jp>; Wed, 29 Jul 2009 07:38:59 +0900 (JST)
Date: Tue, 28 Jul 2009 18:38:57 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6F7E01.20403@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 22:39:18 -0000

Richard Pruss wrote:
> Sorry Ted, he is claiming we do not meet the requirements because we 
> vendors call the L3 DHCP relay
> function a proxy.   Sinking to a semantic debate on if something is a 
> proxy or a relay is a new low.

Ric, the reason of my cliam is NOT because you call the DHCP relay 
funtion a proxy.  I really don't care how vendors are calling the L3 
DHCP relay.  My claim is, if the scenario described in Figure 3 of 
draft-pruss is removed from the draft, then it will not satisfy the 
Broadband Forum's requirements.
>
> We do lots of extra things in this L3 edge because we compete on 
> features and this L3 Edge does all kind
> of things I am sure a pure relay does not, ones I often mention are 
> map attributes from AAA and interact with
> the local session enforcement and routing mechanisms so that the 
> assigned address is the only one the DHCP client can
> send and receive traffic on.

As far as I understand, what you often mention regarding mapping 
attributes from AAA *without EAP* is still possible based on caching.  
As Ted mentioned earlier, this kind of caching does not necessarily 
require the DHCP relay (or DHCP proxy in your term) to be stateful 
entity in terms of DHCP operation.  However, *with EAP*, the DHCP relay 
will need to be stateful as I  and Alper mentioned earlier. It seems 
that DHC WG people are sensible about such a change.  I hope I explained 
my technical point clear enough. If not, let's discuss further.

Yoshihiro Ohba

>
> It was because DHCP does so much already in the BRAS/NAS that the 
> adding a few attributes for authentication
> to add to the quality of the decision is a logical choice.
>
> - Ric
>
> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>
>> Ric, I get that you are frustrated by this discussion, but for us 
>> innocent bystanders, it would be helpful if you could respond 
>> factually, rather than expressing your frustration. Please remember 
>> that your grasp of what you are trying to do is much greater than 
>> ours, since we aren't trying to do it.   If you think it's a bad 
>> question, I'd like to see you say why.
>>
>
>
>


From ric@cisco.com  Tue Jul 28 15:51:17 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4E503A6C1B for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 15:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.766
X-Spam-Level: 
X-Spam-Status: No, score=-3.766 tagged_above=-999 required=5 tests=[AWL=-1.167, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GAHxZf-A-ODk for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 15:51:16 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 3BCC13A6ABB for <dhcwg@ietf.org>; Tue, 28 Jul 2009 15:51:16 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALIdb0oKS+ej/2dsb2JhbAC9EognkCgFhBA
X-IronPort-AV: E=Sophos;i="4.43,285,1246838400"; d="scan'208";a="55868564"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-2.cisco.com with ESMTP; 28 Jul 2009 22:51:11 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6SMpB8g028387;  Wed, 29 Jul 2009 06:51:11 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6SMpAIC012982; Tue, 28 Jul 2009 22:51:11 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 06:51:10 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 06:51:09 +0800
Message-Id: <8FB19091-639D-4A2C-B9C0-87237199F65C@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6F7E01.20403@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 08:51:07 +1000
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> <4A6F7E01.20403@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 28 Jul 2009 22:51:10.0139 (UTC) FILETIME=[E66638B0:01CA0FD5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3047; t=1248821471; x=1249685471; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=jYidpxljfbnHdOshQQo2D8L9eVc/Ma4BKOPzy9QtXzw=; b=NFHx4BIlkcn1UJQsMRJkJLlS2f2BdHma8/tV11UYPKFe/sde6baPi6sBKe Qr9JnCy3dWdTpwcqBsEmT1gn6byRa05+z9d0IcgjI3lx1LE5c8eDUGzipeVH Q5tCX3GMaVN0BUpLUhEvUqQo7Ng8Ov6mxOEJjK7t4tfApTHKCPa40=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 22:51:17 -0000

On 29/07/2009, at 8:38 AM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>> Sorry Ted, he is claiming we do not meet the requirements because  
>> we vendors call the L3 DHCP relay
>> function a proxy.   Sinking to a semantic debate on if something is  
>> a proxy or a relay is a new low.
>
> Ric, the reason of my cliam is NOT because you call the DHCP relay  
> funtion a proxy.  I really don't care how vendors are calling the L3  
> DHCP relay.  My claim is, if the scenario described in Figure 3 of  
> draft-pruss is removed from the draft, then it will not satisfy the  
> Broadband Forum's requirements.

So you are editing what is an not in the draft for me?

>>
>> We do lots of extra things in this L3 edge because we compete on  
>> features and this L3 Edge does all kind
>> of things I am sure a pure relay does not, ones I often mention are  
>> map attributes from AAA and interact with
>> the local session enforcement and routing mechanisms so that the  
>> assigned address is the only one the DHCP client can
>> send and receive traffic on.
>
> As far as I understand, what you often mention regarding mapping  
> attributes from AAA *without EAP* is still possible based on  
> caching.  As Ted mentioned earlier, this kind of caching does not  
> necessarily require the DHCP relay (or DHCP proxy in your term) to  
> be stateful entity in terms of DHCP operation.  However, *with EAP*,  
> the DHCP relay will need to be stateful as I  and Alper mentioned  
> earlier. It seems that DHC WG people are sensible about such a  
> change.  I hope I explained my technical point clear enough. If not,  
> let's discuss further.

Actually as I have mentioned twice, port tracking state you pointed to  
long predates DHCP with EAP as when the BRAS ports are unnumbered a  
single IP address is used as the interface address for thousands of  
interfaces, you need to know that state to be able to forward the DHCP  
packets back down to the correct port.  So no as I have being trying  
to point out this is no change, these are session aggregation devices,  
their roll is to be stateful for each session.  Regardless of if the  
state is implemented inside or outside of the DHCP relay function the  
BRAS is certainly tracking that state and a whole lot more.

- Ric


>
> Yoshihiro Ohba
>
>>
>> It was because DHCP does so much already in the BRAS/NAS that the  
>> adding a few attributes for authentication
>> to add to the quality of the decision is a logical choice.
>>
>> - Ric
>>
>> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>>
>>> Ric, I get that you are frustrated by this discussion, but for us  
>>> innocent bystanders, it would be helpful if you could respond  
>>> factually, rather than expressing your frustration. Please  
>>> remember that your grasp of what you are trying to do is much  
>>> greater than ours, since we aren't trying to do it.   If you think  
>>> it's a bad question, I'd like to see you say why.
>>>
>>
>>
>>
>


From David.Miles@alcatel-lucent.com.au  Tue Jul 28 16:09:33 2009
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECD1A3A6928 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 16:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1NH9Wf+9PKkY for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 16:09:32 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by core3.amsl.com (Postfix) with ESMTP id 7A2B43A6904 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 16:09:31 -0700 (PDT)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id n6SN9T2A007711; Tue, 28 Jul 2009 18:09:29 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id n6SN9QkJ016695; Tue, 28 Jul 2009 18:09:27 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com [135.254.109.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n6SN3fXt014652; Wed, 29 Jul 2009 07:03:43 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 29 Jul 2009 07:09:21 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Wed, 29 Jul 2009 07:09:21 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D03B9D1C6@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <4A6EB8E6.4070800@toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoPXr/Ja1tvxjOETSWqkrdpr9rxdwAIuQsw
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp>
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: "Yoshihiro Ohba" <yoshihiro.ohba@toshiba.co.jp>
X-OriginalArrivalTime: 28 Jul 2009 23:09:21.0227 (UTC) FILETIME=[70BD09B0:01CA0FD8]
X-Scanned-By: MIMEDefang 2.57 on 172.22.12.27
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2009 23:09:34 -0000

SGkgWW9zaGloaXJvLA0KDQpTZWUgbXkgbGluZSBiZWxvdzoNCj4gQWxzbywgaWYgdGhlIE5BUyB3
ZXJlIG5vdA0KPiBmb3JraW5nIEVBUC9SQURJVVMgKGl0IHdhcyBhICJjbGFzc2ljYWwiIGJvb3Rw
L0RIQ1AgcmVsYXkpIGl0IHdvdWxkIG5vdA0KPiBuZWVkIHRvIGhhdmUgbmV3IHN0YXRlIHRhYmxl
cyBmb3IgREhDUEVBUC4NCg0KVGhlcmUgaXMgYSBuZXcgd29ya2luZyB0ZXh0IGxvb2tpbmcgYXQg
d2hhdCBpcyBjYWxsZWQgIklQIFNlc3Npb25zIiBpbiB0aGUgQnJvYWRiYW5kIEZvcnVtIHRoYXQg
d291bGQgbGlrZWx5IGFkZHJlc3MgdGhpbmdzIGxpa2UgREhDUCBBdXRoIHdoaWNoIGlzIGV4dGVu
c2libGUgdG8gc3VwcG9ydCBuZXcgbW9kZWxzLiBQUywgdGhlIG5leHQgQkJGIGlzIGluIFRva3lv
IGFzIEkgdW5kZXJzdGFuZC4NCg0KTXkgaW50ZXJlc3QgaXMgbmFtZWx5IHRoYXQsIGp1c3Qgd2hh
dCBJIGFtIGludGVyZXN0ZWQgaW4gKGFuZCBhbiBvYnNlcnZhdGlvbiBvZiB3aGF0IGFyY2hpdGVj
dHVyZXMgSSBoYXZlIHNlZW4gZGVwbG95ZWQpLiBBIHNwbGl0IG1vZGVsIHdoZXJlIGJvdGggUkFE
SVVTIGFuZCBESENQIGNvbWUgZnJvbSBhIEJORy9OQVMgaXMgbm90IHZlcnkgY29tbW9uIGFzIGN1
c3RvbWVycyB3aWxsIHR5cGljYWxseSB1c2UgZWl0aGVyIG9yLiBJIGRvIG5vdCBwbGFjZSBhIHNw
bGl0IG1vZGVsIGFzIGEgaGlnaCBwcmlvcml0eSBhbmQgaGF2ZSBzaW1wbHkgb2JzZXJ2ZWQgdGhh
dCB0aGlzIGlzIHdoZXJlIG11Y2ggZGViYXRlIGlzIG9yaWdpbmF0aW5nIGZyb20uDQoNCkNoZWVy
cywNCg0KLWQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFlvc2hpaGlybyBP
aGJhIFttYWlsdG86eW9zaGloaXJvLm9oYmFAdG9zaGliYS5jby5qcF0gDQpTZW50OiBUdWVzZGF5
LCBKdWx5IDI4LCAyMDA5IDY6MDggUE0NClRvOiBNSUxFUyBEQVZJRA0KQ2M6IFJpY2hhcmQgUHJ1
c3M7IGRoYyBXRzsgUmFscGggRHJvbXMNClN1YmplY3Q6IFJlOiBbZGhjd2ddIENvbW1lbnRzIG9u
IGRyYWZ0LXBydXNzLWRoY3AtYXV0aC1kc2wtMDYgYW5kIGRyYWZ0LWJyem96b3dza2ktZGhjcC1l
YXAtYW5hbHlzaXMtMDANCg0KRGF2aWQsDQoNCkkgZG9uJ3QgdGhpbmsgInlvdXIgaW50ZXJlc3Qi
IGluIEZpZ3VyZSAyIG1vcmUgdGhhbiBGaWd1cmUgMyBpcyB0aGUgc2FtZSANCmFzIEJyb2FkYmFu
ZCBGb3J1bSdzIHJlcXVpcmVtZW50cy4gSW4gVFItMTAxLCB0aGVyZSBpcyBhIHJlcXVpcmVtZW50
IA0KIlRoZSBCcm9hZGJhbmQgTmV0d29yayBHYXRld2F5IE1VU1QgYmUgYWJsZSB0byBmdW5jdGlv
biBhcyBhIERIQ1AgUmVsYXkgDQpBZ2VudCBhcyBkZXNjcmliZWQgaW4gUkZDIDk1MSDigJxCT09U
UOKAnSwgUkZDIDIxMzHigJ1ESENQ4oCdIGFuZCBSRkMgMzA0NiDigJxESENQIA0KUmVsYXkgQWdl
bnQgSW5mb3JtYXRpb24gT3B0aW9u4oCdIG9uIHNlbGVjdGVkIHVudHJ1c3RlZCBpbnRlcmZhY2Vz
LiINCg0KSXQgc2VlbXMgdG8gbWUgdGhhdCBpZiBkcmFmdC1wcnVzcyBkb2VzIG5vdCBzdXBwb3J0
IEZpZ3VyZSAzLCB0aGVuIGl0IA0KZG9lcyBub3Qgc2F0aXNmeSBCcm9hZGJhbmQgRm9ydW0ncyBy
ZXF1aXJlbWVudHMuIFBsZWFzZSBjb3JyZWN0IG1lIGlmIG15IA0Kb2JzZXJ2YXRpb24gaXMgd3Jv
bmcuDQoNCllvc2hpaGlybyBPaGJhDQoNCg0KTUlMRVMgREFWSUQgd3JvdGU6DQo+IEkgaGFkIG5v
dCByZWFsaXplZCB5b3Ugd2VyZSByZWZlcnJpbmcgdG8gRmlndXJlIDMgLSBJIHdhcyByZWZlcnJp
bmcgdG8gYQ0KPiBESENQIHJlbGF5IHRoYXQgbWF5IGJlIGJldHdlZW4gdGhlIE5BUyBhbmQgdGhl
IGNsaWVudCBzdWNoIGFzIHRob3NlDQo+IGRlc2NyaWJlZCBhcyBMMiBESENQIHJlbGF5cyBhbmQg
cHJlc2VudCBpbiBhbiBhY2Nlc3Mgbm9kZS9EU0xBTSwgZXRjLiBJDQo+IGFwb2xvZ2llcyBmb3Ig
Y3JlYXRpbmcgYW55IGZ1cnRoZXIgY29uZnVzaW9uIHRoZXJlLg0KPg0KPiBJZiB0aGVyZSB3ZXJl
IGEgYm9vdHAgcmVsYXkgb3IgbDIgREhDUCByZWxheSBiZXR3ZWVuIHRoZSBOQVMgYW5kIEhHVyBp
bg0KPiBmaWd1cmUgMiAtIGl0IHdvdWxkIG5vdCBuZWVkIHRvIGJlIHN0YXRlZnVsLiBBbHNvLCBp
ZiB0aGUgTkFTIHdlcmUgbm90DQo+IGZvcmtpbmcgRUFQL1JBRElVUyAoaXQgd2FzIGEgImNsYXNz
aWNhbCIgYm9vdHAvREhDUCByZWxheSkgaXQgd291bGQgbm90DQo+IG5lZWQgdG8gaGF2ZSBuZXcg
c3RhdGUgdGFibGVzIGZvciBESENQRUFQLg0KPg0KPiBGaWd1cmUgMyBkZXNjcmliZXMgc29tZXRo
aW5nIHRoYXQgaXMgbm90IHdlbGwtZGVzY3JpYmVkIGFzIGEgREhDUCByZWxheQ0KPiBJTU8gKHdo
aWNoIG1heSBiZSB5b3VyIHBvaW50IGFzIHdlbGwpLiBJIHdvdWxkIGFncmVlIHRoYXQgdGhlcmUg
aXMgc3RhdGUNCj4gaW4gdGhpcyBkZXZpY2UgYnkgaXRzIG5hdHVyZSBhbmQgdGhhdCBoYXZpbmcg
YSBmb3JrZWQgRUFQIGFuZCBpdCBpcyBhDQo+IEVBUCBhdXRoZW50aWNhdG9yLiANCj4NCj4gSSBh
bSBpbnRlcmVzdGVkIGluIHRoZSBleGFtcGxlIG9mIGZpZ3VyZSAyIGFuZCBsZXNzIGludGVyZXN0
ZWQgaW4gdGhlDQo+IGRlcGxveW1lbnQgbW9kZWwgb2YgZmlndXJlIDMuIENvdWxkIGl0IGJlIGFu
IG9wdGlvbiB0byByZW1vdmUgdGhlDQo+IHNwbGl0L2ZvcmtlZCBFQVAvUkFESVVTIGRlcGxveW1l
bnQgbW9kZWwgKHdoaWNoIHNlZW1zIHRvIGJlIGNhdXNpbmcNCj4gY29uY2VybikgYW5kIGxvb2sg
YXQgdGhlIG1vZGVsIGluIGZpZ3VyZSAyPw0KPg0KPiBUaGFua3MNCj4NCj4gLURhdmlkDQo+DQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFlvc2hpaGlybyBPaGJhIFttYWls
dG86eW9zaGloaXJvLm9oYmFAdG9zaGliYS5jby5qcF0gDQo+IFNlbnQ6IFR1ZXNkYXksIEp1bHkg
MjgsIDIwMDkgOTo1NyBBTQ0KPiBUbzogTUlMRVMgREFWSUQNCj4gQ2M6IFJpY2hhcmQgUHJ1c3M7
IGRoYyBXRzsgUmFscGggRHJvbXMNCj4gU3ViamVjdDogUmU6IFtkaGN3Z10gQ29tbWVudHMgb24g
ZHJhZnQtcHJ1c3MtZGhjcC1hdXRoLWRzbC0wNiBhbmQNCj4gZHJhZnQtYnJ6b3pvd3NraS1kaGNw
LWVhcC1hbmFseXNpcy0wMA0KPg0KPiBNSUxFUyBEQVZJRCB3cm90ZToNCj4gICANCj4+IEkgd2lz
aCB0byBhc2sgYSBxdWVzdGlvbiBmb3IgY2xhcmlmaWNhdGlvbi4NCj4+DQo+PiBJIHVuZGVyc3Rv
b2QgdGhlIHByb3Bvc2FsIGluIGRyYWZ0LXBydXNzLWF1dGgtZHNsIHdhcyB0aGF0IHRoZSBESENQ
DQo+PiBjbGllbnQgd2FzIGluIGZhY3QgYWxzbyB0aGUgRUFQIHN1cHBsaWNhbnQuIFRoZXJlIGlz
IG5vIEVBUG9MIG9yDQo+PiAgICAgDQo+IDgwMi4xeA0KPiAgIA0KPj4gZGV2aWNlLiBUaGUgREhD
UCByZWxheSBpcyBub3QgcGVyZm9ybWluZyBhIEVBUG9MLzgwMi4xeCB0byBESENQDQo+PiBjb252
ZXJzaW9uLg0KPj4NCj4+ICAgDQo+PiAgICAgDQo+IERIQ1AgcmVsYXkgaXMgcnVubmluZyBFQVAg
YWN0aW5nIGFzIGFuIEVBUCBhdXRoZW50aWNhdG9yLg0KPiAgIA0KPj4gV2hpbGUgdGhlIEVBUC9E
SENQIGNsaWVudCBvbiBIb21lIEdhdGV3YXkgYW5kIFNlcnZlciB3aWxsIG5lZWQgdG8gYmUNCj4+
IGF3YXJlL3N0YXRlZnVsIHdpdGggcmVzcGVjdCB0byBFQVAgd2h5IHdvdWxkIHRoaXMgZXh0ZW5k
IHRvIGEgREhDUA0KPj4gcmVsYXk/IElzIHRoaXMgbm90IHNpbWlsYXIgdG8gdGhlIGNhc2Ugb2Yg
RUFQLU1lc3NhZ2Ugb3ZlciBSQURJVVM/IEENCj4+IFJBRElVUyBwcm94eSBkb2VzIG5vdCBuZWVk
IHRvIGJlIGF3YXJlIG9mIHRoZSBkZXRhaWxzIG9mIHRoZQ0KPj4gICAgIA0KPiBFQVAtTWVzc2Fn
ZQ0KPiAgIA0KPj4gbm9yIGJlIGFibGUgdG8gZGVjb2RlIHRoZW0uDQo+PiAgIA0KPj4gICAgIA0K
PiBUaGUgZGlmZmVyZW5jZSBmcm9tIFJBRElVUyBwcm94eSBpcyB0aGF0IHRoZSBSQURJVVMgcHJv
eHkgaXMgbm90IHJ1bm5pbmcNCj4NCj4gRUFQLg0KPiAgIA0KPj4gSW4gdGhlIHByb3Bvc2VkIERI
Q1AgbWVzc2FnZSBleGNoYW5nZSBvZiBESVNDT1ZFUiwgREhDUEVBUCwgREhDUE9GRkVSLA0KPj4g
QUNLIEkgc2VlIG5vIHJlcXVpcmVtZW50IGZvciBhIHN0YXRlZnVsIERIQ1AgcmVsYXkgdG8gc3Vw
cG9ydCBESENQRUFQLg0KPj4gICANCj4+ICAgICANCj4gV2h5PyBBcyBJIGNvbW1lbnRlZCBhYm92
ZSwgREhDUCByZWxheSBpcyBydW5uaW5nIEVBUCBhY3RpbmcgYXMgYW4gRUFQIA0KPiBhdXRoZW50
aWNhdG9yLCB3aGljaCB3aWxsIHJlcXVpcmUgbG93ZXItbGF5ZXIgKGluIHRoaXMgY2FzZSBESENQ
IHJlbGF5KSANCj4gdG8gbWFpbnRhaW4gYSBzdGF0ZS4NCj4gICANCj4+IEFzIHdpdGggb3RoZXIg
REhDUCByZWxheWVkIG1lc3NhZ2VzIHRoZXJlIGlzIHN1ZmZpY2llbnQgaW5mb3JtYXRpb24gaW4N
Cj4+IHRoZSByZXNwb25zZSAoIGNvbnRhaW5zIGNoYWRkciAoSVB2NCkgb3IgcGVlciBhZGRyZXNz
IChJUHY2IHJlbGF5KSkNCj4+IHJlY2VpdmVkIGZyb20gdGhlIERIQ1Agc2VydmVyIHRvIGZvcndh
cmQgdGhpcyBtZXNzYWdlIHRvIHRoZSBIb21lDQo+PiBHYXRld2F5IChvcGVyYXRpbmcgYXMgREhD
UCBjbGllbnQgYW5kIEVBUCBzdXBwbGljYW50KS4NCj4+ICAgDQo+PiAgICAgDQo+IEluIEZpZ3Vy
ZSAzIG9mIGRyYWZ0LXBydXNzLCBESENQRUFQIG1lc3NhZ2UgZG9lcyBub3QgY29tZSBmcm9tIG9y
IGdvIHRvIA0KPiB0aGUgREhDUCBzZXJ2ZXIuDQo+IFRoZSBESENQIHJlbGF5IGluIGRyYWZ0LXBy
dXNzIGlzIG5vdCByZWxheWluZyBESENQRUFQIG1lc3NhZ2UgYmV0d2VlbiANCj4gREhDUCBjbGll
bnQgYW5kIERIQ1Agc2VydmVyLg0KPg0KPiBZb3NoaWhpcm8gT2hiYQ0KPg0KPiAgIA0KPj4gZA0K
Pj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBkaGN3Zy1ib3VuY2Vz
QGlldGYub3JnIFttYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmDQo+PiBP
ZiBZb3NoaWhpcm8gT2hiYQ0KPj4gU2VudDogVHVlc2RheSwgSnVseSAyOCwgMjAwOSAxOjAwIEFN
DQo+PiBUbzogUmljaGFyZCBQcnVzcw0KPj4gQ2M6IGRoYyBXRzsgUmFscGggRHJvbXMNCj4+IFN1
YmplY3Q6IFJlOiBbZGhjd2ddIENvbW1lbnRzIG9uIGRyYWZ0LXBydXNzLWRoY3AtYXV0aC1kc2wt
MDYgYW5kDQo+PiBkcmFmdC1icnpvem93c2tpLWRoY3AtZWFwLWFuYWx5c2lzLTAwDQo+Pg0KPj4g
UmljaGFyZCBQcnVzcyB3cm90ZToNCj4+ICAgDQo+PiAgICAgDQo+Pj4gQXMgSSBzYWlkIHRvIFJh
bHBoIGVhcmxpZXIgd2UgdHJhY2sgdHJhbnNwb3J0IGFuZCBwb3J0IGFzc29jaWF0aW9ucyANCj4+
PiBhbHJlYWR5IHRvIGZhY2lsaXRhdGUgdW5udW1iZXJlZCBpbnRlcmZhY2VzLCBzbyB0aGUgcXVl
c3Rpb24gd2FzIHdoYXQNCj4+PiAgICAgICANCj4NCj4gICANCj4+PiBzdGF0ZSBiZXlvbmQgdGhh
dC4NCj4+PiAgICAgDQo+Pj4gICAgICAgDQo+PiBCZXlvbmQgdGhhdCBlYWNoIEVBUCBjb252ZXJz
YXRpb24gbmVlZHMgdG8gYmUgbWFwcGVkIHRvIGEgZGlzdGluY3QgDQo+PiB0cmFuc3BvcnQgYW5k
IHBvcnQgYXNzb2NpYXRpb24sIHdoaWNoIHdpbGwgcmVxdWlyZSBhIHN0YXRlIG1haW50YWluZWQN
Cj4+ICAgICANCj4gYnkNCj4gICANCj4+IERIQ1AgcmVsYXkuDQo+Pg0KPj4gWW9zaGloaXJvIE9o
YmENCj4+DQo+PiAgIA0KPj4gICAgIA0KPj4+IE9uIDI3LzA3LzIwMDksIGF0IDY6NDIgUE0sIFlv
c2hpaGlybyBPaGJhIHdyb3RlOg0KPj4+DQo+Pj4gICAgIA0KPj4+ICAgICAgIA0KPj4+PiBJbiBn
ZW5lcmFsLCBhIHN0YXRlIG9uIHRoZSBsb2dpY2FsIGNvbm5lY3Rpb24gYmV0d2VlbiB0aGUgcGVl
ciBhbmQgDQo+Pj4+IGF1dGhlbnRpY2F0b3IgbmVlZHMgdG8gYmUgbWFpbnRhaW5lZCBieSBhbnkg
RUFQIGxvd2VyLWxheWVyIGZvciBlYWNoDQo+Pj4+ICAgICAgICAgDQo+DQo+ICAgDQo+Pj4+IEVB
UCBjb252ZXJzYXRpb24uIFN1Y2ggYSBzdGF0ZSBhdCBsZWFzdCBpbmNsdWRlcyB0cmFuc3BvcnQg
YWRkcmVzc2VzDQo+Pj4+ICAgICAgICAgDQo+DQo+ICAgDQo+Pj4+IGFuZC9vciBwb3J0IG51bWJl
cnMgYW5kIHRoZXkgYXJlIG5vdCBjYXJyaWVkIGluIEVBUCBtZXNzYWdlLg0KPj4+Pg0KPj4+PiBZ
b3NoaWhpcm8gT2hiYQ0KPj4+Pg0KPj4+Pg0KPj4+PiBSaWNoYXJkIFBydXNzIHdyb3RlOg0KPj4+
PiAgICAgICANCj4+Pj4gICAgICAgICANCj4+Pj4+IE9uIDI3LzA3LzIwMDksIGF0IDU6NTkgUE0s
IFlvc2hpaGlybyBPaGJhIHdyb3RlOg0KPj4+Pj4NCj4+Pj4+ICAgICAgICAgDQo+Pj4+PiAgICAg
ICAgICAgDQo+Pj4+Pj4gUmljaGFyZCBQcnVzcyB3cm90ZToNCj4+Pj4+PiAgICAgICAgICAgDQo+
Pj4+Pj4gICAgICAgICAgICAgDQo+Pj4+Pj4+IE9uIDI3LzA3LzIwMDksIGF0IDU6NTAgUE0sIFlv
c2hpaGlybyBPaGJhIHdyb3RlOg0KPj4+Pj4+Pg0KPj4+Pj4+PiAgICAgICAgICAgICANCj4+Pj4+
Pj4gICAgICAgICAgICAgICANCj4+Pj4+Pj4+IFJpY2hhcmQgUHJ1c3Mgd3JvdGU6DQo+Pj4+Pj4+
PiAgICAgICAgICAgICAgIA0KPj4+Pj4+Pj4gICAgICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+IFdl
bGwgUmFscGgsICBhcyB5b3Ugc2F5IHNvbWV0aGluZyBlbHNlIGlzIGhvbGRpbmcgdGhlIHN0YXRl
IGFuZA0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgIA0KPg0KPiAgIA0KPj4+Pj4+Pj4+IHRo
ZSByZWxheSBhZ2VudCBpcyBzaW1wbHkgaGFuZGluZyB0aGUgRUFQIG1lc3NhZ2VzIHRvIHRoZSBB
QUEgIA0KPj4+Pj4+Pj4+IHNlcnZpY2UgaW4gdGhlIHJlbGF5IGZ1bmN0aW9uLi4uIHNvIG5vIHRo
ZSBxdWVzdGlvbiBzdGlsbCBtYWtlcw0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgIA0KPg0K
PiAgIA0KPj4+Pj4+Pj4+IG5vIHNlbnNlIHRvIG1lLg0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAg
ICANCj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+IFRoaXMgaXMgYW4gaW5j
b3JyZWN0IHN0YXRlbWVudC4gREhDUCByZWxheSBhY3RpbmcgRUFQIA0KPj4+Pj4+Pj4gYXV0aGVu
dGljYXRvciBpcyBub3Qgc2ltcGx5IGhhbmRpbmcgRUFQIG1lc3NhZ2VzIHRvIHRoZSBBQUEsIGl0
IA0KPj4+Pj4+Pj4gbmVlZHMgdG8gbWFpbnRhaW4gYSBzdGF0ZSBpbmNsdWRpbmcgYSByZXRyYW5z
bWlzc2lvbiB0aW1lciB0byANCj4+Pj4+Pj4+IHJldHJhbnNtaXQgb3V0c3RhbmRpbmcgRUFQLVJl
cXVlc3QgbWVzc2FnZSAoY2YuIFJGQyA0MTM3KS4NCj4+Pj4+Pj4+ICAgICAgICAgICAgICAgDQo+
Pj4+Pj4+PiAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+IE5vIG1hdGUgdGhpcyBpcyB0aGUgcGFy
dCB5b3UgcHJvYmFibHkgbWlzc2VkLCBFQVAgaXMgZG9pbmcgdGhhdCANCj4+Pj4+Pj4gYW5kIGl0
IGlzIGEgc2VwYXJhdGUgZnVuY3Rpb24gcmVnYXJkbGVzcyBvZiB3aGF0IGl0IGlzIGJlaW5nIA0K
Pj4+Pj4+PiBjYXJyaWVkIG9uICwgUFBQLCBFdGhlcm5ldCwgREhDUCBoZXJlIGlzIGp1c3QgdHJh
bnNwb3J0Lg0KPj4+Pj4+PiAgICAgICAgICAgICANCj4+Pj4+Pj4gICAgICAgICAgICAgICANCj4+
Pj4+PiBBbGwgRUFQIHRyYW5zcG9ydCBwcm90b2NvbHMgdGhhdCBJIGtub3cgb2YsIGluY2x1ZGlu
ZyB0aGUgb25lcyB5b3UNCj4+Pj4+PiAgICAgICAgICAgICANCj4NCj4gICANCj4+Pj4+PiBsaXN0
ZWQgYWJvdmUgcmVxdWlyZXMgdG8gbWFpbnRhaW4gYSBzdGF0ZSB0byBjYXJyeSBFQVAgbWVzc2Fn
ZS4gIA0KPj4+Pj4+IFRoZXJlIGlzIG5vIGV4Y2VwdGlvbi4NCj4+Pj4+PiAgICAgICAgICAgDQo+
Pj4+Pj4gICAgICAgICAgICAgDQo+Pj4+PiBXaGF0IHN0YXRlPw0KPj4+Pj4NCj4+Pj4+ICAgICAg
ICAgDQo+Pj4+PiAgICAgICAgICAgDQo+Pj4+Pj4gWW9zaGloaXJvIE9oYmENCj4+Pj4+Pg0KPj4+
Pj4+DQo+Pj4+Pj4gICAgICAgICAgIA0KPj4+Pj4+ICAgICAgICAgICAgIA0KPj4+Pj4+PiAtIFJp
Yw0KPj4+Pj4+Pg0KPj4+Pj4+Pg0KPj4+Pj4+PiAgICAgICAgICAgICANCj4+Pj4+Pj4gICAgICAg
ICAgICAgICANCj4+Pj4+Pj4+IFlvc2hpaGlybyBPaGJhDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gICAg
ICAgICAgICAgICANCj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+PiBUaGUgdGhp
bmcgdGhhdCBtYWtlcyBubyBzZW5zZSBpcyB0aGUgYXNzZXJ0aW9uIHRoYXQgdGhlIHJlbGF5IA0K
Pj4+Pj4+Pj4+IGFnZW50IHN1ZGRlbmx5IG5lZWRzIHRvIGhvbGQgc3RhdGUsIGJleW9uZCB3aGF0
IGl0IGFscmVhZHkgZG9lcw0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgIA0KPg0KPiAgIA0K
Pj4+Pj4+Pj4+IHRvIGhhbmRsZSBpcCB1bm51bWJlcmVkIGludGVyZmFjZXMsDQo+Pj4+Pj4+Pj4g
UmljDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBPbiAyNy8wNy8yMDA5LCBhdCA1OjI2IFBNLCBSYWxw
aCBEcm9tcyB3cm90ZToNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICANCj4+
Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4gUmljIC0gdGhlIHF1ZXN0aW9u
IHNlZW1zIHNlbnNpYmxlIHRvIG1lLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBJIHdvdWxkIGNv
bnNpZGVyIGVuZm9yY2luZyB0aGUgYWRkcmVzcyBhc3NpZ25tZW50IGFzIGENCj4+Pj4+Pj4+Pj4g
ICAgICAgICAgICAgICAgICAgICANCj4gc2VwYXJhdGUNCj4gICANCj4+Pj4+Pj4+Pj4gICAgICAg
ICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgDQo+PiAgIA0KPj4g
ICAgIA0KPj4+Pj4+Pj4+PiBmdW5jdGlvbiBvZiB0aGUgYm94IHRoYXQgaGFwcGVucyB0byBob3Vz
ZSB0aGUgREhDUCByZWxheSBhZ2VudA0KPj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgIA0K
Pg0KPiAgIA0KPj4+Pj4+Pj4+PiBmdW5jdGlvbi4gIFRoYXQgaXMsIHRoZSByZWxheSBhZ2VudCBl
eHRyYWN0cyB0aGUgYXNzaWduZWQgDQo+Pj4+Pj4+Pj4+IGFkZHJlc3MgZnJvbSB0aGUgREhDUEFD
SyBhbmQgaGFuZHMgaXQgdG8gdGhlIGFkZHJlc3MgDQo+Pj4+Pj4+Pj4+IGVuZm9yY2VtZW50IGZ1
bmN0aW9uLiAgVGhlcmVmb3JlLCB0aGUgcmVsYXkgYWdlbnQgZnVuY3Rpb24gaXMgDQo+Pj4+Pj4+
Pj4+IG5vdCBrZWVwaW5nIGFueSBzdGF0ZS4gIFRoZSBhZGRyZXNzIGVuZm9yY2VtZW50IGZ1bmN0
aW9uIGNvdWxkDQo+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgDQo+DQo+ICAgDQo+Pj4+
Pj4+Pj4+IGp1c3QgYXMgZWFzaWx5IGdldCB0aGF0IGFkZHJlc3MgYXNzaWdubWVudCBpbmZvcm1h
dGlvbiBmcm9tIA0KPj4+Pj4+Pj4+PiBzb21lIG90aGVyIHNvdXJjZSBsaWtlIENMSSBvciBTTk1Q
Lg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBUaGUgb3JpZ2luYWwgcHVycG9zZSBvZiB0aGUgcmVs
YXkgYWdlbnQgb3B0aW9uIHdhcyB0byBob2xkIA0KPj4+Pj4+Pj4+PiBzdGF0ZSBmb3IgdGhlIHJl
bGF5IGFnZW50LiAgV2UndmUgdHJpZWQgdG8gbWFpbnRhaW4gdGhhdCANCj4+Pj4+Pj4+Pj4gc3Rh
dGVsZXNzIG9wZXJhdGlvbiAoYnV0IEknbSBub3Qgc3VyZSB3ZSd2ZSBzdHJpY3RseSBlbmZvcmNl
ZCANCj4+Pj4+Pj4+Pj4gdGhlIHJ1bGUpIHdpdGggdGhlIGRlZmluaXRpb24gb2Ygc3Vic2VxdWVu
dCByZWxheSBhZ2VudA0KPj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4g
ICAgICAgICAgICAgICAgICAgICANCj4+IG9wdGlvbnMuDQo+PiAgIA0KPj4gICAgIA0KPj4+Pj4+
Pj4+PiAtIFJhbHBoDQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IE9uIEp1bCAyNywgMjAwOSwgYXQg
OTowNCBBTSA3LzI3LzA5LCBSaWNoYXJkIFBydXNzIHdyb3RlOg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4+PiAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAN
Cj4+Pj4+Pj4+Pj4+IE9uIDI3LzA3LzIwMDksIGF0IDQ6NTUgUE0sIFlvc2hpaGlybyBPaGJhIHdy
b3RlOg0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+
Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4gUmljaGFyZCBQcnVz
cyB3cm90ZToNCj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+
Pj4gICAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4+IFJlbGF5J3MgaW4gdGhl
IGJyb2FkYmFuZCBhcmNoaXRlY3R1cmUgaGF2ZSB0byBiZSBzdGF0ZWZ1bA0KPj4+Pj4+Pj4+Pj4+
PiAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KPiB0bw0KPiAgIA0KPj4+Pj4+Pj4+Pj4+PiAg
ICAgICAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAg
ICAgICAgICANCj4+ICAgDQo+PiAgICAgDQo+Pj4+Pj4+Pj4+Pj4+IGVuZm9yY2UgREhDUCBhZGRy
ZXNzIGFzc2lnbm1lbnQsIHNvIGl0IGlzIG5vdCBhIGNoYW5nZSB0byANCj4+Pj4+Pj4+Pj4+Pj4g
dGhlIGV4aXN0aW5nIGFyY2hpdGVjdHVyZS4NCj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAg
ICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+
Pj4+Pj4+Pj4gQXMgZmFyIGFzIEkgdW5kZXJzdGFuZCwgZW5mb3JjaW5nIERIQ1AgYWRkcmVzcyBh
c3NpZ25tZW50IGlzDQo+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgDQo+DQo+
ICAgDQo+Pj4+Pj4+Pj4+Pj4gbmVlZGVkICphZnRlciogREhDUCBleGNoYW5nZXMgYXJlIGRvbmUs
IGFuZCB0aGVyZWZvcmUgdGhlIA0KPj4+Pj4+Pj4+Pj4+IHN0YXRlIGlzIG1haW50YWluZWQgb3V0
c2lkZSB0aGUgY29udGV4dCBvZiBESENQLCB3aGljaCBJIA0KPj4+Pj4+Pj4+Pj4+IGRvbid0IGNh
cmUuICBNeSBjb21tZW50IHdhcyBpZiBESENQIHJlbGF5IG5lZWRzIHRvIGJlIA0KPj4+Pj4+Pj4+
Pj4+IHN0YXRlZnVsIGluIHRoZSBtaWRkbGUgb2YgREhDUCBleGNoYW5nZXMgdG8gY2FycnkgRUFQ
Lg0KPj4+Pj4+Pj4+Pj4+ID5Gcm9tIERIQ1AgcG9pbnQgb2YgdmlldywgaXQgc2VlbXMgdG8gYmUg
YSBtYWpvciBkZXNpZ24NCj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+
Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgDQo+PiBjaGFuZ2UgDQo+PiAgIA0KPj4g
ICAgIA0KPj4+Pj4+Pj4+Pj4+IHRvIERIQ1AuDQo+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAg
ICAgICAgIA0KPj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+
Pj4gRG8geW91IGFjdHVhbGx5IGhhdmUgYW4gaW1wbGVtZW50YXRpb24gb2YgYnJvYWRiYW5kIERI
Q1ANCj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICANCj4gcmVsYXkNCj4gICANCj4+
Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAg
ICAgICAgICAgDQo+PiAgIA0KPj4gICAgIA0KPj4+Pj4+Pj4+Pj4gYmVjYXVzZSAgd2hhdCB5b3Ug
YXJlIHRhbGtpbmcgbWFrZXMgdmVyeSBsaXR0bGUgc2Vuc2U/DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4+Pj4gLSBSaWMNCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gICAgICAg
ICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICANCj4+Pj4+
Pj4+Pj4+PiBSZWdhcmRzLA0KPj4+Pj4+Pj4+Pj4+IFlvc2hpaGlybyBPaGJhDQo+Pj4+Pj4+Pj4+
Pj4NCj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4gICAg
ICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4+IC0gUmljDQo+Pj4+Pj4+Pj4+Pj4+
DQo+Pj4+Pj4+Pj4+Pj4+IE9uIDI3LzA3LzIwMDksIGF0IDg6MTMgQU0sIFlvc2hpaGlybyBPaGJh
IHdyb3RlOg0KPj4+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAg
ICAgICANCj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+
Pj4+Pj4+IEkgaGF2ZSByZWFkIGJvdGggZG9jdW1lbnRzLiBUaGFua3MgZm9yIHRoZSBhdXRob3Jz
IGZvcg0KPj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KPiBib3Ro
DQo+ICAgDQo+Pj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KPj4+Pj4+
Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KPj4gICANCj4+ICAgICANCj4+
Pj4+Pj4+Pj4+Pj4+IGRvY3VtZW50cyBwcm92aWRpbmcgdGVjaGluaWNhbCBkZXRhaWxzLg0KPj4+
Pj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4+IEhvd2V2ZXIsIEkgc3RpbGwgaGF2ZSBhbiBpc3N1
ZSB3aXRoIGNhcnJ5aW5nIEVBUCBvdmVyDQo+Pj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgDQo+IERIQ1AuDQo+ICAgDQo+Pj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KPj4gICANCj4+ICAgICANCj4+Pj4+Pj4+Pj4+Pj4+IFRoZSBpc3N1ZSBpcyBiYXNpY2FsbHkg
YSBjb25mbGljdCBiZXR3ZWVuIHN0YXRlZnVsbG5lc3Mgb2YNCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICANCj4NCj4gICANCj4+Pj4+Pj4+Pj4+Pj4+IEVBUCBhbmQg
c3RhdGVsZXNzbmVzcyBvZiBESENQIHJlbGF5IGFnZW50Lg0KPj4+Pj4+Pj4+Pj4+Pj4NCj4+Pj4+
Pj4+Pj4+Pj4+IEFzIGZhciBhcyBJIHVuZGVyc3RhbmQsIERIQ1AgcmVsYXkgYWdlbnQgZG9lcyBu
b3QgbWFpbnRhaW4NCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAN
Cj4NCj4gICANCj4+Pj4+Pj4+Pj4+Pj4+IGEgc3RhdGUuIE9uIHRoZSBvdGhlciBoYW5kLCBFQVAg
cmVxdWlyZXMgcGVlciBhbmQgDQo+Pj4+Pj4+Pj4+Pj4+PiBhdXRoZW50aWNhdG9yIHRvIG1haW50
YWluIGEgc3RhdGUgKHNlZSBSRkMgNDEzNykuIFdoZW4NCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICANCj4gREhDUA0KPiAgIA0KPj4+Pj4+Pj4+Pj4+Pj4gICAgICAg
ICAgICAgICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICANCj4+ICAgDQo+PiAgICAgDQo+Pj4+Pj4+Pj4+Pj4+PiByZWxheSBhZ2VudCBhY3Rz
IEVBUCBhdXRoZW50aWNhdG9yLCB0aGVuIHRoZSByZWxheSBhZ2VudCANCj4+Pj4+Pj4+Pj4+Pj4+
IHdpbGwgYmUgbm8gbG9uZ2VyIGEgc3RhdGVsZXNzIERIQ1AgZW50aXR5LiBJIHRoaW5rIHRoaXMg
aXMNCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCj4NCj4gICAN
Cj4+Pj4+Pj4+Pj4+Pj4+IG5vdCBkaXNjdXNzZWQgaW4gZGhjcC1lYXAtYW5hbHlzaXMgZHJhZnQu
IElzIHRoaXMgYW4gDQo+Pj4+Pj4+Pj4+Pj4+PiBhY2NlcHRhYmxlIGRlc2lnbiBjaGFuZ2UgZm9y
IERIQ1A/ICBPciBwbGVhc2UgY29ycmVjdCBtZQ0KPj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIA0KPiBpZg0KPiAgIA0KPj4+Pj4+Pj4+Pj4+Pj4gICAgICAgICAgICAg
ICAgICAgICAgICAgICANCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICANCj4+ICAgDQo+PiAgICAgDQo+Pj4+Pj4+Pj4+Pj4+PiBJIGFtIHdyb25nLg0KPj4+Pj4+Pj4+
Pj4+Pj4NCj4+Pj4+Pj4+Pj4+Pj4+IFJlZ2FyZHMsDQo+Pj4+Pj4+Pj4+Pj4+PiBZb3NoaWhpcm8g
T2hiYQ0KPj4+Pj4+Pj4+Pj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+Pj4+Pj4+Pj4+Pj4+IGRoY3dnIG1haWxpbmcgbGlzdA0KPj4+Pj4+Pj4+
Pj4+Pj4gZGhjd2dAaWV0Zi5vcmcNCj4+Pj4+Pj4+Pj4+Pj4+IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vZGhjd2cNCj4+Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgDQo+Pj4+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQo+
Pj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+Pj4+PiAgICAg
ICAgICAgICAgICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+Pj4gX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+Pj4+Pj4+IGRoY3dnIG1haWxpbmcgbGlz
dA0KPj4+Pj4+Pj4+Pj4gZGhjd2dAaWV0Zi5vcmcNCj4+Pj4+Pj4+Pj4+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCj4+Pj4+Pj4+Pj4+ICAgICAgICAgICAgICAg
ICAgICAgDQo+Pj4+Pj4+Pj4+PiAgICAgICAgICAgICAgICAgICAgICAgDQo+Pj4+Pj4+Pj4gICAg
ICAgICAgICAgICAgIA0KPj4+Pj4+Pj4+ICAgICAgICAgICAgICAgICAgIA0KPj4+Pj4+PiAgICAg
ICAgICAgICANCj4+Pj4+Pj4gICAgICAgICAgICAgICANCj4+Pj4+ICAgICAgICAgDQo+Pj4+PiAg
ICAgICAgICAgDQo+Pj4+ICAgICAgIA0KPj4+PiAgICAgICAgIA0KPj4+ICAgICANCj4+PiAgICAg
ICANCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
PiBkaGN3ZyBtYWlsaW5nIGxpc3QNCj4+IGRoY3dnQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo+Pg0KPj4NCj4+ICAgDQo+PiAgICAgDQo+
DQo+DQo+DQo+ICAgDQoNCg==

From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 18:26:09 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D63B73A69A3 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-KkI7qxniYZ for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:26:09 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 656483A6990 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 18:26:06 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6T1PIWW027232; Wed, 29 Jul 2009 10:25:18 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6T1PICn023936; Wed, 29 Jul 2009 10:25:18 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id LAA23935; Wed, 29 Jul 2009 10:25:18 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6T1PIEI020301; Wed, 29 Jul 2009 10:25:18 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6T1PGUq029594; Wed, 29 Jul 2009 10:25:16 +0900 (JST)
Received: from [133.196.16.81] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNI003V6RY3N3H0@mail.po.toshiba.co.jp>; Wed, 29 Jul 2009 10:25:16 +0900 (JST)
Date: Tue, 28 Jul 2009 21:25:15 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <8FB19091-639D-4A2C-B9C0-87237199F65C@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6FA4FB.5050307@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> <4A6F7E01.20403@toshiba.co.jp> <8FB19091-639D-4A2C-B9C0-87237199F65C@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 01:26:09 -0000

Richard Pruss wrote:
>
>>
>> As far as I understand, what you often mention regarding mapping 
>> attributes from AAA *without EAP* is still possible based on 
>> caching.  As Ted mentioned earlier, this kind of caching does not 
>> necessarily require the DHCP relay (or DHCP proxy in your term) to be 
>> stateful entity in terms of DHCP operation.  However, *with EAP*, the 
>> DHCP relay will need to be stateful as I  and Alper mentioned 
>> earlier. It seems that DHC WG people are sensible about such a 
>> change.  I hope I explained my technical point clear enough. If not, 
>> let's discuss further.
>
> Actually as I have mentioned twice, port tracking state you pointed to 
> long predates DHCP with EAP as when the BRAS ports are unnumbered a 
> single IP address is used as the interface address for thousands of 
> interfaces, you need to know that state to be able to forward the DHCP 
> packets back down to the correct port.  So no as I have being trying 
> to point out this is no change, these are session aggregation devices, 
> their roll is to be stateful for each session.  Regardless of if the 
> state is implemented inside or outside of the DHCP relay function the 
> BRAS is certainly tracking that state and a whole lot more.

Let me clarify. What you mentioned twice is what I am mentioning as 
doable as cache.  My point is, if DHCP starts carrying EAP, your DHCP 
relay will need to create a state within DHCP relay and the state needs 
to exist until an EAP conversation completes in order to appropriately 
map the EAP conversation to a transport entity, which I think is more 
than a cache. My question is: is  this kind of change beyond cache 
acceptable to the DHC WG?  Of course I may be misunderstanding 
something. In that case, I would appreciate if someone can provide much 
more details on interactions between DHCP relay and AAA in DSL environment.

Regards,
Yoshihiro Ohba

>
> - Ric
>
>
>>
>> Yoshihiro Ohba
>>
>>>
>>> It was because DHCP does so much already in the BRAS/NAS that the 
>>> adding a few attributes for authentication
>>> to add to the quality of the decision is a logical choice.
>>>
>>> - Ric
>>>
>>> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>>>
>>>> Ric, I get that you are frustrated by this discussion, but for us 
>>>> innocent bystanders, it would be helpful if you could respond 
>>>> factually, rather than expressing your frustration. Please remember 
>>>> that your grasp of what you are trying to do is much greater than 
>>>> ours, since we aren't trying to do it.   If you think it's a bad 
>>>> question, I'd like to see you say why.
>>>>
>>>
>>>
>>>
>>
>
>
>


From ric@cisco.com  Tue Jul 28 18:39:05 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F5EA3A6939 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.676
X-Spam-Level: 
X-Spam-Status: No, score=-3.676 tagged_above=-999 required=5 tests=[AWL=-1.077, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIuaMMqYpxsO for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:39:04 -0700 (PDT)
Received: from syd-iport-2.cisco.com (syd-iport-2.cisco.com [64.104.193.197]) by core3.amsl.com (Postfix) with ESMTP id 5B1A43A6972 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 18:38:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAF9Eb0oKS+ej/2dsb2JhbAC8XYgnkCAFhBCBTQ
X-IronPort-AV: E=Sophos;i="4.43,285,1246838400"; d="scan'208";a="55872386"
Received: from hkg-dkim-2.cisco.com ([10.75.231.163]) by syd-iport-2.cisco.com with ESMTP; 29 Jul 2009 01:38:51 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n6T1coPd021327;  Wed, 29 Jul 2009 09:38:50 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6T1cn70013090; Wed, 29 Jul 2009 01:38:50 GMT
Received: from xfe-hkg-412.apac.cisco.com ([64.104.123.71]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 09:38:38 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 09:38:37 +0800
Message-Id: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6FA4FB.5050307@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 11:38:34 +1000
X-OriginalArrivalTime: 29 Jul 2009 01:38:38.0235 (UTC) FILETIME=[4B87FEB0:01CA0FED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4384; t=1248831530; x=1249695530; c=relaxed/simple; s=hkgdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=cVDrNs+m0sd5Ln2Oz4ToIOFtPsLOlh3ZnLI6KmlUAbo=; b=S5z18gtxhIIFR6FE5e6ngoXChcjiuNwa87dFdar9RflLy/+NLCNNjYbeJr Q2PC0jO1skiNcKojmpGXR8HCCVarwDvSYiNtajEWw0ZYyVaTpgohTEQ7KasF /JG6tySzr+jtft3wgSKa5iJKl9M2SfiWlovbl31Z0M5IvfoDQRQNk=;
Authentication-Results: hkg-dkim-2; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 01:39:05 -0000

References: <4A6CD501.7030704@toshiba.co.jp> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> <4A6F7E01.20403@toshiba.co.jp> <8FB19091-639D-4A2C-B9C0-87237199F65C@cisco.c
 om> <4A6FA4FB.5050307@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
Return-Path: ric@cisco.com
X-OriginalArrivalTime: 29 Jul 2009 01:38:37.0644 (UTC) FILETIME=[4B2DD0C0:01CA0FED]


On 29/07/2009, at 11:25 AM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>>
>>>
>>> As far as I understand, what you often mention regarding mapping  
>>> attributes from AAA *without EAP* is still possible based on  
>>> caching.  As Ted mentioned earlier, this kind of caching does not  
>>> necessarily require the DHCP relay (or DHCP proxy in your term) to  
>>> be stateful entity in terms of DHCP operation.  However, *with  
>>> EAP*, the DHCP relay will need to be stateful as I  and Alper  
>>> mentioned earlier. It seems that DHC WG people are sensible about  
>>> such a change.  I hope I explained my technical point clear  
>>> enough. If not, let's discuss further.
>>
>> Actually as I have mentioned twice, port tracking state you pointed  
>> to long predates DHCP with EAP as when the BRAS ports are  
>> unnumbered a single IP address is used as the interface address for  
>> thousands of interfaces, you need to know that state to be able to  
>> forward the DHCP packets back down to the correct port.  So no as I  
>> have being trying to point out this is no change, these are session  
>> aggregation devices, their roll is to be stateful for each  
>> session.  Regardless of if the state is implemented inside or  
>> outside of the DHCP relay function the BRAS is certainly tracking  
>> that state and a whole lot more.
>
> Let me clarify. What you mentioned twice is what I am mentioning as  
> doable as cache.  My point is, if DHCP starts carrying EAP, your  
> DHCP relay will need to create a state within DHCP relay and the  
> state needs to exist until an EAP conversation completes in order to  
> appropriately map the EAP conversation to a transport entity, which  
> I think is more than a cache. My question is: is  this kind of  
> change beyond cache acceptable to the DHC WG?  Of course I may be  
> misunderstanding something. In that case, I would appreciate if  
> someone can provide much more details on interactions between DHCP  
> relay and AAA in DSL environment.

Which begs the question what is this state beyond the cached port  
information are you talking about, Alper mentioned some future  
possible keying when one distributes keys to DHCP RFC 3118 will  
probably be interesting in the relay but I have heard about no  
additional state required now for this.

- Ric



>
> Regards,
> Yoshihiro Ohba
>
>>
>> - Ric
>>
>>
>>>
>>> Yoshihiro Ohba
>>>
>>>>
>>>> It was because DHCP does so much already in the BRAS/NAS that the  
>>>> adding a few attributes for authentication
>>>> to add to the quality of the decision is a logical choice.
>>>>
>>>> - Ric
>>>>
>>>> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>>>>
>>>>> Ric, I get that you are frustrated by this discussion, but for  
>>>>> us innocent bystanders, it would be helpful if you could respond  
>>>>> factually, rather than expressing your frustration. Please  
>>>>> remember that your grasp of what you are trying to do is much  
>>>>> greater than ours, since we aren't trying to do it.   If you  
>>>>> think it's a bad question, I'd like to see you say why.
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>


From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 18:47:44 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D47DD3A6C35 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qMW91cDPh9jb for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 18:47:43 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 9C9B33A696A for <dhcwg@ietf.org>; Tue, 28 Jul 2009 18:47:43 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6T1lRpA006563; Wed, 29 Jul 2009 10:47:27 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6T1lRFd012863; Wed, 29 Jul 2009 10:47:27 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id LAA12854; Wed, 29 Jul 2009 10:47:27 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6T1lQGK007832; Wed, 29 Jul 2009 10:47:27 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6T1lG89020563; Wed, 29 Jul 2009 10:47:24 +0900 (JST)
Received: from [133.196.16.81] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNI003NDSYWN7J0@mail.po.toshiba.co.jp>; Wed, 29 Jul 2009 10:47:20 +0900 (JST)
Date: Tue, 28 Jul 2009 21:47:19 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6FAA27.40809@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 01:47:44 -0000

Richard Pruss wrote:
> References: <4A6CD501.7030704@toshiba.co.jp> 
> <C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com> 
> <4A6D4F53.2060608@toshiba.co.jp> 
> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> 
> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> 
> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> 
> <4A6D5C54.6050904@toshiba.co.jp> 
> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> 
> <4A6D5E5D.8070707@toshiba.co.jp> 
> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> 
> <4A6D685A.7000406@toshiba.co.jp> 
> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> 
> <4A6DC7E3.2010001@toshiba.co.jp> 
> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> 
> <4A6E45DC.5030103@toshiba.co.jp> 
> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> 
> <4A6EB8E6.4070800@toshiba.co.jp> 
> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> 
> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> 
> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> 
> <4A6F7E01.20403@toshiba.co.jp> 
> <8FB19091-639D-4A2C-B9C0-87237199F65C@cisco.!
> com> <4A6FA4FB.5050307@toshiba.co.jp>
> X-Mailer: Apple Mail (2.935.3)
> Return-Path: ric@cisco.com
> X-OriginalArrivalTime: 29 Jul 2009 01:38:37.0644 (UTC) 
> FILETIME=[4B2DD0C0:01CA0FED]
>
>
> On 29/07/2009, at 11:25 AM, Yoshihiro Ohba wrote:
>
>> Richard Pruss wrote:
>>>
>>>>
>>>> As far as I understand, what you often mention regarding mapping 
>>>> attributes from AAA *without EAP* is still possible based on 
>>>> caching.  As Ted mentioned earlier, this kind of caching does not 
>>>> necessarily require the DHCP relay (or DHCP proxy in your term) to 
>>>> be stateful entity in terms of DHCP operation.  However, *with 
>>>> EAP*, the DHCP relay will need to be stateful as I  and Alper 
>>>> mentioned earlier. It seems that DHC WG people are sensible about 
>>>> such a change.  I hope I explained my technical point clear enough. 
>>>> If not, let's discuss further.
>>>
>>> Actually as I have mentioned twice, port tracking state you pointed 
>>> to long predates DHCP with EAP as when the BRAS ports are unnumbered 
>>> a single IP address is used as the interface address for thousands 
>>> of interfaces, you need to know that state to be able to forward the 
>>> DHCP packets back down to the correct port.  So no as I have being 
>>> trying to point out this is no change, these are session aggregation 
>>> devices, their roll is to be stateful for each session.  Regardless 
>>> of if the state is implemented inside or outside of the DHCP relay 
>>> function the BRAS is certainly tracking that state and a whole lot 
>>> more.
>>
>> Let me clarify. What you mentioned twice is what I am mentioning as 
>> doable as cache.  My point is, if DHCP starts carrying EAP, your DHCP 
>> relay will need to create a state within DHCP relay and the state 
>> needs to exist until an EAP conversation completes in order to 
>> appropriately map the EAP conversation to a transport entity, which I 
>> think is more than a cache. My question is: is  this kind of change 
>> beyond cache acceptable to the DHC WG?  Of course I may be 
>> misunderstanding something. In that case, I would appreciate if 
>> someone can provide much more details on interactions between DHCP 
>> relay and AAA in DSL environment.
>
> Which begs the question what is this state beyond the cached port 
> information are you talking about, Alper mentioned some future 
> possible keying when one distributes keys to DHCP RFC 3118 will 
> probably be interesting in the relay but I have heard about no 
> additional state required now for this.

In addition, your DHCP relay will need to have a state for EAP 
authenticator state machine.

Yoshihiro Ohba

>
> - Ric
>
>
>
>>
>> Regards,
>> Yoshihiro Ohba
>>
>>>
>>> - Ric
>>>
>>>
>>>>
>>>> Yoshihiro Ohba
>>>>
>>>>>
>>>>> It was because DHCP does so much already in the BRAS/NAS that the 
>>>>> adding a few attributes for authentication
>>>>> to add to the quality of the decision is a logical choice.
>>>>>
>>>>> - Ric
>>>>>
>>>>> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>>>>>
>>>>>> Ric, I get that you are frustrated by this discussion, but for us 
>>>>>> innocent bystanders, it would be helpful if you could respond 
>>>>>> factually, rather than expressing your frustration. Please 
>>>>>> remember that your grasp of what you are trying to do is much 
>>>>>> greater than ours, since we aren't trying to do it.   If you 
>>>>>> think it's a bad question, I'd like to see you say why.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>


From ric@cisco.com  Tue Jul 28 19:36:55 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A8EBB3A6D99 for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUPzsKStgDyw for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:36:54 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id BF15B3A6D3B for <dhcwg@ietf.org>; Tue, 28 Jul 2009 19:36:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALVSb0qrR7PD/2dsb2JhbAC9C4gnkCAFhBA
X-IronPort-AV: E=Sophos;i="4.43,286,1246838400"; d="scan'208";a="355975692"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 29 Jul 2009 02:36:57 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6T2at3e029247;  Tue, 28 Jul 2009 19:36:56 -0700
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6T2asns024481; Wed, 29 Jul 2009 02:36:55 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 10:36:53 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 10:36:53 +0800
Message-Id: <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6FAA27.40809@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 12:36:50 +1000
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jul 2009 02:36:53.0353 (UTC) FILETIME=[6EC8AD90:01CA0FF5]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=635; t=1248835016; x=1249699016; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=J6yJeBkmf1ONDqyQQNNb/pyknQa5buB0cvkgJ95joss=; b=PXHImOrqmqtFUiAzj5Xx883iEGppXvHX9jP7bqMN9neWfHYDP1z/PDfW/r rLpHZ2NrPzIvuvxlyAonAduSypcIh2cM+tMlspjiJXEvFEJJwEKQ0wsLTF9X 79tyqjK9ng;
Authentication-Results: sj-dkim-3; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 02:36:55 -0000

On 29/07/2009, at 11:47 AM, Yoshihiro Ohba wrote:
>> Which begs the question what is this state beyond the cached port  
>> information are you talking about, Alper mentioned some future  
>> possible keying when one distributes keys to DHCP RFC 3118 will  
>> probably be interesting in the relay but I have heard about no  
>> additional state required now for this.
>
> In addition, your DHCP relay will need to have a state for EAP  
> authenticator state machine.

While that is true for the DHCP server function I am not sure why you  
feel the relay would need this as it is not controlling flow control.

- Ric


From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 19:47:45 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 376E93A6D3A for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0xelP9uYeqC for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:47:44 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 44BBD3A6B93 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 19:47:44 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6T2lSp9003778; Wed, 29 Jul 2009 11:47:28 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6T2lSYc007713; Wed, 29 Jul 2009 11:47:28 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id MAA07712; Wed, 29 Jul 2009 11:47:28 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6T2lRRP027447; Wed, 29 Jul 2009 11:47:28 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6T2lP8W029743; Wed, 29 Jul 2009 11:47:26 +0900 (JST)
Received: from [133.196.16.81] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNI00322VR1N5N0@mail.po.toshiba.co.jp>; Wed, 29 Jul 2009 11:47:25 +0900 (JST)
Date: Tue, 28 Jul 2009 22:47:25 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6FB83D.2010900@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp> <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 02:47:45 -0000

Richard Pruss wrote:
>
> On 29/07/2009, at 11:47 AM, Yoshihiro Ohba wrote:
>>> Which begs the question what is this state beyond the cached port 
>>> information are you talking about, Alper mentioned some future 
>>> possible keying when one distributes keys to DHCP RFC 3118 will 
>>> probably be interesting in the relay but I have heard about no 
>>> additional state required now for this.
>>
>> In addition, your DHCP relay will need to have a state for EAP 
>> authenticator state machine.
>
> While that is true for the DHCP server function I am not sure why you 
> feel the relay would need this as it is not controlling flow control.

That is needed because DHCP relay is acting EAP authenticator in your 
model.  This has nothing to do with flow control.

Yoshihiro Ohba


>
> - Ric
>
>
>


From ric@cisco.com  Tue Jul 28 19:55:50 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 112ED3A6D6C for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.666
X-Spam-Level: 
X-Spam-Status: No, score=-5.666 tagged_above=-999 required=5 tests=[AWL=0.933,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aI12tcWz0Dlr for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 19:55:49 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 233E53A6B93 for <dhcwg@ietf.org>; Tue, 28 Jul 2009 19:55:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAFtXb0qrR7PD/2dsb2JhbAC9E4gnkCAFhBA
X-IronPort-AV: E=Sophos;i="4.43,286,1246838400"; d="scan'208";a="355983979"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 29 Jul 2009 02:55:51 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n6T2tnkA014938;  Tue, 28 Jul 2009 19:55:50 -0700
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6T2tnKv028346; Wed, 29 Jul 2009 02:55:49 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 10:55:49 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 10:55:48 +0800
Message-Id: <398BAF56-853D-4600-BD32-B0BED5BE803A@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6FB83D.2010900@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 12:55:45 +1000
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp> <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com> <4A6FB83D.2010900@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jul 2009 02:55:48.0605 (UTC) FILETIME=[137262D0:01CA0FF8]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1051; t=1248836150; x=1249700150; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=diwh5tZkHeiMqmI9O4uUev2BVLpRv+Vdn4j1SlcYO2Q=; b=JuSJEE3tA+m7g/PfHCcNz5YXQW6arQHFBHp6oTHkM5WszlTkq/BkQzaANy QB1YZ0EmGvPV2/SbbYTtP4e5mJSKqfpUFFafqOyfoDsEKkN5Pf4LTgLXcIah wtm02pCldP;
Authentication-Results: sj-dkim-3; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 02:55:50 -0000

On 29/07/2009, at 12:47 PM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>>
>> On 29/07/2009, at 11:47 AM, Yoshihiro Ohba wrote:
>>>> Which begs the question what is this state beyond the cached port  
>>>> information are you talking about, Alper mentioned some future  
>>>> possible keying when one distributes keys to DHCP RFC 3118 will  
>>>> probably be interesting in the relay but I have heard about no  
>>>> additional state required now for this.
>>>
>>> In addition, your DHCP relay will need to have a state for EAP  
>>> authenticator state machine.
>>
>> While that is true for the DHCP server function I am not sure why  
>> you feel the relay would need this as it is not controlling flow  
>> control.
>
> That is needed because DHCP relay is acting EAP authenticator in  
> your model.  This has nothing to do with flow control.

Well the BRAS is acting as the EAP authenticator in the architecture  
but I do not see why this requires state in an implementation of the  
DHCP relay in the BRAS.

- Ric


From yoshihiro.ohba@toshiba.co.jp  Tue Jul 28 20:39:06 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EB773A698B for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 20:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yQu5sJkck81Y for <dhcwg@core3.amsl.com>; Tue, 28 Jul 2009 20:39:05 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 3DAC03A6D6F for <dhcwg@ietf.org>; Tue, 28 Jul 2009 20:38:53 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id n6T3cbds023527; Wed, 29 Jul 2009 12:38:37 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id n6T3cbcb025356; Wed, 29 Jul 2009 12:38:37 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id NAA25355; Wed, 29 Jul 2009 12:38:37 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id n6T3cblL021424; Wed, 29 Jul 2009 12:38:37 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6T3ca3B016927; Wed, 29 Jul 2009 12:38:36 +0900 (JST)
Received: from [133.196.16.81] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNI0082HY4C4W40@mail.po.toshiba.co.jp>; Wed, 29 Jul 2009 12:38:36 +0900 (JST)
Date: Tue, 28 Jul 2009 23:38:35 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <398BAF56-853D-4600-BD32-B0BED5BE803A@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A6FC43B.8010109@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp> <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com> <4A6FB83D.2010900@toshiba.co.jp> <398BAF56-853D-4600-BD32-B0BED5BE803A@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 03:39:06 -0000

Richard Pruss wrote:
>
> On 29/07/2009, at 12:47 PM, Yoshihiro Ohba wrote:
>
>> Richard Pruss wrote:
>>>
>>> On 29/07/2009, at 11:47 AM, Yoshihiro Ohba wrote:
>>>>> Which begs the question what is this state beyond the cached port 
>>>>> information are you talking about, Alper mentioned some future 
>>>>> possible keying when one distributes keys to DHCP RFC 3118 will 
>>>>> probably be interesting in the relay but I have heard about no 
>>>>> additional state required now for this.
>>>>
>>>> In addition, your DHCP relay will need to have a state for EAP 
>>>> authenticator state machine.
>>>
>>> While that is true for the DHCP server function I am not sure why 
>>> you feel the relay would need this as it is not controlling flow 
>>> control.
>>
>> That is needed because DHCP relay is acting EAP authenticator in your 
>> model.  This has nothing to do with flow control.
>
> Well the BRAS is acting as the EAP authenticator in the architecture 
> but I do not see why this requires state in an implementation of the 
> DHCP relay in the BRAS.

EAP authenticator is responsible for method type negotiation, 
remembering the negotiated method type, retransmission of outstanding 
EAP request message, etc. DHCP relay will need to maintain a state to 
access the EAP authenticator state machine block, for each DHCP client, 
to realize this.

Yoshihiro Ohba

>
> - Ric
>
>
>


From ric@cisco.com  Wed Jul 29 01:47:08 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BFCB3A6F4B for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 01:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.724
X-Spam-Level: 
X-Spam-Status: No, score=-5.724 tagged_above=-999 required=5 tests=[AWL=0.875,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhCoXF4DdtOD for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 01:47:06 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id B2D833A6A73 for <dhcwg@ietf.org>; Wed, 29 Jul 2009 01:47:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOuob0oKS+eh/2dsb2JhbAC7ZIgnkCYFhBA
X-IronPort-AV: E=Sophos;i="4.43,288,1246838400"; d="scan'208";a="58661538"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 29 Jul 2009 08:46:59 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6T8kwgA026798;  Wed, 29 Jul 2009 16:46:58 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com [64.104.123.69]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n6T8kw7V015046; Wed, 29 Jul 2009 08:46:58 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 16:46:57 +0800
Received: from syd-rpruss-8716.cisco.com ([10.67.232.183]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 16:46:56 +0800
Message-Id: <B8EEF16B-F236-4C7E-B9CB-CF43F617853B@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-Reply-To: <4A6FC43B.8010109@toshiba.co.jp>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 29 Jul 2009 18:46:54 +1000
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp> <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com> <4A6FB83D.2010900@toshiba.co.jp> <398BAF56-853D-4600-BD32-B0BED5BE803A@cisco.com> <4A6FC43B.8010109@toshiba.co.jp>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 29 Jul 2009 08:46:57.0124 (UTC) FILETIME=[21434240:01CA1029]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1704; t=1248857218; x=1249721218; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Comments=20on=20draft-pruss-d hcp-auth-dsl-06=20and=20draft-brzozowski-dhcp-eap-analysis-0 0 |Sender:=20; bh=k0lUpb8AHN2CfE70utdZzGdiID/n+/Xbuz0m5kEhIWU=; b=Tjkv2mQzNy1ilf2OYULDEh8qnd4EaFpHgPy/quzXK6ryOMfeiL9Wb6wO5a dFicfnVDKvcutcx1EVfUaS54hT7QNqt4bFauJnAXATumTJmIjj44dpMLEcuK 6/6wmptkHbZnOzBjUC24TJiW2L6H6gXSaSGaXyrhoCeKkQl6FaiOg=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 08:47:08 -0000

On 29/07/2009, at 1:38 PM, Yoshihiro Ohba wrote:

> Richard Pruss wrote:
>>
>> On 29/07/2009, at 12:47 PM, Yoshihiro Ohba wrote:
>>
>>> Richard Pruss wrote:
>>>>
>>>> On 29/07/2009, at 11:47 AM, Yoshihiro Ohba wrote:
>>>>>> Which begs the question what is this state beyond the cached  
>>>>>> port information are you talking about, Alper mentioned some  
>>>>>> future possible keying when one distributes keys to DHCP RFC  
>>>>>> 3118 will probably be interesting in the relay but I have heard  
>>>>>> about no additional state required now for this.
>>>>>
>>>>> In addition, your DHCP relay will need to have a state for EAP  
>>>>> authenticator state machine.
>>>>
>>>> While that is true for the DHCP server function I am not sure why  
>>>> you feel the relay would need this as it is not controlling flow  
>>>> control.
>>>
>>> That is needed because DHCP relay is acting EAP authenticator in  
>>> your model.  This has nothing to do with flow control.
>>
>> Well the BRAS is acting as the EAP authenticator in the  
>> architecture but I do not see why this requires state in an  
>> implementation of the DHCP relay in the BRAS.
>
> EAP authenticator is responsible for method type negotiation,  
> remembering the negotiated method type, retransmission of  
> outstanding EAP request message, etc. DHCP relay will need to  
> maintain a state to access the EAP authenticator state machine  
> block, for each DHCP client, to realize this.
We are in so deep into what one could consider this implementation  
specific territory, but I consider the previously mentioned cached  
state sufficient to access said EAP authenticator state block.

- Ric




From volz@cisco.com  Wed Jul 29 07:50:51 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC0DD3A672F for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 07:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vikl0mPKlgQ for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 07:50:51 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id DCF7B3A6A29 for <dhcwg@ietf.org>; Wed, 29 Jul 2009 07:50:50 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALj+b0pAZnme/2dsb2JhbAC7WIgnkDMFhBE
X-IronPort-AV: E=Sophos;i="4.43,289,1246838400"; d="scan'208";a="52153005"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 29 Jul 2009 14:50:52 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6TEoq4s009915;  Wed, 29 Jul 2009 10:50:52 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n6TEoqiG020388; Wed, 29 Jul 2009 14:50:52 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Jul 2009 10:50:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 29 Jul 2009 10:50:50 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210DD95B33@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <105EED7F-0CE5-4902-AA48-28C785128355@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Renewing an empty IA
Thread-Index: AcoHFkdcuC6RS5/ETGS8n7MtCe083wJRYLaQ
References: <105EED7F-0CE5-4902-AA48-28C785128355@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Damien Neil" <Damien.Neil@nominum.com>, "DHC-WG WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 29 Jul 2009 14:50:51.0823 (UTC) FILETIME=[F7C1EBF0:01CA105B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=790; t=1248879052; x=1249743052; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Renewing=20an=20empty=20IA |Sender:=20 |To:=20=22Damien=20Neil=22=20<Damien.Neil@nominum.com>,=20= 22DHC-WG=20WG=22=20<dhcwg@ietf.org>; bh=XHLH7cVHzH24tLYkfLXNmpDtcapdZglJ0VuKO1b9mlM=; b=glZQJnCbNWNbjwXSGHFEymiCNHIORw8yNr56cM+rDPfjou3eikvOI3FqTj C/+lKMVO4uCCjhtIk8JL9q7OV64HFTJMyVf003kDN8Ww+o/LfkR3pQFpFaZy bS9Nn16vlF;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Subject: Re: [dhcwg] Renewing an empty IA
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 14:50:51 -0000

If the server has no record of the binding, RFC 3315 is pretty clear
(return NoBinding). But, if it does, my answer is to renew any existing
addresses for that binding or assign new addresses (if appropriate) and
return them in the Reply.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Damien Neil
Sent: Friday, July 17, 2009 3:39 PM
To: DHC-WG WG
Subject: [dhcwg] Renewing an empty IA

A minor question of conforming behavior that came up here:

How should a server handle a Renew message which contains an IA_NA =20
that contains no IAADDR options?

              - Damien
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From yoshihiro.ohba@toshiba.co.jp  Wed Jul 29 12:37:09 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82C8B3A6FBF for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 12:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.656
X-Spam-Level: 
X-Spam-Status: No, score=-3.656 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRhSIoVf2muL for <dhcwg@core3.amsl.com>; Wed, 29 Jul 2009 12:37:08 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id 95B4E3A6917 for <dhcwg@ietf.org>; Wed, 29 Jul 2009 12:37:08 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6TJaou3002789; Thu, 30 Jul 2009 04:36:50 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6TJaoTk017628; Thu, 30 Jul 2009 04:36:50 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id EAA17627; Thu, 30 Jul 2009 04:36:50 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6TJaoDt028497; Thu, 30 Jul 2009 04:36:50 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6TJaopr022740; Thu, 30 Jul 2009 04:36:50 +0900 (JST)
Received: from [133.199.17.212] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNK00BII6HDOY40@mail.po.toshiba.co.jp>; Thu, 30 Jul 2009 04:36:50 +0900 (JST)
Date: Wed, 29 Jul 2009 15:36:46 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <B8EEF16B-F236-4C7E-B9CB-CF43F617853B@cisco.com>
To: Richard Pruss <ric@cisco.com>
Message-id: <4A70A4CE.5060308@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <AE7097F7-8BC3-4B75-B714-4BB991D5AE07@cisco.com> <4A6FAA27.40809@toshiba.co.jp> <78A12BB2-5E17-43A0-A6A8-989E574F0F94@cisco.com> <4A6FB83D.2010900@toshiba.co.jp> <398BAF56-853D-4600-BD32-B0BED5BE803A@cisco.com> <4A6FC43B.8010109@toshiba.co.jp> <B8EEF16B-F236-4C7E-B9CB-CF43F617853B@cisco.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>, Ted Lemon <mellon@fugue.com>, MILES DAVID <David.Miles@alcatel-lucent.com.au>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2009 19:37:09 -0000

Richard Pruss wrote:
>
>>>
>>> Well the BRAS is acting as the EAP authenticator in the architecture 
>>> but I do not see why this requires state in an implementation of the 
>>> DHCP relay in the BRAS.
>>
>> EAP authenticator is responsible for method type negotiation, 
>> remembering the negotiated method type, retransmission of outstanding 
>> EAP request message, etc. DHCP relay will need to maintain a state to 
>> access the EAP authenticator state machine block, for each DHCP 
>> client, to realize this.
> We are in so deep into what one could consider this implementation 
> specific territory, but I consider the previously mentioned cached 
> state sufficient to access said EAP authenticator state block.
>
I believe EAP state machine block needs to stay longer than the cache, 
otherwise your DHCP relay with cache is characterized as a stateful 
entity. I would like to see much more detailed description and analysis 
on this aspect in the analysis draft so that members can evaluate 
appropriately.

Yoshihiro Ohba


> - Ric
>
>
>
>
>



From alper.yegin@yegin.org  Thu Jul 30 09:12:07 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 771E83A688B for <dhcwg@core3.amsl.com>; Thu, 30 Jul 2009 09:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AF-oq8287MGK for <dhcwg@core3.amsl.com>; Thu, 30 Jul 2009 09:12:06 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 8F10B3A6C43 for <dhcwg@ietf.org>; Thu, 30 Jul 2009 09:12:06 -0700 (PDT)
Received: from LENOVO (dhcp-57aa.meeting.ietf.org [130.129.87.170]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1MWYEa1wXY-000Odw; Thu, 30 Jul 2009 12:12:07 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Richard Pruss'" <ric@cisco.com>, "'Ted Lemon'" <mellon@fugue.com>
References: <4A6CD501.7030704@toshiba.co.jp>	<C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>	<4A6D4F53.2060608@toshiba.co.jp>	<270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>	<8BABA261-DE48-4684-85C8-419591061672@cisco.com>	<9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>	<4A6D5C54.6050904@toshiba.co.jp>	<CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>	<4A6D5E5D.8070707@toshiba.co.jp>	<7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>	<4A6D685A.7000406@toshiba.co.jp>	<6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>	<4A6DC7E3.2010001@toshiba.co.jp>	<986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com>	<4A6E45DC.5030103@toshiba.co.jp>	<986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>	<4A6EB8E6.4070800@toshiba.co.jp>	<9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com>	<ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com>
In-Reply-To: <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com>
Date: Thu, 30 Jul 2009 19:11:59 +0300
Message-ID: <066c01ca1130$7c814730$7583d590$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcoPutXfSzhIva2ERK6wsKRq7j7n0gBdFu3A
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX1+taJAyyrMYEON7W+4uwR4E4fxyBxjLeq19HzU t1hXCvrp/azwMBLFepytFl0tuxib8+VnatcCl/coMTnvFCZnfB w/tEiyZ9VvMdKiOYgxGPA==
Cc: 'dhc WG' <dhcwg@ietf.org>, 'MILES DAVID' <David.Miles@alcatel-lucent.com.au>, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2009 16:12:07 -0000

> Sorry Ted, he is claiming we do not meet the requirements because we
> vendors call the L3 DHCP relay
> function a proxy.   Sinking to a semantic debate on if something is a
> proxy or a relay is a new low.

Your I-D rightfully calls the entity residing on NAS a "DHCP relay". 

   Figure 3: DHCP Authentication Message Flow with DHCP relay NAS

If you remove this scenario, you fail the TR-101 requirement:

The Broadband Network Gateway MUST be able to function as a DHCP Relay Agent
as described in RFC 951 "BOOTP", RFC 2131"DHCP" and RFC 3046 "DHCP Relay
Agent Information Option" on selected untrusted interfaces." 

Isn't that obvious to everyone?


> We do lots of extra things in this L3 edge because we compete on
> features and this L3 Edge does all kind
> of things I am sure a pure relay does not, ones I often mention are
> map attributes from AAA and interact with
> the local session enforcement and routing mechanisms so that the
> assigned address is the only one the DHCP client can
> send and receive traffic on.

People's concern is "DHCP relay implementation" maintaining state; not "the
box that implements DHCP relay" maintaining state. Obviously the latter
would have state for non-DHCP reasons.

Alper




> 
> It was because DHCP does so much already in the BRAS/NAS that the
> adding a few attributes for authentication
> to add to the quality of the decision is a logical choice.
> 
> - Ric
> 
> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
> 
> > Ric, I get that you are frustrated by this discussion, but for us
> > innocent bystanders, it would be helpful if you could respond
> > factually, rather than expressing your frustration. Please remember
> > that your grasp of what you are trying to do is much greater than
> > ours, since we aren't trying to do it.   If you think it's a bad
> > question, I'd like to see you say why.
> >
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From David.Miles@alcatel-lucent.com.au  Thu Jul 30 21:14:39 2009
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D18F3A6B2E for <dhcwg@core3.amsl.com>; Thu, 30 Jul 2009 21:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euBD-eP+tXe8 for <dhcwg@core3.amsl.com>; Thu, 30 Jul 2009 21:14:38 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 927553A6B94 for <dhcwg@ietf.org>; Thu, 30 Jul 2009 21:14:35 -0700 (PDT)
Received: from horh1.usa.alcatel.com (h172-22-218-55.lucent.com [172.22.218.55]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n6V4E0Ls007885; Thu, 30 Jul 2009 23:14:01 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by horh1.usa.alcatel.com (8.13.8/emsr) with ESMTP id n6V4Dvj4022872; Thu, 30 Jul 2009 23:13:58 -0500 (CDT)
Received: from sgsinsbhs01.ad4.ad.alcatel.com (sgsinsbhs01.ap.lucent.com [135.254.109.34]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n6V481os020953; Fri, 31 Jul 2009 12:08:05 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 31 Jul 2009 12:13:30 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 31 Jul 2009 12:13:27 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D03BEC491@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <066c01ca1130$7c814730$7583d590$@yegin@yegin.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
Thread-Index: AcoPutXfSzhIva2ERK6wsKRq7j7n0gBdFu3AABhe71A=
References: <4A6CD501.7030704@toshiba.co.jp>	<C708E5F0-D1FD-48E6-B5DD-8EE0B1D9AA5A@cisco.com>	<4A6D4F53.2060608@toshiba.co.jp>	<270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com>	<8BABA261-DE48-4684-85C8-419591061672@cisco.com>	<9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com>	<4A6D5C54.6050904@toshiba.co.jp>	<CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com>	<4A6D5E5D.8070707@toshiba.co.jp>	<7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com>	<4A6D685A.7000406@toshiba.co.jp>	<6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com>	<4A6DC7E3.2010001@toshiba.co.jp>	<986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com>	<4A6E45DC.5030103@toshiba.co.jp>	<986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com>	<4A6EB8E6.4070800@toshiba.co.jp>	<9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com>	<ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> <066c01ca1130$7c814730$7583d590$@yegin@yegin.org>
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: "Alper Yegin" <alper.yegin@yegin.org>, "Richard Pruss" <ric@cisco.com>, "Ted Lemon" <mellon@fugue.com>
X-OriginalArrivalTime: 31 Jul 2009 04:13:30.0401 (UTC) FILETIME=[42EB8110:01CA1195]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2009 04:14:39 -0000

Gents,

We currently have the two options below:

1) A BNG that acts as DHCP Server, and uses RADIUS for all AAA
2) A BNG that splits the EAP messages from DHCP: Uses RADIUS for EAP
transport, but maintains DHCP for address assignment  (split AAA)

This second model is obviously causing significant controversy.=20

I propose the following model, to me this satisfies operators who wish
the BNG to be a DHCP relay, and does not introduce any requirement for
caching, storing, or otherwise processing the new message type.=20

You can consider this:
3) A BNG that acts as a DHCP Relay. All DHCP messages are relayed to the
DHCP server. There is no cached state, no processing of EAP messages, or
sending EAP requests. The DHCP Server must perform this function.

It is important that we acknowledge this model because any intermediate
relay (including L2RA and LDRA) will need to process the DHCPEAP
messages like this as well - for this reason I have labeled in NAS or AN
[Access Node]. For a BNG it continues to snoop the DHCP ACK to create
the IP Session.


       (HGW)               (NAS or AN)                  (DHCP)
     DHCP client           DHCP Relay            DHCP server
   EAP Supplicant

        DHCPDISCOVER -------->
         (w/DHCP-auth-proto EAP)
                                  DHCPDISCOVER ------->
                                   (w/DHCP-auth-proto EAP)

                                  <------------ DHCPEAP
                                           (w/EAP ID Req.)
        <------------- DHCPEAP
             (w/EAP ID Req.)

        DHCPEAP ------------->
         (w/EAP Message)
                                  DHCPEAP ------------>
                                   (w/EAP Message)
   +--
   |                              <------------ DHCPEAP
   |                                       (w/EAP Message)
   |    <------------- DHCPEAP
   |         (w/EAP Message)
   |
   |    DHCPEAP ------------->
   |     (w/EAP Message)
   |                              DHCPEAP ------------>
   |                              (w/EAP Message)
   +--
    (The last four messages repeat until EAP Success or EAP fail)

                                  <------------ DHCPEAP
                                           (w/EAP Success)
        <------------- DHCPEAP
                (w/EAP Success)

                                  <----------DHCP OFFER
        <---------- DHCP OFFER

        DHCP REQUEST -------->
                                  DHCP REQUEST ------->

                                  <----------DHCP ACK
        <------------ DHCP ACK


Cheers,

d





-----Original Message-----
From: Alper Yegin [mailto:alper.yegin@yegin.org]=20
Sent: Friday, July 31, 2009 1:42 AM
To: 'Richard Pruss'; 'Ted Lemon'
Cc: 'dhc WG'; MILES DAVID; 'Ralph Droms'
Subject: RE: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
draft-brzozowski-dhcp-eap-analysis-00

> Sorry Ted, he is claiming we do not meet the requirements because we
> vendors call the L3 DHCP relay
> function a proxy.   Sinking to a semantic debate on if something is a
> proxy or a relay is a new low.

Your I-D rightfully calls the entity residing on NAS a "DHCP relay".=20

   Figure 3: DHCP Authentication Message Flow with DHCP relay NAS

If you remove this scenario, you fail the TR-101 requirement:

The Broadband Network Gateway MUST be able to function as a DHCP Relay
Agent
as described in RFC 951 "BOOTP", RFC 2131"DHCP" and RFC 3046 "DHCP Relay
Agent Information Option" on selected untrusted interfaces."=20

Isn't that obvious to everyone?


> We do lots of extra things in this L3 edge because we compete on
> features and this L3 Edge does all kind
> of things I am sure a pure relay does not, ones I often mention are
> map attributes from AAA and interact with
> the local session enforcement and routing mechanisms so that the
> assigned address is the only one the DHCP client can
> send and receive traffic on.

People's concern is "DHCP relay implementation" maintaining state; not
"the
box that implements DHCP relay" maintaining state. Obviously the latter
would have state for non-DHCP reasons.

Alper




>=20
> It was because DHCP does so much already in the BRAS/NAS that the
> adding a few attributes for authentication
> to add to the quality of the decision is a logical choice.
>=20
> - Ric
>=20
> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>=20
> > Ric, I get that you are frustrated by this discussion, but for us
> > innocent bystanders, it would be helpful if you could respond
> > factually, rather than expressing your frustration. Please remember
> > that your grasp of what you are trying to do is much greater than
> > ours, since we aren't trying to do it.   If you think it's a bad
> > question, I'd like to see you say why.
> >
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From yoshihiro.ohba@toshiba.co.jp  Fri Jul 31 00:04:37 2009
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCC4D3A6C53 for <dhcwg@core3.amsl.com>; Fri, 31 Jul 2009 00:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.089
X-Spam-Level: 
X-Spam-Status: No, score=-4.089 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSu6C6CJYf3D for <dhcwg@core3.amsl.com>; Fri, 31 Jul 2009 00:04:36 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by core3.amsl.com (Postfix) with ESMTP id F3CFE3A6DF3 for <dhcwg@ietf.org>; Fri, 31 Jul 2009 00:04:14 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp  with ESMTP id n6V73vVT020800; Fri, 31 Jul 2009 16:03:57 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp  id n6V73v9V005404; Fri, 31 Jul 2009 16:03:57 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148]  by arc11.toshiba.co.jp with ESMTP id SAA05403; Fri, 31 Jul 2009 16:03:57 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp  with ESMTP id n6V73vd7000995; Fri, 31 Jul 2009 16:03:57 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id n6V73rqj021821; Fri, 31 Jul 2009 16:03:55 +0900 (JST)
Received: from [133.196.16.147] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0KNM00K03WYHGQB0@mail.po.toshiba.co.jp>; Fri, 31 Jul 2009 16:03:53 +0900 (JST)
Date: Fri, 31 Jul 2009 03:03:47 -0400
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <986DCE2E44129444B6435ABE8C9E424D03BEC491@SGSINSMBS02.ad4.ad.alcatel.com>
To: MILES DAVID <David.Miles@alcatel-lucent.com.au>
Message-id: <4A729753.8070608@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
References: <4A6CD501.7030704@toshiba.co.jp> <4A6D4F53.2060608@toshiba.co.jp> <270BDEDD-E130-48EC-B524-DE95FB4F5FAE@cisco.com> <8BABA261-DE48-4684-85C8-419591061672@cisco.com> <9570F52D-47B2-4863-A0E7-D99002575BF4@cisco.com> <4A6D5C54.6050904@toshiba.co.jp> <CC38CCBB-1091-4570-8AB7-4AB44064BACF@cisco.com> <4A6D5E5D.8070707@toshiba.co.jp> <7C0336BD-D6AB-4A15-96FB-B13EC1C413A3@cisco.com> <4A6D685A.7000406@toshiba.co.jp> <6AB031A0-BFE1-4670-95AE-AC972CAC3C92@cisco.com> <4A6DC7E3.2010001@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CB1A@SGSINSMBS02.ad4.ad.alcatel.com> <4A6E45DC.5030103@toshiba.co.jp> <986DCE2E44129444B6435ABE8C9E424D03B9CC07@SGSINSMBS02.ad4.ad.alcatel.com> <4A6EB8E6.4070800@toshiba.co.jp> <9CA860FA-BACD-40D7-875C-2F9BF8E74143@cisco.com> <ACEA98AF-43CA-49F6-B21E-DA45B18A8EB3@fugue.com> <DD1D91A4-F20D-4CEA-96C4-28ECDEDE53A9@cisco.com> <066c01ca1130$7c814730$7583d590$%yegin@yegin.org> <986DCE2E44129444B6435ABE8C9E424D03BEC491@SGSINSMBS02.ad4.ad.alcatel.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <mellon@fugue.com>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06	and	draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2009 07:04:37 -0000

Your suggested model does not fit DSL Network Architecture (Figure 1) 
where NAS is the entity that interacts with AAA, whereas in your model 
DHCP server (separated from NAS or AN) needs to be the entity that 
interacts with AAA.

Yoshihiro Ohba


MILES DAVID wrote:
> Gents,
>
> We currently have the two options below:
>
> 1) A BNG that acts as DHCP Server, and uses RADIUS for all AAA
> 2) A BNG that splits the EAP messages from DHCP: Uses RADIUS for EAP
> transport, but maintains DHCP for address assignment  (split AAA)
>
> This second model is obviously causing significant controversy. 
>
> I propose the following model, to me this satisfies operators who wish
> the BNG to be a DHCP relay, and does not introduce any requirement for
> caching, storing, or otherwise processing the new message type. 
>
> You can consider this:
> 3) A BNG that acts as a DHCP Relay. All DHCP messages are relayed to the
> DHCP server. There is no cached state, no processing of EAP messages, or
> sending EAP requests. The DHCP Server must perform this function.
>
> It is important that we acknowledge this model because any intermediate
> relay (including L2RA and LDRA) will need to process the DHCPEAP
> messages like this as well - for this reason I have labeled in NAS or AN
> [Access Node]. For a BNG it continues to snoop the DHCP ACK to create
> the IP Session.
>
>
>        (HGW)               (NAS or AN)                  (DHCP)
>      DHCP client           DHCP Relay            DHCP server
>    EAP Supplicant
>
>         DHCPDISCOVER -------->
>          (w/DHCP-auth-proto EAP)
>                                   DHCPDISCOVER ------->
>                                    (w/DHCP-auth-proto EAP)
>
>                                   <------------ DHCPEAP
>                                            (w/EAP ID Req.)
>         <------------- DHCPEAP
>              (w/EAP ID Req.)
>
>         DHCPEAP ------------->
>          (w/EAP Message)
>                                   DHCPEAP ------------>
>                                    (w/EAP Message)
>    +--
>    |                              <------------ DHCPEAP
>    |                                       (w/EAP Message)
>    |    <------------- DHCPEAP
>    |         (w/EAP Message)
>    |
>    |    DHCPEAP ------------->
>    |     (w/EAP Message)
>    |                              DHCPEAP ------------>
>    |                              (w/EAP Message)
>    +--
>     (The last four messages repeat until EAP Success or EAP fail)
>
>                                   <------------ DHCPEAP
>                                            (w/EAP Success)
>         <------------- DHCPEAP
>                 (w/EAP Success)
>
>                                   <----------DHCP OFFER
>         <---------- DHCP OFFER
>
>         DHCP REQUEST -------->
>                                   DHCP REQUEST ------->
>
>                                   <----------DHCP ACK
>         <------------ DHCP ACK
>
>
> Cheers,
>
> d
>
>
>
>
>
> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org] 
> Sent: Friday, July 31, 2009 1:42 AM
> To: 'Richard Pruss'; 'Ted Lemon'
> Cc: 'dhc WG'; MILES DAVID; 'Ralph Droms'
> Subject: RE: [dhcwg] Comments on draft-pruss-dhcp-auth-dsl-06 and
> draft-brzozowski-dhcp-eap-analysis-00
>
>   
>> Sorry Ted, he is claiming we do not meet the requirements because we
>> vendors call the L3 DHCP relay
>> function a proxy.   Sinking to a semantic debate on if something is a
>> proxy or a relay is a new low.
>>     
>
> Your I-D rightfully calls the entity residing on NAS a "DHCP relay". 
>
>    Figure 3: DHCP Authentication Message Flow with DHCP relay NAS
>
> If you remove this scenario, you fail the TR-101 requirement:
>
> The Broadband Network Gateway MUST be able to function as a DHCP Relay
> Agent
> as described in RFC 951 "BOOTP", RFC 2131"DHCP" and RFC 3046 "DHCP Relay
> Agent Information Option" on selected untrusted interfaces." 
>
> Isn't that obvious to everyone?
>
>
>   
>> We do lots of extra things in this L3 edge because we compete on
>> features and this L3 Edge does all kind
>> of things I am sure a pure relay does not, ones I often mention are
>> map attributes from AAA and interact with
>> the local session enforcement and routing mechanisms so that the
>> assigned address is the only one the DHCP client can
>> send and receive traffic on.
>>     
>
> People's concern is "DHCP relay implementation" maintaining state; not
> "the
> box that implements DHCP relay" maintaining state. Obviously the latter
> would have state for non-DHCP reasons.
>
> Alper
>
>
>
>
>   
>> It was because DHCP does so much already in the BRAS/NAS that the
>> adding a few attributes for authentication
>> to add to the quality of the decision is a logical choice.
>>
>> - Ric
>>
>> On 29/07/2009, at 12:56 AM, Ted Lemon wrote:
>>
>>     
>>> Ric, I get that you are frustrated by this discussion, but for us
>>> innocent bystanders, it would be helpful if you could respond
>>> factually, rather than expressing your frustration. Please remember
>>> that your grasp of what you are trying to do is much greater than
>>> ours, since we aren't trying to do it.   If you think it's a bad
>>> question, I'd like to see you say why.
>>>
>>>       
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>>     
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>
>   

