Re: [Idr] [BULK] Benjamin Kaduk's Discuss on draft-ietf-idr-flow-spec-v6-19: (with DISCUSS and COMMENT)

Jeffrey Haas <jhaas@pfrc.org> Mon, 16 November 2020 09:26 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 3017B3A1657; Mon, 16 Nov 2020 01:26:49 -0800 (PST)
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 p7aXrTs0iNaE; Mon, 16 Nov 2020 01:26:48 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8A43A164F; Mon, 16 Nov 2020 01:26:48 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 524971E354; Mon, 16 Nov 2020 04:42:49 -0500 (EST)
Date: Mon, 16 Nov 2020 04:42:49 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Christoph Loibl <c@tix.at>
Cc: Benjamin Kaduk <kaduk@mit.edu>, "idr@ietf. org" <idr@ietf.org>, draft-ietf-idr-flow-spec-v6@ietf.org, Robert Raszuk <robert@raszuk.net>, idr-chairs@ietf.org, The IESG <iesg@ietf.org>, Erik Kline <ek.ietf@gmail.com>
Message-ID: <20201116094249.GC12209@pfrc.org>
References: <E70A15BB-5C6C-447A-832C-571D413139E3@tix.at> <20201109205805.GY39170@kduck.mit.edu> <20201116080901.GI2881@pfrc.org> <20201116075756.GQ39170@kduck.mit.edu> <828ACEB0-C1D8-4A83-AED5-7B9F300F0421@tix.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <828ACEB0-C1D8-4A83-AED5-7B9F300F0421@tix.at>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Nm3KjBIwv7UCTZdJF74Eewg1pw8>
Subject: Re: [Idr] [BULK] Benjamin Kaduk's Discuss on draft-ietf-idr-flow-spec-v6-19: (with DISCUSS and COMMENT)
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: Mon, 16 Nov 2020 09:26:49 -0000

On Mon, Nov 16, 2020 at 10:12:18AM +0100, Christoph Loibl wrote:
> While I (personally) would prefer something like Juniper’s implementation. rfc5575bis's consensus was the approach that we suggest an encoding length for each FS component. The current approach in flow-spec-v6 does not break this concept and is consistent also with the base FS document. As Jeffrey mentioned it is also compatible with the “use as less bits as possible” encoding approach. Thanks for the comment Jeffrey. 

Remind me, is there procedure handling improper values for the length of the
component semantics?

E.g. ports can only be 2 bytes of value. 

I have a feeling this is in the base procedures of "this can't match, so
it's not a problem" but I'm not finding it right now.

-- Jeff