Skip to main content

A MAPOS version 1 Extension - Node Switch Protocol

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 2173.
Authors Mitsuru Maruyama , Ken-ichiro Murakami
Last updated 2013-03-02 (Latest revision 1997-05-01)
RFC stream Legacy stream
Intended RFC status (None)
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Became RFC 2173 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)

Network Working Group                                   K. Murakami
INTERNET-DRAFT                                          M. Maruyama
Category: Informational                                 NTT Laboratories
                                                        May 1997

           A MAPOS version 1 Extension - Node Switch Protocol

Status of this Memo

   This document is an Internet-Draft.  Internet-Drafts are working
   documents of the Internet Engineering task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other
   documents at any time.  It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in

   To learn the current status of any Internet-Draft, please check the
   "1id-abstract.txt" listing contained in the Internet-Drafts Shadow
   Directories on (Africa), (Europe), (Pacific Rim), (US East Coast), or (US West Coast).

Authors' Note 

   This memo documents a MAPOS (Multiple Access Protocol over SONET/SDH)
   extension, Node Switch Protocol for automatic node address
   assignment. This document is NOT the product of an IETF working group
   nor is it a standards track document.  It has not necessarily
   benefited from the widespread and in depth community review that
   standards track documents receive.


   This document describes a MAPOS extension, Node Switch Protocol, for
   automatic node address assignment. MAPOS is a multiple access
   protocol for transmission of network-protocol datagrams, encapsulated
   in High-Level Data Link Control (HDLC) frames, over SONET/SDH. NSP
   automates the HDLC address configuration of each node. Using NSP, a
   node retrieves its its HDLC address from the switch to which it is

1. Introduction

   MAPOS[1], Multiple Access Protocol over SONET(Synchronous Optical
   Network)/SDH(Synchronous Digital Hierarchy)[2][3][4][5], is a
   protocol for transmission of HDLC frames over SONET/SDH. A SONET
   switch provides multiple access capability to each node. In MAPOS,
   each node has a unique HDLC address within a switch. The address is
   equivalent to the port number of the switch to which the node is
   connected.  This document describes an extension to MAPOS, Node
   Switch Protocol, which enable automatic HDLC address assignment.
   First, it explains the addressing of MAPOS. Then, it describes the
   NSP protocol for automatic HDLC node address assignment.

2. Node Address Format

   This section describes MAPOS Version 1 address format in single and
   multiple switch environment.

2.1 Address Format

Murakami, Maruyama                                              [Page 1]
I/D               MAPOS Version 1 Node Switch Protocol          May 1997

   In MAPOS network, each end node has a unique HDLC address. As shown
   in Figure 1, the address length is 8 bits. The LSB is always 1 which
   indicates the end of the field.  When a SONET switch receives an HDLC
   frame, it forwards the frame based on the address in the frame

   In unicast, MSB is 0 and the rest of the bits are the port number to
   which a node is connected. Since the LSB is always 1, the minimum and
   maximum addresses are 0x01 and 0x7F, respectively.  Address 0x01 is
   reserved and is assigned to the control processor in a SONET switch.

   In broadcast, MSB is 1 and the rest of the bits are all 1s. In
   multicast, MSB is 1 and the rest of the bits, except for the LSB,
   indicate the group address.

           | | | | | | | | |
           | |port number|1|
            ^             ^
            |             |
            |             +------- EA bit (always 1)
            1 : broadcast, multicast
            0 : unicast

                              Figure 1 Address format

2.2 Address in multi-switch environment

   In a multi-switch environment, variable-length subnet addressing is
   used. Each switch has a switch number that is unique within the
   system. Subnetted node addresses consists of the switch number and
   the port number to which a node is connected. The address format is
   "0 <switch number> <node number> 1" for a unicast address, "all 1"
   for the broadcast address, and "1 <group address> 1" for a multicast

   The address 0x01 is reserved and is assigned to the control processor
   in the "local" switch. That is, it indicates the switch itself to
   which the node is connected. The addresses of the form "0 <switch
   number> <all 0> 1" are reserved, and indicates the control processor
   of the switch designated by the switch number.

   In Figure 2, the switch numbers are two bits long. Node N1 is
   connected to port 0x3 of switch S1 numbered 0x1 (01 in binary). Thus,
   the node address is 0 + 01 + 00011, that is, 00100011(0x23). Node N3
   has an address 01001001(0x49), since the switch number of S2 is 0x2
   (10 in binary) and the port number is 0x09. Note that all the port

Murakami, Maruyama                                              [Page 2]
I/D             MAPOS Version 1 Node Switch Protocol          May 1997

   numbers are odd because the LSBs are always 1.

                           | node |
                           |  N1  |
                               | 00100011(0x23)
                               |0x3             |0x3
               +------+    +---+----+       +---+----+     +------+
               | node +----+ SONET  +-------+ SONET  +-----+ node |
               |  N2  | 0x5| Switch |0x9 0x5| Switch |0x9  |  N3  |
               +------+    |   S1   |       |   S2   |     +------+
           00100101(0x25)  |  0x1   |       |  0x2   |   01001001(0x49)
                           +---+----+       +---+----+
                               |0x7             |0x7

                Figure 2  Addressing in Multiple Switch Environment

4 NSP(Node-Switch Protocol)

   This section describes the NSP protocol used for automatic node
   address assignment.

4.1 NSP protocol

   NSP is introduced to provide automatic node address assignment
   function in MAPOS version 1. It reduces the administrative overhead
   of node address configuration for each node and prevents troubles
   such as address inconsistency and collision. When a node is connected
   to a switch and receives SONET signal correctly, the node sends an
   address request packet to the control processor in the local switch.
   The destination address of this packet is 00000001(0x01). When the
   control processor receives the packet, it replies with an address
   assignment packet. The destination is the assigned node address. If
   the node does not receive the address assignment packet within 5
   seconds, it retransmits the address request packet. The
   retransmission continues until the node successfully receives the
   address assignment packet.

   Whenever a node detects a transmission error such as carrier loss or
   out-of-synchronization, it SHOULD send an address request packet to
   the control processor and verify its current address. In addition, a
   node MUST verify its address by sending address request packets every
   30 seconds. The switch regards them as keep-alive packets and
   utilizes them to detect the node's status. If it has not received a
   request packet for more than 90 seconds, it assumes that the node
   went down.  In addition, it also assumes the node went down when a

Murakami, Maruyama                                              [Page 3]
I/D             MAPOS Version 1 Node Switch Protocol          May 1997

   switch detects a SONET signal failure.

4.2 Packet Format

   The HDLC protocol field of a NSP frame contains 0xFE03 (hexadecimal)
   as defined by the ``MAPOS Version 1 Assigned Numbers'' [6]. The
   information field contains the NSP packet as shown in Figure 3.

           I  command  I  address   I
           I<- 32bit ->I<- 32 bit ->I

                            Figure 3  NSP packet format

   The command field is 32 bits long and has the following values (in

           1       address request
           2       address assignment
           3       reject(error)

   The length of the address field is 32bits. In address request
   packets, the NSP address field SHOULD be filled with zeroes, although
   the switch ignores it. In address assignment packets, the assigned
   address is placed in the least significant byte of the field. The
   rest of the field is padded with zeroes. When the switch can not
   assign the address for some reason, the switch replies with a reject
   command (the values is 3). The value of the address field is

4.3 Consideration for special cases

   There are two special cases to consider. One is a point-to-point
   connection without a switch. The other is loop-back, that is, direct
   connection between the input and the output of the same port.

4.3.1 point-to-point

   In the case of a point-to-point connection shown in Figure 4, a node
   sends an address request packet to the other node. The destination
   address is 00000001(0x01), that is usually a control processor in a
   switch. When a node receives the address request, it detects the
   point-to-point connection by examining both the destination address
   and the command contained.  Then, it MUST reply with an address
   assignment packet. The assigned address MUST be 00000011(0x03). Since
   both nodes send an address request to each other, both of them get

Murakami, Maruyama                                              [Page 4]
I/D            MAPOS Version 1 Node Switch Protocol          May 1997

   address 00000011(0x03). Since any address can be used in point-to-
   point environment, there is no problem even if both of the nodes have
   the same address.

                   ---- address request ----> 0x01
                      0x03 <---- address assignment ----
           +------+                                +------+
           | node +--------------------------------+ node |
           +------+                                +------+
                      0x01 <---- address request ----
                   ---- address assignment ----> 0x03

                        Figure 4 Point-to-point connection

4.3.2 loop-back

   Another special case is loop-back where the output port of a node is
   simply connected to its input port as shown in Figure 5. In this
   case, the same mechanism as that for point-to-point can be applied
   without modification.  A node sends an address request packet
   destined to 00000001(0x01). The node then receives the same packet.
   Since the destination is 00000001(0x01), it replies with an address
   assignment packet, containing the assigned address 00000011(0x03), to
   the address 0000 0011(0x03).  Thus, the node obtains the address

                     ---- address request ----> 0x01
           +------+  --- address assignment --> 0x03
           |      +-------------->-----------------+
           | node +                                |
           |      +--------------<-----------------+

                         Figure 5 Loop-back Configuration

5. Security Considerations

   Security issues are not discussed in this memo.


   [1]   K. Murakami and M. Maruyama, "MAPOS - Multiple Access Protocol
         over SONET/SDH, Version 1," May 1997.

   [2]   CCITT Recommendation G.707: Synchronous Digital Hierarchy Bit
         Rates (1990).

Murakami, Maruyama                                              [Page 5]
I/D             MAPOS Version 1 Node Switch Protocol          May 1997

   [3]   CCITT Recommendation G.708: Network Node Interface for Synchronous
         Digital Hierarchy (1990).

   [4]   CCITT Recommendation G.709: Synchronous Multiplexing Structure

   [5]   American National Standard for Telecommunications - Digital
         Hierarchy - Optical Interface Rates and Formats Specification,
         ANSI T1.105-1991.

   [6]   M. Maruyama and K. Murakami, "MAPOS Version 1 Assigned Numbers,"
         May, 1997.


   The authors would like to acknowledge the contributions and
   thoughtful suggestions of John P. Mullaney, Clark Bremer, Masayuki
   Kobayashi, Paul Francis, Toshiaki Yoshida, and Takahiro Sajima.

Authors' Address

     Ken Murakami
     NTT Software Laboratories
     3-9-11, Midori-cho
     Tokyo 180, Japan

     Mitsuru Maruyama
     NTT Software Laboratories
     3-9-11, Midori-cho
     Tokyo 180, Japan

Murakami, Maruyama                                              [Page 6]