The Tempest - A practical framework for network programmability

被引:50
作者
van der Merwe, JE [1 ]
Rooney, S [1 ]
Leslie, I [1 ]
Crosby, S [1 ]
机构
[1] Univ Cambridge, Comp Lab, Cambridge CB2 1TN, England
来源
IEEE NETWORK | 1998年 / 12卷 / 03期
关键词
D O I
10.1109/65.690958
中图分类号
TP3 [计算技术、计算机技术];
学科分类号
0812 ;
摘要
The Tempest framework provides a programmable network environment by allowing the dynamic introduction and modification of network services at two levels of granularity. First, the switchlet and associated virtual network concepts enable the safe introduction of alternative control architectures into an operational network. The timescales over which such new control architectures can be introduced might vary from, for example, a video conferencing specific control architecture, which is active only for the duration of the conference, to a new version of a general purpose control architecture, which might be active for several months or longer. Second, the Tempest Framework allows refinement of services at a finer level of granularity by means of the connection closure concept. In this case modification of services can be performed at an application-specific level. These attributes of the Tempest framework allows service providers to effectively become network operators for some well defined partition of the physical network. This enables them to take advantage of the knowledge they possess about how the network resources are to be used, by programming their own specially tailored control architecture. This, as our work with the Tempest shows, is a spur to creativity allowing many of the constraints imposed on operators and end users to be rethought and for new techniques to be quickly and safely introduced into working networks.
引用
收藏
页码:20 / 28
页数:9
相关论文
共 30 条
[1]   SWAN: A mobile multimedia wireless network [J].
Agrawal, P ;
Hyden, E ;
Krzyzanowski, P ;
Mishra, P ;
Srivastava, MB ;
Trotter, JA .
IEEE PERSONAL COMMUNICATIONS, 1996, 3 (02) :18-33
[2]  
Alexander D. S., 1997, Computer Communication Review, V27, P101, DOI 10.1145/263109.263149
[3]  
*ATM FOR, 1995, AFSIG0061000 ATM FOR
[4]  
*ATM FOR, 1996, AFPNNI0055000 ATM FO
[5]  
BATTOU A, 1996, T1A1396071 ATM FOGR
[6]  
BLOEM J, 1995, P TINA C MELB AUSTR
[7]  
CASE JD, 1990, 1577 RFC
[8]  
CHAN M, 1997, INTEGRATED NETWORK M, V5, P301
[9]  
CROSBY S, 1997, PEARL PROPOSAL EXPT
[10]  
DORASWAMY N, 1997, IMPLEMENTATION VIRTU