Re: [Hipsec] Status of WG items
Julien Laganier <julien.ietf@gmail.com> Thu, 13 September 2012 15:41 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 9E91521F860B for <hipsec@ietfa.amsl.com>; Thu, 13 Sep 2012 08:41:48 -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 KPlPsDE1qrSH for <hipsec@ietfa.amsl.com>; Thu, 13 Sep 2012 08:41:47 -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 9DCC221F8607 for <hipsec@ietf.org>; Thu, 13 Sep 2012 08:41:47 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so4138938pbb.31 for <hipsec@ietf.org>; Thu, 13 Sep 2012 08:41:47 -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=Mx1DYAqpgKQlnOK4eKgM51+I4oEGs7SPY2NRk/57JDQ=; b=o09i3MEdvMuo06O+bhTTBqRa76yHC9aCbpY66ONHfJsjN9ph5MxPRw66BlfBeQ9CUZ 6VL8CJKnH4XmRduQF73MBDN8lA0JaLVnoAbhoKmbmbwF7u6Zd2cRUqFu/vgEqKdX931I OSJH3X+WoxA6+1w1EVURiwpXo5YL3paPtQqNrb47nL3ecFy/tVjoAzni12QbKFCbKpSE zLfn257FyfwLiJOB7Xk1pdCNSySwbPGBRktvxG+/vojbZwgggGyUQPy+SSeTgY/6jM/U a0Eyouhte2pPhdRE1u6ZehA8njD9PircaexGTCTAzpfgMotjYgSFpDnjy3H0XpnOB4IO fe3g==
MIME-Version: 1.0
Received: by 10.68.195.34 with SMTP id ib2mr5112743pbc.164.1347550907315; Thu, 13 Sep 2012 08:41:47 -0700 (PDT)
Received: by 10.68.12.130 with HTTP; Thu, 13 Sep 2012 08:41:46 -0700 (PDT)
In-Reply-To: <5012C05B.6080203@nomadiclab.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> <5012C05B.6080203@nomadiclab.com>
Date: Thu, 13 Sep 2012 08:41:46 -0700
Message-ID: <CAE_dhjvX1x8=9min3y16Dz5o1j2mc6gzK4xy+N2+B=x+HA8PYw@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: Ari Keranen <ari.keranen@nomadiclab.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: hipsec@ietf.org
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: Thu, 13 Sep 2012 15:41:48 -0000
Hi Ari, On Fri, Jul 27, 2012 at 9:22 AM, Ari Keranen <ari.keranen@nomadiclab.com> wrote: > > On 7/6/12 3:37 AM, Julien Laganier wrote: >> >> - 5203bis (registration) can IMHO be republished as is as I haven't >> seen any issue with the original version. If people agree I could >> republish it and we could WGLC it... > > > I posted some comments about 5203bis earlier this year but back then there > was no discussion regarding them. So, here goes again. > > Some of these have been discussed also earlier on this list (these relate to > requirements discovered with the native NAT traversal draft [1]), but I'll > have them all here for easier reference. > > Currently, the registrar has no way of indicating that it would otherwise > accept the registration, but it's currently running low on resources. For > this purpose, a failure type "Insufficient resources" could be added to the > "registration failure types". > > Registration using authentication with certificates could be part of the > registration RFC. Currently, only authentication with HI is defined, but > knowing all HIs beforehand is not practical in many cases. > > Text in section 3.2. of [1] could be used as a basis for this (just replace > "HIP' data relay" with "registrar"). Also, if this authentication mode is > added to the draft, failure type "Invalid certificate" should be added for > the failure case. > > [1] http://tools.ietf.org/html/draft-ietf-hip-native-nat-traversal > > Should we have these in the registration draft? These suggestions sound reasonable to me. --julien
- [Hipsec] Status of WG items Gonzalo Camarillo
- Re: [Hipsec] Status of WG items Henderson, Thomas R
- Re: [Hipsec] Status of WG items Tobias Heer
- Re: [Hipsec] Status of WG items Gonzalo Camarillo
- Re: [Hipsec] Status of WG items Julien Laganier
- Re: [Hipsec] Status of WG items Henderson, Thomas R
- Re: [Hipsec] Status of WG items Ari Keranen
- Re: [Hipsec] Status of WG items Robert Moskowitz
- Re: [Hipsec] Status of WG items Ari Keranen
- Re: [Hipsec] Status of WG items Gonzalo Camarillo
- Re: [Hipsec] Status of WG items Julien Laganier
- Re: [Hipsec] Status of WG items Ari Keranen
- Re: [Hipsec] Status of WG items Julien Laganier
- Re: [Hipsec] Status of WG items Gonzalo Camarillo
- Re: [Hipsec] Status of WG items Julien Laganier
- Re: [Hipsec] Status of WG items Henderson, Thomas R
- Re: [Hipsec] Status of WG items Miika Komu
- [Hipsec] Fwd: Status of WG items Julien Laganier
- Re: [Hipsec] Fwd: Status of WG items Gonzalo Camarillo
- Re: [Hipsec] Fwd: Status of WG items Miika Komu
- Re: [Hipsec] Status of WG items Ari Keranen
- Re: [Hipsec] Fwd: Status of WG items Ari Keranen
- Re: [Hipsec] Fwd: Status of WG items Henderson, Thomas R
- Re: [Hipsec] Fwd: Status of WG items Miika Komu
- Re: [Hipsec] Fwd: Status of WG items Samu Varjonen
- Re: [Hipsec] Fwd: Status of WG items Ari Keranen