From owner-ngtrans@sunroof.eng.sun.com  Wed Mar  1 21:37: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 VAA20379
	for <ngtrans-archive@odin.ietf.org>; Wed, 1 Mar 2000 21:37: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 SAA03537;
	Wed, 1 Mar 2000 18:36: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 SAA22741;
	Wed, 1 Mar 2000 18:31:51 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) id e222T6T27384
	for ngtrans-dist; Wed, 1 Mar 2000 18:29:06 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) with ESMTP id e222T0927377
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Mar 2000 18:29:00 -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 SAA26162
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Mar 2000 18:29:00 -0800 (PST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA29887
	for <ngtrans@sunroof.eng.sun.com>; Wed, 1 Mar 2000 19:28:58 -0700 (MST)
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 CAA31220; Thu, 2 Mar 2000 02:28:55 GMT
Received: from hursley.ibm.com (lig32-225-132-135.us.lig-dial.ibm.com [32.225.132.135]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id CAA30910; Thu, 2 Mar 2000 02:28:50 GMT
Message-ID: <38BDBC30.8F86FB2F@hursley.ibm.com>
Date: Wed, 01 Mar 2000 18:56:16 -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: Jim Bound <bound@zk3.dec.com>
CC: ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Input Part 1: draft-ietf-ngtrans-6to4-03.txt
References: <199910280435.AAA0000026936@quarry.zk3.dec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Jim,

The 6to4 update will make it out pretty close to the deadline. There will be updates in response to most of the comments you
sent as Part 1 and all of those as Part 2. 
I will just comment here on points where we may not agree.

Jim Bound wrote:
> 
> Brian and Keith,
> 
> Here is input part 1 from several members of the Compaq IPv6 engineering
> team (Jack McCann, Sowmini Varadhan, Gerri Harter, Vlad Yasevich, Ken
> Powell, Mary Clouter, and Jim Bound). 
 ...
> 5.2.2 Summary of relay router configuration
> 
>    On its 6to4 IPv6 pseudo-interface, the relay router advertises
>    whatever IPv6 native prefixes its local policy permits, from among
>    those reachable through its native IPv6 interface. In the simplest
>    case, a default route to the whole IPv6 address space could be
>    advertised. It has been suggested that these routes could actually by
>   advertised along with IPv4 routes using BGP4 over IPv4, rather than
>    by running a separate BGP4+ session.
> 
> We cannot see the benefit of discussing BGP or BGP+ in the spec.  But if
> you want to talk about it please define how it will work, which is a lot
> of work for you authors.  But it is not needed.  But if you want to
> provide an appendix with diagrams and how BGP4 vs BGP+ will work that
> may be useful to realworld network operators without a doubt, but not
> clear it is needed in this specification.  And in its present terse form
> it is difficult at best to apply applicability assertions to the spec based
> on the above text.

I have added the alternative simple case where BGP4+ is not used, but I am 
convinced that without covering the BGP4+ scenario the document would not describe 
the full power of 6to4. OTOH I don't see why we need to include a description
of how BGP4+ works. I have added the necessary references and generally
clarified the text.
> 
> It may also be wise to get out of the business of trying to explain how
> route-exchanges are done within the spec.

Same response.
...
> 
> Section 5.3 Variant scenarios with tunnels.
> 
> This section should be expanded with examples and as one case which
> is in the scope of this works is where a 6to4 node sends to a native
> IPv6 site that does not support 6to4?  There are others.

This won't get done in this document since the authors don't have cycles.
Others are welcome to write it up.

> 
> Src 2002::/???? to Dst 3ffe::/??? will not work without 5.3 above and we
> feel strongly it should be discussed in this transition mechanism.

Why won't it work via a relay router?

   Brian




From owner-ngtrans@sunroof.eng.sun.com  Thu Mar  2 16:11:47 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 QAA27247
	for <ngtrans-archive@odin.ietf.org>; Thu, 2 Mar 2000 16:11:46 -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 NAA11976;
	Thu, 2 Mar 2000 13:11:17 -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 NAA01326;
	Thu, 2 Mar 2000 13:10:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) id e22L8Sc29594
	for ngtrans-dist; Thu, 2 Mar 2000 13:08:28 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) with ESMTP id e22L8J929587;
	Thu, 2 Mar 2000 13:08:20 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id NAA18174;
	Thu, 2 Mar 2000 13:08:12 -0800 (PST)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA02715;
	Thu, 2 Mar 2000 14:08:12 -0700 (MST)
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id NAA14664;
	Thu, 2 Mar 2000 13:06:07 -0800 (PST)
Received: from chicago.nsd.3com.com (chicago.nsd.3com.com [129.213.157.11])
	by new-york.3com.com (8.8.8/8.8.8) with ESMTP id NAA28582;
	Thu, 2 Mar 2000 13:06:07 -0800 (PST)
Received: from cyndi (lan-isdn-cmj3.nsd.3com.com [129.213.207.235])
	by chicago.nsd.3com.com (8.8.8/8.8.8) with SMTP id NAA05540;
	Thu, 2 Mar 2000 13:04:36 -0800 (PST)
Message-Id: <3.0.6.32.20000302131104.008ef6e0@mailhost.ewd.3com.com>
X-Sender: cmj@mailhost.ewd.3com.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 02 Mar 2000 13:11:04 -0800
To: 6bone@isi.edu, ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        deployment@ipv6.org
From: Cyndi Jung <cmj@3Com.com>
Subject: (ngtrans) Global IPv6 Summit: Members' code
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id e22L8LA29588
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Cyndi Jung <cmj@3Com.com>
Content-Transfer-Encoding: 8bit

There is still time to register for this Summit.

The code below will give you the early registration rate.

Also, the website <http://www.ipv6forum.com> will give you additional
options on lodging - there are still places to stay with reasonable
rates.  The Telluride Conference Center is not in a hotel - so the
entire Town of Telluride (all 10 by 4 blocks) is available for lodging.

Thanks,

Cyndi




>Subject: Global IPv6 Summit: Members' code
>Sender: owner-members@ipv6forum.com
>X-MIME-Autoconverted: from quoted-printable to 8bit by
chicago.nsd.3com.com id QAA02362
>
>Hello Folks,
>
>For those of you planning to attend the Global IPv6 Summit in a few weeks,
>here is a registration code "AEKG". Using this code when you register will
>give you a price of $695 vs $895.
>
>Please register soon at:
> <https://www.stardust.com/events/ipv6summit/register.htm>
>
>Here is an email that IPv6 Forum Members should feel free to pass around to
>company employees, partners and other appropriate persons.
>
>Thanks,
>Marty
>
>
>------------------
>Global IPv6 Summit - <http://www.stardust.com/ipv6summit/>
>------------------
>When:	March 13-16
>Where:	Telluride, Colorado USA
>
>Judy Estrin, Cisco's CTO is the opening keynote for the Global IPv6 Summit.
>
>The Global IPv6 Summit is the industry's gathering on IPv6 adoption,
>innovation and opportunity. The conference, workshops and IPv6 Forum
>meetings are March 13-16, 2000 in the beautiful resort town of Telluride,
>Colorado USA at the conference center in Mountain Village.
>
>In this intimate setting (space is limited to 200 people) you will be able
>to pose questions and debate with the leaders in this technology. Register
>today for only $895 at http://www.stardust.com/ipv6summit/
>
>At the summit we will focus on the deployments of IPv6 around the world,
>explore why wireless and home networking technology demands IPv6, and
>examine how IPv6 is presenting opportunities for application vendors,
>service providers, content providers and enterprise network engineers.
>
>Sessions will focus on
>----------------------
>- The Coming Tidal Wave of Applications
>- The Industry's Roadmap
>- "IPv6-Ready" Platforms and Routers
>- IPv6 Around the World
>- ISP Commercial Deployment
>- IPv6 Customers
>- IPv6 Standards
>- IPv6 Forum Meetings
>
>Who should attend? We expect the mix of summit attendees to include CEO's,
>CIO's, CTO's, network engineers, architects, developers, scientists,
>researchers, network managers and others who are responsible for networks
>and network technology. Attendance is limited to 200 people.
>
>Featured Keynote 
>----------------
>The New Internet presented by Judy Estrin, CTO of Cisco Systems
>
>The promise of the New Internet is communications ubiquity; our appliances,
>networks, electronic equipment, cars and even clothes will communicate with
>us and with each other. But IPv6 is required for us to realize the full
>potential of the global network.
>
>Judy Estrin is Chief Technology Officer and Senior Vice President at Cisco
>Systems. She is responsible for strategic technology planning and business
>development including investments and acquisitions, consulting engineering
>and advanced Internet projects, as well as legal and government affairs.
>
>Speakers will Represent
>-----------------------
>@Home, 3Com, Advanced Systems Consulting, Cisco Systems, Compaq,
>Ericsson-Telebit, InfiniBand Trade Association, Internet-Standard.com, MCI
>WorldCom, Microsoft, NetworkWorld, Nokia, Nortel Networks, NTT, Sun, Telia,
>Thomson-CSF, UCAID, UMTS Forum, UNAM, US Navy, and Viagénie.
>
>Sponsors
>--------
>The Global IPv6 Summit is graciously sponsored by 3Com, Cisco, Compaq,
>Microsoft, Motorola, Nokia, Nortel Networks, Qwest, Sun Microsystems and
>Teleglobe. Viagénie is sponsoring a free IPv6 tutorial on March 13th for
>registered summit attendees.
>
>
>Please email Sherryl Alameda <sherryla@stardust.com> or call with any
>questions at (408)879-8080.
>
>
>
>---
>Marty Bickford  - 408.879.8080 (8081-fax)
>Stardust.com - http://www.stardust.com
>
>



From owner-ngtrans@sunroof.eng.sun.com  Thu Mar  2 20:55: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 UAA02935
	for <ngtrans-archive@odin.ietf.org>; Thu, 2 Mar 2000 20:55:44 -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 RAA20757;
	Thu, 2 Mar 2000 17:55:21 -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 RAA23945;
	Thu, 2 Mar 2000 17:55:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) id e231s6K00589
	for ngtrans-dist; Thu, 2 Mar 2000 17:54:06 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) with ESMTP id e231rx900582
	for <ngtrans@sunroof.eng.sun.com>; Thu, 2 Mar 2000 17:53:59 -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 RAA06178
	for <ngtrans@sunroof.eng.sun.com>; Thu, 2 Mar 2000 17:53:58 -0800 (PST)
Received: from zmamail02.zma.compaq.com (zmamail02.zma.compaq.com [161.114.64.102])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA14867
	for <ngtrans@sunroof.eng.sun.com>; Thu, 2 Mar 2000 17:53:58 -0800 (PST)
Received: by zmamail02.zma.compaq.com (Postfix, from userid 12345)
	id 16E539A3; Thu,  2 Mar 2000 20:53:58 -0500 (EST)
Received: from yquarry.zk3.dec.com (yquarry.zk3.dec.com [16.140.16.3])
	by zmamail02.zma.compaq.com (Postfix) with ESMTP
	id B92CB831; Thu,  2 Mar 2000 20:53:57 -0500 (EST)
Received: from localhost by yquarry.zk3.dec.com (8.8.8/1.1.8.2/16Jan95-0946AM)
	id UAA0000024506; Thu, 2 Mar 2000 20:53:57 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200003030153.UAA0000024506@yquarry.zk3.dec.com>
To: Brian E Carpenter <brian@hursley.ibm.com>
Cc: Jim Bound <bound@zk3.dec.com>, ngtrans@sunroof.eng.sun.com
Subject: Re: (ngtrans) Input Part 1: draft-ietf-ngtrans-6to4-03.txt 
In-reply-to: Your message of "Wed, 01 Mar 2000 18:56:16 CST."
             <38BDBC30.8F86FB2F@hursley.ibm.com> 
Date: Thu, 02 Mar 2000 20:53:57 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Hi Brian,

>I will just comment here on points where we may not agree.

OK cool.  

>> Section 5.3 Variant scenarios with tunnels.
>> 
>> This section should be expanded with examples and as one case which
>> is in the scope of this works is where a 6to4 node sends to a native
>> IPv6 site that does not support 6to4?  There are others.

>This won't get done in this document since the authors don't have cycles.
>Others are welcome to write it up.

I think thats fine let me see if we can help you but can't promise my
cycles are gone until I finish a few other items folks are waiting on.

>> Src 2002::/???? to Dst 3ffe::/??? will not work without 5.3 above and we
>> feel strongly it should be discussed in this transition mechanism.

>Why won't it work via a relay router?

Just move forward it gets back to your response for 5.3.  

We need 6to4 in the market it is a diamond in the rough for IPv6
Deployment.  Will try to help where I can after IETF 47.

regards,
/jim



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar  7 10:14:15 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20487
	for <ngtrans-archive@odin.ietf.org>; Tue, 7 Mar 2000 10:14:14 -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 IAA04842;
	Tue, 7 Mar 2000 08:14:10 -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 HAA27533;
	Tue, 7 Mar 2000 07:12:19 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) id e27FBA804522
	for ngtrans-dist; Tue, 7 Mar 2000 07:11:10 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0.Gamma0+Sun/8.10.0.Gamma0) with ESMTP id e27FB2904515
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Mar 2000 07:11:03 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA27418
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Mar 2000 07:10:59 -0800 (PST)
Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA02905
	for <ngtrans@sunroof.eng.sun.com>; Tue, 7 Mar 2000 08:10:58 -0700 (MST)
Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345)
	id 480C8CB2; Tue,  7 Mar 2000 10:10:58 -0500 (EST)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by zmamail01.zma.compaq.com (Postfix) with ESMTP
	id 0F8C7EA5; Tue,  7 Mar 2000 10:10:58 -0500 (EST)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id KAA0000841606; Tue, 7 Mar 2000 10:10:57 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200003071510.KAA0000841606@anw.zk3.dec.com>
To: ngtrans@sunroof.eng.sun.com
Cc: Michael.Carney@eng.sun.com, charliep@iprg.nokia.com, bound@zk3.dec.com,
        Alain.Durand@sun.com, droms@bucknell.edu
Subject: (ngtrans) Update: draft-ietf-ngtrans-dstm-01.txt
Date: Tue, 07 Mar 2000 10:10:57 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

Folks,

We have updated DSTM to draft-ietf-ngtrans-dstm-01.txt.  

You can retrieve the spec above until the IETF sends out annoucement via
anonymous ftp at sipper.zk3-x.dec.com and then 'cd' to 'pub' directory.

Laurent, Hossam, and I have worked with Alain Durand to fine tune
DSTM to denote mandatory and optional parts for DSTM.  The change
section is as follows:

Changes from draft-00 to draft-01

   1.  Added text explaining why the draft does not use DHCPv4 to assign
       IPv4 compatible addresses to the "Introduction".

   2.  Defined what is mandatory and what is optional and added relative
       text in various places to clarify this change.  And added RFC
       2119 adjectives to the spec where appropriate.

   3.  Scenario 1 where IPv6 node wants to communicate with IPv4
       node is mandatory.

   4.  Scenarios 2 and 3 are now optional where an IPv6 node is
       assigned an IPv4 compatible address because an external
       IPv4 node is attempting communications with the IPv6 node.

   5.  For scenario 1 DHCPv6 is only needed for DSTM and not the
       tightly coupled paradigm of a co-existent DHCPv6 and
       DNS server.  Also added mandatory and optional to the
       DSTM AIIH/NODE/ROUTER Diagram.

   6.  Made Static Tunnel Endpoints mandatory and Dyanmic Tunnel
       End Points optional.

   7.  Fixed DHCPv6 Reconfigure statements to take into account
       changes to the Reconfigure message in the DHCPv6 working
       group, to support AIIH processing.

I will not be at the IETF 47 meeting due to scheduling conflicts but
Laurent and Hossam will be there.  Also Laurent and Hossam now have
prototype of DSTM running and a minimal prototype of DHCPv6.  Whether
this is on the agenda or not is TBD by the chairs.

Please send your input to us on NGTRANS WG list.  

Laurent, Hossam, and I will review any input from IETF 47 after the
meeting and get back to you as soon as we can.  Obviously any final
decisions will have to be made after the IETF 47 meeting so the authors
can communicate the input to each other.  But we are open to your input
right now.

Also our hope is we have a solid draft for DHCPv6 after IETF47 as I
continue to work with Mike Carney and Charlie Perkins on that
specification.  You will see an updated DHCPv6 and Extensions spec soon.
We received an extensive amount of good input from the DHC and NGTRANS
(thank you ngtrans folks for helping with dhcpv6) groups and writing
it all up is quite involved.

regards,
/jim



From owner-ngtrans@sunroof.eng.sun.com  Wed Mar  8 06:34:13 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 GAA29579
	for <ngtrans-archive@odin.ietf.org>; Wed, 8 Mar 2000 06:34: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 DAA09025;
	Wed, 8 Mar 2000 03:33:56 -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 DAA18393;
	Wed, 8 Mar 2000 03:33:21 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e28BWQm05694
	for ngtrans-dist; Wed, 8 Mar 2000 03:32:26 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e28BWIw05687
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Mar 2000 03:32:18 -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 DAA12580
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Mar 2000 03:32:16 -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 DAA24779
	for <ngtrans@sunroof.eng.sun.com>; Wed, 8 Mar 2000 03:32:15 -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 GAA28854;
	Wed, 8 Mar 2000 06:32:12 -0500 (EST)
Message-Id: <200003081132.GAA28854@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-dstm-01.txt
Date: Wed, 08 Mar 2000 06:32:12 -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		: Dual Stack Transition Mechanism (DSTM)
	Author(s)	: J. Bound, L. Toutain, H. AFIFI
	Filename	: draft-ietf-ngtrans-dstm-01.txt
	Pages		: 22
	Date		: 07-Mar-00
	
The initial deployment of IPv6 will require a tightly coupled use of
IPv4 addresses to support the interoperation of IPv6 and IPv4, within
an IPv6 Network.  Nodes will be able to be deployed with IPv6
addresses, but will still need to communicate with IPv4 nodes that do
not have a dual IP layer supporting both IPv4 and IPv6.  The Dual
Stack Transition Method (DSTM) provides a set of mechanisms to assign
temporary Global IPv4 Addresses to IPv6 nodes, use of dynamic tunnels
within an IPv6 Network to carry IPv4 traffic, and a defined set of
processes and architecture for the supporting infrastructure required
for this transition mechanism.

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Mar 10 06:32:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00484
	for <ngtrans-archive@odin.ietf.org>; Fri, 10 Mar 2000 06:32:17 -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 EAA29320;
	Fri, 10 Mar 2000 04:32:09 -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 DAA26858;
	Fri, 10 Mar 2000 03:31:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2ABU2907460
	for ngtrans-dist; Fri, 10 Mar 2000 03:30:02 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2ABTpw07442
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29:51 -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 DAA17670
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29:50 -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 DAA12026
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29:49 -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 GAA29225;
	Fri, 10 Mar 2000 06:29:48 -0500 (EST)
Message-Id: <200003101129.GAA29225@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-socks-gateway-03.txt
Date: Fri, 10 Mar 2000 06:29:48 -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		: A SOCKS-based IPv6/IPv4 Gateway Mechanism
	Author(s)	: H. Kitamura
	Filename	: draft-ietf-ngtrans-socks-gateway-03.txt
	Pages		: 15
	Date		: 09-Mar-00
	
This document describes an IPv6/IPv4 gateway mechanism that is based
on the SOCKS protocol [SOCKSv5]. By applying the SOCKS mechanism to
support the heterogeneous communications relays between IPv6 and IPv4
at the SOCKS server, the SOCKS-based IPv6/IPv4 gateway mechanism is
accomplished.
Since it is accomplished without introducing new protocols, it
provides the same communication environment that is provided by the
SOCKS mechanism. The same appearance is provided to the heterogeneous
communications. No conveniences or functionalities of current
communications are sacrificed.
The SOCKS-based gateway mechanism enables smooth heterogeneous
communications between the IPv6 nodes and IPv4 nodes.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Mar 10 06:32:42 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 GAA00763
	for <ngtrans-archive@odin.ietf.org>; Fri, 10 Mar 2000 06:32:41 -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 DAA13659;
	Fri, 10 Mar 2000 03:32:20 -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 DAA10531;
	Fri, 10 Mar 2000 03:31:45 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2ABU8e07461
	for ngtrans-dist; Fri, 10 Mar 2000 03:30:08 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2ABTvw07450
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29: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 DAA26740
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29:56 -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 DAA12067
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 03:29:55 -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 GAA29277;
	Fri, 10 Mar 2000 06:29:54 -0500 (EST)
Message-Id: <200003101129.GAA29277@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-translator-03.txt
Date: Fri, 10 Mar 2000 06:29:54 -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		: Overview of Transition Techniques for IPv6
                          only to Talk to IPv4-only Communication
	Author(s)	: K. Yamamoto, M. Sumikawa
	Filename	: draft-ietf-ngtrans-translator-03.txt
	Pages		: 8
	Date		: 09-Mar-00
	
This memo discusses translators to enable direct communication
between IPv4 hosts and IPv6 hosts. Three translation mechanisms are
described. From the address mapping point of view, the translators
are categorized into four types and each feasibility is considered.
This memo is based on a paper appeared in Proceedings of
INET98[INET].

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Mar 10 11:57: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 LAA19681
	for <ngtrans-archive@odin.ietf.org>; Fri, 10 Mar 2000 11:57:16 -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 IAA11265;
	Fri, 10 Mar 2000 08:56: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 IAA10636;
	Fri, 10 Mar 2000 08:56:13 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2AGtLk07671
	for ngtrans-dist; Fri, 10 Mar 2000 08:55:21 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2AGtEw07664
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 08:55:14 -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 IAA22135
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 08:55:15 -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 IAA07756
	for <ngtrans@sunroof.eng.sun.com>; Fri, 10 Mar 2000 08:55:11 -0800 (PST)
Received: from rasp2-80.lbl.gov (Truckee) [131.243.212.180] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12TSgh-0000iJ-00; Fri, 10 Mar 2000 08:54:56 -0800
Message-Id: <4.2.2.20000310085221.018efd00@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 10 Mar 2000 08:53:48 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) <draft-ietf-ngtrans-6bone-ptla-00.txt>
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>

The following I-D documents the 6bone pTLA/pNLA addressing structure. 
Nothing new here.

It is intended simply as Informational RFC documentation.


Bob

=======================================================================
INTERNET-DRAFT                                          Bob Fink, ESnet
March 10, 2000

                   6BONE pTLA and pNLA Formats (pTLA)

                  <draft-ietf-ngtrans-6bone-ptla-00.txt>

Abstract

