Re: [Banana] Charter Text w/Milestones

David Allan I <david.i.allan@ericsson.com> Fri, 31 March 2017 16:52 UTC

Return-Path: <david.i.allan@ericsson.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 8BDBE129512 for <banana@ietfa.amsl.com>; Fri, 31 Mar 2017 09:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 qXPkJ7JyBGs3 for <banana@ietfa.amsl.com>; Fri, 31 Mar 2017 09:52:40 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 9FC0012950B for <banana@ietf.org>; Fri, 31 Mar 2017 09:52:40 -0700 (PDT)
X-AuditID: c6180641-80136980000058cf-e5-58de42ff3377
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by (Symantec Mail Security) with SMTP id 2F.8A.22735.FF24ED85; Fri, 31 Mar 2017 13:52:31 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0339.000; Fri, 31 Mar 2017 12:52:38 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
CC: Margaret Cullen <margaretw42@gmail.com>, "banana@ietf.org" <banana@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Banana] Charter Text w/Milestones
Thread-Index: AQHSqXArORmNdBFkBECoq1w7R8yy+qGtogwwgAG4wID//8n/AA==
Date: Fri, 31 Mar 2017 16:52:23 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C68D26771@eusaamb105.ericsson.se>
References: <96A7BC33-FB64-487A-A60D-7AB8504C9DDF@gmail.com> <E6C17D2345AC7A45B7D054D407AA205C68D24314@eusaamb105.ericsson.se> <8D453243-ABD8-45A2-A4AE-1A58E32AEB64@kuehlewind.net>
In-Reply-To: <8D453243-ABD8-45A2-A4AE-1A58E32AEB64@kuehlewind.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyuXRPuO5/p3sRBp/X6Fg8PLGDxeLF9Y/M Fg9ezGNyYPbYOesuu8eSJT+ZPFo+LmQNYI7isklJzcksSy3St0vgynj9cR1bwWTRiuY5fxkb GDsFuxg5OSQETCR+HvjJ0sXIxSEksIFR4sXbA2wQznJGidVf5zKCVLEJGEjs+f8FzBYRMJY4 PPk7K4jNLNDEKDFjdzWILSygL3Hx3yugSRxANQYS965kQpQ7Sey58I8FxGYRUJV4feoQO4jN K+ArsalpMyPErh2MEju2/GAGSXACNRy7/QWsgVFATOL7qTVMELvEJW49mc8EcbWAxJI955kh bFGJl4//sULYShJzXl9jhqjXkViw+xMbhK0tsWzha2aIxYISJ2c+YZnAKDoLydhZSFpmIWmZ haRlASPLKkaO0uKCnNx0I8NNjMAYOSbB5riDcW+v5yFGAQ5GJR7eBRr3IoRYE8uKK3MPMUpw MCuJ8MrkAIV4UxIrq1KL8uOLSnNSiw8xSnOwKInzviu/ECEkkJ5YkpqdmlqQWgSTZeLglAJG EWeOT9nel1MVat1/fAo4LyT1MHCNd/tMdr13Mq/P6fQGt/LttJ4uvMrCw89LZv+fVenFp+6U z378zeZMod/n7tQLR5a4Vorz1GyWmTrr6w8x9pm3nrJPzbmh1hPVH3zUISlBa6Etx+8fGtfs mYvzVH5/cjkkveBjVV5kRc+lL8f7q09+2nBXiaU4I9FQi7moOBEAQMpFiI0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/banana/dOpHA6fkN3kYGqspW2oOFYGz1F0>
Subject: Re: [Banana] Charter Text w/Milestones
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, 31 Mar 2017 16:52:42 -0000

Hi Mirja:

This in some ways will probably be an unsatisfactory answer, simply as some of this is work in progress. But I'll see what I can do.

CPE configuration is currently specified in the BBF based on TR-69 with the various data models for services in the home specified in TR-181 which has a lost list of amendments to extend it . We are expecting to carry this forward as part of our cooperation with 3GPP on "5G fixed access" including hybrid access, which will mean a data model for hybrid access is to be defined.  The consensus for the providers interested in Hybrid access is that the 3GPP Gx interface (Diameter based) would be used for at least the policy aspects of the HAG/network side proxy.  IIRC TR-69 today is bootstrapped via a DHCP option and then RPC like calls to a configuration server, and we expect to extend that into the 5G N1 interface procedures for network attachment.

I'm not 100% clear on what is considered to be in the scope of signaling in this discussion. The solutions the BBF has agreements to make normative (at least draft-zhang-gre-tunnel-bonding and mp-tcp) seem to be self contained from the point of view of peer exchanges between the proxies for flow control etc.   The value we are expecting to add is in the form of deployment scenarios, addressing, and policy models.

I hope this helps
Dave



-----Original Message-----
From: Mirja Kuehlewind (IETF) [mailto:ietf@kuehlewind.net] 
Sent: Friday, March 31, 2017 10:42 AM
To: David Allan I <david.i.allan@ericsson.com>
Cc: Margaret Cullen <margaretw42@gmail.com>; banana@ietf.org; Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: [Banana] Charter Text w/Milestones

Hi David,

one question:

> Am 30.03.2017 um 13:12 schrieb David Allan I <david.i.allan@ericsson.com>:
> 
> 1) I'm focused on the converged operator case where this is likely to be a managed service, and my comments are a result of viewing the problem through that lens. As such, operators already have tools to do a chunk of this (e.g. policy and configuration) which they will simply extend as necessary vs. deploy new protocols.

Can you provide more information which tools/protocols are in use? I think one important comment for the charter is that also the signaling protocol can be an extension to an existing protocol or multiple existing protocols if bootstrapping and state control are done by different protocols, if suitable. Especially if those protocols are IETF protocols this is IETF work. But yes, cooperation with 3GPP as well as BBF seems important here. Usually we use our liaisons for this!