IETF Logo Mail Archive

Re: [Sidrops] erratum

Christopher Morrow <christopher.morrow@gmail.com> Wed, 08 November 2023 22:38 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECC3C15154D for <sidrops@ietfa.amsl.com>; Wed, 8 Nov 2023 14:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 18zBxf0jiv91 for <sidrops@ietfa.amsl.com>; Wed, 8 Nov 2023 14:38:41 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (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 E1822C15153F for <sidrops@ietf.org>; Wed, 8 Nov 2023 14:38:41 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id a1e0cc1a2514c-7b9dc928868so63419241.0 for <sidrops@ietf.org>; Wed, 08 Nov 2023 14:38:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699483121; x=1700087921; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lPe+017Cv6EfgO76G0c28OLtjHpDZNuXPC7+Xtd/9HI=; b=LTlp6vNrz+1A8fzoHVZw0Skea1raK/Rjxemli+QctN3g3xNj27nnSLGbUoZs1JFxHV 3VwXJSqmpMikflaWyot5jOCoA+vqZbLY2M7WlODftNl0WQhjOC0ZsaKwSPLziss9mek8 hMRO1aB/s4T2pjhwUGe+g9TuWoN9gWeNzyEPVJxNPwtLa/DBFjuvP51naOaqV8f++qve o6Wvv3vfj4vgV6FhtBhJALAnqeUIS/DUNhFIpzw4ca7uRInLOui8V3wHKuP011RNDoby FzwyhSN6XSFwq8L5S96hrY4wosX134IN7em7YQmCsKVB0wHU5A7WWc1HDx0XaJorLCXO 2GGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699483121; x=1700087921; h=content-transfer-encoding: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=lPe+017Cv6EfgO76G0c28OLtjHpDZNuXPC7+Xtd/9HI=; b=MCesMIIT9UteXsPqPSfE4IyH6SwupFy/EcypDGZrXuCd961IMGIuQePn/gvaQ2+dmU jwZCpqJbOETN630D6ivsQ7efBoBEIX7IM+u7TRrXN0uRN45ZS/or0bSyBNuA657Bu5Ll t3lGTxoh7tO30U+5B78EnD+jKao6g/UvfAivoZubTer8Xpomqcp94tcEsaWJwZFA3ReV QI1T9qTNAqgvw1glYsoDM9T20S2joj/D+7PsbF47ph7dqfppxXEobiH6oPG6sxK39GGM fi9Z9YUsDBu8Jj1Q3ZZBGfvtKWcwxPFuPeRP4XYfJNaCpYvo4PQn21cb3TFbi+RvV/K/ wtNQ==
X-Gm-Message-State: AOJu0Yz8IRulWrOZCbqQ/05oTq7mKyuNeqxWOZCiBpzryeV4qqfpno4A cv7eOrJtA2/joBmNc4mkiKEKOOBB+jmbjZTnEnc=
X-Google-Smtp-Source: AGHT+IGIYVT2WvXhb0P96BD8pKUf/HhyuuAPo2nkjhqJ1FHLoaaVo2eU3KPhbU2FE/bzMjwjV0JbokqmjbGcMifkc4Y=
X-Received: by 2002:a67:c10a:0:b0:452:6efc:1789 with SMTP id d10-20020a67c10a000000b004526efc1789mr2790590vsj.32.1699483120890; Wed, 08 Nov 2023 14:38:40 -0800 (PST)
MIME-Version: 1.0
References: <m2sf5ggcfu.wl-randy@psg.com> <ZUv_e1xfKT9FG-e-@shrubbery.net> <m2msvnho95.wl-randy@psg.com> <CAL9jLaZ4hpEC+RUGc=tHV65JqGN2ixeO+R_V=gDd2ayqoQr1yQ@mail.gmail.com>
In-Reply-To: <CAL9jLaZ4hpEC+RUGc=tHV65JqGN2ixeO+R_V=gDd2ayqoQr1yQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Wed, 08 Nov 2023 17:38:30 -0500
Message-ID: <CAL9jLab0T7UviyDSDAjuTuqsWCTRsTzhctOBpkze+Z6AWBbViA@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Cc: heasley <heas@shrubbery.net>, SIDR Operations WG <sidrops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/_tEk_iyeflcBI2mT75dsraBXDwg>
Subject: Re: [Sidrops] erratum
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2023 22:38:46 -0000

On Wed, Nov 8, 2023 at 5:37 PM Christopher Morrow
<christopher.morrow@gmail.com> wrote:
>
> On Wed, Nov 8, 2023 at 5:30 PM Randy Bush <randy@psg.com> wrote:
> >
> > >> a friend may have caught an erratum
> > >>
> > >> rfc7115
> > >>
> > >>    Operators should be conservative in use of max length in ROAs.
> > >>    For example, if a prefix will have only a few sub-prefixes
> > >>    announced, multiple ROAs for the specific announcements should be
> > >>    used as opposed to one ROA with a long max length.
> > >>
> > >> should that last "long" be a "short?"
> > >
> > > long seems correct to me.
> >
> > 9319
> >
> > maybe we are confused about the word "long."  to me, a /24 is longer
> > than /20.
>
> i think the text says:
>   "you propose to route 192.168.0.0/20, 192.168.1.0/24 && 192.168.8.0/21
>    please make roa for those exactly, not one roa for 192.168.0.0/20 -> /24"
>
> Or "do not do 192.168.0.0/20 and longer to /24"
>
> long/short / small/large :( it's hard to use these correctly here for
> all listeners/readers :(
>
> Maybe:
>
>   " multiple ROAs for the specific announcements should be used as
>    opposed to one ROA with the longEST max length."

err, or:
  "... ROA with the MAXIMUM PREFIX length."

that might be more clear.. or more clear for me :(

> I see how 'longer prefix length' and 'smaller prefix size' might be
> the confusing parts though :(

v2.46.0 | Report a Bug | By Email | System Status