Re: [Ext] Re: AD Evaluation : draft-ietf-6man-ra-pref64-06

Leo Vegoda <leo.vegoda@icann.org> Thu, 07 November 2019 19:53 UTC

Return-Path: <leo.vegoda@icann.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE46A120255; Thu, 7 Nov 2019 11:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5kE3Jz3vL0ak; Thu, 7 Nov 2019 11:53:26 -0800 (PST)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (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 8641012001A; Thu, 7 Nov 2019 11:53:26 -0800 (PST)
Received: from PFE112-CA-2.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) by ppa5.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id xA7JrOsM015447 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 7 Nov 2019 19:53:24 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 7 Nov 2019 11:53:22 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1497.000; Thu, 7 Nov 2019 11:53:22 -0800
From: Leo Vegoda <leo.vegoda@icann.org>
To: Jen Linkova <furry13@gmail.com>, Suresh Krishnan <Suresh@kaloom.com>
CC: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-ra-pref64@ietf.org" <draft-ietf-6man-ra-pref64@ietf.org>
Subject: Re: [Ext] Re: AD Evaluation : draft-ietf-6man-ra-pref64-06
Thread-Topic: [Ext] Re: AD Evaluation : draft-ietf-6man-ra-pref64-06
Thread-Index: AQHVkTCMshWrGRbR6Euc2J+5rFgk3ad6hzoAgAWgaIA=
Date: Thu, 7 Nov 2019 19:53:21 +0000
Message-ID: <B5015E7D-482C-4EEA-B83C-76EDE740F81F@icann.org>
References: <F1B31C38-7CDB-4057-A573-D6AF76B264D3@kaloom.com> <CAFU7BASEnMTZ71h6sZ3q1SajxtFFrn2dQVEHWiutuG6G+rWJqQ@mail.gmail.com>
In-Reply-To: <CAFU7BASEnMTZ71h6sZ3q1SajxtFFrn2dQVEHWiutuG6G+rWJqQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191013
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.236]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <2D56D52C2DE9BE47A6208CCEF9E04A07@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-07_06:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vLKFeuY1ylb0RddexlaN2Rm2FsI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 19:53:28 -0000

On 11/3/19, 1:58 PM, "ipv6 on behalf of Jen Linkova" <ipv6-bounces@ietf.org on behalf of furry13@gmail.com>; wrote:

[...]

>  > Please use a documentation prefix, say 192.0.2.0/24, instead of the RFC1918 address currently used in the example.
>     
>     Actually I'd agree with Lorenzo here..IMHO 10.0.0.0/8 case describes a

It might be worth noting that RFC 5737 includes this statement in the introduction:

"Documentation also makes use of the ranges reserved in [RFC1918]."

Kind regards,

Leo