CurrentINFORMATIONALIETF stream

RFC 3303: Middlebox communication architecture and framework

In plain English — editorial summary, not part of the RFC

There are a variety of intermediate devices in the Internet today that require application intelligence for their operation. Datagrams pertaining to real-time streaming applications such as SIP and H.323 and peer-to-peer applications such as Napster and NetMeeting cannot be identified by merely examining packet headers.

Document record

Document ID
RFC3303
Published
August 2002
Authors
P. Srisuresh; J. Kuthan; J. Rosenberg; A. Molitor; A. Rayhan
Status
INFORMATIONAL
Stream
IETF
Area
tsv
Pages
34
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3303-middlebox-communication-architecture-and-framework