> in these principles I have not directly addressed the feeling of some
> people that the IETF needs to be able to "blow the bolts" (as I put it
> a while back) with the ISOC quickly if things "go bad" in some way. I
> have not done so not because I want to dismiss or ignore such feelings
> but because I have not figured out a way to express it if I take into
> account the fact that the IETF cannot actually go it alone anytime soon
> because it does not have the cash flow from meeting fees that would
> support an independent IETF - suggestions welcomed
How about:
<section title="Community Consensus and Grant of Authority">
<t>
The IETF is a consensus-based group and authority to act on behalf
of the community is an act that requires a high degree of consensus
and the continued consent of the community
After a careful process of deliberation, there is a broad-based
community consensus to house the IETF Administrative & Support
Activities (IASA) within the Internet Society, which is reflected
in this Best Current Practice (BCP) RFC.</t>
<t>
Termination and change. Any change to this agreement shall require
a similar level of community consensus and deliberation and shall
be reflected by a subsequent Best Current Practice (BCP) RFC.
</t>
</section>
A termination clause is standard in any agreement and this one simply
says "if you want to change this, get another bcp through the process."
This doesn't address the "and we want to take our money with us" issue,
but I believe that could be addressed elsewhere or not addressed at
all. Either way works for me.
> 2/ The IAD, IAOC and the ISOC shall not have any authority over the IETF
> standards development activities.
>
That's almost true, but you probably need to address that the fact that
ISOC does play an important role in the standards process, a role
that is not changed by this document.
> 7/ The right to use any intellectual property rights created by any
> IASA-related or IETF activity may not be withheld by the ISOC from the IETF.
how about "withheld or limited in any way"?
Regards,
Carl
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf