verse lookup is very small, so I
> > don’t think there’s any reason to be concerned about this.
>
> I agree with you completely.
>
> --
> Michael Richardson. o O ( IPv6 IøT consulting )
>Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
n controller
> Distribution governor
> Distribution center
> Distribution central
>
> Grüße, Carsten
>
> _______
> 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
rme 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
> 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
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
Tomek
we instead be using a DNS URI from
> https://tools.ietf.org/html/rfc4501?
>
> That reduces the DM spec to a single parameter that is also extensible for
> the future.
>
> regards,
>
> Daniel Migault wrote on 01/04/2021 18:18:
>
> Hi Bernie,
>
> I apology for missing that em
ft 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
to
>
>be referenced symbolically in the Internet-Drafts that describe them,
>
>and shall be assigned numeric codes by IANA when approved for
>
>publication as an RFC.
>
>
>
> Two “BV>” comments in-line below.
>
>
>
>- Bernie
>
>
&
Hi Bernie,
I apology for missing that email. Your comments addressed an old version,
however most of them applies to the new version. I think all comments have
been addressed on my working local copy and I provide more details on how we
addressed them.
I do have one remaining question regardi
DANE? I guess I'll have to read it.
>
> Mike
>
> ___
> 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
PM
To: Chris Griffiths ; Daniel Migault
; Ralf Weber ; Tomek
Mrugalski ; Wouter Cloetens
Subject: New Version Notification for
draft-ietf-homenet-naming-architecture-dhc-options-09.txt
A new version of I-D, draft-ietf-homenet-naming-architecture-dhc-options-09.txt
has been successfully
ddress, v6 tunnel endpoint hint).
>
> Thanks,
> Ian
>
>
> On 20. Nov 2020, at 09:37, Daniel Migault wrote:
>
> Hi,
>
> While designing the DHCP options to configure the HNA we asked ourselves
> how likely ISP are:
>
> A) How an ISP is likely to perform an act
more in line with what is currently deployed.
Yours,
Daniel
On Fri, Nov 20, 2020 at 4:06 AM Mikael Abrahamsson wrote:
> On Fri, 20 Nov 2020, Daniel Migault wrote:
>
> > Hi,
> >
> > While designing the DHCP options to configure the HNA we asked ourselves
> > how lik
,
Daniel
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
tive
> method of individualizing the bootstrap process?
>
It seems to be fine to provide an individualized response. In our case I
see the DHCP doing an individual action based on the request. That is good
to get early feed back from ISP. Thanks!
>
> regards,
>
> Daniel Migaul
Hi, I posted a revised document, but there are still issues that I don't
> expect to work out until Ray and I put his code through some more testing.
>
> --
> Michael Richardson. o O ( IPv6 IøT consulting )
>Sandelman Software Works In
Home Network Naming Authority
Authors : Daniel Migault
Ralf Weber
Tomek Mrugalski
Chris Griffiths
Wouter Cloetens
Filename:
draft-ietf-homenet-naming-architecture
in
> the coming days?
>
>
>
> Regards
>
>
>
> -éric
>
>
>
> *From: *homenet on behalf of Daniel Migault <
> mglt.i...@gmail.com>
> *Date: *Friday, 9 October 2020 at 19:22
> *To: *homenet
> *Subject: *[homenet] draft-ietf-homenet-front-end
parameters}" may also be removed / merged with
hna-provisionning
6.
Maybe hna-provisionning section can be put in the appendix.
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
re (like maybe
> INT area).
>
> If you disagree, this is best expressed this through technical discussion
> and activities.
> Thx,
> Barbara
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://ww
Hi,
So my notes/comments regarding the feedbacks received are:
* mentioning the work on axfr over tls
* cds needs to be placed in the homenet zone by the HNA
* considering factory reset and removal of the provisioned keys ? - we need
to think of this scenario.
* securing the synchronization betwee
Hi,
Please find our updated draft for outsourcing the DNS authoritative servers.
Any comments are appreciated!
Yours,
Daniel
-Original Message-
From: internet-dra...@ietf.org
Sent: Sunday, November 17, 2019 2:48 AM
To: Wouter Cloetens ; Michael Richardson
; Daniel Migault ; Ralf
The question to the WG is whether this worth being tried, or if we are
missing something. Any thoughts, feed back would be appreciated.
Yours,
Daniel
On Tue, Jun 18, 2019 at 10:56 AM Daniel Migault
wrote:
> Hi Ray,
>
> Thanks for the feed back, I have tried to look at how thes
18, 2019, at 10:56 AM, Daniel Migault
> wrote:
>
> I am also questioning on whether we should provide some sort of
> recommendations for the UI. While we are not UI designers, I believe some
> properties could be interesting for designers, and those may be helpful to
> be provid
ould be an option.
On Sun, Jun 9, 2019 at 7:52 AM Ray Hunter (v6ops) wrote:
>
>
> Daniel Migault wrote on 07/06/2019 22:27:
>
> Hi,
>
> We are looking for a simple way to configure the primary / secondary DNS
> setting between the homenet and the outsourcing infra
Hi Juliusz,
I believe the answer is similar to [1]. Regarding the number of devices we
expect, it seems hard to have exact prediction, however, if we do not make
it possible this number will likely remain zero. We need to make it easier
to have more devices.
Currently services mostly send private
like a good option to look at.
>
>
>
> Jacques
>
>
>
>
>
>
>
> *From:* homenet *On Behalf Of *Daniel Migault
> *Sent:* June 7, 2019 4:03 PM
> *To:* homenet
> *Subject:* [EXT] [homenet] securing zone transfer
>
>
>
> Hi,
>
>
>
> The front e
Hi,
We are looking for a simple way to configure the primary / secondary DNS
setting between the homenet and the outsourcing infrastructure. The
exchange of these information is done over a secure channel - let say TLS.
While we coudl re-define a configuration template / mechanism we believe
that
Hi,
The front end naming architecture uses a primary and a secondary dns server
to synchronize a zone. The expected exchanges are (SOA, NOTIFY, IXFR, AXFR.
We would like to get feed backs from the working group on what are the most
appropriated way to secure this channel.
Options we have consider
Hi Juliusz,
If I understand correctly the question is why do we have a Homenet Naming
Authority responsible to outsource the Homenet Zone to the Public
Authoritative Servers ( Front End architecture) instead of having each
device updating their data directly to the Public Authoritative Servers
(
Hi,
I am planning to update the front end naming delegation draft [1] in the
next weeks. Before revisiting the draft, I am collecting comments that need
to be addressed.
The draft has been waiting the naming architecture draft become more
advanced. I believe this now achieved.
The main comments
team – maybe if editors could unicast me
> with your github user names?
>
>
>
> Next is -dhc-options. I see Tomek has been doing things, so I don’t want
> to set up the repository for this one till I know I have the latest.
>
> Barbara
>
>
>
>
>
>
>
>
Hi,
To ease collaboration I have converted to mkd the following drafts
https://github.com/mglt/ietf-homenet-hna
https://github.com/mglt/ietf-homenet-hna-dhcp
I suggest we focus on the front-end-naming architecture draft, and I will
catch up comments I have not yet answered.
During IETF102, I git
Hi Denis,
Thanks for the feed back! The big read arrow symbolized the synchronization
between the zone hosted on your HNA and the DNS Public server on the
outsourcing infrastructure. This could be your ISP or any third party. One
of the motivation to outsource was to prevent DDoS attack on the HNA
So far the only interaction discussed was to set a specific name. What
other minimal interactions the WG could think of ?
Yours,
Daniel
On Thu, May 31, 2018 at 5:22 PM, Brian E Carpenter <
brian.e.carpen...@gmail.com> wrote:
> On 01/06/2018 00:07, David R. Oran wrote:
> > On 30 May 2018, at 19:
Hi Andrew,
Thanks you for providing the feed backs. An few comments inline.
On Mon, May 28, 2018 at 2:05 PM, Andrew Sullivan
wrote:
> Hi,
>
> Thanks for doing this. Some comments inline. These may seem a little
> picky in a few cases, but I figure it's better to make the corrections
> as we
ginal Message-
From: secdir [mailto:secdir-boun...@ietf.org] On Behalf Of Daniel Migault
Sent: Friday, August 18, 2017 12:44 PM
To: sec...@ietf.org
Cc: draft-ietf-homenet-dot@ietf.org; homenet@ietf.org; i...@ietf.org
Subject: [secdir] Secdir last call review of draft-ietf-homenet-dot-12
Rev
Reviewer: Daniel Migault
Review result: Has Nits
Thank you for writing the draft. Please find my comments. I hope there are
helpful.
Yours,
Daniel
Special Use Domain 'home.arpa.'
draft-ietf-homenet-dot-12
Abstract
This document spe
eir
> statements before the call ends.
> > Barbara
> >
> > From: homenet [mailto:homenet-boun...@ietf.org] On Behalf Of Daniel
> Migault
> > Sent: Wednesday, August 09, 2017 2:37 PM
> > To: Michael Richardson
> > Cc: homenet@ietf.org
> > Subject: Re:
Hi,
I apology for the late response (I was off for two weeks). I will update
the draft by the end of the month integrating numerous feed backs we
received.
As a co-author I am supporting the adoption of this document architecture.
I believe that given the current situation regarding homenet and n
,
Daniel
-Original Message-
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org]
Sent: Wednesday, September 23, 2015 10:47 PM
To: Ralf Weber; Wouter Cloetens; Ray Hunter; Daniel Migault; Chris Griffiths;
Ray Hunter; Wouter Cloetens; Chris Griffiths; Ralf Weber; Daniel Migault
Hi Ray,
Thank you for the comments. Please see inline my response.
BR,
Daniel
I have just read through
> https://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dhc-options-02
> again
>
> Generally, it is looking pretty good.
>
> A couple of comments:
>
> 1. The use of the name "Secur
Networking Working Group of the IETF.
Title : DHCP Options for Homenet Naming Architecture
Authors : Daniel Migault
Wouter Cloetens
Chris Griffiths
Ralf Weber
Filename:
draft
f the Home Networking Working Group of the IETF.
Title : Outsourcing Home Network Authoritative Naming Service
Authors : Daniel Migault
Wouter Cloetens
Chris Griffiths
Ralf Weber
Hi,
Thanks for the comments. We have also discussed this issue during the
meeting in Dallas, I will provide a version soon.
BR,
Daniel
On Fri, Apr 3, 2015 at 3:46 PM, Ray Hunter wrote:
> Apologies for the very late reply: change weekends.
>
> Daniel Migault
> 20 March 201
ence of multiple
> CPEs should be made explicit in the draft. I refer you to RFC 7368
> Section 3.2.4.
>
> Thanks for listening,
>
> -- Juliusz
>
> ___
> homenet mailing list
> hom
ce IP address agnostic.
>
This is the case, as authentication is based only cryptographic keys. The
IP address is only used for reach-ability and is never used otherwise.
>
> --
> Regards,
> RayH
>
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
to be able to support
> both. I hope you can adjust the text to allow both.
>
> Brian
>
--
Daniel Migault
Ericsson
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
On Wed, Mar 4, 2015 at 7:23 AM, Ray Hunter wrote:
>
>
> Daniel Migault wrote:
>
>> Hi,
>>
>> Please find the new version of DHCP Options for Homenet Naming
>> Architecture <https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-
>> architec
ilable from the on-line Internet-Drafts
directories.
This draft is a work item of the Home Networking Working Group of the IETF.
Title : DHCP Options for Homenet Naming Architecture
Authors : Daniel Migault
Wouter Cl
s.
This draft is a work item of the Home Networking Working Group of the IETF.
Title : Outsourcing Home Network Authoritative Naming
Service
Authors : Daniel Migault
Wouter Cloetens
Chris Griffiths
mment, our use case is: outsourcing the
DNS service of your homenet to a dedicated infrastructure.
Working code would make everyone happier, of course.
>
>
Of course, we think the protocols are now mature enough to have it, and we
should be able to have one soon.
> In the current situatio
the PA draft and the two Naming drafts in a single reply.
>
> thanks,
>
> Ray and Mark
>
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
--
Daniel Migault
Oran
;> Suppose your ISP has a connectivity issue, even a node in your home
> >>> network will not be able to contact your web server as the DNS(SEC)
> >>> resolution is not possible.
>
> >> But my nodes are still running mDNS/zeroconf, right?
>
> > By the way,
>> Suppose
>> > you have n devices in the home network and a renumbering occurs. All
>> these n
>> > devices will contact the Public Authoritative Server that may be miles
>> away
>> > from your home network.
>>
>> I've got 100 devices. I
. My abacus has a four-core chip.
>
> > - CPE can integrate multiple protocols to publish a zone. Suppose
> mDNS is
> > used by a node, than registration of its IP address and name cannot be
> > perfomed on a public authoritative server cannot be performed using mDNS.
>
Griffiths
, Ralf Weber
, Daniel Migault
, Wouter Cloetens
, Daniel
Migault
A new version of I-D, draft-mglt-homenet-front-end-naming-delegation-04.txt
has been successfully submitted by Daniel Migault and posted to the
IETF repository.
Name: draft-mglt-homenet-front-end-naming-delegation
up a web server
> on my home network, I'd expect that negotiating a DNS registration is
> a private matter between the web server and the authoritative DNS master;
> why would I want the CPE to act as intermediary?
>
> Thanks,
>
> -
t-mglt-homenet-front-end-naming-delegation.
Feel free to make comments!
Daniel
[1]
http://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options/
--
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58
___
homenet mailin
ress these cases. [Text on that is welcome]
BR
Daniel
-- Forwarded message ------
From: Daniel Migault
Date: Thu, Feb 13, 2014 at 5:37 PM
Subject: draft-mglt-homenet-naming-architecture-dhc-options-01
To: "homenet@ietf.org"
Hi,
Please find the new version of the draf
http://www.ietf.org/id/draft-mglt-homenet-front-end-naming-delegation-03.txt
[2]
http://www.ietf.org/internet-drafts/draft-mglt-homenet-naming-architecture-dhc-options-01.txt
-- Forwarded message --
From: Daniel Migault
Date: Thu, Feb 13, 2014 at 5:37 PM
Subject: draft-mglt-h
successfully submitted by Daniel Migault and posted to the
IETF repository.
Name: draft-mglt-homenet-naming-architecture-dhc-options
Revision: 01
Title: DHCP Options for Homenet Naming Architecture
Document date: 2014-02-13
Group: Individual Submission
Pages: 18
URL:
http://www.ietf.org/internet
*De :* homenet-boun...@ietf.org [mailto:homenet-boun...@ietf.org] *De la
> part de* Daniel Migault
> *Envoyé :* dimanche 20 octobre 2013 21:48
> *À :* homenet@ietf.org
> *Objet :* [homenet] Fwd: New Version Notification for
> draft-mglt-homenet-front-end-naming-delegation-03.txt
>
have a
> problem adding stuff like dnssec roots to their data model.
>
> Mike
>
> __**_
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/**listinfo/homenet<https://www.ietf.org/mailman/listinfo/homenet>
>
--
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
ony.n.finchhttp://dotat.at/
> Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at
> first.
> Rough, becoming slight or moderate. Showers, rain at first. Moderate or
> good,
> occasionally poor at first.
>
--
Daniel Migault
Orange Labs -- Security
+33
y for the proper ICANN website and
> > grab the trust anchor bundle (i.e. what unbound-anchor does) and use the
> > certificate of ICANN.
>
> See also draft-jabley-dnsop-validator-bootstrap-00.
>
>
> Joe
>
--
Daniel Migault
Orange Labs -- Security
+33 6 70 72 6
Hi Paul,
Thanks for your comments. I also share your opinions. I add my comment in
the body part.
On Mon, Oct 21, 2013 at 8:16 PM, Paul Wouters wrote:
> On Mon, 21 Oct 2013, Daniel Migault wrote:
>
> Please find a draft that defines DHCP options to provision DNSSEC
>> valid
it?
>
> The only benefit for the client is that it can decide between sending a
message with "Options not supported" or "Badly configured Homenet Naming
Architectures". We can remove this requirement.
> - Bernie (from iPad)
>
> On Oct 20, 2013, at 3:52 PM, "D
--
From:
Date: Mon, Oct 21, 2013 at 9:12 AM
Subject: New Version Notification for
draft-mglt-homenet-dnssec-validator-dhc-options-02.txt
To: Daniel Migault
A new version of I-D, draft-mglt-homenet-dnssec-validator-dhc-options-02.txt
has been successfully submitted by Daniel Migault and posted
lt-homenet-naming-architecture-dhc-options-00.txt
To: Wouter Cloetens , Chris Griffiths <
cgriffi...@dyn.com>, Daniel Migault , Ralf Weber <
ralf.we...@nominum.com>
A new version of I-D,
draft-mglt-homenet-naming-architecture-dhc-options-00.txt
has been successfully submitted by Daniel
nts!
Best Regards,
Daniel
-- Forwarded message --
From:
Date: Sun, Oct 20, 2013 at 9:41 PM
Subject: New Version Notification for
draft-mglt-homenet-front-end-naming-delegation-03.txt
To: Wouter Cloetens , Chris Griffiths <
cgriffi...@dyn.com>, Daniel Migault , Ralf
: Wouter Cloetens , Chris Griffiths <
cgriffi...@dyn.com>, Daniel Migault , Ralf Weber <
ralf.we...@nominum.com>
A new version of I-D, draft-mglt-homenet-front-end-naming-delegation-02.txt
has been successfully submitted by Daniel Migault and posted to the
IETF repository.
Filename:
fic scenarios we need to address?
>
> How much of it is necessary?
>
> Best,
>
> A
>
> --
> Andrew Sullivan
> a...@anvilwalrusden.com
> _______
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/list
...@gmail.com
Cc: chris_griffi...@cable.comcast.com, wouter.cloet...@softathome.com,
philippe.lemord...@orange.com
A new version of I-D, draft-mglt-homenet-front-end-naming-delegation-01.txt
has been successfully submitted by Daniel Migault and posted to the
IETF repository.
Filename:draft-mglt
Hi Stéphane,
Thank you for reading the drafts. My responses are added in the text.
On Mon, Jul 16, 2012 at 4:09 PM, Stephane Bortzmeyer wrote:
> On Tue, Jul 03, 2012 at 12:11:54PM +0200,
> Daniel Migault wrote
> a message of 155 lines which said:
>
> > Please find two Namin
enet, it's much easier for everyone if "homenet" is
> somewhere in the filename of the draft. Please consider resubmitting, if
> that is your intention.
>
> Thank you,
>
> - Mark
>
> On Jul 3, 2012, at 12:11 PM, Daniel Migault wrote:
>
> Hi,
>
>
e initial DNS query.
The negotiation between the CPE and the ISP is using DHCP Options.
This document provides options so Front End Delegating and the
Delegated DNS Servers configure their respective Zone files and so
that CPEs restrict access and protect themselves from unauthoriz
101 - 177 of 177 matches
Mail list logo
