RFC19331996-04-01
Transition Mechanisms for IPv6 Hosts and Routers
Transition Mechanisms for IPv6 Hosts and Routers
This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. [STANDARDS-TRACK]
IETF · RFC
Опубликованные RFC, связи обновления и замены, официальные статусы и русские переводы.
Реестр · 9 842 документов
RFC19321996-04-01
IP over ATM: A Framework Document
IP over ATM: A Framework Document
It is hoped that this document, in classifying ATM approaches and issues will help to focus the IP over ATM working group's direction.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19311996-04-01
Dynamic RARP Extensions for Automatic Network Address Acquisition
Dynamic RARP Extensions for Automatic Network Address Acquisition
This memo describes extensions to the Reverse Address Resolution Protocol (RARP [2]) and called Dynamic RARP (DRARP, pronounced D-RARP). This memo provides information for the Internet community. This memo does not define an Internet standard of any kind.
RFC19301996-03-01
Guidelines for creation, selection, and registration of an Autonomous System (AS)
Guidelines for creation, selection, and registration of an Autonomous System (AS)
This memo discusses when it is appropriate to register and utilize an Autonomous System (AS), and lists criteria for such. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC19291996-03-01
Username/Password Authentication for SOCKS V5
Username/Password Authentication for SOCKS V5
The protocol specification for SOCKS Version 5 specifies a generalized framework for the use of arbitrary authentication protocols in the initial socks connection setup. This document describes one of those protocols, as it fits into the SOCKS Version 5 authentication "subnegotiation". [STANDARDS-TRACK]
RFC19281996-03-01
SOCKS Protocol Version 5
SOCKS Protocol Version 5
This memo describes a protocol that is an evolution of the previous version of the protocol, version 4 [1]. This new protocol stems from active discussions and prototype implementations. [STANDARDS-TRACK]
RFC19271996-04-01
Suggested Additional MIME Types for Associating Documents
Suggested Additional MIME Types for Associating Documents
Seven new types of MIME types are suggested in this document. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19261996-04-01
An Experimental Encapsulation of IP Datagrams on Top of ATM
An Experimental Encapsulation of IP Datagrams on Top of ATM
This RFC describes a method of encapsulating IP datagrams on top of Acoustical Transmission Media (ATM). This is a non-recommended standard. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19251996-04-01
The Twelve Networking Truths
The Twelve Networking Truths
This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19241996-04-01
A Compact Representation of IPv6 Addresses
A Compact Representation of IPv6 Addresses
This document specifies a more compact representation of IPv6 addresses, which permits encoding in a mere 20 bytes. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19231996-03-01
RIPv1 Applicability Statement for Historic Status
RIPv1 Applicability Statement for Historic Status
RIP Version 1 [RFC-1058] has been declared an historic document. This Applicability statement provides the supporting motivation for that declaration. The primary reason, as described below, is the Classful nature of RIPv1. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19221996-03-01
Chinese Character Encoding for Internet Messages
Chinese Character Encoding for Internet Messages
This memo describes methods of transporting Chinese characters in Internet services which transport text, such as electronic mail [RFC-822], network news [RFC-1036], telnet [RFC-854] and the World Wide Web [RFC-1866]. This memo provides information for the Internet community. It does not specify an Internet standard.
RFC19211996-03-01
TNVIP Protocol
TNVIP Protocol
The goal of this document specifies a Telnet profile to support VIP terminal emulation allowing the access to the BULL hosts applications through a TCP/IP network. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19201996-03-01
Internet Official Protocol Standards
Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). [STANDARDS-TRACK]
RFC19191996-03-01
Classical versus Transparent IP Proxies
Classical versus Transparent IP Proxies
This document explains "classical" and "transparent" proxy techniques and attempts to provide rules to help determine when each proxy system may be used without causing problems. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19181996-02-01
Выделение адресов для частных интернет-сетей
Address Allocation for Private Internets
RFC 1918 описывает выделение адресов IPv4 для частных интернет-сетей и резервирует для этой цели блоки 10/8, 172.16/12 и 192.168/16. Частные адреса уникальны только внутри предприятия либо согласованной группы предприятий и не предназначены для межпредприятийской IP-маршрутизации. Документ различает внутренние узлы, которым не нужна внешняя IP-связность, и публичные узлы, которым требуются глобаль…
Читать русский перевод →RFC19171996-02-01
Обращение к интернет-сообществу с призывом вернуть неиспользуемые IP-сети (префиксы) в IANA
An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANA
RFC 1917 призывает организации и провайдеров возвращать неиспользуемое адресное пространство IPv4 в IANA либо любой из делегированных реестров для повторного распределения. Документ связывает эффективное распределение адресов и сохранение иерархической агрегации CIDR с ограничением роста глобальных таблиц маршрутизации. Для сетей, которые никогда не потребуется подключать к Global Internet либо ко…
Читать русский перевод →RFC19161996-02-01
Enterprise Renumbering: Experience and Information Solicitation
Enterprise Renumbering: Experience and Information Solicitation
Because of the urgent need for, and substantial difficulty in, renumbering IP networks, the PIER working group is compiling a series of documents to assist sites in their renumbering efforts. The intent of these documents is to provide both educational and practical information to the Internet community. This memo provides information for the Internet community. This memo does not specify an Inter…
RFC19151996-02-01
Исключение для протокола управления соединением PPP и протокола управления шифрованием PPP
Variance for The PPP Compression Control Protocol and The PPP Encryption Control Protocol
RFC 1915 устанавливает исключение из процедур RFC 1602, позволяющее IESG продвигать исходные CCP и ECP по стандартному треку без выполнения предусмотренных RFC 1602 условий лицензирования проприетарной технологии. Исключение основано на заявлении Motorola о готовности предоставлять лицензии на патенты США 5,245,614 и 5,130,993 любой стороне на разумных условиях, доказуемо свободных от несправедлив…
Читать русский перевод →RFC19141996-02-01
How to Interact with a Whois++ Mesh
How to Interact with a Whois++ Mesh
In the Whois++ architecture [Deutsch94],[Weider94], mesh traversal is done by the client, since each server 'refers' the client to the next appropriate server(s). [STANDARDS-TRACK]
RFC19131996-02-01
Architecture of the Whois++ Index Service
Architecture of the Whois++ Index Service
The authors describe an architecture for indexing in distributed databases, and apply this to the WHOIS++ protocol. [STANDARDS-TRACK]
RFC19121996-02-01
Common DNS Operational and Configuration Errors
Common DNS Operational and Configuration Errors
This memo describes errors often found in both the operation of Domain Name System (DNS) servers, and in the data that these DNS servers contain. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
RFC19111996-02-01
Voice Profile for Internet Mail
Voice Profile for Internet Mail
The following document is a profile of the Internet standard MIME and ESMTP protocols for use as a digital voice networking protocol. This memo defines an Experimental Protocol for the Internet community.
RFC19101996-02-01
User-based Security Model for SNMPv2
User-based Security Model for SNMPv2
In this administrative framework, a security model defines the mechanisms used to achieve an administratively-defined level of security for protocol interactions. Although many such security models might be defined, it is the purpose of this document, User-based Security Model for SNMPv2, to define the first, and, as of this writing, only, security model for this administrative framework. This mem…
RFC19091996-02-01
An Administrative Infrastructure for SNMPv2
An Administrative Infrastructure for SNMPv2
It is the purpose of this document, An Administrative Infrastructure for SNMPv2, to define an administrative framework which realizes effective management in a variety of configurations and environments. This memo defines an Experimental Protocol for the Internet community.
RFC19081996-01-01
Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework
Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework
The purpose of this document is to describe coexistence between version 2 of the Internet-standard Network Management Framework [1-6], termed the SNMP version 2 framework (SNMPv2), and the original Internet- standard Network Management Framework (SNMPv1). [STANDARDS-TRACK]
RFC19071996-01-01
Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define managed objects which describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK]
RFC19061996-01-01
Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document to define how the SNMPv2 maps onto an initial set of transport domains. [STANDARDS-TRACK]
RFC19051996-01-01
Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)
Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)
It is the purpose of this document, Protocol Operations for SNMPv2, to define the operations of the protocol with respect to the sending and receiving of the PDUs. [STANDARDS-TRACK]
RFC19041996-01-01
Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)
Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)
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]