Hi Bernie, Thank you for the feedback.
I have considered a registry to declare the options that can be echoed in the RADIUS attribute, but I then give it up because that list will be restricted anyway by policy: RADIUS implementations may support a configuration parameter to control the DHCP options that can be included in a DHCP*-Options RADIUS attribute. Cheers, Med De : Add <add-boun...@ietf.org> De la part de Bernie Volz EnvoyΓ© : vendredi 14 octobre 2022 17:48 Γ : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> Cc : dh...@ietf.org; Joe Clarke (jclarke) <jcla...@cisco.com>; opsawg <opsawg@ietf.org>; ADD Mailing list <a...@ietf.org>; rad...@ietf.org Objet : Re: [Add] [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS Hi: Your github document is -03 and published is -03, so likely you want to make it -04? As no dhcp options are being defined and they are just being encapsulated in Radius attributes, not exactly sure how much the DHC wg can (or needs to) comment? This basically changes things so you no longer have unique Radius attributes that are mapped to DHCP options, but you just use the DHCP options directly. This seems fine. (It does complicate the Radius configuration to handle DHCP option configuration if you donβt want them to be hand encoded as octet data, and many of the encoding/validation rules are not as consistent as we would like, especially for older options.) The one concern for DHC wg may be to restrict the options that a DHCP server can send out if these options are intended to be delivered to the client via the dhcp server β¦ for example, one would not want address or prefix delegation options to be allowed. This might be something similar to https://datatracker.ietf.org/doc/rfc6422/ which created a new registry for the allowed DHCPv6 options that can be provided by a relay agent (in this case encoded in the attributes). - Bernie Volz On Oct 14, 2022, at 10:45 AM, mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com> wrote: ο»ΏHi Bernie, dhcwg, We received a comment during the WGLC of this draft that might lead us to revisit the design you have reviewed recently. This alternative design mirrors what we have done in 7037 (dhcwg) but with DHCP options included in RADIUS. The candidate text is available at: https://github.com/boucadair/draft-ietf-opsawg-add-encrypted-dns/blob/main/draft-ietf-opsawg-add-encrypted-dns-encap.txt I'd appreciate if you can review this proposal and share any comments/issues you may have. Thank you. Cheers, Med -----Message d'origine----- De : BOUCADAIR Mohamed INNOV/NET EnvoyΓ© : vendredi 14 octobre 2022 16:32 Γ : 'Alan DeKok' <al...@deployingradius.com<mailto:al...@deployingradius.com>> Cc : Ben Schwartz <bem...@google.com<mailto:bem...@google.com>>; Joe Clarke (jclarke) <jcla...@cisco.com<mailto:jcla...@cisco.com>>; opsawg <opsawg@ietf.org<mailto:opsawg@ietf.org>>; rad...@ietf.org<mailto:rad...@ietf.org>; ADD Mailing list <a...@ietf.org<mailto:a...@ietf.org>> Objet : RE: [Add] [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS Re-, Works for me. Thanks. I will run this candidate version with dhcwg as well. Cheers, Med -----Message d'origine----- De : Alan DeKok <al...@deployingradius.com<mailto:al...@deployingradius.com>> EnvoyΓ© : vendredi 14 octobre 2022 16:00 Γ : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> Cc : Ben Schwartz <bem...@google.com<mailto:bem...@google.com>>; Joe Abley <jab...@hopcount.ca<mailto:jab...@hopcount.ca>>; Ben Schwartz <bemasc=40google....@dmarc.ietf.org<mailto:bemasc=40google....@dmarc.ietf.org>>; Joe Clarke (jclarke) <jcla...@cisco.com<mailto:jcla...@cisco.com>>; opsawg <opsawg@ietf.org<mailto:opsawg@ietf.org>>; rad...@ietf.org<mailto:rad...@ietf.org>; ADD Mailing list <a...@ietf.org<mailto:a...@ietf.org>> Objet : Re: [Add] [OPSAWG] π WG LC: RADIUS Extensions for Encrypted DNS On Oct 14, 2022, at 5:47 AM, <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> <mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>> wrote: Let's try to exercise this approach and see if there are not hidden complications vs. current design with known limitation. A drafty text (not yet in the main draft) can be seen at: https://github.com/boucadair/draft-ietf-opsawg-add-encrypted- dns/blob/main/draft-ietf-opsawg-add-encrypted-dns-encap.txt Nits: Section 3: just drop the ASCII art. RFC 8044 makes it no longer necessary. Section 3.1, 3.2, and 7.1: the data type should be "string" for "opaque data" Other than that, it looks good on first read-through. The attributes should not be seen as opaque data by the RADIUS server but it should understand the encoding of the enclosed options. The intended behavior should be called out, IMO. I would suggest saying something like "for ease of administrator configuration, the RADIUS server SHOULD expose the DHCP options and allow administrators to configure them, instead of requiring them to be entered as opaque data". That gets the best of both worlds. Alan DeKok. _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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
