Re: [Settle] Initial SETTLE Charter discussion
Michael Sweet via ipp <[email protected]> Wed, 23 Apr 2025 11:22:27 -0400
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
Ira, Yeah, Dan and Mohamed wanted to keep the focus as small as possible - the various discussions over the years have all spiraled with lots of feature and standards creep. > On Apr 23, 2025, at 10:54 AM, Ira McDonald via ipp <[email protected]> wrote: > > Hi, > > Draft charter for an IETF SETTLE WG to address local network establishment of "secure contexts with servers" > via an Operations Management solution using existing IETF protocols. The thinnest draft charter I've ever seen. > > Hmm... > > ---------- Forwarded message --------- > From: <[email protected]> > Date: Wed, Apr 23, 2025 at 7:36 AM > Subject: [Settle] Initial SETTLE Charter discussion > To: [email protected] <[email protected]> > Cc: Dan Wing ([email protected]) <[email protected]>, [email protected] <[email protected]> > > > Hi all, > Based on the discussion on this mailing list in particular, it seems that there is interest to work on SETTLE-related topics. Similar discussions are also happening in other venues (W3C, for example). A common aspect of these discussions is that they are relying on protocols owned and maintained by the IETF. > I’m considering creating a short-lived WG with a very focused scope on ** OPS/deployment aspects ** as part of OPS area. An objective of this proposed WG to sketch operational/deployments guidance to obtain a secure context with servers operating within a local network. Operational issues with existing approaches will be identified, as appropriate. To that aim, I asked Dan Wing to hold the pen for editing a charter with that scope/objectives. > Coordination is important here. This is why the draft text has a formal milestone to establish contact and send LSes early in the process. > The draft charter can be seen at: https://github.com/danwing/settle-charter/blob/main/charter.md. > Please review and share comments/suggestions by May 07, 2025. You can share those using the mailing list or via github. Dan will take care of merging and integrating the comments/suggestions (thanks). > Thank you all, in advance, for your input and help in getting this up and running. > Cheers, > Med > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > _______________________________________________ > Settle mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ > ipp mailing list > [email protected] > https://www.pwg.org/mailman/listinfo/ipp ________________________ Michael Sweet _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp