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

"Bernie Volz (volz)" <volz@cisco.com> Mon, 21 October 2013 01:10 UTC

Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1766011E8307; Sun, 20 Oct 2013 18:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2LoZtYtj3F3M; Sun, 20 Oct 2013 18:09:59 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A8E4111E80FB; Sun, 20 Oct 2013 18:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13025; q=dns/txt; s=iport; t=1382317798; x=1383527398; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=P455eNF/ebFXJfSyHKf38tVWSD7uYtdpYzDw7C/KS24=; b=DPZhAJPqDb4KqyGro59R1st2mz4hqCQFEFCwBA3+Wp7ErkH2eOa+3Vv4 6EBq+al2fqLWA9lNipNBd+JHcvIzO5YIcmR6BGq+c88U+Rm4dzkbafxxb mN2hBOHqj73FfB7tm4vQ4bm0GMKfAUZIdlPvAo3p5wCPQ862WJE/+P9SH Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMGAHt+ZFKtJXHB/2dsb2JhbABagkNEOKxNiWaITYElFnSCJQEBAQQBAQFrCQIQAgEIDgMBAgECJAQHIQYLFAMGCAIEDgUJh2sDDw20Aw2Ja4xsgUSBGw0EBgEGA4MWgQoDlh6Ba4EviyGFN4FmgT6Bag
X-IronPort-AV: E=Sophos; i="4.93,535,1378857600"; d="scan'208,217"; a="274415247"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 21 Oct 2013 01:09:58 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r9L19vwb015815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 21 Oct 2013 01:09:57 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Sun, 20 Oct 2013 20:09:57 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Daniel Migault <mglt.ietf@gmail.com>
Thread-Topic: [dhcwg] Fwd: New Version Notification for draft-mglt-homenet-naming-architecture-dhc-options-00.txt
Thread-Index: AQHOzc3YL1Pao1qEC0uGX6iM7/BHRJn+WOcf
Date: Mon, 21 Oct 2013 01:09:56 +0000
Message-ID: <E47592E3-3A16-4AC6-A0B8-66B30B35E34A@cisco.com>
References: <20131020194121.22779.70469.idtracker@ietfa.amsl.com>, <CADZyTkn7jnwE+k__YsubccYnu=e2NZYjT69D-u-FGNfvtutkRg@mail.gmail.com>
In-Reply-To: <CADZyTkn7jnwE+k__YsubccYnu=e2NZYjT69D-u-FGNfvtutkRg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_E47592E33A164AC6A0B866B30B35E34Aciscocom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-mglt-homenet-naming-architecture-dhc-options-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2013 01:10:04 -0000

These are comments with WG co-chair hat off.

I don't recall providing input to this document:


11<http://tools.ietf.org/html/draft-mglt-homenet-naming-architecture-dhc-options-00#section-11>11>.  Acknowledgment

We would like to thank Tomasz Mrugalski and Bernie Volz for their
   comments on the design of the DHCP Options.


And at first glance this looks like encapsulation gone crazy!!

I haven't yet read it carefully enough to determine whether this makes sense to do.

I don't like things like requiring a server to return "empty" options if it "understands" them but they were not configured (or "badly" configured). And I can't see any benefit to the client for doing this documented (there's no special action the client is specified to take) -- so why do it?

- Bernie (from iPad)

On Oct 20, 2013, at 3:52 PM, "Daniel Migault" <mglt.ietf@gmail.com<mailto:mglt.ietf@gmail.com>> 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<mailto: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<mailto:wouter.cloetens@softathome.com>>, Chris Griffiths <cgriffiths@dyn.com<mailto:cgriffiths@dyn.com>>, Daniel Migault <mglt.ietf@gmail.com<mailto:mglt.ietf@gmail.com>>, Ralf Weber <ralf.weber@nominum.com<mailto: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<http://tools.ietf.org>.

The IETF Secretariat




--
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58<tel:%2B33%206%2070%2072%2069%2058>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org<mailto:dhcwg@ietf.org>
https://www.ietf.org/mailman/listinfo/dhcwg