Changes incorporated in draft-ietf-ipcdn-pktc-eventmess-06.txt
"Sumanth Channabasappa" <[email protected]> Mon, 19 Jun 2006 13:55:26 -0600
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <[email protected]> |
Folks,
This is to inform you all that 'draft-ietf-ipcdn-pktc-eventmess-06.txt'
is now available
(http://www.ipcdn.org/drafts/draft-ietf-ipcdn-pktc-eventmess-06.txt).=20
The changes incorporated in this draft are enclosed in this email as an
FYI.
Regards
Sumanth
Note: Changes #1 and #7 are new. Remaining are mostly a repeat of the
changes suggested by Eugene in the email dated 3/29 to the IPCDN mailing
list. However, please verify all changes.
=20
Change #1/8:
---------
- Removed the MIB Object 'pktcDevEvReportingLevel'
=20
Reasoning: This MIB Object affected other MIB Objects and
the behavior when the affected MIB Objects and the MIB Object in=20
question were set in the same SNMP PDU resulted in complications.
=20
Further, attempts to handle such side-effects lead to non-trivial
requirements that would make for a complex MIB Object.
=20
Given that the advantage of this MIB Object was to make it easy to=20
set values across 'Event Classes' and was not required for the=20
MIB to operate, this 'nice-to-have' MIB Object has been removed.
=20
Further, this changes the index of 'pktcDevEventClassReportTable'
from 'pktcDevEventControl 6' to ' pktcDevEventControl 5'
=20
=20
Change #2/8: References
---------
=20
Added the following new references:
=20
- PacketCable(TM) Management Event Mechanism Specification
(PKT-SP-MEM1.5-I01-050128) - to be reffered to by the section 3 and some
MIB Objects
=20
- J. Postel, "User Datagram Protocol", STD0006, RFC 768 - to be refered
to by section 3.6.
=20
- C. Lonvick, "The BSD syslog Protocol", RFC 3164, August 2001 - to be
reffered to by some MIB Objects.
=20
=20
Updated the following references:
=20
- [PKT-SP-PROV], [PKT-SP-MGCP], [PKT-SP-CODEC] to reflect current
documents
=20
=20
=20
Change #3/8:
---------
Renamed the following MIB Objects to stay consistant in terminology with
RFC3164 ("BSD Syslog protocol"):
=20
pktcDevEvReportingLevel -> pktcDevEvSeverityLevel
=20
pktcDevEventClassReportLevel -> pktcDevEventClassSeverityLevel
=20
pktcDevEventDescrLevel -> pktcDevEventDescrSeverityLevel
=20
=20
Change #4/8:
---------
=20
Introduced new textual convention: SeverityLevel
=20
SeverityLevel - to simplify the syntax for pktcDevEvSeverityLevel,
pktcDevEventClassSeverityLevel, and pktcDevEventDescrSeverityLevel=20
=20
SeverityLevel ::=3D TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention represents the severity
levels for the various events reported by the MTA.
The levels are as described below:
emergency(0) - A condition that makes the system=20
unusable.
alert(1) - A service-affecting condition for which
immediate action must be taken.
critical(2) - A service-affecting critical condition.
error(3) - An error condition.
warning(4) - A warning condition.
notice(5) - A normal but significant condition.
info(6) - An informational message.
debug(7) - A debug message."
SYNTAX BITS {
emergency(0),
alert(1),
critical(2), =20
error(3), =20
warning(4), =20
notice(5),
info(6),
debug(7)=20
}
=20
=20
Change #5/8:
---------
The DESCRIPTION and/or SYNTAX clause of certain MIB Objects were
updated, as listed below:=20
=20
pktcDevEvControl: DECSRIPTION clause has been modified to clarify the
behavior of the MTA when resetEventLogTable(0) bit is set.=20
=20
DESCRIPTION =20
"This MIB object defines the actions related to the event=20
log configuration.=20
=20
The MTA MUST take the appropriate action whenever=20
a bit is set to a value of '1'.=20
=20
Setting the resetEventLogTable(0) bit to
a value of '1'
- deletes all entries in pktcDevEventLogTable,
- resets the value of pktcDevEvLogIndex to '0'
=20
Setting resetEventDescrTable(1) to a value of '1'
- resets the pktcDevEventDescrTable to the
factory default values.
=20
Setting a control bit to a value of '0' MUST not
result in any action.=20
=20
Reading this MIB object MUST always return '00'.
MTA MUST perform the same actions regardless of=20
persistentance (i.e. storage in non-volatile memory)."
=20
=20
=20
pktcDevEventClassReportEntry - DECSRIPTION modified to require a
'generic' event class when a vendor does not support multiple event
classes:
DESCRIPTION
"An entry in this table MUST be created for each=20
event class defined by a vendor for the events
described as part of 'pktcDevEventDescrTable'.
=20
If an MTA vendor does not define event classes,
then MTA MUST create one entry for the event=20
class 'generic'."
=20
=20
PktcDevEventClassReportEntry - modified to reflect the textual
conventions defined for: pktcDevEventClass and
pktcDevEventClassSeverityLevel:
=20
PktcDevEventClassReportEntry::=3D SEQUENCE {
pktcDevEventClass SnmpAdminString,
pktcDevEventReportStatus TruthValue,
pktcDevEventClassSeverityLevel SeverityLevel
} =20
=20
pktcDevEventClass:
- DESCRIPTION clause modified to clarify the usage:
=20
DESCRIPTION
"This MIB Object contains the identifier=20
of an event class supported by the device.
Vendors MAY define different event classes=20
(e.g. DHCP, SNMP, DEBUG) to group together=20
related events."
=20
PktcDevEventDescrEntry - modified to use new SYNTAX for two
objects: pktcDevEventDescrSeverityLevel and pktcDevEventDescrClass:
PktcDevEventDescrEntry::=3D SEQUENCE {
pktcDevEventDescrId Unsigned32,
pktcDevEventDescrEnterprise Unsigned32,
pktcDevEventDescrFacility INTEGER,
pktcDevEventDescrSeverityLevel SeverityLevel,
pktcDevEventDescrReporting BITS,
pktcDevEventDescrText SnmpAdminString,
pktcDevEventDescrClass SnmpAdminString
} =20
=20
=20
pktcDevEventDescrClass:
- MAX-ACCESS changed to "read-only" to avoid cross-reference
consistency complications with pktcDevEventClassReportTable.
=20
=20
pktcDevEventLogTable - the following added to the end of the DESCRIPTION
clause:
"The contents of this table MAY persist in non-volatile memory."
=20
pktcDevEvLogCorrelationId:=20
- the following clarification was added to the end of the =20
DECRIPTION clause:
"Although a Correlation-ID, once generated after MTA
reset, does not change until next MTA reset, the=20
value of this object will differ for the events=20
preserved across MTA resets in case of a persistent=20
pktcDevEventLogTable."
=20
- REFERENCE clause added:
REFERENCE
"PacketCable MTA Device Provisioning Specification,=20
[PKT-SP-PROV]."
=20
=20
pktcDevEvLogAdditionalInfo - the following clarification was added to
the DESCRIPTION clause:
"If MTA cannot provide any additional=20
information for the particular event generated, it MUST=20
populate this MIB Object with a string of zero-length."
=20
=20
Change #6/8:
---------
Updated references, as indicated to the following MIB Objects;
=20
=20
> REFERENCE
"RFC 3164, The BSD syslog Protocol, [RFC3164]."
=20
was added to:
=20
pktcDevEvLogTime, pktcDevEventClassSeverityLevel,
pktcDevEvSyslogAddress, pktcDevEvSyslogUdpPort, pktcDevEvSeverityLevel,
pktcDevEventDescrFacility, pktcDevEventDescrSeverityLevel
=20
=20
=20
> REFERENCE
"PacketCable MTA Device Provisioning Specification,=20
[PKT-SP-PROV]."
=20
added to:
=20
pktcDevEvSyslogAddressType, pktcDevEvSyslogAddress, pktcDevEventDescrId
=20
=20
> REFERENCE
"PacketCable MTA Device Provisioning Specification,=20
[PKT-SP-PROV];
added to:
=20
pktcDevEvSyslogAddress, pktcDevEventDescrId
=20
=20
> REFERENCE
"PacketCable Management Event Mechanism Specification,
[PKT-SP-MEM1.5];"
added to:
pktcDevEventDescrId=20
=20
=20
Change #7/8:=20
-----------=20
The size of the index 'pktcDevEventClass' and the MIB Object
'pktcDevEventDescrClass' was increased to 1..100 to allow for=20
descriptive event class names
=20
=20
Change #8/8: Misc. changes
---------
> Updated author's addresses
> Updated date/time
> Updated MIB details to align with the MTA and Sig drafts
> Removed 'NOT RECOMMENDED' from list of keywords
> Fixed non-ASCII characters present in the document
> Removed unused references ([RFC821], [RFC2026], [RFC1034], [RFC3550])
=20
=20
=20
=20
MIB compliation output from ' [email protected]':
------------------------------------------------------
=20
smilint -m -s -e -l 6 PKTC-IETF-EVENT-MIB
=20
PKTC-IETF-EVENT-MIB:71: [2] {bad-identifier-case} `XXX' should start
with a lower case letter
PKTC-IETF-EVENT-MIB:71: [2] {object-identifier-not-prefix} Object
identifier element `XXX' name only allowed as first element
=20
=20
ID-nits output from http://tools.ietf.org/tools/idnits/idnits.pyht:
------------------------------------------------------------------
=20
idnits 1.102=20
=20
tmp/draft-ietf-ipcdn-pktc-eventmess-06.txt:
=20
=20
Checking nits according to http://www.ietf.org/ID-Checklist.html:
=20
Checking conformance with RFC 3978/3979 boilerplate...
=20
the boilerplate looks good.
=20
No nits found.
=20
Checking nits according to
http://www.ietf.org/ietf/1id-guidelines.txt:
Nothing found here (but these checks do not cover all of
1id-guidelines.txt yet).
=20
Miscellaneous warnings:
None.
=20
Experimental warnings:
None.
=20
No nits found.
=20