[NSIS] NATFW TRACE semantics
Martin Stiemerling <stiemerling@netlab.nec.de> Thu, 11 May 2006 13:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeAtZ-0001uv-9Q; Thu, 11 May 2006 09:07:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FeAtY-0001qq-4g for nsis@ietf.org; Thu, 11 May 2006 09:07:56 -0400
Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeAtX-0000CQ-Qo for nsis@ietf.org; Thu, 11 May 2006 09:07:56 -0400
Received: from [10.1.1.109] (mito.netlab.nec.de [195.37.70.39]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 87C4D1BAC4D for <nsis@ietf.org>; Thu, 11 May 2006 15:00:53 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Transfer-Encoding: 7bit
Message-Id: <35F9F869-0972-4393-896D-A72B6E6E1935@netlab.nec.de>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
To: nsis <nsis@ietf.org>
From: Martin Stiemerling <stiemerling@netlab.nec.de>
Date: Thu, 11 May 2006 15:07:52 +0200
X-Mailer: Apple Mail (2.749.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [NSIS] NATFW TRACE semantics
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org
Dear all, This is a request to read about the TRACE message in the NATFW NSLP draft (http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-11.txt) and to comment on it. The semantics of TRACE is preliminary and we need to get more input on it what exactly TRACE should do in the opinion of the working group. The important section about TRACE are: - 3.8.6 - 4.2.8 - 4.3.5 Currently, TRACE can be only sent by the session owner. TRACE will collect the identifiers of the NATFW NSLP nodes involved in a particular session. However, it is not specified which identifier in a case of a NAT is included or what happens if there is a change of the address family (e.g. from IPv4 to IPv6) is happening. Looking forward to the proposals and discussions Martin _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] NATFW TRACE semantics Martin Stiemerling
- [NSIS] Again: NATFW TRACE semantics Martin Stiemerling