IETF Logo Mail Archive

[ippm] PBT draft

Haoyu Song <haoyu.song@futurewei.com> Mon, 16 December 2019 19:57 UTC

Return-Path: <haoyu.song@futurewei.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 7BAC8120902; Mon, 16 Dec 2019 11:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 e3i0aFekKEWu; Mon, 16 Dec 2019 11:57:06 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-bn3nam04on0729.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4e::729]) (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 EB2A412094F; Mon, 16 Dec 2019 11:57:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=e3dH5IuuFOf6bZqw5YhJQfBNxhm1O4pn86Ka5Dc3eYkxYp3h5ZmPAb67b1Pt871ebXfK1Y5YOlycCPx8wWv8kXUkX2apMzFNhhBhUZ7DtLjfDhIZyljyzyyCjxRkBFwztQKTKH9s4oZhnbw7z0+bHPpwu1Ltljup+hLldAaevWkYNM1oDoHN0O46DplW2XCRdzRc0LWCghEYrtPy9A43zjdPm27lzRFtjLluvrKfC0LbpAmTJfar98wqbEgEJ6joExtsoX6NHCGL46LkHtlOlZ7ZLjMIQlDqizyDnzjBJEc+6RiQUcEB9HWQqqjnLqyhxv6DrAJcagLfXdSIJfIm/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=b++De7nn24HI1poe4Td+p6DeyDp79mwn8pGauGIbkK4=; b=j47Fbr+lrvOwHdhILhcZZ3gMTUX03tsdt0+bG3N4JJdRWxqWWEVKddlbFLml+FGv2ahF8EMWtXtXQltH+Q312MN9ko9x/YTEtpMKqXpaVY2ysh8p1yrPMz0qfRH35plnzHeXOP/9Z7hexaOxaBIuGhFO2TLGdpD7GvZ5hQ/3hYazg8ueaUefzj0sj/a2C9JRqlFj3udzoi9z7mE6wTFa+PXukuupELKtrkqQ9AoTQwIfeT2UkLy7lNNTUqAAJMuhfFyZcWXVOVhZHdg0WVj/2hKaerUJp8WzwCkEJoebJSedXpCLTF1WbczL0GbrUYWmy5CMUHiN+escwJsqf3zezQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=b++De7nn24HI1poe4Td+p6DeyDp79mwn8pGauGIbkK4=; b=T5Qu6rrDTcasIVMRjz40/0zbhpBXMguM2u4OkrLP4qqayBp99h0yW8bRzybiMVRUfepIay7xc2QgbJKGoJg5qXjxDIZwZCTfpuLW6KTw13ucWb4pH1+Q7xJb7wZLLBH+Wr/KwcEyZl1yUCKB9nTEPlXjlyLK7PwP2DxHg9s+Umw=
Received: from BYAPR13MB2485.namprd13.prod.outlook.com (52.135.228.19) by BYAPR13MB2456.namprd13.prod.outlook.com (52.135.229.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.12; Mon, 16 Dec 2019 19:42:49 +0000
Received: from BYAPR13MB2485.namprd13.prod.outlook.com ([fe80::61a4:f17f:156:4876]) by BYAPR13MB2485.namprd13.prod.outlook.com ([fe80::61a4:f17f:156:4876%7]) with mapi id 15.20.2559.012; Mon, 16 Dec 2019 19:42:49 +0000
From: Haoyu Song <haoyu.song@futurewei.com>
To: IPPM Chairs <ippm-chairs@ietf.org>
CC: IETF IPPM WG <ippm@ietf.org>
Thread-Topic: PBT draft
Thread-Index: AdW0R9S1rDSbZ/xySHiFRKTVKjbuhQ==
Date: Mon, 16 Dec 2019 19:42:49 +0000
Message-ID: <BYAPR13MB24858E7106BAC88C1F55C4E19A510@BYAPR13MB2485.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=haoyu.song@futurewei.com;
x-originating-ip: [12.111.81.95]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c6af36fc-632c-4a3f-2dd0-08d7826021e0
x-ms-traffictypediagnostic: BYAPR13MB2456:
x-microsoft-antispam-prvs: <BYAPR13MB2456ED80F2ABA150ED263A049A510@BYAPR13MB2456.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02530BD3AA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(39840400004)(366004)(346002)(376002)(136003)(199004)(189003)(316002)(52536014)(5660300002)(44832011)(86362001)(6506007)(2906002)(55016002)(64756008)(66556008)(9686003)(66476007)(66446008)(81156014)(66946007)(76116006)(8936002)(81166006)(8676002)(7116003)(71200400001)(33656002)(478600001)(26005)(6916009)(186003)(4326008)(3480700005)(966005)(450100002)(7696005); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR13MB2456; H:BYAPR13MB2485.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Wh+9tyjQJbcIbXDBUch8/KfBdXPf7RGOiPyfxUDDhjJUcILiUp4j62lcgYE3h33DU8g46fVMGU9PSqKSHAXkCLRy2GBlPPpctfuQZVUxVDHVFiJBUm9StDhIcLSQ1/sXAni9yqsEsK0JChgatDM3eM+Yrf8RIfPTBewbUFPOIIuAkK2GHUwFy7firVQCobfgCi7sV69xY4DNCn42sAq33zu0SXYPlOAFpsSLz9eK1SnR3ouEsEUgbAaOWvBBMvN3Xq5uBwg4WETaT10c+0LRyAcLMujeHNs4KwDpM13dvUF1xiFuh7Jr0LXVnSAHZI4GxLTBI43u2nEspxYMdw6GaZtcvNWphSn17ZCbjn76ghgZFqbAhzVrStFmCtRAYq1iqm1AWM/ktsGFcUPLNc0FSRpgIhKWKacXdq72EabRmTM+vaWl5E460UNRgVQbbDBBvDFhGOAxEKkskEQI6guZV679pY9MpmDzmAD7EOvQTVI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR13MB24858E7106BAC88C1F55C4E19A510BYAPR13MB2485namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c6af36fc-632c-4a3f-2dd0-08d7826021e0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Dec 2019 19:42:49.2266 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: eXq6RGtQM7avW7tGyydwsxeDSkAPONehTZq5x52XqkcsGrjyWSnp/Ug0BE1PoV9tsk+A2vEmedLXwdeiXmzDTQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR13MB2456
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/5vvC2EPEqPyov9-g2JAp2AEWY3s>
Subject: [ippm] PBT draft
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, 16 Dec 2019 19:57:11 -0000

Hi IPPM chairs,

We have requested to present this draft for two times in past meetings but didn't get a chance due to the lack of time in WG sessions.
So I write this email to bring it to your attention.  We also like to raise more discussion in email list.

https://datatracker.ietf.org/doc/draft-song-ippm-postcard-based-telemetry/
The draft is now in version 06.

It describes and compare two basic types of on-path telemetry techniques: postcard and passport.
It describes two subtypes of postcard techniques: instruction-based and marking-based. Both has its applications:

The instruction-based variation has been stripped out from the draft and now evolves to be a new IOAM option mode. The draft has been adopted by IPPM.
https://tools.ietf.org/html/draft-ioamteam-ippm-ioam-direct-export-00

The marking-based variation has inspired an implementation in SRv6 which was presented in 6MAN.
https://tools.ietf.org/html/draft-song-6man-srv6-pbt-01

We also presented in IPPM the work on using postcard or combining passport and postcard to support efficient multicast telemetry.
https://tools.ietf.org/html/draft-song-multicast-telemetry-01

We believe this informational draft introduces an important type of on-path telemetry technique.
The discussion on technique pros and cons can guide the corresponding  technique development, which is evidenced by the above examples.
Therefore, I request the working group to consider adoption of it as WG document.

Please let me know if you have any question about it. Thanks!

Best regards,
Haoyu

v2.23.0 | Report a Bug | By Email