RE: [NSIS] Draft on NSIS Operation Over IP Tunnels
"Charles Shen" <charles@cs.columbia.edu> Sun, 31 July 2005 16:31 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DzGjG-0007Rn-CH; Sun, 31 Jul 2005 12:31:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DzGjF-0007Ri-7x for nsis@megatron.ietf.org; Sun, 31 Jul 2005 12:31:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05847 for <nsis@ietf.org>; Sun, 31 Jul 2005 12:31:54 -0400 (EDT)
Received: from jalapeno.cc.columbia.edu ([128.59.29.5] ident=cu41754) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DzHFK-0003C9-RQ for nsis@ietf.org; Sun, 31 Jul 2005 13:05:08 -0400
Received: from ccs (dhcp-65-162.ee.columbia.edu [128.59.65.162]) (user=qs2005 mech=LOGIN bits=0) by jalapeno.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j6VGVp8O026753 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 31 Jul 2005 12:31:52 -0400 (EDT)
From: Charles Shen <charles@cs.columbia.edu>
To: john.loughney@nokia.com, nsis@ietf.org
Subject: RE: [NSIS] Draft on NSIS Operation Over IP Tunnels
Date: Sun, 31 Jul 2005 12:31:46 -0400
Organization: Columbia University
Message-ID: <000001c595ed$580cf880$a2413b80@ccs>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
In-Reply-To: <1AA39B75171A7144A73216AED1D7478D6CEA61@esebe100.NOE.Nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.5
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: quoted-printable
Cc:
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>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org
Hi John, > -----Original Message----- > From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] > Sent: Saturday, July 30, 2005 5:09 AM > To: charles@cs.columbia.edu; nsis@ietf.org > Subject: RE: [NSIS] Draft on NSIS Operation Over IP Tunnels > > > Hi Charles, > > Thanks for the draft, I think this is quite a useful > analysis. Thank you very much. > As tunneling, like multihoming, can be related to > mobility, I wonder if the analysis could go into the Mobility > Applicability Statement document. > Yes some analysis could go to the Mobility Applicability document since mobility (e.g. Mobile IP) makes use of tunneling. It also seems to be true that tunneling itself does not need to be tied with mobility. So I am not sure whether the topic itself deserves a separate document. (Indeed RFC2746 RSVP over IP tunnel is a separate one). On the other hand, I am not sure whether the scope of the Mobility Applicability Statement document would cover specific solutions. If the NSIS operation over tunnel draft describes a specific solution (like RFC2746) would it still be appropriate to be included in the Mobility Applicability Statement document? The current version of the draft is intended to focus on more generic aspects of NSIS tunneling, without explicit description of mobility. We are also working on applying this general scheme in the NSIS mobility environment, which I think is probably a good part of the Mobility Applicability Statement document. > After that, for the BOUND_FLOW_SESSION object, do you think > that this would be a general object for all NSLPs that might > run over a tunnel? One option would be to add this to the > existing NSLPs, or to write a very short document registering > this as a NSLP object in the NSIS IANA registry (when there is one). > I tend to favor having a general intra-session binding object for all NSLPs. In fact we might also have the same question for inter-session binding. Thanks. Charles > What does the rest of the wg think? > > thanks, > John > > > -----Original Message----- > > From: nsis-bounces@ietf.org > [mailto:nsis-bounces@ietf.org]On Behalf Of > > ext Charles Shen > > Sent: 14 July, 2005 07:45 > > To: nsis@ietf.org > > Subject: [NSIS] Draft on NSIS Operation Over IP Tunnels > > > > > > Dear all, > > > > We've submitted a draft on "NSIS Operation Over IP Tunnels". > > The abstract is > > as follows: > > > > In this draft we briefly review various IP Tunnelling > > mechanisms and > > discuss the main problems with signaling operation over > IP tunnels. > > We also summarize the existing RSVP operation over IP tunnels > > mechanism. Then we present the design details and case > examples of > > an NSIS operation over IP tunnels scheme. QoS NSLP is > > assumed as the > > NSIS signaling application in our discussion. > > > > The document is available at > > > > http://www.ietf.org/internet-drafts/draft-shen-nsis-tunnel-00.txt > > > > Any comments are greatly appreciated! > > > > Best regards, > > > > Charles > > > > > > > > _______________________________________________ > > 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
- RE: [NSIS] Draft on NSIS Operation Over IP Tunnels john.loughney
- RE: [NSIS] Draft on NSIS Operation Over IP Tunnels Hancock, Robert
- RE: [NSIS] Draft on NSIS Operation Over IP Tunnels Charles Shen
- RE: [NSIS] Draft on NSIS Operation Over IP Tunnels Charles Shen
- RE: [NSIS] Draft on NSIS Operation Over IP Tunnels Cheng Hong