-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not speaking as a chair...
> I'm sort of imagining an attribute that the proxy includes indicating it
> has performed some check and the policy applied to perform that check.
> I'm not entirely sure what level of granularity is required.
> I'm wondering if there are participants who would be interested in
> working through details of this?
I'm thinking about the channel-binding-cookie we built into my old
negotiate-ng draft to say that an http proxy knew about the CB token.
Perhaps a similar model might work... At least your description of
the problem sounds similar to the problems we were trying to solve
back then.
Cheers Leif
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1a+RoACgkQ8Jx8FtbMZnelAwCfWvNvb36kuxbYOzTaOpgOsnNc
700AniO54+h2EX7hyVJMUXBDMuIC3nTh
=eLKR
-----END PGP SIGNATURE-----
_______________________________________________
abfab mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/abfab
