[bess] Signaling Control Word in EVPN

Muthu Arul Mozhi Perumal <muthu.arul@gmail.com> Fri, 05 October 2018 04:14 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 C7666130DC5 for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 21:14:48 -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 XXSrXjCXI2Qv for <bess@ietfa.amsl.com>; Thu, 4 Oct 2018 21:14:47 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 B8E6B1292F1 for <bess@ietf.org>; Thu, 4 Oct 2018 21:14:46 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id m18-v6so8363683lfl.11 for <bess@ietf.org>; Thu, 04 Oct 2018 21:14:46 -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=YUN61Pn7GO5Vd3NkedCEoWjhyGotOrlaLbtsimalloc=; b=OJTVBppU2ZY71ERbKIRpaUlXPJH8oC/VxAVPwMb8JrxE2GfvhUc4bR/RmiKgIuVJvs nw/eSUonbleXJfWs/9+XzWjxWI83xVDTls1q3e+cYnjvHuwTvj+/bbakYKKEbdueCPNO AemPkw4AgkJUmng89OuvGsQUKR5PDST39JudzFFxza8gjNYRRDqCgsupaFM91TjaVT2F UgvUG74JZelsPUwOTJfyyCszwn0g11Ajar0t/jf+Rxj2HYh0hgrSzxINqN06qZn12juC jGZM6EE111ZgdczumM7v0slqGbMXKy+z7GWgp6hQp8jm3B4/96dNoiklrKAUJ3wMKKfp MQ2A==
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=YUN61Pn7GO5Vd3NkedCEoWjhyGotOrlaLbtsimalloc=; b=ONyI3vzGgxyeOab8LZmdM+aw0s+3lZHTBs5/c/NiBJPBzx9KqTjx4oU0Q8yNGXA703 ckoVg5ZPaVgbzwlSXAUrKsPGKgESg8qlGRdtDyyKOkoFnCnoDE6zMYA+WLTHOo3ZuwwC ucdha8UejtVcYvCYgg+E/KL3sre0lhXmm1lVnkPC2awmYP0I2IiMvxVIv1acm2cTdd1v IUxiMvd8IkRwbOKZR/9snL0yIqEn5RYAVwpmof9VZhBFMUF3VPTcJmGRxohAzXwbbyI5 I3240724n5C1nUnDbI4mwb+YM59lk6XSJ3/Obn5zv/1ObxeDgV3DpdM8N4Kk8yfIUKjc KqOQ==
X-Gm-Message-State: ABuFfohMLRVTaqFKn1whw5EvqjIJwWUzSNHdK/PI7kwFXn4pqL0FucFD GZY8BCjbHLhCoCLRQua5qoxu4ifi6/BcvZdXDC813A==
X-Google-Smtp-Source: ACcGV60e+dMDOQKswzywTg+yLjQ2txJ6GW3oCa70f2kStBpOpvH5lY6W6X8+cXNJbl89QHBUyXWhbsnsgzFVykZEEEs=
X-Received: by 2002:a19:ea57:: with SMTP id i84-v6mr5284182lfh.91.1538712884863; Thu, 04 Oct 2018 21:14:44 -0700 (PDT)
MIME-Version: 1.0
From: Muthu Arul Mozhi Perumal <muthu.arul@gmail.com>
Date: Fri, 05 Oct 2018 09:44:32 +0530
Message-ID: <CAKz0y8yFQdX5w_38rpyvd_sTJsTLxNEXYxxD=ttBzJi=VKxhjg@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e9e77d0577738279"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/sg8GNOV9qG23zJl9KdtauNjNV78>
Subject: [bess] Signaling Control Word in EVPN
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: Fri, 05 Oct 2018 04:14:49 -0000

RFC 8214 (EVPN VPWS) introduces a new EVPN Layer 2 Attributes extended
community for signaling the L2 MTU and other control flags, including the
one to signal that the control word needs to be included when sending
packets to this PE. It further describes how MTU checking is to be
performed when signaled using this extended community.

RFC 7432 however is completely silent about it. Is the extended community
described in RFC 8214 expected to used in EVPN (VPLS) as well to signal
things like the usage of control word?

Regards,
Muthu