[bess] SHL label

gangadhara reddy chavva <meetgangadhara@gmail.com> Mon, 03 June 2019 11:05 UTC

Return-Path: <meetgangadhara@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 E06101201EE for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 04:05:41 -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_HELO_NONE=0.001, 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 jk-F2n2HNGvn for <bess@ietfa.amsl.com>; Mon, 3 Jun 2019 04:05:40 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 CA4B61201A0 for <bess@ietf.org>; Mon, 3 Jun 2019 04:05:39 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id o13so15744602lji.5 for <bess@ietf.org>; Mon, 03 Jun 2019 04:05:39 -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=QqbkQZNrCIbrYfbPhQEa6mqHNELikuhkpmdx2+KXwFQ=; b=K2vRpYKqfGaVIrRXz+ZRB0YrTBri8234Wyd1EZAqhoispfSlfD5Aad90M/bZ9D3GbM 5JZz0BhAAcTYBkLZTETwATjDYI/x/FeCK9sqSDAlNeYyXTGCgHeIxk8d3Z9nNZpSfbpL zMwFjhI7vFNEnUNu1A5yDRnYL0l7tEvjnG/8AdfLB3d21gMtL7wibCHHEZQ/Qvzw3ixU yHgECjhRECsDAjGgxG6ln1Iv+4QPsPnbw8ioJLIRi4LX+qX3Z1NwSLdfgc1eij88vD+b i+T0+BpwLLtKg/sdX2x5kV3nAFUPenc82wZMsRqK4jsPUk+iw2O61vyBUOJMrTu9jOlc m6sA==
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=QqbkQZNrCIbrYfbPhQEa6mqHNELikuhkpmdx2+KXwFQ=; b=C8j1Bm2C9YVuYg/4xCme+XBlE7dHr5fB2Vv1Q2nIcH7g1omygVg0vyFIqoWvfLicAk c89jD2TZuJPwlfvf52ZbATAC2EcIY+vwDw8KcJ0sJhu7NdS5jzKym8wlZJTrRjRt3Op3 UEROmdhV1Gk/pi8jo2+HFYFV/JnTrfXgtOpkm82kGE2jZteQL44KQ1ULTCcRjY+r3Z/x PhfCLOCTfDNT15+zb9633NWHLOS2aU6/VaVYHo9TaAFoLck7zo4+6v6tUr6aiZpS5s0L AaTzWPY7i5EFDhF05jltgajwbQ42f6bQvogoKS0BEqAyGlxdQ4YNkIZ0I21xf7kG8wYr GwQg==
X-Gm-Message-State: APjAAAXJvQSi6/3wW56HsGO625jUPRfH5N+JBzAGgkeRqSFxgltg0qC8 t5e9vyDN/H8bphslWZiN4u9f3r3A5F8jzysk07TsCMLp
X-Google-Smtp-Source: APXvYqwERkb/zr1KMQVF81qQSTcojEaStEq5vSRm/cibSo+HqiuIumAA3CKnClxXOOD8V0rLkCEKEjftCft3UxYjtec=
X-Received: by 2002:a2e:9e07:: with SMTP id e7mr6157551ljk.55.1559559937457; Mon, 03 Jun 2019 04:05:37 -0700 (PDT)
MIME-Version: 1.0
From: gangadhara reddy chavva <meetgangadhara@gmail.com>
Date: Mon, 03 Jun 2019 16:35:26 +0530
Message-ID: <CAAG_SC-_P53HzYYPBTwag2bN6WOk+xbOM88E6A1Zfg73Aa_Apw@mail.gmail.com>
To: bess@ietf.org, "Rabadan, Jorge (Nokia - US/Mountain View)" <jorge.rabadan@nokia.com>
Content-Type: multipart/alternative; boundary="000000000000140428058a6958a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/NdzeyL0Vud1tMK9f5Q63hXMirE8>
Subject: [bess] SHL label
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: Mon, 03 Jun 2019 11:05:42 -0000

Hi Jorge,

I have a Question on EVPN MH SHL(split horizon label).

Can ESI share the different SHL label for the same ESI?

*case 1:* in the same ESI one customer EVPN VPN can have ingress
replication for the BUM traffic and second EVPN VPN ine the same ESI can do
P2MP? in this case SHL label should be different.

*case 2: *can VPLS allocate one SHL and VPWS can allocate diffrent SHL
label? or SHL should be same per ESI irrespective of number of applications
enabled in that ESI.

Thanks,
Gangadhar