[Hipsec] RFC5204-bis open issues?

Tom Henderson <tomh@tomh.org> Tue, 16 December 2014 15:32 UTC

Return-Path: <tomh@tomh.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBE51A1B66 for <hipsec@ietfa.amsl.com>; Tue, 16 Dec 2014 07:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.232
X-Spam-Level:
X-Spam-Status: No, score=0.232 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 ITVmip2k72u0 for <hipsec@ietfa.amsl.com>; Tue, 16 Dec 2014 07:31:56 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) by ietfa.amsl.com (Postfix) with SMTP id B3A4D1A1B4E for <hipsec@ietf.org>; Tue, 16 Dec 2014 07:31:56 -0800 (PST)
Received: (qmail 2062 invoked by uid 0); 16 Dec 2014 15:31:56 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy9.mail.unifiedlayer.com with SMTP; 16 Dec 2014 15:31:56 -0000
Received: from box528.bluehost.com ([74.220.219.128]) by CMOut01 with id UFXo1p00X2molgS01FXrtR; Tue, 16 Dec 2014 08:31:55 -0700
X-Authority-Analysis: v=2.1 cv=OJu0g0qB c=1 sm=1 tr=0 a=K/474su/0lCI2gKrDs9DLw==:117 a=K/474su/0lCI2gKrDs9DLw==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=ZSdzdHkL1-cA:10 a=8nJEP1OIZ-IA:10 a=HYWc1YUsAAAA:8 a=IA_2sfgTpx8A:10 a=tP-JmWiy0YsA:10 a=A92cGCtB03wA:10 a=48vgC7mUAAAA:8 a=vat5zW2C817gVElhHcoA:9 a=wPNLvfGTeEIA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tomh.org; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=Pax3ryKRg7BPKeNfEumKjECStEhzsZq8bwqxt53fzYM=; b=JgsnAQ6F9gPZCV2LPm08J3mwxIq8buRrGJSpQTIYxVKxlJAoInquda7oFN9FsSP6pkX/zT+8zWc35V5+jm+fz9B5aILFknPzMsadKics3eNb3kuHr4dZjiEUtHQk28cr;
Received: from [73.181.150.17] (port=51968 helo=[192.168.168.45]) by box528.bluehost.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <tomh@tomh.org>) id 1Y0u6F-0002Lu-N0 for hipsec@ietf.org; Tue, 16 Dec 2014 08:31:47 -0700
Message-ID: <54905061.1010200@tomh.org>
Date: Tue, 16 Dec 2014 07:31:45 -0800
From: Tom Henderson <tomh@tomh.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {3122:box528.bluehost.com:tomhorg:tomh.org} {sentby:smtp auth 73.181.150.17 authed with tomh@tomh.org}
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/RPXu4FQfhe5b0UXZGtkjsC0wNRM
Subject: [Hipsec] RFC5204-bis open issues?
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 16 Dec 2014 15:32:04 -0000

I noticed that the draft for RFC5204-bis (rendezvous extension) was 
recently refreshed, and was wondering what the remaining open issues are 
for this draft?

I know of only one, which is a longstanding question of whether we want 
to cover RVS relaying of UPDATE messages in this specification.

https://tools.ietf.org/wg/hip/trac/ticket/1

Some choices appear to be:

* do not support double jump in these specifications, leaving it for 
further study
* add specification in RFC5204-bis that refers to UPDATE relaying
* add specification in RFC5206-bis that refers to UPDATE relaying

- Tom

https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5204-bis/