Re: [ippm] FW: New Version Notification for draft-song-ippm-postcard-based-telemetry-11.txt

[Gyan Mishra <[e-mail]>]

Dear IPPM WG

I have reviewed the draft and as the draft has matured throughout its
updates I believe is ready for adoption.

The draft provides an important optimization to postcard based telemetry
where in-situ on path IOAM data is not carried in the user data packets and
carried separately as postcards sent to the collector.

IOAM DEX Optimization

https://datatracker.ietf.org/doc/draft-ietf-ippm-ioam-direct-export/

The MPLS DT has been investigating extensibility of the MPLS data plane to
using SPL labels for IOAM trace  capabilities which has significant
importance  for gathering telemetry data for operators.

The challenge has been to continue to support existing MPLS architecture,
backwards compatibility as well as not excessively increase the depth of
the MPLS label stack with a variety of functional SPL labels snd NAI
indicators similar in concept to the MPLS Entropy label ELI, EL added to
the label stack, as well as the MPLS extension headers being ISD ( In
Stack) or PSD (Post Stack).

A new draft was published recently by Robert Raszuk related to reference
augmentation forwarding.

https://datatracker.ietf.org/doc/html/draft-raszuk-mpls-raf-fwk-00

This draft keeps the ISD and PSD stack depth in check by using an
alternative means of carrying the IOAM data using IGP  control plane
extension TLV to carry the data to provide In-Situ IOAM on path telemetry
using IOAM DEX Postcard based telemetry.

This draft provides a critical optimization that fills the gaps with IOAM
DEX related to packet marking triggers using existing mechanisms as well as
flow path discovery mechanisms to avoid configuration of on path data plane
node complexity.

The MPLS DT may come up with other alternatives to carry IOAM data such as
the IGP extension mentioned and maybe other solutions, and will heavily
rely on the IOAM DEX Postcard based solution.

The optimizations described herein in this draft are that much more
important for the realization for operators of a postcard based IOAM on
path telemetry solution.

Thank you

Gyan

On Mon, Nov 15, 2021 at 4:31 PM Haoyu Song <[e-mail]> wrote:

> Hi IPPM WG and chairs,
>
> According to Tommy's suggestion in the meeting, we acknowledge that our
> approach is in the same vein of the high level IOAM scheme and
> complementary with the two other approaches which are currently on the
> standard track. In this newly submitted revision, we rename the approach as
> IOAM Marking, making it a member of the family of IOAM telemetry technique.
> Please review the draft and we request the WG consider to adopt it as well.
> Any questions and suggestions are welcome. Thanks!
>
> Best regards,
> Haoyu
>
> -----Original Message-----
> From: [e-mail] <[e-mail]>
> Sent: Monday, November 15, 2021 1:20 PM
> To: Ahmed Abdelsalam <[e-mail]>; Clarence Filsfils <
> [e-mail]>; Greg Mirsky <[e-mail]>; Haoyu Song <
> [e-mail]>; Jongyoon Shin <[e-mail]>; Kyungtae
> Lee <[e-mail]>; Tianran Zhou <[e-mail]>;
> Zhenbin Li <[e-mail]>
> Subject: New Version Notification for
> draft-song-ippm-postcard-based-telemetry-11.txt
>
>
> A new version of I-D, draft-song-ippm-postcard-based-telemetry-11.txt
> has been successfully submitted by Haoyu Song and posted to the IETF
> repository.
>
> Name:           draft-song-ippm-postcard-based-telemetry
> Revision:       11
> Title:          In-Situ OAM Marking-based Direct Export
> Document date:  2021-11-15
> Group:          Individual Submission
> Pages:          12
> URL:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-song-ippm-postcard-based-telemetry-11.txt&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C89fc113339d6481eeeeb08d9a87dabdc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637726080011171689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=EWzRNNy9iO2jsgXVHKVguFtsd3vPQh14oi1sOKKCpyU%3D&amp;reserved=0
> Status:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-song-ippm-postcard-based-telemetry%2F&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C89fc113339d6481eeeeb08d9a87dabdc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637726080011171689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=58N7ojCgFm6Pa0qJUAYrvjiI77laih7E0iK7WCveC34%3D&amp;reserved=0
> Htmlized:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-song-ippm-postcard-based-telemetry&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C89fc113339d6481eeeeb08d9a87dabdc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637726080011171689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=ha26YitmYaP2weLrP6LVM6muFlKqcgLCYqug5gfgobI%3D&amp;reserved=0
> Diff:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfcdiff%3Furl2%3Ddraft-song-ippm-postcard-based-telemetry-11&amp;data=04%7C01%7Chaoyu.song%40futurewei.com%7C89fc113339d6481eeeeb08d9a87dabdc%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637726080011171689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=wIn6PZQKXIUvJHxKhVvEPm7t3lYZ0b3tGo8fDWpn2cg%3D&amp;reserved=0
>
> Abstract:
>    The document describes a packet-marking variation of the IOAM DEX
>    option, referred to as IOAM Marking.  Similar to IOAM DEX, IOAM
>    Marking does not carry the telemetry data in user packets but send
>    the telemetry data through a dedicated packet.  Unlike IOAM DEX, IOAM
>    Marking does not require an extra instruction header.  IOAM Marking
>    raises some unique issues that need to be considered.  This document
>    formally describes the high level scheme and cover the common
>    requirements and issues when applying IOAM Marking in different
>    networks.  IOAM Marking is complementary to the other on-path
>    telemetry schemes such as IOAM trace and E2E options.
>
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> ippm mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ippm
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [e-mail] <[e-mail]>*



*M 301 502-1347*