Re: A few comments on the Midcom MIB-00

Martin Stiemerling <[email protected]>
Newsgroups gmane.ietf.midcom
Message-ID <[email protected]>
Hi Sharon,

Thanks for the first comments. For the remaining part of the document I 
recommend to really wait for the upcoming version.

|
| 1. In the Overview section, how do the managed objects described in the
| third paragraph relate to the solution described in the second paragraph?
| This connection has not been made.

Actually I'm not sure to what you refer. Could please cite the paragraphs 
by email?

|
| 2. In section 3.1, on Terminology, it would be good to tell us what
| RFCXXXX is. Right now I have no idea what document you are referring to,
| but even after it is published, I think including the title of the RFC
| would greatly increase readability.

See Section 11 References: RFCXXX is the MIDCOM semantics document that is 
currently in IESG review.

|
| 3. In section 3.1 in Terminology, it might be worth noting that the latest
| terminology in SNMP is 'SNMP entity' and using this should clarify things
| for you. See section 2.1 in RFC3410. You could then indicate that the
| Midcom SNMP Entity acts in both the manager and agent roles, or something
| along those lines.

We have actually chosen (after long discussions) MIDCOM client for 
clarification. I feel that this brings it to the point, but MIDCOM SNMP 
entity will confuse readers even more (considering that they like more 
MIDCOM-folks)

|
| 4. In section 4, the first paragraph, I might suggest something more along
| the lines of "This memo describes a method of using managing Midcom in
| SNMP and also provides the necessary MIB objects to support this method."
|

Why do you think it is not appropriate? I have problems to follow your 
suggestion "...using managing Midcom in SNMP". This sounds rather confusing 
for me.
Here is the original excerpt:
"In order to realize middlebox communication as described in RFC XXXX,
several aspects and properties of the MIDCOM protocol need to be
mapped to SNMP capabilities and expressed in terms of the Structure
of Management Information version 2 (SMIv2)."

  Martin

|
| Sharon Chisholm
| Portfolio Integration
| Nortel Networks
| Ottawa, Canada
|
| _______________________________________________
| midcom mailing list
| [email protected]
| https://www1.ietf.org/mailman/listinfo/midcom
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.