From owner-ngtrans@sunroof.eng.sun.com  Thu Jul  6 04:31:02 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09636
	for <ngtrans-archive@odin.ietf.org>; Thu, 6 Jul 2000 04:31:02 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA11568;
	Thu, 6 Jul 2000 02:30:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA28082;
	Thu, 6 Jul 2000 01:29:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e668Sid24783
	for ngtrans-dist; Thu, 6 Jul 2000 01:28:44 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e668SZ624776;
	Thu, 6 Jul 2000 01:28:35 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA08450;
	Thu, 6 Jul 2000 01:28:33 -0700 (PDT)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA22604;
	Thu, 6 Jul 2000 01:28:32 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id RAA10421;
	Thu, 6 Jul 2000 17:28:31 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id RAA29191; Thu, 6 Jul 2000 17:28:31 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id RAA00362; Thu, 6 Jul 2000 17:28:30 +0900 (JST)
Date: Thu, 06 Jul 2000 17:27:14 +0900 (JST)
Message-Id: <20000706.172714.91311805.kazu@Mew.org>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Cc: arano@byd.ocn.ad.jp
Subject: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.95b43 on Emacs 21.0 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Multipart/Mixed;
 boundary="--Next_Part(Thu_Jul__6_17:27:14_2000_213)--"
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>

----Next_Part(Thu_Jul__6_17:27:14_2000_213)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Folks,

It seems to me that RTRs are going a wrong way, changing /48 per site
policy. If you think so, please speak up on sig-ipv6@apnic.net now.

--Kazu

----Next_Part(Thu_Jul__6_17:27:14_2000_213)--
Content-Type: Message/Rfc822

From: secretariat@apnic.net
Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)
X-Sender: paulg@compiler.staff.apnic.net
To: apnic-announce@lists.apnic.net
Subject: [apnic-announce] IPv6 Policy Document Revision
Sender: owner-apnic-announce@lists.apnic.net
Reply-To: apnic-talk@apnic.net
MIME-Version: 1.0

[Note "reply-to:" field]


Summary

Both ARIN and the RIPE NCC have had discussions with the Internet
communities in their region concerning the size of address prefixes 
to be assigned to IPv6 end sites.  APNIC is now seeking input from 
the community in the Asia Pacific region on this issue. If you care 
about this, please read on. 

Some background

The existing IPv6 policy document 'Provisional IPv6 Assignment and 
Allocation Policy Document' was published in May 1999. Formal revision
of the document commenced in October 1999. The existing document
is available at:

http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html 

Feedback on the existing document was collected from the Internet community 
at large facilitated through the regional processes of consultation by 
the RIRs as well as input from the membership of the 6bone and the
IETF IPv6 working groups. The deadline for comments was 31st January 2000.

On 29th March, the RIRs, chairs of the IPv6 related IETF working
groups and 6bone particpants met in Adelaide. The purpose of the meeting
was to expand and elaborate in person on the comments made by the 
IAB/IETF/6bone concerning the existing policy document. 

One of the issues of concern that had been previously raised by
members is the size of the end-site prefix (the 'SLA ID', currently 
defined in rfc2374 as 16 bits at a /48). This includes *all* types 
of end-sites including a single device. A /48 is sufficient address 
space to create 64K of subnets. 

The technical motivation for the 16 bit SLA ID field and the 
'one size fits all' principle was described in rfc2374 as:

  "The size of the Site-Level Aggregation Identifier field is 16 bits.
   This supports 65,535 individual subnets per site.  The design goal
   for the size of this field was to be sufficient for all but the
   largest of organizations.  Organizations which need additional
   subnets can arrange with the organization they are obtaining Internet
   service from to obtain additional site identifiers and use this to
   create additional subnets.

   The Site-Level Aggregation Identifier field was given a fixed size in
   order to force the length of all prefixes identifying a particular
   site to be the same length (i.e., 48 bits).  This facilitates
   movement of sites in the topology (e.g., changing service providers
   and multi-homing to multiple service providers)."

It is possible to imagine in future a variety of types of end-sites 
being connected to the Internet.  Some of these devices will be part 
of routed networks and others will not.  The question proposed is whether 
'one size fits all' (the /48) is appropriate for all end-sites? 

Both the RIPE and ARIN communities have rejected this.  

APNIC has been asked to consult with the Internet community in the 
Asia Pacific on this issue.
 
To date, there has been no consensus on what alternatives should be 
taken, but 3 different approaches have been identified in addition to 
the 16 bit SLA ID field specified in rfc2374. 

These are:

1) /64 for single devices (such as mobile phones), /48 for all other sites

2) /64 for single devices, /48 for large end sites which need more 
   than 256 subnets, and /56 for other sites (eg small, domestic/home sites)

3) Assign what is needed for the forseeable needs of the site, as a
   variable-length prefix of between /48 and /64. (It is important to
   remember that for any site that becomes multi-homed it is necessary to 
   use equal length prefixes from each provider even in the case where 
   one provider has allocated more prefix space than the other).

We are interested in your opinions, so that we may convey this to the 
other RIRs and to the IETF community. Please direct all follow up 
discussion and comments to <sig-ipv6@apnic.net>. For details of 
how to subscribe to this mailing list, please visit our web site at:
http://www.apnic.net/general.html#mailing-lists .

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
APNIC Secretariat
<secretariat@apnic.net>
                                                     Tel: +61-7-3367-0490
Asia Pacific Network Information Centre (APNIC) Ltd  Fax: +61-7-3367-0482
Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

*            APNIC-ANNOUNCE: Announcements concerning APNIC              *
* To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net *

----Next_Part(Thu_Jul__6_17:27:14_2000_213)----


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul  6 06:18:05 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10446
	for <ngtrans-archive@odin.ietf.org>; Thu, 6 Jul 2000 06:18:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA21752;
	Thu, 6 Jul 2000 04:17:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA04231;
	Thu, 6 Jul 2000 03:17:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e66AFwx24870
	for ngtrans-dist; Thu, 6 Jul 2000 03:15:58 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e66AFj624856
	for <ngtrans@sunroof.eng.sun.com>; Thu, 6 Jul 2000 03:15:46 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA14380
	for <ngtrans@sunroof.eng.sun.com>; Thu, 6 Jul 2000 03:15:43 -0700 (PDT)
Received: from boat.mail.pipex.net (our.mail.pipex.net [158.43.128.75])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id DAA01852
	for <ngtrans@sunroof.eng.sun.com>; Thu, 6 Jul 2000 03:15:27 -0700 (PDT)
Received: (qmail 26254 invoked from network); 6 Jul 2000 10:15:26 -0000
Received: from mailhost.puck.pipex.net (HELO mailhost.uk.internal) (194.130.147.54)
  by our.mail.pipex.net with SMTP; 6 Jul 2000 10:15:26 -0000
Received: (qmail 608 invoked from network); 6 Jul 2000 10:15:26 -0000
Received: from merlin.cam.uk.internal (HELO uk.uu.net) (172.31.3.9)
  by mailhost.uk.internal with SMTP; 6 Jul 2000 10:15:26 -0000
Message-ID: <39646A02.CACB8F8C@uk.uu.net>
Date: Thu, 06 Jul 2000 11:14:11 +0000
From: Stephen Burley <stephenb@uk.uu.net>
Organization: UUNET
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Kazu@venus.Sun.COM, Yamamoto@venus.Sun.COM
CC: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp,
        sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <20000706.172714.91311805.kazu@Mew.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Stephen Burley <stephenb@uk.uu.net>
Content-Transfer-Encoding: 7bit

"Kazu Yamamoto (山本和彦)" wrote:

> Folks,
>
> It seems to me that RTRs are going a wrong way, changing /48 per site
> policy. If you think so, please speak up on sig-ipv6@apnic.net now.
>
> --Kazu

Hi
    We discussed it at length in the RIPE 36 meeting and the majority not all
were not in favour of not fixing the boundries but rather allowing the LIR to
decide on merit/justification what amount of space to assign whithin the /48 -
/64 boundries. If we fixit to /48 /56 /64 boundries it becomes too rigid, allow

the LIR's to dictate their own assignment policy (ie flexible or fixed at 3
points /48 /56 /64) which they can justify to the RIR, in this way it pleases
everyone - i garuntee if you fix the boundries it will have to be re-addrressed

later on and will not please all.

My thoughts
Stephen Burley
UUNET EMEA Hostmaster

>
>
>   ------------------------------------------------------------------------
>
> Subject: [apnic-announce] IPv6 Policy Document Revision
> Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)
> From: secretariat@apnic.net
> Reply-To: apnic-talk@apnic.net
> To: apnic-announce@lists.apnic.net
>
> [Note "reply-to:" field]
>
> Summary
>
> Both ARIN and the RIPE NCC have had discussions with the Internet
> communities in their region concerning the size of address prefixes
> to be assigned to IPv6 end sites.  APNIC is now seeking input from
> the community in the Asia Pacific region on this issue. If you care
> about this, please read on.
>
> Some background
>
> The existing IPv6 policy document 'Provisional IPv6 Assignment and
> Allocation Policy Document' was published in May 1999. Formal revision
> of the document commenced in October 1999. The existing document
> is available at:
>
> http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html
>
> Feedback on the existing document was collected from the Internet community
> at large facilitated through the regional processes of consultation by
> the RIRs as well as input from the membership of the 6bone and the
> IETF IPv6 working groups. The deadline for comments was 31st January 2000.
>
> On 29th March, the RIRs, chairs of the IPv6 related IETF working
> groups and 6bone particpants met in Adelaide. The purpose of the meeting
> was to expand and elaborate in person on the comments made by the
> IAB/IETF/6bone concerning the existing policy document.
>
> One of the issues of concern that had been previously raised by
> members is the size of the end-site prefix (the 'SLA ID', currently
> defined in rfc2374 as 16 bits at a /48). This includes *all* types
> of end-sites including a single device. A /48 is sufficient address
> space to create 64K of subnets.
>
> The technical motivation for the 16 bit SLA ID field and the
> 'one size fits all' principle was described in rfc2374 as:
>
>   "The size of the Site-Level Aggregation Identifier field is 16 bits.
>    This supports 65,535 individual subnets per site.  The design goal
>    for the size of this field was to be sufficient for all but the
>    largest of organizations.  Organizations which need additional
>    subnets can arrange with the organization they are obtaining Internet
>    service from to obtain additional site identifiers and use this to
>    create additional subnets.
>
>    The Site-Level Aggregation Identifier field was given a fixed size in
>    order to force the length of all prefixes identifying a particular
>    site to be the same length (i.e., 48 bits).  This facilitates
>    movement of sites in the topology (e.g., changing service providers
>    and multi-homing to multiple service providers)."
>
> It is possible to imagine in future a variety of types of end-sites
> being connected to the Internet.  Some of these devices will be part
> of routed networks and others will not.  The question proposed is whether
> 'one size fits all' (the /48) is appropriate for all end-sites?
>
> Both the RIPE and ARIN communities have rejected this.
>
> APNIC has been asked to consult with the Internet community in the
> Asia Pacific on this issue.
>
> To date, there has been no consensus on what alternatives should be
> taken, but 3 different approaches have been identified in addition to
> the 16 bit SLA ID field specified in rfc2374.
>
> These are:
>
> 1) /64 for single devices (such as mobile phones), /48 for all other sites
>
> 2) /64 for single devices, /48 for large end sites which need more
>    than 256 subnets, and /56 for other sites (eg small, domestic/home sites)
>
> 3) Assign what is needed for the forseeable needs of the site, as a
>    variable-length prefix of between /48 and /64. (It is important to
>    remember that for any site that becomes multi-homed it is necessary to
>    use equal length prefixes from each provider even in the case where
>    one provider has allocated more prefix space than the other).
>
> We are interested in your opinions, so that we may convey this to the
> other RIRs and to the IETF community. Please direct all follow up
> discussion and comments to <sig-ipv6@apnic.net>. For details of
> how to subscribe to this mailing list, please visit our web site at:
> http://www.apnic.net/general.html#mailing-lists .
>
> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
> APNIC Secretariat
> <secretariat@apnic.net>
>                                                      Tel: +61-7-3367-0490
> Asia Pacific Network Information Centre (APNIC) Ltd  Fax: +61-7-3367-0482
> Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
>
> *            APNIC-ANNOUNCE: Announcements concerning APNIC              *
> * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net *

--
------------------------------------------------------------------------
Stephen Burley         "If patience is a virtue, and ignorance is bliss,
UUNET EMEA Hostmaster            you can have a pretty good life
Stephenb@uk.uu.net            if you're stupid and willing to wait"
------------------------------------------------------------------------





From owner-ngtrans@sunroof.eng.sun.com  Thu Jul  6 15:39:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24211
	for <ngtrans-archive@odin.ietf.org>; Thu, 6 Jul 2000 15:39:43 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA29288;
	Thu, 6 Jul 2000 13:39:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA14432;
	Thu, 6 Jul 2000 12:38:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e66JbXO25445
	for ngtrans-dist; Thu, 6 Jul 2000 12:37:33 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e66JX4625424;
	Thu, 6 Jul 2000 12:33:04 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA01871;
	Thu, 6 Jul 2000 12:33:02 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA23242;
	Thu, 6 Jul 2000 12:33:00 -0700 (PDT)
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 UAA14734; Thu, 6 Jul 2000 20:32:03 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id UAA15040; Thu, 6 Jul 2000 20:32:05 +0100 (BST)
Message-ID: <3964DE58.7DB92581@hursley.ibm.com>
Date: Thu, 06 Jul 2000 14:30: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: stephenb@uk.uu.net
CC: 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, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <20000706.172714.91311805.kazu@Mew.org> <39646A02.CACB8F8C@uk.uu.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Stephen,

Can you explain why people think there is any need to allocate anything
longer than a /48 in the first place? 

   Brian

Stephen Burley wrote:
> 
> "Kazu Yamamoto (山本和彦)" wrote:
> 
> > Folks,
> >
> > It seems to me that RTRs are going a wrong way, changing /48 per site
> > policy. If you think so, please speak up on sig-ipv6@apnic.net now.
> >
> > --Kazu
> 
> Hi
>     We discussed it at length in the RIPE 36 meeting and the majority not all
> were not in favour of not fixing the boundries but rather allowing the LIR to
> decide on merit/justification what amount of space to assign whithin the /48 -
> /64 boundries. If we fixit to /48 /56 /64 boundries it becomes too rigid, allow
> 
> the LIR's to dictate their own assignment policy (ie flexible or fixed at 3
> points /48 /56 /64) which they can justify to the RIR, in this way it pleases
> everyone - i garuntee if you fix the boundries it will have to be re-addrressed
> 
> later on and will not please all.
> 
> My thoughts
> Stephen Burley
> UUNET EMEA Hostmaster
> 
> >
> >
> >   ------------------------------------------------------------------------
> >
> > Subject: [apnic-announce] IPv6 Policy Document Revision
> > Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)
> > From: secretariat@apnic.net
> > Reply-To: apnic-talk@apnic.net
> > To: apnic-announce@lists.apnic.net
> >
> > [Note "reply-to:" field]
> >
> > Summary
> >
> > Both ARIN and the RIPE NCC have had discussions with the Internet
> > communities in their region concerning the size of address prefixes
> > to be assigned to IPv6 end sites.  APNIC is now seeking input from
> > the community in the Asia Pacific region on this issue. If you care
> > about this, please read on.
> >
> > Some background
> >
> > The existing IPv6 policy document 'Provisional IPv6 Assignment and
> > Allocation Policy Document' was published in May 1999. Formal revision
> > of the document commenced in October 1999. The existing document
> > is available at:
> >
> > http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html
> >
> > Feedback on the existing document was collected from the Internet community
> > at large facilitated through the regional processes of consultation by
> > the RIRs as well as input from the membership of the 6bone and the
> > IETF IPv6 working groups. The deadline for comments was 31st January 2000.
> >
> > On 29th March, the RIRs, chairs of the IPv6 related IETF working
> > groups and 6bone particpants met in Adelaide. The purpose of the meeting
> > was to expand and elaborate in person on the comments made by the
> > IAB/IETF/6bone concerning the existing policy document.
> >
> > One of the issues of concern that had been previously raised by
> > members is the size of the end-site prefix (the 'SLA ID', currently
> > defined in rfc2374 as 16 bits at a /48). This includes *all* types
> > of end-sites including a single device. A /48 is sufficient address
> > space to create 64K of subnets.
> >
> > The technical motivation for the 16 bit SLA ID field and the
> > 'one size fits all' principle was described in rfc2374 as:
> >
> >   "The size of the Site-Level Aggregation Identifier field is 16 bits.
> >    This supports 65,535 individual subnets per site.  The design goal
> >    for the size of this field was to be sufficient for all but the
> >    largest of organizations.  Organizations which need additional
> >    subnets can arrange with the organization they are obtaining Internet
> >    service from to obtain additional site identifiers and use this to
> >    create additional subnets.
> >
> >    The Site-Level Aggregation Identifier field was given a fixed size in
> >    order to force the length of all prefixes identifying a particular
> >    site to be the same length (i.e., 48 bits).  This facilitates
> >    movement of sites in the topology (e.g., changing service providers
> >    and multi-homing to multiple service providers)."
> >
> > It is possible to imagine in future a variety of types of end-sites
> > being connected to the Internet.  Some of these devices will be part
> > of routed networks and others will not.  The question proposed is whether
> > 'one size fits all' (the /48) is appropriate for all end-sites?
> >
> > Both the RIPE and ARIN communities have rejected this.
> >
> > APNIC has been asked to consult with the Internet community in the
> > Asia Pacific on this issue.
> >
> > To date, there has been no consensus on what alternatives should be
> > taken, but 3 different approaches have been identified in addition to
> > the 16 bit SLA ID field specified in rfc2374.
> >
> > These are:
> >
> > 1) /64 for single devices (such as mobile phones), /48 for all other sites
> >
> > 2) /64 for single devices, /48 for large end sites which need more
> >    than 256 subnets, and /56 for other sites (eg small, domestic/home sites)
> >
> > 3) Assign what is needed for the forseeable needs of the site, as a
> >    variable-length prefix of between /48 and /64. (It is important to
> >    remember that for any site that becomes multi-homed it is necessary to
> >    use equal length prefixes from each provider even in the case where
> >    one provider has allocated more prefix space than the other).
> >
> > We are interested in your opinions, so that we may convey this to the
> > other RIRs and to the IETF community. Please direct all follow up
> > discussion and comments to <sig-ipv6@apnic.net>. For details of
> > how to subscribe to this mailing list, please visit our web site at:
> > http://www.apnic.net/general.html#mailing-lists .
> >
> > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
> > APNIC Secretariat
> > <secretariat@apnic.net>
> >                                                      Tel: +61-7-3367-0490
> > Asia Pacific Network Information Centre (APNIC) Ltd  Fax: +61-7-3367-0482
> > Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
> > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
> >
> > *            APNIC-ANNOUNCE: Announcements concerning APNIC              *
> > * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net *
> 
> --
> ------------------------------------------------------------------------
> Stephen Burley         "If patience is a virtue, and ignorance is bliss,
> UUNET EMEA Hostmaster            you can have a pretty good life
> Stephenb@uk.uu.net            if you're stupid and willing to wait"
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul  6 17:30:53 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26001
	for <ngtrans-archive@odin.ietf.org>; Thu, 6 Jul 2000 17:30:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA14992;
	Thu, 6 Jul 2000 15:30:16 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA09869;
	Thu, 6 Jul 2000 14:28:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e66LRa125622
	for ngtrans-dist; Thu, 6 Jul 2000 14:27:36 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e66LPa625606;
	Thu, 6 Jul 2000 14:25:36 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA08981;
	Thu, 6 Jul 2000 14:25:37 -0700 (PDT)
Received: from roam.psg.com (mg-20425422-112.ricochet.net [204.254.22.112])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA11842;
	Thu, 6 Jul 2000 15:25:32 -0600 (MDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13AJ7o-0000rS-00; Thu, 06 Jul 2000 17:24:00 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Randy Bush <rbush@bainbridge.verio.net>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: 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, joao@ripe.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>
Message-Id: <E13AJ7o-0000rS-00@roam.psg.com>
Date: Thu, 06 Jul 2000 17:24:00 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <rbush@bainbridge.verio.net>
Content-Transfer-Encoding: 7bit

> Can you explain why people think there is any need to allocate anything
> longer than a /48 in the first place? 

i believe the document restricted it to single-device network allocations.
is a /64 too small for a single device?

randy


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul  6 18:39:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26910
	for <ngtrans-archive@odin.ietf.org>; Thu, 6 Jul 2000 18:39:00 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA29914;
	Thu, 6 Jul 2000 16:37:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA16210;
	Thu, 6 Jul 2000 15:37:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e66MZh425812
	for ngtrans-dist; Thu, 6 Jul 2000 15:35:43 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e66MXT625782;
	Thu, 6 Jul 2000 15:33:29 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA15467;
	Thu, 6 Jul 2000 15:33:28 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA27148;
	Thu, 6 Jul 2000 16:33:27 -0600 (MDT)
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 XAA54848; Thu, 6 Jul 2000 23:32:31 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id XAA21204; Thu, 6 Jul 2000 23:32:38 +0100 (BST)
Message-ID: <39650844.775A46AA@hursley.ibm.com>
Date: Thu, 06 Jul 2000 17:29:24 -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: Randy Bush <rbush@bainbridge.verio.net>
CC: 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, joao@ripe.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> <E13AJ7o-0000rS-00@roam.psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Well, I'm not sure the concept of single device will mean much.
For example, assuming we do IPv6 over BlueTooth right, what the
phone company thinks is a single device may turn out to be a personal
area network. Or a single 3GPP device might turn out to be three
LANs inside a car. But fundamentally I'm not sure the RIRs need to even
think about it; that question should be well below the horizon for
an RIR policy. IMHO.

  Brian

Randy Bush wrote:
> 
> > Can you explain why people think there is any need to allocate anything
> > longer than a /48 in the first place?
> 
> i believe the document restricted it to single-device network allocations.
> is a /64 too small for a single device?
> 
> randy


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 03:25:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16553
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 03:25:20 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA26154;
	Fri, 7 Jul 2000 01:24:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id AAA28404;
	Fri, 7 Jul 2000 00:24:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e677N6226148
	for ngtrans-dist; Fri, 7 Jul 2000 00:23:06 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e677Mw626141;
	Fri, 7 Jul 2000 00:22:58 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id AAA16215;
	Fri, 7 Jul 2000 00:22:57 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA25193;
	Fri, 7 Jul 2000 01:22:56 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e677Mh651864;
	Fri, 7 Jul 2000 09:22:44 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id JAA09833;
	Fri, 7 Jul 2000 09:22:42 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id JAA52803;
	Fri, 7 Jul 2000 09:22:23 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200007070722.JAA52803@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: stephenb@uk.uu.net, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-reply-to: Your message of Thu, 06 Jul 2000 14:30:32 CDT.
             <3964DE58.7DB92581@hursley.ibm.com> 
Date: Fri, 07 Jul 2000 09:22:23 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   Can you explain why people think there is any need to allocate anything
   longer than a /48 in the first place? 
   
=> many ISPs want to allocate /64 (or worse) to their customers... and
shout a /48 per customer is far too large. I believe this is a consequence
of the slow^N start, ie. the /35 rule (RIRs trim address space of ISPs,
ISPs take back the burden to their customers).
 The idea is to introduce a small site (/56) for "poor & little" customers
and to make it the *default* allocation. IMHO this is an acceptable target.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 04:17:39 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18583
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 04:17:39 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA13981;
	Fri, 7 Jul 2000 02:17:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA22737;
	Fri, 7 Jul 2000 01:16:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e678EP326307
	for ngtrans-dist; Fri, 7 Jul 2000 01:14:25 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e678E8626291;
	Fri, 7 Jul 2000 01:14:08 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA01865;
	Fri, 7 Jul 2000 01:14:05 -0700 (PDT)
From: matthew.ford@bt.com
Received: from gollum.axion.bt.co.uk (gollum.axion.bt.co.uk [132.146.17.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA03980;
	Fri, 7 Jul 2000 01:14:03 -0700 (PDT)
Received: from cbtlipnt01.btlabs.bt.co.uk by gollum (local) with ESMTP;
          Fri, 7 Jul 2000 09:14:20 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <3GLQPGR0>;
          Fri, 7 Jul 2000 09:13:07 +0100
Message-ID: <F66469FCE9C5D311B8FF0000F8FE9E0701178FA9@mbtlipnt03.btlabs.bt.co.uk>
To: Francis.Dupont@enst-bretagne.fr
Cc: stephenb@uk.uu.net, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net,
        brian@hursley.ibm.com, jonathan.2.stevens@bt.com, peter.hovell@bt.com
Subject: RE: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
Date: Fri, 7 Jul 2000 09:12:38 +0100 
X-Mailer: Internet Mail Service (5.5.2651.88)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: matthew.ford@bt.com

If /56 can be agreed upon as a default then that is not too bad IMO.
However, the RIRs seem to be veering towards allowing LIRs to allocate
whatever they choose between /48 and /64 - a movable boundary which will
scupper the technical objectives of multihoming and simplified
site-renumbering. I believe the idea of a movable boundary should be
strongly opposed for this reason.

Regards,

Mat Ford.

-----Original Message-----
From: Francis Dupont [mailto:Francis.Dupont@enst-bretagne.fr]
Sent: 07 July 2000 08:22
To: Brian E Carpenter
Cc: stephenb@uk.uu.net; ipng@sunroof.eng.sun.com;
ngtrans@sunroof.eng.sun.com; arano@byd.ocn.ad.jp; sig-ipv6@apnic.net;
mir@ripe.net; joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document
Revision 


 In your previous mail you wrote:

   Can you explain why people think there is any need to allocate anything
   longer than a /48 in the first place? 
   
=> many ISPs want to allocate /64 (or worse) to their customers... and
shout a /48 per customer is far too large. I believe this is a consequence
of the slow^N start, ie. the /35 rule (RIRs trim address space of ISPs,
ISPs take back the burden to their customers).
 The idea is to introduce a small site (/56) for "poor & little" customers
and to make it the *default* allocation. IMHO this is an acceptable target.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 04:45:35 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18895
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 04:45:34 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA25649;
	Fri, 7 Jul 2000 02:45:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA22111;
	Fri, 7 Jul 2000 01:44:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e678hX726393
	for ngtrans-dist; Fri, 7 Jul 2000 01:43:33 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e678hN626378
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 01:43:23 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA24632
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 01:43:21 -0700 (PDT)
Received: from boat.mail.pipex.net (our.mail.pipex.net [158.43.128.75])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id CAA24916
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 02:43:21 -0600 (MDT)
Received: (qmail 28045 invoked from network); 7 Jul 2000 08:43:20 -0000
Received: from mailhost.puck.pipex.net (HELO mailhost.uk.internal) (194.130.147.54)
  by our.mail.pipex.net with SMTP; 7 Jul 2000 08:43:20 -0000
Received: (qmail 7831 invoked from network); 7 Jul 2000 08:43:19 -0000
Received: from merlin.cam.uk.internal (HELO uk.uu.net) (172.31.3.9)
  by mailhost.uk.internal with SMTP; 7 Jul 2000 08:43:19 -0000
Message-ID: <3965A5F0.8505E7BA@uk.uu.net>
Date: Fri, 07 Jul 2000 09:42:08 +0000
From: Stephen Burley <stephenb@uk.uu.net>
Organization: UUNET
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian E Carpenter <brian@hursley.ibm.com>
CC: 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, joao@ripe.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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Stephen Burley <stephenb@uk.uu.net>
Content-Transfer-Encoding: 7bit

Brian E Carpenter wrote:

> Stephen,
>
> Can you explain why people think there is any need to allocate anything
> longer than a /48 in the first place?
>

Call me oldfashioned but i remember when people thought we had enough space in IPv4
and it would never run out. If you fix the boundry at a /48 it means an ISP will go
through their block of addresses way too fast. It also means that out customers do
not have to think about what they are deploying as they know they will get a /48 no
matter what. So a flexible boundry between /48 and /64 would help us to help
customers to think about how they will deploy their address space. 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.

Just my thoughts.



>
>    Brian
>
> Stephen Burley wrote:
> >
> > "Kazu Yamamoto (山本和彦)" wrote:
> >
> > > Folks,
> > >
> > > It seems to me that RTRs are going a wrong way, changing /48 per site
> > > policy. If you think so, please speak up on sig-ipv6@apnic.net now.
> > >
> > > --Kazu
> >
> > Hi
> >     We discussed it at length in the RIPE 36 meeting and the majority not all
> > were not in favour of not fixing the boundries but rather allowing the LIR to
> > decide on merit/justification what amount of space to assign whithin the /48 -
> > /64 boundries. If we fixit to /48 /56 /64 boundries it becomes too rigid, allow
> >
> > the LIR's to dictate their own assignment policy (ie flexible or fixed at 3
> > points /48 /56 /64) which they can justify to the RIR, in this way it pleases
> > everyone - i garuntee if you fix the boundries it will have to be re-addrressed
> >
> > later on and will not please all.
> >
> > My thoughts
> > Stephen Burley
> > UUNET EMEA Hostmaster
> >
> > >
> > >
> > >   ------------------------------------------------------------------------
> > >
> > > Subject: [apnic-announce] IPv6 Policy Document Revision
> > > Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)
> > > From: secretariat@apnic.net
> > > Reply-To: apnic-talk@apnic.net
> > > To: apnic-announce@lists.apnic.net
> > >
> > > [Note "reply-to:" field]
> > >
> > > Summary
> > >
> > > Both ARIN and the RIPE NCC have had discussions with the Internet
> > > communities in their region concerning the size of address prefixes
> > > to be assigned to IPv6 end sites.  APNIC is now seeking input from
> > > the community in the Asia Pacific region on this issue. If you care
> > > about this, please read on.
> > >
> > > Some background
> > >
> > > The existing IPv6 policy document 'Provisional IPv6 Assignment and
> > > Allocation Policy Document' was published in May 1999. Formal revision
> > > of the document commenced in October 1999. The existing document
> > > is available at:
> > >
> > > http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html
> > >
> > > Feedback on the existing document was collected from the Internet community
> > > at large facilitated through the regional processes of consultation by
> > > the RIRs as well as input from the membership of the 6bone and the
> > > IETF IPv6 working groups. The deadline for comments was 31st January 2000.
> > >
> > > On 29th March, the RIRs, chairs of the IPv6 related IETF working
> > > groups and 6bone particpants met in Adelaide. The purpose of the meeting
> > > was to expand and elaborate in person on the comments made by the
> > > IAB/IETF/6bone concerning the existing policy document.
> > >
> > > One of the issues of concern that had been previously raised by
> > > members is the size of the end-site prefix (the 'SLA ID', currently
> > > defined in rfc2374 as 16 bits at a /48). This includes *all* types
> > > of end-sites including a single device. A /48 is sufficient address
> > > space to create 64K of subnets.
> > >
> > > The technical motivation for the 16 bit SLA ID field and the
> > > 'one size fits all' principle was described in rfc2374 as:
> > >
> > >   "The size of the Site-Level Aggregation Identifier field is 16 bits.
> > >    This supports 65,535 individual subnets per site.  The design goal
> > >    for the size of this field was to be sufficient for all but the
> > >    largest of organizations.  Organizations which need additional
> > >    subnets can arrange with the organization they are obtaining Internet
> > >    service from to obtain additional site identifiers and use this to
> > >    create additional subnets.
> > >
> > >    The Site-Level Aggregation Identifier field was given a fixed size in
> > >    order to force the length of all prefixes identifying a particular
> > >    site to be the same length (i.e., 48 bits).  This facilitates
> > >    movement of sites in the topology (e.g., changing service providers
> > >    and multi-homing to multiple service providers)."
> > >
> > > It is possible to imagine in future a variety of types of end-sites
> > > being connected to the Internet.  Some of these devices will be part
> > > of routed networks and others will not.  The question proposed is whether
> > > 'one size fits all' (the /48) is appropriate for all end-sites?
> > >
> > > Both the RIPE and ARIN communities have rejected this.
> > >
> > > APNIC has been asked to consult with the Internet community in the
> > > Asia Pacific on this issue.
> > >
> > > To date, there has been no consensus on what alternatives should be
> > > taken, but 3 different approaches have been identified in addition to
> > > the 16 bit SLA ID field specified in rfc2374.
> > >
> > > These are:
> > >
> > > 1) /64 for single devices (such as mobile phones), /48 for all other sites
> > >
> > > 2) /64 for single devices, /48 for large end sites which need more
> > >    than 256 subnets, and /56 for other sites (eg small, domestic/home sites)
> > >
> > > 3) Assign what is needed for the forseeable needs of the site, as a
> > >    variable-length prefix of between /48 and /64. (It is important to
> > >    remember that for any site that becomes multi-homed it is necessary to
> > >    use equal length prefixes from each provider even in the case where
> > >    one provider has allocated more prefix space than the other).
> > >
> > > We are interested in your opinions, so that we may convey this to the
> > > other RIRs and to the IETF community. Please direct all follow up
> > > discussion and comments to <sig-ipv6@apnic.net>. For details of
> > > how to subscribe to this mailing list, please visit our web site at:
> > > http://www.apnic.net/general.html#mailing-lists .
> > >
> > > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
> > > APNIC Secretariat
> > > <secretariat@apnic.net>
> > >                                                      Tel: +61-7-3367-0490
> > > Asia Pacific Network Information Centre (APNIC) Ltd  Fax: +61-7-3367-0482
> > > Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
> > > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
> > >
> > > *            APNIC-ANNOUNCE: Announcements concerning APNIC              *
> > > * To unsubscribe, send "unsubscribe" to apnic-announce-request@apnic.net *
> >
> > --
> > ------------------------------------------------------------------------
> > Stephen Burley         "If patience is a virtue, and ignorance is bliss,
> > UUNET EMEA Hostmaster            you can have a pretty good life
> > Stephenb@uk.uu.net            if you're stupid and willing to wait"
> > ------------------------------------------------------------------------
> >
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                     http://playground.sun.com/ipng
> > FTP archive:                     ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------

--
------------------------------------------------------------------------
Stephen Burley         "If patience is a virtue, and ignorance is bliss,
UUNET EMEA Hostmaster            you can have a pretty good life
[SB855-RIPE]                 if you're stupid and willing to wait"
------------------------------------------------------------------------





From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 08:15:45 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22787
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 08:15:44 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA09009;
	Fri, 7 Jul 2000 06:15:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA15754;
	Fri, 7 Jul 2000 05:14:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67CDtF26567
	for ngtrans-dist; Fri, 7 Jul 2000 05:13:55 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67CBj626551;
	Fri, 7 Jul 2000 05:11:46 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA16214;
	Fri, 7 Jul 2000 05:11:42 -0700 (PDT)
Received: from ish7.ericsson.com.au ([203.61.155.111])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA28239;
	Fri, 7 Jul 2000 05:11:38 -0700 (PDT)
Received: from brsi02.epa.ericsson.se (brsi02 [146.11.15.8])
	by ish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id WAA28764;
	Fri, 7 Jul 2000 22:07:04 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019 [146.11.9.165])
	by brsi02.epa.ericsson.se (8.9.1/8.9.1) with ESMTP id WAA13723;
	Fri, 7 Jul 2000 22:08:09 +1000 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2650.21)
	id <3FW9RWGX>; Fri, 7 Jul 2000 22:07:58 +1000
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A5089EB0FF@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'Stephen Burley '" <stephenb@uk.uu.net>,
        "'Brian E Carpenter '"
	 <brian@hursley.ibm.com>
Cc: "'Kazu@venus.Sun.COM '" <Kazu@venus.Sun.COM>,
        "'Yamamoto@venus.Sun.COM '" <Yamamoto@venus.Sun.COM>,
        "'ipng@sunroof.eng.sun.com '" <ipng@sunroof.eng.sun.com>,
        "'ngtrans@sunroof.eng.sun.com '" <ngtrans@sunroof.eng.sun.com>,
        "'arano@byd.ocn.ad.jp '" <arano@byd.ocn.ad.jp>,
        "'sig-ipv6@apnic.net '"
	 <sig-ipv6@apnic.net>,
        "'mir@ripe.net '" <mir@ripe.net>, "'joao@ripe.net '" <joao@ripe.net>
Subject: RE: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Date: Fri, 7 Jul 2000 22:07:56 +1000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFE80B.FC30E3D0"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFE80B.FC30E3D0
Content-Type: text/plain

VERY true IMO



Call me oldfashioned but i remember when people thought we had enough
space in IPv4
and it would never run out. If you fix the boundry at a /48 it means an
ISP will go
through their block of addresses way too fast. It also means that out
customers do
not have to think about what they are deploying as they know they will
get a /48 no
matter what. So a flexible boundry between /48 and /64 would help us to
help
customers to think about how they will deploy their address space. 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.

Just my thoughts.





>
>    Brian
>
> Stephen Burley wrote:
> >
> > "Kazu Yamamoto (山本和彦)" wrote:
> >
> > > Folks,
> > >
> > > It seems to me that RTRs are going a wrong way, changing /48 per
site
> > > policy. If you think so, please speak up on sig-ipv6@apnic.net
now.
> > >
> > > --Kazu
> >
> > Hi
> >     We discussed it at length in the RIPE 36 meeting and the
majority not all
> > were not in favour of not fixing the boundries but rather allowing
the LIR to
> > decide on merit/justification what amount of space to assign whithin
the /48 -
> > /64 boundries. If we fixit to /48 /56 /64 boundries it becomes too
rigid, allow
> >
> > the LIR's to dictate their own assignment policy (ie flexible or
fixed at 3
> > points /48 /56 /64) which they can justify to the RIR, in this way
it pleases
> > everyone - i garuntee if you fix the boundries it will have to be
re-addrressed
> >
> > later on and will not please all.
> >
> > My thoughts
> > Stephen Burley
> > UUNET EMEA Hostmaster
> >
> > >
> > >
> > >
------------------------------------------------------------------------
> > >
> > > Subject: [apnic-announce] IPv6 Policy Document Revision
> > > Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)
> > > From: secretariat@apnic.net
> > > Reply-To: apnic-talk@apnic.net
> > > To: apnic-announce@lists.apnic.net
> > >
> > > [Note "reply-to:" field]
> > >
> > > Summary
> > >
> > > Both ARIN and the RIPE NCC have had discussions with the Internet
> > > communities in their region concerning the size of address
prefixes
> > > to be assigned to IPv6 end sites.  APNIC is now seeking input from
> > > the community in the Asia Pacific region on this issue. If you
care
> > > about this, please read on.
> > >
> > > Some background
> > >
> > > The existing IPv6 policy document 'Provisional IPv6 Assignment and
> > > Allocation Policy Document' was published in May 1999. Formal
revision
> > > of the document commenced in October 1999. The existing document
> > > is available at:
> > >
> > > http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html
> > >
> > > Feedback on the existing document was collected from the Internet
community
> > > at large facilitated through the regional processes of
consultation by
> > > the RIRs as well as input from the membership of the 6bone and the
> > > IETF IPv6 working groups. The deadline for comments was 31st
January 2000.
> > >
> > > On 29th March, the RIRs, chairs of the IPv6 related IETF working
> > > groups and 6bone particpants met in Adelaide. The purpose of the
meeting
> > > was to expand and elaborate in person on the comments made by the
> > > IAB/IETF/6bone concerning the existing policy document.
> > >
> > > One of the issues of concern that had been previously raised by
> > > members is the size of the end-site prefix (the 'SLA ID',
currently
> > > defined in rfc2374 as 16 bits at a /48). This includes *all* types
> > > of end-sites including a single device. A /48 is sufficient
address
> > > space to create 64K of subnets.
> > >
> > > The technical motivation for the 16 bit SLA ID field and the
> > > 'one size fits all' principle was described in rfc2374 as:
> > >
> > >   "The size of the Site-Level Aggregation Identifier field is 16
bits.
> > >    This supports 65,535 individual subnets per site.  The design
goal
> > >    for the size of this field was to be sufficient for all but the
> > >    largest of organizations.  Organizations which need additional
> > >    subnets can arrange with the organization they are obtaining
Internet
> > >    service from to obtain additional site identifiers and use this
to
> > >    create additional subnets.
> > >
> > >    The Site-Level Aggregation Identifier field was given a fixed
size in
> > >    order to force the length of all prefixes identifying a
particular
> > >    site to be the same length (i.e., 48 bits).  This facilitates
> > >    movement of sites in the topology (e.g., changing service
providers
> > >    and multi-homing to multiple service providers)."
> > >
> > > It is possible to imagine in future a variety of types of
end-sites
> > > being connected to the Internet.  Some of these devices will be
part
> > > of routed networks and others will not.  The question proposed is
whether
> > > 'one size fits all' (the /48) is appropriate for all end-sites?
> > >
> > > Both the RIPE and ARIN communities have rejected this.
> > >
> > > APNIC has been asked to consult with the Internet community in the
> > > Asia Pacific on this issue.
> > >
> > > To date, there has been no consensus on what alternatives should
be
> > > taken, but 3 different approaches have been identified in addition
to
> > > the 16 bit SLA ID field specified in rfc2374.
> > >
> > > These are:
> > >
> > > 1) /64 for single devices (such as mobile phones), /48 for all
other sites
> > >
> > > 2) /64 for single devices, /48 for large end sites which need more
> > >    than 256 subnets, and /56 for other sites (eg small,
domestic/home sites)
> > >
> > > 3) Assign what is needed for the forseeable needs of the site, as
a
> > >    variable-length prefix of between /48 and /64. (It is important
to
> > >    remember that for any site that becomes multi-homed it is
necessary to
> > >    use equal length prefixes from each provider even in the case
where
> > >    one provider has allocated more prefix space than the other).
> > >
> > > We are interested in your opinions, so that we may convey this to
the
> > > other RIRs and to the IETF community. Please direct all follow up
> > > discussion and comments to <sig-ipv6@apnic.net>. For details of
> > > how to subscribe to this mailing list, please visit our web site
at:
> > > http://www.apnic.net/general.html#mailing-lists .
> > >
> > > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + +
> > > APNIC Secretariat
> > > <secretariat@apnic.net>
> > >                                                      Tel:
+61-7-3367-0490
> > > Asia Pacific Network Information Centre (APNIC) Ltd  Fax:
+61-7-3367-0482
> > > Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia
> > > + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + +
> > >
> > > *            APNIC-ANNOUNCE: Announcements concerning APNIC
*
> > > * To unsubscribe, send "unsubscribe" to
apnic-announce-request@apnic.net *
> >
> > --
> >
------------------------------------------------------------------------
> > Stephen Burley         "If patience is a virtue, and ignorance is
bliss,
> > UUNET EMEA Hostmaster            you can have a pretty good life
> > Stephenb@uk.uu.net            if you're stupid and willing to wait"
> >
------------------------------------------------------------------------
> >
> > --------------------------------------------------------------------
> > IETF IPng Working Group Mailing List
> > IPng Home Page:                     http://playground.sun.com/ipng
> > FTP archive:                     ftp://playground.sun.com/pub/ipng
> > Direct all administrative requests to majordomo@sunroof.eng.sun.com
> > --------------------------------------------------------------------

--
------------------------------------------------------------------------
Stephen Burley         "If patience is a virtue, and ignorance is bliss,
UUNET EMEA Hostmaster            you can have a pretty good life
[SB855-RIPE]                 if you're stupid and willing to wait"
------------------------------------------------------------------------



------_=_NextPart_001_01BFE80B.FC30E3D0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>VERY true IMO</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=2>Call me oldfashioned but i remember when people thought we had enough</FONT>
<BR><FONT SIZE=2>space in IPv4</FONT>
<BR><FONT SIZE=2>and it would never run out. If you fix the boundry at a /48 it means an</FONT>
<BR><FONT SIZE=2>ISP will go</FONT>
<BR><FONT SIZE=2>through their block of addresses way too fast. It also means that out</FONT>
<BR><FONT SIZE=2>customers do</FONT>
<BR><FONT SIZE=2>not have to think about what they are deploying as they know they will</FONT>
<BR><FONT SIZE=2>get a /48 no</FONT>
<BR><FONT SIZE=2>matter what. So a flexible boundry between /48 and /64 would help us to</FONT>
<BR><FONT SIZE=2>help</FONT>
<BR><FONT SIZE=2>customers to think about how they will deploy their address space. A /64</FONT>
<BR><FONT SIZE=2>for dialup</FONT>
<BR><FONT SIZE=2>is also too rigid because the way technology is going a /64 is not going</FONT>
<BR><FONT SIZE=2>to be</FONT>
<BR><FONT SIZE=2>enough subnets for what wiill be a dial up connection with a large lan</FONT>
<BR><FONT SIZE=2>behind it.</FONT>
</P>

<P><FONT SIZE=2>Just my thoughts.</FONT>
</P>
<BR>
<BR>
<BR>
<BR>

<P><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt;&nbsp;&nbsp;&nbsp; Brian</FONT>
<BR><FONT SIZE=2>&gt;</FONT>
<BR><FONT SIZE=2>&gt; Stephen Burley wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &quot;Kazu Yamamoto (山本和彦)&quot; wrote:</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Folks,</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; It seems to me that RTRs are going a wrong way, changing /48 per</FONT>
<BR><FONT SIZE=2>site</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; policy. If you think so, please speak up on sig-ipv6@apnic.net</FONT>
<BR><FONT SIZE=2>now.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; --Kazu</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; Hi</FONT>
<BR><FONT SIZE=2>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; We discussed it at length in the RIPE 36 meeting and the</FONT>
<BR><FONT SIZE=2>majority not all</FONT>
<BR><FONT SIZE=2>&gt; &gt; were not in favour of not fixing the boundries but rather allowing</FONT>
<BR><FONT SIZE=2>the LIR to</FONT>
<BR><FONT SIZE=2>&gt; &gt; decide on merit/justification what amount of space to assign whithin</FONT>
<BR><FONT SIZE=2>the /48 -</FONT>
<BR><FONT SIZE=2>&gt; &gt; /64 boundries. If we fixit to /48 /56 /64 boundries it becomes too</FONT>
<BR><FONT SIZE=2>rigid, allow</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; the LIR's to dictate their own assignment policy (ie flexible or</FONT>
<BR><FONT SIZE=2>fixed at 3</FONT>
<BR><FONT SIZE=2>&gt; &gt; points /48 /56 /64) which they can justify to the RIR, in this way</FONT>
<BR><FONT SIZE=2>it pleases</FONT>
<BR><FONT SIZE=2>&gt; &gt; everyone - i garuntee if you fix the boundries it will have to be</FONT>
<BR><FONT SIZE=2>re-addrressed</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; later on and will not please all.</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; My thoughts</FONT>
<BR><FONT SIZE=2>&gt; &gt; Stephen Burley</FONT>
<BR><FONT SIZE=2>&gt; &gt; UUNET EMEA Hostmaster</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>------------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Subject: [apnic-announce] IPv6 Policy Document Revision</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Date: Wed, 5 Jul 2000 17:24:24 +1000 (EST)</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; From: secretariat@apnic.net</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Reply-To: apnic-talk@apnic.net</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; To: apnic-announce@lists.apnic.net</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; [Note &quot;reply-to:&quot; field]</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Summary</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Both ARIN and the RIPE NCC have had discussions with the Internet</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; communities in their region concerning the size of address</FONT>
<BR><FONT SIZE=2>prefixes</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; to be assigned to IPv6 end sites.&nbsp; APNIC is now seeking input from</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; the community in the Asia Pacific region on this issue. If you</FONT>
<BR><FONT SIZE=2>care</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; about this, please read on.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Some background</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; The existing IPv6 policy document 'Provisional IPv6 Assignment and</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Allocation Policy Document' was published in May 1999. Formal</FONT>
<BR><FONT SIZE=2>revision</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of the document commenced in October 1999. The existing document</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; is available at:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; <A HREF="http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html" TARGET="_blank">http://www.apnic.net/drafts/ipv6/ipv6-policy-280599.html</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Feedback on the existing document was collected from the Internet</FONT>
<BR><FONT SIZE=2>community</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; at large facilitated through the regional processes of</FONT>
<BR><FONT SIZE=2>consultation by</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; the RIRs as well as input from the membership of the 6bone and the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; IETF IPv6 working groups. The deadline for comments was 31st</FONT>
<BR><FONT SIZE=2>January 2000.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; On 29th March, the RIRs, chairs of the IPv6 related IETF working</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; groups and 6bone particpants met in Adelaide. The purpose of the</FONT>
<BR><FONT SIZE=2>meeting</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; was to expand and elaborate in person on the comments made by the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; IAB/IETF/6bone concerning the existing policy document.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; One of the issues of concern that had been previously raised by</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; members is the size of the end-site prefix (the 'SLA ID',</FONT>
<BR><FONT SIZE=2>currently</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; defined in rfc2374 as 16 bits at a /48). This includes *all* types</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of end-sites including a single device. A /48 is sufficient</FONT>
<BR><FONT SIZE=2>address</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; space to create 64K of subnets.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; The technical motivation for the 16 bit SLA ID field and the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; 'one size fits all' principle was described in rfc2374 as:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp; &quot;The size of the Site-Level Aggregation Identifier field is 16</FONT>
<BR><FONT SIZE=2>bits.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; This supports 65,535 individual subnets per site.&nbsp; The design</FONT>
<BR><FONT SIZE=2>goal</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; for the size of this field was to be sufficient for all but the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; largest of organizations.&nbsp; Organizations which need additional</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; subnets can arrange with the organization they are obtaining</FONT>
<BR><FONT SIZE=2>Internet</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; service from to obtain additional site identifiers and use this</FONT>
<BR><FONT SIZE=2>to</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; create additional subnets.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; The Site-Level Aggregation Identifier field was given a fixed</FONT>
<BR><FONT SIZE=2>size in</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; order to force the length of all prefixes identifying a</FONT>
<BR><FONT SIZE=2>particular</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; site to be the same length (i.e., 48 bits).&nbsp; This facilitates</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; movement of sites in the topology (e.g., changing service</FONT>
<BR><FONT SIZE=2>providers</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; and multi-homing to multiple service providers).&quot;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; It is possible to imagine in future a variety of types of</FONT>
<BR><FONT SIZE=2>end-sites</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; being connected to the Internet.&nbsp; Some of these devices will be</FONT>
<BR><FONT SIZE=2>part</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; of routed networks and others will not.&nbsp; The question proposed is</FONT>
<BR><FONT SIZE=2>whether</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; 'one size fits all' (the /48) is appropriate for all end-sites?</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Both the RIPE and ARIN communities have rejected this.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; APNIC has been asked to consult with the Internet community in the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Asia Pacific on this issue.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; To date, there has been no consensus on what alternatives should</FONT>
<BR><FONT SIZE=2>be</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; taken, but 3 different approaches have been identified in addition</FONT>
<BR><FONT SIZE=2>to</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; the 16 bit SLA ID field specified in rfc2374.</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; These are:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; 1) /64 for single devices (such as mobile phones), /48 for all</FONT>
<BR><FONT SIZE=2>other sites</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; 2) /64 for single devices, /48 for large end sites which need more</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; than 256 subnets, and /56 for other sites (eg small,</FONT>
<BR><FONT SIZE=2>domestic/home sites)</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; 3) Assign what is needed for the forseeable needs of the site, as</FONT>
<BR><FONT SIZE=2>a</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; variable-length prefix of between /48 and /64. (It is important</FONT>
<BR><FONT SIZE=2>to</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; remember that for any site that becomes multi-homed it is</FONT>
<BR><FONT SIZE=2>necessary to</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; use equal length prefixes from each provider even in the case</FONT>
<BR><FONT SIZE=2>where</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp; one provider has allocated more prefix space than the other).</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; We are interested in your opinions, so that we may convey this to</FONT>
<BR><FONT SIZE=2>the</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; other RIRs and to the IETF community. Please direct all follow up</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; discussion and comments to &lt;sig-ipv6@apnic.net&gt;. For details of</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; how to subscribe to this mailing list, please visit our web site</FONT>
<BR><FONT SIZE=2>at:</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; <A HREF="http://www.apnic.net/general.html#mailing-lists" TARGET="_blank">http://www.apnic.net/general.html#mailing-lists</A> .</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +</FONT>
<BR><FONT SIZE=2>+ + + +</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; APNIC Secretariat</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; &lt;secretariat@apnic.net&gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tel:</FONT>
<BR><FONT SIZE=2>+61-7-3367-0490</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Asia Pacific Network Information Centre (APNIC) Ltd&nbsp; Fax:</FONT>
<BR><FONT SIZE=2>+61-7-3367-0482</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; Level 1, 33 Park Road, PO Box 2131, Milton, QLD 4064, Australia</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +</FONT>
<BR><FONT SIZE=2>+ + + +</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; APNIC-ANNOUNCE: Announcements concerning APNIC</FONT>
<BR><FONT SIZE=2>*</FONT>
<BR><FONT SIZE=2>&gt; &gt; &gt; * To unsubscribe, send &quot;unsubscribe&quot; to</FONT>
<BR><FONT SIZE=2>apnic-announce-request@apnic.net *</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; --</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>------------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>&gt; &gt; Stephen Burley&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;If patience is a virtue, and ignorance is</FONT>
<BR><FONT SIZE=2>bliss,</FONT>
<BR><FONT SIZE=2>&gt; &gt; UUNET EMEA Hostmaster&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; you can have a pretty good life</FONT>
<BR><FONT SIZE=2>&gt; &gt; Stephenb@uk.uu.net&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if you're stupid and willing to wait&quot;</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>------------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>&gt; &gt;</FONT>
<BR><FONT SIZE=2>&gt; &gt; --------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>&gt; &gt; IETF IPng Working Group Mailing List</FONT>
<BR><FONT SIZE=2>&gt; &gt; IPng Home Page:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A HREF="http://playground.sun.com/ipng" TARGET="_blank">http://playground.sun.com/ipng</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; FTP archive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A HREF="ftp://playground.sun.com/pub/ipng" TARGET="_blank">ftp://playground.sun.com/pub/ipng</A></FONT>
<BR><FONT SIZE=2>&gt; &gt; Direct all administrative requests to majordomo@sunroof.eng.sun.com</FONT>
<BR><FONT SIZE=2>&gt; &gt; --------------------------------------------------------------------</FONT>
</P>

<P><FONT SIZE=2>--</FONT>
<BR><FONT SIZE=2>------------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>Stephen Burley&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;If patience is a virtue, and ignorance is bliss,</FONT>
<BR><FONT SIZE=2>UUNET EMEA Hostmaster&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; you can have a pretty good life</FONT>
<BR><FONT SIZE=2>[SB855-RIPE]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if you're stupid and willing to wait&quot;</FONT>
<BR><FONT SIZE=2>------------------------------------------------------------------------</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01BFE80B.FC30E3D0--


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 09:00:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24308
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 09:00:29 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA29068;
	Fri, 7 Jul 2000 06:59:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA07481;
	Fri, 7 Jul 2000 05:59:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67CwUt26645
	for ngtrans-dist; Fri, 7 Jul 2000 05:58:30 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Cw7626629;
	Fri, 7 Jul 2000 05:58:07 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA19341;
	Fri, 7 Jul 2000 05:58:07 -0700 (PDT)
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA15870;
	Fri, 7 Jul 2000 05:58:06 -0700 (PDT)
Received: from penelope.ecs.soton.ac.uk (penelope.ecs.soton.ac.uk [152.78.68.135])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id NAA21372;
	Fri, 7 Jul 2000 13:57:31 +0100 (BST)
Received: from penelope (penelope [152.78.68.135])
	by penelope.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id NAA22006;
	Fri, 7 Jul 2000 13:57:31 +0100 (BST)
Date: Fri, 7 Jul 2000 13:57:30 +0100 (BST)
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
cc: Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
In-Reply-To: <200007070722.JAA52803@givry.rennes.enst-bretagne.fr>
Message-ID: <Pine.SOL.4.20.0007071347150.16436-100000@penelope.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Tim Chown <tjc@ecs.soton.ac.uk>


I agree with Francis' comment on the /35 allocations.  If the /29
allocations were made in full from the outset there would be less
pressure at the other end...

In the case of a national educational network (my particular interest)
we currently have just 13 bits of network space to allocate to
institutions, if the institutions (Universities) get a /48 each.  At 
the same time it is bizarre that a University might get the same address 
space as a small end customer.  It is also likely that some Universities 
will command more than one /48, particularly if highly distributed.
If we have single (or multiple) subnets per room (at worst a cheap 
wireless access point per room), that /48 will look small very fast.

At present, the foreseeable allocations seem to offer little room for
the second-layer ISPs (e.g. the Universities).   It's almost as if we're
being painted into a corner by the initial 2001:: allocation and the
committment (rightly or wrongly) by the registries to ensure there are 
only 8K (13 bits) of top level routes in the DFZ, while at the same time
hedging their bets via the /35 strategy.

The last thing we want is end users running IPv6 NAT.

tim

On Fri, 7 Jul 2000, Francis Dupont wrote:

>  In your previous mail you wrote:
>    
> => many ISPs want to allocate /64 (or worse) to their customers... and
> shout a /48 per customer is far too large. I believe this is a consequence
> of the slow^N start, ie. the /35 rule (RIRs trim address space of ISPs,
> ISPs take back the burden to their customers).
>  The idea is to introduce a small site (/56) for "poor & little" customers
> and to make it the *default* allocation. IMHO this is an acceptable target.
> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 09:01:07 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24394
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 09:01:07 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA29415;
	Fri, 7 Jul 2000 07:00:36 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA10912;
	Fri, 7 Jul 2000 06:00:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67Cwxx26653
	for ngtrans-dist; Fri, 7 Jul 2000 05:58:59 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Cuf626619;
	Fri, 7 Jul 2000 05:56:41 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA07249;
	Fri, 7 Jul 2000 05:56:41 -0700 (PDT)
