draft-ietf-bfd-tc-mib-06.txt   draft-ietf-bfd-tc-mib-07.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet-Draft Brocade Internet-Draft Brocade
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: October 31, 2014 N. Akiya Expires: November 1, 2014 N. Akiya
Cisco Systems Cisco Systems
April 29, 2014 April 30, 2014
Definitions of Textual Conventions (TCs) for Definitions of Textual Conventions (TCs) for
Bidirectional Forwarding Detection (BFD) Management Bidirectional Forwarding Detection (BFD) Management
draft-ietf-bfd-tc-mib-06 draft-ietf-bfd-tc-mib-07
Abstract Abstract
This draft defines two Management Information Base (MIB) modules that This draft defines two Management Information Base (MIB) modules that
contain Textual Conventions to represent commonly used Bidirectional contain Textual Conventions to represent commonly used Bidirectional
Forwarding Detection (BFD) management information. The intent is Forwarding Detection (BFD) management information. The intent is
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD
related MIB modules that would otherwise define their own related MIB modules that would otherwise define their own
representations. representations.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 31, 2014. This Internet-Draft will expire on November 1, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 10, line 6 skipping to change at page 10, line 6
END END
4. Security Considerations 4. Security Considerations
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other BFD defines a set of textual conventions which may be used by other BFD
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has modules that define management objects. Therefore, this document
no impact on the security of the Internet. does not introduce any additional security considerations.
5. IANA Considerations 5. IANA Considerations
This document provides the base definition of the IANA-BFD-TC-STD-MIB This document provides the base definition of the IANA-BFD-TC-STD-MIB
module. This MIB module is under the direct control of IANA. Please module. This MIB module is under the direct control of IANA. Please
see the most updated version of this MIB at <http://www.iana.org/ see the most updated version of this MIB at <http://www.iana.org/
assignments/bfdtc-mib>. [RFC-Editor's Note (to be removed prior to assignments/bfdtc-mib>. [RFC-Editor's Note (to be removed prior to
publication): the IANA is requested to create page pointed to by publication): the IANA is requested to create page pointed to by
URL.] Assignments of IANA-BFD-TC-STD-MIB are via IETF Review URL.] Assignments of IANA-BFD-TC-STD-MIB are via IETF Review
[RFC5226]. [RFC5226].
skipping to change at page 10, line 43 skipping to change at page 10, line 43
prior to publication): the IANA is requested to assign a value for prior to publication): the IANA is requested to assign a value for
"YYY" under the 'mib-2' subtree and to record the assignment in the "YYY" under the 'mib-2' subtree and to record the assignment in the
SMI Numbers registry. When the assignment has been made, the RFC SMI Numbers registry. When the assignment has been made, the RFC
Editor is asked to replace "YYY" (here and in the MIB module) with Editor is asked to replace "YYY" (here and in the MIB module) with
the assigned value and to remove this note.] the assigned value and to remove this note.]
6. Acknowledgments 6. Acknowledgments
Authors would like to thank Adrian Farrel and Jeffrey Haas for Authors would like to thank Adrian Farrel and Jeffrey Haas for
performing thorough reviews and providing number of suggestions. performing thorough reviews and providing number of suggestions.
Authors would also like to thank David Ward for his comments and Authors would also like to thank David Ward and Christer Holmberg for
suggestions. his comments and suggestions.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
 End of changes. 6 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/