Skip to main content

SOCKS V5 UDP and Multicast Extensions to Facilitate Multicast Firewall Traversal
draft-ietf-aft-mcast-fw-traversal-01

Document Type Expired Internet-Draft (aft WG)
Expired & archived
Author David Chouinard
Last updated 1997-11-18
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This proposal creates a mechanism for managing the ingress or egress of IP multicast through a firewall. It does this by defining extensions to the existing SOCKS V5 protocol [RFC-1928], which provides a framework for doing user-level, authenticated firewall traversal of unicast TCP and UDP traffic. However, because the current UDP support in SOCKS V5 has scalability problems as well as other deficiencies -- and these need to be addressed before multicast support can be achieved -- the extensions are defined in two parts: Base-level UDP extensions, and Multicast UDP extensions. Using the SOCKS framework for managing multicast flows in/out of an organization, offers numerous security advantages over what is possible with a conventional firewall approach. These are spelled out in the draft.

Authors

David Chouinard

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)