Apologies; disregard - I entered this for the wrong document. > On 2022-10-20, at 14:45, Lars Eggert via Datatracker <nore...@ietf.org> wrote: > > Lars Eggert has entered the following ballot position for > draft-ietf-homenet-naming-architecture-dhc-options-22: Abstain > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ > for more information about how to handle DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > I agree with the Discusses and Comments on this document - this simply isn't > implementable as described. > > My main reason for abstaining is something else though. This document has been > worked on for almost ten years. While in the beginning, we might have expected > or at least hoped that a solution in the shape that this document tries to > describe would see adoption, it's become very clear that dynamic DNS services > as described in Section 4 have won out here. These services are far from > perfect, but at least some of the limitations in Section 4 have been > addressed, > and others are arguably a feature and not a limitation. > > >
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
