[bess] Comment on MAC Mobility Procedure in draft-ietf-bess-evpn-inter-subnet-forwarding

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Sat, 30 March 2019 15:32 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 DDC31120219 for <bess@ietfa.amsl.com>; Sat, 30 Mar 2019 08:32:29 -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 sPepUYoa9llz for <bess@ietfa.amsl.com>; Sat, 30 Mar 2019 08:32:27 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 8B150120226 for <bess@ietf.org>; Sat, 30 Mar 2019 08:32:27 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id j89so4468325ljb.1 for <bess@ietf.org>; Sat, 30 Mar 2019 08:32:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=77PK8vhYvQxd/y3wT35XS84GeHwjqRpEpRlt8qzaXfw=; b=JU23+kQgiNELwSft+nYTmlZyv698sJJfi8eX1xDrvsMKRmf/jY3d799Ju8cPipwOYT mV0OjNzCmcWv9S/jrEO8nAfIXk9hwS7BaMMcHVSruT4X+BG/XKi1oNv4rRMqzLpDBRxd fh3u2uC+9PbxwKJAXV42WOWM/7cA/Q3OFyak+PxIPwU0Fw1mOEm0wXckevqMtvtO4XRa TqlbyW9q5n6cb8YYX9GBgucO22RUttUY80IBPe2ZQ3MYotJKXSZHAqpW3wQ7RGBKAkpY wGGj4JGbMtbxejALaE4yDJFYI9EMZpzqdVLqj/kFUTvCH+34g37ODpqHIkc5vO6ldj9e ELug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=77PK8vhYvQxd/y3wT35XS84GeHwjqRpEpRlt8qzaXfw=; b=dzkA3b6g8XKeLHTRohA9y56vMseTk2jP9n6ZAbcUNjnUwdl/Ah8GHX8AOewbUUHrww wBDJ5IrTFt6caFj6crczBYtbz+MMxeNQzfkDQvxO433TQDSm9KojTm1Fvh5H+ld7v10s 2Z3ZByYrdAub8zL+p37wb40R58R6iRRgh80xMKJn2ZUSce42WZnRaxJCZ95eOLVvnAnE FZHu2ebUAylQ7ZQpNSaQaDI4R1XMFCZ9XQJWDdyvNSCIleltqLmUd//8rJVNr9eoUHFB 6ZSkX/sBBrPCbsjOrPXIdHdngHcYqAnrJDR4533onmDDV4/FQpIlPeEWKAIoQNPBrIk9 fbzw==
X-Gm-Message-State: APjAAAWBOZMljg461kUb/6Kp8gs999TIw/Kmaz+UktHqh1UlSv0KcY4f G/SIry23fS1EbhtEBjPxlf0EIMmTWNUmxr1mvlxJ1/4fCzk=
X-Google-Smtp-Source: APXvYqzM4CR9PSJ/ZwlZljAOSv4cenV7P74mPG2ku18MoZxIzN/sAcsDY3/fGiR7HW13SjL+ocFmE1JeoVAUag/7CJs=
X-Received: by 2002:a2e:8016:: with SMTP id j22mr9064003ljg.189.1553959945685; Sat, 30 Mar 2019 08:32:25 -0700 (PDT)
MIME-Version: 1.0
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Sat, 30 Mar 2019 21:02:14 +0530
Message-ID: <CAKz0y8ztCZJuv=kAgwDbs+srTHLn+1V_JwYGF_A166KhPaaaVg@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="0000000000008ed03d0585517ec0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/nMaOaZ8FeEfUlysoJVayoGpFrlQ>
Subject: [bess] Comment on MAC 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: Sat, 30 Mar 2019 15:32:40 -0000

Section 4.1 of draft-ietf-bess-evpn-inter-subnet-forwarding describes the
mobility procedure when a host initiates an ARP request upon a move.

It says the following regarding the source NVE:

<snip>
   Furthermore, it sends an ARP probe locally to
   ensure that the MAC is gone.  If an ARP response is received, the
   source NVE updates its ARP entry for that <IP, MAC> and re-advertises
   an EVPN MAC/IP route for that <IP, MAC> along with MAC Mobility
   Extended Community with the sequence number incremented by one. The
   source NVE also exercises the MAC duplication detection procedure in
   section 15.1 of [RFC7432].
</snip>

Here, the source NVE is trying to verify if the TS has actually moved back.
However, initiating an ARP probe looks redundant here since the host would
anyway initiate an ARP request upon a move (which is the assumption in that
section). So, the source NVE will anyway detect that the host has moved
back if it re-learns the MAC/IP locally through the ARP request, right?

Regards,
Muthu