IETF Logo Mail Archive

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

"UTTARO, JAMES" <ju1738@att.com> Wed, 08 April 2020 14:03 UTC

Return-Path: <ju1738@att.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 BCB2D3A0C5F for <idr@ietfa.amsl.com>; Wed, 8 Apr 2020 07:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, 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 N6IzyN2rQKNe for <idr@ietfa.amsl.com>; Wed, 8 Apr 2020 07:03:45 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 36AB13A099B for <idr@ietf.org>; Wed, 8 Apr 2020 07:03:45 -0700 (PDT)
Received: from pps.filterd (m0048589.ppops.net [127.0.0.1]) by m0048589.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 038E349f042495; Wed, 8 Apr 2020 10:03:45 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0048589.ppops.net-00191d01. with ESMTP id 3091nuv7st-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 08 Apr 2020 10:03:44 -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 038E3hat031553; Wed, 8 Apr 2020 10:03:43 -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 038E3a5q031351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 8 Apr 2020 10:03:36 -0400
Received: from zlp30484.vci.att.com (zlp30484.vci.att.com [127.0.0.1]) by zlp30484.vci.att.com (Service) with ESMTP id 6E7C04009E66; Wed, 8 Apr 2020 14:03:36 +0000 (GMT)
Received: from GAALPA1MSGHUBAD.ITServices.sbc.com (unknown [130.8.218.153]) by zlp30484.vci.att.com (Service) with ESMTPS id 59D2B4009E65; Wed, 8 Apr 2020 14:03:36 +0000 (GMT)
Received: from GAALPA1MSGEX1BB.ITServices.sbc.com (135.50.89.103) by GAALPA1MSGHUBAD.ITServices.sbc.com (130.8.218.153) with Microsoft SMTP Server (TLS) id 14.3.487.0; Wed, 8 Apr 2020 10:03:35 -0400
Received: from GAALPA1MSGEX1BE.ITServices.sbc.com (135.50.89.106) by GAALPA1MSGEX1BB.ITServices.sbc.com (135.50.89.103) 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 10:03:35 -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 10:03:35 -0400
From: "UTTARO, JAMES" <ju1738@att.com>
To: Susan Hares <shares@ndzh.com>, 'IDR List' <idr@ietf.org>
Thread-Topic: [Idr] draft-ietf-idr-bgp-flowspec-oid-11.txt - Working Group Last Call (3/30 to 4/13)
Thread-Index: AdYGsjkGouveGy3sT42zRQgNbUUoFQG+68lg
Date: Wed, 08 Apr 2020 14:03:35 +0000
Message-ID: <32e5358433ae47ee8c6217bc0f1a32fc@att.com>
References: <00d101d606b2$7d036c50$770a44f0$@ndzh.com>
In-Reply-To: <00d101d606b2$7d036c50$770a44f0$@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_32e5358433ae47ee8c6217bc0f1a32fcattcom_"
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 clxscore=1015 priorityscore=1501 mlxlogscore=999 impostorscore=0 phishscore=0 malwarescore=0 suspectscore=0 bulkscore=0 mlxscore=0 adultscore=0 lowpriorityscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2004080117
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Ohii831vijwTdaOH55rc-OQdsSw>
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 14:03:50 -0000

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.


  1.  Edge Blocking
  2.  DDOS Diversion
  3.  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_doc_draft-2Dietf-2Didr-2Dbgp-2Dflowspec-2Doid_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&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%20implementations<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=u07uFO3Esv1oju44LBsuc0AQoi7HkiD6lsCmVo8Qsmw&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