RFC 1953: Ipsilon Flow Management Protocol Specification for IPv4 Version 1.0
In plain English — editorial summary, not part of the RFC
The Ipsilon Flow Management Protocol (IFMP), is a protocol for allowing a node to instruct an adjacent node to attach a layer 2 label to a specified IP flow. This document provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1953
- Published
- May 1996
- Authors
- P. Newman; W. Edwards; R. Hinden; E. Hoffman; F. Ching Liaw; T. Lyon; G. Minshall
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1923RIPv1 Applicability Statement for Historic StatusCurrent
March 1996
- RFC 2080RIPng for IPv6Current
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 2333NHRP Protocol Applicability StatementCurrent
April 1998
- RFC 27726Bone Backbone Routing GuidelinesUpdated
February 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?