Re: [Hipsec] Certs draft: experimental or PS

Samu Varjonen <samu.varjonen@hiit.fi> Tue, 18 January 2011 11:22 UTC

Return-Path: <samu.varjonen@hiit.fi>
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 606D63A6FCA for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 03:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JWjqqgG4qLvz for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 03:22:52 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 2BE923A6F6B for <hipsec@ietf.org>; Tue, 18 Jan 2011 03:22:52 -0800 (PST)
Received: from [128.214.114.246] (wel-36.pc.hiit.fi [128.214.114.246]) by argo.otaverkko.fi (Postfix) with ESMTP id 1CB9825ED0F for <hipsec@ietf.org>; Tue, 18 Jan 2011 13:25:28 +0200 (EET)
Message-ID: <4D3578A7.8000101@hiit.fi>
Date: Tue, 18 Jan 2011 13:25:27 +0200
From: Samu Varjonen <samu.varjonen@hiit.fi>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: hipsec@ietf.org
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> <B472C1B3-4B7E-4088-AFAD-D5AFF3F6A0E0@cs.rwth-aachen.de>
In-Reply-To: <B472C1B3-4B7E-4088-AFAD-D5AFF3F6A0E0@cs.rwth-aachen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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:22:53 -0000

On 18/01/11 13:22, Tobias Heer wrote:
> 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
>

+1

BR, Samu

>>
>> 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
>>>>>
>
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec