Murray Kucherawy has entered the following ballot position for
draft-ietf-homenet-front-end-naming-delegation-19: No Record
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.
Robert Wilton has entered the following ballot position for
draft-ietf-homenet-front-end-naming-delegation-19: No Objection
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.
Reviewer: Tim Wicinski
Review result: Ready
Hi
As one of the assigned reviewers of this document for DNS Directorate for this
draft.
I have read the other DNS Directorate reviews for this draft, and I agree with
how the
comments raised are being addressed.I do appreciate the examples in th
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.)
Apologies; disregard - I entered this for the wrong document.
> On 2022-10-20, at 14:45, Lars Eggert via Datatracker 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
Hi Daniel,
Thanks for the updates, they look good, I will clear my DISCUSS. One further
comment, below.
> On Oct 19, 2022, at 11:47 PM, Daniel Migault wrote:
[… snip …]
> Later in the section we have
>
> ~~~
>1. The HNA is authenticated (see Section 4.6 of
>[I-D.ietf-homenet-front
John Scudder has entered the following ballot position for
draft-ietf-homenet-naming-architecture-dhc-options-22: No Objection
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, howev
Lars Eggert has entered the following ballot position for
draft-ietf-homenet-front-end-naming-delegation-19: 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.)
Ple
Christer, thank you for your review. I have entered an Abstain ballot for this
document based on my own review.
Lars
> On 2022-10-4, at 13:19, Christer Holmberg via Datatracker
> wrote:
>
> Reviewer: Christer Holmberg
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer f
Lars Eggert has entered the following ballot position for
draft-ietf-homenet-naming-architecture-dhc-options-22: Discuss
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.)
Ines, thank you for your review. I have entered a Discuss ballot for this
document based on my own review.
Lars
> On 2022-10-4, at 19:57, Ines Robles via Datatracker wrote:
>
> Reviewer: Ines Robles
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The G
Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-homenet-naming-architecture-dhc-options-22: No Objection
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
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Home Networking WG of the IETF.
Title : Simple Provisioning of Public Names for Residential
Networks
Authors : Daniel Migault
Hi Lars,
I have removed the section related to dynamic update which is a non
technical section that everyone discusses. Such discussions had been
endless and unhelpful in the homenet wg. We thought this section would
close some of these discussions, but it seems it reopens others. We do not
want t
Hi Lars,
Thanks for the comment. Please see my response inline below. The updates
associated to your comments can be found below:
https://github.com/ietf-homenet-wg/front-end-naming-delegation-dhc-options/commit/3113e186f17ed36ee3ec635b1414bdc181e06484
Yours,
Daniel
On Thu, Oct 20, 2022 at 8:21
Hi Zahed,
Thanks for the review.
On Thu, Oct 20, 2022 at 8:39 AM Zaheduzzaman Sarker via Datatracker <
nore...@ietf.org> wrote:
> Zaheduzzaman Sarker has entered the following ballot position for
> draft-ietf-homenet-naming-architecture-dhc-options-22: No Objection
>
> When responding, please k
-- I clicked send to early.
Hi Zahed,
Thanks for the review. Please find my response inline as well as the
updated text below:
https://github.com/ietf-homenet-wg/front-end-naming-delegation-dhc-options/commit/c29b4ca2b6e2af4de82ba20a975f3540fc93c458
I hope it addresses your concerns.
Yours,
Dan
Thanks for the comment Robert,
I appreciate the suggestion to use YANG, we thought of it. The main reason
we did not do it was we did not want the document to keep on growing and if
such a model were defined it would be good to have it normative.
I will go through the grammar, though I expect we
> On 20 Oct 2022, at 15:47, Daniel Migault wrote:
>
> -- I clicked send to early.
> Hi Zahed,
>
> Thanks for the review. Please find my response inline as well as the updated
> text below:
>
> https://github.com/ietf-homenet-wg/front-end-naming-delegation-dhc-options/commit/c29b4ca2b6e2af
Thanks I will adresse this in a couple of hours.
Yours,
Daniel
On Thu, Oct 20, 2022 at 9:59 AM Zaheduzzaman Sarker <
zaheduzzaman.sar...@ericsson.com> wrote:
>
>
> On 20 Oct 2022, at 15:47, Daniel Migault wrote:
>
> -- I clicked send to early.
> Hi Zahed,
>
> Thanks for the review. Please find m
Hi Zahed and Lars,
I think I mis-understood the comment.
I initially thought you were concerned that the server cannot specify
whatever port it wants. The current text was mostly saying "because DHCP
does not specify the port, the port needs to be defined by a standard. That
standard can be a docu
Hi Zahed and Lars,
I think I mis-understood the comment.
I initially thought you were concerned that the server cannot specify
whatever port it wants. The current text was mostly saying "because DHCP
does not specify the port, the port needs to be defined by a standard. That
standard can be a docu
Hi Paul,
Some brief element of response to your questions. While you are raising
comments within a DISCUSS see your comment as a very high level question on
what is the content of the draft with many questions related not to that
draft. I am happy to respond, but there is nothing actionable that c
On Thu, Oct 20, 2022 at 5:53 PM Daniel Migault wrote:
>
> Thanks for the feed back. Please see my response inline. Note that we are
> clarifying the use of transport protocols in the current document. For the
> synchronization channel we mandate XoT, for the control channel we mandate
> DoT - s
On Thu, Oct 20, 2022 at 6:26 AM Daniel Migault wrote:
>
> Hi Matt,
>
> Following up with other minor concerns. You can see the changes below:
> https://github.com/ietf-homenet-wg/ietf-homenet-hna/commit/88a1700865f80862301f96937ac07071efd58660
Mostly LGTM thanks, just following-up on a few minor
Roman Danyliw has entered the following ballot position for
draft-ietf-homenet-front-end-naming-delegation-20: Discuss
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.)
P
Lars Eggert via Datatracker wrote:
> 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 b
27 matches
Mail list logo