Re: [bess] BGP common parameter Yang module

Giles Heron <giles.heron@gmail.com> Fri, 10 February 2017 16:18 UTC

Return-Path: <giles.heron@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 5C843129A26 for <bess@ietfa.amsl.com>; Fri, 10 Feb 2017 08:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 L4MraxQzqv7z for <bess@ietfa.amsl.com>; Fri, 10 Feb 2017 08:18:46 -0800 (PST)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (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 57592129989 for <bess@ietf.org>; Fri, 10 Feb 2017 08:18:46 -0800 (PST)
Received: by mail-wr0-x22d.google.com with SMTP id i10so111609362wrb.0 for <bess@ietf.org>; Fri, 10 Feb 2017 08:18:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=a3BwcAP0wQo4H07zF0oB1h46eS1KITNIRC2OPtzUo6M=; b=tNmNcpsLZ8MvMRbML8+Ae2rOZAdtioPWyS4huUV6AT0BH+n/Lm31Mb/D/6hC0MGH0f DazSSlL7gastRTBZqUHGtDu1Y23sAnWkSWklgC1Wx4F/Iv+gEK72XNbuke9GUVbw8RN8 gGqh6N+6tzrgrnD863z7JJD+2vYMuofdfp5yuz8hc1bBCKnUfGQ6/8cbuQC5NVNtSk+1 Jf1mw6+QxxPjBqOhNbkaNaiMifWW6Bg3DkmyaTmCAT3MGwAtgqObQLDSU8EuTXwTkSnn eLNSCgcSd3z+/bWxfqp/zmvsRfycTXmXVKv+tS87mqM2Tz/Y0MKEMAB0xh4beryXYVLo KjsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=a3BwcAP0wQo4H07zF0oB1h46eS1KITNIRC2OPtzUo6M=; b=A07/pZ0zwtiMLEurVnDOvazEh0lRdqh7b/+tVWiOAxPsywNlCa95UnFSf1hrciXl05 ctl/S5kNxAV+OIxoBbrk6CH6tAUKW/ZQ+T2yQLfrHOi2nffV5u5G1t+R71VbJome6ooE qwv7QU+bYgANQouE+xZWHwUwuB8ua17+h0lfMUdPYQcKU7QIJ89fcQR0IJEhg9vKhcX1 L6gGWkyX1Vs8wNZ9OgH+uCvNJH88AlXOlkVGVIG0PQPa0aibFrc2Bi7rD6CTOhIouZM7 e1mih/84m/xhnyssxTOjzKhPRhWagpZyUJclidJRf/x8RRByqUp31nAktkzalv+Rs+/2 zkjQ==
X-Gm-Message-State: AMke39lT948Tg0teEJPv6jXDBEcc+TgWZe4BeK+WR5cRaGfaHoMnT44uzIr+NfgnlmldDA==
X-Received: by 10.223.134.151 with SMTP id 23mr9761948wrx.0.1486743524890; Fri, 10 Feb 2017 08:18:44 -0800 (PST)
Received: from ams-giheron-nitro3.cisco.com ([173.38.220.52]) by smtp.gmail.com with ESMTPSA id k195sm2200058wmd.7.2017.02.10.08.18.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 08:18:44 -0800 (PST)
From: Giles Heron <giles.heron@gmail.com>
Message-Id: <3A8EF0FD-3307-435F-A3BE-F4F90E6B47A1@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0D28E1FC-0FE5-4B1D-B0CA-AE724E3B861F"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Fri, 10 Feb 2017 16:18:42 +0000
In-Reply-To: <D4C33B0D.9C077%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
References: <D4C33B0D.9C077%acee@cisco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/1buSlwIohVcvLeYmo7T9jd26Duc>
Cc: "Patrice Brissette \(pbrisset\)" <pbrisset@cisco.com>, "Shah, Himanshu" <hshah@ciena.com>, "bess@ietf.org" <bess@ietf.org>, "Dhanendra Jain \(dhjain\)" <dhjain@cisco.com>
Subject: Re: [bess] BGP common parameter Yang module
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Feb 2017 16:18:48 -0000

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.

Giles

> On 10 Feb 2017, at 14:51, Acee Lindem (acee) <acee@cisco.com> 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. 
> 
> https://www.ietf.org/id/draft-ietf-rtgwg-routing-types-00.txt <https://www.ietf.org/id/draft-ietf-rtgwg-routing-types-00.txt>
> 
> Thanks,
> Acee 
> P.S. We plan an update next week but the RD and RT definitions have not changed. 
> 
> 
> 
> From: BESS <bess-bounces@ietf.org <mailto:bess-bounces@ietf.org>> on behalf of "Patrice Brissette (pbrisset)" <pbrisset@cisco.com <mailto:pbrisset@cisco.com>>
> Date: Friday, February 10, 2017 at 9:26 AM
> To: "bess@ietf.org <mailto:bess@ietf.org>" <bess@ietf.org <mailto:bess@ietf.org>>
> Cc: "Dhanendra Jain (dhjain)" <dhjain@cisco.com <mailto:dhjain@cisco.com>>, Himanshu Shah <hshah@ciena.com <mailto:hshah@ciena.com>>
> Subject: [bess] BGP common parameter Yang module
> 
> Folks,
>  
> 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.
> Regards,
> Patrice Brissette
> _______________________________________________
> BESS mailing list
> BESS@ietf.org <mailto:BESS@ietf.org>
> https://www.ietf.org/mailman/listinfo/bess <https://www.ietf.org/mailman/listinfo/bess>