IETF Logo Mail Archive

Re: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group Last Call (3/30 to 4/13)

Susan Hares <shares@ndzh.com> Wed, 08 April 2020 16:08 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 9F3013A0F2A for <idr@ietfa.amsl.com>; Wed, 8 Apr 2020 09:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.447
X-Spam-Level: *
X-Spam-Status: No, score=1.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, KHOP_HELO_FCRDNS=0.398, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 QWq3O5RjbGw8 for <idr@ietfa.amsl.com>; Wed, 8 Apr 2020 09:08:08 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 1C4133A0F2D for <idr@ietf.org>; Wed, 8 Apr 2020 09:07:59 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.170.25.188;
From: Susan Hares <shares@ndzh.com>
To: "'UTTARO, JAMES'" <ju1738@att.com>, 'IDR List' <idr@ietf.org>
References: <00d101d606b2$7d036c50$770a44f0$@ndzh.com> <32e5358433ae47ee8c6217bc0f1a32fc@att.com>
In-Reply-To: <32e5358433ae47ee8c6217bc0f1a32fc@att.com>
Date: Wed, 08 Apr 2020 12:07:50 -0400
Message-ID: <000301d60dbf$dab073c0$90115b40$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01D60D9E.53A08170"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF1ecGMwNKtmhcYNICGpdpPVFdMMAIBhsURqSB/lBA=
Content-Language: en-us
X-Antivirus: AVG (VPS 200407-0, 04/07/2020), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Q2YQFGTiWEbYcsSxEPJ2aVf8r1I>
Subject: Re: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group Last Call (3/30 to 4/13)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 08 Apr 2020 16:08:10 -0000

Jim:

 

Is this information for public consumption?   If so, can I place it on idr
wiki and shepherd's report. 

 

If not, may I forward the information to Alvaro so he can use it to pass
this work through the IESG. 

 

Thanks,  Sue Hares 

 

From: UTTARO, JAMES [mailto:ju1738@att.com] 
Sent: Wednesday, April 8, 2020 10:04 AM
To: Susan Hares; 'IDR List'
Subject: RE: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group
Last Call (3/30 to 4/13)

 

Sue,

 

              Apologies I could not attend today's IDR meeting. As per our
conversation last week,  AT&T has deployed the following services that
distribute flowspec updates/rules from a centralized controller that depend
on the flowspec-oid technology specification. Note these are all on demand.

 

a.      Edge Blocking 

b.      DDOS Diversion

c.       Traffic Rate Limiting

 

Thanks,

              Jim Uttaro

 

From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
Sent: Monday, March 30, 2020 12:44 PM
To: 'IDR List' <idr@ietf.org>
Subject: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group Last
Call (3/30 to 4/13)

 

This is a 2 week WG LC for  draft-idr-bgp-flowspec-oid-1.txt. 

You may find the draft at: 

 

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-flowspec-oid/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_d
oc_draft-2Dietf-2Didr-2Dbgp-2Dflowspec-2Doid_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicv
jIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=u07uFO3Esv1oju44LBsuc0AQoi7HkiD6lsCmVo8Qsmw&s
=YJZzMD_DisrQZDVVs9UmQg4uGvd9FZZNk7CDGo9vb3I&e=> 

 

Based on our discussion at the 3/30/2020 interim, 

Most  Flow Specification implementations add this feature. 

 

1) draft authors will send a response to this email with their IPR
statements. 

2) draft authors will update the IDR wiki page 

 

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-flowspec-oid%20implem
entations
<https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.ietf.org_trac_idr
_wiki_draft-2Dietf-2Didr-2Dbgp-2Dflowspec-2Doid-2520implementations&d=DwMFAg
&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=u07uFO3Esv1oju44LBsuc0A
Qoi7HkiD6lsCmVo8Qsmw&s=X6dkMmpuFsA4ctk0kmlBG4_l6j_IU500dO6LKWyI9Hg&e=> 

 

3) The WG will run a 2 week WG last call discussion 

 

During this discussion please indicate: 

 

a) What deployments you know about 

  (3rd party information about an implementation is fine)

 

b) Are there any issues with the implementations 

 

c) Is this specification ready for publication? 

 

Cheerily, Sue  Hares

v2.23.0 | Report a Bug | By Email