< draft-cuspdt-rtgwg-cu-separation-yang-model-00.txt   draft-cuspdt-rtgwg-cu-separation-yang-model-01.txt >
IETF RTGWG Fangwei Hu IETF RTGWG Fangwei Hu
Internet-Draft RongRong Hua Internet-Draft ZTE Corporation
Intended status: Standards Track ZTE Corporation Intended status: Standards Track Shujun Hu
Expires: February 22, 2019 Shujun Hu Expires: June 8, 2019 Fengwei Qin
Fengwei Qin
China Mobile China Mobile
August 21, 2018 Dec 5, 2018
YANG Data Model for Configuration Interface of Control-Plane and User- YANG Data Model for Configuration Interface of Control-Plane and User-
Plane separation BNG Plane separation BNG
draft-cuspdt-rtgwg-cu-separation-yang-model-00.txt draft-cuspdt-rtgwg-cu-separation-yang-model-01.txt
Abstract Abstract
This document defines the YANG data model for operation management of This document defines the YANG data model for management of Control-
Control-Plane and User-Plane separation BNG (Broadband Network Plane and User-Plane separation BNGs (Broadband Network Gateways).
Gateway).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 22, 2019. This Internet-Draft will expire on June 8, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 31 skipping to change at page 2, line 29
5. Security Considerations . . . . . . . . . . . . . . . . . . . 22 5. Security Considerations . . . . . . . . . . . . . . . . . . . 22
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
8.1. Normative References . . . . . . . . . . . . . . . . . . 25 8.1. Normative References . . . . . . . . . . . . . . . . . . 25
8.2. Informative References . . . . . . . . . . . . . . . . . 26 8.2. Informative References . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
The main idea of BNG Control-Plane and User-Plane separation is to The main idea of Broadband Network Gateway (BNG) Control-Plane and
extract and centralize the user management functions of multiple BNG User-Plane separation is to extract and centralize the user
devices, forming an unified and centralized control plane (CP), while management functions of multiple BNG devices, forming an unified and
the traditional router's Control Plane and forwarding plane are both centralized control plane (CP), while the traditional router's
preserved on BNG devices in the form of a user plane (UP).We name the control and forwarding information are both preserved on BNG devices
control-Plane and User-plane separation BNG as vBNG. in the form of a user plane (UP). We name the control-Plane and
User-plane separation BNG as vBNG (virtual BNG).
The architecture of Control-plane and user-plane separated BNG is The architecture of Control-plane and User-plane separated BNG is
shown as the following figure. shown as the following figure.
+--------------------------------------+ +--------------------------------------+
| | | |
| vBNG-CP | | vBNG-CP |
| | | |
+----+--------------+--------------+---+ +----+--------------+--------------+---+
| | | | | |
Service | Control | Management| Service | Control | Management|
Interface| Interface| Interface| Interface| Interface| Interface|
skipping to change at page 3, line 35 skipping to change at page 3, line 35
| Access Network | | Access Network |
| | | |
+--------+--------+ +--------+--------+
| |
+----+----+ +----+----+
| | | |
| User | | User |
+---------+ +---------+
Figure 1: Architecture of C/U separated BNG Figure 1: Architecture of C/U separated BNG
There are three interfaces between vBNG-CP and vBNG-UP: Service There are three interfaces between vBNG-CP(vBNG Control Plane) and
interface, control interface and management interface. The service vBNG-UP(vBNG User Plane): Service interface, control interface and
interface is used to carry PPPoE/IPoE dialup packets between user management interface. The service interface is used to carry PPPoE/
plane and control plane. The requirement and possible solution is IPoE dialup packets between user plane and control plane. The
defined in the [I-D.huang-nvo3-vxlan-extension-for-vbras]. Control requirements and possible solution are defined in the
interface is used for setting forwarding entries of user plane [I-D.hu-nvo3-vxlan-gpe-extension-for-vbng]. The control interface is
through CUSP [I-D.cuspdt-rtgwg-cu-separation-bng-protocol] or other used for setting forwarding entries of the user plane using CUSP
protocols. Management interface is used by vBNG-CP to carry out [I-D.cuspdt-rtgwg-cu-separation-bng-protocol] or other protocols.
related configurations of vBNG-UP through NETCONF protocol [RFC6241]. The management interface is used by vBNG-CP to carry out related
configurations of vBNG-UP through NETCONF protocol [RFC6241].
This document defines the YANG data model for vBNG(vBNG-CP and vBNG- This document defines the YANG data model for vBNG(vBNG-CP and vBNG-
UP). There are three types of YANG data model for vBNG in this UP). There are three types of YANG data model for vBNG in this
document: The YANG data models for vBNG-CP, the YANG data models for document: The YANG data models for vBNG-CP, the YANG data models for
vBNG-UP by network management directly, and the YANG data models for vBNG-UP by network management directly, and the YANG data models for
BGN-UP through the management interfaces among the vBNG-UP and vBNG- BGN-UP through the management interfaces among the vBNG-UP and vBNG-
CP. CP.
2. Conventions used in this document 2. Conventions used in this document
skipping to change at page 5, line 5 skipping to change at page 5, line 5
configuration, ACL and QoS. configuration, ACL and QoS.
The vBNG-UP interface configuration is to configure the basic The vBNG-UP interface configuration is to configure the basic
interface informations of vBNG-UP element, such as interface name, interface informations of vBNG-UP element, such as interface name,
the VLAN parameters for the sub-interface. the VLAN parameters for the sub-interface.
The control channel is to configure the CUSP parameters. The control The control channel is to configure the CUSP parameters. The control
channel parameters include: name, id, port, CUSP version, hello channel parameters include: name, id, port, CUSP version, hello
interval, dead time, and keepalive time. interval, dead time, and keepalive time.
The VXLAN tunnel is the suggestion service interface protocol between The VXLAN tunnel is the suggested service interface protocol between
vBNG-CP and vBNG-UP. The VXLAN tunnel parameters include: tunnel- vBNG-CP and vBNG-UP. The VXLAN tunnel parameters include: tunnel-
source-ip,tunnel-destination-ip, vxlan-id, vxlan-tunnel-id, vxlan- source-ip,tunnel-destination-ip, vxlan-id, vxlan-tunnel-id, vxlan-
tunnel-name, etc. tunnel-name, etc.
The ACL information includes ipv4-acl,ipv6-acl,link-acl,etc. The The ACL information includes ipv4-acl,ipv6-acl,link-acl,etc. The
YANG data model for ACL refers to [I-D.ietf-netmod-acl-model] YANG data model for ACL refers to [I-D.ietf-netmod-acl-model]
The QoS information includes IP-DSCP, MPLS,VPLS, VPWS etc. The YANG The QoS information includes IP-DSCP, MPLS,VPLS, VPWS etc. The YANG
data model for QoS refers to [I-D.asechoud-rtgwg-qos-model] data model for QoS refers to [I-D.asechoud-rtgwg-qos-model]
skipping to change at page 16, line 35 skipping to change at page 16, line 35
enum chap { enum chap {
value 2 ; value 2 ;
description "configure chap authentication!"; description "configure chap authentication!";
} }
enum mschapv1 { enum mschapv1 {
value 6 ; value 6 ;
description "configure mschapv1 authentication!"; description "configure mschapv1 authentication!";
} }
enum mschapv2 { enum mschapv2 {
value 7 ; value 7 ;
description "configure mschapv2 authentication!"; description "configure mschapv2 tication!";
} }
enum pap-chap { enum pap-chap {
value 21 ; value 21 ;
description "configure pap-chap authentication!"; description "configure pap-chap authentication!";
} }
} }
default pap-chap ; default pap-chap ;
description 'Set ppp authentication'; description 'Set ppp authentication';
} }
leaf ppp-check-magic-num { leaf ppp-check-magic-num {
skipping to change at page 18, line 5 skipping to change at page 18, line 5
enum enable { enum enable {
value 1 ; value 1 ;
description "enable pppoe ac cookie check"; description "enable pppoe ac cookie check";
} }
} }
default enable ; default enable ;
description 'Check options'; description 'Check options';
} }
leaf pppoe-password-string { leaf pppoe-password-string {
type string ; type string ;
description 'Set authen fail password error string'; description 'Set authentication failure password string';
} }
leaf pppoe-username-string { leaf pppoe-username-string {
type string ; type string ;
description 'Set authen fail username error string'; description 'Set authentication failure username error string';
} }
choice ppp-quick-redial { choice ppp-quick-redial {
case quick-redial-disable { case quick-redial-disable {
leaf ppp-quick-redial-disable { leaf ppp-quick-redial-disable {
type enumeration { type enumeration {
enum disable { enum disable {
value 0 ; value 0 ;
description "disable ppp quick redial"; description "disable ppp quick redial";
} }
skipping to change at page 25, line 15 skipping to change at page 25, line 15
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.asechoud-rtgwg-qos-model] [I-D.asechoud-rtgwg-qos-model]
Choudhary, A., Jethanandani, M., Strahle, N., Aries, E., Choudhary, A., Jethanandani, M., Strahle, N., Aries, E.,
and I. Chen, "YANG Model for QoS", draft-asechoud-rtgwg- and I. Chen, "YANG Model for QoS", draft-asechoud-rtgwg-
qos-model-07 (work in progress), July 2018. qos-model-07 (work in progress), July 2018.
[I-D.ietf-netmod-acl-model] [I-D.ietf-netmod-acl-model]
Jethanandani, M., Huang, L., Agarwal, S., and D. Blair, Jethanandani, M., Agarwal, S., Huang, L., and D. Blair,
"Network Access Control List (ACL) YANG Data Model", "Network Access Control List (ACL) YANG Data Model",
draft-ietf-netmod-acl-model-19 (work in progress), April draft-ietf-netmod-acl-model-21 (work in progress),
2018. November 2018.
[I-D.ietf-rtgwg-lne-model] [I-D.ietf-rtgwg-lne-model]
Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X. Berger, L., Hopps, C., Lindem, A., Bogdanovic, D., and X.
Liu, "YANG Model for Logical Network Elements", draft- Liu, "YANG Model for Logical Network Elements", draft-
ietf-rtgwg-lne-model-10 (work in progress), March 2018. ietf-rtgwg-lne-model-10 (work in progress), March 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 26, line 21 skipping to change at page 26, line 21
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <https://www.rfc-editor.org/info/rfc8040>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[I-D.cuspdt-rtgwg-cu-separation-bng-protocol] [I-D.cuspdt-rtgwg-cu-separation-bng-protocol]
Hu, S., Wang, Z., Qin, F., Li, Z., Song, J., and T. Chua, Hu, S., Eastlake, D., Wang, Z., Qin, F., Li, Z., Song, J.,
"Control-Plane and User-Plane separation BNG control and T. Chua, "Control-Plane and User-Plane Separation BNG
channel Protocol", draft-cuspdt-rtgwg-cu-separation-bng- Control Channel Protocol", draft-cuspdt-rtgwg-cu-
protocol-01 (work in progress), July 2018. separation-bng-protocol-03 (work in progress), November
2018.
[I-D.huang-nvo3-vxlan-extension-for-vbras] [I-D.hu-nvo3-vxlan-gpe-extension-for-vbng]
Huang, L. and S. Hu, "VxLAN Extension Requirement for Hu, S., Qin, F., Li, Z., Wang, Z., and T. Ao, "VXLAN GPE
Signaling Exchange Between Control and User Plane of Extension for Packets Exchange Between Control and User
vBras", draft-huang-nvo3-vxlan-extension-for-vbras-00 Plane of vBNG", draft-hu-nvo3-vxlan-gpe-extension-for-
(work in progress), March 2017. vbng-00 (work in progress), June 2018.
Authors' Addresses Authors' Addresses
Fangwei Hu Fangwei Hu
ZTE Corporation ZTE Corporation
No.889 Bibo Rd No.889 Bibo Rd
Shanghai 201203 Shanghai 201203
China China
Phone: +86 21 68896273 Phone: +86 21 68896273
Email: hu.fangwei@zte.com.cn Email: hu.fangwei@zte.com.cn
RongRong Hua
ZTE Corporation
No.50 Software Avenue,Yuhuatai District
Nanjing, Jiangsu Province 210012
China
Email: hua.rongrong@zte.com.cn
Shujun Hu Shujun Hu
China Mobile China Mobile
32 Xuanwumen West Ave, Xicheng District 32 Xuanwumen West Ave, Xicheng District
Beijing 100053 Beijing 100053
China China
Email: shujun_hu@outlook.com Email: shujun_hu@outlook.com
Fengwei Qin Fengwei Qin
China Mobile China Mobile
32 Xuanwumen West Ave, Xicheng District 32 Xuanwumen West Ave, Xicheng District
Beijing, Beijing 100053 Beijing, Beijing 100053
China China
Email: qinfengwei@chinamobile.com Email: qinfengwei@chinamobile.com
 End of changes. 18 change blocks. 
50 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/