This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix,
allocated in RFC 2471 [6BONE-TLA], to create pseudo Top-Level Aggregation
Identifiers(pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's).

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 September 10, 2000.

Acknowledgements

The address formats here are contributions of various early participants
of the 6bone testbed project, and of the IPng and NGtrans IETF working
groups.

Contents

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

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

2.  6BONE pTLA/pNLA Format...................................

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

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

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

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


1. Introduction

This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix,
allocated in RFC 2471 [6BONE-TLA], to create pseudo Top-Level Aggregation
Identifiers (pTLA) and pseudo Next-Level Aggregation Identifiers (pNLA).

The guiding specifications for IPv6 addressing relating to the 6bone
prefix, and the pTLA and pNLA formats, are "IP Version 6 Addressing
Architecture"  [ADDRARCH], and "An IPv6 Aggregatable Global Unicast
Address Format" [AGGR].

The purpose of creating pseudo TLA and NLA formats for the 6bone is to
provide a prototype of the actual TLA and NLA formats as they might be
used in production IPv6 networks. To do this economically, using only a
minimum of real production IPv6 address space, a single TLA, 3FFE::/16,
was reserved by the IANA (Internet Assigned Numbers Authority) for
testing on the 6bone. Thus it was necessary to define a pretend-to-be,
or pseudo, TLA and NLA structure to use under the 3FFE::/16 prefix.

Given the 48-bit length of the IPv6 Aggregatable Global Unicast Address
external routing prefix (that contains the TLA and NLA identifiers), there
is enough room to extend the TLA ID to contain a pTLA and shorten the
NLA ID to become a pNLA. This document specifies this.

In early 1999, it was decided to change the 6bone's pTLA format to allow
greater expansion of the testbed network, thus accommodating more than the
original 256 pTLA-s. Thus there are now two 6bone pTLA and pNLA formats.
This document specifies this.


2. 6BONE pTLA and pNLA Formats

2.1 Original 8-bit pTLA and 24-bit pNLA Format

The original pTLA and pNLA format was intended to accommodate 256 pTLA-s,
i.e., backbone networks carrying IPv6 transit traffic.

The original TLA and NLA ID-s as specified in [AGGR] are as follows:

          | 3 |  13 |          32         |   16   |    64 bits      |
          +---+-----+---------------------+--------+-----------------+
          |001| TLA |       NLA ID        | SLA ID | Interface ID    |
          +---+-----+---------------------+--------+-----------------+

The TLA value 1FFE was assigned to the 6bone, which when viewed with the
3-bit format preffix in prefix notation form is 3FFE::/16.

The first 8-bits of the NLA ID space are assigned as the pTLA that
defines the top level of aggegation (backbone) for the 6bone. This
provides for 256 6bone backbone networks, or pTLA-s, and leaves a 24-bit
pNLA ID for each pTLA to assign as needed.

          |     16    |  8  |     24      |   16   |    64 bits      |
          +-+---------+-----+-------------+--------+-----------------+
          |  0x3FFE   |pTLA |     pNLA    | SLA ID | Interface ID    |
          +-+---------+-----+-------------+--------+-----------------+

In prefix notation form the pTLA is 3FFE:nn00::/24, where nn is the pTLA
assignment.

The remaining NLA ID space can be used by each pTLA for their downward
aggregated delegation:

          |  n  |      24-n bits     |   16   |    64 bits      |
          +-----+--------------------+--------+-----------------+
          |pNLA1|       Site         | SLA ID | Interface ID    |
          +-----+--------------------+--------+-----------------+

                |  m  |    24-n-m    |   16   |    64 bits      |
                +-----+--------------+--------+-----------------+
                |pNLA2|    Site      | SLA ID | Interface ID    |
                +-----+--------------+--------+-----------------+

                      |  o  |24-n-m-o|   16   |    64 bits      |
                      +-----+--------+--------+-----------------+
                      |pNLA3|  Site  | SLA ID | Interface ID    |
                      +-----+--------+--------+-----------------+

The pNLA delegation works in the same manner as specified in [AGGR].
pTLA's are required to assume registry duties for the pNLA's below them,
pNLA1's for those below them, etc.


2.2 New 12-bit pTLA and 20-bit pNLA Format

After if became clear that the 6bone would become a useful testbed for
transition, in addition to its early role asa testbed for specifications
and implementations, the 6bone community decided to expand the size of the
pTLA ID.

Several important decisions regarding this expansion of the pTLA field are:

1. to leave the currently allocated 8-bit pTLA-s in use until the space was
needed, thus relying on a range value check to indicate the new pTLA format,

2. to use a modulo 4-bit sized pTLA ID to make reverse path entry into the
DNS easier,

3. given 2. above, to keep the pTLA ID size as small as possible to not
restrict pNLA ID size.

Therefore, the first 12-bits of the NLA ID space are assigned as the pTLA
that defines the top level of aggegation (backbone) for the 6bone. This
would eventually provide for 4096 6bone backbone networks, or pTLA-s, and
leaves a 20-bit pNLA ID for each pTLA to assign as needed.

          |     16    |   12  |   20      |   16   |    64 bits      |
          +-+---------+-------+-----------+--------+-----------------+
          |  0x3FFE   | pTLA  |   pNLA    | SLA ID | Interface ID    |
          +-+---------+-------+-----------+--------+-----------------+

In prefix notation form the pTLA is 3FFE:nnn0::/28, where nnn is the pTLA
assignment. However, as the existing 8-bit pTLA's are being left in use
for the present, the nnn value starts at 0x800 for now, thus yielding only
2048 pTLA's in this new format.

The remaining NLA ID space can be used by each pTLA for their downward
aggregated delegation:

          |  n  |      20-n bits     |   16   |    64 bits      |
          +-----+--------------------+--------+-----------------+
          |pNLA1|       Site         | SLA ID | Interface ID    |
          +-----+--------------------+--------+-----------------+

                |  m  |    20-n-m    |   16   |    64 bits      |
                +-----+--------------+--------+-----------------+
                |pNLA2|    Site      | SLA ID | Interface ID    |
                +-----+--------------+--------+-----------------+

                      |  o  |20-n-m-o|   16   |    64 bits      |
                      +-----+--------+--------+-----------------+
                      |pNLA3|  Site  | SLA ID | Interface ID    |
                      +-----+--------+--------+-----------------+

As with the original pTLA format, the pNLA delegation works in the same
manner as specified in [AGGR]. pTLA's are required to assume registry
duties for the pNLA's below them, pNLA1's for those below them, etc.


2.3 Example Format For pNLA's

An example usage of the pNLA space is given to demonstrate what is
reasonable and possible. It should not be assumed that this implies the
pNLA space must be used this way. As the new pTLA and pNLA format is now
the default, the example here assumes the 20-bit pNLA format.

The following example provides for up to 255 intermediate transit ISP's
(called pNLA1 below). The pNLA1 value of zero is meant to indicate that
there is no intermediate transit ISP between the backbone pTLA network
and the end user site.

          |<-----20-bit pNLA ID----->|
          |                          |
          |  8  |       12 bits      |   16   |    64 bits      |
          +-----+--------------------+--------+-----------------+
          |pNLA1|      Site  ID      | SLA ID | Interface ID    |
          +-----+--------------------+--------+-----------------+

Intermediate transit networks (pNLA1's) would assign uniques Site ID's for
eachend user site served.

As an example of this, assuming a backbone pTLA of 0x800, no intermediate
transit ISP (thus a pNLA1 of 0x00) and a sequential site ID (with start at
the right edge numbering) of 0x0001, the routing prefix for the first site
would look like:

         3FFE:8000:0001/48
  6bone _|||| |||| ||||___site
              |||| |
  b/b site____|||| |
                 | |
  transit________|_|

Another example of this usage, assuming the same backbone pTLA1 of 0x800 and
an intermediate transit ISP under it (numbering from the left edge) with an
NLA1 of 0x80, and a sequential site ID of 0x0001, the routing prefix for the
first site connected would look like:

         3FFE:0180:0001/48
  6bone _|||| |||| ||||___site
              ||||
  b/b site____||||
                ||
  transit_______||

Note 1: the two sites numbered 0x001 in the above examples are really two
different sites as their pNLA1 authority above them is different (i.e., in
the first case no transit exists thus the site is directly connected to
the pTLA backbone ISP, and in the second case the site is directly
connected to intermediate transit ISP 0x80).

Note 2: there would be nothing to prevent an pNLA1 transit site from
further allocating pNLA's below, but that becomes the policy of the pTLA
and pNLA's above them to work out.

Note 3: The 6bone registry, which is a RIPE-style database for documenting
IPv6 sites connected to the 6bone, has an "inet6num" object to allow
documentation of all IPv6 addresses allocated.


3.  Security Considerations

IPv6 addressing documents do not have any direct impact on Internet infra-
structure security.


4.  Change Log

Changes since version -00 of the draft:

none yet, still on -00


REFERENCES

[ADDRARCH] R. Hinden, S. Deering, "IP Version 6 Addressing Architecture",
RFC 2373, July 1998.

[AGGR] R. Hinden, M. O'Dell, S. Deering, "An IPv6 Aggregatable Global
Unicast Address Format", RFC 2374, July 1998.

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

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


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  Sun Mar 12 05:00: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 FAA12640
	for <ngtrans-archive@odin.ietf.org>; Sun, 12 Mar 2000 05:00:10 -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 BAA22689;
	Sun, 12 Mar 2000 01:59:45 -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 BAA27192;
	Sun, 12 Mar 2000 01:59:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2C9wDX08533
	for ngtrans-dist; Sun, 12 Mar 2000 01:58:13 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2C9w3w08526
	for <ngtrans@sunroof.eng.sun.com>; Sun, 12 Mar 2000 01:58:04 -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 BAA23209
	for <ngtrans@sunroof.eng.sun.com>; Sun, 12 Mar 2000 01:58:01 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA03559
	for <ngtrans@sunroof.eng.sun.com>; Sun, 12 Mar 2000 02:58:00 -0700 (MST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id SAA28016
	for <ngtrans@sunroof.eng.sun.com>; Sun, 12 Mar 2000 18:57:58 +0900 (JST)
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: (ngtrans) draft-ietf-ngtrans-6to4-04: multicast and PIM/link-local
From: itojun@iijlab.net
Date: Sun, 12 Mar 2000 18:57:58 +0900
Message-ID: <28014.952855078@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


	6to4 draft (draft-ietf-ngtrans-6to4-04) suggests use of PIM over 6to4
	pseudo link (or cloud).  Could someone clarify how can we really use
	PIM over 6to4 cloud?  PIM uses link-local multicast (ff02::{d,e})
	to detect adjacent PIM router.  It is not possible for 6to4 cloud.

	Section 3.1 talks about link-local address, however, I cannot think
	of possible real use of link-local address over 6to4 cloud.  In what
	situation do we use them?

	BTW, 6to4 04 draft clarifies some of multicast forwarding details.
	Thank you very much for clarification.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Sun Mar 12 09:16:54 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 JAA06868
	for <ngtrans-archive@odin.ietf.org>; Sun, 12 Mar 2000 09:16:53 -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 GAA07628;
	Sun, 12 Mar 2000 06:16:36 -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 GAA28389;
	Sun, 12 Mar 2000 06:08:36 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2CE7jj08623
	for ngtrans-dist; Sun, 12 Mar 2000 06:07:45 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2CE7aw08616
	for <ngtrans@sunroof.eng.sun.com>; Sun, 12 Mar 2000 06:07:37 -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 GAA03386;
	Sun, 12 Mar 2000 06:07:36 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA07300;
	Sun, 12 Mar 2000 06:07:34 -0800 (PST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id XAA29763;
	Sun, 12 Mar 2000 23:07:29 +0900 (JST)
To: gilligan@freegate.com, nordmark@eng.sun.com
cc: NGtrans List <ngtrans@sunroof.eng.sun.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
From: itojun@iijlab.net
Date: Sun, 12 Mar 2000 23:07:29 +0900
Message-ID: <29761.952870049@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

	About draft-ietf-ngtrans-mech-04.txt: Could we put more explicit
	wording about addresses (inner and out) on the packet? If the
	receiving node does not filter out non-conforming packets properly,
	there will be security issues.  Ingress filter (section 5.6) is a big
	plus (thanks for the addition!), but not really a complete solution.

	I personally would like to see the following restriction, from security
	perspective.  Actually this may be more restrictive than mech-04
	suggests.  Gory details are attached below.

	    A packet generated by automatic tunnel must carry the following
	    header fields.  Note that inner header field must match the
	    outer header field.

	    outer header
		IPv4 src: IPv4 address of the originating node
		IPv4 dst: IPv4 address of the destination node (not multicast)
	    inner header
		IPv6 src: IPv4 compatible for IPv4 src
		IPv6 dst: IPv4 compatible for IPv4 dst

	    Under any of following conditions, receiving node MUST drop the
	    packet:
	    - any of IPv4 src/dst is an IPv4 multicast address (224.0.0.0/4)
	    - any of IPv4 src/dst equals to 0.0.0.0
	    - any of IPv4 src/dst equals to 255.255.255.255
	    - any of IPv4 src/dst equals to a broadcast address of any of 
	      subnets directly connected to the receiving node
	    - if IPv4 src violates ingress filter rule
	      (incoming interface for the packet != outgoing interface for
	      IPv4 src, computed by the routing table of receiving node)

	Even with the check, malicious party can inject fabricated source
	address (for both IPv4/v6) to force receiving node to reply to
	wrong address (like someone's broadcast address).  In the folloing
	itojun replies to the packet, and the reply packet causes trouble.
	This is same as problem in forged IPv4 source address, so I think
	we are unable to solve it.
		badguy --auto tunnel--> itojun --auto tunnel--> victim
			(victim->itojun)	(itojun->victim)

	Some analysis on RFC1933, and 6to4-03 (04 is mostly the same) can be
	found at:
http://playground.iijlab.net/i-d/draft-itojun-ipv6-transition-abuse-00.txt
	(yes, I missed the i-d cutoff).  I should have checked mech-04 instead.

itojun


* requiring exact match betwen IPv6 src and IPv4 src
	From draft-ietf-ngtrans-mech-04.txt section 5.3 and section 5.4, it
	looks that the only corect form of packet from auto tunnel is like
	this.

	    outer header
		IPv4 src: IPv4 address of the originating node (*2)
		IPv4 dst: IPv4 address of the destination node
	    inner header
		IPv6 src: IPv4 compatible for IPv4 src
		IPv6 dst: IPv4 compatible for IPv4 dst (*1)

	IPv6 destination must always be IPv4 compatible for IPv4 destintaion
	from paragraph 1 of mech-04 section 5.3 (*1).

	mech-04 section 5.4 suggests to have configured tunnel between A
	and C.  This does not require injection of ::/96 route, as long as
	A has global IPv6 address (B can assign an address to A from directly
	attached subnet, and perform proxy NDP for A).
		A <--conf tunnel-- B <--native IPv6-- C
		A ---auto tunnel-------------------->
	Therefore, we can assume that the only address pair appear on the
	auto tunnel is the IPv4 compatible for IPv4 src (*2).  In the above
	example, source on auto tunnel is A.

	RFC2185 3.3.4 tries to cover the following case, where we may see
	non-matching IPv4/v6 source:
		A <--auto tunnel-- B <--native IPv6-- C
		A ---auto tunnel-------------------->
	A packet from C to A will have the following addresses, and IPv6 source
	does not match IPv4 source.
	    outer header
		IPv4 src: B's IPv4 addr
		IPv4 dst: A's IPv4 addr
	    inner header
		IPv6 src: C's normal IPv4 addr (not IPv4 compat)
		IPv6 dst: A's IPv4 compat addr for IPv4 dst
	Because this implies the existence of route for IPv4 compatible
	address (for routing packet from C to B), it seems to be less
	practical for use in wide area.
	From RFC2772 section 3.5, ::/96 is forbidden for EGP.
	RFC2185 is based on RFC1933, so I think mech-04 can override RFC2185.

	Revision of mech-04 should clarify this, by:
	- saying that some of the items in RFC2185 do not match mech-04/05, or
	- dropping reference to RFC2185

* forbidding multicast IPv4 address in outer header
	The last sentence in draft-ietf-ngtrans-mech-04.txt section 5.4
	leaves little room of ambiguity: do we need to allow multicast
	IPv4 address in outer header?  I think we can safely drop them
	(sender rule already forbids it).


From owner-ngtrans@sunroof.eng.sun.com  Mon Mar 13 06:22:50 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 GAA16651
	for <ngtrans-archive@odin.ietf.org>; Mon, 13 Mar 2000 06:22:49 -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 DAA29553;
	Mon, 13 Mar 2000 03:21:17 -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 DAA22910;
	Mon, 13 Mar 2000 03:20:23 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2DBJTZ09022
	for ngtrans-dist; Mon, 13 Mar 2000 03:19:29 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2DBJIw09015
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 03:19:18 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA22790
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 03:19:17 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA03329
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 04:19:17 -0700 (MST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15185;
	Mon, 13 Mar 2000 06:19:10 -0500 (EST)
Message-Id: <200003131119.GAA15185@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-6to4-04.txt
Date: Mon, 13 Mar 2000 06:19:09 -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		: Connection of IPv6 Domains via IPv4 Clouds without 
                          Explicit Tunnels
	Author(s)	: B. Carpenter, K. Moore
	Filename	: draft-ietf-ngtrans-6to4-04.txt
	Pages		: 22
	Date		: 10-Mar-00
	
This memo specifies an optional mechanism for assigning a unique
IPv6 address prefix to any site that currently has at least one
globally unique IPv4 address, and describes scenarios for using such
a prefix during the co-existence phase of IPv4 to IPv6 transition.
Effectively it treats the IPv4 network as a unicast link layer. Note
that this is not considered to be a long term solution and that sites
should migrate in due course to native IPv6 prefixes.
The motivation for this method is to allow isolated IPv6 domains or
hosts, attached to an IPv4 network which has no native IPv6 support,
to communicate with other such IPv6 domains or hosts with minimal
manual configuration. It also automatically provides a globally
unique IPv6 address prefix to any site with at least one globally
unique IPv4 address, even if combined with an IPv4 Network Address
Translator (NAT).

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-6to4-04.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Mon Mar 13 11:54:38 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 LAA21756
	for <ngtrans-archive@odin.ietf.org>; Mon, 13 Mar 2000 11:54:37 -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 IAA19233;
	Mon, 13 Mar 2000 08:53: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 IAA04274;
	Mon, 13 Mar 2000 08:53:18 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2DGqOm09245
	for ngtrans-dist; Mon, 13 Mar 2000 08:52:24 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2DGqHw09238
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 08:52:17 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA22417
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 08:52:17 -0800 (PST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA04200
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 09:52:16 -0700 (MST)
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 QAA62696; Mon, 13 Mar 2000 16:52:14 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id QAA27426; Mon, 13 Mar 2000 16:51:48 GMT
Message-ID: <38CD1C67.1EC860F1@hursley.ibm.com>
Date: Mon, 13 Mar 2000 10:50:47 -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: itojun@iijlab.net
CC: NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04: multicast and PIM/link-local
References: <28014.952855078@coconut.itojun.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Hi,

itojun@iijlab.net wrote:
> 
>         6to4 draft (draft-ietf-ngtrans-6to4-04) suggests use of PIM over 6to4
>         pseudo link (or cloud).  Could someone clarify how can we really use
>         PIM over 6to4 cloud?  PIM uses link-local multicast (ff02::{d,e})
>         to detect adjacent PIM router.  It is not possible for 6to4 cloud.

Well, the 6to4 authors are not experts on PIM-SM. We need someone who is
an expert on PIM-SM to help us. How do PIM-SM routers detect each other
over unicast links? Why is it any different over 6to4 virtual unicast links?

>         Section 3.1 talks about link-local address, however, I cannot think
>         of possible real use of link-local address over 6to4 cloud.  In what
>         situation do we use them?

When a 6to4 router talks to another 6to4 router there is a virtual link between
them (it really is a tunnel, but disguised). So it needs a link-local
address for completeness. We need to define it even if we *never* use it,
to respect the IPv6 addressing model.

> 
>         BTW, 6to4 04 draft clarifies some of multicast forwarding details.
>         Thank you very much for clarification.

Thanks

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Mon Mar 13 16:08: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 QAA03993
	for <ngtrans-archive@odin.ietf.org>; Mon, 13 Mar 2000 16:08:22 -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 NAA16660;
	Mon, 13 Mar 2000 13:07:20 -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 NAA22557;
	Mon, 13 Mar 2000 13:06:46 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2DL50j09614
	for ngtrans-dist; Mon, 13 Mar 2000 13:05:00 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.89.31] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2DL4pw09607
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 13:04:51 -0800 (PST)
Received: from lillen (lillen.Eng.Sun.COM [129.146.86.161])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2DL4nQ922184;
	Mon, 13 Mar 2000 13:04:49 -0800 (PST)
Date: Mon, 13 Mar 2000 13:00:59 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
To: itojun@iijlab.net
Cc: gilligan@freegate.com, nordmark@eng.sun.com,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <29761.952870049@coconut.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.952981259.23276.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>


Unless somebody has problems with these additional constraints
when decapsulating automatic tunnelled packets I'll add the constraints
to section 5.6.

> 	    A packet generated by automatic tunnel must carry the following
> 	    header fields.  Note that inner header field must match the
> 	    outer header field.
> 
> 	    outer header
> 		IPv4 src: IPv4 address of the originating node
> 		IPv4 dst: IPv4 address of the destination node (not multicast)
> 	    inner header
> 		IPv6 src: IPv4 compatible for IPv4 src
> 		IPv6 dst: IPv4 compatible for IPv4 dst
> 
> 	    Under any of following conditions, receiving node MUST drop the
> 	    packet:
> 	    - any of IPv4 src/dst is an IPv4 multicast address (224.0.0.0/4)
> 	    - any of IPv4 src/dst equals to 0.0.0.0
> 	    - any of IPv4 src/dst equals to 255.255.255.255
> 	    - any of IPv4 src/dst equals to a broadcast address of any of 
> 	      subnets directly connected to the receiving node
> 	    - if IPv4 src violates ingress filter rule
> 	      (incoming interface for the packet != outgoing interface for
> 	      IPv4 src, computed by the routing table of receiving node)

I'd like to replace the last bullet with a just a reference to 
the ingress filtering RFC.

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Mon Mar 13 18:54: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 SAA04603
	for <ngtrans-archive@odin.ietf.org>; Mon, 13 Mar 2000 18:54:56 -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 PAA16074;
	Mon, 13 Mar 2000 15:54:30 -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 PAA07031;
	Mon, 13 Mar 2000 15:53:49 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2DNqqf09743
	for ngtrans-dist; Mon, 13 Mar 2000 15:52:52 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2DNqhw09736
	for <ngtrans@sunroof.eng.sun.com>; Mon, 13 Mar 2000 15:52:43 -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 PAA14454;
	Mon, 13 Mar 2000 15:52:39 -0800 (PST)
Received: from itojun.org (nat.camp.wide.ad.jp [203.178.143.3])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA25797;
	Mon, 13 Mar 2000 16:52:36 -0700 (MST)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id IAA00754;
	Tue, 14 Mar 2000 08:52:12 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: gilligan@freegate.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Erik.Nordmark's message of Mon, 13 Mar 2000 13:00:59 PST.
      <Roam.SIMC.2.0.6.952981259.23276.nordmark@jurassic> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Tue, 14 Mar 2000 08:52:12 +0900
Message-ID: <752.952991532@lychee.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>Unless somebody has problems with these additional constraints
>when decapsulating automatic tunnelled packets I'll add the constraints
>to section 5.6.
>> 	    A packet generated by automatic tunnel must carry the following
>> 	    header fields.  Note that inner header field must match the
>> 	    outer header field.
>> 
>> 	    outer header
>> 		IPv4 src: IPv4 address of the originating node
>> 		IPv4 dst: IPv4 address of the destination node (not multicast)
>> 	    inner header
>> 		IPv6 src: IPv4 compatible for IPv4 src
>> 		IPv6 dst: IPv4 compatible for IPv4 dst
>> 
>> 	    Under any of following conditions, receiving node MUST drop the
>> 	    packet:
>> 	    - any of IPv4 src/dst is an IPv4 multicast address (224.0.0.0/4)
>> 	    - any of IPv4 src/dst equals to 0.0.0.0
>> 	    - any of IPv4 src/dst equals to 255.255.255.255
>> 	    - any of IPv4 src/dst equals to a broadcast address of any of 
>> 	      subnets directly connected to the receiving node
>> 	    - if IPv4 src violates ingress filter rule
>> 	      (incoming interface for the packet != outgoing interface for
>> 	      IPv4 src, computed by the routing table of receiving node)
>I'd like to replace the last bullet with a just a reference to 
>the ingress filtering RFC.

	yup, that's fine.

	please add the following to the drop condition (just to clarify):
	- if inner src/dst header does not match the sender rule

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 10:44: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 KAA02988
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 10:44:04 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA11011;
	Tue, 14 Mar 2000 07:43:11 -0800 (PST)
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 HAA22764;
	Tue, 14 Mar 2000 07:42:04 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EFeu610082
	for ngtrans-dist; Tue, 14 Mar 2000 07:40:56 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EFenw10075
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 07:40:50 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id HAA22514;
	Tue, 14 Mar 2000 07:40:49 -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 IAA06652;
	Tue, 14 Mar 2000 08:40:48 -0700 (MST)
Received: from [171.68.181.203] (ssh.cisco.com [171.69.10.34]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id HAA12325; Tue, 14 Mar 2000 07:40:37 -0800 (PST)
Mime-Version: 1.0
X-Sender: deering@127.0.0.1
Message-Id: <v04220804b4f40de954c1@[171.68.181.203]>
In-Reply-To: <Roam.SIMC.2.0.6.952981259.23276.nordmark@jurassic>
References: <Roam.SIMC.2.0.6.952981259.23276.nordmark@jurassic>
Date: Tue, 14 Mar 2000 07:40:59 -0800
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
From: Steve Deering <deering@cisco.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
Cc: itojun@iijlab.net, gilligan@freegate.com, nordmark@eng.sun.com,
        NGtrans List <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>

> > 	    Note that inner header field must match the
> > 	    outer header field.

What does that mean?

Steve



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 11:16:32 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 LAA15931
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 11:16:27 -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 IAA28278;
	Tue, 14 Mar 2000 08:15:41 -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 IAA14438;
	Tue, 14 Mar 2000 08:15:25 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EGEIB10116
	for ngtrans-dist; Tue, 14 Mar 2000 08:14:18 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EGE9w10109
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 08:14:09 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA28967;
	Tue, 14 Mar 2000 08:14:09 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA29287;
	Tue, 14 Mar 2000 09:14:05 -0700 (MST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id BAA09973;
	Wed, 15 Mar 2000 01:13:58 +0900 (JST)
To: Steve Deering <deering@cisco.com>
cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: deering's message of Tue, 14 Mar 2000 07:40:59 PST.
      <v04220804b4f40de954c1@[171.68.181.203]>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
From: itojun@iijlab.net
Date: Wed, 15 Mar 2000 01:13:58 +0900
Message-ID: <9971.953050438@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> > 	    Note that inner header field must match the
>> > 	    outer header field.
>What does that mean?

	IPv4 src/dst address in outer IPv4 header must match the
	IPv6 (in IPv4 compatible address) src/dst address in inner IPv6 header.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 11:36:13 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 LAA24328
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 11:36:10 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA14467;
	Tue, 14 Mar 2000 08:35:51 -0800 (PST)
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 IAA01222;
	Tue, 14 Mar 2000 08:35:36 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EGYUj10139
	for ngtrans-dist; Tue, 14 Mar 2000 08:34:30 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EGYOw10132
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 08:34:24 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA04177;
	Tue, 14 Mar 2000 08:34:23 -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 JAA12939;
	Tue, 14 Mar 2000 09:34:22 -0700 (MST)
Received: from [192.168.2.10] (ssh.cisco.com [171.69.10.34]) by postoffice.cisco.com (8.8.7-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id IAA18068; Tue, 14 Mar 2000 08:33:40 -0800 (PST)
Mime-Version: 1.0
X-Sender: deering@127.0.0.1
Message-Id: <v04220800b4f419ac43f9@[171.68.181.203]>
In-Reply-To: <9971.953050438@coconut.itojun.org>
References: <9971.953050438@coconut.itojun.org>
Date: Tue, 14 Mar 2000 08:33:51 -0800
To: itojun@iijlab.net
From: Steve Deering <deering@cisco.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Steve Deering <deering@cisco.com>

At 1:13 AM +0900 3/15/00, itojun@iijlab.net wrote:
> >> > 	    Note that inner header field must match the
> >> > 	    outer header field.
> >What does that mean?
>
>	IPv4 src/dst address in outer IPv4 header must match the
>	IPv6 (in IPv4 compatible address) src/dst address in inner IPv6 header.

Ah.  OK, that clearer explanation should go in the document.

Steve



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 11:43:55 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 LAA27117
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 11:43:53 -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 IAA19468;
	Tue, 14 Mar 2000 08:43:29 -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 IAA16239;
	Tue, 14 Mar 2000 08:43:03 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EGgCl10163
	for ngtrans-dist; Tue, 14 Mar 2000 08:42:12 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EGg5w10156
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 08:42:06 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id IAA06409
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 08:42:04 -0800 (PST)
Received: from mail5.microsoft.com (mail5.microsoft.com [131.107.3.121])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA17940
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:42:03 -0700 (MST)
Received: from 157.54.9.108 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Tue, 14 Mar 2000 08:35:50 -0800 (Pacific Standard Time)
Received: by INET-IMC-05 with Internet Mail Service (5.5.2651.58)
	id <GNCGY49H>; Tue, 14 Mar 2000 08:35:47 -0800
Message-ID: <4D0A23B3F74DD111ACCD00805F31D8102103ADF9@RED-MSG-50>
From: Richard Draves <richdr@microsoft.com>
To: itojun@iijlab.net, Steve Deering <deering@cisco.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: RE: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
Date: Tue, 14 Mar 2000 08:35:46 -0800
X-Mailer: Internet Mail Service (5.5.2651.58)
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Richard Draves <richdr@microsoft.com>

> 	IPv4 src/dst address in outer IPv4 header must match the
> 	IPv6 (in IPv4 compatible address) src/dst address in 
> inner IPv6 header.

You have to be careful with these kinds of checks, they prevent some
scenarios like forwarding and proxying.

We don't have any similar checks for link-layers like ethernet. (eg checking
that v6 source address resolves to the ethernet mac address in your ND
cache.)

Rich


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 11:45:36 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 LAA27690
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 11:45:33 -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 IAA19972;
	Tue, 14 Mar 2000 08:44:10 -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 IAA19038;
	Tue, 14 Mar 2000 08:43:38 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EGgqM10179
	for ngtrans-dist; Tue, 14 Mar 2000 08:42:52 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EGgaw10165
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 08:42:37 -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 IAA06538;
	Tue, 14 Mar 2000 08:42:35 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA24183;
	Tue, 14 Mar 2000 08:42:34 -0800 (PST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id BAA10381;
	Wed, 15 Mar 2000 01:42:31 +0900 (JST)
To: Richard Draves <richdr@microsoft.com>
cc: Steve Deering <deering@cisco.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: richdr's message of Tue, 14 Mar 2000 08:35:46 PST.
      <4D0A23B3F74DD111ACCD00805F31D8102103ADF9@RED-MSG-50>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
From: itojun@iijlab.net
Date: Wed, 15 Mar 2000 01:42:31 +0900
Message-ID: <10379.953052151@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>> 	IPv4 src/dst address in outer IPv4 header must match the
>> 	IPv6 (in IPv4 compatible address) src/dst address in 
>> inner IPv6 header.
>You have to be careful with these kinds of checks, they prevent some
>scenarios like forwarding and proxying.
>We don't have any similar checks for link-layers like ethernet. (eg checking
>that v6 source address resolves to the ethernet mac address in your ND
>cache.)

	actually, with mech-04 we no longer transmit packets with
	IPv4 compatible address in IPv6 destination field in native form.
	(RFC1933 allows it in section 4.4, sender rule 2.1 and 2.2.2)
	I just suggested more clarification.  Please see the original
	email from me for gory details.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 12:33: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 MAA17765
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 12:33:16 -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 JAA23795;
	Tue, 14 Mar 2000 09:32:55 -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 JAA01785;
	Tue, 14 Mar 2000 09:25:52 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EHP7D10261
	for ngtrans-dist; Tue, 14 Mar 2000 09:25:07 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EHOww10254
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:24:58 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id JAA14265
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:24:58 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA15037
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 10:24:56 -0700 (MST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id CAA10913;
	Wed, 15 Mar 2000 02:24:45 +0900 (JST)
To: Tim Hartrick <tim@mentat.com>
cc: richdr@microsoft.com, deering@cisco.com, Erik.Nordmark@eng.sun.com,
        gilligan@freegate.com, nordmark@eng.sun.com,
        ngtrans@sunroof.eng.sun.com
In-reply-to: tim's message of Tue, 14 Mar 2000 09:17:49 PST.
      <200003141717.JAA06608@feller.mentat.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
From: itojun@iijlab.net
Date: Wed, 15 Mar 2000 02:24:45 +0900
Message-ID: <10911.953054685@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net

>> >> 	IPv4 src/dst address in outer IPv4 header must match the
>> >> 	IPv6 (in IPv4 compatible address) src/dst address in 
>> >> inner IPv6 header.
>Am I understanding correctly that receivers are now supposed to apply
>this rule?  If so how does an implementation tell the difference between
>a datagram that was tunnelled using automatic tunnelling and a datagram
>that was tunnelled from the source using a unidirectional configured
>tunnel?  This filtering rule will cause datagrams of the second form
>to be discarded.

	In mech-04 configured tunnels and auto tunnels are separately
	talked (separate section).  My suggestion is only for auto tunnels.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 12:37:56 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 MAA19711
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 12:37:54 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA26872;
	Tue, 14 Mar 2000 09:37:25 -0800 (PST)
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 JAA09558;
	Tue, 14 Mar 2000 09:20:41 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EHJsF10243
	for ngtrans-dist; Tue, 14 Mar 2000 09:19:54 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EHJjw10236
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:19:46 -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 JAA09305
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:19:46 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA16118
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:19:44 -0800 (PST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id CAA10794;
	Wed, 15 Mar 2000 02:19:23 +0900 (JST)
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: brian's message of Mon, 13 Mar 2000 10:50:47 CST.
      <38CD1C67.1EC860F1@hursley.ibm.com>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-6to4-04: multicast and PIM/link-local
From: itojun@iijlab.net
Date: Wed, 15 Mar 2000 02:19:23 +0900
Message-ID: <10792.953054363@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>>         6to4 draft (draft-ietf-ngtrans-6to4-04) suggests use of PIM over 6to4
>>         pseudo link (or cloud).  Could someone clarify how can we really use
>>         PIM over 6to4 cloud?  PIM uses link-local multicast (ff02::{d,e})
>>         to detect adjacent PIM router.  It is not possible for 6to4 cloud.
>Well, the 6to4 authors are not experts on PIM-SM. We need someone who is
>an expert on PIM-SM to help us. How do PIM-SM routers detect each other
>over unicast links? Why is it any different over 6to4 virtual unicast links?

	from what I see from RFC2362 3.1.1, it is not covered in the document.
	(I'm no way expert in PIM)

>>         Section 3.1 talks about link-local address, however, I cannot think
>>         of possible real use of link-local address over 6to4 cloud.  In what
>>         situation do we use them?
>When a 6to4 router talks to another 6to4 router there is a virtual link between
>them (it really is a tunnel, but disguised). So it needs a link-local
>address for completeness. We need to define it even if we *never* use it,
>to respect the IPv6 addressing model.

	Suppose A and B are 6to4 router.  When A originates packet to B, 
	A needs to avoid using its link-local as source, since B can never
	reply to it.  Do the source address selection rules cover this enough?
	I think it becomes much easier to handle, and safer if we don't
	assign it.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 12:38:13 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 MAA19841
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 12:38:12 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA27088;
	Tue, 14 Mar 2000 09:37:44 -0800 (PST)
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 JAA08906;
	Tue, 14 Mar 2000 09:17:10 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EHG2C10225
	for ngtrans-dist; Tue, 14 Mar 2000 09:16:02 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EHFuw10218
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:15:56 -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 JAA12807;
	Tue, 14 Mar 2000 09:15:55 -0800 (PST)
Received: from roll.mentat.com ([192.88.122.129])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA13883;
	Tue, 14 Mar 2000 09:15:54 -0800 (PST)
Received: from leo.mentat.com (leo [192.88.122.132])
	by roll.mentat.com (8.9.1b+Sun/8.9.1) with ESMTP id JAA21570;
	Tue, 14 Mar 2000 09:16:05 -0800 (PST)
Received: from feller.mentat.com (feller [192.88.122.144])
	by leo.mentat.com (8.9.1b+Sun/8.9.1) with ESMTP id JAA19537;
	Tue, 14 Mar 2000 09:16:06 -0800 (PST)
Received: (from tim@localhost)
	by feller.mentat.com (8.9.3+Sun/8.9.1) id JAA06608;
	Tue, 14 Mar 2000 09:17:49 -0800 (PST)
Date: Tue, 14 Mar 2000 09:17:49 -0800 (PST)
From: Tim Hartrick <tim@mentat.com>
Message-Id: <200003141717.JAA06608@feller.mentat.com>
To: richdr@microsoft.com, itojun@iijlab.net
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
Cc: deering@cisco.com, Erik.Nordmark@eng.sun.com, gilligan@freegate.com,
        nordmark@eng.sun.com, ngtrans@sunroof.eng.sun.com
X-Sun-Charset: US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Tim Hartrick <tim@mentat.com>




> 
> >> 	IPv4 src/dst address in outer IPv4 header must match the
> >> 	IPv6 (in IPv4 compatible address) src/dst address in 
> >> inner IPv6 header.

Am I understanding correctly that receivers are now supposed to apply
this rule?  If so how does an implementation tell the difference between
a datagram that was tunnelled using automatic tunnelling and a datagram
that was tunnelled from the source using a unidirectional configured
tunnel?  This filtering rule will cause datagrams of the second form
to be discarded.

Or is this rule more accurately written as:

	If the source and/or destination address of the IPv6 datagram is an
IPv4 compatible IPv6 address then the source and/or destination address of
the encapsulating IPv4 header must be equivalent to the low order 32 bits
of the source and/or destination of the IPv6 datagram.


Tim Hartrick
Mentat Inc.


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 12:57:54 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 MAA26356
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 12:57:51 -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 JAA10173;
	Tue, 14 Mar 2000 09:56:51 -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 JAA21118;
	Tue, 14 Mar 2000 09:55:21 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EHrwQ10296
	for ngtrans-dist; Tue, 14 Mar 2000 09:53:58 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.82.166] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EHrow10289
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 09:53:50 -0800 (PST)
Received: from awe174-18 (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2EHrjQ161933;
	Tue, 14 Mar 2000 09:53:45 -0800 (PST)
Date: Tue, 14 Mar 2000 09:53:07 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
To: itojun@iijlab.net
Cc: Steve Deering <deering@cisco.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <9971.953050438@coconut.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.953056387.21119.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>

> 
> >> > 	    Note that inner header field must match the
> >> > 	    outer header field.
> >What does that mean?
> 
> 	IPv4 src/dst address in outer IPv4 header must match the
> 	IPv6 (in IPv4 compatible address) src/dst address in inner IPv6 header.


Thinking about this some more ...

When decapsulating a packet that was encapsulated with automatic
tunneling it is absolutely clear that the IPv6 destination should be an
IPv4 compataible address and that it should match the outer IPv4 destination
address.

But for the source address we have in the far past talked about routers
doing automatic tunneling for IPv4-compatible addresses.
In that case the sources would not match.
If we implement the above restrictions we will disable that capability
(it might be the right thing to do - I just feel we should ask the explicit
question).

Also, even for end-end automatic tunneling requiring "matching" source
addresses as above means that the sender is required to have
an IPv4-compatible IPv6 address in order to send packets to an
IPv4-compatible destination address. Once again, this might be the right choice
but I feel we should ask the explicit question.

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 16:58: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 QAA01643
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 16:58:19 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA19661;
	Tue, 14 Mar 2000 13:57:54 -0800 (PST)
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 NAA07546;
	Tue, 14 Mar 2000 13:57:20 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2ELu7c10421
	for ngtrans-dist; Tue, 14 Mar 2000 13:56:07 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2ELu0w10414
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 13:56:00 -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 NAA11343
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 13:55:58 -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 NAA28744
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 13:55:58 -0800 (PST)
Received: from truckee.wins.lbl.gov (Truckee) [128.3.9.220] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12UzIC-0007BN-00; Tue, 14 Mar 2000 13:55:56 -0800
Message-Id: <4.2.2.20000217073447.08120190@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 14 Mar 2000 13:54:47 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) NGtrans almost final agenda (will take input thru Thursday)
Cc: Alain Durand <Alain.Durand@sun.com>, Tony Hain <tonyhain@microsoft.com>,
        Randy Bush <randy@psg.com>, Bert Wijnen <bwijnen@lucent.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,

The final draft agenda is below. I will send it on to the IETF Friday the 
17th in time to meet their deadline. If you have any more comments or 
additions, please let me know.

I'm still looking for anyone to talk on finding 6bone ghost routes.

=======================================================================
The following time slots are for IPv6 activities that I know of so far.

MONDAY, March 27, 2000
1730-1930  Break
1930-2200  Evening Sessions
   Hall B OPS ngtrans Next Generation Transition WG

WEDNESDAY, March 29, 2000
0900-1130  Morning Sessions
   Hall E INT ipngwg IPNG WG (multicasted)
1130-1300  Break
1300-1500  Afternoon Sessions I
   Hall C OPS ngtrans Next Generation Transition WG

THURSDAY, March 30, 2000
1300-1500 Afternoon Sessions
  WG HOLD INT ipngwg IPNG WG (multicasted) MAY NOT HAPPEN??
==========================================================

Thanks,

Bob

=====================================
IETF-47 Adelaide ngtrans wg agenda - version of 14 March 2000

Project status report - Fink, 10 mins

BT Patent IPR status - Fink, 5-10 mins

MECH-04 update status - Nordmark, 5-15 mins

6to4-04 new draft - Carpenter, 30 mins

DSTM-01 new draft - Toutain, 5-10 mins

SOCKS-03 new draft - Kitamura, 10 mins

TRANSLATOR-03 new draft - Kazu, 10 mins (Alain to prod Kazu on status)

BROKER-02 - Guardini, 10 mins confirmed by Ivano

Tunnel Discovery - Durand, 5-10 mins

TCPUDP-RELAY-00 new draft - Itojun, 15 mins

TRANSITION-03 new draft - Steenman/Durand, 10 mins

6PAPA-01 new draft - Fink, 5 mins

pTLA-00 new draft - Fink, 5 mins

ABUSE-00 new draft  - Itojun, 10 mins
<http://playground.iijlab.net/i-d/draft-itojun-ipv6-transition-abuse-00.txt>

Interim NGtrans meeting plannng - Bob/Alain, 10-20 mins

PingERv6 Report - Les Cottrell, 10-15 mins

relocated 6bone registry - David Kessens - 5 mins

6tap report - Parent, 10 mins

pTLA reliability report - Ivano Guardini, 10-15 mins

tools for finding 6bone ghost routes - volunteers?

-end agenda




From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 17:34:20 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 RAA15173
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 17:34:19 -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 OAA07658;
	Tue, 14 Mar 2000 14:33:57 -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 OAA19049;
	Tue, 14 Mar 2000 14:33:05 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2EMVuU10462
	for ngtrans-dist; Tue, 14 Mar 2000 14:31:56 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2EMVnw10455
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 14:31:49 -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 OAA14449;
	Tue, 14 Mar 2000 14:31:46 -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 OAA19731;
	Tue, 14 Mar 2000 14:31:43 -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 WAA28050; Tue, 14 Mar 2000 22:31:39 GMT
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id WAA19186; Tue, 14 Mar 2000 22:31:30 GMT
Message-ID: <38CEBD74.10C6121B@hursley.ibm.com>
Date: Tue, 14 Mar 2000 16:30:12 -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: Richard Draves <richdr@microsoft.com>
CC: itojun@iijlab.net, Steve Deering <deering@cisco.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
References: <4D0A23B3F74DD111ACCD00805F31D8102103ADF9@RED-MSG-50>
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

Richard Draves wrote:
> 
> >       IPv4 src/dst address in outer IPv4 header must match the
> >       IPv6 (in IPv4 compatible address) src/dst address in
> > inner IPv6 header.
> 
> You have to be careful with these kinds of checks, they prevent some
> scenarios like forwarding and proxying.

The analagous check certainly doesn't apply in the case of a 
6to4 relay router receiving a 6to4 packet.

Surely there will be equivalent cases for IPv4-compatible addresses,
in which the next IPv6 hop for an encapsulated packet is not the 
final IPv6 destination? The checks must be configurable 'off' for
such cases.

   Brian


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 14 18:55:47 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 SAA14272
	for <ngtrans-archive@odin.ietf.org>; Tue, 14 Mar 2000 18:55:46 -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 PAA16866;
	Tue, 14 Mar 2000 15:55:19 -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 PAA07311;
	Tue, 14 Mar 2000 15:54:43 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2ENrXx10541
	for ngtrans-dist; Tue, 14 Mar 2000 15:53:33 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2ENrNw10534
	for <ngtrans@sunroof.eng.sun.com>; Tue, 14 Mar 2000 15:53:24 -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 PAA28598;
	Tue, 14 Mar 2000 15:53:21 -0800 (PST)
Received: from itojun.org ([203.178.143.168])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA01068;
	Tue, 14 Mar 2000 16:53:19 -0700 (MST)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id IAA06300;
	Wed, 15 Mar 2000 08:53:09 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Erik.Nordmark's message of Tue, 14 Mar 2000 09:53:07 PST.
      <Roam.SIMC.2.0.6.953056387.21119.nordmark@jurassic> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Wed, 15 Mar 2000 08:53:09 +0900
Message-ID: <6298.953077989@lychee.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>> 	IPv4 src/dst address in outer IPv4 header must match the
>> 	IPv6 (in IPv4 compatible address) src/dst address in inner IPv6 header.
>Thinking about this some more ...
>When decapsulating a packet that was encapsulated with automatic
>tunneling it is absolutely clear that the IPv6 destination should be an
>IPv4 compataible address and that it should match the outer IPv4 destination
>address.
>But for the source address we have in the far past talked about routers
>doing automatic tunneling for IPv4-compatible addresses.
>In that case the sources would not match.
>If we implement the above restrictions we will disable that capability
>(it might be the right thing to do - I just feel we should ask the explicit
>question).

	The above case is like:
		source --IPv6 native-> router --auto tunnel-> dest

		on IPv6 header of the packet (inner):
			src=normal IPv6 address of source
			dst=IPv4 mapped address of dest
		on IPv4 header of the packet between router and dest (outer):
			src=IPv4 address of router
			dst=IPv4 address of dest

	With mech-04 sender rule, the packet will never appear from the
	first place.  The source is required to send the packet in auto tunnel
	form, not IPv6 native.  (see section 5.3, paragrah 4)
	The behavior was already changed between RFC1933 -> mech-04, I believe.

	There might be one pithole: mech-04 does not talk about what the
	behavior of IPv6-only sending node should be.
	(for example, what should happen if the "source" on the above diagram
	is IPv6-only?)

>Also, even for end-end automatic tunneling requiring "matching" source
>addresses as above means that the sender is required to have
>an IPv4-compatible IPv6 address in order to send packets to an
>IPv4-compatible destination address. Once again, this might be the right choice
>but I feel we should ask the explicit question.

	I think this is the right choice.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 06:27:47 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 GAA00661
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 06:27:46 -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 DAA23428;
	Wed, 15 Mar 2000 03:27:27 -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 DAA25416;
	Wed, 15 Mar 2000 03:26:39 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2FBPZg10784
	for ngtrans-dist; Wed, 15 Mar 2000 03:25:35 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2FBPQw10777
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 03:25:26 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id DAA25371
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 03:25:25 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA15763
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 04:25:21 -0700 (MST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29654;
	Wed, 15 Mar 2000 06:25:20 -0500 (EST)
Message-Id: <200003151125.GAA29654@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-ptla-00.txt
Date: Wed, 15 Mar 2000 06:25:20 -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 pTLA and pNLA Formats (pTLA)
	Author(s)	: B. Fink
	Filename	: draft-ietf-ngtrans-6bone-ptla-00.txt
	Pages		: 
	Date		: 14-Mar-00
	
This memo defines how the 6bone uses the 3FFE::/16 IPv6 address prefix,
allocated in RFC 2471 [6BONE-TLA], to create pseudo Top-Level Aggregation
Identifiers(pTLA's) and pseudo Next-Level Aggregation Identifiers (pNLA's).

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ngtrans-6bone-ptla-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 09:45: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 JAA20414
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 09:45:08 -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 GAA23165;
	Wed, 15 Mar 2000 06:44:29 -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 GAA28444;
	Wed, 15 Mar 2000 06:43:54 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2FEfXs10865
	for ngtrans-dist; Wed, 15 Mar 2000 06:41:33 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2FEfQw10858
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 06:41:26 -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 GAA28056;
	Wed, 15 Mar 2000 06:41:26 -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 GAA06385;
	Wed, 15 Mar 2000 06:41:25 -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 OAA52446; Wed, 15 Mar 2000 14:41:22 GMT
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id OAA17662; Wed, 15 Mar 2000 14:41:18 GMT
Message-ID: <38CFA0D6.F224E485@hursley.ibm.com>
Date: Wed, 15 Mar 2000 08:40:22 -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: Jun-ichiro itojun Hagino <itojun@iijlab.net>
CC: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
References: <6298.953077989@lychee.itojun.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Jun-ichiro itojun Hagino wrote:
...
> >Also, even for end-end automatic tunneling requiring "matching" source
> >addresses as above means that the sender is required to have
> >an IPv4-compatible IPv6 address in order to send packets to an
> >IPv4-compatible destination address. Once again, this might be the right choice
> >but I feel we should ask the explicit question.
> 
>         I think this is the right choice.

Why? What is the value of this restriction? It seems to be a real limit on
deployment scenarios to me.

I'm beginning to think that all these rules have to be configurable. From
experience with IPv4 VPNs, this seems to be the only way to have adequate
flexibility.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 10:06:19 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 KAA29341
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 10:06:17 -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 HAA01882;
	Wed, 15 Mar 2000 07:05:25 -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 HAA15311;
	Wed, 15 Mar 2000 07:04:56 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2FF31a10919
	for ngtrans-dist; Wed, 15 Mar 2000 07:03:01 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2FF2jw10912
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 07:02:45 -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 HAA02241;
	Wed, 15 Mar 2000 07:02:39 -0800 (PST)
Received: from itojun.org ([203.178.143.155])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA16327;
	Wed, 15 Mar 2000 07:02:24 -0800 (PST)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id XAA12824;
	Wed, 15 Mar 2000 23:56:21 +0900 (JST)
To: Brian E Carpenter <brian@hursley.ibm.com>
cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: brian's message of Wed, 15 Mar 2000 08:40:22 CST.
      <38CFA0D6.F224E485@hursley.ibm.com> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Wed, 15 Mar 2000 23:56:15 +0900
Message-ID: <12787.953132175@lychee.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>> >Also, even for end-end automatic tunneling requiring "matching" source
>> >addresses as above means that the sender is required to have
>> >an IPv4-compatible IPv6 address in order to send packets to an
>> >IPv4-compatible destination address. Once again, this might be the right choice
>> >but I feel we should ask the explicit question.
>>         I think this is the right choice.
>Why? What is the value of this restriction? It seems to be a real limit on
>deployment scenarios to me.
>I'm beginning to think that all these rules have to be configurable. From
>experience with IPv4 VPNs, this seems to be the only way to have adequate
>flexibility.

	Without this check, your node will be attacked by malicious parties
	and generate unuseful (or harmful) packets, which would chew up your
	precious bandwidth.

	Actually, if the sender obeys mech-04 sender rule, we will only see
	packets that has matching src/dst in inner/outer.  No other
	combinations will appear on the wire, if the sender follows the rule
	carefully.  The wire packet change is due to the changes between
	RFC1933 and mech-04, this is not my call.  I just wanted to get more
	explicit wording, to help implementers filter out non-conforming
	packets.  Are you unhappy with RFC1933 -> mech-04 changes?

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 12:56:44 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 MAA09535
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 12:56:42 -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 JAA11898;
	Wed, 15 Mar 2000 09:56:07 -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 JAA14729;
	Wed, 15 Mar 2000 09:55:20 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2FHs8m11007
	for ngtrans-dist; Wed, 15 Mar 2000 09:54:08 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2FHs1w11000
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 09:54:02 -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 JAA03116;
	Wed, 15 Mar 2000 09:54:01 -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 JAA26290;
	Wed, 15 Mar 2000 09:53:59 -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 RAA28302; Wed, 15 Mar 2000 17:53:56 GMT
Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id RAA23480; Wed, 15 Mar 2000 17:53:54 GMT
Message-ID: <38CFCE10.A933BF17@hursley.ibm.com>
Date: Wed, 15 Mar 2000 11:53:20 -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: Jun-ichiro itojun Hagino <itojun@iijlab.net>
CC: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
References: <12787.953132175@lychee.itojun.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Brian E Carpenter <brian@hursley.ibm.com>
Content-Transfer-Encoding: 7bit

Jun-ichiro itojun Hagino wrote:
> 
> >> >Also, even for end-end automatic tunneling requiring "matching" source
> >> >addresses as above means that the sender is required to have
> >> >an IPv4-compatible IPv6 address in order to send packets to an
> >> >IPv4-compatible destination address. Once again, this might be the right choice
> >> >but I feel we should ask the explicit question.
> >>         I think this is the right choice.
> >Why? What is the value of this restriction? It seems to be a real limit on
> >deployment scenarios to me.
> >I'm beginning to think that all these rules have to be configurable. From
> >experience with IPv4 VPNs, this seems to be the only way to have adequate
> >flexibility.
> 
>         Without this check, your node will be attacked by malicious parties
>         and generate unuseful (or harmful) packets, which would chew up your
>         precious bandwidth.
> 
>         Actually, if the sender obeys mech-04 sender rule, we will only see
>         packets that has matching src/dst in inner/outer.  No other
>         combinations will appear on the wire, if the sender follows the rule
>         carefully.  The wire packet change is due to the changes between
>         RFC1933 and mech-04, this is not my call.  I just wanted to get more
>         explicit wording, to help implementers filter out non-conforming
>         packets.  Are you unhappy with RFC1933 -> mech-04 changes?

Firstly I'm not saying no checks. I am saying that it should be possible to
configure the checks (as I do today on my VPN software and my personal
firewall).

Second, OK, I see that mech-04 excludes automatic tunnels involving routers.
That does make me wonder why we bother with them (given that 6to4 does just
about the same thing but more flexibly). But if we accept this exclusion,
then the check you propose is not a problem.

  Brian


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 17:20: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 RAA28127
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 17:20:43 -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 OAA05084;
	Wed, 15 Mar 2000 14:20:24 -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 OAA14656;
	Wed, 15 Mar 2000 14:19:41 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2FMISe11163
	for ngtrans-dist; Wed, 15 Mar 2000 14:18:28 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.87.31] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2FMIJw11156
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 14:18:19 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2FMIJQ406508;
	Wed, 15 Mar 2000 14:18:19 -0800 (PST)
Date: Wed, 15 Mar 2000 14:14:17 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
To: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Cc: Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <6298.953077989@lychee.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.953158457.26956.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>


> 	The above case is like:
> 		source --IPv6 native-> router --auto tunnel-> dest
> 
> 		on IPv6 header of the packet (inner):
> 			src=normal IPv6 address of source
> 			dst=IPv4 mapped address of dest
> 		on IPv4 header of the packet between router and dest (outer):
> 			src=IPv4 address of router
> 			dst=IPv4 address of dest
> 
> 	With mech-04 sender rule, the packet will never appear from the
> 	first place.  The source is required to send the packet in auto tunnel
> 	form, not IPv6 native.  (see section 5.3, paragrah 4)
> 	The behavior was already changed between RFC1933 -> mech-04, I believe.

The text doesn't quite say that - it talks about the "auto-tunneling module".
Thus on all nodes that have an auto-tunneling module your observation
is correct. But we don't require all dual-stack hosts to have an
auto-tunneling module. 

> 	There might be one pithole: mech-04 does not talk about what the
> 	behavior of IPv6-only sending node should be.
> 	(for example, what should happen if the "source" on the above diagram
> 	is IPv6-only?)

That is another issue.

So unless we want to restrict automatic tunneling to be solely end-end
(i.e. the sender MUST encapsulate when sending to an ipv4-compatible address)
we can't enforce the source address checks when decapsulating.

If we make that restriction then ipv4-compatible addresses will be even
less useful than they are today.
For instance, putting an ipv4-compatible address in the DNS means that
only dual-stack nodes which have an "auto-tunneling module" and
an IPv4-compatible address themselves will be able to reach that 
address.
Sounds like one could never put IPv4-compatible address in the (global) DNS 
under such constraints.

Is this new limitation an acceptable cost for making it harder to
use automatic tunneling as a way to circumvent IPv6 ingress filtering?

   Erik



From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 19:02:36 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 TAA05542
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 19:02:35 -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 QAA26908;
	Wed, 15 Mar 2000 16:02:20 -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 QAA05601;
	Wed, 15 Mar 2000 16:01:58 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2G00jR11386
	for ngtrans-dist; Wed, 15 Mar 2000 16:00:45 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2G00aw11379
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 16:00:36 -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 QAA07993;
	Wed, 15 Mar 2000 16:00:36 -0800 (PST)
Received: from itojun.org ([203.178.143.155])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA21319;
	Wed, 15 Mar 2000 16:00:32 -0800 (PST)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id JAA02212;
	Thu, 16 Mar 2000 09:00:28 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Erik.Nordmark's message of Wed, 15 Mar 2000 14:14:17 PST.
      <Roam.SIMC.2.0.6.953158457.26956.nordmark@jurassic> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Thu, 16 Mar 2000 09:00:28 +0900
Message-ID: <2210.953164828@lychee.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>> 	With mech-04 sender rule, the packet will never appear from the
>> 	first place.  The source is required to send the packet in auto tunnel
>> 	form, not IPv6 native.  (see section 5.3, paragrah 4)
>> 	The behavior was already changed between RFC1933 -> mech-04, I believe.
>The text doesn't quite say that - it talks about the "auto-tunneling module".
>Thus on all nodes that have an auto-tunneling module your observation
>is correct. But we don't require all dual-stack hosts to have an
>auto-tunneling module. 
>> 	There might be one pithole: mech-04 does not talk about what the
>> 	behavior of IPv6-only sending node should be.
>> 	(for example, what should happen if the "source" on the above diagram
>> 	is IPv6-only?)
>That is another issue.

	Hmm, then I need to see text that covers sender rule for
	- IPv6-only node, or
	- IPv4/v6 dual stack node without IPv4 address assigned
	they can be:
	- should not transmit the packet to outside of the node
	- should send packets to IPv4 compatible destination with blablabla

	As you may have guessed, former one has my personal preference.

>So unless we want to restrict automatic tunneling to be solely end-end
>(i.e. the sender MUST encapsulate when sending to an ipv4-compatible address)
>we can't enforce the source address checks when decapsulating.

>If we make that restriction then ipv4-compatible addresses will be even
>less useful than they are today.
>For instance, putting an ipv4-compatible address in the DNS means that
>only dual-stack nodes which have an "auto-tunneling module" and
>an IPv4-compatible address themselves will be able to reach that 
>address.
>Sounds like one could never put IPv4-compatible address in the (global) DNS 
>under such constraints.

	Since we have no global route entry for ::/96 between ASes (EGP),
	practically it is not very meaningful to put IPv4-compatible onto
	global DNS database (RFC2772 3.5).  Even if we put an IPv4 compatible
	address for node A onto DNS database, from RFC2772 3.5, it is not
	possible to reach the node A from any IPv4-non-capable in different
	AS from node A.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 19:34:13 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 TAA18319
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 19:34: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 QAA09070;
	Wed, 15 Mar 2000 16:33:56 -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 QAA13966;
	Wed, 15 Mar 2000 16:33:27 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2G0WSP11410
	for ngtrans-dist; Wed, 15 Mar 2000 16:32:28 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.82.166] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2G0WJw11403
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 16:32:19 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2G0WJQ431522;
	Wed, 15 Mar 2000 16:32:19 -0800 (PST)
Date: Wed, 15 Mar 2000 16:28:15 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
To: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <2210.953164828@lychee.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.953166495.14922.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>


> 	Hmm, then I need to see text that covers sender rule for
> 	- IPv6-only node, or
> 	- IPv4/v6 dual stack node without IPv4 address assigned
> 	they can be:
> 	- should not transmit the packet to outside of the node
> 	- should send packets to IPv4 compatible destination with blablabla
> 
> 	As you may have guessed, former one has my personal preference.

While such text might make sense somewhere I'd like to treat that as outside
the scope of trans-mech - that document talks about dual-stack and currently
says nothing substancial about IPv6-only nodes.


> 	Since we have no global route entry for ::/96 between ASes (EGP),
> 	practically it is not very meaningful to put IPv4-compatible onto
> 	global DNS database (RFC2772 3.5).  Even if we put an IPv4 compatible
> 	address for node A onto DNS database, from RFC2772 3.5, it is not
> 	possible to reach the node A from any IPv4-non-capable in different
> 	AS from node A.

While we don't ever want global routes for anything in ::/96
the rest of your argument doesn't follow from that.

As trans-mech (and RFC 1933) is currently written it is possible to
have a site with dual-stack and/or IPv6 only nodes that have a
::/96 route to some "local" router. That router can then implement an
"auto tunneling module" that will do the encapsulation.
Thus the individual (dual or IPv6-only) hosts do not need an auto-tunneling
module and do not need IPv4-compatible addresses to be able to communicate with
nodes that have IPv4-compatible addresses.

Note: I'm not saying that we need to preserve the above behavior; it might very
well make sense to add your proposed restrictions that force auto-tunneling to 
be end-to-end. I'm just pointing out that your above argument that it isn't 
currently usable is incorrect.

  Erik



From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 19:49:55 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 TAA23268
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 19:49:54 -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 QAA15313;
	Wed, 15 Mar 2000 16:49:42 -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 QAA18303;
	Wed, 15 Mar 2000 16:49:28 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2G0mT411495
	for ngtrans-dist; Wed, 15 Mar 2000 16:48:29 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.82.166] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2G0mLw11488
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 16:48:21 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2G0mKQ435244;
	Wed, 15 Mar 2000 16:48:20 -0800 (PST)
Date: Wed, 15 Mar 2000 16:44:16 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
To: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, gilligan@freegate.com,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <752.952991532@lychee.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.953167456.28988.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>


After looking at the specific text in section 5.6 some more I realized the
following.

When automaticcally tunneled packets are decapsulated they SHOULD NOT be
forwarded since the auto tunnel always terminates at the endpoint.
Thus if we continue allow the IPv6 source and IPv4 source in the packet to
not "match" the worst that would happen is some form of DoS attack that
circumvents ingress filtering *but* the target of the attack has
both the IPv4 (topologically correct) address and the potentially bogus
IPv6 source address. Thus the target has the possibility to log both
addresses when subject to DoS attacks.

This argument is basically the same as the argument why the Mobile IPv6
home address option does not need to be authenticated by itself
(see draft-ietf-mobileip-ipv6-10.txt).

Thus wouldn't it be sufficient to recommend that implementations make
both source address available when logging security relevant events?

   Erik




From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 20:05:56 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 UAA29922
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 20:05:55 -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 RAA21702;
	Wed, 15 Mar 2000 17:05:42 -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 RAA20441;
	Wed, 15 Mar 2000 17:05:11 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2G14Bd11564
	for ngtrans-dist; Wed, 15 Mar 2000 17:04:11 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2G142w11557
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 17:04:02 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA13579;
	Wed, 15 Mar 2000 17:04:02 -0800 (PST)
Received: from itojun.org ([203.178.143.155])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA24678;
	Wed, 15 Mar 2000 18:04:00 -0700 (MST)
Received: from kiwi.itojun.org (localhost [127.0.0.1])
	by itojun.org (8.9.3+3.2W/3.7W) with ESMTP id KAA02847;
	Thu, 16 Mar 2000 10:03:59 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Erik.Nordmark's message of Wed, 15 Mar 2000 16:28:15 PST.
      <Roam.SIMC.2.0.6.953166495.14922.nordmark@jurassic> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date: Thu, 16 Mar 2000 10:03:58 +0900
Message-ID: <2845.953168638@lychee.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jun-ichiro itojun Hagino <itojun@iijlab.net>


>> 	Since we have no global route entry for ::/96 between ASes (EGP),
>> 	practically it is not very meaningful to put IPv4-compatible onto
>> 	global DNS database (RFC2772 3.5).  Even if we put an IPv4 compatible
>> 	address for node A onto DNS database, from RFC2772 3.5, it is not
>> 	possible to reach the node A from any IPv4-non-capable in different
>> 	AS from node A.
>While we don't ever want global routes for anything in ::/96
>the rest of your argument doesn't follow from that.

	sorry I wasn't careful enough.  confusing...

>As trans-mech (and RFC 1933) is currently written it is possible to
>have a site with dual-stack and/or IPv6 only nodes that have a
>::/96 route to some "local" router. That router can then implement an
>"auto tunneling module" that will do the encapsulation.
>Thus the individual (dual or IPv6-only) hosts do not need an auto-tunneling
>module and do not need IPv4-compatible addresses to be able to communicate with
>nodes that have IPv4-compatible addresses.

	hmmmm...  about ::/96 route in a site, I think, is either of follows:
	- if we would like to cover relayed case like this:

		IPv4 non-capable node --native IPv6--> relay
			--auto tunnel--> final destination

		(*) the relay and the final destination are auto tunnel capable.

	  we need to document it in mech-??.  without written documentation
	  admins have no idea how to configure a site.
	- if we don't want the relayed case, we need to explicitly reject it
	  in the document.

	currently mech-04 is silent about it and I figured - maybe wrongly -
	that only auto tunnel capable node should be able to transmit to
	v4 compat address.

>Note: I'm not saying that we need to preserve the above behavior; it might very
>well make sense to add your proposed restrictions that force auto-tunneling to 
>be end-to-end. I'm just pointing out that your above argument that it isn't 
>currently usable is incorrect.

	thank you for clarification.

itojun


From owner-ngtrans@sunroof.eng.sun.com  Wed Mar 15 23:34: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 XAA14668
	for <ngtrans-archive@odin.ietf.org>; Wed, 15 Mar 2000 23:34:32 -0500 (EST)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA08914;
	Wed, 15 Mar 2000 20:34:21 -0800 (PST)
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 UAA11314;
	Wed, 15 Mar 2000 20:34:02 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2G4Wel11803
	for ngtrans-dist; Wed, 15 Mar 2000 20:32:40 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2G4WVw11795
	for <ngtrans@sunroof.eng.sun.com>; Wed, 15 Mar 2000 20:32:31 -0800 (PST)
Received: from lillen (awe174-18.AWE.Sun.COM [192.29.174.18])
	by jurassic.eng.sun.com (8.10.0+Sun/8.10.0) with SMTP id e2G4WTQ459595;
	Wed, 15 Mar 2000 20:32:30 -0800 (PST)
Date: Wed, 15 Mar 2000 20:28:24 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: (ngtrans) Upcoming update to draft-ietf-ngtrans-mech-04.txt
To: ngtrans@sunroof.eng.sun.com
Cc: Erik.Nordmark@eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.953180904.4649.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>


Folks,

I'm trying to finalize edits based on some very old comments (going back to
Aug. 1999!).

Before I finish the ID I need to clarify the XXX below (subject of the email
reply I just sent to Itojun).

But I'd appreciate comments on the other changes.
The changes are hand-edited diff -cbi output with '!' indicating changes
and '+' indicating new text.

   Erik

***************
*** 272,290 ****
  2.2.  DNS
  
     The Domain Naming System (DNS) is used in both IPv4 and IPv6 to map
     between hostnames and IP addresses.  A new resource record type named
!    "AAAA" has been defined for IPv6 addresses [6].  Since IPv6/IPv4
!    nodes must be able to interoperate directly with both IPv4 and IPv6
!    nodes, they must provide resolver libraries capable of dealing with
!    IPv4 "A" records as well as IPv6 "AAAA" records.
  
     DNS resolver libraries on IPv6/IPv4 nodes must be capable of handling
!    both AAAA and A records.  However, when a query locates an AAAA
     record holding an IPv6 address, and an A record holding an IPv4
     address, the resolver library may filter or order the results
     returned to the application in order to influence the version of IP
     packets used to communicate with that node.  In terms of filtering,
     the resolver library has three alternatives:
--- 372,401 ----

  2.2.  DNS
  
     The Domain Naming System (DNS) is used in both IPv4 and IPv6 to map
     between hostnames and IP addresses.  A new resource record type named
!    "A6" has been defined for IPv6 addresses [6] with support for an
!    earlier record named "AAAA".  Since IPv6/IPv4 nodes must be able to
!    interoperate directly with both IPv4 and IPv6 nodes, they must
!    provide resolver libraries capable of dealing with IPv4 "A" records
!    as well as IPv6 "A6" and "AAAA" records.
  
     DNS resolver libraries on IPv6/IPv4 nodes MUST be capable of handling
!    both A6/AAAA and A records.  However, when a query locates an A6/AAAA
     record holding an IPv6 address, and an A record holding an IPv4
     address, the resolver library MAY filter or order the results
     returned to the application in order to influence the version of IP
     packets used to communicate with that node.  In terms of filtering,
     the resolver library has three alternatives:

***************
*** 306,320 ****
+ 2.3.  Advertising Addresses in the DNS
+ 
+    There are some constraint placed on the use of the DNS during
+    transition.  Most of these are obvious but are stated here for
+    completeness.
+ 
+    The recommendation is that A6/AAAA records for a node should not be
+    added to the DNS until all of these are true:
+ 
+      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.
+ 
+    If an IPv6 node is isolated from an IPv6 perspective (e.g. it is not
+    connected to the 6bone to take a concrete example) constraint #3
+    would mean that it should not have an address in the DNS.
+ 
+    This works great when other dual stack nodes tries to contact the
+    isolated dual stack node.  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 nodes have A records in the DNS.)
+ 
+    However, this does not work well when the isolated node is trying to
+    establish communication.  Even though it does not have an IPv6
+    address in the DNS it will find A6/AAAA records in the DNS for the
+    peer.  Since the isolated node has IPv6 addresses assigned to at
+    least one interface it will try to communicate 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 hopefully try
+    the IPv4 addresses based on the A records in the DNS, but this will
+    be painfully slow.
+ 
+    A possible implication of the recommendations 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 or communication failure
+    due to unreachability.  (A delay is incurred if the application
+    correctly falls back to using IPv4 if it can not establish
+    communication using IPv6 addresses.  If this fallback is not done the
+    application would fail to communicate in this case.)  Thus it is
+    suggested that either the recommendations be followed, or care be
+    taken to only do so with nodes that will not be impacted by external
+    accessing delays and/or communication failure.
+ 
+    In the future when a site or node removes the support for IPv4 the
+    above recommendations apply to when the A records for the node(s)
+    should be removed from the DNS.

**************
*** 540,551 **** [Section 3.3 Hop Limit]
       implementation dependent manner.  The current suggested value is
       published in the "Assigned Numbers RFC.  Implementations may
       provide a mechanism to allow the administrator to configure the
!      IPv4 TTL.
  
--- 763,776 ----
       implementation dependent manner.  The current suggested value is
       published in the "Assigned Numbers RFC.  Implementations MAY
       provide a mechanism to allow the administrator to configure the
!      IPv4 TTL such as the one specified in the IP Tunnel MIB [17].

***************
*** 700,722 **** [Section 3.6 Decapsulation]
  
!    When decapsulating the packet, the IPv6 header is not modified.  If
     the packet is subsequently forwarded, its hop limit is decremented by
     one.
  
!    The encapsulating IPv4 header is discarded.  [Note that work underway
!    in the IETF is redefining the Type of Service byte and as a result
!    future RFCs might define a different behavior for the ToS byte when
!    decapsulating a tunneled packet.]
--- 944,982 ----
  
! 
!    When decapsulating the packet, the IPv6 header is not modified.
!    [Note that work underway in the IETF is redefining the Type of
!    Service byte and as a result future RFCs might define a different
!    behavior for the ToS byte when decapsulating a tunneled packet.]  If
     the packet is subsequently forwarded, its hop limit is decremented by
     one.
  
!    As part of the decapsulation the node SHOULD silently discard a
!    packet with an invalid IPv4 source address such as a multicast
!    address, a broadcast address, 0.0.0.0, and 127.0.0.1.
  
+    The encapsulating IPv4 header is discarded.
+ 
+    XXX After the decapsulation the node SHOULD silently discard a packet
+    with an invalid IPv6 source address.  This include IPv6 multicast
+    addresses, the unspecified address, and the loopback address but also
+    IPv4-mapped IPv6 source addresses where the IPv4 part of the address
+    is an (IPv4) multicast address, broadcast address, 0.0.0.0, or
+    127.0.0.1.
+ 

***************
--- 1035,1073 ---- [Section 3.8 Neighbor Discovery over Tunnels]
+    For the purposes of Neighbor Discovery the automatic and configured
+    tunnels specified in this document as assumed to NOT have a link-
+    layer address, even though the link-layer (IPv4) does have address.
+    This means that a sender of Neighbor Discovery packets
+  
+     -   SHOULD NOT include Source Link Layer Address options or Target
+         Link Layer Address options on the tunnel link.
+  
+     -   MUST silently ignore any received SLLA or TLLA options on the
+         tunnel link.

***************
--- 1078,1169 ---- [Section 4.2.  Default Configured Tunnel using IPv4
"Anycast Address"]

+      However, care must be taking when using such a default tunnel to
+      prevent different IPv4 fragments from arriving at different routers
+      for reassembly.  This can be prevented by either avoiding
+      fragmentation of the encapsulated packets (by ensuring an IPv4 MTU
+      of at least 1300 bytes) or by preventing frequent changes to IPv4
+      routing.

***************
*** 964,974 **** [Setion 5.3.  Automatic Tunneling Operation]

     The automatic tunneling module must not send to IPv4 broadcast or
     multicast destinations.  It must drop all IPv6 packets destined to
     IPv4-compatible destinations when the embedded IPv4 address is
!    broadcast or multicast.
  
--- 1303,1314 ----

     The automatic tunneling module MUST NOT send to IPv4 broadcast or
     multicast destinations.  It MUST drop all IPv6 packets destined to
     IPv4-compatible destinations when the embedded IPv4 address is
!    broadcast, multicast, the unspecified (0.0.0.0) address, or the
!    loopback address (127.0.0.1).  Note that the sender can only tell if
!    an address is a network or subnet broadcast for broadcast addresses
!    assigned to directly attached links.
  
***************
--- 1542,1552 ---- [Section 10.  Changes from RFC 1933]

+    -    Clarified that decapsulating nodes MUST be capable of
+         reassembling an IPv4 packet that is 1300 bytes (1280 bytes plus
+         IPv4 header).
+ 
+    -    Clarified that when using a default tunnel to an IPv4 "anycast
+         address" the network must either have an IPv4 MTU of least 1300
+         bytes (to avoid fragmentation of minimum size IPv6 packets) or
+         be configured to avoid frequent changes to IPv4 routing to the
+         "anycast address" (to avoid different IPv4 fragments arriving at
+         different tunnel endpoints).
+ 
+    -    Using A6/AAAA instead of AAAA to reference IPv6 address records
+         in the DNS.
+ 
+    -    Specified when to put IPv6 addresses in the DNS.
+ 
+    -    Added reference to the tunnel mib for TTL specification for the
+         tunnels.
+ 
+    -    Added a table of contents.
+ 
+    -    Added checks in the decapsulation checking both an IPv4-
+         compatible IPv6 source address and the outer IPv4 source
+         addresses for multicast, broadcast, all-zeros etc.
+ 
+    -    Added recommendations for use of source and target link layer
+         address options for the tunnel links.



From owner-ngtrans@sunroof.eng.sun.com  Thu Mar 16 14:40:46 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15885
	for <ngtrans-archive@odin.ietf.org>; Thu, 16 Mar 2000 14:40:45 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA04808;
	Thu, 16 Mar 2000 12:37:26 -0700 (MST)
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 KAA23109;
	Thu, 16 Mar 2000 10:55:48 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2GIs8m12505
	for ngtrans-dist; Thu, 16 Mar 2000 10:54:08 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2GIs1w12498
	for <ngtrans@sunroof.eng.sun.com>; Thu, 16 Mar 2000 10:54:02 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id KAA23145;
	Thu, 16 Mar 2000 10:54:00 -0800 (PST)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA26897;
	Thu, 16 Mar 2000 11:53:05 -0700 (MST)
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 SAA66158; Thu, 16 Mar 2000 18:52:10 GMT
Received: from hursley.ibm.com (gsine01.us.sine.ibm.com [9.14.6.41]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id SAA16940; Thu, 16 Mar 2000 18:52:06 GMT
Message-ID: <38D12D31.6D671576@hursley.ibm.com>
Date: Thu, 16 Mar 2000 12:51:29 -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: Erik Nordmark <Erik.Nordmark@Eng.Sun.COM>
CC: Jun-ichiro itojun Hagino <itojun@iijlab.net>, gilligan@freegate.com,
        NGtrans List <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue
References: <Roam.SIMC.2.0.6.953167456.28988.nordmark@jurassic>
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

I definitely want to see the possibility of routers originating auto
tunnels; it seems a pointless restriction to limit them to e2e use.

So I agree with Erik.

    Brian

Erik Nordmark wrote:
> 
> After looking at the specific text in section 5.6 some more I realized the
> following.
> 
> When automaticcally tunneled packets are decapsulated they SHOULD NOT be
> forwarded since the auto tunnel always terminates at the endpoint.
> Thus if we continue allow the IPv6 source and IPv4 source in the packet to
> not "match" the worst that would happen is some form of DoS attack that
> circumvents ingress filtering *but* the target of the attack has
> both the IPv4 (topologically correct) address and the potentially bogus
> IPv6 source address. Thus the target has the possibility to log both
> addresses when subject to DoS attacks.
> 
> This argument is basically the same as the argument why the Mobile IPv6
> home address option does not need to be authenticated by itself
> (see draft-ietf-mobileip-ipv6-10.txt).
> 
> Thus wouldn't it be sufficient to recommend that implementations make
> both source address available when logging security relevant events?
> 
>    Erik


From owner-ngtrans@sunroof.eng.sun.com  Thu Mar 16 15:09:55 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26887
	for <ngtrans-archive@odin.ietf.org>; Thu, 16 Mar 2000 15:09:53 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA03374;
	Thu, 16 Mar 2000 13:07:51 -0700 (MST)
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 MAA11762;
	Thu, 16 Mar 2000 12:07:27 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2GK5qD12631
	for ngtrans-dist; Thu, 16 Mar 2000 12:05:52 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2GK5Yw12615;
	Thu, 16 Mar 2000 12:05:34 -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 MAA13377;
	Thu, 16 Mar 2000 12:05:29 -0800 (PST)
Received: from raven.ecs.soton.ac.uk (raven.ecs.soton.ac.uk [152.78.70.1])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA27976;
	Thu, 16 Mar 2000 12:05:28 -0800 (PST)
Received: from penelope.ecs.soton.ac.uk (penelope.ecs.soton.ac.uk [152.78.68.135])
	by raven.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id UAA16893;
	Thu, 16 Mar 2000 20:05:24 GMT
Received: from penelope (penelope [152.78.68.135])
	by penelope.ecs.soton.ac.uk (8.9.1a/8.9.1) with ESMTP id UAA01109;
	Thu, 16 Mar 2000 20:05:24 GMT
Date: Thu, 16 Mar 2000 20:05:24 +0000 (GMT)
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) US IPv6 Forum Summit presentations online
Message-ID: <Pine.SOL.4.20.0003162001180.453-100000@penelope.ecs.soton.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Tim Chown <tjc@ecs.soton.ac.uk>


Hi,

The US IPv6 Summit presentations from Telluride are now online at 

        http://www.ipv6forum.com

in HTML, Powerpoint and zipped PDF formats.

The link is from the top of the front page.

Cheers,
Tim




From owner-ngtrans@sunroof.eng.sun.com  Thu Mar 16 16:24:38 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25503
	for <ngtrans-archive@odin.ietf.org>; Thu, 16 Mar 2000 16:24:36 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00758;
	Thu, 16 Mar 2000 14:22:29 -0700 (MST)
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 NAA01103;
	Thu, 16 Mar 2000 13:21:57 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2GLKEP12876
	for ngtrans-dist; Thu, 16 Mar 2000 13:20:14 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2GLK4w12869
	for <ngtrans@sunroof.eng.sun.com>; Thu, 16 Mar 2000 13:20:04 -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 NAA28083
	for <ngtrans@sunroof.eng.sun.com>; Thu, 16 Mar 2000 13:20:03 -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 NAA14971
	for <ngtrans@sunroof.eng.sun.com>; Thu, 16 Mar 2000 13:20:01 -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 QAA23635;
	Thu, 16 Mar 2000 16:19:57 -0500 (EST)
Message-Id: <200003162119.QAA23635@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: ngtrans@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: (ngtrans) I-D ACTION:draft-ietf-ngtrans-introduction-to-ipv6-transition-03.txt
Date: Thu, 16 Mar 2000 16:19:56 -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		: A Guide to the Introduction of IPv6 in the IPv4 World
	Author(s)	: W. Biemolt, H. Steenman, M. Kaat, A. Durand,
                          G. Tsirtsis, R. van der Pol, Y. Sekiya
	Filename	: draft-ietf-ngtrans-introduction-to-ipv6-transition-03.txt
	Pages		: 36
	Date		: 15-Mar-00
	
This document is a guide to the introduction of IPv6 in the IPv4 
based Internet or Intranets.  Several general issues to start IPv6 
networking in a predominantly IPv4 world are discussed, such as IPv6
addresses, IPv6 DNS and routing issues.  Short descriptions are given
of the different translation and migration tools and mechanisms that
translate between IPv6 and IPv4 and/or tunnel IPv6 over IPv4.  The 
remainder of this document describes how IPv6 can be introduced in 
various environments, such as ISPs, Internet Exchanges and end user 
environments.  Suggestions are given on the use of the different 
translation and migration tools in each environment.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-ngtrans@sunroof.eng.sun.com  Fri Mar 17 11:27:56 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06318
	for <ngtrans-archive@odin.ietf.org>; Fri, 17 Mar 2000 11:27:53 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA13101;
	Fri, 17 Mar 2000 09:26:34 -0700 (MST)
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 IAA11726;
	Fri, 17 Mar 2000 08:24:57 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2HGNvq13724
	for ngtrans-dist; Fri, 17 Mar 2000 08:23:57 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2HGNpw13717
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 08:23:51 -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 IAA03910
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 08:23:50 -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 IAA25155
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 08:23:47 -0800 (PST)
Received: from rasp2-66.lbl.gov (Truckee) [131.243.212.166] 
	by mail1.es.net with esmtp (Exim 1.81 #2)
	id 12VzXN-0002wN-00; Fri, 17 Mar 2000 08:23:46 -0800
Message-Id: <4.2.2.20000317082201.017f0e10@imap2.es.net>
X-Sender: rlfink@imap2.es.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 17 Mar 2000 08:23:43 -0800
To: NGtrans List <ngtrans@sunroof.eng.sun.com>
From: Bob Fink <fink@es.net>
Subject: (ngtrans) IETF-47 Adelaide ngtrans wg agenda
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,

Below is the final agenda as submitted to the secretariat today. Further 
changes can be made in Adelaide.


Thanks,

Bob, Tony and Alain


==================================
IETF-47 Adelaide ngtrans wg agenda

Project status report - Fink, 10 mins

BT Patent IPR status - Fink, 5-10 mins

MECH-04 update status - Nordmark, 5-15 mins

6to4-04 new draft - Carpenter, 30 mins

DSTM-01 new draft - Toutain, 5-10 mins

SOCKS-03 new draft - Kitamura, 10 mins

TRANSLATOR-03 new draft - Kazu, 10 mins

BROKER-02 - Guardini, 10 mins

Tunnel Discovery - Durand, 5-10 mins

TCPUDP-RELAY-00 new draft - Itojun, 15 mins

TRANSITION-03 new draft - Steenman/Durand, 10 mins

6PAPA-01 new draft - Fink, 5 mins

pTLA-00 new draft - Fink, 5 mins

ABUSE-00 new draft  - Itojun, 10 mins
<http://playground.iijlab.net/i-d/draft-itojun-ipv6-transition-abuse-00.txt>

Interim NGtrans meeting plannng - Bob/Alain, 10-20 mins

PingERv6 Report - Les Cottrell, 10-15 mins

relocated 6bone registry - David Kessens - 5 mins

6tap report - Parent, 10 mins

pTLA reliability report - Ivano Guardini, 10-15 mins

-end agenda








From owner-ngtrans@sunroof.eng.sun.com  Fri Mar 17 20:17:08 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03921
	for <ngtrans-archive@odin.ietf.org>; Fri, 17 Mar 2000 20:17:08 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA01677;
	Fri, 17 Mar 2000 17:37:49 -0700 (MST)
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 QAA06809;
	Fri, 17 Mar 2000 16:37:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) id e2I0aMd14315
	for ngtrans-dist; Fri, 17 Mar 2000 16:36:22 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.0+Sun/8.10.0) with ESMTP id e2I0aFw14308
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 16:36:16 -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 QAA06559
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 16:36:16 -0800 (PST)
Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA17486
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 16:36:15 -0800 (PST)
Received: from hpncdja.cup.hp.com (hpncdja.cup.hp.com [15.13.106.146])
	by atlrel1.hp.com (Postfix) with ESMTP id DB12DE4D5
	for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 19:36:14 -0500 (EST)
Received: from localhost (dsw@localhost) by hpncdja.cup.hp.com with SMTP (8.8.6 (PHNE_17190)/8.7.3 TIS 5.0.1) id QAA27824 for <ngtrans@sunroof.eng.sun.com>; Fri, 17 Mar 2000 16:41:44 -0800 (PST)
Date: Fri, 17 Mar 2000 16:41:44 -0800 (PST)
From: David Wang <dsw@cup.hp.com>
To: ngtrans@sunroof.eng.sun.com
Subject: (ngtrans) HP-UX IPv6 Developer's Kit version 1.1
Message-ID: <Pine.HPP.3.96.1000317164124.27783E-100000@hpncdja.cup.hp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: David Wang <dsw@cup.hp.com>

Hewlett-Packard Company announces the release of the HP-UX IPv6
Developer's Kit version 1.1

The HP-UX IPv6 Developer's Kit version 1.1 supports the IETF IPv6
standards that will provide IPv6 functionality on HP-UX 11.00. IPv6 is a
new version of the Internet Protocol that provides a larger address space,
simple network configuration, and better security. The IPv6 Developer's
Kit enables the Internet community to evaluate and experiment with the
IPv6 protocol on HP-UX 11.0.

More details are available at:

        http://www.software.hp.com

Please search for "IPv6".

The HP-UX IPv6 development team



From owner-ngtrans@sunroof.eng.sun.com  Mon Mar 20 13:51:55 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10829
	for <ngtrans-archive@odin.ietf.org>; Mon, 20 Mar 2000 13:51:55 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA26232;
	Mon, 20 Mar 2000 11:48:02 -0700 (MST)
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 KAA20177;
	Mon, 20 Mar 2000 10:46:15 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2KIj2S16036
	for ngtrans-dist; Mon, 20 Mar 2000 10:45:02 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.82.166] (may be forged))
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2KIirN16029
	for <ngtrans@sunroof.eng.sun.com>; Mon, 20 Mar 2000 10:44:53 -0800 (PST)
Received: from bobo (bobo.Eng.Sun.COM [129.146.86.130])
	by jurassic.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with SMTP id e2KIipj976596;
	Mon, 20 Mar 2000 10:44:51 -0800 (PST)
Date: Mon, 20 Mar 2000 10:44:51 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
To: Jun-ichiro itojun Hagino <itojun@iijlab.net>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <2845.953168638@lychee.itojun.org>
Message-ID: <Roam.SIMC.2.0.6.953577891.2930.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>


Itojun,

I noticed that there is an updated draft for the addressing architecture
(draft-ietf-ipngwg-addr-arch-v3-00.txt) thus if you feel we should add
something about rejecting bad IPv4-mapped addresses this might be a good
time to ask that question on the ipng list.

FYI: My draft text for ngtrans-mech reads:
   After the decapsulation the node SHOULD silently discard a packet
   with an invalid IPv6 source address.  This includes IPv6 multicast
   addresses, the unspecified address, and the loopback address but also
   IPv4-mapped IPv6 source addresses where the IPv4 part of the address
   is an (IPv4) multicast address, broadcast address, 0.0.0.0, or
   127.0.0.1.

  Erik



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 21 05:10:00 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 FAA05719
	for <ngtrans-archive@odin.ietf.org>; Tue, 21 Mar 2000 05:10:00 -0500 (EST)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA14972;
	Tue, 21 Mar 2000 03:08:58 -0700 (MST)
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 CAA01264;
	Tue, 21 Mar 2000 02:08:29 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2LA7XO16821
	for ngtrans-dist; Tue, 21 Mar 2000 02:07:33 -0800 (PST)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2LA7NN16814
	for <ngtrans@sunroof.eng.sun.com>; Tue, 21 Mar 2000 02:07:23 -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 CAA06994;
	Tue, 21 Mar 2000 02:07:22 -0800 (PST)
Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA15804;
	Tue, 21 Mar 2000 02:07:16 -0800 (PST)
Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.04) with ESMTP id TAA09956;
	Tue, 21 Mar 2000 19:07:10 +0900 (JST)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: Steve Deering <deering@cisco.com>, gilligan@freegate.com,
        nordmark@eng.sun.com, NGtrans List <ngtrans@sunroof.eng.sun.com>
In-reply-to: Erik.Nordmark's message of Mon, 20 Mar 2000 10:44:51 PST.
      <Roam.SIMC.2.0.6.953577891.2930.nordmark@jurassic>
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
Subject: Re: (ngtrans) draft-ietf-ngtrans-mech-04.txt: security issue 
From: itojun@iijlab.net
Date: Tue, 21 Mar 2000 19:07:10 +0900
Message-ID: <9954.953633230@coconut.itojun.org>
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: itojun@iijlab.net


>I noticed that there is an updated draft for the addressing architecture
>(draft-ietf-ipngwg-addr-arch-v3-00.txt) thus if you feel we should add
>something about rejecting bad IPv4-mapped addresses this might be a good
>time to ask that question on the ipng list.

	Thanks, I'll raise it in ipngwg (since the document is tagged as
	ipngwg document).

itojun


From owner-ngtrans@sunroof.eng.sun.com  Thu Mar 23 00:28:26 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05457
	for <ngtrans-archive@odin.ietf.org>; Thu, 23 Mar 2000 00:28:24 -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 WAA24925;
	Wed, 22 Mar 2000 22:27:26 -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 VAA23596;
	Wed, 22 Mar 2000 21:25:17 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2N5OPx18404
	for ngtrans-dist; Wed, 22 Mar 2000 21:24:25 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2N5OIN18397
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:24:18 -0800 (PST)
Received: from fenris.spnusw.sun.com (halley.EBay.Sun.COM [129.150.111.35])
	by engmail4.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id VAA23537
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:24:17 -0800 (PST)
Received: from orpheus.amdahl.com ([129.212.11.6])
	by fenris.spnusw.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA14875
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:13:26 -0800 (PST)
Received: from orpheus.amdahl.com (localhost [127.0.0.1])
	by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id VAA20698
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:24:02 -0800 (PST)
Received: from fujitsuI.fujitsu.com (fujitsuI.fujitsu.com [133.164.253.1])
	by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id VAA20694
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:24:01 -0800 (PST)
Received: from fujitsuI.fujitsu.com (localhost [127.0.0.1])
	by fujitsuI.fujitsu.com (8.9.3/8.9.3) with ESMTP id VAA16741
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:24:00 -0800 (PST)
Received: from abroad.proxy.fujitsu.co.jp ([133.161.11.30])
	by fujitsuI.fujitsu.com (8.9.3/8.9.3) with ESMTP id VAA16735
	for <ngtrans@sunroof.Eng.Sun.COM>; Wed, 22 Mar 2000 21:23:58 -0800 (PST)
Received: from m2.gw.fujitsu.co.jp by abroad.proxy.fujitsu.co.jp (8.9.3/3.7W-0003-Abroad Gateway)
	id OAA20647; Thu, 23 Mar 2000 14:23:57 +0900 (JST)
Received: from phoenix.avalon.flab.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master)
	id OAA22996; Thu, 23 Mar 2000 14:23:57 +0900 (JST)
