pozycje od 1 do 25 z 100, strona 1 z 4
- RFC2599 - Request for Comments Summary RFC Numbers 2500-2599
- RFC2598 - An Expedited Forwarding PHB The definition of PHBs (per-hop forwarding behaviors) is a critical part of the work of the Diffserv Working Group. This document describes a PHB called Expedited Forwarding. [STANDARDS-TRACK]
- RFC2597 - Assured Forwarding PHB Group This document defines a general use Differentiated Services (DS) Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). [STANDARDS-TRACK]
- RFC2596 - Use of Language Codes in LDAP This document describes how language codes are carried in LDAP and are to be interpreted by LDAP servers. [STANDARDS-TRACK]
- RFC2595 - Using TLS with IMAP, POP3 and ACAP Recognizing that such sites will desire simple password authentication in combination with TLS encryption, this specification defines the PLAIN SASL mechanism for use with protocols which lack a simple password authentication command such as ACAP and SMTP. [STANDARDS-TRACK]
- RFC2594 - Definitions of Managed Objects for WWW Services This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet Community. In particular it describes a set of objects for managing World Wide Web (WWW) services. [STANDARDS-TRACK]
- RFC2593 - Script MIB Extensibility Protocol Version 1.0 The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independent Script MIB implementations. This memo defines an Experimental Protocol for the Internet community.
- RFC2592 - Definitions of Managed Objects for the Delegation of Management Script This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers. [STANDARDS-TRACK]
- RFC2591 - Definitions of Managed Objects for Scheduling Management Operations This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
- RFC2590 - Transmission of IPv6 Packets over Frame Relay Networks Specification This memo describes mechanisms for the transmission of IPv6 packets over Frame Relay networks. [STANDARDS-TRACK]
- RFC2589 - Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services This document defines the requirements for dynamic directory services and specifies the format of request and response extended operations for supporting client-server interoperation in a dynamic directories environment. [STANDARDS-TRACK]
- RFC2588 - IP Multicast and Firewalls In this document, we discuss the issues surrounding the traversal of IP multicast traffic across a firewall, and describe possible ways in which a firewall can implement and control this traversal. We also explain why some firewall mechanisms - such as SOCKS - that were designed specifically for unicast traffic, are less appropriate for multicast. This memo provides information for the Internet community.
- RFC2587 - Internet X.509 Public Key Infrastructure LDAPv2 Schema The schema defined in this document is a minimal schema to support PKIX in an LDAPv2 environment, as defined in RFC 2559. Only PKIX-specific components are specified here. [STANDARDS-TRACK]
- RFC2586 - The Audio/L16 MIME content type This document defines the audio/L16 MIME type, a reasonable quality audio format for use in Internet applications. This memo provides information for the Internet community.
- RFC2585 - Internet X.509 Public Key Infrastructure Operational Protocols: FTP and HTTP The protocol conventions described in this document satisfy some of the operational requirements of the Internet Public Key Infrastructure (PKI). This document specifies the conventions for using the File Transfer Protocol (FTP) and the Hypertext Transfer Protocol (HTTP) to obtain certificates and certificate revocation lists (CRLs) from PKI repositories. [STANDARDS-TRACK]
- RFC2584 - Definitions of Managed Objects for APPN/HPR in IP Networks This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling HPR (High Performance Routing) network devices which have the capability to communicate in IP (Internet Protocol) networks. [STANDARDS-TRACK]
- RFC2583 - Guidelines for Next Hop Client (NHC) Developers This document provides guidelines for developers of the Next Hop Resolution Protocol Clients (NHC). The intent is to define the interaction between the NHC code and the TCP/IP protocol stack of the local host operating system. This memo provides information for the Internet community.
- RFC2582 - The NewReno Modification to TCP's Fast Recovery Algorithm This document describes a specific algorithm for responding to partial acknowledgments, referred to as NewReno. This memo defines an Experimental Protocol for the Internet community.
- RFC2581 - TCP Congestion Control This document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. [STANDARDS-TRACK]
- RFC2580 - Conformance Statements for SMIv2 Collections of related objects are defined in MIB modules. It may be useful to define the acceptable lower-bounds of implementation, along with the actual level of implementation achieved. It is the purpose of this document to define the notation used for these purposes. [STANDARDS-TRACK]
- RFC2579 - Textual Conventions for SMIv2 It is the purpose of this document to define the initial set of textual conventions available to all MIB modules. [STANDARDS-TRACK]
- RFC2578 - Structure of Management Information Version 2 (SMIv2) It is the purpose of this document, the Structure of Management Information Version 2 (SMIv2), to define that adapted subset, and to assign a set of associated administrative values. [STANDARDS-TRACK]
- RFC2577 - FTP Security Considerations This document provides suggestions for system administrators and those implementing FTP servers that will decrease the security problems associated with FTP. This memo provides information for the Internet community.
- RFC2576 - Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework The purpose of this document is to describe coexistence between version 3 of the Internet-standard Network Management Framework, (SNMPv3), version 2 of the Internet-standard Network Management Framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1). [STANDARDS TRACK]
- RFC2575 - View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) This document describes the View-based Access Control Model for use in the SNMP architecture (RFC2571). It defines the Elements of Procedure for controlling access to management information. This document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model. [STANDARDS-TRACK]
pozycje od 1 do 25 z 100, strona 1 z 4