Re: [v6ops] Looking for info on IGP choices in production dual-stack networks

Philip Matthews <philip_matthews@magma.ca> Fri, 05 June 2015 14:27 UTC

Return-Path: <philip_matthews@magma.ca>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3DF1B301C for <v6ops@ietfa.amsl.com>; Fri, 5 Jun 2015 07:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 9U_p5KeWdF11 for <v6ops@ietfa.amsl.com>; Fri, 5 Jun 2015 07:27:45 -0700 (PDT)
Received: from tor-smtp-02.primus.ca (mail20.primus.ca [216.254.141.187]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6FA1B3018 for <v6ops@ietf.org>; Fri, 5 Jun 2015 07:27:45 -0700 (PDT)
Received: from [24.114.87.206] (helo=[172.20.10.4]) by tor-smtp-02.primus.ca with esmtpa (Exim 4.84) (envelope-from <philip_matthews@magma.ca>) id 1Z0sb2-00077p-Fe; Fri, 05 Jun 2015 10:27:44 -0400
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <817349377.6562637.1433472844577.JavaMail.yahoo@mail.yahoo.com>
Date: Fri, 5 Jun 2015 10:27:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5A1FD44-0ECD-41CE-AEC6-7A85C80D465E@magma.ca>
References: <F41523E0-37E5-46B2-90FB-19A1FAC63DFE@magma.ca> <817349377.6562637.1433472844577.JavaMail.yahoo@mail.yahoo.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
X-Mailer: Apple Mail (2.1085)
X-Authenticated: philip_matthews - ([172.20.10.4]) [24.114.87.206]
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/FgMMEp216ErsFQZ-YGwRhuaJx7A>
Cc: v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] Looking for info on IGP choices in production dual-stack networks
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2015 14:27:47 -0000

[Reformatting and excerpting my original message and Mark's reply  due to some technical issues]

On 2015-06-04, at 22:54 , Mark ZZZ Smith wrote:
>> Victor and I are looking for information on the IGP combinations people are running in their dual-stack networks. We are gathering this information so we can document in our Design Choices draft which IGP choices are known to work well (i.e., people actually run this combination in production networks without issues). The draft will not name names, but just discuss things in aggregate: for example, "there are 5 large production networks that run OSPF for IPv4 and IS-IS for IPv6, thus that combination is judged to work well".
>>  
> I don't think this is really a good thing to be stating in such abstract terms, that is, at the IGP protocol level. I'd think the successful co-existence or not of IGPs, assuming the protocols themselves aren't broken (e.g., by using the same field value id for two different things), is  implementation dependent, and dependent on which specific revision of the implementation a network has chosen to deploy, and how that network has chosen to deploy it. For example, a literally perfect implementation of OSPF + IS-IS might be "judged to work badly" if deployed badly (by, for example, putting too many routers in the backbone area, overloading control plane resources.) 
> 
> I'm wondering a bit what the fundamental question trying to be being answered is? Is it to try to capture some information on the current popularity of various IGPs used to carrying IPv6 routes, and how popular the use of a single IGP to carry both IPv4 and IPv6 routes is?   What particular question or questions would the reader have that this text is trying to provide an answer for?
> 
> Regards,
> Mark.

In the draft we have a table that lists the various combinations of IGPs for IPv4 and IPv6 and gives a few properties for each combination that people might want to consider when selecting a combination. The idea is to give people with less IPv6 knowledge some guidance and perhaps some reassurance when selecting a combination. 

One of the columns in the table is called "Known to work well".  Originally, Victor and I populated this based on our own experiences and biases, without consulting others.  However, in mid-April Mikael Abrahamsson commented on this table, noting that he has actually run one of the combinations that we marked as "not known to work well".  So Victor and I decided that we should be more scientific in populating this column.  Hence this survey of what people actually run.

Do you think the draft should NOT contain this type of information?  I can say that I have found the responses so far to be very interesting, even though it has been just a day so far.

Or do you have a suggestion for something else useful to say about each combination?  Victor and I feel it might be nice to add more information about each combination, but we don't have any ideas yet on what the "more information" should be.  We would love to hear from anyone who has a suggestion.

- Philip