Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt

"Susan Hares" <shares@ndzh.com> Thu, 06 February 2014 15:39 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549AE1A01E8 for <idr@ietfa.amsl.com>; Thu, 6 Feb 2014 07:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level:
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=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 eoGhfza3m9m1 for <idr@ietfa.amsl.com>; Thu, 6 Feb 2014 07:39:39 -0800 (PST)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id 455B01A018E for <idr@ietf.org>; Thu, 6 Feb 2014 07:39:39 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=64.112.195.202;
From: Susan Hares <shares@ndzh.com>
To: 'Jeffrey Haas' <jhaas@pfrc.org>
References: <CF0FD8F8.6170B%keyupate@cisco.com> <007701cf1de8$53571d70$fa055850$@ndzh.com> <20140206152555.GC23551@pfrc>
In-Reply-To: <20140206152555.GC23551@pfrc>
Date: Thu, 06 Feb 2014 10:39:27 -0500
Message-ID: <001201cf2351$9f3dbbe0$ddb933a0$@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: AQIGxPj1Dal1f7T6ogADUl2weXy9pgLjVe5ZAOjZ9xGaGrd/4A==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Cc: "'Keyur Patel (keyupate)'" <keyupate@cisco.com>, idr@ietf.org
Subject: Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 06 Feb 2014 15:39:40 -0000

Jeff: 

Please provide more details on your opinion on this information to the list:


"Personally, I think it'd be wise to not process the enhanced RR procedures
until GR is complete but I think that can be an implementation decision."
(The justification is that there's a *lot* of work going on while processing
GR and it's more valuable to get RIBs in some initial state of
synchronization rather than worry about trying to fill in holes that might
be present in the midst of it.)

Sue Hares

-----Original Message-----
From: Jeffrey Haas [mailto:jhaas@pfrc.org] 
Sent: Thursday, February 06, 2014 10:26 AM
To: Susan Hares
Cc: 'Keyur Patel (keyupate)'; idr@ietf.org
Subject: Re: [Idr] draft-ietf-idr-bgp-enhanced-route-refresh-06.txt

On Thu, Jan 30, 2014 at 01:23:07PM -0500, Susan Hares wrote:
> IDR WG:
> 
> We will have a 1 week WG LC on this version of the 
> draft-ietf-idr-bgp-enhanced-route-refresh-06.txt
> 
> Please comment.  It would help if you would indicate: 
> support/no-support in your discussion.

I continue to support the draft.  I think the clarifications for covering
end-of-rib procedures (regardless of whether GR is being used or not) are
valuable.

Personally, I think it'd be wise to not process the enhanced RR procedures
until GR is complete but I think that can be an implementation decision.
(The justification is that there's a *lot* of work going on while processing
GR and it's more valuable to get RIBs in some initial state of
synchronization rather than worry about trying to fill in holes that might
be present in the midst of it.)

-- Jeff