MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing

Abstract

MAPOS 16 -Multiple Access Protocol over SONET/SDH with 16 Bit Addressing Status of this MemoThis memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Authors' noteThis memo documents MAPOS 16, a multiple access protocol for transmission of network-protocol datagrams, encapsulated in HDLC frames with 16 bit addressing, over SONET/SDH. The primary difference with MAPOS version 1 is that it has 16 bit address field that offers significant wide address space. 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. AbstractThis document describes the protocol MAPOS 16, Multiple Access Protocol over SONET/SDH with 16 Bit Addressing, for transmitting network-protocol datagrams over SONET/SDH. The primary difference with MAPOS version 1 is that it has 16 bit address field that offers significant wide address space. It first describes the major differences between MAPOS and MAPOS 16 briefly. Then, it explains the header format and its 16 bit address format.

Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over SONET/SDH)

“…The length of the information field of the MAPOS frame may vary, but shall not exceed 65,280 (64K -256) octets [1] [2]. The default maximum transmission unit (MTU) is 65,280 octets.…”

“…The address field of the MAPOS 16 frame header contains the 16-bitwide destination HDLC address [2]. The LSB of the first octet must always be 0 to indicate the continuation of this field, and the LSB of the second octet must always be 1 to indicate the end of this field.…”

“…In the case of a point-to-point connection between two nodes, the same MAPOS address is assigned to each interface. Specifically, in the case of MAPOS version 1, the assigned address is 0x03 [6], and in the case of MAPOS 16, the assigned address is 0x0003 [2]. It is not easy to achieve link-locality of the interface identifier in a strict manner using the same Link-layer address.…”

“…In [5], the length of the Source/Target Link-layer Address option field is specified in units of 8 octets. However, in the case of MAPOS, the length of the address field is 2 octets (MAPOS 16) or 1 octet (MAPOS version 1)[1] [2]. Thus, if the exact form of the address field is embedded in the Link-layer Address field of the Source/Target Linklayer Address option field, the total length of the option field is 4 octets (MAPOS 16) or 3 octets (MAPOS version 1), both of which are shorter than 8 octets.…”

MAPOS/PPP Tunneling mode

“…Security considerations are noted in Chapter 4. shows an example of MAPOS/PPP tunneling mode. The MAPOS network uses MAPOS 16 [2] in this example. Consider a tunneling path between customer premise equipment (CPE) A and CPE B which are industry standard POS equipment.…”