Received: from roam.psg.com (cnri-2-112.cnri.reston.va.us [132.151.2.112])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA15338;
	Fri, 7 Jul 2000 05:56:41 -0700 (PDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13AXgH-0001FT-00; Fri, 07 Jul 2000 08:56:33 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Randy Bush <rbush@bainbridge.verio.net>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Cc: Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
References: <3964DE58.7DB92581@hursley.ibm.com>
	<200007070722.JAA52803@givry.rennes.enst-bretagne.fr>
Message-Id: <E13AXgH-0001FT-00@roam.psg.com>
Date: Fri, 07 Jul 2000 08:56:33 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <rbush@bainbridge.verio.net>
Content-Transfer-Encoding: 7bit

> => many ISPs want to allocate /64 (or worse) to their customers... and
> shout a /48 per customer is far too large. I believe this is a consequence
> of the slow^N start, ie. the /35 rule (RIRs trim address space of ISPs,
> ISPs take back the burden to their customers).

someone who gets it!  the /35 game sucks.

randy


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 11:00:55 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28577
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 11:00:54 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04980;
	Fri, 7 Jul 2000 08:59:53 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA02180;
	Fri, 7 Jul 2000 07:59:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67Evnw26794
	for ngtrans-dist; Fri, 7 Jul 2000 07:57:49 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Evf626787;
	Fri, 7 Jul 2000 07:57:42 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA06030;
	Fri, 7 Jul 2000 07:57:40 -0700 (PDT)
Received: from popcorn.cisco.com (popcorn.cisco.com [171.69.18.32])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA03473;
	Fri, 7 Jul 2000 08:57:39 -0600 (MDT)
Received: from [10.19.130.188] (deering-dsl3.cisco.com [10.19.130.188])
	by popcorn.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id HAA12583;
	Fri, 7 Jul 2000 07:49:47 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220802b58b9b380355@[10.19.130.188]>
In-Reply-To: 
 <Pine.SOL.4.20.0007071347150.16436-100000@penelope.ecs.soton.ac.uk>
References: 
 <Pine.SOL.4.20.0007071347150.16436-100000@penelope.ecs.soton.ac.uk>
Date: Fri, 7 Jul 2000 07:51:19 -0700
To: Tim Chown <tjc@ecs.soton.ac.uk>
From: Steve Deering <deering@cisco.com>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Cc: Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
        Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 1:57 PM +0100 7/7/00, Tim Chown wrote:
>In the case of a national educational network (my particular interest)
>we currently have just 13 bits of network space to allocate to
>institutions, if the institutions (Universities) get a /48 each.

Tim,

/48 was intended to be the *minimum* allocation to a subscriber's site, not
the *maximum*.  Those exceptional subscribers for whom a /48 is too small
are free to request larger blocks from their ISPs.

>At the same time it is bizarre that a University might get the same address 
>space as a small end customer.

It's only "bizarre" if address space is a scarce resource; the purpose and
design of IPv6 was to make it a non-scarce resource.

>The last thing we want is end users running IPv6 NAT.

I think (hope) we all agree on that, and that is one of the reasons to
oppose variable-length allocations to (all but the largest) subscribers.
IPv4 history indicates that ISPs would charge more money for shorter
prefixes, thus creating an economic incentive for many customers to buy
only the smallest amount of address space and use a NAT to expand it locally.

Steve



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 11:38:06 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00018
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 11:38:05 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00022;
	Fri, 7 Jul 2000 09:36:44 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA14966;
	Fri, 7 Jul 2000 08:35:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67FYeA26948
	for ngtrans-dist; Fri, 7 Jul 2000 08:34:40 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67FWB626930;
	Fri, 7 Jul 2000 08:32:11 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA13744;
	Fri, 7 Jul 2000 08:32:10 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA08247;
	Fri, 7 Jul 2000 08:32:07 -0700 (PDT)
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 QAA173712; Fri, 7 Jul 2000 16:31:06 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA21864; Fri, 7 Jul 2000 16:31:15 +0100 (BST)
Message-ID: <3965F75D.E9B4FF6A@hursley.ibm.com>
Date: Fri, 07 Jul 2000 10:29:33 -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: Stephen Burley <stephenb@uk.uu.net>
CC: 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, joao@ripe.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>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Stephen Burley wrote:
> 
> Brian E Carpenter wrote:
> 
> > Stephen,
> >
> > Can you explain why people think there is any need to allocate anything
> > longer than a /48 in the first place?
> >
> 
> Call me oldfashioned but i remember when people thought we had enough space in IPv4
> and it would never run out. If you fix the boundry at a /48 it means an ISP will go
> through their block of addresses way too fast. 

Please define "way too fast" in terms of a world population of say 15 billion
people, compared with the number of /48s available.

> It also means that out customers do
> not have to think about what they are deploying as they know they will get a /48 no
> matter what. 

Indeed. This would be a *big* advantage. Why do think it is a problem?

> So a flexible boundry between /48 and /64 would help us to help
> customers to think about how they will deploy their address space. 

But it will also set us back by ten years in route aggregation.

> 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. 

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 11:59:30 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00923
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 11:59:29 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA14970;
	Fri, 7 Jul 2000 09:58:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA00612;
	Fri, 7 Jul 2000 08:58:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67Fv6P27025
	for ngtrans-dist; Fri, 7 Jul 2000 08:57:06 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Fux627018;
	Fri, 7 Jul 2000 08:56:59 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA00336;
	Fri, 7 Jul 2000 08:56:58 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA23902;
	Fri, 7 Jul 2000 08:56:57 -0700 (PDT)
Received: from hunkular.glarp.com (localhost [127.0.0.1])
	by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id JAA01092;
	Fri, 7 Jul 2000 09:56:23 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200007071556.JAA01092@hunkular.glarp.com>
To: Steve Deering <deering@cisco.com>
cc: Tim Chown <tjc@ecs.soton.ac.uk>,
        Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
        Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: Your message of "Fri, 07 Jul 2000 07:51:19 PDT."
             <v04220802b58b9b380355@[10.19.130.188]> 
Date: Fri, 07 Jul 2000 09:56:23 -0600
From: Brad Huntting <huntting@hunkular.glarp.com>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brad Huntting <huntting@hunkular.glarp.com>


> It's only "bizarre" if address space is a scarce resource; the purpose and
> design of IPv6 was to make it a non-scarce resource.

IMHO, the problem lies with using /64 for the default subnet size;
/80 would probably be more than enough for any conceivable "layer
2" protocol.


brad


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:19:05 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01841
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:19:04 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA28064;
	Fri, 7 Jul 2000 10:18:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA24897;
	Fri, 7 Jul 2000 09:17:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67GGPu27101
	for ngtrans-dist; Fri, 7 Jul 2000 09:16:26 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67GGG627094;
	Fri, 7 Jul 2000 09:16:17 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA05629;
	Fri, 7 Jul 2000 09:16:16 -0700 (PDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA05783;
	Fri, 7 Jul 2000 09:16:11 -0700 (PDT)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id QA29127;
	Sat, 8 Jul 2000 02:15:58 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: Brad Huntting <huntting@hunkular.glarp.com>
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: Your message of "Fri, 07 Jul 2000 09:56:23 CST."
             <200007071556.JAA01092@hunkular.glarp.com> 
Date: Sat, 08 Jul 2000 02:15:57 +1000
Message-Id: <16970.962986557@mundamutti.cs.mu.OZ.AU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Robert Elz <kre@munnari.OZ.AU>

    Date:        Fri, 07 Jul 2000 09:56:23 -0600
    From:        Brad Huntting <huntting@hunkular.glarp.com>
    Message-ID:  <200007071556.JAA01092@hunkular.glarp.com>

  | IMHO, the problem lies with using /64 for the default subnet size;

There is no real "problem".   No-one who has ever actually looked
at the numbers believes there is a problem with /48 allocations to
sites (though I personally have no problem considering a pool of
dial in users to be a single site if they have no need for more than
a /64 each).

The "we have to conserve those 2^48 numbers" comes from the same
kind of philosophy as the people who bought a 2 bedroom house, then
had 3 kids, and all of them had to share a bedroom.   That was a
problem, so then they bought a 500 room hotel - but still made the
kids share a room, because they ran out before, and they were
going to make certain that would never happen again.

  | /80 would probably be more than enough for any conceivable "layer
  | 2" protocol.

Except that IEEE has created 64 bit MAC identifiers for use by its
new protocols, and /80 would kill easy autoconf.   For sure, /80
(even /96) leaves way too many addresses for any conceivable subnet
to ever use them all - but making things fit in less is more work
that it is worth.

kre


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:30:12 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02412
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:30:11 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA05842;
	Fri, 7 Jul 2000 10:29:06 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA14308;
	Fri, 7 Jul 2000 09:28:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67GR2V27186
	for ngtrans-dist; Fri, 7 Jul 2000 09:27:02 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67GPM627170;
	Fri, 7 Jul 2000 09:25:23 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA13536;
	Fri, 7 Jul 2000 09:25:21 -0700 (PDT)
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA11039;
	Fri, 7 Jul 2000 09:25:20 -0700 (PDT)
Received: from penelope.ecs.soton.ac.uk (penelope.ecs.soton.ac.uk [152.78.68.135])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id RAA22528;
	Fri, 7 Jul 2000 17:25:09 +0100 (BST)
Received: from penelope (penelope [152.78.68.135])
	by penelope.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id RAA26604;
	Fri, 7 Jul 2000 17:25:08 +0100 (BST)
Date: Fri, 7 Jul 2000 17:25:08 +0100 (BST)
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Steve Deering <deering@cisco.com>
cc: Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
        Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
In-Reply-To: <v04220802b58b9b380355@[10.19.130.188]>
Message-ID: <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Tim Chown <tjc@ecs.soton.ac.uk>

On Fri, 7 Jul 2000, Steve Deering wrote:

> /48 was intended to be the *minimum* allocation to a subscriber's site, not
> the *maximum*.  Those exceptional subscribers for whom a /48 is too small
> are free to request larger blocks from their ISPs.

But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
to offer a /40 to each University it would at present be looking at being
able to connect just 32 Universities.   By 2001 there will be over 800
University and further education colleges online under the UK JANET network.
Of course they're not all big, varying from maybe 4,000 to 40,000 people,
so most could live under a /48.  At least with the current technology that
lives around us.

I would be interested to know what the addressing requirements of a mobile 
provider would be, in terms of scale and subnetting.  What would the 
"home prefix" of 1,000,000 Vodaphone customers be, for example?  I've
not yet seen a draft IPv6 allocation policy for a mobile provider.

tim



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:48:34 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03295
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:48:33 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA18984;
	Fri, 7 Jul 2000 10:47:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA01125;
	Fri, 7 Jul 2000 09:46:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67GjTw27268
	for ngtrans-dist; Fri, 7 Jul 2000 09:45:29 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67GhG627253;
	Fri, 7 Jul 2000 09:43:16 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA25513;
	Fri, 7 Jul 2000 09:43:15 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA21852;
	Fri, 7 Jul 2000 09:43:13 -0700 (PDT)
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 RAA21626; Fri, 7 Jul 2000 17:42:15 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA24104; Fri, 7 Jul 2000 17:42:25 +0100 (BST)
Message-ID: <39660803.C8EECA45@hursley.ibm.com>
Date: Fri, 07 Jul 2000 11:40:35 -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: Tim Chown <tjc@ecs.soton.ac.uk>
CC: Steve Deering <deering@cisco.com>,
        Francis Dupont <Francis.Dupont@enst-bretagne.fr>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Tim Chown wrote:
...
> I would be interested to know what the addressing requirements of a mobile
> provider would be, in terms of scale and subnetting.  What would the
> "home prefix" of 1,000,000 Vodaphone customers be, for example?  I've
> not yet seen a draft IPv6 allocation policy for a mobile provider.

Good question but it's certainly not a problem unless needlessly
restrictive allocation policies make it so. 1M is a small number in IPv6 land.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:50:18 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03419
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:50:17 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA20353;
	Fri, 7 Jul 2000 10:49:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA18413;
	Fri, 7 Jul 2000 09:47:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67Gk5X27284
	for ngtrans-dist; Fri, 7 Jul 2000 09:46:05 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Gjo627277;
	Fri, 7 Jul 2000 09:45:50 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA18008;
	Fri, 7 Jul 2000 09:45:45 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA17508;
	Fri, 7 Jul 2000 10:45:43 -0600 (MDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id BAA14012;
	Sat, 8 Jul 2000 01:45:41 +0900 (JST)
To: Tim Chown <tjc@ecs.soton.ac.uk>
cc: Steve Deering <deering@cisco.com>,
        Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
        Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
In-reply-to: tjc's message of Fri, 07 Jul 2000 17:25:08 +0100.
      <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
From: itojun@iijlab.net
Date: Sat, 08 Jul 2000 01:45:41 +0900
Message-ID: <14010.962988341@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> /48 was intended to be the *minimum* allocation to a subscriber's site, not
>> the *maximum*.  Those exceptional subscribers for whom a /48 is too small
>> are free to request larger blocks from their ISPs.
>But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
>to offer a /40 to each University it would at present be looking at being
>able to connect just 32 Universities.   By 2001 there will be over 800
>University and further education colleges online under the UK JANET network.

	While I understand the problem you have, I would like t know why
	you'd like to offer /40 to every universities.  Are there any reason
	not to do /48 for universities, or couple of /48s? 

	We (WIDE) offer /48 for leaf sites (an organization which has no
	plan to have sub-organization, i.e. universities and companies,
	not an ISP), and /40 to non-leaf downstream sites (an organization
	which has plan t have sub-organization, i.e. an ISP).
	Once a leaf site use up /48, they'd be able to get another /48 from us.
	Until now we saw no problem with it.
	"/48 allocation to everyone" is just fine for me (or us).
	We cannot predict the future growth of leaf site.
	We don't want to, we don't need to.  SOHO can evolve into
	multinational company.

	We have more important problem to tackle.  The problem lies elsewhere,
	I believe.  Once our network grows into /29, and to /16, we'd need
	to carry 2^(48-29) or 2^(48-16) routes in a TLA.  It's like having
	the whole IPv4 space in one ISP.  We need to have a very careful plan
	on inner-TLA topology, so that we can aggregate internal routes nicely.
	We may need more experiences/standards in hierarchical interior routing
	operation.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:54:02 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03557
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:54:01 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA22779;
	Fri, 7 Jul 2000 10:52:32 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA01834;
	Fri, 7 Jul 2000 09:49:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67Gmia27337
	for ngtrans-dist; Fri, 7 Jul 2000 09:48:44 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67GmW627330;
	Fri, 7 Jul 2000 09:48:32 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA27157;
	Fri, 7 Jul 2000 09:48:31 -0700 (PDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id KAA19516;
	Fri, 7 Jul 2000 10:48:27 -0600 (MDT)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id QA29554;
	Sat, 8 Jul 2000 02:48:11 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp,
        sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: Your message of "Fri, 07 Jul 2000 17:25:08 +0100."
             <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk> 
Date: Sat, 08 Jul 2000 02:48:10 +1000
Message-Id: <17347.962988490@mundamutti.cs.mu.OZ.AU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Robert Elz <kre@munnari.OZ.AU>

    Date:        Fri, 7 Jul 2000 17:25:08 +0100 (BST)
    From:        Tim Chown <tjc@ecs.soton.ac.uk>
    Message-ID:  <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>

  | But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
  | to offer a /40 to each University

Why would i want to do that?   /48 to everyone is what should be offered.
If a site is truly *huge* (that is, is so big an IPv4 class A net isn't
enough for it) then perhaps it gets a /47 - or even a /46.   Why would
anyone routinely be allocating /40?

  | Of course they're not all big, varying from maybe 4,000 to 40,000 people,
  | so most could live under a /48.

All of those could live in a /48.

  | I would be interested to know what the addressing requirements of a mobile 
  | provider would be, in terms of scale and subnetting.

If one assumes (which would probably be wrong) that all the mobile
nodes are sharing some kind of switched link level, then one /64
would be enough for all of that ... Of course, that would make for
pretty huge tables, so some degree of subnetting might be appropriate.
But a /48 is probably going to be enough, even for that size site.
And of course, some of the mobiles might be gateways to other local
nets in which case those nets would be getting their own /48 (or
if they really don't need it, perhaps just /64).

kre


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 12:58:50 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03855
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 12:58:49 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA27225;
	Fri, 7 Jul 2000 10:58:16 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA21013;
	Fri, 7 Jul 2000 09:57:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67GuBR27475
	for ngtrans-dist; Fri, 7 Jul 2000 09:56:11 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Gu2627468;
	Fri, 7 Jul 2000 09:56:03 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA28981;
	Fri, 7 Jul 2000 09:56:01 -0700 (PDT)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00072;
	Fri, 7 Jul 2000 09:56:00 -0700 (PDT)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id BAA14149;
	Sat, 8 Jul 2000 01:55:58 +0900 (JST)
To: Kazu Yamamoto (=?ISO-2022-JP?B?GyRCOzNLXE9CSScbKEI=?=)
  <kazu@iijlab.net>
cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp,
        sig-ipv6@apnic.net
In-reply-to: kazu's message of Thu, 06 Jul 2000 17:27:14 JST.
      <20000706.172714.91311805.kazu@Mew.org>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
From: itojun@iijlab.net
Date: Sat, 08 Jul 2000 01:55:58 +0900
Message-ID: <14147.962988958@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

	sorry for too much cross-posting.  I think the following part in the
	APNIC text is slightly unclear.

>These are:
>1) /64 for single devices (such as mobile phones), /48 for all other sites
>2) /64 for single devices, /48 for large end sites which need more 
>   than 256 subnets, and /56 for other sites (eg small, domestic/home sites)

	Does /64 mean "address behind the device", or "address for the ppp
	link"?

	(1)				(2)

	ISP router			ISP router
	  |link local only		  |link local and global
	  |				  |	<--- /64 is here
	  |link local only		  |link local and global
	customer router			customer device
	  |link local and global
	==+=== <--- /64 is here

	Note that it is legal and possible to run routing protocol on
	diagram (1).  All of IPv6 routing protocol is written this way
	(and static routing is possible too).

itojun


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 13:11:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04817
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 13:11:01 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA05938;
	Fri, 7 Jul 2000 11:09:21 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA21541;
	Fri, 7 Jul 2000 10:06:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67H5Ct27621
	for ngtrans-dist; Fri, 7 Jul 2000 10:05:12 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67H3R627573;
	Fri, 7 Jul 2000 10:03:27 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA01076;
	Fri, 7 Jul 2000 10:03:26 -0700 (PDT)
From: Ronald.vanderPol@surfnet.nl
Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA01328;
	Fri, 7 Jul 2000 11:03:24 -0600 (MDT)
Received: from spock.ncc-1701.surfnet.nl ([192.87.111.34])
	by survis.surfnet.nl with ESMTP (exPP)
	id 13AbX7-0005Fo-00; Fri, 7 Jul 2000 19:03:22 +0200
Date: Fri, 7 Jul 2000 19:04:47 +0200 (CEST)
X-Sender: rvdp@spock.ncc-1701.surfnet.nl
To: Robert Elz <kre@munnari.OZ.AU>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: <17347.962988490@mundamutti.cs.mu.OZ.AU>
Message-ID: <Pine.BSF.4.21.0007071856100.241-100000@spock.ncc-1701.surfnet.nl>
Organisation: SURFnet bv
Address: "Radboudburcht, P.O. Box 19035, 3501 DA Utrecht, NL"
Phone: +31 302 305 305
Telefax: +31 302 305 329
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ronald.vanderPol@surfnet.nl

On Sat, 8 Jul 2000, Robert Elz wrote:

>| But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
>| to offer a /40 to each University
> 
> Why would i want to do that?   /48 to everyone is what should be offered.

A university might have a dialup service for its employees and students.
I think they should get a /48 at home. So the university needs many /48s.
With a /40 they can have no more than 256 students/employees :-)

	rvdp



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:03:54 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07830
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:03:53 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA16845;
	Fri, 7 Jul 2000 12:02:55 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA07340;
	Fri, 7 Jul 2000 11:02:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67I1Db28057
	for ngtrans-dist; Fri, 7 Jul 2000 11:01:13 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67I13628050;
	Fri, 7 Jul 2000 11:01:03 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA15589;
	Fri, 7 Jul 2000 11:01:01 -0700 (PDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id LAA11611;
	Fri, 7 Jul 2000 11:00:56 -0700 (PDT)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id SA30400;
	Sat, 8 Jul 2000 04:00:43 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: Your message of "Fri, 07 Jul 2000 18:57:50 +0200."
             <20000707185750.C25625@theory.cs.uni-bonn.de> 
Date: Sat, 08 Jul 2000 04:00:43 +1000
Message-Id: <19698.962992843@mundamutti.cs.mu.OZ.AU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Robert Elz <kre@munnari.OZ.AU>

    Date:        Fri, 7 Jul 2000 18:57:50 +0200
    From:        Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
    Message-ID:  <20000707185750.C25625@theory.cs.uni-bonn.de>

This is a non-issue, because we're not doing this, but ...

  | assuming everybody could afford (at least) on phone, IP(v6) over the NMBA
  | network called "the world-wide phone system" already would need more then
  | 2^32 addresses, right?

That's going to depend upon whether there is internal structure in that
numbering, aside from what is in the phone numbers already.  2^32 is
probably too small for that particular subnet, but ...

  | /80 would be a problem even for all phones in Germany.

Germany really has more than 2^48 phones?  Or even more than a 2^48
phone number space?   That's a 15 (decimal) digit phone number space.

In any case, the 2^64 space allocated for subnets is easily going to
be big enough to map the POTS number space, should anyone actually
want to do that.

kre


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:09:09 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08098
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:09:08 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA21199;
	Fri, 7 Jul 2000 12:08:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA22872;
	Fri, 7 Jul 2000 11:06:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67I4kh28148
	for ngtrans-dist; Fri, 7 Jul 2000 11:04:46 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67I4W628139;
	Fri, 7 Jul 2000 11:04:33 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA07963;
	Fri, 7 Jul 2000 11:04:31 -0700 (PDT)
Received: from munnari.OZ.AU (munnari.OZ.AU [128.250.1.21])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id LAA13999;
	Fri, 7 Jul 2000 11:04:26 -0700 (PDT)
Received: from mundamutti.cs.mu.OZ.AU ([128.250.1.5])
	by munnari.OZ.AU with SMTP (5.83--+1.3.1+0.59) id SA30462;
	Sat, 8 Jul 2000 04:03:55 +1000 (from kre@munnari.OZ.AU)
From: Robert Elz <kre@munnari.OZ.AU>
To: Ronald.vanderPol@surfnet.nl
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: Your message of "Fri, 07 Jul 2000 19:04:47 +0200."
             <Pine.BSF.4.21.0007071856100.241-100000@spock.ncc-1701.surfnet.nl> 
Date: Sat, 08 Jul 2000 04:03:55 +1000
Message-Id: <19742.962993035@mundamutti.cs.mu.OZ.AU>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Robert Elz <kre@munnari.OZ.AU>

    Date:        Fri, 7 Jul 2000 19:04:47 +0200 (CEST)
    From:        Ronald.vanderPol@surfnet.nl
    Message-ID:  <Pine.BSF.4.21.0007071856100.241-100000@spock.ncc-1701.surfnet.nl>

  | A university might have a dialup service for its employees and students.

If they're really acting as an ISP, then they should be treated as
an ISP, and get an ISP sized number space.

On the other hand, many universities do this kind of thing now
(in fact, I am using such a link right now) and the numbering is
just taken from part of the university's number space .  That
should work just the same for IPv6.

kre


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:20:10 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08479
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:20:09 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA29517;
	Fri, 7 Jul 2000 12:18:48 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA25769;
	Fri, 7 Jul 2000 11:18:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IH7T28261
	for ngtrans-dist; Fri, 7 Jul 2000 11:17:07 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67IET628242;
	Fri, 7 Jul 2000 11:14:29 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA24778;
	Fri, 7 Jul 2000 11:14:28 -0700 (PDT)
Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA20345;
	Fri, 7 Jul 2000 11:14:27 -0700 (PDT)
Received: from [192.87.111.36] (helo=bones.ncc-1701.surfnet.nl)
	by survis.surfnet.nl with SMTP (exPP)
	id 13Acdt-0005PL-00; Fri, 7 Jul 2000 20:14:25 +0200
Date: Fri, 7 Jul 2000 20:09:41 +0200 (CDT)
From: Ronald van der Pol <Ronald.vanderPol@surfnet.nl>
To: Robert Elz <kre@munnari.OZ.AU>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, arano@byd.ocn.ad.jp, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: <19742.962993035@mundamutti.cs.mu.OZ.AU>
Message-ID: <Pine.WNT.3.96.1000707200604.-407059B-100000@bones.ncc-1701.surfnet.nl>
Organisation: SURFnet bv
Address: "Radboudburcht, P.O. Box 19035, 3501 DA Utrecht, NL"
Phone: +31 302 305 305
Telefax: +31 302 305 329
X-X-Sender: rvdp@zuurtje.surfnet.nl
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ronald van der Pol <Ronald.vanderPol@surfnet.nl>

On Sat, 8 Jul 2000, Robert Elz wrote:

> If they're really acting as an ISP, then they should be treated as
> an ISP, and get an ISP sized number space.

That is what Tim was saying. Universities might be assigned a /40.

> On the other hand, many universities do this kind of thing now
> (in fact, I am using such a link right now) and the numbering is
> just taken from part of the university's number space .  That
> should work just the same for IPv6.

Yes, it will work. But I think it's strange when you get a /48 from
a commercial ISP and a longer prefix from your university. Maybe you
will have both and have two (differently sized) prefixes. A nightmare!

	rvdp



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:24:54 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08662
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:24:53 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA03869;
	Fri, 7 Jul 2000 12:23:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA12969;
	Fri, 7 Jul 2000 11:23:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IMA428346
	for ngtrans-dist; Fri, 7 Jul 2000 11:22:10 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67ILw628335;
	Fri, 7 Jul 2000 11:21:59 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA26774;
	Fri, 7 Jul 2000 11:21:58 -0700 (PDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA25095;
	Fri, 7 Jul 2000 11:21:55 -0700 (PDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id NAA08379;
	Fri, 7 Jul 2000 13:21:54 -0500 (CDT)
Message-Id: <200007071821.NAA08379@gungnir.fnal.gov>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-reply-to: Your message of Sat, 08 Jul 2000 02:15:57 +1000.
             <16970.962986557@mundamutti.cs.mu.OZ.AU> 
Date: Fri, 07 Jul 2000 13:21:54 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Matt Crawford" <crawdad@fnal.gov>

The question to answer is, for a liberal estimate of the number of
"sites" required 50 years from now, how efficiently (how non-wastefully)
do assignments need to be made to fit within available space?

An extremely liberal estimate of the number of sites required would be
one per person.  Taking the upper range of the year 2050 population
projection from http://www.popin.org/pop1998/ ...

    World population currently stands at 5.9 billion persons and
    is growing at 1.33 per cent per year, or an annual net
    addition of 78 million people. World population in the mid
    21st century is expected to be in the range of 7.3 to 10.7
    billion. The medium-fertility projection, which is usually
    considered as "most likely", indicates that world population
    will reach 8.9 billion in 2050.

tells us to reckon on 11 billion sites.  The available space for
assignment of /48 site identifiers is 45 bits worth if we confine
ourselves to one three-bit Format Prefix.  (Six more such are potentially
available.)  Using the H-ratio of RFC 1715 to compute the required
efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22.  This is less
than the efficiencies of telephone numbers and DECnetIV or IPv4 addresses
shown in RFC 1715*.  Coupled with the generous assumption of a site per
person, the reasonable expectation of easier renumbering for IPv6 than
IPv4 or the telephone, and the availability of 6x more unicast address
space, I can't see any way to justify a claim that a /48 per site can't
be supported.
				Matt Crawford

(* Actually, RFC 1715 understates the efficiency of phone number
allocation by using the number of nodes /before/ an increase in
numbering space was made but counting the bits /after/ the increase.)


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:25:10 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08681
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:25:09 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA04415;
	Fri, 7 Jul 2000 12:24:36 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA12631;
	Fri, 7 Jul 2000 11:21:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IKm928324
	for ngtrans-dist; Fri, 7 Jul 2000 11:20:48 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67IKf628313
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 11:20:41 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA06006
	for ngtrans@sunroof.eng.sun.com; Fri, 7 Jul 2000 11:19:15 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67H4k627598;
	Fri, 7 Jul 2000 10:04:46 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA23159;
	Fri, 7 Jul 2000 10:04:45 -0700 (PDT)
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA05632;
	Fri, 7 Jul 2000 10:04:44 -0700 (PDT)
Received: (from ignatios@localhost)
	by theory.cs.uni-bonn.de (8.9.1a/8.9.1) id TAA20679;
	Fri, 7 Jul 2000 19:04:34 +0200 (MET DST)
Date: Fri, 7 Jul 2000 19:04:34 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Steve Deering <deering@cisco.com>,
        Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
        Brian E Carpenter <brian@hursley.ibm.com>, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Message-ID: <20000707190434.D25625@theory.cs.uni-bonn.de>
References: <v04220802b58b9b380355@[10.19.130.188]> <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.SOL.4.20.0007071703400.16436-100000@penelope.ecs.soton.ac.uk>; from tjc@ecs.soton.ac.uk on Fri, Jul 07, 2000 at 05:25:08PM +0100
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>

On Fri, Jul 07, 2000 at 05:25:08PM +0100, Tim Chown wrote:
> On Fri, 7 Jul 2000, Steve Deering wrote:
> 
> > /48 was intended to be the *minimum* allocation to a subscriber's site, not
> > the *maximum*.  Those exceptional subscribers for whom a /48 is too small
> > are free to request larger blocks from their ISPs.
> 
> But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
> to offer a /40 to each University it would at present be looking at being
> able to connect just 32 Universities.

Hm... but... 

a /48 (2^16 networks) is already more than any University (I know of) has
today in v4-land. This will allow for quite some growth.

So there is no need to given them a /40 _now_. Sparsely - allocated /48 are 
fine, can be extended if needed, unless filled up, in which case renumbering
is easy. At least much easier than in v4-world.

Regards,
	-is



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:25:15 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08692
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:25:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA04132;
	Fri, 7 Jul 2000 12:24:17 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA12432;
	Fri, 7 Jul 2000 11:19:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IIt428286
	for ngtrans-dist; Fri, 7 Jul 2000 11:18:55 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67IIo628279
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 11:18:50 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA05976
	for ngtrans@sunroof.eng.sun.com; Fri, 7 Jul 2000 11:17:24 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67Gvs627501;
	Fri, 7 Jul 2000 09:57:54 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA29549;
	Fri, 7 Jul 2000 09:57:53 -0700 (PDT)
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA01241;
	Fri, 7 Jul 2000 09:57:52 -0700 (PDT)
Received: (from ignatios@localhost)
	by theory.cs.uni-bonn.de (8.9.1a/8.9.1) id SAA18164;
	Fri, 7 Jul 2000 18:57:50 +0200 (MET DST)
Date: Fri, 7 Jul 2000 18:57:50 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Message-ID: <20000707185750.C25625@theory.cs.uni-bonn.de>
References: <200007071556.JAA01092@hunkular.glarp.com> <16970.962986557@mundamutti.cs.mu.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <16970.962986557@mundamutti.cs.mu.OZ.AU>; from kre@munnari.OZ.AU on Sat, Jul 08, 2000 at 02:15:57AM +1000
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>

On Sat, Jul 08, 2000 at 02:15:57AM +1000, Robert Elz wrote:

> Except that IEEE has created 64 bit MAC identifiers for use by its
> new protocols, and /80 would kill easy autoconf.

Of course.

> For sure, /80
> (even /96) leaves way too many addresses for any conceivable subnet
> to ever use them all -

For traditional subnets, you're right, but...

assuming everybody could afford (at least) on phone, IP(v6) over the NMBA
network called "the world-wide phone system" already would need more then
2^32 addresses, right? /80 would be a problem even for all phones in Germany.

Regards,
	Ignatios



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:29:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08959
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:29:28 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA06920;
	Fri, 7 Jul 2000 12:27:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA13589;
	Fri, 7 Jul 2000 11:24:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67INT528378
	for ngtrans-dist; Fri, 7 Jul 2000 11:23:29 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67INM628371
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jul 2000 11:23:23 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA06035
	for ngtrans@sunroof.eng.sun.com; Fri, 7 Jul 2000 11:21:56 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67HLS627750;
	Fri, 7 Jul 2000 10:21:28 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA25895;
	Fri, 7 Jul 2000 10:21:27 -0700 (PDT)
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA16913;
	Fri, 7 Jul 2000 10:21:25 -0700 (PDT)
Received: (from ignatios@localhost)
	by theory.cs.uni-bonn.de (8.9.1a/8.9.1) id TAA25495;
	Fri, 7 Jul 2000 19:17:48 +0200 (MET DST)
Date: Fri, 7 Jul 2000 19:17:48 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: Ronald.vanderPol@surfnet.nl
Cc: Robert Elz <kre@munnari.OZ.AU>, Tim Chown <tjc@ecs.soton.ac.uk>,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Message-ID: <20000707191748.A24200@theory.cs.uni-bonn.de>
References: <17347.962988490@mundamutti.cs.mu.OZ.AU> <Pine.BSF.4.21.0007071856100.241-100000@spock.ncc-1701.surfnet.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <Pine.BSF.4.21.0007071856100.241-100000@spock.ncc-1701.surfnet.nl>; from Ronald.vanderPol@surfnet.nl on Fri, Jul 07, 2000 at 07:04:47PM +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>

On Fri, Jul 07, 2000 at 07:04:47PM +0200, Ronald.vanderPol@surfnet.nl wrote:
> On Sat, 8 Jul 2000, Robert Elz wrote:
> 
> >| But that's where the /35 "pressure" applies because if (say) UKERNA wanted 
> >| to offer a /40 to each University
> > 
> > Why would i want to do that?   /48 to everyone is what should be offered.
> 
> A university might have a dialup service for its employees and students.
> I think they should get a /48 at home. So the university needs many /48s.
> With a /40 they can have no more than 256 students/employees :-)

Not necessarily.
They would be counted as part of the site, and get less than a /48.

However, assuming all of them are connected at the same time (!!!),
/48 would not be enough, and they'd need something bigger, maybe a /44.

Regards,
	-is

-- 
 * Progress (n.): The process through which Usenet has evolved from
   smart people in front of dumb terminals to dumb people in front of
   smart terminals.  -- obs@burnout.demon.co.uk (obscurity)



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:39:44 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09360
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:39:43 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA16184;
	Fri, 7 Jul 2000 12:39:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA00909;
	Fri, 7 Jul 2000 11:36:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IYqb28518
	for ngtrans-dist; Fri, 7 Jul 2000 11:34:52 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67IWx628500;
	Fri, 7 Jul 2000 11:32:59 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA00034;
	Fri, 7 Jul 2000 11:32:59 -0700 (PDT)
From: Ronald.vanderPol@surfnet.nl
Received: from survis.surfnet.nl (survis.surfnet.nl [192.87.108.3])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA11160;
	Fri, 7 Jul 2000 12:32:54 -0600 (MDT)
Received: from spock.ncc-1701.surfnet.nl ([192.87.111.34])
	by survis.surfnet.nl with ESMTP (exPP)
	id 13Acvk-0005TM-00; Fri, 7 Jul 2000 20:32:52 +0200
Date: Fri, 7 Jul 2000 20:34:22 +0200 (CEST)
X-Sender: rvdp@spock.ncc-1701.surfnet.nl
To: Matt Crawford <crawdad@fnal.gov>
cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-Reply-To: <200007071821.NAA08379@gungnir.fnal.gov>
Message-ID: <Pine.BSF.4.21.0007072031440.241-100000@spock.ncc-1701.surfnet.nl>
Organisation: SURFnet bv
Address: "Radboudburcht, P.O. Box 19035, 3501 DA Utrecht, NL"
Phone: +31 302 305 305
Telefax: +31 302 305 329
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ronald.vanderPol@surfnet.nl

On Fri, 7 Jul 2000, Matt Crawford wrote:

> efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22. 

What does this mean? Do sites (/48) on average have 0.22*2^16=
14417 networks (/64s)?

	rvdp



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 14:59:47 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09932
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 14:59:46 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA00923;
	Fri, 7 Jul 2000 12:59:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA06451;
	Fri, 7 Jul 2000 11:58:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67IvP228579
	for ngtrans-dist; Fri, 7 Jul 2000 11:57:25 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67IvG628572;
	Fri, 7 Jul 2000 11:57:16 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA21703;
	Fri, 7 Jul 2000 11:57:14 -0700 (PDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA29486;
	Fri, 7 Jul 2000 12:57:13 -0600 (MDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id NAA08653;
	Fri, 7 Jul 2000 13:57:11 -0500 (CDT)
Message-Id: <200007071857.NAA08653@gungnir.fnal.gov>
To: Ronald.vanderPol@surfnet.nl
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        mir@ripe.net, joao@ripe.net
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-reply-to: Your message of Fri, 07 Jul 2000 20:34:22 +0200.
      <Pine.BSF.4.21.0007072031440.241-100000@spock.ncc-1701.surfnet.nl> 
Date: Fri, 07 Jul 2000 13:57:11 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Matt Crawford" <crawdad@fnal.gov>

> > efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22. 
> 
> What does this mean? Do sites (/48) on average have 0.22*2^16=
> 14417 networks (/64s)?

This means that if they want to have more than 10^(0.22 * 16) = 3311
subnets, they must assign them more efficiently (more densely) than
site identifiers are assigned.  This should not be difficult to do,
since they would have no need to do variable-length subnet masks like
we're doing at this site in IPv4.  (Our subnets range in size from
/28 to /21.)
				Matt Crawford


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul  7 15:07:51 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10218
	for <ngtrans-archive@odin.ietf.org>; Fri, 7 Jul 2000 15:07:50 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA06808;
	Fri, 7 Jul 2000 13:07:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA24019;
	Fri, 7 Jul 2000 12:06:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e67J5aS28661
	for ngtrans-dist; Fri, 7 Jul 2000 12:05:36 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e67J5S628654;
	Fri, 7 Jul 2000 12:05:29 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA23772;
	Fri, 7 Jul 2000 12:05:27 -0700 (PDT)
Received: from popcorn.cisco.com (popcorn.cisco.com [171.69.18.32])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA22225;
	Fri, 7 Jul 2000 12:05:27 -0700 (PDT)
Received: from [171.70.84.50] (deering-office-mac.cisco.com [171.70.84.50])
	by popcorn.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id MAA24784;
	Fri, 7 Jul 2000 12:04:13 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220802b58bd87223e7@[171.70.84.50]>
In-Reply-To: 
 <Pine.BSF.4.21.0007072031440.241-100000@spock.ncc-1701.surfnet.nl>
References: 
 <Pine.BSF.4.21.0007072031440.241-100000@spock.ncc-1701.surfnet.nl>
Date: Fri, 7 Jul 2000 12:04:52 -0700
To: Ronald.vanderPol@surfnet.nl
From: Steve Deering <deering@cisco.com>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Cc: Matt Crawford <crawdad@fnal.gov>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net, mir@ripe.net,
        joao@ripe.net
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 8:34 PM +0200 7/7/00, Ronald.vanderPol@surfnet.nl wrote:
> > efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22. 
>
>What does this mean? Do sites (/48) on average have 0.22*2^16=
>14417 networks (/64s)?

No.  You really need to read RFC 1715 to understand it.  The H ratio is a
measure of the assignment efficiency of an address space, which takes into
account the inevitable wastage that you get when the addresses must have
hierarchical structure.

In this particular case, the H Ratio that Matt computed applies to the
efficiency of allocation of the high-order /48 (a 45 bit space, when you
exclude the format prefix).  It says nothing about the usage of the low-
order 80 bits (which is irrelevant, for the point that Matt is making).

Steve



From owner-ngtrans@sunroof.eng.sun.com  Sun Jul  9 13:32:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09117
	for <ngtrans-archive@odin.ietf.org>; Sun, 9 Jul 2000 13:32:01 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14303;
	Sun, 9 Jul 2000 11:31:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA07060;
	Sun, 9 Jul 2000 10:29:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e69HSlG29926
	for ngtrans-dist; Sun, 9 Jul 2000 10:28:47 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e69HRF629903;
	Sun, 9 Jul 2000 10:27:15 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA10140;
	Sun, 9 Jul 2000 10:27:14 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA13290;
	Sun, 9 Jul 2000 11:27:13 -0600 (MDT)
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 SAA14380; Sun, 9 Jul 2000 18:26:11 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id SAA16470; Sun, 9 Jul 2000 18:26:16 +0100 (BST)
Message-ID: <3968909A.E0C7E977@hursley.ibm.com>
Date: Sun, 09 Jul 2000 09:47:54 -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: matthew.ford@bt.com
CC: Francis.Dupont@enst-bretagne.fr, stephenb@uk.uu.net,
        ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        arano@byd.ocn.ad.jp, sig-ipv6@apnic.net, mir@ripe.net, joao@ripe.net,
        jonathan.2.stevens@bt.com, peter.hovell@bt.com
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <F66469FCE9C5D311B8FF0000F8FE9E0701178FA9@mbtlipnt03.btlabs.bt.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Mat,

Exactly. A movable boundary (and its consequence, asking registries to make
judgement calls) is a proven enemy of route aggregation, renumbering,
and multi-homing. The lack of IPv4 addresses forced us into this situation,
as per RFC 2050. As Matt Crawford's calculation proves, there is nothing
forcing us into such a situation with IPv6. It's simple arithmetic.
Just allocate /48s. 

   Brian

matthew.ford@bt.com wrote:
> 
> If /56 can be agreed upon as a default then that is not too bad IMO.
> However, the RIRs seem to be veering towards allowing LIRs to allocate
> whatever they choose between /48 and /64 - a movable boundary which will
> scupper the technical objectives of multihoming and simplified
> site-renumbering. I believe the idea of a movable boundary should be
> strongly opposed for this reason.
> 
> Regards,
> 
> Mat Ford.
> 
> -----Original Message-----
> From: Francis Dupont [mailto:Francis.Dupont@enst-bretagne.fr]
> Sent: 07 July 2000 08:22
> To: Brian E Carpenter
> Cc: stephenb@uk.uu.net; ipng@sunroof.eng.sun.com;
> ngtrans@sunroof.eng.sun.com; arano@byd.ocn.ad.jp; sig-ipv6@apnic.net;
> mir@ripe.net; joao@ripe.net
> Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document
> Revision
> 
>  In your previous mail you wrote:
> 
>    Can you explain why people think there is any need to allocate anything
>    longer than a /48 in the first place?
> 
> => many ISPs want to allocate /64 (or worse) to their customers... and
> shout a /48 per customer is far too large. I believe this is a consequence
> of the slow^N start, ie. the /35 rule (RIRs trim address space of ISPs,
> ISPs take back the burden to their customers).
>  The idea is to introduce a small site (/56) for "poor & little" customers
> and to make it the *default* allocation. IMHO this is an acceptable target.
> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 06:36:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02443
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 06:36:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA04054;
	Mon, 10 Jul 2000 04:35:36 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA26160;
	Mon, 10 Jul 2000 03:35:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AAXoA00409
	for ngtrans-dist; Mon, 10 Jul 2000 03:33:50 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AAXf600402
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Jul 2000 03:33:41 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA06328
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Jul 2000 03:33:40 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA03285
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Jul 2000 04:33:39 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02286;
	Mon, 10 Jul 2000 06:33:37 -0400 (EDT)
Message-Id: <200007101033.GAA02286@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-broker-03.txt
Date: Mon, 10 Jul 2000 06:33:37 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: IPv6 Tunnel Broker
	Author(s)	: A. Durand, P. Fasano, I. Guardini, D. Lento
	Filename	: draft-ietf-ngtrans-broker-03.txt
	Pages		: 10
	Date		: 07-Jul-00
	
The IPv6 global Internet as of today is mostly built using tunnels over
the existing IPv4 infrastructure. Those tunnels are difficult to
configure and maintain in a large scale environment. The 6bone has
proven that large sites and ISPs can do it, but this process is too
complex for the isolated end user who already has an IPv4 connection and
would like to enter the IPv6 world. The motivation for the development
of the tunnel broker model is to help early IPv6 adopters to hook up
to an existing IPv6 network (e.g. the 6bone) and to get stable,
permanent IPv6 addresses and DNS names. The concept of the tunnel broker
was first presented at Orlando's IETF in December 1998. Two
implementations were demonstrated during the Grenoble IPng & NGtrans
interim meeting.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-broker-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-broker-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-broker-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000707143858.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-broker-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-broker-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000707143858.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 06:52:38 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02964
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 06:52:38 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA10103;
	Mon, 10 Jul 2000 04:52:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA27073;
	Mon, 10 Jul 2000 03:51:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AAoNC00478
	for ngtrans-dist; Mon, 10 Jul 2000 03:50:23 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AAmL600463;
	Mon, 10 Jul 2000 03:48:21 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA10785;
	Mon, 10 Jul 2000 03:48:19 -0700 (PDT)
From: Heikki.Waris@nokia.com
Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA13720;
	Mon, 10 Jul 2000 03:48:18 -0700 (PDT)
Received: from esvir02nok.ntc.nokia.com (esvir02nok.ntc.nokia.com [131.228.10.151])
	by mgw-x1.nokia.com (8.9.3/8.9.3/o) with ESMTP id NAA16974;
	Mon, 10 Jul 2000 13:48:15 +0300 (EETDST)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir02nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <T83e40a97754d51cd5ae5@esvir02nok.ntc.nokia.com>;
 Mon, 10 Jul 2000 13:48:14 +0300
Received: by esebh03nok with Internet Mail Service (5.5.2650.10)
	id <N63SBY4W>; Mon, 10 Jul 2000 13:48:12 +0300
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE1021673D3@eseis04nok>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net
Subject: RE: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
Date: Mon, 10 Jul 2000 13:43:25 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e6AAmM600464
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Heikki.Waris@nokia.com
Content-Transfer-Encoding: 8bit

I'd like to contribute my view on this prefix length issue.

If we start by trying to estimate the total amount of routers required at
the edge of the network, this whole conversation will gain some perspective.
Let's make a quick calculation, assuming that there are 500 million
well-to-do people in mainly industrialized countries with enough financial
resources who healthily envy their neighbors with more gadgets and gizmos
(and therefore need to have those themselves):

offices/corporate sites        50M
(small separate units, subnet per avg. 5-10 employees)
personal 2G/3G terminals        5M
(1 base station serves 1000 people, 10 overlapping operators)
WLAN access points etc.        50M
(covering all rural areas, avg. 10 users within the radius)
Bluetooth etc. local networks 500M
(ubiqutous, offer routing mainly in business environment)
personal mobile routers       500M
(for connecting wearable equipment, personal subnet)
houses/apartments             500M
vehicles                      500M
                             =====
                         ca. 2100M

Make this available to total active population worldwide, multiply 10x.
Then we add another decade due to the human tendency of hoarding resources
and not freeing address subnets that are no longer used.
Then assume that the total efficiency in assigning the subnet space will be
close to 10% due to (30% efficiency at two levels, or 47% at three levels of
hierarchical providers)

So we need 2*10^12 subnets just for currently foreseeable uses. Or in terms
of address space, consumption of 41 bits. If we leave out the 3 bit format
prefix, this leaves us with 20 bits to waste (if subnets are /64). If the
default subnet is /48, we only have 4 bits to waste. And that's not much.

Organizations can be worried about not getting enough continuous address
space that they can autonomously manage. This is not an excuse for sloppy
address allocation. Why not instead suggest providers to initially assign
only every 8th or 16th SLA ID for growing organizations? This would leave
the provider address space in semi-allocated state (could hamper reaching
the 90% mark) but leave some back doors for those that require it. Solving
the preferences or problems of individual organizations with case-by-case
negotiations instead of generalized rules that may have wider consequences
seems to me like a reasonable approach.

Heikki Waris

> -----Original Message-----
> From: EXT Matt Crawford [mailto:crawdad@fnal.gov]
> Sent: 7. hein�kuuta 2000 21:22
> To: ipng@sunroof.eng.sun.com; ngtrans@sunroof.eng.sun.com;
> sig-ipv6@apnic.net; mir@ripe.net; joao@ripe.net
> Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document
> Revision 
> 
> 
> The question to answer is, for a liberal estimate of the number of
> "sites" required 50 years from now, how efficiently (how 
> non-wastefully)
> do assignments need to be made to fit within available space?
> 
> An extremely liberal estimate of the number of sites required would be
> one per person.  Taking the upper range of the year 2050 population
> projection from http://www.popin.org/pop1998/ ...
> 
>     World population currently stands at 5.9 billion persons and
>     is growing at 1.33 per cent per year, or an annual net
>     addition of 78 million people. World population in the mid
>     21st century is expected to be in the range of 7.3 to 10.7
>     billion. The medium-fertility projection, which is usually
>     considered as "most likely", indicates that world population
>     will reach 8.9 billion in 2050.
> 
> tells us to reckon on 11 billion sites.  The available space for
> assignment of /48 site identifiers is 45 bits worth if we confine
> ourselves to one three-bit Format Prefix.  (Six more such are 
> potentially
> available.)  Using the H-ratio of RFC 1715 to compute the required
> efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22.  
> This is less
> than the efficiencies of telephone numbers and DECnetIV or 
> IPv4 addresses
> shown in RFC 1715*.  Coupled with the generous assumption of 
> a site per
> person, the reasonable expectation of easier renumbering for IPv6 than
> IPv4 or the telephone, and the availability of 6x more unicast address
> space, I can't see any way to justify a claim that a /48 per 
> site can't
> be supported.
> 				Matt Crawford
> 
> (* Actually, RFC 1715 understates the efficiency of phone number
> allocation by using the number of nodes /before/ an increase in
> numbering space was made but counting the bits /after/ the increase.)
> 


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 12:28:49 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15876
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 12:28:49 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA14520;
	Mon, 10 Jul 2000 10:27:35 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA16514;
	Mon, 10 Jul 2000 09:25:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AGONg00736
	for ngtrans-dist; Mon, 10 Jul 2000 09:24:23 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AGOD600729;
	Mon, 10 Jul 2000 09:24:14 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA03182;
	Mon, 10 Jul 2000 09:24:13 -0700 (PDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA11460;
	Mon, 10 Jul 2000 10:24:09 -0600 (MDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id LAA26207;
	Mon, 10 Jul 2000 11:24:03 -0500 (CDT)
Message-Id: <200007101624.LAA26207@gungnir.fnal.gov>
To: Heikki.Waris@nokia.com
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-reply-to: Your message of Mon, 10 Jul 2000 18:12:49 +0300.
             <01D91AFB08B6D211BFD00008C7EABAE1021673D4@eseis04nok> 
Date: Mon, 10 Jul 2000 11:24:03 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Matt Crawford" <crawdad@fnal.gov>

> Yes, sorry about that ambiguous use of terminology. But as you see from the
> calculation, most of the sites are consumed by individual entities (be it
> persons, vehicles, fixed locations or such) instead of traditional provider
> type large organizations ...

I don't know if I'd call a table of made-up numbers a "calculation",
but yes, you assumed that each "wealthy, envious" person would have a
lot of address space.  Then you multiplied by 10 to include everyone,
then you made an extremely dubious second multiplication by 10 to say
that everyone would "take" address assignments ten times over without
"giving back" their old assignments.  That idea just won't survive
contact with the IPv6 operational model of provider-based assignment
and renumbering at need.


> and therefore it is crucial that the assignment is
> done in blocks of /64 subnets.

Even with your dubious multiplicative factors, you still came up with
more than a factor of 10 to spare with assignment of /48s
everywhere.  (Even to personal Bluetooth networks that can hold less
than 10 devices!)  This falls considerably short of "crucial."

> And see that with some carefully chosen parameters we can

"Extravagantly", not "carefully".

> get close to exhausting the IPv6 address space (ok, within 7 bits
> to the limit)

In other words, a safety factor of more than 100.

> even with nowadays recognizable uses.

>  Besides, that 90% waste resulting from suboptimal provider
> allocation is just due to the fact that there may be small scale
> providers down in the hierarchy that will never grow so big that
> their initial address space runs out. Unless we also aggregate the
> providers with mega-mergers...

"Providers down in the hierarchy" are to get their address space from
higher up in the hierarchy.  I wonder if you're familiar with the
addressing and assignment architecture.

> The bottom line is that we shouldn't be absolutely confident that
> there's enough IPv6 addresses unless we take caution in the ways
> that we allocate them.

One form of caution is to make sure that a site can easily change its
prefix if it connects to a different point in the topology.  making
all the leaf-site blocks the same side IS a cautionary measure to
make this possible.
				Matt Crawford


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 13:26:22 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18478
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 13:26:21 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA06119;
	Mon, 10 Jul 2000 11:25:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA06138;
	Mon, 10 Jul 2000 10:04:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AH3lK00808
	for ngtrans-dist; Mon, 10 Jul 2000 10:03:47 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AH1N600789;
	Mon, 10 Jul 2000 10:01:23 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA16649;
	Mon, 10 Jul 2000 10:01:22 -0700 (PDT)
From: Heikki.Waris@nokia.com
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA23303;
	Mon, 10 Jul 2000 10:01:20 -0700 (PDT)
Received: from esvir04nok.ntc.nokia.com (esvir04nok.ntc.nokia.com [131.228.10.153])
	by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id SAA12959;
	Mon, 10 Jul 2000 18:12:51 +0300 (EETDST)
Received: from esebh03nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <T83e40a99754d52bf9e8c@esvir04nok.ntc.nokia.com>;
 Mon, 10 Jul 2000 18:12:51 +0300
Received: by esebh03nok with Internet Mail Service (5.5.2650.10)
	id <N63SCQQW>; Mon, 10 Jul 2000 18:12:51 +0300
Message-ID: <01D91AFB08B6D211BFD00008C7EABAE1021673D4@eseis04nok>
To: crawdad@fnal.gov
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net
Subject: RE: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
Date: Mon, 10 Jul 2000 18:12:49 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.10)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Heikki.Waris@nokia.com

> > So we need 2*10^12 subnets just for currently foreseeable 
> uses. Or in terms
> > of address space, consumption of 41 bits. If we leave out 
> the 3 bit format
> > prefix, this leaves us with 20 bits to waste (if subnets 
> are /64). If the
> > default subnet is /48, we only have 4 bits to waste. And 
> that's not much.
> 
> Point 1: Subnets (under format prefix 001 binary) *are* 64 bits, not
> 48.  That is not under any sort of argument by anyone, as far as I
> know.  The question the registries are trying to open is how many
> subnets get assigned in a block to a "site".

Yes, sorry about that ambiguous use of terminology. But as you see from the
calculation, most of the sites are consumed by individual entities (be it
persons, vehicles, fixed locations or such) instead of traditional provider
type large organizations and therefore it is crucial that the assignment is
done in blocks of /64 subnets.

Real organizations could be eligible for /56 or /48 prefixes but this should
not force the above mentioned entities to get the same prefix lengths by
default. So I still see some relevance in this point.

> Point 2: You've already built in a 90% "waste" into your numbers, so
> saying that you are left with "only n bits to waste" is pure 
> deception.

Buffers on top of buffers, but it is nevertheless useful to look at the
issue from a different angle. And see that with some carefully chosen
parameters we can get close to exhausting the IPv6 address space (ok, within
7 bits to the limit) even with nowadays recognizable uses.

Besides, that 90% waste resulting from suboptimal provider allocation is
just due to the fact that there may be small scale providers down in the
hierarchy that will never grow so big that their initial address space runs
out. Unless we also aggregate the providers with mega-mergers...

The bottom line is that we shouldn't be absolutely confident that there's
enough IPv6 addresses unless we take caution in the ways that we allocate
them. Keeping to the default /64 block at least initially is a good start.

Heikki Waris

> 
> 					Matt Crawford
> 


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 13:35:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19159
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 13:35:15 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14031;
	Mon, 10 Jul 2000 11:34:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA01732;
	Mon, 10 Jul 2000 09:16:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AGEgc00701
	for ngtrans-dist; Mon, 10 Jul 2000 09:14:42 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AGEO600685;
	Mon, 10 Jul 2000 09:14:24 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA01255;
	Mon, 10 Jul 2000 09:14:23 -0700 (PDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA02693;
	Mon, 10 Jul 2000 10:14:19 -0600 (MDT)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 612394CE50; Mon, 10 Jul 2000 12:14:13 -0400 (EDT)
Received: from research.att.com (pc-crk.research.att.com [135.207.17.83])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA15897;
	Mon, 10 Jul 2000 12:14:11 -0400 (EDT)
Message-ID: <3969F4FA.3CB7B8EF@research.att.com>
Date: Mon, 10 Jul 2000 12:08:26 -0400
From: "C. R. Kalmanek" <crk@research.att.com>
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net, ipng@sunroof.eng.sun.com
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "C. R. Kalmanek" <crk@research.att.com>
Content-Transfer-Encoding: 7bit

We need to do anything we can to facilitate aggregation, since 
(assuming there are enough addresses) this will be the thing that 
most hinders scalability.  I don't know where we stand today with 
respect to being able to handle all the routes in the default free 
zone, but we don't want to make things worse.  

Since there appear to be enough addresses, either the current 
option (/48 only) or an option that allows either /48 or /56 seem 
like the best choices.  Having an movable boundary anywhere between
/48 and /64 will definitely hurt aggregation and site mobility.

That said, with the current option, having 64K subnets for the 
network in my car seems like a bit of overkill.  This is a
case that seems to stretch the definition of a "site" in the
current addressing architecture...

chuck


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 14:33:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22074
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 14:33:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01910;
	Mon, 10 Jul 2000 12:31:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA28409;
	Mon, 10 Jul 2000 07:30:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AETYO00578
	for ngtrans-dist; Mon, 10 Jul 2000 07:29:35 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AETP600571;
	Mon, 10 Jul 2000 07:29:25 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA28217;
	Mon, 10 Jul 2000 07:29:24 -0700 (PDT)
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA00657;
	Mon, 10 Jul 2000 08:29:19 -0600 (MDT)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id JAA25294;
	Mon, 10 Jul 2000 09:28:38 -0500 (CDT)
Message-Id: <200007101428.JAA25294@gungnir.fnal.gov>
To: Heikki.Waris@nokia.com
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision 
In-reply-to: Your message of Mon, 10 Jul 2000 13:43:25 +0300.
             <01D91AFB08B6D211BFD00008C7EABAE1021673D3@eseis04nok> 
Date: Mon, 10 Jul 2000 09:28:38 -0500
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Matt Crawford" <crawdad@fnal.gov>

> So we need 2*10^12 subnets just for currently foreseeable uses. Or in terms
> of address space, consumption of 41 bits. If we leave out the 3 bit format
> prefix, this leaves us with 20 bits to waste (if subnets are /64). If the
> default subnet is /48, we only have 4 bits to waste. And that's not much.

Point 1: Subnets (under format prefix 001 binary) *are* 64 bits, not
48.  That is not under any sort of argument by anyone, as far as I
know.  The question the registries are trying to open is how many
subnets get assigned in a block to a "site".

Point 2: You've already built in a 90% "waste" into your numbers, so
saying that you are left with "only n bits to waste" is pure deception.

					Matt Crawford


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 16:27:33 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27247
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 16:27:32 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA17157;
	Mon, 10 Jul 2000 14:25:41 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA27390;
	Mon, 10 Jul 2000 12:42:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AJeZL01298
	for ngtrans-dist; Mon, 10 Jul 2000 12:40:35 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AJeT601291
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Jul 2000 12:40:29 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id MAA06952
	for ngtrans@sunroof.eng.sun.com; Mon, 10 Jul 2000 12:39:01 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AAak600424;
	Mon, 10 Jul 2000 03:36:47 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA26259;
	Mon, 10 Jul 2000 03:36:44 -0700 (PDT)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA10196;
	Mon, 10 Jul 2000 03:36:43 -0700 (PDT)
Received: from [193.0.1.195] (dhcp195.ripe.net [193.0.1.195])
	by birch.ripe.net (8.8.8/8.8.8) with ESMTP id MAA17909;
	Mon, 10 Jul 2000 12:36:28 +0200 (CEST)
Mime-Version: 1.0
X-Sender: joao@mailhost.ripe.net (Unverified)
Message-Id: <a04320404b58f5377cf45@[193.0.1.195]>
In-Reply-To: <3965F75D.E9B4FF6A@hursley.ibm.com>
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>
Date: Mon, 10 Jul 2000 12:36:04 +0200
To: Brian E Carpenter <brian@hursley.ibm.com>,
        Stephen Burley <stephenb@uk.uu.net>
From: Joao Luis Silva Damas <joao@ripe.net>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Cc: 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
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Joao Luis Silva Damas <joao@ripe.net>

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




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 16:52:13 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27961
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 16:52:13 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA02140;
	Mon, 10 Jul 2000 14:47:12 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA18034;
	Mon, 10 Jul 2000 13:19:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AKIRE01480
	for ngtrans-dist; Mon, 10 Jul 2000 13:18:27 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AKF6601465;
	Mon, 10 Jul 2000 13:15:06 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA26101;
	Mon, 10 Jul 2000 13:14:57 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA20747;
	Mon, 10 Jul 2000 13:14:54 -0700 (PDT)
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 VAA17862; Mon, 10 Jul 2000 21:14:28 +0100
Received: from hursley.ibm.com (lig32-225-3-132.us.lig-dial.ibm.com [32.225.3.132]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id VAA23258; Mon, 10 Jul 2000 21:14:40 +0100 (BST)
Message-ID: <396A2DA6.7F503EFE@hursley.ibm.com>
Date: Mon, 10 Jul 2000 15:10:14 -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: Heikki.Waris@nokia.com
CC: crawdad@fnal.gov, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        sig-ipv6@apnic.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <01D91AFB08B6D211BFD00008C7EABAE1021673D4@eseis04nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Heikki.Waris@nokia.com wrote:

> The bottom line is that we shouldn't be absolutely confident that there's
> enough IPv6 addresses unless we take caution in the ways that we allocate
> them. Keeping to the default /64 block at least initially is a good start.

Just to be 100% clear, I disagree. In the IPv6 world we can and must push
the balance further in favour of aggregation, away from conservation, and 
keeping to the default /48 block is a good start.

  Brian



From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 17:47:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29557
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 17:47:29 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA20408;
	Mon, 10 Jul 2000 15:46:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA25342;
	Mon, 10 Jul 2000 11:34:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AIXoU00999
	for ngtrans-dist; Mon, 10 Jul 2000 11:33:50 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AIVn600984;
	Mon, 10 Jul 2000 11:31:49 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA24526;
	Mon, 10 Jul 2000 11:31:47 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA00201;
	Mon, 10 Jul 2000 12:31:22 -0600 (MDT)
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 TAA44420; Mon, 10 Jul 2000 19:28:39 +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 TAA23122; Mon, 10 Jul 2000 19:28:50 +0100 (BST)
Message-ID: <396A0179.241F756D@hursley.ibm.com>
Date: Mon, 10 Jul 2000 12:01:45 -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: Heikki.Waris@nokia.com
CC: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
References: <01D91AFB08B6D211BFD00008C7EABAE1021673D3@eseis04nok>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e6AIVo600985
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 8bit

Heikki,

Matt's calculation is based on Huitema's H-ratio which is based on
actual experience, not theory.

   Brian

Heikki.Waris@nokia.com wrote:
> 
> I'd like to contribute my view on this prefix length issue.
> 
> If we start by trying to estimate the total amount of routers required at
> the edge of the network, this whole conversation will gain some perspective.
> Let's make a quick calculation, assuming that there are 500 million
> well-to-do people in mainly industrialized countries with enough financial
> resources who healthily envy their neighbors with more gadgets and gizmos
> (and therefore need to have those themselves):
> 
> offices/corporate sites        50M
> (small separate units, subnet per avg. 5-10 employees)
> personal 2G/3G terminals        5M
> (1 base station serves 1000 people, 10 overlapping operators)
> WLAN access points etc.        50M
> (covering all rural areas, avg. 10 users within the radius)
> Bluetooth etc. local networks 500M
> (ubiqutous, offer routing mainly in business environment)
> personal mobile routers       500M
> (for connecting wearable equipment, personal subnet)
> houses/apartments             500M
> vehicles                      500M
>                              =====
>                          ca. 2100M
> 
> Make this available to total active population worldwide, multiply 10x.
> Then we add another decade due to the human tendency of hoarding resources
> and not freeing address subnets that are no longer used.
> Then assume that the total efficiency in assigning the subnet space will be
> close to 10% due to (30% efficiency at two levels, or 47% at three levels of
> hierarchical providers)
> 
> So we need 2*10^12 subnets just for currently foreseeable uses. Or in terms
> of address space, consumption of 41 bits. If we leave out the 3 bit format
> prefix, this leaves us with 20 bits to waste (if subnets are /64). If the
> default subnet is /48, we only have 4 bits to waste. And that's not much.
> 
> Organizations can be worried about not getting enough continuous address
> space that they can autonomously manage. This is not an excuse for sloppy
> address allocation. Why not instead suggest providers to initially assign
> only every 8th or 16th SLA ID for growing organizations? This would leave
> the provider address space in semi-allocated state (could hamper reaching
> the 90% mark) but leave some back doors for those that require it. Solving
> the preferences or problems of individual organizations with case-by-case
> negotiations instead of generalized rules that may have wider consequences
> seems to me like a reasonable approach.
> 
> Heikki Waris
> 
> > -----Original Message-----
> > From: EXT Matt Crawford [mailto:crawdad@fnal.gov]
> > Sent: 7. hein�kuuta 2000 21:22
> > To: ipng@sunroof.eng.sun.com; ngtrans@sunroof.eng.sun.com;
> > sig-ipv6@apnic.net; mir@ripe.net; joao@ripe.net
> > Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document
> > Revision
> >
> >
> > The question to answer is, for a liberal estimate of the number of
> > "sites" required 50 years from now, how efficiently (how
> > non-wastefully)
> > do assignments need to be made to fit within available space?
> >
> > An extremely liberal estimate of the number of sites required would be
> > one per person.  Taking the upper range of the year 2050 population
> > projection from http://www.popin.org/pop1998/ ...
> >
> >     World population currently stands at 5.9 billion persons and
> >     is growing at 1.33 per cent per year, or an annual net
> >     addition of 78 million people. World population in the mid
> >     21st century is expected to be in the range of 7.3 to 10.7
> >     billion. The medium-fertility projection, which is usually
> >     considered as "most likely", indicates that world population
> >     will reach 8.9 billion in 2050.
> >
> > tells us to reckon on 11 billion sites.  The available space for
> > assignment of /48 site identifiers is 45 bits worth if we confine
> > ourselves to one three-bit Format Prefix.  (Six more such are
> > potentially
> > available.)  Using the H-ratio of RFC 1715 to compute the required
> > efficiency of assignment as log_10(1.07*10^10) / 45 = 0.22.
> > This is less
> > than the efficiencies of telephone numbers and DECnetIV or
> > IPv4 addresses
> > shown in RFC 1715*.  Coupled with the generous assumption of
> > a site per
> > person, the reasonable expectation of easier renumbering for IPv6 than
> > IPv4 or the telephone, and the availability of 6x more unicast address
> > space, I can't see any way to justify a claim that a /48 per
> > site can't
> > be supported.
> >                               Matt Crawford
> >
> > (* Actually, RFC 1715 understates the efficiency of phone number
> > allocation by using the number of nodes /before/ an increase in
> > numbering space was made but counting the bits /after/ the increase.)
> >




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 17:56:37 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29648
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 17:56:36 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA29334;
	Mon, 10 Jul 2000 15:56:06 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA13091;
	Mon, 10 Jul 2000 11:40:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AIdDT01055
	for ngtrans-dist; Mon, 10 Jul 2000 11:39:13 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AIb0601021;
	Mon, 10 Jul 2000 11:37:00 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA12082;
	Mon, 10 Jul 2000 11:36:58 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA06238;
	Mon, 10 Jul 2000 12:36:49 -0600 (MDT)
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
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
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




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 18:37:53 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00874
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 18:37:52 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA02871;
	Mon, 10 Jul 2000 16:37:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA21844;
	Mon, 10 Jul 2000 15:34:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AMXPu01820
	for ngtrans-dist; Mon, 10 Jul 2000 15:33:25 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AMVP601805;
	Mon, 10 Jul 2000 15:31:25 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA21337;
	Mon, 10 Jul 2000 15:31:24 -0700 (PDT)
From: dancer@zeor.simegen.com
Received: from keon.simegen.com (gw.simegen.com [203.2.135.4])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA14896;
	Mon, 10 Jul 2000 15:31:19 -0700 (PDT)
Received: from anaconda.simegen.com [203.28.9.32] 
	by keon.simegen.com with esmtp (Exim 3.12 #1 (Debian))
	id 13Bm4F-0003at-00; Tue, 11 Jul 2000 08:30:24 +1000
Received: from localhost ([127.0.0.1] helo=zeor.simegen.com)
	by anaconda.simegen.com with esmtp (Exim 3.12 #1 (Debian))
	id 13Bm4A-0000Ml-00; Tue, 11 Jul 2000 08:30:18 +1000
Message-ID: <396A4E79.AB70AB07@zeor.simegen.com>
Date: Tue, 11 Jul 2000 08:30:18 +1000
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.4.0-test1-ac21 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: Joao Luis Silva Damas <joao@ripe.net>
CC: Brian E Carpenter <brian@hursley.ibm.com>,
        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
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: dancer@zeor.simegen.com
Content-Transfer-Encoding: 7bit

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.

The only practical reason I can see for variable-length prefixes is for
the ISP to charge more money for allocation of any prefix shorter than a
/64. Guaranteed, the average ISP (no, I won't tar you all with the same
brush) if permitted to allocate a /64 won't allocate anything shorter
unless lubricated with many times the amount of cash.

Perhaps it sounds cynical, but that's based on my experiences with ISPs.
Under IPv4, I can see how a scarce resource falls under the supply/demand
paradigm. Let's not falsely inflate the value  of a /48 to the end-user
by making longer prefixes available. Those longer prefixes will simply
become the norm, which was not our intent, was it?

D




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 19:13:28 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01524
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 19:13:28 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA01519;
	Mon, 10 Jul 2000 17:12:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA26920;
	Mon, 10 Jul 2000 12:39:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6AJcrR01269
	for ngtrans-dist; Mon, 10 Jul 2000 12:38:53 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6AJcn601262
	for <ngtrans@sunroof.eng.sun.com>; Mon, 10 Jul 2000 12:38:49 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id MAA06923
	for ngtrans@sunroof.eng.sun.com; Mon, 10 Jul 2000 12:37:20 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6A82K600250;
	Mon, 10 Jul 2000 01:02:21 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA27673;
	Mon, 10 Jul 2000 01:02:17 -0700 (PDT)
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA13957;
	Mon, 10 Jul 2000 01:02:14 -0700 (PDT)
Received: (from ignatios@localhost)
	by theory.cs.uni-bonn.de (8.9.1a/8.9.1) id JAA16007;
	Mon, 10 Jul 2000 09:57:23 +0200 (MET DST)
Date: Mon, 10 Jul 2000 09:57:23 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: Robert Elz <kre@munnari.OZ.AU>
Cc: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, sig-ipv6@apnic.net, mir@ripe.net,
        joao@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
Message-ID: <20000710095723.A14952@theory.cs.uni-bonn.de>
References: <20000707185750.C25625@theory.cs.uni-bonn.de> <19698.962992843@mundamutti.cs.mu.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <19698.962992843@mundamutti.cs.mu.OZ.AU>; from kre@munnari.OZ.AU on Sat, Jul 08, 2000 at 04:00:43AM +1000
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>

On Sat, Jul 08, 2000 at 04:00:43AM +1000, Robert Elz wrote:
>     Date:        Fri, 7 Jul 2000 18:57:50 +0200
>     From:        Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
>     Message-ID:  <20000707185750.C25625@theory.cs.uni-bonn.de>
> 
> This is a non-issue, because we're not doing this, but ...
> 
>   | assuming everybody could afford (at least) on phone, IP(v6) over the NMBA
>   | network called "the world-wide phone system" already would need more then
>   | 2^32 addresses, right?
> 
> That's going to depend upon whether there is internal structure in that
> numbering, aside from what is in the phone numbers already.  2^32 is
> probably too small for that particular subnet, but ...
> 
>   | /80 would be a problem even for all phones in Germany.
> 
> Germany really has more than 2^48 phones?  Or even more than a 2^48
> phone number space?   That's a 15 (decimal) digit phone number space.

more than 2^16 phones. Oops. Of course, the phone would be a single device.
I shouldn't post on Fridays.

Regards,
	-is



From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 10 22:14:37 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04511
	for <ngtrans-archive@odin.ietf.org>; Mon, 10 Jul 2000 22:14:36 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA01959;
	Mon, 10 Jul 2000 20:13:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA22727;
	Mon, 10 Jul 2000 19:13:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6B2CBX02140
	for ngtrans-dist; Mon, 10 Jul 2000 19:12:11 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6B2Bt602133;
	Mon, 10 Jul 2000 19:11:55 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA22562;
	Mon, 10 Jul 2000 19:11:53 -0700 (PDT)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA28805;
	Mon, 10 Jul 2000 19:11:38 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id LAA10270;
	Tue, 11 Jul 2000 11:11:29 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id LAA11686; Tue, 11 Jul 2000 11:11:28 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id LAA17810; Tue, 11 Jul 2000 11:11:27 +0900 (JST)
Date: Tue, 11 Jul 2000 11:10:27 +0900 (JST)
Message-Id: <20000711.111027.41646408.kazu@Mew.org>
To: joao@ripe.net
Cc: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
In-Reply-To: <a04320404b58f5377cf45@[193.0.1.195]>
References: <3965A5F0.8505E7BA@uk.uu.net>
	<3965F75D.E9B4FF6A@hursley.ibm.com>
	<a04320404b58f5377cf45@[193.0.1.195]>
X-Mailer: Mew version 1.95b45 on Emacs 21.0 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
Content-Transfer-Encoding: 7bit

From: Joao Luis Silva Damas <joao@ripe.net>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document Revision

> 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.

Please make the way.

--Kazu


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 11 10:48:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02738
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Jul 2000 10:48:15 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04670;
	Tue, 11 Jul 2000 08:46:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA18506;
	Tue, 11 Jul 2000 07:45:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6BEiL802505
	for ngtrans-dist; Tue, 11 Jul 2000 07:44:21 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6BEgA602489;
	Tue, 11 Jul 2000 07:42:11 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA11803;
	Tue, 11 Jul 2000 07:42:10 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA15176;
	Tue, 11 Jul 2000 07:42:06 -0700 (PDT)
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 PAA114430; Tue, 11 Jul 2000 15:40:59 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id PAA17600; Tue, 11 Jul 2000 15:41:08 +0100 (BST)
Message-ID: <396B313F.644AE1E5@hursley.ibm.com>
Date: Tue, 11 Jul 2000 09:37:51 -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: Daniel Karrenberg <Daniel.Karrenberg@ripe.net>
CC: Joao Luis Silva Damas <joao@ripe.net>, 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 DocumentRevision
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]> <4.3.2.7.2.20000711102210.00d18220@localhost.ripe.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Daniel Karrenberg wrote:
> 
> At 06:59 PM 7/10/00, Brian E Carpenter wrote:
> >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
> 
> Brian,
> 
> we - the RIRs - are in no position to tell the ISPs that they are stupid and
> that they "don't understand". I think even the mighty IAB should be a little
> careful before going that route; it is the ISPs, after all, who convert
> integers to address space by routing traffic based on it.
> 
> Policies will change as we go along and all those involved understand more and
> get more comfortable with things.

Indeed, my words that you quote were written to avoid insulting the ISP's
intelligence and experience... but IPv6 is truly different.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 11 11:32:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04534
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Jul 2000 11:32:16 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA08053;
	Tue, 11 Jul 2000 09:25:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA18028;
	Tue, 11 Jul 2000 08:16:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6BFFJ302559
	for ngtrans-dist; Tue, 11 Jul 2000 08:15:19 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6BFCt602544;
	Tue, 11 Jul 2000 08:12:55 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA06394;
	Tue, 11 Jul 2000 08:12:52 -0700 (PDT)
Received: from roam.psg.com (mg-206253200-166.ricochet.net [206.253.200.166])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA27836;
	Tue, 11 Jul 2000 09:12:44 -0600 (MDT)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 13C1he-0000yU-00; Tue, 11 Jul 2000 08:12:06 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Randy Bush <rbush@bainbridge.verio.net>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: Daniel Karrenberg <Daniel.Karrenberg@ripe.net>,
        Joao Luis Silva Damas <joao@ripe.net>,
        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 DocumentRevision
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]>
	<4.3.2.7.2.20000711102210.00d18220@localhost.ripe.net>
	<396B313F.644AE1E5@hursley.ibm.com>
Message-Id: <E13C1he-0000yU-00@roam.psg.com>
Date: Tue, 11 Jul 2000 08:12:06 -0700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <rbush@bainbridge.verio.net>
Content-Transfer-Encoding: 7bit

> Indeed, my words that you quote were written to avoid insulting the ISP's
> intelligence and experience... but IPv6 is truly different.

yes.  it's not deployed.

and to get it deployed, as bernard just said well on the ietf list, we need
to make it *significantly* more attractive than the status quo, like five
times as attractive.

one attraction could be address space.  and ipv6 has a lot of it, though,
having been through some decades in this game it is hard to believe that
this year's effectively-infinite will not be next year's (or decade's) joke.

so it would be nice if we could have an ipv6 address space allocation policy
which allowed users to perceive the benefits of the larger address space.
and, imiho, we should err on the side of generosity.

but we should not forget that we have four more wonderful marvels of ipv6 to
find if we want it to sell.

randy


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 11 17:11:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20507
	for <ngtrans-archive@odin.ietf.org>; Tue, 11 Jul 2000 17:11:00 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA29647;
	Tue, 11 Jul 2000 15:09:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA04810;
	Tue, 11 Jul 2000 11:35:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6BIXbV02722
	for ngtrans-dist; Tue, 11 Jul 2000 11:33:37 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6BIXS602715
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Jul 2000 11:33:29 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA18690
	for ngtrans@sunroof.eng.sun.com; Tue, 11 Jul 2000 11:32:00 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6B8ST602344
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Jul 2000 01:28:29 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id BAA28470
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Jul 2000 01:28:28 -0700 (PDT)
Received: from postman.ripe.net (postman.ripe.net [193.0.0.199])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id CAA11275
	for <ngtrans@sunroof.eng.sun.com>; Tue, 11 Jul 2000 02:28:27 -0600 (MDT)
Received: (qmail 24942 invoked by uid 0); 11 Jul 2000 08:28:24 -0000
Received: from kantoor.ripe.net (HELO laptoy-dfk.ripe.net) (193.0.1.98)
  by postman.ripe.net with SMTP; 11 Jul 2000 08:28:24 -0000
Message-Id: <4.3.2.7.2.20000711102210.00d18220@localhost.ripe.net>
X-Sender: dfk@localhost.ripe.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 11 Jul 2000 10:28:01 +0200
To: Brian E Carpenter <brian@hursley.ibm.com>
From: Daniel Karrenberg <Daniel.Karrenberg@ripe.net>
Subject: Re: (ngtrans) Fw: [apnic-announce] IPv6 Policy Document
  Revision
Cc: Joao Luis Silva Damas <joao@ripe.net>, 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
In-Reply-To: <396A00F4.7C95A15D@hursley.ibm.com>
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]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Daniel Karrenberg <Daniel.Karrenberg@ripe.net>

At 06:59 PM 7/10/00, Brian E Carpenter wrote:
>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


Brian,

we - the RIRs - are in no position to tell the ISPs that they are stupid and
that they "don't understand". I think even the mighty IAB should be a little
careful before going that route; it is the ISPs, after all, who convert 
integers to address space by routing traffic based on it.

Policies will change as we go along and all those involved understand more and
get more comfortable with things.

Daniel




From owner-ngtrans@sunroof.eng.sun.com  Wed Jul 12 07:53:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17664
	for <ngtrans-archive@odin.ietf.org>; Wed, 12 Jul 2000 07:53:16 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA27146;
	Wed, 12 Jul 2000 05:51:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id EAA00214;
	Wed, 12 Jul 2000 04:51:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6CBoUP03428
	for ngtrans-dist; Wed, 12 Jul 2000 04:50:30 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6CBoL603421
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Jul 2000 04:50:22 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id EAA16406
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Jul 2000 04:50:20 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA26535
	for <ngtrans@sunroof.eng.sun.com>; Wed, 12 Jul 2000 05:50:19 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17554;
	Wed, 12 Jul 2000 07:50:16 -0400 (EDT)
Message-Id: <200007121150.HAA17554@ietf.org>
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ngtrans@sunroof.eng.sun.com
From: The IESG <iesg-secretary@ietf.org>
Subject: (ngtrans) Document Action: 6BONE pTLA and pNLA Formats (pTLA) to
	 Informational
Date: Wed, 12 Jul 2000 07:50:16 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: The IESG <iesg-secretary@ietf.org>



The IESG has approved the Internet-Draft '6BONE pTLA and pNLA Formats
(pTLA)' <draft-ietf-ngtrans-6bone-ptla-00.txt> as an Informational
RFC.  This document is the product of the Next Generation Transition
Working Group.  The IESG contact persons are Bert Wijnen and Randy
Bush.


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 06:31:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11655
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 06:31:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA26360;
	Thu, 13 Jul 2000 04:30:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA02344;
	Thu, 13 Jul 2000 03:28:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DARKe05051
	for ngtrans-dist; Thu, 13 Jul 2000 03:27:20 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DARC605044
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 03:27:12 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA26323
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 03:27:11 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA13807
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 03:27:10 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11075;
	Thu, 13 Jul 2000 06:27:09 -0400 (EDT)
Message-Id: <200007131027.GAA11075@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-soliman-siit-dstm-00.txt
Date: Thu, 13 Jul 2000 06:27:08 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Extensions to SIIT and DSTM for enhanced routing of
                          inbound packets
	Author(s)	: H. Soliman, E. Nordmark
	Filename	: draft-soliman-siit-dstm-00.txt
	Pages		: 17
	Date		: 12-Jul-00
	
This document specifies a transition mechanism that combines both
[SIIT] and DSTM mechanisms by adding some extensions to allow fast
routing of inbound packets. This will result in a more decentralised
and flexible tool to allow V6 only hosts to communicate with V4 only
hosts.
The proposed extensions will provide a way that allows SIIT routers
to route packets addressed to a host running a single IPv6 stack with
minimum delay which is suited to real time services.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-soliman-siit-dstm-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-soliman-siit-dstm-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-soliman-siit-dstm-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000712140159.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-soliman-siit-dstm-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-soliman-siit-dstm-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000712140159.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 08:37:31 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15853
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 08:37:31 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA15166;
	Thu, 13 Jul 2000 06:37:07 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA18164;
	Thu, 13 Jul 2000 05:36:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DCZ0V05183
	for ngtrans-dist; Thu, 13 Jul 2000 05:35:00 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DCYq605176;
	Thu, 13 Jul 2000 05:34:53 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA18061;
	Thu, 13 Jul 2000 05:34:52 -0700 (PDT)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA00899;
	Thu, 13 Jul 2000 05:34:50 -0700 (PDT)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id VAA23527;
	Thu, 13 Jul 2000 21:34:49 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id VAA10875; Thu, 13 Jul 2000 21:34:49 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.4.209]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id VAA11735; Thu, 13 Jul 2000 21:34:48 +0900 (JST)
Date: Thu, 13 Jul 2000 21:33:53 +0900 (JST)
Message-Id: <20000713.213353.104059320.kazu@Mew.org>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) IPv6 stuff on INET 2000
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
In-Reply-To: <20000615.174254.15194874.kazu@Mew.org>
References: <20000615.174254.15194874.kazu@Mew.org>
X-Mailer: Mew version 1.95b46 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
Content-Transfer-Encoding: 7bit

From: Kazu Yamamoto (山本和彦) <kazu@iijlab.net>
Subject: (ngtrans) IPv6 stuff on INET 2000

> I would like to summarize the current status of IPv6 stuff on INET
> 2000:
> 
> (1) Network Training Workshop (NTW) at Keio Univ. (not at Hokoyama), 
>     7/10-14
> 
> I'm now negotiating with some track leaders whether or not we will be
> able to take time to give IPv6 tutorial for students from developing
> countries. Itojun and Kazu have committed to be tutors.

We (itojun & kazu) have finished this jobs both for track 1 and track
2.

The material is now available from:
	http://playground.iijlab.net/material/kazu-ntw-presen/

See you in Yokohama.

--Kazu


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 17:18:31 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05269
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 17:18:30 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA27829;
	Thu, 13 Jul 2000 15:17:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA01192;
	Thu, 13 Jul 2000 14:17:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DLFoT05508
	for ngtrans-dist; Thu, 13 Jul 2000 14:15:50 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DLFf605501
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 14:15:42 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id OAA20680
	for ngtrans@sunroof.eng.sun.com; Thu, 13 Jul 2000 14:14:11 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DEpM605261;
	Thu, 13 Jul 2000 07:51:22 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA03858;
	Thu, 13 Jul 2000 07:51:21 -0700 (PDT)
From: stuart.prevost@bt.com
Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA15723;
	Thu, 13 Jul 2000 07:51:19 -0700 (PDT)
Received: from cbtlipnt01.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Thu, 13 Jul 2000 15:49:28 +0100
Received: by cbtlipnt01.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <3GLQTNG3>;
          Thu, 13 Jul 2000 15:49:25 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk>
To: ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net, mir@ripe.net,
        ipng@sunroof.eng.sun.com, sig-ipv6@apnic.net, richardj@arin.net,
        Daniel.Karrenberg@ripe.net, joao@ripe.net
Subject: (ngtrans) IPv6 Policy Document Revision suggestion
Date: Thu, 13 Jul 2000 15:47:30 +0100
X-Mailer: Internet Mail Service (5.5.2651.88)
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: stuart.prevost@bt.com

	All,

	From reading all the emails it seems that the /48 approach as the
*minimum* allocation is the way the IETF would like IPv6 deployment to
proceed.  However, as it has been demonstrated, the /35 allocations today
would only allow for 8,192 /48 per subTLA, and this is assuming that the
subTLA holder hasn't split up the NLA block so they can allocate to other
providers, in which case this figure could be as small as 256 or lower!!!!

	I see this as the reason why ISPs consider /48 for a home customer
as too large, and hence the sliding-window & /56 discussion at the last RIPE
meeting.

	Now, if the /48 allocation is the way to proceed, I feel that all
initial /35 allocations should be initially changed to /29 as the first
step.  This can be done easily as all allocations have the /29 reserved to
ensure a contiguous block.  However a /29 allows for 524,288 /48, again if
the whole subTLA is used.  So at the same time the 80% utilisation section
of the document needs to be worded correctly to allow ISPs to apply for
subsequent subTLA's.

	Also I would like to ask the following question:

	How do we move from the current allocations of /29 & /35 to RFC2374
(IPv6 Aggregatable Global Unicast Address Format) and at what stage will
this happen?
	Otherwise I can see organisations holding multiple subTLA before
moving to the address structure in RFC2374, and more renumbering pain.
	Regards,
	Stuart



Stuart Prevost
---------------------------------------------------
IP Specialist, Futures Testbed
Tel:	+44 1473 646891
Fax:	+44 1473 643906
Mobile:	+44 7801 977290
Email:	stuart.prevost@bt.com
Addr:	B29/136 - Adastral Park, Martlesham Heath, Ipswich. Suffolk. IP5 3RE




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 17:25:52 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08087
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 17:25:52 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA02731;
	Thu, 13 Jul 2000 15:25:17 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA16416;
	Thu, 13 Jul 2000 14:22:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DLKu805553
	for ngtrans-dist; Thu, 13 Jul 2000 14:20:56 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DLKo605546
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 14:20:50 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id OAA20801
	for ngtrans@sunroof.eng.sun.com; Thu, 13 Jul 2000 14:19:20 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DGY3605316
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 09:34:03 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA02006
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 09:34:01 -0700 (PDT)
Received: from moebius2.Space.Net (moebius2.Space.Net [195.30.1.100])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA26657
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jul 2000 09:33:44 -0700 (PDT)
Received: (qmail 63213 invoked by uid 1007); 13 Jul 2000 16:33:43 -0000
Date: Thu, 13 Jul 2000 18:33:43 +0200
From: Gert Doering <gert@Space.Net>
To: stuart.prevost@bt.com
Cc: ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net, mir@ripe.net,
        ipng@sunroof.eng.sun.com, sig-ipv6@apnic.net, richardj@arin.net,
        Daniel.Karrenberg@ripe.net, joao@ripe.net
Subject: (ngtrans) Re: IPv6 Policy Document Revision suggestion
Message-ID: <20000713183343.P89890@Space.Net>
References: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk>; from stuart.prevost@bt.com on Thu, Jul 13, 2000 at 03:47:30PM +0100
X-NCC-RegID: de.space
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Gert Doering <gert@Space.Net>

Hi,

On Thu, Jul 13, 2000 at 03:47:30PM +0100, stuart.prevost@bt.com wrote:
> 	From reading all the emails it seems that the /48 approach as the
> *minimum* allocation is the way the IETF would like IPv6 deployment to
> proceed.  However, as it has been demonstrated, the /35 allocations today
> would only allow for 8,192 /48 per subTLA, and this is assuming that the
> subTLA holder hasn't split up the NLA block so they can allocate to other
> providers, in which case this figure could be as small as 256 or lower!!!!
> 
> 	I see this as the reason why ISPs consider /48 for a home customer
> as too large, and hence the sliding-window & /56 discussion at the last RIPE
> meeting.

Exactly this was the reason from our side for welcoming the /48, /56, /64
suggestion: having more "elbow space" in the /35 allocated to us, being
able to do reasobale NLA structuring (to our resellers, and to *their*
resellers).

regards,

Gert Doering
        -- NetMaster
-- 
SpaceNet GmbH               Mail: netmaster@Space.Net
Joseph-Dollinger-Bogen 14   Tel : +49-89-32356-0
80807 Muenchen              Fax : +49-89-32356-299




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 17:52:06 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17340
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 17:52:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA21537;
	Thu, 13 Jul 2000 15:51:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA12724;
	Thu, 13 Jul 2000 14:51:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DLo2O05648
	for ngtrans-dist; Thu, 13 Jul 2000 14:50:02 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DLnt605641;
	Thu, 13 Jul 2000 14:49:56 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA09915;
	Thu, 13 Jul 2000 14:49:56 -0700 (PDT)
From: george.tsirtsis@bt.com
Received: from marvin.axion.bt.co.uk (marvin.axion.bt.co.uk [132.146.16.82])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA20314;
	Thu, 13 Jul 2000 15:49:54 -0600 (MDT)
Received: from cbtlipnt02.btlabs.bt.co.uk by marvin (local) with ESMTP;
          Thu, 13 Jul 2000 22:49:38 +0100
Received: by cbtlipnt02.btlabs.bt.co.uk 
          with Internet Mail Service (5.5.2651.88) id <3GKHCJ9G>;
          Thu, 13 Jul 2000 22:49:35 +0100
Message-ID: <5104D4DBC598D211B5FE0000F8FE7EB2078A59F9@mbtlipnt02.btlabs.bt.co.uk>
To: stuart.prevost@bt.com, ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net,
        mir@ripe.net, ipng@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        richardj@arin.net, Daniel.Karrenberg@ripe.net, joao@ripe.net
Subject: RE: (ngtrans) IPv6 Policy Document Revision suggestion
Date: Thu, 13 Jul 2000 22:47:34 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2651.88)
Content-Type: text/plain
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: george.tsirtsis@bt.com

Just to complement Stuart's position

> -----Original Message-----
> From:	stuart.prevost@bt.com [SMTP:stuart.prevost@bt.com]
> Sent:	Thursday, July 13, 2000 3:48 PM
> To:	ngtrans@sunroof.eng.sun.com; ipv6-wg@ripe.net; mir@ripe.net;
> ipng@sunroof.eng.sun.com; sig-ipv6@apnic.net; richardj@arin.net;
> Daniel.Karrenberg@ripe.net; joao@ripe.net
> Subject:	(ngtrans) IPv6 Policy Document Revision suggestion
> 
	From reading all the emails it seems that the /48 approach as the
*minimum* allocation is the way the IETF would like IPv6 deployment to
proceed.  However, as it has been demonstrated, the /35 allocations today
would only allow for 8,192 /48 per subTLA, and this is assuming that the
subTLA holder hasn't split up the NLA block so they can allocate to other
	providers, in which case this figure could be as small as 256 or
lower!!!!

> 	I see this as the reason why ISPs consider /48 for a home customer
> as too large, and hence the sliding-window & /56 discussion at the last
> RIPE
> meeting.
> 
> 
	Note that we recognise the benefits of /48 for multihoming/rehomeing
and maybe more importantly to make sure that IPv6 NAT will *never* become a
reality! Thus, as an ISP, we support /48 allocations if can be confident
that we can get enough of them; i.e.: we get /29s instead of /35s. 

> 	Now, if the /48 allocation is the way to proceed, I feel that all
> initial /35 allocations should be initially changed to /29 as the first
> step.  This can be done easily as all allocations have the /29 reserved to
> ensure a contiguous block.  However a /29 allows for 524,288 /48, again if
> the whole subTLA is used.  So at the same time the 80% utilisation section
> of the document needs to be worded correctly to allow ISPs to apply for
> subsequent subTLA's.
> 
	That is: the 80% (or whatever utilisation) to refer to the number of
/48s in a subTLA since ISPs will have no control over how and when our
customers, home users, SOHOs, mobile users are going to utilise their /48
prefix!

	Regards
	George


From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 13 17:53:52 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17950
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jul 2000 17:53:51 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA22847;
	Thu, 13 Jul 2000 15:53:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA26342;
	Thu, 13 Jul 2000 14:53:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6DLpo805672
	for ngtrans-dist; Thu, 13 Jul 2000 14:51:50 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6DLpf605665;
	Thu, 13 Jul 2000 14:51:42 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA25920;
	Thu, 13 Jul 2000 14:51:42 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA21534;
	Thu, 13 Jul 2000 15:51:40 -0600 (MDT)
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 WAA32046; Thu, 13 Jul 2000 22:50:35 +0100
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id WAA18482; Thu, 13 Jul 2000 22:50:54 +0100 (BST)
Message-ID: <396E3123.20A1BCE0@hursley.ibm.com>
Date: Thu, 13 Jul 2000 16:14:11 -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: Gert Doering <gert@Space.Net>
CC: stuart.prevost@bt.com, ngtrans@sunroof.eng.sun.com, ipv6-wg@ripe.net,
        mir@ripe.net, ipng@sunroof.eng.sun.com, sig-ipv6@apnic.net,
        richardj@arin.net, Daniel.Karrenberg@ripe.net, joao@ripe.net
Subject: (ngtrans) Re: IPv6 Policy Document Revision suggestion
References: <5104D4DBC598D211B5FE0000F8FE7EB207413A2D@mbtlipnt02.btlabs.bt.co.uk> <20000713183343.P89890@Space.Net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Now we're getting to the point I think.

We are messing around doing slow start and sub-allocations
inside sub-TLAs, ignoring that fact that all the sub-TLAs
together only eat up one TLA, and we have thousands of TLAs
available. There is no need to impose these artificial
constraints on the ISPs.

  Brian

Gert Doering wrote:
> 
> Hi,
> 
> On Thu, Jul 13, 2000 at 03:47:30PM +0100, stuart.prevost@bt.com wrote:
> >       From reading all the emails it seems that the /48 approach as the
> > *minimum* allocation is the way the IETF would like IPv6 deployment to
> > proceed.  However, as it has been demonstrated, the /35 allocations today
> > would only allow for 8,192 /48 per subTLA, and this is assuming that the
> > subTLA holder hasn't split up the NLA block so they can allocate to other
> > providers, in which case this figure could be as small as 256 or lower!!!!
> >
> >       I see this as the reason why ISPs consider /48 for a home customer
> > as too large, and hence the sliding-window & /56 discussion at the last RIPE
> > meeting.
> 
> Exactly this was the reason from our side for welcoming the /48, /56, /64
> suggestion: having more "elbow space" in the /35 allocated to us, being
> able to do reasobale NLA structuring (to our resellers, and to *their*
> resellers).
> 
> regards,
> 
> Gert Doering
>         -- NetMaster
> --
> SpaceNet GmbH               Mail: netmaster@Space.Net
> Joseph-Dollinger-Bogen 14   Tel : +49-89-32356-0
> 80807 Muenchen              Fax : +49-89-32356-299
> 
> --------------------------------------------------------------------
> IETF IPng Working Group Mailing List
> IPng Home Page:                      http://playground.sun.com/ipng
> FTP archive:                      ftp://playground.sun.com/pub/ipng
> Direct all administrative requests to majordomo@sunroof.eng.sun.com
> --------------------------------------------------------------------


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 14 16:18:44 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05174
	for <ngtrans-archive@odin.ietf.org>; Fri, 14 Jul 2000 16:18:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA05977;
	Fri, 14 Jul 2000 14:18:16 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA04580;
	Fri, 14 Jul 2000 13:17:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6EKG0Z06407
	for ngtrans-dist; Fri, 14 Jul 2000 13:16:00 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6EKFq606400
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 13:15:52 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA21705
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 13:15:35 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id NAA11024
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 13:15:30 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 14 Jul 2000 12:21:18 -0700 (Pacific Daylight Time)
Received: from speak.platinum.corp.microsoft.com ([172.30.236.197]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Fri, 14 Jul 2000 12:29:35 -0700
content-class: urn:content-classes:message
Subject: (ngtrans) 6to4 scale draft
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01BFEDC9.D72B848C"
Date: Fri, 14 Jul 2000 12:29:34 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4408.0
Message-ID: <CC2E64D4B3BAB646A87B5A3AE97090420B36CDF7@speak.platinum.corp.microsoft.com>
Thread-Topic: 6to4 scale draft
Thread-Index: Ab/tyb1WalwXn36lTuyLWfr2B+4gxA==
From: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
To: <internet-drafts@ietf.org>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 14 Jul 2000 19:29:35.0265 (UTC) FILETIME=[D7B22910:01BFEDC9]
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Tony Hain" <tonyhain@Exchange.Microsoft.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01BFEDC9.D72B848C
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01BFEDC9.D72B848C"


------_=_NextPart_002_01BFEDC9.D72B848C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

 <<draft-hain-6to4-scaling-00.txt>>=20

------_=_NextPart_002_01BFEDC9.D72B848C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4408.0">
<TITLE>6to4 scale draft</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><U><SPAN LANG=3D"en-us"><FONT FACE=3D"Arial" SIZE=3D2 =
COLOR=3D"#000000"> &lt;&lt;draft-hain-6to4-scaling-00.txt&gt;&gt; =
</FONT></SPAN></U><U><SPAN LANG=3D"en-us"></SPAN></U><U><SPAN =
LANG=3D"en-us"></SPAN></U><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_002_01BFEDC9.D72B848C--

------_=_NextPart_001_01BFEDC9.D72B848C
Content-Type: text/plain;
	name="draft-hain-6to4-scaling-00.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-hain-6to4-scaling-00.txt
Content-Disposition: attachment;
	filename="draft-hain-6to4-scaling-00.txt"
Content-Transfer-Encoding: base64

DQoNCk5HdHJhbnMgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBULiBIYWluIA0KSW50ZXJuZXQgRHJhZnQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBNaWNyb3NvZnQgDQpEb2N1bWVudDogZHJhZnQtaGFp
bi02dG80LXNjYWxpbmctMDAudHh0ICAgICAgICAgICAgICAgICAgICAgIEp1bHkgMjAwMCANCkNh
dGVnb3J5OiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KIA0KIA0KICAgICAgICAgICAgICAgICAgICAgNnRvNC1yZWxheSBkaXNj
b3ZlcnkgYW5kIHNjYWxpbmcgDQogDQogDQpTdGF0dXMgb2YgdGhpcyBNZW1vIA0KICAgIA0KICAg
VGhpcyBkb2N1bWVudCBpcyBhbiBJbnRlcm5ldC1EcmFmdCBhbmQgaXMgaW4gZnVsbCBjb25mb3Jt
YW5jZSB3aXRoIA0KICAgYWxsIHByb3Zpc2lvbnMgb2YgU2VjdGlvbiAxMCBvZiBSRkMyMDI2IFsx
XS4gIA0KICAgIA0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0
aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcgDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFz
LCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiBOb3RlIHRoYXQgDQogICBvdGhlciBncm91cHMgbWF5
IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0NCiAgIERyYWZ0
cy4gSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11
bSBvZiANCiAgIHNpeCBtb250aHMgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jz
b2xldGVkIGJ5IG90aGVyIA0KICAgZG9jdW1lbnRzIGF0IGFueSB0aW1lLiBJdCBpcyBpbmFwcHJv
cHJpYXRlIHRvIHVzZSBJbnRlcm5ldC0gRHJhZnRzIA0KICAgYXMgcmVmZXJlbmNlIG1hdGVyaWFs
IG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIA0KICAgcHJvZ3Jlc3MuIiAg
DQogICBUaGUgbGlzdCBvZiBjdXJyZW50IEludGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQg
YXQgDQogICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQgIA0KICAg
VGhlIGxpc3Qgb2YgSW50ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nl
c3NlZCBhdCANCiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwuIA0KICAgIA0KICAg
IA0KICAgIA0KQWJzdHJhY3QgDQogICAgDQogICBUaGUgbWVjaGFuaXNtIGZvciA2dG80LXJvdXRl
ciBzY2FsaW5nIGRlc2NyaWJlZCBpbiB0aGUgNnRvNCBkcmFmdCANCiAgIFsyXVs2dG80XSByYWlz
ZXMgY29uY2VybnMgd2hlbiB0aGUgbWF0cml4IG9mIElQdjQgY29ubmVjdGVkIHN5c3RlbXMsIA0K
ICAgY29tbXVuaWNhdGluZyBhY3Jvc3MgdG8gdGhlIG5hdGl2ZSBJUHY2IGNvbm5lY3RlZCBzeXN0
ZW1zLCBhcmUgb24gDQogICB0aGUgb3JkZXIgb2YgdGVucyB0byBodW5kcmVkcyBvZiBtaWxsaW9u
cy4gVGhpcyBkb2N1bWVudCB3aWxsIA0KICAgYWRkcmVzcyB0aG9zZSBjb25jZXJucywgb2ZmZXIg
YWRkaXRpb25hbCBtZWNoYW5pc21zIGZvciByZXNvbHZpbmcgDQogICB0aGVtLCBhbmQgaWRlbnRp
ZnkgdGhlIHNjZW5hcmlvIGZvciBsaW5rLWxvY2FsIGFkZHJlc3NpbmcgcG9zdHVsYXRlZCANCiAg
IGluIHNlY3Rpb24gMy4xLiAgDQogICAgDQogICAgDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KICANCkhhaW4gICAgICAgICAgICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjAwMCAgICAg
ICAgICAgICAgICAgICAgICAgMSAMDQogICAgICAgICAgICAgICAgICA2dG80IHJvdXRlciBkaXNj
b3ZlcnkgYW5kIHNjYWxpbmcgICAgICAgICAgIEp1bHkgMjAwMCANCg0KVGFibGUgb2YgQ29udGVu
dHMgDQogICBTdGF0dXMgb2YgdGhpcyBNZW1vLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uMSANCiAgIEFic3RyYWN0Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xIA0KICAgVGFibGUgb2YgQ29udGVu
dHMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjIgDQog
ICBUZXJtcy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uMiANCiAgIE92ZXJ2aWV3IGFuZCBhc3N1bXB0aW9ucy4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4zIA0KICAgU2NlbmFyaW9zLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjUgDQogICAgIEZp
Zy4gMS4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uNSANCiAgICAgU2VxdWVuY2UgU2NlbmFyaW8gMTouLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi42IA0KICAgICBTZXF1ZW5jZSBTY2VuYXJpbyAyOi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjcgDQogICBOUyBzeW50YXgu
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
OSANCiAgIE5BIHN5bnRheC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi45IA0KICAgUmVkaXJlY3Qgc3ludGF4Li4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMTAgDQogICAgIFByb3RlY3Rpb24gZnJv
bSByYW5kb20gcmVkaXJlY3RzOi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMSANCiAg
IEFkZGl0aW9uYWwgUmVxdWlyZW1lbnRzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLjExIA0KICAgQWRkaXRpb25hbCBUaG91Z2h0cy4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMTIgDQogICBTZWN1cml0eSBDb25zaWRlcmF0aW9u
cy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMiANCiAgIFJlZmVy
ZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLjEyIA0KICAgQWNrbm93bGVkZ21lbnRzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uMTMgDQogICBBdXRob3IncyBBZGRyZXNzZXMuLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4xMyANCiAgICANCiAgICANCiAg
IENvbnZlbnRpb25zIHVzZWQgaW4gdGhpcyBkb2N1bWVudCANCiAgICANCiAgIFRoZSBrZXkgd29y
ZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwg
DQogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAgIk1BWSIsIGFuZCAi
T1BUSU9OQUwiIGluIA0KICAgdGhpcyBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMg
ZGVzY3JpYmVkIGluIFJGQy0yMTE5IFszXS4gDQogICAgDQogICAgDQogICAgDQpUZXJtcyANCiAg
IChleHBhbmRpbmcgc2xpZ2h0bHkgb24gdGhlIGRlZmluaXRpb25zIGluIFs2dG80XSkgDQogICAg
DQogICA2dG80LXJvdXRlcjogYW4gSVB2NiByb3V0ZXIgc3VwcG9ydGluZyBhIDZ0bzQgcHNldWRv
LWludGVyZmFjZS4gSXQgDQogICBpcyBub3JtYWxseSB0aGUgYm9yZGVyIHJvdXRlciBiZXR3ZWVu
IGFuIElQdjYgc2l0ZSBhbmQgYSB3aWRlLWFyZWEgDQogICBJUHY0IG5ldHdvcmsuIFdoZW4gbm90
IGFjdGluZyBhcyBhIHJlbGF5LCBpdCBhZHZlcnRpc2VzIA0KICAgWzIwMDI6SVB2NDo6LzQ4XSBh
cyBhbiBhdHRhY2hlZCBwcmVmaXggb24gSVB2NiBlbmFibGVkIGludGVyZmFjZXMuIA0KICAgIA0K
ICAgUmVsYXkgcm91dGVyOiBhIDZ0bzQtcm91dGVyIGNvbmZpZ3VyZWQgdG8gc3VwcG9ydCB0cmFu
c2l0IHJvdXRpbmcgDQogICBiZXR3ZWVuIDZ0bzQgYWRkcmVzc2VzIGFuZCBuYXRpdmUgSVB2NiBh
ZGRyZXNzZXMuIEFkdmVydGlzZXMgdGhlIA0KICAgWzIwMDI6Oi8xNl0gYXMgYW4gYXR0YWNoZWQg
cHJlZml4IG9uIG5hdGl2ZSBJUHY2IGVuYWJsZWQgaW50ZXJmYWNlcy4gDQogICAocmVmZXJyZWQg
dG8gYXMgNnRvNC1yZWxheSBpbiB0aGlzIGRvY3VtZW50KSANCiAgICANCiAgIDZ0bzQgbm9ybWFs
IGhvc3Q6IGFuIElQdjYgaG9zdCwgd2hpY2ggaGFwcGVucyB0byBoYXZlIGF0IGxlYXN0IG9uZSAN
CiAgIDZ0bzQgYWRkcmVzcyBsZWFybmVkIGZyb20gYSA2dG80LXJvdXRlci4gSW4gYWxsIG90aGVy
IHJlc3BlY3RzIGl0IGlzIA0KICAgYSBzdGFuZGFyZCBJUHY2IGhvc3QuIA0KICAgIA0KICAgNnRv
NCBpbnRlZ3JhdGVkIGhvc3Q6IGFuIElQdjYgaG9zdCB0aGF0IGdlbmVyYXRlcyBhdCBsZWFzdCBv
bmUgNnRvNCANCiAgIGFkZHJlc3MgYW5kIHN1cHBvcnRpbmcgNnRvNCBwc2V1ZG8taW50ZXJmYWNl
IGZyb20gYW4gSVB2NCBhZGRyZXNzLiANCiAgIEl0IGludGVyYWN0cyBkaXJlY3RseSB3aXRoIHJl
bGF5cywgYnV0IGluIGFsbCBvdGhlciByZXNwZWN0cyBpdCBpcyBhIA0KICAgc3RhbmRhcmQgSVB2
NiBob3N0LiANCiAgICANCiAgICANCiAgICANCiAgICAgDQpIYWluICAgICAgICAgICAgICAgICAg
ICBFeHBpcmVzIERlY2VtYmVyIDIwMDAgICAgICAgICAgICAgICAgICAgICAgIDIgDA0KICAgICAg
ICAgICAgICAgICAgNnRvNCByb3V0ZXIgZGlzY292ZXJ5IGFuZCBzY2FsaW5nICAgICAgICAgICBK
dWx5IDIwMDAgDQoNCiAgICANCk92ZXJ2aWV3IGFuZCBhc3N1bXB0aW9ucyANCiAgICANCiAgIFRo
ZSBpbnRlbnQgb2YgdGhpcyBhcHByb2FjaCBpcyB0byB1c2UgdGhlIG1lY2hhbmlzbSBkZWZpbmVk
IGluIA0KICAgWzZ0bzRdIGFzIGEgc2ltcGxpZmllciBmb3IgcHJvdmlkaW5nIElQdjYgc2Vydmlj
ZXMgdG8gYW55IG5vZGUgd2l0aCANCiAgIGEgcHVibGljIElQdjQgYWRkcmVzcy4gKFdoaWxlIElQ
djQtY29tcGF0aWJsZSBJUHY2IGFkZHJlc3NlcyB3b3VsZCANCiAgIGJlIGFub3RoZXIgb3B0aW9u
LCB0aGVyZSBoYXZlIGJlZW4gcXVlc3Rpb25zIHJhaXNlZCByZWxhdGVkIHRvIHRoZWlyIA0KICAg
dXNlIGFuZCB0aGUgc2NhbGluZyBpbXBhY3Qgb24gdGhlIElQdjYgcm91dGluZyB0YWJsZXMuKSBU
aGUgDQogICB0ZWNobmljYWwgYXNwZWN0cyBvZiBjcmVhdGluZyB0aGUgYXBwcm9wcmlhdGUgYWRk
cmVzc2VzIGFyZSBub3QgYW4gDQogICBpc3N1ZSwgYnV0IHRoZXJlIGlzIGFuIGFyZWEgb2YgY29u
Y2VybiByZWxhdGVkIHRvIGRpc2NvdmVyeSBvZiB0aGUgDQogICBwYXRoIGZyb20gNnRvNCBub2Rl
cyB0byBuYXRpdmUtSVB2NiBub2Rlcy4gU2V2ZXJhbCBzY2hlbWVzIGhhdmUgYmVlbiANCiAgIHBy
b3Bvc2VkLCBhbmQgdGhlIGFwcHJvYWNoIGRlc2NyaWJlZCBoZXJlIGRvZXMgbm90IHByZWNsdWRl
IGFueSBvZiANCiAgIHRoZW0uIFdoYXQgaXQgZG9lcyBpcyBwcm92aWRlIGFuIGFsdGVybmF0aXZl
IHRoYXQgYXV0b21hdGVzIHRoZSANCiAgIHByb2Nlc3Mgb24gYSBtYXNzaXZlIHNjYWxlLCB3aXRo
b3V0IHJlcXVpcmluZyB0aGUgNnRvNCByb3V0ZXJzIHRvIA0KICAgcGFydGljaXBhdGUgZGlyZWN0
bHkgaW4gYSBnbG9iYWwgcm91dGluZyBwcm9jZXNzLiAgDQogICAgDQogICBPbmUgd2F5IHRvIGxv
b2sgYXQgdGhpcyBhcHByb2FjaCBpcyBhbiBhdXRvbWF0ZWQgdHVubmVsIGJyb2tlciB0aGF0IA0K
ICAgaXMgdGllZCB0byB0aGUgY3VycmVudCByb3V0aW5nIGluZnJhc3RydWN0dXJlLiBFeGlzdGlu
ZyB0dW5uZWwgDQogICBicm9rZXIgbW9kZWxzIGV4cGVjdCBtYW51YWwgaW50ZXJhY3Rpb24gYW5k
IGJhc2ljYWxseSBzZXQgdXAgYSANCiAgIGRlZmF1bHQgcm91dGUgdG8gdGhlIGVudGlyZSBuYXRp
dmUgSVB2NiBpbmZyYXN0cnVjdHVyZS4gSWYgdGhlIA0KICAgbmF0aXZlIElQdjYgbmV0d29yayBw
YXJ0aXRpb25zLCB0aGUgY29tbXVuaWNhdGlvbnMgd2lsbCBmYWlsIGV2ZW4gDQogICB0aG91Z2gg
dGhlIElQdjQgbmV0d29yayBpcyBpbnRhY3QuIFRoZSBhcHByb2FjaCBwcmVzZW50ZWQgaGVyZSB3
b3VsZCANCiAgIHRoZW9yZXRpY2FsbHkgYWxsb3cgZm9yIGlzbGFuZHMgb2YgbmF0aXZlIElQdjYg
dG8gZXhpc3QgYXJvdW5kIHRoZSANCiAgIGVkZ2Ugb2YgdGhlIElQdjQgY2xvdWQsIGFzIGxvbmcg
YXMgdGhlIHJlZ2lvbmFsIHJlbGF5cyBrbm93IHRoZSANCiAgIGN1cnJlbnQgcHJlZml4IHRvIElQ
djQgbWFwcGluZyBmb3IgdGhlIHJlbGF5cy4gDQogICAgDQogICBBbm90aGVyIHdheSB0byBsb29r
IGF0IHRoaXMgYXBwcm9hY2ggaXMgYSBkZWZhdWx0IHJvdXRlIHRoYXQgb25seSANCiAgIGhhbmRs
ZXMgb25lIHBhY2tldCBwZXIgcHJlZml4LCBhbmQgdGhlbiByZWRpcmVjdHMgZWFjaCBub2RlIGRp
cmVjdGx5IA0KICAgYXR0YWNoZWQgdG8gdGhlIElQdjQgbmV0d29yayB0byB0aGUgYXBwcm9wcmlh
dGUgbmF0aXZlLUlQdjYtSVNQIA0KICAgNnRvNC1yZWxheSBmb3Igc3Vic2VxdWVudCBwYWNrZXRz
LiAgDQogICAgDQogICBUaGUgZGVmYXVsdCByb3V0ZSBhcHByb2FjaCB3b3JrcyBiZWNhdXNlIGZy
b20gdGhlIHBlcnNwZWN0aXZlIG9mIHRoZSANCiAgIDZ0bzQtcm91dGVyIChvciBpbnRlZ3JhdGVk
IGhvc3QpLCB0aGUgZW50aXJlIElQdjQgSW50ZXJuZXQgYXBwZWFycyANCiAgIHRvIGJlIGEgc2lu
Z2xlLXN1Ym5ldCBsaW5rLWxheWVyLiBXaGlsZSBzZWN0aW9uIDMuMSBvZiBbNnRvNF0gDQogICBk
aXNjdXNzZXMgdGhlIGZvcm1hdGlvbiBvZiBhZGRyZXNzZXMgaW4gYSBsaW5rLWxvY2FsIGNvbnRl
eHQsIGl0IA0KICAgcXVlc3Rpb25zIHRoZSB1dGlsaXR5IG9mIHN1Y2ggYWRkcmVzc2VzLiBUaGUg
bWVjaGFuaXNtIGRlc2NyaWJlZCANCiAgIGhlcmUgYW5zd2VycyB0aGUgcXVlc3Rpb24gYnkgdGFr
aW5nIGFkdmFudGFnZSBvZiB0aGUgZm9ybWF0IGZvciANCiAgIGNvbW11bmljYXRpbmcgd2l0aCBh
IHdlbGwta25vd24gcmVsYXksIGFzIHdlbGwgYXMgaW4gdGhlIHJlZGlyZWN0IA0KICAgbWVzc2Fn
ZXMgc2VudCBieSByZWxheXMuIEEgZmluYWwgcG9pbnQgdG8gbWFrZSBpcyB0aGF0IGluIGFkZGl0
aW9uIA0KICAgdG8gYXBwZWFyaW5nIGFzIGEgc2luZ2xlIGxpbmstbGF5ZXIsIHRoZSBJUHY0IElu
dGVybmV0IGRvZXMgbm90IA0KICAgcHJvdmlkZSBtdWx0aWNhc3QgdG8gYWxsIHBvaW50cywgc28g
aXQgc2hvdWxkIGJlIGNvbnNpZGVyZWQgYW4gTkJNQSANCiAgIG5ldHdvcmsuIFNpbmNlIHRoZSBJ
UHY0IEludGVybmV0IGFwcGVhcnMgdG8gYmUgYSBzaW5nbGUgbGluayB0byA2dG80IA0KICAgbm9k
ZXMsIGFsbCBydWxlcyBpbiBzZWN0aW9uIDggb2YgWzRdW05EXSBhcHBseSB0byByZWRpcmVjdHMg
DQogICBkZXNjcmliZWQgaGVyZSwgRVhDRVBUIHRoZSBvbmUgYXQgdGhlIGVuZCBvZiA4LjIgdGhh
dCBwcm9oaWJpdHMgDQogICByb3V0ZXJzIGZyb20gdXBkYXRpbmcgcm91dGVzIGJhc2VkIG9uIHJl
ZGlyZWN0cy4gSXQgc2hvdWxkIGFsc28gYmUgDQogICBub3RlZCB0aGF0IHBhcnQgb2YgYSBwcmV2
aW91c2x5IHJlc2VydmVkIGZpZWxkIGlzIG5vdyBkZWZpbmVkLiANCiAgICANCiAgIEEgYmFzaWMg
YXNzdW1wdGlvbiBpcyB0aGF0IGEgNnRvNCBiYXNlZCBJUHY2IGRlcGxveW1lbnQgd2lsbCBub3Qg
DQogICByZWx5IG9uIEFOWSBzdXBwb3J0IGZyb20gSVB2NCBvbmx5IElTUCdzLiBJZiBhIDZ0bzQt
cmVsYXkgKHdpbGxpbmcgDQogICB0byB0YWtlIHRoZSB0cmFmZmljKSBleGlzdHMsIGEgc2l0ZSA2
dG80LXJvdXRlciBtYXkgYmUgY29uZmlndXJlZCB0byANCiAgIHVzZSB0aGF0IHBhdGggYXMgdGhl
IGRlZmF1bHQgcm91dGUgdG8gdGhlIG5hdGl2ZSBJUHY2IGluZnJhc3RydWN0dXJlIA0KICAgdGhy
b3VnaCBhIHR1bm5lbCBicm9rZXIsIG9yIG90aGVyIG1lYW5zLiBJZiB0aGVyZSBpcyBubyBjb25m
aWd1cmVkIA0KICAgcmVsYXksIHRoZSBkZWZhdWx0IGJlaGF2aW9yIG9mIDZ0bzQtcm91dGVycyBT
SE9VTEQgYmUgdG8gdXNlIGEgd2VsbC0NCg0KICAgICANCkhhaW4gICAgICAgICAgICAgICAgICAg
IEV4cGlyZXMgRGVjZW1iZXIgMjAwMCAgICAgICAgICAgICAgICAgICAgICAgMyAMDQogICAgICAg
ICAgICAgICAgICA2dG80IHJvdXRlciBkaXNjb3ZlcnkgYW5kIHNjYWxpbmcgICAgICAgICAgIEp1
bHkgMjAwMCANCg0KICAga25vd24gc3RhcnRpbmcgcG9pbnQgdG8gZmluZCBhIDZ0bzQtcmVsYXkg
dGhhdCB3aWxsIGdldCBpdCB0byB0aGUgDQogICBuYXRpdmUgSVB2NiBlbmRwb2ludC4gDQogICAg
DQogICBBbm90aGVyIGFzc3VtcHRpb24gaXMgdGhhdCBlYWNoIElTUCBwcm92aWRpbmcgbmF0aXZl
IElQdjYgc2VydmljZXMgDQogICB3aWxsIGJlIG1vdGl2YXRlZCB0byBwcm92aWRlIGEgcmVsYXkg
c2VydmljZSBmb3IgdGhlaXIgY3VzdG9tZXJzIHRvIA0KICAgY29tbXVuaWNhdGUgd2l0aCA2dG80
IHNpdGVzLiBBdCB0aGUgc2FtZSB0aW1lLCB0aGVzZSBJU1BzIHdpbGwgDQogICBnZW5lcmFsbHkg
bm90IHdhbnQgdG8gYmUgdGhlICdkZWZhdWx0JyByb3V0ZSBiZXR3ZWVuIDZ0bzQgJiBuYXRpdmUg
DQogICBJUHY2IGluZnJhc3RydWN0dXJlcy4gVGhleSB3aWxsIGFsc28gbm90IGJlIGV4Y2l0ZWQg
YWJvdXQgbWFuYWdpbmcgYSANCiAgIG1hc3NpdmUgbWFudWFsbHkgY29uZmlndXJlZCB0dW5uZWwg
YXJyYXkgKG5vIG1hdHRlciB3aGljaCBlbmQgdGhlIA0KICAgbWFudWFsIGVmZm9ydCBpcyBhcHBs
aWVkIHRvKS4gT25jZSBhIDZ0bzQtcm91dGVyIChpbnRlZ3JhdGVkIGhvc3QpIA0KICAgYWNxdWly
ZXMgYSBwcmVmaXggdG8gcmVsYXkgbWFwcGluZywgaXQgU0hPVUxEIHNlbmQgTlMgbWVzc2FnZXMg
dG8gDQogICBtYWludGFpbiB0aGUgbWFwcGluZyB1bnRpbCBpZGxlIGZvciAyIGxpZmV0aW1lcy4g
VG8gYWlkIHdpdGggDQogICBzY2FsaW5nLCB0aGVyZSBpcyBubyBuZWVkIGZvciB0aGUgcmVsYXkg
dG8gbWFpbnRhaW4gYSBtYXBwaW5nIHRvIHRoZSANCiAgIDZ0bzQtcm91dGVyIChpbnRlZ3JhdGVk
IGhvc3QpIGFzIHRoZSByZXF1aXJlZCBpbmZvcm1hdGlvbiBpcyBpbiB0aGUgDQogICBkZXN0aW5h
dGlvbiBhZGRyZXNzIG9mIGVhY2ggcGFja2V0IGhlYWRlci4gIA0KICAgIA0KICAgQ29uc3VtZXIg
c3lzdGVtcyAoaWU6ZGlhbC11cCkgd2lsbCBiZSBjb21wbGV0ZWx5IGF1dG9tYXRlZCA2dG80IA0K
ICAgaW50ZWdyYXRlZCBob3N0cy4gVG8gbWFrZSB0aGlzIGF1dG9tYXRpb24gd29yaywgYSB3ZWxs
LWtub3duIHJlbGF5IA0KICAgc2VydmljZSBuZWVkcyB0byBleGlzdCBhbmQgYmUgY2FwYWJsZSBv
ZiBoYW5kbGluZyBncmVhdGVyIHRoYW4gMTBNIA0KICAgY2xpZW50cy4gVGhpcyByZXN1bHRzIGlu
IHNjYWxpbmcgaXNzdWVzIHRoYXQgYXJlIGNvbXBhcmFibGUgdG8gdGhlIA0KICAgRE5TIHJvb3Qu
ICANCiAgICANCiAgIE1haW50YWluaW5nIGEgc3RhdGljIGRhdGFiYXNlIHdpdGggZnVsbCBJUHY2
IGFkZHJlc3NlcyBvZiB0aGUgDQogICBjdXJyZW50IElTUCByZWxheXMgaXMgb3BlcmF0aW9uYWxs
eSBjb21wbGV4LiBBcyBvbmx5IHRoZSBJUHY0IA0KICAgYWRkcmVzcyBhcmUgcmVxdWlyZWQgd2hl
biB1c2luZyBsaW5rLWxvY2FsIFtGRTgwOjpJUHY0XSBmb3JtYXQgDQogICBhZGRyZXNzZXMsIHRo
aXMgaGFzIGJldHRlciBzY2FsaW5nIHByb3BlcnRpZXMgZm9yIGRhdGFiYXNlIA0KICAgbWFpbnRl
bmFuY2UuIChUaGUgQW55Y2FzdCBhZGRyZXNzIFsyMDAyOklQdjQ6OjBdIHdvdWxkIGJlIGEgDQog
ICBjb21wYXJhYmxlIGFsdGVybmF0aXZlLCBidXQgcmVkaXJlY3QgbWVzc2FnZXMgcmVxdWlyZSB1
c2Ugb2YgYSBsaW5rLQ0KICAgbG9jYWwgYWRkcmVzcykuICANCiAgICANCiAgIFRoZSByZWdpb25h
bCBhY2Nlc3MgcmVsYXlzIGRlc2NyaWJlZCBiZWxvdyBhcmUgY3VycmVudGx5IGFzc3VtZWQgdG8g
DQogICBiZSBnZW9ncmFwaGljYWwsIGJ1dCB0aGUgbmF0aXZlLUlQdjYtSVNQIG9uZXMgdGhleSBy
ZWRpcmVjdCB0byBhcmUgDQogICBhc3N1bWVkIHRvIGJlIHRvcG9sb2dpY2FsbHkgbmVhciB0aGUg
bmF0aXZlIElQdjYgZW5kLiANCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCiAgICAgDQpIYWluICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIwMDAg
ICAgICAgICAgICAgICAgICAgICAgIDQgDA0KICAgICAgICAgICAgICAgICAgNnRvNCByb3V0ZXIg
ZGlzY292ZXJ5IGFuZCBzY2FsaW5nICAgICAgICAgICBKdWx5IDIwMDAgDQoNClNjZW5hcmlvcyAN
CiAgICANCiAgIDEuIEEgQ29uc3VtZXIgc3lzdGVtIGRpYWxzIGludG8gdGhlaXIgcHJlZmVycmVk
IElTUCBhbmQgb25seSANCiAgIHJlY2VpdmVzIElQdjQgc2VydmljZS4gVXNpbmcgdGhlIDZ0bzQg
bWVjaGFuaXNtcyBhcyBkZWZpbmVkLCB0aGUgDQogICBzeXN0ZW0gY3JlYXRlcyBJUHY2IGFkZHJl
c3NlcyBmb3IgaXRzIGludGVyZmFjZS4gTGF0ZXIgYW4gDQogICBhcHBsaWNhdGlvbiBhdHRlbXB0
cyB0byBjb25uZWN0IHRvIGEgc3lzdGVtIHRoYXQgaXMgY29ubmVjdGVkIHRvIGEgDQogICBuYXRp
dmUgSVB2NiBuZXR3b3JrIChub24tMjAwMjo6KS4gVGhlIGNvbnN1bWVyIHN5c3RlbSBmb3J3YXJk
cyB0aGUgDQogICBmaXJzdCBwYWNrZXQgdG8gdGhlIHdlbGwta25vd24gcmVsYXkgNnRvNC1yZWxh
eS5pcHY2Lm9yZywgYW5kIA0KICAgdmVyaWZpZXMgdGhlIHJlZGlyZWN0IGl0IHJlY2VpdmVzIGZv
ciB0aGUgZGVzdGluYXRpb24gcHJlZml4LiANCiAgIEZ1cnRoZXIgY29tbXVuaWNhdGlvbnMgYXJl
IGRpcmVjdGVkIHRvIHRoZSBuYXRpdmUtSVB2Ni1JU1AgNnRvNC0NCiAgIHJlbGF5LiBOUyBtZXNz
YWdlcyBTSE9VTEQgYmUgc2VudCB0byB0aGUgbmF0aXZlLUlQdjYtSVNQIDZ0bzQtcmVsYXkgDQog
ICB0byBtYWludGFpbiB0aGlzIFByZWZpeCAvIElQdjQgYWRkcmVzcyAvIExpZmV0aW1lIG1hcHBp
bmcgdW50aWwgaWRsZSANCiAgIGZvciBhdCBsZWFzdCB0d28gbGlmZXRpbWVzLiANCiAgICANCiAg
IDIuIEFuIElQdjYgb25seSBzeXN0ZW0gaW5pdGlhdGVzIGEgY29ubmVjdGlvbiB0byBhIDZ0bzQg
d2ViIHNpdGUuIA0KICAgVGhlIG5hdGl2ZS1JUHY2LUlTUCA2dG80LXJlbGF5IGV4dHJhY3RzIHRo
ZSBJUHY0IGFkZHJlc3MgZnJvbSB0aGUgDQogICBkZXN0aW5hdGlvbiBJUHY2IGFkZHJlc3MsIGFu
ZCB0dW5uZWxzIHBlciB0aGUgNnRvNCBzcGVjaWZpY2F0aW9uLiANCiAgIFRoZSA2dG80LXJvdXRl
ciB3aWxsIHVzZSB0aGUgcmVzcG9uc2UgZnJvbSB0aGUgd2ViIHNpdGUgdG8gZXN0YWJsaXNoIA0K
ICAgdGhlIG1hcHBpbmcgYmV0d2VlbiB0aGUgbmF0aXZlLUlQdjYgcHJlZml4LCBhbmQgaXRzIDZ0
bzQtcmVsYXkgdmlhIA0KICAgdGhlIHdlbGwta25vd24gNnRvNC1yZWxheS4gTlMgbWVzc2FnZXMg
U0hPVUxEIGJlIHNlbnQgdG8gdGhlIG5hdGl2ZS0NCiAgIElQdjYtSVNQIDZ0bzQtcmVsYXkgdG8g
bWFpbnRhaW4gdGhpcyBQcmVmaXggLyBJUHY0IGFkZHJlc3MgLyANCiAgIExpZmV0aW1lIG1hcHBp
bmcgaW5mb3JtYXRpb24gdW50aWwgaWRsZSBmb3IgYXQgbGVhc3QgdHdvIGxpZmV0aW1lcy4gIA0K
ICAgIA0KICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAtLS0t
LSAgICAgLS0tLS0tLS0tLS0tIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIHwgICAgIHwgICB8IDZ0bzQtcmVsYXkufCANCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8IEROUyB8ICAgfEFSLmlwdjYub3JnIHwgDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIC0tLS0tICAgICAtLS0tLS0tLS0tLS0gDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCAgICAgICB8IA0KICAgICAgIC0t
LS0tLS0tLS0tLS0gICAgIC0tLS0tLS0tLS0tLSAgICAgLS0tLS0tLS0tLS0gICAgIC0tLS0tLS0t
LS0gDQogICAgICB8IE5hdGl2ZSBJUHY2IHwgICB8IDZ0bzQtcmVsYXkgfCAgIHwgSVB2NCBvbmx5
IHwgICB8IENvbnN1bWVyIHwgDQogICAgICB8ICAgICBzeXN0ZW0gIHwtLy18ICAgSVB2NiBJU1Ag
fC0tLXwgSW50ZXJuZXQgIHwtLy18IHN5c3RlbSAgIHwgDQogICAgICAgLS0tLS0tLS0tLS0tLSAg
ICAgLS0tLS0tLS0tLS0tICAgICAtLS0tLS0tLS0tLSAgICAgLS0tLS0tLS0tLSANCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIC0tLS0tLS0tLS0tLS0gICAgIC0tLS0tIA0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IDZ0bzQtcm91dGVyIHwgICB8
IFdlYiB8IA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgICAg
ICAgICAgIHwtLS18IHNpdGV8IA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgLS0tLS0tLS0tLS0tLSAgICAgLS0tLS0gDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAtLS0tLSAN
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGaWcuIDEgDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCiAgICAgDQpIYWluICAgICAgICAgICAgICAgICAgICBFeHBpcmVzIERlY2Vt
YmVyIDIwMDAgICAgICAgICAgICAgICAgICAgICAgIDUgDA0KICAgICAgICAgICAgICAgICAgNnRv
NCByb3V0ZXIgZGlzY292ZXJ5IGFuZCBzY2FsaW5nICAgICAgICAgICBKdWx5IDIwMDAgDQoNClNl
cXVlbmNlIFNjZW5hcmlvIDE6IA0KICAgIA0KICAgICAgMSkgVGhlIDZ0bzQgcHJvY2VzcyBpbiBh
IGNvbnN1bWVyIHN5c3RlbSBhdXRvbWF0aWNhbGx5IGxvb2tzIHVwIA0KICAgICAgICAgIHRoZSBJ
UHY0IGFkZHJlc3Mgb2YgdGhlIHdlbGwta25vd24gcmVsYXkgNnRvNC1yZWxheS5pcHY2Lm9yZyAN
CiAgICAgICAgICBmb3IgYW55IG5vbi0yMDAyOjogZGVzdGluYXRpb24gdGhhdCBkb2VzIG5vdCBt
YXRjaCBhIHByZWZpeCANCiAgICAgICAgICBpbiB0aGUgcm91dGluZyBjYWNoZSwgdXNpbmcgSVB2
NC4gDQogICAgICAgDQogICAgICAyKSBETlMgcmV0dXJucyBhIENuYW1lIGJhc2VkIG9uIHRoZSBS
SVIgb2YgdGhlIHJlcXVlc3RvcnMgSVB2NC4gDQogICAgICAgDQogICAgICAzKSBUaGUgNnRvNCBw
cm9jZXNzIHRoZW4gYXV0b21hdGljYWxseSBsb29rcyB1cCA2dG80LQ0KICAgICAgICAgIHJlbGF5
LlJJUi5pcHY2Lm9yZyANCiAgICAgICANCiAgICAgIDQpIEROUyByZXR1cm5zIGEgdHJhZGl0aW9u
YWwgSVB2NCByb3VuZC1yb2JpbiBmb3IgcmVsYXlzIHBlciANCiAgICAgICAgICByZWdpb24uICAN
CiAgICAgICANCiAgICAgIDUpIFRoZSA2dG80IHByb2Nlc3MgdXNlcyA2dG80IHJ1bGVzIGZvciBs
aW5rLWxvY2FsIGFuZCB0dW5uZWxzIA0KICAgICAgICAgIHRoZSBpbml0aWFsIHBhY2tldCB0byB0
aGUgcmVnaW9uYWwgcmVsYXkuICANCiAgICAgICANCiAgICAgIDYpIFJlZ2lvbmFsIFJlZ2lzdHJp
ZXMgaGF2ZSBjb2xsZWN0ZWQgSVB2NCBhZGRyZXNzZXMgb2YgSVNQIA0KICAgICAgICAgIDZ0bzQt
cmVsYXlzIGFzIGVhY2ggSVB2NiBwcmVmaXggaXMgYWxsb2NhdGVkLiANCiAgICAgICANCiAgICAg
IDcpIFJlZ2lvbmFsIGFjY2VzcyBhbmQgSVNQIHJlbGF5cyBwYXJ0aWNpcGF0ZSBpbiB0aGUgZ2xv
YmFsIEJHUCANCiAgICAgICAgICBtZXNoLiAgDQogICAgICAgDQogICAgICA4KSBSZWdpb25hbCBh
Y2Nlc3MgcmVsYXkgc2VuZHMgSVB2NiBwcmVmaXgtYmFzZWQgcmVkaXJlY3QgdG8gdGhlIA0KICAg
ICAgICAgIENvbnN1bWVyIHN5c3RlbSwgcG9pbnRpbmcgaXQgdG8gdGhlIG5hdGl2ZS1JUHY2LUlT
UCA2dG80LQ0KICAgICAgICAgIHJlbGF5IGhhdmluZyB0aGUgbG9uZ2VzdCBtYXRjaC4gSXQgdGhl
biBmb3J3YXJkcyB0aGUgb3JpZ2luYWwgDQogICAgICAgICAgcGFja2V0IHRvIHRoZSBpZGVudGlm
aWVkIG5hdGl2ZS1JUHY2LUlTUCA2dG80LXJlbGF5LiANCiAgICAgICANCiAgICAgIDkpIFRoZSA2
dG80IHByb2Nlc3MgYnVpbGRzIGEgcm91dGluZyB0YWJsZSBjYWNoZSBmcm9tIHRoZSANCiAgICAg
ICAgICByZWRpcmVjdCBtZXNzYWdlcy4gSXQgZmlyc3QgdmVyaWZpZXMgdGhlIHJlZGlyZWN0IHRo
cm91Z2ggdGhlIA0KICAgICAgICAgIG5ldyAnVHVubmVsIElkZW50JyBmaWVsZCAoSVB2NCBJZGVu
dGlmaWVyIGluIG9yaWdpbmFsIHR1bm5lbCANCiAgICAgICAgICBwYWNrZXQpLiBTdWJzZXF1ZW50
IHR1bm5lbGluZyBpcyBiYXNlZCBvbiBsb25nZXN0IG1hdGNoIG9uIA0KICAgICAgICAgIHByZWZp
eC4gT25jZSBpdCBrbm93cyB0aGUgbmVpZ2hib3IsIHRoZSA2dG80LXJvdXRlciwgb3IgDQogICAg
ICAgICAgaW50ZWdyYXRlZCBob3N0LCBTSE9VTEQgc2VuZCBOUyB0byB0aGUgSVNQIHJlbGF5IGl0
IHdhcyANCiAgICAgICAgICByZWRpcmVjdGVkIHRvIGZvciBtYWludGVuYW5jZSBvZiB0aGUgbWFw
cGluZy4gDQogICAgICAgDQogICAgICAxMCkgVGhlIDZ0bzQgcHJvY2VzcyByZXNlbmRzIGZpcnN0
IHBhY2tldCwgbm93IHR1bm5lbGVkIHRvIHRoZSANCiAgICAgICAgICBuYXRpdmUtSVB2Ni1JU1Ag
NnRvNC1yZWxheSB0b3BvbG9naWNhbGx5IGNsb3Nlc3QgdG8gdGhlIA0KICAgICAgICAgIG5hdGl2
ZSBJUHY2IGVuZCBvZiB0aGlzIHRyYWZmaWMgZmxvdy4gDQogICAgICAgDQogICAgICAxMSkgRGVz
dGluYXRpb24gSVNQIHJlbGF5IGZvcndhcmRzIHdpdGhpbiB0aGUgSVB2NiBuZXR3b3JrLiAoSXQg
DQogICAgICAgICAgU0hPVUxEIGFscmVhZHkgYmUgYWR2ZXJ0aXNpbmcgdGhlIHJldHVybiByb3V0
ZSB0byAyMDAyOjovMTYuKSANCiAgICAgICANCiAgICAgIDEyKSBUaGUgTmF0aXZlLUlQdjYgc3lz
dGVtIHNlbmRzIGFuIEFjayBmb3IgZmlyc3QgcGFja2V0IHZpYSB0aGUgDQogICAgICAgICAgbmVh
cmVzdCByZWxheSBhZHZlcnRpc2luZyAyMDAyOjovMTYuIA0KICAgICAgIA0KICAgICAgMTMpIFRo
ZSBOYXRpdmUtSVB2Ni1JU1AgNnRvNC1yZWxheSBleHRyYWN0cyB0aGUgSVB2NCBmcm9tIA0KICAg
ICAgICAgIGRlc3RpbmF0aW9uIGluIHBhY2tldCBoZWFkZXIgYW5kIHR1bm5lbHMgdGhlIHBhY2tl
dCBhY3Jvc3MgDQogICAgICAgICAgdGhlIElQdjQgbG9naWNhbCBsaW5rLiANCiAgICAgICANCiAg
IC0tLS0tLSANCg0KDQogICAgIA0KSGFpbiAgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNl
bWJlciAyMDAwICAgICAgICAgICAgICAgICAgICAgICA2IAwNCiAgICAgICAgICAgICAgICAgIDZ0
bzQgcm91dGVyIGRpc2NvdmVyeSBhbmQgc2NhbGluZyAgICAgICAgICAgSnVseSAyMDAwIA0KDQog
DQpTZXF1ZW5jZSBTY2VuYXJpbyAyOiANCiAgICANCiAgICAgIDEuIFRoZSBOYXRpdmUtSVB2NiBz
eXN0ZW0gbG9va3MgdXAgdGhlIG5hbWUgNnRvNC13ZWItc2l0ZS4gICANCiAgICAgICANCiAgICAg
IDIuIEROUyBNQVkgcmV0dXJuIGEgMjAwMjo6IHJlY29yZCBpbiBhIHRyYWRpdGlvbmFsIHJvdW5k
LXJvYmluIA0KICAgICAgICAgIGZvciB0aGUgd2ViIHNpdGUuIA0KICAgICAgIA0KICAgICAgMy4g
VGhlIG5hdGl2ZS1JUHY2IHN5c3RlbSBzZW5kcyBpdHMgZmlyc3QgcGFja2V0IHZpYSB0aGUgbmVh
cmVzdCANCiAgICAgICAgICByZWxheSBhZHZlcnRpc2luZyAyMDAyOjovMTYuIA0KICAgICAgIA0K
ICAgICAgNC4gVGhlIG5hdGl2ZS1JUHY2LUlTUCA2dG80LXJlbGF5IGV4dHJhY3RzIHRoZSBJUHY0
IGZyb20gDQogICAgICAgICAgZGVzdGluYXRpb24gaW4gcGFja2V0IGhlYWRlciBhbmQgdHVubmVs
cyB0aGUgcGFja2V0IGFjcm9zcyANCiAgICAgICAgICB0aGUgSVB2NCBsb2dpY2FsIGxpbmsuICAN
CiAgICAgICANCiAgICAgIDUuIFRoZSA2dG80LXJvdXRlciBmb3IgdGhlIHdlYiBzaXRlIGZvcndh
cmRzIHRoZSBwYWNrZXQgdG8gdGhlIA0KICAgICAgICAgIGRlc3RpbmF0aW9uIHdlYiBzaXRlLiAN
CiAgICAgICANCiAgICAgIDYuIFRoZSBXZWIgc2l0ZSBzZW5kcyBhbiBBQ0sgdmlhIGl0cyA2dG80
LXJvdXRlci4gDQogICAgICAgDQogICAgICA3LiBUaGUgNnRvNCBwcm9jZXNzIGluIHRoZSA2dG80
LXJvdXRlciBsb29rcyB1cCB0aGUgSVB2NCBhZGRyZXNzIA0KICAgICAgICAgIG9mIHRoZSB3ZWxs
LWtub3duIHJlbGF5IDZ0bzQtcmVsYXkuaXB2Ni5vcmcgZm9yIGFueSBub24tDQogICAgICAgICAg
MjAwMjo6IGRlc3RpbmF0aW9uIHRoYXQgZG9lcyBub3QgbWF0Y2ggYSBwcmVmaXggaW4gdGhlIA0K
ICAgICAgICAgIHJvdXRpbmcgY2FjaGUsIHVzaW5nIElQdjQuIA0KICAgIA0KICAgICAgOC4gRE5T
IHJldHVybnMgYSBDbmFtZSBiYXNlZCBvbiB0aGUgUklSIG9mIHRoZSByZXF1ZXN0b3JzIElQdjQu
IA0KICAgICAgIA0KICAgICAgOS4gVGhlIDZ0bzQgcHJvY2VzcyB0aGVuIGF1dG9tYXRpY2FsbHkg
bG9va3MgdXAgNnRvNC0NCiAgICAgICAgICByZWxheS5SSVIuaXB2Ni5vcmcgDQogICAgICAgDQog
ICAgICAxMC4gRE5TIHJldHVybnMgYSB0cmFkaXRpb25hbCBJUHY0IHJvdW5kLXJvYmluIGZvciBy
ZWxheXMgcGVyIA0KICAgICAgICAgIHJlZ2lvbi4gIA0KICAgICAgIA0KICAgICAgMTEuIFRoZSA2
dG80IHByb2Nlc3MgdXNlcyA2dG80IHJ1bGVzIGZvciBsaW5rLWxvY2FsIGFuZCB0dW5uZWxzIA0K
ICAgICAgICAgIHRoZSBwYWNrZXQgdG8gdGhlIHJlZ2lvbmFsIHJlbGF5LiANCiAgICAgICANCiAg
ICAgIDEyLiBSZWdpb25hbCBSZWdpc3RyaWVzIGhhdmUgY29sbGVjdGVkIElQdjQgYWRkcmVzc2Vz
IG9mIElTUCANCiAgICAgICAgICA2dG80LXJlbGF5cyBhcyBlYWNoIElQdjYgcHJlZml4IGlzIGFs
bG9jYXRlZC4gDQogICAgICAgDQogICAgICAxMy4gUmVnaW9uYWwgYWNjZXNzIGFuZCBJU1AgcmVs
YXlzIHBhcnRpY2lwYXRlIGluIHRoZSBnbG9iYWwgQkdQIA0KICAgICAgICAgIG1lc2guIA0KICAg
ICAgIA0KICAgICAgMTQuIFJlZ2lvbmFsIGFjY2VzcyByZWxheSBzZW5kcyBJUHY2IHByZWZpeC1i
YXNlZCByZWRpcmVjdCB0byB0aGUgDQogICAgICAgICAgNnRvNCByb3V0ZXIsIHBvaW50aW5nIGl0
IHRvIHRoZSBuYXRpdmUtSVB2Ni1JU1AgNnRvNC1yZWxheSANCiAgICAgICAgICBoYXZpbmcgdGhl
IGxvbmdlc3QgbWF0Y2guICANCiAgICAgICANCiAgICAgIDE1LiBUaGUgNnRvNC1yb3V0ZXIgYnVp
bGRzIGEgcm91dGluZyB0YWJsZSBjYWNoZSBmcm9tIHRoZSANCiAgICAgICAgICByZWRpcmVjdCBt
ZXNzYWdlcy4gSXQgZmlyc3QgdmVyaWZpZXMgdGhlIHJlZGlyZWN0IHRocm91Z2ggdGhlIA0KICAg
ICAgICAgIG5ldyAnVHVubmVsIElkZW50JyBmaWVsZCAoSVB2NCBJZGVudGlmaWVyIGluIG9yaWdp
bmFsIHR1bm5lbCANCiAgICAgICAgICBwYWNrZXQpLiBTdWJzZXF1ZW50IHR1bm5lbGluZyBpcyBi
YXNlZCBvbiBsb25nZXN0IG1hdGNoIG9uIA0KICAgICAgICAgIHByZWZpeC4gT25jZSBpdCBrbm93
cyB0aGUgbmVpZ2hib3IsIHRoZSA2dG80LXJvdXRlciwgb3IgDQogICAgICAgICAgaW50ZWdyYXRl
ZCBob3N0LCBTSE9VTEQgc2VuZCBOUyB0byB0aGUgSVNQIHJlbGF5IGl0IHdhcyANCiAgICAgICAg
ICByZWRpcmVjdGVkIHRvIGZvciBtYWludGVuYW5jZSBvZiB0aGUgbWFwcGluZy4gDQogICAgICAg
DQogICAgIA0KSGFpbiAgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAyMDAwICAg
ICAgICAgICAgICAgICAgICAgICA3IAwNCiAgICAgICAgICAgICAgICAgIDZ0bzQgcm91dGVyIGRp
c2NvdmVyeSBhbmQgc2NhbGluZyAgICAgICAgICAgSnVseSAyMDAwIA0KDQogICAgICAqKiogVGhp
cyBjcmVhdGVzIGEgcGVyY2VpdmVkIHByb2JsZW0gOiAtcm91dGVyIHJlc3BvbmRpbmcgdG8gDQog
ICAgICAgICAgcmVkaXJlY3QtIEFjdHVhbGx5IFJGQyAxODEyIFs1XVtyb3V0ZXJyZXFdIDUuMi43
LjIgc3RhdGVzIA0KICAgICAgICAgICdNQVkgY29uc2lkZXIgcmVkaXJlY3Qgd2hlbiBub3QgcnVu
bmluZyBhIHJvdXRpbmcgcHJvdG9jb2wnLCANCiAgICAgICAgICB3aGljaCBpcyB0aGUgY2FzZSBh
dCBoYW5kOyBhdCBsZWFzdCB3aXRoIG90aGVyIHBhcnRpZXMgDQogICAgICAgICAgaW52b2x2ZWQg
d2l0aCB0aGlzIGxvZ2ljYWwgbGluay4gIA0KICAgICAgIA0KICAgICAgMTYuIDZ0bzQtcm91dGVy
IGZvcndhcmRzIHRvIG5hdGl2ZS1JUHY2LUlTUCA2dG80LXJlbGF5IGJhc2VkIG9uIA0KICAgICAg
ICAgIHRoZSBsb25nZXN0IG1hdGNoLiANCiAgICAgICANCiAgICAgIDE3LiBOYXRpdmUtSVB2Ni1J
U1AgNnRvNC1yZWxheSBmb3J3YXJkcyB0byBOYXRpdmUtSVB2NiBzeXN0ZW0uIA0KICAgICAgIA0K
ICAgLS0tLS0tLSANCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCiAgICAgDQpIYWluICAgICAg
ICAgICAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIwMDAgICAgICAgICAgICAgICAgICAgICAg
IDggDA0KICAgICAgICAgICAgICAgICAgNnRvNCByb3V0ZXIgZGlzY292ZXJ5IGFuZCBzY2FsaW5n
ICAgICAgICAgICBKdWx5IDIwMDAgDQoNCk5TIHN5bnRheCANCiAgICANCiAgIDAgICAgICAgICAg
ICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMgDQogICAw
IDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDgg
OSAwIDEgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKyANCiAgIHwgICAgVHlwZSAoMTM1KSB8ICAgIENvZGUgKDApICAg
fCAgICAgICAgICBDaGVja3N1bSAgICAgICAgICAgICB8IA0KICAgKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgUmVzZXJ2ZWQgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICB+ICAgICAgICAgICAgICAgICAg
ICAgICBUYXJnZXQgQWRkcmVzcyAgICAoRkU4MDo6SVB2NCkgICAgICAgICAgfiANCiAgIHwgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB8IA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSsgDQogICB8ICAgICBUeXBlICgyKSAgfCAgICBMZW5ndGggKDEpIHwg
ICAgICAgICAgICBNVVNUIGJlIDAgICAgICAgICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAg
ICAgICAgICBMaW5rLUxheWVyIEFkZHJlc3MgKElQdjQgb2YgNnRvNC1yb3V0ZXIpICAgICAgICAg
IHwgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKyANCiAgICANCiAgICANCk5BIHN5bnRheCANCiAgICANCiAgIDAgICAg
ICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMg
DQogICAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUg
NiA3IDggOSAwIDEgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgIHwgICAgVHlwZSAoMTM2KSB8ICAgIENvZGUg
KDEpICAgfCAgICAgICAgICBDaGVja3N1bSAgICAgICAgICAgICB8IA0KICAgKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQog
ICB8UnxTfE98ICAgICAgICAgICAgICAgICAgICAgUmVzZXJ2ZWQgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICB+ICAgICAgICAgICAg
ICAgICAgICAgICBUYXJnZXQgQWRkcmVzcyAgICAoRkU4MDo6SVB2NCkgICAgICAgICAgfiANCiAg
IHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICB8IA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8ICAgICBUeXBlICgyKSAgfCAgICBMZW5ndGgg
KDEpIHwgICAgICAgICAgICBNVVNUIGJlIDAgICAgICAgICAgfCANCiAgICstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAg
fCAgICAgICAgICAgICBMaW5rLUxheWVyIEFkZHJlc3MgKElQdjQgb2YgNnRvNC1yZWxheSkgICAg
ICAgICAgIHwgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgIHwgICAgIFR5cGUgKDMpICB8ICAgIExlbmd0aCAo
NCkgfCBQcmVmaXggTGVuZ3RoIHxMfEF8IFJlc2VydmVkMSB8IA0KICAgKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8
ICAgICAgICAgICAgICAgICAgICAgICAgIFZhbGlkIExpZmV0aW1lICAgICAgICAgICAgICAgICAg
ICAgICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgUHJlZmVy
cmVkIExpZmV0aW1lICAgICAgICAgICAgICAgICAgICAgIHwgDQogICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgIHwg
ICAgICAgICAgICAgICAgICAgICAgICAgICBSZXNlcnZlZDIgICAgICAgICAgICAgICAgICAgICAg
ICAgICB8IA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgIH4gICAgICAgICAgICAgUHJl
Zml4IChmcm9tIHRhYmxlIGZvciB0aGlzIHRhcmdldCkgICAgICAgICAgICAgICB+IA0KICAgfCAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIHwgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKyANCiAgICANCiAgIENvZGUgaXMgc2V0IHRvIDEgdG8gaWRlbnRp
ZnkgbmV3IG1lc3NhZ2Ugd2l0aCBwcmVmaXggaW5mb3JtYXRpb24gDQogICAgDQogICBSLWJpdCBp
cyBzZXQgYXMgdGhlIDZ0bzQtcmVsYXkgaXMgbG9naWNhbGx5IGEgcm91dGVyIA0KICAgUy1iaXQg
aXMgc2V0IGluIHJlc3BvbnNlIHRvIHNvbGljaXRhdGlvbiANCiAgIE8tYml0IGlzIGNsZWFyZWQg
dG8gcHJldmVudCB0aHJhc2hpbmcgDQogICAgIA0KSGFpbiAgICAgICAgICAgICAgICAgICAgRXhw
aXJlcyBEZWNlbWJlciAyMDAwICAgICAgICAgICAgICAgICAgICAgICA5IAwNCiAgICAgICAgICAg
ICAgICAgIDZ0bzQgcm91dGVyIGRpc2NvdmVyeSBhbmQgc2NhbGluZyAgICAgICAgICAgSnVseSAy
MDAwIA0KDQpSZWRpcmVjdCBzeW50YXggDQogICAgDQogICAoRXhwYW5kcyBzY29wZSBmb3IgcmVk
aXJlY3QgZnJvbSBob3N0IHRvIHByZWZpeCkgDQogICAgDQogICAwICAgICAgICAgICAgICAgICAg
IDEgICAgICAgICAgICAgICAgICAgMiAgICAgICAgICAgICAgICAgICAzIA0KICAgMCAxIDIgMyA0
IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIA0K
ICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSsgDQogICB8ICAgIFR5cGUgKDEzNykgfCAgICBDb2RlICgwKSAgIHwgICAgICAg
ICAgQ2hlY2tzdW0gICAgICAgICAgICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgICAgIFJlc2VydmVkICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQog
ICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKyANCiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgfiAgICAgICAgICAgICAgICAgICAgICAgVGFy
Z2V0IEFkZHJlc3MgKEZFODA6OklQdjQpICAgICAgICAgICAgIH4gDQogICB8ICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAg
ICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIHwgDQogICB+ICAgICAgICAgICAgICAgICAgICAgRGVzdGlu
YXRpb24gQWRkcmVzcyAgICAgICAgICAgICAgICAgICAgICAgfiANCiAgIHwgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAg
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSsgDQogICB8ICAgICBUeXBlICgyKSAgfCAgICBMZW5ndGggKDEpIHwgICAgICAgICAg
ICBNVVNUIGJlIDAgICAgICAgICAgfCANCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgfCAgICAgICAgICAgICBM
aW5rLUxheWVyIEFkZHJlc3MgKElQdjQgb2YgNnRvNC1yZWxheSkgICAgICAgICAgIHwgDQogICAr
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKyANCiAgIHwgICAgIFR5cGUgKDMpICB8ICAgIExlbmd0aCAoNCkgfCBQcmVmaXggTGVu
Z3RoIHxMfEF8IFJlc2VydmVkMSB8IA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8ICAgICAgICAgICAgICAg
ICAgICAgICAgIFZhbGlkIExpZmV0aW1lICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgICst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgUHJlZmVycmVkIExpZmV0aW1lICAg
ICAgICAgICAgICAgICAgICAgIHwgDQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgIHwgICAgICAgICAgICAgICAg
ICAgICAgICAgICBSZXNlcnZlZDIgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSsgDQogICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCANCiAgIH4gICAgICAgICAgICAgUHJlZml4IChmcm9tIHRhYmxl
IGZvciB0aGlzIHRhcmdldCkgICAgICAgICAgICAgICB+IA0KICAgfCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICArLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKyANCiAgIHwgICAgIFR5cGUgICg0KSB8ICAgIExlbmd0aCAgICAgfCAgICAgICAgVHVubmVs
IElkZW50ICAgICAgICAgICB8IA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICB8ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgUmVzZXJ2ZWQgICAgICAgICAgICAgICAgICAgICAgICAgICAgfCANCiAgICstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rIA0KICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIHwgDQogICB+ICAgICAgICAgICAgICAgICAgICAgICBJUCBoZWFkZXIg
KyBkYXRhICAgICAgICAgICAgICAgICAgICAgICAgfiANCiAgIHwgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSsgDQogICAgDQogICBJUCBoZWFkZXIgKyBkYXRhIGlzIHRoZSBvcmlnaW5hbCBwYWNrZXQgdHJ1
bmNhdGVkIHRvIGVuc3VyZSB0aGF0IHRoZSANCiAgIHNpemUgb2YgdGhlIHJlZGlyZWN0IG1lc3Nh
Z2UgZG9lcyBub3QgZXhjZWVkIDEyODAgb2N0ZXRzLiANCiAgICANCiAgIFZhbGlkIGxpZmV0aW1l
IGFuZCBQcmVmZXJyZWQgbGlmZXRpbWUgYXJlIHNldCB0byB0aGUgdGltZSByZW1haW5pbmcgDQog
ICB1bnRpbCBuZXh0IHNjaGVkdWxlZCBCR1AgdXBkYXRlICANCiAgICANCiAgICdUdW5uZWwgSWRl
bnQnIGlzIHVzZWQgZm9yIHNwb29mIHByb3RlY3Rpb24sIGFuZCBpcyBmaWxsZWQgaW4gZnJvbSAN
CiAgIHRoZSBJZGVudGl0eSBmaWVsZCBmcm9tIHRoZSBJUHY0IGhlYWRlciBvZiB0aGUgNnRvNCBw
YWNrZXQuICANCiAgICANCg0KICAgICANCkhhaW4gICAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
RGVjZW1iZXIgMjAwMCAgICAgICAgICAgICAgICAgICAgICAxMCAMDQogICAgICAgICAgICAgICAg
ICA2dG80IHJvdXRlciBkaXNjb3ZlcnkgYW5kIHNjYWxpbmcgICAgICAgICAgIEp1bHkgMjAwMCAN
Cg0KUHJvdGVjdGlvbiBmcm9tIHJhbmRvbSByZWRpcmVjdHM6IA0KICAgIA0KICAgRm9yIHNpbXBs
ZSBzcG9vZiBwcm90ZWN0aW9uLCB0aGUgdXBwZXIgMTYgYml0cyBvZiB0aGUgJ1R1bm5lbCBJZGVu
dCcgDQogICBmaWVsZCAocHJldmlvdXNseSByZXNlcnZlZCkgaW4gdGhlIFJlZGlyZWN0ZWQgSGVh
ZGVyIG9wdGlvbiBhcmUgdXNlZCANCiAgIHRvIHJlZmxlY3QgdGhlIElkZW50aWZpZXIgZmllbGQg
ZnJvbSB0aGUgb3V0ZXIgSVB2NCBoZWFkZXIgb2YgdGhlIA0KICAgb3JpZ2luYWwgcGFja2V0IHNl
bnQgdG8gdGhlIFJlZ2lvbmFsIFJlbGF5LiBUaGlzIGNvbWJpbmVkIHdpdGggdGhlIA0KICAgb3Jp
Z2luYWwgcGFja2V0IGNvbnRlbnRzIG1pdGlnYXRlIGd1ZXNzaW5nIG9yIGZsb29kaW5nIGF0dGFj
a3MsIGFuZCANCiAgIHZpcnR1YWxseSByZXF1aXJlIGFjY2VzcyB0byB0aGUgcGFja2V0IHBhdGgg
dG8gZ2VuZXJhdGUgYSB2YWxpZCANCiAgIHNwb29mLiAgDQogICAgDQogICAgDQpBZGRpdGlvbmFs
IFJlcXVpcmVtZW50cyANCiAgICANCiAgIFJlZ2lvbmFsIHJlbGF5cyBhcmUgcnVuIGFzIGlwdjYu
b3JnIG5hbWVkIHNlcnZpY2UgYnkgdGhlIFJlZ2lvbmFsIA0KICAgSW50ZXJuZXQgUmVnaXN0cmll
cyAoUklScykuICANCiAgICANCiAgIFJlZ2lzdHJhdGlvbiBvZiBuYXRpdmUtSVB2Ni1JU1AgcmVs
YXlzIGlzIGhhbmRsZWQgdGhyb3VnaCBSSVJzLCANCiAgIGJlY2F1c2UgYSB0cnVzdCBtb2RlbCBl
eGlzdHMgYW5kIGl0IGFwcGVhcnMgdG8gYmUgYW4gZWFzeSBhZGRpdGlvbiANCiAgIHRvIHRoZSBh
bGxvY2F0aW9uIHByb2Nlc3MuIA0KICAgIA0KICAgUmVnaW9uYWwgcmVsYXlzIFNIT1VMRCBhZGRy
ZXNzIHNjYWxpbmcgdG8gc3VwcG9ydCB0aGUgbnVtYmVyIG9mIA0KICAgZGlyZWN0bHkgYXR0YWNo
ZWQgSVB2NCBzeXN0ZW1zIGluIHRoZWlyIGFyZWEsIGFuZCBmb3J3YXJkIGFueSANCiAgIHBhY2tl
dHMgcmVjZWl2ZWQgdG8gdGhlIHNhbWUgSVNQIHJlbGF5IGl0IGlkZW50aWZpZWQgaW4gdGhlIHBy
ZWZpeC0NCiAgIGJhc2VkIHJlZGlyZWN0IGRlZmluZWQgYWJvdmUuIFNldmVyZSByYXRlIGxpbWl0
aW5nIE1BWSBiZSBpbXBvc2VkIHRvIA0KICAgZGlzY291cmFnZSA2dG80LXJvdXRlcnMgYW5kIGlu
dGVncmF0ZWQgaG9zdHMgZnJvbSBpZ25vcmluZyB0aGVzZSANCiAgIHJlZGlyZWN0IG1lc3NhZ2Vz
LiAgDQogICAgDQogICA2dG80IGludGVncmF0ZWQgaG9zdHMsIHJvdXRlcnMsIGFuZCByZWxheXMg
TVVTVCByZWNvZ25pemUgYW5kIA0KICAgcmVzcG9uZCB0byBJQ01QIG1lc3NhZ2VzIHRhcmdldGVk
IGZvciBbRkU4MDo6SVB2NF0gdGhhdCBhcmUgcmVjZWl2ZWQgDQogICBvbiB0aGUgNnRvNCBpbnRl
cmZhY2UuIA0KICAgIA0KICAgNnRvNC1yb3V0ZXJzIFNIT1VMRCBlc3RhYmxpc2ggTlVEIChhcyBk
ZWZpbmVkIGluIHNlY3Rpb24gMy44IG9mIA0KICAgWzZdW21lY2hdKSB3aXRoIDZ0bzQtcmVsYXlz
IHRoZXkgYXJlIHJlZGlyZWN0ZWQgdG8sIGFuZCBhdm9pZCANCiAgIHRocmFzaGluZyBpZiBtdWx0
aXBsZSByZWxheXMgZXhpc3QgZm9yIGEgZ2l2ZW4gcHJlZml4LiBUaGUgSVNQIA0KICAgcmVsYXlz
IE1BWSBlc3RhYmxpc2ggTlVEIHdpdGggdGhlIHJvdXRlcnMgaWYgZGVzaXJlZCwgdGhvdWdoIHRo
aXMgDQogICB3aWxsIGNyZWF0ZSBzY2FsaW5nIGNvbmNlcm5zIHdpdGggdGhlIG9ubHkgbWFyZ2lu
YWwgYmVuZWZpdCBiZWluZyANCiAgIHRoZSByYXBpZCByZW1vdmFsIG9mIGFjY2VzcyB0byBub2Rl
cyBiZWhpbmQgdGhlIGFuIGluZGl2aWR1YWwgSVB2NCANCiAgIGFkZHJlc3MuICANCiAgICANCiAg
IDZ0bzQtcm91dGVycyBNQVkgY2hvb3NlIHRvIHRpbWUgb3V0IHRoaXMgcHJlZml4IGVudHJ5IGlm
IHRoZXJlIGlzIG5vIA0KICAgdHJhZmZpYyBmb3IgdHdvIHZhbGlkIGxpZmV0aW1lcy4gDQogICAg
DQogICA2dG80LXJlbGF5cyBTSE9VTEQgYWRkcmVzcyBzY2FsaW5nIGZvciBib3RoIHRyYWZmaWMg
aGFuZGxpbmcgYW5kIE5VRCANCiAgIGV4Y2hhbmdlcy4gDQogICAgDQogICA2dG80LXJlbGF5cyBN
QVkgc2VuZCBwcmVmaXggYmFzZWQgcmVkaXJlY3RzIHRvIHByb3ZpZGUgbG9hZCANCiAgIGJhbGFu
Y2luZyBhbW9uZyByZWxheXMgbm90IGRpcmVjdGx5IGlkZW50aWZpZWQgdmlhIEJHUC4gDQogICAg
DQogICBOZWlnaGJvciBzb2xpY2l0YXRpb24gKHR5cGUgMTM1KSBpcyBzZW50IHdoZW4gdGhlIGxp
ZmV0aW1lIGV4cGlyZXMuIA0KICAgVGhlIDZ0bzQtcmVsYXkgU0hPVUxEIGFuc3dlciBpZiBpdCBp
cyBzdGlsbCB3aWxsaW5nIHRvIGZvcndhcmQgd2l0aCANCiAgIGEgTmVpZ2hib3IgQWR2ZXJ0aXNl
bWVudCAodHlwZSAxMzYpIGluY2x1ZGluZyB0aGUgb3B0aW9ucyBkZWZpbmVkIA0KICAgZm9yIHJl
ZGlyZWN0LiANCiAgICANCiAgICANCiAgICAgDQpIYWluICAgICAgICAgICAgICAgICAgICBFeHBp
cmVzIERlY2VtYmVyIDIwMDAgICAgICAgICAgICAgICAgICAgICAgMTEgDA0KICAgICAgICAgICAg
ICAgICAgNnRvNCByb3V0ZXIgZGlzY292ZXJ5IGFuZCBzY2FsaW5nICAgICAgICAgICBKdWx5IDIw
MDAgDQoNCkFkZGl0aW9uYWwgVGhvdWdodHMgDQogICAgDQogICBTZXBhcmF0ZSByZWdpb25hbCBy
ZWxheXMgYXJlIG5vdCByZXF1aXJlZCBpZiBuYXRpdmUtSVB2Ni1JU1BzIGFyZSANCiAgIHdpbGxp
bmcgdG8gaGF2ZSB0aGVpciByZWxheXMgYWN0IGFzIHRoZSBmaXJzdCBwYWNrZXQgdG9wLWxldmVs
IA0KICAgcmVkaXJlY3RvcnMgZm9yIG5vbi1jdXN0b21lcnMuIFRoZSBvbmx5IHJlcXVpcmVtZW50
cyBhcmUgDQogICBlc3RhYmxpc2hpbmcgd2hvIG1hbmFnZXMgdGhlIHJvdW5kLXJvYmluIEROUyBl
bnRyaWVzIGZvciBlYWNoIA0KICAgcmVnaW9ucyByZWxheSBuYW1lOyBhbmQgdGhhdCBhbGwgc3lz
dGVtcyBpbiB0aGF0IGxpc3QgYmUgDQogICBwYXJ0aWNpcGFudHMgaW4gdGhlIGdsb2JhbCBCR1Ag
bWVzaCwgYXMgd2VsbCBhcyB3aWxsaW5nIGFuZCBjYXBhYmxlIA0KICAgb2YgZ2VuZXJhdGluZyB0
aGUgcHJlZml4IGJhc2VkIHJlZGlyZWN0cy4gIA0KICAgIA0KICAgIA0KU2VjdXJpdHkgQ29uc2lk
ZXJhdGlvbnMgDQogDQogICBUaGlzIGRvY3VtZW50IGRvZXMgbm90IGludHJvZHVjZSBhbnkgbmV3
IHNlY3VyaXR5IGNvbmNlcm5zLCBhbmQgDQogICBhdHRlbXB0cyB0byBhZGQgc29tZSBsZXZlbCBv
ZiBwcm90ZWN0aW9uIGZyb20gc3Bvb2ZlZCByZWRpcmVjdHMgDQogICByZWNlaXZlZCBvdmVyIHRo
ZSA2dG80IGludGVyZmFjZS4gQmFzaWMgcHJvdGVjdGlvbiBmcm9tIHNwb29mZWQgDQogICByZWRp
cmVjdHMgaXMgcHJvdmlkZWQgdW5sZXNzIHRoZSByb3V0aW5nIHBhdGggaW5mcmFzdHJ1Y3R1cmUg
aXMgDQogICBwZW5ldHJhdGVkLiBBZGRpdGlvbmFsIHByb3RlY3Rpb24gb2YgdGhlIHJlZGlyZWN0
IGlzIHBvc3NpYmxlIHVzaW5nIA0KICAgSVBzZWMuIFRoaXMgYXBwcm9hY2ggaXMgbm90IHVzZWQg
YnkgZGVmYXVsdCwgYXMgdGhlIGNhc2Ugd2hlcmUgaXQgaXMgDQogICBuZWNlc3NhcnkgaXMgcmFy
ZSwgYW5kIHRoZSBjb3N0IGlzIHJlbGF0aXZlbHkgaGlnaC4gDQogICAgDQogICBEZW5pYWwtb2Yt
U2VydmljZSBhdHRhY2tzIGFyZSBwb3NzaWJsZSBhZ2FpbnN0IHRoZSBjb21tb24gDQogICBpbmZy
YXN0cnVjdHVyZSBpbiB0aGUgUmVnaW9uYWwgUmVsYXlzLiBJZiBzdWNoIGFuIGF0dGFjayBpcyBk
ZXRlY3RlZCANCiAgIHRoZSB0YXJnZXRlZCByZWxheSBNQVkgY2hvb3NlIHRvIHN0b3AgZm9yd2Fy
ZGluZyBwYWNrZXRzIGFuZCBvbmx5IA0KICAgaXNzdWUgcmVkaXJlY3RzLiBUaGlzIHdpbGwgaW1w
YWN0IGFwcGxpY2F0aW9uIHJlc3BvbnNpdmVuZXNzIGFzIA0KICAgcGFja2V0cyBhcmUgZGlzY2Fy
ZGVkLCBidXQgbm90IGFzIGRyYW1hdGljYWxseSBhcyBsb29zaW5nIGFsbCANCiAgIGFiaWxpdHkg
dG8gZmluZCB0aGUgbmF0aXZlIElQdjYgcmVsYXlzIHNob3VsZCB0aGUgcmVnaW9uYWwgcmVsYXlz
IA0KICAgYmVjb21lIGludW5kYXRlZC4gIA0KICAgIA0KICAgRGVuaWFsLW9mLXNlcnZpY2UgYXR0
YWNrcyBhZ2FpbnN0IG90aGVyIGNvbXBvbmVudHMgZGVzY3JpYmVkIGhlcmUgDQogICBhcmUgYmV5
b25kIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LCBhcyB0aG9zZSBjb21wb25lbnRzIGFyZSBu
b3QgDQogICBjb21tb24gaW5mcmFzdHJ1Y3R1cmUgYW5kIHRoZWlyIGRlZmVuc2UgaXMgYSBsb2Nh
bCBtYXR0ZXIuICANCiAgICANCiAgICANClJlZmVyZW5jZXMgDQogICAgDQogDQogICAxICBbUkZD
LTIwMjZdLCBCcmFkbmVyLCBTLiwgIiBUaGUgSW50ZXJuZXQgU3RhbmRhcmRzIFByb2Nlc3MgLS0g
DQogICAgICBSZXZpc2lvbiAzIiwgQkNQIDksIFJGQyAyMDI2LCBPY3RvYmVyIDE5OTYuIA0KICAg
IA0KICAgMiAgWzZ0bzRdLCBDYXJwZW50ZXIsIEIuLCAiQ29ubmVjdGlvbiBvZiBJUHY2IERvbWFp
bnMgdmlhIElQdjQgDQogICAgICBDbG91ZHMgd2l0aG91dCBFeHBsaWNpdCBUdW5uZWxzIiwgZHJh
ZnQtaWV0Zi1uZ3RyYW5zLTZ0bzQtMDYudHh0LCANCiAgICAgIEp1bmUgMjAwMCANCiAgICANCiAg
IDMgIFtSRkMtMjExOV0sIEJyYWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0
byBJbmRpY2F0ZSANCiAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTks
IE1hcmNoIDE5OTcgDQogICAgDQogICA0ICBbTkRdLCBOYXJ0ZW4sIFQuLCBOb3JkbWFyaywgRS4s
IFNpbXBzb24sIFcuLCAiTmVpZ2hib3IgRGlzY292ZXJ5IA0KICAgICAgZm9yIElQIFZlcnNpb24g
NiIsIFJGQyAyNDYxLCBEZWNlbWJlciAxOTk4IA0KICAgIA0KICAgNSAgW3JvdXRlcnJlcV0gQmFr
ZXIsIEYuLCAiUmVxdWlyZW1lbnRzIGZvciBJUCBWZXJzaW9uIDQgUm91dGVycyIsIA0KICAgICAg
UkZDLTE4MTIsIEp1bmUgMTk5NSANCiAgICANCiANCiAgICAgDQpIYWluICAgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIERlY2VtYmVyIDIwMDAgICAgICAgICAgICAgICAgICAgICAgMTIgDA0KICAg
ICAgICAgICAgICAgICAgNnRvNCByb3V0ZXIgZGlzY292ZXJ5IGFuZCBzY2FsaW5nICAgICAgICAg
ICBKdWx5IDIwMDAgDQoNCiANCiAgIDYgIFttZWNoXSwgTm9yZG1hcmssIEUuLCBHaWxsaWdhbiwg
Ui4gRS4sICJUcmFuc2l0aW9uIE1lY2hhbmlzbXMgZm9yIA0KICAgICAgSVB2NiBIb3N0cyBhbmQg
Um91dGVycyIsIEFwcmlsIDE0LCAyMDAwIA0KICAgIA0KICAgIA0KICAgIA0KICAgIA0KQWNrbm93
bGVkZ21lbnRzIA0KICAgIA0KICAgVGhhbmtzIGZvciBjcml0aXF1ZSBvZiB0aGlzIGRvY3VtZW50
IHByb3ZpZGVkIGJ5IENocmlzdGlhbiBIdWl0ZW1hLCANCiAgIERhdmlkIFRoYWxlciwgRnJlZCBC
YWtlciBhbmQgQnJpYW4gQ2FycGVudGVyLiAgDQogICAgDQogICAgDQpBdXRob3IncyBBZGRyZXNz
ZXMgDQogICAgDQogICBUb255IEhhaW4gDQogICBNaWNyb3NvZnQgDQogICBPbmUgTWljcm9zb2Z0
IFdheSANCiAgIFJlZG1vbmQsIFdhLiBVU0EgIDk4MDUyIA0KICAgRW1haWw6IHRvbnloYWluQG1p
Y3Jvc29mdC5jb20gDQogICAgDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQogICAgIA0KSGFpbiAgICAgICAgICAgICAgICAg
ICAgRXhwaXJlcyBEZWNlbWJlciAyMDAwICAgICAgICAgICAgICAgICAgICAgIDEzIAw=

------_=_NextPart_001_01BFEDC9.D72B848C--


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 14 17:16:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23374
	for <ngtrans-archive@odin.ietf.org>; Fri, 14 Jul 2000 17:16:07 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA14512;
	Fri, 14 Jul 2000 15:15:26 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA08658;
	Fri, 14 Jul 2000 14:14:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6ELDfs06445
	for ngtrans-dist; Fri, 14 Jul 2000 14:13:41 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6ELDW606438
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 14:13:32 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA17121
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 14:13:33 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA13273
	for <ngtrans@sunroof.eng.sun.com>; Fri, 14 Jul 2000 15:13:32 -0600 (MDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id RAA00916;
        Fri, 14 Jul 2000 17:13:31 -0400 (EDT)
Message-Id: <200007142113.RAA00916@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
X-PGP-Key: 2F07A741 ; 78 15 8E 8B C0 06 5D D1  BC 08 05 7F 42 81 7E 90 
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) 6to4 and DNS
cc: moore@cs.utk.edu
From: Keith Moore <moore@cs.utk.edu>
Date: Fri, 14 Jul 2000 17:13:31 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

I've just submitted an internet-draft outlining possible solutions
to the problem of providing DNS reverse lookups to 6to4 addresses.
it's called draft-moore-6to4-dns-00.txt; until it comes out in
the repositories (probably a few days) you can find it at

http://www.cs.utk.edu/~moore/draft-moore-6to4-dns-00.txt

-Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 17 18:05:46 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10142
	for <ngtrans-archive@odin.ietf.org>; Mon, 17 Jul 2000 18:05:45 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA05609;
	Mon, 17 Jul 2000 16:05:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA00380;
	Mon, 17 Jul 2000 14:12:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6HLAbg07933
	for ngtrans-dist; Mon, 17 Jul 2000 14:10:37 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6HLAT607926
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:10:29 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA10179
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:10:26 -0700 (PDT)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id OAA05872
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:10:23 -0700 (PDT)
Received: from truckee.wins.lbl.gov (Truckee.lbl.gov) [128.3.9.224] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 13EI9d-0006DU-00; Mon, 17 Jul 2000 14:10:21 -0700
Message-Id: <4.3.1.2.20000717133950.029b9348@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Mon, 17 Jul 2000 14:10:14 -0700
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) W.G. Last Call on IPv6 Tunnel Broker" - closes July 31, 2000
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>,
        Guardini Ivano <Ivano.Guardini@CSELT.IT>,
        Fasano Paolo <Paolo.Fasano@CSELT.IT>, Randy Bush <randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>

This is an ngtrans working group last call for comments on advancing the
IPv6 Tunnel Broker document as Informational RFC:

	Title		: IPv6 Tunnel Broker
	Author(s)	: A. Durand, P. Fasano, I. Guardini, D. Lento
	Filename	: draft-ietf-ngtrans-broker-03.txt
	Pages		: 10
	Date		: 07-Jul-00

<http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-broker-03.txt>

Please send substantive comments to the ngtrans mailing list, and minor
editorial comments to the authors.  This last call period will end two
week from today on July 31, 2000.

Bob Fink/ Alain Durand / Tony Hain



===changes from the BROKER-02 version
section 1:
   - clarified that the draft is a framework document
   - highlighted that the TB approach allows IPv6 ISPs to easily perform
     access control on the users

section 2.3:
   - explained that a security association should exist between TB and
     client to prevent unauthorized use of the service

section 2.6:
   - clarified that the definition of a specific set of protocols to be
     used for the communication among the Tunnel Broker entities is outside
     of the scope of the document
   - added the MIME-based approach among the other communication options

section 4: New section on the possibility to use the Tunnel Broker concept
in other areas

section 5: various improvements in the security considerations

-end



From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 17 19:39:48 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21440
	for <ngtrans-archive@odin.ietf.org>; Mon, 17 Jul 2000 19:39:48 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA04540;
	Mon, 17 Jul 2000 17:38:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA01410;
	Mon, 17 Jul 2000 14:16:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6HLFCG07955
	for ngtrans-dist; Mon, 17 Jul 2000 14:15:12 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6HLF5607948
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:15:06 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id OAA26475
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:15:06 -0700 (PDT)
Received: from zmamail04.zma.compaq.com (zmamail04.zma.compaq.com [161.114.64.104])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA09168
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 14:15:05 -0700 (PDT)
Received: by zmamail04.zma.compaq.com (Postfix, from userid 12345)
	id 8F03F245; Mon, 17 Jul 2000 17:15:03 -0400 (EDT)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail04.zma.compaq.com (Postfix) with ESMTP id 56CE6164
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jul 2000 17:15:03 -0400 (EDT)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id RAA0001043746; Mon, 17 Jul 2000 17:14:50 -0400 (EDT)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200007172114.RAA0001043746@anw.zk3.dec.com>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) Updated draft-ietf-ngtrans-dstm-02.txt
Date: Mon, 17 Jul 2000 17:14:50 -0400
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Folks,

We sent this into IETF ID folks last Thursday a.m.  So it should be out
soon.  But you can see it now at:

ftp://206.152.163.3/pub/draft-ietf-ngtrans-dstm-02.txt

Changes from draft 01 to draft 02

   1.  Added futher clarifications to DSTM components.

   2.  Added client/server details for DHCPv6 ngtrans extension.

   3.  Removed optional scenarios to simplify this mechanism.

   4.  Removed AIIH concepts and changed to be DSTM components.

   5.  Add Applicability Statement

   6.  Added acknowledgment section and new coauthors Francis Dupont
       and Alain Durand.

regards,
/jim


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 18 06:38:13 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14950
	for <ngtrans-archive@odin.ietf.org>; Tue, 18 Jul 2000 06:38:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA05485;
	Tue, 18 Jul 2000 04:37:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA13707;
	Tue, 18 Jul 2000 03:37:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6IAZsx08490
	for ngtrans-dist; Tue, 18 Jul 2000 03:35:54 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6IAZi608483
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Jul 2000 03:35:44 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA07239
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Jul 2000 03:35:43 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA09808
	for <ngtrans@sunroof.eng.sun.com>; Tue, 18 Jul 2000 03:35:42 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13799;
	Tue, 18 Jul 2000 06:35:41 -0400 (EDT)
Message-Id: <200007181035.GAA13799@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-socks-gateway-05.txt
Date: Tue, 18 Jul 2000 06:35:41 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: A SOCKS-based IPv6/IPv4 Gateway Mechanism
	Author(s)	: H. Kitamura
	Filename	: draft-ietf-ngtrans-socks-gateway-05.txt
	Pages		: 10
	Date		: 17-Jul-00
	
This document describes a SOCKS-based IPv6/IPv4 gateway mechanism
that enables smooth heterogeneous communications between the IPv6
nodes and IPv4 nodes.
It is based on the SOCKS protocol [SOCKSv5]. By applying the SOCKS
mechanism to the heterogeneous communications and relaying two
'terminated' IPv4 and IPv6 connections at the 'application layer'
(the SOCKS server), the SOCKS-based IPv6/IPv4 gateway mechanism is
accomplished.
Since it is accomplished without introducing new protocols, it
provides the same communication environment that is provided by the
SOCKS mechanism. The same appearance is provided to the heterogeneous
communications. No conveniences or functionalities of current
communications are sacrificed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-socks-gateway-05.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-socks-gateway-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-socks-gateway-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000717150003.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-socks-gateway-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-socks-gateway-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000717150003.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 20 06:51:07 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14453
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jul 2000 06:51:07 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA02227;
	Thu, 20 Jul 2000 04:50:44 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA11696;
	Thu, 20 Jul 2000 03:49:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6KAl2O10378
	for ngtrans-dist; Thu, 20 Jul 2000 03:47:02 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6KAkn610370
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 03:46:50 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA16840
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 03:46:48 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA00845
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 04:46:47 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11950;
	Thu, 20 Jul 2000 06:46:45 -0400 (EDT)
Message-Id: <200007201046.GAA11950@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-6bone-registry-03.txt
Date: Thu, 20 Jul 2000 06:46:45 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: The 6bone registry
	Author(s)	: D. Kessens
	Filename	: draft-ietf-ngtrans-6bone-registry-03.txt
	Pages		: 13
	Date		: 19-Jul-00
	
This proposal describes the proposed syntax of a new RIPE database object that describes the several IPv6 sites in the world. The object and resulting database collection will be used to facilitate the introduction of IPv6 in the Internet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6bone-registry-03.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-6bone-registry-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-6bone-registry-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000719141522.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-6bone-registry-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-6bone-registry-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000719141522.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 20 06:51:11 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14489
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jul 2000 06:51:11 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA02248;
	Thu, 20 Jul 2000 04:50:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA16995;
	Thu, 20 Jul 2000 03:49:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6KAkva10377
	for ngtrans-dist; Thu, 20 Jul 2000 03:46:57 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6KAki610362
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 03:46:45 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA11548
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 03:46:42 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA00825
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 04:46:42 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11910;
	Thu, 20 Jul 2000 06:46:41 -0400 (EDT)
Message-Id: <200007201046.GAA11910@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt
Date: Thu, 20 Jul 2000 06:46:41 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: On overview of the Introduction of IPv6 in the        
                          Internet
	Author(s)	: W. Biemolt, M. Kaat, T. Larder, H. Steenman, 
                          R. van der Pol, G. Tsirtsis, Y. Sekiya,
                          A. Durand, K. Yamamoto
	Filename      draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt
 	Pages		: 36
	Date		: 19-Jul-00
	
This document is a guide to the introduction of IPv6 in the IPv4 
based Internet or Intranets.  Several general issues to start IPv6 
networking in a predominantly IPv4 world are discussed, such as IPv6
addresses, IPv6 DNS and routing issues.  Short descriptions are given
of the different translation and migration tools and mechanisms that
translate between IPv6 and IPv4 and/or tunnel IPv6 over IPv4.  The 
remainder of this document describes how IPv6 can be introduced in 
various environments, such as ISPs, Internet Exchanges and end user 
environments.  Suggestions are given on the use of the different 
translation and migration tools in each environment.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000719141513.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000719141513.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 20 15:02:23 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00731
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jul 2000 15:02:22 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA07977;
	Thu, 20 Jul 2000 13:00:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA13799;
	Thu, 20 Jul 2000 11:35:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6KIYNh10670
	for ngtrans-dist; Thu, 20 Jul 2000 11:34:23 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6KIYJ610663
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 11:34:19 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA02225
	for ngtrans@sunroof.eng.sun.com; Thu, 20 Jul 2000 11:32:40 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6KIU2610651
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 11:30:03 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA03667
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 11:30:00 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA14654
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 12:29:39 -0600 (MDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id LAA12459
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 11:29:30 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <3977450A.9F8856DD@aciri.org>
Date: Thu, 20 Jul 2000 11:29:30 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) questions about 6to4
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit


I'm having a hard time understanding the notion of the "6to4 exterior
routing domain" in the 6to4 document.  In particular, I don't see why
you need it.  Considering that misconfiguration in this area can result
in routing loops, it seems it would be useful to get rid of it if that
is possible.


The thing I can't understand is why a 6to4 router, once it has a path to
a relay, would not simply adopt a native IPv6 prefix from the same
prefix that the relay uses.  It seems to me that once a 6to4 router has
gone through the process of configuration required to know how to reach
a relay (some configured tunnel, for instance), it is for all practical
purposes "directly" connected to the IPv6 world.  Having achieved this
connectivity, why wouldn't it just get an IPv6 native prefix and become
a "full" member of the IPv6 world?  If this were required for all 6to4
routers that had relay connectivity, then you could get rid of the 6to4
exterior routing domain altogether, simplify the 6to4 transition
scenario, and get rid of this nasty routing loop.


Speaking of the routing loop, the 6to4 spec makes it sound like the loop
can come about from the result of a single misconfigured 6to4 router
(i.e., misconfigured to leak 2002::/16 into the 6to4 exterior).  But
presumably the relays are also configured to only accept 2002::/16
routes from other relays.  So the loop would require misconfiguration on
the part of at 2 boxes, not just one.  (If this is not the case, then
you have a serious DoS problem.)  In other words, the loop that can come
from this misconfiguration is no different than the loop (or black hole)
that would result from a standard IPv4 BGP router advertising an IPv4
prefix that it in fact cannot reach.  The defense against this is simply
careful configuration of BGP peers and the prefixes they can validly
advertise...


Finally, one other question just to make sure I understand something
right.  Section 5.2 says that poor route filtering policy for 
advertised by relays into native IPv6 routing can result in potential
unreachability.  Is this simply because a prefix advertised too far will
result in a lot of traffic directed to the prefix resulting in
unreachability due to congestion (as opposed to some actual routing
black hole)?  Also, is this filtering any different qualitatively from
the filtering one might do within IPv4 today to spread traffic to a give
IPv4 prefix among a number of routers that have connectivity to that
prefix in order not to overload any one of them with traffic?

Thanks,

PF



From owner-ngtrans@sunroof.eng.sun.com  Thu Jul 20 18:35:23 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14747
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jul 2000 18:35:22 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA15092;
	Thu, 20 Jul 2000 16:34:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA17824;
	Thu, 20 Jul 2000 15:34:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6KMWWm10839
	for ngtrans-dist; Thu, 20 Jul 2000 15:32:32 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6KMWP610832
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 15:32:25 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id PAA03700
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 15:32:25 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA05432
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jul 2000 15:32:23 -0700 (PDT)
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 XAA47798; Thu, 20 Jul 2000 23:31:49 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id XAA06598; Thu, 20 Jul 2000 23:32:18 +0100 (BST)
Message-ID: <39777D6F.5998AE04@hursley.ibm.com>
Date: Thu, 20 Jul 2000 17:30:07 -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: Paul Francis <francis@aciri.org>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4
References: <3977450A.9F8856DD@aciri.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Hi Paul,

Paul Francis wrote:
> 
> I'm having a hard time understanding the notion of the "6to4 exterior
> routing domain" in the 6to4 document.  In particular, I don't see why
> you need it.  Considering that misconfiguration in this area can result
> in routing loops, it seems it would be useful to get rid of it if that
> is possible.

The reason is that it allows you to exploit the power of BGP4+ policy
to engineer the traffic paths and regions of reachability. If you don't
want to do that, you don't use BGP4+ and the exterior routing domain
is pretty much a no-op.

> 
> The thing I can't understand is why a 6to4 router, once it has a path to
> a relay, would not simply adopt a native IPv6 prefix from the same
> prefix that the relay uses.  

Then it would effectively be using a configured tunnel to talk to the
relay, rather than using the implicit tunnel created by the 6to4
address mapping. 

> It seems to me that once a 6to4 router has
> gone through the process of configuration required to know how to reach
> a relay (some configured tunnel, for instance), it is for all practical
> purposes "directly" connected to the IPv6 world.  Having achieved this
> connectivity, why wouldn't it just get an IPv6 native prefix and become
> a "full" member of the IPv6 world?  If this were required for all 6to4
> routers that had relay connectivity, then you could get rid of the 6to4
> exterior routing domain altogether, simplify the 6to4 transition
> scenario, and get rid of this nasty routing loop.

I'm not convinced it works in all cases. Being in a hotel room without
a whiteboard, I can't do the analysis. Certainly, there is a degenerate
mode of 6to4 where *all* you get from it is a free IPv6 prefix without
asking a registry, and everything else is bog standard. But I think this
requires manual configuration, whereas the original 6to4 model should
be essentially plug and play.
> 
> Speaking of the routing loop, the 6to4 spec makes it sound like the loop
> can come about from the result of a single misconfigured 6to4 router
> (i.e., misconfigured to leak 2002::/16 into the 6to4 exterior).  But
> presumably the relays are also configured to only accept 2002::/16
> routes from other relays.  So the loop would require misconfiguration on
> the part of at 2 boxes, not just one.  (If this is not the case, then
> you have a serious DoS problem.)  In other words, the loop that can come
> from this misconfiguration is no different than the loop (or black hole)
> that would result from a standard IPv4 BGP router advertising an IPv4
> prefix that it in fact cannot reach.  The defense against this is simply
> careful configuration of BGP peers and the prefixes they can validly
> advertise...

I think I agree. But I was asked to provide a description of potential
routing loops by our respected AD, so I did ;-)
> 
> Finally, one other question just to make sure I understand something
> right.  Section 5.2 says that poor route filtering policy for
> advertised by relays into native IPv6 routing can result in potential
> unreachability.  Is this simply because a prefix advertised too far will
> result in a lot of traffic directed to the prefix resulting in
> unreachability due to congestion (as opposed to some actual routing
> black hole)?  

No, I think that if you screw up the BGP4+ policy you can have
genuine unreachability. This was hard to illustrate in ASCII art
but I did some PowerPoint pictures once that seemed fairly convincing.

> Also, is this filtering any different qualitatively from
> the filtering one might do within IPv4 today to spread traffic to a give
> IPv4 prefix among a number of routers that have connectivity to that
> prefix in order not to overload any one of them with traffic?

...or to implement ISP peering and transit agreements and the lack thereof.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 09:42:43 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13067
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 09:42:42 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA10582;
	Fri, 21 Jul 2000 07:42:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA12351;
	Fri, 21 Jul 2000 06:42:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LDf1911566
	for ngtrans-dist; Fri, 21 Jul 2000 06:41:01 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LDer611559
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 06:40:53 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id GAA04244
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 06:40:52 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA15110
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 06:40:52 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12898;
	Fri, 21 Jul 2000 09:40:49 -0400 (EDT)
Message-Id: <200007211340.JAA12898@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-dstm-02.txt
Date: Fri, 21 Jul 2000 09:40:48 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Internet-Drafts@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Next Generation Transition Working Group of the IETF.

	Title		: Dual Stack Transition Mechanism (DSTM)
	Author(s)	: J. Bound, L. Toutain, H. Afifi, F. Dupont, A. Durand
	Filename	: draft-ietf-ngtrans-dstm-02.txt
	Pages		: 19
	Date		: 20-Jul-00
	
The initial deployment of IPv6 will require a tightly coupled use of
IPv4 addresses to support the interoperation of IPv6 and IPv4, within
an IPv6 Network.  Nodes will be able to be deployed with IPv6
addresses, but will still need to communicate with IPv4 nodes that do
not have a dual IP layer supporting both IPv4 and IPv6.  The Dual
Stack Transition Method (DSTM) provides a set of mechanisms to assign
temporary Global IPv4 Addresses to IPv6 nodes, use of dynamic tunnels
within an IPv6 Network to carry IPv4 traffic, and a defined set of
processes and architecture for the supporting infrastructure required
for this transition mechanism.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-dstm-02.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-ngtrans-dstm-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-ngtrans-dstm-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000720142001.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-dstm-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ngtrans-dstm-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000720142001.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 13:40:53 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02926
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 13:40:52 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA05903;
	Fri, 21 Jul 2000 11:39:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA09505;
	Fri, 21 Jul 2000 10:38:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LHbEg11876
	for ngtrans-dist; Fri, 21 Jul 2000 10:37:14 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LHbA611869
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 10:37:10 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id KAA08292
	for ngtrans@sunroof.eng.sun.com; Fri, 21 Jul 2000 10:35:32 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LFnV611713
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 08:49:31 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id IAA01197
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 08:49:30 -0700 (PDT)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04317
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 08:49:29 -0700 (PDT)
Received: from vaio ([63.204.196.3])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FY2005HO0LCSL@mta5.snfc21.pbi.net> for
 ngtrans@sunroof.eng.sun.com; Fri, 21 Jul 2000 08:34:25 -0700 (PDT)
Date: Fri, 21 Jul 2000 08:34:47 -0700
From: Paul Francis <francis@aciri.org>
Subject: RE: (ngtrans) questions about 6to4
In-reply-to: <39777D6F.5998AE04@hursley.ibm.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: ngtrans@sunroof.eng.sun.com
Message-id: <020e01bff329$33d3f200$03c4cc3f@pacbell.net>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Priority: 3 (Normal)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit


>
> Then it would effectively be using a configured tunnel to talk to the
> relay, rather than using the implicit tunnel created by the 6to4
> address mapping.

I don't see how a 6to4 router can talk to a relay without *some* kind of
explicit configuration...either a tunnel, a direct link to the relay, or a
direct link to a router that is in this 6to4 exterior routing domain.

>
> I'm not convinced it works in all cases. Being in a hotel room without
> a whiteboard, I can't do the analysis. Certainly, there is a degenerate
> mode of 6to4 where *all* you get from it is a free IPv6 prefix without
> asking a registry, and everything else is bog standard. But I think this

bog?

> requires manual configuration, whereas the original 6to4 model should
> be essentially plug and play.

But this is just my point...I don't see how you can avoid some manual
configuration (if you want to be able to exchange packets with hosts with
native IPv6 prefixes).  Let me go back over my understanding:

Basic 6to4 consists of a 6to4 router with an interface to the IPv4 backbone.
This allows the 6to4 router to forward packets to all other 6to4 routers
with no configuration, because it can pull the forwarding IPv4 address out
of the IPv6 address.  So far so good.

The problem is that the 6to4 router does not know how to forward packets to
routers with native IPv6 addresses *without some additional connectivity or
configuration information*.  Specifically, it has to know how to forward a
packet with a native IPv6 address to some relay.  One way is for it to know
the 6to4 address of the relay's IPv4 interface, which amounts to a
configured tunnel (right?).  Another way is to have another (non-6to4)
interface to connects directly to a relay or to a router in the 6to4
exterior routing domain.  But this is also a form of manual configuration.

So you seem to need some kind of manual configuration.  Assuming this is
right, and getting back to my original point, once you've done this
configuration, why not just get a native IPv6 prefix from the relay?


>
> I think I agree. But I was asked to provide a description of potential
> routing loops by our respected AD, so I did ;-)

Well, you really need to make the document more clear then.  As it reads
now, it sounds like the routing loop is trivial for a single 6to4 router to
create, and therefore an obvious DoS attack.


>
> No, I think that if you screw up the BGP4+ policy you can have
> genuine unreachability. This was hard to illustrate in ASCII art
> but I did some PowerPoint pictures once that seemed fairly convincing.

Again, is this somehow different from screwing up any BGP4 policy (say, in a
pure native IPv6 environment), or is there something special about the mixed
6to4/native environment?

You need to make all this more clear in the document.  As it now reads, it
gives the impression that qualitatively new routing failure modes are
introduced by 6to4.  But I can't see what those new failure modes are, which
leads me to believe that there are none...just the usual failure modes that
come from mis-configured routing.  But I'm still not sure one way or the
other!

PF




From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 14:17:29 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29176
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 14:17:28 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA03655;
	Fri, 21 Jul 2000 12:15:51 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA18534;
	Fri, 21 Jul 2000 11:11:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LI9pI11925
	for ngtrans-dist; Fri, 21 Jul 2000 11:09:51 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LI9d611918
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 11:09:39 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA09595
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 11:09:38 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA08737
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 11:09:37 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id OAA16147;
        Fri, 21 Jul 2000 14:09:32 -0400 (EDT)
Message-Id: <200007211809.OAA16147@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Francis <francis@aciri.org>
cc: Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4 
In-reply-to: Your message of "Fri, 21 Jul 2000 08:34:47 PDT."
             <020e01bff329$33d3f200$03c4cc3f@pacbell.net> 
Date: Fri, 21 Jul 2000 14:09:32 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> So you seem to need some kind of manual configuration.  Assuming this is
> right, and getting back to my original point, once you've done this
> configuration, why not just get a native IPv6 prefix from the relay?

a) we're working on tools for automatic relay discovery, they're just
   not part of the core 6to4 proposal.  but we don't want to preclude
   such tools from existing.

b) getting a native v6 prefix from the relay would presume that the
   6to4 site is always using the same relay.  we'd like to avoid
   this for a variety of reasons.  e.g. at least at first, a relay 
   might well be fairly distant from many of the leaf networks that 
   it serves.  later on, relays might be more common, so it might be
   possible to find a closer one.  since addresses need to be somewhat 
   stable, the use of a prefix borrowed from the relay would discourage
   the creation of more relays (not as much benefit to be derived)
   and encourage the establishment of permanent long tunnels.

   in effect, always getting a native prefix from a relay would defeat 
   topological address assignment.

c) when using 6to4 addresses, traffic between 6to4 sites flows more-or-less
   'optimally' or at least, according to the ISPs routing policies for v4 
   packets.  6to4 is so easy to deploy that we can expect this case to be 
   fairly common.  traffic between 6to4 sites and native sites flows 
   suboptimally if the relays aren't close to the 6to4 sites.  but 
   we're working on ways to help 6to4 sites find relays that are close.

   however, if all sites were to use native prefixes, traffic would
   flow suboptimally in almost all cases, because either the relay
   used by a site would have to be "close' to that site (effectively 
   requiring sites' ISPs to implement native v6 before they use it - 
   the very hurdle we are trying to avoid), or the relays would use 
   long tunnels.  

Keith


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 15:35:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13723
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 15:35:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA29310;
	Fri, 21 Jul 2000 13:34:31 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA13430;
	Fri, 21 Jul 2000 12:34:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LJX3W12055
	for ngtrans-dist; Fri, 21 Jul 2000 12:33:03 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LJWu612048
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 12:32:56 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA12880
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 12:32:55 -0700 (PDT)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id MAA28229
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 12:32:54 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 21 Jul 2000 12:03:50 -0700 (Pacific Daylight Time)
Received: from speak.platinum.corp.microsoft.com ([172.30.236.197]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Fri, 21 Jul 2000 12:09:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4408.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: (ngtrans) questions about 6to4
Date: Fri, 21 Jul 2000 12:09:20 -0700
Message-ID: <CC2E64D4B3BAB646A87B5A3AE97090420B8DBC1A@speak.platinum.corp.microsoft.com>
Thread-Topic: (ngtrans) questions about 6to4
Thread-Index: Ab/zOtUeEfNak1+yTyyoRmjjsnyXYgAAlFeg
From: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
To: "Paul Francis" <francis@aciri.org>,
        "Brian E Carpenter" <brian@hursley.ibm.com>
Cc: <ngtrans@sunroof.eng.sun.com>
X-OriginalArrivalTime: 21 Jul 2000 19:09:21.0827 (UTC) FILETIME=[2D527730:01BFF347]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e6LJWv612049
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Tony Hain" <tonyhain@Exchange.Microsoft.com>
Content-Transfer-Encoding: 8bit


> -----Original Message-----
> From: Paul Francis [mailto:francis@aciri.org]
> Sent: Friday, July 21, 2000 8:35 AM
> To: Brian E Carpenter
> Cc: ngtrans@sunroof.eng.sun.com
> Subject: RE: (ngtrans) questions about 6to4
> 
> >
> > Then it would effectively be using a configured tunnel to 
> talk to the
> > relay, rather than using the implicit tunnel created by the 6to4
> > address mapping.
> 
> I don't see how a 6to4 router can talk to a relay without 
> *some* kind of
> explicit configuration...either a tunnel, a direct link to 
> the relay, or a
> direct link to a router that is in this 6to4 exterior routing domain.
> 

Whenever it finally pops out look at
http://www.ietf.org/internet-drafts/draft-hain-6to4-scaling-00.txt


> >
> > I'm not convinced it works in all cases. Being in a hotel 
> room without
> > a whiteboard, I can't do the analysis. Certainly, there is 
> a degenerate
> > mode of 6to4 where *all* you get from it is a free IPv6 
> prefix without
> > asking a registry, and everything else is bog standard. But 
> I think this
> 
> bog?
> 
> > requires manual configuration, whereas the original 6to4 
> model should
> > be essentially plug and play.
> 
> But this is just my point...I don't see how you can avoid some manual
> configuration (if you want to be able to exchange packets 
> with hosts with
> native IPv6 prefixes).  Let me go back over my understanding:
> 
> Basic 6to4 consists of a 6to4 router with an interface to the 
> IPv4 backbone.
> This allows the 6to4 router to forward packets to all other 
> 6to4 routers
> with no configuration, because it can pull the forwarding 
> IPv4 address out
> of the IPv6 address.  So far so good.
> 
> The problem is that the 6to4 router does not know how to 
> forward packets to
> routers with native IPv6 addresses *without some additional 
> connectivity or
> configuration information*.  Specifically, it has to know how 
> to forward a
> packet with a native IPv6 address to some relay.  One way is 
> for it to know
> the 6to4 address of the relay's IPv4 interface, which amounts to a
> configured tunnel (right?).  Another way is to have another (non-6to4)
> interface to connects directly to a relay or to a router in the 6to4
> exterior routing domain.  But this is also a form of manual 
> configuration.
> 
> So you seem to need some kind of manual configuration.  
> Assuming this is
> right, and getting back to my original point, once you've done this
> configuration, why not just get a native IPv6 prefix from the relay?
> 
> 

This is another artifact of the point I will be talking about in
Pittsburgh; The IPv4 Internet is simply an NBMA link from the
perspective of 6to4 nodes. Given that it is a link, all that is needed
is an ARP mechanism (manual config is one solution to that) to find
other nodes.  The basic premise of 6to4 is that on-link ARP is built-in,
so the only problem is finding the routers (relays) that attach to the
off-link (native) networks. Once the routers are known, all
non-multicast link-layer functions MUST be applicable (including
redirect). This points out a basic problem with 2461 in that it assumes
a node will always want a single default route to get off-link, and that
the media is always multicast capable. Neither of those is true for a
6to4 connected site router.


> >
> > I think I agree. But I was asked to provide a description 
> of potential
> > routing loops by our respected AD, so I did ;-)
> 
> Well, you really need to make the document more clear then.  
> As it reads
> now, it sounds like the routing loop is trivial for a single 
> 6to4 router to
> create, and therefore an obvious DoS attack.
> 
> 

