Hi Med, Thanks for the review, please find some responses to your comments inline. I will publish shortly a new version that addresses your comments.
Yours, Daniel In this context agnostic is used to mention the CE router can learn everything from the network without requiring interaction from the end user. [1] https://dictionary.cambridge.org/dictionary/english/agnostic [BMT17]: Do you assume that default ports are used? If not, how this is discovered? > Yes, we currently only configure the most simple configuration. There is no discovery. Non default parameters might be defined out of bound, or other mechanisms such as SVCB for example. [BMT18]: Why not returning a list of IP addresses? Or do you need it for authentication? > this has been extensively discussed but I agree a long time ago. As far as I remember, we used the FQDN for compactness and we assumed the CE is able to resolve the name. On Wed, May 5, 2021 at 8:33 AM <[email protected]> wrote: > Hi all, > > FWIW, some comments to be considered by the authors as part the WGLC can > be seen at: > > * draft-ietf-homenet-naming-architecture-dhc-options: > - pdf: > https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-homenet-naming-architecture-dhc-options-12-rev%20Med.pdf > - doc: > https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-homenet-naming-architecture-dhc-options-12-rev%20Med.docx > > * draft-ietf-homenet-front-end-naming-delegation: > - pdf: > https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-homenet-front-end-naming-delegation-14-rev%20Med.pdf > - doc: > https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-homenet-front-end-naming-delegation-14-rev%20Med.docx > > > Cheers, > Med > > > -----Message d'origine----- > > De : dns-privacy [mailto:[email protected]] De la part de > > STARK, BARBARA H > > Envoyé : mardi 4 mai 2021 15:56 > > À : '[email protected]' <[email protected]> > > Cc : '[email protected]' <[email protected]>; '[email protected]' <dns- > > [email protected]>; '[email protected]' <[email protected]> > > Objet : [dns-privacy] WGLC started > > > > Hi homenet, intarea, dhc, and dprive, > > Homenet has started WGLC for draft-ietf-homenet-front-end-naming- > > delegation-14 and draft-ietf-homenet-naming-architecture-dhc-options- > > 12. > > > > https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming- > > delegation/ (Simple Provisioning of Public Names for Residential > > Networks) https://datatracker.ietf.org/doc/draft-ietf-homenet-naming- > > architecture-dhc-options/ (DHCPv6 Options for Home Network Naming > > Authority) > > > > We're including intarea, dhc, and dprive to get a slightly wider > > audience for the technical aspects of these drafts (dhc is > > specifically asked to look at the dhc-options draft). > > The drafts do also need some editorial fixing-up. I'll be focusing on > > that so the technical experts can focus on the technical aspects. > > > > I've made the WGLCs for 3 weeks instead of the normal 2. I'm doing > > this because > > - we're reaching out to WGs that haven't seen this before and asking > > them for comments > > - there are 2 drafts > > - I'm on vacation next week and was getting stressed out by > > everything I need to get done by this Friday > > > > The meeting minutes (from the homenet April 23 interim) list intarea, > > dprive, and dhc as other groups to request comments from. Is this the > > right list? Are there others? > > Please let me know if I should broaden this. > > Thx, > > Barbara > > > > _______________________________________________ > > dns-privacy mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/dns-privacy > > > _________________________________________________________________________________________________________________________ > > 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. > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet > -- Daniel Migault Ericsson
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
