Re: [appsdir] APPSDIR review of draft-ietf-homenet-arch-10

SM <sm+ietf@elandsys.com> Thu, 19 September 2013 23:59 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: appsdir@ietfa.amsl.com
Delivered-To: appsdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F003D21F89FF for <appsdir@ietfa.amsl.com>; Thu, 19 Sep 2013 16:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level:
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FUtIVz8jhFYO for <appsdir@ietfa.amsl.com>; Thu, 19 Sep 2013 16:59:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DAE21F85C9 for <appsdir@ietf.org>; Thu, 19 Sep 2013 16:59:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.144.105]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r8JNxNN7018292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Sep 2013 16:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1379635178; bh=3MSOJjDeV2DV1OwvRW8u3wJRaGvW9ylEeuaiIC9zmyQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gkMThQMoQIOAowHjpkZZgNl7GzdP9huBsXhJTZdjT1dRpC/EsgO/9QGy9r3ZwD57O xH1C2k2LCqM3mjl+fAJHXmBbVRo96pVANi+Klq4Knqyd2glWip5gcUsBcg8nhL1zo8 mVU/vvTBWKz+8L9gpXw3kjLSXdPgEK4PCyZ7gNdQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1379635178; i=@elandsys.com; bh=3MSOJjDeV2DV1OwvRW8u3wJRaGvW9ylEeuaiIC9zmyQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1KCKFQfYchfOdXZqlxMXBfq3g15d0HqtNpqxjknl479Y0PU2qmc7lDLkwisfPHDKR NSoDlsVn++qMl17QZWV2p4nNfDE+pV5QoE8tqIYsvHEqQxppjZGthzBTg8p5IZIITp buAJdCDER0x2v3iOUFlajFJz8RFt1vCWPs4yBBvU=
Message-Id: <6.2.5.6.2.20130919155631.0d2bc4a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Sep 2013 16:58:48 -0700
To: Ted Lemon <ted.lemon@nominum.com>
From: SM <sm+ietf@elandsys.com>
In-Reply-To: <1C0F7F8E-1BEF-4748-B23A-FF8F141A5F0E@nominum.com>
References: <6.2.5.6.2.20130914143222.0b9590f0@elandnews.com> <C4F6B742-3784-48BA-8B97-BE3B8972DC39@ecs.soton.ac.uk> <EMEW3|72d902bbed65dc8b06cf46c298d30fe1p8I0CV03tjc|ecs.soton.ac.uk|C4F6B742-3784-48BA-8B97-BE3B8972DC39@ecs.soton.ac.uk> <6.2.5.6.2.20130918225335.0d0e2478@elandnews.com> <EFAA8F17-D53B-4F77-9718-88863ABF5387@nominum.com> <6.2.5.6.2.20130919123250.0e8ce9f0@elandnews.com> <1C0F7F8E-1BEF-4748-B23A-FF8F141A5F0E@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Barry Leiba <barryleiba@computer.org>, appsdir@ietf.org, Claudio Allocchio <Claudio.Allocchio@garr.it>, Dave Cridland <dave@cridland.net>
Subject: Re: [appsdir] APPSDIR review of draft-ietf-homenet-arch-10
X-BeenThere: appsdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Apps Area Review List <appsdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/appsdir>, <mailto:appsdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/appsdir>
List-Post: <mailto:appsdir@ietf.org>
List-Help: <mailto:appsdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/appsdir>, <mailto:appsdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 23:59:59 -0000

Hi Ted,
At 14:30 19-09-2013, Ted Lemon wrote:
>There won't be a fight—I'm just trying to figure 
>out what the right thing is to do.   The 
>situation is complicated by the fact that as 
>Brian said, the document really does focus on 
>layer 3 and naming, and isn't intended to go any 
>wider than that.   To us, that's what "IPv6" 
>means, but I think we failed to account for the 
>possibility that other readers might think it includes the application layer.

The document discusses about addressability.  As 
Pete pointed out there's an application 
perspective to that.  There are two alternatives 
right now, i.e. what Dave Cridland suggested or 
looking into the organization of the 
document.  There may be more alternatives if there is input from other people.

> From my perspective, I think accounting for the 
> application layer is a good idea—it's just not 
> something that this document sets out to do, 
> and indeed I don't think this document by 
> itself can do that, so that needs to be 
> excluded by what we mean by "IPv6 Home Network 
> Architecture."   As Brian said, we really are 
> talking about the bottom of the stack here.

The bottom of the stack approach is not that 
practical when the parts have to be put 
together.  In my opinion it leads to complexity.

>I would actually encourage you to look at the 
>MIF architecture document (not yet adopted, but 
>should be soon), which is still an intarea 
>document, but really addresses the apps layer 
>problem more directly: 
>https://datatracker.ietf.org/doc/draft-anipko-mif-mpvd-arch/
>
>I say this not only because I think it's a good 
>and interesting document, and not only because I 
>would like your input, but also because I 
>believe it relates pretty closely to what's 
>going on with the homenet architecture document, 
>and I'm realizing that by exposing you to 
>partial snapshots of the larger picture, we are making your work harder.

I thought about MIF when I was reading the 
draft.  The home networking would likely be using 
split views for DNS.  I have to go through the 
DHCPv6 specifications and some of the MIF work 
before I can comment on the MIF architecture 
document.  The work is not that hard. I'll take 
the liberty not to explain why or else I will be 
volunteered for IETF work.  :-)

Best regards,
-sm