Re: [dhcwg] Fwd: New Version Notification for draft-mglt-homenet-naming-architecture-dhc-options-00.txt

Hi,

Thanks for reading it even "lightly and not thoroughly" ;-). My response is
in the text below and we will try to make it clearer in the next versions.

On Mon, Oct 21, 2013 at 12:19 AM, Sten Carlsen <stenc@s-carlsen.dk> wrote:

>  Hi
>
> Having read this lightly and not thoroughly it strikes me that it almost
> amounts to hijacking the customers own naming efforts?  If I read this
> wrongly, please excuse, my opinions may not be the general opinions.
>
> Actually that is the reverse. The DHCP options  makes possible for a user
to define its naming configuration for the homenet and push it to any CPE
that is plugged. This avoids reconfiguration when changing CPE or when the
CPE settups are erased.
Although specific configuration may concern a fraction of end users, we
believe the large portion of end users, prefers a default naming settings
that may be proposed by the DHCP.

> The way I see this, is that either I know what I want and make my own
> DNS-entries or I don't care, in which case there is no meaning in doing
> naming for people, specially as these namings will likely not be meaningful
> to people.
>
> Well, most of our end users do not really care about configuring DNS
architectures for their home network. At most they want it to work on a
specific domain name "example.com" so they can reach there service like "
myvideo.example.com"  from outside the homenet. This latest name is
meaningful for them, they are interested in the naming service to work
properly. However,  they are not interested in deep understanding of the
naming architecture and most probably not in how to perform key roll over.
It looks these end users are just in between your two alternatives.

Note also that you can also just ignore the DHCP Options.

Just my 0.02€
>
>
> On 20/10/13 21.51, Daniel Migault wrote:
>
> Hi,
>
>  Please find a description of DHCP options intended to configure the "IPv6
> Home Network Naming Delegation". [1]
>
> Feel free to make comments!
>
>  Best Regards,
> Daniel
>
> URL:
> http://www.ietf.org/internet-drafts/draft-mglt-homenet-naming-architecture-dhc-options-00.txt
> Htmlized:
> http://tools.ietf.org/html/draft-mglt-homenet-naming-architecture-dhc-options-00
>
>  [1]
> http://www.ietf.org/internet-drafts/draft-mglt-homenet-front-end-naming-delegation-03.txt
>
>
>
>  ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Sun, Oct 20, 2013 at 9:41 PM
> Subject: New Version Notification for
> draft-mglt-homenet-naming-architecture-dhc-options-00.txt
> To: Wouter Cloetens <wouter.cloetens@softathome.com>, Chris Griffiths <
> cgriffiths@dyn.com>, Daniel Migault <mglt.ietf@gmail.com>, Ralf Weber <
> ralf.weber@nominum.com>
>
>
>
> A new version of I-D,
> draft-mglt-homenet-naming-architecture-dhc-options-00.txt
> has been successfully submitted by Daniel Migault and posted to the
> IETF repository.
>
> Filename:        draft-mglt-homenet-naming-architecture-dhc-options
> Revision:        00
> Title:           DHCP DNS Public Authoritative Server Options
> Creation date:   2013-10-20
> Group:           Individual Submission
> Number of pages: 35
> URL:
> http://www.ietf.org/internet-drafts/draft-mglt-homenet-naming-architecture-dhc-options-00.txt
> Status:
> http://datatracker.ietf.org/doc/draft-mglt-homenet-naming-architecture-dhc-options
> Htmlized:
> http://tools.ietf.org/html/draft-mglt-homenet-naming-architecture-dhc-options-00
>
>
> Abstract:
>    The home network naming architecture as described in [I-D.mglt-
>    homenet-front-end-naming-delegation] requires a complex naming
>    configuration on the CPE.  This configuration MAY not be handled
>    easily by the average end user.  Furthermore, such misconfiguration
>    MAY result in making home network unreachable.
>
>    This document proposes a DHCP options that provide the CPE all
>    necessary parameters to set up the home network naming architecture.
>
>    First, this DHCP options provide automatic configuration and avoid
>    most end users' misconfiguration.  Most average end users may not
>    require specific configuration, and their ISP default configuration
>    MAY fully address their needs.  In that case, the naming homenet
>    architecture configuration will be completely transparent to the end
>    users.  Then, saving naming configuration outside the CPE, makes it
>    resilient to change of CPE or CPE upgrades.  Such configuration may
>    also be configured by the end user, via the customer area of their
>    ISP.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
>
>  --
> Daniel Migault
> Orange Labs -- Security
> +33 6 70 72 69 58
>
>
> _______________________________________________
> dhcwg mailing listdhcwg@ietf.orghttps://www.ietf.org/mailman/listinfo/dhcwg
>
>
> --
> Best regards
>
> Sten Carlsen
>
> No improvements come from shouting:
>
>        "MALE BOVINE MANURE!!!"
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>

-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58