IETF Logo Mail Archive

Re: [NSIS] Message Looping in GIMPS

Xiaoming Fu <fu@cs.uni-goettingen.de> Sat, 20 March 2004 09:45 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03759 for <nsis-archive@odin.ietf.org>; Sat, 20 Mar 2004 04:45:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4d2V-0001f6-Hz for nsis-archive@odin.ietf.org; Sat, 20 Mar 2004 04:45:27 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2K9jBDF006351 for nsis-archive@odin.ietf.org; Sat, 20 Mar 2004 04:45:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4d2N-0001eD-QK; Sat, 20 Mar 2004 04:45:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B4d29-0001dn-3W for nsis@optimus.ietf.org; Sat, 20 Mar 2004 04:44:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03745 for <nsis@ietf.org>; Sat, 20 Mar 2004 04:44:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B4d26-0005fH-00 for nsis@ietf.org; Sat, 20 Mar 2004 04:44:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B4d18-0005aN-00 for nsis@ietf.org; Sat, 20 Mar 2004 04:43:46 -0500
Received: from user.informatik.uni-goettingen.de ([134.76.81.16] helo=s2.ifi.informatik.uni-goettingen.de) by ietf-mx with esmtp (Exim 4.12) id 1B4d0z-0005VS-00 for nsis@ietf.org; Sat, 20 Mar 2004 04:43:37 -0500
Received: from cs.uni-goettingen.de (IBZGate.ibz.gwdg.de [::ffff:134.76.38.21]) (AUTH: PLAIN fu, TLS: TLSv1/SSLv3,128bits,RC4-MD5) by s2.ifi.informatik.uni-goettingen.de with esmtp; Sat, 20 Mar 2004 10:43:35 +0100
Message-ID: <405C123C.4010501@cs.uni-goettingen.de>
Date: Sat, 20 Mar 2004 10:43:24 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
CC: 'Henning Schulzrinne ' <hgs@cs.columbia.edu>, "'Nsis (E-mail) '" <nsis@ietf.org>
Subject: Re: [NSIS] Message Looping in GIMPS
References: <EA943CD30BCB104E9D38F5B5DC2D9A70019A0437@rsys004a.roke.co.uk>
In-Reply-To: <EA943CD30BCB104E9D38F5B5DC2D9A70019A0437@rsys004a.roke.co.uk>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: nsis-admin@ietf.org
Errors-To: nsis-admin@ietf.org
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Id: Next Steps in Signaling <nsis.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Hi,

Hancock, Robert wrote:
> ok - we should distinguish between
> 
> *) easy to add later - doesn't change the rest of the protocol 
> processing rules
> 
> *) hard to add later - it's mainly useful when a high percentage of
> the nodes implement it but a lot have been deployed without it
> 
> i think the route recording function matches both these. i agree 
> with the debugging aspect being important, and important from the 
> start (i don't believe the qos-nslp needs that have been mentioned
> actually need route recording themselves, i write something about that
> later). 
> 
> i'd be very happy to see someone define a 'diagnostics NSLP' 
> which could even become a MUST/SHOULD to implement along 
> with GIMPS (apart from anything else, it would give us a 
> non-trivial NSLP to play with). there are probably other 
> diagnostic functions that are also needed (some sort of e2e
> echo, for example).
Earlier we had an attempt with a simple "traceroute", described in 
http://user.informatik.uni-goettingen.de/~fu/paper/draft-fu-ccamp-traceroute-00.txt 

http://user.informatik.uni-goettingen.de/~fu/paper/IETF-fu-ccamp-traceroute.pdf 
(presentation slides at IETF#57 - CCAMP WG)

We are currently prototyping it. If interested we would be glad to work 
with the team and extend it towards diagnostics NSLP.

Regards,
Xiaoming

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis

v2.23.0 | Report a Bug | By Email