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

Scott Brim <scott.brim@gmail.com> Tue, 24 September 2013 23:08 UTC

Return-Path: <scott.brim@gmail.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 B8A8C11E8186; Tue, 24 Sep 2013 16:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level:
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, 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 eElzaXRUwXJS; Tue, 24 Sep 2013 16:08:27 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id DA6A611E80F8; Tue, 24 Sep 2013 16:08:26 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id i4so87796oah.36 for <multiple recipients>; Tue, 24 Sep 2013 16:08:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ggm8u+26nbFfvk7PdynFKG0i9ywtfPBgI41kZQTe7qc=; b=oJ0+QTtLzOXKH6lgjo7o3EbfDYQl34f7S+IK39Aevi6Pyy5/Hqb3N+GxdzEVEZSC9L 8nDn7jWuz0Asdd/59aRneuHvK3kFbtTmivYlC4obQOguysQGt0WAsv+DvUKGoYlufd0A 26/VHTbTOgfFLe2Hd96i6mkwnjqX68rHxK6QuEMA2l/dAEeT5vTLIlbxMUhnAPs24c/e 1a4QmWHzM1WGJWOHtFxO7tiERy+7Kdg7lFxnwRAZ4QfsChcHm77r1mpUA85RtbuZ1hpe AVd4/KUdY7hCNjllcRI53FkYuQdKQbnnOeW/1IKV06WnRN3UFCrBKVDmiEuGNItfHNTa nQOQ==
MIME-Version: 1.0
X-Received: by 10.182.99.231 with SMTP id et7mr27634777obb.10.1380064099963; Tue, 24 Sep 2013 16:08:19 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Tue, 24 Sep 2013 16:08:19 -0700 (PDT)
Received: by 10.182.2.134 with HTTP; Tue, 24 Sep 2013 16:08:19 -0700 (PDT)
In-Reply-To: <52421A8F.2090603@gmail.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> <14439.1380035891@sandelman.ca> <76716D93-E946-4682-BE1C-CF2DC0434CE5@nominum.com> <52421A8F.2090603@gmail.com>
Date: Tue, 24 Sep 2013 19:08:19 -0400
Message-ID: <CAPv4CP_=M6dYWKV6n0wi7OP2rsSsgS0X1G51QKppJfLhmCF-mQ@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="089e0158a92e721ad804e72936bb"
Cc: "&lt, apps-discuss@ietf.org&gt, " <apps-discuss@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, S Moonesamy <sm+ietf@elandsys.com>, Tim Chown <tjc@ecs.soton.ac.uk>, Ted Lemon <ted.lemon@nominum.com>, draft-ietf-homenet-arch.all@tools.ietf.org, "homenet@ietf.org Group" <homenet@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [homenet] [apps-discuss] 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: Tue, 24 Sep 2013 23:08:27 -0000

I propose Architecture Overview.
On Sep 24, 2013 7:04 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 25/09/2013 04:01, Ted Lemon wrote:
> > On Sep 24, 2013, at 11:18 AM, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> >> I believe that perhaps the title is now wrong.
> >> I think that it should say:
> >>    "Requirements for Home Networking for IPv6"
> >>
> >> (But, it's really more than requirements. It's just less than
> architecture)
> >
> > I previously suggested "Preliminary architecture ..."   Would that
> address your concern?   I don't think it's precisely a requirements
> document; the document does what the working group currently needs it to
> do, and I would hate to see us spend another couple of meeting cycles
> turning it into a formal requirements document unless someone can make a
> clear argument that doing so is necessary.
>
> Both 'framework' and 'architecture' mean different things to different
> people. I could say the same about 'guidelines' too.
>
> It doesn't matter which of these vague words we use. 'Preliminary
> architecture' is fine. Just make sure that the abstract and introduction
> set the reader's expectations correctly, which judging by SM's review
> is not quite the case yet.
>
>     Brian
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>