To: Sam Whited <sam@samwhited.com>
Cc: precis@ietf.org
References: <150024725625.303.17137036571104960991@ietfa.amsl.com>
 <33f7468c-6742-7cbe-fa6f-70002c35cc62@stpeter.im>
 <CAHbk4RLa5AZp+sKUMoVOE2VsUmaDKGdWBqoTvurU_o=rj_OM0g@mail.gmail.com>
 <1504880015.1561911.1099626960.6CB0430C@webmail.messagingengine.com>
 <bd11bb2f-81a7-4081-ed49-15fa0fcb117c@stpeter.im>
 <1505397979.578298.1106052760.03A5025F@webmail.messagingengine.com>
 <0fc31e75-7893-c982-30b4-a6fe4ecae5fb@stpeter.im>
 <1505675616.1686212.1109016016.7A9E7FFE@webmail.messagingengine.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <a50d8f06-2a2e-5062-5a9d-ace5b718090c@stpeter.im>
Date: Sun, 17 Sep 2017 14:41:35 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <1505675616.1686212.1109016016.7A9E7FFE@webmail.messagingengine.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="E38OCo06oekMu7qTxNs77veNC5ABqSuV1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/precis/MUVaiv-9UNOVQl9m4uGhJXZaXek>
Subject: Re: [precis] I-D Action: draft-ietf-precis-7564bis-09.txt
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--E38OCo06oekMu7qTxNs77veNC5ABqSuV1
Content-Type: multipart/mixed; boundary="NEahEn14sfsd3jHPUB4X1uX4jW8GJQa6U";
 protected-headers="v1"
From: Peter Saint-Andre <stpeter@stpeter.im>
To: Sam Whited <sam@samwhited.com>
Cc: precis@ietf.org
Message-ID: <a50d8f06-2a2e-5062-5a9d-ace5b718090c@stpeter.im>
Subject: Re: [precis] I-D Action: draft-ietf-precis-7564bis-09.txt
References: <150024725625.303.17137036571104960991@ietfa.amsl.com>
 <33f7468c-6742-7cbe-fa6f-70002c35cc62@stpeter.im>
 <CAHbk4RLa5AZp+sKUMoVOE2VsUmaDKGdWBqoTvurU_o=rj_OM0g@mail.gmail.com>
 <1504880015.1561911.1099626960.6CB0430C@webmail.messagingengine.com>
 <bd11bb2f-81a7-4081-ed49-15fa0fcb117c@stpeter.im>
 <1505397979.578298.1106052760.03A5025F@webmail.messagingengine.com>
 <0fc31e75-7893-c982-30b4-a6fe4ecae5fb@stpeter.im>
 <1505675616.1686212.1109016016.7A9E7FFE@webmail.messagingengine.com>
In-Reply-To: <1505675616.1686212.1109016016.7A9E7FFE@webmail.messagingengine.com>

--NEahEn14sfsd3jHPUB4X1uX4jW8GJQa6U
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 9/17/17 1:13 PM, Sam Whited wrote:
> On Thu, Sep 14, 2017, at 21:04, Peter Saint-Andre wrote:
>> What needs fixing? We added explanatory text about idempotence, and
>> there will also be an example of such in the RFC version.
>=20
> That is not enough. Someone writing a PRECIS implementation *might* see=

> that. Someone actually using the PRECIS implementation (eg. the author
> of an XMPP Client, Spotify, etc.) will most likely not see that. If
> they're lucky, the text will have been copied over into the
> implementations documentation. That's a lot of "if's".

Why would an application need to care about this? This is an internal
implementation detail of a PRECIS library/API, and IMHO it would be
irresponsible of the library/API author to offer an option for
application developers to select how many times to apply the rules.

>> Please note that these documents are now in AUTH48 (very final edits
>> before publication). So speak now or forever hold your peace!
>=20
> I brought this up earlier as well. I wanted to bring it up again becaus=
e
> the Nickname profile is getting so close to being published again with
> something that I think is possibly a security concern and that needs to=

> be fixed since we won't have this opportunity again.

Sam, I am going to reiterate that we are EXTREMELY close to publication
of this document - it could have happened on, say, Thursday morning
right before you posted to the list about this. Please please please
either propose very specific text or point to an earlier email message
where you did so, because personally I have forgotten if you already did
that and my recollection from the previous discussion was that you did
not raise objections to the compromise text that Bill Fisher and I
agreed on. If your proposal is that we make significant changes to the
document at this time, then the Working Group chair or Area Director
will likely have to suggest a path forward, because your feedback is
coming so very late in the process.

Peter



--NEahEn14sfsd3jHPUB4X1uX4jW8GJQa6U--

--E38OCo06oekMu7qTxNs77veNC5ABqSuV1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJZvt4AAAoJEOoGpJErxa2pS4YP/RlZb3IWfSFuPvALb3FxGQAk
V9b/6J3xUk90xmOl2w0qQOT6b3MQEMKmK54kk1VFZCINk7L3OtaPbTpx4TY4QjV3
ltmBw6GdpQ/ARNjuXrYj3pf54mCT4tbAdw+UC7iSufjdzFRKnLrsnQVJx/oNHrzM
iZBdbTywywMiw9BkiyeZtLgtDvi2JrBmuwohfUKeNdh/vxOytoXhAvOcSDX1ZKXJ
+jf5fX9WNamxRFJ+32+21QMiC3SMzypjpJODNWwhFicuAJLGje3crUXgZG9YVAc+
sHLzXbEhtOxVx0p2uhKSuNzuArlYeQilywbWiddXTULNUK1vSfbyuK+DHh1lmEiS
m7lK3Tx5tUiuhGe7bWnyUci03flOTkVrCB+ZfVK0pAu4trd8X9jpMbShtWzGB01N
ioTDstntcbG0mF/tDLg3penX2kSNVUuRGPsUIt08SJpQUf/N/Ef6WrApq/kn0zj9
QJiHROkprjlNlEJxCQv5/z5CklU5iaMI06jbvXPODaVm4AdC/mU/HTGm9b8WDOxD
kqBPPLp+nVuROKzbV28lDO2vXLZhm7Do4C+E3v9dGorbIn7+namt4uLaoWQb2SiK
bDCQAAmZKh9EaP+zW4zYMo6Be9TZLfhrjMKoP5ljgyN1epRrbhPvgQ71K2DrYRSn
gLC99ydt+Frrrz3HUXwp
=h4l1
-----END PGP SIGNATURE-----

--E38OCo06oekMu7qTxNs77veNC5ABqSuV1--