About: Local Management Interface is a research topic. Over the lifetime, 417 publications have been published within this topic receiving 7925 citations.
TL;DR: Narada as discussed by the authors is an alternative architecture for end-to-end multicast, where end systems implement all multicast related functionality including membership management and packet replication, and self-organize into an overlay structure using a fully distributed protocol.
Abstract: The conventional wisdom has been that Internet protocol (IP) is the natural protocol layer for implementing multicast related functionality. However, more than a decade after its initial proposal, IP multicast is still plagued with concerns pertaining to scalability, network management, deployment, and support for higher layer functionality such as error, flow, and congestion control. We explore an alternative architecture that we term end system multicast, where end systems implement all multicast related functionality including membership management and packet replication. This shifting of multicast support from routers to end systems has the potential to address most problems associated with IP multicast. However, the key concern is the performance penalty associated with such a model. In particular, end system multicast introduces duplicate packets on physical links and incurs larger end-to-end delays than IP multicast. We study these performance concerns in the context of the Narada protocol. In Narada, end systems self-organize into an overlay structure using a fully distributed protocol. Further, end systems attempt to optimize the efficiency of the overlay by adapting to network dynamics and by considering application level performance. We present details of Narada and evaluate it using both simulation and Internet experiments. Our results indicate that the performance penalties are low both from the application and the network perspectives. We believe the potential benefits of transferring multicast functionality from end systems to routers significantly outweigh the performance penalty incurred.
TL;DR: This document discusses ATM adaptation layer parameter indication in the SETUP message, use of Forward and Backward Maximum CPCS-SDU Size by the AAL entity in the user plane, and guidelines on the use of Bearer Class, Traffic Parameters and QoS.
Abstract: 1. Introduction. Purpose of Document. Scope of Document. Structure of Document. Terminology. ATM Bearer Service Overview. User-Network Interface Configuration. User-Network Interface Protocol Architecture. 2. Physical Layer Interfaces Specification. SONET STS-3c Physical Layer Interface. DS3 Physical Layer Interface. Physical Layer for 100 Mbps Multimode Fiber Interface. Physical Layer for 155 Mbps Interface. E3 Physical Layer Services. E4 Physical Layer Interface. 3. ATM Layer Specification. ATM Layer Services. Service Expected from the Physical Layer. ATM Cell Structure and Encoding at the UNI. ATM Layer Functions Involved at the UNI (U-plane). ATM Layer Management Specification (M-plane). Traffic Control and Congestion Control. 4. Interim Local Management Interface Specification. Interim Local Management Interface (ILMI) Functions. ILMI Service Interface. Simple Network Management Protocol (SNMP). Management Information Base (MIB) Model for ILMI Managed Objects. Relationship to Other MIBs. Actual MIB. ILMI Protocol. 5. UNI Signalling. General. Overview of Call Control. Message Functional Definitions and Contents. General Message Format and Information Element Coding. Call/Connection Control Procedures For ATM Point-to-Point Calls. Call/Connection Control Procedures for Point-to-Multipoint Calls. List of Timers. Address Registration. Signalling ATM Adaptation Layer (SAAL). References. Annex A: Guidelines for Use of ATM Address Formats. Annex B: Compatibility Checking. Annex C: B-LLI Negotiation. General. B-LLI notification to the called user. B-LLI negotiation between users. Alternate requested values. Annex D: Transit Network Selection. Selection not supported. Selection supported. Annex E: Cause Definitions. Annex F: ATM Adaptation Layer Parameters Negotiation. General. ATM adaptation layer parameter indication in the SETUP message. Maximum CPCS-SDU Size negotiation. MID range negotiation. Use of Forward and Backward Maximum CPCS-SDU Size by the AAL entity in the user plane. Appendix A: A Quality of Service Guidelines. Introduction. QoS Reference Configuration. ATM Performance Parameters. QoS Classes. Measurement Methods. Factors Affecting ATM QoS Performance Parameters. Appendix B: Conformance Examples in a Traffic Contract. Introduction. Example 1: Switched Multi-megabit Data Service (SMDS). Example 2a: Frame Relay Service (FRS). Example 2b: Frame Relay Service (FRS). Example 3: Constant Bit Rate Services. Example 4: LAN Interconnection. Appendix C: Point-to-Mulitpoint Signalling Procedures Using Separate State Machines (Informative). Introduction. Description of the Separate State Machines. Information Flows for Point-to-Multipoint Communication. Appendix D: Example Signalling Codings. ATM Adaptation Layer Parameters. Broadband Bearer Capability. Broadband Low Layer Information. Appendix E: Differences with ITU-T draft Recommendation Q.2931. Appendix F: Guidelines on the use of Bearer Class, Traffic Parameters and QoS. Bearer Class. Allowed Combination of Bearer Capabilities, Traffic Parameters, and QoS. Appendix G: OAM Cell Error Detection Code Field. Appendix H: Glossary.
TL;DR: Two approaches to the design of a high-performance router, the gigabit router and the IP switch are examined, and some detail on the implementation of an IP switch and the protocols associated with IP switching is provided.
Abstract: To cope with the growth in the Internet and corporate IP networks, we require IP routers capable of much higher performance than is possible with existing architectures. This article examines two approaches to the design of a high-performance router, the gigabit router and the IP switch, and then provides some detail on the implementation of an IP switch and the protocols associated with IP switching.
TL;DR: In this paper, the authors proposed a method for congestion management in a frame relay network, where a virtual channel associated with a frame (39) to be transferred is determined, and when the result of the comparison falls outside a predetermined value range, the frame is discarded.
Abstract: The invention relates to a method for congestion management in a frame relay network. In the method, a virtual channel associated with a frame (39) to be transferred is determined. In order to provide a congestion management method which is reliable and capable of rapid responding and which allows event virtual connections to be prioritized with respect to the throughput probability, (a) at least some of the virtual channels are assigned a respective service level; (b) a congestion level having values in a predetermined relationship to the values of the service levels is determined for a network resource (15) liable to congestion; (c) the value representing the service level of the virtual channel of the FR frame (39) is compared with the value representing the congestion level of said resource; and (d) when the result of the comparison falls outside a predetermined value range, the frame (39) is discarded.
TL;DR: In this paper, a virtual router system implements a plurality of virtual routers, and various combinations of resources may be shared by the router system when implementing the virtual routers when the particular combination of resources to share when implementing virtual router is user programmable.
Abstract: A router system implements a plurality of virtual routers. Various combinations of resources may be shared by the router system when implementing the virtual routers. In one embodiment, the particular combination of resources to share when implementing the virtual router is user programmable.