[Nsis-imp] timer management and message formats

"Hancock, Robert" <robert.hancock@roke.co.uk> Thu, 14 April 2005 15:03 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22507; Thu, 14 Apr 2005 11:03:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM61y-0003NG-77; Thu, 14 Apr 2005 11:13:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM5qB-0001Jz-JN; Thu, 14 Apr 2005 11:01:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DM5qA-0001CL-Fy for nsis-imp@megatron.ietf.org; Thu, 14 Apr 2005 11:01:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22263 for <nsis-imp@ietf.org>; Thu, 14 Apr 2005 11:00:11 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM5zA-0003ED-Kk for nsis-imp@ietf.org; Thu, 14 Apr 2005 11:10:35 -0400
Received: from rsys005a.comm.ad.roke.co.uk ([193.118.193.85]) by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id j3EExrQc007655 for <nsis-imp@ietf.org>; Thu, 14 Apr 2005 15:59:53 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 14 Apr 2005 16:00:10 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2B3@rsys004a>
Thread-Topic: timer management and message formats
Thread-Index: AcVA/8MQhMVlsM3VQOKPmzQ9TWpVQwAAjIQg
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: <nsis-imp@ietf.org>
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: quoted-printable
Subject: [Nsis-imp] timer management and message formats
X-BeenThere: nsis-imp@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: List for implementation questions for NSIS protocols <nsis-imp.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis-imp>, <mailto:nsis-imp-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/nsis-imp>
List-Post: <mailto:nsis-imp@lists.ietf.org>
List-Help: <mailto:nsis-imp-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis-imp>, <mailto:nsis-imp-request@lists.ietf.org?subject=subscribe>
Sender: nsis-imp-bounces@ietf.org
Errors-To: nsis-imp-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable

Hi implementors,

I've done some tidying and refinement of the timer handling for routing
state and messaging association management in response to some of the
open issues.

As a side effect, I would like to re-arrange the message formats (for
routing-state-lifetime and node-addressing) somewhat.

I'd be interested to get some feedback from implementors of the
consequences of these proposals. The discussion and (outline) proposals
are in the issue tracker, specifically
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue16
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue40
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue41

Comments welcome (on this list or the tracker itself).

cheers,

Robert H.

_______________________________________________
NSIS-imp mailing list
NSIS-imp@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/nsis-imp