Re: [Bier] draft-ietf-bier-ipv6-requirements-09

Alvaro Retana <aretana.ietf@gmail.com> Thu, 19 November 2020 03:50 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F033E3A0949; Wed, 18 Nov 2020 19:50:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 nQViOfzSJC12; Wed, 18 Nov 2020 19:50:42 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 B3EE33A0942; Wed, 18 Nov 2020 19:50:41 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id t9so4330746edq.8; Wed, 18 Nov 2020 19:50:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=kGOP6FPpkVWwgY1a1Vp4GyAX65228pWVrFe3Sl9X4VM=; b=HK7y5aDmrTcF86qg96Ejtq7e5OfIbiZOYG2KMZMEyIZ1cMtXNvMkvDtuKFmov5m7sS TecdSt9s4kUxr0Cq+/QMLOp8gOGvBtZbSdRNpfcRzgcFf1VRQuFrwPxJLl0ydjp7XqiU sOYsljauEDFNHJxNU3Q1FeCk3RY+oMfrfXmNk1Bei7+Sf3stMB11gvNZYos8C1BECb5i xF6DlalibApLgFZpbAPJorsjcFRGzHHRn/TyShFohbkiZVx9y2VrLIPrk2aKx1kkYTxS TqwSSl9J6BTGvkzMwtWM4Kr3+4mNfv2b0ZcAdms+9IRlWCJRPDoM+/Wi2UBOpK4bvTmI WyYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=kGOP6FPpkVWwgY1a1Vp4GyAX65228pWVrFe3Sl9X4VM=; b=qG8Rx03mSCe/Gnv9Kjkc5ceRvTXNfCHP0p+PDbX/WE6RsMEFFf/LxaMSHkR5zlx4Lm sJ4YzqgB3bsjCnv5QtLzXfqQXBFgO36JiZUFjRuxZgnOV9kOYzhY9OAPRI1logWMbGkw dHYNr/TiJP/QfeY2vHxrsr/z0nkiLjXedBBam0sHQerP2ttmH97EpUP2bLwN4Q7pujit oay/ADDDC/7mZ1L90Wwg+Ukw1zO25l1xK7R0BSgf+XI6sVBKxkZl6wJSbGppTMW1ujnz 6PbOHE1vefeZeMaZhWjh3u40kXf8jFrgJN+jauZREDuit2SfC8tEcd50nxy10jT3Z5Ze OWDQ==
X-Gm-Message-State: AOAM531N5+sSeRDlHG2V8PdfpO/QwaNdL/q4a/npNCYgAI6Pj5i08yrC OP1iTVdRpjKq3H6ZeCyZ7HZvBHTWZPbPZAX0VKE=
X-Google-Smtp-Source: ABdhPJyjMmNnSc5FKNqEpnvYNigyOC6Cv9FzZi3jb31NFNBYrUJVi3xx1W2C6NQ51RIWcJ2nJmVkZ6M1B6BHwsZ+lDA=
X-Received: by 2002:a05:6402:1281:: with SMTP id w1mr30318662edv.353.1605757839914; Wed, 18 Nov 2020 19:50:39 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 18 Nov 2020 19:50:38 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CABNhwV26CqDs8vwT=mcPQMVGVTFLVEOgVYtaYZyuyNiBFMYGcw@mail.gmail.com>
References: <CABNhwV0aZRqXP2wAweEktsibTYpHqHhDB9OTPkO+1JmyOb7-gA@mail.gmail.com> <MN2PR05MB5981CEBAA6AB7329350293EED4E10@MN2PR05MB5981.namprd05.prod.outlook.com> <CABNhwV26CqDs8vwT=mcPQMVGVTFLVEOgVYtaYZyuyNiBFMYGcw@mail.gmail.com>
MIME-Version: 1.0
Date: Wed, 18 Nov 2020 19:50:38 -0800
Message-ID: <CAMMESsxcToFPgS6S64AYwdZCMAwsVbV37cvoNKqgE=hF112r9g@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Cc: draft-ietf-bier-ipv6-requirements <draft-ietf-bier-ipv6-requirements@ietf.org>, Greg Shepherd <gjshep@gmail.com>, Tony Przygienda <tonysietf@gmail.com>, "EXT-zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, BIER WG <bier@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/cO7ISeNJ4E8BqqtLghivaMS99bQ>
Subject: Re: [Bier] draft-ietf-bier-ipv6-requirements-09
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2020 03:50:44 -0000

On November 19, 2020 at 3:18:58 AM, Gyan Mishra wrote:


Hi!

Just a couple of comments.


> On Wed, Nov 18, 2020 at 11:29 AM Jeffrey (Zhaohui) Zhang wrote:
..
> > From: Gyan Mishra
> > Sent: Wednesday, November 18, 2020 10:14 AM
...
> > > Alvaro mentioned as far as the list of requirements that they were
> > > fairly basic but maybe needed some more meat behind it such as the
> > > “support various L2 link types” but we did not specify. In previous
> > > versions we stated L2 agnostic and then switched to various but being
> > > vague on which L2. Alvaro also mentioned why OAM should be a
> > > requirement. We may want to add a sentence on justification as to why we
> > > picked BIER IPv6 requirements as required versus optional.
> >
> > Zzh> I actually don’t think L2 link types is a key issue. Whatever modern
> > L2 links that an operator wants to use, it’ll need to be supported both by
> > IPv6 and BIER, and it is as simple as adding a codepoint for the L2 header
> > to indicate whether the next header is IP/MPLS/BIER/whatever (again – the
> > beauty of clear and independent layering).
> >
> Gyan> I don’t think Alvaro was saying there was any issue but just pointing
> out that we did not specify which link types. We can discuss with authors
> what link types we should add explicitly.

<individual hat on>

It was Loa, not me, who raised the point about the L2 requirement
being vague.  I do agree with him.  I also agree with Jeffrey on his
point that "modern L2 links that an operator wants to use, it’ll need
to be supported".  To me, this then becomes another general
requirement -- unless there's a special reason to add or exclude
something.

I did say that the mandatory requirements are general and broad.  For
example, "support the BIER architecture" is obvious, and I assume both
solutions do.  BTW, "deployments with BIER-incapable routers" is also
covered in rfc8279.

My comment about OAM was along the lines of the fact that there is no
standard BIER OAM mechanism defined.  It seems like a stretch to
require BIER functionality that has not been defined.  A better
approach might be to explain the required functionality (for example,
continuity, liveliness, etc.).



...
> > Zzh> With the above consideration, I would say the “suggested next steps”
> > in my presentation is quite reasonable.
> >
> Gyan> Let’s have the chairs and AD chime in on this thread.

<AD hat on.>

As I mentioned on the call, my opinions on this thread are as an
individual.  The Chairs are more than capable of providing direction
and don't need me for that.


Thanks!

Alvaro.