Received: from localhost (koba@localhost [127.0.0.1])
	by phoenix.avalon.flab.fujitsu.co.jp (8.9.3/3.7W-avalon-2000013115) with ESMTP id OAA01698;
	Thu, 23 Mar 2000 14:23:55 +0900 (JST)
To: ngtrans@sunroof.eng.sun.com, 6bone@ISI.EDU
Subject: (ngtrans) SOCKS64: An implementation of SOCKS based IPv6/IPv4 Gateway Mechanism
From: KOBAYASHI Shinji <koba@flab.fujitsu.co.jp>
X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000323142352L.koba@flab.fujitsu.co.jp>
Date: Thu, 23 Mar 2000 14:23:52 +0900
X-Dispatcher: imput version 980905(IM100)
Lines: 25
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: KOBAYASHI Shinji <koba@flab.fujitsu.co.jp>
Content-Transfer-Encoding: 7bit


We released the new version of our implementation of the SOCKS based
IPv6/IPv4 Gateway Mechanism. The URL is:

ftp://ftp.kame.net/pub/kame/misc/socks64-v10r10-20000322.tgz

Main changes from socks64-v10r8-19990118.tgz are:

1. Based on the latest SOCKS5 package socks5-v1.0r10.
2. Support for Linux (kernel-2.2.x, GNU libc 2.1) is added.
3. New option -r (--reverse) is added.

With -r option, socks64 server tries to get the FQDN of the target by
reverse querying DNS if the client specifies its target in IPv4
address. Using this option, we can provide (limited) supports to SOCKS
version 4 (not 5) clients such as Netscape Communicator without
SocksCap or runsocks. Please refer to README.socks64 for detail.

We would appreciate your problem reports, comments, and
suggestions. Please send e-mails to:

mailto:socks64@pds-flab.rwcp.or.jp

Kobayashi Shinji
koba@flab.fujitsu.co.jp


From owner-ngtrans@sunroof.eng.sun.com  Thu Mar 23 20:34:17 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22644
	for <ngtrans-archive@odin.ietf.org>; Thu, 23 Mar 2000 20:34:16 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA21529;
	Thu, 23 Mar 2000 18:31:43 -0700 (MST)
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 RAA00093;
	Thu, 23 Mar 2000 17:31:03 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2O1Sfh19235
	for ngtrans-dist; Thu, 23 Mar 2000 17:28:41 -0800 (PST)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2O1SNN19226
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:28:23 -0800 (PST)
Received: from fenris.spnusw.sun.com (halley.EBay.Sun.COM [129.150.111.35])
	by engmail1.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id RAA15273
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:28:18 -0800 (PST)
Received: from orpheus.amdahl.com ([129.212.11.6])
	by fenris.spnusw.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA10975
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:17:26 -0800 (PST)
Received: from orpheus.amdahl.com (localhost [127.0.0.1])
	by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id RAA16334
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:27:48 -0800 (PST)
Received: from fujitsuI.fujitsu.com (fujitsuI.fujitsu.com [133.164.253.1])
	by orpheus.amdahl.com (8.9.3/8.9.3) with ESMTP id RAA16329
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:27:47 -0800 (PST)
Received: from fujitsuI.fujitsu.com (localhost [127.0.0.1])
	by fujitsuI.fujitsu.com (8.9.3/8.9.3) with ESMTP id RAA25099
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:27:30 -0800 (PST)
Received: from abroad.proxy.fujitsu.co.jp ([133.161.11.30])
	by fujitsuI.fujitsu.com (8.9.3/8.9.3) with ESMTP id RAA25083
	for <ngtrans@sunroof.Eng.Sun.COM>; Thu, 23 Mar 2000 17:27:29 -0800 (PST)
