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

Gert Doering <gert@space.net> Wed, 04 November 2015 20:17 UTC

Return-Path: <gert@Space.Net>
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 688951B3400 for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 12:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 PO5L1EK2e371 for <v6ops@ietfa.amsl.com>; Wed, 4 Nov 2015 12:17:47 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 354A91B33FD for <v6ops@ietf.org>; Wed, 4 Nov 2015 12:17:36 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B6D6762F15 for <v6ops@ietf.org>; Wed, 4 Nov 2015 21:17:34 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 7783E6099E for <v6ops@ietf.org>; Wed, 4 Nov 2015 21:17:34 +0100 (CET)
Received: (qmail 45662 invoked by uid 1007); 4 Nov 2015 21:17:34 +0100
Date: Wed, 04 Nov 2015 21:17:34 +0100
From: Gert Doering <gert@space.net>
To: Mark Smith <markzzzsmith@gmail.com>
Message-ID: <20151104201734.GZ70452@Space.Net>
References: <CAKD1Yr3Qn48eQ1Q4VovCsr_S2+RADRZKzi9qBDoh8G2w6Be+=g@mail.gmail.com> <20151104024731.0DCDE3BC3CBF@rock.dv.isc.org> <D25FB58B.C9B04%Lee.Howard@twcable.com> <20151104104208.GL70452@Space.Net> <0EE48C9B-801D-4670-8D02-248789E2F411@umn.edu> <50027DBA-C4C2-4679-8D1C-2992BE7C3B75@delong.com> <20151104170711.GV70452@Space.Net> <ADA388DF-1E4D-43E4-B2EC-7D3E1B93FCD0@delong.com> <20151104195254.GW70452@Space.Net> <CAO42Z2wq4qtUuVLMF2hLkJH268Aij8L=5uX+vkRKbbZ-reZtiw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="ReC6eBXgY35T+BYH"
Content-Disposition: inline
In-Reply-To: <CAO42Z2wq4qtUuVLMF2hLkJH268Aij8L=5uX+vkRKbbZ-reZtiw@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/CVjDArXQ55eIGk6W2EW8y-Lxs6M>
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: Wed, 04 Nov 2015 20:17:48 -0000

Hi,

On Thu, Nov 05, 2015 at 07:14:09AM +1100, Mark Smith wrote:
> > Widen your mind :-) - and indeed, I am making this case.  Multiple
> > different scenarios where NAT is making life much easier (or enabling
> > a solution at all that might not be otherwise possible).
> 
> Are people who use it "successfully" aware of the limitations it imposes
> i.e. those described in RFC2993?

Yes.  The most important limitation in these cases is "make sure your
documentation is precise".

I said before that *imposing* NAT on people is bad, but taking away
tools is also bad.  And as such, I oppose the statement that there
would be IETF consensus on "NAT is bad".

In almost all cases, alternative approaches could be used (like, in
the loadbalancing case, use a reverse proxy, add extra http headers
so the real server can know the real client IP, etc) - but in many
cases, these are more expensive or require cooperation by other parties
that have no interest.  Tool.  Useful.  By conscenting adults.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279