IETF Logo Mail Archive

Re: [Nsis-imp] timer management and message formats

Martin Stiemerling <stiemerling@netlab.nec.de> Mon, 02 May 2005 11:49 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DSZQI-0006On-2p; Mon, 02 May 2005 07:49:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DSWb5-00038T-Q5 for nsis-imp@megatron.ietf.org; Mon, 02 May 2005 04:48:11 -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 EAA14886 for <nsis-imp@ietf.org>; Mon, 2 May 2005 04:48:09 -0400 (EDT)
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DSWoi-0004lJ-NA for nsis-imp@ietf.org; Mon, 02 May 2005 05:02:18 -0400
Received: from [192.168.178.22] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 4DA411BAC4D; Mon, 2 May 2005 10:48:00 +0200 (CEST)
Date: Mon, 02 May 2005 10:47:57 +0200
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>, nsis-imp@ietf.org
Subject: Re: [Nsis-imp] timer management and message formats
Message-ID: <B34D765ADAC32F43ABC45542@[10.1.1.109]>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2B3@rsys004a>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2B3@rsys004a>
X-Mailer: Mulberry/3.1.6 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc:
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@lists.ietf.org
Errors-To: nsis-imp-bounces@lists.ietf.org

Hi Robert and all,

All changes fine with me.  Another reason for not relying on
transport protocol refreshes:  They do not know NSIS' needs
about refreshes.

  Martin


--On Donnerstag, 14. April 2005 16:00 Uhr +0100 "Hancock, Robert" 
<robert.hancock@roke.co.uk> wrote:

| 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



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

v2.8.7 | Report a Bug | By Email