Re: [bmwg] Out-going Liaison on draft-jacpra-bmwg-pmtest-02

"MORTON, ALFRED C (AL)" <acmorton@att.com> Mon, 14 November 2016 23:16 UTC

Return-Path: <acmorton@att.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0372D12964F for <bmwg@ietfa.amsl.com>; Mon, 14 Nov 2016 15:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 QW4yRwCQOROF for <bmwg@ietfa.amsl.com>; Mon, 14 Nov 2016 15:16:09 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD75312962F for <bmwg@ietf.org>; Mon, 14 Nov 2016 15:15:59 -0800 (PST)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id uAENFD6J003891; Mon, 14 Nov 2016 18:15:43 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049459.ppops.net-00191d01. with ESMTP id 26qn5qjskc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 14 Nov 2016 18:15:42 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id uAENFfi1013431; Mon, 14 Nov 2016 18:15:42 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id uAENFZVQ013314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 14 Nov 2016 18:15:39 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Mon, 14 Nov 2016 23:15:30 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id uAENFUN1011507; Mon, 14 Nov 2016 17:15:30 -0600
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id uAENFGsb010094; Mon, 14 Nov 2016 17:15:16 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-azure.research.att.com (Postfix) with ESMTP id 4E64CE07DB; Mon, 14 Nov 2016 18:15:12 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Mon, 14 Nov 2016 18:15:12 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Dan Romascanu <dromasca@gmail.com>
Thread-Topic: [bmwg] Out-going Liaison on draft-jacpra-bmwg-pmtest-02
Thread-Index: AdI+txd/fo3M7pxDRtmMehGTflHdTAAMIH0AAAbndEA=
Date: Mon, 14 Nov 2016 23:15:11 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF645D30@njmtexg5.research.att.com>
References: <4D7F4AD313D3FC43A053B309F97543CF645C7B@njmtexg5.research.att.com> <CAFgnS4VboRTm0M2qDc3kh23ZmbrU9ujJTXHqOwkK3Ks2TxmQsA@mail.gmail.com>
In-Reply-To: <CAFgnS4VboRTm0M2qDc3kh23ZmbrU9ujJTXHqOwkK3Ks2TxmQsA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.25.171]
Content-Type: multipart/alternative; boundary="_000_4D7F4AD313D3FC43A053B309F97543CF645D30njmtexg5researcha_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-11-14_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1031 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1611140438
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/7NHbifv7SZytQAKASZ33o4MQOh0>
Cc: "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [bmwg] Out-going Liaison on draft-jacpra-bmwg-pmtest-02
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2016 23:16:12 -0000

Hi Dan,

SG 11’s Mandate is very broad, and I understand it has
expanded in the recent WTSA-16 concluding a few weeks ago.

AFAIK, BMWG hasn’t liaised with ITU-T before, and when we
liaised with other SDOs that had a relevant testing emphasis
or project in-progress, the SDO preferred to do the work
themselves. When there was no comparable work, BMWG was
able to proceed.

So, we’ll see what they say.
Al
bmwg co-chair

From: Dan Romascanu [mailto:dromasca@gmail.com]
Sent: Monday, November 14, 2016 4:26 PM
To: MORTON, ALFRED C (AL)
Cc: bmwg@ietf.org
Subject: Re: [bmwg] Out-going Liaison on draft-jacpra-bmwg-pmtest-02

Hi Al,
Can you explain shortly what is meant by:

'In this proposal, there is an intersection between IETF benchmarking
practice and ITU-T standardization and mandates.'
BMWG defined for the last two decades or so benchmarking methodologies that referred performance metrics defined in the IETF and other industry organizations including the ITU-T. AFAIK this was considered complementary and added value work. Is this case different?
Just to be clear, I feel it's fine and even recommended to ask for review and advice from the owners of Y.1731 - this is sound communication on the technical plane. However, asking another organization about 'your preference on how to progress this work' sounds different than previous cases.
Thanks and Regards,
Dan

On Mon, Nov 14, 2016 at 10:40 PM, MORTON, ALFRED C (AL) <acmorton@att.com<mailto:acmorton@att.com>> wrote:
BMWG,

Since draft-jacpra-bmwg-pmtest-02 intends to benchmark
PM features based on ITU-T Recommendation Y.1731, it is
essential that we communicate with the relevant
ITU-T Study Groups and obtain their perspective before
proceeding further.

The draft text of the Liaison is provided below,
for BMWG comment prior to transmittal.

Please provide any comments before Nov 22, 2016.

regards,
Al
bmwg co-chair

---------------------------------------------------------------
To: ITU-T SG 15 and SG 11
TSBSG15, ITU (tsbsg15@itu.int<mailto:tsbsg15@itu.int>)
TSBSG11, ITU (tsbsg11@itu.int<mailto:tsbsg11@itu.int>)

From: IETF-BMWG
Al Morton, WG Co-Chair acmorton@att.com<mailto:acmorton@att.com>
Sarah Banks, WG Co-Chair sbanks@encrypted.net<mailto:sbanks@encrypted.net>
For Action/Comment
Deadline: March 1, 2017

Title: Proposal to Develop a Benchmarking Methodology for
ITU-T Recommendation Y.1731 OAM Performance


The purpose of this Liaison is to inform you of a new work proposal
in the Benchmarking Methodology Working Group (BMWG) of the IETF, and seek
your comments and future plans regarding the subject work area.

BMWG has been presented with a new work proposal to benchmark the
Y.1731 OAM capabilities of network devices. Please see
the Internet Draft by Sudhin Jacob and Praveen Ananthasankaran:
https://tools.ietf.org/html/draft-jacpra-bmwg-pmtest-02
In this proposal, there is an intersection between IETF benchmarking
practice and ITU-T standardization and mandates.

The Internet-Draft seeks to characterize the accuracy of performance
monitoring:
* under various traffic conditions,
* during routing engine fail-over (High Availability),
* during multiple OAM test sessions to characterize the scale/capacity, and
* during long test intervals (Soak tests).

This Internet Draft is at an early stage, so considerable review
and development would be necessary, as with all work items.

The charter of BMWG strictly limits our work to laboratory characterization.
Therefore, live network performance testing, manageability, MIB module
development, and other operational/functional testing are beyond our scope.
https://datatracker.ietf.org/wg/bmwg/charter/

We recognize that ITU-T SG 15 is the maintainer of Rec. Y.1731, and that
compliance and interoperability specifications are the mandate of SG 11.
Therefore, prior to considering this work proposal further,
we seek your respective comments on:
  - whether you see this topic as valuable to the Industry
  - whether your experience and knowledge of Y.1731 implementations
    is essential to complete this work with the necessary quality
  - whether there is overlapping work in ITU-T, planned or in-progress
  - the proposal details, as currently described, and
  - your preference on how to progress this work.

Replies received prior to our March 2017 meeting will be most appreciated.

-------------------------------------------------------------------------

_______________________________________________
bmwg mailing list
bmwg@ietf.org<mailto:bmwg@ietf.org>
https://www.ietf.org/mailman/listinfo/bmwg