Return-Path: 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 133BF1200B8 for ; Fri, 3 May 2019 02:47:02 -0700 (PDT) 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 cYIQ20WprgDf for ; Fri, 3 May 2019 02:46:59 -0700 (PDT) Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 7279E12006D for ; Fri, 3 May 2019 02:46:58 -0700 (PDT) Received: by mail-lj1-x229.google.com with SMTP id w12so4655432ljh.12 for ; Fri, 03 May 2019 02:46:58 -0700 (PDT) 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=0MA/ROwK6kozasZqDMsvtYBlFZYkMUEErqvdQUq+Ia4=; b=L8aWfPt/ddp+iuZR0mAct2fhb+DJ/ZEqQF6+ssnPA1sX1VYS4poGpUjjqtW6rlMYef gU++EfDiW34+/GpI4gd0g2qSJve/yx4MWIHGrfLwL6X9BrZHU9y8cOkwyS8xe2AR9ct5 tswwYfJ80/4i2NIsd/zaIAM/uw9pVjq1lJ4trDYImT6uQNga8sQlmzjN4TPyhDOfnswH 9pyDvkrG2Gr+cF3BXCcGH3dN6flE37b6IqubUMXmcBNDK5j4Z4f3WveGENH1beMbiVwT NcHc24V/d+u5XS1AeeWVBTK2M3UqpZf5qHiaPyk9TcJ6sGbhtMnY9508kQzq7QI9O+OZ okvg== 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=0MA/ROwK6kozasZqDMsvtYBlFZYkMUEErqvdQUq+Ia4=; b=WCVW+x58t5BeqalbDikfcniJuP/ycP04Tdrt/A1toPUf6cPj/Ppw0CiiSE1YXSb4Ek 9r1wmTbHbiuXpqO/oTpcBCylvV0m3Yc97acBcCIpjvbMep0SyIQHcIq/UcES4y6QZq8x vB9dUnaZIZbYWTfAaDHS6oRLNwTEt/O7NCEDK79sGdctUANVpl9fgCYfI2IALdCNfm5s 4XebTMQcRi1qH3NXRRLh2zy1NN5aTeAYfuGOnJDQJfY9o7wl8FePQUku4o3VEJUcrQbg do/aCFfrfgEKk6EjH6vjgFFy2JeDt2SPQWjfHvfcYb9Y3TdlKEztzIgCGpEZMxaifvyY wrqw== X-Gm-Message-State: APjAAAUirRoiyTK3gPclCYndAJI5/Vayj7eDax8XgPTsEb4hHBr6mrVR zbx3sypIVvMYLFvj+DHNfz7p1s2ALb46B8cvSP4= X-Google-Smtp-Source: APXvYqxAj/4toehNFQx6x220ZNs+qVkSfs8N1c5lvWE/MdFmMcIWA+axV3ev/2i62apUI72XiQYPCYrA3lQljeTbqGk= X-Received: by 2002:a2e:2b16:: with SMTP id q22mr4654213lje.20.1556876816666; Fri, 03 May 2019 02:46:56 -0700 (PDT) MIME-Version: 1.0 References: <67ADA5CE-E49B-4FD9-9DD2-C363F3DD3284@nokia.com> In-Reply-To: <67ADA5CE-E49B-4FD9-9DD2-C363F3DD3284@nokia.com> From: Muthu Arul Mozhi Perumal Date: Fri, 3 May 2019 15:16:45 +0530 Message-ID: To: "Rabadan, Jorge (Nokia - US/Mountain View)" Cc: "bess@ietf.org" Content-Type: multipart/alternative; boundary="0000000000009dd70b0587f8a153" Archived-At: Subject: Re: [bess] Question on ARP probe 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2019 09:47:02 -0000 --0000000000009dd70b0587f8a153 Content-Type: text/plain; charset="UTF-8" Please see inline.. On Fri, May 3, 2019 at 12:02 PM Rabadan, Jorge (Nokia - US/Mountain View) < jorge.rabadan@nokia.com> wrote: > You only need the IP-VRF RT in case of the IP is included in the MAC/IP > route _*and*_ you are in symmetric mode, since you need to install the IP > in the route-table. > If we follow the argument that there is only one IP-VRF per BD which you can identify based on the RT for the MAC-VRF and Ethernet tag, you don't need the RT for the IP-VRF even if the MAC/IP route includes the IP and you are in symmetric mode, right? > The mobility section is done for both symmetric and asymmetric modes, and > also, in particular, that case you allude to, there is only a MAC in the > route that the source NVE receives. So you cannot guarantee the source NVE > will receive an RT for the IP-VRF. > Agree. But, neither section 4.2 nor anywhere else in draft-ietf-bess-evpn-inter-subnet-forwarding we describe how the source NVE deduces the IP-VRF when the MAC/IP route has only the MAC address and MAC-VRF RT. Regards, Muthu > > > Thx > > Jorge > > > > *From: *Muthu Arul Mozhi Perumal > *Date: *Friday, May 3, 2019 at 7:39 AM > *To: *"Rabadan, Jorge (Nokia - US/Mountain View)" > > *Cc: *"bess@ietf.org" > *Subject: *Re: [bess] Question on ARP probe in > draft-ietf-bess-evpn-inter-subnet-forwarding > > > > Hi Jorge, > > > > Thanks for your response. Please see inline.. > > > > On Tue, Apr 30, 2019 at 8:43 PM Rabadan, Jorge (Nokia - US/Mountain View) < > jorge.rabadan@nokia.com> wrote: > > Muthu, > > > > The source NVE identifies the MAC-VRF/BD out of the RT/eth-tag. The > assumption is that the BD is only attached to one IP-VRF, hence you know > what ARP table to look up. > > > > If this is the case, why include the RT for the IP-VRF at all in route > type-2 advertisements? > > > > Regards, > > Muthu > > > > My two cents. > > > > Jorge > > > > *From: *BESS on behalf of Muthu Arul Mozhi > Perumal > *Date: *Tuesday, April 30, 2019 at 4:39 AM > *To: *"bess@ietf.org" > *Subject: *[bess] Question on ARP probe in > draft-ietf-bess-evpn-inter-subnet-forwarding > > > > Hi Everyone, > > > > draft-ietf-bess-evpn-inter-subnet-forwarding describes the mobility > procedure to be followed when a TS moves from a source NVE to a target NVE > and starts sending data traffic without first initiating an ARP request. It > says the following in section 4.2: > > > > > > - The source NVE upon receiving this MAC/IP advertisement, realizes > > that the MAC has moved to the new NVE. It updates its MAC-VRF table > > accordingly by updating the adjacency information for that MAC > > address to point to the target NVE and withdraws its EVPN MAC/IP > > route that has only the MAC address (if it has advertised such route > > previously). Furthermore, *it searches its ARP table for this MAC and* > > *sends an ARP probe for this pair*. The ARP request message is > > sent both locally to all attached TSes in that subnet as well as it > > is sent to other NVEs participating in that subnet including the > > target NVE. > > > > > > The question I have is, the MAC/IP Advertisement route the source NVE > receives from the target NVE in the above case has only the MAC address of > the TS and the RT corresponding to the MAC-VRF. How can the source NVE > deduce the IP-VRF to search the corresponding ARP table and send an ARP > probe? > > > > Regards, > > Muthu > > --0000000000009dd70b0587f8a153 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Please see inline..

