Re: [sidr] BGPSec RFC status

Christopher Morrow <morrowc.lists@gmail.com> Fri, 15 April 2016 03:18 UTC

Return-Path: <christopher.morrow@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 51D1512DCCA for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 20:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 72D0f6gI4GBa for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 20:18:01 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 A05EC12DC6C for <sidr@ietf.org>; Thu, 14 Apr 2016 20:18:01 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id i84so124446201ywc.2 for <sidr@ietf.org>; Thu, 14 Apr 2016 20:18: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=RnMhca8Lgx32cKNb6uMySxA1HquAR+VYdEexQdSnks8=; b=bYrU8tKL7lfeGURVTXE3Um4Jk06eEplgRnfcUyDF33JDt1L7W0TxizKj5LWZcoHOod s/bojNXHNCgp5MvsSkhai5XUyqreJcaNuoAmPISI/HBlLUmiqcii9pkf22RiEbiZXi81 0knViEWyj3Ob6viFZKodnenrJqokmyut8/yB4cJbw98FV5xF8qDqPImsTL9XJl5jU3a4 5kv7xVrpH+0XgGXOpJh/3u6Vko2PlK7bDpW3RqGeEph58GvVtl6egtG8IAupKXkPmdDL bMBeunyPSG4t1OwFBbfa/KmWzb64HPcJ2u6dEGtqIx38C6vV4nS3S1bnRlQ60D4j41iG xmaA==
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=RnMhca8Lgx32cKNb6uMySxA1HquAR+VYdEexQdSnks8=; b=CIQRll22yms2QUE+p5S8iPoZEn87Shz9OsTEhQvP8p9+xYSHoJpIXEtvPtJZE+ONUm 7iYd6jyzpqRnZt+d6e3YYX4owHMHmYwsiVDjctXCv2Bp06cIrbBS8Ru5N2l82OtF6i2G bJTfGjxe+5elwsh1HunjFvd1JZ4bTK5QCzfTMDmW/qM38dbpDpQ/VsJBAKeQo4XEFAvx ArkH5aO+Ozz1WwTl3UCKjBayF2zQ6ecMgOC7ghYKbMEt1uodRc0sf1HPN6xYccF0gM1R 0ijSWzOwbD5tTNof1xV137U2R3yBYWvIz92QTdbl3uuVLcrWtyWe3AZbhjO+bj5dL7zB 8/RQ==
X-Gm-Message-State: AOPr4FVNvIuVfZk6X0tXZaJmzuoesg7IRNyJ5I0J4mkpdhRCGXkaQRflTG27MBVLIGUOgC2oYXOCO73oQ5HLjg==
MIME-Version: 1.0
X-Received: by 10.129.130.196 with SMTP id s187mr10518243ywf.315.1460690280921; Thu, 14 Apr 2016 20:18:00 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.13.209.198 with HTTP; Thu, 14 Apr 2016 20:18:00 -0700 (PDT)
In-Reply-To: <052401d196b2$dc84a280$958de780$@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>
Date: Fri, 15 Apr 2016 00:18:00 -0300
X-Google-Sender-Auth: d7loRet9YnUFlFiyVDo6FqddMok
Message-ID: <CAL9jLaZwyvtuX_fCjH5-SCU6VmRFNCZuAZRUkhPTicHvUgCEvw@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Russ White <7riw77@gmail.com>
Content-Type: multipart/alternative; boundary="94eb2c07c18a52418c05307d75b1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/OtmBl95cHQzfhHdYfCA3NWciQ6M>
Cc: sidr wg list <sidr@ietf.org>
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:18:03 -0000

On Thu, Apr 14, 2016 at 10:05 PM, Russ White <7riw77@gmail.com> wrote:

>
> > snmp, netconf, yang, ...  heck even cops played in the space
> >
> > when your so-bgp, 15 years in the non-making, is mature as a document
> set,
> > with two or more implementations, i'll support it for standards track, no
> > problem.  i am not desperate enough to sabatoge the work of others to
> > move my work forward.
>
> Wow -- care to prove that accusation? Or have we gotten to the point in the
> IETF where personal accusations are a normal, everyday, substitute for
> actual discussion? This sort of personal abuse is what turns people away
> from the IETF, and reduces our value as a community. This is just wrong,
> Randy, and you know it is.
>
>
​<co-chair-hat>​

​to be very clear, I don't think that rock tossing helps here.. in fact I
think it's distracting to the question asked. (original question I mean)
let's not toss rocks please. (either of the 2 folk on To: nor other folk on
the -list)​
​</hat>​



> My point is simple -- the "no-one will use it" argument washes either way,
> so there needs to be some other grounds for deciding -- it's not a useful
> argument in either direction, honestly. Which throws us back to what
> "standards track" actually means. On that score, I'm not certain what the
> terms mean, so I asked for clarification on what the wording actually
> means.
>
>
​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

In fact the last sentence implies that more work could be done and that
it's NOT the final solution.

​let's please keep to the question. I do think discussion of this topic is
interesting, to me at least, and useful for the group. My personal opinion
is that PS seems like the right answer still, even after all these years.

-chris
<co-chair>​