Return-Path: 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 DB529120464 for ; Fri, 5 Apr 2019 08:10:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 tDOagngLFSOC for ; Fri, 5 Apr 2019 08:10:53 -0700 (PDT) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 161B6120460 for ; Fri, 5 Apr 2019 08:10:53 -0700 (PDT) Received: by mail-lj1-x22e.google.com with SMTP id r24so5588505ljg.3 for ; Fri, 05 Apr 2019 08:10:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XvtZ1R99pqFh/i3Nr7g3YHaykuNdHx3TonWC3oG6qVo=; b=mqgC4sspTkVBltHmmaQ4iHso3Wv3OoHI2zUDvU9pgTksck+1o7BA8uotsXeXsxJhE+ V7CRcLUDV9w135U9VWUTNKv4kyHxuQa/1HU3W4fHq/22ZhUQi61kqBonUcj9WHOrQ1nv T4PrwrePRfclIwJajm5MlQRxEvi9vtL1FayZczfj3FWkYsQqKEf0cGMKQuEbg+uSUgZV U7Z7I0m2e442beNNyggcDvJBU+KnUobKEQITJs7yn/wbaptpU9lxJDD/OxvYb4b3IM5y X/0xcL5xAWWHlrtqK3SZUXWlzsS71mWuqPl++8dgwzQgUO9OSbBtBGu8h01HrvLxCwxE pTMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XvtZ1R99pqFh/i3Nr7g3YHaykuNdHx3TonWC3oG6qVo=; b=CgJ1esUmO8GFCKy9SyJUmI1/vmB3vjpHp/BN9s1HOs4H5MAppX1o8os2rC2QQcVW9Q l98tPI2/lTYldxY7r1lLBYoDQsQNVMUnKg/0zlLeb234dCMsXCZjt8JDqomdWfiiqbXj OHmnnvktqlskXEfYihb4gDc0fBQd3ynAI9UNKJXX0PK5JzJHDeMA3iKnz4LOyYKQP5LR hAPEqmaPv30xo18e8YEBxl0c1jF2w2GfTYuMkRRotDH4V+IKXKqCkfJVs634urg8YJGr wSijOlo1UY/ormk8kqEUlwwW8idM4VIyflu6SDCJawMBxw+O+DeokP2RLROiam+926z6 iuxA== X-Gm-Message-State: APjAAAVPQQ17m2izVLA23HfGl1+ZQwdoyLKLCv4/SDkZ0OlSS13sYJ3+ Xf1KoNVxM8EcqbN0gVQ/95/DCvB4U4cG9D0OBZM= X-Google-Smtp-Source: APXvYqzUPZ/FoEWgjzK073U1h4w4tgVGv+Q9uoX5fEVSdSeW0J51UVO+qP3u4qIIANvoPbYCy+5vYruqXPVfPGqauRE= X-Received: by 2002:a2e:844a:: with SMTP id u10mr7716974ljh.41.1554477051303; Fri, 05 Apr 2019 08:10:51 -0700 (PDT) MIME-Version: 1.0 References: <09CBA32C-C703-408F-9F73-9F26D8FD1C25@nokia.com> In-Reply-To: <09CBA32C-C703-408F-9F73-9F26D8FD1C25@nokia.com> From: Muthu Arul Mozhi Perumal Date: Fri, 5 Apr 2019 20:40:37 +0530 Message-ID: To: "Rabadan, Jorge (Nokia - US/Mountain View)" Cc: Jaikumar Somasundaram , "bess@ietf.org" , P Muthu Arul Mozhi Content-Type: multipart/alternative; boundary="000000000000745e720585c9e435" Archived-At: Subject: Re: [bess] DF election rule in EVPN MH, for untagged interface - reg X-BeenThere: bess@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: BGP-Enabled ServiceS working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Apr 2019 15:10:56 -0000 --000000000000745e720585c9e435 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, Jorge. It is clear that the Ethernet Tag needs to be different from 0 for the purpose of DF election.. One of the options a provider has for supporting untagged frames in EVPN VPLS multihoming in VID translation...a rule to match untagged frames and impose a VID at the ingress and another rule to match that VID and dispose it at the egress. Are there any other options that can interop well? Regards, Muthu On Fri, Apr 5, 2019 at 11:11 AM Rabadan, Jorge (Nokia - US/Mountain View) < jorge.rabadan@nokia.com> wrote: > Hi, > > > > I think you should check out > https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-framework-09 > > > > This draft updates RFC7432 in certain aspects of the DF Election, and it > is already at the RFC editor. > > > > Check out the use of Ethernet Tag in the document. > > > > o Ethernet Tag - used to represent a Broadcast Domain that is > > configured on a given ES for the purpose of DF election. Note that > > any of the following may be used to represent a Broadcast Domain: > > VIDs (including Q-in-Q tags), configured IDs, VNI (VXLAN Network > > Identifiers), normalized VID, I-SIDs (Service Instance > > Identifiers), etc., as long as the representation of the broadcast > > domains is configured consistently across the multi-homed PEs > > attached to that ES. The Ethernet Tag value MUST be different from > > zero. > > > > Thanks. > > Jorge > > > > *From: *BESS on behalf of Jaikumar Somasundaram < > jaikumar.somasundaram@ericsson.com> > *Date: *Friday, April 5, 2019 at 6:15 AM > *To: *"bess@ietf.org" > *Cc: *P Muthu Arul Mozhi > *Subject: *[bess] DF election rule in EVPN MH, for untagged interface - > reg > > > > Hi All, > > > > RFC7432, section 8.5, talks about DF election algorithm (service carving > algorithm) > > only for for VLAN-based service or for VLAN-= (aware) > > bundle service. > > > > But there wont be any vlan id for untagged interface and so I wonder > > how the service carving algorithm can be applied to elect the DF. > > Also, should I use the lower VLAN ID even in the case of VLAN-bundle > > service, for electing the DF? > > > > Could some one help me to understand this please? > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 8.5 . Designated > Forwarder Election > > =E2=80=A6 > > The default procedure for DF election at the granularity of > VLAN> for VLAN-based service or for VLAN-(aware) > > bundle service is referred to as "service carving". > > =E2=80=A6 > > Assuming a redundancy group of N PE nodes, for VLAN-based service, > > the PE with ordinal i is the DF for an when (V mod N) > > =3D i. In the case of VLAN-(aware) bundle service, then the > > numerically lowest VLAN value in that bundle on that ES MUST be > > used in the modulo function. > > =E2=80=A6 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > > > > Thanks & Regards > > Jaikumar S > > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > --000000000000745e720585c9e435 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, Jorge. It is c= lear that the Ethernet Tag needs to be different from 0 for the purpose of = DF election..=C2=A0

On= e of the options a provider has for supporting untagged frames in EVPN VPLS= multihoming in VID translation...a rule to match untagged frames and impos= e a VID at the ingress and another rule to match that VID and dispose it at= the egress.

Are there= any other options that can interop well?

Regards,
Muthu

<= div class=3D"gmail_quote">
On Fri, Apr= 5, 2019 at 11:11 AM Rabadan, Jorge (Nokia - US/Mountain View) <jorge.rabadan@nokia.com> wrote:<= br>

Hi,

=C2=A0

I think you should check out https://tools.ietf.org/html/draft-ietf-bess-evpn-df-election-framework-09

=C2=A0

This draft updates RFC7432 in certain aspects of the DF Election, and it = is already at the RFC editor.

=C2=A0

Check out the use of Ethernet Tag in the document.

=C2=A0

=C2=A0=C2=A0 o Ethernet Tag - used to represent = a Broadcast Domain that is

=C2=A0=C2=A0=C2=A0=C2=A0 configured on a given E= S for the purpose of DF election. Note that

=C2=A0=C2=A0=C2=A0=C2=A0 any of the following ma= y be used to represent a Broadcast Domain:

=C2=A0=C2=A0=C2=A0=C2=A0 VIDs (including Q-in-Q = tags), configured IDs, VNI (VXLAN Network

=C2=A0=C2=A0=C2=A0=C2=A0 Identifiers), normalize= d VID, I-SIDs (Service Instance

=C2=A0=C2=A0=C2=A0=C2=A0 Identifiers), etc., as = long as the representation of the broadcast

=C2=A0=C2=A0=C2=A0=C2=A0 domains is configured c= onsistently across the multi-homed PEs

=C2=A0=C2=A0=C2=A0=C2=A0 attached to that ES. Th= e Ethernet Tag value MUST be different from

=C2=A0=C2=A0=C2=A0=C2=A0 zero.

=C2=A0

Thanks.

Jorge

=C2=A0

From: BESS <bess-bounces@ietf.org>= ; on behalf of Jaikumar Somasundaram <jaikumar.somasundaram@ericsson.com>
Date: Friday, April 5, 2019 at 6:15 AM
To: "bess@ie= tf.org" <bes= s@ietf.org>
Cc: P Muthu Arul Mozhi <p.muthu.arul.mozhi@ericsson.com>
Subject: [bess] DF election rule in EVPN MH, for untagged interface = - reg

=C2=A0

Hi All,

=C2=A0

RFC7432, section 8.5, talks about DF election al= gorithm (service carving algorithm)

only f=
or <ES, VLAN> for VLAN-based servi=
ce or <ES, VLAN bundle> for VLAN-(aware)

bundle service= .<= /p>

=C2=A0

But there wont be any vlan id for untagged inter= face and so I wonder

how the service carving algorithm can be applied= to elect the DF.

Also, should I use the lower VLAN ID even in the= case of VLAN-bundle

service, for electing the DF?

=C2=A0

Could some one help me to understand this please= ?

=C2=A0

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<snip from RFC = 7432, section 8.5>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

8.5.=C2=A0 Designated Forwarder Election

=E2=80=A6
=C2=A0=C2=A0 Th=
e default procedure for DF election at the granularity of <ES,=

=C2=A0=C2=A0 VL=
AN> for VLAN-based service or <ES, VLAN bundle> for VLAN-(aware)
=C2=A0=C2=A0 bu=
ndle service is referred to as "service carving". <=
u>

=E2=80=A6

=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 Assuming a redundancy group of N PE nodes, for VLAN-based s=
ervice,
=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 the PE with ordinal i is the DF for an <ES, VLAN V> w=
hen (V mod N)
=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 =3D i.=C2=A0 In the case of VLAN-(aware) bundle service, th=
en the
=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 numerically lowest VLAN value in that bundle on that ES MUS=
T be
=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 used in the modulo function.

=E2=80=A6

=3D=3D=3D=3D=3D=3D=3D=3D=3D<snip end>=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=C2=A0

Thanks & Regards

Jaikumar S

=C2=A0

_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
--000000000000745e720585c9e435--