Re: [ippm] Second WGLC for draft-ietf-ippm-ioam-data

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Fri, 29 May 2020 08:04 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 980353A0C8F for <ippm@ietfa.amsl.com>; Fri, 29 May 2020 01:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=MyoVpWU+; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=CIPjUJda
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 Nm_MKJN5o4Pv for <ippm@ietfa.amsl.com>; Fri, 29 May 2020 01:04:53 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B20393A0C89 for <ippm@ietf.org>; Fri, 29 May 2020 01:04:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16706; q=dns/txt; s=iport; t=1590739493; x=1591949093; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=q5vPuPQzxYJ0gPufYDDYf9wxz9t6JkvhELQP4EXbmtQ=; b=MyoVpWU+yWowlC6+Idhms6X9v42AQ41Ojbk1fmbye13++8Q9wipEejiz YPGplc+6zcIW8jtK5M0HAfWHPYQqVw6WoBvSlx/x/DaXY1ayAoB/s7/nR Sr9pn0IE9WuLxnFgHQmyh0yLrtb7izfkWftz2FgZbUoHyyBZBFAoGx2w8 w=;
IronPort-PHdr: 9a23:PeraWB1IVFqIdTxUsmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxWGu6d/kFKPVoLerflC2KLasKHlDGoH55vJ8HUPa4dFWBJNj8IK1xchD8iIBQyeTrbqYiU2Ed4EWApj+He2YlpJFYD1YFiUqXvhpTIXEw/0YAxyIOm9E4XOjsOxgua1/ZCbYwhBiDenJ71oKxDjpgTKvc5Qioxneas=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWCAC9wdBe/4UNJK1mHQEBAQEJARIBBQUBggqBIS9SB29YLywKhBuDRgONQZNhhGeBQoEQA1ULAQEBDAEBGAEKCgIEAQGERAIXggQCJDgTAgMBAQsBAQUBAQECAQYEbYUsBicMhXIBAQEBAwEBEBEKEwEBLAwPAgEGAhABBAEBKAMCAgIlCxQJCAIEARIIGoMFgX5NAy4BDpN9kGcCgTmIYXaBMoMBAQEFgTYChAgYgg4DBoE4gmSJYRqBQT+BEUOCTT6CZwEBAgGBLQESASMrCYJeM4ItjkWDKYYniwmQJQqCVIgwhhGHUIJ3gmWJBZImHZA/iXOTewIEAgQFAg4BAQWBaiJmcHAVO4JpUBcCDYNnjFkMF4NPhRSFQnQCNQIGAQcBAQMJfItoAYEPAQE
X-IronPort-AV: E=Sophos;i="5.73,447,1583193600"; d="scan'208,217";a="501433063"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 May 2020 08:04:51 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 04T84p6A005716 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 29 May 2020 08:04:51 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 29 May 2020 03:04:50 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 29 May 2020 03:04:50 -0500
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 29 May 2020 03:04:50 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=N0rT1G1OjrQC4ViKgrFK4vTLikW8D1JbCKq5mKe0Cf8DIh1EyvBdotWk/mluQga6sIT3AOovM+b+Jj9iM1dZPm2Ily1icXtN82d3/ABBJ3uI+bpJyl+Yk1A4SRnlVm5Y90uXv/tZAX+42US9+hna40P9aamdzLHyldoXB/e8pbFPUEnjUOrgGh8zDpb5n976+8n4/kKQEnlU/78yyuQFc4ZY9fahK6Sv2TGUg4BqfxA4VGWYmSCNNQNJSj+5fu+Cvn3VH4vH46UaXvnUAg9AYC5EoKj7m2SHoGlQuCK8vnQa1e5QUjUBXWmvuKViMDBjH2d6CCk4yrFyj/k00UlO2w==
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=q5vPuPQzxYJ0gPufYDDYf9wxz9t6JkvhELQP4EXbmtQ=; b=Pp8jOhLep640PHNyJXJWW7BNWJnmHatg4jEhmbXQ5XYpX1gd5LdmV+yG2r7eutXXL4oXI1Vp2GPeNhVP/noJZsNfQTtJCy2ce+ZaM+x7MKdhX7ihensthxITzk8Mwkw9vea3rADf3EValzZkdd/38R9tdKAPTduA+rGgSH8iqHVQ/a1gwmtlROIRcBJhD5N2WZ3jcwtO4abDVK4naCU3LNykKcGZTQeidsxyGx72LsiNJyM6FRqKkEnTzhZf5XcTmAfb8FgxskNysrVV8WRCv8oqryczgkw6KNsKxejZO3lqKSJhZjOBhm3IkrEwr6iEr4yC6LI+RyrF8IE4AUZkwg==
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=q5vPuPQzxYJ0gPufYDDYf9wxz9t6JkvhELQP4EXbmtQ=; b=CIPjUJdaWmMknuHQ786t32rFTG4omzVEie9BzqJnxjpb6xfagJZC3z4g9/TrY4cKjdb8EZ3pRT0h7witg9DNAXinQDT6WshqeEy7peky0c4qoKnkadSUzxKOIJqptrDCxlhbXbluCabd/dzJeW+B3vr69FEN3PTrj/wZ8TqH5zg=
Received: from BYAPR11MB2584.namprd11.prod.outlook.com (2603:10b6:a02:c8::31) by BYAPR11MB2789.namprd11.prod.outlook.com (2603:10b6:a02:cc::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.17; Fri, 29 May 2020 08:04:48 +0000
Received: from BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::d8d7:dbc7:25a8:a4bd]) by BYAPR11MB2584.namprd11.prod.outlook.com ([fe80::d8d7:dbc7:25a8:a4bd%3]) with mapi id 15.20.3045.018; Fri, 29 May 2020 08:04:48 +0000
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>, "ippm@ietf.org" <ippm@ietf.org>, "tpauly=40apple.com@dmarc.ietf.org" <tpauly=40apple.com@dmarc.ietf.org>
Thread-Topic: [ippm] Second WGLC for draft-ietf-ippm-ioam-data
Thread-Index: AQHWKhNuJJGId+Vn1EukvMi3ERkkBaioxv8AgBYA3dA=
Date: Fri, 29 May 2020 08:04:48 +0000
Message-ID: <BYAPR11MB258434C22DCCE9AAE3271060DA8F0@BYAPR11MB2584.namprd11.prod.outlook.com>
References: E60BA8FF-A246-476F-81D6-03D230E7FFBE@apple.com <202005151551000453484@zte.com.cn>
In-Reply-To: <202005151551000453484@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: zte.com.cn; dkim=none (message not signed) header.d=none;zte.com.cn; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [173.38.220.33]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d6f056f2-ab8c-4c92-71f0-08d803a6f561
x-ms-traffictypediagnostic: BYAPR11MB2789:
x-microsoft-antispam-prvs: <BYAPR11MB278927738D54056B46F2C776DA8F0@BYAPR11MB2789.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 04180B6720
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FWaFccm6E++36TBSWbdg14NMGuQh784Zz78sUUp9kv+guUIGSzfAyNRfWZQW9JC5+itQEFCcKfpJ8u9JrVxqCYCJvXGwQqCwqyJyv6KO5mLTozo1aXOPBX+kzXp9/nygF9T5ecwnOHp949HwFFcuOxjFXnKF+xdR/Y9bzMpAWLARDnmQDzeD1H2/x9vWkIKdOC0iDAmtsbfL4H6NlN1lBqwsqNQXkOl+MbK1nNRbEcUulFJamRJ3RVnv0AipPBpFl5dSuQwcFGF5wXkoAY/SM/y8qY4RHYyN14S0u8EzwN9PDmta9Z8EIhPYhABAypS3SQw20QiyTlyjQ2ssN1P+5kGPYxYPy/mmySlozrv3g/Vq13St+Wn1DiDC/3J966nS+KpiKblgS8HS7PPbllAHgA==
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; SFTY:; SFS:(4636009)(346002)(376002)(136003)(39860400002)(366004)(396003)(55016002)(110136005)(316002)(33656002)(76116006)(64756008)(66476007)(52536014)(9686003)(66946007)(5660300002)(66446008)(66556008)(2906002)(166002)(7696005)(186003)(478600001)(53546011)(8936002)(8676002)(966005)(71200400001)(6506007)(86362001)(26005)(83380400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: D8V7xXtbGwSLBT1ZN6EJLQcgqxS5oPRH8rhcgrwPoKqFkamFF2/hSvly1OKy+gx2xFzCni9BwY/ZNBLyt6+9kpNhh5ITlTiXL1Uob03UFkESkoZdH0NCHXR55Mz8AzOedIjY/7Aceibg1Iom3x1FtAwTXAAOyxfsKJon4ul72C7Q0uaw5t3xRnMf+XfUK1f13g8stqc0PR7R9sK9oRWCDWS3gzsunq7WYjrBbO/MzyoiYwf9tTWmuOmVMklGw25d6OKQmv+rzbF7XbDmHjv6Jxpet+E9/bN2XdLV8E7ZOxa86Krqr7nRtmJsaGvnzjUjXm4fUwUDsb4fUtLmc2oDFivYiycxhJGIXBueRcopOt0sB+ux7i65tPQUq5LgRVDc7Tk2X+xXLaGa5tvWlgC0TBkY2m+8W18QOSufNzxxf5GQV/AGum/GLwgawyo2uMfF9aSWNTE3/pOaILGKfmZi+jHrS+zN4RC40wLGbJY1ei/GDxjWyIQSQ+nVbk4E3mXN
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB258434C22DCCE9AAE3271060DA8F0BYAPR11MB2584namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d6f056f2-ab8c-4c92-71f0-08d803a6f561
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2020 08:04:48.6835 (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: VrcVIsAxAYLYQHsvU46L2iaSE9na+9XsK4OXWKiSpJAo6Fjigi/EL4f2jUhb3zUlLj66bOe8u+1Ckf4S8tauqg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2789
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/dri0_ERYFja5vKMazjR-mqdeGos>
Subject: Re: [ippm] Second WGLC for draft-ietf-ippm-ioam-data
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, 29 May 2020 08:04:56 -0000

Hi Xiao Min,

my understanding is that there are devices which can calculate transit delay, which is why the field was introduced quite a while ago.
draft-ietf-ippm-ioam-data already includes an option to timestamp packets (see e.g. sections 4.4.2 and 4.6 in draft-ietf-ippm-ioam-data-09) which you can use exactly the same way as you propose below, i.e. you can use the timestamp field for the time, at which the packet was transmitted by the node. What draft-ietf-ippm-ioam-data asks you to do is to properly document when you timestamp the packet.

Cheers, Frank

From: ippm <ippm-bounces@ietf.org> On Behalf Of xiao.min2@zte.com.cn
Sent: Freitag, 15. Mai 2020 09:51
To: ippm@ietf.org; tpauly=40apple.com@dmarc.ietf.org
Subject: Re: [ippm] Second WGLC for draft-ietf-ippm-ioam-data


Hi all,



I have a comment on this draft.

I was told by the implementers of my company that it's difficult to add accurate transit delay into the trace option data. The reason is that in order to calculate transit delay, the node firstly needs to obtain the time at which the packet is transmitted by the node, which is obtained at PHY layer, otherwise, the node can't do any calculation after the time is obtained.

If the above issue is common across different implementations, I suggest to substitute the "transit delay" with '"timestamp" of the time at which the packet is transmitted by the node.



Best Regards,

Xiao Min
原始邮件
发件人:TommyPauly <tpauly=40apple.com@dmarc.ietf.org<mailto:tpauly=40apple.com@dmarc.ietf.org>>
收件人:IETF IPPM WG <ippm@ietf.org<mailto:ippm@ietf.org>>;
日 期 :2020年05月15日 01:16
主 题 :[ippm] Second WGLC for draft-ietf-ippm-ioam-data
_______________________________________________
ippm mailing list
ippm@ietf.org<mailto:ippm@ietf.org>
https://www.ietf.org/mailman/listinfo/ippm

Hi IPPM,

At our virtual interim meeting, we decided to put draft-ietf-ippm-ioam-data through a second last call, based on the new revisions, in mid-May. This email starts a two-week WGLC for this draft.

The latest version can be found here: https://tools.ietf.org/html/draft-ietf-ippm-ioam-data-09

This last call will end on Thursday, May 28. Please reply to ippm@ietf.org<mailto:ippm@ietf.org> with your reviews and comments.

Thanks,
Tommy & Ian