RFC1001：TCP/IP环境下的NetBIOS服务协议概述

下载需积分: 3 | PDF格式 | 88KB | 更新于2025-01-08 | 22 浏览量 | 举报

"RFC1001文档是1987年3月由Network Working Group发布的一份重要标准，名为'Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods'。这份RFC旨在为TCP/IP环境中的NetBIOS服务提供一个统一的协议规范，支持本地网络和互联网操作，并定义了不同的节点类型以适应各种网络拓扑结构，包括是否使用IP广播。文档的摘要部分涵盖了以下几个关键内容： 1. 状态和目的：首先，概述了该文档的当前状态，表明其为建议性标准，可能会根据反馈进行更新或修订。 2. 致谢：感谢了所有参与文档编写的人员和组织，强调了团队合作的重要性。 3. 介绍：介绍了文档的背景和目标，着重于解释在TCP/IP环境中引入NetBIOS服务的基本概念和方法。 4. 设计原则：详述了制定此标准时遵循的关键原则，可能涉及效率、兼容性和可扩展性等方面。 5. NetBIOS概述：对NetBIOS服务进行了基础介绍，可能涉及其在TCP/IP网络中的作用，以及它如何增强网络通信和资源管理。 6. 支持的服务和功能：列出了本标准所定义的NetBIOS服务和支持的特性，如名称解析、数据报传输等。 7. 必需的服务接口和定义：明确了服务接口的规格，包括客户端和服务端如何交互，以及相关的数据结构和协议元素。 8. 相关协议和服务：讨论了NetBIOS与TCP、UDP等其他协议的关系，以及可能存在的兼容性和互操作性问题。 9. NetBIOS的范围：界定了NetBIOS的应用场景，可能包括局域网(LAN)和广域网(WAN)，以及其在不同环境下的适用性。 10. NetBIOS节点类型：详细说明了不同类型节点的角色，例如客户机、服务器和混合节点，以及它们在网络中的行为和功能。 11. NetBIOS支持的服务器：解释了服务器如何通过NetBIOS提供共享资源和服务，如文件、打印和命名服务。 12. 网络拓扑支持：探讨了文档如何考虑不同的网络拓扑结构，确保协议在不同环境下都能有效地工作。 RFC1001文档是NetBIOS在TCP/IP网络中的基石，提供了关键的标准化指导，使得网络设备能够无缝地在TCP和UDP传输层上提供和利用NetBIOS服务。这份文档对于理解早期网络基础设施和设计现代网络架构有着重要意义。

RFC 1001 March 1987

5.3. SESSION SERVICE

A session is a reliable message exchange, conducted between a pair of

NetBIOS applications. Sessions are full-duplex, sequenced, and

reliable. Data is organized into messages. Each message may range

in size from 0 to 131,071 bytes. No expedited or urgent data

capabilities are present.

Multiple sessions may exist between any pair of calling and called

names.

The parties to a connection have access to the calling and called

names.

The NetBIOS specification does not define how a connection request to

a shared (group) name resolves into a session. The usual assumption

is that a session may be established with any one owner of the called

group name.

An important service provided to NetBIOS applications is the

detection of sessions failure. The loss of a session is reported to

an application via all of the outstanding service requests for that

session. For example, if the application has only a NetBIOS receive

primitive pending and the session terminates, the pending receive

will abort with a termination indication.

Session Service primitives are:

1) Call

Initiate a session with a process that is listening under

the specified name. The calling entity must indicate both a

calling name (properly registered to the caller) and a

called name.

2) Listen

Accept a session from a caller. The listen primitive may be

constrained to accept an incoming call from a named caller.

Alternatively, a call may be accepted from any caller.

3) Hang Up

Gracefully terminate a session. All pending data is

transferred before the session is terminated.

4) Send

Transmit one message. A time-out can occur. A time-out of

any session send forces the non-graceful termination of the

session.

NetBIOS Working Group [Page 12]

RFC 1001 March 1987

A "chain send" primitive is required by the PC NetBIOS

software interface to allow a single message to be gathered

from pieces in various buffers. Chain Send is an interface

detail and does not effect the protocol.

5) Receive

Receive data. A time-out can occur. A time-out on a

session receive only terminates the receive, not the

session, although the data is lost.

The receive primitive may be implemented with variants, such

as "Receive Any", which is required by the PC NetBIOS

software interface. Receive Any is an interface detail and

does not effect the protocol.

6) Session Status

Obtain information about all of the requestor’s sessions,

under the specified name. No network activity is involved.

5.4. DATAGRAM SERVICE

The Datagram service is an unreliable, non-sequenced, connectionless

service. Datagrams are sent under cover of a name properly

registered to the sender.

Datagrams may be sent to a specific name or may be explicitly

broadcast.

Datagrams sent to an exclusive name are received, if at all, by the

holder of that name. Datagrams sent to a group name are multicast to

all holders of that name. The sending application program cannot

distinguish between group and unique names and thus must act as if

all non-broadcast datagrams are multicast.

As with the Session Service, the receiver of the datagram is told the

sending and receiving names.

Datagram Service primitives are:

1) Send Datagram

Send an unreliable datagram to an application that is

associated with the specified name. The name may be unique

or group; the sender is not aware of the difference. If the

name belongs to a group, then each member is to receive the

datagram.

NetBIOS Working Group [Page 13]

剩余67页未读，继续阅读

imicky

粉丝: 0

RFC1001：TCP/IP环境下的NetBIOS服务协议概述

rfc1001-rfc1500

PDF版RFC：rfc1001-1500。(共12部分)

RFC系列文档大全（RFC1001-RFC2000）

SIP RFC3263英文文档

标准RFC英文参考文档

RFC英文文档下载

RFC文档 纯英文rfc文档 RFCs0501-1000

RFC959英文原版文档

RDP协议RFC英文文档

RFC英文文档word版

最新资源

RFC文档纯英文rfc文档 RFCs0501-1000