Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?

Mark Smith <markzzzsmith@gmail.com> Fri, 06 November 2015 06:51 UTC

Return-Path: <markzzzsmith@gmail.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 D258B1A916F for <v6ops@ietfa.amsl.com>; Thu, 5 Nov 2015 22:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 a-0zbq3kwXpp for <v6ops@ietfa.amsl.com>; Thu, 5 Nov 2015 22:51:12 -0800 (PST)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 202321A9132 for <v6ops@ietf.org>; Thu, 5 Nov 2015 22:51:12 -0800 (PST)
Received: by ykdv3 with SMTP id v3so84365868ykd.0 for <v6ops@ietf.org>; Thu, 05 Nov 2015 22:51:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=K+O9zgjCj1cCyeqEOFCRrnCCDVm3g+Fzf36sTY20bwI=; b=Oh75DqCpISLVNaPvpvlSfLBG/FIO5ItbQAi5/CGraPTFHRQMQjRMsY12VSPRNVDeSj 78jh/F3UC2dlaSAS0XsHfS8c9VtG1cgWa+fynSVd2yNVHEG0zy4uTPWXdSQzqjvzECGk DCPxkqaa58n3wIBG7CEMa3TPA1qS/h6svIpFLKhZWoxSl9GsjClLOm58GYTceS92Qjbn 5OVfAoXQPBf2JwsU3vYJm+7R0I0scSGkgxqgDvMeYCiKNszhV2fejAdPfAkl7W8yy4mJ PT+wMaZb3z6EvWPYjvJPGuMTGxP45jLa1c8UUf0oK2TA8EZHQRY4HtPEAF3tpnao58TN rEqA==
MIME-Version: 1.0
X-Received: by 10.31.162.148 with SMTP id l142mr11181510vke.40.1446792671410; Thu, 05 Nov 2015 22:51:11 -0800 (PST)
Received: by 10.103.67.194 with HTTP; Thu, 5 Nov 2015 22:51:11 -0800 (PST)
Received: by 10.103.67.194 with HTTP; Thu, 5 Nov 2015 22:51:11 -0800 (PST)
In-Reply-To: <20151106.063106.74659839.sthaug@nethelp.no>
References: <CAKD1Yr3Vsn7Ny_xSCr_=sVCHyU+=ZrRh2iQDUPx-5FWdHajv2w@mail.gmail.com> <D2614A6A.CA099%Lee.Howard@twcable.com> <Pine.LNX.4.64.1511050424410.1055@moonbase.nullrouteit.net> <20151106.063106.74659839.sthaug@nethelp.no>
Date: Fri, 06 Nov 2015 17:51:11 +1100
Message-ID: <CAO42Z2x3O8A1XKqN3PTcvM=xpF8W_WNSL1rVhHQ4ZY5HbVG=OQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
To: sthaug@nethelp.no
Content-Type: multipart/alternative; boundary="001a114333d63e47300523d9ab23"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/_9sRFPmBX-CHWlw7JvpBAOoiNp0>
Cc: v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?
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: Fri, 06 Nov 2015 06:51:14 -0000

On 6 Nov 2015 4:31 PM, <sthaug@nethelp.no> wrote:
>
> > That makes it sound like IETF is not "endorsing" NPT66, as opposed to
> > actively recommending that people don't use it. I'm with Lorenzo here -
> > I would prefer very strong language in the form of "deployment of NPT66
is
> > concidered harmful" or "we strongly recommend against the use of NPT66".
>
> Okay, one more operator then. I want to have NPT66 (and ULA) available
> in the toolbox.
>

Why would a recommendation against it prevent you using it on your network
if you wanted to? How is the IETF recommending against it stopping you from
using it?

A recommendation not to do something is for people who fundamentally don't
know better.

If you know better, meaning you understand the costs and consequences, and
the owners of the network are willing to pay those costs and deal with the
consequences, then there is nothing stopping you. Nobody is and can force
you to follow the recommendation in your own network.

(Having directly and indirectly paid those costs and having dealt with the
consequences of NAT in IPv4, I don't want to pay them in IPv6, and I don't
think those who don't know better should inadvertently have to end up
paying them either. I personally see the lack of reason for NAT, due to
plenty of addresses, and mechanisms to help smoothly renumber, to be the
most important properly if IPv6.)

Regards,
Mark.

> Steinar Haug, AS 2116
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops