From owner-ngtrans@sunroof.eng.sun.com  Tue Jan  4 11:16:29 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01580
	for <ngtrans-archive@odin.ietf.org>; Tue, 4 Jan 2000 11:16:28 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA05341;
	Tue, 4 Jan 2000 08:16:06 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA28053;
	Tue, 4 Jan 2000 08:15:31 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id e04GEZB07610
	for ngtrans-dist; Tue, 4 Jan 2000 08:14:36 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id e04GBoY07591;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA01920;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01956;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: by mailext02.compaq.com (Postfix, from userid 12345)
	id E79AF9A825; Tue,  4 Jan 2000 10:11:49 -0600 (CST)
Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190])
	by mailext02.compaq.com (Postfix) with ESMTP
	id D753A90D82; Tue,  4 Jan 2000 10:11:49 -0600 (CST)
Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345)
	id 6DF874FB01; Tue,  4 Jan 2000 10:11:42 -0600 (CST)
Received: from quarry.zk3.dec.com (bryquarry.zk3.dec.com [16.141.40.15])
	by mailint12.im.hou.compaq.com (Postfix) with ESMTP
	id 88D374C902; Tue,  4 Jan 2000 10:11:41 -0600 (CST)
Received: from localhost by quarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id LAA0000007759; Tue, 4 Jan 2000 11:11:48 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200001041611.LAA0000007759@quarry.zk3.dec.com>
To: members@ipv6forum.com, deployment@ipv6.org, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, Michael.Carney@east.sun.com,
        ipv6imp@munnari.oz.au
Cc: cmj@3com.com, us-summit@ipv6forum.com, tech@ipv6forum.com
Subject: (ngtrans) IPv6 Interoperability Testing Connectathon and IPv6 US Summit
Date: Tue, 04 Jan 2000 11:11:47 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

PLEASE DO NOT REPLY TO THIS MAIL SEND TO INDIVIDUAL LISTS ONLY OR TO 
CYNDI JUNG and/or I.  THANK YOU.........

Folks,

The University of New Hampshire (UNH) will be supporting the testing of IPv6
and interoperability testing of IPv6 between multiple independent
implementations at Sun Connectathon March 6-8 and the IPv6 Forum U.S. 
Summit at Teluride Colorado March 13-15.   If implementors can make both 
events that would be great, but it would be ideal if the routing vendors 
could attend Teluride for this testing.  Cyndi Jung at 3Com is driving this 
with UNH so please try to give IPv6 this support for the U.S. Summit.  We 
are hoping live and breathing end user decision makers attend this event at
Teluride.  More details and logistics will follow later.

Also UNH has added new IPv6 Mobility spec tests and Routing tests for
the events too, for those that can test these parts.

Implementor support is appreciated.
Theme: for testing is "Lets find the bugs when all the players are on
the same net with different implementations, do we all work, do some
only work in their own lab, and the results are not for public
consumption at either event so you can't get into marketing trouble,
only implementor attendees will know the results of doing the
interoperability testing, the press will not be allowed in the testing
area at Telluride".  

thanks
/jim



From owner-ngtrans@sunroof.eng.sun.com  Sat Jan  8 02:35:17 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16300
	for <ngtrans-archive@odin.ietf.org>; Sat, 8 Jan 2000 02:35:16 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA17673;
	Fri, 7 Jan 2000 23:35:13 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id XAA26636;
	Fri, 7 Jan 2000 23:34:55 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id e087XNb16712
	for ngtrans-dist; Fri, 7 Jan 2000 23:33:23 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id e087X5Y16699
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jan 2000 23:33:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id XAA23934
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jan 2000 23:33:05 -0800 (PST)
Received: from internexus.net (internexus.net [206.152.14.2])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id XAA13132
	for <ngtrans@sunroof.eng.sun.com>; Fri, 7 Jan 2000 23:33:02 -0800 (PST)
Received: (qmail 14912 invoked by uid 8079); 8 Jan 2000 07:32:34 -0000
MBOX-Line: From owner-ipng@sunroof.eng.sun.com Tue Jan 04 16:17:49 2000
X-UIDL: 7735ea6d980d8413e1efe661063e42eb
Delivered-To: ry@internexus.net
Received: (qmail 17102 invoked from network); 4 Jan 2000 16:17:48 -0000
Received: from mercury.sun.com (192.9.25.1)
  by internexus.net with SMTP; 4 Jan 2000 16:17:48 -0000
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA05512;
	Tue, 4 Jan 2000 08:16:24 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA17611;
	Tue, 4 Jan 2000 08:15:47 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) id e04GBxJ07598
	for ipng-dist; Tue, 4 Jan 2000 08:11:59 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta10+Sun/8.10.0.Beta10) with ESMTP id e04GBoY07591;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA01920;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: from mailext02.compaq.com (mailext02.compaq.com [207.18.199.33])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01956;
	Tue, 4 Jan 2000 08:11:50 -0800 (PST)
Received: by mailext02.compaq.com (Postfix, from userid 12345)
	id E79AF9A825; Tue,  4 Jan 2000 10:11:49 -0600 (CST)
Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190])
	by mailext02.compaq.com (Postfix) with ESMTP
	id D753A90D82; Tue,  4 Jan 2000 10:11:49 -0600 (CST)
Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345)
	id 6DF874FB01; Tue,  4 Jan 2000 10:11:42 -0600 (CST)
Received: from quarry.zk3.dec.com (bryquarry.zk3.dec.com [16.141.40.15])
	by mailint12.im.hou.compaq.com (Postfix) with ESMTP
	id 88D374C902; Tue,  4 Jan 2000 10:11:41 -0600 (CST)
Received: from localhost by quarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id LAA0000007759; Tue, 4 Jan 2000 11:11:48 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200001041611.LAA0000007759@quarry.zk3.dec.com>
To: members@ipv6forum.com, deployment@ipv6.org, ipng@sunroof.eng.sun.com,
        ngtrans@sunroof.eng.sun.com, Michael.Carney@east.sun.com,
        ipv6imp@munnari.oz.au
Cc: cmj@3com.com, us-summit@ipv6forum.com, tech@ipv6forum.com
Subject: (ngtrans) IPv6 Interoperability Testing Connectathon and IPv6 US Summit
Date: Tue, 04 Jan 2000 11:11:47 -0500
X-Mts: smtp
Status: RO
X-Keywords:                 
X-UID: 337
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

PLEASE DO NOT REPLY TO THIS MAIL SEND TO INDIVIDUAL LISTS ONLY OR TO 
CYNDI JUNG and/or I.  THANK YOU.........

Folks,

The University of New Hampshire (UNH) will be supporting the testing of IPv6
and interoperability testing of IPv6 between multiple independent
implementations at Sun Connectathon March 6-8 and the IPv6 Forum U.S. 
Summit at Teluride Colorado March 13-15.   If implementors can make both 
events that would be great, but it would be ideal if the routing vendors 
could attend Teluride for this testing.  Cyndi Jung at 3Com is driving this 
with UNH so please try to give IPv6 this support for the U.S. Summit.  We 
are hoping live and breathing end user decision makers attend this event at
Teluride.  More details and logistics will follow later.

Also UNH has added new IPv6 Mobility spec tests and Routing tests for
the events too, for those that can test these parts.

Implementor support is appreciated.
Theme: for testing is "Lets find the bugs when all the players are on
the same net with different implementations, do we all work, do some
only work in their own lab, and the results are not for public
consumption at either event so you can't get into marketing trouble,
only implementor attendees will know the results of doing the
interoperability testing, the press will not be allowed in the testing
area at Telluride".  

thanks
/jim

--------------------------------------------------------------------
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 Jan 13 05:40:05 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14812
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jan 2000 05:40:05 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA24499;
	Thu, 13 Jan 2000 02:38:33 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA17546;
	Thu, 13 Jan 2000 02:37:34 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0DAaNw00526
	for ngtrans-dist; Thu, 13 Jan 2000 02:36:23 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0DAaFw00519
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 02:36:16 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id CAA21796
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 02:36:14 -0800 (PST)
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 CAA00265
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 02:36:13 -0800 (PST)
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 TAA12340
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 19:34:58 +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 TAA29684 for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 19:34:57 +0900 (JST)
Received: from localhost (mine.iij.ad.jp [192.168.10.205]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id TAA01761 for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 19:34:57 +0900 (JST)
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) questions on SIIT
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.94.2pre8 on Emacs 20.5 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000113193437Z.kazu@iijlab.net>
Date: Thu, 13 Jan 2000 19:34:37 +0900
X-Dispatcher: imput version 20000113(IM136)
Lines: 41
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

I have two questions on the motivation of SIIT. The 08 ID says:

---
   However, there are other potential solutions in this area:
  (1) If there is no IPv4 routing inside the network i.e., the cloud
      that contains the new devices, some possible solutions are to
      either use the translators specified in this document at the
      boundary of the cloud, or to use Application Layer Gateways (ALG)
      on dual nodes at the cloud's boundary.  The ALG solution is less
      flexible in that it is application protocol specific and it is
      also less robust since an ALG box is likely to be a single point
      of failure for a connection using that box.

  (2) Otherwise, if IPv4 routing is supported inside the cloud and the
      implementations support both IPv6 and IPv4 it might suffice to
      have a mechanism for allocating a temporary address IPv4 and use
      IPv4 end to end when communicating with IPv4-only nodes.  However,
      it would seem that such a solution would require the pool of
      temporary IPv4 addresses to be partitioned across all the subnets
      in the cloud which would either require a larger pool of IPv4
      addresses or result in cases where communication would fail due to
      no available IPv4 address for the node's subnet.
---

(Q1) When we provide "a mechanism for providing routing (perhaps using
*IPv6* in IPv6 tunneling)" for SIIT, isn't it a single point of
failure?  So, is the observation (1) appropriate?

(Q2) Let's consider "a mechanism for allocating a temporary address
IPv4 and use IPv4 end to end when communicating with IPv4-only nodes"
in (2).

Suppose that we provide both "a mechanism for the IPv6-only node to
somehow acquire a temporary IPv4 address" and "a mechanism for
providing routing (perhaps using *IPv4* in IPv6 tunneling)" for this
mechanism.

In this case, is the observation (2) appropriate? I think this can
solve the routing problem described in (2).

--Kazu


From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 13 17:16:21 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25854
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jan 2000 17:16:19 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA28881;
	Thu, 13 Jan 2000 14:15:18 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA02757;
	Thu, 13 Jan 2000 14:14:50 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0DMDcJ01311
	for ngtrans-dist; Thu, 13 Jan 2000 14:13:38 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0DMDWw01304
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 14:13:32 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA14413
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 14:13:30 -0800 (PST)
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 OAA10322
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 14:13:29 -0800 (PST)
Received: from alderhill.wins.lbl.gov (alderhill) [128.3.9.220] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 128sUf-0004Sm-00; Thu, 13 Jan 2000 14:13:25 -0800
Message-Id: <4.2.2.20000113133800.00c63680@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Thu, 13 Jan 2000 14:13:07 -0800
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: Re: (ngtrans) When to put IPv6 addresses in the DNS
Cc: ngtrans@sunroof.eng.sun.com
In-Reply-To: <Roam.SIMC.2.0.6.944784085.18852.nordmark@jurassic>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_256393089==_.ALT"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bob Fink <fink@es.net>

--=====================_256393089==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Erik,

At 04:01 PM 12/9/99 -0800, Erik Nordmark wrote:

>Keith Moore has asked me to clarify when to put addresses
>in the DNS in the update to RFC 1933 (draft-ietf-ngtrans-mech-05.txt).
>This would be a very useful clarification.
>My current attempt (not yet submitted as an updated I-D) says:
>
>2.3.  Advertising Addresses in the DNS
>
>      There are some constraint place on the use of the DNS during
>      transition.  Most of these are obvious but are stated here for
>      completeness.
>
>      An A6/AAAA record for a node should not be added to the DNS until
>
>   1.    The address is assigned to the interface on the node.
>
>   2.    The address is configured on the interface.
>
>   3.    The interface is on a link which is connected to the IPv6
>         infrastructure.
>
>(Excuse the borken formatting.)
>The problem is with #3 as I and George discovered when discussing NAT-PT 
>in DC.
>I'd been under the impression that if you follow the above rules things would
>work. If an IPv6 host is isolated from an IPv6 perspective (e.g. it is not
>connected to the 6bone to take a concrete example) rule #3 would mean that it
>should not have an address in the DNS.
>
>This works great when other dual stack hosts tries to contact the isolated
>dual stack host. There is no IPv6 address in the DNS thus the peer doesn't 
>even
>try communicating using IPv6 but goes directly to IPv4 (we are assuming both
>hosts have A records in the DNS.)
>
>The suboptimal behavior occurs when the isolated host is doing the connect.
>It finds A6/AAAA records in the DNS for the peer and it has local IPv6
>addresses configured thus it will try to connect using IPv6.
>If it has no IPv6 route to the 6bone (e.g. because the local router
>was upgraded to advertise IPv6 addresses using Neighbor Discovery
>but that router doesn't have any IPv6 routes) this communication will
>fail. Typically this means a few minutes of delay as TCP times out.
>The TCP specification says that ICMP unreachable messages could be
>due to routing transients thus they should not immediately terminate
>the TCP connection. This means that the normal TCP timeout of a few minutes
>apply.
>Once TCP times out the application will presumably try the IPv4 addresses
>based on the A records in the DNS, but this will be painfully slow.
>
>What should we say in draft-ietf-ngtrans-mech?
>We should at least document the above issue.
>But is there some other advise or recommendation that makes sense?
>A possible but undesirable recommendation is:
>         Don't configure any routers to advertise any IPv6 prefixes in your
>         site until the site is connected to the *global IPv6 infrastructure*
>         (which I don't know what it is except possibly the 6bone) to ensure
>         that when the hosts find A6/AAAA records in the DNS they in fact
>         have an IPv6 path to communicate with those addresses.
>This is undesirable since it doesn't recommend users playing with IPv6
>internally in their site before they get external IPv6 communication.
>
>Any better suggestions?

In looking back over outstanding comments on MECH-05, I found this month 
old question you posed to the ngtrans list re Keith Moore's comments on 
when to put IPv6 addresses in the DNS. I think that we must resolve this in 
favour of the rules you suggest above, as it is key to our transition 
strategy. I.e., if you request a resource on the Internet, and it says it 
has a v6 address, and you have one as well, then you can use v6 to talk to 
it. So I am strongly in favour of these rules, and putting them quite 
explicitly into MECH.

As for your concern about experimenting with v6 on your site network when 
you have no external v6 connectivity, I want to take a simplistic view. 
That is, if one is experimenting with v6 prior to having any external 
connectivity, it is very unlikely you will do so on production server 
resources that are important or critical.

More likely, you will enable less critical systems with IPv6 and experiment 
to see how they work. In this case, it is very unlikely anyone externally 
will see the A6/AAAA entries for these systems (if you do choose to violate 
the rules above), and if someone does, and they suffer a delay, so what. 
They are local use systems under test, not critical resources.

I think that simply stating the issue, and its implications, is sufficient. 
So I would suggest and alternative to your "undesirable" paragraph to 
recognize this.

"A possible implication of the rules above is that, if one enables IPv6 on 
a node on a link without IPv6 infrastructure, and choose to add A6/AAAA 
records to the DNS for that node, then external IPv6 nodes that might see 
these A6/AAAA records will possibly try to reach that node using IPv6 and 
suffer delays due to unreachability. Thus it is recommended that either the 
rules be followed, or care be taken to only do so with nodes that will not 
be impacted by external accessing delays."

Between the 6bone and the upcoming ability to use "6to4", and a growing 
choice of production IPv6 network services, it doesn't seem very likely 
that a site will have much trouble connecting to external IPv6 
infrastructure when they so choose.

Anyway, it would be good to resolve this on the list prior to Adelaide and 
get RFC 1933 replaced at PS.


Thanks for bringing this up.

Bob


--=====================_256393089==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Erik,<br>
<br>
At 04:01 PM 12/9/99 -0800, Erik Nordmark wrote:<br>
<br>
<blockquote type=cite cite>Keith Moore has asked me to clarify when to
put addresses<br>
in the DNS in the update to RFC 1933
(draft-ietf-ngtrans-mech-05.txt).<br>
This would be a very useful clarification.<br>
My current attempt (not yet submitted as an updated I-D) says:<br>
<br>
2.3.&nbsp; Advertising Addresses in the DNS<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; There are some constraint place on the use of
the DNS during<br>
&nbsp;&nbsp;&nbsp;&nbsp; transition.&nbsp; Most of these are obvious but
are stated here for<br>
&nbsp;&nbsp;&nbsp;&nbsp; completeness.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; An A6/AAAA record for a node should not be added
to the DNS until<br>
<br>
&nbsp; 1.&nbsp;&nbsp;&nbsp; The address is assigned to the interface on
the node.<br>
<br>
&nbsp; 2.&nbsp;&nbsp;&nbsp; The address is configured on the
interface.<br>
<br>
&nbsp; 3.&nbsp;&nbsp;&nbsp; The interface is on a link which is connected
to the IPv6<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; infrastructure.<br>
<br>
(Excuse the borken formatting.)<br>
The problem is with #3 as I and George discovered when discussing NAT-PT
in DC.<br>
I'd been under the impression that if you follow the above rules things
would<br>
work. If an IPv6 host is isolated from an IPv6 perspective (e.g. it is
not <br>
connected to the 6bone to take a concrete example) rule #3 would mean
that it<br>
should not have an address in the DNS.<br>
<br>
This works great when other dual stack hosts tries to contact the
isolated<br>
dual stack host. There is no IPv6 address in the DNS thus the peer
doesn't even<br>
try communicating using IPv6 but goes directly to IPv4 (we are assuming
both<br>
hosts have A records in the DNS.)<br>
<br>
The suboptimal behavior occurs when the isolated host is doing the
connect.<br>
It finds A6/AAAA records in the DNS for the peer and it has local
IPv6<br>
addresses configured thus it will try to connect using IPv6.<br>
If it has no IPv6 route to the 6bone (e.g. because the local router<br>
was upgraded to advertise IPv6 addresses using Neighbor Discovery<br>
but that router doesn't have any IPv6 routes) this communication
will<br>
fail. Typically this means a few minutes of delay as TCP times out.<br>
The TCP specification says that ICMP unreachable messages could be<br>
due to routing transients thus they should not immediately 
terminate<br>
the TCP connection. This means that the normal TCP timeout of a few
minutes<br>
apply.<br>
Once TCP times out the application will presumably try the IPv4
addresses<br>
based on the A records in the DNS, but this will be painfully slow.<br>
<br>
What should we say in draft-ietf-ngtrans-mech?<br>
We should at least document the above issue.<br>
But is there some other advise or recommendation that makes sense?<br>
A possible but undesirable recommendation is: <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Don't
configure any routers to advertise any IPv6 prefixes in your <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>site until
the site is connected to the *global IPv6 infrastructure*<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>(which I
don't know what it is except possibly the 6bone) to ensure <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>that when
the hosts find A6/AAAA records in the DNS they in fact <br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>have an
IPv6 path to communicate with those addresses.<br>
This is undesirable since it doesn't recommend users playing with
IPv6<br>
internally in their site before they get external IPv6
communication.<br>
<br>
Any better suggestions?<br>
</blockquote><br>
In looking back over outstanding comments on MECH-05, I found this month
old question you posed to the ngtrans list re Keith Moore's comments on
when to put IPv6 addresses in the DNS. I think that we must resolve this
in favour of the rules you suggest above, as it is key to our transition
strategy. I.e., if you request a resource on the Internet, and it says it
has a v6 address, and you have one as well, then you can use v6 to talk
to it. So I am strongly in favour of these rules, and putting them quite
explicitly into MECH.<br>
<br>
As for your concern about experimenting with v6 on your site network when
you have no external v6 connectivity, I want to take a simplistic view.
That is, if one is experimenting with v6 prior to having any external
connectivity, it is very unlikely you will do so on production server
resources that are important or critical. <br>
<br>
More likely, you will enable less critical systems with IPv6 and
experiment to see how they work. In this case, it is very unlikely anyone
externally will see the A6/AAAA entries for these systems (if you do
choose to violate the rules above), and if someone does, and they suffer
a delay, so what. They are local use systems under test, not critical
resources. <br>
<br>
I think that simply stating the issue, and its implications, is
sufficient. So I would suggest and alternative to your
&quot;undesirable&quot; paragraph to recognize this.<br>
<br>
&quot;A possible implication of the rules above is that, if one enables
IPv6 on a node on a link without IPv6 infrastructure, and choose to add
A6/AAAA records to the DNS for that node, then external IPv6 nodes that
might see these A6/AAAA records will possibly try to reach that node
using IPv6 and suffer delays due to unreachability. Thus it is
recommended that either the rules be followed, or care be taken to only
do so with nodes that will not be impacted by external accessing
delays.&quot;<br>
<br>
Between the 6bone and the upcoming ability to use &quot;6to4&quot;, and a
growing choice of production IPv6 network services, it doesn't seem very
likely that a site will have much trouble connecting to external IPv6
infrastructure when they so choose. <br>
<br>
Anyway, it would be good to resolve this on the list prior to Adelaide
and get RFC 1933 replaced at PS.<br>
<br>
<br>
Thanks for bringing this up.<br>
<br>
Bob<br>
<br>
</html>

--=====================_256393089==_.ALT--



From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 13 20:26:23 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27001
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jan 2000 20:26:22 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA29156;
	Thu, 13 Jan 2000 17:25:07 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA18716;
	Thu, 13 Jan 2000 17:24:40 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0E1NMn01529
	for ngtrans-dist; Thu, 13 Jan 2000 17:23:22 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0E1NFw01518
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 17:23:15 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA18530;
	Thu, 13 Jan 2000 17:23:14 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA12491;
	Thu, 13 Jan 2000 18:23:13 -0700 (MST)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.8.7/8.8.6) id RAA27306;
	Thu, 13 Jan 2000 17:23:11 -0800 (PST)
From: Bill Manning <bmanning@ISI.EDU>
Message-Id: <200001140123.RAA27306@boreas.isi.edu>
Subject: Re: (ngtrans) When to put IPv6 addresses in the DNS
To: fink@es.net
Date: Thu, 13 Jan 100 17:23:11 -0800 (PST)
Cc: Erik.Nordmark@eng.sun.com, ngtrans@sunroof.eng.sun.com
In-Reply-To: <4.2.2.20000113133800.00c63680@imap2.es.net> from "Bob Fink" at Jan 13, 0 02:13:07 pm
X-Mailer: ELM [version 2.4 PL24 PGP6]
Content-Type: text
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Bill Manning <bmanning@ISI.EDU>

% 
% "A possible implication of the rules above is that, if one enables IPv6 on 
% a node on a link without IPv6 infrastructure, and choose to add A6/AAAA 
% records to the DNS for that node, then external IPv6 nodes that might see 
% these A6/AAAA records will possibly try to reach that node using IPv6 and 
% suffer delays due to unreachability. Thus it is recommended that either the 
% rules be followed, or care be taken to only do so with nodes that will not 
% be impacted by external accessing delays."


	This is exactly the problem seen today w/ IPv4 labels in the DNS.
	If its not there, then there will be the lookup delay before an
	alternate choice is taken. Granted that in the IPv4 only world, 
	the alternate choice is to report a failure. This will lead people
	to use literals or some splitDNS thing.

	I guess that I I see this as being a bit overbearing on how people
	may wish to do their implementation. Its really a local matter and
	IMHO, is overstating things to call them "rules".  It perhaps would
	be better phrased as, "a recommended procedure for when to add
	IPv6 data to the DNS".


... html cruft.... ick.

% 2.3.&nbsp; Advertising Addresses in the DNS<br>
% <br>
% &nbsp;&nbsp;&nbsp;&nbsp; There are some constraint place on the use of
% the DNS during<br>
% &nbsp;&nbsp;&nbsp;&nbsp; transition.&nbsp; Most of these are obvious but
% are stated here for<br>
% &nbsp;&nbsp;&nbsp;&nbsp; completeness.<br>
% <br>
% &nbsp;&nbsp;&nbsp;&nbsp; An A6/AAAA record for a node should not be added
% to the DNS until<br>
% <br>
% &nbsp; 1.&nbsp;&nbsp;&nbsp; The address is assigned to the interface on
% the node.<br>
% <br>
% &nbsp; 2.&nbsp;&nbsp;&nbsp; The address is configured on the
% interface.<br>
% <br>
% &nbsp; 3.&nbsp;&nbsp;&nbsp; The interface is on a link which is connected
% to the IPv6<br>
% &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; infrastructure.<br>
% <br>
% (Excuse the borken formatting.)<br>
% The problem is with #3 as I and George discovered when discussing NAT-PT
% in DC.<br>
% I'd been under the impression that if you follow the above rules things
% would<br>
% work. If an IPv6 host is isolated from an IPv6 perspective (e.g. it is
% not <br>
% connected to the 6bone to take a concrete example) rule #3 would mean
% that it<br>
% should not have an address in the DNS.<br>
% <br>
% This works great when other dual stack hosts tries to contact the
% isolated<br>
% dual stack host. There is no IPv6 address in the DNS thus the peer
% doesn't even<br>
% try communicating using IPv6 but goes directly to IPv4 (we are assuming
% both<br>
% hosts have A records in the DNS.)<br>
% <br>
% The suboptimal behavior occurs when the isolated host is doing the
% connect.<br>
% It finds A6/AAAA records in the DNS for the peer and it has local
% IPv6<br>
% addresses configured thus it will try to connect using IPv6.<br>
% If it has no IPv6 route to the 6bone (e.g. because the local router<br>
% was upgraded to advertise IPv6 addresses using Neighbor Discovery<br>
% but that router doesn't have any IPv6 routes) this communication
% will<br>
% fail. Typically this means a few minutes of delay as TCP times out.<br>
% The TCP specification says that ICMP unreachable messages could be<br>
% due to routing transients thus they should not immediately 
% terminate<br>
% the TCP connection. This means that the normal TCP timeout of a few
% minutes<br>
% apply.<br>
% Once TCP times out the application will presumably try the IPv4
% addresses<br>
% based on the A records in the DNS, but this will be painfully slow.<br>
% <br>
% What should we say in draft-ietf-ngtrans-mech?<br>
% We should at least document the above issue.<br>
% But is there some other advise or recommendation that makes sense?<br>
% A possible but undesirable recommendation is: <br>
% <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Don't
% configure any routers to advertise any IPv6 prefixes in your <br>
% <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>site until
% the site is connected to the *global IPv6 infrastructure*<br>
% <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>(which I
% don't know what it is except possibly the 6bone) to ensure <br>
% <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>that when
% the hosts find A6/AAAA records in the DNS they in fact <br>
% <x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>have an
% IPv6 path to communicate with those addresses.<br>
% This is undesirable since it doesn't recommend users playing with
% IPv6<br>
% internally in their site before they get external IPv6
% communication.<br>
% <br>
% Any better suggestions?<br>
% </blockquote><br>
% In looking back over outstanding comments on MECH-05, I found this month
% old question you posed to the ngtrans list re Keith Moore's comments on
% when to put IPv6 addresses in the DNS. I think that we must resolve this
% in favour of the rules you suggest above, as it is key to our transition
% strategy. I.e., if you request a resource on the Internet, and it says it
% has a v6 address, and you have one as well, then you can use v6 to talk
% to it. So I am strongly in favour of these rules, and putting them quite
% explicitly into MECH.<br>
% <br>
% As for your concern about experimenting with v6 on your site network when
% you have no external v6 connectivity, I want to take a simplistic view.
% That is, if one is experimenting with v6 prior to having any external
% connectivity, it is very unlikely you will do so on production server
% resources that are important or critical. <br>
% <br>
% More likely, you will enable less critical systems with IPv6 and
% experiment to see how they work. In this case, it is very unlikely anyone
% externally will see the A6/AAAA entries for these systems (if you do
% choose to violate the rules above), and if someone does, and they suffer
% a delay, so what. They are local use systems under test, not critical
% resources. <br>
% <br>
% I think that simply stating the issue, and its implications, is
% sufficient. So I would suggest and alternative to your
% &quot;undesirable&quot; paragraph to recognize this.<br>
% <br>
% &quot;A possible implication of the rules above is that, if one enables
% IPv6 on a node on a link without IPv6 infrastructure, and choose to add
% A6/AAAA records to the DNS for that node, then external IPv6 nodes that
% might see these A6/AAAA records will possibly try to reach that node
% using IPv6 and suffer delays due to unreachability. Thus it is
% recommended that either the rules be followed, or care be taken to only
% do so with nodes that will not be impacted by external accessing
% delays.&quot;<br>
% <br>
% Between the 6bone and the upcoming ability to use &quot;6to4&quot;, and a
% growing choice of production IPv6 network services, it doesn't seem very
% likely that a site will have much trouble connecting to external IPv6
% infrastructure when they so choose. <br>
% <br>
% Anyway, it would be good to resolve this on the list prior to Adelaide
% and get RFC 1933 replaced at PS.<br>
% <br>
% <br>
% Thanks for bringing this up.<br>
% <br>
% Bob<br>
% <br>
% </html>
% 
% --=====================_256393089==_.ALT--
% 
% 


-- 
--bill


From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 13 22:31:57 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 WAA29169
	for <ngtrans-archive@odin.ietf.org>; Thu, 13 Jan 2000 22:31:57 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA19741;
	Thu, 13 Jan 2000 20:31:13 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id TAA25419;
	Thu, 13 Jan 2000 19:30:46 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0E3TMw01706
	for ngtrans-dist; Thu, 13 Jan 2000 19:29:22 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0E3TEw01699
	for <ngtrans@sunroof.eng.sun.com>; Thu, 13 Jan 2000 19:29:14 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id TAA02717;
	Thu, 13 Jan 2000 19:29:12 -0800 (PST)
Date: Thu, 13 Jan 2000 19:29:10 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) When to put IPv6 addresses in the DNS
To: Bob Fink <fink@es.net>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, ngtrans@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <4.2.2.20000113133800.00c63680@imap2.es.net>
Message-ID: <Roam.SIMC.2.0.6.947820550.15368.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>


> I think that simply stating the issue, and its implications, is sufficient. 
> So I would suggest and alternative to your "undesirable" paragraph to 
> recognize this.
> 
> "A possible implication of the rules above is that, if one enables IPv6 on 
> a node on a link without IPv6 infrastructure, and choose to add A6/AAAA 
> records to the DNS for that node, then external IPv6 nodes that might see 
> these A6/AAAA records will possibly try to reach that node using IPv6 and 
> suffer delays due to unreachability. Thus it is recommended that either the 
> rules be followed, or care be taken to only do so with nodes that will not 
> be impacted by external accessing delays."

Sounds reasonable.
I'll edit it some to point out that the delay occurs only if the applications
fall back to using IPv4 when IPv6 communication can not be established.
If the applications don't do this fallback they will fail to communicate in
this case.

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Sat Jan 15 20:10:24 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15576
	for <ngtrans-archive@odin.ietf.org>; Sat, 15 Jan 2000 20:10:24 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA15275;
	Sat, 15 Jan 2000 17:09:16 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA24413;
	Sat, 15 Jan 2000 17:08:23 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0G17JV03702
	for ngtrans-dist; Sat, 15 Jan 2000 17:07:19 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0G17Bw03695
	for <ngtrans@sunroof.eng.sun.com>; Sat, 15 Jan 2000 17:07:11 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA11754
	for <ngtrans@sunroof.eng.sun.com>; Sat, 15 Jan 2000 17:07:11 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id SAA04980
	for <ngtrans@sunroof.eng.sun.com>; Sat, 15 Jan 2000 18:07:11 -0700 (MST)
Received: from alderhill.wins.lbl.gov (alderhill) [131.243.136.213] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 129e9t-0000KL-00; Sat, 15 Jan 2000 17:07:10 -0800
Message-Id: <4.2.2.20000115170522.00be4df0@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Sat, 15 Jan 2000 17:06:22 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) 6BONE Pre-Qualification for Address Prefix Allocation (6PAPA)
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>

INTERNET-DRAFT                                          Bob Fink, ESnet
January 10, 2000

          6BONE Pre-Qualification for Address Prefix Allocation (6PAPA)

                  <draft-ietf-ngtrans-6bone-6papa-01.txt>


Abstract

This memo describes how the 6bone may be used as a prequalification step
during the "bootstrap" phase of sub-TLA assignment by the Regional
Internet Registries (RIRs).


Status of this Memo

This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other groups
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and
may be updated, replaced, or obsoleted by other documents at any time.  It
is inappropriate to use Internet-Drafts as reference material or to cite
them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet Draft expires July 10, 2000.


Acknowledgements

Ideas in this draft are, in part, contributions of various IETF working
groups, the Regional Internet Registries, participants of the 6bone
testbed, and the worldwide IPv6 community.


Contents

Status of this Memo..........................................

Acknowledgements.............................................

1.  Introduction.............................................

2.  6BONE Prequalification for sub-TLAs......................

3.  Security Considerations..................................

4.  Change Log...............................................

REFERENCES...................................................

AUTHOR'S ADDRESS.............................................


1. Introduction

This memo describes how the 6bone is used as a prequalification step
during the "bootstrap" phase of sub-TLA assignment by the Regional
Internet Registries (RIRs). It is based on the following points.

1.1 The 6bone community represented the world-wide IPv6 operational
networking community as of early 1999, including all existing IPv6
providers and users in the world, operating under the only IPv6 address
allocation and authority in place at that time, i.e., the 3FFE::/16 TLA
allocation to the 6bone, documented in [6BONE-TLA].

1.2 The 6bone uses a well defined top level address structure called a
pseudo-TLA (pTLA), documented in [PSEUDO], that is delegated from its
3FFE::/16 allocation, that all top level 6BONE IPv6 transit providers use.

1.3 The 6bone process for allocation of pTLA-s is well defined in section
7 of [HARDEN] and is well accepted by the 6bone community.

1.4 The 6bone community as a whole is willing to provide their knowledge,
experience and opinions as part of a process to help "bootstrap" the sub-
TLA address allocation process for the RIRs.


2. 6BONE Prequalification for sub-TLAs

2.1 A sub-TLA requestor (sTR) places a sub-TLA request with the
appropriate RIR, per the RIR's own sub-TLA procedures, indicating that
they intend to use 6bone prequalification.

2.2 The sTR follows the published process for becoming a pTLA as
documented in Section 7 of [HARDEN]. (Note that [HARDEN] specifies the
minimum time from first joining the 6bone as an end-site network to
becoming a pTLA as 3 months.) Those pTLA allocations in effect prior to
[HARDEN], or its predecessor RFC2546, are considered to have met all
requirements for becoming a pTLA. However, 2.3 still applies.

2.3 An sTR must have operated as a pTLA for at least 3 months, with at
least 3 active delegations under its pTLA (either lower level transits or
end-sites, or a mix of both), for the sTR to meet the 6bone experience
criterion (6EC).

2.4 A 6bone steering group (6SG), consisting of 3-5 persons established
by 6bone participant consensus, uses factual operational information and
other relevant experience of the sTR to determine if the 6EC has been met.
It is expected that the 6SG will respond within 30 days. It is up to the
RIR's own policies and procedures to determine what happens if this time
is not met.

2.5 After allocation of a sub-TLA to the sTR (by an RIR), the sTR may
optionally renumber from the 6bone pTLA prefix to the new sub-TLA prefix,
or continue to use their pTLA for multihoming purposes. If the pTLA space
becomes over subscribed, the most likely networks to be asked to surrender
a pTLA would be those holding production TLA/sub-TLA prefix space.
Given the large size of the pTLA space this is not considered likely to
ever happen.


3.  Security Considerations

There are no security considerations of this document as it only specifies
a process of recommendations made to IPv6 Address Registries for
prequalification for production IPv6 Address Prefix allocations.


4.  Change Log

Changes since version -00 of the draft:

Various rewordings for clarity.

Replace [RFC 2546] references with new HARDEN specification now
approved as Informational RFC.

Notes that pTLAs prior to [HARDEN] and RFC 2546 are legitimate pTLAs,
though still 3 months of oeprating experience with at leasts 3
delegations.

Removal of the previous 2.2 requirement that the sTR notifies the 6bone
list of intent to use the 6PP.

In previous 2.4 (now 2.3) clarifies that it is 6bone experience criteria
that is being met by the sTR for operating for 3 months.

The new 2.4 specifies a 6SG maximum response interval of 30 days, with the
RIR being responsible for deciding what to do when this time is exceeded.

Removal of any mention or implication that the 6bone community us stating
that an sTR is qualified for a sub-TLA allocation.

Removal of previous 2.6 regarding time out issues.

Removal of section 3. Only meaningful removal was regarding some pTLA-s
not qualifying for this process due to the nature of there network.
This had been regarded as unfair and unreasonable and there was general
agreement to remove this.


REFERENCES

[KEYWORDS] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997.

[6BONE-TLA] R. Hinden, R. Fink, J. Postel, "IPv6 Testing Address
Allocation", RFC 2471, December 1998.

[PSEUDO] R. Fink, "6bone pTLA & pNLA Formats", see <http://6bone.net>,
January, 2000.

[HARDEN] R. Rockell, R. Fink, "6Bone Backbone Routing Guidelines",
RFC xxxx, December 1999. Replaces RFC 2546.


AUTHOR'S ADDRESS

         Bob Fink, ESnet
         Lawrence Berkeley National Lab
         MS 50A-3111
         1 Cyclotron Road
         Berkeley, CA 94720
         USA

         phone: +1 510 486 5692
         fax:   +1 510 486 4790
         email: fink@es.net

-end



From owner-ngtrans@sunroof.eng.sun.com  Mon Jan 17 14:52: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 OAA07587
	for <ngtrans-archive@odin.ietf.org>; Mon, 17 Jan 2000 14:52:32 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA10175;
	Mon, 17 Jan 2000 12:51:32 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA25265;
	Mon, 17 Jan 2000 11:51:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0HJo8g08757
	for ngtrans-dist; Mon, 17 Jan 2000 11:50:08 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0HJo1w08750
	for <ngtrans@sunroof.eng.sun.com>; Mon, 17 Jan 2000 11:50:01 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA25124;
	Mon, 17 Jan 2000 11:50:00 -0800 (PST)
Received: from front4.grolier.fr (front4.grolier.fr [194.158.96.54])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA00472;
	Mon, 17 Jan 2000 11:49:59 -0800 (PST)
Received: from sardine (ppp-214-188.kd.club-internet.fr [195.36.214.188])
	by front4.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id UAA14950;
	Mon, 17 Jan 2000 20:49:53 +0100 (MET)
Message-Id: <4.2.2.20000117124053.00af1d70@brahma.imag.fr>
X-Sender: durand@brahma.imag.fr
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Mon, 17 Jan 2000 12:46:16 +1030
To: Bill Manning <bmanning@ISI.EDU>, fink@es.net
From: Alain Durand <Alain.Durand@imag.fr>
Subject: Re: (ngtrans) When to put IPv6 addresses in the DNS
Cc: Erik.Nordmark@eng.sun.com, ngtrans@sunroof.eng.sun.com
In-Reply-To: <200001140123.RAA27306@boreas.isi.edu>
References: <4.2.2.20000113133800.00c63680@imap2.es.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Alain Durand <Alain.Durand@imag.fr>

At 17:23 13/01/00 -0800, Bill Manning wrote:

>         I guess that I I see this as being a bit overbearing on how people
>         may wish to do their implementation. Its really a local matter and
>         IMHO, is overstating things to call them "rules".  It perhaps would
>         be better phrased as, "a recommended procedure for when to add
>         IPv6 data to the DNS".

I agree.
If people want to put stupid things in their DNS, they'll suffer the costs.
This will not impact the Internet at large.
I don't think we can mandate to put only smart entries in their DNS,
we can only recommend that.

         - Alain.



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 06:10: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 GAA25653
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 06:10:28 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA27756;
	Wed, 19 Jan 2000 04:09:54 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA20863;
	Wed, 19 Jan 2000 03:08:26 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JB7Xp10506
	for ngtrans-dist; Wed, 19 Jan 2000 03:07:33 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JB59p10490;
	Wed, 19 Jan 2000 03:05:09 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA11120;
	Wed, 19 Jan 2000 03:05:08 -0800 (PST)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA26465;
	Wed, 19 Jan 2000 04:05:07 -0700 (MST)
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 UAA13720;
	Wed, 19 Jan 2000 20:05:06 +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 UAA00634; Wed, 19 Jan 2000 20:05:06 +0900 (JST)
Received: from iijlab.net (mine.iij.ad.jp [192.168.10.205]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with SMTP id UAA19238; Wed, 19 Jan 2000 20:05:05 +0900 (JST)
Date: Wed, 19 Jan 2000 20:04:56 +0900 (JST)
Message-Id: <20000119.200456.23033996.kazu@iijlab.net>
To: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: (ngtrans) filtering against IPv6 in IPv4
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.95b17 on Emacs 20.5 / Mule 4.0 (HANANOEN)
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

Hi all,

Some ISPs configure IP filters NOT to forward "IPv6 in IPv4" packets.
This is obstacles for transition from IPv4 to IPv6.

Are there any activities in IETF to recommend ISPs not to filter "IPv6
in IPv4" packets? (e.g. IAB recommendation)

--Kazu


From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 09:55:52 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00029
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 09:55:52 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA06948;
	Wed, 19 Jan 2000 06:54:51 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id GAA24447;
	Wed, 19 Jan 2000 06:54:19 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JEqlI10687
	for ngtrans-dist; Wed, 19 Jan 2000 06:52:47 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JEoGp10671;
	Wed, 19 Jan 2000 06:50:16 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id GAA02737;
	Wed, 19 Jan 2000 06:50:17 -0800 (PST)
Received: from mailext03.compaq.com (mailext03.compaq.com [207.18.199.41])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA21580;
	Wed, 19 Jan 2000 06:50:16 -0800 (PST)
Received: by mailext03.compaq.com (Postfix, from userid 12345)
	id F02D715212C; Wed, 19 Jan 2000 08:50:15 -0600 (CST)
Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35])
	by mailext03.compaq.com (Postfix) with ESMTP
	id E6172148506; Wed, 19 Jan 2000 08:50:15 -0600 (CST)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345)
	id 49A07BC4D2; Wed, 19 Jan 2000 08:50:08 -0600 (CST)
Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP
	id D30A1B2A42; Wed, 19 Jan 2000 08:50:07 -0600 (CST)
Received: from localhost by quarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id JAA0000031970; Wed, 19 Jan 2000 09:50:14 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200001191450.JAA0000031970@quarry.zk3.dec.com>
To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
Cc: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4 
In-reply-to: Your message of "Wed, 19 Jan 2000 20:04:56 +0900."
             <20000119.200456.23033996.kazu@iijlab.net> 
Date: Wed, 19 Jan 2000 09:50:14 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

we should take this to the IPv6 Forum too.  Many of the ISPs are members of
the Forum.  I will send a note to the Forum.  But I agree this would be
a good statement from the IAB.

/jim


From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 10:02:53 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00259
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 10:02:52 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA10105;
	Wed, 19 Jan 2000 07:01:55 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA20554;
	Wed, 19 Jan 2000 07:01:28 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JF0df10739
	for ngtrans-dist; Wed, 19 Jan 2000 07:00:39 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JF0Rp10732
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 07:00:27 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA01738
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 07:00:28 -0800 (PST)
Received: from newdev.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA13404
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 08:00:27 -0700 (MST)
Received: (from sob@localhost)
	by newdev.harvard.edu (8.9.3/8.9.3) id KAA14620
	for ngtrans@sunroof.eng.sun.com; Wed, 19 Jan 2000 10:00:21 -0500 (EST)
Date: Wed, 19 Jan 2000 10:00:21 -0500 (EST)
From: Scott Bradner <sob@harvard.edu>
Message-Id: <200001191500.KAA14620@newdev.harvard.edu>
To: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Scott Bradner <sob@harvard.edu>


the statement has been made that ISPs are filtering to block IPv6 in
IPv4 traffic - I have not heard of such a thing (and in general ISPs do
not do this sort of filtering due to the perfoe`rmance impact on their
routers) - does anyone have specific informatyion information on what
ISPs are said to be doing this and why they might want to (since there is no
ISP operational reason to do this)

Scott


From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 10:49:15 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00985
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 10:49:13 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA29360;
	Wed, 19 Jan 2000 07:48:01 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA06115;
	Wed, 19 Jan 2000 07:47:47 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JFkdG10851
	for ngtrans-dist; Wed, 19 Jan 2000 07:46:39 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JFkXp10844
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 07:46:33 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA06035
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 07:46:34 -0800 (PST)
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 HAA19727
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 07:46:33 -0800 (PST)
Received: from rasp2-52.lbl.gov (alderhill) [131.243.212.152] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12AxJY-0001su-00; Wed, 19 Jan 2000 07:46:32 -0800
Message-Id: <4.2.2.20000119074203.00cfc750@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Wed, 19 Jan 2000 07:43:11 -0800
To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) <kazu@iijlab.net>
From: Bob Fink <fink@es.net>
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
Cc: ngtrans@sunroof.eng.sun.com
In-Reply-To: <20000119.200456.23033996.kazu@iijlab.net>
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>

Kazu,

At 08:04 PM 1/19/00 +0900, =?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?= wrote:
 >Hi all,
 >
 >Some ISPs configure IP filters NOT to forward "IPv6 in IPv4" packets.
 >This is obstacles for transition from IPv4 to IPv6.
 >
 >Are there any activities in IETF to recommend ISPs not to filter "IPv6
 >in IPv4" packets? (e.g. IAB recommendation)


If you can point me to folk that really do this, I will try to dissaude them.

As for IETF policy recommendations or such, none that I know of.


Bob



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 11:11:03 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01272
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 11:10:58 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA09362;
	Wed, 19 Jan 2000 08:09:53 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA08879;
	Wed, 19 Jan 2000 08:08:32 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JG73r10877
	for ngtrans-dist; Wed, 19 Jan 2000 08:07:03 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JG6vp10870
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 08:06:57 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA10923
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 08:06:57 -0800 (PST)
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 IAA02169
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 08:06:56 -0800 (PST)
Received: from rasp2-52.lbl.gov (alderhill) [131.243.212.152] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12AxdB-00029K-00; Wed, 19 Jan 2000 08:06:50 -0800
Message-Id: <4.2.2.20000119080448.00afff00@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Wed, 19 Jan 2000 08:05:41 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) An IPv6-to-IPv4 transport relay translator
Cc: Alain Durand <Alain.Durand@imag.fr>, Tony Hain <tonyhain@microsoft.com>,
        Bert Wijnen <WIJNEN@VNET.IBM.COM>, 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>

NGtrans folk,

Jun-ichiro itojun Hagino has requested that we start a new project on a 
TCP/UDP (transport) Relay Translator. Below is the draft as submitted to 
the I-D editor.

There is no determination yet of the destination status of this document 
(info, standard or experimental) so please comment on this as well.

Comments to the ngtrans list please.


Thanks,

Bob

===
 >Abstract
 >
 >The document describes an IPv6-to-IPv4 transport relay translator.  It
 >enables an IPv6-only node to exchange TCP or UDP traffic with IPv4-only
 >nodes.  A transport relay translator box, which sits in the middle, will
 >take care of the protocol translation.
 >
 >The draft talks about how we can implement a transport relay translator
 >box.  The draft is about how you can use existing technologies, and it
 >does not define any new protocols.

	Bob Fink (ngtrans chair) suggested draft-ietf-ngtrans-tcpudp-relay-NN
	as filename, so the attached version reflects that.  Thanks.

itojun

========================================================================
Internet Engineering Task Force                 Jun-ichiro itojun Hagino
INTERNET-DRAFT                                         Research Lab, IIJ
Expires: July 16, 2000                                     Kazu Yamamoto
                                                        Research Lab, IIJ
                                                         January 16, 2000


                An IPv6-to-IPv4 transport relay translator
                  draft-ietf-ngtrans-tcpudp-relay-00.txt

Status of this Memo


This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.

Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups.  Note that other groups
may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time.  It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as ``work in progress.''

To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.

Distribution of this memo is unlimited.

The internet-draft will expire in 6 months.  The date of expiration will
be July 16, 2000.


Abstract

The document describes an IPv6-to-IPv4 transport relay translator.  It
enables an IPv6-only node to exchange TCP or UDP traffic with IPv4-only
nodes.  A transport relay translator box, which sits in the middle, will
take care of the protocol translation.

The draft talks about how we can implement a transport relay translator
box.  The draft is about how you can use existing technologies, and it
does not define any new protocols.


1.  Problem domain

When you deploy an IPv6-only network, you still want to be able to
access IPv4-only network resources outside, like IPv4-only web servers.
To support such a configuration, many IPv6-to-IPv4 translation
technologies are proposed, mainly in the IETF ngtrans working group.


Hagino                   Expires: July 16, 2000                 [Page 1]

DRAFT              v6-to-v4 transport relay translator      January 2000

The document solves the same problem as other translation technologies
solve, but based on transport relay technique.

The list of advantages and disadvantages of the technique is as follows:

o  A transport relay translator is designed to require no extra
    configuration or requirement on IPv6-only originating nodes, nor
    IPv4-only destination nodes.  Some other translation mechanisms need
    extra configuration on IPv6-only originating nodes, limiting
    possibility of deployment.

o  If you perform an IPv6-to-IPv4 header translation, you will need a
    great care about path MTU and fragmentation issues.  If we relay TCP
    traffic by transport relay boxes, we do not need to care about path
    MTU nor fragmentation issues.

o  A transport relay supports connected bidirectional traffic only.  An
    IPv6-to-IPv4 header translator may be able to support other cases,
    such as unidirectional multicast datagrams, as well.

o  Transport relay needs a stateful translator box between the
    communicating peers, just like NAT boxes.  While it is possible to
    place multiple translator boxes in a site (see section on operational
    experiences), a transport layer connection will go through
    particular, single translator box.  Therefore, the traslator box can
    be considered a single point of failure, again like NAT boxes.  Some
    other mechanisms, such as SIIT [Nordmark, 1999] , use stateless
    translator boxes.  With stateless translator boxes, you do not have a
    single point of failure.

The document assumes that connections are originated at IPv6 node
destined to IPv4 node.  The document can be extended to handle opposite
direction, if an apprpriate address mapping mechanism is introduced.


2.  IPv4-to-IPv4 transport relay

To help understanding of the proposal in the next section, here we
describe transparent transport relay in general.  The transport relay
technique itself is not new, as it has been used in many of firewall-
related products.


2.1.  Transparent TCP relay

Transparent TCP relay devices have been used in firewall-related
products.  These products are designed to achieve the follwing goals:
(1) disallow forwarding of IP packet across the device, (2) while
allowing TCP or UDP traffic to go through, indirectly, across the
device.  For example, consider a network constructed like the following
diagram.  ``TCP relay box'' in the diagram does not forward IP packet
across inner to outer network.  It only relays TCP traffic on specific


Hagino                   Expires: July 16, 2000                 [Page 2]

DRAFT              v6-to-v4 transport relay translator      January 2000

port, from inner network side to outer network side.  (Note: The diagram
has only two subnets, one for inner and one for outer.  Actually both
side can be more complex, and there can be as many subnets and routers
as you wish)

      destination node
        |X
      ==+=======+== outer network
                |Y
              TCP relay box
                |B
      ==+=======+== inner network
        |A
      originating node


When originating node (IP address is A) tries to make a TCP connection
to destination node (X), TCP packets will be routed toward TCP relay box
based on routing decision.  TCP relay box will receive and accept the
packet, even though TCP relay box does not own the destination IP
address (X).  TCP relay box pretends to having IP address X, and
establishes TCP connection with the originating node as X.  TCP relay
box will then make a separate TCP connection, from Y to X, and relay
traffic from A to X, and the other way around.

Therefore, there will be two TCP connections in the picture: from A to B
(as X), and Y to X, like below:

      originating node (A) --> TCP relay box (as X, interface is B)
          address on IP header: A -> X
      TCP relay box (Y) --> destination node (X)
          address on IP header: Y -> X


TCP relay box needs to capture some of TCP packets that is not destined
to its address.  The way to do it is implementation specific.


2.2.  Transparent UDP relay

If you can recognize UDP inbound and outbound traffic pair in some way
UDP relay can be implemented in similar manner as TCP relay.  An
implementation can recognize UDP traffic pair like NAT boxes does, by
recording address/port pairs onto an table and managing table entries by
using timeouts.


3.  IPv6-to-IPv4 transport relay translator

We propose a transport relay box with IPv6-to-IPv4 protocol translation,
which we call ``translator box'' in the document.  In the following
description TCP relay with IPv6-to-IPv4 translation is described.  UDP


Hagino                   Expires: July 16, 2000                 [Page 3]

DRAFT              v6-to-v4 transport relay translator      January 2000

relay can be implemented in similar manner.

For address translation, we will reserve an IPv6 prefix referred to by
C6::/64.  Routing information must be configured so that it will be
routed toward translator box.  The following diagram shows the network
configuration.  The subnet marked as ``dummy prefix'' does not actually
exist.  Also, now we assume that the originating node to be IPv6-only,
and the destination node to be IPv4-only.

      destination node
        |X4
      ==+=======+== outer network
                |Y4
              translator box --- dummy prefix (C6::/64)
                |B6
      ==+=======+== inner network
        |A6
      originating node


When the originating node (IPv6 address is A6) wishes to make a
connection to the destination node (IPv4 address is X4), it needs to
make a IPv6 TCP connection toward C6::X4.  If C4::/64 equals to
fec0:0:0:1::/64, and X4 equals to 10.1.1.1, the destination address to
be used is fec0:0:0:1::10.1.1.1.  The packet will be routed toward
translator box, and will be captured by translator box.  Translator box
will accept the IPv6 TCP connection between A6 and C6::X4, and
communicate with originating node, using IPv6 TCP.  Then, translator box
will look at the lowermost 32bit of the destination address (IPv6
address C6::X4) to get the real IPv4 destination (IPv4 address X4).  It
will make a IPv4 TCP connection from Y4 to X4, and forward traffic
across two TCP connections.

There will be two TCP connections, one is IPv6 TCP and another is IPv4
TCP, in the picture: from A6 to B6 (as C6::X4), and Y4 to X4, like
below:

      IPv6 TCP: originating node (A6)
              --> translator box (as C6::X4, interface is B6)
          address on IPv6 header: A6 -> C6::X4
      IPv4 TCP: translator box (Y4) --> destination node (X4)
          address on IPv4 header: Y4 -> X4



4.  Address mapping

As seen in the previous section, originating node must use special form
of IPv6 address to connect to IPv4 destination node.  The special form
can be resolved from hostname by static address mapping table on the
originating node (like /etc/hosts in UNIX), special DNS server
implementation, or modified DNS resolver implementation on originating


Hagino                   Expires: July 16, 2000                 [Page 4]

DRAFT              v6-to-v4 transport relay translator      January 2000

node.


5.  Notes to implementers

UDP relay translator may need to care about path MTU issues and
fragmentation issues.

Though the translator box only relays TCP or UDP traffic, it needs to
check ICMPv6 packets destined to C6::X4 as well, so that it can
recognize path MTU discovery messsages and other notifications.

When forwarding TCP traffic, the translator box needs to handle urgent
data [Postel, 1981] carefully.

To relay NAT-unfriendly protocols such as FTP [Postel, 1985] the
translator box needs to modify data content.

Scalability issues must carefully be considered when you deploy
translator box to a large IPv6 site.  Scalability parameters would be
(1) number of connections the operating system kernel can accept, (2)
number of connections a userland process can forward (equals to number
of filehandles per process), and (3) number of transport relaying
processes on a box.  Design decision must be made to use proper number
of userland processes to support proper number of connections.

To make TCP relay translator more scalable when you install it to a
large site, it is possible to have multiple translator boxes in a site.
This can be done by taking the following steps: (1) configure multiple
translator boxes, (2) configure different dummy prefix to them, (3a) and
let the originating node pick a dummy prefix randomly for load-
balancing.  If you install special DNS server to the site, you may (3b)
configure DNS servers differently to return different dummy prefixes and
tell originating nodes of different DNS servers, or (3c) let DNS server
pick a dummy prefix randomly for load-balancing.  This is possible
because you will not be changing destination address (hence the
translator box), once a TCP connection is established.

For address mapping, the authors recommend use of a special DNS server
for large-scale installation, and static mapping for small-scale
installation.  It is not always possible to have special resolver on the
originating node, and assuming it would cause a deployment problem.


6.  Operational experiences

WIDE KAME IPv6 stack implements the tecnique as ``FAITH'' IPv6-to-IPv4
TCP relay translator implementation.  The implementation came from WIDE
Hydrangea IPv6 stack, which is one of ancestors of the KAME IPv6 stack.

The FAITH code has been available and operational for more than 3 years.
The implementation has been used at WIDE research group offsite meeting,


Hagino                   Expires: July 16, 2000                 [Page 5]

DRAFT              v6-to-v4 transport relay translator      January 2000

and IETF ipngwg 1999 Tokyo interim meeting.  At the latter occasion, we
configured IPv6-only terminal network cluster just like we do in IETF
meetings, and used translator box to support more than 100 IPv6 nodes on
the meeting network to connect to outside IPv4 nodes.  From statistics
we gathered, SSH, FTP, HTTP, and POP3 are the most popular protocol we
have relayed.

Source code is available as free software, bundled in the KAME IPv6
stack kit.

Special DNS server implementations are available as ``newbie'' DNS
server implementation by Yusuke Doi, and ``totd'' DNS proxy server from
University of Tromso (Norway).

7.  Security considerations

The document describes transport relay box used for IPv6-to-IPv4
protocol translation.  The authors believe that there is no new security
risk introduced by this draft.

Malicious IPv6 node may try to use translator box for anonymizing the
source IP address of traffic to IPv4 destinations.  A translator box
should implement some sort of access control to avoid such improper
usage.

Careless transport relay implementation may subject to buffer overflow
attack, but this kind of issue is implementation issue, not the document
issue.


References

Nordmark, 1999.
Erik Nordmark, "Stateless IP/ICMP Translator (SIIT)" in draft-ietf-
ngtrans-siit-06.txt (June 24, 1999). work in progress material.

Postel, 1981.
J. Postel, "Transmission Control Protocol" in RFC793 (Sep 1, 1981).
ftp://ftp.isi.edu/in-notes/rfc793.txt.

Postel, 1985.
J. Postel and J.K. Reynolds, "File Transfer Protocol" in RFC959 (Oct 1,
1985). ftp://ftp.isi.edu/in-notes/rfc959.txt.


Acknowledgements

The authors would like to thank people who were involved in implementing
KAME FAITH translator code, including Kei-ichi Shima and Munechika
Sumikawa.




Hagino                   Expires: July 16, 2000                 [Page 6]

DRAFT              v6-to-v4 transport relay translator      January 2000

Author's address

      Jun-ichiro itojun Hagino
      Research Laboratory, Internet Initiative Japan Inc.
      Takebashi Yasuda Bldg.,
      3-13 Kanda Nishiki-cho,
      Chiyoda-ku,Tokyo 101-0054, JAPAN
      Tel: +81-3-5259-6350
      Fax: +81-3-5259-6351
      email: itojun@iijlab.net

      Kazu Yamamoto
      Research Laboratory, Internet Initiative Japan Inc.
      (see above for address and phone #)
      email: kazu@iijlab.net







































Hagino                   Expires: July 16, 2000                 [Page 7]



From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 14:23:03 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03969
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 14:23:00 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA08106;
	Wed, 19 Jan 2000 11:22:10 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA24102;
	Wed, 19 Jan 2000 11:20:39 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JJJCf11437
	for ngtrans-dist; Wed, 19 Jan 2000 11:19:12 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JJJ5p11430
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 11:19:06 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id LAA18958
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 11:19:05 -0800 (PST)
Received: from roam.psg.com (mg130-116.ricochet.net [204.179.130.116])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA00886
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 11:18:59 -0800 (PST)
Received: from randy by roam.psg.com with local (Exim 3.12 #1)
	id 12B0d8-00029K-00; Wed, 19 Jan 2000 11:18:58 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Scott Bradner <sob@harvard.edu>
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
References: <200001191500.KAA14620@newdev.harvard.edu>
Message-Id: <E12B0d8-00029K-00@roam.psg.com>
Date: Wed, 19 Jan 2000 11:18:58 -0800
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

> the statement has been made that ISPs are filtering to block IPv6 in
> IPv4 traffic

we have this bit of hysteria every six months.  it has yet to be true.

randy


From owner-ngtrans@sunroof.eng.sun.com  Wed Jan 19 18:58: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 SAA06599
	for <ngtrans-archive@odin.ietf.org>; Wed, 19 Jan 2000 18:58:00 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA00698;
	Wed, 19 Jan 2000 16:57:16 -0700 (MST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id PAA20689;
	Wed, 19 Jan 2000 15:57:01 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0JNthk11771
	for ngtrans-dist; Wed, 19 Jan 2000 15:55:44 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0JNtYp11764
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 15:55:34 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id PAA23833
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 15:55:35 -0800 (PST)
Received: from mail1.es.net (mail1.es.net [198.128.3.181])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id QAA14683
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 16:21:34 -0700 (MST)
Received: from alderhill.wins.lbl.gov (alderhill) [128.3.9.226] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12B4Pq-0007O8-00; Wed, 19 Jan 2000 15:21:31 -0800
Message-Id: <4.2.2.20000119151354.00bc1440@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Wed, 19 Jan 2000 15:18:17 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) dates for IESG processing of ngtrans drafts pre-Adelaide
Cc: Tony Hain <tonyhain@microsoft.com>, Alain Durand <Alain.Durand@imag.fr>,
        Bob Fink <fink@es.net>
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>

NGtrans Editors,

Those of you wishing to get your documents processed prior to Adelaide 
should be aware of the dates below.

I believe this applies to:

MECH - Nordmark
SOCKS- Kitamura
TRANSLATOR - Kazu
BROKER - Guardini

Thanks,

your co-chairs (Tony, Alain and Bob)


============================================
From: Thomas Narten <narten@raleigh.ibm.com>
Subject: Timetable for IESG action before Adelaide
Date: Mon, 17 Jan 2000 14:21:56 -0500

Looking at the calendar, we're rapidly running out of time to get
things through the IESG before Adelaide.  Taking the date of the last
IESG telechat and working backwards from there, important dates are:

ID cutoff:		       March 10	
Last IESG telechat:	       March 9
AD asks to put on IESG agenda: March 1
IETF Last Call starts:	       February 16
IETF Last Call starts (safer): February 2

Note that the February 2 target is much safer, as it allows time for
reissuing a document if there are comments (either Last Call or from
the IESG), takes into account a key person who may be traveling, etc.

We eagerly await requests for document advancement!!!

Thomas & Erik



From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 20 07:02:06 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25270
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 07:02:06 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA25191;
	Thu, 20 Jan 2000 04:01:14 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id EAA21537;
	Thu, 20 Jan 2000 04:00:26 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0KBx1H12203
	for ngtrans-dist; Thu, 20 Jan 2000 03:59:01 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0KBwnp12195
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:49 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA00664
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:48 -0800 (PST)
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 DAA03873
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:47 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25079;
	Thu, 20 Jan 2000 06:58:46 -0500 (EST)
Message-Id: <200001201158.GAA25079@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-tcpudp-relay-00.txt
Date: Thu, 20 Jan 2000 06:58:45 -0500
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		: An IPv6-to-IPv4 transport relay translator
	Author(s)	: J. Hagino, K. Yamamoto	
        Filename	: draft-ietf-ngtrans-tcpudp-relay-00.txt
	Pages		: 7
	Date		: 19-Jan-00
	
The document describes an IPv6-to-IPv4 transport relay translator.  It
enables an IPv6-only node to exchange TCP or UDP traffic with IPv4-only
nodes.  A transport relay translator box, which sits in the middle, will
take care of the protocol translation.

The draft talks about how we can implement a transport relay translator
box.  The draft is about how you can use existing technologies, and it
does not define any new protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-tcpudp-relay-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-ietf-ngtrans-tcpudp-relay-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-ietf-ngtrans-tcpudp-relay-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:	<20000119140722.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-tcpudp-relay-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 20 07:02:27 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25292
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 07:02:26 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA25192;
	Thu, 20 Jan 2000 04:01:14 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id EAA21539;
	Thu, 20 Jan 2000 04:00:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0KBwu712202
	for ngtrans-dist; Thu, 20 Jan 2000 03:58:56 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0KBwip12187
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:44 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA15334
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:43 -0800 (PST)
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 DAA03847
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 03:58:42 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25063;
	Thu, 20 Jan 2000 06:58:41 -0500 (EST)
Message-Id: <200001201158.GAA25063@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-6papa-01.txt
Date: Thu, 20 Jan 2000 06:58:41 -0500
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		: 6BONE Pre-Qualification for Address Prefix Allocation 
                          (6PAPA)
 	Author(s)	: B. Fink
	Filename	: draft-ietf-ngtrans-6bone-6papa-01.txt
	Pages		: 4
	Date		: 19-Jan-00
	
This memo describes how the 6bone may be used as a prequalification step
during the 'bootstrap' phase of sub-TLA assignment by the Regional
Internet Registries (RIRs).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ngtrans-6bone-6papa-01.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-6papa-01.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-6papa-01.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:	<20000119140713.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-6bone-6papa-01.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 20 12:40:40 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08960
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 12:40:39 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA25622;
	Thu, 20 Jan 2000 09:39:44 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id JAA20358;
	Thu, 20 Jan 2000 09:39:20 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0KHbsK12401
	for ngtrans-dist; Thu, 20 Jan 2000 09:37:54 -0800 (PST)
Received: from stinker.eng.sun.com (stinker [129.146.86.121])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0KHbop12394
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 09:37:50 -0800 (PST)
Received: (from jrh@localhost)
	by stinker.eng.sun.com (8.9.3+Sun/8.9.3) id JAA09740
	for ngtrans@sunroof.eng.sun.com; Thu, 20 Jan 2000 09:36:41 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0K68Qp12043
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 22:08:26 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id WAA04448
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 22:08:26 -0800 (PST)
Received: from orange.kame.net (orange.kame.net [203.178.141.194])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA25576
	for <ngtrans@sunroof.eng.sun.com>; Wed, 19 Jan 2000 23:08:24 -0700 (MST)
Received: from localhost (kame217.kame.net [203.178.141.217])
	by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id PAA16167;
	Thu, 20 Jan 2000 15:08:20 +0900 (JST)
To: sob@harvard.edu
Cc: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
In-Reply-To: <200001191500.KAA14620@newdev.harvard.edu>
References: <200001191500.KAA14620@newdev.harvard.edu>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000120150858D.shin@nd.net.fujitsu.co.jp>
Date: Thu, 20 Jan 2000 15:08:58 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 36
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Content-Transfer-Encoding: 7bit

> the statement has been made that ISPs are filtering to block IPv6 in
> IPv4 traffic - I have not heard of such a thing (and in general ISPs do
> not do this sort of filtering due to the perfoe`rmance impact on their
> routers) - does anyone have specific informatyion information on what
> ISPs are said to be doing this and why they might want to (since there is no
> ISP operational reason to do this)
> 
> Scott

I received reports that some ISPs are filtering IPv6 over
IPv4, but I don't think they are specifically or intentionally
filtering it.
They would be just passing some specific well knonwn protocols
for security reason, and other packets like IPv6 over IPv4 is
just filtered as the result.
So actually this is not an IPv6 only issue. I also received
same kind of report that mobile-ip packets are filtered by
some ISP.

Also, those filtering seems to be done at dial-up access
points, so performance issue won't be so significant.

I don't think we should check and make the name of such ISPs
public in this stage, but we should annouce the possibility of
such problem widely, and let ISPs notice that they might be
doing such kind of filtering, and prompt them to check the
current filtering configuration and let them alter it if it
has any problem. (e.g. If they are filtering packets such as
IPv6 over IPv4.)

And if there are still problems after such announcement, then
I think we need to enumerate specific names of such ISPs.


Yoshinobu Inoue
KAME project



From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 20 20:53:30 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18082
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 20:53:30 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA21382;
	Thu, 20 Jan 2000 17:51:59 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA00876;
	Thu, 20 Jan 2000 17:51:37 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0L1oLL12921
	for ngtrans-dist; Thu, 20 Jan 2000 17:50:21 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0L1oEp12914
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 17:50:14 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA13171
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 17:50:14 -0800 (PST)
Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA23831
	for <ngtrans@sunroof.eng.sun.com>; Thu, 20 Jan 2000 18:50:13 -0700 (MST)
Received: by mailext04.compaq.com (Postfix, from userid 12345)
	id 24E3C104C94; Thu, 20 Jan 2000 19:50:13 -0600 (CST)
Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35])
	by mailext04.compaq.com (Postfix) with ESMTP
	id 1A1FFFB101; Thu, 20 Jan 2000 19:50:13 -0600 (CST)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345)
	id 7408ABC4CA; Thu, 20 Jan 2000 19:50:05 -0600 (CST)
Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP
	id F3863B2A43; Thu, 20 Jan 2000 19:50:04 -0600 (CST)
