Re: multihoming, was IPv10

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 31 December 2016 00:25 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A561F12945E for <ietf@ietfa.amsl.com>; Fri, 30 Dec 2016 16:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OifXKWBeMCM2 for <ietf@ietfa.amsl.com>; Fri, 30 Dec 2016 16:25:28 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (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 2592B129472 for <ietf@ietf.org>; Fri, 30 Dec 2016 16:25:28 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id i5so117193747pgh.2 for <ietf@ietf.org>; Fri, 30 Dec 2016 16:25:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=+G5dLCnfiP7J7ZtXhEHXXr2gbcpl4K8xqa4yXqmhlng=; b=QFNhY260x8MYmF1yBKA/2DyaKxcEGexPBP5CT6pPb4J/09u0vhs2ZZoPS/X0zOk6eX 0RJKvzpdl8vQ/zbGTeCq++O0hNzIst7Ax7ACgTXMtfR4CitijMEn8ixTgGkq2P7g/TdN sSwbKxD0acnxjrufDignPkZb+FOL5H/gGDljvRA4D2K/pckpAzrFsLxI6yV19yVL7s6P 5o1pX2VvZk2xxhzsdZvXKWuMqE/saBESqmZ39De3jbKjVBmDTmf1JqjNvgtku3HYjmOo pMKy/5vNM7Ons/VxHncIBuoKmRB6JwnnwI/r9Sat71YFs8SDZqc4It1U7WyYV3T5n4q9 rmkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=+G5dLCnfiP7J7ZtXhEHXXr2gbcpl4K8xqa4yXqmhlng=; b=oGy3o30aBHu8xhigdx0CNV7ranjHkkqG8rIPCCQRtrXup9qUb2anbV+9umJ88v4hWj tXElIpE5RJrzu3qFYy5lhRDO8IF2gL5dlWhPH4wZntmlqu5I0i43rGlUiqJT0Hwd7R8Q NTKINW92b53q7lJYmJrXs7+fF37Y8iWTYLyxpb2Eg3K37922Dkwb6Dbu3zOcaJPRWg0m ahnxoP9ABDJ1uav4XmHKfXeJdkEHuZukCCK3NV861SPWY0eG/B9U57aKyKCi4ZOhvrgw sTWe4XkYNLXHDmQvMxPtY+a+pDFN17ycgyo3Jiz4jK4WmazvtNcR7JLyP+J8p8PgYIUO wbWg==
X-Gm-Message-State: AIkVDXKwiVYHzgDg518ig2ppP5MpP/olQSEh+T4pG0kL0TXXS/rRn1xxCfz+gfBtr1aGVQ==
X-Received: by 10.84.138.165 with SMTP id 34mr103537223plp.20.1483143927532; Fri, 30 Dec 2016 16:25:27 -0800 (PST)
Received: from ?IPv6:2406:e007:62f9:1:28cc:dc4c:9703:6781? ([2406:e007:62f9:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m12sm66883887pfg.92.2016.12.30.16.25.22 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Dec 2016 16:25:26 -0800 (PST)
Subject: Re: multihoming, was IPv10
To: IETF discussion list <ietf@ietf.org>
References: <20161230024719.36002.qmail@ary.lan> <7401a840-590e-28c3-2c3f-1e4b46c34e29@gmail.com> <F04ED1585899D842B482E7ADCA581B845946D258@newserver.arneill-py.local> <685eee97-795a-6705-52a5-19707d529975@necom830.hpcl.titech.ac.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <03dd408a-3294-cda9-47ad-a2eb8139b7bb@gmail.com>
Date: Sat, 31 Dec 2016 13:25:31 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <685eee97-795a-6705-52a5-19707d529975@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MTz0bGl8F9xaZhLgz8I7jrr3CDg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Dec 2016 00:25:29 -0000

On 31/12/2016 11:20, Masataka Ohta wrote:
> Michel Py wrote:
> 
>>> Brian E Carpenter wrote :
>>> Which is exactly why we have to make multi-prefix multihoming work out of the box. Which is why we
>>> have RFC 7157 and RFC 8028 and draft-ietf-rtgwg-dst-src-routing, and we're not done yet.
>>
>> We have missed the delivery date by 14 years.
> 
> I wrote:
> 
> 	https://tools.ietf.org/html/draft-ohta-e2e-multihoming-00
> 
> in April 2000 and I know it is stupid to use source routing for
> multihoming. So, never deliver it.
> 
> All we need is transport/application layer capability to treat
> multiple source and destination addresses and implementations
> of such TCP has been available since 2003 or so, more than 14
> years ago.

I am very suspicious of any claim about "all we need" in this area, but
I have written about this in some detail elsewhere:
http://www.sigcomm.org/node/3484

   Brian