Re: [btns] BTNS API documents

Joe Touch <touch@ISI.EDU> Tue, 24 November 2009 17:29 UTC

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