RFC 2768: Network Policy and Services: A Report of a Workshop on Middleware
In plain English — editorial summary, not part of the RFC
An ad hoc middleware workshop was held at the International Center for Advanced Internet Research in December 1998. The need for a more organized framework for middleware R&D was recognized, and a list of specific topics needing further work was identified. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2768
- Published
- February 2000
- Authors
- B. Aiken; J. Strassner; B. Carpenter; I. Foster; C. Lynch; J. Mambretti; R. Moore; B. Teitelbaum
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)Obsoleted
February 2000
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
- RFC 2316Report of the IAB Security Architecture WorkshopCurrent
April 1998
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
- RFC 2780IANA Allocation Guidelines For Values In the Internet Protocol and Related HeadersUpdated
March 2000
- RFC 2828Internet Security GlossaryObsoleted
May 2000
- RFC 2705Media Gateway Control Protocol (MGCP) Version 1.0Obsoleted
October 1999
- RFC 2835IP and ARP over HIPPI-6400 (GSN)Updated
May 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?