Return-Path: <rogaglia@cisco.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
 with ESMTP id C0ED121F84D9 for <sidr@ietfa.amsl.com>;
 Tue,  3 Jan 2012 03:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No,
 score=-5.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glp1F6qK8fyb for
 <sidr@ietfa.amsl.com>; Tue,  3 Jan 2012 03:23:54 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78])
 by ietfa.amsl.com (Postfix) with ESMTP id 6087021F84D2 for <sidr@ietf.org>;
 Tue,  3 Jan 2012 03:23:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com;
 i=rogaglia@cisco.com; l=48342; q=dns/txt; s=iport; t=1325589834; x=1326799434;
 h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version;
 bh=/fvkySAe3tQYYiwp9sg13EWE6+prnNNamH/KwgDFb9w=;
 b=Oaa0CoYCgpQZsLqgKV9KzOC90gVStMEg9AK+0rmCyf5FJPXOHmWa6xIA
 1RpW1QRP8MCtQJpbi5mu7jiCfj7arQyHE57koU038PkINoDBe+vCi1MaM
 mI2pXKYvZKZNj0a6jI3xkrV+W7pgMJTjniBLhpeYQyeoPhtXTKbFw2Za5 w=; 
X-Files: smime.p7s : 4389
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAQAMDkAk+tJV2d/2dsb2JhbABEggWqW4EFgXIBAQEDAQEBAQ8BB1QGBQULAgEIEQMBAiEBDQIlCx0IAgQOBQ4Uh1gIln8BnV4EiyxjBI4mgReFRZI0
X-IronPort-AV: E=Sophos; i="4.71,449,1320624000"; d="p7s'?scan'208,217";
 a="48276699"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by
 rcdn-iport-7.cisco.com with ESMTP; 03 Jan 2012 11:23:53 +0000
Received: from xht-rcd-x01-p.cisco.com (xht-rcd-x01-p.cisco.com
 [173.37.178.212]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id
 q03BNrE9021732; Tue, 3 Jan 2012 11:23:53 GMT
Received: from xmb-rcd-x01-p.cisco.com ([169.254.3.213]) by
 xht-rcd-x01-p.cisco.com ([173.37.178.212]) with mapi id 14.01.0339.001;
 Tue, 3 Jan 2012 03:23:53 -0800
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Danny McPherson <danny@tcb.net>
Thread-Topic: [sidr] I-D Action: draft-ietf-sidr-algorithm-agility-04.txt
Thread-Index: AQHMwWLFjG4EG3bWq0+mtC6Ddbyq5ZX7F6cA
Date: Tue, 3 Jan 2012 11:23:52 +0000
Message-ID: <61AE0027-3FF1-4FBB-B1F0-E9552004009D@cisco.com>
References: <0E9A31B3-0BAF-4942-AAC6-486BCF17394B@tcb.net>
 <42DEE995-AE41-46EA-A21E-CDFAD31A6401@cisco.com>
In-Reply-To: <42DEE995-AE41-46EA-A21E-CDFAD31A6401@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [173.37.178.200]
x-tm-as-product-ver: SMEX-10.0.0.4211-6.800.1017-18622.006
x-tm-as-result: No--63.635300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/signed; boundary="Apple-Mail-75--609720550";
 protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] I-D Action: draft-ietf-sidr-algorithm-agility-04.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>,
 <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>,
 <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2012 11:23:56 -0000

--Apple-Mail-75--609720550
Content-Type: multipart/alternative;
	boundary=Apple-Mail-74--609724217


--Apple-Mail-74--609724217
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> From: Danny McPherson <danny@tcb.net>
> Date: December 23, 2011 6:15:54 AM GMT+01:00
> To: <sidr@ietf.org>
> Subject: Re: [sidr] I-D Action: =
draft-ietf-sidr-algorithm-agility-04.txt
>=20
>=20
> I've reviewed the -04 version of the draft and have the following=20
> comments (most of which persist from the previous version of the=20
> draft, although many were accommodated - thanks).
>>=20
>=20

Danny, I want to thank you for your second throughout review. You spot =
some new problems with the old and new text.

Please see comments inline.

Roque

>> -danny
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Substantial:
>>=20
>> ---
>> S 4.4 (&& S 4.6):
>>=20
>> I remain concerned that independent publication points for=20
>> product sets for different algorithms are not a mandatory=20
>> requirement.  Is there any reason why, for example, this is a=20
>> SHOULD rather than a MUST:
>>=20
>> "Suite B product SHOULD be stored at independent publication=20
>> points"
>>=20
>> It's precisely the assumptions this introduces in S 4.4 that=20
>> makes me think independent publication points must be a hard=20
>> requirement (i.e., MUST).
>=20
(Roque) Having a SHOULD was discuss a while ago when checking pro a cons =
of a complete separation from a separation based on the information in =
the manifest. The complete separation was preferred but a separation =
based on the information in the different manifests while sharing the =
same publication points was not ruled out. =20

>=20
>> S 4.6 on same issue:
>>=20
>>   "Since the Suite B products SHOULD be published at distinct=20
>>   publication points, RPs that cannot process Suite B products=20
>>   can be expected to revert to the Suite A products that still =
exist."
>>=20
>> This text to me still assumes interdependence between=20
>> independent publication points, even after you explicitly=20
>> stated that an algorithm that validates under either object=20
>> (which technically, they're independent anyway) should be
>> considered valid.  It lends itself to the thought that an RP=20
>> should prolly maintain both suites until EOL, which isn't=20
>> necessarily the suggestion, methinks.
>=20
(Roque) This new piece of the text is part of a paragraph on how to stop =
the transition process at this stage. In the previous paragraph it is =
clearly stated that "failure" is defined by local policies. So, at this =
stage all product MUST be using both algorithm suites, the RP can decide =
to use local policies such as:=20
		- validate both repositories and stay with the union of =
the validated objects
		- validate only B and  under certain conditions of =
number of total valid/invalid objects validate A
An RP can decide to continue validating A until EOL. The only policy for =
RP that we are requesting is that it MUST be validating Algorithm B at =
Twilight and that it MUST stop validating Algorithm C after EOL.

>=20
>>=20
>> ---
>> S 4.4:
>>=20
>>   "If the Suite B algorithm is deemed unsuitable, the algorithm
>>   transition timeline and the algorithm specification documents MUST =
be
>>   replaced.  CAs MUST cease accepting requests for certificates under
>>   Suite B, and Suite B certificates that have been issued MUST be
>>   revoked."
>>=20
>> I know this is in the Phase 1 section, but it may be worth iterating=20=

>> here that this is only possible in these early phases of the =
transition.
>=20

(Roque) The "cancelation" text changes in every phase. I rather not =
clarify that this text should be read in the correspondent section.... =
:-)

>> ---
>> S 4.5:
>>=20
>>   "An RP that validates all signed product sets using both Algorithm
>>   Suite A or Algorithm Suite B, SHOULD expect the same results.
>>   However, an object that validates using either Algorithm Suite A or
>>   Algorithm Suite B MUST be considered valid.  A detailed analysis on
>>   the validation of multiple instance of signed objects is included =
in
>>   Section 6."
>>=20

(Roque) I guess you are referring here to the SHOULD to be changed for =
MUST. See above.

>=20
>=20
>> ---
>> S 4.6:
>>=20
>>   "Phase 3 starts at the RP Ready Algorithm B Date.  During this =
phase,
>>   all signed product sets are available using both algorithm suites =
and
>>   all RPs MUST be able to validate them using either suite.  An =
object
>>   that validates using either Algorithm Suite A or Algorithm Suite B
>>   MUST be considered valid.  It is RECOMMENDED that, in preparation =
for
>>   Phase 4, RPs utilize Suite B as the first and preferred option for
>>   validation throughout this phase.  Thus, for example, an RP SHOULD
>>   try to validate the sets of signed products retrieved from the
>>   Algorithm Suite B repository first.  If this effort fails (relative
>>   to the local validation policy), the RP SHOULD revert to using the
>>   Algorithm Suite A repository."
>>=20
>> Given that the two algorithm suite product sets are independent and=20=

>> use different publication points there may be a place where "all =
signed
>> product sets" are NOT available using both algorithm suites, no?  =
Else
>> what if they aren't what would you do anyway?   Phase 6 says there
>> must be parity as well, particularly during Phase 2 & 3, and it's not =
really
>> the case is it?  It's a darn good idea, but that's a different issue.
>>=20
>=20

(Roque) At this phase the CA MUST use both algorithm suites. The RP have =
to chose their local policies. As mentioned before, an RP may decide =
that it want to continue validating using the two suites until EOL, but =
that is not required.

>=20
>=20
>> ---
>> S 4.7:=20
>>=20
>> I don't know what this text is aiming to accomplish (i.e., where else
>> would they be published)?
>>=20
>>   "All signed products sets issued using Suite A MUST be published=20
>>   at their corresponding publication points, but signed products sets=20=

>>   issued using Suite C MAY be published at their corresponding=20
>>   publication points."
>=20

(Roque) s/MAY/MAY NOT

So, you MAY create the Suite C products (i.e. provisioning protocol =
support) and you MAY publish them.

>> ---
>> S 4.7:
>>=20
>> My previous concerns persist here:
>>=20
>>   "Also, every RP MUST validate signed product sets using Suite A=20
>>   but also MAY validate signed product sets using Suite C. However,=20=

>>   RPs SHOULD NOT assume the Suite C repository is complete."
>>=20
>> If RPs do this and you've got Suite A that validates and Suite C that=20=

>> does not then what is the behavior?  It really has to be just as in =
earlier
>> phases, where valid in either is valid, period, no?  That's why I =
don't=20
>> like this collision probability we're introducing. =20
>>=20
>=20

(Roque) The sentence only says that if you decide to validate a product =
set using Suite C and that product validates, it is valid. But you =
should not consider that the Suite C repository is complete. I do not =
see the collision.