Received: from m4.gw.fujitsu.co.jp by abroad.proxy.fujitsu.co.jp (8.9.3/3.7W-0003-Abroad Gateway)
	id KAA20342; Fri, 24 Mar 2000 10:27:28 +0900 (JST)
Received: from phoenix.avalon.flab.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0003-Fujitsu Domain Master)
	id KAA17225; Fri, 24 Mar 2000 10:27:27 +0900 (JST)
Received: from localhost (koba@localhost [127.0.0.1])
	by phoenix.avalon.flab.fujitsu.co.jp (8.9.3/3.7W-avalon-2000013115) with ESMTP id KAA17842;
	Fri, 24 Mar 2000 10:27:24 +0900 (JST)
To: mmckinlay@labs.interopen.org, ngtrans@sunroof.eng.sun.com, 6bone@ISI.EDU
Subject: (ngtrans) Re: SOCKS64: An implementation of SOCKS based IPv6/IPv4 Gateway
 Mechanism
From: KOBAYASHI Shinji <koba@flab.fujitsu.co.jp>
In-Reply-To: Your message of "Thu, 23 Mar 2000 10:31:15 +0000 (GMT)"
	<Pine.LNX.4.04.10003231030170.17388-100000@inet-gw0.labs.ekto.org>
References: <Pine.LNX.4.04.10003231030170.17388-100000@inet-gw0.labs.ekto.org>
X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000324102720N.koba@flab.fujitsu.co.jp>
Date: Fri, 24 Mar 2000 10:27:20 +0900
X-Dispatcher: imput version 980905(IM100)
Lines: 15
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: KOBAYASHI Shinji <koba@flab.fujitsu.co.jp>
Content-Transfer-Encoding: 7bit


>>>>> "Mo" == Mo McKinlay <mmckinlay@labs.interopen.org> writes:

Mo> Is there a WWW URL for this? I'd be quite interested in reading about it
Mo> before embarking on a hefty download :-)

Sorry, currently no english page is available. Client setup
information in Japanese is available at:

http://www.pds-flab.rwcp.or.jp/SOCKS64/

socks64-v10r10-20000322.tgz is only 34KB, so please try to download it. :-)

Kobayashi Shinji
koba@flab.fujitsu.co.jp


From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 28 07:21:56 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20104
	for <ngtrans-archive@odin.ietf.org>; Tue, 28 Mar 2000 07:21:55 -0500 (EST)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA00881;
	Tue, 28 Mar 2000 05:20:43 -0700 (MST)
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 EAA12719;
	Tue, 28 Mar 2000 04:20:00 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2SCJB421438
	for ngtrans-dist; Tue, 28 Mar 2000 04:19:11 -0800 (PST)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2SCJ0N21429
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 04:19:00 -0800 (PST)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6) with ESMTP id EAA11110
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 04:18:59 -0800 (PST)
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA00024
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 05:18:58 -0700 (MST)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with ESMTP id OAA13376
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 14:18:56 +0200 (MET DST)
Received: from leibniz.danubius by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id OAA12204; Tue, 28 Mar 2000 14:18:54 +0200 (MET DST)
Received: from eth.ericsson.se (localhost [127.0.0.1])
	by leibniz.danubius (8.8.8+Sun/8.8.8) with ESMTP id OAA01084
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 14:18:54 +0200 (MET DST)
Message-ID: <38E0A32E.24156CA7@eth.ericsson.se>
Date: Tue, 28 Mar 2000 14:18:54 +0200
From: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
X-Mailer: Mozilla 4.61 [en] (X11; I; SunOS 5.6 sun4m)
X-Accept-Language: en
MIME-Version: 1.0
To: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: (ngtrans) What happened to AIIH?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Content-Transfer-Encoding: 7bit

