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

Watson Ladd <[email protected]>
Newsgroups gmane.ietf.saag
Message-ID <CACsn0cnJ7LNhHiMEeG7EUz5Od9s1wrkb-kWEEF7UbUyi2PEsCA@mail.gmail.com>
On Thu, Jan 23, 2025, 12:09 PM Simon Josefsson <simon=
[email protected]> wrote:

> Stephen Farrell <[email protected]> writes:
>
> > Hiya,
> >
> > On 23/01/2025 14:38, Eric Rescorla wrote:
> >> Thanks for this example, as I think it shows that you've badly
> >> mischaracterized my position.
> >
> > Sorry, I was trying to describe what I'm relatively
> > sure some other folks took as being your position,
> > but I guess I didn't phrase it well enough. I agree
> > that their impression of your position differs from
> > what you intended.
>
> Interesting.  I read both Eric's original statement and the
> clarification both expressing the identical message: "we don't want to
> publish ntruprime-SSH as an RFC standard".  As far as I can tell that is
> Eric's position [1].  My interpretation of Eric's clarification being
> identical to the original quote is based on the incorrect but often
> repeated claim (even by IETF AD's) that the ntruprime-SSH draft is not
> under IETF change control, and the related opinion that only
> NIST-blessed crypto can "serve the IETF purpose".
>

Why is standards track required and not informational?

>
> /Simon
>
> [1] https://mailarchive.ietf.org/arch/msg/ssh/CH6kRRISzwyorzF-l1NLiIUK05A/
> _______________________________________________
> saag mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.