Re: [sidr] BGPSec RFC status

"Russ White" <7riw77@gmail.com> Fri, 15 April 2016 01:13 UTC

Return-Path: <7riw77@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 D078812D6D6 for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 18:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 u1CVOGwvhwUp for <sidr@ietfa.amsl.com>; Thu, 14 Apr 2016 18:13:32 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 5513C12DAA8 for <sidr@ietf.org>; Thu, 14 Apr 2016 18:05:13 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id d68so122234332ywe.1 for <sidr@ietf.org>; Thu, 14 Apr 2016 18:05:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=Pim9TEtHR8vsBldvjUg352vWNAZ2wIDxs3MX3/gy+YA=; b=hpRz2a2ePbm7Vro49GpLgptnklILSSbkHaLOetJpThdqo2gvniRwDqqrClPXQOFOLt pgPocx8q3khTPQ0T7uNZVxhTKW645xhTpdmj3foFJ0whahhd3KnGplPzNMopRjLs3V2N V1fc/ks33PHBz1HLSqjmQAgcp7f36zplwTJYSc3ywzqHeOfwRoTQCNY4luHazcmuxVIu KcUevBIX6rciqG9AS0zbDHRg6xzvy83Oo52qF+e2KiARFoQkGOGNNuhLTdc10hK9uqnj GwoJ7TI2A1joCF5koVpmvvAvDtL245+58JFHAAJAOtgTIktZlUEkX97780g0rAG2Udca 9KaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=Pim9TEtHR8vsBldvjUg352vWNAZ2wIDxs3MX3/gy+YA=; b=m1p2KR/4NxzXcwtdDbiX03rUzFfOGlUCMg6SaTSWbas6L9dM5AfuR/AykKjlQN+a1z UpzUh0vs/3TeDEOCNerRvY8qc4WV3Cd9UVoaQPeQp7zfMiGe+O7bryYsJl3sRoC4IIZw U/Z9NKXQimlLOwsVPI39xDaaRgk6t/fVexf5+8dmqLOosZIBeuvSAX9ghVY+T3E4G31a x4c5XqpG74PASDtshAvbyfRwcPm+SM9MzTId88eqO8Oitip9NQouN3hi33o34tqUKkRx UxaucEg1XNPpzQ0256Nb18UnU8ePoXhKVTbiq5DTw+wakjUIbnLkIu1R/+A26H+bLSfX I8iQ==
X-Gm-Message-State: AOPr4FWeDphnRLNnahm1dlX1M9irYknNjEGMORoPMHtfXqzKczpAASc/ifpdVZCTal6S+Q==
X-Received: by 10.129.27.6 with SMTP id b6mr11950584ywb.205.1460682312644; Thu, 14 Apr 2016 18:05:12 -0700 (PDT)
Received: from Russ (162-229-180-77.lightspeed.rlghnc.sbcglobal.net. [162.229.180.77]) by smtp.gmail.com with ESMTPSA id f129sm25379749ywd.10.2016.04.14.18.05.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Apr 2016 18:05:12 -0700 (PDT)
From: Russ White <7riw77@gmail.com>
To: 'Randy Bush' <randy@psg.com>
References: <570E8D44.1080208@bbn.com> <04F2C4EA-BF87-45A1-904F-350455D11FDE@apnic.net> <052101d196a8$85e90c90$91bb25b0$@gmail.com> <m2r3e7u38h.wl%randy@psg.com>
In-Reply-To: <m2r3e7u38h.wl%randy@psg.com>
Date: Thu, 14 Apr 2016 21:05:11 -0400
Message-ID: <052401d196b2$dc84a280$958de780$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQK50UkYZgz1WOiK04JSUwHF5BdAuwJ4+ki0AigqhLYDB8zkQp18eJcA
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/YMd0JEdij5Y8HmvWAXyre2bGZ2Y>
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 01:13:34 -0000

> 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.

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.

:-)

Russ