Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly?

"Susan Hares" <shares@ndzh.com> Thu, 20 July 2017 08:59 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 9C13C12ECCB; Thu, 20 Jul 2017 01:59:06 -0700 (PDT)
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 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 oQOvP7np7QVw; Thu, 20 Jul 2017 01:59:05 -0700 (PDT)
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 0D92B129B40; Thu, 20 Jul 2017 01:59:04 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.141.64;
From: Susan Hares <shares@ndzh.com>
To: 'Job Snijders' <job@ntt.net>, 'Christopher Morrow' <christopher.morrow@gmail.com>
Cc: idr@ietf.org, grow@ietf.org
References: <001c01d3012d$d55f3920$801dab60$@ndzh.com> <CAL9jLaaqevUU8_20BERVrZ5P1xL7GNuhAcTrJT4Nm4NVaAYyzg@mail.gmail.com> <20170720084207.aprg44zv26y5wo3y@Vurt.local>
In-Reply-To: <20170720084207.aprg44zv26y5wo3y@Vurt.local>
Date: Thu, 20 Jul 2017 04:52:58 -0400
Message-ID: <008d01d30135$96c3b8a0$c44b29e0$@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: AQE1HBtGRW8wMtBhjg9X2oQYXEAYSQKRllTpAUp6yWqjeVHoAA==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/e6KX4JTO8iYzYNhvSGhYZL4Em6k>
Subject: Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 08:59:07 -0000

Job: 

If this solution was good was the best solution,  there is no further work. 

If this solution was due to the slow progress of IDR, I'd like to know.
We've been trying to fast track all operator needs. 

Sue 

-----Original Message-----
From: Job Snijders [mailto:job@ntt.net] 
Sent: Thursday, July 20, 2017 4:42 AM
To: Christopher Morrow
Cc: Susan Hares; idr@ietf.org List; grow@ietf.org grow@ietf.org
Subject: Re: [Idr] Are there IDR drafts the Grow WG needs completed quickly?

On Thu, Jul 20, 2017 at 10:33:04AM +0200, Christopher Morrow wrote:
> On Thu, Jul 20, 2017 at 9:57 AM, Susan Hares <shares@ndzh.com> wrote:
> > As the IDR co-chairs sat in the grow meeting, we heard of an IDR 
> > draft that was so long in becoming an RFC that the Grow authors took 
> > another approach (which was less desired).
> 
> I'm unsure what draft this is? this might be the gshut draft?  

GROW's draft-ietf-grow-bgp-gshut had a dependency on
draft-ietf-idr-reserved-extended-communities which related to
draft-ietf-idr-as4octet-extcomm-generic-subtype - eventually this was
resolved by just working with RFC 1997 well-known communities.

Kind regards,

Job