Round 2

Terry Disz disz at mcs.anl.gov
Mon Feb 10 15:43:42 CST 2003


In the following comments, no motivation is supplied to the community for
the reasons behind the change to dynamic address allocation and the ensuing
issues. You might want to supply some words of justification so it doesn't
seem an arbitrary change.


>
> The problem we have is the following:
>
> - AG 1.0 used statically assigned multicast addresses for the media (e.g.
> one address for video and one address for audio).
>
> - There has been some work at making sure this set of addresses work,
> including various firewall, bridge, and tunneling solutions.
>
> - AG 2.0 uses dynamically assigned addresses for media by default, however
> static addressing is supported. The static address support should ensure
> events like SCGlobal can succeed.
>
> - We can't support infinite backwards compatibility , but want to backward
> compatibility enough for users to comfortably transition (we don't want to
> abandon the community!)
>
> - We're moving to dynamic addressing, but before we can do
> entirely dynamic
> address allocation we need to ensure the basic services are fault tolerant
> and robust enough to handle the problems associated with network
> brokenness.
>




More information about the ag-dev mailing list