NEW MIDCOM MIB I-D draft-ietf-midcom-mib-03.txt

Martin Stiemerling <[email protected]> Thu, 28 Oct 2004 11:04:18 +0200
Newsgroups gmane.ietf.midcom
Message-ID <A919021454C3872D96354E04@[10.1.1.109]>
Hi,

A new version of the MIDCOM MIB has been submitted on Monday to the I-D 
repository. Some information ahead, while waiting for the I-D announcement 
to come.

The new version implements a change requested during the last IETF meeting 
with respect to the MIDCOM session and notification messages.  The -02 
version (and all before) have implemented in midcomSessionTable one 
conceptual row for each MIDCOM client with a session, even if there are 
multiple clients sharing the same identity.  The upcoming -03 version has 
only one conceptual row per client identity and uses the TARGET-MIB to 
select which MIDCOM client will receive notifications (which is the 
remaining idea of a MIDCOM session).

This version of the MIDCOM MIB has been submitted without reaching a full 
consensus amongst the authors.  The issues where we could not reach 
consensus are:

1. Figure 7 & the use of right internal/external terminology in PRR & PER
transactions(sections 6.4 through 6.6)

2. Is asynchronous notification a requirement to complete transaction such 
as PRR, PER & TLC?

3. Wes suggested the use of target MIB & notification MIB as a means to 
replace midcomSession with.  A proposal to this is implemented in the MIB.

4. Miscellaneous issues for operational considerations:
   - Conflicting MIDCOM rules that impact same middlebox resources - both
     firewall & NAT resources, implementation recommendations.
   - Idempotency impact on rule lifetime

Please read it and give us comments.  A copy of the new draft is accessible 
here:
ftp://ftp.netlab.nec.de/pub/internet-drafts/draft-ietf-midcom-mib-03.txt

Thank you!

  Martin