Re: [Hipsec] Status of WG items

Julien Laganier <julien.ietf@gmail.com> Sat, 22 September 2012 00:34 UTC

Return-Path: <julien.ietf@gmail.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 028D621F855E for <hipsec@ietfa.amsl.com>; Fri, 21 Sep 2012 17:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJOnCpVqbn8n for <hipsec@ietfa.amsl.com>; Fri, 21 Sep 2012 17:34:57 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 89FFA21F8554 for <hipsec@ietf.org>; Fri, 21 Sep 2012 17:34:57 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so6273858pbb.31 for <hipsec@ietf.org>; Fri, 21 Sep 2012 17:34:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/d9ct8Nw1CO7kqjkkJ/lF24mFqjrwZphTHhCHNnDpCU=; b=oCDZ9fgfj/8bqUzzwsIFVyl7jWt5C5mdB8jdm6Mn9Ai1duHVzu/dnN2kkD/BSUqf2E +URQj8WfsxmB9YJNpZTwwcSgK9o8yLYCV9z4u2//XGH1a+5ilt/XJxEc2Ri9lfi2hkfb /pVXY6tjRNcjWS5bcJgn5b73a7sqzaNLsDgqFXGYb4Gkq+c0XLXk/0wxn6VyIcT4yOFe KHaE9Ci/7P+narr3aa/ByU8NY4WESm93CdHWQSFqddnGGXC3hK1PoJludjfC80MhTXs5 g6bUQ60c5hizqjEJV8Plk4AUyzo+RNFBpCdmJmYt7+++y8BMOteowFmvSOq1RUazjxtP mSPA==
MIME-Version: 1.0
Received: by 10.68.192.7 with SMTP id hc7mr19744544pbc.6.1348274097143; Fri, 21 Sep 2012 17:34:57 -0700 (PDT)
Received: by 10.68.12.130 with HTTP; Fri, 21 Sep 2012 17:34:57 -0700 (PDT)
In-Reply-To: <CAE_dhjveQ6WVVE3BVKk2txfBxNhfWvjbz+QVU2P919dNZ1WO4A@mail.gmail.com>
References: <4FE96F9F.3090800@ericsson.com> <758141CC3D829043A8C3164DD3D593EA1BD324E110@XCH-NW-16V.nw.nos.boeing.com> <4FEA1876.900@cs.rwth-aachen.de> <CAE_dhjveQ6WVVE3BVKk2txfBxNhfWvjbz+QVU2P919dNZ1WO4A@mail.gmail.com>
Date: Fri, 21 Sep 2012 17:34:57 -0700
Message-ID: <CAE_dhjtJ_c6OWA9iFXOkpqej2BPuURUumroCTh5xgb3=8+UFQQ@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: hipsec@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [Hipsec] Status of WG items
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Sep 2012 00:34:58 -0000

Folks,

I've been thinking a bit more about the update of RFC5204 / Rendezvous
Server support. See below:

On Thu, Jul 5, 2012 at 5:37 PM, Julien Laganier <julien.ietf@gmail.com> wrote:
> [...]
> - 5204bis (rendezvous) needs one more subsection regarding relaying of
> the UPDATE packet to support double jump of mobile nodes. As this
> isn't really useful without the mobility support my proposal is to
> tackle this one together with the 5206bis.

I figured two things:

1- relaying an UPDATE packet is pointless in the absence of HIP
mobility support on both endpoints.

2- support for rendezvous server is useful independently of support
for HIP mobility.

Taking both 1. and 2. into account, my conclusion is that it makes
sense to keep the rendezvous server support self-contained in 5203bis,
i.e., without a normative dependency to the mobility support in
5206bis, while 5206 would specify an extension to rendezvous mechanism
for support of relaying UPDATE packets.

Makes sense?

--julien