1UUID-TC-MIB DEFINITIONS ::= BEGIN 2 3 IMPORTS 4 MODULE-IDENTITY, mib-2 5 FROM SNMPv2-SMI -- RFC 2578 6 TEXTUAL-CONVENTION 7 FROM SNMPv2-TC -- RFC 2579 8 ; 9 10 uuidTCMIB MODULE-IDENTITY 11 12 LAST-UPDATED "201304050000Z" -- April 5, 2013 13 ORGANIZATION "IETF Energy Management Working Group" 14 CONTACT-INFO "WG Email: eman@ietf.org 15 Mailing list subscription info: 16 http://www.ietf.org/mailman/listinfo/eman 17 18 Dan Romascanu 19 Avaya 20 Park Atidim, Bldg. #3 21 Tel Aviv, 61581 22 Israel 23 Phone: +972-3-6458414 24 Email: dromasca@avaya.com 25 26 Juergen Quittek 27 NEC Europe Ltd. 28 Network Research Division 29 Kurfuersten-Anlage 36 30 Heidelberg 69115 31 Germany 32 Phone: +49 6221 4342-115 33 Email: quittek@neclab.eu 34 35 Mouli Chandramouli 36 Cisco Systems, Inc. 37 Sarjapur Outer Ring Road 38 Bangalore 560103 39 India 40 Phone: +91 80 4429 2409 41 Email: moulchan@cisco.com" 42 DESCRIPTION 43 "This MIB module defines TEXTUAL-CONVENTIONs 44 representing Universally Unique IDentifiers 45 (UUIDs). 46 47 Copyright (c) 2013 IETF Trust and the persons 48 identified as authors of the code. All rights 49 reserved. 50 51 Redistribution and use in source and binary forms, 52 with or without modification, is permitted 53 pursuant to, and subject to the license terms 54 contained in, the Simplified BSD License set forth 55 in Section 4.c of the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info)." 58 59 REVISION "201304050000Z" -- April 5, 2013 60 DESCRIPTION "Initial version of this MIB as published in 61 RFC 6933." 62 ::= { mib-2 217 } 63 64 -- Textual Conventions 65 66UUID ::= TEXTUAL-CONVENTION 67 DISPLAY-HINT "4x-2x-2x-1x1x-6x" 68 STATUS current 69 DESCRIPTION 70 "Universally Unique Identifier information. The syntax must 71 conform to RFC 4122, Section 4.1." 72 SYNTAX OCTET STRING (SIZE (16)) 73 74UUIDorZero ::= TEXTUAL-CONVENTION 75 DISPLAY-HINT "4x-2x-2x-1x1x-6x" 76 STATUS current 77 DESCRIPTION 78 "Universally Unique Identifier information. The syntax must 79 conform to RFC 4122, Section 4.1. 80 81 The semantics of the value zero-length OCTET STRING are 82 object-specific and must therefore be defined as part of 83 the description of any object that uses this syntax." 84 SYNTAX OCTET STRING (SIZE (0|16)) 85 86END 87