Bookmark and Share

pozycje od 1 do 25 z 100,  strona 1 z 4
 1  2  3  4  > 
  • RFC2699 - Request for Comments Summary RFC Numbers 2600-2699
  • RFC2698 - A Two Rate Three Color Marker This document defines a Two Rate Three Color Marker (trTCM), which can be used as a component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
  • RFC2697 - A Single Rate Three Color Marker This document defines a Single Rate Three Color Marker (srTCM), which can be used as component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
  • RFC2696 - LDAP Control Extension for Simple Paged Results Manipulation This document describes an LDAPv3 control extension for simple paging of search results. This memo provides information for the Internet community.
  • RFC2695 - Authentication Mechanisms for ONC RPC This document describes two authentication mechanisms created by Sun Microsystems that are commonly used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocol. This memo provides information for the Internet community.
  • RFC2694 - DNS extensions to Network Address Translators (DNS_ALG) This document identifies the need for DNS extensions to NATs and outlines how a DNS Application Level Gateway (DNS_ALG) can meet the need. This memo provides information for the Internet community.
  • RFC2693 - SPKI Certificate Theory This document gives the theory behind SPKI certificates and ACLs without going into technical detail about those structures or their uses. This memo defines an Experimental Protocol for the Internet community.
  • RFC2692 - SPKI Requirements The SPKI Working Group first established a list of things one might want to do with certificates (attached at the end of this document), and then summarized that list of desires into requirements. This document presents that summary of requirements. This memo defines an Experimental Protocol for the Internet community.
  • RFC2691 - A Memorandum of Understanding for an ICANN Protocol Support Organization This is the text of the Memorandum of Understanding (MoU) that was signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 in Oslo. This MoU creates the Protocol Support Organization (PSO) within the Internet Corporation for Assigned Names and Numbers (ICANN). This memo provides information for the Internet community.
  • RFC2690 - A Proposal for an MOU-Based ICANN Protocol Support Organization This is a copy of the proposal for an MOU-based Protocol Supporting Organization that was submitted to ICANN on April 23, 1999. This memo provides information for the Internet community.
  • RFC2689 - Providing Integrated Services over Low-bitrate Links This document describes an architecture for providing integrated services over low-bitrate links, such as modem lines, ISDN B-channels, and sub-T1 links. This memo provides information for the Internet community.
  • RFC2688 - Integrated Services Mappings for Low Speed Networks This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK]
  • RFC2687 - PPP in a Real-time Oriented HDLC-like Framing This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS- TRACK]
  • RFC2686 - The Multi-Class Extension to Multi-Link PPP This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
  • RFC2685 - Virtual Private Networks Identifier This document proposes a format for a globally unique VPN identifier. [STANDARDS-TRACK]
  • RFC2684 - Multiprotocol Encapsulation over ATM Adaptation Layer 5 This memo replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. [STANDARDS-TRACK]
  • RFC2683 - IMAP4 Implementation Recommendations The IMAP4 specification describes a rich protocol for use in building clients and servers for storage, retrieval, and manipulation of electronic mail. Because the protocol is so rich and has so many implementation choices, there are often trade-offs that must be made and issues that must be considered when designing such clients and servers. This document attempts to outline these issues and to make recommendations in order to make the end products as interoperable as possible. This memo provides information for the Internet community.
  • RFC2682 - Performance Issues in VC-Merge Capable ATM LSRs This document investigates the impact of VC merging on the additional buffer required for the reassembly buffers and other buffers. This memo provides information for the Internet community.
  • RFC2681 - A Round-trip Delay Metric for IPPM This memo defines a metric for round-trip delay of packets across Internet paths. [STANDARDS-TRACK]
  • RFC2680 - A One-way Packet Loss Metric for IPPM This memo defines a metric for one-way packet loss across Internet paths. [STANDARDS-TRACK]
  • RFC2679 - A One-way Delay Metric for IPPM This memo defines a metric for one-way delay of packets across Internet paths. [STANDARDS-TRACK]
  • RFC2678 - IPPM Metrics for Measuring Connectivity This memo defines a series of metrics for connectivity between a pair of Internet hosts. [STANDARDS-TRACK]
  • RFC2677 - Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP) This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
  • RFC2676 - QoS Routing Mechanisms and OSPF Extensions This memo describes extensions to the OSPF protocol to support QoS routes. The focus of this document is on the algorithms used to compute QoS routes and on the necessary modifications to OSPF to support this function, e.g., the information needed, its format, how it is distributed, and how it is used by the QoS path selection process. This memo defines an Experimental Protocol for the Internet community.
  • RFC2675 - IPv6 Jumbograms This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. [STANDARDS-TRACK]
pozycje od 1 do 25 z 100,  strona 1 z 4
 1  2  3  4  >