Re: [homenet] use of MPvD in homenet

Ted Lemon <mellon@fugue.com> Sun, 13 August 2017 02:36 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C04B13241A for <homenet@ietfa.amsl.com>; Sat, 12 Aug 2017 19:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 pFSYQ8aZn_Oi for <homenet@ietfa.amsl.com>; Sat, 12 Aug 2017 19:36:07 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 6151913240F for <homenet@ietf.org>; Sat, 12 Aug 2017 19:36:07 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id a77so36958598qkb.0 for <homenet@ietf.org>; Sat, 12 Aug 2017 19:36:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=r0lrJc6r7YmagOn1EMUhOOxJr6ISxqFNJTtdzIRs7es=; b=IHPIhORUT0xGP28pArokZzUapgS7SkapdzEmz3ZMAYnbJsc0iHBgLMgs2fCYCdDkco EOkpFVII/WbY+0fM/Qa8tlLj842XvajRNe0ZLs8WWgRicT7thrw6ABbfNYoyXogXeTkB oza3u3HXWP4iBc422vv764JWVHLMm+hWmPkMsyhPHZcwHVWNDWnKrSJsrtHv15VPPrm9 VL/WDpaIsn1dzAjdevjjRHaBOmZuowGstjs7YDfCc7eBAdKt9Ymrc0oTE/YC1P0rg+8+ B9GEUu0nJhILvrnYon2rTlXrim8vYGVDBSxKL+VTdsE1PrXtmIcOJtP7eU9hxdX7uvuy q9jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=r0lrJc6r7YmagOn1EMUhOOxJr6ISxqFNJTtdzIRs7es=; b=YRj2VkP+3+r96LF0GNKxXwiJCtoaWWZgQbr9ne0QBjbxsumTgGRVPQLCMTbHp/08bj j7nR/T39OtvtjcEJeG9KdMaYbfRMCnRcfIoIJcTvLbp8EiIkE0ulJNv2jyEbcskKf53C 0odq/BIowGOvMpVnIGXddqR8bY7HNZRzzCcowwHKEq/2B0O0fFg5s78e/qZ0y7DHU73V s07XFu6X+wy/WeKb+z6sWQMgTnPAAYHAObJV1hrEMvvkXasUYq+hCofAlCgODPXf3kV3 EkaeKGKNCfKtoWApg3fREGxwZ+iQE39PAwbhbgwLRFcp/cMhJc7b91lImGjilftEpJ90 rNvg==
X-Gm-Message-State: AHYfb5jrfxcsb3bqv8Wc8YRC+q8oIvEy+dqs+86jFS2EXXl0ZeHCkL90 U1Dv/EB3pGwmfzxRyWa1UQ==
X-Received: by 10.55.40.104 with SMTP id o101mr25830765qkh.311.1502591766375; Sat, 12 Aug 2017 19:36:06 -0700 (PDT)
Received: from cavall.ether.lede.home (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f11sm3160126qtk.7.2017.08.12.19.36.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 12 Aug 2017 19:36:05 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <7161D4C4-7E15-480B-AF4F-73A2464F991B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD779F81-593A-4D4C-86FF-AA3AA0364449"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Sat, 12 Aug 2017 22:36:04 -0400
In-Reply-To: <29406.1502582965@obiwan.sandelman.ca>
Cc: HOMENET <homenet@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <29406.1502582965@obiwan.sandelman.ca>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/QGo3DnC13f8_yOIgiiVeQ8y8Ov4>
Subject: Re: [homenet] use of MPvD in homenet
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Aug 2017 02:36:09 -0000

El 12 ag 2017, a les 20:09, Michael Richardson <mcr+ietf@sandelman.ca> va escriure:
> This seems a bit like FUD: the Internet depends upon all sorts of "brittle" things
> like "not deliberately or accidentially" setting up the routing wrong.

I get that, and it's possible that MPvD is the wrong answer here.   However, I think we need to actually analyze the problem and not just theorize about it at this level.   The reason that the MPvD work happened was that there was a need for it; it may not have been the right way to solve the problem, but I'm having trouble figuring out how LISP or Shim6 improves the situation.

The problem is simply that it needs to be the case that if a host looks up a name from one ISP's name servers, then it needs to use that ISP's prefix to contact the address that it gets from the lookup; if it uses the other ISP's name servers, then it needs to use that ISP's prefix.   Otherwise CDNs fail.

The other problems that you are talking about are also worth thinking about, but we haven't looked at them in this amount of detail.

But one thing to remember is that there's a reason why it's beneficial for hosts to implement MPvD; this is handset vendors implement it it.   It neatly wraps up real problems that real hosts have, pretty much orthogonally to whether IPv4 or IPv6 (or both) are in use.   Given that this is the case, part of the benefit of using it in the homenet is that we'd be using existing logic in hosts.

But if you really think Shim6 or LISP solve the problem better, one exercise that you might want to try is answering the question, "how does Shim6 help me with the CDN problem?   How does LISP help me with the CDN problem.   What do I have to put in a homenet router to make this work?   Which homenet router do I put it in?"   When I consider those questions, I don't know the answers to them.   I do know the answer for MPvD.   So that's why I proposed that approach.