[Teas] Consistency checked & WG adoption Request//Re: Review and thoughts on draft-zheng-teas-gmpls-controller-inter-work

"Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com> Mon, 25 March 2019 19:29 UTC

Return-Path: <zhenghaomian@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025E3120020; Mon, 25 Mar 2019 12:29:15 -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 ztu79ubuhy3w; Mon, 25 Mar 2019 12:29:12 -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 1290512001A; Mon, 25 Mar 2019 12:29:12 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id CDC1E17FF00CBED91FAC; Mon, 25 Mar 2019 19:29:09 +0000 (GMT)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 25 Mar 2019 19:29:09 +0000
Received: from DGGEML511-MBX.china.huawei.com ([169.254.1.239]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0415.000; Tue, 26 Mar 2019 03:29:02 +0800
From: "Zhenghaomian (Zhenghaomian, Optical Technology Research Dept)" <zhenghaomian@huawei.com>
To: 'Lou Berger' <lberger@labn.net>, "'adrian@olddog.co.uk'" <adrian@olddog.co.uk>, "'teas@ietf.org'" <teas@ietf.org>
CC: "'draft-zheng-teas-gmpls-controller-inter-work@ietf.org'" <draft-zheng-teas-gmpls-controller-inter-work@ietf.org>, "draft-li-teas-hierarchy-ip-controllers@ietf.org" <draft-li-teas-hierarchy-ip-controllers@ietf.org>
Thread-Topic: Consistency checked & WG adoption Request//Re: [Teas] Review and thoughts on draft-zheng-teas-gmpls-controller-inter-work
Thread-Index: AdTjQKp/5WNxXJSCTXySJbStF4sFog==
Date: Mon, 25 Mar 2019 19:29:02 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B7A26C7@dggeml511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.220.71.102]
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/teas/LOWs0LrGicGFDtGPfawPj9ZMv6E>
Subject: [Teas] Consistency checked & WG adoption Request//Re: Review and thoughts on draft-zheng-teas-gmpls-controller-inter-work
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 19:29:15 -0000

Hi, Chairs, WG, 

As indicated in previous emails, we have been working on updating draft-zheng-teas-gmpls-controller-inter-work and addressing the comments from chairs. We are now writing to indicate that the controller structure in this work is in good consistency with the counterpart in draft-li-teas-hierarchy-ip-controllers. 

Given the progress so far, the authors would like to ask for WG adoption in the WG session, thank you. 

Best wishes,
Haomian (on behalf of all the authors & contributors)

-----邮件原件-----
发件人: Zhenghaomian (Zhenghaomian, Optical Technology Research Dept) 
发送时间: 2019年2月15日 17:23
收件人: Lou Berger <lberger@labn.net>et>; adrian@olddog.co.uk; teas@ietf.org
抄送: draft-zheng-teas-gmpls-controller-inter-work@ietf.org
主题: Re: [Teas] Review and thoughts on draft-zheng-teas-gmpls-controller-inter-work

Hi, Lou, Adrian, Pavan, WG, 

We followed up the previous comments by updating this work with -03, with the first 2 comments addressed. Your review and comments are highly appreciated, thanks.

The 3rd one would be always ongoing and we can continue working after WG adoption, draft details can be found as follow. 

Name:		draft-zheng-teas-gmpls-controller-inter-work
Revision:	03
Title:		Interworking of GMPLS Control and Centralized Controller System
Document date:	2019-02-15
Group:		Individual Submission
Pages:		14
URL:            https://www.ietf.org/internet-drafts/draft-zheng-teas-gmpls-controller-inter-work-03.txt 
Status:         https://datatracker.ietf.org/doc/draft-zheng-teas-gmpls-controller-inter-work/ 
Htmlized:       https://tools.ietf.org/html/draft-zheng-teas-gmpls-controller-inter-work-03 
Htmlized:       https://datatracker.ietf.org/doc/html/draft-zheng-teas-gmpls-controller-inter-work 
Diff:           https://www.ietf.org/rfcdiff?url2=draft-zheng-teas-gmpls-controller-inter-work-03 

Best wishes,
Haomian (on behalf of all authors & contributors)

-----邮件原件-----
发件人: Lou Berger [mailto:lberger@labn.net]
发送时间: 2018年12月8日 21:54
收件人: Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research Dept) <zhenghaomian@huawei.com>om>; adrian@olddog.co.uk; teas@ietf.org
抄送: draft-zheng-teas-gmpls-controller-inter-work@ietf.org
主题: Re: [Teas] Review and thoughts on draft-zheng-teas-gmpls-controller-inter-work

Hi,

Since you asked....

I think Pavan and I have no reservations about this work progressing in the WG.  We do have a couple of things that think it would be worth clarifying before adoption poll.

1) it would be good to clarify that ACTN is one (example) method for implementing centralized control.  The document is good in some places, e.g., section 1, but less so in others. It would be good to ensure that the reader, particularly those new to the topic, understand that ACTN is just one way to provide centralized control, e.g., section 2.3 reads as if ACTN is the sole supported method; a PCE based approach is mentioned in the document but this is buried at end of section 5.2.

2) It would best if the examples lined up with what we are covering in the WG.  For example, I don't believe we've had any suggestion or discussion use of OSPF-TE as an SBI as shown in figure 1.  (A nit, it should be NetConf/YANG.) If your intent is to propose this, than this should be clarified and perhaps added to section 7.

3) We see Section 7 as the (future) core of the document and clearly a work in progress.  This is can be addressed pre or post WG adoption.

Thanks,
Pavan and Lou

On 12/6/2018 7:38 AM, Zhenghaomian (Zhenghaomian, Optical &Microwave Technology Research Dept) wrote:
> Hi, Adrian,
>
> Thank you for the comments, we just updated this work to -02 and hopefully all the comments are addressed. We are also looking forward to see the feedback from the chairs, plans and/or advices are highly appreciated, thank you.
>
> FYI, the -02 draft is now available at:
> URL:            https://www.ietf.org/internet-drafts/draft-zheng-teas-gmpls-controller-inter-work-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-zheng-teas-gmpls-controller-inter-work/
> Htmlized:       https://tools.ietf.org/html/draft-zheng-teas-gmpls-controller-inter-work-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-zheng-teas-gmpls-controller-inter-work
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-zheng-teas-gmpls-controller-inter-work-02
>
> Best wishes,
> Haomian
>
> -----邮件原件-----
> 发件人: Adrian Farrel [mailto:adrian@olddog.co.uk]
> 发送时间: 2018年12月5日 17:33
> 收件人: teas@ietf.org
> 抄送: draft-zheng-teas-gmpls-controller-inter-work@ietf.org
> 主题: Review and thoughts on
> draft-zheng-teas-gmpls-controller-inter-work
>
> Hi,
>
> I just had cause to read this draft, and that generated a few small comments (below). Otherwise, it seems a fairly sound document.
>
> I wonder what the plans are for this document. IIRC it was moved from CCAMP to TEAS after discussion between the chairs and considering that it had a broader TE scope. Does that mean there is a plan for this to become a TEAS WG document? Chairs?
>
> Thanks,
> Adrian
>
> ===
>
> Right hand margin alignment on the top of the front page seems to be a bit messed up.
>   
> ---
>   
> There seem to be two carriage returns at the bottom of each page.
>   
> ---
>   
> idnits shows a few issues with references
>    == Missing Reference: 'TE-TOPO' is mentioned on line 247, but not 
> defined
>   
>    == Missing Reference: 'I-D.ietf-pce-pce-initiated-lsp' is mentioned on line
>       349, but not defined
>   
>    == Missing Reference: 'PCEP-LS' is mentioned on line 397, but not 
> defined
>   
>    == Unused Reference: 'RFC8281' is defined on line 593, but no explicit
>       reference was found in the text
>   
> ---
>   
> Abstract
> I think, in order to avoid having to expand "LMP" and to make the text a little bit more brief, you might leave out the three examples in parentheses.
>   
> ---
>   
> Abstract
> You aren't allowed citations in the Abstract, so OLD is ACTN 
> controller hierarchy [RFC8453] NEW is the ACTN controller hierarchy 
> described in RFC 8453 END
>   
> ---
>   
> Abstract
> s/advantage/advantages/
>   
> ---
>   
> If you think you need the 2119 language (which you currently don't use and probably don't need), you should move "Conventions used in this document" down to become Section 2 and replace it with the new text...
>   
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
>     "OPTIONAL" in this document are to be interpreted as described in BCP
>     14 [RFC2119] [RFC8174] when, and only when, they appear in all
>     capitals, as shown here.
>   
> That requires you to make an addition to the normative references for RFC 8174.
>   
> Of course, better is to entirely remove this text and to remove the reference to 2119 from 11.1.
>   
> ---
>   
> Introduction
> Need to expand PNC, MDSC, and CNC.
> Similarly PCE.
>   
> ---
>   
> 2.1
> s/establish LSP/establish Label Switched Paths (LSPs)/ s/the same 
> network topology/the same view of the network topology/
>   
> ---
>   
> 2.2
> s/In centralized controller system/In centralized controller systems/
>   
> ---
>   
> 2.3
> s/Following figure/Figure 1/
>   
> ---
>   
> 3.
> OLD
>     In addition to setup and
>     maintain control channels,
> NEW
>     In addition to the setup and
>     maintenance of control channels,
> END
>   
> ---
>   
> 5.
> s/Once a controller learn/Once a controller learns/
>   
> ---
>   
> 6.
> s/Signaling mechanism is/Signaling mechanisms are/
>   
> ---
>   
> 6.
> You have....
>     Signaling protocols such as
>     RSVP-TE [RFC3473] and CR-LDP [RFC3472] have been extended to support
>     different interfaces in GMPLS.
>   
> I think it is time to stop mentioning CR-LDP. It is now substantially historic and has fallen so far behind RSVP-TE as to be basically unusable.
>   
> ---
>   
> 7.1
> s/method has/methods have/
>   
> ---
>   
> Obviously sections 8 and 9 need some text.
>   
> ---
>   
> I think you need to sort out the references. Currently you have them all as Normative, and that isn't right. Your guide should be "Which documents *must* you read to understand the basis of this document (normative), and which documents provide additional detail that a dedicated reader would want to read (informative)?"
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas