Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed

--On 24. august 2005 17:24 -0400 Sam Hartman <hartmans-ietf@mit.edu> wrote:

>     iesg> It is customary to include normative references to
>     iesg> informational documents describing cryptographic algorithms.
>     iesg> However the procedures of RFC 3967 require that this
>     iesg> normative reference be called out in the IETF last call.
>
>
> For the record I'd like to say that RFc 3967 seems poorly considered
> and I don't think strikes a reasonable balance between efficiency and
> quality.
>
> In particular RFC 3967 does not allow classes of documents such as
> cryptographic algorithms to be exempted from last call notice, only
> single documents.

For the record, I'd like to say that I disagree.

I think that if we search for an "easiest possible way to implement" the 
RFC 3967 requirement, we will end up with a single web-maintained document 
of "documents that are OK to refer to". Doing explicit action to add each 
sensible crypto document to that list as it comes out doesn't strike me as 
onerous.

                  Harald

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf