[bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08

Anoop Ghanwani <anoop@alumni.duke.edu> Wed, 19 July 2017 05:39 UTC

Return-Path: <ghanwani@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 3722D1274D0 for <bess@ietfa.amsl.com>; Tue, 18 Jul 2017 22:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 DbJ3uj3lA7NZ for <bess@ietfa.amsl.com>; Tue, 18 Jul 2017 22:39:08 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 AEE5E126CC4 for <bess@ietf.org>; Tue, 18 Jul 2017 22:39:08 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id b40so32800234qtb.2 for <bess@ietf.org>; Tue, 18 Jul 2017 22:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=bK5y4dGyFsc+gR81TzdZWSUvSDHyPbcmy+SLgzU5eoc=; b=of6d+ikDT8xxslKijq4KaOo1IfYyK4s5qQLkx9zsSxQ3UMYcyM+f/MFLft+i7HucyZ SdVkLbLF55PvGEcoQXpYNmLktJDO8gyylUy6shbqb8iOdaSV2jdDCJZyTeqIvNInl2TW mujpmbLpzcW47Vn4FnlP8QFxoJMGoWTGlLwEoFEekb9aTmXem3pVO82ydz0jsr8bbQt/ LeKScWzJdwvV+wDMW3ABXGdBEbYVUdmTQd37fUtjNkIdZgQeYVOmacwqV7q43hOx5Mt6 Ljq4LT2ybLYmu5LzWs9FDIHivRwNkILXPAklomXDhLyM17YEifryEOc0LQtwNFcnA0Pm xlEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=bK5y4dGyFsc+gR81TzdZWSUvSDHyPbcmy+SLgzU5eoc=; b=lHabtnIw0eg+9r9aAqZKg7OzIAoQ5/3dE8mPgH8GBYoNjKq6/ZQv8c6ZNvzrd6hAOv W4qMTS8IthMMMstoI2+KSbXk2fmw0bUc2XE8F/aCPLQT7HJAIE8UNud/lFLaB06zuUVc fk8hwq/uukrk+SktmQ17nWjeeTRrFRDHITdPXlnfoxCYYAZQM7ZRfeUpExbqMlt6Kbpg sJsDRr2fLevGdGQT+W32TA7LZz5pcxC1NWTS+oEvAeIYGNzv7DDXmcal/cmKj9vaZOO+ Ltu4XUJNbNz/YTy1yUAHnAwSBC0VetAurNFj562BYBgy12QJrqs1a61Ln014ozW8nVrl XHHw==
X-Gm-Message-State: AIVw112zer1yGKiSG7cJdaJ0N0iuFAalfR2//ffuAs1ucArO5X+fowTw QJCosRrkG9mRPjSbrS+t1lBXnn6aRsx+
X-Received: by 10.237.35.131 with SMTP id j3mr1311540qtc.215.1500442747664; Tue, 18 Jul 2017 22:39:07 -0700 (PDT)
MIME-Version: 1.0
Sender: ghanwani@gmail.com
Received: by 10.200.57.225 with HTTP; Tue, 18 Jul 2017 22:39:07 -0700 (PDT)
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Tue, 18 Jul 2017 22:39:07 -0700
X-Google-Sender-Auth: MK7zjuXRaVg2b7G0p5Rf2i4voio
Message-ID: <CA+-tSzwAfZZ8EyvVbXxxZgWesS_P0jSwjvcSKjT7N76iBnzhUQ@mail.gmail.com>
To: bess@ietf.org
Content-Type: multipart/alternative; boundary="001a113703fcfb33530554a50c64"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/WD89eS1OOvgt0v-A4lg2guTN1i8>
Subject: [bess] a question about bundled service in draft-ietf-bess-evpn-overlay-08
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
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, 19 Jul 2017 05:39:10 -0000

This is what the draft says about bundled service:
https://tools.ietf.org/html/draft-ietf-bess-evpn-overlay-08#section-4
>>>

8) When a 802.1Q interface is used between a CE and a PE, each of the
   VLAN ID (VID) on that interface can be mapped onto a bridge table
   (for upto 4094 such bridge tables). All these bridge tables may be
   mapped onto a single MAC-VRF (in case of VLAN-aware bundle service).

>>>

So it sounds like 1:1 is supported (that's the straightforward case where
the inner VLAD ID is stripped from the encap'ed packet) and All:1 is
supported (i.e. the service is blind to the incoming tag and just preserves
it as is, potentially with normalization if translation is required).

What about the case for n:1 where I want some subset of VLAN IDs coming in
on a port to map to VNID1, and another subset map to VNID2?  Is that
explicitly disallowed?  If so, why?

Thanks,
Anoop