The failing assumption is that all the 6to4 routers are participating in
a common routing conversation. What is more likely is that they will
participate in a local routing domain, and be configured for external
routes. Despite the discussion in 5.2-2.2, is it really likely that the
ISP community will want-to/allow/be-capable-of enabling all site 6to4
routers as BGP  participants? A few multi-homed ones maybe, but that is
no different than today. My proposal addresses this and suggests that a
few well-known relays participate in that BGP, and redirect the masses
of 6to4 routers. Tunnel brokers also work for finding an initial
default, but they break down if the native IPv6 networks are
partitioned. 


> >
> > No, I think that if you screw up the BGP4+ policy you can have
> > genuine unreachability. This was hard to illustrate in ASCII art
> > but I did some PowerPoint pictures once that seemed fairly 
> convincing.
> 
> Again, is this somehow different from screwing up any BGP4 
> policy (say, in a
> pure native IPv6 environment), or is there something special 
> about the mixed
> 6to4/native environment?
> 
> You need to make all this more clear in the document.  As it 
> now reads, it
> gives the impression that qualitatively new routing failure modes are
> introduced by 6to4.  But I can't see what those new failure 
> modes are, which
> leads me to believe that there are none...just the usual 
> failure modes that
> come from mis-configured routing.  But I'm still not sure one 
> way or the
> other!
> 
> PF
> 
> 

