Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication

"Ali Sajassi (sajassi)" <> Thu, 14 December 2017 18:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 13CBF12704A for <>; Thu, 14 Dec 2017 10:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VdxSG79VdaKi for <>; Thu, 14 Dec 2017 10:25:01 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 829F91200FC for <>; Thu, 14 Dec 2017 10:25:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=17892; q=dns/txt; s=iport; t=1513275901; x=1514485501; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=izVwTcLCAwLieJmZi5t0hqCP9HRbT4v8P/VEFbHhYIg=; b=OQML4C9fW5C5eZblwdpwKvdWuJtOFlc3udMvMkzKsntpAyXqbxSHt3i2 zzZwOuhA4wVIfiMZCHTiY7OCevQ+d1TGlQ9MLCFua1Kyzwz4XZANXkpQF 4rqHJB5RkZAMjBTT60+7WzusD+2p6l8jexaRVMEVEr7O6HM9uD23vGGBt c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.45,401,1508803200"; d="scan'208,217";a="114538292"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Dec 2017 18:25:00 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id vBEIP0R9006703 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Dec 2017 18:25:00 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Dec 2017 13:24:59 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Thu, 14 Dec 2017 13:24:59 -0500
From: "Ali Sajassi (sajassi)" <>
To: Marco Marzetti <>, Thomas Morin <>
CC: "" <>
Thread-Topic: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication
Thread-Index: AQHTdM5AxSlRFluwPkmVHdFfkfBaX6NDLCyAgAALcQD//74qAA==
Date: Thu, 14 Dec 2017 18:24:59 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.29.0.171205
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_003CD803EAB847F4B36D2E3CD6F8E9A4ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication
X-Mailman-Version: 2.1.22
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: Thu, 14 Dec 2017 18:25:04 -0000

Hi Marco,

If an implementation doesn’t add PMSI to an IMET route, then that implementation is broken. RFC 7432 says:
“In order to identify the P-tunnel used for sending broadcast, unknown
   unicast, or multicast traffic, the Inclusive Multicast Ethernet Tag
   route MUST carry a Provider Multicast Service Interface (PMSI) Tunnel
   attribute as specified in [RFC6514<>].”
An section 9 of evpn-overlay says:
“This route is tagged
   with the PMSI Tunnel attribute, which is used to encode the type of
   multicast tunnel to be used as well as the multicast tunnel
   identifier. The tunnel encapsulation is encoded by adding the BGP
   Encapsulation extended community as per section 5.1.1.”

There should be no ambiguity here. The BGP encapsulation EC can be optional if MPLS encap or static config is used – ie, section 5.1.3 says” if the BGP Encapsulation extended community is not present, then either MPLS encapsulation or a statically configured encapsulation is assumed”.


From: BESS <> on behalf of Marco Marzetti <>
Date: Thursday, December 14, 2017 at 6:20 AM
To: Thomas Morin <>
Cc: "" <>
Subject: Re: [bess] draft-ietf-bess-evpn-overlay-10 PMSI with Ingress Replication


I have encountered an implementation that is not attaching any PMSI to the IMET.
The authors think they don't really need it because they only support Ingress Replication.
Such behavior breaks interoperability with other implementations that are dropping the NLRI if PMSI is not attached.

So i looked at draft-ietf-bess-evpn-overlay-10 and noticed that there's no clear indication of what the proper behavior is.
As said i assumed i had to look at RFC7432 and RFC6514 (and i did it), but i wasn't 100% sure and i preferred to ask.

Onestly you already made my day by confirming what i thought.
My suggestion was to make things more clear, but i admit that it could look redundant.


On Thu, Dec 14, 2017 at 2:39 PM, Thomas Morin <<>> wrote:
Hi Marco,

Marco Marzetti, 2017-12-14 12:25:
> I am writing this email asking you to clarify what's the suggested
> behavior when PMSI Tunnel Type is set to "Ingress Replication" (type
> 6) as draft-ietf-bess-evpn-overlay-10 only suggests what to do with
> multicast tunnel trees.
> I think the originating PE should conform with RFC6514 and RFC7432
> (from which you've taken inspiration) and always (RFC2119 MUST)
> attach PMSI Tunnel attribute with the Tunnel Type set to Ingress
> Replication and Tunnel Identifier set to a routable address of the PE
> itself (more specifically NVE's IP address).
> Is that correct?
> In that case i suggest to add the following line at the end of
> Section 9.
> """
> For Ingress Replication the PE should follow what's stated in RFC6514
> Section 5 .
> """

The text of section 9 lists "Ingress Replication" in the list of tunnel
types that can be used. My understanding is that, in the absence of
anything being specifically said for Ingress Replication, an
implementation should follow what is said in RFC7432 and RFC6514. (What
other specs could it follow to implement this supported type ? RFC7432
and RFC6514 are more than an inspiration here, these are specs that the
document refers to explicitly)

So I'm not sure that it is useful or needed to add text.

Can you perhaps expand on why the current text would possibly be
ambiguous, misleading or incomplete...?