IETF Logo Mail Archive

RE: [NSIS] Proposed draft "Mobility Support in NSIS"

"Charles Q. Shen" <charles@ee.columbia.edu> Mon, 07 July 2003 00:10 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 UAA26345 for <nsis-archive@odin.ietf.org>; Sun, 6 Jul 2003 20:10:34 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZJa3-0006yB-DU for nsis-archive@odin.ietf.org; Sun, 06 Jul 2003 20:10:07 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h670A7Qa026785 for nsis-archive@odin.ietf.org; Sun, 6 Jul 2003 20:10:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZJZx-0006wz-LR; Sun, 06 Jul 2003 20:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZJZE-0006wV-S4 for nsis@optimus.ietf.org; Sun, 06 Jul 2003 20:09:16 -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 UAA26329 for <nsis@ietf.org>; Sun, 6 Jul 2003 20:09:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZJZC-0005fo-00 for nsis@ietf.org; Sun, 06 Jul 2003 20:09:14 -0400
Received: from dewberry.cc.columbia.edu ([128.59.59.68] ident=cu41754) by ietf-mx with esmtp (Exim 4.12) id 19ZJZC-0005fk-00 for nsis@ietf.org; Sun, 06 Jul 2003 20:09:14 -0400
Received: from president (dyn-fair-240-199.dyn.columbia.edu [160.39.240.199]) (user=qs2005 mech=LOGIN bits=0) by dewberry.cc.columbia.edu (8.12.8p1/8.12.8) with ESMTP id h6709EIQ003498 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <nsis@ietf.org>; Sun, 6 Jul 2003 20:09:14 -0400 (EDT)
From: "Charles Q. Shen" <charles@ee.columbia.edu>
To: nsis@ietf.org
Subject: RE: [NSIS] Proposed draft "Mobility Support in NSIS"
Date: Sun, 06 Jul 2003 20:09:11 -0400
Organization: Columbia University
Message-ID: <000201c3441b$fe941830$c7f027a0@president>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
Importance: Normal
In-Reply-To: <3F05804D.2040504@cs.uni-goettingen.de>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.32 (www . roaringpenguin . com / mimedefang)
Content-Transfer-Encoding: 7bit
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: 7bit

Hi,  

I think having such a draft discussing mobility issues with NSIS is
helpful and inline with the WG charter. I started a similar effort in an
earlier draft last July
http://www.ee.columbia.edu/~charles/publication/draft-shen-nsis-mobility
-fw-00.txt.  

Fu's draft incorporated some recent issues including NSLP/NTLP
interaction, Discovery, peer-to-peer addressing etc. It would be good to
elaborate those parts when they become clearer in the WG discussion. 

Disscussion of tunneling/non-optimized routing is also useful, but it
would be beneficial to refer to RFC2746 which provides a very good
example of solving tunneling issues in the case of RSVP. 

Some issues may also be grouped together. Basically there are cases of
sender mobility and receiver mobility (The protocol itself could be
either sender initiated or receiver initated). Handoff causes
appropriate signaling actions in three segments of the network: the
intact path, the new path and the obsoleted path. (This applies to both
optimized/non-optimized routing, and possibly involves tunneling.) The
handoff process would further impact subsequent regular soft-state
refresh which has to be considered.

Best regards,

Charles

---
Charles Q. Shen
Department of Electrical Engineering
Columbia University
Email: charles@ee.columbia.edu
Phone: +1 212 853 8475
http://www.ee.columbia.edu/~charles


-------- Original Message --------
Subject: [NSIS] Proposed draft "Mobility Support in NSIS"
Date: Sat, 28 Jun 2003 23:43:09 +0200
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
To: nsis@ietf.org

Hi all,

Here is a new Internet Draft that we propose as a problem statement and
proposed mechanisms to extend NSIS for mobility support:
http://www.ietf.org/internet-drafts/draft-fu-nsis-mobility-00.txt or
http://www.ietf.org/internet-drafts/draft-fu-nsis-mobility-00.pdf

Following previous work (Michael Thomas, Cedric Westphal/Hemant Chaskar,
Charles Shen, and many others), this Draft aims to provide an extensive
view on mobility support related issues that will be of broad general
use.

We welcome your comments. We are also especially interested in other
open issues and studying how they may be addressed by future versions of
the Draft.

Regards,
Xiaoming


_______________________________________________
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

v2.23.0 | Report a Bug | By Email