rfc2299.txt

RFC 的详细文档！

Ramos                        Informational                      [Page 6]

RFC 2299                  Summary of 2200-2299              January 1999


2277    Alvestrand      Jan 1998        IETF Policy on Character Sets
                                        and Languages

This document is the current policies being applied by the Internet
Engineering Steering Group (IESG) towards the standardization efforts in
the Internet Engineering Task Force (IETF) in order to help Internet
protocols fulfill these requirements.  This document specifies an
Internet Best Current Practices for the Internet Community, and requests
discussion and suggestions for improvements.


2276    Sollins         Jan 1998        Architectural Principles of
                                        Uniform Resource Name Resolution

This document addresses the issues of the discovery of URN (Uniform
Resource Name) resolver services that in turn will directly translate
URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource
Characteristics).  This memo provides information for the Internet
community.  It does not specify an Internet standard of any kind.


2275    Wijnen          Jan 1998        View-based Access Control
                                        Model (VACM) for the
                                        Simple Network Management
                                        Protocol (SNMP)

This document describes the View-based Access Control Model for use in
the SNMP architecture [RFC2261].  It defines the Elements of Procedure
for controlling access to management information.  This document also
includes a MIB for remotely managing the configuration parameters for
the View-based Access Control Model.  [STANDARDS-TRACK]


2274    Blumenthal      Jan 1998        User-based Security Model
                                        (USM) for version 3 of the
                                        Simple Network Management
                                        Protocol (SNMPv3)

This document describes the User-based Security Model (USM) for SNMP
version 3 for use in the SNMP architecture [RFC2261].  It defines the
Elements of Procedure for providing SNMP message level security.  This
document also includes a MIB for remotely monitoring/managing the
configuration parameters for this Security Model.  [STANDARDS-TRACK]








Ramos                        Informational                      [Page 7]

RFC 2299                  Summary of 2200-2299              January 1999


2273    Levi            Jan 1998        SNMPv3 Applications

This memo describes five types of SNMP applications which make use of an
SNMP engine as described in [RFC2261].  The types of application
described are Command Generators, Command Responders, Notification
Originators, Notification Receivers, and Proxy Forwarders.  This memo
also defines MIB modules for specifying targets of management
operations, for notification filtering, and for proxy forwarding.
[STANDARDS-TRACK]


2272    Case            Jan 1998        Message Processing and
                                        Dispatching for the Simple
                                        Network Management Protocol
                                        (SNMP)

This document describes the Message Processing and Dispatching for SNMP
messages within the SNMP architecture [RFC2271].  It defines the
procedures for dispatching potentially multiple versions of SNMP
messages to the proper SNMP Message Processing Models, and for
dispatching PDUs to SNMP applications.  This document also describes one
Message Processing Model - the SNMPv3 Message Processing Model.
[STANDARDS-TRACK]


2271    Harrington      Jan 1998        An Architecture for Describing
                                        SNMP Management Frameworks

This document describes an architecture for describing SNMP Management
Frameworks.  The architecture is designed to be modular to allow the
evolution of the SNMP protocol standards over time.  [STANDARDS-TRACK]


2270    Stewart         Jan 1998        Using a Dedicated AS for Sites
                                        Homed to a Single Provider

With the increased growth of the Internet, the number of customers using
BGP4 has grown significantly. RFC1930 outlines a set of guidelines for
when one needs and should use an AS. However, the customer and service
provider (ISP) are left with a problem as a result of this in that while
there is no need for an allocated AS under the guidelines, certain
conditions make the use of BGP4 a very pragmatic and perhaps only way to
connect a customer homed to a single ISP.  This paper proposes a
solution to this problem in line with recommendations set forth in
RFC1930.  This memo provides information for the Internet community.  It
does not specify an Internet standard of any kind.





Ramos                        Informational                      [Page 8]

RFC 2299                  Summary of 2200-2299              January 1999


2269    Armitage        Jan 1998        Using the MARS Model in
                                        non-ATM NBMA Networks

This document is intended to state the obvious equivalences, and explain
the less obvious implications.  This memo provides information for the
Internet community.  It does not specify an Internet standard of any
kind.


2268    Rivest          Mar 1998        A Description of the RC2(r)
                                        Encryption Algorithm

This memo describes a conventional (secret-key) block encryption
algorithm, called RC2, which may be considered as a proposal for a DES
replacement.  This memo provides information for the Internet community.
It does not specify an Internet standard of any kind.


2267    Ferguson        Jan 1998        Network Ingress Filtering:
                                        Defeating Denial of Service
                                        Attacks which employ
                                        IP Source Address Spoofing

This paper discusses a simple, effective, and straightforward method for
using ingress traffic filtering to prohibit DoS attacks which use forged
IP addresses to be propagated from 'behind' an Internet Service
Provider's (ISP) aggregation point.  This memo provides information for
the Internet community.  It does not specify an Internet standard of any
kind.


2266    Flick           Jan 1998        Definitions of Managed Objects
                                        for IEEE 802.12 Repeater Devices

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 network repeaters based on
IEEE 802.12.  [STANDARDS-TRACK]













Ramos                        Informational                      [Page 9]

RFC 2299                  Summary of 2200-2299              January 1999


