Re: Last Call: <draft-ietf-iasa2-rfc4071bis-08.txt> (Structure of the IETF Administrative Support Activity, Version 2.0) to Best Current Practice

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 07-Mar-19 04:30, Alissa Cooper wrote:
> 
>> On Mar 5, 2019, at 5:41 PM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
>>
>> On 06-Mar-19 11:03, Alissa Cooper wrote:
>> ...
>>>>
>>>> Will the insurance coverage for IETF "decisions-making" be managed by the IETF LLC?
>>>
>>> No.
>>
>> Hang on. If this refers to liability insurance for IETF volunteer leadership positions, RFC2031bis says that the LLC does it:
>> https://tools.ietf.org/html/draft-ietf-iasa2-rfc2031bis-04#page-6
>>
>> Who is carrying that insurance right now today? Surely it must be carried by the LLC, since it's a vital admin requirement for the IETF? I certainly assumed that it was part of "other appropriate insurance policies" as mentioned in RFC4071bis.
>>
>> If the intention is that ISOC continues to carry this insurance, RFC2031bis needs to say so instead of the opposite. And somebody needs to tell ISOC.
> 
> Sorry. My interpretation of the question was “do we have insurance to cover all decisions made in the IETF?” And the answer to that is no. The insurance we have related to the standards process covers the leadership, and it is held by the IETF LLC.

Thanks Alissa! No, I don't think we can insure against bad decisions ;-).

   Brian





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux