Re: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Mon, 31 August 2020 14:40 UTC

Return-Path: <fbrockne@cisco.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 319D03A1484 for <ippm@ietfa.amsl.com>; Mon, 31 Aug 2020 07:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.5
X-Spam-Level:
X-Spam-Status: No, score=-9.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Y2VemprI; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kY89opi7
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 lXIySqL2izSL for <ippm@ietfa.amsl.com>; Mon, 31 Aug 2020 07:40:18 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2E753A1468 for <ippm@ietf.org>; Mon, 31 Aug 2020 07:40:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=30260; q=dns/txt; s=iport; t=1598884817; x=1600094417; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=lssfdTSkznYj8COMa4TSqNxKpoCcbpyUAQEGyqosP3E=; b=Y2VemprIOmMlFs2gumGhuzo5CMLif95sbAeMBO+8GlBxPvYgOvc89TiI VqEivzl/Oodc00BVizk6qYpw0o7JIiM2oct04EEpuq16yKzVK8t7l7SfD UelbpUq0Lh+jmFaAwayLD0KIstJmfSWLBfkKsjGeHFFL8DGHGCys1jvEF o=;
IronPort-PHdr: 9a23:19quaBPbc8fAZug8Yj4l6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEvK893kXERojS8flEzePKr+brXmlTqZqCsXVXdptKWldFjMgNhAUvDYaDDlGzN//laSE2XaEgHF9o9n22Kw5ZTcD5YVCBuHCp4DcIERW5PBZpYO/yH92ag8G+zevn/ZrVbk1Bjya8ZrUnKhKwoE3Ru8AajJEkJLw2z07Co2BDfKJdwmY7KA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0C1AAAbC01f/4sNJK1WCRoBAQEBAQEBAQEBAwEBAQESAQEBAQICAQEBAYIKgSMvUQdwWC8sCoNuQIFdgWkDjXaYcYJTA1ULAQEBDAEBGAEJBwQCBAEBhEwCF4IzAiQ4EwIDAQELAQEFAQEBAgEGBG2FXAyFcgEBAQQBAQoGEQoTAQEsBAcBDwIBBgIQAQQBASEHAwICAiULFAkIAgQBDQUIFwODBYF+TQMuAQ6VCJBoAoE5iGF2gTKDAQEBBYE3AoQEGIIQCYE4gnGCV0tDgj5fgzIbgUE/gRFDgU9+PoJcAQECARaBGi4rCQiCWTOCLZMbhmqLbZB8CoJliGiRa4MJgSeISI4ehUCSUYpOkGGEKAIEAgQFAg4BAQWBayOBV3AVO4JpCUcXAg2NfCODcYUUhUJ0AgEUIAIGAQkBAQMJfI8VAYEQAQE
X-IronPort-AV: E=Sophos;i="5.76,375,1592870400"; d="scan'208,217";a="567610768"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Aug 2020 14:40:16 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 07VEeFK5014083 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 31 Aug 2020 14:40:15 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 31 Aug 2020 09:40:15 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 31 Aug 2020 10:40:14 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 31 Aug 2020 09:40:14 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AmSb9KMZ6Zu2T3TfN3gKJXju/2Pmd+pQt00DrFBBSjo+t7IuonkjmqWF29TqpujyalQi/wJb1uwWGK/SR9Y+fsnTAw16/bk8K77oZpqnaHAvpBAAAJWN00iRXqUQQysW3GtpeBco/+f+pAEQv8pObxcT12rEUjpIEhFapPl1nGdf0xz5g2h3gpcdf7e3oo1tiFnZFEwrSABh6Kp1kmogKmAd9mGRBtyqQ0Zr3bJMYfS4k9nVb+nq1mJ5LQtYzVX10xmZCLt1WDv9L3UN7jrJ5wfujBHINzVycIwv5Wltac2x1/W4sgUDgf0i/bimUfjiAhIuECgC0gBM5rCCflHd/w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lssfdTSkznYj8COMa4TSqNxKpoCcbpyUAQEGyqosP3E=; b=P8fSGbstJQ1YcsUN89AVrjTHQ0Nk/1Sz6BrNw63x67gvA8G4DJmKC4szzJOWGiYifOyxMrnY+iL/T0bRuyl2jczoSvwPKn3+B2dxx/dRA2sAYHXKzwISKUtJTmcQZKuEZyjmKEtJESb1Cr7sTZ5dBzd91hoJC1YaCShh6+wjtEdtR70PRhh9GNic+IjsmuYzRY4rSXql4AT/h8UOkCnCdo/EL0wg6uYQPURiYbXaA80DP8D05YkJefVjxN0jHuZhPS+StjCUHa8bAQBWtOS473JaPWuUfNnmdRGj2bv9VoSXPQQh2T75WnYuZ8e3X4/zfYRtCWpiH/bETGcQcznmjQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lssfdTSkznYj8COMa4TSqNxKpoCcbpyUAQEGyqosP3E=; b=kY89opi7R/U2yneruQfRO5rL88rg7zVHP5cAbbuyzFU3MtME8dKCBQfKvSp5G97/h5bhO2KdSB0EZC4L/71Im7W0ZSZbEtD0Bv5snPKgdTnh2ohyBDAC6bFwmqMH02jJa/TmTpuSEyyYtxfG1rrF2/fPl7HiQqbIiZT215fO0+c=
Received: from BYAPR11MB2584.namprd11.prod.outlook.com (2603:10b6:a02:c8::31) by BYAPR11MB2710.namprd11.prod.outlook.com (2603:10b6:a02:c7::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3326.24; Mon, 31 Aug 2020 14:40:12 +0000
Received: from BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::4141:82af:eeb8:e7c6]) by BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::4141:82af:eeb8:e7c6%7]) with mapi id 15.20.3326.025; Mon, 31 Aug 2020 14:40:12 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "MORTON, ALFRED C (AL)" <acm@research.att.com>, Tommy Pauly <tpauly@apple.com>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
CC: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Thread-Topic: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method
Thread-Index: AQHWcoDs2QbZQ6/rRUCWoK1Kl2WS66k4H4cAgBYSYYCAABXVAIAEDeNg
Date: Mon, 31 Aug 2020 14:40:12 +0000
Message-ID: <BYAPR11MB258442AFA1F9597BF3B7BECEDA510@BYAPR11MB2584.namprd11.prod.outlook.com>
References: <03CC314C-21FA-44CD-AF2E-F0076755AF04@apple.com> <4D7F4AD313D3FC43A053B309F97543CF0140BC96B0@njmtexg5.research.att.com> <D2F2FAE3-6998-4793-AD57-F12987FF3A5D@apple.com> <4D7F4AD313D3FC43A053B309F97543CF0140BCEEB5@njmtexg5.research.att.com>
In-Reply-To: <4D7F4AD313D3FC43A053B309F97543CF0140BCEEB5@njmtexg5.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: research.att.com; dkim=none (message not signed) header.d=none; research.att.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.220.37]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 13683ef4-0c26-428d-d9e2-08d84dbbc4a2
x-ms-traffictypediagnostic: BYAPR11MB2710:
x-microsoft-antispam-prvs: <BYAPR11MB271011F6964C559999909032DA510@BYAPR11MB2710.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: KzJaksFegsqJIQvSLvrNak/MpEiDAkE0fOXufSijajanaW/EfJmP/7S4WlkF2tK0oCYpWO95Ldrt76GP2rgCghzdctI3S4RLH0VHln5qZQnXPPVyBEjwN7fdBgBITVzgzpVzXMIFOAlT6o3uV2KpWgB7AnC87z0N7xFSpe6tp702cLh7eIeAKbXu0bhYLC5KjZqgEZYlezndE5AtO6DwW4HjHN9hDlkpp4Ng6Yx43MxY4l2HY6qOcvu8WHPX9k01R9+O+0JKoZDRIvo2eVeLmVFg0aA5T1b89/W8MIQZVXgKJ+BzaHbV93RDjnXf0mIqYKruDNvXsC/TsVsWDrjZ4s56oENT65vp3Chd3aUcazzL+M73VqY3qtXWjlHoWYuyc6bpfMIxIZHaUeQ1G3BHGQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2584.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(346002)(376002)(39860400002)(136003)(366004)(396003)(7696005)(966005)(66556008)(66476007)(66946007)(8676002)(64756008)(76116006)(66446008)(4326008)(26005)(186003)(71200400001)(33656002)(2906002)(110136005)(86362001)(166002)(53546011)(6506007)(83380400001)(5660300002)(9686003)(55016002)(316002)(478600001)(52536014)(8936002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 2kMxBf0NDFz3fnVmEnZ7P4tZgR0Ns0GOEwixobeNUOkXrtOvZR+BleNDB/6mvg09urBzYfU98u2Q40eppjorOMx0GU/MNug19t4GARXxVHq5jCSOpncGyIfnfjQGzt9mN2ylUDTjRG4XSD1XPG3xKIF1cJOMEbAzW9YrVfJBaf1Pmyv2CG1jzrZmHRsxm77lNw4moTZWS2ShdHDYd3ZoOA6wio8jYVAvcNwcq7fk9pZYVK5HZKSOIXMPHeb9zysSdDexIX1RdsVd0Gl6pD6ms2UfNe1FHm3NJYeMMolsOmZ/iSX0OLDx8ewTCnKD/EsQOyQpOMHggMaQTpEgxwoLBq1Fs+Tefn9lj/e0JPVQQdo0LFRcnIDB7kIt8Bt0ph40YHaRLy4Av1+EWBOhRgmtKNHpCPS0V3Pv7KSo4IIOmwXDSrBgR+91LTztl/3ZKEjncxBqFQCy5vG527XkwyFl7/mEk9vAV4zV/ms4eUPtLIGDV8Fm3z0eU/G5ypeAyZvSeCKWPlNV0Qif7ZwI6KPBCTQIzKLnbAjSfAEt/uEwvhE1NBE8ppA1hRyenFlJOHzdYby1vpGe53SfgZ+QYw+zJR4M5bOvJBtyk1oSdeKCxhA6839XaQis8nOVW2ACwBkv7wi4600L4rvrc6Feb0Uq1w==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB258442AFA1F9597BF3B7BECEDA510BYAPR11MB2584namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2584.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 13683ef4-0c26-428d-d9e2-08d84dbbc4a2
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Aug 2020 14:40:12.2937 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: oabj2Hi589MXNVXiS4LY5yVLinuHbpUtSF9wAIqMUvvwTwirW8xaCdFsXDW3CVIs6WL2oX4MnhkG4cMb0YI05Q==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2710
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Z3JtT0vJqXi1Gmro7iP8rHTEGwQ>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method
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: Mon, 31 Aug 2020 14:40:22 -0000

Thanks for getting the document to the finish line. I support advancing the document – but noticed a couple of nits while reading through the -03 version of draft (see below).

Cheers, Frank

A few nits:

* Section 1: [copycat][copycat] mentioned twice
* Notation: Would it make sense to use a notation which is more Latex-style, e.g. use dt_n, dt_n+1 instead of dtn,dtn+1. Initially I got a bit confused because the dtn wasn’t defined in section 4, whereas dt was.
* Notation: Would it make sense to use a different character that “I” for the duration, because “I” can easily be confused with (me, myself)? E.g. section 8 says: “The duration of a test, I, MUST be constrained in a production network, since this is an active test method and it will likely cause congestion on the Src to Dst host path during a test.”.. and at first glimpse, I was wondering why I should be constrained in a production network :-).
* Section 5.3: IMHO it would be useful to add a sentence / stress the fact, that the definition of “IP Layer Capacity” is always wrt/ particular endpoints, i.e. E2E – rather than that of a channel between endpoints. I.e. the capacity of the channel between endpoints could be lower (in case e.g. compression is used) than the capacity between endpoints. Another place to put this discussion could be section 8.3.
* Section 5.4: Shouldn’t the text say [T0, T0+I]? T0 is defined in section 4, T is not. (There are several occurrences of T in the document)
* Section 6.3: Replace “[see section Related Round-Trip Delay and Loss Definitions below]” with a proper reference
* Section 6.3: What are “Standard Formed packets”? Could we add a reference?

