Re: [Idr] Lars Eggert's No Objection on draft-ietf-idr-rfc7752bis-14: (with COMMENT)

Ketan Talaulikar <ketant.ietf@gmail.com> Fri, 17 February 2023 12:08 UTC

Return-Path: <ketant.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 62C6FC14CEFE; Fri, 17 Feb 2023 04:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kdCHRbKw2_H; Fri, 17 Feb 2023 04:08:46 -0800 (PST)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADCA9C14E513; Fri, 17 Feb 2023 04:08:46 -0800 (PST)
Received: by mail-ed1-x530.google.com with SMTP id eg30so3216635edb.7; Fri, 17 Feb 2023 04:08:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VW4xcTpveEGiKZ97Vocxo50nBtr+U4VI5MPcVtuhxa4=; b=FICY4v38fB2htI6bVjVALKpgBQ/sf2eg/rpjAqU3EWkUdzu9O16Rnzq44wDb/ZMhV3 H+wjPcVH7lweRPJpw34wo0osZGR5vHGVho/iiC+AzVxbibXepIBrvZcuoQAYWOZJ/geg Ps37v8nbAtr+BfDtU0+L68AVRVvkwHXFmYd0d0iNS7HZbXlatIavVUYq1BFv2Wi9qO29 ggQ0OxMwkMJ0GzVyqisUyQbE5Kjmx/2Okc3DjiuKmmXixAiAmWkObuJgXu0LB1qXF9wn 4RuW6kiafTIE0jFlTGACn/oPrViMo7TxJR1ddlhT6VjYavjgFHsZmYmioJ/W0yEoDDhB V89Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VW4xcTpveEGiKZ97Vocxo50nBtr+U4VI5MPcVtuhxa4=; b=L+7kiHl18ZbcpjpqQKAjYqIb5T0Jedyd4mPSP+XoDqtUKqcJ8nitM7yArcUBc1nu1v fTI1Q8CYx9mrDHWmBtGgsAmUtt1mkxFs/+2MP4upiYjlsl9oNRm0QSDp/QXCqkoqS9k8 hplzEI752hYbmzmEPF+TPgqbobTowIegl5ht1qK+xpqaKu+rMvHz5/DcCo0dDsfrgSHm gqStZ2GtX5lcaBPfFmS/6tHTOfCx4otJLCEe9f9B9ORE7w5hUVhIRzQFzn6uLIS3sAp0 qQfOpYhZilqNGrib/KKWBj/EOQT9zUCka06k1eOIe9Fg1rgSAKE0emGgQtY1NUsW3+GO tF2g==
X-Gm-Message-State: AO0yUKWZZOXoaztw/a8O+lYYUuQ2UuA5r3tSyy0UuCtPqk80yTq0+YCK S6ydeXDDBmgSaavOYsrmRY+UGbVzlNmM/fHhZDo/LAzSybY=
X-Google-Smtp-Source: AK7set/18+UfliT8HfLrY7Srk3h3warwC/PRUUTlIucg+xElUURq9oBv9qB8qdEytu2ZdBRKBK0ql+bOyWqU85L1opE=
X-Received: by 2002:a17:906:680f:b0:883:b1d3:ae67 with SMTP id k15-20020a170906680f00b00883b1d3ae67mr470587ejr.5.1676635724632; Fri, 17 Feb 2023 04:08:44 -0800 (PST)
MIME-Version: 1.0
References: <167110671278.47364.16506124207984879789@ietfa.amsl.com> <CAH6gdPxw=bvr+cU3khvC2Fmkvf86UdQu35_R+h9qtK1dtL8Hmg@mail.gmail.com> <58257CA6-2A38-4FDE-A2E0-BA5839626DBD@eggert.org> <CAH6gdPyJZL72TFZ1XbU3DaTwCR9BftCkPtxGQ+3wSTJ-yYrofQ@mail.gmail.com> <26F6790A-6F09-4CB9-83CA-AFF2CA5B2E1E@eggert.org>
In-Reply-To: <26F6790A-6F09-4CB9-83CA-AFF2CA5B2E1E@eggert.org>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Fri, 17 Feb 2023 17:38:32 +0530
Message-ID: <CAH6gdPxfsW1v5qQjdszg2fJNv5PaTRaG-7pFrdnro67i=9VEiQ@mail.gmail.com>
To: Lars Eggert <lars@eggert.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-idr-rfc7752bis@ietf.org, idr-chairs@ietf.org, idr@ietf.org, shares@ndzh.com, jhaas@pfrc.org, aretana.ietf@gmail.com
Content-Type: multipart/alternative; boundary="000000000000c8d7cd05f4e42c51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0rg3GrP0SWgudrAYczv6deuPJYA>
Subject: Re: [Idr] Lars Eggert's No Objection on draft-ietf-idr-rfc7752bis-14: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Feb 2023 12:08:48 -0000

Hi Lars,

What we have in the latest version (posted earlier today) is the following:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc7752bis-15#section-5.1

   To compare NLRIs with unknown TLVs, all TLVs within the NLRI MUST be
   ordered in ascending order by TLV Type.  If there are multiple TLVs
   of the same type within a single NLRI, then the TLVs sharing the same
   type MUST be first in ascending order based on the length field
   followed by ascending order based on the value field.  Comparison of
   the value fields is performed by treating the entire field as opaque
   binary data and ordered lexicographically.


Does that work?

Thanks,
Ketan


On Fri, Feb 17, 2023 at 5:33 PM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> On Feb 17, 2023, at 13:54, Ketan Talaulikar <ketant.ietf@gmail.com> wrote:
> > > ```
> > >      To compare NLRIs with unknown TLVs, all TLVs within the NLRI MUST
> be
> > >      ordered in ascending order by TLV Type.  If there are multiple
> TLVs
> > >      of the same type within a single NLRI, then the TLVs sharing the
> same
> > >      type MUST be in ascending order based on the value field.
> Comparison
> > >      of the value fields is performed by treating the entire field as
> > >      opaque binary data and ordered lexicographically.
> > > ```
> ...
> > KT2> Are you suggesting that the description in the text is
> insufficient? I am not sure if a Wikipedia article would fly as a (in this
> case normative?) reference.
>
> Yes, I think you need to say something more, because the current text says
>
> 1. order TLVs by type
> 2. if there are multiple TLVs of the same type, order them by value
> 3. to order by value, order lexicographically
>
> My point is that in step 3, the values may be of different lengths, and so
> you need to say what *kind* of lexicographic order you intend (= shortlex).
>
> You don't need to cite Wikipedia, you could also just require that values
> are first compare solely by length and lexicographically when the lengths
> are equal.
>
> Lars
>