RFC 8772 on The China Mobile, Huawei, and ZTE Broadband Network Gateway (BNG) Simple Control and User Plane Separation Protocol (S-CUSP)
rfc-editor@rfc-editor.org Tue, 12 May 2020 00:11 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0651A3A0DCD for <ietf-announce@ietfa.amsl.com>; Mon, 11 May 2020 17:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eqkq82RsOXgG for <ietf-announce@ietfa.amsl.com>; Mon, 11 May 2020 17:11:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C85C3A0C74 for <ietf-announce@ietf.org>; Mon, 11 May 2020 17:11:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4B8F6F4074C; Mon, 11 May 2020 17:10:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8772 on The China Mobile, Huawei, and ZTE Broadband Network Gateway (BNG) Simple Control and User Plane Separation Protocol (S-CUSP)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200512001048.4B8F6F4074C@rfc-editor.org>
Date: Mon, 11 May 2020 17:10:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/P764soC-1Ts0FhEA3cooJJU3viI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 00:11:05 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8772
Title: The China Mobile, Huawei, and ZTE
Broadband Network Gateway (BNG) Simple
Control and User Plane Separation Protocol (S-CUSP)
Author: S. Hu,
D. Eastlake,
F. Qin,
T. Chua,
D. Huang
Status: Informational
Stream: Independent
Date: May 2020
Mailbox: hushujun@chinamobile.com,
d3e3e3@gmail.com,
qinfengwei@chinamobile.com,
teemong@singtel.com,
huang.guangping@zte.com.cn
Pages: 124
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-chz-simple-cu-separation-bng-protocol-06.txt
URL: https://www.rfc-editor.org/info/rfc8772
DOI: 10.17487/RFC8772
A Broadband Network Gateway (BNG) in a fixed wireline access network
is an Ethernet-centric IP edge router and the aggregation point for
subscriber traffic. Control and User Plane Separation (CUPS) for such
a BNG improves flexibility and scalability but requires various
communication between the User Plane (UP) and the Control Plane (CP).
China Mobile, Huawei Technologies, and ZTE have developed a simple
CUPS control channel protocol to support such communication: the
Simple Control and User Plane Separation Protocol (S-CUSP). S-CUSP is
defined in this document.
This document is not an IETF standard and does not have IETF
consensus. S-CUSP is presented here to make its specification
conveniently available to the Internet community to enable diagnosis
and interoperability.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC