DVMRP and MBGP

Current architecture:

• AS 10888 has presence at FIX-West, PAIX, and ???.
• FIXW-MBONE.NSN.NASA.GOV imports DVMRP routes into MBGP at FIX-West, sets their LOCAL_PREF to 0 and their COMMUNITY to 10888:668.
• FIXW-MBONE.NSN.NASA.GOV exports any MBGP route tagged with COMMUNITY 10888:777 into DVMRP at FIX-West.
• In order to allow any MBGP route to override an imported DVMRP route, all participating AS's should set the LOCAL_PREF of routes with COMMUNITY 10888:668 to 0.

Important rules to follow:

• You may export your own AS's routes into DVMRP. Suggest using a COMMUNITY of your-as:777 to tag the routes you are exporting yourself.
• Tag routes with COMMUNITY 10888:777 if you want FIXW-MBONE to export them into DVMRP. You may do both, e.g. by translating your-as:777 to 10888:777 at your border.
• You MUST NOT export any routes with COMMUNITY 10888:668 into DVMRP.
• You MUST NOT import any DVMRP routes into MBGP and pass them along (unless it is a stub DVMRP cloud disconnected from the global DVMRP cload).
• If you are importing your own DVMRP routes, you might want to filter out the DVMRP routes imported by FIXW-MBONE (by filtering out COMMUNITY 10888:668 at your border).
• Should joe-blow AS be allowed to export all routes with community 10888:777? How about an extended community list of [0-9]*:777? (is that how it works?)

need lots more here... config examples?

This material is based upon work supported by the National Science Foundation under Grant No. 9729498. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author and do not necessarily reflect the views of the National Science Foundation (NSF).