Re: [Banana] Charter

"Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com> Fri, 15 September 2017 04:39 UTC

Return-Path: <wim.henderickx@nokia.com>
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 E2C93132ED3 for <banana@ietfa.amsl.com>; Thu, 14 Sep 2017 21:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.42
X-Spam-Level:
X-Spam-Status: No, score=-0.42 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
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 CfQHJIOZ58j2 for <banana@ietfa.amsl.com>; Thu, 14 Sep 2017 21:39:06 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0123.outbound.protection.outlook.com [104.47.2.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41CFF132EDC for <banana@ietf.org>; Thu, 14 Sep 2017 21:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=1Rawc3nmEiW+xCqh/LocmCfBN8NrMFlyEXjr1eIfcxU=; b=rPhPbD5FJapA/dOCAU/PwuAmdRqHOPqIspaof4E2OIEYouvOvnnhlwwFKdu1CrHkCZEOkFlaDFY1Yp5kkhcRjUpsfcbzs7Mog5hV5WnHwwH3WN4oIb8M8vh7ESlSmcH49m6L40MgdesjTb3mcSgv9CGd5FZyZ4noQTQJnasqQuk=
Received: from AM2PR07MB0961.eurprd07.prod.outlook.com (10.162.37.144) by AM2PR07MB0705.eurprd07.prod.outlook.com (10.160.56.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.4; Fri, 15 Sep 2017 04:39:02 +0000
Received: from AM2PR07MB0961.eurprd07.prod.outlook.com ([fe80::4c8a:b7d0:b947:7695]) by AM2PR07MB0961.eurprd07.prod.outlook.com ([fe80::4c8a:b7d0:b947:7695%13]) with mapi id 15.20.0056.010; Fri, 15 Sep 2017 04:39:02 +0000
From: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
To: "Zhangmingui (Martin)" <zhangmingui@huawei.com>, "mrcullen42@gmail.com" <mrcullen42@gmail.com>
CC: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "banana@ietf.org" <banana@ietf.org>
Thread-Topic: [Banana] Charter
Thread-Index: AQHS/w5mXMtIffsXq0694fWkm5K0oaJYQcGAgFroUYCAADjXgIAArCGAgAGWRYA=
Date: Fri, 15 Sep 2017 04:39:00 +0000
Message-ID: <260086DD-D245-46EF-89E2-308D5A58AAFB@nokia.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>
In-Reply-To: <4552F0907735844E9204A62BBDD325E7A65EC703@NKGEML515-MBX.china.huawei.com>
Accept-Language: nl-BE, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.170913
authentication-results: spf=none (sender IP is ) smtp.mailfrom=wim.henderickx@nokia.com;
x-originating-ip: [88.128.80.64]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0705; 6:hvQzJZVpWY0P4yLgd0VvDkhvgYA4QFmauIKr0Z9eIP1p/SPEb8HDMRFPOnqZCnpRTzQrH0cebS9IRPgQYiSCLyboc/bYytZkc8v2BfFjjlOjTxXt3VSXS4B/kG8zGuLNaqnFw1gLA7WUZELd8JGL2C3fZtCJvFZDvtZ8vGOHup2x3QEQE5/Sen+M3KO+fs7iLDvuGnEnpXQx0DhOeJ6V59Ut3/q66C9cDg4xURgxCu310n9wGW363e7aArKl4CUNRcnlcCPSEZUta2omaiAXpOk7XZ9J3YtBrjXPUAo+AZS+qEBoEAJrvULKS+GwtHk/Aa7lltE3uzL6JSeNKYByig==; 5:WQLnVnpQV1xjl3UUnO9Yc/zOvSiB/7b0YvMLiLIdcRNI1PwsrUaLsZ49Qs4eZlmE1EFL9Rh0BNc8JaGY7BCxMP1k+dng8JmInGxFkbDjKfyrWiCwW98tjsisVpIgXPGB1ItErKKTlpGTWMofcfVTJA==; 24:umL0enxlgL1L/tK8vmUmMheenq7zb62jBwgOwdmnpCYkXoPnFbQ1nDJiHHGO8G7UA5uVSGDt21NQJ6w4OIMepviUoFHG0YzsP6fh7dNmchE=; 7:kCCVix6uBVmn3vODgNmBhKzNrsYrjkntDscOOEYxexJCBrHqg9NPv0+M2cUZrL1MGjgLWcsEVubvV1f+98vm8cNS+jVfle/q70tqCSZ0JNetk+py7Ib47kb1tJYsyPdPkuEDkArsJcTfs3IbKH6NsHHfd1l7liBF8+oRvperXbbo8n8BLIU5ScTKlEyqMhAFWFeJTS7jvmHWLphYFSFD2wJf1BNziT1NHVsgL49fXJ4=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: bc3960c2-544a-480a-c3e0-08d4fbf3b093
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254152)(48565401081)(300000503095)(300135400095)(2017052603199)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:AM2PR07MB0705;
x-ms-traffictypediagnostic: AM2PR07MB0705:
x-exchange-antispam-report-test: UriScan:(50582790962513)(82608151540597);
x-microsoft-antispam-prvs: <AM2PR07MB0705F00456764E4E9F12483F836C0@AM2PR07MB0705.eurprd07.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(10201501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(6055026)(6041248)(20161123564025)(20161123558100)(20161123560025)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB0705; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB0705;
x-forefront-prvs: 0431F981D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(39860400002)(189002)(199003)(24454002)(93886005)(106356001)(36756003)(229853002)(105586002)(53546010)(2900100001)(76176999)(54356999)(101416001)(189998001)(50986999)(6306002)(6512007)(66066001)(8676002)(68736007)(53936002)(561944003)(81166006)(5003630100001)(33656002)(8936002)(81156014)(4326008)(6506006)(6436002)(478600001)(7736002)(25786009)(39060400002)(305945005)(2501003)(14454004)(3280700002)(3660700001)(6246003)(6486002)(2906002)(966005)(5250100002)(82746002)(83716003)(102836003)(99286003)(83506001)(54906002)(6116002)(2950100002)(3846002)(316002)(5660300001)(58126008)(86362001)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM2PR07MB0705; H:AM2PR07MB0961.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <E0C475E9B7EDED4F9584AABED9D8B475@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Sep 2017 04:39:00.9494 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0705
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/j6wVUVg7EQNvyL3vhp5HHGzpfbY>
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: Fri, 15 Sep 2017 04:39:09 -0000

The issue I have here is the following. We are chartering a new WG to solve a certain problem.
The charter already hints to GRE while we have not understood the requirements and have looked at what the best solution would be to accommodate these requirements. The environment in the charter is multi-operator, which means we will have to deal with NAT in multiple ways as long as we intend to use v6.

So, the issue I have with the charter in general is that we are trying to define a protocols/signalling extensions, while we have not understood the requirements and have done a gap analysis regarding this. The first thing that should happen is look at the requirements and more importantly look at the algorithms we would need to accommodate these requirements. After do gap analysis for the existing protocols and then define the potential extensions. In the last step we should even see if other WG are not already suited to handle this activity.

On 14/09/2017, 07:07, "Zhangmingui (Martin)" <zhangmingui@huawei.com> wrote:

    Hi Alex,
    
    If "GRE passthrough NAT" was proved to be really required, there are two options:
    1. GRE in UDP while the UDP provides you the port number.
    2. The GRE Key field to be used to carry the port number. 
    For the second option, there are some existing implementations. But it is not an option if the Key field has already used for other purpose, e.g., security.
    
    However, I would say the popular usage is that the NAT happens just before the GRE tunnel. Why do we have to insert a NAT device in between two GRE tunnel endpoints?
    
    Thanks,
    Mingui
    
    ________________________________________
    From: Banana [banana-bounces@ietf.org] on behalf of Henderickx, Wim (Nokia - BE/Antwerp) [wim.henderickx@nokia.com]
    Sent: Thursday, September 14, 2017 0:51
    To: mrcullen42@gmail.com
    Cc: Alexandre Petrescu; banana@ietf.org
    Subject: Re: [Banana] Charter
    
    How will you sent GRE through NAT. GRE has no port number
    
    On 13/09/2017, 17:27, "mrcullen42@gmail.com" <mrcullen42@gmail.com> wrote:
    
        Hi Wim,
    
        Sent from my iPhone
    
        > If I hear GRE as a proposal it is very NAT unfriendly and the solution need to work across multiple providers, so this is an important consideration.
    
        Sorry, I somehow dropped this thread while I was in vacation...
    
        Why do you think that (all) GRE-based proposal(s) would be NAT unfriendly?
    
        Margaret
    
    
    _______________________________________________
    Banana mailing list
    Banana@ietf.org
    https://www.ietf.org/mailman/listinfo/banana