Re: [Idr] the first field

Joe Provo <jzp-idr@rsuc.gweep.net> Mon, 19 September 2016 20:02 UTC

Return-Path: <crimson@sidehack.sat.gweep.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 2E47312B53A for <idr@ietfa.amsl.com>; Mon, 19 Sep 2016 13:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level:
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, 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 oo21v8ZXv8Me for <idr@ietfa.amsl.com>; Mon, 19 Sep 2016 13:02:15 -0700 (PDT)
Received: from sidehack.sat.gweep.net (sidehack.sat.gweep.net [72.93.233.150]) by ietfa.amsl.com (Postfix) with SMTP id 13D4212B537 for <idr@ietf.org>; Mon, 19 Sep 2016 13:02:15 -0700 (PDT)
Received: (qmail 87745 invoked by uid 524); 19 Sep 2016 16:02:14 -0400
Date: Mon, 19 Sep 2016 16:02:14 -0400
From: Joe Provo <jzp-idr@rsuc.gweep.net>
To: Interminable Discussion Room <idr@ietf.org>
Message-ID: <20160919200214.GF85721@gweep.net>
References: <m2h99b6eub.wl-randy@psg.com> <20160919174056.GC79185@Space.Net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20160919174056.GC79185@Space.Net>
X-PGP-Key: http://www.gweep.net/~crimson/pgp.txt
X-Disclaimer: "I'm the only one foolish enough to claim these opinions."
Organization: RSUC: NT? No Thanks!
X-Do-Not-Email-Here: trivial@spammers.can-bite.me.uk
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WjiyhUXYfjEdYVgvalst9Da61b4>
Subject: Re: [Idr] the first field
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jzp-idr@rsuc.gweep.net
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: Mon, 19 Sep 2016 20:02:16 -0000

On Mon, Sep 19, 2016 at 07:40:56PM +0200, Gert Doering wrote:
> Hi,
> 
> On Mon, Sep 19, 2016 at 09:20:44AM -0700, Randy Bush wrote:
> > clue bat please.  i am making the assumption that, as we consider using
> > communities to cause remote (further than next AS) semantics, the intent

One should never assume that actions requested further than the flow 
of ones payments will be honoured. That doesn't bar the request nor 
anyone supporting said request for free, but this is my first reading 
of action at a distance. I'll go re-read the threads.
nip]
>  <the AS that should do something>:<the AS peering that is affected>:<what>

That's close to my previous "<actor>:<target>:<action>". For action at
a distnace, the onus is on the actor as to from whom they'll honour 
requests for <action> toward <target>.  Given we're positing a world
involving action at a distance, <target> should not be assumed to be
a direct adjacency. 

It would not be unimaginable for a transit provider to offer BGP 
customers the ability to signal actions for prefixes facing arbitrary
ASNs, where the customer gets the luxury of not having to monitor the
provider's adjecencies ("oh no - I have been leaking prefixes because 
they now use a third-party to reach FOO!") and the provider could simply
act locally or also tag the request for appropriate remote action.

Cheers!

Joe

-- 
        RSUC / GweepNet / Spunk / FnB / CotSG / Usenix / NANOG