Re: [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020).

Gyan Mishra <hayabusagsm@gmail.com> Fri, 19 February 2021 06:32 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 431883A1079 for <idr@ietfa.amsl.com>; Thu, 18 Feb 2021 22:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, 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 fJ8U46og_YWz for <idr@ietfa.amsl.com>; Thu, 18 Feb 2021 22:32:37 -0800 (PST)
Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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 725233A1075 for <idr@ietf.org>; Thu, 18 Feb 2021 22:32:37 -0800 (PST)
Received: by mail-pl1-x62b.google.com with SMTP id d15so2816793plh.4 for <idr@ietf.org>; Thu, 18 Feb 2021 22:32:37 -0800 (PST)
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=DIj8Wbb4GdN0gEX0hrmYPt8/gdGhnKxVIt1XkZ+Te80=; b=XfFdosDsyRKLeuOeBWYal0JygEIzYNd8y13vQu3TR/X2jbzj5jUGJCA1T04Vg769k5 9oxuSj5CcZF0sBy+pONiF7R99VJBhZLdhq79qjjyN8fJtTUE5TQftsyFRpohJiL/UNwG XN/6JiR8e1k/ACMlHK+Eo+4ZLlKqAgLFx6MBN4xLW6nMAGaGIgBt3vEZR4G9zATkq7mX C9bXo8lopRv2vmVDO/+KXDYnFAPrULXZ4dzqtuAc/DiGYSFSe888EUmW66t2ymhVCpfe DPyTlQDP4xDj78fKpBztyCQle8ZS/LKirLXIuIasAIkYocVRr/nbW1Gc1H2ZWosIK9YF bzGQ==
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=DIj8Wbb4GdN0gEX0hrmYPt8/gdGhnKxVIt1XkZ+Te80=; b=el3LRYeK/xT1t13tfqSXBsZ9Ku9Z8cBq5YvMZtcr689xo6fKeNXeuOe40M7QslKnPd Z/aGrcOtpkmHXd3TzoFLlG6uczdUjaEhIOZ1CXr82r7UgESvFxwFzx3bo0aiaHs5saA2 fjdqFlfWw/rMlojuf4VgQvkKh/fPUIFPO5VhXI1D3FZuQpMkbKpafCfDLluvFVH69u0w pgKQG3RwdjWVp5iUDO/rzicH/RK/Z7RExg3dxzva0h1tznaWB5Er7mMItQd/Gx/XjY02 duq2uLHQZQXGmkbZGCAYPvPzyF/3UTgtJDdQM2h2mg28Tk0+P561xzBKGzGbBf4e8HxP io2w==
X-Gm-Message-State: AOAM533bB3sDngvCLprW2MBZev9DTxajoxC07K3qIrKIrDD0d7/I/xVU FiJfE3Y1HnT9u7ohampiXMddWW7HYtDV20bFkQ4=
X-Google-Smtp-Source: ABdhPJwibhNTOX+fomHBFKSx/hQPnUttNfFs8Y15vChXWVkxTUXjayn1k0UVJUaECvtEgD/bcL9bRl1TWx91cV/u0V4=
X-Received: by 2002:a17:902:9b91:b029:e3:2c9e:f511 with SMTP id y17-20020a1709029b91b02900e32c9ef511mr7700429plp.74.1613716356712; Thu, 18 Feb 2021 22:32:36 -0800 (PST)
MIME-Version: 1.0
References: <012d01d6fb0d$b50468c0$1f0d3a40$@ndzh.com> <32e9db67e4b44375b06b7f1111a0fbec@huawei.com>
In-Reply-To: <32e9db67e4b44375b06b7f1111a0fbec@huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 19 Feb 2021 01:32:26 -0500
Message-ID: <CABNhwV29HqBRUj-v9w9JuSdHvrYnA9mtn9WW47VCpUH80pS7QQ@mail.gmail.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035cdfd05bbaa9e90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mGutZ3zyz6TMr6pa3OkeJLBh9JA>
Subject: Re: [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology only (2/4/2020 to 2/18/2020).
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, 19 Feb 2021 06:32:40 -0000

Hi Sue

I support publication of this document as a standard RFC.

Since this document supports GRE, IP in IP and L2TPv3, even though the
title states NVO3 overlays, should this draft really include all tunnel
types described in tunnel-encap-22 that would be applicable to flow spec
dissemination. If so the then maybe removal of NVO3 in the draft name and
change to tunneled traffic maybe appropriate.

1.) Does WG to standardize this technology with

    the IPR Statement (which appeared in 5/8/2020 after a modification of
the draft)?

 Yes

2) Is this approach to flow-specification for tunnels ready for
standardization?

 Yes

3) Would this technology inter-work with tunnels created by

 draft-ietf-idr-tunnel-encap-22.txt?

 Yes.  I think it is very important for this document to support the tunnel
encap draft NVO overlay encapsulations.

4) Should this technology wait for a flow-specification v2?
I don’t think so.  As we are proceeding with modified WG LC without any
implementations i think in that light we can proceed to publish and not
wait for flow spec v2.  At that time we can always to an bis update if
needed to the publication as necessary.

Thank you


Gyan


On Thu, Feb 18, 2021 at 7:37 AM Dongjie (Jimmy) <jie.dong@huawei.com> wrote:

> Hi Sue,
>
>
>
> I’ve reviewed this document and support its publication as standard RFC.
>
>
>
> Best regards,
>
> Jie
>
>
>
> *From:* Idr [mailto:idr-bounces@ietf.org] *On Behalf Of *Susan Hares
> *Sent:* Thursday, February 4, 2021 11:52 PM
> *To:* idr@ietf.org
> *Subject:* [Idr] WG LC - draft-ietf-idr-flowspec-nvo3-12 - Technology
> only (2/4/2020 to 2/18/2020).
>
>
>
> Greetings:
>
>
>
> This begins a modified draft-ietf-idr-flowspec-nvo3-12.txt.
>
>
>
> It is a modified WG LC because:
>
> 1) the WG still has to discussion where we make the cutoff for
> flow-specification v2,
>
> 2) there are no implementation for this WG LC
>
>
>
> This WG LC should examine the following things:
>
>
>
> 1.) Does WG to standardize this technology with
>
>     the IPR Statement (which appeared in 5/8/2020 after a modification of
> the draft)?
>
>
>
> 2) Is this approach to flow-specification for tunnels ready for
> standardization?
>
>
>
> 3) Would this technology inter-work with tunnels created by
>
>  draft-ietf-idr-tunnel-encap-22.txt?
>
>
>
> 4) Should this technology wait for a flow-specification v2?
>
>
>
> 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 *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD