RFC 2316: Report of the IAB Security Architecture Workshop
In plain English — editorial summary, not part of the RFC
On 3-5 March 1997, the IAB held a security architecture workshop at Bell Labs in Murray Hill, NJ. We identified the core security components of the architecture, and specified several documents that need to be written. Most importantly, we agreed that security was not optional, and that it needed to be designed in from the beginning. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2316
- Published
- April 1998
- Authors
- S. Bellovin
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 2902Overview of the 1998 IAB Routing WorkshopCurrent
August 2000
- RFC 3238IAB Architectural and Policy Considerations for Open Pluggable Edge ServicesCurrent
January 2002
- RFC 2282IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
February 1998
- RFC 2450Proposed TLA and NLA Assignment RuleCurrent
December 1998
- RFC 2130The Report of the IAB Character Set Workshop held 29 February - 1 March, 1996Updated
April 1997
- RFC 2027IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
October 1996
- RFC 2727IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall CommitteesObsoleted
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?