Bookmark and Share

pozycje od 1 do 25 z 100,  strona 1 z 4
 1  2  3  4  > 
  • RFC2399 - Request for Comments Summary
  • RFC2398 - Some Testing Tools for TCP Implementors This document lists only tools which can evaluate one or more TCP implementations, or which can privde some specific results which describe or evaluate the TCP being tested. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2397 - The "data" URL scheme A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]
  • RFC2396 - Uniform Resource Identifiers (URI): Generic Syntax This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK]
  • RFC2395 - IP Payload Compression Using LZS This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2394 - IP Payload Compression Using DEFLATE This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2393 - IP Payload Compression Protocol (IPComp) This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK]
  • RFC2392 - Content-ID and Message-ID Uniform Resource Locators The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS- TRACK]
  • RFC2391 - Load Sharing using IP Network Address Translation (LSNAT) In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2390 - Inverse Address Resolution Protocol This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
  • RFC2389 - Feature negotiation mechanism for the File Transfer Protocol This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK]
  • RFC2388 - Returning Values from Forms: multipart/form-data This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. [STANDARDS-TRACK]
  • RFC2387 - The MIME Multipart/Related Content-type This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
  • RFC2386 - A Framework for QoS-based Routing in the Internet This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2385 - Protection of BGP Sessions via the TCP MD5 Signature Option This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK]
  • RFC2384 - POP URL Scheme This memo defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK]
  • RFC2383 - ST2+ over ATM Protocol Specification - UNI 3.1 Version This document specifies an ATM-based protocol for communication between ST2+ agents. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2382 - A Framework for Integrated Services and RSVP over ATM This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2381 - Interoperation of Controlled-Load Service and Guaranteed Service with ATM This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK]
  • RFC2380 - RSVP over ATM Implementation Requirements This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK]
  • RFC2379 - RSVP over ATM Implementation Guidelines This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
  • RFC2378 - The CCSO Nameserver (Ph) Architecture The Ph Nameserver from the Computing and Communications Services Office (CCSO), University of Illinois at Urbana-Champaign has for some time now been used by several organizations as their choice of publicly available database for information about people as well as other things. This document provides a formal definition of the client-server protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2377 - Naming Plan for Internet Directory-Enabled Applications Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2376 - XML Media Types This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
  • RFC2375 - IPv6 Multicast Address Assignments This document defines the initial assignment of IPv6 multicast addresses. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
pozycje od 1 do 25 z 100,  strona 1 z 4
 1  2  3  4  >