Re: [ippm] Magnus Westerlund's Discuss on draft-ietf-ippm-capacity-metric-method-06: (with DISCUSS)

"MORTON, ALFRED C (AL)" <acm@research.att.com> Fri, 05 March 2021 13:22 UTC

Return-Path: <acm@research.att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 358803A2540; Fri, 5 Mar 2021 05:22:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 FCR0qljA-otf; Fri, 5 Mar 2021 05:22:16 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 910533A253F; Fri, 5 Mar 2021 05:22:16 -0800 (PST)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.43/8.16.0.43) with SMTP id 125D55O3010443; Fri, 5 Mar 2021 08:22:06 -0500
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049287.ppops.net-00191d01. with ESMTP id 373aap70mf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 05 Mar 2021 08:22:06 -0500
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id 125DM0Ak023848; Fri, 5 Mar 2021 07:22:01 -0600
Received: from zlp30495.vci.att.com (zlp30495.vci.att.com [135.46.181.158]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id 125DLu4F023775 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 5 Mar 2021 07:21:56 -0600
Received: from zlp30495.vci.att.com (zlp30495.vci.att.com [127.0.0.1]) by zlp30495.vci.att.com (Service) with ESMTP id A7A3B4068F83; Fri, 5 Mar 2021 13:21:56 +0000 (GMT)
Received: from clph811.sldc.sbc.com (unknown [135.41.107.12]) by zlp30495.vci.att.com (Service) with ESMTP id 844F64068F82; Fri, 5 Mar 2021 13:21:56 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clph811.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id 125DLuOU011431; Fri, 5 Mar 2021 07:21:56 -0600
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clph811.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id 125DLm6b010920; Fri, 5 Mar 2021 07:21:49 -0600
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-green.research.att.com (Postfix) with ESMTP id 1BB7610A18D7; Fri, 5 Mar 2021 08:21:48 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0513.000; Fri, 5 Mar 2021 08:22:07 -0500
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
CC: "tpauly@apple.com" <tpauly@apple.com>, "ianswett@google.com" <ianswett@google.com>, "draft-ietf-ippm-capacity-metric-method@ietf.org" <draft-ietf-ippm-capacity-metric-method@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Thread-Topic: Magnus Westerlund's Discuss on draft-ietf-ippm-capacity-metric-method-06: (with DISCUSS)
Thread-Index: AQHXC4EzqJ5daDOk8keYoMTRANvS6qpo9txggAGffICAACldMIAGGjkAgADI6CCAAuLjkIABA+eAgAAUJgCAAB+NgP//reVw
Date: Fri, 05 Mar 2021 13:22:06 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF0147CA565A@njmtexg5.research.att.com>
References: <161426272345.2083.7668347127672505809@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF01476A0C0E@njmtexg5.research.att.com> <66f367953ae838c8ba7505c60e51367843117787.camel@ericsson.com> <4D7F4AD313D3FC43A053B309F97543CF01476A0FE3@njmtexg5.research.att.com> <HE1PR0702MB3772A66E2C0409F5A69DC7DA95999@HE1PR0702MB3772.eurprd07.prod.outlook.com> <4D7F4AD313D3FC43A053B309F97543CF0147CA50DA@njmtexg5.research.att.com> <HE1PR0702MB377281B141FBB6D63015CC1895969@HE1PR0702MB3772.eurprd07.prod.outlook.com> <FRYP281MB01127EE4544CADF8B6E6E2E19C969@FRYP281MB0112.DEUP281.PROD.OUTLOOK.COM> <HE1PR0702MB37725A93AE2748D0619DB95D95969@HE1PR0702MB3772.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0702MB37725A93AE2748D0619DB95D95969@HE1PR0702MB3772.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [24.148.42.167]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-03-05_08:2021-03-03, 2021-03-05 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 malwarescore=0 lowpriorityscore=0 clxscore=1015 mlxscore=0 suspectscore=0 bulkscore=0 phishscore=0 adultscore=0 mlxlogscore=999 spamscore=0 priorityscore=1501 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2103050065
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/rEJiP-cSzQ8lhgZAezmfHX0soI0>
Subject: Re: [ippm] Magnus Westerlund's Discuss on draft-ietf-ippm-capacity-metric-method-06: (with DISCUSS)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Mar 2021 13:22:18 -0000

Hi Magnus and Rüdiger,

The working text on the "applicability" limits that we added to the scope section *included an earlier agreement* to add the first sentence below and the bullet, so now the whole paragraph reads:

   The primary application of the metric and method of measurement
   described here is the same as in Section 2 of [RFC7479] where:

   o  The access portion of the network is the focus of this problem
      statement.  The user typically subscribes to a service with
      bidirectional access partly described by rates in bits per second.

   In addition, the use of the load adjustment algorithm described in
   section 8.1 has the following additional applicability limitations:

   - MUST only be used in the application of diagnostic and operations
   measurements as described in this memo

   - MUST only be used in circumstances consistent with Section 10,
   Security Considerations

We can make further edits to balance your comments but let's start here,
and sorry for not including the whole paragraph last night - it seems 
that I should have. 

Al

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: Friday, March 5, 2021 8:06 AM
> To: Ruediger.Geib@telekom.de
> Cc: tpauly@apple.com; ianswett@google.com; draft-ietf-ippm-capacity-
> metric-method@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org;
> iesg@ietf.org; MORTON, ALFRED C (AL) <acm@research.att.com>
> Subject: RE: Magnus Westerlund's Discuss on draft-ietf-ippm-capacity-
> metric-method-06: (with DISCUSS)
> 
> Hi,
> 
> Ruediger, if you can find a formulation that covers that national test
> case I
> am likely fine with it. If the involved parties know who to discuss issues
> with and can get them addressed I am not worried. I am worried where
> someone
> deploys a couple of servers, like the current TCP speed tests and users
> run it
> totally by themselves.
> 
> And to be clear I think with more experience with large scale deployment
> of
> the algorithm and more experiments beyond the intended deployment model
> this
> should be possible to update the specs to remove this type of limitation.
> 
> Cheers
> 
> Magnus
> 
> > -----Original Message-----
> > From: Ruediger.Geib@telekom.de <Ruediger.Geib@telekom.de>
> > Sent: den 5 mars 2021 12:13
> > To: Magnus Westerlund <magnus.westerlund@ericsson.com>
> > Cc: tpauly@apple.com; ianswett@google.com; draft-ietf-ippm-capacity-
> > metric-method@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org;
> > iesg@ietf.org; acm@research.att.com
> > Subject: AW: Magnus Westerlund's Discuss on draft-ietf-ippm-capacity-
> > metric-method-06: (with DISCUSS)
> >
> > <snip>
> >
> > I think this is a bit to unclear in regards to the limitation of scope.
> My
> > worry are internet wide measurements. Reading what exists in the
> currently
> > available draft in the Section 10, there are no limitation here
> described to
> > only use this algorithm only across controlled networks. Especially as
> > bullet
> > 5 in Section 10 relies on the load algorithm what is currently written
> is
> > fine
> > across the whole internet as long as sender and receiver are okay with
> the
> > measurement which is not what I at least thought we agreed.
> >
> > Can you please be explicit that the load algorithm is limited to use
> across
> > networks path that are controlled or managed and not intended for
> Internet
> > wide usage.
> >
> >  - MUST only be used as part of measurements within managed networks,
> > and not
> > across general Internet.
> >
> > [RG] That's tough, as regulators are interested in this test and
> regulators
> > aren't part of a domain. So they might resort to TCP speed tests, being
> less
> > accurate and precise and not standardised (note that penalties are
> discussed
> > to be linked to results). I'd be interested in finding agreement to have
> > metric and method standardized for at least nations under authority of a
> > single regulator. No idea how exactly. Would a bound on RTT/in some
> > countries
> > multiple instances and some additional parametrization information prior
> to
> > start, e.g., a contracted access bandwidth, help?
> >
> > [RG] I'm off for the weekend (I'm out for a lasting solution, not
> > necessarily
> > a speedy one) - regards,
> >
> > Ruediger