Ok. - Bernie (from iPad)
> On Nov 21, 2022, at 2:04 AM, mohamed.boucad...@orange.com wrote: > > ο»Ώ > Hi Bernie, > > Thanks for the comment. > > I agree that reference may be confusing for some readers. I went with a less > verbose text by simply replacing the OLD reference with βSection 8.3 of > [This-Document]β. Please see https://tinyurl.com/opsawg-add-latest. > > [This-Document] will be replaced by the RFC Editor with the RFC number to be > assigned to this draft. > > Cheers, > Med > > De : Add <add-boun...@ietf.org> De la part de Bernie Volz > EnvoyΓ© : dimanche 20 novembre 2022 13:30 > Γ : Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org> > Cc : opsawg@ietf.org; dh...@ietf.org; a...@ietf.org > Objet : Re: [Add] [dhcwg] π WG LC: RADIUS Extensions for Encrypted DNS > [EXTENDED] > > The changes related to 4014 are really minor as just changes text to use IANA > registry instead of list in original 4014. So not sure why this is really > that significant. > > My only concern is that the βnewβ text references section 8.3 of this new > draft and so the replacement text is a bit βoddβ? It is not referring to > section 8.3 in 4014. > > NEW: > To avoid dependencies between the address allocation and other > state information between the RADIUS server and the DHCP server, > the DHCP relay agent SHOULD include only the attributes in the > IANA-maintained registry (Section 8.3) in an instance of the > RADIUS Attributes suboption. > > I wonder if using the following might be better instead of referencing > section 8.3 from the new document? (In both βnewβ sections.) > > NEW: > To avoid dependencies between the address allocation and other > state information between the RADIUS server and the DHCP server, > the DHCP relay agent SHOULD include only the attributes in the > IANA-maintained sub-registry entitled "RADIUS Attributes Permitted > in RADIUS Attributes Sub-option" in the "Dynamic Host Configuration > Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters" registry > [BOOTP] > IANA-maintained registry in an instance of the > RADIUS Attributes suboption. > > But perhaps this is not a concern others have? > > - Bernie (from iPad) > > > On Nov 11, 2022, at 3:13 AM, Joe Clarke (jclarke) > <jclarke=40cisco....@dmarc.ietf.org> wrote: > > ο»Ώ > I am closing this WG LC. While I am glad that this work received a number of > reviews both in opsawg and from other WGs, I would have still like to see > more comments around the incorporation of the 4014 changes. > > We will now look to find a shepherd for this doc. Authors, if you know of > someone that may want to act in that role, let us know. > > Joe > > From: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org> > Date: Wednesday, October 19, 2022 at 10:11 > To: Joe Clarke (jclarke) <jcla...@cisco.com>, opsawg@ietf.org > <opsawg@ietf.org> > Cc: dh...@ietf.org <dh...@ietf.org>, a...@ietf.org <a...@ietf.org> > Subject: Re: π WG LC: RADIUS Extensions for Encrypted DNS [EXTENDED] > > After discussion with dhcwg, this document has taken on work from another > document that updates RFC 4014. I want to make sure that opsawg has had a > chance to review the extended scope and text. > > The WG LC is extended to end on November 3, 2022. To those in the WG that > have already commented, please review revision -05 or later and share your > thoughts on list. > > Joe > > From: OPSAWG <opsawg-boun...@ietf.org> on behalf of Joe Clarke (jclarke) > <jclarke=40cisco....@dmarc.ietf.org> > Date: Wednesday, October 12, 2022 at 12:43 > To: opsawg@ietf.org <opsawg@ietf.org> > Subject: [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS > > Hello, WG. While this work was recently adopted, there was a considerable > amount of discussion and work put in to address issues and stabilize the > spec. The authors feel it has reached a steady state and is ready for WG LC. > Based on my read of the discussion threads, it does appear the major issues > have been addressed. > > Therefore, this serves as the start of a two week WG LC for > https://datatracker.ietf.org/doc/draft-ietf-opsawg-add-encrypted-dns/. > Please provide your comments and/or support for the current spec on-list > prior to October 27. > > Thanks. > > Joe > _______________________________________________ > dhcwg mailing list > dh...@ietf.org > https://www.ietf.org/mailman/listinfo/dhcwg > _________________________________________________________________________________________________________________________ > > 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.
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
