rfc2097.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   |   1st NetBIOS-Name (cont.)    |    Added      |2nd NetBIOS Name...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Type

      1

   Length

      2 + (Number of NetBIOS names * 17)

   NetBIOS-Names

      This group of zero or more sixteen octet NetBIOS-Name fields
      contains a list of all the NetBIOS names the peer wishes to add to
      the remote network if the packet is Configure-Request.  If the
      packet is Configure-Reject, the peer does not support this
      configuration option and it can be assumed that no NetBIOS names
      were added.

      Because the length field is only one octet, only 14 NetBIOS names
      can be added per Name-Projection option.  If more than 14 NetBIOS
      names should be added, then more than one Name-Projection option
      packet will have to be sent in the Configure-Request packet.



Pall                        Standards Track                     [Page 7]

RFC 2097                         NBFCP                      January 1997


   Added

      This is a one octet field which plays a dual role.  The Added
      field in the Name-Projection Request packet contains the type of
      NetBIOS name added.  A summary of name types is listed below.

         01   Unique Name.
         02   Group Name.

      If the packet is a Configure-Reject the Added field should contain
      the NetBIOS return code for the NetBIOS Add Name or NetBIOS Add
      Group Name command as defined in the NetBIOS 3.0 specification =
      [3].

   A summary of common result codes is listed below in type hex.

         00   Name successfully added.
         0D   Duplicate name in local name table.
         0E   Name table full.
         15   Name not found or cannot specify "*" or null.
         16   Name in use on remote NetBIOS.
         19   Name conflict detected.
         30   Name defined by another environment.
         35   Required system resources exhausted.

3.2.  Peer-Information

   Description

      This Configuration Option provides a way for the peer to
      communicate NetBIOS pertinent configuration information. Although
      negotiation of this option is not mandatory, it is suggested.

   A summary of the Peer-Information Option format is shown below.  The
   fields are transmitted from left to right.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |         Peer-class            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Peer-version (major)   |       Peer-version(minor)    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Peer-name ....
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+






Pall                        Standards Track                     [Page 8]

RFC 2097                         NBFCP                      January 1997


   Type

      2

   Length

      >=3D8

      If the length is 8, there is no Peer-name.  If the length is
      greater than 8, the Peer-name's length is Length - 8.

   Peer-class

      The Peer-class field is one octet. It identifies the sender's
      implementation type.

      Initial values are assigned as follows:

      Value           Class

        1             Reserved for legacy implementations.
        2             PPP NetBIOS Gateway Server.
        3             Reserved for legacy implementations.
        4             PPP Local Access Only Server.
        5             Reserved for legacy implementations.
        6             PPP NBF Bridge.
        7             Reserved for legacy implementations.
        8             PPP End-System.

   Peer-version

      The Peer-version field is four octets and indicates the version of
      the communication peer providing one side of the PPP connection.
      The first two octets are the major version number and the last two
      octets are the minor version number.  The major and minor version
      represent a 16 bit unsigned number sent with the most significant
      octet first.

   Peer-name

      The name of the peer.  A suggested name is the NetBIOS workstation
      name of the peer.  If the length field is 8, no peer name is
      provided.  The peer-name may not be greater than 32 octets in
      length.







Pall                        Standards Track                     [Page 9]

RFC 2097                         NBFCP                      January 1997


3.3.  Multicast-Filtering

   Description

      This Configuration Option provides a way to negotiate the use of
      the Multicast-Forward-Period and the Multicast-Priority.  This
      Configuration Option provides a way to negotiate how to handle
      mulicast packets.  It allows the sender of the Configure-Request
      to state the current handling of multicast packets.  The peer can
      request parameters by NAKing the option, and returning valid
      Multicast-Filtering parameters.

      If negotiation about the remote Multicast-Filtering is required,
      and the peer did not provide the option in its Configure-Request,
      the option SHOULD be appended to a Configure-Nak.

      Controlling the multicast rate is important because some NetBIOS
      applications use multicasts to communicate and withholding
      multicasts may prevent these applications from working.  It is
      also true that other NetBIOS applications do not need to receive
      any multicast packets and therefore it is best to quench the rate
      at which the peer will send multicast packets.

      By default, the peer is pre-configured to an administrator
      assigned Multicast-Forward-Period and Priority.  A Multicast-
      Forward-Period specified as hex type FFFF in a Configure-Request
      is interpreted as requesting the receiving peer to specify a value
      in its Configure-Nak.  A Multicast-Forward-Period value specified
      as hex type FFFF in a Configure-Nak is interpreted as agreement
      that no value exists. A Multicast-Forward-Period of zero indicates
      that all multicast packets SHOULD be forwarded.

      Peers that rely on all multicast packets being forwarded SHOULD
      request a Multicast-Forward-Period of zero and a Multicast-
      Priority of one by NAKing the Configure-Request option and
      appending the proper parameters to a Configure-Nak.

   A summary of the Multicast-Filtering Configuration Option format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |    Multicast-Forward-Period   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |   Priority    |
   +-+-+-+-+-+-+-+-+




