
From acmorton@att.com  Wed May  2 08:02:18 2012
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 13AD221F861C for <bmwg@ietfa.amsl.com>; Wed,  2 May 2012 08:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.322
X-Spam-Level: 
X-Spam-Status: No, score=-102.322 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, 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 6m87iIoG742Y for <bmwg@ietfa.amsl.com>; Wed,  2 May 2012 08:02:17 -0700 (PDT)
Received: from nbfkord-smmo08.seg.att.com (nbfkord-smmo08.seg.att.com [209.65.160.95]) by ietfa.amsl.com (Postfix) with ESMTP id D950A21F84BF for <bmwg@ietf.org>; Wed,  2 May 2012 08:02:16 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo08.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 87c41af4.0.1209556.00-437.3317980.nbfkord-smmo08.seg.att.com (envelope-from <acmorton@att.com>);  Wed, 02 May 2012 15:02:16 +0000 (UTC)
X-MXL-Hash: 4fa14c782fc8aada-d0d0b3f24e741c4fc701071c1cbfdad272f9d3b9
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q42F2Cq3023037 for <bmwg@ietf.org>; Wed, 2 May 2012 11:02:13 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q42F24XW022910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Wed, 2 May 2012 11:02:05 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Wed, 2 May 2012 11:01:53 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q42F1qYJ017402 for <bmwg@ietf.org>; Wed, 2 May 2012 11:01:53 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q42F1h2V013296 for <bmwg@ietf.org>; Wed, 2 May 2012 11:01:43 -0400
Message-Id: <201205021501.q42F1h2V013296@alpd052.aldc.att.com>
Received: from acmt.att.com (dn135-16-251-71.dhcpn.ugn.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120502145826gw10060leve>; Wed, 2 May 2012 14:58:26 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 02 May 2012 11:02:55 -0400
To: bmwg@ietf.org
From: Al Morton <acmorton@att.com>
In-Reply-To: <201204191847.q3JIlbeR015174@alpd052.aldc.att.com>
References: <201204191847.q3JIlbeR015174@alpd052.aldc.att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=W2hlYBC8_kYA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=qc-SjYU91_GNd1lLm6AA:9 a=]
X-AnalysisOut: [Ptj6VjYAVVQoAYBoXI4A:7 a=CjuIK1q_8ugA:10]
Subject: Re: [bmwg] WGLC on SIP Benchmarking Drafts (04)
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 02 May 2012 15:02:18 -0000

At 02:48 PM 4/19/2012, Al Morton wrote:
>A WG Last Call period for the Internet-Drafts on SIP Device
>Benchmarking:
>
>http://www.ietf.org/id/draft-ietf-bmwg-sip-bench-term-04.txt
>
>http://www.ietf.org/id/draft-ietf-bmwg-sip-bench-meth-04.txt
>
>will be open from 19 April 2012 through 18 May 2012.


Below are the comments I've collected on these versions.
Al
(as a participant)

-=-=-=-=-=-=-=-=-=-=-

There are a few minor inconsistencies between the Abstract and the Scope
in the term draft. Some may be sorted out by using clear terminology.

Abstract (3rd sent.)
...                                      The performance benchmark
    metrics are obtained for the SIP control plane and media plane.
Scope
...
     o  Control Signaling in presence of Media
       *  The media performance is not benchmarked in this work item.

Also,
Abstract
... It is critical to provide test setup parameters and a
    methodology document for SIP performance benchmarking because SIP
    allows a wide range of configuration and operational conditions that
    can influence performance benchmark measurements.
Scope
    The scope of this work item is summarized as follows:
    o  This terminology document describes SIP signaling (control- plane)
       performance benchmarks for black-box measurements of SIP
       networking devices.  Stress and debug scenarios are not addressed
       in this work item.   ^^^^^^
Later in the Scope
    o  SIP Overload [I-D.ietf-soc-overload-design] is within the scope of
       this work item.  We test to failure and then can continue to
       observe and record the behavior of the system after failures are
       recorded.
 >>> Isn't Overload a form of Stress testing?

-=-=-=-=-=-=-=-=-=-=-=-

