Re: [v6ops] discussion of transition technologies

Fred Baker <> Mon, 22 January 2018 17:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0E92E126E64 for <>; Mon, 22 Jan 2018 09:29:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id VZ_kAxEBEQ3t for <>; Mon, 22 Jan 2018 09:29:50 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 31895126CE8 for <>; Mon, 22 Jan 2018 09:29:50 -0800 (PST)
Received: by with SMTP id m20so7595528pgc.11 for <>; Mon, 22 Jan 2018 09:29:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UYBnzPbLYxhoW8SKYPkNf1gQzd4kmTz2vwd9wMH2ACI=; b=qJZJtA1bDgwJZepKyT9X73lGo3TzwbAQZ7pMZwb7/qkoMpxruUut+DiqY8obru2bEK 2NXW3jwbnUms9JoJdnPlWAjYqEWjUYR22ebHPcbS6DkZxqI3WDlrPX3d2pc4Mv0qgAQ1 6qo5zcTMP7YexhVmRoqZGlFdH5fAEMur2LHKVgPgxaHyTdxP04ckGYuUC0vyueksgIW0 z7naHLe+rbZ8f3dG0EveMlx/SNWpCsxAPX+bOuq0+DvLKAhLkhnpsC/5Ij2wr1Kj4Gel O2bpKLw4HToaZx+Oadw15yzfqqWSaY/EfB2V4Xai7fhPiD1aVD/3AhkXekqie8Q+fAXP SiaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UYBnzPbLYxhoW8SKYPkNf1gQzd4kmTz2vwd9wMH2ACI=; b=s+/+4Tfb+00zoe52+8im+LW5t3Cg1Dg50rdKUx5GN9nSE1nvCM73a9CatdYOjeEveW jliodsfbeDX/s78wUGlByF9DuGMkEjCMwt5jr+Cd0gR20+wHeFRRReU8FAbiZ2yuj2C0 f1dMQB6I9160MBp+GWWo6mvPzo1+cuRamPikaUvPqOQk6CrvUGaDordd57dQcah0QAZc lmkbkFuGf/2YxOAFKZbastri8EXd7zP69J7YDminEJoFPOmcEC2Nl59+r/HY8gZu+Ijj MTYkZRPSs4NgsrPTs7N0/za6MvmolnwWXnktOfPbAWgRghOaJE2+c4b6BWD+ZhEBKkh0 RGAw==
X-Gm-Message-State: AKwxytcrMlesNvSnb55uNyOTYmgjhPem7FArVyuFZmw2HKkgVxcP9rn7 Qx0fc2uZasdy4yKZpLq41Mi1Tjvw
X-Google-Smtp-Source: AH8x227+UoOunyCUH3f9enJMwPekRGAkzq2es/Wgm1Zl0ZdYuSdEQW06VMSv9CwIzmoQwXb/OsM42w==
X-Received: by 2002:a17:902:1682:: with SMTP id h2-v6mr3876265plh.116.1516642189839; Mon, 22 Jan 2018 09:29:49 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id c83sm1434748pfk.8.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jan 2018 09:29:48 -0800 (PST)
From: Fred Baker <>
Message-Id: <>
Content-Type: multipart/signed; boundary="Apple-Mail=_10979FD8-95F9-44EB-9287-A6CDCC4E486B"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 22 Jan 2018 09:29:46 -0800
In-Reply-To: <>
Cc: Sander Steffann <>, " WG" <>
To: Tim Chown <>
References: <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <>
Subject: Re: [v6ops] discussion of transition technologies
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Jan 2018 17:29:52 -0000

On Jan 22, 2018, at 2:46 AM, Tim Chown <> wrote:
> So what translation mechanisms are you recommending "above the IP layer" ?

The one that comes quickly to mind is a load balancer that terminates one transport connection and relays data to another. It's a transport layer gateway, and so not translation in the SIIT sense of the word. It also has interesting ramifications for ICMP and so on - they don't follow the transport connection and so are invisible to it through such a gateway. The one place that seems to be a headache is with location-based or customer-based services - load balancers will often insert an http header letting the ultimate recipient know the address of its ultimate peer in the session. That, of course, has ramifications for https etc, which might be just as happy to carry the data as some form of login cookie or REST data element.