Re: [Rtg-yang-coord] [netmod] rib-data-model and routing-cfg

Ladislav Lhotka <lhotka@nic.cz> Wed, 21 October 2015 13:52 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B36EB1A87ED; Wed, 21 Oct 2015 06:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.061
X-Spam-Level:
X-Spam-Status: No, score=-0.061 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, J_CHICKENPOX_14=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 ZirfiOA5wV6C; Wed, 21 Oct 2015 06:52:31 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C3091A87E6; Wed, 21 Oct 2015 06:52:31 -0700 (PDT)
Received: from [IPv6:2001:718:1a02:1:38e4:f37d:433d:89fd] (unknown [IPv6:2001:718:1a02:1:38e4:f37d:433d:89fd]) by mail.nic.cz (Postfix) with ESMTPSA id E67BF181855; Wed, 21 Oct 2015 15:52:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1445435549; bh=1fFnwGFK3ggpQismo/YhcHglVUqmHE2pbOe1cYH6Z9E=; h=From:Date:To; b=NUuihW3Hl4QpO4NncpIaFvG5dbd53aboVbMRCSmYTDQ15BHxO93700IgtfVfpfGB+ /PrXULL3/yYCnzs89X3Bd7WZ8VlYaCJtdSF3f97+eUaSDw1W6ODfEPQwOMy9xWy4RT ukOCJTI+do36Mk/Axd9Zc6bZXjW8/KNoIZ0Gr31c=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <etPan.56279299.3a0e4920.12fd@piccolo.local>
Date: Wed, 21 Oct 2015 15:52:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C6909AC-51B9-42D8-82EB-B5006BABC845@nic.cz>
References: <7E24547E-B42B-46E2-AF76-F7639D61963F@nic.cz> <D23D3103.34500%acee@cisco.com> <D2429721.34A0E%acee@cisco.com> <DBF22257-A7A2-4679-927A-EBCC1022FE13@nic.cz> <D242C30E.34C2A%acee@cisco.com> <m27fmowezi.fsf@birdie.labs.nic.cz> <D2458D0F.36813%acee@cisco.com> <etPan.56279299.3a0e4920.12fd@piccolo.local>
To: Rob Shakir <rjs@rob.sh>
X-Mailer: Apple Mail (2.3094)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/IO10CAn5c7NiIjNYASzVbgySJTI>
Cc: Routing YANG <rtg-yang-coord@ietf.org>, "i2rs@ietf.org" <i2rs@ietf.org>, "Acee Lindem \(acee\)" <acee@cisco.com>, NETMOD WG <netmod@ietf.org>, Routing WG <rtgwg@ietf.org>
Subject: Re: [Rtg-yang-coord] [netmod] rib-data-model and routing-cfg
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>, <mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2015 13:52:32 -0000

> On 21 Oct 2015, at 15:26, Rob Shakir <rjs@rob.sh>; wrote:
> 
> On 15 October 2015 at 15:13:38, Acee Lindem (acee) (acee@cisco.com) wrote:
>> 
>> Do we really see associating the same interface with different 
>> routing-instances for IPv4 and IPv6? I can seem to remember the use case 
>> and it does add complexity forever. 
>> 
> 
> At least two of the operators for whom I have worked utilise this functionality (providing separate L3VPNs for IPv6 and IPv4) - so in my experience, it is not possible to make this simplification.

One option would be to create two virtual interfaces - one for IPv4 VPN and another for IPv6 VPN, and define routing-instance and addresses separately for each.

Lada

> 
> r.

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C