Re: [bcause] Fwd: I-D Action: draft-haleplidis-bcause-forces-gap-analysis-00.txt

"Miaofuyou (Miao Fuyou)" <fuyou.miao@huawei.com> Thu, 09 May 2019 01:44 UTC

Return-Path: <fuyou.miao@huawei.com>
X-Original-To: bcause@ietfa.amsl.com
Delivered-To: bcause@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB07120232 for <bcause@ietfa.amsl.com>; Wed, 8 May 2019 18:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 m1vHdakENSeh for <bcause@ietfa.amsl.com>; Wed, 8 May 2019 18:44:49 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 E62E1120223 for <bcause@ietf.org>; Wed, 8 May 2019 18:44:48 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 1E8CF70B4187FF86797C for <bcause@ietf.org>; Thu, 9 May 2019 02:44:47 +0100 (IST)
Received: from DGGEML421-HUB.china.huawei.com (10.1.199.38) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 9 May 2019 02:44:46 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.13]) by dggeml421-hub.china.huawei.com ([10.1.199.38]) with mapi id 14.03.0439.000; Thu, 9 May 2019 09:44:40 +0800
From: "Miaofuyou (Miao Fuyou)" <fuyou.miao@huawei.com>
To: Jamal Hadi Salim <hadi@mojatatu.com>
CC: "bcause@ietf.org" <bcause@ietf.org>
Thread-Topic: [bcause] Fwd: I-D Action: draft-haleplidis-bcause-forces-gap-analysis-00.txt
Thread-Index: AQHU/0ECnKVHu/rFAES0l2AyxNvr+KZg8g0g///lFYCAATgHcA==
Date: Thu, 09 May 2019 01:44:40 +0000
Message-ID: <0ADCB19B1B24A64C8DC0F9AEE06214CE91BE4C17@DGGEML532-MBX.china.huawei.com>
References: <155662041187.12996.10187800655418325441@ietfa.amsl.com> <CAAFAkD806Lzoq2KSd56hkNtLtxPdyap_6jmRVk4JajvASve1hA@mail.gmail.com> <0ADCB19B1B24A64C8DC0F9AEE06214CE91BE4534@DGGEML532-MBX.china.huawei.com> <CAAFAkD8Y6E0SCjw=xBHttusofo0FdiPsy-5EaKfcXP3hcFr+MA@mail.gmail.com>
In-Reply-To: <CAAFAkD8Y6E0SCjw=xBHttusofo0FdiPsy-5EaKfcXP3hcFr+MA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.193.251]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bcause/Qkd3pRfVKb6rNTRSS6jXe2oLMBo>
Subject: Re: [bcause] Fwd: I-D Action: draft-haleplidis-bcause-forces-gap-analysis-00.txt
X-BeenThere: bcause@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <bcause.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bcause>, <mailto:bcause-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bcause/>
List-Post: <mailto:bcause@ietf.org>
List-Help: <mailto:bcause-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bcause>, <mailto:bcause-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2019 01:44:52 -0000

There are 3 interfaces: service, control and management for CU separation. As you pointed out, the management interface is on netconf domain. The service interface is tunnel. Control interface is the one for major consideration, that is SCUSP protocol. I believe your intention for ForCES is also control interface. Draft-*-yang-model is helpful to understand the interfaces, while you may refer SCUSP protocol for latest details, including various message and TLS/sub-TLV. 

The CUSP work is on-going work, it's not possible to get all drafts updated in complete sync. But, the SCUSP protocols is latest one for reference. 

> -----Original Message-----
> From: Jamal Hadi Salim [mailto:hadi@mojatatu.com]
> Sent: Wednesday, May 08, 2019 10:54 PM
> To: Miaofuyou (Miao Fuyou) <fuyou.miao@huawei.com>
> Cc: bcause@ietf.org
> Subject: Re: [bcause] Fwd: I-D Action:
> draft-haleplidis-bcause-forces-gap-analysis-00.txt
> 
> On Wed, May 8, 2019 at 4:35 AM Miaofuyou (Miao Fuyou)
> <fuyou.miao@huawei.com> wrote:
> >
> >
> > Thanks for writing the draft to explore the applicability of ForCES to BNG CU
> separation!
> >
> > BTW, the CUSP protocol draft is updated:
> > https://datatracker.ietf.org/doc/draft-cuspdt-rtgwg-cu-separation-bng-
> > protocol/
> >
> 
> Note, our draft is strictly on CUSP-s. We didnt try to explore the full coverage of
> BNG because we assume that things like management are as your draft shows
> are netconf domain etc.
> 
> We did look at your draft and made two observations:
> 
> 1) In ours we used the info model draft for the data model. It seems you have
> more details than what is provided in the info model.
> Where is you CUSP-s abstraction for the control coming from? Maybe the info
> model is outdated?
> We are thinking of publishing a new version of ours which covers all the details
> you are considering in your document - but it would be easier if there was a
> document which separately captured the abstraction (the info model was a
> good fit).
> 
> 2) Everything in the CUSP-s you have can be covered under ForCES.
> 
> cheers,
> jamal
> 
> >
> > > -----Original Message-----
> > > From: bcause [mailto:bcause-bounces@ietf.org] On Behalf Of Jamal
> > > Hadi Salim
> > > Sent: Tuesday, April 30, 2019 6:39 PM
> > > To: bcause@ietf.org
> > > Subject: [bcause] Fwd: I-D Action:
> > > draft-haleplidis-bcause-forces-gap-analysis-00.txt
> > >
> > > As a result of side discussions at IETF 104.
> > > Comments welcome.
> > >
> > > cheers,
> > > jamal
> > > ---------- Forwarded message ---------
> > > From: <internet-drafts@ietf.org>
> > > Date: Tue, Apr 30, 2019 at 6:33 AM
> > > Subject: I-D Action:
> > > draft-haleplidis-bcause-forces-gap-analysis-00.txt
> > > To: <i-d-announce@ietf.org>
> > >
> > >
> > >
> > > A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> > >
> > >
> > >         Title           : ForCES architecture CUSP applicability
> > >         Authors         : Evangelos Haleplidis
> > >                           Jamal Hadi Salim
> > >         Filename        :
> > > draft-haleplidis-bcause-forces-gap-analysis-00.txt
> > >         Pages           : 40
> > >         Date            : 2019-04-30
> > >
> > > Abstract:
> > >    This document provides a gap-analysis on how the ForCES architecture
> > >    meets the requirements for CUSP.  In addition it provides a ForCES
> > >    XML model that implements the current proposed CUSP information
> > >    model.
> > >
> > >
> > > The IETF datatracker status page for this draft is:
> > > https://datatracker.ietf.org/doc/draft-haleplidis-bcause-forces-gap-
> > > analysis/
> > >
> > > There are also htmlized versions available at:
> > > https://tools.ietf.org/html/draft-haleplidis-bcause-forces-gap-analy
> > > sis-00
> > > https://datatracker.ietf.org/doc/html/draft-haleplidis-bcause-forces
> > > -gap-analys
> > > is-00
> > >
> > >
> > > 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
> > >
> > > --
> > > bcause mailing list
> > > bcause@ietf.org
> > > https://www.ietf.org/mailman/listinfo/bcause