Re: [Sidrops] update to document status

Randy Bush <randy@psg.com> Thu, 21 November 2019 22:41 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B221201A3 for <sidrops@ietfa.amsl.com>; Thu, 21 Nov 2019 14:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 n_FHQiscTa9x for <sidrops@ietfa.amsl.com>; Thu, 21 Nov 2019 14:41:24 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D617512016E for <sidrops@ietf.org>; Thu, 21 Nov 2019 14:41:24 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1iXv8c-0004nr-LM; Thu, 21 Nov 2019 22:41:23 +0000
Date: Fri, 22 Nov 2019 06:41:20 +0800
Message-ID: <m2eey07sz3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Job Snijders <job@ntt.net>
Cc: sidrops@ietf.org
In-Reply-To: <20191121082436.GG53958@vurt.meerval.net>
References: <20191121082436.GG53958@vurt.meerval.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/0-1m2YFnhDRkOfqBS2YEX64Swhs>
Subject: Re: [Sidrops] update to document status
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 22:41:26 -0000

> As per discussion in the SIDROPS meeting yesterday, can
> draft-ietf-sidrops-validating-bgp-speaker be marked as 'dead'? (for
> clarification: this status is defined in RFC 6174 Section 4.2.6)

job,

i will print a copy and bring it to the reg desk and you can jump up and
down on it and pour cold coffee on it.  :)

but seriously, why are you so exteemely vehement about this one draft?
it's just a mild attempt at doumenting something actually in play.

randy