[Trigtran] mobile SCTP using TRIGTRAN
"Seok Joo Koh" <sjkoh@etri.re.kr> Tue, 04 March 2003 05:37 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24985 for <trigtran-archive@odin.ietf.org>; Tue, 4 Mar 2003 00:37:14 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h245lWZ26485 for trigtran-archive@odin.ietf.org; Tue, 4 Mar 2003 00:47:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h245lWp26482 for <trigtran-web-archive@optimus.ietf.org>; Tue, 4 Mar 2003 00:47:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24973 for <trigtran-web-archive@ietf.org>; Tue, 4 Mar 2003 00:36:43 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h245lOp26467; Tue, 4 Mar 2003 00:47:24 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h245kDp26400 for <trigtran@optimus.ietf.org>; Tue, 4 Mar 2003 00:46:13 -0500
Received: from cms1.etri.re.kr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24960 for <trigtran@ietf.org>; Tue, 4 Mar 2003 00:35:24 -0500 (EST)
Received: from LocalHost (sjkoh.etri.re.kr [129.254.112.15]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id GCGB7479; Tue, 4 Mar 2003 14:37:15 +0900
Message-ID: <009501c2e210$10d98480$0f70fe81@LocalHost>
From: Seok Joo Koh <sjkoh@etri.re.kr>
To: trigtran@ietf.org
Date: Tue, 04 Mar 2003 14:36:54 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Subject: [Trigtran] mobile SCTP using TRIGTRAN
Sender: trigtran-admin@ietf.org
Errors-To: trigtran-admin@ietf.org
X-BeenThere: trigtran@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=unsubscribe>
List-Id: Triggers for Transport <trigtran.ietf.org>
List-Post: <mailto:trigtran@ietf.org>
List-Help: <mailto:trigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/trigtran>, <mailto:trigtran-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Hi, everyone, My general impression on TRIGTRAN is as follows. Some L2 triggers, if defined, will also be very useful for SCTP (RFC 2960) as well as TCP/UDP. As you know, the SCTP multi-homing feature enables SCTP transport session to be used for seamless handover. Some reference materials associated with mobile SCTP are shown in http://www.ietf.org/internet-drafts/draft-sjkoh-mobile-sctp-handover-00.txt http://www.ietf.org/internet-drafts/draft-sjkoh-mobile-sctp-mobileip-00.txt More specifically, the L2 triggers in wireless networks can be used for the mobile SCTP host to add and delete new and old IP addresses to and from its SCTP association. Actually, the SCTP/IP handover performance will severely depend on whether any triggers can be supported or not in the network or systems. Such triggers may be generated within the host system or by a TRIGTRAN router. This requirement is similar to the case of Fast MIPv6. Accordingly, for each of the issues identified by the agenda of TRIGTRAN BOF, - is an end-to-end solution sufficient, or do we really need help from the network? => If network can inform the IP address change to host by using triggers, it will be helpful for speed-up of SCTP handover - are explicit messages required? => Yes. Trigtran router needs to indicate the L2 event signal - can we agree on the list of canonical triggers? - can these triggers be generated by subnetwork technologies? => L2 triggers will severely depend on the access technologies. - can we agree on a list of reasonable responses? - who would use TRIGTRAN notifications? (OMA, SIP, etc.)? => SCTP (transport layer) can also use the TRIGTRAN notification - who would implement a reasonable TRIGTRAN specification? => I guess, Mobile equipments (gateways and terminals) will do so. My conclusion is that the triggers will also be essential for realizing the seamless IP handover, regardless of FMIPv6 or mobile SCTP. Thanks, Seok Joo Koh _______________________________________________ Trigtran mailing list Trigtran@ietf.org https://www1.ietf.org/mailman/listinfo/trigtran
- [Trigtran] mobile SCTP using TRIGTRAN Seok Joo Koh