IETF Logo Mail Archive

Re: [bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding

"Ali Sajassi (sajassi)" <sajassi@cisco.com> Tue, 12 February 2019 03:02 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 4672F130DE3 for <bess@ietfa.amsl.com>; Mon, 11 Feb 2019 19:02:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, 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, 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=AHABom7I; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=j7ISQXtq
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 a58DJEZDRejs for <bess@ietfa.amsl.com>; Mon, 11 Feb 2019 19:02:39 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98D98129B88 for <bess@ietf.org>; Mon, 11 Feb 2019 19:02:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8987; q=dns/txt; s=iport; t=1549940559; x=1551150159; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=+zr7EZW/gRZNU+OmVuwDFSWtoH1ycJFvGpdhvlduSQM=; b=AHABom7IAbYEQ5r3/CUfZnoGq6jHaWFZe/LiScuIz+c3lvS53k7UhYos HvlaiZYQfNpgGBrTsccEk4QJw3gLxPbXRD2RjR2K4/IS0azdo+ZC3CRCs riMyL/Ldug3gNFskkJmJnLTyMXrPHNuuvkqqyqCaGf40+JHZrsdVnR1on U=;
IronPort-PHdr: 9a23:1wUP7RIkJZtFoOmD7tmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvad2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXFbyLvfxdC0SF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAAAnNmJc/49dJa1jGwEBAQEDAQEBBwMBAQGBUQYBAQELAYENI1ADZ3QECyeEBINHA4RQiyeCV4kqiHqFb4EkA1QLAQEshEACF4MoIjQJDQEDAQECAQECbRwMhUoBAQEBAyMdAQE4DwIBCBEDAQIeDQICAh8RHQgCBAESgyQBgR1MAxUBAqB2AooUcYEvgngBAQWCRYJADQuCCwiMQxeBf4ERJx+CTIJXgkoYglExgiaQHocTiz0zCQKPE4M7GZJgijOGaYp5AgQCBAUCDQEBBYFGOIFWcBVlAYJBghyDbopTcoEojQ4BAQ
X-IronPort-AV: E=Sophos;i="5.58,361,1544486400"; d="scan'208,217";a="516577151"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Feb 2019 03:02:22 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id x1C32McA031286 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 Feb 2019 03:02:22 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 Feb 2019 21:02:22 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 11 Feb 2019 22:02:20 -0500
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Mon, 11 Feb 2019 21:02:20 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+zr7EZW/gRZNU+OmVuwDFSWtoH1ycJFvGpdhvlduSQM=; b=j7ISQXtqml7x2hZqyL4qZoZhWtZtyBv+uU+hhv8DDDftU84pBxHk5Ev+jmClxr8IWD2tvSjp1re2jqRYBfwfJDHxGCuqDQO6NMdmGBk5KjEZR4ZatcxTL5VJv7SBYXaWnYSKB3wX7eArf4LfLaS5MnICCLw3Fk+l/dvjRaawnOg=
Received: from DM6PR11MB3692.namprd11.prod.outlook.com (20.178.231.138) by DM6PR11MB3401.namprd11.prod.outlook.com (20.176.123.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1601.22; Tue, 12 Feb 2019 03:02:19 +0000
Received: from DM6PR11MB3692.namprd11.prod.outlook.com ([fe80::78ce:fef4:632b:b820]) by DM6PR11MB3692.namprd11.prod.outlook.com ([fe80::78ce:fef4:632b:b820%4]) with mapi id 15.20.1601.023; Tue, 12 Feb 2019 03:02:19 +0000
From: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
To: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding
Thread-Index: AQHUvdOeA0CecBxKZkusIcb9rnGTC6Xa/PYA
Date: Tue, 12 Feb 2019 03:02:19 +0000
Message-ID: <B5086259-4B1F-4A9B-9AD0-AD240FC0F647@cisco.com>
References: <CAKz0y8xjC10J-g0t05CW_-RGAf-7T+R=Hx_dQvxfhAKbD3f9tA@mail.gmail.com>
In-Reply-To: <CAKz0y8xjC10J-g0t05CW_-RGAf-7T+R=Hx_dQvxfhAKbD3f9tA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.6.190114
x-originating-ip: [2001:420:c0c8:1008::32d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d42f37c4-d029-4160-79b2-08d690968091
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600110)(711020)(4605077)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:DM6PR11MB3401;
x-ms-traffictypediagnostic: DM6PR11MB3401:
x-microsoft-exchange-diagnostics: 1;DM6PR11MB3401;23:QFtaipLmrx+PyPvasas3Fm0sPo/2SM2kbgSmUzLACNjNHlg3oAdho7Kll6h9S6SL6qFOTjBdvUmASpbFE3v9Tr6tYSsaUIAkJmMqTTbeaNsXpsvOf6VvzZBewT1ROF7SM+sMczAZGvFAkBfXryeMex6s66BpkiXyiLboV1l0Ykc3YH68VxQxiO/zfPnC/HkHFkVlA0B/qRyy+yY49n/NZh2pGSM5f1jCBkq4N3AeJqx+iJwAUDDRcPvIMW3n73K8s7m0l+b4VUSPbcvK0yL5QBRDpROq7qQzSoDl5/wfiypFshtYoDYAM2NzmeItEQCRtqzGkjWZ6lIoVXmV4AyIQ4pHWEQOoBplVvxiWwW7ONvwFJzovkn6+62HiCNNvKut8qPB/yZB7HqGk+awrn08Zhr+F4Iwk5IRR3VH+llaRKq0arqKeSBlybZh7kLw74MDrUifZRa8PHXT/9/M31uWcAF8Yhu+WWF8koIgHbWF1y003UxSytDIQV7OM/RgBetHfTShgveZW3pfdjuBqQmjvjjRjwjKD7Y3oQFM99p5A7MOeo+Oh5eaisZgQ+eILdf6Ria2pA+wncx6rh71xGQgn7J0aCY3T1E711xlY6ipCoklBIHpaRCgVL+1Zetmbsyi0Sp57aSdCLklLiX3K+5WOlEc3LOlTdNzrkEWHcavtL9BtIeGVKTYfy6peUvMvdJ90CPABz94mp8npg1xK1oRbMdBDx4YZ3FfTRZy+TyIIavXJfz1OBSrAZduy3QE4pvBHjx1ylm7oLPEp6TSbrwSXQb3s/lVz4GEtQYkFeY03VBE+Vu7DZgbZo6NSLNtexRBpmvOZ18Gc21TYa4krjPcB5CdzWARq4XCp0DZrku+97nCzgDGNns0lFJtC7vNY2vp5lovOr6eMG4g0BKKYYFLE/qLjvkdlc/OCAQcrCwLDjBmThsulWy+Z7rjI3B7/eXB/yQJKbF6TJX4JIr684IE4TA8I9a8i97DAtEoFTo6uO5R7YO7A+6eP5jrzBO8XXankym1xqaAtrvgm6Bd3aVt3WYZyfEnUC6CbvGiWTiegZ94PMxd7zDRhFRt9MrjUIRFNKcJJ4ClAlnrbvr1dfJ3Wz00ly8SyvZO8VXPr4va8EqlUk+k4O4sxqyMNGeUHxE8LUx+PClMQrqzU9UVykHZhHWNh99Ik8ayxGIqt36saaXPi+G0kTEKn23m/ru1AVdy1cVoeDaHR1Ak/GiH8DKfdQ==
x-microsoft-antispam-prvs: <DM6PR11MB34017463F098E31770F301F4B0650@DM6PR11MB3401.namprd11.prod.outlook.com>
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(39860400002)(376002)(136003)(346002)(189003)(199004)(478600001)(46003)(6512007)(58126008)(316002)(99286004)(229853002)(36756003)(68736007)(81156014)(33656002)(11346002)(6436002)(110136005)(446003)(14454004)(2616005)(2906002)(476003)(81166006)(8676002)(97736004)(6116002)(6306002)(54896002)(6346003)(82746002)(76176011)(6246003)(106356001)(86362001)(53546011)(6506007)(105586002)(83716004)(102836004)(71190400001)(7736002)(186003)(71200400001)(256004)(25786009)(53936002)(486006)(2501003)(6486002)(8936002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3401; H:DM6PR11MB3692.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)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sajassi@cisco.com;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: lRYJwlM/ImAxpv1UmEoxO5/RUHjT13/q8+h7i6mjRMHifyqB3npt+zVRqQ5y1jzk1jid3vxju6v0tbizWOH/qP3+rQ0+wk6QREWzp86oGFjSf1uW5MxvP7FpT8z5zbSuCKz7MpMb9vgNSeJSYEt7YKPo2nghV2D8imASJV3xYhlOzDeFElTXuzes3P3VJXSO3r9TX9nwFs3PeznELFiiZYI1RO5MJ8Aq59cOYV0pa+j3wY6FEo4v8cyvSt8AOPs6hOMTPb3D505nvAjDrZQvRAqY63ohhfXLCeYhJ4qc9dBK7bgM9cthENvSjjd2QkgqDEGorNbli7BvItTwMC9/mYNTpGVVvKt31eiOursWBoJlSCSOCaPzEpyNNGArP55kdB667AClMy/JwDVeJ7u9R34BMyPL4q8ai4dUfJguDZk=
Content-Type: multipart/alternative; boundary="_000_B50862594B1F4A9B9AD0AD240FC0F647ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d42f37c4-d029-4160-79b2-08d690968091
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Feb 2019 03:02:19.4944 (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-Transport-CrossTenantHeadersStamped: DM6PR11MB3401
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.17, xch-aln-007.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1y_7AVwL2-Wg7AYbmfQ9i2IyXdY>
Subject: Re: [bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding
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: Tue, 12 Feb 2019 03:02:48 -0000

Mobility procedures for asymmetric IRB is very similar to symmetric IRB except for ARP response handling by the source NVE. So, I added the following sentence to the sections 4.1, 4.2, and 4.3 in rev07.

“In case of the asymmetric IRB, the source NVE also updates its ARP table with the received adjacency information and in case of the symmetric IRB, the source NVE removes the entry associated with the received <MAC, IP> from its local ARP table.”

Cheers,
Ali

From: BESS <bess-bounces@ietf.org> on behalf of Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Tuesday, February 5, 2019 at 8:22 PM
To: "bess@ietf.org" <bess@ietf.org>
Subject: [bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding

Section 4 (Mobility Procedure) of the draft says the following:

   This section describes mobility procedures for both
   symmetric and asymmetric IRB.

However, it describes the mobility procedure only for symmetric IRB (section 4.1). Mobility procedure for asymmetric IRB is not described in the draft.

Is the mobility procedure for asymmetric IRB expected to be described in an upcoming version of the draft?

Regards,
Muthu

v2.23.0 | Report a Bug | By Email