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

Ted Lemon <ted.lemon@nominum.com> Thu, 19 September 2013 12:55 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5B121F9654; Thu, 19 Sep 2013 05:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.511
X-Spam-Level:
X-Spam-Status: No, score=-106.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 tRpi6ynR6GcM; Thu, 19 Sep 2013 05:55:20 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id DF41E21F9385; Thu, 19 Sep 2013 05:55:19 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUjr0N6E1RQ2OVYlnERSIAAXBW5sX9rji@postini.com; Thu, 19 Sep 2013 05:55:20 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 292E41B82DE; Thu, 19 Sep 2013 05:55:19 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 92F6A190068; Thu, 19 Sep 2013 05:55:16 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 19 Sep 2013 05:55:16 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1811\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <6.2.5.6.2.20130918225335.0d0e2478@elandnews.com>
Date: Thu, 19 Sep 2013 08:55:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <E01ACFFF-CA8F-4280-8CE0-2CC57E6270EE@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>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1811)
X-Originating-IP: [192.168.1.10]
Cc: "<apps-discuss@ietf.org>" <apps-discuss@ietf.org>, Dave Cridland <dave@cridland.net>, Tim Chown <tjc@ecs.soton.ac.uk>, The IESG <iesg@ietf.org>, draft-ietf-homenet-arch.all@tools.ietf.org, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] APPSDIR review of draft-ietf-homenet-arch-10
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 19 Sep 2013 12:55:26 -0000

On Sep 19, 2013, at 6:59 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> The Chairs have already agreed about the five topics to be covered.  It's not a problem.  The next step would be to take these topics, make them accessible to the average reader, and organize them.  This may require avoiding too many details if it is doable.

I think that you are interpreting this document to be something that it is not, and cannot yet be.   What this document is is an architecture for the homenet working group—a crib sheet that tells us what we are trying to accomplish.   I don't think it's intended to be something that a random person who is not implementing home gateways would find useful.   The working group is hoping that subsequent versions of this document will evolve over time, and I think it would be good for the working group to evolve the document into something that meets the goals that you've set out above.

However, I think that if the working group attempts to do that now, two things will happen.  First, the working group won't actually get to the work it's supposed to be doing, because completing the architecture document will continue to be an all-consuming effort.   Second, the document that is produced will be purely theoretical, not based on actual practice, and probably useless.

So I would like you to consider whether you can accept this restatement of the purpose of the document.   Do you feel that this document cannot be of use until it meets the goals you've set out above, or does the different purpose I've expressed here make sense to you?   If the latter, can you reconsider your review in light of this new stated purpose for the document?   Is part of the problem that the goals of the document are poorly expressed in the document?   Given the goals I've stated, do all of your comments still apply, or would you have responded differently to the document if you'd been evaluating it on the basis I'm proposing?