IETF Logo Mail Archive

Re: [Idr] WG Adoption call draft-ymbk-idr-bgp-open-policy - (6/6 to 6/20/2016)

Robert Raszuk <robert@raszuk.net> Fri, 10 June 2016 11:57 UTC

Return-Path: <rraszuk@gmail.com>
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 B90EE12D999; Fri, 10 Jun 2016 04:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0oGpY_0OBYLz; Fri, 10 Jun 2016 04:57:02 -0700 (PDT)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95B2512B02F; Fri, 10 Jun 2016 04:57:01 -0700 (PDT)
Received: by mail-lf0-x230.google.com with SMTP id j7so20812008lfg.1; Fri, 10 Jun 2016 04:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=1Mt188GQBjM4eQBjfKeoiM62Jzq0iTjubkLHiwTeITY=; b=bXUwvtTeJ7AqgS4ZxZVelaVm44WVwQXlRc8YsmPPb0+1d10fzSD29TP8PsQ6EEvEbU D4I/y8Dp/rhVJhmzQv/pPD1q8r3R86LAd3BRH37h9+c9uBS/fj0Sw9DtglzkaS1mlo2f By5RUjTHn03Ioew/c+gJgmOqJ04/fG1/o0S969AmYkOkWHvat6qTrZJoFRlU3R9/NShy WRNjCQJ3cMd2emXAmftvnC1MqkTPy8iB5sfHPI1Y2/9ItxxZcnw5QOYFwsFKRKW5Iwyx HJdE5oUbuyC6DrvMQt8p0/s7/opeDsg0qnP43X9U+95hsvJwpBf+VKRGg9EuZdxYhptO Xx/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=1Mt188GQBjM4eQBjfKeoiM62Jzq0iTjubkLHiwTeITY=; b=h7BM57OFJ63tvE/Pp9Xp0umHkbVJEh0e+yzNwq5cu74Y6T1o/mhSyArPa6tLpRLt4Y 39lKFY4NVefK6dvvzAfAojYSa0096KocVRxPScGjPRRXnF7E1tBU5EtKKyOoQtPKMQ1u u3cty4BMMrmoKW0pJJjjRfso4K8AaKp7nhNyW07APQr0mdNyPJlGi+VTcjHKH0TScYDU /j7tWXpfCu+xywBBUxXni5NdEVQo6cOdQYoUKLqsHWG1Avc5cEeFUkC5g2QZEYXmnhCU 4AyYUDVCYBUSkZeOAXK4hDQ9MSLb569aaaSg2pi6Jh6RQMT5D0lVyNLqYxS2o0iB/4hh Hr0w==
X-Gm-Message-State: ALyK8tKu8s6KHyFJLLC3OzS6KPla92J8WJdCK4LIOlvzRVKsO0k56ULfeaKAlWN0dmc9b4CTyHkm3OQ0nfDNWw==
MIME-Version: 1.0
X-Received: by 10.25.33.133 with SMTP id h127mr452513lfh.82.1465559819691; Fri, 10 Jun 2016 04:56:59 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.25.21.30 with HTTP; Fri, 10 Jun 2016 04:56:59 -0700 (PDT)
Received: by 10.25.21.30 with HTTP; Fri, 10 Jun 2016 04:56:59 -0700 (PDT)
In-Reply-To: <CA+b+ER=fcFXVdLN475QeE=5-DfdhmVd0LxBMzo4MogGcjTaYxQ@mail.gmail.com>
References: <012e01d1c012$1d05f8d0$5711ea70$@ndzh.com> <CA+b+ERmCugH3kV5-yCG7=ArQGvzCeOV9Fij0=0-WqDU=YYa52A@mail.gmail.com> <CA+b+ER=fcFXVdLN475QeE=5-DfdhmVd0LxBMzo4MogGcjTaYxQ@mail.gmail.com>
Date: Fri, 10 Jun 2016 13:56:59 +0200
X-Google-Sender-Auth: HnNggIcxtc5yaenZKJPBn2a-tlQ
Message-ID: <CA+b+ERk_-8P0YsCC1cFEscLBMG37oaNLvXnqRABZ2kt+yuyTsw@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="001a113f1888732f9b0534eb3cac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/uKPH9yOxOAfFFKOBkl1GYS2Flco>
Cc: idr wg <idr@ietf.org>, draft-ietf-idr-route-leak-detection-mitigation@ietf.org, "John G. Scudder" <jgs@bgp.nu>
Subject: Re: [Idr] WG Adoption call draft-ymbk-idr-bgp-open-policy - (6/6 to 6/20/2016)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Jun 2016 11:57:04 -0000

Responding to #3 how authors envision deployment via IX where I peer single
session to RS while on the other side I may have various types of peers ?

I do not think BGP OPEN MSG is the right place for this.

Thx
R.
On Jun 6, 2016 12:40, "Susan Hares" <shares@ndzh.com> wrote:

This begins a 2 week WG Adoption call for draft-ymbk-idr-bgp-open-policy.
You can find the draft at:

https://datatracker.ietf.org/doc/draft-ymbk-idr-bgp-open-policy/.



In your comments on adopting this draft, please indicate:



1)      “Support” or “no Support”

2)      Do you feel this is a way to prevent route leaks?

3)      Are there any deployment issues that might prevent deployment of
this enhancement to BGP Open?

4)      Does this interact with
draft-ietf-idr-route-leak-detection-mitigation?



Sue Hares and John Scudder



_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email