Re: [mpls] Alvaro Retana's Discuss on draft-ietf-mpls-ri-rsvp-frr-07: (with DISCUSS and COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Fri, 11 December 2020 11:45 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E453A0AEE; Fri, 11 Dec 2020 03:45:24 -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 0IzOhLN15ZcM; Fri, 11 Dec 2020 03:45:23 -0800 (PST)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (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 154953A0AE8; Fri, 11 Dec 2020 03:45:22 -0800 (PST)
Received: by mail-ej1-x630.google.com with SMTP id qw4so11877840ejb.12; Fri, 11 Dec 2020 03:45:22 -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=gzK9/ID6yGejGouKscNkZcPN9uu0KcclgrC6p2UhGxI=; b=fu9oyT7cn/XwovZ5PGdS9+d0OPBrKS/fNibWSiydmik5hpztRzQOiJarkqUrzgYMUh h2K4iw4E0ACGMD+Nuq2dhMPvKg6TN8dcxCEZadn5F9RxkWjQRW6ko2TrzhkdwwPCJuW3 Q4X3N0YOSrZ48XurFTI72HshndYvZhq07RihE+ZMlD1TLR9ClH4/sDnAjtcyt1zX914J qiZvFPmGJ2ONk5dKcvTLxgGC9OU4Nf82eAh4HEnqVnEbmN7NQRT+yzzuydrTuz3b+THz IlAyYeQ3CV7ADlqi29idR0YPgWsTS73OmQQAzYv/5jgQ6YVqiV6vkyc4qSufRg3XBAUV m0kg==
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=gzK9/ID6yGejGouKscNkZcPN9uu0KcclgrC6p2UhGxI=; b=enATm+M4jh0EtvcEK/o75RkFd5UT4gToRBJxCtcSwlMh+Fy0USoUgvwu/RoVsddiQb +qStJvINxD7Lohz0fdSmHWLKrwHVmXp5Dkl+NySEbqrRRiF8/oeiwTAUkub90mP08HYZ PtNaqlIc5ePByIE/DlW9a/cOE1qXnF+5ughvmVJJ6mB4SlFetMfqS8PHuJWp5wigt/no SIkNLKTdP6VCzHWG0Ea4RF/pQgXHfL71X6r6r5ESjS1I44Yr/pAh9232gdcBkdQrbtDZ t1TMzDnjG+xhH5GiJqAzL4sblgPDPkmMtls5jXBlkoBYXltZfiv5XW9gHyX/BBEPHqvy UmFA==
X-Gm-Message-State: AOAM532Vf3neoUeLi4EZMD8GBbknFeCT/OIYQmPovWY31uYv16CgqvHI o2FEow/sawGsNN7SqyfTP2EKULW1r0r0Vo2aKf8=
X-Google-Smtp-Source: ABdhPJxQp3z2hPDEYirxqQWiXxXUjQC7bLvH5q1T376TxmkS6SrC1bbdUX2J/xb8I02HZBFVeSYRtNulsVg5HZ199yU=
X-Received: by 2002:a17:907:444f:: with SMTP id on23mr10757358ejb.300.1607687121256; Fri, 11 Dec 2020 03:45:21 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 11 Dec 2020 03:45:20 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <DM6PR05MB51299C70F8D011D1AF0F1837D9FC0@DM6PR05MB5129.namprd05.prod.outlook.com>
References: <157532380379.1952.9823190776406362368.idtracker@ietfa.amsl.com> <MN2PR05MB61746F4DCF7D06BC7BF73055D95D0@MN2PR05MB6174.namprd05.prod.outlook.com> <CAMMESsx4oUrGbhD4OiHMNxA32NAmqFyZV_00BA_MBWW0kyojKw@mail.gmail.com> <MN2PR05MB6174F008ECD126C8201D081BD95C0@MN2PR05MB6174.namprd05.prod.outlook.com> <CAMMESszzw-VvswxwVPQYFAiEuXU+OkNwTWayebE7HBOaNMfS=g@mail.gmail.com> <F64C10EAA68C8044B33656FA214632C8AF84E8B6@MISOUT7MSGUSRDE.ITServices.sbc.com> <CAMMESsx8qH=LSAj=KLxjCeQok8Re_V5PB=qbrc50KhPd840aKg@mail.gmail.com> <DM6PR05MB51299C70F8D011D1AF0F1837D9FC0@DM6PR05MB5129.namprd05.prod.outlook.com>
MIME-Version: 1.0
Date: Fri, 11 Dec 2020 03:45:20 -0800
Message-ID: <CAMMESsw07O5bS8hRhntZUyxRouKveFgyvWqG965NdzHAJe86Gw@mail.gmail.com>
To: Chandrasekar Ramachandran <csekar@juniper.net>, The IESG <iesg@ietf.org>, "BRUNGARD, DEBORAH A" <db3546@att.com>
Cc: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-ri-rsvp-frr@ietf.org" <draft-ietf-mpls-ri-rsvp-frr@ietf.org>, Nicolai Leymann <n.leymann@telekom.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/fU_b30mtpa1uopSjImOfnJ9s6vo>
Subject: Re: [mpls] Alvaro Retana's Discuss on draft-ietf-mpls-ri-rsvp-frr-07: (with DISCUSS and COMMENT)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Dec 2020 11:45:25 -0000

On November 23, 2020 at 12:19:22 AM, Chandrasekar Ramachandran wrote:


Chandra:

Hi!

> I have reworded the text in Section 4.1 to spell out the requirements on
> setting or not setting the I-bit by implementations that support RFC 4090
> and RFC 8370. I have also included a new Section 4.6.2.3 “Advertising
> RI-RSVP without RI-RSVP-FRR” describing the impact of ignoring the
> requirements for setting the I-bit.
>
> Could you go through these sections in the 09 version of the draft and
> respond if your comment is addressed?

The text in §4.1 still contains normative text directed at nodes that
don't support this spec: "node...not supporting the extensions
specified in	this document MUST NOT set the...I bit".  Your original
suggestion worked:

...
> > > > > [Chandra] I agree that what you have pointed out requires some
> > > > > changes to the text. Would the following changes to the document
> > > > > address your concerns adequately?
> > > > ...
> > > > > (3) Change the only paragraph in Section 4.1 from "A node supporting
> > > > > [RFC4090] facility protection FRR MAY set the RI-RSVP capability (I
> > > > > bit) defined in Section 3 of RSVP-TE Scaling Techniques [RFC8370]
> > > > > only if it supports all the extensions specified in the rest of this
> > > > > document. A node supporting [RFC4090] facility bypass FRR but not
> > > > > supporting the extensions specified in this document MUST reset the
> > > > > RI-RSVP capability (I bit) in the outgoing Node-ID based Hello
> > > > > messages. Hence, this document updates [RFC4090] by defining
> > > > > extensions and additional procedures over facility protection FRR
> > > > > defined in [RFC4090] in order to advertise RI-RSVP capability
> > > > > [RFC8370]."
> > > > > To
> > > > > "A node supporting [RFC4090] facility protection FRR MUST set the
> > > > > RI-RSVP capability (I bit) defined in Section 3 of RSVP-TE Scaling
> > > > > Techniques [RFC8370] only if it supports all the extensions
> > > > > specified in the rest of this document. Hence, this document updates
> > > > > [RFC4090] and [RFC8370] by defining extensions and additional
> > > > > procedures over facility protection FRR defined in [RFC4090] in order
> > > > > to advertise RI-RSVP capability [RFC8370]."


I think that §4.6.2.3 is ok, but there's still the possibility of some
of the timing issues described in §3 as well, right?

Thanks!

Alvaro.