From julienl@qualcomm.com  Tue Nov 24 09:08:44 2009
Return-Path: <julienl@qualcomm.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 E5B4A3A6847 for <btns@core3.amsl.com>; Tue, 24 Nov 2009 09:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.27
X-Spam-Level: 
X-Spam-Status: No, score=-105.27 tagged_above=-999 required=5 tests=[AWL=1.329, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 l6MGA9C8Q1iC for <btns@core3.amsl.com>; Tue, 24 Nov 2009 09:08:44 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id E07AB3A67A2 for <btns@ietf.org>; Tue, 24 Nov 2009 09:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl@qualcomm.com; q=dns/txt; s=qcdkim; t=1259082519; x=1290618519; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:content-transfer-encoding:mime-version: x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl@qualcomm.com> |To:=20"btns@ietf.org"=20<btns@ietf.org>|CC:=20"btns-chai rs@tools.ietf.org"=20<btns-chairs@tools.ietf.org>,=0D=0A =20=20=20=20=20=20=20=20"btns-ads@tools.ietf.org"=20<btns -ads@tools.ietf.org>|Date:=20Tue,=2024=20Nov=202009=2009: 08:35=20-0800|Subject:=20BTNS=20API=20documents |Thread-Topic:=20BTNS=20API=20documents|Thread-Index:=20A cptKMHo/KLngSa2RKKmMsDrtB6ckQ=3D=3D|Message-ID:=20<BF345F 63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualc omm.com>|Accept-Language:=20en-US|Content-Language:=20en- US|X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 400,1158,5812"=3B=20a=3D"28337225"; bh=dITIYwc/0sDcviLLnbfUc/RUeKDoAUpjqKz+zAQNv7g=; b=E/aXR0x78/40qLqFw8ExHi31FIJkFStm2u2y1O19ofC7CqBS14Hf/GIp l2hk6+pAjbKbAvhzRzVdlZMrvEaje1wy4wTyHKGy1DzB/IZ24xi09Mzf+ 4tL7WLLduCuqUQgjqmQXkTqOT8M+KOUJ1yBpFNg3+++guFK7P8WOTKKlM o=;
X-IronPort-AV: E=McAfee;i="5400,1158,5812"; a="28337225"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP; 24 Nov 2009 09:08:39 -0800
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id nAOH8cuq013296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 24 Nov 2009 09:08:39 -0800
Received: from nasanexhub06.na.qualcomm.com (nasanexhub06.na.qualcomm.com [129.46.134.254]) by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id nAOH8XKn006303 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 24 Nov 2009 09:08:38 -0800
Received: from nalasexhub02.na.qualcomm.com (10.47.130.89) by nasanexhub06.na.qualcomm.com (129.46.134.254) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 24 Nov 2009 09:08:37 -0800
Received: from NALASEXMB04.na.qualcomm.com ([10.47.7.118]) by nalasexhub02.na.qualcomm.com ([10.47.130.89]) with mapi; Tue, 24 Nov 2009 09:08:36 -0800
From: "Laganier, Julien" <julienl@qualcomm.com>
To: "btns@ietf.org" <btns@ietf.org>
Date: Tue, 24 Nov 2009 09:08:35 -0800
Thread-Topic: BTNS API documents
Thread-Index: AcptKMHo/KLngSa2RKKmMsDrtB6ckQ==
Message-ID: <BF345F63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "btns-ads@tools.ietf.org" <btns-ads@tools.ietf.org>, "btns-chairs@tools.ietf.org" <btns-chairs@tools.ietf.org>
Subject: [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: Tue, 24 Nov 2009 17:08:45 -0000

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 ded=
icate 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

From touch@ISI.EDU  Tue Nov 24 09:29:35 2009
Return-Path: <touch@ISI.EDU>
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 175813A68DA for <btns@core3.amsl.com>; Tue, 24 Nov 2009 09:29:35 -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 EGJ8DNVVIVxK for <btns@core3.amsl.com>; Tue, 24 Nov 2009 09:29:34 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 5E9893A6870 for <btns@ietf.org>; Tue, 24 Nov 2009 09:29:34 -0800 (PST)
Received: from [75.212.132.192] (192.sub-75-212-132.myvzw.com [75.212.132.192]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id nAOHT62c021185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 24 Nov 2009 09:29:09 -0800 (PST)
Message-ID: <4B0C17E2.6020607@isi.edu>
Date: Tue, 24 Nov 2009 09:29:06 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Laganier, Julien" <julienl@qualcomm.com>
References: <BF345F63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualcomm.com>
In-Reply-To: <BF345F63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualcomm.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "btns-ads@tools.ietf.org" <btns-ads@tools.ietf.org>, "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: Tue, 24 Nov 2009 17:29:35 -0000

-----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-----

From miika.komu@hiit.fi  Tue Nov 24 12:05:33 2009
Return-Path: <miika.komu@hiit.fi>
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 7A2CA28C116 for <btns@core3.amsl.com>; Tue, 24 Nov 2009 12:05:33 -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 BJaCRr+XhIuM for <btns@core3.amsl.com>; Tue, 24 Nov 2009 12:05:32 -0800 (PST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id 7FE8D3A691C for <btns@ietf.org>; Tue, 24 Nov 2009 12:05:32 -0800 (PST)
Received: from ip104.infrahip.net (cs27096138.pp.htv.fi [89.27.96.138]) by argo.otaverkko.fi (Postfix) with ESMTP id 2704325ED06; Tue, 24 Nov 2009 22:05:27 +0200 (EET)
Message-ID: <4B0C3C86.3040809@hiit.fi>
Date: Tue, 24 Nov 2009 21:05:26 +0100
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
References: <BF345F63074F8040B58C00A186FCA57F1C65FB294B@NALASEXMB04.na.qualcomm.com> <4B0C17E2.6020607@isi.edu>
In-Reply-To: <4B0C17E2.6020607@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "btns-ads@tools.ietf.org" <btns-ads@tools.ietf.org>, "btns@ietf.org" <btns@ietf.org>, "btns-chairs@tools.ietf.org" <btns-chairs@tools.ietf.org>, Sasu A O Tarkoma <starkoma@cc.helsinki.fi>
Subject: Re: [btns] BTNS API documents
X-BeenThere: btns@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: miika.komu@hiit.fi
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: Tue, 24 Nov 2009 20:05:33 -0000

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


From mglt.ietf@gmail.com  Tue Nov 24 23:51:33 2009
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

--0016e65aeed02c340204792d53d8
Content-Type: text/plain; charset=ISO-8859-1

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

--0016e65aeed02c340204792d53d8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I also did not had time this year but I plain to contribute to i=
t with the editing level of commitment in 2010. Can we wait for IETF78 to d=
ecide if we have to close or not the WG?<br><br>Daniel <br><br><br><div cla=
ss=3D"gmail_quote">
On Tue, Nov 24, 2009 at 9:05 PM, Miika Komu <span dir=3D"ltr">&lt;<a href=
=3D"mailto:miika.komu@hiit.fi">miika.komu@hiit.fi</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Joe Touch wrote:<br>
<br>
Hi,<br>
<br>
we don&#39;t have much time to contribute with Sasu this year. Sorry.<div><=
div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
I&#39;d help with reviewing and/or editing, presuming others are driving th=
e<br>
content creation (since I&#39;m not experienced in coding IPsec; it&#39;s n=
ot a<br>
lack of cycles or commitment).<br>
<br>
I.e., I&#39;ll contribute whatever&#39;s needed to help finish this up, and=
 IMO<br>
the API is part of finishing.<br>
<br>
Joe<br>
<br>
Laganier, Julien wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Folks,<br>
<br>
Is there anybody interested in helping completing the BTNS APIs<br>
documents? If you are, please also state the level of commitment you&#39;re=
<br>
willing to dedicate to that goal (e.g., editing, contributing, reviewing.)<=
br>
<br>
If there isn&#39;t enough interest it seems the logical next step for the<b=
r>
BTNS WG is to close without publishing the API docs.<br>
<br>
--julien<br>
_______________________________________________<br>
btns mailing list<br>
<a href=3D"mailto:btns@ietf.org" target=3D"_blank">btns@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/btns" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/btns</a><br>
</blockquote>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (MingW32)<br>
<br>
iEYEARECAAYFAksMF+IACgkQE5f5cImnZrsyCACg+c4Jd22iGsDaOZUcadeMGX/K<br>
rNEAn3XQcB2q5PPGeJdp1buQ1iv/Xzri<br>
=3D5gxJ<br>
-----END PGP SIGNATURE-----<br>
_______________________________________________<br>
btns mailing list<br>
<a href=3D"mailto:btns@ietf.org" target=3D"_blank">btns@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/btns" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/btns</a><br>
</blockquote>
<br>
_______________________________________________<br>
btns mailing list<br>
<a href=3D"mailto:btns@ietf.org" target=3D"_blank">btns@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/btns" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/btns</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Daniel Miga=
ult<br>Orange Labs -- Security<br>+33 6 70 72 69 58<br>

--0016e65aeed02c340204792d53d8--