scispace - formally typeset
Search or ask a question

Showing papers by "Xiaoming Fu published in 2003"


Proceedings ArticleDOI
27 Mar 2003
TL;DR: A light-weight version of RSVP, RSVP Lite, is presented, which clearly separates the signaled data from signaling messages and removes the multicast capability from the mandatory components ofRSVP.
Abstract: RSVP is a reservation setup protocol designed specifically to support QoS signaling in the Internet. However, RSVP end-to-end signaled QoS for the Internet has not become a reality. Moreover, there are many other applications demanding different signaling services. The paper analyses the features of RSVP version 1 we believe to be essential, and its complexity due to QoS-oriented design and multicast support as an indispensable component in a signaling protocol, deriving the design principles to be covered in a more generic signaling protocol. Based on this analysis, we present a light-weight version of RSVP, RSVP Lite, which clearly separates the signaled data from signaling messages and removes the multicast capability from the mandatory components of RSVP. RSVP Lite is intended to be applicable to a wide range of networking environments, while providing the flexibility to serve for generic signaling purposes and incremental deployment in the Internet.

11 citations


07 Mar 2003
TL;DR: This document describes a client protocol that supports per-flo w resource reservation in both sender- and receiver-directed modes operation.
Abstract: Signaling resource reservations is one of the possible applications of the Cross-Application Signaling Protocol (CASP). This document describes a client protocol that supports per-flo w resource reservationin both sender- and receiver-directed modes operation.

10 citations


Proceedings ArticleDOI
27 Oct 2003
TL;DR: The paper presents the prototype implementation and performance evaluation of such a QoS-enabled micro-mobility scheme, which is called "QoS-conditionalized handoff", extended to support the basic mode of Hierarchical Mobile IPv6 as the underlying micro-Mobility mechanism.
Abstract: Future internetworks will include large numbers of portable devices moving among small, wireless cells. In order to support real-time applications, users demand seamless mobility and quality-of-service (QoS) provisioning. One approach towards a more flexible, customizable and scalable mobility architecture that also reduces signaling load and handoff latency results from the introduction of micro-mobility. Furthermore, by coupling QoS signaling and mobility management, QoS requirements can be negotiated without incurring significant additional signaling latency. The paper presents the prototype implementation and performance evaluation of such a QoS-enabled micro-mobility scheme, which is called "QoS-conditionalized handoff". We extended the Mobile IPv6 for Linux implementation to support the basic mode of Hierarchical Mobile IPv6 as the underlying micro-mobility mechanism. One problem that appeared during the implementation was the rather complex event handling in the mobile node; to enable a simple and generic way of event handling, a priority-based execution structure has been developed that can be easily adapted to various policies. Our experimental results show that by this QoS-conditionalized handoff scheme, QoS-enabled handoffs can be achieved with a small amount of introduced latency compared to Hierarchical Mobile IPv6, which is much less than that of Mobile IPv6. It is further observed that fewer packets were lost and registration latency could be much more decreased when mobility management in the mobile node takes advantage of a movement detection mechanism to expedite the QoS-conditionalized handoff procedure.

7 citations


Henning Schulzrinne1, Xiaoming Fu, C. Pampu, Siemens Ag, Cornelia Kappler 
01 Jan 2003
TL;DR: The Cross-Application Signaling Protocol (CASP) is presented, which is a general-purpose protocol for managing state information in network devices and is one of the promising protocol candidates for the IETF NSIS WG.
Abstract: Existing signaling solutions are insufficient in terms of inter-domain and out-of-path signaling, mobility support and inter-working with policy and security mechanisms. The paper presents the Cross-Application Signaling Protocol (CASP) which is a general-purpose protocol for managing state information in network devices. This technology independent signaling protocol can be used for inter- and intra-domain QoS signaling, the configuration of middleboxes, for collecting measurement data and any other application where state management is required. It relies on existing transport protocols and consists of a messaging layer and a client layer. The messaging layer is application independent and is responsible for routing, session establishment and feature negotiation. In contrast to this application independent component of CASP, the client layer is the application-dependent part. As an example for a client the paper describes the QoS Resource Allocation Client for CASP and discusses requirements for extending CASP to include interdomain signaling.. The discovery of next peers along the data path is handled by the Scout protocol, which is a specialized client protocol. Some of the basic mechanisms are derived from existing protocols. This way the design of this protocol relies on the experiences made in this area and is therefore one of the promising protocol candidates for the IETF NSIS WG.

6 citations


Proceedings ArticleDOI
20 Oct 2003
TL;DR: This paper gives an overview of the recent efforts underway on next steps in QoS signaling protocols, namely RSVP extensions with mobility support, QoS-conditionalized handoff protocol, the layered architecture RSVP lite and the cross-application signaling protocol (CASP).
Abstract: QoS signaling protocol is one of the key components in Internet QoS architectures to establish, maintain, and remove reservation states in network nodes. This paper gives an overview of the recent efforts underway on next steps in QoS signaling protocols, namely RSVP extensions with mobility support, QoS-conditionalized handoff protocol, the layered architecture RSVP lite and the cross-application signaling protocol (CASP). These efforts address main issues with existing approaches differently: modularity, complexity and mobility support, with a focus on protocol behaviors based on different design principles. The paper also provides pointers to standards effort towards general Internet signaling and other service-specific signaling protocols.

3 citations


Proceedings ArticleDOI
01 Jan 2003
TL;DR: This paper presents a generic signaling architecture, the cross-application signaling protocol (CASP) and describes how it supports efficient and secure signaling in IP mobility scenarios.
Abstract: Internet signaling protocols establish, maintain and remove state along the data path. Next-generation signaling protocols design must meet the scaling requirements imposed by the various tasks of the Internet signaling applications, such as resource reservation and middlebox configuration, and to meet the demand for general functionality in signaling protocols, including strong security, reliability, congestion control, support for various signaling purposes and message sizes, and efficient support for mobility. This paper presents a generic signaling architecture, the cross-application signaling protocol (CASP) and describes how it supports efficient and secure signaling in IP mobility scenarios. In this approach, the signaling functionality is splitted into two layers: a generic messaging layer which provides the generic functionality for message delivery, and a client layer consisting of a next-hop discovery client and any number of client protocols which perform the actual signaling tasks. The essential mechanisms required to support mobility are: (1) a session identifier uniquely selected by the initiator and effective discovery of the cross-over node; (2) a branch identifier incrementally assigned for the new branch and efficient release of state in the abandoned branch; (3) ensuring discovery messages are delivered exactly following the path that mobile IP packets are encapsulated; and (4) effective hop-by-hop authentication and re-authorization provided by the messaging layer, non hop-by-hop security for signaling clients and denial-of-service protection in the discovery client.

3 citations


01 Jan 2003
TL;DR: This document attempts to determine what the expected functionality is, how various problems can be solved and what implications are caused by certain design decisions.
Abstract: Mobility support was one of the shortcommings of RSVP and a number of proposals have been made in the past to improve various features. This document attempts to determine what the expected functionality is, how various problems can be solved and what implications are caused by certain design decisions.

2 citations