Re: [Idr] request for WGLC for draft-ietf-idr-rfc8203bis
"Susan Hares" <shares@ndzh.com> Tue, 30 April 2019 12:27 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACAA12004F for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 05:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, URIBL_BLOCKED=0.001] autolearn=no 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 hF20UPT_ZC4O for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 05:27:04 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 21F9E12004E for <idr@ietf.org>; Tue, 30 Apr 2019 05:27:04 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.176.248.72;
From: Susan Hares <shares@ndzh.com>
To: 'Job Snijders' <job@ntt.net>, idr@ietf.org
References: <20190429225941.GD96687@vurt.meerval.net>
In-Reply-To: <20190429225941.GD96687@vurt.meerval.net>
Date: Tue, 30 Apr 2019 08:26:55 -0400
Message-ID: <00c101d4ff50$00270210$00750630$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJSwwp2mVLzsHoduY9SWnlxV0JnjqVZD5Eg
Content-Language: en-us
X-Antivirus: AVG (VPS 190430-2, 04/30/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/KJlkhL3wgcJEiejtZHYxBs0xPwg>
Subject: Re: [Idr] request for WGLC for draft-ietf-idr-rfc8203bis
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Apr 2019 12:27:05 -0000
Job: We can start the WG Last call on 5/2 (when our current sequence of WG adoption calls is complete). In preparation, please update the idr wiki page with the implementation reports at the particular location. https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-rfc8203bis I have sent out the IPR call. If all your co-authors send in IPR by May 2nd, I can start the WG LC on May 2nd. I would appreciate if you have your implementation reports filled in by May 2nd as well. Cheerily, Sue -----Original Message----- From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Job Snijders Sent: Monday, April 29, 2019 7:00 PM To: idr@ietf.org Subject: [Idr] request for WGLC for draft-ietf-idr-rfc8203bis Dear WG, I'd like to ask the chairs to consider starting a working group last call for draft-ietf-idr-rfc8203bis-04 to progress the document towards RFC publication. At the moment of writing there are 3 implementations (Juniper Junos, OpenBSD OpenBGPD, and a patch has been submitted to NIC.CZ's BIRD project). Kind regards, Job ----- Forwarded message from internet-drafts@ietf.org ----- Date: Mon, 29 Apr 2019 15:53:52 -0700 From: internet-drafts@ietf.org To: Job Snijders <job@ntt.net>, Jakob Heitz <jheitz@cisco.com>, Alexander Azimov <a.e.azimov@gmail.com>, John Scudder <jgs@juniper.net> Subject: New Version Notification for draft-ietf-idr-rfc8203bis-04.txt A new version of I-D, draft-ietf-idr-rfc8203bis-04.txt has been successfully submitted by Job Snijders and posted to the IETF repository. Name: draft-ietf-idr-rfc8203bis Revision: 04 Title: Extended BGP Administrative Shutdown Communication Document date: 2019-04-29 Group: idr Pages: 7 URL: https://www.ietf.org/internet-drafts/draft-ietf-idr-rfc8203bis-04.txt Status: https://datatracker.ietf.org/doc/draft-ietf-idr-rfc8203bis/ Htmlized: https://tools.ietf.org/html/draft-ietf-idr-rfc8203bis-04 Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc8203bis Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rfc8203bis-04 Abstract: This document enhances the BGP Cease NOTIFICATION message "Administrative Shutdown" and "Administrative Reset" subcodes for operators to transmit a short freeform message to describe why a BGP session was shutdown or reset. This document updates RFC 4486 and obsoletes RFC 8203 by defining an Extended BGP Administrative Shutdown Communication to improve communication using multibyte character sets. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat ----- End forwarded message ----- _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] request for WGLC for draft-ietf-idr-rfc8203… Job Snijders
- Re: [Idr] request for WGLC for draft-ietf-idr-rfc… Susan Hares
- Re: [Idr] request for WGLC for draft-ietf-idr-rfc… Jeffrey Haas