Request for Comments Summary RFC Numbers 3000-3099
RFC 3099
|
Document |
Type |
|
RFC - Informational
(November 2001; No errata)
|
|
Author |
|
Sandy Ginoza
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
Legacy
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
Stream |
Legacy state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
RFC 3099 (Informational)
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group S. Ginoza
Request for Comments: 3099 ISI
Category: Informational November 2001
Request for Comments Summary
RFC Numbers 3000-3099
Status of This Memo
This RFC is a slightly annotated list of the 100 RFCs from RFC 3000
through RFCs 3099. This is a status report on these RFCs. This memo
provides information for the Internet community. It does not specify
an Internet standard of any kind. Distribution of this memo is
unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Note
Many RFCs, but not all, are Proposed Standards, Draft Standards, or
Standards. Since the status of these RFCs may change during the
standards processing, we note here only that they are on the
standards track. Please see the latest edition of "Internet Official
Protocol Standards" for the current state and status of these RFCs.
In the following, RFCs on the standards track are marked [STANDARDS-
TRACK].
RFC Author Date Title
--- ------ ---- -----
3099 Ginoza Nov 2001 Request for Comments Summary
This memo.
Ginoza Informational [Page 1]
RFC 3099 Summary of 3000-3099
3098 Gavin Apr 2001 How to Advertise Responsibly
Using E-Mail and Newsgroups or
- how NOT to $$$$$ MAKE
ENEMIES FAST! $$$$$
This memo offers useful suggestions for responsible advertising
techniques that can be used via the internet in an environment where the
advertiser, recipients, and the Internet Community can coexist in a
productive and mutually respectful fashion. This memo provides
information for the Internet community.
3097 Braden Apr 2001 RSVP Cryptographic
Authentication -- Updated
Message Type Value
This memo resolves a duplication in the assignment of RSVP Message
Types, by changing the Message Types assigned by RFC 2747 to Challenge
and Integrity Response messages. [STANDARDS TRACK]
3096 Degermark Jul 2001 Requirements for robust
IP/UDP/RTP header compression
This document contains requirements for robust IP/UDP/RTP (Internet
Protocol/User Datagram Protocol/Real-Time Transport Protocol) header
compression to be developed by the ROHC (Robust Header Compression) WG.
It is based on the ROHC charter, discussions in the WG, the 3GPP
document "3GPP TR 23.922", version 1.0.0 of October 1999, as well as
contributions from 3G.IP. This memo provides information for the
Internet community.
3095 Bormann Jul 2001 RObust Header Compression
(ROHC): Framework and four
profiles: RTP, UDP, ESP, and
uncompressed
This document specifies a highly robust and efficient header compression
scheme for RTP/UDP/IP (Real-Time Transport Protocol, User Datagram
Protocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating Security
Payload) headers. [STANDARDS TRACK]
Ginoza Informational [Page 2]
RFC 3099 Summary of 3000-3099
3094 Sprague Apr 2001 Tekelec's Transport Adapter
Layer Interface
This document proposes the interfaces of a Signaling Gateway, which
provides interworking between the Switched Circuit Network (SCN) and an
IP network. This memo provides information for the Internet community.
3093 Gaynor 1 Apr 2001 Firewall Enhancement Protocol
(FEP)
Internet Transparency via the end-to-end architecture of the Internet
has allowed vast innovation of new technologies and services [1].
However, recent developments in Firewall technology have altered this
model and have been shown to inhibit innovation. We propose the
Firewall Enhancement Protocol (FEP) to allow innovation, without
violating the security model of a Firewall. This memo provides
information for the Internet community.
3092 Eastlake 1 Apr 2001 Etymology of "Foo"
Approximately 212 RFCs so far, starting with RFC 269, contain the terms
`foo', `bar', or `foobar' as metasyntactic variables without any proper
explanation or definition. This document rectifies that deficiency.
This memo provides information for the Internet community.
3091 Kennedy 1 Apr 2001 Pi Digit Generation Protocol
This memo defines a protocol to provide the Pi digit generation service
Show full document text