[CCAMP] 答复: 答复: 答复: 答复: WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09

Fatai Zhang <zhangfatai@huawei.com> Thu, 15 November 2012 02:49 UTC

Return-Path: <zhangfatai@huawei.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B387A21F8499 for <ccamp@ietfa.amsl.com>; Wed, 14 Nov 2012 18:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.315
X-Spam-Level: **
X-Spam-Status: No, score=2.315 tagged_above=-999 required=5 tests=[AWL=-0.473, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Y4FlfikFRMQ for <ccamp@ietfa.amsl.com>; Wed, 14 Nov 2012 18:49:17 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A12121F8472 for <ccamp@ietf.org>; Wed, 14 Nov 2012 18:49:12 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALN64600; Thu, 15 Nov 2012 02:49:12 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 02:48:58 +0000
Received: from SZXEML425-HUB.china.huawei.com (10.72.61.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Nov 2012 02:49:10 +0000
Received: from SZXEML552-MBX.china.huawei.com ([169.254.1.218]) by szxeml425-hub.china.huawei.com ([10.72.61.33]) with mapi id 14.01.0323.003; Thu, 15 Nov 2012 10:49:05 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: Lou Berger <lberger@labn.net>
Thread-Topic: =?gb2312?B?tPC4tDogW0NDQU1QXSC08Li0OiC08Li0OiAgV0cgTGFzdCBDYWxsIGNvbW1l?= =?gb2312?Q?nts_on_draft-ietf-ccamp-gmpls-g709-framework-09?=
Thread-Index: AQHNwngdgXb5qFrW20aw0tYhvhkP8ZfqGlxg//+LCACAAIu8oA==
Date: Thu, 15 Nov 2012 02:49:04 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF8358300B6@SZXEML552-MBX.china.huawei.com>
References: <50733BED.8090304@labn.net> <5081DCC1.60202@labn.net> <F82A4B6D50F9464B8EBA55651F541CF83582F514@SZXEML552-MBX.china.huawei.com> <50A25171.9060709@labn.net> <F82A4B6D50F9464B8EBA55651F541CF83582FB55@SZXEML552-MBX.china.huawei.com> <50A392FA.5060408@labn.net> <F64C10EAA68C8044B33656FA214632C822090E@MISOUT7MSGUSR9O.ITServices.sbc.com> <F82A4B6D50F9464B8EBA55651F541CF835830040@SZXEML552-MBX.china.huawei.com> <50A4522A.8000303@labn.net>
In-Reply-To: <50A4522A.8000303@labn.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.72.85]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: CCAMP <ccamp@ietf.org>, "draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org" <draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org>
Subject: [CCAMP] =?gb2312?b?tPC4tDogtPC4tDogILTwuLQ6ILTwuLQ6ICBXRyBMYXN0?= =?gb2312?b?IENhbGwgY29tbWVudHMgb24gZHJhZnQtaWV0Zi1jY2FtcC1nbXBscy1nNzA5?= =?gb2312?b?LWZyYW1ld29yay0wOQ==?=
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 15 Nov 2012 02:49:18 -0000

Hi Lou,

OK to use [G709-2012] and keep the file names.

By following Deborah's, my understanding is to use the same approach as RFC4328 to reference the "old" G.709, am I right?



Best Regards

Fatai


-----邮件原件-----
发件人: Lou Berger [mailto:lberger@labn.net] 
发送时间: 2012年11月15日 10:24
收件人: Fatai Zhang
抄送: BRUNGARD, DEBORAH A; CCAMP; draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org
主题: Re: 答复: [CCAMP] 答复: 答复: WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09



On 11/14/2012 8:59 PM, Fatai Zhang wrote:
> Hi Chairs,
> 
> Thanks for your comments and suggestions.
> 
> A couple of things that I want to clarify on the reference:
> 
> (1)The "new" G.709: The latest version of G.709 in force is V4, so we
> need to reflect the newest one for the new features of OTN as what
> Deborah and Huub suggested, ie., we need to use [G709-V4] to replace

how about [G709-2012] (per Deborah)?

> [G709-V3] and [G709-V3A2]. In this way, the file name of solution
> drafts (draft-ietf-ccamp-gmpls-signaling-g709v3,
> draft-ietf-ccamp-gmpls-ospf-g709v3) should be changed (ie., remove v3
> in the file name).
>
> Is that OK?

NO. Please don't try to change the file name(s). It's just a file name
and changing it will complicate the process.


> (2) The "old" G.709: We need to reference the "old" G.709 when we
> talk about the history of G.709 including data plane and control
> plane. For the ITU-T recommendations (data plane), there are a couple
> of versions (including V1=G.709/Y.1331 (02/2001), V1.1= G.709/Y.1331
> (2001) Amd. 1 (11/2001), V2=G.709/Y.1331 (03/2003) ) before RFC4328
> published in 2006. Actually, I think RFC4328 should reference V2, but
> it referenced V1 and V1.1 (v1amd1). So when we talked about the
> control plane history, RFC4328 only supports V1 and V1.1 (RFC4328 may
> not support something of V2). Note that an amd means amendment (delta
> info) and it is not a complete version of a recommendation.
> 

> This is the reason that we reused the same approach as RFC4328. Does this make sense?
> 

I'm not sure what your question is here, but please follow Deborah's
advice with respect to the old versions.

Lou
> 
> 
> 
> Best Regards
> 
> Fatai
> 
> 
> -----邮件原件-----
> 发件人: BRUNGARD, DEBORAH A [mailto:db3546@att.COM] 
> 发送时间: 2012年11月14日 22:55
> 收件人: Lou Berger; Fatai Zhang
> 抄送: CCAMP; draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org
> 主题: RE: [CCAMP] 答复: 答复: WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09
> 
> Hi,
> 
> For RFC4328, both the Recommendation and Amendment were the current references at the time. It is questionable if should do as one reference or two, but it doesn't matter, as now these have all been superseded (incorporated in) by the latest G.709 dated 02/2012. We should use that (only) as reference. Similar for G.798, we should only use the latest pub. For ITU, one only needs to reference the latest pub.
> 
> Thanks,
> Deborah
> 
> 
> -----Original Message-----
> From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of Lou Berger
> Sent: Wednesday, November 14, 2012 7:48 AM
> To: Fatai Zhang
> Cc: CCAMP; draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org
> Subject: Re: [CCAMP] 答复: 答复: WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09
> 
> 
> 
> On 11/13/2012 8:24 PM, Fatai Zhang wrote:
>> Hi Lou,
>>
>> Regarding [G709-v1] reference, there is only general reference to [G709-v1] and [G709-v1a1], ie., no specific text is referenced from some specific place of these two documents, so we reused the same approach used by [RFC4328], otherwise, [G709-v1] and [G709-v1a1] should be used together to replace the alone [G709-v1] (because it is really difficult to differentiate either [G709-v1] or [G709-v1a1] should be referenced). 
>>
>> Here is the referenced used by [RFC4328]: 
>> [ITUT-G709] ITU-T, "Interface for the Optical Transport Network (OTN)," G.709 Recommendation (and Amendment 1), February 2001 (October 2001).
>>
>> Is that acceptable for you?
>>
> 
> I don't understand how one reference can be used for two documents.  I
> suspect this slipped by the RFC editor.  I think it makes most sense to
> have one reference per document.
> 
>> In addition, the nits will be resolved in the next update.
> 
> Thanks.
> 
> Lou
> 
>>
>>
>>
>>
>> Best Regards
>>
>> Fatai
>>
>>
>> -----邮件原件-----
>> 发件人: Lou Berger [mailto:lberger@labn.net] 
>> 发送时间: 2012年11月13日 21:56
>> 收件人: Fatai Zhang; draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org
>> 抄送: CCAMP
>> 主题: Re: 答复: [CCAMP] WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09
>>
>> Fatai, Authors,
>> 	Thank you for the update.  Please see below for specific responses.
>>
>> On 11/13/2012 1:32 AM, Fatai Zhang wrote:
>>> Hi Lou and all, 
>>>
>>> A new version has been submitted with the udpates based on the comments from Lou.
>>>
>>> Please see more in-line below marked with [Fatai]. 
>>>
>>>
>>> Best Regards
>>>
>>> Fatai
>>>
>>>
>>> -----邮件原件-----
>>> 发件人: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] 代表 Lou Berger
>>> 发送时间: 2012年10月20日 7:06
>>> 收件人: CCAMP; draft-ietf-ccamp-gmpls-g709-framework@tools.ietf.org
>>> 主题: [CCAMP] WG Last Call comments on draft-ietf-ccamp-gmpls-g709-framework-09
>>>
>>> Authors,
>>> 	I have the following LC comments:
>>>
>>>
>>> General comment:
>>> - I have a comment related to the info document, that I'll cover in a
>>> separate mail on the info-model document .
>>>
>>> - I found appendix A to not be very informative and thing there are
>>> better examples in the other documents, suggest either moving one ore
>>> more to this document or drop the appendix.
>>>
>>> [Fatai] The appendix has been dropped, because we think it is better to keep the examples in the other documents. 
>>>
>>
>> Okay.  You might want to have a reference to examples in other documents
>> where appropriate.
>>
>>> The remaining comments are editorial in nature
>>>
>>> - Please verify that abbreviations are defined before being used .
>>> There are a number of these.
>>>
>>> [Fatai] Checked and updated. 
>>
>> great.
>>
>>>
>>> - Please use a consistent decimal representation (sometimes commas are
>>> used other times periods)
>>>
>>> [Fatai] Checked and commas are used.
>>
>> okay.
>>
>>>
>>> - the references [G709-v1] and [G709-v3] each actually refer to multiple
>>> documents, each documented needs to have it's own (correct) reference,
>>> i.g., [G709-v1] and [G709-v1a1]. The document text will need to be
>>> revisited to ensure the proper reference is made.
>>>
>>> [Fatai] [G709-V3A2] is introduced and referenced in the right place.
>>
>> It looks like v1 still has this issue.
>>
>>> -
>>> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-ccamp-gmpls-g709-framework-09.txt
>>> shows there are unresolved nits that need to resolved .  I'm using line
>>> numbers from this url in my subsequent comments.
>>
>> In your next update, please resolve the nits as reported in
>> http://tools.ietf.org/idnits?url=http://tools.ietf.org/id/draft-ietf-ccamp-gmpls-g709-framework-10.txt
>>
>> The rest looks good.
>>
>> Much thanks,
>> Lou
>>
>>>
>>> - Line 46: How about replace "as consented in October 2009" with "as
>>> published in 2009."
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 255: Drop "approved in 2009" the reference is sufficient
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 260: suggest the following change:
>>> OLD
>>>                 2.5Gb/s     1.25Gb/s           Nominal Bit rate
>>> NEW
>>>                 Time Slot Granularity
>>>                 2.5Gb/s     1.25Gb/s           Nominal Bit rate
>>>
>>> [Fatai] Accepted.
>>>
>>> - Lines 272-274: Please add the appropriate reference to G.709 section
>>> or table that points to where one finds the information on determining
>>> actual bit rate.
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 307: suggest changing "into the OTUk" --> "into a specific OTUk"
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 340/1: need a reference to where this is defined.
>>>
>>> [Fatai] Accepted and added.
>>>
>>> - Line 346-347: Need a reference to where this behavior is defined.
>>>
>>> [Fatai] Accepted and added.
>>>
>>> - Lines 387/388.  Isn't this sentence OBE and should be dropped?
>>>
>>> [Fatai] Accepted.
>>>
>>> - Page 11, RWA is used in a few places on this page as is OCh layer,
>>> suggest replacing all instances of RWA with OCH or "OCh layer".
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 500: what do you mean by "including OCh layer visibility."? this
>>> isn't really reflected in the solutions documents (other than as MLN).
>>>
>>> [Fatai] Deleted to avoid ambiguity. 
>>>
>>> - Line 589: replace "New label" with "A new label format"
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 636: replace "some" with "sufficient"
>>>
>>> [Fatai] Accepted.
>>>
>>> - Lines 639-641: drop lines (seems redundant with following paragraph)
>>>
>>> [Fatai] Accepted and dropped.
>>>
>>> - Line 686: your usage of "just" is a bit odd, how about replace "be
>>> just switched" with "restricted to switching"
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 688: similarly how about replace "just terminated" to "restricted
>>> to termination"
>>>
>>> [Fatai] Accepted.
>>>
>>> - lines 714-719, probably should have a reference to [rfc4201]
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 879: Replace "contrary" with "opposite" or "reverse"
>>>
>>> [Fatai] Accepted.
>>>
>>> - Line 888. I suggest adding "Although, this is not greater than the
>>> risks presented by the existing OTN control plane as defined by
>>> [RFC4203] and [RFC4328]."
>>>
>>> [Fatai] Accepted.
>>>
>>> - Lines 888-890, I suggest dropping the sentence starting with "The data
>>> plane technology..." for multiple reasons, not least of which is that
>>> the ITU-T owns the data plane so the comment is completely out of scope.
>>>
>>> [Fatai] Accepted.
>>>
>>> - Lines 1081/2: The whole document is non-normative, so just drop this
>>> sentence.
>>>
>>> [Fatai] Accepted.
>>>
>>> That's it on this document.
>>>
>>> Lou
>>>
>>> On 10/8/2012 4:47 PM, Lou Berger wrote:
>>>> This mail begins a two week working group last call on:
>>>>
>>>> http://tools.ietf.org/html/draft-ietf-ccamp-gmpls-g709-framework-09
>>>> (Informational)
>>>>
>>>> http://tools.ietf.org/html/draft-ietf-ccamp-otn-g709-info-model-04
>>>> (Informational)
>>>>
>>>> http://tools.ietf.org/html/draft-ietf-ccamp-gmpls-ospf-g709v3-03
>>>> (Standards Track)
>>>>
>>>> http://tools.ietf.org/html/draft-ietf-ccamp-gmpls-signaling-g709v3-04
>>>> (Standards Track)
>>>>
>>>> This working group last call ends on October 22.  Comments should be
>>>> sent to the CCAMP mailing list.  Please remember to include the
>>>> technical basis for any comments.
>>>>
>>>> Please note that we're still missing a few IPR statements, and look
>>>> for these to come in during the LC period.  Any forthcoming publication
>>>> request will be delayed by late IPR statements/disclosures.
>>>>
>>>> Thank you,
>>>> Lou (and Deborah)
>>>> _______________________________________________
>>>> CCAMP mailing list
>>>> CCAMP@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> CCAMP mailing list
>>> CCAMP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>
> _______________________________________________
> CCAMP mailing list
> CCAMP@ietf.org
> https://www.ietf.org/mailman/listinfo/ccamp
>