RFC 3077: A Link-Layer Tunneling Mechanism for Unidirectional Links
In plain English — editorial summary, not part of the RFC
This document describes a mechanism to emulate full bidirectional connectivity between all nodes that are directly connected by a unidirectional link. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3077
- Published
- March 2001
- Authors
- E. Duros; W. Dabbous; H. Izumiyama; N. Fujii; Y. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3033The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet ProtocolCurrent
January 2001
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 3122Extensions to IPv6 Neighbor Discovery for Inverse Discovery SpecificationCurrent
June 2001
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
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?