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

Anoop Ghanwani <anoop@alumni.duke.edu> Wed, 19 July 2017 16:11 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 135C712F3CB; Wed, 19 Jul 2017 09:11:26 -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 SACD79omiYfp; Wed, 19 Jul 2017 09:11:24 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 91226127B60; Wed, 19 Jul 2017 09:11:24 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id n42so6277835qtn.0; Wed, 19 Jul 2017 09:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NmQPNDFkUl6v5L6R+aEc9mj7BbW7Cg66rbQmW5eSGb4=; b=b672E8znzWGFp407jc3LP6Z8YHFt0AfL4bNoC60QDsPMOCQFPCoj2/zi9d1enBcIhl 36zg234ylLHxvyOer41fjKAW+FN86s2vkKrL5/qdHEc7QNgm6aw/X/uTZmZEeZ/x2kRO HLnzLgyMuKWAYf2mm6hV4ix+7t9Eg17uJizlRdReBOx4qQzZI3Y8CRetaDh4WnqGBCL5 1Dqm2lkeRRYOg8u91PWyqGRXp3jfpQbJYLkdhwGWFVxumZ3xKgLlJ/Ry4C0BE+PmkZpS v7UeFoKElQi9fUPjYHnFs1iA4mg7abyb9xQ8E6V3SeGtyJdsBhoRGdAgDZ3l55wG/3pE Q9FA==
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:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NmQPNDFkUl6v5L6R+aEc9mj7BbW7Cg66rbQmW5eSGb4=; b=AEx6cvjuQqI1ivQhUOPb2yfpt3PMDKm5vf0zGzveewfm9p1uOJLxNehUok0Yt7GUjF HRmPXirKDt8GnF4sgfBKiM6yp0AcizEoU1c9AgdlfV1EQOa3/tTWBFr000v+TFGMr4Ld XWsm27vl2pf3uR/3refelez8kbNj9qMTLqGrrw+kogsY8MezwHN1Di06vpZKH77qp6fe deERWDdb5be8tzCigH6Brz8My1KZelZ/541f+YxkRKnRaacMAVvEltXAbLBjBL0KJy7s RfEULDg5KW6Wq3yZYZmoeewa8/WQSspctVvAqS5exzZCf8nezp+6t1FSuPDdLVgKk84+ ILCA==
X-Gm-Message-State: AIVw11287K5YLFvMZAdzCInMhmeC9lHfJV4rDmjVWxcj5TaskUXUDu2z GASDhK1sBof56dqOshg8NJImqJwc/Q==
X-Received: by 10.237.62.60 with SMTP id l57mr903413qtf.20.1500480683716; Wed, 19 Jul 2017 09:11:23 -0700 (PDT)
MIME-Version: 1.0
Sender: ghanwani@gmail.com
Received: by 10.200.62.25 with HTTP; Wed, 19 Jul 2017 09:11:23 -0700 (PDT)
In-Reply-To: <D594D20D.2138C0%sajassi@cisco.com>
References: <CA+-tSzwAfZZ8EyvVbXxxZgWesS_P0jSwjvcSKjT7N76iBnzhUQ@mail.gmail.com> <D594D20D.2138C0%sajassi@cisco.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Wed, 19 Jul 2017 09:11:23 -0700
X-Google-Sender-Auth: xdr1YYfYZ_hVBLkSPqfXvaM-1G4
Message-ID: <CA+-tSzywX3t_pMj7b4k2xq=iYbAtMxYCoR4Spj63O=_perZivw@mail.gmail.com>
To: "Ali Sajassi (sajassi)" <sajassi@cisco.com>
Cc: "bess@ietf.org" <bess@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140860225345a0554ade2d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/_Z9NagDaBmJ7YQZNd_67-4BdDDA>
Subject: Re: [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 16:11:26 -0000

Thanks Ali.

May be worth modifying the sentence below to say:
>>>

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). More than one bridge table may be
   mapped onto a single MAC-VRF (in case of VLAN-aware bundle service).

>>>

Anoop

On Wed, Jul 19, 2017 at 12:14 AM, Ali Sajassi (sajassi) <sajassi@cisco.com>
wrote:

>
> From: BESS <bess-bounces@ietf.org> on behalf of Anoop Ghanwani <
> anoop@alumni.duke.edu>
> Date: Tuesday, July 18, 2017 at 10:39 PM
> To: "bess@ietf.org" <bess@ietf.org>
> Subject: [bess] a question about bundled service in
> draft-ietf-bess-evpn-overlay-08
>
>
> 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?
>
> That’s is also supported. Refer to section 6 of RFC 7432 for different
> service interfaces that are supported.
>
> Cheers,
> Ali
>
> Thanks,
> Anoop
>
>
>
>