mboned: Closing the MSDP WG

David Meyer <dmm <at> 1-4-5.net>
2004-01-14 23:34:44 GMT

Alex/Bill,
The MSDP WG has concluded its work on the MSDP spec (the
MSDP MIB will be finished in the MBONED WG). As such, I'm
requesting that you close the MSDP WG.
I want to thank all of you who worked on MSDP for your
hard work, attention to detail, and perseverance. Well
done all.
Thanks,
Dave
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive: http://darkwing.uoregon.edu/~llynch/mboned/

mboned: MSDP MIB

David Meyer <dmm <at> 1-4-5.net>
2003-12-17 15:43:17 GMT

Folks,
In our never-ending quest to close the MSDP working
group, we've come up against the question of what to do
with the MSDP MIB (in particular, where to finish
it). The current thinking is to close the MSDP WG and
finish the MIB in MBONED.
Please speak up now if you have issues or concerns about
this approach.
Thanks,
Dave
_______________________________________________________________
user interface: http://darkwing.uoregon.edu/~llynch/mboned.html
web archive: http://darkwing.uoregon.edu/~llynch/mboned/

mboned: Multicast Source Discovery Protocol (MSDP) - RFC 3618

David Meyer <dmm <at> 1-4-5.net>
2003-10-17 20:36:59 GMT

Since RFC 3618 is about to be published, I wanted to
thank all of you for the hard and thoughful work you have
done in getting MSDP to this point.
Congratulations all on sticking with this and on work
well done.
Dave
__________________________________________________________
web archive: http://darkwing.uoregon.edu/~llynch/mboned/

MSDP implementations

Dear all,
I'm interested in multicast routing protocols, and I've just started to investigate MSDP.
Let me ask a quick question. Are there any implementations of MSDP?
I appreciate your any feedback.
Thank you
Hidetoshi Ueno
NTT DoCoMo, Inc.

MSDP MIB questions

Bill Fenner <fenner <at> research.att.com>
2003-06-11 02:18:33 GMT

A couple of brief MSDP MIB questions:
1. Has anyone implemented the draft -06 or -07 (or, for that matter,
any version)? I'm curious if renumbering the OIDs would affect
anyone.
2. In the Requests table, does it make sense for longest-match to
happen first, or highest priority first?
3. I'm planning to delete msdpPeerEncapsulationType,
msdpPeerInNotifications, msdpPeerOutNotifications, msdpPeerLastError
to reflect evolution of the MSDP spec. Can anyone think of any other
changes relevant to the structure of the MIB?
Thanks,
Bill

MSDP MIB

Bill Fenner <fenner <at> research.att.com>
2003-06-04 05:59:36 GMT

I just republished the MSDP MIB. Since MSDP is now approved, let's get
this finished up to go with it. Here are the open issues from the
draft. Some of them are irrelevant now since they applied to pieces
that we removed to get to the current version. Comments are welcome.
--
We need Components to describe multiple instances of MSDP in the same
box (similar to the PIM MIB)
Need a static RPF-peer table (see spec, section 14.3)
Do we need an msdpPeerLastErrorSent, too, for what notification I last
sent to this peer?
The Backwards Transition notification won't trigger on established ->
disabled. Is that desired?
A table to express policy was suggested on the MSDP mailing list. More
discussion is required before including this in the MIB. (Some of the
more discussion: other than filtering announcements at an RP, policy in
MSDP == black holes; policy should be in MBGP)
An OID for control of encapsulation (e.g. SA-encapsulate the first N
packets sent to this group?) was suggested, although it might be more
appropriate to be a table for fine-grained control.
Is the RowStatus object in the SACache appropriate? (e.g. used to flush
potentially bad state)

[MSDP] MSDP approved for Experimental by the IESG

David Meyer <dmm <at> 1-4-5.net>
2003-05-29 17:30:02 GMT

Folks,
MSDP was approved for Experimental by the IESG.
Congratulations to all for the hard work. We still have
the MIB to work on, and Bill has just refreshed that
draft.
I don't plan to have MSDP meet in Vienna; rather, we'll
handle any issues in MBONED (and I'll cross post to both
lists).
Again, congratulations to all on the hard work and
perseverance. It only took 4 years longer than we though
it might
Dave