Re: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state

"Chengli (Cheng Li)" <> Tue, 17 November 2020 09:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 799B63A0DBA; Tue, 17 Nov 2020 01:53:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2m2Perxwgou1; Tue, 17 Nov 2020 01:53:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9ADEB3A0C0E; Tue, 17 Nov 2020 01:53:44 -0800 (PST)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4Cb1SQ61rGz67F7S; Tue, 17 Nov 2020 17:52:06 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 17 Nov 2020 10:53:39 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Tue, 17 Nov 2020 10:53:39 +0100
Received: from ([]) by ([fe80::89ed:853e:30a9:2a79%31]) with mapi id 14.03.0487.000; Tue, 17 Nov 2020 17:53:30 +0800
From: "Chengli (Cheng Li)" <>
To: "Chengli (Cheng Li)" <>, "" <>
CC: "" <>, "" <>, "" <>, "" <>
Thread-Topic: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state
Thread-Index: AQHWvLkTkAn5jFR/UE+awxVQkZJh3KnMFSgw
Date: Tue, 17 Nov 2020 09:53:29 +0000
Message-ID: <>
References:,, <> <>
In-Reply-To: <>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB02CBEA49dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Nov 2020 09:53:48 -0000

I meant I don’t think we can detect the (Non Routing ) capabilities of a node in another domain. Sorry for the typo.

From: ippm [] On Behalf Of Chengli (Cheng Li)
Sent: Tuesday, November 17, 2020 4:09 PM
Subject: Re: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state

Hi Min,

That is also my understanding. IOAM is limited in a trusted domain.

But ICMP can be used in the global Internet? I don’t think we can detect the capabilities of a node in another node. Privacy and security will be a big challenge.

So personally I prefer IGP/BGP/BGP-LS or NETCONF/YANG way.


From:<> []
Sent: Tuesday, November 17, 2020 3:52 PM
To: Chengli (Cheng Li) <<>>
Subject: Re:[ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state

Hello Cheng,

I noticed that Frank has submitted an In-situ OAM deployment draft within OPSAWG, in section 3 of that draft it says:


IOAM is a network domain specific feature, with "network domain"

   being a set of network devices or entities within a single

   administration.  IOAM is not targeted for a deployment on the global

   Internet.  The part of the network which employs IOAM is referred to

   as the "IOAM-Domain".


To my understanding, the IOAM data is collected only within a trusted domain, of course, Frank can correct me if I'm wrong.

For your convenience, the link for this quoted draft is provided as below.

Best Regards,

Xiao Min
收件人:Frank Brockners (fbrockne);Tommy Pauly;IETF IPPM WG (<>);
抄送人:IPPM Chairs;
日 期 :2020年11月16日 17:28
主 题 :Re: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state
ippm mailing list<>
I have one simple question like I mentioned in the meeting: Is it secure to discover the non-routing capabilities info from the data plane?

For instance, a packet may travel several network domains, and the trusted scope is only within each domain. When we use ICMP Ping, we can get the non-routing info from other domains. Is it OK to do it?  I think we should consider more about security and privacy.

Furthermore, can we collect the IOAM data in multiple domain scenarios? Or only within a trusted domain?


From: ippm [] On Behalf OfFrank Brockners (fbrockne)
Sent: Monday, November 16, 2020 3:13 PM
To: Tommy Pauly <<>>; IETF IPPM WG (<>) <<>>
Cc: IPPM Chairs <<>>
Subject: Re: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state

Hello IPPM,

per what I mentioned during the IPPM WG meeting today, I don’t think we should adopt the document before we have a couple of key questions resolved:

* Why can’t we use Netconf/YANG (with the existing capabilities discovery process – a la RFC 6241) to retrieve the IOAM capabilities of IOAM nodes? E.g. the encapsulating node (as a NC client) could retrieve the IOAM capabilities from other IOAM nodes  (acting as a NC server). Plus there is already a YANG model in flight for IOAM (draft-zhou-ippm-ioam-yang-08). At a minimum I would have expected that the draft discusses why NC/YANG is not suitable for the scenario that the authors have in mind. The slides ( that were presented in the IPPM WG meeting today, mention “Changed from “IOAM Configuration Data” to “Enabled IOAM Capabilities” since the former is too associated with NETCONF/YANG.” IMHO we need a bit more than just wordsmithing.

* While the draft uses IOAM capabilities discovery as the use-case, in more general terms, it proposes to add management/ops capabilities to echo-request/reply protocols like ICMP, which is a much broader topic. The TLV structures which are proposed to be added to echo-requests and echo-replies could obviously be leveraged for other use-cases. Does the work really fit the scope of the IPPM WG?

Thanks, Frank

From: ippm <<>>On Behalf Of Tommy Pauly
Sent: Freitag, 30. Oktober 2020 19:46
To: IETF IPPM WG (<>) <<>>
Cc: IPPM Chairs <<>>
Subject: [ippm] Call for adoption: draft-xiao-ippm-ioam-conf-state

Hello IPPM,

This email starts a Working Group call for adoption for draft-xiao-ippm-ioam-conf-state. This document has been presented several times and discussed within the working group in the context of our overall IOAM work.

The document can be found here:<>

Please provide your feedback on these document, and state whether or not you believe the IPPM WG should adopt this work by replying to this email. Please provide your feedback by the start of the IETF 109 meeting week, on Monday, November 16.

Tommy & Ian