[saag] Re: draft update on discussion on crypto practices at IETF

Paul Wouters <[email protected]> wrote:
    > Paul Hoffman has helped me restructure and clarify the draft I had written
    > about crypto practices at the IETF. We used a different draft name because
    > diffing the old and new would make little sense due to the changes.

    > Hopefully this brings the draft in line with the comments received on the
    > list and the last two saag meetings.

    > https://datatracker.ietf.org/doc/html/draft-paulwh-crypto-components

Seems like a good document: it is certainly accurate about how things have
gone.  

May I suggest that in the sections 3.1,3.2 and 3.3 that some examples be
added?  I think that the SecSH method of [email protected] is useful.
Is there an example of a 256-entry registry?  
And I think we have some private-use code points in IKEv2.
Probably there are some TLS examples.
Where you write private enterprise number in the OID section, please include
the TLA "PEN", because many people only know that.  Do you need an example?

I found section 2.2 to be awkwardly worded.
It seems that probably the IAB would never publish a code point, but an
example of an AD sponsored and ISE document would be good.

The reason for examples is to cultivate familiarity, like "Oh yeah, I
remember when that happened"

Is it worth publishing as an RFC?   I dunno exactly.
It would be definitely be worth it if it was also establishing a clearer
policy going forward.  Is that where you are trying to get to?

For instance, the ITU-T, when it published ISO/IEC 14888-3:2018 (SM2
algorithms, $$$ to read) *SHOULD* have gone to the IANA to get a IPsec/IKEv2
code allocation, instead we have draft-guo-ipsecme-ikev2-using-shangmi-01
via ISE that has to do the allocations.   
{Consistently, RFC9206 (from NIST) also came through the ISE, but it isn't
clear to me that this has occured consistently across the IETF}

-- 
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]

-----BEGIN PGP SIGNATURE-----

iQFKBAEBCgA0FiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmeQcTwWHG1jcitpZXRm
QHNhbmRlbG1hbi5jYQAKCRCAi3D73dDdZeY/CACgmmw0xv5rhrue+/4uO9Om2QFc
ZtMz3fqZBxQY972lSgjHE07NdEFG4uXlHvyueBokhKscz5MmB1U+6/HoXWc/HquA
YO0CghjwyvAyG9djMTCig5GOCs8qDrbd4r3khjKHMm3rxoW+Gy/AUopBI8j8t1ji
v+dgC0fHaA8rttDdAC5IbsuYoakRXWOG5w3c1G4nzeE3MANg8bNat4ijcML5PuGy
I5XdJ4F9EZskGeMRCE6fLWJH+kXcMhbiiwKTS9qmAgZUnFz7CkP16zD/SMPJciD+
HyIDqi0DbSM0acFkHcO8oXJyQv48/24kmrXgBDDumIO7LVLHtjB1RWmIPMrV
=O5p5
-----END PGP SIGNATURE-----