RE: [NSIS] NSLP versioning

<john.loughney@nokia.com> Fri, 09 June 2006 13:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Foh2j-0008N3-3s; Fri, 09 Jun 2006 09:28:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Foh2i-0008MF-6N for nsis@ietf.org; Fri, 09 Jun 2006 09:28:52 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FogwY-00056B-7N for nsis@ietf.org; Fri, 09 Jun 2006 09:22:31 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id k59DMT6p029257; Fri, 9 Jun 2006 16:22:29 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Jun 2006 16:22:29 +0300
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 9 Jun 2006 16:22:28 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NSIS] NSLP versioning
Date: Fri, 09 Jun 2006 16:22:28 +0300
Message-ID: <BAA65A575825454CBB0103267553FCCC39C930@esebe199.NOE.Nokia.com>
In-Reply-To: <92D2D606-F717-4C03-BB35-D3A49B498E8E@netlab.nec.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NSIS] NSLP versioning
Thread-Index: AcaK37ytF8IFFG2RSNGMcxGtncr0iwA5/Tng
From: john.loughney@nokia.com
To: stiemerling@netlab.nec.de, bless@tm.uka.de
X-OriginalArrivalTime: 09 Jun 2006 13:22:28.0359 (UTC) FILETIME=[C1400970:01C68BC7]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: nsis@ietf.org
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

>>> There is still a not completely solved issue back from the old days
>>> (2004) about NSLP versioning. It is about wether an NSLP can have 
>>> multiple versions or not.
>>
>> I would say yes, naturally it can. The question is probably what can 
>> be considered as an appropriate demultiplexer.
>> So what is the issue exactly? Whether there should be an 
>NSLP version 
>> field in the NSLP protocol itself? The current alternative 
>is to use a 
>> different NSLP ID for each version, thus using the NSLP ID 
>in GIST as 
>> demultiplexing value. Since the NSLP ID is 16bit I guess that there 
>> are no issues here. So as long as we assume GIST as underlying 
>> transport (or some other protocol at least carrying session ID, MRM, 
>> NSLPID and so on) there is no problem here. There is only trouble if 
>> all you have is the NSLP data packet alone.
>
>The issue here is whether an NSIS initiator should have the 
>ability to ask with a single request message for multiple, 
>different NSLP version.
>This would require a single general NSLP-ID per NSLP and a 
>version information with the NSLP itself.
>
>I do not know if this issue is solvable by now or if it should 
>be handled in the NSLP extensibility draft. Since we have only 
>a single version anyway of each NSLP.

Is there anyone requesting this feature, it sounds extremely messy to
actually get working.

John

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