Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-flexible-grid-rsvp-te-ext-03

"Zhangxian (Xian)" <zhang.xian@huawei.com> Thu, 29 October 2015 10:14 UTC

Return-Path: <zhang.xian@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652411B2CAA for <gen-art@ietfa.amsl.com>; Thu, 29 Oct 2015 03:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.76
X-Spam-Level:
X-Spam-Status: No, score=-1.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 JVdS82HTHSg0 for <gen-art@ietfa.amsl.com>; Thu, 29 Oct 2015 03:14:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DFD61B2CAB for <gen-art@ietf.org>; Thu, 29 Oct 2015 03:14:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CDF82863; Thu, 29 Oct 2015 10:14:45 +0000 (GMT)
Received: from SZXEMA411-HUB.china.huawei.com (10.82.72.70) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 29 Oct 2015 10:14:44 +0000
Received: from SZXEMA512-MBS.china.huawei.com ([169.254.8.78]) by szxema411-hub.china.huawei.com ([10.82.72.70]) with mapi id 14.03.0235.001; Thu, 29 Oct 2015 18:14:36 +0800
From: "Zhangxian (Xian)" <zhang.xian@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-ccamp-flexible-grid-rsvp-te-ext-03
Thread-Index: AdESCmRqavGiv2M5RKmb5YRrmzKzUAAJBc8Q
Date: Thu, 29 Oct 2015 10:14:36 +0000
Message-ID: <C636AF2FA540124E9B9ACB5A6BECCE6B54AD46A4@SZXEMA512-MBS.china.huawei.com>
References: <7594FB04B1934943A5C02806D1A2204B37B9858C@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37B9858C@ESESSMB209.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.104.209]
Content-Type: multipart/alternative; boundary="_000_C636AF2FA540124E9B9ACB5A6BECCE6B54AD46A4SZXEMA512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/zp-gpI0jcRkkx3bPDv8KYszihE4>
Cc: "draft-ietf-ccamp-flexible-grid-rsvp-te-ext.all@tools.ietf.org" <draft-ietf-ccamp-flexible-grid-rsvp-te-ext.all@tools.ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-flexible-grid-rsvp-te-ext-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2015 10:14:51 -0000

Hi, Christer,

   Thank you for the detailed review. Please see my reply inline:

Cheers,
Xian

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: 2015年10月29日 17:21
To: gen-art@ietf.org
Cc: draft-ietf-ccamp-flexible-grid-rsvp-te-ext.all@tools.ietf.org
Subject: Gen-ART review of draft-ietf-ccamp-flexible-grid-rsvp-te-ext-03

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
Document:                                   draft-ietf-ccamp-flexible-grid-rsvp-te-ext-03.txt
Reviewer:                                     Christer Holmberg
Review Date:                               29 October 2015
IETF LC End Date:                       9 November 2015
IETF Telechat Date:                   N/A
Summary:                                     The document is well written, and almost ready for publication. However, I have a few editorial issue that I’d like the authors to address.
Major Issues: None
Minor Issues: None
Editorial Issues:

Q1:

‘RSVP-TE’ is expanded in the Abstract, but not in the main document. Please expand on first occurrence also in the Introduction (last paragraph).

Same comment applies to ‘LSP’.

[Xian]: Accepted.

Q2:

There is no reference for RSVP-TE.

[Xian]: Accepted. Will add.

Q3:

Would it be possible to replace the last paragraph of the Introduction with the Abstract text?
[Xian]: they are essentially the same, but the last paragraph in introduction covers the draft structure better. Unless you strongly object, I would like to keep it unchanged. OK?

Q4:

Does ‘GMPLS’ need to be expanded on first occurrence?
[Xian]: It is a pretty solid abbreviation for whoever needs to read for the technical content. But I think your suggestion is reasonable, just like we need to expand to RSVP-TE and LSP. Will do.

Q5:

There is no reference to ‘GMPLS’ in sections 1 and 3.
[Xian]: Point taken. Will add.

Q6:

The text in section 7 says:

“This section records the status of known implementations of the
              protocol defined by this specification at the time of posting of
              this Internet-Draft,…”

I am not sure whether we should use “Internet-Draft” terminology in a published RFC, and I am not sure what time “at the time of posting of this Internet-Draft” refers to.

Perhaps you could say something like:

“This section records the status of known implementations of the
              protocol defined by this specification at the time of writing the
specification,…”

[Xian]: This section will be removed when it becomes a RFC (see the editor note put at the beginning of this section in the draft). So I do not think your issue applies. I would prefer to leave it, avoiding using specification twice. OK?