Hi:
Yes, I don’t see an issue.
One minor item you may want to look at is whether “text” is the best way to
label the following data type in Table 2:
TBA3 | Encrypted-DNS-ADN | text | This-Document, |
| | | | Section 3.3.1
Perhaps “dns wire encoding” might be better? Someone that just uses this table
may get it wrong? While perhaps there is some definition of “text” for Radius
attributes, a quick check of some seems to show that it is mostly used for
textual values. But perhaps you have limited choices here and other dns encoded
attributes already use text?
- Bernie
> On Oct 5, 2022, at 7:52 AM, [email protected] wrote:
>
> Hi Bernie, all,
>
> I don't expect this to be problematic but I prefer to have a formal request
> to review
> https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-add-encrypted-dns-01#section-6.3
> as it relates to a DHC registry.
>
> Thank you.
>
> Cheers,
> Med
>
> -----Message d'origine-----
> De : [email protected] <[email protected]>
> Envoyé : vendredi 30 septembre 2022 16:25
> À : Tirumaleswar Reddy.K <[email protected]>; BOUCADAIR Mohamed INNOV/NET
> <[email protected]>; Tirumaleswar Reddy <[email protected]>
> Objet : New Version Notification for
> draft-ietf-opsawg-add-encrypted-dns-01.txt
>
>
> A new version of I-D, draft-ietf-opsawg-add-encrypted-dns-01.txt
> has been successfully submitted by Mohamed Boucadair and posted to the IETF
> repository.
>
> Name: draft-ietf-opsawg-add-encrypted-dns
> Revision: 01
> Title: RADIUS Extensions for Encrypted DNS
> Document date: 2022-09-30
> Group: opsawg
> Pages: 18
> URL:
> https://www.ietf.org/archive/id/draft-ietf-opsawg-add-encrypted-dns-01.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-opsawg-add-encrypted-dns/
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-add-encrypted-dns
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-add-encrypted-dns-01
>
> Abstract:
> This document specifies new Remote Authentication Dial-In User
> Service (RADIUS) attributes that carry an authentication domain name,
> a list of IP addresses, and a set of service parameters of encrypted
> DNS resolvers.
>
>
>
>
> The IETF Secretariat
>
>
>
> _________________________________________________________________________________________________________________________
>
> 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
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
