Browse Prior Art Database

Data Link Switching Remote Access Protocol (RFC2106)

IP.com Disclosure Number: IPCOM000002660D
Original Publication Date: 1997-Feb-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 19 page(s) / 21K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Chiang: AUTHOR [+2]

Related Documents

10.17487/RFC2106: DOI

Abstract

This memo describes the Data Link Switching Remote Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group S. Chiang Request for Comments: 2106 J. Lee Category: Informational Cisco Systems, Inc. H. Yasuda Mitsubishi Electric Corp. February 1997

Data Link Switching Remote Access Protocol

Status of this Memo

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Abstract

This memo describes the Data Link Switching Remote Access Protocol that is used between workstations and routers to transport SNA/ NetBIOS traffic over TCP sessions. Any questions or comments should be sent to drap@cisco.com.

1. Introduction

Since the Data Link Switching Protocol, RFC 1795, was published, some software vendors have begun implementing DLSw on workstations. The implementation of DLSw on a large number of workstations raises several important issues that must be addressed. Scalability is the major concern. For example, the number of TCP sessions to the DLSw router increases in direct proportion to the number of workstations added. Another concern is efficiency. Since DLSw is a switch-to- switch protocol, it is not efficient when implemented on workstations.

DRAP addresses the above issues. It introduces a hierarchical structure to resolve the scalability problems. All workstations are clients to the router (server) rather than peers to the router. This creates a client/server model. It also provides a more efficient protocol between the workstation (client) and the router (server).

Chiang, et. al. Informational [Page 1]

RFC 2106 DLSRAP February 1997

2. Overview

2.1. DRAP Client/Server Model

+-----------+ +-----------+ +---------+ | Mainframe | | IP Router +- ppp -+ DLSw | +--+--------+ +-----+-----+ | Work | | | | Station | | | +---------+ +--+--+ +-------------+ | | FEP +- TR -+ DLSw Router +-- IP Backbone +-----+ +-------------+ | | | +-----------+ +---------+ | IP Router +- ppp -+ DLSw | +-----+-----+ | Work | | Station | +---------+

| DLSw Session | +-------------------------------+ Figure 2-1. Running DLSw on a large number of workstations creates a scalability problem.

Figure 2-1 shows a typical DLSw implementation on a workstation. The workstations are connected to the central site DLSw router over the IP network. As the network grows, scalability will become an issue as the number of TCP sessions increases due to the growing number of workstations.

Chiang, et. al. Informational [Page 2]

RFC 2106 DLSRAP February 1997

+-----------+ +-------+ +-----------+ | DLSw/DRAP | | DRAP | | Mainframe | | Router +- ppp -+ Client| +--+--------+ +-----+-----+ +-------+ | | | | +--+--+ +-------------+ | | FEP +- TR -+ DLSw Router +-- IP Backbone +-----+ +-------------+ | | | +-----------+ +-------+ | DLSw/DRAP | | DRAP | | Router +- ppp -+ Client| +-----+-----+ +-------+

| DLSw Session | | DRAP Session | +--------------+ +--------------+ Figure 2-2. DLSw Remote Access Protocol solves the scalability problem.

In a large network, DRAP addresses the scalab...

Processing...
Loading...