📄 rfc2999.txt
字号:
2974 Handley Oct 2000 Session Announcement Protocol
This document describes version 2 of the multicast session directory
announcement protocol, Session Announcement Protocol (SAP), and the
related issues affecting security and scalability that should be taken
into account by implementors. This memo defines an Experimental
Protocol for the Internet community.
Ginoza Informational [Page 6]
RFC 2999 Summary of 2900-2999 August 2001
2973 Balay Oct 2000 IS-IS Mesh Groups
This document describes a mechanism to reduce redundant packet
transmissions for the Intermediate System to Intermediate System (IS-IS)
Routing protocol, as described in ISO 10589. This memo provides
information for the Internet community.
2972 Popp Oct 2000 Context and Goals for Common
Name Resolution
This document establishes the context and goals for a Common Name
Resolution Protocol. This memo provides information for the Internet
community.
2971 Showalter Oct 2000 IMAP4 ID extension
This document describes an ID extension which will enable Internet
Message Access Protocol - Version 4rev1 (IMAP4rev1) to advertise what
program a client or server uses to provide service. The ID extension
allows the server and client to exchange identification information on
their implementation in order to make bug reports and usage statistics
more complete. [STANDARDS TRACK]
2970 Daigle Oct 2000 Architecture for Integrated
Directory Services - Result
from TISDAG
Drawing from experiences with the TISDAG (Technical Infrastructure for
Swedish Directory Access Gateways) project, this document outlines an
approach to providing the necessary infrastructure for integrating such
widely-scattered servers into a single service, rather than attempting
to mandate a single protocol and schema set for all participating
servers to use. This memo provides information for the Internet
community.
Ginoza Informational [Page 7]
RFC 2999 Summary of 2900-2999 August 2001
2969 Eklof Oct 2000 Wide Area Directory Deployment
- Experiences from TISDAG
This document catalogues some of the experiences gained in developing
the necessary infrastructure for a national (i.e., multi-organizational)
directory service and pilot deployment of the service in an environment
with off-the-shelf directory service products. This memo provides
information for the Internet community.
2968 Daigle Oct 2000 Mesh of Multiple DAG servers -
Results from TISDAG
This document defines the basic principle for establishing a mesh, that
interoperating services should exchange index objects, according to the
architecture of the mesh (e.g., hierarchical, or graph-like, preferably
without loops!). The Common Indexing Protocol (CIP) is designed to
facilitate the creation not only of query referral indexes, but also of
meshes of (loosely) affiliated referral indexes. The purpose of such a
mesh of servers is to implement some kind of distributed sharing of
indexing and/or searching tasks across different servers. So far, the
TISDAG (Technical Infrastructure for Swedish Directory Access Gateways)
project has focused on creating a single referral index; the obvious
next step is to integrate that into a larger set of interoperating
services. This memo provides information for the Internet community.
2967 Daigle Oct 2000 TISDAG - Technical
Infrastructure for Swedish
Directory Access Gateways
The overarching goal of this project is to develop the necessary
technical infrastructure to provide a single-access-point service for
searching for whitepages information on Swedish Internet users. This
memo provides information for the Internet community.
2966 Li Oct 2000 Domain-wide Prefix
Distribution with Two-Level
IS-IS
This document describes extensions to the Intermediate System to
Intermediate System (IS-IS) protocol to support optimal routing within a
two-level domain. This memo provides information for the Internet
community.
Ginoza Informational [Page 8]
RFC 2999 Summary of 2900-2999 August 2001
2965 Kristol Oct 2000 HTTP State Management
Mechanism
This document specifies a way to create a stateful session with
Hypertext Transfer Protocol (HTTP) requests and responses. [STANDARDS
TRACK]
2964 Moore Oct 2000 Use of HTTP State Management
This memo identifies specific uses of Hypertext Transfer Protocol (HTTP)
State Management protocol which are either (a) not recommended by the
IETF, or (b) believed to be harmful, and discouraged. This memo also
details additional privacy considerations which are not covered by the
HTTP State Management protocol specification. This document specifies
an Internet Best Current Practices for the Internet Community, and
requests discussion and suggestions for improvements.
2963 Bonaventure Oct 2000 A Rate Adaptive Shaper for
Differentiated Services
This memo describes several Rate Adaptive Shapers (RAS) that can be used
in combination with the single rate Three Color Markers (srTCM) and the
two rate Three Color Marker (trTCM) described in RFC2697 and RFC2698,
respectively. This memo provides information for the Internet
community.
2962 Raz Oct 2000 An SNMP Application Level
Gateway for Payload Address
Translation
This document describes the ALG (Application Level Gateway) for the SNMP
(Simple Network Management Protocol) by which IP (Internet Protocol)
addresses in the payload of SNMP packets are statically mapped from one
group to another. This memo provides information for the Internet
community.
Ginoza Informational [Page 9]
RFC 2999 Summary of 2900-2999 August 2001
2961 Berger Apr 2001 RSVP Refresh Overhead
Reduction Extensions
This document describes a number of mechanisms that can be used to
reduce processing overhead requirements of refresh messages, eliminate
the state synchronization latency incurred when an RSVP (Resource
ReserVation Protocol) message is lost and, when desired, refreshing
state without the transmission of whole refresh messages. [STANDARDS
TRACK]
2960 Stewart Oct 2000 Stream Control Transmission
Protocol
This document describes the Stream Control Transmission Protocol (SCTP).
[STANDARDS TRACK]
2959 Baugher Oct 2000 Real-Time Transport Protocol
Management Information Base
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
[STANDARDS TRACK]
2958 Daigle Oct 2000 The application/whoispp-
response Content-type
The intention of this document, in conjunction with RFC 2957, is to
enable MIME-enabled mail software, and other systems using Internet
media types, to carry out Whois++ transactions. This memo provides
information for the Internet community.
2957 Daigle Oct 2000 The application/whoispp-query
Content-Type
The intention of this document, in conjunction with RFC 2958, is to
enable MIME-enabled mail software, and other systems using Internet
media types, to carry out Whois++ transactions. This memo provides
information for the Internet community.
Ginoza Informational [Page 10]
RFC 2999 Summary of 2900-2999 August 2001
2956 Kaat Oct 2000 Overview of 1999 IAB Network
Layer Workshop
This document is an overview of a workshop held by the Internet
Architecture Board (IAB) on the Internet Network Layer architecture
hosted by SURFnet in Utrecht, the Netherlands on 7-9 July 1999. The
goal of the workshop was to understand the state of the network layer
and its impact on continued growth and usage of the Internet. This memo
provides information for the Internet community.
2955 Rehbehn Oct 2000 Definitions of Managed Objects
for Monitoring and Controlling
the Frame Relay/ATM PVC Service
Interworking Function
This memo defines a Management Information Base (MIB) to configure,
monitor, and control a service interworking function (IWF) for Permanent
Virtual Connections (PVC) between Frame Relay and Asynchronous Transfer
Mode (ATM) technologies. [STANDARDS TRACK]
2954 Rehbehn Oct 2000 Definitions of Managed Objects
for Frame Relay Service
This memo defines an extension to the Management Information Base (MIB)
for use with network management protocols in Transmission Control
Protocol/Internet Protocol-based (TCP/IP) internets. In particular, it
defines objects for managing the frame relay service. [STANDARDS TRACK]
2953 Ts'o Sep 2000 Telnet Encryption: DES 64 bit
Output Feedback
This document specifies how to use the data encryption standard (DES)
encryption algorithm in output feedback mode with the telnet encryption
option. This memo provides information for the Internet community.
2952 Ts'o Sep 2000 Telnet Encryption: DES 64 bit
Cipher Feedback
This document specifies how to use the DES encryption algorithm in
cipher feedback mode with the telnet encryption option. This memo
provides information for the Internet community.
Ginoza Informational [Page 11]
RFC 2999 Summary of 2900-2999 August 2001
2951 Housley Sep 2000 TELNET Authentication Using
KEA and SKIPJACK
This document defines a method to authenticate TELNET using the Key
Exchange Algorithm (KEA), and encryption of the TELNET stream using
SKIPJACK. This memo provides information for the Internet community.
2950 Altman Sep 2000 Telnet Encryption: CAST-128 64
bit Cipher Feedback
This document specifies how to use the CAST-128 encryption algorithm in
cipher feedback mode with the telnet encryption option. Two key sizes
are defined: 40 bit and 128 bit. [STANDARDS TRACK]
2949 Altman Sep 2000 Telnet Encryption: CAST-128 64
bit Output Feedback
This document specifies how to use the CAST-128 encryption algorithm in
output feedback mode with the telnet encryption option. Two key sizes
are defined: 40 bit and 128 bit. [STANDARDS TRACK]
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -