IETF Logo Mail Archive

RE: הנדון: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC

Malcolm.BETTS@zte.com.cn Wed, 21 March 2012 20:35 UTC

Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638EA21E812A for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.218
X-Spam-Level:
X-Spam-Status: No, score=-100.218 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_WIN1255=0.647, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ot0611mGcvun for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:35:00 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3A69021E8102 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:35:00 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 1228011182326; Thu, 22 Mar 2012 04:00:52 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 84000.1346409004; Thu, 22 Mar 2012 04:34:53 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2LKYsdQ067183; Thu, 22 Mar 2012 04:34:54 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C016F6EE0@DEMUEXC013.nsn-intra.net>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net> <E4873516F3FC7547BCFE792C7D94039C016F6EE0@DEMUEXC013.nsn-intra.net>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Subject: RE: הנדון: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
MIME-Version: 1.0
X-KeepSent: 64E69521:55EAB63F-852579C8:006EE6A1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OF64E69521.55EAB63F-ON852579C8.006EE6A1-852579C8.00710D12@zte.com.cn>
From: Malcolm.BETTS@zte.com.cn
Date: Wed, 21 Mar 2012 15:34:46 -0500
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-22 04:34:53, Serialize complete at 2012-03-22 04:34:53
Content-Type: multipart/alternative; boundary="=_alternative 00710D11852579C8_="
X-MAIL: mse01.zte.com.cn q2LKYsdQ067183
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 20:35:01 -0000

Nurit,

Section 2 “Scope of the Ethernet based OAM ACH Type” contains the 
following text:

"The code point allocated by this document is intended to be used only for 
Ethernet based OAM messages, defined in the ITU-T Recommendation 
[G.8113.1], carried in the G-ACh . These Ethernet based OAM messages and 
procedures, address the OAM functional requirements defined in [RFC5860]. 
Other message types should not be carried behind this code point."

The restrictions on the future use of the code point could be made more 
explicit by modifying the text as follows:

The code point allocated by this document should only be used for Ethernet 
based OAM messages, defined in the ITU-T Recommendation [G.8113.1], 
carried in the G-ACh. The messages and procedures carried behind this code 
point, are restricted to only those that the address the OAM functional 
requirements defined in [RFC5860]. Other message types should not be 
carried behind this code point.

I hope that this addresses your concern.

Regards,

Malcolm




"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com> 
14/03/2012 06:43 AM

To
"Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, 
"Andrew G. Malis" <agmalis@gmail.com>, "ext Ross Callon" 
<rcallon@juniper.net>, <malcolm.betts@zte.com.cn>
cc
<ietf@ietf.org>
Subject
RE: הנדון: RE: Last 
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof   an 
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to 
Informational RFC






Malcolm,
As mentioned before, I cannot support the publication of the current 
version of draft-betts...it must be revised first to address the concerns 
I and others raised on the list. 
Maybe you could clarify how the text in your draft can be improved to 
protect the use of the code point from future extensions beyond the 
purpose of the code point allocation?
Best regards,
Nurit 

________________________________


>-------------------------snip
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email