Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-08.txt

"Ackermann, Michael" <MAckermann@bcbsm.com> Wed, 08 July 2015 15:02 UTC

Return-Path: <mackermann@bcbsm.com>
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 603421A0011 for <v6ops@ietfa.amsl.com>; Wed, 8 Jul 2015 08:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3] 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 nozC8nsBZ_Q6 for <v6ops@ietfa.amsl.com>; Wed, 8 Jul 2015 08:01:55 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF981A000D for <v6ops@ietf.org>; Wed, 8 Jul 2015 08:01:55 -0700 (PDT)
Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with SMTP id 1D916103173 for <v6ops@ietf.org>; Wed, 8 Jul 2015 10:01:54 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id AC4AB1217DA; Wed, 8 Jul 2015 10:01:53 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id 8BF722F70BC; Wed, 8 Jul 2015 10:55:09 -0400 (EDT)
Received: from pwn401ea100.ent.corp.bcbsm.com (unknown [10.64.80.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by imsva2.bcbsm.com (Postfix) with ESMTP id 7A9472F709B; Wed, 8 Jul 2015 10:55:09 -0400 (EDT)
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA100.ent.corp.bcbsm.com ([::1]) with mapi id 14.01.0438.000; Wed, 8 Jul 2015 11:01:47 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Philip Matthews <philip_matthews@magma.ca>, v6ops list <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-08.txt
Thread-Index: AQHQuDJV+Hpx49dFOEuzsXSTRDyQUZ3POuEAgADYyyA=
Date: Wed, 8 Jul 2015 15:01:51 +0000
Deferred-Delivery: Tue, 7 Jul 2015 21:00:00 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CE24B25@PWN401EA160.ent.corp.bcbsm.com>
References: <20150706212506.2640.97532.idtracker@ietfa.amsl.com> <23C53E8B-6029-4782-8567-3A9984D556AC@magma.ca>
In-Reply-To: <23C53E8B-6029-4782-8567-3A9984D556AC@magma.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.10.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-VPM-MSG-ID: caa4903a-aa49-40bc-94e8-21212d24742c
X-VPM-HOST: vmvpm01.z120.zixworks.com
X-VPM-GROUP-ID: 9c9b93e6-660a-4bfe-a193-56eb7ffc9bef
X-VPM-ENC-REGIME: Plaintext
X-VPM-CERT-FLAG: 0
X-VPM-IS-HYBRID: 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Jkn3uCfs7GMzQzZIj-PMwdPnVO0>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-08.txt
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 08 Jul 2015 15:02:02 -0000

Thanks for the great document that Enterprises considering the serious deployment of  IPv6 will find very valuable.  

The initial sections are good in pointing out what this document does and does not address.   Also pointing out RFC's where information on areas NOT addressed can be found. 

In Section 2.1.1 the reference to RFC1918 addresses seems to suggest this is the IPv4 equivalent to ULA's.     Is this a commonly accepted concept?  

In the Chart, under Tunneled,  it says private addresses are likely a better option.   Why?  A subsequent paragraph says something about these addresses having limited visibility.   Is that the rationale?       The paragraph goes on to describe reasons why  PI space is the next best option, but the discourse seems to suggest it may be the better option.     So I come away unclear of which would be "Best".  

Is Section 2.2 intended to address end hosts, as well as Routers (Middleboxes)?   Could the answer be different in certain situations?       Also, is option "a." Dual Stack?   Is there a reason this term is avoided?  

Section 2.2.2, seems to answer a question I have had.  IPAM can/should ignore Link Local addresses.  Is this the intended conclusion?   
In general, this section has a great deal of useful information regarding the use of Link-Local-Only addresses.  

Section 2.4.1, the IGP Choice chart shows 4 Multiple Known Deployments,  but the following paragraph says 3.     Other than that,  the chart contains a lot of relevant information and should be a helpful decision tool.    I also thank you for including EIGRP and RIP, which I recall was difficult and controversial.  

Thanks again for the effort, content and quality put into this document!

Mike 
  
-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Philip Matthews
Sent: Monday, July 06, 2015 5:39 PM
To: v6ops list
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-08.txt

Folks:

Victor and I have just submitted a new revision of the Design Choices draft. There are two main changes:
1. A new section called "Addresses" that discusses the pros and cons of using PI vs. PA vs. Private addresses in your IPv6 or dual-stack network. This addresses some comments we got during the WG Last Call about using ULAs in certain situations. We consider this a significant addition to the draft.
2. Added EIGRP to the section on IGP Choice.  Some of you will recall the discussion around this on the mailing list a couple of months ago.

Victor and I have plans for more revisions to address other WG comments.  In particular, as you may remember, Victor and I have been gathering hard data from operators around the IGPs that are actually used in production networks. Unfortunately, Victor and I both got hit with other stuff in the last few weeks, so we didn't have time to add this data to the draft, or make some other planned changes. So consider this still a work-in-progress with other changes coming.

- Philip
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
 
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.