Re: [homenet] congrats!

[Extending to homenet as the concluded WG list should still exist] Indeed, congratulations to the authors, shepherds, WG chairs ! It has been a long path, but all main documents are now published, and SNAC WG (a spin-off) is thriving. Regards -éric On 29/01/2024, 11:36, "Stephen Farrell"

[homenet] FW: Protocol Action: 'Service Identity in TLS' to Proposed Standard (draft-ietf-uta-rfc6125bis-15.txt)

FYI, Once this document is published, it will unblock the last two approved but not yet published Homenet documents: - draft-ietf-homenet-front-end-naming-delegation-27 - draft-ietf-homenet-naming-architecture-dhc-options-24 See also https://www.rfc-editor.org/cluster_info.php?cid=C472 (even if

[homenet] Closing Homenet (was Re: Homenet Mission accomplished ?)

and congratulations to all participants, past and active chairs, past AD for the hard work done. Regards -éric [1] draft-ietf-uta-rfc6125bis From: homenet on behalf of "Eric Vyncke (evyncke)" Date: Wednesday, 1 February 2023 at 10:07 To: "homenet@ietf.org" Subject: [home

[homenet] Homenet Mission accomplished ?

Dear Homenet, As you may have read on https://datatracker.ietf.org/wg/homenet/documents/ the last WG documents have been approved for publication: - draft-ietf-homenet-front-end-naming-delegation-26 had a major rewrite end of 2022 and the intended status is now experimental per IESG request -

Re: [homenet] Intdir telechat review of draft-ietf-homenet-front-end-naming-delegation-25

s confuse semantics, but it’s in a very poor state compared to other draft that I’ve reviewed at a close to Ready state. The suggestion to move it to Experimental is good, imo. Tim On 6 Jan 2023, at 11:56, Eric Vyncke (evyncke) wrote: Thank you very much Tim for your review for int-dir.

Re: [homenet] Intdir telechat review of draft-ietf-homenet-front-end-naming-delegation-25

Thank you very much Tim for your review for int-dir. Even if a little too late for the IESG telechat, I am sure that the authors will take your review in consideration. I personally like your suggestion to add an appendix section on the deployment/operation timeline. Regards -éric On

Re: [homenet] Datatracker State Update Notice:

Dear authors, dear Homenet WG, Happy New Year ! As you may have noticed, the I-D was not approved on yesterday telechat. The IESG was unanimous to say that the latest revision is much more readable and clearer. Barring the DNS-directorate and the late GENART reviews (to be addressed at least

Re: [homenet] Dnsdir telechat review of draft-ietf-homenet-front-end-naming-delegation-25

Geoff, Thank you very much for this detailed review, I am sure that it will assist the IESG in their 2nd evaluation. Regards -éric On 18/12/2022, 00:36, "Geoff Huston via Datatracker" mailto:nore...@ietf.org>> wrote: Reviewer: Geoff Huston Review result: Ready with Issues I have been

Re: [homenet] Next actions for I-D Action: draft-ietf-homenet-front-end-naming-delegation-24.txt

2022 at 8:11 AM Daniel Migault mailto:mglt.i...@gmail.com>> wrote: On Wed, Dec 7, 2022 at 7:56 AM Michael Richardson mailto:mcr%2bi...@sandelman.ca>> wrote: Eric Vyncke (evyncke) mailto:evyn...@cisco.com>> wrote: > As the text has changed a lot, not so much on the technical conten

[homenet] Next actions for I-D Action: draft-ietf-homenet-front-end-naming-delegation-24.txt

As already written, thanks again to the authors (and mainly Michael and Daniel who recently updated the document). As the text has changed a lot, not so much on the technical content but more or completeness and readability, I will re-submit it to another IESG evaluation early January in the

Re: [homenet] Homenet NA bike shed opportunities: terminology DOI

[Obviously with any hat on a late Sunday evening...] Michael, Let's work on bike shedding [1], it is always easier and funnier ;-) DOS: DNS Outsourcing Services EDI: External DNS Infrastructure Or somehow more seriously: NOS: Naming Outsourcing Services NES: Naming External Services NEOS:

[homenet] AD submission for draft-ietf-homenet-front-end-naming-delegation

Bonjour Daniel, As it seems that you and Michael have worked a lot of this I-D and as it appears to be ready for submission, may I suggest that you submit it manually *even* during this no-submission period ? I will then approve it as it may unblock the DISCUSS points. Send the XML to

Re: [homenet] Lars Eggert's Abstain on draft-ietf-homenet-naming-architecture-dhc-options-22: (with COMMENT)

Michael's point is indeed important: reverse DNS and, IMHO, justifies the whole effort of the two related I-Ds. Whether they will be implemented is still a valid question... Regards -éric On 21/10/2022, 08:50, "homenet on behalf of Michael Richardson" wrote: Lars Eggert via

[homenet] FW: Formal IESG Teleconference WebEx and Dial-in Information:20 October 2022

Dear Homenet, You may find interesting to attend as a silent observer to this telechat next week as the last 2 remaining I-D of our Homenet WG will be balloted and hopefully approved by the IESG. I expect the Homenet document to be discussed within the first hour. This is of course *optional*

Re: [homenet] [dnsdir] Dnsdir telechat review of draft-ietf-homenet-front-end-naming-delegation-18

Thank you for your first (if not mistaken) review at the IETF: it is detailed and I am sure that the authors will also reply to you. Regards -éric On 12/10/2022, 14:26, "dnsdir on behalf of Anthony Somerset via Datatracker via dnsdir" wrote: Reviewer: Anthony Somerset Review

Re: [homenet] AD review of draft-ietf-homenet-naming-architecture-dhc-options-16

ompanion document we can easily publish such a document. Yours, Daniel On Tue, Sep 20, 2022 at 8:17 AM Eric Vyncke (evyncke) mailto:evyn...@cisco.com>> wrote: Daniel, Ralf, Tomek, Thank you for posting the -17 revision. Before requesting the IETF Last Call, I kindly request one small

Re: [homenet] AD review of draft-ietf-homenet-naming-architecture-dhc-options-16

why "PS" is the right intended status? 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 Date: Friday, 12 August 2022 at 02:04 To: "Eric Vyncke (evync

[homenet] FW: [Snac] WG Review: Stub Network Auto Configuration for IPv6 (snac)

As this is the follow-up of Ted Lemon's work on 'stub neworks' in the Homenet WG, you may find useful to review this proposed WG charter. -éric On 10/09/2022, 07:01, "The IESG" wrote: A new IETF WG has been proposed in the Internet Area. The IESG has not made any determination yet.

[homenet] Status of draft-ietf-homenet-front-end-naming-delegation and draft-ietf-homenet-naming-architecture-dhc-options after the AD review

Just want to check what is the current status of those 2 documents after my AD review of the 8th of August. AFAIK, the authors have prepared a revised I-D addressing all the comments, so we should be ready to launch the IETF Last Call once the revised IETF drafts are uploaded. And I understand

[homenet] AD review of draft-ietf-homenet-naming-architecture-dhc-options-16

As usual, I do my own review before requesting the IETF Last Call for all documents. The intent is to give another polishing pass on the I-D. For this review, the MD format is used. Hope this helps Regards -éric # Éric Vyncke, INT AD, comments for

[homenet] AD review of draft-ietf-homenet-front-end-naming-delegation-16

As usual, I do my own review before requesting the IETF Last Call for all documents. The intent is to give another polishing pass on the I-D. For this review, the MD format is used. Hope this helps Regards -éric # Éric Vyncke, INT AD, comments for

Re: [homenet] Fwd: I-D Action: draft-ietf-homenet-front-end-naming-delegation-16.txt

Daniel, and other authors, Does this version address all comments received during the 2021 WG last call [1] ? There is also a new version of the DHCP part, does this version also address all comments received during the 2021 WG last call ? Thank you very much for the work done, I know that

Re: [homenet] naming drafts

o:s...@ietf.org> mailing list). Therefore, the plan is to close Homenet early July 2022 if nothing changes. Hoping to see you in “Philly” to celebrate the achievments of Homenet ! Regards -éric From: homenet on behalf of "Eric Vyncke (evyncke)" Date: Thursday, 14 April 2022 at 09

Re: [homenet] naming drafts

Dear Homenet, After 9 months, it is time to resurrect this email thread and move forward with the 'naming drafts', which are still in WG Last Call since May 2021: * draft-ietf-homenet-front-end-naming-delegation - draft-ietf-homenet-naming-architecture-dhc-options AT IETF-113,

[homenet] Barbara is officially stepping down as homenet and dnssd chair

Barbara Stark just contacted me and the Homenet chairs (Stephen Farrel and Kiran Makhijani) with the message that she is ready to step down from her duties as the Homenet co-chair. This was announced months ago, and Kiran has stepped forward as co-chair for Homenet. I am sure that Barbara

Re: [homenet] Looking for a Homenet co-chair

Dear all, Even if the Homenet WG will probably close in the coming months, I am adding a third chair to the WG (planning for Barbara's departure from her active role) and am happy to announce that Kiran Makhijani has accepted to take the position of the 3rd chair. So, please welcome her ;-)

Re: [homenet] Should homenet continue ?

[Changing the subject header to better reflect the current discussion] Stephen, I agree with you: let's continue this thread about homenet WG continuation until mid-September. To be honest, I am wondering whether there is WG momentum as only active IETF drafts authors are replying to this

[homenet] Looking for a Homenet co-chair

Dear all, As you are probably aware, Barbara Stark is retiring from her WG chair position after IETF-112 and I now have ‘mission impossible n++’ to find a new WG chair to assist Stephen Farrel. As Stephen is an experimented WG chair, having a ‘junior’ co-chair would be welcome (of course

Re: [homenet] [Editorial Errata Reported] RFC8375 (6378)

Dear all, I will reject the errata as the WG consensus is to reject it. Kulvinder, thank you for submitting it (even if finally rejected) Regards and Happy New Year to all -éric -Original Message- From: homenet on behalf of "STARK, BARBARA H" Date: Saturday, 2 January 2021 at

Re: [homenet] ISPs using DHCP for individual clients

Subject: Re: [homenet] ISPs using DHCP for individual clients On Sat, 21 Nov 2020, Eric Vyncke (evyncke) wrote: > The idea to identity the kind of devices (hence any QoE) based on MAC > address (probably on the OUI part) has work for many years; but, now > more and more

Re: [homenet] ISPs using DHCP for individual clients

Hi Mikael, The idea to identity the kind of devices (hence any QoE) based on MAC address (probably on the OUI part) has work for many years; but, now more and more OS do MAC address randomization (cfr the MADINAS BoF at IETF-109), so, I am afraid that this 'easy/smart' technique is a thing of

Re: [homenet] draft-ietf-homenet-front-end-naming-delegation

Daniel, thank you for the update on this draft. May the WG expect a revised I-D (and possibly one for the DHCPv6 draft) in the coming days? Regards -éric From: homenet on behalf of Daniel Migault Date: Friday, 9 October 2020 at 19:22 To: homenet Subject: [homenet]

Re: [homenet] https://tools.ietf.org/id/draft-ietf-mboned-ieee802-mcast-problems-09.txt

Ray and Christophe and others, As the responsible AD for this draft, would you mind forwarding/adding mbo...@ietf.org to the recipient list? So that authors can read your valuable comments? Thank you -éric From: homenet on behalf of "Ray Hunter (v6ops)" Date:

Re: [homenet] HNCP: avoiding renumbering

I think that Brian has summarized this renumbering avoidance as desirable but nothing to be depended on -éric On 17/08/15 08:57, homenet on behalf of Toerless Eckert (eckert) homenet-boun...@ietf.org on behalf of eck...@cisco.com wrote: On Mon, Aug 17, 2015 at 09:41:24AM +0300, Markus Stenberg

Re: [homenet] [ieee-ietf-coord] Multicast on 802.11

On 12/08/15 07:51, homenet on behalf of Henning Rogge homenet-boun...@ietf.org on behalf of hro...@gmail.com wrote: The problem is we are dealing with more and more wireless devices, so the medium starts to become congested more easily. 0.1% - 1% packet loss (not frame loss) is possible for

Re: [homenet] WiFi handover [was: question: equal-cost multipath?]

While I pay for it, I never use the millions of WiFi access points I can use here in the Netherlands. I tried it once, walking in a small city. At the time the handover was completed, the connectivity was gone. It might have to do with IEEE and IETF mismatch. Same SSID shall have same IP subnet

Re: [homenet] WiFi handover [was: question: equal-cost multipath?]

On 12/08/15 15:18, Teco Boot t...@inf-net.nl wrote: How works *seamless* WiFi handover with same SSID, with different IPv6 subnets? Single subnet for a neighborhood, with all the multicast suppression? Single subnet for a country? Not sure whether 'community wifi' belongs to this alias but

Re: [homenet] 802.11 is just fine for IPv6 [was: Despair]

To come back on the discussion why mcast matters for IPv6 while bcast does not for IPv4: - IPv6 uses heavily mcast while in IPv4 (ND is quite chatty) - IPv6 uses many more addresses than IPv4 (hence even more chatty) A couple of us running very large (more than 1 STA) WiFi network have