Hi Glenn thanks for this draft, can I suggest NEMO (NEtwork MObility)
related MIB entries to the MIP6-MIB?
As you may already know, the NEMO WG went through designing and spec of
enhancing MN to act not only as a Mobile Host but also as a Router - a
Mobile Router. This was done by extending Mobile IPv6 BU-BAck exchanges
featuring a new 'R' router bit in BU, DHAAD Req/Rep, HA Info Option, new
BAck Status Codes, two modes of operation (Explicit/Implicit, saying how
the moving network prefix is communicated). There are no new messages
or new Mobility Headers created by NEMO with respect to MIP6.
Current NEMO base draft is at
http://tinyurl.com/5mgs5 and a slightly prior version went through IESG
and currently queued for publishing as RFC.
It is very useful to have NEMO-related info integrated into the MIP6-MIB
(and not into an OSPF MIP or other routing MIB) since NEMO base is
mostly MIP6.
Glenn Mansfield Keeni wrote:
Hi, A new version of the MIP6-MIB draft is available in the archives.
Let us have your comments. The type of comments that we are looking
for are, - I want to monitor XXX ( it is useful ) but there is no way
it can be done with the present MIB module
I want to monitor on the HA the fact that the MN with which it has a
binding relationship is, in fact, a router.
I want to monitor on the HA the fact that the MN who sent _this_ DHAAD
Request is a router.
I want to monitor on the HA and MR the mode of operation of this binding
- is it Implicit or Explicit.
I want to monitor on the MR the BAck replies from the HA with values
140, 141, 142 or 143.
- I want to control YYY ( set it on or off ) but there is no way it
can be done with the present MIB module
I want to control the NEMO "Mode" of operation on the MR to switch
between "Implicit" to "Explicit". I think currently the MIP6-MIB is
only for HA and CN, so I'd like it on MR too.
- I want to be informed about events ZZZ asynchronously, this is not
defined in the present MIB module - The decription of objects ABC is
unclear. - I want to have an implementation that will only have
feature A, B and C but there is no such COMPLIANCE defined for that
in the MIB module. - The security implications of object ABC is
absent/incorrect/ incomplete. - XYZ is unclear - editorial nits
Nit: use Home Address instead of home address and Home Agent instead of
Home Agent (capitalize) in the running text everywhere.
Thanks,
Alex
signature.asc
Description: OpenPGP digital signature
_______________________________________________
Mip6 mailing list
Mip6@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/mip6
| 