There is no attempt to mix the environments so there shouldn't be any
new failure modes. There may be a high number of players newly exposed
to the known failures though, which I assumed to be the reason for
discussing it here. It might work better to use a pointer to any
existing documentation on BGP failure modes and defense mechanisms, than
to try and summarize it here.

Tony


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 19:19:33 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19672
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 19:19:32 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA23197;
	Fri, 21 Jul 2000 17:19:10 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA07944;
	Fri, 21 Jul 2000 16:18:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LNHdF12459
	for ngtrans-dist; Fri, 21 Jul 2000 16:17:39 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LNHX612452
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:17:33 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA27437
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:17:32 -0700 (PDT)
Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id RAA22440
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:17:32 -0600 (MDT)
Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 21 Jul 2000 16:15:43 -0700 (Pacific Daylight Time)
Received: by INET-IMC-04 with Internet Mail Service (5.5.2651.58)
	id <PGAHSAD1>; Fri, 21 Jul 2000 16:15:43 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF01101D@red-msg-24.redmond.corp.microsoft.com>
From: Brian Zill <bzill@microsoft.com>
To: "'Paul Francis'" <francis@aciri.org>,
        Brian E Carpenter
	 <brian@hursley.ibm.com>
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) questions about 6to4
Date: Fri, 21 Jul 2000 16:15:36 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian Zill <bzill@microsoft.com>

