rfc1499.txt

RFC 的详细文档！

Network Working Group                                         J. Elliott
Request for Comments: 1499                                           ISI
Category: Informational                                     January 1997


                      Request for Comments Summary

                         RFC Numbers 1400-1499

Status of This Memo

   This RFC is a slightly annotated list of the 100 RFCs from RFC 1400
   through RFCs 1499.  This is a status report on these RFCs.  This memo
   provides information for the Internet community.  It does not specify
   an Internet standard of any kind.  Distribution of this memo is
   unlimited.

Note

   Many RFCs, but not all, are Proposed Standards, Draft Standards, or
   Standards.  Since the status of these RFCs may change during the
   standards processing, we note here only that they are on the
   standards track.  Please see the latest edition of "Internet Official
   Protocol Standards" for the current state and status of these RFCs.
   In the following, RFCs on the standards track are marked [STANDARDS-
   TRACK].

RFC     Author       Date      Title
---     ------       ----      -----

1499    Elliott      Jan 97   Requests For Comments Summary

This memo.


1498    Saltzer      Aug 93   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 memo
provides information for the Internet community.  It does not specify an
Internet standard.





Elliott                      Informational                      [Page 1]

RFC 1499                  Summary of 1400-1499              January 1997


1497    Reynolds     Aug 93   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).


1496    Alverstrand  Aug 93   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:

                    SMTP(MIME) -> X.400(84)
                    X.400(84) -> SMTP(MIME)

It replaces chapter 6 of RFC-1328. The rest of RFC-1328 is NOT
obsoleted.  [STANDARDS-TRACK]


1495    Alverstrand  Aug 93   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]


1494    Alverstrand  Aug 93   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]










Elliott                      Informational                      [Page 2]

RFC 1499                  Summary of 1400-1499              January 1997


1493    Decker       Jul 93   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]


1492    Finseth      Jul 93   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.


1491    Weider       Jul 93   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 Internet
community.  It does not specify an Internet standard.


1490    Bradley      Jul 93   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]












Elliott                      Informational                      [Page 3]

RFC 1499                  Summary of 1400-1499              January 1997


1489    Chernov      Jul 93   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 for the Internet
community.  It does not specify an Internet standard.


1488    Howes        Jul 93   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]


1487    Yeong        Jul 93   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]


1486    Rose         Jul 93   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.


1485    Kille        Jul 93   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]






Elliott                      Informational                      [Page 4]

RFC 1499                  Summary of 1400-1499              January 1997


1484    Kille        Jul 93   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.


1483    Heinanen     Jul 93   Multiprotocol Encapsulation over ATM
                              Adaptation Layer 5

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


1482    Knopper      Jun 93   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.


1481    Huitema      Jul 93   IAB Recommendation for an Intermediate
                              Strategy to Address the Issue of Scaling

CIDR is proposed as an immediate term strategy to extend the life of the
current 32 bit IP address space.  This memo provides information for the
Internet community.  It does not specify an Internet standard.


1480    Cooper       Jun 93   The US Domain

This is a description of the US Top Level Domains on the Internet.  This
memo provides information for the Internet community. It does not
specify an Internet standard.


1479    Steenstrup   Jul 93   Inter-Domain Policy Routing Protocol
                              Specification: Version 1

We present the set of protocols and procedures that constitute Inter-
Domain Policy Routing (IDPR).  [STANDARDS-TRACK]





Elliott                      Informational                      [Page 5]

RFC 1499                  Summary of 1400-1499              January 1997


1478    Steenstrup   Jul 93   An Architecture for Inter-Domain Policy
                              Routing

We present an architecture for inter-domain policy routing (IDPR).
[STANDARDS-TRACK]


1477    Steenstrup   Jul 93   IDPR as a Proposed Standard

This document contains a discussion of inter-domain policy routing
(IDPR), including an overview of functionality and a discussion of
experiments.  This memo provides information for the Internet community.
It does not specify an Internet standard.


1476    Ullman       Jun 93   RAP: Internet Route Access Protocol

This RFC describes an open distance vector routing protocol for use at
all levels of the internet, from isolated LANs to the major routers of
an international commercial network provider.  This memo defines an
Experimental Protocol for the Internet community.  It does not specify
an Internet standard.


1475    Ullman       Jun 93   TP/IX: The Next Internet

This memo presents the specification for version 7 of the Internet
Protocol, as well as version 7 of the TCP and the user datagram
protocol.  This memo defines an Experimental Protocol for the Internet
community.  It does not specify an Internet standard.


1474    Kastrenholz  Jun 93   The Definitions of Managed Objects for
                              the Bridge Network Control Protocol of
                              the Point-to-Point Protocol

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 describes managed objects used for managing the bridge
Network Control Protocol [10] on subnetwork interfaces using the family
of Point-to-Point Protocols.  [STANDARDS-TRACK]










Elliott                      Informational                      [Page 6]

RFC 1499                  Summary of 1400-1499              January 1997


1473    Kastrenholz  Jun 93   The Definitions of Managed Objects for
                              the IP Network Control Protocol of
                              the Point-to-Point Protocol

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 describes managed objects used for managing the IP
Network Control Protocol on subnetwork interfaces using the family of
Point-to-Point Protocols [8, 9, 10, 11, & 12].  [STANDARDS-TRACK]


1472    Kastrenholz  Jun 93   The Definitions of Managed Objects for
                              the Security Protocols of
                              the Point-to-Point Protocol

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 describes managed objects used for managing the Security
Protocols on subnetwork interfaces using the family of Point-to-Point
Protocols [8, 9, 10, 11, & 12].  [STANDARDS-TRACK]


1471    Kastrenholz  Jun 93   The Definitions of Managed Objects for
                              the Link Control Protocol of
                              the Point-to-Point Protocol

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 describes managed objects used for managing the Link
Control Protocol and Link Quality Monitoring on subnetwork interfaces
that use the family of Point-to-Point Protocols [8, 9, 10, 11, & 12].
[STANDARDS-TRACK]


1470    Enger        Jun 93   FYI on a Network Management Tool
                              Catalog: Tools for Monitoring and
                              Debugging TCP/IP Internets and
                              Interconnected Devices

The goal of this FYI memo is to provide an update to FYI 2, RFC 1147
[1], which provided practical information to site administrators and
network managers.  This memo provides information for the Internet
community.  It does not specify an Internet standard.








Elliott                      Informational                      [Page 7]