ietf-alarms-x733

Organization:

IETF CCAMP Working Group

Module:

ietf-alarms-x733

Version:

2019-09-11

File:

ietf-alarms-x733@2019-09-11.yang

Abstract:

This module augments the ietf-alarms module with X.733 alarm parameters. The following structures are augmented with the X.733 ...

Contact:

WG Web: <https://trac.ietf.org/trac/ccamp>
WG List: <mailto:ccamp@ietf.org>

Editor: Stefan Vallin
<mailto:stefan@wallan.se>

Editor: Martin Bjorklund
<mailto:mbj@tail-f.com>

Check for an additional details:

YANG Catalog

Description:

This module augments the ietf-alarms module with X.733 alarm
parameters.

The following structures are augmented with the X.733 event type
and probable cause:

1) alarms/alarm-inventory: all possible alarm types
2) alarms/alarm-list: every alarm in the system
3) alarm-notification: notifications indicating alarm-state
changes
4) alarms/shelved-alarms

The module also optionally allows the alarm-management system
to configure the mapping from the ietf-alarms' alarm keys
to the ITU tuple (event-type, probable-cause).

The mapping does not include a corresponding problem value
specific to X.733. The recommendation is to use the
'alarm-type-qualifier' leaf, which serves the same purpose.

The module uses an integer and a corresponding string for
probable cause instead of a globally defined enumeration, in
order to be able to manage conflicting enumeration definitions.
A single globally defined enumeration is challenging to
maintain.

The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL
NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED',
'MAY', and 'OPTIONAL' in this document are to be interpreted as
described in BCP 14 (RFC 2119) (RFC 8174) when, and only when,
they appear in all capitals, as shown here.

Copyright (c) 2019 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
(https://trustee.ietf.org/license-info).

This version of this YANG module is part of RFC 8632; see
the RFC itself for full legal notices.