Re: [Idr] Question about draft-haas-flowspec-capability-bits-02

Jeffrey Haas <jhaas@pfrc.org> Tue, 22 June 2021 12:09 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 347E33A22B1; Tue, 22 Jun 2021 05:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 XqJTqKm8rjPK; Tue, 22 Jun 2021 05:09:08 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id A1E883A2235; Tue, 22 Jun 2021 05:09:08 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 835EE1E45C; Tue, 22 Jun 2021 08:34:53 -0400 (EDT)
Date: Tue, 22 Jun 2021 08:34:53 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Linda Dunbar <ldunbar@futurewei.com>
Cc: "draft-haas-flowspec-capability-bits@ietf.org" <draft-haas-flowspec-capability-bits@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <20210622123453.GA23751@pfrc.org>
References: <CO1PR13MB4920AD5CA604B232E294B978A90A9@CO1PR13MB4920.namprd13.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CO1PR13MB4920AD5CA604B232E294B978A90A9@CO1PR13MB4920.namprd13.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/6mOuJ_JzISFs2AaTcGCvkPHqkbY>
Subject: Re: [Idr] Question about draft-haas-flowspec-capability-bits-02
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: Tue, 22 Jun 2021 12:09:10 -0000

Linda,

On Mon, Jun 21, 2021 at 08:39:14PM +0000, Linda Dunbar wrote:
> Section 2 of the draft-haas-flowspec-capability-bits-02 shows the example of 13 bits representing the capacity.
> When the Nth bit is set to 1, does it represent Type N component is supported?

Correct.

> What if more types are proposed later? RFC8956 has Type 14-255 as reserved. I'd assume future drafts can propose more types. Does it mean the Capability value has to be expanded to 255 bits?

It means the protocol needs a serious rewrite.

The component types 14-255 are reserved, but that was partially because
there was no way to incrementally deploy new features.  Addressing that
potentially before a flowspec v2 protocol was a motivation for this draft.

> A nit: the second paragraph of the Section 1 says that "The components are documented in the Section 3 of RFC8955". But the components are actually specified in the Section 4. Do I miss something?

Thanks for bringing that to my attention.  That's a lingering issue from
changing from RFC 5575 where it was in section 3.  If I update the draft
I'll correct it next round.

-- Jeff