Re: [OPSEC] draft-ietf-opsec-blackhole-urpf-00

Christopher Morrow <morrowc.lists@gmail.com> Wed, 21 January 2009 04:59 UTC

Return-Path: <opsec-bounces@ietf.org>
X-Original-To: opsec-archive@optimus.ietf.org
Delivered-To: ietfarch-opsec-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 345943A6A1C; Tue, 20 Jan 2009 20:59:47 -0800 (PST)
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0729A3A6A1C for <opsec@core3.amsl.com>; Tue, 20 Jan 2009 20:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIDcRQKZvkic for <opsec@core3.amsl.com>; Tue, 20 Jan 2009 20:59:45 -0800 (PST)
Received: from mail-bw0-f21.google.com (mail-bw0-f21.google.com [209.85.218.21]) by core3.amsl.com (Postfix) with ESMTP id 088073A68B5 for <opsec@ietf.org>; Tue, 20 Jan 2009 20:59:43 -0800 (PST)
Received: by bwz14 with SMTP id 14so12045136bwz.13 for <opsec@ietf.org>; Tue, 20 Jan 2009 20:59:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=YQeCQoulsLtd5nu9CZcut49mRtIQB41ps4OEvYQWaA4=; b=U7EkGCSa2WoxFQtR6SmnEtVjC/5kRwNpw8zMarzhcmuWJSlyFD1E8e5Y6Qs7W6Pu1w G1GGRovPmYwYFJ/xCFhjIgluavADVMSVxPZTFirpROdxqQOzuEogQqQEM8vShavtiCDg 0YjTyHnPnLEYct2HArHz4cApCvndBqS+FFNVI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=FNKxeJjcCR6mvxkbJC3aOCPlwwoh3caIL8DUKf4eqIF0Vg4v9goh70NbesYfEeLBYy EHT+BM1Rn56ijGR32c5EVlKSBJ6KNaR33Sgp1VdMBU8rMjIcOUsJ4edT1cG4iJT0YTku hACZc1ncTyI0aFf35CWVlWQzh4WI+kKKNFOgc=
MIME-Version: 1.0
Received: by 10.223.105.208 with SMTP id u16mr658299fao.14.1232513965302; Tue, 20 Jan 2009 20:59:25 -0800 (PST)
In-Reply-To: <E3B4452D-A984-439F-9069-7E43F51E3F42@kumari.net>
References: <E3B4452D-A984-439F-9069-7E43F51E3F42@kumari.net>
Date: Tue, 20 Jan 2009 23:59:25 -0500
X-Google-Sender-Auth: f4bfd797093b807c
Message-ID: <75cb24520901202059h313c2ff2oafa4d4c4d517d062@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: opsec@ietf.org
Subject: Re: [OPSEC] draft-ietf-opsec-blackhole-urpf-00
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsec-bounces@ietf.org
Errors-To: opsec-bounces@ietf.org On Tue, Jan 20, 2009 at 1:21 PM, Warren Kumari <warren@kumari.net> wrote:

> Now, for the big question:
>
> In the draft we are are requesting a registered BGP community to be used to
> signal your provider that you want destination based RTBH applied to an
> announced prefix.

I don't believe a 'well known community' helps here... I believe it
will cause more issues than it resolves. I fear that folks will assume
their provider has this enabled (because configuration is required on
the provider side, unlike no-advertise and no-export). This will cause
unpredictable behaviour for customers and operators.

-Chris
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec