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

"Bacher, Martin" <> Thu, 02 February 2017 19:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CC76C1294AE for <>; Thu, 2 Feb 2017 11:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eDBtprY6TTMI for <>; Thu, 2 Feb 2017 11:56:25 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4ED8D129474 for <>; Thu, 2 Feb 2017 11:56:24 -0800 (PST)
X-IronPort-MID: 5104267
X-IronPort-Reputation: None
X-IronPort-Listener: DefaultListener
X-IronPort-SenderGroup: TMA_Relay
X-IronPort-MailFlowPolicy: $RELAY
X-HAT: Sender Group TMA_Relay, Policy $RELAY applied.
X-ExtLoop1: 1
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.33,326,1477954800"; d="scan'208";a="5104267"
X-Spam-Processed:, Thu, 02 Feb 2017 20:56:44 +0100 (not processed: spam filter heuristic analysis disabled)
X-MDArrival-Date: Thu, 02 Feb 2017 20:56:44 +0100
From: "Bacher, Martin" <>
To: "John G. Scudder" <>, idr wg <>
Date: Thu, 2 Feb 2017 20:56:15 +0100
Thread-Topic: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"
Thread-Index: AdJ8qik1kqtVr82MS2WR0YPHLJN5eAA4/nMw
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, de-AT
Content-Language: de-DE
acceptlanguage: en-US, de-AT
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Idr] WG adoption call for draft-hr-idr-rfc5575bis-02 "Dissemination of Flow Specification Rules"
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 02 Feb 2017 19:56:28 -0000


I support the adoption of this draft as an co-author.  

Martin Bacher

-----Ursprüngliche Nachricht-----
Von: Idr [] Im Auftrag von John G. Scudder
Gesendet: Mittwoch, 01. Februar 2017 17:42
An: idr wg <>
Betreff: 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.



> On Jan 21, 2017, at 10:03 AM, John G. Scudder <> 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 mailing list

Notice: This e-mail and any attachments are confidential and may be privileged.
If you are not the intended recipient, notify the sender immediately, destroy all
copies from your system and do not disclose or use the information for any purpose.
Diese E-Mail inklusive aller Anhaenge ist vertraulich und koennte bevorrechtigtem
Schutz unterliegen. Wenn Sie nicht der beabsichtigte Adressat sind, informieren Sie
bitte den Absender unverzueglich, loeschen Sie alle Kopien von Ihrem System und
veroeffentlichen Sie oder nutzen Sie die Information keinesfalls, gleich zu welchem Zweck.

Think before you print!

T-Mobile Austria GmbH
Geschaeftsfuehrung: Dr. Andreas Bierwirth (Vorsitzender), Aufsichtsrat: Branka Skaramuca (Vorsitzende)
Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 171112k, UID ATU 45011703, DVR 0898295
Konto: UniCredit Bank Austria AG IBAN: AT93 1200 0528 4407 2301, BIC: BKAUATWW

T-Mobile – Das verbindet uns.