Re: comments on draft-ietf-sming-reqs-03.txt

[Frank Strauss <strauss@ibr.cs.tu-bs.de>]

Hi!

js> I do not understand your arguing about the SMIng syntax in the context
js> of the SMIng requirements document. Requirements 4.1.3 and 4.1.4 say
js> that the syntax has to be human friendly and machine friendly. I hope
js> we all agree with that.

Jeff> i am not arguing about anything ... frank is trying to get me to argue
Jeff> again, i respectfully decline

Jeff, I got the impression that I (and Juergen probably too) used the
wrong term to beg you to give not just plain statements, but also
reasons and arguments why you think so. It was not my intention to ask
for a verbal fight. I'm sorry for this mistake.

>> If you want to discuss the pros and cons of the syntax in the current
>> SMIng specification, then that is fine with me. But let us do that in
>> a separate thread since I fail to see how such a discussion is related
>> to the requirements document currently under last call.

Jeff> the reason the two are linked is because draft-ietf-sming-req-03.txt
Jeff> links them on the bottom of page 4, the top of page 5, and throughout
Jeff> section 4 of the document

I cannot find any text passage near page 4 and 5 that talks about the
syntax in the current SMING specification proposal and I'm quite sure
that there's also none in Section 4. But maybe, I missed them. Please
quote them, so that we can remove or change these passages, since they
would not fit into the requirements document.

Jeff> furthermore, the requirements document adopts the nomenclature of
Jeff> the current nmrg proposals ... such as the renaming of notifications
Jeff> to events ... which i am sure you will recall discussing with me

Jeff> recall the seattle interim meeting:
Jeff> 	you said "what is another name non-objectionable name for event?"
Jeff> 	i said "we don't need another name for event -- we already call it 
Jeff> 	notification and can continue to do so ..."

AFAIR, we also explained that we regard 

  - an event as `something that happens', thus independent from any
    encoding and protocol and used only in the protocol independent
    parts, and
  
  - a notification as the data structure used in the SNMP mapping since
    this is the term used for SNMP.


 -frank