ABSTRACT
Many residential and small business users connect to the Internet via home gateways, such as DSL and cable modems. The characteristics of these devices heavily influence the quality and performance of the Internet service that these users receive. Anecdotal evidence suggests that an extremely diverse set of behaviors exists in the deployed base, forcing application developers to design for the lowest common denominator. This paper experimentally analyzes some characteristics of a substantial number of different home gateways: binding timeouts, queuing delays, throughput, protocol support and others.
- J. Åhlund and P. Wallström. DNSSEC Tests of Consumer Broadband Routers. Technical Report, .SE Internet Infrastructure Foundation, Feb. 2008.Google Scholar
- R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. RFC 4033 (Proposed Standard), Mar. 2005.Google Scholar
- F. Audet and C. Jennings. Network Address Translation (NAT) Behavioral Requirements for Unicast UDP. RFC 4787 (Best Current Practice), Jan. 2007.Google Scholar
- R. Bellis. DNS Proxy Implementation Guidelines. RFC 5625 (Best Current Practice), Aug. 2009.Google Scholar
- R. Bellis and L. Phifer. Test Report: DNSSEC Impact on Broadband Routers and Firewalls. Technical Report, Nominet, Sept. 2008.Google Scholar
- R. Braden. Requirements for Internet Hosts - Communication Layers. RFC 1122 (Standard), Oct. 1989.Google Scholar
- L. D'Acunto, J. Pouwelse, and H. Sips. A Measurement of NAT & Firewall Characteristics in Peer to Peer Systems. In Proc. ASCI Conference, 2009.Google Scholar
- S. Deering and R. Hinden. Internet Protocol, Version 6 (IPv6) Specification. RFC 2460 (Draft Standard), Dec. 1998.Google Scholar
- T. Dietrich. DNSSEC Support by Home Routers in Germany. In Proc. 60th Réseaux IP Européens (RIPE) Meeting, May 2010.Google Scholar
- B. Ford, P. Srisuresh, and D. Kegel. Peer-to-Peer Communication Across Network Address Translators. In Proc. USENIX Annual Technical Conference, pages 13--13, 2005. Google Scholar
Digital Library
- S. Guha, K. Biswas, B. Ford, S. Sivakumar, and P. Srisuresh. NAT Behavioral Requirements for TCP. RFC 5382 (Best Current Practice), Oct. 2008.Google Scholar
- S. Guha and P. Francis. Characterization and Measurement of TCP Traversal through NATs and Firewalls. In Proc. ACM SIGCOMM IMC, pages 199--211, 2005. Google Scholar
Digital Library
- H. Haverinen, J. Siren, and P. Eronen. Energy Consumption of Always-On Applications in WCDMA Networks. In Proc. IEEE Vehicular Technology Conference, pages 964--968, Apr. 2007.Google Scholar
Cross Ref
- C. Jennings. NAT Classification Test Results. Internet-Draft draft-jennings-behave-test-results-04, Internet Engineering Task Force, July 2007. Work in Progress.Google Scholar
- E. Kohler, M. Handley, and S. Floyd. Datagram Congestion Control Protocol (DCCP). RFC 4340 (Proposed Standard), Mar. 2006.Google Scholar
- E. Kohler, M. Handley, and S. Floyd. Designing DCCP: Congestion Control Without Reliability. ACM SIGCOMM CCR, 36(4):27--38, 2006. Google Scholar
Digital Library
- K. Lahey. TCP Problems with Path MTU Discovery. RFC 2923 (Informational), Sept. 2000.Google Scholar
- R. Mahy, P. Matthews, and J. Rosenberg. Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN). RFC 5766 (Proposed Standard), Apr. 2010.Google Scholar
- L. Mäkinen and J. Nurminen. Measurements on the Feasibility of TCP NAT Traversal in Cellular Networks. In Proc. Conference on Next Generation Internet Networks, pages 261--267, 2008.Google Scholar
Cross Ref
- M. Mathis, J. Mahdavi, S. Floyd, and A. Romanow. TCP Selective Acknowledgment Options. RFC 2018 (Proposed Standard), Oct. 1996.Google Scholar
Digital Library
- A. Medina, M. Allman, and S. Floyd. Measuring the Evolution of Transport Protocols in the Internet. ACM SIGCOMM CCR, 35(2):37--52, 2005. Google Scholar
Digital Library
- J. Mogul and S. Deering. Path MTU Discovery. RFC 1191 (Draft Standard), Nov. 1990.Google Scholar
- J. Postel. Internet Control Message Protocol. RFC 792 (Standard), Sept. 1981.Google Scholar
- K. Ramakrishnan, S. Floyd, and D. Black. The Addition of Explicit Congestion Notification (ECN) to IP. RFC 3168 (Proposed Standard), Sept. 2001.Google Scholar
- Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, and E. Lear. Address Allocation for Private Internets. RFC 1918 (Best Current Practice), Feb. 1996.Google Scholar
Digital Library
- J. Rosenberg. Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols. RFC 5245 (Proposed Standard), Apr. 2010.Google Scholar
- J. Rosenberg, R. Mahy, P. Matthews, and D. Wing. Session Traversal Utilities for NAT (STUN). RFC 5389 (Proposed Standard), Oct. 2008.Google Scholar
- J. Rosenberg, J. Weinberger, C. Huitema, and R. Mahy. STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs). RFC 3489 (Proposed Standard), Mar. 2003.Google Scholar
- P. Srisuresh, B. Ford, S. Sivakumar, and S. Guha. NAT Behavioral Requirements for ICMP. RFC 5508 (Best Current Practice), Apr. 2009.Google Scholar
- R. Stewart. Stream Control Transmission Protocol. RFC 4960 (Proposed Standard), Sept. 2007.Google Scholar
Index Terms
- An experimental study of home gateway characteristics
Recommendations
Mapping home-network appliances to TCP/IP sockets using a three-tiered home gateway architecture
A three-tier gateway architecture for internetworking between home automation networks and a TCP/IP based wide area network, such as the Internet, is described. The architecture abstracts the functionality of any home network into a driver layer (tier ...
Remote management of non-TR-069 UPnP end-user devices in a private network
CCNC'09: Proceedings of the 6th IEEE Conference on Consumer Communications and Networking ConferenceEnd-to-end broadband service delivery requires remote management of devices in the home network, beyond the home gateway (HG). The service provider can only put limited requirements to these of-the-shelf devices, and therefore has to make intelligent ...
Home gateway architecture and its implementation
We propose a home network architecture, which integrates heterogeneous home network environments. Our architecture incorporates various home network technologies into the gateway technology. We use link-layer dependent protocols within a single network ...





Comments