UUID-TC-MIB
- Registered at
- 1.3.6.1.2.1.217
- Last updated
- 2013-04-05 00:00
- Organization
- IETF Energy Management Working Group
- Revisions
- 2013-04-05 00:00
- Namespace
- standard
- Source file
UUID-TC-MIB- Digest
sha256:7c3d21529995d35eed3d3996e3c719185013850a563ddc640547e3281acfe397
Description
This MIB module defines TEXTUAL-CONVENTIONs representing Universally Unique IDentifiers (UUIDs). Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
Contact
WG Email: eman@ietf.org Mailing list subscription info: http://www.ietf.org/mailman/listinfo/eman Dan Romascanu Avaya Park Atidim, Bldg. #3 Tel Aviv, 61581 Israel Phone: +972-3-6458414 Email: dromasca@avaya.com Juergen Quittek NEC Europe Ltd. Network Research Division Kurfuersten-Anlage 36 Heidelberg 69115 Germany Phone: +49 6221 4342-115 Email: quittek@neclab.eu Mouli Chandramouli Cisco Systems, Inc. Sarjapur Outer Ring Road Bangalore 560103 India Phone: +91 80 4429 2409 Email: moulchan@cisco.com
Imports
| From | Symbols |
|---|---|
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP |
| SNMPv2-SMI | MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso, mib-2 |
| SNMPv2-TC | DisplayString, TEXTUAL-CONVENTION |
Imported by
3 module(s) in this corpus import this one.
Load order
Every file a consumer needs in order to load this module, dependencies first.
SNMPv2-CONF SNMPv2-SMI SNMPv2-TC UUID-TC-MIB
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| UUID TEXTUAL-CONVENTION Universally Unique Identifier information. The syntax must conform to RFC 4122, Section 4.1. | current | |||
| UUIDorZero TEXTUAL-CONVENTION Universally Unique Identifier information. The syntax must conform to RFC 4122, Section 4.1. The semantics of the value zero-length OCTET STRING are object-specific and must therefore be defined as part of the description of any object that uses this syntax. | current |