Re: [saag] Or grow a real PKI (Re: SHA-1 to SHA-n transition)

"Hallam-Baker, Phillip" <pbaker@verisign.com> Tue, 03 March 2009 19:15 UTC

Return-Path: <pbaker@verisign.com>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA7203A69BB for <saag@core3.amsl.com>; Tue, 3 Mar 2009 11:15:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.225
X-Spam-Level:
X-Spam-Status: No, score=-6.225 tagged_above=-999 required=5 tests=[AWL=0.373, 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 yLJTooQO79VN for <saag@core3.amsl.com>; Tue, 3 Mar 2009 11:15:55 -0800 (PST)
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by core3.amsl.com (Postfix) with ESMTP id D16C83A695E for <saag@ietf.org>; Tue, 3 Mar 2009 11:15:55 -0800 (PST)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id n23IpbpE015165; Tue, 3 Mar 2009 10:51:37 -0800
Received: from MOU1WNEXMB09.vcorp.ad.vrsn.com ([10.25.15.197]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 3 Mar 2009 11:16:13 -0800
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_01C99C34.8435B596"
Date: Tue, 03 Mar 2009 11:12:46 -0800
Message-ID: <2788466ED3E31C418E9ACC5C3166155768B2F3@mou1wnexmb09.vcorp.ad.vrsn.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [saag] Or grow a real PKI (Re: SHA-1 to SHA-n transition)
Thread-Index: AcmcMXUztgJ2QE6DQ4ujbgfcaav7dAAApQY5
References: <20090227022359.8D45150822@romeo.rtfm.com> <20090302161134.GG9992@Sun.COM> <20090302172135.DA43650822@romeo.rtfm.com> <200903021720.n22HKZOv006388@grapenut.srv.cs.cmu.edu> <864C82388E530D27DCB6002F@minbar.fac.cs.cmu.edu> <20090302182547.GX9992@Sun.COM> <0DE6E86D395C657BABF43B97@minbar.fac.cs.cmu.edu> <20090302185050.GB9992@Sun.COM> <20090302205656.GF9992@Sun.COM> <2788466ED3E31C418E9ACC5C3166155768B2EC@mou1wnexmb09.vcorp.ad.vrsn.com> <20090303163002.GA9992@Sun.COM> <2788466ED3E31C418E9ACC5C3166155768B2EE@mou1wnexmb09.vcorp.ad.vrsn.com> <p0624080fc5d32caf7188@[10.34.4.253]>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: Stephen Kent <kent@bbn.com>
X-OriginalArrivalTime: 03 Mar 2009 19:16:13.0841 (UTC) FILETIME=[84E21010:01C99C34]
Cc: saag@ietf.org, Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: [saag] Or grow a real PKI (Re: SHA-1 to SHA-n transition)
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2009 19:15:57 -0000

We already went through that phase. Early in the life of PKI there was a whole slew of state regulation. At one point there was an entire wall in the practices group covered in certification and accreditation plaques.

None of it had any real effect.

These are hard problems that governments have difficulty with as well. It was a government inquiry that started my thinking on this topic.


Regulation is a government tool, it is rarely a government objective in its own right.


-----Original Message-----
From: Stephen Kent [mailto:kent@bbn.com]
Sent: Tue 3/3/2009 1:53 PM
To: Hallam-Baker, Phillip
Cc: Nicolas Williams; saag@ietf.org
Subject: Re: [saag] Or grow a real PKI (Re:  SHA-1 to SHA-n transition)
 
At 9:04 AM -0800 3/3/09, Hallam-Baker, Phillip wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>	boundary="----_=_NextPart_001_01C99C22.4DD0C516"
>
>Governments can regulate PKIs to be employed for government purposes.
>

A government can regulate CAs that operate in its country, for ANY 
purpose, if so desires.

But, I already noted that this outcome is likely in the U.S. or the EU.

Steve