Re: [homenet] ANIMA scope + homenet interaction + charter v15
Rene Struik <rstruik.ext@gmail.com> Tue, 28 October 2014 21:37 UTC
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92BEE1AD065; Tue, 28 Oct 2014 14:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-TFFlfFARHO; Tue, 28 Oct 2014 14:37:26 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 857C71AD064; Tue, 28 Oct 2014 14:37:26 -0700 (PDT)
Received: by mail-ig0-f179.google.com with SMTP id r10so1950099igi.12 for <multiple recipients>; Tue, 28 Oct 2014 14:37:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KxD74K2l6uyn9MWjz9jfdqVzojZMuXNYNlltEFrZ3Uc=; b=dMJTtaCWc6sUs9YywkYJBzotQbjhf9g8nUj0k3uAe059+IzeW9prYarxt/yIhTfQ4B dj77NdahHtDQWga9VyAFTxjzWRoRZWVzYz4cGFxEQUmQIQ+EthsS86+0XlcT/Gnv5K0b iVxRa64ZvuwrImzWu5tfUfNMWnFp8ch86j6Wzdj3LSWyBUawbQaMiDeKwEq8/ROYgBFP zUPJT0IG0m0vNUPwLHvgyCY1lF86YGuYZsDMmckB1oG3zTfz1Iw3qTn5Y04qBVSW+mgU yqr1Mi/CD7ZlCpv4H2bXWc91ooqIeyCBWAwrP347g9qxPnu8vVYhlEfjDIBt2Ec//Yfq Ld0A==
X-Received: by 10.42.167.1 with SMTP id q1mr6563198icy.48.1414532244776; Tue, 28 Oct 2014 14:37:24 -0700 (PDT)
Received: from [192.168.0.10] (CPE7cb21b2cb904-CM7cb21b2cb901.cpe.net.cable.rogers.com. [99.231.49.38]) by mx.google.com with ESMTPSA id x9sm6931656igl.10.2014.10.28.14.37.23 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Oct 2014 14:37:24 -0700 (PDT)
Message-ID: <54500C8F.5030104@gmail.com>
Date: Tue, 28 Oct 2014 17:37:19 -0400
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, "anima@ietf.org" <anima@ietf.org>, homenet <homenet@ietf.org>
References: <544FF8FC.5090103@cisco.com>
In-Reply-To: <544FF8FC.5090103@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/tJ2DBOe_7En8I9HBTkHLEAULvRI
Subject: Re: [homenet] ANIMA scope + homenet interaction + charter v15
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Oct 2014 21:37:29 -0000
Hi Benoit: -1 on you suggestion #1. I do not think suggesting "constrained networks and devices" to be suddenly out of scope helps: it is one of the main areas where semi-automatic management is imperative. If one has a bootstrapping solution and configuration negotiation/synchronization protocol that is not useful in constrained settings, what is the point? In my mind, it seems much more prudent to design schemes with constrained networks and devices and failure recovery models that apply there (configuration mismatch due to sleepy devices, malfunctioning data store, etc.), where these would then obviously also fit the less constrained, "professionally managed" networks. Design for the"nimble", so that both "nimble" and "fatter" networks can use this. This also has the advantage that one is forced to think in terms of many potential actors, rather than a few ones, which helps in viewing solutions in terms of heterogeneous rather than homogeneous deployment models. I have done all my reviews of nmrg drafts (http://www.ietf.org/mail-archive/web/anima/current/msg00327.html) with constrained networks and devices in mind. It would be a shame if one would now narrow down the focus and rule this (future almost ubiquitous) deployment category out of scope. Or, is this a political ploy, so as to avoid a turf war with homenet people? If that is the case, it would be much more prudent to have another BoF to iron out some of these issues. {This may be prudent for reasons I already indicated in the same #00327 message as well - I will not repeat those arguments here.} Best regards, Rene On 10/28/2014 4:13 PM, Benoit Claise wrote: > Dear all, > > [sorry for double-posting, but we need the specific feedback from the > HOMENET community] > > 1. scope > I finished reading the ANIMA mailing list and, based on the feedback, > Joel, Ted, and I would like to clarify the ANIMA scope for "the set of > specific reusable infrastructure components that support autonomic > interactions between devices" (quoting the charter) > > The charter currently mentions: > The ANIMA working group will initially focus on enterprise, ISP > networks and IoT. > > Multiple tracks were discussed on the mailing list. > * keep enterprise, ISP networks and IoT > * focus on enterprise and ISP networks > * everything, but the initial focus is enterprise and carrier? > * professionally-managed networks > > It seems to us that "professionally-managed networks" is what ANIMA is > after. And it's potentially a distraction to try to segment the scope > based on enterprise, ISP, homenet, or IoT. What is IoT after all? > > OLD: The ANIMA working group will initially focus on enterprise, > ISP networks and IoT. > NEW: The ANIMA working group focuses on professionally-managed > networks. > > Does it sound about right? > > 2. Overlap with HOMENET > This distinction in point 1 might help regarding the potential overlap > of the solution for distributed IPv6 prefix management. > Btw, the new charter has been adapted: > OLD: A solution for distributed IPv6 prefix management within a network. > NEW: the solution for distributed IPv6 prefix management within a > large-scale network > > Also, The HOMENET collaboration has been stressed in the charter. > > 3. Others > I believe I took care of the others changes proposed on the mailing. > If this is not the case, let me know. > At this point in time, please provide concrete change to the charter > text if some issues persist. > Charter v15 has just been posted, and you can review the detailed > changes at > https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-anima%2Fwithmilestones-00-14.txt&difftype=--html&submit=Go!&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-anima%2Fwithmilestones-00-15.txt > > > 4. Security Advisor. > I have requested one for ANIMA to the security ADs. > > Regards, Benoit > > _______________________________________________ > homenet mailing list > homenet@ietf.org > https://www.ietf.org/mailman/listinfo/homenet -- email: rstruik.ext@gmail.com | Skype: rstruik cell: +1 (647) 867-5658 | US: +1 (415) 690-7363
- Re: [homenet] ANIMA scope + homenet interaction +… Rene Struik
- [homenet] ANIMA scope + homenet interaction + cha… Benoit Claise
- Re: [homenet] ANIMA scope + homenet interaction +… Brian E Carpenter
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter
- Re: [homenet] ANIMA scope + homenet interaction +… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Laurent Ciavaglia
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Michael Richardson
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Benoit Claise
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Benoit Claise
- Re: [homenet] ANIMA scope + homenet interaction +… Michael Richardson
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Rene Struik
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Markus Stenberg
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Markus Stenberg
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ole Troan
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ralph Droms
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ole Troan
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Alexandru Petrescu
- Re: [homenet] ANIMA scope + homenet interaction +… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ralph Droms
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Ted Lemon
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Sheng Jiang
- Re: [homenet] [Anima] ANIMA scope + homenet inter… Brian E Carpenter