RFC 2129: Toshiba's Flow Attribute Notification Protocol (FANP) Specification
In plain English — editorial summary, not part of the RFC
This memo discusses Flow Attribute Notification Protocol (FANP), which is a protocol between neighbor nodes for the management of cut-through packet forwarding functionalities. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2129
- Published
- April 1997
- Authors
- K. Nagami; Y. Katsube; Y. Shobatake; A. Mogi; S. Matsuzawa; T. Jinmei; H. Esaki
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2430A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)Current
October 1998
- RFC 2105Cisco Systems' Tag Switching Architecture OverviewCurrent
February 1997
- RFC 1953Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0Current
May 1996
- RFC 2307An Approach for Using LDAP as a Network Information ServiceCurrent
March 1998
- RFC 2340Nortel's Virtual Network Switching (VNS) OverviewCurrent
May 1998
- RFC 2345Domain Names and Company Name RetrievalCurrent
May 1998
- RFC 2658RTP Payload Format for PureVoice(tm) AudioCurrent
August 1999
- RFC 2697A Single Rate Three Color MarkerCurrent
September 1999
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?