Re: [bess] BGP common parameter Yang module

Jeff Tantsura <> Fri, 10 February 2017 19:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 60613129B3D for <>; Fri, 10 Feb 2017 11:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Status: No, score=-2.698 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AzRmmFrJmXw7 for <>; Fri, 10 Feb 2017 11:43:24 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c00::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 947BE129B3B for <>; Fri, 10 Feb 2017 11:43:24 -0800 (PST)
Received: by with SMTP id 68so1136337pfx.2 for <>; Fri, 10 Feb 2017 11:43:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=c9rFqV0JURli+x1DjNwBWQ5rgJoUSmVpe5A3mgpeKMk=; b=YC/feqc34TGj1yKWwDJVj3AaID0z1RC2UwLy4rwjyBUDWLGq2ZduW07JtRe0WJ6C9F 14H4XOxKRSQElkYFYCE911LEGuqRnMz6mBr9Z9gYvZNuRYhWUPzXEs+zOdwuafPavukx rfygek43YmB3N2OZnMmjrZy1SiNzStRxKq7b/6L0BWacJLapN0Vjbs07uJkRhPqQK483 Dj2Vkii1WCwC1l/Gb8raUpQrAFd7bybKDOtkcCUEHKR6jhEkB/wXKXuJZhuAtd3KTYT4 yeGEHvPUzGMCI3iANGCBDSJsAbN4zpy/Et8NVyIvJuKxeDVH1sJyEIKUZB57lEQY8C5y NRnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=c9rFqV0JURli+x1DjNwBWQ5rgJoUSmVpe5A3mgpeKMk=; b=IgJ0wn6pOGctws3kNlzmGwNwggqn0VzgnovkGdRsUGlIxWnpuEa/HBEc0/EiMWQbZM koKzuPfTkHBe0vBdfOAfCV4WGhczlXfQ48ecc4GNH6Yz+H1JwpHetcJ3/Nf3LDgynfBY vFqKU0KBmkn8Q4YI4p5dhyGnWYau6SivmVY0jPot02eoivT89Pp6fUGl+Wq6HR+pXL4j Ds7XSvQSYP8BfhXIZKnyaXeMsKUO95ZUpmm6GffVoIfaMYp8JaosMRJ5Ds2GHXE0DFDJ afWZpYwYJNbESKHpxJCNkdhkTs4sHYj1BEizlFUmYT3IAFcbiyHScnjDpvS03CFYJ9r9 qyVQ==
X-Gm-Message-State: AMke39nv8AMNNIQXHsxd28dZYlBoneYezbQf+i3rxeQZqRLIdmOw3tButoAVEW3kQVVEbQ==
X-Received: by with SMTP id i61mr13437380plb.88.1486755804070; Fri, 10 Feb 2017 11:43:24 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id m21sm7229449pgh.4.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 11:43:23 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Fri, 10 Feb 2017 11:43:22 -0800
From: Jeff Tantsura <>
To: "Acee Lindem (acee)" <>, Giles Heron <>
Message-ID: <>
Thread-Topic: [bess] BGP common parameter Yang module
References: <> <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3569571803_1635499773"
Archived-At: <>
Cc: "Patrice Brissette \(pbrisset\)" <>, "" <>, "Shah, Himanshu" <>, "Dhanendra Jain \(dhjain\)" <>
Subject: Re: [bess] BGP common parameter Yang module
X-Mailman-Version: 2.1.17
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, 10 Feb 2017 19:43:26 -0000

I’d prefer common grouping in draft-ietf-rtgwg-routing-types and references from any other model using it 







From: BESS <> on behalf of "Acee Lindem (acee)" <>
Date: Friday, February 10, 2017 at 08:42
To: Giles Heron <>
Cc: "Patrice Brissette (pbrisset)" <>om>, "Shah, Himanshu" <>om>, "" <>rg>, "Dhanendra Jain (dhjain)" <>
Subject: Re: [bess] BGP common parameter Yang module


Hi Giles,

I will add the route-target-type type (enum of import, export, both) but for a general grouping, it appears there are some discrepancies between the 3 models. Assuming the types: route-discriminator, route-target, and route-target-type, can you provide a consensus grouping that all the models would use? 




From: Giles Heron <>
Date: Friday, February 10, 2017 at 11:18 AM
To: Acee Lindem <>
Cc: "Patrice Brissette (pbrisset)" <>om>, "" <>rg>, Himanshu Shah <>om>, "Dhanendra Jain (dhjain)" <>
Subject: Re: [bess] BGP common parameter Yang module


Hi Acee, 


In general seems that for any BGP VPN (L2 or L3) you have an RD plus a list of RTs (which can be import, export or both) - so I’d prefer that to be defined in a shared grouping (more or less as per the structure Patrice gave below) than to force each model to redefine it.




On 10 Feb 2017, at 14:51, Acee Lindem (acee) <> wrote:


Hi Patrice – we are working fervently on a common IETF routing types model. We have both route-target and router-distinguisher types defined there. The work is being done in the Routing WG. Our intension is to accelerate standardization so it doesn’t hold up standardization of the importing modules. Please comment as to whether you think this meets BESS requirements.




P.S. We plan an update next week but the RD and RT definitions have not changed. 




From: BESS <> on behalf of "Patrice Brissette (pbrisset)" <>
Date: Friday, February 10, 2017 at 9:26 AM
To: "" <>
Cc: "Dhanendra Jain (dhjain)" <>om>, Himanshu Shah <>
Subject: [bess] BGP common parameter Yang module




As part of EVPN, L2VPn and L3VPN Yang model, there is a “module” common to all 3 Yang models.


      |     +--rw bgp-parameters

      |     |  +--rw common

      |     |     +--rw rd-rt* [route-distinguisher]

      |     |        +--rw route-distinguisher    string

      |     |        +--rw vpn-target* [rt-value]

      |     |           +--rw rt-value    string

      |     |           +--rw rt-type     bgp-rt-type



It will be interesting to create a common BGP parameter Yang module as shown above. I think it just makes sense.

However, there is a minor challenge; that module require a home (a draft).

I’m looking for feedback about the best place/draft for such a module.


Thanks for your help.


Patrice Brissette

BESS mailing list


_______________________________________________ BESS mailing list