Hi Dirk, Many thanks for the review.
Please see inline. Cheers, Med De : dirk.von-h...@telekom.de <dirk.von-h...@telekom.de> EnvoyΓ© : jeudi 15 septembre 2022 17:04 Γ : opsawg@ietf.org Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> Objet : RE: π CALL FOR ADOPTION: RADIUS Extensions for Encrypted DNS Dear WG, I have read the draft and find it useful for the foreseen applications of secure broadband access control. I support adoption and would mention some nits or clarification of the issues below: p.2: DNS Recursive DNS server(s)=> DNS Recursive name server(s)[?] [Med] Changed to βDNS recursive server(s)β. p.4: DNS-related information (e.g., ADN, => DNS-related information (e.g., ADN(Authentication Domain Name), [Med] Fixed. RADIUS CoA message => RADIUS CoA (Change-of-Authorization) message [Med] Fixed Attributed to the NAS => Attribute to the NAS [Med] ACK p.9: β¦ use the format defined in [RFC6929<https://datatracker.ietf.org/doc/html/rfc6929>]. [I wonder whether reference to RFC2865 would be more appropriate here since no Extended-Type field is needed, if I understood it correctly?] [Med] Added a pointer to Section 2.3 of 6929 to make the intent explicit. p.10: TLV is identified as 241.TBA1.TBA5 as part of the IPv4-Encrypted-DNS Attribute => TLV is identified as 241.TBA2.TBA5 as part of the IPv4-Encrypted-DNS Attribute [Med] Good catch. Fixed p.13: I wonder whether in IANA section the proposed new RADIUS TLVs are not denoted as TBA3 β TBA7 as mentioned in the corresponding sub-sections, but by 1 β 5? [Med] Updated the IANA section accordingly. FWIW, the changes can be tracked at: Diff: draft-boucadair-opsawg-add-encrypted-dns-07.txt - draft-boucadair-opsawg-add-encrypted-dns.txt (ietf.org)<https://www.ietf.org/rfcdiff?url1=draft-boucadair-opsawg-add-encrypted-dns&url2=https://raw.githubusercontent.com/boucadair/draft-boucadair-opsawg-add-encrypted-dns/master/draft-boucadair-opsawg-add-encrypted-dns.txt> Thanks! Best regards Dirk From: OPSAWG <opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org%3cmailto:opsawg-boun...@ietf.org>>> on behalf of Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org<mailto:jclarke=40cisco....@dmarc.ietf.org<mailto:jclarke=40cisco....@dmarc.ietf.org%3cmailto:jclarke=40cisco....@dmarc.ietf.org>>> Date: Wednesday, September 14, 2022 at 10:28 To: opsawg@ietf.org<mailto:opsawg@ietf.org<mailto:opsawg@ietf.org%3cmailto:opsawg@ietf.org>> <opsawg@ietf.org<mailto:opsawg@ietf.org<mailto:opsawg@ietf.org%3cmailto:opsawg@ietf.org>>> Subject: [OPSAWG] π CALL FOR ADOPTION: RADIUS Extensions for Encrypted DNS Hello, WG. I like Henkβs subject icon. Makes for some attention-grabbing. This work has been discussed previously in opsawg, going back over a year. The authors have continued to progress the work and would like to gauge WG interest in adopting it. One might ask, why opsawg? The radext WG has been concluded, but, like IPFIX, there is interest in continuing to produce extensions for RADIUS. It was suggested by Benjamin Kaduk that opsawg was a potential fit for this work. Therefore, this kicks off a two-week CfA for https://datatracker.ietf.org/doc/draft-boucadair-opsawg-add-encrypted-dns/. Please comment on-list with support and/or discussion of the work. Thanks. Joe _________________________________________________________________________________________________________________________ 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