Pall                        Standards Track                    [Page 10]

RFC 2097                         NBFCP                      January 1997


   Type

      3

   Length

      5

   Multicast-Forward-Period

      The Multicast-Forward-Period field is two octets and indicates
      the maximum period in seconds at which multicast packets can
      be sent.  The maximum value for this field is 60 (one minute).
      A value of zero indicates that there is no maximum period at
      which multicast packets can be sent.  A value of hex type FFFF
      indicates that the Multicast-Forward-Period is unknown.  A value
      of five indicates that multicast packets will not be sent at a
      rate more frequent than once every five seconds.  This two
      octet value represents a 16 bit unsigned number sent with
      the most significant octet first.

   Priority

      The Priority field is one octet long and indicates if multicast
      packets have priority over other packets when being sent.  A value
      of 0 indicates that directed packets have priority.  A value of 1
      indicates that multicast packets have priority.

3.4.  IEEE-MAC-Address-Required

   Description

      This boolean Configuration Option provides a method for the peer
      to require that all NBF datagrams be sent with a 12 octet IEEE MAC
      Address header.  By default, it is assumed that no MAC header is
      required.

   A summary of the IEEE-MAC-Address-Required Boolean Configuration
   Option format is shown below.  The fields are transmitted from left
   to right.

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |    Length     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+





Pall                        Standards Track                    [Page 11]

RFC 2097                         NBFCP                      January 1997


   Type

      4

   Length

      2

   Requirements

      By default the NBF datagram is sent without any MAC header
      information.  The NBF datagram information field is equivalent to
      the data field in 802.3, 802.5, and FDDI frames.

      If this option is negotiated successfully, each NBF datagram is
      sent with a 12 octet IEEE MAC Address header prepended to the
      information field.  A summary of the information field when using
      12 octet IEEE MAC Headers is shown below. The fields are
      transmitted from left to right.  The MAC Address is in non-
      canonical form. This means that the first bit to be transmitted in
      every byte is the most significant bit.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Destination MAC Address                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Destination MAC Address   |  Source MAC Address           |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Source MAC Address                      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               802.3/802.5/FDDI data field...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Security Considerations

   Security issues are not discussed in this memo.

References

   [1]   Simpson, W., Editor, "The Point-to-Point Protocol (PPP)",
         STD 51, RFC 1661, July 1994.

   [2]   Reynolds, J., and J. Postel, "Assigned Numbers", STD 2,
         RFC 1700, October 1994.

   [3]   IBM Corp., "IBM Local Area Network Technical Reference",
         Third Edition, Document Number SC30-3383-2, November 4, 1988.



Pall                        Standards Track                    [Page 12]

RFC 2097                         NBFCP                      January 1997


   [4]   Baker, F., and R. Bowen "PPP Bridging Control Protocol (BCP)",
         Work in Progress.

Acknowledgments

   Some of the text in this document is taken from previous documents
   produced by the Point-to-Point Protocol Working Group of the Internet
   Engineering Task Force (IETF).

   Thomas J. Dimitri (previously at Microsoft Corporation) authored the
   original draft.

   Special thanks go to coworkers at Microsoft, Bill Simpson
   (Daydreamer), Tom Coradetti (DigiBoard), Marty Del Vecchio (Shiva),
   Russ Gocht (Shiva) and several members of the IETF PPP Working Group.

Chair's Address

   The working group can be contacted via the current chair:

      Karl Fox
      Ascend Communications
      3518 Riverside Drive, Suite 101
      Columbus, Ohio 43221

      [e-mail]
      [e-mail]

Author's Address

   Questions about this memo can also be directed to:

      Gurdeep Singh Pall
      Microsoft Corporation
      1 Microsoft Way
      Redmond, WA 98052-6399

      EMail: [e-mail]













Pall                        Standards Track                    [Page 13]