Re: [Hipsec] Certs draft: experimental or PS
Ari Keranen <ari.keranen@nomadiclab.com> Tue, 18 January 2011 10:19 UTC
Return-Path: <ari.keranen@nomadiclab.com>
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 BF73A3A6FA9 for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 02:19:19 -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=[AWL=0.000, 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 CZLhMUovZV88 for <hipsec@core3.amsl.com>; Tue, 18 Jan 2011 02:19:18 -0800 (PST)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id AC0213A6FA7 for <hipsec@ietf.org>; Tue, 18 Jan 2011 02:19:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 763CA4E6D7; Tue, 18 Jan 2011 12:21:49 +0200 (EET)
X-Virus-Scanned: amavisd-new at nomadiclab.com
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQbAElgChDWH; Tue, 18 Jan 2011 12:21:48 +0200 (EET)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id DFB334E6D1; Tue, 18 Jan 2011 12:21:48 +0200 (EET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Ari Keranen <ari.keranen@nomadiclab.com>
In-Reply-To: <4D355F0B.8080305@ericsson.com>
Date: Tue, 18 Jan 2011 12:21:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4B69051-1157-403D-93BB-F09EA557C408@nomadiclab.com>
References: <4D3449E3.50904@ericsson.com> <1486BB76-57BF-49A9-85A0-8136C6EC255F@cs.rwth-aachen.de> <4D355F0B.8080305@ericsson.com>
To: HIP <hipsec@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
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 10:19:19 -0000
Hi, I'd go for publishing experimental CERT now and bis'ed PS version later with the rest of the PS HIP stuff. 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] Certs draft: experimental or PS Gonzalo Camarillo
- Re: [Hipsec] Certs draft: experimental or PS Miika Komu
- Re: [Hipsec] Certs draft: experimental or PS Tobias Heer
- Re: [Hipsec] Certs draft: experimental or PS Gonzalo Camarillo
- Re: [Hipsec] Certs draft: experimental or PS Ari Keranen
- Re: [Hipsec] Certs draft: experimental or PS Tobias Heer
- Re: [Hipsec] Certs draft: experimental or PS Samu Varjonen
- Re: [Hipsec] Certs draft: experimental or PS Henderson, Thomas R
- Re: [Hipsec] Certs draft: experimental or PS Miika Komu
- Re: [Hipsec] Certs draft: experimental or PS Gonzalo Camarillo