On Mon, Dec 12, 2016 at 7:10 PM, Steve Medin <[email protected]> wrote: > Yea, but when I talk about the Plex Pass certs, I'm not on the internal > network privacy concern that split-horizon suits, I'm talking about how TCSC > fits customers with static and limited domain ownership.
Can you expand on what use case for redaction doesn't fit into that model? I don't believe we've heard such a use case articulated. That is, while it's possible to imagine foo.corp.example.com as part of a domain hierarchy, or even impendingmerger.example.com (to use Peter Bowen's example), are you suggesting that you believe it to be routine and normal that such certificate holders need impendingmerger.example.com impendingmerger.example.net impendingmerger.example.org impendingmerger.example impendingmerger.pretend-the-next-word-is-a-cctld.example impendingmerger.some-other-brand-name.example (etc)? Otherwise, the discussion of the limitations of TCSC to branding don't really seem to fit to the topic of the redaction use cases discussed so far, but it's possible you're imagining a yet undiscovered case? _______________________________________________ Trans mailing list [email protected] https://www.ietf.org/mailman/listinfo/trans