<= div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 3, 2019 at 12:02 PM Rabada= n, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com> wrote:

You only need the IP-VRF RT in case of the IP is included in the MAC/IP r= oute _and_ you are in symmetric mode, since you need to install the = IP in the route-table.


If we follow the argument that there is only one IP-V= RF per BD which you can identify based on the RT for the MAC-VRF and Ethern= et=C2=A0 tag, you don't need the RT for the IP-VRF even if the MAC/IP r= oute includes the IP and you are in symmetric mode, right?
= =C2=A0

=

The mobility section is done for both symmetric and asymmetric modes, and= also, in particular, that case you allude to, there is only a MAC in the r= oute that the source NVE receives. So you cannot guarantee the source NVE will receive an RT for the IP-VRF.


Agre= e. But, neither section 4.2 nor anywhere else in=C2=A0draft-ietf-bess-evpn-= inter-subnet-forwarding we describe how the source NVE deduces the IP-VRF w= hen the MAC/IP route has only the MAC address and MAC-VRF RT.

Regards,
Mu= thu
=C2=A0

=C2=A0

Thx

Jorge

=C2=A0

From: Muthu Arul Mozhi Peru= mal <muthu.aru= l@gmail.com>
Date: Friday, May 3, 2019 at 7:39 AM
To: "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.= com>
Cc: "bess@ie= tf.org" <bes= s@ietf.org>
Subject: Re: [bess] Question on ARP probe in draft-ietf-bess-evpn-in= ter-subnet-forwarding

=C2=A0

Hi Jorge,

=C2=A0

Thanks for your response. Please see inl= ine..

=C2=A0

On Tue, Apr 30, 2019 at 8= :43 PM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com> wrot= e:

Muthu,<= u>

=C2=A0<= u>

The source NVE identi= fies the MAC-VRF/BD out of the RT/eth-tag. The assumption is that the BD is= only attached to one IP-VRF, hence you know what ARP table to look up.

=C2=A0

If this is the case, why include the RT = for the IP-VRF at all in route type-2 advertisements?=C2=A0

=C2=A0

Regards,

Muthu

=C2=A0<= u>

My two cents.<= u>

=C2=A0<= u>

Jorge

=C2=A0<= u>

From: BESS <bess-bounces@ietf.org> on behalf of Muthu A= rul Mozhi Perumal <muthu.arul@gmail.com>
Date: Tuesday, April 30, 2019 at 4:39 AM
To: "bess@ie= tf.org" <bes= s@ietf.org>
Subject: [bess] Question on ARP probe in draft-ietf-bess-evpn-inter-= subnet-forwarding

=C2=A0

Hi Everyone,

=C2=A0

draft-ietf-bess-evpn-inter-sub= net-forwarding describes the mobility procedure to be followed when a TS mo= ves from a source NVE to a target NVE and starts sending data traffic witho= ut first initiating an ARP request. It says the following in section 4.2:

=C2=A0

<snip><= /u>

=C2=A0 =C2=A0- The source NVE = upon receiving this MAC/IP advertisement, realizes

=C2=A0 =C2=A0that the MAC has = moved to the new NVE. It updates its MAC-VRF table

=C2=A0 =C2=A0accordingly by up= dating the adjacency information for that MAC

=C2=A0 =C2=A0address to point = to the target NVE and withdraws its EVPN MAC/IP

=C2=A0 =C2=A0route that has on= ly the MAC address (if it has advertised such route

=C2=A0 =C2=A0previously). Furt= hermore, it searches its ARP table for this MAC and=

=C2=A0 =C2=A0sends an ARP p= robe for this <MAC,IP> pair. The ARP request message is=

=C2=A0 =C2=A0sent both locally= to all attached TSes in that subnet as well as it

=C2=A0 =C2=A0is sent to other = NVEs participating in that subnet including the

=C2=A0 =C2=A0target NVE.

</snip>=

=C2=A0

The question I have is, the MA= C/IP Advertisement route the source NVE receives from the target NVE in the= above case has only the MAC address of the TS and the RT corresponding to = the MAC-VRF. How can the source NVE deduce the IP-VRF to search the corresponding ARP table and send an AR= P probe?

=C2=A0

Regards,<= /p>

Muthu

--0000000000009dd70b0587f8a153--