Re: [GROW] Limiting AS path length?

William Herrin <bill@herrin.us> Thu, 19 September 2019 15:57 UTC

Return-Path: <bill@herrin.us>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDC6120814 for <grow@ietfa.amsl.com>; Thu, 19 Sep 2019 08:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Z8vCp5Og2AF5 for <grow@ietfa.amsl.com>; Thu, 19 Sep 2019 08:57:14 -0700 (PDT)
Received: from magic.dirtside.com (magic.dirtside.com [199.33.225.25]) by ietfa.amsl.com (Postfix) with ESMTP id C06B8120810 for <grow@ietf.org>; Thu, 19 Sep 2019 08:57:14 -0700 (PDT)
Received: from minoc.dirtside.com ([199.33.225.53]) by magic.dirtside.com (8.14.3/) with ESMTP id x8JFv7OV025345 for <grow@ietf.org>; Thu, 19 Sep 2019 08:57:09 -0700
X-Really-To: <grow@ietf.org>
Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by minoc.dirtside.com (Postfix) with ESMTPSA id 7026FEBDB5 for <grow@ietf.org>; Thu, 19 Sep 2019 08:57:07 -0700 (PDT)
Received: by mail-pg1-f179.google.com with SMTP id w10so2130671pgj.7 for <grow@ietf.org>; Thu, 19 Sep 2019 08:57:07 -0700 (PDT)
X-Gm-Message-State: APjAAAUIlcoteI3TR83nx35d1IcLG0yxniUXHiSjEv7k1sY39+FHOVK5 X3m3vAB+D7wXYerypqeWdDPN+hcLmwg/bn2enn8=
X-Google-Smtp-Source: APXvYqw/TAYkTM71HsxcIlkka+pTgqykbrTKgw+EYPpCqihZg7yw40MlhG3l4OeHa+3j9RpVKtvA/Ibb8B4PO4fOZgs=
X-Received: by 2002:a17:90a:9ab:: with SMTP id 40mr4517252pjo.38.1568908627057; Thu, 19 Sep 2019 08:57:07 -0700 (PDT)
MIME-Version: 1.0
References: <4AB89C90-67E9-4B6F-8F30-3E2748D37C20@pfrc.org> <5B8AED56-3218-4AD0-8453-14ABC0DADC21@puck.nether.net> <CACWOCC94rT+YA7j=1SMkqkyjjZN12z1E_jX44=6XCczc+MfN5Q@mail.gmail.com>
In-Reply-To: <CACWOCC94rT+YA7j=1SMkqkyjjZN12z1E_jX44=6XCczc+MfN5Q@mail.gmail.com>
From: William Herrin <bill@herrin.us>
Date: Thu, 19 Sep 2019 08:56:50 -0700
X-Gmail-Original-Message-ID: <CAP-guGWON5w9GTqYVbM5t1z=m+UjOOL3SqfxKFa1x2CtAyyuKQ@mail.gmail.com>
Message-ID: <CAP-guGWON5w9GTqYVbM5t1z=m+UjOOL3SqfxKFa1x2CtAyyuKQ@mail.gmail.com>
To: Job Snijders <job@instituut.net>
Cc: Jared Mauch <jared@puck.nether.net>, Iljitsch van Beijnum <iljitsch=40muada.com@dmarc.ietf.org>, "grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066a3a40592ea01a8"
X-Spam-Checker: magic.dirtside.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/frb1qWYr7sG9JU0XhXEqYol_o0M>
Subject: Re: [GROW] Limiting AS path length?
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2019 15:57:16 -0000

On Mon, Sep 16, 2019 at 11:37 AM Job Snijders <job@instituut.net> wrote:

> Limiting the AS_PATH length - from an IETF RFC publication process in
> context of providing operational guidance, probably shouldn’t be “limit the
> path length to avoid vendor bugs”.
>
> Instead, the guidance perhaps should be “please report and fix bugs”,
> right? :-)
>

Hi Job,

"Don't poke the bear," is generally good advice. When we have sufficient
reason to believe a particular behavior is error-prone, we should
discourage that behavior. Regardless of whose "fault" it is.

AND we should encourage folks to report and fix bugs.

Regards,
Bill Herrin

-- 
William Herrin
bill@herrin.us
https://bill.herrin.us/