As per Relevance of the word management, we have this rfc below:
Network Working Group J.
Request for Comments: 1499
Category: Informational January 1997
Request for Comments
RFC Numbers 1400-1499
Status of This
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
provides information for the Internet community. It does not
an Internet standard of any kind. Distribution of this memo
unlimited
Many RFCs, but not all, are Proposed Standards, Draft Standards,
Standards. Since the status of these RFCs may change during
standards processing, we note here only that they are on
standards track. Please see the latest edition of "Internet
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
--- ------ ---- -----
1499 Elliott Jan 97 Requests For Comments
This memo
1498 Saltzer Aug 93 On the Naming and Binding of
This brief paper offers a perspective on the subject of names
destinations in data communication networks. It suggests two ideas
First, it is helpful to distinguish among four different kinds
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
describe the relations among the four kinds of objects. This
provides information for the Internet community. It does not specify
Internet standard
Elliott Informational [Page 1]
RFC 1499 Summary of 1400-1499 January 1997
1497 Reynolds Aug 93 BOOTP Vendor Information
This RFC is a slight revision and extension of RFC-1048 by
Prindeville, who should be credited with the original work in this memo
This memo is a status report on the vendor information extensions
in the Bootstrap Protocol (BOOTP).
1496 Alverstrand Aug 93 Rules for Downgrading Messages
X.400/88 to X.400/84 When
Content-Types are Present in
This document describes how RFC-1328 must be modified in order
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
obsoleted. [STANDARDS-TRACK
1495 Alverstrand Aug 93 Mapping between X.400 and RFC-822
Message
Since the introduction of X.400(84), there has been work ongoing
defining mappings between MHS and RFC-822. The most recent work in
area is RFC-1327 [3], which focuses primarily on translation of
and headers. This document is complimentary to RFC-1327 as it
on translation of the message body. [STANDARDS-TRACK
1494 Alverstrand Aug 93 Equivalences between 1988 X.400
RFC-822 Message
This document describes the content of the "IANA MHS/MIME
table", and defines the initial configuration of this table.
for new MIME content-types and/or X.400 body part types should
registered with the IANA to minimize redundancy and
interoperability. [STANDARDS-TRACK
Elliott Informational [Page 2]
RFC 1499 Summary of 1400-1499 January 1997
1493 Decker Jul 93 Definitions of Managed
for
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP based internets.
particular it defines objects for managing MAC bridges based on the
802.1D-1990 standard between Local Area Network (LAN) segments
[STANDARDS-TRACK
1492 Finseth Jul 93 An Access Control Protocol,
Called
This RFC documents the extended TACACS protocol use by the Cisco
terminal servers. This same protocol is used by the University
Minnesota's distributed authentication system. This memo
information for the Internet community. It does not specify an
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
advanced usages of X.500. It is intended to show how
organizations are using X.500 in ways which extend the view of X.500
a "White Pages" service. This RFC is a product of the
Directory Services Working Group of the Application and User
Areas of the IETF. This memo provides information for the
community. It does not specify an Internet standard
1490 Bradley Jul 93 Multiprotocol Interconnect over
This memo describes an encapsulation method for carrying
interconnect traffic over a Frame Relay backbone. It covers aspects
both Bridging and Routing. Additionally, it describes a
fragmentation procedure for carrying large frames over a frame
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
Though the proposed character set "koi8-r" is not currently
international standard, there is very large user community (
Relcom Net) supporting it. Factually, "koi8-r" is de-facto standard
Unix and global network applications in the former Soviet Union.
is the reason the Society of Unix User Groups (SUUG) believes "koi8-r
should be registered. This memo provides information for the
community. It does not specify an Internet standard
1488 Howes Jul 93 The X.500 String Representation
Standard Attribute
This document defines the requirements that must be satisfied
encoding rules used to render Directory attribute syntaxes into a
suitable for use in the LDAP, then goes on to define the encoding
for the standard set of attribute syntaxes defined in [1,2] and [3].
[STANDARDS-TRACK
1487 Yeong Jul 93 X.500 Lightweight Directory
The protocol described in this document is designed to provide access
the Directory while not incurring the resource requirements of
Directory Access Protocol (DAP). [STANDARDS-TRACK
1486 Rose Jul 93 An Experiment in Remote
This memo describes a technique for "remote printing" using the
mail infrastructure. In particular, this memo focuses on the case
which remote printers are connected to the international
network. This memo defines an Experimental Protocol for the
community. It does not specify an Internet standard
1485 Kille Jul 93 A String Representation of
Names (OSI-DS 23 (v5))
When a distinguished name is communicated between to users not using
directory protocol (e.g., in a mail message), there is a need to have
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
User Friendly Naming (OSI-DS 24 (v1.2))
This proposal sets out some conventions for representing names in
friendly manner, and shows how this can be used to achieve
friendly naming. This memo defines an Experimental Protocol for
Internet community. It does not specify an Internet standard
1483 Heinanen Jul 93 Multiprotocol Encapsulation over
Adaptation Layer 5
This memo describes two encapsulations methods for carrying
interconnect traffic over ATM AAL5. [STANDARDS-TRACK
1482 Knopper Jun 93 Aggregation Support in the
Policy-Based Routing
This document describes plans for support of route aggregation,
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
specify an Internet standard
1481 Huitema Jul 93 IAB Recommendation for an
Strategy to Address the Issue of
CIDR is proposed as an immediate term strategy to extend the life of
current 32 bit IP address space. This memo provides information for
Internet community. It does not specify an Internet standard
1480 Cooper Jun 93 The US
This is a description of the US Top Level Domains on the Internet.
memo provides information for the Internet community. It does
specify an Internet standard
1479 Steenstrup Jul 93 Inter-Domain Policy Routing
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
We present an architecture for inter-domain policy routing (IDPR).
[STANDARDS-TRACK
1477 Steenstrup Jul 93 IDPR as a Proposed
This document contains a discussion of inter-domain policy
(IDPR), including an overview of functionality and a discussion
experiments. This memo provides information for the Internet community
It does not specify an Internet standard
1476 Ullman Jun 93 RAP: Internet Route Access
This RFC describes an open distance vector routing protocol for use
all levels of the internet, from isolated LANs to the major routers
an international commercial network provider. This memo defines
Experimental Protocol for the Internet community. It does not
an Internet standard
1475 Ullman Jun 93 TP/IX: The Next
This memo presents the specification for version 7 of the
Protocol, as well as version 7 of the TCP and the user
protocol. This memo defines an Experimental Protocol for the
community. It does not specify an Internet standard
1474 Kastrenholz Jun 93 The Definitions of Managed Objects
the Bridge Network Control Protocol
the Point-to-Point
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it describes managed objects used for managing the
Network Control Protocol [10] on subnetwork interfaces using the
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
the IP Network Control Protocol
the Point-to-Point
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it describes managed objects used for managing the
Network Control Protocol on subnetwork interfaces using the family
Point-to-Point Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK
1472 Kastrenholz Jun 93 The Definitions of Managed Objects
the Security Protocols
the Point-to-Point
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it describes managed objects used for managing the
Protocols on subnetwork interfaces using the family of Point-to-
Protocols [8, 9, 10, 11, & 12]. [STANDARDS-TRACK
1471 Kastrenholz Jun 93 The Definitions of Managed Objects
the Link Control Protocol
the Point-to-Point
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it describes managed objects used for managing the
Control Protocol and Link Quality Monitoring on subnetwork
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
Catalog: Tools for Monitoring
Debugging TCP/IP Internets
Interconnected
The goal of this FYI memo is to provide an update to FYI 2, RFC 1147
[1], which provided practical information to site administrators
network managers. This memo provides information for the
community. It does not specify an Internet standard
Elliott Informational [Page 7]
RFC 1499 Summary of 1400-1499 January 1997
1469 Pusateri Jun 93 IP Multicast over Token-Ring Local
This document specifies a method for the transmission of IP
datagrams over Token-Ring Local Area Networks. [STANDARDS-TRACK
1468 Murai Jun 93 Japanese Character Encoding for
This document describes the encoding used in electronic mail [RFC822]
and network news [RFC1036] messages in several Japanese networks.
memo provides information for the Internet community. It does
specify an Internet standard
1467 Topolcic Aug 93 Status of CIDR Deployment in
This document describes the current status of the development
deployment of CIDR technology into the Internet. This document
RFC 1367, which was a schedule for the deployment of IP address
management procedures to support route aggregation. This memo
information for the Internet community. It does not specify an
standard
1466 Gerich May 93 Guidelines for Management of IP
This document proposes a plan which will forward the implementation
RFC 1174 and which defines the allocation and assignment of the
number space. This memo provides information for the
community. It does not specify an Internet standard
1465 Eppenberger May 93 Routing Coordination for X.400
Services Within a Multi Protocol /
Network Environment Table Format V3
Static
This document proposes short term solutions for maintaining
distributing routing information and shows how messages can travel
different networks by using multi stack MTAs as relays. This
defines an Experimental Protocol for the Internet community
Elliott Informational [Page 8]
RFC 1499 Summary of 1400-1499 January 1997
1464 Rosenbaum May 93 Using the Domain Name
To Store Arbitrary String
This paper describes a simple means to associate arbitrary
information (ASCII text) with attributes that have not been defined
the DNS. This memo defines an Experimental Protocol for the
community
1463 Hoffman May 93 FYI on Introducing the Internet--
A Short Bibliography of
Internetworking Readings for the
This bibliography offers a short list of recent information
that will help the network novice become familiar with the Internet
including its associated networks, resources, protocols, and history
This memo provides information for the Internet community. It does
specify an Internet standard
1462 Krol May 93 FYI on "What is the Internet?"
This FYI RFC answers the question, "What is the Internet?" and
produced by the User Services Working Group of the Internet
Task Force (IETF). This memo provides information for the
community. It does not specify an Internet standard
1461 Throop May 93 SNMP MIB extension for
Interconnect over X.25
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing Multiprotocol
(including IP) traffic carried over X.25. [STANDARDS-TRACK
1460 Rose Jun 93 Post Office Protocol - Version 3
This memo is a revision to RFC 1225, a Draft Standard. [STANDARDS
TRACK
Elliott Informational [Page 9]
RFC 1499 Summary of 1400-1499 January 1997
1459 Oikarinen May 93 Internet Relay Chat
The IRC protocol is a text-based protocol, with the simplest
being any socket program capable of connecting to the server. This
defines an Experimental Protocol for the Internet community
1458 Braudes May 93 Requirements for Multicast
This memo discusses some of these unresolved issues, and provides
high-level design for a new multicast transport protocol, group
and membership authority, and modifications to existing
protocols. This memo provides information for the Internet community
It does not specify an Internet standard
1457 Housley May 93 Security Label Framework for
This memo presents a security labeling framework for the Internet.
framework is intended to help protocol designers determine what, if any
security labeling should be supported by their protocols. This
provides information for the Internet community. It does not specify
Internet standard
1456 V.S.W.G. May 93 Conventions for Encoding the
Language VISCII: VIetnamese
Code for Information Interchange VIQR
Vietnamese Quoted-Readable
Revision 1.1
This document provides information to the Internet community on
currently used conventions for encoding Vietnamese characters into 7-
US ASCII and in an 8-bit form. This memo provides information for
Internet community. It does not specify an Internet standard
1455 Eastlake May 93 Physical Link Security Type of
This RFC documents an experimental protocol providing a Type of
(TOS) to request maximum physical link security. This is an addition
the types of service enumerated in RFC 1349: Type of Service in
Internet Protocol Suite. This memo defines an Experimental Protocol
the Internet community
Elliott Informational [Page 10]
RFC 1499 Summary of 1400-1499 January 1997
1454 Dixon May 93 Comparison of Proposals for Next
of
This is a slightly edited reprint of RARE Technical Report (RTC(93)004).
This memo provides information for the Internet community. It does
specify an Internet standard
1453 Chimiak Apr 93 A Comment on Packet Video
Conferencing and the Transport/
This RFC is a vehicle to inform the Internet community about XTP as
benefits from past Internet activity and targets general-
applications and multimedia applications with the emerging ATM
in mind. This memo provides information for the Internet community.
does not specify an Internet standard
1452 Case Apr 93 Coexistence between version 1
version 2 of the Internet-
Network Management
The purpose of this document is to describe coexistence between
2 of the Internet-standard Network Management Framework, termed the
version 2 framework (SNMPv2) [1], and the original Internet-
Network Management Framework (SNMPv1). [STANDARDS-TRACK
1451 Case Apr 93 Manager-to-
Management Information
It is the purpose of this document to define managed objects
describe the behavior of a SNMPv2 entity acting in both a manager
and an agent role. [STANDARDS-TRACK
1450 Case Apr 93 Management Information Base for
2 of the Simple Network
Protocol (SNMPv2)
It is the purpose of this document to define managed objects
describe the behavior of a SNMPv2 entity. [STANDARDS-TRACK
Elliott Informational [Page 11]
RFC 1499 Summary of 1400-1499 January 1997
1449 Case Apr 93 Transport Mapplings for version 2 of
Simple Network Management
(SNMPv2)
It is the purpose of this document to define how the SNMPv2 maps onto
initial set of transport domains. [STANDARDS-TRACK
1448 Case Apr 93 Protocol Operations for version 2 of
Simple Network Management
(SNMPv2)
It is the purpose of this document, Protocol Operations for SNMPv2,
define the operations of the protocol with respect to the sending
receiving of the PDUs. [STANDARDS-TRACK
1447 McCloghrie Apr 93 Party MIB for version 2 of the
Network Management Protocol (SNMPv2)
The Administrative Model for SNMPv2 document [3] defines the
associated with SNMPv2 parties, SNMPv2 contexts, and access
policies. It is the purpose of this document, the Party MIB for SNMPv2,
to define managed objects which correspond to these properties
[STANDARDS-TRACK
1446 Galvin Apr 93 Security Protocols for version 2 of
Simple Network Management
(SNMPv2)
It is the purpose of this document, Security Protocols for SNMPv2,
define one such authentication and one such privacy protocol
[STANDARDS-TRACK
1445 Galvin Apr 93 Administrative Model for version 2
the Simple Network Management
(SNMPv2)
It is the purpose of this document, the Administrative Model for SNMPv2,
to define how the administrative framework is applied to
effective network management in a variety of configurations
environments. [STANDARDS-TRACK
Elliott Informational [Page 12]
RFC 1499 Summary of 1400-1499 January 1997
1444 Case Apr 93 Conformance Statements for version 2
the Simple Network Management
(SNMPv2)
It may be useful to define the acceptable lower-bounds
implementation, along with the actual level of implementation achieved
It is the purpose of this document to define the notation used for
purposes. [STANDARDS-TRACK
1443 Case Apr 93 Textual Conventions for version 2 of
Simple Network Management
(SNMPv2)
It is the purpose of this document to define the initial set of
conventions available to all MIB modules. [STANDARDS-TRACK
1442 Case Apr 93 Structure of Management Information
version 2 of the Simple
Management Protocol (SNMPv2)
Management information is viewed as a collection of managed objects
residing in a virtual information store, termed the
Information Base (MIB). Collections of related objects are defined
MIB modules. These modules are written using a subset of OSI's
Syntax Notation One (ASN.1) [1]. It is the purpose of this document
the Structure of Management Information (SMI), to define that subset
[STANDARDS-TRACK
1441 Case Apr 93 Introduction to version 2 of
Internet-standard Network
The purpose of this document is to provide an overview of version 2
the Internet-standard Network Management Framework, termed the
version 2 framework (SNMPv2). [STANDARDS-TRACK
1440 Troth Jul 93 SIFT/UFT: Sender-Initiated/
File
This document describes a Sender-Initiated File Transfer (SIFT
protocol, also commonly called Unsolicited File Transfer (UFT) protocol
This memo defines an Experimental Protocol for the Internet community
Elliott Informational [Page 13]
RFC 1499 Summary of 1400-1499 January 1997
1439 Finseth Mar 93 The Uniqueness of Unique
This RFC provides information that may be useful when selecting a
to use for assigning unique identifiers to people. This memo
information for the Internet community. It does not specify an
standard
1438 Chapin Apr 93 IETF Statements Of Boredom (SOB)
This document creates a new subseries of RFCs, entitled, IETF
Of Boredom (SOBs). This memo provides information for the
community. It does not specify an Internet standard
1437 Borenstein Apr 93 The Extension of MIME Content-Types to
New
This document defines one particular type of MIME data, the matter
transport/sentient-life-form type. This memo provides information
the Internet community. It does not specify an Internet standard
1436 Anklesaria Mar 93 The Internet Gopher
This document describes the protocol, lists some of the
currently available, and has an overview of how to implement new
and server applications. This memo provides information for
Internet community. It does not specify an Internet standard
1435 Knowles Mar 93 IESG Advice from Experience with
MTU
In the course of reviewing the MTU Discovery protocol for
elevation to Draft Standard, a specific operational problem
uncovered. The problem results from the optional suppression of
messages implemented in some routers. This memo outlines a
to this practice to allow the correct functioning of MTU Discovery
This memo provides information for the Internet community. It does
specify an Internet standard
Elliott Informational [Page 14]
RFC 1499 Summary of 1400-1499 January 1997
1434 Dixon Mar 93 Data Link Switching: Switch-to-
This RFC describes IBM's support of Data Link Switching over TCP/IP
This memo provides information for the Internet community. It does
specify an Internet standard
1433 Garrett Mar 93 Directed
Directed ARP is a dynamic address resolution procedure that
hosts and routers to resolve advertised potential next-hop IP
on foreign IP networks to their associated link level addresses.
memo defines an Experimental Protocol for the Internet community
1432 Quarterman Mar 93 Recent Internet
Here is a list of books related to using the Internet. This
provides information for the Internet community. It does not specify
Internet standard
1431 Barker Feb 93 DUA
This document defines a set of criteria by which a DUA implementation
or more precisely a Directory user interface, may be judged. This
provides information for the Internet community. It does not specify
Internet standard
1430 Kille Feb 93 A Strategic Plan for Deploying
Internet X.500 Directory
This document describes an overall strategy for deploying a
Service on the Internet, based on the OSI X.500 Directory Service.
memo provides information for the Internet community. It does
specify an Internet standard
1429 Thomas Feb 93 Listserv Distribute
This memo specifies a subset of the distribution protocol used by
BITNET LISTSERV to deliver mail messages to large amounts of recipients
This memo provides information for the Internet community. It does
specify an Internet standard
Elliott Informational [Page 15]
RFC 1499 Summary of 1400-1499 January 1997
1428 Vaudreuil Feb 93 Transition of Internet Mail
Just-Send-8 to 8bit-SMTP/
This document outlines the problems in this environment and an
to minimizing the cost of transition from current usage of non-MIME 8
messages to MIME. This RFC provides information for the
community. It does not specify an Internet standard
1427 Klensin Feb 93 SMTP Service
for Message Size
This memo defines an extension to the SMTP service whereby an
client and server may interact to give the server an opportunity
decline to accept a message (perhaps temporarily) based on the client'
estimate of the message size. [STANDARDS-TRACK
1426 Klensin Feb 93 SMTP Service
for 8bit-
This memo defines an extension to the SMTP service whereby an
content body containing octets outside of the US ASCII octet range (
00-7F) may be relayed using SMTP. [STANDARDS-TRACK
1425 Klensin Feb 93 SMTP Service
This memo defines a framework for extending the SMTP service by
a means whereby a server SMTP can inform a client SMTP as to the
extensions it supports. [STANDARDS-TRACK
1424 Kaliski Feb 93 Privacy Enhancement for
Electronic Mail: Part IV:
Certification and Related
This document describes three types of service in support of
Privacy-Enhanced Mail (PEM) [1-3]: key certification, certificate
revocation list (CRL) storage, and CRL retrieval. [STANDARDS-TRACK
Elliott Informational [Page 16]
RFC 1499 Summary of 1400-1499 January 1997
1423 Balenson Feb 93 Privacy Enhancement for
Electronic Mail: Part III: Algorithms
Modes, and
This document provides definitions, formats, references, and
for cryptographic algorithms, usage modes, and associated
and parameters used in support of Privacy Enhanced Mail (PEM) in
Internet community. [STANDARDS-TRACK
1422 Kent Feb 93 Privacy Enhancement for
Electronic Mail: Part II
Certificate-Based Key
This is one of a series of documents defining privacy
mechanisms for electronic mail transferred using Internet
protocols. [STANDARDS-TRACK
1421 Linn Feb 93 Privacy Enhancement for
Electronic Mail: Part I:
Encryption and
This document defines message encryption and authentication procedures
in order to provide privacy-enhanced mail (PEM) services for
mail transfer in the Internet. [STANDARDS-TRACK
1420 Bostock Mar 93 SNMP over
This document defines a convention for encapsulating Simple
Management Protocol (SNMP) [1] packets over the transport
provided via the Internetwork Packet Exchange (IPX) protocol [2].
[STANDARDS-TRACK
1419 Minshall Mar 93 SNMP over
This memo describes the method by which the Simple Network
Protocol (SNMP) as specified in [1] can be used over AppleTalk
[2] instead of the Internet UDP/IP protocol stack. [STANDARDS-TRACK
Elliott Informational [Page 17]
RFC 1499 Summary of 1400-1499 January 1997
1418 Rose Mar 93 SNMP over
This memo addresses some concerns by defining a framework for
the SNMP in an environment which supports the OSI connectionless-
transport service. [STANDARDS-TRACK
1417 N.A.D.F. Feb 93 NADF Standing Documents
A Brief
The purpose of this document is to provide a brief overview of
NADF's Standing Document series. This memo provides information for
Internet community. It does not specify an Internet standard
1416 Borman Feb 93 Telnet Authentication
This RFC 1416 replaces RFC 1409, which has an important
error in the example on page 6 (one occurance of "REPLY" should
"IS"). This memo defines an Experimental Protocol for the
community
1415 Mindel Jan 93 FTP-FTAM Gateway
This memo describes a dual protocol stack application layer gateway
performs protocol translation, in an interactive environment,
the FTP and FTAM file transfer protocols. [STANDARDS-TRACK
1414 St. Johns Feb 93 Identification
This memo defines a MIB for use with identifying the users
with TCP connections. It provides functionality
equivalent to that provided by the protocol defined in RFC 1413 [1].
[STANDARDS-TRACK
1413 St. Johns Feb 93 Identification
The Identification Protocol was formerly called the
Server Protocol. It has been renamed to better reflect its function
[STANDARDS-TRACK
Elliott Informational [Page 18]
RFC 1499 Summary of 1400-1499 January 1997
1412 Alagappan Jan 93 Telnet Authentication:
This memo defines an Experimental Protocol for the Internet community
1411 Borman Jan 93 Telnet Authentication
Kerberos Version 4
This memo defines an Experimental Protocol for the Internet community
1410 I.A.B Mar 93 IAB OFFICIAL PROTOCOL
This memo describes the state of standardization of protocols used
the Internet as determined by the Internet Architecture Board (IAB).
1409 Borman Jan 93 Telnet Authentication
This memo defines an Experimental Protocol for the Internet community
1408 Borman Jan 93 Telnet Environment
This document specifies a mechanism for passing environment
between a telnet client and server. [STANDARDS-TRACK
1407 Cox Jan 93 Definitions of Managed Objects for
DS3/E3 Interface
This memo defines an extension to the Management Information Base (MIB
for use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing DS3 and E3 Interfaces
[STANDARDS-TRACK
1406 Basker Jan 93 Definitions of Managed Objects for
DS1 and E1 Interface
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it defines objects for managing DS1 Interfaces --
both T1 and E1 (a.k.a., CEPT 2 Mbit/s) links. [STANDARDS-TRACK
Elliott Informational [Page 19]
RFC 1499 Summary of 1400-1499 January 1997
1405 Allocchio Jan 93 Mapping between X.400(1984/1988)
Mail-11 (DECnet mail
This document describes a set of mappings which will enable
working between systems operating the CCITT X.400 ( 1984 / 1988 )
Recommendations on Message Handling Systems, and systems running
Mail-11 (also known as DECnet mail) protocol. This memo defines
Experimental Protocol for the Internet community
1404 Stockman Jan 93 A Model for Common
This memo describes a model for operational statistics in the Internet
It gives recommendations for metrics, measurements, polling periods
storage formats and presentation formats. This memo
information for the Internet community. It does not specify an
standard
1403 Varadhan Jan 93 BGP OSPF
This memo defines the various criteria to be used when designing
Autonomous System Border Routers (ASBR) that will run BGP with
ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK
1402 Martin Jan 93 There's Gold in them thar Networks
Searching for Treasure in all the
The ultimate goal is to make the route to these sources of
invisible to you. At present, this is not easy to do. I will
some of the techniques that can be used to make these nuggets easier
pick up so that we all can be richer. This RFC provides information
the Internet community. It does not specify an Internet standard
1401 I.A.B. Jan 93 Correspondence between the IAB and
on the use of DNS throughout
This memo reproduces three letters exchanged between the
Activities Board (IAB) and the Defense Information Systems Agency (DISA
regarding the importance of using the Domain Name System (DNS
throughout the Internet, and phasing out the use of older host name
address tables, such as "hosts.txt". This memo provides information
the Internet community. It does not specify an Internet standard
Elliott Informational [Page 20]
RFC 1499 Summary of 1400-1499 January 1997
1400 Williamson Mar 93 Transition and
of the Internet Registration
As a result of the NREN NIS award by National Science Foundation, non
DDN registration services will soon be transferred from the DDN NIC
the new Internet Registration Service, which is a part of an
referred to as the InterNIC. This memo provides information for
Internet community. It does not specify an Internet standard
Security
Security issues are not discussed in this memo
Author's
Josh
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: elliott@isi.
Elliott Informational [Page 21]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
