Re: [btns] BTNS API documents

Daniel Migault <mglt.ietf@gmail.com> Wed, 25 November 2009 07:51 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: btns@core3.amsl.com
Delivered-To: btns@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADFE23A6A6D for <btns@core3.amsl.com>; Tue, 24 Nov 2009 23:51:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 VWQSDoV9kO6u for <btns@core3.amsl.com>; Tue, 24 Nov 2009 23:51:32 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 5D5AB3A63EC for <btns@ietf.org>; Tue, 24 Nov 2009 23:51:32 -0800 (PST)
Received: by fxm5 with SMTP id 5so6664087fxm.28 for <btns@ietf.org>; Tue, 24 Nov 2009 23:51:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=nbYZR4rli5+lGfvRAZksQ+2usXqYCEFwLJvjBqlAKDA=; b=wjYmFLkjdbvaQ3r8dPx7xXIcsouovv2V6OErkCPdhL772RNyKKOR1R2cG8oTUhu3wO hRbQi5szGLTRJDPTD9L3mg7g0jWqvtzAlWkRoctYUuknTrhFEg4zrAKsTiIdNd4VBVUq EeXHxspEoYd450vON+gV94f9TxaUkdQngyZ+g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=FF+LO85IYoc1esPTcTvCBQhnIkYMtG9OMUBQTfHTEN/gCmgsC8qhSP9E6+B8+o07tb sM3hfvWlWm/R19HDjW9VCkcs/gPoRhf11VNB6ZDeRAqULIJorioeWCLTSI0KwfVyG9to qY1UjubLdbRQWflZkqBXmGHxkUZ4sKqwM96+0=
MIME-Version: 1.0
Received: by 10.103.76.29 with SMTP id d29mr3250514mul.50.1259135482737; Tue, 24 Nov 2009 23:51:22 -0800 (PST)
In-Reply-To: <4B0C3C86.3040809@hiit.fi>
References: <BF345F63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualcomm.com> <4B0C17E2.6020607@isi.edu> <4B0C3C86.3040809@hiit.fi>
Date: Wed, 25 Nov 2009 08:51:22 +0100
Message-ID: <51eafbcb0911242351u678449d5sc0bcbe62cd75b483@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: miika.komu@hiit.fi
Content-Type: multipart/alternative; boundary=0016e65aeed02c340204792d53d8
Cc: "btns-ads@tools.ietf.org" <btns-ads@tools.ietf.org>, Sasu A O Tarkoma <starkoma@cc.helsinki.fi>, "btns@ietf.org" <btns@ietf.org>, "btns-chairs@tools.ietf.org" <btns-chairs@tools.ietf.org>
Subject: Re: [btns] BTNS API documents
X-BeenThere: btns@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Better-Than-Nothing-Security Working Group discussion list <btns.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/btns>
List-Post: <mailto:btns@ietf.org>
List-Help: <mailto:btns-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/btns>, <mailto:btns-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Nov 2009 07:51:33 -0000

Hi,

I also did not had time this year but I plain to contribute to it with the
editing level of commitment in 2010. Can we wait for IETF78 to decide if we
have to close or not the WG?

Daniel


On Tue, Nov 24, 2009 at 9:05 PM, Miika Komu <miika.komu@hiit.fi> wrote:

> Joe Touch wrote:
>
> Hi,
>
> we don't have much time to contribute with Sasu this year. Sorry.
>
>
>  -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I'd help with reviewing and/or editing, presuming others are driving the
>> content creation (since I'm not experienced in coding IPsec; it's not a
>> lack of cycles or commitment).
>>
>> I.e., I'll contribute whatever's needed to help finish this up, and IMO
>> the API is part of finishing.
>>
>> Joe
>>
>> Laganier, Julien wrote:
>>
>>> Folks,
>>>
>>> Is there anybody interested in helping completing the BTNS APIs
>>> documents? If you are, please also state the level of commitment you're
>>> willing to dedicate to that goal (e.g., editing, contributing,
>>> reviewing.)
>>>
>>> If there isn't enough interest it seems the logical next step for the
>>> BTNS WG is to close without publishing the API docs.
>>>
>>> --julien
>>> _______________________________________________
>>> btns mailing list
>>> btns@ietf.org
>>> https://www.ietf.org/mailman/listinfo/btns
>>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (MingW32)
>>
>> iEYEARECAAYFAksMF+IACgkQE5f5cImnZrsyCACg+c4Jd22iGsDaOZUcadeMGX/K
>> rNEAn3XQcB2q5PPGeJdp1buQ1iv/Xzri
>> =5gxJ
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> btns mailing list
>> btns@ietf.org
>> https://www.ietf.org/mailman/listinfo/btns
>>
>
> _______________________________________________
> btns mailing list
> btns@ietf.org
> https://www.ietf.org/mailman/listinfo/btns
>



-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58