Re: [ippm] IOAM Direct Exporting Open Issue
Barak Gafni <gbarak@nvidia.com> Wed, 14 October 2020 07:04 UTC
Return-Path: <gbarak@nvidia.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 64D753A0EB3; Wed, 14 Oct 2020 00:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nvidia.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 hD2JCFXU4oSi; Wed, 14 Oct 2020 00:04:00 -0700 (PDT)
Received: from nat-hk.nvidia.com (nat-hk.nvidia.com [203.18.50.4]) (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 57FB33A0957; Wed, 14 Oct 2020 00:03:59 -0700 (PDT)
Received: from HKMAIL102.nvidia.com (Not Verified[10.18.92.77]) by nat-hk.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id <B5f86a2dd0000>; Wed, 14 Oct 2020 15:03:57 +0800
Received: from HKMAIL103.nvidia.com (10.18.16.12) by HKMAIL102.nvidia.com (10.18.16.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 14 Oct 2020 07:03:48 +0000
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (104.47.36.55) by HKMAIL103.nvidia.com (10.18.16.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 14 Oct 2020 07:03:47 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KC0ZaEZIZetRcjfUgbvfVMXC6gauH8el4XuosZcIwkchpw0AWF2wLcfXiI/u1TLl1T8LCT3rWz4NwqU3dhmbuqjmP7d7EshaFQ2d8kjuvXvsCYVBTDKKJmDLz0RpIpIhW4Sq1Unnie+5pWLc7nQngA08iSD+p/PA+BzpK+HLww7YBZ28Sm7hINE1pcoeSZKlglB0mCG5w/obRDUlEVyzQXdTno+IvTsL4Uq8ONjM5GDf4+cDVi1KIt5ugk6Z5LR3V6FkoTrHWqZiHvC5gxzFl/j4BwXK/qurzspdgiGgUgII8EOse8/7M1DRLmx5xMmJRfd+mSXnGh+ZTpuJDGD3hQ==
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=PNU0DWuN2eGNxYFvXfe6EK/HwUGb/uJSOkIkyTh458U=; b=jrK+uyxHUBBElHJZNSN6awW5bwc621dgJEicbdcLOHZvpec+mO7JzTGRVW7HZwR9+DWn20HmbIGN0tAeM45MCNvgGSSRblHa0mg32EDiGE+LLQfBd7qYgPPk6cI545rxKNyzsevzMaOeM4hy3P7UfI6Gti+WLEqarowgFz5Y1oFuhc0QhvzgRNezDbcEpHHWKBD7ggbMnZ2kgWdVfrsTf9ZVtu7eNRbbL6iei0coheQcXNG8065KuDgjnSU3ZvkSZrx81Fe2HzaLm+yOeaLodcDVEZNqKoT6qtMXke+N4v9moubSqwX4wCScFnvdk/GdfRHPyjf8yM4+tbvbzx1SJw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nvidia.com; dmarc=pass action=none header.from=nvidia.com; dkim=pass header.d=nvidia.com; arc=none
Received: from BYAPR12MB3446.namprd12.prod.outlook.com (2603:10b6:a03:d7::23) by BYAPR12MB3640.namprd12.prod.outlook.com (2603:10b6:a03:aa::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.29; Wed, 14 Oct 2020 07:03:45 +0000
Received: from BYAPR12MB3446.namprd12.prod.outlook.com ([fe80::60f7:3609:3b81:4a89]) by BYAPR12MB3446.namprd12.prod.outlook.com ([fe80::60f7:3609:3b81:4a89%3]) with mapi id 15.20.3477.020; Wed, 14 Oct 2020 07:03:45 +0000
From: Barak Gafni <gbarak@nvidia.com>
To: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>, Tommy Pauly <tpauly@apple.com>, Haoyu Song <haoyu.song@futurewei.com>
CC: Tal Mizrahi <tal.mizrahi.phd@gmail.com>, IPPM Chairs <ippm-chairs@ietf.org>, "draft-ietf-ippm-ioam-direct-export@ietf.org" <draft-ietf-ippm-ioam-direct-export@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>
Thread-Topic: IOAM Direct Exporting Open Issue
Thread-Index: AQHWi/GlSqW4RkTIpkK1WSKNa4NFEqlri0IAgBkPzYCAAAzdgIAAFayAgBISLwCAAAQtUA==
Date: Wed, 14 Oct 2020 07:03:37 +0000
Deferred-Delivery: Wed, 14 Oct 2020 07:02:55 +0000
Message-ID: <BYAPR12MB3446F6AB70078C4F0DC652DEB4050@BYAPR12MB3446.namprd12.prod.outlook.com>
References: <DM6PR13MB2762A3C2024A7CE1F4025F809A310@DM6PR13MB2762.namprd13.prod.outlook.com> <4941A7B7-7147-48C6-8A05-1D1572DFACA2@apple.com> <BYAPR11MB2584BB076D44E8F8B2D0C405DA050@BYAPR11MB2584.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB2584BB076D44E8F8B2D0C405DA050@BYAPR11MB2584.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=nvidia.com;
x-originating-ip: [2601:647:4a01:6160:5ce4:14ea:9397:2f5c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c572bb21-3ff8-4c22-dc7b-08d8700f4ace
x-ms-traffictypediagnostic: BYAPR12MB3640:
x-microsoft-antispam-prvs: <BYAPR12MB3640D8813B4BA7D1FC7D6821B4050@BYAPR12MB3640.namprd12.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: lNQ38jLGKcQDpNNYMOejoU4hBzSDrBDZjN/9R8g8TgLK2ZF++W/Y3v5s7zyXCzf4YEkosFp5h3MiwBflGUd4B0NcyAVvd5gtSXSwv8FIyZsgSdbi1clco9XaG2hOKjfNGymdktYaWziKeEAKMcEGucrfc/2fTtFn0kVuD9ox2qCBZjBCemULSwosb7MpFkfh4NrBJXOpwGd0+ZCChKLz21sA8uZjKRTSOF94QqV7X42CfPrSibbdyRh4opvxsY3KLtQC6vJqEI7pbgzxK8sEOdpmbBY3ENeXTKLplnU+6C/8fTEvuZfPCRSAHxWGpgMw6wqr3ZnSQ05qC0jRrbpTrcEp4//huhUVul+GKTLRCuEjk00OrfdkSO+Y/nX8h9UGKRVdS751fMtes2g4LSEB6Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR12MB3446.namprd12.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(396003)(376002)(136003)(39850400004)(346002)(5660300002)(45080400002)(83380400001)(966005)(55016002)(52536014)(186003)(6506007)(53546011)(8676002)(66946007)(8936002)(66476007)(66556008)(64756008)(76116006)(66446008)(7696005)(83080400001)(9686003)(478600001)(54906003)(110136005)(86362001)(2906002)(316002)(4326008)(6666004)(33656002)(71200400001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: X7Mw4v8eJdNrR2kuGoOmKKgGgMuGAz6Q8v27KvU0g4xKFD0nwMNGWbme74F8S1+qD1qBI+CHXfgSpJNh1CdnZFz5IwVj3Ha6LyQJ+ibQUUn9/nLvE5yIelhI6FjLEdttS+DvkdCUOA5WsJjUO48/2x5VRVYxmSDCUpLhfFBVyJpF+Vh3x9QbpsANaVlhvtkeqew3lfeNf60Zjn7/jVqATLdFaI1MiGWiwKzRibejniGrAKAaBvpPqs4FMmlOYIJ3lG8a+el6I1vG2pIf4ttSgOWbaDncj//AV7usmEzSXH5RgTY4ozo7XP6FjQ/P/hGyqEUsCTkkLknjRMR9XkdnE4EC1AP3oG9suM+s95XcODl9XfMPi9+BEIM/ohXHB9tFAVgYoUMEoyiAMdK8dErBm/ocpkhCfz7WRT5udZcEX4Y9dqF4tEoOJmlojfzTaCt+kwCjKIxQak2/NX+qsoEoLjvvUG9uoBCpvm2BE9I5QjYTxA7ebu4z0sH2wgTGn+YUtKV05Swsk4iRVd0N5Sg+eFdObNOWPONKJqR2sRRqb5lLsmLuo5mpFoR7R1q2Q9tNCxwZrB0loNLRziIqjS6Djt/d+v50V0uwjIX3fpZCqphVYALuNBaIETHeiypPlgsEw+js0FxSyk1nfMsCb7fLBHKcvqNOoT0uOtOZWL+i1Ed4PasPUBWR7aywlM8cumUta5NyYFuprAq3LZ3HGGhoxQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR12MB3446.namprd12.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c572bb21-3ff8-4c22-dc7b-08d8700f4ace
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2020 07:03:45.3527 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 43083d15-7273-40c1-b7db-39efd9ccc17a
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3P+zaBKYGkOTJsiqrZL0+BXpE6Tel4bKHSmla4oREq0wCNnYI5gJl4yu3a8Mi2J+cGCY7/WdFG5Zu124XPwNmw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR12MB3640
X-OriginatorOrg: Nvidia.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1602659037; bh=PNU0DWuN2eGNxYFvXfe6EK/HwUGb/uJSOkIkyTh458U=; h=ARC-Seal:ARC-Message-Signature:ARC-Authentication-Results:From:To: CC:Subject:Thread-Topic:Thread-Index:Date:Deferred-Delivery: Message-ID:References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:authentication-results: x-originating-ip:x-ms-publictraffictype: x-ms-office365-filtering-correlation-id:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-ms-oob-tlc-oobclassifiers: x-ms-exchange-senderadcheck:x-microsoft-antispam: x-microsoft-antispam-message-info:x-forefront-antispam-report: x-ms-exchange-antispam-messagedata:x-ms-exchange-transport-forked: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-AuthAs: X-MS-Exchange-CrossTenant-AuthSource: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-CrossTenant-mailboxtype: X-MS-Exchange-CrossTenant-userprincipalname: X-MS-Exchange-Transport-CrossTenantHeadersStamped:X-OriginatorOrg; b=ZTllTvgAP2A4fm8GqZmkW8+FUzL3N1U8gR0x1Y4JGbD6Coa/X9r8gFyE4qGl9s6ou wWI4dSeXyxsrVACrXDpLvZukJp3jfjzz9C0jGlNgJkHkVGc97gssMJhigC4pvXWC04 UMiiNq7nZN/k9Lq5gIclLjmTLn+pUbDDMnwjFmC+2Z6I/25xwHDaTSkxc89oBeTJRV Wyv++NUDBOzSbB1tAkPdW2D+2Iucxf4JlLVQKiBuwEXJ5RrTKlwlyrWy4OCd1uzZ0C 5sDsPZDEQrBuVxSHUbJ6Z1FJkMNgAHdXkfxOBLfh79eCYMbPm+WEd+F3YB+AGW/x81 Z/p6YTt9GYNhw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/dlGe-yrudBBy-y5jeOJJBCY_qps>
X-Mailman-Approved-At: Wed, 14 Oct 2020 06:37:05 -0700
Subject: Re: [ippm] IOAM Direct Exporting Open Issue
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: Wed, 14 Oct 2020 07:04:03 -0000
+1 My view is that if there is a need to discuss what a hop count is - the scope is the data draft where it has been defined, rather than DEX. Would you agree? Thanks, Barak -----Original Message----- From: Frank Brockners (fbrockne) <fbrockne@cisco.com> Sent: Tuesday, October 13, 2020 11:33 PM To: Tommy Pauly <tpauly@apple.com>; Haoyu Song <haoyu.song@futurewei.com> Cc: Tal Mizrahi <tal.mizrahi.phd@gmail.com>; IPPM Chairs <ippm-chairs@ietf.org>; draft-ietf-ippm-ioam-direct-export@ietf.org; IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org> Subject: RE: IOAM Direct Exporting Open Issue External email: Use caution opening links or attachments Cc'ing IPPM WG. IMHO it makes sense to tackle the question of how IOAM applies to L2 networks as a separate topic. Cheers, Frank > -----Original Message----- > From: Tommy Pauly <tpauly@apple.com> > Sent: Freitag, 2. Oktober 2020 20:35 > To: Haoyu Song <haoyu.song@futurewei.com> > Cc: Frank Brockners (fbrockne) <fbrockne@cisco.com>; Tal Mizrahi > <tal.mizrahi.phd@gmail.com>; IPPM Chairs <ippm-chairs@ietf.org>; > draft-ietf- ippm-ioam-direct-export@ietf.org > Subject: Re: IOAM Direct Exporting Open Issue > > If there are scenarios where the hop limit/TTL is not available, could > those not have a separate mechanism to define a hop limit? This DEX > alone could remain simple and without duplication for the L3 case, but > not preventing combining with another mechanism for L2? > > Tommy > > > On Oct 2, 2020, at 10:17 AM, Haoyu Song <haoyu.song@futurewei.com> > wrote: > > > > Hi Frank and Tommy, > > > > It's also clear that "Hop_count" is not semantically identical to > > "Hop_lim" (or > TTL) as specified in IOAM data. The most critical question is: what if > Hop_lim is not available at all (e.g., in L2 networks)? Then how can > we get such information? We need to add explanations in the draft how > to handle such a possibility, and how to get and interpret Hop_lim, if it exists. > > > > Best regards, > > Haoyu > > > > -----Original Message----- > > From: Frank Brockners (fbrockne) <fbrockne@cisco.com> > > Sent: Friday, October 2, 2020 9:31 AM > > To: Tommy Pauly <tpauly@apple.com>; Tal Mizrahi > > <tal.mizrahi.phd@gmail.com> > > Cc: IPPM Chairs <ippm-chairs@ietf.org>; > > draft-ietf-ippm-ioam-direct-export@ietf.org > > Subject: RE: IOAM Direct Exporting Open Issue > > > > Hi Tommy, > > > > as we all agree, one guiding principle in standards is to avoid > > reimplementation > of an already available functionality. This principle helps > implementors and avoid a proliferation of different options to > implement the same functionality. IMHO we're presented with such a case here. > > > > DEX was originally designed to avoid recording/updating the IOAM > > related > metadata in the packet as the packet traverses the network, but > instead have every transited node create and immediately export the OAM data of interest. > Let's call this "Vanilla DEX". > > > > If we add "hop count recording", we create a "Hybrid DEX" mode, in > > that we > record and update a hop-count field in the packet *and* have every > transited node create and immediately export the OAM data of interest. > The hop-count recording in this "Hybrid DEX" mode would just be a > re-implementation of a capability which we already have if we combine > "Vanilla DEX" with "IOAM tracing". > draft-ietf-ippm-ioam-direct-export-01 kind of states this in section 7 > - but IMHO we should make it really clear that we're talking about a re- implementation of an already existing capability. > > > > Maybe this context could help us to come to a conclusion on this topic. > > > > Cheers, Frank > > > >> -----Original Message----- > >> From: Tommy Pauly <tpauly@apple.com> > >> Sent: Mittwoch, 16. September 2020 19:48 > >> To: Tal Mizrahi <tal.mizrahi.phd@gmail.com> > >> Cc: IPPM Chairs <ippm-chairs@ietf.org>; > >> draft-ietf-ippm-ioam-direct- export@ietf.org > >> Subject: Re: IOAM Direct Exporting Open Issue > >> > >> Hi Tal, > >> > >> We may need to take some time on our upcoming IETF 109 agenda to > >> dedicate to resolving this if we can’t get it done before then. > >> > >> To get a sense from the authors, for either option, is there > >> someone who can’t live with that outcome? I can see the trade offs > >> either way, and I do think we should prescribe only one method. The > >> text lists the pros and cons—how do they weigh against one another? > >> > >> Tommy > >> > >>> On Sep 15, 2020, at 11:21 PM, Tal Mizrahi > >>> <tal.mizrahi.phd@gmail.com> > >> wrote: > >>> > >>> Dear Chairs, > >>> > >>> There were no responses to this email, probably since everyone who > >>> had comments about this open issue has already commented in the past. > >>> At this point we would like your help with proceeding to resolve this issue. > >>> > >>> Thanks, > >>> Tal. > >>> > >>> ---------- Forwarded message --------- > >>> From: Tal Mizrahi <tal.mizrahi.phd@gmail.com> > >>> Date: Sun, Aug 30, 2020 at 8:52 AM > >>> Subject: IOAM Direct Exporting Open Issue > >>> To: IETF IPPM WG <ippm@ietf.org> > >>> > >>> > >>> Hi, > >>> > >>> There is an open issue in the DEX draft about whether to include > >>> an explicit Hop Count field in the DEX header, or to rely on the > >>> existing Hop_Lim/Node_ID data field. > >>> > >>> Section 7 of the draft presents the pros and cons of each of these > >>> alternatives. This issue has also been discussed on the mailing > >>> list a couple of times, and on the last few IPPM meetings. > >>> > >>> We would like to encourage non-authors to express their opinion > >>> about which approach should be taken: (1) use an explicit Hop > >>> Count field, or (2) rely on the existing Hop_Lim/Node_ID data field. > >>> > >>> Cheers, > >>> Tal. > >>> > >>> > >>> Here is a link to the draft: > >>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2F > >>> da > >>> tatracker.ietf.org%2Fdoc%2Fdraft-ietf-ippm-ioam-direct-export%2F&a > >>> mp > >>> > ;data=02%7C01%7Chaoyu.song%40futurewei.com%7C2f840fbff5b34808bb3f08 > d > >>> > 866f0c247%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6373725315 > 361 > >>> > 39070&sdata=zOeIUtzXzqkyb5D9pdc1UgUP%2Bnpjc0aB0AHU0Df8Y1E%3D > & > >>> ;reserved=0 > >>> > >>> Section 7 of the draft, which presents the two alternatives is > >>> quoted here for convenience. > >>> > >>> Hop Limit / Hop Count: in order to help correlate and order the > >>> exported packets, it is possible to include a 1-octet Hop Count > >>> field in the DEX header (presumably by claiming some space from > >>> the Flags field). Its value starts from 0 at the encapsulating > >>> node and is incremented by each IOAM transit node that supports > >>> the DEX option. The Hop Count field value is also included in the > >>> exported packet. An alternative approach is to use the Hop_Lim/ > >>> Node_ID data field; if the IOAM-Trace-Type > >>> [I-D.ietf-ippm-ioam-data] has the Hop_Lim/Node_ID bit set, then > >>> exported packets include the Hop_Lim/Node_ID data field, which > >>> contains the TTL/Hop Limit value from a lower layer protocol. The > >>> main advantage of the Hop_Lim/Node_ID approach is that it provides > >>> information about the current hop count without requiring each > >>> transit node to modify the DEX option, thus simplifying the data > >>> plane functionality of Direct Exporting. The main advantage of > >>> the Hop Count approach is that it counts the number of IOAM- > >>> capable nodes without relying on the lower layer TTL, especially > >>> when the lower layer cannot prvide the accurate TTL information, > >>> e.g., Layer 2 Ethernet or hierarchical VPN. It also explicitly > >>> allows to detect a case where an IOAM-capable node fails to export > >>> packets. In order to facilitate the Hop Count approach it is > >>> possible to use a flag to indicate an optional Hop Count field, > >>> which enables to control the tradeoff. On one hand it addresses > >>> the use cases that the Hop_Lim/Node_ID cannot cover, and on the > >>> other hand it does not require transit switches to update the > >>> option if it is not supported or disabled. Further discussion is > >>> required about the tradeoff between the two alternatives.
- [ippm] IOAM Direct Exporting Open Issue Tal Mizrahi
- Re: [ippm] IOAM Direct Exporting Open Issue Frank Brockners (fbrockne)
- Re: [ippm] IOAM Direct Exporting Open Issue Barak Gafni
- Re: [ippm] IOAM Direct Exporting Open Issue MORTON, ALFRED C (AL)
- Re: [ippm] IOAM Direct Exporting Open Issue Haoyu Song
- Re: [ippm] IOAM Direct Exporting Open Issue Haoyu Song
- Re: [ippm] IOAM Direct Exporting Open Issue Tommy Pauly
- Re: [ippm] IOAM Direct Exporting Open Issue Barak Gafni
- Re: [ippm] IOAM Direct Exporting Open Issue Barak Gafni
- Re: [ippm] IOAM Direct Exporting Open Issue Tal Mizrahi
- Re: [ippm] IOAM Direct Exporting Open Issue Tommy Pauly
- Re: [ippm] IOAM Direct Exporting Open Issue Haoyu Song
- Re: [ippm] IOAM Direct Exporting Open Issue Tal Mizrahi
- Re: [ippm] IOAM Direct Exporting Open Issue Frank Brockners (fbrockne)
- Re: [ippm] IOAM Direct Exporting Open Issue Haoyu Song