Overview of the 2002 IAB Network Management Workshop

Schoenwaelder, Juergen

doi:10.17487/rfc3535

Cited by 40 publications

(32 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The IAB, for example, discussed these concerns at a special Network Management Workshop, which was organized in summer 2002. One of the conclusions at that workshop was that it becomes time to investigate alternative network management technologies, in particular those that take advantage of XML technology [1], [2].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Comparing the performance of SNMP and Web services-based management

Pras

Drevers

Meent

et al. 2004

IEEE Trans. Netw. Serv. Manage.

View full text Add to dashboard Cite

Abstract-This paper compares the performance of Web services based network monitoring to traditional, SNMP based, monitoring. The study focuses on the ifTable, and investigates performance as function of the number of retrieved objects. The following aspects are examined: bandwidth usage, CPU time, memory consumption and round trip delay. For our study several prototypes of Web services based agents were implemented; these prototypes can retrieve single ifTable elements, ifTable rows, ifTable columns or the entire ifTable. This paper presents a generic formula to calculate SNMP's bandwidth requirements; the bandwidth consumption of our prototypes was compared to that formula. The CPU time, memory consumption and round trip delay of our prototypes was compared to Net-SNMP, as well as several other SNMP agents. Our measurements show that SNMP is more efficient in cases where only a single object is retrieved; for larger number of objects Web services may be more efficient. Our study also shows that, if performance is the issue, the choice between BER (SNMP) or XML (Web services) encoding is generally not the determining factor; other choices can have stronger impact on performance.

show abstract

Section: Introductionmentioning

confidence: 99%

“…This difference may be particularly interesting whenever large amounts of management data must be exchanged. A good example is the case where software of cable modems must be updated; at this moment this is often done via SNMP [1]. Another example is the retrieval of interface specific data from access switches and DSLAMs.…”

Section: Introductionmentioning

confidence: 99%

Comparing the performance of SNMP and Web services-based management

Pras

Drevers

Meent

et al. 2004

IEEE Trans. Netw. Serv. Manage.

View full text Add to dashboard Cite

show abstract

“…The decision in 2002 [44] to stop any further development of SNMP and the focus of the management community to XML-based technologies prevented further evolution of these technologies. Though the Expression MIB could be used to perform a set of more complex monitoring tasks such as a the query tool introduced later to minimize the processing overhead of WS monitoring operations, its use as shown later is impractical and introduces greater overhead.…”

Section: Discussionmentioning

confidence: 99%

On the Performance and Scalability of Web Services for Monitoring MPLS-based Networks

2009

View full text Add to dashboard Cite

Web Services is an XML-based technology that has attracted significant attention for building distributed Internet services. Considerable research efforts have been trying to extend it to become a unifying management technology; initial evaluation efforts have demonstrated promising application potential in the domain of network and service management. This paper analyzes the monitoring requirements of a management system used in architectures for providing quality of service, and shows how Web Services can be used effectively to fulfill these requirements. In order to achieve this, a WS-based framework was designed and a query tool was developed to support distributed, optimized retrieval of management information exposed as Web Services. The query tool supports selective and bulk retrieval from MPLS-capable routers. Management information retrieval is demonstrated through three monitoring scenarios, and the measured performance in terms of latency and bandwidth is compared against a conventional approach based on SNMP.

show abstract

“…Management frameworks [32] are not optimized for frequent updates between the manager and the managed entity and tend to replace humans, e.g. as a CLI replacement.…”

Section: Comparisson Of Network Programmability Approachesmentioning

confidence: 99%

Network Programmability With ForCES

Haleplidis

Salim²,

Halpern

et al. 2015

IEEE Commun. Surv. Tutorials

View full text Add to dashboard Cite

Network programmability has re-emerged as top item of the networking research agenda as Software Defined Networking (SDN) gained wide acceptance simultaneously in vendor product line plans and operator expectations for future deployments. One of the key ingredients for the successful deployment of SDN technologies are standardized models, mechanisms, and protocols for the separation of the control and forwarding planes. The Internet Engineering Task Force (IETF) standardization effort on Forwarding and Control Element Separation (ForCES) has published a set of standards track documents which specify in detail a comprehensive architectural framework and the respective standard protocols which can be employed to implement the separation of these two planes in a flexible, scalable and vendor-agnostic yet fully interoperable manner. The IETF standards on ForCES define how to achieve said separation through a complete and modular system model of the forwarding plane elements. In the ForCES model every network element is composed of numerous logically separate and well-defined functional entities that cooperate to provide the desired overall functionality, such as a routing or IP switching. The elegance of the model lies in the fact that a ForCES-based implementation of a network element is indistinguishable from a traditional ("closed-box") network element and therefore can be deployed in the field without any need for migration to a new architecture. Conversely, ForCES allows for rapid prototyping and agile deployment of new architectures as emphasis is placed on software-defined functionality and full programmability. The difference of ForCES from other SDN approaches that depend on logically centralized controllers and the deployment of solely simple or "dumb" switches is that ForCES standards provide a complete toolbox to design, implement, and interoperate ForCES-based network elements with both previously deployed infrastructures as well as in experimental or early-deployment phase endeavors. An example of the former is the implementation of 3GPP-standardized network elements such as a packet gateway (PGW). Examples of the latter include the use of ForCES for network function virtualization (NFV) proves-ofconcepts. This paper surveys the programmable networks and SDN area and provides a comprehensive tutorial on ForCES by summarizing numerous standards documents and thus making the technology easily understood by the wider research community. We present the design goals, choices and tradeoffs for this standardized approach for network programmability and provide a thorough primer on the ForCES model and protocol. The article also surveys recent independent interoperable implementations that showcase the full spectrum of ForCES applications in the era of NFV and SDN.

show abstract

Overview of the 2002 IAB Network Management Workshop

Cited by 40 publications

References 3 publications

Comparing the performance of SNMP and Web services-based management

Comparing the performance of SNMP and Web services-based management

On the Performance and Scalability of Web Services for Monitoring MPLS-based Networks

Network Programmability With ForCES

Contact Info

Product

Resources

About