ipv6-wg

Download

ipv6-wg@ripe.net

November 1997

2 participants
2 discussions

Re: Last Call: IP Version 6 Addressing Architecture to Proposed Standard
by Daniel Karrenberg 01 Dec '97

01 Dec '97

Authors Robert Blokzijl RIPE Chair Daniel Karrenberg RIPE NCC General Manager Background RIPE is an organisation founded in 1989 wich aims to ensure the technical and administrative coordination necessary for the operation of the Internet in Europe [ripe-01]. The RIPE NCC performs activities for the benefit of the Internet service providers (ISPs) in Europe and the surrounding areas; primarily activities that the ISPs need to organise as a group, although they may be competing with each other in other areas. In particular the RIPE NCC, as Regional Internet Registry, allocates and assigns IPv4 address space in Europe and surrounding areas [ripe-162]. The RIPE NCC started operations in 1992. It currently allocates address space to more than 800 local Internet Registries almost all of which are operated by ISPs. The number of local IRs is expected to reach 1250 in 1998. There are currently no indications that the number of local IRs will stop growing. The authors have contributed significantly to the development of the distributed Internet registry system which is used for the allocation and assignment of provider based IPv4 address space today. As such they have ample experience with the development of address space allocation and assignment policies. One important element of current policies is that the size of address space allocations is determined by previous justified use of address space. A prerequisite for this policy is that the size of allocations can start small and increase or decrease according to previous justified usage [ripe-159]. Argument We believe <draft-ietf-ipngwg-unicast-aggr-02.txt> is critically flawed because it standardises address aggregation boundaries without any explicit technical justification. In particular the length of the TLA and NLA fields are proposed to be standardised as fixed at prarticular values with no technical justification for either the fact that these lengths need to be fixed nor for the particular values chosen. The lack of technical justification is significant because the standardisation of TLA and NLA lengths directly influences many elements of Internet operations including address space allocation policies. In particular the TLA being fixed at 13bit length makes only 8K TLAs available per FP. Consequently Internet Registries will not be able to use proven allocation policies but rather engage in regulatory practises. The rules proposed in <draft-ietf-ipngwg-tla-assignment-01.txt> are clear evidence of this. Broad acceptance of such rules and their implementation is extremely unlikely unless there is convincing technical reasoning behind the constraints that necessitate the rules. Because of this critical flaw we request that the IESG not advance <draft-ietf-ipngwg-unicast-aggr-02.txt> and <draft-ietf-ipngwg-addr-arch-v2-05.txt> to proposed standard yet. We suggest that the IESG refer these documents back to the authors and the WG with the request to provide technical justification for the placement of aggregation boundaries and to consider making these boundaries variable where technically feasible. References The referenced RIPE documents can be accessed at http://www.ripe.net/docs/ripe-xxx.html HTML ftp://ftp.ripe.net/ripe/docs/ripe-xxx.txt ASCII ftp://ftp.ripe.net/ripe/docs/ripe-xxx.ps PostScript

2 3

Minutes of the IPv6 WG at RIPE 28th
by Bernard.Tuy＠urec.cnrs.fr 30 Nov '97

30 Nov '97

---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Charset: us-ascii X-Sun-Content-Lines: 14 Hi everybody, Here enclosed a proposal for the minutes of the IPv6 WG at the RIPE 28th meeting held in A'dam on last September. Comments, additions, corrections please to me directly :tuy@urec.fr Thanx for your careful reading and help, Regards, +Bernard Tuy. ---------- X-Sun-Data-Type: default X-Sun-Data-Name: IPv6-wg X-Sun-Charset: us-ascii X-Sun-Content-Lines: 114 OD: CNRS/U.R.E.C Tx: B. Tuy Dt: 20.10.1997 NV: 1.0 ------- Minutes from the RIPE IPv6-wg ** DRAFT ** Chairman : Thomas Trede, Nacamar, Germany Scribe : Bernard Tuy, UREC, France Attendance: xx persons present Agenda : sent to the mailing list before the meeting Reports . 6bone (F. Dupont) Presenting 6bone maps (sites and core) more than 120 sites are now connected to the 6bone (representing #30 countries) A new addressing scheme (cf related IETF IDs at http://playground.sun.com) is being to be deployed. Top Level Aggregators (in fact, pseudo TLAs) have begun to be allocated to people matching the conditions to get one. The pseudo TLAs (pTLAs) list is available at http://www.6bone.net/6bone_pTLA_list.html As an example the aggregated addressing plan in France is shown. To a question from BT : 4 people claimed to be deploying this aggregated plan, many are connected to the 6bone and less are using IPv6 ... ! . IPv6 Registry (D. Kessens) fully operational yet (whois.6bone.net) miror sites : whois.nic.fr and whois.ra.net 26 countries are now registered One can find a new whois client able to solve external references at www.isi.edu/~davidk/6bone/ Inet-num-ipv6 object attributes : (refer to David's Internet Draft for the syntax to use to fill every attribute) ipv6-site : prefix: multiple if needed application : apps running at that site tunnel: multiple if needed to describe the topology of the site contact: NIC-handle from RIPE, InterNIC or 6bone-NIC ... url: how to get more info on this site Test address allocation: same object as in IPv4 except the inetnum label ! . Last IETF meeting (Munich, Germany, Aug. 1997) (Francis Dupont) NGtrans-wg : see the minutes of the meeting already sent by email . tools : the translation between IPv4 and IPv6 headers (NAT,...) is under discussion, various solutions are being considered. Cisco has an implementation (the S/w is available from P. Marques) . 6bone : a new domain has been set up (6bone.net) BGP4+ is getting the consensus. Strong opposition from Cisco to BGP5 Implemented by : Cisco, Digital, GateD, Telebit Core backbone sites of the 6bone as to move to the new aggregated addressing scheme before Dec 1st. IPng-wg : see the minutes of the meeting already sent by email . Advancing the IPv6 specifications and related documents to standards . large discussion with the flow label identifier (why and how to use it ?), still open over the mailing list . strong consensus for the MTU specifications (minimal is moving from 576 to 1300) ION-wg : . G. Armitage proposal is the only one today using MARS for multicasting, NHRP for external routing and Neighbor Discovery for local routing. NBMA's are limited to ATM only today IDR-wg : BGP4+ will replace RIPng in the core backbone, before the end of the year. IPSEC-wg : New drafts are expected, since the 182x serie seems to be obsolete Multicast : no consistent progress except we have to have new specs based on the new IGMPv2 RFC. Implementations : refer to the SUN web page (http://playground.sun.com/pub/ipng/html/ipng-implementations.2.html) RIPE IPv6 address assignment : Noone in the audience claimed to need an IPv6 address space allocated yet. Other wg's input : DNS ? ____ EoF.

2 1