Re: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions (11/1 to 11/16)

Dhruv Dhody <dhruv.ietf@gmail.com> Fri, 13 November 2020 06:00 UTC

Return-Path: <dhruv.ietf@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 1CEFB3A1543 for <idr@ietfa.amsl.com>; Thu, 12 Nov 2020 22:00:59 -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, 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 T8auuBP6JYmc for <idr@ietfa.amsl.com>; Thu, 12 Nov 2020 22:00:57 -0800 (PST)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 2FA293A150C for <idr@ietf.org>; Thu, 12 Nov 2020 22:00:57 -0800 (PST)
Received: by mail-il1-x136.google.com with SMTP id l12so7533734ilo.1 for <idr@ietf.org>; Thu, 12 Nov 2020 22:00:57 -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=+Ll0IN2UNUCb9FUUl6Eh2ZlQT8C3NIgF4G0Go8lLF5s=; b=npfs+khP/tGJkMrf4ArSlGkqn71zi1zGPWZt+zAFWk5LfYaXNChJkAGYldN+mq2tXX s1mc9EPbHtHhegZKGA1RadmiAh5RMuFTt2LqXmaGQKwyX8EkE60Tz9xPb62FPyk9EkVl rt4JVZA1Vq4wA3OebOrEMAiYl0KTjOH6EhqoAsnbWWPguaO9ggZpxMXxVtk9+LVR89vg xbuciN6H2izEmKNgBGIe73QV7jiJ3T/pxpv04NwVJtIUivFqWzHFCynL+XdCpvskEHo6 Fx9zQKqshMy3oIkQH1TzowQOr+ZAZm9gjTFVJ+AKaSsHuOUDvzn8CHc/zD04h6XcYr1Y PE/Q==
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=+Ll0IN2UNUCb9FUUl6Eh2ZlQT8C3NIgF4G0Go8lLF5s=; b=QFxXQzUrnI5ZqtG/a+dv5D0PoAh7QpXineeiq4K/O/Qx0tKauSXaVVtBggbtcKpw8A 2P1YoQAuG5zvGIsg+t5BKIX0PQKy9BBojBsyGASpG0b32lE2B1YpWKks5ZFPTk0xJ1OO OHBi+dnRb4m237EFwRKOnaUV+bCzr4OOwpItG4Op63gsMmyTIlf4qK5pjWRZhtzyFPuz urWN/0UNrvOfoZBESmqlPDDm1ve+vl8byP/2vwTJHctMNKWQH4yN8upkaIyVuIzxJvZn r9q/2Um7TYiWnFwYHSLrScXGbt2sMePfJm9ahAZayvkOVZpp0BT7O/+7NoxKC0dlVohY JYEw==
X-Gm-Message-State: AOAM531q1R0hP9REC9gjVKHyGPQAreaZhXSD28lo5dluoMZdkECCtPQT EcsTvaQOQfznY6lw+kR2j7N692L71NNB1B2VOQQ=
X-Google-Smtp-Source: ABdhPJwgP/ZswfYHG1Wu29+dMC2v4nvkXYDv7VH57UeCXC8qVl2uyCUcGDpx6UbJCW4yCotbhQEL+qSOdM1ZVSewiNA=
X-Received: by 2002:a92:c84e:: with SMTP id b14mr725519ilq.1.1605247256101; Thu, 12 Nov 2020 22:00:56 -0800 (PST)
MIME-Version: 1.0
References: <040101d6b0c2$05f080c0$11d18240$@ndzh.com> <CAB75xn7PDPdzu73MTBskWcnhe7tDPRHUydVq9Ctcp7AE_Xt39A@mail.gmail.com> <MW3PR11MB45708D22450E4EFAD9790D21C1E60@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB45708D22450E4EFAD9790D21C1E60@MW3PR11MB4570.namprd11.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 13 Nov 2020 11:30:19 +0530
Message-ID: <CAB75xn5FRFEo+2kV=V0JbVghUrbaXGG9PB88JO_ra-6eO8eRyQ@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: Susan Hares <shares@ndzh.com>, idr wg <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3eCoGLznwsljPAWF8wsn47A-2zQ>
Subject: Re: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions (11/1 to 11/16)
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, 13 Nov 2020 06:00:59 -0000

Hi Ketan,

On Fri, Nov 13, 2020 at 11:11 AM Ketan Talaulikar (ketant)
<ketant@cisco.com> wrote:
>
> Hi Dhruv,
>
> Thanks for your review and ack for all the comments except the last one on the references. The IGP specs have been traditionally used as normative in BGP-LS and so I would prefer to keep it that way here too.
>

I am all for traditions :) but IMHO they were normative in the other
BGP-LS documents because one needs to "normatively" refer to them to
know the encoding and understand the meaning of the various fields. I
don't see that here. Hope this helps to understand why I asked to
re-evaluate this, rest is up to you!

Thanks!
Dhruv

> Thanks,
> Ketan
>
> -----Original Message-----
> From: Idr <idr-bounces@ietf.org> On Behalf Of Dhruv Dhody
> Sent: 13 November 2020 10:36
> To: Susan Hares <shares@ndzh.com>
> Cc: idr wg <idr@ietf.org>
> Subject: Re: [Idr] IPR and WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions (11/1 to 11/16)
>
> Hi WG,
>
> I support publication, the extension is useful and the document clear.
>
> Just a few nits -
>
> - Expand LSP, PW, iBGP, eBGP on first use
> - s/Type: 1032/Type: 1032 (early allocated by IANA)/
> - Section 4, you have -
>
>    The S-BFD Discriminators TLV can only be added to the BGP-LS
>    Attribute associated with the Node NLRI that originates the
>    corresponding underlying IGP TLV/sub-TLV as described below.
>
> and then the next paragraph -
>
>    When the node is not running any of the IGPs but running a protocol
>    like BGP, ...
>
> I suggest removing the "only" as it adds to confusion as non-IGP cases are allowed as well.
>
> - Check if RFC7883 and RFC7884 are better suited as informative.
>
> Thanks!
> Dhruv
>
>
>
>
>
>
> On Mon, Nov 2, 2020 at 8:14 AM Susan Hares <shares@ndzh.com> wrote:
> >
> > This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions (11/1 to 11/16).
> >
> > This is the second WG LC call since the initial call had only 1 reponse besides the authors.
> >
> >
> >
> > You can access the draft at:
> >
> > https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sbfd-extensions
> > /
> >
> >
> >
> > We have a report of draft has 1 implementation from Nokia:
> >
> > https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-sbfd-extensi
> > ons%20implementations
> >
> >
> >
> > We are missing IPR statements from Sam Aldrin and Greg Minsky.
> >
> > The co-authors should encourage these authors to submit IPR statements
> >
> > by Tuesday (11/3/2020).
> >
> >
> >
> > In your responses please consider the following questions:
> >
> > a) Do you know any issues with this technology?
> >
> > b) Will this technology help BGP-LS deployments?
> >
> > c) Is this draft ready for publication?
> >
> >
> >
> > If you know of any additional implementations, please
> >
> > send email to the WG chairs or respond to this email
> >
> > with the information.
> >
> >
> >
> > Cheers, Susan Hares
> >
> >
> >
> > _______________________________________________
> > Idr mailing list
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr