draft-ietf-pint-mib-01.txt | draft-ietf-pint-mib-02.txt | |||
---|---|---|---|---|
PINT Working Group Murali Krishnaswamy | PINT Working Group Murali Krishnaswamy | |||
Internet Draft Dan Romascanu | Internet Draft Dan Romascanu | |||
Lucent Technologies | Lucent Technologies | |||
Management Information Base for the PINT Services Architecture | Management Information Base for the PINT Services Architecture | |||
<draft-ietf-pint-mib-01.txt> | <draft-ietf-pint-mib-02.txt> | |||
Abstract | Abstract | |||
This memo describes a proposed MIB for the PINT Services | This memo describes a proposed MIB for the PINT Services | |||
Architecture. | Architecture. | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
all provisions of Section 10 of RFC 2026. Internet-Drafts are working | all provisions of Section 10 of RFC 2026. Internet-Drafts are working | |||
skipping to change at page 18, line 21 | skipping to change at page 18, line 21 | |||
features as provided by the SNMPv3 framework. Specifically, the use | features as provided by the SNMPv3 framework. Specifically, the use | |||
of the User-based Security Model RFC 2574 [13] and the View- based | of the User-based Security Model RFC 2574 [13] and the View- based | |||
Access Control Model RFC 2575 [16] is recommended. | Access Control Model RFC 2575 [16] is recommended. | |||
It is then a customer/user responsibility to ensure that the SNMP | It is then a customer/user responsibility to ensure that the SNMP | |||
entity giving access to an instance of this MIB, is properly config- | entity giving access to an instance of this MIB, is properly config- | |||
ured to give access to the objects only to those principals (users) | ured to give access to the objects only to those principals (users) | |||
that have legitimate rights to indeed GET or SET | that have legitimate rights to indeed GET or SET | |||
(change/create/delete) them. | (change/create/delete) them. | |||
8. References | 8. IANA Considerations | |||
All extensions to the values listed in this MIB must be done through | ||||
Standards Action processes as defined in RFC 2434 [21]. | ||||
9. References | ||||
[1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- | [1] H.Lu, et. al, "Toward the PSTN/Internet Inter-Networking --Pre- | |||
PINT Implementations", RFC 2458, November 1998. | PINT Implementations", RFC 2458, November 1998. | |||
[2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for | [2] Wijnen, B., Harrington, D., and Presuhn, R., "An Architecture for | |||
Describing SNMP Management Frameworks", RFC 2571, April 1999. | Describing SNMP Management Frameworks", RFC 2571, April 1999. | |||
[3] Rose, M. and McCloghrie, K., "Structure and Identification of | [3] Rose, M. and McCloghrie, K., "Structure and Identification of | |||
Management Information for TCP/IP-based Internets", RFC 1155, May | Management Information for TCP/IP-based Internets", RFC 1155, May | |||
1990. | 1990. | |||
skipping to change at page 19, line 45 | skipping to change at page 20, line 5 | |||
[18] S. Petrack, L. Conroy, "The PINT Service Protocol: Extensions to | [18] S. Petrack, L. Conroy, "The PINT Service Protocol: Extensions to | |||
SIP and SDP for IP Access to Telephone Call Services", draft- | SIP and SDP for IP Access to Telephone Call Services", draft- | |||
ietf-pint-protocol-01.txt, 14 July 1999. | ietf-pint-protocol-01.txt, 14 July 1999. | |||
[19] C. Krupczak, J. Saperia, "Definitions of System-Level Managed | [19] C. Krupczak, J. Saperia, "Definitions of System-Level Managed | |||
Objects for Applications", RFC 2287, February 1998. | Objects for Applications", RFC 2287, February 1998. | |||
[20] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for | [20] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for | |||
Describing SNMP Management Frameworks", RFC 2271, January 1998. | Describing SNMP Management Frameworks", RFC 2271, January 1998. | |||
9. Authors' Addresses | [21] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA | |||
Considerations Section in RFCs", RFC 2434, October 1998. | ||||
10. Authors' Addresses | ||||
Murali Krishnaswamy | Murali Krishnaswamy | |||
Lucent Technologies | Lucent Technologies | |||
3C-512, 101 Crawfords Corner Rd. | 3C-512, 101 Crawfords Corner Rd. | |||
Holmdel, NJ 07733 | Holmdel, NJ 07733 | |||
Tel: +1 (732)949-3611 | Tel: +1 (732)949-3611 | |||
Fax: +1 (732)949-3210 | Fax: +1 (732)949-3210 | |||
E-mail: murali@lucent.com | E-mail: murali@lucent.com | |||
Dan Romascanu | Dan Romascanu | |||
End of changes. 3 change blocks. | ||||
3 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |