[Idr] draft-ietf-bess-nsh-bgp-control-plane contains new Flowspec action

John Scudder <jgs@juniper.net> Mon, 29 April 2019 17:27 UTC

Return-Path: <jgs@juniper.net>
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 30C7F1205D1 for <idr@ietfa.amsl.com>; Mon, 29 Apr 2019 10:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.338
X-Spam-Level:
X-Spam-Status: No, score=-1.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 htRZPO0qbGux for <idr@ietfa.amsl.com>; Mon, 29 Apr 2019 10:27:19 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 31F971205D4 for <idr@ietf.org>; Mon, 29 Apr 2019 10:27:12 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3THPExL023196; Mon, 29 Apr 2019 10:27:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=sofsWTPI2bEtbos+XKXOrZ29QIjSFb+W2bxZyhsVllY=; b=t8SgoNpMKPfT8tLRuw1TGoLIJtpHNub7+ppWs5o1h7sqRcwGNzlY11cy28zxB8msuCuT d66d9eU7rq0+3l+nWPFjRGkeW9zTy+0PzsLn/30+Fp7VCW/2ud3MEOzs8AI4ej1GvHhC q/VO1bKkp2kEyok5pyiCM0rR7lSu518fF15nBfvc5fcPbZltA4NWGF9+jipp5+ZkTK4v akmf72mspzcR3sTsBkwZVBvM48LnilVk9kihKMOIYm3ajaL5lee/vZ3xFkM9RrJrbtg+ wImdCo75P3MbtilEcbnlmCa+zPgRLe7PvgXoWSntzDTS1vzGbvBfIKxPZ0LyhMdXHJv4 OA==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp2050.outbound.protection.outlook.com [104.47.42.50]) by mx0b-00273201.pphosted.com with ESMTP id 2s62gn0a6b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Apr 2019 10:27:10 -0700
Received: from DM6PR05MB4714.namprd05.prod.outlook.com (20.176.109.215) by DM6PR05MB5995.namprd05.prod.outlook.com (20.178.29.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.5; Mon, 29 Apr 2019 17:27:07 +0000
Received: from DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1523:af80:389f:efb5]) by DM6PR05MB4714.namprd05.prod.outlook.com ([fe80::1523:af80:389f:efb5%2]) with mapi id 15.20.1835.010; Mon, 29 Apr 2019 17:27:07 +0000
From: John Scudder <jgs@juniper.net>
To: "idr@ietf.org" <idr@ietf.org>
CC: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, Hares Susan <shares@ndzh.com>
Thread-Topic: draft-ietf-bess-nsh-bgp-control-plane contains new Flowspec action
Thread-Index: AQHU/rDF8UQjI4W2JkaH3SVoYXhUqw==
Date: Mon, 29 Apr 2019 17:27:07 +0000
Message-ID: <B5A970EA-2C05-4B37-B9F4-4B24B4CD1335@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [162.225.191.79]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7db188a1-5c71-49a2-9a6e-08d6ccc7e7b3
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:DM6PR05MB5995;
x-ms-traffictypediagnostic: DM6PR05MB5995:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DM6PR05MB5995B3356FE82DA9BE92DEC5AA390@DM6PR05MB5995.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0022134A87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(366004)(136003)(39860400002)(376002)(53754006)(199004)(189003)(2616005)(1730700003)(33656002)(8936002)(476003)(68736007)(14454004)(966005)(486006)(6916009)(478600001)(3846002)(2906002)(73956011)(6116002)(54906003)(2501003)(99286004)(71200400001)(76116006)(66476007)(66946007)(91956017)(66446008)(66556008)(64756008)(83716004)(66066001)(6506007)(71190400001)(5660300002)(102836004)(5640700003)(256004)(6436002)(36756003)(86362001)(97736004)(6512007)(6486002)(25786009)(4326008)(316002)(82746002)(305945005)(186003)(26005)(2351001)(7736002)(53936002)(81156014)(8676002)(81166006)(6306002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB5995; H:DM6PR05MB4714.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Qng7IVgRc1692pE/m6n2HQBeMIzyI7vQ0cx5naktD7sRwAaOphZpSKM5/WtC2buyAAllZbvUkM61joSD2HdEF+xGFyrTCSUI1zjQvPBFiy04FmZJtElX6wZmvem7Ww7gzzRgrCbThEIAv1xygNttJ4iS1Hsl2bu4idhoRqOyAbHFchDMrw7A3oM/wzvf5eRx8kCz3KCzICQRY+q6IQuXs10ew+t+bcxLT85XfLQf3cfdFg4AuZ4TsmEesKZz7IHenhW/MEbTM6jwIX7Sy4JDg7kaq8qBepo7mvfPxjZ2o8JGuRpvlUhKK8rx3s+aDP+V+MIQhb/8gh72k+HNoWe8WoD1aFKJNCj8Q2TnqtmGULhoGKfKexnHL3mrs/0q4pRzYL8iX4CRVWdzZxX7OkwJxMVYWU/aGYNzO25WzoC58eA=
Content-Type: text/plain; charset="utf-8"
Content-ID: <E6B80B2D0BF05844ABEA1A30988A4A36@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 7db188a1-5c71-49a2-9a6e-08d6ccc7e7b3
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Apr 2019 17:27:07.6248 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB5995
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-29_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=905 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904290119
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lOZJ15EAJEW0H5naeQsM77l1moU>
Subject: [Idr] draft-ietf-bess-nsh-bgp-control-plane contains new Flowspec action
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: Mon, 29 Apr 2019 17:27:21 -0000

Hi All,

Stephane Litkowski pointed out to Sue and me that draft-ietf-bess-nsh-bgp-control-plane contains a new Flowspec action to redirect the traffic on a Service Function Path, in section 7.4:
https://tools.ietf.org/html/draft-ietf-bess-nsh-bgp-control-plane-10#page-33

I’ve already provided the feedback that rfc5575bis asks that the new action specify its interaction and error handling:

   Some traffic action communities may interfere with each other.
   Section 7.6 of this specification provides general considerations on
   such traffic action interference.  Any additional definition of a
   traffic actions specified by additional standards documents or vendor
   documents MUST specify if the traffic action interacts with an
   existing traffic actions, and provide error handling per [RFC7606].

I hope the IDR WG will take a look at the draft, at least section 7.4, and provide any further review. Note that it has already passed WGLC in BESS and is currently in shepherd’s review (almost completed) so although there is no specific deadline, time is of the essence — please raise any additional concerns promptly.

Thanks,

—John