Re: [sidr] Fwd: New Version Notification for draft-dickson-sidr-route-leak-def-01.txt
Brian Dickson <brian.peter.dickson@gmail.com> Mon, 12 March 2012 01:15 UTC
Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF15721F8592 for <sidr@ietfa.amsl.com>; Sun, 11 Mar 2012 18:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 BtxiqbmqouVY for <sidr@ietfa.amsl.com>; Sun, 11 Mar 2012 18:15:02 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id E48AF21F8569 for <sidr@ietf.org>; Sun, 11 Mar 2012 18:15:01 -0700 (PDT)
Received: by wibhr17 with SMTP id hr17so2548986wib.1 for <sidr@ietf.org>; Sun, 11 Mar 2012 18:15:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i7tF2FlYDF0YsjfC0NacnQQGOgdCHCEsbUn7WJZMFEI=; b=lEu06D7kWSHYJ85/1aUh7xBXEaB4ebkfFDZTtWsmu6rbJ7LhjkZQl0jYSX4Ejqd1VF bsO0vUnlSVPWlYGoN2hmksuIuZLkpOjfLxaZcZI9EBUtVZnnCguZEkF0pYLpx9rE7SRh 9j3d1Tc2RKLRVxXz4aiW7a8JHtrT8nV6aIdf2tUlICbbqv6xDTcOkb2hrvbq0+k//si0 duYtB9RCh+z2e7ReVeOOYY6MchH0zcO06VD1EIqP6T/sJcvZ7PChCDyxdmKnNEsK6XyM Ylpoeaa6wMzwd9nfwMW90DMjUaXRemngJt4fKuoSU9g6eYj81j0/pkhyjNSDVs42x01U eWbw==
MIME-Version: 1.0
Received: by 10.180.105.69 with SMTP id gk5mr2857391wib.3.1331514900817; Sun, 11 Mar 2012 18:15:00 -0700 (PDT)
Received: by 10.223.69.3 with HTTP; Sun, 11 Mar 2012 18:15:00 -0700 (PDT)
In-Reply-To: <20120311213644.GA21499@slice>
References: <20120305180943.16641.16867.idtracker@ietfa.amsl.com> <CAH1iCiqvN2FhOhLGuZ44rm9BeUSM0UD9_qupt8eSD-nkX39cpg@mail.gmail.com> <20120311213644.GA21499@slice>
Date: Sun, 11 Mar 2012 21:15:00 -0400
Message-ID: <CAH1iCiogDUinxscw94aGXYF4odd9ySnJ94y32tuatyqRhkVDtA@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="f46d04426f14ad25f504bb017831"
Cc: sidr wg list <sidr@ietf.org>
Subject: Re: [sidr] Fwd: New Version Notification for draft-dickson-sidr-route-leak-def-01.txt
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 01:15:03 -0000
On Sun, Mar 11, 2012 at 5:36 PM, Jeffrey Haas <jhaas@pfrc.org> wrote: > Brian, > > On Mon, Mar 05, 2012 at 07:31:23PM -0500, Brian Dickson wrote: > > Here is the first of three IDs, concerning the definitions of "route > leak". > > > : 1.1. Rationale > : > : > : A route-leak occurs when a prefix is originated by one party, > : propagated by other parties, and received by the observer, where the > : path used was not intentional end-to-end. It is a leak if the > : receiver did not want the route, from a generic policy perspective. > > If the receiver didn't want the route? While that's perhaps true in many > cases, the impacted party is usually someone whose route was distributed > outside the scope where they intended it to be distributed. > > -- Jeff > Yes, you are correct. We can expand the language however folks would prefer. (But it is different from saying, "It is a leak _only_ if"... that was definitely not the intention of the description.) It should also be noted that, based on the definition(s), it would appear to be a leak, to every recipient after it became a leak. And, in most instances, it would also meet other leak-like criteria, including intended scope. The important thing is to reduce it to the smallest set of consistently present conditions -- a basis, if you will -- to make it possible to build rules into the protocol to stop leaks. Brian
- [sidr] Fwd: New Version Notification for draft-di… Brian Dickson
- Re: [sidr] Fwd: New Version Notification for draf… Jeffrey Haas
- Re: [sidr] Fwd: New Version Notification for draf… Brian Dickson