IETF Logo Mail Archive

Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)

Andrew Lange <andrew.lange@alcatel-lucent.com> Tue, 20 November 2012 22:37 UTC

Return-Path: <andrew.lange@alcatel-lucent.com>
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 2274C21F8815 for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 14:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGwRWnPsWS9l for <grow@ietfa.amsl.com>; Tue, 20 Nov 2012 14:37:33 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by ietfa.amsl.com (Postfix) with ESMTP id 563F121F872D for <grow@ietf.org>; Tue, 20 Nov 2012 14:37:32 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id qAKMbUfZ021817 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 20 Nov 2012 23:37:30 +0100
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 20 Nov 2012 23:37:30 +0100
Received: from alange.lra.lucent.com (135.5.27.17) by US70TWXCHHUB03.zam.alcatel-lucent.com (135.5.2.35) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 20 Nov 2012 17:37:27 -0500
MIME-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Andrew Lange <andrew.lange@alcatel-lucent.com>
In-Reply-To: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
Date: Tue, 20 Nov 2012 14:33:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-ID: <02F2E288-0042-4637-9234-A946B7501EC6@alcatel-lucent.com>
References: <CAL9jLabt0S98HEygsQp=a98ARwiRxJ2x3F2=H5w-pDRbyqWE7A@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Originating-IP: [135.5.27.17]
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
X-Mailman-Approved-At: Thu, 29 Nov 2012 08:49:38 -0800
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-mcpherson-irr-routing-policy-considerations@tools.ietf.org, grow-ads@tools.ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call: draft-mcpherson-irr-routing-policy-considerations (END: 11/28/2012)
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: Tue, 20 Nov 2012 22:37:34 -0000

Strongly support.  IRR is a key issue for interdomain routing.  Understanding the history is key for getting things right in the future.

Andrew

On Nov 14, 2012, at 2:35 PM, Christopher Morrow wrote:

> Grow Folks,
> the authors of:  draft-mcpherson-irr-routing-policy-considerations
>  <http://tools.ietf.org/html/draft-mcpherson-irr-routing-policy-considerations-01>
> 
> have asked if their work is appropriate for the GROW-wg, could we take
> the next 14 days (ending Nov 28, 2012) to think/discuss this draft and
> it's efficacy to work in the GROW arena? The abstract of the draft is:
>  "The purpose of this document is to catalog past issues influencing
>   the efficacy of Internet Routing Registries (IRR) for inter-domain
>   routing policy specification and application in the global routing
>   system over the past two decades.  Additionally, it provides a
>   discussion regarding which of these issues are still problematic in
>   practice, and which are simply artifacts that are no longer
>   applicable but continue to stifle inter-provider policy-based
>   filtering adoption and IRR utility to this day."
> 
> Thanks!
> -Chris
> (co-chair)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

v2.23.0 | Report a Bug | By Email