Re: [Hipsec] HIP multihoming status

Tom Henderson <tomhend@u.washington.edu> Fri, 08 April 2016 06:04 UTC

Return-Path: <tomhend@u.washington.edu>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2A312D0AE for <hipsec@ietfa.amsl.com>; Thu, 7 Apr 2016 23:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 GKPGmKf9LXZI for <hipsec@ietfa.amsl.com>; Thu, 7 Apr 2016 23:04:03 -0700 (PDT)
Received: from mxout23.cac.washington.edu (mxout23.cac.washington.edu [140.142.32.140]) (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 BAC6A12D095 for <hipsec@ietf.org>; Thu, 7 Apr 2016 23:04:03 -0700 (PDT)
Received: from hymn04.u.washington.edu (hymn04.u.washington.edu [140.142.8.72]) by mxout23.cac.washington.edu (8.14.4+UW14.03/8.14.4+UW16.03) with ESMTP id u3862wKX006623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Apr 2016 23:02:58 -0700
Received: from hymn04.u.washington.edu (localhost [127.0.0.1]) by hymn04.u.washington.edu (8.14.4+UW14.03/8.14.4+UW16.03) with ESMTP id u3862taC003522; Thu, 7 Apr 2016 23:02:55 -0700
Received: from localhost (Unknown UID 10745@localhost) by hymn04.u.washington.edu (8.14.4+UW14.03/8.14.4+Submit-local) with ESMTP id u3862t1N003519; Thu, 7 Apr 2016 23:02:55 -0700
X-Auth-Received: from [73.239.169.224] by hymn04.u.washington.edu via HTTP; Thu, 07 Apr 2016 23:02:54 PDT
Date: Thu, 7 Apr 2016 23:02:54 -0700 (PDT)
From: Tom Henderson <tomhend@u.washington.edu>
To: hipsec@ietf.org
Message-ID: <alpine.LRH.2.01.1604072302540.916@hymn04.u.washington.edu>
User-Agent: Web Alpine 2.01 (LRH 1302 2010-07-20)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.4.8.55116
X-PMX-Server: mxout23.cac.washington.edu
X-Uwash-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FRAUD_INTRO 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_URI_TEXT 0, __PHISH_SPEAR_GREETING 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_IN_BODY 0, __URI_NO_MAILTO 0, __URI_NO_WWW 0, __URI_NS , __URI_WITH_PATH 0, __USER_AGENT 0'
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/D2STVUBI6VsDobzX3xZSCTEM504>
Subject: Re: [Hipsec] HIP multihoming status
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Apr 2016 06:04:05 -0000

Below I am replying inline to my message from November regarding the HIP
multihoming issues, and how they are addressed in newly published draft
version -08.

On 11/22/2015 11:01 PM, Tom Henderson wrote:
> 
> 
> On 11/17/2015 11:52 PM, Gonzalo Camarillo wrote:
>> Authors of the following drafts,
>> 
>> could you please let the WG know their status and what needs to
>> happen next for each of them in order to be able to WGLC them at
>> some point in the future?
>> 
>> https://datatracker.ietf.org/doc/draft-ietf-hip-multihoming/ 
>> http://datatracker.ietf.org/doc/draft-ietf-hip-rfc5206-bis/
> 
> Recall that we split multihoming from mobility for this version of
> the HIP specifications.  The HIP multihoming draft has received less
> attention than the mobility draft over the years.
> 
> The open tracker issues are listed here: 
> https://trac.tools.ietf.org/wg/hip/trac/query?component=multihoming
> 
> The first one (#3) is one that somewhat prompted the draft split.
> RFC5206 advocates creating full mesh of SAs for multihoming use
> cases. That has led to a lot of overhead/complexity, so this tracker
> item is a reminder to revisit that issue.

There were several complaints that the recommendations for multihoming in RFC5206 led to the formation of too many SAs. For instance, the scenario of two hosts with two addresses each recommended that four pairs of SAs (a full mesh) be set up between the address combinations.

In this revision, the two use cases of fault tolerance and load balancing are distinguished. For the fault tolerance scenario, it is no longer recommended that hosts set up SAs in parallel, but that they keep the addresses in reserve in case an address failure is detected. For the load balancing scenario, it is recommended to create different SA pairs for different paths to be used for load balancing, but stops short of recommending a full mesh of SAs.

> 
> Issue #5 suggests to add support for cross-(address)-family
> handovers, as outlined in a paper several years ago.

I reviewed the paper by Samu, Miika, and Andrei, and included their recommendations to allow the LOCATOR_SET in the R2 packet, and to allow hosts to avoid setting the preferred bit if they choose to do so. Related to address families, I removed draft text about supporting associations and SAs that cross address family realms (e.g. one host has IPv4 address, one has IPv6 addres), since there is no description for how that would work in practice.
> 
> Issue #7 raises the issue of incorporating support for load-balancing
> across multihomed scenarios.

See above; load balancing is explicitly listed as a scenario in the new draft.

> 
> Issue #11 points out that the draft should better clarify the
> relationships between SPIs, interfaces, and locators when multihoming
> is available.

This is related to issue #3 and hopefully has been improved in the rewrite.

> 
> Issue #16 suggests to add support for sending UPDATEs in parallel, to
> lower latency in finding working locator pairs.  Perhaps what should
> be done initially is to review whether there is any specification on
> the receiving side that would preclude such operation in the future.

I did not include this (previously called the 'shotgun' approach) and suggest that we leave it for further study.

> 
> Issue #17 suggests to review two drafts on fault tolerance that may
> contribute to the multihoming specification.  I haven't looked at
> these for several years so I am not sure what specific changes might
> be needed now.

I read these drafts again. I included fault tolerance as a use case supported by the new draft. I did not try to include failure detection protocols such as REAP or the other proposed protocol, and suggest to leave failure detection protocols for further study.

> 
> So in summary, there still seems to be some work to do to resolve the
> above open issues.  I guess that we could perhaps reduce the work by
> avoiding scope increase (e.g. issues 5, 7, 16, 17) but we should
> still review the basic complexity issue that prompted this split and
> led to issues 3 and 11.  Are there any other opinions or
> recommendations about proceeding with the multihoming open issues?

I believe that if this draft passes review by the WG, we could close the open issues as either resolved or wontfix based on the above discussion.

- Tom