[CCAMP] 答复: [Editorial Errata Reported] RFC7139 (3924)

Fatai Zhang <zhangfatai@huawei.com> Sat, 22 March 2014 14:44 UTC

Return-Path: <zhangfatai@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 2098A1A072D for <ccamp@ietfa.amsl.com>; Sat, 22 Mar 2014 07:44:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.078
X-Spam-Level: **
X-Spam-Status: No, score=2.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id glX9JpQqcIFO for <ccamp@ietfa.amsl.com>; Sat, 22 Mar 2014 07:44:41 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) by ietfa.amsl.com (Postfix) with ESMTP id 47D0C1A06E0 for <ccamp@ietf.org>; Sat, 22 Mar 2014 07:44:40 -0700 (PDT)
Received: from (EHLO lhreml204-edg.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEV30616; Sat, 22 Mar 2014 14:44:38 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com ( by lhreml204-edg.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Sat, 22 Mar 2014 14:44:22 +0000
Received: from SZXEMA402-HUB.china.huawei.com ( by lhreml406-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Sat, 22 Mar 2014 14:44:36 +0000
Received: from SZXEMA504-MBS.china.huawei.com ([]) by SZXEMA402-HUB.china.huawei.com ([]) with mapi id 14.03.0158.001; Sat, 22 Mar 2014 22:44:30 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Thread-Topic: [Editorial Errata Reported] RFC7139 (3924)
Thread-Index: AQHPRLJnVB0Ye/fVskG9FMlt/QGJVJrsqTkAgACHZzA=
Date: Sat, 22 Mar 2014 14:44:28 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF85CADA265@SZXEMA504-MBS.china.huawei.com>
References: <20140321030515.3EF087FC387@rfc-editor.org> <0a6b01cf45dc$60228370$20678a50$@olddog.co.uk>
In-Reply-To: <0a6b01cf45dc$60228370$20678a50$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/KFo2b8Rlel81EZ56Ta5J-7uwaXk
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: [CCAMP] =?gb2312?b?tPC4tDogW0VkaXRvcmlhbCBFcnJhdGEgUmVwb3J0ZWRd?= =?gb2312?b?IFJGQzcxMzkgKDM5MjQp?=
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Mar 2014 14:44:44 -0000

Hi Adrian,

That is fine, it is up to you.

I reported this because I got a request from Pearl.

>Fatai, regarding #1, you need to submit an errata to RFC7139 and have the AD verified it before we can update the draft string to the RFC.



发件人: Adrian Farrel [mailto:adrian@olddog.co.uk] 
发送时间: 2014年3月22日 22:38
收件人: Fatai Zhang
抄送: ccamp@ietf.org
主题: RE: [Editorial Errata Reported] RFC7139 (3924)

Hi Fatai,

I'm having trouble understanding the report.

RFC 4328 shows the value 5 as "reserved (for future use)." This is the equivalent of the IANA tag "Unassigned".

RFC 7139 creates the "OTN Signal Type" registry and includes the value 5 as Unassigned.

I don't find any other mention of the value 5 in RFC 7139, so I don't understand how this value is being specially treated. In particular, I don't find any mention in the table of Signal Types in section 5.

Also, I don't understand the meaning of "Reserved (for G.709)". Does it mean that the G.709 Recommendation can make a code point allocation? Does it mean that a future update of RFC 7139 might want to request allocation of this value for a very specific purpose and so it would be bad to allocate it for something else?

And lastly, given that these are OTN signal types, and given that OTN is defined in G.709, why would this value need special reservation treatment "for G.709"?

I'm inclined to reject your Errata Report, but want to give you a chance to clarify.


> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> Sent: 21 March 2014 03:05
> To: zhangfatai@huawei.com; zhangguoying@mail.ritt.com.cn; 
> sergio.belotti@alcatel-lucent.it; daniele.ceccarelli@ericsson.com; 
> kpithewan@infinera.com; akatlas@gmail.com; adrian@olddog.co.uk; 
> lberger@labn.net; dbrungard@att.com
> Cc: zhangfatai@huawei.com; ccamp@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Editorial Errata Reported] RFC7139 (3924)
> The following errata report has been submitted for RFC7139, "GMPLS 
> Signaling Extensions for Control of Evolving G.709 Optical Transport 
> Networks".
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=7139&eid=3924
> --------------------------------------
> Type: Editorial
> Reported by: Fatai Zhang <zhangfatai@huawei.com>
> Section: 11
> Original Text
> -------------
> 5        Unassigned                            [RFC4328]
> Corrected Text
> --------------
> 5       Reserved (for G.709)                  [RFC7139]
> Notes
> -----
> (1)Unassigned->Reserved (for G.709)
> (2)[RFC4328]->[RFC7139]
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please 
> use "Reply All" to discuss whether it should be verified or rejected. 
> When a decision is reached, the verifying party (IESG) can log in to 
> change the status and edit the report, if necessary.
> --------------------------------------
> RFC7139 (draft-ietf-ccamp-gmpls-signaling-g709v3-12)
> --------------------------------------
> Title               : GMPLS Signaling Extensions for Control of Evolving G.709
> Transport Networks
> Publication Date    : March 2014
> Author(s)           : F. Zhang, Ed., G. Zhang, S. Belotti, D. Ceccarelli, K.
> Category            : PROPOSED STANDARD
> Source              : Common Control and Measurement Plane
> Area                : Routing
> Stream              : IETF
> Verifying Party     : IESG