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

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Tue, 12 February 2019 08:59 UTC

Return-Path: <muthu.arul@gmail.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 E49FD124BAA for <bess@ietfa.amsl.com>; Tue, 12 Feb 2019 00:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 c3uMAEVD8CRN for <bess@ietfa.amsl.com>; Tue, 12 Feb 2019 00:59:04 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB3CB124408 for <bess@ietf.org>; Tue, 12 Feb 2019 00:59:03 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id s5-v6so1486866ljd.12 for <bess@ietf.org>; Tue, 12 Feb 2019 00:59:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YsPCpazY8MXtX/qJdUJ1cQmLx4oXU+Qv9MCluo6qTTI=; b=fADW/6upbWihbawHWtwTT9Oe5BkAo+Kvi4I1+F0Y78Gl4+DvS1OeLwKI9Q+bXk7Ahy JLjsElhNbr+ETTGh84R+x5SYdPmxORnfoIaT0mNF+OrxhgMz3LNue9GWiHleI7UG3ifh DdcourpWpZGlt9TbpCrSygc68orYe1DV+IMUgfzn058mLH7ahB2cLUVUzK8VMXvtyHDn v8k95pmGmmFY01ECPzjWRCdvhA99cLtQGB7YHWW+tyCnNV3JYXs2TLbM0oRS6YRxiDIp eQ6TfAo/VCFlLPc92kvv80dIL1McNk30NQgsa66Al24SEgIJC7uzR+wFTLoMBgVkRJqp vt+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YsPCpazY8MXtX/qJdUJ1cQmLx4oXU+Qv9MCluo6qTTI=; b=Fa4mMhR7u+OoBbHWznop9q2FwbxFjBrVYkmlnP0VeZYwWJehSqY9+6SiuYoYh80YwQ JUJuqmlqOfoearUVX4itV1VkMtEM1eDvS1K+XmAhkr4qgcnNY8yWWO+CTWzX6ZLY45g/ eXZxy2/aJ15GDXo5GnWpqVj0oDiHMMw1OZ6Tp1OYr/Pd6vpekeBB7LGjuVx0VpGr76gs 4F93mO+i5lt69ERTKhF7UUTKp3j42fT6+sMAiE/jhL27ZZaIfnrv9OTf5aNEzRXSosUh 9RDPuYTDy/bvzmjvkbpy7RhXXWsXTsY9HLjKftkQaff6+L1HeiHcZDAMmvXl7BcmGA5n vmxg==
X-Gm-Message-State: AHQUAuaJgDdTQyVo8/d/QgEOj8Lugx0UZeni7ekeOiVFhKCada0JHcXw ODWz8UgAONqd4k7CCyZyMfwE2V0K5FYGOfkv8Js=
X-Google-Smtp-Source: AHgI3IbdgwjDbqZLtWSV62lejb+zNqmrFY9gNheiyFa+ZKVKuEiugyUUxglKe0SLi6LYZhVSxNqcNUQ9YkHGW0+BrEw=
X-Received: by 2002:a2e:870c:: with SMTP id m12-v6mr1669815lji.180.1549961941834; Tue, 12 Feb 2019 00:59:01 -0800 (PST)
MIME-Version: 1.0
References: <CAKz0y8xjC10J-g0t05CW_-RGAf-7T+R=Hx_dQvxfhAKbD3f9tA@mail.gmail.com> <B5086259-4B1F-4A9B-9AD0-AD240FC0F647@cisco.com>
In-Reply-To: <B5086259-4B1F-4A9B-9AD0-AD240FC0F647@cisco.com>
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Tue, 12 Feb 2019 14:28:50 +0530
Message-ID: <CAKz0y8zJCKO7X18d5-KfmsVND7UueFF3keR2Ejf0m+H+nXF=Lw@mail.gmail.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Cc: "bess@ietf.org" <bess@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f55f9c0581aea25f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/oJesPuOk4ERToTZu1u9JSat3rcQ>
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 08:59:06 -0000

Sounds good and both of my earlier comments are addressed in -07.

thanks,
Muthu

On Tue, Feb 12, 2019 at 8:32 AM Ali Sajassi (sajassi) <sajassi@cisco.com>
wrote:

>
>
> 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
>