IETF Logo Mail Archive

Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

Ted Lemon <mellon@fugue.com> Tue, 15 July 2014 19:43 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4F81A005B for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 12:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwvqd7-gdznV for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 12:43:49 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4207C1A0054 for <homenet@ietf.org>; Tue, 15 Jul 2014 12:43:49 -0700 (PDT)
Received: from [10.0.10.40] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 6B193238088A; Tue, 15 Jul 2014 15:43:48 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <53C58350.3020006@mtcc.com>
Date: Tue, 15 Jul 2014 15:43:45 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F076247-1C4B-4006-98D7-BA1DAE2E9438@fugue.com>
References: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com> <87fvij5wdw.wl.jch@pps.univ-paris-diderot.fr> <CADZyTkk2bv7T-Bs_ckG4i2MpXVDRqLA2R1dQgrMVrPSckOy-GQ@mail.gmail.com> <87k37uy703.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=YgD=JtyDpEz8TXOQmHxKzBoiEZbbW0LhZQy2GaKLqZQ@mail.gmail.com> <87vbrcydr9.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=kST4zPaPzz4DsAcCOtmYbQo-s2du+nEvJv0MSrneEMg@mail.gmail.com> <CADZyTkmZ+rC99qeC7gFEwc4JBoX9sHBUpo7p89+VC6zY7Z8drQ@mail.gmail.com> <87d2dfb98w.wl-jch@pps.univ-paris-diderot.fr> <CADZyTk=U25=Yck8BL5nrzGAR7mPk5HWp0r0h2wYy5ruSOf6rsQ@mail.gmail.com> <87vbr6mv8t.wl-jch@pps.univ-paris-diderot.fr> <7EEF5CD0-C3B8-4559-A75D-E55931F94F61@iki.fi> <21162.1405438875@sandelman.ca> <7ioawqpqcv.wl%jch@pps.univ-paris-diderot.fr> <7B5390DD-6969-4E26-A85E-0B436F48448F@fugue.com> <87a98acvxe.wl-jch@pps.univ-paris-diderot.fr> <E01C736F-75C0-436C-A283-28763208E46E@iki.fi> <F689B456-2A87-41BE-8884-ED23BD35D748@fugue.com> <53C58350.3020006@mt cc.com>
To: Michael Thomas <mike@mtcc.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/tOhaJjVST173XqNJ0KSRJqQklhc
Cc: homenet@ietf.org
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 19:43:50 -0000

On Jul 15, 2014, at 3:38 PM, Michael Thomas <mike@mtcc.com> wrote:
> That pretty much means that you need a solution that isn't bolted to DHCP, right?
> Or at least, that DHCP is only providing a default discovery mechanism which my CPE
> is completely free to ignore. Beyond the discovery, it ought to work identically regardless
> of whether it's my first hop ISP(s), or 20 hops away in Nairobi, right?

The point is that what the ISP is offering may be ideal for some users, and not others.   And some ISPs may offer it, while others don't.   So if there's a standard mechanism in place for using it when it's offered, if desired, then that's a win, even if not everyone wins.

What happens with queries isn't important as long as they are satisfied; there are lots of ways of satisfying queries for AAAA records, but only two ways of satisfying queries for PTR records, and the ISP may support one or both of those two ways, or neither.   The point of the DNS-PD document is to provide a way for the ISP and CPE to communicate about which mechanisms are supported and desired.

v2.23.0 | Report a Bug | By Email