Peterson, L., ed. NodeOS Interface Specification. Active Network Working Group, January 10 2001.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....including interactions with the management node, use a standard bus. LARA PAL (Platform Abstraction Layer) provides a platform independent interface over which di#erent EEs may be instantiated. The holy grail of active networking research is the Node Operating System (NodeOS) The NodeOS [Peterson00a] interface is defined as part of the Active Networks Working Group Architectural Framework [Calvert98] It is intended to provide a minimal common fixed point for active networking in the same way that IP provides a common fixed point for passive Internetworking. The NodeOS is, as its name ....

....usage bounds for untrusted agents. Whilst these techniques do go some way to prevent serious DoS attacks, they are insu#cient for providing e#ective fine grained resource guarantees. More recent work has begun to focus on issues of proper resource control. The specification of the NodeOS [Peterson00a] provides an interface for allocating and scheduling computing and network resources on a programmable node. Early implementations of this interface, such as Bowman [Merugu00] have shown e#ective isolation between multiple flows of packets passing through a node. Java has proved a popular ....

[Article contains additional citation context not shown here]

L Peterson, ed. NodeOS Interface Specification. AN Node OS Working Group, January 2000. Draft. (pp 27, 37, 57, 64, 145)

....in our work [10] 11] Most systems enforce isolation of packet processing between flows (e.g. malicious packets cannot affect the proper processing of other packets) However, QoS issues at the level of processing are addressed only in a few cases. The commonly used NodeOS specification [21] asks for packets to be processed by individual threads to allow for an accounting mechanism. However, methods for admission control and QoS scheduling are not described. 22] describes the problem of scheduling computational resources among competing flows, but relies on being able to ....

Larry Peterson, ed. NodeOS interface specification. Technical report, AN Node OS Working Group, January 2001.

