IETF Logo Mail Archive

Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

Leo Bicknell <bicknell@isc.org> Thu, 29 September 2011 13:32 UTC

Return-Path: <bicknell@isc.org>
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 60D6121F8C82 for <grow@ietfa.amsl.com>; Thu, 29 Sep 2011 06:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.425
X-Spam-Level:
X-Spam-Status: No, score=-1.425 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, J_CHICKENPOX_43=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZZ1CThtG7nN for <grow@ietfa.amsl.com>; Thu, 29 Sep 2011 06:32:43 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0AE21F8C61 for <grow@ietf.org>; Thu, 29 Sep 2011 06:32:43 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 741E05F98FC; Thu, 29 Sep 2011 13:35:14 +0000 (UTC) (envelope-from bicknell@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10294) id EA8DF216C36; Thu, 29 Sep 2011 13:35:12 +0000 (UTC)
Date: Thu, 29 Sep 2011 13:35:12 +0000
From: Leo Bicknell <bicknell@isc.org>
To: Danny McPherson <danny@tcb.net>
Message-ID: <20110929133512.GA77671@bikeshed.isc.org>
References: <20110928193323.GA57548@bikeshed.isc.org> <CC4CB415-C615-4379-842F-2177B333D380@tcb.net> <20110928235156.GA65454@bikeshed.isc.org> <352BFFD6-B2C3-4ACD-96C1-46F28B5E5719@tcb.net> <20110929130632.GA76531@bikeshed.isc.org> <E6D92094-5836-4BB8-8E3A-5F620AA67696@tcb.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E6D92094-5836-4BB8-8E3A-5F620AA67696@tcb.net>
Organization: Internet Systems Consortium, Inc
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 29 Sep 2011 13:32:48 -0000

In a message written on Thu, Sep 29, 2011 at 09:27:57AM -0400, Danny McPherson wrote:
> I never said "does not require any pre-knowledge".  As a matter of fact,  
> what I said, and what the draft says, is that with unique origins the 
> services operator _could publish in a well-known location a list of origin 
> ASNs for a given prefix and the feasible adjacent upstreams for each ASN.  
> With that information network operators can make informed decisions about 
> the legitimacy of a new path in the routing system for a critical Internet
> services prefix.

Ok, fair enough.  So let's ask the direct question:

  Would it not be even better then for them to have a unique origin
  ASN, and publish the list of paths that originate the route,
  achieving the same result without needing to have an inconsistent
  origin?

Seems like that would be a quick change to the draft...

And couldn't the entire draft thus be greatly simplifed to a single
paragraph?

  Anycast operators SHOULD publish a list of all valid AS-Paths to reach
  their Anycast service to aid in the detection of routing leaks.

I suppose bonus points if we could agree on a method for publishing
(RPSL?).

-- 
Leo Bicknell; E-mail: bicknell@isc.org, Phone: +1 650 423 1358
INOC*DBA *3357*592; Internet Systems Consortium, Inc.  www.isc.org

v2.23.0 | Report a Bug | By Email