Hi,

the latest draft I saw on AIIH was to expire in June 1999. Now it has
completely disappeared: there isn't a newer version on the IETF home
page, and I couldn't find an RFC on it either. What happened to AIIH?

                    Kornel



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 28 07:37: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 HAA20243
	for <ngtrans-archive@odin.ietf.org>; Tue, 28 Mar 2000 07:37:01 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA06690;
	Tue, 28 Mar 2000 05:36:17 -0700 (MST)
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 EAA15983;
	Tue, 28 Mar 2000 04:35:54 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2SCYs021487
	for ngtrans-dist; Tue, 28 Mar 2000 04:34:54 -0800 (PST)
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2SCYkN21480
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 04:34:46 -0800 (PST)
Received: from lillen ([192.9.10.203])
	by jurassic.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with SMTP id e2SCYhG875942;
	Tue, 28 Mar 2000 04:34:44 -0800 (PST)
Date: Tue, 28 Mar 2000 04:29:43 -0800 (PST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: (ngtrans) What happened to AIIH?
To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
In-Reply-To: "Your message with ID" <38E0A32E.24156CA7@eth.ericsson.se>
Message-ID: <Roam.SIMC.2.0.6.954246583.3298.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>


AIIH is alive and well.

Look at draft-ietf-ngtrans-dstm-01.txt.

  Erik



From owner-ngtrans@sunroof.eng.sun.com  Tue Mar 28 10:24:49 2000
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22067
	for <ngtrans-archive@odin.ietf.org>; Tue, 28 Mar 2000 10:24:49 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA04976;
	Tue, 28 Mar 2000 08:23:09 -0700 (MST)
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 HAA29367;
	Tue, 28 Mar 2000 07:22:34 -0800 (PST)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) id e2SFL7O21543
	for ngtrans-dist; Tue, 28 Mar 2000 07:21:07 -0800 (PST)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.10.1.Beta0+Sun/8.10.1.Beta0) with ESMTP id e2SFKxN21536
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 07:21:00 -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 HAA28836
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 07:21:00 -0800 (PST)
Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42])
	by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA16828
	for <ngtrans@sunroof.eng.sun.com>; Tue, 28 Mar 2000 07:20:59 -0800 (PST)
Received: by mailext04.compaq.com (Postfix, from userid 12345)
	id 6B000104BC4; Tue, 28 Mar 2000 09:20:55 -0600 (CST)
Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35])
	by mailext04.compaq.com (Postfix) with ESMTP
	id 6458FFB101; Tue, 28 Mar 2000 09:20:55 -0600 (CST)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345)
	id EE0394D404; Tue, 28 Mar 2000 09:20:48 -0600 (CST)
Received: from anw.zk3.dec.com (wasted.zk3.dec.com [16.140.32.3])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP
	id 8DBF743982; Tue, 28 Mar 2000 09:20:48 -0600 (CST)
Received: from localhost by anw.zk3.dec.com (8.9.3/1.1.22.2/08Sep98-0251PM)
	id KAA0000654832; Tue, 28 Mar 2000 10:20:54 -0500 (EST)
From: Jim Bound <bound@zk3.dec.com>
Message-Id: <200003281520.KAA0000654832@anw.zk3.dec.com>
To: Kornel Szegedi <Kornel.Szegedi@eth.ericsson.se>
Cc: "'ngtrans@sunroof.eng.sun.com'" <ngtrans@sunroof.eng.sun.com>
Subject: Re: (ngtrans) What happened to AIIH? 
In-reply-to: Your message of "Tue, 28 Mar 2000 14:18:54 +0200."
             <38E0A32E.24156CA7@eth.ericsson.se> 
Date: Tue, 28 Mar 2000 10:20:54 -0500
X-Mts: smtp
Sender: owner-ngtrans@sunroof.eng.sun.com
Precedence: bulk
Reply-To: Jim Bound <bound@zk3.dec.com>

AIIH is now part of DSTM.
thanks
/jim


