IETF Logo Mail Archive

Re: [sidr] BGPSec RFC status

Rob Austein <sra@hactrn.net> Fri, 15 April 2016 03:56 UTC

Return-Path: <sra@hactrn.net>
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 C164912DF42 for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 20:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
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 Yas7TMRl76yu for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 20:56:20 -0700 (PDT)
Received: from cyteen.hactrn.net (cyteen.hactrn.net [66.92.66.68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37D9212E11A for <sidr@ietf.org>; Thu, 14 Apr 2016 20:56:12 -0700 (PDT)
Received: from minas-ithil.hactrn.net (c-73-47-197-23.hsd1.ma.comcast.net [73.47.197.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nargothrond.hactrn.net", Issuer "Grunchweather Associates" (not verified)) by cyteen.hactrn.net (Postfix) with ESMTPS id DB039129A for <sidr@ietf.org>; Fri, 15 Apr 2016 03:55:57 +0000 (UTC)
Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id B31A13E949BC for <sidr@ietf.org>; Thu, 14 Apr 2016 23:55:49 -0400 (EDT)
Date: Thu, 14 Apr 2016 23:55:49 -0400
From: Rob Austein <sra@hactrn.net>
To: sidr@ietf.org
In-Reply-To: <CAL9jLaZwyvtuX_fCjH5-SCU6VmRFNCZuAZRUkhPTicHvUgCEvw@mail.gmail.com>
References: <570E8D44.1080208@bbn.com> <04F2C4EA-BF87-45A1-904F-350455D11FDE@apnic.net> <052101d196a8$85e90c90$91bb25b0$@gmail.com> <m2r3e7u38h.wl%randy@psg.com> <052401d196b2$dc84a280$958de780$@gmail.com> <CAL9jLaZwyvtuX_fCjH5-SCU6VmRFNCZuAZRUkhPTicHvUgCEvw@mail.gmail.com>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20160415035549.B31A13E949BC@minas-ithil.hactrn.net>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/kx1pX1FXR-g-mFP5BMWYWA4YOZc>
Subject: Re: [sidr] BGPSec RFC status
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 15 Apr 2016 03:56:23 -0000

At Fri, 15 Apr 2016 00:18:00 -0300, Christopher Morrow wrote:
> 
> I don't know exactly either, but this from 2026:
> 
> "   A Proposed Standard specification is generally stable, has resolved
>    known design choices, is believed to be well-understood, has received
>    significant community review, and appears to enjoy enough community
>    interest to be considered valuable.  However, further experience
>    might result in a change or even retraction of the specification
>    before it advances."
> 
> doesn't:
>   1) say anything about the 'Final and Ultimate Solution'
>   2) that other work can't be done

Exactly.  Enough people seem to think this is a promising approach to
merit PS status.  The fact that there are also people who don't want
to use it doesn't change that.  Go for PS and move on.

v2.23.0 | Report a Bug | By Email