Hi Paul,

> why not just get a native IPv6 prefix from the relay?

You're assuming you want one :-)  As Keith points out, using 6to4 results in
much more efficient use of the underlying IPv4 network when compared to the
network of configured tunnels that comprise most of 6bone today.  Until you
have native IPv6 end-to-end, you're likely to get better performance out of
6to4.

Imagine for a moment that we convince everybody (or mostly everybody) to get
6to4 addresses, regardless of whether or not they also have a native
address.  Put both addresses in the DNS and the source/destination address
selection rules will cause native connectivity to be used if it is present
at both ends, 6to4 otherwise.  Now there is no issue of finding/scaling 6to4
relays since everyone is reachable via 6to4.  We could still put up a couple
6to4 relays to handle the few folks who absolutely can't get a 6to4 prefix
for some reason, but there shouldn't be any scaling issues and finding one
is easy when we only have a small number of addresses to distribute - just
put a well-known name into the DNS that maps to them.

This is a great transition scenario.  Everyone who has at least one IPv4
address automatically has a huge amount of globally routable IPv6 address
space.  And 6to4 is trivial to set up.  No waiting on the registries.  No
worries about getting your ISP to carry IPv6 natively, you can operate just
fine while waiting for them to get with the program.  And as folks get IPv6
pipes put into place, they will get used automatically.  Bottom line: it's
more efficient than today's 6bone tunnel scheme and with almost zero
configuration hassles.

> One way is for it to know the 6to4 address of the
> relay's IPv4 interface, which amounts to a configured
> tunnel (right?).

Just a terminology nit, this isn't a configured tunnel.  It's more akin to
the automatic tunneling that is done for v4-compatible addresses.

--Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 19:40:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27149
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 19:40:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA03506;
	Fri, 21 Jul 2000 17:39:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA09062;
	Fri, 21 Jul 2000 16:39:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6LNbMu12492
	for ngtrans-dist; Fri, 21 Jul 2000 16:37:22 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LNbG612485
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:37:16 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA12227
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:37:15 -0700 (PDT)
Received: from popcorn.cisco.com (popcorn.cisco.com [171.69.18.32])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA02130
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:37:15 -0600 (MDT)
Received: from [171.70.84.50] (deering-office-mac.cisco.com [171.70.84.50])
	by popcorn.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.8.8) with ESMTP id QAA02857;
	Fri, 21 Jul 2000 16:36:20 -0700 (PDT)
Mime-Version: 1.0
X-Sender: deering@ups
Message-Id: <p04320401b59e8dfbe107@[171.70.84.50]>
In-Reply-To: 
 <2E3FA0558747934A8F753CC533A3F6DF01101D@red-msg-24.redmond.corp.microsoft.
 com>
References: 
 <2E3FA0558747934A8F753CC533A3F6DF01101D@red-msg-24.redmond.corp.microsoft.
 com>
Date: Fri, 21 Jul 2000 16:37:03 -0700
To: Brian Zill <bzill@microsoft.com>
From: Steve Deering <deering@cisco.com>
Subject: RE: (ngtrans) questions about 6to4
Cc: "'Paul Francis'" <francis@aciri.org>,
        Brian E Carpenter	 <brian@hursley.ibm.com>,
        ngtrans@sunroof.eng.sun.com
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 4:15 PM -0700 7/21/00, Brian Zill wrote:
>This is a great transition scenario.  Everyone who has at least one IPv4
>address automatically has a huge amount of globally routable IPv6 address
>space.

Not to disagree, but just to observe that there are many Internet
subscribers who do not have even one globally-unique IPv4 address --
they only get temporary use of one from a shared pool when they
"login to the Internet".

Steve


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 20:29:56 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11778
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 20:29:55 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA25433;
	Fri, 21 Jul 2000 18:29:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA11797;
	Fri, 21 Jul 2000 17:29:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M0S5W12568
	for ngtrans-dist; Fri, 21 Jul 2000 17:28:05 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M0Ru612561
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:27:57 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA10250
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:27:56 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA24505
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:27:55 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id UAA22616;
        Fri, 21 Jul 2000 20:27:47 -0400 (EDT)
Message-Id: <200007220027.UAA22616@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Steve Deering <deering@cisco.com>
cc: Brian Zill <bzill@microsoft.com>, "'Paul Francis'" <francis@aciri.org>,
        Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4 
In-reply-to: Your message of "Fri, 21 Jul 2000 16:37:03 PDT."
             <p04320401b59e8dfbe107@[171.70.84.50]> 
Date: Fri, 21 Jul 2000 20:27:47 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> >This is a great transition scenario.  Everyone who has at least one IPv4
> >address automatically has a huge amount of globally routable IPv6 address
> >space.
> 
> Not to disagree, but just to observe that there are many Internet
> subscribers who do not have even one globally-unique IPv4 address --
> they only get temporary use of one from a shared pool when they
> "login to the Internet".

right...though the addresses usually are globally-scoped, they're
just temporary.  those folks for whom temporary addresses are "good 
enough" can presumably run 6to4 over a dialup line and get temporary
IPv6 addresses.  

this would still be good enough, for instance, to allow my laptop 
to communicate over IPv6 (and reach IPv6-only hosts) when I'm on travel.  

Keith


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 20:37:36 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14191
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 20:37:36 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA28454;
	Fri, 21 Jul 2000 18:37:15 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA13107;
	Fri, 21 Jul 2000 17:36:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M0aDJ12587
	for ngtrans-dist; Fri, 21 Jul 2000 17:36:13 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M0a6612580
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:36:06 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id RAA23620
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:36:05 -0700 (PDT)
Received: from mail1.microsoft.com (mail1.microsoft.com [131.107.3.125])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id SAA28024
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:36:05 -0600 (MDT)
Received: from 157.54.9.101 by mail1.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 21 Jul 2000 17:35:38 -0700 (Pacific Daylight Time)
Received: by INET-IMC-01 with Internet Mail Service (5.5.2651.58)
	id <PGA2K3JX>; Fri, 21 Jul 2000 17:35:38 -0700
Message-ID: <2E3FA0558747934A8F753CC533A3F6DF011020@red-msg-24.redmond.corp.microsoft.com>
From: Brian Zill <bzill@microsoft.com>
To: "'Paul Francis'" <francis@aciri.org>
Cc: Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) questions about 6to4
Date: Fri, 21 Jul 2000 17:34:48 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian Zill <bzill@microsoft.com>

Hi Paul,

> > You're assuming you want one :-)
> 
> Please believe me, I was never assuming such a thing!

I was just joking.

> I had merely observed that native IPv6 addresses is
> the end-goal for IPv6, and so wondered why one wouldn't
> want to move towards that goal a bit quicker given the
> opportunity.

Yes, it was a good question.  But, more specifically, I think the goal is
getting everyone _connected_ natively.  Using "native" addresses over
configured tunnels isn't preferable to using "6to4" addresses over 6to4
automatic tunnels.  And note, you can route 6to4 addresses in native
v6-space as well as dropping them down to v4.  The use of "native" when used
with addresses means something different than the use of "native" when used
with transmission media.

> So, why would anybody ever move to native IPv6 addresses
> once they are happily using 6to4?

To save encapsulation overhead.  Both on the wire, and it terms of
processing power at the en/de/capsulation point.

> More to the point, why would an ISP ever start offering
> IPv6 services if all of their customers are happily
> tunneling their IPv6 over IPv4?

To recover the "wasted" bandwidth of the encapsulation overhead.  ISP's will
realize that their customer's only care about the IPv6 data going through,
so if they can carry IPv6 natively, they "get back" the amount of bandwidth
being used on IPv4 encapsulation.

There are also all the other good points about IPv6 that we've beaten to
death: ease of configuration, routing aggregation, etc. etc.

I suspect that a moderate amount of 6to4 use will be enough to demonstrate
to the ISPs that there is customer demand for IPv6.  And then they'll start
offering it natively.

--Brian


