25 May
2009
25 May
'09
5:15 p.m.
Edson - Lists writes:
But with Your proposed change (lcr-id), what about
functionality overlap
with CarrierRoute (or vice-versa)? They already have, but LCR is much
simpler and more 'direct' for a single domain/'routing policy'
installation...
i'm not worried with possible overlap. users can decide, which module
to use. i use lcr, because i'm familar with it.
i have had a need myself too, where each domain could configure their
gws and lcr rules independent from other domains.
i'll check how much this lcr_id would complicate the implementation.
-- juha