From nsis-imp-bounces@ietf.org  Mon Apr  4 08:07:07 2005
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 IAA23775;
	Mon, 4 Apr 2005 08:07:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIQUA-0000IX-Io; Mon, 04 Apr 2005 08:15:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIQIG-0003ES-L6; Mon, 04 Apr 2005 08:03:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIQIF-0003EN-3M
	for nsis-imp@megatron.ietf.org; Mon, 04 Apr 2005 08:02:59 -0400
Received: from rsys001a.roke.co.uk (rsys001a.roke.co.uk [193.118.192.110])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAB23035
	for <nsis-imp@lists.ietf.org>; Mon, 4 Apr 2005 08:02:58 -0400 (EDT)
Received: by rsys001a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <22RDQRRP>; Mon, 4 Apr 2005 13:02:30 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD275@rsys004a>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "'Georgios Karagiannis'" <karagian@cs.utwente.nl>
Date: Mon, 4 Apr 2005 13:02:22 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
Cc: nsis-imp@ietf.org
Subject: [Nsis-imp] RE: question about GIMPS-Data messages
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: d185fa790257f526fedfd5d01ed9c976

hi georgios,

sorry for the delay, especially since the answer is (IMHO) quite 
simple ;-)

A GIMPS-Data message is used when GIMPS needs to transfer some 
signalling data but doesn't need to do any routing state maintenance 
or set up a messaging association. (In other words, it's an 
'ordinary' message which has no role other than to transfer an 
NSLP-Data payload.) 

so far as the encapsulation is concerned, the three choices 
from -05 (5.3.1/5.3.2/5.4.2) apply. If you know the routing state 
you can use 'normal datagram mode'; if you have a messaging 
association as well you can use connection mode; if you don't 
know either you may be able to use query mode. The choice is 
up to the message sender, but largely irrelevant to the message 
receiver.

in the next version, we'll include a table of the allowed type/encapsulation
combinations, a bit like the following...

   +----------------+----------------+----------------+----------------+
   |     Message    |  D-Mode Normal |  D-Mode Query  |     C-Mode     |
   +----------------+----------------+----------------+----------------+
   |   GIMPS-Query  |      Never     |     Always     |      Never     |
   |                |                |                |                |
   | GIMPS-Response |    Unless a    |      Never     | If a messaging |
   |                |    messaging   |                | association is |
   |                | association is |                |  being re-used |
   |                |  being re-used |                |                |
   |                |                |                |                |
   |  GIMPS-Confirm |    Unless a    |      Never     | If a messaging |
   |                |    messaging   |                |   association  |
   |                |   association  |                |  has been set  |
   |                |  has been set  |                | up or is being |
   |                | up or is being |                |     re-used    |
   |                |     re-used    |                |                |
   |                |                |                |                |
   |   GIMPS-Data   |   If routing   |  If no routing | If a messaging |
   |                |  state exists  |  state exists  |   association  |
   |                |  for the flow  |   and the MRI  |     exists     |
   |                |     but no     | can be used to |                |
   |                |   appropriate  |   derive the   |                |
   |                |    messaging   |      query     |                |
   |                |   association  |  encapsulation |                |
   +----------------+----------------+----------------+----------------+

hope this helps!

robert h.

-----Original Message-----
From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl] 
Sent: 30 March 2005 09:31
To: Hancock, Robert
Cc: nsis-imp@lists.ietf.org
Subject: question about GIMPS-Data messages


Hi Robert and all

In Section 5.1 of  draft-ietf-nsis-ntlp-05.txt, in addition to GIMPS-Query,
GIMPS-Response, 
GIMPS-Confirm another message is specified, i.e.,:
GIMPS-Data.

Could you give an example on where the GIMPS-Data messages are used?

How is the addressing of  the GIMPS-Data messages performed?
In downstream using (typically) IP source and IP destination address of the
flow
In upstream using previuos hop addressing.

Best Regards,
Georgios

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


From nsis-imp-bounces@ietf.org  Fri Apr  8 05:22:45 2005
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 FAA21808;
	Fri, 8 Apr 2005 05:22:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJpq7-0000VU-Jy; Fri, 08 Apr 2005 05:31:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJpfK-0000R1-NH; Fri, 08 Apr 2005 05:20:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJpf6-0000Kj-VM
	for nsis-imp@megatron.ietf.org; Fri, 08 Apr 2005 05:20:25 -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 FAA21605
	for <nsis-imp@ietf.org>; Fri, 8 Apr 2005 05:20:22 -0400 (EDT)
