Re: Report of CUSP design team research and welcome U involving into this work

"Acee Lindem (acee)" <acee@cisco.com> Mon, 12 March 2018 11:34 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1FE1272E1 for <rtgwg@ietfa.amsl.com>; Mon, 12 Mar 2018 04:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level:
X-Spam-Status: No, score=-14.53 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_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 XQkGyHfr-539 for <rtgwg@ietfa.amsl.com>; Mon, 12 Mar 2018 04:34:12 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F6D8127333 for <rtgwg@ietf.org>; Mon, 12 Mar 2018 04:34:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30828; q=dns/txt; s=iport; t=1520854452; x=1522064052; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9jVpIIx7sU8wk1LLAk35teO9APXhVzcz10+Cf5lDI5w=; b=MVQIaWp46ldzwAcncMlZdnSDFJgDurNgsVpIQJO9r4sNYc/ES8svqUdv uethQWlyXDp3XxR+/31bR8o3cV9YyTF9lEDnXcWf1/h92fzmruXCag3q4 yn/ytmw42nZDwsg1YBxOKFe/kVaPjrRUcMBMubdKm/4RVXR5m2/4ZiLEX I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ALAQBrZaZa/4MNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJadmZvKAqDRoofjXGCBHsblDIUggEKJYUAAhqCfCE0GAECAQE?= =?us-ascii?q?BAQEBAmsnhSMBAQEEI1YQAgEGAhEBAgECIQcDAgICMBQDBggBAQQBDQWDGgSBF?= =?us-ascii?q?kwDFQ+NUJ1tgiaIXYIVBYU1gi6DPCmCTzaBLIICAoE1AgJYFoJSMIIyBIg1TIo?= =?us-ascii?q?4hx0JAolRhxAOjlORIQIREwGBKwEeOA2BRXAVZAGCGAmEPQF3AYxcgRgBAQE?=
X-IronPort-AV: E=Sophos; i="5.47,461,1515456000"; d="scan'208,217"; a="82172947"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Mar 2018 11:34:11 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w2CBYB9t011390 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 12 Mar 2018 11:34:11 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 12 Mar 2018 07:34:10 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Mon, 12 Mar 2018 07:34:10 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ariel Gu <gurong@chinamobile.com>, =?utf-8?B?J+mhviDmiI4n?= <gurong_cmcc@outlook.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
CC: "victor.lopezalvarez@telefonica.com" <victor.lopezalvarez@telefonica.com>, "hushujun@chinamobile.com" <hushujun@chinamobile.com>, "russ@riw.us" <russ@riw.us>, "shares@ndzh.com" <shares@ndzh.com>
Subject: Re: Report of CUSP design team research and welcome U involving into this work
Thread-Topic: Report of CUSP design team research and welcome U involving into this work
Thread-Index: AdO5tSJ+VO84QHk13EqHlWyqC8HebgAQOaiA
Date: Mon, 12 Mar 2018 11:34:10 +0000
Message-ID: <E2F70763-5A4C-4EF4-A005-26B54AD7D66B@cisco.com>
References: <001b01d3b9b5$23a37390$6aea5ab0$@chinamobile.com>
In-Reply-To: <001b01d3b9b5$23a37390$6aea5ab0$@chinamobile.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: multipart/alternative; boundary="_000_E2F707635A4C4EF4A00526B54AD7D66Bciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/h5R2OTaPJ3CwW2LRrquu_t8NSzQ>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2018 11:34:20 -0000

The actual BNG deployment/performance number would be interesting to include in the RTG WG presentation.
Thanks,
Acee

From: Ariel Gu <gurong@chinamobile.com>;
Date: Sunday, March 11, 2018 at 11:49 PM
To: Acee Lindem <acee@cisco.com>;, '顾 戎' <gurong_cmcc@outlook.com>;, Routing WG <rtgwg@ietf.org>;
Cc: "victor.lopezalvarez@telefonica.com"; <victor.lopezalvarez@telefonica.com>;, "hushujun@chinamobile.com"; <hushujun@chinamobile.com>;, Russ White <russ@riw.us>;, Susan Hares <shares@ndzh.com>;
Subject: RE: Report of CUSP design team research and welcome U involving into this work

Hi, Acee.

We have the trial of BNG (not the BGP) in several provinces. Test around BNG basically classifies as follows. We can go detailed discussion if you are interested in it.
Functionality

Basic test considering BNG-CP

BNG access function

COA/DM function

QoS function

Performance

Dial rate of users on BNG-CP/BNG-UP

Maximum Sessions on BNG-CP /BNG-UP

Reliability

BNG-CP  failure

BNG-UP reload

HA of BNG-UP

Channel of BNG-CP and BNG-UP failure


Gu Rong
gurong_cmcc@outlook.com<mailto:gurong_cmcc@outlook.com>
gurong@chinamobile.com
发件人: Acee Lindem (acee) [mailto:acee@cisco.com]
发送时间: 2018年3月9日 20:25
收件人: 顾 戎; rtgwg@ietf.org
抄送: victor.lopezalvarez@telefonica.com; hushujun@chinamobile.com; russ@riw.us; gurong@chinamobile.com; shares@ndzh.com
主题: Re: Report of CUSP design team research and welcome U involving into this work

Hi Gu,

Have you implemented this BGP deployment model or is it still in the IETF draft and powerpoint phase? If it has been implemented, can you share any benchmarks?

Acee

From: rtgwg <rtgwg-bounces@ietf.org<mailto:rtgwg-bounces@ietf.org>> on behalf of 顾 戎 <gurong_cmcc@outlook.com<mailto:gurong_cmcc@outlook.com>>
Date: Thursday, March 8, 2018 at 11:32 PM
To: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Cc: "victor.lopezalvarez@telefonica.com<mailto:victor.lopezalvarez@telefonica.com>" <victor.lopezalvarez@telefonica.com<mailto:victor.lopezalvarez@telefonica.com>>, "hushujun@chinamobile.com<mailto:hushujun@chinamobile.com>" <hushujun@chinamobile.com<mailto:hushujun@chinamobile.com>>, Russ White <russ@riw.us<mailto:russ@riw.us>>, "gurong@chinamobile.com<mailto:gurong@chinamobile.com>" <gurong@chinamobile.com<mailto:gurong@chinamobile.com>>, Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Subject: Report of CUSP design team research and welcome U involving into this work


Hi, dear all.



Here we give a short introduction of CUSP design team research work. Recently CloudCO project on CU separation BNG device has been approved. Now WT-384 is now approved and officially TR-384. In TR-384, the CU-separated BNG architecture is provided with control plane (BNG-CP) and user plane (BNG-UP) separation. This new architecture brings several advantages such as centralized session management, flexible address allocation, and high scalability and cost-efficient redundancy and so on.



Besides the architecture, there are reserved work to be done with details. Here we present several related drafts.

(1) One is the "Information model of control plane and user plane separation BNG" which describes the information model of BNG-CP and BNG-UP in order to form the related data model.
https://www.ietf.org/internet-drafts/draft-cuspdt-rtgwg-cu-separation-infor-model-00.txt

(2) Another is "Deployment Model of Control Plane and User Plane Separated BNG" introducing the deployment of CU-Separation BNG.

https://www.ietf.org/internet-drafts/draft-cuspdt-rtgwg-cu-separation-bng-deployment-01.txt



(3) Besides the draft "Requirement for the protocol of the control plane and user planes separation BNG" involving the communication protocol requirement of BNG-CP and BNG-UP.

https://www.ietf.org/internet-drafts/draft-cuspdt-rtgwg-cusp-requirements-01.txt



Any comments are welcomed.



Gu Rong

gurong_cmcc@outlook.com<mailto:gurong_cmcc@outlook.com>

gurong@chinamobile.com<mailto:gurong@chinamobile.com>