As per Relevance of the word management, we have this rfc below:
Network Working Group J.
Request for Comments: 1399
Category: Informational January 1997
Request for Comments
RFC Numbers 1300-1399
Status of This
This RFC is a slightly annotated list of the 100 RFCs from RFC 1300
through RFCs 1399. 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
--- ------ ---- -----
1399 Elliott Jan 97 Requests For Comments
This memo
1398 Kastenholz Jan 93 Definitions of Managed Objects for
Ethernet-like 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 ehternet-like objects
[STANDARDS-TRACK
Elliott Informational [Page 1]
RFC 1399 Summary of 1300-1399 January 1997
1397 Haskin Jan 93 Default Route Advertisement In BGP2
BGP3 Versions of the Border
This document speficies the recommendation of the BGP Working Group
default route advertisement support in BGP2 [1] and BGP3 [2] versions
the Border Gateway Protocol. [STANDARDS-TRACK
1396 Crocker Jan 93 The Process for Organization of
This report provides a summary of the POISED Working Group (WG),
starting from the events leading to the formation of the WG to the
of 1992. This memo provides information for the Internet community.
does not specify an Internet standard
1395 Reynolds Jan 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 will be updated as additional tags are defined. This
introduces Tag 14 for Merit Dump File, Tag 15 for Domain Name, Tag 16
for Swap Server and Tag 17 for Root Path. This memo is a status
on the vendor information extensions used int the Bootstrap
(BOOTP).
1394 Robinson Jan 93 Relationship of Telex Answerback
to Internet
This RFC gives the list, as best known, of all common Internet
and the conversion between specific country telex answerback codes
Internet country domain identifiers. It also lists the telex code
international dialing code, wherever it is available. It will also
major Internet "Public" E-Mail addresses. This memo
information for the Internet community. It does not specify an
standard
1393 Malkin Jan 93 Traceroute Using an IP
This document specifies a new IP option and ICMP message type
duplicates the functionality of the existing traceroute method
generating fewer packets and completing in a shorter time. This
defines an Experimental Protocol for the Internet community
Elliott Informational [Page 2]
RFC 1399 Summary of 1300-1399 January 1997
1392 Malkin Jan 93 Internet Users'
There are many networking glossaries in existence. This
concentrates on terms which are specific to the Internet. This
provides information for the Internet community. It does not specify
Internet standard
1391 Malkin Jan 93 The Tao of
A Guide for New Attendees of
Internet Engineering Task
The purpose of this For Your Information (FYI) RFC is to explain to
newcomers how the IETF works. This will give them a warm, fuzzy
and enable them to make the meeting more productive for everyone.
memo provides information for the Internet community. It does
specify an Internet standard
1390 Katz Jan 93 Transmission of IP and ARP over
This memo defines a method of encapsulating the Internet Protocol (IP
datagrams and Address Resolution Protocol (ARP) requests and replies
Fiber Distributed Data Interface (FDDI) Networks. [STANDARDS-TRACK
1389 Malkin Jan 93 RIP Version 2 MIB
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets
[STANDARDS-TRACK
1388 Malkin Jan 93 RIP Version 2
Carrying Additional
This document specifies an extension of the Routing Information
(RIP), as defined in [1], to expand the amount of useful
carried in RIP packets and to add a measure of security. [STANDARDS
TRACK
Elliott Informational [Page 3]
RFC 1399 Summary of 1300-1399 January 1997
1387 Malkin Jan 93 RIP Version 2 Protocol
As required by Routing Protocol Criteria (RFC 1264), this
documents the key features of the RIP-2 protocol and the
implementation experience. This memo provides information for
Internet community. It does not specify an Internet standard
1386 Cooper Dec 92 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
1385 Wang Nov 92 EIP: The Extended Internet
A Framework for Maintaining
EIP can substantially reduce the amount of modifications needed to
current Internet systems and greatly ease the difficulties
transition. This is an "idea" paper and discussion is
encouraged on Big-Internet@munnari.oz.au. This memo
information for the Internet community. It does not specify an
standard
1384 Barker Jan 93 Naming Guidelines for Directory
This document defines a number of naming guidelines. Alignment to
guidelines is recommended for directory pilots. This memo
information for the Internet community. It does not specify an
standard
1383 Huitema Dec 92 An Experiment in DNS Based IP
Potential solutions to the routing explosion. This memo defines
Experimental Protocol for the Internet community
1382 Throop Nov 92 SNMP MIB Extension for the X.25
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets
[STANDARDS-TRACK
Elliott Informational [Page 4]
RFC 1399 Summary of 1300-1399 January 1997
1381 Throop Nov 92 SNMP MIB Extension for 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 the Link Layer of X.25,
LAPB. [STANDARDS-TRACK
1380 Gross Nov 92 IESG Deliberations on Routing
This memo summarizes issues surrounding the routing and
scaling problems in the IP architecture, and it provides a
background of the ROAD group and related activities in the
Engineering Task Force (IETF). This memo provides information for
Internet community. It does not specify an Internet standard
1379 Braden Nov 92 Extending TCP for Transactions --
This memo discusses extension of TCP to provide transaction-
service, without altering its virtual-circuit operation. This
provides information for the Internet community. It does not specify
Internet standard
1378 Parker Nov 92 The PPP AppleTalk Control
(ATCP
This document defines the NCP for establishing and configuring
AppleTalk Protocol [3] over PPP. [STANDARDS-TRACK
1377 Katz Nov 92 The PPP OSI Network Layer
Protocol (OSINLCP
This document defines the NCP for establishing and configuring
Network Layer Protocols. [STANDARDS-TRACK
Elliott Informational [Page 5]
RFC 1399 Summary of 1300-1399 January 1997
1376 Senum Nov 92 The PPP DECnet Phase IV
Protocol (DNCP
This document defines the NCP for establishing and configuring Digital'
DNA Phase IV Routing protocol (DECnet Phase IV) over PPP. This
applies only to DNA Phase IV Routing messages (both data and control),
and not to other DNA Phase IV protocols (MOP, LAT, etc.). [STANDARDS
TRACK
1375 Robinson Oct 92 Suggestion for New Classes of
This RFC suggests a change in the method of specifying the IP address
add new classes of networks to be called F, G, H, and K, to reduce
amount of wasted address space, and to increase the available IP
number space, especially for smaller organizations or classes
connectors that do not need or do not want a full Class C IP address
This memo provides information for the Internet community. It does
specify an Internet standard
1374 Renwick Oct 92 IP and ARP on
The ANSI X3T9.3 committee has drafted a proposal for the
of IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. Another X3T9.3
draft describes the operation of HIPPI physical switches. X3T9.3
to leave HIPPI networking issues largely outside the scope of
standards; this document discusses methods of using of ANSI
HIPPI hardware and protocols in the context of the Internet,
the use of HIPPI switches as LANs and interoperation with
networks. This memo is intended to become an Internet Standard
[STANDARDS-TRACK
1373 Tignor Oct 92 PORTABLE
This document comes in two parts. The first part is for regular
who wish to set up their own DUAs (Directory User Interfaces) to
the Directory. The second part is for ISODE-maintainers wishing
provide portable DUAs to users. This part gives instructions in
similar but longer, step-by-step format. This memo provides
for the Internet community. It does not specify an Internet standard
Elliott Informational [Page 6]
RFC 1399 Summary of 1300-1399 January 1997
1372 Hedrick Oct 92 Telnet Remote Flow Control
This document specifies an extended version of the Telnet Remote
Control Option, RFC 1080, with the addition of the RESTART-ANY
RESTART-XON suboptions. [STANDARDS-TRACK
1371 Gross Oct 92 Choosing a "Common IGP" for the
(The IESG's Recommendation to the IAB
This memo presents motivation, rationale and other
background information leading to the IESG's recommendation to the
for a single "common IGP" for the IP portions of the Internet.
memo provides information for the Internet community. It does
specify an Internet standard
1370 I.A.B. Oct 92 Applicability Statement for
This Applicability Statement places a requirement on vendors
conformance to this standard, in order to assure that users will
the option of deploying OSPF when they need a multivendor,
IGP in their environment. [STANDARDS-TRACK
1369 Kastenholz Oct 92 Implementation Notes and Experience
The Internet Ethernet
This document reflects the currently known status of 11
implementations of the MIB by 7 different vendors on 7
Ethernet interface chips. This memo provides information for
Internet community. It does not specify an Internet standard
1368 McMaster Oct 92 Definitions of Managed Objects for
802.3 Repeater
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 IEEE 802.3 10 Mb/
baseband repeaters, sometimes referred to as "hubs". [STANDARDS-TRACK
Elliott Informational [Page 7]
RFC 1399 Summary of 1300-1399 January 1997
1367 Topolcic Oct 92 Schedule for IP Address
Management
This memo suggests a schedule for the implementation of the IP
number allocation plan described in RFC 1366. This memo
information for the Internet community. It does not specify an
standard
1366 Gerich Oct 92 Guidelines for Management of IP
This document has been reviewed by the Federal Engineering Task
(FEPG) on behalf of the Federal Networking Council (FNC), the co-
of the International Engineering Planning Group (IEPG), and the
IP Europeens (RIPE). There was general consensus by those groups
support the recommendations proposed in this document for management
the IP address space. This memo provides information for the
community. It does not specify an Internet standard
1365 Siyan Spt 92 An IP Address Extension
This RFC suggests an extension to the IP protocol to solve the
of IP address problem, and requests discussion and suggestions
improvements. This memo provides information for the
community. It does not specify an Internet standard
1364 Varadhan Spt 92 BGP OSPF
This memo defines the various criteria to be used when
Autonomous System Border Routers (ASBR) that will run BGP with
ASBRs external to the AS and OSPF as its IGP. [STANDARDS-TRACK
1363 Partridge Spt 92 A Proposed Flow
The flow specification defined in this memo is intended for
and possible experimentation (i.e., experimental use by
routers and applications only). This RFC is a product of the
Research Task Force (IRTF). This memo provides information for
Internet community. It does not specify an Internet standard
Elliott Informational [Page 8]
RFC 1399 Summary of 1300-1399 January 1997
1362 Allen Spt 92 Novell IPX Over Various WAN
(IPXWAN
This document describes how Novell IPX operates over various WAN media
Specifically, it describes the common "IPX WAN" protocol Novell uses
exchange necessary router to router information prior to
standard IPX routing information and traffic over WAN datalinks.
memo provides information for the Internet community. It does
specify an Internet standard
1361 Mills Aug 92 Simple Network Time Protocol (SNTP
This memorandum describes the Simple Network Time Protocol (SNTP),
is an adaptation of the Network Time Protocol (NTP) used to
computer clocks in the Internet. This memorandum does not obsolete
update any RFC. This memo provides information for the
community. It does not specify an Internet standard
1360 I.A.B. Spt 92 IAB OFFICIAL PROTOCOL
Discussion of the standardization process and the RFC document series
presented first, followed by an explanation of the terms. Sections 6.2
- 6.9 contain the lists of protocols in each stage of standardization
Finally come pointers to references and contacts for
information. [STANDARDS-TRACK
1359 ACM SIGUCCS Aug 92 Connecting to the
What Connecting Institutions
This FYI RFC outlines the major issues an institution should consider
the decision and implementation of a campus connection to the Internet
This memo provides information for the Internet community. It does
specify an Internet standard
1358 Chapin Aug 92 Charter of the Internet
Board (IAB
The Internet Architecture Board (IAB) shall be constituted and
operate as a technical advisory group of the Internet Society.
memo provides information for the Internet community. It does
specify an Internet standard
Elliott Informational [Page 9]
RFC 1399 Summary of 1300-1399 January 1997
1357 Cohen Jul 92 A Format for E-mailing
This memo defines a format for E-mailing bibliographic records
technical reports. It is intended to accelerate the dissemination
information about new Computer Science Technical Reports (CS-TR).
memo provides information for the Internet community. It does
specify an Internet standard
1356 Malis Aug 92 Multiprotocol
on X.25 and ISDN in the Packet
This document specifies the encapsulation of IP and other network
protocols over X.25 networks, in accordance and alignment with ISO/
and CCITT standards. It is a replacement for RFC 877, "A Standard
the Transmission of IP Datagrams Over Public Data Networks" [1].
[STANDARDS-TRACK
1355 Curran Aug 92 Privacy and Accuracy Issues in
Information Center
This document provides a set of guidelines for the administration
operation of public Network Information Center (NIC) databases.
memo provides information for the Internet community. It does
specify an Internet standard
1354 Baker Jul 92 IP Forwarding Table
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 routes in the IP Internet
[STANDARDS-TRACK
1353 McCloghrie Jul 92 Definitions of Managed
for Administration of SNMP
This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in TCP/IP-based internets.
particular, it describes a representation of the SNMP parties defined
[8] as objects defined according to the Internet Standard SMI [1].
[STANDARDS-TRACK
Elliott Informational [Page 10]
RFC 1399 Summary of 1300-1399 January 1997
1352 Galvin Jul 92 SNMP Security
The Simple Network Management Protocol (SNMP) specification [1]
for the protection of network management operations by a variety
security protocols. The SNMP administrative model described in [2]
provides a framework for securing SNMP network management. In
context of that framework, this memo defines protocols to support
following three security services: data integrity, data
authentication and data confidentiality. [STANDARDS-TRACK
1351 Davin Jul 92 SNMP Administrative
This memo presents an elaboration of the SNMP administrative model
forth in [1]. This model provides a unified conceptual basis
administering SNMP protocol entities to support: authenticaiton
integrity, privacy, access control, and cooperation of
entities. [STANDARDS-TRACK
1350 Sollins Jul 92 THE TFTP PROTOCOL (REVISION 2)
TFTP is a very simple protocol used to transfer files. It is from
that its name comes, Trivial File Transfer Protocol or TFTP.
nonterminal packet is acknowledged separately. This document
the protocol and its types of packets. The document also explains
reasons behind some of the design decisions. [STANDARDS-TRACK
1349 Almquist Jul 92 Type of Service in the
Protocol
This memo changes and clarifies some aspects of the semantics of
Type of Service octet in the Internet Protocol (IP) header
[STANDARDS-TRACK
1348 Manning Jul 92 DNS NSAP
This RFC defines the format of two new Resource Records (RRs) for
Domain Name System (DNS), and reserves corresponding DNS type
and numerical codes. This memo defines an Experimental Protocol for
Internet community
Elliott Informational [Page 11]
RFC 1399 Summary of 1300-1399 January 1997
1347 Callon Jun 92 TCP and UDP with bigger
(TUBA), A Simple Proposal for
Addressing and
This paper describes a simple proposal which provides a long-
solution to Internet addressing, routing, and scaling. This
provides information for the Internet community. It does not specify
Internet standard
1346 Jones Jun 92 Resource Allocation, Control,
Accounting for the Use of
The purpose of this RFC is to focus discussion on particular
in large service networks in general, and the International IP
in particular. No solution discussed in this document is intended as
standard. Rather, it is hoped that a general consensus will emerge
to the appropriate solutions, leading eventually to the adoption
standards. This memo provides information for the Internet community
It does not specify an Internet standard
1345 Simonsen Jun 92 Character Mnemonics & Character
This memo lists a selection of characters and their presence in
coded character sets. This memo provides information for the
community. It does not specify an Internet standard
1344 Borenstein Jun 92 Implicaitons of MIME for Internet
While MIME was carefully designed so that it does not require
changes to Internet electronic message transport facilities, there
several ways in which message transport systems may want to
advantage of MIME. These opportunities are the subject of this memo
This memo provides information for the Internet community. It does
specify an Internet standard
1343 Borenstein Jun 92 A User Agent Configuration
For Multimedia Mial Format
This memo suggests a file format to be used to inform multiple
reading user agent programs about the locally-installed facilities
handling mail in various formats. This memo provides information
the Internet community. It does not specify an Internet standard
Elliott Informational [Page 12]
RFC 1399 Summary of 1300-1399 January 1997
1342 Moore Jun 92 Representation of Non-ASCII Text
Internet Message
This memo describes an extension to the message format defined in [1]
(known to the IETF Mail Extensions Working Group as "RFC 1341"),
allow the representation of character sets other than ASCII in RFC 822
message headers. [STANDARDS-TRACK
1341 Borenstein Jun 92 MIME: Mechanisms for Specifying
Describing the Format of
Message
This document redefines the format of message bodies to allow multi-
textual and non-textual message bodies to be represented and
without loss of information. [STANDARDS-TRACK
1340 Reynolds Jul 92 ASSIGNED
This Network Working Group Request for Comments documents the
assigned values from several series of numbers used in network
implementations. This memo is a status report on the parameters (i.e.,
numbers and keywords) used in protocols in the Internet community
1339 Dorner Jun 92 Remote Mail Checking
This RFC defines a protocol to provide a mail checking service to
used between a client and server pair. Typically, a small program on
client workstation would use the protocol to query a server in order
find out whether new mail has arrived for a specified user. This
defines an Experimental Protocol for the Internet community
1338 Fuller Jun 92 Supernetting: an Address
and Aggregation
This memo discusses strategies for address assignment of the existing
address space with a view to conserve the address space and stem
explosive growth of routing tables in default-route-free routers run
transit routing domain providers. This memo provides information
the Internet community. It does not specify an Internet standard
Elliott Informational [Page 13]
RFC 1399 Summary of 1300-1399 January 1997
1337 Braden May 92 TIME-WAIT Assassination Hazards in
This note describes some theoretically-possible failure modes for
connections and discusses possible remedies. In particular, one
simple fix is identified. This memo provides information for
Internet community. It does not specify an Internet standard
1336 Malkin May 92 Who's Who in the
Biographies of IAB, IESG
IRSG
This FYI RFC contains biographical information about members of
Internet Activities Board (IAB), the Internet Engineering Steering
(IESG) of the Internet Engineering Task Force (IETF), and the
Internet Research Steering Group (IRSG) of the Internet Research
Force (IRTF). This memo provides information for the
community. It does not specify any standard
1335 Wang May 92 A Two-Tier Address Structure for
Internet: A Solution to the
of Address Space
This RFC presents a solution to problem of address space exhaustion
the Internet. It proposes a two-tier address structure for
Internet. This is an "idea" paper and discussion is
encouraged. This memo provides information for the Internet community
It does not specify an Internet standard
1334 Lloyd Oct 92 PPP Authentication
This document defines two protocols for Authentication: the
Authentication Protocol and the Challenge-Handshake
Protocol. [STANDARDS-TRACK
1333 Simpson May 92 PPP Link Quality
The Point-to-Point Protocol (PPP) [1] provides a standard method
encapsulating Network Layer protocol information over point-to-
links. PPP also defines an extensible Link Control Protocol,
allows negotiation of a Quality Protocol for continuous monitoring
the viability of the link. [STANDARDS-TRACK
Elliott Informational [Page 14]
RFC 1399 Summary of 1300-1399 January 1997
1332 McGregor May 92 The PPP Internet Protocol
Protocol (IPCP
The Point-to-Point Protocol (PPP) [1] provides a standard method
encapsulating Network Layer protocol information over point-to-
links. PPP also defines an extensible Link Control Protocol,
proposes a family of Network Control Protocols (NCPs) for
and configuring different network-layer protocols. [STANDARDS-TRACK
1331 Simpson May 92 The Point-to-Point Protocol (PPP
for the Transmission of Multi-
Datagrams over Point-to-Point
This document defines the PPP encapsulation scheme, together with
PPP Link Control Protocol (LCP), an extensible option
protocol which is able to negotiate a rich assortment of
parameters and provides additional management functions. [STANDARDS
TRACK
1330 E.S.C.C. May 92 Recommendations for the Phase
Deployment of OSI Directory
(X.500) and OSI Message
Services
This RFC is a near verbatim copy of the whitepaper produced by the
Site Coordinating Committee's X.500/X.400 Task Force. This
provides information for the Internet community. It does not specify
Internet standard
1329 Kuehn May 92 Thoughts on Address Resolution
Dual MAC FDDI
In this document an idea is submitted how IP and ARP can be used
inhomogeneous FDDI networks (FDDI networks with single MAC and dual
stations) by introducing a new protocol layer in the protocol suite
the dual MAC stations. This memo provides information for the
community. It does not specify an Internet standard
Elliott Informational [Page 15]
RFC 1399 Summary of 1300-1399 January 1997
1328 Kille May 92 X.400 1988 to 1984
This document considers issues of downgrading from X.400(1988)
X.400(1984) [MHS88a, MHS84]. Annexe B of X.419 specifies
downgrading rules [MHS88b], but these are not sufficient for
of service in an environment containing both 1984 and 1988 components
This document defines a number of extensions to this annexe
[STANDARDS-TRACK
1327 Kille May 92 Mapping between X.400(1988) /
10021 and RFC 822
This document specifies a mapping between two protocols.
specification should be used when this mapping is performed on the
Internet or in the UK Academic Community. This specification may
modified in the light of implementation experience, but no
changes are expected. [STANDARDS-TRACK
1326 Tsuchiya May 92 Mutual Encapsulation
This memo describes a packet explosion problem that can occur
mutual encapsulation of protocols (A encapsulates B and B
A). This memo provides information for the Internet community. It
not specify an Internet standard
1325 Malkin May 92 FYI on Questions and
Answers to Commonly asked "
Internet User"
This FYI RFC is one of two FYI's called, "Questions and Answers" (Q/A),
produced by the User Services Working Group of the Internet
Task Force (IETF). The goal is to document the most commonly
questions and answers in the Internet. This memo provides
for the Internet community. It does not specify an Internet standard
Elliott Informational [Page 16]
RFC 1399 Summary of 1300-1399 January 1997
1324 Reed May 92 A Discussion on Computer
This memo is intended to make more people aware of the
developments in the Computer Conferencing field as well as put
ideas on what should be done to formalize this work so that there is
common standard for programmers and others who are involved in
field to work with. This memo provides information for the
community. It does not specify an Internet standard
1323 Jacobson May 92 TCP Extensions for High
This memo presents a set of TCP extensions to improve performance
large bandwidth*delay product paths and to provide reliable
over very high-speed paths. It defines new TCP options for
windows and timestamps, which are designed to provide
interworking with TCP's that do not implement the extensions
[STANDARDS-TRACK
1322 Estrin May 92 A Unified Approach to Inter-
This memo is an informational RFC which outlines one potential
for inter-domain routing in future global internets. This memo
information for the Internet community. It does not specify an
standard
1321 Rivest Apr 92 The MD5 Message-Digest
This document describes the MD5 message-digest algorithm. The
takes as input a message of arbitrary length and produces as output
128-bit "fingerprint" or "message digest" of the input. This
provides information for the Internet community. It does not specify
Internet standard
1320 Rivest Apr 92 The MD4 Message-Digest
This document describes the MD4 message-digest algorithm [1].
algorithm takes as input a message of arbitrary length and produces
output a 128-bit "fingerprint" or "message digest" of the input.
memo provides information for the Internet community. It does
specify an Internet standard
Elliott Informational [Page 17]
RFC 1399 Summary of 1300-1399 January 1997
1319 Kaliski Apr 92 The MD2 Message-Digest
This document describes the MD2 message-digest algorithm. The
takes as input a message of arbitrary length and produces as output
128-bit "fingerprint" or "message digest" of the input. This
provides information for the Internet community. It does not specify
Internet standard
1318 Stewart Apr 92 Definitions of Managed
for Parallel-printer-like
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 the management of parallel-printer
like devices. [STANDARDS-TRACK
1317 Stewart Apr 92 Definitions of Managed Objects
RS-232-like Hardware
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 the management of RS-232-
devices. [STANDARDS-TRACK
1316 Stewart Apr 92 Definitions of Managed
for Character Stream
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 the management of character
devices. [STANDARDS-TRACK
1315 Brown Apr 92 Management Information Base for
Relay
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 Frame Relay. [STANDARDS
TRACK
Elliott Informational [Page 18]
RFC 1399 Summary of 1300-1399 January 1997
1314 Katz Apr 92 A File Format for the Exchange
Images in the
This document defines a standard file format for the exchange of fax
like black and white images within the Internet. [STANDARDS-TRACK
1313 Partridge Apr 92 Today's Programming for KRFC AM 1313
Internet Talk
Hi and welcome to KRFC Internet Talk Radio, your place on the AM
for lively talk and just-breaking news on internetworking. This
provides information for the Internet community. It does not specify
Internet standard
1312 Nelson Apr 92 Message Send Protocol 2
The Message Send Protocol is used to send a short message to a
user on a given terminal on a given host. This memo defines
Experimental Protocol for the Internet community
1311 Postel Mar 92 Introduction to the STD
The STDs are a subseries of notes within the RFC series that are
Internet standards. The intent is to identify clearly for the
community those RFCs which document Internet standards. [STANDARDS
TRACK
1310 I.A.B. Mar 92 The Internet Standards
This memo documents the process currently used for the
of Internet protocols and procedures. [STANDARDS-TRACK
1309 Weider Mar 92 Technical Overview of
Services Using the X.500
This document is an overview of the X.500 standard for people
familiar with the technology. It compares and contrasts
Services based on X.500 with several of the other Directory
currently in use in the Internet. This paper also describes the
of the standard and provides references for further information on X.500
implementations and technical information. This memo
information for the Internet community. It does not specify an
standard
Elliott Informational [Page 19]
RFC 1399 Summary of 1300-1399 January 1997
1308 Weider Mar 92 Executive Introduction to
Services Using the X.500
This document is an Executive Introduction to Directory Services
the X.500 protocol. It briefly discusses the deficiencies in
deployed Internet Directory Services, and then illustrates the
provided by X.500. This memo provides information for the
community. It does not specify an Internet standard
1307 Young Mar 92 Dynamically Switched Link
This memo describes an experimental protocol developed by a project
at Cray Research, Inc., in implementing support for circuit-switched T
services. The protocol is used for the control of network
external to a host, but known to the host. This memo defines
Experimental Protocol for the Internet community
1306 Nicholson Mar 92 Experiences Supporting By-
Circuit-Switched T3
This memo describes the experiences of a project team at Cray Research
Inc., in implementing support for circuit-switched T3 services.
the issues discussed may not be directly relevant to the
problems of the Internet, they may be interesting to a number
researchers and implementers. This RFC provides information for
Internet community. It does not specify an Internet standard
1305 Mills Mar 92 Network Time Protocol (Version 3):
Specification, Implementation
This document describes the Network Time Protocol (NTP), specifies
formal structure and summarizes information useful for
implementation. [STANDARDS-TRACK
1304 Cox Feb 92 Definitions of Managed Objects for
SIP 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 SIP (SMDS
Protocol) objects. [STANDARDS-TRACK
Elliott Informational [Page 20]
RFC 1399 Summary of 1300-1399 January 1997
1303 McCloghrie Feb 92 A Convention for Describing SNMP-
This memo suggests a straight-forward approach towards describing SNMP
based agents. This memo provides information for the
community. It does not specify an Internet standard
1302 Sitzler Feb 92 Building a Network
Services
This FYI RFC document is intended for existing Internet
Information Center (NIC) personnel, people interested in establishing
new NIC, Internet Network Operations Centers (NOCs), and
agencies interested in contributing to user support facilities.
memo provides information for the Internet community. It does
specify an Internet standard
1301 Armstrong Feb 92 Multicast Transport
This memo describes a protocol for reliable transport that utilizes
multicast capability of applicable lower layer networking architectures
The transport definition permits an arbitrary number of
providers to perform realtime collaborations without
networking clients (aka, applications) to possess detailed knowledge
the population or geographical dispersion of the participating members
It is not network architectural specific, but does implicitly
some form of multicasting (or broadcasting) at the data link level,
well as some means of communicating that capability up through
layers to the transport. This memo provides information for
Internet community. It does not specify an Internet standard
1300 Greenfield Feb 92 Remembrances of Things
Poem. This memo provides information for the Internet community.
does not specify an Internet standard
Elliott Informational [Page 21]
RFC 1399 Summary of 1300-1399 January 1997
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 22]
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
