IETF · RFC

Common Authentication Technology Overview

Common Authentication Technology Overview

This memo provides information for the Internet community. It does not specify an Internet standard.

The Kerberos Network Authentication Service (V5)

The Kerberos Network Authentication Service (V5)

This document gives an overview and specification of Version 5 of the protocol for the Kerberos network authentication system. [STANDARDS-TRACK]

Generic Security Service API : C-bindings

Generic Security Service API : C-bindings

This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents. [STANDARDS-TRACK]

Generic Security Service Application Program Interface

Generic Security Service Application Program Interface

This Generic Security Service Application Program Interface (GSS-API) definition provides security services to callers in a generic fashion, supportable with a range of underlying mechanisms and technologies and hence allowing source-level portability of applications to different environments. [STANDARDS-TRACK]

DASS - Distributed Authentication Security Service

DASS - Distributed Authentication Security Service

The goal of DASS is to provide authentication services in a distributed environment which are both more secure and easier to use than existing mechanisms. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.

A Tutorial on Gatewaying between X.400 and Internet Mail

A Tutorial on Gatewaying between X.400 and Internet Mail

This tutorial was produced especially to help new gateway managers find their way into the complicated subject of mail gatewaying according to RFC 1327. This memo provides information for the Internet community. It does not specify an Internet standard.

Encoding Header Field for Internet Messages

Encoding Header Field for Internet Messages

This document expands upon the elective experimental Encoding header field which permits the mailing of multi-part, multi-structured messages. It replaces RFC 1154. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.

Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing

Appletalk Update-Based Routing Protocol: Enhanced Appletalk Routing

This document provides detailed information about the AppleTalk Update- based Routing Protocol (AURP) and wide area routing. AURP provides wide area routing enhancements to the AppleTalk routing protocols and is fully compatible with AppleTalk Phase 2. This memo provides information for the Internet community. It does not specify an Internet standard.

Algorithms for Automating Administration in SNMPv2 Managers

Algorithms for Automating Administration in SNMPv2 Managers

When a user invokes an SNMPv2 management application, it may be desirable for the user to specify the minimum amount of information necessary to establish and maintain SNMPv2 communications. This memo suggests an approach to achieve this goal. This memo provides information for the Internet community. It does not specify an Internet standard.

X.400 Use of Extended Character Sets

X.400 Use of Extended Character Sets

This RFC defines a suggested method of using "GeneralText" in order to harmonize as much as possible the usage of this body part. [STANDARDS-TRACK]

OS/2 User Group

OS/2 User Group

Memo soliciting reactions to the proposal of a OS/2 User Group. This memo provides information for the Internet community. This memo does not specify an IAB standard of any kind.

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 Activities Board (IAB). [STANDARDS-TRACK]

Summary of 1400-1499

Summary of 1400-1499

On the Naming and Binding of Network Destinations

On the Naming and Binding of Network Destinations

This brief paper offers a perspective on the subject of names of destinations in data communication networks. It suggests two ideas: First, it is helpful to distinguish among four different kinds of objects that may be named as the destination of a packet in a network. Second, the operating system concept of binding is a useful way to describe the relations among the four kinds of objects. This me…

BOOTP Vendor Information Extensions

BOOTP Vendor Information Extensions

This RFC is a slight revision and extension of RFC-1048 by Philip Prindeville, who should be credited with the original work in this memo. This memo is a status report on the vendor information extensions used in the Bootstrap Protocol (BOOTP).

Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages

Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messages

This document describes how RFC-1328 must be modified in order to provide adequate support for the scenarios: It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT obsoleted. [STANDARDS-TRACK]

Mapping between X.400 and RFC-822 Message Bodies

Mapping between X.400 and RFC-822 Message Bodies

Since the introduction of X.400(84), there has been work ongoing for defining mappings between MHS and RFC-822. The most recent work in this area is RFC-1327 [3], which focuses primarily on translation of envelope and headers. This document is complimentary to RFC-1327 as it focuses on translation of the message body. [STANDARDS-TRACK]

Equivalences between 1988 X.400 and RFC-822 Message Bodies

Equivalences between 1988 X.400 and RFC-822 Message Bodies

This document describes the content of the "IANA MHS/MIME Equivalence table", and defines the initial configuration of this table. Mappings for new MIME content-types and/or X.400 body part types should be registered with the IANA to minimize redundancy and promote interoperability. [STANDARDS-TRACK]

Definitions of Managed Objects for Bridges

Definitions of Managed Objects for Bridges

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular it defines objects for managing MAC bridges based on the IEEE 802.1D-1990 standard between Local Area Network (LAN) segments. [STANDARDS-TRACK]

An Access Control Protocol, Sometimes Called TACACS

An Access Control Protocol, Sometimes Called TACACS

This RFC documents the extended TACACS protocol use by the Cisco Systems terminal servers. This same protocol is used by the University of Minnesota's distributed authentication system. This memo provides information for the Internet community. It does not specify an Internet standard.

A Survey of Advanced Usages of X.500

A Survey of Advanced Usages of X.500

This document is the result of a survey asking people to detail their advanced usages of X.500. It is intended to show how various organizations are using X.500 in ways which extend the view of X.500 as a "White Pages" service. This RFC is a product of the Integrated Directory Services Working Group of the Application and User Services Areas of the IETF. This memo provides information for the Inte…

Multiprotocol Interconnect over Frame Relay

Multiprotocol Interconnect over Frame Relay

This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. Additionally, it describes a simple fragmentation procedure for carrying large frames over a frame relay network with a smaller MTU. [STANDARDS-TRACK]

Registration of a Cyrillic Character Set

Registration of a Cyrillic Character Set

Though the proposed character set "koi8-r" is not currently an international standard, there is very large user community (including Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard for Unix and global network applications in the former Soviet Union. This is the reason the Society of Unix User Groups (SUUG) believes "koi8-r" should be registered. This memo provides information f…

The X.500 String Representation of Standard Attribute Syntaxes

The X.500 String Representation of Standard Attribute Syntaxes

This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the LDAP, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. [STANDARDS-TRACK]

X.500 Lightweight Directory Access Protocol

X.500 Lightweight Directory Access Protocol

The protocol described in this document is designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). [STANDARDS-TRACK]

An Experiment in Remote Printing

An Experiment in Remote Printing

This memo describes a technique for "remote printing" using the Internet mail infrastructure. In particular, this memo focuses on the case in which remote printers are connected to the international telephone network. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.

A String Representation of Distinguished Names (OSI-DS 23 (v5))

A String Representation of Distinguished Names (OSI-DS 23 (v5))

When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. [STANDARDS-TRACK]

Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))

Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))

This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard.

Multiprotocol Encapsulation over ATM Adaptation Layer 5

Multiprotocol Encapsulation over ATM Adaptation Layer 5

This memo describes two encapsulations methods for carrying network interconnect traffic over ATM AAL5. [STANDARDS-TRACK]

Aggregation Support in the NSFNET Policy-Based Routing Database

Aggregation Support in the NSFNET Policy-Based Routing Database

This document describes plans for support of route aggregation, as specified in the descriptions of Classless Inter-Domain Routing (CIDR) [1] and the BGP-4 protocol [2], by the NSFNET Backbone Network Service. This memo provides information for the Internet community. It does not specify an Internet standard.