MAPOS Version 1 Assigned Numbers

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Copyright Notice

Copyright © The Internet Society (1997).

Table of Contents

1.  Abstract
2.  Introduction
3.  Protocol Field Assignments
4.  Acknowledgements
5.  References
§  Authors' Addresses
§  Intellectual Property and Copyright Statements

1.  Abstract

This document describes the protocol parameters used in the Multiple Access Over SONET/SDH (MAPOS) version 1. MAPOS is a link layer protocol and provides multiple access capability over SONET/SDH links.

2.  Introduction

Multiple Access Protocol over SONET/SDH (MAPOS) [1] (, “Murakami, K. and M. Maruyama, "MAPOS - Multiple Access Protocol over SONET/SDH, Version 1," RFC-2171,” June 1997.) is a high-speed link-layer protocol that provides multiple access capability over SONET(Synchronous Optical Network)/SDH(Synchronous Digital Hierarchy)[2] (, “CCITT Recommendation G.707: Synchronous Digital Hierarchy Bit Rates (1990,” .)[3] (, “CCITT Recommendation G.708: Network Node Interface for Synchronous Digital Hierarchy (1990,” .)[4] (, “CCITT Recommendation G.709: Synchronous Multiplexing Structure (1990,” .)[5] (, “American National Standard for Telecommunications - Digital Hierarchy - Optical Interface Rates and Formats Specification, ANSI T1.105,” 1991.). Its frame format is based on the HDLC-like framing [6] (Simpson, W., “PPP in HDLC-like Framing," RFC-1662,” July 1994.) for PPP. A component called "Frame Switch" [1] (, “Murakami, K. and M. Maruyama, "MAPOS - Multiple Access Protocol over SONET/SDH, Version 1," RFC-2171,” June 1997.) allows multiple nodes to be connected together in a star topology to form a LAN. Using long haul SONET/SDH links, the nodes on such a "SONET-LAN" can span over a wide geographical area. The Internet Protocol (IP) [7] (Postel, J., “Internet Protocol (IP," RFC-791,” September 1981.) datagrams are transmitted in MAPOS HDLC frames [8] (, “Murakami, K. and M. Maruyama, "IPv4 over MAPOS Version 1," RFC-2176,” June 1997.).

This document describes the protocol parameters used in MAPOS version 1 [1] (, “Murakami, K. and M. Maruyama, "MAPOS - Multiple Access Protocol over SONET/SDH, Version 1," RFC-2171,” June 1997.).

3.  Protocol Field Assignments

The MAPOS Version 1 Data Link Layer [1] (, “Murakami, K. and M. Maruyama, "MAPOS - Multiple Access Protocol over SONET/SDH, Version 1," RFC-2171,” June 1997.) contains a 16 bit Protocol field to identify the the encapsulated protocol. The Protocol field is consistent with the ISO 3309 (HDLC) extension mechanism for address fields. All protocol numbers MUST be assigned such that the least significant bit of the most significant octet equals "0", and the least significant bit of the least significant octet equals "1".

Assigned MAPOS Protocol Numbers

Value (in hex) Protocol Name

0001-001F Not Used - reserved

0021 MAPOS Version 1 Internet Protocol Version 4 [8] (, “Murakami, K. and M. Maruyama, "IPv4 over MAPOS Version 1," RFC-2176,” June 1997.)

0023-FCFF Not Used - reserved

FE01 MAPOS Version 1 Address Resolution Protocol (ARP[8] (, “Murakami, K. and M. Maruyama, "IPv4 over MAPOS Version 1," RFC-2176,” June 1997.))

FE03 MAPOS Version 1 Node Switch Protocol (NSP[9] (, “Murakami, K. and M. Maruyama, "A MAPOS version 1 Extension -Node Switch Protocol," RFC-2173,” June 1997.))

FE05 MAPOS Version 1 Switch Switch Protocol (SSP[10] (, “Murakami, K. and M. Maruyama, "A MAPOS version 1 Extension -Switch Switch Protocol," RFC-2174,” June 1997.))

FE07-FEFF Not Used - reserved

4.  Acknowledgements

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.

5. References

Authors' Addresses

Full Copyright Statement

Copyright © The Internet Society (1997).

This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.

This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.

Acknowledgment

Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).