[Disman] draft-ietf-disman-event-mib-v2-06.txt: Issue-1 -> "MAY not"

[Benoit Claise <[e-mail]>]

Dear all,

As pointed it out by Dave Shield in 
http://www1.ietf.org/mail-archive/web/disman/current/msg00648.html, one 
of the remaining issues in the draft is:

Another question:
   In a couple of places in this draft (mteObjectEntryStatus,
mteEventEntryStatus, etc), the description refers to the term
"MAY not".  What does this actually mean?

RFC 2119 defines "MAY" as referring to optional features,
and makes no mention of "MAY not".  Is this intended to be
a prohibition on making any changes to an active row?

If so:
  a)  Shouldn't the text use  "MUST NOT" ?
  b)  What's the purpose of the mteEventEnabled column
        if the value can't be changed?
  c)  What is the reason for this prohibition?

Specifically, we speak about:

mteObjectsEntryStatus OBJECT-TYPE 
    SYNTAX      RowStatus 
    MAX-ACCESS  read-create 
    STATUS      current 
    DESCRIPTION 
        "The control that allows creation and deletion of entries. 
        Once made active an entry MAY not be modified except to 
        delete it." 
    ::= { mteObjectsEntry 5 } 

mteEventEntryStatus OBJECT-TYPE 
    SYNTAX      RowStatus 
    MAX-ACCESS  read-create 
    STATUS      current 
    DESCRIPTION 
        "The control that allows creation and deletion of entries. 
        Once made active an entry MAY not be modified except to 
        modify the value of mteEventEnabled or to delete the entry." 
    ::= { mteEventEntry 5 } 

I share Dave's concern. It seems to me that MUST NOT is more appropriate in those two cases.

Feedback?

Regards, Benoit.