RFC 2057: Source Directed Access Control on the Internet
In plain English — editorial summary, not part of the RFC
This memo was developed from a deposition that I submitted as part of a challenge to the Communications Decency Act of 1996, part of the Telecommunications Reform Act of 1996. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2057
- Published
- November 1996
- Authors
- S. Bradner
- 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 2077The Model Primary Content Type for Multipurpose Internet Mail ExtensionsUpdated
January 1997
- RFC 1049Content-type header field for Internet messagesCurrent
March 1988
- RFC 1894An Extensible Message Format for Delivery Status NotificationsObsoleted
January 1996
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 1999
- RFC 3297Content Negotiation for Messaging Services based on EmailCurrent
July 2002
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3451Layered Coding Transport (LCT) Building BlockObsoleted
December 2002
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 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?