[spring] Progressing the PBT-M “Zero Overhead property” draft

Gyan Mishra <hayabusagsm@gmail.com> Wed, 14 December 2022 03:25 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5613EC14CF04; Tue, 13 Dec 2022 19:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level:
X-Spam-Status: No, score=-2.084 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2JNM8leCXWh; Tue, 13 Dec 2022 19:25:26 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46B2FC14F748; Tue, 13 Dec 2022 19:25:26 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id k3so724346qki.13; Tue, 13 Dec 2022 19:25:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=kcx7J8iEBwIxCAWsArc8mpPgyPqH4ECG24ZVpOHC+WU=; b=RThet8r8unvdO7sD3aLhPT3FPE2wjZgEyYcm2W8FT9363jCyIeWH7bMA/Mx5FRn7q5 j5ZIIVx23NqBjfso3zAcc6flUoG7MB14zF4X3melJUJFe0xcxGlvcdCYa1VD+gunZThn mINLOjDbZ4wqvhKavGvX7kspJQkoGi1QZRlS29/gUzeDIPfcoCYfiKlIzEhp4uAJC6v4 3DlVkS/hHDcmVAFkZ+phRKRAI0ruPSEK8DdH5+ka8bQENDKftpdb023ARu6QXaUsuZyD g0VySCLQ/ggCOSPB28N3sUcoe+AnVh2RZqL2HvdoHkP9jsylqibbJxHJRadXYvh/Pyvw vlsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=kcx7J8iEBwIxCAWsArc8mpPgyPqH4ECG24ZVpOHC+WU=; b=TA3tw1gEYfMW2z237JCt7sz+jw90WvPMaIqbU6iPf1+rMInYxJfCj2Ptgi724bWY5Y 8UNS68mxYDRQljxgyLxQeSYD1ltp3cayvpXlqGPOrnSpAQOGkgTKAWCDIFdyUgnDI+94 cnyjN7LQVLuvh2qhPnKiOHCbVriP6FmAbIleRNXYi7jYQ+aXt4RW0QsMLuno+oFM9tKv JOOHmislqkb/gChmcwnVoYvJAgZebyPJx2gfcSztdOhUMHZGGIxDOwXteZKq4vih3TwI JkL/tbAj7y2WCh+sWKfDYqTG30f7wdnSeWokV9Z1FtHRp5b0OjHz19e2/sH/LvfOWG95 tK4w==
X-Gm-Message-State: ANoB5pk4PmzJej1v9GMc+CqQzfwA+SKxGFnOItBhW1p88FFKLfSsjYP8 29S3/R5jZLUeFMNryvKnTjtVRMO0SCEUWfqJ+BV9S70G
X-Google-Smtp-Source: AA0mqf5N2CCfTsmYjxppnfqDOwz5UXwiLT8At0XsZoNcV24rJxp8lq6i76XDMlACaAbxcxo9qHLgiCRZ+3Gtm8V7r1I=
X-Received: by 2002:a05:620a:1657:b0:6ff:ab52:af3b with SMTP id c23-20020a05620a165700b006ffab52af3bmr198277qko.293.1670988324512; Tue, 13 Dec 2022 19:25:24 -0800 (PST)
MIME-Version: 1.0
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 13 Dec 2022 22:25:13 -0500
Message-ID: <CABNhwV38P-WV1jGJFgAGuCPws=kBLm9Ryhr0RdidebAAwVO_NQ@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>, SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081a85105efc14989"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/hd6hyQpYIkUIZkOQMLjV56_CW3k>
Subject: [spring] Progressing the PBT-M “Zero Overhead property” draft
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Dec 2022 03:25:30 -0000

Dear IPPM WG

RE: Progressing draft-song-ippm-postcard-based-telemetry-15

I would like to provide some important feedback related to the draft and
the critically of this draft to the industry at large especially with 5G
MNOs and future soon to be 6G and UPF F1 interface network slicing and IPPM
telemetry for Flex Algo latency constraint for ultra low latency path for
MEC services and end to end ultra low latency path instantiation.

My POV as well as others whom I have discussed the draft in and outside the
WG is that in order to make PBT viable and useful to operators to deploy,
the changes and improvements described in this draft are very important and
not just to the IPPM WG but to the industry at large namely for deployments
of Segment Routing both SR-MPLS and SRv6  and viability of IOAM in-situ
telemetry.

This is a huge issue today and PBT RFC 9326 is an attempt to solve the
issues with telemetry with Segment Routing but unfortunately that is not
enough and now with this draft, PBT based telemetry with Segment Routing
can finally come to fruition for all operators around the world wanting to
deploy Segment Routing.

I think with SR both SR-MPLS and SRv6 MSD and SR-MPLS Maximum readable
label depth issues and MPLS MNA extensibility discussed in the MPLS Open DT
meetings are important issues and considerations and with IOAM data with
DEX PBT solution can possibly resolves the issue with the export with zero
in-situ overhead philosophy and is a fabulous attempt but with a major
hitch.

To make RFC 9326 viable out the gate for any operators to implement,  we
really need the changes and updates to RFC 9326 described in this draft to
be progressed.

This draft should be and I think the authors of this draft as well as the
authors of RFC 9326 would as well agree that this draft should be Standards
Track and update the base specification RFC 9326 for PBT.

I believe that would be the best path forward for the WG.

All comments are welcome on this important topic.

Many Thanks

Gyan
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*