From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 21:51:26 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07965
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 21:51:26 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA20900;
	Fri, 21 Jul 2000 19:51:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA28704;
	Fri, 21 Jul 2000 18:50:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M1n4e12724
	for ngtrans-dist; Fri, 21 Jul 2000 18:49:04 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M1mw612717
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:48:58 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id SAA08770
	for ngtrans@sunroof.eng.sun.com; Fri, 21 Jul 2000 18:47:19 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LNWU612473
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:32:30 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA29025
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:32:31 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA29527
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:32:29 -0600 (MDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id QAA23302;
	Fri, 21 Jul 2000 16:32:22 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <3978DD86.29C39507@aciri.org>
Date: Fri, 21 Jul 2000 16:32:22 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian Zill <bzill@microsoft.com>
CC: Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4
References: <2E3FA0558747934A8F753CC533A3F6DF01101D@red-msg-24.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit


> 
> You're assuming you want one :-)  As Keith points out, using 6to4 results in

Please believe me, I was never assuming such a thing!  I had merely
observed that native IPv6 addresses is the end-goal for IPv6, and so
wondered why one wouldn't want to move towards that goal a bit quicker
given the opportunity.



> 
> This is a great transition scenario.  Everyone who has at least one IPv4
> .....
> pipes put into place, they will get used automatically.  Bottom line: it's
> more efficient than today's 6bone tunnel scheme and with almost zero
> configuration hassles.
> 

So, why would anybody ever move to native IPv6 addresses once they are
happily using 6to4?  More to the point, why would an ISP ever start
offering IPv6 services if all of their customers are happily tunneling
their IPv6 over IPv4?

PF



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 21:56:07 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10025
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 21:56:07 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA22056;
	Fri, 21 Jul 2000 19:55:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA02230;
	Fri, 21 Jul 2000 18:55:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M1spO12763
	for ngtrans-dist; Fri, 21 Jul 2000 18:54:51 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M1sl612756
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:54:47 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id SAA08833
	for ngtrans@sunroof.eng.sun.com; Fri, 21 Jul 2000 18:53:07 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6LNWU612473
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:32:30 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id QAA29025
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 16:32:31 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA29527
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 17:32:29 -0600 (MDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id QAA23302;
	Fri, 21 Jul 2000 16:32:22 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <3978DD86.29C39507@aciri.org>
Date: Fri, 21 Jul 2000 16:32:22 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian Zill <bzill@microsoft.com>
CC: Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4
References: <2E3FA0558747934A8F753CC533A3F6DF01101D@red-msg-24.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit


> 
> You're assuming you want one :-)  As Keith points out, using 6to4 results in

Please believe me, I was never assuming such a thing!  I had merely
observed that native IPv6 addresses is the end-goal for IPv6, and so
wondered why one wouldn't want to move towards that goal a bit quicker
given the opportunity.



> 
> This is a great transition scenario.  Everyone who has at least one IPv4
> .....
> pipes put into place, they will get used automatically.  Bottom line: it's
> more efficient than today's 6bone tunnel scheme and with almost zero
> configuration hassles.
> 

So, why would anybody ever move to native IPv6 addresses once they are
happily using 6to4?  More to the point, why would an ISP ever start
offering IPv6 services if all of their customers are happily tunneling
their IPv6 over IPv4?

PF

From owner-ipng@sunroof.eng.sun.com  Fri Jul 21 18:11:33 2000
X-Unix-From: owner-ipng@sunroof.eng.sun.com  Fri Jul 21 18:11:33 2000
Return-Path: <owner-ipng@sunroof.eng.sun.com>
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by jurassic.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M1BXI573971
	for <jrh@jurassic.eng.sun.com>; Fri, 21 Jul 2000 18:11:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M1BVQ12619;
	Fri, 21 Jul 2000 18:11:31 -0700 (PDT)
Date: Fri, 21 Jul 2000 18:11:31 -0700 (PDT)
From: owner-ipng@sunroof.eng.sun.com
Message-Id: <200007220111.e6M1BVQ12619@sunroof.eng.sun.com>
To: owner-ipng@sunroof.eng.sun.com
Subject: BOUNCE ipng@sunroof.eng.sun.com:    Non-member submission from [Hideaki YOSHIFUJI <yoshfuji@v6.linux.or.jp>]   
Content-Length: 4331
Status: RO
X-Status: $$$T
X-UID: 0000000031

From owner-ipng Fri Jul 21 18:11:17 2000
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M1BH612612
	for <ipng@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:11:17 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id SAA28151
	for <ipng@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:11:16 -0700 (PDT)
Received: from cerberus.nemoto.ecei.tohoku.ac.jp ([130.34.199.67])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA07457
	for <ipng@sunroof.eng.sun.com>; Fri, 21 Jul 2000 18:11:15 -0700 (PDT)
Received: from localhost (yoshfuji@localhost [127.0.0.1])
	by cerberus.nemoto.ecei.tohoku.ac.jp (8.9.3+3.2W/8.9.3/Debian 8.9.3-21) with ESMTP id KAA01997;
	Sat, 22 Jul 2000 10:10:22 +0900
To: bzill@microsoft.com
Cc: itojun@iijlab.net, bound@zk3.dec.com, ipng@sunroof.eng.sun.com
Subject: RE: New "IP Version 6 Addressing Architecture" draft
From: Hideaki YOSHIFUJI <yoshfuji@v6.linux.or.jp>
In-Reply-To: <2E3FA0558747934A8F753CC533A3F6DF01101E@red-msg-24.redmond.corp.microsoft.com>
References: <2E3FA0558747934A8F753CC533A3F6DF01101E@red-msg-24.redmond.corp.microsoft.com>
X-Mailer: Mew version 1.94 on Emacs 20.7 / Mule 4.1 (AOI)
Sender: YOSHIFUJI Hideaki <yoshfuji@cerberus.nemoto.ecei.tohoku.ac.jp>
X-URL: http://www.ecei.tohoku.ac.jp/%7Eyoshfuji/
X-Fingerprint: F7 31 65 99 5E B2 BB A7 15 15  13 23 18 06 A9 6F 57 00 6B 25
X-Pgp5-Key-Url: http://cerberus.nemoto.ecei.tohoku.ac.jp/%7Eyoshfuji/yoshfuji@ecei.tohoku.ac.jp.asc
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000722101021L.yoshfuji@cerberus.nemoto.ecei.tohoku.ac.jp>
Date: Sat, 22 Jul 2000 10:10:21 +0900
X-Dispatcher: imput version 990905(IM130)
Lines: 63

In article <2E3FA0558747934A8F753CC533A3F6DF01101E@red-msg-24.redmond.corp.microsoft.com> (at Fri, 21 Jul 2000 17:03:19 -0700), Brian Zill <bzill@microsoft.com> says:

> I am unwilling to give up SIIT.  Changing the architecture to forbid
> IPv4-mapped addresses on the wire is unacceptable in my opinion.

Me too.


> If an IPv4 packet arrived at your machine with a source address of
> 127.0.0.1, what would your kernel do?  Now if an IPv6 packet arrives at your
> machine with a source address of ::ffff:127.0.0.1, what does your kernel do?
> If it does the same thing in both cases, why should user-land care how it
> got there?  If it doesn't do the same thing, why not?

Same thing.  You are right!


> > they can let us relay malicious packets by abusing
> > normal IPv6 routers, auto-tunnel capable IPv6
> > routers, and 6to4 relay routers.  it will be much
> > harder to track than normal IP packets we are seeing.
> 
> These are all tunnelling issues.  Nobody is suggesting getting rid of
> tunnels to fix them - they're suggesting appropriate security checks.  I ask
> again, why is adding checks to protect against v4-mapped address misuse any
> different?

Agreed.


> > SIIT requires the dual use of IPv4 mapped address 
> > (native-ipv4-mapped and RFC2553-inbound).  this is
> > a feature of SIIT, not the other documents.
> 
> No, SIIT doesn't require user-level programs to receive IPv4 packets on
> AF_INET6 socekts.  It only requires that IPv6 packets (with v4-mapped
> addresses) are received on AF_INET6 sockets.  Machines living on the v6 side
> of the translator only need to speak v6!

Yes, SIIT is for IPv6 node that is not IPv4 capable.
And you can drop packet that have encapsulated ipv4 source
address belongs to local subnet (a.b.c.d/n) from outside:

   subnet      +----------+ outside (IPv6, IPv4)
---------------| SIIT Box |----------------------
 (a.b.c.d/n)   +----------+

And, leaf nodes should drops packets from ::ffff:127.0.0.0/104 from subnet
as we want to drop 127.0.0.0/8 on ipv4 nodes:

+-----------+            subnet
| ipv6 node |---------------------------------
+-----------+ (IPv6 capable, don't care IPv4)


Itojun, issues/examples you raised are not problems
(at RFC2553 or addressing-architecture level).
You should raise new examples again to convince us.

-- 
Hideaki YOSHIFUJI @ USAGI Project  <yoshfuji@v6.linux.or.jp>
Web Page: http://www.ecei.tohoku.ac.jp/%7Eyoshfuji/
PGP5i FP: F731 6599 5EB2 BBA7 1515  1323 1806 A96F 5700 6B25 



From owner-ngtrans@sunroof.eng.sun.com  Fri Jul 21 22:31:05 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22812
	for <ngtrans-archive@odin.ietf.org>; Fri, 21 Jul 2000 22:31:05 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA01627;
	Fri, 21 Jul 2000 20:30:28 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA24430;
	Fri, 21 Jul 2000 19:30:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6M2TJL12844
	for ngtrans-dist; Fri, 21 Jul 2000 19:29:19 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6M2TC612837
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 19:29:12 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA04981
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 19:29:10 -0700 (PDT)
Received: from melimelo.enst-bretagne.fr (melimelo.enst-bretagne.fr [192.108.115.36])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA27924
	for <ngtrans@sunroof.eng.sun.com>; Fri, 21 Jul 2000 19:29:09 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by melimelo.enst-bretagne.fr (8.10.1/8.10.1) with ESMTP id e6M2Lt616379;
	Sat, 22 Jul 2000 04:21:55 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id EAA27614;
	Sat, 22 Jul 2000 04:21:55 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.9.3/8.9.3) with ESMTP id EAA41418;
	Sat, 22 Jul 2000 04:22:04 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200007220222.EAA41418@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Steve Deering <deering@cisco.com>
cc: Brian Zill <bzill@microsoft.com>, "'Paul Francis'" <francis@aciri.org>,
        Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4 
In-reply-to: Your message of Fri, 21 Jul 2000 16:37:03 PDT.
             <p04320401b59e8dfbe107@[171.70.84.50]> 
Date: Sat, 22 Jul 2000 04:22:04 +0200
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>

 In your previous mail you wrote:

   At 4:15 PM -0700 7/21/00, Brian Zill wrote:
   >This is a great transition scenario.  Everyone who has at least one IPv4
   >address automatically has a huge amount of globally routable IPv6 address
   >space.
   
=> *personally* I don't like 6to4 because this is far too close to
automatic tunnel / compatible address stuff which was proved to
be a bad idea.

   Not to disagree, but just to observe that there are many Internet
   subscribers who do not have even one globally-unique IPv4 address --
   they only get temporary use of one from a shared pool when they
   "login to the Internet".
   
=> you can easily change the shared-temporary IPv4 address for
a globally-unique IPv6 one (draft-ietf-ngtrans-hometun-00.txt).
IPv6 is for users at home too, even if they don't know it today...

Regards

Francis.Dupont@enst-bretagne.fr

PS: perhaps I should present my draft at a ngtrans session and
implement it (:-)...


From owner-ngtrans@sunroof.eng.sun.com  Sat Jul 22 12:51:05 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21273
	for <ngtrans-archive@odin.ietf.org>; Sat, 22 Jul 2000 12:51:04 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA22911;
	Sat, 22 Jul 2000 10:50:42 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA05584;
	Sat, 22 Jul 2000 09:50:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6MGmqH13318
	for ngtrans-dist; Sat, 22 Jul 2000 09:48:52 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6MGmj613311
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 09:48:45 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id JAA14941
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 09:48:44 -0700 (PDT)
Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA22584
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 10:48:43 -0600 (MDT)
Received: from hunkular.glarp.com (localhost [127.0.0.1])
	by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id KAA78322;
	Sat, 22 Jul 2000 10:48:36 -0600 (MDT)
	(envelope-from huntting@hunkular.glarp.com)
Message-Id: <200007221648.KAA78322@hunkular.glarp.com>
To: Paul Francis <francis@aciri.org>
cc: Brian Zill <bzill@microsoft.com>,
        Brian E Carpenter <brian@hursley.ibm.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4 
In-Reply-To: Your message of "Fri, 21 Jul 2000 16:32:22 PDT."
             <3978DD86.29C39507@aciri.org> 
Date: Sat, 22 Jul 2000 10:48:36 -0600
From: Brad Huntting <huntting@hunkular.glarp.com>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brad Huntting <huntting@hunkular.glarp.com>


> So, why would anybody ever move to native IPv6 addresses once they are
> happily using 6to4? [....]

Because eventually they will want multicast.


brad


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 13:19:56 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29686
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 13:19:55 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA17538;
	Mon, 24 Jul 2000 11:18:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA22910;
	Mon, 24 Jul 2000 10:15:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6OHDvB14434
	for ngtrans-dist; Mon, 24 Jul 2000 10:13:57 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OHDq614427
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 10:13:52 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id KAA09563
	for ngtrans@sunroof.eng.sun.com; Mon, 24 Jul 2000 10:12:11 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6N4EK613447
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 21:14:21 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id VAA08347
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 21:14:19 -0700 (PDT)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id WAA02797
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jul 2000 22:14:18 -0600 (MDT)
Received: from vaio ([63.204.196.3])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with SMTP id <0FY4008IEUEFHX@mta5.snfc21.pbi.net> for
 ngtrans@sunroof.eng.sun.com; Sat, 22 Jul 2000 21:13:28 -0700 (PDT)
Date: Sat, 22 Jul 2000 21:12:26 -0700
From: Paul Francis <francis@aciri.org>
Subject: RE: (ngtrans) questions about 6to4
In-reply-to: <200007220222.EAA41418@givry.rennes.enst-bretagne.fr>
To: Francis.Dupont@enst-bretagne.fr
Cc: ngtrans@sunroof.eng.sun.com
Message-id: <028201bff45c$36431dc0$03c4cc3f@pacbell.net>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Importance: Normal
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Priority: 3 (Normal)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit

>    
> => *personally* I don't like 6to4 because this is far too close to
> automatic tunnel / compatible address stuff which was proved to
> be a bad idea.
> 

What, in a nutshell, was the problem?

PF




From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 13:56:21 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11191
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 13:56:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA19927;
	Mon, 24 Jul 2000 11:55:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA04576;
	Mon, 24 Jul 2000 10:20:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6OHJnn14460
	for ngtrans-dist; Mon, 24 Jul 2000 10:19:49 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OHJj614453
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 10:19:45 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id KAA09592
	for ngtrans@sunroof.eng.sun.com; Mon, 24 Jul 2000 10:18:04 -0700 (PDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OAgt614159
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 03:42:56 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id DAA09365
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 03:42:54 -0700 (PDT)
Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA19568
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 04:42:53 -0600 (MDT)
Received: from kanagw970.kanagawa.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id TAA01739; Mon, 24 Jul 2000 19:42:52 +0900 (JST)
Received: by kanagw970.kanagawa.hitachi.co.jp (8.9.0/3.6Wbeta6-GPCD) id TAA13057; Mon, 24 Jul 2000 19:42:52 +0900 (JST)
Message-Id: <200007241042.TAA13057@kanagw970.kanagawa.hitachi.co.jp>
X-Sender: tsuchiya@158.214.152.195
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3-J (32)
Date: Mon, 24 Jul 2000 19:42:53 +0900
To: ngtrans@sunroof.eng.sun.com
From: Kazuaki Tsuchiya <tsuchiya@kanagawa.hitachi.co.jp>
Subject: (ngtrans) Re: I-D ACTION:draft-tsuchiya-mtp-00.txt
Cc: tsuchiya@kanagawa.hitachi.co.jp
In-Reply-To: <200007111029.GAA23282@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kazuaki Tsuchiya <tsuchiya@kanagawa.hitachi.co.jp>

Ngtrans folks,

Sorry for interrupting you.

But I just want to inform you that we have submitted a draft
describing a mechanism which enables multicast communication
between IPv4 nodes and IPv6 nodes.

You can get it from the following ftp site, if you have interest
in it:
  http://www.ietf.org/internet-drafts/draft-tsuchiya-mtp-00.txt

Any suggestions and comments are appreciated.

Thanks.

-- Kazuaki Tsuchiya, Hitachi.

At 06:29 00/07/11 -0400, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 
> 	Title		: An IPv6/IPv4 Multicast Translator based on IGMP/MLD 
>                           Proxying (MTP)
> 	Author(s)	: K. Tsuchiya, H. Higuchi, S. Sawada, S. Nozaki
> 	Filename	: draft-tsuchiya-mtp-00.txt
> 	Pages		: 11
> 	Date		: 10-Jul-00
> 	
> In the stage of the transition from IPv4 to IPv6 it is necessary
> that IPv4 nodes and IPv6 nodes can communicate directly. This memo
> proposes a mechanism which enables such direct communication for
> multicast, in addition to that for unicast defined in [SIIT] and
> [NAT-PT].
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-tsuchiya-mtp-00.txt
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-tsuchiya-mtp-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-tsuchiya-mtp-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID:	<20000710151135.I-D@ietf.org>
> 
> ENCODING mime
> FILE /internet-drafts/draft-tsuchiya-mtp-00.txt
> 
> <ftp://ftp.ietf.org/internet-drafts/draft-tsuchiya-mtp-00.txt>
> 
------------------------------------------------------------
Kazuaki Tsuchiya (mailto:tsuchiya@kanagawa.hitachi.co.jp)
  Hitachi,Ltd. Enterprise Server Division
  Phone: +81(463)87-7499[Dial-in] Fax: +81(463)87-7341



From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 14:00:51 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12310
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 14:00:50 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA23788;
	Mon, 24 Jul 2000 12:00:12 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA22009;
	Mon, 24 Jul 2000 10:56:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6OHsv214556
	for ngtrans-dist; Mon, 24 Jul 2000 10:54:57 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OHso614549
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 10:54:51 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA04760
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 10:54:49 -0700 (PDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA05652
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 10:54:47 -0700 (PDT)
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 SAA99732; Mon, 24 Jul 2000 18:54:04 +0100
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id SAA18764; Mon, 24 Jul 2000 18:54:39 +0100 (BST)
Message-ID: <397C8089.E6D6303C@hursley.ibm.com>
Date: Mon, 24 Jul 2000 12:44:41 -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: Paul Francis <francis@aciri.org>
CC: Francis.Dupont@enst-bretagne.fr, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) questions about 6to4
References: <028201bff45c$36431dc0$03c4cc3f@pacbell.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Paul Francis wrote:
> 
> >
> > => *personally* I don't like 6to4 because this is far too close to
> > automatic tunnel / compatible address stuff which was proved to
> > be a bad idea.
> >
> 
> What, in a nutshell, was the problem?

ErHum, 6to4 was designed to avoid the issues that
compatible addresses generated, mainly pollution of
the IPv6 routing tables with the IPv4 swamp.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 14:35:26 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21524
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 14:35:25 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA22574;
	Mon, 24 Jul 2000 12:34:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA23465;
	Mon, 24 Jul 2000 11:33:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6OIWnK14629
	for ngtrans-dist; Mon, 24 Jul 2000 11:32:49 -0700 (PDT)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OIWj614622
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 11:32:45 -0700 (PDT)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id LAA09718
	for ngtrans@sunroof.eng.sun.com; Mon, 24 Jul 2000 11:31:03 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OIQN614609
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 11:26:23 -0700 (PDT)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA21477
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 11:26:22 -0700 (PDT)
Received: from baboon.aciri.org (baboon.aciri.org [192.150.187.38])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA28489
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 11:26:15 -0700 (PDT)
Received: from aciri.org (localhost [127.0.0.1])
	by baboon.aciri.org (8.9.3/8.9.3) with ESMTP id LAA43145;
	Mon, 24 Jul 2000 11:26:15 -0700 (PDT)
	(envelope-from francis@aciri.org)
Message-ID: <397C8A47.772BB9F1@aciri.org>
Date: Mon, 24 Jul 2000 11:26:15 -0700
From: Paul Francis <francis@aciri.org>
Organization: ACIRI
X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.0.36 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com
CC: Brian Zill <bzill@microsoft.com>,
        Brad Huntting <huntting@hunkular.glarp.com>
Subject: Re: (ngtrans) questions about 6to4
References: <2E3FA0558747934A8F753CC533A3F6DF011020@red-msg-24.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Paul Francis <francis@aciri.org>
Content-Transfer-Encoding: 7bit

Brian Zill wrote:
> 
> To recover the "wasted" bandwidth of the encapsulation overhead.  ISP's will
> realize that their customer's only care about the IPv6 data going through,
> so if they can carry IPv6 natively, they "get back" the amount of bandwidth
> being used on IPv4 encapsulation.

I cannot take seriously the idea that an ISP would go through the
tremendous expense of putting in an IPv6 infrastructure for the purpose
of saving 20 bytes per packet.

> 
> There are also all the other good points about IPv6 that we've beaten to
> death: ease of configuration, routing aggregation, etc. etc.
> 

Ease of (host) configuration has nothing to do with 6to4.  An IPv6 site
operates the same whether it has 6to4 prefixes or native prefixes.  

At the risk of a little hand-waving---routing aggregation could still be
achieved in IPv4...once the IPv6 sites have renumbering running, ISPs
could change a customer's 6to4 prefix as easily as it could change the
customer's native prefix.  Or, looked at another way, we could allocate
a block of IPv4 addresses for use *only* with 6to4 prefixes.  We could
allocate the same number of these as we have top level native prefixes
now.  These would therefore have the same aggregation characteristics as
native v6 is supposed to have.  So I see no fundamental difference in
getting aggregation from 6to4 versus native.

Brad Huntting wrote:
> 
> > So, why would anybody ever move to native IPv6 addresses once they are
> > happily using 6to4? [....]
> 
> Because eventually they will want multicast.
> 

First of all, I doubt it...I see the global multicast world solidly
moving in the direction of unicast overlays.

But this is an arguable view, so lets assume for the sake of argument
that there is a demand for IPv6 global multicast.  Fine...do IPv6
multicast using IPv6 routers (that run multicast, not necessarily
unicast) with 6to4 prefixes... 


Bottom line, I still have yet to see a solid argument for why we need
native IPv6 prefixes at all...

PF



From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 15:30:46 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08716
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 15:30:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA02652;
	Mon, 24 Jul 2000 13:29:51 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA07864;
	Mon, 24 Jul 2000 12:29:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6OJSHm14677
	for ngtrans-dist; Mon, 24 Jul 2000 12:28:17 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6OJS7614670
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 12:28:07 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA07526
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 12:27:50 -0700 (PDT)
Received: from astro.cs.utk.edu (ASTRO.CS.UTK.EDU [128.169.93.168])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA01428
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 13:27:49 -0600 (MDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id PAA04044;
        Mon, 24 Jul 2000 15:27:45 -0400 (EDT)
Message-Id: <200007241927.PAA04044@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Paul Francis <francis@aciri.org>
cc: ngtrans@sunroof.eng.sun.com, Brian Zill <bzill@microsoft.com>,
        Brad Huntting <huntting@hunkular.glarp.com>
Subject: Re: (ngtrans) questions about 6to4 
In-reply-to: Your message of "Mon, 24 Jul 2000 11:26:15 PDT."
             <397C8A47.772BB9F1@aciri.org> 
Date: Mon, 24 Jul 2000 15:27:45 -0400
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Keith Moore <moore@cs.utk.edu>

> > To recover the "wasted" bandwidth of the encapsulation overhead.  ISP's will
> > realize that their customer's only care about the IPv6 data going through,
> > so if they can carry IPv6 natively, they "get back" the amount of bandwidth
> > being used on IPv4 encapsulation.
> 
> I cannot take seriously the idea that an ISP would go through the
> tremendous expense of putting in an IPv6 infrastructure for the purpose
> of saving 20 bytes per packet.

I don't know about "tremendous expense"...I expect that ISPs will
evaluate IPv6 requirements as part of their normal facilities planning
and that they will upgrade their existing infrastructures to support
native IPv6 as part of their normal infrastructure improvement.  
The ability to save 20 bytes per packet might have a slight effect
on when an ISP decides to upgrade -- as might other economic 
considerations such as the ability to route v6 traffic more 
efficiently than is feasible with 6to4. 

> Ease of (host) configuration has nothing to do with 6to4.  

but ease of site configuration - especially in not needing to get 
a separate prefix - certainly is part of the incentive to use 6to4.

> At the risk of a little hand-waving---routing aggregation could still be
> achieved in IPv4...once the IPv6 sites have renumbering running, ISPs
> could change a customer's 6to4 prefix as easily as it could change the
> customer's native prefix.  

yes.

> Or, looked at another way, we could allocate
> a block of IPv4 addresses for use *only* with 6to4 prefixes.  

we could, but insisting that 6to4 use such prefixes (which you would
need to get any benefit from this strategy) would make 6to4 
much less attractive and much less likely to be deployed.

> Bottom line, I still have yet to see a solid argument for why we need
> native IPv6 prefixes at all...

I don't know how soon we will need them - 6to4 provides a bit of
growing room.  but it seems unwise to assume that 6to4 prefixes
will always be sufficient forever.  I can certainly think of
potential IPv6 applications for which the existing number of 
unused IPv4 prefixes would not be sufficient - not that we
have the luxury of using all of the remaining prefixes v4 for 
6to4 anyway.    Even if 6to4 is wildly successful, we can expect 
the v4 net to be around for another decade or two, during which 
time those prefixes will likely be needed for native v4.

but 6to4 buys flexibility - it allows near-term deployment of v6 
along with an easy transition to native v6.  it lets the ISPs and 
the users decide when that transition should be made, and lets them
make that transition away from 6to4 (like the transition *to* 6to4)
if and when it makes sense to do so.

Keith


From owner-ngtrans@sunroof.eng.sun.com  Mon Jul 24 23:43:04 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15834
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jul 2000 23:43:03 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA10522;
	Mon, 24 Jul 2000 21:42:42 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA26377;
	Mon, 24 Jul 2000 20:42:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6P3fOa15229
	for ngtrans-dist; Mon, 24 Jul 2000 20:41:24 -0700 (PDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6P3fI615222
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 20:41:18 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id UAA09022
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 20:41:16 -0700 (PDT)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id VAA10026
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jul 2000 21:41:16 -0600 (MDT)
Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 24 Jul 2000 20:40:49 -0700 (Pacific Daylight Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2651.58)
	id <PGAHMCFW>; Mon, 24 Jul 2000 20:40:45 -0700
Message-ID: <4D0A23B3F74DD111ACCD00805F31D8101CA22287@RED-MSG-50>
From: Richard Draves <richdr@microsoft.com>
To: "'Paul Francis'" <francis@aciri.org>
Cc: ngtrans@sunroof.eng.sun.com
Subject: RE: (ngtrans) questions about 6to4
Date: Mon, 24 Jul 2000 20:40:04 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Richard Draves <richdr@microsoft.com>

> I cannot take seriously the idea that an ISP would go through the
> tremendous expense of putting in an IPv6 infrastructure for 
> the purpose
> of saving 20 bytes per packet.

It's their call. At some point, I think if the ISPs see their customers
using IPv6 then they will want to support it more directly (surely
supporting your customers needs directly is better than indirectly?) but if
this doesn't happen soon, that's fine too.

> > => *personally* I don't like 6to4 because this is far too close to
> > automatic tunnel / compatible address stuff which was proved to
> > be a bad idea.
> > 
> 
> What, in a nutshell, was the problem?

The problem with IPv4-compatible addresses is that every machine needs an
IPv4 address. (Otherwise they work great.) If you can get that many IPv4
addresses, the major advantage of IPv6 is moot. Whereas with 6to4, you just
need one IPv4 address for your entire site.

Rich


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 25 08:25:11 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24588
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jul 2000 08:25:10 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA06094;
	Tue, 25 Jul 2000 06:24:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA25400;
	Tue, 25 Jul 2000 05:24:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6PCN9X15434
	for ngtrans-dist; Tue, 25 Jul 2000 05:23:09 -0700 (PDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6PCN3615427
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 05:23:03 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id FAA05260
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 05:23:02 -0700 (PDT)
Received: from mail2.microsoft.com (mail2.microsoft.com [131.107.3.124])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id GAA05223
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 06:23:01 -0600 (MDT)
Received: from 157.54.9.104 by mail2.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 25 Jul 2000 05:21:26 -0700 (Pacific Daylight Time)
Received: by INET-IMC-02 with Internet Mail Service (5.5.2651.58)
	id <P261R3CH>; Tue, 25 Jul 2000 05:22:21 -0700
Message-ID: <4D0A23B3F74DD111ACCD00805F31D810219D39C4@RED-MSG-50>
From: Richard Black <rjblack@microsoft.com>
To: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>,
        "'alain.durand@sun.com'" <alain.durand@sun.com>
Cc: Richard Black <rjblack@microsoft.com>,
        "Stuart Prevost (E-mail)"
	 <stuart.prevost@bt.com>
Subject: (ngtrans) Re: draft-ietf-ngtrans-broker-03.txt
Date: Tue, 25 Jul 2000 05:21:16 -0700
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Richard Black <rjblack@microsoft.com>

I would like to make several comments on the current
draft-ietf-ngtrans-broker-03.txt document.  For background, I am the
principal author of the Microsoft Research IPv6 Tunnel Broker, which
is currently in beta.

1.  First, I am unhappy about the suggestions that the prefix length
    supported by brokers and/or the allocations made to the clients
    should be either /64 or /48.  The draft reads:

      "This prefix can be ether [sic] 48 or 64 bits."

    Later it reads

      "[the broker] chooses the IPv6 prefix (e.g., /128, /64 or /48)
       to be allocated to the client."

    which is much better.  There are several issues here.

    a) No user should be given more addresses than they can correctly
       configure.  If an address range is allocated to a user then the
       tunnel server at the ISP will have a (pseudo-) static route for
       that address range pointing at the user's end of the tunnel.
       The user is likely to have a default route pointing back at the
       ISP.

       That user must ensure that packets sent to any address within
       that range are handled correctly.  If the addresses are not in
       use then an ICMP unreachable should be returned.  If, however,
       a user is allocated a range larger than they can assign, then
       they must ensure that other addresses are routed to their
       loop-back (or discard) interface as appropriate to ensure that
       the packets do not bounce back and forward between the user and
       the ISP.

       Many users may not be aware of this responsibility (or
       sufficiently technically proficient), and so allocating them a
       range larger than that which they can reasonably handle is just
       going to lead to support issues for the ISP.

    b) Part of the reason for CIDR and the specific prefix in IPv6
       notation was to get away from clasfullness and hard and
       inflexible divisions of the address space.

       Whilst it may be useful to have some common defaults, and for
       BGP visible Autonomous Systems to have some maximum on the
       number of prefix bits allocated, within one agregatable route
       (e.g., between an ISP and its customers) there is no reason to
       mandate by standard any particular fixed prefix allocations.

       An ISP should be free to make this division any way that it
       chooses.  I should think (for example) that a /56 is likely to
       be sufficient for most organisations.  [For reference the
       MSR broker presently supports /48 /64 and /128 so I'm not
       saying this just because I've done it.]

       The broker draft should not appear to mandate any particular
       standard prefix allocations (other than /64 and /128).


2. Secondly, I'm unhappy with paragraph 7 of section 2.6 (para 3 of
   page 7) in which it is suggested that a broker use RSH to configure
   clients.

   Since IP(v4 or v6) level configuration is inevitably a root /
   Administrator function I do not think that any RFC should suggest
   that a user configure their machine to have remote root RSH
   access.  [RSH may be appropriate between the broker and the server
   however]

   Likewise, none of the security effects of extending use of DHCP
   beyond a single administrative boundary have been considered, and
   this is also likely to be unreasonable.

   This paragraph should simply be removed.  


3. I am unclear as to the utility of a MIME attachment to achieve user
   configuration.

   Few users run an MUA with root privileges (and again its unclear
   whether this should be encouraged),  likewise the machine on which
   the email is handled need not be the same as the machine which will
   be used for the client end of the tunnel.

   A configuration script seems much more flexible (if less pretty)
   and has the advantage that the user can check it for safety, and
   clever administrator can modify it.   Besides which, how is a MIME
   agent going to decide which interface to allocate the /64 to, or
   how to subnet a /48 or .....



Richard Black
Microsoft Research


From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 25 14:56:14 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00711
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jul 2000 14:56:14 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA25792;
	Tue, 25 Jul 2000 12:55:31 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id LAA13940;
	Tue, 25 Jul 2000 11:54:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6PIrKQ15976
	for ngtrans-dist; Tue, 25 Jul 2000 11:53:20 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.87.31] (may be forged))
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6PIrD615969
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 11:53:14 -0700 (PDT)
Received: from eng.sun.com (sappey.Eng.Sun.COM [129.146.85.69])
	by jurassic.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6PIr9I962163;
	Tue, 25 Jul 2000 11:53:11 -0700 (PDT)
Message-ID: <397DE19C.441D8FE4@eng.sun.com>
Date: Tue, 25 Jul 2000 11:51:08 -0700
From: Alain Durand <alain.durand@eng.sun.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Richard Black <rjblack@microsoft.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
CC: "Stuart Prevost (E-mail)" <stuart.prevost@bt.com>
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-broker-03.txt
References: <4D0A23B3F74DD111ACCD00805F31D810219D39C4@RED-MSG-50>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <alain.durand@eng.sun.com>
Content-Transfer-Encoding: 7bit

Richard Black wrote:

> I would like to make several comments on the current
> draft-ietf-ngtrans-broker-03.txt document.  For background, I am the
> principal author of the Microsoft Research IPv6 Tunnel Broker, which
> is currently in beta.

Richard,

Thank you very much from your comments.


> 1.  First, I am unhappy about the suggestions that the prefix length
>     supported by brokers and/or the allocations made to the clients
>     should be either /64 or /48.  The draft reads:
>
>       "This prefix can be ether [sic] 48 or 64 bits."
>
>     Later it reads
>
>       "[the broker] chooses the IPv6 prefix (e.g., /128, /64 or /48)
>        to be allocated to the client."
>
>     which is much better.  There are several issues here.

You're right, The first paragraph  should be made more consistent with
the second one.

>        An ISP should be free to make this division any way that it
>        chooses.  I should think (for example) that a /56 is likely to
>        be sufficient for most organisations.  [For reference the
>        MSR broker presently supports /48 /64 and /128 so I'm not
>        saying this just because I've done it.]
>
>        The broker draft should not appear to mandate any particular
>        standard prefix allocations (other than /64 and /128).

/48 is comming from the address architecture that specifies that
a site prefix lenght is /48. I know that there are discussion with
the registries and the ISPs to change this.
However, I agree that whatever is connected via the tunnel broker
may or may not be a "site", thus the /48 boundary may or may not
apply. We may add some text to say that and relax the boundary
limitation.
We should discuss this point in Pittsburgh.


> 2. Secondly, I'm unhappy with paragraph 7 of section 2.6 (para 3 of
>    page 7) in which it is suggested that a broker use RSH to configure
>    clients.
>
>    Since IP(v4 or v6) level configuration is inevitably a root /
>    Administrator function I do not think that any RFC should suggest
>    that a user configure their machine to have remote root RSH
>    access.  [RSH may be appropriate between the broker and the server
>    however]
>
>    Likewise, none of the security effects of extending use of DHCP
>    beyond a single administrative boundary have been considered, and
>    this is also likely to be unreasonable.
>
>    This paragraph should simply be removed.

We could probably be less specific in this paragraph.

> 3. I am unclear as to the utility of a MIME attachment to achieve user
>    configuration.
>
>    Few users run an MUA with root privileges (and again its unclear
>    whether this should be encouraged),  likewise the machine on which
>    the email is handled need not be the same as the machine which will
>    be used for the client end of the tunnel.
>
The MIME type is not necessairely sent over a mail message.
It's just a framework to convey configuration parameters
ant let the client do the actual configuration itself.
This is somehow more secure than blindly executing a script
downloaded from a remote location. Also, il could make hte life
of router implementing a tunnel broker client easier.


>    A configuration script seems much more flexible (if less pretty)
>    and has the advantage that the user can check it for safety, and
>    clever administrator can modify it.   Besides which, how is a MIME
>    agent going to decide which interface to allocate the /64 to, or
>    how to subnet a /48 or .....

This is a local configuration matter. You can have a site local topology
and use router renumbering messages to change this to the prefix
allocated
by the tunnel broker.

    - Alain.



From owner-ngtrans@sunroof.eng.sun.com  Tue Jul 25 15:39:01 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13524
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jul 2000 15:39:00 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA29057;
	Tue, 25 Jul 2000 13:38:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA12357;
	Tue, 25 Jul 2000 12:38:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6PJajF16260
	for ngtrans-dist; Tue, 25 Jul 2000 12:36:45 -0700 (PDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6PJac616253
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 12:36:38 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id MAA01066
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 12:36:37 -0700 (PDT)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA27590
	for <ngtrans@sunroof.eng.sun.com>; Tue, 25 Jul 2000 13:36:37 -0600 (MDT)
Received: from randy by rip.psg.com with local (Exim 3.13 #1)
	id 13HAVF-000HtX-00; Tue, 25 Jul 2000 12:36:33 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Alain Durand <alain.durand@eng.sun.com>
Cc: Richard Black <rjblack@microsoft.com>,
        "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>,
        "Stuart Prevost (E-mail)" <stuart.prevost@bt.com>
Subject: Re: (ngtrans) Re: draft-ietf-ngtrans-broker-03.txt
References: <4D0A23B3F74DD111ACCD00805F31D810219D39C4@RED-MSG-50>
	<397DE19C.441D8FE4@eng.sun.com>
Message-Id: <E13HAVF-000HtX-00@rip.psg.com>
Date: Tue, 25 Jul 2000 12:36:33 -0700
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

>>        The broker draft should not appear to mandate any particular
>>        standard prefix allocations (other than /64 and /128).
> /48 is comming from the address architecture that specifies that
> a site prefix lenght is /48. I know that there are discussion with
> the registries and the ISPs to change this.

ad hat off, isp and registry watcher's hat on.  i suspect that these
boundaries will be fluid for a fair while, and would not recommend
hard coding any boundaries.

randy


From owner-ngtrans@sunroof.eng.sun.com  Wed Jul 26 22:37:16 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25951
	for <ngtrans-archive@odin.ietf.org>; Wed, 26 Jul 2000 22:37:15 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA21735;
	Wed, 26 Jul 2000 20:36:37 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id TAA01555;
	Wed, 26 Jul 2000 19:36:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) id e6R2ZBo19316
	for ngtrans-dist; Wed, 26 Jul 2000 19:35:11 -0700 (PDT)
Received: from jurassic.eng.sun.com (jurassic [129.146.81.144] (may be forged))
	by sunroof.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6R2Z5619309
	for <ngtrans@sunroof.eng.sun.com>; Wed, 26 Jul 2000 19:35:05 -0700 (PDT)
Received: from eng.sun.com (dsl197-48.Eng.Sun.COM [129.146.197.48])
	by jurassic.eng.sun.com (8.10.2+Sun/8.10.2) with ESMTP id e6R2Z4I320206;
	Wed, 26 Jul 2000 19:35:04 -0700 (PDT)
Message-ID: <397F9FD9.182D00D9@eng.sun.com>
Date: Wed, 26 Jul 2000 19:35:05 -0700
From: alain.durand@eng.sun.com
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.8 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: ngtrans@sunroof.eng.sun.com, fink@es.net, tonyhain@microsoft.com
Subject: (ngtrans) NGtrans draft Agenda
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: alain.durand@eng.sun.com
Content-Transfer-Encoding: 7bit

Here is the draft agenda. As you will see, it is very very full.
We apologize to all people we promised longer slots, but
we are trying to fit everybody in.


Agenda bashing                                  5 min Chairs
TOKYO N+I backbone                              5 min Jinmei Tatuya
Document status                                         10 min Chairs
Overview document                                       5 min Alain
Durand
   - draft-ietf-ngtrans-introduction-to-ipv6-transition-04.txt
DSTM                                                    10 min Jim Bound

   - draft-ietf-ngtrans-dstm-02.txt
SIIT evolution                                  10 min Eric
   - draft-soliman-siit-dstm-00.txt
6to4 multicast                                  10 min Dave Thaler
   - draft-thaler-ngtrans-6to4-multicast-00.txt
6to4 scaling issues                             10 mins Tony Hain
   - draft-hain-6to4-scaling-00.txt
6to4 addresses reverse DNS lookups              10 min Keith Moore
   - draft-moore-6to4-dns-00.txt
Tunnels end point in DNS                        5 min Alain Durand
   - draft-durand-ngtrans-tunnel-endpoint-00.txt
Broker/Mime type                                        5 min
Ivano/Alain
   - draft-durand-ngtrans-tunnel-mime-type-00.txt
v6v4compat                                              5 min Fred
Templin
   - draft-templin-ngtrans-v6v4compat-01.txt
Hometun                                                 10 min Francis
Dupont
   - draft-ietf-ngtrans-hometun-00.txt
Multicast Translator                            5 min Kazuaki Tsuchiya
   - draft-tsuchiya-mtp-00.txt
Abuse against IPv6 transition           2 min Itojun
   - draft-itojun-ipv6-transition-abuse-01.txt
Transport relay translator                      2 min Itojun
   - draft-ietf-ngtrans-tcpudp-relay-01.txt
SOCKS update                                    2 min Hiroshi Kitamura
   - draft-ietf-ngtrans-socks-gateway-05.txt
Bump in the API                                         2 min Erik
Nordmark
   - draft-...
WG Name change                                  2 min Chairs



