As per Relevance of the word provides, we have this rfc below:
Network Working Group S.
Request for Comments: 3099
Category: Informational November 2001
Request for Comments
RFC Numbers 3000-3099
Status of This
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
provides information for the Internet community. It does not
an Internet standard of any kind. Distribution of this memo
unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
Many RFCs, but not all, are Proposed Standards, Draft Standards,
Standards. Since the status of these RFCs may change during
standards processing, we note here only that they are on
standards track. Please see the latest edition of "Internet
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
--- ------ ---- -----
3099 Ginoza Nov 2001 Request for Comments
This memo
Ginoza Informational [Page 1]
RFC 3099 Summary of 3000-3099
3098 Gavin Apr 2001 How to Advertise
Using E-Mail and Newsgroups
- how NOT to $$$$$
ENEMIES FAST! $$$$$
This memo offers useful suggestions for responsible
techniques that can be used via the internet in an environment where
advertiser, recipients, and the Internet Community can coexist in
productive and mutually respectful fashion. This memo
information for the Internet community
3097 Braden Apr 2001 RSVP
Authentication --
Message Type
This memo resolves a duplication in the assignment of RSVP
Types, by changing the Message Types assigned by RFC 2747 to
and Integrity Response messages. [STANDARDS TRACK
3096 Degermark Jul 2001 Requirements for
IP/UDP/RTP header
This document contains requirements for robust IP/UDP/RTP (
Protocol/User Datagram Protocol/Real-Time Transport Protocol)
compression to be developed by the ROHC (Robust Header Compression) WG
It is based on the ROHC charter, discussions in the WG, the 3
document "3GPP TR 23.922", version 1.0.0 of October 1999, as well
contributions from 3G.IP. This memo provides information for
Internet community
3095 Bormann Jul 2001 RObust Header
(ROHC): Framework and
profiles: RTP, UDP, ESP,
This document specifies a highly robust and efficient header
scheme for RTP/UDP/IP (Real-Time Transport Protocol, User
Protocol, Internet Protocol), UDP/IP, and ESP/IP (Encapsulating
Payload) headers. [STANDARDS TRACK
Ginoza Informational [Page 2]
RFC 3099 Summary of 3000-3099
3094 Sprague Apr 2001 Tekelec's Transport
Layer
This document proposes the interfaces of a Signaling Gateway,
provides interworking between the Switched Circuit Network (SCN) and
IP network. This memo provides information for the Internet community
3093 Gaynor 1 Apr 2001 Firewall Enhancement
(FEP
Internet Transparency via the end-to-end architecture of the
has allowed vast innovation of new technologies and services [1].
However, recent developments in Firewall technology have altered
model and have been shown to inhibit innovation. We propose
Firewall Enhancement Protocol (FEP) to allow innovation,
violating the security model of a Firewall. This memo
information for the Internet community
3092 Eastlake 1 Apr 2001 Etymology of "Foo
Approximately 212 RFCs so far, starting with RFC 269, contain the
`foo', `bar', or `foobar' as metasyntactic variables without any
explanation or definition. This document rectifies that deficiency
This memo provides information for the Internet community
3091 Kennedy 1 Apr 2001 Pi Digit Generation
This memo defines a protocol to provide the Pi digit generation
(PIgen) used between clients and servers on host computers. This
provides information for the Internet community
3090 Lewis Mar 2001 DNS Security
Clarification on Zone
The definition of a secured zone is presented, clarifying and
sections of RFC 2535. RFC 2535 defines a zone to be secured based on
per algorithm basis, e.g., a zone can be secured with RSA keys, and
secured with DSA keys. This document changes this to define a zone
be secured or not secured regardless of the key algorithm used (or
used). To further simplify the determination of a zone's status
"experimentally secure" status is deprecated. [STANDARDS TRACK
Ginoza Informational [Page 3]
RFC 3099 Summary of 3000-3099
3089 Kitamura Apr 2001 A SOCKS-based IPv6/IPv
Gateway
This document describes a SOCKS-based IPv6/IPv4 gateway mechanism
enables smooth heterogeneous communications between the IPv6 nodes
IPv4 nodes. This memo provides information for the Internet community
3088 Zeilenga Apr 2001 OpenLDAP Root Service
experimental LDAP
The OpenLDAP Project is operating an experimental LDAP (
Directory Access Protocol) referral service known as the "OpenLDAP
Service". The automated system generates referrals based upon
location information published in DNS SRV RRs (Domain Name
location of services resource records). This document describes
service. This memo defines an Experimental Protocol for the
community
3087 Campbell Apr 2001 Control of Service
using SIP Request-
This memo describes a useful way to conceptualize the use of
standard SIP (Session Initiation Protocol) Request-URI (Uniform
Identifier) that the authors and many members of the SIP community
is suitable as a convention. It does not define any new protocol
respect to RFC 2543. This memo provides information for the
community
3086 Nichols Apr 2001 Definition of
Services Per Domain
and Rules for their
This document defines and discusses Per-Domain Behaviors in detail
lays out the format and required content for contributions to
Diffserv WG on PDBs and the procedure that will be applied
individual PDB specifications to advance as WG products. This format
specified to expedite working group review of PDB submissions.
memo provides information for the Internet community
Ginoza Informational [Page 4]
RFC 3099 Summary of 3000-3099
3085 Coates Mar 2001 URN Namespace for
This document describes a URN (Uniform Resource Name) namespace
identifying NewsML NewsItems. This memo provides information for
Internet community
3084 Chan Mar 2001 COPS Usage for
Provisioning (COPS-PR
This document describes the use of the Common Open Policy Service (COPS
protocol for support of policy provisioning (COPS-PR). [
TRACK
3083 Woundy Mar 2001 Baseline Privacy
Management Information
for DOCSIS Compliant
Modems and Cable
Termination
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it defines a basic set of managed objects for SNMP-
(Simple Network Management Protocol) management of the Baseline
Interface (BPI), which provides data privacy for DOCSIS 1.0 (Data-Over
Cable Service Interface Specifications) compliant Cable Modems and
Modem Termination Systems. This MIB is defined as an extension to
DOCSIS Radio Frequency Interface MIB, RFC 2670. This memo
information for the Internet community
3082 Kempf Mar 2001 Notification and
for
The Service Location Protocol (SLP) provides mechanisms whereby
agent clients can advertise and user agent clients can query
services. The design is very much demand-driven, so that user
only obtain service information when they specifically ask for it
There exists another class of user agent applications, however,
requires notification when a new service appears or disappears. In
RFC 2608 design, these applications are forced to poll the network
catch changes. In this document, we describe a protocol for
such clients to be notified when a change occurs, removing the need
polling. This memo defines an Experimental Protocol for the
community
Ginoza Informational [Page 5]
RFC 3099 Summary of 3000-3099
3081 Rose Mar 2001 Mapping the BEEP Core onto
This memo describes how a BEEP (Blocks Extensible Exchange Protocol
session is mapped onto a single TCP (Transmission Control Protocol
connection. [STANDARDS TRACK
3080 Rose Mar 2001 The Blocks Extensible
Protocol
This memo describes a generic application protocol kernel
connection-oriented, asynchronous interactions called the BEEP (
Extensible Exchange Protocol) core. [STANDARDS TRACK
3079 Zorn Mar 2001 Deriving Keys for use
Microsoft Point-to-
Encryption (MPPE
This document describes the method used to derive initial MPPE
keys from a variety of credential types. It is expected that this
will be updated whenever Microsoft defines a new key derivation
for MPPE, since its primary purpose is to provide an open,
accessible reference for third-parties wishing to interoperate
Microsoft products. This memo provides information for the
community
3078 Pall Mar 2001 Microsoft Point-To-
Encryption (MPPE)
This document describes the use of the Microsoft Point to
Encryption (MPPE) to enhance the confidentiality of PPP-
packets. This memo provides information for the Internet community
3077 Duros Mar 2001 A Link-Layer
Mechanism for
This document describes a mechanism to emulate full
connectivity between all nodes that are directly connected by
unidirectional link. [STANDARDS TRACK
Ginoza Informational [Page 6]
RFC 3099 Summary of 3000-3099
3076 Boyer Mar 2001 Canonical XML Version 1.0
This specification describes a method for generating a
representation, the canonical form, of an XML document that accounts
the permissible changes. This memo provides information for
Internet community
3075 Eastlake Mar 2001 XML-Signature Syntax
This document specifies XML (Extensible Markup Language)
signature processing rules and syntax. [STANDARDS TRACK
3074 Volz Feb 2001 DHC Load Balancing
This document proposes a method of algorithmic load balancing
[STANDARDS TRACK
3073 Collins Mar 2001 Portable Font Resource (PFR) -
application/font-tdpfr
Sub-type
This document describes the registration of the Multipurpose
Mail Extensions (MIME) sub-type application/font-tdpfr. The encoding
defined by the PFR Specification. This memo provides information
the Internet community
3072 Wildgrube Mar 2001 Structured Data
Format (SDXF
This specification describes an all-purpose interchange format for
as a file format or for net-working. This memo provides information
the Internet community
Ginoza Informational [Page 7]
RFC 3099 Summary of 3000-3099
3071 Klensin Feb 2001 Reflections on the DNS,
1591, and Categories
This document is being published primarily for historical context
comparative purposes, essentially to document some thoughts about
1591 might have been interpreted and adjusted by the Internet
Numbers Authority (IANA) and ICANN to better reflect today's world
retaining characteristics and policies that have proven to be
in supporting Internet growth and stability. This memo
information for the Internet community
3070 Rawat Feb 2001 Layer Two Tunneling
(L2TP) over Frame
This document describes how L2TP is implemented over Frame
Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs).
[STANDARDS TRACK
3069 McPherson Feb 2001 VLAN Aggregation for
IP Address
This document introduces the concept of Virtual Local Area
(VLAN) aggregation as it relates to IPv4 address allocation. This
provides information for the Internet community
3068 Huitema Jun 2001 An Anycast Prefix for 6to
Relay
This memo introduces a "6to4 anycast address" in order to simplify
configuration of 6to4 routers. It also defines how this address will
used by 6to4 relay routers, how the corresponding "6to4 anycast prefix
will be advertised in the IGP and in the EGP. The memo documents
reservation by IANA (Internet Assigned Numbers Authority) of the "6to
relay anycast prefix." [STANDARDS TRACK
Ginoza Informational [Page 8]
RFC 3099 Summary of 3000-3099
3067 Arvidsson Feb 2001 TERENA's Incident
Description and
Format
The purpose of the Incident Object Description and Exchange Format is
define a common data format for the description, archiving and
of information about incidents between CSIRTs (Computer
Incident Response Teams) (including alert, incident in investigation
archiving, statistics, reporting, etc.). This document describes
high-level requirements for such a description and exchange format
including the reasons for those requirements. This memo
information for the Internet community
3066 Alvestrand Jan 2001 Tags for the Identification
This document describes a language tag for use in cases where it
desired to indicate the language used in an information object, how
register values for use in this language tag, and a construct
matching such language tags. This document specifies an Internet
Current Practices for the Internet Community, and requests
and suggestions for improvements
3065 Traina Feb 2001 Autonomous
Confederations for
This document describes an extension to BGP which may be used to
a confederation of autonomous systems that is represented as a
autonomous system to BGP peers external to the confederation,
removing the "full mesh" requirement. The intention of this
is to aid in policy administration and reduce the management
of maintaining a large autonomous system. [STANDARDS TRACK
3064 Foster Feb 2001 MGCP CAS
This document contains a collection of media gateway Channel
Signaling (CAS) packages for R1 CAS, North American CAS, CAS
interconnect as well as basic FXO support. This memo
information for the Internet community
Ginoza Informational [Page 9]
RFC 3099 Summary of 3000-3099
3063 Ohba Feb 2001 MPLS Loop Prevention
This paper presents a simple mechanism, based on "threads", which can
used to prevent Multiprotocol Label Switching (MPLS) from setting
label switched path (LSPs) which have loops. This memo defines
Experimental Protocol for the Internet community
3062 Zeilenga Feb 2001 LDAP Password Modify
This document describes an LDAP extended operation to allow
of user passwords which is not dependent upon the form of
authentication identity nor the password storage mechanism used
[STANDARDS TRACK
3061 Mealling Feb 2001 A URN Namespace of
This document describes a Uniform Resource Name (URN) namespace
contains Object Identifiers (OIDs). This memo provides information
the Internet community
3060 Moore Feb 2001 Policy Core Information
-- Version 1
This document presents the object-oriented information model
representing policy information developed jointly in the IETF
Framework WG and as extensions to the Common Information Model (CIM
activity in the Distributed Management Task Force (DMTF). [
TRACK
3059 Guttman Feb 2001 Attribute List Extension
the Service Location
This document specifies a SLPv2 extension which allows a User Agent (UA
to request a service's attributes be included as an extension to
Reply messages. This will eliminate the need for multiple round
messages for a UA to acquire all service information. [STANDARDS TRACK
Ginoza Informational [Page 10]
RFC 3099 Summary of 3000-3099
3058 Teiwes Feb 2001 Use of the IDEA
Algorithm in
This memo specifies how to incorporate International Data
Algorithm (IDEA) into CMS or S/MIME as an additional strong
for symmetric encryption. This memo provides information for
Internet community
3057 Morneault Feb 2001 ISDN Q.921-User
This document defines a protocol for backhauling of ISDN Q.921
messages over IP using the Stream Control Transmission Protocol (SCTP).
This protocol would be used between a Signaling Gateway (SG) and
Gateway Controller (MGC). [STANDARDS TRACK
3056 Carpenter Feb 2001 Connection of IPv6 Domains
IPv4
This memo specifies an optional interim mechanism for IPv6 sites
communicate with each other over the IPv4 network without
tunnel setup, and for them to communicate with native IPv6 domains
relay routers. [STANDARDS TRACK
3055 Krishnaswamy Feb 2001 Management Information
for the PINT
This memo describes a proposed Management Information Base (MIB) for
PSTN/Internet Interworking (PINT) Services Architecture. [
TRACK
3054 Blatherwick Jan 2001 Megaco IP Phone Media
Application
This document specifies a particular application of the Megaco/H.248
Protocol for control of Internet telephones and similar appliances:
Megaco IP Phone Media Gateway. This memo provides information for
Internet community
Ginoza Informational [Page 11]
RFC 3099 Summary of 3000-3099
3053 Durand Jan 2001 IPv6 Tunnel
The motivation for the development of the tunnel broker model is to
early IPv6 adopters to hook up to an existing IPv6 network (e.g.,
6bone) and to get stable, permanent IPv6 addresses and DNS names.
concept of the tunnel broker was first presented at Orlando's IETF
December 1998. Two implementations were demonstrated during
Grenoble IPng & NGtrans interim meeting in February 1999. This
provides information for the Internet community
3052 Eder Jan 2001 Service
Architectures Issues
The purpose of this document is to explore the problems of defining
Service management framework and to examine some of the issues
still need to be resolved. This memo provides information for
Internet community
3051 Heath Jan 2001 IP Payload Compression
ITU-T V.44 Packet
This document describes a compression method based on the
compression algorithm described in International Telecommunication
(ITU-T) Recommendation V.44. This document defines the application
V.44 Packet Method to the Internet Protocol (IP) Payload
Protocol (RFC 2393). This memo provides information for the
community
3050 Lennox Jan 2001 Common Gateway Interface
This document defines a SIP CGI interface for providing SIP services
a SIP server. This memo provides information for the
community
Ginoza Informational [Page 12]
RFC 3099 Summary of 3000-3099
3049 Naugle Jan 2001 TN3270E Service Location
Session
This document discusses the implementation of Service Location
(SLP) and session balancing with a TN3270E emulator in a client
implementation with a TN3270E server. [STANDARDS TRACK
3048 Whetten Jan 2001 Reliable Multicast
Building Blocks
One-to-Many Bulk-Data
This document describes a framework for the standardization of bulk-
reliable multicast transport. This memo provides information for
Internet community
3047 Luthi Jan 2001 RTP Payload Format for ITU-
Recommendation G.722.1
This document describes the payload format for including G.722.1
generated bit streams within an RTP packet. Also included here are
necessary details for the use of G.722.1 with MIME and SDP. [
TRACK
3046 Patrick Jan 2001 DHCP Relay Agent
Newer high-speed public Internet access technologies call for a high
speed modem to have a local area network (LAN) attachment to one or
customer premise hosts. It is advantageous to use the Dynamic
Configuration Protocol (DHCP) as defined in RFC 2131 to assign
premise host IP addresses in this environment. However, a number
security and scaling problems arise with such "public" DHCP use.
document describes a new DHCP option to address these issues.
option extends the set of DHCP options as defined in RFC 2132.
[STANDARDS TRACK
3045 Meredith Jan 2001 Storing Vendor Information
the LDAP root
This document specifies two Lightweight Directory Access Protocol (LDAP
attributes, vendorName and vendorVersion that MAY be included in
root DSA-specific Entry (DSE) to advertise vendor-specific information
This memo provides information for the Internet community
Ginoza Informational [Page 13]
RFC 3099 Summary of 3000-3099
3044 Rozenfeld Jan 2001 Using The ISSN (
Serial Standard Number) as
(Uniform Resource Names
within an ISSN-URN
This document presents how the ISSN - International Standard
Number - which is a persistent number for unique identification
serials widely recognised and used in the bibliographic world, can
supported within the Uniform Resource Name (URN) framework as a
URN namespace identifier. This memo provides information for
Internet community
3043 Mealling Jan 2001 The Network Solutions
Internet Name (PIN): A
Namespace for People
This document describes a Uniform Resource Name (URN) namespace that
engineered by Network Solutions, Inc. for naming people
organizations. This memo provides information for the
community
3042 Allman Jan 2001 Enhancing TCP's Loss
Using Limited
This document proposes a new Transmission Control Protocol (TCP
mechanism that can be used to more effectively recover lost
when a connection's congestion window is small, or when a large
of segments are lost in a single transmission window. [STANDARDS TRACK
3041 Narten Jan 2001 Privacy Extensions
Stateless
Autoconfiguration in IPv
This document describes an extension to IPv6 stateless
autoconfiguration for interfaces whose interface identifier is
from an IEEE identifier. [STANDARDS TRACK
Ginoza Informational [Page 14]
RFC 3099 Summary of 3000-3099
3040 Cooper Jan 2001 Internet Web Replication
Caching
This memo specifies standard terminology and the taxonomy of
replication and caching infrastructure as deployed today. It
standard concepts, and protocols used today within this
domain. This memo provides information for the Internet community
3039 Santesson Jan 2001 Internet X.509 Public
Infrastructure
Certificates
This document forms a certificate profile for Qualified Certificates
based on RFC 2459, for use in the Internet. The goal of this
is to define a general syntax independent of local legal requirements
[STANDARDS TRACK
3038 Nagami Jan 2001 VCID Notification over
link for
This document specifies the procedures for the communication of
values between neighboring ATM-LSRs that must occur in order to
this property. [STANDARDS TRACK
3037 Thomas Jan 2001 LDP
A fundamental concept in MPLS is that two Label Switching Routers (LSRs
must agree on the meaning of the labels used to forward traffic
and through them. This common understanding is achieved by using a
of procedures, called a label distribution protocol, by which one
informs another of label bindings it has made. This document
the applicability of a set of such procedures called LDP (for
Distribution Protocol) by which LSRs distribute labels to support
forwarding along normally routed paths. This memo provides
for the Internet community
Ginoza Informational [Page 15]
RFC 3099 Summary of 3000-3099
3036 Andersson Jan 2001 LDP
A fundamental concept in MPLS is that two Label Switching Routers (LSRs
must agree on the meaning of the labels used to forward traffic
and through them. This common understanding is achieved by using a
of procedures, called a label distribution protocol, by which one
informs another of label bindings it has made. This document defines
set of such procedures called LDP (for Label Distribution Protocol)
which LSRs distribute labels to support MPLS forwarding along
routed paths. [STANDARDS TRACK
3035 Davie Jan 2001 MPLS using LDP and ATM
This document extends and clarifies the relevant portions of RFC 3031
and RFC 3036 by specifying in more detail the procedures which to
used when distributing labels to or from ATM-LSRs, when those
represent Forwarding Equivalence Classes (FECs, see RFC 3031) for
the routes are determined on a hop-by-hop basis by network layer
algorithms. [STANDARDS TRACK
3034 Conta Jan 2001 Use of Label Switching
Frame Relay
This document defines the model and generic mechanisms for
Label Switching on Frame Relay networks. [STANDARDS TRACK
3033 Suzuki Jan 2001 The Assignment of
Information Field and
Identifier in the Q.2941
Identifier and Q.2957
User-to-user Signaling for
Internet
The purpose of this document is to specify the assignment of
information field and protocol identifier in the Q.2941
Identifier and Q.2957 User-to-user Signaling for the Internet protocol
[STANDARDS TRACK
Ginoza Informational [Page 16]
RFC 3099 Summary of 3000-3099
3032 Rosen Jan 2001 MPLS Label Stack
This document specifies the encoding to be used by an LSR in order
transmit labeled packets on Point-to-Point Protocol (PPP) data links,
LAN data links, and possibly on other data links as well. This
also specifies rules and procedures for processing the various fields
the label stack encoding. [STANDARDS TRACK
3031 Rosen Jan 2001 Multiprotocol Label
This document specifies the architecture for Multiprotocol
Switching (MPLS). [STANDARDS TRACK
3030 Vaudreuil Dec 2000 SMTP Service Extensions
Transmission of Large
Binary MIME
This memo defines two extensions to the SMTP (Simple Mail
Protocol) service. [STANDARDS TRACK
3029 Adams Feb 2001 Internet X.509 Public
Infrastructure Data
and Certification
This document describes a general Data Validation and
Server (DVCS) and the protocols to be used when communicating with it
This memo defines an Experimental Protocol for the Internet community
3028 Showalter Jan 2001 Sieve: A Mail
This document describes a language for filtering e-mail messages at
of final delivery. [STANDARDS TRACK
Ginoza Informational [Page 17]
RFC 3099 Summary of 3000-3099
3027 Holdrege Jan 2001 Protocol Complications
the IP Network
The purpose of this document is to identify the protocols
applications that break with NAT enroute. The document also attempts
identify any known workarounds. This document attempts to capture
much information as possible, but is by no means a
coverage. This memo provides information for the Internet community
3026 Blane Jan 2001 Liaison to IETF/ISOC on
Working Party 1/2, of the International Telecommunication
Telecommunication Standardization Sector (ITU-T) held a meeting of
collaborators in Berlin Germany 19-26 October 2000. This liaison
WP1/2 to the IETF/ISOC conveys the understandings of the WP1/2
collaborators resulting from the discussions. This memo
information for the Internet community
3025 Dommety Feb 2001 Mobile
Vendor/Organization-
This document defines two new extensions to Mobile IP. These
will facilitate equipment vendors and organizations to make specific
of these extensions as they see fit for research or deployment purposes
[STANDARDS TRACK
3024 Montenegro Jan 2001 Reverse Tunneling for
IP,
This document proposes backwards-compatible extensions to Mobile IP
support topologically correct reverse tunnels. This document does
attempt to solve the problems posed by firewalls located between
home agent and the mobile node's care-of address. [STANDARDS TRACK
Ginoza Informational [Page 18]
RFC 3099 Summary of 3000-3099
3023 Murata Jan 2001 XML Media
This document standardizes five new media types -- text/xml
application/xml, text/xml-external-parsed-entity, application/xml
external-parsed-entity, and application/xml-dtd -- for use in
network entities that are related to the Extensible Markup
(XML). This document also standardizes a convention (using the
'+xml') for naming media types outside of these five types when
media types represent XML MIME (Multipurpose Internet Mail Extensions
entities. [STANDARDS TRACK
3022 Srisuresh Jan 2001 Traditional IP Network
Translator (Traditional NAT
The NAT operation described in this document extends address
introduced in RFC 1631 and includes a new type of network address
TCP/UDP port translation. In addition, this document corrects
Checksum adjustment algorithm published in RFC 1631 and attempts
discuss NAT operation and limitations in detail. This memo
information for the Internet community
3021 Retana Dec 2000 Using 31-Bit Prefixes on IPv
Point-to-Point
With ever-increasing pressure to conserve IP address space on
Internet, it makes sense to consider where relatively minor changes
be made to fielded practice to improve numbering efficiency. One
change, proposed by this document, is to halve the amount of
space assigned to point-to-point links (common throughout the
infrastructure) by allowing the use of 31-bit subnet masks in a
limited way. [STANDARDS TRACK
3020 Pate Dec 2000 Definitions of Managed
for Monitoring and
the UNI/NNI Multilink
Relay
This memo defines a Management Information Base (MIB) for monitoring
controlling a UNI/NNI Multilink Frame Relay Function as defined in
Relay Forum FRF.16. [STANDARDS TRACK
Ginoza Informational [Page 19]
RFC 3099 Summary of 3000-3099
3019 Haberman Jan 2001 IP Version 6
Information Base for
Multicast Listener
This document defines a portion of the Management Information Base (MIB
for use with network management protocols in Internet Protocol Version 6
internets. Specifically, this document is the MIB module that
managed objects for implementations of the Multicast Listener
Protocol [RFC2710]. [STANDARDS TRACK
3018 Bogdanov Dec 2000 Unified Memory Space
This document specifies Unified Memory Space Protocol (UMSP),
gives a capability of immediate access to memory of the remote nodes
This memo defines an Experimental Protocol for the Internet community
3017 Riegel Dec 2000 XML DTD for Roaming
Phone
This document defines the syntax as well as the semantics of
information to be included in the phone book for roaming applications
[STANDARDS TRACK
3016 Kikuchi Nov 2000 RTP Payload Format for MPEG-4
Audio/Visual
This document describes Real-Time Transport Protocol (RTP)
formats for carrying each of MPEG-4 Audio and MPEG-4 Visual
without using MPEG-4 Systems. [STANDARDS TRACK
3015 Cuervo Nov 2000 Megaco Protocol Version 1.0
This document defines the protocol used between elements of a
decomposed multimedia gateway, i.e. a Media Gateway and a Media
Controller. [STANDARDS TRACK
Ginoza Informational [Page 20]
RFC 3099 Summary of 3000-3099
3014 Kavasseri Nov 2000 Notification Log
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community.
particular, it describes managed objects used for logging Simple
Management Protocol (SNMP) Notifications. [STANDARDS TRACK
3013 Killalea Nov 2000 Recommended Internet
Provider Security Services
The purpose of this document is to express what the
community as represented by the IETF expects of Internet
Providers (ISPs) with respect to security. This document specifies
Internet Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
3012 Perkins Nov 2000 Mobile IPv4 Challenge/
In this specification, we define extensions for the Mobile IP
Advertisements and the Registration Request that allow a foreign
to use a challenge/response mechanism to authenticate the mobile node
[STANDARDS TRACK
3011 Waters Nov 2000 The IPv4 Subnet
Option for
This memo defines a new Dynamic Host Configuration Protocol (DHCP
option for selecting the subnet on which to allocate an address
[STANDARDS TRACK
3010 Shepler Dec 2000 NFS version 4
NFS (Network File System) version 4 is a distributed file
protocol which owes heritage to NFS protocol versions 2 [RFC1094] and 3
[RFC1813]. Unlike earlier versions, the NFS version 4 protocol
traditional file access while integrating support for file locking
the mount protocol. In addition, support for strong security (and
negotiation), compound operations, client caching,
internationalization have been added. Of course, attention has
applied to making NFS version 4 operate well in an Internet environment
[STANDARDS TRACK
Ginoza Informational [Page 21]
RFC 3099 Summary of 3000-3099
3009 Rosenberg Nov 2000 Registration of parityfec
The RTP (Real-time Transport Protocol) payload format for
forward error correction allows RTP participants to improve
resiliency through the use of traditional parity-based channel codes
This payload format requires four new MIME types, audio/parityfec
video/parityfec, text/parityfec and application/parityfec.
document serves as the MIME type registration for those formats
[STANDARDS TRACK
3008 Wellington Nov 2000 Domain Name System
(DNSSEC) Signing
This document proposes a revised model of Domain Name System
(DNSSEC) Signing Authority. The revised model is designed to
earlier documents and add additional restrictions to simplify the
resolution process. Specifically, this affects the authorization
keys to sign sets of records. [STANDARDS TRACK
3007 Wellington Nov 2000 Secure Domain Name
(DNS) Dynamic
This document proposes a method for performing secure Domain Name
(DNS) dynamic updates. [STANDARDS TRACK
3006 Davie Nov 2000 Integrated Services in
Presence of Compressible
This specification describes an extension to the TSpec which enables
sender of potentially compressible data to provide hints to int-
routers about the compressibility they may obtain. [STANDARDS TRACK
Ginoza Informational [Page 22]
RFC 3099 Summary of 3000-3099
3005 Harris Nov 2000 IETF Discussion List
The Internet Engineering Task Force (IETF) discussion mailing
furthers the development and specification of Internet
through discussion of technical issues, and hosts discussions of
direction, policy, meetings, and procedures. As this is the
general IETF mailing list, considerable latitude is allowed
Advertising, whether to solicit business or promote
opportunities, falls well outside the range of acceptable topics, as
discussions of a personal nature. This document specifies an
Best Current Practices for the Internet Community, and
discussion and suggestions for improvements
3004 Stump Nov 2000 The User Class Option for
This option is used by a Dynamic Host Configuration Protocol (DHCP
client to optionally identify the type or category of user
applications it represents. The information contained in this option
an opaque field that represents the user class of which the client is
member. Based on this class, a DHCP server selects the
address pool to assign an address to the client and the
configuration parameters. This option should be configurable by a user
[STANDARDS TRACK
3003 Nilsson Nov 2000 The audio/mpeg Media
The audio layers of the MPEG-1 and MPEG-2 standards are in frequent
on the internet, but there is no uniform Multipurpose Internet
Extension (MIME) type for these files. The intention of this
is to define the media type audio/mpeg to refer to this kind
contents. [STANDARDS TRACK
3002 Mitzel Dec 2000 Overview of 2000 IAB
Internetworking
This document provides an overview of a workshop held by the
Architecture Board (IAB) on wireless internetworking. This
provides information for the Internet community
Ginoza Informational [Page 23]
RFC 3099 Summary of 3000-3099
3001 Mealling Nov 2000 A URN Namespace of
This document describes a Uniform Resource Names (URN) namespace
contains Object Identifiers (OIDs). This memo provides information
the Internet community
3000 Reynolds Nov 2001 Internet Official
This memo contains a snapshot of the state of standardization
protocols used in the Internet as of October 25, 2001. It
official protocol standards and Best Current Practice RFCs; it is not
complete index to the RFC series. The latest version of this memo
designated STD 1. [STANDARDS TRACK
Security
Security issues are not discussed in this memo
Author's
Sandy
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: ginoza@isi.
Ginoza Informational [Page 24]
RFC 3099 Summary of 3000-3099
Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Ginoza Informational [Page 25]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
