Re: [Banana] Charter

<N.Leymann@telekom.de> Tue, 19 September 2017 08:30 UTC

Return-Path: <N.Leymann@telekom.de>
X-Original-To: banana@ietfa.amsl.com
Delivered-To: banana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E98EE132198 for <banana@ietfa.amsl.com>; Tue, 19 Sep 2017 01:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.318
X-Spam-Level:
X-Spam-Status: No, score=-4.318 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 4M5b-tYV93H5 for <banana@ietfa.amsl.com>; Tue, 19 Sep 2017 01:30:16 -0700 (PDT)
Received: from MAILOUT21.telekom.de (MAILOUT21.telekom.de [80.149.113.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83B15126DFE for <banana@ietf.org>; Tue, 19 Sep 2017 01:30:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1505809815; x=1537345815; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=LdV+ZOsRN7DimIxMmq/sfqOiSFKTFg192n7xQ5xWwoY=; b=uONcwCdAof0AxUMKcBnTXKMH5GDpN9s/EfgfgjWBZHoWE8omjlPI5Gi4 IekPvwHplcHBnO4SRg23+/vdovmeWBxwcV6da7qEQMbNw+dnDC40oz8Be 9GRJfZk/b5njPcR6GwTkcLKsMs2/mm3wm+C7j6Pcs8QTSSIphcwa7hT/e ivCIdibC6tAogIhVccNGfTUwespmFSWU9/wk1ntzbGKUbSDfDqiGlVV1X x7u/Hz4ss951Zlg2CVNjgYabl1d0FsSWzd/KC9JLhDvbdtLRvO87zTOTD sFgxcBJA67UJ98GG77h5XskZxNxYVMjL2LyHMtdEx4MhM8p9zd1x8qcXa Q==;
Received: from qde8e4.de.t-internal.com ([10.171.255.33]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Sep 2017 10:30:12 +0200
X-IronPort-AV: E=Sophos; i="5.42,417,1500933600"; d="scan'208,217"; a="81589847"
Received: from he105661.emea1.cds.t-internal.com ([10.169.119.57]) by QDE8PP.de.t-internal.com with ESMTP/TLS/AES256-SHA; 19 Sep 2017 10:30:12 +0200
Received: from HE105662.EMEA1.cds.t-internal.com (10.169.119.58) by HE105661.emea1.cds.t-internal.com (10.169.119.57) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 19 Sep 2017 10:30:11 +0200
Received: from HE105662.EMEA1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4]) by HE105662.emea1.cds.t-internal.com ([fe80::442c:834e:c489:d2c4%26]) with mapi id 15.00.1293.002; Tue, 19 Sep 2017 10:30:11 +0200
From: N.Leymann@telekom.de
To: sgundave@cisco.com, mrcullen42@gmail.com
CC: zhangmingui@huawei.com, alexandre.petrescu@gmail.com, wim.henderickx@nokia.com, banana@ietf.org
Thread-Topic: [Banana] Charter
Thread-Index: AQHTLJQzNrnZhGRodUOLwvlmQzK+5qKy5lgAgACsH4CAAavyAIAAtJ8AgASaK4CAAF38AIAABwgAgAASn4CAABvcAIAAw7XQ
Date: Tue, 19 Sep 2017 08:30:11 +0000
Message-ID: <2585ec071c7242cda57ada0e6cd5cc9b@HE105662.emea1.cds.t-internal.com>
References: <96A7BC33-FB64-487A-A60D-7AB8504C9DDF@gmail.com> <a1df884a51f246a7969c0057ff78d807@BTWP000357.corp.ads> <C3A4BFB9-EAD7-4B32-90C1-248D6D74ECD1@gmail.com> <9A767D1D-C6CA-4C7D-A281-7150E259881D@gmail.com> <DB5PR07MB13998EE07C5B5D5DBACED79C9B1A0@DB5PR07MB1399.eurprd07.prod.outlook.com> <7ED94797-5E72-4191-B861-4CD2F410BBD5@gmail.com> <7i60gox0c8.wl-jch@irif.fr> <DB5PR07MB1399FEDB262E0205457EA8AB9BFC0@DB5PR07MB1399.eurprd07.prod.outlook.com> <87bmqgov69.wl-jch@irif.fr> <DB5PR07MB1399977AFFE9FA7D19A2D34D9BFC0@DB5PR07MB1399.eurprd07.prod.outlook.com> <0d8ce583860345b89020113f1239be5d@BTWP000357.corp.ads> <21BD0F20-9CE5-466B-992E-93F6D84DB7D4@gmail.com> <95788B92-E8C1-4FE6-9B0C-7F29361D9297@trammell.ch> <d3759d89-9f6e-bcf4-8c44-32f3f435d784@gmail.com> <01e83ac6-0bd0-e7c7-01e4-0ffb7af73034@gmail.com> <4B6D7CF5-E6BC-4ECA-9299-7458A624320B@nokia.com> <B31BA5EB-7369-4B49-B240-AA6C3E653231@gmail.com> <2F216DBC-43EE-45AC-AAB8-68C81A14AD73@nokia.com> <4552F0907735844E9204A62BBDD325E7A65EC703@NKGEML515-MBX.china.huawei.com> <260086DD-D245-46EF-89E2-308D5A58AAFB@nokia.com> <5FECB6A6-41B7-41D1-A8B8-B7BCE8474F90@gmail.com> <2CD45C9D-41FB-425F-946E-D3AE47C9B000@nokia.com> <6A618A1C-92FB-467F-8F7D-6A9B40FC191E@gmail.com> <D5E56BEA.28AE8D%sgundave@cisco.com> <9CD725AF-B9FE-4E81-BFD6-21A812DF48CF@gmail.com> <D5E58ECD.22D723%sgundave@cisco.com>
In-Reply-To: <D5E58ECD.22D723%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.213.102.147]
Content-Type: multipart/alternative; boundary="_000_2585ec071c7242cda57ada0e6cd5cc9bHE105662emea1cdstintern_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/-QpbjPN1vYpZUw_CBMEahWNs0CI>
Subject: Re: [Banana] Charter
X-BeenThere: banana@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Bandwidth Aggregation for interNet Access: Discussion of bandwidth aggregation solutions based on IETF technologies." <banana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/banana>, <mailto:banana-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/banana/>
List-Post: <mailto:banana@ietf.org>
List-Help: <mailto:banana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/banana>, <mailto:banana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2017 08:30:20 -0000