....which can be called by active packets. The switchlets are also programmed in a language that allows formal verification for safe execution. To make systems interoperable, a common architecture for active router operating systems has been proposed. This Node Operating System (NodeOS [Pet01] defines common abstractions for communication and processing resources. On top of the NodeOS, several Execution Environments (EEs) can operate in parallel. Di#erent active functionalities are implemented within the EEs. One instance of a NodeOS compliant architecture is the CANES and Bowman ....

....programmable routers (see Section 2.5.1) enforce isolation of packet processing between flows (e.g. malicious packets cannot e#ect the proper processing of other packets) However, QoS issues at the level of processing are addressed only in a few cases. The commonly used NodeOS specification [Pet01] asks for packets to be processed by individual threads to allow for an accounting mechanism. However, methods for admission control and QoS scheduling are not described. Qie et al. QBPK01] describe the problem of scheduling computational resources among competing flows, but relies on being able ....

Larry Peterson, ed. NodeOS interface specification. Technical report, AN Node OS Working Group, January 2001.

....in our work [5] 4] Most systems enforce isolation of packet processing between flows (e.g. malicious packets cannot effect the proper processing of other packets) However, QoS issues at the level of processing are addressed only in a few cases. The commonly used NodeOS specification [6] asks for packets processor engine 1 processing engine m scheduler queue 1 queue n queue 1 queue n feedback feedback from switch fabric outgoing . processing resource Fig. 1. System Outline. to be processed by individual threads to allow for an accounting mechanism. However, ....

Larry Peterson, ed., "NodeOS interface specification," Tech. Rep., AN Node OS Working Group, Jan. 2001.

....entails the problems of security and safety. Unless sophisticated security mechanisms and resource control are implemented, malicious or erroneous programs can a#ect the execution of other programs. The general switch architecture [5] of an active node consists of a node operating system (NodeOS [31]) and a set of Execution Environments (EEs) which process active packets. Many projects implement EEs in their own router architecture. The first EE was ANTS [49] which used capsules that carry JAVA bytecode from node to node where the code is executed. Others include Switchware [2] PLAN [21] ....

L. Peterson, ed. NodeOS interface specification. Technical report, AN Node OS Working Group, Feb. 1999.

....and limiting resource usage depending on specified policies. Figure 1. Main components of the DARPA AN architecture. The NodeOS plays a crucial role in providing access to local node resources, as well as information about resource availability. A NodeOS API is currently being defined [PET 00] At the moment this API treats four types of resources: computation, memory, communication, and persistent storage. The communication resource is handled through the channel abstraction, which when ready should include QoS support, as well as access to link information such as bandwidth, queue ....

L. PETERSON (ED) ET AL., "NodeOS Interface Specification", (DARPA) AN NodeOS Working Group, draft, January 2000, work in progress.

....CPU cycles, memory, input and output channels, and timers. In order to allow many possible operating systems to provide services to many possible execution environments, the active network node architecture includes a standard specification of system calls (the Node OS Interface Layer in Figure 1) [2]. Execution environments, similar to virtual machines, can be loaded onto an active node using ANETD [3] a daemon that implements a load and go protocol for execution environments. Each execution environment accepts active packets that can initiate the execution of packet specific code. Each ....

L. Peterson (ed.), NodeOS Interface Specification, January 24, 2000.

....for controlling the access from the AAs to local resources, and limiting resource usage depending on specified policies. The NodeOS plays a crucial role in providing access to local node resources, as well as information about resource availability. A NodeOS API is currently being defined [9]. At the moment this API treats four types of resources: computation, memory, communication, and persistent storage. The communication resource is handled through the channel abstraction, which when ready should include QoS support, as well as access to link information such as bandwidth, queue ....

L. Peterson (ed) et al., "NodeOS Interface Specification ", (DARPA) AN NodeOS Working Group, draft, January 2000, work in progress.

....for controlling the access from the AAs to local resources, and limiting resource usage depending on specified policies. The NodeOS plays a crucial role in providing access to local node resources, as well as information about resource availability. A NodeOS API is currently being defined [18]. At the moment this API treats four types of resources: computation, memory, communication, and persistent storage. The communication resource is handled through the channel abstraction, which when ready should include QoS support, as well as access to link information such as bandwidth, queue ....

L. Peterson (ed) et al., "NodeOS Interface Specification", (DARPA) AN NodeOS Working Group, draft, January 2000, work in progress.

....capabilities in the underlying OS and hardware (e.g. multi processing, realtime, etc. but it should also be possible for them to exist on just a set of minimal services. NodeOS Computation Memory Communication Storage Thread pool Memory pool Channels I O Files A A A A A A A UA [8] defines an abstract NodeOS EE interface providing access to the node s resources through a system calls interface. This interface consists of five primary resource abstractions: thread pools, memory pools, channels, files and flows. The first four abstractions are mapped by the NodeOS to actual ....

PETERSON, L., (Editor), "NodeOS Interface Specification," DARPA AN NodeOS Working Group Draft, 1999

....useful for users, Bowman provides an extension mechanism that is analogous to loadable modules in traditional operating systems. Using extensions, the Bowman NodeOS interface can be extended to provide support for additional abstractions such as queues, routing tables, user protocols and services ([15] provides a more complete NodeOS API) The CANEs EE is built on the top of the Bowman NodeOS. It provides a composition framework for active services based on customizing a generic underlying program by injecting code to run in specific points called slots. The composition model basically has two ....

L. Peterson, ed. NodeOS Interface Specifications. AN NodeOS Working Group. Draft.

....in our work [5] 4] Most systems enforce isolation of packet processing between flows (e.g. malicious packets cannot effect the proper processing of other packets) However, QoS issues at the level of processing are addressed only in a few cases. The commonly used NodeOS specification [6] asks for packets processor engine 1 engine m from switch fabric outgoing . processing resource Fig. 1. System Outline. to be processed by individual threads to allow for an accounting mechanism. However, methods for admission control and QoS scheduling are not described. Reference [7] ....

Larry Peterson, ed., "NodeOS interface specification," Tech. Rep., AN Node OS Working Group, Jan. 2001.

.... efforts have begun focusing on the standardization of interfaces in networking equipment, either in the form of control protocols for label switches (IETF GSMP [DHSW00] IP routers (IETF FoRCES [F01] and media gateways (IETF MEGACO [GRR00] or more generic APIs such as those described in [Pet99, Bis00, CF00, dKTG00] It is expected that in a heterogeneous network a variety of solutions are likely to coexist. 3 Service Deployment Framework Large scale service deployment over programmable networks requires an automated installation mechanism. To provide this, a number of new elements ....

L. Peterson. NodeOS Interface Specification. Technical report, DARPA Active Networks Program, June 1999.

....detail on Bowman can be found in [18] Mor detail on CANEs can be found in [5] A. Bowman Bowman waswr;W;W out of necessity, to pr vide aplatfor for CANEs. At the time the Bowman development was beginning (Fall 1998) ther wer no NodeOS implementations available; indeed, the NodeOS specification [10] was still inconsider333 flux. For theserese(S; Bowman does not implement thecurSK t NodeOS specificationprificati , though it includes elements thatar similar to those in the specification. Ther ar four elements of Bowman thatar of inter3 ] namely, channels, a flows,ti and the state ....

L. Peterson (Editor). NodeOS Interface Specification. DARPA AN NodeOS WorkingGrou Draft, 1999.

....in our work [4] 3] Most systems enforce isolation of packet processing between flows (e.g. malicious packets cannot effect the proper processing of other packets) However, QoS issues at the level of processing are addressed only in a few cases. The commonly used NodeOS specification [5] asks for packets to be processed by individual threads to allow for an accounting mechanism. However, methods for admission control and QoS scheduling are not described. 6] describes the problem of scheduling computational resources among competing flows, but relies on being able to ....

Larry Peterson, ed., "NodeOS interface specification," Tech. Rep., AN Node OS Working Group, Jan. 2001.

....and considers implications of the architecture for implementations on a high performance switch or router. The third part (Sections 9 10) discusses some considerations for building practical networks from active nodes. Companion documents describe the functional interface provided by the NodeOS [NodeOS], and the security architecture for the active network [SecArch] 1.2 Status This document reflects the rough consensus of the DARPA active networks research community, as expressed in workshops at Tucson (March 1998) Atlanta (July 1998) New York (November 1998) and in discussions on the ....

...., routing packets between channels and EEs within the active node, mediating access to node resources such as transmission and computing bandwidth, and optionally supporting common services such as routing. The functionality exported by the NodeOS to the EEs is specified in a separate document [NodeOS]. 6.1 Abstractions The NodeOS provides EEs with access to node resources. There are three primary resource abstractions: threads, memory, and channels. The thread and memory abstractions are similar to those of traditional operating systems, while channels implement lower level and or legacy ....

[Article contains additional citation context not shown here]

L. Peterson, ed. NodeOS Interface Specification. AN Working Group Draft, July, 1999.

....allocation (algorithm 2) than algorithm 2. Algorithm 2 tries to keep resource utilization balanced by allocating more slack to the more loaded resource. 9 Related Work Recent interest in providing system support for router programmability has led to the specification of the NodeOS interface [10] which attempts to lay down implementationindependent primitives that a programmable router should provide. NodeOS implementations internally implement these primitives using substrates like language runtimes or specialized OSes [11] and expose the NodeOS interface to router applications. Placing ....

Peterson L., et al, NodeOS Interface Specification.

....The EEs implement security and resource sharing schemes to allow a safe execution of the custom code. The design space of an activenetwork platform can be divided into three elementary components: the hardware platform, the software which consists of the node s operating system (NodeOS) [2] and a set of Execution Environments [3] and the protocol used for communication between active network nodes. This paper puts emphasis on a streamlined protocol between active nodes and the efficient forwarding of activepackets through the OS and EE components on an activenode. While most AN ....

L. Peterson (rson "NodeOS interface specification, " AN Node OS Working Group, http://www.cs.princeton.edu/nsg/papers/nodeos99.ps

....is capable of performing processing of packets as they are being forwarded. Typical implementations range from workstations that act as active routers to high performance switches that are augmented with per port network processors. The definition of a unifying node operating system (NodeOS [3]) aims at making these systems interoperable. While Aggregated Hierarchical Multicast is an application for active networks, we do not go into the details of active networking in this paper. Section II introduces the example applications considered here and shows di#erent information aggregation ....

Larry Peterson, ed., "NodeOS interface specification," Tech. Rep., AN Node OS Working Group, Feb. 1999.

....several aspects that are important to build an Active Network Processing Element with a good overall performance: functionality . performance . scalability The following sections explain the reason behind each aspect and how good overall performance can be achieved. Functionality The NodeOS[2] and the Execution Environment determine the functionality of an ANPE that is exposed to active packets. Typically, there is a tradeoff between additional features and performance. There are some basic features that are characteristics of an active network that have to be supported: Execution ....

Peterson, L. (ed.): "NodeOS Interface Specification". AN Node OS Working Group, October 1998.

....EEs with controlled access to resources such as CPU cycles, memory, input and output channels, and timers. To permit various operating systems to provide services to various EEs, the node architecture includes a standard specification for system calls (the Node OS Interface Layer in Figure 1) [14]. Each EE accepts active packets that initiate execution of packet specific code. Analysis of Figure 1, and real systems, reveals many sources of variability affecting CPU usage by AAs [6] In the hardware layer, the main factors include: processor architecture and frequency, available memory, ....

L. Peterson. Nodeos interface specification. http://www.dcs.uky.edu/#calvert/nodeos-latest.ps, January 2000.

No context found.

Peterson, L., ed. NodeOS Interface Specification. Active Network Working Group, January 10 2001.

No context found.

L. Peterson, ed. NodeOS Interface Specification. AN draft, AN Node OS Working Group, Jan. 2000.

No context found.

Larry Peterson, ed., NodeOS interface specification, Tech Rep., AN Node OS Working group, Jan. 2001.

No context found.

L. Peterson, ed., "NodeOS interface specification," Tech. Rep., AN Node OS Working Group, Jan. 2001.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC