Benjamin Kaduk <[email protected]> wrote: >> > The requirement "the client MUST be able to determine whether an AS has >> > the authority to issue access tokens for a certain RS. This can for >> > example be done through pre-configured lists, or through an online >> > lookup mechanism that in turn also must be secured." indicates that C >> > is required to have another mechanism to determine the AS for a >> > specific RS and that the unauthorized AS address is completely >> > redundant. >> >> This is a hard problem. >> Q: "Who are you?" >> A: "Depends upon who is asking! Who are you?" >> A: "Depends upon who is asking! Who are you?" >> ... >> >> The DNS-SD WG produced rfc8882, but as I understand it, >> https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-privacy-05 >> was abandonned because the WG did not see implementation/energy. >> I can't seem to find the thread discussing that state.
> Interestingly, the corresponding requirements document was just published
> recently as RFC 8882.
> "A problem with no solution is a hard problem"...
I thought Christian Huitema's solution, which I think is three or four years
old, was reasonable. The WG just couldn't get reviews or people interested
in implementing. Maybe ACE cares enough now.
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
