Re: [mif] Adrian Farrel's No Objection on draft-ietf-mif-mpvd-arch-10: (with COMMENT)

Ted Lemon <Ted.Lemon@nominum.com> Thu, 19 February 2015 16:25 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FD21A916C; Thu, 19 Feb 2015 08:25:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Az_-T5t8ll_q; Thu, 19 Feb 2015 08:25:39 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 CF5C21A9250; Thu, 19 Feb 2015 08:25:15 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 89315DA01D2; Thu, 19 Feb 2015 16:25:15 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4ED9753E07C; Thu, 19 Feb 2015 08:25:15 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 19 Feb 2015 08:25:15 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <20150219141936.5149.23302.idtracker@ietfa.amsl.com>
Date: Thu, 19 Feb 2015 11:24:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <ED603C15-7700-462C-8BDC-8FE6D026F351@nominum.com>
References: <20150219141936.5149.23302.idtracker@ietfa.amsl.com>
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/mTwvzRspbAk0fTsiSH9Mz1Dux_Y>
Cc: draft-ietf-mif-mpvd-arch.all@ietf.org, denghui02@hotmail.com, mif@ietf.org, The IESG <iesg@ietf.org>, mif-chairs@ietf.org
Subject: Re: [mif] Adrian Farrel's No Objection on draft-ietf-mif-mpvd-arch-10: (with COMMENT)
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif/>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 16:25:41 -0000

Just a high-level response to one of the points you raised: this document is indeed talking about hosts, generally, not nodes, although it's possible that a router could be connected to an upstream network, for instance, that advertises more than one provisioning domain, and the architecture intends to be able to reflect that to nodes on the downstream end.

This document certainly isn't taking any positions on the operation of ASBRs.

However, it is expected that Homenet will write a document that talks about how to provide MPVD info to hosts in a dual-homed home network or a single-homed network with an ISP that provides multiple provisioning domains.   The point of this is that a node connected to a single link on a homenet that is dual-homed ought in principle to be able to behave the same as if that node were connected to a single-homed homenet and also to the other upstream provider (e.g., a mobile data service), or if it were connected to the single upstream link with multiple provisioning domains.

For instance, one of the upstream networks may provide services not accessible through the other upstream network.   A classic example of this would be a VPN, but this could also be something like a VoIP service that is offered by one ISP, where the equivalent service is not available through the other, or when accessed through the other does not provide the same QoS guarantees.