>=20
>> ---
>> S 6:
>>=20
>> Where do we say that both "instances" of such products MUST=20
>> contain the same resources (and what's an "instance")?  I don't see=20=

>> this requirement earlier in the draft and it seems a REALLY bad=20
>> requirement to be - they MUST be independent:
>=20
>=20

(Roque)=20
This text is on the first paragraph:
"In this section, we describe the RP behavior when validating instances =
of the same signed product but signed with different algorithm suites."

We use also the definition of two different files for the same object:
"During Phase 1 two (corresponding) files for an object MAY be available =
for each signed product, one signed under Algorithm Suite A and one =
under Algorithm Suite B."

The idea of "same signed product" includes the resources, when relevant =
to this object. We kept the text more general as there are a variety of =
signed objects.

>>=20
>> "Because both instances of such products MUST contain the same=20
>> resources, relying on either instance will yield the same outcome."
>>=20
>> For example, this text in the following section itself is in conflict
>> with the S 6 requirement:
>>=20
>> "As the algorithm migration process mandates the maintenance of=20
>> two parallel certificate hierarchies, revocations requests for each
>> algorithm suite MUST be handled independently.  A Child CA=20
>> MUST request revocation of a certificate relative to a specific=20
>> algorithm suite."
>=20

(Roque) I do not see the conflict.

>=20
>>=20
>> ---
>> S 7:
>>=20
>> I don't understand this revocation requirement, the hierarchies are=20=

>> independent and it'd seem perfectly reasonable to revoke something
>> in one hierarchy and not in the other:
>>=20
>> "During phase 2 and phase 3, the two parallel certificate hierarchies
>> are designed to carry identical information.  Consequently, a child
>> CA requesting the revocation of a certificate during these two phases
>> MUST perform that request for both algorithm suites (A and B).  A
>> non-leaf CA is NOT required to verify that its child CAs comply with
>> this requirement."
>=20

(Roque) If the child CA does not do that, your CA stops complying with =
the requirement that MUST publish all objects using both algorithm =
suites.=20
However, you raised the point that we need to add an exception for key =
roll-overs as we are mentioning in the following section that the =
processes are independent.



>=20
>> ---
>> S 11:
>>=20
>> This text is also in conflict with earlier requirements of absolute =
parity=20
>> across the two independent hierarchies (e.g., CRLs in both, etc..):
>>=20
>> "If a CA does not complete its migration to the new algorithm suite =
as
>> described in this document (after the EOL of the "old" algorithm
>> suite), its signed product set will no longer be valid.  =
Consequently,=20
>> the RPKI may, at the end of Phase 4, have a smaller number of valid=20=

>> signed products than before starting the process."
>>=20
>=20
(Roque) That is exactly what we are saying. If a CA does not comply with =
the process, there is a risk of ending up with a smaller RPKI. IF the CA =
complies with the process, this will not happen.

>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Nits:
>>=20
>> ---
>> S 2:
>>=20
>> This seems a bit redundant:
>>=20
>> "This document does not specify any algorithm suite.  This document=20=

>> does not specify any algorithm suite per se."
>=20

(Roque) ok.

>=20
>> ---
>> S 3:
>>=20
>> Technically, all are changing algorithms suites in this document,=20
>> why are you just indicating this for CA Y?
>>=20
>>   CA X        The CA that issued CA Y's certificate (i.e., CA Y's
>>               parent), used in examples in this document.
>>=20
>>   CA Y        The CA that is changing keys and/or algorithm suites,
>>               used in examples this document
>>=20
>>   CA Z        A CA that is a "child" of CA Y, used in examples this
>>               document
>=20
(Roque) ok.

>> ---
>> S 3:
>>=20
>> I think linking in this "unilateral" re-issuance function and =
employing
>> the term you've defined here would be of benefit (e.g., in S 4.1):
>=20

(Roque) Can you provide the text?

>=20
>>=20
>>   Certificate re-issuance (unilateral)  A CA MAY reissue a =
certificate
>>               to a subordinate Subject without the involvement of the
>>               Subject.  The public key, resource extensions, and most
>>               other fields are copied from the current Subject
>>               certificate into the next Subject certificate.  The
>>               Issuer name MAY change, if necessary to reflect the
>>               Subject name in the CA certificate under which the
>>               reissued certificate will be validated.  The validity
>>               interval also MAY be changed.  This action is defined =
as
>>               a unilateral certificate re-issuance.
>>=20
>> ---
>> S 3:=20
>>=20
>> s/conventions use in examples/conventions used in examples/
>=20
(Roque) ok.
>=20
>>=20
>> ---
>> S 4.1:
>>=20
>> s/have re-issued all of its signed/have reissued all of their signed/
>>=20
>>   "CA Go Algorithm B Date  - After this date, all (non-leaf) CAs MUST
>>               have re-issued all of its signed product set under the
>>               Algorithm B suite."
>>=20
>=20
(Roque) ok.
>=20
>> ---
>> S 4.2:
>>=20
>> s/certificate.(X.509/certificate.  (X.509/
>=20
(Roque) ok
>=20
>>=20
>> s/RPs might be ready/RPs might not be ready/ ?

(Roque) ok

>>=20
>>   "For example, many CAs might not prepared to issue signed
>>    products under Suite B, or many RPs might be ready to process=20
>>   Suite B product sets."
>>=20
>> ---
>> S 4.4:
>>=20
>> s/since Suite B product SHOULD/since Suite B product sets SHOULD/
>>=20
>=20
(Roque) ok.
>=20
>> ---
>> S 4.5:
>>=20
>> s/each signed product sets MUST/each signed product set MUST/
>>=20
>> s/Section 4.2../Section 4.2./
>>=20
>> s/Suite B, SHOULD/Suite B SHOULD/
>>=20
>> s/multiple instance of signed objects/multiple instances of signed =
objects/
>=20
(Roque) ok.
>=20
>>=20
>> ---
>> S 4.7:
>>=20
>> "old Suite A"?  Isn't that now "Algorithm Suite C" by definition?
>> You do nearly the same thing in S 4.8 as well, but you add a =
qualifier:
>>=20
>> "Suite C (old Suite A)"
>>=20
>=20

(Roque) Good catch, one reference is enough.=20

>=20
>> ---
>>=20
>>=20
>>=20
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>=20


--Apple-Mail-74--609724217
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>From: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">Danny McPherson &lt;<a =
href=3D"mailto:danny@tcb.net">danny@tcb.net</a>&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">December 23, 2011 =
6:15:54 AM GMT+01:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;<a =
href=3D"mailto:sidr@ietf.org">sidr@ietf.org</a>&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>Re: [sidr] I-D =
Action: =
draft-ietf-sidr-algorithm-agility-04.txt</b><br></span></div><br><div><br>=
I've reviewed the -04 version of the draft and have the following =
<br>comments (most of which persist from the previous version of the =
<br>draft, although many were accommodated - =
thanks).<br></div></blockquote></div></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div><br></div></blockquote><div><br></div><div></div></div>=
</div></div></blockquote><br><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div>Danny, I want to thank you for your second throughout =
review. You spot some new problems with the old and new =
text.</div><div><br></div><div>Please see comments =
inline.</div><div><br></div><div>Roque</div><br></div></div></div><blockqu=
ote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><blockquote =
type=3D"cite"><div>-danny<br><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<br>Substantial:<br><br>---<br>S 4.4 (&amp;&amp; =
S 4.6):<br><br>I remain concerned that independent publication points =
for <br>product sets for different algorithms are not a mandatory =
<br>requirement. &nbsp;Is there any reason why, for example, this is a =
<br>SHOULD rather than a MUST:<br><br>"Suite B product SHOULD be stored =
at independent publication <br>points"<br><br>It's precisely the =
assumptions this introduces in S 4.4 that <br>makes me think independent =
publication points must be a hard <br>requirement (i.e., =
MUST).<br></div></blockquote><div><br></div></div></div></div></blockquote=
><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) Having a =
SHOULD was discuss a while ago when checking pro a cons of a complete =
separation from a separation based on the information in the manifest. =
The complete separation was preferred but a separation based on the =
information in the different manifests while sharing the same =
publication points was not ruled out. =
&nbsp;</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><blockquote type=3D"cite"><div>S 4.6 on same =
issue:<br><br> &nbsp;&nbsp;"Since the Suite B products SHOULD be =
published at distinct <br> &nbsp;&nbsp;publication points, RPs that =
cannot process Suite B products <br> &nbsp;&nbsp;can be expected to =
revert to the Suite A products that still exist."<br><br>This text to me =
still assumes interdependence between <br>independent publication =
points, even after you explicitly <br>stated that an algorithm that =
validates under either object <br>(which technically, they're =
independent anyway) should be<br>considered valid. &nbsp;It lends itself =
to the thought that an RP <br>should prolly maintain both suites until =
EOL, which isn't <br>necessarily the suggestion, =
methinks.<br></div></blockquote><div><br></div><div></div></div></div></di=
v></blockquote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div><div>(Roque) =
This new piece of the text is part of a paragraph on how to stop the =
transition process at this stage. In the previous paragraph it is =
clearly stated that "failure" is defined by local policies. So, at this =
stage all product MUST be using both algorithm suites, the RP can decide =
to use local policies such as:&nbsp;</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">		=
</span>-&nbsp;validate both repositories and stay with the union of the =
validated objects</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>- validate only B and =
&nbsp;under certain conditions of number of total valid/invalid =
objects&nbsp;validate A</div><div>An RP can decide to continue =
validating A until EOL. The only policy for RP that we are requesting is =
that it MUST be validating Algorithm B at Twilight&nbsp;and that it MUST =
stop validating Algorithm C after =
EOL.</div></div></div></div><br><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div><div><div><br></div><blockquote type=3D"cite"><div><br>---<br>S =
4.4:<br><br> &nbsp;&nbsp;"If the Suite B algorithm is deemed unsuitable, =
the algorithm<br> &nbsp;&nbsp;transition timeline and the algorithm =
specification documents MUST be<br> &nbsp;&nbsp;replaced. &nbsp;CAs MUST =
cease accepting requests for certificates under<br> &nbsp;&nbsp;Suite B, =
and Suite B certificates that have been issued MUST be<br> =
&nbsp;&nbsp;revoked."<br><br>I know this is in the Phase 1 section, but =
it may be worth iterating <br>here that this is only possible in these =
early phases of the =
transition.<br></div></blockquote><div><br></div><div></div></div></div></=
div></blockquote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) The "cancelation" text changes =
in every phase. I rather not clarify that this text should be read in =
the correspondent section.... :-)</div><br></div></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div>---<br>S 4.5:<br><br> &nbsp;&nbsp;"An RP that =
validates all signed product sets using both Algorithm<br> =
&nbsp;&nbsp;Suite A or Algorithm Suite B, SHOULD expect the same =
results.<br> &nbsp;&nbsp;However, an object that validates using either =
Algorithm Suite A or<br> &nbsp;&nbsp;Algorithm Suite B MUST be =
considered valid. &nbsp;A detailed analysis on<br> &nbsp;&nbsp;the =
validation of multiple instance of signed objects is included in<br> =
&nbsp;&nbsp;Section =
6."<br><br></div></blockquote><div></div></div></div></div></blockquote><b=
r><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) I guess =
you are referring here to the SHOULD to be changed for MUST. See =
above.</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><br><blockquote type=3D"cite"><div>---<br>S =
4.6:<br><br> &nbsp;&nbsp;"Phase 3 starts at the RP Ready Algorithm B =
Date. &nbsp;During this phase,<br> &nbsp;&nbsp;all signed product sets =
are available using both algorithm suites and<br> &nbsp;&nbsp;all RPs =
MUST be able to validate them using either suite. &nbsp;An object<br> =
&nbsp;&nbsp;that validates using either Algorithm Suite A or Algorithm =
Suite B<br> &nbsp;&nbsp;MUST be considered valid. &nbsp;It is =
RECOMMENDED that, in preparation for<br> &nbsp;&nbsp;Phase 4, RPs =
utilize Suite B as the first and preferred option for<br> =
&nbsp;&nbsp;validation throughout this phase. &nbsp;Thus, for example, =
an RP SHOULD<br> &nbsp;&nbsp;try to validate the sets of signed products =
retrieved from the<br> &nbsp;&nbsp;Algorithm Suite B repository first. =
&nbsp;If this effort fails (relative<br> &nbsp;&nbsp;to the local =
validation policy), the RP SHOULD revert to using the<br> =
&nbsp;&nbsp;Algorithm Suite A repository."<br><br>Given that the two =
algorithm suite product sets are independent and <br>use different =
publication points there may be a place where "all signed<br>product =
sets" are NOT available using both algorithm suites, no? =
&nbsp;Else<br>what if they aren't what would you do anyway? =
&nbsp;&nbsp;Phase 6 says there<br>must be parity as well, particularly =
during Phase 2 &amp; 3, and it's not really<br>the case is it? =
&nbsp;It's a darn good idea, but that's a different =
issue.<br><br></div></blockquote><div><br></div></div></div></div></blockq=
uote><br><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) At this =
phase the CA MUST use both algorithm suites. The RP have to chose their =
local policies. As mentioned before, an RP may decide that it want to =
continue validating using the two suites until EOL, but that is not =
required.</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><br><blockquote type=3D"cite"><div>---<br>S =
4.7: <br><br>I don't know what this text is aiming to accomplish (i.e., =
where else<br>would they be published)?<br><br> &nbsp;&nbsp;"All signed =
products sets issued using Suite A MUST be published <br> &nbsp;&nbsp;at =
their corresponding publication points, but signed products sets <br> =
&nbsp;&nbsp;issued using Suite C MAY be published at their corresponding =
<br> &nbsp;&nbsp;publication =
points."<br></div></blockquote><div><br></div><div></div></div></div></div=
></blockquote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) s/MAY/MAY =
NOT</div><div><br></div><div>So, you MAY create the Suite C products =
(i.e. provisioning protocol support) and you MAY publish =
them.</div><br></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div>---<br>S 4.7:<br><br>My previous concerns persist =
here:<br><br> &nbsp;&nbsp;"Also, every RP MUST validate signed product =
sets using Suite A <br> &nbsp;&nbsp;but also MAY validate signed product =
sets using Suite C. However, <br> &nbsp;&nbsp;RPs SHOULD NOT assume the =
Suite C repository is complete."<br><br>If RPs do this and you've got =
Suite A that validates and Suite C that <br>does not then what is the =
behavior? &nbsp;It really has to be just as in earlier<br>phases, where =
valid in either is valid, period, no? &nbsp;That's why I don't <br>like =
this collision probability we're introducing. =
&nbsp;<br><br></div></blockquote><div><br></div></div></div></div></blockq=
uote><br><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) The =
sentence only says that if you decide to validate a product set using =
Suite C and that product validates, it is valid. But you should not =
consider that the Suite C repository is complete. I do not see the =
collision.</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote type=3D"cite"><div>---<br>S 6:<br><br>Where =
do we say that both "instances" of such products MUST <br>contain the =
same resources (and what's an "instance")? &nbsp;I don't see <br>this =
requirement earlier in the draft and it seems a REALLY bad =
<br>requirement to be - they MUST be =
independent:<br></div></blockquote><div><br></div><div><br></div><div></di=
v></div></div></div></blockquote><br><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div><div>(Roque)&nbsp;</div><div>This text is =
on the first paragraph:</div><div>"<span class=3D"Apple-style-span" =
style=3D"white-space: pre; ">In this section, we describe the RP =
behavior</span><span class=3D"Apple-style-span" style=3D"white-space: =
pre; "> when validating instances of the same signed product but signed =
with</span><span class=3D"Apple-style-span" style=3D"white-space: pre; =
"> different algorithm suites."</span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre; =
"><br></span></div><div><span class=3D"Apple-style-span" =
style=3D"white-space: pre; ">We use also the definition of two different =
files for the same object:</span></div><div><span =
class=3D"Apple-style-span" style=3D"white-space: pre; ">"</span><span =
class=3D"Apple-style-span" style=3D"white-space: pre; ">During Phase 1 =
two (corresponding) files for an object MAY be </span><span =
class=3D"Apple-style-span" style=3D"white-space: pre; ">available for =
each signed product, one signed under Algorithm Suite A</span><span =
class=3D"Apple-style-span" style=3D"white-space: pre; "> and one under =
Algorithm Suite B."</span></div><div><br></div><div><div>The idea of =
"same signed product" includes the resources, when relevant to this =
object. We kept the text more general as there are a variety of signed =
objects.</div></div><br></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div><br>"Because both instances of such products MUST =
contain the same <br> resources, relying on either instance will yield =
the same outcome."<br><br>For example, this text in the following =
section itself is in conflict<br>with the S 6 requirement:<br><br>"As =
the algorithm migration process mandates the maintenance of <br>two =
parallel certificate hierarchies, revocations requests for =
each<br>algorithm suite MUST be handled independently. &nbsp;A Child CA =
<br>MUST request revocation of a certificate relative to a specific =
<br>algorithm =
suite."<br></div></blockquote><div><br></div></div></div></div></blockquot=
e><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) I do not see the =
conflict.</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote type=3D"cite"><div><br>---<br>S 7:<br><br>I =
don't understand this revocation requirement, the hierarchies are =
<br>independent and it'd seem perfectly reasonable to revoke =
something<br>in one hierarchy and not in the other:<br><br>"During phase =
2 and phase 3, the two parallel certificate hierarchies<br>are designed =
to carry identical information. &nbsp;Consequently, a child<br>CA =
requesting the revocation of a certificate during these two =
phases<br>MUST perform that request for both algorithm suites (A and B). =
&nbsp;A<br>non-leaf CA is NOT required to verify that its child CAs =
comply with<br>this =
requirement."<br></div></blockquote><div><br></div><div></div></div></div>=
</div></blockquote><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) If the child CA does not do =
that, your CA stops complying with the requirement that MUST publish all =
objects using both algorithm suites.&nbsp;</div><div>However, you raised =
the point that we need to add an exception for key roll-overs as we are =
mentioning in the following section that the processes are =
independent.</div></div></div><div><br></div><div><br></div><div><br></div=
></div><blockquote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote type=3D"cite"><div>---<br>S 11:<br><br>This =
text is also in conflict with earlier requirements of absolute parity =
<br>across the two independent hierarchies (e.g., CRLs in both, =
etc..):<br><br>"If a CA does not complete its migration to the new =
algorithm suite as<br>described in this document (after the EOL of the =
"old" algorithm<br>suite), its signed product set will no longer be =
valid. &nbsp;Consequently, <br>the RPKI may, at the end of Phase 4, have =
a smaller number of valid <br>signed products than before starting the =
process."<br><br></div></blockquote><div><br></div><div></div></div></div>=
</div></blockquote><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div>(Roque) That is exactly what we are saying. If a CA =
does not comply with the process, there is a risk of ending up with a =
smaller RPKI. IF the CA complies with the process, this will not =
happen.</div><br></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>Nits:<br><br>---<br>S 2:<br><br>This seems a bit =
redundant:<br><br>"This document does not specify any algorithm suite. =
&nbsp;This document <br>does not specify any algorithm suite per =
se."<br></div></blockquote><div><br></div></div></div></div></blockquote><=
br><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>(Roque) =
ok.<br></div></div><div><br></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div>---<br>S 3:<br><br>Technically, all are changing =
algorithms suites in this document, <br>why are you just indicating this =
for CA Y?<br><br> &nbsp;&nbsp;CA X =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The CA that issued CA Y's =
certificate (i.e., CA Y's<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;parent), used in examples in this document.<br><br> =
&nbsp;&nbsp;CA Y &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The CA that =
is changing keys and/or algorithm suites,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;used in examples this document<br><br> &nbsp;&nbsp;CA Z =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A CA that is a "child" of CA =
Y, used in examples this<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;document<br></div></blockquote><div><br></div><div></div></div><=
/div></div></blockquote><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div><div>(Roque) ok.</div><br></div></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div>---<br>S 3:<br><br>I think linking in this =
"unilateral" re-issuance function and employing<br>the term you've =
defined here would be of benefit (e.g., in S =
4.1):<br></div></blockquote><div><br></div></div></div></div></blockquote>=
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) Can you provide the =
text?</div></div></div><div><br></div></div><blockquote type=3D"cite"><div=
 style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div><br> &nbsp;&nbsp;Certificate re-issuance (unilateral) =
