[Hipsec] updates to HIP mobility and multihoming drafts

Tom Henderson <tomhend@u.washington.edu> Tue, 11 October 2016 00:23 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 EC09E129416 for <hipsec@ietfa.amsl.com>; Mon, 10 Oct 2016 17:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.476
X-Spam-Level:
X-Spam-Status: No, score=-3.476 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 ZDZb03mUtyiB for <hipsec@ietfa.amsl.com>; Mon, 10 Oct 2016 17:23:18 -0700 (PDT)
Received: from mxout21.s.uw.edu (mxout21.s.uw.edu [140.142.32.139]) (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 5F26E129405 for <hipsec@ietf.org>; Mon, 10 Oct 2016 17:23:18 -0700 (PDT)
Received: from hymn04.u.washington.edu (hymn04.u.washington.edu [140.142.8.72]) by mxout21.s.uw.edu (8.14.4+UW14.03/8.14.4+UW16.03) with ESMTP id u9B0Mjh7021193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <hipsec@ietf.org>; Mon, 10 Oct 2016 17:22:46 -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 u9B0MhVk001504 for <hipsec@ietf.org>; Mon, 10 Oct 2016 17:22:43 -0700
Received: from localhost (Unknown UID 17623@localhost) by hymn04.u.washington.edu (8.14.4+UW14.03/8.14.4+Submit-local) with ESMTP id u9B0Mh9C001494 for <hipsec@ietf.org>; Mon, 10 Oct 2016 17:22:43 -0700
X-Auth-Received: from [73.140.18.44] by hymn04.u.washington.edu via HTTP; Mon, 10 Oct 2016 17:22:42 PDT
Date: Mon, 10 Oct 2016 17:22:43 -0700 (PDT)
From: Tom Henderson <tomhend@u.washington.edu>
To: hipsec@ietf.org
Message-ID: <alpine.LRH.2.01.1610101722430.12372@hymn04.u.washington.edu>
User-Agent: Web Alpine 2.01 (LRH 1302 2010-07-20)
MIME-Version: 1.0
Content-Type: TEXT/HTML; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.10.11.1816
X-PMX-Server: mxout21.s.uw.edu
X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_NO_HTTP 0.1, BODYTEXTH_SIZE_10000_LESS 0, BODY_SIZE_1200_1299 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, __CT 0, __CTE 0, __CTYPE_HTML 0, __HAS_FROM 0, __HAS_HTML 0, __HAS_MSGID 0, __MIME_HTML 0, __MIME_HTML_ONLY 0, __MIME_TEXT_H 0, __MIME_TEXT_H1 0, __MIME_VERSION 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __SUBJ_ALPHA_START 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __USER_AGENT 0'
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/mkXWIVV2fBUltNFneWJIkls8t7A>
Subject: [Hipsec] updates to HIP mobility and multihoming drafts
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: Tue, 11 Oct 2016 00:23:20 -0000

The new versions of the HIP mobility and multihoming drafts address various review comments received during IESG reviews.

Besides editorial changes, the following changes were made to RFC 5206-bis version 14:

*  Replace references to 'middleboxes' with more specific |'NATs and firewalls' and make reference to RFC 5207
*  Describe a simple heuristic for setting the credit value for Credit-Based Authorization based on sending rate and RTT.
*  Add subsection about privacy concerns of locator exposure to the Security Considerations section.
*  Clarify that a host must be able to receive and avoid reprocessing redundant LOCATOR_SET parameters that may have been sent in parallel to multiple addresses of the host.
*  Clarify that multicast or broadcast addresses must not be announced in a LOCATOR_SET.  

and the following to the multihoming draft version 12:

* Added section about locator privacy concerns ! to the Security Considerations section.
* Added section about relationship to split tunnel issues to the Security Considerations section.

I believe that all outstanding comments and issues have been addressed.

- Tom