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

顾 戎 <gurong_cmcc@outlook.com> Fri, 09 March 2018 04:32 UTC

Return-Path: <gurong_cmcc@outlook.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 AB6FA126C22 for <rtgwg@ietfa.amsl.com>; Thu, 8 Mar 2018 20:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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=outlook.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 diollzEIiLS5 for <rtgwg@ietfa.amsl.com>; Thu, 8 Mar 2018 20:32:19 -0800 (PST)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255050.outbound.protection.outlook.com [40.92.255.50]) (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 0A900120227 for <rtgwg@ietf.org>; Thu, 8 Mar 2018 20:32:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8xxP21c3t6YbhKFMvel5tRu4DjEeteSxCDP4tRz20KI=; b=nISW3BRmb4DHOHxUHslzigua9h1jPHA3WsbxD2b24P/FQhaOwRMOjYbHD7q27lAIp8Kk/RFDsrtkZOp9sldlcZUgkkfXPC0hTPdTbSH8vI9d8+Frd2Zkfh0MyBeCjDk0T/mEFGuZm91/QqRT30Uw8K4jjyYve5JnEkQlGIqitZb/UOFmO/dQv3dRvl4KfyLta3uubzzopYd6Xsm0kDt8r9NsDLERccuEdMqgShfXWZxSqvpunrkjDuvTD8jzgjNUAVyB2EKmlC6bgDwugtwPVCW2uUXM9+Mc2C1HtFxnHZALqPhTU+K6SReKd5H9E67SYL9StTwe8W0sZ1+VfscQDA==
Received: from SG2APC01FT056.eop-APC01.prod.protection.outlook.com (10.152.250.60) by SG2APC01HT184.eop-APC01.prod.protection.outlook.com (10.152.251.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.444.13; Fri, 9 Mar 2018 04:32:14 +0000
Received: from HK2PR02MB1251.apcprd02.prod.outlook.com (10.152.250.51) by SG2APC01FT056.mail.protection.outlook.com (10.152.251.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.527.18 via Frontend Transport; Fri, 9 Mar 2018 04:32:14 +0000
Received: from HK2PR02MB1251.apcprd02.prod.outlook.com ([fe80::acde:9696:83ad:57b]) by HK2PR02MB1251.apcprd02.prod.outlook.com ([fe80::acde:9696:83ad:57b%14]) with mapi id 15.20.0548.016; Fri, 9 Mar 2018 04:32:14 +0000
From: =?gb2312?B?ucsgyNY=?= <gurong_cmcc@outlook.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>
CC: "victor.lopezalvarez@telefonica.com" <victor.lopezalvarez@telefonica.com>, "hushujun@chinamobile.com" <hushujun@chinamobile.com>, "gurong@chinamobile.com" <gurong@chinamobile.com>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "wangzitao@huawei.com" <wangzitao@huawei.com>, "jefftant.ietf@gmail.com" <jefftant.ietf@gmail.com>, "chrisbowers.ietf@gmail.com" <chrisbowers.ietf@gmail.com>, "shares@ndzh.com" <shares@ndzh.com>, "russ@riw.us" <russ@riw.us>
Subject: 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: AQHTt1DlVO84QHk13EqHlWyqC8Hebg==
Date: Fri, 9 Mar 2018 04:32:13 +0000
Message-ID: <HK2PR02MB12514F5935AD5C273FA8B2C98BDE0@HK2PR02MB1251.apcprd02.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:A437E63C8F1314970D0B90A8C4A81CBFD25AC4E1EFE5C50471767266FAB23301; UpperCasedChecksum:F94CFA9B6CA98694BA25C1AB636C4D3BBB4EB92F7389DF89750FF8E1C15B5C38; SizeAsReceived:7408; Count:44
x-tmn: [ZESXhYWB54J97Eml7SncxVLVHrn2zzCi7fe/izeQry0=]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT184; 6:lf6e9n4LvkPtuHbiS0pTkzkh5OkXxZXKwCgfdN/NMkyx16K5TZ2TrbxoQspTFQdgTu0xkh4S0di44p8Bs9HvthFBQP20iZ5Y9apPCJnls9+KwpweTXqe7caMbksgnArAlT2cceUuZ5kZL4Cgu5KkBd7T076UWCzqSBtB6YhGDMJczSk06S48TZqWL8EJA9+M7sx7CUa9NF6QPHeJmAgousoL6eEAZrhysV4gGXz6iCVMLf5UTHTpsaAoT/OYIrbguGit+fJ0jWi3e8YkUOWJHiytF7XsOFAg1V0FhzDJv9rQzzhnahbhnsfBh5FIoRfgwiPwgYehY0zDHT2xsGdx7KrmklE33EnHzgt1ulKdAho=; 5:5zK1272mekxylrSDEdMS6gzeiUeA6TF4QGVRGxT3Y1UY7sTBas1HTj4y2qDEvP27hNlCzfNdtra4cfpdk9yfm1NGwLHaygUJKPCbmsIRLEPKhVAN07ypDPzsmObPq4SpOFhkbz9IYasl3CMISxQzJzyXJhck5/PWVjHOSCssur4=; 24:yNGJx5JcdvDT8fZ1/10tBSlU3w1it5O1Jwy9/kZXA3E/LH9fuQSXriLMCZc5u5mNbqCJiNTz+GPffdKfaCS1BGw4mg+cdIB9nMNegLvLr0M=; 7:xAaeeGXQcWlNRj+OmpLBOC7h3CNBHI/nFkj9SHKscNaLS6+z/Lgd+NhtMXzI6S4Pzs7BxoGHnYSpxcpRC/SOo5on3CdpoxJsuAFZRUwzHuLbmqAq49p4lwOAunoIGbVKlwnJvyPjglh+QgdK6RCHVJEss6CW6cm+6olsC1vVBdV7hPn2nfK1DfX7DW8xFTDwzOds4Wl000XmnZZQeWijC4yToWl39r0zXh3QQDKLdi9RTg21VyWYoMwSyP1YN8At
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1601125374)(1603101448)(1701031045); SRVR:SG2APC01HT184;
x-ms-traffictypediagnostic: SG2APC01HT184:
x-ms-office365-filtering-correlation-id: 097446a7-56df-4614-fea3-08d58576bba1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:SG2APC01HT184; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT184;
x-forefront-prvs: 0606BBEB39
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SG2APC01HT184; H:HK2PR02MB1251.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:;
x-microsoft-antispam-message-info: bsvLgAqSDBFdKR3u49YUbkghvy8dtkGegt2CmxaTjD2mPJx1J9M5A87kJTHAxFmdh5QHKRSH0l0LvnZpyOGkqlqxk7V8TXd9WOaSJkR2NrntLSnCcopGFYy3uMmmou0LX3lW1JDxFY6Dql4sWNQlMEXSILvBAyw1wdCexUdBbdq9OQyn7lSyCSvXlJ4S7+81
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR02MB12514F5935AD5C273FA8B2C98BDE0HK2PR02MB1251apcp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 097446a7-56df-4614-fea3-08d58576bba1
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Mar 2018 04:32:14.0259 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT184
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/9ZfxVfFh4KojbZUCgZlLjVn9IT0>
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: Fri, 09 Mar 2018 04:32:22 -0000

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

<https://datatracker.ietf.org/doc/draft-cuspdt-rtgwg-cu-separation-infor-model>
(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://datatracker.ietf.org/doc/draft-cuspdt-rtgwg-cusp-requirements>https://www.ietf.org/internet-drafts/draft-cuspdt-rtgwg-cusp-requirements-01.txt


Any comments are welcomed.


Gu Rong

gurong_cmcc@outlook.com

gurong@chinamobile.com