&nbsp;A CA MAY reissue a certificate<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;to a subordinate Subject without the involvement of the<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Subject. &nbsp;The public key, resource extensions, and =
most<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;other fields are copied from the current Subject<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;certificate into the next Subject certificate. &nbsp;The<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Issuer name MAY change, if necessary to reflect the<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Subject name in the CA certificate under which the<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;reissued certificate will be validated. &nbsp;The validity<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;interval also MAY be changed. &nbsp;This action is defined =
as<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;a unilateral certificate re-issuance.<br><br>---<br>S 3: =
<br><br>s/conventions use in examples/conventions used in =
examples/<br></div></blockquote><div><br></div></div></div></div></blockqu=
ote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) =
ok.</div></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div><br>---<br>S 4.1:<br><br>s/have re-issued all of its =
signed/have reissued all of their signed/<br><br> &nbsp;&nbsp;"CA Go =
Algorithm B Date &nbsp;- After this date, all (non-leaf) CAs MUST<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;have re-issued all of its signed product set under the<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;Algorithm B =
suite."<br><br></div></blockquote><div><br></div></div></div></div></block=
quote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) =
ok.</div></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div>---<br>S =
4.2:<br><br>s/certificate.(X.509/certificate. =
&nbsp;(X.509/<br></div></blockquote><div><br></div></div></div></div></blo=
ckquote><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) =
ok</div></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div><br>s/RPs might be ready/RPs might not be ready/ =
?<br></div></blockquote><div></div></div></div></div></blockquote><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) =
ok</div><br></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><blockquote =
type=3D"cite"><div><br> &nbsp;&nbsp;"For example, many CAs might not =
prepared to issue signed<br> &nbsp;&nbsp;&nbsp;products under Suite B, =
or many RPs might be ready to process <br> &nbsp;&nbsp;Suite B product =
sets."<br><br>---<br>S 4.4:<br><br>s/since Suite B product SHOULD/since =
Suite B product sets =
SHOULD/<br><br></div></blockquote><br></div></div></div></blockquote><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) =
ok.</div></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div>---<br>S 4.5:<br><br>s/each signed product sets =
MUST/each signed product set MUST/<br><br>s/Section 4.2../Section =
4.2./<br><br>s/Suite B, SHOULD/Suite B SHOULD/<br><br>s/multiple =
instance of signed objects/multiple instances of signed =
objects/<br></div></blockquote><div><br></div></div></div></div></blockquo=
te><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><div>(Roque) =
ok.</div></div></div></div><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div><br><blockquote =
type=3D"cite"><div><br>---<br>S 4.7:<br><br>"old Suite A"? &nbsp;Isn't =
that now "Algorithm Suite C" by =
definition?</div></blockquote><blockquote type=3D"cite"><div>You do =
nearly the same thing in S 4.8 as well, but you add a =
qualifier:<br><br>"Suite C (old Suite =
A)"<br><br></div></blockquote><div><br></div></div></div></div></blockquot=
e><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
"><div><div><div><br></div><div>(Roque) Good catch, one reference is =
enough.&nbsp;</div></div></div><div><br></div></div><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote =
type=3D"cite"><div>---<br><br><br><br>____________________________________=
___________<br>sidr mailing list<br><a =
href=3D"mailto:sidr@ietf.org">sidr@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/sidr">https://www.ietf.org/m=
ailman/listinfo/sidr</a><br></div></blockquote></div><br></div></div></blo=
ckquote></div><br></body></html>=

--Apple-Mail-74--609724217--

--Apple-Mail-75--609720550
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMXDCCBWYw
ggROoAMCAQICEFyqcUyRFrhvN5s0SHw/EO4wDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTA1MTAwMDAwMDBaFw0x
MjA1MTEyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRcwFQYDVQQDFA5Sb3F1ZSBHYWdsaWFubzEhMB8GCSqGSIb3DQEJARYScm9nYWdsaWFAY2lz
Y28uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxIp28SUiJ/fiFYD/Nct8MUbG
WJuPqSnhkfBYMFbbWfDDrHR8OXzK2LkWIuHY5aeAo1nalAQCO40oeTYt0cp9W++a7USNCEDQzgVN
Rg0YMYL27YSQoVJnecO3u9wi0jjwhJGblWWxphaztdaMbqiChgND1PHqf7dcs4UjeUOhhKFk0/61
mTmduV721jrxj6ABIlUHAc7nXhKANtDbKdBZzEhM4dbzp6STKq65EQ3xRLVFIuapTgNVckvXtc1e
Cyu4xLOLZgaD2aLq9JzBn9y/rFRMtf2euP/Nmzl7QRjAUjpPdo1n6NXWGDtNyR0lUrcJ/x1leccZ
Gfj0eaqe+tpJmQIDAQABo4HoMIHlMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwFAYKYIZIAYb4RQEGBwQGFgROb25lMFAG
A1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9pbmRjMWRpZ2l0YWxpZC1nMy1jcmwudmVyaXNpZ24uY29t
L0luZEMxRGlnaXRhbElELUczLmNybDANBgkqhkiG9w0BAQUFAAOCAQEAsvqKrlga/tU0vyBtnBOj
4miDAZxou0/fN2wVEK7dRLzIQLYEJD35sELVhiP8v8wVHtgOeVHz9FyBEVqXmJ0RKy4kMC7gdQxj
+t1MlqSTDShEaPMmiwaK6M1iJ9jpBL4JvoiirpHnQYGukkgvTUeqITWZ5ecg03nB3QHuab91Gc+n
RZ1OKL4D4p5IkvzWhRlIAlxW9yGZyB8r9V6iu3+1SYEpPPUN3AYCxXeXrn8fJjkOoEodybRiGyfW
pMpShpTZg2tHB7ZX162Ti3sRvwA2mktDMnBtEm1pXo15z7yieDUPmjVybMA4byV7AQcbIrjQj0eq
c/biBsueC2KWoJY7TDCCBu4wggXWoAMCAQICEHEVZgVK5JEhTem8RPms09wwDQYJKoZIhvcNAQEF
BQAwgcoxCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVy
aVNpZ24gVHJ1c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBG
b3IgYXV0aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMg
UHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTA5MDUwMTAwMDAwMFoXDTE5
MDQzMDIzNTk1OVowgd0xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0G
A1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIg
Q0EgLSBHMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAO3ER98qKB18Bmu71yEyyWwT
j+mxjUFONPfaC+Nq+mWIIAsRE+mb4ElOi2/VAdBfDUeRilpMdD4/xpEJu0w0no1uoYJRYvdpdliW
B6+eFBgHT1q9n9IxslQZc0ZqGUIR7BJzIY313DDN5dlWCjHFNm0pFJe9LdqJRxmI2EsEPeu2PGce
dAATDdCG2pNn+DMDrho8a2l49sAsjuGDP3f5mf/+n1JawrSHCthsqUfBVCllQz5KwJYfwa33d69s
sQRevsG2lC2XkC0n0rse6YNqhPbEsq4jBmUmpSdYKwcitG+mYkgad/LVUCeaKdOW+yj1uiR2YuOM
Wev7btVCxL5Bx/UCAwEAAaOCArkwggK1MDQGCCsGAQUFBwEBBCgwJjAkBggrBgEFBQcwAYYYaHR0
cDovL29jc3AudmVyaXNpZ24uY29tMBIGA1UdEwEB/wQIMAYBAf8CAQAwcAYDVR0gBGkwZzBlBgtg
hkgBhvhFAQcXATBWMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vY3BzMCoG
CCsGAQUFBwICMB4aHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEwNAYDVR0fBC0wKzApoCeg
JYYjaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS1nMy5jcmwwDgYDVR0PAQH/BAQDAgEGMG4G
CCsGAQUFBwEMBGIwYKFeoFwwWjBYMFYWCWltYWdlL2dpZjAhMB8wBwYFKw4DAhoEFEtruSiWBgy7
0FI4mymsSweLIQUYMCYWJGh0dHA6Ly9sb2dvLnZlcmlzaWduLmNvbS92c2xvZ28xLmdpZjAuBgNV
HREEJzAlpCMwITEfMB0GA1UEAxMWUHJpdmF0ZUxhYmVsNC0yMDQ4LTExODAdBgNVHQ4EFgQUeUdh
CEH9OASiS+e1zPVD9kkrEfgwgfEGA1UdIwSB6TCB5qGB0KSBzTCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzOCEQCLW3VWhFSFCwDPrzhIzrGkMA0GCSqGSIb3DQEBBQUAA4IBAQA5Tc9B
mYG1qQW1UjjpOYSJbOQ0qFrn2GwJTCQaulmkhztzIfGTgc+/aGNaZ/41hSuhw12jSsI6Gd0w1sxN
7/HSgZfKVFpDvzeLeo4ZjQ9DqIzyr2CzFYqzlZw84J6zJ5ikNXIX5fwqXYfTig3C0UUq+MD0rCqT
OtWuEnAI6/s74nfs6CtkNXbNutrg0csU1nFYm77VPn222egkxSRmTF2RH3azFz5/DcYhiS+zN7ih
/1yybUneZVJC+w6I0u1KHb9L4/jMcvpIDmWOScjW+JmYO7eUPjFxBof6bFlTLtffK+1fYwCsFe0D
uFUWjMZoA+ciqHMLsbyg2lJY3QoOf8GCMYIEizCCBIcCAQEwgfIwgd0xCzAJBgNVBAYTAlVTMRcw
FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazE7
MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEgKGMp
MDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24gQ2xh
c3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQXKpxTJEWuG83mzRIfD8Q7jAJBgUr
DgMCGgUAoIICbTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjAx
MDMxMTIzNTBaMCMGCSqGSIb3DQEJBDEWBBQ99Rc4YQdCSSbIP06P+kS9+jrmxTCCAQMGCSsGAQQB
gjcQBDGB9TCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBcqnFMkRa4bzebNEh8PxDuMIIBBQYLKoZIhvcNAQkQAgsxgfWggfIwgd0xCzAJBgNV
BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3Qg
TmV0d29yazE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNv
bS9ycGEgKGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVy
aVNpZ24gQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMwIQXKpxTJEWuG83mzRI
fD8Q7jANBgkqhkiG9w0BAQEFAASCAQBg8ZXaYz54S4GlDH38ruAZ9bhtKFb8orOIFWf3chrxYzEA
edE0nQc98D3Y85fmTrVX4Or5wr9yFW6QKcRf9mlxkTg6eGfj0RoQFzQhaok1n+VTM0lWgcVgzoqs
GE7XAK4H60MwrUjU3z9JCbHFirbEm1jB62RqOnxJPOrzsukSLg86trtrlN80D6cYfVnNI1pRq0NJ
tUJPYqYkf+9TK8U8jnNRHoUUZl074kQZqQhFgHIQ5chCyOWurjvYI99Ou2peJQBvR1uL1x5dW8iY
vbmlDm9BU9jzZj/VAdbAJD0jeW5NnpI4/D0H8Ox+KABC320TnglrWBBuj3fKxFHi3Yf/AAAAAAAA

--Apple-Mail-75--609720550--
