Active Network NodeOS Working Group. NodeOS interface specification. Available as http://www.cs.princeton.edu/nsg/papers/nodeos.ps, Jan. 2000. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
Hybrid Resource Control of Active Extensions - Patel, Lepreau (2003) (2 citations) (Correct)
.... RBCLICK In this section, we present the design of RBClick, an active network environment for best effort active extensions, which implements hybrid resource control. To discuss RBClick in terms of established terminology, we borrow active networking terminology from the NodeOS specification [18] and use Click terminology as defined in [4] A. Background RBClick is designed to be implemented in Janos, an active network operating system that implements the NodeOS and EE layers of an active node [5] Figure 2 shows a block diagram of the software layers in Janos and their correspondence ....
....A. Background RBClick is designed to be implemented in Janos, an active network operating system that implements the NodeOS and EE layers of an active node [5] Figure 2 shows a block diagram of the software layers in Janos and their correspondence with the DARPA active network node architecture [18]. Janos supports Java based active applications on top of the Bees execution environment which runs on top of the resource controlling JVM, called JanosVM. Together, Bees and JanosVM form the EE layer of an active node and run on top of Moab, the NodeOS in Janos. Moab is an active node operating ....
[Article contains additional citation context not shown here]
Active Network NodeOS Working Group, "NodeOS interface specification, " Available as http://www.cs.princeton.edu/nsg/papers/nodeos.ps, Jan. 2000.
Design and Evaluation of a High-Performance.. - Kuhns, DeHart.. (2002) (Correct)
....Module Module Software based FPX Four Port Switch EC EC Switching ccp North Program RAD SDRAM SDRAM Data Data Bridge South Bridge EDO DRAM Data SRAM Data Module Intel Embedded PCI Interface PCI Bus Figure 3. An FPX SPC Port Processor support such as Java and NodeOS [6, 7]. This approach results in an inflexible, high performance standard packet forwarding path and a relatively low performance active processing path. The DER takes a different approach to supporting active processing and high performance packet forwarding. The port processors are implemented using ....
DARPA Active Network Node OS Working Group, NodeOS Interface Specification, Jan 2001.
An OS Interface for Active Routers - Peterson, Gottlieb, Hibler.. (2001) (12 citations) (Correct)
....and NSF grants ANI 99 06704 and ANI 00 82493. 3] 11] and CANES [5] At the topmost level are the active applications (AA) themselves. Environments Fig. 1. Software layers running on an active router. We were major contributors to developing and docu menting the interface [1] between the bottom two layers in Figure 1. This paper focuses on that interface, making two contributions. The first is to motivate and describe the NodeOS interface. While similar in many respects to a standard API such as POSIX, the emphasis of an active router on forwarding packets makes this ....
....the NodeOS requires a mechanism that is not particularly unique to active networks, the NodeOS interface should borrow from established interfaces, such as POSIX. III. ARCHITECTURE The NodeOS interface defines five primary abstractions: thread pools, memory pools, channels, files, and domains [1]. The first four encapsulate a system s four types of re sources: computation, memory, communication, and persistent storage. The fifth abstraction, the domain, is used to aggregate control and scheduling of the other four ab stractions. This section motivates and describes these five ....
Active Network NodeOS Working Group. NodeOS interface specification. Available as http://www.cs.princeton.edu/nsg/- papers/nodeos.ps, January 2000.
Strong Security for Active Networks - Murphy, Lewis, Puga, Watson, Yee (2001) (11 citations) (Correct)
....an ar hitectur for an active node [10] that depicts a node ascomprLfl7L a NodeOS and oneor mor Execution EnvirRREP ts. The Execution EnvirWOOfl ts (EE s)pr vide aprSS( fl ing interOPL or virOPL machine that can be prRERLfl ed or contrflWES by the active packets. The NodeOS interWOW document [9], 11] of the communitydescr ( es thereflWOWE abstrWE ions of an active node operWSPR system asthrEW pools (computation) memor pools(memor00 channels (communication) files (perRW0 tentstorR(fl and domains. 1 Domainsar theprflR(L abstrRREP nfor rrLWWfl management and ar allocated a set of ....
AN Node OS Working Group, "NodeOS interface specification," January 2000, available online at http://www.cs.princeton.edu/nsg/papers/nodeos.ps.
The Network I/O Daemon - netiod - Gradman, Berson, Braden (2000) (Correct)
....experiments on Unix platforms. Netiod is a Unix process for demultiplexing incoming active packets to active network Execution Environments (EEs) 3] on behalf of Active Applications (AAs) and for sending active packets. Netiod implements the network I O model of the NodeOS channel abstraction [4]. This model, which is described below in Section 1.1, also provides a convenient vehicle for describing the functions of netiod. Section 1.2 explains the objectives of netiod and Section 1.3 outlines its design. Section 1.4 Section 2 describes the service interface seen by the active user. ....
....2 describes the service interface seen by the active user. Section 3 outlines an access control mechanism that is under consideration. Section 4 describes the implementation, and Section 5 gives the current implementation status. 1. 1 The NodeOS Channel Abstraction The NodeOS interface spec [4] defines input channels (InChannels) and output channels (OutChan nels) for network I O. An InChannel specifies a packet filter to select a subset of the input stream and present it to an active user an EE or an AA that created the channel. An OutChannel allows the active user to send ....
[Article contains additional citation context not shown here]
AN Node OS Working Group. Nodeos interface specification. http://www.cs.princeton.edu/ nsg/papers/nodeos.ps, January 2000.
RCANE: A Resource Controlled Framework for Active Network Services - Menage (1999) (27 citations) (Correct)
....code. This approach is taken by PLAN [5] and Smart Packets [13] PLAN also extends the concept of the hop count found in IP to apply to recursive or remote invocations, bounding the resources that a packet can consume globally. The Active Networks Working Group NodeOS Interface Specification [14] aims to standardise on an API addressing similar issues to Rcane, although at a lower level of abstraction. 5.2 Resource Control and Isolation in Safe Languages JRes [15] provides Java resource control using minimal runtime support. This provides portability, but with high accounting overheads. ....
Active Networks NodeOS Working Group. NodeOS Interface Specification. Draft.
Janos: A Java-oriented OS for Active Network Nodes - Patrick Tullmann Mike (2001) (4 citations) Self-citation (Group) (Correct)
No context found.
Active Network NodeOS Working Group. NodeOS interface specification. Available as http://- 11 www.cs.princeton.edu/nsg/papers/nodeos.ps, Jan. 2000.
Hybrid Resource Control for Fast-Path Active Extensions - Patel (2003) (Correct)
No context found.
Active Network NodeOS Working Group. NodeOS interface specification. Available as http://www.cs.princeton.edu/nsg/papers/nodeos.ps, Jan. 2000.
A Framework for Resource Management in Active Nodes - Lazanakis, Karetsos.. (2001) (Correct)
No context found.
AN Node OS Working Group, "NodeOS Interface Specification", January 2000
Management of Active and Programmable Networks - Alex Galis Alvin (Correct)
No context found.
AN Node OS Working Group, "NodeOS Interface Specification", January 2000
Clack: An active network platform - Yuen, Lo, Jha (Correct)
No context found.
Active Network NodeOS Working Group. NodeOS interface specification. Available as http://www.cs.princeton.edu/nsg/papers/nodeos.ps, January 2000.
An Active Network Services Architecture for.. - Jaeger, Duncan.. (1999) (2 citations) (Correct)
No context found.
AN Node OS Working Group, NodeOS Interface Specification", June 15, 1999
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