IETF Logo Mail Archive

[bess] Resolutions on draft-snr-bess-evpn-loop-protect &

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Sat, 12 October 2019 00:31 UTC

Return-Path: <sajassi@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2743012010D; Fri, 11 Oct 2019 17:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=Yfm+6+2T; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=VzfhECtg
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 d1wu7xFh26id; Fri, 11 Oct 2019 17:31:47 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995871200E0; Fri, 11 Oct 2019 17:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11845; q=dns/txt; s=iport; t=1570840307; x=1572049907; h=from:to:cc:subject:date:message-id:mime-version; bh=Tyj7/PITrl1ec+N6BULlZOnkz3lUk8deNQidXaqrwA4=; b=Yfm+6+2TlDpJfY1VYhJox/5m7VLEedZIHW1GI1xjintJYdrgexl5H3Wg KMkh43Ym+Kzy/TcjDeRfWInnCk6tsIOt59AOWyuvNX29cDFARuN7Bh/U2 gwDjrc5qFrLR7hyv6+osP+bvGIe+80rP2g6mwLUYUjPAtC0bjMn2fr/tI Q=;
IronPort-PHdr: 9a23:erFwHR3YkxrQ6JIksmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxKHt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQEkT5JeXxbgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DEAABBHqFd/5hdJa1mHAEBAQEBBwEBEQEEBAEBgWkFAQELAYEbLyQsBWxWIAQLKoQjg0cDikmCN5NChGGBLoEkA1QJAQEBDAEBIwoCAQGEQBmCRyM2Bw4CAwkBAQQBAQECAQUEbYUtDIVOFhEKEwEBNwERAUoCBDAnBAENIAeDAAGBeU0DLgECDKdEAoE4iGF1gTKCfQEBBYE4Ag5BgwEYghcDBoE0AYwNGIF/gRAoDBOCTIMfAQEDAYIKgmEygiyNO4I0hTeYIQqCIgOHBY4RG4I6h06ELIsMiD6Fb4gikRUCBAIEBQIOAQEFgVkBMYFYcBVlAYJBUBAUgU8MF4NQhRSFP3SBKZAXAQE
X-IronPort-AV: E=Sophos;i="5.67,286,1566864000"; d="scan'208,217";a="355233756"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Oct 2019 00:31:46 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x9C0Vkks020463 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 12 Oct 2019 00:31:46 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 19:31:45 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 11 Oct 2019 19:31:45 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 11 Oct 2019 20:31:45 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=c2otSjVJJKj0sVXexlR3CAhcQTiRq4jMwU1+Q9QKzGICoIF0XRlFIYMjIze2SRjueEyPJrX3IDF1OuAvXKamNqYxt7SwQpFNCBWEXyQ1wcKZlXu+sSGGZJdbLt4gvoiDkTY2tJMcRm81uH1Uf83ZZ1ietu9N/4NYPXnA1W1BB7c+GkH3MefMRCvmTpZ5MCvp0wGVQVuGcnXLc7r89ZcvEmxzLQ84ozO+QzS234Gj8LbUgPCf6MY2vM8nFN9vbdia8/zwDiZGCCtXLPd7x+x9Tkc1jcjjGSG9TAytPNm9trJQ2Gesvk5qdvBmEvCXszZpx9u8mwGrcji1B4NVnsOSfQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Tyj7/PITrl1ec+N6BULlZOnkz3lUk8deNQidXaqrwA4=; b=demlm2IV9/3LG7Hf/YlIykWhW9FIUYGev0nm760hwojzf387irFU/3lAZID1wbQjOs8LI4gxJ4eDHr+yc/MsiJ6gS5GRGFtVj8OAC9+Voaal0yCYJzysAMYioBf1Cae+3MzcstTUsFpBRxPEci0AhYvnWtXXXYN7YmDwuVkF4nbDpw7p86dhmuofd6MogRCvgVPr0EdD7i20vy8zxc8jko1eaoehWa8yYEM2JiAgmlrcWiQqOotc98nJ89CltMLZCrZKBc+zSkRfDHHORAnOLmzHwaAQzhaKN5j8r0Mq119GbgU0vGxy7BNAeY5Y94cIfjRPNxDc8TcE4kvfsFzHpg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Tyj7/PITrl1ec+N6BULlZOnkz3lUk8deNQidXaqrwA4=; b=VzfhECtgAP1jn1PXUGF5sRL/aB1ug+4EAQTrtdIB7CnuqCLMThb/B4ymcZnr+ABXkVVtMWJrM2ac/mCkJRT/uufWjpnXcsXnrVAMJIQCXrogcvJyBfhWC3120ej6PUKeFgBdvblpPWugHSMOFMapx3ZklPqDCgxW+1n8UW1rVYQ=
Received: from BN8PR11MB3699.namprd11.prod.outlook.com (20.178.218.208) by BN8PR11MB3844.namprd11.prod.outlook.com (20.178.222.88) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.18; Sat, 12 Oct 2019 00:31:44 +0000
Received: from BN8PR11MB3699.namprd11.prod.outlook.com ([fe80::fd99:9153:1ce7:2a74]) by BN8PR11MB3699.namprd11.prod.outlook.com ([fe80::fd99:9153:1ce7:2a74%4]) with mapi id 15.20.2347.021; Sat, 12 Oct 2019 00:31:44 +0000
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "bess@ietf.org" <bess@ietf.org>
CC: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Thread-Topic: Resolutions on draft-snr-bess-evpn-loop-protect &
Thread-Index: AQHVgJRrSqpVUU8nKUOv4iH0qeSdiA==
Date: Sat, 12 Oct 2019 00:31:43 +0000
Message-ID: <93419492-F230-4744-82C7-8C1C2B5AA495@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1d.0.190908
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sajassi@cisco.com;
x-originating-ip: [2001:420:c0c8:1006::155]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7b8a5f50-6037-4483-4b76-08d74eab8eff
x-ms-traffictypediagnostic: BN8PR11MB3844:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <BN8PR11MB3844891DA597E288D7ACFC7EB0960@BN8PR11MB3844.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0188D66E61
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(376002)(366004)(39860400002)(396003)(189003)(199004)(236005)(81156014)(6306002)(8936002)(54896002)(8676002)(81166006)(71200400001)(71190400001)(6512007)(966005)(54906003)(2501003)(4743002)(186003)(2616005)(58126008)(476003)(46003)(486006)(14454004)(606006)(33656002)(110136005)(99286004)(6486002)(102836004)(478600001)(256004)(9326002)(6436002)(7736002)(316002)(6116002)(76116006)(91956017)(25786009)(66946007)(64756008)(66476007)(6506007)(66446008)(36756003)(2906002)(86362001)(4326008)(107886003)(5660300002)(790700001)(66556008); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3844; H:BN8PR11MB3699.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Xrase6/aGaOOCLV+erDX8gSeMMpJdmlJqWik77VLxTnlp6MYbClqaKWzzhQrqgEar3d0ZYid6T2dUaZXhgsqSUye6dAr1IzhFTSmyg2PuvGk01i1HCU8u9ht41u2X1a1In4O+lPRwSx12v/Nyoh5rOsshBD/jH3NnNm3gWnCVJ8l7wHdliAmHcuwdPFZbgNtFJhacS9/v8BC1E+Kk/ih6atXj747FxrEEvcRMOWOa61LB4d37FIHdqYV/O5S35+BSme9lhWikeiqAKoo1820Hbgl3LdU6Uqf5mBddiWR6Og3i7i9pbA6SYLww1AIUj02WoRrQxH3eV4qd8qq1oN6gUncTAHiyugqL55EokO2Esu36bvdKmHl7/0dGSNzbyKoh0OrxQjIAmhdChgroCfPhj/eJPUDl1U9vbRQaswC93uWfcq0MP80DfuB0rgwok/y4F+X7GsJiKK+vLMMSHCCJA==
Content-Type: multipart/alternative; boundary="_000_93419492F230474482C78C1C2B5AA495ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 7b8a5f50-6037-4483-4b76-08d74eab8eff
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2019 00:31:43.9965 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tvvEKyQ9q3qdsmarSV+JvSPNPZQgF7aj/smMP8HE2SLwyA812+mxazmErN8ZieP0sdRaXYTd+csvodXwEEd3BA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3844
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/OFZrda3xtsOgLG6ww4cS1IdfXbE>
Subject: [bess] Resolutions on draft-snr-bess-evpn-loop-protect &
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Oct 2019 00:31:50 -0000

