IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-deprecate-as-set-confed-set-01.txt

john heasley <heas@shrubbery.net> Tue, 05 November 2019 21:03 UTC

Return-Path: <heas@shrubbery.net>
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 7AA4F120BC9; Tue, 5 Nov 2019 13:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 4mHxzTKXCSY5; Tue, 5 Nov 2019 13:03:56 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F633120B7E; Tue, 5 Nov 2019 13:03:42 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id B5DB921BAC6; Tue, 5 Nov 2019 21:03:40 +0000 (UTC)
Date: Tue, 05 Nov 2019 21:03:40 +0000
From: john heasley <heas@shrubbery.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: john heasley <heas@shrubbery.net>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, IDR <idr@ietf.org>, "draft-ietf-idr-deprecate-as-set-confed-set@ietf.org" <draft-ietf-idr-deprecate-as-set-confed-set@ietf.org>
Message-ID: <20191105210340.GB55337@shrubbery.net>
References: <BN6PR09MB13317B7AD6F4229F5E00FDD284610@BN6PR09MB1331.namprd09.prod.outlook.com> <20191029213844.GC10145@pfrc.org> <BN6PR09MB13310C894E01C67E7E4DC761847F0@BN6PR09MB1331.namprd09.prod.outlook.com> <20191104214109.GC3277@pfrc.org> <20191104230615.GC67962@shrubbery.net> <20191105194917.GG3277@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20191105194917.GG3277@pfrc.org>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.12.2 (2019-09-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/rFaC5pjnaC3N-fUH1BLdKJJjKnA>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-deprecate-as-set-confed-set-01.txt
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: Tue, 05 Nov 2019 21:03:59 -0000

Tue, Nov 05, 2019 at 02:49:17PM -0500, Jeffrey Haas:
> My meaning was that it's a best common practice in the operational sense,
> not that someone wrote and RFC that has received that capital letter
> blessing.

IETF BCP or otherwise :)

> If you network is a more specific in that aggregate, what policy construct
> are you using to detect that your prefix is being covered in a less specific?

All one can reasonably do is verify the origin of the shorter aggregate in
the DMZ or, preferrably, origin validation.  Am I missing something?

v2.23.0 | Report a Bug | By Email