Re: [Idr] Progressing draft-ietf-idr-rfc5575bis -- implementation reports?

Jeffrey Haas <jhaas@pfrc.org> Tue, 26 June 2018 18:24 UTC

Return-Path: <jhaas@pfrc.org>
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 B25E8130E20; Tue, 26 Jun 2018 11:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ccy_l9SyIVbV; Tue, 26 Jun 2018 11:24:12 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 9812F130E0F; Tue, 26 Jun 2018 11:24:12 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id C73AC1E3CE; Tue, 26 Jun 2018 14:24:05 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_74CEA584-9799-4EDC-8518-471C87ABEE13"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <C72DE5DD-3455-4787-A847-B8D29126ADA4@juniper.net>
Date: Tue, 26 Jun 2018 14:24:09 -0400
Cc: "draft-ietf-idr-rfc5575bis@ietf.org" <draft-ietf-idr-rfc5575bis@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Message-Id: <6EEDC008-A5C1-4019-8D65-F2F43DA42901@pfrc.org>
References: <289A4A15-675C-4C56-810D-B5809434A669@juniper.net> <7868BEF8-7B24-43BD-B36A-6C621D17D14A@pfrc.org> <C72DE5DD-3455-4787-A847-B8D29126ADA4@juniper.net>
To: John Scudder <jgs@juniper.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jtQgkmyzJIweliYV2lxHgXUXv88>
Subject: Re: [Idr] Progressing draft-ietf-idr-rfc5575bis -- implementation reports?
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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, 26 Jun 2018 18:24:16 -0000

John,

> On Jun 26, 2018, at 1:47 PM, John Scudder <jgs@juniper.net> wrote:
> On Jun 26, 2018, at 10:46 AM, Jeffrey Haas <jhaas@pfrc.org <mailto:jhaas@pfrc.org>> wrote:
>> 
>> An open point on the mailing list though has been whether the ipv6 flowspec work should be merged in.  See prior comments from Sue.
>> 
>> I'm personally ambivalent about doing that bit of merge work, but it's a good fit as long as the Working Group doesn't feel it's an issue to encumber the update to the core spec with the IPv6 stuff which is optional.  But if so, we'd need to see a merge to continue.
> 
> Unless I've missed it, there hasn't been an outcry from the WG to roll the work in. On the balance, my take (with co-chair propeller beanie on) is that since we are so far along with progressing 5575bis, and as Christop previously has pointed out, the original scope was set to be "clarification" and not more, we shouldn't hold it up further.
> 
> This is not to say the work isn't important or relevant, just that we have a doc pretty much ready for publication, respinning it now is maybe not the best use of anyone's time.

As I mentioned, I'm ambivalent.  

That said, I promise to have provided review by IETF in Montreal.
I'd ask the WG chairs to push for refreshing of the v6 spec and a subsequent WGLC after we've advanced the bis and hopefully have incorporated -bis learnings into the v6 spec.

-- Jeff (two birds, an iterative number of stones)