[dtn-interest] IANA registry for LTP (and the BP?)
Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 01 May 2008 15:19 UTC
Received: from outbound5-sin-R.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m41FJlsC019607 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 08:19:48 -0700
Received: from outbound5-sin.bigfish.com (localhost.localdomain [127.0.0.1]) by outbound5-sin-R.bigfish.com (Postfix) with ESMTP id 1B52BF10D9F for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 15:21:31 +0000 (UTC)
Received: from mail218-sin-R.bigfish.com (unknown [10.3.40.3]) by outbound5-sin.bigfish.com (Postfix) with ESMTP id F33FD8B8067 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 15:21:30 +0000 (UTC)
Received: from mail218-sin (localhost.localdomain [127.0.0.1]) by mail218-sin-R.bigfish.com (Postfix) with ESMTP id E917E358411 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 15:21:30 +0000 (UTC)
X-BigFish: VP
X-MS-Exchange-Organization-Antispam-Report: OrigIP: 134.226.1.156; Service: EHS
Received: by mail218-sin (MessageSwitch) id 1209655290570952_7285; Thu, 1 May 2008 15:21:30 +0000 (UCT)
Received: from imx2.tcd.ie (imx2.tcd.ie [134.226.1.156]) by mail218-sin.bigfish.com (Postfix) with ESMTP id D53AB3E0083 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 15:21:29 +0000 (UTC)
Received: from Vams.imx2 (imx2.tcd.ie [134.226.1.156]) by imx2.tcd.ie (Postfix) with SMTP id F1EBC68002 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 16:21:25 +0100 (IST)
Received: from imx2.tcd.ie ([134.226.1.156]) by imx2.tcd.ie ([134.226.1.156]) with SMTP (gateway) id A0628DEE244; Thu, 01 May 2008 16:21:25 +0100
Received: from [134.226.36.180] (sfarrell.dsg.cs.tcd.ie [134.226.36.180]) by imx2.tcd.ie (Postfix) with ESMTP id E47AA68002 for <dtn-interest@mailman.dtnrg.org>; Thu, 1 May 2008 16:21:25 +0100 (IST)
Message-ID: <4819DFF6.8020504@cs.tcd.ie>
Date: Thu, 01 May 2008 16:21:26 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: DTN <dtn-interest@mailman.dtnrg.org>
X-Enigmail-Version: 0.95.6
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiVirus-Status: MessageID = A1628DEE244
X-AntiVirus-Status: Host: imx2.tcd.ie
X-AntiVirus-Status: Action Taken:
X-AntiVirus-Status: NONE
X-AntiVirus-Status: Checked by TCD Vexira. (version=1.57.6 VDF=9.127.3)
Subject: [dtn-interest] IANA registry for LTP (and the BP?)
X-BeenThere: dtn-interest@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Delay Tolerant Networking Interest List <dtn-interest.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-interest>
List-Post: <mailto:dtn-interest@mailman.dtnrg.org>
List-Help: <mailto:dtn-interest-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2008 15:19:49 -0000
The comment we got about LTP extensions was: > An IANA registry for LTP extension values seems appropriate. Since > [LTPSPEC] does not establish one, it should probably happen here to > assign the two values used here and have a place to register more. > > Since the extension space is small, I recommend expert review as the > policy for new assignments. I think (anyone know for sure?) that the relevant guidelines here are BCP 26. [1] So the questions are whether or not to do this for LTP extensions (and maybe ciphersuites) and secondly for extensible bits of the BP (block types, ciphersuites, anything else?). And if we do want any IANA registries, then what rules should we adopt for updates? I guess there is the possibility that CCSDS's DTN group might want to extend LTP and/or the BP, so maybe it is a good idea for us to think about this now. If anyone knows of other groups that might want to create their own extensions or blocks that'd be useful input here too. As I said in the other mail, my plan for LTP would be to create a new draft-irtf-dtnrg-ltp-iana to document whatever it is we think is the right thing to do. (If anyone wants to take on doing that, let Kevin and I know.) Thoughts? Stephen. [1] http://tools.ietf.org/html/bcp26
- [dtn-interest] IANA registry for LTP (and the BP?) Stephen Farrell
- Re: [dtn-interest] IANA registry for LTP (and the… Stephen Farrell
- [dtn-interest] Re(2): IANA registry for LTP (and … Peter Lovell
- Re: [dtn-interest] IANA registry for LTP (and the… Stephen Farrell