From owner-ietf-pkix@mail.imc.org Mon Jun 04 14:51:18 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvHeA-0002Ta-07
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 14:51:18 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvHe8-00024k-9F
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 14:51:17 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Hc5em050124
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 10:38:05 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54Hc5Yf050123;
	Mon, 4 Jun 2007 10:38:05 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Hc4ur050116
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 10:38:05 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l54Hc1Zs018120
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 10:38:03 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Jun 2007 10:38:01 -0700
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_01C7A6CF.18E753C3"
Subject: Three short fixes
Date: Mon, 4 Jun 2007 10:36:50 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbg==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 17:38:01.0353 (UTC) FILETIME=[19233F90:01C7A6CF]
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6CF.18E753C3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Work in the w3C Web Security Context group and elsewhere has prompted me =
to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:
=20
1) Text Representation of Community Logos
=20
    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20
=20
    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.
=20
    This is not a problem for either the subject or the issuer since =
there are already=20
=20
2) Member Since attribute
=20
    This attribute would take a date as a parameter and would encode the =
first date at which the certified entity was issued a credential. The =
exact interpretation of this would be left to the CPS of the certificate =
issuer.
=20
3) No Padlock Icon attribute
=20
    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.
=20
    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.
=20
    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.
=20
    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.
=20
=20
Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.
=20
Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.
=20
We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.

------_=_NextPart_001_01C7A6CF.18E753C3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C Web=20
Security Context group and elsewhere has prompted me to consider that we =
need to=20
take the necessary steps to allow the following information to be =
encoded in=20
certificates in a consistent manner:</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
Representation of Community Logos</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is an accessibility issue. If a certificate is issued with =
an FDIC=20
community logo in it there has to be a way to present this information =
to blind=20
users, users with an audio browser, etc. etc. </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
logo slot. Alternatively we could encode the information in the image =
itself.=20
Alternatively we could specify an extension OID that simply takes a list =
of=20
community DNs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is not a problem for either the subject or the issuer =
since there=20
are already </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
Since attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would take a date as a parameter and would =
encode the=20
first date at which the certified entity was issued a credential. The =
exact=20
interpretation of this would be left to the CPS of the certificate=20
issuer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would allow a certificate to say that no user =
indication=20
should be specified in the chrome, nor should any nag screens. It would =
be an=20
option that the issuing CA would put in at their =
discretion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>The need for this is to allow a CA to support a wide range of=20
applications which&nbsp;require encryption but require even less =
authentication=20
than current schemes such as domain validated certs. For example self =
signed=20
certificates, certificates issued to embedded hardware, etc.=20
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>What I want to do is to get us to the point where the browser =
authors=20
feel comfortable with a user experience that does not contain the nag =
screens=20
that disfigure current schemes. In many cases all that is required is to =
turn on=20
encryption. The user does not need to be told that the certificate has =
expired,=20
has been issued by an unknown CA or any of the usual nonsense. just =
don't tell=20
the user that its safe in the first place and the browser does not need =
to say=20
that it is dangerous.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>Clearly this attribute is unnecessary from a technical point of =
view.=20
From a market point of view it is essential if we are going to ensure =
that=20
applications are doing the right thing. The padlock icon has some pretty =
strong=20
semantics. Many applications require less. We are not going to get =
everyone who=20
currently has a padlock certificate to get a green bar cert. So lets =
serve the=20
applications that require even less than the padlock without diluting =
the=20
padlock semantics further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Before =
writing up a=20
draft I would like to guage whether folk feel there is a need for any of =
these=20
and if so what the likely level of contention is, whether it can be =
completed=20
within PKIX or should it be a personal submission.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
here is the reservation of the OIDs under a neutral, non VeriSign arc. I =
don't=20
think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
and VeriSign might not be comfortable with them doing so=20
either.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We are =
definitely=20
going to require the first, the second seems to be considered a 'no =
brainer'=20
since it is information that every CA holds, that is not currently =
provided to=20
the user and is very very effective at providing security=20
context.</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C7A6CF.18E753C3--




From owner-ietf-pkix@mail.imc.org Mon Jun 04 15:45:34 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvIUg-0000T4-EW
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 15:45:34 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvIUf-0002Gv-LC
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 15:45:34 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54IpH8E058578
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 11:51:17 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54IpHUY058577;
	Mon, 4 Jun 2007 11:51:17 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp108.biz.mail.re2.yahoo.com (smtp108.biz.mail.re2.yahoo.com [206.190.52.47])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l54IpGWL058560
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 11:51:16 -0700 (MST)
	(envelope-from turners@ieca.com)
Received: (qmail 17244 invoked from network); 4 Jun 2007 18:51:12 -0000
Received: from unknown (HELO Wylie) (turners@ieca.com@70.108.15.46 with login)
  by smtp108.biz.mail.re2.yahoo.com with SMTP; 4 Jun 2007 18:51:11 -0000
X-YMail-OSG: Qs5z3cUVM1lIPs4KiX._6oDZwIS9hq.C_Z42X_vIIxAiaEmoy8FFT_gjo0i2GpA6YC6RkeMH0Cfl_FH4mSqjXhnERUL4RV9WjNkimTGVz70y9naunfCa4MlbP0oGr_Q4kW5Y7yLfF3JpcBk-
Reply-To: <turners@ieca.com>
From: "Turner, Sean P." <turners@ieca.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>,
        "'pkix'" <ietf-pkix@imc.org>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 14:44:28 -0400
Organization: IECA, Inc.
Message-ID: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00DF_01C7A6B6.DB0F2510"
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/w
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672


This is a multi-part message in MIME format.

------=_NextPart_000_00DF_01C7A6B6.DB0F2510
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Phil,
 
For the logos, can't we just use the logo types RFC
(http://ietf.org/rfc/rfc3709.txt).
 
spt

  _____  

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On
Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes


Work in the w3C Web Security Context group and elsewhere has prompted me to
consider that we need to take the necessary steps to allow the following
information to be encoded in certificates in a consistent manner:
 
1) Text Representation of Community Logos
 
    This is an accessibility issue. If a certificate is issued with an FDIC
community logo in it there has to be a way to present this information to
blind users, users with an audio browser, etc. etc. 
 
    One simple fix would be to simply allow for text/plain as a community
logo slot. Alternatively we could encode the information in the image
itself. Alternatively we could specify an extension OID that simply takes a
list of community DNs.
 
    This is not a problem for either the subject or the issuer since there
are already 
 
2) Member Since attribute
 
    This attribute would take a date as a parameter and would encode the
first date at which the certified entity was issued a credential. The exact
interpretation of this would be left to the CPS of the certificate issuer.
 
3) No Padlock Icon attribute
 
    This attribute would allow a certificate to say that no user indication
should be specified in the chrome, nor should any nag screens. It would be
an option that the issuing CA would put in at their discretion.
 
    The need for this is to allow a CA to support a wide range of
applications which require encryption but require even less authentication
than current schemes such as domain validated certs. For example self signed
certificates, certificates issued to embedded hardware, etc. etc.
 
    What I want to do is to get us to the point where the browser authors
feel comfortable with a user experience that does not contain the nag
screens that disfigure current schemes. In many cases all that is required
is to turn on encryption. The user does not need to be told that the
certificate has expired, has been issued by an unknown CA or any of the
usual nonsense. just don't tell the user that its safe in the first place
and the browser does not need to say that it is dangerous.
 
    Clearly this attribute is unnecessary from a technical point of view.
From a market point of view it is essential if we are going to ensure that
applications are doing the right thing. The padlock icon has some pretty
strong semantics. Many applications require less. We are not going to get
everyone who currently has a padlock certificate to get a green bar cert. So
lets serve the applications that require even less than the padlock without
diluting the padlock semantics further.
 
 
Before writing up a draft I would like to guage whether folk feel there is a
need for any of these and if so what the likely level of contention is,
whether it can be completed within PKIX or should it be a personal
submission.
 
Main thing I want here is the reservation of the OIDs under a neutral, non
VeriSign arc. I don't think that the rest of the industry would feel
comfortable using VeriSign OIDs and VeriSign might not be comfortable with
them doing so either.
 
We are definitely going to require the first, the second seems to be
considered a 'no brainer' since it is information that every CA holds, that
is not currently provided to the user and is very very effective at
providing security context.

------=_NextPart_000_00DF_01C7A6B6.DB0F2510
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Phil,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>For the logos, can't we just use the logo types =
RFC (<A=20
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>spt</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org=20
[mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Hallam-Baker,=20
Phillip<BR><B>Sent:</B> Monday, June 04, 2007 1:37 PM<BR><B>To:</B>=20
pkix<BR><B>Subject:</B> Three short fixes<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C Web=20
Security Context group and elsewhere has prompted me to consider that we =
need to=20
take the necessary steps to allow the following information to be =
encoded in=20
certificates in a consistent manner:</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
Representation of Community Logos</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is an accessibility issue. If a certificate is issued with =
an FDIC=20
community logo in it there has to be a way to present this information =
to blind=20
users, users with an audio browser, etc. etc. </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
logo slot. Alternatively we could encode the information in the image =
itself.=20
Alternatively we could specify an extension OID that simply takes a list =
of=20
community DNs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is not a problem for either the subject or the issuer =
since there=20
are already </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
Since attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would take a date as a parameter and would =
encode the=20
first date at which the certified entity was issued a credential. The =
exact=20
interpretation of this would be left to the CPS of the certificate=20
issuer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would allow a certificate to say that no user =
indication=20
should be specified in the chrome, nor should any nag screens. It would =
be an=20
option that the issuing CA would put in at their =
discretion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>The need for this is to allow a CA to support a wide range of=20
applications which&nbsp;require encryption but require even less =
authentication=20
than current schemes such as domain validated certs. For example self =
signed=20
certificates, certificates issued to embedded hardware, etc.=20
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>What I want to do is to get us to the point where the browser =
authors=20
feel comfortable with a user experience that does not contain the nag =
screens=20
that disfigure current schemes. In many cases all that is required is to =
turn on=20
encryption. The user does not need to be told that the certificate has =
expired,=20
has been issued by an unknown CA or any of the usual nonsense. just =
don't tell=20
the user that its safe in the first place and the browser does not need =
to say=20
that it is dangerous.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>Clearly this attribute is unnecessary from a technical point of =
view.=20
From a market point of view it is essential if we are going to ensure =
that=20
applications are doing the right thing. The padlock icon has some pretty =
strong=20
semantics. Many applications require less. We are not going to get =
everyone who=20
currently has a padlock certificate to get a green bar cert. So lets =
serve the=20
applications that require even less than the padlock without diluting =
the=20
padlock semantics further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Before =
writing up a=20
draft I would like to guage whether folk feel there is a need for any of =
these=20
and if so what the likely level of contention is, whether it can be =
completed=20
within PKIX or should it be a personal submission.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
here is the reservation of the OIDs under a neutral, non VeriSign arc. I =
don't=20
think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
and VeriSign might not be comfortable with them doing so=20
either.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We are =
definitely=20
going to require the first, the second seems to be considered a 'no =
brainer'=20
since it is information that every CA holds, that is not currently =
provided to=20
the user and is very very effective at providing security=20
context.</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_00DF_01C7A6B6.DB0F2510--





From owner-ietf-pkix@mail.imc.org Mon Jun 04 16:19:14 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJ1G-0007rG-LN
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 16:19:14 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJ1E-0000M7-QJ
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 16:19:14 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JNiXJ068454
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 12:23:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54JNiuh068453;
	Mon, 4 Jun 2007 12:23:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JNgIV068447
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 12:23:43 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l54JNcEF012801;
	Mon, 4 Jun 2007 12:23:38 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Jun 2007 12:23:38 -0700
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_01C7A6DD.DA444793"
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 12:22:27 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5E0B@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAFTxYA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: <turners@ieca.com>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 19:23:38.0225 (UTC) FILETIME=[DA352E10:01C7A6DD]
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 731ea0e9f5725b67e634db1918f3b951


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6DD.DA444793
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

No, in case I am not being clear here,
=20
The assumption is that we issue a certificate with the FDIC and Equal =
Opportunity lender LOGOTYPE images as community logos.
=20
Now how do I provide the same information to a non sighted reader? For =
Issuer and Subject logos I just pull the info out of the cert issuer and =
subject. I need a way to express the same info in text as the LOGOTYPE =
contains.


________________________________

	From: Turner, Sean P. [mailto:turners@ieca.com]=20
	Sent: Monday, June 04, 2007 2:44 PM
	To: Hallam-Baker, Phillip; 'pkix'
	Subject: RE: Three short fixes
=09
=09
	Phil,
	=20
	For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).
	=20
	spt

________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
	Sent: Monday, June 04, 2007 1:37 PM
	To: pkix
	Subject: Three short fixes
=09
=09
	Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:
	=20
	1) Text Representation of Community Logos
	=20
	    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20
	=20
	    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.
	=20
	    This is not a problem for either the subject or the issuer since =
there are already=20
	=20
	2) Member Since attribute
	=20
	    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.
	=20
	3) No Padlock Icon attribute
	=20
	    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.
	=20
	    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.
	=20
	    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.
	=20
	    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.
	=20
	=20
	Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.
	=20
	Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.
	=20
	We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A6DD.DA444793
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>No, in case I am not being clear =
here,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The assumption is that we issue a certificate =
with the FDIC=20
and Equal Opportunity lender LOGOTYPE images as community=20
logos.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Now how do I provide the same information to a =
non sighted=20
reader? For Issuer and Subject logos I just pull the info out of the =
cert issuer=20
and subject. I need a way to express the same info in text as the =
LOGOTYPE=20
contains.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Turner, Sean P.=20
  [mailto:turners@ieca.com] <BR><B>Sent:</B> Monday, June 04, 2007 2:44=20
  PM<BR><B>To:</B> Hallam-Baker, Phillip; 'pkix'<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Phil,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>For the logos, can't we just use the logo =
types RFC (<A=20
  =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>spt</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of =
</B>Hallam-Baker,=20
  Phillip<BR><B>Sent:</B> Monday, June 04, 2007 1:37 PM<BR><B>To:</B>=20
  pkix<BR><B>Subject:</B> Three short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C=20
  Web Security Context group and elsewhere has prompted me to consider =
that we=20
  need to take the necessary steps to allow the following information to =
be=20
  encoded in certificates in a consistent manner:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
  Representation of Community Logos</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This is an accessibility issue. If a certificate is issued =
with an FDIC=20
  community logo in it there has to be a way to present this information =
to=20
  blind users, users with an audio browser, etc. etc. =
</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
  logo slot. Alternatively we could encode the information in the image =
itself.=20
  Alternatively we could specify an extension OID that simply takes a =
list of=20
  community DNs.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This is not a problem for either the subject or the issuer =
since there=20
  are already </FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
  Since attribute</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This attribute would take a date as a parameter and would =
encode the=20
  first date at which the certified entity was issued a credential. The =
exact=20
  interpretation of this would be left to the CPS of the certificate=20
  issuer.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
  Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This attribute would allow a certificate to say that no user =
indication=20
  should be specified in the chrome, nor should any nag screens. It =
would be an=20
  option that the issuing CA would put in at their=20
  discretion.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>The need for this is to allow a CA to support a wide range of =

  applications which&nbsp;require encryption but require even less=20
  authentication than current schemes such as domain validated certs. =
For=20
  example self signed certificates, certificates issued to embedded =
hardware,=20
  etc. etc.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>What I want to do is to get us to the point where the browser =
authors=20
  feel comfortable with a user experience that does not contain the nag =
screens=20
  that disfigure current schemes. In many cases all that is required is =
to turn=20
  on encryption. The user does not need to be told that the certificate =
has=20
  expired, has been issued by an unknown CA or any of the usual =
nonsense. just=20
  don't tell the user that its safe in the first place and the browser =
does not=20
  need to say that it is dangerous.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>Clearly this attribute is unnecessary from a technical point =
of view.=20
  From a market point of view it is essential if we are going to ensure =
that=20
  applications are doing the right thing. The padlock icon has some =
pretty=20
  strong semantics. Many applications require less. We are not going to =
get=20
  everyone who currently has a padlock certificate to get a green bar =
cert. So=20
  lets serve the applications that require even less than the padlock =
without=20
  diluting the padlock semantics further.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2>Before writing up=20
  a draft I would like to guage whether folk feel there is a need for =
any of=20
  these and if so what the likely level of contention is, whether it can =
be=20
  completed within PKIX or should it be a personal=20
  submission.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
  here is the reservation of the OIDs under a neutral, non VeriSign arc. =
I don't=20
  think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
  and VeriSign might not be comfortable with them doing so=20
  either.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We =
are definitely=20
  going to require the first, the second seems to be considered a 'no =
brainer'=20
  since it is information that every CA holds, that is not currently =
provided to=20
  the user and is very very effective at providing security=20
  context.</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7A6DD.DA444793--




From owner-ietf-pkix@mail.imc.org Mon Jun 04 16:29:08 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvJAq-0003I1-8K
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 16:29:08 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvJAo-00022H-7A
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 16:29:08 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JdFBS073286
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 12:39:15 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54JdFVg073285;
	Mon, 4 Jun 2007 12:39:15 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail7.exchange.microsoft.com [131.107.1.27])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JdDHc073276
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 12:39:14 -0700 (MST)
	(envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-02.exchange.corp.microsoft.com (157.54.71.211) by
 DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft SMTP
 Server (TLS) id 8.1.122.1; Mon, 4 Jun 2007 12:39:13 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by
 df-bhd-02.exchange.corp.microsoft.com ([157.54.71.211]) with mapi; Mon, 4 Jun
 2007 12:39:13 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "turners@ieca.com" <turners@ieca.com>,
        "'Hallam-Baker, Phillip'"
	<pbaker@verisign.com>,
        "'pkix'" <ietf-pkix@imc.org>
Date: Mon, 4 Jun 2007 12:39:06 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvA=
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
 <00de01c7a6d8$6220c510$0301a8c0@Wylie>
In-Reply-To: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_"
MIME-Version: 1.0
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: e9eeacd7fe925d5f7faae01ed8f85b97


--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, RFC3709 already supports audio formats which was specifically added fo=
r accessibility scenarios such as visually impaired users.

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Turner, Sean P.
Sent: Monday, June 04, 2007 11:44 AM
To: 'Hallam-Baker, Phillip'; 'pkix'
Subject: RE: Three short fixes

Phil,

For the logos, can't we just use the logo types RFC (http://ietf.org/rfc/rf=
c3709.txt).

spt

________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes
Work in the w3C Web Security Context group and elsewhere has prompted me to=
 consider that we need to take the necessary steps to allow the following i=
nformation to be encoded in certificates in a consistent manner:

1) Text Representation of Community Logos

    This is an accessibility issue. If a certificate is issued with an FDIC=
 community logo in it there has to be a way to present this information to =
blind users, users with an audio browser, etc. etc.

    One simple fix would be to simply allow for text/plain as a community l=
ogo slot. Alternatively we could encode the information in the image itself=
. Alternatively we could specify an extension OID that simply takes a list =
of community DNs.

    This is not a problem for either the subject or the issuer since there =
are already

2) Member Since attribute

    This attribute would take a date as a parameter and would encode the fi=
rst date at which the certified entity was issued a credential. The exact i=
nterpretation of this would be left to the CPS of the certificate issuer.

3) No Padlock Icon attribute

    This attribute would allow a certificate to say that no user indication=
 should be specified in the chrome, nor should any nag screens. It would be=
 an option that the issuing CA would put in at their discretion.

    The need for this is to allow a CA to support a wide range of applicati=
ons which require encryption but require even less authentication than curr=
ent schemes such as domain validated certs. For example self signed certifi=
cates, certificates issued to embedded hardware, etc. etc.

    What I want to do is to get us to the point where the browser authors f=
eel comfortable with a user experience that does not contain the nag screen=
s that disfigure current schemes. In many cases all that is required is to =
turn on encryption. The user does not need to be told that the certificate =
has expired, has been issued by an unknown CA or any of the usual nonsense.=
 just don't tell the user that its safe in the first place and the browser =
does not need to say that it is dangerous.

    Clearly this attribute is unnecessary from a technical point of view. F=
rom a market point of view it is essential if we are going to ensure that a=
pplications are doing the right thing. The padlock icon has some pretty str=
ong semantics. Many applications require less. We are not going to get ever=
yone who currently has a padlock certificate to get a green bar cert. So le=
ts serve the applications that require even less than the padlock without d=
iluting the padlock semantics further.


Before writing up a draft I would like to guage whether folk feel there is =
a need for any of these and if so what the likely level of contention is, w=
hether it can be completed within PKIX or should it be a personal submissio=
n.

Main thing I want here is the reservation of the OIDs under a neutral, non =
VeriSign arc. I don't think that the rest of the industry would feel comfor=
table using VeriSign OIDs and VeriSign might not be comfortable with them d=
oing so either.

We are definitely going to require the first, the second seems to be consid=
ered a 'no brainer' since it is information that every CA holds, that is no=
t currently provided to the user and is very very effective at providing se=
curity context.

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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'>Yes, RFC3709 already supports audio formats which was specif=
ically
added for accessibility scenarios such as visually impaired users.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'> owner-ietf-pk=
ix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Turner, Sean P.<b=
r>
<b>Sent:</b> Monday, June 04, 2007 11:44 AM<br>
<b>To:</b> 'Hallam-Baker, Phillip'; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Phil,</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>For the logos, can't we just use the logo types RFC (<a
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt</a=
>).</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>spt</span><o:p></o:p></p>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Hallam-Baker, Phi=
llip<br>
<b>Sent:</b> Monday, June 04, 2007 1:37 PM<br>
<b>To:</b> pkix<br>
<b>Subject:</b> Three short fixes</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Work
in the w3C Web Security Context group and elsewhere has prompted me to cons=
ider
that we need to take the necessary steps to allow the following information=
 to
be encoded in certificates in a consistent manner:</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>1)
Text Representation of Community Logos</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is an accessibility issue. If a certificate is
issued with an FDIC community logo in it there has to be a way to present t=
his
information to blind users, users with an audio browser, etc. etc. </span><=
o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>One simple fix would be to simply allow for text/plai=
n as
a community logo slot. Alternatively we could encode the information in the
image itself. Alternatively we could specify an extension OID that simply t=
akes
a list of community DNs.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is not a problem for either the subject or the
issuer since there are already </span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>2)
Member Since attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would take a date as a parameter and w=
ould
encode the first date at which the certified entity was issued a credential=
.
The exact interpretation of this would be left to the CPS of the certificat=
e
issuer.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>3)
No Padlock Icon attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would allow a certificate to say that =
no
user indication should be specified in the chrome, nor should any nag scree=
ns.
It would be an option that the issuing CA would put in at their discretion.=
</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>The need for this is to allow a CA to support a wide
range of applications which&nbsp;require encryption but require even less
authentication than current schemes such as domain validated certs. For exa=
mple
self signed certificates, certificates issued to embedded hardware, etc. et=
c.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>What I want to do is to get us to the point where the
browser authors feel comfortable with a user experience that does not conta=
in
the nag screens that disfigure current schemes. In many cases all that is
required is to turn on encryption. The user does not need to be told that t=
he
certificate has expired, has been issued by an unknown CA or any of the usu=
al
nonsense. just don't tell the user that its safe in the first place and the
browser does not need to say that it is dangerous.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>Clearly this attribute is unnecessary from a technica=
l
point of view. From a market point of view it is essential if we are going =
to
ensure that applications are doing the right thing. The padlock icon has so=
me
pretty strong semantics. Many applications require less. We are not going t=
o
get everyone who currently has a padlock certificate to get a green bar cer=
t.
So lets serve the applications that require even less than the padlock with=
out
diluting the padlock semantics further.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Before
writing up a draft I would like to guage whether folk feel there is a need =
for
any of these and if so what the likely level of contention is, whether it c=
an
be completed within PKIX or should it be a personal submission.</span><o:p>=
</o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Main
thing I want here is the reservation of the OIDs under a neutral, non VeriS=
ign
arc. I don't think that the rest of the industry would feel comfortable usi=
ng
VeriSign OIDs and VeriSign might not be comfortable with them doing so eith=
er.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>We
are definitely going to require the first, the second seems to be considere=
d a
'no brainer' since it is information that every CA holds, that is not curre=
ntly
provided to the user and is very very effective at providing security conte=
xt.</span><o:p></o:p></p>

</div>

</div>

</div>

</body>

</html>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_--




From owner-ietf-pkix@mail.imc.org Mon Jun 04 17:57:54 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvKYk-0003j9-6U
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 17:57:54 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvKYj-0007nV-I4
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 17:57:54 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54L1fPB098330
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 14:01:41 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54L1fwS098328;
	Mon, 4 Jun 2007 14:01:41 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54L1efD098304
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 14:01:41 -0700 (MST)
	(envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8])
	by stingray.missi.ncsc.mil with SMTP id l54L1ejZ000285
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 17:01:40 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 04 Jun 2007 17:01:39 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 4 Jun 2007 17:01:39 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 17:01:39 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2g
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 21:01:39.0986 (UTC) FILETIME=[8C02AF20:01C7A6EB]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15218000
X-TM-AS-Result: : Yes--16.114000-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE1LTE1MDU2Ny03MDcy?=
	=?us-ascii?B?MDktNzAyNzI2LTcwNzg4Ny03MDE1NzYtNzA0NTY4LTcwMDUzNy03?=
	=?us-ascii?B?MDUxMDItMTA2NjYwLTcwNDQyNS03MDE4MzctNzAzNDY4LTcxMDYx?=
	=?us-ascii?B?MS03MDM1NDQtNzAwNzU2LTcwMzc4Mi03MDI0ODUtNzAzMzY2LTcw?=
	=?us-ascii?B?MjEwNi03MDUzODgtNzAwODY5LTcwOTM3Mi03MDk1ODQtNzAwNzQ5?=
	=?us-ascii?B?LTcwMDI5OC03MDAwNzMtMTM5NzA0LTcwODE5Ni03MDAzNDItMTEx?=
	=?us-ascii?B?NjA0LTE4ODExOS03MDYxMTAtNzAwMDE4LTcwMDAwNy03MDAwMTUt?=
	=?us-ascii?B?NzAwMDE3LTcwMDM2Mi0xODgxNDYtMTg4MTE4LTcwNTcxOC03MDE4?=
	=?us-ascii?B?MjctNzAwMjY0LTcwMjQ5Ny03MDAzNDUtNzA0MTQxLTcwMDczMi03?=
	=?us-ascii?B?MDEwMTItNzAwOTA3LTcwMTMwNi03MDI4MzgtNzAwNjIyLTcwMDE2?=
	=?us-ascii?B?MC0xODgxMjUtMTExNjA1LTcwMDA3NC03MDAxNDItNzAwMDc5LTE4?=
	=?us-ascii?B?ODEyNC0xMTE2MDgtMTg4MDU3LTE4ODA3OC0xMTE2MDMtMTExNjAx?=
	=?us-ascii?B?LTE0ODA1MA==?=
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771


This is a multi-part message in MIME format.

------=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A6EB.8BE92584"

------_=_NextPart_001_01C7A6EB.8BE92584
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

1) Text Representation of Community Logos

=20

Although RFC3709 currently has no support for ALT text,
LogotypeImageInfo and LogotypeAudioInfo could easily be modified to
include a text description field after the language field.  Although
audio could be used for visually impaired users, I agree with also
having a text option usable with screenreaders (and Lynx).

=20

2) Member Since attribute

=20

No objections to creating a PKIX OID for this.  Where would it be used -
as a directory attribute for subject alternative name?  A new PKIX
private extension seems like overkill for this purpose.

=20

3) No Padlock Icon attribute

=20

I do not believe PKIX should sponsor an attribute that tells a
certificate user to "ignore this certificate", e.g. "accept this
certificate even if it cannot be validated".  I don't object to
applications supporting unauthenticated encryption while making no
security claims.  But if the application is not going to authenticate an
encryption key, then the application should not be transmitting or
consuming certificates in the first place.  Saying "but TLS won't work
without certificates" is not a convincing argument - the TLS working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not
PKIX.


------_=_NextPart_001_01C7A6EB.8BE92584
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
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 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>1) Text Representation of Community =
Logos<o:p></o:p></span></font></b></strong></p>

<p class=3DMsoNormal><strong><b><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></b></strong></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Although RFC3709 currently has no =
support
for ALT text, LogotypeImageInfo and LogotypeAudioInfo could easily be =
modified
to include a text description field after the language field.&nbsp; =
Although audio
could be used for visually impaired users, I agree with also having a =
text
option usable with screenreaders (and =
Lynx).<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>2) Member Since =
attribute<o:p></o:p></span></font></b></strong></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>No objections to creating a PKIX =
OID for
this. &nbsp;Where would it be used &#8211; as a directory attribute for =
subject alternative
name? &nbsp;A new PKIX private extension seems like overkill for this =
purpose.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>3) No Padlock Icon =
attribute</span></font></b></strong><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I do not believe PKIX should =
sponsor an
attribute that tells a certificate user to &#8220;ignore this =
certificate&#8221;,
e.g. &#8220;accept this certificate even if it cannot be =
validated&#8221;. &nbsp;I
don&#8217;t object to applications supporting unauthenticated encryption =
while
making no security claims. &nbsp;But if the application is not going to =
authenticate
an encryption key, then the application should not be transmitting or =
consuming
certificates in the first place. &nbsp;Saying &#8220;but TLS won&#8217;t =
work
without certificates&#8221; is not a convincing argument &#8211; the TLS =
working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not =
PKIX.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7A6EB.8BE92584--

------=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb--




From owner-ietf-pkix@mail.imc.org Mon Jun 04 19:25:43 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvLvj-0001w7-5h
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 19:25:43 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvLvi-0002Sb-5i
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 19:25:43 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54MdAxo035042
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 15:39:10 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54MdAX2035041;
	Mon, 4 Jun 2007 15:39:10 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Md931035026
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 15:39:09 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33])
	by colibri.verisign.com (8.13.1/8.13.4) with ESMTP id l54Md6kY009303;
	Mon, 4 Jun 2007 15:39:06 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 4 Jun 2007 15:39:06 -0700
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_01C7A6F9.282F6B7B"
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 15:39:05 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Trevor Freeman" <trevorf@exchange.microsoft.com>, <turners@ieca.com>,
        "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 22:39:06.0052 (UTC) FILETIME=[28899040:01C7A6F9]
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: d67762704726a1bed57e7f4595960d34


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6F9.282F6B7B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Talking to folk it appears that audio is useful but not enough.=20
=20
How do I develop authentication criteria for audio? I am having a =
difficult enough time with images. And it also tips into the language =
issue.
=20
I can't render audio in braille for example. If it is in text or an =
X.500 DN I can render it in any medium I need.
=20
=20


________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
	Sent: Monday, June 04, 2007 3:39 PM
	To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
	Subject: RE: Three short fixes
=09
=09

	Yes, RFC3709 already supports audio formats which was specifically =
added for accessibility scenarios such as visually impaired users.

	=20

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Turner, Sean P.
	Sent: Monday, June 04, 2007 11:44 AM
	To: 'Hallam-Baker, Phillip'; 'pkix'
	Subject: RE: Three short fixes

	=20

	Phil,

	=20

	For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).

	=20

	spt

	=20

________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
	Sent: Monday, June 04, 2007 1:37 PM
	To: pkix
	Subject: Three short fixes

	Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:

	=20

	1) Text Representation of Community Logos

	=20

	    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20

	=20

	    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.

	=20

	    This is not a problem for either the subject or the issuer since =
there are already=20

	=20

	2) Member Since attribute

	=20

	    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.

	=20

	3) No Padlock Icon attribute

	=20

	    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.

	=20

	    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.

	=20

	    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.

	=20

	    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.

	=20

	=20

	Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.

	=20

	Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.

	=20

	We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A6F9.282F6B7B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =
=3D=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D =3D "DAV:" xmlns:x2 =
=3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
=3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" =
xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Talking to folk it appears that audio is useful =
but not=20
enough. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>How do I develop authentication criteria for =
audio? I am=20
having a difficult enough time with images. And it also tips into the =
language=20
issue.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I can't render audio in braille for example. If =
it is in=20
text or an X.500 DN I can render it in any medium I =
need.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D765402022-04062007></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Trevor=20
  Freeman<BR><B>Sent:</B> Monday, June 04, 2007 3:39 PM<BR><B>To:</B>=20
  turners@ieca.com; Hallam-Baker, Phillip; 'pkix'<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">Yes,=20
  RFC3709 already supports audio formats which was specifically added =
for=20
  accessibility scenarios such as visually impaired =
users.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
  owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
  Behalf Of </B>Turner, Sean P.<BR><B>Sent:</B> Monday, June 04, 2007 =
11:44=20
  AM<BR><B>To:</B> 'Hallam-Baker, Phillip'; 'pkix'<BR><B>Subject:</B> =
RE: Three=20
  short fixes<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Phil,</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">For=20
  the logos, can't we just use the logo types RFC (<A=20
  =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">spt</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
  <HR align=3Dcenter width=3D"100%" SIZE=3D2>
  </DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
  owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
  Behalf Of </B>Hallam-Baker, Phillip<BR><B>Sent:</B> Monday, June 04, =
2007 1:37=20
  PM<BR><B>To:</B> pkix<BR><B>Subject:</B> Three short=20
  fixes</SPAN><o:p></o:p></P>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Work in =
the w3C Web=20
  Security Context group and elsewhere has prompted me to consider that =
we need=20
  to take the necessary steps to allow the following information to be =
encoded=20
  in certificates in a consistent manner:</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">1) Text=20
  Representation of Community Logos</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
an=20
  accessibility issue. If a certificate is issued with an FDIC community =
logo in=20
  it there has to be a way to present this information to blind users, =
users=20
  with an audio browser, etc. etc. </SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">One =
simple fix=20
  would be to simply allow for text/plain as a community logo slot.=20
  Alternatively we could encode the information in the image itself.=20
  Alternatively we could specify an extension OID that simply takes a =
list of=20
  community DNs.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
not a=20
  problem for either the subject or the issuer since there are already=20
  </SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">2) Member =
Since=20
  attribute</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
  would take a date as a parameter and would encode the first date at =
which the=20
  certified entity was issued a credential. The exact interpretation of =
this=20
  would be left to the CPS of the certificate=20
issuer.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">3) No =
Padlock Icon=20
  attribute</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
  would allow a certificate to say that no user indication should be =
specified=20
  in the chrome, nor should any nag screens. It would be an option that =
the=20
  issuing CA would put in at their =
discretion.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">The need =
for this=20
  is to allow a CA to support a wide range of applications =
which&nbsp;require=20
  encryption but require even less authentication than current schemes =
such as=20
  domain validated certs. For example self signed certificates, =
certificates=20
  issued to embedded hardware, etc. etc.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">What I =
want to do=20
  is to get us to the point where the browser authors feel comfortable =
with a=20
  user experience that does not contain the nag screens that disfigure =
current=20
  schemes. In many cases all that is required is to turn on encryption. =
The user=20
  does not need to be told that the certificate has expired, has been =
issued by=20
  an unknown CA or any of the usual nonsense. just don't tell the user =
that its=20
  safe in the first place and the browser does not need to say that it =
is=20
  dangerous.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Clearly =
this=20
  attribute is unnecessary from a technical point of view. From a market =
point=20
  of view it is essential if we are going to ensure that applications =
are doing=20
  the right thing. The padlock icon has some pretty strong semantics. =
Many=20
  applications require less. We are not going to get everyone who =
currently has=20
  a padlock certificate to get a green bar cert. So lets serve the =
applications=20
  that require even less than the padlock without diluting the padlock =
semantics=20
  further.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Before =
writing up a=20
  draft I would like to guage whether folk feel there is a need for any =
of these=20
  and if so what the likely level of contention is, whether it can be =
completed=20
  within PKIX or should it be a personal =
submission.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Main =
thing I want=20
  here is the reservation of the OIDs under a neutral, non VeriSign arc. =
I don't=20
  think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
  and VeriSign might not be comfortable with them doing so=20
  either.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">We are =
definitely=20
  going to require the first, the second seems to be considered a 'no =
brainer'=20
  since it is information that every CA holds, that is not currently =
provided to=20
  the user and is very very effective at providing security=20
  =
context.</SPAN><o:p></o:p></P></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C7A6F9.282F6B7B--




From owner-ietf-pkix@mail.imc.org Mon Jun 04 20:27:13 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvMtF-0003gM-5f
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 20:27:13 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvMtE-00017W-1x
	for pkix-archive@lists.ietf.org; Mon, 04 Jun 2007 20:27:13 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54NgL1o059765
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 16:42:21 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54NgLnk059764;
	Mon, 4 Jun 2007 16:42:21 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail7.exchange.microsoft.com [131.107.1.27])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54NgJgA059746
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 16:42:19 -0700 (MST)
	(envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-01.exchange.corp.microsoft.com (157.54.54.216) by
 DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft SMTP
 Server (TLS) id 8.1.122.1; Mon, 4 Jun 2007 16:42:18 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by
 df-bhd-01.exchange.corp.microsoft.com ([157.54.54.216]) with mapi; Mon, 4 Jun
 2007 16:42:18 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "turners@ieca.com"
	<turners@ieca.com>, pkix <ietf-pkix@imc.org>
Date: Mon, 4 Jun 2007 16:42:10 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsAACMPXg
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
 <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_"
MIME-Version: 1.0
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 4824b9ef1b1988f2983d420e78cedc0a


--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would have thought audio is a more constrained problem for verification t=
han images. Saying you can build a procedure which verifies the rights some=
one to assert "foo bar" but you have difficulty building a procedure where =
someone verifies a wav file contains someone reading the text "foo bar" see=
ms hard to believe. However the set of logotypes defined by 3709 is extensi=
ble so you can define whatever logotypes you want for the audio browsers an=
d it does not need workgroup input.

From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
Sent: Monday, June 04, 2007 3:39 PM
To: Trevor Freeman; turners@ieca.com; pkix
Subject: RE: Three short fixes

Talking to folk it appears that audio is useful but not enough.

How do I develop authentication criteria for audio? I am having a difficult=
 enough time with images. And it also tips into the language issue.

I can't render audio in braille for example. If it is in text or an X.500 D=
N I can render it in any medium I need.



________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Trevor Freeman
Sent: Monday, June 04, 2007 3:39 PM
To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
Subject: RE: Three short fixes
Yes, RFC3709 already supports audio formats which was specifically added fo=
r accessibility scenarios such as visually impaired users.

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Turner, Sean P.
Sent: Monday, June 04, 2007 11:44 AM
To: 'Hallam-Baker, Phillip'; 'pkix'
Subject: RE: Three short fixes

Phil,

For the logos, can't we just use the logo types RFC (http://ietf.org/rfc/rf=
c3709.txt).

spt

________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes
Work in the w3C Web Security Context group and elsewhere has prompted me to=
 consider that we need to take the necessary steps to allow the following i=
nformation to be encoded in certificates in a consistent manner:

1) Text Representation of Community Logos

    This is an accessibility issue. If a certificate is issued with an FDIC=
 community logo in it there has to be a way to present this information to =
blind users, users with an audio browser, etc. etc.

    One simple fix would be to simply allow for text/plain as a community l=
ogo slot. Alternatively we could encode the information in the image itself=
. Alternatively we could specify an extension OID that simply takes a list =
of community DNs.

    This is not a problem for either the subject or the issuer since there =
are already

2) Member Since attribute

    This attribute would take a date as a parameter and would encode the fi=
rst date at which the certified entity was issued a credential. The exact i=
nterpretation of this would be left to the CPS of the certificate issuer.

3) No Padlock Icon attribute

    This attribute would allow a certificate to say that no user indication=
 should be specified in the chrome, nor should any nag screens. It would be=
 an option that the issuing CA would put in at their discretion.

    The need for this is to allow a CA to support a wide range of applicati=
ons which require encryption but require even less authentication than curr=
ent schemes such as domain validated certs. For example self signed certifi=
cates, certificates issued to embedded hardware, etc. etc.

    What I want to do is to get us to the point where the browser authors f=
eel comfortable with a user experience that does not contain the nag screen=
s that disfigure current schemes. In many cases all that is required is to =
turn on encryption. The user does not need to be told that the certificate =
has expired, has been issued by an unknown CA or any of the usual nonsense.=
 just don't tell the user that its safe in the first place and the browser =
does not need to say that it is dangerous.

    Clearly this attribute is unnecessary from a technical point of view. F=
rom a market point of view it is essential if we are going to ensure that a=
pplications are doing the right thing. The padlock icon has some pretty str=
ong semantics. Many applications require less. We are not going to get ever=
yone who currently has a padlock certificate to get a green bar cert. So le=
ts serve the applications that require even less than the padlock without d=
iluting the padlock semantics further.


Before writing up a draft I would like to guage whether folk feel there is =
a need for any of these and if so what the likely level of contention is, w=
hether it can be completed within PKIX or should it be a personal submissio=
n.

Main thing I want here is the reservation of the OIDs under a neutral, non =
VeriSign arc. I don't think that the rest of the industry would feel comfor=
table using VeriSign OIDs and VeriSign might not be comfortable with them d=
oing so either.

We are definitely going to require the first, the second seems to be consid=
ered a 'no brainer' since it is information that every CA holds, that is no=
t currently provided to the user and is very very effective at providing se=
curity context.

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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'>I would have thought audio is a more constrained problem for
verification than images. Saying you can build a procedure which verifies t=
he rights
someone to assert &#8220;foo bar&#8221; but you have difficulty building a =
procedure
where someone verifies a wav file contains someone reading the text &#8220;=
foo bar&#8221;
seems hard to believe. However the set of logotypes defined by 3709 is exte=
nsible
so you can define whatever logotypes you want for the audio browsers and it=
 does
not need workgroup input.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'> Hallam-Baker,
Phillip [mailto:pbaker@verisign.com] <br>
<b>Sent:</b> Monday, June 04, 2007 3:39 PM<br>
<b>To:</b> Trevor Freeman; turners@ieca.com; pkix<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Talking to folk it appears that audio is useful but not enough.=
 </span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>How do I develop authentication criteria for audio? I am having=
 a
difficult enough time with images. And it also tips into the language issue=
.</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>I can't render audio in braille for example. If it is in text o=
r an
X.500 DN I can render it in any medium I need.</span><o:p></o:p></p>

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

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

<blockquote style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0=
in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Trevor Freeman<br=
>
<b>Sent:</b> Monday, June 04, 2007 3:39 PM<br>
<b>To:</b> turners@ieca.com; Hallam-Baker, Phillip; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes</span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Yes, RFC3709 already supports audio formats which was
specifically added for accessibility scenarios such as visually impaired us=
ers.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'>
owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] <b>On Be=
half
Of </b>Turner, Sean P.<br>
<b>Sent:</b> Monday, June 04, 2007 11:44 AM<br>
<b>To:</b> 'Hallam-Baker, Phillip'; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Phil,</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>For the logos, can't we just use the logo types RFC (<a
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt</a=
>).</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>spt</span><o:p></o:p></p>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Hallam-Baker, Phi=
llip<br>
<b>Sent:</b> Monday, June 04, 2007 1:37 PM<br>
<b>To:</b> pkix<br>
<b>Subject:</b> Three short fixes</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Work
in the w3C Web Security Context group and elsewhere has prompted me to cons=
ider
that we need to take the necessary steps to allow the following information=
 to
be encoded in certificates in a consistent manner:</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>1)
Text Representation of Community Logos</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is an accessibility issue. If a certificate is
issued with an FDIC community logo in it there has to be a way to present t=
his
information to blind users, users with an audio browser, etc. etc. </span><=
o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>One simple fix would be to simply allow for text/plai=
n as
a community logo slot. Alternatively we could encode the information in the
image itself. Alternatively we could specify an extension OID that simply t=
akes
a list of community DNs.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is not a problem for either the subject or the
issuer since there are already </span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>2)
Member Since attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would take a date as a parameter and w=
ould
encode the first date at which the certified entity was issued a credential=
.
The exact interpretation of this would be left to the CPS of the certificat=
e
issuer.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>3)
No Padlock Icon attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would allow a certificate to say that =
no
user indication should be specified in the chrome, nor should any nag scree=
ns.
It would be an option that the issuing CA would put in at their discretion.=
</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>The need for this is to allow a CA to support a wide
range of applications which&nbsp;require encryption but require even less
authentication than current schemes such as domain validated certs. For exa=
mple
self signed certificates, certificates issued to embedded hardware, etc. et=
c.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>What I want to do is to get us to the point where the
browser authors feel comfortable with a user experience that does not conta=
in
the nag screens that disfigure current schemes. In many cases all that is
required is to turn on encryption. The user does not need to be told that t=
he
certificate has expired, has been issued by an unknown CA or any of the usu=
al
nonsense. just don't tell the user that its safe in the first place and the
browser does not need to say that it is dangerous.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>Clearly this attribute is unnecessary from a technica=
l
point of view. From a market point of view it is essential if we are going =
to
ensure that applications are doing the right thing. The padlock icon has so=
me
pretty strong semantics. Many applications require less. We are not going t=
o
get everyone who currently has a padlock certificate to get a green bar cer=
t.
So lets serve the applications that require even less than the padlock with=
out
diluting the padlock semantics further.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Before
writing up a draft I would like to guage whether folk feel there is a need =
for
any of these and if so what the likely level of contention is, whether it c=
an
be completed within PKIX or should it be a personal submission.</span><o:p>=
</o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Main
thing I want here is the reservation of the OIDs under a neutral, non VeriS=
ign
arc. I don't think that the rest of the industry would feel comfortable usi=
ng
VeriSign OIDs and VeriSign might not be comfortable with them doing so eith=
er.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>We
are definitely going to require the first, the second seems to be considere=
d a
'no brainer' since it is information that every CA holds, that is not curre=
ntly
provided to the user and is very very effective at providing security conte=
xt.</span><o:p></o:p></p>

</div>

</div>

</blockquote>

</div>

</div>

</body>

</html>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_--




From owner-ietf-pkix@mail.imc.org Tue Jun 05 03:38:36 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvTci-0007f7-4Y
	for pkix-archive@lists.ietf.org; Tue, 05 Jun 2007 03:38:36 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvTcg-0000p9-NT
	for pkix-archive@lists.ietf.org; Tue, 05 Jun 2007 03:38:36 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l556kaca009661
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 4 Jun 2007 23:46:36 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l556kafI009660;
	Mon, 4 Jun 2007 23:46:36 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l556kXoY009622
	for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 23:46:35 -0700 (MST)
	(envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000)
	id B56B6D98313; Tue,  5 Jun 2007 08:46:32 +0200 (CEST)
Date: Tue, 5 Jun 2007 08:46:32 +0200
From: Thomas Pornin <pornin@bolet.org>
To: pkix <ietf-pkix@imc.org>
Subject: Re: Three short fixes
Message-ID: <20070605064632.GA10490@localhost.localdomain>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com> <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
User-Agent: Mutt/1.5.11
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2


On Mon, Jun 04, 2007 at 05:01:39PM -0400, Kemp, David P. wrote:
> I do not believe PKIX should sponsor an attribute that tells a
> certificate user to "ignore this certificate", e.g. "accept this
> certificate even if it cannot be validated".

In all generality, the public key represented in a certificate is
obtained as a byproduct of path validation: for DSA-like public keys,
the public key parameters may be inherited from certificates higher in
the path. A stand-alone certificate may not contain by itself enough
data to represent a complete and usable public key. Of course, most
certificates in the wild contain RSA public keys, which are
self-contained. Nonetheless, using the contents of certificates outside
of the context of a certificate path is a kind of paradigm shift from
what X.509 usually does.


> Saying "but TLS won't work without certificates" is not a convincing
> argument - the TLS working group has made decisions regarding
> unauthenticated (and/or unencrypted) ciphersuites, and the place to
> revisit those decisions is there, not PKIX.

TLS 1.1 (RFC 4346) still documents the "DH_anon" ciphersuites which
allow for unauthenticated key exchange. They are marked as deprecated
because they are vulnerable to man-in-the-middle attacks (and you have a
quite unusual attack model if encryption is needed by active attacks are
not to be feared). But they still exist. Ideally, additional "RSA_anon"
cipher suites would be added, because RSA key exchange makes it much
easier for megahertz-impaired clients.


	--Thomas Pornin




From owner-ietf-pkix@mail.imc.org Wed Jun 06 13:54:32 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvziK-0005Vr-QZ
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:32 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvziJ-00050P-GH
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:32 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56GwjIB096564
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2007 09:58:45 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56Gwj28096563;
	Wed, 6 Jun 2007 09:58:45 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56Gwh9d096546
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 09:58:44 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35])
	by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l56Gweed008955;
	Wed, 6 Jun 2007 09:58:40 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 6 Jun 2007 09:58:40 -0700
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_01C7A85B.EEB36611"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 09:57:31 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6000@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsAACMPXgAFcVnrA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Trevor Freeman" <trevorf@exchange.microsoft.com>, <turners@ieca.com>,
        "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 16:58:40.0231 (UTC) FILETIME=[EEA01F70:01C7A85B]
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: c25c25eef92c03b403abac6c7c688517


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A85B.EEB36611
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I already have an authentication process for an X.500 DN. Seems like =
that is going to be the most efficient scheme.


________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
	Sent: Monday, June 04, 2007 7:42 PM
	To: Hallam-Baker, Phillip; turners@ieca.com; pkix
	Subject: RE: Three short fixes
=09
=09

	I would have thought audio is a more constrained problem for =
verification than images. Saying you can build a procedure which =
verifies the rights someone to assert "foo bar" but you have difficulty =
building a procedure where someone verifies a wav file contains someone =
reading the text "foo bar" seems hard to believe. However the set of =
logotypes defined by 3709 is extensible so you can define whatever =
logotypes you want for the audio browsers and it does not need workgroup =
input.

	=20

	From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]=20
	Sent: Monday, June 04, 2007 3:39 PM
	To: Trevor Freeman; turners@ieca.com; pkix
	Subject: RE: Three short fixes

	=20

	Talking to folk it appears that audio is useful but not enough.=20

	=20

	How do I develop authentication criteria for audio? I am having a =
difficult enough time with images. And it also tips into the language =
issue.

	=20

	I can't render audio in braille for example. If it is in text or an =
X.500 DN I can render it in any medium I need.

	=20

	=20

		=20

________________________________

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
		Sent: Monday, June 04, 2007 3:39 PM
		To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
		Subject: RE: Three short fixes

		Yes, RFC3709 already supports audio formats which was specifically =
added for accessibility scenarios such as visually impaired users.

		=20

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Turner, Sean P.
		Sent: Monday, June 04, 2007 11:44 AM
		To: 'Hallam-Baker, Phillip'; 'pkix'
		Subject: RE: Three short fixes

		=20

		Phil,

		=20

		For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).

		=20

		spt

		=20

________________________________

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
		Sent: Monday, June 04, 2007 1:37 PM
		To: pkix
		Subject: Three short fixes

		Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:

		=20

		1) Text Representation of Community Logos

		=20

		    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20

		=20

		    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.

		=20

		    This is not a problem for either the subject or the issuer since =
there are already=20

		=20

		2) Member Since attribute

		=20

		    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.

		=20

		3) No Padlock Icon attribute

		=20

		    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.

		=20

		    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.

		=20

		    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.

		=20

		    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.

		=20

		=20

		Before writing up a draft I would like to guage whether folk feel =
there is a need for any of these and if so what the likely level of =
contention is, whether it can be completed within PKIX or should it be a =
personal submission.

		=20

		Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.

		=20

		We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A85B.EEB36611
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =
=3D=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D =3D "DAV:" xmlns:x2 =
=3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
=3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" =
xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal
}
SPAN.EmailStyle19 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265555616-06062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I already have an authentication process for an =
X.500 DN.=20
Seems like that is going to be the most efficient=20
scheme.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Trevor=20
  Freeman<BR><B>Sent:</B> Monday, June 04, 2007 7:42 PM<BR><B>To:</B>=20
  Hallam-Baker, Phillip; turners@ieca.com; pkix<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">I=20
  would have thought audio is a more constrained problem for =
verification than=20
  images. Saying you can build a procedure which verifies the rights =
someone to=20
  assert =93foo bar=94 but you have difficulty building a procedure =
where someone=20
  verifies a wav file contains someone reading the text =93foo bar=94 =
seems hard to=20
  believe. However the set of logotypes defined by 3709 is extensible so =
you can=20
  define whatever logotypes you want for the audio browsers and it does =
not need=20
  workgroup input.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> =
Hallam-Baker,=20
  Phillip [mailto:pbaker@verisign.com] <BR><B>Sent:</B> Monday, June 04, =
2007=20
  3:39 PM<BR><B>To:</B> Trevor Freeman; turners@ieca.com;=20
  pkix<BR><B>Subject:</B> RE: Three short=20
fixes<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Talking=20
  to folk it appears that audio is useful but not enough. =
</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">How do=20
  I develop authentication criteria for audio? I am having a difficult =
enough=20
  time with images. And it also tips into the language=20
  issue.</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">I=20
  can't render audio in braille for example. If it is in text or an =
X.500 DN I=20
  can render it in any medium I need.</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Trevor Freeman<BR><B>Sent:</B> Monday, June 04, 2007 =
3:39=20
    PM<BR><B>To:</B> turners@ieca.com; Hallam-Baker, Phillip;=20
    'pkix'<BR><B>Subject:</B> RE: Three short =
fixes</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">Yes,=20
    RFC3709 already supports audio formats which was specifically added =
for=20
    accessibility scenarios such as visually impaired=20
    users.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <DIV>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
    <P class=3DMsoNormal><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Turner, Sean P.<BR><B>Sent:</B> Monday, June 04, 2007 =
11:44=20
    AM<BR><B>To:</B> 'Hallam-Baker, Phillip'; 'pkix'<BR><B>Subject:</B> =
RE:=20
    Three short fixes<o:p></o:p></SPAN></P></DIV></DIV>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Phil,</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">For=20
    the logos, can't we just use the logo types RFC (<A=20
    =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">spt</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Hallam-Baker, Phillip<BR><B>Sent:</B> Monday, June 04, =
2007=20
    1:37 PM<BR><B>To:</B> pkix<BR><B>Subject:</B> Three short=20
    fixes</SPAN><o:p></o:p></P>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Work in =
the w3C=20
    Web Security Context group and elsewhere has prompted me to consider =
that we=20
    need to take the necessary steps to allow the following information =
to be=20
    encoded in certificates in a consistent =
manner:</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">1) Text =

    Representation of Community =
Logos</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
an=20
    accessibility issue. If a certificate is issued with an FDIC =
community logo=20
    in it there has to be a way to present this information to blind =
users,=20
    users with an audio browser, etc. etc. </SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">One =
simple fix=20
    would be to simply allow for text/plain as a community logo slot.=20
    Alternatively we could encode the information in the image itself.=20
    Alternatively we could specify an extension OID that simply takes a =
list of=20
    community DNs.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
not a=20
    problem for either the subject or the issuer since there are already =

    </SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">2) =
Member Since=20
    attribute</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
    would take a date as a parameter and would encode the first date at =
which=20
    the certified entity was issued a credential. The exact =
interpretation of=20
    this would be left to the CPS of the certificate=20
    issuer.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">3) No =
Padlock=20
    Icon attribute</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
    would allow a certificate to say that no user indication should be =
specified=20
    in the chrome, nor should any nag screens. It would be an option =
that the=20
    issuing CA would put in at their =
discretion.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">The =
need for this=20
    is to allow a CA to support a wide range of applications =
which&nbsp;require=20
    encryption but require even less authentication than current schemes =
such as=20
    domain validated certs. For example self signed certificates, =
certificates=20
    issued to embedded hardware, etc. etc.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">What I =
want to do=20
    is to get us to the point where the browser authors feel comfortable =
with a=20
    user experience that does not contain the nag screens that disfigure =
current=20
    schemes. In many cases all that is required is to turn on =
encryption. The=20
    user does not need to be told that the certificate has expired, has =
been=20
    issued by an unknown CA or any of the usual nonsense. just don't =
tell the=20
    user that its safe in the first place and the browser does not need =
to say=20
    that it is dangerous.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Clearly =
this=20
    attribute is unnecessary from a technical point of view. From a =
market point=20
    of view it is essential if we are going to ensure that applications =
are=20
    doing the right thing. The padlock icon has some pretty strong =
semantics.=20
    Many applications require less. We are not going to get everyone who =

    currently has a padlock certificate to get a green bar cert. So lets =
serve=20
    the applications that require even less than the padlock without =
diluting=20
    the padlock semantics further.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Before =
writing up=20
    a draft I would like to guage whether folk feel there is a need for =
any of=20
    these and if so what the likely level of contention is, whether it =
can be=20
    completed within PKIX or should it be a personal=20
    submission.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Main =
thing I want=20
    here is the reservation of the OIDs under a neutral, non VeriSign =
arc. I=20
    don't think that the rest of the industry would feel comfortable =
using=20
    VeriSign OIDs and VeriSign might not be comfortable with them doing =
so=20
    either.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">We are =
definitely=20
    going to require the first, the second seems to be considered a 'no =
brainer'=20
    since it is information that every CA holds, that is not currently =
provided=20
    to the user and is very very effective at providing security=20
    =
context.</SPAN><o:p></o:p></P></DIV></DIV></BLOCKQUOTE></DIV></DIV></BLOC=
KQUOTE></BODY></HTML>

------_=_NextPart_001_01C7A85B.EEB36611--




From owner-ietf-pkix@mail.imc.org Wed Jun 06 13:54:32 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvziK-0005W3-Tz
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:32 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvziJ-00050O-GH
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:32 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H8VYN099520
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2007 10:08:31 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56H8VeP099519;
	Wed, 6 Jun 2007 10:08:31 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H8UpI099513
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 10:08:30 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l56H8Lvd004490;
	Wed, 6 Jun 2007 10:08:24 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 6 Jun 2007 10:08:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 10:07:14 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <20070605064632.GA10490@localhost.localdomain>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcenSVqu7Qxesz8PRwe9LBwZZsDSEgBE5obw
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Thomas Pornin" <pornin@bolet.org>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 17:08:23.0365 (UTC) FILETIME=[4A334F50:01C7A85D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l56H8VpH099514
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002


If you have a certificate that does not have sufficient information to establish encryption then you can't use encryption. I don't see the relevance of that fact. 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Thomas Pornin
> Sent: Tuesday, June 05, 2007 2:47 AM
> To: pkix
> Subject: Re: Three short fixes
> 
> 
> On Mon, Jun 04, 2007 at 05:01:39PM -0400, Kemp, David P. wrote:
> > I do not believe PKIX should sponsor an attribute that tells a 
> > certificate user to "ignore this certificate", e.g. "accept this 
> > certificate even if it cannot be validated".
> 
> In all generality, the public key represented in a 
> certificate is obtained as a byproduct of path validation: 
> for DSA-like public keys, the public key parameters may be 
> inherited from certificates higher in the path. A stand-alone 
> certificate may not contain by itself enough data to 
> represent a complete and usable public key. Of course, most 
> certificates in the wild contain RSA public keys, which are 
> self-contained. Nonetheless, using the contents of 
> certificates outside of the context of a certificate path is 
> a kind of paradigm shift from what X.509 usually does.
> 
> 
> > Saying "but TLS won't work without certificates" is not a 
> convincing 
> > argument - the TLS working group has made decisions regarding 
> > unauthenticated (and/or unencrypted) ciphersuites, and the place to 
> > revisit those decisions is there, not PKIX.
> 
> TLS 1.1 (RFC 4346) still documents the "DH_anon" ciphersuites 
> which allow for unauthenticated key exchange. They are marked 
> as deprecated because they are vulnerable to 
> man-in-the-middle attacks (and you have a quite unusual 
> attack model if encryption is needed by active attacks are 
> not to be feared). But they still exist. Ideally, additional 
> "RSA_anon"
> cipher suites would be added, because RSA key exchange makes 
> it much easier for megahertz-impaired clients.
> 
> 
> 	--Thomas Pornin
> 
> 




From owner-ietf-pkix@mail.imc.org Wed Jun 06 13:54:33 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvziL-0005WF-T2
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:33 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HvziL-00050U-98
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 13:54:33 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H6tQZ099045
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2007 10:06:56 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56H6tfo099044;
	Wed, 6 Jun 2007 10:06:55 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H6se8099036
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 10:06:55 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l56H6nci004280;
	Wed, 6 Jun 2007 10:06:52 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 6 Jun 2007 10:06:49 -0700
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_01C7A85D.1234E33F"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 10:05:40 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gAF9iywA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 17:06:49.0305 (UTC) FILETIME=[1222E490:01C7A85D]
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A85D.1234E33F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20

	3) No Padlock Icon attribute

	=20

	I do not believe PKIX should sponsor an attribute that tells a =
certificate user to "ignore this certificate", e.g. "accept this =
certificate even if it cannot be validated".  I don't object to =
applications supporting unauthenticated encryption while making no =
security claims.  But if the application is not going to authenticate an =
encryption key, then the application should not be transmitting or =
consuming certificates in the first place.  Saying "but TLS won't work =
without certificates" is not a convincing argument - the TLS working =
group has made decisions regarding unauthenticated (and/or unencrypted) =
ciphersuites, and the place to revisit those decisions is there, not =
PKIX.=20

	=20

The point here is precisely to allow a certificate to state 'there are =
no security claims being made here'.=20

=20

The user does not accept the certificate, the client application does. =
No user has ever checked a certificate path and no user ever will. The =
question is whether the client application should be telling the user =
that it is 'safe' or not.

=20

I don't see why we need to tell the user that encryption is being used =
unless they have explicitly said that they need confidentiality. Telling =
the user that there is encryption means also telling them about a whole =
range of failures and other error conditions.=20

=20

=20


------_=_NextPart_001_01C7A85D.1234E33F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV><FONT=20
face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DSection1>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">3) No Padlock Icon=20
  attribute</SPAN></FONT></B></STRONG><o:p></o:p></P></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: =
navy"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I do not =
believe PKIX=20
  should sponsor an attribute that tells a certificate user to =93ignore =
this=20
  certificate=94, e.g. =93accept this certificate even if it cannot be =
validated=94.=20
  &nbsp;I don=92t object to applications supporting unauthenticated =
encryption=20
  while making no security claims. &nbsp;But if the application is not =
going to=20
  authenticate an encryption key, then the application should not be=20
  transmitting or consuming certificates in the first place. =
&nbsp;Saying =93but=20
  TLS won=92t work without certificates=94 is not a convincing argument =
=96 the TLS=20
  working group has made decisions regarding unauthenticated (and/or=20
  unencrypted) ciphersuites, and the place to revisit those decisions is =
there,=20
  not PKIX.<FONT color=3D#0000ff><SPAN=20
  class=3D531105816-06062007>&nbsp;</SPAN></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
  color=3D#0000ff><SPAN=20
  =
class=3D531105816-06062007></SPAN></FONT></SPAN></FONT>&nbsp;</P></DIV></=
BLOCKQUOTE>
<P class=3DMsoNormal dir=3Dltr><FONT color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><SPAN class=3D531105816-06062007>The&nbsp;point here is =
precisely to=20
allow a certificate to state 'there are no security claims being made=20
here'.&nbsp;</SPAN></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN class=3D531105816-06062007>The user does not =
accept the=20
certificate, the client application does. No user has ever checked a =
certificate=20
path and no user ever will. The question is whether the client =
application=20
should be telling the user that it is 'safe' or=20
not.</SPAN></o:p></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN class=3D531105816-06062007>I don't see why we =
need to=20
tell the user that encryption is being used unless they have explicitly =
said=20
that they need confidentiality. Telling the user that there is =
encryption means=20
also telling them about a whole range of failures and other error =
conditions.=20
</SPAN></o:p></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P></=
BODY></HTML>

------_=_NextPart_001_01C7A85D.1234E33F--




From owner-ietf-pkix@mail.imc.org Wed Jun 06 15:20:27 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw13T-0005En-9n
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 15:20:27 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hw13R-0003mi-D6
	for pkix-archive@lists.ietf.org; Wed, 06 Jun 2007 15:20:27 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56IQk8r024649
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2007 11:26:46 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56IQkvr024648;
	Wed, 6 Jun 2007 11:26:46 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56IQjpr024631
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 11:26:46 -0700 (MST)
	(envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8])
	by stingray.missi.ncsc.mil with SMTP id l56IQhOZ006368
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 14:26:43 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Wed, 06 Jun 2007 14:26:42 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 6 Jun 2007 14:26:42 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 14:26:42 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C6BEB@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gAF9iywAAAHbvAA==
References: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil> <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 18:26:42.0754 (UTC) FILETIME=[3B412A20:01C7A868]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15222000
X-TM-AS-Result: : Yes--15.524700-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE1LTE1MDU2Ny03MDE1?=
	=?us-ascii?B?NzYtNzA1OTAxLTcwOTU4NC03MDIzNTgtNzAzMzY2LTcwMTQ1NS03?=
	=?us-ascii?B?MDEzOTQtNzAwNzU0LTcwMDI2Mi03MDIxMjYtNzAyOTY4LTcwNjQx?=
	=?us-ascii?B?Mi0xMTM2NjAtNzA3NDEwLTcwMjEwNi03MDMxNzYtMTIxNTM0LTcw?=
	=?us-ascii?B?MTkyNy03MDQxODktNzAwMDczLTcwMDIxNS03MDExNzUtNzAyNjI2?=
	=?us-ascii?B?LTcxMDYxMS03MDM1NDQtNzAwNzU2LTcwMzc4Mi03MDI0ODUtNzA1?=
	=?us-ascii?B?Mzg4LTcwMDg2OS03MDI3MjYtNzA5MzcyLTEwNTcwMC0xMDUwNDAt?=
	=?us-ascii?B?NzAxMTYzLTcwNDA0OS03MDQwNTUtNzAwNzQ5LTcwMDI5OC0xMzk3?=
	=?us-ascii?B?MDQtNzA4MTk2LTcwMDM0Mi0xMTE2MDQtMTg4MTE5LTcwNjExMC03?=
	=?us-ascii?B?MDAwMTgtNzAwMDA3LTcwMDAxNS03MDAwMTctNzAwMzYyLTE4ODEx?=
	=?us-ascii?B?OC0xODgxNDYtNzAwNzgyLTcwNjgxNy03MDI2MDktNzAzMzIxLTE4?=
	=?us-ascii?B?ODExNC0xODgwMzgtNzAwMzQ1LTcwNTcxOC03MDE4MjctNzAwMjY0?=
	=?us-ascii?B?LTcwMjQ5Ny03MDQ0MjUtNzA0MTQxLTcwMDczMi03MDEwMTItNzAw?=
	=?us-ascii?B?OTA3LTcwMTMwNi03MDI4MzgtNzAwNjIyLTcwMDE2MC0xODgxMjUt?=
	=?us-ascii?B?MTExNjA1LTcwMDA3NC03MDAxNDItNzAwMDc5LTE4ODEyNC0xODgw?=
	=?us-ascii?B?NzgtMTExNjA4LTcwMDUyOS03MDAwNzctNzAwODAyLTcwMTY2OS0x?=
	=?us-ascii?B?ODgwNTctNzA1NDk0LTE4ODAzNS03MDAxMDktMTQ4MDUw?=
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cd000eda3d43531d5b01b5d305410e3c


This is a multi-part message in MIME format.

------=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A868.3B35778E"

------_=_NextPart_001_01C7A868.3B35778E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

And my point is that there is no reason to use a certificate to say "no
security claims are being made".  You achieve the identical result (an
encrypted channel that makes no security claims) by using DH_ANON
encryption without transmitting, validating, or even issuing a
certificate.

=20

In other words, it is up to applications and encryption protocols to
support unauthenticated and unannounced encryption if they so desire.
Because no certificates are needed to support such applications, there
is no requirement for PKIX to profile such certificates.

=20

=20

=20

[phill]: If you have a certificate that does not have sufficient
information to establish encryption then you can't use encryption. I
don't see the relevance of that fact.

=20

A certificate only needs to have sufficient information to
"authenticate" encryption, not establish.  The amount of certified
information needed to "establish" an unauthenticated encryption key is
zero.    DH or RSA public keys and parameters can be made up on the fly
(ephemerally) or pre-stored (statically) and handshaked without ever
touching a CA.

=20

=20

  _____ =20

From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]=20
Sent: Wednesday, June 06, 2007 1:06 PM
To: Kemp, David P.; pkix
Subject: RE: Three short fixes

=20

=20

=20

3) No Padlock Icon attribute

=20

I do not believe PKIX should sponsor an attribute that tells a
certificate user to "ignore this certificate", e.g. "accept this
certificate even if it cannot be validated".  I don't object to
applications supporting unauthenticated encryption while making no
security claims.  But if the application is not going to authenticate an
encryption key, then the application should not be transmitting or
consuming certificates in the first place.  Saying "but TLS won't work
without certificates" is not a convincing argument - the TLS working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not
PKIX.=20

=20

The point here is precisely to allow a certificate to state 'there are
no security claims being made here'.=20

=20

The user does not accept the certificate, the client application does.
No user has ever checked a certificate path and no user ever will. The
question is whether the client application should be telling the user
that it is 'safe' or not.

=20

I don't see why we need to tell the user that encryption is being used
unless they have explicitly said that they need confidentiality. Telling
the user that there is encryption means also telling them about a whole
range of failures and other error conditions.=20

=20

=20


------_=_NextPart_001_01C7A868.3B35778E
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=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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>And my point is that there is no =
reason to
use a certificate to say &#8220;no security claims are being =
made&#8221;. &nbsp;You
achieve the identical result (an encrypted channel that makes no =
security
claims) by using DH_ANON encryption without transmitting, validating, or =
even
issuing a certificate.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In other words, it is up to =
applications
and encryption protocols to support unauthenticated and unannounced =
encryption
if they so desire. &nbsp;Because no certificates are needed to support =
such
applications, there is no requirement for PKIX to profile such =
certificates.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>[phill]:
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>If you have a certificate that does not have
sufficient information to establish encryption then you can't use =
encryption. I
don't see the relevance of that fact.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>A certificate only needs to have
sufficient information to &#8220;authenticate&#8221; encryption, not =
establish.
&nbsp;The amount of certified information needed to =
&#8220;establish&#8221; an
unauthenticated encryption key is zero. &nbsp;&nbsp;&nbsp;DH or RSA =
public keys and parameters
can be made up on the fly (ephemerally) or pre-stored (statically) and
handshaked without ever touching a CA.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Hallam-Baker,
Phillip [mailto:pbaker@verisign.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, June 06, =
2007
1:06 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Kemp, David P.; =
pkix<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Three short =
fixes</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>3) No Padlock Icon =
attribute</span></font></b></strong><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I do not believe PKIX should =
sponsor an
attribute that tells a certificate user to &#8220;ignore this
certificate&#8221;, e.g. &#8220;accept this certificate even if it =
cannot be
validated&#8221;. &nbsp;I don&#8217;t object to applications supporting
unauthenticated encryption while making no security claims. &nbsp;But if =
the
application is not going to authenticate an encryption key, then the
application should not be transmitting or consuming certificates in the =
first
place. &nbsp;Saying &#8220;but TLS won&#8217;t work without =
certificates&#8221;
is not a convincing argument &#8211; the TLS working group has made =
decisions
regarding unauthenticated (and/or unencrypted) ciphersuites, and the =
place to
revisit those decisions is there, not PKIX.</span></font><font size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</blockquote>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The&nbsp;point here is precisely to =
allow
a certificate to state 'there are no security claims being made =
here'.&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The user does not accept the =
certificate,
the client application does. No user has ever checked a certificate path =
and no
user ever will. The question is whether the client application should be
telling the user that it is 'safe' or not.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I don't see why we need to tell the =
user
that encryption is being used unless they have explicitly said that they =
need
confidentiality. Telling the user that there is encryption means also =
telling
them about a whole range of failures and other error conditions. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7A868.3B35778E--

------=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19--




From owner-ietf-pkix@mail.imc.org Thu Jun 07 03:58:31 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwCt5-0006pe-Og
	for pkix-archive@lists.ietf.org; Thu, 07 Jun 2007 03:58:31 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwCt4-0002gx-Az
	for pkix-archive@lists.ietf.org; Thu, 07 Jun 2007 03:58:31 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l576uKr5098600
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 6 Jun 2007 23:56:20 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l576uK4s098599;
	Wed, 6 Jun 2007 23:56:20 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l576uGBY098564
	for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 23:56:19 -0700 (MST)
	(envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000)
	id D4890D98634; Thu,  7 Jun 2007 08:56:13 +0200 (CEST)
Date: Thu, 7 Jun 2007 08:56:13 +0200
From: Thomas Pornin <pornin@bolet.org>
To: pkix <ietf-pkix@imc.org>
Subject: Re: Three short fixes
Message-ID: <20070607065613.GA2663@localhost.localdomain>
References: <20070605064632.GA10490@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.5.11
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034


On Wed, Jun 06, 2007 at 10:07:14AM -0700, Hallam-Baker, Phillip wrote:
> If you have a certificate that does not have sufficient information to
> establish encryption then you can't use encryption. I don't see the
> relevance of that fact. 

The point is that certificates are meant to be used only after a
complete path validation, and the "sufficient information to establish
encryption" is computed by the validation procedure. It so happens that
for some public key types, you may extract the public key from a lone
certificate, but nothing in X.509 was optimized for such usage.

Another way to see your proposal is the following: what you suggest is
that the server encodes its public key into something which looks like a
certificate. The server adds issuer and subject X.500 names, a serial
number, validity dates, a signature, and a bunch of extensions,
including one which states that all this added information is rubbish
and the client should just extract the public key and ignore everything
else in that "certificate". This strikes me as unnecessarily
inefficient: the server adds several layers of data, making the whole
object fatter and more complex, just so that the client gets rid of that
extra data. It would be much more efficient, especially network-wise, to
just send the server public key without bothering at all with encodings
which look like certificates and hundreds of bytes whose sole fate is to
be utterly ignored by the receiver.

And, lo and behold, SSL/TLS already has cipher suites where a simple
public key is transmitted, with no X.509 implication at all. These are
named "DH_anon". These cipher suites do what you ask for, and do it
faster and better than what your proposal would imply.


	--Thomas Pornin




From owner-ietf-pkix@mail.imc.org Thu Jun 07 06:16:24 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwF2W-0005AF-8h
	for pkix-archive@lists.ietf.org; Thu, 07 Jun 2007 06:16:24 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwF2U-0000Oh-SJ
	for pkix-archive@lists.ietf.org; Thu, 07 Jun 2007 06:16:24 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l579JTEj036269
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 7 Jun 2007 02:19:29 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l579JTWh036268;
	Thu, 7 Jun 2007 02:19:29 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (curly.its.auckland.ac.nz [130.216.12.33])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l579JSLN036262
	for <ietf-pkix@imc.org>; Thu, 7 Jun 2007 02:19:28 -0700 (MST)
	(envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 3240B9C354;
	Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (curly.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id YNFZQzb3BNHW; Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 189929C352;
	Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33])
	by iris.cs.auckland.ac.nz (Postfix) with ESMTP
	id 026BDD14CFA; Thu,  7 Jun 2007 21:19:24 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian))
	id 1HwE9T-000804-00; Thu, 07 Jun 2007 21:19:31 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org, pbaker@verisign.com
Subject: RE: Three short fixes
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Message-Id: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
Date: Thu, 07 Jun 2007 21:19:31 +1200
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>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad


"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>The point here is precisely to allow a certificate to state 'there are no
>security claims being made here'.

So is the intent to create an attribute that says "This certificate is merely
a convenient universally-accepted blob for communicating a public key and a
name/email address/URL"?  In other words it's not really TLS-specific?

Peter.





From odcqxzgphx@rrmf.org Fri Jun 08 17:00:31 2007
Return-path: <odcqxzgphx@rrmf.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwlZP-00062z-2m; Fri, 08 Jun 2007 17:00:31 -0400
Received: from [207.199.229.175] (helo=YOUR-XB2X7J77GN)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HwlZN-0007p4-Mx; Fri, 08 Jun 2007 17:00:30 -0400
Message-ID: <76617559254982.9873585FF7@AMRPLE>
From: "Arnold Villarreal" <kwsxdukpbra@rrhsalumni.com>
To: <pkix-archive@megatron.ietf.org>
Subject: A source of anxiety for their partners
Date: Fri, 8 Jun 2007 15:57:53 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: qI0cncHyhv2KPdwV6y9WpdOaPqurCXTqQ0qZ
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc

<font size="3" face="Times New Roman">
<p>
<font face="Georgia" 
color="#339966" size="6">
<strong>Restore your sex life, or just
 give it a little kick.</strong>
</font>
</p>
<p>
<font face="Georgia">Erectile dysfunction (ED), sometimes referred 
to as impotence, is the inability for a sexually active male to obtain 
and sustain an erection for sexual purposes. In the past, this has been 
very embarrassing for
 men, and a source of anxiety for their partners, 
and, in fact, there has been very little diagnostic testing or treatment
options available 
until very recently.
</font></p>
<p>
<font face="Georgia" color="#993300" size="5"><strong>Viagra 
can help you!
</strong>
</font>
</p>
<p>
<font face="Georgia">
<strong>The benefits of 
Viagra:
</strong></font>
</p>
<ul id="list">
<li class="even">
<font face="Georgia">Helps men with ED achieve better
 erections 
</font>
</li>
<li class="odd"><font face="Georgia">Helps men 
with ED maintain 
an erection during sex 
</font></li>
<li class="even"><font face="Georgia">Can work in as little
 as 
14 minutes 
</font>
</li>
   
<li class="odd">
<font face="Georgia">Viagra-induced erections 
satisfy
 the partners of men with ED 
</font>
</li>
  
<li class="even">
<font face="Georgia">Has a proven safety 
record
</font>
</li>
    <li class="odd">
<font face="Georgia">Works for men 
with ED who 
also have a wide range of health issues 
</font></li>
   
<li class="odd">
<font face="Georgia">Can be taken with other 
medications 
</font>
</li>
<li class="odd"><font face="Georgia">As safe for your 
heart as a
 sugar pill </font>
</li>
</ul>
<p>
<font face="Georgia" color="#ff0000" size="5">
<strong>
<a 
href="http://NTk2OTBhN2Q1YzI2YTE2ZTk4ZTAwMzY2.ncmohuney.com">http://NTk2OTBhN2Q1YzI2YTE2ZTk4ZTAwMzY2.ncmohuney.com</a>
</strong>
</font></p>
</font>




From owner-ietf-pkix@mail.imc.org Sat Jun 09 13:02:53 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hx4KO-0006Tx-5l
	for pkix-archive@lists.ietf.org; Sat, 09 Jun 2007 13:02:16 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hx48K-0006a0-PV
	for pkix-archive@lists.ietf.org; Sat, 09 Jun 2007 12:49:50 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l59FrPeA039073
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 9 Jun 2007 08:53:25 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l59FrPn1039072;
	Sat, 9 Jun 2007 08:53:25 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp103.biz.mail.re2.yahoo.com (smtp103.biz.mail.re2.yahoo.com [68.142.229.217])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l59FrLGM039035
	for <ietf-pkix@imc.org>; Sat, 9 Jun 2007 08:53:23 -0700 (MST)
	(envelope-from turners@ieca.com)
Received: (qmail 63898 invoked from network); 9 Jun 2007 15:53:12 -0000
Received: from unknown (HELO Wylie) (turners@ieca.com@70.108.2.7 with login)
  by smtp103.biz.mail.re2.yahoo.com with SMTP; 9 Jun 2007 15:53:12 -0000
X-YMail-OSG: aR1yhKAVM1lDi7YcZRk1MosD.MyDxNuY.Ca1cUjCmlr6qpCLBz5Km9lpD316TTOdAfwkGnteb78PVGnWUznZnB3TQJDxaOTfcKl8uYatvzCiLQzfmKs-
Reply-To: <turners@ieca.com>
From: "Turner, Sean P." <turners@ieca.com>
To: "'pkix'" <ietf-pkix@imc.org>
Subject: New mailing list and potential BOF: trust anchor management
Date: Sat, 9 Jun 2007 11:46:03 -0400
Organization: IECA, Inc.
Message-ID: <007201c7aaad$4918e1a0$0301a8c0@Wylie>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceqrUi7psFA1IzaQFqxkMF3plxpSg==
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8


A mailing list has been established to discuss a standard protocol for trust
anchor management.  Numerous groups within the IETF (e.g., PKIX, SIDR, and
Kerberos) have all indicated a need for trust anchor management, but that it
is outside of their documents.

A BOF to discuss this has been proposed for IETF 69 in Chicago.

Subscription information for the ietf-trust-anchor mailing list can be found
at:
<http://www.vpnc.org/ietf-trust-anchor/>.

A description of the problem statement can be found at:
<http://www.ietf.org/internet-drafts/draft-wallace-ta-mgmt-problem-statement
-00.txt>.

spt 






From owner-ietf-pkix@mail.imc.org Sun Jun 10 10:42:12 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxOcO-0004fM-Nq
	for pkix-archive@lists.ietf.org; Sun, 10 Jun 2007 10:42:12 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxOcM-0004wD-8h
	for pkix-archive@lists.ietf.org; Sun, 10 Jun 2007 10:42:12 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5ADkpeE016564
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 10 Jun 2007 06:46:51 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5ADkpYv016563;
	Sun, 10 Jun 2007 06:46:51 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mx1.kent.ac.uk (mx1.kent.ac.uk [129.12.21.39])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5ADknnZ016548
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ietf-pkix@imc.org>; Sun, 10 Jun 2007 06:46:51 -0700 (MST)
	(envelope-from d.w.chadwick@kent.ac.uk)
Received: from c-24-8-221-135.hsd1.co.comcast.net ([24.8.221.135] helo=[10.1.10.120])
	by mx1.kent.ac.uk with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.62)
	(envelope-from <d.w.chadwick@kent.ac.uk>)
	id 1HxNkZ-0002Fy-6j
	for ietf-pkix@imc.org; Sun, 10 Jun 2007 14:46:35 +0100
Message-ID: <466C00B4.6070308@kent.ac.uk>
Date: Sun, 10 Jun 2007 14:46:28 +0100
From: David Chadwick <d.w.chadwick@kent.ac.uk>
Organization: University of Kent
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: PKIX <ietf-pkix@imc.org>
Subject: Use of WebDAV for X.509
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-UKC-Mail-System: No virus detected
X-UKC-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5,
	autolearn=disabled, ALL_TRUSTED -1.44)
X-UKC-MailScanner-From: d.w.chadwick@kent.ac.uk
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4


Dear WG

I have published a new ID at

http://www.ietf.org/internet-drafts/draft-chadwick-webdav-00.txt

This document describes the use of the WebDAV protocol for publishing
and revoking X.509 public key certificates and specifies two new access
methods for the Authority Information Access extension to support this.

WebDAV is an extension of HTTP, and allows certificates and CRLs to be 
published on Web servers such as Apache, rather than (or as well as) in 
LDAP servers, since we all know that LDAP servers are often not 
accessible on the Internet.

I should like the WG to consider including this work in its charter, and 
would appreciate comments on this draft either to me in person or to the 
PKIX list.

regards

David



*****************************************************************
David W. Chadwick, BSc PhD
Professor of Information Systems Security
The Computing Laboratory, University of Kent, Canterbury, CT2 7NF
Skype Name: davidwchadwick
Tel: +44 1227 82 3221
Fax +44 1227 762 811
Mobile: +44 77 96 44 7184
Email: D.W.Chadwick@kent.ac.uk
Home Page: http://www.cs.kent.ac.uk/people/staff/dwc8/index.html
Research Web site: http://www.cs.kent.ac.uk/research/groups/iss/index.html
Entrust key validation string: MLJ9-DU5T-HV8J
PGP Key ID is 0xBC238DE5

*****************************************************************




From owner-ietf-pkix@mail.imc.org Mon Jun 11 11:21:17 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxlhl-0008PF-UR
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 11:21:17 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxlhk-0002U0-H2
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 11:21:17 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BEPMBw046128
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 07:25:22 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BEPMer046127;
	Mon, 11 Jun 2007 07:25:22 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BEPJdb046119
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 07:25:19 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5BEPA2w014529;
	Mon, 11 Jun 2007 07:25:11 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jun 2007 07:25:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 07:23:56 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Aceo5PPkQ+niKfZUQ36auwffVIOhhwDTeP5w
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "pgut001" <pgut001@cs.auckland.ac.nz>, <DPKemp@missi.ncsc.mil>,
        <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 14:25:10.0456 (UTC) FILETIME=[513CBB80:01C7AC34]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BEPJda046120
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17


I don't see why I should appologize for a fix for being 'centered' on the only X.509 prototocol that can be regarded as a real success. 

The reason for using a certificate is to allow for backwards compatibility with a billion installed browsers. The dilution of trust is inevitable, all it takes to get a WebTrust audit is to do what you say. Eventually someone is going to get a WebTrust audit on the null CPS.


I want to be able to issue device SSL certs. People want to buy them. All that I want to do here is to make sure that they can be distinguished from certs people are using to take credit cards.

I can give you a cast iron chain for an EUI48 MAC address. But it says nothing that should give an end user warm fuzzies.


'This cert makes no security claims that are worth display to an end user'.

> -----Original Message-----
> From: pgut001 [mailto:pgut001@cs.auckland.ac.nz] 
> Sent: Thursday, June 07, 2007 5:20 AM
> To: DPKemp@missi.ncsc.mil; ietf-pkix@imc.org; Hallam-Baker, Phillip
> Subject: RE: Three short fixes
> 
> "Hallam-Baker, Phillip" <pbaker@verisign.com> writes:
> 
> >The point here is precisely to allow a certificate to state 
> 'there are 
> >no security claims being made here'.
> 
> So is the intent to create an attribute that says "This 
> certificate is merely a convenient universally-accepted blob 
> for communicating a public key and a name/email address/URL"? 
>  In other words it's not really TLS-specific?
> 
> Peter.
> 
> 
> 




From owner-ietf-pkix@mail.imc.org Mon Jun 11 12:30:27 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxmmg-0000L8-UU
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:30:27 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxmmf-0004CU-FF
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:30:26 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BFjGDu057091
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 08:45:16 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BFjGPR057090;
	Mon, 11 Jun 2007 08:45:16 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (moe.its.auckland.ac.nz [130.216.12.35])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BFjEQK057081
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 08:45:15 -0700 (MST)
	(envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 222304801BD;
	Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IO5kz+3YIxn5; Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 081DD4801B0;
	Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33])
	by iris.cs.auckland.ac.nz (Postfix) with ESMTP
	id E3AD61280A1; Tue, 12 Jun 2007 03:45:12 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian))
	id 1Hxm54-00085O-00; Tue, 12 Jun 2007 03:45:22 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org, pbaker@verisign.com,
        pgut001@cs.auckland.ac.nz
Subject: RE: Three short fixes
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Message-Id: <E1Hxm54-00085O-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 03:45:22 +1200
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>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d


"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>I don't see why I should appologize for a fix for being 'centered' on the
>only X.509 prototocol that can be regarded as a real success.

Uhh... who was that intended for?  It doesn't seem to be a response to my
message that you've quoted.

>'This cert makes no security claims that are worth display to an end user'.

As it turns out I've already got an OID out there for just such an extension,
which I added after constant user requests (that is, they didn't specifically
ask for this, but said that all they needed from a cert was a universally-
recognised bit bag for public keys, and they needed some way to tag it so that
relying parties could tell that it was just a no-semantics-attached bit bag).
So if Verisign needs a vendor-neutral OID, you can use mine, assuming that's
what you want (you didn't really answer my question below).

> So is the intent to create an attribute that says "This
> certificate is merely a convenient universally-accepted blob
> for communicating a public key and a name/email address/URL"?

In response to that I got several private-mail comments saying things like
"That's the default action for certificates isn't it?" and "How does this
differ from the current situation" :-).

Peter.




From owner-ietf-pkix@mail.imc.org Mon Jun 11 12:49:12 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxn4q-0001R0-QB
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:49:12 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxn4q-0006to-BA
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:49:12 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BG6Qq3061901
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 09:06:26 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BG6QQh061900;
	Mon, 11 Jun 2007 09:06:26 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BG6OTr061894
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 09:06:25 -0700 (MST)
	(envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8])
	by stingray.missi.ncsc.mil with SMTP id l5BG6NRg020853
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 12:06:24 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 11 Jun 2007 12:06:23 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 11 Jun 2007 12:06:23 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 12:06:22 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
In-Reply-To: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Aceo5PYyGdvxM0iuT9S2MjuukyYxMwDVcyzQ
References: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com> <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 16:06:23.0738 (UTC) FILETIME=[753205A0:01C7AC42]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15232000
X-TM-AS-Result: : Yes--6.444900-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE4LTE1MDU2Ny03MDU5?=
	=?us-ascii?B?MDEtNzAzMzU1LTcwNjc5MS03MDc1NTMtNzAyMTA2LTcwMTU3Ni03?=
	=?us-ascii?B?MDA2MTgtNzA2ODE3LTcwOTU4NC03MDA2NjEtNzAzMDg4LTcwNTM3?=
	=?us-ascii?B?NC03MDEwMDEtNzA3MTYzLTcwMTYxOC03MDY0NTQtMTE0NTQ3LTcw?=
	=?us-ascii?B?MTkyOC03MDQ5OTQtNzAyMDQ0LTcwMjkyMC0xMDY2NjAtNzAyMTEz?=
	=?us-ascii?B?LTcwMDMyNC03MDAxMDQtNzA0NzEyLTcwMDc3MS03MDU4NjEtNzA4?=
	=?us-ascii?B?NjU1LTcwMjk1Ny0xMzkwMDYtNzAwMjE1LTcwMTE3NS03MDQxODkt?=
	=?us-ascii?B?NzAwMDczLTcwMjYyNi03MDM3MzEtMTM5MDEwLTEwNTcwMC0xMDUw?=
	=?us-ascii?B?NDAtNzAzMzY2LTE0ODA1MA==?=
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BG6PTr061895
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c


More to the point, the intent is to create an attribute that says:

  "This certificate is merely a convenient universally-accepted
   blob for communicating a public key and a name/email address/URL"
*AND*
  "There is no claim that the public key and the name/email/URL
   have any relationship whatsoever"

In other words, the name/email/URL could belong to Bank of America
but the key pair and certificate request could have been created by
Phish-R-Us, and no claims to the contrary are made by the issuer.
Unfortunately, the mere existence of a certificate implies such
a claim even if it is disclaimed by an extension.

Saying "CAs want to sell no-claim certificates and server operators
want to buy them" ignores the societal cost of issuing certificates
that can be used to promote phishing.

If the extension MUST be marked critical, and if the certificate
MUST be rejected if subject name is non-null, and if the certificate
MUST be rejected if any other extension (including SAN) is present,
then perhaps there is less danger that current TLS applications
would be misled by the existence of such certificates.  But the
safer approach is to not issue them in the first place, particularly
since alternatives (anonymous ciphersuites) already exist.



-----Original Message-----
From: pgut001 [mailto:pgut001@cs.auckland.ac.nz] 
Sent: Thursday, June 07, 2007 5:20 AM
To: Kemp, David P.; ietf-pkix@imc.org; pbaker@verisign.com
Subject: RE: Three short fixes

"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>The point here is precisely to allow a certificate to state 'there are
no
>security claims being made here'.

So is the intent to create an attribute that says "This certificate is
merely
a convenient universally-accepted blob for communicating a public key
and a
name/email address/URL"?  In other words it's not really TLS-specific?

Peter.






From owner-ietf-pkix@mail.imc.org Mon Jun 11 12:49:13 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxn4r-0001RC-RY
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:49:13 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxn4r-0006tt-Bj
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 12:49:13 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BGBgex063170
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 09:11:42 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BGBgHM063169;
	Mon, 11 Jun 2007 09:11:42 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BGBeJc063145
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 09:11:41 -0700 (MST)
	(envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000)
	id 29FCFD98637; Mon, 11 Jun 2007 18:11:39 +0200 (CEST)
Date: Mon, 11 Jun 2007 18:11:39 +0200
From: Thomas Pornin <pornin@bolet.org>
To: ietf-pkix@imc.org
Subject: Re: Three short fixes
Message-ID: <20070611161139.GA27557@localhost.localdomain>
References: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz> <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.5.11
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168


On Mon, Jun 11, 2007 at 07:23:56AM -0700, Hallam-Baker, Phillip wrote:
> I don't see why I should appologize for a fix for being 'centered' on
> the only X.509 prototocol that can be regarded as a real success. 

This is a technical debate on a technical mailing-list. This is not a
trial and there is nothing to apologize about yet.


> The reason for using a certificate is to allow for backwards
> compatibility with a billion installed browsers. The dilution of trust
> is inevitable, all it takes to get a WebTrust audit is to do what you
> say. Eventually someone is going to get a WebTrust audit on the null
> CPS.

For backward compatibility, SSL/TLS already has a beautiful scheme which
is called "cipher suite selection" and it works. Basically, the client
sends a message ("ClientHello") where it states which cipher suites it
supports, and then the server selects one which it also supports. The
cipher suite defines how the session will be protected. For DH_anon
cipher suites, both client and server know that there is no X.509
certificate involved, only a public key.

Let's assume that we have a server which wishes to use encryption but
needs not any kind of authentication(*). This server will be fine with
a DH_anon suite. A client comes along:

-- Either this is a client which supports the concept of an
unauthenticated but encrypted session. That client then implements
DH_anon cipher suites, because that is exactly what these suites are
about, and they have been standard for quite a long time. The client
states that it supports DH_anon suites, the server selects one, and the
session is encrypted but not authenticated. No X.509 certificate is
involved here, and, in particular, no X.509-related warning message is
displayed to the user.

-- Or the client does not support the concept of an unauthenticated but
encrypted session. This means that the client does not support DH_anon
cipher suites (because DH_anon suites are meant for one thing and one
thing only: unauthenticated but encrypted session). The client will send
a ClientHello message which will not contain a DH_anon suite, but other
cipher suites which expect a X.509 certificate from the server. The
server sends a certificate which cannot be authenticated by the client.
The client displays a warning to the user, but we cannot do better than
that since the client does not support unauthenticated sessions: this is
the "backward compatibility" situation.



What could be done here to makes things even better would be the
following:

-- Make DH_anon suites more "supported" (newer TLS specifications tell
that DH_anon suites are obsolescent due to the involved security
issues(**)).

-- Define RSA_anon suites which should provide better performance for
computationaly challenged clients (RSA encryption is cheap).

Both of these are issues for the IETF TLS mailing-list, not the IETF PKIX
mailing-list.


To sum up, what you ask for _already exists_ in a better way (less
network traffic and less X.509 processing for the same functionality).
Unless what you want is something entirely different. You write:

> I want to be able to issue device SSL certs. People want to buy them.

Of course, if you sell certificates, you will not like a scheme where
nobody uses certificates and, as such, nobody buys certificates.


	--Thomas Pornin


(*) Basically, unauthenticated but encrypted session are useful only if
the security model allows only passive attacks. This is rarely a valid
assumptions, but this is not the issue in this discussion. We assume
here that there are plausible situations where unauthenticated but
encrypted sessions are what is needed.

(**) People involved in the definition of TLS do not believe in the
existence of plausible situations where unauthenticated but encrypted
sessions are what is needed. This is why DH_anon suites are currently
deprecated. But the same people, and, more importantly from your point
of view, the TLS implementors will think just the same about any way to
get unauthenticated but encryted sessions, whether by using the TLS
features which have been designed for exactly that usage (DH_anon), or
by any X.509-related trickery such as your fake certificates. So this is
not an issue in this debate.




From owner-ietf-pkix@mail.imc.org Mon Jun 11 14:38:16 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxomO-0002oy-Kx
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 14:38:16 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxomO-0002P2-24
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 14:38:16 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BHkl5Q091393
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 10:46:47 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BHklRP091390;
	Mon, 11 Jun 2007 10:46:47 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BHkkqx091368
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 10:46:47 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5BHkeG7002382;
	Mon, 11 Jun 2007 10:46:42 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jun 2007 10:46:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 10:45:29 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <20070611161139.GA27557@localhost.localdomain>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIg
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Thomas Pornin" <pornin@bolet.org>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 17:46:40.0382 (UTC) FILETIME=[776509E0:01C7AC50]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BHklqw091377
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003


The TLS features are irrelevant.

The information to be encoded here relates to the issue practices of the certificate. Therefore they go into the certificate.

These are not anonymous communications, they are merely communications that do not require the level of assurance that is necessary to alert the user to tell tham that the communication is secure.

 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Thomas Pornin
> Sent: Monday, June 11, 2007 12:12 PM
> To: ietf-pkix@imc.org
> Subject: Re: Three short fixes
> 
> 
> On Mon, Jun 11, 2007 at 07:23:56AM -0700, Hallam-Baker, Phillip wrote:
> > I don't see why I should appologize for a fix for being 
> 'centered' on 
> > the only X.509 prototocol that can be regarded as a real success.
> 
> This is a technical debate on a technical mailing-list. This 
> is not a trial and there is nothing to apologize about yet.
> 
> 
> > The reason for using a certificate is to allow for backwards 
> > compatibility with a billion installed browsers. The 
> dilution of trust 
> > is inevitable, all it takes to get a WebTrust audit is to 
> do what you 
> > say. Eventually someone is going to get a WebTrust audit on 
> the null 
> > CPS.
> 
> For backward compatibility, SSL/TLS already has a beautiful 
> scheme which is called "cipher suite selection" and it works. 
> Basically, the client sends a message ("ClientHello") where 
> it states which cipher suites it supports, and then the 
> server selects one which it also supports. The cipher suite 
> defines how the session will be protected. For DH_anon cipher 
> suites, both client and server know that there is no X.509 
> certificate involved, only a public key.
> 
> Let's assume that we have a server which wishes to use 
> encryption but needs not any kind of authentication(*). This 
> server will be fine with a DH_anon suite. A client comes along:
> 
> -- Either this is a client which supports the concept of an 
> unauthenticated but encrypted session. That client then 
> implements DH_anon cipher suites, because that is exactly 
> what these suites are about, and they have been standard for 
> quite a long time. The client states that it supports DH_anon 
> suites, the server selects one, and the session is encrypted 
> but not authenticated. No X.509 certificate is involved here, 
> and, in particular, no X.509-related warning message is 
> displayed to the user.
> 
> -- Or the client does not support the concept of an 
> unauthenticated but encrypted session. This means that the 
> client does not support DH_anon cipher suites (because 
> DH_anon suites are meant for one thing and one thing only: 
> unauthenticated but encrypted session). The client will send 
> a ClientHello message which will not contain a DH_anon suite, 
> but other cipher suites which expect a X.509 certificate from 
> the server. The server sends a certificate which cannot be 
> authenticated by the client.
> The client displays a warning to the user, but we cannot do 
> better than that since the client does not support 
> unauthenticated sessions: this is the "backward 
> compatibility" situation.
> 
> 
> 
> What could be done here to makes things even better would be the
> following:
> 
> -- Make DH_anon suites more "supported" (newer TLS 
> specifications tell that DH_anon suites are obsolescent due 
> to the involved security issues(**)).
> 
> -- Define RSA_anon suites which should provide better 
> performance for computationaly challenged clients (RSA 
> encryption is cheap).
> 
> Both of these are issues for the IETF TLS mailing-list, not 
> the IETF PKIX mailing-list.
> 
> 
> To sum up, what you ask for _already exists_ in a better way 
> (less network traffic and less X.509 processing for the same 
> functionality).
> Unless what you want is something entirely different. You write:
> 
> > I want to be able to issue device SSL certs. People want to 
> buy them.
> 
> Of course, if you sell certificates, you will not like a 
> scheme where nobody uses certificates and, as such, nobody 
> buys certificates.
> 
> 
> 	--Thomas Pornin
> 
> 
> (*) Basically, unauthenticated but encrypted session are 
> useful only if the security model allows only passive 
> attacks. This is rarely a valid assumptions, but this is not 
> the issue in this discussion. We assume here that there are 
> plausible situations where unauthenticated but encrypted 
> sessions are what is needed.
> 
> (**) People involved in the definition of TLS do not believe 
> in the existence of plausible situations where 
> unauthenticated but encrypted sessions are what is needed. 
> This is why DH_anon suites are currently deprecated. But the 
> same people, and, more importantly from your point of view, 
> the TLS implementors will think just the same about any way 
> to get unauthenticated but encryted sessions, whether by 
> using the TLS features which have been designed for exactly 
> that usage (DH_anon), or by any X.509-related trickery such 
> as your fake certificates. So this is not an issue in this debate.
> 
> 




From owner-ietf-pkix@mail.imc.org Mon Jun 11 16:27:54 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxqUU-0004YN-NF
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 16:27:54 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxqUT-0002pI-7b
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 16:27:54 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BJgLAu027460
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 12:42:21 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BJgL8g027459;
	Mon, 11 Jun 2007 12:42:21 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BJgKPb027453
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 12:42:20 -0700 (MST)
	(envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8])
	by stingray.missi.ncsc.mil with SMTP id l5BJgJB8002707
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 15:42:19 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 11 Jun 2007 15:42:19 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959);
	 Mon, 11 Jun 2007 15:42:19 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 15:42:18 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmA=
References: <20070611161139.GA27557@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 19:42:19.0394 (UTC) FILETIME=[9F5E3E20:01C7AC60]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15232000
X-TM-AS-Result: : Yes--3.370900-0-4-1
X-TM-AS-Category-Info: : 4:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE4LTE1MDU2Ny03MDIy?=
	=?us-ascii?B?NDgtNzAxNDU1LTcwNDQyNS03MDIxMTMtNzA0MTcxLTcwMjc0Ny03?=
	=?us-ascii?B?MDIzNDItNzAyMDYxLTcwMjA0NC03MDIzNTgtMTA2NjQwLTcwMDAw?=
	=?us-ascii?B?OS03MDM0NjgtNzAyODk4LTcwMjU5OC03MDQ3MTItNzAxNDI2LTcw?=
	=?us-ascii?B?MTA2NS03MDAzMjQtMTM5MDA2LTcwNDI4Ny03MDM4MjktNzAyOTU3?=
	=?us-ascii?B?LTcwNjc5MS03MTA0NDItNzAwNzU2LTExMDQ2Mi0xMDUwNDAtNzAy?=
	=?us-ascii?B?ODAxLTcwMTU3Ni03MDA2NjEtNzAyNDg1LTEzOTcwNC03MDgxOTYt?=
	=?us-ascii?B?NzA0MTg5LTcwMDA3My03MTEyMDctNzAwNDcyLTcwMTU5MC03MDU1?=
	=?us-ascii?B?MjYtMTQ4MDUw?=
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BJgKPb027454
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b


In order to achieve backwards compatibility with a billion browsers,
you would have to mark any new extension as non-critical, where it
would be ignored by every single browser currently in existence.

Therefore users would be told that their communication is secure while
issuing practices permit (no, positively encourage, once the word
on this extension gets out) web site spoofing.

If you want to use Peter's OID for this, no one can stop you.  But
the PKIX WG can refuse to assign an OID whose ostensible purpose is
to enable non-advertised encryption but whose actual effect on current
browsers would be to advertise secure communications while using
null-assurance certificates.




-----Original Message-----
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org]
On Behalf Of Hallam-Baker, Phillip

These are not anonymous communications, they are merely communications
that do not require the level of assurance that is necessary to alert
the user to tell tham that the communication is secure.
 
> > The reason for using a certificate is to allow for backwards 
> > compatibility with a billion installed browsers. 


-----------

P.S., the difference between anonymous communications and
communications for which the participants can claim any desired
name (e.g. my webserver operating as https://www.verisign.com)
and into which third parties (e.g. hotel wireless APs) may
insert themselves eludes me. One definition of anonymous is
"unnamed", but the second definition is "of unknown origin".
Spoofed names certainly seem to fit the second definition.




From owner-ietf-pkix@mail.imc.org Mon Jun 11 18:08:25 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxs3l-0005bC-9P
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 18:08:25 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxs3j-0005K5-KP
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 18:08:25 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLN69e059801
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 14:23:06 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BLN6jg059799;
	Mon, 11 Jun 2007 14:23:06 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailrelay.tugraz.at (mailrelay.tu-graz.ac.at [129.27.2.202])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLN3EB059775
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 14:23:05 -0700 (MST)
	(envelope-from peter.lipp@iaik.tugraz.at)
Received: from thor.iaik.tugraz.at (mail1.iaik.tugraz.at [129.27.152.30])
	by mailrelay2.tugraz.at (8.14.1/8.14.1) with ESMTP id l5BLMxuM022792;
	Mon, 11 Jun 2007 23:22:59 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
	by thor.iaik.tugraz.at (Postfix) with ESMTP id 835E9194002;
	Mon, 11 Jun 2007 23:22:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at iaik.tugraz.at
Received: from thor.iaik.tugraz.at ([127.0.0.1])
	by localhost (thor.iaik.tugraz.at [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oksrijmEqThK; Mon, 11 Jun 2007 23:22:58 +0200 (CEST)
Received: from tabletlipp (unknown [129.27.152.247])
	by thor.iaik.tugraz.at (Postfix) with ESMTP;
	Mon, 11 Jun 2007 23:22:58 +0200 (CEST)
From: "Peter Lipp" <peter.lipp@iaik.tugraz.at>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf-pkix@imc.org>
References: <20070611161139.GA27557@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Subject: AW: Three short fixes
Date: Mon, 11 Jun 2007 23:22:58 +0200
Organization: IAIK TU Graz
Message-ID: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uA=
Content-Language: de-at
MIME-Version: 1.0
Content-Type: multipart/signed;
	boundary="----=_NextPart_000_0349_01C7AC7F.72128970";
	protocol="application/x-pkcs7-signature";
	micalg=SHA1
X-Spam-Scanner: SpamAssassin 3.002000 
X-Spam-Score-relay: 1.4
X-Scanned-By: MIMEDefang 2.62 on 129.27.10.19
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c


Dies ist eine mehrteilige Nachricht im MIME-Format.

------=_NextPart_000_0349_01C7AC7F.72128970
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> The information to be encoded here relates to the issue practices of
> the certificate. Therefore they go into the certificate.
Like the warning sign for an unusable safety-belt that is sewn into the belt
saying: "manufactured without care, don't use for driving"? And the belt is
applied automatically too, without the user noticing, so he wouldn't be
realizing that the belt breaks...

Earlier on you wrote:
> In many cases all that is required is to turn on encryption.
This would be the case with TLS-anon-cipher suites. Because if "all that is
required" is encryption, we don't care how it is initiated. So there must be
a use case.... 

...like a pre-manufactured bulk certificate that you ship to your customer
who puts it into one shipped appliance, so you as the issuer have no full
control on what happens with the certificate (and probably pregenerated key)
and thus can't give out any warranties, but the overall procedure may be
safe enough for its purposes? Thus, if the certificate should be misused, it
might not do any harm elsewhere if this extension is in. Then there is a
difference to the anon-cipher-suite.

Otherwise, I don't get the point... Since you want to sell your
certificates, you should first sell your story better.

Peter

------=_NextPart_000_0349_01C7AC7F.72128970
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIhczCCA2Aw
ggJIoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwQTEQMA4GA1UEChMHRXVyb1BLSTEtMCsGA1UEAxMk
RXVyb1BLSSBSb290IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk5MTIyOTE3MzAzOVoXDTEw
MTIzMTEyMDAwMFowQTEQMA4GA1UEChMHRXVyb1BLSTEtMCsGA1UEAxMkRXVyb1BLSSBSb290IENl
cnRpZmljYXRpb24gQXV0aG9yaXR5MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA/y/8
y4eFIIJCIiQNiZrsHev0yzqE6Gc9w69BaAoHoYqfmTa19XoQcNHrAiumdfEnwznsgwfomt6lmpbX
nUFbbS1EJ1T3V5s7myFWqVhaB5tbt6C4QYEqdZhwZgLCphrx1fyGBeLe9PbVEJaXmYIyM6W48ze/
fV6Gtl9siahhgQA8xyoiZ+afNC7DJ8d1Uf1MiF2SRKutdVJQA3yR9aocFMzWtBfNI9LZO/6Wi4Z1
q2Q7H2TRpALoECwQ1IvpwSlLuBYnKX2C+xxl+H0ZrYPqC7kNbx5WHtmFbPlBiOO3u43eGH9b244p
0NDlK8dp8fM/saOO5YF8DGxCe1cKxAo0twIDAQABo2MwYTAfBgNVHSMEGDAWgBSM3IuxpUqQ506I
cxg8ndVefuSyzTAdBgNVHQ4EFgQUjNyLsaVKkOdOiHMYPJ3VXn7kss0wDgYDVR0PAQH/BAQDAgHG
MA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADggEBAFto/551vUIbQntYkHVfShcva5zq
Sh+N7RxY7lAZYKYLzb9Nf61zFy5/1vNZ7i05mcHYWHI5XVGWUellBi7QKzi0GlJE0DB43PxJFP7N
L/DLljYOb4Qt2bBRTVbX0fIlmtmvoAOLgR9e3F3ej7s6g9BzBQO+T99pHrN8W5RVmeakmBkL8uGl
qE/xQ7G3iRv1KafBW2dmdKUqn4vXAFhqs0WJU9HYLvGdkRcMHf7z71aUJXQdUnEZH6S+jwi75pnz
ER6vGYNCTHKpiF2GIND3D3SfhAopEmHf+xudP7iHyQw2RDiJJqV1Z93EJnDA0Wrob8LKEegdpQl/
3BCNDxJzAWgwggSKMIIDcqADAgECAgERMA0GCSqGSIb3DQEBBQUAMEExEDAOBgNVBAoTB0V1cm9Q
S0kxLTArBgNVBAMTJEV1cm9QS0kgUm9vdCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wMjEy
MTIxNzAwMDBaFw0wODEyMzEwOTAwMDBaMFIxCzAJBgNVBAYTAkFUMRAwDgYDVQQKEwdFdXJvUEtJ
MTEwLwYDVQQDEyhFdXJvUEtJIEF1c3RyaWFuIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoE5gWK44kT3O3Yenp0GT6+gkypmIAlhqYAcmokav
l3WaQ4BhBlAv4ORtBF/hVObG1ugPCep7cTNyoXZ+sNIbmlLzBxzrRpT4nYQIEu3IXR108c6APycH
+9vbYIUQrsCKx8Qs/csU5rdOxc15pHsZLJiiCYATB0GWyrcbVcoNgAj6crv7Lx37SlENgMAssOoG
4E3/2wrCQ2n/QiqBEosscpnEqQs6ABvdQiLKSpfVQJA77l9ujQ1C/ugtlYwAr5GrtSOhOTYvKB4t
uVleqlHFzJoA6XaWQRpD4Oy4ymF0+5IAe9q+lOQ6U57rWIZ0MMr8xAmf7VZtmk0KJYCkAl3DPwID
AQABo4IBejCCAXYwTAYJYIZIAYb4QgENBD8WPUlzc3VlZCB1bmRlciBwb2xpY3k6CiBodHRwOi8v
d3d3LmV1cm9wa2kub3JnL2NhL3Jvb3QvY3BzLzEuMS8wOAYIKwYBBQUHAQEELDAqMCgGCCsGAQUF
BzABhhxodHRwOi8vb2NzcC5ldXJvcGtpLm9yZzo4MDI2MDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6
Ly93d3cuZXVyb3BraS5vcmcvY2Evcm9vdC9jcmwvY3JsLmRlcjAPBgNVHRMBAf8EBTADAQH/ME4G
A1UdIARHMEUwQwYKKwYBBAGpBwEBATA1MDMGCCsGAQUFBwIBFidodHRwOi8vd3d3LmV1cm9wa2ku
b3JnL2NhL3Jvb3QvY3BzLzEuMS8wDgYDVR0PAQH/BAQDAgH2MB0GA1UdDgQWBBTQlAuMnkklreDR
A1zeuwDyvzWc9zAfBgNVHSMEGDAWgBSM3IuxpUqQ506Icxg8ndVefuSyzTANBgkqhkiG9w0BAQUF
AAOCAQEAQNx/GA75gR3WJWcf6A9/yvQWAHeUJNGCrB5miAg5Cd+Ac+7rAmdyWS+6ovB2vsbiwDoA
BuVuntCVVRdiu26/eXstDjFwUo99X6CmAMhHqv9MolzMjKRzwKk9QKDP4xUoEk/fXoIhUPHbeN3T
3bNpQlW6RH3mkIS08/3Rlncv0AOUtk+EO1YuDwy1WAdwp5Wo8E1pYxkQlalzDzSZrt6SpOAdM5dZ
Vj7PQrjswKfGj48OOIxmKliuojmPy+UZv8PoFkB8MX9Cqk5gOlWUt5pTvl6x/iP32h4kF0bCF76D
7sx5SjekbNmEtZ1thHQLY7aalOVBF1K+mJvYWMGrnvB8djCCBLQwggOcoAMCAQICFQCEWAP+T9cN
Wn701+2abEum54RkPDANBgkqhkiG9w0BAQUFADBSMQswCQYDVQQGEwJBVDEQMA4GA1UEChMHRXVy
b1BLSTExMC8GA1UEAxMoRXVyb1BLSSBBdXN0cmlhbiBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAe
Fw0wMjEyMTcxMjI1MDdaFw0wODEyMzAyMjU5MzBaMIHMMQswCQYDVQQGEwJBVDENMAsGA1UEBxME
R3JhejEZMBcGA1UECRMQSW5mZmVsZGdhc3NlIDE2YTEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZ
IE9GIFRFQ0hOT0xPR1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlv
biBQcm9jZXNzaW5nIGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UEAxMYSUFJSyBFdXJvUEtJIElu
dHJhbmV0IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz8KxI9Ubcz1kWVBqbVr9
vyrID0NBcjBx2HpoZ//kI1L+dWg/X5nKqlFPwoK6CROrC7TenGaEPdYJ8SEvxsPeTzYVF+o2XzeD
xeSvxl892VMf23L3JuLYxRhtdo8Vk+CDfXd6E+UjDI4dQMNARN+cskp5agXH1h0e4LQabHQKL8NU
8cvAbfL5ga4Xtu3WNHd2yYrVCztQhtfRtEN++K5yfwmPWRB7M9OPfBI+fnhZ3n0hIpSe5EDQzVNs
wse8brtI3btMq2+WNfkQXYCRwqDJXVGzgNh5DTs/WC8omFj1kcU/X3D4F7/Y0mLvrfgwdDDD8+d2
XGCC1bKKbI4SnblTuQIDAQABo4IBBDCCAQAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC
AcYwHwYDVR0jBBgwFoAU0JQLjJ5JJa3g0QNc3rsA8r81nPcwVgYDVR0gBE8wTTBLBgwrBgEEAZUS
AQIBAQEwOzA5BggrBgEFBQcCARYtaHR0cDovL2V1cm9wa2kuaWFpay5hdC9jYS9ldXJvcGtpLWF0
L2Nwcy8xLjEvMEUGA1UdHwQ+MDwwOqA4oDaGNGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2EvZXVy
b3BraS1hdC9jcmwvYXVzdHJpYS5jcmwwHQYDVR0OBBYEFIRYA/5P1w1afvTX7ZpsSrS7EDPSMA0G
CSqGSIb3DQEBBQUAA4IBAQB/O6DNrOa1v+n+fsglJAmAYQrMQZisqnRoqGXhEK1IMCc55wRx8iXq
ZTIYRm7F4PtNK0tmqP80DvCf/Gni0Sx/Lh5fJuUKlyP0OU8v474TnubUnKYimeFeJjqTI0dIddlj
bwHBbeLMvTksX8cIi8Hb/yhaMwTTPfg0fDlBpjjundgghlBYyDKLwDPFnpwM+TVGSvBlkSIELPdv
DY1f7NQz8QWRi7HhY2OOzZuSfU7FBFejQVzvcqangwZWHZZwdb5QgBOirqAeFJrLChheXRdJ2iWH
WKGRGQ0LShkhGNUzTJsTobjL1/gLjfu+uOtr5XBPPBsR2MjvH+ZqQ7maVxQGMIIFKTCCBBGgAwIB
AgICA+owDQYJKoZIhvcNAQEFBQAwgcUxCzAJBgNVBAYTAkFUMSYwJAYDVQQKEx1HUkFaIFVOSVZF
UlNJVFkgT0YgVEVDSE5PTE9HWTFIMEYGA1UECxM/SW5zdGl0dXRlIGZvciBBcHBsaWVkIEluZm9y
bWF0aW9uIFByb2Nlc3NpbmcgYW5kIENvbW11bmljYXRpb25zMSEwHwYDVQQLExhJQUlLIEV1cm9Q
S0kgSU5UUkFORVQgQ0ExITAfBgNVBAMTGElBSUsgRXVyb1BLSSBUVS1HUkFaIFNJRzAeFw0wNzA0
MjUwOTUzMDhaFw0wODA0MjQwOTUzMDhaMIHuMQ4wDAYDVQQqEwVQZXRlcjENMAsGA1UEBBMETGlw
cDETMBEGA1UEAxMKUGV0ZXIgTGlwcDEmMCQGA1UEChMdR3JheiBVbml2ZXJzaXR5IG9mIFRlY2hu
b2xvZ3kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNz
aW5nIGFuZCBDb21tdW5pY2F0aW9uczEZMBcGA1UECRMQSW5mZmVsZGdhc3NlIDE2YTENMAsGA1UE
BxMER3JhejEPMA0GA1UECBMGU3R5cmlhMQswCQYDVQQGEwJBVDCBnzANBgkqhkiG9w0BAQEFAAOB
jQAwgYkCgYEAtUB8RyTq8pYMf09Ux3d94Yf2UkwCSYehLxdph4u6vV8ApLpdDnraux36axtVymdv
JRGqfkhleEraizu/hAP9Zn/R/p+7fXKFMRxBctngfv8WISOKw/fE4JQwnzqF8ilguPYdL/41Pe8r
3Dqr2gRg3yYsd4SNrtruSVmmUA3h81UCAwEAAaOCAXowggF2MA4GA1UdDwEB/wQEAwIGwDAMBgNV
HRMBAf8EAjAAMFQGA1UdIARNMEswSQYMKwYBBAGVEgECAgECMDkwNwYIKwYBBQUHAgEWK2h0dHA6
Ly9ldXJvcGtpLmlhaWsuYXQvY2EvaW50cmFuZXQvY3BzLzEuMi8wHQYDVR0OBBYEFDcFtRTPbZ3w
yhc99asBh8o8j3a1MFEGA1UdHwRKMEgwRqBEoEKGQGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2Ev
aW50cmFuZXQvY3JsLzIwMDIvaWFpa19ldXJvcGtpX3NpZy5jcmwwRwYIKwYBBQUHAQEEOzA5MDcG
CCsGAQUFBzABhitodHRwOi8vb2NzcC5ldXJvcGtpLmlhaWsuYXQvT0NTUD90eXBlPWVtYWlsMB8G
A1UdIwQYMBaAFHi1VaEzvYMlf+rz54y3o5+Vc6p7MCQGA1UdEQQdMBuBGXBldGVyLmxpcHBAaWFp
ay50dWdyYXouYXQwDQYJKoZIhvcNAQEFBQADggEBAFYQ2pmxirCGc/c2EwQmGTR28RzUlXGDw6E/
cgMnYUzANv/G+qBvThPy4lm1obamynjecvg5ImOK+MaSO6oxxocu6Iz44Pmiazdfry5L7StEsyvr
g/TchBMij6NqjYbbf7Fg3ptcheP8jDecuSUWy11n/4v4oduGxDbVYBPPEJ/+9epdZCRPSDqla5S8
Sv4KiqaHwqTx0Qud6uxGqzVs58aNzJtEzJFXmcGT3n/uzog3b40/ALFVkN86Dy1EmZgcZjZkGI7W
WKNAP/AXMSNmJTqW9pM1OePpyyZOwD2y9JlEIfIG5HKdWEAEPHuUCL/IOFbKRPZQgAJAfQhCvNsU
xjkwggUtMIIEFaADAgECAgID6zANBgkqhkiG9w0BAQUFADCBxzELMAkGA1UEBhMCQVQxJjAkBgNV
BAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9y
IEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxITAfBgNV
BAsTGElBSUsgRXVyb1BLSSBJTlRSQU5FVCBDQTEjMCEGA1UEAxMaSUFJSyBFdXJvUEtJIFRVLUdS
QVogQ1JZUFQwHhcNMDcwNDI1MDk1MzE3WhcNMDgwNDI0MDk1MzE3WjCB7jEOMAwGA1UEKhMFUGV0
ZXIxDTALBgNVBAQTBExpcHAxEzARBgNVBAMTClBldGVyIExpcHAxJjAkBgNVBAoTHUdyYXogVW5p
dmVyc2l0eSBvZiBUZWNobm9sb2d5MUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5m
b3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxGTAXBgNVBAkTEEluZmZlbGRn
YXNzZSAxNmExDTALBgNVBAcTBEdyYXoxDzANBgNVBAgTBlN0eXJpYTELMAkGA1UEBhMCQVQwgZ8w
DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOETtJ4MyeJuY5x7sBGAcaX0yPW53dEiLlZjs7YU5L50
N1UE0fur9HLesnVn9qJwB8Kc8yYPAfwJajJAOs/wYONxOtuB8OkQjlo3oBgCCCth30DVPvNuBGvF
1hdX7LN2Kjf+NJhtkdV1jqqEco3DHA3v/O7qsnCIdQ+786Dajgq1AgMBAAGjggF8MIIBeDAOBgNV
HQ8BAf8EBAMCBDAwDAYDVR0TAQH/BAIwADBUBgNVHSAETTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcG
CCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2Nwcy8xLjIvMB0G
A1UdDgQWBBSnqZ3lNDpsvPvZigTAaOgoWCRJijBTBgNVHR8ETDBKMEigRqBEhkJodHRwOi8vZXVy
b3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2NybC8yMDAyL2lhaWtfZXVyb3BraV9jcnlwdC5jcmww
RwYIKwYBBQUHAQEEOzA5MDcGCCsGAQUFBzABhitodHRwOi8vb2NzcC5ldXJvcGtpLmlhaWsuYXQv
T0NTUD90eXBlPWNyeXB0MB8GA1UdIwQYMBaAFJopGdYXnsFR38xng6G35L8PuEMdMCQGA1UdEQQd
MBuBGXBldGVyLmxpcHBAaWFpay50dWdyYXouYXQwDQYJKoZIhvcNAQEFBQADggEBAHdMfxlM9HHu
5RDA+DeFF6OmAV5JN6gvkhmYfCxaN6/wqr3mlSq00u/Sk410h9/IaZd3PntRuYwq88LIF2y+xmwK
qeDSurvXnHR821sigd8x9zXpog8o/+0bl5N6jkTUBGg0vzs/zwkZo/VEaWw45tKxn6r+Xw2wsxEo
AQXcefjBGYZN0ZbDtBThU6pBXnPr28jTgIwmefV3oqoglRRpbEzs8/B7jpVcuSEi/OM1+dy9FWyq
LLpyZpGNj013gwCCAfMseZPvacCTTedZ8ZxB7rHGCAZAIw3DbSRtvycUhvaW2qzzIW21Z8mNCQm+
nVXEdPECWItViECDKuKYLyLnAmAwggUwMIIEGKADAgECAhR4tVWhM72DJX/q8+eMt6SRwlgmbzAN
BgkqhkiG9w0BAQUFADCBzDELMAkGA1UEBhMCQVQxDTALBgNVBAcTBEdyYXoxGTAXBgNVBAkTEElu
ZmZlbGRnYXNzZSAxNmExJjAkBgNVBAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgw
RgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQg
Q29tbXVuaWNhdGlvbnMxITAfBgNVBAMTGElBSUsgRXVyb1BLSSBJbnRyYW5ldCBDQTAeFw0wMjEy
MTcxNDI3NDFaFw0wODEyMzAyMjU5MzBaMIHFMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBV
TklWRVJTSVRZIE9GIFRFQ0hOT0xPR1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJ
bmZvcm1hdGlvbiBQcm9jZXNzaW5nIGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBF
dXJvUEtJIElOVFJBTkVUIENBMSEwHwYDVQQDExhJQUlLIEV1cm9QS0kgVFUtR1JBWiBTSUcwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDxWjtQORZimthvkSAAJlIL97tgPeJ8+151iGCy
d44WFAyjHsP9oQrZHxazVAB+o8clYdPpp/ECognU41o40iafdgkNIfsjyFMm3VvcWNx+F4vKYTHo
LQascxRJUULgub+B4k4pb9A4URQnxkrMriQlISoFXeEY1l2Mv4DlXHF3qOEMiLW5B1vmZZaEpNvH
/me8fuvJYLi9FWA+Ojk/UybbrGybkeJY3RAq+FImnWkaB9BAoAhdROR+GXU8YvqZTzqUndKog1Kc
cBKaFTBKwSz9RxOVPFORs1VLGItlnGRCn25uOiDTDfrU2D4D9cyFEVU+Qd55RzD6PfgP8BbeUyTx
AgMBAAGjggENMIIBCTASBgNVHRMBAf8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBxjAfBgNVHSME
GDAWgBSEWAP+T9cNWn701+2abEq0uxAz0jBUBgNVHSAETTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcG
CCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2Nwcy8xLjIvME0G
A1UdHwRGMEQwQqBAoD6GPGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2EvaW50cmFuZXQvY3JsLzIw
MDIvaWFpa19ldXJvcGtpLmNybDAdBgNVHQ4EFgQUeLVVoTO9gyV/6vPnjLejn5VzqnswDQYJKoZI
hvcNAQEFBQADggEBAKzKGUR++U1HNASLU47Wje4xIFPusnfd+hWKUR4bol+MtE0zEaAjyrnlgR3r
Hv0S0xnsQKIZMlt9ujiZi/lSzMelr7BDlfoHvV60W85uHROs2wAsSBw20oX2cnxbfZqHQzl2RCcd
1pZKYAu3NExcbJzz9ByjPbxszgBq3qfzywl/+hghd5sDVSr43H3BJ7yrjTiVyHNSVV4g3sz8wQlL
o2Ij/y/hLx2ZQwzXjVZIwL/9Mor2pMl08uD9f+ZSJKXLbWelSorTSD2Xbw3r8vTk1Opy5tnhP5Q7
751azOVvcfiP7Vwz7PdsxoTHrgloUXtdOeRk5XsfEFZnYJQyS9fYDl4wggUzMIIEG6ADAgECAhUA
mikZ1heewVHfzGeDobflsTyT48IwDQYJKoZIhvcNAQEFBQAwgcwxCzAJBgNVBAYTAkFUMQ0wCwYD
VQQHEwRHcmF6MRkwFwYDVQQJExBJbmZmZWxkZ2Fzc2UgMTZhMSYwJAYDVQQKEx1HUkFaIFVOSVZF
UlNJVFkgT0YgVEVDSE5PTE9HWTFIMEYGA1UECxM/SW5zdGl0dXRlIGZvciBBcHBsaWVkIEluZm9y
bWF0aW9uIFByb2Nlc3NpbmcgYW5kIENvbW11bmljYXRpb25zMSEwHwYDVQQDExhJQUlLIEV1cm9Q
S0kgSW50cmFuZXQgQ0EwHhcNMDIxMjE3MTQxODAyWhcNMDgxMjMwMjI1OTMwWjCBxzELMAkGA1UE
BhMCQVQxJjAkBgNVBAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9J
bnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNh
dGlvbnMxITAfBgNVBAsTGElBSUsgRXVyb1BLSSBJTlRSQU5FVCBDQTEjMCEGA1UEAxMaSUFJSyBF
dXJvUEtJIFRVLUdSQVogQ1JZUFQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWIkt2
4ac2iD1RZW0BzsolEcM7k6C5Pb8EHxVojWsjJsscBB32XS9H2h2/XmjVOLtCPoNiEaqm8WrqFky2
9IdoktkLdV6bvW4gN32k17mvPUNCPmqO78idaqXCm//ocXRMwUHpMCv1NN+5KUMJ18BDchltI/Zj
1btYA7cZy4Ax01k6Z2zHUJkoAc7/+x95o8Cm/1D9JxxZ5o6tHdiAYgyUjCA6Q3L0DmNQgLPOMWU5
ZfcANDWfMTAH71c3oRJaKIum3yCKzThyX24X7iSU/SI1mA2uJnOerEweuLNhmu5kJzH+079B2Jys
cr921fzcz6KEEjEoEtnF8VSUvhFWxb2bAgMBAAGjggENMIIBCTASBgNVHRMBAf8ECDAGAQH/AgEA
MA4GA1UdDwEB/wQEAwIBxjAfBgNVHSMEGDAWgBSEWAP+T9cNWn701+2abEq0uxAz0jBUBgNVHSAE
TTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcGCCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0
L2NhL2ludHJhbmV0L2Nwcy8xLjIvME0GA1UdHwRGMEQwQqBAoD6GPGh0dHA6Ly9ldXJvcGtpLmlh
aWsuYXQvY2EvaW50cmFuZXQvY3JsLzIwMDIvaWFpa19ldXJvcGtpLmNybDAdBgNVHQ4EFgQUmikZ
1heewVHfzGeDobfkvw+4Qx0wDQYJKoZIhvcNAQEFBQADggEBAIgvmnj7ZJAOsLKiDtSRJ3S16HTW
j9JqjfXmy5S7EXRmw7SqeL7/rdXYgkhoXDF7mlEMvrTxIXBA75WCzUowfcVnC+T0EhDbfUq4NFh/
jQVpQEeRXE0EJXFDgtUmQuobFgeNe/KKzs2jcXEBgZMBZcxosxMPbfqPD7hFJxMghOe0id/HSZuL
iroFyoMefkfBABG12w2hQV5m8tnlva8s14/7rw5x8blsAnWsKA0yVzto3EikB3cVL+GslnrGM6R5
Ad/CY5iYKjPvD5w68OyCX6H/BxeAnEESoxwpHEXGDUNASZoQu5HPvCO/GNXs+CuXKrgo7UCg2ylE
luMawt9NmVgxggQDMIID/wIBATCBzDCBxTELMAkGA1UEBhMCQVQxJjAkBgNVBAoTHUdSQVogVU5J
VkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5m
b3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxITAfBgNVBAsTGElBSUsgRXVy
b1BLSSBJTlRSQU5FVCBDQTEhMB8GA1UEAxMYSUFJSyBFdXJvUEtJIFRVLUdSQVogU0lHAgID6jAJ
BgUrDgMCGgUAoIICjDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w
NzA2MTEyMTIyNTdaMCMGCSqGSIb3DQEJBDEWBBSCLR+jAo4KravLRDw44VZGXh2djzBnBgkqhkiG
9w0BCQ8xWjBYMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCB3wYJKwYBBAGCNxAEMYHR
MIHOMIHHMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZIE9GIFRFQ0hOT0xP
R1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNzaW5n
IGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBFdXJvUEtJIElOVFJBTkVUIENBMSMw
IQYDVQQDExpJQUlLIEV1cm9QS0kgVFUtR1JBWiBDUllQVAICA+swgeEGCyqGSIb3DQEJEAILMYHR
oIHOMIHHMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZIE9GIFRFQ0hOT0xP
R1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNzaW5n
IGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBFdXJvUEtJIElOVFJBTkVUIENBMSMw
IQYDVQQDExpJQUlLIEV1cm9QS0kgVFUtR1JBWiBDUllQVAICA+swDQYJKoZIhvcNAQEBBQAEgYA0
UuerauIt7bsgz/etFUUl8FOs7qNTyykRuEw2h7WOYlup3f0blrNIGwm5iOY+YrvrSkS7+jyLQP/2
gQ72iYNnyvfsfK79jhTluRWcRGt1mFyk1EXaNqWyjVlbKsZsckH0gf984b1xgYdernSfUKUNKQZK
t3HYjOarwzkXQEcSYQAAAAAAAA==

------=_NextPart_000_0349_01C7AC7F.72128970--




From owner-ietf-pkix@mail.imc.org Mon Jun 11 18:56:27 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxsoF-0007Je-Rl
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 18:56:27 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxsoE-0005V2-AQ
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 18:56:27 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BMFiFA077349
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 15:15:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BMFigQ077348;
	Mon, 11 Jun 2007 15:15:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail1.exchange.microsoft.com [131.107.1.17])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BMFgjq077340
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 15:15:43 -0700 (MST)
	(envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-01.exchange.corp.microsoft.com (157.54.54.216) by
 DF-GWY-05.exchange.corp.microsoft.com (157.54.63.146) with Microsoft SMTP
 Server (TLS) id 8.0.685.24; Mon, 11 Jun 2007 15:15:42 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.8]) by
 df-bhd-01.exchange.corp.microsoft.com ([157.54.54.216]) with mapi; Mon, 11
 Jun 2007 15:15:42 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>,
        "ietf-pkix@imc.org"
	<ietf-pkix@imc.org>
Date: Mon, 11 Jun 2007 15:15:39 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmAABcwnoA==
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC926A9696A8@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <20070611161139.GA27557@localhost.localdomain>
 <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
 <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
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"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BMFhjp077341
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5


I have to agree with Dave here. For HTTPS these certificates would be practically useless for at least 5 years and probably more  given the lag time on OS and browser upgrades. Now other applications of TLS already support the concept of "confidentiality only" TLS with certificates. I am thinking here of SMTP. SMTP servers use "opportunistic TLS" where the SMTP server has a policy to pick the STARTTLS verb whenever it its offered by the receiving server. When operating under optimistic mode the sending server does not validate the receiving servers certificate because the alternative course of action with validation errors is to send in the clear. Because the sending server does not validate the receiving server certificate a common practice is to use self signed certificates which clearly make no warranty about the identity of the owner. Most use of TLS with SMTP over the internet uses opportunistic TLS.  I don't see why such a strategy does not work elsewhere if all you wa!
 nt is confidentiality. An interesting side bar is that the anonymous cipher suites would not work in this scenario because these same servers have a subset of domains they do want to authenticate. There is not enough data at the time of the negotiation for the receiving server to decide they do not want to authenticate the sending server so it has to pick a cipher suite with certificates then it has the option to skip validation or not later in the session.

Trevor

* -----Original Message-----
* From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
* pkix@mail.imc.org] On Behalf Of Kemp, David P.
* Sent: Monday, June 11, 2007 12:42 PM
* To: ietf-pkix@imc.org
* Subject: RE: Three short fixes
*
*
* In order to achieve backwards compatibility with a billion browsers,
* you would have to mark any new extension as non-critical, where it
* would be ignored by every single browser currently in existence.
*
* Therefore users would be told that their communication is secure while
* issuing practices permit (no, positively encourage, once the word
* on this extension gets out) web site spoofing.
*
* If you want to use Peter's OID for this, no one can stop you.  But
* the PKIX WG can refuse to assign an OID whose ostensible purpose is
* to enable non-advertised encryption but whose actual effect on current
* browsers would be to advertise secure communications while using
* null-assurance certificates.
*
*
*
*
* -----Original Message-----
* From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
* pkix@mail.imc.org]
* On Behalf Of Hallam-Baker, Phillip
*
* These are not anonymous communications, they are merely communications
* that do not require the level of assurance that is necessary to alert
* the user to tell tham that the communication is secure.
*
* > > The reason for using a certificate is to allow for backwards
* > > compatibility with a billion installed browsers.
*
*
* -----------
*
* P.S., the difference between anonymous communications and
* communications for which the participants can claim any desired
* name (e.g. my webserver operating as https://www.verisign.com)
* and into which third parties (e.g. hotel wireless APs) may
* insert themselves eludes me. One definition of anonymous is
* "unnamed", but the second definition is "of unknown origin".
* Spoofed names certainly seem to fit the second definition.





From owner-ietf-pkix@mail.imc.org Mon Jun 11 19:08:33 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxszx-0003xJ-5L
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 19:08:33 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxszw-0007pd-6Y
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 19:08:33 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLSiaR061490
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 14:28:45 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BLSiOH061484;
	Mon, 11 Jun 2007 14:28:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLShWK061457
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 14:28:43 -0700 (MST)
	(envelope-from pbaker@verisign.com)
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 l5BLSO2B028232;
	Mon, 11 Jun 2007 14:28:26 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jun 2007 14:28:23 -0700
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"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 14:27:11 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62B9@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uAAAJ3lAA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Peter Lipp" <peter.lipp@iaik.tugraz.at>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 21:28:23.0972 (UTC) FILETIME=[70F3C640:01C7AC6F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BLShWJ061460
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca


No: like the roll cage which is stamped 'not certified for competition
use'.

There are plenty of safety measure on my cars which I am completely
unaware of which are perfectly safe for normal road driving but not
designed for competition use.

Building a certification path up from the MAC address is prefectly
sensible and an appropriate use for PKIX. But it is not by itself
sufficient to present a trust statement. There is no accountability - by
design.

What I am working towards here is a multilayer security approach and I
want to use PKIX at a lower level than the SSL folk did.

> -----Original Message-----
> From: Peter Lipp [mailto:peter.lipp@iaik.tugraz.at] 
> Sent: Monday, June 11, 2007 5:23 PM
> To: Hallam-Baker, Phillip; ietf-pkix@imc.org
> Subject: AW: Three short fixes
> 
> > The information to be encoded here relates to the issue 
> practices of 
> > the certificate. Therefore they go into the certificate.
> Like the warning sign for an unusable safety-belt that is 
> sewn into the belt
> saying: "manufactured without care, don't use for driving"? 
> And the belt is applied automatically too, without the user 
> noticing, so he wouldn't be realizing that the belt breaks...
> 
> Earlier on you wrote:
> > In many cases all that is required is to turn on encryption.
> This would be the case with TLS-anon-cipher suites. Because 
> if "all that is required" is encryption, we don't care how it 
> is initiated. So there must be a use case.... 
> 
> ...like a pre-manufactured bulk certificate that you ship to 
> your customer who puts it into one shipped appliance, so you 
> as the issuer have no full control on what happens with the 
> certificate (and probably pregenerated key) and thus can't 
> give out any warranties, but the overall procedure may be 
> safe enough for its purposes? Thus, if the certificate should 
> be misused, it might not do any harm elsewhere if this 
> extension is in. Then there is a difference to the anon-cipher-suite.
> 
> Otherwise, I don't get the point... Since you want to sell 
> your certificates, you should first sell your story better.
> 
> Peter
> 




From owner-ietf-pkix@mail.imc.org Mon Jun 11 21:03:38 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxunK-0007HG-1y
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 21:03:38 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxunJ-0007DG-LV
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 21:03:38 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C01iaE081735
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 17:01:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C01i2w081734;
	Mon, 11 Jun 2007 17:01:44 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C01heO081728
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 17:01:44 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5C01QeT003784;
	Mon, 11 Jun 2007 17:01:29 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jun 2007 17:01:29 -0700
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"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 17:00:16 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62D5@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uAABf0AkA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Peter Lipp" <peter.lipp@iaik.tugraz.at>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 12 Jun 2007 00:01:29.0002 (UTC) FILETIME=[D3A820A0:01C7AC84]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5C01ieN081729
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c


Case in point here being your S/MIME cert which does not satisfy my
Outlook chaining so give a warning.

Yet I can get mail from plenty of places without any security and
without a warning either.

Wouldn't it be nice if a cert could say 'the correct course of action if
you don't like me is to simply show the email without any indication the
message is secure'.

Why do folk feel that the user has to be told about merely sub-standard
security when 99% of the Internet has no security at all? 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Peter Lipp
> Sent: Monday, June 11, 2007 5:23 PM
> To: Hallam-Baker, Phillip; ietf-pkix@imc.org
> Subject: AW: Three short fixes
> 
> > The information to be encoded here relates to the issue 
> practices of 
> > the certificate. Therefore they go into the certificate.
> Like the warning sign for an unusable safety-belt that is 
> sewn into the belt
> saying: "manufactured without care, don't use for driving"? 
> And the belt is applied automatically too, without the user 
> noticing, so he wouldn't be realizing that the belt breaks...
> 
> Earlier on you wrote:
> > In many cases all that is required is to turn on encryption.
> This would be the case with TLS-anon-cipher suites. Because 
> if "all that is required" is encryption, we don't care how it 
> is initiated. So there must be a use case.... 
> 
> ...like a pre-manufactured bulk certificate that you ship to 
> your customer who puts it into one shipped appliance, so you 
> as the issuer have no full control on what happens with the 
> certificate (and probably pregenerated key) and thus can't 
> give out any warranties, but the overall procedure may be 
> safe enough for its purposes? Thus, if the certificate should 
> be misused, it might not do any harm elsewhere if this 
> extension is in. Then there is a difference to the anon-cipher-suite.
> 
> Otherwise, I don't get the point... Since you want to sell 
> your certificates, you should first sell your story better.
> 
> Peter
> 




From owner-ietf-pkix@mail.imc.org Mon Jun 11 22:28:44 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxw7g-0001pB-VT
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 22:28:44 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxw7g-0007zm-Gx
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 22:28:44 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1hxil086639
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 18:43:59 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C1hxuC086638;
	Mon, 11 Jun 2007 18:43:59 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (larry.its.auckland.ac.nz [130.216.12.34])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1hwel086629
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 18:43:59 -0700 (MST)
	(envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 73FF218345;
	Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LYa49ci1FkZh; Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 5B91118334;
	Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33])
	by iris.cs.auckland.ac.nz (Postfix) with ESMTP
	id 91F351280A1; Tue, 12 Jun 2007 13:43:54 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian))
	id 1HxvQM-0001HJ-00; Tue, 12 Jun 2007 13:43:58 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org
Subject: RE: Three short fixes
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
Message-Id: <E1HxvQM-0001HJ-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 13:43:58 +1200
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>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5


"Kemp, David P." <DPKemp@missi.ncsc.mil> writes:

>More to the point, the intent is to create an attribute that says:
>
>  "This certificate is merely a convenient universally-accepted
>   blob for communicating a public key and a name/email address/URL"
>*AND*
>  "There is no claim that the public key and the name/email/URL
>   have any relationship whatsoever"

Sure, the latter was implied in the former.

>In other words, the name/email/URL could belong to Bank of America but the
>key pair and certificate request could have been created by Phish-R-Us, and
>no claims to the contrary are made by the issuer. 

More or less.  As I said, there are people using certs simply as a universal
container for a public key because there's nothing else available.  They don't
care about any cert semantics, they just need a means of getting a key from A
to B in a format that B can process.  Providing some means of indicating this
in the cert would be useful.

I'm not really too fussed about it, I'll let users keep using Xyzzy certs,
however if there's no centralised record of this you end up with a pile of ad
hoc approaches instead, including the current one of taking otherwise normal-
looking certs and ignoring all the cert semantics.  The choice is really:

  1) Use null-semantics certs that look like normal certs.

  2) Use null-semantics certs but at least mark them as such.

Of these two, (2) seems to be the better approach.

Peter.




From owner-ietf-pkix@mail.imc.org Mon Jun 11 22:28:45 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxw7h-0001pS-TW
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 22:28:45 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxw7g-0007zn-Gy
	for pkix-archive@lists.ietf.org; Mon, 11 Jun 2007 22:28:45 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1lfPh086811
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 18:47:41 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C1levo086810;
	Mon, 11 Jun 2007 18:47:40 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (larry.its.auckland.ac.nz [130.216.12.34])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1le88086803
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 18:47:40 -0700 (MST)
	(envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id AFD591834A;
	Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1])
	by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id IVSixmwTFiiS; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152])
	by mailhost.auckland.ac.nz (Postfix) with ESMTP id 980CE18345;
	Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33])
	by iris.cs.auckland.ac.nz (Postfix) with ESMTP
	id 6BDE61280A1; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian))
	id 1HxvTy-0001MI-00; Tue, 12 Jun 2007 13:47:42 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org
Subject: RE: Three short fixes
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
Message-Id: <E1HxvTy-0001MI-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 13:47:42 +1200
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>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad


I wrote:

>I'm not really too fussed about it, I'll let users keep using Xyzzy certs,

Oops, what I meant with "Xyzzy certs" is that that's the name of the OID used
to indicate that the cert is merely a bit-bag for a public key.  Currently
it's used as a policy OID, which seemed to be the best place to put it,
although a standard extension would be a better way to handle it.  The policy
is "This certificate isn't worth the paper it's not printed on".

Peter.




From owner-ietf-pkix@mail.imc.org Tue Jun 12 00:12:45 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxxkL-0004it-EY
	for pkix-archive@lists.ietf.org; Tue, 12 Jun 2007 00:12:45 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HxxkJ-00044e-U3
	for pkix-archive@lists.ietf.org; Tue, 12 Jun 2007 00:12:45 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C3QwYs092171
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 11 Jun 2007 20:26:58 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C3QwMf092170;
	Mon, 11 Jun 2007 20:26:58 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C3Qv5b092163
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 20:26:57 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33])
	by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5C3Qsbg022450;
	Mon, 11 Jun 2007 20:26:54 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 11 Jun 2007 20:26:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 20:25:42 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62EA@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmAAEhMlkA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 12 Jun 2007 03:26:54.0077 (UTC) FILETIME=[85F952D0:01C7ACA1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5C3Qw5a092165
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab


The null assurance CAs are already out there :-(

Have been for five years :-(  :-(


> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Kemp, David P.
> Sent: Monday, June 11, 2007 3:42 PM
> To: ietf-pkix@imc.org
> Subject: RE: Three short fixes
> 
> 
> In order to achieve backwards compatibility with a billion 
> browsers, you would have to mark any new extension as 
> non-critical, where it would be ignored by every single 
> browser currently in existence.
> 
> Therefore users would be told that their communication is 
> secure while issuing practices permit (no, positively 
> encourage, once the word on this extension gets out) web site 
> spoofing.
> 
> If you want to use Peter's OID for this, no one can stop you. 
>  But the PKIX WG can refuse to assign an OID whose ostensible 
> purpose is to enable non-advertised encryption but whose 
> actual effect on current browsers would be to advertise 
> secure communications while using null-assurance certificates.
> 
> 
> 
> 
> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org]
> On Behalf Of Hallam-Baker, Phillip
> 
> These are not anonymous communications, they are merely 
> communications that do not require the level of assurance 
> that is necessary to alert the user to tell tham that the 
> communication is secure.
>  
> > > The reason for using a certificate is to allow for backwards 
> > > compatibility with a billion installed browsers.
> 
> 
> -----------
> 
> P.S., the difference between anonymous communications and
> communications for which the participants can claim any desired
> name (e.g. my webserver operating as https://www.verisign.com)
> and into which third parties (e.g. hotel wireless APs) may
> insert themselves eludes me. One definition of anonymous is
> "unnamed", but the second definition is "of unknown origin".
> Spoofed names certainly seem to fit the second definition.
> 
> 




From owner-ietf-pkix@mail.imc.org Thu Jun 14 19:44:35 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyyzT-0007xG-Q2
	for pkix-archive@lists.ietf.org; Thu, 14 Jun 2007 19:44:35 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HyyzT-0001ws-CA
	for pkix-archive@lists.ietf.org; Thu, 14 Jun 2007 19:44:35 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5EMo4AE084592
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 15:50:04 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5EMo44C084591;
	Thu, 14 Jun 2007 15:50:04 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ns1.neustar.com (ns1.neustar.com [156.154.16.138])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5EMo3Xl084575
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Thu, 14 Jun 2007 15:50:04 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns1.neustar.com (Postfix) with ESMTP id DB77426EF1;
	Thu, 14 Jun 2007 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hyy8g-0005IP-MN; Thu, 14 Jun 2007 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-pkix@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pkix-lightweight-ocsp-profile-11.txt 
Message-Id: <E1Hyy8g-0005IP-MN@stiedprstage1.ietf.org>
Date: Thu, 14 Jun 2007 18:50:02 -0400
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>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745


--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Public-Key Infrastructure (X.509) Working Group of the IETF.

	Title		: Lightweight OCSP Profile  for High Volume Environments
	Author(s)	: R. Hurst, A. Deacon
	Filename	: draft-ietf-pkix-lightweight-ocsp-profile-11.txt
	Pages		: 21
	Date		: 2007-6-14
	
This specification defines a profile of the Online Certificate 
   Status Protocol (OCSP) that addresses the scalability issues 
   inherent when using OCSP in large scale (high volume) Public Key 
   Infrastructure (PKI) environments and/or in PKI environments that 
   require a lightweight solution to minimize communication bandwidth 
   and client side processing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pkix-lightweight-ocsp-profile-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-6-14153557.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pkix-lightweight-ocsp-profile-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-6-14153557.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ietf-pkix@mail.imc.org Fri Jun 15 12:02:47 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzEG7-00032c-Du
	for pkix-archive@lists.ietf.org; Fri, 15 Jun 2007 12:02:47 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HzEG5-0002Hf-0l
	for pkix-archive@lists.ietf.org; Fri, 15 Jun 2007 12:02:47 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FF4uf0070825
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 15 Jun 2007 08:04:56 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5FF4uBQ070824;
	Fri, 15 Jun 2007 08:04:56 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ns4.neustar.com (ns4.neustar.com [156.154.24.139])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FF4qV0070798
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Fri, 15 Jun 2007 08:04:55 -0700 (MST)
	(envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10])
	by ns4.neustar.com (Postfix) with ESMTP id 7B0CE2AC92;
	Fri, 15 Jun 2007 15:04:50 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HzDM2-0006NB-8c; Fri, 15 Jun 2007 11:04:50 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Last Call: draft-ietf-pkix-lightweight-ocsp-profile 
         (Lightweight OCSP Profile for High Volume Environments) 
         to Proposed Standard
Reply-To: ietf@ietf.org
Cc: <ietf-pkix@imc.org>
Message-Id: <E1HzDM2-0006NB-8c@stiedprstage1.ietf.org>
Date: Fri, 15 Jun 2007 11:04:50 -0400
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3


The IESG has received a request from the Public-Key Infrastructure 
(X.509) WG (pkix) to consider the following document:

- 'Lightweight OCSP Profile for High Volume Environments'
   <draft-ietf-pkix-lightweight-ocsp-profile-11.txt> as a
   Proposed Standard

An earlier version of this document was sent out for Last Call on
2007-03-05 with the intent of being published as an Informational RFC.
After the recent revisions, the IESG is considering this document for
publication as a Standards-Track RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-06-29. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12331&rfc_flag=0




From owner-ietf-pkix@mail.imc.org Sun Jun 17 23:45:08 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I08Au-0005zg-QY
	for pkix-archive@lists.ietf.org; Sun, 17 Jun 2007 23:45:08 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I08At-0008Bh-L6
	for pkix-archive@lists.ietf.org; Sun, 17 Jun 2007 23:45:08 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5I1dj4F059066
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 17 Jun 2007 18:39:45 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5I1djfd059065;
	Sun, 17 Jun 2007 18:39:45 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailipbo.ntcif.telstra.com.au (mailipbo.ntcif.telstra.com.au [202.12.233.29])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5I1dgCV059047
	for <ietf-pkix@imc.org>; Sun, 17 Jun 2007 18:39:43 -0700 (MST)
	(envelope-from James.H.Manger@team.telstra.com)
Received: from unknown (HELO mailbi.ntcif.telstra.com.au) ([202.12.162.19])
  by mailipbi.ntcif.telstra.com.au with ESMTP; 18 Jun 2007 11:39:41 +1000
Received: from mail2.cdn.telstra.com.au (localhost [127.0.0.1])
	by mailbi.ntcif.telstra.com.au (Postfix) with ESMTP id F3154FF87
	for <ietf-pkix@imc.org>; Mon, 18 Jun 2007 11:39:37 +1000 (EST)
Received: from wsmsg2902.srv.dir.telstra.com (wsmsg2902.srv.dir.telstra.com [172.49.40.51])
	by mail2.cdn.telstra.com.au (Postfix) with ESMTP id 042C541E1C
	for <ietf-pkix@imc.org>; Mon, 18 Jun 2007 11:39:16 +1000 (EST)
Received: from WSMSG2103V.srv.dir.telstra.com ([172.49.40.20]) by wsmsg2902.srv.dir.telstra.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 18 Jun 2007 11:39:15 +1000
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_01C7B149.7A9E4C70"
Subject: RE: Three short fixes: no padlock; text logo; member since
Date: Mon, 18 Jun 2007 11:39:13 +1000
Message-ID: <6215401E01247448A306C54F499111F202BB51C8@WSMSG2103V.srv.dir.telstra.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes: no padlock; text logo; member since
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgKZqHkA
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 18 Jun 2007 01:39:15.0471 (UTC) FILETIME=[7AD2C1F0:01C7B149]
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 544c2133b952fa264803d857bb70855b


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B149.7A9E4C70
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SSBsaWtlIHRoZSBpZGVhIG9mIHJldmVydGluZyB0byBhbiDigJx1bnNlY3VyZWTigJ0gbG9vay1u
LWZlZWwgYW5kIGF2b2lkaW5nIG5hZyBzY3JlZW5zIHdoZW4gdGhlIHNlY3VyaXR5LCB0aG91Z2gg
cHJlc2VudCwgaXMgbm90IOKAnHBlcmZlY3TigJ0uDQoNCkl0IGlzIGJhZCB0aGF0IG1hbnkgY2xp
ZW50cyB0cmVhdCB1bmNvbmZpcm1lZCBzZWN1cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEg
bG9jYWxseS10cnVzdGVkIHJvb3QpIGFzIHdvcnNlIHRoYW4gbm8gc2VjdXJpdHkuIFRoaXMgZGlz
Y291cmFnZXMgYXR0ZW1wdHMgdG8gaW1wcm92ZSBzZWN1cml0eS4NCg0KSSBhbSBsZXNzIHN1cmUg
dGhhdCBhIOKAnG5vIHBhZGxvY2vigJ0gYXR0cmlidXRlIGlzIHRoZSByaWdodCB3YXkgdG8gYWNo
aWV2ZSB0aGlzLg0KDQogDQoNCj5Xb3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBz
YXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMg
dG8gc2ltcGx5IHNob3cgdGhlIGVtYWlsIHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3Nh
Z2UgaXMgc2VjdXJlJy4NCg0KIA0KDQpXb3VsZG7igJl0IGl0IGJlIGJldHRlciB0byBmaXggZW1h
aWwgY2xpZW50cyBzbyB0aGV5IGFsd2F5cyBhY3QgdGhpcyB3YXksIGluc3RlYWQgb2Ygb25seSB0
cmlnZ2VyaW5nIHRoaXMgYmVoYXZpb3VyIGZvciBjZXJ0YWluIGNlcnRpZmljYXRlcz8gVW5sZXNz
IGl0IGlzIGEgdGFjdGljYWwgZGVjaXNpb24gdGhhdCBzb2Z0d2FyZSB2ZW5kb3JzIGFyZSBtb3Jl
IGxpa2VseSB0byBpbXBsZW1lbnQgYSBuZXcgY2VydGlmaWNhdGUgZmVhdHVyZSB0aGFuIGNoYW5n
ZSBleGlzdGluZyBiZWhhdmlvdXIgKGVzcGVjaWFsbHkgaWYgdGhlIGxhdHRlciBtaWdodCBiZSBi
cmFuZGVkIGFzIHdvcnNlbmluZyBzZWN1cml0eSkuDQoNCiANCg0KRm9yIEhUVFBTIGNvbm5lY3Rp
b25zLCBhIGNlcnRpZmljYXRlIHdpdGhvdXQgYSBzdWJqZWN0QWx0TmFtZS5kTlNOYW1lIGZpZWxk
IChhbmQgbm8gZG9tYWluIG5hbWUgaW4gYSBjb21tb24gbmFtZSBjb21wb25lbnQgb2YgdGhlIHN1
YmplY3QgZmllbGQpIHNob3VsZCBiZSBzdWZmaWNpZW50IGZvciBhIGJyb3dzZXIgdG8gc2F5IOKA
nHdlbGwgSSBjYW5ub3QgZG8gdGhlIFVSTC10by1jZXJ0IGNoZWNrIHNvIEkgd2lsbCBkaXNwbGF5
IHRoZSBwYWdlIGp1c3QgbGlrZSBhbiBIVFRQIHBhZ2XigJ06IG5vIGNvbG91cmVkIGFkZHJlc3Mg
YmFyLCBubyBsb2NrZWQgcGFkbG9jaywgbm8gbmFnIHNjcmVlbnMsIHN0aWxsIHVzaW5nIFRMUyBv
bi10aGUtd2lyZSB0aG91Z2guIE5vIHBhdGggdG8gYSB0cnVzdGVkIHJvb3QgKGVnIGEgc2VsZi1z
aWduZWQgY2VydCkgc2hvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5LiBVbmF2YWlsYWJsZSBD
UkxzIGNvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5Lg0KDQogDQoNCk90aGVyIGVycm9ycyBz
dWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yIGEg
bWlzbWF0Y2ggYmV0d2VlbiBVUkwgJiBjZXJ0IG5hbWUgaW1wbHkgdGhlIGNlcnRpZmljYXRlIGhv
bGRlciBoYXMgZG9uZSBzb21ldGhpbmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3
aXRoIG5hZyBzY3JlZW5zIChvciBvdXRyaWdodCByZWZ1c2FsIHRvIGNvbm5lY3QpIGluIHRoZXNl
IGNhc2VzLg0KDQogDQoNClBST0JMRU0NCg0KPiBJIGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0
ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlwdGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhh
dmUgZXhwbGljaXRseSBzYWlkIHRoYXQgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eS4NCg0KIA0K
DQpUaGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBIVFRQUyBzY2hlbWUgaW4gYSBVUkwgaW1wbGllcyBh
IOKAnHNhZmXigJ0gY29ubmVjdGlvbiwgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBvciBh
ZGRyZXNzIGJhciBjb2xvdXIuIElmIGEgdXNlciBkaWRu4oCZdCBrbm93IGlmIHRoZSBVUkwgd2Fz
IEhUVFAgb3IgSFRUUFMgKGVnIHRoZWlyIGJyb3dzZXIgYXV0b21hdGljYWxseSB3ZW50IHRoZXJl
IGFmdGVyIGFuIEhUVFAgMzA3IHJlZGlyZWN0KSB0aGVuIHRyZWF0aW5nIOKAnHVuY29uZmlybWVk
IHNlY3VyaXR54oCdIGFzIOKAnHVuc2VjdXJlZOKAnSB3b3VsZCBiZSByZWFzb25hYmxlLiBPbiB0
aGUgb3RoZXIgaGFuZCwgaWYgSSBjaG9vc2UgbXkgSFRUUFMgYm9va21hcmsgZm9yIG15IGJhbmsg
dGhlbiBJIGV4cGVjdCBteSBicm93c2VyIG5vdCB0byBwcm9jZXNzIGFueSAocG90ZW50aWFsbHkt
bWFsaWNpb3VzKSBodG1sL2phdmFzY3JpcHQvYWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNv
dXJjZS4gSWYgbXkgYnJvd3NlciAocGVyaGFwcyBkdWUgdG8gYSBETlMgYXR0YWNrKSBzaWxlbnRs
eSBhY2NlcHRlZCBjb250ZW50IG5vdCBmcm9tIG15IGJhbmsgSSB3b3VsZCBiZSB3b3JzZSBvZmYu
DQoNCiANCg0KQW55IHZpc2liaWxpdHkgb2YgYW4gSFRUUFMgVVJMIHRvIHRoZSB1c2VyIGNvdWxk
IGJlIGNvbnNpZGVyZWQgYXMgdGhlbSBleHBsaWNpdGx5IHNheWluZyB0aGV5IG5lZWQgY29uZmlk
ZW50aWFsaXR5OiBjaG9vc2luZyBhbiBIVFRQUyBib29rbWFyazsgdHlwaW5nIEhUVFBTIGludG8g
dGhlIGFkZHJlc3MgYmFyOyBjbGlja2luZyBvbiBhbiBIVFRQUyBsaW5rIHdoZW4gdGhlIFVSTCB3
YXMgc2hvd24gaW4gdGhlIHN0YXR1cyBiYXIgYmVmb3JlIHRoZSBjbGljazsgZXZlbiBzZWVpbmcg
SFRUUFMgaW4gdGhlIGFkZHJlc3MgYmFyIGFmdGVyIHJlY2VpdmluZyBhIHBhZ2UgY2FuIGJlIGVu
b3VnaC4NCg0KIA0KDQogDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkZy
b206IEhhbGxhbS1CYWtlciwgUGhpbGxpcA0KU2VudDogVHVlc2RheSwgNSBKdW5lIDIwMDcgMzoz
NyBBTQ0KU3ViamVjdDogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsg
bWVtYmVyIHNpbmNlDQoNCiANCg0K4oCmDQoNCjMpIE5vIFBhZGxvY2sgSWNvbiBhdHRyaWJ1dGUN
Cg0KIA0KDQogICAgVGhpcyBhdHRyaWJ1dGUgd291bGQgYWxsb3cgYSBjZXJ0aWZpY2F0ZSB0byBz
YXkgdGhhdCBubyB1c2VyIGluZGljYXRpb24gc2hvdWxkIGJlIHNwZWNpZmllZCBpbiB0aGUgY2hy
b21lLCBub3Igc2hvdWxkIGFueSBuYWcgc2NyZWVucy4gSXQgd291bGQgYmUgYW4gb3B0aW9uIHRo
YXQgdGhlIGlzc3VpbmcgQ0Egd291bGQgcHV0IGluIGF0IHRoZWlyIGRpc2NyZXRpb24uDQoNCiAN
Cg0KICAgIFRoZSBuZWVkIGZvciB0aGlzIGlzIHRvIGFsbG93IGEgQ0EgdG8gc3VwcG9ydCBhIHdp
ZGUgcmFuZ2Ugb2YgYXBwbGljYXRpb25zIHdoaWNoIHJlcXVpcmUgZW5jcnlwdGlvbiBidXQgcmVx
dWlyZSBldmVuIGxlc3MgYXV0aGVudGljYXRpb24gdGhhbiBjdXJyZW50IHNjaGVtZXMgc3VjaCBh
cyBkb21haW4gdmFsaWRhdGVkIGNlcnRzLiBGb3IgZXhhbXBsZSBzZWxmIHNpZ25lZCBjZXJ0aWZp
Y2F0ZXMsIGNlcnRpZmljYXRlcyBpc3N1ZWQgdG8gZW1iZWRkZWQgaGFyZHdhcmUsIGV0Yy4gZXRj
Lg0KDQogDQoNCiAgICBXaGF0IEkgd2FudCB0byBkbyBpcyB0byBnZXQgdXMgdG8gdGhlIHBvaW50
IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbCBjb21mb3J0YWJsZSB3aXRoIGEgdXNlciBl
eHBlcmllbmNlIHRoYXQgZG9lcyBub3QgY29udGFpbiB0aGUgbmFnIHNjcmVlbnMgdGhhdCBkaXNm
aWd1cmUgY3VycmVudCBzY2hlbWVzLiBJbiBtYW55IGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVpcmVk
IGlzIHRvIHR1cm4gb24gZW5jcnlwdGlvbi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byBiZSB0
b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBleHBpcmVkLCBoYXMgYmVlbiBpc3N1ZWQgYnkg
YW4gdW5rbm93biBDQSBvciBhbnkgb2YgdGhlIHVzdWFsIG5vbnNlbnNlLiBqdXN0IGRvbid0IHRl
bGwgdGhlIHVzZXIgdGhhdCBpdHMgc2FmZSBpbiB0aGUgZmlyc3QgcGxhY2UgYW5kIHRoZSBicm93
c2VyIGRvZXMgbm90IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgZGFuZ2Vyb3VzLg0KDQogDQoNCiAg
ICBDbGVhcmx5IHRoaXMgYXR0cmlidXRlIGlzIHVubmVjZXNzYXJ5IGZyb20gYSB0ZWNobmljYWwg
cG9pbnQgb2Ygdmlldy4gRnJvbSBhIG1hcmtldCBwb2ludCBvZiB2aWV3IGl0IGlzIGVzc2VudGlh
bCBpZiB3ZSBhcmUgZ29pbmcgdG8gZW5zdXJlIHRoYXQgYXBwbGljYXRpb25zIGFyZSBkb2luZyB0
aGUgcmlnaHQgdGhpbmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJldHR5IHN0cm9uZyBz
ZW1hbnRpY3MuIE1hbnkgYXBwbGljYXRpb25zIHJlcXVpcmUgbGVzcy4gV2UgYXJlIG5vdCBnb2lu
ZyB0byBnZXQgZXZlcnlvbmUgd2hvIGN1cnJlbnRseSBoYXMgYSBwYWRsb2NrIGNlcnRpZmljYXRl
IHRvIGdldCBhIGdyZWVuIGJhciBjZXJ0LiBTbyBsZXRzIHNlcnZlIHRoZSBhcHBsaWNhdGlvbnMg
dGhhdCByZXF1aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBwYWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcg
dGhlIHBhZGxvY2sgc2VtYW50aWNzIGZ1cnRoZXIuDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQoNCkZyb206IG93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcgW21haWx0bzpv
d25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQ
aGlsbGlwDQpTZW50OiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzowNiBBTQ0KVG86IEtlbXAsIERh
dmlkIFAuOyBwa2l4DQoNCiANCg0KMykgTm8gUGFkbG9jayBJY29uIGF0dHJpYnV0ZQ0KDQogDQoN
ClRoZSBwb2ludCBoZXJlIGlzIHByZWNpc2VseSB0byBhbGxvdyBhIGNlcnRpZmljYXRlIHRvIHN0
YXRlICd0aGVyZSBhcmUgbm8gc2VjdXJpdHkgY2xhaW1zIGJlaW5nIG1hZGUgaGVyZScuIA0KDQog
DQoNClRoZSB1c2VyIGRvZXMgbm90IGFjY2VwdCB0aGUgY2VydGlmaWNhdGUsIHRoZSBjbGllbnQg
YXBwbGljYXRpb24gZG9lcy4gTm8gdXNlciBoYXMgZXZlciBjaGVja2VkIGEgY2VydGlmaWNhdGUg
cGF0aCBhbmQgbm8gdXNlciBldmVyIHdpbGwuIFRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHRoZSBj
bGllbnQgYXBwbGljYXRpb24gc2hvdWxkIGJlIHRlbGxpbmcgdGhlIHVzZXIgdGhhdCBpdCBpcyAn
c2FmZScgb3Igbm90Lg0KDQogDQoNCkkgZG9uJ3Qgc2VlIHdoeSB3ZSBuZWVkIHRvIHRlbGwgdGhl
IHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVzZWQgdW5sZXNzIHRoZXkgaGF2ZSBleHBs
aWNpdGx5IHNhaWQgdGhhdCB0aGV5IG5lZWQgY29uZmlkZW50aWFsaXR5LiBUZWxsaW5nIHRoZSB1
c2VyIHRoYXQgdGhlcmUgaXMgZW5jcnlwdGlvbiBtZWFucyBhbHNvIHRlbGxpbmcgdGhlbSBhYm91
dCBhIHdob2xlIHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhlciBlcnJvciBjb25kaXRpb25zLiAN
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBv
d25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwu
aW1jLm9yZ10gPG1haWx0bzolNWJtYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyU1
ZD4gIE9uIEJlaGFsZiBPZiBIYWxsYW0tQmFrZXIsIFBoaWxsaXANClNlbnQ6IFR1ZXNkYXksIDEy
IEp1bmUgMjAwNyAxMjoyNCBBTQ0KDQogDQoNCuKApg0KDQpJIGNhbiBnaXZlIHlvdSBhIGNhc3Qg
aXJvbiBjaGFpbiBmb3IgYW4gRVVJNDggTUFDIGFkZHJlc3MuIEJ1dCBpdCBzYXlzIG5vdGhpbmcg
dGhhdCBzaG91bGQgZ2l2ZSBhbiBlbmQgdXNlciB3YXJtIGZ1enppZXMuDQoNCiANCg0KIA0KDQon
VGhpcyBjZXJ0IG1ha2VzIG5vIHNlY3VyaXR5IGNsYWltcyB0aGF0IGFyZSB3b3J0aCBkaXNwbGF5
IHRvIGFuIGVuZCB1c2VyJy4NCg0K4oCmDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KRnJvbTogb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyBbbWFp
bHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddIDxtYWlsdG86JTVibWFpbHRvOm93bmVy
LWlldGYtcGtpeEBtYWlsLmltYy5vcmclNWQ+ICBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQ
aGlsbGlwDQpTZW50OiBUdWVzZGF5LCAxMiBKdW5lIDIwMDcgMzo0NSBBTQ0KDQogDQoNCuKAplRo
ZSBpbmZvcm1hdGlvbiB0byBiZSBlbmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0aGUgaXNzdWUgcHJh
Y3RpY2VzIG9mIHRoZSBjZXJ0aWZpY2F0ZS4gVGhlcmVmb3JlIHRoZXkgZ28gaW50byB0aGUgY2Vy
dGlmaWNhdGUuDQoNCiANCg0KVGhlc2UgYXJlIG5vdCBhbm9ueW1vdXMgY29tbXVuaWNhdGlvbnMs
IHRoZXkgYXJlIG1lcmVseSBjb21tdW5pY2F0aW9ucyB0aGF0IGRvIG5vdCByZXF1aXJlIHRoZSBs
ZXZlbCBvZiBhc3N1cmFuY2UgdGhhdCBpcyBuZWNlc3NhcnkgdG8gYWxlcnQgdGhlIHVzZXIgdG8g
dGVsbCB0aGFtIHRoYXQgdGhlIGNvbW11bmljYXRpb24gaXMgc2VjdXJlLg0KDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IG93bmVyLWlldGYtcGtp
eEBtYWlsLmltYy5vcmcgW21haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8bWFp
bHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkPiAgT24gQmVoYWxm
IE9mIEhhbGxhbS1CYWtlciwgUGhpbGxpcA0KU2VudDogVHVlc2RheSwgMTIgSnVuZSAyMDA3IDEw
OjAwIEFNDQoNCiANCg0KQ2FzZSBpbiBwb2ludCBoZXJlIGJlaW5nIHlvdXIgUy9NSU1FIGNlcnQg
d2hpY2ggZG9lcyBub3Qgc2F0aXNmeSBteSBPdXRsb29rIGNoYWluaW5nIHNvIGdpdmUgYSB3YXJu
aW5nLg0KDQogDQoNCllldCBJIGNhbiBnZXQgbWFpbCBmcm9tIHBsZW50eSBvZiBwbGFjZXMgd2l0
aG91dCBhbnkgc2VjdXJpdHkgYW5kIHdpdGhvdXQgYSB3YXJuaW5nIGVpdGhlci4NCg0KIA0KDQpX
b3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJz
ZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVt
YWlsIHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy4NCg0KIA0K
DQpXaHkgZG8gZm9sayBmZWVsIHRoYXQgdGhlIHVzZXIgaGFzIHRvIGJlIHRvbGQgYWJvdXQgbWVy
ZWx5IHN1Yi1zdGFuZGFyZCBzZWN1cml0eSB3aGVuIDk5JSBvZiB0aGUgSW50ZXJuZXQgaGFzIG5v
IHNlY3VyaXR5IGF0IGFsbD8NCg0K

------_=_NextPart_001_01C7B149.7A9E4C70
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RS
L1JFQy1odG1sNDAiPg0KDQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNv
bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPUdlbmVyYXRvciBj
b250ZW50PSJNaWNyb3NvZnQgV29yZCAxMSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8IS0tW2lmICFt
c29dPg0KPHN0eWxlPg0Kdlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPg0K
PCFbZW5kaWZdLS0+DQo8c3R5bGU+DQo8IS0tDQogLyogRm9udCBEZWZpbml0aW9ucyAqLw0KIEBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KCXBhbm9zZS0xOjIg
MTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0K
CXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IlxAQXJpYWwgVW5pY29kZSBNUyI7DQoJcGFub3NlLTE6MiAxMSA2IDQgMiAyIDIgMiAyIDQ7
fQ0KIC8qIFN0eWxlIERlZmluaXRpb25zICovDQogcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtjb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7
bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkFyaWFsIFVuaWNv
ZGUgTVMiOw0KCWNvbG9yOmJsdWU7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6
bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KQHBhZ2UgU2VjdGlvbjENCgl7
c2l6ZTo1OTUuM3B0IDg0MS45cHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBw
dDt9DQpkaXYuU2VjdGlvbjENCgl7cGFnZTpTZWN0aW9uMTt9DQotLT4NCjwvc3R5bGU+DQoNCjwv
aGVhZD4NCg0KPGJvZHkgbGFuZz1FTi1BVSBsaW5rPWJsdWUgdmxpbms9Ymx1ZT4NCg0KPGRpdiBj
bGFzcz1TZWN0aW9uMT4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPkkg
bGlrZSB0aGUgaWRlYSBvZiByZXZlcnRpbmcgdG8gYW4g4oCcdW5zZWN1cmVk4oCdIGxvb2stbi1m
ZWVsIGFuZA0KYXZvaWRpbmcgbmFnIHNjcmVlbnMgd2hlbiB0aGUgc2VjdXJpdHksIHRob3VnaCBw
cmVzZW50LCBpcyBub3Qg4oCccGVyZmVjdOKAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz5JdCBpcyBiYWQgdGhhdCBtYW55IGNs
aWVudHMgdHJlYXQgdW5jb25maXJtZWQgc2VjdXJpdHkgKGVnIHNpZ25lZCwNCmJ1dCBub3QgYnkg
YSBsb2NhbGx5LXRydXN0ZWQgcm9vdCkgYXMgd29yc2UgdGhhbiBubyBzZWN1cml0eS4gVGhpcyBk
aXNjb3VyYWdlcyBhdHRlbXB0cw0KdG8gaW1wcm92ZSBzZWN1cml0eS48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz5JIGFtIGxlc3Mg
c3VyZSB0aGF0IGEg4oCcbm8gcGFkbG9ja+KAnSBhdHRyaWJ1dGUgaXMgdGhlIHJpZ2h0IHdheSB0
bw0KYWNoaWV2ZSB0aGlzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmlj
b2RlIE1TIjsNCmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tbGVmdDozNi4wcHQnPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiO2NvbG9yOiM5
OTMzMDAnPiZndDtXb3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydA0KY291bGQgc2F5ICd0aGUg
Y29ycmVjdCBjb3Vyc2Ugb2YgYWN0aW9uIGlmIHlvdSBkb24ndCBsaWtlIG1lIGlzIHRvIHNpbXBs
eSBzaG93DQp0aGUgZW1haWwgd2l0aG91dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyBz
ZWN1cmUnLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsN
CmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBV
bmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPldvdWxkbuKAmXQgaXQgYmUgYmV0dGVyIHRvIGZpeCBl
bWFpbCBjbGllbnRzIHNvIHRoZXkgYWx3YXlzIGFjdCB0aGlzDQp3YXksIGluc3RlYWQgb2Ygb25s
eSB0cmlnZ2VyaW5nIHRoaXMgYmVoYXZpb3VyIGZvciBjZXJ0YWluIGNlcnRpZmljYXRlcz8gVW5s
ZXNzDQppdCBpcyBhIHRhY3RpY2FsIGRlY2lzaW9uIHRoYXQgc29mdHdhcmUgdmVuZG9ycyBhcmUg
bW9yZSBsaWtlbHkgdG8gaW1wbGVtZW50IGENCm5ldyBjZXJ0aWZpY2F0ZSBmZWF0dXJlIHRoYW4g
Y2hhbmdlIGV4aXN0aW5nIGJlaGF2aW91ciAoZXNwZWNpYWxseSBpZiB0aGUNCmxhdHRlciBtaWdo
dCBiZSBicmFuZGVkIGFzIHdvcnNlbmluZyBzZWN1cml0eSkuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KY29sb3I6Ymx1ZSc+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KY29sb3I6Ymx1ZSc+Rm9y
IEhUVFBTIGNvbm5lY3Rpb25zLCBhIGNlcnRpZmljYXRlIHdpdGhvdXQgYSBzdWJqZWN0QWx0TmFt
ZS5kTlNOYW1lDQpmaWVsZCAoYW5kIG5vIGRvbWFpbiBuYW1lIGluIGEgY29tbW9uIG5hbWUgY29t
cG9uZW50IG9mIHRoZSBzdWJqZWN0IGZpZWxkKQ0Kc2hvdWxkIGJlIHN1ZmZpY2llbnQgZm9yIGEg
YnJvd3NlciB0byBzYXkg4oCcd2VsbCBJIGNhbm5vdCBkbyB0aGUgVVJMLXRvLWNlcnQNCmNoZWNr
IHNvIEkgd2lsbCBkaXNwbGF5IHRoZSBwYWdlIGp1c3QgbGlrZSBhbiBIVFRQIHBhZ2XigJ06IG5v
IGNvbG91cmVkIGFkZHJlc3MNCmJhciwgbm8gbG9ja2VkIHBhZGxvY2ssIG5vIG5hZyBzY3JlZW5z
LCBzdGlsbCB1c2luZyBUTFMgb24tdGhlLXdpcmUgdGhvdWdoLiBObw0KcGF0aCB0byBhIHRydXN0
ZWQgcm9vdCAoZWcgYSBzZWxmLXNpZ25lZCBjZXJ0KSBzaG91bGQgYmUgdHJlYXRlZCB0aGUgc2Ft
ZSB3YXkuDQpVbmF2YWlsYWJsZSBDUkxzIGNvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJs
dWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1T
IjsNCmNvbG9yOmJsdWUnPk90aGVyIGVycm9ycyBzdWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1
cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yDQphIG1pc21hdGNoIGJldHdlZW4gVVJMICZhbXA7
IGNlcnQgbmFtZSBpbXBseSB0aGUgY2VydGlmaWNhdGUgaG9sZGVyIGhhcyBkb25lDQpzb21ldGhp
bmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChvciBv
dXRyaWdodCByZWZ1c2FsDQp0byBjb25uZWN0KSBpbiB0aGVzZSBjYXNlcy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpi
bHVlJz5QUk9CTEVNPG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21hcmdpbi1sZWZ0OjM2LjBwdCc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7
DQpmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7Y29sb3I6Izk5MzMwMCc+Jmd0OyBJIGRv
bid0IHNlZSB3aHkgd2UgbmVlZCB0bw0KdGVsbCB0aGUgdXNlciB0aGF0IGVuY3J5cHRpb24gaXMg
YmVpbmcgdXNlZCB1bmxlc3MgdGhleSBoYXZlIGV4cGxpY2l0bHkgc2FpZA0KdGhhdCB0aGV5IG5l
ZWQgY29uZmlkZW50aWFsaXR5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBV
bmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPlRoZSBwcm9ibGVtIGlzIHRoYXQg
dGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg4oCcc2FmZeKAnQ0KY29ubmVjdGlv
biwgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBvciBhZGRyZXNzIGJhciBjb2xvdXIuIElm
IGEgdXNlciBkaWRu4oCZdA0Ka25vdyBpZiB0aGUgVVJMIHdhcyBIVFRQIG9yIEhUVFBTIChlZyB0
aGVpciBicm93c2VyIGF1dG9tYXRpY2FsbHkgd2VudCB0aGVyZQ0KYWZ0ZXIgYW4gSFRUUCAzMDcg
cmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCcdW5jb25maXJtZWQgc2VjdXJpdHnigJ0gYXMg4oCc
dW5zZWN1cmVk4oCdDQp3b3VsZCBiZSByZWFzb25hYmxlLiBPbiB0aGUgb3RoZXIgaGFuZCwgaWYg
SSBjaG9vc2UgbXkgSFRUUFMgYm9va21hcmsgZm9yIG15DQpiYW5rIHRoZW4gSSBleHBlY3QgbXkg
YnJvd3NlciA8aT5ub3Q8L2k+IHRvIHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMp
DQpodG1sL2phdmFzY3JpcHQvYWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNvdXJjZS4gSWYg
bXkgYnJvd3NlciAocGVyaGFwcyBkdWUNCnRvIGEgRE5TIGF0dGFjaykgc2lsZW50bHkgYWNjZXB0
ZWQgY29udGVudCBub3QgZnJvbSBteSBiYW5rIEkgd291bGQgYmUgd29yc2UNCm9mZi48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpj
b2xvcjpibHVlJz5BbnkgdmlzaWJpbGl0eSBvZiBhbiBIVFRQUyBVUkwgdG8gdGhlIHVzZXIgY291
bGQgYmUgY29uc2lkZXJlZCBhcyB0aGVtDQpleHBsaWNpdGx5IHNheWluZyB0aGV5IG5lZWQgY29u
ZmlkZW50aWFsaXR5OiBjaG9vc2luZyBhbiBIVFRQUyBib29rbWFyazsgdHlwaW5nDQpIVFRQUyBp
bnRvIHRoZSBhZGRyZXNzIGJhcjsgY2xpY2tpbmcgb24gYW4gSFRUUFMgbGluayB3aGVuIHRoZSBV
Ukwgd2FzIHNob3duIGluDQp0aGUgc3RhdHVzIGJhciBiZWZvcmUgdGhlIGNsaWNrOyBldmVuIHNl
ZWluZyBIVFRQUyBpbiB0aGUgYWRkcmVzcyBiYXIgYWZ0ZXINCnJlY2VpdmluZyBhIHBhZ2UgY2Fu
IGJlIGVub3VnaC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBN
UyI7DQpjb2xvcjpibHVlJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJp
YWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQoNCjxkaXY+DQoNCjxkaXYgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWNlbnRlciBzdHlsZT0ndGV4
dC1hbGlnbjpjZW50ZXInPg0KDQo8aHIgc2l6ZT0yIHdpZHRoPSIxMDAlIiBhbGlnbj1jZW50ZXIg
dGFiaW5kZXg9LTE+DQoNCjwvZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6VGFob21hJz5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlRhaG9tYSc+IEhhbGxh
bS1CYWtlciwgUGhpbGxpcDxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAz
OjM3IEFNPGJyPg0KPGI+U3ViamVjdDo8L2I+IFRocmVlIHNob3J0IGZpeGVzOiBubyBwYWRsb2Nr
OyB0ZXh0IGxvZ287IG1lbWJlciBzaW5jZTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+
DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTpBcmlhbCc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8
L2Rpdj4NCg0KPGRpdj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOmJsdWUnPuKApjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3Ryb25n
PjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4zKQ0KTm8g
UGFkbG9jayBJY29uIGF0dHJpYnV0ZTwvc3Bhbj48L3N0cm9uZz48bzpwPjwvbzpwPjwvcD4NCg0K
PC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDsmbmJzcDsm
bmJzcDsgPHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6DQpBcmlhbCc+
VGhpcyBhdHRyaWJ1dGUgd291bGQgYWxsb3cgYSBjZXJ0aWZpY2F0ZSB0byBzYXkgdGhhdCBubyB1
c2VyIGluZGljYXRpb24NCnNob3VsZCBiZSBzcGVjaWZpZWQgaW4gdGhlIGNocm9tZSwgbm9yIHNo
b3VsZCBhbnkgbmFnIHNjcmVlbnMuIEl0IHdvdWxkIGJlIGFuDQpvcHRpb24gdGhhdCB0aGUgaXNz
dWluZyBDQSB3b3VsZCBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi48L3NwYW4+PG86cD48L286
cD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+Jm5ic3A7PG86
cD48L286cD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
Og0KQXJpYWwnPlRoZSBuZWVkIGZvciB0aGlzIGlzIHRvIGFsbG93IGEgQ0EgdG8gc3VwcG9ydCBh
IHdpZGUgcmFuZ2Ugb2YNCmFwcGxpY2F0aW9ucyB3aGljaCZuYnNwO3JlcXVpcmUgZW5jcnlwdGlv
biBidXQgcmVxdWlyZSBldmVuIGxlc3MgYXV0aGVudGljYXRpb24NCnRoYW4gY3VycmVudCBzY2hl
bWVzIHN1Y2ggYXMgZG9tYWluIHZhbGlkYXRlZCBjZXJ0cy4gRm9yIGV4YW1wbGUgc2VsZiBzaWdu
ZWQNCmNlcnRpZmljYXRlcywgY2VydGlmaWNhdGVzIGlzc3VlZCB0byBlbWJlZGRlZCBoYXJkd2Fy
ZSwgZXRjLiBldGMuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPGRp
dj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToNCkFyaWFsJz5XaGF0IEkgd2FudCB0byBkbyBp
cyB0byBnZXQgdXMgdG8gdGhlIHBvaW50IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbA0K
Y29tZm9ydGFibGUgd2l0aCBhIHVzZXIgZXhwZXJpZW5jZSB0aGF0IGRvZXMgbm90IGNvbnRhaW4g
dGhlIG5hZyBzY3JlZW5zIHRoYXQNCmRpc2ZpZ3VyZSBjdXJyZW50IHNjaGVtZXMuIEluIG1hbnkg
Y2FzZXMgYWxsIHRoYXQgaXMgcmVxdWlyZWQgaXMgdG8gdHVybiBvbg0KZW5jcnlwdGlvbi4gVGhl
IHVzZXIgZG9lcyBub3QgbmVlZCB0byBiZSB0b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBl
eHBpcmVkLA0KaGFzIGJlZW4gaXNzdWVkIGJ5IGFuIHVua25vd24gQ0Egb3IgYW55IG9mIHRoZSB1
c3VhbCBub25zZW5zZS4ganVzdCBkb24ndCB0ZWxsDQp0aGUgdXNlciB0aGF0IGl0cyBzYWZlIGlu
IHRoZSBmaXJzdCBwbGFjZSBhbmQgdGhlIGJyb3dzZXIgZG9lcyBub3QgbmVlZCB0byBzYXkNCnRo
YXQgaXQgaXMgZGFuZ2Vyb3VzLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+DQoNCjxk
aXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+
DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDsmbmJzcDsmbmJzcDsgPHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6DQpBcmlhbCc+Q2xlYXJseSB0aGlz
IGF0dHJpYnV0ZSBpcyB1bm5lY2Vzc2FyeSBmcm9tIGEgdGVjaG5pY2FsIHBvaW50IG9mIHZpZXcu
DQpGcm9tIGEgbWFya2V0IHBvaW50IG9mIHZpZXcgaXQgaXMgZXNzZW50aWFsIGlmIHdlIGFyZSBn
b2luZyB0byBlbnN1cmUgdGhhdA0KYXBwbGljYXRpb25zIGFyZSBkb2luZyB0aGUgcmlnaHQgdGhp
bmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJldHR5IHN0cm9uZw0Kc2VtYW50aWNzLiBN
YW55IGFwcGxpY2F0aW9ucyByZXF1aXJlIGxlc3MuIFdlIGFyZSBub3QgZ29pbmcgdG8gZ2V0IGV2
ZXJ5b25lIHdobw0KY3VycmVudGx5IGhhcyBhIHBhZGxvY2sgY2VydGlmaWNhdGUgdG8gZ2V0IGEg
Z3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2VydmUgdGhlDQphcHBsaWNhdGlvbnMgdGhhdCByZXF1
aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBwYWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcgdGhlDQpwYWRs
b2NrIHNlbWFudGljcyBmdXJ0aGVyLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+DQoN
CjxkaXYgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWNlbnRlciBzdHlsZT0ndGV4dC1hbGlnbjpjZW50
ZXInPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpuYXZ5Jz4NCg0KPGhyIHNpemU9MiB3aWR0aD0iMTAwJSIgYWxpZ249Y2VudGVyIHRhYkluZGV4
PS0xPg0KDQo8L3NwYW4+PC9kaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpUYWhvbWE7DQpjb2xvcjpibGFjayc+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlRh
aG9tYTsNCmNvbG9yOmJsYWNrJz4gb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZw0KW21haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkhhbGxh
bS1CYWtlciwgUGhpbGxpcDxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgNyBKdW5lIDIwMDcg
MzowNiBBTTxicj4NCjxiPlRvOjwvYj4gS2VtcCwgRGF2aWQgUC47IHBraXg8L3NwYW4+PHNwYW4g
c3R5bGU9J2NvbG9yOm5hdnknPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFjayc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+
PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHN0cm9uZz48c3BhbiBzdHlsZT0nZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDsNCmNvbG9yOmJsYWNrJz4zKSBObyBQYWRsb2NrIElj
b24gYXR0cmlidXRlPC9zcGFuPjwvc3Ryb25nPjxzcGFuDQpzdHlsZT0nY29sb3I6YmxhY2snPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdj
b2xvcjpuYXZ5Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibHVlJz5UaGUmbmJzcDtwb2ludA0KaGVyZSBpcyBwcmVjaXNlbHkgdG8gYWxsb3cgYSBjZXJ0
aWZpY2F0ZSB0byBzdGF0ZSAndGhlcmUgYXJlIG5vIHNlY3VyaXR5IGNsYWltcw0KYmVpbmcgbWFk
ZSBoZXJlJy4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOm5hdnknPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFj
ayc+Jm5ic3A7PC9zcGFuPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTpBcmlhbDtjb2xvcjpibHVlJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibHVlJz5UaGUNCnVzZXIgZG9lcyBub3QgYWNjZXB0IHRoZSBjZXJ0aWZpY2F0ZSwgdGhl
IGNsaWVudCBhcHBsaWNhdGlvbiBkb2VzLiBObyB1c2VyIGhhcw0KZXZlciBjaGVja2VkIGEgY2Vy
dGlmaWNhdGUgcGF0aCBhbmQgbm8gdXNlciBldmVyIHdpbGwuIFRoZSBxdWVzdGlvbiBpcyB3aGV0
aGVyDQp0aGUgY2xpZW50IGFwcGxpY2F0aW9uIHNob3VsZCBiZSB0ZWxsaW5nIHRoZSB1c2VyIHRo
YXQgaXQgaXMgJ3NhZmUnIG9yIG5vdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6YmxhY2snPiZuYnNwOzwvc3Bhbj48c3Bhbg0K
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+PG86
cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+SQ0KZG9uJ3Qgc2Vl
IHdoeSB3ZSBuZWVkIHRvIHRlbGwgdGhlIHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVz
ZWQgdW5sZXNzDQp0aGV5IGhhdmUgZXhwbGljaXRseSBzYWlkIHRoYXQgdGhleSBuZWVkIGNvbmZp
ZGVudGlhbGl0eS4gVGVsbGluZyB0aGUgdXNlciB0aGF0DQp0aGVyZSBpcyBlbmNyeXB0aW9uIG1l
YW5zIGFsc28gdGVsbGluZyB0aGVtIGFib3V0IGEgd2hvbGUgcmFuZ2Ugb2YgZmFpbHVyZXMgYW5k
DQpvdGhlciBlcnJvciBjb25kaXRpb25zLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNs
YXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTo2LjBwdCc+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTpUYWhvbWE7Y29sb3I6YmxhY2snPl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCjxiPkZyb206PC9iPiA8
YSBocmVmPSJtYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyI+b3duZXItaWV0Zi1w
a2l4QG1haWwuaW1jLm9yZzwvYT4NCjxhIGhyZWY9Im1haWx0bzolNWJtYWlsdG86b3duZXItaWV0
Zi1wa2l4QG1haWwuaW1jLm9yZyU1ZCI+W21haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnXTwvYT4NCjxiPk9uIEJlaGFsZiBPZiA8L2I+SGFsbGFtLUJha2VyLCBQaGlsbGlwPGJyPg0K
PGI+U2VudDo8L2I+IFR1ZXNkYXksIDEyIEp1bmUgMjAwNyAxMjoyNCBBTTwvc3Bhbj48c3BhbiBz
dHlsZT0nY29sb3I6YmxhY2snPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2Nv
bG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibHVlJz7igKY8L3NwYW4+PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OkFyaWFsO2NvbG9yOmJsYWNrJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlh
bDtjb2xvcjpibGFjayc+SQ0KY2FuIGdpdmUgeW91IGEgY2FzdCBpcm9uIGNoYWluIGZvciBhbiBF
VUk0OCBNQUMgYWRkcmVzcy4gQnV0IGl0IHNheXMgbm90aGluZw0KdGhhdCBzaG91bGQgZ2l2ZSBh
biBlbmQgdXNlciB3YXJtIGZ1enppZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJp
YWw7Y29sb3I6YmxhY2snPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFs
O2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibGFjayc+J1RoaXMNCmNlcnQgbWFrZXMgbm8gc2VjdXJpdHkgY2xhaW1zIHRoYXQgYXJl
IHdvcnRoIGRpc3BsYXkgdG8gYW4gZW5kIHVzZXInLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpibGFjayc+4oCm
PC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6VGFob21h
O2NvbG9yOmJsdWUnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFs
IHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpibGFjayc+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KPGI+RnJvbTo8L2I+IDxhIGhyZWY9Im1haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIj5vd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnPC9hPg0KPGEgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5p
bWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddPC9hPg0KPGI+
T24gQmVoYWxmIE9mIDwvYj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8YnI+DQo8Yj5TZW50OjwvYj4g
VHVlc2RheSwgMTIgSnVuZSAyMDA3IDM6NDUgQU08L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOmJs
YWNrJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpibGFjayc+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+4oCmPC9z
cGFuPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibGFjayc+VGhlIGluZm9ybWF0aW9uIHRvIGJlDQplbmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0
aGUgaXNzdWUgcHJhY3RpY2VzIG9mIHRoZSBjZXJ0aWZpY2F0ZS4gVGhlcmVmb3JlIHRoZXkNCmdv
IGludG8gdGhlIGNlcnRpZmljYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFs
O2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibGFjayc+VGhlc2UNCmFyZSBub3QgYW5vbnltb3VzIGNvbW11bmljYXRpb25zLCB0aGV5
IGFyZSBtZXJlbHkgY29tbXVuaWNhdGlvbnMgdGhhdCBkbyBub3QgcmVxdWlyZQ0KdGhlIGxldmVs
IG9mIGFzc3VyYW5jZSB0aGF0IGlzIG5lY2Vzc2FyeSB0byBhbGVydCB0aGUgdXNlciB0byB0ZWxs
IHRoYW0gdGhhdA0KdGhlIGNvbW11bmljYXRpb24gaXMgc2VjdXJlLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpi
bGFjayc+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0K
PGI+RnJvbTo8L2I+IDxhIGhyZWY9Im1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3Jn
Ij5vd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnPC9hPg0KPGEgaHJlZj0ibWFpbHRvOiU1Ym1h
aWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYt
cGtpeEBtYWlsLmltYy5vcmddPC9hPg0KPGI+T24gQmVoYWxmIE9mIDwvYj5IYWxsYW0tQmFrZXIs
IFBoaWxsaXA8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgMTIgSnVuZSAyMDA3IDEwOjAwIEFN
PC9zcGFuPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFjayc+PG86cD48L286cD48L3NwYW4+PC9wPg0K
DQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6QXJpYWw7Y29sb3I6YmxhY2snPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OkFyaWFsO2NvbG9yOmJsYWNrJz5DYXNlDQppbiBwb2ludCBoZXJlIGJlaW5nIHlvdXIgUy9N
SU1FIGNlcnQgd2hpY2ggZG9lcyBub3Qgc2F0aXNmeSBteSBPdXRsb29rIGNoYWluaW5nDQpzbyBn
aXZlIGEgd2FybmluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpi
bGFjayc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymxh
Y2snPllldA0KSSBjYW4gZ2V0IG1haWwgZnJvbSBwbGVudHkgb2YgcGxhY2VzIHdpdGhvdXQgYW55
IHNlY3VyaXR5IGFuZCB3aXRob3V0IGEgd2FybmluZw0KZWl0aGVyLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTpBcmlhbDtjb2xvcjpibGFjayc+V291bGRuJ3QNCml0IGJlIG5pY2UgaWYgYSBj
ZXJ0IGNvdWxkIHNheSAndGhlIGNvcnJlY3QgY291cnNlIG9mIGFjdGlvbiBpZiB5b3UgZG9uJ3Qg
bGlrZQ0KbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVtYWlsIHdpdGhvdXQgYW55IGluZGljYXRp
b24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNs
YXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpB
cmlhbDtjb2xvcjpibGFjayc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJp
YWw7Y29sb3I6YmxhY2snPldoeQ0KZG8gZm9sayBmZWVsIHRoYXQgdGhlIHVzZXIgaGFzIHRvIGJl
IHRvbGQgYWJvdXQgbWVyZWx5IHN1Yi1zdGFuZGFyZCBzZWN1cml0eQ0Kd2hlbiA5OSUgb2YgdGhl
IEludGVybmV0IGhhcyBubyBzZWN1cml0eSBhdCBhbGw/PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
DQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo=

------_=_NextPart_001_01C7B149.7A9E4C70--




From owner-ietf-pkix@mail.imc.org Wed Jun 20 12:44:44 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I13IS-0005HK-PJ
	for pkix-archive@lists.ietf.org; Wed, 20 Jun 2007 12:44:44 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I13IR-0004Kn-EA
	for pkix-archive@lists.ietf.org; Wed, 20 Jun 2007 12:44:44 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KFVEWM089844
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 20 Jun 2007 08:31:15 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5KFVE82089838;
	Wed, 20 Jun 2007 08:31:14 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KFVCNU089817
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Wed, 20 Jun 2007 08:31:13 -0700 (MST)
	(envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35])
	by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l5KFVCqO028283;
	Wed, 20 Jun 2007 08:31:12 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Wed, 20 Jun 2007 08:31:11 -0700
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_01C7B350.07C19428"
Subject: RE: Three short fixes: no padlock; text logo; member since
Date: Wed, 20 Jun 2007 08:29:50 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012F622A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <6215401E01247448A306C54F499111F202BB51C8@WSMSG2103V.srv.dir.telstra.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes: no padlock; text logo; member since
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgKZqHkAAIZIOoA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>,
        "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 20 Jun 2007 15:31:11.0638 (UTC) FILETIME=[0800E360:01C7B350]
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>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9724479da43a8325ad975c1a9b841870


This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B350.07C19428
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhlIGlzc3VlIGhlcmUgaXMgYmFja3dhcmRzIGNvbXBhdGliaWxpdHkuDQogDQpBbnkgY2VydGlm
aWNhdGUgaXNzdWVkIHRvZGF5IG11c3Qgd29yayBhY2NhcHRhYmx5IHdpdGggZXhpc3RpbmcgYnJv
d3NlcnMuIFRoYXQgbWVhbnMgY2hhaW5pbmcgdXAgdG8gYW4gZW1iZWRkZWQgcm9vdC4gVW5kZXIg
dGhlIHJ1bGVzIGFzIHRoZXkgYXJlIHRvZGF5IGEgY2VydCBpc3N1ZXIgY2FuIGlzc3VlIGEgY2Vy
dGlmaWNhdGUgd2l0aCBlc3NlbnRpYWxseSBubyBtZWFuaW5nZnVsIGF1dGhlbnRpY2F0aW9uIGFu
ZCBtYW55IGRvLg0KIA0KVGhlIHBvaW50IGlzIHRvIGFsbG93IGFuIGlzc3VlciB0byBkaWZmZXJl
bnRpYXRlIGJldHdlZW4gY2VydGlmaWNhdGVzIHRoYXQgYXJlIGRlc2lnbmVkIHRvIHByb3ZpZGUg
YSBtZWFuaW5nZnVsIGRlZ3JlZSBvZiBhY2NvdW50YWJpbGl0eSBmcm9tIHRob3NlIHdoaWNoIGFy
ZSBzaW1wbHkgZGVzaWduZWQgdG8gdHVybiBvbiBTU0wgaW4gdGhlIGRlcGxveWVkIGJhc2Ugb2Yg
YSBiaWxsaW9uIGJyb3dzZXJzLiBPdmVyIHRpbWUgdGhlIGRlcGxveW1lbnQgb2YgYnJvd3NlcnMg
dGhhdCBvYnNlcnZlIHRoZSBPSUQgd291bGQgaW5jcmVhc2UuDQogDQogDQpJZiB3ZSB3ZXJlIGRl
c2lnbmluZyBmcm9tIHNjcmF0Y2ggdGhlIHNlbnNpYmxlIHdheSB0byBkbyB0aGlzIHdvdWxkIGJl
IHRvIGhhdmUgYW4gT0lEIHdpdGggcG9zaXRpdmUgc2VtYW50aWNzICdhc3NlcnQgc2VjdXJpdHkg
dG8gdGhlIHVzZXInLiBTaW5jZSB3ZSBkb24ndCBoYXZlIHRoYXQgbHV4dXJ5IGFuZCBzaW5jZSB3
ZSBoYXZlIHRvIGRlYWwgd2l0aCB0aGUgYmlsbGlvbiBkZXBsb3llZCBicm93c2VycyB3ZSBuZWVk
IGEgZGlmZmVyZW50IGFwcHJvYWNoLg0KIA0KSSBkbyBub3QgYWdyZWUgd2l0aCB0aGUgc2VudGlt
ZW50IHRoYXQgYSBzdGFuZGFyZHMgcHJvY2VzcyBzaG91bGQgb25seSBkZWFsIHdpdGggcGVyZmVj
dCBzaXR1YXRpb25zIGFuZCBzdGljayBpdHMgaGVhZCBpbiB0aGUgc2FuZCB3aGVuIGl0IGNvbWVz
IHRvIHRvdWdoIGRlcGxveW1lbnQgaXNzdWVzLiBNYW5hZ2luZyB0aGUgY29uc3RyYWludHMgb2Yg
dGhlIGRlcGxveWVkIGJhc2Ugc2hvdWxkIGJlIHRoZSBmaXJzdCBjb25jZXJuIGZvciBhIFdHIHRo
YXQgaGFzIGJlZW4gaW4gZXhpc3RlbmNlIGZvciB0ZW4geWVhcnMuIA0KIA0KQXQgbGVhc3QgUEtJ
WCBoYXMgYSBkZXBsb3llZCBiYXNlIHRvIHdvcnJ5IGFib3V0Lg0KIA0KDQoNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQoNCglGcm9tOiBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gT24gQmVoYWxmIE9mIE1h
bmdlciwgSmFtZXMgSA0KCVNlbnQ6IFN1bmRheSwgSnVuZSAxNywgMjAwNyA5OjM5IFBNDQoJVG86
IHBraXgNCglTdWJqZWN0OiBSRTogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQg
bG9nbzsgbWVtYmVyIHNpbmNlDQoJDQoJDQoNCglJIGxpa2UgdGhlIGlkZWEgb2YgcmV2ZXJ0aW5n
IHRvIGFuIOKAnHVuc2VjdXJlZOKAnSBsb29rLW4tZmVlbCBhbmQgYXZvaWRpbmcgbmFnIHNjcmVl
bnMgd2hlbiB0aGUgc2VjdXJpdHksIHRob3VnaCBwcmVzZW50LCBpcyBub3Qg4oCccGVyZmVjdOKA
nS4NCg0KCUl0IGlzIGJhZCB0aGF0IG1hbnkgY2xpZW50cyB0cmVhdCB1bmNvbmZpcm1lZCBzZWN1
cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEgbG9jYWxseS10cnVzdGVkIHJvb3QpIGFzIHdv
cnNlIHRoYW4gbm8gc2VjdXJpdHkuIFRoaXMgZGlzY291cmFnZXMgYXR0ZW1wdHMgdG8gaW1wcm92
ZSBzZWN1cml0eS4NCg0KCUkgYW0gbGVzcyBzdXJlIHRoYXQgYSDigJxubyBwYWRsb2Nr4oCdIGF0
dHJpYnV0ZSBpcyB0aGUgcmlnaHQgd2F5IHRvIGFjaGlldmUgdGhpcy4NCg0KCSANCg0KCT5Xb3Vs
ZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBv
ZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVtYWls
IHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy4NCg0KCSANCg0K
CVdvdWxkbuKAmXQgaXQgYmUgYmV0dGVyIHRvIGZpeCBlbWFpbCBjbGllbnRzIHNvIHRoZXkgYWx3
YXlzIGFjdCB0aGlzIHdheSwgaW5zdGVhZCBvZiBvbmx5IHRyaWdnZXJpbmcgdGhpcyBiZWhhdmlv
dXIgZm9yIGNlcnRhaW4gY2VydGlmaWNhdGVzPyBVbmxlc3MgaXQgaXMgYSB0YWN0aWNhbCBkZWNp
c2lvbiB0aGF0IHNvZnR3YXJlIHZlbmRvcnMgYXJlIG1vcmUgbGlrZWx5IHRvIGltcGxlbWVudCBh
IG5ldyBjZXJ0aWZpY2F0ZSBmZWF0dXJlIHRoYW4gY2hhbmdlIGV4aXN0aW5nIGJlaGF2aW91ciAo
ZXNwZWNpYWxseSBpZiB0aGUgbGF0dGVyIG1pZ2h0IGJlIGJyYW5kZWQgYXMgd29yc2VuaW5nIHNl
Y3VyaXR5KS4NCg0KCSANCg0KCUZvciBIVFRQUyBjb25uZWN0aW9ucywgYSBjZXJ0aWZpY2F0ZSB3
aXRob3V0IGEgc3ViamVjdEFsdE5hbWUuZE5TTmFtZSBmaWVsZCAoYW5kIG5vIGRvbWFpbiBuYW1l
IGluIGEgY29tbW9uIG5hbWUgY29tcG9uZW50IG9mIHRoZSBzdWJqZWN0IGZpZWxkKSBzaG91bGQg
YmUgc3VmZmljaWVudCBmb3IgYSBicm93c2VyIHRvIHNheSDigJx3ZWxsIEkgY2Fubm90IGRvIHRo
ZSBVUkwtdG8tY2VydCBjaGVjayBzbyBJIHdpbGwgZGlzcGxheSB0aGUgcGFnZSBqdXN0IGxpa2Ug
YW4gSFRUUCBwYWdl4oCdOiBubyBjb2xvdXJlZCBhZGRyZXNzIGJhciwgbm8gbG9ja2VkIHBhZGxv
Y2ssIG5vIG5hZyBzY3JlZW5zLCBzdGlsbCB1c2luZyBUTFMgb24tdGhlLXdpcmUgdGhvdWdoLiBO
byBwYXRoIHRvIGEgdHJ1c3RlZCByb290IChlZyBhIHNlbGYtc2lnbmVkIGNlcnQpIHNob3VsZCBi
ZSB0cmVhdGVkIHRoZSBzYW1lIHdheS4gVW5hdmFpbGFibGUgQ1JMcyBjb3VsZCBiZSB0cmVhdGVk
IHRoZSBzYW1lIHdheS4NCg0KCSANCg0KCU90aGVyIGVycm9ycyBzdWNoIGFzIGFuIGluY29ycmVj
dCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yIGEgbWlzbWF0Y2ggYmV0d2VlbiBV
UkwgJiBjZXJ0IG5hbWUgaW1wbHkgdGhlIGNlcnRpZmljYXRlIGhvbGRlciBoYXMgZG9uZSBzb21l
dGhpbmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChv
ciBvdXRyaWdodCByZWZ1c2FsIHRvIGNvbm5lY3QpIGluIHRoZXNlIGNhc2VzLg0KDQoJIA0KDQoJ
UFJPQkxFTQ0KDQoJPiBJIGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRo
YXQgZW5jcnlwdGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhhdmUgZXhwbGljaXRseSBz
YWlkIHRoYXQgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eS4NCg0KCSANCg0KCVRoZSBwcm9ibGVt
IGlzIHRoYXQgdGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg4oCcc2FmZeKAnSBj
b25uZWN0aW9uLCByZWdhcmRsZXNzIG9mIGEgcGFkbG9jayBpY29uIG9yIGFkZHJlc3MgYmFyIGNv
bG91ci4gSWYgYSB1c2VyIGRpZG7igJl0IGtub3cgaWYgdGhlIFVSTCB3YXMgSFRUUCBvciBIVFRQ
UyAoZWcgdGhlaXIgYnJvd3NlciBhdXRvbWF0aWNhbGx5IHdlbnQgdGhlcmUgYWZ0ZXIgYW4gSFRU
UCAzMDcgcmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCcdW5jb25maXJtZWQgc2VjdXJpdHnigJ0g
YXMg4oCcdW5zZWN1cmVk4oCdIHdvdWxkIGJlIHJlYXNvbmFibGUuIE9uIHRoZSBvdGhlciBoYW5k
LCBpZiBJIGNob29zZSBteSBIVFRQUyBib29rbWFyayBmb3IgbXkgYmFuayB0aGVuIEkgZXhwZWN0
IG15IGJyb3dzZXIgbm90IHRvIHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMpIGh0
bWwvamF2YXNjcmlwdC9hY3RpdmV4L2ZsYXNoIGZvciBhbnkgb3RoZXIgc291cmNlLiBJZiBteSBi
cm93c2VyIChwZXJoYXBzIGR1ZSB0byBhIEROUyBhdHRhY2spIHNpbGVudGx5IGFjY2VwdGVkIGNv
bnRlbnQgbm90IGZyb20gbXkgYmFuayBJIHdvdWxkIGJlIHdvcnNlIG9mZi4NCg0KCSANCg0KCUFu
eSB2aXNpYmlsaXR5IG9mIGFuIEhUVFBTIFVSTCB0byB0aGUgdXNlciBjb3VsZCBiZSBjb25zaWRl
cmVkIGFzIHRoZW0gZXhwbGljaXRseSBzYXlpbmcgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eTog
Y2hvb3NpbmcgYW4gSFRUUFMgYm9va21hcms7IHR5cGluZyBIVFRQUyBpbnRvIHRoZSBhZGRyZXNz
IGJhcjsgY2xpY2tpbmcgb24gYW4gSFRUUFMgbGluayB3aGVuIHRoZSBVUkwgd2FzIHNob3duIGlu
IHRoZSBzdGF0dXMgYmFyIGJlZm9yZSB0aGUgY2xpY2s7IGV2ZW4gc2VlaW5nIEhUVFBTIGluIHRo
ZSBhZGRyZXNzIGJhciBhZnRlciByZWNlaXZpbmcgYSBwYWdlIGNhbiBiZSBlbm91Z2guDQoNCgkg
DQoNCgkgDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCglGcm9tOiBIYWxs
YW0tQmFrZXIsIFBoaWxsaXANCglTZW50OiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAzOjM3IEFNDQoJ
U3ViamVjdDogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsgbWVtYmVy
IHNpbmNlDQoNCgkgDQoNCgnigKYNCg0KCTMpIE5vIFBhZGxvY2sgSWNvbiBhdHRyaWJ1dGUNCg0K
CSANCg0KCSAgICBUaGlzIGF0dHJpYnV0ZSB3b3VsZCBhbGxvdyBhIGNlcnRpZmljYXRlIHRvIHNh
eSB0aGF0IG5vIHVzZXIgaW5kaWNhdGlvbiBzaG91bGQgYmUgc3BlY2lmaWVkIGluIHRoZSBjaHJv
bWUsIG5vciBzaG91bGQgYW55IG5hZyBzY3JlZW5zLiBJdCB3b3VsZCBiZSBhbiBvcHRpb24gdGhh
dCB0aGUgaXNzdWluZyBDQSB3b3VsZCBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi4NCg0KCSAN
Cg0KCSAgICBUaGUgbmVlZCBmb3IgdGhpcyBpcyB0byBhbGxvdyBhIENBIHRvIHN1cHBvcnQgYSB3
aWRlIHJhbmdlIG9mIGFwcGxpY2F0aW9ucyB3aGljaCByZXF1aXJlIGVuY3J5cHRpb24gYnV0IHJl
cXVpcmUgZXZlbiBsZXNzIGF1dGhlbnRpY2F0aW9uIHRoYW4gY3VycmVudCBzY2hlbWVzIHN1Y2gg
YXMgZG9tYWluIHZhbGlkYXRlZCBjZXJ0cy4gRm9yIGV4YW1wbGUgc2VsZiBzaWduZWQgY2VydGlm
aWNhdGVzLCBjZXJ0aWZpY2F0ZXMgaXNzdWVkIHRvIGVtYmVkZGVkIGhhcmR3YXJlLCBldGMuIGV0
Yy4NCg0KCSANCg0KCSAgICBXaGF0IEkgd2FudCB0byBkbyBpcyB0byBnZXQgdXMgdG8gdGhlIHBv
aW50IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbCBjb21mb3J0YWJsZSB3aXRoIGEgdXNl
ciBleHBlcmllbmNlIHRoYXQgZG9lcyBub3QgY29udGFpbiB0aGUgbmFnIHNjcmVlbnMgdGhhdCBk
aXNmaWd1cmUgY3VycmVudCBzY2hlbWVzLiBJbiBtYW55IGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVp
cmVkIGlzIHRvIHR1cm4gb24gZW5jcnlwdGlvbi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byBi
ZSB0b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBleHBpcmVkLCBoYXMgYmVlbiBpc3N1ZWQg
YnkgYW4gdW5rbm93biBDQSBvciBhbnkgb2YgdGhlIHVzdWFsIG5vbnNlbnNlLiBqdXN0IGRvbid0
IHRlbGwgdGhlIHVzZXIgdGhhdCBpdHMgc2FmZSBpbiB0aGUgZmlyc3QgcGxhY2UgYW5kIHRoZSBi
cm93c2VyIGRvZXMgbm90IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgZGFuZ2Vyb3VzLg0KDQoJIA0K
DQoJICAgIENsZWFybHkgdGhpcyBhdHRyaWJ1dGUgaXMgdW5uZWNlc3NhcnkgZnJvbSBhIHRlY2hu
aWNhbCBwb2ludCBvZiB2aWV3LiBGcm9tIGEgbWFya2V0IHBvaW50IG9mIHZpZXcgaXQgaXMgZXNz
ZW50aWFsIGlmIHdlIGFyZSBnb2luZyB0byBlbnN1cmUgdGhhdCBhcHBsaWNhdGlvbnMgYXJlIGRv
aW5nIHRoZSByaWdodCB0aGluZy4gVGhlIHBhZGxvY2sgaWNvbiBoYXMgc29tZSBwcmV0dHkgc3Ry
b25nIHNlbWFudGljcy4gTWFueSBhcHBsaWNhdGlvbnMgcmVxdWlyZSBsZXNzLiBXZSBhcmUgbm90
IGdvaW5nIHRvIGdldCBldmVyeW9uZSB3aG8gY3VycmVudGx5IGhhcyBhIHBhZGxvY2sgY2VydGlm
aWNhdGUgdG8gZ2V0IGEgZ3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2VydmUgdGhlIGFwcGxpY2F0
aW9ucyB0aGF0IHJlcXVpcmUgZXZlbiBsZXNzIHRoYW4gdGhlIHBhZGxvY2sgd2l0aG91dCBkaWx1
dGluZyB0aGUgcGFkbG9jayBzZW1hbnRpY3MgZnVydGhlci4NCg0KCQ0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCg0KDQoJRnJvbTogb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9y
ZyBbbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddIE9uIEJlaGFsZiBPZiBIYWxs
YW0tQmFrZXIsIFBoaWxsaXANCglTZW50OiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzowNiBBTQ0K
CVRvOiBLZW1wLCBEYXZpZCBQLjsgcGtpeA0KDQoJIA0KDQoJMykgTm8gUGFkbG9jayBJY29uIGF0
dHJpYnV0ZQ0KDQoJIA0KDQoJVGhlIHBvaW50IGhlcmUgaXMgcHJlY2lzZWx5IHRvIGFsbG93IGEg
Y2VydGlmaWNhdGUgdG8gc3RhdGUgJ3RoZXJlIGFyZSBubyBzZWN1cml0eSBjbGFpbXMgYmVpbmcg
bWFkZSBoZXJlJy4gDQoNCgkgDQoNCglUaGUgdXNlciBkb2VzIG5vdCBhY2NlcHQgdGhlIGNlcnRp
ZmljYXRlLCB0aGUgY2xpZW50IGFwcGxpY2F0aW9uIGRvZXMuIE5vIHVzZXIgaGFzIGV2ZXIgY2hl
Y2tlZCBhIGNlcnRpZmljYXRlIHBhdGggYW5kIG5vIHVzZXIgZXZlciB3aWxsLiBUaGUgcXVlc3Rp
b24gaXMgd2hldGhlciB0aGUgY2xpZW50IGFwcGxpY2F0aW9uIHNob3VsZCBiZSB0ZWxsaW5nIHRo
ZSB1c2VyIHRoYXQgaXQgaXMgJ3NhZmUnIG9yIG5vdC4NCg0KCSANCg0KCUkgZG9uJ3Qgc2VlIHdo
eSB3ZSBuZWVkIHRvIHRlbGwgdGhlIHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVzZWQg
dW5sZXNzIHRoZXkgaGF2ZSBleHBsaWNpdGx5IHNhaWQgdGhhdCB0aGV5IG5lZWQgY29uZmlkZW50
aWFsaXR5LiBUZWxsaW5nIHRoZSB1c2VyIHRoYXQgdGhlcmUgaXMgZW5jcnlwdGlvbiBtZWFucyBh
bHNvIHRlbGxpbmcgdGhlbSBhYm91dCBhIHdob2xlIHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhl
ciBlcnJvciBjb25kaXRpb25zLiANCg0KCV9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KCUZyb206IG93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcgW21haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8bWFpbHRvOiU1Ym1haWx0bzpvd25lci1p
ZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkPiAgT24gQmVoYWxmIE9mIEhhbGxhbS1CYWtlciwgUGhp
bGxpcA0KCVNlbnQ6IFR1ZXNkYXksIDEyIEp1bmUgMjAwNyAxMjoyNCBBTQ0KDQoJIA0KDQoJ4oCm
DQoNCglJIGNhbiBnaXZlIHlvdSBhIGNhc3QgaXJvbiBjaGFpbiBmb3IgYW4gRVVJNDggTUFDIGFk
ZHJlc3MuIEJ1dCBpdCBzYXlzIG5vdGhpbmcgdGhhdCBzaG91bGQgZ2l2ZSBhbiBlbmQgdXNlciB3
YXJtIGZ1enppZXMuDQoNCgkgDQoNCgkgDQoNCgknVGhpcyBjZXJ0IG1ha2VzIG5vIHNlY3VyaXR5
IGNsYWltcyB0aGF0IGFyZSB3b3J0aCBkaXNwbGF5IHRvIGFuIGVuZCB1c2VyJy4NCg0KCeKApg0K
DQoJX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJRnJvbTog
b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyBbbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWls
LmltYy5vcmddIDxtYWlsdG86JTVibWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcl
NWQ+ICBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQaGlsbGlwDQoJU2VudDogVHVlc2RheSwg
MTIgSnVuZSAyMDA3IDM6NDUgQU0NCg0KCSANCg0KCeKAplRoZSBpbmZvcm1hdGlvbiB0byBiZSBl
bmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0aGUgaXNzdWUgcHJhY3RpY2VzIG9mIHRoZSBjZXJ0aWZp
Y2F0ZS4gVGhlcmVmb3JlIHRoZXkgZ28gaW50byB0aGUgY2VydGlmaWNhdGUuDQoNCgkgDQoNCglU
aGVzZSBhcmUgbm90IGFub255bW91cyBjb21tdW5pY2F0aW9ucywgdGhleSBhcmUgbWVyZWx5IGNv
bW11bmljYXRpb25zIHRoYXQgZG8gbm90IHJlcXVpcmUgdGhlIGxldmVsIG9mIGFzc3VyYW5jZSB0
aGF0IGlzIG5lY2Vzc2FyeSB0byBhbGVydCB0aGUgdXNlciB0byB0ZWxsIHRoYW0gdGhhdCB0aGUg
Y29tbXVuaWNhdGlvbiBpcyBzZWN1cmUuDQoNCglfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCglGcm9tOiBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFtt
YWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gPG1haWx0bzolNWJtYWlsdG86b3du
ZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyU1ZD4gIE9uIEJlaGFsZiBPZiBIYWxsYW0tQmFrZXIs
IFBoaWxsaXANCglTZW50OiBUdWVzZGF5LCAxMiBKdW5lIDIwMDcgMTA6MDAgQU0NCg0KCSANCg0K
CUNhc2UgaW4gcG9pbnQgaGVyZSBiZWluZyB5b3VyIFMvTUlNRSBjZXJ0IHdoaWNoIGRvZXMgbm90
IHNhdGlzZnkgbXkgT3V0bG9vayBjaGFpbmluZyBzbyBnaXZlIGEgd2FybmluZy4NCg0KCSANCg0K
CVlldCBJIGNhbiBnZXQgbWFpbCBmcm9tIHBsZW50eSBvZiBwbGFjZXMgd2l0aG91dCBhbnkgc2Vj
dXJpdHkgYW5kIHdpdGhvdXQgYSB3YXJuaW5nIGVpdGhlci4NCg0KCSANCg0KCVdvdWxkbid0IGl0
IGJlIG5pY2UgaWYgYSBjZXJ0IGNvdWxkIHNheSAndGhlIGNvcnJlY3QgY291cnNlIG9mIGFjdGlv
biBpZiB5b3UgZG9uJ3QgbGlrZSBtZSBpcyB0byBzaW1wbHkgc2hvdyB0aGUgZW1haWwgd2l0aG91
dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyBzZWN1cmUnLg0KDQoJIA0KDQoJV2h5IGRv
IGZvbGsgZmVlbCB0aGF0IHRoZSB1c2VyIGhhcyB0byBiZSB0b2xkIGFib3V0IG1lcmVseSBzdWIt
c3RhbmRhcmQgc2VjdXJpdHkgd2hlbiA5OSUgb2YgdGhlIEludGVybmV0IGhhcyBubyBzZWN1cml0
eSBhdCBhbGw/DQoNCg==

------_=_NextPart_001_01C7B350.07C19428
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4
bWxuczp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1
cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIj48SEVBRD4NCjxNRVRBIGh0dHAtZXF1
aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8TUVU
QSBjb250ZW50PSJNU0hUTUwgNi4wMC41NzMwLjExIiBuYW1lPUdFTkVSQVRPUj48IS0tW2lmICFt
c29dPg0KPFNUWUxFPnZcOiogew0KCUJFSEFWSU9SOiB1cmwoI2RlZmF1bHQjVk1MKQ0KfQ0Kb1w6
KiB7DQoJQkVIQVZJT1I6IHVybCgjZGVmYXVsdCNWTUwpDQp9DQp3XDoqIHsNCglCRUhBVklPUjog
dXJsKCNkZWZhdWx0I1ZNTCkNCn0NCi5zaGFwZSB7DQoJQkVIQVZJT1I6IHVybCgjZGVmYXVsdCNW
TUwpDQp9DQo8L1NUWUxFPg0KPCFbZW5kaWZdLS0+DQo8U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9u
dC1mYW1pbHk6IEFyaWFsIFVuaWNvZGUgTVM7DQp9DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWls
eTogVGFob21hOw0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IEBBcmlhbCBVbmljb2Rl
IE1TOw0KfQ0KQHBhZ2UgU2VjdGlvbjEge3NpemU6IDU5NS4zcHQgODQxLjlwdDsgbWFyZ2luOiA3
Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7IH0NClAuTXNvTm9ybWFsIHsNCglGT05ULVNJWkU6
IDEycHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFu
Ig0KfQ0KTEkuTXNvTm9ybWFsIHsNCglGT05ULVNJWkU6IDEycHQ7IE1BUkdJTjogMGNtIDBjbSAw
cHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIg0KfQ0KRElWLk1zb05vcm1hbCB7DQoJ
Rk9OVC1TSVpFOiAxMnB0OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVz
IE5ldyBSb21hbiINCn0NCkE6bGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjog
dW5kZXJsaW5lDQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVD
T1JBVElPTjogdW5kZXJsaW5lDQp9DQpBOnZpc2l0ZWQgew0KCUNPTE9SOiBibHVlOyBURVhULURF
Q09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BBTi5Nc29IeXBlcmxpbmtGb2xsb3dlZCB7DQoJQ09M
T1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLkVtYWlsU3R5bGUx
OCB7DQoJRk9OVC1XRUlHSFQ6IG5vcm1hbDsgQ09MT1I6IGJsdWU7IEZPTlQtU1RZTEU6IG5vcm1h
bDsgRk9OVC1GQU1JTFk6ICJBcmlhbCBVbmljb2RlIE1TIjsgVEVYVC1ERUNPUkFUSU9OOiBub25l
OyBtc28tc3R5bGUtdHlwZTogcGVyc29uYWwtcmVwbHkNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFn
ZTogU2VjdGlvbjENCn0NCjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9EWSBsYW5nPUVOLUFVIHZMaW5r
PWJsdWUgbGluaz1ibHVlPg0KPERJViBkaXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkz
MzcyMTE1LTIwMDYyMDA3PjxGT05UIGZhY2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj5U
aGUgaXNzdWUgaGVyZSBpcyBiYWNrd2FyZHMgDQpjb21wYXRpYmlsaXR5LjwvRk9OVD48L1NQQU4+
PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAw
NjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQ
QU4+Jm5ic3A7PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMz
NzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPkFu
eSBjZXJ0aWZpY2F0ZSBpc3N1ZWQgdG9kYXkgbXVzdCB3b3JrIGFjY2FwdGFibHkgd2l0aCANCmV4
aXN0aW5nIGJyb3dzZXJzLiBUaGF0IG1lYW5zIGNoYWluaW5nIHVwIHRvIGFuIGVtYmVkZGVkIHJv
b3QuIFVuZGVyIHRoZSBydWxlcyANCmFzIHRoZXkgYXJlIHRvZGF5IGEgY2VydCBpc3N1ZXIgY2Fu
Jm5ic3A7aXNzdWUgYSBjZXJ0aWZpY2F0ZSB3aXRoIGVzc2VudGlhbGx5IG5vIA0KbWVhbmluZ2Z1
bCBhdXRoZW50aWNhdGlvbiBhbmQgbWFueSBkby48L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJViBk
aXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkzMzcyMTE1LTIwMDYyMDA3PjxGT05UIGZh
Y2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj48L0ZPTlQ+PC9TUEFOPiZuYnNwOzwvRElW
Pg0KPERJViBkaXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkzMzcyMTE1LTIwMDYyMDA3
PjxGT05UIGZhY2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj5UaGUgcG9pbnQgaXMgdG8g
YWxsb3cgYW4gaXNzdWVyIHRvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiANCmNlcnRpZmljYXRlcyB0
aGF0IGFyZSBkZXNpZ25lZCB0byBwcm92aWRlIGEgbWVhbmluZ2Z1bCBkZWdyZWUgb2YgYWNjb3Vu
dGFiaWxpdHkgDQpmcm9tIHRob3NlIHdoaWNoIGFyZSBzaW1wbHkgZGVzaWduZWQgdG8gdHVybiBv
biBTU0wgaW4gdGhlIGRlcGxveWVkIGJhc2Ugb2YgYSANCmJpbGxpb24gYnJvd3NlcnMuIE92ZXIg
dGltZSB0aGUgZGVwbG95bWVudCBvZiBicm93c2VycyB0aGF0IG9ic2VydmUgdGhlIE9JRCANCndv
dWxkIGluY3JlYXNlLjwvRk9OVD48L1NQQU4+PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVm
dD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9y
PSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWIGRpcj1sdHIg
YWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1Bcmlh
bCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElW
IGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQg
ZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPklmIHdlIHdlcmUgZGVzaWduaW5nIGZy
b20gc2NyYXRjaCB0aGUgc2Vuc2libGUgd2F5IHRvIGRvIA0KdGhpcyB3b3VsZCBiZSB0byBoYXZl
IGFuIE9JRCB3aXRoIHBvc2l0aXZlIHNlbWFudGljcyAnYXNzZXJ0IHNlY3VyaXR5IHRvIHRoZSAN
CnVzZXInLiBTaW5jZSB3ZSBkb24ndCBoYXZlIHRoYXQgbHV4dXJ5IGFuZCBzaW5jZSB3ZSBoYXZl
IHRvIGRlYWwgd2l0aCB0aGUgDQpiaWxsaW9uIGRlcGxveWVkIGJyb3dzZXJzIHdlIG5lZWQgYSBk
aWZmZXJlbnQgYXBwcm9hY2guPC9GT05UPjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGln
bj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0K
Y29sb3I9IzAwMDBmZiBzaXplPTI+PC9GT05UPjwvU1BBTj4mbmJzcDs8L0RJVj4NCjxESVYgZGly
PWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNl
PUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXplPTI+SSBkbyBub3QgYWdyZWUgd2l0aCB0aGUgc2Vu
dGltZW50IHRoYXQgYSBzdGFuZGFyZHMgcHJvY2VzcyANCnNob3VsZCBvbmx5IGRlYWwgd2l0aCBw
ZXJmZWN0IHNpdHVhdGlvbnMgYW5kIHN0aWNrIGl0cyBoZWFkIGluIHRoZSBzYW5kIHdoZW4gaXQg
DQpjb21lcyB0byB0b3VnaCBkZXBsb3ltZW50IGlzc3Vlcy4gTWFuYWdpbmcgdGhlIGNvbnN0cmFp
bnRzIG9mIHRoZSBkZXBsb3llZCBiYXNlIA0Kc2hvdWxkIGJlIHRoZSBmaXJzdCBjb25jZXJuIGZv
ciBhIFdHIHRoYXQgaGFzIGJlZW4gaW4gZXhpc3RlbmNlIGZvciB0ZW4geWVhcnMuIA0KPC9GT05U
PjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3
MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXplPTI+PC9G
T05UPjwvU1BBTj4mbmJzcDs8L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNs
YXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBz
aXplPTI+QXQgbGVhc3QgUEtJWCBoYXMgYSBkZXBsb3llZCBiYXNlIHRvIHdvcnJ5IA0KYWJvdXQu
PC9GT05UPjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNz
PTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXpl
PTI+PC9GT05UPjwvU1BBTj4mbmJzcDs8L0RJVj48QlI+DQo8QkxPQ0tRVU9URSBkaXI9bHRyIA0K
c3R5bGU9IlBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDog
IzAwMDBmZiAycHggc29saWQ7IE1BUkdJTi1SSUdIVDogMHB4Ij4NCiAgPERJViBjbGFzcz1PdXRs
b29rTWVzc2FnZUhlYWRlciBsYW5nPWVuLXVzIGRpcj1sdHIgYWxpZ249bGVmdD4NCiAgPEhSIHRh
YkluZGV4PS0xPg0KICA8Rk9OVCBmYWNlPVRhaG9tYSBzaXplPTI+PEI+RnJvbTo8L0I+IG93bmVy
LWlldGYtcGtpeEBtYWlsLmltYy5vcmcgDQogIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwu
aW1jLm9yZ10gPEI+T24gQmVoYWxmIE9mIDwvQj5NYW5nZXIsIEphbWVzIA0KICBIPEJSPjxCPlNl
bnQ6PC9CPiBTdW5kYXksIEp1bmUgMTcsIDIwMDcgOTozOSBQTTxCUj48Qj5Ubzo8L0I+IA0KICBw
a2l4PEJSPjxCPlN1YmplY3Q6PC9CPiBSRTogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7
IHRleHQgbG9nbzsgbWVtYmVyIA0KICBzaW5jZTxCUj48L0ZPTlQ+PEJSPjwvRElWPg0KICA8RElW
PjwvRElWPg0KICA8RElWIGNsYXNzPVNlY3Rpb24xPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQ
QU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTog
J0FyaWFsIFVuaWNvZGUgTVMnIj5JIGxpa2UgDQogIHRoZSBpZGVhIG9mIHJldmVydGluZyB0byBh
biDigJx1bnNlY3VyZWTigJ0gbG9vay1uLWZlZWwgYW5kIGF2b2lkaW5nIG5hZyBzY3JlZW5zIA0K
ICB3aGVuIHRoZSBzZWN1cml0eSwgdGhvdWdoIHByZXNlbnQsIGlzIG5vdCDigJxwZXJmZWN04oCd
LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBV
bmljb2RlIE1TJyI+SXQgaXMgDQogIGJhZCB0aGF0IG1hbnkgY2xpZW50cyB0cmVhdCB1bmNvbmZp
cm1lZCBzZWN1cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEgDQogIGxvY2FsbHktdHJ1c3Rl
ZCByb290KSBhcyB3b3JzZSB0aGFuIG5vIHNlY3VyaXR5LiBUaGlzIGRpc2NvdXJhZ2VzIGF0dGVt
cHRzIHRvIA0KICBpbXByb3ZlIHNlY3VyaXR5LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAg
Y2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjog
Ymx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+SSBhbSANCiAgbGVzcyBzdXJl
IHRoYXQgYSDigJxubyBwYWRsb2Nr4oCdIGF0dHJpYnV0ZSBpcyB0aGUgcmlnaHQgd2F5IHRvIGFj
aGlldmUgDQogIHRoaXMuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3Jt
YWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZB
TUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQog
IDxQIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOLUxFRlQ6IDM2cHQiPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogIzk5MzMwMDsgRk9OVC1GQU1JTFk6ICdBcmlh
bCBVbmljb2RlIE1TJyI+Jmd0O1dvdWxkbid0IA0KICBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3Vs
ZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgDQog
IG1lIGlzIHRvIHNpbXBseSBzaG93IHRoZSBlbWFpbCB3aXRob3V0IGFueSBpbmRpY2F0aW9uIHRo
ZSBtZXNzYWdlIGlzIA0KICBzZWN1cmUnLjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+PG86cD4mbmJzcDs8L286cD48L1NQ
QU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj5Xb3Vs
ZG7igJl0IA0KICBpdCBiZSBiZXR0ZXIgdG8gZml4IGVtYWlsIGNsaWVudHMgc28gdGhleSBhbHdh
eXMgYWN0IHRoaXMgd2F5LCBpbnN0ZWFkIG9mIG9ubHkgDQogIHRyaWdnZXJpbmcgdGhpcyBiZWhh
dmlvdXIgZm9yIGNlcnRhaW4gY2VydGlmaWNhdGVzPyBVbmxlc3MgaXQgaXMgYSB0YWN0aWNhbCAN
CiAgZGVjaXNpb24gdGhhdCBzb2Z0d2FyZSB2ZW5kb3JzIGFyZSBtb3JlIGxpa2VseSB0byBpbXBs
ZW1lbnQgYSBuZXcgY2VydGlmaWNhdGUgDQogIGZlYXR1cmUgdGhhbiBjaGFuZ2UgZXhpc3Rpbmcg
YmVoYXZpb3VyIChlc3BlY2lhbGx5IGlmIHRoZSBsYXR0ZXIgbWlnaHQgYmUgDQogIGJyYW5kZWQg
YXMgd29yc2VuaW5nIHNlY3VyaXR5KS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNz
PU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7
IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFO
PjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAx
MHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+Rm9yIA0K
ICBIVFRQUyBjb25uZWN0aW9ucywgYSBjZXJ0aWZpY2F0ZSB3aXRob3V0IGEgc3ViamVjdEFsdE5h
bWUuZE5TTmFtZSBmaWVsZCAoYW5kIA0KICBubyBkb21haW4gbmFtZSBpbiBhIGNvbW1vbiBuYW1l
IGNvbXBvbmVudCBvZiB0aGUgc3ViamVjdCBmaWVsZCkgc2hvdWxkIGJlIA0KICBzdWZmaWNpZW50
IGZvciBhIGJyb3dzZXIgdG8gc2F5IOKAnHdlbGwgSSBjYW5ub3QgZG8gdGhlIFVSTC10by1jZXJ0
IGNoZWNrIHNvIEkgDQogIHdpbGwgZGlzcGxheSB0aGUgcGFnZSBqdXN0IGxpa2UgYW4gSFRUUCBw
YWdl4oCdOiBubyBjb2xvdXJlZCBhZGRyZXNzIGJhciwgbm8gDQogIGxvY2tlZCBwYWRsb2NrLCBu
byBuYWcgc2NyZWVucywgc3RpbGwgdXNpbmcgVExTIG9uLXRoZS13aXJlIHRob3VnaC4gTm8gcGF0
aCB0byANCiAgYSB0cnVzdGVkIHJvb3QgKGVnIGEgc2VsZi1zaWduZWQgY2VydCkgc2hvdWxkIGJl
IHRyZWF0ZWQgdGhlIHNhbWUgd2F5LiANCiAgVW5hdmFpbGFibGUgQ1JMcyBjb3VsZCBiZSB0cmVh
dGVkIHRoZSBzYW1lIHdheS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05v
cm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQt
RkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4N
CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBD
T0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+T3RoZXIgDQogIGVy
cm9ycyBzdWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUs
IG9yIGEgbWlzbWF0Y2ggDQogIGJldHdlZW4gVVJMICZhbXA7IGNlcnQgbmFtZSBpbXBseSB0aGUg
Y2VydGlmaWNhdGUgaG9sZGVyIGhhcyBkb25lIHNvbWV0aGluZyANCiAgd3JvbmcuIEkgZG9u4oCZ
dCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChvciBvdXRyaWdodCByZWZ1c2FsIHRv
IA0KICBjb25uZWN0KSBpbiB0aGVzZSBjYXNlcy48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQ
IGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6
IGJsdWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+
PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1T
SVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+
UFJPQkxFTTxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl
PSJNQVJHSU4tTEVGVDogMzZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENP
TE9SOiAjOTkzMzAwOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj4mZ3Q7IA0KICBJ
IGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlwdGlvbiBp
cyBiZWluZyB1c2VkIHVubGVzcyANCiAgdGhleSBoYXZlIGV4cGxpY2l0bHkgc2FpZCB0aGF0IHRo
ZXkgbmVlZCANCmNvbmZpZGVudGlhbGl0eS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNs
YXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJs
dWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9T
UEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpF
OiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+VGhl
IA0KICBwcm9ibGVtIGlzIHRoYXQgdGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg
4oCcc2FmZeKAnSBjb25uZWN0aW9uLCANCiAgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBv
ciBhZGRyZXNzIGJhciBjb2xvdXIuIElmIGEgdXNlciBkaWRu4oCZdCBrbm93IGlmIA0KICB0aGUg
VVJMIHdhcyBIVFRQIG9yIEhUVFBTIChlZyB0aGVpciBicm93c2VyIGF1dG9tYXRpY2FsbHkgd2Vu
dCB0aGVyZSBhZnRlciBhbiANCiAgSFRUUCAzMDcgcmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCc
dW5jb25maXJtZWQgc2VjdXJpdHnigJ0gYXMg4oCcdW5zZWN1cmVk4oCdIHdvdWxkIA0KICBiZSBy
ZWFzb25hYmxlLiBPbiB0aGUgb3RoZXIgaGFuZCwgaWYgSSBjaG9vc2UgbXkgSFRUUFMgYm9va21h
cmsgZm9yIG15IGJhbmsgDQogIHRoZW4gSSBleHBlY3QgbXkgYnJvd3NlciA8ST5ub3Q8L0k+IHRv
IHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMpIA0KICBodG1sL2phdmFzY3JpcHQv
YWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNvdXJjZS4gSWYgbXkgYnJvd3NlciAocGVyaGFw
cyBkdWUgDQogIHRvIGEgRE5TIGF0dGFjaykgc2lsZW50bHkgYWNjZXB0ZWQgY29udGVudCBub3Qg
ZnJvbSBteSBiYW5rIEkgd291bGQgYmUgd29yc2UgDQogIG9mZi48bzpwPjwvbzpwPjwvU1BBTj48
L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBw
dDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5i
c3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHls
ZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmlj
b2RlIE1TJyI+QW55IA0KICB2aXNpYmlsaXR5IG9mIGFuIEhUVFBTIFVSTCB0byB0aGUgdXNlciBj
b3VsZCBiZSBjb25zaWRlcmVkIGFzIHRoZW0gZXhwbGljaXRseSANCiAgc2F5aW5nIHRoZXkgbmVl
ZCBjb25maWRlbnRpYWxpdHk6IGNob29zaW5nIGFuIEhUVFBTIGJvb2ttYXJrOyB0eXBpbmcgSFRU
UFMgDQogIGludG8gdGhlIGFkZHJlc3MgYmFyOyBjbGlja2luZyBvbiBhbiBIVFRQUyBsaW5rIHdo
ZW4gdGhlIFVSTCB3YXMgc2hvd24gaW4gdGhlIA0KICBzdGF0dXMgYmFyIGJlZm9yZSB0aGUgY2xp
Y2s7IGV2ZW4gc2VlaW5nIEhUVFBTIGluIHRoZSBhZGRyZXNzIGJhciBhZnRlciANCiAgcmVjZWl2
aW5nIGEgcGFnZSBjYW4gYmUgZW5vdWdoLjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+PG86cD4mbmJzcDs8L286cD48L1NQ
QU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj48bzpw
PiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxESVY+DQogIDxESVYgY2xhc3M9TXNvTm9ybWFs
IHN0eWxlPSJURVhULUFMSUdOOiBjZW50ZXIiIGFsaWduPWNlbnRlcj4NCiAgPEhSIHRhYkluZGV4
PS0xIGFsaWduPWNlbnRlciB3aWR0aD0iMTAwJSIgU0laRT0yPg0KICA8L0RJVj4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxCPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZB
TUlMWTogVGFob21hIj5Gcm9tOjwvU1BBTj48L0I+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IEZPTlQtRkFNSUxZOiBUYWhvbWEiPiBIYWxsYW0tQmFrZXIsIA0KICBQaGlsbGlwPEJS
PjxCPlNlbnQ6PC9CPiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAzOjM3IEFNPEJSPjxCPlN1YmplY3Q6
PC9CPiBUaHJlZSANCiAgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsgbWVtYmVy
IHNpbmNlPC9TUEFOPjxvOnA+PC9vOnA+PC9QPjwvRElWPg0KICA8RElWPg0KICA8UCBjbGFzcz1N
c29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+Jm5ic3A7PG86cD48L286cD48L1NQQU4+PC9QPjwvRElWPg0KICA8RElWPg0KICA8UCBj
bGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBi
bHVlOyBGT05ULUZBTUlMWTogQXJpYWwiPuKApjwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJVj4N
CiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTVFJPTkc+PFNQQU4gDQogIHN0eWxlPSJG
T05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbCI+MykgTm8gUGFkbG9jayBJY29uIA0K
ICBhdHRyaWJ1dGU8L1NQQU4+PC9TVFJPTkc+PG86cD48L286cD48L1A+PC9ESVY+DQogIDxESVY+
DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJ
Vj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8U1BBTiANCiAgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5UaGlzIGF0dHJpYnV0ZSB3
b3VsZCBhbGxvdyBhIA0KICBjZXJ0aWZpY2F0ZSB0byBzYXkgdGhhdCBubyB1c2VyIGluZGljYXRp
b24gc2hvdWxkIGJlIHNwZWNpZmllZCBpbiB0aGUgY2hyb21lLCANCiAgbm9yIHNob3VsZCBhbnkg
bmFnIHNjcmVlbnMuIEl0IHdvdWxkIGJlIGFuIG9wdGlvbiB0aGF0IHRoZSBpc3N1aW5nIENBIHdv
dWxkIA0KICBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi48L1NQQU4+PG86cD48L286cD48L1A+
PC9ESVY+DQogIDxESVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwv
UD48L0RJVj4NCiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNw
OyA8U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5U
aGUgbmVlZCBmb3IgdGhpcyBpcyB0byBhbGxvdyBhIENBIA0KICB0byBzdXBwb3J0IGEgd2lkZSBy
YW5nZSBvZiBhcHBsaWNhdGlvbnMgd2hpY2gmbmJzcDtyZXF1aXJlIGVuY3J5cHRpb24gYnV0IA0K
ICByZXF1aXJlIGV2ZW4gbGVzcyBhdXRoZW50aWNhdGlvbiB0aGFuIGN1cnJlbnQgc2NoZW1lcyBz
dWNoIGFzIGRvbWFpbiB2YWxpZGF0ZWQgDQogIGNlcnRzLiBGb3IgZXhhbXBsZSBzZWxmIHNpZ25l
ZCBjZXJ0aWZpY2F0ZXMsIGNlcnRpZmljYXRlcyBpc3N1ZWQgdG8gZW1iZWRkZWQgDQogIGhhcmR3
YXJlLCBldGMuIGV0Yy48L1NQQU4+PG86cD48L286cD48L1A+PC9ESVY+DQogIDxESVY+DQogIDxQ
IGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJVj4NCiAg
PFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8U1BBTiANCiAgc3R5bGU9IkZP
TlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5XaGF0IEkgd2FudCB0byBkbyBpcyB0
byBnZXQgdXMgdG8gDQogIHRoZSBwb2ludCB3aGVyZSB0aGUgYnJvd3NlciBhdXRob3JzIGZlZWwg
Y29tZm9ydGFibGUgd2l0aCBhIHVzZXIgZXhwZXJpZW5jZSANCiAgdGhhdCBkb2VzIG5vdCBjb250
YWluIHRoZSBuYWcgc2NyZWVucyB0aGF0IGRpc2ZpZ3VyZSBjdXJyZW50IHNjaGVtZXMuIEluIG1h
bnkgDQogIGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVpcmVkIGlzIHRvIHR1cm4gb24gZW5jcnlwdGlv
bi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byANCiAgYmUgdG9sZCB0aGF0IHRoZSBjZXJ0aWZp
Y2F0ZSBoYXMgZXhwaXJlZCwgaGFzIGJlZW4gaXNzdWVkIGJ5IGFuIHVua25vd24gQ0Egb3IgDQog
IGFueSBvZiB0aGUgdXN1YWwgbm9uc2Vuc2UuIGp1c3QgZG9uJ3QgdGVsbCB0aGUgdXNlciB0aGF0
IGl0cyBzYWZlIGluIHRoZSBmaXJzdCANCiAgcGxhY2UgYW5kIHRoZSBicm93c2VyIGRvZXMgbm90
IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgDQogIGRhbmdlcm91cy48L1NQQU4+PG86cD48L286cD48
L1A+PC9ESVY+DQogIDxESVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpw
PjwvUD48L0RJVj4NCiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZu
YnNwOyA8U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFs
Ij5DbGVhcmx5IHRoaXMgYXR0cmlidXRlIGlzIA0KICB1bm5lY2Vzc2FyeSBmcm9tIGEgdGVjaG5p
Y2FsIHBvaW50IG9mIHZpZXcuIEZyb20gYSBtYXJrZXQgcG9pbnQgb2YgdmlldyBpdCBpcyANCiAg
ZXNzZW50aWFsIGlmIHdlIGFyZSBnb2luZyB0byBlbnN1cmUgdGhhdCBhcHBsaWNhdGlvbnMgYXJl
IGRvaW5nIHRoZSByaWdodCANCiAgdGhpbmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJl
dHR5IHN0cm9uZyBzZW1hbnRpY3MuIE1hbnkgYXBwbGljYXRpb25zIA0KICByZXF1aXJlIGxlc3Mu
IFdlIGFyZSBub3QgZ29pbmcgdG8gZ2V0IGV2ZXJ5b25lIHdobyBjdXJyZW50bHkgaGFzIGEgcGFk
bG9jayANCiAgY2VydGlmaWNhdGUgdG8gZ2V0IGEgZ3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2Vy
dmUgdGhlIGFwcGxpY2F0aW9ucyB0aGF0IA0KICByZXF1aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBw
YWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcgdGhlIHBhZGxvY2sgc2VtYW50aWNzIA0KICBmdXJ0aGVy
LjwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJViBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9IlRFWFQtQUxJR046IGNlbnRlciIgYWxpZ249Y2VudGVyPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogbmF2eTsgRk9OVC1GQU1JTFk6IEFyaWFsIj4NCiAgPEhSIHRh
YkluZGV4PS0xIGFsaWduPWNlbnRlciB3aWR0aD0iMTAwJSIgU0laRT0yPg0KICA8L1NQQU4+PC9E
SVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48Qj48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTog
MTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogVGFob21hIj5Gcm9tOjwvU1BBTj48L0I+
PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1J
TFk6IFRhaG9tYSI+IA0KICBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFttYWlsdG86b3du
ZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gPEI+T24gDQogIEJlaGFsZiBPZiA8L0I+SGFsbGFt
LUJha2VyLCBQaGlsbGlwPEJSPjxCPlNlbnQ6PC9CPiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzow
NiANCiAgQU08QlI+PEI+VG86PC9CPiBLZW1wLCBEYXZpZCBQLjsgcGtpeDwvU1BBTj48U1BBTiAN
CiAgc3R5bGU9IkNPTE9SOiBuYXZ5Ij48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNz
PU1zb05vcm1hbD48U1BBTiBzdHlsZT0iQ09MT1I6IGJsYWNrIj4mbmJzcDs8bzpwPjwvbzpwPjwv
U1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1RST05HPjxTUEFOIA0KICBzdHlsZT0i
Rk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+MykgTm8g
UGFkbG9jayBJY29uIA0KICBhdHRyaWJ1dGU8L1NQQU4+PC9TVFJPTkc+PFNQQU4gc3R5bGU9IkNP
TE9SOiBibGFjayI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+
PFNQQU4gc3R5bGU9IkNPTE9SOiBuYXZ5Ij48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQog
IDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09M
T1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlhbCI+VGhlJm5ic3A7cG9pbnQgaGVyZSANCiAgaXMg
cHJlY2lzZWx5IHRvIGFsbG93IGEgY2VydGlmaWNhdGUgdG8gc3RhdGUgJ3RoZXJlIGFyZSBubyBz
ZWN1cml0eSBjbGFpbXMgDQogIGJlaW5nIG1hZGUgaGVyZScuJm5ic3A7PC9TUEFOPjxTUEFOIHN0
eWxlPSJDT0xPUjogbmF2eSI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29O
b3JtYWw+PFNQQU4gc3R5bGU9IkNPTE9SOiBibGFjayI+Jm5ic3A7PC9TUEFOPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6IEFyaWFsIj48
bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlhbCI+VGhl
IHVzZXIgZG9lcyBub3QgDQogIGFjY2VwdCB0aGUgY2VydGlmaWNhdGUsIHRoZSBjbGllbnQgYXBw
bGljYXRpb24gZG9lcy4gTm8gdXNlciBoYXMgZXZlciBjaGVja2VkIA0KICBhIGNlcnRpZmljYXRl
IHBhdGggYW5kIG5vIHVzZXIgZXZlciB3aWxsLiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB0aGUg
Y2xpZW50IA0KICBhcHBsaWNhdGlvbiBzaG91bGQgYmUgdGVsbGluZyB0aGUgdXNlciB0aGF0IGl0
IGlzICdzYWZlJyBvciANCiAgbm90LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9
TXNvTm9ybWFsPjxTUEFOIHN0eWxlPSJDT0xPUjogYmxhY2siPiZuYnNwOzwvU1BBTj48U1BBTiAN
CiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlh
bCI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQog
IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogQXJpYWwi
PkkgZG9uJ3Qgc2VlIHdoeSB3ZSANCiAgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlw
dGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhhdmUgDQogIGV4cGxpY2l0bHkgc2FpZCB0
aGF0IHRoZXkgbmVlZCBjb25maWRlbnRpYWxpdHkuIFRlbGxpbmcgdGhlIHVzZXIgdGhhdCB0aGVy
ZSBpcyANCiAgZW5jcnlwdGlvbiBtZWFucyBhbHNvIHRlbGxpbmcgdGhlbSBhYm91dCBhIHdob2xl
IHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhlciANCiAgZXJyb3IgY29uZGl0aW9ucy4gPG86cD48
L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9Ik1BUkdJTi1CT1RU
T006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsg
Rk9OVC1GQU1JTFk6IFRhaG9tYSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPEJSPjxCPkZyb206PC9CPiANCiAgPEEgaHJlZj0ibWFpbHRvOm93bmVyLWlldGYt
cGtpeEBtYWlsLmltYy5vcmciPm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmc8L0E+IA0KICA8
QSANCiAgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3Jn
JTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddPC9BPiANCiAgPEI+T24g
QmVoYWxmIE9mIDwvQj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8QlI+PEI+U2VudDo8L0I+IFR1ZXNk
YXksIDEyIEp1bmUgDQogIDIwMDcgMTI6MjQgQU08L1NQQU4+PFNQQU4gc3R5bGU9IkNPTE9SOiBi
bGFjayI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4g
DQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFy
aWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48
U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZ
OiBBcmlhbCI+4oCmPC9TUEFOPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xP
UjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8
UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9S
OiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5JIGNhbiBnaXZlIHlvdSBhIA0KICBjYXN0IGly
b24gY2hhaW4gZm9yIGFuIEVVSTQ4IE1BQyBhZGRyZXNzLiBCdXQgaXQgc2F5cyBub3RoaW5nIHRo
YXQgc2hvdWxkIGdpdmUgDQogIGFuIGVuZCB1c2VyIHdhcm0gZnV6emllcy48bzpwPjwvbzpwPjwv
U1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0la
RTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD4mbmJz
cDs8L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxl
PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj4nVGhp
cyBjZXJ0IG1ha2VzIG5vIA0KICBzZWN1cml0eSBjbGFpbXMgdGhhdCBhcmUgd29ydGggZGlzcGxh
eSB0byBhbiBlbmQgdXNlcicuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29O
b3JtYWwgc3R5bGU9Ik1BUkdJTi1CT1RUT006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJ
WkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+4oCmPC9TUEFOPjxT
UEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6
IFRhaG9tYSI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9Ik1BUkdJTi1CT1RUT006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7
IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPEJSPjxCPkZyb206PC9CPiANCiAgPEEgaHJlZj0ibWFp
bHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmciPm93bmVyLWlldGYtcGtpeEBtYWlsLmlt
Yy5vcmc8L0E+IA0KICA8QSANCiAgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBr
aXhAbWFpbC5pbWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmdd
PC9BPiANCiAgPEI+T24gQmVoYWxmIE9mIDwvQj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8QlI+PEI+
U2VudDo8L0I+IFR1ZXNkYXksIDEyIEp1bmUgDQogIDIwMDcgMzo0NSBBTTwvU1BBTj48U1BBTiBz
dHlsZT0iQ09MT1I6IGJsYWNrIj48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1z
b05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBG
T05ULUZBTUlMWTogQXJpYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6IEFyaWFsIj7igKY8L1NQQU4+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJ
WkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5UaGUgaW5mb3JtYXRp
b24gdG8gDQogIGJlIGVuY29kZWQgaGVyZSByZWxhdGVzIHRvIHRoZSBpc3N1ZSBwcmFjdGljZXMg
b2YgdGhlIGNlcnRpZmljYXRlLiBUaGVyZWZvcmUgDQogIHRoZXkgZ28gaW50byB0aGUgY2VydGlm
aWNhdGUuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4g
DQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFy
aWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48
U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlM
WTogQXJpYWwiPlRoZXNlIGFyZSBub3QgDQogIGFub255bW91cyBjb21tdW5pY2F0aW9ucywgdGhl
eSBhcmUgbWVyZWx5IGNvbW11bmljYXRpb25zIHRoYXQgZG8gbm90IHJlcXVpcmUgDQogIHRoZSBs
ZXZlbCBvZiBhc3N1cmFuY2UgdGhhdCBpcyBuZWNlc3NhcnkgdG8gYWxlcnQgdGhlIHVzZXIgdG8g
dGVsbCB0aGFtIHRoYXQgDQogIHRoZSBjb21tdW5pY2F0aW9uIGlzIHNlY3VyZS48bzpwPjwvbzpw
PjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOLUJPVFRPTTog
NnB0Ij48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05U
LUZBTUlMWTogVGFob21hIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX188QlI+PEI+RnJvbTo8L0I+IA0KICA8QSBocmVmPSJtYWlsdG86b3duZXItaWV0Zi1wa2l4
QG1haWwuaW1jLm9yZyI+b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZzwvQT4gDQogIDxBIA0K
ICBocmVmPSJtYWlsdG86JTVibWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmclNWQi
PlttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ108L0E+IA0KICA8Qj5PbiBCZWhh
bGYgT2YgPC9CPkhhbGxhbS1CYWtlciwgUGhpbGxpcDxCUj48Qj5TZW50OjwvQj4gVHVlc2RheSwg
MTIgSnVuZSANCiAgMjAwNyAxMDowMCBBTTwvU1BBTj48U1BBTiBzdHlsZT0iQ09MT1I6IGJsYWNr
Ij48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAg
c3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFO
IA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+Q2FzZSBpbiBwb2ludCBoZXJlIA0KICBiZWluZyB5b3VyIFMvTUlNRSBjZXJ0IHdoaWNo
IGRvZXMgbm90IHNhdGlzZnkgbXkgT3V0bG9vayBjaGFpbmluZyBzbyBnaXZlIGEgDQogIHdhcm5p
bmcuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQog
IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BB
TiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTog
QXJpYWwiPllldCBJIGNhbiBnZXQgbWFpbCANCiAgZnJvbSBwbGVudHkgb2YgcGxhY2VzIHdpdGhv
dXQgYW55IHNlY3VyaXR5IGFuZCB3aXRob3V0IGEgd2FybmluZyANCiAgZWl0aGVyLjxvOnA+PC9v
OnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD4mbmJz
cDs8L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxl
PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5Xb3Vs
ZG4ndCBpdCBiZSBuaWNlIA0KICBpZiBhIGNlcnQgY291bGQgc2F5ICd0aGUgY29ycmVjdCBjb3Vy
c2Ugb2YgYWN0aW9uIGlmIHlvdSBkb24ndCBsaWtlIG1lIGlzIHRvIA0KICBzaW1wbHkgc2hvdyB0
aGUgZW1haWwgd2l0aG91dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyANCiAgc2VjdXJl
Jy48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAg
c3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFO
IA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+V2h5IGRvIGZvbGsgZmVlbCANCiAgdGhhdCB0aGUgdXNlciBoYXMgdG8gYmUgdG9sZCBh
Ym91dCBtZXJlbHkgc3ViLXN0YW5kYXJkIHNlY3VyaXR5IHdoZW4gOTklIG9mIA0KICB0aGUgSW50
ZXJuZXQgaGFzIG5vIHNlY3VyaXR5IGF0IA0KYWxsPzwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJ
Vj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg==

------_=_NextPart_001_01C7B350.07C19428--




From owner-ietf-pkix@mail.imc.org Sat Jun 23 17:52:09 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2DWb-0004A5-Tj
	for pkix-archive@lists.ietf.org; Sat, 23 Jun 2007 17:52:09 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I2DWX-0001pH-Ex
	for pkix-archive@lists.ietf.org; Sat, 23 Jun 2007 17:52:09 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5NKkg4B055937
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 23 Jun 2007 13:46:42 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5NKkgOW055936;
	Sat, 23 Jun 2007 13:46:42 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.pingtel.com (hide.pingtel.com [65.220.123.2])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5NKkaf9055903
	for <ietf-pkix@imc.org>; Sat, 23 Jun 2007 13:46:40 -0700 (MST)
	(envelope-from slawrence@pingtel.com)
Received: from [127.0.0.1] (pi.pingtel.com [10.1.1.12])
	by mail.pingtel.com (Postfix) with ESMTP id AA8E76C025;
	Sat, 23 Jun 2007 16:45:55 -0400 (EDT)
Subject: Domain certificates in SIP
From: Scott Lawrence <slawrence@pingtel.com>
To: ietf-pkix@imc.org
Cc: Vijay Gurbani <vkg@lucent.com>
Content-Type: text/plain
Organization: Pingtel Corp.
Date: Sat, 23 Jun 2007 16:46:27 -0400
Message-Id: <1182631587.3432.26.camel@scott.skrb.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 
Content-Transfer-Encoding: 7bit
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


draft-gurbani-sip-domain-certs-05 has been submitted to
the IETF archives.  We've tried to incorporate some of the advice we got
around the Prague meeting.

This version focuses fairly narrowly on:

- How to use and interpret the SIP identities in a X.509 certificate.
- How to indicate that this particular certificate is for SIP
  usage.

What goes in the subjectAltName, and a new EKU value, with the detailed
steps to interpret and validate them are provided from the viewpoint of
user agents, proxies, and registrars.

Until the -05 version appears in the archives, you can get it from:

http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-gurbani-sip-domain-certs-05.txt
http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-gurbani-sip-domain-certs-05.html

Comments, questions and other feedback is much appreciated.

-- 
Scott Lawrence  tel:+1-781-938-5306;ext=162 or sip:slawrence@pingtel.com
  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
  Chief Technology Officer    - Pingtel Corp. http://www.pingtel.com/




From tqbneain@rrf.org Tue Jun 26 09:02:01 2007
Return-path: <tqbneain@rrf.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3AgD-0003s7-3E; Tue, 26 Jun 2007 09:02:01 -0400
Received: from [122.2.219.150] (helo=VALENCIA-12)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3AgC-0001Qm-IE; Tue, 26 Jun 2007 09:02:01 -0400
Message-ID: <82640365123197.F95643DA3E@N5TU>
From: "Stacey Cochran" <ccaerzkt@rrocha.com>
To: <nsis-request@megatron.ietf.org>
Subject: Sex can be one of the most enjoyable parts of your life.
Date: Tue, 26 Jun 2007 13:57:52 +0100
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 8v1oncNMoN7n2T9FmQ1c8UzasYVReHb0ePNp
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

<font size="3" face="Times New Roman"><p class="subtextcialis"><font face="Tahoma" color="#333300" size="5"><strong>What is CIALIS?</strong></font></p>
<p><font face="Tahoma" size="2">CIALIS is the only ED (Erectile Disfunction) tablet clinically proven to work both <br />up to 36 hours and in as fast as 30 minutes. </font><font face="Tahoma" size="2">And because CIALIS has an extended <br />period of effectiveness, you don’t have the pressure to perform within a few hours. <br />You and your partner can relax and take your time choosing the moment that is right for both of you.</font></p>
<p class="subtextcialis"><font size="2"><font face="Tahoma"><font color="#003300" size="5"><strong>Benefits of CIALIS</strong></font> </font></font></p>
<ul>
    <li><font face="Tahoma" size="2">Works up to 36 hours </font></li>
    <li><font face="Tahoma" size="2">Works fast </font></li>
    <li><font face="Tahoma" size="2">Works Effectively </font></li>
    <li><font face="Tahoma" size="2">Keeps you ready </font></li>
    <li><font face="Tahoma" size="2">No need to plan around meals </font></li>
    <li><font face="Tahoma" size="2">Used by millions of men </font></li>
</ul>
<p><font face="Tahoma" color="#003300" size="5"><strong><a href="http://lgjowf.aspenbearing.com/?67415077">Buy CIALIS online!</a></strong></font></p></font>




From vfszytailpf@rri.sari.ac.uk Wed Jun 27 19:47:01 2007
Return-path: <vfszytailpf@rri.sari.ac.uk>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3hDx-0007Sf-3z; Wed, 27 Jun 2007 19:47:01 -0400
Received: from icarus.thecsl.org ([66.92.77.160] helo=e8i4xaie.r6aire.optonline.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3hDw-0005yr-Sd; Wed, 27 Jun 2007 19:47:01 -0400
Message-ID: <85542148763181.6C985E2CE5@BVVPZE2>
From: "Nellie Hutchison" <kahlgokge@rrinsurance.ab.ca>
To: <pkix-archive@megatron.ietf.org>
Subject: It may strengthen your relationship with your partner.
Date: Wed, 27 Jun 2007 19:41:36 -0400
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: 99LcsQb1WfoESA6SLnOHcL1I9p9OrFU6bpJr
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

<font size="3" face="Times New Roman"><p class="subtextcialis"><font face="Tahoma" color="#333300" size="5"><strong>What is CIALIS?</strong></font></p>
<p><font face="Tahoma" size="2">CIALIS is the only ED (Erectile Disfunction) tablet clinically proven to work both <br />up to 36 hours and in as fast as 30 minutes. </font><font face="Tahoma" size="2">And because CIALIS has an extended <br />period of effectiveness, you don’t have the pressure to perform within a few hours. <br />You and your partner can relax and take your time choosing the moment that is right for both of you.</font></p>
<p class="subtextcialis"><font size="2"><font face="Tahoma"><font color="#003300" size="5"><strong>Benefits of CIALIS</strong></font> </font></font></p>
<ul>
    <li><font face="Tahoma" size="2">Works up to 36 hours </font></li>
    <li><font face="Tahoma" size="2">Works fast </font></li>
    <li><font face="Tahoma" size="2">Works Effectively </font></li>
    <li><font face="Tahoma" size="2">Keeps you ready </font></li>
    <li><font face="Tahoma" size="2">No need to plan around meals </font></li>
    <li><font face="Tahoma" size="2">Used by millions of men </font></li>
</ul>
<p><font face="Tahoma" color="#003300" size="5"><strong><a href="http://rqoibh.sadabatement.net/?23161451">Buy CIALIS online!</a></strong></font></p></font>




From necojp@citiz.net Thu Jun 28 08:04:15 2007
Return-path: <necojp@citiz.net>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3sjP-0006Dc-Di
	for PKIX-ARCHIVE@LISTS.IETF.ORG; Thu, 28 Jun 2007 08:04:15 -0400
Received: from [218.61.104.236] (helo=so-net.ne.jp)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3sjO-000057-G7
	for PKIX-ARCHIVE@LISTS.IETF.ORG; Thu, 28 Jun 2007 08:04:15 -0400
Received: from qht2 (unknown [201.125.247.248])
	by smtp97 (Coremail) with SMTP id q6KbrKDqRzLAsPVF.1
	for <pkix-archive@lists.ietf.org>; Sat, 28 Jun 2008 20:03:35 +0800 (CST)
X-Originating-IP: [201.125.247.248]
Subject: =?iso-2022-jp?B?GyRCJTslQyUvJTkkNyQrNj1MIyRKJDcbKEI=?=
From: =?shift-jis?B?bWF5YQ==?= <necojp@citiz.net>
To: <pkix-archive@lists.ietf.org>
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0008_01C7AF45.580252E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: 4.0 (++++)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027

This is a multi-part message in MIME format.

------=_NextPart_000_0008_01C7AF45.580252E0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit

$B0&$@$NNx$@$N$$$j$^$;$s!*(B
$B$H$K$+$/3d$j@Z$j%;%C%/%9$N$_$G2q$C$F2<$5$$!#(B
http://pure-love.biz/yu/?fs29
































$B%$%d!*!*!*(B
hosono145yuko@yahoo.co.uk 
------=_NextPart_000_0008_01C7AF45.580252E0
Content-Type: text/html;
	charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-2022-jp">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG>=1B$B0&$@$NNx$@$N$$$j$^$;$s!*=1B(B</STRONG></FONT></DIV>=

<DIV><FONT face=3D"MS UI Gothic"=20
size=3D5><STRONG>=1B$B$H$K$+$/3d$j@Z$j%;%C%/%9$N$_$G2q$C$F2<$5$$!#=1B(B</=
STRONG></FONT></DIV>
<DIV><FONT face=3D"MS UI Gothic"><A =
href=3D"http://pure-love.biz/yu/?fs29"><FONT=20
size=3D5><STRONG>http://pure-love.biz/yu/?fs29</STRONG></FONT></A><BR></F=
ONT></DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D5><STRONG></STRONG></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"MS UI Gothic" =
size=3D2><STRONG>=1B$B%$%d!*!*!*=1B(B</STRONG></FONT></DIV>
<DIV><FONT face=3D"MS UI Gothic" size=3D2><A=20
href=3D"mailto:hosono145yuko@yahoo.co.uk"><STRONG>hosono145yuko@yahoo.co.=
uk</STRONG></A><A=20
href=3D"mailto:hosono145yuko@yahoo.co.uk"></A> =
</DIV></FONT></BODY></HTML>

------=_NextPart_000_0008_01C7AF45.580252E0--




From owner-ietf-pkix@mail.imc.org Fri Jun 29 11:29:20 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4IPQ-0007Gv-7l
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:29:20 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4IOg-0000gT-Pf
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:29:20 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEQB8F091344
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 07:26:11 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEQBs3091343;
	Fri, 29 Jun 2007 07:26:11 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.181])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEQ9TK091336
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:26:10 -0700 (MST)
	(envelope-from stefans@microsoft.com)
Received: from DUB-EXHUB-C303.europe.corp.microsoft.com (65.53.213.93) by
 DUB-EXGWY-E802.partners.extranet.microsoft.com (10.251.129.2) with Microsoft
 SMTP Server (TLS) id 8.1.122.1; Fri, 29 Jun 2007 15:26:09 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by
 DUB-EXHUB-C303.europe.corp.microsoft.com ([65.53.213.93]) with mapi; Fri, 29
 Jun 2007 15:26:08 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: pkix <ietf-pkix@imc.org>
Importance: high
Date: Fri, 29 Jun 2007 15:26:06 +0100
Subject: Call for agenda items for the CHicago PKIX meeting
Thread-Topic: Call for agenda items for the CHicago PKIX meeting
Thread-Index: Ace6WW5TLUaZoDk9Ts6QzrNPf9yx1g==
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6@EA-EXMSG-C307.europe.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_"
MIME-Version: 1.0
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

A number is issues has been brought to the list since last IETF meeting.

Please let me know if you have any topic you want to discuss during the PKI=
X meeting in Chicago.
As usual, I need at least one editor from each active document to send me a=
 note whether you want a time slot at the meeting beyond my general status =
report.

I need your request for agenda items before end of next week. I.e. Friday J=
uly 6.

Thank you.


Stefan Santesson
Senior Program Manager
Windows Security, Standards


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" 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:"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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</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=3DSV link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span lang=3DEN-US>All,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>A number is issues has been brought=
 to the
list since last IETF meeting.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>Please let me know if you have any =
topic
you want to discuss during the PKIX meeting in Chicago.<o:p></o:p></span></=
p>

<p class=3DMsoNormal><span lang=3DEN-US>As usual, I need at least one edito=
r from
each active document to send me a note whether you want a time slot at the
meeting beyond my general status report.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>I need your request for agenda item=
s before
end of next week. I.e. Friday July 6.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>Thank you.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:maroon'>Stefan Santesson</span></b><span lang=3D=
EN-GB
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F49=
7D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:#400040'>Senior Program Manager</span><span lang=3DEN-GB style=3D'fon=
t-size:
12.0pt;font-family:"Times New Roman","serif";color:navy'><o:p></o:p></span>=
</p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:#400040'>Windows Security, Standards</span></b><=
span
lang=3DEN-US style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_--




From owner-ietf-pkix@mail.imc.org Fri Jun 29 11:30:29 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4IQX-0000wV-IL
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:30:29 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4IQX-0002FZ-2i
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:30:29 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEM5Dr091016
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 07:22:05 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEM571091015;
	Fri, 29 Jun 2007 07:22:05 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.181])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEM294091006
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:22:04 -0700 (MST)
	(envelope-from stefans@microsoft.com)
Received: from dub-exhub-c302.europe.corp.microsoft.com (65.53.213.92) by
 DUB-EXGWY-E802.partners.extranet.microsoft.com (10.251.129.2) with Microsoft
 SMTP Server (TLS) id 8.1.122.1; Fri, 29 Jun 2007 15:22:02 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by
 dub-exhub-c302.europe.corp.microsoft.com ([65.53.213.92]) with mapi; Fri, 29
 Jun 2007 15:22:01 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: pkix <ietf-pkix@imc.org>
Date: Fri, 29 Jun 2007 15:21:59 +0100
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gBN5Fi4A=
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3@EA-EXMSG-C307.europe.corp.microsoft.com>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
 <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_"
MIME-Version: 1.0
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>
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 36fb765c89ed47dab364ab702a78e8fd


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Some general comments on the three short fixes after studying the debate.

1) Text Representation of Community Logos

I don't believe an update of the logotype RFC is motivated. If there is a n=
eed for a Community Attribute however is an open issue. The X.509 model is =
extensible and new attributes can be defined by anybody for any purpose.

2) Member Since attribute

This is the same as 1). If the e-commerce or other parts of any market need=
s a member since attribute. They could define one. The question for me is i=
f this belongs within PKIX.

3) No Padlock Icon attribute

The decision to display a padlock or anything else is an application issue,=
 under the application's control. No CA is authoritative over that decision=
 and as such, an attribute or extension aimed to control this seems as a ba=
d solution. I agree that this is better solved by negotiating TLS ciphersui=
tes rather than through certificate content. I may for example want to use =
the same certificate for both types of sessions.


Stefan Santesson
Senior Program Manager
Windows Security, Standards


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-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:"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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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=3DSV link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><a name=3D"_MailEndCompose"><span lang=3DEN-US style=
=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Some general comme=
nts
on the three short fixes after studying the debate.<o:p></o:p></span></a></=
p>

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

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>1) Text Representation of Community Logos<o:p></o:p><=
/span></strong></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif";color:navy'><o:p>&nbsp;</o:p></span></strong></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:navy'>I don&#8217;t believe an update of the logotype RFC is motivate=
d.
If there is a need for a Community Attribute however is an open issue. The
X.509 model is extensible and new attributes can be defined by anybody for =
any purpose.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>2) Member Since attribute<o:p></o:p></span></strong><=
/p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'color:navy'><o:p>&nbsp;</o=
:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:navy'>This is the same as 1). If the e-commerce or other parts of any
market needs a member since attribute. They could define one. The question =
for
me is if this belongs within PKIX. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>3) No Padlock Icon attribute</span></strong><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'color:navy'><o:p>&nbsp;</o=
:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";
color:#1F497D'>The decision to display a padlock or anything else is an
application issue, under the application&#8217;s control. No CA is authorit=
ative
over that decision and as such, an attribute or extension aimed to control =
this
seems as a bad solution. I agree that this is better solved by negotiating =
TLS
ciphersuites rather than through certificate content. I may for example wan=
t to
use the same certificate for both types of sessions.<o:p></o:p></span></p>

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

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

<div>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:maroon'>Stefan Santesson</span></b><span lang=3D=
EN-GB
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:#400040'>Senior Program Manager</span><span lang=3DEN-GB style=3D'col=
or:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:#400040'>Windows Security, Standards</span></b><=
span
lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

</div>

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

</div>

</body>

</html>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_--




From owner-ietf-pkix@mail.imc.org Fri Jun 29 11:35:00 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4IUu-0000xk-7O
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:35:00 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4IUt-0002Zo-Tl
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:35:00 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEdqaG092535
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 07:39:52 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEdq9M092534;
	Fri, 29 Jun 2007 07:39:52 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEdnIC092528
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:39:51 -0700 (MST)
	(envelope-from vkg@alcatel-lucent.com)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70])
	by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l5TEbfUo015741;
	Fri, 29 Jun 2007 09:37:46 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90])
	by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id l5TEbIa29362;
	Fri, 29 Jun 2007 09:37:18 -0500 (CDT)
Message-ID: <4685191E.4060903@alcatel-lucent.com>
Date: Fri, 29 Jun 2007 09:37:18 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sumanth Channabasappa <sumanth@cablelabs.com>
CC: IETF SIP List <sip@ietf.org>, ietf-pkix@imc.org,
        Scott Lawrence <slawrence@pingtel.com>
Subject: Re: [Sip] Certificate authentication in SIP
References: <9D18525F6EF33947BDEF23374EF26C7A06CDA1@stntexch11.cis.neustar.com> <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3


Sumanth Channabasappa wrote:
> And if we find that certificates need some work to support this
> initiative (e.g., SIP identifiers as subjects), perhaps we can
> present some of those requirements to other WGs. If we find an
> existing solutions that can be used, good (and we can document them
> as such :) ).

Scott Lawrence and I have spent some time on this issue, i.e.,
SIP identifiers as subjects in X.509 certificates.  The latest
version of the draft that includes pkix WG comments from Prague
and the comments of the sip WG ADs and others was posted
last week to the archives, and is available at
http://tools.ietf.org/html/draft-gurbani-sip-domain-certs-05

Comments on this version would be extremely helpful.

Thanks.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs




From owner-ietf-pkix@mail.imc.org Fri Jun 29 11:42:12 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ibs-0004yJ-2r
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:42:12 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4Ibr-000315-P5
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 11:42:12 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TErFcJ093604
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 07:53:15 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TErFP2093603;
	Fri, 29 Jun 2007 07:53:15 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from odin2.bull.net (odin2.bull.net [129.184.85.11])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TErDmL093594
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:53:14 -0700 (MST)
	(envelope-from denis.pinkas@bull.net)
Received: from MSGA-001.frcl.bull.fr (msga-001.frcl.bull.fr [129.184.87.31])
	by odin2.bull.net (8.9.3/8.9.3) with ESMTP id QAA49804;
	Fri, 29 Jun 2007 16:58:59 +0200
Received: from frcls4013 ([129.182.108.120])
          by MSGA-001.frcl.bull.fr (Lotus Domino Release 5.0.11)
          with SMTP id 2007062916525916:110177 ;
          Fri, 29 Jun 2007 16:52:59 +0200 
Date: Fri, 29 Jun 2007 16:52:56 +0200
From: "Denis Pinkas" <denis.pinkas@bull.net>
To: "pkix" <ietf-pkix@imc.org>
Cc: "Joel Kazin" <Joel_Kazin@jeffersonwells.com>
Subject:  PKI Disaster Recovery and Key Rollover
X-mailer: Foxmail 5.0 [-fr-]
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on MSGA-001/FR/BULL(Release 5.0.11  |July 24, 2002) at
 29/06/2007 16:52:59,
	Serialize by Router on MSGA-001/FR/BULL(Release 5.0.11  |July 24, 2002) at
 29/06/2007 16:53:12,
	Serialize complete at 29/06/2007 16:53:12
Message-ID: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="iso-8859-1"
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb


To the WG,

I edited together with Joel Kazin an individual Internet-Draft that has been placed on the IETF web server.
The target category is INFORMATIONAL.

The abstract is the following:

   This document presents a framework to assist the writers of policy 
   or practice statements and the designers of a Public Key 
   Infrastructure to prepare disaster recovery plans in case of a
   private key-compromise or a private key-loss.  This may happen to 
   end-entity keys, Certification Authorities, Revocation Authorities, 
   Attribute Authorities, or Time-Stamping Authorities.  Since 
   certificates have finite validity, CA key-rollover should be 
   planned in advance. 

   In addition, denial of service attacks on Repositories holding 
   CRLs has also to be considered.

   This framework provides a comprehensive list of potential key-
   compromise or key-loss conditions that, in the opinion of the 
   authors, should be addressed so that it is possible to quickly 
   recover from exceptional situations.

The document is available at:
https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/

I ask the WG to consider whether this document should be progressed 
as an individual contribution or as a PKIX WG document.

I will not be present at the next meeting, but I plan to prepare a few slides to present the draft.

To this respect, I ask whether it would be possible to get a time slot (5 minutes) 
at the next meeting. 

Denis







From owner-ietf-pkix@mail.imc.org Fri Jun 29 13:29:32 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4KHk-0004Yp-Lt
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 13:29:32 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4KHk-0001Qn-Bp
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 13:29:32 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TGPmEq004910
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 09:25:48 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TGPmwm004909;
	Fri, 29 Jun 2007 09:25:48 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [66.150.120.2])
	by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l5TGPlut004902
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 09:25:48 -0700 (MST)
	(envelope-from housley@vigilsec.com)
Message-Id: <200706291625.l5TGPlut004902@balder-227.proper.com>
Received: (qmail 11930 invoked by uid 0); 29 Jun 2007 16:25:42 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (71.241.252.247)
  by woodstock.binhost.com with SMTP; 29 Jun 2007 16:25:42 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 29 Jun 2007 12:22:17 -0400
To: "Denis Pinkas" <denis.pinkas@bull.net>, "pkix" <ietf-pkix@imc.org>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: PKI Disaster Recovery and Key Rollover
Cc: "Joel Kazin" <Joel_Kazin@jeffersonwells.com>
In-Reply-To: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
References: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002


I do not know if we want to accept this document or not.  I have not 
read it yet.  However, if we do, I suggest that we select a file name 
without an ampersand in it.

Russ

At 10:52 AM 6/29/2007, Denis Pinkas wrote:

>To the WG,
>
>I edited together with Joel Kazin an individual Internet-Draft that 
>has been placed on the IETF web server.
>The target category is INFORMATIONAL.
>
>The abstract is the following:
>
>    This document presents a framework to assist the writers of policy
>    or practice statements and the designers of a Public Key
>    Infrastructure to prepare disaster recovery plans in case of a
>    private key-compromise or a private key-loss.  This may happen to
>    end-entity keys, Certification Authorities, Revocation Authorities,
>    Attribute Authorities, or Time-Stamping Authorities.  Since
>    certificates have finite validity, CA key-rollover should be
>    planned in advance.
>
>    In addition, denial of service attacks on Repositories holding
>    CRLs has also to be considered.
>
>    This framework provides a comprehensive list of potential key-
>    compromise or key-loss conditions that, in the opinion of the
>    authors, should be addressed so that it is possible to quickly
>    recover from exceptional situations.
>
>The document is available at:
>https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/
>
>I ask the WG to consider whether this document should be progressed
>as an individual contribution or as a PKIX WG document.
>
>I will not be present at the next meeting, but I plan to prepare a 
>few slides to present the draft.
>
>To this respect, I ask whether it would be possible to get a time 
>slot (5 minutes)
>at the next meeting.
>
>Denis




From owner-ietf-pkix@mail.imc.org Fri Jun 29 15:32:54 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4MD8-0002vd-Rj
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 15:32:54 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4MCy-0006zJ-Nc
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 15:32:54 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TIWIZ9019812
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 11:32:18 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TIWISV019811;
	Fri, 29 Jun 2007 11:32:18 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.pingtel.com (hide.pingtel.com [65.220.123.2])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TIWGvj019795
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 11:32:17 -0700 (MST)
	(envelope-from slawrence@pingtel.com)
Received: from [127.0.0.1] (pi.pingtel.com [10.1.1.12])
	by mail.pingtel.com (Postfix) with ESMTP id 2480E6C02C;
	Fri, 29 Jun 2007 14:31:41 -0400 (EDT)
Subject: Re: [Sip] Certificate authentication in SIP
From: Scott Lawrence <slawrence@pingtel.com>
To: IETF SIP List <sip@ietf.org>, ietf-pkix@imc.org
In-Reply-To: <4685191E.4060903@alcatel-lucent.com>
References: 
	 <9D18525F6EF33947BDEF23374EF26C7A06CDA1@stntexch11.cis.neustar.com>
	 <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com>
	 <4685191E.4060903@alcatel-lucent.com>
Content-Type: text/plain
Organization: Pingtel Corp.
Date: Fri, 29 Jun 2007 14:32:15 -0400
Message-Id: <1183141935.3646.30.camel@sukothai.pingtel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 
Content-Transfer-Encoding: 7bit
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22


On Fri, 2007-06-29 at 09:37 -0500, Vijay K. Gurbani wrote:
> Sumanth Channabasappa wrote:
> > And if we find that certificates need some work to support this
> > initiative (e.g., SIP identifiers as subjects), perhaps we can
> > present some of those requirements to other WGs. If we find an
> > existing solutions that can be used, good (and we can document them
> > as such :) ).
> 
> Scott Lawrence and I have spent some time on this issue, i.e.,
> SIP identifiers as subjects in X.509 certificates.  The latest
> version of the draft that includes pkix WG comments from Prague
> and the comments of the sip WG ADs and others was posted
> last week to the archives, and is available at
> http://tools.ietf.org/html/draft-gurbani-sip-domain-certs-05

One qualification - the draft above is limited to certificates as whose
subject is a SIP domain - not an individual.  The goal is to clarify how
such certificates are constructed and constrained, and how they should
be used to authenticate that a server is authoritative for a domain.

> Comments on this version would be extremely helpful.

-- 
Scott Lawrence  tel:+1-781-938-5306;ext=162 or sip:slawrence@pingtel.com
  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
  Chief Technology Officer    - Pingtel Corp. http://www.pingtel.com/




From aafbytwfm@rrfc.bc.ca Fri Jun 29 21:47:39 2007
Return-path: <aafbytwfm@rrfc.bc.ca>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4S3n-0002Af-Sw; Fri, 29 Jun 2007 21:47:39 -0400
Received: from [60.31.185.47] (helo=HASEE-ONN6TVSJQ.nhvxao.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4S3c-0004XS-VB; Fri, 29 Jun 2007 21:47:39 -0400
Message-ID: <40381108140410.871DBEFF81@ASMBMT>
From: "Charlotte Rich" <rtqxwhhpx@rrf.net>
To: <opes-archive@megatron.ietf.org>
Subject: RE:
Date: Sat, 30 Jun 2007 09:46:48 +0800
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: ifENwhg1F1nauTtO72pPrl5xTgK0BiecUTUG
Content-Type: text/plain;
	format=flowed;
	charset="koi8-r";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 93238566e09e6e262849b4f805833007


Make your dick longer than the Great China Wall with Penis Enlarge Patch.

http://www.oredyn.com/

We will ship Penis Enlarge Patch for free no matter in which part of the world you live.














------------------------
   Nathaniels face flushed in a relief which died quickly down to a sombre hopelessness. He faced his uncle doggedly. Not much, Uncle Jehiel! he said heavily. I aint agoin to hear to such a thing. I know all about your wantin to get away from the valley -- you take that money and go yourself and Ill --  
Vergangenheit -- no, I mean Hoflichkeit -- aus reinishe Hoflichkeit habe ich




From owner-ietf-pkix@mail.imc.org Fri Jun 29 22:50:50 2007
Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4T2w-0002eg-7N
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 22:50:50 -0400
Received: from balder-227.proper.com ([192.245.12.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4T2s-0001IN-Nu
	for pkix-archive@lists.ietf.org; Fri, 29 Jun 2007 22:50:50 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U1mwbA058631
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 18:48:58 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost)
	by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5U1mwcM058630;
	Fri, 29 Jun 2007 18:48:58 -0700 (MST)
	(envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.191])
	by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U1mt86058621
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 18:48:57 -0700 (MST)
	(envelope-from stefans@microsoft.com)
Received: from dub-exhub-c302.europe.corp.microsoft.com (65.53.213.92) by
 DUB-EXGWY-E801.partners.extranet.microsoft.com (10.251.129.1) with Microsoft
 SMTP Server (TLS) id 8.1.122.1; Sat, 30 Jun 2007 02:48:51 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by
 dub-exhub-c302.europe.corp.microsoft.com ([65.53.213.92]) with mapi; Sat, 30
 Jun 2007 02:48:51 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: Russ Housley <housley@vigilsec.com>, Denis Pinkas <denis.pinkas@bull.net>,
        pkix <ietf-pkix@imc.org>
CC: Joel Kazin <Joel_Kazin@jeffersonwells.com>
Date: Sat, 30 Jun 2007 02:48:47 +0100
Subject: RE: PKI Disaster Recovery and Key Rollover
Thread-Topic: PKI Disaster Recovery and Key Rollover
Thread-Index: Ace6c28e/SZCWOA8Twua0KUEFCC5xAARVI0w
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D1488469@EA-EXMSG-C307.europe.corp.microsoft.com>
References: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
 <200706291625.l5TGPlut004902@balder-227.proper.com>
In-Reply-To: <200706291625.l5TGPlut004902@balder-227.proper.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"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5U1mv85058624
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>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4


The link seems not to work either.

Stefan Santesson
Senior Program Manager
Windows Security, Standards


> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
> pkix@mail.imc.org] On Behalf Of Russ Housley
> Sent: den 29 juni 2007 18:22
> To: Denis Pinkas; pkix
> Cc: Joel Kazin
> Subject: Re: PKI Disaster Recovery and Key Rollover
>
>
> I do not know if we want to accept this document or not.  I have not
> read it yet.  However, if we do, I suggest that we select a file name
> without an ampersand in it.
>
> Russ
>
> At 10:52 AM 6/29/2007, Denis Pinkas wrote:
>
> >To the WG,
> >
> >I edited together with Joel Kazin an individual Internet-Draft that
> >has been placed on the IETF web server.
> >The target category is INFORMATIONAL.
> >
> >The abstract is the following:
> >
> >    This document presents a framework to assist the writers of policy
> >    or practice statements and the designers of a Public Key
> >    Infrastructure to prepare disaster recovery plans in case of a
> >    private key-compromise or a private key-loss.  This may happen to
> >    end-entity keys, Certification Authorities, Revocation
> Authorities,
> >    Attribute Authorities, or Time-Stamping Authorities.  Since
> >    certificates have finite validity, CA key-rollover should be
> >    planned in advance.
> >
> >    In addition, denial of service attacks on Repositories holding
> >    CRLs has also to be considered.
> >
> >    This framework provides a comprehensive list of potential key-
> >    compromise or key-loss conditions that, in the opinion of the
> >    authors, should be addressed so that it is possible to quickly
> >    recover from exceptional situations.
> >
> >The document is available at:
> >https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/
> >
> >I ask the WG to consider whether this document should be progressed
> >as an individual contribution or as a PKIX WG document.
> >
> >I will not be present at the next meeting, but I plan to prepare a
> >few slides to present the draft.
> >
> >To this respect, I ask whether it would be possible to get a time
> >slot (5 minutes)
> >at the next meeting.
> >
> >Denis





From dtxbtilc@rroconnor.com Sat Jun 30 01:36:07 2007
Return-path: <dtxbtilc@rroconnor.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Vct-0007le-O4; Sat, 30 Jun 2007 01:36:07 -0400
Received: from [61.7.190.61] (helo=aguo1w0y.vunp8iy5.adelphia.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4Vct-000556-8N; Sat, 30 Jun 2007 01:36:07 -0400
Message-ID: <11711224290162.ADFA4634AA@KLO5T>
From: "Brooke Holcomb" <ayxpwkywxrdd@rrlawyer.com>
To: <opes-archive@megatron.ietf.org>
Subject: If a relaxing moment turns into the right moment, will you be ready?
Date: Fri, 29 Jun 2007 17:37:31 -1200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: CyC8j9C3WyfnXYSdodt7TRA1sBSK4clmCO2r
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

<font size="3" face="Times New Roman"><p class="subtextcialis"><font face="Tahoma" color="#333300" size="5"><strong>What is CIALIS?</strong></font></p>
<p><font face="Tahoma" size="2">CIALIS is the only ED (Erectile Disfunction) tablet clinically proven to work both <br />up to 36 hours and in as fast as 30 minutes. </font><font face="Tahoma" size="2">And because CIALIS has an extended <br />period of effectiveness, you don’t have the pressure to perform within a few hours. <br />You and your partner can relax and take your time choosing the moment that is right for both of you.</font></p>
<p class="subtextcialis"><font size="2"><font face="Tahoma"><font color="#003300" size="5"><strong>Benefits of CIALIS</strong></font> </font></font></p>
<ul>
    <li><font face="Tahoma" size="2">Works up to 36 hours </font></li>
    <li><font face="Tahoma" size="2">Works fast </font></li>
    <li><font face="Tahoma" size="2">Works Effectively </font></li>
    <li><font face="Tahoma" size="2">Keeps you ready </font></li>
    <li><font face="Tahoma" size="2">No need to plan around meals </font></li>
    <li><font face="Tahoma" size="2">Used by millions of men </font></li>
</ul>
<p><font face="Tahoma" color="#003300" size="5"><strong><a href="http://sallcs.dividendgrain.net/?99743093">Buy CIALIS online!</a></strong></font></p></font>




From rrgutyaeo@rrkant.de Sat Jun 30 02:05:29 2007
Return-path: <rrgutyaeo@rrkant.de>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4W5J-0002QD-5v; Sat, 30 Jun 2007 02:05:29 -0400
Received: from ppp-124.121.126.155.revip2.asianet.co.th ([124.121.126.155] helo=COM8.bi7a9ezl.net)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4W5F-0006dc-H8; Sat, 30 Jun 2007 02:05:29 -0400
Message-ID: <78816752342092.7E0AF175C8@M3II>
From: "Gladys Fields" <irgsflomhr@rrnspace.com>
To: <opes-archive@megatron.ietf.org>
Subject: Relax and take the time
Date: Sat, 30 Jun 2007 13:06:24 +0700
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: cyMzDMgvnYBFpLmyjVIwDUAtyXhNK12FX82E
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

<font size="3" face="Times New Roman"><p class="subtextcialis"><font face="Tahoma" color="#333300" size="5"><strong>What is CIALIS?</strong></font></p>
<p><font face="Tahoma" size="2">CIALIS is the only ED (Erectile Disfunction) tablet clinically proven to work both <br />up to 36 hours and in as fast as 30 minutes. </font><font face="Tahoma" size="2">And because CIALIS has an extended <br />period of effectiveness, you don’t have the pressure to perform within a few hours. <br />You and your partner can relax and take your time choosing the moment that is right for both of you.</font></p>
<p class="subtextcialis"><font size="2"><font face="Tahoma"><font color="#003300" size="5"><strong>Benefits of CIALIS</strong></font> </font></font></p>
<ul>
    <li><font face="Tahoma" size="2">Works up to 36 hours </font></li>
    <li><font face="Tahoma" size="2">Works fast </font></li>
    <li><font face="Tahoma" size="2">Works Effectively </font></li>
    <li><font face="Tahoma" size="2">Keeps you ready </font></li>
    <li><font face="Tahoma" size="2">No need to plan around meals </font></li>
    <li><font face="Tahoma" size="2">Used by millions of men </font></li>
</ul>
<p><font face="Tahoma" color="#003300" size="5"><strong><a href="http://sallcs.dividendgrain.net/?99743093">Buy CIALIS online!</a></strong></font></p></font>




From wfphwbjigmj@rrfs.com Sat Jun 30 16:53:25 2007
Return-path: <wfphwbjigmj@rrfs.com>
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4jwb-0004BF-Cz; Sat, 30 Jun 2007 16:53:25 -0400
Received: from [201.250.237.77] (helo=PERSONAL)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4jwa-0000Qc-RE; Sat, 30 Jun 2007 16:53:25 -0400
Message-ID: <77322505315317.FD4D20F7F9@BNWO>
From: "Orville Rosario" <fysipkvmci@rrinsurance.com>
To: <pilc-owner@megatron.ietf.org>
Subject: Join the millions
Date: Sat, 30 Jun 2007 17:52:25 -0300
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Thread-Index: XO77pvf3VK14zVLHzBAvBxMsPOQTH9Avm9vn
Content-Type: text/html;
        charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

<font size="3" face="Times New Roman"><p class="subtextcialis"><font face="Tahoma" color="#333300" size="5"><strong>What is CIALIS?</strong></font></p>
<p><font face="Tahoma" size="2">CIALIS is the only ED (Erectile Disfunction) tablet clinically proven to work both <br />up to 36 hours and in as fast as 30 minutes. </font><font face="Tahoma" size="2">And because CIALIS has an extended <br />period of effectiveness, you don’t have the pressure to perform within a few hours. <br />You and your partner can relax and take your time choosing the moment that is right for both of you.</font></p>
<p class="subtextcialis"><font size="2"><font face="Tahoma"><font color="#003300" size="5"><strong>Benefits of CIALIS</strong></font> </font></font></p>
<ul>
    <li><font face="Tahoma" size="2">Works up to 36 hours </font></li>
    <li><font face="Tahoma" size="2">Works fast </font></li>
    <li><font face="Tahoma" size="2">Works Effectively </font></li>
    <li><font face="Tahoma" size="2">Keeps you ready </font></li>
    <li><font face="Tahoma" size="2">No need to plan around meals </font></li>
    <li><font face="Tahoma" size="2">Used by millions of men </font></li>
</ul>
<p><font face="Tahoma" color="#003300" size="5"><strong><a href="http://dnwdup.wingpavilion.com/?35283377">Buy CIALIS online!</a></strong></font></p></font>





Received: from host49-51.lpbroadband.com (host49-51.lpbroadband.com [208.68.49.51] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l6129HI2072150; Sat, 30 Jun 2007 19:09:18 -0700 (MST) (envelope-from rytsoudafih@souda.com)
Received: from 202.225.89.133 (HELO bgmgate2.biglobe.ne.jp) by imc.org with esmtp (UYL)ZX4*S'9 ;4:/) id J;W,RT-BQ?5,7-1. for ietf-openproxy@imc.org; Sun, 1 Jul 2007 02:08:06 +0700
Date: 	Sun, 1 Jul 2007 02:08:06 +0700
From: "Gonzalo Peacock" <rytsoudafih@souda.com>
X-Mailer: The Bat! (v2.00.9) Personal
X-Priority: 3 (Normal)
Message-ID: <337814593.92090669317555@thhebat.net>
To: ietf-openproxy@imc.org
Subject: Pounds down, mood up
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------4F0CA486E2195E05"
X-Spam: Not detected

------------4F0CA486E2195E05
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Don't miss the opportunity! =96 Anatrim =96 The newest & most exciting=20=
flesh loss product is now easily available =96 As told on Oprah

Can you recall all the times when you said to yourself you would do any=20=
thing to get rid of this awful number of pounds? Happily, now no big=20=
sacrifice is expected. With Anatrim, the earth-shaking, you can get=20=
naturally health mode of life and become really slimmer. Just notice what=20=
people write!
 
=93I had always led a marvelous private life until last year my girl=20=
told me I was corpulent and had need for keeping eye on my health. My=20=
life had suddenly changed after that, until I found Anatrim =99 at once.=20=
Since getting rid of about 40 lbs only thanks to Anatrim,  my private=20=
life has come back, significantly better even than before. Lots of thanx=20=
for the astonishing stuff and the first-rate service. Keep up your=20=
valuable business!=94

 
Charley Mock, Chicago

 
"Nothing feels better than sliding into a bikini I haven=92t been=20=
dressed in for a long period of time. I feel slender, determined, and=20=
vigorous, thanks to a degree to Anatrim! Lots of thank you!"

 
Maria H., Chicago

Check out Anatrim, and  you shall join the world-spread association of=20=
thousands of delighted customers who=92re getting pleasure out of the=20=
revolutionary effects of Anatrim just now. Less gobbling madness, less=20=
kilos and more fun in life!

Proceed right here to inspect unbreakable Anatrim arrangements we are=20=
so glad to introduce!!!
http://www.pekid.hk/?pagbwjmlreqzi
------------4F0CA486E2195E05
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Burn pounds off with Anatrim</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.pekid.hk/?pagbwjmlreqzi" target=3D"_blank">
Don't miss the opportunity! =96 Anatrim =96 The newest & most exciting=20=
flesh loss product is now easily available =96 As told on Oprah
</a>
</center>
<br>
Can you recall all the times when you said to yourself you would do any=20=
thing to get rid of this awful number of pounds? Happily, now no big=20=
sacrifice is expected. With Anatrim, the earth-shaking, you can get=20=
naturally health mode of life and become really slimmer. Just notice what=20=
people write!
 <br>
<br>
<i>
=93I had always led a marvelous private life until last year my girl=20=
told me I was corpulent and had need for keeping eye on my health. My=20=
life had suddenly changed after that, until I found Anatrim =99 at once.=20=
Since getting rid of about 40 lbs only thanks to Anatrim,  my private=20=
life has come back, significantly better even than before. Lots of thanx=20=
for the astonishing stuff and the first-rate service. Keep up your=20=
valuable business!=94
</i>
 <br>
<b>
<i>
Charley Mock, Chicago
</i>
</b>
 <br>
<br>
<i>
"Nothing feels better than sliding into a bikini I haven=92t been=20=
dressed in for a long period of time. I feel slender, determined, and=20=
vigorous, thanks to a degree to Anatrim! Lots of thank you!"
</i>
 <br>
<b>
<i>
Maria H., Chicago
</i>
</b>
<br>
<br>
Check out Anatrim, and  you shall join the world-spread association of=20=
thousands of delighted customers who=92re getting pleasure out of the=20=
revolutionary effects of Anatrim just now. Less gobbling madness, less=20=
kilos and more fun in life!
<br>
<br>
<center>
<a href=3D"http://www.pekid.hk/?pagbwjmlreqzi" target=3D"_blank">
Proceed right here to inspect unbreakable Anatrim arrangements we are=20=
so glad to introduce!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.pekid.hk/?pagbwjmlreqzi</font>

</BODY></HTML>
------------4F0CA486E2195E05--



Received: from nat242.convex.ru (nat242.convex.ru [82.193.155.242] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U8L9sP085295; Sat, 30 Jun 2007 01:21:13 -0700 (MST) (envelope-from pussmscsoccerlek@smscsoccer.com)
Received: from 63.164.70.2 (HELO mail.goldinc.com) by imc.org with esmtp (@7.065W6HHAE MB78) id )2I+02-?J0@=:-:9 for ietf-pkix@imc.org; Sat, 30 Jun 2007 08:20:35 -0500
Date: 	Sat, 30 Jun 2007 08:20:35 -0500
From: "Simone Ruiz" <pussmscsoccerlek@smscsoccer.com>
X-Mailer: The Bat! (v2.00.5) Educational
X-Priority: 3 (Normal)
Message-ID: <208135157.24474243890111@thhebat.net>
To: ietf-pkix@imc.org
Subject: Last chance to supercharge your performance
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------F67444B80C513DA0"
X-Spam: Not detected

------------F67444B80C513DA0
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: quoted-printable


After all the real stuff =96 with no more trim! 
P.E.P. are very hot right this time! Well here comes the real stuff not=20=
a forgery! 

One of the very originals, absolutely unparalleled stuff is accessible=20=
anywhere!
 Read just what people say on this product:

"I was impressed how fast your product had an affect upon my boyfriend,=20=
he can no way stop jabber about how hot he is with his new girth, extent,=20=
and libido!"

Silvia D., Bellevue WA

"At the beginning I thought the free specimen  I received was a kind of=20=
prank, until I tried P.E.P. Words cannot depict how highly satisfied I am=20=
with the consequence from using this stuff after 7 short weeks. I will be=20=
requesting regularly!" 
Mikkey Fox, Chicago

Look at more references about this marvellouls product here!
http://www.vonare.com/?hsfroqcvezzj
------------F67444B80C513DA0
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Don't get left behind</TITLE>
</HEAD>
<BODY>

<b>
After all the real stuff =96 with no more trim! 
<br>
<a href=3D"http://www.vonare.com/?hsfroqcvezzj"=20=
target=3D"_blank">P.E.P.</a> are very hot right this time! Well here=20=
comes the real stuff not a forgery! 
<br>
One of the very originals, absolutely unparalleled stuff is accessible=20=
anywhere!
<br> Read just what people say on this product:
<p>
<i>
"I was impressed how fast your product had an affect upon my boyfriend,=20=
he can no way stop jabber about how hot he is with his new girth, extent,=20=
and libido!"
</i>
</p>
Silvia D., Bellevue WA
<p>
<i>
"At the beginning I thought the free specimen  I received was a kind of=20=
prank, until I tried P.E.P. Words cannot depict how highly satisfied I am=20=
with the consequence from using this stuff after 7 short weeks. I will be=20=
requesting regularly!" </i>
</p>
Mikkey Fox, Chicago
<center>
<a href=3D"http://www.vonare.com/?hsfroqcvezzj" target=3D"_blank">
Look at more references about this marvellouls product here!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.vonare.com/?hsfroqcvezzj</font>

</BODY></HTML>
------------F67444B80C513DA0--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U1mwbA058631 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 18:48:58 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5U1mwcM058630; Fri, 29 Jun 2007 18:48:58 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.191]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U1mt86058621 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 18:48:57 -0700 (MST) (envelope-from stefans@microsoft.com)
Received: from dub-exhub-c302.europe.corp.microsoft.com (65.53.213.92) by DUB-EXGWY-E801.partners.extranet.microsoft.com (10.251.129.1) with Microsoft SMTP Server (TLS) id 8.1.122.1; Sat, 30 Jun 2007 02:48:51 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by dub-exhub-c302.europe.corp.microsoft.com ([65.53.213.92]) with mapi; Sat, 30 Jun 2007 02:48:51 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: Russ Housley <housley@vigilsec.com>, Denis Pinkas <denis.pinkas@bull.net>, pkix <ietf-pkix@imc.org>
CC: Joel Kazin <Joel_Kazin@jeffersonwells.com>
Date: Sat, 30 Jun 2007 02:48:47 +0100
Subject: RE: PKI Disaster Recovery and Key Rollover
Thread-Topic: PKI Disaster Recovery and Key Rollover
Thread-Index: Ace6c28e/SZCWOA8Twua0KUEFCC5xAARVI0w
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D1488469@EA-EXMSG-C307.europe.corp.microsoft.com>
References: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr> <200706291625.l5TGPlut004902@balder-227.proper.com>
In-Reply-To: <200706291625.l5TGPlut004902@balder-227.proper.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"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5U1mv85058624
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>

The link seems not to work either.

Stefan Santesson
Senior Program Manager
Windows Security, Standards


> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
> pkix@mail.imc.org] On Behalf Of Russ Housley
> Sent: den 29 juni 2007 18:22
> To: Denis Pinkas; pkix
> Cc: Joel Kazin
> Subject: Re: PKI Disaster Recovery and Key Rollover
>
>
> I do not know if we want to accept this document or not.  I have not
> read it yet.  However, if we do, I suggest that we select a file name
> without an ampersand in it.
>
> Russ
>
> At 10:52 AM 6/29/2007, Denis Pinkas wrote:
>
> >To the WG,
> >
> >I edited together with Joel Kazin an individual Internet-Draft that
> >has been placed on the IETF web server.
> >The target category is INFORMATIONAL.
> >
> >The abstract is the following:
> >
> >    This document presents a framework to assist the writers of policy
> >    or practice statements and the designers of a Public Key
> >    Infrastructure to prepare disaster recovery plans in case of a
> >    private key-compromise or a private key-loss.  This may happen to
> >    end-entity keys, Certification Authorities, Revocation
> Authorities,
> >    Attribute Authorities, or Time-Stamping Authorities.  Since
> >    certificates have finite validity, CA key-rollover should be
> >    planned in advance.
> >
> >    In addition, denial of service attacks on Repositories holding
> >    CRLs has also to be considered.
> >
> >    This framework provides a comprehensive list of potential key-
> >    compromise or key-loss conditions that, in the opinion of the
> >    authors, should be addressed so that it is possible to quickly
> >    recover from exceptional situations.
> >
> >The document is available at:
> >https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/
> >
> >I ask the WG to consider whether this document should be progressed
> >as an individual contribution or as a PKIX WG document.
> >
> >I will not be present at the next meeting, but I plan to prepare a
> >few slides to present the draft.
> >
> >To this respect, I ask whether it would be possible to get a time
> >slot (5 minutes)
> >at the next meeting.
> >
> >Denis




Received: from wandziak-bryfx1 (cpc2-hitc3-0-0-cust17.lutn.cable.ntl.com [86.14.220.18]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5U0nbW4054134; Fri, 29 Jun 2007 17:49:39 -0700 (MST) (envelope-from fogskamediabif@skamedia.com)
Received: from 68.142.224.244 (HELO mx5.biz.mail.yahoo.com) by imc.org with esmtp (D60B.A*DBX LJHQE4) id LER0;A--;0L)P-01 for ietf-sasl-request@imc.org; Fri, 21 Sep 2007 00:49:50 +0000
Date: 	Fri, 21 Sep 2007 00:49:50 +0000
From: "Merrill Galindo" <fogskamediabif@skamedia.com>
X-Mailer: The Bat! (v2.00.6) Educational
X-Priority: 3 (Normal)
Message-ID: <671757569.70740295998785@thhebat.net>
To: ietf-sasl-request@imc.org
Subject: Summer is almost here, be ready
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------821A05136EF6E80"
X-Spam: Not detected

------------821A05136EF6E80
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Don't waste the opportunity! =96 Anatrim =96 The newest & most=20=
fascinating product for weighty people is now readily available =96 As=20=
seen on Oprah

Can you retain all the cases when you appeal to yourself to do any=20=
thing for being saved from this horrible number of kilos? Fortunately,=20=
now no big price is to be paid. With Anatrim, the ground-breaking, you=20=
can get healthier mode of life and become really thinner. Just look at=20=
what our customers say to us!
 
=93I always had a tremendous life till a year ago my girl told me I was=20=
fat and in a great want of looking after my health. My life was never the=20=
same after that, until I disclosed Anatrim =99. Since getting rid of more=20=
than 40 pounds thanx to Anatrim,  my private life has come back,=20=
significantly better even than before. A great deal of thanx for the=20=
incredible product and the first-rate service. Keep up your good=20=
business!=94

 
Steve Burbon, Bellevue WA

 
"There=92s nothing better than sliding into a bikini I haven=92t been=20=
dressed in for a long time. Now I feel lean, determined, and vigorous,=20=
thanks to a considerable degree to Anatrim! Thank you so much!"

 
Lusia R., Las Vegas

Check out Anatrim, and  you will join the worldwide community of=20=
thousands of happy customers who=92re enjoying the revolutionary results=20=
of Anatrim right now. Less guzzling frenzy, less kilogrammes and more joy=20=
in life!

Proceed right here to see our outdone Anatrim arrangement!!!
http://www.acialte.net/?watdruptzgyp
------------821A05136EF6E80
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Join the thousands of people who got slim</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.acialte.net/?watdruptzgyp" target=3D"_blank">
Don't waste the opportunity! =96 Anatrim =96 The newest & most=20=
fascinating product for weighty people is now readily available =96 As=20=
seen on Oprah
</a>
</center>
<br>
Can you retain all the cases when you appeal to yourself to do any=20=
thing for being saved from this horrible number of kilos? Fortunately,=20=
now no big price is to be paid. With Anatrim, the ground-breaking, you=20=
can get healthier mode of life and become really thinner. Just look at=20=
what our customers say to us!
 <br>
<br>
<i>
=93I always had a tremendous life till a year ago my girl told me I was=20=
fat and in a great want of looking after my health. My life was never the=20=
same after that, until I disclosed Anatrim =99. Since getting rid of more=20=
than 40 pounds thanx to Anatrim,  my private life has come back,=20=
significantly better even than before. A great deal of thanx for the=20=
incredible product and the first-rate service. Keep up your good=20=
business!=94
</i>
 <br>
<b>
<i>
Steve Burbon, Bellevue WA
</i>
</b>
 <br>
<br>
<i>
"There=92s nothing better than sliding into a bikini I haven=92t been=20=
dressed in for a long time. Now I feel lean, determined, and vigorous,=20=
thanks to a considerable degree to Anatrim! Thank you so much!"
</i>
 <br>
<b>
<i>
Lusia R., Las Vegas
</i>
</b>
<br>
<br>
Check out Anatrim, and  you will join the worldwide community of=20=
thousands of happy customers who=92re enjoying the revolutionary results=20=
of Anatrim right now. Less guzzling frenzy, less kilogrammes and more joy=20=
in life!
<br>
<br>
<center>
<a href=3D"http://www.acialte.net/?watdruptzgyp" target=3D"_blank">
Proceed right here to see our outdone Anatrim arrangement!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.acialte.net/?watdruptzgyp</font>

</BODY></HTML>
------------821A05136EF6E80--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TIWIZ9019812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 11:32:18 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TIWISV019811; Fri, 29 Jun 2007 11:32:18 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.pingtel.com (hide.pingtel.com [65.220.123.2]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TIWGvj019795 for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 11:32:17 -0700 (MST) (envelope-from slawrence@pingtel.com)
Received: from [127.0.0.1] (pi.pingtel.com [10.1.1.12]) by mail.pingtel.com (Postfix) with ESMTP id 2480E6C02C; Fri, 29 Jun 2007 14:31:41 -0400 (EDT)
Subject: Re: [Sip] Certificate authentication in SIP
From: Scott Lawrence <slawrence@pingtel.com>
To: IETF SIP List <sip@ietf.org>, ietf-pkix@imc.org
In-Reply-To: <4685191E.4060903@alcatel-lucent.com>
References:  <9D18525F6EF33947BDEF23374EF26C7A06CDA1@stntexch11.cis.neustar.com> <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com> <4685191E.4060903@alcatel-lucent.com>
Content-Type: text/plain
Organization: Pingtel Corp.
Date: Fri, 29 Jun 2007 14:32:15 -0400
Message-Id: <1183141935.3646.30.camel@sukothai.pingtel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 
Content-Transfer-Encoding: 7bit
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>

On Fri, 2007-06-29 at 09:37 -0500, Vijay K. Gurbani wrote:
> Sumanth Channabasappa wrote:
> > And if we find that certificates need some work to support this
> > initiative (e.g., SIP identifiers as subjects), perhaps we can
> > present some of those requirements to other WGs. If we find an
> > existing solutions that can be used, good (and we can document them
> > as such :) ).
> 
> Scott Lawrence and I have spent some time on this issue, i.e.,
> SIP identifiers as subjects in X.509 certificates.  The latest
> version of the draft that includes pkix WG comments from Prague
> and the comments of the sip WG ADs and others was posted
> last week to the archives, and is available at
> http://tools.ietf.org/html/draft-gurbani-sip-domain-certs-05

One qualification - the draft above is limited to certificates as whose
subject is a SIP domain - not an individual.  The goal is to clarify how
such certificates are constructed and constrained, and how they should
be used to authenticate that a server is authoritative for a domain.

> Comments on this version would be extremely helpful.

-- 
Scott Lawrence  tel:+1-781-938-5306;ext=162 or sip:slawrence@pingtel.com
  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
  Chief Technology Officer    - Pingtel Corp. http://www.pingtel.com/



Received: from gip154.internetdsl.tpnet.pl (gip154.internetdsl.tpnet.pl [83.12.223.154]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5THe960013798; Fri, 29 Jun 2007 10:40:15 -0700 (MST) (envelope-from wyfsilmasum@silma.net)
Received: from [83.12.223.154] by mail.silma.net; Fri, 29 Jun 2007 17:40:26 -0100
Date: 	Fri, 29 Jun 2007 17:40:26 -0100
From: "Brittney Murray" <wyfsilmasum@silma.net>
X-Mailer: The Bat! (v2.01) Educational
Reply-To: wyfsilmasum@silma.net
X-Priority: 3 (Normal)
Message-ID: <583924749.77474199603835@silma.net>
To: ietf-pkix-approval@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------84090167CBD3AE1"

------------84090167CBD3AE1
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

LegalRXMedications chemist's acquaints you with all preparations you have a necessity in to renew your health at little price. 
We manage all over the planet with customers from Europe, America and Asia. 
At present time you got no need to seek out drug-store at your area.
We necessarily transfer high-quality drugs to the distant parts of the planet.
Come please to our site & obtain medications that you immediately need direct to your abode. 
http://bloodlike.hk/ 
We are ratified by VeriSign & VISA then we support secure and dependable acquisition.

------------84090167CBD3AE1
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> chemist's acquaints you with all preparations you have a necessity in to renew your health at little price. <br>
We manage all over the planet with customers from Europe, America and Asia. <br>
At present time you got no need to seek out drug-store at your area.<br>
We necessarily transfer high-quality drugs to the distant parts of the planet.
<br>
<br>
<a href="http://bloodlike.hk/" target="_blank"><em>Come please to our site & obtain medications that you immediately need direct to your abode.</em></a></b> 
<br>
<font color="#D9EDFF">http://bloodlike.hk/</font> 
<br><b>We are ratified by <font color="#FF0000"><em>VeriSign</em></font> & <font color="#FF0000"><em>VISA</em></font> then we support secure and dependable acquisition.
</b>

</BODY></HTML>
------------84090167CBD3AE1--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TGPmEq004910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 09:25:48 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TGPmwm004909; Fri, 29 Jun 2007 09:25:48 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [66.150.120.2]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l5TGPlut004902 for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 09:25:48 -0700 (MST) (envelope-from housley@vigilsec.com)
Message-Id: <200706291625.l5TGPlut004902@balder-227.proper.com>
Received: (qmail 11930 invoked by uid 0); 29 Jun 2007 16:25:42 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (71.241.252.247) by woodstock.binhost.com with SMTP; 29 Jun 2007 16:25:42 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 29 Jun 2007 12:22:17 -0400
To: "Denis Pinkas" <denis.pinkas@bull.net>, "pkix" <ietf-pkix@imc.org>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: PKI Disaster Recovery and Key Rollover
Cc: "Joel Kazin" <Joel_Kazin@jeffersonwells.com>
In-Reply-To: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
References: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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>

I do not know if we want to accept this document or not.  I have not 
read it yet.  However, if we do, I suggest that we select a file name 
without an ampersand in it.

Russ

At 10:52 AM 6/29/2007, Denis Pinkas wrote:

>To the WG,
>
>I edited together with Joel Kazin an individual Internet-Draft that 
>has been placed on the IETF web server.
>The target category is INFORMATIONAL.
>
>The abstract is the following:
>
>    This document presents a framework to assist the writers of policy
>    or practice statements and the designers of a Public Key
>    Infrastructure to prepare disaster recovery plans in case of a
>    private key-compromise or a private key-loss.  This may happen to
>    end-entity keys, Certification Authorities, Revocation Authorities,
>    Attribute Authorities, or Time-Stamping Authorities.  Since
>    certificates have finite validity, CA key-rollover should be
>    planned in advance.
>
>    In addition, denial of service attacks on Repositories holding
>    CRLs has also to be considered.
>
>    This framework provides a comprehensive list of potential key-
>    compromise or key-loss conditions that, in the opinion of the
>    authors, should be addressed so that it is possible to quickly
>    recover from exceptional situations.
>
>The document is available at:
>https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/
>
>I ask the WG to consider whether this document should be progressed
>as an individual contribution or as a PKIX WG document.
>
>I will not be present at the next meeting, but I plan to prepare a 
>few slides to present the draft.
>
>To this respect, I ask whether it would be possible to get a time 
>slot (5 minutes)
>at the next meeting.
>
>Denis



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TErFcJ093604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 07:53:15 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TErFP2093603; Fri, 29 Jun 2007 07:53:15 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from odin2.bull.net (odin2.bull.net [129.184.85.11]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TErDmL093594 for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:53:14 -0700 (MST) (envelope-from denis.pinkas@bull.net)
Received: from MSGA-001.frcl.bull.fr (msga-001.frcl.bull.fr [129.184.87.31]) by odin2.bull.net (8.9.3/8.9.3) with ESMTP id QAA49804; Fri, 29 Jun 2007 16:58:59 +0200
Received: from frcls4013 ([129.182.108.120]) by MSGA-001.frcl.bull.fr (Lotus Domino Release 5.0.11) with SMTP id 2007062916525916:110177 ; Fri, 29 Jun 2007 16:52:59 +0200 
Date: Fri, 29 Jun 2007 16:52:56 +0200
From: "Denis Pinkas" <denis.pinkas@bull.net>
To: "pkix" <ietf-pkix@imc.org>
Cc: "Joel Kazin" <Joel_Kazin@jeffersonwells.com>
Subject:  PKI Disaster Recovery and Key Rollover
X-mailer: Foxmail 5.0 [-fr-]
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on MSGA-001/FR/BULL(Release 5.0.11  |July 24, 2002) at 29/06/2007 16:52:59, Serialize by Router on MSGA-001/FR/BULL(Release 5.0.11  |July 24, 2002) at 29/06/2007 16:53:12, Serialize complete at 29/06/2007 16:53:12
Message-ID: <OF718A6529.C81A8459-ONC1257309.0051C15C@frcl.bull.fr>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="iso-8859-1"
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>

To the WG,

I edited together with Joel Kazin an individual Internet-Draft that has been placed on the IETF web server.
The target category is INFORMATIONAL.

The abstract is the following:

   This document presents a framework to assist the writers of policy 
   or practice statements and the designers of a Public Key 
   Infrastructure to prepare disaster recovery plans in case of a
   private key-compromise or a private key-loss.  This may happen to 
   end-entity keys, Certification Authorities, Revocation Authorities, 
   Attribute Authorities, or Time-Stamping Authorities.  Since 
   certificates have finite validity, CA key-rollover should be 
   planned in advance. 

   In addition, denial of service attacks on Repositories holding 
   CRLs has also to be considered.

   This framework provides a comprehensive list of potential key-
   compromise or key-loss conditions that, in the opinion of the 
   authors, should be addressed so that it is possible to quickly 
   recover from exceptional situations.

The document is available at:
https://datatracker.ietf.org/drafts/draft-pinkas-pkix-pki-dr&kr/

I ask the WG to consider whether this document should be progressed 
as an individual contribution or as a PKIX WG document.

I will not be present at the next meeting, but I plan to prepare a few slides to present the draft.

To this respect, I ask whether it would be possible to get a time slot (5 minutes) 
at the next meeting. 

Denis






Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEdqaG092535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 07:39:52 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEdq9M092534; Fri, 29 Jun 2007 07:39:52 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEdnIC092528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:39:51 -0700 (MST) (envelope-from vkg@alcatel-lucent.com)
Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id l5TEbfUo015741; Fri, 29 Jun 2007 09:37:46 -0500 (CDT)
Received: from [135.185.244.90] (il0015vkg1.ih.lucent.com [135.185.244.90]) by ihmail.ih.lucent.com (8.11.7p1+Sun/8.12.11) with ESMTP id l5TEbIa29362; Fri, 29 Jun 2007 09:37:18 -0500 (CDT)
Message-ID: <4685191E.4060903@alcatel-lucent.com>
Date: Fri, 29 Jun 2007 09:37:18 -0500
From: "Vijay K. Gurbani" <vkg@alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sumanth Channabasappa <sumanth@cablelabs.com>
CC: IETF SIP List <sip@ietf.org>, ietf-pkix@imc.org, Scott Lawrence <slawrence@pingtel.com>
Subject: Re: [Sip] Certificate authentication in SIP
References: <9D18525F6EF33947BDEF23374EF26C7A06CDA1@stntexch11.cis.neustar.com> <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C6016BA6@srvxchg3.cablelabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
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>

Sumanth Channabasappa wrote:
> And if we find that certificates need some work to support this
> initiative (e.g., SIP identifiers as subjects), perhaps we can
> present some of those requirements to other WGs. If we find an
> existing solutions that can be used, good (and we can document them
> as such :) ).

Scott Lawrence and I have spent some time on this issue, i.e.,
SIP identifiers as subjects in X.509 certificates.  The latest
version of the draft that includes pkix WG comments from Prague
and the comments of the sip WG ADs and others was posted
last week to the archives, and is available at
http://tools.ietf.org/html/draft-gurbani-sip-domain-certs-05

Comments on this version would be extremely helpful.

Thanks.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA)
Email: vkg@{alcatel-lucent.com,bell-labs.com,acm.org}
WWW:   http://www.alcatel-lucent.com/bell-labs



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEQB8F091344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 07:26:11 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEQBs3091343; Fri, 29 Jun 2007 07:26:11 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.181]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEQ9TK091336 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:26:10 -0700 (MST) (envelope-from stefans@microsoft.com)
Received: from DUB-EXHUB-C303.europe.corp.microsoft.com (65.53.213.93) by DUB-EXGWY-E802.partners.extranet.microsoft.com (10.251.129.2) with Microsoft SMTP Server (TLS) id 8.1.122.1; Fri, 29 Jun 2007 15:26:09 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by DUB-EXHUB-C303.europe.corp.microsoft.com ([65.53.213.93]) with mapi; Fri, 29 Jun 2007 15:26:08 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: pkix <ietf-pkix@imc.org>
Importance: high
Date: Fri, 29 Jun 2007 15:26:06 +0100
Subject: Call for agenda items for the CHicago PKIX meeting
Thread-Topic: Call for agenda items for the CHicago PKIX meeting
Thread-Index: Ace6WW5TLUaZoDk9Ts6QzrNPf9yx1g==
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6@EA-EXMSG-C307.europe.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_"
MIME-Version: 1.0
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>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

A number is issues has been brought to the list since last IETF meeting.

Please let me know if you have any topic you want to discuss during the PKI=
X meeting in Chicago.
As usual, I need at least one editor from each active document to send me a=
 note whether you want a time slot at the meeting beyond my general status =
report.

I need your request for agenda items before end of next week. I.e. Friday J=
uly 6.

Thank you.


Stefan Santesson
Senior Program Manager
Windows Security, Standards


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" 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:"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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</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=3DSV link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span lang=3DEN-US>All,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>A number is issues has been brought=
 to the
list since last IETF meeting.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>Please let me know if you have any =
topic
you want to discuss during the PKIX meeting in Chicago.<o:p></o:p></span></=
p>

<p class=3DMsoNormal><span lang=3DEN-US>As usual, I need at least one edito=
r from
each active document to send me a note whether you want a time slot at the
meeting beyond my general status report.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>I need your request for agenda item=
s before
end of next week. I.e. Friday July 6.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>Thank you.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:maroon'>Stefan Santesson</span></b><span lang=3D=
EN-GB
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F49=
7D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:#400040'>Senior Program Manager</span><span lang=3DEN-GB style=3D'fon=
t-size:
12.0pt;font-family:"Times New Roman","serif";color:navy'><o:p></o:p></span>=
</p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:#400040'>Windows Security, Standards</span></b><=
span
lang=3DEN-US style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C6EAEXMSGC307euro_--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEM5Dr091016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2007 07:22:05 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5TEM571091015; Fri, 29 Jun 2007 07:22:05 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp-dub.microsoft.com (smtp-dub.microsoft.com [213.199.138.181]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5TEM294091006 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <ietf-pkix@imc.org>; Fri, 29 Jun 2007 07:22:04 -0700 (MST) (envelope-from stefans@microsoft.com)
Received: from dub-exhub-c302.europe.corp.microsoft.com (65.53.213.92) by DUB-EXGWY-E802.partners.extranet.microsoft.com (10.251.129.2) with Microsoft SMTP Server (TLS) id 8.1.122.1; Fri, 29 Jun 2007 15:22:02 +0100
Received: from EA-EXMSG-C307.europe.corp.microsoft.com ([65.53.221.19]) by dub-exhub-c302.europe.corp.microsoft.com ([65.53.213.92]) with mapi; Fri, 29 Jun 2007 15:22:01 +0100
From: Stefan Santesson <stefans@microsoft.com>
To: pkix <ietf-pkix@imc.org>
Date: Fri, 29 Jun 2007 15:21:59 +0100
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gBN5Fi4A=
Message-ID: <A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3@EA-EXMSG-C307.europe.corp.microsoft.com>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com> <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_"
MIME-Version: 1.0
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>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Some general comments on the three short fixes after studying the debate.

1) Text Representation of Community Logos

I don't believe an update of the logotype RFC is motivated. If there is a n=
eed for a Community Attribute however is an open issue. The X.509 model is =
extensible and new attributes can be defined by anybody for any purpose.

2) Member Since attribute

This is the same as 1). If the e-commerce or other parts of any market need=
s a member since attribute. They could define one. The question for me is i=
f this belongs within PKIX.

3) No Padlock Icon attribute

The decision to display a padlock or anything else is an application issue,=
 under the application's control. No CA is authoritative over that decision=
 and as such, an attribute or extension aimed to control this seems as a ba=
d solution. I agree that this is better solved by negotiating TLS ciphersui=
tes rather than through certificate content. I may for example want to use =
the same certificate for both types of sessions.


Stefan Santesson
Senior Program Manager
Windows Security, Standards


--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-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:"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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Arial","sans-serif";
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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=3DSV link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><a name=3D"_MailEndCompose"><span lang=3DEN-US style=
=3D'font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Some general comme=
nts
on the three short fixes after studying the debate.<o:p></o:p></span></a></=
p>

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

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>1) Text Representation of Community Logos<o:p></o:p><=
/span></strong></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif";color:navy'><o:p>&nbsp;</o:p></span></strong></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:navy'>I don&#8217;t believe an update of the logotype RFC is motivate=
d.
If there is a need for a Community Attribute however is an open issue. The
X.509 model is extensible and new attributes can be defined by anybody for =
any purpose.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>2) Member Since attribute<o:p></o:p></span></strong><=
/p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'color:navy'><o:p>&nbsp;</o=
:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:navy'>This is the same as 1). If the e-commerce or other parts of any
market needs a member since attribute. They could define one. The question =
for
me is if this belongs within PKIX. <o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><strong><span lang=3DEN-US style=3D'font-size:10.0pt;f=
ont-family:
"Arial","sans-serif"'>3) No Padlock Icon attribute</span></strong><span
lang=3DEN-US><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'color:navy'><o:p>&nbsp;</o=
:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif";
color:#1F497D'>The decision to display a padlock or anything else is an
application issue, under the application&#8217;s control. No CA is authorit=
ative
over that decision and as such, an attribute or extension aimed to control =
this
seems as a bad solution. I agree that this is better solved by negotiating =
TLS
ciphersuites rather than through certificate content. I may for example wan=
t to
use the same certificate for both types of sessions.<o:p></o:p></span></p>

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

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

<div>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:maroon'>Stefan Santesson</span></b><span lang=3D=
EN-GB
style=3D'color:#1F497D'><o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-GB style=3D'font-size:10.0pt;font-fami=
ly:"Arial","sans-serif";
color:#400040'>Senior Program Manager</span><span lang=3DEN-GB style=3D'col=
or:navy'><o:p></o:p></span></p>

<p class=3DMsoNormal><b><span lang=3DEN-GB style=3D'font-size:10.0pt;font-f=
amily:
"Arial","sans-serif";color:#400040'>Windows Security, Standards</span></b><=
span
lang=3DEN-US style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>

</div>

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

</div>

</body>

</html>

--_000_A15AC0FBACD3464E95961F7C0BCD1FF0D14883C3EAEXMSGC307euro_--



Received: from mail.sgmlink.ru (selyatino.g2.ru [82.138.14.234]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5T7vJoX049264; Fri, 29 Jun 2007 00:57:20 -0700 (MST) (envelope-from wyfsilhouetteclothingsum@silhouetteclothing.com)
Received: from 205.178.149.7 (HELO INBOUND.SILHOUETTECLOTHING.COM.NETSOLMAIL.NET) by imc.org with esmtp ((+8.Z0;(.7( 4L(*0) id S7)7M)-+/VA5;-*N for ietf-vcard-request@imc.org; Fri, 29 Jun 2007 08:00:09 -0300
Date: 	Fri, 29 Jun 2007 08:00:09 -0300
From: "Lawrence Bender" <wyfsilhouetteclothingsum@silhouetteclothing.com>
X-Mailer: The Bat! (v2.10.01) Business
X-Priority: 3 (Normal)
Message-ID: <033090852.88100939720737@thhebat.net>
To: ietf-vcard-request@imc.org
Subject: Don't be inadequate anymore
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------5AF05AF2991CEDA"
X-Spam: Not detected

------------5AF05AF2991CEDA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable


Finally the true stuff =96 with no swindle! 
P.E.P. are very hot right now! This is the real stuff not an imitation! 

One of the very exceptionals, absolutely unequalled product is=20=
available anywhere!
 Take note of what people tell about this stuff:

"I was impressed how quickly P.E.P. worked on my boyfriend, he can not=20=
stop chatting on how excited he is with his new calibre, length, and=20=
libido!"

Rita R., Boston

"Firstly I thought the gratuitous specimen  I received was a mean=20=
trick, till I tried P.E.P. I can=92t describe report how highly satisfied=20=
I am with the consequence I got from using the patch for 7 short weeks. I=20=
will be requesting at every turn!" 
Mike Brown, Chicago

Look at more testimonies on this wonderful product right here and right=20=
now!
http://www.typefad.com/?cpvmbhmksabid
------------5AF05AF2991CEDA
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Last offer- Discount special for PE patch almost over</TITLE>
</HEAD>
<BODY>

<b>
Finally the true stuff =96 with no swindle! 
<br>
<a href=3D"http://www.typefad.com/?cpvmbhmksabid"=20=
target=3D"_blank">P.E.P.</a> are very hot right now! This is the real=20=
stuff not an imitation! 
<br>
One of the very exceptionals, absolutely unequalled product is=20=
available anywhere!
<br> Take note of what people tell about this stuff:
<p>
<i>
"I was impressed how quickly P.E.P. worked on my boyfriend, he can not=20=
stop chatting on how excited he is with his new calibre, length, and=20=
libido!"
</i>
</p>
Rita R., Boston
<p>
<i>
"Firstly I thought the gratuitous specimen  I received was a mean=20=
trick, till I tried P.E.P. I can=92t describe report how highly satisfied=20=
I am with the consequence I got from using the patch for 7 short weeks. I=20=
will be requesting at every turn!" </i>
</p>
Mike Brown, Chicago
<center>
<a href=3D"http://www.typefad.com/?cpvmbhmksabid" target=3D"_blank">
Look at more testimonies on this wonderful product right here and right=20=
now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.typefad.com/?cpvmbhmksabid</font>

</BODY></HTML>
------------5AF05AF2991CEDA--



Received: from embarqhsd.net (oh-76-5-254-47.dhcp.embarqhsd.net [76.5.254.47]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l5SLsJJw098398; Thu, 28 Jun 2007 14:54:26 -0700 (MST) (envelope-from ZW0rdg9@nypost.com)
Message-Id: <200706282154.l5SLsJJw098398@balder-227.proper.com>
Received: from localhost (localhost.localdomain [127.0.0.1]) by host24948495.nypost.com (8.13.1/8.13.1) with SMTP id Hib6Q3E627.177086.MMi.g0H.8991743915716 for <ietf-pkix-archive@imc.org>; Thu, 28 Jun 2007 17:54:05 +0500
Date: Thu, 28 Jun 2007 17:54:05 +0500
From: "Aida Stiles" <ZW0rdg9@nypost.com>
MIME-Version: 1.0
To: ietf-pkix-archive@imc.org
Cc: ietf-pkix-request@imc.org, ietf-pkix@imc.org, ietf-pkix@vpnc.org, ietf-pop3ext-request@imc.org
Subject: treacherous kremlin alarm;
MIME-Version: 1.0
Content-Type: text/plain;

Hello,

Visit our new online store and save.
http://www.dooragree.com/

All popular ones are available with free shipping worldwide with no need for any visits.

http://www.closebreak.com/

Dr. Josie Butcher


Received: from adsl0-ats42-p5.mts-nn.ru (adsl0-ats42-p5.mts-nn.ru [213.177.106.26] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5S7ZN7m013702; Thu, 28 Jun 2007 00:35:26 -0700 (MST) (envelope-from mihservicesexplorationgod@servicesexploration.com)
Received: from 142.217.192.32 (HELO mx1.servicesexploration.com) by imc.org with esmtp (I+9*<I(RZ5'V X<0989) id ;=*V9S-C67S8*-GA for ietf-openproxy@imc.org; Thu, 28 Jun 2007 07:35:29 -0300
Date: 	Thu, 28 Jun 2007 07:35:29 -0300
From: "Lenny Minor" <mihservicesexplorationgod@servicesexploration.com>
X-Mailer: The Bat! (v3.5) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <966485304.02332808187110@thhebat.net>
To: ietf-openproxy@imc.org
Subject: Doctors and Celebrities endorse Anatrim
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------DA29E821A29EFDA"
X-Spam: Not detected

------------DA29E821A29EFDA
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit



Make use of the chance! – Anatrim – The newest & most enchanting product for weighty people is now easily available – As you could see on Oprah

Do you recall all the situations when you said to yourself you would do anything for being delivered from this awful kilos of fat? Luckily, now no great price is to be paid. Thanks to Anatrim, the ground-breaking, you can get naturally health life style and a really slender figure. Simply notice what people say!
 
“I always had a tremendous life till last year my girlfriend told me I was corpulent and had need for being careful to my health. Life had changed the wrong way after that, till I found Anatrim ™ at once. Since getting rid of about 40 lbs thanks to Anatrim,  my private life has come back, better even than before. Many thanks for the coolest stuff and the first-class maintenance service. Go on your valuable work!”

 
Charley Mock, Boston

 
"Nothing feels better than slipping into a bikini I have not worn for a long period of time. Now I feel slender, defined, and sturdy, thanks to a great extent to Anatrim! Plenty of thanks to you!"

 
Amelia B., San Diego

Check out Anatrim, and  you'll join the worldwide company of thousands of delighted user who are enjoying the revolutionary results of Anatrim right here & right now. Less gorging madness, less lbs and more gladness in your life!

Proceed here to inspect our unbeatable Anatrim arrangements!!!
http://www.berezh.com/?qrbaklrlhhgol

------------DA29E821A29EFDA
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Stop being obese and unhappy</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href="http://www.berezh.com/?qrbaklrlhhgol" target="_blank">
Make use of the chance! – Anatrim – The newest & most enchanting product for weighty people is now easily available – As you could see on Oprah
</a>
</center>
<br>
Do you recall all the situations when you said to yourself you would do anything for being delivered from this awful kilos of fat? Luckily, now no great price is to be paid. Thanks to Anatrim, the ground-breaking, you can get naturally health life style and a really slender figure. Simply notice what people say!
 <br>
<br>
<i>
“I always had a tremendous life till last year my girlfriend told me I was corpulent and had need for being careful to my health. Life had changed the wrong way after that, till I found Anatrim ™ at once. Since getting rid of about 40 lbs thanks to Anatrim,  my private life has come back, better even than before. Many thanks for the coolest stuff and the first-class maintenance service. Go on your valuable work!”
</i>
 <br>
<b>
<i>
Charley Mock, Boston
</i>
</b>
 <br>
<br>
<i>
"Nothing feels better than slipping into a bikini I have not worn for a long period of time. Now I feel slender, defined, and sturdy, thanks to a great extent to Anatrim! Plenty of thanks to you!"
</i>
 <br>
<b>
<i>
Amelia B., San Diego
</i>
</b>
<br>
<br>
Check out Anatrim, and  you'll join the worldwide company of thousands of delighted user who are enjoying the revolutionary results of Anatrim right here & right now. Less gorging madness, less lbs and more gladness in your life!
<br>
<br>
<center>
<a href="http://www.berezh.com/?qrbaklrlhhgol" target="_blank">
Proceed here to inspect our unbeatable Anatrim arrangements!!!
</a>
</center>
</b>
</p>
<font color="#D9EDFF">http://www.berezh.com/?qrbaklrlhhgol</font>

</BODY></HTML>
------------DA29E821A29EFDA--



Received: from f048068167.adsl.alicedsl.de (f048068167.adsl.alicedsl.de [78.48.68.167]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l5RLLFl4062976; Wed, 27 Jun 2007 14:21:17 -0700 (MST) (envelope-from countdown@we-help-u.biz)
Date: Thu, 28 Jun 2007 04:19:31 +0600
From: "Jean Hawkins" <countdown@we-help-u.biz>
Message-ID: <05381037.24294555@dialect.com>
To: press@imc.org
Subject: Don't afraid of your wishes.
MIME-Version: 1.0
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY bgcolor=#FFFFFF leftmargin=5 topmargin=5 rightmargin=5 bottommargin=5>
<FONT size=2 color=#000000 face="Arial">
<DIV align=center>
<FONT size=6 color=#800000 face="Blue Highway Condensed">Your wished will come true with our new super offer.</FONT></DIV>
<DIV align=center>
<FONT size=6 color=#800000 face="Blue Highway Condensed">You'll cann't refuse from it.</FONT></DIV>
<DIV align=center>
<FONT size=5 color=#FF0000 face="Kristen ITC">Only today for you!</FONT></DIV>
<DIV align=center>
<FONT size=6 color=#0000FF face="Blue Highway">Viagra+Tadalafil&nbsp; (super \/iagra) have the lowest price.</FONT></DIV>
<DIV align=center>
<FONT size=6 color=#FF0000 face="Boopee"><B>+Viagra FREE of charge.</B></FONT></DIV>
<DIV align=center>
<FONT size=6 color=#0000FF face="Blue Highway">Of course there areSoma,\/iagra soft tabs and another preparations.</FONT></DIV>
<DIV align=center>
<FONT size=7 color=#800000 face="Blue Highway Condensed">You'll save over 85%.</FONT></DIV>
<DIV align=center>
<FONT size=3 face="Tw Cen MT"><B>We have real quality on astonishing price.</B></FONT></DIV>
<DIV align=center>
<FONT size=3 face="Tw Cen MT"><B>It approved by time and our customers.</B></FONT></DIV>
<DIV align=center>
<FONT size=3 face="Tw Cen MT"><B>Don't diddle your time for search the better.</B></FONT></DIV>
<DIV align=center>
<FONT size=3 face="Tw Cen MT"><B>&nbsp;</B></FONT></DIV>
<DIV align=center>
<FONT size=3 color=#FF0000 face="Kristen ITC"><B>We have the best on the East and the West. </B></FONT></DIV>
<DIV align=center>
<FONT size=3 color=#FF0000 face="Kristen ITC"><B>&nbsp;</B></FONT></DIV>
<DIV align=center>
<FONT color=#000000 face="Microsoft JhengHei"><B><U>http://etbapct.happyeven.hk/?622480915935</B></U></FONT></DIV>
<DIV align=center>
<FONT size=3 face="Kristen ITC"> </FONT></DIV>
<DIV>
&nbsp;</DIV>
</FONT>
</BODY></HTML>




Received: from pc52.ziebice.silesianet.pl (pc52.ziebice.silesianet.pl [80.48.206.52]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5RBEO4m095685; Wed, 27 Jun 2007 04:14:26 -0700 (MST) (envelope-from jursanwinintdet@sanwinint.com)
Received: from [80.48.206.52] by barracuda.ayayai.com; Wed, 27 Jun 2007 11:14:32 -0100
Date: 	Wed, 27 Jun 2007 11:14:32 -0100
From: "Silvia Talbot" <jursanwinintdet@sanwinint.com>
X-Mailer: The Bat! (v3.51) Educational
Reply-To: jursanwinintdet@sanwinint.com
X-Priority: 3 (Normal)
Message-ID: <792428151.43253851534157@sanwinint.com>
To: ietf-mmms-request@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------84092CB67CBD33A"

------------84092CB67CBD33A
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

LegalRXMedications pharmacy acquaints you with all medicinal agents that you feel need in in order to recover your health for a little price. 
We operate all over the globe with buyers from Europe, America, and Asia. 
At the time you don't have to search for drug shop somewhere at your local area.
We necessarily transfer the best quality pharmas to all parts of the planet.
Visit our site & get drugs that you require instantly straightly to your lodging. 
http://portside.hk/ 
We are verified by VISA & VeriSign so then we support effective and trustworthy buying.

------------84092CB67CBD33A
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> pharmacy acquaints you with all medicinal agents that you feel need in in order to recover your health for a little price. <br>
We operate all over the globe with buyers from Europe, America, and Asia. <br>
At the time you don't have to search for drug shop somewhere at your local area.<br>
We necessarily transfer the best quality pharmas to all parts of the planet.
<br>
<br>
<a href="http://portside.hk/" target="_blank"><em>Visit our site & get drugs that you require instantly straightly to your lodging.</em></a></b> 
<br>
<font color="#D9EDFF">http://portside.hk/</font> 
<br><b>We are verified by <font color="#FF0000"><em>VISA</em></font> & <font color="#FF0000"><em>VeriSign</em></font> so then we support effective and trustworthy buying.
</b>

</BODY></HTML>
------------84092CB67CBD33A--



Received: from 89-109-46-71.dynamic.mts-nn.ru (89-109-46-71.dynamic.mts-nn.ru [89.109.46.71]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5RAA35V087596; Wed, 27 Jun 2007 03:10:09 -0700 (MST) (envelope-from sogsccdwhur@sccdw.de)
Received: from 212.227.15.150 (HELO mx01.schlund.de) by imc.org with esmtp (/<J<H*-/E* 60)*) id 0>CN4O-CM>32+-)* for ietf-pkix-oid-reg@imc.org; Wed, 27 Jun 2007 10:10:10 -0300
Date: 	Wed, 27 Jun 2007 10:10:10 -0300
From: "Millicent Mckay" <sogsccdwhur@sccdw.de>
X-Mailer: The Bat! (v3.80.03) Educational
X-Priority: 3 (Normal)
Message-ID: <101420212.50739417674871@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Get your ideal weight with this natural method
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------ABB486E295E2111"
X-Spam: Not detected

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


Don't miss the opportunity! =96 Anatrim =96 The very up-to-date & most=20=
fascinating flesh loss product available =96 As were told on Oprah

Can you recall all the cases when you plead to yourself to do any thing=20=
for being saved from this frightful kilos of fat? Luckily, now no great=20=
price is to be paid. Thanks to Anatrim, the earth-shaking, you can=20=
achieve healthier life style and become really slimmer. Have a look at=20=
what our clients say!
 
=93I always had a terrific private life till a year back the girl I was=20=
meeting said to me I was corpulent and needed to begin being careful to=20=
my health. Life was never the same after that, until I discovered Anatrim=20=
=99. After getting rid of about 20 kilogrames only thanks to Anatrim,  my=20=
private life=92s come back, even much better than before. Great thanks to=20=
you for the astonishing stuff & the great maintenance service. Proceed=20=
with the good business!=94

 
Steve Burbon, Bellevue WA

 
"Nothing to compare with slipping into a bikini that I have not been=20=
dressed in for many long years. I feel slender, steadfast, and sturdy,=20=
thanks in great part to Anatrim! Plenty of thanks to you!"

 
Victoria K., Boston

Check out Anatrim, and  you'll add yourself to the worldwide=20=
association of thousands of happy customers who are enjoying the=20=
revolutionary effects of Anatrim here and now. Less devouring madness,=20=
less lbs and more mirth in your life!

Click here to look through our outdone Anatrim arrangement!!!
http://www.betiro.com/?hxfckthwafuz

------------ABB486E295E2111
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Shed weight now and enjoy the process</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.betiro.com/?hxfckthwafuz" target=3D"_blank">
Don't miss the opportunity! =96 Anatrim =96 The very up-to-date & most=20=
fascinating flesh loss product available =96 As were told on Oprah
</a>
</center>
<br>
Can you recall all the cases when you plead to yourself to do any thing=20=
for being saved from this frightful kilos of fat? Luckily, now no great=20=
price is to be paid. Thanks to Anatrim, the earth-shaking, you can=20=
achieve healthier life style and become really slimmer. Have a look at=20=
what our clients say!
 <br>
<br>
<i>
=93I always had a terrific private life till a year back the girl I was=20=
meeting said to me I was corpulent and needed to begin being careful to=20=
my health. Life was never the same after that, until I discovered Anatrim=20=
=99. After getting rid of about 20 kilogrames only thanks to Anatrim,  my=20=
private life=92s come back, even much better than before. Great thanks to=20=
you for the astonishing stuff & the great maintenance service. Proceed=20=
with the good business!=94
</i>
 <br>
<b>
<i>
Steve Burbon, Bellevue WA
</i>
</b>
 <br>
<br>
<i>
"Nothing to compare with slipping into a bikini that I have not been=20=
dressed in for many long years. I feel slender, steadfast, and sturdy,=20=
thanks in great part to Anatrim! Plenty of thanks to you!"
</i>
 <br>
<b>
<i>
Victoria K., Boston
</i>
</b>
<br>
<br>
Check out Anatrim, and  you'll add yourself to the worldwide=20=
association of thousands of happy customers who are enjoying the=20=
revolutionary effects of Anatrim here and now. Less devouring madness,=20=
less lbs and more mirth in your life!
<br>
<br>
<center>
<a href=3D"http://www.betiro.com/?hxfckthwafuz" target=3D"_blank">
Click here to look through our outdone Anatrim arrangement!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.betiro.com/?hxfckthwafuz</font>

</BODY></HTML>
------------ABB486E295E2111--



Received: from 89-109-46-71.dynamic.mts-nn.ru (89-109-46-71.dynamic.mts-nn.ru [89.109.46.71]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5RACDbD088136; Wed, 27 Jun 2007 03:12:14 -0700 (MST) (envelope-from sogschoofonlinehur@schoofonline.de)
Received: from 213.191.73.2 (HELO webmail.hansenet.de) by imc.org with esmtp (AHX2G-70 >3D2) id ,2A>P+-6ZKGU<-.+ for ietf-pkix-oid-reg@imc.org; Wed, 27 Jun 2007 10:12:15 -0300
Date: 	Wed, 27 Jun 2007 10:12:15 -0300
From: "Otto Hand" <sogschoofonlinehur@schoofonline.de>
X-Mailer: The Bat! (v3.51.10) Home
X-Priority: 3 (Normal)
Message-ID: <549862942.09782929931999@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Become fit and happy again
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------6E1D33A7CBDAE92C"
X-Spam: Not detected

------------6E1D33A7CBDAE92C
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Do not miss your chance! =96 Anatrim =96 The very up-to-date & most=20=
delighting lose flesh product is made available now =96 As seen on Oprah

Do you recall all the cases when you appeal to yourself to do anything=20=
for being saved from this awful number of pounds? Luckily, now no great=20=
offering is demanded. With Anatrim, the earth-shaking, you can get=20=
naturally health lifestyle and become really thinner. Just look at what=20=
our clients state!
 
=93I had always led a marvelous life till a year ago my girl said to me=20=
I was stout and in great want of being careful to my health. Life had=20=
abruptly changed after that, until I disclosed Anatrim =99 at once. Since=20=
loosing about 40 lbs only thanks to Anatrim,  my private life is back on=20=
track, notoriously better even than before. Greatest thanks for the=20=
coolest stuff & the first-rate maintenance service. Keep on the valuable=20=
action!=94

 
Charley Mock, Bellevue WA

 
"Nothing to compare with sliding into a bikini that I haven't worn for=20=
many years. I feel slender, steadfast, and healthy, thanks to a=20=
considerable degree to Anatrim! Great deal of thank you!"

 
Lusia R., Bellevue WA

Check out Anatrim, and  you shall join the world-wide community of=20=
thousands of pleased user who are getting pleasure out of the=20=
revolutionary results of Anatrim here and now. Less swallowing mania,=20=
less lbs and more gladness in life!

Click right here to gaze at our outdone Anatrim deal!!!
http://www.betiro.com/?hxfckthwafuz

------------6E1D33A7CBDAE92C
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Losing weight has never been so easy</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.betiro.com/?hxfckthwafuz" target=3D"_blank">
Do not miss your chance! =96 Anatrim =96 The very up-to-date & most=20=
delighting lose flesh product is made available now =96 As seen on Oprah
</a>
</center>
<br>
Do you recall all the cases when you appeal to yourself to do anything=20=
for being saved from this awful number of pounds? Luckily, now no great=20=
offering is demanded. With Anatrim, the earth-shaking, you can get=20=
naturally health lifestyle and become really thinner. Just look at what=20=
our clients state!
 <br>
<br>
<i>
=93I had always led a marvelous life till a year ago my girl said to me=20=
I was stout and in great want of being careful to my health. Life had=20=
abruptly changed after that, until I disclosed Anatrim =99 at once. Since=20=
loosing about 40 lbs only thanks to Anatrim,  my private life is back on=20=
track, notoriously better even than before. Greatest thanks for the=20=
coolest stuff & the first-rate maintenance service. Keep on the valuable=20=
action!=94
</i>
 <br>
<b>
<i>
Charley Mock, Bellevue WA
</i>
</b>
 <br>
<br>
<i>
"Nothing to compare with sliding into a bikini that I haven't worn for=20=
many years. I feel slender, steadfast, and healthy, thanks to a=20=
considerable degree to Anatrim! Great deal of thank you!"
</i>
 <br>
<b>
<i>
Lusia R., Bellevue WA
</i>
</b>
<br>
<br>
Check out Anatrim, and  you shall join the world-wide community of=20=
thousands of pleased user who are getting pleasure out of the=20=
revolutionary results of Anatrim here and now. Less swallowing mania,=20=
less lbs and more gladness in life!
<br>
<br>
<center>
<a href=3D"http://www.betiro.com/?hxfckthwafuz" target=3D"_blank">
Click right here to gaze at our outdone Anatrim deal!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.betiro.com/?hxfckthwafuz</font>

</BODY></HTML>
------------6E1D33A7CBDAE92C--



Received: from switch.plk.vectranet.pl (switch.plk.vectranet.pl [212.244.79.117] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5QJRKnC001458; Tue, 26 Jun 2007 12:27:24 -0700 (MST) (envelope-from tegsaatchieggiq@saatchieg.com)
Received: from [212.244.79.117] by mxrelay2.grexnetdns.com; Tue, 26 Jun 2007 19:27:30 -0100
Date: 	Tue, 26 Jun 2007 19:27:30 -0100
From: "Maggie Bryant" <tegsaatchieggiq@saatchieg.com>
X-Mailer: The Bat! (v2.00.2) Business
Reply-To: tegsaatchieggiq@saatchieg.com
X-Priority: 3 (Normal)
Message-ID: <200315224.61498234377658@saatchieg.com>
To: ietf-openproxy@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------2991534F0534F2"

------------2991534F0534F2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

LegalRXMedications drugstore acquaints you with all medicinal preparations you feel need in in order to restore your health for a little price. 
We work across the whole planet with buyers from Europe, America and Asia. 
At present you got no need to look for drug-shop at your local area.
We can deliver high-quality tablets to the remotest parts of the planet.
Visit our site to acquire pharmas you instantly require direct to your home. 
http://statehome.hk/ 
We are confirmed by VISA & VeriSign accordingly we support safe and reliable purchasing.

------------2991534F0534F2
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drugstore acquaints you with all medicinal preparations you feel need in in order to restore your health for a little price. <br>
We work across the whole planet with buyers from Europe, America and Asia. <br>
At present you got no need to look for drug-shop at your local area.<br>
We can deliver high-quality tablets to the remotest parts of the planet.
<br>
<br>
<a href="http://statehome.hk/" target="_blank"><em>Visit our site to acquire pharmas you instantly require direct to your home.</em></a></b> 
<br>
<font color="#D9EDFF">http://statehome.hk/</font> 
<br><b>We are confirmed by <font color="#FF0000"><em>VISA</em></font> & <font color="#FF0000"><em>VeriSign</em></font> accordingly we support safe and reliable purchasing.
</b>

</BODY></HTML>
------------2991534F0534F2--



Received: from user-387o4ei.cable.mindspring.com (user-387o4ei.cable.mindspring.com [208.124.17.210]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5QGGWWN051097; Tue, 26 Jun 2007 09:16:37 -0700 (MST) (envelope-from tegsabarigirischoolgiq@sabarigirischool.com)
Received: from 64.34.173.90 (HELO mail.sabarigirischool.com) by imc.org with esmtp (85H>E-5-.= ;=19) id V5YD</-BK4SH5-+5 for owner-ietf-imapext@imc.org; Tue, 26 Jun 2007 16:16:35 +0600
Date: 	Tue, 26 Jun 2007 16:16:35 +0600
From: "Jane Kilgore" <tegsabarigirischoolgiq@sabarigirischool.com>
X-Mailer: The Bat! (v3.60.07) Home
X-Priority: 3 (Normal)
Message-ID: <657317338.54641966125290@thhebat.net>
To: owner-ietf-imapext@imc.org
Subject: Customers alert, new pharma site is realised!
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------842C8BDAA3E5BD"
X-Spam: Not detected

------------842C8BDAA3E5BD
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

After all new I-net web-site is realized!!! 
 Mankind=92s health
Anti-Depressants
Pain relief
Women's Health
Anti-Diabetics
High Blood pressure/Cholesterol problems
Anti-allergic/Asthma medicinal remedies
Anti Intragastric Acidity
As our respective buyers now you can first test our lovely offer!! 
 FDA, CPA Tested, Visa Approved. 
Check this out right now!!!  
http://restelf.com/

------------842C8BDAA3E5BD
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Customers alert, new pharma site is realised!</TITLE>
</HEAD>
<BODY>

<b><font color=3D"#FF0000"><em><p>After all new I-net web-site is=20=
realized!!! </p></em></font>
 <li>Mankind=92s health
<li>Anti-Depressants
<li>Pain relief
<li>Women's Health
<li>Anti-Diabetics
<li>High Blood pressure/Cholesterol problems
<li>Anti-allergic/Asthma medicinal remedies
<li>Anti Intragastric Acidity
<br>
<font color=3D"#09B00D">As our respective buyers now you can first test=20=
our lovely offer!! </font><br>
 <font color=3D"#FF0000"><em>FDA, CPA Tested, Visa Approved.</em></font> 
<p>
<a href=3D"http://restelf.com/" target=3D"_blank">Check this out right=20=
now!!! </a></p>
</b> 
<p><font color=3D"#D9EDFF">http://restelf.com/</font></p>

</BODY></HTML>
------------842C8BDAA3E5BD--



Received: from [151.77.158.36] ([151.77.158.36]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5Q6k7DO059051 for <ietf-pkix-archive@imc.org>; Mon, 25 Jun 2007 23:46:09 -0700 (MST) (envelope-from Christan.hammond@ALPATOV.RU)
Message-Id: <200706260646.l5Q6k7DO059051@balder-227.proper.com>
Received: from [198.111.160.168] by [151.77.158.36] with HTTP; Tue, 26 Jun 2007 08:46:30 +0200
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Jun 2007 08:46:10 +0200
To: ietf-pkix-archive@imc.org
From: "Christan hammond" <Christan.hammond@ALPATOV.RU>
Subject: Then this little baby grows up big, an' you find another'n.
Mime-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="=====================_520171==.REL"

--=====================_520171==.REL
Content-Type: multipart/alternative;
	boundary="=====================_520171==.ALT"

--=====================_520171==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed


[]

The display context is a special device context that treats each 
window as a separate display surface. Sweat soaked through the shirt 
immediately and began making dark patches on the coat.
CPP(35) - fixes bug 3845. So shall you quietly enjoy your hope And 
marry sweet Bianca with consent.
The mbstowcs function converts a string of multibyte characters to a 
wide character array. CPP The main implementation file for FRESERVE.
You can even look up an ICOM authorized dealer near you. CPP - 
partial fix for bug 4728 If DoFileSave fails because disk is full, 
don't clear the image.
Cabanas virus uses this method. CTRL+OPT+M yet again takes you to the 
Netscape Fish Cam.
Baron Jukaga lunged forward, grabbing at the commander's holster and 
pulled out his pistol. Now it is directly on a line with the blue 
cupola of the theatre where an imposing general is holding a war 
council against the insurgents.
But he's a mysterious, superior being--that's what makes it so 
interesting. But their stroke was too late.
Then this little baby grows up big, an' you find another'n. CONCHITA 
But will they love me.
CW is permitted on all frequencies but is exclusive where shown. 
CPP(40) - fixes bug 5818.
Cache items with this priority level are the most likely to be 
deleted from the cache as the server frees system memory. CPP - Fix 
conflict with scanto file of the same name.
CSurrogate class implementation (ISurrogate). Initializes an instance 
of the class using an object that maps one type to another.
Or it's not, really. CPP 31 31 The files were just checked in over 
the old files.
--=====================_520171==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
<a href="http://inventstand.hk/">
<img src="cid:7.1.0.9.2.20070626084610.001464e8@ALPATOV.RU.0" width=320 height=332 alt="[]">
</a>
<br>
The display context is a special device context that treats each<br>
window as a separate display surface. Sweat soaked through the shirt<br>
immediately and began making dark patches on the coat.<br>
CPP(35) - fixes bug 3845. So shall you quietly enjoy your hope And<br>
marry sweet Bianca with consent.<br>
The mbstowcs function converts a string of multibyte characters to a<br>
wide character array. CPP The main implementation file for FRESERVE.<br>
You can even look up an ICOM authorized dealer near you. CPP -<br>
partial fix for bug 4728 If DoFileSave fails because disk is full,<br>
don't clear the image.<br>
Cabanas virus uses this method. CTRL+OPT+M yet again takes you to the<br>
Netscape Fish Cam.<br>
Baron Jukaga lunged forward, grabbing at the commander's holster and<br>
pulled out his pistol. Now it is directly on a line with the blue<br>
cupola of the theatre where an imposing general is holding a war<br>
council against the insurgents.<br>
But he's a mysterious, superior being--that's what makes it so<br>
interesting. But their stroke was too late.<br>
Then this little baby grows up big, an' you find another'n. CONCHITA<br>
But will they love me.<br>
CW is permitted on all frequencies but is exclusive where shown.<br>
CPP(40) - fixes bug 5818.<br>
Cache items with this priority level are the most likely to be<br>
deleted from the cache as the server frees system memory. CPP - Fix<br>
conflict with scanto file of the same name.<br>
CSurrogate class implementation (ISurrogate). Initializes an instance<br>
of the class using an object that maps one type to another.<br>
Or it's not, really. CPP 31 31 The files were just checked in over<br>
the old files.</body>
</html>

--=====================_520171==.ALT--

--=====================_520171==.REL
Content-Type: image/jpeg; name="Rights.jpg";
 x-mac-type="4A504766"; x-mac-creator="4A565752"
Content-ID: <7.1.0.9.2.20070626084610.001464e8@ALPATOV.RU.0>
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="Rights.jpg"

R0lGODlhQAFMAYcHAAAIC40AAACMAIeHAAAAhXcAhgh/g8fHw7HQxZ3O/DkuAmklAHErAKImALgR
ANUUAAA4ABhAAEFMAFtGAHpDAKMzALJKAOtEAwBSACFUAEpsAFZfDHRtAJZaAL9TAuVfCwiHBxmB
AEaCA2h/Ao2HBaxyAMp7BduLAgCRABytADOmAGeaDnupCKatBsWtAOGbAAi6ABPFAknJBFzDCIG7
AJnHALG4ANLHCQDeACnjBkbXAG7ZAoPZB5nYAMjcANjgBgAFTBcFNzYAN1UDRX8AQJwETc0ANukG
SwooOiMVMT4ZRF0oR3MYM5IhOr4bPe0kQQBKTSc3NTY0Nl9JNYNIMZg+QLdDSOdNQwBRPC5jR0xq
Q1hePYZSAK5RTrVUOO1YMwqHQR10M0t1RGZ0MoiBN59/RL6KR+1+Nw6YOyucMTuXRWmsQn+YPJmW
OsWbPNieRQnARSXDMUqxQWXJNo7IPZixP7a6PtHCOgXXORLdTT3qQ1nkOITRMZXUNbfSRNXjSAAA
jSUHiTIAhlgAgoINdJsAe8MJfuIAcgAtfColejMhcVMkg3cpjJEnhM4nd+gehwAxgx1Di0RFe2lB
eo1EcptMdr5IiupHcwBWiyRZdTtheWJfjnJsiqBYjbRejuRkcQ12eSmJf0eMelGBh3yNiJ91ecd3
hNt7hgSTiCSudjahd2KrcXutgaOYir+qiNmmeQ67iCPAgDnOfFm/gYe0iK24hsTEi9e6jADmghHb
gTTmdmrkg4zfe6LXdL/XiOboeQsAyyYAzkcAwlYMxYMAsqUEzbgAtu4GuwcjuS4Uujwpv2ogs3wh
spcnuMsix9IetwJFti1LwTVHwFlDwIE/zKdGvLw+ydFNwgBctCtizD1Zw1JqtoNZyqdtscFpvdFj
vQKNzRt8tUR5xl+BzIFxzpOIzr6HuNSAzQCWuhapzEmZxGShtXSezK2jy7qfyOWXyAC9yhbFwj/A
ymW/u3q7yqnFxfb/6ZORq3p9jP8NAAD/APb/CQAO/fUD/wz3+P/x/yH5BABgp70ALAAAAABAAUwB
Bwj/AA8IHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuX
MGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGjSJMqXcq0qdOnUKNKnUq1qtWrSvPlY6kVq9eYWsNu
PdlVYNmNYsMOPPu1bcq0ak2eZZsRblm6bvOKjLuW7FiQbNXi1Uu442C/e/+a3Xq4sGOLjQ/AJdhV
LOW0Be2uHTt5s2S+B+lWZgy68+LPpFFz5mt6813FkR+/jKx5senaqi2fzj0Xt0HRpG8Lt2y3Nm7N
cWPLdqncs23nv/8Glq4YOuvql7Ojhp6ZOuze1EOH/+/7efdym7GFa7edvHpv19fXR+88/bLu8vLr
s3+NkP959NjZd59+vK3WnXPHfZdQawQmeCB3r2GG33yS/XdTY/GZh1+GwHmW4YQgPhiddh92CGFw
CAbInoUXqtiggiD6Z11qM8on4o0yTmiihqORqKJqLALono7vpejac0iWB96JC7oI45IaxqgglKUd
GaSQmBXHZIHeSaikg9zdmN9q6o2ZnZb7EXglTcPRKCV8Uva4G3HjRWnjlkAWieeGgn0HWohrBupY
c4IWahWhhiYaFaKKNroUo45GKumklFZq6aWYUhpApopuuilBnxYUwKgJhaqRqaCOiqpBn67akKqk
cv/kKqcweTqQqgjNKpCuFLlqKq+8MvSrrLTSBGusu+aaLK4HwNoss57ayuyzsTp7K6vNUnttttGG
ai2oonJr67bH7lotrtZGay6yxXo0LrgHteptstlei+y99dK76r7PkrvsvMPCa++89oJLcKsGE0xv
ux29uy22+daLcMEPcwsvv+EGjPCwAVdsccUOO6yvwQJHzDBGx6I668QjU4tuyd1CCzHJ/n7877cL
LwtzxPIeTPO60558qslEt9wyxjmLnPPSNkusM8XK/szz1BcnTbXQ7ha9stVOQz21xvFWXXPIV3Pd
ManevjsxxztjnZHI5aZKtrkuc61v0OwCDfLIGgf/DbTC60qMduC3xrw0zm4n3qvijNfa+OMoIQ75
5JRXbvnlmGeu+eacd+7556CHLvropJdu+umop6766qy37vrrsMcu++y012777bjnrvvuvPfu++/A
By/88MQXb/zxyNcEAMM33ECR8w4tH6g++ghE/QHXgyT9QNsXBMD3BIG/E/QHOE8+Rs03fxD55wuU
vvoGta9Q9993z7349Ys/VfbZh5S/QPoLH/cA6BP2cUR+BTHg+hKCwIP8b3v2g+AB7EcV/lXPgv2j
ngaxt0EO9m+AEXQgCH9iQOilbyDvK58Kywc/FMYPfic8YQIJIsMUuq+FE8yhQUJIQApWsIMf5KAQ
/4XYQYIEcXk83CH+6tcT87lvhiWUX/tq6EIFxm+BJRQhBbcIQiZaRYPVGyIYLxjG631wjEqknwh7
OMDxrdCEMawiDWV4xSw+cYEojOMTcXg/Ne6wjYDcHxDJaD1CEjGMYkSkACX4RzYS0I0mXKEK7SjJ
Bjpxjy7EYyU3ecM/Ss+HOgzlI6uSQUOasYyGTKQWA/nJEY5ylIwMZSxnCUhaXhGTuJxkJiUJRTne
8ZabtCIv2chFWRrzi4jEoDJT6cEjenGC+oNgNAMIy1pas5rYPKYodwlHGOrxhji0IQsjmUdgjtN8
NeTj/6DpRWm6c01BjN55GpgTUFIKjBSxp1fo+P8TfSbvnwCFXT8w0o+BTsSgDfGnTfjBD4goVHMF
LegBEEqQgVLUIBG9qEAQqtGManSiD6EfNQE4zYc2hKEoPQBDEbLSlTJEpKAsqeI+itGF0HQgHEXI
TW/qPSbGspo/pYhLT9rQ6Pk0kK8Mars6ulGJgtSgEa0oRp0a1agWhKJWzShOnepI73n1lduUyFAH
4lKUFrWlZ03pIteIVKUWi6lStShID5JVnM71rlel613l6smeNlKWJlXIWAUyWLSqtKGDdaUAe4o/
pC61phOt6lN5yten2lWvW5VoTrkavpFu8ZlgFWtRCVJWsx72tGpN42K/qsN1Co2pm90rTStLW53/
XtayG91qX1f719BGJLGGRS1iR5vatYY1m759a15ji1Xbxja3mN2rdG87QkbyMKi2DGthh0tY7o41
sTlEYiN/GlhLaRWqkrUoZyPL1brqNq+ZVS9V1+vaZ0qzs8XUpg/Nyt3DptSwpmXsJ9f5TpIG1KFT
Ke+BK6JgoTR4wRCOsIQrYoADVHghD7ZKhhN3YQt7WCMGCPFBKtzhhMDUgQHcMEbKK96InFjAbuVU
h0u8ERoLhMQYPipYraviizRYwQ90bBtHSqsZfzjEM0ayhy+s5BHfWMRL/rCUw8vWv/bYIhFsLDHB
12LQUrm3vL2yoHA85Sjf2MI2trGZo0zmKbeY/7edhTNK/PhlKt+XtXUWclLdRmYmK9nIJUaymkks
aDO3uY9yZq2Y84nfxraSvF4GrT2TeLI+S7nNmB7IoMtsaTV3+aV6LgmdXfnm7JJ6fniutKYvzWoj
n9kgmc70Kotp6mvq19bYXS0ts8vFN9s61DJeNZqhXOhAN/nJSWYyqwVM0nYiutlWxrW0d9zOFA/Z
165l54CdTe1FY0rNFwH3cR/j7codmyPiLndT1D3hdrv7d+wuyj04Em+GZRvLqX42sHcy74HM+98a
eXGjY2zvjhDYh7Osd0n6LRCAMxzLOh53axXOos9uG5r67mpyhyxxnjzc4fdweMNDPvJ/P7zOMf8e
deK4/eVWhnmb+nQ5xUfy8QMAfOQGuXm/H15qPauccT2XebOz/PNa3vsnNb+5zQkScpLvvOGMRW5b
KRf0R/bcqymvclCSvnSoe33pT+/6Wt1K6cZVvbXaVKwfYxrtbPJ62rfGJtcZTnd/dz3sY+d4aGf+
n/pqWeaStm80h/7zt7sd7obXZtPD7nSmN/3uX9e2vrFL5NPx3S2XB13mv7L5d3v+85/vvPYwjOp6
EmYTqEc9QzbhENaPROB+1Xa8i57oMLNcnox2cb5frhTXr771r494fne/4trvm86+TuhJDm7iOyfF
9wdI/UCkL/3oq14g1L9+9Vnv+u1X3/rQz/P/1LW+kbU7WvLQFqUE/b7ti7Nzy0h8tOBDWHbFdjwo
vs9/9Amif+zvf/oA6H/aB4D6138ah3HMZnw+lj9B53Iwp35qZ0zrZ01/R0wRaH/H5YD3BxT5l3rc
Z4AFCIIe+H8kyH0EOIL4BWa1Rm+LFGTY5IJDB1QwWGozaHUoJ3tRJ2QMuG8cGIAFoXogOH0m6H/8
54NDuH/hh3WptoLlZ1zSNoHjJ35Q+IA2aGcYqIQbB4G9Z4RFGIQEyIVBWIA+WF16Z10IkXi5FoG7
Zn9JdHY32FVC54a9xkp4JnoiAX3e14HYp33XZ3172H38N4BE+H0xmH6AlXWHJ3Xm54Dsh22K/5Z+
PAaJZfiGkTZ/UehlQBc6dngpm2gonQh6oBiKojiKpFiKpniKqJiKqriKrNiKrviKsBiLsjiLtFiL
tniLuJiLuriLvNiLvviLwBiMwjiMxFiMnAhk8WcSlRdSnyhqMfVZxcKAkyZSCEgSy2hUT8Flz6hE
7XJ0fXRf10hvPRaOR1F5ntWMUSGNZyh41fiNJbVEzGdg8Nh+KPZAPnVn6oh+CXhwmFiIS+SPyYh+
+TiP6LgU1+h37QiJAYlx1VaN2uhX/ThN7+eQC/mQLxV/A3Y/8xOQ1PSQHYmR8liRBUkV/8iQ0BiS
GimRKpllCamRKGlgL2mSCSWSLrmOhRhnFv+ZkuBIk0JTkjlZkzkZlDRJkC0JkzJplEJpiDBGkTuY
RvPojke5gyspe+RYKQO5kEA5lDupkwj4k3EWk1NplC35jxK5kTAZjx7JkVpZlPZGjV5JkXAZlvfY
lVj5lXN5lhYZeNx4lHAZe2VJlzJJllv5l93olnVJlVCJmISnlndZj42pmOrojTiYYpLZlO0olYyp
jWgpmZdTlWxJE54Ji54ZmilhmcZ4mqh5HqTpPyNpivm4lCu2jbFnk9qzYebYmoVJZITpEav5mbEJ
iq9Zk+7oTu+YmWIZkvxIlJL3mk1pmosZg0SpmfPXj6Nzm6rFl175kWMJkoCJlNzZkGV5mxn/CZ4s
SZ7CGTvNuZUxeZxvmZR9iZ3q2Z17CZ8JmZS7STv2GZksOZnQGJ7E2ZgrmZ60SZ/aGZa++Tr5OZ8v
2Z48eZ9/+ZZsaaDZuZbHiaDxmaA4OZ79iY/O5570GaEXWpcYSp2tk56N+J90+ZhgWWAC6p2El4Iw
lpF4OZf+yZmz05tOgaMSoaOow6MGqXDOmZpCOqQr4aMzSaQZEZyGiKOraaSzaZe46TreyI47ioyl
GaWso6QC2X7PmJwoaqJP6ZfGKZ30CJxdqqHnGZfxmZU6iXBoSpku2opp+Z5saqBsup77iJUleaCj
+JQOGqLbWafT6JOECqOq6KfOJ6hcOZt2/5qnGVqhThpQMvWn0Nao7wmhd7qgJ5mKMoWDjqmcnjqR
LTqg0umdGImlSJqqqrqqrKqJqNqqz5mDfBqrH3GQifqKU3qfpNqJkRp6QbqZEbmToOqly3mq0cml
tGqjByaeaAqpwuqicAqjmomXi2qSzcqpyeihigqt1PiVHyqhFIqt0HmrkPmf8MiegKqm1XquqIio
aXqOaVqt3OqS4EqnvXo8k0qu8BqneFqv6rqi3lqKnRqkgZqYJ6qm2XaXo1qqsMpgr9qwswqxEjux
2fiwF5lPGXavtqOlWtp8znixT+pQm4qNGxusE6GxHnuyGWuxmMOxFkecoUqvMgqmz1moBP+JrI5Z
ruXKfMxJsK46oNyonShGrQE6r4CJoQWrkNaKnChpnhWapc45oc13levKoVTrrwE7lfWKtChbOedY
beQ6nHvqoTcrmG2aqzIamIDKtSyrKEIbrcsojWPLkykqoJZqk1q7tuHatVS3n3Abc2nrr1Qql9oK
kYOpt/9KoqnztQyrlFA6cGLZs3F6lcE6t9YKtk5bt3yLpPuKsRTruSE7k4r7uaSrqpt7saeLiy57
dD6KqeXXtkkKu1WRqyLhugEnuwvYmb9KdJnJpeYalW4KoPQIpr47nWXKbAGKucU5rqPrNtYprVp5
rXOatEabqXkpvdz5pEW7tASqq5yjn1X/+6/Aq5v7yZf8er0A+7zVy7aXibt6IbSXK7yJa7Leyq6X
qpbIaY9Tu757q6fumxfwy6DhG6YhS5iWq6l4eqDsu7Xd+rP1278pSqcBG8Eyu61mm8CGW6mIu56p
e4yMirM1Kr/rqLynCr0N2Z2jmoCISbnGi67/u3Iv7LAKeoodDJojW7o4nMM6vMM83MM+/MNAHMRC
PMREXMRGfMRInMRKvMRM3MRO/MRQHMVSPMVUXMVWfMVYnMVavMVc3MVe/MVgHMZiPMZkXMZmfMZo
nMZqvMZs3MZu/MZwHMdyPMd0XMd2fMd4nMd6vMd83Md+/MeAHMiCPMiEXMiGfMiInMiKB7zIjNyL
AQEAOw==

--=====================_520171==.REL--



Received: from 213138131136.edelkey.net (213138131136.edelkey.net [213.138.131.136]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5P8bUv6017025; Mon, 25 Jun 2007 01:37:31 -0700 (MST) (envelope-from vofreformasjig@reformas.org)
Received: from [213.138.131.136] by mailserver.reformas.org; Mon, 25 Jun 2007 08:37:31 -0200
Date: 	Mon, 25 Jun 2007 08:37:31 -0200
From: "Deann Price" <vofreformasjig@reformas.org>
X-Mailer: The Bat! (v2.01) Business
Reply-To: vofreformasjig@reformas.org
X-Priority: 3 (Normal)
Message-ID: <743766578.13595494526349@reformas.org>
To: ietf-mta-filters-request@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------21957D386E29C38D"

------------21957D386E29C38D
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

LegalRXMedications chemist's shop acquaints you with all medicinal agents that you want to restore your health with a little cost. 
We manage around the globe with clients from Europe, America and Asia. 
At this time you don't have to seek out chemist's shop at your area.
We surely convey medicinal preparations of the highest qualityworldwide.
Visit our site and get cures you require instantly straightly to your lodging. 
http://secondmine.hk/ 
We’re endorsed by VISA & VeriSign so then we ensure safe & reliable acquisition.

------------21957D386E29C38D
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> chemist's shop acquaints you with all medicinal agents that you want to restore your health with a little cost. <br>
We manage around the globe with clients from Europe, America and Asia. <br>
At this time you don't have to seek out chemist's shop at your area.<br>
We surely convey medicinal preparations of the highest qualityworldwide.
<br>
<br>
<a href="http://secondmine.hk/" target="_blank"><em>Visit our site and get cures you require instantly straightly to your lodging.</em></a></b> 
<br>
<font color="#D9EDFF">http://secondmine.hk/</font> 
<br><b>We’re endorsed by <font color="#FF0000"><em>VISA</em></font> & <font color="#FF0000"><em>VeriSign</em></font> so then we ensure safe & reliable acquisition.
</b>

</BODY></HTML>
------------21957D386E29C38D--



Received: from h9.226.89.75.ip.alltel.net (h9.226.89.75.ip.alltel.net [75.89.226.9]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5OHdJje003869; Sun, 24 Jun 2007 10:39:21 -0700 (MST) (envelope-from sifrayhatfieldvug@rayhatfield.com)
Received: from 69.49.101.246 (HELO mx3c10.megamailservers.com) by imc.org with esmtp (K3QSQG)*,R 3V,L=) id SL-2W)-2JRCE*-8, for ietf-scmp-request@imc.org; Sun, 24 Jun 2007 17:39:24 +0500
Date: 	Sun, 24 Jun 2007 17:39:24 +0500
From: "Cornelia Mccoy" <sifrayhatfieldvug@rayhatfield.com>
X-Mailer: The Bat! (v2.00.9) Business
X-Priority: 3 (Normal)
Message-ID: <468377232.50716678095734@thhebat.net>
To: ietf-scmp-request@imc.org
Subject: Obesity is dangerous, stop it
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------E9016E925FFF8401"
X-Spam: Not detected

------------E9016E925FFF8401
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Do not fail the opportunity! =96 Anatrim =96 The newest and most=20=
enchanting lose flesh product is now available =96 As shown on Oprah

Can you remember all the situations when you plead to yourself to do=20=
anything for being rescued from this horrible kilos of fat? Happily, now=20=
no major price is to be paid. Thanks to Anatrim, the earth-shaking, you=20=
can get healthier lifestyle and a really slender figure. Just notice what=20=
people say to us!
 
=93I always had an incredible private life until last year my girl said=20=
to me I was fat and in want of keeping eye on my health. My life went the=20=
wrong way after that, till I was told about Anatrim =99. Since loosing=20=
more than 18 kilogrames thanks to Anatrim,  my private life=92s come=20=
back, better even than before. Great deal of thanks to you for the=20=
awesome product and the top-quality service. Go on your valuable action!=94

 
Steve Doubt, Washington

 
"Nothing to compare with sliding into a bikini I have not worn for=20=
years. I feel svelte, defined, and sturdy, thanx to a degree to Anatrim!=20=
Thank you a lot!"

 
Linda F., Boston

Discover Anatrim, and  you will add yourself to the world-wide=20=
association of thousands of happy buyers who=92re enjoying the=20=
revolutionary results of Anatrim right here & right now. Less swallowing=20=
madness, less lbs and more happiness in life!

Proceed here to inspect outdone Anatrim deal we=92re proud to offer!!!
http://www.gutif.hk/?lcslzmxllu
------------E9016E925FFF8401
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Get your ideal weight with this natural method</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.gutif.hk/?lcslzmxllu" target=3D"_blank">
Do not fail the opportunity! =96 Anatrim =96 The newest and most=20=
enchanting lose flesh product is now available =96 As shown on Oprah
</a>
</center>
<br>
Can you remember all the situations when you plead to yourself to do=20=
anything for being rescued from this horrible kilos of fat? Happily, now=20=
no major price is to be paid. Thanks to Anatrim, the earth-shaking, you=20=
can get healthier lifestyle and a really slender figure. Just notice what=20=
people say to us!
 <br>
<br>
<i>
=93I always had an incredible private life until last year my girl said=20=
to me I was fat and in want of keeping eye on my health. My life went the=20=
wrong way after that, till I was told about Anatrim =99. Since loosing=20=
more than 18 kilogrames thanks to Anatrim,  my private life=92s come=20=
back, better even than before. Great deal of thanks to you for the=20=
awesome product and the top-quality service. Go on your valuable action!=94
</i>
 <br>
<b>
<i>
Steve Doubt, Washington
</i>
</b>
 <br>
<br>
<i>
"Nothing to compare with sliding into a bikini I have not worn for=20=
years. I feel svelte, defined, and sturdy, thanx to a degree to Anatrim!=20=
Thank you a lot!"
</i>
 <br>
<b>
<i>
Linda F., Boston
</i>
</b>
<br>
<br>
Discover Anatrim, and  you will add yourself to the world-wide=20=
association of thousands of happy buyers who=92re enjoying the=20=
revolutionary results of Anatrim right here & right now. Less swallowing=20=
madness, less lbs and more happiness in life!
<br>
<br>
<center>
<a href=3D"http://www.gutif.hk/?lcslzmxllu" target=3D"_blank">
Proceed here to inspect outdone Anatrim deal we=92re proud to offer!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.gutif.hk/?lcslzmxllu</font>

</BODY></HTML>
------------E9016E925FFF8401--



Received: from komputerek (pc3-41.chomiczowka.waw.pl [195.136.168.41]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5OENjpb051466; Sun, 24 Jun 2007 07:23:46 -0700 (MST) (envelope-from sifrazormvug@razorm.com)
Received: from 209.85.135.27 (HELO aspmx2.googlemail.com) by imc.org with esmtp (:L3,.+0A5003 9.?Y*') id 2FR;,*-OBHB./-0* for ietf-pkix-oid-reg@imc.org; Sun, 24 Jun 2007 14:23:49 -0100
Date: 	Sun, 24 Jun 2007 14:23:49 -0100
From: "Byron Coleman" <sifrazormvug@razorm.com>
X-Mailer: The Bat! (v2.12.00) Business
X-Priority: 3 (Normal)
Message-ID: <315321031.59805050906284@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Make her worship you
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------7FD321EB805C1E"
X-Spam: Not detected

------------7FD321EB805C1E
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


After all the real stuff =96 with no more swindle! 
P.E.P. are very hot at the time! This is the true stuff not a=20=
counterfeit! 

One of the very exceptionals, absolutely unparalleled stuff is on sale=20=
all over the world!
 Take note of what people tell on this produce:

"I like how fast your product affected on my boyfriend, he can not stop=20=
chatting on how hot he is having his new size, length, and libido!"

Amely S., Chicago

"Firstly I decided the gratuitous specimen parcel I was given was a=20=
nasty trick, till I tried P.E.P. There are no words to depict how plume I=20=
am with the effect I got from using this remedy for 8 brief weeks. I'll=20=
be ordering at every turn!" 
Mike Brown, New York

Look at more testimonies on this marvellouls product right here!
http://www.kopab.hk/?rvrtxwargfv
------------7FD321EB805C1E
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Last offer- Discount special for PE patch almost over</TITLE>
</HEAD>
<BODY>

<b>
After all the real stuff =96 with no more swindle! 
<br>
<a href=3D"http://www.kopab.hk/?rvrtxwargfv"=20=
target=3D"_blank">P.E.P.</a> are very hot at the time! This is the true=20=
stuff not a counterfeit! 
<br>
One of the very exceptionals, absolutely unparalleled stuff is on sale=20=
all over the world!
<br> Take note of what people tell on this produce:
<p>
<i>
"I like how fast your product affected on my boyfriend, he can not stop=20=
chatting on how hot he is having his new size, length, and libido!"
</i>
</p>
Amely S., Chicago
<p>
<i>
"Firstly I decided the gratuitous specimen parcel I was given was a=20=
nasty trick, till I tried P.E.P. There are no words to depict how plume I=20=
am with the effect I got from using this remedy for 8 brief weeks. I'll=20=
be ordering at every turn!" </i>
</p>
Mike Brown, New York
<center>
<a href=3D"http://www.kopab.hk/?rvrtxwargfv" target=3D"_blank">
Look at more testimonies on this marvellouls product right here!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.kopab.hk/?rvrtxwargfv</font>

</BODY></HTML>
------------7FD321EB805C1E--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5NKkg4B055937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 Jun 2007 13:46:42 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5NKkgOW055936; Sat, 23 Jun 2007 13:46:42 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.pingtel.com (hide.pingtel.com [65.220.123.2]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5NKkaf9055903 for <ietf-pkix@imc.org>; Sat, 23 Jun 2007 13:46:40 -0700 (MST) (envelope-from slawrence@pingtel.com)
Received: from [127.0.0.1] (pi.pingtel.com [10.1.1.12]) by mail.pingtel.com (Postfix) with ESMTP id AA8E76C025; Sat, 23 Jun 2007 16:45:55 -0400 (EDT)
Subject: Domain certificates in SIP
From: Scott Lawrence <slawrence@pingtel.com>
To: ietf-pkix@imc.org
Cc: Vijay Gurbani <vkg@lucent.com>
Content-Type: text/plain
Organization: Pingtel Corp.
Date: Sat, 23 Jun 2007 16:46:27 -0400
Message-Id: <1182631587.3432.26.camel@scott.skrb.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 
Content-Transfer-Encoding: 7bit
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>

draft-gurbani-sip-domain-certs-05 has been submitted to
the IETF archives.  We've tried to incorporate some of the advice we got
around the Prague meeting.

This version focuses fairly narrowly on:

- How to use and interpret the SIP identities in a X.509 certificate.
- How to indicate that this particular certificate is for SIP
  usage.

What goes in the subjectAltName, and a new EKU value, with the detailed
steps to interpret and validate them are provided from the viewpoint of
user agents, proxies, and registrars.

Until the -05 version appears in the archives, you can get it from:

http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-gurbani-sip-domain-certs-05.txt
http://svn.resiprocate.org/rep/ietf-drafts/gurbani/domain-certs/draft-gurbani-sip-domain-certs-05.html

Comments, questions and other feedback is much appreciated.

-- 
Scott Lawrence  tel:+1-781-938-5306;ext=162 or sip:slawrence@pingtel.com
  sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs
  Chief Technology Officer    - Pingtel Corp. http://www.pingtel.com/



Received: from host-89-228-34-240.elk.mm.pl (host-89-228-34-240.elk.mm.pl [89.228.34.240]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5N0hHup019170; Fri, 22 Jun 2007 17:43:27 -0700 (MST) (envelope-from dinprovenmenfem@provenmen.org)
Received: from 65.163.13.18 (HELO mail.provenmen.org) by imc.org with esmtp (@-;69Y>P99Q 7H326) id --29V+-@88M45-5> for ietf-pkix-request@imc.org; Sat, 23 Jun 2007 00:43:31 -0100
Date: 	Sat, 23 Jun 2007 00:43:31 -0100
From: "Ramon Chin" <dinprovenmenfem@provenmen.org>
X-Mailer: The Bat! (v2.00.8) Business
X-Priority: 3 (Normal)
Message-ID: <358079707.15287595418208@thhebat.net>
To: ietf-pkix-request@imc.org
Subject: Get your ideal weight with this natural method
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------EEE7A52C6EE7318F"
X-Spam: Not detected

------------EEE7A52C6EE7318F
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: quoted-printable


Don't fail the opportunity! =96 Anatrim =96 The newest and most=20=
attracting product for corpulent people is made available now =96 As you=20=
could see on Oprah

Can you recall all the times when you appeal to yourself to do any=20=
thing for being delivered from this terrible number of kilos?=20=
Fortunately, now no big price is to be paid. Thanks to Anatrim, the=20=
ground-breaking, you can achieve healthier life style and a really=20=
slender figure. Simply notice what people state!
 
=93I had always led an incredible private life till a year back the=20=
girl I was meeting said to me I was plump and in need of looking after my=20=
health. Life went the wrong way after that, until I discovered Anatrim=20=
=99 for me. Since getting rid of more than 18 kilogrammes only thanx to=20=
Anatrim,  my private life has come back, notoriously better than before=20=
even. Greatest thanks to you for the awesome stuff and the first-rate=20=
maintenance service. Proceed with your helpful action!=94

 
Serge Smith, Bellevue WA

 
"There=92s nothing better than sliding into a bikini that I haven't=20=
worn for many long years. I feel svelte, determined, and healthy, thanks=20=
to a considerable degree to Anatrim! Thanks a lot!"

 
Amely S., Chicago

Check out Anatrim, and  you shall add yourself to the worldwide=20=
community of thousands of pleased buyers who are getting pleasure out of=20=
the revolutionary results of Anatrim here and now. Less swallowing=20=
madness, less kilogrames and more happiness in life!

Click right here to examine our unbeatable Anatrim bargain!!!
http://www.apents.hk/?qokvwrsyzi
------------EEE7A52C6EE7318F
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Melt away fat easily</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.apents.hk/?qokvwrsyzi" target=3D"_blank">
Don't fail the opportunity! =96 Anatrim =96 The newest and most=20=
attracting product for corpulent people is made available now =96 As you=20=
could see on Oprah
</a>
</center>
<br>
Can you recall all the times when you appeal to yourself to do any=20=
thing for being delivered from this terrible number of kilos?=20=
Fortunately, now no big price is to be paid. Thanks to Anatrim, the=20=
ground-breaking, you can achieve healthier life style and a really=20=
slender figure. Simply notice what people state!
 <br>
<br>
<i>
=93I had always led an incredible private life till a year back the=20=
girl I was meeting said to me I was plump and in need of looking after my=20=
health. Life went the wrong way after that, until I discovered Anatrim=20=
=99 for me. Since getting rid of more than 18 kilogrammes only thanx to=20=
Anatrim,  my private life has come back, notoriously better than before=20=
even. Greatest thanks to you for the awesome stuff and the first-rate=20=
maintenance service. Proceed with your helpful action!=94
</i>
 <br>
<b>
<i>
Serge Smith, Bellevue WA
</i>
</b>
 <br>
<br>
<i>
"There=92s nothing better than sliding into a bikini that I haven't=20=
worn for many long years. I feel svelte, determined, and healthy, thanks=20=
to a considerable degree to Anatrim! Thanks a lot!"
</i>
 <br>
<b>
<i>
Amely S., Chicago
</i>
</b>
<br>
<br>
Check out Anatrim, and  you shall add yourself to the worldwide=20=
community of thousands of pleased buyers who are getting pleasure out of=20=
the revolutionary results of Anatrim here and now. Less swallowing=20=
madness, less kilogrames and more happiness in life!
<br>
<br>
<center>
<a href=3D"http://www.apents.hk/?qokvwrsyzi" target=3D"_blank">
Click right here to examine our unbeatable Anatrim bargain!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.apents.hk/?qokvwrsyzi</font>

</BODY></HTML>
------------EEE7A52C6EE7318F--



Received: from muedsl-82-207-196-115.citykom.de (muedsl-82-207-196-115.citykom.de [82.207.196.115]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5MHTs9G094038; Fri, 22 Jun 2007 10:29:56 -0700 (MST) (envelope-from gytprimaryconsultingdac@primaryconsulting.com)
Received: from 208.218.214.23 (HELO mx1.cniweb.net) by imc.org with esmtp (/T7(*YYYY 1R@6) id ,<57>7-I=+G/H-79 for ietf-ltans-oid-reg@imc.org; Fri, 22 Jun 2007 17:30:04 -0100
Date: 	Fri, 22 Jun 2007 17:30:04 -0100
From: "Darren Flanagan" <gytprimaryconsultingdac@primaryconsulting.com>
X-Mailer: The Bat! (v3.0.1.33) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <631994995.72700938958549@thhebat.net>
To: ietf-ltans-oid-reg@imc.org
Subject: Last chance to supercharge your performance
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------677EA14DA9F46EA"
X-Spam: Not detected

------------677EA14DA9F46EA
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7bit



At last, the true stuff – no more trim! 
P.E.P. are very hot right this time! Well this is the real thing not a fictitious one! 

One of the very originals, totally unrivalled produce is affordable all over the world!
 Pay attention to just what people tell on this produce:

"I like how rapidly P.E.P. had an affect on my boyfriend, he can not stop chatting on how excited he is having such new girth, extent, and libido!"

Lusia R., Las Vegas

"At first I thought the free specimen package I acquired was a jest, until I tried P.E.P. There are no words to describe how highly satisfied I am with the consequence from using this stuff for 9 brief weeks. I'll be asking for P.E.P. on a regular basis!" 
Rikky Martin, Las Vegas

Look at more recommendations on this wonderful product right here!
http://www.upeyan.hk/?dpmmhafynux

------------677EA14DA9F46EA
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Last chance to supercharge your performance</TITLE>
</HEAD>
<BODY>

<b>
At last, the true stuff – no more trim! 
<br>
<a href="http://www.upeyan.hk/?dpmmhafynux" target="_blank">P.E.P.</a> are very hot right this time! Well this is the real thing not a fictitious one! 
<br>
One of the very originals, totally unrivalled produce is affordable all over the world!
<br> Pay attention to just what people tell on this produce:
<p>
<i>
"I like how rapidly P.E.P. had an affect on my boyfriend, he can not stop chatting on how excited he is having such new girth, extent, and libido!"
</i>
</p>
Lusia R., Las Vegas
<p>
<i>
"At first I thought the free specimen package I acquired was a jest, until I tried P.E.P. There are no words to describe how highly satisfied I am with the consequence from using this stuff for 9 brief weeks. I'll be asking for P.E.P. on a regular basis!" </i>
</p>
Rikky Martin, Las Vegas
<center>
<a href="http://www.upeyan.hk/?dpmmhafynux" target="_blank">
Look at more recommendations on this wonderful product right here!
</a>
</center>
</b>
<font color="#D9EDFF">http://www.upeyan.hk/?dpmmhafynux</font>

</BODY></HTML>
------------677EA14DA9F46EA--



Received: from oem-72e6cc5266e (host-81-190-242-25.malbork.mm.pl [81.190.242.25]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5LGSwEJ059377; Thu, 21 Jun 2007 09:29:00 -0700 (MST) (envelope-from bofpokerprofisuw@pokerprofi.info)
Received: from 81.222.135.9 (HELO mx2.spaceweb.ru) by imc.org with esmtp ((Y-:'A=28 .MU0I)) id T-0XNI-A(OO9A-86 for ietf-pkix-archive@imc.org; Thu, 21 Jun 2007 16:28:53 -0100
Date: 	Thu, 21 Jun 2007 16:28:53 -0100
From: "Lesley Sanderson" <bofpokerprofisuw@pokerprofi.info>
X-Mailer: The Bat! (v3.0.1.33) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <423511531.26481773603059@thhebat.net>
To: ietf-pkix-archive@imc.org
Subject: Make yourself more attractive to others
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------01D3AE16E9090925"
X-Spam: Not detected

------------01D3AE16E9090925
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit



Profit by the chance! – Anatrim – The up-to-the-moment & most exciting product for over-weight people is now easily available – As shown on Oprah

Can you count up all the situations when you appeal to yourself to do anything for being saved from this awful kilos of fat? Happily, now no big offering is demanded. With Anatrim, the ground-breaking, you can achieve naturally health lifestyle and become really slimmer. Notice what people say to us!
 
“I had always led a great private life till a year ago my girlfriend told me I was portly and in want of keeping eye on my health. My life went the wrong way after that, until I was told about Anatrim ™ at once. After loosing more than 18 kilogrammes only thanx to Anatrim,  my private life’s back on track, significantly better than even before. Thank you for the awesome stuff & the great service. Proceed with your helpful work!”

 
Steve Doubt, Chicago

 
"There’s nothing better than slipping into a bikini I have not worn for years. I feel lean, steadfast, and vigorous, thanks to a considerable degree to Anatrim! Lots of thank you!"

 
Linda F., San Diego

Discover Anatrim, and  you shall add yourself to the world-wide association of thousands of delighted user who take pleasure in the revolutionary results of Anatrim here & now. Less devouring frenzy, less lbs and more joy in your life!

Proceed here to gaze at invincible Anatrim bargain we are so proud to propose!!!
http://www.promfore.com/?zhfuylqkyfm

------------01D3AE16E9090925
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Summer is almost here, be ready</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href="http://www.promfore.com/?zhfuylqkyfm" target="_blank">
Profit by the chance! – Anatrim – The up-to-the-moment & most exciting product for over-weight people is now easily available – As shown on Oprah
</a>
</center>
<br>
Can you count up all the situations when you appeal to yourself to do anything for being saved from this awful kilos of fat? Happily, now no big offering is demanded. With Anatrim, the ground-breaking, you can achieve naturally health lifestyle and become really slimmer. Notice what people say to us!
 <br>
<br>
<i>
“I had always led a great private life till a year ago my girlfriend told me I was portly and in want of keeping eye on my health. My life went the wrong way after that, until I was told about Anatrim ™ at once. After loosing more than 18 kilogrammes only thanx to Anatrim,  my private life’s back on track, significantly better than even before. Thank you for the awesome stuff & the great service. Proceed with your helpful work!”
</i>
 <br>
<b>
<i>
Steve Doubt, Chicago
</i>
</b>
 <br>
<br>
<i>
"There’s nothing better than slipping into a bikini I have not worn for years. I feel lean, steadfast, and vigorous, thanks to a considerable degree to Anatrim! Lots of thank you!"
</i>
 <br>
<b>
<i>
Linda F., San Diego
</i>
</b>
<br>
<br>
Discover Anatrim, and  you shall add yourself to the world-wide association of thousands of delighted user who take pleasure in the revolutionary results of Anatrim here & now. Less devouring frenzy, less lbs and more joy in your life!
<br>
<br>
<center>
<a href="http://www.promfore.com/?zhfuylqkyfm" target="_blank">
Proceed here to gaze at invincible Anatrim bargain we are so proud to propose!!!
</a>
</center>
</b>
</p>
<font color="#D9EDFF">http://www.promfore.com/?zhfuylqkyfm</font>

</BODY></HTML>
------------01D3AE16E9090925--



Received: from 78-3-25-121.adsl.net.t-com.hr (78-3-25-121.adsl.net.t-com.hr [78.3.25.121]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5L9SGtH050365; Thu, 21 Jun 2007 02:28:38 -0700 (MST) (envelope-from nehpistahansot@pistahan.net)
Received: from 74.208.5.3 (HELO mx00.1and1.com) by imc.org with esmtp (14;2.34+@B< ++7H) id 6M66*--.,08+C--< for ietf-pkix-oid-reg@imc.org; Thu, 21 Jun 2007 09:28:38 -0100
Date: 	Thu, 21 Jun 2007 09:28:38 -0100
From: "Milo Gilbert" <nehpistahansot@pistahan.net>
X-Mailer: The Bat! (v3.0.0.15) Home
X-Priority: 3 (Normal)
Message-ID: <311279339.08204284686426@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Don't be inadequate anymore
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------A988F46EA9FB2C"
X-Spam: Not detected

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


At last, the original thing =96 without swindle! 
P.E.P. are hot right this time! Well here comes the true stuff not a=20=
forgery! 

One of the very originals, totally unequalled product is easy=20=
accessible everywhere!
 Take note of what people say about this product:

"I pleased how swiftly P.E.P. worked on my boyfriend, he can't stop=20=
jabber on how excited he is having such new girth, length, and libido!"

Amely S., San Diego

"At the beginning I thought the specimen parcel I acquired gratis was a=20=
kind of a nasty trick, till I tried P.E.P. There are no words to describe=20=
how satisfied I am with the effect I got from using this patch for 9=20=
brief weeks. I'll be requesting on a constant basis!" 
Steve Burbon, Chicago

Look at more testimonies on this astonishing product right here & right=20=
now!
http://www.promfore.com/?gbhxfhcwgwfm

------------A988F46EA9FB2C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Hey man, stop throwing away your money</TITLE>
</HEAD>
<BODY>

<b>
At last, the original thing =96 without swindle! 
<br>
<a href=3D"http://www.promfore.com/?gbhxfhcwgwfm"=20=
target=3D"_blank">P.E.P.</a> are hot right this time! Well here comes the=20=
true stuff not a forgery! 
<br>
One of the very originals, totally unequalled product is easy=20=
accessible everywhere!
<br> Take note of what people say about this product:
<p>
<i>
"I pleased how swiftly P.E.P. worked on my boyfriend, he can't stop=20=
jabber on how excited he is having such new girth, length, and libido!"
</i>
</p>
Amely S., San Diego
<p>
<i>
"At the beginning I thought the specimen parcel I acquired gratis was a=20=
kind of a nasty trick, till I tried P.E.P. There are no words to describe=20=
how satisfied I am with the effect I got from using this patch for 9=20=
brief weeks. I'll be requesting on a constant basis!" </i>
</p>
Steve Burbon, Chicago
<center>
<a href=3D"http://www.promfore.com/?gbhxfhcwgwfm" target=3D"_blank">
Look at more testimonies on this astonishing product right here & right=20=
now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.promfore.com/?gbhxfhcwgwfm</font>

</BODY></HTML>
------------A988F46EA9FB2C--



Received: from smtp01.maxnet.net.nz (smtp01.maxnet.net.nz [202.89.32.6]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KIJVOP024949; Wed, 20 Jun 2007 11:19:31 -0700 (MST) (envelope-from service@paypal.com)
Received: from muffinbreak.co.nz (port166-199.ubs.maxnet.net.nz [203.89.166.199]) by smtp01.maxnet.net.nz (Postfix) with ESMTP id 815D473991A; Thu, 21 Jun 2007 06:19:29 +1200 (NZST)
Received: from User ([67.53.61.46]) by muffinbreak.co.nz with Microsoft SMTPSVC(6.0.3790.1830); Thu, 21 Jun 2007 06:19:27 +1200
Reply-To: <support@paypal.com>
From: "PayPal"<service@paypal.com>
Subject: Dispute Transaction
Date: Wed, 20 Jun 2007 08:19:27 -1000
MIME-Version: 1.0
Content-Type: text/html; charset="Windows-1251"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <FOODCOSVRZ9fhzgAfiw00000f21@muffinbreak.co.nz>
X-OriginalArrivalTime: 20 Jun 2007 18:19:27.0983 (UTC) FILETIME=[89E4DFF0:01C7B367]
X-TM-AS-Product-Ver: SMEX-7.5.0.1166-3.6.1039-15250.000
X-TM-AS-Result: No--2.782600-5.000000-2
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
To: undisclosed-recipients:;

<html>
</font>
&nbsp;</div>
			<div id="message5">
				<pre><tt>Dear PayPal Member</font></a>,


This email confirms that you have sent an eBay payment of $47.85 USD to 
<a href="mailto:acoyner2@comcast.net&YY=24663&order=down&sort=date&pos=0&view=a&head=f" target="_top">acoyner2@comcast.net</a> for an eBay item. 



-----------------------------------
Payment Details
-----------------------------------


Amount: $47.85 USD

Transaction ID: 2LC956793J776333Y

Subject: Digimax 130





Note:
<span class="style5"><em>If you haven't authorized this charge ,click the link below to dispute transaction 
and get full refund</em></span>

<a target="_blank" href="http://ool-43566527.dyn.optonline.net:9999/www.paypal.com/cgi-bin/webscr=home=p/index.php">Dispute transaction</a> (Encrypted Link )

<span class="style5">*SSL connection:
PayPal automatically encrypts your confidential information
in transit from your computer to ours using the Secure 
Sockets Layer protocol (SSL) with an encryption key length 
of 128-bits (the highest level commercially available)
</span>
-----------------------------------
Item Information
-----------------------------------


eBay User ID: scratchandgnaw2
   

----------------------------------------------------------------
Edward Harrell's UNCONFIRMED Address
----------------------------------------------------------------

Edward Harrell
211 David St. 
Springtown, TX 76082
United States

Important Note: Edward Harrell has provided an Unconfirmed Address. If 
you are planning on shipping items to Edward Harrell, please check the 
Transaction Details page of this payment to find out whether you will 
be covered by the PayPal Seller Protection Policy. 




----------------------------------------------------------------
This payment was sent using your bank account. 

By using your bank account to send money, you just:

- Paid easily and securely

- Sent money faster than writing and mailing paper checks
- Paid instantly -- your purchase won't show up on bills at the end of 
the month. 

Thanks for using your bank account!



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

Thank you for using PayPal!
The PayPal Team
PayPal Email ID PP118
<html>


Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KFVEWM089844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Jun 2007 08:31:15 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5KFVE82089838; Wed, 20 Jun 2007 08:31:14 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KFVCNU089817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Wed, 20 Jun 2007 08:31:13 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l5KFVCqO028283; Wed, 20 Jun 2007 08:31:12 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 08:31:11 -0700
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_01C7B350.07C19428"
Subject: RE: Three short fixes: no padlock; text logo; member since
Date: Wed, 20 Jun 2007 08:29:50 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012F622A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <6215401E01247448A306C54F499111F202BB51C8@WSMSG2103V.srv.dir.telstra.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes: no padlock; text logo; member since
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgKZqHkAAIZIOoA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 20 Jun 2007 15:31:11.0638 (UTC) FILETIME=[0800E360:01C7B350]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B350.07C19428
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

VGhlIGlzc3VlIGhlcmUgaXMgYmFja3dhcmRzIGNvbXBhdGliaWxpdHkuDQogDQpBbnkgY2VydGlm
aWNhdGUgaXNzdWVkIHRvZGF5IG11c3Qgd29yayBhY2NhcHRhYmx5IHdpdGggZXhpc3RpbmcgYnJv
d3NlcnMuIFRoYXQgbWVhbnMgY2hhaW5pbmcgdXAgdG8gYW4gZW1iZWRkZWQgcm9vdC4gVW5kZXIg
dGhlIHJ1bGVzIGFzIHRoZXkgYXJlIHRvZGF5IGEgY2VydCBpc3N1ZXIgY2FuIGlzc3VlIGEgY2Vy
dGlmaWNhdGUgd2l0aCBlc3NlbnRpYWxseSBubyBtZWFuaW5nZnVsIGF1dGhlbnRpY2F0aW9uIGFu
ZCBtYW55IGRvLg0KIA0KVGhlIHBvaW50IGlzIHRvIGFsbG93IGFuIGlzc3VlciB0byBkaWZmZXJl
bnRpYXRlIGJldHdlZW4gY2VydGlmaWNhdGVzIHRoYXQgYXJlIGRlc2lnbmVkIHRvIHByb3ZpZGUg
YSBtZWFuaW5nZnVsIGRlZ3JlZSBvZiBhY2NvdW50YWJpbGl0eSBmcm9tIHRob3NlIHdoaWNoIGFy
ZSBzaW1wbHkgZGVzaWduZWQgdG8gdHVybiBvbiBTU0wgaW4gdGhlIGRlcGxveWVkIGJhc2Ugb2Yg
YSBiaWxsaW9uIGJyb3dzZXJzLiBPdmVyIHRpbWUgdGhlIGRlcGxveW1lbnQgb2YgYnJvd3NlcnMg
dGhhdCBvYnNlcnZlIHRoZSBPSUQgd291bGQgaW5jcmVhc2UuDQogDQogDQpJZiB3ZSB3ZXJlIGRl
c2lnbmluZyBmcm9tIHNjcmF0Y2ggdGhlIHNlbnNpYmxlIHdheSB0byBkbyB0aGlzIHdvdWxkIGJl
IHRvIGhhdmUgYW4gT0lEIHdpdGggcG9zaXRpdmUgc2VtYW50aWNzICdhc3NlcnQgc2VjdXJpdHkg
dG8gdGhlIHVzZXInLiBTaW5jZSB3ZSBkb24ndCBoYXZlIHRoYXQgbHV4dXJ5IGFuZCBzaW5jZSB3
ZSBoYXZlIHRvIGRlYWwgd2l0aCB0aGUgYmlsbGlvbiBkZXBsb3llZCBicm93c2VycyB3ZSBuZWVk
IGEgZGlmZmVyZW50IGFwcHJvYWNoLg0KIA0KSSBkbyBub3QgYWdyZWUgd2l0aCB0aGUgc2VudGlt
ZW50IHRoYXQgYSBzdGFuZGFyZHMgcHJvY2VzcyBzaG91bGQgb25seSBkZWFsIHdpdGggcGVyZmVj
dCBzaXR1YXRpb25zIGFuZCBzdGljayBpdHMgaGVhZCBpbiB0aGUgc2FuZCB3aGVuIGl0IGNvbWVz
IHRvIHRvdWdoIGRlcGxveW1lbnQgaXNzdWVzLiBNYW5hZ2luZyB0aGUgY29uc3RyYWludHMgb2Yg
dGhlIGRlcGxveWVkIGJhc2Ugc2hvdWxkIGJlIHRoZSBmaXJzdCBjb25jZXJuIGZvciBhIFdHIHRo
YXQgaGFzIGJlZW4gaW4gZXhpc3RlbmNlIGZvciB0ZW4geWVhcnMuIA0KIA0KQXQgbGVhc3QgUEtJ
WCBoYXMgYSBkZXBsb3llZCBiYXNlIHRvIHdvcnJ5IGFib3V0Lg0KIA0KDQoNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQoNCglGcm9tOiBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gT24gQmVoYWxmIE9mIE1h
bmdlciwgSmFtZXMgSA0KCVNlbnQ6IFN1bmRheSwgSnVuZSAxNywgMjAwNyA5OjM5IFBNDQoJVG86
IHBraXgNCglTdWJqZWN0OiBSRTogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQg
bG9nbzsgbWVtYmVyIHNpbmNlDQoJDQoJDQoNCglJIGxpa2UgdGhlIGlkZWEgb2YgcmV2ZXJ0aW5n
IHRvIGFuIOKAnHVuc2VjdXJlZOKAnSBsb29rLW4tZmVlbCBhbmQgYXZvaWRpbmcgbmFnIHNjcmVl
bnMgd2hlbiB0aGUgc2VjdXJpdHksIHRob3VnaCBwcmVzZW50LCBpcyBub3Qg4oCccGVyZmVjdOKA
nS4NCg0KCUl0IGlzIGJhZCB0aGF0IG1hbnkgY2xpZW50cyB0cmVhdCB1bmNvbmZpcm1lZCBzZWN1
cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEgbG9jYWxseS10cnVzdGVkIHJvb3QpIGFzIHdv
cnNlIHRoYW4gbm8gc2VjdXJpdHkuIFRoaXMgZGlzY291cmFnZXMgYXR0ZW1wdHMgdG8gaW1wcm92
ZSBzZWN1cml0eS4NCg0KCUkgYW0gbGVzcyBzdXJlIHRoYXQgYSDigJxubyBwYWRsb2Nr4oCdIGF0
dHJpYnV0ZSBpcyB0aGUgcmlnaHQgd2F5IHRvIGFjaGlldmUgdGhpcy4NCg0KCSANCg0KCT5Xb3Vs
ZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBv
ZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVtYWls
IHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy4NCg0KCSANCg0K
CVdvdWxkbuKAmXQgaXQgYmUgYmV0dGVyIHRvIGZpeCBlbWFpbCBjbGllbnRzIHNvIHRoZXkgYWx3
YXlzIGFjdCB0aGlzIHdheSwgaW5zdGVhZCBvZiBvbmx5IHRyaWdnZXJpbmcgdGhpcyBiZWhhdmlv
dXIgZm9yIGNlcnRhaW4gY2VydGlmaWNhdGVzPyBVbmxlc3MgaXQgaXMgYSB0YWN0aWNhbCBkZWNp
c2lvbiB0aGF0IHNvZnR3YXJlIHZlbmRvcnMgYXJlIG1vcmUgbGlrZWx5IHRvIGltcGxlbWVudCBh
IG5ldyBjZXJ0aWZpY2F0ZSBmZWF0dXJlIHRoYW4gY2hhbmdlIGV4aXN0aW5nIGJlaGF2aW91ciAo
ZXNwZWNpYWxseSBpZiB0aGUgbGF0dGVyIG1pZ2h0IGJlIGJyYW5kZWQgYXMgd29yc2VuaW5nIHNl
Y3VyaXR5KS4NCg0KCSANCg0KCUZvciBIVFRQUyBjb25uZWN0aW9ucywgYSBjZXJ0aWZpY2F0ZSB3
aXRob3V0IGEgc3ViamVjdEFsdE5hbWUuZE5TTmFtZSBmaWVsZCAoYW5kIG5vIGRvbWFpbiBuYW1l
IGluIGEgY29tbW9uIG5hbWUgY29tcG9uZW50IG9mIHRoZSBzdWJqZWN0IGZpZWxkKSBzaG91bGQg
YmUgc3VmZmljaWVudCBmb3IgYSBicm93c2VyIHRvIHNheSDigJx3ZWxsIEkgY2Fubm90IGRvIHRo
ZSBVUkwtdG8tY2VydCBjaGVjayBzbyBJIHdpbGwgZGlzcGxheSB0aGUgcGFnZSBqdXN0IGxpa2Ug
YW4gSFRUUCBwYWdl4oCdOiBubyBjb2xvdXJlZCBhZGRyZXNzIGJhciwgbm8gbG9ja2VkIHBhZGxv
Y2ssIG5vIG5hZyBzY3JlZW5zLCBzdGlsbCB1c2luZyBUTFMgb24tdGhlLXdpcmUgdGhvdWdoLiBO
byBwYXRoIHRvIGEgdHJ1c3RlZCByb290IChlZyBhIHNlbGYtc2lnbmVkIGNlcnQpIHNob3VsZCBi
ZSB0cmVhdGVkIHRoZSBzYW1lIHdheS4gVW5hdmFpbGFibGUgQ1JMcyBjb3VsZCBiZSB0cmVhdGVk
IHRoZSBzYW1lIHdheS4NCg0KCSANCg0KCU90aGVyIGVycm9ycyBzdWNoIGFzIGFuIGluY29ycmVj
dCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yIGEgbWlzbWF0Y2ggYmV0d2VlbiBV
UkwgJiBjZXJ0IG5hbWUgaW1wbHkgdGhlIGNlcnRpZmljYXRlIGhvbGRlciBoYXMgZG9uZSBzb21l
dGhpbmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChv
ciBvdXRyaWdodCByZWZ1c2FsIHRvIGNvbm5lY3QpIGluIHRoZXNlIGNhc2VzLg0KDQoJIA0KDQoJ
UFJPQkxFTQ0KDQoJPiBJIGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRo
YXQgZW5jcnlwdGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhhdmUgZXhwbGljaXRseSBz
YWlkIHRoYXQgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eS4NCg0KCSANCg0KCVRoZSBwcm9ibGVt
IGlzIHRoYXQgdGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg4oCcc2FmZeKAnSBj
b25uZWN0aW9uLCByZWdhcmRsZXNzIG9mIGEgcGFkbG9jayBpY29uIG9yIGFkZHJlc3MgYmFyIGNv
bG91ci4gSWYgYSB1c2VyIGRpZG7igJl0IGtub3cgaWYgdGhlIFVSTCB3YXMgSFRUUCBvciBIVFRQ
UyAoZWcgdGhlaXIgYnJvd3NlciBhdXRvbWF0aWNhbGx5IHdlbnQgdGhlcmUgYWZ0ZXIgYW4gSFRU
UCAzMDcgcmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCcdW5jb25maXJtZWQgc2VjdXJpdHnigJ0g
YXMg4oCcdW5zZWN1cmVk4oCdIHdvdWxkIGJlIHJlYXNvbmFibGUuIE9uIHRoZSBvdGhlciBoYW5k
LCBpZiBJIGNob29zZSBteSBIVFRQUyBib29rbWFyayBmb3IgbXkgYmFuayB0aGVuIEkgZXhwZWN0
IG15IGJyb3dzZXIgbm90IHRvIHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMpIGh0
bWwvamF2YXNjcmlwdC9hY3RpdmV4L2ZsYXNoIGZvciBhbnkgb3RoZXIgc291cmNlLiBJZiBteSBi
cm93c2VyIChwZXJoYXBzIGR1ZSB0byBhIEROUyBhdHRhY2spIHNpbGVudGx5IGFjY2VwdGVkIGNv
bnRlbnQgbm90IGZyb20gbXkgYmFuayBJIHdvdWxkIGJlIHdvcnNlIG9mZi4NCg0KCSANCg0KCUFu
eSB2aXNpYmlsaXR5IG9mIGFuIEhUVFBTIFVSTCB0byB0aGUgdXNlciBjb3VsZCBiZSBjb25zaWRl
cmVkIGFzIHRoZW0gZXhwbGljaXRseSBzYXlpbmcgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eTog
Y2hvb3NpbmcgYW4gSFRUUFMgYm9va21hcms7IHR5cGluZyBIVFRQUyBpbnRvIHRoZSBhZGRyZXNz
IGJhcjsgY2xpY2tpbmcgb24gYW4gSFRUUFMgbGluayB3aGVuIHRoZSBVUkwgd2FzIHNob3duIGlu
IHRoZSBzdGF0dXMgYmFyIGJlZm9yZSB0aGUgY2xpY2s7IGV2ZW4gc2VlaW5nIEhUVFBTIGluIHRo
ZSBhZGRyZXNzIGJhciBhZnRlciByZWNlaXZpbmcgYSBwYWdlIGNhbiBiZSBlbm91Z2guDQoNCgkg
DQoNCgkgDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCglGcm9tOiBIYWxs
YW0tQmFrZXIsIFBoaWxsaXANCglTZW50OiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAzOjM3IEFNDQoJ
U3ViamVjdDogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsgbWVtYmVy
IHNpbmNlDQoNCgkgDQoNCgnigKYNCg0KCTMpIE5vIFBhZGxvY2sgSWNvbiBhdHRyaWJ1dGUNCg0K
CSANCg0KCSAgICBUaGlzIGF0dHJpYnV0ZSB3b3VsZCBhbGxvdyBhIGNlcnRpZmljYXRlIHRvIHNh
eSB0aGF0IG5vIHVzZXIgaW5kaWNhdGlvbiBzaG91bGQgYmUgc3BlY2lmaWVkIGluIHRoZSBjaHJv
bWUsIG5vciBzaG91bGQgYW55IG5hZyBzY3JlZW5zLiBJdCB3b3VsZCBiZSBhbiBvcHRpb24gdGhh
dCB0aGUgaXNzdWluZyBDQSB3b3VsZCBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi4NCg0KCSAN
Cg0KCSAgICBUaGUgbmVlZCBmb3IgdGhpcyBpcyB0byBhbGxvdyBhIENBIHRvIHN1cHBvcnQgYSB3
aWRlIHJhbmdlIG9mIGFwcGxpY2F0aW9ucyB3aGljaCByZXF1aXJlIGVuY3J5cHRpb24gYnV0IHJl
cXVpcmUgZXZlbiBsZXNzIGF1dGhlbnRpY2F0aW9uIHRoYW4gY3VycmVudCBzY2hlbWVzIHN1Y2gg
YXMgZG9tYWluIHZhbGlkYXRlZCBjZXJ0cy4gRm9yIGV4YW1wbGUgc2VsZiBzaWduZWQgY2VydGlm
aWNhdGVzLCBjZXJ0aWZpY2F0ZXMgaXNzdWVkIHRvIGVtYmVkZGVkIGhhcmR3YXJlLCBldGMuIGV0
Yy4NCg0KCSANCg0KCSAgICBXaGF0IEkgd2FudCB0byBkbyBpcyB0byBnZXQgdXMgdG8gdGhlIHBv
aW50IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbCBjb21mb3J0YWJsZSB3aXRoIGEgdXNl
ciBleHBlcmllbmNlIHRoYXQgZG9lcyBub3QgY29udGFpbiB0aGUgbmFnIHNjcmVlbnMgdGhhdCBk
aXNmaWd1cmUgY3VycmVudCBzY2hlbWVzLiBJbiBtYW55IGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVp
cmVkIGlzIHRvIHR1cm4gb24gZW5jcnlwdGlvbi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byBi
ZSB0b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBleHBpcmVkLCBoYXMgYmVlbiBpc3N1ZWQg
YnkgYW4gdW5rbm93biBDQSBvciBhbnkgb2YgdGhlIHVzdWFsIG5vbnNlbnNlLiBqdXN0IGRvbid0
IHRlbGwgdGhlIHVzZXIgdGhhdCBpdHMgc2FmZSBpbiB0aGUgZmlyc3QgcGxhY2UgYW5kIHRoZSBi
cm93c2VyIGRvZXMgbm90IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgZGFuZ2Vyb3VzLg0KDQoJIA0K
DQoJICAgIENsZWFybHkgdGhpcyBhdHRyaWJ1dGUgaXMgdW5uZWNlc3NhcnkgZnJvbSBhIHRlY2hu
aWNhbCBwb2ludCBvZiB2aWV3LiBGcm9tIGEgbWFya2V0IHBvaW50IG9mIHZpZXcgaXQgaXMgZXNz
ZW50aWFsIGlmIHdlIGFyZSBnb2luZyB0byBlbnN1cmUgdGhhdCBhcHBsaWNhdGlvbnMgYXJlIGRv
aW5nIHRoZSByaWdodCB0aGluZy4gVGhlIHBhZGxvY2sgaWNvbiBoYXMgc29tZSBwcmV0dHkgc3Ry
b25nIHNlbWFudGljcy4gTWFueSBhcHBsaWNhdGlvbnMgcmVxdWlyZSBsZXNzLiBXZSBhcmUgbm90
IGdvaW5nIHRvIGdldCBldmVyeW9uZSB3aG8gY3VycmVudGx5IGhhcyBhIHBhZGxvY2sgY2VydGlm
aWNhdGUgdG8gZ2V0IGEgZ3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2VydmUgdGhlIGFwcGxpY2F0
aW9ucyB0aGF0IHJlcXVpcmUgZXZlbiBsZXNzIHRoYW4gdGhlIHBhZGxvY2sgd2l0aG91dCBkaWx1
dGluZyB0aGUgcGFkbG9jayBzZW1hbnRpY3MgZnVydGhlci4NCg0KCQ0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCg0KDQoJRnJvbTogb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9y
ZyBbbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddIE9uIEJlaGFsZiBPZiBIYWxs
YW0tQmFrZXIsIFBoaWxsaXANCglTZW50OiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzowNiBBTQ0K
CVRvOiBLZW1wLCBEYXZpZCBQLjsgcGtpeA0KDQoJIA0KDQoJMykgTm8gUGFkbG9jayBJY29uIGF0
dHJpYnV0ZQ0KDQoJIA0KDQoJVGhlIHBvaW50IGhlcmUgaXMgcHJlY2lzZWx5IHRvIGFsbG93IGEg
Y2VydGlmaWNhdGUgdG8gc3RhdGUgJ3RoZXJlIGFyZSBubyBzZWN1cml0eSBjbGFpbXMgYmVpbmcg
bWFkZSBoZXJlJy4gDQoNCgkgDQoNCglUaGUgdXNlciBkb2VzIG5vdCBhY2NlcHQgdGhlIGNlcnRp
ZmljYXRlLCB0aGUgY2xpZW50IGFwcGxpY2F0aW9uIGRvZXMuIE5vIHVzZXIgaGFzIGV2ZXIgY2hl
Y2tlZCBhIGNlcnRpZmljYXRlIHBhdGggYW5kIG5vIHVzZXIgZXZlciB3aWxsLiBUaGUgcXVlc3Rp
b24gaXMgd2hldGhlciB0aGUgY2xpZW50IGFwcGxpY2F0aW9uIHNob3VsZCBiZSB0ZWxsaW5nIHRo
ZSB1c2VyIHRoYXQgaXQgaXMgJ3NhZmUnIG9yIG5vdC4NCg0KCSANCg0KCUkgZG9uJ3Qgc2VlIHdo
eSB3ZSBuZWVkIHRvIHRlbGwgdGhlIHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVzZWQg
dW5sZXNzIHRoZXkgaGF2ZSBleHBsaWNpdGx5IHNhaWQgdGhhdCB0aGV5IG5lZWQgY29uZmlkZW50
aWFsaXR5LiBUZWxsaW5nIHRoZSB1c2VyIHRoYXQgdGhlcmUgaXMgZW5jcnlwdGlvbiBtZWFucyBh
bHNvIHRlbGxpbmcgdGhlbSBhYm91dCBhIHdob2xlIHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhl
ciBlcnJvciBjb25kaXRpb25zLiANCg0KCV9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KCUZyb206IG93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcgW21haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8bWFpbHRvOiU1Ym1haWx0bzpvd25lci1p
ZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkPiAgT24gQmVoYWxmIE9mIEhhbGxhbS1CYWtlciwgUGhp
bGxpcA0KCVNlbnQ6IFR1ZXNkYXksIDEyIEp1bmUgMjAwNyAxMjoyNCBBTQ0KDQoJIA0KDQoJ4oCm
DQoNCglJIGNhbiBnaXZlIHlvdSBhIGNhc3QgaXJvbiBjaGFpbiBmb3IgYW4gRVVJNDggTUFDIGFk
ZHJlc3MuIEJ1dCBpdCBzYXlzIG5vdGhpbmcgdGhhdCBzaG91bGQgZ2l2ZSBhbiBlbmQgdXNlciB3
YXJtIGZ1enppZXMuDQoNCgkgDQoNCgkgDQoNCgknVGhpcyBjZXJ0IG1ha2VzIG5vIHNlY3VyaXR5
IGNsYWltcyB0aGF0IGFyZSB3b3J0aCBkaXNwbGF5IHRvIGFuIGVuZCB1c2VyJy4NCg0KCeKApg0K
DQoJX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJRnJvbTog
b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyBbbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWls
LmltYy5vcmddIDxtYWlsdG86JTVibWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcl
NWQ+ICBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQaGlsbGlwDQoJU2VudDogVHVlc2RheSwg
MTIgSnVuZSAyMDA3IDM6NDUgQU0NCg0KCSANCg0KCeKAplRoZSBpbmZvcm1hdGlvbiB0byBiZSBl
bmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0aGUgaXNzdWUgcHJhY3RpY2VzIG9mIHRoZSBjZXJ0aWZp
Y2F0ZS4gVGhlcmVmb3JlIHRoZXkgZ28gaW50byB0aGUgY2VydGlmaWNhdGUuDQoNCgkgDQoNCglU
aGVzZSBhcmUgbm90IGFub255bW91cyBjb21tdW5pY2F0aW9ucywgdGhleSBhcmUgbWVyZWx5IGNv
bW11bmljYXRpb25zIHRoYXQgZG8gbm90IHJlcXVpcmUgdGhlIGxldmVsIG9mIGFzc3VyYW5jZSB0
aGF0IGlzIG5lY2Vzc2FyeSB0byBhbGVydCB0aGUgdXNlciB0byB0ZWxsIHRoYW0gdGhhdCB0aGUg
Y29tbXVuaWNhdGlvbiBpcyBzZWN1cmUuDQoNCglfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCglGcm9tOiBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFtt
YWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gPG1haWx0bzolNWJtYWlsdG86b3du
ZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyU1ZD4gIE9uIEJlaGFsZiBPZiBIYWxsYW0tQmFrZXIs
IFBoaWxsaXANCglTZW50OiBUdWVzZGF5LCAxMiBKdW5lIDIwMDcgMTA6MDAgQU0NCg0KCSANCg0K
CUNhc2UgaW4gcG9pbnQgaGVyZSBiZWluZyB5b3VyIFMvTUlNRSBjZXJ0IHdoaWNoIGRvZXMgbm90
IHNhdGlzZnkgbXkgT3V0bG9vayBjaGFpbmluZyBzbyBnaXZlIGEgd2FybmluZy4NCg0KCSANCg0K
CVlldCBJIGNhbiBnZXQgbWFpbCBmcm9tIHBsZW50eSBvZiBwbGFjZXMgd2l0aG91dCBhbnkgc2Vj
dXJpdHkgYW5kIHdpdGhvdXQgYSB3YXJuaW5nIGVpdGhlci4NCg0KCSANCg0KCVdvdWxkbid0IGl0
IGJlIG5pY2UgaWYgYSBjZXJ0IGNvdWxkIHNheSAndGhlIGNvcnJlY3QgY291cnNlIG9mIGFjdGlv
biBpZiB5b3UgZG9uJ3QgbGlrZSBtZSBpcyB0byBzaW1wbHkgc2hvdyB0aGUgZW1haWwgd2l0aG91
dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyBzZWN1cmUnLg0KDQoJIA0KDQoJV2h5IGRv
IGZvbGsgZmVlbCB0aGF0IHRoZSB1c2VyIGhhcyB0byBiZSB0b2xkIGFib3V0IG1lcmVseSBzdWIt
c3RhbmRhcmQgc2VjdXJpdHkgd2hlbiA5OSUgb2YgdGhlIEludGVybmV0IGhhcyBubyBzZWN1cml0
eSBhdCBhbGw/DQoNCg==

------_=_NextPart_001_01C7B350.07C19428
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: base64

77u/PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9u
YWwvL0VOIj4NCjxIVE1MIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIiB4
bWxuczp2ID0gDQoidXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm8gPSANCiJ1
cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTpvZmZpY2UiIHhtbG5zOncgPSANCiJ1cm46
c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIj48SEVBRD4NCjxNRVRBIGh0dHAtZXF1
aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8TUVU
QSBjb250ZW50PSJNU0hUTUwgNi4wMC41NzMwLjExIiBuYW1lPUdFTkVSQVRPUj48IS0tW2lmICFt
c29dPg0KPFNUWUxFPnZcOiogew0KCUJFSEFWSU9SOiB1cmwoI2RlZmF1bHQjVk1MKQ0KfQ0Kb1w6
KiB7DQoJQkVIQVZJT1I6IHVybCgjZGVmYXVsdCNWTUwpDQp9DQp3XDoqIHsNCglCRUhBVklPUjog
dXJsKCNkZWZhdWx0I1ZNTCkNCn0NCi5zaGFwZSB7DQoJQkVIQVZJT1I6IHVybCgjZGVmYXVsdCNW
TUwpDQp9DQo8L1NUWUxFPg0KPCFbZW5kaWZdLS0+DQo8U1RZTEU+QGZvbnQtZmFjZSB7DQoJZm9u
dC1mYW1pbHk6IEFyaWFsIFVuaWNvZGUgTVM7DQp9DQpAZm9udC1mYWNlIHsNCglmb250LWZhbWls
eTogVGFob21hOw0KfQ0KQGZvbnQtZmFjZSB7DQoJZm9udC1mYW1pbHk6IEBBcmlhbCBVbmljb2Rl
IE1TOw0KfQ0KQHBhZ2UgU2VjdGlvbjEge3NpemU6IDU5NS4zcHQgODQxLjlwdDsgbWFyZ2luOiA3
Mi4wcHQgOTAuMHB0IDcyLjBwdCA5MC4wcHQ7IH0NClAuTXNvTm9ybWFsIHsNCglGT05ULVNJWkU6
IDEycHQ7IE1BUkdJTjogMGNtIDBjbSAwcHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFu
Ig0KfQ0KTEkuTXNvTm9ybWFsIHsNCglGT05ULVNJWkU6IDEycHQ7IE1BUkdJTjogMGNtIDBjbSAw
cHQ7IEZPTlQtRkFNSUxZOiAiVGltZXMgTmV3IFJvbWFuIg0KfQ0KRElWLk1zb05vcm1hbCB7DQoJ
Rk9OVC1TSVpFOiAxMnB0OyBNQVJHSU46IDBjbSAwY20gMHB0OyBGT05ULUZBTUlMWTogIlRpbWVz
IE5ldyBSb21hbiINCn0NCkE6bGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjog
dW5kZXJsaW5lDQp9DQpTUEFOLk1zb0h5cGVybGluayB7DQoJQ09MT1I6IGJsdWU7IFRFWFQtREVD
T1JBVElPTjogdW5kZXJsaW5lDQp9DQpBOnZpc2l0ZWQgew0KCUNPTE9SOiBibHVlOyBURVhULURF
Q09SQVRJT046IHVuZGVybGluZQ0KfQ0KU1BBTi5Nc29IeXBlcmxpbmtGb2xsb3dlZCB7DQoJQ09M
T1I6IGJsdWU7IFRFWFQtREVDT1JBVElPTjogdW5kZXJsaW5lDQp9DQpTUEFOLkVtYWlsU3R5bGUx
OCB7DQoJRk9OVC1XRUlHSFQ6IG5vcm1hbDsgQ09MT1I6IGJsdWU7IEZPTlQtU1RZTEU6IG5vcm1h
bDsgRk9OVC1GQU1JTFk6ICJBcmlhbCBVbmljb2RlIE1TIjsgVEVYVC1ERUNPUkFUSU9OOiBub25l
OyBtc28tc3R5bGUtdHlwZTogcGVyc29uYWwtcmVwbHkNCn0NCkRJVi5TZWN0aW9uMSB7DQoJcGFn
ZTogU2VjdGlvbjENCn0NCjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9EWSBsYW5nPUVOLUFVIHZMaW5r
PWJsdWUgbGluaz1ibHVlPg0KPERJViBkaXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkz
MzcyMTE1LTIwMDYyMDA3PjxGT05UIGZhY2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj5U
aGUgaXNzdWUgaGVyZSBpcyBiYWNrd2FyZHMgDQpjb21wYXRpYmlsaXR5LjwvRk9OVD48L1NQQU4+
PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAw
NjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQ
QU4+Jm5ic3A7PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMz
NzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPkFu
eSBjZXJ0aWZpY2F0ZSBpc3N1ZWQgdG9kYXkgbXVzdCB3b3JrIGFjY2FwdGFibHkgd2l0aCANCmV4
aXN0aW5nIGJyb3dzZXJzLiBUaGF0IG1lYW5zIGNoYWluaW5nIHVwIHRvIGFuIGVtYmVkZGVkIHJv
b3QuIFVuZGVyIHRoZSBydWxlcyANCmFzIHRoZXkgYXJlIHRvZGF5IGEgY2VydCBpc3N1ZXIgY2Fu
Jm5ic3A7aXNzdWUgYSBjZXJ0aWZpY2F0ZSB3aXRoIGVzc2VudGlhbGx5IG5vIA0KbWVhbmluZ2Z1
bCBhdXRoZW50aWNhdGlvbiBhbmQgbWFueSBkby48L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJViBk
aXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkzMzcyMTE1LTIwMDYyMDA3PjxGT05UIGZh
Y2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj48L0ZPTlQ+PC9TUEFOPiZuYnNwOzwvRElW
Pg0KPERJViBkaXI9bHRyIGFsaWduPWxlZnQ+PFNQQU4gY2xhc3M9NTkzMzcyMTE1LTIwMDYyMDA3
PjxGT05UIGZhY2U9QXJpYWwgDQpjb2xvcj0jMDAwMGZmIHNpemU9Mj5UaGUgcG9pbnQgaXMgdG8g
YWxsb3cgYW4gaXNzdWVyIHRvIGRpZmZlcmVudGlhdGUgYmV0d2VlbiANCmNlcnRpZmljYXRlcyB0
aGF0IGFyZSBkZXNpZ25lZCB0byBwcm92aWRlIGEgbWVhbmluZ2Z1bCBkZWdyZWUgb2YgYWNjb3Vu
dGFiaWxpdHkgDQpmcm9tIHRob3NlIHdoaWNoIGFyZSBzaW1wbHkgZGVzaWduZWQgdG8gdHVybiBv
biBTU0wgaW4gdGhlIGRlcGxveWVkIGJhc2Ugb2YgYSANCmJpbGxpb24gYnJvd3NlcnMuIE92ZXIg
dGltZSB0aGUgZGVwbG95bWVudCBvZiBicm93c2VycyB0aGF0IG9ic2VydmUgdGhlIE9JRCANCndv
dWxkIGluY3JlYXNlLjwvRk9OVD48L1NQQU4+PC9ESVY+DQo8RElWIGRpcj1sdHIgYWxpZ249bGVm
dD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1BcmlhbCANCmNvbG9y
PSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWIGRpcj1sdHIg
YWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQgZmFjZT1Bcmlh
bCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD48L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElW
IGRpcj1sdHIgYWxpZ249bGVmdD48U1BBTiBjbGFzcz01OTMzNzIxMTUtMjAwNjIwMDc+PEZPTlQg
ZmFjZT1BcmlhbCANCmNvbG9yPSMwMDAwZmYgc2l6ZT0yPklmIHdlIHdlcmUgZGVzaWduaW5nIGZy
b20gc2NyYXRjaCB0aGUgc2Vuc2libGUgd2F5IHRvIGRvIA0KdGhpcyB3b3VsZCBiZSB0byBoYXZl
IGFuIE9JRCB3aXRoIHBvc2l0aXZlIHNlbWFudGljcyAnYXNzZXJ0IHNlY3VyaXR5IHRvIHRoZSAN
CnVzZXInLiBTaW5jZSB3ZSBkb24ndCBoYXZlIHRoYXQgbHV4dXJ5IGFuZCBzaW5jZSB3ZSBoYXZl
IHRvIGRlYWwgd2l0aCB0aGUgDQpiaWxsaW9uIGRlcGxveWVkIGJyb3dzZXJzIHdlIG5lZWQgYSBk
aWZmZXJlbnQgYXBwcm9hY2guPC9GT05UPjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGln
bj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0K
Y29sb3I9IzAwMDBmZiBzaXplPTI+PC9GT05UPjwvU1BBTj4mbmJzcDs8L0RJVj4NCjxESVYgZGly
PWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNl
PUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXplPTI+SSBkbyBub3QgYWdyZWUgd2l0aCB0aGUgc2Vu
dGltZW50IHRoYXQgYSBzdGFuZGFyZHMgcHJvY2VzcyANCnNob3VsZCBvbmx5IGRlYWwgd2l0aCBw
ZXJmZWN0IHNpdHVhdGlvbnMgYW5kIHN0aWNrIGl0cyBoZWFkIGluIHRoZSBzYW5kIHdoZW4gaXQg
DQpjb21lcyB0byB0b3VnaCBkZXBsb3ltZW50IGlzc3Vlcy4gTWFuYWdpbmcgdGhlIGNvbnN0cmFp
bnRzIG9mIHRoZSBkZXBsb3llZCBiYXNlIA0Kc2hvdWxkIGJlIHRoZSBmaXJzdCBjb25jZXJuIGZv
ciBhIFdHIHRoYXQgaGFzIGJlZW4gaW4gZXhpc3RlbmNlIGZvciB0ZW4geWVhcnMuIA0KPC9GT05U
PjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNzPTU5MzM3
MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXplPTI+PC9G
T05UPjwvU1BBTj4mbmJzcDs8L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNs
YXNzPTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBz
aXplPTI+QXQgbGVhc3QgUEtJWCBoYXMgYSBkZXBsb3llZCBiYXNlIHRvIHdvcnJ5IA0KYWJvdXQu
PC9GT05UPjwvU1BBTj48L0RJVj4NCjxESVYgZGlyPWx0ciBhbGlnbj1sZWZ0PjxTUEFOIGNsYXNz
PTU5MzM3MjExNS0yMDA2MjAwNz48Rk9OVCBmYWNlPUFyaWFsIA0KY29sb3I9IzAwMDBmZiBzaXpl
PTI+PC9GT05UPjwvU1BBTj4mbmJzcDs8L0RJVj48QlI+DQo8QkxPQ0tRVU9URSBkaXI9bHRyIA0K
c3R5bGU9IlBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVGVDogNXB4OyBCT1JERVItTEVGVDog
IzAwMDBmZiAycHggc29saWQ7IE1BUkdJTi1SSUdIVDogMHB4Ij4NCiAgPERJViBjbGFzcz1PdXRs
b29rTWVzc2FnZUhlYWRlciBsYW5nPWVuLXVzIGRpcj1sdHIgYWxpZ249bGVmdD4NCiAgPEhSIHRh
YkluZGV4PS0xPg0KICA8Rk9OVCBmYWNlPVRhaG9tYSBzaXplPTI+PEI+RnJvbTo8L0I+IG93bmVy
LWlldGYtcGtpeEBtYWlsLmltYy5vcmcgDQogIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwu
aW1jLm9yZ10gPEI+T24gQmVoYWxmIE9mIDwvQj5NYW5nZXIsIEphbWVzIA0KICBIPEJSPjxCPlNl
bnQ6PC9CPiBTdW5kYXksIEp1bmUgMTcsIDIwMDcgOTozOSBQTTxCUj48Qj5Ubzo8L0I+IA0KICBw
a2l4PEJSPjxCPlN1YmplY3Q6PC9CPiBSRTogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7
IHRleHQgbG9nbzsgbWVtYmVyIA0KICBzaW5jZTxCUj48L0ZPTlQ+PEJSPjwvRElWPg0KICA8RElW
PjwvRElWPg0KICA8RElWIGNsYXNzPVNlY3Rpb24xPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQ
QU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTog
J0FyaWFsIFVuaWNvZGUgTVMnIj5JIGxpa2UgDQogIHRoZSBpZGVhIG9mIHJldmVydGluZyB0byBh
biDigJx1bnNlY3VyZWTigJ0gbG9vay1uLWZlZWwgYW5kIGF2b2lkaW5nIG5hZyBzY3JlZW5zIA0K
ICB3aGVuIHRoZSBzZWN1cml0eSwgdGhvdWdoIHByZXNlbnQsIGlzIG5vdCDigJxwZXJmZWN04oCd
LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBV
bmljb2RlIE1TJyI+SXQgaXMgDQogIGJhZCB0aGF0IG1hbnkgY2xpZW50cyB0cmVhdCB1bmNvbmZp
cm1lZCBzZWN1cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEgDQogIGxvY2FsbHktdHJ1c3Rl
ZCByb290KSBhcyB3b3JzZSB0aGFuIG5vIHNlY3VyaXR5LiBUaGlzIGRpc2NvdXJhZ2VzIGF0dGVt
cHRzIHRvIA0KICBpbXByb3ZlIHNlY3VyaXR5LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAg
Y2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjog
Ymx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+SSBhbSANCiAgbGVzcyBzdXJl
IHRoYXQgYSDigJxubyBwYWRsb2Nr4oCdIGF0dHJpYnV0ZSBpcyB0aGUgcmlnaHQgd2F5IHRvIGFj
aGlldmUgDQogIHRoaXMuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3Jt
YWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZB
TUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQog
IDxQIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOLUxFRlQ6IDM2cHQiPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogIzk5MzMwMDsgRk9OVC1GQU1JTFk6ICdBcmlh
bCBVbmljb2RlIE1TJyI+Jmd0O1dvdWxkbid0IA0KICBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3Vs
ZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgDQog
IG1lIGlzIHRvIHNpbXBseSBzaG93IHRoZSBlbWFpbCB3aXRob3V0IGFueSBpbmRpY2F0aW9uIHRo
ZSBtZXNzYWdlIGlzIA0KICBzZWN1cmUnLjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+PG86cD4mbmJzcDs8L286cD48L1NQ
QU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj5Xb3Vs
ZG7igJl0IA0KICBpdCBiZSBiZXR0ZXIgdG8gZml4IGVtYWlsIGNsaWVudHMgc28gdGhleSBhbHdh
eXMgYWN0IHRoaXMgd2F5LCBpbnN0ZWFkIG9mIG9ubHkgDQogIHRyaWdnZXJpbmcgdGhpcyBiZWhh
dmlvdXIgZm9yIGNlcnRhaW4gY2VydGlmaWNhdGVzPyBVbmxlc3MgaXQgaXMgYSB0YWN0aWNhbCAN
CiAgZGVjaXNpb24gdGhhdCBzb2Z0d2FyZSB2ZW5kb3JzIGFyZSBtb3JlIGxpa2VseSB0byBpbXBs
ZW1lbnQgYSBuZXcgY2VydGlmaWNhdGUgDQogIGZlYXR1cmUgdGhhbiBjaGFuZ2UgZXhpc3Rpbmcg
YmVoYXZpb3VyIChlc3BlY2lhbGx5IGlmIHRoZSBsYXR0ZXIgbWlnaHQgYmUgDQogIGJyYW5kZWQg
YXMgd29yc2VuaW5nIHNlY3VyaXR5KS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNz
PU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7
IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFO
PjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAx
MHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+Rm9yIA0K
ICBIVFRQUyBjb25uZWN0aW9ucywgYSBjZXJ0aWZpY2F0ZSB3aXRob3V0IGEgc3ViamVjdEFsdE5h
bWUuZE5TTmFtZSBmaWVsZCAoYW5kIA0KICBubyBkb21haW4gbmFtZSBpbiBhIGNvbW1vbiBuYW1l
IGNvbXBvbmVudCBvZiB0aGUgc3ViamVjdCBmaWVsZCkgc2hvdWxkIGJlIA0KICBzdWZmaWNpZW50
IGZvciBhIGJyb3dzZXIgdG8gc2F5IOKAnHdlbGwgSSBjYW5ub3QgZG8gdGhlIFVSTC10by1jZXJ0
IGNoZWNrIHNvIEkgDQogIHdpbGwgZGlzcGxheSB0aGUgcGFnZSBqdXN0IGxpa2UgYW4gSFRUUCBw
YWdl4oCdOiBubyBjb2xvdXJlZCBhZGRyZXNzIGJhciwgbm8gDQogIGxvY2tlZCBwYWRsb2NrLCBu
byBuYWcgc2NyZWVucywgc3RpbGwgdXNpbmcgVExTIG9uLXRoZS13aXJlIHRob3VnaC4gTm8gcGF0
aCB0byANCiAgYSB0cnVzdGVkIHJvb3QgKGVnIGEgc2VsZi1zaWduZWQgY2VydCkgc2hvdWxkIGJl
IHRyZWF0ZWQgdGhlIHNhbWUgd2F5LiANCiAgVW5hdmFpbGFibGUgQ1JMcyBjb3VsZCBiZSB0cmVh
dGVkIHRoZSBzYW1lIHdheS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05v
cm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQt
RkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4N
CiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBD
T0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+T3RoZXIgDQogIGVy
cm9ycyBzdWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUs
IG9yIGEgbWlzbWF0Y2ggDQogIGJldHdlZW4gVVJMICZhbXA7IGNlcnQgbmFtZSBpbXBseSB0aGUg
Y2VydGlmaWNhdGUgaG9sZGVyIGhhcyBkb25lIHNvbWV0aGluZyANCiAgd3JvbmcuIEkgZG9u4oCZ
dCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChvciBvdXRyaWdodCByZWZ1c2FsIHRv
IA0KICBjb25uZWN0KSBpbiB0aGVzZSBjYXNlcy48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQ
IGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6
IGJsdWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+
PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1T
SVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+
UFJPQkxFTTxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsIHN0eWxl
PSJNQVJHSU4tTEVGVDogMzZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENP
TE9SOiAjOTkzMzAwOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj4mZ3Q7IA0KICBJ
IGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlwdGlvbiBp
cyBiZWluZyB1c2VkIHVubGVzcyANCiAgdGhleSBoYXZlIGV4cGxpY2l0bHkgc2FpZCB0aGF0IHRo
ZXkgbmVlZCANCmNvbmZpZGVudGlhbGl0eS48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNs
YXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJs
dWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5ic3A7PC9vOnA+PC9T
UEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpF
OiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+VGhl
IA0KICBwcm9ibGVtIGlzIHRoYXQgdGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg
4oCcc2FmZeKAnSBjb25uZWN0aW9uLCANCiAgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBv
ciBhZGRyZXNzIGJhciBjb2xvdXIuIElmIGEgdXNlciBkaWRu4oCZdCBrbm93IGlmIA0KICB0aGUg
VVJMIHdhcyBIVFRQIG9yIEhUVFBTIChlZyB0aGVpciBicm93c2VyIGF1dG9tYXRpY2FsbHkgd2Vu
dCB0aGVyZSBhZnRlciBhbiANCiAgSFRUUCAzMDcgcmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCc
dW5jb25maXJtZWQgc2VjdXJpdHnigJ0gYXMg4oCcdW5zZWN1cmVk4oCdIHdvdWxkIA0KICBiZSBy
ZWFzb25hYmxlLiBPbiB0aGUgb3RoZXIgaGFuZCwgaWYgSSBjaG9vc2UgbXkgSFRUUFMgYm9va21h
cmsgZm9yIG15IGJhbmsgDQogIHRoZW4gSSBleHBlY3QgbXkgYnJvd3NlciA8ST5ub3Q8L0k+IHRv
IHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMpIA0KICBodG1sL2phdmFzY3JpcHQv
YWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNvdXJjZS4gSWYgbXkgYnJvd3NlciAocGVyaGFw
cyBkdWUgDQogIHRvIGEgRE5TIGF0dGFjaykgc2lsZW50bHkgYWNjZXB0ZWQgY29udGVudCBub3Qg
ZnJvbSBteSBiYW5rIEkgd291bGQgYmUgd29yc2UgDQogIG9mZi48bzpwPjwvbzpwPjwvU1BBTj48
L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBw
dDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiAnQXJpYWwgVW5pY29kZSBNUyciPjxvOnA+Jm5i
c3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHls
ZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmlj
b2RlIE1TJyI+QW55IA0KICB2aXNpYmlsaXR5IG9mIGFuIEhUVFBTIFVSTCB0byB0aGUgdXNlciBj
b3VsZCBiZSBjb25zaWRlcmVkIGFzIHRoZW0gZXhwbGljaXRseSANCiAgc2F5aW5nIHRoZXkgbmVl
ZCBjb25maWRlbnRpYWxpdHk6IGNob29zaW5nIGFuIEhUVFBTIGJvb2ttYXJrOyB0eXBpbmcgSFRU
UFMgDQogIGludG8gdGhlIGFkZHJlc3MgYmFyOyBjbGlja2luZyBvbiBhbiBIVFRQUyBsaW5rIHdo
ZW4gdGhlIFVSTCB3YXMgc2hvd24gaW4gdGhlIA0KICBzdGF0dXMgYmFyIGJlZm9yZSB0aGUgY2xp
Y2s7IGV2ZW4gc2VlaW5nIEhUVFBTIGluIHRoZSBhZGRyZXNzIGJhciBhZnRlciANCiAgcmVjZWl2
aW5nIGEgcGFnZSBjYW4gYmUgZW5vdWdoLjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6ICdBcmlhbCBVbmljb2RlIE1TJyI+PG86cD4mbmJzcDs8L286cD48L1NQ
QU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogJ0FyaWFsIFVuaWNvZGUgTVMnIj48bzpw
PiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxESVY+DQogIDxESVYgY2xhc3M9TXNvTm9ybWFs
IHN0eWxlPSJURVhULUFMSUdOOiBjZW50ZXIiIGFsaWduPWNlbnRlcj4NCiAgPEhSIHRhYkluZGV4
PS0xIGFsaWduPWNlbnRlciB3aWR0aD0iMTAwJSIgU0laRT0yPg0KICA8L0RJVj4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxCPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBGT05ULUZB
TUlMWTogVGFob21hIj5Gcm9tOjwvU1BBTj48L0I+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6
IDEwcHQ7IEZPTlQtRkFNSUxZOiBUYWhvbWEiPiBIYWxsYW0tQmFrZXIsIA0KICBQaGlsbGlwPEJS
PjxCPlNlbnQ6PC9CPiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAzOjM3IEFNPEJSPjxCPlN1YmplY3Q6
PC9CPiBUaHJlZSANCiAgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsgbWVtYmVy
IHNpbmNlPC9TUEFOPjxvOnA+PC9vOnA+PC9QPjwvRElWPg0KICA8RElWPg0KICA8UCBjbGFzcz1N
c29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+Jm5ic3A7PG86cD48L286cD48L1NQQU4+PC9QPjwvRElWPg0KICA8RElWPg0KICA8UCBj
bGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBi
bHVlOyBGT05ULUZBTUlMWTogQXJpYWwiPuKApjwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJVj4N
CiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTVFJPTkc+PFNQQU4gDQogIHN0eWxlPSJG
T05ULVNJWkU6IDEwcHQ7IEZPTlQtRkFNSUxZOiBBcmlhbCI+MykgTm8gUGFkbG9jayBJY29uIA0K
ICBhdHRyaWJ1dGU8L1NQQU4+PC9TVFJPTkc+PG86cD48L286cD48L1A+PC9ESVY+DQogIDxESVY+
DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJ
Vj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8U1BBTiANCiAgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5UaGlzIGF0dHJpYnV0ZSB3
b3VsZCBhbGxvdyBhIA0KICBjZXJ0aWZpY2F0ZSB0byBzYXkgdGhhdCBubyB1c2VyIGluZGljYXRp
b24gc2hvdWxkIGJlIHNwZWNpZmllZCBpbiB0aGUgY2hyb21lLCANCiAgbm9yIHNob3VsZCBhbnkg
bmFnIHNjcmVlbnMuIEl0IHdvdWxkIGJlIGFuIG9wdGlvbiB0aGF0IHRoZSBpc3N1aW5nIENBIHdv
dWxkIA0KICBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi48L1NQQU4+PG86cD48L286cD48L1A+
PC9ESVY+DQogIDxESVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwv
UD48L0RJVj4NCiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNw
OyA8U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5U
aGUgbmVlZCBmb3IgdGhpcyBpcyB0byBhbGxvdyBhIENBIA0KICB0byBzdXBwb3J0IGEgd2lkZSBy
YW5nZSBvZiBhcHBsaWNhdGlvbnMgd2hpY2gmbmJzcDtyZXF1aXJlIGVuY3J5cHRpb24gYnV0IA0K
ICByZXF1aXJlIGV2ZW4gbGVzcyBhdXRoZW50aWNhdGlvbiB0aGFuIGN1cnJlbnQgc2NoZW1lcyBz
dWNoIGFzIGRvbWFpbiB2YWxpZGF0ZWQgDQogIGNlcnRzLiBGb3IgZXhhbXBsZSBzZWxmIHNpZ25l
ZCBjZXJ0aWZpY2F0ZXMsIGNlcnRpZmljYXRlcyBpc3N1ZWQgdG8gZW1iZWRkZWQgDQogIGhhcmR3
YXJlLCBldGMuIGV0Yy48L1NQQU4+PG86cD48L286cD48L1A+PC9ESVY+DQogIDxESVY+DQogIDxQ
IGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJVj4NCiAg
PFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8U1BBTiANCiAgc3R5bGU9IkZP
TlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFsIj5XaGF0IEkgd2FudCB0byBkbyBpcyB0
byBnZXQgdXMgdG8gDQogIHRoZSBwb2ludCB3aGVyZSB0aGUgYnJvd3NlciBhdXRob3JzIGZlZWwg
Y29tZm9ydGFibGUgd2l0aCBhIHVzZXIgZXhwZXJpZW5jZSANCiAgdGhhdCBkb2VzIG5vdCBjb250
YWluIHRoZSBuYWcgc2NyZWVucyB0aGF0IGRpc2ZpZ3VyZSBjdXJyZW50IHNjaGVtZXMuIEluIG1h
bnkgDQogIGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVpcmVkIGlzIHRvIHR1cm4gb24gZW5jcnlwdGlv
bi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byANCiAgYmUgdG9sZCB0aGF0IHRoZSBjZXJ0aWZp
Y2F0ZSBoYXMgZXhwaXJlZCwgaGFzIGJlZW4gaXNzdWVkIGJ5IGFuIHVua25vd24gQ0Egb3IgDQog
IGFueSBvZiB0aGUgdXN1YWwgbm9uc2Vuc2UuIGp1c3QgZG9uJ3QgdGVsbCB0aGUgdXNlciB0aGF0
IGl0cyBzYWZlIGluIHRoZSBmaXJzdCANCiAgcGxhY2UgYW5kIHRoZSBicm93c2VyIGRvZXMgbm90
IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgDQogIGRhbmdlcm91cy48L1NQQU4+PG86cD48L286cD48
L1A+PC9ESVY+DQogIDxESVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpw
PjwvUD48L0RJVj4NCiAgPERJVj4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZu
YnNwOyA8U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgRk9OVC1GQU1JTFk6IEFyaWFs
Ij5DbGVhcmx5IHRoaXMgYXR0cmlidXRlIGlzIA0KICB1bm5lY2Vzc2FyeSBmcm9tIGEgdGVjaG5p
Y2FsIHBvaW50IG9mIHZpZXcuIEZyb20gYSBtYXJrZXQgcG9pbnQgb2YgdmlldyBpdCBpcyANCiAg
ZXNzZW50aWFsIGlmIHdlIGFyZSBnb2luZyB0byBlbnN1cmUgdGhhdCBhcHBsaWNhdGlvbnMgYXJl
IGRvaW5nIHRoZSByaWdodCANCiAgdGhpbmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJl
dHR5IHN0cm9uZyBzZW1hbnRpY3MuIE1hbnkgYXBwbGljYXRpb25zIA0KICByZXF1aXJlIGxlc3Mu
IFdlIGFyZSBub3QgZ29pbmcgdG8gZ2V0IGV2ZXJ5b25lIHdobyBjdXJyZW50bHkgaGFzIGEgcGFk
bG9jayANCiAgY2VydGlmaWNhdGUgdG8gZ2V0IGEgZ3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2Vy
dmUgdGhlIGFwcGxpY2F0aW9ucyB0aGF0IA0KICByZXF1aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBw
YWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcgdGhlIHBhZGxvY2sgc2VtYW50aWNzIA0KICBmdXJ0aGVy
LjwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJVj4NCiAgPERJViBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9IlRFWFQtQUxJR046IGNlbnRlciIgYWxpZ249Y2VudGVyPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogbmF2eTsgRk9OVC1GQU1JTFk6IEFyaWFsIj4NCiAgPEhSIHRh
YkluZGV4PS0xIGFsaWduPWNlbnRlciB3aWR0aD0iMTAwJSIgU0laRT0yPg0KICA8L1NQQU4+PC9E
SVY+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48Qj48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTog
MTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogVGFob21hIj5Gcm9tOjwvU1BBTj48L0I+
PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1J
TFk6IFRhaG9tYSI+IA0KICBvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFttYWlsdG86b3du
ZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ10gPEI+T24gDQogIEJlaGFsZiBPZiA8L0I+SGFsbGFt
LUJha2VyLCBQaGlsbGlwPEJSPjxCPlNlbnQ6PC9CPiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzow
NiANCiAgQU08QlI+PEI+VG86PC9CPiBLZW1wLCBEYXZpZCBQLjsgcGtpeDwvU1BBTj48U1BBTiAN
CiAgc3R5bGU9IkNPTE9SOiBuYXZ5Ij48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNz
PU1zb05vcm1hbD48U1BBTiBzdHlsZT0iQ09MT1I6IGJsYWNrIj4mbmJzcDs8bzpwPjwvbzpwPjwv
U1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1RST05HPjxTUEFOIA0KICBzdHlsZT0i
Rk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+MykgTm8g
UGFkbG9jayBJY29uIA0KICBhdHRyaWJ1dGU8L1NQQU4+PC9TVFJPTkc+PFNQQU4gc3R5bGU9IkNP
TE9SOiBibGFjayI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+
PFNQQU4gc3R5bGU9IkNPTE9SOiBuYXZ5Ij48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQog
IDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09M
T1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlhbCI+VGhlJm5ic3A7cG9pbnQgaGVyZSANCiAgaXMg
cHJlY2lzZWx5IHRvIGFsbG93IGEgY2VydGlmaWNhdGUgdG8gc3RhdGUgJ3RoZXJlIGFyZSBubyBz
ZWN1cml0eSBjbGFpbXMgDQogIGJlaW5nIG1hZGUgaGVyZScuJm5ic3A7PC9TUEFOPjxTUEFOIHN0
eWxlPSJDT0xPUjogbmF2eSI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29O
b3JtYWw+PFNQQU4gc3R5bGU9IkNPTE9SOiBibGFjayI+Jm5ic3A7PC9TUEFOPjxTUEFOIA0KICBz
dHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6IEFyaWFsIj48
bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5
bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlhbCI+VGhl
IHVzZXIgZG9lcyBub3QgDQogIGFjY2VwdCB0aGUgY2VydGlmaWNhdGUsIHRoZSBjbGllbnQgYXBw
bGljYXRpb24gZG9lcy4gTm8gdXNlciBoYXMgZXZlciBjaGVja2VkIA0KICBhIGNlcnRpZmljYXRl
IHBhdGggYW5kIG5vIHVzZXIgZXZlciB3aWxsLiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB0aGUg
Y2xpZW50IA0KICBhcHBsaWNhdGlvbiBzaG91bGQgYmUgdGVsbGluZyB0aGUgdXNlciB0aGF0IGl0
IGlzICdzYWZlJyBvciANCiAgbm90LjxvOnA+PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9
TXNvTm9ybWFsPjxTUEFOIHN0eWxlPSJDT0xPUjogYmxhY2siPiZuYnNwOzwvU1BBTj48U1BBTiAN
CiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZOiBBcmlh
bCI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQog
IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibHVlOyBGT05ULUZBTUlMWTogQXJpYWwi
PkkgZG9uJ3Qgc2VlIHdoeSB3ZSANCiAgbmVlZCB0byB0ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlw
dGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhhdmUgDQogIGV4cGxpY2l0bHkgc2FpZCB0
aGF0IHRoZXkgbmVlZCBjb25maWRlbnRpYWxpdHkuIFRlbGxpbmcgdGhlIHVzZXIgdGhhdCB0aGVy
ZSBpcyANCiAgZW5jcnlwdGlvbiBtZWFucyBhbHNvIHRlbGxpbmcgdGhlbSBhYm91dCBhIHdob2xl
IHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhlciANCiAgZXJyb3IgY29uZGl0aW9ucy4gPG86cD48
L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9Ik1BUkdJTi1CT1RU
T006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsg
Rk9OVC1GQU1JTFk6IFRhaG9tYSI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fPEJSPjxCPkZyb206PC9CPiANCiAgPEEgaHJlZj0ibWFpbHRvOm93bmVyLWlldGYt
cGtpeEBtYWlsLmltYy5vcmciPm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmc8L0E+IA0KICA8
QSANCiAgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3Jn
JTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddPC9BPiANCiAgPEI+T24g
QmVoYWxmIE9mIDwvQj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8QlI+PEI+U2VudDo8L0I+IFR1ZXNk
YXksIDEyIEp1bmUgDQogIDIwMDcgMTI6MjQgQU08L1NQQU4+PFNQQU4gc3R5bGU9IkNPTE9SOiBi
bGFjayI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4g
DQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFy
aWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48
U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsdWU7IEZPTlQtRkFNSUxZ
OiBBcmlhbCI+4oCmPC9TUEFOPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xP
UjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8
UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9S
OiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5JIGNhbiBnaXZlIHlvdSBhIA0KICBjYXN0IGly
b24gY2hhaW4gZm9yIGFuIEVVSTQ4IE1BQyBhZGRyZXNzLiBCdXQgaXQgc2F5cyBub3RoaW5nIHRo
YXQgc2hvdWxkIGdpdmUgDQogIGFuIGVuZCB1c2VyIHdhcm0gZnV6emllcy48bzpwPjwvbzpwPjwv
U1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0la
RTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD4mbmJz
cDs8L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxl
PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj4nVGhp
cyBjZXJ0IG1ha2VzIG5vIA0KICBzZWN1cml0eSBjbGFpbXMgdGhhdCBhcmUgd29ydGggZGlzcGxh
eSB0byBhbiBlbmQgdXNlcicuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29O
b3JtYWwgc3R5bGU9Ik1BUkdJTi1CT1RUT006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJ
WkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+4oCmPC9TUEFOPjxT
UEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1ZTsgRk9OVC1GQU1JTFk6
IFRhaG9tYSI+PG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWwgc3R5
bGU9Ik1BUkdJTi1CT1RUT006IDZwdCI+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7
IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IFRhaG9tYSI+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPEJSPjxCPkZyb206PC9CPiANCiAgPEEgaHJlZj0ibWFp
bHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmciPm93bmVyLWlldGYtcGtpeEBtYWlsLmlt
Yy5vcmc8L0E+IA0KICA8QSANCiAgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBr
aXhAbWFpbC5pbWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmdd
PC9BPiANCiAgPEI+T24gQmVoYWxmIE9mIDwvQj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8QlI+PEI+
U2VudDo8L0I+IFR1ZXNkYXksIDEyIEp1bmUgDQogIDIwMDcgMzo0NSBBTTwvU1BBTj48U1BBTiBz
dHlsZT0iQ09MT1I6IGJsYWNrIj48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1z
b05vcm1hbD48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBG
T05ULUZBTUlMWTogQXJpYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xh
c3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmx1
ZTsgRk9OVC1GQU1JTFk6IEFyaWFsIj7igKY8L1NQQU4+PFNQQU4gDQogIHN0eWxlPSJGT05ULVNJ
WkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5UaGUgaW5mb3JtYXRp
b24gdG8gDQogIGJlIGVuY29kZWQgaGVyZSByZWxhdGVzIHRvIHRoZSBpc3N1ZSBwcmFjdGljZXMg
b2YgdGhlIGNlcnRpZmljYXRlLiBUaGVyZWZvcmUgDQogIHRoZXkgZ28gaW50byB0aGUgY2VydGlm
aWNhdGUuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4g
DQogIHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFy
aWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48
U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlM
WTogQXJpYWwiPlRoZXNlIGFyZSBub3QgDQogIGFub255bW91cyBjb21tdW5pY2F0aW9ucywgdGhl
eSBhcmUgbWVyZWx5IGNvbW11bmljYXRpb25zIHRoYXQgZG8gbm90IHJlcXVpcmUgDQogIHRoZSBs
ZXZlbCBvZiBhc3N1cmFuY2UgdGhhdCBpcyBuZWNlc3NhcnkgdG8gYWxlcnQgdGhlIHVzZXIgdG8g
dGVsbCB0aGFtIHRoYXQgDQogIHRoZSBjb21tdW5pY2F0aW9uIGlzIHNlY3VyZS48bzpwPjwvbzpw
PjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0iTUFSR0lOLUJPVFRPTTog
NnB0Ij48U1BBTiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05U
LUZBTUlMWTogVGFob21hIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX188QlI+PEI+RnJvbTo8L0I+IA0KICA8QSBocmVmPSJtYWlsdG86b3duZXItaWV0Zi1wa2l4
QG1haWwuaW1jLm9yZyI+b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZzwvQT4gDQogIDxBIA0K
ICBocmVmPSJtYWlsdG86JTVibWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmclNWQi
PlttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZ108L0E+IA0KICA8Qj5PbiBCZWhh
bGYgT2YgPC9CPkhhbGxhbS1CYWtlciwgUGhpbGxpcDxCUj48Qj5TZW50OjwvQj4gVHVlc2RheSwg
MTIgSnVuZSANCiAgMjAwNyAxMDowMCBBTTwvU1BBTj48U1BBTiBzdHlsZT0iQ09MT1I6IGJsYWNr
Ij48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAg
c3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFO
IA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+Q2FzZSBpbiBwb2ludCBoZXJlIA0KICBiZWluZyB5b3VyIFMvTUlNRSBjZXJ0IHdoaWNo
IGRvZXMgbm90IHNhdGlzZnkgbXkgT3V0bG9vayBjaGFpbmluZyBzbyBnaXZlIGEgDQogIHdhcm5p
bmcuPG86cD48L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQog
IHN0eWxlPSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BB
TiANCiAgc3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTog
QXJpYWwiPllldCBJIGNhbiBnZXQgbWFpbCANCiAgZnJvbSBwbGVudHkgb2YgcGxhY2VzIHdpdGhv
dXQgYW55IHNlY3VyaXR5IGFuZCB3aXRob3V0IGEgd2FybmluZyANCiAgZWl0aGVyLjxvOnA+PC9v
OnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFOIA0KICBzdHlsZT0iRk9O
VC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBBcmlhbCI+PG86cD4mbmJz
cDs8L286cD48L1NQQU4+PC9QPg0KICA8UCBjbGFzcz1Nc29Ob3JtYWw+PFNQQU4gDQogIHN0eWxl
PSJGT05ULVNJWkU6IDEwcHQ7IENPTE9SOiBibGFjazsgRk9OVC1GQU1JTFk6IEFyaWFsIj5Xb3Vs
ZG4ndCBpdCBiZSBuaWNlIA0KICBpZiBhIGNlcnQgY291bGQgc2F5ICd0aGUgY29ycmVjdCBjb3Vy
c2Ugb2YgYWN0aW9uIGlmIHlvdSBkb24ndCBsaWtlIG1lIGlzIHRvIA0KICBzaW1wbHkgc2hvdyB0
aGUgZW1haWwgd2l0aG91dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyANCiAgc2VjdXJl
Jy48bzpwPjwvbzpwPjwvU1BBTj48L1A+DQogIDxQIGNsYXNzPU1zb05vcm1hbD48U1BBTiANCiAg
c3R5bGU9IkZPTlQtU0laRTogMTBwdDsgQ09MT1I6IGJsYWNrOyBGT05ULUZBTUlMWTogQXJpYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9TUEFOPjwvUD4NCiAgPFAgY2xhc3M9TXNvTm9ybWFsPjxTUEFO
IA0KICBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0OyBDT0xPUjogYmxhY2s7IEZPTlQtRkFNSUxZOiBB
cmlhbCI+V2h5IGRvIGZvbGsgZmVlbCANCiAgdGhhdCB0aGUgdXNlciBoYXMgdG8gYmUgdG9sZCBh
Ym91dCBtZXJlbHkgc3ViLXN0YW5kYXJkIHNlY3VyaXR5IHdoZW4gOTklIG9mIA0KICB0aGUgSW50
ZXJuZXQgaGFzIG5vIHNlY3VyaXR5IGF0IA0KYWxsPzwvU1BBTj48bzpwPjwvbzpwPjwvUD48L0RJ
Vj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg==

------_=_NextPart_001_01C7B350.07C19428--



Received: from rotex-ce2b9322b (CMPC017-119.CNet2.Gawex.PL [84.205.17.119]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5KFGmTD087504; Wed, 20 Jun 2007 08:16:55 -0700 (MST) (envelope-from nehpipettetechsot@pipettetech.com)
Received: from 209.216.205.25 (HELO www.pipettetech.com) by imc.org with esmtp (N-3*/L4AL 2D*2+) id (7UK)O-),Q'81-U3 for ietf-pkix-oid-reg@imc.org; Wed, 20 Jun 2007 15:16:59 -0100
Date: 	Wed, 20 Jun 2007 15:16:59 -0100
From: "Sharon Brock" <nehpipettetechsot@pipettetech.com>
X-Mailer: The Bat! (v3.5.30) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <676037965.83184200428008@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Other guys are improving themselves..are you? 
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------77777777EA1467E3"
X-Spam: Not detected

------------77777777EA1467E3
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit



After all the genuine stuff – with no more swindle! 
P.E.P. are very hot right this time! Well here comes the original thing not a forgery! 

One of the very prominents, absolutely unrivalled produce is available anywhere!
 Pay attention to just what people tell on this produce:

"I was really impressed how swiftly this product affected on my boyfriend, he can’t put an end to his jabber on how hot he is with his new calibre, length, and libido!"

Lusia R., Chicago

"In the beginning I considered the free specimen  I was given was a prank, until I tried P.E.P. No words can report how highly satisfied I am with the consequences I achieved from using this remedy after 2 brief months. I will be requesting constantly!" 
Dave Klark, Colorado

Look at more references about this amazing product right here and right now!
http://www.promfore.com/?iaujzarvotirp

------------77777777EA1467E3
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Why be an average guy any longer</TITLE>
</HEAD>
<BODY>

<b>
After all the genuine stuff – with no more swindle! 
<br>
<a href="http://www.promfore.com/?iaujzarvotirp" target="_blank">P.E.P.</a> are very hot right this time! Well here comes the original thing not a forgery! 
<br>
One of the very prominents, absolutely unrivalled produce is available anywhere!
<br> Pay attention to just what people tell on this produce:
<p>
<i>
"I was really impressed how swiftly this product affected on my boyfriend, he can’t put an end to his jabber on how hot he is with his new calibre, length, and libido!"
</i>
</p>
Lusia R., Chicago
<p>
<i>
"In the beginning I considered the free specimen  I was given was a prank, until I tried P.E.P. No words can report how highly satisfied I am with the consequences I achieved from using this remedy after 2 brief months. I will be requesting constantly!" </i>
</p>
Dave Klark, Colorado
<center>
<a href="http://www.promfore.com/?iaujzarvotirp" target="_blank">
Look at more references about this amazing product right here and right now!
</a>
</center>
</b>
<font color="#D9EDFF">http://www.promfore.com/?iaujzarvotirp</font>

</BODY></HTML>
------------77777777EA1467E3--



Received: from epix.net (bngr-207-7-166-21-pppoe.dsl.bngr.epix.net [207.7.166.21]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l5KF7mTI086066 for <ietf-pkix-archive@imc.org>; Wed, 20 Jun 2007 08:07:58 -0700 (MST) (envelope-from Jeanninehavocoriental@form1023help.com)
Date: Wed, 20 Jun 2007 08:07:48 -0700 (MST)
Message-Id: <200706201507.l5KF7mTI086066@balder-227.proper.com>
Received: from seth by form1023help.com with SMTP id Fi3xVZGsia for <ietf-pkix-archive@imc.org>; Wed, 20 Jun 2007 11:07:36 +0500
From: "Dale Abernathy" <Jeanninehavocoriental@form1023help.com>
To: ietf-pkix-archive@imc.org
Subject: Want to lose the pounds?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Weight is a major problem everywhere.  Many people battle the bulge every day and hope that they will find a diet that works for them.  However, you don't need a fad diet to lose weight.  You don't need expensive gym memberships either.  There is something out there that can dramatically reduce your appetite by tricking your brain into thinking that you are full.

http://www.eirkf.com/

People eat for lots of different reasons, hunger isn't the only one.  There are many reasons why people resort to food as a comforter but old habits die hard.  What if I were to tell you that there is a simple way to lose weight?  A way that, the television favourite, Oprah herself claims to work!  Want to know what she recommends?

http://www.eirkf.com/

Cosmetic surgeries and diets are quick and easy ways out but they also have side effects that can't be avoided, not only that but the bills from surgeries are astronomical!  Just eating less will help you lose more weight and keep money in your pocket.  Harder said than done?  Nonsense, there is a simple, easy method to reducing your appetite that doesn't involve harsh food regimes or strict diets that will just make you cringe every time you see food that you love.  If you want to eat what you always eat but still lose weight and feel great then click below.

http://www.eirkf.com/

The wagon was reversing down the driveway before he got his door all the way closed. Things had a way of dropping out of Annies mind once the immediate moment was past.

Abby Ledford


Received: from cpc2-ware3-0-0-cust84.lutn.cable.ntl.com (cpc2-ware3-0-0-cust84.lutn.cable.ntl.com [86.13.228.85]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5J8UdoZ095901; Tue, 19 Jun 2007 01:30:42 -0700 (MST) (envelope-from pilpeomichiganhev@peomichigan.org)
Received: from 208.64.136.201 (HELO mail.peomichigan.org) by imc.org with esmtp (N3M/(=Q; A81(.E) id H(*0,K-9044D+-A6 for abuse@imc.org; Tue, 19 Jun 2007 08:30:46 +0000
Date: 	Tue, 19 Jun 2007 08:30:46 +0000
From: "Harriet Rushing" <pilpeomichiganhev@peomichigan.org>
X-Mailer: The Bat! (v2.00) Personal
X-Priority: 3 (Normal)
Message-ID: <854592612.38735292830023@thhebat.net>
To: abuse@imc.org
Subject: Make her worship you
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------E82136E80C513DA2"
X-Spam: Not detected

------------E82136E80C513DA2
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Finally the true stuff =96 with no rip offs! 
P.E.P. are piping hot at this time! This is the genuine thing not a=20=
fictitious one! 

One of the very exceptionals, absolutely unrivalled stuff is easy=20=
accessible at any place!
 Note what people say about this produce:

"I was really impressed how fast this product worked on my boyfriend,=20=
he can not stop chatting on how hot he is with his new size, length, and=20=
libido!"

Amelia B., New York

"At the beginning I considered the specimen package I acquired gratis=20=
was a kind of joke, until I have takentaking the P.E.P. There are no=20=
words to report how greatly satisfied I am with the result I achieved=20=
from using this patch after 6 brief weeks. I will be asking for P.E.P.=20=
continually!" 
Charley Mock, Bellevue WA

Read more testimonies on this amazing product right here & right now!
http://www.promfore.com/?jpgfsufme
------------E82136E80C513DA2
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Other guys are improving themselves..are you? </TITLE>
</HEAD>
<BODY>

<b>
Finally the true stuff =96 with no rip offs! 
<br>
<a href=3D"http://www.promfore.com/?jpgfsufme"=20=
target=3D"_blank">P.E.P.</a> are piping hot at this time! This is the=20=
genuine thing not a fictitious one! 
<br>
One of the very exceptionals, absolutely unrivalled stuff is easy=20=
accessible at any place!
<br> Note what people say about this produce:
<p>
<i>
"I was really impressed how fast this product worked on my boyfriend,=20=
he can not stop chatting on how hot he is with his new size, length, and=20=
libido!"
</i>
</p>
Amelia B., New York
<p>
<i>
"At the beginning I considered the specimen package I acquired gratis=20=
was a kind of joke, until I have takentaking the P.E.P. There are no=20=
words to report how greatly satisfied I am with the result I achieved=20=
from using this patch after 6 brief weeks. I will be asking for P.E.P.=20=
continually!" </i>
</p>
Charley Mock, Bellevue WA
<center>
<a href=3D"http://www.promfore.com/?jpgfsufme" target=3D"_blank">
Read more testimonies on this amazing product right here & right now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.promfore.com/?jpgfsufme</font>

</BODY></HTML>
------------E82136E80C513DA2--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5I1dj4F059066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Jun 2007 18:39:45 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5I1djfd059065; Sun, 17 Jun 2007 18:39:45 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailipbo.ntcif.telstra.com.au (mailipbo.ntcif.telstra.com.au [202.12.233.29]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5I1dgCV059047 for <ietf-pkix@imc.org>; Sun, 17 Jun 2007 18:39:43 -0700 (MST) (envelope-from James.H.Manger@team.telstra.com)
Received: from unknown (HELO mailbi.ntcif.telstra.com.au) ([202.12.162.19]) by mailipbi.ntcif.telstra.com.au with ESMTP; 18 Jun 2007 11:39:41 +1000
Received: from mail2.cdn.telstra.com.au (localhost [127.0.0.1]) by mailbi.ntcif.telstra.com.au (Postfix) with ESMTP id F3154FF87 for <ietf-pkix@imc.org>; Mon, 18 Jun 2007 11:39:37 +1000 (EST)
Received: from wsmsg2902.srv.dir.telstra.com (wsmsg2902.srv.dir.telstra.com [172.49.40.51]) by mail2.cdn.telstra.com.au (Postfix) with ESMTP id 042C541E1C for <ietf-pkix@imc.org>; Mon, 18 Jun 2007 11:39:16 +1000 (EST)
Received: from WSMSG2103V.srv.dir.telstra.com ([172.49.40.20]) by wsmsg2902.srv.dir.telstra.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Jun 2007 11:39:15 +1000
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_01C7B149.7A9E4C70"
Subject: RE: Three short fixes: no padlock; text logo; member since
Date: Mon, 18 Jun 2007 11:39:13 +1000
Message-ID: <6215401E01247448A306C54F499111F202BB51C8@WSMSG2103V.srv.dir.telstra.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes: no padlock; text logo; member since
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgKZqHkA
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 18 Jun 2007 01:39:15.0471 (UTC) FILETIME=[7AD2C1F0:01C7B149]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B149.7A9E4C70
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SSBsaWtlIHRoZSBpZGVhIG9mIHJldmVydGluZyB0byBhbiDigJx1bnNlY3VyZWTigJ0gbG9vay1u
LWZlZWwgYW5kIGF2b2lkaW5nIG5hZyBzY3JlZW5zIHdoZW4gdGhlIHNlY3VyaXR5LCB0aG91Z2gg
cHJlc2VudCwgaXMgbm90IOKAnHBlcmZlY3TigJ0uDQoNCkl0IGlzIGJhZCB0aGF0IG1hbnkgY2xp
ZW50cyB0cmVhdCB1bmNvbmZpcm1lZCBzZWN1cml0eSAoZWcgc2lnbmVkLCBidXQgbm90IGJ5IGEg
bG9jYWxseS10cnVzdGVkIHJvb3QpIGFzIHdvcnNlIHRoYW4gbm8gc2VjdXJpdHkuIFRoaXMgZGlz
Y291cmFnZXMgYXR0ZW1wdHMgdG8gaW1wcm92ZSBzZWN1cml0eS4NCg0KSSBhbSBsZXNzIHN1cmUg
dGhhdCBhIOKAnG5vIHBhZGxvY2vigJ0gYXR0cmlidXRlIGlzIHRoZSByaWdodCB3YXkgdG8gYWNo
aWV2ZSB0aGlzLg0KDQogDQoNCj5Xb3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBz
YXkgJ3RoZSBjb3JyZWN0IGNvdXJzZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMg
dG8gc2ltcGx5IHNob3cgdGhlIGVtYWlsIHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3Nh
Z2UgaXMgc2VjdXJlJy4NCg0KIA0KDQpXb3VsZG7igJl0IGl0IGJlIGJldHRlciB0byBmaXggZW1h
aWwgY2xpZW50cyBzbyB0aGV5IGFsd2F5cyBhY3QgdGhpcyB3YXksIGluc3RlYWQgb2Ygb25seSB0
cmlnZ2VyaW5nIHRoaXMgYmVoYXZpb3VyIGZvciBjZXJ0YWluIGNlcnRpZmljYXRlcz8gVW5sZXNz
IGl0IGlzIGEgdGFjdGljYWwgZGVjaXNpb24gdGhhdCBzb2Z0d2FyZSB2ZW5kb3JzIGFyZSBtb3Jl
IGxpa2VseSB0byBpbXBsZW1lbnQgYSBuZXcgY2VydGlmaWNhdGUgZmVhdHVyZSB0aGFuIGNoYW5n
ZSBleGlzdGluZyBiZWhhdmlvdXIgKGVzcGVjaWFsbHkgaWYgdGhlIGxhdHRlciBtaWdodCBiZSBi
cmFuZGVkIGFzIHdvcnNlbmluZyBzZWN1cml0eSkuDQoNCiANCg0KRm9yIEhUVFBTIGNvbm5lY3Rp
b25zLCBhIGNlcnRpZmljYXRlIHdpdGhvdXQgYSBzdWJqZWN0QWx0TmFtZS5kTlNOYW1lIGZpZWxk
IChhbmQgbm8gZG9tYWluIG5hbWUgaW4gYSBjb21tb24gbmFtZSBjb21wb25lbnQgb2YgdGhlIHN1
YmplY3QgZmllbGQpIHNob3VsZCBiZSBzdWZmaWNpZW50IGZvciBhIGJyb3dzZXIgdG8gc2F5IOKA
nHdlbGwgSSBjYW5ub3QgZG8gdGhlIFVSTC10by1jZXJ0IGNoZWNrIHNvIEkgd2lsbCBkaXNwbGF5
IHRoZSBwYWdlIGp1c3QgbGlrZSBhbiBIVFRQIHBhZ2XigJ06IG5vIGNvbG91cmVkIGFkZHJlc3Mg
YmFyLCBubyBsb2NrZWQgcGFkbG9jaywgbm8gbmFnIHNjcmVlbnMsIHN0aWxsIHVzaW5nIFRMUyBv
bi10aGUtd2lyZSB0aG91Z2guIE5vIHBhdGggdG8gYSB0cnVzdGVkIHJvb3QgKGVnIGEgc2VsZi1z
aWduZWQgY2VydCkgc2hvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5LiBVbmF2YWlsYWJsZSBD
UkxzIGNvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5Lg0KDQogDQoNCk90aGVyIGVycm9ycyBz
dWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yIGEg
bWlzbWF0Y2ggYmV0d2VlbiBVUkwgJiBjZXJ0IG5hbWUgaW1wbHkgdGhlIGNlcnRpZmljYXRlIGhv
bGRlciBoYXMgZG9uZSBzb21ldGhpbmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3
aXRoIG5hZyBzY3JlZW5zIChvciBvdXRyaWdodCByZWZ1c2FsIHRvIGNvbm5lY3QpIGluIHRoZXNl
IGNhc2VzLg0KDQogDQoNClBST0JMRU0NCg0KPiBJIGRvbid0IHNlZSB3aHkgd2UgbmVlZCB0byB0
ZWxsIHRoZSB1c2VyIHRoYXQgZW5jcnlwdGlvbiBpcyBiZWluZyB1c2VkIHVubGVzcyB0aGV5IGhh
dmUgZXhwbGljaXRseSBzYWlkIHRoYXQgdGhleSBuZWVkIGNvbmZpZGVudGlhbGl0eS4NCg0KIA0K
DQpUaGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBIVFRQUyBzY2hlbWUgaW4gYSBVUkwgaW1wbGllcyBh
IOKAnHNhZmXigJ0gY29ubmVjdGlvbiwgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBvciBh
ZGRyZXNzIGJhciBjb2xvdXIuIElmIGEgdXNlciBkaWRu4oCZdCBrbm93IGlmIHRoZSBVUkwgd2Fz
IEhUVFAgb3IgSFRUUFMgKGVnIHRoZWlyIGJyb3dzZXIgYXV0b21hdGljYWxseSB3ZW50IHRoZXJl
IGFmdGVyIGFuIEhUVFAgMzA3IHJlZGlyZWN0KSB0aGVuIHRyZWF0aW5nIOKAnHVuY29uZmlybWVk
IHNlY3VyaXR54oCdIGFzIOKAnHVuc2VjdXJlZOKAnSB3b3VsZCBiZSByZWFzb25hYmxlLiBPbiB0
aGUgb3RoZXIgaGFuZCwgaWYgSSBjaG9vc2UgbXkgSFRUUFMgYm9va21hcmsgZm9yIG15IGJhbmsg
dGhlbiBJIGV4cGVjdCBteSBicm93c2VyIG5vdCB0byBwcm9jZXNzIGFueSAocG90ZW50aWFsbHkt
bWFsaWNpb3VzKSBodG1sL2phdmFzY3JpcHQvYWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNv
dXJjZS4gSWYgbXkgYnJvd3NlciAocGVyaGFwcyBkdWUgdG8gYSBETlMgYXR0YWNrKSBzaWxlbnRs
eSBhY2NlcHRlZCBjb250ZW50IG5vdCBmcm9tIG15IGJhbmsgSSB3b3VsZCBiZSB3b3JzZSBvZmYu
DQoNCiANCg0KQW55IHZpc2liaWxpdHkgb2YgYW4gSFRUUFMgVVJMIHRvIHRoZSB1c2VyIGNvdWxk
IGJlIGNvbnNpZGVyZWQgYXMgdGhlbSBleHBsaWNpdGx5IHNheWluZyB0aGV5IG5lZWQgY29uZmlk
ZW50aWFsaXR5OiBjaG9vc2luZyBhbiBIVFRQUyBib29rbWFyazsgdHlwaW5nIEhUVFBTIGludG8g
dGhlIGFkZHJlc3MgYmFyOyBjbGlja2luZyBvbiBhbiBIVFRQUyBsaW5rIHdoZW4gdGhlIFVSTCB3
YXMgc2hvd24gaW4gdGhlIHN0YXR1cyBiYXIgYmVmb3JlIHRoZSBjbGljazsgZXZlbiBzZWVpbmcg
SFRUUFMgaW4gdGhlIGFkZHJlc3MgYmFyIGFmdGVyIHJlY2VpdmluZyBhIHBhZ2UgY2FuIGJlIGVu
b3VnaC4NCg0KIA0KDQogDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCkZy
b206IEhhbGxhbS1CYWtlciwgUGhpbGxpcA0KU2VudDogVHVlc2RheSwgNSBKdW5lIDIwMDcgMzoz
NyBBTQ0KU3ViamVjdDogVGhyZWUgc2hvcnQgZml4ZXM6IG5vIHBhZGxvY2s7IHRleHQgbG9nbzsg
bWVtYmVyIHNpbmNlDQoNCiANCg0K4oCmDQoNCjMpIE5vIFBhZGxvY2sgSWNvbiBhdHRyaWJ1dGUN
Cg0KIA0KDQogICAgVGhpcyBhdHRyaWJ1dGUgd291bGQgYWxsb3cgYSBjZXJ0aWZpY2F0ZSB0byBz
YXkgdGhhdCBubyB1c2VyIGluZGljYXRpb24gc2hvdWxkIGJlIHNwZWNpZmllZCBpbiB0aGUgY2hy
b21lLCBub3Igc2hvdWxkIGFueSBuYWcgc2NyZWVucy4gSXQgd291bGQgYmUgYW4gb3B0aW9uIHRo
YXQgdGhlIGlzc3VpbmcgQ0Egd291bGQgcHV0IGluIGF0IHRoZWlyIGRpc2NyZXRpb24uDQoNCiAN
Cg0KICAgIFRoZSBuZWVkIGZvciB0aGlzIGlzIHRvIGFsbG93IGEgQ0EgdG8gc3VwcG9ydCBhIHdp
ZGUgcmFuZ2Ugb2YgYXBwbGljYXRpb25zIHdoaWNoIHJlcXVpcmUgZW5jcnlwdGlvbiBidXQgcmVx
dWlyZSBldmVuIGxlc3MgYXV0aGVudGljYXRpb24gdGhhbiBjdXJyZW50IHNjaGVtZXMgc3VjaCBh
cyBkb21haW4gdmFsaWRhdGVkIGNlcnRzLiBGb3IgZXhhbXBsZSBzZWxmIHNpZ25lZCBjZXJ0aWZp
Y2F0ZXMsIGNlcnRpZmljYXRlcyBpc3N1ZWQgdG8gZW1iZWRkZWQgaGFyZHdhcmUsIGV0Yy4gZXRj
Lg0KDQogDQoNCiAgICBXaGF0IEkgd2FudCB0byBkbyBpcyB0byBnZXQgdXMgdG8gdGhlIHBvaW50
IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbCBjb21mb3J0YWJsZSB3aXRoIGEgdXNlciBl
eHBlcmllbmNlIHRoYXQgZG9lcyBub3QgY29udGFpbiB0aGUgbmFnIHNjcmVlbnMgdGhhdCBkaXNm
aWd1cmUgY3VycmVudCBzY2hlbWVzLiBJbiBtYW55IGNhc2VzIGFsbCB0aGF0IGlzIHJlcXVpcmVk
IGlzIHRvIHR1cm4gb24gZW5jcnlwdGlvbi4gVGhlIHVzZXIgZG9lcyBub3QgbmVlZCB0byBiZSB0
b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBleHBpcmVkLCBoYXMgYmVlbiBpc3N1ZWQgYnkg
YW4gdW5rbm93biBDQSBvciBhbnkgb2YgdGhlIHVzdWFsIG5vbnNlbnNlLiBqdXN0IGRvbid0IHRl
bGwgdGhlIHVzZXIgdGhhdCBpdHMgc2FmZSBpbiB0aGUgZmlyc3QgcGxhY2UgYW5kIHRoZSBicm93
c2VyIGRvZXMgbm90IG5lZWQgdG8gc2F5IHRoYXQgaXQgaXMgZGFuZ2Vyb3VzLg0KDQogDQoNCiAg
ICBDbGVhcmx5IHRoaXMgYXR0cmlidXRlIGlzIHVubmVjZXNzYXJ5IGZyb20gYSB0ZWNobmljYWwg
cG9pbnQgb2Ygdmlldy4gRnJvbSBhIG1hcmtldCBwb2ludCBvZiB2aWV3IGl0IGlzIGVzc2VudGlh
bCBpZiB3ZSBhcmUgZ29pbmcgdG8gZW5zdXJlIHRoYXQgYXBwbGljYXRpb25zIGFyZSBkb2luZyB0
aGUgcmlnaHQgdGhpbmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJldHR5IHN0cm9uZyBz
ZW1hbnRpY3MuIE1hbnkgYXBwbGljYXRpb25zIHJlcXVpcmUgbGVzcy4gV2UgYXJlIG5vdCBnb2lu
ZyB0byBnZXQgZXZlcnlvbmUgd2hvIGN1cnJlbnRseSBoYXMgYSBwYWRsb2NrIGNlcnRpZmljYXRl
IHRvIGdldCBhIGdyZWVuIGJhciBjZXJ0LiBTbyBsZXRzIHNlcnZlIHRoZSBhcHBsaWNhdGlvbnMg
dGhhdCByZXF1aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBwYWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcg
dGhlIHBhZGxvY2sgc2VtYW50aWNzIGZ1cnRoZXIuDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQoNCkZyb206IG93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmcgW21haWx0bzpv
d25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQ
aGlsbGlwDQpTZW50OiBUaHVyc2RheSwgNyBKdW5lIDIwMDcgMzowNiBBTQ0KVG86IEtlbXAsIERh
dmlkIFAuOyBwa2l4DQoNCiANCg0KMykgTm8gUGFkbG9jayBJY29uIGF0dHJpYnV0ZQ0KDQogDQoN
ClRoZSBwb2ludCBoZXJlIGlzIHByZWNpc2VseSB0byBhbGxvdyBhIGNlcnRpZmljYXRlIHRvIHN0
YXRlICd0aGVyZSBhcmUgbm8gc2VjdXJpdHkgY2xhaW1zIGJlaW5nIG1hZGUgaGVyZScuIA0KDQog
DQoNClRoZSB1c2VyIGRvZXMgbm90IGFjY2VwdCB0aGUgY2VydGlmaWNhdGUsIHRoZSBjbGllbnQg
YXBwbGljYXRpb24gZG9lcy4gTm8gdXNlciBoYXMgZXZlciBjaGVja2VkIGEgY2VydGlmaWNhdGUg
cGF0aCBhbmQgbm8gdXNlciBldmVyIHdpbGwuIFRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHRoZSBj
bGllbnQgYXBwbGljYXRpb24gc2hvdWxkIGJlIHRlbGxpbmcgdGhlIHVzZXIgdGhhdCBpdCBpcyAn
c2FmZScgb3Igbm90Lg0KDQogDQoNCkkgZG9uJ3Qgc2VlIHdoeSB3ZSBuZWVkIHRvIHRlbGwgdGhl
IHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVzZWQgdW5sZXNzIHRoZXkgaGF2ZSBleHBs
aWNpdGx5IHNhaWQgdGhhdCB0aGV5IG5lZWQgY29uZmlkZW50aWFsaXR5LiBUZWxsaW5nIHRoZSB1
c2VyIHRoYXQgdGhlcmUgaXMgZW5jcnlwdGlvbiBtZWFucyBhbHNvIHRlbGxpbmcgdGhlbSBhYm91
dCBhIHdob2xlIHJhbmdlIG9mIGZhaWx1cmVzIGFuZCBvdGhlciBlcnJvciBjb25kaXRpb25zLiAN
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBv
d25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIFttYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwu
aW1jLm9yZ10gPG1haWx0bzolNWJtYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyU1
ZD4gIE9uIEJlaGFsZiBPZiBIYWxsYW0tQmFrZXIsIFBoaWxsaXANClNlbnQ6IFR1ZXNkYXksIDEy
IEp1bmUgMjAwNyAxMjoyNCBBTQ0KDQogDQoNCuKApg0KDQpJIGNhbiBnaXZlIHlvdSBhIGNhc3Qg
aXJvbiBjaGFpbiBmb3IgYW4gRVVJNDggTUFDIGFkZHJlc3MuIEJ1dCBpdCBzYXlzIG5vdGhpbmcg
dGhhdCBzaG91bGQgZ2l2ZSBhbiBlbmQgdXNlciB3YXJtIGZ1enppZXMuDQoNCiANCg0KIA0KDQon
VGhpcyBjZXJ0IG1ha2VzIG5vIHNlY3VyaXR5IGNsYWltcyB0aGF0IGFyZSB3b3J0aCBkaXNwbGF5
IHRvIGFuIGVuZCB1c2VyJy4NCg0K4oCmDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KRnJvbTogb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyBbbWFp
bHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddIDxtYWlsdG86JTVibWFpbHRvOm93bmVy
LWlldGYtcGtpeEBtYWlsLmltYy5vcmclNWQ+ICBPbiBCZWhhbGYgT2YgSGFsbGFtLUJha2VyLCBQ
aGlsbGlwDQpTZW50OiBUdWVzZGF5LCAxMiBKdW5lIDIwMDcgMzo0NSBBTQ0KDQogDQoNCuKAplRo
ZSBpbmZvcm1hdGlvbiB0byBiZSBlbmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0aGUgaXNzdWUgcHJh
Y3RpY2VzIG9mIHRoZSBjZXJ0aWZpY2F0ZS4gVGhlcmVmb3JlIHRoZXkgZ28gaW50byB0aGUgY2Vy
dGlmaWNhdGUuDQoNCiANCg0KVGhlc2UgYXJlIG5vdCBhbm9ueW1vdXMgY29tbXVuaWNhdGlvbnMs
IHRoZXkgYXJlIG1lcmVseSBjb21tdW5pY2F0aW9ucyB0aGF0IGRvIG5vdCByZXF1aXJlIHRoZSBs
ZXZlbCBvZiBhc3N1cmFuY2UgdGhhdCBpcyBuZWNlc3NhcnkgdG8gYWxlcnQgdGhlIHVzZXIgdG8g
dGVsbCB0aGFtIHRoYXQgdGhlIGNvbW11bmljYXRpb24gaXMgc2VjdXJlLg0KDQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IG93bmVyLWlldGYtcGtp
eEBtYWlsLmltYy5vcmcgW21haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8bWFp
bHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkPiAgT24gQmVoYWxm
IE9mIEhhbGxhbS1CYWtlciwgUGhpbGxpcA0KU2VudDogVHVlc2RheSwgMTIgSnVuZSAyMDA3IDEw
OjAwIEFNDQoNCiANCg0KQ2FzZSBpbiBwb2ludCBoZXJlIGJlaW5nIHlvdXIgUy9NSU1FIGNlcnQg
d2hpY2ggZG9lcyBub3Qgc2F0aXNmeSBteSBPdXRsb29rIGNoYWluaW5nIHNvIGdpdmUgYSB3YXJu
aW5nLg0KDQogDQoNCllldCBJIGNhbiBnZXQgbWFpbCBmcm9tIHBsZW50eSBvZiBwbGFjZXMgd2l0
aG91dCBhbnkgc2VjdXJpdHkgYW5kIHdpdGhvdXQgYSB3YXJuaW5nIGVpdGhlci4NCg0KIA0KDQpX
b3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydCBjb3VsZCBzYXkgJ3RoZSBjb3JyZWN0IGNvdXJz
ZSBvZiBhY3Rpb24gaWYgeW91IGRvbid0IGxpa2UgbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVt
YWlsIHdpdGhvdXQgYW55IGluZGljYXRpb24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy4NCg0KIA0K
DQpXaHkgZG8gZm9sayBmZWVsIHRoYXQgdGhlIHVzZXIgaGFzIHRvIGJlIHRvbGQgYWJvdXQgbWVy
ZWx5IHN1Yi1zdGFuZGFyZCBzZWN1cml0eSB3aGVuIDk5JSBvZiB0aGUgSW50ZXJuZXQgaGFzIG5v
IHNlY3VyaXR5IGF0IGFsbD8NCg0K

------_=_NextPart_001_01C7B149.7A9E4C70
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RS
L1JFQy1odG1sNDAiPg0KDQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNv
bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPUdlbmVyYXRvciBj
b250ZW50PSJNaWNyb3NvZnQgV29yZCAxMSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8IS0tW2lmICFt
c29dPg0KPHN0eWxlPg0Kdlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPg0K
PCFbZW5kaWZdLS0+DQo8c3R5bGU+DQo8IS0tDQogLyogRm9udCBEZWZpbml0aW9ucyAqLw0KIEBm
b250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KCXBhbm9zZS0xOjIg
MTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6VGFob21hOw0K
CXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IlxAQXJpYWwgVW5pY29kZSBNUyI7DQoJcGFub3NlLTE6MiAxMSA2IDQgMiAyIDIgMiAyIDQ7
fQ0KIC8qIFN0eWxlIERlZmluaXRpb25zICovDQogcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtjb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7
bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkFyaWFsIFVuaWNv
ZGUgTVMiOw0KCWNvbG9yOmJsdWU7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6
bm9ybWFsOw0KCXRleHQtZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KQHBhZ2UgU2VjdGlvbjENCgl7
c2l6ZTo1OTUuM3B0IDg0MS45cHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBw
dDt9DQpkaXYuU2VjdGlvbjENCgl7cGFnZTpTZWN0aW9uMTt9DQotLT4NCjwvc3R5bGU+DQoNCjwv
aGVhZD4NCg0KPGJvZHkgbGFuZz1FTi1BVSBsaW5rPWJsdWUgdmxpbms9Ymx1ZT4NCg0KPGRpdiBj
bGFzcz1TZWN0aW9uMT4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPkkg
bGlrZSB0aGUgaWRlYSBvZiByZXZlcnRpbmcgdG8gYW4g4oCcdW5zZWN1cmVk4oCdIGxvb2stbi1m
ZWVsIGFuZA0KYXZvaWRpbmcgbmFnIHNjcmVlbnMgd2hlbiB0aGUgc2VjdXJpdHksIHRob3VnaCBw
cmVzZW50LCBpcyBub3Qg4oCccGVyZmVjdOKAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxw
IGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz5JdCBpcyBiYWQgdGhhdCBtYW55IGNs
aWVudHMgdHJlYXQgdW5jb25maXJtZWQgc2VjdXJpdHkgKGVnIHNpZ25lZCwNCmJ1dCBub3QgYnkg
YSBsb2NhbGx5LXRydXN0ZWQgcm9vdCkgYXMgd29yc2UgdGhhbiBubyBzZWN1cml0eS4gVGhpcyBk
aXNjb3VyYWdlcyBhdHRlbXB0cw0KdG8gaW1wcm92ZSBzZWN1cml0eS48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz5JIGFtIGxlc3Mg
c3VyZSB0aGF0IGEg4oCcbm8gcGFkbG9ja+KAnSBhdHRyaWJ1dGUgaXMgdGhlIHJpZ2h0IHdheSB0
bw0KYWNoaWV2ZSB0aGlzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmlj
b2RlIE1TIjsNCmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tbGVmdDozNi4wcHQnPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiO2NvbG9yOiM5
OTMzMDAnPiZndDtXb3VsZG4ndCBpdCBiZSBuaWNlIGlmIGEgY2VydA0KY291bGQgc2F5ICd0aGUg
Y29ycmVjdCBjb3Vyc2Ugb2YgYWN0aW9uIGlmIHlvdSBkb24ndCBsaWtlIG1lIGlzIHRvIHNpbXBs
eSBzaG93DQp0aGUgZW1haWwgd2l0aG91dCBhbnkgaW5kaWNhdGlvbiB0aGUgbWVzc2FnZSBpcyBz
ZWN1cmUnLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFu
IHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsN
CmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBV
bmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPldvdWxkbuKAmXQgaXQgYmUgYmV0dGVyIHRvIGZpeCBl
bWFpbCBjbGllbnRzIHNvIHRoZXkgYWx3YXlzIGFjdCB0aGlzDQp3YXksIGluc3RlYWQgb2Ygb25s
eSB0cmlnZ2VyaW5nIHRoaXMgYmVoYXZpb3VyIGZvciBjZXJ0YWluIGNlcnRpZmljYXRlcz8gVW5s
ZXNzDQppdCBpcyBhIHRhY3RpY2FsIGRlY2lzaW9uIHRoYXQgc29mdHdhcmUgdmVuZG9ycyBhcmUg
bW9yZSBsaWtlbHkgdG8gaW1wbGVtZW50IGENCm5ldyBjZXJ0aWZpY2F0ZSBmZWF0dXJlIHRoYW4g
Y2hhbmdlIGV4aXN0aW5nIGJlaGF2aW91ciAoZXNwZWNpYWxseSBpZiB0aGUNCmxhdHRlciBtaWdo
dCBiZSBicmFuZGVkIGFzIHdvcnNlbmluZyBzZWN1cml0eSkuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KY29sb3I6Ymx1ZSc+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkFyaWFsIFVuaWNvZGUgTVMiOw0KY29sb3I6Ymx1ZSc+Rm9y
IEhUVFBTIGNvbm5lY3Rpb25zLCBhIGNlcnRpZmljYXRlIHdpdGhvdXQgYSBzdWJqZWN0QWx0TmFt
ZS5kTlNOYW1lDQpmaWVsZCAoYW5kIG5vIGRvbWFpbiBuYW1lIGluIGEgY29tbW9uIG5hbWUgY29t
cG9uZW50IG9mIHRoZSBzdWJqZWN0IGZpZWxkKQ0Kc2hvdWxkIGJlIHN1ZmZpY2llbnQgZm9yIGEg
YnJvd3NlciB0byBzYXkg4oCcd2VsbCBJIGNhbm5vdCBkbyB0aGUgVVJMLXRvLWNlcnQNCmNoZWNr
IHNvIEkgd2lsbCBkaXNwbGF5IHRoZSBwYWdlIGp1c3QgbGlrZSBhbiBIVFRQIHBhZ2XigJ06IG5v
IGNvbG91cmVkIGFkZHJlc3MNCmJhciwgbm8gbG9ja2VkIHBhZGxvY2ssIG5vIG5hZyBzY3JlZW5z
LCBzdGlsbCB1c2luZyBUTFMgb24tdGhlLXdpcmUgdGhvdWdoLiBObw0KcGF0aCB0byBhIHRydXN0
ZWQgcm9vdCAoZWcgYSBzZWxmLXNpZ25lZCBjZXJ0KSBzaG91bGQgYmUgdHJlYXRlZCB0aGUgc2Ft
ZSB3YXkuDQpVbmF2YWlsYWJsZSBDUkxzIGNvdWxkIGJlIHRyZWF0ZWQgdGhlIHNhbWUgd2F5Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJs
dWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxz
cGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBVbmljb2RlIE1T
IjsNCmNvbG9yOmJsdWUnPk90aGVyIGVycm9ycyBzdWNoIGFzIGFuIGluY29ycmVjdCBzaWduYXR1
cmUsIGV4cGlyZWQgY2VydGlmaWNhdGUsIG9yDQphIG1pc21hdGNoIGJldHdlZW4gVVJMICZhbXA7
IGNlcnQgbmFtZSBpbXBseSB0aGUgY2VydGlmaWNhdGUgaG9sZGVyIGhhcyBkb25lDQpzb21ldGhp
bmcgd3JvbmcuIEkgZG9u4oCZdCBoYXZlIGEgcHJvYmxlbSB3aXRoIG5hZyBzY3JlZW5zIChvciBv
dXRyaWdodCByZWZ1c2FsDQp0byBjb25uZWN0KSBpbiB0aGVzZSBjYXNlcy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpi
bHVlJz5QUk9CTEVNPG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwg
c3R5bGU9J21hcmdpbi1sZWZ0OjM2LjBwdCc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7
DQpmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7Y29sb3I6Izk5MzMwMCc+Jmd0OyBJIGRv
bid0IHNlZSB3aHkgd2UgbmVlZCB0bw0KdGVsbCB0aGUgdXNlciB0aGF0IGVuY3J5cHRpb24gaXMg
YmVpbmcgdXNlZCB1bmxlc3MgdGhleSBoYXZlIGV4cGxpY2l0bHkgc2FpZA0KdGhhdCB0aGV5IG5l
ZWQgY29uZmlkZW50aWFsaXR5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiJBcmlhbCBV
bmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiJBcmlhbCBVbmljb2RlIE1TIjsNCmNvbG9yOmJsdWUnPlRoZSBwcm9ibGVtIGlzIHRoYXQg
dGhlIEhUVFBTIHNjaGVtZSBpbiBhIFVSTCBpbXBsaWVzIGEg4oCcc2FmZeKAnQ0KY29ubmVjdGlv
biwgcmVnYXJkbGVzcyBvZiBhIHBhZGxvY2sgaWNvbiBvciBhZGRyZXNzIGJhciBjb2xvdXIuIElm
IGEgdXNlciBkaWRu4oCZdA0Ka25vdyBpZiB0aGUgVVJMIHdhcyBIVFRQIG9yIEhUVFBTIChlZyB0
aGVpciBicm93c2VyIGF1dG9tYXRpY2FsbHkgd2VudCB0aGVyZQ0KYWZ0ZXIgYW4gSFRUUCAzMDcg
cmVkaXJlY3QpIHRoZW4gdHJlYXRpbmcg4oCcdW5jb25maXJtZWQgc2VjdXJpdHnigJ0gYXMg4oCc
dW5zZWN1cmVk4oCdDQp3b3VsZCBiZSByZWFzb25hYmxlLiBPbiB0aGUgb3RoZXIgaGFuZCwgaWYg
SSBjaG9vc2UgbXkgSFRUUFMgYm9va21hcmsgZm9yIG15DQpiYW5rIHRoZW4gSSBleHBlY3QgbXkg
YnJvd3NlciA8aT5ub3Q8L2k+IHRvIHByb2Nlc3MgYW55IChwb3RlbnRpYWxseS1tYWxpY2lvdXMp
DQpodG1sL2phdmFzY3JpcHQvYWN0aXZleC9mbGFzaCBmb3IgYW55IG90aGVyIHNvdXJjZS4gSWYg
bXkgYnJvd3NlciAocGVyaGFwcyBkdWUNCnRvIGEgRE5TIGF0dGFjaykgc2lsZW50bHkgYWNjZXB0
ZWQgY29udGVudCBub3QgZnJvbSBteSBiYW5rIEkgd291bGQgYmUgd29yc2UNCm9mZi48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBNUyI7DQpj
b2xvcjpibHVlJz5BbnkgdmlzaWJpbGl0eSBvZiBhbiBIVFRQUyBVUkwgdG8gdGhlIHVzZXIgY291
bGQgYmUgY29uc2lkZXJlZCBhcyB0aGVtDQpleHBsaWNpdGx5IHNheWluZyB0aGV5IG5lZWQgY29u
ZmlkZW50aWFsaXR5OiBjaG9vc2luZyBhbiBIVFRQUyBib29rbWFyazsgdHlwaW5nDQpIVFRQUyBp
bnRvIHRoZSBhZGRyZXNzIGJhcjsgY2xpY2tpbmcgb24gYW4gSFRUUFMgbGluayB3aGVuIHRoZSBV
Ukwgd2FzIHNob3duIGluDQp0aGUgc3RhdHVzIGJhciBiZWZvcmUgdGhlIGNsaWNrOyBldmVuIHNl
ZWluZyBIVFRQUyBpbiB0aGUgYWRkcmVzcyBiYXIgYWZ0ZXINCnJlY2VpdmluZyBhIHBhZ2UgY2Fu
IGJlIGVub3VnaC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJpYWwgVW5pY29kZSBN
UyI7DQpjb2xvcjpibHVlJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToiQXJp
YWwgVW5pY29kZSBNUyI7DQpjb2xvcjpibHVlJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQoNCjxkaXY+DQoNCjxkaXYgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWNlbnRlciBzdHlsZT0ndGV4
dC1hbGlnbjpjZW50ZXInPg0KDQo8aHIgc2l6ZT0yIHdpZHRoPSIxMDAlIiBhbGlnbj1jZW50ZXIg
dGFiaW5kZXg9LTE+DQoNCjwvZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PGI+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6VGFob21hJz5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlRhaG9tYSc+IEhhbGxh
bS1CYWtlciwgUGhpbGxpcDxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCA1IEp1bmUgMjAwNyAz
OjM3IEFNPGJyPg0KPGI+U3ViamVjdDo8L2I+IFRocmVlIHNob3J0IGZpeGVzOiBubyBwYWRsb2Nr
OyB0ZXh0IGxvZ287IG1lbWJlciBzaW5jZTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+
DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTpBcmlhbCc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8
L2Rpdj4NCg0KPGRpdj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOmJsdWUnPuKApjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3Ryb25n
PjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsJz4zKQ0KTm8g
UGFkbG9jayBJY29uIGF0dHJpYnV0ZTwvc3Bhbj48L3N0cm9uZz48bzpwPjwvbzpwPjwvcD4NCg0K
PC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCg0KPC9kaXY+DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDsmbmJzcDsm
bmJzcDsgPHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6DQpBcmlhbCc+
VGhpcyBhdHRyaWJ1dGUgd291bGQgYWxsb3cgYSBjZXJ0aWZpY2F0ZSB0byBzYXkgdGhhdCBubyB1
c2VyIGluZGljYXRpb24NCnNob3VsZCBiZSBzcGVjaWZpZWQgaW4gdGhlIGNocm9tZSwgbm9yIHNo
b3VsZCBhbnkgbmFnIHNjcmVlbnMuIEl0IHdvdWxkIGJlIGFuDQpvcHRpb24gdGhhdCB0aGUgaXNz
dWluZyBDQSB3b3VsZCBwdXQgaW4gYXQgdGhlaXIgZGlzY3JldGlvbi48L3NwYW4+PG86cD48L286
cD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+Jm5ic3A7PG86
cD48L286cD48L3A+DQoNCjwvZGl2Pg0KDQo8ZGl2Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
Og0KQXJpYWwnPlRoZSBuZWVkIGZvciB0aGlzIGlzIHRvIGFsbG93IGEgQ0EgdG8gc3VwcG9ydCBh
IHdpZGUgcmFuZ2Ugb2YNCmFwcGxpY2F0aW9ucyB3aGljaCZuYnNwO3JlcXVpcmUgZW5jcnlwdGlv
biBidXQgcmVxdWlyZSBldmVuIGxlc3MgYXV0aGVudGljYXRpb24NCnRoYW4gY3VycmVudCBzY2hl
bWVzIHN1Y2ggYXMgZG9tYWluIHZhbGlkYXRlZCBjZXJ0cy4gRm9yIGV4YW1wbGUgc2VsZiBzaWdu
ZWQNCmNlcnRpZmljYXRlcywgY2VydGlmaWNhdGVzIGlzc3VlZCB0byBlbWJlZGRlZCBoYXJkd2Fy
ZSwgZXRjLiBldGMuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPGRpdj4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KDQo8L2Rpdj4NCg0KPGRp
dj4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPiZuYnNwOyZuYnNwOyZuYnNwOyA8c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseToNCkFyaWFsJz5XaGF0IEkgd2FudCB0byBkbyBp
cyB0byBnZXQgdXMgdG8gdGhlIHBvaW50IHdoZXJlIHRoZSBicm93c2VyIGF1dGhvcnMgZmVlbA0K
Y29tZm9ydGFibGUgd2l0aCBhIHVzZXIgZXhwZXJpZW5jZSB0aGF0IGRvZXMgbm90IGNvbnRhaW4g
dGhlIG5hZyBzY3JlZW5zIHRoYXQNCmRpc2ZpZ3VyZSBjdXJyZW50IHNjaGVtZXMuIEluIG1hbnkg
Y2FzZXMgYWxsIHRoYXQgaXMgcmVxdWlyZWQgaXMgdG8gdHVybiBvbg0KZW5jcnlwdGlvbi4gVGhl
IHVzZXIgZG9lcyBub3QgbmVlZCB0byBiZSB0b2xkIHRoYXQgdGhlIGNlcnRpZmljYXRlIGhhcyBl
eHBpcmVkLA0KaGFzIGJlZW4gaXNzdWVkIGJ5IGFuIHVua25vd24gQ0Egb3IgYW55IG9mIHRoZSB1
c3VhbCBub25zZW5zZS4ganVzdCBkb24ndCB0ZWxsDQp0aGUgdXNlciB0aGF0IGl0cyBzYWZlIGlu
IHRoZSBmaXJzdCBwbGFjZSBhbmQgdGhlIGJyb3dzZXIgZG9lcyBub3QgbmVlZCB0byBzYXkNCnRo
YXQgaXQgaXMgZGFuZ2Vyb3VzLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+DQoNCjxk
aXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+
DQoNCjxkaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD4mbmJzcDsmbmJzcDsmbmJzcDsgPHNwYW4g
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6DQpBcmlhbCc+Q2xlYXJseSB0aGlz
IGF0dHJpYnV0ZSBpcyB1bm5lY2Vzc2FyeSBmcm9tIGEgdGVjaG5pY2FsIHBvaW50IG9mIHZpZXcu
DQpGcm9tIGEgbWFya2V0IHBvaW50IG9mIHZpZXcgaXQgaXMgZXNzZW50aWFsIGlmIHdlIGFyZSBn
b2luZyB0byBlbnN1cmUgdGhhdA0KYXBwbGljYXRpb25zIGFyZSBkb2luZyB0aGUgcmlnaHQgdGhp
bmcuIFRoZSBwYWRsb2NrIGljb24gaGFzIHNvbWUgcHJldHR5IHN0cm9uZw0Kc2VtYW50aWNzLiBN
YW55IGFwcGxpY2F0aW9ucyByZXF1aXJlIGxlc3MuIFdlIGFyZSBub3QgZ29pbmcgdG8gZ2V0IGV2
ZXJ5b25lIHdobw0KY3VycmVudGx5IGhhcyBhIHBhZGxvY2sgY2VydGlmaWNhdGUgdG8gZ2V0IGEg
Z3JlZW4gYmFyIGNlcnQuIFNvIGxldHMgc2VydmUgdGhlDQphcHBsaWNhdGlvbnMgdGhhdCByZXF1
aXJlIGV2ZW4gbGVzcyB0aGFuIHRoZSBwYWRsb2NrIHdpdGhvdXQgZGlsdXRpbmcgdGhlDQpwYWRs
b2NrIHNlbWFudGljcyBmdXJ0aGVyLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCg0KPC9kaXY+DQoN
CjxkaXYgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWNlbnRlciBzdHlsZT0ndGV4dC1hbGlnbjpjZW50
ZXInPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpuYXZ5Jz4NCg0KPGhyIHNpemU9MiB3aWR0aD0iMTAwJSIgYWxpZ249Y2VudGVyIHRhYkluZGV4
PS0xPg0KDQo8L3NwYW4+PC9kaXY+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48Yj48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpUYWhvbWE7DQpjb2xvcjpibGFjayc+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OlRh
aG9tYTsNCmNvbG9yOmJsYWNrJz4gb3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZw0KW21haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnXSA8Yj5PbiBCZWhhbGYgT2YgPC9iPkhhbGxh
bS1CYWtlciwgUGhpbGxpcDxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgNyBKdW5lIDIwMDcg
MzowNiBBTTxicj4NCjxiPlRvOjwvYj4gS2VtcCwgRGF2aWQgUC47IHBraXg8L3NwYW4+PHNwYW4g
c3R5bGU9J2NvbG9yOm5hdnknPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFjayc+Jm5ic3A7PG86cD48L286cD48L3NwYW4+
PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHN0cm9uZz48c3BhbiBzdHlsZT0nZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDsNCmNvbG9yOmJsYWNrJz4zKSBObyBQYWRsb2NrIElj
b24gYXR0cmlidXRlPC9zcGFuPjwvc3Ryb25nPjxzcGFuDQpzdHlsZT0nY29sb3I6YmxhY2snPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdj
b2xvcjpuYXZ5Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibHVlJz5UaGUmbmJzcDtwb2ludA0KaGVyZSBpcyBwcmVjaXNlbHkgdG8gYWxsb3cgYSBjZXJ0
aWZpY2F0ZSB0byBzdGF0ZSAndGhlcmUgYXJlIG5vIHNlY3VyaXR5IGNsYWltcw0KYmVpbmcgbWFk
ZSBoZXJlJy4mbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOm5hdnknPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFj
ayc+Jm5ic3A7PC9zcGFuPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTpBcmlhbDtjb2xvcjpibHVlJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibHVlJz5UaGUNCnVzZXIgZG9lcyBub3QgYWNjZXB0IHRoZSBjZXJ0aWZpY2F0ZSwgdGhl
IGNsaWVudCBhcHBsaWNhdGlvbiBkb2VzLiBObyB1c2VyIGhhcw0KZXZlciBjaGVja2VkIGEgY2Vy
dGlmaWNhdGUgcGF0aCBhbmQgbm8gdXNlciBldmVyIHdpbGwuIFRoZSBxdWVzdGlvbiBpcyB3aGV0
aGVyDQp0aGUgY2xpZW50IGFwcGxpY2F0aW9uIHNob3VsZCBiZSB0ZWxsaW5nIHRoZSB1c2VyIHRo
YXQgaXQgaXMgJ3NhZmUnIG9yIG5vdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nY29sb3I6YmxhY2snPiZuYnNwOzwvc3Bhbj48c3Bhbg0K
c3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+PG86
cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+SQ0KZG9uJ3Qgc2Vl
IHdoeSB3ZSBuZWVkIHRvIHRlbGwgdGhlIHVzZXIgdGhhdCBlbmNyeXB0aW9uIGlzIGJlaW5nIHVz
ZWQgdW5sZXNzDQp0aGV5IGhhdmUgZXhwbGljaXRseSBzYWlkIHRoYXQgdGhleSBuZWVkIGNvbmZp
ZGVudGlhbGl0eS4gVGVsbGluZyB0aGUgdXNlciB0aGF0DQp0aGVyZSBpcyBlbmNyeXB0aW9uIG1l
YW5zIGFsc28gdGVsbGluZyB0aGVtIGFib3V0IGEgd2hvbGUgcmFuZ2Ugb2YgZmFpbHVyZXMgYW5k
DQpvdGhlciBlcnJvciBjb25kaXRpb25zLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNs
YXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2luLWJvdHRvbTo2LjBwdCc+PHNwYW4gc3R5bGU9J2Zv
bnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTpUYWhvbWE7Y29sb3I6YmxhY2snPl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCjxiPkZyb206PC9iPiA8
YSBocmVmPSJtYWlsdG86b3duZXItaWV0Zi1wa2l4QG1haWwuaW1jLm9yZyI+b3duZXItaWV0Zi1w
a2l4QG1haWwuaW1jLm9yZzwvYT4NCjxhIGhyZWY9Im1haWx0bzolNWJtYWlsdG86b3duZXItaWV0
Zi1wa2l4QG1haWwuaW1jLm9yZyU1ZCI+W21haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnXTwvYT4NCjxiPk9uIEJlaGFsZiBPZiA8L2I+SGFsbGFtLUJha2VyLCBQaGlsbGlwPGJyPg0K
PGI+U2VudDo8L2I+IFR1ZXNkYXksIDEyIEp1bmUgMjAwNyAxMjoyNCBBTTwvc3Bhbj48c3BhbiBz
dHlsZT0nY29sb3I6YmxhY2snPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNv
Tm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFsO2Nv
bG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05v
cm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibHVlJz7igKY8L3NwYW4+PHNwYW4NCnN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OkFyaWFsO2NvbG9yOmJsYWNrJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNz
PU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlh
bDtjb2xvcjpibGFjayc+SQ0KY2FuIGdpdmUgeW91IGEgY2FzdCBpcm9uIGNoYWluIGZvciBhbiBF
VUk0OCBNQUMgYWRkcmVzcy4gQnV0IGl0IHNheXMgbm90aGluZw0KdGhhdCBzaG91bGQgZ2l2ZSBh
biBlbmQgdXNlciB3YXJtIGZ1enppZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJp
YWw7Y29sb3I6YmxhY2snPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFs
O2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibGFjayc+J1RoaXMNCmNlcnQgbWFrZXMgbm8gc2VjdXJpdHkgY2xhaW1zIHRoYXQgYXJl
IHdvcnRoIGRpc3BsYXkgdG8gYW4gZW5kIHVzZXInLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48c3BhbiBzdHls
ZT0nZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpibGFjayc+4oCm
PC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6VGFob21h
O2NvbG9yOmJsdWUnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFs
IHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBw
dDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpibGFjayc+X19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KPGI+RnJvbTo8L2I+IDxhIGhyZWY9Im1haWx0
bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnIj5vd25lci1pZXRmLXBraXhAbWFpbC5pbWMu
b3JnPC9hPg0KPGEgaHJlZj0ibWFpbHRvOiU1Ym1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5p
bWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYtcGtpeEBtYWlsLmltYy5vcmddPC9hPg0KPGI+
T24gQmVoYWxmIE9mIDwvYj5IYWxsYW0tQmFrZXIsIFBoaWxsaXA8YnI+DQo8Yj5TZW50OjwvYj4g
VHVlc2RheSwgMTIgSnVuZSAyMDA3IDM6NDUgQU08L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOmJs
YWNrJz48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBz
dHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpibGFjayc+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymx1ZSc+4oCmPC9z
cGFuPjxzcGFuDQpzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xv
cjpibGFjayc+VGhlIGluZm9ybWF0aW9uIHRvIGJlDQplbmNvZGVkIGhlcmUgcmVsYXRlcyB0byB0
aGUgaXNzdWUgcHJhY3RpY2VzIG9mIHRoZSBjZXJ0aWZpY2F0ZS4gVGhlcmVmb3JlIHRoZXkNCmdv
IGludG8gdGhlIGNlcnRpZmljYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OkFyaWFs
O2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1z
b05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtj
b2xvcjpibGFjayc+VGhlc2UNCmFyZSBub3QgYW5vbnltb3VzIGNvbW11bmljYXRpb25zLCB0aGV5
IGFyZSBtZXJlbHkgY29tbXVuaWNhdGlvbnMgdGhhdCBkbyBub3QgcmVxdWlyZQ0KdGhlIGxldmVs
IG9mIGFzc3VyYW5jZSB0aGF0IGlzIG5lY2Vzc2FyeSB0byBhbGVydCB0aGUgdXNlciB0byB0ZWxs
IHRoYW0gdGhhdA0KdGhlIGNvbW11bmljYXRpb24gaXMgc2VjdXJlLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSdtYXJnaW4tYm90dG9tOjYuMHB0Jz48
c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5OlRhaG9tYTtjb2xvcjpi
bGFjayc+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0K
PGI+RnJvbTo8L2I+IDxhIGhyZWY9Im1haWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3Jn
Ij5vd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnPC9hPg0KPGEgaHJlZj0ibWFpbHRvOiU1Ym1h
aWx0bzpvd25lci1pZXRmLXBraXhAbWFpbC5pbWMub3JnJTVkIj5bbWFpbHRvOm93bmVyLWlldGYt
cGtpeEBtYWlsLmltYy5vcmddPC9hPg0KPGI+T24gQmVoYWxmIE9mIDwvYj5IYWxsYW0tQmFrZXIs
IFBoaWxsaXA8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgMTIgSnVuZSAyMDA3IDEwOjAwIEFN
PC9zcGFuPjxzcGFuIHN0eWxlPSdjb2xvcjpibGFjayc+PG86cD48L286cD48L3NwYW4+PC9wPg0K
DQo8cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6QXJpYWw7Y29sb3I6YmxhY2snPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCg0K
PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OkFyaWFsO2NvbG9yOmJsYWNrJz5DYXNlDQppbiBwb2ludCBoZXJlIGJlaW5nIHlvdXIgUy9N
SU1FIGNlcnQgd2hpY2ggZG9lcyBub3Qgc2F0aXNmeSBteSBPdXRsb29rIGNoYWluaW5nDQpzbyBn
aXZlIGEgd2FybmluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1h
bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpBcmlhbDtjb2xvcjpi
bGFjayc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWw+
PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJpYWw7Y29sb3I6Ymxh
Y2snPllldA0KSSBjYW4gZ2V0IG1haWwgZnJvbSBwbGVudHkgb2YgcGxhY2VzIHdpdGhvdXQgYW55
IHNlY3VyaXR5IGFuZCB3aXRob3V0IGEgd2FybmluZw0KZWl0aGVyLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OkFyaWFsO2NvbG9yOmJsYWNrJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTpBcmlhbDtjb2xvcjpibGFjayc+V291bGRuJ3QNCml0IGJlIG5pY2UgaWYgYSBj
ZXJ0IGNvdWxkIHNheSAndGhlIGNvcnJlY3QgY291cnNlIG9mIGFjdGlvbiBpZiB5b3UgZG9uJ3Qg
bGlrZQ0KbWUgaXMgdG8gc2ltcGx5IHNob3cgdGhlIGVtYWlsIHdpdGhvdXQgYW55IGluZGljYXRp
b24gdGhlIG1lc3NhZ2UgaXMgc2VjdXJlJy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQoNCjxwIGNs
YXNzPU1zb05vcm1hbD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTpB
cmlhbDtjb2xvcjpibGFjayc+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KDQo8cCBjbGFz
cz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6QXJp
YWw7Y29sb3I6YmxhY2snPldoeQ0KZG8gZm9sayBmZWVsIHRoYXQgdGhlIHVzZXIgaGFzIHRvIGJl
IHRvbGQgYWJvdXQgbWVyZWx5IHN1Yi1zdGFuZGFyZCBzZWN1cml0eQ0Kd2hlbiA5OSUgb2YgdGhl
IEludGVybmV0IGhhcyBubyBzZWN1cml0eSBhdCBhbGw/PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
DQo8L2Rpdj4NCg0KPC9ib2R5Pg0KDQo8L2h0bWw+DQo=

------_=_NextPart_001_01C7B149.7A9E4C70--



Received: from host-ip78-11.crowley.pl (host-ip78-11.crowley.pl [85.128.11.78]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5HE5bTA013950; Sun, 17 Jun 2007 07:05:38 -0700 (MST) (envelope-from sufpacificsunsetdal@pacificsunset.com)
Received: from [85.128.11.78] by mail.pacificsunset.com; Sun, 17 Jun 2007 14:05:36 -0100
Date: 	Sun, 17 Jun 2007 14:05:36 -0100
From: "Reinaldo Cahill" <sufpacificsunsetdal@pacificsunset.com>
X-Mailer: The Bat! (v3.5.25) Professional
Reply-To: sufpacificsunsetdal@pacificsunset.com
X-Priority: 3 (Normal)
Message-ID: <039129076.41676903267243@pacificsunset.com>
To: ietf-mta-filters@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------48DA8D348DA86ED3"

------------48DA8D348DA86ED3
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

LegalRXMedications drugstore propose all medicinal remedies you have a need in in order to renew your health for a little cost. 
We operate through the whole planet with customers from America, Europe, and Asia. 
At this time you don't have to seek chemist's somewhere at your local area.
We necessarily deliver high-quality pharmas to the remotest parts of the globe.
Visit our site & acquire pharmas you need immediately direct to your dwelling. 
http://coastvoice.hk/ 
We are confirmed by VISA and VeriSign accordingly we support secure and trustworthy buying.

------------48DA8D348DA86ED3
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drugstore propose all medicinal remedies you have a need in in order to renew your health for a little cost. <br>
We operate through the whole planet with customers from America, Europe, and Asia. <br>
At this time you don't have to seek chemist's somewhere at your local area.<br>
We necessarily deliver high-quality pharmas to the remotest parts of the globe.
<br>
<br>
<a href="http://coastvoice.hk/" target="_blank"><em>Visit our site & acquire pharmas you need immediately direct to your dwelling.</em></a></b> 
<br>
<font color="#D9EDFF">http://coastvoice.hk/</font> 
<br><b>We are confirmed by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>VeriSign</em></font> accordingly we support secure and trustworthy buying.
</b>

</BODY></HTML>
------------48DA8D348DA86ED3--



Received: from pc-55139.zdnet.com.pl (pc-55139.zdnet.com.pl [194.150.251.139]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5GB9DZ5005929; Sat, 16 Jun 2007 04:09:20 -0700 (MST) (envelope-from lyqorangepipsgij@orangepips.com)
Received: from 64.20.53.22 (HELO orangepips.com) by imc.org with esmtp (/,P.6O9<I .A-7HD) id TO,A5(-8L,49+-78 for ietf-pkix-request@imc.org; Sat, 16 Jun 2007 11:09:27 -0100
Date: 	Sat, 16 Jun 2007 11:09:27 -0100
From: "Gerard Staley" <lyqorangepipsgij@orangepips.com>
X-Mailer: The Bat! (v3.5) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <392707350.81159790107999@thhebat.net>
To: ietf-pkix-request@imc.org
Subject: Make your fat friends envy you
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------B25094D39467A50"
X-Spam: Not detected

------------B25094D39467A50
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Profit by the chance! – Anatrim – The up-to-the-moment & most delighting flesh loss product available – As could be seen on Oprah

Do you retain all the times when you told yourself you would do any thing for being delivered from this terrible pounds of fat? Happily, now no major offering is necessary. With Anatrim, the earth-shaking, you can achieve healthier lifestyle and become really slimmer. Just look at what people say!
 
“I had always led a terrific life till a year back my girl said to me I was obese and in extreme want of looking after my health. Life had abruptly changed after that, until I found Anatrim ™. After loosing more than 18 kilogrammes only thanx to Anatrim,  my private life has come back, much better than before even. Lots of thanks to you for the marvelous product and the great service. Keep on the valuable business!”

 
Rikky Martin, New York

 
"Nothing to compare with sliding into a bikini I haven't worn for a long period. I feel slender, steadfast, and vigorous, thanks to a great extent to Anatrim! Thanks a lot!"

 
Silvia D., Colorado

Check out Anatrim, and  you'll join the world-wide company of thousands of delighted user who’re enjoying the revolutionary effects of Anatrim right here and right now. Less devouring madness, less kilos and more fun in your life!

Click here to gaze at unbreakable Anatrim deal we are proud to offer!!!
http://www.promfore.com/?dgdchmawdq

------------B25094D39467A50
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Control your weight and appetite</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href="http://www.promfore.com/?dgdchmawdq">
Profit by the chance! – Anatrim – The up-to-the-moment & most delighting flesh loss product available – As could be seen on Oprah
</a>
</center>
<br>
Do you retain all the times when you told yourself you would do any thing for being delivered from this terrible pounds of fat? Happily, now no major offering is necessary. With Anatrim, the earth-shaking, you can achieve healthier lifestyle and become really slimmer. Just look at what people say!
 <br>
<br>
<i>
“I had always led a terrific life till a year back my girl said to me I was obese and in extreme want of looking after my health. Life had abruptly changed after that, until I found Anatrim ™. After loosing more than 18 kilogrammes only thanx to Anatrim,  my private life has come back, much better than before even. Lots of thanks to you for the marvelous product and the great service. Keep on the valuable business!”
</i>
 <br>
<b>
<i>
Rikky Martin, New York
</i>
</b>
 <br>
<br>
<i>
"Nothing to compare with sliding into a bikini I haven't worn for a long period. I feel slender, steadfast, and vigorous, thanks to a great extent to Anatrim! Thanks a lot!"
</i>
 <br>
<b>
<i>
Silvia D., Colorado
</i>
</b>
<br>
<br>
Check out Anatrim, and  you'll join the world-wide company of thousands of delighted user who’re enjoying the revolutionary effects of Anatrim right here and right now. Less devouring madness, less kilos and more fun in your life!
<br>
<br>
<center>
<a href="http://www.promfore.com/?dgdchmawdq">
Click here to gaze at unbreakable Anatrim deal we are proud to offer!!!
</a>
</center>
</b>
</p>
<font color="#D9EDFF">http://www.promfore.com/?dgdchmawdq</font>

</BODY></HTML>
------------B25094D39467A50--



Received: from user-85-201-168-111.tvcablenet.be (user-85-201-168-111.tvcablenet.be [85.201.168.111]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FFJAbb074118; Fri, 15 Jun 2007 08:19:13 -0700 (MST) (envelope-from vigonetimeincfuw@onetimeinc.org)
Received: from [85.201.168.111] by alt1.aspmx.l.google.com; Sat, 16 Jun 2007 15:19:23 -0100
Date: 	Sat, 16 Jun 2007 15:19:23 -0100
From: "Joan Waller" <vigonetimeincfuw@onetimeinc.org>
X-Mailer: The Bat! (v3.80.06) Professional
Reply-To: vigonetimeincfuw@onetimeinc.org
X-Priority: 3 (Normal)
Message-ID: <541409999.95993615776728@onetimeinc.org>
To: imc-smime-dev-request@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------0188FB01F46E731"

------------0188FB01F46E731
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7bit

LegalRXMedications drug shop introduce all cures you need in order to restore your health at lowest price. 
We manage through the world with buyers from America, Europe and Asia. 
At present time you don't have to search for chemist's shop somewhere at your area.
We can transfer medicinal agents of the highest quality to the distant parts of the world.
Come to our site and procure medicinal preparations that you immediately require straightly to your lodging. 
http://likeedge.hk/ 
We are accredited by VISA and VeriSign thus we support secure and confidential buying.

------------0188FB01F46E731
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drug shop introduce all cures you need in order to restore your health at lowest price. <br>
We manage through the world with buyers from America, Europe and Asia. <br>
At present time you don't have to search for chemist's shop somewhere at your area.<br>
We can transfer medicinal agents of the highest quality to the distant parts of the world.
<br>
<br>
<a href="http://likeedge.hk/"><em>Come to our site and procure medicinal preparations that you immediately require straightly to your lodging.</em></a></b> 
<br>
<font color="#D9EDFF">http://likeedge.hk/</font> 
<br><b>We are accredited by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>VeriSign</em></font> thus we support secure and confidential buying.
</b>

</BODY></HTML>
------------0188FB01F46E731--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FF4uf0070825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 15 Jun 2007 08:04:56 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5FF4uBQ070824; Fri, 15 Jun 2007 08:04:56 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ns4.neustar.com (ns4.neustar.com [156.154.24.139]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FF4qV0070798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Fri, 15 Jun 2007 08:04:55 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 7B0CE2AC92; Fri, 15 Jun 2007 15:04:50 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HzDM2-0006NB-8c; Fri, 15 Jun 2007 11:04:50 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Subject: Last Call: draft-ietf-pkix-lightweight-ocsp-profile  (Lightweight OCSP Profile for High Volume Environments)  to Proposed Standard
Reply-To: ietf@ietf.org
Cc: <ietf-pkix@imc.org>
Message-Id: <E1HzDM2-0006NB-8c@stiedprstage1.ietf.org>
Date: Fri, 15 Jun 2007 11:04:50 -0400
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>

The IESG has received a request from the Public-Key Infrastructure 
(X.509) WG (pkix) to consider the following document:

- 'Lightweight OCSP Profile for High Volume Environments'
   <draft-ietf-pkix-lightweight-ocsp-profile-11.txt> as a
   Proposed Standard

An earlier version of this document was sent out for Last Call on
2007-03-05 with the intent of being published as an Informational RFC.
After the recent revisions, the IESG is considering this document for
publication as a Standards-Track RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-06-29. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=12331&rfc_flag=0



Received: from nafta.net.pl (nafta.net.pl [212.244.176.50]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5FBcaub033475; Fri, 15 Jun 2007 04:38:42 -0700 (MST) (envelope-from vigopaclinefuw@opacline.com)
Received: from 212.121.233.12 (HELO mail.opacline.com) by imc.org with esmtp (/M)-+M** 4T:*J) id 2U=9?W-660MJ*-)= for ietf-pkix-oid-reg@imc.org; Fri, 15 Jun 2007 11:15:57 -0100
Date: 	Fri, 15 Jun 2007 11:15:57 -0100
From: "Darcy Kyle" <vigopaclinefuw@opacline.com>
X-Mailer: The Bat! (v3.5.25) Educational
X-Priority: 3 (Normal)
Message-ID: <421469805.31255645505835@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Don't get left behind
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------EFDA29E80C51A0"
X-Spam: Not detected

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


Ultimately the true stuff =96 with no rip offs! 
P.E.P. are piping hot at the time! This is the real stuff not a forgery! 

One of the very originals, totally unparalleled product is easy=20=
accessible around the world!
 Notice just what people tell on this stuff:

"I pleased how fast your stuff had an affect upon my boyfriend, he can=20=
no way stop talking on how excited he is with his new calibre, extent,=20=
and libido!"

Victoria K., Bellevue WA

"In the beginning I thought the gratuitous specimen parcel I was given=20=
was a jest, till I have taken to take the P.E.P. Words cannot depict how=20=
greatly satisfied I am with the results from using this remedy for 8=20=
brief weeks. I'll be asking for P.E.P. on a regular basis!" 
Charley Mock, Chicago

Read more references about this marvellouls product here!
http://www.promfore.com/?nnbqddtfvra

------------EFDA29E80C51A0
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Make her worship you</TITLE>
</HEAD>
<BODY>

<b>
Ultimately the true stuff =96 with no rip offs! 
<br>
<a href=3D"http://www.promfore.com/?nnbqddtfvra">P.E.P.</a> are piping=20=
hot at the time! This is the real stuff not a forgery! 
<br>
One of the very originals, totally unparalleled product is easy=20=
accessible around the world!
<br> Notice just what people tell on this stuff:
<p>
<i>
"I pleased how fast your stuff had an affect upon my boyfriend, he can=20=
no way stop talking on how excited he is with his new calibre, extent,=20=
and libido!"
</i>
</p>
Victoria K., Bellevue WA
<p>
<i>
"In the beginning I thought the gratuitous specimen parcel I was given=20=
was a jest, till I have taken to take the P.E.P. Words cannot depict how=20=
greatly satisfied I am with the results from using this remedy for 8=20=
brief weeks. I'll be asking for P.E.P. on a regular basis!" </i>
</p>
Charley Mock, Chicago
<center>
<a href=3D"http://www.promfore.com/?nnbqddtfvra">
Read more references about this marvellouls product here!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.promfore.com/?nnbqddtfvra</font>

</BODY></HTML>
------------EFDA29E80C51A0--



Received: from q0.netfirms.com ([212.76.176.139]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5F3QlHm038620; Thu, 14 Jun 2007 20:26:49 -0700 (MST) (envelope-from kefoldertouchdyc@oldertouch.com)
Received: from 146.82.200.252 (HELO www.oldertouch.com) by imc.org with esmtp (AKKVZ42W.Z UD,3C) id -2YBWL-2=/R/2-4L for decode@imc.org; Fri, 15 Jun 2007 03:26:14 -0500
Date: 	Fri, 15 Jun 2007 03:26:14 -0500
From: "Jacquelyn Emery" <kefoldertouchdyc@oldertouch.com>
X-Mailer: The Bat! (v3.51) Educational
X-Priority: 3 (Normal)
Message-ID: <643382004.57370007964493@thhebat.net>
To: decode@imc.org
Subject: Be leaner and slimmer by next week
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------AE9016E9258409"
X-Spam: Not detected

------------AE9016E9258409
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Seize the opportunity! =96 Anatrim =96 The very up-to-date & most=20=
enchanting flesh loss product is now available =96 As told on Oprah

Can you count up all the situations when you told yourself you would do=20=
anything to get rid of this horrible number of pounds? Luckily, now no=20=
great price is to be paid. With Anatrim, the earth-shaking, you can get=20=
naturally health life style and become really slimmer. Just look at what=20=
customers state!
 
=93I always had a tremendous private life till a year back my=20=
girlfriend told me I was stout and had need for keeping eye on my health.=20=
My life had abruptly changed after that, till I discovered Anatrim =99=20=
for me at once. Since loosing about 40 lbs only thanks to Anatrim,  my=20=
private life has come back, significantly better than even before. A lot=20=
of thanx for the terrific stuff and the first-class maintenance service.=20=
Go on your helpful action!=94

 
Mike Brown, New York

 
"Nothing feels better than gliding into a bikini that I have not worn=20=
for a long time. I feel slender, steadfast, and vigorous, thanks to a=20=
great extent to Anatrim! Thank you a lot!"

 
Silvia D., New York

Check out Anatrim, and  you shall add yourself to the worldwide=20=
association of thousands of pleased buyers who=92re getting pleasure out=20=
of the revolutionary effects of Anatrim just now. Less devouring madness,=20=
less pounds and more gaiety in your life!

Go right here to inspect our outdone Anatrim dealings!!!
http://www.puddenom.net/?chdorbypfluns

------------AE9016E9258409
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Melt away fat easily</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.puddenom.net/?chdorbypfluns">
Seize the opportunity! =96 Anatrim =96 The very up-to-date & most=20=
enchanting flesh loss product is now available =96 As told on Oprah
</a>
</center>
<br>
Can you count up all the situations when you told yourself you would do=20=
anything to get rid of this horrible number of pounds? Luckily, now no=20=
great price is to be paid. With Anatrim, the earth-shaking, you can get=20=
naturally health life style and become really slimmer. Just look at what=20=
customers state!
 <br>
<br>
<i>
=93I always had a tremendous private life till a year back my=20=
girlfriend told me I was stout and had need for keeping eye on my health.=20=
My life had abruptly changed after that, till I discovered Anatrim =99=20=
for me at once. Since loosing about 40 lbs only thanks to Anatrim,  my=20=
private life has come back, significantly better than even before. A lot=20=
of thanx for the terrific stuff and the first-class maintenance service.=20=
Go on your helpful action!=94
</i>
 <br>
<b>
<i>
Mike Brown, New York
</i>
</b>
 <br>
<br>
<i>
"Nothing feels better than gliding into a bikini that I have not worn=20=
for a long time. I feel slender, steadfast, and vigorous, thanks to a=20=
great extent to Anatrim! Thank you a lot!"
</i>
 <br>
<b>
<i>
Silvia D., New York
</i>
</b>
<br>
<br>
Check out Anatrim, and  you shall add yourself to the worldwide=20=
association of thousands of pleased buyers who=92re getting pleasure out=20=
of the revolutionary effects of Anatrim just now. Less devouring madness,=20=
less pounds and more gaiety in your life!
<br>
<br>
<center>
<a href=3D"http://www.puddenom.net/?chdorbypfluns">
Go right here to inspect our outdone Anatrim dealings!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.puddenom.net/?chdorbypfluns</font>

</BODY></HTML>
------------AE9016E9258409--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5EMo4AE084592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 14 Jun 2007 15:50:04 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5EMo44C084591; Thu, 14 Jun 2007 15:50:04 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from ns1.neustar.com (ns1.neustar.com [156.154.16.138]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5EMo3Xl084575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Thu, 14 Jun 2007 15:50:04 -0700 (MST) (envelope-from ietf@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id DB77426EF1; Thu, 14 Jun 2007 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Hyy8g-0005IP-MN; Thu, 14 Jun 2007 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
Cc: ietf-pkix@imc.org
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-pkix-lightweight-ocsp-profile-11.txt 
Message-Id: <E1Hyy8g-0005IP-MN@stiedprstage1.ietf.org>
Date: Thu, 14 Jun 2007 18:50:02 -0400
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Public-Key Infrastructure (X.509) Working Group of the IETF.

	Title		: Lightweight OCSP Profile  for High Volume Environments
	Author(s)	: R. Hurst, A. Deacon
	Filename	: draft-ietf-pkix-lightweight-ocsp-profile-11.txt
	Pages		: 21
	Date		: 2007-6-14
	
This specification defines a profile of the Online Certificate 
   Status Protocol (OCSP) that addresses the scalability issues 
   inherent when using OCSP in large scale (high volume) Public Key 
   Infrastructure (PKI) environments and/or in PKI environments that 
   require a lightweight solution to minimize communication bandwidth 
   and client side processing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pkix-lightweight-ocsp-profile-11.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2007-6-14153557.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pkix-lightweight-ocsp-profile-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pkix-lightweight-ocsp-profile-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2007-6-14153557.I-D@ietf.org>

--OtherAccess--

--NextPart--



Received: from [89.230.1.146] (host-89-230-1-146.ozorkow.mm.pl [89.230.1.146]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5EHC4l8014468; Thu, 14 Jun 2007 10:12:06 -0700 (MST) (envelope-from hewnzwinelinksfib@nzwinelinks.org)
Received: from [89.230.1.146] by mx00.schlund.de; Thu, 14 Jun 2007 17:12:02 -0100
Date: 	Thu, 14 Jun 2007 17:12:02 -0100
From: "Delmer Crabtree" <hewnzwinelinksfib@nzwinelinks.org>
X-Mailer: The Bat! (v3.5) Professional
Reply-To: hewnzwinelinksfib@nzwinelinks.org
X-Priority: 3 (Normal)
Message-ID: <486267460.74947694609201@nzwinelinks.org>
To: ietf-openproxy-request@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------D3B48DA867299153"

------------D3B48DA867299153
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

LegalRXMedications drug shop introduce all medicinal preparations you feel necessity in in order to restore your health at lowest price. 
We manage through the whole world with customers from Europe, America and Asia. 
This time you don't have to search for drug shop at your area.
We surely transfer pills of the best quality to the remotest parts of the globe.
Visit our site and obtain medicinal preparations you demand instantly straight to your abode. 
http://shoearm.hk/ 
We’re ratified by VeriSign and VISA then we provide certain and dependable buying.

------------D3B48DA867299153
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drug shop introduce all medicinal preparations you feel necessity in in order to restore your health at lowest price. <br>
We manage through the whole world with customers from Europe, America and Asia. <br>
This time you don't have to search for drug shop at your area.<br>
We surely transfer pills of the best quality to the remotest parts of the globe.
<br>
<br>
<a href="http://shoearm.hk/"><em>Visit our site and obtain medicinal preparations you demand instantly straight to your abode.</em></a></b> 
<br>
<font color="#D9EDFF">http://shoearm.hk/</font> 
<br><b>We’re ratified by <font color="#FF0000"><em>VeriSign</em></font> and <font color="#FF0000"><em>VISA</em></font> then we provide certain and dependable buying.
</b>

</BODY></HTML>
------------D3B48DA867299153--



Received: from l64-81-64.cn.ru (l64-81-64.cn.ru [80.64.81.64]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5ECpPDZ081604; Thu, 14 Jun 2007 05:51:46 -0700 (MST) (envelope-from hewnyacpfib@nyacp.org)
Received: from 24.97.29.19 (HELO mail.nyacp.org) by imc.org with esmtp (Z'C.H9?MRM/ 75>KM-) id *L-268-53=2TA-A7 for ietf-openproxy@imc.org; Thu, 14 Jun 2007 12:52:44 -0600
Date: 	Thu, 14 Jun 2007 12:52:44 -0600
From: "Consuelo Colvin" <hewnyacpfib@nyacp.org>
X-Mailer: The Bat! (v3.51.10) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <164125650.68785868551671@thhebat.net>
To: ietf-openproxy@imc.org
Subject: Doctors and Celebrities endorse Anatrim
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------6E5425409D37109"
X-Spam: Not detected

------------6E5425409D37109
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit



Take advantage of the chance! – Anatrim – The latest and most attracting product for over-weight people available – As could be seen on Oprah

Do you remember all the situations when you plead to yourself to do any thing to get rid of this horrible fat? Fortunately, now no big price is to be paid. Thanks to Anatrim, the ground-breaking, you can get naturally health life style and become really slimmer. Have a look at what customers state!
 
“I had always led a marvelous life until last year my girl said to me I was portly and had need for being attentive to my health. My life had changed the wrong way after that, till I disclosed Anatrim ™. Since loosing more than 18 kilogrames thanks to Anatrim,  my private life’s come back, considerably better even than before. Thanx for the incredible stuff and the top-quality service. Go on your worthy work!”

 
Mikkey Fox, Chicago

 
"There’s nothing better than gliding into a bikini I haven’t been dressed in for a long time. Now I feel slim, determined, and sturdy, thanx in great part to Anatrim! A great deal of thanks to you!"

 
Victoria K., Bellevue WA

Discover Anatrim, and  you'll join the world-wide company of thousands of pleased user who’re getting pleasure out of the revolutionary effects of Anatrim right now. Less guzzling insanity, less kilos and more mirth in life!

Click right here to scan outdone Anatrim dealings we are so proud to propose!!!
http://www.borev.hk/?wzzgxwwjoll

------------6E5425409D37109
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Get your ideal weight with this natural method</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href="http://www.borev.hk/?wzzgxwwjoll">
Take advantage of the chance! – Anatrim – The latest and most attracting product for over-weight people available – As could be seen on Oprah
</a>
</center>
<br>
Do you remember all the situations when you plead to yourself to do any thing to get rid of this horrible fat? Fortunately, now no big price is to be paid. Thanks to Anatrim, the ground-breaking, you can get naturally health life style and become really slimmer. Have a look at what customers state!
 <br>
<br>
<i>
“I had always led a marvelous life until last year my girl said to me I was portly and had need for being attentive to my health. My life had changed the wrong way after that, till I disclosed Anatrim ™. Since loosing more than 18 kilogrames thanks to Anatrim,  my private life’s come back, considerably better even than before. Thanx for the incredible stuff and the top-quality service. Go on your worthy work!”
</i>
 <br>
<b>
<i>
Mikkey Fox, Chicago
</i>
</b>
 <br>
<br>
<i>
"There’s nothing better than gliding into a bikini I haven’t been dressed in for a long time. Now I feel slim, determined, and sturdy, thanx in great part to Anatrim! A great deal of thanks to you!"
</i>
 <br>
<b>
<i>
Victoria K., Bellevue WA
</i>
</b>
<br>
<br>
Discover Anatrim, and  you'll join the world-wide company of thousands of pleased user who’re getting pleasure out of the revolutionary effects of Anatrim right now. Less guzzling insanity, less kilos and more mirth in life!
<br>
<br>
<center>
<a href="http://www.borev.hk/?wzzgxwwjoll">
Click right here to scan outdone Anatrim dealings we are so proud to propose!!!
</a>
</center>
</b>
</p>
<font color="#D9EDFF">http://www.borev.hk/?wzzgxwwjoll</font>

</BODY></HTML>
------------6E5425409D37109--



Received: from ap.energyam.ru (ap.energyam.ru [195.18.36.135]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5E5j9RV017755; Wed, 13 Jun 2007 22:45:10 -0700 (MST) (envelope-from tabnovakilldyh@novakill.com)
Received: from 69.56.132.66 (HELO novakill.com) by imc.org with esmtp (Y1')056P= ZG+((:) id R3J8K1-2)5-+2-09 for ietf-pkix@imc.org; Thu, 14 Jun 2007 05:41:01 -0300
Date: 	Thu, 14 Jun 2007 05:41:01 -0300
From: "Dorothea Vance" <tabnovakilldyh@novakill.com>
X-Mailer: The Bat! (v2.00.3) Personal
X-Priority: 3 (Normal)
Message-ID: <002192053.43436797132246@thhebat.net>
To: ietf-pkix@imc.org
Subject: Last offer- Discount special for PE patch almost over
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------53B48D3B4F0C70"
X-Spam: Not detected

------------53B48D3B4F0C70
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: quoted-printable


After all the real stuff =96 with no more swindle! 
P.E.P. are piping hot right now! Well this is the true stuff not an=20=
imitation! 

One of the very originals, absolutely unique product is easy accessible=20=
anywhere!
 Take a look at just what people say about this stuff:

"I like how quickly your stuff had an affect upon my boyfriend, he=20=
can't stop babbling about how excited he is having his new calibre,=20=
length, and libido!"

Victoria K., Chicago

"Firstly I decided the free specimen package I was given was some kind=20=
of joke, till I actually tried taking the P.E.P. There are no words to=20=
depict how highly satisfied I am with the consequence from using the=20=
stuff for 6 brief weeks. I will be requesting continually!" 
Mike Brown, New York

Read more recommendations about this amazing product right here!
http://www.iromat.hk/?nayrjsegcarwq
------------53B48D3B4F0C70
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Don't be inadequate anymore</TITLE>
</HEAD>
<BODY>

<b>
After all the real stuff =96 with no more swindle! 
<br>
<a href=3D"http://www.iromat.hk/?nayrjsegcarwq">P.E.P.</a> are piping=20=
hot right now! Well this is the true stuff not an imitation! 
<br>
One of the very originals, absolutely unique product is easy accessible=20=
anywhere!
<br> Take a look at just what people say about this stuff:
<p>
<i>
"I like how quickly your stuff had an affect upon my boyfriend, he=20=
can't stop babbling about how excited he is having his new calibre,=20=
length, and libido!"
</i>
</p>
Victoria K., Chicago
<p>
<i>
"Firstly I decided the free specimen package I was given was some kind=20=
of joke, till I actually tried taking the P.E.P. There are no words to=20=
depict how highly satisfied I am with the consequence from using the=20=
stuff for 6 brief weeks. I will be requesting continually!" </i>
</p>
Mike Brown, New York
<center>
<a href=3D"http://www.iromat.hk/?nayrjsegcarwq">
Read more recommendations about this amazing product right here!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.iromat.hk/?nayrjsegcarwq</font>

</BODY></HTML>
------------53B48D3B4F0C70--



Received: from xdsl-10654.walbrzych.dialog.net.pl (xdsl-10654.walbrzych.dialog.net.pl [87.105.207.158]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5DIrlRd081510; Wed, 13 Jun 2007 11:53:56 -0700 (MST) (envelope-from hunnorcalsurplusveg@norcalsurplus.com)
Received: from [87.105.207.158] by mail.mcsweb1.com; Wed, 13 Jun 2007 18:53:56 -0100
Date: 	Wed, 13 Jun 2007 18:53:56 -0100
From: "Lessie Chandler" <hunnorcalsurplusveg@norcalsurplus.com>
X-Mailer: The Bat! (v2.00.7) Educational
Reply-To: hunnorcalsurplusveg@norcalsurplus.com
X-Priority: 3 (Normal)
Message-ID: <449689177.52890086367880@norcalsurplus.com>
To: ietf-openproxy@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------29CA486E29CABB4F"

------------29CA486E29CABB4F
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

LegalRXMedications drug-store propose all medicines that you want to recover your health with a little cost. 
We manage across the whole world with clients from America, Europe, and Asia. 
Today you got no need to seek drug-shop at your area.
We convey high-quality drugsworld-wide.
Visit our site to gain preparations you instantly demand straight to your home. 
http://logrepeat.hk/ 
We’re accredited by VISA and VeriSign accordingly we provide certain and dependable purchase.

------------29CA486E29CABB4F
Content-Type: text/html; charset=iso-8859-2
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drug-store propose all medicines that you want to recover your health with a little cost. <br>
We manage across the whole world with clients from America, Europe, and Asia. <br>
Today you got no need to seek drug-shop at your area.<br>
We convey high-quality drugsworld-wide.
<br>
<br>
<a href="http://logrepeat.hk/"><em>Visit our site to gain preparations you instantly demand straight to your home.</em></a></b> 
<br>
<font color="#D9EDFF">http://logrepeat.hk/</font> 
<br><b>We’re accredited by <font color="#FF0000"><em>VISA</em></font> and <font color="#FF0000"><em>VeriSign</em></font> accordingly we provide certain and dependable purchase.
</b>

</BODY></HTML>
------------29CA486E29CABB4F--



Received: from mail1.wss.vip.scd.yahoo.com ([213.234.235.98]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5D9DWqP099331; Wed, 13 Jun 2007 02:13:40 -0700 (MST) (envelope-from hunnonpublicationveg@nonpublication.com)
Received: from 64.60.0.28 (HELO mailqueue.telepacific.net) by imc.org with esmtp (AQ1W/1Q,= 32U3.0) id C7,C0<-=/Z1(O-L4 for ietf-pop3ext@imc.org; Wed, 13 Jun 2007 09:13:41 -0300
Date: 	Wed, 13 Jun 2007 09:13:41 -0300
From: "Linda Grayson" <hunnonpublicationveg@nonpublication.com>
X-Mailer: The Bat! (v3.5) Professional
X-Priority: 3 (Normal)
Message-ID: <776525602.04683210700098@thhebat.net>
To: ietf-pop3ext@imc.org
Subject: Doctors and Celebrities endorse Anatrim
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------67EA1B01B098FB09"
X-Spam: Not detected

------------67EA1B01B098FB09
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Don't miss the chance! =96 Anatrim =96 The latest and most fascinating=20=
product for over-weight people is now easily available =96 As were told=20=
on Oprah

Do you hold in your memory all the situations when you said to yourself=20=
you would do anything for being delivered from this terrible number of=20=
kilos? Fortunately, now no big price is to be paid. Thanks to Anatrim,=20=
the ground-breaking, you can get healthier mode of life and become really=20=
slimmer. Just notice what people say to us!
 
=93I always had an incredible private life until a year ago my=20=
girlfriend told me I was plump and in great need of keeping eye on my=20=
health. My life went the wrong way after that, till I was told about=20=
Anatrim =99. Since getting rid of about 20 kilogrames thanx to Anatrim, =20=
my private life is back on track, better even than before. Great thanks=20=
to you for the astonishing stuff and the first-rate maintenance service.=20=
Proceed with your valuable business!=94

 
Steve Burbon, San Diego

 
"There=92s nothing better than sliding into a bikini that I haven't=20=
worn for a long time. Now I feel slender, determined, and vigorous,=20=
thanks in great part to Anatrim! A plenty of thanks to you!"

 
Lusia R., Boston

Check out Anatrim, and  you shall join the world-wide community of=20=
thousands of pleased buyers who are enjoying the revolutionary results of=20=
Anatrim here and now. Less guzzling madness, less lbs and more gaiety in=20=
life!

Click here to look through outdone Anatrim deal we=92re so proud to=20=
offer!!!
http://www.kyolt.hk/?jgdpglabrhx

------------67EA1B01B098FB09
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Join the Anatrim revolution</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.kyolt.hk/?jgdpglabrhx">
Don't miss the chance! =96 Anatrim =96 The latest and most fascinating=20=
product for over-weight people is now easily available =96 As were told=20=
on Oprah
</a>
</center>
<br>
Do you hold in your memory all the situations when you said to yourself=20=
you would do anything for being delivered from this terrible number of=20=
kilos? Fortunately, now no big price is to be paid. Thanks to Anatrim,=20=
the ground-breaking, you can get healthier mode of life and become really=20=
slimmer. Just notice what people say to us!
 <br>
<br>
<i>
=93I always had an incredible private life until a year ago my=20=
girlfriend told me I was plump and in great need of keeping eye on my=20=
health. My life went the wrong way after that, till I was told about=20=
Anatrim =99. Since getting rid of about 20 kilogrames thanx to Anatrim, =20=
my private life is back on track, better even than before. Great thanks=20=
to you for the astonishing stuff and the first-rate maintenance service.=20=
Proceed with your valuable business!=94
</i>
 <br>
<b>
<i>
Steve Burbon, San Diego
</i>
</b>
 <br>
<br>
<i>
"There=92s nothing better than sliding into a bikini that I haven't=20=
worn for a long time. Now I feel slender, determined, and vigorous,=20=
thanks in great part to Anatrim! A plenty of thanks to you!"
</i>
 <br>
<b>
<i>
Lusia R., Boston
</i>
</b>
<br>
<br>
Check out Anatrim, and  you shall join the world-wide community of=20=
thousands of pleased buyers who are enjoying the revolutionary results of=20=
Anatrim here and now. Less guzzling madness, less lbs and more gaiety in=20=
life!
<br>
<br>
<center>
<a href=3D"http://www.kyolt.hk/?jgdpglabrhx">
Click here to look through outdone Anatrim deal we=92re so proud to=20=
offer!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.kyolt.hk/?jgdpglabrhx</font>

</BODY></HTML>
------------67EA1B01B098FB09--




Received: from mail.krona-market.ru (mail.krona-market.ru [213.167.48.106]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5D8WR7E096041; Wed, 13 Jun 2007 01:32:28 -0700 (MST) (envelope-from hunnordoniaschoolsveg@nordoniaschools.org)
Received: from [213.167.48.106] by mx1.neonetda.org; Wed, 13 Jun 2007 08:30:49 -0300
Date: 	Wed, 13 Jun 2007 08:30:49 -0300
From: "Elvin Booth" <hunnordoniaschoolsveg@nordoniaschools.org>
X-Mailer: The Bat! (v2.11) Educational
Reply-To: hunnordoniaschoolsveg@nordoniaschools.org
X-Priority: 3 (Normal)
Message-ID: <788806857.44645251587018@nordoniaschools.org>
To: ietf-pkix-archive@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------FFFFF840167CBD"

------------FFFFF840167CBD
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7bit

LegalRXMedications pharmacy offers all cures you feel need in in order to recover your health at lowest price. 
We operate through the planet with buyers from Europe, America and Asia. 
At this time you got no need to search for drugstore at your local area.
We can transfer high quality medicines to all parts of the world.
Come please to our site & gain pharmas you need immediately direct to your abode. 
http://babyfraction.hk/ 
We are ratified by VeriSign and VISA then we support secure and dependable acquisition.

------------FFFFF840167CBD
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> pharmacy offers all cures you feel need in in order to recover your health at lowest price. <br>
We operate through the planet with buyers from Europe, America and Asia. <br>
At this time you got no need to search for drugstore at your local area.<br>
We can transfer high quality medicines to all parts of the world.
<br>
<br>
<a href="http://babyfraction.hk/"><em>Come please to our site & gain pharmas you need immediately direct to your abode.</em></a></b> 
<br>
<font color="#D9EDFF">http://babyfraction.hk/</font> 
<br><b>We are ratified by <font color="#FF0000"><em>VeriSign</em></font> and <font color="#FF0000"><em>VISA</em></font> then we support secure and dependable acquisition.
</b>

</BODY></HTML>
------------FFFFF840167CBD--



Received: from AToulouse-157-1-81-253.w86-213.abo.wanadoo.fr (AToulouse-157-1-81-253.w86-213.abo.wanadoo.fr [86.213.44.253]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5CJsUnq049452; Tue, 12 Jun 2007 12:54:38 -0700 (MST) (envelope-from pernetrentdis@netrent.net)
Received: from 199.203.54.184 (HELO netrent.net) by imc.org with esmtp (LC.825J36J3 52C?I+) id W?V-(/-R3356+-,0 for ietf-pkix-request@imc.org; Tue, 12 Jun 2007 19:54:32 -0100
Date: 	Tue, 12 Jun 2007 19:54:32 -0100
From: "April Rodriquez" <pernetrentdis@netrent.net>
X-Mailer: The Bat! (v3.71.01) UNREG / CD5BF9353B3B7091
X-Priority: 3 (Normal)
Message-ID: <745916733.41632726287862@thhebat.net>
To: ietf-pkix-request@imc.org
Subject: Dude check out this sweet site
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------8D38676E0CAB486E"
X-Spam: Not detected

------------8D38676E0CAB486E
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: 7bit



Ultimately the true stuff – no more ramp! 
P.E.P. are very hot right this time! Well this is the true stuff not an imitation! 

One of the very prominents, totally unrivalled stuff is accessible anywhere!
 Read just what people tell about this stuff:

"I was impressed how quick your product affected on my boyfriend, he can not stop babbling about how excited he is having such new girth, extent, and libido!"

Silvia D., Washington

"At first I thought the gratuitous specimen parcel I received was some kind of joke, till I have taken to take the P.E.P. Words cannot depict how greatly pleased I am with the effects from using this patch for 6 brief weeks. I will be ordering at every turn!" 
Serge Smith, Chicago

Check up more references about this astonishing product here now!
http://www.circoba.com/?tojtluntmdeiq

------------8D38676E0CAB486E
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Make her worship you</TITLE>
</HEAD>
<BODY>

<b>
Ultimately the true stuff – no more ramp! 
<br>
<a href="http://www.circoba.com/?tojtluntmdeiq">P.E.P.</a> are very hot right this time! Well this is the true stuff not an imitation! 
<br>
One of the very prominents, totally unrivalled stuff is accessible anywhere!
<br> Read just what people tell about this stuff:
<p>
<i>
"I was impressed how quick your product affected on my boyfriend, he can not stop babbling about how excited he is having such new girth, extent, and libido!"
</i>
</p>
Silvia D., Washington
<p>
<i>
"At first I thought the gratuitous specimen parcel I received was some kind of joke, till I have taken to take the P.E.P. Words cannot depict how greatly pleased I am with the effects from using this patch for 6 brief weeks. I will be ordering at every turn!" </i>
</p>
Serge Smith, Chicago
<center>
<a href="http://www.circoba.com/?tojtluntmdeiq">
Check up more references about this astonishing product here now!
</a>
</center>
</b>
<font color="#D9EDFF">http://www.circoba.com/?tojtluntmdeiq</font>

</BODY></HTML>
------------8D38676E0CAB486E--



Received: from mail.hostglobe.com ([86.110.162.2]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5CGmE3U036300; Tue, 12 Jun 2007 09:48:15 -0700 (MST) (envelope-from pernetzsolutionsdis@netzsolutions.com)
Received: from 208.75.64.250 (HELO mail.netzsolutions.com) by imc.org with esmtp (9/7.)H1X; C'S?) id ,<Z,0>-920657-D, for ietf-schema-reg@imc.org; Tue, 12 Jun 2007 16:48:27 -0300
Date: 	Tue, 12 Jun 2007 16:48:27 -0300
From: "Cleo Boucher" <pernetzsolutionsdis@netzsolutions.com>
X-Mailer: The Bat! (v2.00.9) Business
X-Priority: 3 (Normal)
Message-ID: <799666713.56362900280174@thhebat.net>
To: ietf-schema-reg@imc.org
Subject: Anatrim will change your life
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------F2915AF053BB4F2"
X-Spam: Not detected

------------F2915AF053BB4F2
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Take advantage of the opportunity! =96 Anatrim =96 The newest & most=20=
fascinating flesh loss product is now readily available =96 As could be=20=
seen on Oprah

Do you hold in your memory all the times when you told yourself you=20=
would do any thing to get rid of this terrible number of kilos? Happily,=20=
now no major sacrifice is required. Thanks to Anatrim, the earth-shaking,=20=
you can get healthier lifestyle and become really thinner. Just look at=20=
what our clients write!
 
=93I always had a great life until a year ago the girl I was meeting=20=
said to me I was portly and in great need of being careful to my health.=20=
Life had changed the wrong way after that, till I was told about Anatrim=20=
=99. Since getting rid of about 40 pounds only thanks to Anatrim,  my=20=
private life is back on track, much better than even before. Great thanks=20=
for the incredible stuff and the first-class maintenance service. Keep on=20=
the worthy action!=94

 
Steve Doubt, Las Vegas

 
"There=92s nothing better than sliding into a bikini that I have not=20=
been dressed in for a long period. I feel slim, defined, and healthy,=20=
thanx to a considerable degree to Anatrim! Thanks a lot!"

 
Amely S., Boston

Discover Anatrim, and  you will join the world-wide association of=20=
thousands of happy buyers who are getting pleasure out of the=20=
revolutionary results of Anatrim right here and right now. Less guzzling=20=
mania, less lbs and more happiness in life!

Proceed here to look at our outdone Anatrim bargain!!!
http://www.flagho.hk/?puuggydun
------------F2915AF053BB4F2
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Less weight - more pleasure and joy</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.flagho.hk/?puuggydun">
Take advantage of the opportunity! =96 Anatrim =96 The newest & most=20=
fascinating flesh loss product is now readily available =96 As could be=20=
seen on Oprah
</a>
</center>
<br>
Do you hold in your memory all the times when you told yourself you=20=
would do any thing to get rid of this terrible number of kilos? Happily,=20=
now no major sacrifice is required. Thanks to Anatrim, the earth-shaking,=20=
you can get healthier lifestyle and become really thinner. Just look at=20=
what our clients write!
 <br>
<br>
<i>
=93I always had a great life until a year ago the girl I was meeting=20=
said to me I was portly and in great need of being careful to my health.=20=
Life had changed the wrong way after that, till I was told about Anatrim=20=
=99. Since getting rid of about 40 pounds only thanks to Anatrim,  my=20=
private life is back on track, much better than even before. Great thanks=20=
for the incredible stuff and the first-class maintenance service. Keep on=20=
the worthy action!=94
</i>
 <br>
<b>
<i>
Steve Doubt, Las Vegas
</i>
</b>
 <br>
<br>
<i>
"There=92s nothing better than sliding into a bikini that I have not=20=
been dressed in for a long period. I feel slim, defined, and healthy,=20=
thanx to a considerable degree to Anatrim! Thanks a lot!"
</i>
 <br>
<b>
<i>
Amely S., Boston
</i>
</b>
<br>
<br>
Discover Anatrim, and  you will join the world-wide association of=20=
thousands of happy buyers who are getting pleasure out of the=20=
revolutionary results of Anatrim right here and right now. Less guzzling=20=
mania, less lbs and more happiness in life!
<br>
<br>
<center>
<a href=3D"http://www.flagho.hk/?puuggydun">
Proceed here to look at our outdone Anatrim bargain!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.flagho.hk/?puuggydun</font>

</BODY></HTML>
------------F2915AF053BB4F2--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C3QwYs092171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 20:26:58 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C3QwMf092170; Mon, 11 Jun 2007 20:26:58 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C3Qv5b092163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 20:26:57 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5C3Qsbg022450; Mon, 11 Jun 2007 20:26:54 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 20:26:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 20:25:42 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62EA@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmAAEhMlkA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 12 Jun 2007 03:26:54.0077 (UTC) FILETIME=[85F952D0:01C7ACA1]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5C3Qw5a092165
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>

The null assurance CAs are already out there :-(

Have been for five years :-(  :-(


> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Kemp, David P.
> Sent: Monday, June 11, 2007 3:42 PM
> To: ietf-pkix@imc.org
> Subject: RE: Three short fixes
> 
> 
> In order to achieve backwards compatibility with a billion 
> browsers, you would have to mark any new extension as 
> non-critical, where it would be ignored by every single 
> browser currently in existence.
> 
> Therefore users would be told that their communication is 
> secure while issuing practices permit (no, positively 
> encourage, once the word on this extension gets out) web site 
> spoofing.
> 
> If you want to use Peter's OID for this, no one can stop you. 
>  But the PKIX WG can refuse to assign an OID whose ostensible 
> purpose is to enable non-advertised encryption but whose 
> actual effect on current browsers would be to advertise 
> secure communications while using null-assurance certificates.
> 
> 
> 
> 
> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org]
> On Behalf Of Hallam-Baker, Phillip
> 
> These are not anonymous communications, they are merely 
> communications that do not require the level of assurance 
> that is necessary to alert the user to tell tham that the 
> communication is secure.
>  
> > > The reason for using a certificate is to allow for backwards 
> > > compatibility with a billion installed browsers.
> 
> 
> -----------
> 
> P.S., the difference between anonymous communications and
> communications for which the participants can claim any desired
> name (e.g. my webserver operating as https://www.verisign.com)
> and into which third parties (e.g. hotel wireless APs) may
> insert themselves eludes me. One definition of anonymous is
> "unnamed", but the second definition is "of unknown origin".
> Spoofed names certainly seem to fit the second definition.
> 
> 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1lfPh086811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 18:47:41 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C1levo086810; Mon, 11 Jun 2007 18:47:40 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (larry.its.auckland.ac.nz [130.216.12.34]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1le88086803 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 18:47:40 -0700 (MST) (envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id AFD591834A; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1]) by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVSixmwTFiiS; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 980CE18345; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33]) by iris.cs.auckland.ac.nz (Postfix) with ESMTP id 6BDE61280A1; Tue, 12 Jun 2007 13:47:39 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian)) id 1HxvTy-0001MI-00; Tue, 12 Jun 2007 13:47:42 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org
Subject: RE: Three short fixes
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
Message-Id: <E1HxvTy-0001MI-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 13:47:42 +1200
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>

I wrote:

>I'm not really too fussed about it, I'll let users keep using Xyzzy certs,

Oops, what I meant with "Xyzzy certs" is that that's the name of the OID used
to indicate that the cert is merely a bit-bag for a public key.  Currently
it's used as a policy OID, which seemed to be the best place to put it,
although a standard extension would be a better way to handle it.  The policy
is "This certificate isn't worth the paper it's not printed on".

Peter.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1hxil086639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 18:43:59 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C1hxuC086638; Mon, 11 Jun 2007 18:43:59 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (larry.its.auckland.ac.nz [130.216.12.34]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C1hwel086629 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 18:43:59 -0700 (MST) (envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 73FF218345; Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1]) by localhost (larry.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYa49ci1FkZh; Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 5B91118334; Tue, 12 Jun 2007 13:43:57 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33]) by iris.cs.auckland.ac.nz (Postfix) with ESMTP id 91F351280A1; Tue, 12 Jun 2007 13:43:54 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian)) id 1HxvQM-0001HJ-00; Tue, 12 Jun 2007 13:43:58 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org
Subject: RE: Three short fixes
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
Message-Id: <E1HxvQM-0001HJ-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 13:43:58 +1200
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>

"Kemp, David P." <DPKemp@missi.ncsc.mil> writes:

>More to the point, the intent is to create an attribute that says:
>
>  "This certificate is merely a convenient universally-accepted
>   blob for communicating a public key and a name/email address/URL"
>*AND*
>  "There is no claim that the public key and the name/email/URL
>   have any relationship whatsoever"

Sure, the latter was implied in the former.

>In other words, the name/email/URL could belong to Bank of America but the
>key pair and certificate request could have been created by Phish-R-Us, and
>no claims to the contrary are made by the issuer. 

More or less.  As I said, there are people using certs simply as a universal
container for a public key because there's nothing else available.  They don't
care about any cert semantics, they just need a means of getting a key from A
to B in a format that B can process.  Providing some means of indicating this
in the cert would be useful.

I'm not really too fussed about it, I'll let users keep using Xyzzy certs,
however if there's no centralised record of this you end up with a pile of ad
hoc approaches instead, including the current one of taking otherwise normal-
looking certs and ignoring all the cert semantics.  The choice is really:

  1) Use null-semantics certs that look like normal certs.

  2) Use null-semantics certs but at least mark them as such.

Of these two, (2) seems to be the better approach.

Peter.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C01iaE081735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 17:01:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5C01i2w081734; Mon, 11 Jun 2007 17:01:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5C01heO081728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 17:01:44 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5C01QeT003784; Mon, 11 Jun 2007 17:01:29 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 17:01:29 -0700
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"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 17:00:16 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62D5@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uAABf0AkA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Peter Lipp" <peter.lipp@iaik.tugraz.at>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 12 Jun 2007 00:01:29.0002 (UTC) FILETIME=[D3A820A0:01C7AC84]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5C01ieN081729
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>

Case in point here being your S/MIME cert which does not satisfy my
Outlook chaining so give a warning.

Yet I can get mail from plenty of places without any security and
without a warning either.

Wouldn't it be nice if a cert could say 'the correct course of action if
you don't like me is to simply show the email without any indication the
message is secure'.

Why do folk feel that the user has to be told about merely sub-standard
security when 99% of the Internet has no security at all? 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Peter Lipp
> Sent: Monday, June 11, 2007 5:23 PM
> To: Hallam-Baker, Phillip; ietf-pkix@imc.org
> Subject: AW: Three short fixes
> 
> > The information to be encoded here relates to the issue 
> practices of 
> > the certificate. Therefore they go into the certificate.
> Like the warning sign for an unusable safety-belt that is 
> sewn into the belt
> saying: "manufactured without care, don't use for driving"? 
> And the belt is applied automatically too, without the user 
> noticing, so he wouldn't be realizing that the belt breaks...
> 
> Earlier on you wrote:
> > In many cases all that is required is to turn on encryption.
> This would be the case with TLS-anon-cipher suites. Because 
> if "all that is required" is encryption, we don't care how it 
> is initiated. So there must be a use case.... 
> 
> ...like a pre-manufactured bulk certificate that you ship to 
> your customer who puts it into one shipped appliance, so you 
> as the issuer have no full control on what happens with the 
> certificate (and probably pregenerated key) and thus can't 
> give out any warranties, but the overall procedure may be 
> safe enough for its purposes? Thus, if the certificate should 
> be misused, it might not do any harm elsewhere if this 
> extension is in. Then there is a difference to the anon-cipher-suite.
> 
> Otherwise, I don't get the point... Since you want to sell 
> your certificates, you should first sell your story better.
> 
> Peter
> 



Received: from host144.190-30-73.telecom.net.ar (host144.190-30-73.telecom.net.ar [190.30.73.144]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BNsqvU081399; Mon, 11 Jun 2007 16:54:56 -0700 (MST) (envelope-from gtrupert@manawatu.gen.nz)
Received: from [10.0.17.89] by 141.red-217-124-20.dialup.dynamic.ccgg.telefonica.net id w4M1Lh5grK8b; Tue, 12 Jun 2007 02:54:26 +0300
Message-ID: <00a901c7ac83$d524cb00$5911000a@141.red-217-124-20.dialup.dynamic.ccgg.telefonica.net>
From: "Vanessa C" <gtrupert@manawatu.gen.nz>
To: "Erich" <kix-request@imc.org>
Subject: Re[2]:  greetings from me, dear
Date: Tue, 12 Jun 2007 02:54:26 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit

Hello, Erich

I don't want to get up into darkness of long, empty and lonely cool days. 
I can't be happy to something if I don't have my soul mate, who will 
understand me...I want to change my life and let love to come into it. I 
looked here at search of a good man, my destiny...And I found you! Give me a 
chance to come into your life and to bring into your heart true love  We are 
masters of our destiny and we create it. I will wait for your letter with 
hopes and dreams http://allwaylove.com/womans


Waiting for your answer

Vanessa C




Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BMFiFA077349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 15:15:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BMFigQ077348; Mon, 11 Jun 2007 15:15:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail1.exchange.microsoft.com [131.107.1.17]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BMFgjq077340 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 15:15:43 -0700 (MST) (envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-01.exchange.corp.microsoft.com (157.54.54.216) by DF-GWY-05.exchange.corp.microsoft.com (157.54.63.146) with Microsoft SMTP Server (TLS) id 8.0.685.24; Mon, 11 Jun 2007 15:15:42 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.8]) by df-bhd-01.exchange.corp.microsoft.com ([157.54.54.216]) with mapi; Mon, 11 Jun 2007 15:15:42 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>, "ietf-pkix@imc.org" <ietf-pkix@imc.org>
Date: Mon, 11 Jun 2007 15:15:39 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmAABcwnoA==
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC926A9696A8@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <20070611161139.GA27557@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com> <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
In-Reply-To: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
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"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BMFhjp077341
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>

I have to agree with Dave here. For HTTPS these certificates would be practically useless for at least 5 years and probably more  given the lag time on OS and browser upgrades. Now other applications of TLS already support the concept of "confidentiality only" TLS with certificates. I am thinking here of SMTP. SMTP servers use "opportunistic TLS" where the SMTP server has a policy to pick the STARTTLS verb whenever it its offered by the receiving server. When operating under optimistic mode the sending server does not validate the receiving servers certificate because the alternative course of action with validation errors is to send in the clear. Because the sending server does not validate the receiving server certificate a common practice is to use self signed certificates which clearly make no warranty about the identity of the owner. Most use of TLS with SMTP over the internet uses opportunistic TLS.  I don't see why such a strategy does not work elsewhere if all you want is confidentiality. An interesting side bar is that the anonymous cipher suites would not work in this scenario because these same servers have a subset of domains they do want to authenticate. There is not enough data at the time of the negotiation for the receiving server to decide they do not want to authenticate the sending server so it has to pick a cipher suite with certificates then it has the option to skip validation or not later in the session.

Trevor

* -----Original Message-----
* From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
* pkix@mail.imc.org] On Behalf Of Kemp, David P.
* Sent: Monday, June 11, 2007 12:42 PM
* To: ietf-pkix@imc.org
* Subject: RE: Three short fixes
*
*
* In order to achieve backwards compatibility with a billion browsers,
* you would have to mark any new extension as non-critical, where it
* would be ignored by every single browser currently in existence.
*
* Therefore users would be told that their communication is secure while
* issuing practices permit (no, positively encourage, once the word
* on this extension gets out) web site spoofing.
*
* If you want to use Peter's OID for this, no one can stop you.  But
* the PKIX WG can refuse to assign an OID whose ostensible purpose is
* to enable non-advertised encryption but whose actual effect on current
* browsers would be to advertise secure communications while using
* null-assurance certificates.
*
*
*
*
* -----Original Message-----
* From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-
* pkix@mail.imc.org]
* On Behalf Of Hallam-Baker, Phillip
*
* These are not anonymous communications, they are merely communications
* that do not require the level of assurance that is necessary to alert
* the user to tell tham that the communication is secure.
*
* > > The reason for using a certificate is to allow for backwards
* > > compatibility with a billion installed browsers.
*
*
* -----------
*
* P.S., the difference between anonymous communications and
* communications for which the participants can claim any desired
* name (e.g. my webserver operating as https://www.verisign.com)
* and into which third parties (e.g. hotel wireless APs) may
* insert themselves eludes me. One definition of anonymous is
* "unnamed", but the second definition is "of unknown origin".
* Spoofed names certainly seem to fit the second definition.




Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLSiaR061490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 14:28:45 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BLSiOH061484; Mon, 11 Jun 2007 14:28:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLShWK061457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 14:28:43 -0700 (MST) (envelope-from pbaker@verisign.com)
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 l5BLSO2B028232; Mon, 11 Jun 2007 14:28:26 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 14:28:23 -0700
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"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 14:27:11 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A62B9@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uAAAJ3lAA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Peter Lipp" <peter.lipp@iaik.tugraz.at>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 21:28:23.0972 (UTC) FILETIME=[70F3C640:01C7AC6F]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BLShWJ061460
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>

No: like the roll cage which is stamped 'not certified for competition
use'.

There are plenty of safety measure on my cars which I am completely
unaware of which are perfectly safe for normal road driving but not
designed for competition use.

Building a certification path up from the MAC address is prefectly
sensible and an appropriate use for PKIX. But it is not by itself
sufficient to present a trust statement. There is no accountability - by
design.

What I am working towards here is a multilayer security approach and I
want to use PKIX at a lower level than the SSL folk did.

> -----Original Message-----
> From: Peter Lipp [mailto:peter.lipp@iaik.tugraz.at] 
> Sent: Monday, June 11, 2007 5:23 PM
> To: Hallam-Baker, Phillip; ietf-pkix@imc.org
> Subject: AW: Three short fixes
> 
> > The information to be encoded here relates to the issue 
> practices of 
> > the certificate. Therefore they go into the certificate.
> Like the warning sign for an unusable safety-belt that is 
> sewn into the belt
> saying: "manufactured without care, don't use for driving"? 
> And the belt is applied automatically too, without the user 
> noticing, so he wouldn't be realizing that the belt breaks...
> 
> Earlier on you wrote:
> > In many cases all that is required is to turn on encryption.
> This would be the case with TLS-anon-cipher suites. Because 
> if "all that is required" is encryption, we don't care how it 
> is initiated. So there must be a use case.... 
> 
> ...like a pre-manufactured bulk certificate that you ship to 
> your customer who puts it into one shipped appliance, so you 
> as the issuer have no full control on what happens with the 
> certificate (and probably pregenerated key) and thus can't 
> give out any warranties, but the overall procedure may be 
> safe enough for its purposes? Thus, if the certificate should 
> be misused, it might not do any harm elsewhere if this 
> extension is in. Then there is a difference to the anon-cipher-suite.
> 
> Otherwise, I don't get the point... Since you want to sell 
> your certificates, you should first sell your story better.
> 
> Peter
> 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLN69e059801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 14:23:06 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BLN6jg059799; Mon, 11 Jun 2007 14:23:06 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailrelay.tugraz.at (mailrelay.tu-graz.ac.at [129.27.2.202]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BLN3EB059775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 14:23:05 -0700 (MST) (envelope-from peter.lipp@iaik.tugraz.at)
Received: from thor.iaik.tugraz.at (mail1.iaik.tugraz.at [129.27.152.30]) by mailrelay2.tugraz.at (8.14.1/8.14.1) with ESMTP id l5BLMxuM022792; Mon, 11 Jun 2007 23:22:59 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by thor.iaik.tugraz.at (Postfix) with ESMTP id 835E9194002; Mon, 11 Jun 2007 23:22:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at iaik.tugraz.at
Received: from thor.iaik.tugraz.at ([127.0.0.1]) by localhost (thor.iaik.tugraz.at [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oksrijmEqThK; Mon, 11 Jun 2007 23:22:58 +0200 (CEST)
Received: from tabletlipp (unknown [129.27.152.247]) by thor.iaik.tugraz.at (Postfix) with ESMTP; Mon, 11 Jun 2007 23:22:58 +0200 (CEST)
From: "Peter Lipp" <peter.lipp@iaik.tugraz.at>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, <ietf-pkix@imc.org>
References: <20070611161139.GA27557@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Subject: AW: Three short fixes
Date: Mon, 11 Jun 2007 23:22:58 +0200
Organization: IAIK TU Graz
Message-ID: <034e01c7ac6e$aef74850$0ce5d8f0$@lipp@iaik.tugraz.at>
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAcY0uA=
Content-Language: de-at
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="----=_NextPart_000_0349_01C7AC7F.72128970"; protocol="application/x-pkcs7-signature"; micalg=SHA1
X-Spam-Scanner: SpamAssassin 3.002000 
X-Spam-Score-relay: 1.4
X-Scanned-By: MIMEDefang 2.62 on 129.27.10.19
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>

Dies ist eine mehrteilige Nachricht im MIME-Format.

------=_NextPart_000_0349_01C7AC7F.72128970
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

> The information to be encoded here relates to the issue practices of
> the certificate. Therefore they go into the certificate.
Like the warning sign for an unusable safety-belt that is sewn into the belt
saying: "manufactured without care, don't use for driving"? And the belt is
applied automatically too, without the user noticing, so he wouldn't be
realizing that the belt breaks...

Earlier on you wrote:
> In many cases all that is required is to turn on encryption.
This would be the case with TLS-anon-cipher suites. Because if "all that is
required" is encryption, we don't care how it is initiated. So there must be
a use case.... 

...like a pre-manufactured bulk certificate that you ship to your customer
who puts it into one shipped appliance, so you as the issuer have no full
control on what happens with the certificate (and probably pregenerated key)
and thus can't give out any warranties, but the overall procedure may be
safe enough for its purposes? Thus, if the certificate should be misused, it
might not do any harm elsewhere if this extension is in. Then there is a
difference to the anon-cipher-suite.

Otherwise, I don't get the point... Since you want to sell your
certificates, you should first sell your story better.

Peter

------=_NextPart_000_0349_01C7AC7F.72128970
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIhczCCA2Aw
ggJIoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwQTEQMA4GA1UEChMHRXVyb1BLSTEtMCsGA1UEAxMk
RXVyb1BLSSBSb290IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk5MTIyOTE3MzAzOVoXDTEw
MTIzMTEyMDAwMFowQTEQMA4GA1UEChMHRXVyb1BLSTEtMCsGA1UEAxMkRXVyb1BLSSBSb290IENl
cnRpZmljYXRpb24gQXV0aG9yaXR5MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA/y/8
y4eFIIJCIiQNiZrsHev0yzqE6Gc9w69BaAoHoYqfmTa19XoQcNHrAiumdfEnwznsgwfomt6lmpbX
nUFbbS1EJ1T3V5s7myFWqVhaB5tbt6C4QYEqdZhwZgLCphrx1fyGBeLe9PbVEJaXmYIyM6W48ze/
fV6Gtl9siahhgQA8xyoiZ+afNC7DJ8d1Uf1MiF2SRKutdVJQA3yR9aocFMzWtBfNI9LZO/6Wi4Z1
q2Q7H2TRpALoECwQ1IvpwSlLuBYnKX2C+xxl+H0ZrYPqC7kNbx5WHtmFbPlBiOO3u43eGH9b244p
0NDlK8dp8fM/saOO5YF8DGxCe1cKxAo0twIDAQABo2MwYTAfBgNVHSMEGDAWgBSM3IuxpUqQ506I
cxg8ndVefuSyzTAdBgNVHQ4EFgQUjNyLsaVKkOdOiHMYPJ3VXn7kss0wDgYDVR0PAQH/BAQDAgHG
MA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADggEBAFto/551vUIbQntYkHVfShcva5zq
Sh+N7RxY7lAZYKYLzb9Nf61zFy5/1vNZ7i05mcHYWHI5XVGWUellBi7QKzi0GlJE0DB43PxJFP7N
L/DLljYOb4Qt2bBRTVbX0fIlmtmvoAOLgR9e3F3ej7s6g9BzBQO+T99pHrN8W5RVmeakmBkL8uGl
qE/xQ7G3iRv1KafBW2dmdKUqn4vXAFhqs0WJU9HYLvGdkRcMHf7z71aUJXQdUnEZH6S+jwi75pnz
ER6vGYNCTHKpiF2GIND3D3SfhAopEmHf+xudP7iHyQw2RDiJJqV1Z93EJnDA0Wrob8LKEegdpQl/
3BCNDxJzAWgwggSKMIIDcqADAgECAgERMA0GCSqGSIb3DQEBBQUAMEExEDAOBgNVBAoTB0V1cm9Q
S0kxLTArBgNVBAMTJEV1cm9QS0kgUm9vdCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wMjEy
MTIxNzAwMDBaFw0wODEyMzEwOTAwMDBaMFIxCzAJBgNVBAYTAkFUMRAwDgYDVQQKEwdFdXJvUEtJ
MTEwLwYDVQQDEyhFdXJvUEtJIEF1c3RyaWFuIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoE5gWK44kT3O3Yenp0GT6+gkypmIAlhqYAcmokav
l3WaQ4BhBlAv4ORtBF/hVObG1ugPCep7cTNyoXZ+sNIbmlLzBxzrRpT4nYQIEu3IXR108c6APycH
+9vbYIUQrsCKx8Qs/csU5rdOxc15pHsZLJiiCYATB0GWyrcbVcoNgAj6crv7Lx37SlENgMAssOoG
4E3/2wrCQ2n/QiqBEosscpnEqQs6ABvdQiLKSpfVQJA77l9ujQ1C/ugtlYwAr5GrtSOhOTYvKB4t
uVleqlHFzJoA6XaWQRpD4Oy4ymF0+5IAe9q+lOQ6U57rWIZ0MMr8xAmf7VZtmk0KJYCkAl3DPwID
AQABo4IBejCCAXYwTAYJYIZIAYb4QgENBD8WPUlzc3VlZCB1bmRlciBwb2xpY3k6CiBodHRwOi8v
d3d3LmV1cm9wa2kub3JnL2NhL3Jvb3QvY3BzLzEuMS8wOAYIKwYBBQUHAQEELDAqMCgGCCsGAQUF
BzABhhxodHRwOi8vb2NzcC5ldXJvcGtpLm9yZzo4MDI2MDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6
Ly93d3cuZXVyb3BraS5vcmcvY2Evcm9vdC9jcmwvY3JsLmRlcjAPBgNVHRMBAf8EBTADAQH/ME4G
A1UdIARHMEUwQwYKKwYBBAGpBwEBATA1MDMGCCsGAQUFBwIBFidodHRwOi8vd3d3LmV1cm9wa2ku
b3JnL2NhL3Jvb3QvY3BzLzEuMS8wDgYDVR0PAQH/BAQDAgH2MB0GA1UdDgQWBBTQlAuMnkklreDR
A1zeuwDyvzWc9zAfBgNVHSMEGDAWgBSM3IuxpUqQ506Icxg8ndVefuSyzTANBgkqhkiG9w0BAQUF
AAOCAQEAQNx/GA75gR3WJWcf6A9/yvQWAHeUJNGCrB5miAg5Cd+Ac+7rAmdyWS+6ovB2vsbiwDoA
BuVuntCVVRdiu26/eXstDjFwUo99X6CmAMhHqv9MolzMjKRzwKk9QKDP4xUoEk/fXoIhUPHbeN3T
3bNpQlW6RH3mkIS08/3Rlncv0AOUtk+EO1YuDwy1WAdwp5Wo8E1pYxkQlalzDzSZrt6SpOAdM5dZ
Vj7PQrjswKfGj48OOIxmKliuojmPy+UZv8PoFkB8MX9Cqk5gOlWUt5pTvl6x/iP32h4kF0bCF76D
7sx5SjekbNmEtZ1thHQLY7aalOVBF1K+mJvYWMGrnvB8djCCBLQwggOcoAMCAQICFQCEWAP+T9cN
Wn701+2abEum54RkPDANBgkqhkiG9w0BAQUFADBSMQswCQYDVQQGEwJBVDEQMA4GA1UEChMHRXVy
b1BLSTExMC8GA1UEAxMoRXVyb1BLSSBBdXN0cmlhbiBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAe
Fw0wMjEyMTcxMjI1MDdaFw0wODEyMzAyMjU5MzBaMIHMMQswCQYDVQQGEwJBVDENMAsGA1UEBxME
R3JhejEZMBcGA1UECRMQSW5mZmVsZGdhc3NlIDE2YTEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZ
IE9GIFRFQ0hOT0xPR1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlv
biBQcm9jZXNzaW5nIGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UEAxMYSUFJSyBFdXJvUEtJIElu
dHJhbmV0IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz8KxI9Ubcz1kWVBqbVr9
vyrID0NBcjBx2HpoZ//kI1L+dWg/X5nKqlFPwoK6CROrC7TenGaEPdYJ8SEvxsPeTzYVF+o2XzeD
xeSvxl892VMf23L3JuLYxRhtdo8Vk+CDfXd6E+UjDI4dQMNARN+cskp5agXH1h0e4LQabHQKL8NU
8cvAbfL5ga4Xtu3WNHd2yYrVCztQhtfRtEN++K5yfwmPWRB7M9OPfBI+fnhZ3n0hIpSe5EDQzVNs
wse8brtI3btMq2+WNfkQXYCRwqDJXVGzgNh5DTs/WC8omFj1kcU/X3D4F7/Y0mLvrfgwdDDD8+d2
XGCC1bKKbI4SnblTuQIDAQABo4IBBDCCAQAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC
AcYwHwYDVR0jBBgwFoAU0JQLjJ5JJa3g0QNc3rsA8r81nPcwVgYDVR0gBE8wTTBLBgwrBgEEAZUS
AQIBAQEwOzA5BggrBgEFBQcCARYtaHR0cDovL2V1cm9wa2kuaWFpay5hdC9jYS9ldXJvcGtpLWF0
L2Nwcy8xLjEvMEUGA1UdHwQ+MDwwOqA4oDaGNGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2EvZXVy
b3BraS1hdC9jcmwvYXVzdHJpYS5jcmwwHQYDVR0OBBYEFIRYA/5P1w1afvTX7ZpsSrS7EDPSMA0G
CSqGSIb3DQEBBQUAA4IBAQB/O6DNrOa1v+n+fsglJAmAYQrMQZisqnRoqGXhEK1IMCc55wRx8iXq
ZTIYRm7F4PtNK0tmqP80DvCf/Gni0Sx/Lh5fJuUKlyP0OU8v474TnubUnKYimeFeJjqTI0dIddlj
bwHBbeLMvTksX8cIi8Hb/yhaMwTTPfg0fDlBpjjundgghlBYyDKLwDPFnpwM+TVGSvBlkSIELPdv
DY1f7NQz8QWRi7HhY2OOzZuSfU7FBFejQVzvcqangwZWHZZwdb5QgBOirqAeFJrLChheXRdJ2iWH
WKGRGQ0LShkhGNUzTJsTobjL1/gLjfu+uOtr5XBPPBsR2MjvH+ZqQ7maVxQGMIIFKTCCBBGgAwIB
AgICA+owDQYJKoZIhvcNAQEFBQAwgcUxCzAJBgNVBAYTAkFUMSYwJAYDVQQKEx1HUkFaIFVOSVZF
UlNJVFkgT0YgVEVDSE5PTE9HWTFIMEYGA1UECxM/SW5zdGl0dXRlIGZvciBBcHBsaWVkIEluZm9y
bWF0aW9uIFByb2Nlc3NpbmcgYW5kIENvbW11bmljYXRpb25zMSEwHwYDVQQLExhJQUlLIEV1cm9Q
S0kgSU5UUkFORVQgQ0ExITAfBgNVBAMTGElBSUsgRXVyb1BLSSBUVS1HUkFaIFNJRzAeFw0wNzA0
MjUwOTUzMDhaFw0wODA0MjQwOTUzMDhaMIHuMQ4wDAYDVQQqEwVQZXRlcjENMAsGA1UEBBMETGlw
cDETMBEGA1UEAxMKUGV0ZXIgTGlwcDEmMCQGA1UEChMdR3JheiBVbml2ZXJzaXR5IG9mIFRlY2hu
b2xvZ3kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNz
aW5nIGFuZCBDb21tdW5pY2F0aW9uczEZMBcGA1UECRMQSW5mZmVsZGdhc3NlIDE2YTENMAsGA1UE
BxMER3JhejEPMA0GA1UECBMGU3R5cmlhMQswCQYDVQQGEwJBVDCBnzANBgkqhkiG9w0BAQEFAAOB
jQAwgYkCgYEAtUB8RyTq8pYMf09Ux3d94Yf2UkwCSYehLxdph4u6vV8ApLpdDnraux36axtVymdv
JRGqfkhleEraizu/hAP9Zn/R/p+7fXKFMRxBctngfv8WISOKw/fE4JQwnzqF8ilguPYdL/41Pe8r
3Dqr2gRg3yYsd4SNrtruSVmmUA3h81UCAwEAAaOCAXowggF2MA4GA1UdDwEB/wQEAwIGwDAMBgNV
HRMBAf8EAjAAMFQGA1UdIARNMEswSQYMKwYBBAGVEgECAgECMDkwNwYIKwYBBQUHAgEWK2h0dHA6
Ly9ldXJvcGtpLmlhaWsuYXQvY2EvaW50cmFuZXQvY3BzLzEuMi8wHQYDVR0OBBYEFDcFtRTPbZ3w
yhc99asBh8o8j3a1MFEGA1UdHwRKMEgwRqBEoEKGQGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2Ev
aW50cmFuZXQvY3JsLzIwMDIvaWFpa19ldXJvcGtpX3NpZy5jcmwwRwYIKwYBBQUHAQEEOzA5MDcG
CCsGAQUFBzABhitodHRwOi8vb2NzcC5ldXJvcGtpLmlhaWsuYXQvT0NTUD90eXBlPWVtYWlsMB8G
A1UdIwQYMBaAFHi1VaEzvYMlf+rz54y3o5+Vc6p7MCQGA1UdEQQdMBuBGXBldGVyLmxpcHBAaWFp
ay50dWdyYXouYXQwDQYJKoZIhvcNAQEFBQADggEBAFYQ2pmxirCGc/c2EwQmGTR28RzUlXGDw6E/
cgMnYUzANv/G+qBvThPy4lm1obamynjecvg5ImOK+MaSO6oxxocu6Iz44Pmiazdfry5L7StEsyvr
g/TchBMij6NqjYbbf7Fg3ptcheP8jDecuSUWy11n/4v4oduGxDbVYBPPEJ/+9epdZCRPSDqla5S8
Sv4KiqaHwqTx0Qud6uxGqzVs58aNzJtEzJFXmcGT3n/uzog3b40/ALFVkN86Dy1EmZgcZjZkGI7W
WKNAP/AXMSNmJTqW9pM1OePpyyZOwD2y9JlEIfIG5HKdWEAEPHuUCL/IOFbKRPZQgAJAfQhCvNsU
xjkwggUtMIIEFaADAgECAgID6zANBgkqhkiG9w0BAQUFADCBxzELMAkGA1UEBhMCQVQxJjAkBgNV
BAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9y
IEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxITAfBgNV
BAsTGElBSUsgRXVyb1BLSSBJTlRSQU5FVCBDQTEjMCEGA1UEAxMaSUFJSyBFdXJvUEtJIFRVLUdS
QVogQ1JZUFQwHhcNMDcwNDI1MDk1MzE3WhcNMDgwNDI0MDk1MzE3WjCB7jEOMAwGA1UEKhMFUGV0
ZXIxDTALBgNVBAQTBExpcHAxEzARBgNVBAMTClBldGVyIExpcHAxJjAkBgNVBAoTHUdyYXogVW5p
dmVyc2l0eSBvZiBUZWNobm9sb2d5MUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5m
b3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxGTAXBgNVBAkTEEluZmZlbGRn
YXNzZSAxNmExDTALBgNVBAcTBEdyYXoxDzANBgNVBAgTBlN0eXJpYTELMAkGA1UEBhMCQVQwgZ8w
DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOETtJ4MyeJuY5x7sBGAcaX0yPW53dEiLlZjs7YU5L50
N1UE0fur9HLesnVn9qJwB8Kc8yYPAfwJajJAOs/wYONxOtuB8OkQjlo3oBgCCCth30DVPvNuBGvF
1hdX7LN2Kjf+NJhtkdV1jqqEco3DHA3v/O7qsnCIdQ+786Dajgq1AgMBAAGjggF8MIIBeDAOBgNV
HQ8BAf8EBAMCBDAwDAYDVR0TAQH/BAIwADBUBgNVHSAETTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcG
CCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2Nwcy8xLjIvMB0G
A1UdDgQWBBSnqZ3lNDpsvPvZigTAaOgoWCRJijBTBgNVHR8ETDBKMEigRqBEhkJodHRwOi8vZXVy
b3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2NybC8yMDAyL2lhaWtfZXVyb3BraV9jcnlwdC5jcmww
RwYIKwYBBQUHAQEEOzA5MDcGCCsGAQUFBzABhitodHRwOi8vb2NzcC5ldXJvcGtpLmlhaWsuYXQv
T0NTUD90eXBlPWNyeXB0MB8GA1UdIwQYMBaAFJopGdYXnsFR38xng6G35L8PuEMdMCQGA1UdEQQd
MBuBGXBldGVyLmxpcHBAaWFpay50dWdyYXouYXQwDQYJKoZIhvcNAQEFBQADggEBAHdMfxlM9HHu
5RDA+DeFF6OmAV5JN6gvkhmYfCxaN6/wqr3mlSq00u/Sk410h9/IaZd3PntRuYwq88LIF2y+xmwK
qeDSurvXnHR821sigd8x9zXpog8o/+0bl5N6jkTUBGg0vzs/zwkZo/VEaWw45tKxn6r+Xw2wsxEo
AQXcefjBGYZN0ZbDtBThU6pBXnPr28jTgIwmefV3oqoglRRpbEzs8/B7jpVcuSEi/OM1+dy9FWyq
LLpyZpGNj013gwCCAfMseZPvacCTTedZ8ZxB7rHGCAZAIw3DbSRtvycUhvaW2qzzIW21Z8mNCQm+
nVXEdPECWItViECDKuKYLyLnAmAwggUwMIIEGKADAgECAhR4tVWhM72DJX/q8+eMt6SRwlgmbzAN
BgkqhkiG9w0BAQUFADCBzDELMAkGA1UEBhMCQVQxDTALBgNVBAcTBEdyYXoxGTAXBgNVBAkTEElu
ZmZlbGRnYXNzZSAxNmExJjAkBgNVBAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgw
RgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQg
Q29tbXVuaWNhdGlvbnMxITAfBgNVBAMTGElBSUsgRXVyb1BLSSBJbnRyYW5ldCBDQTAeFw0wMjEy
MTcxNDI3NDFaFw0wODEyMzAyMjU5MzBaMIHFMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBV
TklWRVJTSVRZIE9GIFRFQ0hOT0xPR1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJ
bmZvcm1hdGlvbiBQcm9jZXNzaW5nIGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBF
dXJvUEtJIElOVFJBTkVUIENBMSEwHwYDVQQDExhJQUlLIEV1cm9QS0kgVFUtR1JBWiBTSUcwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDxWjtQORZimthvkSAAJlIL97tgPeJ8+151iGCy
d44WFAyjHsP9oQrZHxazVAB+o8clYdPpp/ECognU41o40iafdgkNIfsjyFMm3VvcWNx+F4vKYTHo
LQascxRJUULgub+B4k4pb9A4URQnxkrMriQlISoFXeEY1l2Mv4DlXHF3qOEMiLW5B1vmZZaEpNvH
/me8fuvJYLi9FWA+Ojk/UybbrGybkeJY3RAq+FImnWkaB9BAoAhdROR+GXU8YvqZTzqUndKog1Kc
cBKaFTBKwSz9RxOVPFORs1VLGItlnGRCn25uOiDTDfrU2D4D9cyFEVU+Qd55RzD6PfgP8BbeUyTx
AgMBAAGjggENMIIBCTASBgNVHRMBAf8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBxjAfBgNVHSME
GDAWgBSEWAP+T9cNWn701+2abEq0uxAz0jBUBgNVHSAETTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcG
CCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0L2NhL2ludHJhbmV0L2Nwcy8xLjIvME0G
A1UdHwRGMEQwQqBAoD6GPGh0dHA6Ly9ldXJvcGtpLmlhaWsuYXQvY2EvaW50cmFuZXQvY3JsLzIw
MDIvaWFpa19ldXJvcGtpLmNybDAdBgNVHQ4EFgQUeLVVoTO9gyV/6vPnjLejn5VzqnswDQYJKoZI
hvcNAQEFBQADggEBAKzKGUR++U1HNASLU47Wje4xIFPusnfd+hWKUR4bol+MtE0zEaAjyrnlgR3r
Hv0S0xnsQKIZMlt9ujiZi/lSzMelr7BDlfoHvV60W85uHROs2wAsSBw20oX2cnxbfZqHQzl2RCcd
1pZKYAu3NExcbJzz9ByjPbxszgBq3qfzywl/+hghd5sDVSr43H3BJ7yrjTiVyHNSVV4g3sz8wQlL
o2Ij/y/hLx2ZQwzXjVZIwL/9Mor2pMl08uD9f+ZSJKXLbWelSorTSD2Xbw3r8vTk1Opy5tnhP5Q7
751azOVvcfiP7Vwz7PdsxoTHrgloUXtdOeRk5XsfEFZnYJQyS9fYDl4wggUzMIIEG6ADAgECAhUA
mikZ1heewVHfzGeDobflsTyT48IwDQYJKoZIhvcNAQEFBQAwgcwxCzAJBgNVBAYTAkFUMQ0wCwYD
VQQHEwRHcmF6MRkwFwYDVQQJExBJbmZmZWxkZ2Fzc2UgMTZhMSYwJAYDVQQKEx1HUkFaIFVOSVZF
UlNJVFkgT0YgVEVDSE5PTE9HWTFIMEYGA1UECxM/SW5zdGl0dXRlIGZvciBBcHBsaWVkIEluZm9y
bWF0aW9uIFByb2Nlc3NpbmcgYW5kIENvbW11bmljYXRpb25zMSEwHwYDVQQDExhJQUlLIEV1cm9Q
S0kgSW50cmFuZXQgQ0EwHhcNMDIxMjE3MTQxODAyWhcNMDgxMjMwMjI1OTMwWjCBxzELMAkGA1UE
BhMCQVQxJjAkBgNVBAoTHUdSQVogVU5JVkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9J
bnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5mb3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNh
dGlvbnMxITAfBgNVBAsTGElBSUsgRXVyb1BLSSBJTlRSQU5FVCBDQTEjMCEGA1UEAxMaSUFJSyBF
dXJvUEtJIFRVLUdSQVogQ1JZUFQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDWIkt2
4ac2iD1RZW0BzsolEcM7k6C5Pb8EHxVojWsjJsscBB32XS9H2h2/XmjVOLtCPoNiEaqm8WrqFky2
9IdoktkLdV6bvW4gN32k17mvPUNCPmqO78idaqXCm//ocXRMwUHpMCv1NN+5KUMJ18BDchltI/Zj
1btYA7cZy4Ax01k6Z2zHUJkoAc7/+x95o8Cm/1D9JxxZ5o6tHdiAYgyUjCA6Q3L0DmNQgLPOMWU5
ZfcANDWfMTAH71c3oRJaKIum3yCKzThyX24X7iSU/SI1mA2uJnOerEweuLNhmu5kJzH+079B2Jys
cr921fzcz6KEEjEoEtnF8VSUvhFWxb2bAgMBAAGjggENMIIBCTASBgNVHRMBAf8ECDAGAQH/AgEA
MA4GA1UdDwEB/wQEAwIBxjAfBgNVHSMEGDAWgBSEWAP+T9cNWn701+2abEq0uxAz0jBUBgNVHSAE
TTBLMEkGDCsGAQQBlRIBAgIBAjA5MDcGCCsGAQUFBwIBFitodHRwOi8vZXVyb3BraS5pYWlrLmF0
L2NhL2ludHJhbmV0L2Nwcy8xLjIvME0GA1UdHwRGMEQwQqBAoD6GPGh0dHA6Ly9ldXJvcGtpLmlh
aWsuYXQvY2EvaW50cmFuZXQvY3JsLzIwMDIvaWFpa19ldXJvcGtpLmNybDAdBgNVHQ4EFgQUmikZ
1heewVHfzGeDobfkvw+4Qx0wDQYJKoZIhvcNAQEFBQADggEBAIgvmnj7ZJAOsLKiDtSRJ3S16HTW
j9JqjfXmy5S7EXRmw7SqeL7/rdXYgkhoXDF7mlEMvrTxIXBA75WCzUowfcVnC+T0EhDbfUq4NFh/
jQVpQEeRXE0EJXFDgtUmQuobFgeNe/KKzs2jcXEBgZMBZcxosxMPbfqPD7hFJxMghOe0id/HSZuL
iroFyoMefkfBABG12w2hQV5m8tnlva8s14/7rw5x8blsAnWsKA0yVzto3EikB3cVL+GslnrGM6R5
Ad/CY5iYKjPvD5w68OyCX6H/BxeAnEESoxwpHEXGDUNASZoQu5HPvCO/GNXs+CuXKrgo7UCg2ylE
luMawt9NmVgxggQDMIID/wIBATCBzDCBxTELMAkGA1UEBhMCQVQxJjAkBgNVBAoTHUdSQVogVU5J
VkVSU0lUWSBPRiBURUNITk9MT0dZMUgwRgYDVQQLEz9JbnN0aXR1dGUgZm9yIEFwcGxpZWQgSW5m
b3JtYXRpb24gUHJvY2Vzc2luZyBhbmQgQ29tbXVuaWNhdGlvbnMxITAfBgNVBAsTGElBSUsgRXVy
b1BLSSBJTlRSQU5FVCBDQTEhMB8GA1UEAxMYSUFJSyBFdXJvUEtJIFRVLUdSQVogU0lHAgID6jAJ
BgUrDgMCGgUAoIICjDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0w
NzA2MTEyMTIyNTdaMCMGCSqGSIb3DQEJBDEWBBSCLR+jAo4KravLRDw44VZGXh2djzBnBgkqhkiG
9w0BCQ8xWjBYMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCB3wYJKwYBBAGCNxAEMYHR
MIHOMIHHMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZIE9GIFRFQ0hOT0xP
R1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNzaW5n
IGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBFdXJvUEtJIElOVFJBTkVUIENBMSMw
IQYDVQQDExpJQUlLIEV1cm9QS0kgVFUtR1JBWiBDUllQVAICA+swgeEGCyqGSIb3DQEJEAILMYHR
oIHOMIHHMQswCQYDVQQGEwJBVDEmMCQGA1UEChMdR1JBWiBVTklWRVJTSVRZIE9GIFRFQ0hOT0xP
R1kxSDBGBgNVBAsTP0luc3RpdHV0ZSBmb3IgQXBwbGllZCBJbmZvcm1hdGlvbiBQcm9jZXNzaW5n
IGFuZCBDb21tdW5pY2F0aW9uczEhMB8GA1UECxMYSUFJSyBFdXJvUEtJIElOVFJBTkVUIENBMSMw
IQYDVQQDExpJQUlLIEV1cm9QS0kgVFUtR1JBWiBDUllQVAICA+swDQYJKoZIhvcNAQEBBQAEgYA0
UuerauIt7bsgz/etFUUl8FOs7qNTyykRuEw2h7WOYlup3f0blrNIGwm5iOY+YrvrSkS7+jyLQP/2
gQ72iYNnyvfsfK79jhTluRWcRGt1mFyk1EXaNqWyjVlbKsZsckH0gf984b1xgYdernSfUKUNKQZK
t3HYjOarwzkXQEcSYQAAAAAAAA==

------=_NextPart_000_0349_01C7AC7F.72128970--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BJgLAu027460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 12:42:21 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BJgL8g027459; Mon, 11 Jun 2007 12:42:21 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BJgKPb027453 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 12:42:20 -0700 (MST) (envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8]) by stingray.missi.ncsc.mil with SMTP id l5BJgJB8002707 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 15:42:19 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 11 Jun 2007 15:42:19 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Jun 2007 15:42:19 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 15:42:18 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C77FD@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIgAAI1XmA=
References: <20070611161139.GA27557@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 19:42:19.0394 (UTC) FILETIME=[9F5E3E20:01C7AC60]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15232000
X-TM-AS-Result: : Yes--3.370900-0-4-1
X-TM-AS-Category-Info: : 4:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE4LTE1MDU2Ny03MDIy?= =?us-ascii?B?NDgtNzAxNDU1LTcwNDQyNS03MDIxMTMtNzA0MTcxLTcwMjc0Ny03?= =?us-ascii?B?MDIzNDItNzAyMDYxLTcwMjA0NC03MDIzNTgtMTA2NjQwLTcwMDAw?= =?us-ascii?B?OS03MDM0NjgtNzAyODk4LTcwMjU5OC03MDQ3MTItNzAxNDI2LTcw?= =?us-ascii?B?MTA2NS03MDAzMjQtMTM5MDA2LTcwNDI4Ny03MDM4MjktNzAyOTU3?= =?us-ascii?B?LTcwNjc5MS03MTA0NDItNzAwNzU2LTExMDQ2Mi0xMDUwNDAtNzAy?= =?us-ascii?B?ODAxLTcwMTU3Ni03MDA2NjEtNzAyNDg1LTEzOTcwNC03MDgxOTYt?= =?us-ascii?B?NzA0MTg5LTcwMDA3My03MTEyMDctNzAwNDcyLTcwMTU5MC03MDU1?= =?us-ascii?B?MjYtMTQ4MDUw?=
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BJgKPb027454
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>

In order to achieve backwards compatibility with a billion browsers,
you would have to mark any new extension as non-critical, where it
would be ignored by every single browser currently in existence.

Therefore users would be told that their communication is secure while
issuing practices permit (no, positively encourage, once the word
on this extension gets out) web site spoofing.

If you want to use Peter's OID for this, no one can stop you.  But
the PKIX WG can refuse to assign an OID whose ostensible purpose is
to enable non-advertised encryption but whose actual effect on current
browsers would be to advertise secure communications while using
null-assurance certificates.




-----Original Message-----
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org]
On Behalf Of Hallam-Baker, Phillip

These are not anonymous communications, they are merely communications
that do not require the level of assurance that is necessary to alert
the user to tell tham that the communication is secure.
 
> > The reason for using a certificate is to allow for backwards 
> > compatibility with a billion installed browsers. 


-----------

P.S., the difference between anonymous communications and
communications for which the participants can claim any desired
name (e.g. my webserver operating as https://www.verisign.com)
and into which third parties (e.g. hotel wireless APs) may
insert themselves eludes me. One definition of anonymous is
"unnamed", but the second definition is "of unknown origin".
Spoofed names certainly seem to fit the second definition.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BHkl5Q091393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 10:46:47 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BHklRP091390; Mon, 11 Jun 2007 10:46:47 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BHkkqx091368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 10:46:47 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5BHkeG7002382; Mon, 11 Jun 2007 10:46:42 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 10:46:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 10:45:29 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A628C@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <20070611161139.GA27557@localhost.localdomain>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcesS6iSbuLiO+ZXTq++eISs8rCQuQABEiIg
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Thomas Pornin" <pornin@bolet.org>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 17:46:40.0382 (UTC) FILETIME=[776509E0:01C7AC50]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BHklqw091377
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>

The TLS features are irrelevant.

The information to be encoded here relates to the issue practices of the certificate. Therefore they go into the certificate.

These are not anonymous communications, they are merely communications that do not require the level of assurance that is necessary to alert the user to tell tham that the communication is secure.

 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Thomas Pornin
> Sent: Monday, June 11, 2007 12:12 PM
> To: ietf-pkix@imc.org
> Subject: Re: Three short fixes
> 
> 
> On Mon, Jun 11, 2007 at 07:23:56AM -0700, Hallam-Baker, Phillip wrote:
> > I don't see why I should appologize for a fix for being 
> 'centered' on 
> > the only X.509 prototocol that can be regarded as a real success.
> 
> This is a technical debate on a technical mailing-list. This 
> is not a trial and there is nothing to apologize about yet.
> 
> 
> > The reason for using a certificate is to allow for backwards 
> > compatibility with a billion installed browsers. The 
> dilution of trust 
> > is inevitable, all it takes to get a WebTrust audit is to 
> do what you 
> > say. Eventually someone is going to get a WebTrust audit on 
> the null 
> > CPS.
> 
> For backward compatibility, SSL/TLS already has a beautiful 
> scheme which is called "cipher suite selection" and it works. 
> Basically, the client sends a message ("ClientHello") where 
> it states which cipher suites it supports, and then the 
> server selects one which it also supports. The cipher suite 
> defines how the session will be protected. For DH_anon cipher 
> suites, both client and server know that there is no X.509 
> certificate involved, only a public key.
> 
> Let's assume that we have a server which wishes to use 
> encryption but needs not any kind of authentication(*). This 
> server will be fine with a DH_anon suite. A client comes along:
> 
> -- Either this is a client which supports the concept of an 
> unauthenticated but encrypted session. That client then 
> implements DH_anon cipher suites, because that is exactly 
> what these suites are about, and they have been standard for 
> quite a long time. The client states that it supports DH_anon 
> suites, the server selects one, and the session is encrypted 
> but not authenticated. No X.509 certificate is involved here, 
> and, in particular, no X.509-related warning message is 
> displayed to the user.
> 
> -- Or the client does not support the concept of an 
> unauthenticated but encrypted session. This means that the 
> client does not support DH_anon cipher suites (because 
> DH_anon suites are meant for one thing and one thing only: 
> unauthenticated but encrypted session). The client will send 
> a ClientHello message which will not contain a DH_anon suite, 
> but other cipher suites which expect a X.509 certificate from 
> the server. The server sends a certificate which cannot be 
> authenticated by the client.
> The client displays a warning to the user, but we cannot do 
> better than that since the client does not support 
> unauthenticated sessions: this is the "backward 
> compatibility" situation.
> 
> 
> 
> What could be done here to makes things even better would be the
> following:
> 
> -- Make DH_anon suites more "supported" (newer TLS 
> specifications tell that DH_anon suites are obsolescent due 
> to the involved security issues(**)).
> 
> -- Define RSA_anon suites which should provide better 
> performance for computationaly challenged clients (RSA 
> encryption is cheap).
> 
> Both of these are issues for the IETF TLS mailing-list, not 
> the IETF PKIX mailing-list.
> 
> 
> To sum up, what you ask for _already exists_ in a better way 
> (less network traffic and less X.509 processing for the same 
> functionality).
> Unless what you want is something entirely different. You write:
> 
> > I want to be able to issue device SSL certs. People want to 
> buy them.
> 
> Of course, if you sell certificates, you will not like a 
> scheme where nobody uses certificates and, as such, nobody 
> buys certificates.
> 
> 
> 	--Thomas Pornin
> 
> 
> (*) Basically, unauthenticated but encrypted session are 
> useful only if the security model allows only passive 
> attacks. This is rarely a valid assumptions, but this is not 
> the issue in this discussion. We assume here that there are 
> plausible situations where unauthenticated but encrypted 
> sessions are what is needed.
> 
> (**) People involved in the definition of TLS do not believe 
> in the existence of plausible situations where 
> unauthenticated but encrypted sessions are what is needed. 
> This is why DH_anon suites are currently deprecated. But the 
> same people, and, more importantly from your point of view, 
> the TLS implementors will think just the same about any way 
> to get unauthenticated but encryted sessions, whether by 
> using the TLS features which have been designed for exactly 
> that usage (DH_anon), or by any X.509-related trickery such 
> as your fake certificates. So this is not an issue in this debate.
> 
> 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BGBgex063170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 09:11:42 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BGBgHM063169; Mon, 11 Jun 2007 09:11:42 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BGBeJc063145 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 09:11:41 -0700 (MST) (envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000) id 29FCFD98637; Mon, 11 Jun 2007 18:11:39 +0200 (CEST)
Date: Mon, 11 Jun 2007 18:11:39 +0200
From: Thomas Pornin <pornin@bolet.org>
To: ietf-pkix@imc.org
Subject: Re: Three short fixes
Message-ID: <20070611161139.GA27557@localhost.localdomain>
References: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz> <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.5.11
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>

On Mon, Jun 11, 2007 at 07:23:56AM -0700, Hallam-Baker, Phillip wrote:
> I don't see why I should appologize for a fix for being 'centered' on
> the only X.509 prototocol that can be regarded as a real success. 

This is a technical debate on a technical mailing-list. This is not a
trial and there is nothing to apologize about yet.


> The reason for using a certificate is to allow for backwards
> compatibility with a billion installed browsers. The dilution of trust
> is inevitable, all it takes to get a WebTrust audit is to do what you
> say. Eventually someone is going to get a WebTrust audit on the null
> CPS.

For backward compatibility, SSL/TLS already has a beautiful scheme which
is called "cipher suite selection" and it works. Basically, the client
sends a message ("ClientHello") where it states which cipher suites it
supports, and then the server selects one which it also supports. The
cipher suite defines how the session will be protected. For DH_anon
cipher suites, both client and server know that there is no X.509
certificate involved, only a public key.

Let's assume that we have a server which wishes to use encryption but
needs not any kind of authentication(*). This server will be fine with
a DH_anon suite. A client comes along:

-- Either this is a client which supports the concept of an
unauthenticated but encrypted session. That client then implements
DH_anon cipher suites, because that is exactly what these suites are
about, and they have been standard for quite a long time. The client
states that it supports DH_anon suites, the server selects one, and the
session is encrypted but not authenticated. No X.509 certificate is
involved here, and, in particular, no X.509-related warning message is
displayed to the user.

-- Or the client does not support the concept of an unauthenticated but
encrypted session. This means that the client does not support DH_anon
cipher suites (because DH_anon suites are meant for one thing and one
thing only: unauthenticated but encrypted session). The client will send
a ClientHello message which will not contain a DH_anon suite, but other
cipher suites which expect a X.509 certificate from the server. The
server sends a certificate which cannot be authenticated by the client.
The client displays a warning to the user, but we cannot do better than
that since the client does not support unauthenticated sessions: this is
the "backward compatibility" situation.



What could be done here to makes things even better would be the
following:

-- Make DH_anon suites more "supported" (newer TLS specifications tell
that DH_anon suites are obsolescent due to the involved security
issues(**)).

-- Define RSA_anon suites which should provide better performance for
computationaly challenged clients (RSA encryption is cheap).

Both of these are issues for the IETF TLS mailing-list, not the IETF PKIX
mailing-list.


To sum up, what you ask for _already exists_ in a better way (less
network traffic and less X.509 processing for the same functionality).
Unless what you want is something entirely different. You write:

> I want to be able to issue device SSL certs. People want to buy them.

Of course, if you sell certificates, you will not like a scheme where
nobody uses certificates and, as such, nobody buys certificates.


	--Thomas Pornin


(*) Basically, unauthenticated but encrypted session are useful only if
the security model allows only passive attacks. This is rarely a valid
assumptions, but this is not the issue in this discussion. We assume
here that there are plausible situations where unauthenticated but
encrypted sessions are what is needed.

(**) People involved in the definition of TLS do not believe in the
existence of plausible situations where unauthenticated but encrypted
sessions are what is needed. This is why DH_anon suites are currently
deprecated. But the same people, and, more importantly from your point
of view, the TLS implementors will think just the same about any way to
get unauthenticated but encryted sessions, whether by using the TLS
features which have been designed for exactly that usage (DH_anon), or
by any X.509-related trickery such as your fake certificates. So this is
not an issue in this debate.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BG6Qq3061901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 09:06:26 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BG6QQh061900; Mon, 11 Jun 2007 09:06:26 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BG6OTr061894 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 09:06:25 -0700 (MST) (envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8]) by stingray.missi.ncsc.mil with SMTP id l5BG6NRg020853 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 12:06:24 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 11 Jun 2007 12:06:23 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959); Mon, 11 Jun 2007 12:06:23 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 12:06:22 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C764E@EXCH.missi.ncsc.mil>
In-Reply-To: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Aceo5PYyGdvxM0iuT9S2MjuukyYxMwDVcyzQ
References: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com> <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 16:06:23.0738 (UTC) FILETIME=[753205A0:01C7AC42]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15232000
X-TM-AS-Result: : Yes--6.444900-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE4LTE1MDU2Ny03MDU5?= =?us-ascii?B?MDEtNzAzMzU1LTcwNjc5MS03MDc1NTMtNzAyMTA2LTcwMTU3Ni03?= =?us-ascii?B?MDA2MTgtNzA2ODE3LTcwOTU4NC03MDA2NjEtNzAzMDg4LTcwNTM3?= =?us-ascii?B?NC03MDEwMDEtNzA3MTYzLTcwMTYxOC03MDY0NTQtMTE0NTQ3LTcw?= =?us-ascii?B?MTkyOC03MDQ5OTQtNzAyMDQ0LTcwMjkyMC0xMDY2NjAtNzAyMTEz?= =?us-ascii?B?LTcwMDMyNC03MDAxMDQtNzA0NzEyLTcwMDc3MS03MDU4NjEtNzA4?= =?us-ascii?B?NjU1LTcwMjk1Ny0xMzkwMDYtNzAwMjE1LTcwMTE3NS03MDQxODkt?= =?us-ascii?B?NzAwMDczLTcwMjYyNi03MDM3MzEtMTM5MDEwLTEwNTcwMC0xMDUw?= =?us-ascii?B?NDAtNzAzMzY2LTE0ODA1MA==?=
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BG6PTr061895
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>

More to the point, the intent is to create an attribute that says:

  "This certificate is merely a convenient universally-accepted
   blob for communicating a public key and a name/email address/URL"
*AND*
  "There is no claim that the public key and the name/email/URL
   have any relationship whatsoever"

In other words, the name/email/URL could belong to Bank of America
but the key pair and certificate request could have been created by
Phish-R-Us, and no claims to the contrary are made by the issuer.
Unfortunately, the mere existence of a certificate implies such
a claim even if it is disclaimed by an extension.

Saying "CAs want to sell no-claim certificates and server operators
want to buy them" ignores the societal cost of issuing certificates
that can be used to promote phishing.

If the extension MUST be marked critical, and if the certificate
MUST be rejected if subject name is non-null, and if the certificate
MUST be rejected if any other extension (including SAN) is present,
then perhaps there is less danger that current TLS applications
would be misled by the existence of such certificates.  But the
safer approach is to not issue them in the first place, particularly
since alternatives (anonymous ciphersuites) already exist.



-----Original Message-----
From: pgut001 [mailto:pgut001@cs.auckland.ac.nz] 
Sent: Thursday, June 07, 2007 5:20 AM
To: Kemp, David P.; ietf-pkix@imc.org; pbaker@verisign.com
Subject: RE: Three short fixes

"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>The point here is precisely to allow a certificate to state 'there are
no
>security claims being made here'.

So is the intent to create an attribute that says "This certificate is
merely
a convenient universally-accepted blob for communicating a public key
and a
name/email address/URL"?  In other words it's not really TLS-specific?

Peter.





Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BFjGDu057091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 08:45:16 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BFjGPR057090; Mon, 11 Jun 2007 08:45:16 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (moe.its.auckland.ac.nz [130.216.12.35]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BFjEQK057081 for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 08:45:15 -0700 (MST) (envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 222304801BD; Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1]) by localhost (moe.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IO5kz+3YIxn5; Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 081DD4801B0; Tue, 12 Jun 2007 03:45:14 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33]) by iris.cs.auckland.ac.nz (Postfix) with ESMTP id E3AD61280A1; Tue, 12 Jun 2007 03:45:12 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian)) id 1Hxm54-00085O-00; Tue, 12 Jun 2007 03:45:22 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org, pbaker@verisign.com, pgut001@cs.auckland.ac.nz
Subject: RE: Three short fixes
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Message-Id: <E1Hxm54-00085O-00@medusa01.cs.auckland.ac.nz>
Date: Tue, 12 Jun 2007 03:45:22 +1200
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>

"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>I don't see why I should appologize for a fix for being 'centered' on the
>only X.509 prototocol that can be regarded as a real success.

Uhh... who was that intended for?  It doesn't seem to be a response to my
message that you've quoted.

>'This cert makes no security claims that are worth display to an end user'.

As it turns out I've already got an OID out there for just such an extension,
which I added after constant user requests (that is, they didn't specifically
ask for this, but said that all they needed from a cert was a universally-
recognised bit bag for public keys, and they needed some way to tag it so that
relying parties could tell that it was just a no-semantics-attached bit bag).
So if Verisign needs a vendor-neutral OID, you can use mine, assuming that's
what you want (you didn't really answer my question below).

> So is the intent to create an attribute that says "This
> certificate is merely a convenient universally-accepted blob
> for communicating a public key and a name/email address/URL"?

In response to that I got several private-mail comments saying things like
"That's the default action for certificates isn't it?" and "How does this
differ from the current situation" :-).

Peter.



Received: from mail.natconcorp.com ([86.57.232.34]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BEdrrt047819; Mon, 11 Jun 2007 07:39:54 -0700 (MST) (envelope-from vomnatalsdiw@natals.us)
Received: from 216.180.233.175 (HELO mail.natals.us) by imc.org with esmtp (:IQ0N-X,84 )N9B/) id 9C//8P-JN4@;6-0) for ietf-whois@imc.org; Mon, 11 Jun 2007 14:39:56 -0200
Date: 	Mon, 11 Jun 2007 14:39:56 -0200
From: "Ericka Ashley" <vomnatalsdiw@natals.us>
X-Mailer: The Bat! (v3.80.06) Educational
X-Priority: 3 (Normal)
Message-ID: <807142267.89654621899450@thhebat.net>
To: ietf-whois@imc.org
Subject: Don't get left behind
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------EBF6E4BF6E44B8"
X-Spam: Not detected

------------EBF6E4BF6E44B8
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Ultimately the original thing =96 no more trickery! 
P.E.P. are piping hot at the time! Well here comes the true stuff not a=20=
fictitious one! 

One of the very exceptionals, absolutely unrivalled produce is easy=20=
accessible all over the world!
 Take note of what people tell on this product:

"I was really impressed how quick your product affected on my=20=
boyfriend, he can not stop chatting on how hot he is having his new=20=
calibre, extent, and libido!"

Linda F., New York

"In the beginning I decided the sample parcel I received gratis was a=20=
prank, till I have taken to take the P.E.P. There are no words to=20=
describe how plume I am with the effects I achieved from using this patch=20=
after 6 brief weeks. I will be ordering regularly!" 
Charley Mock, Chicago

Look at more testimonials on this wonderful product right here and=20=
right now!
http://www.relhee.hk/?asnrneafivq

------------EBF6E4BF6E44B8
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Don't be the "little guy" in the club</TITLE>
</HEAD>
<BODY>

<b>
Ultimately the original thing =96 no more trickery! 
<br>
<a href=3D"http://www.relhee.hk/?asnrneafivq">P.E.P.</a> are piping hot=20=
at the time! Well here comes the true stuff not a fictitious one! 
<br>
One of the very exceptionals, absolutely unrivalled produce is easy=20=
accessible all over the world!
<br> Take note of what people tell on this product:
<p>
<i>
"I was really impressed how quick your product affected on my=20=
boyfriend, he can not stop chatting on how hot he is having his new=20=
calibre, extent, and libido!"
</i>
</p>
Linda F., New York
<p>
<i>
"In the beginning I decided the sample parcel I received gratis was a=20=
prank, till I have taken to take the P.E.P. There are no words to=20=
describe how plume I am with the effects I achieved from using this patch=20=
after 6 brief weeks. I will be ordering regularly!" </i>
</p>
Charley Mock, Chicago
<center>
<a href=3D"http://www.relhee.hk/?asnrneafivq">
Look at more testimonials on this wonderful product right here and=20=
right now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.relhee.hk/?asnrneafivq</font>

</BODY></HTML>
------------EBF6E4BF6E44B8--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BEPMBw046128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Jun 2007 07:25:22 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5BEPMer046127; Mon, 11 Jun 2007 07:25:22 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5BEPJdb046119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 11 Jun 2007 07:25:19 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l5BEPA2w014529; Mon, 11 Jun 2007 07:25:11 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 11 Jun 2007 07:25:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Mon, 11 Jun 2007 07:23:56 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6228@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Aceo5PPkQ+niKfZUQ36auwffVIOhhwDTeP5w
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "pgut001" <pgut001@cs.auckland.ac.nz>, <DPKemp@missi.ncsc.mil>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 11 Jun 2007 14:25:10.0456 (UTC) FILETIME=[513CBB80:01C7AC34]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l5BEPJda046120
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>

I don't see why I should appologize for a fix for being 'centered' on the only X.509 prototocol that can be regarded as a real success. 

The reason for using a certificate is to allow for backwards compatibility with a billion installed browsers. The dilution of trust is inevitable, all it takes to get a WebTrust audit is to do what you say. Eventually someone is going to get a WebTrust audit on the null CPS.


I want to be able to issue device SSL certs. People want to buy them. All that I want to do here is to make sure that they can be distinguished from certs people are using to take credit cards.

I can give you a cast iron chain for an EUI48 MAC address. But it says nothing that should give an end user warm fuzzies.


'This cert makes no security claims that are worth display to an end user'.

> -----Original Message-----
> From: pgut001 [mailto:pgut001@cs.auckland.ac.nz] 
> Sent: Thursday, June 07, 2007 5:20 AM
> To: DPKemp@missi.ncsc.mil; ietf-pkix@imc.org; Hallam-Baker, Phillip
> Subject: RE: Three short fixes
> 
> "Hallam-Baker, Phillip" <pbaker@verisign.com> writes:
> 
> >The point here is precisely to allow a certificate to state 
> 'there are 
> >no security claims being made here'.
> 
> So is the intent to create an attribute that says "This 
> certificate is merely a convenient universally-accepted blob 
> for communicating a public key and a name/email address/URL"? 
>  In other words it's not really TLS-specific?
> 
> Peter.
> 
> 
> 



Received: from nat-b2-121.tsi.tychy.pl (nat-b2-121.tsi.tychy.pl [83.142.122.121]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5AKSXYh056813; Sun, 10 Jun 2007 13:28:35 -0700 (MST) (envelope-from figmusicsquadnur@musicsquad.com)
Received: from 69.5.81.49 (HELO Eta.sitelutions.com) by imc.org with esmtp (076804)0;G4Q -88S0) id ?GWP+M-(.9(U6-(. for ietf-sasl-request@imc.org; Sun, 10 Jun 2007 20:28:41 -0100
Date: 	Sun, 10 Jun 2007 20:28:41 -0100
From: "Sondra Jean" <figmusicsquadnur@musicsquad.com>
X-Mailer: The Bat! (v2.00.8) Business
X-Priority: 3 (Normal)
Message-ID: <575123984.81776905939126@thhebat.net>
To: ietf-sasl-request@imc.org
Subject: Make her worship you
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------94DAC67394DA50"
X-Spam: Not detected

------------94DAC67394DA50
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable


Ultimately the true stuff =96 no more trickery! 
P.E.P. are piping hot at the time! Well this is the true stuff not a=20=
forgery! 

One of the very originals, totally unequalled product is accessible=20=
everywhere!
 Pay attention to just what people tell on this produce:

"I was impressed how fast your product worked on my boyfriend, he can=20=
no way stop babbling about how excited he is having his new girth,=20=
length, and libido!"

Lusia R., Boston

"At the beginning I decided the free sample package I got was a nasty=20=
trick, till I have taken taking the P.E.P. I can not describe depict how=20=
pleased I am with the consequences I achieved from using the patch after=20=
2 brief months. I will be asking for P.E.P. constantly!" 
Mike Brown, Chicago

Read more recommendations on this wonderful product right here and=20=
right now!
http://www.vapor.hk/?dkapmulxybc
------------94DAC67394DA50
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Hey man, stop throwing away your money</TITLE>
</HEAD>
<BODY>

<b>
Ultimately the true stuff =96 no more trickery! 
<br>
<a href=3D"http://www.vapor.hk/?dkapmulxybc">P.E.P.</a> are piping hot=20=
at the time! Well this is the true stuff not a forgery! 
<br>
One of the very originals, totally unequalled product is accessible=20=
everywhere!
<br> Pay attention to just what people tell on this produce:
<p>
<i>
"I was impressed how fast your product worked on my boyfriend, he can=20=
no way stop babbling about how excited he is having his new girth,=20=
length, and libido!"
</i>
</p>
Lusia R., Boston
<p>
<i>
"At the beginning I decided the free sample package I got was a nasty=20=
trick, till I have taken taking the P.E.P. I can not describe depict how=20=
pleased I am with the consequences I achieved from using the patch after=20=
2 brief months. I will be asking for P.E.P. constantly!" </i>
</p>
Mike Brown, Chicago
<center>
<a href=3D"http://www.vapor.hk/?dkapmulxybc">
Read more recommendations on this wonderful product right here and=20=
right now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.vapor.hk/?dkapmulxybc</font>

</BODY></HTML>
------------94DAC67394DA50--



Received: from 211.line.pl ([213.199.253.211]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5AJPTkd035165; Sun, 10 Jun 2007 12:25:41 -0700 (MST) (envelope-from cajmozejkomug@mozejko.com)
Received: from [213.199.253.211] by cust-mail1.buz.net; Sun, 10 Jun 2007 19:25:47 -0100
Date: 	Sun, 10 Jun 2007 19:25:47 -0100
From: "Scott Ziegler" <cajmozejkomug@mozejko.com>
X-Mailer: The Bat! (v2.00.18) Educational
Reply-To: cajmozejkomug@mozejko.com
X-Priority: 3 (Normal)
Message-ID: <276213479.23683825245074@mozejko.com>
To: ietf-openproxy-request@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------9D3712CF8B6EC8"

------------9D3712CF8B6EC8
Content-Type: text/plain; charset=windows-1250
Content-Transfer-Encoding: 7bit

LegalRXMedications chemist's shop offers all cures that you want in order to recover your health at little price. 
We operate around the planet with buyers from America, Europe and Asia. 
This time you got no need to look for drug shop somewhere at your area.
We can bring pills of the highest quality to the distant parts of the planet.
Visit our site & order pharmas that you immediately need direct to your residence. 
http://checkfruit.hk/ 
We are confirmed by VeriSign and VISA so then we support certain and confidential buying.

------------9D3712CF8B6EC8
Content-Type: text/html; charset=windows-1250
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> chemist's shop offers all cures that you want in order to recover your health at little price. <br>
We operate around the planet with buyers from America, Europe and Asia. <br>
This time you got no need to look for drug shop somewhere at your area.<br>
We can bring pills of the highest quality to the distant parts of the planet.
<br>
<br>
<a href="http://checkfruit.hk/"><em>Visit our site & order pharmas that you immediately need direct to your residence.</em></a></b> 
<br>
<font color="#D9EDFF">http://checkfruit.hk/</font> 
<br><b>We are confirmed by <font color="#FF0000"><em>VeriSign</em></font> and <font color="#FF0000"><em>VISA</em></font> so then we support certain and confidential buying.
</b>

</BODY></HTML>
------------9D3712CF8B6EC8--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5ADkpeE016564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 10 Jun 2007 06:46:51 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l5ADkpYv016563; Sun, 10 Jun 2007 06:46:51 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mx1.kent.ac.uk (mx1.kent.ac.uk [129.12.21.39]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5ADknnZ016548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-pkix@imc.org>; Sun, 10 Jun 2007 06:46:51 -0700 (MST) (envelope-from d.w.chadwick@kent.ac.uk)
Received: from c-24-8-221-135.hsd1.co.comcast.net ([24.8.221.135] helo=[10.1.10.120]) by mx1.kent.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62) (envelope-from <d.w.chadwick@kent.ac.uk>) id 1HxNkZ-0002Fy-6j for ietf-pkix@imc.org; Sun, 10 Jun 2007 14:46:35 +0100
Message-ID: <466C00B4.6070308@kent.ac.uk>
Date: Sun, 10 Jun 2007 14:46:28 +0100
From: David Chadwick <d.w.chadwick@kent.ac.uk>
Organization: University of Kent
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: PKIX <ietf-pkix@imc.org>
Subject: Use of WebDAV for X.509
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-UKC-Mail-System: No virus detected
X-UKC-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44)
X-UKC-MailScanner-From: d.w.chadwick@kent.ac.uk
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>

Dear WG

I have published a new ID at

http://www.ietf.org/internet-drafts/draft-chadwick-webdav-00.txt

This document describes the use of the WebDAV protocol for publishing
and revoking X.509 public key certificates and specifies two new access
methods for the Authority Information Access extension to support this.

WebDAV is an extension of HTTP, and allows certificates and CRLs to be 
published on Web servers such as Apache, rather than (or as well as) in 
LDAP servers, since we all know that LDAP servers are often not 
accessible on the Internet.

I should like the WG to consider including this work in its charter, and 
would appreciate comments on this draft either to me in person or to the 
PKIX list.

regards

David



*****************************************************************
David W. Chadwick, BSc PhD
Professor of Information Systems Security
The Computing Laboratory, University of Kent, Canterbury, CT2 7NF
Skype Name: davidwchadwick
Tel: +44 1227 82 3221
Fax +44 1227 762 811
Mobile: +44 77 96 44 7184
Email: D.W.Chadwick@kent.ac.uk
Home Page: http://www.cs.kent.ac.uk/people/staff/dwc8/index.html
Research Web site: http://www.cs.kent.ac.uk/research/groups/iss/index.html
Entrust key validation string: MLJ9-DU5T-HV8J
PGP Key ID is 0xBC238DE5

*****************************************************************



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l59FrPeA039073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 9 Jun 2007 08:53:25 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l59FrPn1039072; Sat, 9 Jun 2007 08:53:25 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp103.biz.mail.re2.yahoo.com (smtp103.biz.mail.re2.yahoo.com [68.142.229.217]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l59FrLGM039035 for <ietf-pkix@imc.org>; Sat, 9 Jun 2007 08:53:23 -0700 (MST) (envelope-from turners@ieca.com)
Received: (qmail 63898 invoked from network); 9 Jun 2007 15:53:12 -0000
Received: from unknown (HELO Wylie) (turners@ieca.com@70.108.2.7 with login) by smtp103.biz.mail.re2.yahoo.com with SMTP; 9 Jun 2007 15:53:12 -0000
X-YMail-OSG: aR1yhKAVM1lDi7YcZRk1MosD.MyDxNuY.Ca1cUjCmlr6qpCLBz5Km9lpD316TTOdAfwkGnteb78PVGnWUznZnB3TQJDxaOTfcKl8uYatvzCiLQzfmKs-
Reply-To: <turners@ieca.com>
From: "Turner, Sean P." <turners@ieca.com>
To: "'pkix'" <ietf-pkix@imc.org>
Subject: New mailing list and potential BOF: trust anchor management
Date: Sat, 9 Jun 2007 11:46:03 -0400
Organization: IECA, Inc.
Message-ID: <007201c7aaad$4918e1a0$0301a8c0@Wylie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceqrUi7psFA1IzaQFqxkMF3plxpSg==
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>

A mailing list has been established to discuss a standard protocol for trust
anchor management.  Numerous groups within the IETF (e.g., PKIX, SIDR, and
Kerberos) have all indicated a need for trust anchor management, but that it
is outside of their documents.

A BOF to discuss this has been proposed for IETF 69 in Chicago.

Subscription information for the ietf-trust-anchor mailing list can be found
at:
<http://www.vpnc.org/ietf-trust-anchor/>.

A description of the problem statement can be found at:
<http://www.ietf.org/internet-drafts/draft-wallace-ta-mgmt-problem-statement
-00.txt>.

spt 





Received: from Lizzy.bivapr.net ([216.24.245.114]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l58JTag6079938; Fri, 8 Jun 2007 12:29:39 -0700 (MST) (envelope-from budmegamermersow@megamermer.com)
Received: from 212.58.5.9 (HELO mail2.doruk.net.tr) by imc.org with esmtp (.0N>40O.95-7 00-1X) id 2V5;)D-3.69O7--6 for ietf-openproxy@imc.org; Fri, 8 Jun 2007 19:29:33 +0400
Date: 	Fri, 8 Jun 2007 19:29:33 +0400
From: "Rochelle Mcmahon" <budmegamermersow@megamermer.com>
X-Mailer: The Bat! (v2.00.8) Personal
X-Priority: 3 (Normal)
Message-ID: <322713275.72200204252914@thhebat.net>
To: ietf-openproxy@imc.org
Subject: Don't be inadequate anymore
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------D3EC8B67967125"
X-Spam: Not detected

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


Finally the real thing =96 no more money tricks! 
P.E.P. are piping hot at the time! This is the genuine stuff not a=20=
fictitious one! 

One of the very exceptionals, totally unequalled produce is easy=20=
accessible anywhere!
 Take note of what people say on this stuff:

"I pleased how quick your product worked on my boyfriend, he can no way=20=
stop chatting on how excited he is having such new size, extent, and=20=
libido!"

Victoria K., New York

"At the beginning I decided the gratuitous specimen parcel I was given=20=
was a jest, until I tried taking the P.E.P. There are no words to depict=20=
how plume I am with the consequence I achieved from using this remedy=20=
after 2 brief months. I will be requesting constantly!" 
Charley Mock, Boston

Read more testimonies on this astonishing product just now!
http://www.clate.hk/?ilujulgptog
------------D3EC8B67967125
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Be the "biggest" out of all your friends</TITLE>
</HEAD>
<BODY>

<b>
Finally the real thing =96 no more money tricks! 
<br>
<a href=3D"http://www.clate.hk/?ilujulgptog">P.E.P.</a> are piping hot=20=
at the time! This is the genuine stuff not a fictitious one! 
<br>
One of the very exceptionals, totally unequalled produce is easy=20=
accessible anywhere!
<br> Take note of what people say on this stuff:
<p>
<i>
"I pleased how quick your product worked on my boyfriend, he can no way=20=
stop chatting on how excited he is having such new size, extent, and=20=
libido!"
</i>
</p>
Victoria K., New York
<p>
<i>
"At the beginning I decided the gratuitous specimen parcel I was given=20=
was a jest, until I tried taking the P.E.P. There are no words to depict=20=
how plume I am with the consequence I achieved from using this remedy=20=
after 2 brief months. I will be requesting constantly!" </i>
</p>
Charley Mock, Boston
<center>
<a href=3D"http://www.clate.hk/?ilujulgptog">
Read more testimonies on this astonishing product just now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.clate.hk/?ilujulgptog</font>

</BODY></HTML>
------------D3EC8B67967125--



Received: from cpe-70-95-166-121.hawaii.res.rr.com (cpe-70-95-166-121.hawaii.res.rr.com [70.95.166.121]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l58EpC0a005137; Fri, 8 Jun 2007 07:51:16 -0700 (MST) (envelope-from budmediplantexsow@mediplantex.com)
Received: from 202.67.150.251 (HELO mail.mediplantex.com) by imc.org with esmtp (2)*P?27'3- .11-)) id TNFG8A-).9+1E-Q' for ietf-pkix-oid-reg@imc.org; Fri, 8 Jun 2007 14:51:16 +1000
Date: 	Fri, 8 Jun 2007 14:51:16 +1000
From: "Melanie Erickson" <budmediplantexsow@mediplantex.com>
X-Mailer: The Bat! (v3.81.14 Beta) Home
X-Priority: 3 (Normal)
Message-ID: <299083935.53653590525996@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: Melt away fat easily
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------053B4F21C72991"
X-Spam: Not detected

------------053B4F21C72991
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable


Profit by your opportunity! =96 Anatrim =96 The up-to-the-moment & most=20=
fascinating flesh loss product is now readily available =96 As were told=20=
on Oprah

Can you count up all the cases when you said to yourself you would do=20=
anything for being saved from this horrible pounds of fat? Fortunately,=20=
now no great price is to be paid. With Anatrim, the earth-shaking, you=20=
can get naturally health life style and become really slimmer. Have a=20=
look at what customers say to us!
 
=93I always had a stunning life till last year my girl told me I was=20=
corpulent and in need of being careful to my health. Life went the wrong=20=
way after that, until I discovered Anatrim =99. Since getting rid of more=20=
than 40 lbs only thanx to Anatrim,  my private life is back on track,=20=
considerably better than even before. Lots of thanx for the incredible=20=
product & the great maintenance service. Keep up your good action!=94

 
Rikky Martin, San Diego

 
"There=92s nothing better than slipping into a bikini that I have not=20=
been dressed in for a long time. I feel slim, determined, and healthy,=20=
thanx in great part to Anatrim! Great deal of thanks to you!"

 
Lusia R., Texas

Check out Anatrim, and  you'll join the worldwide company of thousands=20=
of delighted user who get pleasure in the revolutionary results of=20=
Anatrim just now. Less eating insanity, less lbs and more gaiety in life!

Proceed here to scan our invincible Anatrim deals!!!
http://www.clate.hk/?zdpnjxrcd

------------053B4F21C72991
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Getting thinner can be enjoyable</TITLE>
</HEAD>
<BODY>

<p>
<center>
<b>
<a href=3D"http://www.clate.hk/?zdpnjxrcd">
Profit by your opportunity! =96 Anatrim =96 The up-to-the-moment & most=20=
fascinating flesh loss product is now readily available =96 As were told=20=
on Oprah
</a>
</center>
<br>
Can you count up all the cases when you said to yourself you would do=20=
anything for being saved from this horrible pounds of fat? Fortunately,=20=
now no great price is to be paid. With Anatrim, the earth-shaking, you=20=
can get naturally health life style and become really slimmer. Have a=20=
look at what customers say to us!
 <br>
<br>
<i>
=93I always had a stunning life till last year my girl told me I was=20=
corpulent and in need of being careful to my health. Life went the wrong=20=
way after that, until I discovered Anatrim =99. Since getting rid of more=20=
than 40 lbs only thanx to Anatrim,  my private life is back on track,=20=
considerably better than even before. Lots of thanx for the incredible=20=
product & the great maintenance service. Keep up your good action!=94
</i>
 <br>
<b>
<i>
Rikky Martin, San Diego
</i>
</b>
 <br>
<br>
<i>
"There=92s nothing better than slipping into a bikini that I have not=20=
been dressed in for a long time. I feel slim, determined, and healthy,=20=
thanx in great part to Anatrim! Great deal of thanks to you!"
</i>
 <br>
<b>
<i>
Lusia R., Texas
</i>
</b>
<br>
<br>
Check out Anatrim, and  you'll join the worldwide company of thousands=20=
of delighted user who get pleasure in the revolutionary results of=20=
Anatrim just now. Less eating insanity, less lbs and more gaiety in life!
<br>
<br>
<center>
<a href=3D"http://www.clate.hk/?zdpnjxrcd">
Proceed here to scan our invincible Anatrim deals!!!
</a>
</center>
</b>
</p>
<font color=3D"#D9EDFF">http://www.clate.hk/?zdpnjxrcd</font>

</BODY></HTML>
------------053B4F21C72991--



Received: from Brainstorm.nsw.bigpond.net.au (CPE-58-160-58-133.vic.bigpond.net.au [58.160.58.133]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l5875WHa016877; Fri, 8 Jun 2007 00:05:36 -0700 (MST) (envelope-from dirmbblvjif@mbblv.com)
Received: from 208.57.165.4 (HELO mail.mbblv.com) by imc.org with esmtp ((8L<49YT EA,3OR) id 0*+--T-AMRA,?-EB for ietf-pkix-oid-reg@imc.org; Fri, 8 Jun 2007 07:05:36 -1000
Date: 	Fri, 8 Jun 2007 07:05:36 -1000
From: "Waldo Looney" <dirmbblvjif@mbblv.com>
X-Mailer: The Bat! (v3.71.01) Educational
X-Priority: 3 (Normal)
Message-ID: <691901338.14836696302806@thhebat.net>
To: ietf-pkix-oid-reg@imc.org
Subject: She will love you more than any other guy
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------58425842CB6E1D"
X-Spam: Not detected

------------58425842CB6E1D
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


Finally the real thing =96 without money tricks! 
P.E.P. are very hot right this time! Well this is the real thing not a=20=
counterfeit! 

One of the very originals, totally unrivalled produce is easy=20=
accessible at any place!
 Draw attention to just what people say on this stuff:

"I pleased how fast this product affected on my boyfriend, he can=92t=20=
put an end to his talking about how hot he is having such new girth,=20=
length, and libido!"

Amelia B., Chicago

"In the beginning I thought the free sample I received was a mean=20=
trick, until I tried taking the P.E.P. I can=92t describe depict how=20=
greatly satisfied I am with the outcomes from using the patch for 7 brief=20=
weeks. I will be requesting regularly!" 
Steve Doubt, Bellevue WA

Read more recommendations on this astonishing product just now!
http://www.bipal.hk/?fdbfgtuwe

------------58425842CB6E1D
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Make her worship you</TITLE>
</HEAD>
<BODY>

<b>
Finally the real thing =96 without money tricks! 
<br>
<a href=3D"http://www.bipal.hk/?fdbfgtuwe">P.E.P.</a> are very hot=20=
right this time! Well this is the real thing not a counterfeit! 
<br>
One of the very originals, totally unrivalled produce is easy=20=
accessible at any place!
<br> Draw attention to just what people say on this stuff:
<p>
<i>
"I pleased how fast this product affected on my boyfriend, he can=92t=20=
put an end to his talking about how hot he is having such new girth,=20=
length, and libido!"
</i>
</p>
Amelia B., Chicago
<p>
<i>
"In the beginning I thought the free sample I received was a mean=20=
trick, until I tried taking the P.E.P. I can=92t describe depict how=20=
greatly satisfied I am with the outcomes from using the patch for 7 brief=20=
weeks. I will be requesting regularly!" </i>
</p>
Steve Doubt, Bellevue WA
<center>
<a href=3D"http://www.bipal.hk/?fdbfgtuwe">
Read more recommendations on this astonishing product just now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.bipal.hk/?fdbfgtuwe</font>

</BODY></HTML>
------------58425842CB6E1D--



Received: from 110.96.207.247.213.in-addr.arpa (host-110.INFORMGRAND.03-183.macomnet.net [213.247.207.110] (may be forged)) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l57NAwNa046786; Thu, 7 Jun 2007 16:11:00 -0700 (MST) (envelope-from dirmbijif@mbi.es)
Received: from [213.247.207.110] by mail.mbi.es; Thu, 7 Jun 2007 23:08:14 -0300
Date: 	Thu, 7 Jun 2007 23:08:14 -0300
From: "Mike Phipps" <dirmbijif@mbi.es>
X-Mailer: The Bat! (v2.00) Business
Reply-To: dirmbijif@mbi.es
X-Priority: 3 (Normal)
Message-ID: <820426631.68300601811016@mbi.es>
To: ietf-openproxy@imc.org
Subject: Can you imagine that you are healthy?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------6EFDA0CC59E829"

------------6EFDA0CC59E829
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

LegalRXMedications drug-store presents all cures you need to recover your health at lowest price. 
We manage across the globe with customers from Europe, America and Asia. 
At this time you got no need to look for chemist's somewhere at your local area.
We can convey meds of the highest quality to all parts of the globe.
Come please to our site & place an order for medicinal preparations that you need instantly straightly to your home. 
http://funrail.hk/ 
We are verified by VeriSign and VISA consequently we support safe & trustworthy purchase.

------------6EFDA0CC59E829
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
</HEAD>
<BODY>

<b><font color="#00CC33"><em>LegalRXMedications</em></font> drug-store presents all cures you need to recover your health at lowest price. <br>
We manage across the globe with customers from Europe, America and Asia. <br>
At this time you got no need to look for chemist's somewhere at your local area.<br>
We can convey meds of the highest quality to all parts of the globe.
<br>
<br>
<a href="http://funrail.hk/"><em>Come please to our site & place an order for medicinal preparations that you need instantly straightly to your home.</em></a></b> 
<br>
<font color="#D9EDFF">http://funrail.hk/</font> 
<br><b>We are verified by <font color="#FF0000"><em>VeriSign</em></font> and <font color="#FF0000"><em>VISA</em></font> consequently we support safe & trustworthy purchase.
</b>

</BODY></HTML>
------------6EFDA0CC59E829--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l579JTEj036269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Jun 2007 02:19:29 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l579JTWh036268; Thu, 7 Jun 2007 02:19:29 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mailhost.auckland.ac.nz (curly.its.auckland.ac.nz [130.216.12.33]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l579JSLN036262 for <ietf-pkix@imc.org>; Thu, 7 Jun 2007 02:19:28 -0700 (MST) (envelope-from pgut001@cs.auckland.ac.nz)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 3240B9C354; Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1]) by localhost (curly.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNFZQzb3BNHW; Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id 189929C352; Thu,  7 Jun 2007 21:19:27 +1200 (NZST)
Received: from medusa01.cs.auckland.ac.nz (medusa01.cs.auckland.ac.nz [130.216.34.33]) by iris.cs.auckland.ac.nz (Postfix) with ESMTP id 026BDD14CFA; Thu,  7 Jun 2007 21:19:24 +1200 (NZST)
Received: from pgut001 by medusa01.cs.auckland.ac.nz with local (Exim 3.36 #1 (Debian)) id 1HwE9T-000804-00; Thu, 07 Jun 2007 21:19:31 +1200
From: pgut001@cs.auckland.ac.nz (Peter Gutmann)
To: DPKemp@missi.ncsc.mil, ietf-pkix@imc.org, pbaker@verisign.com
Subject: RE: Three short fixes
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Message-Id: <E1HwE9T-000804-00@medusa01.cs.auckland.ac.nz>
Date: Thu, 07 Jun 2007 21:19:31 +1200
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>

"Hallam-Baker, Phillip" <pbaker@verisign.com> writes:

>The point here is precisely to allow a certificate to state 'there are no
>security claims being made here'.

So is the intent to create an attribute that says "This certificate is merely
a convenient universally-accepted blob for communicating a public key and a
name/email address/URL"?  In other words it's not really TLS-specific?

Peter.




Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l576uKr5098600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2007 23:56:20 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l576uK4s098599; Wed, 6 Jun 2007 23:56:20 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l576uGBY098564 for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 23:56:19 -0700 (MST) (envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000) id D4890D98634; Thu,  7 Jun 2007 08:56:13 +0200 (CEST)
Date: Thu, 7 Jun 2007 08:56:13 +0200
From: Thomas Pornin <pornin@bolet.org>
To: pkix <ietf-pkix@imc.org>
Subject: Re: Three short fixes
Message-ID: <20070607065613.GA2663@localhost.localdomain>
References: <20070605064632.GA10490@localhost.localdomain> <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.5.11
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>

On Wed, Jun 06, 2007 at 10:07:14AM -0700, Hallam-Baker, Phillip wrote:
> If you have a certificate that does not have sufficient information to
> establish encryption then you can't use encryption. I don't see the
> relevance of that fact. 

The point is that certificates are meant to be used only after a
complete path validation, and the "sufficient information to establish
encryption" is computed by the validation procedure. It so happens that
for some public key types, you may extract the public key from a lone
certificate, but nothing in X.509 was optimized for such usage.

Another way to see your proposal is the following: what you suggest is
that the server encodes its public key into something which looks like a
certificate. The server adds issuer and subject X.500 names, a serial
number, validity dates, a signature, and a bunch of extensions,
including one which states that all this added information is rubbish
and the client should just extract the public key and ignore everything
else in that "certificate". This strikes me as unnecessarily
inefficient: the server adds several layers of data, making the whole
object fatter and more complex, just so that the client gets rid of that
extra data. It would be much more efficient, especially network-wise, to
just send the server public key without bothering at all with encodings
which look like certificates and hundreds of bytes whose sole fate is to
be utterly ignored by the receiver.

And, lo and behold, SSL/TLS already has cipher suites where a simple
public key is transmitted, with no X.509 implication at all. These are
named "DH_anon". These cipher suites do what you ask for, and do it
faster and better than what your proposal would imply.


	--Thomas Pornin



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56IQk8r024649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2007 11:26:46 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56IQkvr024648; Wed, 6 Jun 2007 11:26:46 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56IQjpr024631 for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 11:26:46 -0700 (MST) (envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8]) by stingray.missi.ncsc.mil with SMTP id l56IQhOZ006368 for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 14:26:43 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Wed, 06 Jun 2007 14:26:42 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Jun 2007 14:26:42 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 14:26:42 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF5989078C6BEB@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gAF9iywAAAHbvAA==
References: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil> <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 18:26:42.0754 (UTC) FILETIME=[3B412A20:01C7A868]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15222000
X-TM-AS-Result: : Yes--15.524700-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE1LTE1MDU2Ny03MDE1?= =?us-ascii?B?NzYtNzA1OTAxLTcwOTU4NC03MDIzNTgtNzAzMzY2LTcwMTQ1NS03?= =?us-ascii?B?MDEzOTQtNzAwNzU0LTcwMDI2Mi03MDIxMjYtNzAyOTY4LTcwNjQx?= =?us-ascii?B?Mi0xMTM2NjAtNzA3NDEwLTcwMjEwNi03MDMxNzYtMTIxNTM0LTcw?= =?us-ascii?B?MTkyNy03MDQxODktNzAwMDczLTcwMDIxNS03MDExNzUtNzAyNjI2?= =?us-ascii?B?LTcxMDYxMS03MDM1NDQtNzAwNzU2LTcwMzc4Mi03MDI0ODUtNzA1?= =?us-ascii?B?Mzg4LTcwMDg2OS03MDI3MjYtNzA5MzcyLTEwNTcwMC0xMDUwNDAt?= =?us-ascii?B?NzAxMTYzLTcwNDA0OS03MDQwNTUtNzAwNzQ5LTcwMDI5OC0xMzk3?= =?us-ascii?B?MDQtNzA4MTk2LTcwMDM0Mi0xMTE2MDQtMTg4MTE5LTcwNjExMC03?= =?us-ascii?B?MDAwMTgtNzAwMDA3LTcwMDAxNS03MDAwMTctNzAwMzYyLTE4ODEx?= =?us-ascii?B?OC0xODgxNDYtNzAwNzgyLTcwNjgxNy03MDI2MDktNzAzMzIxLTE4?= =?us-ascii?B?ODExNC0xODgwMzgtNzAwMzQ1LTcwNTcxOC03MDE4MjctNzAwMjY0?= =?us-ascii?B?LTcwMjQ5Ny03MDQ0MjUtNzA0MTQxLTcwMDczMi03MDEwMTItNzAw?= =?us-ascii?B?OTA3LTcwMTMwNi03MDI4MzgtNzAwNjIyLTcwMDE2MC0xODgxMjUt?= =?us-ascii?B?MTExNjA1LTcwMDA3NC03MDAxNDItNzAwMDc5LTE4ODEyNC0xODgw?= =?us-ascii?B?NzgtMTExNjA4LTcwMDUyOS03MDAwNzctNzAwODAyLTcwMTY2OS0x?= =?us-ascii?B?ODgwNTctNzA1NDk0LTE4ODAzNS03MDAxMDktMTQ4MDUw?=
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>

This is a multi-part message in MIME format.

------=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A868.3B35778E"

------_=_NextPart_001_01C7A868.3B35778E
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

And my point is that there is no reason to use a certificate to say "no
security claims are being made".  You achieve the identical result (an
encrypted channel that makes no security claims) by using DH_ANON
encryption without transmitting, validating, or even issuing a
certificate.

=20

In other words, it is up to applications and encryption protocols to
support unauthenticated and unannounced encryption if they so desire.
Because no certificates are needed to support such applications, there
is no requirement for PKIX to profile such certificates.

=20

=20

=20

[phill]: If you have a certificate that does not have sufficient
information to establish encryption then you can't use encryption. I
don't see the relevance of that fact.

=20

A certificate only needs to have sufficient information to
"authenticate" encryption, not establish.  The amount of certified
information needed to "establish" an unauthenticated encryption key is
zero.    DH or RSA public keys and parameters can be made up on the fly
(ephemerally) or pre-stored (statically) and handshaked without ever
touching a CA.

=20

=20

  _____ =20

From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]=20
Sent: Wednesday, June 06, 2007 1:06 PM
To: Kemp, David P.; pkix
Subject: RE: Three short fixes

=20

=20

=20

3) No Padlock Icon attribute

=20

I do not believe PKIX should sponsor an attribute that tells a
certificate user to "ignore this certificate", e.g. "accept this
certificate even if it cannot be validated".  I don't object to
applications supporting unauthenticated encryption while making no
security claims.  But if the application is not going to authenticate an
encryption key, then the application should not be transmitting or
consuming certificates in the first place.  Saying "but TLS won't work
without certificates" is not a convincing argument - the TLS working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not
PKIX.=20

=20

The point here is precisely to allow a certificate to state 'there are
no security claims being made here'.=20

=20

The user does not accept the certificate, the client application does.
No user has ever checked a certificate path and no user ever will. The
question is whether the client application should be telling the user
that it is 'safe' or not.

=20

I don't see why we need to tell the user that encryption is being used
unless they have explicitly said that they need confidentiality. Telling
the user that there is encryption means also telling them about a whole
range of failures and other error conditions.=20

=20

=20


------_=_NextPart_001_01C7A868.3B35778E
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=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 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>And my point is that there is no =
reason to
use a certificate to say &#8220;no security claims are being =
made&#8221;. &nbsp;You
achieve the identical result (an encrypted channel that makes no =
security
claims) by using DH_ANON encryption without transmitting, validating, or =
even
issuing a certificate.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>In other words, it is up to =
applications
and encryption protocols to support unauthenticated and unannounced =
encryption
if they so desire. &nbsp;Because no certificates are needed to support =
such
applications, there is no requirement for PKIX to profile such =
certificates.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>[phill]:
</span></font><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>If you have a certificate that does not have
sufficient information to establish encryption then you can't use =
encryption. I
don't see the relevance of that fact.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3D"Courier New"><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>A certificate only needs to have
sufficient information to &#8220;authenticate&#8221; encryption, not =
establish.
&nbsp;The amount of certified information needed to =
&#8220;establish&#8221; an
unauthenticated encryption key is zero. &nbsp;&nbsp;&nbsp;DH or RSA =
public keys and parameters
can be made up on the fly (ephemerally) or pre-stored (statically) and
handshaked without ever touching a CA.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Hallam-Baker,
Phillip [mailto:pbaker@verisign.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, June 06, =
2007
1:06 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Kemp, David P.; =
pkix<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: Three short =
fixes</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>3) No Padlock Icon =
attribute</span></font></b></strong><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I do not believe PKIX should =
sponsor an
attribute that tells a certificate user to &#8220;ignore this
certificate&#8221;, e.g. &#8220;accept this certificate even if it =
cannot be
validated&#8221;. &nbsp;I don&#8217;t object to applications supporting
unauthenticated encryption while making no security claims. &nbsp;But if =
the
application is not going to authenticate an encryption key, then the
application should not be transmitting or consuming certificates in the =
first
place. &nbsp;Saying &#8220;but TLS won&#8217;t work without =
certificates&#8221;
is not a convincing argument &#8211; the TLS working group has made =
decisions
regarding unauthenticated (and/or unencrypted) ciphersuites, and the =
place to
revisit those decisions is there, not PKIX.</span></font><font size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</blockquote>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The&nbsp;point here is precisely to =
allow
a certificate to state 'there are no security claims being made =
here'.&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>The user does not accept the =
certificate,
the client application does. No user has ever checked a certificate path =
and no
user ever will. The question is whether the client application should be
telling the user that it is 'safe' or not.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I don't see why we need to tell the =
user
that encryption is being used unless they have explicitly said that they =
need
confidentiality. Telling the user that there is encryption means also =
telling
them about a whole range of failures and other error conditions. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font><font size=3D2 color=3Dblue =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:blue'><o:p></o:p></span=
></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7A868.3B35778E--

------=_NextPartTM-000-57e80408-8ac9-4714-b51b-db3506ec8a19--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H8VYN099520 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2007 10:08:31 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56H8VeP099519; Wed, 6 Jun 2007 10:08:31 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H8UpI099513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 10:08:30 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l56H8Lvd004490; Wed, 6 Jun 2007 10:08:24 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 10:08:23 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 10:07:14 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6002@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <20070605064632.GA10490@localhost.localdomain>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: AcenSVqu7Qxesz8PRwe9LBwZZsDSEgBE5obw
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Thomas Pornin" <pornin@bolet.org>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 17:08:23.0365 (UTC) FILETIME=[4A334F50:01C7A85D]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l56H8VpH099514
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>

If you have a certificate that does not have sufficient information to establish encryption then you can't use encryption. I don't see the relevance of that fact. 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Thomas Pornin
> Sent: Tuesday, June 05, 2007 2:47 AM
> To: pkix
> Subject: Re: Three short fixes
> 
> 
> On Mon, Jun 04, 2007 at 05:01:39PM -0400, Kemp, David P. wrote:
> > I do not believe PKIX should sponsor an attribute that tells a 
> > certificate user to "ignore this certificate", e.g. "accept this 
> > certificate even if it cannot be validated".
> 
> In all generality, the public key represented in a 
> certificate is obtained as a byproduct of path validation: 
> for DSA-like public keys, the public key parameters may be 
> inherited from certificates higher in the path. A stand-alone 
> certificate may not contain by itself enough data to 
> represent a complete and usable public key. Of course, most 
> certificates in the wild contain RSA public keys, which are 
> self-contained. Nonetheless, using the contents of 
> certificates outside of the context of a certificate path is 
> a kind of paradigm shift from what X.509 usually does.
> 
> 
> > Saying "but TLS won't work without certificates" is not a 
> convincing 
> > argument - the TLS working group has made decisions regarding 
> > unauthenticated (and/or unencrypted) ciphersuites, and the place to 
> > revisit those decisions is there, not PKIX.
> 
> TLS 1.1 (RFC 4346) still documents the "DH_anon" ciphersuites 
> which allow for unauthenticated key exchange. They are marked 
> as deprecated because they are vulnerable to 
> man-in-the-middle attacks (and you have a quite unusual 
> attack model if encryption is needed by active attacks are 
> not to be feared). But they still exist. Ideally, additional 
> "RSA_anon"
> cipher suites would be added, because RSA key exchange makes 
> it much easier for megahertz-impaired clients.
> 
> 
> 	--Thomas Pornin
> 
> 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H6tQZ099045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2007 10:06:56 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56H6tfo099044; Wed, 6 Jun 2007 10:06:55 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56H6se8099036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 10:06:55 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l56H6nci004280; Wed, 6 Jun 2007 10:06:52 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 10:06:49 -0700
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_01C7A85D.1234E33F"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 10:05:40 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6001@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2gAF9iywA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Kemp, David P." <DPKemp@missi.ncsc.mil>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 17:06:49.0305 (UTC) FILETIME=[1222E490:01C7A85D]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A85D.1234E33F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20

	3) No Padlock Icon attribute

	=20

	I do not believe PKIX should sponsor an attribute that tells a =
certificate user to "ignore this certificate", e.g. "accept this =
certificate even if it cannot be validated".  I don't object to =
applications supporting unauthenticated encryption while making no =
security claims.  But if the application is not going to authenticate an =
encryption key, then the application should not be transmitting or =
consuming certificates in the first place.  Saying "but TLS won't work =
without certificates" is not a convincing argument - the TLS working =
group has made decisions regarding unauthenticated (and/or unencrypted) =
ciphersuites, and the place to revisit those decisions is there, not =
PKIX.=20

	=20

The point here is precisely to allow a certificate to state 'there are =
no security claims being made here'.=20

=20

The user does not accept the certificate, the client application does. =
No user has ever checked a certificate path and no user ever will. The =
question is whether the client application should be telling the user =
that it is 'safe' or not.

=20

I don't see why we need to tell the user that encryption is being used =
unless they have explicitly said that they need confidentiality. Telling =
the user that there is encryption means also telling them about a whole =
range of failures and other error conditions.=20

=20

=20


------_=_NextPart_001_01C7A85D.1234E33F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV><FONT=20
face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DSection1>
  <P class=3DMsoNormal><STRONG><B><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">3) No Padlock Icon=20
  attribute</SPAN></FONT></B></STRONG><o:p></o:p></P></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: =
navy"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I do not =
believe PKIX=20
  should sponsor an attribute that tells a certificate user to =93ignore =
this=20
  certificate=94, e.g. =93accept this certificate even if it cannot be =
validated=94.=20
  &nbsp;I don=92t object to applications supporting unauthenticated =
encryption=20
  while making no security claims. &nbsp;But if the application is not =
going to=20
  authenticate an encryption key, then the application should not be=20
  transmitting or consuming certificates in the first place. =
&nbsp;Saying =93but=20
  TLS won=92t work without certificates=94 is not a convincing argument =
=96 the TLS=20
  working group has made decisions regarding unauthenticated (and/or=20
  unencrypted) ciphersuites, and the place to revisit those decisions is =
there,=20
  not PKIX.<FONT color=3D#0000ff><SPAN=20
  class=3D531105816-06062007>&nbsp;</SPAN></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dnavy><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
  color=3D#0000ff><SPAN=20
  =
class=3D531105816-06062007></SPAN></FONT></SPAN></FONT>&nbsp;</P></DIV></=
BLOCKQUOTE>
<P class=3DMsoNormal dir=3Dltr><FONT color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><SPAN class=3D531105816-06062007>The&nbsp;point here is =
precisely to=20
allow a certificate to state 'there are no security claims being made=20
here'.&nbsp;</SPAN></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT color=3Dnavy><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN class=3D531105816-06062007>The user does not =
accept the=20
certificate, the client application does. No user has ever checked a =
certificate=20
path and no user ever will. The question is whether the client =
application=20
should be telling the user that it is 'safe' or=20
not.</SPAN></o:p></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN class=3D531105816-06062007>I don't see why we =
need to=20
tell the user that encryption is being used unless they have explicitly =
said=20
that they need confidentiality. Telling the user that there is =
encryption means=20
also telling them about a whole range of failures and other error =
conditions.=20
</SPAN></o:p></FONT></SPAN></FONT></P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P>
<P class=3DMsoNormal dir=3Dltr><FONT><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#0000ff><o:p><SPAN=20
class=3D531105816-06062007></SPAN></o:p></FONT></SPAN></FONT>&nbsp;</P></=
BODY></HTML>

------_=_NextPart_001_01C7A85D.1234E33F--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56GwjIB096564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jun 2007 09:58:45 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l56Gwj28096563; Wed, 6 Jun 2007 09:58:45 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l56Gwh9d096546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Wed, 6 Jun 2007 09:58:44 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by colibri.verisign.com (8.13.6/8.13.4) with ESMTP id l56Gweed008955; Wed, 6 Jun 2007 09:58:40 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 09:58:40 -0700
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_01C7A85B.EEB36611"
Subject: RE: Three short fixes
Date: Wed, 6 Jun 2007 09:57:31 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A6000@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsAACMPXgAFcVnrA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Trevor Freeman" <trevorf@exchange.microsoft.com>, <turners@ieca.com>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 06 Jun 2007 16:58:40.0231 (UTC) FILETIME=[EEA01F70:01C7A85B]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A85B.EEB36611
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I already have an authentication process for an X.500 DN. Seems like =
that is going to be the most efficient scheme.


________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
	Sent: Monday, June 04, 2007 7:42 PM
	To: Hallam-Baker, Phillip; turners@ieca.com; pkix
	Subject: RE: Three short fixes
=09
=09

	I would have thought audio is a more constrained problem for =
verification than images. Saying you can build a procedure which =
verifies the rights someone to assert "foo bar" but you have difficulty =
building a procedure where someone verifies a wav file contains someone =
reading the text "foo bar" seems hard to believe. However the set of =
logotypes defined by 3709 is extensible so you can define whatever =
logotypes you want for the audio browsers and it does not need workgroup =
input.

	=20

	From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]=20
	Sent: Monday, June 04, 2007 3:39 PM
	To: Trevor Freeman; turners@ieca.com; pkix
	Subject: RE: Three short fixes

	=20

	Talking to folk it appears that audio is useful but not enough.=20

	=20

	How do I develop authentication criteria for audio? I am having a =
difficult enough time with images. And it also tips into the language =
issue.

	=20

	I can't render audio in braille for example. If it is in text or an =
X.500 DN I can render it in any medium I need.

	=20

	=20

		=20

________________________________

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
		Sent: Monday, June 04, 2007 3:39 PM
		To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
		Subject: RE: Three short fixes

		Yes, RFC3709 already supports audio formats which was specifically =
added for accessibility scenarios such as visually impaired users.

		=20

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Turner, Sean P.
		Sent: Monday, June 04, 2007 11:44 AM
		To: 'Hallam-Baker, Phillip'; 'pkix'
		Subject: RE: Three short fixes

		=20

		Phil,

		=20

		For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).

		=20

		spt

		=20

________________________________

		From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
		Sent: Monday, June 04, 2007 1:37 PM
		To: pkix
		Subject: Three short fixes

		Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:

		=20

		1) Text Representation of Community Logos

		=20

		    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20

		=20

		    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.

		=20

		    This is not a problem for either the subject or the issuer since =
there are already=20

		=20

		2) Member Since attribute

		=20

		    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.

		=20

		3) No Padlock Icon attribute

		=20

		    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.

		=20

		    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.

		=20

		    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.

		=20

		    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.

		=20

		=20

		Before writing up a draft I would like to guage whether folk feel =
there is a need for any of these and if so what the likely level of =
contention is, whether it can be completed within PKIX or should it be a =
personal submission.

		=20

		Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.

		=20

		We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A85B.EEB36611
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =
=3D=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D =3D "DAV:" xmlns:x2 =
=3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
=3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" =
xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal
}
SPAN.EmailStyle19 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D265555616-06062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I already have an authentication process for an =
X.500 DN.=20
Seems like that is going to be the most efficient=20
scheme.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Trevor=20
  Freeman<BR><B>Sent:</B> Monday, June 04, 2007 7:42 PM<BR><B>To:</B>=20
  Hallam-Baker, Phillip; turners@ieca.com; pkix<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">I=20
  would have thought audio is a more constrained problem for =
verification than=20
  images. Saying you can build a procedure which verifies the rights =
someone to=20
  assert =93foo bar=94 but you have difficulty building a procedure =
where someone=20
  verifies a wav file contains someone reading the text =93foo bar=94 =
seems hard to=20
  believe. However the set of logotypes defined by 3709 is extensible so =
you can=20
  define whatever logotypes you want for the audio browsers and it does =
not need=20
  workgroup input.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> =
Hallam-Baker,=20
  Phillip [mailto:pbaker@verisign.com] <BR><B>Sent:</B> Monday, June 04, =
2007=20
  3:39 PM<BR><B>To:</B> Trevor Freeman; turners@ieca.com;=20
  pkix<BR><B>Subject:</B> RE: Three short=20
fixes<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Talking=20
  to folk it appears that audio is useful but not enough. =
</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">How do=20
  I develop authentication criteria for audio? I am having a difficult =
enough=20
  time with images. And it also tips into the language=20
  issue.</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">I=20
  can't render audio in braille for example. If it is in text or an =
X.500 DN I=20
  can render it in any medium I need.</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Trevor Freeman<BR><B>Sent:</B> Monday, June 04, 2007 =
3:39=20
    PM<BR><B>To:</B> turners@ieca.com; Hallam-Baker, Phillip;=20
    'pkix'<BR><B>Subject:</B> RE: Three short =
fixes</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">Yes,=20
    RFC3709 already supports audio formats which was specifically added =
for=20
    accessibility scenarios such as visually impaired=20
    users.<o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
    <DIV>
    <DIV=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
    <P class=3DMsoNormal><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Turner, Sean P.<BR><B>Sent:</B> Monday, June 04, 2007 =
11:44=20
    AM<BR><B>To:</B> 'Hallam-Baker, Phillip'; 'pkix'<BR><B>Subject:</B> =
RE:=20
    Three short fixes<o:p></o:p></SPAN></P></DIV></DIV>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Phil,</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">For=20
    the logos, can't we just use the logo types RFC (<A=20
    =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">spt</SPAN><o:p></o:p></P>
    <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
    <HR align=3Dcenter width=3D"100%" SIZE=3D2>
    </DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
    owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
    Behalf Of </B>Hallam-Baker, Phillip<BR><B>Sent:</B> Monday, June 04, =
2007=20
    1:37 PM<BR><B>To:</B> pkix<BR><B>Subject:</B> Three short=20
    fixes</SPAN><o:p></o:p></P>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Work in =
the w3C=20
    Web Security Context group and elsewhere has prompted me to consider =
that we=20
    need to take the necessary steps to allow the following information =
to be=20
    encoded in certificates in a consistent =
manner:</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">1) Text =

    Representation of Community =
Logos</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
an=20
    accessibility issue. If a certificate is issued with an FDIC =
community logo=20
    in it there has to be a way to present this information to blind =
users,=20
    users with an audio browser, etc. etc. </SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">One =
simple fix=20
    would be to simply allow for text/plain as a community logo slot.=20
    Alternatively we could encode the information in the image itself.=20
    Alternatively we could specify an extension OID that simply takes a =
list of=20
    community DNs.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
not a=20
    problem for either the subject or the issuer since there are already =

    </SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">2) =
Member Since=20
    attribute</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
    would take a date as a parameter and would encode the first date at =
which=20
    the certified entity was issued a credential. The exact =
interpretation of=20
    this would be left to the CPS of the certificate=20
    issuer.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><STRONG><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">3) No =
Padlock=20
    Icon attribute</SPAN></STRONG><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
    would allow a certificate to say that no user indication should be =
specified=20
    in the chrome, nor should any nag screens. It would be an option =
that the=20
    issuing CA would put in at their =
discretion.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">The =
need for this=20
    is to allow a CA to support a wide range of applications =
which&nbsp;require=20
    encryption but require even less authentication than current schemes =
such as=20
    domain validated certs. For example self signed certificates, =
certificates=20
    issued to embedded hardware, etc. etc.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">What I =
want to do=20
    is to get us to the point where the browser authors feel comfortable =
with a=20
    user experience that does not contain the nag screens that disfigure =
current=20
    schemes. In many cases all that is required is to turn on =
encryption. The=20
    user does not need to be told that the certificate has expired, has =
been=20
    issued by an unknown CA or any of the usual nonsense. just don't =
tell the=20
    user that its safe in the first place and the browser does not need =
to say=20
    that it is dangerous.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Clearly =
this=20
    attribute is unnecessary from a technical point of view. From a =
market point=20
    of view it is essential if we are going to ensure that applications =
are=20
    doing the right thing. The padlock icon has some pretty strong =
semantics.=20
    Many applications require less. We are not going to get everyone who =

    currently has a padlock certificate to get a green bar cert. So lets =
serve=20
    the applications that require even less than the padlock without =
diluting=20
    the padlock semantics further.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Before =
writing up=20
    a draft I would like to guage whether folk feel there is a need for =
any of=20
    these and if so what the likely level of contention is, whether it =
can be=20
    completed within PKIX or should it be a personal=20
    submission.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Main =
thing I want=20
    here is the reservation of the OIDs under a neutral, non VeriSign =
arc. I=20
    don't think that the rest of the industry would feel comfortable =
using=20
    VeriSign OIDs and VeriSign might not be comfortable with them doing =
so=20
    either.</SPAN><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">We are =
definitely=20
    going to require the first, the second seems to be considered a 'no =
brainer'=20
    since it is information that every CA holds, that is not currently =
provided=20
    to the user and is very very effective at providing security=20
    =
context.</SPAN><o:p></o:p></P></DIV></DIV></BLOCKQUOTE></DIV></DIV></BLOC=
KQUOTE></BODY></HTML>

------_=_NextPart_001_01C7A85B.EEB36611--



Received: from bobowska-phil9r.tesatnet.pl (host-88.199.62.7.tesatnet.pl [88.199.62.7]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l55LiR1V092726; Tue, 5 Jun 2007 14:44:30 -0700 (MST) (envelope-from cedmadroneloungegym@madronelounge.com)
Received: from 204.202.2.157 (HELO madronelounge.com) by imc.org with esmtp ((0--7F4YUFN 249/) id .9D:SU-XM/A@1-0( for imc-sfl@imc.org; Tue, 5 Jun 2007 21:44:36 -0100
Date: 	Tue, 5 Jun 2007 21:44:36 -0100
From: "Gino Doran" <cedmadroneloungegym@madronelounge.com>
X-Mailer: The Bat! (v3.51.10) Professional
X-Priority: 3 (Normal)
Message-ID: <522025106.75329645631050@thhebat.net>
To: imc-sfl@imc.org
Subject: Hey man, stop throwing away your money
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------053BB486E6ED34F"
X-Spam: Not detected

------------053BB486E6ED34F
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


After all the genuine thing =96 without ripoffs! 
P.E.P. are very hot right this time! Well this is the true stuff not a=20=
counterfeit! 

One of the very prominents, totally unrivalled produce is available=20=
everywhere!
 Take a look at just what people say on this product:

"I love how swiftly your stuff affected on my boyfriend, he can not=20=
stop chatting on how excited he is having such new girth, length, and=20=
libido!"

Linda F., New York

"At first I considered the sample package I got gratis was some kind of=20=
joke, till I tried using the P.E.P. I can not describe report how pleased=20=
I am with the effect I got from using the patch for 2 brief months. I'll=20=
be ordering on a regular basis!" 
Rikky Martin, San Diego

Read more testimonials on this amazing product right here and right now!
http://www.beatlo.com/?phvomtaniwi

------------053BB486E6ED34F
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Don't get left behind</TITLE>
</HEAD>
<BODY>

<b>
After all the genuine thing =96 without ripoffs! 
<br>
<a href=3D"http://www.beatlo.com/?phvomtaniwi">P.E.P.</a> are very hot=20=
right this time! Well this is the true stuff not a counterfeit! 
<br>
One of the very prominents, totally unrivalled produce is available=20=
everywhere!
<br> Take a look at just what people say on this product:
<p>
<i>
"I love how swiftly your stuff affected on my boyfriend, he can not=20=
stop chatting on how excited he is having such new girth, length, and=20=
libido!"
</i>
</p>
Linda F., New York
<p>
<i>
"At first I considered the sample package I got gratis was some kind of=20=
joke, till I tried using the P.E.P. I can not describe report how pleased=20=
I am with the effect I got from using the patch for 2 brief months. I'll=20=
be ordering on a regular basis!" </i>
</p>
Rikky Martin, San Diego
<center>
<a href=3D"http://www.beatlo.com/?phvomtaniwi">
Read more testimonials on this amazing product right here and right now!
</a>
</center>
</b>
<font color=3D"#D9EDFF">http://www.beatlo.com/?phvomtaniwi</font>

</BODY></HTML>
------------053BB486E6ED34F--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l556kaca009661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 23:46:36 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l556kafI009660; Mon, 4 Jun 2007 23:46:36 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from helios.bolet.org (helios.bolet.org [88.191.25.203]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l556kXoY009622 for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 23:46:35 -0700 (MST) (envelope-from pornin@helios.bolet.org)
Received: by helios.bolet.org (Postfix, from userid 1000) id B56B6D98313; Tue,  5 Jun 2007 08:46:32 +0200 (CEST)
Date: Tue, 5 Jun 2007 08:46:32 +0200
From: Thomas Pornin <pornin@bolet.org>
To: pkix <ietf-pkix@imc.org>
Subject: Re: Three short fixes
Message-ID: <20070605064632.GA10490@localhost.localdomain>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com> <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
User-Agent: Mutt/1.5.11
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>

On Mon, Jun 04, 2007 at 05:01:39PM -0400, Kemp, David P. wrote:
> I do not believe PKIX should sponsor an attribute that tells a
> certificate user to "ignore this certificate", e.g. "accept this
> certificate even if it cannot be validated".

In all generality, the public key represented in a certificate is
obtained as a byproduct of path validation: for DSA-like public keys,
the public key parameters may be inherited from certificates higher in
the path. A stand-alone certificate may not contain by itself enough
data to represent a complete and usable public key. Of course, most
certificates in the wild contain RSA public keys, which are
self-contained. Nonetheless, using the contents of certificates outside
of the context of a certificate path is a kind of paradigm shift from
what X.509 usually does.


> Saying "but TLS won't work without certificates" is not a convincing
> argument - the TLS working group has made decisions regarding
> unauthenticated (and/or unencrypted) ciphersuites, and the place to
> revisit those decisions is there, not PKIX.

TLS 1.1 (RFC 4346) still documents the "DH_anon" ciphersuites which
allow for unauthenticated key exchange. They are marked as deprecated
because they are vulnerable to man-in-the-middle attacks (and you have a
quite unusual attack model if encryption is needed by active attacks are
not to be feared). But they still exist. Ideally, additional "RSA_anon"
cipher suites would be added, because RSA key exchange makes it much
easier for megahertz-impaired clients.


	--Thomas Pornin



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54NgL1o059765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 16:42:21 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54NgLnk059764; Mon, 4 Jun 2007 16:42:21 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail7.exchange.microsoft.com [131.107.1.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54NgJgA059746 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 16:42:19 -0700 (MST) (envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-01.exchange.corp.microsoft.com (157.54.54.216) by DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft SMTP Server (TLS) id 8.1.122.1; Mon, 4 Jun 2007 16:42:18 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by df-bhd-01.exchange.corp.microsoft.com ([157.54.54.216]) with mapi; Mon, 4 Jun 2007 16:42:18 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, "turners@ieca.com" <turners@ieca.com>, pkix <ietf-pkix@imc.org>
Date: Mon, 4 Jun 2007 16:42:10 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsAACMPXg
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com> <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_"
MIME-Version: 1.0
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>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would have thought audio is a more constrained problem for verification t=
han images. Saying you can build a procedure which verifies the rights some=
one to assert "foo bar" but you have difficulty building a procedure where =
someone verifies a wav file contains someone reading the text "foo bar" see=
ms hard to believe. However the set of logotypes defined by 3709 is extensi=
ble so you can define whatever logotypes you want for the audio browsers an=
d it does not need workgroup input.

From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
Sent: Monday, June 04, 2007 3:39 PM
To: Trevor Freeman; turners@ieca.com; pkix
Subject: RE: Three short fixes

Talking to folk it appears that audio is useful but not enough.

How do I develop authentication criteria for audio? I am having a difficult=
 enough time with images. And it also tips into the language issue.

I can't render audio in braille for example. If it is in text or an X.500 D=
N I can render it in any medium I need.



________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Trevor Freeman
Sent: Monday, June 04, 2007 3:39 PM
To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
Subject: RE: Three short fixes
Yes, RFC3709 already supports audio formats which was specifically added fo=
r accessibility scenarios such as visually impaired users.

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Turner, Sean P.
Sent: Monday, June 04, 2007 11:44 AM
To: 'Hallam-Baker, Phillip'; 'pkix'
Subject: RE: Three short fixes

Phil,

For the logos, can't we just use the logo types RFC (http://ietf.org/rfc/rf=
c3709.txt).

spt

________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes
Work in the w3C Web Security Context group and elsewhere has prompted me to=
 consider that we need to take the necessary steps to allow the following i=
nformation to be encoded in certificates in a consistent manner:

1) Text Representation of Community Logos

    This is an accessibility issue. If a certificate is issued with an FDIC=
 community logo in it there has to be a way to present this information to =
blind users, users with an audio browser, etc. etc.

    One simple fix would be to simply allow for text/plain as a community l=
ogo slot. Alternatively we could encode the information in the image itself=
. Alternatively we could specify an extension OID that simply takes a list =
of community DNs.

    This is not a problem for either the subject or the issuer since there =
are already

2) Member Since attribute

    This attribute would take a date as a parameter and would encode the fi=
rst date at which the certified entity was issued a credential. The exact i=
nterpretation of this would be left to the CPS of the certificate issuer.

3) No Padlock Icon attribute

    This attribute would allow a certificate to say that no user indication=
 should be specified in the chrome, nor should any nag screens. It would be=
 an option that the issuing CA would put in at their discretion.

    The need for this is to allow a CA to support a wide range of applicati=
ons which require encryption but require even less authentication than curr=
ent schemes such as domain validated certs. For example self signed certifi=
cates, certificates issued to embedded hardware, etc. etc.

    What I want to do is to get us to the point where the browser authors f=
eel comfortable with a user experience that does not contain the nag screen=
s that disfigure current schemes. In many cases all that is required is to =
turn on encryption. The user does not need to be told that the certificate =
has expired, has been issued by an unknown CA or any of the usual nonsense.=
 just don't tell the user that its safe in the first place and the browser =
does not need to say that it is dangerous.

    Clearly this attribute is unnecessary from a technical point of view. F=
rom a market point of view it is essential if we are going to ensure that a=
pplications are doing the right thing. The padlock icon has some pretty str=
ong semantics. Many applications require less. We are not going to get ever=
yone who currently has a padlock certificate to get a green bar cert. So le=
ts serve the applications that require even less than the padlock without d=
iluting the padlock semantics further.


Before writing up a draft I would like to guage whether folk feel there is =
a need for any of these and if so what the likely level of contention is, w=
hether it can be completed within PKIX or should it be a personal submissio=
n.

Main thing I want here is the reservation of the OIDs under a neutral, non =
VeriSign arc. I don't think that the rest of the industry would feel comfor=
table using VeriSign OIDs and VeriSign might not be comfortable with them d=
oing so either.

We are definitely going to require the first, the second seems to be consid=
ered a 'no brainer' since it is information that every CA holds, that is no=
t currently provided to the user and is very very effective at providing se=
curity context.

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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'>I would have thought audio is a more constrained problem for
verification than images. Saying you can build a procedure which verifies t=
he rights
someone to assert &#8220;foo bar&#8221; but you have difficulty building a =
procedure
where someone verifies a wav file contains someone reading the text &#8220;=
foo bar&#8221;
seems hard to believe. However the set of logotypes defined by 3709 is exte=
nsible
so you can define whatever logotypes you want for the audio browsers and it=
 does
not need workgroup input.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'> Hallam-Baker,
Phillip [mailto:pbaker@verisign.com] <br>
<b>Sent:</b> Monday, June 04, 2007 3:39 PM<br>
<b>To:</b> Trevor Freeman; turners@ieca.com; pkix<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Talking to folk it appears that audio is useful but not enough.=
 </span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>How do I develop authentication criteria for audio? I am having=
 a
difficult enough time with images. And it also tips into the language issue=
.</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>I can't render audio in braille for example. If it is in text o=
r an
X.500 DN I can render it in any medium I need.</span><o:p></o:p></p>

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

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

<blockquote style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0=
in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Trevor Freeman<br=
>
<b>Sent:</b> Monday, June 04, 2007 3:39 PM<br>
<b>To:</b> turners@ieca.com; Hallam-Baker, Phillip; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes</span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Yes, RFC3709 already supports audio formats which was
specifically added for accessibility scenarios such as visually impaired us=
ers.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'>
owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] <b>On Be=
half
Of </b>Turner, Sean P.<br>
<b>Sent:</b> Monday, June 04, 2007 11:44 AM<br>
<b>To:</b> 'Hallam-Baker, Phillip'; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Phil,</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>For the logos, can't we just use the logo types RFC (<a
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt</a=
>).</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>spt</span><o:p></o:p></p>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Hallam-Baker, Phi=
llip<br>
<b>Sent:</b> Monday, June 04, 2007 1:37 PM<br>
<b>To:</b> pkix<br>
<b>Subject:</b> Three short fixes</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Work
in the w3C Web Security Context group and elsewhere has prompted me to cons=
ider
that we need to take the necessary steps to allow the following information=
 to
be encoded in certificates in a consistent manner:</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>1)
Text Representation of Community Logos</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is an accessibility issue. If a certificate is
issued with an FDIC community logo in it there has to be a way to present t=
his
information to blind users, users with an audio browser, etc. etc. </span><=
o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>One simple fix would be to simply allow for text/plai=
n as
a community logo slot. Alternatively we could encode the information in the
image itself. Alternatively we could specify an extension OID that simply t=
akes
a list of community DNs.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is not a problem for either the subject or the
issuer since there are already </span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>2)
Member Since attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would take a date as a parameter and w=
ould
encode the first date at which the certified entity was issued a credential=
.
The exact interpretation of this would be left to the CPS of the certificat=
e
issuer.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>3)
No Padlock Icon attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would allow a certificate to say that =
no
user indication should be specified in the chrome, nor should any nag scree=
ns.
It would be an option that the issuing CA would put in at their discretion.=
</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>The need for this is to allow a CA to support a wide
range of applications which&nbsp;require encryption but require even less
authentication than current schemes such as domain validated certs. For exa=
mple
self signed certificates, certificates issued to embedded hardware, etc. et=
c.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>What I want to do is to get us to the point where the
browser authors feel comfortable with a user experience that does not conta=
in
the nag screens that disfigure current schemes. In many cases all that is
required is to turn on encryption. The user does not need to be told that t=
he
certificate has expired, has been issued by an unknown CA or any of the usu=
al
nonsense. just don't tell the user that its safe in the first place and the
browser does not need to say that it is dangerous.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>Clearly this attribute is unnecessary from a technica=
l
point of view. From a market point of view it is essential if we are going =
to
ensure that applications are doing the right thing. The padlock icon has so=
me
pretty strong semantics. Many applications require less. We are not going t=
o
get everyone who currently has a padlock certificate to get a green bar cer=
t.
So lets serve the applications that require even less than the padlock with=
out
diluting the padlock semantics further.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Before
writing up a draft I would like to guage whether folk feel there is a need =
for
any of these and if so what the likely level of contention is, whether it c=
an
be completed within PKIX or should it be a personal submission.</span><o:p>=
</o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Main
thing I want here is the reservation of the OIDs under a neutral, non VeriS=
ign
arc. I don't think that the rest of the industry would feel comfortable usi=
ng
VeriSign OIDs and VeriSign might not be comfortable with them doing so eith=
er.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>We
are definitely going to require the first, the second seems to be considere=
d a
'no brainer' since it is information that every CA holds, that is not curre=
ntly
provided to the user and is very very effective at providing security conte=
xt.</span><o:p></o:p></p>

</div>

</div>

</blockquote>

</div>

</div>

</body>

</html>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46AD150DFGRTDANEMSGe_--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54MdAxo035042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 15:39:10 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54MdAX2035041; Mon, 4 Jun 2007 15:39:10 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from colibri.verisign.com (colibri.verisign.com [65.205.251.74]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Md931035026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 15:39:09 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN03.vcorp.ad.vrsn.com (mailer6.verisign.com [65.205.251.33]) by colibri.verisign.com (8.13.1/8.13.4) with ESMTP id l54Md6kY009303; Mon, 4 Jun 2007 15:39:06 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN03.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Jun 2007 15:39:06 -0700
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_01C7A6F9.282F6B7B"
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 15:39:05 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5E5A@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvAABcpHsA==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "Trevor Freeman" <trevorf@exchange.microsoft.com>, <turners@ieca.com>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 22:39:06.0052 (UTC) FILETIME=[28899040:01C7A6F9]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6F9.282F6B7B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Talking to folk it appears that audio is useful but not enough.=20
=20
How do I develop authentication criteria for audio? I am having a =
difficult enough time with images. And it also tips into the language =
issue.
=20
I can't render audio in braille for example. If it is in text or an =
X.500 DN I can render it in any medium I need.
=20
=20


________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Trevor Freeman
	Sent: Monday, June 04, 2007 3:39 PM
	To: turners@ieca.com; Hallam-Baker, Phillip; 'pkix'
	Subject: RE: Three short fixes
=09
=09

	Yes, RFC3709 already supports audio formats which was specifically =
added for accessibility scenarios such as visually impaired users.

	=20

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Turner, Sean P.
	Sent: Monday, June 04, 2007 11:44 AM
	To: 'Hallam-Baker, Phillip'; 'pkix'
	Subject: RE: Three short fixes

	=20

	Phil,

	=20

	For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).

	=20

	spt

	=20

________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
	Sent: Monday, June 04, 2007 1:37 PM
	To: pkix
	Subject: Three short fixes

	Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:

	=20

	1) Text Representation of Community Logos

	=20

	    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20

	=20

	    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.

	=20

	    This is not a problem for either the subject or the issuer since =
there are already=20

	=20

	2) Member Since attribute

	=20

	    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.

	=20

	3) No Padlock Icon attribute

	=20

	    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.

	=20

	    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.

	=20

	    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.

	=20

	    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.

	=20

	=20

	Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.

	=20

	Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.

	=20

	We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A6F9.282F6B7B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:x =3D=20
"urn:schemas-microsoft-com:office:excel" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =3D=20
"urn:schemas-microsoft-com:office:access" xmlns:dt =3D=20
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =3D=20
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =3D=20
"urn:schemas-microsoft-com:rowset" xmlns:z =3D "#RowsetSchema" xmlns:b =
=3D=20
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =3D=20
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =3D=20
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa =3D=20
"urn:schemas-microsoft-com:office:activation" xmlns:html =3D=20
"http://www.w3.org/TR/REC-html40" xmlns:q =3D=20
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D =3D "DAV:" xmlns:x2 =
=3D=20
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =3D=20
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =3D=20
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =3D=20
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =3D=20
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =3D=20
"http://schemas.microsoft.com/data/udc" xmlns:xsd =3D=20
"http://www.w3.org/2001/XMLSchema" xmlns:sps =3D=20
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =3D=20
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf =3D=20
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf =3D=20
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver =3D=20
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
=3D=20
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =3D=20
"http://schemas.openxmlformats.org/package/2006/relationships" =
xmlns:ex12t =3D=20
"http://schemas.microsoft.com/exchange/services/2006/types"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Cambria Math;
}
@font-face {
	font-family: Calibri;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New =
Roman","serif"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle18 {
	COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: =
personal-reply
}
.MsoChpDefault {
	FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
	page: Section1
}
</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 vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Talking to folk it appears that audio is useful =
but not=20
enough. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>How do I develop authentication criteria for =
audio? I am=20
having a difficult enough time with images. And it also tips into the =
language=20
issue.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I can't render audio in braille for example. If =
it is in=20
text or an X.500 DN I can render it in any medium I =
need.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D765402022-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D765402022-04062007></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Trevor=20
  Freeman<BR><B>Sent:</B> Monday, June 04, 2007 3:39 PM<BR><B>To:</B>=20
  turners@ieca.com; Hallam-Baker, Phillip; 'pkix'<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'">Yes,=20
  RFC3709 already supports audio formats which was specifically added =
for=20
  accessibility scenarios such as visually impaired =
users.<o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: =
'Calibri','sans-serif'"><o:p>&nbsp;</o:p></SPAN></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <DIV>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
#b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: =
medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
  owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
  Behalf Of </B>Turner, Sean P.<BR><B>Sent:</B> Monday, June 04, 2007 =
11:44=20
  AM<BR><B>To:</B> 'Hallam-Baker, Phillip'; 'pkix'<BR><B>Subject:</B> =
RE: Three=20
  short fixes<o:p></o:p></SPAN></P></DIV></DIV>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">Phil,</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">For=20
  the logos, can't we just use the logo types RFC (<A=20
  =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Arial','sans-serif'">spt</SPAN><o:p></o:p></P>
  <P class=3DMsoNormal><o:p>&nbsp;</o:p></P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>
  <HR align=3Dcenter width=3D"100%" SIZE=3D2>
  </DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
'Tahoma','sans-serif'">From:</SPAN></B><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">=20
  owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] =
<B>On=20
  Behalf Of </B>Hallam-Baker, Phillip<BR><B>Sent:</B> Monday, June 04, =
2007 1:37=20
  PM<BR><B>To:</B> pkix<BR><B>Subject:</B> Three short=20
  fixes</SPAN><o:p></o:p></P>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Work in =
the w3C Web=20
  Security Context group and elsewhere has prompted me to consider that =
we need=20
  to take the necessary steps to allow the following information to be =
encoded=20
  in certificates in a consistent manner:</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">1) Text=20
  Representation of Community Logos</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
an=20
  accessibility issue. If a certificate is issued with an FDIC community =
logo in=20
  it there has to be a way to present this information to blind users, =
users=20
  with an audio browser, etc. etc. </SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">One =
simple fix=20
  would be to simply allow for text/plain as a community logo slot.=20
  Alternatively we could encode the information in the image itself.=20
  Alternatively we could specify an extension OID that simply takes a =
list of=20
  community DNs.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This is =
not a=20
  problem for either the subject or the issuer since there are already=20
  </SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">2) Member =
Since=20
  attribute</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
  would take a date as a parameter and would encode the first date at =
which the=20
  certified entity was issued a credential. The exact interpretation of =
this=20
  would be left to the CPS of the certificate=20
issuer.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><STRONG><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">3) No =
Padlock Icon=20
  attribute</SPAN></STRONG><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">This =
attribute=20
  would allow a certificate to say that no user indication should be =
specified=20
  in the chrome, nor should any nag screens. It would be an option that =
the=20
  issuing CA would put in at their =
discretion.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">The need =
for this=20
  is to allow a CA to support a wide range of applications =
which&nbsp;require=20
  encryption but require even less authentication than current schemes =
such as=20
  domain validated certs. For example self signed certificates, =
certificates=20
  issued to embedded hardware, etc. etc.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">What I =
want to do=20
  is to get us to the point where the browser authors feel comfortable =
with a=20
  user experience that does not contain the nag screens that disfigure =
current=20
  schemes. In many cases all that is required is to turn on encryption. =
The user=20
  does not need to be told that the certificate has expired, has been =
issued by=20
  an unknown CA or any of the usual nonsense. just don't tell the user =
that its=20
  safe in the first place and the browser does not need to say that it =
is=20
  dangerous.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Clearly =
this=20
  attribute is unnecessary from a technical point of view. From a market =
point=20
  of view it is essential if we are going to ensure that applications =
are doing=20
  the right thing. The padlock icon has some pretty strong semantics. =
Many=20
  applications require less. We are not going to get everyone who =
currently has=20
  a padlock certificate to get a green bar cert. So lets serve the =
applications=20
  that require even less than the padlock without diluting the padlock =
semantics=20
  further.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Before =
writing up a=20
  draft I would like to guage whether folk feel there is a need for any =
of these=20
  and if so what the likely level of contention is, whether it can be =
completed=20
  within PKIX or should it be a personal =
submission.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Main =
thing I want=20
  here is the reservation of the OIDs under a neutral, non VeriSign arc. =
I don't=20
  think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
  and VeriSign might not be comfortable with them doing so=20
  either.</SPAN><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal>&nbsp;<o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">We are =
definitely=20
  going to require the first, the second seems to be considered a 'no =
brainer'=20
  since it is information that every CA holds, that is not currently =
provided to=20
  the user and is very very effective at providing security=20
  =
context.</SPAN><o:p></o:p></P></DIV></DIV></DIV></BLOCKQUOTE></BODY></HTM=
L>

------_=_NextPart_001_01C7A6F9.282F6B7B--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54L1fPB098330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 14:01:41 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54L1fwS098328; Mon, 4 Jun 2007 14:01:41 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from stingray.missi.ncsc.mil (stingray.missi.ncsc.mil [144.51.50.20]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54L1efD098304 for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 14:01:41 -0700 (MST) (envelope-from DPKemp@missi.ncsc.mil)
Received: from Cerberus.missi.ncsc.mil (cerberus.missi.ncsc.mil [144.51.51.8]) by stingray.missi.ncsc.mil with SMTP id l54L1ejZ000285 for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 17:01:40 -0400 (EDT)
Received: from 144.51.60.33 by Cerberus.missi.ncsc.mil (InterScan VirusWall 6); Mon, 04 Jun 2007 17:01:39 -0400
Received: from EXCH.missi.ncsc.mil ([144.51.60.19]) by antigone.missi.ncsc.mil with Microsoft SMTPSVC(6.0.3790.3959); Mon, 4 Jun 2007 17:01:39 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 17:01:39 -0400
Message-ID: <FA998122A677CF4390C1E291BFCF598907851066@EXCH.missi.ncsc.mil>
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgAD2K2g
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
From: "Kemp, David P." <DPKemp@missi.ncsc.mil>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 21:01:39.0986 (UTC) FILETIME=[8C02AF20:01C7A6EB]
X-TM-AS-Product-Ver: : ISVW-6.0.0.1396-3.6.0.1039-15218000
X-TM-AS-Result: : Yes--16.114000-0-31-1
X-TM-AS-Category-Info: : 31:0.000000
X-TM-AS-MatchedID: : =?us-ascii?B?MTQ3MDE1LTE1MDU2Ny03MDcy?= =?us-ascii?B?MDktNzAyNzI2LTcwNzg4Ny03MDE1NzYtNzA0NTY4LTcwMDUzNy03?= =?us-ascii?B?MDUxMDItMTA2NjYwLTcwNDQyNS03MDE4MzctNzAzNDY4LTcxMDYx?= =?us-ascii?B?MS03MDM1NDQtNzAwNzU2LTcwMzc4Mi03MDI0ODUtNzAzMzY2LTcw?= =?us-ascii?B?MjEwNi03MDUzODgtNzAwODY5LTcwOTM3Mi03MDk1ODQtNzAwNzQ5?= =?us-ascii?B?LTcwMDI5OC03MDAwNzMtMTM5NzA0LTcwODE5Ni03MDAzNDItMTEx?= =?us-ascii?B?NjA0LTE4ODExOS03MDYxMTAtNzAwMDE4LTcwMDAwNy03MDAwMTUt?= =?us-ascii?B?NzAwMDE3LTcwMDM2Mi0xODgxNDYtMTg4MTE4LTcwNTcxOC03MDE4?= =?us-ascii?B?MjctNzAwMjY0LTcwMjQ5Ny03MDAzNDUtNzA0MTQxLTcwMDczMi03?= =?us-ascii?B?MDEwMTItNzAwOTA3LTcwMTMwNi03MDI4MzgtNzAwNjIyLTcwMDE2?= =?us-ascii?B?MC0xODgxMjUtMTExNjA1LTcwMDA3NC03MDAxNDItNzAwMDc5LTE4?= =?us-ascii?B?ODEyNC0xMTE2MDgtMTg4MDU3LTE4ODA3OC0xMTE2MDMtMTExNjAx?= =?us-ascii?B?LTE0ODA1MA==?=
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>

This is a multi-part message in MIME format.

------=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A6EB.8BE92584"

------_=_NextPart_001_01C7A6EB.8BE92584
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

1) Text Representation of Community Logos

=20

Although RFC3709 currently has no support for ALT text,
LogotypeImageInfo and LogotypeAudioInfo could easily be modified to
include a text description field after the language field.  Although
audio could be used for visually impaired users, I agree with also
having a text option usable with screenreaders (and Lynx).

=20

2) Member Since attribute

=20

No objections to creating a PKIX OID for this.  Where would it be used -
as a directory attribute for subject alternative name?  A new PKIX
private extension seems like overkill for this purpose.

=20

3) No Padlock Icon attribute

=20

I do not believe PKIX should sponsor an attribute that tells a
certificate user to "ignore this certificate", e.g. "accept this
certificate even if it cannot be validated".  I don't object to
applications supporting unauthenticated encryption while making no
security claims.  But if the application is not going to authenticate an
encryption key, then the application should not be transmitting or
consuming certificates in the first place.  Saying "but TLS won't work
without certificates" is not a convincing argument - the TLS working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not
PKIX.


------_=_NextPart_001_01C7A6EB.8BE92584
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
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 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

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

<div class=3DSection1>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>1) Text Representation of Community =
Logos<o:p></o:p></span></font></b></strong></p>

<p class=3DMsoNormal><strong><b><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></b></strong></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Although RFC3709 currently has no =
support
for ALT text, LogotypeImageInfo and LogotypeAudioInfo could easily be =
modified
to include a text description field after the language field.&nbsp; =
Although audio
could be used for visually impaired users, I agree with also having a =
text
option usable with screenreaders (and =
Lynx).<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>2) Member Since =
attribute<o:p></o:p></span></font></b></strong></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>No objections to creating a PKIX =
OID for
this. &nbsp;Where would it be used &#8211; as a directory attribute for =
subject alternative
name? &nbsp;A new PKIX private extension seems like overkill for this =
purpose.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><strong><b><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'>3) No Padlock Icon =
attribute</span></font></b></strong><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I do not believe PKIX should =
sponsor an
attribute that tells a certificate user to &#8220;ignore this =
certificate&#8221;,
e.g. &#8220;accept this certificate even if it cannot be =
validated&#8221;. &nbsp;I
don&#8217;t object to applications supporting unauthenticated encryption =
while
making no security claims. &nbsp;But if the application is not going to =
authenticate
an encryption key, then the application should not be transmitting or =
consuming
certificates in the first place. &nbsp;Saying &#8220;but TLS won&#8217;t =
work
without certificates&#8221; is not a convincing argument &#8211; the TLS =
working
group has made decisions regarding unauthenticated (and/or unencrypted)
ciphersuites, and the place to revisit those decisions is there, not =
PKIX.<o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------_=_NextPart_001_01C7A6EB.8BE92584--

------=_NextPartTM-000-a4e111a6-eba7-483f-ad24-c7226da58ecb--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JdFBS073286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 12:39:15 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54JdFVg073285; Mon, 4 Jun 2007 12:39:15 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from mail.exchange.microsoft.com (mail7.exchange.microsoft.com [131.107.1.27]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JdDHc073276 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 12:39:14 -0700 (MST) (envelope-from trevorf@exchange.microsoft.com)
Received: from df-bhd-02.exchange.corp.microsoft.com (157.54.71.211) by DF-GWY-07.exchange.corp.microsoft.com (157.54.63.164) with Microsoft SMTP Server (TLS) id 8.1.122.1; Mon, 4 Jun 2007 12:39:13 -0700
Received: from DF-GRTDANE-MSG.exchange.corp.microsoft.com ([157.54.62.10]) by df-bhd-02.exchange.corp.microsoft.com ([157.54.71.211]) with mapi; Mon, 4 Jun 2007 12:39:13 -0700
From: Trevor Freeman <trevorf@exchange.microsoft.com>
To: "turners@ieca.com" <turners@ieca.com>, "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, "'pkix'" <ietf-pkix@imc.org>
Date: Mon, 4 Jun 2007 12:39:06 -0700
Subject: RE: Three short fixes
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAHStvA=
Message-ID: <E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8E@DF-GRTDANE-MSG.exchange.corp.microsoft.com>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com> <00de01c7a6d8$6220c510$0301a8c0@Wylie>
In-Reply-To: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_"
MIME-Version: 1.0
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>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes, RFC3709 already supports audio formats which was specifically added fo=
r accessibility scenarios such as visually impaired users.

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Turner, Sean P.
Sent: Monday, June 04, 2007 11:44 AM
To: 'Hallam-Baker, Phillip'; 'pkix'
Subject: RE: Three short fixes

Phil,

For the logos, can't we just use the logo types RFC (http://ietf.org/rfc/rf=
c3709.txt).

spt

________________________________
From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On=
 Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes
Work in the w3C Web Security Context group and elsewhere has prompted me to=
 consider that we need to take the necessary steps to allow the following i=
nformation to be encoded in certificates in a consistent manner:

1) Text Representation of Community Logos

    This is an accessibility issue. If a certificate is issued with an FDIC=
 community logo in it there has to be a way to present this information to =
blind users, users with an audio browser, etc. etc.

    One simple fix would be to simply allow for text/plain as a community l=
ogo slot. Alternatively we could encode the information in the image itself=
. Alternatively we could specify an extension OID that simply takes a list =
of community DNs.

    This is not a problem for either the subject or the issuer since there =
are already

2) Member Since attribute

    This attribute would take a date as a parameter and would encode the fi=
rst date at which the certified entity was issued a credential. The exact i=
nterpretation of this would be left to the CPS of the certificate issuer.

3) No Padlock Icon attribute

    This attribute would allow a certificate to say that no user indication=
 should be specified in the chrome, nor should any nag screens. It would be=
 an option that the issuing CA would put in at their discretion.

    The need for this is to allow a CA to support a wide range of applicati=
ons which require encryption but require even less authentication than curr=
ent schemes such as domain validated certs. For example self signed certifi=
cates, certificates issued to embedded hardware, etc. etc.

    What I want to do is to get us to the point where the browser authors f=
eel comfortable with a user experience that does not contain the nag screen=
s that disfigure current schemes. In many cases all that is required is to =
turn on encryption. The user does not need to be told that the certificate =
has expired, has been issued by an unknown CA or any of the usual nonsense.=
 just don't tell the user that its safe in the first place and the browser =
does not need to say that it is dangerous.

    Clearly this attribute is unnecessary from a technical point of view. F=
rom a market point of view it is essential if we are going to ensure that a=
pplications are doing the right thing. The padlock icon has some pretty str=
ong semantics. Many applications require less. We are not going to get ever=
yone who currently has a padlock certificate to get a green bar cert. So le=
ts serve the applications that require even less than the padlock without d=
iluting the padlock semantics further.


Before writing up a draft I would like to guage whether folk feel there is =
a need for any of these and if so what the likely level of contention is, w=
hether it can be completed within PKIX or should it be a personal submissio=
n.

Main thing I want here is the reservation of the OIDs under a neutral, non =
VeriSign arc. I don't think that the rest of the industry would feel comfor=
table using VeriSign OIDs and VeriSign might not be comfortable with them d=
oing so either.

We are definitely going to require the first, the second seems to be consid=
ered a 'no brainer' since it is information that every CA holds, that is no=
t currently provided to the user and is very very effective at providing se=
curity context.

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"http://ww=
w.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope=
/" xmlns:D=3D"DAV:" xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2=
003/xml" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xm=
lns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:d=
s=3D"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.micros=
oft.com/sharepoint/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc"=
 xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" xmlns:sps=3D"http://schemas=
.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSch=
ema-instance" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile"=
 xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:=
mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:=
m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http:=
//schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t=3D"htt=
p://schemas.microsoft.com/exchange/services/2006/types" xmlns=3D"http://www=
.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @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;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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'>Yes, RFC3709 already supports audio formats which was specif=
ically
added for accessibility scenarios such as visually impaired users.<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-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<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"'> owner-ietf-pk=
ix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Turner, Sean P.<b=
r>
<b>Sent:</b> Monday, June 04, 2007 11:44 AM<br>
<b>To:</b> 'Hallam-Baker, Phillip'; 'pkix'<br>
<b>Subject:</b> RE: Three short fixes<o:p></o:p></span></p>

</div>

</div>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>Phil,</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>For the logos, can't we just use the logo types RFC (<a
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt</a=
>).</span><o:p></o:p></p>

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

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif";
color:blue'>spt</span><o:p></o:p></p>

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

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D2 width=3D"100%" align=3Dcenter>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><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"'> owner-ietf-pkix@mail.imc.org
[mailto:owner-ietf-pkix@mail.imc.org] <b>On Behalf Of </b>Hallam-Baker, Phi=
llip<br>
<b>Sent:</b> Monday, June 04, 2007 1:37 PM<br>
<b>To:</b> pkix<br>
<b>Subject:</b> Three short fixes</span><o:p></o:p></p>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Work
in the w3C Web Security Context group and elsewhere has prompted me to cons=
ider
that we need to take the necessary steps to allow the following information=
 to
be encoded in certificates in a consistent manner:</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>1)
Text Representation of Community Logos</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is an accessibility issue. If a certificate is
issued with an FDIC community logo in it there has to be a way to present t=
his
information to blind users, users with an audio browser, etc. etc. </span><=
o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>One simple fix would be to simply allow for text/plai=
n as
a community logo slot. Alternatively we could encode the information in the
image itself. Alternatively we could specify an extension OID that simply t=
akes
a list of community DNs.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This is not a problem for either the subject or the
issuer since there are already </span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>2)
Member Since attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would take a date as a parameter and w=
ould
encode the first date at which the certified entity was issued a credential=
.
The exact interpretation of this would be left to the CPS of the certificat=
e
issuer.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><strong><span style=3D'font-size:10.0pt;font-family:"A=
rial","sans-serif"'>3)
No Padlock Icon attribute</span></strong><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>This attribute would allow a certificate to say that =
no
user indication should be specified in the chrome, nor should any nag scree=
ns.
It would be an option that the issuing CA would put in at their discretion.=
</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>The need for this is to allow a CA to support a wide
range of applications which&nbsp;require encryption but require even less
authentication than current schemes such as domain validated certs. For exa=
mple
self signed certificates, certificates issued to embedded hardware, etc. et=
c.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>What I want to do is to get us to the point where the
browser authors feel comfortable with a user experience that does not conta=
in
the nag screens that disfigure current schemes. In many cases all that is
required is to turn on encryption. The user does not need to be told that t=
he
certificate has expired, has been issued by an unknown CA or any of the usu=
al
nonsense. just don't tell the user that its safe in the first place and the
browser does not need to say that it is dangerous.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal>&nbsp;&nbsp;&nbsp; <span style=3D'font-size:10.0pt;fon=
t-family:
"Arial","sans-serif"'>Clearly this attribute is unnecessary from a technica=
l
point of view. From a market point of view it is essential if we are going =
to
ensure that applications are doing the right thing. The padlock icon has so=
me
pretty strong semantics. Many applications require less. We are not going t=
o
get everyone who currently has a padlock certificate to get a green bar cer=
t.
So lets serve the applications that require even less than the padlock with=
out
diluting the padlock semantics further.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Before
writing up a draft I would like to guage whether folk feel there is a need =
for
any of these and if so what the likely level of contention is, whether it c=
an
be completed within PKIX or should it be a personal submission.</span><o:p>=
</o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>Main
thing I want here is the reservation of the OIDs under a neutral, non VeriS=
ign
arc. I don't think that the rest of the industry would feel comfortable usi=
ng
VeriSign OIDs and VeriSign might not be comfortable with them doing so eith=
er.</span><o:p></o:p></p>

</div>

<div>

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

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>We
are definitely going to require the first, the second seems to be considere=
d a
'no brainer' since it is information that every CA holds, that is not curre=
ntly
provided to the user and is very very effective at providing security conte=
xt.</span><o:p></o:p></p>

</div>

</div>

</div>

</body>

</html>

--_000_E1D42DFE30883B488A5BEFC1801FA2DC91D46ACF8EDFGRTDANEMSGe_--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JNiXJ068454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 12:23:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54JNiuh068453; Mon, 4 Jun 2007 12:23:44 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54JNgIV068447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 12:23:43 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l54JNcEF012801; Mon, 4 Jun 2007 12:23:38 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Jun 2007 12:23:38 -0700
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_01C7A6DD.DA444793"
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 12:22:27 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5E0B@MOU1WNEXMB04.vcorp.ad.vrsn.com>
In-Reply-To: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/wAAFTxYA=
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: <turners@ieca.com>, "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 19:23:38.0225 (UTC) FILETIME=[DA352E10:01C7A6DD]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6DD.DA444793
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

No, in case I am not being clear here,
=20
The assumption is that we issue a certificate with the FDIC and Equal =
Opportunity lender LOGOTYPE images as community logos.
=20
Now how do I provide the same information to a non sighted reader? For =
Issuer and Subject logos I just pull the info out of the cert issuer and =
subject. I need a way to express the same info in text as the LOGOTYPE =
contains.


________________________________

	From: Turner, Sean P. [mailto:turners@ieca.com]=20
	Sent: Monday, June 04, 2007 2:44 PM
	To: Hallam-Baker, Phillip; 'pkix'
	Subject: RE: Three short fixes
=09
=09
	Phil,
	=20
	For the logos, can't we just use the logo types RFC =
(http://ietf.org/rfc/rfc3709.txt).
	=20
	spt

________________________________

	From: owner-ietf-pkix@mail.imc.org =
[mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Hallam-Baker, Phillip
	Sent: Monday, June 04, 2007 1:37 PM
	To: pkix
	Subject: Three short fixes
=09
=09
	Work in the w3C Web Security Context group and elsewhere has prompted =
me to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:
	=20
	1) Text Representation of Community Logos
	=20
	    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20
	=20
	    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.
	=20
	    This is not a problem for either the subject or the issuer since =
there are already=20
	=20
	2) Member Since attribute
	=20
	    This attribute would take a date as a parameter and would encode =
the first date at which the certified entity was issued a credential. =
The exact interpretation of this would be left to the CPS of the =
certificate issuer.
	=20
	3) No Padlock Icon attribute
	=20
	    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.
	=20
	    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.
	=20
	    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.
	=20
	    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.
	=20
	=20
	Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.
	=20
	Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.
	=20
	We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.


------_=_NextPart_001_01C7A6DD.DA444793
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>No, in case I am not being clear =
here,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The assumption is that we issue a certificate =
with the FDIC=20
and Equal Opportunity lender LOGOTYPE images as community=20
logos.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D515412019-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Now how do I provide the same information to a =
non sighted=20
reader? For Issuer and Subject logos I just pull the info out of the =
cert issuer=20
and subject. I need a way to express the same info in text as the =
LOGOTYPE=20
contains.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Turner, Sean P.=20
  [mailto:turners@ieca.com] <BR><B>Sent:</B> Monday, June 04, 2007 2:44=20
  PM<BR><B>To:</B> Hallam-Baker, Phillip; 'pkix'<BR><B>Subject:</B> RE: =
Three=20
  short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Phil,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>For the logos, can't we just use the logo =
types RFC (<A=20
  =
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>spt</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org =

  [mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of =
</B>Hallam-Baker,=20
  Phillip<BR><B>Sent:</B> Monday, June 04, 2007 1:37 PM<BR><B>To:</B>=20
  pkix<BR><B>Subject:</B> Three short fixes<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C=20
  Web Security Context group and elsewhere has prompted me to consider =
that we=20
  need to take the necessary steps to allow the following information to =
be=20
  encoded in certificates in a consistent manner:</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
  Representation of Community Logos</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This is an accessibility issue. If a certificate is issued =
with an FDIC=20
  community logo in it there has to be a way to present this information =
to=20
  blind users, users with an audio browser, etc. etc. =
</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
  logo slot. Alternatively we could encode the information in the image =
itself.=20
  Alternatively we could specify an extension OID that simply takes a =
list of=20
  community DNs.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This is not a problem for either the subject or the issuer =
since there=20
  are already </FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
  Since attribute</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This attribute would take a date as a parameter and would =
encode the=20
  first date at which the certified entity was issued a credential. The =
exact=20
  interpretation of this would be left to the CPS of the certificate=20
  issuer.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
  Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>This attribute would allow a certificate to say that no user =
indication=20
  should be specified in the chrome, nor should any nag screens. It =
would be an=20
  option that the issuing CA would put in at their=20
  discretion.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>The need for this is to allow a CA to support a wide range of =

  applications which&nbsp;require encryption but require even less=20
  authentication than current schemes such as domain validated certs. =
For=20
  example self signed certificates, certificates issued to embedded =
hardware,=20
  etc. etc.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>What I want to do is to get us to the point where the browser =
authors=20
  feel comfortable with a user experience that does not contain the nag =
screens=20
  that disfigure current schemes. In many cases all that is required is =
to turn=20
  on encryption. The user does not need to be told that the certificate =
has=20
  expired, has been issued by an unknown CA or any of the usual =
nonsense. just=20
  don't tell the user that its safe in the first place and the browser =
does not=20
  need to say that it is dangerous.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
  size=3D2>Clearly this attribute is unnecessary from a technical point =
of view.=20
  From a market point of view it is essential if we are going to ensure =
that=20
  applications are doing the right thing. The padlock icon has some =
pretty=20
  strong semantics. Many applications require less. We are not going to =
get=20
  everyone who currently has a padlock certificate to get a green bar =
cert. So=20
  lets serve the applications that require even less than the padlock =
without=20
  diluting the padlock semantics further.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2>Before writing up=20
  a draft I would like to guage whether folk feel there is a need for =
any of=20
  these and if so what the likely level of contention is, whether it can =
be=20
  completed within PKIX or should it be a personal=20
  submission.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
  here is the reservation of the OIDs under a neutral, non VeriSign arc. =
I don't=20
  think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
  and VeriSign might not be comfortable with them doing so=20
  either.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We =
are definitely=20
  going to require the first, the second seems to be considered a 'no =
brainer'=20
  since it is information that every CA holds, that is not currently =
provided to=20
  the user and is very very effective at providing security=20
  context.</FONT></SPAN></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7A6DD.DA444793--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54IpH8E058578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 11:51:17 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54IpHUY058577; Mon, 4 Jun 2007 11:51:17 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from smtp108.biz.mail.re2.yahoo.com (smtp108.biz.mail.re2.yahoo.com [206.190.52.47]) by balder-227.proper.com (8.13.5/8.13.5) with SMTP id l54IpGWL058560 for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 11:51:16 -0700 (MST) (envelope-from turners@ieca.com)
Received: (qmail 17244 invoked from network); 4 Jun 2007 18:51:12 -0000
Received: from unknown (HELO Wylie) (turners@ieca.com@70.108.15.46 with login) by smtp108.biz.mail.re2.yahoo.com with SMTP; 4 Jun 2007 18:51:11 -0000
X-YMail-OSG: Qs5z3cUVM1lIPs4KiX._6oDZwIS9hq.C_Z42X_vIIxAiaEmoy8FFT_gjo0i2GpA6YC6RkeMH0Cfl_FH4mSqjXhnERUL4RV9WjNkimTGVz70y9naunfCa4MlbP0oGr_Q4kW5Y7yLfF3JpcBk-
Reply-To: <turners@ieca.com>
From: "Turner, Sean P." <turners@ieca.com>
To: "'Hallam-Baker, Phillip'" <pbaker@verisign.com>, "'pkix'" <ietf-pkix@imc.org>
References: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
Subject: RE: Three short fixes
Date: Mon, 4 Jun 2007 14:44:28 -0400
Organization: IECA, Inc.
Message-ID: <00de01c7a6d8$6220c510$0301a8c0@Wylie>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DF_01C7A6B6.DB0F2510"
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbgACTK/w
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>

This is a multi-part message in MIME format.

------=_NextPart_000_00DF_01C7A6B6.DB0F2510
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Phil,
 
For the logos, can't we just use the logo types RFC
(http://ietf.org/rfc/rfc3709.txt).
 
spt

  _____  

From: owner-ietf-pkix@mail.imc.org [mailto:owner-ietf-pkix@mail.imc.org] On
Behalf Of Hallam-Baker, Phillip
Sent: Monday, June 04, 2007 1:37 PM
To: pkix
Subject: Three short fixes


Work in the w3C Web Security Context group and elsewhere has prompted me to
consider that we need to take the necessary steps to allow the following
information to be encoded in certificates in a consistent manner:
 
1) Text Representation of Community Logos
 
    This is an accessibility issue. If a certificate is issued with an FDIC
community logo in it there has to be a way to present this information to
blind users, users with an audio browser, etc. etc. 
 
    One simple fix would be to simply allow for text/plain as a community
logo slot. Alternatively we could encode the information in the image
itself. Alternatively we could specify an extension OID that simply takes a
list of community DNs.
 
    This is not a problem for either the subject or the issuer since there
are already 
 
2) Member Since attribute
 
    This attribute would take a date as a parameter and would encode the
first date at which the certified entity was issued a credential. The exact
interpretation of this would be left to the CPS of the certificate issuer.
 
3) No Padlock Icon attribute
 
    This attribute would allow a certificate to say that no user indication
should be specified in the chrome, nor should any nag screens. It would be
an option that the issuing CA would put in at their discretion.
 
    The need for this is to allow a CA to support a wide range of
applications which require encryption but require even less authentication
than current schemes such as domain validated certs. For example self signed
certificates, certificates issued to embedded hardware, etc. etc.
 
    What I want to do is to get us to the point where the browser authors
feel comfortable with a user experience that does not contain the nag
screens that disfigure current schemes. In many cases all that is required
is to turn on encryption. The user does not need to be told that the
certificate has expired, has been issued by an unknown CA or any of the
usual nonsense. just don't tell the user that its safe in the first place
and the browser does not need to say that it is dangerous.
 
    Clearly this attribute is unnecessary from a technical point of view.
>From a market point of view it is essential if we are going to ensure that
applications are doing the right thing. The padlock icon has some pretty
strong semantics. Many applications require less. We are not going to get
everyone who currently has a padlock certificate to get a green bar cert. So
lets serve the applications that require even less than the padlock without
diluting the padlock semantics further.
 
 
Before writing up a draft I would like to guage whether folk feel there is a
need for any of these and if so what the likely level of contention is,
whether it can be completed within PKIX or should it be a personal
submission.
 
Main thing I want here is the reservation of the OIDs under a neutral, non
VeriSign arc. I don't think that the rest of the industry would feel
comfortable using VeriSign OIDs and VeriSign might not be comfortable with
them doing so either.
 
We are definitely going to require the first, the second seems to be
considered a 'no brainer' since it is information that every CA holds, that
is not currently provided to the user and is very very effective at
providing security context.

------=_NextPart_000_00DF_01C7A6B6.DB0F2510
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Phil,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>For the logos, can't we just use the logo types =
RFC (<A=20
href=3D"http://ietf.org/rfc/rfc3709.txt">http://ietf.org/rfc/rfc3709.txt<=
/A>).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D343414218-04062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>spt</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> owner-ietf-pkix@mail.imc.org=20
[mailto:owner-ietf-pkix@mail.imc.org] <B>On Behalf Of </B>Hallam-Baker,=20
Phillip<BR><B>Sent:</B> Monday, June 04, 2007 1:37 PM<BR><B>To:</B>=20
pkix<BR><B>Subject:</B> Three short fixes<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C Web=20
Security Context group and elsewhere has prompted me to consider that we =
need to=20
take the necessary steps to allow the following information to be =
encoded in=20
certificates in a consistent manner:</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
Representation of Community Logos</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is an accessibility issue. If a certificate is issued with =
an FDIC=20
community logo in it there has to be a way to present this information =
to blind=20
users, users with an audio browser, etc. etc. </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
logo slot. Alternatively we could encode the information in the image =
itself.=20
Alternatively we could specify an extension OID that simply takes a list =
of=20
community DNs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is not a problem for either the subject or the issuer =
since there=20
are already </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
Since attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would take a date as a parameter and would =
encode the=20
first date at which the certified entity was issued a credential. The =
exact=20
interpretation of this would be left to the CPS of the certificate=20
issuer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would allow a certificate to say that no user =
indication=20
should be specified in the chrome, nor should any nag screens. It would =
be an=20
option that the issuing CA would put in at their =
discretion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>The need for this is to allow a CA to support a wide range of=20
applications which&nbsp;require encryption but require even less =
authentication=20
than current schemes such as domain validated certs. For example self =
signed=20
certificates, certificates issued to embedded hardware, etc.=20
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>What I want to do is to get us to the point where the browser =
authors=20
feel comfortable with a user experience that does not contain the nag =
screens=20
that disfigure current schemes. In many cases all that is required is to =
turn on=20
encryption. The user does not need to be told that the certificate has =
expired,=20
has been issued by an unknown CA or any of the usual nonsense. just =
don't tell=20
the user that its safe in the first place and the browser does not need =
to say=20
that it is dangerous.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>Clearly this attribute is unnecessary from a technical point of =
view.=20
>From a market point of view it is essential if we are going to ensure =
that=20
applications are doing the right thing. The padlock icon has some pretty =
strong=20
semantics. Many applications require less. We are not going to get =
everyone who=20
currently has a padlock certificate to get a green bar cert. So lets =
serve the=20
applications that require even less than the padlock without diluting =
the=20
padlock semantics further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Before =
writing up a=20
draft I would like to guage whether folk feel there is a need for any of =
these=20
and if so what the likely level of contention is, whether it can be =
completed=20
within PKIX or should it be a personal submission.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
here is the reservation of the OIDs under a neutral, non VeriSign arc. I =
don't=20
think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
and VeriSign might not be comfortable with them doing so=20
either.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We are =
definitely=20
going to require the first, the second seems to be considered a 'no =
brainer'=20
since it is information that every CA holds, that is not currently =
provided to=20
the user and is very very effective at providing security=20
context.</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_00DF_01C7A6B6.DB0F2510--




Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Hc5em050124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Jun 2007 10:38:05 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l54Hc5Yf050123; Mon, 4 Jun 2007 10:38:05 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l54Hc4ur050116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 10:38:05 -0700 (MST) (envelope-from pbaker@verisign.com)
Received: from MOU1WNEXCN02.vcorp.ad.vrsn.com (mailer2.verisign.com [65.205.251.35]) by robin.verisign.com (8.13.6/8.13.4) with ESMTP id l54Hc1Zs018120 for <ietf-pkix@imc.org>; Mon, 4 Jun 2007 10:38:03 -0700
Received: from MOU1WNEXMB04.vcorp.ad.vrsn.com ([10.25.13.157]) by MOU1WNEXCN02.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 4 Jun 2007 10:38:01 -0700
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_01C7A6CF.18E753C3"
Subject: Three short fixes
Date: Mon, 4 Jun 2007 10:36:50 -0700
Message-ID: <198A730C2044DE4A96749D13E167AD37012A5DFF@MOU1WNEXMB04.vcorp.ad.vrsn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Three short fixes
Thread-Index: Acemzu8J1FtF9cTgR/K0AnGIU7jXbg==
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "pkix" <ietf-pkix@imc.org>
X-OriginalArrivalTime: 04 Jun 2007 17:38:01.0353 (UTC) FILETIME=[19233F90:01C7A6CF]
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>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A6CF.18E753C3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Work in the w3C Web Security Context group and elsewhere has prompted me =
to consider that we need to take the necessary steps to allow the =
following information to be encoded in certificates in a consistent =
manner:
=20
1) Text Representation of Community Logos
=20
    This is an accessibility issue. If a certificate is issued with an =
FDIC community logo in it there has to be a way to present this =
information to blind users, users with an audio browser, etc. etc.=20
=20
    One simple fix would be to simply allow for text/plain as a =
community logo slot. Alternatively we could encode the information in =
the image itself. Alternatively we could specify an extension OID that =
simply takes a list of community DNs.
=20
    This is not a problem for either the subject or the issuer since =
there are already=20
=20
2) Member Since attribute
=20
    This attribute would take a date as a parameter and would encode the =
first date at which the certified entity was issued a credential. The =
exact interpretation of this would be left to the CPS of the certificate =
issuer.
=20
3) No Padlock Icon attribute
=20
    This attribute would allow a certificate to say that no user =
indication should be specified in the chrome, nor should any nag =
screens. It would be an option that the issuing CA would put in at their =
discretion.
=20
    The need for this is to allow a CA to support a wide range of =
applications which require encryption but require even less =
authentication than current schemes such as domain validated certs. For =
example self signed certificates, certificates issued to embedded =
hardware, etc. etc.
=20
    What I want to do is to get us to the point where the browser =
authors feel comfortable with a user experience that does not contain =
the nag screens that disfigure current schemes. In many cases all that =
is required is to turn on encryption. The user does not need to be told =
that the certificate has expired, has been issued by an unknown CA or =
any of the usual nonsense. just don't tell the user that its safe in the =
first place and the browser does not need to say that it is dangerous.
=20
    Clearly this attribute is unnecessary from a technical point of =
view. From a market point of view it is essential if we are going to =
ensure that applications are doing the right thing. The padlock icon has =
some pretty strong semantics. Many applications require less. We are not =
going to get everyone who currently has a padlock certificate to get a =
green bar cert. So lets serve the applications that require even less =
than the padlock without diluting the padlock semantics further.
=20
=20
Before writing up a draft I would like to guage whether folk feel there =
is a need for any of these and if so what the likely level of contention =
is, whether it can be completed within PKIX or should it be a personal =
submission.
=20
Main thing I want here is the reservation of the OIDs under a neutral, =
non VeriSign arc. I don't think that the rest of the industry would feel =
comfortable using VeriSign OIDs and VeriSign might not be comfortable =
with them doing so either.
=20
We are definitely going to require the first, the second seems to be =
considered a 'no brainer' since it is information that every CA holds, =
that is not currently provided to the user and is very very effective at =
providing security context.

------_=_NextPart_001_01C7A6CF.18E753C3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Work =
in the w3C Web=20
Security Context group and elsewhere has prompted me to consider that we =
need to=20
take the necessary steps to allow the following information to be =
encoded in=20
certificates in a consistent manner:</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>1) Text=20
Representation of Community Logos</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is an accessibility issue. If a certificate is issued with =
an FDIC=20
community logo in it there has to be a way to present this information =
to blind=20
users, users with an audio browser, etc. etc. </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>One simple fix would be to simply allow for text/plain as a =
community=20
logo slot. Alternatively we could encode the information in the image =
itself.=20
Alternatively we could specify an extension OID that simply takes a list =
of=20
community DNs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This is not a problem for either the subject or the issuer =
since there=20
are already </FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>2) Member=20
Since attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would take a date as a parameter and would =
encode the=20
first date at which the certified entity was issued a credential. The =
exact=20
interpretation of this would be left to the CPS of the certificate=20
issuer.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial =
size=3D2><STRONG>3) No=20
Padlock Icon attribute</STRONG></FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>This attribute would allow a certificate to say that no user =
indication=20
should be specified in the chrome, nor should any nag screens. It would =
be an=20
option that the issuing CA would put in at their =
discretion.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>The need for this is to allow a CA to support a wide range of=20
applications which&nbsp;require encryption but require even less =
authentication=20
than current schemes such as domain validated certs. For example self =
signed=20
certificates, certificates issued to embedded hardware, etc.=20
etc.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>What I want to do is to get us to the point where the browser =
authors=20
feel comfortable with a user experience that does not contain the nag =
screens=20
that disfigure current schemes. In many cases all that is required is to =
turn on=20
encryption. The user does not need to be told that the certificate has =
expired,=20
has been issued by an unknown CA or any of the usual nonsense. just =
don't tell=20
the user that its safe in the first place and the browser does not need =
to say=20
that it is dangerous.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007>&nbsp;&nbsp;&nbsp; <FONT =
face=3DArial=20
size=3D2>Clearly this attribute is unnecessary from a technical point of =
view.=20
>From a market point of view it is essential if we are going to ensure =
that=20
applications are doing the right thing. The padlock icon has some pretty =
strong=20
semantics. Many applications require less. We are not going to get =
everyone who=20
currently has a padlock certificate to get a green bar cert. So lets =
serve the=20
applications that require even less than the padlock without diluting =
the=20
padlock semantics further.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Before =
writing up a=20
draft I would like to guage whether folk feel there is a need for any of =
these=20
and if so what the likely level of contention is, whether it can be =
completed=20
within PKIX or should it be a personal submission.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>Main =
thing I want=20
here is the reservation of the OIDs under a neutral, non VeriSign arc. I =
don't=20
think that the rest of the industry would feel comfortable using =
VeriSign OIDs=20
and VeriSign might not be comfortable with them doing so=20
either.</FONT></SPAN></DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D000471817-04062007><FONT face=3DArial size=3D2>We are =
definitely=20
going to require the first, the second seems to be considered a 'no =
brainer'=20
since it is information that every CA holds, that is not currently =
provided to=20
the user and is very very effective at providing security=20
context.</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C7A6CF.18E753C3--


