Skip to main content
Log in

Die Firewall-Problematik bei Voice over IP

The firewall problem of voice over IP

  • Originalarbeiten
  • Published:
e & i Elektrotechnik und Informationstechnik Aims and scope Submit manuscript

Zusammenfassung

Das Grundprinzip des Internets, intelligente Endgeräte über ein relativ einfaches Netz aus Routern zu verbinden, wurde durch die Einführung so genannter Middleboxen, z. B. Firewalls, durchbrochen. Diese, meist aus Sicherheitsgründen zwischen Clients und Servern eingefügten Netzelemente, bringen für die Voice over IP-Telefonie erhebliche Schwierigkeiten. Durch zusätzliche Protokolle, mit deren Hilfe die Middleboxen gesteuert werden können, lassen sich diese Probleme beherrschen. Dabei sind UPnP und MIDCOM zwei der wichtigsten Protokollansätze. Der Beitrag stellt die beiden Protokolle gegenüber und zeigt ihre Möglichkeiten im Zusammenhang mit VoIP auf.

Abstract

The basic principle of the Internet is to connect intelligent terminals via a relatively simple network made up of routers. This principle was broken by the introduction of so called middleboxes, e.g. firewalls. These network elements, mostly interconnected between clients and servers for security reasons, lead to many problems in the Voice over IP-telephony. Using additional protocols that control the middleboxes, these problems can be solved. UPnP and MIDCOM are two of the most important approaches. This article compares the two protocols and shows their potential in connection with VoIP.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Literatur

  • Barnes, M. (2002): Middlebox communication (MIDCOM) protocol evaluation. internet draft (expired May 2003). IETF.

  • Bartel, M., Boyer, J., Fox, B., LaMacchia, B., Simon, E. (2002): XML signature syntax and processing. W3C recommendation.

  • Cordell, P., MIDCOM WG. (2002): Span discussion issues. Internet draft (expired February 2003). IETF.

  • Dierks, T., Allen, C., (1999): The TLS protocol version 1.0. IETF RFC 2246.

  • Ellison, C. (2003a): UPnPTM security ceremonies. Design document. UPnP Forum.

  • Ellison, C. (2003b): SecurityConsole:1 service template. Standardized DCP. UPnP Forum.

  • Ellison, C. (2003c): DeviceSecurity :1 service template. Standardized DCP. UPnP Forum.

  • Gudgin, M., Hadley, M., Mendelsohn, N., Moreau, J.-J., Nielsen, H. F. (2003): SOAP version 1.2 part 1: Messaging framework. W3C recommendation.

  • Housley, R., Polk, W., Ford, W., Solo, D. (2002): Internet X.509 public key infrastructure certificate and certificate revocation (CRL) profile. IETF RFC 3280.

  • Imamura, T., Dillaway, B., Simon, E. (2002): XML encryption syntax and processing. W3C recommendation.

  • ITU-T (2000): X.509 “The directory: public-key andattribute certificate frameworks”.

  • ITU-T (2003): H.225.0v5 “Call signalling protocols and media stream packetization for packet-based multimedia communication systems”.

  • ITU-T (2003): H.323v5 “Packet-based Multimedia communications systems”.

  • Iyer, P., Warrier, U. (2001a): InternetGatewayDevice: 1 device template version 1.01. Standardized DCP. UPnP Forum.

  • Iyer, P., Warrier, U., Schmitz, M. (2001b): WANIPConnection:1 device template version 1.01. Standardized DCP. UPnP Forum.

  • Kent, S., Atkinson, R. (1998): Security architecture for the Internet protocol. IETF RFC 2401.

  • McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, J., Waldbusser, M., Waldbusser, S. (1999a): Structure of management information version 2 (SMIv2). IETF RFC 2578.

  • McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, J., Waldbusser, M., Waldbusser, S. (1999b): Textual conventions for SMIv2. IETF RFC 2579.

  • McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, J., Waldbusser, M., Waldbusser, S. (1999b): Conformance statements for SMIv2. IETF RFC 2580.

  • Quittek, J., Stiemerling, M., Srisuresh, P. (2004): Definitions of managed objects for middlebox communication. Internet draft (expires October 2004). IETF.

  • Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., Schooler, E. (2002): SIP: session initiation protocol. IETF RFC 3261.

  • Rosenberg, J., Weinberger, J., Huitema, C., Mahy, R. (2003): STUN — simple traversal of user datagram protocol (UDP) through network address translators (NATs). IETF RFC 3489.

  • Srisuresh, P., Holdrege, M. (1999): IP network address translator (NAT) Terminology and considerations. IETF RFC 2663.

  • Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A., Rayhan, A. (2002): Middlebox communication architecture and framework. IETF RFC 3303.

  • Stallings W. (1999): SNMP, SNMv2, SNMPv3, and RMON 1 and 2. 3rd ed. Massachusetts: Addison Wesley.

    Google Scholar 

  • Stiemerling, M., Quittek, J., Taylor, T. (2004): MIDCOM protocol semantics. Internet draft (expires July 2004). IETF.

  • Swale, R. P., Mart, P. A., Sijben, P., Brim, S., Shore, M. (2002): Middlebox communications (MIDCOM) protocol requirements. IETF RFC 3304.

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to F. Schüller Dipl.-Ing..

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Schüller, F., Höher, T. & Weisgrab, H. Die Firewall-Problematik bei Voice over IP. Elektrotech. Inftech. 122, 55–61 (2005). https://doi.org/10.1007/BF03054024

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF03054024

Schlüsselwörter

Keywords

Navigation