Hi Stephane,


Jorge and I had a meeting to discuss our comments on the following two drafts that are going through WG call:

https://tools.ietf.org/html/draft-snr-bess-pbb-evpn-isid-cmacflush-06
https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

and reached the following resolutions:

On isid-cmacflush, we agreed to proceed with this draft and since we don’t want to have two separate solutions for I-SID flushing in PBB-EVPN, we decided to remove the section on I-SID flushing in virtual-eth-segment. The main factor for this decision was the fact that isid-cmacflush draft has been implemented by at least one vendor; whereas, the isid flusing section in virtual-eth-segment draft has not been implemented by any vendor to best of our knowledge even though the draft at large has been implemented by many vendors. If any of the co-authors or WG individual has any comment about this, please speak up, otherwise we’ll remove the appropriate section.

On loop-protect draft, we agreed on holding its WG adoption at this time and extend mac mobility in rfc7432bis to cover loops. The main factor for this decision was the fact that the detection mechanism for loop-protect draft is the same as mac-duplicate detection mechanism in section 15.1 of RFC 7432. So, we agreed we can build based on that and add some paragraphs to describe the action of loop protection. Once rfc7432bis is out, we would like to encourage people to read it and, unless there is feedback against it, the loop-protect draft will be abandoned. If there is feedback stating 7432bis is not enough for loop protection, at that time we can discuss if the loop-protect draft needs to be resumed and extended or if a new draft is needed.

Regards,
Ali & Jorge

v2.23.0 | Report a Bug | By Email