Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt

I do not see any overlap here. 
All the information, the usage and the extended protocol are quite different.

Tianran

-----Original Message-----
From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of xiao.min2@zte.com.cn
Sent: Thursday, June 30, 2022 10:22 AM
To: shares@ndzh.com
Cc: ippm@ietf.org
Subject: Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022)

Hi Susan,

Thank you for the response.
Please see inline my comments with [XM]>>>.

Best Regards,
Xiao Min
------------------Original------------------
From: SusanHares <shares@ndzh.com>
To: 肖敏10093570;
Cc: ippm@ietf.org <ippm@ietf.org>;
Date: 2022年06月30日 05:28
Subject: RE: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022) " _ue_custom_node_="true">
Xiao:
Thank you for your feedback regarding this draft.
I need clarification on your feedback.
The introduction of draft-wang-idr-bgp-ifit-capabilities-05.txt
states IFIT is an abbreviation used by their draft as denoted in their abstract:
“This document defines extensions to BGP [RFC4271] to advertise the In-situ Flow Information Telemetry (IFIT) capabilities.”
Since this abbreviation is shared with:
draft-ietf-idr-sr-policy-ifit-03 (ready for WG LC) in their abstract:
“In-situ Flow Information Telemetry
(IFIT) refers to network OAM data plane on-path telemetry techniques, in particular the most popular are In-situ OAM (IOAM) and Alternate Marking.”
Are you objecting to their abbreviation or the terms behind the abbreviation?
[XM]>>> Since I started work in IPPM around 2017, both Alternate Marking and In-situ OAM were already there and I've been used to them. If the IPPM WG decides to introduce a new/second term to scope Alternate Marking and/or In-situ OAM, that's fine to me. However, I don't believe it's the common practice to put a new/second term to IPPM techniques from the outside of IPPM.
2.  Would you please provide additional details on the overlap between draft-wang-idr-bgp-ifit-cpabilities-05.txt and draft-ietf-ippm-ioam-conf-state.
[XM]>>> As I said, the term IFIT brings some confusion to me, in IPPM, Alternate Marking and In-situ OAM are targeted by separate documents. If I understand draft-wang-idr-bgp-ifit-cpabilities-05 correctly, this document covers Capabilities Discovery for both Alternate Marking and In-situ OAM, only edge to edge. As a comparison, draft-ietf-ippm-ioam-conf-state-03 covers Capabilities Discovery for In-situ OAM (if necessary, the same mechanism can be used for Alternate Marking as well), both edge to edge and hop by hop.
Thank you Susan Hares

From: xiao.min2@zte.com.cn <xiao.min2@zte.com.cn>
Sent: Wednesday, June 29, 2022 5:06 AM
To: Susan Hares <shares@ndzh.com>
Cc: ippm@ietf.org
Subject: Re: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022) Hi Susan, Thank you for this notice, very helpful.
I have two concerns as follow:
1. As far as I know, iFIT is not a standardized term defined in any IPPM RFC or WG draft, however iFIT includes Alternate Marking and In-situ OAM which both are defined in IPPM. I'm not sure it's appropriate, that looks out of order to  me. The right order IMHO is to define iFIT in IPPM first (if necessary), and then to define protocol extensions (e.g. BGP extensions) to support iFIT.
2. In IPPM there is draft-ietf-ippm-ioam-conf-state that achieves the similar function intended by draft-wang-idr-ifit-capabilities, the two documents looks overlapping to some extent.
Best Regards,
Xiao Min
------------------Original------------------
From: SusanHares <shares@ndzh.com>
To: ippm@ietf.org <ippm@ietf.org>;
Date: 2022年06月24日 23:29
Subject: [ippm] IDR adoption of draft-wang-idr-bgp-ifit-cpabilities-05.txt - Request for input (6/24 to 7/8/2022) _______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
Marcus, Tommy and ippm WG:
The IDR WG would like your feedback on two drafts in IDR:
1. draft-ietf-idr-sr-policy-ifit-03.txt – The IDR WG is planning WG LC on this draft in August.
2. draft-wang-idr-ifit-capabilities-05.tt – The IDR WG has consensus on adopting this draft.
Please let us know if you have any concerns regarding these drafts.
We note that these drafts reference:
1) draft-ietf-6man-ipv6-alt-mark
2) draft-ietf-ippm-ioam-data
3) draft-ietf-ippm-ioam-direct-export
4) draft-ietf-ippm-ioam-flags
5) draft-ietf-ippm-ioam-ipv6-options
Please let me know if you have any questions regarding these two drafts.
I am one of the IDR WG co-chairs and the shepherd for these two drafts.
You can reply to this thread or provide information to your WG chairs.
Cheers, Susan Hares

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