One document matched: draft-ietf-rap-cops-client-mib-03.txt
Differences from draft-ietf-rap-cops-client-mib-02.txt
A new Request for Comments is now available in online RFC libraries.
RFC 2940
Title: Definitions of Managed Objects for Common Open
Policy Service (COPS) Protocol Clients
Author(s): A. Smith, D. Partain, J. Seligson
Status: Proposed Standard
Date: October 2000
Mailbox: ah_smith@pacbell.net,
David.Partain@ericsson.com,
jseligso@nortelnetworks.com,
Pages: 27
Characters: 52427
Updates/Obsoletes/SeeAlso: none
I-D Tag: draft-ietf-rap-cops-client-mib-03.txt
URL: ftp://ftp.isi.edu/in-notes/rfc2940.txt
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 a client of the Common
Open Policy Service (COPS) protocol.
This memo includes a MIB module in a manner that is compliant to the
SMIv2 [V2SMI].
This document is a product of the Resource Allocation Protocol Working
Group of the IETF.
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.| PAFTECH AB 2003-2026 | 2026-04-23 02:20:15 |