Re: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"

"Susan Hares" <shares@ndzh.com> Thu, 02 February 2017 18:33 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 49F581298C1 for <idr@ietfa.amsl.com>; Thu, 2 Feb 2017 10:33:38 -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 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 CwN9p6cyrDoX for <idr@ietfa.amsl.com>; Thu, 2 Feb 2017 10:33:36 -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 AF916129509 for <idr@ietf.org>; Thu, 2 Feb 2017 10:33:36 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.36.162.137;
From: "Susan Hares" <shares@ndzh.com>
To: "'John G. Scudder'" <jgs@juniper.net>, "'idr wg'" <idr@ietf.org>
References: <36E285C0-C716-437A-806D-A453273146DD@juniper.net> <1D651738-BCED-4F25-88B5-5257871697DA@juniper.net>
In-Reply-To: <1D651738-BCED-4F25-88B5-5257871697DA@juniper.net>
Date: Thu, 2 Feb 2017 13:29:19 -0500
Message-ID: <01a401d27d82$44f25b80$ced71280$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIgMsv1YXbB2Jqp0eajZl6T0Qh3WQII4s4woKpXndA=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/hNiaPld7SbUekhxBfQrUFctT1a8>
Subject: Re: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"
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: Thu, 02 Feb 2017 18:33:38 -0000

<WG chair hat off> 
<individual contributor hat on> 

I support adoption of this work as a co-author.  

Sue Hares 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of John G. Scudder
Sent: Wednesday, February 1, 2017 11:42 AM
To: idr wg
Subject: Re: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"

Hi All,

Reminder, this call for adoption is going on and will end in five days. So far, the only reply has been from Christoph (thanks!) with a pointer to his paper "BGP Flow Specification Multi Vendor and Inter AS Interoperability". The paper is long, but I encourage you to look at it. To encourage you, here are a few excerpts from the conclusion:

"we think that what we listed as bugs sometimes is a result of unclear sections and definitions in RFC 5575"

"With this update we think that a proper interoperable implementation should be possible and unambiguous sections have been improved"

and perhaps most motivational to the WG:

"Given the current bugs, interoperability issues and missing features we do not recommend flow specification BGP sessions between different carriers […] Invalid flow specification NLRIs or action filters have the potential to remotely trigger a complete network failure."

If you do NOT support adopting this work, it would be interesting to hear why. For example, do you think RFC 5575 is fine as it is, and if so, why (considering the issues raised in the paper and on the list). Of course, it is not IDR's job to document and fix implementation bugs. But it is *exactly* our job to fix the spec if it's ambiguous and that ambiguity leads to interoperability issues.

If you do support adopting the work, please remember to say so on the list — we can't declare consensus based on silence.

Thanks,

—John

> On Jan 21, 2017, at 10:03 AM, John G. Scudder <jgs@juniper.net> wrote:
> 
> Hi All,
> 
> The authors have requested IDR working group adoption of draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules". Please send your comments to the list.
> 
> This adoption call will conclude on Monday, February 6.
> 
> Thanks,
> 
> —John
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

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