[NSIS] RE: Crossover node discovery issue
"Hancock, Robert" <robert.hancock@roke.co.uk> Fri, 29 August 2003 09:31 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03152 for <nsis-archive@odin.ietf.org>; Fri, 29 Aug 2003 05:31:56 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sfDy-0002Xw-GD for nsis-archive@odin.ietf.org; Fri, 29 Aug 2003 05:07:20 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7T97IpL009781 for nsis-archive@odin.ietf.org; Fri, 29 Aug 2003 05:07:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sf5y-0002Bz-Id; Fri, 29 Aug 2003 04:59:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sekb-0001BI-Dd for nsis@optimus.ietf.org; Fri, 29 Aug 2003 04:36:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28384 for <nsis@ietf.org>; Fri, 29 Aug 2003 04:36:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sekY-00059D-00 for nsis@ietf.org; Fri, 29 Aug 2003 04:36:54 -0400
Received: from rsys002a.roke.co.uk ([193.118.192.251]) by ietf-mx with esmtp (Exim 4.12) id 19sekX-00058T-00 for nsis@ietf.org; Fri, 29 Aug 2003 04:36:53 -0400
Received: by rsys002a.roke.co.uk with Internet Mail Service (5.5.2653.19) id <Q9Z6Z85H>; Fri, 29 Aug 2003 09:36:19 +0100
Message-ID: <EA943CD30BCB104E9D38F5B5DC2D9A708AC069@rsys004a.roke.co.uk>
From: "Hancock, Robert" <robert.hancock@roke.co.uk>
To: Seong Ho Jeong <shjeong@hufs.ac.kr>
Cc: nsis@ietf.org, Sung Hycuk Lee <starsu@sait.samsung.co.kr>, jh0278.bang@samsung.com, bj33.lee@samsung.com
Date: Fri, 29 Aug 2003 09:36:20 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="utf-8"
Subject: [NSIS] RE: Crossover node discovery issue
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>
hi Seong Jeong, thanks for the comment and apologies for the slow response. in the framework document, i would prefer to look purely at a definition of what the crossover router is rather than mechanisms for how to discover it (which would be more of a protocol issue). i think my current definition of x-over router would be: the NSLP aware node which, for a given session id, has one neighbour NE in one direction but two neighbour NEs in the other, and this situation may be transient (re-routing case) or long-term (multihoming case). this would probably require more wordsmithing. on the security issues, i think these are important to discuss, but at the moment I think they are more signalling application specific than NSIS generic so all we can do is talk generally. what I would really like to see is some discussion on this list of hannes' draft on the issue, http://www.ietf.org/internet-drafts/draft-tschofenig-nsis-sid-00.txt (which is very short and easy to read!) cheers, robert h. > -----Original Message----- > From: Seong Ho Jeong [mailto:shjeong@hufs.ac.kr] > Sent: Thursday, August 07, 2003 05:20 > To: Hancock, Robert > Cc: nsis@ietf.org; Sung Hycuk Lee; jh0278.bang@samsung.com; > bj33.lee@samsung.com > Subject: Crossover node discovery issue > > > Hi Robert, > > In Section 5.2.2 (Localized Path Repair) of the framework document, > I think it would be good to give a general description of how > to discover the > crossover node in a little more detail. For example, as > discussed before, a session ID, > a flow ID, and/or a mobility object can be used for the > crossover node discovery. > In this case, we may also need to check whether or not the > use of those fields is > sufficient because some sort of authorization and > determination of session ownership may be > necessary...How about adding a general description of the > crossover node discovery > and related security issues to the framework document? > > Regards, > > Seong Jeong > _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] RE: Crossover node discovery issue Hancock, Robert
- RE: [NSIS] RE: Crossover node discovery issue Hancock, Robert
- Re: [NSIS] RE: Crossover node discovery issue Jukka MJ Manner
- RE: [NSIS] RE: Crossover node discovery issue Charles Q. Shen
- Re: [NSIS] RE: Crossover node discovery issue Xiaoming Fu