RE: [NSIS] Session in NSIS

"Elena Scialpi" <scel@inwind.it> Thu, 19 February 2004 14:17 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 JAA19449 for <nsis-archive@odin.ietf.org>; Thu, 19 Feb 2004 09:17:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AtozD-0000Fr-MU for nsis-archive@odin.ietf.org; Thu, 19 Feb 2004 09:17:07 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1JEH7gs000978 for nsis-archive@odin.ietf.org; Thu, 19 Feb 2004 09:17:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atoz8-0000Ed-Av; Thu, 19 Feb 2004 09:17:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Atoya-0000CD-Qx for nsis@optimus.ietf.org; Thu, 19 Feb 2004 09:16:28 -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 JAA19392 for <nsis@ietf.org>; Thu, 19 Feb 2004 09:16:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AtoyY-0006Vf-00 for nsis@ietf.org; Thu, 19 Feb 2004 09:16:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Atoxc-0006Qg-00 for nsis@ietf.org; Thu, 19 Feb 2004 09:15:29 -0500
Received: from smtp2.libero.it ([193.70.192.52]) by ietf-mx with esmtp (Exim 4.12) id 1Atox0-0006Ku-00 for nsis@ietf.org; Thu, 19 Feb 2004 09:14:50 -0500
Received: from libero.it (193.70.192.38) by smtp2.libero.it (7.0.020-DD01) id 3F6F0DA001282680; Thu, 19 Feb 2004 15:14:49 +0100
Date: Thu, 19 Feb 2004 15:14:07 +0100
Message-Id: <HTC4VJ$915EC914D727A6C75EE1654DB186F30E@libero.it>
Subject: RE: [NSIS] Session in NSIS
MIME-Version: 1.0
X-Sensitivity: 3
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
From: Elena Scialpi <scel@inwind.it>
To: "hannes.tschofenig" <hannes.tschofenig@siemens.com>, nsis <nsis@ietf.org>
X-XaM3-API-Version: 4.1 (B27)
X-type: 0
X-SenderIP: 193.204.86.168
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: quoted-printable
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: quoted-printable

---------- Initial Header -----------

From      : nsis-admin@ietf.org
To          : "Elena Scialpi" scel@inwind.it,"nsis" nsis@ietf.org
Cc          : 
Date      : Thu, 19 Feb 2004 13:01:40 +0100
Subject : RE: [NSIS] Session in NSIS

> hi elena, 
> 
> in nsis the concept of a session is separated from the flow identifier. the
> advantage of this approach is also visible in many of the nsis mobility
> drafts. you can find the latest version (a merge of previous drafts) at:
> http://www.tschofenig.com/drafts/draft-manyfolks-signaling-protocol-mobility
> -00.txt
> 
> you might also want to take a look at :
> http://www.tschofenig.priv.at/drafts/draft-tschofenig-nsis-sid-00.txt
> 
> this draft describes alternative ways to create the session id with security
> properties.  
> 
> as a summary, the session id allows you to change the flow identfier
> - during the lifetime of a session (e.g., due to mobility, IPv6
> privacy,...),
> - somewhere along the path and 
> - to group different flows together
> 
> does this answer your question? 


I haven't understand very well the concept of session. 
I think that a session is between two specific nodes (sender and receiver of signaling)  while in 
RSVP it consider only one node.
Is it right?

Thanks for your reply,
Elena





> 
> ciao
> hannes
> 
> 
> > -----Original Message-----
> > From: Elena Scialpi [mailto:scel@inwind.it]
> > Sent: Thursday, February 19, 2004 12:15 PM
> > To: nsis
> > Subject: [NSIS] Session in NSIS
> > 
> > 
> > 
> > 
> > Hi all,
> > 
> > In RFC 2205 (http://ietf.org/rfc/rfc2205.txt?number=2205) a 
> > RSVP session is defined as "a data 
> > flow with a particular destination and transport-layer 
> > protocol" and it "is defined by the triple: 
> > (DestAddress, ProtocolId [, DstPort])"
> > 
> > NSIS framework 
> > (http://www.ietf.org/internet-drafts/draft-ietf-nsis-fw-05.txt
> > )  defines session as 
> > "application layer flow of information for which some network 
> > control state information is to be 
> > manipulated or monitored".
> > 
> > Session_ID is a random number but which parameters can be 
> > used to represent a session?
> > 
> > 
> > Regards,
> > Elena 
> > 
> > 
> > _______________________________________________
> > nsis mailing list
> > nsis@ietf.org
> > https://www1.ietf.org/mailman/listinfo/nsis
> > 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 


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