From nobody Fri Mar 18 09:33:48 2022 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3082A3A0D06; Fri, 18 Mar 2022 09:33:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.009 X-Spam-Level: X-Spam-Status: No, score=-2.009 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, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 z3OgWl3KaPcL; Fri, 18 Mar 2022 09:33:40 -0700 (PDT) Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2070c.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe59::70c]) (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 A45CA3A0D07; Fri, 18 Mar 2022 09:33:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U2rwBebAOlIQ9l3cXToaPZ1+gW+P13bG/50Zdkq35D6CHSk6MJjbBQr3ckKsr4P0NuhUDXUC1djsM4MAJvkSjYfEBIblPHQY+eQ3O6A4D++cuM13kj3akaFcWgdbotSE1hM+ZUnZVHvIijinEgwIeXIHEjWpEtxgGiSmmAOvbJIh0l/ei9PU/Bd6NLViP9eousZzGrPduQzNJ0ZeuwDnULbTcq7VaOiaBHWBqy9i6IfA3nHQs25+R/FCUlPCnwN3sCoFHb55VtBX5LHskySvXLRsgaw5FqzNmeUYMGbWeMszAeyBPGIgwweMB/utoj0apJqDXCx+9Co8GYAQQN3ufQ== 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=XdFqY9IzD0ZXJ9FsnZVUiaa6ul8vYIEDHxgAZZDNyzs=; b=oR4FpTlklprcPDypSzBewBKeUROw1QgVSXr021s0bLu8I4jfhxazGTRpdKtWImHEHQvF1hHkN+T0VChHy7qhKhYQ5heEnmO7rwZwTvQYXhFZWzExeyoHfgohrImKNHuu4IusKB/oJerVJp4aE8lG86XxDri7+BprC7L1Z8lCYNYingSD/wiS6kkPSXcACJetPmuaTXJXPwHJToYD+jqCWIZPPv6QySk2vT0nmV2MUWZ82VZeZEiM49zCWmsxY7EGBISmojrQsMACYOu6CWlqukNGFGo6101UcAI9U7+kRXxfk3sQEIrNvnZuAJSCY11Q9hCoB6bCN22FYcrWuUhiFg== 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=XdFqY9IzD0ZXJ9FsnZVUiaa6ul8vYIEDHxgAZZDNyzs=; b=oiqkWHRmdn9QOVSmxVLVmFYDnRJqWmbjl9N8oDM7V3ER1fR8L4ApBR4immtE9WaWy75SGBwU1TMezCxDyGo467vMudq0xRRVG2cIDw/g7tyDPpPtkQCoivy5bfjMfTrZTL+K0sJ8tFSl5sO5N9NMIdBDMsz6XLA4fsa6iE6SY54= Received: from BY3PR13MB4787.namprd13.prod.outlook.com (2603:10b6:a03:357::13) by BY5PR13MB4372.namprd13.prod.outlook.com (2603:10b6:a03:1f5::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5102.8; Fri, 18 Mar 2022 16:33:31 +0000 Received: from BY3PR13MB4787.namprd13.prod.outlook.com ([fe80::9435:617d:d2c3:4c3d]) by BY3PR13MB4787.namprd13.prod.outlook.com ([fe80::9435:617d:d2c3:4c3d%6]) with mapi id 15.20.5102.008; Fri, 18 Mar 2022 16:33:30 +0000 From: Haoyu Song To: Greg Mirsky , "Jeffrey (Zhaohui) Zhang" CC: "draft-xzlnp-bier-ioam@ietf.org" , "bier@ietf.org" Thread-Topic: [Bier] A comment about draft-xzlnp-bier-ioam Thread-Index: Adg6xfU8UxzNoslpTIerKIi728m8bgAHP96AAACL1YA= Date: Fri, 18 Mar 2022 16:33:30 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=futurewei.com; x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 14536f17-e1cb-45e6-c08d-08da08fd09be x-ms-traffictypediagnostic: BY5PR13MB4372:EE_ x-ms-exchange-atpmessageproperties: SA|SL x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: Hretpy6WUOnKKCrZhsYzAoAZQZLlrJDlmrnncOeBC8M9Ueo6sAgayHVwT1uOBehn05qjzPbRYTU/qGq8A3/KeDczLsjlhEex+4rwcRvdAQFOUTllnM+WGaDLW09gjDLPdGq+PjCpUarZmSfDdCr5wuzqQILuk3w/Wg8kRKb63La50AIooav244WIg0HLa0Wb2Vjy0HX7m0hzqkH+lm2XEWVn14vKZIEeIZ99MTMKIKDV0MQzEF+3rAUMikNWyFIvbHKa71I1sPXf2iMBnAkZwI/cocld4/eqAQe0q+XY2Wb6yiMjEBvKTDzFvXi5NFaQgQOzjqpyehsMHW5fs6K/Y2LkkNJyVz3XRXs5tPzqkgOyVPcpqcghrQJlBJZXvDp9CjG0s8hkWpj51MKUPMDolrmcgL6vSvMVcUiyN1Ob0FwOZZlkNOEs4IxQFc9ki0CYCWwy52r3ojbaoMf8aB893PjB2sT5viWm9aLeZQIdcMZhEC9qhAMV4nsfwUIq9AjPI48sRu8f0bmgthfqB6NTJn7nVj3V+U+5Y0Nng4DQ0CzNawGBI9QvXpWHqnK5g/IbeLHTO8WwQU0VM62YbLG+/z5NVtzgiV4iH5xE8WLsZimxuk7Ja2aa+CVyKgWQaKFEViT/neXEysJEwjsT41CBe/ueQidWjnjmvvGfxfUUxLKbTps9WZKs40wsrm3CxuXpYa9uXdTzVFYiaZNsJjQoVm7cWlehnJpsk8VYRxQjDBinpBwsIQUu3oSXpptexgnB7u/p7YPNX2PG1DHdMF9iJbfrIa/pfQ45Fwu8WmlesNqS5VIogQzxfM1ErtfLrZ6Pf1yGuY45ByJCExnW9yjflg== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY3PR13MB4787.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(38070700005)(5660300002)(122000001)(4326008)(44832011)(8936002)(52536014)(66556008)(76116006)(66946007)(8676002)(66446008)(64756008)(66476007)(166002)(86362001)(54906003)(316002)(33656002)(966005)(83380400001)(508600001)(110136005)(186003)(26005)(55016003)(2906002)(38100700002)(53546011)(6506007)(7696005)(71200400001)(9686003); DIR:OUT; SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?6He4U2mRdK1cn8CojK7myqNsEqNmmjr/spdVKIpoIzmaJHtRFrfr/ISJoVLr?= =?us-ascii?Q?U7px5ePRx9J973FtAHicbtTUN9wie4fcQDKbYz8K43vRc9jxK32ZDLcrHagW?= =?us-ascii?Q?nSi2zITgHnOywy3ZB+vVbl4zNuizEbPlq6tgJkHx/thBVlW3jdKWMSBjnmFe?= =?us-ascii?Q?pyj42/Ppc0EVL6MnrhazuZiMGjP329wS518cZXeyir2GI+OV49RFKriXQu6+?= =?us-ascii?Q?fs+h25CFF/1ppkbuq1rdcl66LQHz8BOial2PEcDSdakFCOozW4qayDkyX9bb?= =?us-ascii?Q?nF81ykFHepT3F+e+dT+0xocwhlmlHRXahexG+lT4AC6pv9PtfqtsHD+fHE8X?= =?us-ascii?Q?bllV6wCIM1Yw2Tj3WuFPT3BDSG8i8JLoW4eDy+46ZVARkqSLk2NVBD3bJxrv?= =?us-ascii?Q?gYHJY9d2a1VethSUsxSlX5bDJXOeqnel8h7WeCPf5CeF0zpAw0MadxBp70AO?= =?us-ascii?Q?qdmFi6YQew+J9nvidNLNGr0tdUo+KaTNIochE7cG2UtYqWVFoY5L7Mp7VpP6?= =?us-ascii?Q?79OQSZTgF8oeHg+e3eMmJlzhN8wK/bHufKhErx/qKxjHCGsIR4kj6wHynSi4?= =?us-ascii?Q?5cEBcUiDgSDgnoz2a6xkaWvLZCsvwJbWXCCKqRl7HIgWJNuvLVqBvKyrnCtK?= =?us-ascii?Q?FplK3HEeOCYUUUu9CwRk000f3xoaSoEeyHrs6nS23FXl7VXpunaDj7qAeVtv?= =?us-ascii?Q?Xl2LQ7ymd+CjYDjxaIfJU/K697VFgaXnUXY1JolQrN5nlOUxDCajM6omfzCK?= =?us-ascii?Q?589f22LSdU5tkWMp68J0wTnYbrSXIoDesLuN7PvmpT+dEAHx53IhXkpem3a/?= =?us-ascii?Q?BAxAiXT0yiMr+qw4iPC5Da3Urpz1K2sCht07Qg9GlcFJiYvdRnXtTjdTjKaJ?= =?us-ascii?Q?eZMWf5iN/t3eOFGiwmoch1w8IGJ7VX+ncCPpXMpXidPHVUc/rWShy5WoU/fa?= =?us-ascii?Q?QzP2HPkJ/FfcS3oVnQasg9TNKr2AnyKQsEq01FYQJOY4EUCVnaXsmix8HLCB?= =?us-ascii?Q?FUX/JDxIWReJnZZ4ggO+eFzYZCRY+pvHHT2+unR//n9MUccPVy8krYldPCzn?= =?us-ascii?Q?d6DotiQs8BAzOKDcnyPyATmvd2+25LDc1msV3SN/Rjlq0fuW/slDuL8BvDQM?= =?us-ascii?Q?VN+K7yOI1NC/Iy6nF/GoE+4u/WsUsMjHxRIrOM8U0ajveNB9Tn++ptdprUEW?= =?us-ascii?Q?VyhArzS+0yFI9uutgL9m8XY3PePwA818qJQD1HFLWQTd5cAaMYynNXo0Vuqz?= =?us-ascii?Q?/gyx0dtgYL/gxw7RokJ4Sph9cBcCdANNgRaAEWKytAzYMuyuruJsiwsR8cSu?= =?us-ascii?Q?SDfb53GpHBJx061qJKgH1fIfn0B7tswIEeMtbE7kNvyIs3NFobRCpXp8fVOc?= =?us-ascii?Q?WbySqnc0coOxI7Lbwk7lp9miOQEt9jI7XXc0U0qcCHWs6BHEoPRjyy2GCQnT?= =?us-ascii?Q?RXV0/zlj5nF6upo4rb6Kk+aHw2UZS3Ze?= Content-Type: multipart/alternative; boundary="_000_BY3PR13MB4787561122F140264682E0839A139BY3PR13MB4787namp_" MIME-Version: 1.0 X-OriginatorOrg: Futurewei.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BY3PR13MB4787.namprd13.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 14536f17-e1cb-45e6-c08d-08da08fd09be X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Mar 2022 16:33:30.6778 (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: 1UJ6Gm6yP11RMBbcd5RvmpAIc90mPIZgULIimI6uTZrhKyHf6THo+JHmFgQnlfwbbZpSY7CyCD4+wyXRtP3HWA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB4372 Archived-At: Subject: Re: [Bier] A comment about draft-xzlnp-bier-ioam X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Mar 2022 16:33:45 -0000 --_000_BY3PR13MB4787561122F140264682E0839A139BY3PR13MB4787namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I agree with the first point made by Greg. It is inefficient to support the= IOAM trace in multicast scenario due to unnecessary data duplication. In o= ur draft we have discussed the issues and provided solutions, which are als= o applicable to BIER (sec 5.3). https://datatracker.ietf.org/doc/html/draft-ietf-mboned-multicast-telemetry= -02 Thanks, Haoyu From: BIER On Behalf Of Greg Mirsky Sent: Friday, March 18, 2022 9:12 AM To: Jeffrey (Zhaohui) Zhang Cc: draft-xzlnp-bier-ioam@ietf.org; bier@ietf.org Subject: Re: [Bier] A comment about draft-xzlnp-bier-ioam Thank you for bringing this work to the discussion. I have read the draft and got several comments: * the IOAM mechanism described in draft-ietf-ippm-ioam-data appears to = be better suited for p2p flows. When applied in a multicast network, IOAM r= esults in unnecessary replication of IOAM data recorded upstream. This can = be avoided by separating the process of generating telemetry information on= a node according to the profile in the IOAM header from transporting that = information to a collector for processing. That can be achieved using the I= OAM Direct Export mode of IOAM tracing, the Hybrid Two-step protocol, or any oth= er means of transportation. * I suggest updating Figure 1. As mentioned above, there are other meth= ods of transporting IOAM data rather than in the trigger packet immediately= following the IOAM Option header. I think that the right tag for the field= would be "IOAM Option and Optional Data Space". Alternatively, the figure = may display IOAM Option and IOAM Data Space fields separately, noting that = the latter is optional. Regards, Greg On Fri, Mar 18, 2022 at 5:56 AM Jeffrey (Zhaohui) Zhang > wrote: Hi, For IOAM data in BIER, I want to point out that we should use a generic hea= der format that can be used for BIER/MPLS/IPv6. The same extension mechanis= m can be used for other purposes like fragmentation/security, etc.. This was discussed in https://www.ietf.org/archive/id/draft-zzhang-intarea-= generic-delivery-functions-02.txt, and was mentioned in slid= e #6 of https://datatracker.ietf.org/meeting/112/materials/slides-112-bier-= 03-bier-slicing-and-differentiation-00 = in IETF112 BIER session. Thanks. Jeffrey Juniper Business Use Only _______________________________________________ BIER mailing list BIER@ietf.org https://www.ietf.org/mailman/listinfo/bier --_000_BY3PR13MB4787561122F140264682E0839A139BY3PR13MB4787namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I agree with the first point made by Greg. It is ine= fficient to support the IOAM trace in multicast scenario due to unnecessary= data duplication. In our draft we have discussed the issues and provided s= olutions, which are also applicable to BIER (sec 5.3).

https://datatracker.ietf.org/doc/htm= l/draft-ietf-mboned-multicast-telemetry-02

 

Thanks,

Haoyu

 

From: BIER <bier-bounces@ietf.org> O= n Behalf Of Greg Mirsky
Sent: Friday, March 18, 2022 9:12 AM
To: Jeffrey (Zhaohui) Zhang <zzhang=3D40juniper.net@dmarc.ietf.or= g>
Cc: draft-xzlnp-bier-ioam@ietf.org; bier@ietf.org
Subject: Re: [Bier] A comment about draft-xzlnp-bier-ioam=

 

Thank you for bringing this work to the discussion.<= o:p>

I have read the draft and got several comments:=

  • the IOAM mechanism described in draft-ietf-ippm-ioam-data appears to be bet= ter suited for p2p flows. When applied in a multicast network, IOAM results= in unnecessary replication of IOAM data recorded upstream. This can be avo= ided by separating the process of generating telemetry information on a node according to the profile in the= IOAM header from transporting that information to a collector for processi= ng. That can be achieved using the IOAM Direct Export mode of IOAM tracing, the Hybrid Two-step protocol, or any other means of transportation.
  • I suggest updating Figure 1. As mentioned above, there are other methods of= transporting IOAM data rather than in the trigger packet immediately follo= wing the IOAM Option header. I think that the right tag for the field would= be "IOAM Option and Optional Data Space". Alternatively, the figure may display IOAM Option and IOAM Da= ta Space fields separately, noting that the latter is optional.<= /li>

Regards,

Greg

 

On Fri, Mar 18, 2022 at 5:56 AM Jeffrey (Zhaohui) Zh= ang <zzhang=3D40juniper.net@dmarc.ietf.org> wrote:

Hi,

For IOAM data in BIER, I want to point out that we should use a generic hea= der format that can be used for BIER/MPLS/IPv6. The same extension mechanis= m can be used for other purposes like fragmentation/security, etc..

This was discussed in https://www.ietf.org/archive/id/draft-zzhang-intarea-generic-delivery-funct= ions-02.txt, and was mentioned in slide #6 of https://datatracker.ietf.org/meeting/112/materials/slides-112-bier-03-bier-= slicing-and-differentiation-00 in IETF112 BIER session.

Thanks.

Jeffrey

Juniper Business Use Only

_______________________________________________
BIER mailing list
BIER@ietf.org
https://www.ietf.org/mailman/listinfo/bier

--_000_BY3PR13MB4787561122F140264682E0839A139BY3PR13MB4787namp_--