Hi,

Von: Banana [mailto:banana-bounces@ietf.org] Im Auftrag von Sri Gundavelli (sgundave)
Gesendet: Dienstag, 19. September 2017 00:30
An: Margaret Cullen <mrcullen42@gmail.com>
Cc: Zhangmingui (Martin) <zhangmingui@huawei.com>; Alexandre Petrescu <alexandre.petrescu@gmail.com>; Henderickx, Wim (Nokia - BE/Antwerp) <wim.henderickx@nokia.com>; banana@ietf.org
Betreff: Re: [Banana] Charter

> The IETF WG formation process focuses on making sure that there is an actual community
>   of people who want to do a well-understood set of work, that those people have the skills and
>  knowledge to do the work successfully, and that they represent enough segments of the
> industry to have a wide-enough perspective to do the work in a way that will be widely applicable.
> The IETF is set up to attract competent groups of people who want to do interesting work within
> the IETF's scope, and offer them an environment and support that will allow them to do a good job.

> Generally, I agree with your above statement. If there is enough interest to do some new work and people ready to write some
> drafts and people ready to chair the meetings, creation of a WG should be the most logical thing. But, that goes with the
> assumption that the work is not overlapping with some other work that is happening some where else. That needs to be
> ensured and hence the need to agree upon the problem statement from both interested and non-interested parties.
> We need to review this overlap with QUIC, MPTCP, MobIKE and Mobile IPv6 protocols.
My impression from the last IETF meeting was that there is sufficient support for that type of work. I agree that there are ongoing
discussions in other working groups which might address some of the BANANA aspects but I do not see any WG which addresses
the whole picture and intends to come up with a solution. The (proposed) charter also states that existing protocols will be
considered. Nobody want's to reinvent the wheel.

> We can define a new signaling protocol, just to solve this distribution problem, which can authenticate/authorize the peers,
> allows path registrations, or prefix allocations, but it will be exactly the same as some existing protocols, but with a new
> signaling semantics. So, what would be achieve from this effort? It will be another signaling protocol  called "Banana",
> which does exactly the same. I wonder, what is the point of this effort?

I don't think that we have the requirement to create a new signaling protocol called BANANA. The reuse of an existing
protocol in combination with some extensions is also a very valid approach.

Nic


From: Margaret Cullen <mrcullen42@gmail.com<mailto:mrcullen42@gmail.com>>
Date: Monday, September 18, 2017 at 1:50 PM
To: Sri Gundavelli <sgundave@cisco.com<mailto:sgundave@cisco.com>>
Cc: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com<mailto:wim.henderickx@nokia.com>>, "Zhangmingui (Martin)" <zhangmingui@huawei.com<mailto:zhangmingui@huawei.com>>, Alexandre Petrescu <alexandre.petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>>, "banana@ietf.org<mailto:banana@ietf.org>" <banana@ietf.org<mailto:banana@ietf.org>>
Subject: Re: [Banana] Charter