Re: [Hipsec] updates to HIP mobility and multihoming drafts

Robert Moskowitz <rgm@htt-consult.com> Fri, 21 October 2016 13:55 UTC

Return-Path: <rgm@htt-consult.com>
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 9061C1297BC for <hipsec@ietfa.amsl.com>; Fri, 21 Oct 2016 06:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.631
X-Spam-Level:
X-Spam-Status: No, score=-4.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.431, SPF_PASS=-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 gWkKaKkMZSQH for <hipsec@ietfa.amsl.com>; Fri, 21 Oct 2016 06:55:19 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [50.253.254.3]) (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 A24671293FE for <hipsec@ietf.org>; Fri, 21 Oct 2016 06:55:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id D2F10623C9; Fri, 21 Oct 2016 09:55:18 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id r1mc38vU6p13; Fri, 21 Oct 2016 09:55:04 -0400 (EDT)
Received: from lx120e.htt-consult.com (pool-71-246-69-74.bltmmd.east.verizon.net [71.246.69.74]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 9F859623BE; Fri, 21 Oct 2016 09:55:03 -0400 (EDT)
To: Tom Henderson <tomhend@u.washington.edu>, hipsec@ietf.org
References: <alpine.LRH.2.01.1610101722430.12372@hymn04.u.washington.edu>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <41f2cbaa-118a-4cf8-84a8-a5201e78214a@htt-consult.com>
Date: Fri, 21 Oct 2016 09:55:00 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.01.1610101722430.12372@hymn04.u.washington.edu>
Content-Type: multipart/alternative; boundary="------------F09DD74A5F5EA6B2E5ED67B0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/-gMXVZhleEhIv-QT15vpyzZOV7Q>
Subject: Re: [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: Fri, 21 Oct 2016 13:55:21 -0000

Ver 14 of HIP mobility addresses my concerns.

Tom, thank you for making the change to clarify the draft.

Bob

On 10/10/2016 08:22 PM, Tom Henderson wrote:
> 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
>
>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec