Re: [CCAMP] draft-galikunze-ccamp-g-698-2-snmp-mib and draft-dharinigert-ccamp-g-698-2-lmp

Fatai Zhang <zhangfatai@huawei.com> Thu, 20 February 2014 02:37 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0937B1A063A for <ccamp@ietfa.amsl.com>; Wed, 19 Feb 2014 18:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level:
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] 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 HFiVCu3XcWiF for <ccamp@ietfa.amsl.com>; Wed, 19 Feb 2014 18:37:23 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 81EBB1A0627 for <ccamp@ietf.org>; Wed, 19 Feb 2014 18:37:22 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBH69957; Thu, 20 Feb 2014 02:37:18 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 20 Feb 2014 02:37:05 +0000
Received: from SZXEMA401-HUB.china.huawei.com (10.82.72.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 20 Feb 2014 02:37:17 +0000
Received: from SZXEMA504-MBS.china.huawei.com ([169.254.8.231]) by SZXEMA401-HUB.china.huawei.com ([10.82.72.33]) with mapi id 14.03.0158.001; Thu, 20 Feb 2014 10:37:14 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, Gert Grammel <ggrammel@juniper.net>, Lou Berger <lberger@labn.net>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: draft-galikunze-ccamp-g-698-2-snmp-mib and draft-dharinigert-ccamp-g-698-2-lmp
Thread-Index: Ac8mR6/gOMCOocD3RHmxonwohGms1gHY+yiAAAP2sAAACdFGYA==
Date: Thu, 20 Feb 2014 02:37:13 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF85CABDE6B@SZXEMA504-MBS.china.huawei.com>
References: <c3172e38521043fa91c27da92b2c49d0@BN1PR05MB041.namprd05.prod.outlook.com> <F64C10EAA68C8044B33656FA214632C80C14B0B2@MISOUT7MSGUSR9O.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C80C14B0B2@MISOUT7MSGUSR9O.ITServices.sbc.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.72.159]
Content-Type: multipart/alternative; boundary="_000_F82A4B6D50F9464B8EBA55651F541CF85CABDE6BSZXEMA504MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/3seiS2jhZXGBbzBk0WKfMIfG0cY
Subject: Re: [CCAMP] draft-galikunze-ccamp-g-698-2-snmp-mib and draft-dharinigert-ccamp-g-698-2-lmp
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: Thu, 20 Feb 2014 02:37:26 -0000

Hi Gert,

I don't think there were sufficient support (besides claim from the authors) on these drafts  from the WG (even from ITU-T SG15) because I was there for a couple of IETF meetings.

I am not going to share my technical comments here, but I would like to share the conclusion on this topic from the Q6/SG15 report in Nuremberg last October, (fortunately, our WG chair-Deborah was there, :)):

========================================================================================================================
WD06-19 contained a proposal to add a new appendix on link management protocol (LMP) to G.698.2 and to send a Liaison Statement to IETF's CCAMP WG with a list of parameters that could be exchanged via LMP. During the discussion on WD06-19 it became clear that this proposal is intended to enable operators to use different boundaries than provided by the specifications in G.698.2. There was no support for this contribution because:

*        G.698.2 is about a binary state of being compliant to an application code specification: Yes or No.

*        How to do joint engineering, in particular inside a black link, is outside the scope of G.698.2.

*        The possibilities when modifying parameter values are outside the scope of G.698.2.

*        An architectural need to perform degradation management and operating of links outside the boundaries of the specifications of G.698.2 has not yet been established by Q14/15.




Best Regards

Fatai

From: CCAMP [mailto:ccamp-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: Thursday, February 20, 2014 6:04 AM
To: Gert Grammel; Lou Berger; ccamp@ietf.org
Subject: Re: [CCAMP] draft-galikunze-ccamp-g-698-2-snmp-mib and draft-dharinigert-ccamp-g-698-2-lmp

Hi Gert,

Considering the timing, we will poll at the meeting for support and then follow up after the meeting with a poll on the list. Recommend you should not use your time slot to present information previously presented/discussed, as we will need the time to gauge the interest in the drafts.

Thanks,
Deborah


From: Gert Grammel [mailto:ggrammel@juniper.net]
Sent: Wednesday, February 19, 2014 3:01 PM
To: BRUNGARD, DEBORAH A; Lou Berger; ccamp@ietf.org<mailto:ccamp@ietf.org>
Subject: draft-galikunze-ccamp-g-698-2-snmp-mib and draft-dharinigert-ccamp-g-698-2-lmp

Hi Deborah and Lou,

the authors think that the content of  http://tools.ietf.org/html/draft-galikunze-ccamp-g-698-2-snmp-mib-06 and http://tools.ietf.org/html/draft-dharinigert-ccamp-g-698-2-lmp-06 has sufficient maturity and support in the WG. We suggest starting a poll on the mailing list so we can conclude at the IETF meeting in London.

Thanks

Gert