Ray,
I think our goal is to not lose essential participants from the IETF due
to clashes. In fact that's why we want to schedule several years out, so
as to make it easier for many other organizations to do their scheduling.
If we do that, it's each organization's choice whether or not they avoid IETF
weeks. (This week, for example, ITU-T NGN chose to schedule two major meetings
in other cities.)
I don't think it's discriminatory to put the NICs and NOGs that don't seem
to have a large overlap with IETF participants in the second category. It's
just a matter of practicality, given that optimal scheduling is a
fundamentally imsoluble problem anyway. I'd be delighted to see growth in
African participation in the IETF (the spreadsheet shows two people from
Africa pre-registered this week).
Brian
Ray Plzak wrote:
Why should AfriNIC be considered any less of an RIR than the other APNIC,
ARIN, LACNIC, or RIPE NCC(meeting is at RIPE meeting)? Why should AFNOG be
considered any less of an operator's forum than NANOG or EOF(meeting is at
RIPE meeting)? We are talking about an entire continent. It seems to me in
this case that the priority should be equality of treatment based on the
function being performed for a region and not any other perceived reason for
inequity. Or doesn't the IETF care about the Internet in the developing
regions of the world?
Ray
-----Original Message-----
From: Joel Jaeggli [mailto:joelja@xxxxxxxxxxxxxxxxxxxx]
Sent: Saturday, March 25, 2006 1:53 AM
To: JORDI PALET MARTINEZ
Cc: ietf@xxxxxxxx
Subject: Re: Proposed 2008 - 2010 IETF Meeting dates
yOn Fri, 24 Mar 2006, JORDI PALET MARTINEZ wrote:
Hi Ray,
I know is difficult already to manage to avoid clashes, but I think is
unfair and discriminatory to have all the RIRs and *NOGs in the MUST NOT
list, but AfriNIC, AfNOG and SANOG in the other list.
having attended two of three I would simply observe that the overlap
between the two communites is a little lower. also. having attended every
afnog meeting, it hasn't yet clashed with the ietf. You have to have some
priorities.
Anticipating for so many years is good enough to allow all those
organizations to chat together and make sure the there is not a clash,
not
just in the exact dates, but allowing a few days in between (if they are
hosted in different places of the world) to allow traveling among them,
which has not been the case up to now all the time.
Regards,
Jordi
De: Ray Pelletier <rpelletier@xxxxxxxx>
Responder a: <ietf-bounces@xxxxxxxx>
Fecha: Fri, 24 Mar 2006 09:41:48 -0500
Para: "ietf@xxxxxxxx" <ietf@xxxxxxxx>
Asunto: Proposed 2008 - 2010 IETF Meeting dates
The IETF is proposing dates for its meetings being held 2008 through
2010. Those dates can be found at
http://www.ietf.org/meetings/future_meetings0810.html
The dates will be evaluated and selected to meet the IETF's standards
development objectives, while avoiding conflicts with SDOs and other
organizations to the extent possible. Those organizations can be found
on the Clash List from the same url.
Comments regarding these dates should be addressed to the IAD at
iad@xxxxxxxxx
It is anticipated that an official IETF Meeting Calendar for 2008 -
2010
will be formally adopted on April 20, 2006 by the IAOC.
Regards
Ray Pelletier
IAD
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
**********************************************
The IPv6 Portal: http://www.ipv6tf.org
Barcelona 2005 Global IPv6 Summit
Slides available at:
http://www.ipv6-es.com
This electronic message contains information which may be privileged or
confidential. The information is intended to be for the use of the
individual(s) named above. If you are not the intended recipient be aware
that any disclosure, copying, distribution or use of the contents of this
information, including attached files, is prohibited.
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
--
--------------------------------------------------------------------------
Joel Jaeggli Unix Consulting
joelja@xxxxxxxxxxxxxxxxxxxx
GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf