[122997] in North American Network Operators' Group
[Fwd: [members-discuss] [ncc-announce] RIPE NCC Position On The ITU
daemon@ATHENA.MIT.EDU (Adam Waite)
Fri Feb 26 07:03:31 2010
Date: Fri, 26 Feb 2010 13:03:01 +0100
From: Adam Waite <awaite@tuenti.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is a multi-part message in MIME format.
--------------050700010302000101040007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
I didn't see this on NANOG yet, but it's caused a stir on the RIPE list.
--------------050700010302000101040007
Content-Type: message/rfc822;
name="[Admin] [members-discuss] [ncc-announce] RIPE NCC Position On
The ITU IPv6Group.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename*0="[Admin] [members-discuss] [ncc-announce] RIPE NCC Position
O"; filename*1="n The ITU IPv6 Group.eml"
Return-Path: <admin-bounces@tuenti.com>
X-Original-To: awaite@tuenti.com
Delivered-To: awaite@tuenti.com
Received: from calipso.tuenti.int (localhost [127.0.0.1])
by calipso.tuenti.com ((8.14.2/8.14.2)) with ESMTP id CB42A1801B8E;
Thu, 25 Feb 2010 18:05:40 +0100 (CET)
X-Original-To: admin@lists.tuenti.com
Delivered-To: admin@lists.tuenti.com
Received: from localhost (localhost [127.0.0.1])
by calipso.tuenti.com ((8.14.2/8.14.2)) with ESMTP id 7EA41195F3E8
for <admin@lists.tuenti.com>; Thu, 25 Feb 2010 18:05:31 +0100 (CET)
Received: from postboy.ripe.net (postboy.ripe.net [193.0.19.3])
by calipso.tuenti.com ((8.14.2/8.14.2)) with ESMTP id 0491E195F3EB
for <admin@tuenti.com>; Thu, 25 Feb 2010 18:05:30 +0100 (CET)
Received: from postboy.ripe.net (localhost [127.0.0.1])
by postboy.ripe.net (Postfix) with ESMTP id 5AD8B6A05F;
Thu, 25 Feb 2010 18:05:03 +0100 (CET)
X-Original-To: members-discuss@ripe.net
Delivered-To: members-discuss@lists.ripe.net
Received: from postboy.ripe.net (localhost [127.0.0.1])
by postboy.ripe.net (Postfix) with ESMTP id 733876A04A;
Thu, 25 Feb 2010 17:30:24 +0100 (CET)
X-Original-To: ncc-announce@lists.ripe.net
Delivered-To: ncc-announce@lists.ripe.net
Received: from ayeaye.ripe.net (ayeaye.ripe.net [193.0.1.103])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by postboy.ripe.net (Postfix) with ESMTP id 712C36A035
for <ncc-announce@lists.ripe.net>; Thu, 25 Feb 2010 17:20:19 +0100 (CET)
Received: from vifa-1.office-lb-1.ripe.net ([193.0.1.5]
helo=chris.vpn.ripe.net)
by ayeaye.ripe.net with esmtps (TLSv1:AES128-SHA:128) (Exim 4.63)
(envelope-from <ncc@ripe.net>) id 1NkgRn-0007nX-8f
for ncc-announce@ripe.net; Thu, 25 Feb 2010 17:20:19 +0100
Message-Id: <43A17797-7C76-4BD7-855B-093B41362627@ripe.net>
From: Axel Pawlik <ncc@ripe.net>
To: ncc-announce@ripe.net
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
X-Mailer: Apple Mail (2.936)
X-RIPE-Signature: 4aec2e1a63375039d8a9243630c874149b89d40abe2c867bb8a309175b122366
X-BeenThere: ncc-announce@ripe.net
X-Mailman-Version: 2.0.13
Precedence: bulk
X-BeenThere: members-discuss@ripe.net
X-RIPE-Lists: Members discussion list <members-discuss.ripe.net>
Date: Thu, 25 Feb 2010 17:20:18 +0100
Subject: [Admin] [members-discuss] [ncc-announce] RIPE NCC Position On The
ITU IPv6 Group
X-BeenThere: admin@tuenti.com
List-Id: Admin Team mailing list <admin.tuenti.com>
List-Unsubscribe: <http://lists.tuenti.local/mailman/options/admin>,
<mailto:admin-request@tuenti.com?subject=unsubscribe>
List-Archive: <http://lists.tuenti.local/mailman/private/admin>
List-Post: <mailto:admin@tuenti.com>
List-Help: <mailto:admin-request@tuenti.com?subject=help>
List-Subscribe: <http://lists.tuenti.local/mailman/listinfo/admin>,
<mailto:admin-request@tuenti.com?subject=subscribe>
Sender: admin-bounces@tuenti.com
Errors-To: admin-bounces@tuenti.com
Dear Colleagues,
As you may be aware, the International Telecommunication Union's (ITU)
Telecommunication Standardization Bureau (TSB) has convened an ITU
IPv6 Group, the first meeting of which will be held on 15-16 March
2010 in Geneva, Switzerland. Information on this group is available at:
http://www.itu.int/ITU-T/othergroups/ipv6/
Among the group's Terms of Reference are the following:
* To draft a global policy proposal for the reservation of a large
IPv6 block, taking into consideration the future needs of developing
countries (as outlined in paragraph 23 of ITU document C09/29).
* To further study possible methodologies and related
implementation mechanisms to ensure 'equitable access' to IPv6
resource by countries.
* To further study the possibility for ITU to become another
Internet Registry, and propose policies and procedures for ITU to
manage a reserved IPv6 block.
* To further study the feasibility and advisability of implementing
the CIR [Country Internet Registry] model for those countries who
would request national allocations.
The ITU IPv6 Group is open to ITU Member States and Sector Members of
ITU-T and ITU-D. RIRs that are not members have also been extended an
invitation to participate.
IPv6 address policy is clearly of critical importance to the RIPE NCC
membership, and the unsympathetic implementation of any of the Terms
of Reference stated above would have serious impact on the global IP
address distribution environment.
Members of RIPE NCC staff will be participating in this meeting of the
ITU IPv6 Group to represent the interests of our members and community.
The position of the RIPE NCC is based on support for smooth and
reliable working of the Internet globally, and for the bottom-up, open
policy development process that allows for all stakeholders, including
business, government and the technical community, to participate.
Some of the issues addressed in the Terms of Reference listed above
are a cause for concern because they could directly affect the RIPE
NCC operations as a Regional Internet Registry (RIR). Therefore, the
RIPE NCC position on the Terms of Reference is as follows:
* The needs of developing economies in IP address policy are
important. Network operators in these economies have fair and equal
access to IPv6 resources from the Regional Internet Registries (RIRs),
and to the Policy Development Processes in their RIR and globally.
Each of the RIRs has been allocated an equal block of IPv6 to
distribute to networks in their region. (eg. AfriNIC has been
allocated the same sized block of IPv6 as the RIPE NCC).
* IPv6 allocations made by RIRs to date amount to the equivalent of
500 times the size of the entire IPv4 address pool, allocated to
networks in over 150 economies.
* If a significant sector in the Internet community feels that the
"reservation of a large IPv6 block" for "the future needs of
developing countries" is warranted, the open, bottom-up Policy
Development Processes (PDPs) of the RIRs provide an appropriate forum
in which to argue that case and develop such a policy.
* The RIRs, as the recognised stewards of Internet Number Resources,
are working, individually, jointly, and with invited experts, to
engage the ITU membership. We have closely followed discussions in the
ITU to date. The RIPE NCC does not believe that there are any problems
that would be solved by the shift to a country-based allocation system
or the installation of the ITU as an Internet Registry.
The purpose of this email is to ensure that all RIPE NCC members are
informed of the RIPE NCC's participation in this ITU IPv6 Group, and
our position. If you have any comments or questions regarding this
information, please send an email to <ncc@ripe.net>.
Kind regards,
Axel Pawlik
Managing Director
RIPE NCC
----
If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/
First click on General and then click on Edit.
At the bottom of the Page you can add or remove addresses.
--------------050700010302000101040007--
