Return-Path: 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 D06D73A0CC2 for ; Wed, 8 Apr 2020 09:22:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.798 X-Spam-Level: X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-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 M2NNrVgj4xhc for ; Wed, 8 Apr 2020 09:22:01 -0700 (PDT) Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E5903A0CA0 for ; Wed, 8 Apr 2020 09:22:01 -0700 (PDT) Received: from pps.filterd (m0049458.ppops.net [127.0.0.1]) by m0049458.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 038GCLrZ023454; Wed, 8 Apr 2020 12:22:00 -0400 Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049458.ppops.net-00191d01. with ESMTP id 3091nwpq5y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 08 Apr 2020 12:22:00 -0400 Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 038GLxGM001096; Wed, 8 Apr 2020 12:21:59 -0400 Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [135.47.91.179]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 038GLpQB000917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Apr 2020 12:21:51 -0400 Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id 224914009E66; Wed, 8 Apr 2020 16:21:51 +0000 (GMT) Received: from GAALPA1MSGHUBAB.ITServices.sbc.com (unknown [130.8.218.151]) by zlp30484.vci.att.com (Service) with ESMTPS id 0B6984009E65; Wed, 8 Apr 2020 16:21:51 +0000 (GMT) Received: from GAALPA1MSGEX1BA.ITServices.sbc.com (135.50.89.102) by GAALPA1MSGHUBAB.ITServices.sbc.com (130.8.218.151) with Microsoft SMTP Server (TLS) id 14.3.487.0; Wed, 8 Apr 2020 12:21:49 -0400 Received: from GAALPA1MSGEX1BE.ITServices.sbc.com (135.50.89.106) by GAALPA1MSGEX1BA.ITServices.sbc.com (135.50.89.102) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 8 Apr 2020 12:21:49 -0400 Received: from GAALPA1MSGEX1BE.ITServices.sbc.com ([135.50.89.106]) by GAALPA1MSGEX1BE.ITServices.sbc.com ([135.50.89.106]) with mapi id 15.01.1913.007; Wed, 8 Apr 2020 12:21:49 -0400 From: "UTTARO, JAMES" To: Susan Hares , "'IDR List'" Thread-Topic: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group Last Call (3/30 to 4/13) Thread-Index: AdYGsjkGouveGy3sT42zRQgNbUUoFQG+68lgAAzeNAAAB+e74A== Date: Wed, 8 Apr 2020 16:21:49 +0000 Message-ID: <5948c51db2a942b989cc2051d4e71c58@att.com> References: <00d101d606b2$7d036c50$770a44f0$@ndzh.com> <32e5358433ae47ee8c6217bc0f1a32fc@att.com> <000301d60dbf$dab073c0$90115b40$@ndzh.com> In-Reply-To: <000301d60dbf$dab073c0$90115b40$@ndzh.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.70.132.73] Content-Type: multipart/alternative; boundary="_000_5948c51db2a942b989cc2051d4e71c58attcom_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-04-07_10:2020-04-07, 2020-04-07 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 lowpriorityscore=0 phishscore=0 suspectscore=0 mlxscore=0 spamscore=0 clxscore=1015 bulkscore=0 adultscore=0 priorityscore=1501 mlxlogscore=999 malwarescore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004080126 Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2020 16:22:03 -0000 --_000_5948c51db2a942b989cc2051d4e71c58attcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Sue, Let me double check with the manager of this team.. Thanks, Jim Uttaro From: Susan Hares Sent: Wednesday, April 08, 2020 12:08 PM To: UTTARO, JAMES ; 'IDR List' Subject: RE: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group L= ast Call (3/30 to 4/13) 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 th= is 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 L= ast 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 dist= ribute 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 > On Behalf Of = Susan Hares Sent: Monday, March 30, 2020 12:44 PM To: 'IDR List' > 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/ 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 statemen= ts. 2) draft authors will update the IDR wiki page https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-flowspec-oid%20imple= mentations 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 --_000_5948c51db2a942b989cc2051d4e71c58attcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Su= e,

 

&n= bsp;            = ; Let me double check with the manager of this team..=

 

Th= anks,

&n= bsp;            = ; Jim Uttaro

 

From: Susan Hares <shares@ndzh.com> Sent: Wednesday, April 08, 2020 12:08 PM
To: UTTARO, JAMES <ju1738@att.com>; 'IDR List' <idr@ietf.or= g>
Subject: RE: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working = Group Last Call (3/30 to 4/13)

 

Jim:=

 

Is this information fo= r public consumption?   If so, can I place it on idr wiki and she= pherd’s report.

 

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

 

Thanks,  Sue Hare= s

 

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)

 

Su= e,

 

&n= bsp;            = ; Apologies I could not attend today’s IDR meeting. As per our conver= sation last week,  AT&T has deployed the following services that d= istribute 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

 

Th= anks,

&n= bsp;            = ; 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&= gt;
Subject: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Grou= p Last Call (3/30 to 4/13)

 

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

You may find the draft at:

 

https://datatracker.ietf.or= g/doc/draft-ietf-idr-bgp-flowspec-oid/

 

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

Most  Flow Specification implementations add th= is 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%20implementa= tions

 

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

 

During this discussion please indicate: <= /p>

 

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

 

 

--_000_5948c51db2a942b989cc2051d4e71c58attcom_--