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

"Chettle, Nick" <> Fri, 05 September 2014 15:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CB8FD1A08BE for <>; Fri, 5 Sep 2014 08:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sFm51x0s5J8C for <>; Fri, 5 Sep 2014 08:38:27 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 46F6F1A0739 for <>; Fri, 5 Sep 2014 08:38:27 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1024.12; Fri, 5 Sep 2014 15:38:25 +0000
Received: from (2a01:111:f400:7e00::121) by (2a01:111:e400:9800::31) with Microsoft SMTP Server (TLS) id 15.0.1024.12 via Frontend Transport; Fri, 5 Sep 2014 15:38:24 +0000
Received: from CHIXEDG01.BSKYB.COM ( by ( with Microsoft SMTP Server (TLS) id 15.0.1010.11 via Frontend Transport; Fri, 5 Sep 2014 15:38:24 +0000
From: "Chettle, Nick" <>
To: Philip Matthews <>, v6ops list <>, Owen DeLong <>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-02.txt
Thread-Index: AQHPyKvi+JIp7a6Fsk6A4ZTqboez95vxuk2AgADzMIA=
Date: Fri, 5 Sep 2014 15:38:22 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:; CTRY:GB; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(6009001)(428002)(24454002)(377424004)(51874003)(51704005)(479174003)(505014003)(189002)(199003)(95666004)(118246001)(90102001)(74662001)(25786005)(74502001)(26826002)(230783001)(31966008)(4396001)(53416004)(2656002)(77096002)(87936001)(21056001)(85852003)(83072002)(15975445006)(83506001)(107046002)(36756003)(15202345003)(106116001)(105586002)(92566001)(106466001)(86362001)(92726001)(47776003)(20776003)(64706001)(101416001)(46102001)(81342001)(77982001)(85306004)(81542001)(80022001)(19580395003)(6806004)(44976005)(83322001)(19580405001)(23756003)(79102001)(99396002)(76482001)(54356999)(50466002)(76176999)(50986999); DIR:OUT; SFP:; SCL:1; SRVR:AMSPR07MB470; H:CHIXEDG01.BSKYB.COM; FPR:; MLV:ovrnspm;; MX:1; A:0; LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;UriScan:;
X-Forefront-PRVS: 0325F6C77B
Received-SPF: None ( does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is;
Cc: Victor Kuarsingh <>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-design-choices-02.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Sep 2014 15:38:34 -0000

Hi Phillip,

I think this is document pulls a lot of useful best practices together. A
couple of minor points.

   o  It is not often not possible to identify the interface or link (in
      a database, email, etc) by giving just its address without also
      specifying the link in some manner.

I think this should read "often not possible² ?

Additionally, in section 2.1.2 you talk about link-local vs. GUA/ULA for
point-to-point links, it might be useful to reference something on address
assignment here (/64, /126, /127, etc.). I see you¹ve already referenced
RFC5375 in the introduction however it may be worth a second mention here?

Cheers, Nick

On 05/09/2014 03:07, "Philip Matthews" <> wrote:

>As you can see, Victor and I have just submitted an update to the Design
>Choices draft.
>This is a significant update, with completely re-written text around IGP
>choice and BGP. The IGP choice section looks more completely at the
>various options, while the BGP section now considers iBGP as well as
>eBGP. This update also addresses comments sent to us by Owen DeLong
>(thanks, Owen, and sorry that we took so long to address them!).
>In terms of draft status, we are thinking that we are getting close to a
>final version. There are surely problems with the draft that need
>correcting, but we don't have any plans to add significant new content.
>So please read this version with that in mind.
>Thanks in advance for any comments, and sorry that we have been a bit
>slow in updating the draft.
>On 2014-09-04, at 21:50 , wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> This draft is a work item of the IPv6 Operations Working Group of the
>>        Title           : Design Choices for IPv6 Networks
>>        Authors         : Philip Matthews
>>                          Victor Kuarsingh
>>      Filename        : draft-ietf-v6ops-design-choices-02.txt
>>      Pages           : 16
>>      Date            : 2014-09-04
>> Abstract:
>>   This document presents advice on the design choices that arise when
>>   designing IPv6 networks (both dual-stack and IPv6-only).  The
>>   intended audience is someone designing an IPv6 network who is
>>   knowledgeable about best current practices around IPv4 network
>>   design, and wishes to learn the corresponding practices for IPv6.
>> The IETF datatracker status page for this draft is:
>> There's also a htmlized version available at:
>> A diff from the previous version is available at:
>> Please note that it may take a couple of minutes from the time of
>> until the htmlized version and diff are available at
>> Internet-Drafts are also available by anonymous FTP at:
>> _______________________________________________
>> v6ops mailing list
>v6ops mailing list

Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trademarks of British Sky Broadcasting Group plc and Sky International AG and are used under licence. British Sky Broadcasting Limited (Registration No. 2906991), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of British Sky Broadcasting Group plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD.