RE: multihoming, was IPv10

Michel Py <michel@arneill-py.sacramento.ca.us> Fri, 30 December 2016 03:42 UTC

Return-Path: <michel@arneill-py.sacramento.ca.us>
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 D473A129416 for <ietf@ietfa.amsl.com>; Thu, 29 Dec 2016 19:42:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level:
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-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 WOSNZUM3M4gt for <ietf@ietfa.amsl.com>; Thu, 29 Dec 2016 19:42:18 -0800 (PST)
Received: from arneill-py.sacramento.ca.us (arneill-py.sacramento.ca.us [50.1.8.254]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B46D126BF6 for <ietf@ietf.org>; Thu, 29 Dec 2016 19:42:18 -0800 (PST)
Received: from newserver.arneill-py.local ([fe80::e9e0:5b4:170e:c286]) by newserver.arneill-py.local ([fe80::e9e0:5b4:170e:c286%11]) with mapi id 14.03.0319.002; Thu, 29 Dec 2016 19:42:15 -0800
From: Michel Py <michel@arneill-py.sacramento.ca.us>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: multihoming, was IPv10
Thread-Topic: multihoming, was IPv10
Thread-Index: AQHSYfB9dq9bmGAjZ0uqywafDBrpD6EfvEcwgACGdgD//4NjQIAAiL4AgAABcICAAAgagP//gFgw
Date: Fri, 30 Dec 2016 03:42:15 +0000
Message-ID: <F04ED1585899D842B482E7ADCA581B845946D258@newserver.arneill-py.local>
References: <20161230024719.36002.qmail@ary.lan> <7401a840-590e-28c3-2c3f-1e4b46c34e29@gmail.com>
In-Reply-To: <7401a840-590e-28c3-2c3f-1e4b46c34e29@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [96.81.169.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O-ew0-Ol-nWtkC2TpYJG-gVted4>
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: Fri, 30 Dec 2016 03:42:19 -0000

Brian,

> 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. 

Michel.