Re: Re: Re. Re: I-D Action: draft-hu-rtgwg-cu-separation-yang-model-01.txt

<hu.fangwei@zte.com.cn> Mon, 12 March 2018 07:26 UTC

Return-Path: <hu.fangwei@zte.com.cn>
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 1799A1204DA for <rtgwg@ietfa.amsl.com>; Mon, 12 Mar 2018 00:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 iin3yrccbdAi for <rtgwg@ietfa.amsl.com>; Mon, 12 Mar 2018 00:26:43 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 22D6F1200C5 for <rtgwg@ietf.org>; Mon, 12 Mar 2018 00:26:42 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id A558994D06DADF713169; Mon, 12 Mar 2018 15:26:39 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id 902A85409766DCA0FBF7; Mon, 12 Mar 2018 15:26:39 +0800 (CST)
Received: from xgxapp01.zte.com.cn ([10.30.14.22]) by mse01.zte.com.cn with SMTP id w2C7QT6Z004121; Mon, 12 Mar 2018 15:26:29 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
Received: from mapi (xgxapp02[null]) by mapi (Zmail) with MAPI id mid71; Mon, 12 Mar 2018 15:26:30 +0800 (CST)
Date: Mon, 12 Mar 2018 15:26:30 +0800 (CST)
X-Zmail-TransId: 2afa5aa62ba6ffffffff94a-2b3bb
X-Mailer: Zmail v1.0
Message-ID: <201803121526307457879@zte.com.cn>
In-Reply-To: <019201d3aff0$4e3b5740$4001a8c0@gateway.2wire.net>
References: 151686701151.15818.13885760302798308838@ietfa.amsl.com, 201802271504249971021@zte.com.cn, 019201d3aff0$4e3b5740$4001a8c0@gateway.2wire.net
Mime-Version: 1.0
From: <hu.fangwei@zte.com.cn>
To: <ietfa@btconnect.com>
Cc: <rtgwg@ietf.org>, <gurong_cmcc@outlook.com>, <hushujun@chinamobile.com>
Subject: =?UTF-8?B?UmU6IFJlOiBSZS4gUmU6IEktRCBBY3Rpb246IGRyYWZ0LWh1LXJ0Z3dnLWN1LXNlcGFyYXRpb24teWFuZy1tb2RlbC0wMS50eHQ=?=
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn w2C7QT6Z004121
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/jYHhrAUki_VTAs0Zy5QwH6Box3E>
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 07:26:47 -0000

Hi, Petch


Sorry for the late response.


Sincere thanks for your review and comments.  They are very helpful. 


I have updated the draft to a new version and accepte all your suggestions. The draft will be submit to the IETF website when the window is reopen. 


The draft and other CUSP design team documents are scheduled to present on Tuesday morning(20 March) in the coming IETF meeting.  Welcome to attend it .  


BTW.   The CUSP design team documents are following:


(1) "Information model of control plane and user plane separation BNG". It 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)  "Deployment Model of Control Plane and User Plane Separated BNG".  It  introduces the deployment of CU-Separation BNG.


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


 


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


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






Comments are appreciately welcomed.






Regards.


Fangwei.









发件人:t.petch <ietfa@btconnect.com>;
收件人:胡方伟10075772;rtgwg@ietf.org <rtgwg@ietf.org>;
日 期 :2018年02月28日 01:30
主 题 :Re: Re. Re: I-D Action: draft-hu-rtgwg-cu-separation-yang-model-01.txt


----- Original Message -----
From: <hu.fangwei@zte.com.cn>;
To: <ietfa@btconnect.com>;; <rtgwg@ietf.org>;
Sent: Tuesday, February 27, 2018 7:04 AM

> Hi, Petch
>
> A new version draft has been submitted to the IETF website to fix your
comments. We add the descriptions of security consideration section.
>
> More comments are appreciatedly welcomed. Thanks.

Since you are asking:-)

Imports into the yang modules must have a reference in the Reference
section of the I-D to the RFC/I-D from which they are being imported

The RFC/I-D must then have a I-D style reference to them lest they be
listed as unused references but this reference cannot appear in the YANG
module since that must be standalone plain text .

So the text of the I-D must contain the references.

draft-ietf-netmod-syslog-model shows you one way of doing this.

You must have an IANA Considerations to register the namespace and the
XML - again
draft-ietf-netmod-syslog-model
shows how this might be done.

The Abstract contains the abbreviation BNG which I do not think well
enough known yet for it not to be spelled out.

Tom Petch

>
> A new version of I-D, draft-hu-rtgwg-cu-separation-yang-model-02.txt
>
> has been successfully submitted by Fangwei Hu and posted to the
>
> IETF repository.
>
>
>
>
> Name:        draft-hu-rtgwg-cu-separation-yang-model
>
> Revision:    02
>
> Title:        YANG Data Model for Configuration Interface of
Control-Plane and User- Plane separation BNG
>
> Document date:    2018-02-26
>
> Group:        Individual Submission
>
> Pages:        32
>
> URL:
https://www.ietf.org/internet-drafts/draft-hu-rtgwg-cu-separation-yang-m
odel-02.txt
>
> Status:
https://datatracker.ietf.org/doc/draft-hu-rtgwg-cu-separation-yang-model
/
>
> Htmlized:
https://tools.ietf.org/html/draft-hu-rtgwg-cu-separation-yang-model-02
>
> Htmlized:
https://datatracker.ietf.org/doc/html/draft-hu-rtgwg-cu-separation-yang-
model-02
>
> Diff:
https://www.ietf.org/rfcdiff?url2=draft-hu-rtgwg-cu-separation-yang-mode
l-02
>
>
>
>
> Abstract:
>
>    This document defines the YANG data model for operation management
of
>
>    Control-Plane and User-Plane separation BNG.
>
>
>
>
>
>
>
>
>
>
> Regards.
>
>
> Fangwei.
>
>
>
>
>
> 发件人: <ietfa@btconnect.com>;;
> 收件人:胡方伟10075772;
> 抄送人: <rtgwg@ietf.org>;;
> 日 期 :2018年01月30日 21:27
> 主 题 :Re: Re: I-D Action:
draft-hu-rtgwg-cu-separation-yang-model-01.txt
>
>
> Fangwei
>
> I don't know if you are familiar with
>    Guidelines for Authors and Reviewers of YANG Data Model Documents
>                     draft-ietf-netmod-rfc6087bis-16
> but that is where I look for the latest on red tape for YANG modules.
>
> It is in Last Call and so is reasonably stable.
>
> It is rather big but can be dipped into to find e.g. what is needed
for
> the section on Security Considerations.
>
> Tom Petch
>
> ----- Original Message -----
> From: <hu.fangwei@zte.com.cn>;
> To: <ietfa@btconnect.com>;
> Cc: <rtgwg@ietf.org>;
> Sent: Monday, January 29, 2018 1:21 AM
>
> > Hi, Petch
> >
> >
> > Thanks for your comments, I will update the draft to fix the
> questions.
> >
> >
> > Regards
> >
> >
> > Fangwei.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 原始邮件
> >
> >
> >
> > 发件人: <ietfa@btconnect.com>;;
> > 收件人: <rtgwg@ietf.org>;;
> > 抄送人:胡方伟10075772;
> > 日 期 :2018年01月27日 01:45
> > 主 题 :Re: I-D Action: draft-hu-rtgwg-cu-separation-yang-model-01.txt
> >
> >
> > This I-D is still lacking some basics e.g. you cannot have a YANG
> module
> > without IANA Considerations or without Security Considerations nor
are
> > most of the necessary Normative References listed..
> >
> > Tom Petch
> >
> > ----- Original Message -----
> > From: <internet-drafts@ietf.org>;
> > To: <i-d-announce@ietf.org>;
> > Sent: Thursday, January 25, 2018 7:56 AM
> >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > >
> > >
> > >         Title           : YANG Data Model for Configuration
> Interface
> > of Control-Plane and User- Plane separation BNG
> > >         Authors         : Fangwei Hu
> > >                           RongRong Hua
> > >                           Shujun Hu
> > > Filename        : draft-hu-rtgwg-cu-separation-yang-model-01.txt
> > > Pages           : 30
> > > Date            : 2018-01-24
> > >
> > > Abstract:
> > >    This document defines the YANG data model for operation
> management
> > of
> > >    Control-Plane and User-Plane separation BNG.
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > >
> >
>
https://datatracker.ietf.org/doc/draft-hu-rtgwg-cu-separation-yang-model
> > /
> > >
> > > There are also htmlized versions available at:
> > >
> https://tools.ietf.org/html/draft-hu-rtgwg-cu-separation-yang-model-01
> > >
> >
>
https://datatracker.ietf.org/doc/html/draft-hu-rtgwg-cu-separation-yang-
> > model-01
> > >
> > > A diff from the previous version is available at:
> > >
> >
>
https://www.ietf.org/rfcdiff?url2=draft-hu-rtgwg-cu-separation-yang-mode
> > l-01
> > >
> > >
> > > Please note that it may take a couple of minutes from the time of
> > submission
> > > until the htmlized version and diff are available at
tools.ietf.org.
> > >
> > > Internet-Drafts are also available by anonymous FTP at:
> > > ftp://ftp.ietf.org/internet-drafts/
> > >
> > > _______________________________________________
> > > I-D-Announce mailing list
> > > I-D-Announce@ietf.org
> > > https://www.ietf.org/mailman/listinfo/i-d-announce
> > > Internet-Draft directories: http://www.ietf.org/shadow.html
> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt