[c-nsp] VRF RD/RT... your preferences?

[Jeff Kell]

The recent discussion of VRFs, RDs, RTs, VPNv4 labels, etc was
interesting, and starting to sink in.

I've been in early stages of a VRF-lite deployment for some time. 
Admittedly, from a VRF-lite perspective, a lot of the configuration is
essentially cut-and-paste, and most of the values you can just make up
as you go along as long as you're consistent.  I'm guilty as charged
:-)  We have essentially one PE, multiple CEs, and no real MPLS going on
anywhere; just VRF-lite and dot1q trunks/dedicated vlans to connect them
together.

However... one never knows what the future holds, and if the current
economic crisis doesn't get us all, we might actually have multiple PEs
and/or real MPLS one of these days.

If that happens, I would prefer not to have to renumber/relabel/etc
everything in a fit of  "If I had only known better..." musings under my
breath.

With that said... what should REALLY be used for RDs / RTs?

I'm currently using "ASN:vlan-id" for RTs, this identifies our ASN and
the vlan ID used in the VRF-lite trunk mesh to carry the VRF into the CEs.

I am using the same label for RD at the moment, but I noticed in an
earlier discussion that the RD should be unique across the net (where in
my case it's common).

Should the RD reference the router IP?  The global VRF loopback, or an
interface address within the VRF?

If I get a request to run an MPLS link out to a new research station
halfway across the country, will this numbering scheme fit into an MPLS
carrier's scheme?

Jeff