Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)

Gyan Mishra <hayabusagsm@gmail.com> Fri, 18 March 2022 05:03 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C04D33A1842 for <idr@ietfa.amsl.com>; Thu, 17 Mar 2022 22:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-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 KK20Nl6gvVdb for <idr@ietfa.amsl.com>; Thu, 17 Mar 2022 22:03:11 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 662183A1841 for <idr@ietf.org>; Thu, 17 Mar 2022 22:03:11 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id v4so6633887pjh.2 for <idr@ietf.org>; Thu, 17 Mar 2022 22:03:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=J6wdh42fFo2HiKF3L0aPqbFyWug/FM50NtU8Ub0RMS4=; b=iFV+Nl+0MhLRVGnXH8fc3H1g0TrgAwwNjxRUjDE/cCyJHYOnCSWmvdyXXuTKa5/Ksn bZ440SGL8YrZml9wjFF0Q6s7iuvxofnYo4vNirjxHL+rN+ZrWu7bcpH7KxtLNG8fe/Bt xvuNavMXbeZWEWRWFLtKzeCN/CPkdbKBz3RzdHE/CT99zfzLN7Sxnxtlo4HhgoLm0BGS iT5y+CHc7OzgLxomMAmsQ+QxChd0XTA28isBIsXXLM1Ak1qr1EoJqQ2Vf/7ZQZwddO9m rO208FoNOFsL5d8p6mdheNigEqjm2Ti9+cxj5mrjhaWrzaLshZ01/9WrKX3Y3dxFRDYO 10HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=J6wdh42fFo2HiKF3L0aPqbFyWug/FM50NtU8Ub0RMS4=; b=dbCSnMoYdztNvLXO2wORjQf33rj1cfn3ioTu6HnQU7UfsQOoe5Ccq+2PFl4gvSTwuA 4uAjBTLBnxg2MJAgE22gN4fBF20zTF+Ch1k3HIkZ5IIv47iCwv4wxJWJvodExTIHS2M7 68emQ1zluz9fdm+3sRlyoqUDoZv0bXo4Yt997Bfjra/QoFUeseJDE7ziA3x5kEGosa5v HqSdzOzZFmSpRfTEuJfgO8Q+fGbsd0HmdS0UHLV8jX7yGgsYKF8qWIGA3KV8OehcJwQ5 RIx3AWmk1LUmvTEjGe7n7e/H4SlH+BufqUcLBsumG3ybzQ8n8p2SpU8cedYaans2fPMu n+NQ==
X-Gm-Message-State: AOAM531vSBvwe/9119TuUJaWuAPSg5pjcdl6sx92KVs96tfK4GJ/7V6y kznJfZc2gm6U/Y0ryL4knCmcsAttcXsbHHeI2kdHUQtN
X-Google-Smtp-Source: ABdhPJwHCfmXGYwY5DgO6FynU3s0xfwPx0Wiu66jT2+OxHqmAp7F+6+TYBJ6NoA4wKZKELPYdQQztcBCWEvqAhqh+hs=
X-Received: by 2002:a17:902:cccc:b0:14e:e89c:c669 with SMTP id z12-20020a170902cccc00b0014ee89cc669mr8309294ple.58.1647579789983; Thu, 17 Mar 2022 22:03:09 -0700 (PDT)
MIME-Version: 1.0
References: <00ca01d8348c$8b05d270$a1117750$@ndzh.com>
In-Reply-To: <00ca01d8348c$8b05d270$a1117750$@ndzh.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 18 Mar 2022 01:02:58 -0400
Message-ID: <CABNhwV2BXK9vf0tvoYprd8aYdFOe_6JHWAD2tmztC=0N9mYRpA@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf.org
Content-Type: multipart/alternative; boundary="0000000000001f04ef05da77102a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/srbqT292ofRn26lWkK93ES7Zjig>
Subject: Re: [Idr] Adoption call for draft-wang-idr-bgp-ifit-capabilities-04 (3/10 to 3/24)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2022 05:03:18 -0000

Hi Sue & WG

I Support WG adoption.

I believe this draft will help operators in distribution of IFIT telemetry
 capabilities from tail to head end nodes.  The draft needs to describe
more clearly what the new extended communities are to be used for.  Is is
not clear the use.

The draft iFIT SR policy draft below is completely independent of this
draft and is used to distribute SR policy containing IFIT information.

https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-policy-ifit-03

I think this draft will help in the deployment of IFIT technology.

Kind Regards

Gyan

On Thu, Mar 10, 2022 at 9:39 AM Susan Hares <shares@ndzh.com> wrote:

> Greeting:
>
>
>
> This begins a 2 week WG Adoption call (3/10/2022 to 3/24/2022)
>
> for draft-wang-idr-bgp-ifit-capabilities-04
>
> https://datatracker.ietf.org/doc/draft-wang-idr-bgp-ifit-capabilities/
>
>
>
> In your comments please consider if:
>
>
>
> 1) Do the additions to BGP (2 Communities and
>
> TLV for next-hop-capability attribute)
>
> help the distribute information regarding the  IFIT options
>
> from tail (egress) nodes to head nodes (ingress)?
>
>
>
> Are there any cases where these BGP
>
> Communities should be removed or ignored?
>
>
>
>
>
> 2) Are the mechanisms (2 Communities and
>
> attribute TLV) correctly specified?
>
>
>
> 3) How do these additions interaction with the
>
>   With SR technology for IFIT described in
>
>    draft-ietf-idr-sr-policy-ifit, and its
>
>    use of RFC9012 (tunnel attributes)?
>
>
>
> (Authors an example on how these
>
> technologies work together or
>
>  operate separately would be helpful).
>
>
>
> 4)  Will this addition help network operators
>
> deploying IFIT technology?
>
>
>
>
>
> Cheerily, Sue
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

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