Hi Arnaud, To be honest we don't have one (yet), need to add it to my todo list..
On Wed, Mar 15, 2023 at 2:59 AM Arnaud Taddei <[email protected]> wrote: > Thank you Warren, we appreciate be given a chance to present. > > Please note we issued revision -04 and plan a revision -05 by Monday 27th > of March. > Encrypted Client Hello Deployment Considerations > <https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/> > datatracker.ietf.org > <https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/> > [image: ietf-logo-nor-180.png] > <https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/> > <https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/> > > One question as we are working on the best way to make our Github public. > > I observed that there is a ’tslwg’ Github entity which is hosting for > example the ECH repo. > > Is there an equivalent ‘opsecwg’ entity we should be using to host our > repo and have all the magic links done (notifications, etc.) through this > working group mailing list? > > Sorry if this is a naive question. Trying to do the right things the right > way. > > Best > > Le 7 mars 2023 à 23:22, Warren Kumari <[email protected]> a écrit : > > Hello WG! > > I'd encourage the WG to review this document - it's relatively short, and > is an easy read. > > ECH is likely to be a fairly active topic in the IETF, and has significant > Opsec implications. The document is on the OpSec agenda, and so having read > it before the meeting will be really helpful.. > > W > > > > On Fri, Feb 17, 2023 at 8:15 AM, Andrew Campling < > [email protected]> wrote: > >> Hi Opsec wg >> >> You may be aware that some of us have been looking at the potential >> impact of the deployment of Encrypted Client Hello (ECH), an extension to >> TLS1.3+. We are continuing to develop the draft, which is accessible at >> https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/. >> You will note that many of the issues that we have identified relate to >> various aspects of operational security in a variety of contexts. >> >> >> >> We have been encouraged to share the draft with the Opsec working group >> to see if there is interest in the topic within the group, hence this >> post. I and at least one of my co-authors will be present in Yokohama for >> the IETF 116 meeting and will be happy to present the highlights of the >> draft if time is available on the wg agenda. >> >> >> >> >> >> Andrew >> >> >> >> _______________________________________________ >> OPSEC mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/opsec >> > > _______________________________________________ > OPSEC mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsec > > > _______________________________________________ > OPSEC mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsec > -- SY, Jen Linkova aka Furry
_______________________________________________ OPSEC mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsec
