Re: [Idr] Old WGLC for draft-ietf-idr-bgp-gr-notification [was: Re: WG LC draft-ietf-idr-bgp-gr-notificatoin-02.txt - from 5/27/14 to 6/10/14]

"Susan Hares" <shares@ndzh.com> Mon, 19 December 2016 19:54 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 4D79B12960B for <idr@ietfa.amsl.com>; Mon, 19 Dec 2016 11:54:14 -0800 (PST)
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, HTML_MESSAGE=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 Mr4TqgYMQHce for <idr@ietfa.amsl.com>; Mon, 19 Dec 2016 11:54:13 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 C22C812960A for <idr@ietf.org>; Mon, 19 Dec 2016 11:54:12 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.7.237;
From: "Susan Hares" <shares@ndzh.com>
To: "'John Scudder'" <jgs@juniper.net>
References: <00b901cf79cf$c4a03aa0$4de0afe0$@ndzh.com> <F5977A01-0018-432C-B829-6A7B4695A667@juniper.net> <76AD4ADF-A14F-4CD4-BF43-8DD01E60E390@juniper.net>
In-Reply-To: <76AD4ADF-A14F-4CD4-BF43-8DD01E60E390@juniper.net>
Date: Mon, 19 Dec 2016 14:50:57 -0500
Message-ID: <012a01d25a31$38005950$a8010bf0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_012B_01D25A07.4F2B89D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHj8zmFvh1jk/WZ0RLUyz06hRSFGgMC6nFTANxaQOagzYAwYA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sRlVKBaoao84mVUnZvMOR_MhfXo>
Cc: 'idr wg' <idr@ietf.org>
Subject: Re: [Idr] Old WGLC for draft-ietf-idr-bgp-gr-notification [was: Re: WG LC draft-ietf-idr-bgp-gr-notificatoin-02.txt - from 5/27/14 to 6/10/14]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 19 Dec 2016 19:54:14 -0000

John: 

 

This draft was waiting for 2 implementations.  We were waiting for a confirmation from Cisco.   Perhaps Jakob can help us with the status the implementation of draft-ietf-idr-bgp-gr-notification in IOS implementation.  

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of John Scudder
Sent: Saturday, December 10, 2016 10:05 PM
To: John Scudder
Cc: idr wg; Susan Hares
Subject: Re: [Idr] Old WGLC for draft-ietf-idr-bgp-gr-notification [was: Re: WG LC draft-ietf-idr-bgp-gr-notificatoin-02.txt - from 5/27/14 to 6/10/14]

 

By the way, I would like to encourage implementors to update the (quite dated) implementation report at https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-gr-notification%20implementations

 

Thanks,

--John


On Dec 10, 2016, at 2:50 PM, John Scudder <jgs@juniper.net> wrote:

Hi Everybody, 

 

My mistake, the WGLC wasn't in 2015, it was in 2014 and the last traffic to the thread was 2015 :-o. I think that under the circumstances we probably have to do another one, although I leave the final decision to my co-chair.

 

FYI the diff from the version that was originally WGLC'd to the current one is:https://www.ietf.org/rfcdiff?url1=draft-ietf-idr-bgp-gr-notification-02 <http://www.ietf.org/rfcdiff?url1=draft-ietf-idr-bgp-gr-notification-02&url2=draft-ietf-idr-bgp-gr-notification-09> &url2=draft-ietf-idr-bgp-gr-notification-09. I believe this resolves all issues that were raised.

 

Thanks,

 

--John

 

On May 27, 2014, at 1:19 PM, Susan Hares <shares@ndzh.com> wrote:

 

Working Group,

 

This is to begin a 2 week WG LC for draft-ietf-idr-bgp-gr-notification-02.txt which will end on 6/10/2014.  Please put within your comments:  “support” or “no-support” for WG LC. 

 

Jeff Haas comments that the most recent changes reflect implementation experience and some word smithing.  There is also a minor clarification in the NOTIFICATION message with respect to including a data byte so the original reason for the event can be propagated.  (See sec. 3.1 in the diff.)

 

The abstract is below. 

 

Sue Hares

 

 

----------

 

Abstract:

   The current BGP Graceful Restart mechanism limits the usage of BGP

   Graceful Restart to BGP protocol messages other than a BGP

   NOTIFICATION message.  This document defines an extension to the BGP

   Graceful Restart that permits the Graceful Restart procedures to be

   performed when the BGP speaker receives a BGP NOTIFICATION Message.

   This document also defines a new BGP NOTIFICATION Cease Error subcode

   to prevent BGP speakers supporting the extension defined in this

   document from performing a Graceful Restart.

 

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr