Prefix attribute

I have a couple issues with the Prefix Attribute.

1) I have concerns regarding the Prefix attribute being conditionally
mandatory.

It is logical from a route advertisement standpoint to express a list of
prefixes along with ReachableRoutes containing the TrunkGroup and/or Carrier
address family.  If we use Carrier or TrunkGroup families inside
ReachableRoutes to change statistics (i.e. AvailableCircuits), we then need
to list all Prefixes for a Carrier/TrunkGroup plus other mandatory
attributes each time statistics are sent. This may be a fair amount of
"worthless" data sent for each message, especially if the TrunkGroup or
Carrier contains many prefixes.  More importantly, the LS that receives the
message needs to check the entire Prefix list because it may change--it
seems like a lot of overhead to update statistics.

2) Do the address families in the Prefix attribute need to be negotiated in
the Open exchange?

If not, the GW has a "backdoor" to insert routes with any address family!
The GW may send TrunkGroup routes with POTS prefixes, and the LS may only
want, or know how, to convert E164 prefixes.

If so, the LS may be forced to accept routes of an address family it may not
want to support.  The LS may not want individual E164 routes, but says E164
to support TrunkGroup routes with E164 prefixes.


Thanks,
Rick