2265    Wijnen          Jan 1998        View-based Access Control
                                        Model (VACM) for the
                                        Simple Network Management
                                        Protocol (SNMP)

This document describes the View-based Access Control Model for use in
the SNMP architecture [RFC2261].  It defines the Elements of Procedure
for controlling access to management information.  This document also
includes a MIB for remotely managing the configuration parameters for
the View-based Access Control Model.  [STANDARDS-TRACK]


2264    Blumenthal      Jan 1998        User-based Security Model
                                        (USM) for version 3 of the
                                        Simple Network Management
                                        Protocol (SNMPv3)

This document describes the User-based Security Model (USM) for SNMP
version 3 for use in the SNMP architecture [RFC2261].  It defines the
Elements of Procedure for providing SNMP message level security.  This
document also includes a MIB for remotely monitoring/managing the
configuration parameters for this Security Model.  [STANDARDS-TRACK]


2263    Levi            Jan 1998        SNMPv3 Applications

This memo describes five types of SNMP applications which make use of an
SNMP engine as described in [RFC2261].  The types of application
described are Command Generators, Command Responders, Notification
Originators, Notification Receivers, and Proxy Forwarders.  This memo
also defines MIB modules for specifying targets of management
operations, for notification filtering, and for proxy forwarding.
[STANDARDS-TRACK]


2262    Case            Jan 1998        Message Processing and
                                        Dispatching for the Simple
                                        Network Management Protocol
                                        (SNMP)

This document describes the Message Processing and Dispatching for SNMP
messages within the SNMP architecture [RFC2261].  It defines the
procedures for dispatching potentially multiple versions of SNMP
messages to the proper SNMP Message Processing Models, and for
dispatching PDUs to SNMP applications.  This document also describes one
Message Processing Model - the SNMPv3 Message Processing Model.
[STANDARDS-TRACK]




Ramos                        Informational                     [Page 10]

RFC 2299                  Summary of 2200-2299              January 1999


2261    Harrington      Jan 1998        An Architecture for Describing
                                        SNMP Management Frameworks

This document describes an architecture for describing SNMP Management
Frameworks.  The architecture is designed to be modular to allow the
evolution of the SNMP protocol standards over time.  [STANDARDS-TRACK]


2260    Bates           Jan 1998        Scalable Support for
                                        Multi-homed Multi-provider
                                        Connectivity

This document describes addressing and routing strategies for multi-
homed enterprises attached to multiple Internet Service Providers (ISPs)
that are intended to reduce the routing overhead due to these
enterprises in the global Internet routing system.  This memo provides
information for the Internet community.  It does not specify an Internet
standard of any kind.


2259    Elliott         Jan 1998        Simple Nomenclator Query
                                        Protocol (SNQP)

The Simple Nomenclator Query Protocol (SNQP) allows a client to
communicate with a descriptive name service or other relational-style
query service.  This memo provides information for the Internet
community.  It does not specify an Internet standard of any kind


2258    Ordille         Jan 1998        Internet Nomenclator Project

The goal of the Internet Nomenclator Project is to integrate the
hundreds of publicly available CCSO servers from around the world.  This
document provides an overview of the Nomenclator system, describes how
to register a CCSO server in the Internet Nomenclator Project, and how
to use the Nomenclator search engine to find people on the Internet.
This memo provides information for the Internet community.  It does not
specify an Internet standard of any kind.


2257    Daniele         Jan 1998        Agent Extensibility (AgentX)
                                        Protocol Version 1

This memo defines a standardized framework for extensible SNMP agents.
It defines processing entities called master agents and subagents, a
protocol (AgentX) used to communicate between them, and the elements of
procedure by which the extensible agent processes SNMP protocol
messages.  [STANDARDS-TRACK]



Ramos                        Informational                     [Page 11]

RFC 2299                  Summary of 2200-2299              January 1999


2256    Wahl            Dec 1997        A Summary of the X.500(96)
                                          User Schema for use with LDAPv3

This document provides an overview of the attribute types and object
classes defined by the ISO and ITU-T committees in the X.500 documents,
in particular those intended for use by directory clients.  [STANDARDS-
TRACK]


2255    Howes           Dec 1997        The LDAP URL Format

This document describes a format for an LDAP Uniform Resource Locator.
[STANDARDS-TRACK]


2254    Howes           Dec 1997        The String Representation of
                                        LDAP Search Filters

This document defines a human-readable string format for representing
LDAP search filters.  [STANDARDS-TRACK]


2253    Wahl            Dec 1997        Lightweight Directory Access
                                        Protocol (v3): UTF-8 String
                                        Representation of
                                        Distinguished Names

This specification defines the string format for representing names,
which is designed to give a clean representation of commonly used
distinguished names, while being able to represent any distinguished
name.  [STANDARDS-TRACK]


2252    Wahl            Dec 1997        Lightweight Directory Access
                                        Protocol (v3): Attribute
                                        Syntax Definitions

This document defines a set of syntaxes for LDAPv3, and the rules by
which attribute values of these syntaxes are represented as octet
strings for transmission in the LDAP protocol.  [STANDARDS-TRACK]











Ramos                        Informational                     [Page 12]