Re: [rtcweb] [MMUSIC] Draft new: draft-wang-mmusic-encrypted-ice-candidates

This draft has the effect of defining a new gTLD.  That's problematic, and likely unnecessary.  I would encourage you to look into ways to signal these candidates differently.  a=encrypted-candidate might work, for instance.  You might be able to encrypt more data than an IP address in the process.

I also don't see how key management works here.  The goal of the draft is to define a set of entities that you are OK with reading your IP address, but I don't see any text that addresses the difficulty of a) identifying the entities in that set, and b) getting those entities the necessary keys.  Those are the really hard problems in this space.

I don't see how this provides any sort of algorithm agility or ability to identify the keys that are in use.  Maybe trial decryption is acceptable in this context, but that can get unwieldy fairly rapidly.

On Sat, Nov 2, 2019, at 07:06, Qingsi Wang wrote:
> Greetings.
> 
> This draft 
> (https://tools.ietf.org/html/draft-wang-mmusic-encrypted-ice-candidates-00) proposes a complementary solution to the mDNS candidate detailed in draft-ietf-rtcweb-mdns-ice-candidates, specifically for managed networks. IPs of ICE candidates are encrypted via PSK and signaled as pseudo-FQDNs in this proposal, and it aims to address the connectivity challenge from the mDNS technique in these managed environments. The current work on this draft is tracked in https://github.com/tQsW/encrypted-ice-candidates.
> 
> Regards,
> Qingsi
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>