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

"UTTARO, JAMES" <ju1738@att.com> Tue, 31 March 2020 11:48 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 B7AAD3A18E1 for <idr@ietfa.amsl.com>; Tue, 31 Mar 2020 04:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.102
X-Spam-Level:
X-Spam-Status: No, score=0.102 tagged_above=-999 required=5 tests=[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 73hN9YbKyVtY for <idr@ietfa.amsl.com>; Tue, 31 Mar 2020 04:48:43 -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 9C1813A18DC for <idr@ietf.org>; Tue, 31 Mar 2020 04:48:43 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 02VBfwkE021499; Tue, 31 Mar 2020 07:48:43 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049297.ppops.net-00191d01. with ESMTP id 302m3wuhrf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 31 Mar 2020 07:48:42 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 02VBmfWa014465; Tue, 31 Mar 2020 07:48:41 -0400
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [135.66.87.31]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 02VBma56013693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2020 07:48:36 -0400
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [127.0.0.1]) by zlp27127.vci.att.com (Service) with ESMTP id EE605400AE37; Tue, 31 Mar 2020 11:48:35 +0000 (GMT)
Received: from MISOUT7MSGHUBAC.ITServices.sbc.com (unknown [130.9.129.147]) by zlp27127.vci.att.com (Service) with ESMTPS id D9D37400AE36; Tue, 31 Mar 2020 11:48:35 +0000 (GMT)
Received: from MISOUT7MSGUSRCD.ITServices.sbc.com ([169.254.4.201]) by MISOUT7MSGHUBAC.ITServices.sbc.com ([130.9.129.147]) with mapi id 14.03.0487.000; Tue, 31 Mar 2020 07:48: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: AdYGsjkGouveGy3sT42zRQgNbUUoFQAn/J7Q
Date: Tue, 31 Mar 2020 11:48:35 +0000
Message-ID: <B17A6910EEDD1F45980687268941550F4DA70083@MISOUT7MSGUSRCD.ITServices.sbc.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.127.156]
Content-Type: multipart/alternative; boundary="_000_B17A6910EEDD1F45980687268941550F4DA70083MISOUT7MSGUSRCD_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.676 definitions=2020-03-31_04:2020-03-31, 2020-03-31 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 impostorscore=0 phishscore=0 spamscore=0 malwarescore=0 mlxscore=0 lowpriorityscore=0 bulkscore=0 clxscore=1011 adultscore=0 mlxlogscore=735 suspectscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003310107
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/yYX9bhbeV68ckYrqV_G0gk9AlMY>
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: Tue, 31 Mar 2020 11:48:45 -0000

Sue,

              I am not aware of any IPR on this draft.

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