Re: Using DNS for SSM

[Dino Farinacci <dino@procket.com>]

>> simpler still would be to simply have two A records:
>>    radio.example.com	A	10.1.1.1
>>    radio.example.com	A	232.1.1.1
>> and let the application determine which is source and which is group
>> based on the address range? (i'm prepared for someone to tell me that
>> there are resolvers out there that pass only on A record to the app.)

    Yes, this could work and if someone wanted the same source to send
    tv content, you'd have:

	tv.example.com A        10.1.1.1
	tv.example.com A        232.1.1.2

    and if this *only* existed:

	cartoons.example.com A  232.1.1.1
        movies.example.co m  A  232.1.1.1

    it would be ambiguous (and insufficient) to the application so it would
    be ignored.

    However, I was thinking that potential source mirroring would be used so

        radio.example.com AA         10.1.1.1.232.1.1.1
        radio.example.com AA         10.2.2.2.232.1.1.1
        radio.west.example.com A     10.1.1.1
        radio.east.example.com A     10.2.2.2

    might make sense and the members of the mirror would use consistent
    group addresses for the same content.

Dino