gt;
>
> I am happy with the proposed rewording of DDoS attack surface – this at
> least remains accurate to what is taking place.
>
>
>
> Thanks
>
>
>
> Anthony
>
>
>
> *From: *Daniel Migault
> *Date: *Wednesday, 08 February 2023 at 17:36
> *T
t mentioned below have been addressed previously. In other
words, no action is expected.
Section 3.2 - Original NIT dealt with
>
> 1.1 - now 3 - NIT dealt with
>
> 3.1 now 5.1 - Typo fixed
>
> 4.5.1 - now 6.5.1 - i believe this NIT to be well addressed now, the
> reflowing
> of the document definitely helps here.
>
> Thanks
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
>
> -éric
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
ked up by other reviews.
>
> Tim
>
> On 13 Jan 2023, at 19:17, Daniel Migault wrote:
>
> Hi Tim,
>
> Thanks for the feed backs. Please see how the document has been updated.
> The ULA comment may remain open.
>
> https://github.com/ietf-home
for the follow-up!
Yours,
Daniel
On Thu, Jan 12, 2023 at 10:28 AM Tim Chown wrote:
> Hi,
>
> In-line...
>
> On 9 Jan 2023, at 18:15, Daniel Migault wrote:
>
> Hi Tim,
>
> Thanks for the review we updated the file as follows:
>
> https://github.com/ietf-homenet-wg
Jan 9, 2023 at 2:52 PM Daniel Migault wrote:
>
>> Hi Paul,
>>
>> Thanks for the review. We updated the document as follows.
>>
>> https://github.com/ietf-homenet-wg/ietf-homenet-hna/pull/63/commits/f221d3413f71bf95f8961f8fe3c71e53f8f3dd20
>>
>
> Than
On Thu, Oct 27, 2022 at 3:43 PM Daniel Migault wrote:
>
>
> On Thu, Oct 27, 2022 at 5:32 AM Michael Richardson
> wrote:
>
>>
>> Roman Danyliw via Datatracker wrote:
>> > [per -18] I’m not sure if this my misreading of the behavior of
>> >
aster protocols.
"""
Yours,
Daniel
On Fri, Dec 30, 2022 at 9:54 PM Daniel Migault wrote:
> Hi Murray,
>
> Thanks for the review. I will provide a more complete review in a few
> days, but here are some quick and partial responses.
>
> Yours,
> Daniel
>
are more for the developers of the protocol which are
expected to tweak it to their targeted end users.
> Carriers may need to deploy additional mitigations to ensure that
> attacks do not originate from their networks. The use of RFC8520
> (MUD)
> filters is one
function.
> Section 14:
>
> The document “exposes a mechanism” ?
>
> In 14.4, maybe mention here if any special considerations for a
> replacement CPE
> (and thus HNA if that model its used) are needed?
>
> Well, I believe that is more related to the operation of the HNA, and
this can be handled in multiple ways. The DHCP companion describes one way
to do.
Tim
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
e that choice or provide implementers with any guidance
> about
> when it might be appropriate to exercise that choice. I suggest reviewing
> them
> (there are 25, and 6 RECOMMENDEDs) and either adding such prose, or
> reconsidering whether they should be MUST or MAY.
>
>
>
just one clarification: do we prefer to have a version 25 being published
or should we leave it as version 24 ?
Yours.
Daniel
On Wed, Dec 7, 2022 at 8:11 AM Daniel Migault wrote:
>
>
> On Wed, Dec 7, 2022 at 7:56 AM Michael Richardson
> wrote:
>
>>
>> E
t removed rfc6125
> As for RFC5077. I have replaced it with RFC8446 (TLS1.3), section 4.6.1,
> but
> the reference feels less useful now.
>
>
> --
> Michael Richardson. o O ( IPv6 IøT consulting )
>Sandelman Software Works Inc, Ottawa and Worldwide
>
>
Thank Michael. I think the changes made are improving the clarity of the
text.
Yours,
Daniel
On Sat, Dec 3, 2022, 22:14 Michael Richardson wrote:
>
> internet-dra...@ietf.org wrote:
> > There is also an HTML version available at:
> >
>
On Fri, Dec 2, 2022 at 9:50 AM Michael Richardson
wrote:
>
> Daniel Migault wrote:
> > In my opinion the Synchronization Channel is initiated by the DM and
> > follows AXFR over TLS (9103). To my understanding NOTIFY, SOA
> exchange
> > may be protect
larly check (via a DNS resolution) that
> the address of the DM in the filter is still valid.
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
> No the core protocol is about outsourcing the zone to the DOI.
>Similarly, if the HNA is provided by a registrar, the HNA may be
>handed pre-configured to end user.
>
> How can that be if the user decides on the homenet netw
On Wed, Nov 23, 2022 at 9:12 AM Paul Wouters wrote:
> On Nov 22, 2022, at 16:15, Daniel Migault wrote:
> >
> >
> > Hi Paul,
> >
> > I am doing the follow-up and would like to check if there are any
> specific questions regarding the current version of
> —John
>
> On Nov 22, 2022, at 4:24 PM, Daniel Migault wrote:
>
>
>
> Hi John,
>
> Just let us know what remains to be addressed or clarified. We are
> happy to move that document forward.
>
> Yours,
> Daniel
>
> On Fri, Oct 28, 2022 at 5:38 PM Daniel
Hi John,
Just let us know what remains to be addressed or clarified. We are happy to
move that document forward.
Yours,
Daniel
On Fri, Oct 28, 2022 at 5:38 PM Daniel Migault wrote:
>
>
> On Fri, Oct 28, 2022 at 4:18 PM John Scudder wrote:
>
>> > On Oct 28, 2022, at 2:
Hi Warren,
I am doing the follow-up and would like to know if there are any technical
concerns in the current version. Feel free to let us which they are so we
can address them shortly.
Yours,
Daniel
On Fri, Oct 28, 2022 at 4:49 PM Daniel Migault wrote:
>
> Hi Warren,
>
> This is
Hi Paul,
I am doing the follow-up and would like to check if there are any specific
questions regarding the current version of the document.
Yours,
Daniel
On Mon, Oct 31, 2022 at 10:34 PM Daniel Migault wrote:
> Ray implemented the front end naming architecture but I am unaw
Hi Roman,
I am just following up and I am wondering if there is anything that we
missed to lift your DISCUSS ?
Yours,
Daniel
On Thu, Nov 3, 2022 at 9:48 PM Daniel Migault wrote:
> Thanks Roman for the follow-up. For some reason I could not find the
> response.
>
> So
update/
[3]]https://help.dyn.com/update-client-faqs/
[4] https://help.dyn.com/tsig/
On Thu, Nov 3, 2022 at 1:35 PM Roman Danyliw wrote:
> Hi!
>
>
>
> Please see an response to below to Michael’s email:
>
>
>
> *From:* Daniel Migault
> *Sent:* Monday,
to understand what the other means.
This is what we are trying to do.
> When did that happen?
>
> -- Juliusz
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/
Yours,
Daniel
On Mon, Oct 31, 2022 at 5:56 PM Paul Wouters wrote:
> On Oct 31, 2022, at 09:39, Daniel Migault wrote:
>
>
>
> Hi Paul,
>
> This is just a follow-up regarding the remaining concerns that need to be
>
Hi,
We just published today the latest version today, so you can rely on
the one published in the datatracker.
Yours,
Daniel
On Mon, Oct 31, 2022 at 9:46 AM Daniel Migault wrote:
> Hi Lars,
>
> I am just doing a follow-up regarding the comment "This simply isn't
> implement
uite a lot of clarifications, and we
expect to publish a new version as soon as the datatracker re-open. It's
probably worth waiting for that new version (unless you read the one from
github).
Yours,
Daniel
On Thu, Oct 20, 2022 at 9:22 AM Daniel Migault wrote:
> Hi Lars,
>
> I have removed the section
gt; > So I am guessing. The only known method for hostnames publishing
> their
> > names into a zone I know of is with Dynamic Updates on a local zone.
> But
> > perhaps what homenet
> > envisions is that I give my sauna a static IP and configure some
> webgui on
> > my CPE to add it to my "zone" ?
>
> No, and the document explains why this is a non-starter.
>
>
> --
> Michael Richardson , Sandelman Software Works
> -= IPv6 IoT consulting =-
>
>
>
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
I forgot to put the github link below:
https://github.com/ietf-homenet-wg/front-end-naming-delegation-dhc-options/commit/769a236615d47d812037bf3b74cddeefb9d5daf2
Yours,
Daniel
On Mon, Oct 31, 2022 at 9:34 AM Daniel Migault wrote:
> Hi Paul,
>
> We implemented the change and used
. Of
course, the DISCUSS being raised does not mean no changes can be made.
Yours,
Daniel
On Fri, Oct 28, 2022 at 7:32 PM Daniel Migault wrote:
> I am happy to close this issue with DNS over mTLS.
> Yours,
> Daniel
> On Fri, Oct 28, 2022 at 7:19 PM Paul Wouters
> wrote:
>
>>
Hi Roman,
This is just a follow-up. Currently we believe we have addressed your
concerns, but we would like to double check if there are any other
concerns/questions you would like us to address.
Yours,
Daniel
On Thu, Oct 27, 2022 at 3:43 PM Daniel Migault wrote:
>
>
> On Thu, Oct
at these two things which are separate are one option.
>
Perhaps it is better if we resolve the other document DISCUSS first and
> then see if that helps resolve this DISCUSS.
>
> Sent using a virtual keyboard on a phone
>
> On Oct 28, 2022, at 17:06, Daniel Migault wrote:
On Fri, Oct 28, 2022 at 4:18 PM John Scudder wrote:
> > On Oct 28, 2022, at 2:52 PM, Daniel Migault wrote:
> >
> > Let me know if the text below is clearer.
>
> So much clearer! Thanks!
>
> > OLD:
> > The transport channel (including port number) is t
n a phone
>
> On Oct 28, 2022, at 15:14, Daniel Migault wrote:
>
>
> Hi Paul,
>
> I am wondering if there are any remaining concerns left for
> the draft-ietf-homenet-naming-architecture-dhc-options document and
> anything you would like us to address to lift your discuss.
&g
anging the key.
I cannot tell what Appropriate means in that context.
On Thu, Oct 20, 2022 at 1:43 AM Daniel Migault wrote:
> Hi Warren,
>
> Thanks for the review. I went through all comments and addressed them here:
>
> https://github.com
Hi Paul,
I am wondering if there are any remaining concerns left for
the draft-ietf-homenet-naming-architecture-dhc-options document and
anything you would like us to address to lift your discuss.
Yours,
Daniel
On Mon, Oct 24, 2022 at 8:49 PM Daniel Migault wrote:
> Hi Paul,
>
&g
I find time to review the rest.
>
> > On Oct 20, 2022, at 1:23 AM, Daniel Migault wrote:
>
> [… snip …]
>
> > ### Section 4.3
> >
> > I don't understand what this paragraph is telling me about the provision
> of the
> > IP address by the HNA:
> >
>
ichardson , Sandelman Software Works
> -= IPv6 IoT consulting =-
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
t; On Sun, Oct 23, 2022 at 10:45 PM Daniel Migault
> wrote:
>
>> While TLS gives you privacy,
>>
>>> the DNS Update cannot be done with only TLS (as far as I understand it).
>>>>
>>>> please develop, but just in case, we do not use dns update to
>
xplaining why only DoT is specified in this draft.
>
> This draft looks good to me.
>
> Regards,
> Miek Gieben
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
Hi Paul,
Thanks for the feedback. This is interesting. Please see my responses. I do
not see any need to add some text, but I am happy to do so if you think
that is needed.
Yours,
Daniel
On Sun, Oct 23, 2022 at 8:57 PM Paul Wouters wrote:
>
> On Thu, Oct 20, 2022 at 4:04 PM Daniel M
menet zone and homenet zone so not all
your devices are expected to be public.
> Scanning IPv6 is still fairly hard to
> do, even of endusers /64. And putting those IPv6 addresses in DNS makes it
> much
> much easier to find all these devices and use their exposed se
AM Matt Brown wrote:
> On Sat, Oct 22, 2022 at 4:11 AM Daniel Migault
> wrote:
> >
> > Hi Matt,
> >
> > Thanks for the follow-up, please see my response.
> >
> > Yours,
> > Daniel
> >
> > On Thu, Oct 20, 2022 at 4:37 PM Matt Brown wro
it.
NEW:
The main difference is that ISP that provides the IP connectivity is likely
also the owner of the corresponding reverse zone and administrating the
Reverse Public Authoritative Servers ( or being the DOI)
> _______
> homenet mailing list
> homenet@i
“DNSSEC Resolver” or “DNS(SEC) Resolver” (as was introduced
> later) since DNSSEC is not mandatory.
>
>
> I changed it in 8 places
> ------
> COMMENT:
> --
Hi Matt,
Thanks for the follow-up, please see my response.
Yours,
Daniel
On Thu, Oct 20, 2022 at 4:37 PM Matt Brown wrote:
> 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
> a
> instead f TSIG/SIG0.
>
> not at all. we do not use dns update at all for synchronizing the zones.
>
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
rt, port ) as well as the possibility to use a dedicated IP
address for the DM in case the default port was already in use.
Yours,
Daniel
On Thu, Oct 20, 2022 at 9:37 AM Daniel Migault wrote:
> Hi Lars,
>
> Thanks for the comment. Please see my response inline below. The updates
> associated
rt, port ) as well as the possibility to use a dedicated IP
address for the DM in case the default port was already in use.
Yours,
Daniel
On Thu, Oct 20, 2022 at 10:11 AM Daniel Migault wrote:
> Thanks I will adresse this in a couple of hours.
> Yours,
> Daniel
>
> On Thu, Oct 20, 2022
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,
>
> Than
"been"
>
> Section: A.1, draft text:
> Once the registrar has been selected, the HNA redirects the end user to
> that
> registrar in order to receive a access token. Warning: Use an instead of
> 'a'
> if the following word starts with a vowel sound, e.g. 'an article', 'an
&
t;dedicated IP address for the DM.
>>
>> should be moved to section 4.4 if this consideration is also true for
>> section
>> 4.3.
>>
>> correct. I just copied the lines.
>
>>
>>
>> ___
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
>
>
> --
> Daniel Migault
> Ericsson
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
ed the lines.
>
>
> _______
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
present
> participle
> "expecting" here.
>
>
> ## Notes
>
> This review is in the ["IETF Comments" Markdown format][ICMF], You can use
> the
> [`ietf-comments` tool][ICT] to automatically convert this review into
> individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].
>
> [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
> [ICT]: https://github.com/mnot/ietf-comments
> [IRT]: https://github.com/larseggert/ietf-reviewtool
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
me of the limitations in Section 4 have been
> addressed,
> and others are arguably a feature and not a limitation.
>
>
>
> ___________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
The HNA SHOULD provide the hash of the KSK (DS RRset), so the DOI
> provides this value to the parent zone."
> C: Is it that the HNA should provide the DS, or a hash of the KSK? (The DS
> is
> more than just the hash). C: "so that the DOI
k is) this field as "Registered
> Homenet Domain (zone)". Should the latter be "Registered Homenet Domain
> (registered_domain)" instead? (Or, rename "registered_domain" in the CDDL
> as
> "zone"?)
changed thanks.
>
> ### Appendix B - 2119 keywords
>
> It's weird that you lead with "This section is non-normative" but then
> pepper
> the content with the RFC 2119 keyword "OPTIONAL". I think probably you
> don't
> mean it's "non-normative" (that generally means something like "this is an
> example, it doesn't define anything, it can safely be ignored"). Rather, I
> think you mean implementing it is optional. I think you could fix this by
> deleting the words "is non-normative and".
>
> changed.
> Also, "MANDATORY" isn't an RFC 2119 keyword but you've capitalized it like
> one.
> If you want to introduce your own keyword to put the the force of VERY
> SERIOUS
> NORMATIVE CAPITALIZATION behind this word, I think it would be a good idea
> to
> define it in your Terminology section, probably right after the RFC 2119
> boilerplate paragraph. Alternately, you could just change all your uses of
> "mandatory" and "optional" in this section to lower-case. It would still be
> clear, IMO.
>
> done
> ## NITS
>
> - "these names needs" --> "these names need"
> - "The remaining of the document" --> "the rest of the document"
> - "buys a domain name to a registrar" --> "buys a domain name from a
> registrar"
> - "DOI has a roof of ownership" --> "roof" should be... "proof"?
> - "as detaille din further details below" --> "as detailed below"
> - "rsynch" --> "rsync"
> - "meth of" --> "method"
>
> changed.
> ## Notes
>
> This review is in the ["IETF Comments" Markdown format][ICMF], You can use
> the
> [`ietf-comments` tool][ICT] to automatically convert this review into
> individual GitHub issues.
>
> [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
> [ICT]: https://github.com/mnot/ietf-comments
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
concern regarding mutual authentication.
Yours,
Daniel
On Wed, Oct 19, 2022 at 8:29 PM Matt Brown wrote:
> On Wed, Oct 19, 2022 at 3:25 PM Daniel Migault
> wrote:
> >
> > Hi Matt,
> >
> > Thanks for the review. I am only responding to the major comments - for
>
ust happen if a client retrieves a set of parameters, does things based on
> them, later retrieves the parameters again and the new ones don't match
> the old
> ones. If the parameters were subject to lease expiration, this would be an
> expected part of the lifecycle of the protoc
be focused on IPv6
> addresses. Section 1.1. seems to allow for IPv4. Please reflect that.
>
> This is correct, initially homenet was only IPv6 and the described
mechanism was extended to IPv4.
we added:
IPv4 Addresses are 4 bytes long leading to 2**32 possibilities.
With IPv6 addresses, the
nd on their own
>
> I always like getting the terminology lined up right away so the reader
> isn't reading ahead, but that is probably just me.
>
> tim
>
> (working on my dnsdir review also!)
>
>
>
>
>
>> --
>> Michael Richardson. o O ( IPv6 IøT consult
ative
Servers.
> I think there would be merit in this going for security review
> additionally.
> My specific minor concerns about this is about the concept of having a DNS
> service exposed to the internet on a CPE to enable the transmission of
> data
> between Homenet Naming Au
on 1.3.
>
> Similarly, Section 1.2 seems to talk about alternative solutions, before
> the
> solution in the draft has been clearly explained. I think it should be a
> separate section, later in the document.
>
> Q2:
>
> It is quite difficult to get a picture of how the mechanism
has been
> updated
> in the parent zone." - This statement is too authoritative, and conflicts
> with
> 4.2 which clarifies (correctly) that DS updates in the parent zone are
> optional. I suggest removing this statement, or correcting it to somethign
> like
> "Depending on configuration, the DOI may also be responsible...".
>
> already updated ( see my previous comment)
> 3.2: s/RECOMMENDED to use TLS with mutually authentication/RECOMMENDED to
> use
> TLS with mutual authentication/ - in the final sentence of the 2nd
> paragraph.
>
>
> done
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
1: s/detaille din/detailed in/ - in the final sentence of the first
> paragraph.
>
> 3.1: "The DOI is also responsible for ensuring the DS record has been
> updated
> in the parent zone." - This statement is too authoritative, and conflicts
> with
> 4.2 which clarifi
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
__
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
history - well done for sticking
> with
> it. I hope one day to buy a product which uses the end result of this
> work and
> transparently configures MY home network!
>
>
> _______
>
;
> Q2:
>
> It is quite difficult to get a picture of how the mechanism work. There
> are no
> examples, or step-by-step functionality/use-case descriptions. Also,
> Section
> 3.1 seems to be a mixture of architecture and functionality, which is a
> little
>
ited scope of scenarios that are assumed to be representative. Many
> other scenarios may be derived from these.
>
> s/section/Appendix/g and other fixes.
>
>
> _______
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/
ust as
> the one used to provide the IP prefix." In which features are similar? In
> which
> features are dissimilar?
>
> Thanks for this document,
>
> Ines.
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://w
gt; -éric-waiting-for-19 ;-)
>
>
>
> Also waiting for the revision of
> draft-ietf-homenet-front-end-naming-delegation-17 as my plan is to group
> the two I-D for the last call
>
>
>
> *From: *Daniel Migault
> *Date: *Tuesday, 20 September 2022 at 15:05
> *To: *
>
> We can aim to request the Last Call still this week if this I-D and the
> architecture revised I-Ds are quickly posted.
>
>
>
> Regards
>
>
>
> -éric
>
>
>
>
>
> *From: *homenet on behalf of Daniel Migault <
> mglt.i...@gmail.com>
> *Date: *Friday, 12
ve is not ‘to pass the id-nits’ examination but rather
> to give the readers the list of what they MUST read to implement
> (normative) and the list of useful links to understand (informative)
>
>
>
> Regards,
>
>
>
> -éric
>
>
>
> PS: going in vacation mode for on
companion document.
>
The purpose of the appendix was to show that these DHCP option cannot be
used by an ISP to prevent users from using their own registered domain
names. I do not think that better fits the companion document which
describes the architecture and protocols to outsource the DNS
dded was a plausible list of instances, but we are
> fine removing it.
>
> OLD:
>
> For a very few numbers (one to three) of hosts (media servers, VPN
> gateways, ... ),
>
> NEW:
>
> For a very few numbers of hosts,
>
>
>-
>
>
>
> Yours,
>
>
a very few numbers of hosts,
>
>-
>
>
>
Yours,
Daniel
> Please continue the good work
>
>
>
> Regards
>
>
>
> -éric
>
>
>
> [1] I am sure that you know
> https://www.ietf.org/about/groups/iesg/statements/normative-informative-refere
s/For a very few number/For a very few numbers/ ?
>
> ok
>
>
> ### Section 4.2
>
>
>
> `so the that DOI`? how to parse this ?
>
> changed to: so the DOI
>
>
> ### No comma before 'and'
>
>
>
> AFAIK, there is no comma before 'and', exception made for the Oxford comma
> of course.
>
>
>
ok - works for me.
> ### Section 4.2
>
>
>
> s/were/was/ ?
>
>
>
I cannot find it in section 4.2 it might have been changed addressing a
previous comment.
> ### Section 4.5
>
>
>
> s/long term session/long-term session/
>
>
>
ok
> ### Section 4.6
>
>
>
> Unbalanced parenthesis.
>
>
>
ok
> ### Section 4.7
>
>
>
> s/describe din/described in/
>
> ok
>
>
> ### Section 5
>
>
>
> Duplicate `toward a service a service`
>
>
>
ok
> ### Section 6
>
>
>
> s/is outside/are outside/ ?
>
>
>
ok
> ### Non-empty well-known
>
>
>
> Several missing '-' in 'non-empty' and 'well-known' (when applicable).
>
>
>
ok
> ### E.g.
>
>
>
> "E.g." should be enclosed in ','.
>
>
>
ok
> ### Section 9
>
>
>
> 'by by' ?
>
> ok
>
>
> ### Section 10
>
>
>
> s/privacy MAY be provide/privacy MAY be provided/
>
>
>
ok
> ### Section 11.1
>
>
>
> `To ensure the multiple TLS session are are continuously authenticating `
> duplicated 'are'
>
> ok
>
>
> s/This MAY Be handle by a off-line /This MAY be handled by an off-line/
>
>
>
ok
> ### DNS in uppercase
>
>
>
> There are a couple of 'dns' (lowercase) instances.
>
>
>
ok
> ## Notes
>
>
>
> This review is in the ["IETF Comments" Markdown format][ICMF], You can use
> the
>
> [`ietf-comments` tool][ICT] to automatically convert this review into
>
> individual GitHub issues.
>
>
>
> [ICMF]: https://github.com/mnot/ietf-comments/blob/main/format.md
>
> [ICT]: https://github.com/mnot/ietf-comments
>
>
>
>
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
ived during the 2021 WG last call ?
>
>
>
> Thank you very much for the work done, I know that the last mile can be
> very painful...
>
>
>
> Regards
>
>
>
> -éric
>
>
>
> [1]
> https://mailarchive.ietf.org/arch/msg/homenet/2yussyqUPAFf9gKNFNGw43ywA_Y/
&g
-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
Ralf Weber
ument. My
> apologies for the delay. Many thanks for addressing the first round of
> comments, the readability has improved quite a bit. The remainder of the
> comments are in the Github. Hope we will see a revision soon.
>
> Cheers,
> Kiran
>
>
> ----------
>
gt; (evyncke)"
> *Date: *Thursday, 14 April 2022 at 09:16
> *To: *"homenet@ietf.org"
> *Cc: *"kiran.i...@gmail.com" , Michael Richardson <
> mcr+i...@sandelman.ca>, Daniel Migault , Stephen
> Farrell
> *Subject: *Re: [homenet] naming drafts
>
&g
eople here want to pursue that.
>
> > I thought that you *wanted* to go to INTAREA with this document. I
> > agree that it's an important document.
>
> If we need to keep HOMENET open to do stub networks, then let's do that.
>
> _______
Hi,
Thanks for the follow up Chris. I apologize for the delay.
Yours,
Daniel
On Tue, Jun 22, 2021 at 12:31 PM Chris Box wrote:
> Daniel,
>
> On Wed, 16 Jun 2021 at 01:27, Daniel Migault wrote:
>
>>
>>> The HNA SHOULD drop any packets arriving on the WAN interfa
ine below.
>
> On Tue, 15 Jun 2021 at 02:58, Daniel Migault wrote:
>
>>
>>>
>> """
>> Limited exchanges:
>> : the purpose of the Hidden Primary Server is to synchronize with the DM,
>> not to serve any zones to end users, or the
I do not believe these drafts have received enough review or
>> support to put them forward as representing WG consensus.
>>
>> But the authors have spent significant effort in creating these drafts
>> and the associated implementation. We will work with Éric V (as INT area
>> AD) and the authors to determine next steps.
>>
>> Barbara and Stephen
>>
>> ___
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
wrote:
>
> Hiya,
>
> On 08/06/2021 14:55, Daniel Migault wrote:
> > I disagree that discussing whether the proposal will take over DDNS
> > is a side discussion that unfortunately happens at a bad time.
>
> Sorry, I don't get what you mean.
>
Let me try to prov
of
> review means there's no way to claim they represent any
> useful level of WG consensus.
>
> Cheers,
> S.
>
> _______
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
Hi Stephen,
Please find inline some responses or follow-up discussion.
Yours,
Daniel
On Wed, May 26, 2021 at 3:37 PM Stephen Farrell
wrote:
>
> Hiya,
>
> A few responses below...
>
> On 26/05/2021 18:02, Daniel Migault wrote:
> > Hi Stephen,
> >
> > Th
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
n
> [I-D.ietf-homenet-naming-architecture-dhc-options]."
>
>
The ISP manages a DOI for the IP prefix domain name, identifies the line to
which the IP prefix is assigned which makes out-of band configuration of
the client unnecessary. Without such out-of-band step, the process can be
completely automated.
> - section 9: "2001:db8:babe:0001::2" - the string "babe" has
>both innocent and less innocent interpretations, not sure if
> you want to risk the latter being some reader's interpretation.
>
>
Thanks. You are correct I prefer not to take the risk. When reading I did
not go further than it is a word and the one I know is a kid's movie, so I
did not pay attention. I changed it to aeae.
- section 10: you use a different example here from earlier,
>just one is probably better, unless there's a reason they
> ought differ.
>
>
Changed to myhome.example. Thanks.
> - 11.1: is a subsection needed there really? (I kinda skipped
>all that text TBH;-)
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
On Fri, May 14, 2021 at 11:17 AM Michael Richardson
wrote:
>
> Daniel Migault wrote:
> > Please find the new version that is considering the discussions of
> the
> > mailing list as well as comments received from Med.
>
> Daniel, I was just proofreading, an
-delegation-15.txt
To:
Cc:
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
cline 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 yo
is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Home Networking WG of the IETF.
Title : DHCPv6 Options for Home Network Naming Authority
Authors : Daniel Migault
Ralf Weber
ibuted, 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
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
nd 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
ted to
> raise it as it probably isn’t considered as often as it should be.
>
>
>
>- Bernie
>
>
>
> *From: *Daniel Migault
> *Date: *Wednesday, May 12, 2021 at 1:11 PM
> *To: *Michael Richardson
> *Cc: *Ted Lemon , int-a...@ietf.org ,
> dh...@ietf.org , dns
Sounds good to me. Anyone objecting DIstribution Manager ? If not I will
consider this terminology.
Yours,
Daniel
On Wed, May 12, 2021 at 5:11 PM Michael Richardson
wrote:
>
> Daniel Migault wrote:
> > "Distribution Primary" is probably my preferred alternative as t
1 - 100 of 165 matches
Mail list logo
