IETF Logo Mail Archive

Re: [HOKEY] adoption of https://datatracker.ietf.org/doc/draft-wu-hokey-ldn-discovery/ as a WG document

Sebastien Decugis <sdecugis@nict.go.jp> Fri, 02 April 2010 03:09 UTC

Return-Path: <sdecugis@nict.go.jp>
X-Original-To: hokey@core3.amsl.com
Delivered-To: hokey@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CB393A67C0 for <hokey@core3.amsl.com>; Thu, 1 Apr 2010 20:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.847
X-Spam-Level: **
X-Spam-Status: No, score=2.847 tagged_above=-999 required=5 tests=[AWL=-1.727, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, FRT_SOMA2=2.199, HELO_EQ_JP=1.244]
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 n8fe-wn+S3eU for <hokey@core3.amsl.com>; Thu, 1 Apr 2010 20:09:14 -0700 (PDT)
Received: from ns2.nict.go.jp (ns2.nict.go.jp [IPv6:2001:2f8:29::3]) by core3.amsl.com (Postfix) with ESMTP id 0785D3A67F5 for <hokey@ietf.org>; Thu, 1 Apr 2010 20:09:12 -0700 (PDT)
Received: from gw2.nict.go.jp (gw2 [133.243.18.251]) by ns2.nict.go.jp with ESMTP id o3239f2b014558 for <hokey@ietf.org>; Fri, 2 Apr 2010 12:09:41 +0900 (JST)
Received: from gw2.nict.go.jp (localhost [127.0.0.1]) by gw2.nict.go.jp with ESMTP id o3239e2g028614 for <hokey@ietf.org>; Fri, 2 Apr 2010 12:09:40 +0900 (JST)
Received: from mail1.nict.go.jp (mail.nict.go.jp [133.243.18.3]) by gw2.nict.go.jp with ESMTP id o3239eYM028611 for <hokey@ietf.org>; Fri, 2 Apr 2010 12:09:40 +0900 (JST)
Received: from mail1.nict.go.jp (localhost [127.0.0.1]) by mail1.nict.go.jp (NICT Mail) with ESMTP id C754A165D8 for <hokey@ietf.org>; Fri, 2 Apr 2010 12:09:40 +0900 (JST)
Received: from [133.243.146.171] (5gou2f-dhcp11.nict.go.jp [133.243.146.171]) by mail1.nict.go.jp (NICT Mail) with ESMTP id C2C49165C4 for <hokey@ietf.org>; Fri, 2 Apr 2010 12:09:40 +0900 (JST)
Message-ID: <4BB55FEF.5070609@nict.go.jp>
Date: Fri, 02 Apr 2010 12:09:35 +0900
From: Sebastien Decugis <sdecugis@nict.go.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: hokey@ietf.org
References: <008501cacd54$504b4ea0$f0e1ebe0$@net>
In-Reply-To: <008501cacd54$504b4ea0$f0e1ebe0$@net>
X-Enigmail-Version: 1.0.1
OpenPGP: id=33D9F61D
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [HOKEY] adoption of https://datatracker.ietf.org/doc/draft-wu-hokey-ldn-discovery/ as a WG document
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2010 03:09:15 -0000

I don't fully understand the purpose of this document.

If my understanding is correct, in many deployment scenario, the DHCP
traffic is allowed only once the peer is authenticated (ex: 802.1X). To
authenticate using ERP protocol, the peer needs to know the local domain
name before the re-authentication starts. Therefore, I really don't
understand how carrying the LDN information in DHCP can help.

Can you please explain it to me?

Best regards,
Sebastien.

Le 27/03/2010 11:22, Glen Zorn a écrit :
> During yesterday's session, the consensus of the room was to adopt
> https://datatracker.ietf.org/doc/draft-wu-hokey-ldn-discovery/ as a WG
> document; the purpose of this message is to confirm this with the entire WG.
> Please read the document and express an opinion before 2 Apr.  Thanks!
>
> _______________________________________________
> HOKEY mailing list
> HOKEY@ietf.org
> https://www.ietf.org/mailman/listinfo/hokey
>
>   

-- 
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)

v2.23.0 | Report a Bug | By Email