* Section 6.5: Line break in “Maximum_C(T,I,PM)”

* Section 6.6: Does one Megabit consist of 1048576 bits or 1000000 bits?

* Section 8.1: If I understand things correctly, the examples given here refer to Mbps as a unit, i.e. Rx+10 would mean Rx+10Mbps. Correct? Is there a way to future proof these numbers and methods: What is Mbps might be Gbps in 10 years? E.g. we could consider defining those formulas in relation to the nominal interface speeds of the Src and Dst. Relative numbers might be better than absolute values, e.g. Rx-30: How would we know that we can always reduce the rate by 30 Mbps?

* Section 8.4: Empty bullet

* Section 10.: How about adding a requirement that the identity and integrity of Src and Dst should be checked and confirmed? That way we ensure that we indeed measure Src to Dst  and not to some MIM “friendly” proxy that would give me the impression of stellar IP layer capacity...






From: ippm <ippm-bounces@ietf.org> On Behalf Of MORTON, ALFRED C (AL)
Sent: Samstag, 29. August 2020 01:53
To: Tommy Pauly <tpauly@apple.com>; IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method

Hi Tommy,
Thanks for sending the reminder!
I support this as an author of course,
Al


From: Tommy Pauly [mailto:tpauly@apple.com]
Sent: Friday, August 28, 2020 6:35 PM
To: IETF IPPM WG (ippm@ietf.org<mailto:ippm@ietf.org>) <ippm@ietf.org<mailto:ippm@ietf.org>>
Cc: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>; MORTON, ALFRED C (AL) <acm@research.att.com<mailto:acm@research.att.com>>
Subject: Re: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method

Hi IPPM,

A reminder that our WGLC is ending next week for draft-ietf-ippm-capacity-metric-method. Please take a moment to review the document!

Thanks,
Tommy

On Aug 14, 2020, at 2:31 PM, MORTON, ALFRED C (AL) <acm@research.att.com<mailto:acm@research.att.com>> wrote:

Thanks Tommy and Ian!

While updating a few references this week, I noticed that the 02 draft had no Security Considerations Section.  That won’t do!

The co-authors came together and supplied new text for the Section in version 03, posted minutes ago. Please consider version 03 of the draft during WGLC.  Thank you IPPM.

For the co-authors,
Al


From: ippm [mailto:ippm-bounces@ietf..org] On Behalf Of Tommy Pauly
Sent: Friday, August 14, 2020 5:21 PM
To: IETF IPPM WG (ippm@ietf.org<mailto:ippm@ietf.org>) <ippm@ietf.org<mailto:ippm@ietf.org>>
Subject: [ippm] WGLC for draft-ietf-ippm-capacity-metric-method

Hello IPPM,

As discussed at IETF 108, draft-ietf-ippm-capacity-metric-method is stable, and the group felt it is ready for Working Group Last Call.

The latest version can be found here: https://tools.ietf.org/html/draft-ietf-ippm-capacity-metric-method-02<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dippm-2Dcapacity-2Dmetric-2Dmethod-2D02&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=SIvlMcMEEzV1Wv8tA8hftr1Fvi38_c2R6bgbotceIsU&s=WEcaTbukpUJlfOGrn8Lbw-jjrpTxRsPst6bsHPjjExE&e=>

The last call will end on Wednesday, September 2. Please reply to ippm@ietf.org<mailto:ippm@ietf.org> with your reviews and comments, and indicate if you think the document is ready to progress!

Best,
Tommy & Ian
_______________________________________________
ippm mailing list
ippm@ietf.org<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_ippm&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_6cen3Hn-e_hOm0BhY7aIpA58dd19Z9qGQsr8-6zYMI&m=WhdjOJaLaKnkqCY9q-_CdCoH6_wwB1_QaV9FHk-qgNc&s=mMx6KKiG6xhHD9mZLMLJ70_AsL7gk_GnydQqC14aB00&e=>