pozycje od 1 do 25 z 100, strona 1 z 4
- RFC2199 - Request for Comments Summary RFC Numbers 2100-2199
- RFC2198 - RTP Payload for Redundant Audio Data This document describes a payload format for use with the real-time transport protocol (RTP), version 2, for encoding redundant audio data. [STANDARDS-TRACK]
- RFC2197 - SMTP Service Extension for Command Pipelining This memo defines an extension to the SMTP service whereby a server can indicate the extent of its ability to accept multiple commands in a single TCP send operation. [STANDARDS-TRACK]
- RFC2196 - Site Security Handbook This handbook is a guide to developing computer security policies and procedures for sites that have systems on the Internet. The purpose of this handbook is to provide practical guidance to administrators trying to secure their information and services. The subjects covered include policy content and formation, a broad range of technical system and network security topics, and security incident response. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
- RFC2195 - IMAP/POP AUTHorize Extension for Simple Challenge/Response This specification provides a simple challenge-response authentication protocol that is suitable for use with IMAP4. [STANDARDS TRACK]
- RFC2194 - Review of Roaming Implementations This document reviews the design and functionality of existing roaming implementations. Examples of cases where roaming capability might be required include ISP "confederations" and ISP-provided corporate network access support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2193 - IMAP4 Mailbox Referrals Mailbox referrals allow clients to seamlessly access mailboxes that are distributed across several IMAP4 servers. [STANDARDS-TRACK]
- RFC2192 - IMAP URL Scheme This document defines a URL scheme for referencing objects on an IMAP server. [STANDARDS-TRACK]
- RFC2191 - VENUS - Very Extensive Non-Unicast Service This document focuses exclusively on the problems associated with extending the MARS model to cover multiple clusters or clusters spanning more than one subnet. It describes a hypothetical solution, dubbed "Very Extensive NonUnicast Service" (VENUS), and shows how complex such a service would be. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2190 - RTP Payload Format for H.263 Video Streams This document specifies the payload format for encapsulating an H.263 bitstream in the Real-Time Transport Protocol (RTP). [STANDARDS TRACK]
- RFC2189 - Core Based Trees (CBT version 2) Multicast Routing -- Protocol Specification -- This document describes the Core Based Tree (CBT version 2) network layer multicast routing protocol. CBT builds a shared multicast distribution tree per group, and is suited to inter- and intra-domain multicast routing. This memo defines an Experimental Protocol for the Internet community.
- RFC2188 - AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1.2 This document specifies the service model, the notation and protocol for Efficient Short Remote Operations (ESRO). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
- RFC2187 - Application of Internet Cache Protocol (ICP), version 2 This document describes the application of ICPv2 (Internet Cache Protocol version 2, RFC2186) to Web caching. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2186 - Internet Cache Protocol (ICP), version 2 This document describes version 2 of the Internet Cache Protocol (ICPv2) as currently implemented in two World-Wide Web proxy cache packages. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2185 - Routing Aspects of IPv6 Transition This document gives an overview of the routing aspects of the IPv6 transition. It is based on the protocols defined in the document "Transition Mechanisms for IPv6 Hosts and Routers." Readers should be familiar with the transition mechanisms before reading this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2184 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations This memo defines extensions to the RFC 2045 media type and RFC 2183 disposition parameter value mechanisms. [STANDARDS-TRACK]
- RFC2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field This memo provides a mechanism whereby messages conforming to the MIME specifications [RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049] can convey presentational information. It specifies the "Content- Disposition" header field, which is optional and valid for any MIME entity ("message" or "body part"). [STANDARDS-TRACK]
- RFC2182 - Selection and Operation of Secondary DNS Servers This document discusses the selection of secondary servers for DNS zones.The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2181 - Clarifications to the DNS Specification This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS TRACK]
- RFC2180 - IMAP4 Multi-Accessed Mailbox Practice The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2179 - Network Security For Trade Shows This document is designed to assist vendors and other participants in trade shows, such as Networld+Interop, in designing effective protection against network and system attacks by unauthorized individuals. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2178 - OSPF Version 2 This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS TRACK]
- RFC2177 - IMAP4 IDLE command This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. [STANDARDS-TRACK]
- RFC2176 - IPv4 over MAPOS Version 1 This memo documents a mechanism for supporting Version 4 of the Internet Protocol (IPv4) on Version 1 of the Multiple Access Protocol over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
- RFC2175 - MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing This memo documents MAPOS 16, a multiple access protocol for transmission of network-protocol datagrams, encapsulated in HDLC frames with 16 bit addressing, over SONET/SDH. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
pozycje od 1 do 25 z 100, strona 1 z 4