DOCSLIB.ORG

Draft Stable Implementation Agreement for Open

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

NBS PUBLICATIONS U.S. DEPARTMENT OF COMMERCE National Bureau of Standards Institute for Computer Sciences and Technology A 11 IDE 7 E T M NBSIR 87-3674 Draft Stable Implementation Agreements for Open Systems Interconnection Protocols NBS Workshop for Implementors of Open Systems Interconnection Version 1 Edition 0 October 1987 DRAFT STABLE IMPLEMENTATION AGREEMENTS Based on the Proceeding of the NBS/OSI Implementor’s Workshop Plenary Assembly Held October 9, 1987 National Bureau of Standards Gaithersburg, MD 20899 U.S. DEPARTMENT OF COMMERCE NATIONAL BUREAU OF STANDARDS — QC 100 - U 5 6 87-3674 1987 C • 2 U.S. DEPARTMENT OF COMMERCE National Bureau of Standards Institute for Computer Sciences and Technology Research Information Center NBSIR 87-3674 National r>ureau of Standards Gaithersburg, Maryland 20899 A) BSc DRAFT STABLE IMPLEMENTATION QCtoo AGREEMENTS FOR OPEN SYSTEMS < USy INTERCONNECTION PROTOCOLS m., 1921 c.> NBS Workshop for Implementors of Open Systems Interconnection Version 1 Edition 0 October 1987 DRAFT STABLE IMPLEMENTATION AGREEMENTS Based on the Proceeding of the NBS/OSI Implementor’s Workshop Plenary Assembly Held October 9, 1987 National Bureau of Standards Gaithersburg, MD 20899 U.S. DEPARTMENT OF COMMERCE, C. William Verity, Acting Secretary NATIONAL BUREAU OF STANDARDS, Ernest Ambler, Director 21 Table of Contents 1. GENERAL INFORMATION 1 1.1 PURPOSE OF THIS DOCUMENT * 1 1.2 PURPOSE OF THE WORKSHOP 1 1.3 WORKSHOP ORGANIZATION 1 2. SUB NETWORKS 1 2.1 LOCAL AREA NETWORKS 1 2.1.1 IEEE 802.2 LOGICAL LINK CONTROL 1 2.1.2 IEEE 802.3 CSMA/CD ACCESS METHOD 1 2.1.3 IEEE 802.4 TOKEN BUS ACCESS METHOD 1 2.1.4 IEEE 802.5 Token Ring Access Method 3 2.2 WIDE AREA NETWORKS 4 2.2.1 CCITT RECOMMENDATION X.25 4 2.3 PRIVATE SUBNETWORKS 4 2.3.1 PRIVATE SUBNETWORKS' 4 3. NETWORK LAYER 1 3.1 INTRODUCTION 1 3.2 SCOPE AND FIELD OF APPLICATION 1 3.3 STATUS 1 3.4 ERRATA 1 3.5 CONNECTIONLESS -MODE NETWORK SERVICE (CLNS) 1 3.5.1 Provision of CLNS Using ISO 8473 1 3.5.2 Agreements on Mandatory Protocol Functions .... 2 3.5.3 Agreements on Optional Protocol Functions .... 2 3.5.4 Subnetwork Dependent Convergence Function .... 2 3.6 CONNECTION-MODE NETWORK SERVICE (CONS) 2 3.6.1 Provision of CONS Using X. 25/PLP- 1984 3 3.6.2 Subnetwork Dependent Convergence Protocol .... 3 3.7 ADDRESSING 4 3 . 8 ROUTING 4 3.8.1 Static Routing 4 3.8.2 End System to Intermediate System 4 3.9 MIGRATION CONSIDERATIONS 5 3.9.1 X. 25-1980 5 3.10 CONFORMANCE 5 3.11 TEST REQUIREMENTS ..... 5 4. TRANSPORT 1 4.1 INTRODUCTION 1 4.2 SCOPE AND FIELD OF APPLICATION 1 4.3 STATUS 1 4.4 ERRATA 1 4.5 TRANSPORT CLASS 4 1 4.5.1 Transport Class 1 4.5.2 Protocol Agreements 1 4.5.2. Rules for Negotiation 1 4. 5. 2. TRANSPORT CLASS 4 SERVICE ACCESS POINTS OR SELECTORS 3 iii 4256731 4. 5. 2. Retransmission Timer . 3 4. 5. 2. Keep-Alive Function . 4 4.6 TRANSPORT CLASS 0 ..... ........ 6 4.6.1 Transport Class 0 Overview .... 6 4.6.2 Protocol Agreements ..... 6 4.6.2. TRANSPORT CLASS 0 SERVICE ACCESS POINTS ... 7 4.6.3 Rules for Negotiation 7 3. UPPER LAYERS . 1 5.1 INTRODUCTION 1 5.1.1 References . 1 5.2 SCOPE AND FIELD OF APPLICATION 1 5.3 STATUS 2 5.4 ERRATA . 2 5.4.1 ISO Defect Reports 2 5.4. 1.1 Session Defects . 2 5.5 ASSOCIATION CONTROL SERVICE ELEMENT ............ 2 5.5.1 Introduction 2 5.5.2 Services ..... 2 5. 5. 2.1 ACSE Services 2 5. 5. 2. Use of Presentation Layer Services 3 5.5.3 Protocol agreements 3 5. 5. 3.1 Application Context 3 5.6 PRESENTATION ..... 4 5.6.1 Introduction 4 5.6.2 Services ....... 4 5.6.2. Presentation Services 4 5. 6. 2. Use of Session Layer Services 5 5.6.3 Protocol Agreements ... 5 5. 6. 3.1 Transfer Syntaxes 5 5. 6. 3. Abstract Syntaxes 5 5. 6. 3. Presentation Context Identifier 5 5. 6. 3. Mode-selector Position in SET 6 5. 6. 3. EXTERNAL Type ...... 6 5. 6. 3. Default Context ....... 6 5. 6. 3. P-Selectors 6 5.6.4 Presentation ASN.l Encoding Rules 6 5. 6. 4.1 Invalid Encoding ... 6 5. 6. 4. Protocol-version, Presentation-requirements . 6 5.7 SESSION 7 5.7.1 Introduction 7 5.7.2 Services 7 5.7.2. Session Services 7 5. 7. 2. Use of Transport Services ... 7 5.7.3 Protocol Agreements 8 5.7.3. Concatenation 8 5. 7. 3. Segmenting ............ 8 5. 7. 3. Reuse of Transport Connection ........ 8 5. 7. 3. Use of Transport Expedited Data 8 5. 7. 3. Use of Session Version Number 8 5. 7. 3. Receipt of Invalid SPDUs 9 5. 7. 3. Invalid SPM Intersections 9 iv 8 2 5. 7. 3. P-Selectors 9 5.8 Universal ASN.l Encoding Rules 9 5.8.1 Tags 9 5. 8. 1.1 Definite length 9 5.9 CONFORMANCE 10 5.9.1 Specific ASE Requirements for ACSE, Presentation, and Session 10 5. 9. 1.1 FTAM 10 5. 9. 1.1.1 Phase 2 10 5.9. 1.2 MHS 12 5.9. 1.2.1 Phase 1 12 5.9. 1.3 VT 13 5.9. 1.3.1 Phase 1 13 5. 9. 1.3. Phase 2 14 5.10 TEST REQUIREMENTS 15 5.11 APPENDIX A: RECOMMENDED PRACTICES 16 5.11.1 Reflect Parameter Values 16 5.12 APPENDIX B: OBJECT IDENTIFIER: STRUCTURE AND ALLOCATION . 20 6. ISO DIS FILE TRANSFER, ACCESS, & MANAGEMENT 1 6.1 INTRODUCTION 1 6.2 SCOPE AND FIELD OF APPLICATION 2 6.3 STATUS . 2 6.4 ERRATA 3 6.5 ASSUMPTIONS 3 6.6 PRESENTATION AGREEMENTS 3 6.7 SERVICE CLASS AGREEMENTS 4 6.8 FUNCTIONAL UNIT AGREEMENTS 4 6.9 FILE ATTRIBUTE AGREEMENTS 4 6.10 DOCUMENT TYPE AGREEMENTS 5 6.10.1 Character Sets 9 6.10.1.1 IA5 Character Set 9 6.10.1.2 8859-1 Character Set 11 6.10.2 Document Type Negotiation Rules 11 6.10.2.1 Connection Establishment 11 6.10.2.2 File Creation 11 6.10.2.3 File Opening 11 6.10.3 Relationship Between DUs DEs and Document Types . 12 , 6.11 F-CANCEL ACTION 13 6.12 IMPLEMENTATION INFORMATION AGREEMENTS . 13 6.13 DIAGNOSTIC AGREEMENTS 13 6.14 CONCURRENCY 14 6.15 REQUESTED ACCESS 15 6.16 SECURITY 15 6.16.1 Optional Password Support 15 6.16.2 Access Passwords 16 6.16.3 Implementation Responsibilities 16 6.17 REQUIREMENT FOR CONFORMANT IMPLEMENTATIONS 16 6.17.1 Interoperable Configurations 16 6.17.2 Relationship to ISO 8571--The FTAM Standard ... 17 6.17.3 Requirements for Document Type Support 18 6.17.4 Initiators 18 v 4231 6.17.5 Responders . 19 6.17.6 Senders 21 6.17.6.1 Initiator Senders 21 6.17.6.2 Responder Senders . 21 6.17.7 Receivers ...... 22 6.17.7.1 Initiator Receivers 22 6.17.7.2 Responder Receivers ..... 22 6.17.8 Minimum Ranges 23 6.18 IMPLEMENTATION PROFILES 26 6.18.1 General Requirements for the Defined Implementation Profiles 26 6.18.2 Use of Lower Layer Services 27 6.18.3 Document Type Requirements for the Defined Implementation Profiles 27 6.18.4 Parameters for the Defined Implementation Profiles 28 6.18.5 Parameter Ranges for the Defined Implementation Profiles ..... .... 29 6.18.6 File Attribute Support for Implementations .... 29 6.19 PROVISION OF SPECIFIC FUNCTION . ..... 31 6.19.1 Implementation Profile T1 : Simple File Transfer . 31 6.19.2 Implementation Profile T2: Positional File Transfer 31 6.19.3 Implementation Profile T3: Full File Transfer . 32 6.19.4 Implementation Profile A1 : Simple File Access . 32 6.19.5 Implementation Profile A2 : Full File Access ... 33 6.19.6 Implementation Profile Ml: Management 34 6.20 HARMONIZATION 34 6.21 APPENDIX A: FTAM DOCUMENT TYPES 35 6.22 APPENDIX B: KNOWN ERRORS IN ISO AND CCITT DOCUMENTS ... 60 7. CCITT 1984 X.400 BASED MESSAGE HANDLING SYSTEM 1 7.1 INTRODUCTION 1 7.2 SCOPE 2 7.3 STATUS 3 7.4 ERRATA . 3 7.5 PRMD to PRMD 3 . 7.5.1 Introduction 3 7.5.2 Service Elements and Optional User Facilities . 4 7. 5. 2.1 Classification of Support for Services ... 4 7. 5. 2. 1.1 Support (S) 5 7. 5. 2. 1.2 Non Support (N) 5 7. 5. 2. 1.3 Not Used (N/U) 6 7. 5. 2. 1.4 Not Applicable (N/A) 6 7. 5. 2. Summary of Supported Services 6 7. 5. 2. MT Service Elements and Optional User Facilities 6 7. 5. 2. IPM Service Elements and Optional User Facilities 8 7.5.3 X.400 Protocol Definitions 9 7.5.3. Protocol Classification 10 7. 5. 3. General Statements on Pragmatic Constraints . 10 7. 5. 3. MPDU Size 11 7. 5. 3. PI Protocol Elements 11 vi 462531 32 7. 5. 3.4.1 PI Envelope Protocol Elements 11 7. 5. 3. ORName Protocol Elements 16 7. 5. 3. P2 Protocol Profile (Based on [X.420]) ... 18 7. 5. 3. 6.1 P2 Protocol - Heading 19 7.5. 3.6.2 P2 Protocol - BodyParts 21 7. 5. 3. 6. P2 BodyPart Protocol Elements 23 7.5.4 Reliable Transfer Server (RTS) 25 7.
Recommended publications
  • QUESTION 20-1/2 Examination of Access Technologies for Broadband Communications

    QUESTION 20-1/2 Examination of Access Technologies for Broadband Communications

    International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies eport on broadband access technologies QUESTION 20-1/2 R International Telecommunication Union ITU-D THE STUDY GROUPS OF ITU-D The ITU-D Study Groups were set up in accordance with Resolutions 2 of the World Tele- communication Development Conference (WTDC) held in Buenos Aires, Argentina, in 1994. For the period 2002-2006, Study Group 1 is entrusted with the study of seven Questions in the field of telecommunication development strategies and policies. Study Group 2 is entrusted with the study of eleven Questions in the field of development and management of telecommunication services and networks. For this period, in order to respond as quickly as possible to the concerns of developing countries, instead of being approved during the WTDC, the output of each Question is published as and when it is ready. For further information: Please contact Ms Alessandra PILERI Telecommunication Development Bureau (BDT) ITU Place des Nations CH-1211 GENEVA 20 Switzerland Telephone: +41 22 730 6698 Fax: +41 22 730 5484 E-mail: [email protected] Free download: www.itu.int/ITU-D/study_groups/index.html Electronic Bookshop of ITU: www.itu.int/publications © ITU 2006 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. International Telecommunication Union QUESTION 20-1/2 Examination of access technologies for broadband communications ITU-D STUDY GROUP 2 3rd STUDY PERIOD (2002-2006) Report on broadband access technologies DISCLAIMER This report has been prepared by many volunteers from different Administrations and companies.
  • Medium Access Control Layer

    Medium Access Control Layer

    Telematics Chapter 5: Medium Access Control Sublayer User Server watching with video Beispielbildvideo clip clips Application Layer Application Layer Presentation Layer Presentation Layer Session Layer Session Layer Transport Layer Transport Layer Network Layer Network Layer Network Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller Data Link Layer Data Link Layer Data Link Layer Computer Systems and Telematics (CST) Physical Layer Physical Layer Physical Layer Institute of Computer Science Freie Universität Berlin http://cst.mi.fu-berlin.de Contents ● Design Issues ● Metropolitan Area Networks ● Network Topologies (MAN) ● The Channel Allocation Problem ● Wide Area Networks (WAN) ● Multiple Access Protocols ● Frame Relay (historical) ● Ethernet ● ATM ● IEEE 802.2 – Logical Link Control ● SDH ● Token Bus (historical) ● Network Infrastructure ● Token Ring (historical) ● Virtual LANs ● Fiber Distributed Data Interface ● Structured Cabling Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.2 Design Issues Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.3 Design Issues ● Two kinds of connections in networks ● Point-to-point connections OSI Reference Model ● Broadcast (Multi-access channel, Application Layer Random access channel) Presentation Layer ● In a network with broadcast Session Layer connections ● Who gets the channel? Transport Layer Network Layer ● Protocols used to determine who gets next access to the channel Data Link Layer ● Medium Access Control (MAC) sublayer Physical Layer Univ.-Prof. Dr.-Ing. Jochen H. Schiller ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.4 Network Types for the Local Range ● LLC layer: uniform interface and same frame format to upper layers ● MAC layer: defines medium access ..
  • Medium Access Control Sublayer

    Medium Access Control Sublayer

    Telematics Chapter 5: Medium Access Control Sublayer User Server watching with video Beispielbildvideo clip clips Application Layer Application Layer Presentation Layer Presentation Layer Session Layer Session Layer Transport Layer Transport Layer Network Layer Network Layer Network Layer Prof. Dr. Mesut Güneş Data Link Layer Data Link Layer Data Link Layer Computer Systems and Telematics (CST) Physical Layer Physical Layer Physical Layer Distributed, embedded Systems Institute of Computer Science Freie Universität Berlin http://cst.mi.fu-berlin.de Contents ● Design Issues ● Metropolitan Area Networks ● Network Topologies (()MAN) ● The Channel Allocation Problem ● Wide Area Networks (WAN) ● Multiple Access Protocols ● Frame Relay ● Ethernet ● ATM ● IEEE 802.2 – Logical Link Control ● SDH ● Token Bus ● Network Infrastructure ● Token Ring ● Virtual LANs ● Fiber Distributed Data Interface ● Structured Cabling Prof. Dr. Mesut Güneş ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.2 Design Issues Prof. Dr. Mesut Güneş ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.3 Design Issues ● Two kinds of connections in networks ● Point-to-point connections OSI Reference Model ● Broadcast (Multi-access channel, Application Layer Random access channel) Presentation Layer ● In a network with broadcast Session Layer connections ● Who gets the channel? Transport Layer Network Layer ● PtProtoco ls use dtdtd to determ ine w ho gets next access to the channel Data Link Layer ● Medium Access Control (()MAC) sublay er Phy sical Laye r Prof. Dr. Mesut Güneş ▪ cst.mi.fu-berlin.de ▪ Telematics ▪ Chapter 5: Medium Access Control Sublayer 5.4 Network Types for the Local Rang e ● LLC layer: uniform interface and same frame format to upper layers ● MAC layer: defines medium access - LLC IEEE 802.2 Logical Link Control ..
  • Chapter 2. Network Interfaces

    Chapter 2. Network Interfaces

    Chapter 2. Network interfaces This chapter provides an overview of the protocols and interfaces that allow TCP/IP traffic to flow over various kinds of physical networks. TCP/IP, as an internetwork protocol suite, can operate over a vast number of physical networks. The most common and widely used of these protocols is, of course, Ethernet. The number of network protocols that have provisions for natively supporting IP is clearly beyond the scope of this redbook. However, we provide a summary of some of the different networks most commonly used with TCP/IP. 2.1 Ethernet and IEEE 802.x Local Area Networks (LANs) Two frame formats can be used on the Ethernet coaxial cable: 1. The standard issued in 1978 by Xerox Corporation, Intel Corporation and Digital Equipment Corporation, usually called Ethernet (or DIX Ethernet). 2. The international IEEE 802.3 standard, a more recently defined standard. See Figure 6 for more details. The difference between the two standards is in the use of one of the header fields, which contains a protocol-type number for Ethernet and the length of the data in the frame for IEEE 802.3. Dest Source Preamble Addr Addr Type Info FCS 8bytes 6bytes 6bytes 2bytes 46<=N<=1500 bytes 4 bytes Ethernet IEEE 802.2 header Dest Source Preamble SFD Addr Addr Length DSAP SSAP Ctrl Info FCS 7 bytes1byte 6 bytes 6 bytes 2 bytes 1byte 1byte 1byte variable 4bytes IEEE 802.3 3376\3376F2AE Figure 6. ARP - Frame formats for Ethernet and IEEE 802.3 • The type field in Ethernet is used to distinguish between different protocols running on the coaxial cable, and allows their coexistence on the same physical cable.
  • Computer Networks(2015 Pattern) Unit I- Physical Layer

    Computer Networks(2015 Pattern) Unit I- Physical Layer

    Computer Networks(2015 Pattern) Unit I- Physical Layer By Prof. B.A.Khivsara Note: Material for this presentations are taken from Internet and books and only being used for student reference Outline Introduction of LAN; MAN; WAN; PAN, Ad-hoc Network Topologies Network Architectures OSI Model TCP/IP Model Design issues for Layers Transmission Mediums Network Devices Manchester and Differential Manchester Encodings; IEEE802.11: Frequency Hopping (FHSS) and Direct Sequence (DSSS) Introduction of Network Network: A network is defined as a group of two or more computer systems linked together. Types of Networks: LAN MAN WAN PAN Ad-hoc Network Local Area Networks (LAN) floor/building-wide single communication medium no routing, broadcast segments connected by switches or hubs high bandwidth, low latency Ethernet - 10Mbps, 100Mbps, 1Gbps no latency guarantees LAN- Local Area Network It is designed for small physical areas such as an office, group of buildings or a factory. LANs are used widely as it is easy to design and to troubleshoot. Personal computers and workstations are connected to each other through LANs. We can use different types of topologies through LAN, these are Star, Ring, Bus, Tree etc. LAN can be a simple network like connecting two computers, to share files and network among each other while it can also be as complex as interconnecting an entire building. LAN networks are also widely used to share resources like printers, shared hard-drive etc. LAN Diagram LAN Advantages • Cost reductions through sharing of information and databases, resources and network services. • Increased information exchange between different departments in an organization, or between individuals.
  • MAC Layer Protocols for Internet of Things: a Survey

    MAC Layer Protocols for Internet of Things: a Survey

    future internet Review MAC Layer Protocols for Internet of Things: A Survey Luiz Oliveira 1, Joel J. P. C. Rodrigues 1,2,3,* , Sergei A. Kozlov 3 , Ricardo A. L. Rabêlo 4 and Victor Hugo C. de Albuquerque 5 1 National Institute of Telecommunications (Inatel), Santa Rita do Sapucaí MG 37540-000, Brazil; [email protected] 2 Instituto de Telecomunicações, 1049-001 Lisboa, Portugal 3 International Institute of Photonics and Optoinformatics, ITMO University, 197101 Saint Petersburg, Russia; [email protected] 4 Department of Computing (DC), Graduate Program in Computer Science (PPGCC), Federal University of Piaui (UFPI), Ministro Petronio Portela Campus, Teresina 64049-550, Piaui, Brazil; [email protected] 5 Graduate Program in Applied Informatics, University of Fortaleza (UNIFOR), Fortaleza CE 60811-905, Brazil; [email protected] * Correspondence: [email protected]; Tel.: +55-35-3471-9200 Received: 27 November 2018; Accepted: 18 December 2018; Published: 14 January 2019 Abstract: Due to the wide variety of uses and the diversity of features required to meet an application, Internet of Things (IoT) technologies are moving forward at a strong pace to meet this demand while at the same time trying to meet the time-to-market of these applications. The characteristics required by applications, such as coverage area, scalability, transmission data rate, and applicability, refer to the Physical and Medium Access Control (MAC) layer designs of protocols. This paper presents a deep study of medium access control (MAC) layer protocols that are used in IoT with a detailed description of such protocols grouped (by short and long distance coverage).
  • UNIT II DATA-LINK LAYER & MEDIA ACCESS Introduction – Link-Layer

    UNIT II DATA-LINK LAYER & MEDIA ACCESS Introduction – Link-Layer

    UNIT II DATA-LINK LAYER & MEDIA ACCESS Introduction – Link-Layer Addressing – DLC Services – Data-Link Layer Protocols – HDLC – PPP - Media Access Control - Wired LANs: Ethernet - Wireless LANs – Introduction – IEEE 802.11, Bluetooth – Connecting Devices. 2.1 Introduction What is DLL (Data Link Layer)? The Data Link Layer is the second layer in the OSI model, above the Physical Layer, which ensures that the error free data is transferred between the adjacent nodes in the network. It breaks the datagram passed down by above layers and converts them into frames ready for transfer. This is called Framing. It provides two main functionalities Reliable data transfer service between two peer network layers Flow Control mechanism which regulates the flow of frames such that data congestion is not there at slow receivers due to fast senders. 2.2 LINK-LAYER ADDRESSING In a connectionless internetwork such as the Internet we cannot make a datagram reach its destination using only IP addresses. The reason is that each datagram in the Internet, from the same source host to the same destination host, may take a different path. The source and destination IP addresses define the two ends but cannot define which links the datagram should pass through. Three Types of addresses Some link-layer protocols define three types of addresses: unicast, multicast, and broadcast. Unicast Address Each host or each interface of a router is assigned a unicast address. Unicasting means one-to-one communication. A frame with a unicast address destination is destined only for one entity in the link. A3:34:45:11:92:F1 Multicast Address Some link-layer protocols define multicast addresses.
  • Atn) Ground-Ground Router Description

    Atn) Ground-Ground Router Description

    INTERNATIONAL CIVIL AVIATION ORGANIZATION ASIA AND PACIFIC OFFICE ASIA/PACIFIC REGIONAL AERONAUTICAL TELECOMMUNICATION NETWORK (ATN) GROUND-GROUND ROUTER DESCRIPTION Edition 1.2 – May 2004 Reference Document for the ATN Router Description ISSUE 1.2- MAY 2004 Table of Contents 1.0 INTRODUCTION............................................................................................................................3 1.1 SCOPE .............................................................................................................................................3 1.2 SARPS COMPLIANCE......................................................................................................................4 2.0 DOCUMENTS..................................................................................................................................5 2.1 APPLICABLE DOCUMENTS ..............................................................................................................5 2.2 REFERENCE DOCUMENTS ...............................................................................................................6 3.0 ATN GROUND-GROUND ROUTER REQUIREMENTS..........................................................7 3.1 OVERVIEW ......................................................................................................................................7 3.1.1 ATN G/G Router Protocol Characteristics .............................................................................8 3.1.1.1 Application Layer................................................................................................................8
  • Internetworking: an Analysis and Proposal

    Internetworking: an Analysis and Proposal

    Rochester Institute of Technology RIT Scholar Works Theses 1990 Internetworking: an analysis and proposal Gary M. Diana Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Diana, Gary M., "Internetworking: an analysis and proposal" (1990). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Internetworking: An Analysis and Proposal Internetworking: An Analysis and Proposal Gary M. Diana April 26, 1990 Rochester Institute ofTechnology Department of Computer Science A Thesis, submitted to the Faculty of the School of Computer Science and Information Technology, in partial fulfillment for the Degree of Master of Science in Computer Science Approved by: ~/( Ie () i Associate Professor Dr. Andrew T. Kitchen Chairman, Thesis Committee Associate Professor Dr. James E. Heliotis Reading Member, Thesis Committee Associate Professor Henry A. Etlinger Reading Member, Thesis Committee Title of Thesis: Internetworking: An Analysis and Proposal I Gary M. Diana hereby grant permission to the Wallace Memorial Library, of RIT, to reproduce my thesis in whole or in part. Any reproduction will not be used for commercial use or profit. Date: May 22, 1990 Acknowledgements This thesis represents the final efforts on my way to obtaining the degree of Master of in Science Computer Science. There are many people who supported me over the six years it has taken, and I would like to take this opportunity to recognize them.
  • IEEE 802.11 Wireless LAN Standard

    IEEE 802.11 Wireless LAN Standard

    IEEE 802.11 Wireless LAN Standard Updated: 5/10/2011 IEEE 802.11 History and Enhancements o 802.11 is dedicated to WLAN o The group started in 1990 o First standard that received industry support was 802.11b n Accepted in 1999 n Focusing on 2.4 GHz unlicensed band n Initially 2 Mbit BW – relatively slow (802.11) 802.11 Standards WiFi Alliance http://www.wi-fi.org/ Read the handout! 802.11 Standards 802.11ac @5GHz with 1.3Gbps Max. Data Rate! http://en.wikipedia.org/wiki/IEEE_802.11 http://www.wi-fi.org/discover-and-learn OSI Model IEEE 802 Protocol Layers Provide an interface to higher layers and perform flow and error control • Encoding/decoding of signals transmission medium IEEE• Preamble 802 generation/removal Protocol Layers (for synchronization) • Bit transmission/reception • Includes specification of the transmission medium • On transmission, assemble data into a frame with address and error detection fields • On reception, disassemble frame and perform address recognition and error detection • Govern access to the LAN transmission medium LLC and MAC are separated: - The logic required to manage access to a shared- access medium not found in traditional layer 2 data link control - For the same LLC, several MAC options may be provided Protocol Architecture o Functions of physical layer: n Encoding/decoding of signals n Preamble generation/removal (for synchronization) n Bit transmission/reception n Includes specification of the transmission medium Protocol Architecture o Functions of medium access control (MAC) layer: n On transmission,
  • The OSI Model and Switching 1

    The OSI Model and Switching 1

    The OSI Model and Switching 1 Chapter I The OSI Model and Switching Vasilios A. Siris Institute of Computer Science–FORTH, Greece In this chapter we give the motivation and basic concepts of the OSI reference model, discuss its seven-layer architecture, the communication between systems using the OSI model, and finally the relationship between the OSI model and multilayer switching. MOTIVATION AND BASIC CONCEPTS The Open System Interconnection (OSI) reference model is a framework for defining the conventions and tasks required for network systems to communicate with one another. The work on the OSI model began in the late 1970s, mostly independently, by the International Organization for Standardization (ISO) and the International Telegraph and Telephone Consultative Committee or CCITT (which comes from the translation of the title in French). CCITT has been succeeded by the Telecommunications Standardization Sector of the International Telecommunica- tions Union (ITU-TS). In 1983 the work of the two organizations was combined, and a single document describing the reference model for Open Systems Interconnec- tion was produced. The term “open systems” refers to the fact that the specifications are publicly available to everyone. The purpose of the OSI model was to assist vendors and communications software developers to produce interoperable network systems. Although the OSI model was designed to replace all previous computer communications standards, it is no longer viewed as such a replacement. Rather, the OSI model has succeeded as a tool for describing and defining how heterogeneous network systems communicate. Copyright © 2002, Idea Group Publishing. 2 Siris The OSI model is based on a widely accepted structuring technique called layering.

  • Software Defined Protocols Based on Generic Protocol Functions for Wired and Wireless Networks

    SOFTWARE DEFINED PROTOCOLS BASED ON GENERIC PROTOCOL FUNCTIONS FOR WIRED AND WIRELESS NETWORKS Lars Berlemann, Matthias Siebert, Bernhard Walke (Communication Networks, Aachen University, Germany) {ber|mst|walke}@comnets.rwth-aachen.de ABSTRACT wireless networks. Due to the dedicated constraints of the air-interface wireless communication protocols are much This paper introduces an efficient and flexible approach for more sophisticated than protocols for wired technologies. the design and implementation of communication protocols Thus, the main challenges of protocol design are introduced for wired and wireless networks, enabling an adaptive and under consideration of the distinctive characteristics of reusable protocol stack realization. For the design and wired and wireless networks. Section 3 shows the evolution specification of new communication protocols suitability from wired to wireless networks at the example of the Link proven components are often reused and extended to meet Access Procedure on the D-channel (LAPD) of the ISDN system specific demands. So, wireless protocols share a standard. This data link control protocol is used in wired common origin with wired protocols as exemplarily shown ISDN, also referred to as N-ISDN, and B-ISDN as well as for the LAPD, LAPDm and LAPC data link control lightly modified in the wireless standards GSM/GPRS, there protocols. To enable the vision of a smooth integration of referred to as LAPDm, and DECT, there named LAPC. the fixed and the mobile world a protocol design based on a Section 4 proposes a generic protocol stack as a common generic protocol stack is proposed. The considered protocols basis of these in the past departing wired and wireless are grouped into a system specific and a common part.