On Wed, 2009-03-25 at 09:02 -0400, Joly, Robert (CAR:9D30) wrote:
> > On Tue, 2009-03-24 at 15:01 -0400, Robert Joly wrote:
> > > > Hi,
> > > > 
> > > > Regarding XCF-3139 (Cannot add or delete Intranet Subnets on the 
> > > > Internet Calling GUI Page) After a discussion took on IRC 
> > we agreed 

> > > 3- What is the motivation for providing multiple topology 
> > sets.  If we 
> > > cannot think of a compelling use case then my vote is to stick a 
> > > single set for simplicity sake.
> > 
> > There are lots of companies out there that have multiple 
> > subnets - ours included, but even small ones often do.
> 
> That I understand and that has my full support however that is not what
> I was inquiring about.  A topology can consist of n IP subnets and m DNS
> widlcards and that is fine but what is being proposed is the ability to
> define multiple topologies.  See xml file mock-up proposed (re-copied
> below):
> 
>    <localtopology>
>      <ipV4subnet>10.0.0.0/8</ipV4subnet>
>      <ipV4subnet>172.16.0.0/12</ipV4subnet>
>      <ipV4subnet>192.168.0.0/16</ipV4subnet>
>      <dnsWildcard>*.d1.itcnetworks.ro</dnsWildcard>
>    </localtopology>
>    <localtopology>
>      <ipV4subnet>11.0.0.0/8</ipV4subnet>
>      <ipV4subnet>173.16.0.0/12</ipV4subnet>
>      <ipV4subnet>194.168.0.0/16</ipV4subnet>
>      <dnsWildcard>*.d2.itcnetworks.ro</dnsWildcard>
>    </localtopology>
> 
> What I'm asking about is the presence of multiple <localtopology>.
> Currently, we can only define one local topology (hence a single
> <localtopology>).  Is was inquiring about the justifications for
> introducing multiple ones.

Ah... ok.

Mircea... what's the difference between one localtopology element like
you describe above that contains all the subnets, and many?

I think that in the future, we may need many for some purposes (branch
office support), but I don't want to try to solve that kind of problem
yet.


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to