Re: [tcpinc] Eric Rescorla's Discuss on draft-ietf-tcpinc-tcpeno-13: (with DISCUSS and COMMENT)

[Tero Kivinen <[e-mail]>]

David Mazieres writes:
>    o  TEPs MUST NOT permit the use of encryption algorithms with a
>       security strength [SP800-57part1] of less than 120 bits.  The
>       intent of this requirement is to allow the use of algorithms such
>       as AES-128 [AES] that are designed for 128-bit security and still
>       widely considered secure even after losing a few bits of security
>       to highly theoretical attacks.

Just side comment about all this MUST / MUST NOT discussion. Remember
that there is going to be customer coming to you at one point and
asking you to show the line numbers which implements each MUST and
MUST NOT in the code, as their auditor required that information
before they allow product to be certified. Then you will curse all
those people who wrote the document and added all kind of MUSTs and
MUST NOTs to which cannot be verified.

I think both cases here are something that only limit the future IESG
or TEPs, and does not really need upper case MUST, and also mostly are
not even implementation or protocol issues but policy issues. And I
myself would recommend writing them in non-conformant manner just to
make implementors life easier.

And yes, I did get request from support asking me to provide line
numbers which implement the RFC7296 text saying "field X MUST NOT be
zero", so they can pass them to customers who is going to pass it to
audit lab... My original answer was "all of the lines", but I think
support converted it to more suitable answer.
-- 
[e-mail]