Re: [Ssh] draft charter
Jeffrey Hutzelman <[email protected]> Tue, 13 Aug 2024 20:05:20 -0400
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <CALF+FNwiHitoU=cwTN2ns5BaWV40GE+nJnw+JGeEDJmPBtuJJw@mail.gmail.com> |
--0000000000002005f3061f997c51 Content-Type: text/plain; charset="UTF-8" Hm. The [email protected] list was used by the original secsh working group and has served as a forum for ongoing (if quite low-volume) discussion since then. Why not reuse it, instead of setting up a new list? The scope of a maintenance group like this should include discussion and evaluation of proposed extensions and revisions. Of course, actually working on any such proposal would require a charter revision, but IMHO it should be clear that this group is the right place for such discussions. -- Jeff On Tue, Aug 13, 2024, 18:38 Stephen Farrell <[email protected]> wrote: > > Thanks Deb, > > On 13/08/2024 23:24, Deb Cooley wrote: > > > > Or for more information see here: > > https://datatracker.ietf.org/wg/sshm/about/ > > As you'll have seen if you went to that web page, Deb > and Paul have asked Job Snijders and I to help out doing > a bit of chairing whenever this WG is officially setup. > We're happy to try help out that way. > > If anyone has any questions about IETF process or anything > else relevant, feel free to just mail the list, or if you > prefer, you could send off-list mail to Job and I. > > Meanwhile, comments on the draft charter, [1] as Deb said, > would be good to get in the immediate future. If you think > that text is good enough, getting a few "looks good to me" > mails sent to the list could also be useful for people > involved in approving the formation of the WG. > > Cheers, > S. > > [1] https://datatracker.ietf.org/doc/charter-ietf-sshm/ > > --0000000000002005f3061f997c51 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">Hm.=C2=A0 The=C2=A0<a href=3D"mailto:[email protected]"= >[email protected]</a>=C2=A0list was used by the original secsh working g= roup and has served as a forum for ongoing (if quite low-volume) discussion= since then. Why not reuse it, instead of setting up a new list?=C2=A0<div = dir=3D"auto"><br></div><div dir=3D"auto">The scope of a maintenance group l= ike this should include discussion and evaluation of proposed extensions an= d revisions. Of course, actually working on any such proposal would require= a charter revision, but IMHO it should be clear that this group is the rig= ht place for such discussions.</div><div dir=3D"auto"><br></div><div dir=3D= "auto">-- Jeff</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c= lass=3D"gmail_attr">On Tue, Aug 13, 2024, 18:38 Stephen Farrell <<a href= =3D"mailto:[email protected]">[email protected]</a>> wro= te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px = 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> Thanks Deb,<br> <br> On 13/08/2024 23:24, Deb Cooley wrote:<br> > <br> > Or for more information see here:<br> > <a href=3D"https://datatracker.ietf.org/wg/sshm/about/" rel=3D"norefer= rer noreferrer" target=3D"_blank">https://datatracker.ietf.org/wg/sshm/abou= t/</a><br> <br> As you'll have seen if you went to that web page, Deb<br> and Paul have asked Job Snijders and I to help out doing<br> a bit of chairing whenever this WG is officially setup.<br> We're happy to try help out that way.<br> <br> If anyone has any questions about IETF process or anything<br> else relevant, feel free to just mail the list, or if you<br> prefer, you could send off-list mail to Job and I.<br> <br> Meanwhile, comments on the draft charter, [1] as Deb said,<br> would be good to get in the immediate future. If you think<br> that text is good enough, getting a few "looks good to me"<br> mails sent to the list could also be useful for people<br> involved in approving the formation of the WG.<br> <br> Cheers,<br> S.<br> <br> [1] <a href=3D"https://datatracker.ietf.org/doc/charter-ietf-sshm/" rel=3D"= noreferrer noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/c= harter-ietf-sshm/</a><br> <br> </blockquote></div> --0000000000002005f3061f997c51--