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

S Moonesamy <sm+ietf@elandsys.com> Thu, 19 September 2013 19:35 UTC

Return-Path: <sm@elandsys.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 CD44621F8FDC for <homenet@ietfa.amsl.com>; Thu, 19 Sep 2013 12:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level:
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, 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 gnC8esYkDvdb for <homenet@ietfa.amsl.com>; Thu, 19 Sep 2013 12:35:30 -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 8CCF421F8F9A for <homenet@ietf.org>; Thu, 19 Sep 2013 12:35:30 -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 r8JJYgas010744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Sep 2013 12:34:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1379619296; bh=b4esdBTh4Gjp4TOMprATtiPOJNFmjNDUlNxUly6ddLM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Xqz0ElGBUKDYLmC/+VfWpuUBnUefVYco+YYXkp1dLpcmVhn3MviM3nHTV4fzZIbD6 tkUqS7C1iXZFJkAGMSQ6iTS9BIhQtsqgxtnDhGP93gDWDOylQRh3rNzSpRLpOBhHFf EAn9l9XL7TIPwlBRLujKk0wiF8pivQnbF8RnqQWo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1379619296; i=@elandsys.com; bh=b4esdBTh4Gjp4TOMprATtiPOJNFmjNDUlNxUly6ddLM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YYzs0njqSZmJJxrLN1FwewV10x9N52a1Skw6YM3ZRV94JlXEhr5oJjQVXVMFp1doS uKyFrhUkQuGjOqnn1qPBra2onbKzMne1P9QZMmqVdcCbVOPDbAm4j3k19MprLtMqCi 2Ovl6TLzHOCcJTysIV0lSqthBoDTIgvxEthKjYqI=
Message-Id: <6.2.5.6.2.20130919120656.0e8ce8a8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Sep 2013 12:34:38 -0700
To: Ted Lemon <ted.lemon@nominum.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <EFAA8F17-D53B-4F77-9718-88863ABF5387@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>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: apps-discuss@ietf.org, Dave Cridland <dave@cridland.net>, Tim Chown <tjc@ecs.soton.ac.uk>, iesg@ietf.org, draft-ietf-homenet-arch.all@tools.ietf.org, 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 19:35:32 -0000

Hi Ted,

At 08:31 19-09-2013, Ted Lemon wrote:

>On Sep 19, 2013, at 10:40 AM, Dave Cridland <dave@cridland.net> wrote:
>
> > Ted Lemon wrote:
> >> On Sep 19, 2013, at 10:06 AM, Dave Cridland <dave@cridland.net> wrote:
> >>> I reiterate for you: If the IETF publishes 
> this document as it stands,     it will look 
> like, and be taken as, the official "Home 
> Networking     Architecture for IPv6". Change 
> the title (at least) to avoid this. I 
> even     proposed alternate title texts. How 
> much more constructive would you     like?
> >>
> >> That is the goal of the document.   And that 
> is what the document is.   The problem with 
> your suggestions is that they propose that we 
> give the document at title that does not 
> describe what it is.   Perhaps a better title 
> would be "Preliminary Home Network Architecture for IPv6."

I like Dave's idea of having a different title 
for the draft.  The problem, to state it in 
simple terms, was "architecture".  The problem 
could be solved by using a different term, e.g. 
framework.  I would avoid "preliminary architecture" (see comment below).

> > There's been a few cases over the years where 
> a document has been published knowing full well 
> it's not complete, or that there would be a 
> replacement within the lifetime of the working 
> group, I know. But all the ones I can 
> immediately think of were cases where the 
> document could clearly provide value to people 
> outside the IETF, and the document stood on its own.

I am not keen on the idea of committing to do future work on a replacement.

> > This document is, to my eyes, borderline for 
> this. In point of fact, you don't seem to be 
> arguing it should be thrust in front of the 
> noses of every TP-Link and so on; you talk 
> above about making it available to "the IETF as 
> a whole". I appreciate an RFC (and the 
> publication process surrounding it) acts as a 
> useful mechanism for internal publicity and 
> awareness, of course, but I'd be more 
> comfortable if this were handled by an explicit 
> note to ietf@ietf.org asking for cross-area review.

Yes.

>Hm, okay, now I think we're getting 
>somewhere.   I think the reason the IETF should 
>publish this is that there is no clear "outside" 
>to the IETF—everybody is welcome.   So part of 
>the goal of publishing it ought to be to put a 
>stake in the sand that CPE vendors will pay 
>attention to, and possibly criticize.   That 
>won't happen with a working group 
>document.   But I think you are right that it 
>would help to be clearer about that.   Do

I understand the goal and I am okay with it.

Regards,
S. Moonesamy