[NSIS] Point 2: dictates that encapsulation of the original initiator QSPEC ...

<john.loughney@nokia.com> Fri, 05 January 2007 12:58 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2oeB-0005Rn-Qt; Fri, 05 Jan 2007 07:58:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H2oeB-0005Re-4D for nsis@ietf.org; Fri, 05 Jan 2007 07:58:11 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2oe9-0007Vz-In for nsis@ietf.org; Fri, 05 Jan 2007 07:58:11 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l05CuRhf017223; Fri, 5 Jan 2007 14:56:27 +0200
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jan 2007 14:57:44 +0200
Received: from esebe199.NOE.Nokia.com ([172.21.138.143]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 5 Jan 2007 14:57:43 +0200
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
Date: Fri, 05 Jan 2007 14:57:43 +0200
Message-ID: <BAA65A575825454CBB0103267553FCCC01B49198@esebe199.NOE.Nokia.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0DDC8091@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Point 2: dictates that encapsulation of the original initiator QSPEC ...
Thread-Index: AccnNAmV02JEI4mYSJ2rqx7HFPHiiwIEzvwgADBavYAAL/pCsA==
From: john.loughney@nokia.com
To: gash@att.com, nsis@ietf.org
X-OriginalArrivalTime: 05 Jan 2007 12:57:43.0862 (UTC) FILETIME=[172B4560:01C730C9]
X-eXpurgate-Category: 1/0
X-eXpurgate-ID: 149371::070105145627-42995BB0-28C1462B/0-0/0-0
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc:
Subject: [NSIS] Point 2: dictates that encapsulation of the original initiator QSPEC ...
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

>> Point_2: dictates that encapsulation of the original initiator QSPEC 
>> feature cannot be used in combination with the tunneling (parallel
>> session) feature.
>> 
>> In the discussion that we have had in the nsis mailing list and
during 
>> the IETF meeting it was stated that both these features should be 
>> possible, while now version 13 of the QSPEC template draft dictates 
>> that these two features cannot be used together and at the same time 
>> by the same QoS model.
>> As I mentioned in all the discussions the encapsulation of the 
>> original QSPEC feature is needed to satisfy Requirement:
>> "5.4.2.  It SHOULD be Possible to Add and Remove Local Domain 
>> Information" given in: http://www.ietf.org/rfc/rfc3726.txt
>> Therefore the encapsulation (of the original initiator QSPEC into a
local
>> QSPEC) feature should be seen as an independent feature and it should

>> be able to be used in combination with the tunneling (parallel 
>> session) feature that is used for another goal.
>> 
>> Thus my proposal is that it should be mentioned that even when the 
>> tunneling (parallel session) feature is used, it is also allowed to 
>> use, at the same time, the encapsulation (of the original initiator 
>> QSPEC into a local QSPEC) feature in order to satisfy Requirement
>> 5.4.2 of RFC
>> 3726.
>
>I don't see a reason to preclude using, at the same time, both 
>1. tunneling a QSPEC through a local domain by initiating a 
>new RESERVE at the domain edge, AND 2. defining a local QSPEC 
>and encapsulating the initiator QSPEC, as defined in Section 
>5.1 of the QSPEC draft 
>http://ietf.org/internet-drafts/draft-ietf-nsis-qspec-13.txt.
>
>Georgios provided an example based on the RMD-QOSM of when it 
>would be necessary to use both features at the same time.  I 
>think we're in agreement here.


I agree as well.

John

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