[netmod] Question about ietf-routing

Alex Campbell <Alex.Campbell@Aviatnet.com> Tue, 06 June 2017 23:43 UTC

Return-Path: <Alex.Campbell@Aviatnet.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8AD1B128B4E for <netmod@ietfa.amsl.com>; Tue, 6 Jun 2017 16:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id gZdwjWRmlPC6 for <netmod@ietfa.amsl.com>; Tue, 6 Jun 2017 16:43:20 -0700 (PDT)
Received: from mail-send.aviatnet.com (mail-send.aviatnet.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC0C5120721 for <netmod@ietf.org>; Tue, 6 Jun 2017 16:43:20 -0700 (PDT)
From: Alex Campbell <Alex.Campbell@Aviatnet.com>
To: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: Question about ietf-routing
Thread-Index: AQHS3x5Bkeeb5JjXkkKedeZMDHRzCg==
Date: Tue, 6 Jun 2017 23:43:19 +0000
Message-ID: <1496792599527.55133@Aviatnet.com>
Accept-Language: en-NZ, en-US
Content-Language: en-NZ
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_149679259952755133Aviatnetcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/db0G1bnYUk--H_G2DCGOSpikaZU>
Subject: [netmod] Question about ietf-routing
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jun 2017 23:43:22 -0000


I noticed that the ietf-routing YANG (published in RFC 8022) allows for multiple instances of each control plane protocol, as well as multiple RIBs per address family.
However I don't see any way to associate one with the other. Without additional configuration, protocols will only place their routes in default RIBs.
Is it intended that this will be left to vendor-specific modules and/or future standards?