Re: [Hipsec] Certs draft: experimental or PS

Tobias Heer <heer@cs.rwth-aachen.de> Tue, 18 January 2011 11:19 UTC

Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 602E43A6FC0 for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 03:19:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShQTj5SRVQon for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 03:19:53 -0800 (PST)
Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by core3.amsl.com (Postfix) with ESMTP id 5B1CF3A6F78 for <hipsec@ietf.org>; Tue, 18 Jan 2011 03:19:53 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; charset="us-ascii"
Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0LF700KA5U9HWNG0@mta-1.ms.rz.RWTH-Aachen.de> for hipsec@ietf.org; Tue, 18 Jan 2011 12:22:29 +0100 (CET)
X-IronPort-AV: E=Sophos;i="4.60,338,1291590000"; d="scan'208";a="89128155"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Tue, 18 Jan 2011 12:22:25 +0100
Received: from umic-i4-137-226-45-197.nn.rwth-aachen.de ([unknown] [137.226.45.197]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0LF7000S2U9DHR80@relay-auth-1.ms.rz.rwth-aachen.de> for hipsec@ietf.org; Tue, 18 Jan 2011 12:22:25 +0100 (CET)
From: Tobias Heer <heer@cs.rwth-aachen.de>
In-reply-to: <F4B69051-1157-403D-93BB-F09EA557C408@nomadiclab.com>
Date: Tue, 18 Jan 2011 12:22:25 +0100
Message-id: <B472C1B3-4B7E-4088-AFAD-D5AFF3F6A0E0@cs.rwth-aachen.de>
References: <4D3449E3.50904@ericsson.com> <1486BB76-57BF-49A9-85A0-8136C6EC255F@cs.rwth-aachen.de> <4D355F0B.8080305@ericsson.com> <F4B69051-1157-403D-93BB-F09EA557C408@nomadiclab.com>
To: HIP <hipsec@ietf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Hipsec] Certs draft: experimental or PS
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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, 18 Jan 2011 11:19:54 -0000

Hello, 

Am 18.01.2011 um 11:21 schrieb Ari Keranen:

> Hi,
> 
> I'd go for publishing experimental CERT now and bis'ed PS version later with the rest of the PS HIP stuff.
> 
I second that. I think it makes sense to publish the RFC as experimental first.

The draft is a companion document for 5201 (not bis).
I think it should be published as experimental right now. However, I think we might consider a non-experimental version in the future (when 5201-bis is done).

Tobias

> 
> Cheers,
> Ari
> 
> On Jan 18, 2011, at 11:36 AM, Gonzalo Camarillo wrote:
>> Hi Tobias,
>> 
>> yes, those are exactly the points that need to be considered. A straight
>> forward approach would be to publish this draft as experimental and then
>> create a bis draft, this time as a PS, which would reference 5201bis.
>> 
>> Another possibility is not to publish the experimental draft at all. We
>> could update the current draft so that it references 5201bis and publish
>> it together with 5201bis.
>> 
>> Cheers,
>> 
>> Gonzalo
>> 
>> 
>> On 18/01/2011 11:13 AM, Tobias Heer wrote:
>>> Hello Gonzalo,
>>> 
>>> Am 17.01.2011 um 14:53 schrieb Gonzalo Camarillo:
>>> 
>>>> Hi,
>>>> 
>>>> in our last charter update, we decided to move the certs draft to the
>>>> standards track:
>>>> 
>>>> o Specify in a standards track RFC how to carry certificates in the
>>>> base exchange. This was removed from the base HIP spec so that the
>>>> mechanism is specified in a stand-alone spec.
>>>> 
>>>> However, I would like to double-check with the group. If we intend to
>>>> specify all this in 5201 bis anyway, it may make sense to publish this
>>>> as an Experimental RFC. If we want 5201bis to reference this spec, then
>>>> it needs to be PS. I would like to get your opinions on this issue?
>>>> 
>>> 
>>> I would be interested what the implications of PS or experimetal are for the publication of the draft.
>>> 
>>> Can we publish the draft as PS with downreferences to RFC5201 now (in absence of a 5201-bis) or would we have to wait until 5201-bis is approved?
>>> 
>>> If we go experimental, can we bis the cert draft later and go for PS instead?
>>> 
>>> One reason why I would not like to have the certs in 5201-bis is because it is a separate issue/problem/solution and does not really belong to the _base_ documents but rather extends it. As extension it covers a well defined problem space and can stand on its own.
>>> 
>>> Tobias
>>> 
>>> 
>>>> Thanks,
>>>> 
>>>> Gonzalo
>>>>