Re: [homegate] Proposed Charter Update - 2010/09/09

Andrew Sullivan <ajs@shinkuro.com> Fri, 10 September 2010 13:33 UTC

Return-Path: <ajs@shinkuro.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 503563A6880 for <homegate@core3.amsl.com>; Fri, 10 Sep 2010 06:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.982
X-Spam-Level:
X-Spam-Status: No, score=-101.982 tagged_above=-999 required=5 tests=[AWL=0.617, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qvc4-plUPpUn for <homegate@core3.amsl.com>; Fri, 10 Sep 2010 06:33:04 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id B7C173A68B6 for <homegate@ietf.org>; Fri, 10 Sep 2010 06:33:04 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 3F4C31ECB41D for <homegate@ietf.org>; Fri, 10 Sep 2010 13:33:31 +0000 (UTC)
Date: Fri, 10 Sep 2010 09:33:24 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: homegate@ietf.org
Message-ID: <20100910133323.GC8376@shinkuro.com>
References: <14B94CC6-EA1D-44BD-9E01-457EB89C5E4E@nominet.org.uk> <p06240845c8aeaf99c3eb@[10.20.30.158]> <ABE50CF883E14B7CB7145B27F7B954F6@23FX1C1> <4C8A08E0.6050804@piuha.net> <4C8A2A60.3080202@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4C8A2A60.3080202@cisco.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [homegate] Proposed Charter Update - 2010/09/09
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 13:33:06 -0000

On Fri, Sep 10, 2010 at 02:53:52PM +0200, Mark Townsley wrote:
> > 
> > Why are local and global naming bundled here? I presume we have dyndns
> > and other solutions for the global naming problem already, and that
> > problem space seems different from the local routed network problem.
> 
> Bundled because if DNS is used for both, you hit a split DNS issue that
> must be carefully addressed.

Let me put on my dnsext hat for a moment and agree with Mark.  Llmnr
and mDNS are treated up in the clients as though they're just part of
the unified DNS name space.  But they're not part of that name space.
Moreover, stuff leaks from local networks to the global DNS all the
time.  If it didn't, we wouldn't need the AS112 project and drafts
like draft-ietf-dnsop-default-local-zones (even though that latter
isn't explicitly named at the home network).  Even DNS experts can't
navigate the huge number of DNS-related RFCs.  So developing a codex
for home network device implementers would be very helpful: "Here's
the stuff you need to know, and here's where it's written down." 

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.