RIPE NCC to Support the Sustainability of the IETF
Dear colleagues, During the RIPE NCC Services Working Group at RIPE 72, and at the RIPE NCC General Meeting (GM), there was a presentation and discussion on the request for the RIPE NCC to support the IETF’s long-term sustainability: https://ripe72.ripe.net/programme/meeting-plan/services-wg/ The RIPE NCC Executive Board asked RIPE NCC members to discuss the proposal on the RIPE NCC Membership Discussion mailing list, and we would like to thank those who provided their input. The feedback received showed support for the proposal for the RIPE NCC to provide an ongoing financial contribution to the IETF. However, there were concerns that providing a one-off payment to the IETF would not be the ideal way to do this, and that there should be mechanisms in place that would allow the RIPE NCC to discontinue the annual financial support should circumstances change in the future. The RIPE NCC Executive Board has therefore composed the following Letter of Intent, which proposes the annual contribution of EUR 100,000 over the next ten years (2017-2026) to support the sustainability of the IETF. As noted, the proposed contribution will be added to the annual RIPE NCC Activity Plan and Budget, with regards to which members are encouraged to provide their feedback at the second GM every year. Best regards, Nigel Titley RIPE NCC Executive Board Chairman ================================= Letter of Intent by the RIPE NCC to Support the Sustainability of the IETF The RIPE Network Coordination Centre (RIPE NCC) hereby states its intent to make an annual financial contribution of EUR 100,000 over the next ten years (2017-2026) in support of the sustainability of the Internet Engineering Task Force (IETF). As with all financial contributions that the RIPE NCC commits to activities, this contribution will be reviewed annually and may be amended accordingly. This contribution will be reflected each year in the RIPE NCC Activity Plan and Budget. The RIPE NCC is proud to support the IETF and wishes it continued success in the years ahead. This letter of intent does not create in any way legal rights or obligations regarding the above described contribution. The RIPE NCC retains its right to discontinue this contribution at any time before the ten-year period elapses. =================================
Nigel, At 2016-07-13 12:24:58 +0200 Nigel Titley <exec-board@ripe.net> wrote:
The RIPE NCC Executive Board has therefore composed the following Letter of Intent, which proposes the annual contribution of EUR 100,000 over the next ten years (2017-2026) to support the sustainability of the IETF. As noted, the proposed contribution will be added to the annual RIPE NCC Activity Plan and Budget, with regards to which members are encouraged to provide their feedback at the second GM every year.
Wow! As a participant in the IETF, I think that this is great. Thank you RIPE NCC members & board! :-D Cheers, -- Shane
Nigel, Just like Shane, I applaud this measure. At the same time I do note that there has been a lot of discussion about the increasing cost of participating in IETF meetings. Has there been any thoughts on also supporting IETF indirectly by helping sponsor RIPE community members participating in the IETF prosess? Julf
Hi,
On 13 Jul 2016, at 15:38, Johan Helsingius <julf@julf.com> wrote:
increasing cost of participating in IETF meetings
Are you referring to the recent $50 increase in registration fees (the first increase since 2011) or something else? Mat
Hi, Mat,
Are you referring to the recent $50 increase in registration fees (the first increase since 2011) or something else?
That $50 increase in itself isn't probably very significant (travel and accommodation are still the largest expenses), but there has been a number of people (some of them very active in the IETF) who have recently raised the issue of cost of participation. Julf
Nigel, Just like Shane, I applaud this measure. At the same time I do note that there has been a lot of discussion about the increasing cost of participating in IETF meetings. Has there been any thoughts on also supporting IETF indirectly by helping sponsor RIPE community members participating in the IETF prosess? Julf
On 13/07/16 16:00, Johan Helsingius wrote:
Nigel,
Just like Shane, I applaud this measure. At the same time I do note that there has been a lot of discussion about the increasing cost of participating in IETF meetings. Has there been any thoughts on also supporting IETF indirectly by helping sponsor RIPE community members participating in the IETF prosess?
We haven't considered this, but it's a point worth considering. I'll make sure it gets onto the next board meeting agenda. All the best Nigel
Speaking as someone who works "behind the scenes" in the IETF, but still in a personal capacity, I would love for the IETF to be well-enough funded to *reduce* registration fees and provide offerings similar to those you find at a RIPE meeting ("free lunch", etc). The IETF Endowment is one way to achieve this if properly funded. On the specific topic of RIPE community members participating in the IETF process, there has been much discussion about the need for better collaboration between the IETF, RIR and Operator communities and I am hoping that this too can be supported by funding programs such as this one. Ole Ole J. Jacobsen Editor and Publisher The Internet Protocol Journal Office: +1 415-550-9433 Cell: +1 415-370-4628 Web: protocoljournal.org E-mail: olejacobsen@me.com On Wed, 13 Jul 2016, Nigel Titley wrote:
On 13/07/16 16:00, Johan Helsingius wrote:
Nigel,
Just like Shane, I applaud this measure. At the same time I do note that there has been a lot of discussion about the increasing cost of participating in IETF meetings. Has there been any thoughts on also supporting IETF indirectly by helping sponsor RIPE community members participating in the IETF prosess?
We haven't considered this, but it's a point worth considering. I'll make sure it gets onto the next board meeting agenda.
All the best
Nigel
Ole,
On the specific topic of RIPE community members participating in the IETF process, there has been much discussion about the need for better collaboration between the IETF, RIR and Operator communities and I am hoping that this too can be supported by funding programs such as this one.
Indeed, that would be a Good Thing. Maybe it needs formal liaisons to be appointed, but maybe it can just be accomplished by more informal cross-participation. Julf
participants (6)
-
Johan Helsingius -
Matthew Ford -
Nigel Titley -
Nigel Titley -
Ole Jacobsen -
Shane Kerr