Re: [bmwg] Fwd: Tentative Agenda for BMWG at IETF-57

Kevin Dubray <kdubray@juniper.net> Mon, 07 July 2003 20:18 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13045 for <bmwg-archive@lists.ietf.org>; Mon, 7 Jul 2003 16:18:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZcQy-0002BH-GO; Mon, 07 Jul 2003 16:18:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZcQd-00028Z-DJ for bmwg@optimus.ietf.org; Mon, 07 Jul 2003 16:17:39 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12999 for <bmwg@ietf.org>; Mon, 7 Jul 2003 16:17:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZcQb-00028i-00 for bmwg@ietf.org; Mon, 07 Jul 2003 16:17:37 -0400
Received: from natint.juniper.net ([207.17.136.129] helo=merlot.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 19ZcQa-00028O-00 for bmwg@ietf.org; Mon, 07 Jul 2003 16:17:36 -0400
Received: from juniper.net (ssh.juniper.net [207.17.136.39]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h67KFlu94848; Mon, 7 Jul 2003 13:15:47 -0700 (PDT) (envelope-from kdubray@juniper.net)
Message-ID: <3F09D4F3.6020003@juniper.net>
Date: Mon, 07 Jul 2003 16:15:47 -0400
From: Kevin Dubray <kdubray@juniper.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 (CK-SillyDog)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Poretsky <sporetsky@avici.com>
CC: Al Morton <acmorton@att.com>, jerry.perser@spirentcom.com, bmwg@ietf.org
Subject: Re: [bmwg] Fwd: Tentative Agenda for BMWG at IETF-57
References: <5.0.2.1.2.20030707151545.034f48e0@pop.avici.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: bmwg-admin@ietf.org
Errors-To: bmwg-admin@ietf.org
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Scott Poretsky wrote:
 >
 > In Atlanta, Jerry presented "Automatic Protection Switching Benchmark
 > Terminology".  We had a 15 minute discussion.  The group concluded with
 > Kevin's agreement and affirmation that the proposed work was too broad
 > and MPLS should not be addressed in the same document as SONET APS and
 > RPR.  I am open to the MPLS Protection Methodology being covered under
 > this work item or considered a separate work item.  I guess we can
 > revisit it at the meeting.

 From the Atlanta BMWG minutes:

"Since protection could happen at various layers (or sub-layers), such as
SONET or MPLS, there was a discussion on how best to tackle this.  The
group gravitated to the idea that a single, common terminology document
with subsequent methodology documents for individual recovery
mechanisms (e.g., one for MPLS, one for APS, etc.) might be the way to go."

I believe the current effort proposes to conform to the above notions, no?
(I.e., single terminology spec; multiple, narrowly focused methodological
specifications?)


_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg