[bess] Mobility procedure in draft-ietf-bess-evpn-inter-subnet-forwarding
Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Wed, 06 February 2019 04:22 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 8B5C2126C7E for <bess@ietfa.amsl.com>; Tue, 5 Feb 2019 20:22:27 -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 MoaeBQYAUvfr for <bess@ietfa.amsl.com>; Tue, 5 Feb 2019 20:22:26 -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 F3BB4123FFD for <bess@ietf.org>; Tue, 5 Feb 2019 20:22:25 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id v14-v6so2057085ljv.1 for <bess@ietf.org>; Tue, 05 Feb 2019 20:22:25 -0800 (PST)
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=3Re3dTXIbWuXghd9vnfE5BQsWdpTQqLemB7TeOJOsc8=; b=UxdVsBqc0f8U0XazRWFKeWrtfDdsfq5ZRU6IhPZ3pJF8W/UTGtsgwMmulhLoKfCYSq uNjU5fAVbyMoFVOvvgzPIXCzcUMnd4sj3D0cfancqE7g5H8WlvihuC6ju7FvGdfgtxus DtsvhwuEBfa7uDlAKC1yCvhDFxUmHPLcp24OZ6pDF+6pU30Fg75QguG9cAgMhtjQMGN+ XB3z06eYO2cc63y42Yp4fkoh5Q//KFnn+JUR2neaC/4h8YHCCTW0Sdh7mUPaRd8plq7e wdMPI0WHkFsGTQEXPf/44S1CuIi7J0k5vzahkGNIuJCFpQBLg4FxxdMl2V4VXPJlPFMs vZtg==
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=3Re3dTXIbWuXghd9vnfE5BQsWdpTQqLemB7TeOJOsc8=; b=dQtsYT+8+Vl6FNXJJU9KSoCw/HMDOybyfbJxyT/oFciDcA1B48ghwaQOLLwrWwmGE0 yu5Uk441CvApu/GwwW3vlNYNLWGscPaUrsYWYhYUNGYru8t7FzjT5x0IJhC3Kqsc8ARs F2qOlX7BtF6aWg2tOCQbycRz5YO+SiJXLrkxv+7EfR1bM1z+LkrgZr89kLpucj3Fizex EFdf/kzyO9TIpIu3NEYLcTIk6KKxi/NvXVwaGrQ+tR2P+9kvHZh6WiH0ODroIYd6GSum pS2BqlXhCUdf/D1iLvu6vAvfYtBrYOdrrBukTy+PcbNcdz53MaZskBYCrcFt60z7lSH7 v3lg==
X-Gm-Message-State: AHQUAub/9eJR+lVwQWvjdqUqCwby19zGOq9l8ZS69aqoEXec3erAnmii EgcQY6WRpiCSxvpY5ZTl45J1pPR55SQy41AaZ6FUJpJW
X-Google-Smtp-Source: AHgI3IaqdgbCpa9snKprTu566uDyKyZzpIjMnbQY8fpc6Y5L/gkrkq1K5hHKSPcK0JD6e0Fj69mC/o3J7AC3rYBfa8M=
X-Received: by 2002:a2e:5d85:: with SMTP id v5-v6mr2559397lje.180.1549426943937; Tue, 05 Feb 2019 20:22:23 -0800 (PST)
MIME-Version: 1.0
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Wed, 06 Feb 2019 09:52:12 +0530
Message-ID: <CAKz0y8xjC10J-g0t05CW_-RGAf-7T+R=Hx_dQvxfhAKbD3f9tA@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="000000000000995135058132122e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/TZnE7JkGEzW8udp5V3LwHGLFfQg>
Subject: [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: Wed, 06 Feb 2019 04:22:28 -0000
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
- [bess] Mobility procedure in draft-ietf-bess-evpn… Muthu Arul Mozhi Perumal
- Re: [bess] Mobility procedure in draft-ietf-bess-… Ali Sajassi (sajassi)
- Re: [bess] Mobility procedure in draft-ietf-bess-… Muthu Arul Mozhi Perumal