G. Karagiannis
G. Karagiannis has a total of 10 co-authors. Here are the top co-authors by number of shared publications:
A. Charny
2 shared publications- Michael Menth
University of Tübingen
2 shared publications - C. N. Höfer
University of Twente
1 shared publication - F. Huang
University of Twente M Menth University of Tuebingen T. Taylor Ed
1 shared publication - J. Veldhuizen
Netherlands Organisation for Applied Scientific Research - Information and Communication Technology (TNO-ICT), Delft, the Netherlands
1 shared publication - J. Zhang
University of Twente M Menth University of Tuebingen T. Taylor Ed
1 shared publication
Latest Publications
- Open Access
- 1 July 2012
- Published by RFC Editor
Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using three PCN marking states: notmarked, threshold-marked, and excess-traffic-marked. This behavior is known informally as the Controlled Load (CL) PCN-boundary-node behavior.
- 1 July 2012
- Published by RFC Editor
Open AccessPre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using three PCN marking states: notmarked, threshold-marked, and excess-traffic-marked. This behavior is known informally as the Controlled Load (CL) PCN-boundary-node behavior.
- Open Access
- 1 July 2012
- Published by RFC Editor
Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: notmarked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior.
- 1 July 2012
- Published by RFC Editor
Open AccessPre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: notmarked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior.
- 29 September 2011
- Published by Springer Nature
- p. 355-359
Support for Resilient Communications in Future Disaster Management
- 29 September 2011
- Published by Springer Nature
- p. 355-359
Support for Resilient Communications in Future Disaster Management
- Open Access
- 19 June 2011
- Published by Sociedade Brasileira de Computação in Journal of Internet Services and Applications
- Vol. 2 (2) , 81-94
Cloud computing services: taxonomy and comparison
Cloud computing is a highly discussed topic in the technical and economic world, and many of the big players of the software industry have entered the development of cloud services. Several companies what to explore the possibilities and benefits of incorporating such cloud computing services in their business, as well as the possibilities to offer own cloud services. However, with the amount of cloud computing services increasing quickly, the need for a taxonomy framework rises. This paper examines the available cloud computing services and identifies and explains their main characteristics. Next, this paper organizes these characteristics and proposes a tree-structured taxonomy. This taxonomy allows quick classifications of the different cloud computing services and makes it easier to compare them. Based on existing taxonomies, this taxonomy provides more detailed characteristics and hierarchies. Additionally, the taxonomy offers a common terminology and baseline information for easy communication. Finally, the taxonomy is explained and verified using existing cloud services as examples.
- 19 June 2011
- Published by Sociedade Brasileira de Computação in Journal of Internet Services and Applications
- Vol. 2 (2) , 81-94
Open AccessCloud computing services: taxonomy and comparison
Cloud computing is a highly discussed topic in the technical and economic world, and many of the big players of the software industry have entered the development of cloud services. Several companies what to explore the possibilities and benefits of incorporating such cloud computing services in their business, as well as the possibilities to offer own cloud services. However, with the amount of cloud computing services increasing quickly, the need for a taxonomy framework rises. This paper examines the available cloud computing services and identifies and explains their main characteristics. Next, this paper organizes these characteristics and proposes a tree-structured taxonomy. This taxonomy allows quick classifications of the different cloud computing services and makes it easier to compare them. Based on existing taxonomies, this taxonomy provides more detailed characteristics and hierarchies. Additionally, the taxonomy offers a common terminology and baseline information for easy communication. Finally, the taxonomy is explained and verified using existing cloud services as examples.
- 1 November 2007
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21660077,p. 1-6
AAA architectures applied in multi-domain IMS (IP Multimedia Subsystem)
There is a group of communication services that use resources from multiple domains in order to deliver their service. Authorization of the end-user is important for such services, because several domains are involved. There are no current solutions for delivering authentication, authorization and accounting (AAA) to multi-domain services. In our study we present two architectures for the delivery of AAA to such services. The architectures are analyzed on their qualitative aspects. A result of this analysis is that direct interconnection of AAA servers is an effective architectural solution. In current multi-domain IP Multimedia Subsystem (IMS) architectures, direct interconnection of AAA servers, such as the Home Subscriber Servers (HSS), is not yet possible. In this paper we argue and recommend to extend the IMS specification by adding a new interface to HSS in order to support the direct interconnection of HSS/AAA servers located in different IMS administrative domains.
- 1 November 2007
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 21660077,p. 1-6
AAA architectures applied in multi-domain IMS (IP Multimedia Subsystem)
There is a group of communication services that use resources from multiple domains in order to deliver their service. Authorization of the end-user is important for such services, because several domains are involved. There are no current solutions for delivering authentication, authorization and accounting (AAA) to multi-domain services. In our study we present two architectures for the delivery of AAA to such services. The architectures are analyzed on their qualitative aspects. A result of this analysis is that direct interconnection of AAA servers is an effective architectural solution. In current multi-domain IP Multimedia Subsystem (IMS) architectures, direct interconnection of AAA servers, such as the Home Subscriber Servers (HSS), is not yet possible. In this paper we argue and recommend to extend the IMS specification by adding a new interface to HSS in order to support the direct interconnection of HSS/AAA servers located in different IMS administrative domains.