Re: [mif] next step for MIF PVD configuration

Ted Lemon <Ted.Lemon@nominum.com> Mon, 04 April 2016 02:06 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947DB12D099 for <mif@ietfa.amsl.com>; Sun, 3 Apr 2016 19:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 pUdPDcrHbqWl for <mif@ietfa.amsl.com>; Sun, 3 Apr 2016 19:06:10 -0700 (PDT)
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 8FD5512D0A7 for <mif@ietf.org>; Sun, 3 Apr 2016 19:06:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 7BB667400E7; Mon, 4 Apr 2016 02:06:10 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Sun, 3 Apr 2016 19:04:57 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Margaret Cullen <mrcullen42@gmail.com>
Thread-Topic: [mif] next step for MIF PVD configuration
Thread-Index: AQHRctr3cYtc1+T2V0K7xE+Md8M/OZ9DifuAgAMZ7gCAAYFIAIABo3AAgA1RIwCAIcdeAIAAZdHd
Date: Mon, 4 Apr 2016 02:04:56 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A438AF@mbx-03.WIN.NOMINUM.COM>
References: <COL125-W396ADD4D31445DAE7867D3B1BA0@phx.gbl> <56D44703.7050700@fer.hr> <256A8C0C-EEED-4AF4-8B59-DD8109AB1519@gmail.com> <56D82434.5020803@fer.hr> <alpine.DEB.2.02.1603041334290.31096@uplift.swm.pp.se> <B1328946-34AD-4222-813E-3B7A67B5B6CA@gmail.com>, <alpine.DEB.2.02.1604031455150.31096@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1604031455150.31096@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [31.133.146.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/lrrUsf8_nUAwTUQjzqI6mordgU0>
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] next step for MIF PVD configuration
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 04 Apr 2016 02:06:11 -0000

In the homenet naming architecture this is addressed by giving out multiple caching resolver IP addresses per link, one for each pvd.