Re: Wireless LAN Certificate Extensions

Hiroyuki CHIBA <hiro@bisd.hitachi.co.jp> Mon, 29 July 2002 03:45 UTC

Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA08034 for <pkix-archive@odin.ietf.org>; Sun, 28 Jul 2002 23:45:03 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id g6T3BPf02311 for ietf-pkix-bks; Sun, 28 Jul 2002 20:11:25 -0700 (PDT)
Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g6T3BNw02306 for <ietf-pkix@imc.org>; Sun, 28 Jul 2002 20:11:23 -0700 (PDT)
Received: from navsg2.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id MAA16087; Mon, 29 Jul 2002 12:10:26 +0900 (JST)
Received: from navsg2.hitachi.co.jp by navsg2.hitachi.co.jp (8.9.3/3.7W-navsg2) id MAA09434; Mon, 29 Jul 2002 12:10:25 +0900 (JST)
Received: from navgw4.itg.hitachi.co.jp ([158.213.165.15]) by navsg2.hitachi.co.jp (NAVGW 2.5.1.16) with SMTP id M2002072912102527537 for <ietf-pkix@imc.org>; Mon, 29 Jul 2002 12:10:25 +0900
Received: from bisdgw.bisd.hitachi.co.jp ([133.144.87.253]) by navgw4.itg.hitachi.co.jp (NAVGW 2.5.2.9) with SMTP id M2002072912102521498 ; Mon, 29 Jul 2002 12:10:25 +0900
Received: from bisdmlvg1.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with SMTP id MAA12394; Mon, 29 Jul 2002 12:10:25 +0900 (JST) (envelope-from hiro@bisd.hitachi.co.jp)
Received: by bisdmail.bisd.hitachi.co.jp (8.11.3/3.7W-bisdmail) id g6T3AND46797; Mon, 29 Jul 2002 12:10:23 +0900 (JST) (envelope-from hiro)
To: rhousley@rsasecurity.com, ietf-pkix@imc.org
Cc: hiro@bisd.hitachi.co.jp
Subject: Re: Wireless LAN Certificate Extensions
From: Hiroyuki CHIBA <hiro@bisd.hitachi.co.jp>
In-Reply-To: <5.1.0.14.2.20020724173521.034df950@exna07.securitydynamics.com>
References: <5.1.0.14.2.20020724173521.034df950@exna07.securitydynamics.com>
X-Mailer: Mew version 1.94.2 on Emacs 19.34 / Mule 2.3 (末摘花)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <20020729120839E.hiro@bisd.hitachi.co.jp>
Date: Mon, 29 Jul 2002 12:08:39 +0900
X-Dispatcher: imput version 20000228(IM140)
Lines: 31
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi,

>>>>> On Wed, 24 Jul 2002 17:40:33 -0400,
	"Housley, Russ" <rhousley@rsasecurity.com> said
	 about: Wireless LAN Certificate Extensions:

rhousley> At the IETF meeting in Japan last week, I gave a presentation on 
rhousley> draft-ietf-pkix-wlan-extns-00.txt. I got one question that deserves 
rhousley> discussion on the list.

It's my question.

rhousley> The question was: Can the SSID change?  And if so, is there a more stable 
rhousley> alternative that we could include in the certificate instead.

rhousley> Yes the SSID can change, but it does not change often.  For example when 
rhousley> Mobilestar was bought, the SSID was changed to TMOBILE from Mobilestar. 
rhousley> There isn't a good replacement. One that the authors considered is the 
rhousley> network name of the RADIUS server/proxy (not the final RADIUS server) which 
rhousley> would be mobilestar.com in the previous example.  However, this name would 
rhousley> also change under then same circumstances that cause the SSID to change.

rhousley> I propose that we stick with SSID as described in the document.

If this extension can be included in either PKC or AC, we can select
the alternative for a volatile SSID with reduced revocation cost, I think.
Any comments?

----
Hiroyuki CHIBA: hiro@bisd.hitachi.co.jp clin@imasy.org
     Security Solution Promoting Division, Hitachi,Ltd.