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

Gyan Mishra <hayabusagsm@gmail.com> Fri, 02 July 2021 16:30 UTC

Return-Path: <hayabusagsm@gmail.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 50D663A2406 for <ippm@ietfa.amsl.com>; Fri, 2 Jul 2021 09:30:04 -0700 (PDT)
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_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twaUP24kga_K for <ippm@ietfa.amsl.com>; Fri, 2 Jul 2021 09:29:59 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED08C3A2403 for <ippm@ietf.org>; Fri, 2 Jul 2021 09:29:58 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id g22so10024071pgl.7 for <ippm@ietf.org>; Fri, 02 Jul 2021 09:29:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EMdlcl3LpfWl6bWqLA7z5yljCxpgLiKhMx/eicVWudg=; b=hFUnOAT32f17qM3EhW+oja7H+iUcch4Y8b9ZztJ/RueZaFTBTpt0Pr0BcytZCWP4+n aCwwaeRYBl54zYFqGRCgQ/ELJXiLdoSQfzDEMeLH+seQECIbItZWvFF3z8L5P7uygYFc EEIFU9AuQLaVPkbhZwUnRe6qpUG/oiB8FBz6WoM+XZ99WSdXBM+CLXGRnY13IaW0Onfa moeBg57SzDiGI+j/iBANLsqo1IzLHcJ6baO64ZUYCqQVJBVFVy6JGfgxTMZEqrs/mHCR 6xmThVCgnZCTcB2id2JJ63jdJsu2cCkytTE1E7/ixs5t9rYdyVyNKZ2zXE3ae31mJYpr RNaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EMdlcl3LpfWl6bWqLA7z5yljCxpgLiKhMx/eicVWudg=; b=UhAiS10GlcKhoNdiMpW63FjaOtWj+k9wl2A0o1Ipf95lH8tkacOInxw2D7G9k93xHS 5fuFBRGqjh65lmcMtY/6+RRjQpquTVven13oCWp4M+igIu3yDEoxqmuILFJjwrRYUhNa e7aby9SVjbWWTEeG2qJ6ONGnOILWS2++QnQaHGdqUZNxO1/cX55XG2MZgBIJnidsFKWy je53xwcExiElJhZddTgnDvdOimndmTats5ZusYACOqEzuUQeGdSno8VvWozaTsFYeb4o JVBKtGBR+JH57hTCGqlZISiGclguiHYD+rLBLrF3/pQvTWfHsUMVQF1FT3flnsdyvHbB zErQ==
X-Gm-Message-State: AOAM531a1rJ6+kuGmM8vB7R7mjkEoyMPPvOZyXPaQBUDdb7ys6J7myzF 6WgryFlLzSMLQo3b3EeL/s6PnKOlV6bB/2yaz3uC2inEejw=
X-Google-Smtp-Source: ABdhPJzZ6E7q5lWPBdiXqAzXCfWNVSP57ogXaXUlZNFz5IjYdt2ErBzJ+zokKVRIho3Hob29JQ0y6ZmaAkDUSd/+rMs=
X-Received: by 2002:a65:6210:: with SMTP id d16mr860929pgv.50.1625243397506; Fri, 02 Jul 2021 09:29:57 -0700 (PDT)
MIME-Version: 1.0
References: <956C2EA9-5703-4318-BD97-32EE60A4C011@apple.com> <202107021030004065160@zte.com.cn> <CABNhwV3UwLc=LoyezLkxrcXZUd2o=xeKaKEScYsOX_R5DKOfzg@mail.gmail.com>
In-Reply-To: <CABNhwV3UwLc=LoyezLkxrcXZUd2o=xeKaKEScYsOX_R5DKOfzg@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 2 Jul 2021 12:29:45 -0400
Message-ID: <CABNhwV2nV9J4dfcNhcLpQK9GGDzMy5y7iwiAMFqQN-1qiJxDjQ@mail.gmail.com>
To: gregory.mirsky@ztetx.com
Cc: ippm@ietf.org, tpauly=40apple.com@dmarc.ietf.org
Content-Type: multipart/related; boundary="00000000000061dd5f05c626770b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/MHyU5DSV0j6SRwcyuID9Cdetmxs>
Subject: Re: [ippm] Re-call for adoption: draft-xiao-ippm-ioam-conf-state
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: Fri, 02 Jul 2021 16:30:04 -0000

Dear Authors

Few questions.

The solution appear to be data plane agnostic and can apply to any data
plane.  Correct?

I would add SR to list of data planes or just say that the solution is data
plane agnostic applies to all data planes.

Also the recommended feasible method of deployment is to use PCE or PCE CC
 SDN centralized controller.

In the introduction towards the bottom below is stated.

“ The IOAM encapsulating node can acquire these IOAM capabilities info from
the centralized controller, through, e.g., NETCONF/YANG, PCEP, or BGP.”

As for centralized controller do you mean to say PCE or PCE CC-CCI object
PCE/SDN centralized controller.

You may want to state that the centralized controller option is the
recommended method and reasons why.

For IGP scenario would you need an IGP extension - much more complicated,
or I guess you could use ISIS instance or OSPF transport mode to carry the
metadata.  I think it maybe better to drop the IGP scenario.

Kind Regards

Gyan

On Fri, Jul 2, 2021 at 11:59 AM Gyan Mishra <hayabusagsm@gmail.com> wrote:

> Dear Authors
>
> I support WG adoption.
>
> This is a valuable telemetry tool in the operators toolbox for in-situ
> IOAM transit nodes data container  encap / decap within IOAM domain, with
> this extension to existing OAM echo-request/reply used in IPv6, MPLS, SFC,
> BIER, SR.
>
> Highly valuable to operators.
>
> Gyan
>
> On Thu, Jul 1, 2021 at 10:30 PM <gregory.mirsky@ztetx.com> wrote:
>
>> Hi Tommy and Ian,
>>
>> I support the adoption of this draft (as co-author).
>>
>>
>> Regards,
>>
>> Greg Mirsky
>>
>>
>> Sr. Standardization Expert
>> 预研标准部/有线研究院/有线产品经营部 Standard Preresearch Dept./Wireline Product R&D
>> Institute/Wireline Product Operation Division
>>
>>
>>
>> E: gregory.mirsky@ztetx.com
>> www.zte.com.cn
>> Original Mail
>> *Sender: *TommyPauly
>> *To: *IETF IPPM WG (ippm@ietf.org);
>> *Date: *2021/07/01 09:48
>> *Subject: **[ippm] Re-call for adoption: draft-xiao-ippm-ioam-conf-state*
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ippm
>>
>> Hello IPPM,
>>
>> Back in November, we had a call for adoption
>> for draft-xiao-ippm-ioam-conf-state that led to several questions, and we
>> asked for revised drafts.
>>
>> We’ve gotten several new versions, so Ian and I would like to re-start
>> the adoption call to get people’s input on the current version.
>>
>> https://datatracker.ietf.org/doc/html/draft-xiao-ippm-ioam-conf-state-10
>>
>> Please review the document and reply to the list to indicate if you
>> support adopting this work by *Thursday, July 15*.
>>
>> Best,
>> Tommy & Ian
>>
>>
>> _______________________________________________
>> ippm mailing list
>> ippm@ietf.org
>> https://www.ietf.org/mailman/listinfo/ippm
>>
> --
>
> <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*
>
> --

<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*