-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
(1) Use of XPTR records for SSP. The idea here is to create a more
general policy mechanism that can be used by WS-* and such. There
were about 20 messages discussing this from 5 people. I'm not
reading a clear consensus on this.
Issue#1: +1 - include use of XPTR as part of ssp-00
Issue#1: -1 - exclude use of XPTR from ssp-00
+1
(2) SSP record type (TXT vs. something new). Only 4 messages in
discussion, mostly saying "if you support TXT, don't bother with
anything else." Again, no clear consensus.
Issue#2: +1 - Define how to use a TXT RR for SSP policies (with or
without something else)
Issue#2: -1 - Don't use TXT at all, only use new RRs for SSP
+1
(3) Upward query vs. wildcard publication. 27 messages in
discussion from 15 people. Most of the discussion was a rehash of
the idea of associating semantics with DNS zone-cuts, which we had
already discussed and rejected. I have also been trying to get an
opinion from DNSOP on the idea of a one-level upward search (which
I think solves 90% of the problem), but haven't gotten any response.
Issue#3: +1 - Define an upward query based approach to finding SSP
statements
Issue#3: -1 - Define a wildcard based approach to finding SSP
statemetns
- -1, but I agree with Eric that if we end up with exiting RR types,
then we kinda have to make it +1.
Jon
-----BEGIN PGP SIGNATURE-----
Version: PGP Universal 2.6.1
Charset: US-ASCII
wj8DBQFGbenosTedWZOD3gYRAoKPAKC5D6PG3tpPEeurz8mGOt1YBkXI7wCguzkY
uLNw+69KbkAhYzaioHprTj8=
=jcbh
-----END PGP SIGNATURE-----
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html