Re: [saag] sntrup761x25519-sha512

[Peter Yee <[e-mail]>]

Thanks for the input, Mark. I suspect what will happen is that the designated experts list will be made of individuals who combined will have the breadth to cover all the registries. I rather doubt it will be one person (and probably a backup expert). I think a single mailing list simplifies where discussion takes place. If there are many experts (one can wish), I expect they will work it out amongst themselves how to divvy up the incoming registration requests.

 

                                Kind regards,

                                -Peter

 

[Sent from my Windows PC – Please pardon any flappy-finger created typos.]

 

From: Mark Baushke <[e-mail]> 
Sent: Tuesday, May 23, 2023 5:51 PM
To: Peter Yee <[e-mail]>
Cc: Paul Wouters <paul.wouters=[e-mail]>; Simon Josefsson <simon=[e-mail]>; [e-mail]
Subject: Re: [saag] sntrup761x25519-sha512

 

Hi Peter,

 

Yes, RFC 4250 Section 4.6.1 specifies names be approved by IETF CONSENSUS as defined in section 3.2 with this definition:

 

  IETF CONSENSUS - New values are assigned through the IETF consensus
   process.  Specifically, new assignments are made via RFCs approved by
   the IESG.  Typically, the IESG will seek input on prospective
   assignments from appropriate persons (e.g., a relevant Working Group
   if one exists).
 
Your suggestion to move to 
 
 
  EXPERT REVIEW - approval by a Designated Expert is required.

 

makes sense to me as the experts are designated by RFC  8126 in section 5 via the IESG with the help of ADs… I think I got that right?

 

I would suspect that Kex method names and encryption algorithm names may not always be given to the same designated expert person.  I am uncertain if a mailing list for all of the SSH parameters table update approval should be the same individual or not.

 

I agree that the [e-mail] <mailto:[e-mail]>  list could be used as a start and that group could choose the expert to use for a request.

 

                -- Mark

 

[Sent from my iPad -- Please pardon any auto-fix created typos.]





On May 23, 2023, at 7:10 PM, Peter Yee <[e-mail] <mailto:[e-mail]> > wrote:



And, yes, I need to finish that off. I let it slip off my radar, but I’ll turn it around shortly.

 

                                -Peter

 

From: saag <[e-mail] <mailto:[e-mail]> > On Behalf Of Paul Wouters
Sent: Tuesday, May 23, 2023 4:57 PM
To: Simon Josefsson <simon=[e-mail] <mailto:simon=[e-mail]> >
Cc: [e-mail] <mailto:[e-mail]> 
Subject: Re: [saag] sntrup761x25519-sha512

 

 

On Tue, May 23, 2023 at 6:37 PM Simon Josefsson <simon=[e-mail] <mailto:[e-mail]> > wrote:

"Martin Thomson" <[e-mail] <mailto:[e-mail]> > writes:


As far as I understand, the independent submission route is not possible
due to the IANA registration policy for the SSH KEX registry.

 

https://datatracker.ietf.org/doc/html/draft-yee-ssh-iana-requirements-01

 

Paul

_______________________________________________
saag mailing list
[e-mail] <mailto:[e-mail]> 
https://www.ietf.org/mailman/listinfo/saag