[sig-ipv6] BOUNCE sig-ipv6@lists.apnic.net: Non-member submission from [Brian E Carpenter <brian@hursley.ibm.com>]

[owner-sig-ipv6@lists.apnic.net]

>From owner-sig-ipv6  Tue Jul 11 04:36:12 2000
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by whois.apnic.net (8.9.3/8.9.3) with ESMTP id EAA95524
	for <sig-ipv6@apnic.net>; Tue, 11 Jul 2000 04:36:10 +1000 (EST)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id TAA145598; Mon, 10 Jul 2000 19:28:33 +0100
Received: from hursley.ibm.com (lig32-225-4-144.us.lig-dial.ibm.com [32.225.4.144]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id TAA21830; Mon, 10 Jul 2000 19:28:40 +0100 (BST)
Message-ID: <396A00F4.7C95A15D@hursley.ibm.com>
Date: Mon, 10 Jul 2000 11:59:32 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Joao Luis Silva Damas <joao@ripe.net>
CC: Stephen Burley <stephenb@uk.uu.net>, Kazu@venus.Sun.COM,
        Yamamoto@venus.Sun.COM, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp, sig-ipv6@apnic.net,
        mir@ripe.net, ipv6-wg@ripe.net, richardj@arin.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <20000706.172714.91311805.kazu@Mew.org>
	 <39646A02.CACB8F8C@uk.uu.net> <3964DE58.7DB92581@hursley.ibm.com>
	 <3965A5F0.8505E7BA@uk.uu.net> <3965F75D.E9B4FF6A@hursley.ibm.com> <a04320404b58f5377cf45@[193.0.1.195]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Of course we should talk, the next opportunity is the Pittsburgh IETF.

However, let's be careful about deducing general policy from what today's
ISPs believe, based on IPv4 experience. Things are truly different 
in IPv6. 

   Brian

Joao Luis Silva Damas wrote:
> 
> Brian,
> 
> At 10:29 -0500 7/7/00, Brian E Carpenter wrote:
> ...snip...
> >  > A /64 for dialup
> >>  is also too rigid because the way technology is going a /64 is not
> >>going to be
> >>  enough subnets for what wiill be a dial up connection with a large
> >>lan behind it.
> >
> >Indeed. But that isn't an issue the RIRs need to think about.
> 
> It is not the RIRs trying to force variable length prefixes. At the
> RIPE meeting in Budapest and the ARIN meeting in Calgary we reported
> what the outcome of conversations with IETF people was (the /48, /56,
> /64 options for allocation).
> This seemed to be a reasonable way of doing it for the IPv6/ngtrans
> IETF people and to the RIR people present in Adelaide.
> 
> At both the ARIN and RIPE meetings, ISPs (the people who will use the
> address space, after all) were the ones that suggested variable
> length prefixes for allocation and the RIRs must go by the community
> consensus (BTW, at the RIPE meeting no consensus was reached, with
> both the variable length and the 3 fixed lengths having supporters).
> 
> A second issue is to think about a way of getting the IETF IPv6
> people and the 3 RIR communities to talk to each other at the same,
> otherwise we are entering a loop, with at least 4 separate
> discussions and each dependant on the other 3.
> 
> Joao
> 
> >   Brian


*              sig-ipv6:  APNIC SIG on IPv6 technology and policy issues           *
* To unsubscribe: send "unsubscribe" to sig-ipv6-request@apnic.net *