Section 3.1.1

       Sessions will be represented as a vector array with three
       components, as follows:
       session->
       session[x].sig, the signaling component
       session[x].medc, the media control component (e.g.  RTCP)
       session[x].med[y], an array of associated media streams (e.g.

Question: Why is media control not indicated as a value on the z-axis?
       session[x].medc[z], the media control component (e.g.  RTCP)

If medc is a only a function of session[x], then is the 3rd axis necessary?

-=-=-=-=-=-=-=-=-=-=-

Section 3.1.5 Overload

    Definition:
       Overload is defined as the state where a SIP server does not have
       sufficient resources to process all incoming SIP messages
       [I-D.ietf-soc-overload-design].  The distinction between an
       overload condition and other failure scenarios is outside the
       scope of this document which is blackbox testing.

Does the last sentence really mean this?

Achieving Overload state does not require a level of SIP message load
sufficient to cause failure. Testing with under failure conditions is
beyond the scope of this document.

And, it would be good to say whether Overload state can be considered
part of Stress conditions (or remove the word Stress from the Scope?).


Also:

    Issues:
       The issue of overload in SIP networks is currently a topic of
       discussion in the SIPPING WG.  The normal response to an overload
       stimulus -- sending a 503 response -- is considered inadequate and
       new response codes and behaviors may be specified in the future.
       From the perspective of this document, all these responses will be
       considered to be failures.  There is thus no dependency between
       this document and the ongoing work on the treatment of overload
       failure.

There has been some progress on the overload topic, and an RFC published,
so this section may need to be updated. In general, IETF considers
working groups to be ephemeral, and therefore not mentioned by name
in RFCs.

-=-=-=-=-=-=-=-=-=-=-

3.1.7.  Established Session

    Definition:
       A SIP session for which the EA acting as the UE/UA has received a
       200 OK message from the DUT/SUT.

As a practical matter, how long does one wait for 200 OK?
Is there a standard time-out to cite here?

-=-=-=-=-=-=-=-=-=-=-

3.1.9.  Non-INVITE-initiated Session (NS)

    Definition:
       A session that is created by an exchange of messages in the
       Signaling Plane that does not include an initial SIP INVITE
       message.

s/an exchange/any exchange/  ??

-=-=-=-=-=-=-=-=-=-=-=-


3.4.4.  Session Overload Capacity

    Definition:
       The maximum number of Established Sessions that can exist
       simultaneously on the DUT/SUT until it stops responding to Session
       Attempts.

Again, the waiting time for 200 OK figures in this benchmark,
and any other that relies on the Established Session definition.

-=-=-=-=-=-=-=-=-=-=-=-=-

5.  Security Considerations

    Documents of this type do not directly affect the security of
    Internet or corporate networks as long as benchmarking is not
    performed on devices or systems connected to production networks.
    Security threats and how to counter these in SIP and the media layer
    is discussed in RFC3261 [RFC3261], RFC 3550 [RFC3550], RFC3711
    [RFC3711] and various other drafts.  This document attempts to
    formalize a set of common terminology for benchmarking SIP networks.
add ... constructed in isolated test environments (not production networks).

(same comment for methodology draft)

These considerations below seem to apply to another draft, remove?

    Packets with unintended and/or unauthorized DSCP or IP precedence
    values may present security issues.  Determining the security
    consequences of such packets is out of scope for this document.




From acmorton@att.com  Thu May  3 06:33:01 2012
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 56BA121F8495 for <bmwg@ietfa.amsl.com>; Thu,  3 May 2012 06:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.287
X-Spam-Level: 
X-Spam-Status: No, score=-104.287 tagged_above=-999 required=5 tests=[AWL=1.509, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, 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 jt9A1S3iVmt6 for <bmwg@ietfa.amsl.com>; Thu,  3 May 2012 06:33:00 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 9B30321F848F for <bmwg@ietf.org>; Thu,  3 May 2012 06:33:00 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id c0982af4.0.1076265.00-353.2973284.nbfkord-smmo03.seg.att.com (envelope-from <acmorton@att.com>);  Thu, 03 May 2012 13:33:00 +0000 (UTC)
X-MXL-Hash: 4fa2890c3ffd4b64-36ab5d3fb1881bbff13bcc9f576466657ec9720f
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q43DX0Jc028896 for <bmwg@ietf.org>; Thu, 3 May 2012 09:33:00 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q43DWsJF028872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <bmwg@ietf.org>; Thu, 3 May 2012 09:32:54 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <bmwg@ietf.org>; Thu, 3 May 2012 09:32:37 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q43DWbcg025279 for <bmwg@ietf.org>; Thu, 3 May 2012 09:32:37 -0400
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q43DWUXX025114 for <bmwg@ietf.org>; Thu, 3 May 2012 09:32:31 -0400
Message-Id: <201205031332.q43DWUXX025114@alpd052.aldc.att.com>
Received: from acmt.att.com (dn135-16-251-71.dhcpn.ugn.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20120503132913gw10060lhbe>; Thu, 3 May 2012 13:29:13 +0000
X-Originating-IP: [135.16.251.71]
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 03 May 2012 09:33:42 -0400
To: "Aamer Akhter (aakhter)" <aakhter@cisco.com>, <davids@iit.edu>
From: Al Morton <acmorton@att.com>
In-Reply-To: <7F298ACC76CC154F832B6D02852D169F078D5B4F@XMB-RCD-101.cisco .com>
References: <CB8420E9.17A24%davids@iit.edu> <4F717406.4050902@cisco.com> <7F298ACC76CC154F832B6D02852D169F078D5B4F@XMB-RCD-101.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <acmorton@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=dit6Jc5sqrAA:10 a=Dzs50GiFyKYA:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=nws6cERoKuFFMsnpILcA:9 a=CjuIK1q_8ugA:10]
Cc: bmwg@ietf.org
Subject: Re: [bmwg] SIP Benchmarking methodology and terminology - version 4 updates
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 May 2012 13:33:01 -0000

These comments will be considered under the current WGLC.
Al
bmwg chair

At 05:28 AM 3/27/2012, Aamer Akhter (aakhter) wrote:
>Please find my comments for draft-ietf-bmwg-sip-bench-*-04 below:
>
>General comment:
>
>1. Can we please add a statement with regards to the relationship
>between this work and rfc6076? (something more deeper than BMWG is in
>the lab).
>
>2. Have anybody checked to see if the metrics out of rfc6076 and this
>work are comparable?
>
>3. "However, benchmarking SIP
>       presence is not a part of this work item.". Is there a reason for
>this. Presence would be one of the more interesting cases to understand.
>
>
>4. "Only session establishment is considered for the performance
>       benchmarks.  Session disconnect is not considered in the scope of
>       this work item." I would think that given connectivity churn
>(links going up and down, power outages, etc), both establishment as
>well as disconnect are interest items. Consider the cleanup work needed
>after a disconnect... some of this might be a high workload than simply
>maintaining a connection.
>
>5. term-04, figure 12 seems misformatted, or it needs a better
>explanation of how to read it...
>
>6. For the case of video conferencing the SDP can get quite large. I am
>wondering if this (SDP size) is an interesting axis to explore.
>
>


From Rajiv.Papneja@huawei.com  Tue May 22 11:30:32 2012
Return-Path: <Rajiv.Papneja@huawei.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 F408121F85DF; Tue, 22 May 2012 11:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.509
X-Spam-Level: 
X-Spam-Status: No, score=-4.509 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
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 GsTtTbQ9+Vtq; Tue, 22 May 2012 11:30:26 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 02E2121F85D4; Tue, 22 May 2012 11:30:25 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGD85816; Tue, 22 May 2012 14:30:25 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 22 May 2012 11:28:06 -0700
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.75]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Tue, 22 May 2012 11:28:01 -0700
From: Rajiv Papneja <Rajiv.Papneja@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: [Gen-art] Review: draft-ietf-bmwg-protection-meth-09.txt
Thread-Index: AQHM/j0YcQICZ4zzmkasgx8iN2o5AZbWR6dw
Date: Tue, 22 May 2012 18:28:00 +0000
Message-ID: <52B0D42F4BADB144B850705C4549F6EA017F1B97@dfweml511-mbs.china.huawei.com>
References: <4F5973CE.309@nostrum.com> <4F5A784D.4020401@joelhalpern.com>
In-Reply-To: <4F5A784D.4020401@joelhalpern.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.132.180]
Content-Type: multipart/alternative; boundary="_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 23 May 2012 08:17:07 -0700
Cc: "draft-ietf-bmwg-protection-meth.all@tools.ietf.org" <draft-ietf-bmwg-protection-meth.all@tools.ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [bmwg] [Gen-art] Review: draft-ietf-bmwg-protection-meth-09.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 22 May 2012 18:30:32 -0000

--_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Joel,



Thank you so much for your review and comments. Please see our responses in=
line. We will posting the updated draft soon.



Regards,

-Rajiv



-----Original Message-----

From: Joel M. Halpern [mailto:jmh@joelhalpern.com]

Sent: Friday, March 09, 2012 4:38 PM

To: gen-art@ietf.org

Cc: bmwg@ietf.org; draft-ietf-bmwg-protection-meth.all@tools.ietf.org

Subject: [Gen-art] Review: draft-ietf-bmwg-protection-meth-09.txt



I am the assigned Gen-ART reviewer for this draft. For background on

Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.



Please resolve these comments along with any other Last Call comments

you may receive.



Document: draft-ietf-bmwg-protection-meth-09.txt

     Methodology for benchmarking MPLS protection mechanisms

Reviewer: Joel M. Halpern

Review Date: 9-March-2012

IETF LC End Date: 20-March-2012

IESG Telechat date: N/A



Summary: This document is almost ready for publication as an

Informational RFC.



Major issues:

     I find a definitions section (Section 3)that says

"This document also uses existing terminology defined in other BMWG work."

and follows this with examples, but neither a complete list of terms nor

a complete list of documents, to be an unclear approach.  If the reader

finds terms they do not know, they have no good indication as to what

document(s) they should read to repair the gap.



response> Addressed this by removing the examples, and adding the reference=
s as following:

The last line in the section 3 now read as -



"This document also uses existing terminology defined in other BMWG

   Work [Br91], [Ma98], [Po06]"

****************



    The description of the General Reference Topology (section 4) seems

unclear to me.  The text starts out discussing, and the diagram

explicitly shows, a Traffic Generator and a Traffic Analyzer.  In the

diagram these are two disparate devices, connected to routers R1 and R5

respectively.  So far, so good.  However, the text then talks about

"the Tester" as being made up of the Traffic generator and the Traffic

Analyzer", and describes "the Tester" as being directly connected to the

Device Under Test.  It is exceedingly unclear whether this is supposed

to mean that the full collection of routers R1-R6 are the device under

test, or whether R1, R5, or some other specific router is the device

under test.



Response>

Current : A Tester is directly connected to the DUT.



New text:  A Tester is connected to the test network and depending upon the=
 test case, the DUT may vary.

***************



     Could an effort be made to reword section 5.7?  First it says "one

or more traffic streams".  Then it says "16 flows".  Then it talks about

traffic spreading across some set of prefixes.  And the description of

the reason for not doing round-robin across the prefixes leaves me even

more confused about what one actually should set up.





Response>

Current: At least 16 flows should be used, and more if possible.

New text: For better accuracy, one may even consider provisioning 16 flows,=
 or

      more if possible.



Current: It is suggested that there be one or more traffic streams as long =
as

   there is a steady and constant rate of flow for all the streams.



New text: It is suggested that there be three or more traffic streams as lo=
ng as

   there is a steady and constant rate of flow for all the streams.



***********

     Section 5.8 describing the capabilities of "the Tester" seems to

contradict section 4, where "the Tester is comprised of" the Traffic

generator and the Traffic Analyzer.  The capabilities listed in section

5.8 go well beyond that.





Response>



Current: The Tester is comprised of a Traffic Generator (TG) & Test Analyze=
r (TA)



New : The Tester is comprised of a Traffic Generator (TG), Test Analyzer (T=
A) and an Emulator

***********



     The 8 scenarios shown in section 6 all have Mid-Point PLRs as far

as I can tell.  Section 7 says that the test it describes can be applied

to all the 8 cases from section 6.  But then it carefully describes

cases of Headend, Mid-Point, and Egress PLR.  But no examples of the

first or third have been shown.  Thus, I do not see, for example, as

described in section 7.1. one can select a scenario from section 6, and

then establish a headend PLR.



Response>

Added the following in section 6

  UR - Upstream router, MID PLR, HE PLR



Updated the topologies accordingly - for R1 added UR in all setups, for R2 =
modified the current description to MID PLR, HE PLR



************



    This reviewer would like to verify that the test procedures

described produce a meaningful value for items like Failover Packet Loss

and Failover Time.  Is there a specific reference for these, since the

actual calculations are not described here?



     Finding the definition of the Failover Time calculation methods

hidden in the reporting format (section 8) was quite surprising.  Given

that these are important definitions for the meaning fo the tests, they

should occur before the test descriptions, not in the reporting format.





Response> We agree to move the failover time measurements sections from the=
 reporting section to section 5.9 -



Text remains the same.



********************



Minor issues:

     As noted by id-nits, section 3 references TERM-ID as a document

defining terminology, but there is no such ID in the list of references.

  And why do the section headers for 5.1, 5.2, and 5.6 also have

"[TERM-ID]"?  Note that even if those section headers are defined terms,

it is stylistically unusual to put the reference into the section header.

(It almost looks like "TERM-ID" was a marker for things which still

needed a proper reference.)





Response> s/[Term-ID]/RFC6414



*********************



     In section 5.1 a set of example failure events is listed.  It is

unclear whether this list is the ones to be tested for, or just "some"

events.  In addition, it is unclear why there is inconsistency in the

coverage of the descriptions of the failures. The three different

monitoring methods are mentioned explicitly with the Interface Shutdown

failures, but are not even mentioned for the other failures.  And then

while most of the failures list local or remote side, the last two

failures do not indicate a side.  Why?



Response> Clarified the significance of mentioning of failover events. Adde=
d remote and local side applicability on Sub-interface failure and Parent i=
nterface failure.



*************************************





     Some of the abbreviations in section 6 are unclear.  For example,

since there is no real provider it is not clear which router(s) are

meant by PE as distinct from P routers.  Also, while I familiar with

Layer3 VPN, I am not familiar with the usage"Layer2 VC".  Further given

taht VPNs have different label usages, I suspect that both "Layer3 VPN"

and "Layer2 VC" are insufficiently specific to match to a specific size

label stack.





     As an example of the above confusion, in the figure in section

6.1.2, the number of labels  in the Layer3VPN from the PE to the P

router is described as going from 2 to 3 upon failure.  The PE->P link

in the diagram is R1->R2, which is upstream of the failure.  So the

number of labels on that link won't change.  The number of labels on the

R6->R3 P->PE link (assuming I have properly guessed what PE is) does go

from 2 to 3.  But the lines refer simply to PE-P.



Response> Following changes have been made



1.    Added a relationship between the general reference topology and indiv=
idual test setups. Suggested that the individual test setups are sub-set of=
 a large topology

2.    Removed TA/TG

3.    Added notes for purposes clarifying the roles of the routers wrt to P=
/PE -



Following template used for all the figures-

               +-------+  +--------+    +--------+

               |  R1   |  |   R2   | PRI|   R3   |

               |  UR/HE|--|  HE/MID|----| MP/TE  |

               |       |  |  PLR   |----|        |

               +-------+  +--------+ BKP+--------+



                             Figure 2.



          Traffic            Num of Labels   Num of labels

                             before failure  after failure

          IP TRAFFIC (P-P)         0             0

          Layer3 VPN (PE-PE)       1             1

          Layer3 VPN (PE-P)        2             2

          Layer2 VC (PE-PE)        1             1

          Layer2 VC (PE-P)         2             2

    Mid-point LSPs           0             0





Note: Please note the following:

For P-P case, R2 and R3 acts as P routers.

For PE-PE case, R2 acts as PE and R3 is acts as a remote PE

   For PE-P case, R2 acts as a PE router, R3 acts as a P router and R5 acts=
 as

remote PE router (Please refer figure 1 for complete setup)

For Mid-point case, R1, R2 and R3 acts as shown in figure - HE, Midpoint/PL=
R

and TE respectively.





***********************************



     Similarly, while I suspect that the numbers are accurate, it is

very hard to map the pre-failure label counts to the diagrams in a way

that explains the difference between the numbers in section 6.1.1/6.1.2

and  6.1.3 and onward.  Assuming PE-PE traffic is HE-TE traffic, then

the internal topology should not affect the label count on that.  So you

probably mean something else.  But I don't know what.



     It is unclear what section 7 means by "Select an overlay technology

(e.g. IGP, VPN, or VC)."  Please clarify.



Response> Clarified Section 7.1.1, step B



New text - Select or enable IP, Layer 3 VPN or Layer 2 VPN services with th=
e DUT as the headend PLR



Updated this as necessary



For section 7.1.2 - test setup, "B" is not applicable - removed.



**********



     Why is section 7.1.3 (determining tailend performance) included in

the document, when no test cases include tailend failure?



Response> Removed 7.1.3



************



     Is it an issue that the timestamp based  method for determining the

failover time will, on average, overestimate the failure time by on

inter-packet interval?  (Based on assuming that on average the failure

and recovery are each uniformly distributed across the inter-packet

interval.)



RESPONSE> We suggest other two measurement methods, so it is up the user to=
 have a preference.



***********





Nits/editorial comments:

     Section 7.1.2 item A refers to 9 scenarios from section 6. There

are only 8.



RESPONSE>  Fixed



*********

     Section 7.4 decides to leave out the nubmer of scenarios from

section 6, leading to a surprising, but otherwise probably meaningless,

difference in wording.



RESPONSE>  Fixed

**************

--_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hello Joel,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thank you so much for your review and comments. P=
lease see our responses inline. We will posting the updated draft soon.<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Regards,<o:p></o:p></p>
<p class=3D"MsoPlainText">-Rajiv<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">-----Original Message-----<o:p></o:p></p>
<p class=3D"MsoPlainText">From: Joel M. Halpern [mailto:jmh@joelhalpern.com=
] <o:p></o:p></p>
<p class=3D"MsoPlainText">Sent: Friday, March 09, 2012 4:38 PM<o:p></o:p></=
p>
<p class=3D"MsoPlainText">To: gen-art@ietf.org<o:p></o:p></p>
<p class=3D"MsoPlainText">Cc: bmwg@ietf.org; draft-ietf-bmwg-protection-met=
h.all@tools.ietf.org<o:p></o:p></p>
<p class=3D"MsoPlainText">Subject: [Gen-art] Review: draft-ietf-bmwg-protec=
tion-meth-09.txt<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. For background on
<o:p></o:p></p>
<p class=3D"MsoPlainText">Gen-ART, please see the FAQ at <o:p></o:p></p>
<p class=3D"MsoPlainText">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki=
/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Please resolve these comments along with any othe=
r Last Call comments
<o:p></o:p></p>
<p class=3D"MsoPlainText">you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-bmwg-protection-meth-09.txt<=
o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Methodology for benchmar=
king MPLS protection mechanisms<o:p></o:p></p>
<p class=3D"MsoPlainText">Reviewer: Joel M. Halpern<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 9-March-2012<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 20-March-2012<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG Telechat date: N/A<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: This document is almost ready for public=
ation as an
<o:p></o:p></p>
<p class=3D"MsoPlainText">Informational RFC.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; I find a definitions sec=
tion (Section 3)that says<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;This document also uses existing terminolog=
y defined in other BMWG work.&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">and follows this with examples, but neither a com=
plete list of terms nor
<o:p></o:p></p>
<p class=3D"MsoPlainText">a complete list of documents, to be an unclear ap=
proach.&nbsp; If the reader
<o:p></o:p></p>
<p class=3D"MsoPlainText">finds terms they do not know, they have no good i=
ndication as to what
<o:p></o:p></p>
<p class=3D"MsoPlainText">document(s) they should read to repair the gap.<o=
:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">response&gt; Addressed this by removing the examp=
les, and adding the references as following:<o:p></o:p></p>
<p class=3D"MsoPlainText">The last line in the section 3 now read as - <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&quot;This document also uses existing terminolog=
y defined in other BMWG<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; Work [Br91], [Ma98], [Po06]&quot;<o:=
p></o:p></p>
<p class=3D"MsoPlainText">****************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp; The description of the General=
 Reference Topology (section 4) seems
<o:p></o:p></p>
<p class=3D"MsoPlainText">unclear to me.&nbsp; The text starts out discussi=
ng, and the diagram
<o:p></o:p></p>
<p class=3D"MsoPlainText">explicitly shows, a Traffic Generator and a Traff=
ic Analyzer.&nbsp; In the
<o:p></o:p></p>
<p class=3D"MsoPlainText">diagram these are two disparate devices, connecte=
d to routers R1 and R5
<o:p></o:p></p>
<p class=3D"MsoPlainText">respectively.&nbsp; So far, so good.&nbsp; Howeve=
r, the text then talks about
<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;the Tester&quot; as being made up of the Tr=
affic generator and the Traffic
<o:p></o:p></p>
<p class=3D"MsoPlainText">Analyzer&quot;, and describes &quot;the Tester&qu=
ot; as being directly connected to the
<o:p></o:p></p>
<p class=3D"MsoPlainText">Device Under Test.&nbsp; It is exceedingly unclea=
r whether this is supposed
<o:p></o:p></p>
<p class=3D"MsoPlainText">to mean that the full collection of routers R1-R6=
 are the device under
<o:p></o:p></p>
<p class=3D"MsoPlainText">test, or whether R1, R5, or some other specific r=
outer is the device
<o:p></o:p></p>
<p class=3D"MsoPlainText">under test.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Current : A Tester is directly connected to the D=
UT.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text:&nbsp; A Tester is connected to the test=
 network and depending upon the test case, the DUT may vary.<o:p></o:p></p>
<p class=3D"MsoPlainText">***************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Could an effort be made =
to reword section 5.7?&nbsp; First it says &quot;one
<o:p></o:p></p>
<p class=3D"MsoPlainText">or more traffic streams&quot;.&nbsp; Then it says=
 &quot;16 flows&quot;.&nbsp; Then it talks about
<o:p></o:p></p>
<p class=3D"MsoPlainText">traffic spreading across some set of prefixes.&nb=
sp; And the description of
<o:p></o:p></p>
<p class=3D"MsoPlainText">the reason for not doing round-robin across the p=
refixes leaves me even
<o:p></o:p></p>
<p class=3D"MsoPlainText">more confused about what one actually should set =
up.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Current: At least 16 flows should be used, and mo=
re if possible.<o:p></o:p></p>
<p class=3D"MsoPlainText">New text: For better accuracy, one may even consi=
der provisioning 16 flows, or
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; more if possible.<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Current: It is suggested that there be one or mor=
e traffic streams as long as<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; there is a steady and constant rate =
of flow for all the streams.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text: It is suggested that there be three or =
more traffic streams as long as<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; there is a steady and constant rate =
of flow for all the streams.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 5.8 describing t=
he capabilities of &quot;the Tester&quot; seems to
<o:p></o:p></p>
<p class=3D"MsoPlainText">contradict section 4, where &quot;the Tester is c=
omprised of&quot; the Traffic
<o:p></o:p></p>
<p class=3D"MsoPlainText">generator and the Traffic Analyzer.&nbsp; The cap=
abilities listed in section
<o:p></o:p></p>
<p class=3D"MsoPlainText">5.8 go well beyond that.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Current: The Tester is comprised of a Traffic Gen=
erator (TG) &amp; Test Analyzer (TA)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New : The Tester is comprised of a Traffic Genera=
tor (TG), Test Analyzer (TA) and an Emulator<o:p></o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; The 8 scenarios shown in=
 section 6 all have Mid-Point PLRs as far
<o:p></o:p></p>
<p class=3D"MsoPlainText">as I can tell.&nbsp; Section 7 says that the test=
 it describes can be applied
<o:p></o:p></p>
<p class=3D"MsoPlainText">to all the 8 cases from section 6.&nbsp; But then=
 it carefully describes
<o:p></o:p></p>
<p class=3D"MsoPlainText">cases of Headend, Mid-Point, and Egress PLR.&nbsp=
; But no examples of the
<o:p></o:p></p>
<p class=3D"MsoPlainText">first or third have been shown.&nbsp; Thus, I do =
not see, for example, as
<o:p></o:p></p>
<p class=3D"MsoPlainText">described in section 7.1. one can select a scenar=
io from section 6, and
<o:p></o:p></p>
<p class=3D"MsoPlainText">then establish a headend PLR.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">Added the following in section 6<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; UR - Upstream router, MID PLR, HE PLR <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Updated the topologies accordingly - for R1 added=
 UR in all setups, for R2 modified the current description to MID PLR, HE P=
LR<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp; This reviewer would like to ve=
rify that the test procedures
<o:p></o:p></p>
<p class=3D"MsoPlainText">described produce a meaningful value for items li=
ke Failover Packet Loss
<o:p></o:p></p>
<p class=3D"MsoPlainText">and Failover Time.&nbsp; Is there a specific refe=
rence for these, since the
<o:p></o:p></p>
<p class=3D"MsoPlainText">actual calculations are not described here?<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Finding the definition o=
f the Failover Time calculation methods
<o:p></o:p></p>
<p class=3D"MsoPlainText">hidden in the reporting format (section 8) was qu=
ite surprising.&nbsp; Given
<o:p></o:p></p>
<p class=3D"MsoPlainText">that these are important definitions for the mean=
ing fo the tests, they
<o:p></o:p></p>
<p class=3D"MsoPlainText">should occur before the test descriptions, not in=
 the reporting format.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; We agree to move the failover time m=
easurements sections from the reporting section to section 5.9 &#8211;
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Text remains the same.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">********************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; As noted by id-nits, sec=
tion 3 references TERM-ID as a document
<o:p></o:p></p>
<p class=3D"MsoPlainText">defining terminology, but there is no such ID in =
the list of references.
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;And why do the section headers for 5.=
1, 5.2, and 5.6 also have
<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;[TERM-ID]&quot;?&nbsp; Note that even if th=
ose section headers are defined terms,
<o:p></o:p></p>
<p class=3D"MsoPlainText">it is stylistically unusual to put the reference =
into the section header.<o:p></o:p></p>
<p class=3D"MsoPlainText">(It almost looks like &quot;TERM-ID&quot; was a m=
arker for things which still
<o:p></o:p></p>
<p class=3D"MsoPlainText">needed a proper reference.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; s/[Term-ID]/RFC6414<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">*********************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; In section 5.1 a set of =
example failure events is listed.&nbsp; It is
<o:p></o:p></p>
<p class=3D"MsoPlainText">unclear whether this list is the ones to be teste=
d for, or just &quot;some&quot;
<o:p></o:p></p>
<p class=3D"MsoPlainText">events.&nbsp; In addition, it is unclear why ther=
e is inconsistency in the
<o:p></o:p></p>
<p class=3D"MsoPlainText">coverage of the descriptions of the failures. The=
 three different
<o:p></o:p></p>
<p class=3D"MsoPlainText">monitoring methods are mentioned explicitly with =
the Interface Shutdown
<o:p></o:p></p>
<p class=3D"MsoPlainText">failures, but are not even mentioned for the othe=
r failures.&nbsp; And then
<o:p></o:p></p>
<p class=3D"MsoPlainText">while most of the failures list local or remote s=
ide, the last two
<o:p></o:p></p>
<p class=3D"MsoPlainText">failures do not indicate a side.&nbsp; Why?<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Clarified the significance of mentio=
ning of failover events. Added remote and local side applicability on Sub-i=
nterface failure and Parent interface failure.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">*************************************<o:p></o:p><=
/p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Some of the abbreviation=
s in section 6 are unclear.&nbsp; For example,
<o:p></o:p></p>
<p class=3D"MsoPlainText">since there is no real provider it is not clear w=
hich router(s) are
<o:p></o:p></p>
<p class=3D"MsoPlainText">meant by PE as distinct from P routers.&nbsp; Als=
o, while I familiar with
<o:p></o:p></p>
<p class=3D"MsoPlainText">Layer3 VPN, I am not familiar with the usage&quot=
;Layer2 VC&quot;.&nbsp; Further given
<o:p></o:p></p>
<p class=3D"MsoPlainText">taht VPNs have different label usages, I suspect =
that both &quot;Layer3 VPN&quot;
<o:p></o:p></p>
<p class=3D"MsoPlainText">and &quot;Layer2 VC&quot; are insufficiently spec=
ific to match to a specific size
<o:p></o:p></p>
<p class=3D"MsoPlainText">label stack.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; As an example of the abo=
ve confusion, in the figure in section
<o:p></o:p></p>
<p class=3D"MsoPlainText">6.1.2, the number of labels&nbsp; in the Layer3VP=
N from the PE to the P
<o:p></o:p></p>
<p class=3D"MsoPlainText">router is described as going from 2 to 3 upon fai=
lure.&nbsp; The PE-&gt;P link
<o:p></o:p></p>
<p class=3D"MsoPlainText">in the diagram is R1-&gt;R2, which is upstream of=
 the failure.&nbsp; So the
<o:p></o:p></p>
<p class=3D"MsoPlainText">number of labels on that link won't change.&nbsp;=
 The number of labels on the
<o:p></o:p></p>
<p class=3D"MsoPlainText">R6-&gt;R3 P-&gt;PE link (assuming I have properly=
 guessed what PE is) does go
<o:p></o:p></p>
<p class=3D"MsoPlainText">from 2 to 3.&nbsp; But the lines refer simply to =
PE-P.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Following changes have been made <o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">1.&nbsp;&nbsp;&nbsp; Added a relationship between=
 the general reference topology and individual test setups. Suggested that =
the individual test setups are sub-set of a large topology
<o:p></o:p></p>
<p class=3D"MsoPlainText">2.&nbsp;&nbsp;&nbsp; Removed TA/TG <o:p></o:p></p=
>
<p class=3D"MsoPlainText">3.&nbsp;&nbsp;&nbsp; Added notes for purposes cla=
rifying the roles of the routers wrt to P/PE &#8211;
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Following template used for all the figures- <o:p=
></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#43;-------&#43;&nbsp; &#43;-----=
---&#43;&nbsp;&nbsp;&nbsp; &#43;--------&#43;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; R1&nbsp;&nbsp; |&nbsp; |&nbsp;&=
nbsp; R2&nbsp;&nbsp; | PRI|&nbsp;&nbsp; R3&nbsp;&nbsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; UR/HE|--|&nbsp; HE/MID|----| MP=
/TE&nbsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |=
&nbsp; |&nbsp; PLR&nbsp;&nbsp; |----|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; |<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-------&#43;&nbsp; &#43;--------&#=
43; BKP&#43;--------&#43;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Figure 2.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Traffic&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Num of Labels&nbsp;&nbsp; Num of labels<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; before failure&nbsp; after fai=
lure<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; IP TRAFFIC (P-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<o:p=
></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer3 VPN (PE-PE)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1<o:p></o:p></p=
>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer3 VPN (PE-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2<o:p></o:=
p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer2 VC (PE-PE)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1<o:p></o:=
p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Layer2 VC (PE-P)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2<o:p=
></o:p></p>
<p class=3D"MsoPlainText" style=3D"text-indent:.5in">&nbsp;&nbsp; &nbsp;Mid=
-point LSPs&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0<o:=
p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Note: Please note the following:<o:p></o:p></p>
<p class=3D"MsoPlainText">For P-P case, R2 and R3 acts as P routers.<o:p></=
o:p></p>
<p class=3D"MsoPlainText">For PE-PE case, R2 acts as PE and R3 is acts as a=
 remote PE
<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;For PE-P case, R2 acts as a PE =
router, R3 acts as a P router and R5 acts as
<o:p></o:p></p>
<p class=3D"MsoPlainText">remote PE router (Please refer figure 1 for compl=
ete setup)<o:p></o:p></p>
<p class=3D"MsoPlainText">For Mid-point case, R1, R2 and R3 acts as shown i=
n figure &#8211; HE, Midpoint/PLR
<o:p></o:p></p>
<p class=3D"MsoPlainText">and TE respectively. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********************************<o:p></o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Similarly, while I suspe=
ct that the numbers are accurate, it is
<o:p></o:p></p>
<p class=3D"MsoPlainText">very hard to map the pre-failure label counts to =
the diagrams in a way
<o:p></o:p></p>
<p class=3D"MsoPlainText">that explains the difference between the numbers =
in section 6.1.1/6.1.2
<o:p></o:p></p>
<p class=3D"MsoPlainText">and&nbsp; 6.1.3 and onward.&nbsp; Assuming PE-PE =
traffic is HE-TE traffic, then
<o:p></o:p></p>
<p class=3D"MsoPlainText">the internal topology should not affect the label=
 count on that.&nbsp; So you
<o:p></o:p></p>
<p class=3D"MsoPlainText">probably mean something else.&nbsp; But I don't k=
now what.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; It is unclear what secti=
on 7 means by &quot;Select an overlay technology
<o:p></o:p></p>
<p class=3D"MsoPlainText">(e.g. IGP, VPN, or VC).&quot;&nbsp; Please clarif=
y.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Clarified Section 7.1.1, step B <o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">New text - Select or enable IP, Layer 3 VPN or La=
yer 2 VPN services with the DUT as the headend PLR<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Updated this as necessary<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For section 7.1.2 &#8211; test setup, &#8220;B&#8=
221; is not applicable &#8211; removed.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">**********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Why is section 7.1.3 (de=
termining tailend performance) included in
<o:p></o:p></p>
<p class=3D"MsoPlainText">the document, when no test cases include tailend =
failure?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Response&gt; Removed 7.1.3<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">************<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Is it an issue that the =
timestamp based&nbsp; method for determining the
<o:p></o:p></p>
<p class=3D"MsoPlainText">failover time will, on average, overestimate the =
failure time by on
<o:p></o:p></p>
<p class=3D"MsoPlainText">inter-packet interval?&nbsp; (Based on assuming t=
hat on average the failure
<o:p></o:p></p>
<p class=3D"MsoPlainText">and recovery are each uniformly distributed acros=
s the inter-packet
<o:p></o:p></p>
<p class=3D"MsoPlainText">interval.)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt; We suggest other two measurement met=
hods, so it is up the user to have a preference.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">***********<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 7.1.2 item A ref=
ers to 9 scenarios from section 6. There
<o:p></o:p></p>
<p class=3D"MsoPlainText">are only 8.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt;&nbsp; Fixed <o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">*********<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp; Section 7.4 decides to l=
eave out the nubmer of scenarios from
<o:p></o:p></p>
<p class=3D"MsoPlainText">section 6, leading to a surprising, but otherwise=
 probably meaningless,
<o:p></o:p></p>
<p class=3D"MsoPlainText">difference in wording.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">RESPONSE&gt;&nbsp; Fixed&nbsp; <o:p></o:p></p>
<p class=3D"MsoPlainText">**************<o:p></o:p></p>
</div>
</body>
</html>

--_000_52B0D42F4BADB144B850705C4549F6EA017F1B97dfweml511mbschi_--

From internet-drafts@ietf.org  Mon May 28 20:54:25 2012
Return-Path: <internet-drafts@ietf.org>
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 A395121F87DC; Mon, 28 May 2012 20:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.43
X-Spam-Level: 
X-Spam-Status: No, score=-102.43 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, 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 PCOlmZmKNARm; Mon, 28 May 2012 20:54:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3264421F87B3; Mon, 28 May 2012 20:54:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529035425.19614.95333.idtracker@ietfa.amsl.com>
Date: Mon, 28 May 2012 20:54:25 -0700
Cc: bmwg@ietf.org
Subject: [bmwg] I-D Action: draft-ietf-bmwg-protection-meth-10.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 29 May 2012 03:54:25 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Benchmarking Methodology Working Grou=
p of the IETF.

	Title           : Methodology for Benchmarking MPLS-TE Fast Reroute Protec=
tion
	Author(s)       : Rajiv Papneja
                          Samir Vapiwala
                          Jay Karthik
                          Scott Poretsky
                          Shankar Rao
                          JL. Le Roux
	Filename        : draft-ietf-bmwg-protection-meth-10.txt
	Pages           : 37
	Date            : 2012-05-28

   This document describes the methodology for benchmarking MPLS
   Protection mechanisms for link and node protection as defined in
   [RFC4090].  This document provides test methodologies and testbed
   setup for measuring failover times while considering all dependencies
   that might impact faster recovery of real-time applications bound to
   MPLS traffic engineered (MPLS-TE) tunnels.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-bmwg-protection-meth-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-bmwg-protection-meth-10.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bmwg-protection-meth/

