Proceedings of the ACM Symposium on Communications Architectures &Amp; Protocols 1990
DOI: 10.1145/99508.99545
|View full text |Cite
|
Sign up to set email alerts
|

Protocol implementation on the Nectar Communication Processor

Abstract: Wc have built a high-speed local-area network called Nectar that uses programmable communication processors as host interfaces. In contrast to most protocol engines, our communication processors have a flexible runtime system that supports multiple transport protocols as well as application-specific activities. In particular, we have implemented the TCP/IP protocol suite and Nectar-specific communication protocols on the communication processor. The Nectar network currently has 25 hosts and has been in use for… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
15
0

Year Published

1993
1993
2007
2007

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 51 publications
(15 citation statements)
references
References 11 publications
0
15
0
Order By: Relevance
“…The programmability can be used by applications to customize protocol processing. Cooper, et al [8], report that TCP/IP and a number of Nectar-specific protocols have been implemented on the CAB.…”
Section: Example Host Interface Architecturesmentioning
confidence: 99%
“…The programmability can be used by applications to customize protocol processing. Cooper, et al [8], report that TCP/IP and a number of Nectar-specific protocols have been implemented on the CAB.…”
Section: Example Host Interface Architecturesmentioning
confidence: 99%
“…Although this work is redundant with respect to the host's network stack, it allows self-securing NIs to be deployed with no client software modification. For NIs that offload higher-level protocols (e.g., IP security or TCP) from the host [Cooper90,Dalton93], redundant work becomes unnecessary because the only instance of the work is already within the NI. Self-securing NIs enforce policies set by the network administrator, just as a centralized firewall would.…”
Section: Self-securing Network Interfacesmentioning
confidence: 99%
“…Implementations include the XTP Protocol Engine [8], the Nectar communications processor [14], and the VMP adaptor [23]. Follow on work [22,33] based on the Protocol Engine architecture implemented TCP/IP on the host interface for a 622Mb/s ATM network.…”
Section: Introductionmentioning
confidence: 99%