Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter

Martin Vigoureux <martin.vigoureux@alcatel-lucent.com> Tue, 24 May 2011 12:33 UTC

Return-Path: <martin.vigoureux@alcatel-lucent.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D94E068C for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxhKc9K0Vhf6 for <irtf-discuss@ietfa.amsl.com>; Tue, 24 May 2011 05:33:22 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 4039DE067C for <irtf-discuss@irtf.org>; Tue, 24 May 2011 05:33:21 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p4OCTxfZ010318 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 May 2011 14:33:17 +0200
Received: from [172.27.205.227] (135.120.57.7) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (135.120.45.63) with Microsoft SMTP Server (TLS) id 8.3.106.1; Tue, 24 May 2011 14:33:07 +0200
Message-ID: <4DDBA583.604@alcatel-lucent.com>
Date: Tue, 24 May 2011 14:33:07 +0200
From: Martin Vigoureux <martin.vigoureux@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Paulo Mendes <paulo.mendes@ulusofona.pt>
References: <DC91B532-727D-428C-889F-4669268D46BB@ericsson.com> <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
In-Reply-To: <62C44350-6EED-4A6F-9E02-6D3F89A3097D@ulusofona.pt>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "icn-interest@listserv.netlab.nec.de" <icn-interest@listserv.netlab.nec.de>
Subject: Re: [irtf-discuss] [Icn-interest] Draft ICN RG Charter
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/irtf-discuss>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2011 12:33:23 -0000

Hello Paulo,

Le 24/05/2011 13:55, Paulo Mendes a écrit :
> Hi Borje and Dirk
>
> I would be careful with the word "architecture" since IETF/IRTF does not standardize architectures. Hence I would propose to use the following sentence...
>
> "The ICNRG will investigate components of a common protocol framework for information-centric networking, aiming to: i) identify protocols for standardization, which may or may not re; ii) support an ICN architecture with large applicability."
>
> ... to replace the following two sentences:
>
> "The ICNRG will identify key ICN architecture invariants across different specific approaches which could form the basis of a future ICN architecture."
>
> "The intention is that one result from this work could be a common protocol framework that can be used to identify protocols for standardization. These protocols may or may not re-use existing IETF protocols."

In turn, I would be careful with the statement "IETF/IRTF does not 
standardize architectures" :-)
It all depends on what one reads in "architecture".
Note also that the charter does not say that an architecture will be 
standardized.
I think the text is fine.

best regards,
martin