IETF Logo Mail Archive

Re: [Netconf] Issue SN #5: How to represent Source VRF of configured subscription?

"Eric Voit (evoit)" <evoit@cisco.com> Mon, 20 November 2017 14:41 UTC

Return-Path: <evoit@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65AE3129A8D for <netconf@ietfa.amsl.com>; Mon, 20 Nov 2017 06:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 kqAO6qiiW0yq for <netconf@ietfa.amsl.com>; Mon, 20 Nov 2017 06:41:15 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9559129A9C for <netconf@ietf.org>; Mon, 20 Nov 2017 06:41:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1878; q=dns/txt; s=iport; t=1511188874; x=1512398474; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=XGjBWsCttN3Y9pD0guvKRKDCMXdH6mxUZJuOogdyhBc=; b=jfD7CcYAGnWMQPYuzjxVdxPTjnnCWPUS/3XZKEefvc6H+rV8rPUGBJBS YtPB+7a7t/ia8O8UhJ9ys0j55KmG308ipVPuNcqguacR0rMapB7CX35J2 hMDiuYocLF0NP4JLDDliyZC1XCUWbnt2GCsKPshozMKyozvvsEfmMOCHz Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DBAAAw6BJa/4QNJK1YAxkBAQEBAQEBAQEBAQEHAQEBAQGDPGZuLoN4ih+PKIF9lmKCEQofhAeBFQIahGQ/GAEBAQEBAQEBAWsohR4BAQEBAgEjEUUFCQICAQgOAgUDAgIJHQICAhkXFRACBAENDYoVCKhpgieKdAEBAQEBAQEBAQEBAQEBAQEBAQEBAR0FgQqCJYIHgVWFFIUyChkNgk6CYwWRdJBKApUBk1WWBQIRGQGBOQEfOYF0ehWDLgiDCIFOiy+BFAEBAQ
X-IronPort-AV: E=Sophos;i="5.44,427,1505779200"; d="scan'208";a="312421137"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Nov 2017 14:41:13 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id vAKEfDul019727 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 20 Nov 2017 14:41:13 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 20 Nov 2017 09:41:12 -0500
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Mon, 20 Nov 2017 09:41:12 -0500
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Lou Berger <lberger@labn.net>
CC: "Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)" <rwilton@cisco.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [Netconf] Issue SN #5: How to represent Source VRF of configured subscription?
Thread-Index: AdNdqNgU4QJmn1g8RCO8EZWBkLDxQwALeFkAAAkwfMAAWON/kAAnygQAAIFUkLAACvjAgAAKFTbA
Date: Mon, 20 Nov 2017 14:41:12 +0000
Message-ID: <a2e7de033cca411b9e069f15bb9d0d14@XCH-RTP-013.cisco.com>
References: <f11c1a157bec4b0588a955a6385b96bf@XCH-RTP-013.cisco.com> <eb3ddb7b-ff49-b1c6-c91c-14bae2a7895f@cisco.com> <c474b5778c704baab9070b298b5b2a3d@XCH-RTP-013.cisco.com> <383a834a60eb489a9e4fbb9bdf5a5c43@XCH-RTP-013.cisco.com> <31442888-3dba-7834-c408-bd7986b9e381@cisco.com> <57573502664643a2bf6b9af22b52e69c@XCH-RTP-013.cisco.com> <20171120134305.h5q3ghfml2vtoy7n@elstar.local>
In-Reply-To: <20171120134305.h5q3ghfml2vtoy7n@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/juTCAwoqYtQDT6T7NecU3A-7OmI>
Subject: Re: [Netconf] Issue SN #5: How to represent Source VRF of configured subscription?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 14:41:16 -0000

> From: Juergen Schoenwaelder, November 20, 2017 8:43 AM
> 
> On Mon, Nov 20, 2017 at 01:34:07PM +0000, Eric Voit (evoit) wrote:
> 
> [...]
> 
> > I think that I would call the feature "supports-vrf" rather than "vrf".
> >
> > <Eric> “supports-vrf” is fine with me.  Also as we only have one transport
> per subscription, any error checking on configuration should be
> straightforward.
> >
> 
> Since this same question (how to support VRFs) has come up in other
> contexts, it would really be good if it would be documented, say in the
> network instances draft, how other protocol models should refer to VRFs -
> ideally with the rationale behind it.

I agree that it would be helpful to include supporting context within the network instances draft.  Some elements worth covering:

(a) a "supports-vrf" if-feature maintained within network-instances which is available to any model wanting to refer to a VRF.

(b) Examples of constraint checking to see if a /network-instances/network-instance/name is only of root type:  vrf-root or vv-root.  (I.e., don't let someone configure an L2VPN via a Leafref)

Eric

> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

v2.23.0 | Report a Bug | By Email