Re: timeouts in draft-ietf-mboned-driad-amt-discovery (was: MBONED WG Call For Adoption: draft-jholland-mboned-driad-amt-discovery)

On Fri, 25 Jan 2019, Holland, Jake wrote:

> Hi Mikael,
>
> Thanks for your comments, they led me to realize I had left out some
> important context. I've submitted a new version of the draft:
> https://datatracker.ietf.org/doc/draft-ietf-mboned-driad-amt-discovery/
>
> Unfortunately I'm not seeing the diff links from the prior version
> in the html--is there a way to get those turned on?  (I assume I
> screwed that up when submitting, but I checked and saw it there
> for others?)

http://tools.ietf.org//rfcdiff?url1=https://www.ietf.org/archive/id/draft-jholland-mboned-driad-amt-discovery-03.txt&url2=https://www.ietf.org/id/draft-ietf-mboned-driad-amt-discovery-00.txt

I read that, and your proposed approach to handle this seems fine. 
However, do we really want to make this up to the implementor to decide 
and not have more guidance? Again, I am no AMT expert so I'll defer that 
to people who know more than I do.

I realised another thing.

3.2.1.  Sender-controlled Relays

    When a sender network is also operating AMT relays to distribute
    multicast traffic, as in Figure 6, each address could appear as an
    AMTRELAY RR for the reverse IP of the sender, or one or more domain
    names could appear in AMTRELAY RRs, and the AMT relay addresses can
    be discovered by finding an A or AAAA record from those domain names.

Does this mean there can only ever be a single A *or* AAAA record? What 
happens if there are 2 A records and 3 AAAA records? Which one does it 
use, in what order? Should it implement some kind of "Happy Eyeball" 
functionality to figure out the best way to talk to it?

-- 
Mikael Abrahamsson    email: [email protected]

_______________________________________________
MBONED mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mboned