Received: from localhost by quarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id UAA0000016006; Thu, 20 Jan 2000 20:50:11 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200001210150.UAA0000016006@quarry.zk3.dec.com>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
Cc: sob@harvard.edu, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4 
In-reply-to: Your message of "Thu, 20 Jan 2000 15:08:58 +0900."
             <20000120150858D.shin@nd.net.fujitsu.co.jp> 
Date: Thu, 20 Jan 2000 20:50:11 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

very good point.  on not naming any ISPs.  this should not be a witch
hunt but a means to let folks know that we want to encap IPv6 via
proto-id 41.  I also would guess its not intentional but rather a
screening of proto-ids that are yeah or nay.

/jim  


From owner-ngtrans@sunroof.eng.sun.com  Thu Jan 20 21:12:53 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18309
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 21:12:46 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA25798;
	Thu, 20 Jan 2000 18:11:20 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id SAA16509;
	Thu, 20 Jan 2000 18:11:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0L29uF12965
	for ngtrans-dist; Thu, 20 Jan 2000 18:09:56 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0L29np12958;
	Thu, 20 Jan 2000 18:09:49 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id SAA00819;
	Thu, 20 Jan 2000 18:09:49 -0800 (PST)
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 SAA21322;
	Thu, 20 Jan 2000 18:09:47 -0800 (PST)
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 CAA81004; Fri, 21 Jan 2000 02:09:46 GMT
Received: from hursley.ibm.com (lig32-225-4-86.us.lig-dial.ibm.com [32.225.4.86]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id CAA21854; Fri, 21 Jan 2000 02:09:42 GMT
Message-ID: <3887015C.36EA0323@hursley.ibm.com>
Date: Thu, 20 Jan 2000 06:36:44 -0600
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: Kazu@hursley.ibm.com, Yamamoto@hursley.ibm.com
CC: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com
Subject: (ngtrans) Re: filtering against IPv6 in IPv4
References: <20000119.200456.23033996.kazu@iijlab.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

This is not the sort of thing that the IAB can meaningfully recommend. 
It needs customer demand.

I suspect that this is not anti-IPv6 discrimination; more likely they
are filtering all protocol types except a few.

   Brian

"Kazu Yamamoto ($B;3K\OBI'(B)" wrote:
> 
> Hi all,
> 
> Some ISPs configure IP filters NOT to forward "IPv6 in IPv4" packets.
> This is obstacles for transition from IPv4 to IPv6.
> 
> Are there any activities in IETF to recommend ISPs not to filter "IPv6
> in IPv4" packets? (e.g. IAB recommendation)
> 
> --Kazu
> --------------------------------------------------------------------
> 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 Jan 20 22:00:09 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19553
	for <ngtrans-archive@odin.ietf.org>; Thu, 20 Jan 2000 22:00:05 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA05178;
	Thu, 20 Jan 2000 18:58:27 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id SAA22019;
	Thu, 20 Jan 2000 18:58:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) id e0L2vJv13193
	for ngtrans-dist; Thu, 20 Jan 2000 18:57:19 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta11+Sun/8.10.0.Beta11) with ESMTP id e0L2sqp13174;
	Thu, 20 Jan 2000 18:54:53 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id SAA21554;
	Thu, 20 Jan 2000 18:54:53 -0800 (PST)
Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA13259;
	Thu, 20 Jan 2000 19:54:52 -0700 (MST)
Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345)
	id 5E7BA18C; Thu, 20 Jan 2000 21:54:51 -0500 (EST)
Received: from quarry.zk3.dec.com (quarry.zk3.dec.com [16.140.16.3])
	by zmamail02.zma.compaq.com (Postfix) with ESMTP
	id 3A84C208; Thu, 20 Jan 2000 21:54:51 -0500 (EST)
Received: from localhost by quarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id VAA0000028789; Thu, 20 Jan 2000 21:54:50 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200001210254.VAA0000028789@quarry.zk3.dec.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: Kazu@hursley.ibm.com, Yamamoto@hursley.ibm.com,
        ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com,
        bound@zk3.dec.com
Subject: Re: (ngtrans) Re: filtering against IPv6 in IPv4 
In-reply-to: Your message of "Thu, 20 Jan 2000 06:36:44 CST."
             <3887015C.36EA0323@hursley.ibm.com> 
Date: Thu, 20 Jan 2000 21:54:50 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>


>This is not the sort of thing that the IAB can meaningfully recommend. 
>It needs customer demand.

I can see that good point.  In fact the IETF really can't do anything
about it nor should they.  Now that I think about it.

The IPv6 Forum can help resolve this.                 

>I suspect that this is not anti-IPv6 discrimination; more likely they
>are filtering all protocol types except a few.

thats what I think too.

/jim


From owner-ngtrans@sunroof.eng.sun.com  Sat Jan 22 19:44:58 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12619
	for <ngtrans-archive@odin.ietf.org>; Sat, 22 Jan 2000 19:44:57 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA19926;
	Sat, 22 Jan 2000 16:43:58 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA07655;
	Sat, 22 Jan 2000 16:43:22 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0N0gGX14508
	for ngtrans-dist; Sat, 22 Jan 2000 16:42:16 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0N0g8j14501
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jan 2000 16:42:08 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA11909
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jan 2000 16:42:08 -0800 (PST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA21638
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jan 2000 16:42:06 -0800 (PST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id AD28E1E00E4; Sat, 22 Jan 2000 19:42:05 -0500 (EST)
To: Randy Bush <randy@psg.com>
Cc: Scott Bradner <sob@harvard.edu>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
References: <200001191500.KAA14620@newdev.harvard.edu> <E12B0d8-00029K-00@roam.psg.com>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 22 Jan 2000 19:42:05 -0500
In-Reply-To: Randy Bush's message of "Wed, 19 Jan 2000 11:18:58 -0800"
Message-ID: <87puutvcte.fsf@snark.piermont.com>
Lines: 11
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Perry E. Metzger" <perry@piermont.com>


Randy Bush <randy@psg.com> writes:
> > the statement has been made that ISPs are filtering to block IPv6 in
> > IPv4 traffic
> 
> we have this bit of hysteria every six months.  it has yet to be true.

It is, however, the case that people behind NATs have a hard time
running v6 in v4. A v6 in UDP in v4 protocol would help with that.

Perry


From owner-ngtrans@sunroof.eng.sun.com  Sun Jan 23 02:34:10 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29372
	for <ngtrans-archive@odin.ietf.org>; Sun, 23 Jan 2000 02:34:09 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA06248;
	Sat, 22 Jan 2000 23:33:27 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id XAA20258;
	Sat, 22 Jan 2000 23:33:11 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0N7W2D14593
	for ngtrans-dist; Sat, 22 Jan 2000 23:32:02 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0N7Vsj14586
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jan 2000 23:31:54 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id XAA20241
	for <ngtrans@sunroof.eng.sun.com>; Sat, 22 Jan 2000 23:31:49 -0800 (PST)
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 AAA18837
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Jan 2000 00:31:49 -0700 (MST)
Received: from randy by rip.psg.com with local (Exim 3.12 #1)
	id 12CHUp-000KdT-00; Sat, 22 Jan 2000 23:31:39 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Perry E. Metzger" <perry@piermont.com>
Cc: Scott Bradner <sob@harvard.edu>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
References: <200001191500.KAA14620@newdev.harvard.edu>
	<E12B0d8-00029K-00@roam.psg.com>
	<87puutvcte.fsf@snark.piermont.com>
Message-Id: <E12CHUp-000KdT-00@rip.psg.com>
Date: Sat, 22 Jan 2000 23:31:39 -0800
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Randy Bush <randy@psg.com>
Content-Transfer-Encoding: 7bit

>>> the statement has been made that ISPs are filtering to block IPv6 in
>>> IPv4 traffic
>> we have this bit of hysteria every six months.  it has yet to be true.
> It is, however, the case that people behind NATs have a hard time
> running v6 in v4. A v6 in UDP in v4 protocol would help with that.

funny, i somehow misread the statement to be about ISPs filtering.  silly
and irrelevant me.

randy


From owner-ngtrans@sunroof.eng.sun.com  Sun Jan 23 16:07:57 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11723
	for <ngtrans-archive@odin.ietf.org>; Sun, 23 Jan 2000 16:07:57 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA13769;
	Sun, 23 Jan 2000 13:07:04 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id NAA20780;
	Sun, 23 Jan 2000 13:06:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0NL5IG14818
	for ngtrans-dist; Sun, 23 Jan 2000 13:05:18 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0NL5Cj14811
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Jan 2000 13:05:12 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id NAA23317
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Jan 2000 13:05:10 -0800 (PST)
Received: from snark.piermont.com (snark.piermont.com [206.1.51.10])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA05294
	for <ngtrans@sunroof.eng.sun.com>; Sun, 23 Jan 2000 13:05:09 -0800 (PST)
Received: by snark.piermont.com (Postfix, from userid 1000)
	id D69611E00E4; Sun, 23 Jan 2000 16:05:04 -0500 (EST)
To: Randy Bush <randy@psg.com>
Cc: Scott Bradner <sob@harvard.edu>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
References: <200001191500.KAA14620@newdev.harvard.edu> 	<E12B0d8-00029K-00@roam.psg.com> 	<87puutvcte.fsf@snark.piermont.com> <E12CHUp-000KdT-00@rip.psg.com>
From: "Perry E. Metzger" <perry@piermont.com>
Date: 23 Jan 2000 16:05:04 -0500
In-Reply-To: Randy Bush's message of "Sat, 22 Jan 2000 23:31:39 -0800"
Message-ID: <87iu0k33en.fsf@snark.piermont.com>
Lines: 19
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Perry E. Metzger" <perry@piermont.com>


Randy Bush <randy@psg.com> writes:
> >>> the statement has been made that ISPs are filtering to block IPv6 in
> >>> IPv4 traffic
> >> we have this bit of hysteria every six months.  it has yet to be true.
> > It is, however, the case that people behind NATs have a hard time
> > running v6 in v4. A v6 in UDP in v4 protocol would help with that.
> 
> funny, i somehow misread the statement to be about ISPs filtering.

It was. There are ISPs using NAT these days. Even without filtering,
those users do have some issues that ngtrans could help smooth
out. You might think this is irrelevant, but I don't, given that this
is the ngtrans mailing list...

-- 
Perry Metzger		perry@piermont.com
--
"Ask not what your country can force other people to do for you..."


From owner-ngtrans@sunroof.eng.sun.com  Mon Jan 24 11:57:30 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14198
	for <ngtrans-archive@odin.ietf.org>; Mon, 24 Jan 2000 11:57:28 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA21476;
	Mon, 24 Jan 2000 08:55:57 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA21345;
	Mon, 24 Jan 2000 08:00:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0OFwax15192
	for ngtrans-dist; Mon, 24 Jan 2000 07:58:36 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0OFwQj15185
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jan 2000 07:58:27 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA09581
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jan 2000 07:58:27 -0800 (PST)
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 HAA06505
	for <ngtrans@sunroof.eng.sun.com>; Mon, 24 Jan 2000 07:58:25 -0800 (PST)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id JAA13261;
	Mon, 24 Jan 2000 09:58:23 -0600 (CST)
Message-Id: <200001241558.JAA13261@gungnir.fnal.gov>
To: Randy Bush <randy@psg.com>
Cc: ngtrans@sunroof.eng.sun.com
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: (ngtrans) filtering against IPv6 in IPv4 
In-reply-to: Your message of Sat, 22 Jan 2000 23:31:39 PST.
             <E12CHUp-000KdT-00@rip.psg.com> 
Date: Mon, 24 Jan 2000 09:58:23 -0600
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Matt Crawford" <crawdad@fnal.gov>

> >>> the statement has been made that ISPs are filtering to block IPv6 in
> >>> IPv4 traffic
> >> we have this bit of hysteria every six months.  it has yet to be true.
> > It is, however, the case that people behind NATs have a hard time
> > running v6 in v4. A v6 in UDP in v4 protocol would help with that.
> funny, i somehow misread the statement to be about ISPs filtering.  silly
> and irrelevant me.

Not quite irrelevant.  Often it's the ISP who imposes the use of NAT.


From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 25 17:59:33 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09150
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jan 2000 17:59:31 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA06019;
	Tue, 25 Jan 2000 14:58:44 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id OAA08096;
	Tue, 25 Jan 2000 14:58:13 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0PMuoI16519
	for ngtrans-dist; Tue, 25 Jan 2000 14:56:50 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0PMugj16512;
	Tue, 25 Jan 2000 14:56:42 -0800 (PST)
Received: from bobo (bobo.Eng.Sun.COM [129.146.86.130])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id OAA12404;
	Tue, 25 Jan 2000 14:56:42 -0800 (PST)
Date: Tue, 25 Jan 2000 14:56:42 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: (ngtrans) Use of IP6.INT
To: ipngwg@sunroof.eng.sun.com
Cc: Erik.Nordmark@eng.sun.com, ngtrans@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <Roam.SIMC.2.0.6.947830379.9759.nordmark@jurassic>
Message-ID: <Roam.SIMC.2.0.6.948841002.12374.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>


Please followup on the ipngwg list only.

There has been some discussion for a while in the IAB and IESG about the
use of .INT. Since this is assigned to ITU to do assignments for
international (treaty?) organizations it is clear that the IETF should
not use .INT for any future use.

The question on the table is whether or not we should switch IP6.INT
to be somewhere else. I'd like to understand the implications of
doing such a switch and in particular it it can be piggy-backed on
the transition from AAAA to A6, DNAME, and binary labels.

There seems to be consensus that .arpa would be a good place to put
things like the IPv6 reverse tree since it already contains
the IPv4 reverse tree. If we go this path we should presumably invent a new
meaning for .arpa. So far I've seen two good suggestions:
	Address Reversing Pointer Access
	Address and Routing Parameters Area

Thus ip6.arpa (or in6-addr.arpa if you want it to be closer to in-addr.arpa)
could be a reasonable domain to use.


Transition:
Looking at the draft-ietf-ipngwg-dns-lookups draft and the binary 
labels RFC (RFC 2673) there already seems to be a transition for 
reverse lookups, althought it isn't explicitly mentioned in dns-lookups draft.

The old AAAA spec says to look in IP6.INT by making a (text) label out of each
nibble and reversing the order.
In the new dns-lookups spec says to look in IP6.INT for a binary label 
consisting of the whole IPv6 address. This can be viewed as 128 one bit 
labels in reverse order. Note that RFC 2673 clearly says that a binary label 
never matches an ASCII label "0" and "1".
Thus for transition purposes it seems like the reverse lookup, just like 
the forward lookup trying A6 and AAAA in some order,  need to try two
different lookups in some order.

Thus it might be realatively painless to make the new way also look in
a different place; such as ip6.arpa instead of ip6.int.


Comments?
   Erik



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 25 18:05:05 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09306
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jan 2000 18:05:04 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA08449;
	Tue, 25 Jan 2000 15:03:54 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id PAA20438;
	Tue, 25 Jan 2000 15:03:40 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0PN2ax16544
	for ngtrans-dist; Tue, 25 Jan 2000 15:02:36 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.88.31])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0PN2Mj16537;
	Tue, 25 Jan 2000 15:02:23 -0800 (PST)
Received: from bobo (bobo.Eng.Sun.COM [129.146.86.130])
	by jurassic.eng.sun.com (8.9.3+Sun/8.9.3) with SMTP id PAA13527;
	Tue, 25 Jan 2000 15:02:23 -0800 (PST)
Date: Tue, 25 Jan 2000 15:02:23 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: (ngtrans) Use of IP6.INT
To: ipng@sunroof.eng.sun.com
Cc: ngtrans@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <Roam.SIMC.2.0.6.948841002.12374.nordmark@jurassic>
Message-ID: <Roam.SIMC.2.0.6.948841343.11986.nordmark@jurassic>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Erik Nordmark <Erik.Nordmark@eng.sun.com>

[Retransmitted with correct email for the ipng list.]

Please followup on the ipng list only.

There has been some discussion for a while in the IAB and IESG about the
use of .INT. Since this is assigned to ITU to do assignments for
international (treaty?) organizations it is clear that the IETF should
not use .INT for any future use.

The question on the table is whether or not we should switch IP6.INT
to be somewhere else. I'd like to understand the implications of
doing such a switch and in particular it it can be piggy-backed on
the transition from AAAA to A6, DNAME, and binary labels.

There seems to be consensus that .arpa would be a good place to put
things like the IPv6 reverse tree since it already contains
the IPv4 reverse tree. If we go this path we should presumably invent a new
meaning for .arpa. So far I've seen two good suggestions:
	Address Reversing Pointer Access
	Address and Routing Parameters Area

Thus ip6.arpa (or in6-addr.arpa if you want it to be closer to in-addr.arpa)
could be a reasonable domain to use.


Transition:
Looking at the draft-ietf-ipngwg-dns-lookups draft and the binary 
labels RFC (RFC 2673) there already seems to be a transition for 
reverse lookups, althought it isn't explicitly mentioned in dns-lookups draft.

The old AAAA spec says to look in IP6.INT by making a (text) label out of each
nibble and reversing the order.
In the new dns-lookups spec says to look in IP6.INT for a binary label 
consisting of the whole IPv6 address. This can be viewed as 128 one bit 
labels in reverse order. Note that RFC 2673 clearly says that a binary label 
never matches an ASCII label "0" and "1".
Thus for transition purposes it seems like the reverse lookup, just like 
the forward lookup trying A6 and AAAA in some order,  need to try two
different lookups in some order.

Thus it might be realatively painless to make the new way also look in
a different place; such as ip6.arpa instead of ip6.int.


Comments?
   Erik



From owner-ngtrans@sunroof.eng.sun.com  Tue Jan 25 19:29:45 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10921
	for <ngtrans-archive@odin.ietf.org>; Tue, 25 Jan 2000 19:29:44 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA12441;
	Tue, 25 Jan 2000 16:29:00 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA27119;
	Tue, 25 Jan 2000 16:28:35 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0Q0RD816687
	for ngtrans-dist; Tue, 25 Jan 2000 16:27:13 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0Q0R6j16680;
	Tue, 25 Jan 2000 16:27:06 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id QAA10415;
	Tue, 25 Jan 2000 16:27:05 -0800 (PST)
Received: from postoffice.cisco.com (postoffice.cisco.com [171.69.198.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA08031;
	Tue, 25 Jan 2000 17:27:04 -0700 (MST)
Received: from [171.71.38.63] (deering-office-mac.cisco.com [171.71.38.63]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id QAA20322; Tue, 25 Jan 2000 16:26:26 -0800 (PST)
Mime-Version: 1.0
X-Sender: deering@postoffice
Message-Id: <v04220809b4b02279b64f@[10.19.130.188]>
Date: Tue, 25 Jan 2000 16:26:24 -0800
To: Anne Lord <anne@apnic.net>, ipv6-registry@apnic.net
From: Steve Deering <deering@cisco.com>
Subject: (ngtrans) Re: IPv6 Policy Document Review - Call for comments
Cc: ipng@sunroof.eng.sun.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>

Anne et al,

Here are some comments on the Provisional IPv6 Assignment and Allocation
Policy Document from the co-chairs of the IPng and NGTrans Working Groups.
We very much appreciate your invitation for us to review the document.

Let us first note that we are delighted that the IPv6 address allocation
and assignment process has begun and seems to be functioning smoothly.
The establishment of such a process was a critical requirement for
production deployment of IPv6, and we would like to say thanks to you
and your colleagues in the RIRs for all the work you have done to get
the process up and running.

Let us also point out that these comments are not based on us being
customers of the allocation process -- we hope that those ISPs who have
been allocated IPv6 address space under the existing process will
separately comment on any difficulties they may have encountered or any
suggestions for improvement they might have.  Rather, these comments
are based on our knowledge of the design goals and technical
requirements of IPv6 addressing and our concerns about some potential
negative consequences of the current allocation policy.

Our primary concern with the current document is that it stresses
unnecessary address conservation in a number of places, and in ways
that are contrary to the intent of the protocol design.  Specifically:

    (1) The third paragraph of section 4.3.1, regarding dial-up lines,
	is apparently motivated by a desire to conserve address space.
	Unfortunately, it is ambiguous and contradictory, and depending
	on how it is interpreted, it could impose an unnecessary and
	potentially harmful constraint on IPv6 address allocation to
	customer sites.

	      o It is ambiguous because it seems to equate dial-up
		access with single-user access, while clearly those
		properties are distinct:  a single dial-up line may
		well serve multiple users.  And why is the number of
		users relevant to IP address allocation?  A single user
		with multiple IP devices requires more IP addresses
		than multiple users sharing a single device.

	      o It is contradictory because a dial-up customer (e.g., a
		residential or small-office customer) who has a need to
		create subnets is intended to receive a /48, according
		to the first paragraph of that section, and a longer
		prefix than /48, according to the third paragraph.
		
	      o It is unnecessary because the size of the public
		topology part of the IPv6 address was explicitly chosen
		to be far more than enough to hierarchically assign a
		unique TLA+NLA (i.e., a unique /48) to every enterprise
		and every household in the world, for the foreseeable
		future and beyond, regardless of their type of access
		technology.  We took into consideration the possibility
		that all dial-up users would one day migrate to always-
		on access, and we sized the public topology part of the
		IPv6 address accordingly.  Thus there is no need to
		share a /48 among multiple customers, whether they use
		dial-up access or not.

	      o It is potentially harmful because if ISPs interpret the
		policy to mean they should assign only a single /64 to
		each dial-up customer, given that at least some and
		possibly many dial-up customers will have a need to
		create subnets, we will almost certainly see one or both
		of the following harmful developments:

		      - subdivision of the customer's 64-bit interface
			ID field into a subnet ID field and a smaller
			interface ID field, which would defeat the IPv6
			goals of stateless address autoconfiguration and
			topologically-independent, globally-unique node
			identification that are achieved through the use
			of EUI-64-based interface IDs.

		      - deployment of IPv6 NAT devices to allow the
			customer to have multiple /64 subnets behind
			a single /64 allocation, which would defeat the
			IPv6 goal of having a single, global address
			space for all IPv6 devices.

	Therefore, we recommend that the third paragraph of section 4.3.1
	be deleted from the document, and that it be made clear to the
	RIRs and ISPs that it is perfectly legitimate and desirable that
	every end-user customer, including dial-up and residential
	customers, be assigned a static, unique /48 IPv6 address prefix.


    (2) The last paragraph of section 3.2, regarding address assignment
	to point-to-point links, also seems to be motivated by the desire
	to conserve address space.  The recommendation against ISPs
	assigning global, public addresses to routers' point-to-point
	interfaces is both unnecessary and inappropriate.

	      o It is unnecessary because it would have negligible impact
		on address space consumption if each ISP were to set aside
		one of its allocated NLA values (i.e., one /48), from
		which to assign global /64 prefixes to each of its point-
		to-point links.  The IPv6 address space is, by design, big
		enough to allow all Internet device interfaces, including
		those of ISPs' routers, to have globally-unique, publicly
		visible addresses.

	      o It is inappropriate because it is beyond the RIRs' mandate
		to determine that ISPs' router interfaces "do not require
		public address space".  An ISP might well choose to assign
		global addresses to its point-to-point interfaces, for
		example to permit inter-ISP traceroute to work properly,
		and the RIRs have no business interfering in that
		operational decision.

	Therefore, we recommend that the last paragraph of section 3.2
	be deleted.  (However, the parenthetical comment at the end of
	that paragraph, concerning the validity of all 1s and all 0s
	field values, should be retained somewhere, or be promoted to
	being a paragraph of its own).

    (3) Though the document does not explicitly say so, a number of
	readers have interpreted the description of the slow-start
	mechanism in section 4.2.4 to mean that an ISP will normally
	start with a /35 allocation and then, as its IPv6 customer
	base grows, be required to come back to its RIR for each
	additional bit of address space, i.e., first for the enclosing
	/34, then for the enclosing /33, and so on, up to the sub-TLA
	allocation of /29.  While that might be a reasonable approach
	if we were trying to force the ISPs to achieve maximal density
	of address usage, such aggressive address conservation is
	explicitly not a goal of the IPv6 allocation policy, and if it
	were in fact to be implemented that way, it would impose an
	unnecessary and undesirable burden on ISPs.  For example, while
	an ISP might reasonably do flat routing for its first 6500 NLAs
	(80% of the NLAs in the initial /35), if it expected to enjoy
	any significant further growth, the next sensible step would be
	for it to establish an internal hierarchy for its subsequent NLA
	assignments.  However, obtaining only a single bit of additional
	address space would not allow for any sort of long-term hierarchy
	to be established.  Instead, we suggest that a reasonable
	expectation for any ISP that appears at all likely to grow into a
	full sub-TLA, and eventually a TLA, should be that they go from
	a /35 initial allocation to a /29 full sub-TLA allocation in one
	step.  We do not believe this would be inconsistent with the
	purposes of slow start for IPv6 address allocation, which we
	understand to be:

	      o prevention of flagrant wastage or stockpiling of IPv6
		address space,

	      o arranging that ISPs with significantly fewer customers
		have longer prefixes than others, and

	      o forcing occasions for ISPs to receive guidance from
		their RIRs on acceptable address usage practices.

	Now perhaps our suggested approach is in fact what you have in
	mind -- we note that the document gives considerable (and
	sensible) flexibility for the RIRs to exercise their best
	judgement regarding how much additional space to grant.  If that
	is the intent (and we hope it is), we would prefer that that be
	made much more explicit in the policy document, so that any
	legitimate ISP with serious plans for a large IPv6 deployment
	can know that it will not be subjected to many small "baby-step"
	allocations that would complicate its planning and possibly
	force it to impose otherwise unnecessary renumbering events
	on its earlier customers.

	We also suggest that you consider changing the criteria so
	that existing top-level IPv4 ISPs who already have a large
	installed infrastructure and IPv4 customer base, and who
	presumably require less guidance on prudent address allocation
	practices, be able to obtain a full /29 sub-TLA to start, rather
	than being required to slow start from a /35.  Yes, that creates
	the risk of such an ISP obtaining a lot of IPv6 space and then
	never using it, but (a) the requirement that ISPs report their
	NLA allocations in a public database provides a separate
	mechanism for monitoring usage, and that could be used as input
	to a reclamation decision, should that become necessary, and
	(b) if existing large IPv4 ISPs fail to eventually acquire a
	significant number of IPv6 customers, that will almost certainly
	indicate an overall lack of demand for IPv6 service, in which
	case the issue of IPv6 address stockpiling will have become moot.

    (4) The very few words in the document regarding allocation of TLAs
	("If no further growth is possible within that sub-TLA range,
	the Regional IR may allocate a full TLA.", in section 4.2.5.1),
	when read in the context of the other, unnecessary address
	conservation requirements above, give the impression that the
	RIRs will be very reluctant to allocate actual TLAs.  In
	particular:

	      o Why does it say "...*may* allocate a full TLA", rather
		than "...*will* allocate a full TLA" (or "...*will
		normally* allocate a full TLA", to allow for exceptions)?

	      o What is the criterion for determining that "no further
		growth is possible" with a sub-TLA?  The only reference
		to determining when a piece of address space is "full"
		is in the section on sub-TLA allocation, section 4.2.5,
		in which there is an "at least 80% used" requirement.
		That is a reasonable threshold for determining when
		a flat address space, or a single field of a
		hierarchical address (such as the 13-bit NLA field in
		an initial /35 allocation, handled as a flat space),
		is near capacity, but it is unreasonable and unachievable
		in practice in a hierarchically-structured address space
		(such as the 19-bit NLA space in a full sub-TLA).

	We recommend that the criteria for obtaining a TLA be made more
	explicit, and we suggest that you consider a metric such as the
	"H ratio" defined in RFC 1715, which takes into account the
	significantly reduced density achievable in a hierarchical
	address space.  For example, specifying an H ratio of 0.26,
	which that RFC describes as "optimistic" based on past
	experience with other, similar address spaces, would yield a
	recommendation that an ISP be granted a TLA at the point that
	it has allocated about 87,000 NLA values to end-user customers
	and/or downstream ISPs.  Perhaps you could round that number down
	to 75,000 or up to 100,000 to come up with a simple rule for when
	an ISP could expect to acquire a TLA.


Our remaining comments, both substantive and editorial, are given below,
following quotations of the relevant text:

> ABSTRACT
>
> This document describes the registry system for distributing
> globally unique unicast IPv6 address space.

Append to the end of that sentence: "under format prefix 001, as defined
in RFC 2374", to make it clear that this policy does not necessarily
apply to any future global unicast space that might be created under
other format prefixes.

>                                               IPv6 address
> space is distributed in a hierarchical manner (as is IPv4
> address space), managed by the IANA and further delegated by
> the Regional Internet Registries (Regional IRs) as described
> in RFC 1881. In the case of IPv6, the Regional IRs allocate
> Top-Level Aggregation Identifiers (TLAs) to organizations,
> which, as TLA Registries, in turn allocate or assign address
> space to other Internet Service Providers (ISPs) and end
> users. ISPs then serve as Next Level Aggregation (NLA)
> Registries for their customers.

The use of the terms "TLA Registry" and "NLA Registry" above, and
throughout the document, are inconsistent and often counter-intuitive.
For example, the above paragraph uses:

      - "TLA Registry" to refer to an organization to whom a TLA value
	has been assigned, but

      - "NLA Registry" to refer to an organization that assigns NLA
	values to others.

We suggest that you consistently use:

      - TLA Registry only to refer to those organization that assign
	TLA and sub-TLA values, i.e., IANA, the RIRs, and  subordinate
	registries (like JPNIC), if any.

      - NLA Registry only to refer to those organizations that assign
	NLA values, i.e., ISPs and Exchanges, and their subordinate
	ISPs, if any.

      - SLA Registry only to refer to those organizations that assign
	SLA values, i.e., end-user customers (and ISPs, for their own
	infrastructure).

> 2 IPv6 ADDRESS SPACE AND THE INTERNET REGISTRY SYSTEM
>
> IPv6 unicast addresses are aggregatable with contiguous
> bit-wise masks used to define routable prefixes,...

The reference to "contiguous bit-wise masks" is obsolete and
inapplicable to IPv6.  In IPv6, prefixes are always specified by
length (number of bits), never by mask.

>...using a method similar to that used for IPv4 addresses under CIDR.

The method of aggregation is not just "similar" to that used for IPv4
under CIDR, it is the same.

> Internet. The Internet Registry system exists to ensure that
> IPv6 address space is managed in a globally consistent,
> fair, and responsible manner that minimizes wastage, and
> maximizes aggregation within the routing structure.

The goal is not to *minimize* wastage, nor is it to *maximize*
aggregation.  Rather, the goal is to *limit* wastage, and to achieve
*adequate* aggregation to meet the demands of stable, global routing.

> 2.1 The Internet Registry System Hierarchy
>
> The hierarchical Internet Registry system exists to enable
> the goals described in this document to be met. In the case
> of IPv6, this hierarchy consists of the following levels, as
> seen from the top down: IANA, Regional Internet Registries,
> TLA, NLA Registries, and end-sites.

Following our suggestion above for consistent usage of terms, remove
"TLA," from the last sentence above.  (IANA and the RIRs are the TLA
registries.)  And if you disagree with that, then at least add the word
"Registries" after "TLA", for grammatical consistency.

> 2.1.3 TLA Registries
>
> TLA Registries are established under the authority of the
> appropriate Regional IR to enable "custodianship" of a TLA
> or sub-TLA block of IPv6 addresses.

Following our terminology suggestion, this section would refer to NLA
registries having custodianship over blocks of NLAs (that fall under
specific TLA or sub-TLA values assigned by the RIRs), and the subsequent
(currently empty) section 2.1.4 would be deleted.

We would also like to see this same language about custodianship
applied to the RIRs themselves, so that it is made clear the RIRs are
also custodians, not owners, of the address space (blocks of TLAs and
sub-TLAs) allocated to them by IANA.

> 2.1.5 End-sites
>
> [to be written]

We assume the points to be made here are that:

	- end-site customers are not granted "ownership" of the
	  address space they are assigned.

	- end-site customers are responsible for assigning SLA IDs
	  (subnet numbers) and interface IDs to their own links and
	  nodes.

> 2.2.1 Uniqueness
>
> Each IPv6 unicast address must be globally unique.

After "unicast address", add the phrase "under format prefix 001",
because the statement above is not true of *all* IPv6 unicast addresses
(particularly site-local, link-local, and loopback unicast addresses).

> This is an absolute requirement for guaranteeing that every host
>on the Internet can be uniquely identified.

Change "host" to "node".  (In IPv6, the term "host" does not include
routers, whereas "node" includes all IPv6 devices, both hosts and
routers.)

> 2.2.2 Aggregation
>
> IPv6 addresses must be distributed in a hierarchical manner,

In several places in the document, the term "distribution" is used,
rather than "allocation" or "assignment".  If "distribution" has a
distinct meaning, or is meant to refer to the union of allocation and
assignment, please include it in the glossary at the end, with an
explanation of its meaning.

> permitting the aggregation of routing information and
> limiting the number of routing entries advertised into the
> Internet. This is necessary to ensure proper operation of
> Internet routing and to maximize the routing system's
> ability to meet the demands of both likely and unforeseeable
> future increases in both size and topological complexity. In
> IPv6, aggregation of external routes is the primary goal.

In that last sentence, change "the primary goal" to "a primary goal".
IPv6 has other primary goals, such as increasing the available address
space.

> This goal is motivated by the problems which arose in IPv4
> network addressing. IPv4 address allocations have not been
> sufficiently hierarchical to ensure efficient routing across
> the Internet. Inefficient use of classful allocations led to
> an excess of routing entries appearing in the default-free
> routing table.

Change "Inefficient use of classful allocations" to "Allocations of
non-hierarchical (classful) prefixes".  It was not the inefficiency of
classful allocation that led to large routing tables, but rather their
lack of sufficient hierarchy.

> Furthermore, increased complexity of network
> topologies led to IPv4 prefixes being announced many times
> via different routes.

The presence of this sentence, in the context of the paragraph in which
it appears, would seem to imply that a goal is to reduce the complexity
of network topologies, which is certainly not a goal of IPv6 addressing
or the allocation policy.

> 2.2.4 Registration
>
> Every assignment and allocation of IPv6 Internet address
> space must be registered in a publicly accessible database.
> This is necessary to ensure uniqueness and to provide
> information for Internet trouble shooting at all levels.

Add a hyphen to "trouble shooting".

> 3.2 Initial IPv6 Addressing Hierarchy
>
> ...
>
> All router interfaces are required to have at least one
> link-local unicast address or site-local address.

As we explained in our earlier comments, we recommend that the paragraph
containing this sentence be deleted.  However, in case you decline to
accept that recommendation, you should know that the above sentence is
not exactly right.  All router (and host) interfaces are required to
have at least one link-local unicast address.  *In addition*, they may
be assigned site-local and/or global unicast addresses.

> 4.1 IPv6 Addresses not to be considered property
>
> All allocations and assignments of IPv6 address space are
> made on the basis that the holder of the address space is
> not to be considered the "owner" of the address space, and
> that all such allocations and assignments always remain
> subject to the current policies and guidelines described in
> this document.

Change "all such allocations and assignments" to "all allocations and
assignments of addresses under format prefix 001".

Perhaps change "in this document" to "in the most recent version of
this document".

>                 Holders of address space may potentially be
> required, at some time in the future, to return their
> address space and renumber their networks in accordance with
> the consensus of the Internet community in ensuring that the
> goals of aggregation and efficiency continue to be met.

Perhaps change "that the goals of aggregation and efficiency be met" to
"that the technically and operationally necessary levels of aggregation
and efficiency be met".


> 4.2.1 General Criteria for Initial Sub-TLA Allocation
>
> Subject to sections 4.2.2, and 4.2.3, Regional IRs will only
> make an initial allocation of sub-TLA address space to
> organizations that meet criterion (a) AND at least one part
> of criterion (b), as follows:
>
>      a. The requesting organization's IPv6 network must
>      have exterior routing protocol peering
>      relationships with the IPv6 networks of at least
>      three other organizations that have a sub-TLA
>      allocated to them.

In criterion (a), change "sub-TLA" to "sub-TLA or TLA".

>
> AND either
>
>      b(i). The requesting organization must have
>      reassigned IPv6 addresses received from its
>      upstream provider or providers to 40 SLA customer
>      sites with routed networks connected by permanent
>      or semi-permanent links.

What's a semi-permanent link?

>
> OR
>
>      b(ii). The requesting organization must
>      demonstrate a clear intent to provide IPv6 service
>      within 12 months after receiving allocated address
>      space. This must be substantiated by such
>      documents as an engineering plan or deployment
>      plan.

So, what sort of organization would satisfy (a) AND b(ii)?  Any ISP
who could satisfy (a) would presumably already be providing IPv6
service, not just planning to do it.

>
> 4.2.2 Criteria for sub-TLA Allocations in Transitional
> "Bootstrap" Phase
>
> ...
>
>      a. The requesting organization's network must have
>      exterior routing protocol peering relationships
>      with at least three other public Autonomous
>      Systems in the default-free zone.

Make it clearer that you are talking about *IPv4* peering arrangements,
in this case.

>
> AND
>
>      b. The requesting organization must show that it
>      plans to provide production IPv6 service within 12
>      months after receiving allocated address space.
>      This must be substantiated by such documents as an
>      engineering plan or a deployment plan.
>
> AND either
>
>      c. The requesting organization must be an IPv4
>      transit provider and must show that it already has
>      issued IPv4 address space to 40 customer sites
>      that can meet the criteria for a /48 IPv6
>      assignment. In this case, the organization must
>      have an up-to-date routing policy registered in
>      one of the databases of the Internet Routing
>      Registry, which the Regional IR may verify by
>      checking the routing table information on one of
>      the public looking glass sites).
>
> OR
>
>      d. The requesting organization must demonstrate
>      that it has experience with IPv6 through active
>      participation in the 6bone project for at least
>      six months, during which time it operated a
>      pseudo-TLA (pTLA) for at least three months. The
>      Regional IRs may require documentation of
>      acceptable 6Bone routing policies and practice
>      from the requesting organization.

We understood that the 6bone pre-qualification process was to be
independent of the other bootstrap criteria, i.e. sufficient on it own.
It seems unlikely that many ISPs meeting criteria (a) would need to
rely on criterion (d), rather than (c).  The 6bone pre-qual was
supposed to allow bootstrapping of IPv6 providers who are *not*
established IPv4 providers, i.e., do not satisfy (a).

> 4.2.3.2 Multihomed Sites
>
> [to be written]

What needs to be said here is that end-user sites connected to multiple
ISPs are expected to receive an NLA assignment (i.e., a /48) from each
of those ISPs, and therefore, each of such an end-user's nodes may have
multiple, globally-unique addresses.  However, it should also be explicitly
said that nothing in this policy is intended to prevent or discourage a
multi-homed end-user site from negotiating with any number of ISPs
for the service of advertising and routing a /48 prefix obtained from
another ISP.

> 4.2.4 Size for Initial Allocation: "Slow-Start" Mechanism
>
> Regional IRs will adopt a "slow start" mechanism when making
> initial allocations of sub-TLA space to eligible
> organizations. By this mechanism, the initial allocation
> will allow 13 bits worth of NLA IDs to be used by the
> organization unless the requesting organization submits
> documentation to the Regional IR to justify an exception
> based on topological grounds. This initial allocation allows
> the organization to create a hierarchy within the allocation
> depending on their customer type (ISP or end-site) and the
> topology of their own network. For example, an organization
> may receive 8,192 SLAs (a /48 each).

In that last sentence, change "8,192 SLAs" to "8,192 NLAs".

> 4.2.6 Registering and Verifying Usage
>
> Each TLA Registry is responsible for the usage of the
> sub-TLA address space it receives...

Change "sub-TLA" to "sub-TLA or TLA".  (And we would prefer that these
be called NLA registries, because they register NLAs, not TLAs, as
discussed above.)

> Registered end-sites must be connected and reachable.

This is inconsistent with our recommendation that dial-up customers be
able to obtain a /48, just like any other customers, so if our
recommendation is accepted, this section will have to be reconsidered.

>                        ...Filtering holes should be negotiated
> by the Regional IR and the organization holding the
> addresses in question.

Explain what is meant by a "filtering hole".

>...If an end-site requests an additional SLA, the TLA Registry must
>send the request to the Regional IR for a second opinion.

That should be "If an end-site requests an additional *NLA*, the
*NLA* Registry must...".

> 4.2.7 Renumbering
>
> It is possible that circumstances could arise whereby
> sub-TLA address space becomes scarce. This could occur, for
> example, due to inefficient use of assigned address space,
> or to an increase in the number of organizations holding
> both TLA and sub-TLA space.

Change "inefficient" to "very inefficient".

> Regional IRs requiring a TLA Registry to renumber will allow
> that Registry at least 12 months to return the sub-TLA
> space. [Note that the granted renumbering time may depend on
> the prefix length returned. The draft document
> http://search.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-08.txt
> describes the issues involved in and methods used for
> renumbering IPv6 networks.]

Just for your information, the IPng working group has an effort underway
to produce a new document describing the renumbering process for a site,
which will be more appropriate to cite here, once it has been published.

> 4.4 Reclamation Methods/Conditions
>
> ...
>
> However, if the limit is reached and routing technology at
> that time is not able to support additional routing entries,
> Regional IRs will review all allocations made up to that
> point. In the course of this review, the Regional IRs may
> seek consensus of the Internet registry and engineering
> communities to set minimum acceptable usage rates or new
> criteria determining eligibility to hold sub-TLA space.
> Dependent upon such a consensus, the Regional IRs may revoke
> the sub-TLA allocations of any Registry not complying with
> those rates or criteria.

We wonder if you want to say "sub-TLA or TLA" in the two places above
where you refer only to "sub-TLA".


> During the period that routing technology is being
> investigated, the Regional IRs will continue allocating
> address space even if the number of "possible" routes are
> reached.

Change "are reached" to "is reached".

> 6.1 Allocation and Reverse Address Mapping
>
> ...
>
> For each IPv6 address block allocated by a Regional IR to a
> member or customer, the Regional IR must set up NS records
> in the appropriate sub-domain within the "ip6.int" domain.

Just for your information, it is very likely that the "ip6.int" domain
will be moved out of ".int" and into ".arpa".  We expect this to be
decided fairly soon, probably by Adelaide.

> 7. GLOSSARY
>
> Allocation - The provision of IP address space to ISPs that
> reassign their address space to customers.

Change "ISPs" to "ISPs or exchanges".

> End-user - An organization receiving reassignments of IPv6
> addresses exclusively for use in operational networks.

Why "reassignments" instead of "assignments"?

What is the point of using the phrase "operational networks"?  Is this in
contrast to experimental networks or non-operational networks?  If this is actually intended to mean "not for offering public transit service to other
organizations" or something like that, please say that.

> Public Topology - The collection of providers and exchanges
> who provide public Internet transit service.

Change "who" to "that".

> Site - A location, physical or virtual, with a network
> backbone connecting various network equipment and systems
> together. There is no limit to the physical size or scope of
> a site.

Insert the word "geographic" before "scope"?

> Unicast - An identifier for a single interface. A packet
> sent to a unicast address is delivered to the interface
> identified by that address. Note that the definition of an
> IPv4 host is different from an IPv6 identifier. One physical
> host may have many interfaces, and therefore many IPv6
> identifiers.

IPv4 and IPv6 are *not* different in the way that this confusing text
seems to suggest.  In both protocols, addresses identify interfaces,
not hosts, and in both kinds of addresses, the lowest-order field
identifies an interface within a net or subnet (even though it is
less precisely called the "host field" in IPv4).


Finally, in the Call for Comments for the policy document, you said:

>* Definition of 'transit provider'
>
>A definition for the above term was not included in the current document. 
>Comments and suggestions for an appropriate definition are encouraged.

We suggest that you *not* try to define that term, knowing what a slippery
slope that is.  We believe the  criteria for allocation specified by the
policy document (however it turns out after this review cycle) is, or
ought to be, sufficient to indicate who is eligible to be assigned a
sub-TLA or TLA value and who is not.


Thanks again for requesting our feedback, and we apologize for the lateness
and lengthiness of our response.  We would be happy to set up a meeting to
discuss any of these issues with you in person, if that would be helpful.


Steve Deering & Bob Hinden,
Co-Chairs, IPng Working Group

Alain Durand, Bob Fink & Tony Hain,
Co-Chairs, NGTrans Working Group       



From owner-ngtrans@sunroof.eng.sun.com  Sat Jan 29 00:08:48 2000
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04600
	for <ngtrans-archive@odin.ietf.org>; Sat, 29 Jan 2000 00:08:47 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA10130;
	Fri, 28 Jan 2000 21:08:19 -0800 (PST)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id VAA05958;
	Fri, 28 Jan 2000 21:07:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) id e0T56gw22698
	for ngtrans-dist; Fri, 28 Jan 2000 21:06:42 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Beta12+Sun/8.10.0.Beta12) with ESMTP id e0T56Zj22691
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Jan 2000 21:06:36 -0800 (PST)
Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id VAA05882
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Jan 2000 21:06:34 -0800 (PST)
Received: from jazz-1.trumpet.com.au (jazz-1.trumpet.com.au [203.5.119.62])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA17607
	for <ngtrans@sunroof.eng.sun.com>; Fri, 28 Jan 2000 21:06:33 -0800 (PST)
Received: from localhost (peter-v6@localhost)
	by jazz-1.trumpet.com.au (8.9.3/8.9.3) with SMTP id QAA09874;
	Sat, 29 Jan 2000 16:06:18 +1100 (EST)
Date: Sat, 29 Jan 2000 16:06:18 +1100 (EST)
From: "Peter Tattam (IPv6 Mail)" <peter-v6@jazz-1.trumpet.com.au>
To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
cc: sob@harvard.edu, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) filtering against IPv6 in IPv4
In-Reply-To: <20000120150858D.shin@nd.net.fujitsu.co.jp>
Message-ID: <Pine.BSF.3.96.1000129160341.9426A-100000@jazz-1.trumpet.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: "Peter Tattam (IPv6 Mail)" <peter-v6@jazz-1.trumpet.com.au>

As a typical case, this issue bit me when I first hooked up to the 6bone.

I had to have a word to my sysadmin to make sure we passed the right traffic.
It is good network security practice to only allow traffic that you are sure
about and then to open up the filters slightly as needs arise.

I don't think our case would be uncommon.

Peter

On Thu, 20 Jan 2000, Yoshinobu Inoue wrote:

> > the statement has been made that ISPs are filtering to block IPv6 in
> > IPv4 traffic - I have not heard of such a thing (and in general ISPs do
> > not do this sort of filtering due to the perfoe`rmance impact on their
> > routers) - does anyone have specific informatyion information on what
> > ISPs are said to be doing this and why they might want to (since there is no
> > ISP operational reason to do this)
> > 
> > Scott
> 
> I received reports that some ISPs are filtering IPv6 over
> IPv4, but I don't think they are specifically or intentionally
> filtering it.
> They would be just passing some specific well knonwn protocols
> for security reason, and other packets like IPv6 over IPv4 is
> just filtered as the result.
> So actually this is not an IPv6 only issue. I also received
> same kind of report that mobile-ip packets are filtered by
> some ISP.
> 
> Also, those filtering seems to be done at dial-up access
> points, so performance issue won't be so significant.
> 
> I don't think we should check and make the name of such ISPs
> public in this stage, but we should annouce the possibility of
> such problem widely, and let ISPs notice that they might be
> doing such kind of filtering, and prompt them to check the
> current filtering configuration and let them alter it if it
> has any problem. (e.g. If they are filtering packets such as
> IPv6 over IPv4.)
> 
> And if there are still problems after such announcement, then
> I think we need to enumerate specific names of such ISPs.
> 
> 
> Yoshinobu Inoue
> KAME project
> 
> 

--
Peter R. Tattam                            peter-v6@trumpet.com.au
Managing Director,    Trumpet Software International Pty Ltd
Hobart, Australia,  Ph. +61-3-6245-0220,  Fax +61-3-62450210



