<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">The new 9.2.2 clause prohibits this.
You can't choose to follow either 9.2.1 or 9.2.2.<br>
<br>
And I personally approve all the proposed changes.<br>
<br>
<pre class="moz-signature" cols="72">--
Erwann ABALEA
</pre>
Le 20/11/2012 11:47, Janssen, M.A. (Mark) - Logius a écrit :<br>
</div>
<blockquote
cite="mid:5790F2B51C0F71488E5678317966D0E712312034@SSO608259.frd.shsdir.nl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:Verdana}
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
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.BallontekstChar
{font-family:"Tahoma","sans-serif"}
p.line862, li.line862, div.line862
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.line874, li.line874, div.line874
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.line867, li.line867, div.line867
{margin-right:0cm;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.apple-style-span
{}
span.anchor
{}
span.E-mailStijl25
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.E-mailStijl26
{font-family:"Calibri","sans-serif";
color:#1F497D}
p.BalloonText, li.BalloonText, div.BalloonText
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.E-mailStijl30
{font-family:"Verdana","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
{}
-->
</style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US">So, do I understand it correctly
that an OV cert which includes a Reserved IP Address or an
Internal Server Name in the Subject Common Name Field is not
prohibited? If so this should be made clear in the ballot. </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US">Thanks.
</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US">Best Regards,<br>
<br>
<b>Mark Janssen</b><br>
Senior Advisor PKIoverheid<br>
........................................................................<br>
</span><b><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-GB">Logius<br>
The ministry of the Interior and Kingdom Relations (BZK)</span></b><span
style="font-size:9.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-GB"><br>
</span><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-GB">Wilhelmina van Pruisenweg 52 |
2595 AN | The Hague<br>
P.O. Box 96810 | 2509 JE | The Hague<br>
........................................................................<br>
</span><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US">T +31(0) 70 8887 967<br>
F +31(0) 70 8887 882<br>
</span><span style="font-size:9.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D"><a moz-do-not-send="true"
href="mailto:mark.janssen@logius.nl" target="_blank"
title="mailto:mark.janssen@logius.nl"><span
style="font-size:7.5pt" lang="EN-US">mark.janssen@logius.nl</span></a></span><span
style="font-size:9.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US"><br>
</span><span style="font-size:9.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="FR"><a moz-do-not-send="true"
href="https://webmail.ictu.nl/exchweb/bin/redir.asp?URL=http://www.logius.nl/"
target="_blank"
title="https://webmail.ictu.nl/exchweb/bin/redir.asp?URL=http://www.logius.nl/"><span
style="font-size:7.5pt">http://www.logius.nl/</span></a></span><span
style="font-size:9.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US"><br>
</span><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US">........................................................................<br>
<b>Service e-government</b><br>
........................................................................</span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;
font-family:"Verdana","sans-serif";
color:green" lang="EN-GB">Please consider the environment
- do you really need to print this mail?</span><span
style="color:#1F497D" lang="EN-US"></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;
font-family:"Verdana","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt;
padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;
font-family:"Tahoma","sans-serif"">Van:</span></b><span
style="font-size:10.0pt;
font-family:"Tahoma","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a>
[<a class="moz-txt-link-freetext" href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>]
<b>Namens </b>Jeremy Rowley<br>
<b>Verzonden:</b> donderdag 15 november 2012 23:27<br>
<b>Aan:</b> <a class="moz-txt-link-abbreviated" href="mailto:richard.smith@comodo.com">richard.smith@comodo.com</a>; 'Steve Roylance';
<a class="moz-txt-link-abbreviated" href="mailto:public@cabforum.org">public@cabforum.org</a><br>
<b>Onderwerp:</b> Re: [cabfpub] Ballot 92 - Subject
Alternative Names</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US">The reason is the same as the
rest of the changes in this ballot. Relying parties should
have some information about the entity behind a
certificate. With internal servers names, there isn’t a
link between a validated domain and a specific entity. With
a DV certificate, this problem is exasperated since the
relying party has absolutely no information about the
certificate holder of an internal name certificate (a DV
certificate containing only mail.server contains no
independently verified information) This change ensures
that all certificates are tied to some verified information.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US">Jeremy</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt;
padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;
font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;
font-family:"Tahoma","sans-serif""
lang="EN-US">
<a moz-do-not-send="true"
href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a>
[<a moz-do-not-send="true"
href="mailto:public-bounces@cabforum.org">mailto:public-bounces@cabforum.org</a>]
<b>On Behalf Of </b>Rich Smith<br>
<b>Sent:</b> Thursday, November 15, 2012 2:52 PM<br>
<b>To:</b> 'Steve Roylance'; <a moz-do-not-send="true"
href="mailto:public@cabforum.org">public@cabforum.org</a><br>
<b>Subject:</b> Re: [cabfpub] Ballot 92 - Subject
Alternative Names</span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US">Since many clients and servers
will still choke on a cert with no Common Name. Prohibiting
Reserved IPs and Internal host names in the CN field
effectively prohibits single site certificates for Reserved
IPs and internal names. What's the reasoning behind this?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:#1F497D" lang="EN-US"> </span></p>
<div style="border:none; border-left:solid blue 1.5pt;
padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt;
padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;
font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;
font-family:"Tahoma","sans-serif""
lang="EN-US">
<a moz-do-not-send="true"
href="mailto:public-bounces@cabforum.org">public-bounces@cabforum.org</a>
<a moz-do-not-send="true"
href="mailto:[mailto:public-bounces@cabforum.org]">
[mailto:public-bounces@cabforum.org]</a> <b>On
Behalf Of </b>Steve Roylance<br>
<b>Sent:</b> Thursday, November 15, 2012 12:28 PM<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:public@cabforum.org">public@cabforum.org</a>;
CABForum Management<br>
<b>Subject:</b> [cabfpub] Ballot 92 - Subject
Alternative Names</span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"><a moz-do-not-send="true"
href="https://www.cabforum.org/wiki/92%20-%20Subject%20Alternative%20Names">https://www.cabforum.org/wiki/92%20-%20Subject%20Alternative%20Names</a></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> </span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span
style="font-size:13.5pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Steve Roylance of
GlobalSign made the following motion and Yngve
Pettersen of Opera and Jeremy Rowley of Digicert
have endorsed it:</span></span><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"></span></p>
</div>
<div>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">... Motion begins...</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Effective on the 1st July
2013</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">... Erratum begins ...</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">The following sections
will be amended in the Baseline Requirements
document.</span></p>
<p class="line867"><strong><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">INSERT</span></strong><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> in Section 4. Definitions
the following:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Public IP Address: An IP
Address that is not a Reserved IP Address.</span></p>
<p class="line867"><strong><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">REPLACE</span></strong><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> Section 9.2.1 (Subject
Alternative Name Extension) with the following:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">9.2.1 Subject Alternative
Name Extension</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Certificate Field:
extensions:subjectAltName</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Required/Optional:
Required</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Contents: This extension
MUST contain at least one entry that is either a
Fully-Qualified Domain Name or Public IP Address.
Each subjectAltName entry MUST either be a Domain
Name or an IP Address. The CA MUST confirm the
Applicant’s control of each dNSName or Public IP
Address entry in accordance with Section 11.1.</span></p>
<p class="line867"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">SubjectAltName entries MAY
include domain Names containing wildcard characters.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">If the subjectAltName is:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">1) a Public IP Address,</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">2) a Registered Domain
Name that has a Domain Name Registrant different
than (and not an Affiliate of) the Domain Name
Registrant of any other Registered Domain Name in
the subjectAltName extension in the Certificate, or</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">3) a Reserved IP Address
or Internal Server Name.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">then the CA MUST verify
the identity of an entity that controls the private
key in accordance with Section 11.2 and include the
Subject Identity Information in the issued
Certificate in accordance with 9.2.4. The CA MAY
include explanatory information in the Subject
Organizational Unit field or a non-subject
certificate field to clarify the Subject Identity
Information included in the Certificate.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Prior to issuing a
Certificate containing an Internal Server Name or
Reserved IP Address, the CA SHALL notify the
Applicant that the use of such Certificates has been
deprecated by the CA / Browser Forum and that the
practice will be eliminated by October 2016. As of
the Effective Date, the CA SHALL NOT issue a
certificate with an Expiry Date later than 1
November 2015 if the subjectAlternativeName contains
a Reserved IP Address or Internal Server Name.
Effective 1 October 2016, CAs SHALL revoke all
unexpired Certificates whose subjectAlternativeName
extension or Subject commonName field contains a
Reserved IP Address or Internal Server Name.</span></p>
<p class="line867"><strong><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">REPLACE</span></strong><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> Section 9.2.2 (Subject
Common Name Field) with the following:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">9.2.2 Subject Common Name
Field</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Certificate Field:
subject:commonName (OID 2.5.4.3)</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Required/Optional:
Deprecated (Discouraged, but not prohibited)</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Contents: If present, this
field MUST contain a single Public IP address or
single Fully-Qualified Domain Name that is one of
the values contained in the Certificate’s
subjectAltName extension (see Section 9.2.1).
Reserved IP Addresses and Internal Server Names are
prohibited.</span></p>
<p class="line867"><strong><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">REPLACE</span></strong><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> Section 10.2.3
(Information Requirements) with the following:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">10.2.3 Information
Requirements</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">The certificate request
MAY include all factual information about the
Applicant to be included in the Certificate, and
such additional information as is necessary for the
CA to obtain from the Applicant in order to comply
with these Requirements and the CA’s Certificate
Policy and/or Certification Practice Statement. In
cases where the certificate request does not contain
all the necessary information about the Applicant,
the CA SHALL obtain the remaining information from
the Applicant or, having obtained it from a
reliable, independent, third-party data source,
confirm it with the Applicant.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Applicant information MUST
include, but not be limited to, at least one Subject
Alternative Name as defined in Section 9.2.1.</span></p>
<p class="line867"><strong><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">INSERT</span></strong><span
style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US"> in Section 11.1
(Authorization by Domain Name Registrant) the
following two new sections:</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">11.1.3 Wildcard Domain
Validation</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Before issuing a
certificate with a wildcard character (*) in a CN or
subjectAltName of type DNS-ID, the CA MUST establish
and follow a documented procedure† that determines
if the wildcard character occurs in the first label
position to the left of a “registry-controlled”
label or “public suffix” (e.g. “*.com”, “*.co.uk”,
see RFC 6454 Section 8.2 for further
explanation). If a wildcard would fall within the
label immediately to the left of a
registry-controlled† or public suffix, CAs SHALL
refuse issuance unless the applicant proves its
rightful control of the entire Domain Namespace.
(e.g. CAs SHALL NOT issue “*.co.uk”, but MAY issue
“*.example.co.uk” to Example Ltd.)</span></p>
<p class="line862"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">†Determination of what is
“registry-controlled” versus the registerable
portion of a Country Code Top-Level Domain Namespace
is not standardized at the time of writing and is
not a property of the DNS itself. Current best
practice is to consult a “public suffix list” such
as <a moz-do-not-send="true"
href="http://publicsuffix.org/"><span
style="color:#0044B3; border:none windowtext
1.0pt; padding:0cm; text-decoration:none">http://publicsuffix.org/</span></a>.
If the process for making this determination is
standardized by an RFC, then such a procedure SHOULD
be preferred.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">... Erratum ends ...</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">The review period for this
ballot shall commence at 21:00 UTC on 15 November
2012 and will close at 21:00 UTC on 22 November
2012. Unless the motion is withdrawn during the
review period, the voting period will start
immediately thereafter and will close at 21:00 UTC
on 29 November 2012. Votes must be cast by posting
an on-list reply to this thread.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">... Motions ends ...</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">A vote in favor of the
motion must indicate a clear 'yes' in the response.</span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">A vote against must
indicate a clear 'no' in the response. A vote to
abstain must indicate a clear 'abstain' in the
response. Unclear responses will not be counted. The
latest vote received from any representative of a
voting member before the close of the voting period
will be counted.</span></p>
<p class="line862"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">Voting members are listed
here: <a moz-do-not-send="true"
href="http://www.cabforum.org/forum.html"><span
style="color:#0044B3; border:none windowtext
1.0pt; padding:0cm; text-decoration:none">http://www.cabforum.org/forum.html</span></a></span></p>
<p class="line874"><span style="font-size:9.0pt;
font-family:"Arial","sans-serif";
color:black" lang="EN-US">In order for the motion to
be adopted, two thirds or more of the votes cast by
members in the CA category and one half or more of
the votes cast by members in the browser category
must be in favor. Also, at least six members must
participate in the ballot, either by voting in
favor, voting against or abstaining.</span></p>
</div>
</div>
</div>
</div>
</div>
<br>
<hr>
<font color="Gray" face="Arial" size="1"><br>
Dit bericht kan informatie bevatten die niet voor u is bestemd.
Indien u niet de geadresseerde bent of dit bericht abusievelijk
aan u is toegezonden, wordt u verzocht dat aan de afzender te
melden en het bericht te verwijderen. De Staat aanvaardt geen
aansprakelijkheid voor schade, van welke aard ook, die verband
houdt met risico's verbonden aan het elektronisch verzenden van
berichten.<br>
This message may contain information that is not intended for
you. If you are not the addressee or if this message was sent to
you by mistake, you are requested to inform the sender and
delete the message. The State accepts no liability for damage of
any kind resulting from the risks inherent in the electronic
transmission of messages. .<br>
</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Public@cabforum.org">Public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a>
</pre>
</blockquote>
<br>
</body>
</html>