RFC1434 日本語訳
1434 Data Link Switching: Switch-to-Switch Protocol. R. Dixon, D.Kushi. March 1993. (Format: TXT=80182, PS=292006, PDF=181839 bytes) (Obsoleted by RFC1795) (Status: INFORMATIONAL)
プログラムでの自動翻訳です。
RFC一覧
英語原文
Network Working Group R. Dixon
Request for Comments: 1434 D. Kushi
IBM
March 1993
コメントを求めるワーキンググループR.ディクソン要求をネットワークでつないでください: 1434 1993年のD.Kushi IBMの行進
Data Link Switching: Switch-to-Switch Protocol
データは切り換えをリンクします: スイッチからスイッチへのプロトコル
Status of this Memo
このMemoの状態
This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.
このメモはインターネットコミュニティのための情報を提供します。 それはインターネット標準を指定しません。 このメモの分配は無制限です。
Abstract
要約
This RFC describes IBM's support of Data Link Switching over TCP/IP. The RFC is being distributed to members of the Internet community in order to solicit their reactions to the proposals contained in it. While the issues discussed may not be directly relevant to the research problems of the Internet, they may be interesting to a number of researchers and implementors.
このRFCはTCP/IPの上でIBMのData Link Switchingのサポートについて説明します。 RFCは、それに含まれた提案への彼らの反応に請求するためにインターネットコミュニティのメンバーに分配されています。 議論した問題が直接インターネットの研究課題に関連していないかもしれない間、多くの研究者と作成者にとって、それらはおもしろいかもしれません。
Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com.
このRFCのコンテンツに比例したどんな質問やコメントも以下のインターネット・アドレスに送るべきです: dlsw@ralvma.vnet.ibm.com 。
Table of Contents
目次
1. Introduction 2
2. Overview 2
3. Transport Connection 4
3.1. SSP Frame Formats 5
3.2. Address Parameters 8
3.3. Message Types 10
4. Protocol Specification 11
4.1. Protocol Flow Diagrams 11
4.1.1. Connect Protocols 11
4.1.2. Link Restart Protocols 13
4.1.3. Disconnect Protocols 15
4.2. DLS State Machine 16
4.2.1 Data Link Switch States 16
4.2.2 State Transition Tables 21
4.3. NetBIOS Datagrams 30
Acknowledgments 32
References 32
Security Considerations 32
Authors' Addresses 33
1. 序論2 2。 概要2 3。 接続4 3.1を輸送してください。 SSPは3.2に形式5を縁どっています。 パラメタ8が3.3であると扱ってください。 メッセージは4に10をタイプします。 仕様11 4.1について議定書の中で述べてください。 プロトコルフローチャート11 4.1.1。 .2にプロトコル11 4.1を接続してください。 再開プロトコル13 4.1.3をリンクしてください。 プロトコル15が4.2であると切断してください。 dlが、.1データ・リンクスイッチが4.2に.2個の状態遷移テーブル21 4.3に16を述べるとマシン16 4.2に述べます。 NetBIOSデータグラム30承認32参照32セキュリティ問題32作者のアドレス33
Dixon & Kushi [Page 1] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[1ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
1. Introduction
1. 序論
Data Link Switching (DLS) is a forwarding mechanism for the IBM SNA and IBM NetBIOS protocols. It does not provide full routing, but instead provides switching at the Data Link layer and encapsulation in TCP/IP for transport over the Internet. This memo documents the Switch-to-Switch Protocol (SSP) that is used between IBM 6611 Network Processors.
データLink Switching(DLS)はIBM SNAとIBM NetBIOSプロトコルのための推進メカニズムです。 それは、完全なルーティングを提供しませんが、代わりにインターネットの上の輸送のためにTCP/IPにおけるData Link層とカプセル化で切り替わりながら、提供されます。 このメモはSwitchからスイッチへのIBM6611Network Processorsの間で使用されるプロトコル(SSP)を記録します。
Today, the IBM 6611 supports SNA (PU 2 and PU 4) systems and NetBIOS systems attached to token-ring networks, as well as SNA (PU 2) systems attached to SDLC links. For the later case, the SDLC attached systems are provided with a LAN appearance within the IBM 6611. For the LAN attached systems, the IBM 6611 appears as a source-routing bridge. Remote systems that are accessed through the IBM 6611 appear as systems attached to an adjacent ring. This ring is a virtual ring that is manifested within each IBM 6611.
今日、IBM6611は、SNA(PU2とPU4)システムとNetBIOSがトークンリングネットワークに取り付けられたシステムであると、サポートします、SDLCリンクに取り付けられたSNA(PU2)システムと同様に。 後のケースにおいて、IBM6611の中でSDLC付属しているシステムにLAN外観を提供します。 LAN付属しているシステムに関しては、IBM6611はソースルーティングブリッジとして現れます。 システムが隣接しているリングに付いたので、IBM6611を通してアクセスされるリモートシステムは現れます。 このリングは各IBM6611の中に表される仮想リングです。
2. Overview
2. 概要
Data Link Switching was developed to provide support for SNA and NetBIOS in multi-protocol routers. Since SNA and NetBIOS are basically connection oriented protocols, the Data Link Control procedure that they use on the LAN is IEEE 802.2 Logical Link Control (LLC) Type 2. Data Link Switching also accommodates SNA protocols over WAN links via the SDLC protocol.
データLink Switchingは、SNAとNetBIOSのサポートをマルチプロトコルルータに提供するために開発されました。 SNAとNetBIOSが基本的に接続指向のプロトコルであるので、それらがLANで用いるData Link Control手順はIEEE802.2Logical Link Control(LLC)タイプ2です。 また、データLink SwitchingはWANリンクの上にSDLCプロトコルでSNAプロトコルを収容します。
IEEE 802.2 LLC Type 2 was designed with the assumption that the network transit delay would be small and predictable (i.e., a local LAN). Therefore the LLC elements of procedure use a fixed timer for detecting lost frames. When bridging is used over wide area lines (especially at lower speeds), the network delay is larger and it can vary greatly based upon congestion. When the delay exceeds the time-out value LLC attempts to retransmit. If the frame is not actually lost, only delayed, it is possible for the LLC Type 2 procedures to become confused. And as a result, the link is eventually taken down.
IEEE802.2LLC Type2はネットワークトランジット遅れが小さくて、予測できるだろうという仮定(すなわち、地方のLAN)で設計されました。 したがって、手順のLLC要素は、無くなっているフレームを検出するのに固定タイマを使用します。 ブリッジするのが広い領域線(特に下側の速度における)の上で使用されているとき、ネットワーク遅延は、より大きいです、そして、それは混雑に大いに基づいた状態で異なることができます。 遅れがタイムアウトを超えていると、値のLLCは、再送するのを試みます。 遅らせられるだけであって、フレームが実際になくされていないなら、LLC Type2手順が混乱するようになるのは、可能です。 そして、その結果、リンクは結局、降ろされます。
Given the use of LLC Type 2 services, Data Link Switching addresses the following bridging problems:
LLC Type2サービスの使用を考えて、Data Link Switchingは問題をブリッジしながら、以下を扱います:
DLC Time-outs
DLC Acknowledgments over the WAN
Flow and Congestion Control
Broadcast Control of Search Packets
Source-Route Bridging Hop Count Limits
ホップカウント限界をブリッジする検索パケット送信元経路の青白い流れと輻輳制御放送制御装置の上のDLCタイムアウトDLC承認
NetBIOS also makes extensive use of datagram services that use LLC
また、NetBIOSはLLCを使用するデータグラムサービスの大規模な使用をします。
Dixon & Kushi [Page 2] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[2ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Type 1. In this case, Data Link Switching addresses the last two problems in the above list.
1をタイプしてください。 この場合、Data Link Switchingは上記のリストにおける最後のその2つの問題を訴えます。
The principal difference between Data Link Switching and bridging is that DLS terminates the Data Link Control whereas bridging does not. The following figure illustrates this difference based upon two end systems operating with LLC Type 2 services.
Data Link Switchingとブリッジするところの主要な違いはDLSがData Link Controlを終えますが、ブリッジするのが終えるというわけではないということです。 以下の図はLLC Type2サービスで作動する2台のエンドシステムに基づくこの違いを例証します。
Bridging
-------- Bridge Bridge
+------+ +----+ +----+ +------+
| End | +---------+ | +-----/ | | +---------+ | End |
|System+-+ LAN +-+ | /------+ +-+ LAN +-+System|
| | +---------+ | | TCP/IP | | +---------+ | |
+------+ +----+ +----+ +------+
Info------------------------------------------------------->
<-------------------------------------------------------RR
ブリッジします。-------- ブリッジが+であるとブリッジしてください。------+ +----+ +----+ +------+ | 終わり| +---------+ | +-----/ | | +---------+ | 終わり| |システム++、LAN、++| /------+ ++LAN、++、システム| | | +---------+ | | TCP/IP| | +---------+ | | +------+ +----+ +----+ +------+ インフォメーション-------------------------------------------------------><。-------------------------------------------------------RR
Data Link Switching
-------------------
+------+ +----+ +----+ +------+
| End | +---------+ | +-----/ | | +---------+ | End |
|System+-+ LAN +-+DLS | /------+ DLS+-+ LAN +-+System|
| | +---------+ | | TCP/IP | | +---------+ | |
+------+ +----+ +----+ +------+
Info-------------------> -------------> Info
<-------------------RR ---------------->
<----------------RR
データ・リンクの切り換え------------------- +------+ +----+ +----+ +------+ | 終わり| +---------+ | +-----/ | | +---------+ | 終わり| |システム++、LAN、++、dl| /------+ dl++、LAN、++、システム| | | +---------+ | | TCP/IP| | +---------+ | | +------+ +----+ +----+ +------+ インフォメーション------------------->。------------->インフォメーション<。-------------------RR----------------><。----------------RR
Figure 1. Data Link Switching Contrasted to Bridging
図1。 ブリッジすることに対して対照されたデータ・リンクの切り換え
In traditional bridging, the Data Link Control is end-to-end. Data Link Switching terminates the LLC Type 2 connection at the switch. This means that the LLC Type 2 connections do not cross the wide area network. The DLS multiplexes LLC connections onto a TCP connection to another DLS. Therefore, the LLC connections at each end are totally independent of each other. It is the responsibility of the Data Link Switch to deliver frames that it has received from a LLC connection to the other end. TCP is used between the Data Link Switches to guarantee delivery of frames.
伝統的なブリッジするのに、Data Link Controlは終わらせる終わりです。 データLink SwitchingはスイッチでLLC Type2接続を終えます。 これは、LLC Type2接続が広域ネットワークを横断しないことを意味します。 DLSは別のDLSとのTCP接続にLLC接続を多重送信します。 したがって、各端のLLC接続は互いから完全に独立しています。 それがLLC接続からもう一方の端まで受けたフレームを提供するのは、Data Link Switchの責任です。 TCPは、フレームの配送を保証するのにData Link Switchesの間で使用されます。
As a result of this design, LLC time-outs are limited to the local LAN (i.e., they do not traverse the wide area). Also, the LLC Type 2 acknowledgments (RR's) do not traverse the WAN, thereby reducing traffic across the wide area links. For SDLC links, polling and poll response occurs locally, not over the WAN. Broadcast of search frames is controlled by the Data Link Switches once the location of a target system is discovered. Finally, the switches can now apply
このデザインの結果、LLCタイムアウトは地方のLANに制限されます(すなわち、それらは広い領域を横断しません)。 また、LLC Type2承認(RRのもの)はWANを横断して、その結果、広い領域のリンクの向こう側にトラフィックを減少させることがないです。 SDLCリンクに関しては、世論調査と投票応答はいずれのWANの上にも局所的に起こりません。 目標システムの位置がいったん発見されると、検索フレームの放送はData Link Switchesによって制御されます。 最終的に、現在、スイッチは適用できます。
Dixon & Kushi [Page 3] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[3ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
back pressure to the end systems to provide flow and congestion control.
エンドシステムに対する圧力を支持して、流れと輻輳制御を供給してください。
Data Link Switching uses LAN addressing to set up connections between SNA systems. SDLC attached devices are defined with MAC addresses to enable them to communicate with LAN attached devices. For NetBIOS systems, Data Link Switching uses the NetBIOS name to forward datagrams and to set up connections for NetBIOS sessions. For circuit establishment, SNA systems send TEST (or in some cases, XID) frames to the null (x'00') SAP. NetBIOS systems have an address resolution procedure, based upon the Name Query and Name Recognized frames, that is used to establish an end-to-end circuit.
データLink Switchingは、SNAシステムの間の接続をセットアップするのにLANアドレシングを使用します。SDLC付属しているデバイスはMACアドレスで定義されて、彼らがLANと付属デバイスを伝えるのを可能にします。 NetBIOSシステムのために、Data Link Switchingはデータグラムを進めて、NetBIOSセッションのために接続をセットアップするNetBIOS名を使用します。 回路設立のために、SNAシステムはヌル(x'00')のSAPへのフレームをTEST(または、いくつかの場合XID)に送ります。 NetBIOSシステムには、終わりから端への回路を証明するのに用いられるName QueryとName Recognizedフレームに基づくアドレス解決手順があります。
Since Data Link Switching may be implemented in multi-protocol routers, there may be situations where both bridging and switching are enabled. SNA frames can be identified by their link SAP. Typical SAP values for SNA are x'04', x'08', and x'0C'. NetBIOS always uses a link SAP value of x'F0'.
Data Link Switchingがマルチプロトコルルータで実装されるかもしれないので、状況がブリッジするのと切り換えの両方が可能にされるところにあるかもしれません。 それらのリンクSAPはSNAフレームを特定できます。 SNAのための典型的なSAP値は、'0C'x'04'と、x'08'と、xです。 'NetBIOSはいつもx'F0のリンクSAP価値を使用します'。
3. Transport Connection
3. 輸送接続
Data Link Switches can be in used in pairs or by themselves. A Single DLS internally switches one data link to another without using TCP (DLC(1) to DLC(2) in the figure below). A paired DLS multiplexes data links over a reliable transport using a Switch-to-Switch Protocol (SSP). This RFC will document the frame formats and protocols for this multiplexing between Data Link Switches. The initial implementation of SSP uses TCP as the reliable transport between Data Link Switches. However, other transport connections such as OSI TP4 could be used.
対になっている自分たちで使用されて、Link Switchesがいることができるデータ。 TCP(以下の図のDLC(2)へのDLC(1))を使用しないで、Single DLSは内部的に1個のデータ・リンクを別のものに切り換えます。 対にされたDLSは、Switchからスイッチへのプロトコル(SSP)を使用することで信頼できる輸送の上にデータ・リンクを多重送信します。 このRFCはData Link Switchesの間のこのマルチプレクシングのためにフレーム形式とプロトコルを記録するでしょう。 SSPの初期の実装はData Link Switchesの間の信頼できる輸送としてTCPを使用します。 しかしながら、OSI TP4などの他の輸送の接続を使用できました。
+-----------------------------------------------+Switch-to-Switch
| DLC Interfaces | Protocol (SSP)
|+------------+ DLC Request +------------+ |
|| Data |<---------------- | | |Send SSP Frame
|| Link | DLC Indication | | |-------------->
|| Control 1 |----------------->| | |
|+------------+ | Data Link | |
|+------------+ DLC Request | Switch | |
|| Data |<---------------- | | |Rec. SSP Frame
|| Link | DLC Indication | | |<-------------
|| Control 2 | ---------------->| | |
|+------------+ +------------+ |
| Multi-Protocol Router |
+-----------------------------------------------+
+-----------------------------------------------+ 切り換えるスイッチ| DLCインタフェース| プロトコル(SSP)|+------------+ DLC要求+------------+ | || データ| <、-、-、-、-、-、-、-、-、-、-、-、-、-、-、--、|、| |フレームをSSPに送ってください。|| リンク| DLC指示| | |-------------->|| コントロール1|、-、-、-、-、-、-、-、-、-、-、-、-、-、-、-、--、>|、|、| |+------------+ | データ・リンク| | |+------------+ DLC要求| スイッチ| | || データ| <、-、-、-、-、-、-、-、-、-、-、-、-、-、-、--、|、| |Rec。 SSPフレーム|| リンク| DLC指示| | | <、-、-、-、-、-、-、-、-、-、-、-、-- || コントロール2| ---------------->|、|、| |+------------+ +------------+ | | マルチプロトコルルータ| +-----------------------------------------------+
Figure 2. DLS System Diagram
図2。 dl系統図
Dixon & Kushi [Page 4] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[4ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Before Data Link Switching can occur between two routers, they must establish a TCP connection between them. Each DLS will maintain a list of DLS capable routers and their status (active/inactive). Once this connection is established, the DLS will employ SSP to establish end-to-end circuits over the transport connection. Within the transport connection is a specific set of DLS message units. The message formats and types for these PDUs are documented in the following sections.
Data Link Switchingが2つのルータの間に起こることができる前に、それらはそれらの間のTCP接続を確立しなければなりません。 各DLSは、DLSのリストができるルータとそれらの状態(アクティブであるか不活発な)であることを支持するでしょう。 この接続がいったん確立されると、DLSは、輸送接続の上で終わりから端への回路を証明するのにSSPを使うでしょう。 中では、輸送接続がDLSメッセージユニットの特定のセットです。 これらのPDUsのためのメッセージ・フォーマットとタイプは以下のセクションで記録されます。
The default parameters associated with the TCP connections between Data Link Switches are as follows:
Data Link Switchesの間のTCP接続に関連しているデフォルトパラメタは以下の通りです:
Socket Family AF_INET (Internet protocols)
Socket Type SOCK_STREAM (stream socket)
Read Port Number 2065
Write Port Number 2067
ソケットFamily AF_INET(インターネットプロトコル)ソケットType SOCK_STREAM(ストリームソケット)はPort Number2065Write Port Number2067を読みます。
Two or more Data Link Switches may be attached to the same LAN, consisting of a number of token-ring segments interconnected by source-routing bridges. In this case, a TCP connection is not defined between bridges attached to the same LAN. This will allow using systems to select one of the possible Data Link Switches in a similar manner to the selection of a bridge path through a source- routed bridged network. The virtual ring segment in each Data Link Switch attached to a common LAN must be configured with the same ring number. This will prevent LAN frames sent by one Data Link Switch from being propagated through the other Data Link Switches.
2Data Link Switchesが同じLANに取り付けられるかもしれません、ソースルーティングブリッジによってインタコネクトされた多くのトークンリングセグメントから成って。 この場合、TCP接続は同じLANに付けられたブリッジの間で定義されません。 これで、同じようにソースの発送されたブリッジしているネットワークを通したブリッジ経路の選択するのに可能なData Link Switchesの1つを選択するのにシステムを使用するでしょう。 同じリング番号で一般的なLANに取り付けられた各Data Link Switchの仮想リングセグメントを構成しなければなりません。 これは、1Data Link Switchによって送られたLANフレームが他のData Link Switchesを通して伝播されるのを防ぐでしょう。
3.1. SSP Frame Formats
3.1. SSPフレーム形式
The following diagrams show the two message headers for traffic between Data Link Switches. The control message header is used for all messages except information messages. The information message header is 16 bytes long, and the control message header is 72 bytes long. The first sixteen bytes of the control message header are identical to the information message header.
以下のダイヤグラムはData Link Switchesの間のトラフィックのために2個のメッセージヘッダーを示しています。 コントロールメッセージヘッダーは情報メッセージ以外のすべてのメッセージに使用されます。 情報メッセージヘッダーは16バイト長です、そして、コントロールメッセージヘッダーは72バイト長です。 情報メッセージヘッダーに、コントロールメッセージヘッダーの最初の16バイトは同じです。
Dixon & Kushi [Page 5] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[5ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
CONTROL MESSAGES (72 Bytes)
+-----------------------------------------------------------------+
| Version Number Reserved Field |
| Message Length ----> . |
| Remote Data Link Correlator ----> . |
| . . |
| Remote DLC Port ID ----> . |
| . . |
| Reserved Field ----> . |
| Message Type Reserved Field |
| Protocol ID Header Number |
| Header Length ----> . |
| Reserved Field ----> . |
| Reserved Field Message Type |
| Target MAC Address ----> . |
| . . |
| . . |
| Origin MAC Address ----> . |
| . . |
| . . |
| Origin Link SAP Target Link SAP |
| Frame Direction Reserved Field |
| Message Length ----> . |
| DLC Header Length ----> . |
| Origin DLC Port ID ----> . |
| . . |
| Origin Data Link Correlator ----> . |
| . . |
| Origin Transport ID ----> . |
| . . |
| Target DLC Port ID ----> . |
| . . |
| Target Data Link Correlator ----> . |
| . . |
| Target Transport ID ----> . |
| . . |
| Reserved Field ----> . |
| . . |
+-----------------------------------------------------------------+
(Even Byte) (Odd Byte)
コントロールメッセージ(72バイト)+-----------------------------------------------------------------+ | バージョンの数の予約された分野| | メッセージ長---->。| | リモートデータ・リンク相関器---->。| | . . | | 遠く離れたDLC Port ID---->。| | . . | | 予約された分野---->。| | メッセージのタイプの予約された分野| | プロトコルIDヘッダー番号| | ヘッダ長---->。| | 予約された分野---->。| | 控え目な分野メッセージタイプ| | 目標マックーアドレス---->。| | . . | | . . | | 発生源マックーアドレス---->。| | . . | | . . | | 発生源リンク体液目標リンクSAP| | 方向の予約された分野を縁どってください。| | メッセージ長---->。| | DLCヘッダ長---->。| | 発生源DLCポートID---->。| | . . | | 発生源データ・リンク相関器---->。| | . . | | 発生源輸送ID---->。| | . . | | 目標DLCはIDを移植します。---->。| | . . | | 目標データ・リンク相関器---->。| | . . | | Transport IDを狙ってください。---->。| | . . | | 予約された分野---->。| | . . | +-----------------------------------------------------------------+ (バイトさえ)(奇数バイト)
Dixon & Kushi [Page 6] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[6ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
INFORMATION MESSAGE (16 Bytes)
+-----------------------------------------------------------------+
| Version Reserved Field |
| Message Length ----> . |
| Remote Data Link Correlator ----> . |
| . . |
| Remote DLC Port ID ----> . |
| . . |
| Reserved Field ----> . |
| Message Type Reserved Field |
+-----------------------------------------------------------------+
(Even Byte) (Odd Byte)
情報メッセージ(16バイト)+-----------------------------------------------------------------+ | バージョンは分野を予約しました。| | メッセージ長---->。| | リモートデータ・リンク相関器---->。| | . . | | 遠く離れたDLC Port ID---->。| | . . | | 予約された分野---->。| | メッセージのタイプの予約された分野| +-----------------------------------------------------------------+ (バイトさえ)(奇数バイト)
The Version Number is set to x'4B', indicating a numeric value of 75.
'75の数値を示して、バージョンNumberはx'4B'に用意ができています。
The Header Length is x'00 48', indicating a numeric value of 72 bytes.
72バイトの数値を示して、Header Lengthはx'00 48'です。
The Header Number is x'01', indicating a value of one.
1の値を示して、Header Numberはx'01'です。
The Frame Direction field is set to x'01' for frames sent from the origin DLS to the target DLS, and is set to x'02' for frames sent from the target DLS to the origin DLS.
'フレームが目標DLSから発生源DLSまで発信したので、Frame Direction分野は、発生源DLSから目標DLSに送られたフレームのためにx'01'に設定されて、x'02に設定されます。
Note: The Remote Data Link Correlator and Remote DLC Port ID are
set equal to the Target Data Link Correlator and Target DLC Port
ID if the Frame Direction field is set to x'01', and are set equal
to the Origin Data Link Correlator and Origin DLC Port ID if the
Direction Field is set to x'02'.
以下に注意してください。 Remote Data Link CorrelatorとRemote DLC Port IDは、Frame Direction分野がx'01に設定されるならTarget Data Link CorrelatorとTarget DLC Port IDと等しいセットであり、'Direction Fieldがx'02に用意ができているなら、Origin Data Link CorrelatorとOrigin DLC Port IDと等しいセットです'。
The Protocol ID field is set to x'42', indicating a numeric value of 66.
66の数値を示して、'プロトコルID分野はx42年に設定されます'。
The Message Length field defines the number of bytes within the data field following the header. Note that this value is specified in two different fields of the message header.
ヘッダーに続いて、Message Length分野はデータ・フィールドの中でバイト数を定義します。 この値がメッセージヘッダーの2つの異なった分野で指定されることに注意してください。
The DLC Header Length is set to zero for SNA and is set to x'23' for NetBIOS datagrams, indicating a length of 35 bytes. This includes the Access Control (AC) field, the Frame Control (FC) field, Destination MAC Address (DA), the Source MAC Address (SA), the Routing Information (RI) field (padded to 18 bytes), the Destination link SAP (DSAP), the Source link SAP (SSAP), and the LLC control field (UI).
NetBIOSデータグラムにおいて'DLC Header LengthはSNAのためにゼロに用意ができていて、x23年に用意ができています'、35バイトの長さを示して。 これはAccess Control(西暦)分野、Frame Control(FC)分野、Destinationマックーアドレス(DA)、Sourceマックーアドレス(SA)、経路情報(ロードアイランド)分野(18バイトに、そっと歩く)、DestinationリンクSAP(DSAP)、SourceリンクSAP(SSAP)、およびLLC制御フィールド(UI)を含んでいます。
The values for the Message Type field are defined in a later section. Note that this value is specified in two different fields of the message header.
Message Type分野への値は後のセクションで定義されます。 この値がメッセージヘッダーの2つの異なった分野で指定されることに注意してください。
Dixon & Kushi [Page 7] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[7ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Reserved fields are set to zero upon transmission and should be ignored upon receipt.
予約された分野は、トランスミッションのゼロに設定されて、領収書で無視されるべきです。
3.2. Address Parameters
3.2. アドレスパラメタ
A data link is defined as a logical association between the two end stations using Data Link Switching. It is identified by a Data Link ID (14 bytes) consisting of the pair of attachment addresses associated with each end system. Each attachment address is represented by the concatenation of the MAC address (6 bytes) and the LLC address (1 byte).
データ・リンクは、Data Link Switchingを使用することで2つの端のステーションの間の論理的な協会と定義されます。 それは、それぞれのエンドシステムに関連している付属アドレスの組から成りながら、Data Link ID(14バイト)によって特定されます。 それぞれの付属アドレスはMACアドレス(6バイト)とLLCアドレス(1バイト)の連結で表されます。
DATA LINK ID (14 Bytes)
+-----------------------------------------------------------------+
|Target MAC Address ----> . |
| . . |
| . . |
|Origin MAC Address ----> . |
| . . |
| . . |
|Origin Link SAP Target Link SAP |
+-----------------------------------------------------------------+
データ・リンクID(14バイト)+-----------------------------------------------------------------+ |目標マックーアドレス---->。| | . . | | . . | |発生源マックーアドレス---->。| | . . | | . . | |発生源リンク体液目標リンクSAP| +-----------------------------------------------------------------+
An end-to-end circuit is identified by a pair of Circuit ID's. A Circuit ID is a 64 bit number that identifies the DLC circuit within a single DLS. It consists of a DLC Port ID (4 bytes), and a Data Link Correlator (4 bytes). This value is unique in a single DLS and is assigned locally. The pair of Circuit ID's along with the identifiers of the Data Link Switches, uniquely identify a single end-to-end circuit. Each DLS must keep a table of these Circuit ID pairs, one for the local end of the circuit and the other for the remote end of the circuit. In order to identify which Data Link Switch originated the establishment of a circuit, the terms, origin DLS and target DLS, will be employed in this document.
終わりから端への回路は1組のCircuit IDのものによって特定されます。 Circuit IDは独身のDLSの中でDLC回路を特定する64ビットの数です。 それはDLC Port ID(4バイト)、およびData Link Correlator(4バイト)から成ります。 この値は、独身のDLSでユニークであり、局所的に割り当てられます。 組、Data Link Switchesに関する識別子に伴うCircuit IDのものでは、唯一ただ一つの終わりから端への回路を特定してください。 各DLSは回路のリモートエンドのためにこれらのCircuit ID組のテーブル、回路ともう片方の地方の終わりのものを保たなければなりません。 どのData Link Switchが回路の設立を溯源したかを特定するために、用語(発生源DLSと目標DLS)は、本書では使われるでしょう。
CIRCUIT ID (8 Bytes)
+-----------------------------------------------------------------+
|DLC Port ID ----> . |
| . . |
|Data Link Correlator ----> . |
| . . |
+-----------------------------------------------------------------+
回路ID(8バイト)+-----------------------------------------------------------------+ |DLC Port ID---->。| | . . | |データ・リンク相関器---->。| | . . | +-----------------------------------------------------------------+
The Origin Transport ID and the Target Transport ID fields in the message header are used to identify the individual TCP/IP port on a Data Link Switch. The values have only local significance. However, each Data Link Switch is required to reflect the values contained in these two fields, along with the associated values for DLC Port ID
メッセージヘッダーのOrigin Transport IDとTarget Transport ID分野は、Data Link Switchの上の個々のTCP/IPポートを特定するのに使用されます。 値には、ローカルの意味しかありません。 しかしながら、各Data Link Switchがこれらの2つの分野に保管されていた値を反映するのに必要です、DLC Port IDへの関連値と共に
Dixon & Kushi [Page 8] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[8ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
and the Data Link Correlator, when returning a message to the other Data Link Switch.
そして、もう片方のData Link Switchにメッセージを返すときのData Link Correlator。
The following figure shows the use of the addressing parameters during the establishment of an end-to-end connection. The CANUREACH, ICANREACH, and REACH_ACK messages all carry the Data Link ID, consisting of the MAC and Link SAP addresses associated with the two end stations. Upon receipt of a CANUREACH message, the target DLS starts a data link for each port, thereby obtaining a Data Link Correlator. If the target station can be reached, an ICANREACH message is returned to the origin DLS containing the Target Circuit ID parameter. Upon receipt, the origin DLS starts a data link and returns the Origin Circuit ID to the target DLS within the REACH_ACK message. If the REACH_ACK message is not successfully received, the target Data Link Switch can obtain the Origin Circuit ID from a subsequent message (i.e., CONTACT, XIDFRAME, or DGRMFRAME).
以下の図は終わりから終わりとの接続の設立の間、アドレシングパラメタの使用を示しています。 CANUREACH、ICANREACH、およびREACH_ACKメッセージはすべて、Data Link IDを運びます、2つの端のステーションに関連しているMACとLink SAPアドレスから成って。 CANUREACHメッセージを受け取り次第、目標DLSは各ポートにデータ・リンクを始動します、その結果、Data Link Correlatorを入手します。 目標ステーションに達することができるなら、Target Circuit IDパラメタを含む発生源DLSにICANREACHメッセージを返します。 領収書で、発生源DLSはREACH_ACKメッセージの中の目標DLSにデータ・リンクを始動して、Origin Circuit IDを返します。 REACH_ACKメッセージが首尾よく受け取られないなら、目標Data Link Switchはその後のメッセージ(すなわち、CONTACT、XIDFRAME、またはDGRMFRAME)からOrigin Circuit IDを得ることができます。
+------------+ +------------+
|Disconnected| |Disconnected|
+------------+ CANUREACH (Data Link ID) +------------+
------------------------------------------------->
ICANREACH (Data Link ID, Target Circuit ID)
<------------------------------------------------
REACH_ACK (Data Link ID, Origin Cir ID, Target Cir ID)
------------------------------------------------->
+------------+ +------------+
|Circuit Est.| |Circuit Est.|
+------------+ +------------+
XIDFRAME (Data Link ID, Origin Cir ID, Target Cir ID)
<------------------------------------------------>
CONTACT (Data Link ID, Origin Cir ID, Target Cir ID)
------------------------------------------------->
CONTACTED (Data Link ID, Origin Cir ID, Target Cir ID)
<-------------------------------------------------
+------------+ +------------+
| Connected | | Connected |
+------------+ +------------+
INFOFRAME (Remote Circuit ID = Target Circuit ID)
------------------------------------------------->
INFOFRAME (Remote Circuit ID = Origin Circuit ID)
<-------------------------------------------------
+------------+ +------------+ |切断されます。| |切断されます。| +------------+ CANUREACH(データ・リンクID)+------------+ ------------------------------------------------->ICANREACH(データ・リンク目標Circuit ID(ID))<。------------------------------------------------ _ACK(データ・リンク発生源Cir目標Cir ID(ID)(ID))に達してください。------------------------------------------------->+------------+ +------------+ |回路エスト、||回路、エスト| +------------+ +------------+ XIDFRAME(データ・リンク発生源Cir目標Cir ID(ID)(ID))<。------------------------------------------------>接触(データ・リンク発生源Cir目標Cir ID(ID)(ID))------------------------------------------------->は(データ・リンク発生源Cir目標Cir ID(ID)(ID))<に連絡しました。------------------------------------------------- +------------+ +------------+ | 接続されます。| | 接続されます。| +------------+ +------------+ INFOFRAME(遠く離れたCircuit IDは目標Circuit IDと等しいです)------------------------------------------------->INFOFRAME(遠く離れたCircuit IDは発生源Circuit IDと等しい)<。-------------------------------------------------
Figure 3. DLS Circuits and Connections
図3。 dl回路とコネクションズ
During the exchange of the XIDFRAME, CONTACT, and CONTACTED messages, the pair of Circuit ID parameters is included in the message format along with the DATA LINK ID parameter. Once the connection has been established, the INFOFRAME messages are exchanged with the shorter
XIDFRAME、CONTACT、およびCONTACTEDメッセージの交換の間、Circuit IDパラメタの組はDATA LINK IDパラメタに伴うメッセージ・フォーマットで含まれています。 いったん接続を確立すると、より短いことでINFOFRAMEメッセージを交換します。
Dixon & Kushi [Page 9] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[9ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
header. This header contains only the Circuit ID associated with the remote DLS. The Remote Data Link Correlator and the Remote DLC Port ID are set equal to the Data Link Correlator and the DLC Port ID that are associated with the origin or target Data Link Switch, dependent upon the direction of the packet.
ヘッダー。 このヘッダーはリモートDLSに関連しているCircuit IDだけを含んでいます。 Remote Data Link CorrelatorとRemote DLC Port IDは、発生源に関連しているData Link CorrelatorとDLC Port IDと等しいセットか目標Data Link Switchです、パケットの方向に依存しています。
3.3. Message Types
3.3. メッセージタイプ
The following table lists the protocol data units that are exchanged between Data Link Switches. All values not listed are reserved for potential use in follow-on releases.
以下のテーブルはData Link Switchesの間で交換されるプロトコルデータ単位を記載します。 値が記載しなかったすべてがフォローオンリリースにおける潜在的使用のために予約されます。
Command Function Hex Value
------- -------- ---------
CANUREACH Can U Reach Station x'03'
ICANREACH I Can Reach Station x'04'
REACH_ACK Reach Acknowledgment x'05'
DGRMFRAME Datagram Frame (See note) x'06'
XIDFRAME XID Frame x'07'
CONTACT Contact Remote Station x'08'
CONTACTED Remote Station Contacted x'09'
RESTART_DL Restart Data Link x'10'
DL_RESTARTED Data Link Restarted x'11'
INFOFRAME Information (I) Frame x'0A'
HALT_DL Halt Data Link x'0E'
DL_HALTED Data Link Halted x'0F'
NETBIOS_NQ NetBIOS Name Query x'12'
NETBIOS_NR NetBIOS Name Recognized x'13'
DATAFRAME Data Frame (See note) x'14'
NETBIOS_ANQ NetBIOS Add Name Query x'1A'
NETBIOS_ANR NetBIOS Add Name Response x'1B'
指揮の機能十六進法価値------- -------- --------- 'CANUREACH Can U Reach駅x'03'ICANREACH、私、Can Reach駅のx'04'REACH_ACK Reach Acknowledgment x'05'DGRMFRAMEデータグラムFrame(注意を見る)x'06'XIDFRAME XID Frame x'07'CONTACT Contact Remote駅xの'08'CONTACTED Remote駅のContacted x'09'RESTART_DL Restart Data Link x10年'DL_RESTARTED Data Link; '再開しているx11年、'INFOFRAME情報(I)フレームx'0A'HALT_DL Halt Data Link x'0E'DL_HALTED Data Link Halted x'0F'NETBIOS_NQ NetBIOS Name Query x12年'NETBIOS_NR NetBIOS Name Recognized x13年の'DATAFRAME Data Frame(注意を見る)x14年'NETBIOS_ANQ NetBIOS Add Name Query x'1A'NETBIOS_ANR NetBIOS Add Name Response x'1B'
Table 1. SSP Message Types
1を見送ってください。 SSPメッセージタイプ
Note: Both the DGRMFRAME and DATAFRAME messages are used to carry
information received by the DLC entity within UI frames. As will
be explained below, the DGRMFRAME message is addressed according
to a pair of Circuit IDs, while the DATAFRAME message is addressed
according to a Data Link ID, being composed of a pair of MAC
addresses and a pair of link SAP addresses. The latter is
employed prior to the establishment of an end-to-end circuit when
Circuit IDs have yet to be established.
以下に注意してください。 DGRMFRAMEとDATAFRAMEメッセージの両方が、UIフレームの中にDLC実体によって受け取られた情報を運ぶのに使用されます。 以下で説明されるように、1組のCircuit IDによると、DGRMFRAMEメッセージは扱われます、Data Link IDによると、DATAFRAMEメッセージが扱われますが、1組のMACアドレスと1組のリンクSAPアドレスで構成されて。 Circuit IDがまだ確立されていないとき、後者は終わりから端への回路の設立の前に使われます。
For the exchange of NetBIOS control messages, the entire DLC header is carried as part of the message unit. This includes the MAC header, with the routing information field padded to 18 bytes, and the LLC header. The following message types are affected: NETBIOS_NQ, NETBIOS_NR, NETBIOS_ANQ, NETBIOS_ANR, and DATAFRAME when
NetBIOSコントロールメッセージの交換において、全体のDLCヘッダーはメッセージユニットの一部として運ばれます。 これはルーティング情報フィールドが18バイトに水増しされているMACヘッダー、およびLLCヘッダーを含んでいます。 以下のメッセージタイプは影響を受けます: NETBIOS_NQ、NETBIOS_NR、NETBIOS_ANQ、NETBIOS_ANR、およびDATAFRAME、いつ
Dixon & Kushi [Page 10] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[10ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
being used by NetBIOS systems. The routing information in the DLC header is not used by the remote Data Link Switch upon receiving the above five messages.
上記の5つのメッセージを受け取るとき、NetBIOSシステムDLCヘッダーのルーティング情報によって使用されるのはリモートData Link Switchによって使用されません。
4. Protocol Specification
4. プロトコル仕様
This section provides a description of the Switch-to-Switch Protocols. Included is a set of high-level protocol flows and a detail set of state transition tables. The states and the protocols are described in terms that are intended to be generic to different platforms. Emphasis of the technical details is to ensure operability of the IBM 6611 with another vendor's implementation. Notes are inserted at points where the IBM 6611 performs local actions that are specific to the AIX platform upon which it operates.
このセクションはSwitchからスイッチへのプロトコルの記述を提供します。 含まれているのは、1セットのハイレベルのプロトコル流れと状態遷移テーブルの詳細セットです。 州とプロトコルは異なったプラットホームへのジェネリックであることを意図する用語で説明されます。技術的詳細の強調は別のベンダーの実装でIBM6611の運転可能性を確実にすることです。 注意はIBM6611がそれが作動するAIXプラットホームに特定の地方の動きを実行するポイントで挿入されます。
4.1. Protocol Flow Diagrams
4.1. プロトコルフローチャート
The switch-to-switch protocols are used to setup and take down circuits between a pair of Data Link Switches. Once a circuit is established, the end stations on the local networks can employ LLC Type 1 (connectionless) protocols. In addition, the end systems can establish an end-to-end connection for support of LLC Type 2 (connection oriented) protocols.
スイッチからスイッチへのプロトコルは、1組のData Link Switchesの間の回路をセットアップして、降ろすのに使用されます。 回路がいったん確立されると、企業内情報通信網の端のステーションはLLC Type1の(コネクションレス)のプロトコルを使うことができます。 さらに、エンドシステムはLLC Type2(適応する接続)プロトコルのサポートのための終わりから終わりとの接続を確立できます。
The term, Data Link, is used in this document to refer to both a "logical data link" when supporting Type 1 LLC services, and a "data link connection" when supporting Type 2 LLC services. In both cases, the Data Link in defined by the concatenation of the destination MAC address (DA), the source MAC address (SA), the destination link SAP (DSAP) and source link SAP (SSAP).
用語(Data Link)は、2つのLLCサービスをTypeにサポートするとき、TypeがLLCが修理する1、「データリンク接続」であるとサポートするとき、両方への「論理的なデータ・リンク」を参照するのに本書では使用されます。 どちらの場合も、送付先MACアドレスの連結(DA)、ソースMACアドレス(SA)、目的地リンクSAP(DSAP)、および情報筋によって定義されるところのData LinkはSAP(SSAP)をリンクします。
4.1.1. Connect Protocols
4.1.1. プロトコルを接続してください。
The following figure depicts the protocol flows that are used for the establishment of a circuit between a pair of Data Link Switches, followed by the establishment of a connection between the pair of end systems. The figure is drawn assuming that the two end systems are SNA (the protocol flow for NetBIOS systems is described in a later paragraph).
以下の図はエンドシステムの組の間の接続の設立によって続かれた1組のData Link Switchesの間の回路の設立に使用されるプロトコル流れについて表現します。2台のエンドシステムがSNAであると仮定しながら、図は作成されます(NetBIOSシステムのためのプロトコル流動は後のパラグラフで説明されます)。
Dixon & Kushi [Page 11] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[11ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Data Link Data Link Data Link Data Link
Control Switch Switch Control
-------------------- --------------------
+------------+ +------------+
|Disconnected| |Disconnected|
+------------+ +------------+
Test Command CANUREACH Test Comd.
----------> ---------------------------------------> ------->
(DSAP=Null) (DSAP=SSAP)
Test Response
ICANREACH <---------
Test Response <---------------------------------------
<---------- REACH ACK
--------------------------------------->
+------------+ +------------+
|Circuit Est.| |Circuit Est.|
+------------+ +------------+
SABME CONTACT
----------> ---------------------------------------> SABME
UA ------->
<----------
RNR UA
<---------- CONTACTED <-------
<---------------------------------------
+------------+ +------------+
| Connected | | Connected |
+------------+ +------------+
RR
<---------
データ・リンクデータ・リンクデータ・リンクデータリンク制御スイッチスイッチ制御装置-------------------- -------------------- +------------+ +------------+ |切断されます。| |切断されます。| +------------+ +------------+ テストコマンドCANUREACHテストComd。 ---------->。--------------------------------------->。------->(DSAPはヌルと等しいです)(DSAP=SSAP)テスト応答ICANREACH<。--------- テスト応答<。--------------------------------------- <、-、-、-、-、-、-、-、-、-- ACKに達してください。--------------------------------------->+------------+ +------------+ |回路エスト、||回路、エスト| +------------+ +------------+ SABME接触---------->。--------------------------------------->SABME Ua-------><。---------- RNR Ua<。---------- 連絡された<。------- <--------------------------------------- +------------+ +------------+ | 接続されます。| | 接続されます。| +------------+ +------------+ RR<。---------
Figure 4. DLS Connect Message Protocols
図4。 dlがメッセージプロトコルを接続します。
Upon receipt of a Test command from the origin station, the origin DLS will send a CANUREACH (i.e., can you reach) message to the target DLS. If the target DLS is not known to the origin DLS, the CANUREACH message is sent to all remote Data Link Switches defined to the origin DLS. The receipt of the CANUREACH message causes the target DLS to send a Test command searching for the target station. The target station will return a Test response, causing the target DLS to return an ICANREACH (i.e., I can reach) message to the origin DLS. If multiple Data Link Switches can reach the target station, the origin DLS will receive multiple ICANREACH messages. The origin DLS will select the first message and send a REACH_ACK (i.e., reach acknowledgment) message to the selected Data Link Switch. During this exchange of messages, both Data Link Switches change states from the Disconected state to the Circuit Established state. Once the circuit is established, Type-1 frames, such as XID, may be exchanged between the origin and target stations.
発生源ステーションからのTestコマンドを受け取り次第、発生源DLSはCANUREACH(すなわち、あなたは達することができます、)メッセージを目標DLSに送るでしょう。 発生源DLSにおいて目標DLSを知っていないなら、発生源DLSと定義されたすべてのリモートData Link SwitchesにCANUREACHメッセージを送ります。 CANUREACHメッセージの領収書で、目標DLSはTestコマンドに目標ステーションを捜し求めさせます。 目標ステーションはTest応答を返すでしょう、目標DLSがICANREACH(すなわち、私は達することができる)メッセージを発生源DLSに返すことを引き起こして。 複数のData Link Switchesが目標ステーションに達することができると、発生源DLSは複数のICANREACHメッセージを受け取るでしょう。 発生源DLSは最初のメッセージを選択して、REACH_ACK(すなわち、承認に達する)メッセージを選択されたData Link Switchに送るでしょう。 メッセージのこの交換の間、両方のData Link Switchesは州をDisconected状態からCircuit Established状態に変えます。 いったん回路を確立すると、発生源と目標ステーションの間でXIDなどのType-1フレームを交換するかもしれません。
Dixon & Kushi [Page 12] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[12ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
To establish a connection, the origin station sends a SABME command. Upon receipt of this command, the origin DLS will send a CONTACT message to the target DLS and return a UA response to the origin station. To inhibit traffic flow until the connection is established to the remote station, a RNR supervisory frame is sent to the origin station. The CONTACT message will cause the target DLS to send a SABME command to the target station, which in return will reply with a UA response. Upon receipt of the UA response, the target DLS will send a CONTACTED message to the origin DLS. The origin DLS will now send an RR supervisory frame to the origin station. During this exchange of messages, both Data Link Switches change states from the Circuit Established state to the Connected state.
取引関係を築くために、発生源ステーションはSABMEコマンドを送ります。 このコマンドを受け取り次第、発生源DLSはCONTACTメッセージを目標DLSに送って、発生源ステーションへのUA応答を返すでしょう。 接続が遠隔局に確立されるまで交通の流れを抑制するために、RNRの管理のフレームを発生源ステーションに送ります。 目標DLSはCONTACTメッセージでSABMEコマンドを目標ステーションに送るでしょう。(代わりに、それは、UA応答で返答するでしょう)。 UA応答を受け取り次第、目標DLSはCONTACTEDメッセージを発生源DLSに送るでしょう。 発生源DLSは現在、RRの管理のフレームを発生源ステーションに送るでしょう。 メッセージのこの交換の間、両方のData Link Switchesは州をCircuit Established状態からConnected状態に変えます。
For NetBIOS end systems, the protocol flows are similar but employ different frames and SSP messages. Instead of using a Test command frame to initiate the circuit, a NetBIOS system will use a Name Query frame. Receipt of a Name Query frame will cause the Data Link Switch to issue a NETBIOS_NQ message instead of the CANUREACH message. In a like fashion, the Test response is replaced with a Name Recognized frame and the ICANREACH message is replaced with a NETBIOS_NR message. As with the SNA protocol flows, the receipt of a NETBIOS_NR message causes the origin Data Link Switch to respond with a REACH_ACK message.
NetBIOSエンドシステムに、プロトコル流れは同様ですが、異なったフレームとSSPメッセージを使ってください。 回路を開始するのにTestコマンド・フレームを使用することの代わりに、NetBIOSシステムはName Queryフレームを使用するでしょう。 Name Queryフレームの領収書で、Data Link SwitchはCANUREACHメッセージの代わりにNETBIOS_NQメッセージを発行するでしょう。 同様に、Test応答をName Recognizedフレームに取り替えます、そして、ICANREACHメッセージをNETBIOS_NRメッセージに取り替えます。 SNAプロトコル流れのように、発生源Data Link SwitchはNETBIOS_NRメッセージの領収書でREACH_ACKメッセージで応じます。
4.1.2. Link Restart Protocols
4.1.2. リンク再開プロトコル
The following figure depicts the protocol flows that result from restarting the end-to-end connection. This causes the Data Link Switches to terminate the existing connection and to enter the Circuit Established state awaiting the start of a new connection.
以下の図は、終わりから終わりとの接続を再出発するので、結果として生じるプロトコル流れについて表現します。 これは、Data Link Switchesが既存の接続を終えて、新しい接続の始まりを待つCircuit Established州に入れることを引き起こします。
Dixon & Kushi [Page 13] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[13ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Data Link Data Link Data Link Data Link
Control Switch Switch Control
--------------------- ---------------------
+-----------+ +-----------+
| Connected | | Connected |
SABME +-----------+ +-----------+
-----------> RESTART_DL
DM -------------------------------------> DISC
<----------- -------->
UA
DL_RESTARTED (Case 1) <--------
<-------------------------------------
+-----------+ +-----------+
|Circuit Est| |Circuit Est|
+-----------+ +-----------+
........... or ...........
SABME
-----------> DL_RESTARTED (Case 2)
UA <-------------------------------------
<----------- +-----------+
|Circuit Est|
CONTACT +-----------+
RNR ------------------------------------>
<----------
データ・リンクデータ・リンクデータ・リンクデータリンク制御スイッチスイッチ制御装置--------------------- --------------------- +-----------+ +-----------+ | 接続されます。| | 接続されます。| SABME+-----------+ +-----------+ ----------->再開_dl DM------------------------------------->ディスク<。----------- -------->Ua dl_は(ケース1)<を再開しました。-------- <------------------------------------- +-----------+ +-----------+ |回路エスト| |回路エスト| +-----------+ +-----------+、…、… SABME----------->dl_は(ケース2)UA<を再開しました。------------------------------------- <、-、-、-、-、-、-、-、-、-、-- +-----------+ |回路エスト| 接触+-----------+ RNR------------------------------------><。----------
Figure 5. DLS Link Restart Message Protocols
図5。 dlが再開メッセージプロトコルをリンクします。
Upon receipt of a SABME command from the origin station, the origin DLS will send a RESTART_DL message to the target DLS. A DM response is also returned to the origin station and the data link is restarted.
発生源ステーションからのSABMEコマンドを受け取り次第、発生源DLSはRESTART_DLメッセージを目標DLSに送るでしょう。 また、DM応答を発生源ステーションに返します、そして、データ・リンクを再開します。
Upon receipt of the RESTART_DL message, the target DLS will issue a DISC command to the target station. The target station is expected to return a UA response. The target DLS will then restart its data link and send an DL_RESTARTED message back to the origin DLS. During this exchange of messages, both Data Link Switches change states from Connected state to Circuit Established state.
RESTART_DLメッセージを受け取り次第、目標DLSは目標ステーションにDISCコマンドを発行するでしょう。 目標ステーションがUA応答を返すと予想されます。 目標DLSは次に、データ・リンクを再開して、DL_RESTARTEDメッセージを発生源DLSに送り返すでしょう。 メッセージのこの交換の間、両方のData Link Switchesは州をConnected状態からCircuit Established状態に変えます。
If the origin station now resends the SABME command, the origin DLS will send a CONTACT message to the target DLS. If the SABME command is received prior to the receipt of the DL_RESTARTED message (case 2 in the figure), the CONNECT message is delayed until the DL_RESTARTED message is received. The resulting protocol flows at this point parallel those given above for the connect sequence.
発生源ステーションが現在SABMEコマンドを再送すると、発生源DLSはCONTACTメッセージを目標DLSに送るでしょう。 DL_RESTARTEDメッセージ(図におけるケース2)の領収書の前にSABMEコマンドを受け取るなら、DL_RESTARTEDメッセージが受信されるまで、CONNECTメッセージを遅らせます。 結果として起こるプロトコル流れがここに上に与えられたものに沿う、系列を接続してください。
Dixon & Kushi [Page 14] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[14ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
4.1.3. Disconnect Protocols
4.1.3. プロトコルから切断してください。
The following figure depicts the protocol flows that result from the end system terminating an existing connection. Not only is the connection terminated, but the circuit between the Data Link Switches is taken down.
以下の図は既存の接続を終えるエンドシステムから生じるプロトコル流れについて表現します。 接続が終えられるだけではなく、Data Link Switchesの間の回路は降ろされます。
Data Link Data Link Data Link Data Link
Control Switch Switch Control
-------------------- --------------------
+-----------+ +-----------+
| Connected | | Connected |
+-----------+ +-----------+
DISC
----------> HALT_DL
UA -------------------------------------> DISC
<---------- --------->
UA
DL_HALTED <--------
<-------------------------------------
+-----------+ +-----------+
|Disconnectd| |Disconnectd|
+-----------+ +-----------+
......... or ..........
+-----------+ +-----------+
| Connected | | Connected |
+-----------+ +-----------+
データ・リンクデータ・リンクデータ・リンクデータリンク制御スイッチスイッチ制御装置-------------------- -------------------- +-----------+ +-----------+ | 接続されます。| | 接続されます。| +-----------+ +-----------+ ディスク---------->停止_dl Ua------------------------------------->ディスク<。---------- --------->Ua dl_は<を止めました。-------- <------------------------------------- +-----------+ +-----------+ |Disconnectd| |Disconnectd| +-----------+ +-----------+、…、… +-----------+ +-----------+ | 接続されます。| | 接続されます。| +-----------+ +-----------+
DISC TCP Connection Failure DISC
<-------- <------------------------------------> --------->
UA UA
--------> <--------
+-----------+ +-----------+
|Disconnectd| |Disconnectd|
+-----------+ +-----------+
ディスクTCP接続失敗ディスク<。-------- <------------------------------------>。--------->Ua Ua--------><。-------- +-----------+ +-----------+ |Disconnectd| |Disconnectd| +-----------+ +-----------+
Figure 6. DLS Disconnect Message Protocols
図6。 dlがメッセージプロトコルから切断します。
Upon receipt of a DISC command from the origin station, the origin DLS will reply with a UA response and issue a HALT_DL message to the target DLS. Upon receipt of the HALT_DL message, the target DLS will send a DISC command to the target station. The target station will then respond with a UA response, causing the target DLS to return a DL_HALTED message to the origin DLS. During this exchange of messages, both Data Link Switches change states from the Connected state to the Disconnected state.
発生源ステーションからのDISCコマンドを受け取り次第、発生源DLSはUA応答で返答して、HALT_DLメッセージを目標DLSに発行するでしょう。 HALT_DLメッセージを受け取り次第、目標DLSはDISCコマンドを目標ステーションに送るでしょう。 次に、目標ステーションはUA応答で応じるでしょう、目標DLSがDL_HALTEDメッセージを発生源DLSに返すことを引き起こして。 メッセージのこの交換の間、両方のData Link Switchesは州をConnected状態からDisconnected状態に変えます。
Dixon & Kushi [Page 15] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[15ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
If the TCP connection between two Data Link Switches fails, all connections that are currently multiplexed on the failed TCP connection will be taken down. This implies that both Data Link Switches will send DISC commands to all the local systems that are associated with the failed connections. Upon sending the DISC command, the Data Link Switch will enter the DISCONNECT state for each circuit.
2Data Link Switchesの間のTCP接続が失敗すると、失敗したTCP接続のときに現在多重送信されるすべての接続が降ろされるでしょう。 これは、両方のData Link Switchesが失敗した接続に関連しているすべてのローカルシステムへのコマンドをDISCに送るのを含意します。 DISCコマンドを送ると、Data Link Switchは各回路のためにDISCONNECT状態に入るでしょう。
4.2. DLS State Machine
4.2. dlがマシンを述べます。
The following state tables describe the states for a single connection through the Data Link Switch. State information is kept for each connection. The initial state for a connection is DISCONNECT. The steady state is either CIRCUIT_ESTABLISHED or CONNECTED. In the former state, an end-to-end circuit has been established allowing the support of Type 1 LLC between the end systems. The latter state exists when an end-to-end connection has been established for the support of Type 2 LLC services between the end systems.
以下のステートテーブルは単独結合のためにData Link Switchを通して州について説明します。 州の情報は各接続のために保たれます。 接続のための初期状態はDISCONNECTです。 定常状態は、CIRCUIT_ESTABLISHEDかCONNECTEDのどちらかです。 前の状態に、終わりから端への回路は、エンドシステムの間の1LLCをTypeのサポートに許容しながら、確立されました。終わりから終わりとの接続がエンドシステムの間のType2LLCサービスのサポートのために確立されたとき、後者の状態は存在しています。
For SNA, circuit establishment is via the use of IEEE 802.2 Test or XID frames. SNA devices send these frames to the null SAP in order to determine the source route information in support of bridging. Normally SNA devices use SAP x'04', x'08', or x'0C'. Typically the SAP would be used to determine if the Test frames should be sent to the DLS code in the router. If both bridging and DLS are enabled, this allows the product to ensure that SNA frames are not both bridged and switched.
SNAのために、IEEE802.2TestかXIDフレームの使用で回路設立はものです。 SNAデバイスは、ブリッジすることを支持してソース経由地案内を決定するためにこれらのフレームをヌルSAPに送ります。 通常、SNAデバイスはSAP x'04'、x'08'、またはxを'0C'使用します。 通常、SAPは、TestフレームがルータにおけるDLSコードに送られるべきであるかどうか決定するのに使用されるでしょう。 ブリッジするのとDLSの両方が有効にされるなら、これで、製品は、SNAフレームがブリッジされて、切り換えられないのを保証できます。
For NetBIOS, circuit establishment is via the Name Query and Name Recognized frames. These frames are used for both address resolution and source route determination. Normally NetBIOS devices use SAP x'F0'.
NetBIOSに関しては、Name QueryとName Recognizedフレームを通して回路設立があります。 これらのフレームはアドレス解決と送信元経路決断の両方に使用されます。 '通常、NetBIOSデバイスはSAP x'F0を使用します'。
4.2.1. Data Link Switch States
4.2.1. データ・リンクスイッチ州
The Switch-to-Switch Protocols will be formally defined through a single state machine. The following table lists the eleven possible states. A separate state machine is employed for each end-to-end circuit that is maintained by the Data Link Switch. The three steady states are DISCONNECTED, CIRCUIT_ESTABLISHED, and CONNECTED.
Switchからスイッチへのプロトコルは単一の州のマシンを通して正式に定義されるでしょう。 以下のテーブルは11の可能な州を記載します。 別々の州のマシンは終わりから端へのData Link Switchによって維持されるそれぞれの回路に使われます。 3つの定常状態が、DISCONNECTEDと、CIRCUIT_ESTABLISHEDと、CONNECTEDです。
Dixon & Kushi [Page 16] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[16ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
State Name Description
---------- -----------
CIRCUIT_ESTABLISHED The end-to-end circuit has been
established. At this time LLC Type 1
services are available from end-to-end.
CIRCUIT_PENDING The target DLS is awaiting a REACH_ACK
response to an ICANREACH message.
CIRCUIT_RESTART The DLS that originated the reset is
awaiting the restart of the data link
and the DL_RESTARTED response to a
RESTART_DL message.
CONNECTED The end-to-end connection has been
established thereby allowing LLC Type 2
services from end-to-end in addition to
LLC Type 1 services.
CONNECT_PENDING The origin DLS is awaiting the CONTACTED
response to a CONTACT message.
CONTACT_PENDING The target DLS is awaiting the
DLC_CONTACTED confirmation to a DLC_CONTACT
signal (i.e., DLC is waiting for a UA
response to an SABME command).
DISCONNECTED The initial state with no circuit or
connection established, the DLS is awaiting
either a CANUREACH, an ICANREACH, a
NETBIOS_NQ, or a NETBIOS_NR message.
DISCONNECT_PENDING The DLS that originated the disconnect
is awaiting the DL_HALTED response to a
HALT_DL message.
HALT_PENDING The remote DLS is awaiting the DLC_DL_HALTED
indication following the DLC_HALT_DL request
(i.e., DLC is waiting for a UA response to a
DISC command).
RESTART_PENDING The remote DLS is awaiting the DLC_DL_HALTED
indication following the DLC_HALT_DL request
(i.e., DLC is waiting for a UA response to a
DISC command), and the restart of the data
link.
RESOLVE_PENDING The target DLS is awaiting either the
DLC_DL_STARTED indication following the
DLC_START_DL reqest (i.e., DLC is waiting
for a Test response as a result of sending a
Test command), or a NB_Name_Recognized
frame in response to a NB_Name_Query frame.
州の名前記述---------- ----------- CIRCUIT_ESTABLISHED終わらせる端の回路は確立されました。 このとき、LLC Type1サービスは終わらせる終わりから利用可能です。 CIRCUIT_PENDING目標DLSはICANREACHメッセージへのREACH_ACK応答を待っています。 リセットを溯源したCIRCUIT_RESTART DLSはデータ・リンクの再開とRESTART_DLメッセージへのDL_RESTARTED応答を待っています。 CONNECTED終わらせる終わりの接続は、その結果、LLC Type1サービスに加えて終わらせる終わりからLLC Type2にサービスを許しながら、確立されました。 CONNECT_PENDING発生源DLSはCONTACTメッセージへのCONTACTED応答を待っています。 CONTACT_PENDING目標DLSはDLC_CONTACT信号にDLC_CONTACTED確認を待っています(すなわち、DLCはSABMEコマンドへのUA応答を待っています)。 ICANREACH、NETBIOS_NQ、またはNETBIOS_NRが、どんな回路も接続も確立されていない初期状態、DISCONNECTED DLSがCANUREACHを待っているのを通信します。 分離を溯源したDISCONNECT_PENDING DLSはHALT_DLメッセージへのDL_HALTED応答を待っています。 DLが要求するDLC_HALT_に続いて、HALT_PENDINGのリモートDLSはDLC_DL_HALTED指示を待っています(すなわち、DLCはDISCコマンドへのUA応答を待っています)。 DLが要求する(すなわち、DLCはDISCコマンドへのUA応答を待っています)DLC_HALT_、およびデータ・リンクの再開に続いて、RESTART_PENDINGのリモートDLSはDLC_DL_HALTED指示を待っています。 RESOLVE_PENDING目標DLSはネブラスカ_Name_Queryフレームに対応してDLC_START_DL reqest(Testコマンドを送ることの結果、すなわち、DLCはTest応答を待っている)に続くDLC_DL_STARTED指示かネブラスカ_Name_Recognizedフレームのどちらかを待っています。
Table 2. Data Link Switch States
2を見送ってください。 データ・リンクスイッチ州
The following figure depicts the events that cause a transition to a new state. The resulting action(s) are not explicitly shown. The
以下の図は新しい状態への変遷を引き起こすイベントについて表現します。 結果として起こる動作は明らかに示されません。 The
Dixon & Kushi [Page 17] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[17ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
DISCONNECT_PENDING state will be entered whenever a DLC error condition occurs in any of the other states (except RESOLVE_PENDING), or when a DISC command is received by the DLC.
DLCエラー条件が他の州(RESOLVE_PENDINGを除いた)のどれかに起こるときはいつも、DISCコマンドがDLCによって受け取られるとき、DISCONNECT_PENDING状態は入られるでしょう。
Dixon & Kushi [Page 18] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[18ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
DLC_RESOLVE_C+----+ +----DLC_ERROR---+
| | \|/ |
+------------+ +>+--+---------+ CANUREACH +-+----------+
| Disconnect +--DL_HALTED-->|Disconnected|------------>| Resolve |
| Pending |<+ +------->| |<-------+ | Pending |
+---------+--+ | | +-----+------+ | +-----+------+
/|\ | HALT_DL| /|\ |/|\/|\ | |
DLC_ERROR +----+ | +----+ | | +------+ | DLC_DL_STARTED
| | | |HALT_DL(ts)| +------+ |
| | ICANREACH| | HALT_DL(ts)|
+--HALT_DL(ts)+ | | | | | |
| HALT_DL(ts) | | HALT_DL(ts) | |
| | | | | | |
| +-RESTART_DL(ts)+----+ | | | | |
| | | \|/ \|/| | | \|/
+----+---+---+ | +-------+----+ | +-+----------+
| Contact |<-CONTACT--+--+ Circuit |<-REACH_ACK--+ Circuit |
| Pending | | | Established| (DLC not | Pending |
+-----+------+ | +----------+-+ contacted)+-+------+---+
| /|\ | /|\ /|\ | | | |
| | +--+----+ | | | | |
| +-CONTACT--+--+--------+----+------+----------+ REACH_ACK
| | |RESTART_DL(ts) | (DLC contacted)
DLC_CONTACTED | +------+ | | +--------------+ |
| | | | | DLC_CONTACTED | |
+---------------+-------+ | | +-----------------+ | |
+-----DL_RESTARTED | | | | | |
| (DLC not contacted) \|/| | \|/ | \|/
+-----+------+ +---+-+------+ CONTACTED +-----+------+
| Circuit |<-DLC_RESET---+ Connected |<------------+ Connect |
| Restart | | | | Pending |
+----------+-+ +------------+ +-----+------+
/|\ | DL_RESTARTED /|\ |
| +----------------(DLC contacted)--------------+ |
| |
+-------------------------DLC_RESET--------------------+
DLC_決心_C+----+ +----DLC_誤り---+ | | \|/ | +------------+ + >+--、+---------+ CANUREACH++----------+ | 分離+--dl_は停止しました-->|切断されます。|、-、-、-、-、-、-、-、-、-、-、--、>| 決心| | 未定|<++------->| | <、-、-、-、-、-、--+ | 未定| +---------+--+ | | +-----+------+ | +-----+------+ /|\ | _dlを止めてください。| /|\ |/|\/|\ | | DLC_誤り+----+ | +----+ | | +------+ | DLC_dl_は始まりました。| | | |_DL(ts)を止めてください。| +------+ | | | ICANREACH| | _DL(ts)を止めてください。| +--_DL(ts)+を止めてください。| | | | | | | _DL(ts)を止めてください。| | _DL(ts)を止めてください。| | | | | | | | | | +再開_DL(ts)+----+ | | | | | | | | \|/ \|/| | | \|/ +----+---+---+ | +-------+----+ | +-+----------+ | 接触| <、-接触--+--+ 回路| <、-範囲_ACK--+ 回路| | 未定| | | 設立されます。| | +まで(DLC、|、-、-、-、--、+、-、-、-、-、--、+| +、-、-、-、-、-、-、-、-、--、連絡された++)+-+------+---+ | /|\ | /|\ /|\ | | | | | | +--+----+ | | | | | | +接触--+--+--------+----+------+----------+ 範囲_ACK| | |再開_DL(ts)| (連絡されたDLC) 連絡されたDLC_| +------+ | | +--------------+ | | | | | | 連絡されたDLC_| | +---------------+-------+ | | +-----------------+ | | +-----dl_は再開しました。| | | | | | | (連絡されなかったDLC) \|/| | \|/ | \|/ +-----+------+ +---+-+------+は+に連絡しました。-----+------+ | 回路| <、-DLC_リセット---接続された+| <、-、-、-、-、-、-、-、-、-、-、--+は接続します。| | 再開| | | | 未定| +----------+-+ +------------+ +-----+------+ /|\ | dl_は/を再開しました。|\ | | +----------------(連絡されたDLC)--------------+ | | | +-------------------------DLC_リセット--------------------+
Figure 7. DLS State Transitions (ts = transitional state)
図7。 dl状態遷移(過渡的なt=状態)
The DISCONNECT state is the initial state for a new circuit. One end station starts the connection via a TEST or XID command (i.e., DLC_RESOLVE_C) or a NetBIOS Name Query command (not explicitly shown). Upon receipt, the Data Link Switches exchange a set of CANUREACH, ICANREACH and REACH_ACK messages. Upon completion of this three-legged exchange, both Data Link Switches will be in the CIRCUIT_ESTABLISHED state. Two pending states also exist during this exchange. The RESOLVE_PENDING state is entered by the target Data Link Switch awaiting a Test response to a Test Command and the
DISCONNECT状態は新しい回路への初期状態です。 TEST、XIDコマンド(すなわち、DLC_RESOLVE_C)またはNetBIOS Name Queryコマンド(明らかに、目立たない)で片端ステーションは接続を始めます。 領収書で、Data Link Switchesは1セットのCANUREACH、ICANREACH、およびREACH_ACKメッセージを交換します。 この三脚の交換の完成には、両方のData Link SwitchesがCIRCUIT_ESTABLISHED状態にあるでしょう。 また、2つの未定の州がこの交換の間、存在しています。 そしてRESOLVE_PENDING状態がTest CommandへのTest応答を待つ目標Data Link Switchによって入られる。
Dixon & Kushi [Page 19] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[19ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
CIRCUIT_PENDING state is entered by the target DLS awaiting the REACH_ACK reply to an ICANREACH message.
CIRCUIT_PENDING状態はREACH_ACK回答をICANREACHメッセージにお待ちしている目標DLSによって入られます。
The CIRCUIT_ESTABLISHED state allows for the exchange of LLC Type 1 frames such as the XID exchanges between SNA stations that occurs prior to the establishment of a connection. Also, datagram traffic (i.e., UI frames) may be sent and received between the end stations. These exchanges use the XIDFRAME and DGRMFRAME messages sent between the Data Link Switches.
CIRCUIT_ESTABLISHED州は接続の設立の前に起こるSNAステーションの間のXID交換などのLLC Type1フレームの交換を考慮します。 また、データグラムトラフィック(すなわち、UIフレーム)を端のステーションの間に送って、受け取るかもしれません。 これらの交換はメッセージがData Link Switchesの間で送ったXIDFRAMEとDGRMFRAMEを使用します。
In the CIRCUIT_ESTABLISHED state, the receipt of a SABME command (i.e., DLC_CONTACTED) causes the origin DLS to issue a CONTACT message, to send an RNR supervisory frame (i.e., DLC_ENTER_BUSY) to the origin station, and to enter the CONNECT_PENDING state awaiting a CONTACTED message. The target DLS, upon the receipt of a CONTACT message, will issue a SABME command (i.e., DLC_CONTACT) and enter the Contact Pending state. Once the UA response is received (i.e., DLC_CONTACTED), the target DLS sends a CONTACTED message and enters the CONNECTED state. When received, the origin DLS enters the Connected state and sends an RR supervisory frame (i.e., DLC_EXIT_BUSY).
In the CIRCUIT_ESTABLISHED state, the receipt of a SABME command (i.e., DLC_CONTACTED) causes the origin DLS to issue a CONTACT message, to send an RNR supervisory frame (i.e., DLC_ENTER_BUSY) to the origin station, and to enter the CONNECT_PENDING state awaiting a CONTACTED message. The target DLS, upon the receipt of a CONTACT message, will issue a SABME command (i.e., DLC_CONTACT) and enter the Contact Pending state. Once the UA response is received (i.e., DLC_CONTACTED), the target DLS sends a CONTACTED message and enters the CONNECTED state. When received, the origin DLS enters the Connected state and sends an RR supervisory frame (i.e., DLC_EXIT_BUSY).
The CONNECTED state is the steady state for normal data flow once a connection has been established. Information frames (i.e., INFOFRAME messages) are simply sent back and forth between the end points of the connection. This is the path that should be optimized for performance.
The CONNECTED state is the steady state for normal data flow once a connection has been established. Information frames (i.e., INFOFRAME messages) are simply sent back and forth between the end points of the connection. This is the path that should be optimized for performance.
The connection is terminated upon the receipt of a DISC frame or under some other error condition detected by DLC (i.e., DLC_ERROR). Upon receipt of this indication, the DLS will halt the local data link, send a HALT_DL message to the remote DLS, and enter the DISCONNECT_PENDING State. When the HALT_DL frame is received by the other DLS, the local DLC is halted for this data link, a DL_HALTED message is returned, and the DISCONNECTED state is entered. Receipt of this DL_HALTED message causes the other DLS to also enter the DISCONNECTED state.
The connection is terminated upon the receipt of a DISC frame or under some other error condition detected by DLC (i.e., DLC_ERROR). Upon receipt of this indication, the DLS will halt the local data link, send a HALT_DL message to the remote DLS, and enter the DISCONNECT_PENDING State. When the HALT_DL frame is received by the other DLS, the local DLC is halted for this data link, a DL_HALTED message is returned, and the DISCONNECTED state is entered. Receipt of this DL_HALTED message causes the other DLS to also enter the DISCONNECTED state.
The CIRCUIT_RESTART state is entered if one of the Data Link Switches receives a SABME command (i.e., DLC_RESET) while in the CONNECTED state. This causes a DM command to be returned to the origin station and a RESTART_DL message to be sent to the remote Data Link Switch. This causes the remote data link to be halted and then restarted. The remote DLS will then send a DL_RESTARTED message back to the first DLS. The receipt of the DL_RESTARTED message causes the first DLS to issue a new CONTACT message, assuming that the local DLC has been contacted (i.e., the origin station has resent the SABME command). This is eventually responded to by a CONTACTED message.
The CIRCUIT_RESTART state is entered if one of the Data Link Switches receives a SABME command (i.e., DLC_RESET) while in the CONNECTED state. This causes a DM command to be returned to the origin station and a RESTART_DL message to be sent to the remote Data Link Switch. This causes the remote data link to be halted and then restarted. The remote DLS will then send a DL_RESTARTED message back to the first DLS. The receipt of the DL_RESTARTED message causes the first DLS to issue a new CONTACT message, assuming that the local DLC has been contacted (i.e., the origin station has resent the SABME command). This is eventually responded to by a CONTACTED message.
Dixon & Kushi [Page 20] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 20] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Following this exchange, both Data Link Switches will return to the CONNECTED state. If the local DLC has not been contacted, the receipt of a DL_RESTARTED command causes the Data Link Switch to enter the CIRCUIT_ESTABLISHED state awaiting the receipt of a SABME command (i.e., DLC_CONTACTED signal).
Following this exchange, both Data Link Switches will return to the CONNECTED state. If the local DLC has not been contacted, the receipt of a DL_RESTARTED command causes the Data Link Switch to enter the CIRCUIT_ESTABLISHED state awaiting the receipt of a SABME command (i.e., DLC_CONTACTED signal).
In the figure, the transition labeled HALT_DL(ts) represents the HALT_PENDING state and the transition labeled RESTART_DL(ts) represents the RESTART_PENDING state. Both these transitional states have only one input event and only one output action. While in these states, the Data Link Switch is awaiting responses from the local station on the adjacent LAN (i.e., a UA response to a DISC command). Also in the RESTART_PENDING state, the Data Link Switch will attempt to restart the data link prior to sending a DL_RESTARTED message. For the IBM 6611 implementation, the start of a data link involves the exchange of a Test command/response on the adjacent LAN (i.e., DLC_START_DL). For other implementations, this additional exchange may not be required.
In the figure, the transition labeled HALT_DL(ts) represents the HALT_PENDING state and the transition labeled RESTART_DL(ts) represents the RESTART_PENDING state. Both these transitional states have only one input event and only one output action. While in these states, the Data Link Switch is awaiting responses from the local station on the adjacent LAN (i.e., a UA response to a DISC command). Also in the RESTART_PENDING state, the Data Link Switch will attempt to restart the data link prior to sending a DL_RESTARTED message. For the IBM 6611 implementation, the start of a data link involves the exchange of a Test command/response on the adjacent LAN (i.e., DLC_START_DL). For other implementations, this additional exchange may not be required.
4.2.2. State Transition Tables
4.2.2. State Transition Tables
This section provides a detail representation of the Data Link Switch, as document by a set of state machines. The first state machine documents the sending and receiving of SSP messages. Many of the transitions are dependent upon local signals between the Data Link Switch entity and one of the DLC entities. These signals and their definitions are given in the following tables.
This section provides a detail representation of the Data Link Switch, as document by a set of state machines. The first state machine documents the sending and receiving of SSP messages. Many of the transitions are dependent upon local signals between the Data Link Switch entity and one of the DLC entities. These signals and their definitions are given in the following tables.
Dixon & Kushi [Page 21] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 21] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Event Name Description
---------- -----------
DLC_CONTACTED Contact Indication: DLC has received an SABME
command and will send a UA response, or DLC has
received a UA response as a result of sending an
SABME command.
DLC_DGRM Datagram Indication: DLC has received a UI frame.
DLC_ERROR Error condition indicated by DLC: Such a
condition occurs when a DISC command is received
or when DLC experiences an unrecoverable error.
DLC_INFO Information Indication: DLC has received an
Information (I) frame.
DLC_DL_HALTED Data Link Halted Indication: DLC has
received a UA response to a DISC command.
DLC_DL_STARTED Data Link Started Indication: DLC has
received a Test response from the null SAP.
DLC_RESET Reset Indication: DLC has received an SABME
command during the time a connection is
currently active and has responded with DM.
DLC_RESOLVE_C Resolve Command Indication: DLC has received
a Test command addressed to the null SAP, or an
XID command addressed to the null SAP.
DLC_XID XID Indication: DLC has received an XID command
or response to a non-null SAP.
Event Name Description ---------- ----------- DLC_CONTACTED Contact Indication: DLC has received an SABME command and will send a UA response, or DLC has received a UA response as a result of sending an SABME command. DLC_DGRM Datagram Indication: DLC has received a UI frame. DLC_ERROR Error condition indicated by DLC: Such a condition occurs when a DISC command is received or when DLC experiences an unrecoverable error. DLC_INFO Information Indication: DLC has received an Information (I) frame. DLC_DL_HALTED Data Link Halted Indication: DLC has received a UA response to a DISC command. DLC_DL_STARTED Data Link Started Indication: DLC has received a Test response from the null SAP. DLC_RESET Reset Indication: DLC has received an SABME command during the time a connection is currently active and has responded with DM. DLC_RESOLVE_C Resolve Command Indication: DLC has received a Test command addressed to the null SAP, or an XID command addressed to the null SAP. DLC_XID XID Indication: DLC has received an XID command or response to a non-null SAP.
Table 3. Local DLC Events
Table 3. Local DLC Events
Action Name Description
----------- -----------
DLC_CONTACT Contact Station Request: DLC will send a SABME
command.
DLC_DGRM Datagram Request: DLC will send a UI frame.
DLC_ENTER_BUSY Enter Link Station Busy: DLC will send an
RNR supervisory frame.
DLC_EXIT_BUSY Exit Link Station Busy: DLC will send an RR
supervisory frame.
DLC_HALT_DL Halt Data Link Request: DLC will send a DISC
command.
DLC_INFO Information Request: DLC will send an I frame.
DLC_RESOLVE_R Resolve Response Request: DLC will send a
Test response or XID response from the null SAP.
DLC_START_DL Start Data Link Request: DLC will send a Test
command to the null SAP.
DLC_XID XID Request: DLC will send an XID command or an
XID response.
Action Name Description ----------- ----------- DLC_CONTACT Contact Station Request: DLC will send a SABME command. DLC_DGRM Datagram Request: DLC will send a UI frame. DLC_ENTER_BUSY Enter Link Station Busy: DLC will send an RNR supervisory frame. DLC_EXIT_BUSY Exit Link Station Busy: DLC will send an RR supervisory frame. DLC_HALT_DL Halt Data Link Request: DLC will send a DISC command. DLC_INFO Information Request: DLC will send an I frame. DLC_RESOLVE_R Resolve Response Request: DLC will send a Test response or XID response from the null SAP. DLC_START_DL Start Data Link Request: DLC will send a Test command to the null SAP. DLC_XID XID Request: DLC will send an XID command or an XID response.
Table 4. Local DLC Actions
Table 4. Local DLC Actions
Dixon & Kushi [Page 22] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 22] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
The Data Link Switch may be described by a state transition table consisting of eleven states. Each of these states is described below in terms of the events, actions, and next state for each transition. If a particular event is not listed for a given state, no action and no state transition should occur for that event. Any significant comments concerning the transitions within a given state are given immediately following the table representing the state.
The Data Link Switch may be described by a state transition table consisting of eleven states. Each of these states is described below in terms of the events, actions, and next state for each transition. If a particular event is not listed for a given state, no action and no state transition should occur for that event. Any significant comments concerning the transitions within a given state are given immediately following the table representing the state.
A separate state machine is maintained by the Data Link Switch for each end-to-end circuit. The number of circuits that may be supported by each Data Link Switch is a local implementation option.
A separate state machine is maintained by the Data Link Switch for each end-to-end circuit. The number of circuits that may be supported by each Data Link Switch is a local implementation option.
4.2.2.1 DISCONNECTED State
4.2.2.1 DISCONNECTED State
Event Action(s) Next State
----- --------- ----------
Receive CANUREACH DLC_START_DL RESOLVE_PENDING
Receive ICANREACH Send REACH_ACK, CIRCUIT_ESTABLISHED
DLC_RESOLVE_R
(See note 1)
Receive DATAFRAME DLC_DGRM
Receive NETBIOS_NQ DLC_DGRM RESOLVE_PENDING
Receive NETBIOS_NR Send REACH_ACK, CIRCUIT_ESTABLISHED
DLC_DGRM
(See note 2)
DLC_RESOLVE_C Send CANUREACH
DLC_DGRM If NB_Name_Query:
Send NETBIOS_NQ,
Else:
Send DATAFRAME
Event Action(s) Next State ----- --------- ---------- Receive CANUREACH DLC_START_DL RESOLVE_PENDING Receive ICANREACH Send REACH_ACK, CIRCUIT_ESTABLISHED DLC_RESOLVE_R (See note 1) Receive DATAFRAME DLC_DGRM Receive NETBIOS_NQ DLC_DGRM RESOLVE_PENDING Receive NETBIOS_NR Send REACH_ACK, CIRCUIT_ESTABLISHED DLC_DGRM (See note 2) DLC_RESOLVE_C Send CANUREACH DLC_DGRM If NB_Name_Query: Send NETBIOS_NQ, Else: Send DATAFRAME
It is assumed that each Data Link Switch will build a set of topology tables giving the identity of each Data Link Switch that can reach a specific MAC address or a specific NetBIOS name. This table can be built based upon the origin address information received within the CANUREACH message or NETBIOS_NQ message and the target address information within the ICANREACH message or NETBIOS_NR message. As a consequence, the amount of search traffic can be kept to a minimum.
It is assumed that each Data Link Switch will build a set of topology tables giving the identity of each Data Link Switch that can reach a specific MAC address or a specific NetBIOS name. This table can be built based upon the origin address information received within the CANUREACH message or NETBIOS_NQ message and the target address information within the ICANREACH message or NETBIOS_NR message. As a consequence, the amount of search traffic can be kept to a minimum.
Upon receipt of a Test command or XID command to the null SAP (i.e., DLC_RESOLVE_C signal from DLC), the Data Link Switch will check the topology table prior to sending the CANUREACH message. If the target MAC address is in the table, the CANUREACH message will be sent to only those Data Link Switches that are known to be able to reach the given MAC address. If the MAC address is not in the table, the CANUREACH message will be sent to all known Data Link Switches. Since the destination link SAP (DSAP) value is null, the Target Link SAP field in the CANUREACH message header is set equal to the Origin
Upon receipt of a Test command or XID command to the null SAP (i.e., DLC_RESOLVE_C signal from DLC), the Data Link Switch will check the topology table prior to sending the CANUREACH message. If the target MAC address is in the table, the CANUREACH message will be sent to only those Data Link Switches that are known to be able to reach the given MAC address. If the MAC address is not in the table, the CANUREACH message will be sent to all known Data Link Switches. Since the destination link SAP (DSAP) value is null, the Target Link SAP field in the CANUREACH message header is set equal to the Origin
Dixon & Kushi [Page 23] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 23] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Link SAP value.
Link SAP value.
Upon receipt of a NB_Name_Query the Data Link Switch will check the topology table prior to sending the NETBIOS_NQ message. If the target NetBIOS name is in the table, the NETBIOS_NQ message will be sent to only those Data Link Switches that are known to be able to reach the given NetBIOS name. If the NetBIOS name is not in the table, the NETBIOS_NQ message will be sent to all known Data Link Switches.
Upon receipt of a NB_Name_Query the Data Link Switch will check the topology table prior to sending the NETBIOS_NQ message. If the target NetBIOS name is in the table, the NETBIOS_NQ message will be sent to only those Data Link Switches that are known to be able to reach the given NetBIOS name. If the NetBIOS name is not in the table, the NETBIOS_NQ message will be sent to all known Data Link Switches.
For SNA, the DISCONNECTED state is exited upon receipt of a CANUREACH message by a prospective target Data Link Switch, or upon receipt of an ICANREACH message by the origin Data Link Switch. In the former case, the Data Link Switch will issue a Test command to the target station (i.e., DLC_START_DL signal is presented to DLC). In the later case, a Test response is sent to the origin station (i.e., DLC_RESOLVE_R will be issued) and a REACH_ACK message will be returned to the target Data Link Switch.
For SNA, the DISCONNECTED state is exited upon receipt of a CANUREACH message by a prospective target Data Link Switch, or upon receipt of an ICANREACH message by the origin Data Link Switch. In the former case, the Data Link Switch will issue a Test command to the target station (i.e., DLC_START_DL signal is presented to DLC). In the later case, a Test response is sent to the origin station (i.e., DLC_RESOLVE_R will be issued) and a REACH_ACK message will be returned to the target Data Link Switch.
Note 1- The IBM 6611 will not send a Test response, but will send
a Test command to the station that originated the resolve
procedure (i.e., a DLC_START_DL will be issued) in order to start
the data link.
Note 1- The IBM 6611 will not send a Test response, but will send a Test command to the station that originated the resolve procedure (i.e., a DLC_START_DL will be issued) in order to start the data link.
For NetBIOS, the DISCONNECTED state is exited upon the receipt of a NETBIOS_NQ message by the prospective target Data Link Switch, or upon the receipt of a NETBIOS_NR message by the origin Data Link Switch. In the former case, the Data Link Switch will send a NB_Name_Query frame. In the later case, the Data Link Switch will send a NB_Name_Recognized frame to the origin station and a REACH_ACK message will be returned to the target Data Link Switch.
For NetBIOS, the DISCONNECTED state is exited upon the receipt of a NETBIOS_NQ message by the prospective target Data Link Switch, or upon the receipt of a NETBIOS_NR message by the origin Data Link Switch. In the former case, the Data Link Switch will send a NB_Name_Query frame. In the later case, the Data Link Switch will send a NB_Name_Recognized frame to the origin station and a REACH_ACK message will be returned to the target Data Link Switch.
Note 2- The IBM 6611 will also send a Test command (i.e., a
DLC_START_DL will be issued) to the station that originated the
name resolution in order to start the data link.
Note 2- The IBM 6611 will also send a Test command (i.e., a DLC_START_DL will be issued) to the station that originated the name resolution in order to start the data link.
4.2.2.2 RESOLVE_PENDING State
4.2.2.2 RESOLVE_PENDING State
Event Action(s) Next State
----- --------- ----------
Receive DATAFRAME DLC_DGRM
DLC_DL_STARTED Send ICANREACH CIRCUIT_PENDING
DLC_ERROR DISCONNECTED
DLC_DGRM If NB_Name_Recognized: If
Send NETBIOS_NR NB_Name_Recognized:
(See note), CIRCUIT_PENDING
Else:
Send DATAFRAME
Event Action(s) Next State ----- --------- ---------- Receive DATAFRAME DLC_DGRM DLC_DL_STARTED Send ICANREACH CIRCUIT_PENDING DLC_ERROR DISCONNECTED DLC_DGRM If NB_Name_Recognized: If Send NETBIOS_NR NB_Name_Recognized: (See note), CIRCUIT_PENDING Else: Send DATAFRAME
Dixon & Kushi [Page 24] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 24] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
The RESOLVE_PENDING state is entered upon receipt of a CANUREACH message or a NETBIOS_NQ message by the target DLS. In the former case, a data link is started, causing a Test command to be sent by the DLC. In the later case, a NB_Name_Query frame is sent. This frame is directed to a group MAC address.
The RESOLVE_PENDING state is entered upon receipt of a CANUREACH message or a NETBIOS_NQ message by the target DLS. In the former case, a data link is started, causing a Test command to be sent by the DLC. In the later case, a NB_Name_Query frame is sent. This frame is directed to a group MAC address.
Any CANUREACH messages received in the RESOLVE_PENDING state will be responded to if a DLC_DL_STARTED signal is received. The Data Link Switch may also update its topology information based upon the origin MAC address information in each CANUREACH message.
Any CANUREACH messages received in the RESOLVE_PENDING state will be responded to if a DLC_DL_STARTED signal is received. The Data Link Switch may also update its topology information based upon the origin MAC address information in each CANUREACH message.
Upon the receipt of a DLC_DL_STARTED signal in the RESOLVE_PENDING state, the Data Link Switch may update its topology table base upon the remote MAC address information. The ICANREACH message should be returned to all Data Link Switches that had sent a CANUREACH message. In a similar fashion, the Data Link Switch may update its topology table upon the receipt of a NB_Name_Recognized frame and a NETBIOS_NR message will be returned to all Data Link Switches that have sent a NETBIOS_NQ message.
Upon the receipt of a DLC_DL_STARTED signal in the RESOLVE_PENDING state, the Data Link Switch may update its topology table base upon the remote MAC address information. The ICANREACH message should be returned to all Data Link Switches that had sent a CANUREACH message. In a similar fashion, the Data Link Switch may update its topology table upon the receipt of a NB_Name_Recognized frame and a NETBIOS_NR message will be returned to all Data Link Switches that have sent a NETBIOS_NQ message.
The RESOLVE_PENDING state is exited once the data link has been started (i.e., a DLC_DL_STARTED signal is received as a result of a Test response received by the DLC) or a NB_Name_Recognized frame is received (i.e., a DLC_DGRM signal is received). The target Data Link Switch will then enter the CIRCUIT_PENDING state.
The RESOLVE_PENDING state is exited once the data link has been started (i.e., a DLC_DL_STARTED signal is received as a result of a Test response received by the DLC) or a NB_Name_Recognized frame is received (i.e., a DLC_DGRM signal is received). The target Data Link Switch will then enter the CIRCUIT_PENDING state.
Note: The IBM 6611 will also send a Test command in order to
start the data link to the station that responded to the Name
Query frame (i.e., a DLC_START_DL will be issued).
Note: The IBM 6611 will also send a Test command in order to start the data link to the station that responded to the Name Query frame (i.e., a DLC_START_DL will be issued).
4.2.2.3 CIRCUIT_PENDING State
4.2.2.3 CIRCUIT_PENDING State
Event Action(s) Next State
----- --------- ----------
Receive CONTACT DLC_CONTACT CONTACT_PENDING
Receive HALT_DL DLC_HALT_DL HALT_PENDING
Receive REACH_ACK If Connected: If Connected:
Send CONTACT CONNECT_PENDING,
else: CIRCUIT_ESTABLISHED
Receive XIDFRAME DLC_XID
Receive DGRMFRAME DLC_DGRM
Receive DATAFRAME DLC_DGRM
DLC_CONTACTED DLC_ENTER_BUSY
DLC_ERROR Send HALT_DL DISCONNECT_PENDING
DLC_XID Send XIDFRAME
DLC_DGRM Send DGRMFRAME
Event Action(s) Next State ----- --------- ---------- Receive CONTACT DLC_CONTACT CONTACT_PENDING Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive REACH_ACK If Connected: If Connected: Send CONTACT CONNECT_PENDING, else: CIRCUIT_ESTABLISHED Receive XIDFRAME DLC_XID Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_CONTACTED DLC_ENTER_BUSY DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_XID Send XIDFRAME DLC_DGRM Send DGRMFRAME
Dixon & Kushi [Page 25] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 25] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
The CIRCUIT_PENDING state is entered by the target Data Link Switch following the sending of an ICANREACH message or the sending of a NETBIOS_NR message. In this state it is awaiting the reception of a REACH_ACK message from the origin Data Link Switch. If a connection does not exist with the target station (i.e., the normal case), the Data Link Switch will enter the CIRCUIT_ESTABLISHED state.
The CIRCUIT_PENDING state is entered by the target Data Link Switch following the sending of an ICANREACH message or the sending of a NETBIOS_NR message. In this state it is awaiting the reception of a REACH_ACK message from the origin Data Link Switch. If a connection does not exist with the target station (i.e., the normal case), the Data Link Switch will enter the CIRCUIT_ESTABLISHED state.
If the target Data Link Switch happens to receive a SABME command from the target station while in the CIRCUIT_PENDING state (i.e., a DLC_CONTACTED signal received from the DLC), the reception of the REACH_ACK message will cause the Data Link Switch to enter the CONNECT_PENDING state and to send a CONTACT message to the other Data Link Switch. Thus the target Data Link Switch has assumed the role of the origin Data Link Switch.
If the target Data Link Switch happens to receive a SABME command from the target station while in the CIRCUIT_PENDING state (i.e., a DLC_CONTACTED signal received from the DLC), the reception of the REACH_ACK message will cause the Data Link Switch to enter the CONNECT_PENDING state and to send a CONTACT message to the other Data Link Switch. Thus the target Data Link Switch has assumed the role of the origin Data Link Switch.
4.2.2.4 CONNECT_PENDING State
4.2.2.4 CONNECT_PENDING State
Event Action(s) Next State ----- --------- ---------- Receive CONTACTED DLC_EXIT_BUSY CONNECTED Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_RESET Send RESTART_DL (See note) CIRCUIT_RESTART DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME
Event Action(s) Next State ----- --------- ---------- Receive CONTACTED DLC_EXIT_BUSY CONNECTED Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_RESET Send RESTART_DL (See note) CIRCUIT_RESTART DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME
The CONNECT_PENDING state is entered by the origin Data Link Switch when a DLC_CONTACTED signal has been received from the DLC (i.e., a SABME command has been received). A CONTACT message is then issued. The state is exited upon the receipt of a CONTACTED message from the target Data Link Switch. If a DLC_RESET signal is received, the local data link is restarted and a RESTART_DL message is sent to the remote DLS.
The CONNECT_PENDING state is entered by the origin Data Link Switch when a DLC_CONTACTED signal has been received from the DLC (i.e., a SABME command has been received). A CONTACT message is then issued. The state is exited upon the receipt of a CONTACTED message from the target Data Link Switch. If a DLC_RESET signal is received, the local data link is restarted and a RESTART_DL message is sent to the remote DLS.
Note: The IBM 6611 will also send a Test command in order to
restart the data link to the station that sent the SABME command
(i.e., a DLC_START_DL will be issued).
Note: The IBM 6611 will also send a Test command in order to restart the data link to the station that sent the SABME command (i.e., a DLC_START_DL will be issued).
Dixon & Kushi [Page 26] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 26] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
4.2.2.5 CIRCUIT_ESTABLISHED State
4.2.2.5 CIRCUIT_ESTABLISHED State
Event Action(s) Next State
----- --------- ----------
Receive CONTACT DLC_CONTACT CONTACT_PENDING
Receive HALT_DL DLC_HALT_DL HALT_PENDING
Receive XIDFRAME DLC_XID
Receive DGRMFRAME DLC_DGRM
Receive DATAFRAME DLC_DGRM
DLC_CONTACTED Send CONTACT CONNECT_PENDING
DLC_ENTER_BUSY
DLC_ERROR Send HALT_DL DISCONNECT_PENDING
DLC_DGRM Send DGRMFRAME
DLC_XID Send XIDFRAME
Event Action(s) Next State ----- --------- ---------- Receive CONTACT DLC_CONTACT CONTACT_PENDING Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive XIDFRAME DLC_XID Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_CONTACTED Send CONTACT CONNECT_PENDING DLC_ENTER_BUSY DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME DLC_XID Send XIDFRAME
The CIRCUIT_ESTABLISHED state is entered by the origin Data Link Switch from the DISCONNECTED state, and by the target Data Link Switch from the CIRCUIT_PENDING state. The state is exited when a connection is started (i.e., DLC receives a SABME command). The next state is CONTACT_PENDING for the target Data Link Switch and CONNECT_PENDING for the origin Data Link Switch.
The CIRCUIT_ESTABLISHED state is entered by the origin Data Link Switch from the DISCONNECTED state, and by the target Data Link Switch from the CIRCUIT_PENDING state. The state is exited when a connection is started (i.e., DLC receives a SABME command). The next state is CONTACT_PENDING for the target Data Link Switch and CONNECT_PENDING for the origin Data Link Switch.
4.2.2.6 CONTACT_PENDING State
4.2.2.6 CONTACT_PENDING State
Event Action(s) Next State ----- --------- ---------- Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive RESTART_DL DLC_HALT_DL RESTART_PENDING Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_CONTACTED Send CONTACTED CONNECTED DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME
Event Action(s) Next State ----- --------- ---------- Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive RESTART_DL DLC_HALT_DL RESTART_PENDING Receive DGRMFRAME DLC_DGRM Receive DATAFRAME DLC_DGRM DLC_CONTACTED Send CONTACTED CONNECTED DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME
The CONTACT_PENDING state is entered by the target Data Link Switch upon the receipt of a CONTACT message. This causes the Data Link Switch to issue a DLC_CONTACT signal to the DLC (i.e., DLC sends a SABME command). This state is then exited upon the receipt of a DLC_CONTACTED signal from the DLC (i.e., a UA response received).
The CONTACT_PENDING state is entered by the target Data Link Switch upon the receipt of a CONTACT message. This causes the Data Link Switch to issue a DLC_CONTACT signal to the DLC (i.e., DLC sends a SABME command). This state is then exited upon the receipt of a DLC_CONTACTED signal from the DLC (i.e., a UA response received).
If a RESTART_DL message is received, indicating that the remote Data Link Switch has received a DLC_RESET signal, the local Data Link Switch will send a DISC command frame on the adjacent LAN (i.e., DLC_HALT_DL signal) and enter the RESTART_PENDING state.
If a RESTART_DL message is received, indicating that the remote Data Link Switch has received a DLC_RESET signal, the local Data Link Switch will send a DISC command frame on the adjacent LAN (i.e., DLC_HALT_DL signal) and enter the RESTART_PENDING state.
Dixon & Kushi [Page 27] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 27] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
4.2.2.7 CONNECTED State
4.2.2.7 CONNECTED State
Event Action(s) Next State ----- --------- ---------- Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive RESTART_DL DLC_HALT_DL RESTART_PENDING Receive DGRMFRAME DLC_DGRM Receive INFOFRAME DLC_INFO Receive DATAFRAME DLC_DGRM DLC_RESET Send RESTART_DL (See note) CIRCUIT_RESTART DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME DLC_INFO Send INFOFRAME
Event Action(s) Next State ----- --------- ---------- Receive HALT_DL DLC_HALT_DL HALT_PENDING Receive RESTART_DL DLC_HALT_DL RESTART_PENDING Receive DGRMFRAME DLC_DGRM Receive INFOFRAME DLC_INFO Receive DATAFRAME DLC_DGRM DLC_RESET Send RESTART_DL (See note) CIRCUIT_RESTART DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DGRMFRAME DLC_INFO Send INFOFRAME
The CONNECTED state is entered by the origin Data Link Switch from the CONNECT_PENDING state upon the receipt of a CONTACTED message. The CONNECTED state is entered by the target Data Link Switch from the CONTACT_PENDING state upon the receipt of a DLC_CONTACTED signal. At this time, the target Data Link Switch will return a CONTACTED message to the origin Data Link Switch.
The CONNECTED state is entered by the origin Data Link Switch from the CONNECT_PENDING state upon the receipt of a CONTACTED message. The CONNECTED state is entered by the target Data Link Switch from the CONTACT_PENDING state upon the receipt of a DLC_CONTACTED signal. At this time, the target Data Link Switch will return a CONTACTED message to the origin Data Link Switch.
The CONNECTED state is exited usually under one of two conditions: a DLC_ERROR signal received from the DLC (e.g., a DISC command received by the local DLC), or a HALT_DL message received from the other Data Link Switch (e.g., a DISC command received by the remote DLC).
The CONNECTED state is exited usually under one of two conditions: a DLC_ERROR signal received from the DLC (e.g., a DISC command received by the local DLC), or a HALT_DL message received from the other Data Link Switch (e.g., a DISC command received by the remote DLC).
A SABME command (i.e., a DLC_RESET signal) received by either Data Link Switch will also cause the two Data Link Switches to leave the CONNECTED state and eventually restart a new circuit.
A SABME command (i.e., a DLC_RESET signal) received by either Data Link Switch will also cause the two Data Link Switches to leave the CONNECTED state and eventually restart a new circuit.
Note: The IBM 6611 will also send a Test command in order to
restart the data link to the station that sent the SABME command
(i.e., a DLC_START_DL will be issued).
Note: The IBM 6611 will also send a Test command in order to restart the data link to the station that sent the SABME command (i.e., a DLC_START_DL will be issued).
Following the receipt of a reset signal, the Data Link Switch will send a RESTART_DL message to the other Data Link Switch and will enter the CIRCUIT_RESTART state. Upon the receipt of the RESTART_DL message, the remote Data Link Switch will send a DISC command (i.e., DLC_HALT_DL signal) and enter the RESTART_PENDING state.
Following the receipt of a reset signal, the Data Link Switch will send a RESTART_DL message to the other Data Link Switch and will enter the CIRCUIT_RESTART state. Upon the receipt of the RESTART_DL message, the remote Data Link Switch will send a DISC command (i.e., DLC_HALT_DL signal) and enter the RESTART_PENDING state.
4.2.2.8 CIRCUIT_RESTART State
4.2.2.8 CIRCUIT_RESTART State
Event Action(s) Next State
----- --------- ----------
Receive DL_RESTARTED If Connected: If Connected:
Send CONTACT CONNECT_PENDING,
else: CIRCUIT_ESTABLISHED
Receive DATAFRAME DLC_DGRM
Event Action(s) Next State ----- --------- ---------- Receive DL_RESTARTED If Connected: If Connected: Send CONTACT CONNECT_PENDING, else: CIRCUIT_ESTABLISHED Receive DATAFRAME DLC_DGRM
Dixon & Kushi [Page 28] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 28] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DATAFRAME
DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DATAFRAME
The CIRCUIT_RESTART state is entered if a DLC_RESET signal is received from the local DLC. This was caused by the receipt of a SABME command while a connection was currently active. A DM response will be issued to the SABME command and the Data Link Switch will attempt to restart the end-to- end circuit.
The CIRCUIT_RESTART state is entered if a DLC_RESET signal is received from the local DLC. This was caused by the receipt of a SABME command while a connection was currently active. A DM response will be issued to the SABME command and the Data Link Switch will attempt to restart the end-to- end circuit.
The CIRCUIT_RESTART state is exited through one of two transitions. The next state depends upon the time the local DLC has reached the contacted state (i.e., a DLC_CONTACTED signal is presented) relative to the receipt of the DL_RESTARTED message. This signal is caused by the origin station resending the SABME command that initially caused the DATA Link Switch to enter the CIRCUIT_RESTART state. The two cases are as follows:
The CIRCUIT_RESTART state is exited through one of two transitions. The next state depends upon the time the local DLC has reached the contacted state (i.e., a DLC_CONTACTED signal is presented) relative to the receipt of the DL_RESTARTED message. This signal is caused by the origin station resending the SABME command that initially caused the DATA Link Switch to enter the CIRCUIT_RESTART state. The two cases are as follows:
1) DL_RESTARTED message received before the
DLC_CONTACTED signal- In this case, the
CIRCUIT_ESTABLISHED state is entered.
1) DL_RESTARTED message received before the DLC_CONTACTED signal- In this case, the CIRCUIT_ESTABLISHED state is entered.
2) DL_RESTARTED message received after the
DLC_CONTACTED signal- In this case, the
CONNECT_PENDING state is entered.
2) DL_RESTARTED message received after the DLC_CONTACTED signal- In this case, the CONNECT_PENDING state is entered.
4.2.2.9 DISCONNECT_PENDING State
4.2.2.9 DISCONNECT_PENDING State
Event Action(s) Next State
----- --------- ----------
Receive DL_HALTED DISCONNECTED
Receive HALT_DL Send DL_HALTED
Receive DATAFRAME DLC_DGRM
DLC_DGRM Send DATAFRAME
Event Action(s) Next State ----- --------- ---------- Receive DL_HALTED DISCONNECTED Receive HALT_DL Send DL_HALTED Receive DATAFRAME DLC_DGRM DLC_DGRM Send DATAFRAME
The DISCONNECT_PENDING state is entered when a DLC_ERROR signal is received from the local DLC. Upon receipt of this signal, a HALT message is sent. Once an DL_HALTED message is received, the state is exited, and the Data Link Switch enters the DISCONNECTED state.
The DISCONNECT_PENDING state is entered when a DLC_ERROR signal is received from the local DLC. Upon receipt of this signal, a HALT message is sent. Once an DL_HALTED message is received, the state is exited, and the Data Link Switch enters the DISCONNECTED state.
4.2.2.10 RESTART_PENDING State
4.2.2.10 RESTART_PENDING State
Event Action(s) Next State
----- --------- ----------
Receive DATAFRAME DLC_DGRM
DLC_DL_HALTED (See note) Send DL_RESTARTED CIRCUIT_ESTABLISHED
DLC_ERROR Send HALT_DL DISCONNECT_PENDING
DLC_DGRM Send DATAFRAME
Event Action(s) Next State ----- --------- ---------- Receive DATAFRAME DLC_DGRM DLC_DL_HALTED (See note) Send DL_RESTARTED CIRCUIT_ESTABLISHED DLC_ERROR Send HALT_DL DISCONNECT_PENDING DLC_DGRM Send DATAFRAME
Dixon & Kushi [Page 29] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
Dixon & Kushi [Page 29] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
The RESTART_PENDING state is entered upon the receipt of a RESTART_DL message from the remote DLS while the local Data Link Switch is in either the CONTACT_PENDING state or the CONNECTED state. These cause the local DLC to issue a DISC command. Upon the receipt of the UA response (DLC_DL_HALTED), the data link is restarted, a DL_RESTARTED message is returned to the remote DLS, and the CIRCUIT_ESTABLISHED state is entered.
The RESTART_PENDING state is entered upon the receipt of a RESTART_DL message from the remote DLS while the local Data Link Switch is in either the CONTACT_PENDING state or the CONNECTED state. These cause the local DLC to issue a DISC command. Upon the receipt of the UA response (DLC_DL_HALTED), the data link is restarted, a DL_RESTARTED message is returned to the remote DLS, and the CIRCUIT_ESTABLISHED state is entered.
Note: The IBM 6611 will send a Test command in order to restart
the data link to the target station (i.e., a DLC_START_DL will be
issued) prior to sending the DL_RESTARTED message.
Note: The IBM 6611 will send a Test command in order to restart the data link to the target station (i.e., a DLC_START_DL will be issued) prior to sending the DL_RESTARTED message.
4.2.2.11 HALT_PENDING State
4.2.2.11 _未定の状態を止めてください。
Event Action(s) Next State
----- --------- ----------
Receive DATAFRAME DLC_DGRM
DLC_DL_HALTED Send DL_HALTED DISCONNECTED
DLC_ERROR Send DL_HALTED DISCONNECTED
DLC_DGRM Send DATAFRAME
次の動きが述べるイベント----- --------- ---------- 受信、_dl_が止めたDATAFRAME DLC_DGRM DLCは_の停止している切断しているDLC_DGRMがDATAFRAMEを送るdlを_の停止している切断しているDLC_誤りが送るdlに送ります。
The HALT_PENDING state is entered upon the receipt of a HALT_DL message. This causes the local DLC to issue a DISC command. Upon the receipt of the UA response (DLC_DL_HALTED), a DL_HALTED message is returned to the remote DLS and the DISCONNECTED state is entered.
HALT_PENDING状態はHALT_DLメッセージの領収書で入られます。 これで、地方のDLCはDISCコマンドを発行します。 UA応答(DLC_DL_HALTED)の領収書で、DL_HALTEDメッセージをリモートDLSに返します、そして、DISCONNECTED状態を入れます。
4.3. NetBIOS Datagrams
4.3. NetBIOSデータグラム
The NetBIOS protocols use a number of UI frames for directory services and the transmission of datagrams. Most of these frames are directed to a group MAC address (GA) with the routing information field indicating spanning tree explorer (STE). Two of the frames, NB_Add_Name_Response and NB_Status_Response, are directed to a specific MAC address with the routing information field indicating a specifically routed frame (SRF). The handling of these frames is summarized in the following table.
NetBIOSプロトコルはディレクトリサービスのための多くのUIフレームとデータグラムのトランスミッションを使用します。ルーティング情報フィールドがスパニングツリー探検家(STE)を示していて、これらのフレームの大部分はグループMACアドレス(ジョージア)に向けられます。 フレーム、_ネブラスカAdd_Name_Response、および_ネブラスカStatus_では、Responseは向けられます。2、特定のMACに、ルーティング情報フィールドが明確に発送されたフレームを示していて、(SRF)を扱ってください。 これらのフレームの取り扱いは以下のテーブルにまとめられます。
Event Action(s) Comment
----- --------- -------
DLC_DGRM (NB Group Address): Send NETBIOS_ANQ Transmitted to all
NB_Add_Name_Query remote DLS
DLC_DGRM (Specific Address): Send NETBIOS_ANR Transmitted to
NB_Add_Name_Response specific DLS
DLC_DGRM (Specific Address): Send DATAFRAME Transmitted to all
NB_Status_Response remote DLS
DLC_DGRM (NB Group Address): Send DATAFRAME Transmitted to all
NB_Name_in_Conflict, remote DLS
NB_Add_Group_Name_Query,
イベント動作コメント----- --------- ------- DLC_DGRM(ネブラスカグループアドレス): すべての_のName_Queryのリモートネブラスカ_Add DLS DLC_DGRM(特定のAddress)にNETBIOS_ANQ Transmittedを送ってください: _のName_Responseの特定のネブラスカ_Add DLS DLC_DGRM(特定のAddress)にNETBIOS_ANR Transmittedを送ってください: _すべてのネブラスカのStatus_ResponseのリモートDLS DLC_DGRM(ネブラスカGroup Address)にDATAFRAME Transmittedを送ってください: __ConflictのすべてのネブラスカName_、リモート__DLS NB_Add Group_Name QueryにDATAFRAME Transmittedを送ってください。
Dixon & Kushi [Page 30] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[30ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
NB_Datagram,
NB_Datagram_Broadcast,
NB_Status_Query,
NB_Terminate_Trace
ネブラスカ_データグラム_が、ネブラスカ_状態_が質問するのを放送するネブラスカ_データグラム、Nb_は_跡を終えます。
Table 5. NetBIOS DLC Frames
5を見送ってください。 NetBIOS DLCフレーム
The above actions do not apply in the following states: CIRCUIT_ESTABLISHED, CONTACT_PENDING, CONNECT_PENDING, CONNECTED, and CIRCUIT_PENDING. The handling of the remaining two UI frames used by NetBIOS systems, NB_Name_Query and NB_Name_Recognized, are documented as part of the DLS state machine in the previous section (i.e., DISCONNECTED and RESOLVE_PENDING states). Furthermore, the handling of NetBIOS datagrams (i.e., NB_Datagram) sent to a specific MAC address is also governed by the DLS state machine.
上の動作は以下の州で適用されません: _が確立した回路、未定の接触_は未定の_、未定の接続されるのと回路の_を接続します。 システム_ネブラスカName_Queryと_(ネブラスカName_Recognized)が記録されるNetBIOSが使用された2個の残っているUIフレームの取り扱いは前項(すなわち、DISCONNECTEDとPENDINGが述べるRESOLVE_)でDLS州のマシンを離れさせます。 その上、また、特定のMACアドレスに送られたNetBIOSデータグラム(すなわち、ネブラスカ_データグラム)の取り扱いはDLS州のマシンによって治められます。
Note: The IBM 6611 will also issue Test frames during the
exchange of the NetBIOS, NB_Name_Query and NB_Name_Recognized.
This exchange of protocol data units occurs during the start of a
data link and is used to determine the routing information. Most
other implementations of NetBIOS will use the
NB_Name_Query/NB_Name_Recognized exchange to determine routes in
conjunction with resolving the NetBIOS names. These differences
are not reflected in the SSP protocols.
以下に注意してください。 また、IBM6611はNetBIOS、ネブラスカの_Name_Queryと_ネブラスカName_Recognizedの交換の間、Testにフレームを発行するでしょう。 プロトコルデータ単位のこの交換は、データ・リンクの始まりの間、起こって、ルーティング情報を決定するのに使用されます。 NetBIOSの他のほとんどの実装が、NetBIOS名を決議することに関連してルートを決定するのにネブラスカ_Name_Query/ネブラスカ_Name_Recognized交換を使用するでしょう。 これらの違いはSSPプロトコルに反映されません。
The handling of the NetBIOS specific SSP messages is given in the following table.
以下のテーブルでNetBIOSの特定のSSPメッセージの取り扱いを与えます。
Event Action(s) Comment
----- --------- -------
NETBIOS_ANQ DLC_DGRM: Routed STE
NB_Add_Name_Query (NB Group Address)
NETBIOS_ANR DLC_DGRM: Routed SRF
NB_Add_Name_Response (Specific MAC Address)
NETBIOS_NQ DLC_DGRM: Routed STE
NB_Name_Query (NB Group Address)
NETBIOS_NR DLC_DGRM: Routed SRF
NB_Name_Recognized (Specific MAC Address)
DATAFRAME DLC_DGRM Routed STE
(If NB_Status_Response:
Specific MAC Address
Else: NB Group Address)
イベント動作コメント----- --------- ------- NETBIOS_ANQ DLC_DGRM: 発送されたSTEネブラスカ_は_名前_質問(ネブラスカグループアドレス)NETBIOS_ANR DLC_DGRMを加えます: 発送されたSRFネブラスカ_は_名前_応答(特定のマックーアドレス)NETBIOS_NQ DLC_DGRMを加えます: 発送されたSTEネブラスカ_は_質問(ネブラスカグループアドレス)NETBIOS_をNR DLC_DGRMと命名します: 発送されたSRFネブラスカ_名前_は、(特定のマックーアドレス)DATAFRAME DLC_DGRMがSTEを発送したと認めました。(Nb_状態_応答: 特定のほかのマックーアドレス: ネブラスカグループアドレスであるなら)
Table 6. NetBIOS SSP Messages
6を見送ってください。 NetBIOS SSPメッセージ
The above actions apply to all DLS states. The handling of NetBIOS datagrams sent within DGRMFRAME messages is governed by the DLS state machine. The DGRMFRAME message type is employed instead of the
上の動作はすべてのDLS州に適用されます。 DGRMFRAMEメッセージの中で送られたNetBIOSデータグラムの取り扱いはDLS州のマシンによって治められます。 の代わりにするDGRMFRAMEメッセージタイプが採用している。
Dixon & Kushi [Page 31] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[31ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
DATAFRAME message type once the end-to-end circuit has been established. At that time, the message is addressed according to the pair of Circuit IDs in the message header instead of relying upon the MAC address information in the token ring header.
終わりから端への回路がいったん確立されると、DATAFRAMEメッセージはタイプします。 その時、Circuit IDの組に従って、メッセージはトークンリングヘッダーでMACアドレス情報を当てにすることの代わりにメッセージヘッダーで扱われます。
Acknowledgments
承認
Randall Campbell, David Miller, Gene Cox, Ravi Periasamy, and The Ghost of Christmas Past.
ランドル・キャンベル、デヴィッド・ミラー、遺伝子がコックスを務めて、ラービーがPeriasamyであり、クリスマスの幽霊は過去です。
References
参照
1) ISO 8802-2/IEEE Std 802.2 International Standard,
Information Processing Systems, Local Area Networks, Part 2:
Logical Link Control, December 31, 1989
1) ISO8802-2/IEEE Std802.2国際規格、情報処理システム、ローカル・エリア・ネットワーク、第2部: 論理的なリンク制御、1989年12月31日
2) The NETBIOS Frames Protocol, IBM Local Area Technical
Reference, SC30-3383-03, Chapter 5, December 1990
2) NETBIOSは1990年12月にプロトコル、IBMの局部の技術的な参照、SC30-3383-03、第5章を縁どります。
3) ISO/IEC DIS 10038 DAM 2, MAC Bridging, Source Routing
Supplement, December 1991
3) ISO/IECは1991年12月に10038ダム2、MACのブリッジするソースルート設定補足をけなします。
Security Considerations
セキュリティ問題
Security issues are not discussed in this memo.
このメモで安全保障問題について議論しません。
Dixon & Kushi [Page 32] RFC 1434 DLS: Switch-to-Switch Protocol March 1993
ディクソンとKushi[32ページ]RFC1434dl: 1993年のスイッチからスイッチへのプロトコル行進
Authors' Addresses
作者のアドレス
Roy C. Dixon IBM Networking Systems Department B57, Building 060 P.O. Box 12195 Research Triangle Park, NC 27709
ロイC.ディクソンIBMネットワークシステム部のB57、ビル060P.O. Box12195リサーチトライアングル公園、NC 27709
Phone: (919) 543-3380 EMail: rcdixon@ralvmg.vnet.ibm.com
以下に電話をしてください。 (919) 543-3380 メールしてください: rcdixon@ralvmg.vnet.ibm.com
David M. Kushi IBM Research Division T. J. Watson Research Center Room H0-C07 30 Saw Mill River Road Hawthorne, NY 10532
デヴィッド・M.Kushi IBMのResearch事業部のT.J.ワトソン研究所のRoom H0-C07 30製材機械の川のRoadホーソーン、ニューヨーク 10532
Phone: (914) 784-7815 EMail: kushi@watson.ibm.com
以下に電話をしてください。 (914) 784-7815 メールしてください: kushi@watson.ibm.com
Note: Any questions or comments relative to the contents of this RFC should be sent to the following Internet address: dlsw@ralvma.vnet.ibm.com. This address will be used to coordinate the handling of responses.
以下に注意してください。 このRFCのコンテンツに比例したどんな質問やコメントも以下のインターネット・アドレスに送るべきです: dlsw@ralvma.vnet.ibm.com 。 このアドレスは、応答の取り扱いを調整するのに使用されるでしょう。
Dixon & Kushi [Page 33]
ディクソンとKushi[33ページ]
一覧
スポンサーリンク