Received: from s2.ifi.informatik.uni-goettingen.de ([134.76.81.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJpnq-0000Pj-5j
	for nsis-imp@ietf.org; Fri, 08 Apr 2005 05:29:26 -0400
Received: from localhost (localhost [127.0.0.1]) (uid 1009)
	by s2.ifi.informatik.uni-goettingen.de with local;
	Fri, 08 Apr 2005 11:20:15 +0200 id 00033CD9.42564CCF.00007911
From: "Xiaoming Fu" <fu@cs.uni-goettingen.de>
To: casp@cs.uni-goettingen.de, nsis-imp@ietf.org
Date: Fri, 08 Apr 2005 11:20:15 +0200
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Sender: fu@s2.ifi.informatik.uni-goettingen.de
Message-ID: <courier.42564CCF.00007911@s2.ifi.informatik.uni-goettingen.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Cc: hgs@cs.uni-goettingen.de, ruediger.geib@t-systems.com
Subject: [Nsis-imp] review of a QoS NSLP implementation
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: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Dear colleagues, 

You may note that a prototype implemenation of QoS NSLP has been released to 
public a few weeks ago, available at 
http://user.informatik.uni-goettingen.de/~qos. It is based on GoCASP as NTLP 
which uses a plug-in architecture for building any NSLP application. We 
would greatly appreciate if you could review it and possibly provide 
suggestions for its improvements, as well as the CASP implementations. 

Thanks,
Xiaoming 

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


From nsis-imp-bounces@ietf.org  Fri Apr  8 09:11:15 2005
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 JAA15847;
	Fri, 8 Apr 2005 09:11:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJtPG-0004ca-Rb; Fri, 08 Apr 2005 09:20:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJtDj-0006Zr-VE; Fri, 08 Apr 2005 09:08:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJtDj-0006Zm-4h
	for nsis-imp@megatron.ietf.org; Fri, 08 Apr 2005 09:08:23 -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 JAA15590
	for <nsis-imp@ietf.org>; Fri, 8 Apr 2005 09:08:22 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJtMT-0004Tr-DK
	for nsis-imp@ietf.org; Fri, 08 Apr 2005 09:17:27 -0400
Received: from rsys002a.roke.co.uk (rsys002a.roke.co.uk [193.118.192.251])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id j38D7qQc020723;
	Fri, 8 Apr 2005 14:07:53 +0100
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <23Y4WTH8>; Fri, 8 Apr 2005 14:08:04 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD297@rsys004a>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "'Xiaoming Fu'" <fu@cs.uni-goettingen.de>, casp@cs.uni-goettingen.de,
        nsis-imp@ietf.org
Subject: RE: [Nsis-imp] review of a QoS NSLP implementation
Date: Fri, 8 Apr 2005 14:07:46 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: hgs@cs.uni-goettingen.de, ruediger.geib@t-systems.com
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: a7d6aff76b15f3f56fcb94490e1052e4

just out of interest...

are there plans to move this towards a more NSIS-compliant
implementation? (from the interoperability perspective, this
would be interesting.)

r.

> -----Original Message-----
> From: Xiaoming Fu [mailto:fu@cs.uni-goettingen.de] 
> Sent: 08 April 2005 10:20
> To: casp@cs.uni-goettingen.de; nsis-imp@ietf.org
> Cc: hgs@cs.uni-goettingen.de; ruediger.geib@t-systems.com
> Subject: [Nsis-imp] review of a QoS NSLP implementation
> 
> 
> Dear colleagues, 
> 
> You may note that a prototype implemenation of QoS NSLP has 
> been released to 
> public a few weeks ago, available at 
> http://user.informatik.uni-goettingen.de/~qos. It is based on 
> GoCASP as NTLP 
> which uses a plug-in architecture for building any NSLP 
> application. We 
> would greatly appreciate if you could review it and possibly provide 
> suggestions for its improvements, as well as the CASP 
> implementations. 
> 
> Thanks,
> Xiaoming 
> 
> _______________________________________________
> 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


From nsis-imp-bounces@ietf.org  Fri Apr  8 09:42:38 2005
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 JAA19860;
	Fri, 8 Apr 2005 09:42:38 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJttf-0006cd-2B; Fri, 08 Apr 2005 09:51:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJtj9-0007c9-L2; Fri, 08 Apr 2005 09:40:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJtj8-0007c4-3i
	for nsis-imp@megatron.ietf.org; Fri, 08 Apr 2005 09:40:50 -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 JAA19632
	for <nsis-imp@ietf.org>; Fri, 8 Apr 2005 09:40:48 -0400 (EDT)
Received: from s2.ifi.informatik.uni-goettingen.de ([134.76.81.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJtrs-0006TZ-JD
	for nsis-imp@ietf.org; Fri, 08 Apr 2005 09:49:54 -0400
Received: from [213.7.194.61] (Bc23d.b.pppool.de [::ffff:213.7.194.61])
	(AUTH: LOGIN fu) by s2.ifi.informatik.uni-goettingen.de with esmtp;
	Fri, 08 Apr 2005 15:40:42 +0200 id 00033CC8.425689DD.00007FF1
Message-ID: <425689AF.4000507@cs.uni-goettingen.de>
Date: Fri, 08 Apr 2005 15:39:59 +0200
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.5) Gecko/20041217
X-Accept-Language: en-us, en, de, en-gb, de-de, zh-cn
MIME-Version: 1.0
To: "Hancock, Robert" <robert.hancock@roke.co.uk>
Subject: Re: [Nsis-imp] review of a QoS NSLP implementation
References: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD297@rsys004a>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD297@rsys004a>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.9 (++)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit
Cc: casp@cs.uni-goettingen.de, nsis-imp@ietf.org
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: 2.9 (++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit

Yes, actually in internal planning and hopefully be available sometime soon.
Cheers,
Xiaoming
Hancock, Robert wrote:
> just out of interest...
> 
> are there plans to move this towards a more NSIS-compliant
> implementation? (from the interoperability perspective, this
> would be interesting.)
> 
> r.
> 
> 
>>-----Original Message-----
>>From: Xiaoming Fu [mailto:fu@cs.uni-goettingen.de] 
>>Sent: 08 April 2005 10:20
>>To: casp@cs.uni-goettingen.de; nsis-imp@ietf.org
>>Cc: hgs@cs.uni-goettingen.de; ruediger.geib@t-systems.com
>>Subject: [Nsis-imp] review of a QoS NSLP implementation
>>
>>
>>Dear colleagues, 
>>
>>You may note that a prototype implemenation of QoS NSLP has 
>>been released to 
>>public a few weeks ago, available at 
>>http://user.informatik.uni-goettingen.de/~qos. It is based on 
>>GoCASP as NTLP 
>>which uses a plug-in architecture for building any NSLP 
>>application. We 
>>would greatly appreciate if you could review it and possibly provide 
>>suggestions for its improvements, as well as the CASP 
>>implementations. 
>>
>>Thanks,
>>Xiaoming 
>>
>>_______________________________________________
>>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


From nsis-imp-bounces@ietf.org  Sat Apr  9 20:12:17 2005
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 UAA18776;
	Sat, 9 Apr 2005 20:12:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DKQCm-0004on-Qo; Sat, 09 Apr 2005 20:21:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DKQ31-00014j-W2; Sat, 09 Apr 2005 20:11:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DKQ30-00014Z-22
	for nsis-imp@megatron.ietf.org; Sat, 09 Apr 2005 20:11:30 -0400
Received: from www.difra-computer.de (difra-computer.de [81.169.157.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18706
	for <nsis-imp@lists.ietf.org>; Sat, 9 Apr 2005 20:11:28 -0400 (EDT)
Received: from win2003.dickmann2003.home (pD9509BB1.dip.t-dialin.net
	[217.80.155.177]) (using TLSv1 with cipher RC4-MD5 (128/128 bits))
	(No client certificate requested)
	by www.difra-computer.de (Postfix) with ESMTP id D19243E4049
	for <nsis-imp@lists.ietf.org>; Sun, 10 Apr 2005 02:05:38 +0200 (CEST)
Received: from christian ([192.168.0.2]) by win2003.dickmann2003.home with
	Microsoft SMTPSVC(6.0.3790.211); Sun, 10 Apr 2005 02:03:21 +0200
From: "Christian Dickmann" <mail@christian-dickmann.de>
To: <nsis-imp@ietf.org>
Date: Sun, 10 Apr 2005 02:04:10 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU9YNJ8kNCmApAPS6K1u0WCX8eIvw==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <WIN2003bZGjYRHogN2B0000002b@win2003.dickmann2003.home>
X-OriginalArrivalTime: 10 Apr 2005 00:03:21.0876 (UTC)
	FILETIME=[B55B9540:01C53D60]
Content-Transfer-Encoding: 7bit
Subject: [Nsis-imp] Small mistake in C.4.1 of GIMPS-05
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.2 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

Hi,

I think I found a small mistake in chapter C.4.1 of the GIMPS
draft (version 05).

In version 5 the Source Port and Destination Port flags of MRI
where renamed from S/D to A/B. The text however continues
refering to S and D ("If only one of S, D is set, both ...").

I hope this mailing list is the right place to report
this issue.

Christian Dickmann



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


From nsis-imp-bounces@ietf.org  Thu Apr 14 10:39:05 2005
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 KAA19736;
	Thu, 14 Apr 2005 10:39:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM5ep-0002DZ-H1; Thu, 14 Apr 2005 10:49:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM5UW-0005mw-BV; Thu, 14 Apr 2005 10:38:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM5UV-0005ka-DR
	for nsis-imp@megatron.ietf.org; Thu, 14 Apr 2005 10:38:47 -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 KAA19661
	for <nsis-imp@ietf.org>; Thu, 14 Apr 2005 10:38:40 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM5eP-0002Cv-OA
	for nsis-imp@ietf.org; Thu, 14 Apr 2005 10:49:03 -0400
Received: from rsys002a.roke.co.uk (rsys002a.roke.co.uk [193.118.192.251])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id j3EEcIQc002179;
	Thu, 14 Apr 2005 15:38:18 +0100
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <26RQ8K50>; Thu, 14 Apr 2005 15:38:37 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2B2@rsys004a>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "'Christian Dickmann'" <mail@christian-dickmann.de>, nsis-imp@ietf.org
Subject: RE: [Nsis-imp] Small mistake in C.4.1 of GIMPS-05
Date: Thu, 14 Apr 2005 15:38:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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: 0ddefe323dd869ab027dbfff7eff0465

Hi Christian,

You can report it here (which I read) or send it direct to the editors
(of which I am one).

(And you are right that it is an error!)

You can also check out the GIMPS issue tracker at 
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/index
(where you will find issue 35 contains a whole stream of issues
we found about this object format during the first informal set of
interoperability tests ...)

Thanks and keep reading ;-)

Robert H.

> -----Original Message-----
> From: Christian Dickmann [mailto:mail@christian-dickmann.de] 
> Sent: 10 April 2005 01:04
> To: nsis-imp@ietf.org
> Subject: [Nsis-imp] Small mistake in C.4.1 of GIMPS-05
> 
> 
> Hi,
> 
> I think I found a small mistake in chapter C.4.1 of the GIMPS
> draft (version 05).
> 
> In version 5 the Source Port and Destination Port flags of MRI
> where renamed from S/D to A/B. The text however continues
> refering to S and D ("If only one of S, D is set, both ...").
> 
> I hope this mailing list is the right place to report
> this issue.
> 
> Christian Dickmann
> 
> 
> 
> _______________________________________________
> 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


From nsis-imp-bounces@ietf.org  Thu Apr 14 11:03:00 2005
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


From nsis-imp-bounces@lists.ietf.org Tue Apr 26 06:28:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQNJJ-0003Or-Dp; Tue, 26 Apr 2005 06:28:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQNJI-0003Og-GB
	for nsis-imp@megatron.ietf.org; Tue, 26 Apr 2005 06:28:56 -0400
Received: from denhaag.ewi.utwente.nl (denhaag.ewi.utwente.nl [130.89.10.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19600
	for <nsis-imp@lists.ietf.org>; Tue, 26 Apr 2005 05:43:43 -0400 (EDT)
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id j3Q9hhh2018776
	for <nsis-imp@lists.ietf.org>; Tue, 26 Apr 2005 11:43:43 +0200 (MEST)
Message-ID: <010d01c54a44$6fd79c80$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: <nsis-imp@ietf.org>
Date: Tue, 26 Apr 2005 11:43:39 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -4.2 () BAYES_00,HTML_MESSAGE,J_CHICKENPOX_92
X-Scanned-By: MIMEDefang 2.44
Cc: 
Subject: [Nsis-imp] some clarification questions regarding GIMPS
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>
Content-Type: multipart/mixed; boundary="===============2033824407=="
Sender: nsis-imp-bounces@lists.ietf.org
Errors-To: nsis-imp-bounces@lists.ietf.org

This is a multi-part message in MIME format.

--===============2033824407==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_010A_01C54A55.302788A0"

This is a multi-part message in MIME format.

------=_NextPart_000_010A_01C54A55.302788A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear all

We at the moment implementing the GIMPS protocol and we find that there =
are some issues
that would need some clarification, etc.

These issues are:

1- For the implementation of the discovery mechanism,it is important to =
know=20
if a procedure has to be implemented to check whether the sender of the=20
Query cookie is also the sender of the confirm cookie.

2- The value of the D-flag that corresponds to the upstream and=20
downstream has to be specified.

3- The function of the source prefix and destination prefix of the=20
MRI object has to be defined.

4- In our implementation we are only using IP-Ver 4. Therefore it might =
be=20
useful to know if the entire 32 bit word for the Flow Label parameter in =
the=20
MRI object must be ignored or set to zero (empty object).

Could you clarify the above?

Best regards,
Georgios

------=_NextPart_000_010A_01C54A55.302788A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Dear all</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We at the moment implementing the GIMPS =
protocol=20
and we find that there are some issues</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>that would need some clarification,=20
etc.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>These issues are:</FONT></DIV><FONT =
face=3DArial=20
size=3D2>
<DIV><BR>1- For the implementation of the discovery mechanism,it is =
important to=20
know <BR>if a procedure has to be implemented to check whether the =
sender of the=20
<BR>Query cookie is also the sender of the confirm cookie.</DIV>
<DIV><BR>2- The value of the D-flag that corresponds to the upstream and =

<BR>downstream has to be specified.</DIV>
<DIV><BR>3- The function of the source prefix and destination prefix of =
the=20
<BR>MRI object has to be defined.</DIV>
<DIV><BR>4- In our implementation we are only using IP-Ver 4. Therefore =
it might=20
be <BR>useful to know if the entire 32 bit word for the Flow Label =
parameter in=20
the <BR>MRI object must be ignored or set to zero (empty=20
object).</FONT><BR></DIV>
<DIV><FONT face=3DArial size=3D2>Could you clarify the =
above?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Georgios</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_010A_01C54A55.302788A0--



--===============2033824407==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2033824407==--





From nsis-imp-bounces@lists.ietf.org Tue Apr 26 06:47:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQNbS-00059X-LN; Tue, 26 Apr 2005 06:47:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQNbR-00059S-G6
	for nsis-imp@megatron.ietf.org; Tue, 26 Apr 2005 06:47:41 -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 GAA24176
	for <nsis-imp@ietf.org>; Tue, 26 Apr 2005 06:47:38 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQNnq-0008Jm-HN
	for nsis-imp@ietf.org; Tue, 26 Apr 2005 07:00:32 -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 j3QAlFqP020419;
	Tue, 26 Apr 2005 11:47:15 +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
Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS
Date: Tue, 26 Apr 2005 11:47:49 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2E0@rsys004a>
Thread-Topic: [Nsis-imp] some clarification questions regarding GIMPS
Thread-Index: AcVKSuP1QB0C7Du0SESZxckWcbzZEgAAPnbg
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>, <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: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
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 georgios,

thanks for the questions! see in line...

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
> Sent: 26 April 2005 10:44
> To: nsis-imp@ietf.org
> Subject: [Nsis-imp] some clarification questions regarding GIMPS
>=20
>=20
> Dear all
>=20
> We at the moment implementing the GIMPS protocol and we find=20
> that there are some issues
> that would need some clarification, etc.
>=20
> These issues are:
>=20
> 1- For the implementation of the discovery mechanism,it is=20
> important to know=20
> if a procedure has to be implemented to check whether the=20
> sender of the=20
> Query cookie is also the sender of the confirm cookie.

this is a hard question. the ideal answer is 'yes' but, given
that the purpose of the 3 way handshake is supposed to allow=20
the responding node to forget the query contents and work only
with the confirm, it is not clear to me at the moment that it
is possible in general, unless the responder cookie is designed
to refer to information that will be repeated in the confirm.
(we have started this discussion at=20
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue17)

we need to do more work on this, and i have text lying around,
but still need to make it comprehensible (and plausible).

>=20
> 2- The value of the D-flag that corresponds to the upstream and=20
> downstream has to be specified.

do you just mean 'is 1 up and 0 down or the other way round'?
or something more subtle?

>=20
> 3- The function of the source prefix and destination prefix of the=20
> MRI object has to be defined.

this is to allow wildcarding on address fields. the signalling message
delivery uses the actual addresses, but the MRI is interpreted as
referring to the whole subnet (e.g. might be used by an NSLP as a
wildcard in a traffic classifier). GIMPS should reject 'too broad'
wildcards (in a manner to be defined in the next version of the
draft).

>=20
> 4- In our implementation we are only using IP-Ver 4.=20
> Therefore it might be=20
> useful to know if the entire 32 bit word for the Flow Label=20
> parameter in the=20
> MRI object must be ignored or set to zero (empty object).

wrong on both counts (see
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue34
which we wrote during the interoperability testing
in minneapolis). the short answer is:
if the flag for a field in set in the first word, the field must
be present and interpreted as significant
otherwise, the field must not be present at all.

(this is supposed to be implied by the ':' symbols in the box
notation indicating 'optional fields' but I accept it is a bit
hard to spot and the next version will be more explicit.)

at the moment my expectation is not to try to pin down exactly
which version/flag combinations must be supported, but to=20
rely on common sense (e.g. people won't generate MRIs with v=3D4
and F set) and defining a general purpose ICMP-like 'parameter=20
problem' message to allow people to report that they don't like
particular settings. i'd appreciate input on that, however.

hope this helps,

r.
>=20
> Could you clarify the above?
>=20
> Best regards,
> Georgios
>=20

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



From nsis-imp-bounces@lists.ietf.org Tue Apr 26 06:56:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQNk9-0006CP-3U; Tue, 26 Apr 2005 06:56:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQNk7-0006CK-71
	for nsis-imp@megatron.ietf.org; Tue, 26 Apr 2005 06:56:39 -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 GAA25119
	for <nsis-imp@ietf.org>; Tue, 26 Apr 2005 06:56:36 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQNwX-00007C-FK
	for nsis-imp@ietf.org; Tue, 26 Apr 2005 07:09:30 -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 j3QAu7qP022751;
	Tue, 26 Apr 2005 11:56:07 +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
Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS
Date: Tue, 26 Apr 2005 11:56:41 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2E1@rsys004a>
Thread-Topic: [Nsis-imp] some clarification questions regarding GIMPS
Thread-Index: AcVKTYq+9GUjsv9vRSav36AeR5L0RQAAJIRw
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>,
	"Georgios Karagiannis" <karagian@cs.utwente.nl>, <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: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: quoted-printable
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

and a brief followup on the cookie front:

for *interoperability* the only thing that is required is to
copy the cookies correctly between Q/R/C messages. so, for
testing, that is the only thing that will get exercised.

the *generation and validation* you do is up to the implementation=20
and not visible externally (you might just generate a random
number and not validate anything). we will give informative
examples in the spec of how to do a good job, however. but=20
in any case we will ensure that they don't violate the basic
design goals (e.g. stateless handling of an initial query.)

r.


> -----Original Message-----
> From: Hancock, Robert=20
> Sent: 26 April 2005 11:48
> To: Georgios Karagiannis; nsis-imp@ietf.org
> Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS
>=20
>=20
> hi georgios,
>=20
> thanks for the questions! see in line...
>=20
> > -----Original Message-----
> > From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl]=20
> > Sent: 26 April 2005 10:44
> > To: nsis-imp@ietf.org
> > Subject: [Nsis-imp] some clarification questions regarding GIMPS
> >=20
> >=20
> > Dear all
> >=20
> > We at the moment implementing the GIMPS protocol and we find=20
> > that there are some issues
> > that would need some clarification, etc.
> >=20
> > These issues are:
> >=20
> > 1- For the implementation of the discovery mechanism,it is=20
> > important to know=20
> > if a procedure has to be implemented to check whether the=20
> > sender of the=20
> > Query cookie is also the sender of the confirm cookie.
>=20
> this is a hard question. the ideal answer is 'yes' but, given
> that the purpose of the 3 way handshake is supposed to allow=20
> the responding node to forget the query contents and work only
> with the confirm, it is not clear to me at the moment that it
> is possible in general, unless the responder cookie is designed
> to refer to information that will be repeated in the confirm.
> (we have started this discussion at=20
> http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue17)
>=20
> we need to do more work on this, and i have text lying around,
> but still need to make it comprehensible (and plausible).
>=20
> >=20
> > 2- The value of the D-flag that corresponds to the upstream and=20
> > downstream has to be specified.
>=20
> do you just mean 'is 1 up and 0 down or the other way round'?
> or something more subtle?
>=20
> >=20
> > 3- The function of the source prefix and destination prefix of the=20
> > MRI object has to be defined.
>=20
> this is to allow wildcarding on address fields. the signalling message
> delivery uses the actual addresses, but the MRI is interpreted as
> referring to the whole subnet (e.g. might be used by an NSLP as a
> wildcard in a traffic classifier). GIMPS should reject 'too broad'
> wildcards (in a manner to be defined in the next version of the
> draft).
>=20
> >=20
> > 4- In our implementation we are only using IP-Ver 4.=20
> > Therefore it might be=20
> > useful to know if the entire 32 bit word for the Flow Label=20
> > parameter in the=20
> > MRI object must be ignored or set to zero (empty object).
>=20
> wrong on both counts (see
> http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue34
> which we wrote during the interoperability testing
> in minneapolis). the short answer is:
> if the flag for a field in set in the first word, the field must
> be present and interpreted as significant
> otherwise, the field must not be present at all.
>=20
> (this is supposed to be implied by the ':' symbols in the box
> notation indicating 'optional fields' but I accept it is a bit
> hard to spot and the next version will be more explicit.)
>=20
> at the moment my expectation is not to try to pin down exactly
> which version/flag combinations must be supported, but to=20
> rely on common sense (e.g. people won't generate MRIs with v=3D4
> and F set) and defining a general purpose ICMP-like 'parameter=20
> problem' message to allow people to report that they don't like
> particular settings. i'd appreciate input on that, however.
>=20
> hope this helps,
>=20
> r.
> >=20
> > Could you clarify the above?
> >=20
> > Best regards,
> > Georgios
> >=20
>=20
> _______________________________________________
> NSIS-imp mailing list
> NSIS-imp@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis-imp
>=20

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



From nsis-imp-bounces@lists.ietf.org Thu Apr 28 04:29:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DR4Op-00050C-DR; Thu, 28 Apr 2005 04:29:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DR4On-0004yw-4u
	for nsis-imp@megatron.ietf.org; Thu, 28 Apr 2005 04:29:29 -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 EAA23378
	for <nsis-imp@ietf.org>; Thu, 28 Apr 2005 04:29:27 -0400 (EDT)
Received: from denhaag.ewi.utwente.nl ([130.89.10.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DR4bc-0007LH-6s
	for nsis-imp@ietf.org; Thu, 28 Apr 2005 04:42:44 -0400
Received: from utip105 (utip105.ewi.utwente.nl [130.89.13.76])
	by denhaag.ewi.utwente.nl (8.13.1/8.13.1) with SMTP id j3S8TLpE027536; 
	Thu, 28 Apr 2005 10:29:23 +0200 (MEST)
Message-ID: <001e01c54bcc$61fe3b30$4c0d5982@dynamic.ewi.utwente.nl>
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "Hancock, Robert" <robert.hancock@roke.co.uk>, <nsis-imp@ietf.org>
References: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2E0@rsys004a>
Subject: Re: [Nsis-imp] some clarification questions regarding GIMPS
Date: Thu, 28 Apr 2005 10:29:16 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: -4.3 () BAYES_00,J_CHICKENPOX_92
X-Scanned-By: MIMEDefang 2.44
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
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 

Thank you very much!
Regarding points 2 and 3., see below:

>> 2- The value of the D-flag that corresponds to the upstream and 
>> downstream has to be specified.
> 
> do you just mean 'is 1 up and 0 down or the other way round'?
> or something more subtle?

What I mean, is:
 'is 1 up and 0 down or the other way round'?

> 
>> 
>> 3- The function of the source prefix and destination prefix of the 
>> MRI object has to be defined.

Could you please give an example?

Best Regards,
Georgios

----- Original Message ----- 
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "Georgios Karagiannis" <karagian@cs.utwente.nl>; <nsis-imp@ietf.org>
Sent: Tuesday, April 26, 2005 12:47 PM
Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS


> hi georgios,
> 
> thanks for the questions! see in line...
> 
>> -----Original Message-----
>> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl] 
>> Sent: 26 April 2005 10:44
>> To: nsis-imp@ietf.org
>> Subject: [Nsis-imp] some clarification questions regarding GIMPS
>> 
>> 
>> Dear all
>> 
>> We at the moment implementing the GIMPS protocol and we find 
>> that there are some issues
>> that would need some clarification, etc.
>> 
>> These issues are:
>> 
>> 1- For the implementation of the discovery mechanism,it is 
>> important to know 
>> if a procedure has to be implemented to check whether the 
>> sender of the 
>> Query cookie is also the sender of the confirm cookie.
> 
> this is a hard question. the ideal answer is 'yes' but, given
> that the purpose of the 3 way handshake is supposed to allow 
> the responding node to forget the query contents and work only
> with the confirm, it is not clear to me at the moment that it
> is possible in general, unless the responder cookie is designed
> to refer to information that will be repeated in the confirm.
> (we have started this discussion at 
> http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue17)
> 
> we need to do more work on this, and i have text lying around,
> but still need to make it comprehensible (and plausible).
> 
>> 
>> 2- The value of the D-flag that corresponds to the upstream and 
>> downstream has to be specified.
> 
> do you just mean 'is 1 up and 0 down or the other way round'?
> or something more subtle?
> 
>> 
>> 3- The function of the source prefix and destination prefix of the 
>> MRI object has to be defined.
> 
> this is to allow wildcarding on address fields. the signalling message
> delivery uses the actual addresses, but the MRI is interpreted as
> referring to the whole subnet (e.g. might be used by an NSLP as a
> wildcard in a traffic classifier). GIMPS should reject 'too broad'
> wildcards (in a manner to be defined in the next version of the
> draft).
> 
>> 
>> 4- In our implementation we are only using IP-Ver 4. 
>> Therefore it might be 
>> useful to know if the entire 32 bit word for the Flow Label 
>> parameter in the 
>> MRI object must be ignored or set to zero (empty object).
> 
> wrong on both counts (see
> http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue34
> which we wrote during the interoperability testing
> in minneapolis). the short answer is:
> if the flag for a field in set in the first word, the field must
> be present and interpreted as significant
> otherwise, the field must not be present at all.
> 
> (this is supposed to be implied by the ':' symbols in the box
> notation indicating 'optional fields' but I accept it is a bit
> hard to spot and the next version will be more explicit.)
> 
> at the moment my expectation is not to try to pin down exactly
> which version/flag combinations must be supported, but to 
> rely on common sense (e.g. people won't generate MRIs with v=4
> and F set) and defining a general purpose ICMP-like 'parameter 
> problem' message to allow people to report that they don't like
> particular settings. i'd appreciate input on that, however.
> 
> hope this helps,
> 
> r.
>> 
>> Could you clarify the above?
>> 
>> Best regards,
>> Georgios
>> 
>

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



From nsis-imp-bounces@lists.ietf.org Fri Apr 29 04:36:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRQz0-0003nd-0F; Fri, 29 Apr 2005 04:36:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRQyx-0003nO-Vs
	for nsis-imp@megatron.ietf.org; Fri, 29 Apr 2005 04:36:20 -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 EAA04204
	for <nsis-imp@ietf.org>; Fri, 29 Apr 2005 04:36:17 -0400 (EDT)
Received: from kyoto.netlab.nec.de ([195.37.70.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRRBz-00084W-Sy
	for nsis-imp@ietf.org; Fri, 29 Apr 2005 04:49:48 -0400
Received: from [192.168.178.22] (mito.netlab.nec.de [195.37.70.39])
	by kyoto.netlab.nec.de (Postfix) with ESMTP id 462551BAC99
	for <nsis-imp@ietf.org>; Fri, 29 Apr 2005 10:36:10 +0200 (CEST)
Date: Fri, 29 Apr 2005 10:31:57 +0200
From: Martin Stiemerling <stiemerling@netlab.nec.de>
To: nsis-imp@ietf.org
Message-ID: <468F8F7D92EAE5B8C6A5EACE@753F3B888A9969457862729D>
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: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Nsis-imp] NSIS/NTLP Interoperability Event before IETF in Paris
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 all,

This is an announcement for the NSIS/NTLP interoperability testing
event to be held July 28 to July 30 in Paris. July 28 to July 30,
Thursday to Saturday, is right before the 63rd IETF meeting in Paris.
The interoperability venue is at the same venue as the IETF meeting
is going to be, Palais des Congres
(<http://www.palaisdescongres-paris.com/gb/index.asp>).

The interoperability event focuses on testing of the NTLP between
different implementations, but is not necessary limited to the NTLP
only.

The venue will provided by NEC and the EU IST project Eurolabs
(<http://www.ist-eurolabs.org/>).  Participation for implementers
is free of charge and only implementers are allowed to join
the event.

Further information about registration, times, shipping, modalities,
etc will be provided soon.

This event will be co-located with the interoperability testing event
of the IST MOME project (<http://www.ist-mome.org/events/interop/>)

With best regards,

    Martin Stiemerling

NEC Europe Ltd. -- Network Laboratories stiemerling@netlab.nec.de
PGP Key at:        http://www.stiemerling.org/stiemerling_nec.gpg
WWW: http://www.netlab.nec.de

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



From nsis-imp-bounces@lists.ietf.org Fri Apr 29 04:49:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRRBG-00066E-Q7; Fri, 29 Apr 2005 04:49:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRRBD-000668-Ka
	for nsis-imp@megatron.ietf.org; Fri, 29 Apr 2005 04:48:59 -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 EAA04995
	for <nsis-imp@ietf.org>; Fri, 29 Apr 2005 04:48:57 -0400 (EDT)
Received: from rsys001x.roke.co.uk ([193.118.201.108])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRROF-000090-3I
	for nsis-imp@ietf.org; Fri, 29 Apr 2005 05:02:28 -0400
Received: from rsys002a.roke.co.uk (rsys002a.roke.co.uk [193.118.192.251])
	by rsys001x.roke.co.uk (8.12.8/8.12.8) with ESMTP id j3T8maqP013717;
	Fri, 29 Apr 2005 09:48:36 +0100
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2657.72)
	id <JF3JW6YJ>; Fri, 29 Apr 2005 09:49:14 +0100
Message-ID: <3F2E01E1D7B04F4EBEC92D3FA324D8807DD2FE@rsys004a>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: "'Georgios Karagiannis'" <karagian@cs.utwente.nl>, nsis-imp@ietf.org
Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS
Date: Fri, 29 Apr 2005 09:49:07 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-MailScanner-rsys001x: Found to be clean
X-MailScanner-From: robert.hancock@roke.co.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
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 georgios,

answers below:

> -----Original Message-----
> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl] 
> Sent: 28 April 2005 09:29
> To: Hancock, Robert; nsis-imp@ietf.org
> Subject: Re: [Nsis-imp] some clarification questions regarding GIMPS
> 
> 
> Hi Robert 
> 
> Thank you very much!
> Regarding points 2 and 3., see below:
> 
> >> 2- The value of the D-flag that corresponds to the upstream and 
> >> downstream has to be specified.
> > 
> > do you just mean 'is 1 up and 0 down or the other way round'?
> > or something more subtle?
> 
> What I mean, is:
>  'is 1 up and 0 down or the other way round'?

the D=direction flag is:
if clear: in the same direction as the flow
if set: in the opposite direction to the flow

for example, a Query would normally have D=0 and the 
Response D=1.

i've given myself an editorial issue to make this clearer.
http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue42

> 
> > 
> >> 
> >> 3- The function of the source prefix and destination prefix of the 
> >> MRI object has to be defined.
> 
> Could you please give an example?

this is a more interesting question, which will send me into 
discursive mode briefly:

the addresses in the MRI have a dual significance:
- they tell GIMPS how to encapsulate the Q/R/C messages (i.e. what
source and destination addresses to use for them) and hence 
implicitly define the path;
- they form part of the definition of which packets the signalling
is about (i.e. is used as part of the packet classifier).

For the second, sometimes a wildcard is appropriate (see e.g.
draft-bajko-nsis-FW-reqs-00.txt and the various protocol
specs). An example would be a IPv6 'leaf network' with a /64
address range allocated (like a cellular host) which wanted to
signal something about all its addresses (e.g. it might be using
privacy addresses) without carrying out multiple signalling
exchanges. For this reason, you can apply a prefix length to the
addresses to implement this wildcarding.

To take a concrete example of a single GIMPS data message
  MRI(IPversion = 4,
	Flow source = 123.231.112.45,
	Flow destination = 56.78.90.12,
	Source prefix length = 24,
	Destination prefix length = 32,
	Direction = 0 [downstream])

The message will go along the path between 123.231.112.45 and
56.78.90.12 (and a Query message would use precisely those addresses
in its IP header), but will refer to packets from anywhere in 
123.231.112.0/24 to 56.78.90.12.

It's possible for wildcarding to be too wild (e.g. setting a
prefix length to 0). If the prefix length is too short for the
path (i.e. it includes addresses for which the packets would
go along different paths), it's up to GIMPS to reject the
message. I am working on the error messages at the moment ;-)

Hope this helps,

Robert H.

> 
> Best Regards,
> Georgios
> 
> ----- Original Message ----- 
> From: "Hancock, Robert" <robert.hancock@roke.co.uk>
> To: "Georgios Karagiannis" <karagian@cs.utwente.nl>; 
> <nsis-imp@ietf.org>
> Sent: Tuesday, April 26, 2005 12:47 PM
> Subject: RE: [Nsis-imp] some clarification questions regarding GIMPS
> 
> 
> > hi georgios,
> > 
> > thanks for the questions! see in line...
> > 
> >> -----Original Message-----
> >> From: Georgios Karagiannis [mailto:karagian@cs.utwente.nl] 
> >> Sent: 26 April 2005 10:44
> >> To: nsis-imp@ietf.org
> >> Subject: [Nsis-imp] some clarification questions regarding GIMPS
> >> 
> >> 
> >> Dear all
> >> 
> >> We at the moment implementing the GIMPS protocol and we find 
> >> that there are some issues
> >> that would need some clarification, etc.
> >> 
> >> These issues are:
> >> 
> >> 1- For the implementation of the discovery mechanism,it is 
> >> important to know 
> >> if a procedure has to be implemented to check whether the 
> >> sender of the 
> >> Query cookie is also the sender of the confirm cookie.
> > 
> > this is a hard question. the ideal answer is 'yes' but, given
> > that the purpose of the 3 way handshake is supposed to allow 
> > the responding node to forget the query contents and work only
> > with the confirm, it is not clear to me at the moment that it
> > is possible in general, unless the responder cookie is designed
> > to refer to information that will be repeated in the confirm.
> > (we have started this discussion at 
> > http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue17)
> > 
> > we need to do more work on this, and i have text lying around,
> > but still need to make it comprehensible (and plausible).
> > 
> >> 
> >> 2- The value of the D-flag that corresponds to the upstream and 
> >> downstream has to be specified.
> > 
> > do you just mean 'is 1 up and 0 down or the other way round'?
> > or something more subtle?
> > 
> >> 
> >> 3- The function of the source prefix and destination prefix of the 
> >> MRI object has to be defined.
> > 
> > this is to allow wildcarding on address fields. the 
> signalling message
> > delivery uses the actual addresses, but the MRI is interpreted as
> > referring to the whole subnet (e.g. might be used by an NSLP as a
> > wildcard in a traffic classifier). GIMPS should reject 'too broad'
> > wildcards (in a manner to be defined in the next version of the
> > draft).
> > 
> >> 
> >> 4- In our implementation we are only using IP-Ver 4. 
> >> Therefore it might be 
> >> useful to know if the entire 32 bit word for the Flow Label 
> >> parameter in the 
> >> MRI object must be ignored or set to zero (empty object).
> > 
> > wrong on both counts (see
> > http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-ntlp-issues/issue34
> > which we wrote during the interoperability testing
> > in minneapolis). the short answer is:
> > if the flag for a field in set in the first word, the field must
> > be present and interpreted as significant
> > otherwise, the field must not be present at all.
> > 
> > (this is supposed to be implied by the ':' symbols in the box
> > notation indicating 'optional fields' but I accept it is a bit
> > hard to spot and the next version will be more explicit.)
> > 
> > at the moment my expectation is not to try to pin down exactly
> > which version/flag combinations must be supported, but to 
> > rely on common sense (e.g. people won't generate MRIs with v=4
> > and F set) and defining a general purpose ICMP-like 'parameter 
> > problem' message to allow people to report that they don't like
> > particular settings. i'd appreciate input on that, however.
> > 
> > hope this helps,
> > 
> > r.
> >> 
> >> Could you clarify the above?
> >> 
> >> Best regards,
> >> Georgios
> >> 
> >
> 

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



