![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
John,
Dave, I'm sorry, but some of the assertions that have been made about what "protecting existing implementations" means have been indistinguishable to me from "no real changes permitted". It
My impression is that it is exactly that set of assertions, and
the associated implication that some process outside the normal
give and take of WG interactions will be used to determine which
changes are acceptable and which ones are not, are exactly what
has drawn those of us who have no DKIM-specific reservations
into this discussion.
Wow.
I have no idea what you are talking about or what you are basing it on.
If that interpretation was not what was intended, I would have expected Tony Hanson's suggestion about reuse of the XMPP language to be welcomed, not because of pressure from on high,
I saw it as a
helpful and constructive suggestion, coming from a respected
member of the community, to get things unstuck in a way for
which we already had established precedent.
Helpfulness requires that a problem exist. It didn't.
You apparently see all of the objections and reservations that have arisen to the language of the proposed charter as coming from people who raised the issues during the earlier, BOF and other pre-charter, discussions, lost, and are now trying to raise them again.
precisely because of the language about existing implementations, who have not previously been substantively involved with DKIM and who, instead, represent some small groundswell of community resistance to a WG that is thus constrained without any clear understanding of who gets to interpret the rules.
Groundswell? Again, wow.
d/
--
Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.