IETF Logo Mail Archive

Re: [Sidrops] erratum

Christopher Morrow <christopher.morrow@gmail.com> Wed, 08 November 2023 22:37 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 6B841C15154D for <sidrops@ietfa.amsl.com>; Wed, 8 Nov 2023 14:37:47 -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 imdeeaNR33TI for <sidrops@ietfa.amsl.com>; Wed, 8 Nov 2023 14:37:47 -0800 (PST)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (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 0679AC15153F for <sidrops@ietf.org>; Wed, 8 Nov 2023 14:37:47 -0800 (PST)
Received: by mail-vs1-xe33.google.com with SMTP id ada2fe7eead31-45dae475aedso124192137.2 for <sidrops@ietf.org>; Wed, 08 Nov 2023 14:37:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699483066; x=1700087866; 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=4S9DpZny3255aRbh+Ac2Y9muhI3sQ+X2nRvuYygqP+s=; b=VTcZ96bRN0iMknOBUvnLBtjHsqk5yLLlWhaUWOma8/eLdE1p61SP5EE2lr/5gtJjFJ oYAj98s2syYABEqRBlwRvxrauKLgTLaEFp9BfvoPvcyddUPqr1HqLCjCVtdHDubXikPY FRzxQei0vjl0Ehoq2/oZEgUWH0dR5sqPmHZy+YOcsh1UMTPvW+PcN/0lYaOo8FAqce+b /OaNMjkFdCgCQkg06PIBBlwZ+bRrwjIRdjSTpxq+MnzOUs0dNCPa8tSL+LqCJfAkP0Uo oDUgUU4BKonzYzhytzKm7Z/9EnDb9pFa7F8U64aI3dQhJB9Kitt6QhGFsdRQihfivhbY 4LVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699483066; x=1700087866; 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=4S9DpZny3255aRbh+Ac2Y9muhI3sQ+X2nRvuYygqP+s=; b=SziZyiHQMTYGRcyM9H9/oWBgIh+UtIM2vhZjU7McNdyp3xDgLaj3DLUC2Rh68PwjP7 k1JRQWKKbrhITKvQH8KOiRhmKHWZCJpvA70b5eKW561LJZa1p5VDLksT9c4RhUFb+R6r 7ZC9W0nbqGdrQaAxVaY8l/3jujSK6y2mWPBizxRM2wVYKfUryL9joWSBhDkJ0b5ZW24M pB0iF/cbPFrY9Stq7xU96HKzOCimawCkoE+K09LAxbc2OvY70CIDMFdEIVRmFXrNa1g8 i6UrtUnoISEcNR9QIoySv5w0uceRstbSdJrVlpoFvdZcKm+hKBtwU1LAHmCcSS1VKgE3 rxsA==
X-Gm-Message-State: AOJu0YwZ5Hkyru9+Qqh05AyzdvK+HuS0K2k0RBNeXS9ssY717dx1vaOw 4fe+DHr8M6+2Jd0KVCyemGJ099aW/8RMRM7lHL8MwLuFISM=
X-Google-Smtp-Source: AGHT+IHb7cSfIbhiK3zjI8H96FIgghY2QMI+xwnXbxkoUA9ZJcXgE3yDGe8rmazkm3AfU4n2pCTJBSgXuLe2oQd8XCs=
X-Received: by 2002:a67:e1c5:0:b0:45d:9a4d:dc1d with SMTP id p5-20020a67e1c5000000b0045d9a4ddc1dmr2503019vsl.8.1699483065902; Wed, 08 Nov 2023 14:37:45 -0800 (PST)
MIME-Version: 1.0
References: <m2sf5ggcfu.wl-randy@psg.com> <ZUv_e1xfKT9FG-e-@shrubbery.net> <m2msvnho95.wl-randy@psg.com>
In-Reply-To: <m2msvnho95.wl-randy@psg.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Wed, 08 Nov 2023 17:37:35 -0500
Message-ID: <CAL9jLaZ4hpEC+RUGc=tHV65JqGN2ixeO+R_V=gDd2ayqoQr1yQ@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/QkMUXYwSVD1YxiHBznDdZKe-5Dk>
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:37:47 -0000

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."

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