From ipv6-bounces@ietf.org Fri Jun 01 08:11:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu5yc-0003l5-9Z; Fri, 01 Jun 2007 08:11:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hts8I-0006dI-VK
	for ipv6@ietf.org; Thu, 31 May 2007 17:24:34 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hts8H-0006M1-PE
	for ipv6@ietf.org; Thu, 31 May 2007 17:24:34 -0400
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.33247665;
	Thu, 31 May 2007 17:24:08 -0400
Message-ID: <465F3CF9.3030409@innovationslab.net>
Date: Thu, 31 May 2007 17:24:09 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0705281139x1eb48a22t762e8f5e2abcd184@mail.gmail.com>	
	<77ead0ec0705291054w2f0fff50j70efa5d84e4685c4@mail.gmail.com>	
	<m17iqrl091.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<77ead0ec0705291740m1230df50u60571d81df4cc02e@mail.gmail.com>	
	<m14plul6za.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<77ead0ec0705300932q72773378kefe758103ead5c10@mail.gmail.com>	
	<m13b1ekyc0.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<77ead0ec0705301048p33af7c0bqa952a0d99042f6a0@mail.gmail.com>	
	<m1tzttk3eg.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<465EE66D.8010904@innovationslab.net>
	<77ead0ec0705311049y1e14d24ew7a3def802e8f7aec@mail.gmail.com>
In-Reply-To: <77ead0ec0705311049y1e14d24ew7a3def802e8f7aec@mail.gmail.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Fri, 01 Jun 2007 08:11:28 -0400
Cc: ipv6@ietf.org, manoj@ipinfusion.com, Markku Savela <msa@burp.tkv.asdf.org>,
	Pekka Savola <pekkas@netcore.fi>,
	=?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Destination options attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Vishwas Manral wrote:
> Hi Brian/ Jinmei,
> 
> What about the case of having such malicious packets tunnelled inside
> unicast packets?

The multicast address and the victim source address still need to be
known along with the multicast tree topology in order to make the attack
work.  It may help to have some kind of sketch of the topology, along
with the tunnel endpoints to make sure everyone understands the scenario
you are worried about.

Are you assuming that any arbitrary router/node will decapsulate your
packet?

> 
>> > that case the returned ICMPv6 messages will most likely be forwarded
>> > by the attacking router
> I feel two points are totally missed in the argument here. Forwarding
> traffic is generally done in the hardware by ASIC's while thats not
> the case of packets that need to be processed. So any router in the
> middle will not process the packet so will not be overwhelmed.

I am not sure what you mean here.

> 
> The second more interesting case is again, a malicious device can
> attack any router upstream of a router in its same network too.

A diagram would help me understand your concern.

Regards,
Brian



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 01 09:17:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu70W-0006rM-MH; Fri, 01 Jun 2007 09:17:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hu70U-0006p8-Kn; Fri, 01 Jun 2007 09:17:31 -0400
Received: from [202.99.23.227] (helo=people.com.cn)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1Hu70S-00036h-PQ; Fri, 01 Jun 2007 09:17:30 -0400
Received: from people.com.cn([127.0.0.1]) by people.com.cn(AIMC 2.9.5.8)
	with SMTP id jm8546606684; Fri, 01 Jun 2007 21:28:27 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id jm73465b901b; Tue, 29 May 2007 03:28:00 +0800
Received: from megatron.ietf.org([156.154.16.145]) by people.com.cn(AIMC
	2.9.5.8) with SMTP id AISP action; Tue, 29 May 2007 03:28:00 +0800
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HskJh-000497-1S; Mon, 28 May 2007 14:51:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HskJd-00043n-Ve; Mon, 28 May 2007 14:51:38 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HskJc-0003kd-Ly; Mon, 28 May 2007 14:51:37 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9BD6E2AC8F;
	Mon, 28 May 2007 18:51:06 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HskJ8-0007rt-Cw; Mon, 28 May 2007 14:51:06 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HskJ8-0007rt-Cw@stiedprstage1.ietf.org>
Date: Mon, 28 May 2007 14:51:06 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: ietf-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: iesg-secretary@ietf.org
X-Auto-Forward: jaglee@people.com.cn
 jag@kw.com.cn
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: Internet Architecture Board <iab@iab.org>,
	ipv6 mailing list <ipv6@ietf.org>, ipv6 chair <ipv6-chairs@tools.ietf.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'IP Version 6 over PPP' to Draft Standard 
X-BeenThere: ipv6@ietf.org
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

The IESG has approved the following document:

- 'IP Version 6 over PPP '
   <draft-ietf-ipv6-over-ppp-v2-03.txt> as a Draft Standard

This document is the product of the IP Version 6 Working Group Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt

Technical Summary
 
  The Point-to-Point Protocol (PPP) provides a standard method of 
  encapsulating Network Layer protocol information over  
  point-to-point links.  PPP also defines an extensible Link Control  
  Protocol, and proposes a family of Network Control Protocols  
  (NCPs) for establishing and configuring different network-layer  
  protocols. 
    
  This document defines the method for sending IPv6 packets over PPP 
  links, the NCP for establishing and configuring the IPv6 over PPP  
  and the method for forming IPv6 link-local addresses on PPP links. 
  It also specifies the conditions for performing Duplicate Address 
  Detection on IPv6 global unicast addresses configured for PPP 
  links either through stateful or stateless address 
  autoconfiguration. 

Working Group Summary
 
  The IPv6 working group has reviewed this document and it
  reflects the consensus of the group.
 
Protocol Quality
 
  This specification has been reviewed for the IESG by
  Margaret Wasserman. In the working group, it was
  reviewed by the members of the mailing list and by
  the working group chairs.

Note to RFC Editor

  Please move reference [4] (IANA assigned numbers)
  to be informative.

  Please replace reference [5] with the following:

     [5] IEEE, "Guidelines For 64-bit Global Identifier (EUI-64)", 
         http://standards.ieee.org/regauth/oui/tutorials/EUI64.html


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 02 20:00:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HudVu-0007Qg-MW; Sat, 02 Jun 2007 20:00:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HudVt-0007Qb-W4
	for ipv6@ietf.org; Sat, 02 Jun 2007 20:00:05 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HudVt-0001s9-Kp
	for ipv6@ietf.org; Sat, 02 Jun 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id D701F28429
	for <ipv6@ietf.org>; Sun,  3 Jun 2007 00:00:02 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 03 Jun 2007 00:00:02 +0000
Message-Id: <20070603000002.D701F28429@cyteen.hactrn.net>
X-Spam-Score: -0.9 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 20.00% |    8 | 19.55% |    51117 | vishwas.ietf@gmail.com
 15.00% |    6 | 13.35% |    34907 | jinmei@isl.rdc.toshiba.co.jp
 15.00% |    6 | 11.60% |    30333 | pekkas@netcore.fi
 10.00% |    4 |  7.73% |    20222 | brian@innovationslab.net
  2.50% |    1 | 14.84% |    38800 | jabley@ca.afilias.info
  7.50% |    3 |  6.94% |    18157 | suresh.krishnan@ericsson.com
  7.50% |    3 |  5.45% |    14265 | itojun@itojun.org
  5.00% |    2 |  3.69% |     9652 | gnn@neville-neil.com
  2.50% |    1 |  4.24% |    11101 | arnaud.ebalard@eads.net
  2.50% |    1 |  3.10% |     8112 | volz@cisco.com
  2.50% |    1 |  2.22% |     5807 | bob.hinden@nokia.com
  2.50% |    1 |  1.95% |     5108 | iesg-secretary@ietf.org
  2.50% |    1 |  1.95% |     5106 | brian.e.carpenter@gmail.com
  2.50% |    1 |  1.78% |     4667 | mailman-owner@ietf.org
  2.50% |    1 |  1.59% |     4171 | sra+ipng@hactrn.net
--------+------+--------+----------+------------------------
100.00% |   40 |100.00% |   261525 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 03 14:34:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuutZ-0003V1-GG; Sun, 03 Jun 2007 14:33:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HuutX-0003Uw-9l
	for ipv6@ietf.org; Sun, 03 Jun 2007 14:33:39 -0400
Received: from nz-out-0506.google.com ([64.233.162.232])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuutW-0002mi-24
	for ipv6@ietf.org; Sun, 03 Jun 2007 14:33:39 -0400
Received: by nz-out-0506.google.com with SMTP id z31so789182nzd
	for <ipv6@ietf.org>; Sun, 03 Jun 2007 11:33:37 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=nbOyMwCfBugd+AF7qz3XdkKUN12SyMbVDIoaE6ZpfTGG3sd7tB/9sy0gtIhST3ADPLDwL9yQlZ9AUiaPAmDSkPO+YKLsNQGQhMl+XzN+EpcZ26KeVcGEVqKhQ2fwjYBLWXOX9Ev0Wz9Cam8ZpnJwHruGO4pCeTtUOyqsLD12ap4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=Z+XPQBOf7nnBtFQ4ca8j+IlcKhDrLH/wiPGpe1QFR1Fa+cSLYHUJjfXVLSNCnWrVzhT65kL1MEl5FSBGheZifa/d1ukxRj/sHqSFCK+wDFrCylBbc6Yt6/hE6L78/NgMmjdk/4nFBDr9VXxnckogP9DAye0pPvL7dRWuTznZq60=
Received: by 10.115.32.1 with SMTP id k1mr4014889waj.1180895617235;
	Sun, 03 Jun 2007 11:33:37 -0700 (PDT)
Received: by 10.114.24.9 with HTTP; Sun, 3 Jun 2007 11:33:37 -0700 (PDT)
Message-ID: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
Date: Sun, 3 Jun 2007 11:33:37 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: ipv6@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

We have posted a draft which checks for loops in the source routed
header. It works for nearly all the cases. The reason is in case a new
header is added to replace the RH0, or if the RH0 is not deprecated
(for reasons that it is required by the management) then we can as
well use the checks in the RH0 header itself.

Such packets should however be rate limited and such checks will
probably best be performed by software.

http://www.ietf.org/internet-drafts/draft-manral-ipv6-detecting-loops-rh-01.txt

Thanks,
Vishwas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 03 15:11:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HuvTy-0001wq-5g; Sun, 03 Jun 2007 15:11:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HuvTu-0001wj-AE
	for ipv6@ietf.org; Sun, 03 Jun 2007 15:11:15 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HuvTs-0005YE-MY
	for ipv6@ietf.org; Sun, 03 Jun 2007 15:11:14 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id C31C2140C00E;
	Sun,  3 Jun 2007 21:11:11 +0200 (CEST)
Message-ID: <46631250.30407@spaghetti.zurich.ibm.com>
Date: Sun, 03 Jun 2007 20:11:12 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
In-Reply-To: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
X-Enigmail-Version: 0.95.0
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.2,
	clamav-milter version 0.90.2 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1280645156=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1280645156==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig1E0B4D5BE3A210B432E6F439"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1E0B4D5BE3A210B432E6F439
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Vishwas Manral wrote:
> Hi,
>=20
> We have posted a draft which checks for loops in the source routed
> header. It works for nearly all the cases. The reason is in case a new
> header is added to replace the RH0, or if the RH0 is not deprecated
> (for reasons that it is required by the management) then we can as
> well use the checks in the RH0 header itself.
>=20
> Such packets should however be rate limited and such checks will
> probably best be performed by software.
>=20
> http://www.ietf.org/internet-drafts/draft-manral-ipv6-detecting-loops-r=
h-01.txt

Properly configured uRPF already solves most of the routing loops.

Section 3 very shortly describes a method of 'checking if the packet
goes through a router twice', but it doesn't actually explain how it
can be accomplished, it only explains that one can't because there is
no 'routing identifier'.

The second paragraph of section 3 in effect describes performing uRPF
on the RH0 header.

Also, if you would check for a loop, the typical "management" use of
RH0 (read: traceroute6) stops working, as in most cases the packet
will come back over the same path as it was sent.

Greets,
 Jeroen


--------------enig1E0B4D5BE3A210B432E6F439
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZjElAuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58Iyh8AJ9ycIWgPsCcsuWCbK3Ry5LEcGNX
tgCfWvp0SMr96IEceiGFMd21z1hLSuY=
=JJKM
-----END PGP SIGNATURE-----

--------------enig1E0B4D5BE3A210B432E6F439--


--===============1280645156==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1280645156==--




From ipv6-bounces@ietf.org Sun Jun 03 22:21:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv2BW-0005dP-Ar; Sun, 03 Jun 2007 22:20:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv2BU-0005dK-MB
	for ipv6@ietf.org; Sun, 03 Jun 2007 22:20:40 -0400
Received: from wa-out-1112.google.com ([209.85.146.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv2BR-0005Hq-Bo
	for ipv6@ietf.org; Sun, 03 Jun 2007 22:20:40 -0400
Received: by wa-out-1112.google.com with SMTP id j5so199697wah
	for <ipv6@ietf.org>; Sun, 03 Jun 2007 19:20:36 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=o+Dvb10dhXD31Rc8va89vN6uw8aU+XH5kj4HZoawDH/SLjWWtWGFlRTpe9eUdyw4/pSLfFzH1ffJvbbqLMDmdeO41VOT1mQAdHnNRPOXhPJ3NkxEmfOcY8CNaqf/brUl+h8zCRoLeBJaZLkvDPSzXGba7G0H69RFNUYLTqVFc6k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=eovH8QKsSQ8qsdp9iFsQyJb27w6srAZT8DJAm6ZFcppd+ZpPtL3T+vfkIOFgHwQTkDXy4dUVU9vkcKSX+x2XPEOr63F3HHs2CV0lfva5/BQCphRK19r1v9r2DdMzEQxb/ia7NO2xSkQatWoxN0V7GfbNC27wGYUbgl9oM3jM8oE=
Received: by 10.114.124.1 with SMTP id w1mr4289902wac.1180923636455;
	Sun, 03 Jun 2007 19:20:36 -0700 (PDT)
Received: by 10.114.24.9 with HTTP; Sun, 3 Jun 2007 19:20:36 -0700 (PDT)
Message-ID: <77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
Date: Sun, 3 Jun 2007 19:20:36 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Jeroen Massar" <jeroen@unfix.org>
In-Reply-To: <46631250.30407@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jeoren,

The idea is that for every router the packet goes through, we need to
check the IP address of all the interface addresses, and make sure
that the none of the interface address either before or after in the
source routing header match any of the IP address of the packet.

Yes RPF check could be helpful too. But I am unsure how it would
behave in case of ECMP other other anomaly cases.

Thanks,
Vishwas

On 6/3/07, Jeroen Massar <jeroen@unfix.org> wrote:
> Vishwas Manral wrote:
> > Hi,
> >
> > We have posted a draft which checks for loops in the source routed
> > header. It works for nearly all the cases. The reason is in case a new
> > header is added to replace the RH0, or if the RH0 is not deprecated
> > (for reasons that it is required by the management) then we can as
> > well use the checks in the RH0 header itself.
> >
> > Such packets should however be rate limited and such checks will
> > probably best be performed by software.
> >
> > http://www.ietf.org/internet-drafts/draft-manral-ipv6-detecting-loops-rh-01.txt
>
> Properly configured uRPF already solves most of the routing loops.
>
> Section 3 very shortly describes a method of 'checking if the packet
> goes through a router twice', but it doesn't actually explain how it
> can be accomplished, it only explains that one can't because there is
> no 'routing identifier'.
>
> The second paragraph of section 3 in effect describes performing uRPF
> on the RH0 header.
>
> Also, if you would check for a loop, the typical "management" use of
> RH0 (read: traceroute6) stops working, as in most cases the packet
> will come back over the same path as it was sent.
>
> Greets,
>  Jeroen
>
>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 03 23:02:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv2pH-0007ql-J6; Sun, 03 Jun 2007 23:01:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv2pF-0007qd-Pf
	for ipv6@ietf.org; Sun, 03 Jun 2007 23:01:45 -0400
Received: from nz-out-0506.google.com ([64.233.162.235])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv2pE-0001V7-Fi
	for ipv6@ietf.org; Sun, 03 Jun 2007 23:01:45 -0400
Received: by nz-out-0506.google.com with SMTP id z31so856430nzd
	for <ipv6@ietf.org>; Sun, 03 Jun 2007 20:01:44 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=eVGjIOsLoAsEzvle8cGzfplr+7qwI7En3WTM2sjS71AMNfTSv60ug7tSXiZ+EqzMnFkuDd7CVsQ4HWTQut92smDV9agtqXFtwlO7xlNVc9jQBbtNAvll1/BNL98llqsdqjamdwNPDSUzxt5TGbSydiIBFGL0kqpO8gnTHIRIaVs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Qn4+X1YwHb2dX14u+oEo03cSH6lBftVwul1XDJsFOceF/xYcHblLbdFEgGsib2NzEoAFtbj+Jb1th6DTAr8SPVW0dZ7gQza0OSOsEKnuVJ/qonDFyxxXYeZCOjoqn2I71t5CjcaTKC+HcuPIYjXspB4Dn/mnu0ocIYMX1IJG4U8=
Received: by 10.114.27.20 with SMTP id a20mr4325553waa.1180926103861;
	Sun, 03 Jun 2007 20:01:43 -0700 (PDT)
Received: by 10.114.24.9 with HTTP; Sun, 3 Jun 2007 20:01:43 -0700 (PDT)
Message-ID: <77ead0ec0706032001g423ebc54l2a0f38c57dd905e1@mail.gmail.com>
Date: Sun, 3 Jun 2007 20:01:43 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Jeroen Massar" <jeroen@unfix.org>
In-Reply-To: <77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Joeren,

After thinking a while I realized that, by talking about RPF
everywhere you miss a very basic point. Internet routing is
essentially assymetric in nature. So the path taken for a packet from
source A to B is not the same as one taken from B to A. RPF works at
the edge in my view but not on all routers. Having worked on routing
protocols I know that for a fact.

Do let me know what you think?

Thanks,
Vishwas

On 6/3/07, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi Jeoren,
>
> The idea is that for every router the packet goes through, we need to
> check the IP address of all the interface addresses, and make sure
> that the none of the interface address either before or after in the
> source routing header match any of the IP address of the packet.
>
> Yes RPF check could be helpful too. But I am unsure how it would
> behave in case of ECMP other other anomaly cases.
>
> Thanks,
> Vishwas
>
> On 6/3/07, Jeroen Massar <jeroen@unfix.org> wrote:
> > Vishwas Manral wrote:
> > > Hi,
> > >
> > > We have posted a draft which checks for loops in the source routed
> > > header. It works for nearly all the cases. The reason is in case a new
> > > header is added to replace the RH0, or if the RH0 is not deprecated
> > > (for reasons that it is required by the management) then we can as
> > > well use the checks in the RH0 header itself.
> > >
> > > Such packets should however be rate limited and such checks will
> > > probably best be performed by software.
> > >
> > > http://www.ietf.org/internet-drafts/draft-manral-ipv6-detecting-loops-rh-01.txt
> >
> > Properly configured uRPF already solves most of the routing loops.
> >
> > Section 3 very shortly describes a method of 'checking if the packet
> > goes through a router twice', but it doesn't actually explain how it
> > can be accomplished, it only explains that one can't because there is
> > no 'routing identifier'.
> >
> > The second paragraph of section 3 in effect describes performing uRPF
> > on the RH0 header.
> >
> > Also, if you would check for a loop, the typical "management" use of
> > RH0 (read: traceroute6) stops working, as in most cases the packet
> > will come back over the same path as it was sent.
> >
> > Greets,
> >  Jeroen
> >
> >
> >
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 04 01:14:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hv4tC-0002SK-7i; Mon, 04 Jun 2007 01:13:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hv4t9-0002S4-Eb
	for ipv6@ietf.org; Mon, 04 Jun 2007 01:13:55 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hv4t7-0003fQ-Rw
	for ipv6@ietf.org; Mon, 04 Jun 2007 01:13:55 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l545DnZn031271;
	Mon, 4 Jun 2007 08:13:49 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l545DmCP031268;
	Mon, 4 Jun 2007 08:13:48 +0300
Date: Mon, 4 Jun 2007 08:13:48 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vishwas Manral <vishwas.ietf@gmail.com>
In-Reply-To: <77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0706040806240.31082@netcore.fi>
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="1589707168-1003748326-1180934028=:31082"
X-Virus-Scanned: ClamAV 0.90.2/3347/Mon Jun 4 02:00:51 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1589707168-1003748326-1180934028=:31082
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by netcore.fi id
	l545DnZn031271

On Sun, 3 Jun 2007, Vishwas Manral wrote:
> The idea is that for every router the packet goes through, we need to
> check the IP address of all the interface addresses, and make sure
> that the none of the interface address either before or after in the
> source routing header match any of the IP address of the packet.

Not sure whether this is worth doing in the first place, but just to=20
get the story straight:

By 'goes through', do you also intermediate routers which are do not=20
need to process the routing header in any way (i.e.: are never in=20
"Destination Address" field of the routing header)?

If yes, this would require punting packets from hardware forwarding to=20
the control processor which is IMHO a non-starter.

> Yes RPF check could be helpful too. But I am unsure how it would=20
> behave in case of ECMP other other anomaly cases.

Maybe Jeroen meant to refer to ingress/egress filtering in general,=20
not just uRPF.  Strict uRPF is usually applied around the edges of the=20
network (where the size and definion of 'network' varies).  Other=20
kinds of ingress/egress ACLs (usually static / automatically generated=20
ones) can be better applied at peering/upstream/etc. borders.  Having=20
such ACLs prevents almost all RH0 looping abuse.  (There is a scenario=20
Gert D=F6ring mentioned where you loop between backbone routers within=20
the target organization but that can be eliminated by disabling RH0=20
processing in that organization's routers' control plane).

--=20
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--1589707168-1003748326-1180934028=:31082
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--1589707168-1003748326-1180934028=:31082--




From ipv6-bounces@ietf.org Mon Jun 04 11:23:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvEOh-0007wr-Jj; Mon, 04 Jun 2007 11:23:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvEOf-0007wm-Ou
	for ipv6@ietf.org; Mon, 04 Jun 2007 11:23:05 -0400
Received: from nz-out-0506.google.com ([64.233.162.230])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvEOe-0004Mo-G5
	for ipv6@ietf.org; Mon, 04 Jun 2007 11:23:05 -0400
Received: by nz-out-0506.google.com with SMTP id z31so1022769nzd
	for <ipv6@ietf.org>; Mon, 04 Jun 2007 08:23:04 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=PtzxzI1m5rNAmhD1Q+8sJWqvnBgHFVfKiqoCjhaDkYnl0K+lTlLmPl9XpF8B1+ns1ClbekBBAmsZh61W8+oFHGmpOEVnqVDGHShJkr8oRnfjJXiBi2rStpIxVpDWRmKWKeVyFGSg1yON6b6spQ9k+nnpMabYis6DMhrRskVbmB8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=o6J2nuCAvPtHXbWszkLmWmWCSOIOxchX0C5qJ+B1JAOBv6Flj645dwFLTr7Rd7wNthuF1HS4hS9kMun5LrvFqceOBtRa2+JtED7GJU4XEJC5AA3mRgGTA3LtXk5urec+iIdezUIPrsgK0R1v12WZ5A/cn92bbOHKuBwZPNl2JmY=
Received: by 10.115.32.1 with SMTP id k1mr4941014waj.1180970583575;
	Mon, 04 Jun 2007 08:23:03 -0700 (PDT)
Received: by 10.114.24.9 with HTTP; Mon, 4 Jun 2007 08:23:03 -0700 (PDT)
Message-ID: <77ead0ec0706040823n17961373rc183e5afa1ffbfc3@mail.gmail.com>
Date: Mon, 4 Jun 2007 08:23:03 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Pekka Savola" <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706040806240.31082@netcore.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
	<Pine.LNX.4.64.0706040806240.31082@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Pekka,

> By 'goes through', do you also intermediate routers which are do not
> need to process the routing header in any way (i.e.: are never in
> "Destination Address" field of the routing header)?
>
> If yes, this would require punting packets from hardware forwarding to
> the control processor which is IMHO a non-starter.
Having a background on ASIC design for packet forwarding, I believe
that is exactly what is done for packets that need to be processed in
some exceptional behavior. Its a very very normal case. The other case
is to process the packets in the embedded processors, using some
firmware.

Can you explain why the above design is a non-starter?

Thanks,
Vishwas

On 6/3/07, Pekka Savola <pekkas@netcore.fi> wrote:
> On Sun, 3 Jun 2007, Vishwas Manral wrote:
> > The idea is that for every router the packet goes through, we need to
> > check the IP address of all the interface addresses, and make sure
> > that the none of the interface address either before or after in the
> > source routing header match any of the IP address of the packet.
>
> Not sure whether this is worth doing in the first place, but just to
> get the story straight:
>
> By 'goes through', do you also intermediate routers which are do not
> need to process the routing header in any way (i.e.: are never in
> "Destination Address" field of the routing header)?
>
> If yes, this would require punting packets from hardware forwarding to
> the control processor which is IMHO a non-starter.
>
> > Yes RPF check could be helpful too. But I am unsure how it would
> > behave in case of ECMP other other anomaly cases.
>
> Maybe Jeroen meant to refer to ingress/egress filtering in general,
> not just uRPF.  Strict uRPF is usually applied around the edges of the
> network (where the size and definion of 'network' varies).  Other
> kinds of ingress/egress ACLs (usually static / automatically generated
> ones) can be better applied at peering/upstream/etc. borders.  Having
> such ACLs prevents almost all RH0 looping abuse.  (There is a scenario
> Gert D=F6ring mentioned where you loop between backbone routers within
> the target organization but that can be eliminated by disabling RH0
> processing in that organization's routers' control plane).
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 04 12:00:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvEyy-0007mB-PA; Mon, 04 Jun 2007 12:00:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvEyh-0006wd-9c
	for ipv6@ietf.org; Mon, 04 Jun 2007 12:00:19 -0400
Received: from ns2.its.eads.net ([193.56.40.67] helo=mx2.its.eads.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvEyf-0004Vu-Sd
	for ipv6@ietf.org; Mon, 04 Jun 2007 12:00:19 -0400
Received: from fr-gate2.mailhub.intra.corp ([53.154.16.34]) by
	mx2.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); 
	Mon, 4 Jun 2007 17:57:51 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate2.mailhub.intra.corp
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 4 Jun 2007 18:03:07 +0200
Received: from [172.16.23.108] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id H92Z3FW7; Mon, 4 Jun 2007 18:00:33 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-Mailer: Apple Mail (2.752.2)
Content-class: urn:content-classes:message
Date: Mon, 4 Jun 2007 17:59:59 +0200
Message-ID: <F820FC4D-8215-42AC-80E4-0742CFA119D1@eads.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Checks for amplification attack
Thread-Index: AcemwXteSziXsn0QSdOMJulAFdwU4Q==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 04 Jun 2007 16:03:07.0499 (UTC)
	FILETIME=[D75613B0:01C7A6C1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Vishwas,

Le 4 juin 07 =E0 04:20, Vishwas Manral a =E9crit :

> The idea is that for every router the packet goes through, we need to
> check the IP address of all the interface addresses, and make sure
> that the none of the interface address either before or after in the
> source routing header match any of the IP address of the packet.

Can you tell me if I understand correctly by commenting that example: =20
for every packet that includes a Routing Header with something like =20
88 addresses in it (feasible with a 1500 PMTU), a router with 5 =20
addresses will check every address it is configured with against =20
those 88 ones (440 comparisons). With 100 Mbit/s of traffic, the =20
router can see almost 9000 such packets per second. Where I come is =20
that it will have to perform something like 4 millions IPv6 address =20
comparison per sec, and in slow path. Is that correct ?

Regards,

a+

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 04 12:34:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvFVs-0007jV-SU; Mon, 04 Jun 2007 12:34:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvFVr-0007jQ-GL
	for ipv6@ietf.org; Mon, 04 Jun 2007 12:34:35 -0400
Received: from nz-out-0506.google.com ([64.233.162.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvFVq-00083M-8T
	for ipv6@ietf.org; Mon, 04 Jun 2007 12:34:35 -0400
Received: by nz-out-0506.google.com with SMTP id z31so1045119nzd
	for <ipv6@ietf.org>; Mon, 04 Jun 2007 09:34:33 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=NvYG1jhrkZwuuJGPuqL8VpFp7FDxgLC4CI4Y8wgAwRi6FU2oEDEESvJ8/PyD/pNXB/aDyL4/5OrKdTn7Z9F07SL15lw5OnoHXc7tOnGEG3In3ln9wvmQ8mRd8+e+2r+HYNSMOQWQu2ziLTINtd8y6IqWsKVXiW3ozHk3wDn1jOQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Mt4IznW8vtsolddkhrh61u0qScI8+GFcP2z9ajfllnXl+RKda//kkVsvLKOsyxtFKwsnREeiyuWowVHTA5J/Z/AWix4+jqPATgzDzMb+D7Ag2aPO7D0ujxS2KKqceZ/rbHw0yIK4pILOvhAhsAjZCBlMX3clzOc/UxlI2Meu/z4=
Received: by 10.114.79.1 with SMTP id c1mr4991468wab.1180974873150;
	Mon, 04 Jun 2007 09:34:33 -0700 (PDT)
Received: by 10.114.24.9 with HTTP; Mon, 4 Jun 2007 09:34:33 -0700 (PDT)
Message-ID: <77ead0ec0706040934s5100f812v4eb78f6af4ec8571@mail.gmail.com>
Date: Mon, 4 Jun 2007 09:34:33 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
In-Reply-To: <F820FC4D-8215-42AC-80E4-0742CFA119D1@eads.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
	<F820FC4D-8215-42AC-80E4-0742CFA119D1@eads.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Arnaud,

You nearly got it right. Only small thing however is such packets will
be rate limited to the CPU (software), so we will drop all packets not
conforming to the rate limiting.

The reason it will be used is only for management purposes only (hence
the header should never be used for data traffic - which seems like
the only reason why people want to use the routing header).

Thanks,
Vishwas

On 6/4/07, Ebalard, Arnaud <Arnaud.Ebalard@eads.net> wrote:
> Hi Vishwas,
>
> Le 4 juin 07 =E0 04:20, Vishwas Manral a =E9crit :
>
> > The idea is that for every router the packet goes through, we need to
> > check the IP address of all the interface addresses, and make sure
> > that the none of the interface address either before or after in the
> > source routing header match any of the IP address of the packet.
>
> Can you tell me if I understand correctly by commenting that example:
> for every packet that includes a Routing Header with something like
> 88 addresses in it (feasible with a 1500 PMTU), a router with 5
> addresses will check every address it is configured with against
> those 88 ones (440 comparisons). With 100 Mbit/s of traffic, the
> router can see almost 9000 such packets per second. Where I come is
> that it will have to perform something like 4 millions IPv6 address
> comparison per sec, and in slow path. Is that correct ?
>
> Regards,
>
> a+
>
> -- Arnaud Ebalard
> EADS Innovation Works - IT Sec Research Engineer
> PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026
>
>
>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 04 13:14:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvG8P-0005P8-LD; Mon, 04 Jun 2007 13:14:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvG8O-0005P3-3k
	for ipv6@ietf.org; Mon, 04 Jun 2007 13:14:24 -0400
Received: from ns1.its.eads.net ([193.56.40.66] helo=mx1.its.eads.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvG8M-0004Yd-O2
	for ipv6@ietf.org; Mon, 04 Jun 2007 13:14:24 -0400
Received: from fr-gate2.mailhub.intra.corp ([53.154.16.34]) by
	mx1.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); 
	Mon, 4 Jun 2007 19:11:56 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate2.mailhub.intra.corp
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 4 Jun 2007 19:17:16 +0200
Received: from [172.16.23.108] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id H92Z3F6P; Mon, 4 Jun 2007 19:14:43 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-Mailer: Apple Mail (2.752.2)
Content-class: urn:content-classes:message
Date: Mon, 4 Jun 2007 19:14:42 +0200
Message-ID: <1DC4043D-7324-436F-A766-FC7B7F5B294A@eads.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Checks for amplification attack
Thread-Index: Acemy9g7t/sNL1WrRE+276aahotrHA==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 04 Jun 2007 17:17:16.0023 (UTC)
	FILETIME=[32DCF870:01C7A6CC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi again,

Le 4 juin 07 =E0 18:34, Vishwas Manral a =E9crit :

> You nearly got it right. Only small thing however is such packets will
> be rate limited to the CPU (software), so we will drop all packets not
> conforming to the rate limiting.

The packets you want to rate limit are the one addressed to the =20
router that include a RH0, not the one that are flowing through (dst =20
address of IPv6 packet is not one of the router), right ?

a+

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 05 02:26:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvSUQ-0006am-9o; Tue, 05 Jun 2007 02:25:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvSUP-0006ah-Mx
	for ipv6@ietf.org; Tue, 05 Jun 2007 02:25:57 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvSUP-0002zg-7L
	for ipv6@ietf.org; Tue, 05 Jun 2007 02:25:57 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l556Plek005071;
	Tue, 5 Jun 2007 09:25:47 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l556Plc5005068;
	Tue, 5 Jun 2007 09:25:47 +0300
Date: Tue, 5 Jun 2007 09:25:47 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vishwas Manral <vishwas.ietf@gmail.com>
In-Reply-To: <77ead0ec0706040823n17961373rc183e5afa1ffbfc3@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0706050922041.2967@netcore.fi>
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
	<Pine.LNX.4.64.0706040806240.31082@netcore.fi>
	<77ead0ec0706040823n17961373rc183e5afa1ffbfc3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 4 Jun 2007, Vishwas Manral wrote:
>>  By 'goes through', do you also intermediate routers which are do not
>>  need to process the routing header in any way (i.e.: are never in
>>  "Destination Address" field of the routing header)?
>>
>>  If yes, this would require punting packets from hardware forwarding to
>>  the control processor which is IMHO a non-starter.
>
> Having a background on ASIC design for packet forwarding, I believe
> that is exactly what is done for packets that need to be processed in
> some exceptional behavior. Its a very very normal case. The other case
> is to process the packets in the embedded processors, using some
> firmware.
>
> Can you explain why the above design is a non-starter?

As an operator, I do not wish to buy routers that are DoS'able or 
whose control processor CPU resources can be wasted on inspecting 
transiting traffic. "Punting packets to the slow path" is one primary 
thing that a high-speed router should not have to do.  I think I'm not 
alone in the operator field with this sentiment.

Oh yeah, hop-by-hop extension header should be retired as well :-)

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 05 05:26:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvVIN-0005zK-Sc; Tue, 05 Jun 2007 05:25:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvVIM-0005zE-T9
	for ipv6@ietf.org; Tue, 05 Jun 2007 05:25:42 -0400
Received: from mrout2-b.corp.dcn.yahoo.com ([216.109.112.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvVIL-0007iW-Nt
	for ipv6@ietf.org; Tue, 05 Jun 2007 05:25:42 -0400
Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com
	[216.145.48.13])
	by mrout2-b.corp.dcn.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id
	l559PYhP035057; Tue, 5 Jun 2007 02:25:35 -0700 (PDT)
Date: Tue, 05 Jun 2007 18:25:09 +0900
Message-ID: <m2hcpmah3e.wl%gnn@neville-neil.com>
From: "George V. Neville-Neil" <gnn@neville-neil.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m11wgykxdz.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<m18xb7llay.wl%jinmei@isl.rdc.toshiba.co.jp>
	<Pine.LNX.4.64.0705292131400.9157@netcore.fi>
	<m11wgykxdz.wl%jinmei@isl.rdc.toshiba.co.jp>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95
	(i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Pekka Savola <pekkas@netcore.fi>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Where are we on this draft at the moment?

Best,
George

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 05 11:19:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvanv-0001Pl-AK; Tue, 05 Jun 2007 11:18:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvant-0001Pg-Bn
	for ipv6@ietf.org; Tue, 05 Jun 2007 11:18:37 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvans-0007uu-27
	for ipv6@ietf.org; Tue, 05 Jun 2007 11:18:37 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HvaqQ-000KNe-DD; Tue, 05 Jun 2007 15:21:14 +0000
In-Reply-To: <m2hcpmah3e.wl%gnn@neville-neil.com>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<m18xb7llay.wl%jinmei@isl.rdc.toshiba.co.jp>
	<Pine.LNX.4.64.0705292131400.9157@netcore.fi>
	<m11wgykxdz.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m2hcpmah3e.wl%gnn@neville-neil.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DCC7A5C7-1A89-4101-B43A-2C7D26E3898E@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Tue, 5 Jun 2007 11:18:28 -0400
To: George V. Neville-Neil <gnn@neville-neil.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Pekka Savola <pekkas@netcore.fi>,
	=?UTF-8?Q?JINMEI_Tatuya_/_=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 5-Jun-2007, at 05:25, George V. Neville-Neil wrote:

> Where are we on this draft at the moment?

I was taken out of commission last week by an IAB retreat, and am  
currently trying to catch up on all the things I am behind on.  
Apologies for the delay. I aim to have a revised candidate on the  
list in the next day or two.


Joe


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 05 18:51:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvhrV-0000dM-Ny; Tue, 05 Jun 2007 18:50:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvhrF-00009a-Rb; Tue, 05 Jun 2007 18:50:34 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HvhrE-0000XF-EL; Tue, 05 Jun 2007 18:50:33 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 5F0282ACA7;
	Tue,  5 Jun 2007 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Hvhqk-0006ut-4M; Tue, 05 Jun 2007 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1Hvhqk-0006ut-4M@stiedprstage1.ietf.org>
Date: Tue, 05 Jun 2007 18:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipv6@ietf.org
Subject: I-D ACTION:draft-ietf-ipv6-ra-flags-option-00.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: IPv6 Router Advertisement Flags Option
	Author(s)	: B. Haberman, R. Hinden
	Filename	: draft-ietf-ipv6-ra-flags-option-00.txt
	Pages		: 7
	Date		: 2007-6-5
	
   The IPv6 Neighbor Discovery's Router Advertisement message contains
   an 8-bit field reserved for single-bit flags.  Several protocols have
   reserved flags in this field and others are preparing to reserve a
   sufficient number of flags to exhaust the field.  This document
   defines an option to the Router Advertisement message that expands
   the available number of flag bits available.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ra-flags-option-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ipv6-ra-flags-option-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-ipv6-ra-flags-option-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: <2007-6-5152730.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipv6-ra-flags-option-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-ipv6-ra-flags-option-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--NextPart--





From ipv6-bounces@ietf.org Tue Jun 05 23:41:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HvmNQ-0002qJ-BJ; Tue, 05 Jun 2007 23:40:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HvmNP-0002qB-6M
	for ipv6@ietf.org; Tue, 05 Jun 2007 23:40:03 -0400
Received: from mrout1-b.corp.dcn.yahoo.com ([216.109.112.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvmNO-0001G0-0k
	for ipv6@ietf.org; Tue, 05 Jun 2007 23:40:03 -0400
Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com
	[216.145.48.98])
	by mrout1-b.corp.dcn.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id
	l563dsQv049531; Tue, 5 Jun 2007 20:39:55 -0700 (PDT)
Date: Wed, 06 Jun 2007 12:39:29 +0900
Message-ID: <m2myzd92fi.wl%gnn@neville-neil.com>
From: gnn@neville-neil.com
To: Joe Abley <jabley@ca.afilias.info>
In-Reply-To: <DCC7A5C7-1A89-4101-B43A-2C7D26E3898E@ca.afilias.info>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<m18xb7llay.wl%jinmei@isl.rdc.toshiba.co.jp>
	<Pine.LNX.4.64.0705292131400.9157@netcore.fi>
	<m11wgykxdz.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m2hcpmah3e.wl%gnn@neville-neil.com>
	<DCC7A5C7-1A89-4101-B43A-2C7D26E3898E@ca.afilias.info>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95
	(i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.2 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Pekka Savola <pekkas@netcore.fi>,
	JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Tue, 5 Jun 2007 11:18:28 -0400,
Joe Abley wrote:
> 
> 
> On 5-Jun-2007, at 05:25, George V. Neville-Neil wrote:
> 
> > Where are we on this draft at the moment?
> 
> I was taken out of commission last week by an IAB retreat, and am  
> currently trying to catch up on all the things I am behind on.  
> Apologies for the delay. I aim to have a revised candidate on the  
> list in the next day or two.

Great, sorry to nag.

Best,
George

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 06 12:42:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvya4-0005SC-8Y; Wed, 06 Jun 2007 12:41:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvya2-0005Qc-CD
	for ipv6@ietf.org; Wed, 06 Jun 2007 12:41:54 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HvyYS-0001XH-1w
	for ipv6@ietf.org; Wed, 06 Jun 2007 12:40:17 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l56GdvY8001063 for <ipv6@ietf.org>; Wed, 6 Jun 2007 19:40:14 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Jun 2007 19:39:56 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 19:39:56 +0300
Received: from [172.19.74.164] (dadhcp-172019074164.americas.nokia.com
	[172.19.74.164])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l56GdskF029833 for <ipv6@ietf.org>; Wed, 6 Jun 2007 19:39:54 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Wed, 6 Jun 2007 09:39:54 -0700
To: IPv6 WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 06 Jun 2007 16:39:56.0069 (UTC)
	FILETIME=[50929D50:01C7A859]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: IPv6 WG Last Call: <draft-ietf-ipv6-ra-flags-option-00.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This starts a two week IPv6 working group last call on advancing

	Title		: IPv6 Router Advertisement Flags Option
	Author(s)	: B. Haberman, R. Hinden
	Filename	: draft-ietf-ipv6-ra-flags-option-00.txt
	Pages		: 7
	Date		: 2007-6-5

to Proposed Standard.  Please send substantive comments to the IPv6  
mailing list. Editorial comments can be sent to the authors.

Note:  I will be acting as the shepherding chair and Brian Haberman  
will be the responsible author for this document.

This last call will end on 20 June 2007.

Regards,
Bob Hinden
IPv6 WG co-chair




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 06 12:49:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hvyhg-0007qS-Ai; Wed, 06 Jun 2007 12:49:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hvyhe-0007no-A1
	for ipv6@ietf.org; Wed, 06 Jun 2007 12:49:46 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hvyhb-0005wK-RS
	for ipv6@ietf.org; Wed, 06 Jun 2007 12:49:46 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l56GodN0008475;
	Wed, 6 Jun 2007 11:50:39 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Jun 2007 11:49:42 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Jun 2007 11:49:42 -0500
Message-ID: <4666E602.4060808@ericsson.com>
Date: Wed, 06 Jun 2007 12:51:14 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
In-Reply-To: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jun 2007 16:49:42.0935 (UTC)
	FILETIME=[AE5F4270:01C7A85A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-ra-flags-option-00.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian and Bob,
   I went through the latest version of this document. It is concise and 
well written. I would just like a new verification step to be added to 
the receiving algorithm in Section 4.

This is the current text

"   Upon reception, a receiver processing NDP messages containing this
    option:

    o  MUST ignore the option if it occurs in a message other than a
       Router Advertisement

    o  MUST ignore all instances of the option except the first one
       encountered in the Router Advertisement message"

I would like a new step

    o  MUST ignore the option if it is not the first option in the
       Router Advertisement message

to be inserted between the two current steps.

Cheers
Suresh

Bob Hinden wrote:
> This starts a two week IPv6 working group last call on advancing
> 
>     Title        : IPv6 Router Advertisement Flags Option
>     Author(s)    : B. Haberman, R. Hinden
>     Filename    : draft-ietf-ipv6-ra-flags-option-00.txt
>     Pages        : 7
>     Date        : 2007-6-5
> 
> to Proposed Standard.  Please send substantive comments to the IPv6 
> mailing list. Editorial comments can be sent to the authors.
> 
> Note:  I will be acting as the shepherding chair and Brian Haberman will 
> be the responsible author for this document.
> 
> This last call will end on 20 June 2007.
> 
> Regards,
> Bob Hinden
> IPv6 WG co-chair
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 06 19:31:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw4yI-0002S6-IN; Wed, 06 Jun 2007 19:31:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw4yH-0002S0-Ae
	for ipv6@ietf.org; Wed, 06 Jun 2007 19:31:21 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hw4yE-0007xi-Vk
	for ipv6@ietf.org; Wed, 06 Jun 2007 19:31:21 -0400
Received: from eagle (127.0.0.1:1892)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S33805A> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 6 Jun 2007 16:31:16 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
In-Reply-To: <D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
Date: Wed, 6 Jun 2007 16:31:15 -0700
Message-ID: <094201c7a892$c6f0cd30$54d26790$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aceha8dDFBFnfmAPQFSrqdOhVjEvFAHIhl9Q
Content-Language: en-us
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 17cf8eab1d6bbd2874a56f9e3554d91d
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

All RH0 hysteria needs to stop now. This entire thread and effort is a BS
smokescreen. There is nothing new here. The effort to kill off RH0 is all
about enforcing a specific business model to sustain the zombie's of the
telco world after they bought up all the independent isp's and still can't
make the intelligent-network king. 

There is no 'amplification', so the abstract is just wrong. The best this
can do is route a single stream around policy; and for some the ability to
route around the brokenness of an ISP in anti-competitive mode is a value,
not a drawback. The crap in the document about an anycast destination being
an amplification shows how little understanding there is about the concept.
Anycast == 'unicast to the nearest instance'. There is no amplification, so
again I say the hysteria needs to stop.

There is no reason to preclude nodes from processing RH0 packets. If you
have to say something say that 'hosts must not forward' else they become
routers. It is perfectly fine for a host to process an RH0 packet as long as
the result is another address on the same host. There is no reason for a
host to forward an RH0 packet. If a router processes an RH0 packet, policy
must have allowed it to do so as the network manager is presumably in
control of his routers.

The business model where RH0 has value is for metro/geo aggregation where
the source needs to select the subscriber's transit provider across the
metro/geo fabric. This is a business model the telco minded world wants to
preclude because it recognizes that the customer has control, not the
provider in a monopolistic strangle-hold.

/rant
I am getting really tired of the recent efforts by the telco world trying to
kill off value to the end user, just because they get no direct benefit or
perceive a direct threat to their dying model.
rant/

Tony 


> -----Original Message-----
> From: Joe Abley [mailto:jabley@ca.afilias.info]
> Sent: Monday, May 28, 2007 2:04 PM
> To: IETF IPv6 Mailing List
> Subject: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
> 
> 
> On 24-May-2007, at 17:07, Joe Abley wrote:
> 
> > I've identified the following areas in which 00 might be modified,
> > based on traffic in this list and a small handful of private mail.
> > Please comment on the following, and point out any other outstanding
> > issues that I missed.
> 
> I have made some edits. Note that I am hoping to reach consensus on the
> changes to -00 which will produce -01 so that once -01 is submitted, it
> is ready for working group last call.
> 
> Attached is a proposed -01, and a unified diff from -00 follows.
> Please comment on the changes, and suggest others which are needed.
> 
> 
> Joe
> 
> --- draft-ietf-ipv6-deprecate-rh0-00.unpg       2007-05-28
> 16:56:44.000000000 -0400
> +++ draft-ietf-ipv6-deprecate-rh0-01.unpg       2007-05-28
> 16:56:59.000000000 -0400
> @@ -3,15 +3,15 @@
> Network Working Group                                           J.
> Abley
> Internet-Draft
> Afilias
> -Updates: 2460 (if approved)                                    P.
> Savola
> -Intended status: Standards Track                               CSC/
> FUNET
> -Expires: November 29, 2007                               G. Neville-
> Neil
> -                                                 Neville-Neil
> Consulting
> +Updates: 2460, 4294                                            P.
> Savola
> +(if approved)                                                  CSC/
> FUNET
> +Intended status: Standards Track                         G. Neville-
> Neil
> +Expires: November 29, 2007                       Neville-Neil
> Consulting
>                                                               May 28,
> 2007
>                Deprecation of Type 0 Routing Headers in IPv6
> -                    draft-ietf-ipv6-deprecate-rh0-00
> +             draft-ietf-ipv6-deprecate-rh0-01-candidate-00
> Status of this Memo
> @@ -45,13 +45,12 @@
> Abstract
>      The functionality provided by IPv6's Type 0 Routing Header can be
> -   exploited in order to perform remote network discovery, to bypass
> -   firewalls and to achieve packet amplification for the purposes of
> -   generating denial-of-service traffic.  This document updates the
> IPv6
> -   specification to deprecate the use of IPv6 Type 0 Routing
> Headers, in
> -   the light of these security concerns.
> +   exploited in order to achieve packet amplification for the purposes
> +   of generating denial-of-service traffic.  This document updates the
> +   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
> +   Headers, in the light of the severity of this security concern.
> -   This document updates RFC 2460.
> +   This document updates RFC 2460 and RFC 4294.
> Table of Contents
> @@ -65,6 +64,12 @@
>        4.1.  Ingress Filtering
>        4.2.  Packet Filtering
>      5.  Security Considerations
> +     5.1.  Network Discovery
> +       5.1.1.  Testing Ingress Filtering
> +       5.1.2.  Finding Attractors
> +     5.2.  Bypassing Filtering Devices
> +     5.3.  Denial of Service
> +     5.4.  Defeating Anycast
>      6.  IANA Considerations
>      7.  Acknowlegements
>      8.  References
> @@ -83,11 +88,13 @@
>      also defined.  Type 0 Routing Headers are referred to as "RH0" in
>      this document.
> -   Use of RH0 has been shown to have unpleasant security implications,
> -   some of which are summarised in Section 5.  This document
> deprecates
> -   the use of RH0.
> +   The functionality provided by IPv6's Type 0 Routing Header can be
> +   exploited in order to achieve packet amplification for the purposes
> +   of generating denial-of-service traffic.  This document updates the
> +   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
> +   Headers, in the light of the severity of this security concern.
> -   This document updates [RFC2460].
> +   This document updates [RFC2460] and [RFC4294].
> 2.  Definitions
> @@ -107,6 +114,9 @@
>      IPv6 nodes MUST NOT originate IPv6 packets containing RH0.
> +   IPv6 implementations are no longer required to implement RH0 in any
> +   way.
> +
> 3.2.  Processing
>      IPv6 nodes MUST NOT process RH0 in packets addressed to them.
> Such @@ -137,17 +147,131 @@
>      Where filtering capabilities do not facilitate matching specific
>      types of Routing Headers, filtering based on the presence of any
> -   Routing Headers on IPv6 routers, regardless of type, is strongly
> -   discouraged.
> +   Routing Headers on IPv6 routers, without explicitly checking the
> +   Routing Header type, is strongly discouraged.
> 5.  Security Considerations
>      The purpose of this document is to deprecate a feature of IPv6
> which
> -   has been shown to have serious security implications.
> +   has been shown to have undesirable security implications.
>      Specific examples of vulnerabilities which are facilitated by the
> -   availability of RH0 can be found in [CanSecWest07].
> +   availability of RH0 can be found in [CanSecWest07], and are also
> +   summarised below.
> +
> +5.1.  Network Discovery
> +
> +5.1.1.  Testing Ingress Filtering
> +
> +   A node N1 can probe a second node N2 in a remote autonomous
> system in
> +   order to discover whether or not that autonomous system implements
> +   ingress filtering ([RFC2827], [RFC3704]), so long as N2 supports
> RH0
> +   processing, and N1 is able to identify one of N2's global-scope,
> +   unicast IPv6 addresses.
> +
> +   N1 selects a global-scope source address A1 which is bound to a
> local
> +   interface, and identifies a global-scope, unicast address A2
> which is
> +   local to node N2.
> +
> +   N1 constructs an IPv6 datagram with IPv6 header source A1 and
> +   destination address A2, and a RH0 containing the single waypoint
> +   address A1.  N1 originates the datagram; if the datagram returns to
> +   N1, then the autonomous system containing N2 does not implement
> +   ingress filtering.
> +
> +5.1.2.  Finding Attractors
> +
> +   Some services are deployed on the Internet using anycast [RFC4786].
> +   Individual anycast nodes normally receive traffic from sources
> within
> +   a bounded topological region (a "catchment area").  Examples of
> +   services deployed using IPv6 anycast include DNS authority
> +   nameservers, 6to4 relay routers [RFC3068] and Teredo relays
> +   [RFC4380].
> +
> +   It is usually difficult to determine the number and topological
> +   locations of all anycast nodes providing a single service using a
> +   single client probe, since only one node is typically visible to a
> +   client at any time.  By including RH0 in packets addressed to an
> +   anycast service address, however, a single client can cause a
> packet
> +   to be sent via hosts or routers located in the catchment area of
> +   remote anycast nodes.
> +
> +   Although the catchment areas of individual anycast nodes vary with
> +   changing network topology and routing policy, opportunities to
> +   discover the existence of other nodes without using RH0 are, in
> +   general, limited.  RH0 provides a mechanism for automatic mapping
> of
> +   anycast nodes and their catchment areas, information which might
> +   subsequently be used to carry out attacks (see Section 5.4).
> +
> +5.2.  Bypassing Filtering Devices
> +
> +   Suppose a packet filter F is configured to protect two hosts S1 and
> +   S2 which have different requirements for protection: S1 is intended
> +   to serve some remote client C, but the filtering policies in F
> +   restrict access to S2.  An example of such a scenario might be the
> +   deployment of a public-facing web server (S1) and some other
> internal
> +   device which provides an administrative interface over HTTP (S2).
> +
> +   If client C originates a datagram to S1 and includes a RH0 which
> +   specifies an address of S2, then the packet might be passed by F
> +   towards S1 and subsequently routed from S1 towards S2 without being
> +   subject to the policies enforced by F. If S2 originates a packet in
> +   reply towards C, it is feasible that the reply will be permitted by
> +   F, and perhaps even that the reply will create state in F
> relating to
> +   the communication between C and S2 which will allow subsequent
> +   packets from C to be sent directly to S2 through F without the
> use of
> +   RH0.
> +
> +5.3.  Denial of Service
> +
> +   A single RH0 may contain multiple waypoint addresses, and the same
> +   address may be included more than once in the same RH0.  This
> allows
> +   a packet to be constructed such that it will oscillate between two
> +   RH0-processing hosts or routers many times.  This allows a stream
> of
> +   packets from an attacker to be amplified along the path between two
> +   remote routers, which could be used to cause congestion along
> +   arbitrary remote paths and hence act as a denial-of-service
> +   mechanism. 88-fold amplification has been demonstrated using this
> +   technique [CanSecWest07].
> +
> +   This technique can also be used as a more general traffic
> amplifier,
> +   accumulating attack traffic in-flight between two well-connected
> but
> +   mutually-distant waypoints and then finally delivering it towards a
> +   third party once the RH0-directed oscillations for each packet are
> +   complete. 7-fold amplification has been postulated using this
> +   "capacitive effect" [CanSecWest07].
> +
> +   Various IPv6 transition mechanisms involve the transmission of IPv6
> +   packets through tunnels built on IPv4 infrastructure (e.g.
> +   [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
> +   writing for the transmission of IPv6 traffic over IPv4 networks.
> The
> +   use of such tunnels can result in IPv6 paths which include a small
> +   number of routers apparently connected by very high latency
> circuits
> +   (tunnels).  Such paths provide opportunities to keep packets in-
> +   flight for longer, with corresponding increases in amplification
> +   potential.
> +
> +5.4.  Defeating Anycast
> +
> +   Packets originated by a single clients towards anycast destination
> +   addresses will normally be routed towards a topologically local
> +   anycast node for service.  This underpins one of the reasons to
> +   deploy services using anycast: to sink traffic from flash crowds
> +   locally, allowing damage from non-distributed sources to be
> localised
> +   to the benefit of clients who are served by different anycast
> nodes.
> +
> +   By including RH0 with a waypoint address within the catchment
> area of
> +   a remote anycast node, a single client can send traffic to multiple
> +   anycast nodes providing the same service, avoiding the isolation of
> +   such traffic to a single node which would otherwise result.
> +
> +   Section 5.1.2 describes the use of RH0 to facilitate the
> discovery of
> +   anycast nodes deployed across the Internet, and to identify sets of
> +   clients whose traffic is naturally attracted to particular anycast
> +   nodes.  Together, these discovery and directed delivery techniques
> +   allow all nodes of an anycast service to be targetted by a single
> +   host.
> 6.  IANA Considerations
> @@ -165,8 +289,10 @@
>      [I-D.savola-ipv6-rh-hosts].  These efforts did not gain sufficient
>      momentum to change the IPv6 specification, but resulted in the
>      modification of the Mobile IPv6 specification to use the type 2
> -   Routing Header instead of RH0 [RFC3775].  Routing Header issues
> were
> -   later documented in [I-D.ietf-v6ops-security-overview].
> +   Routing Header instead of RH0 [RFC3775].  Vishwas Manral identified
> +   various risks associated with RH0 in 2006 including the
> amplification
> +   attack; several of these vulnerabilities (together with other
> issues)
> +   were later documented in [I-D.ietf-v6ops-security-overview].
>      An eloquent and useful description of the operational security
>      implications of RH0 was presented by Philippe Biondi and Arnaud @@
> -191,11 +317,14 @@
>      [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version
> 6
>                 (IPv6) Specification", RFC 2460, December 1998.
> +   [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
> +              April 2006.
> +
> 8.2.  Informative References
>      [CanSecWest07]
>                 BIONDI, P. and A. EBALARD, "IPv6 Routing Header
> Security",
> -              April 2007.
> +              CanSecWest Security Conference 2007, April 2007.
>                 http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf
> @@ -218,12 +347,28 @@
>                 Defeating Denial of Service Attacks which employ IP
> Source
>                 Address Spoofing", BCP 38, RFC 2827, May 2000.
> +   [RFC2893]  Gilligan, R. and E. Nordmark, "Transition Mechanisms for
> +              IPv6 Hosts and Routers", RFC 2893, August 2000.
> +
> +   [RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
> +              via IPv4 Clouds", RFC 3056, February 2001.
> +
> +   [RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
> +              RFC 3068, June 2001.
> +
>      [RFC3704]  Baker, F. and P. Savola, "Ingress Filtering for
> Multihomed
>                 Networks", BCP 84, RFC 3704, March 2004.
>      [RFC3775]  Johnson, D., Perkins, C., and J. Arkko, "Mobility
> Support
>                 in IPv6", RFC 3775, June 2004.
> +   [RFC4380]  Huitema, C., "Teredo: Tunneling IPv6 over UDP through
> +              Network Address Translations (NATs)", RFC 4380,
> +              February 2006.
> +
> +   [RFC4786]  Abley, J. and K. Lindqvist, "Operation of Anycast
> +              Services", BCP 126, RFC 4786, December 2006.
> +
> Appendix A.  Change History
> @@ -239,6 +384,11 @@
>      00 Renamed, draft-ietf-ipv6-deprecate-rh0, a candidate working
> group
>         document.
> +   01-candidate-00  Incorporated text summarising some of the
> unwelcome
> +      uses of RH0; added some clariying text describing deprecation;
> +      modified some ambiguous text in Section 4.2; added "Updates:
> +      4294".
> +
> Authors' Addresses



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 06 22:34:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw7oo-0002Ho-6c; Wed, 06 Jun 2007 22:33:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw7on-0002He-9a
	for ipv6@ietf.org; Wed, 06 Jun 2007 22:33:45 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw7ol-0005eu-UM
	for ipv6@ietf.org; Wed, 06 Jun 2007 22:33:45 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1Hw7rL-000G2d-84; Thu, 07 Jun 2007 02:36:24 +0000
In-Reply-To: <094201c7a892$c6f0cd30$54d26790$@net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 6 Jun 2007 22:33:32 -0400
To: alh-ietf@tndh.net
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Tony,

On 6-Jun-2007, at 19:31, Tony Hain wrote:

> There is no 'amplification', so the abstract is just wrong.

The candidate -01 contains the following text:

    A single RH0 may contain multiple waypoint addresses, and the same
    address may be included more than once in the same RH0.  This allows
    a packet to be constructed such that it will oscillate between two
    RH0-processing hosts or routers many times.  This allows a stream of
    packets from an attacker to be amplified along the path between two
    remote routers, which could be used to cause congestion along
    arbitrary remote paths and hence act as a denial-of-service
    mechanism. 88-fold amplification has been demonstrated using this
    technique [CanSecWest07].

    This technique can also be used as a more general traffic amplifier,
    accumulating attack traffic in-flight between two well-connected but
    mutually-distant waypoints and then finally delivering it towards a
    third party once the RH0-directed oscillations for each packet are
    complete. 7-fold amplification has been postulated using this
    "capacitive effect" [CanSecWest07].

    Various IPv6 transition mechanisms involve the transmission of IPv6
    packets through tunnels built on IPv4 infrastructure (e.g.
    [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
    writing for the transmission of IPv6 traffic over IPv4 networks.   
The
    use of such tunnels can result in IPv6 paths which include a small
    number of routers apparently connected by very high latency circuits
    (tunnels).  Such paths provide opportunities to keep packets in-
    flight for longer, with corresponding increases in amplification
    potential.

That text attempts to summarise three techniques which, facilitated  
by the widespread availability of RH0 processing, facilitates  
amplification which could be used as part of a denial-of-service attack.

If you have objections to the text I quoted above, it would help me  
if you could spell them out. I find it far easier to grasp objections  
if they are grounded in specific text.

> The crap in the document about an anycast destination being
> an amplification shows how little understanding there is about the  
> concept.

If you can find text that equates an anycast destination being "an  
amplification", please point it out so I can remove it.

> Anycast == 'unicast to the nearest instance'.

Indeed. I was one of the authors of BCP 126 and have some familiarity  
with the concept.

> /rant
> I am getting really tired of the recent efforts by the telco world  
> trying to
> kill off value to the end user, just because they get no direct  
> benefit or
> perceive a direct threat to their dying model.
> rant/

I'm confused by your references to telco bias, and I'd appreciate  
some clarification.

Regards,


Joe

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 02:20:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwBLl-00040q-SW; Thu, 07 Jun 2007 02:20:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwBLj-00040f-MD
	for ipv6@ietf.org; Thu, 07 Jun 2007 02:19:59 -0400
Received: from ns1.its.eads.net ([193.56.40.66] helo=mx1.its.eads.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwBLi-00078G-88
	for ipv6@ietf.org; Thu, 07 Jun 2007 02:19:59 -0400
Received: from fr-gate2.mailhub.intra.corp ([53.154.16.34]) by
	mx1.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); 
	Thu, 7 Jun 2007 08:17:34 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate2.mailhub.intra.corp
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 7 Jun 2007 08:22:53 +0200
Received: from [172.16.23.108] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id H92Z3SA4; Thu, 7 Jun 2007 08:20:24 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-Mailer: Apple Mail (2.752.2)
Content-class: urn:content-classes:message
Date: Thu, 7 Jun 2007 08:19:44 +0200
Message-ID: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
Thread-Index: Aceoy+7YGBrrDXMUQDibp54UwKBdYw==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: <alh-ietf@tndh.net>
X-OriginalArrivalTime: 07 Jun 2007 06:22:53.0507 (UTC)
	FILETIME=[47D1B930:01C7A8CC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Le 7 juin 07 =E0 01:31, Tony Hain a =E9crit :

> There is no 'amplification', so the abstract is just wrong.
No, you are wrong. At least, read that :

http://www1.ietf.org/mail-archive/web/ipv6/current/msg07331.html

> The best this can do is route a single stream around policy;
Again, wrong.

> and for some the ability to route around the brokenness of an ISP
> in anti-competitive mode is a value, not a drawback.
Can you point us to the tool/device you are using to do that.

> The crap in the document about an anycast destination being
> an amplification shows how little understanding
And your sentence little reading of the document.

> Anycast =3D=3D 'unicast to the nearest instance'
RH0 mechanism allows people to bypass that.

>  again I say the hysteria needs to stop.
True

> There is no reason to preclude nodes from processing RH0 packets. =20
> If you
> have to say something say that 'hosts must not forward' else they =20
> become
> routers. [...]
Already said. *BSD did it wrong, but that's just a tiny part of the =20
whole story.

Cheers,

a+

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 12:46:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwL77-0004EG-CD; Thu, 07 Jun 2007 12:45:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwL6z-0004Bp-U9
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:45:25 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwL2a-0005cT-Ed
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:40:53 -0400
Received: from eagle (127.0.0.1:3995)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S339753> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 09:40:49 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Joe Abley'" <jabley@ca.afilias.info>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
In-Reply-To: <BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
Date: Thu, 7 Jun 2007 09:40:46 -0700
Message-ID: <09c901c7a922$9bb54980$d31fdc80$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AceorFNggyPvy1/dRYaCREDgpsSvSwAVgVNQ
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Joe Abley wrote:
> Hi Tony,
> 
> On 6-Jun-2007, at 19:31, Tony Hain wrote:
> 
> > There is no 'amplification', so the abstract is just wrong.
> 
> The candidate -01 contains the following text:
> 
>     A single RH0 may contain multiple waypoint addresses, and the same
>     address may be included more than once in the same RH0.  This
> allows
>     a packet to be constructed such that it will oscillate between two
>     RH0-processing hosts or routers many times.  This allows a stream
> of
>     packets from an attacker to be amplified along the path between two
>     remote routers, which could be used to cause congestion along
>     arbitrary remote paths and hence act as a denial-of-service
>     mechanism. 88-fold amplification has been demonstrated using this
>     technique [CanSecWest07].

The stream is not amplified, it is still a single stream, and it is only one
packet at a time that has to wait for reception before being reflected back.
The total traffic volume over a given path may be higher, but this is not a
multiplication of the number of streams. 

> 
>     This technique can also be used as a more general traffic
> amplifier,
>     accumulating attack traffic in-flight between two well-connected
> but
>     mutually-distant waypoints and then finally delivering it towards a
>     third party once the RH0-directed oscillations for each packet are
>     complete. 7-fold amplification has been postulated using this
>     "capacitive effect" [CanSecWest07].

The discussion about 3rd party implies this is related to spoofing. In any
case there are 4 parties in this scenario; src/RH0-1/RH0-2/dst, unless it is
being reflected back to the source. The traffic is not accumulated, it is
reflected back over the same paths multiple times. The postulation is
irrelevant and without looking it up (just going on 'capacitive'), likely
related to latency creating the ability to 'store a large volume oFrom ipv6-bounces@ietf.org Thu Jun 07 12:46:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwL77-0004EG-CD; Thu, 07 Jun 2007 12:45:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwL6z-0004Bp-U9
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:45:25 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwL2a-0005cT-Ed
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:40:53 -0400
Received: from eagle (127.0.0.1:3995)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S339753> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 09:40:49 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Joe Abley'" <jabley@ca.afilias.info>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
In-Reply-To: <BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
Date: Thu, 7 Jun 2007 09:40:46 -0700
Message-ID: <09c901c7a922$9bb54980$d31fdc80$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AceorFNggyPvy1/dRYaCREDgpsSvSwAVgVNQ
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Joe Abley wrote:
> Hi Tony,
> 
> On 6-Jun-2007, at 19:31, Tony Hain wrote:
> 
> > There is no 'amplification', so the abstract is just wrong.
> 
> The candidate -01 contains the following text:
> 
>     A single RH0 may contain multiple waypoint addresses, and the same
>     address may be included more than once in the same RH0.  This
> allows
>     a packet to be constructed such that it will oscillate between two
>     RH0-processing hosts or routers many times.  This allows a stream
> of
>     packets from an attacker to be amplified along the path between two
>     remote routers, which could be used to cause congestion along
>     arbitrary remote paths and hence act as a denial-of-service
>     mechanism. 88-fold amplification has been demonstrated using this
>     technique [CanSecWest07].

The stream is not amplified, it is still a single stream, and it is only one
packet at a time that has to wait for reception before being reflected back.
The total traffic volume over a given path may be higher, but this is not a
multiplication of the number of streams. 

> 
>     This technique can also be used as a more general traffic
> amplifier,
>     accumulating attack traffic in-flight between two well-connected
> but
>     mutually-distant waypoints and then finally delivering it towards a
>     third party once the RH0-directed oscillations for each packet are
>     complete. 7-fold amplification has been postulated using this
>     "capacitive effect" [CanSecWest07].

The discussion about 3rd party implies this is related to spoofing. In any
case there are 4 parties in this scenario; src/RH0-1/RH0-2/dst, unless it is
being reflected back to the source. The traffic is not accumulated, it is
reflected back over the same paths multiple times. The postulation is
irrelevant and without looking it up (just going on 'capacitive'), likely
related to latency creating the ability to 'store a large volume of data'.
That is just wrong, because the packet is not replicated or stored beyond a
single instance in flight. There is at most one instance in flight, in only
one direction at a time. The longer the latency, the lower the total number
of bit times in any given period that a single RH0 reflection can impact.
The total number of bit times for the stream will be the same independent of
latency, but they will be spread out over time as the delay goes up.

> 
>     Various IPv6 transition mechanisms involve the transmission of IPv6
>     packets through tunnels built on IPv4 infrastructure (e.g.
>     [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
>     writing for the transmission of IPv6 traffic over IPv4 networks.
> The
>     use of such tunnels can result in IPv6 paths which include a small
>     number of routers apparently connected by very high latency
> circuits
>     (tunnels).  Such paths provide opportunities to keep packets in-
>     flight for longer, with corresponding increases in amplification
>     potential.

This is absolute BS. The type of path has absolutely nothing to do with the
'opportunity' to exercise the exploit, and the fact that the packet is in
flight longer actually lowers the volume of traffic over a unit of time. In
any case the total number of bits is the same no matter what the latency is,
so tunneling has absolutely no ability to 'increase' the amplification
potential. 

> 
> That text attempts to summarise three techniques which, facilitated
> by the widespread availability of RH0 processing, facilitates
> amplification which could be used as part of a denial-of-service
> attack.
> 
> If you have objections to the text I quoted above, it would help me
> if you could spell them out. I find it far easier to grasp objections
> if they are grounded in specific text.
> 
> > The crap in the document about an anycast destination being
> > an amplification shows how little understanding there is about the
> > concept.
> 
> If you can find text that equates an anycast destination being "an
> amplification", please point it out so I can remove it.

5.4
   By including RH0 with a waypoint address within the catchment area of
   a remote anycast node, a single client can send traffic to multiple
   anycast nodes providing the same service, avoiding the isolation of
   such traffic to a single node which would otherwise result.

The traffic will always go to one-and-only-one anycast node. It may not be
the same one that would have been selected without RH0, but it will not go
to multiple nodes. Also this is about routing around policy, which has the
conveniently overlooked benefit that if the local anycast instance fails but
the route still exists, the service is still available to those that use RH0
to find another. RH0 is a tool, it is not bad or evil, it is a tool that
allows stating a specific waypoint. Any tool can be exploited for unintended
uses, but that is not a reason to ban the tool.

> 
> > Anycast == 'unicast to the nearest instance'.
> 
> Indeed. I was one of the authors of BCP 126 and have some familiarity
> with the concept.

Unfortunately the text in 5.4 does not reflect that. 

> 
> > /rant
> > I am getting really tired of the recent efforts by the telco world
> > trying to
> > kill off value to the end user, just because they get no direct
> > benefit or
> > perceive a direct threat to their dying model.
> > rant/
> 
> I'm confused by your references to telco bias, and I'd appreciate
> some clarification.

That was a rant, related to multiple days of off list FUD from obstinate ISP
types that want to remove any capability for IPv6 to allow the end users to
exercise any control. Since this document is about killing off a technology
that is required for a metro/geo business model, and it started life as
*-evil-*, it automatically gets bucketed in with the ISP myopia about end
users having any form of control. I have no problem limiting the number of
RH0 segments, but killing it off is a knee-jerk reaction to a well known
exploit. TCP-SYN can be exploited, but I donf data'.
That is just wrong, because the packet is not replicated or stored beyond a
single instance in flight. There is at most one instance in flight, in only
one direction at a time. The longer the latency, the lower the total number
of bit times in any given period that a single RH0 reflection can impact.
The total number of bit times for the stream will be the same independent of
latency, but they will be spread out over time as the delay goes up.

> 
>     Various IPv6 transition mechanisms involve the transmission of IPv6
>     packets through tunnels built on IPv4 infrastructure (e.g.
>     [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
>     writing for the transmission of IPv6 traffic over IPv4 networks.
> The
>     use of such tunnels can result in IPv6 paths which include a small
>     number of routers apparently connected by very high latency
> circuits
>     (tunnels).  Such paths provide opportunities to keep packets in-
>     flight for longer, with corresponding increases in amplification
>     potential.

This is absolute BS. The type of path has absolutely nothing to do with the
'opportunity' to exercise the exploit, and the fact that the packet is in
flight longer actually lowers the volume of traffic over a unit of time. In
any case the total number of bits is the same no matter what the latency is,
so tunneling has absolutely no ability to 'increase' the amplification
potential. 

> 
> That text attempts to summarise three techniques which, facilitated
> by the widespread availability of RH0 processing, facilitates
> amplification which could be used as part of a denial-of-service
> attack.
> 
> If you have objections to the text I quoted above, it would help me
> if you could spell them out. I find it far easier to grasp objections
> if they are grounded in specific text.
> 
> > The crap in the document about an anycast destination being
> > an amplification shows how little understanding there is about the
> > concept.
> 
> If you can find text that equates an anycast destination being "an
> amplification", please point it out so I can remove it.

5.4
   By including RH0 with a waypoint address within the catchment area of
   a remote anycast node, a single client can send traffic to multiple
   anycast nodes providing the same service, avoiding the isolation of
   such traffic to a single node which would otherwise result.

The traffic will always go to one-and-only-one anycast node. It may not be
the same one that would have been selected without RH0, but it will not go
to multiple nodes. Also this is about routing around policy, which has the
conveniently overlooked benefit that if the local anycast instance fails but
the route still exists, the service is still available to those that use RH0
to find another. RH0 is a tool, it is not bad or evil, it is a tool that
allows stating a specific waypoint. Any tool can be exploited for unintended
uses, but that is not a reason to ban the tool.

> 
> > Anycast == 'unicast to the nearest instance'.
> 
> Indeed. I was one of the authors of BCP 126 and have some familiarity
> with the concept.

Unfortunately the text in 5.4 does not reflect that. 

> 
> > /rant
> > I am getting really tired of the recent efforts by the telco world
> > trying to
> > kill off value to the end user, just because they get no direct
> > benefit or
> > perceive a direct threat to their dying model.
> > rant/
> 
> I'm confused by your references to telco bias, and I'd appreciate
> some clarification.

That was a rant, related to multiple days of off list FUD from obstinate ISP
types that want to remove any capability for IPv6 to allow the end users to
exercise any control. Since this document is about killing off a technology
that is required for a metro/geo business model, and it started life as
*-evil-*, it automatically gets bucketed in with the ISP myopia about end
users having any form of control. I have no problem limiting the number of
RH0 segments, but killing it off is a knee-jerk reaction to a well known
exploit. TCP-SYN can be exploited, but I don't see calls to deprecate TCP
... 


Section 7
This presentation resulted in widespread publicity for the risks associated
with RH0.

s/publicity/hysteria


Tony



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org Thu Jun 07 12:46:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwL78-0004EW-LB; Thu, 07 Jun 2007 12:45:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwL6z-0004Bq-U8
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:45:25 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwL2a-0005cS-8U
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:40:53 -0400
Received: from eagle (127.0.0.1:3995)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S339751> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 09:40:47 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Ebalard, Arnaud'" <Arnaud.Ebalard@eads.net>
References: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
In-Reply-To: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
Date: Thu, 7 Jun 2007 09:40:45 -0700
Message-ID: <09c801c7a922$9a5e9320$cf1bb960$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aceoy+7YGBrrDXMUQDibp54UwKBdYwAOhd6A
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ebalard, Arnaud wrote:
> Hi,
>=20
> Le 7 juin 07 =E0 01:31, Tony Hain a =E9crit :
>=20
> > There is no 'amplification', so the abstract is just wrong.
> No, you are wrong. At least, read that :
>=20
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07331.html
>=20

I read it around the time it was sent, and it says that you were able to
reflect the same packet back multiple times. That does not amplify it to
multiple destinations as the current document claims, or amplify the =
amount
of bits in flight at any given time.=20

> > The best this can do is route a single stream around policy;
> Again, wrong.

It is still a single stream, and your assumption about policy is that a
packet should traverse a single link at most once. As I said, it routes =
a
single stream around policy.=20

>=20
> > and for some the ability to route around the brokenness of an ISP
> > in anti-competitive mode is a value, not a drawback.
> Can you point us to the tool/device you are using to do that.
>=20
> > The crap in the document about an anycast destination being
> > an amplification shows how little understanding
> And your sentence little reading of the document.

I will admit I only read it through once, and given the overall =
agitation
over the hysteria related to this topic I likely missed subtle points. =
That
said, this entire effort is about preventing opportunities, there is =
nothing
that is new and the same mitigation that is done for IPv4 routing =
headers
works here.

>=20
> > Anycast =3D=3D 'unicast to the nearest instance'
> RH0 mechanism allows people to bypass that.

It still only goes to the 'nearest instance', just the 't see calls to deprecate TCP
... 


Section 7
This presentation resulted in widespread publicity for the risks associated
with RH0.

s/publicity/hysteria


Tony



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org Thu Jun 07 12:46:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwL78-0004EW-LB; Thu, 07 Jun 2007 12:45:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwL6z-0004Bq-U8
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:45:25 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwL2a-0005cS-8U
	for ipv6@ietf.org; Thu, 07 Jun 2007 12:40:53 -0400
Received: from eagle (127.0.0.1:3995)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S339751> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 09:40:47 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Ebalard, Arnaud'" <Arnaud.Ebalard@eads.net>
References: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
In-Reply-To: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
Date: Thu, 7 Jun 2007 09:40:45 -0700
Message-ID: <09c801c7a922$9a5e9320$cf1bb960$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aceoy+7YGBrrDXMUQDibp54UwKBdYwAOhd6A
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ebalard, Arnaud wrote:
> Hi,
>=20
> Le 7 juin 07 =E0 01:31, Tony Hain a =E9crit :
>=20
> > There is no 'amplification', so the abstract is just wrong.
> No, you are wrong. At least, read that :
>=20
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07331.html
>=20

I read it around the time it was sent, and it says that you were able to
reflect the same packet back multiple times. That does not amplify it to
multiple destinations as the current document claims, or amplify the =
amount
of bits in flight at any given time.=20

> > The best this can do is route a single stream around policy;
> Again, wrong.

It is still a single stream, and your assumption about policy is that a
packet should traverse a single link at most once. As I said, it routes =
a
single stream around policy.=20

>=20
> > and for some the ability to route around the brokenness of an ISP
> > in anti-competitive mode is a value, not a drawback.
> Can you point us to the tool/device you are using to do that.
>=20
> > The crap in the document about an anycast destination being
> > an amplification shows how little understanding
> And your sentence little reading of the document.

I will admit I only read it through once, and given the overall =
agitation
over the hysteria related to this topic I likely missed subtle points. =
That
said, this entire effort is about preventing opportunities, there is =
nothing
that is new and the same mitigation that is done for IPv4 routing =
headers
works here.

>=20
> > Anycast =3D=3D 'unicast to the nearest instance'
> RH0 mechanism allows people to bypass that.

It still only goes to the 'nearest instance', just the one closest to =
the
RH0 target rather than the source. That is not an amplification, it is
bypassing local policy.

>=20
> >  again I say the hysteria needs to stop.
> True
>=20
> > There is no reason to preclude nodes from processing RH0 packets.
> > If you
> > have to say something say that 'hosts must not forward' else they
> > become
> > routers. [...]
> Already said. *BSD did it wrong, but that's just a tiny part of the
> whole story.

So we are in the mode of changing specs when an implementation got it
wrong??? If MSFT had been the one, wouldn't the response be screaming =
about
how clueless they are about following specs?

A device that forwards L3 packets not addressed to itself is a router. =
If a
device is not expected to forward packets, it must drop RH0 packets =
where
the next hop is other than self.=20

Since RH0 processing in the host is about dealing with ingress filtering =
to
reach an alternate address, and we now have mobility to do that, I have =
no
problem with removing the ability for a host to process a received RH0
packet. I do have a problem with trying to kill it outright because that
precludes a metro/geo aggregation environment where the source needs to
select transit across the local exchange fabric.

Tony




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------





one closest to =
the
RH0 target rather than the source. That is not an amplification, it is
bypassing local policy.

>=20
> >  again I say the hysteria needs to stop.
> True
>=20
> > There is no reason to preclude nodes from processing RH0 packets.
> > If you
> > have to say something say that 'hosts must not forward' else they
> > become
> > routers. [...]
> Already said. *BSD did it wrong, but that's just a tiny part of the
> whole story.

So we are in the mode of changing specs when an implementation got it
wrong??? If MSFT had been the one, wouldn't the response be screaming =
about
how clueless they are about following specs?

A device that forwards L3 packets not addressed to itself is a router. =
If a
device is not expected to forward packets, it must drop RH0 packets =
where
the next hop is other than self.=20

Since RH0 processing in the host is about dealing with ingress filtering =
to
reach an alternate address, and we now have mobility to do that, I have =
no
problem with removing the ability for a host to process a received RH0
packet. I do have a problem with trying to kill it outright because that
precludes a metro/geo aggregation environment where the source needs to
select transit across the local exchange fabric.

Tony




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------





From ipv6-bounces@ietf.org Thu Jun 07 13:17:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwLbb-0001s6-4r; Thu, 07 Jun 2007 13:17:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwLba-0001rz-1E
	for ipv6@ietf.org; Thu, 07 Jun 2007 13:17:02 -0400
Received: from smistad.uninett.no ([158.38.62.77])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwLbY-0003Ct-OM
	for ipv6@ietf.org; Thu, 07 Jun 2007 13:17:02 -0400
Received: from localhost (smistad.uninett.no [158.38.62.77])
	by smistad.uninett.no (Postfix) with ESMTP id 9B25B21DC36;
	Thu,  7 Jun 2007 19:16:59 +0200 (CEST)
Date: Thu, 07 Jun 2007 19:16:59 +0200 (CEST)
Message-Id: <20070607.191659.14348043.he@uninett.no>
To: alh-ietf@tndh.net
From: Havard Eidnes <he@uninett.no>
In-Reply-To: <094201c7a892$c6f0cd30$54d26790$@net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
X-Mailer: Mew version 4.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

<counter-rant>

All this monomanic ISP-bashing needs to stop now, if IPv6 is ever
to take off in any manner.

The claim that RH0 is "just a tool" and that there is no "amplification=
"
is narrow-sighted at best, since I understood from what has been
discussed here that it can indeed cause excessive bandwith utilization
along a path, and is therefore a much too useful tool in a miscreant's
hand to let loose on the unsuspecting masses.

Also, please do note, one man's tool to "select which ISP to use" can
easily be viewed by the ISPs as a tool for theft of service, inducing
routers to carry packets between customers A and B where neither
customer has any direct or indirect customer/provider relationship
with the providers of the path which is being used.  Why would any
reasonable ISP tolerate such (potential) behaviour?

</counter-rant>

Best regards,

- H=E5vard

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 13:26:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwLkQ-0002bb-RQ; Thu, 07 Jun 2007 13:26:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwLkP-0002bT-FP
	for ipv6@ietf.org; Thu, 07 Jun 2007 13:26:09 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwLkO-0004bF-0W
	for ipv6@ietf.org; Thu, 07 Jun 2007 13:26:09 -0400
Received: from mymb.local (t050096.ppp.asahi-net.or.jp [203.189.50.96])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 559E37301E;
	Fri,  8 Jun 2007 02:26:06 +0900 (JST)
Date: Fri, 08 Jun 2007 02:26:04 +0900
Message-ID: <m2hcpjznf7.wl%jinmei@wide.ad.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@wide.ad.jp>
To: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
In-Reply-To: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
References: <E9E92057-B9F3-4F04-9AD7-8FDCF5F8AD03@eads.net>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Thu, 7 Jun 2007 08:19:44 +0200,
"Ebalard, Arnaud" <Arnaud.Ebalard@eads.net> wrote:

> > There is no reason to preclude nodes from processing RH0 packets.  
> > If you
> > have to say something say that 'hosts must not forward' else they  
> > become
> > routers. [...]
> Already said. *BSD did it wrong, but that's just a tiny part of the  
> whole story.

Please precisely define "wrong" here.  And however "wrong" it is (or
even whether or not it's wrong), host vs router is irrelevant to the
main point in this context (I thought you understood this, so I'm
wondering why you bother to refer to the irrelevant point...).  IMO
it's just misleading to mention the behavior of a specific
implementation using the unclear term.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 15:28:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwNeJ-00075l-Fi; Thu, 07 Jun 2007 15:27:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwNdd-0005i3-HE
	for ipv6@ietf.org; Thu, 07 Jun 2007 15:27:17 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwNdc-0008LB-9O
	for ipv6@ietf.org; Thu, 07 Jun 2007 15:27:17 -0400
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.33974769;
	Thu, 07 Jun 2007 15:26:52 -0400
Message-ID: <46685BFC.9090904@innovationslab.net>
Date: Thu, 07 Jun 2007 15:26:52 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Ipv <ipv6@ietf.org>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-Mailman-Approved-At: Thu, 07 Jun 2007 15:27:58 -0400
Subject: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

All,
     There has been recent activity in the Registry Community looking at
policies utilizing the Centrally Assigned ULA specification that has
expired.  Several people with ties to both the IETF and the RIRs have
been working with the authors to revise the specification in order to
meet the needs of the policy proposals in the RIRs.

     Given that the previous work on Centrally Assigned ULAs was adopted
as an IPv6 WG document, the chairs feel that this upcoming revision
should be considered a continuation of that work.

     The chairs highly encourage people interested in this work to
review and comment on the upcoming revision when it is published.

     As a note, Bob will be the responsible editor for this document and
Brian will be the shepherding WG chair.

Regards,
Brian and Bob


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 16:19:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwORZ-0002HF-Ud; Thu, 07 Jun 2007 16:18:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwORY-0002Ga-Er
	for ipv6@ietf.org; Thu, 07 Jun 2007 16:18:52 -0400
Received: from paoakoavas09.cable.comcast.com ([208.17.35.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwOQ5-0005hp-CS
	for ipv6@ietf.org; Thu, 07 Jun 2007 16:17:22 -0400
Received: from ([24.40.15.92])
	by paoakoavas09.cable.comcast.com with ESMTP  id KP-NTF18.43546689;
	Thu, 07 Jun 2007 16:17:05 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PACDCEXCSMTP03.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 16:17:05 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Jun 2007 16:17:04 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD40232683F@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <46685BFC.9090904@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AcepOinAdglBnSXpRHunrRuCdcyCQQABnQnQ
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Brian Haberman" <brian@innovationslab.net>,
	"Ipv" <ipv6@ietf.org>
X-OriginalArrivalTime: 07 Jun 2007 20:17:05.0352 (UTC)
	FILETIME=[D10B2C80:01C7A940]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian,

Give the heat this proposal is generating (at least in the ARIN region)
it does not seem very constructive to tackle this issue
in a sleeping working group that is not meeting face to face.

   - Alain.=20

> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]=20
> Sent: Thursday, June 07, 2007 3:27 PM
> To: Ipv
> Subject: Revising Centrally Assigned ULA draft
>=20
> All,
>      There has been recent activity in the Registry Community=20
> looking at policies utilizing the Centrally Assigned ULA=20
> specification that has expired.  Several people with ties to=20
> both the IETF and the RIRs have been working with the authors=20
> to revise the specification in order to meet the needs of the=20
> policy proposals in the RIRs.
>=20
>      Given that the previous work on Centrally Assigned ULAs=20
> was adopted as an IPv6 WG document, the chairs feel that this=20
> upcoming revision should be considered a continuation of that work.
>=20
>      The chairs highly encourage people interested in this=20
> work to review and comment on the upcoming revision when it=20
> is published.
>=20
>      As a note, Bob will be the responsible editor for this=20
> document and Brian will be the shepherding WG chair.
>=20
> Regards,
> Brian and Bob
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 17:22:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwPQT-0000Uj-AE; Thu, 07 Jun 2007 17:21:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwPQR-0000UZ-Ia
	for ipv6@ietf.org; Thu, 07 Jun 2007 17:21:47 -0400
Received: from wa-out-1112.google.com ([209.85.146.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwPQQ-0001Xx-5z
	for ipv6@ietf.org; Thu, 07 Jun 2007 17:21:47 -0400
Received: by wa-out-1112.google.com with SMTP id j5so912543wah
	for <ipv6@ietf.org>; Thu, 07 Jun 2007 14:21:45 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=hP6IhPXDVtXOznmCUzvGAwEJcvfqnB5kGldcZaZAye/xAifeygAP6vPNz7feBiE1OIy0I+dtcinUa1EQKNZ5rn+H9nSlmBAWU1VDiJxd//qQsSGj3ywFQgmyVvSI2K2OA++C4P2ViZQ+VN8/ZV0tkIcJVDOCos+pCVWwzk8ll6s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=njDO2aXAauTxgNMUMKOPqSJKzwBfvNRLLZ2YzesPCPBuLe3zjoobbXK4+sYSbi4zTSedCvYH9pe2UYTE0FIS1wYTZE1PrP4Oh0fLCaI8C2PTD+kazeWTdneU9//VlBejg9fV1oC+qkO5Fkp9iaYP7CmqR/5DGHXR05PETnJr//k=
Received: by 10.114.180.1 with SMTP id c1mr1879016waf.1181251305007;
	Thu, 07 Jun 2007 14:21:45 -0700 (PDT)
Received: by 10.114.24.20 with HTTP; Thu, 7 Jun 2007 14:21:44 -0700 (PDT)
Message-ID: <77ead0ec0706071421o44efda9al2756fa5324afbe2f@mail.gmail.com>
Date: Thu, 7 Jun 2007 14:21:44 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Pekka Savola" <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706050922041.2967@netcore.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
	<Pine.LNX.4.64.0706040806240.31082@netcore.fi>
	<77ead0ec0706040823n17961373rc183e5afa1ffbfc3@mail.gmail.com>
	<Pine.LNX.4.64.0706050922041.2967@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Pekka/ A+,

> The packets you want to rate limit are the one addressed to the
> router that include a RH0, not the one that are flowing through (dst
> address of IPv6 packet is not one of the router), right ?
Its slightly more complicated. By checking only at the destination
addresses, we reduce attacks, except for the case where someone knows
intricate details of IP routing. By checking in all nodes, we further
reduce the probability of all such attacks. If as Pekka said we do not
want to process the packet on all intermediate nodes, we could as well
only process the packet at the destination.

Pekka I agree with your sentiment regarding the below.

> As an operator, I do not wish to buy routers that are DoS'able or
> whose control processor CPU resources can be wasted on inspecting
> transiting traffic. "Punting packets to the slow path" is one primary
> thing that a high-speed router should not have to do.  I think I'm not
> alone in the operator field with this sentiment.
My aim has been to try and salvage the functionality present in the
RH0 header, without having to still deal with the attacks. The router
is not DoS'able as streams to the CPU can be ratelimited. I had
pointed out checks that can reduce the kind of problems that have been
discussed on the list. If the same checks can be done in the hardware/
embedded processors that would be ok too.

Thanks,
Vishwas

On 6/4/07, Pekka Savola <pekkas@netcore.fi> wrote:
> On Mon, 4 Jun 2007, Vishwas Manral wrote:
> >>  By 'goes through', do you also intermediate routers which are do not
> >>  need to process the routing header in any way (i.e.: are never in
> >>  "Destination Address" field of the routing header)?
> >>
> >>  If yes, this would require punting packets from hardware forwarding to
> >>  the control processor which is IMHO a non-starter.
> >
> > Having a background on ASIC design for packet forwarding, I believe
> > that is exactly what is done for packets that need to be processed in
> > some exceptional behavior. Its a very very normal case. The other case
> > is to process the packets in the embedded processors, using some
> > firmware.
> >
> > Can you explain why the above design is a non-starter?
>
> As an operator, I do not wish to buy routers that are DoS'able or
> whose control processor CPU resources can be wasted on inspecting
> transiting traffic. "Punting packets to the slow path" is one primary
> thing that a high-speed router should not have to do.  I think I'm not
> alone in the operator field with this sentiment.
>
> Oh yeah, hop-by-hop extension header should be retired as well :-)
>
> --
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 21:39:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwTS1-0006en-Nv; Thu, 07 Jun 2007 21:39:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwTPg-0004Zq-8Q
	for ipv6@ietf.org; Thu, 07 Jun 2007 21:37:16 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwTAv-0002kK-IX
	for ipv6@ietf.org; Thu, 07 Jun 2007 21:22:03 -0400
Received: from [192.94.63.85] (dhcp085.yarralumla.aarnet.edu.au [192.94.63.85])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id AC641D5F2D;
	Fri,  8 Jun 2007 11:21:59 +1000 (EST)
Message-ID: <4668AFA5.9070907@apnic.net>
Date: Fri, 08 Jun 2007 11:23:49 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: alh-ietf@tndh.net
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
In-Reply-To: <09c901c7a922$9bb54980$d31fdc80$@net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>>     This technique can also be used as a more general traffic
>> amplifier,
>>     accumulating attack traffic in-flight between two well-connected
>> but
>>     mutually-distant waypoints and then finally delivering it towards a
>>     third party once the RH0-directed oscillations for each packet are
>>     complete. 7-fold amplification has been postulated using this
>>     "capacitive effect" [CanSecWest07].
> 
> The discussion about 3rd party implies this is related to spoofing. In any
> case there are 4 parties in this scenario; src/RH0-1/RH0-2/dst, unless it is
> being reflected back to the source. The traffic is not accumulated, it is
> reflected back over the same paths multiple times. The postulation is
> irrelevant and without looking it up (just going on 'capacitive'), likely
> related to latency creating the ability to 'store a large volume of data'.
> That is just wrong, because the packet is not replicated or stored beyond a
> single instance in flight. There is at most one instance in flight, in only
> one direction at a time. The longer the latency, the lower the total number
> of bit times in any given period that a single RH0 reflection can impact.
> The total number of bit times for the stream will be the same independent of
> latency, but they will be spread out over time as the delay goes up.


you are right that no packet gets duplicated in this scenario and 
ultimately the number of packets in equals the number out. But the 
attack relies of the technique of stuffing packets in over an extended 
interval and then releasing them all towards the destination in a much 
shorter time interval.

My understanding of this form of "capacitance attack" was to send the 
first N packets with X number of address pairs in the routing header, 
the second set of N packets with Y address pairs in the routing header 
(where Y is less than X) and so on. If you get the numbers just right, 
then all the packets get released to the destination address at the same 
time - i.e. discharging all the traffic to the ultimate destination in 
the routing header address pair "capacitor" at the same time.


Yes, getting the timing right for this approach would appear to be a 
very tricky issue to solve!


regards,

   Geoff

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 21:56:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwTiG-0006Qc-J7; Thu, 07 Jun 2007 21:56:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwTiF-0006QQ-6e
	for ipv6@ietf.org; Thu, 07 Jun 2007 21:56:27 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwTiC-0003XE-RK
	for ipv6@ietf.org; Thu, 07 Jun 2007 21:56:27 -0400
Received: from eagle (127.0.0.1:1101)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S33A3A3> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 18:56:20 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Havard Eidnes'" <he@uninett.no>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<20070607.191659.14348043.he@uninett.no>
In-Reply-To: <20070607.191659.14348043.he@uninett.no>
Date: Thu, 7 Jun 2007 18:56:19 -0700
Message-ID: <0b9c01c7a970$364dfb20$a2e9f160$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcepJ6klHiYAjMl6QsefJz5RFPNLaAASBs+A
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Havard Eidnes wrote:
> <counter-rant>
> 
> All this monomanic ISP-bashing needs to stop now, if IPv6 is ever
> to take off in any manner.
> 
> The claim that RH0 is "just a tool" and that there is no
> "amplification"
> is narrow-sighted at best, since I understood from what has been
> discussed here that it can indeed cause excessive bandwith utilization
> along a path, and is therefore a much too useful tool in a miscreant's
> hand to let loose on the unsuspecting masses.

So fix it by restricting the number of waypoints. Killing it only prevents
valid uses.

> 
> Also, please do note, one man's tool to "select which ISP to use" can
> easily be viewed by the ISPs as a tool for theft of service, inducing
> routers to carry packets between customers A and B where neither
> customer has any direct or indirect customer/provider relationship
> with the providers of the path which is being used.  Why would any
> reasonable ISP tolerate such (potential) behaviour?
> 
> </counter-rant>

There is no requirement that an ISP accept a packet with RH0 from a
non-customer, so this claim of theft is just more FUD feeding the hysteria. 

Tony





--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 22:00:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwTln-00023w-B3; Thu, 07 Jun 2007 22:00:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwTll-00023q-IN
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:00:05 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwTll-0006Mp-44
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:00:05 -0400
Received: from eagle (127.0.0.1:1130)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S33A3B6> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 19:00:00 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Geoff Huston'" <gih@apnic.net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net> <4668AFA5.9070907@apnic.net>
In-Reply-To: <4668AFA5.9070907@apnic.net>
Date: Thu, 7 Jun 2007 18:59:59 -0700
Message-ID: <0b9d01c7a970$b9e51d60$2daf5820$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acepa2qyTiFs77CNSne6hzhMz+RaEwAAdIvg
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Geoff Huston wrote:
> >>     This technique can also be used as a more general traffic
> >> amplifier,
> >>     accumulating attack traffic in-flight between two well-connected
> >> but
> >>     mutually-distant waypoints and then finally delivering it
> towards a
> >>     third party once the RH0-directed oscillations for each packet
> are
> >>     complete. 7-fold amplification has been postulated using this
> >>     "capacitive effect" [CanSecWest07].
> >
> > The discussion about 3rd party implies this is related to spoofing.
> In any
> > case there are 4 parties in this scenario; src/RH0-1/RH0-2/dst,
> unless it is
> > being reflected back to the source. The traffic is not accumulated,
> it is
> > reflected back over the same paths multiple times. The postulation is
> > irrelevant and without looking it up (just going on 'capacitive'),
> likely
> > related to latency creating the ability to 'store a large volume of
> data'.
> > That is just wrong, because the packet is not replicated or stored
> beyond a
> > single instance in flight. There is at most one instance in flight,
> in only
> > one direction at a time. The longer the latency, the lower the total
> number
> > of bit times in any given period that a single RH0 reflection can
> impact.
> > The total number of bit times for the stream will be the same
> independent of
> > latency, but they will be spread out over time as the delay goes up.
> 
> 
> you are right that no packet gets duplicated in this scenario and
> ultimately the number of packets in equals the number out. But the
> attack relies of the technique of stuffing packets in over an extended
> interval and then releasing them all towards the destination in a much
> shorter time interval.

This makes no sense. The latency is the same for the entire packet chain, so
the delay between the first and last should be the same at the exit, modulo
normal queuing jitter.

> 
> My understanding of this form of "capacitance attack" was to send the
> first N packets with X number of address pairs in the routing header,
> the second set of N packets with Y address pairs in the routing header
> (where Y is less than X) and so on. If you get the numbers just right,
> then all the packets get released to the destination address at the
> same
> time - i.e. discharging all the traffic to the ultimate destination in
> the routing header address pair "capacitor" at the same time.

Well one might try, but reality is that the last hop will just queue the
pile and they will arrive serially based on link speed if they are not
dropped. Also, unless X & Y are different paths for each time interval, the
preceding set of N will be tying up the link queues to preclude the
subsequent ones from moving.

> 
> 
> Yes, getting the timing right for this approach would appear to be a
> very tricky issue to solve!

I think it is more than timing. It would appear that one needs to choose an
appropriate set of X & Y alternative pairs to keep serialization delays from
getting in the way of the plan. It is much simpler to tell the army of
zombies to ddos a site than it is to figure out the right set of X & Y pairs
along with the right number of bounces for each set of N. The FUD over this
supposed threat is just feeding the hysteria. 


As I said earlier, it is reasonable to limit the number of waypoints in the
RH0 path. I don't know the right number, but to support the simple scenario
of selecting transit across a metro/geo fabric I could be convinced that 1
is right. Others may have different use cases with slightly more. In any
case, a small number of waypoints does not raise the threat of dos due to
bouncing significantly more than the threat of back-to-back packet dos.  

Tony




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 22:04:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwTq4-0006v6-9P; Thu, 07 Jun 2007 22:04:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwTq2-0006ut-DW
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:04:30 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwTq1-0007f9-Ug
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:04:30 -0400
Received: from eagle (127.0.0.1:1167)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S33A3D1> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Thu, 7 Jun 2007 19:04:25 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Durand, Alain'" <Alain_Durand@cable.comcast.com>,
	"'Brian Haberman'" <brian@innovationslab.net>, "'Ipv'" <ipv6@ietf.org>
References: <46685BFC.9090904@innovationslab.net>
	<EF2F0EC839870F43A6637360BC12ABD40232683F@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD40232683F@PACDCEXCMB05.cable.comcast.com>
Date: Thu, 7 Jun 2007 19:04:24 -0700
Message-ID: <0b9e01c7a971$57c7d0e0$075772a0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcepOinAdglBnSXpRHunrRuCdcyCQQABnQnQAAwP1QA=
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

ARIN & NANOG are nothing more than heat lately (all hot air?). As I
suggested at NANOG this week, the right thing to do is for the WG to define
the space, and turn it over to IANA to manage. Beyond that it was all policy
anyway, so the fact that it is defined makes no difference if policy chooses
to ignore it. Not defining it leaves policy with no alternative but to
succumb to those that want nothing more than to exercise power through
control of the address space.

I say wrap it up and ship it. 
Tony

> -----Original Message-----
> From: Durand, Alain [mailto:Alain_Durand@cable.comcast.com]
> Sent: Thursday, June 07, 2007 1:17 PM
> To: Brian Haberman; Ipv
> Subject: RE: Revising Centrally Assigned ULA draft
> 
> Brian,
> 
> Give the heat this proposal is generating (at least in the ARIN region)
> it does not seem very constructive to tackle this issue
> in a sleeping working group that is not meeting face to face.
> 
>    - Alain.
> 
> > -----Original Message-----
> > From: Brian Haberman [mailto:brian@innovationslab.net]
> > Sent: Thursday, June 07, 2007 3:27 PM
> > To: Ipv
> > Subject: Revising Centrally Assigned ULA draft
> >
> > All,
> >      There has been recent activity in the Registry Community
> > looking at policies utilizing the Centrally Assigned ULA
> > specification that has expired.  Several people with ties to
> > both the IETF and the RIRs have been working with the authors
> > to revise the specification in order to meet the needs of the
> > policy proposals in the RIRs.
> >
> >      Given that the previous work on Centrally Assigned ULAs
> > was adopted as an IPv6 WG document, the chairs feel that this
> > upcoming revision should be considered a continuation of that work.
> >
> >      The chairs highly encourage people interested in this
> > work to review and comment on the upcoming revision when it
> > is published.
> >
> >      As a note, Bob will be the responsible editor for this
> > document and Brian will be the shepherding WG chair.
> >
> > Regards,
> > Brian and Bob
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 22:41:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUPP-0003ww-J0; Thu, 07 Jun 2007 22:41:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwUPO-0003wo-PG
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:41:02 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwUPN-0001q6-4w
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:41:02 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HwURu-00050M-JL; Fri, 08 Jun 2007 02:43:40 +0000
In-Reply-To: <09c901c7a922$9bb54980$d31fdc80$@net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Thu, 7 Jun 2007 22:40:51 -0400
To: <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 7-Jun-2007, at 12:40, Tony Hain wrote:

> Joe Abley wrote:
>> Hi Tony,
>>
>> On 6-Jun-2007, at 19:31, Tony Hain wrote:
>>
>>> There is no 'amplification', so the abstract is just wrong.
>>
>> The candidate -01 contains the following text:
>>
>>     A single RH0 may contain multiple waypoint addresses, and the  
>> same
>>     address may be included more than once in the same RH0.  This
>> allows
>>     a packet to be constructed such that it will oscillate between  
>> two
>>     RH0-processing hosts or routers many times.  This allows a stream
>> of
>>     packets from an attacker to be amplified along the path  
>> between two
>>     remote routers, which could be used to cause congestion along
>>     arbitrary remote paths and hence act as a denial-of-service
>>     mechanism. 88-fold amplification has been demonstrated using this
>>     technique [CanSecWest07].
>
> The stream is not amplified, it is still a single stream,

That's a valid editorial point, thanks.

> and it is only one
> packet at a time that has to wait for reception before being  
> reflected back.

No, that's not the case. Packets constructed with an RH0 extension  
header containing intermediate addresses A and B, N times (so, for  
example, if N=5 then RH0 contains ten addresses, A B A B A B A B A B)  
can be injected into the A-B cyclotron as rapidly as the path between  
the origin and A allows, without ever waiting for a response.

So long as the injection rate is higher than 1/(N*T) where T is the  
round-trip delay between A and B, the traffic impact between A and B  
will exceed that between the origin and A, N-fold.

> The total traffic volume over a given path may be higher, but this  
> is not a
> multiplication of the number of streams.

It's a multiplication of the amount of traffic being carried, though.  
The ability to cause 88Mbit/s of traffic in a remote network with  
only 1Mbit/s of effort is surely an amplification effect (and surely  
a concern).

>>     This technique can also be used as a more general traffic
>> amplifier,
>>     accumulating attack traffic in-flight between two well-connected
>> but
>>     mutually-distant waypoints and then finally delivering it  
>> towards a
>>     third party once the RH0-directed oscillations for each packet  
>> are
>>     complete. 7-fold amplification has been postulated using this
>>     "capacitive effect" [CanSecWest07].
>
> The discussion about 3rd party implies this is related to spoofing.

No, not at all. The victim address in this case is a destination  
address, not a source address.

My understanding of the CanSecWest authors' thinking with respect to  
this particular technique is that the number of (A, B) waypoints in  
the RH0 header would be varied such that for every one packet that  
entered the A-B cyclotron, you could achieve N packets leaving  
simultaneously, each having been round the A-B loop a different  
number of times.

Maximising the output of such a capacitor would require tuning the  
RH0 extension header construction according to the observed round- 
trip latency between A and B which seems non-trivial, but at the same  
time not impossible.

Note that I have not explored the details of this with the CanSecWest  
presenters, however; it's possible that they were thinking of  
something different (and equally plausible that there's a fault with  
my logic, above).

>>     Various IPv6 transition mechanisms involve the transmission of  
>> IPv6
>>     packets through tunnels built on IPv4 infrastructure (e.g.
>>     [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
>>     writing for the transmission of IPv6 traffic over IPv4 networks.
>> The
>>     use of such tunnels can result in IPv6 paths which include a  
>> small
>>     number of routers apparently connected by very high latency
>> circuits
>>     (tunnels).  Such paths provide opportunities to keep packets in-
>>     flight for longer, with corresponding increases in amplification
>>     potential.
>
> This is absolute BS. The type of path has absolutely nothing to do  
> with the
> 'opportunity' to exercise the exploit,

Right, but the round-trip path latency does (see above).

>>> The crap in the document about an anycast destination being
>>> an amplification shows how little understanding there is about the
>>> concept.
>>
>> If you can find text that equates an anycast destination being "an
>> amplification", please point it out so I can remove it.
>
> 5.4
>    By including RH0 with a waypoint address within the catchment  
> area of
>    a remote anycast node, a single client can send traffic to multiple
>    anycast nodes providing the same service, avoiding the isolation of
>    such traffic to a single node which would otherwise result.
>
> The traffic will always go to one-and-only-one anycast node.

Not with widespread RH0 support; that's the point this section  
attempts to make. With RH0 support a single origin can send packets  
which will arrive at different anycast nodes, regardless of the  
natural (no-RH0) node that would normally receive the traffic.

>>> Anycast == 'unicast to the nearest instance'.
>>
>> Indeed. I was one of the authors of BCP 126 and have some familiarity
>> with the concept.
>
> Unfortunately the text in 5.4 does not reflect that.

I have not yet understood your point (or you have not understood  
mine). I'm not convinced that we have a problem in 5.4, yet.

> That was a rant, related to multiple days of off list FUD from  
> obstinate ISP
> types that want to remove any capability for IPv6 to allow the end  
> users to
> exercise any control.

I am sympathetic to the problem; if I had a magic wand that would  
allow press coverage of technical issues to be (a) accurate and (b)  
fully understood by all who read it, I would wave it :-)

However, this seems orthogonal to the technical issue.

> Since this document is about killing off a technology
> that is required for a metro/geo business model, and it started  
> life as
> *-evil-*, it automatically gets bucketed in with the ISP myopia  
> about end
> users having any form of control.

There's a long history of "-is-evil-" being used in document names in  
the IETF, and it's common argot amongst operators when describing  
things that have unpleasant side-effects (see, for example, the  
recent, huge NANOG thread on NAT, where NAT was declared as being  
evil about every three messages).

You know this, of course. I feel your frustration, and I appreciate  
that one more reason not deploy IPv6 amongst operators of any share  
is not something that is going to make for a happy fun day for you.  
However, I don't think that blaming my earlier document name for non- 
deployment of IPv6 in this case is reasonable.

> I have no problem limiting the number of
> RH0 segments, but killing it off is a knee-jerk reaction to a well  
> known
> exploit. TCP-SYN can be exploited, but I don't see calls to  
> deprecate TCP
> ...

The well-known exploit in this case was judged by this working group  
to have minimal demonstrated application in the real world, and non- 
trivial risks associated with its availability, hence the decision to  
deprecate.

If you think that judgement of consensus by the wg chairs was wrong,  
then that seems like something best taken up with them; this document  
is a reaction to that consensus, not a proponent of it.

> Section 7
> This presentation resulted in widespread publicity for the risks  
> associated
> with RH0.
>
> s/publicity/hysteria

It seems like it would be unusual to see one without the other.


Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 22:53:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUbK-0007oa-Cy; Thu, 07 Jun 2007 22:53:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwUbJ-0007oR-3p
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:53:21 -0400
Received: from an-out-0708.google.com ([209.85.132.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwUbI-0004Fg-LJ
	for ipv6@ietf.org; Thu, 07 Jun 2007 22:53:21 -0400
Received: by an-out-0708.google.com with SMTP id c17so151856anc
	for <ipv6@ietf.org>; Thu, 07 Jun 2007 19:53:20 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=c5DnaJkFfzr+7/8DRNaF5b0COBR9/Mx+fphzAHnljJevp8wazoZoEJ5FlejHcrCUk4Y5d5qJBnIldxMZ7aCtbqx0m08y79MNgHQOd4W9wAeGFxAL8acUVkQGp4kwoBRLIwBZdpstY5gncJ8OSmsBryRNR7TtQTVpyz92/LfNGB4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=QP3pQ5++KBNYdd2sutNQxyEBzzBBCm3hT9DMcc2uiPSbYNXoQPOaFZYjAtfzShx4N2sumu1EFathR5rDYqcvcPPfWdypT8tbL1ECivJAwtbUK828iWRxrBuebodYyk2MGW0zbR56YUGyRrEsPCQZLz2oUIe17k2EhDzkqrjPG9A=
Received: by 10.115.17.1 with SMTP id u1mr2109487wai.1181271199601;
	Thu, 07 Jun 2007 19:53:19 -0700 (PDT)
Received: by 10.114.24.20 with HTTP; Thu, 7 Jun 2007 19:53:19 -0700 (PDT)
Message-ID: <77ead0ec0706071953p52ce1caerb1f968d956b41655@mail.gmail.com>
Date: Thu, 7 Jun 2007 19:53:19 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Joe Abley" <jabley@ca.afilias.info>
In-Reply-To: <05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
	<05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, alh-ietf@tndh.net
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Joe,

> > The stream is not amplified, it is still a single stream,
>
> That's a valid editorial point, thanks.
The amount of traffic is amplified. I dont see a reason to say that
the amount of traffic is not amplified. The amount of processing is
amplified too.

Thanks,
Vishwas

On 6/7/07, Joe Abley <jabley@ca.afilias.info> wrote:
>
> On 7-Jun-2007, at 12:40, Tony Hain wrote:
>
> > Joe Abley wrote:
> >> Hi Tony,
> >>
> >> On 6-Jun-2007, at 19:31, Tony Hain wrote:
> >>
> >>> There is no 'amplification', so the abstract is just wrong.
> >>
> >> The candidate -01 contains the following text:
> >>
> >>     A single RH0 may contain multiple waypoint addresses, and the
> >> same
> >>     address may be included more than once in the same RH0.  This
> >> allows
> >>     a packet to be constructed such that it will oscillate between
> >> two
> >>     RH0-processing hosts or routers many times.  This allows a stream
> >> of
> >>     packets from an attacker to be amplified along the path
> >> between two
> >>     remote routers, which could be used to cause congestion along
> >>     arbitrary remote paths and hence act as a denial-of-service
> >>     mechanism. 88-fold amplification has been demonstrated using this
> >>     technique [CanSecWest07].
> >
> > The stream is not amplified, it is still a single stream,
>
> That's a valid editorial point, thanks.
>
> > and it is only one
> > packet at a time that has to wait for reception before being
> > reflected back.
>
> No, that's not the case. Packets constructed with an RH0 extension
> header containing intermediate addresses A and B, N times (so, for
> example, if N=5 then RH0 contains ten addresses, A B A B A B A B A B)
> can be injected into the A-B cyclotron as rapidly as the path between
> the origin and A allows, without ever waiting for a response.
>
> So long as the injection rate is higher than 1/(N*T) where T is the
> round-trip delay between A and B, the traffic impact between A and B
> will exceed that between the origin and A, N-fold.
>
> > The total traffic volume over a given path may be higher, but this
> > is not a
> > multiplication of the number of streams.
>
> It's a multiplication of the amount of traffic being carried, though.
> The ability to cause 88Mbit/s of traffic in a remote network with
> only 1Mbit/s of effort is surely an amplification effect (and surely
> a concern).
>
> >>     This technique can also be used as a more general traffic
> >> amplifier,
> >>     accumulating attack traffic in-flight between two well-connected
> >> but
> >>     mutually-distant waypoints and then finally delivering it
> >> towards a
> >>     third party once the RH0-directed oscillations for each packet
> >> are
> >>     complete. 7-fold amplification has been postulated using this
> >>     "capacitive effect" [CanSecWest07].
> >
> > The discussion about 3rd party implies this is related to spoofing.
>
> No, not at all. The victim address in this case is a destination
> address, not a source address.
>
> My understanding of the CanSecWest authors' thinking with respect to
> this particular technique is that the number of (A, B) waypoints in
> the RH0 header would be varied such that for every one packet that
> entered the A-B cyclotron, you could achieve N packets leaving
> simultaneously, each having been round the A-B loop a different
> number of times.
>
> Maximising the output of such a capacitor would require tuning the
> RH0 extension header construction according to the observed round-
> trip latency between A and B which seems non-trivial, but at the same
> time not impossible.
>
> Note that I have not explored the details of this with the CanSecWest
> presenters, however; it's possible that they were thinking of
> something different (and equally plausible that there's a fault with
> my logic, above).
>
> >>     Various IPv6 transition mechanisms involve the transmission of
> >> IPv6
> >>     packets through tunnels built on IPv4 infrastructure (e.g.
> >>     [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time of
> >>     writing for the transmission of IPv6 traffic over IPv4 networks.
> >> The
> >>     use of such tunnels can result in IPv6 paths which include a
> >> small
> >>     number of routers apparently connected by very high latency
> >> circuits
> >>     (tunnels).  Such paths provide opportunities to keep packets in-
> >>     flight for longer, with corresponding increases in amplification
> >>     potential.
> >
> > This is absolute BS. The type of path has absolutely nothing to do
> > with the
> > 'opportunity' to exercise the exploit,
>
> Right, but the round-trip path latency does (see above).
>
> >>> The crap in the document about an anycast destination being
> >>> an amplification shows how little understanding there is about the
> >>> concept.
> >>
> >> If you can find text that equates an anycast destination being "an
> >> amplification", please point it out so I can remove it.
> >
> > 5.4
> >    By including RH0 with a waypoint address within the catchment
> > area of
> >    a remote anycast node, a single client can send traffic to multiple
> >    anycast nodes providing the same service, avoiding the isolation of
> >    such traffic to a single node which would otherwise result.
> >
> > The traffic will always go to one-and-only-one anycast node.
>
> Not with widespread RH0 support; that's the point this section
> attempts to make. With RH0 support a single origin can send packets
> which will arrive at different anycast nodes, regardless of the
> natural (no-RH0) node that would normally receive the traffic.
>
> >>> Anycast == 'unicast to the nearest instance'.
> >>
> >> Indeed. I was one of the authors of BCP 126 and have some familiarity
> >> with the concept.
> >
> > Unfortunately the text in 5.4 does not reflect that.
>
> I have not yet understood your point (or you have not understood
> mine). I'm not convinced that we have a problem in 5.4, yet.
>
> > That was a rant, related to multiple days of off list FUD from
> > obstinate ISP
> > types that want to remove any capability for IPv6 to allow the end
> > users to
> > exercise any control.
>
> I am sympathetic to the problem; if I had a magic wand that would
> allow press coverage of technical issues to be (a) accurate and (b)
> fully understood by all who read it, I would wave it :-)
>
> However, this seems orthogonal to the technical issue.
>
> > Since this document is about killing off a technology
> > that is required for a metro/geo business model, and it started
> > life as
> > *-evil-*, it automatically gets bucketed in with the ISP myopia
> > about end
> > users having any form of control.
>
> There's a long history of "-is-evil-" being used in document names in
> the IETF, and it's common argot amongst operators when describing
> things that have unpleasant side-effects (see, for example, the
> recent, huge NANOG thread on NAT, where NAT was declared as being
> evil about every three messages).
>
> You know this, of course. I feel your frustration, and I appreciate
> that one more reason not deploy IPv6 amongst operators of any share
> is not something that is going to make for a happy fun day for you.
> However, I don't think that blaming my earlier document name for non-
> deployment of IPv6 in this case is reasonable.
>
> > I have no problem limiting the number of
> > RH0 segments, but killing it off is a knee-jerk reaction to a well
> > known
> > exploit. TCP-SYN can be exploited, but I don't see calls to
> > deprecate TCP
> > ...
>
> The well-known exploit in this case was judged by this working group
> to have minimal demonstrated application in the real world, and non-
> trivial risks associated with its availability, hence the decision to
> deprecate.
>
> If you think that judgement of consensus by the wg chairs was wrong,
> then that seems like something best taken up with them; this document
> is a reaction to that consensus, not a proponent of it.
>
> > Section 7
> > This presentation resulted in widespread publicity for the risks
> > associated
> > with RH0.
> >
> > s/publicity/hysteria
>
> It seems like it would be unusual to see one without the other.
>
>
> Joe
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 23:00:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUhx-0003mf-JJ; Thu, 07 Jun 2007 23:00:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwUhs-0003Wl-KN
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:00:08 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwUhq-0006gT-BL
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:00:08 -0400
Received: by ug-out-1314.google.com with SMTP id j30so2202062ugc
	for <ipv6@ietf.org>; Thu, 07 Jun 2007 20:00:05 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=fPTy0NUaU3cnl49KhVuKfLT/qoQPjMSxCoB7jE0FnoNbLipm1df0MKqd61nSOdBnKihYT5H1iAxlzvHZKsrtS3LQNMF9DzlaLfM+psrXWq/jw2C6xV9OAZ3LuwkyKJVKGZh2MDz64PT5O8KOt1ye7p0JGQAnDT59x8/SM9UGg+w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=bLiLJ9AlDPS7hMjHz5uuYLKZW2pnM0ydHdn0tco+2wSLJAma441cARLeLUPb1ktstUUv3G74Rkk0weGS9j/XFi2ymUXsHO667Xl1+VIvBaD/0X7Fe2pjiV+LWlAlm225kKWxRjqQ/R9ovtHhTJXReR/eSXFLoVEuNKDxnhavkD0=
Received: by 10.115.18.1 with SMTP id v1mr2181748wai.1181271604155;
	Thu, 07 Jun 2007 20:00:04 -0700 (PDT)
Received: by 10.114.24.20 with HTTP; Thu, 7 Jun 2007 20:00:04 -0700 (PDT)
Message-ID: <77ead0ec0706072000y55443200ha2ad4161905e85c5@mail.gmail.com>
Date: Thu, 7 Jun 2007 20:00:04 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: alh-ietf@tndh.net
In-Reply-To: <09c901c7a922$9bb54980$d31fdc80$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Tony,

> The stream is not amplified, it is still a single stream, and it is only one
> packet at a time that has to wait for reception before being reflected back.
> The total traffic volume over a given path may be higher, but this is not a
> multiplication of the number of streams.
The packets are not replicated and as you said the amount of traffic
between the link is amplified.  It seems to be clearly stated in the
dictionary.

Amplify =  to make larger or greater (as in amount, importance, or
intensity) . http://www.m-w.com/dictionary/amplify

> So fix it by restricting the number of waypoints. Killing it only prevents
> valid uses.
I have added a draft that puts in checks to reduce such traffic
amplification, for exactly the purpose you state.

Thanks,
Vishwas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 23:09:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwUqp-0003dK-MA; Thu, 07 Jun 2007 23:09:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwUqo-0003Zk-N0
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:09:22 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwUqn-0002Sw-EM
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:09:22 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HwUtK-0005Tu-QM; Fri, 08 Jun 2007 03:12:01 +0000
In-Reply-To: <77ead0ec0706071953p52ce1caerb1f968d956b41655@mail.gmail.com>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
	<05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
	<77ead0ec0706071953p52ce1caerb1f968d956b41655@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BF937B16-7453-41A1-A431-5A5AAD2764AD@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Thu, 7 Jun 2007 23:09:12 -0400
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, alh-ietf@tndh.net
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 7-Jun-2007, at 22:53, Vishwas Manral wrote:

>> > The stream is not amplified, it is still a single stream,
>>
>> That's a valid editorial point, thanks.
> The amount of traffic is amplified.

Yes.

> I dont see a reason to say that
> the amount of traffic is not amplified.

Indeed, that would seem contradictory :-)

> The amount of processing is
> amplified too.

Yes.


Joe

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 23:47:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwVRX-0000yQ-2W; Thu, 07 Jun 2007 23:47:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwVRV-0000yL-G6
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:47:17 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwVRU-0005Op-1x
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:47:17 -0400
Received: from [192.94.63.85] (dhcp085.yarralumla.aarnet.edu.au [192.94.63.85])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 9542AD5F2D;
	Fri,  8 Jun 2007 13:47:14 +1000 (EST)
Message-ID: <4668D1B0.7060104@apnic.net>
Date: Fri, 08 Jun 2007 13:49:04 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: alh-ietf@tndh.net
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>	<09c901c7a922$9bb54980$d31fdc80$@net>
	<4668AFA5.9070907@apnic.net> <0b9d01c7a970$b9e51d60$2daf5820$@net>
In-Reply-To: <0b9d01c7a970$b9e51d60$2daf5820$@net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Tony Hain wrote:
>>
>> you are right that no packet gets duplicated in this scenario and
>> ultimately the number of packets in equals the number out. But the
>> attack relies of the technique of stuffing packets in over an extended
>> interval and then releasing them all towards the destination in a much
>> shorter time interval.
> 
> This makes no sense. The latency is the same for the entire packet chain, so
> the delay between the first and last should be the same at the exit, modulo
> normal queuing jitter.


Here's an example:

The first N packets do       Src -> A -> B -> A -> B -> A -> B ->Dst

The second set of packets do Src -> A -> B -> A -> B ->Dst

The third set of packets do  Src -> A -> B ->Dst

Now if you get everything _just right_ in terms of timings (and that 
will be tricky) you can get all 3 sets of packets released to the 
destination in a burst that is up to 3 x the input packet rate in this 
example.

And, yes there are probably simpler DDOS attacks out there! I was simply 
trying to explain what the original work and Joe's draft referred to 
when they referred to "capacitance attacks".


regards,

   Geoff



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 07 23:56:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwVae-00081Y-6r; Thu, 07 Jun 2007 23:56:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwVac-00081R-NZ
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:56:42 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwVaa-0007CE-9m
	for ipv6@ietf.org; Thu, 07 Jun 2007 23:56:42 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id CD2B011429
	for <ipv6@ietf.org>; Fri,  8 Jun 2007 03:56:39 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "'Ipv'" <ipv6@ietf.org>
In-Reply-To: Your message of "Thu, 07 Jun 2007 19:04:24 MST."
	<0b9e01c7a971$57c7d0e0$075772a0$@net> 
References: <46685BFC.9090904@innovationslab.net>
	<EF2F0EC839870F43A6637360BC12ABD40232683F@PACDCEXCMB05.cable.comcast.com>
	<0b9e01c7a971$57c7d0e0$075772a0$@net> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 08 Jun 2007 03:56:39 +0000
Message-ID: <38056.1181274999@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> ARIN & NANOG are nothing more than heat lately (all hot air?). As I
> suggested at NANOG this week, the right thing to do is for the WG to define
> the space, and turn it over to IANA to manage.

the internet's addressing system uses a combination of top-down architectural
guideance (from IAB and IESG and the WGs) and bottom-up operational policy
guideance (from the RIRs).  the fact that this proposal is garnering a lot
of heat from the bottom-up side of the process ought to be a strong hint
that the top-down side ought to listen carefully and use great caution.

> Beyond that it was all policy anyway, so the fact that it is defined makes
> no difference if policy chooses to ignore it. Not defining it leaves policy
> with no alternative but to succumb to those that want nothing more than to
> exercise power through control of the address space.
> 
> I say wrap it up and ship it. 

if that's what we're doing, then, i say kill it.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 00:42:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwWId-0002q0-HK; Fri, 08 Jun 2007 00:42:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwWIc-0002mH-6T
	for ipv6@ietf.org; Fri, 08 Jun 2007 00:42:10 -0400
Received: from an-out-0708.google.com ([209.85.132.249])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwWIb-0006dk-0D
	for ipv6@ietf.org; Fri, 08 Jun 2007 00:42:10 -0400
Received: by an-out-0708.google.com with SMTP id c17so158541anc
	for <ipv6@ietf.org>; Thu, 07 Jun 2007 21:42:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ads2j4hDKyNR7dHkLplc0sPCFG2GAiIzNsgrSSLqjUQl0j59x6eBWEkVUQC/KLQLa2gFIXqmn5WOQbdBRbjrnDBiXTUfqBOYSdD6v0Q11PjwC+3uzlxBg7KNViMiNpocoQ5jwM33UeTO/Dt9SNJxt7TfoKcZd2IgHw1FUi0PRrU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=b+AR+5q94Ibw6oLOiI+UIm2peoOaw8URDk0iUjiwCa010Wf1Z0uMTYKnxdupmgEGAN4Q5Ll6+DBNiceyDi/9Ra1lzBbX68bEEbXhbRYm0jGKVb/Gk6egLNJ7pCjaMu0IFNLXBlolz4w7OFKzdrxR32WrIIgqumyFP1t7FO004Ag=
Received: by 10.114.60.19 with SMTP id i19mr2167062waa.1181277728380;
	Thu, 07 Jun 2007 21:42:08 -0700 (PDT)
Received: by 10.114.93.7 with HTTP; Thu, 7 Jun 2007 21:42:08 -0700 (PDT)
Message-ID: <75cb24520706072142l4a2ed48an5f6972f5c0292a3c@mail.gmail.com>
Date: Fri, 8 Jun 2007 00:42:08 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "Pekka Savola" <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706050922041.2967@netcore.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0706031133u35e518c1gcfcfaa0ff625218@mail.gmail.com>
	<46631250.30407@spaghetti.zurich.ibm.com>
	<77ead0ec0706031920g7a3f52c8g1d2df5005ffcedcd@mail.gmail.com>
	<Pine.LNX.4.64.0706040806240.31082@netcore.fi>
	<77ead0ec0706040823n17961373rc183e5afa1ffbfc3@mail.gmail.com>
	<Pine.LNX.4.64.0706050922041.2967@netcore.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org
Subject: Re: Checks for amplification attack
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 6/5/07, Pekka Savola <pekkas@netcore.fi> wrote:

> As an operator, I do not wish to buy routers that are DoS'able or
> whose control processor CPU resources can be wasted on inspecting
> transiting traffic. "Punting packets to the slow path" is one primary
> thing that a high-speed router should not have to do.  I think I'm not
> alone in the operator field with this sentiment.

you are not alone.

>
> Oh yeah, hop-by-hop extension header should be retired as well :-)
>

i hate to sound heretical, but perhaps having an option to 'not
process', one to 'process' and one to 'drop if having' is called for?
I need to read the jabley-draft I think now too.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 02:42:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwYAD-0002DT-Lf; Fri, 08 Jun 2007 02:41:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwYAB-0002D9-Jz
	for ipv6@ietf.org; Fri, 08 Jun 2007 02:41:35 -0400
Received: from mx2.its.eads.net ([193.56.40.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwYA9-0006Cc-Nz
	for ipv6@ietf.org; Fri, 08 Jun 2007 02:41:35 -0400
Received: from fr-gate2.mailhub.intra.corp ([53.154.16.34]) by
	mx2.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); 
	Fri, 8 Jun 2007 08:39:07 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate2.mailhub.intra.corp
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 8 Jun 2007 08:44:27 +0200
Received: from [172.16.23.108] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id H92Z3WNB; Fri, 8 Jun 2007 08:42:00 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-Mailer: Apple Mail (2.752.2)
Content-class: urn:content-classes:message
Date: Fri, 8 Jun 2007 08:41:22 +0200
Message-ID: <594C9952-627F-48AA-8C6F-747ABB6A2BC6@eads.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
Thread-Index: AcepmB419vGcbh4NRsOlcOkjyejsCQ==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: "Joe Abley" <jabley@ca.afilias.info>
X-OriginalArrivalTime: 08 Jun 2007 06:44:27.0226 (UTC)
	FILETIME=[755953A0:01C7A998]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, alh-ietf@tndh.net
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hello,

Le 8 juin 07 =E0 04:40, Joe Abley a =E9crit :

> My understanding of the CanSecWest authors' thinking with respect to
> this particular technique is that the number of (A, B) waypoints in
> the RH0 header would be varied such that for every one packet that
> entered the A-B cyclotron, you could achieve N packets leaving
> simultaneously, each having been round the A-B loop a different
> number of times.

That's a good summary.

The values given in the slide are based on the simple computation of =20
the number of packet you can inject per second : this depends on your =20
upload bandwidth, the PMTU and the number of addresses in the RH0 =20
(less addresses, more packets, as they are shorter).

> Maximising the output of such a capacitor would require tuning the
> RH0 extension header construction according to the observed round-
> trip latency between A and B which seems non-trivial, but at the same
> time not impossible.

True, it is non-trivial.

> Note that I have not explored the details of this with the CanSecWest
> presenters, however; it's possible that they were thinking of
> something different (and equally plausible that there's a fault with
> my logic, above).

nope, not AFAIK.

a+

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 03:14:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwYfl-0008Qa-6q; Fri, 08 Jun 2007 03:14:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwYfj-0008QN-FY
	for ipv6@ietf.org; Fri, 08 Jun 2007 03:14:11 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HwYfh-0007fH-Rm
	for ipv6@ietf.org; Fri, 08 Jun 2007 03:14:11 -0400
Received: by ug-out-1314.google.com with SMTP id j30so2307248ugc
	for <ipv6@ietf.org>; Fri, 08 Jun 2007 00:14:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=GmF4ifBK7tDkuyf4vwa8KC4JWA2rd7Vww1Eai3gV6OhElvJWb3wk5GhYhi4JpFqXwGpDesy32KFsdK+pFqWQIwslU7dDjg/NaVAyjSehGLg0+QLtbcc7tUznbZEfE9LHGEKBjk/HZZymwNAYGTV2+Cxtc4WLmruTOorWlwxGgcQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=MtZwb0yvFblNmDxCO06NLtnkM3e8vRw7XcGlKSZXfOHyZu+VqNiqW/z4adwCkB/x6+D5J6FfkWOrMsarg++VC/zRhWk4Gs0pfI8kaNdZ/syHbBGQJq/yxZ7Zb+RH1Qqz0/st+FjH1L3mjLFHD7ZeoflZ/+cPHDQ2G0FoXZ9TMC0=
Received: by 10.67.96.14 with SMTP id y14mr1970078ugl.1181286848751;
	Fri, 08 Jun 2007 00:14:08 -0700 (PDT)
Received: from ?9.159.130.110? ( [195.212.29.187])
	by mx.google.com with ESMTP id w40sm1715014ugc.2007.06.08.00.14.05
	(version=SSLv3 cipher=RC4-MD5); Fri, 08 Jun 2007 00:14:06 -0700 (PDT)
Message-ID: <466901BC.8040902@gmail.com>
Date: Fri, 08 Jun 2007 09:14:04 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <46685BFC.9090904@innovationslab.net>
In-Reply-To: <46685BFC.9090904@innovationslab.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I trust that the new version will include the proposal
for a fully robotic solution for creating and escrowing
guaranteed-unique ULAs. That's the only missing property in
existing ULAs, and we should certainly consider a purely
robotic solution with no need for registry action or registry
policy of any kind.

     Brian

On 2007-06-07 21:26, Brian Haberman wrote:
> All,
>      There has been recent activity in the Registry Community looking at
> policies utilizing the Centrally Assigned ULA specification that has
> expired.  Several people with ties to both the IETF and the RIRs have
> been working with the authors to revise the specification in order to
> meet the needs of the policy proposals in the RIRs.
> 
>      Given that the previous work on Centrally Assigned ULAs was adopted
> as an IPv6 WG document, the chairs feel that this upcoming revision
> should be considered a continuation of that work.
> 
>      The chairs highly encourage people interested in this work to
> review and comment on the upcoming revision when it is published.
> 
>      As a note, Bob will be the responsible editor for this document and
> Brian will be the shepherding WG chair.
> 
> Regards,
> Brian and Bob
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 07:21:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwcWb-0006Pq-3H; Fri, 08 Jun 2007 07:21:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwcQW-0001eC-JG
	for ipv6@ietf.org; Fri, 08 Jun 2007 07:14:44 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwcQV-0002Kc-9t
	for ipv6@ietf.org; Fri, 08 Jun 2007 07:14:44 -0400
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.34046997;
	Fri, 08 Jun 2007 07:14:30 -0400
Message-ID: <46693A16.8050103@innovationslab.net>
Date: Fri, 08 Jun 2007 07:14:30 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: alh-ietf@tndh.net
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>	<20070607.191659.14348043.he@uninett.no>
	<0b9c01c7a970$364dfb20$a2e9f160$@net>
In-Reply-To: <0b9c01c7a970$364dfb20$a2e9f160$@net>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-Mailman-Approved-At: Fri, 08 Jun 2007 07:20:59 -0400
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Tony,

Tony Hain wrote:
> Havard Eidnes wrote:
>> <counter-rant>
>>
>> All this monomanic ISP-bashing needs to stop now, if IPv6 is ever
>> to take off in any manner.
>>
>> The claim that RH0 is "just a tool" and that there is no
>> "amplification"
>> is narrow-sighted at best, since I understood from what has been
>> discussed here that it can indeed cause excessive bandwith utilization
>> along a path, and is therefore a much too useful tool in a miscreant's
>> hand to let loose on the unsuspecting masses.
> 
> So fix it by restricting the number of waypoints. Killing it only prevents
> valid uses.

I am thinking that it is easier to fix by deprecating RH0 and then
defining a new routing header with stricter properties.  Similar to the
MIPv6 routing header.  That way, the safer RH option can be clearly
identified in the wild and won't be blocked/restricted/blocked by
filters meant to protect networks/nodes from the RH0 attacks.

Regards,
Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 07:59:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwd82-0006Qh-H8; Fri, 08 Jun 2007 07:59:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwd81-0006Qb-Ua
	for ipv6@ietf.org; Fri, 08 Jun 2007 07:59:41 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwd80-00006E-OC
	for ipv6@ietf.org; Fri, 08 Jun 2007 07:59:41 -0400
Received: from ([10.52.116.31])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.4368692;
	Fri, 08 Jun 2007 07:59:25 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 8 Jun 2007 07:59:25 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 8 Jun 2007 07:59:22 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD402326919@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <38056.1181274999@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcepgRdGf581nXDxQmekp5sHng4vxAAQtoUQ
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Paul Vixie" <paul@vix.com>,
	"Ipv" <ipv6@ietf.org>
X-OriginalArrivalTime: 08 Jun 2007 11:59:25.0223 (UTC)
	FILETIME=[756ED370:01C7A9C4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Thursday, June 07, 2007 11:57 PM
> To: 'Ipv'
> Subject: Re: Revising Centrally Assigned ULA draft=20
>> > I say wrap it up and ship it.=20
>=20
> if that's what we're doing, then, i say kill it

This email exchange is the proof that an open discussion is needed.
The IETF IPv6 wg doing a contraversial thing on its own without
listening to the input from the operational people is not productive,
the last thing the community need is yet another power struggle.

   - Alain.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 11:13:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwg94-0008Rm-Ca; Fri, 08 Jun 2007 11:12:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwg5K-0001Iu-9f
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:09:06 -0400
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwg5J-0003H0-3o
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:09:06 -0400
Received: from ([128.244.206.105])
	by piper.jhuapl.edu with ESMTP  id 5502121.31573954;
	Fri, 08 Jun 2007 11:08:52 -0400
Message-ID: <46697103.6080004@innovationslab.net>
Date: Fri, 08 Jun 2007 11:08:51 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
References: <EF2F0EC839870F43A6637360BC12ABD402326919@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD402326919@PACDCEXCMB05.cable.comcast.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
X-Mailman-Approved-At: Fri, 08 Jun 2007 11:12:56 -0400
Cc: Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

All,

Durand, Alain wrote:
>  
> 
>> -----Original Message-----
>> From: Paul Vixie [mailto:paul@vix.com] 
>> Sent: Thursday, June 07, 2007 11:57 PM
>> To: 'Ipv'
>> Subject: Re: Revising Centrally Assigned ULA draft 
>>>> I say wrap it up and ship it. 
>> if that's what we're doing, then, i say kill it
> 
> This email exchange is the proof that an open discussion is needed.
> The IETF IPv6 wg doing a contraversial thing on its own without
> listening to the input from the operational people is not productive,
> the last thing the community need is yet another power struggle.

Before this thread gets any deeper in a rat hole, allow me to point out
a few things.

1. The discussion of reviving Centrally Assigned ULAs originated in the
RIR community

2. A new draft of the spec *with significant changes* is being worked on

3. Input for the revised draft is coming from the RIR community

Rather than assume the contents of the draft and argue their merits,
please wait for the posting of the new draft and then comment.

Regards,
Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 11:17:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwgD4-0005uC-Jc; Fri, 08 Jun 2007 11:17:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwgD2-0005u4-PB
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:17:04 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwgD2-0008Te-Br
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:17:04 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l58FF8wk012528
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 8 Jun 2007 08:15:08 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l58FF89d012526;
	Fri, 8 Jun 2007 08:15:08 -0700 (PDT)
Date: Fri, 8 Jun 2007 08:15:08 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20070608151508.GA7432@boreas.isi.edu>
References: <46685BFC.9090904@innovationslab.net> <466901BC.8040902@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <466901BC.8040902@gmail.com>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Brian Haberman <brian@innovationslab.net>, Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


presuming this course of action is taken, it raises a much larger
issue consisting of the IETF creating "property rights" in the 
address space arena.  To date, (AFAIK)  most legal arguments have
taken the line that IP addresses are NOT property, come from a
common resource that the RIR's administer for the good of the 
community.   ULA-C  carves out a bit of IP space and in the absence
of RIR oversight, creates "property"... creating an ambigious
set of legal issues which will be fought for years.  

I -REALLY- am uncomfortable w/ the IETF, in a mothballed WG,
creating this nightmare for the operational community.

--bill


On Fri, Jun 08, 2007 at 09:14:04AM +0200, Brian E Carpenter wrote:
> I trust that the new version will include the proposal
> for a fully robotic solution for creating and escrowing
> guaranteed-unique ULAs. That's the only missing property in
> existing ULAs, and we should certainly consider a purely
> robotic solution with no need for registry action or registry
> policy of any kind.
> 
>     Brian
> 
> On 2007-06-07 21:26, Brian Haberman wrote:
> >All,
> >     There has been recent activity in the Registry Community looking at
> >policies utilizing the Centrally Assigned ULA specification that has
> >expired.  Several people with ties to both the IETF and the RIRs have
> >been working with the authors to revise the specification in order to
> >meet the needs of the policy proposals in the RIRs.
> >
> >     Given that the previous work on Centrally Assigned ULAs was adopted
> >as an IPv6 WG document, the chairs feel that this upcoming revision
> >should be considered a continuation of that work.
> >
> >     The chairs highly encourage people interested in this work to
> >review and comment on the upcoming revision when it is published.
> >
> >     As a note, Bob will be the responsible editor for this document and
> >Brian will be the shepherding WG chair.
> >
> >Regards,
> >Brian and Bob
> >
> >
> >--------------------------------------------------------------------
> >IETF IPv6 working group mailing list
> >ipv6@ietf.org
> >Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> >--------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 11:22:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwgI5-0002k9-Fd; Fri, 08 Jun 2007 11:22:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwgI3-0002jw-Rn
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:22:15 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HwgI2-0003OF-R9
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:22:15 -0400
Received: from eagle (127.0.0.1:2463)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S33B56B> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 8 Jun 2007 08:21:23 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Joe Abley'" <jabley@ca.afilias.info>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
	<05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
In-Reply-To: <05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
Date: Fri, 8 Jun 2007 08:21:22 -0700
Message-ID: <0bc501c7a9e0$c147dff0$43d79fd0$@net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcepdnLDzDogwTbYR0aYsfkx44RqfgAEOdow
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8cb9b411340046bf4080a729180a0672
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Joe Abley wrote:
> ...
> That's a valid editorial point, thanks.
> 
> > and it is only one
> > packet at a time that has to wait for reception before being
> > reflected back.
> 
> No, that's not the case. Packets constructed with an RH0 extension
> header containing intermediate addresses A and B, N times (so, for
> example, if N=5 then RH0 contains ten addresses, A B A B A B A B A B)
> can be injected into the A-B cyclotron as rapidly as the path between
> the origin and A allows, without ever waiting for a response.

And as soon as they are at A the packets have to wait for head of line
blocking to get to B. 

> 
> So long as the injection rate is higher than 1/(N*T) where T is the
> round-trip delay between A and B, the traffic impact between A and B
> will exceed that between the origin and A, N-fold.
> 
> > The total traffic volume over a given path may be higher, but this
> > is not a
> > multiplication of the number of streams.
> 
> It's a multiplication of the amount of traffic being carried, though.
> The ability to cause 88Mbit/s of traffic in a remote network with
> only 1Mbit/s of effort is surely an amplification effect (and surely
> a concern).

So fix the spec so there is only one RH0 allowed. Killing it does not
prevent exploitation of the network. If exploitation is such a threat then
we need to kill off ICMP because it is a much more widely used attack vector
than routing headers.

> 
> >>     This technique can also be used as a more general traffic
> >> amplifier,
> >>     accumulating attack traffic in-flight between two well-connected
> >> but
> >>     mutually-distant waypoints and then finally delivering it
> >> towards a
> >>     third party once the RH0-directed oscillations for each packet
> >> are
> >>     complete. 7-fold amplification has been postulated using this
> >>     "capacitive effect" [CanSecWest07].
> >
> > The discussion about 3rd party implies this is related to spoofing.
> 
> No, not at all. The victim address in this case is a destination
> address, not a source address.

Due to serialization delay the victim will never be the destination. It
might be the upstream router queue from the destination, but the nice
mathematical theory about instantaneous convergence falls flat when reality
strikes in the form of bit serialization. 

> 
> My understanding of the CanSecWest authors' thinking with respect to
> this particular technique is that the number of (A, B) waypoints in
> the RH0 header would be varied such that for every one packet that
> entered the A-B cyclotron, you could achieve N packets leaving
> simultaneously, each having been round the A-B loop a different
> number of times.

Unless they vary the actual A & B with the destination behind a richly
connected fabric, the packets will never converge at exactly the same time.
Even if they did vary A & B, the packets can't exit simultaneously because
they have to queue up to get over that interface. 

> 
> Maximising the output of such a capacitor would require tuning the
> RH0 extension header construction according to the observed round-
> trip latency between A and B which seems non-trivial, but at the same
> time not impossible.

Converging packet streams onto an interface queue is much simpler using an
army of zombies in a ddos attack. Why would anyone waste time trying to game
a dynamic state where the tuning would have to be precise, and would easily
be disrupted by 3rd party traffic on the path? Unless someone can provide
the working code, this does not belong in any document because it is just
conjecture. 

> 
> Note that I have not explored the details of this with the CanSecWest
> presenters, however; it's possible that they were thinking of
> something different (and equally plausible that there's a fault with
> my logic, above).

You essentially described the same thing Geoff Huston did, so I suspect your
reading is not flawed. Their premise on the other hand is because the
reality of interface queuing and clocking invalidates the claimed result of
a simultaneous arrival. 

> 
> >>     Various IPv6 transition mechanisms involve the transmission of
> >> IPv6
> >>     packets through tunnels built on IPv4 infrastructure (e.g.
> >>     [RFC2893], [RFC3056]).  Tunnels remain widely-used at the time
> of
> >>     writing for the transmission of IPv6 traffic over IPv4 networks.
> >> The
> >>     use of such tunnels can result in IPv6 paths which include a
> >> small
> >>     number of routers apparently connected by very high latency
> >> circuits
> >>     (tunnels).  Such paths provide opportunities to keep packets in-
> >>     flight for longer, with corresponding increases in amplification
> >>     potential.
> >
> > This is absolute BS. The type of path has absolutely nothing to do
> > with the
> > 'opportunity' to exercise the exploit,
> 
> Right, but the round-trip path latency does (see above).
> 
> >>> The crap in the document about an anycast destination being
> >>> an amplification shows how little understanding there is about the
> >>> concept.
> >>
> >> If you can find text that equates an anycast destination being "an
> >> amplification", please point it out so I can remove it.
> >
> > 5.4
> >    By including RH0 with a waypoint address within the catchment
> > area of
> >    a remote anycast node, a single client can send traffic to
> multiple
> >    anycast nodes providing the same service, avoiding the isolation
> of
> >    such traffic to a single node which would otherwise result.
> >
> > The traffic will always go to one-and-only-one anycast node.
> 
> Not with widespread RH0 support; that's the point this section
> attempts to make. With RH0 support a single origin can send packets
> which will arrive at different anycast nodes, regardless of the
> natural (no-RH0) node that would normally receive the traffic.

The world should tremble in fear ... a single node can send individual
packets to more than one destination ?!?!?!?!   This section is still worded
wrong. Any single packet will always go to a single destination. Use of RH0
does not result in a single packet arriving at multiple anycast
destinations. 

The entire title of 5.4 is wrong, anycast is not defeated, the packet still
arrives at one-and-only-one of the anycast instances. Depending on where the
RH0 target is, that MAY be a different instance that would occur without the
routing header. 

Clearly the reason this text was put in was someone wants the entire world
to be forced into their policy model where nodes are not allowed to route
around a broken instance of an anycast service. Flash crowd containment
still happens, it just may be that a different instance of the service feels
the pain than what was expected. Load distribution is the goal for anycast,
even in the flash-crowd-containment scenario. Clearly somebody doesn't like
the idea that the end user should have the ability to select an instance if
the local one is broken, so again I say this entire effort is not about
fixing brokenness, it is about power and control over the lowly end user.

> 
> >>> Anycast == 'unicast to the nearest instance'.
> >>
> >> Indeed. I was one of the authors of BCP 126 and have some
> familiarity
> >> with the concept.
> >
> > Unfortunately the text in 5.4 does not reflect that.
> 
> I have not yet understood your point (or you have not understood
> mine). I'm not convinced that we have a problem in 5.4, yet.

The existing language effectively says that packets to an anycast dst which
have an RH0 header will arrive at multiple instances. I know you are trying
to say that 'the source node gets to select the anycast instance', but that
is not what this says, and if you said it the way I did it would not
generate the hysteria needed to get consensus. 

> 
> > That was a rant, related to multiple days of off list FUD from
> > obstinate ISP
> > types that want to remove any capability for IPv6 to allow the end
> > users to
> > exercise any control.
> 
> I am sympathetic to the problem; if I had a magic wand that would
> allow press coverage of technical issues to be (a) accurate and (b)
> fully understood by all who read it, I would wave it :-)
> 
> However, this seems orthogonal to the technical issue.

The issue at hand is that RH0 should be limited to 1 or 2 to avoid the
bounce problem. Other than that this is all about control which is also a
non-technical issue, so exactly why are we doing this again?

> 
> > Since this document is about killing off a technology
> > that is required for a metro/geo business model, and it started
> > life as
> > *-evil-*, it automatically gets bucketed in with the ISP myopia
> > about end
> > users having any form of control.
> 
> There's a long history of "-is-evil-" being used in document names in
> the IETF, and it's common argot amongst operators when describing
> things that have unpleasant side-effects (see, for example, the
> recent, huge NANOG thread on NAT, where NAT was declared as being
> evil about every three messages).

I am aware of that, and those almost always start as non-technical 'I want
control' nonsense. As for the nanog thread on nat, the other 2 of 3 messages
were defending nat as the savior of the universe and absolutely necessary in
IPv6 networks. 

NANOG has stopped being a useful technical reference because it is all about
religion. 

> 
> You know this, of course. I feel your frustration, and I appreciate
> that one more reason not deploy IPv6 amongst operators of any share
> is not something that is going to make for a happy fun day for you.
> However, I don't think that blaming my earlier document name for non-
> deployment of IPv6 in this case is reasonable.

Lack of deployment of IPv6 has nothing to do with IETF documentation. It is
all about the unwillingness of the 'guru cult' to risk their status by
trying to learn something different. The desperation is becoming more
apparent though as the reality of the end of IPv4 storms over the horizon. 

RH0 is not a threat if limited to 1 or 2. I can't come up with a reason for
more than one, but I am willing to believe there are use cases. 

> 
> > I have no problem limiting the number of
> > RH0 segments, but killing it off is a knee-jerk reaction to a well
> > known
> > exploit. TCP-SYN can be exploited, but I don't see calls to
> > deprecate TCP
> > ...
> 
> The well-known exploit in this case was judged by this working group
> to have minimal demonstrated application in the real world, and non-
> trivial risks associated with its availability, hence the decision to
> deprecate.

That is because it's applicability is to an environment that can't get
formed until there is sufficient deployment of IPv6 to force the point that
alternative aggregation models to PA and swamp PI are required. Metro/geo in
addition to PA/PI will allow scaling capabilities to the masses, but making
those work requires at least a one hop RH0.

> 
> If you think that judgement of consensus by the wg chairs was wrong,
> then that seems like something best taken up with them; this document
> is a reaction to that consensus, not a proponent of it.

Hopefully I will get some time in the next couple of weeks to draft an
alternative viewpoint related to fixing RH0. Claiming that consensus was
reached in the middle of press and mail list hysteria is a stretch. At the
same time there is precedent in the SL fiasco. 

> 
> > Section 7
> > This presentation resulted in widespread publicity for the risks
> > associated
> > with RH0.
> >
> > s/publicity/hysteria
> 
> It seems like it would be unusual to see one without the other.
> 
> 
> Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 11:40:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwga1-0006Kl-LX; Fri, 08 Jun 2007 11:40:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwga0-0006Kc-Nj
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:40:48 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwgZz-00042d-EA
	for ipv6@ietf.org; Fri, 08 Jun 2007 11:40:48 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id CEFD311425;
	Fri,  8 Jun 2007 15:40:46 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Brian Haberman <brian@innovationslab.net>
In-Reply-To: Your message of "Fri, 08 Jun 2007 11:08:51 -0400."
	<46697103.6080004@innovationslab.net> 
References: <EF2F0EC839870F43A6637360BC12ABD402326919@PACDCEXCMB05.cable.comcast.com>
	<46697103.6080004@innovationslab.net> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 08 Jun 2007 15:40:46 +0000
Message-ID: <15051.1181317246@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Rather than assume the contents of the draft and argue their merits,
> please wait for the posting of the new draft and then comment.

i understood alain to be asking that the ipv6 wg be de-mothballed in
order that the upcoming revised ULA I-D will be properly reviewed.  i
hope that alain may even be willing to serve as interrim wg chair.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 12:06:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwgyJ-00087N-EZ; Fri, 08 Jun 2007 12:05:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwgyI-00087G-6G
	for ipv6@ietf.org; Fri, 08 Jun 2007 12:05:54 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwgyG-000595-VI
	for ipv6@ietf.org; Fri, 08 Jun 2007 12:05:54 -0400
Received: from ([10.52.116.30])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.4381751;
	Fri, 08 Jun 2007 12:05:28 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 8 Jun 2007 12:05:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 8 Jun 2007 12:05:27 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD4014B9051@PACDCEXCMB05.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: Acep3wLcHL1/f7K6RxSTlRk7IEATywAB9GjF
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: <brian@innovationslab.net>
X-OriginalArrivalTime: 08 Jun 2007 16:05:28.0791 (UTC)
	FILETIME=[D5348670:01C7A9E6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0179908287=="
Errors-To: ipv6-bounces@ietf.org

--===============0179908287==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SSBkbyBub3QgaGF2ZSBhbiBpc3N1ZSAoeWV0Pykgd2l0aCB0aGUgZHJhZnQuIEkgaGF2ZSBhbiBp
c3N1ZSB3aXRoIHRoZSBwcm9jZXNzIHRvIGNyZWF0ZSBhIGRyYWZ0IGFib3V0IGEgdmVyeSBjb250
cm92ZXJzaWFsIGlzc3VlIGluIGEgd2cgdGhhdCBpcyBub3QgbWVldGluZyBmYWNlIHRvIGZhY2Uu
DQoNCiAgLSBBbGFpbi4gDQogDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZyb206
IEJyaWFuIEhhYmVybWFuIDxicmlhbkBpbm5vdmF0aW9uc2xhYi5uZXQ+DQpUbzogRHVyYW5kLCBB
bGFpbg0KQ2M6IFBhdWwgVml4aWUgPHBhdWxAdml4LmNvbT47IElwdiA8aXB2NkBpZXRmLm9yZz4N
ClNlbnQ6IEZyaSBKdW4gMDggMTE6MDg6NTEgMjAwNw0KU3ViamVjdDogUmU6IFJldmlzaW5nIENl
bnRyYWxseSBBc3NpZ25lZCBVTEEgZHJhZnQNCg0KQWxsLA0KDQpEdXJhbmQsIEFsYWluIHdyb3Rl
Og0KPiAgDQo+IA0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IFBhdWwg
Vml4aWUgW21haWx0bzpwYXVsQHZpeC5jb21dIA0KPj4gU2VudDogVGh1cnNkYXksIEp1bmUgMDcs
IDIwMDcgMTE6NTcgUE0NCj4+IFRvOiAnSXB2Jw0KPj4gU3ViamVjdDogUmU6IFJldmlzaW5nIENl
bnRyYWxseSBBc3NpZ25lZCBVTEEgZHJhZnQgDQo+Pj4+IEkgc2F5IHdyYXAgaXQgdXAgYW5kIHNo
aXAgaXQuIA0KPj4gaWYgdGhhdCdzIHdoYXQgd2UncmUgZG9pbmcsIHRoZW4sIGkgc2F5IGtpbGwg
aXQNCj4gDQo+IFRoaXMgZW1haWwgZXhjaGFuZ2UgaXMgdGhlIHByb29mIHRoYXQgYW4gb3BlbiBk
aXNjdXNzaW9uIGlzIG5lZWRlZC4NCj4gVGhlIElFVEYgSVB2NiB3ZyBkb2luZyBhIGNvbnRyYXZl
cnNpYWwgdGhpbmcgb24gaXRzIG93biB3aXRob3V0DQo+IGxpc3RlbmluZyB0byB0aGUgaW5wdXQg
ZnJvbSB0aGUgb3BlcmF0aW9uYWwgcGVvcGxlIGlzIG5vdCBwcm9kdWN0aXZlLA0KPiB0aGUgbGFz
dCB0aGluZyB0aGUgY29tbXVuaXR5IG5lZWQgaXMgeWV0IGFub3RoZXIgcG93ZXIgc3RydWdnbGUu
DQoNCkJlZm9yZSB0aGlzIHRocmVhZCBnZXRzIGFueSBkZWVwZXIgaW4gYSByYXQgaG9sZSwgYWxs
b3cgbWUgdG8gcG9pbnQgb3V0DQphIGZldyB0aGluZ3MuDQoNCjEuIFRoZSBkaXNjdXNzaW9uIG9m
IHJldml2aW5nIENlbnRyYWxseSBBc3NpZ25lZCBVTEFzIG9yaWdpbmF0ZWQgaW4gdGhlDQpSSVIg
Y29tbXVuaXR5DQoNCjIuIEEgbmV3IGRyYWZ0IG9mIHRoZSBzcGVjICp3aXRoIHNpZ25pZmljYW50
IGNoYW5nZXMqIGlzIGJlaW5nIHdvcmtlZCBvbg0KDQozLiBJbnB1dCBmb3IgdGhlIHJldmlzZWQg
ZHJhZnQgaXMgY29taW5nIGZyb20gdGhlIFJJUiBjb21tdW5pdHkNCg0KUmF0aGVyIHRoYW4gYXNz
dW1lIHRoZSBjb250ZW50cyBvZiB0aGUgZHJhZnQgYW5kIGFyZ3VlIHRoZWlyIG1lcml0cywNCnBs
ZWFzZSB3YWl0IGZvciB0aGUgcG9zdGluZyBvZiB0aGUgbmV3IGRyYWZ0IGFuZCB0aGVuIGNvbW1l
bnQuDQoNClJlZ2FyZHMsDQpCcmlhbg0K


--===============0179908287==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0179908287==--



From ipv6-bounces@ietf.org Fri Jun 08 12:11:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwh41-0006Oi-Tl; Fri, 08 Jun 2007 12:11:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwh40-0006Oa-3L
	for ipv6@ietf.org; Fri, 08 Jun 2007 12:11:48 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwh3y-0007qs-QK
	for ipv6@ietf.org; Fri, 08 Jun 2007 12:11:48 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l58GBjhm013170
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 8 Jun 2007 11:11:45 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l58GBjQI006249; Fri, 8 Jun 2007 11:11:45 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l58GBZGV005967; Fri, 8 Jun 2007 11:11:44 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 8 Jun 2007 09:11:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 8 Jun 2007 09:11:37 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED862@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <46697103.6080004@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: Acep341Y03QdfOGrSY6o6/YQj3stRAAB51gw
References: <EF2F0EC839870F43A6637360BC12ABD402326919@PACDCEXCMB05.cable.comcast.com>
	<46697103.6080004@innovationslab.net>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Brian Haberman" <brian@innovationslab.net>,
	"Durand, Alain" <Alain_Durand@cable.comcast.com>
X-OriginalArrivalTime: 08 Jun 2007 16:11:38.0639 (UTC)
	FILETIME=[B1A6D9F0:01C7A9E7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: Ipv <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Given that there are other important documents still
being actively finalized within the wg, I don't see
a problem with Brian's suggested approach.

Fred
fred.l.templin@boeing.com
=20

> -----Original Message-----
> From: Brian Haberman [mailto:brian@innovationslab.net]=20
> Sent: Friday, June 08, 2007 8:09 AM
> To: Durand, Alain
> Cc: Ipv
> Subject: Re: Revising Centrally Assigned ULA draft
>=20
> All,
>=20
> Durand, Alain wrote:
> > =20
> >=20
> >> -----Original Message-----
> >> From: Paul Vixie [mailto:paul@vix.com]=20
> >> Sent: Thursday, June 07, 2007 11:57 PM
> >> To: 'Ipv'
> >> Subject: Re: Revising Centrally Assigned ULA draft=20
> >>>> I say wrap it up and ship it.=20
> >> if that's what we're doing, then, i say kill it
> >=20
> > This email exchange is the proof that an open discussion is needed.
> > The IETF IPv6 wg doing a contraversial thing on its own without
> > listening to the input from the operational people is not=20
> productive,
> > the last thing the community need is yet another power struggle.
>=20
> Before this thread gets any deeper in a rat hole, allow me to=20
> point out
> a few things.
>=20
> 1. The discussion of reviving Centrally Assigned ULAs=20
> originated in the
> RIR community
>=20
> 2. A new draft of the spec *with significant changes* is=20
> being worked on
>=20
> 3. Input for the revised draft is coming from the RIR community
>=20
> Rather than assume the contents of the draft and argue their merits,
> please wait for the posting of the new draft and then comment.
>=20
> Regards,
> Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 13:54:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwiel-0001WN-2T; Fri, 08 Jun 2007 13:53:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwiej-0001WH-Mr
	for ipv6@ietf.org; Fri, 08 Jun 2007 13:53:49 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwieh-0007Sh-3S
	for ipv6@ietf.org; Fri, 08 Jun 2007 13:53:49 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181328654; x=1181933454; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=MqBMTY3F7LVTxX
	ClH1pVWl7ng/8Zf35XKzhBSm3z2Pgkn/zs5kqLmfMNGTmx/qt8qsqMC/qyWrWMI4
	pcB+H7mE7V9OGig79es1A0VqLCEs6nRkKQNM+QHPiHhbEgT6egHvLDMWCwUl1NAa
	Do13+onUoD3W3UJeXMRn5zSRePqPE=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=p8Wrje6WW1PTDGYUyhecR8ooPudGAVDvOBu4e5EC8Opkd4CJzFNsYwdwZUZvUysL1Gcr4MKYT9kUlxfBMOU7E+KkOi47chwXdK38WsOH7D8oEPjQftaUqho8t15i05+zmXVIdXOMiqERnjib2hj7E5xvrejgCper0AY/q9H8tMM=;
Received: from [10.10.10.50] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002537476.msg
	for <ipv6@ietf.org>; Fri, 08 Jun 2007 19:50:53 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 08 Jun 2007 19:53:45 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C28F6449.19D6B9%jordi.palet@consulintel.es>
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: Acep3wLcHL1/f7K6RxSTlRk7IEATywAB9GjFAAPIMFI=
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD4014B9051@PACDCEXCMB05.cable.comcast.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070608:ipv6@ietf.org::0uKGuwTnEwJe3ami:00003nBv
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Fri, 08 Jun 2007 19:50:54 +0200
X-MDAV-Processed: consulintel.es, Fri, 08 Jun 2007 19:50:54 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Alain,

The IETF doesn't take decision on face to face meetings, so that should not
be a problem, because we can look for consensus in the mailing list.

Furthermore, it is not a new draft, is a new version. It reached consensus
in the previous round. Now we took the time and further experience to
improve it.

I don't see anything wrong in the process, in fact, we should have sent it
to the last call in the previous round, so now it may become a new version
anyway.

I also believe that Fred offered some time in v6ops agenda to discuss about
that. I don't think that's again the process, especially considering that
most of the people in both WG is the same.

Regards,
Jordi




> De: "Durand, Alain" <Alain_Durand@cable.comcast.com>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Fri, 8 Jun 2007 12:05:27 -0400
> Para: <brian@innovationslab.net>
> CC: <ipv6@ietf.org>
> Conversaci=F3n: Revising Centrally Assigned ULA draft
> Asunto: Re: Revising Centrally Assigned ULA draft
>=20
> I do not have an issue (yet?) with the draft. I have an issue with the process
> to create a draft about a very controversial issue in a wg that is not meeting
> face to face.
>=20
>   - Alain.=20
> =20
>=20
> ----- Original Message -----
> From: Brian Haberman <brian@innovationslab.net>
> To: Durand, Alain
> Cc: Paul Vixie <paul@vix.com>; Ipv <ipv6@ietf.org>
> Sent: Fri Jun 08 11:08:51 2007
> Subject: Re: Revising Centrally Assigned ULA draft
>=20
> All,
>=20
> Durand, Alain wrote:
>> =20
>>=20
>>> -----Original Message-----
>>> From: Paul Vixie [mailto:paul@vix.com]
>>> Sent: Thursday, June 07, 2007 11:57 PM
>>> To: 'Ipv'
>>> Subject: Re: Revising Centrally Assigned ULA draft
>>>>> I say wrap it up and ship it.
>>> if that's what we're doing, then, i say kill it
>>=20
>> This email exchange is the proof that an open discussion is needed.
>> The IETF IPv6 wg doing a contraversial thing on its own without
>> listening to the input from the operational people is not productive,
>> the last thing the community need is yet another power struggle.
>=20
> Before this thread gets any deeper in a rat hole, allow me to point out
> a few things.
>=20
> 1. The discussion of reviving Centrally Assigned ULAs originated in the
> RIR community
>=20
> 2. A new draft of the spec *with significant changes* is being worked on
>=20
> 3. Input for the revised draft is coming from the RIR community
>=20
> Rather than assume the contents of the draft and argue their merits,
> please wait for the posting of the new draft and then comment.
>=20
> Regards,
> Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 14:39:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwjME-0005bS-PY; Fri, 08 Jun 2007 14:38:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwjMC-0005bN-Pl
	for ipv6@ietf.org; Fri, 08 Jun 2007 14:38:44 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwjMB-0004F7-Ep
	for ipv6@ietf.org; Fri, 08 Jun 2007 14:38:44 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HwjOh-000Efe-K0; Fri, 08 Jun 2007 18:41:20 +0000
In-Reply-To: <46693A16.8050103@innovationslab.net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>	<20070607.191659.14348043.he@uninett.no>
	<0b9c01c7a970$364dfb20$a2e9f160$@net>
	<46693A16.8050103@innovationslab.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A367757E-6161-41B0-8E0D-47ACC05C8D38@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Fri, 8 Jun 2007 14:38:31 -0400
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org, alh-ietf@tndh.net
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 8-Jun-2007, at 07:14, Brian Haberman wrote:

> I am thinking that it is easier to fix by deprecating RH0 and then
> defining a new routing header with stricter properties.  Similar to  
> the
> MIPv6 routing header.  That way, the safer RH option can be clearly
> identified in the wild and won't be blocked/restricted/blocked by
> filters meant to protect networks/nodes from the RH0 attacks.

This has the practical side-effect that it is well-aligned with  
operational practice (since several prominent implementations have  
been modified to treat RH0 has an unknown extension header, which is  
effectively the behaviour required by draft-ietf-ipv6-deprecate-rh0).


Joe


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 14:48:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwjVV-0004Km-RT; Fri, 08 Jun 2007 14:48:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwjVV-0004Kf-28
	for ipv6@ietf.org; Fri, 08 Jun 2007 14:48:21 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwjVU-0000Ic-Ir
	for ipv6@ietf.org; Fri, 08 Jun 2007 14:48:21 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HwjY2-000Eio-G7; Fri, 08 Jun 2007 18:51:01 +0000
In-Reply-To: <0bc501c7a9e0$c147dff0$43d79fd0$@net>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>	<094201c7a892$c6f0cd30$54d26790$@net>
	<BDED36E5-58E6-44B9-B6FA-2FDE2B8827D7@ca.afilias.info>
	<09c901c7a922$9bb54980$d31fdc80$@net>
	<05C6DF4D-3ECD-40E1-A449-E65DE7167847@ca.afilias.info>
	<0bc501c7a9e0$c147dff0$43d79fd0$@net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <935A2F6A-E61B-4D32-947D-ECF2162B075F@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Fri, 8 Jun 2007 14:48:10 -0400
To: <alh-ietf@tndh.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 8-Jun-2007, at 11:21, Tony Hain wrote:

> Joe Abley wrote:
>> ...
>> That's a valid editorial point, thanks.
>>
>>> and it is only one
>>> packet at a time that has to wait for reception before being
>>> reflected back.
>>
>> No, that's not the case. Packets constructed with an RH0 extension
>> header containing intermediate addresses A and B, N times (so, for
>> example, if N=5 then RH0 contains ten addresses, A B A B A B A B A B)
>> can be injected into the A-B cyclotron as rapidly as the path between
>> the origin and A allows, without ever waiting for a response.
>
> And as soon as they are at A the packets have to wait for head of line
> blocking to get to B.

Yes. I do not currently see how this prevents the amplification  
effect, however, except in corner cases where the round-trip latency  
between A and B is very low and the B-facing interface at A is of  
very low bandwidth.

>>>>     This technique can also be used as a more general traffic
>>>> amplifier,
>>>>     accumulating attack traffic in-flight between two well- 
>>>> connected
>>>> but
>>>>     mutually-distant waypoints and then finally delivering it
>>>> towards a
>>>>     third party once the RH0-directed oscillations for each packet
>>>> are
>>>>     complete. 7-fold amplification has been postulated using this
>>>>     "capacitive effect" [CanSecWest07].
>>>
>>> The discussion about 3rd party implies this is related to spoofing.
>>
>> No, not at all. The victim address in this case is a destination
>> address, not a source address.
>
> Due to serialization delay the victim will never be the  
> destination. It
> might be the upstream router queue from the destination, but the nice
> mathematical theory about instantaneous convergence falls flat when  
> reality
> strikes in the form of bit serialization.

Seems to me that every denial-of-service attack against a single  
point victim experiences serialisation delay somewhere along the  
line, but that doesn't seem to mean that denial-of-service attacks  
don't deny service.

> Converging packet streams onto an interface queue is much simpler  
> using an
> army of zombies in a ddos attack. Why would anyone waste time  
> trying to game
> a dynamic state where the tuning would have to be precise, and  
> would easily
> be disrupted by 3rd party traffic on the path? Unless someone can  
> provide
> the working code, this does not belong in any document because it  
> is just
> conjecture.

There was code in the CanSecWest slides.

>> Not with widespread RH0 support; that's the point this section
>> attempts to make. With RH0 support a single origin can send packets
>> which will arrive at different anycast nodes, regardless of the
>> natural (no-RH0) node that would normally receive the traffic.
>
> The world should tremble in fear ... a single node can send individual
> packets to more than one destination ?!?!?!?!   This section is  
> still worded
> wrong. Any single packet will always go to a single destination.  
> Use of RH0
> does not result in a single packet arriving at multiple anycast
> destinations.

I agree, and it was not my intention to imply that they could. I will  
see whether I can make that more clear in the text (thanks).

> The entire title of 5.4 is wrong, anycast is not defeated, the  
> packet still
> arrives at one-and-only-one of the anycast instances. Depending on  
> where the
> RH0 target is, that MAY be a different instance that would occur  
> without the
> routing header.

The point of the section is that a single client can arrange for  
packets with a single destination to be routed to different anycast  
nodes at will, not that the same packet could be made to arrive at  
multiple anycast nodes.

>> I have not yet understood your point (or you have not understood
>> mine). I'm not convinced that we have a problem in 5.4, yet.
>
> The existing language effectively says that packets to an anycast  
> dst which
> have an RH0 header will arrive at multiple instances. I know you  
> are trying
> to say that 'the source node gets to select the anycast instance',  
> but that
> is not what this says, and if you said it the way I did it would not
> generate the hysteria needed to get consensus.

I will change the text. I don't agree that the text as-written was  
designed to generate hysteria (and as I wrote it, I should know :-)  
but I agree that the text as it stands is woolly and could do with  
being made more clear.


Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 08 21:48:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwq32-00059k-RH; Fri, 08 Jun 2007 21:47:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwq30-00059B-Mg
	for ipv6@ietf.org; Fri, 08 Jun 2007 21:47:22 -0400
Received: from mrout3.yahoo.com ([216.145.54.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwq2z-0008Nv-C3
	for ipv6@ietf.org; Fri, 08 Jun 2007 21:47:22 -0400
Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com
	[216.145.48.13])
	by mrout3.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l591lB7l095604; 
	Fri, 8 Jun 2007 18:47:11 -0700 (PDT)
Date: Sat, 09 Jun 2007 10:47:10 +0900
Message-ID: <m2wsyddhlt.wl%gnn@neville-neil.com>
From: "George V. Neville-Neil" <gnn@neville-neil.com>
To: Joe Abley <jabley@ca.afilias.info>
In-Reply-To: <A367757E-6161-41B0-8E0D-47ACC05C8D38@ca.afilias.info>
References: <789B685F-3385-490B-9B11-2A78A405346E@ca.afilias.info>
	<D64F9604-8A21-4961-AAB7-1F7C1D93C6A5@ca.afilias.info>
	<094201c7a892$c6f0cd30$54d26790$@net>
	<20070607.191659.14348043.he@uninett.no>
	<0b9c01c7a970$364dfb20$a2e9f160$@net>
	<46693A16.8050103@innovationslab.net>
	<A367757E-6161-41B0-8E0D-47ACC05C8D38@ca.afilias.info>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95
	(i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org, alh-ietf@tndh.net
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-00
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Fri, 8 Jun 2007 14:38:31 -0400,
Joe Abley wrote:
> 
> 
> On 8-Jun-2007, at 07:14, Brian Haberman wrote:
> 
> > I am thinking that it is easier to fix by deprecating RH0 and then
> > defining a new routing header with stricter properties.  Similar to  
> > the
> > MIPv6 routing header.  That way, the safer RH option can be clearly
> > identified in the wild and won't be blocked/restricted/blocked by
> > filters meant to protect networks/nodes from the RH0 attacks.
> 
> This has the practical side-effect that it is well-aligned with  
> operational practice (since several prominent implementations have  
> been modified to treat RH0 has an unknown extension header, which is  
> effectively the behaviour required by draft-ietf-ipv6-deprecate-rh0).

Creating a new "safer" option has been suggested by others several
times already including on this mailing list.  So, let's do one thing
then the next.  If someone wants to suggest a safe version of this
they are welcome to.

Best,
George

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 03:05:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hwuzz-0003JM-Pk; Sat, 09 Jun 2007 03:04:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hwuzy-0003J7-5X
	for ipv6@ietf.org; Sat, 09 Jun 2007 03:04:34 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hwuzx-0001d7-My
	for ipv6@ietf.org; Sat, 09 Jun 2007 03:04:34 -0400
Received: by ug-out-1314.google.com with SMTP id j30so2920361ugc
	for <ipv6@ietf.org>; Sat, 09 Jun 2007 00:04:33 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=drj3xaItUEzpDnur1LszHNBPSTM9p3S26Tsq7wpOi+zeUnGV25+o4wQjSvWb/+od9g4OU4zMbazzl+XnTF7vFssigfT18pNh/bXEVRYAZ757/20AJ46kQ5ioyHB7M/2yrExVXdegGg4yqQalNTGUdsfPs2eaUgqywTU/BUutcX4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=YKbTDOFqJKOW8FrjUBP6kRoMmjXMLBtSEkkCVFGUBX3GN2DWQ0I5vNptM1nKAOy1CUr7oyDG103Ym95MMiXf5UqCqyE5hRz4sbvyTz0EfGLzCT47/0LanHOmOOZwNbRNYnRp73KSIDvWdmiZiefjOajTGtD7VIXAPiMGPJogaak=
Received: by 10.66.248.8 with SMTP id v8mr2541814ugh.1181372673064;
	Sat, 09 Jun 2007 00:04:33 -0700 (PDT)
Received: from ?192.168.1.101? ( [213.103.155.32])
	by mx.google.com with ESMTP id j2sm2340230ugf.2007.06.09.00.04.31
	(version=SSLv3 cipher=RC4-MD5); Sat, 09 Jun 2007 00:04:31 -0700 (PDT)
Message-ID: <466A50FE.9080904@gmail.com>
Date: Sat, 09 Jun 2007 09:04:30 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Bill Manning <bmanning@ISI.EDU>
References: <46685BFC.9090904@innovationslab.net> <466901BC.8040902@gmail.com>
	<20070608151508.GA7432@boreas.isi.edu>
In-Reply-To: <20070608151508.GA7432@boreas.isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: Brian Haberman <brian@innovationslab.net>, Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-08 17:15, Bill Manning wrote:
> presuming this course of action is taken, it raises a much larger
> issue consisting of the IETF creating "property rights" in the 
> address space arena.  

I decline to take the issue of property rights seriously in a
pseudo-random space of 2**40 natural numbers. I *would* recommend
that the robot be hosted by a trusted organization.

> To date, (AFAIK)  most legal arguments have
> taken the line that IP addresses are NOT property, come from a
> common resource that the RIR's administer for the good of the 
> community.   ULA-C  carves out a bit of IP space and in the absence
> of RIR oversight, creates "property"... creating an ambigious
> set of legal issues which will be fought for years.

IMHO it's just not going to happen, in the absence of scarcity.

> 
> I -REALLY- am uncomfortable w/ the IETF, in a mothballed WG,

As others have pointed out, the fact that this WG isn't currently
meeting f2f is irrelevant. Of course, the debate should include
the entire community, which is why this list is open.

> creating this nightmare for the operational community.

Since ULAs aren't routable, I don't see it. If we were talking
about routable PI, it would be a different matter.

    Brian
> 
> --bill
> 
> 
> On Fri, Jun 08, 2007 at 09:14:04AM +0200, Brian E Carpenter wrote:
>> I trust that the new version will include the proposal
>> for a fully robotic solution for creating and escrowing
>> guaranteed-unique ULAs. That's the only missing property in
>> existing ULAs, and we should certainly consider a purely
>> robotic solution with no need for registry action or registry
>> policy of any kind.
>>
>>     Brian
>>
>> On 2007-06-07 21:26, Brian Haberman wrote:
>>> All,
>>>     There has been recent activity in the Registry Community looking at
>>> policies utilizing the Centrally Assigned ULA specification that has
>>> expired.  Several people with ties to both the IETF and the RIRs have
>>> been working with the authors to revise the specification in order to
>>> meet the needs of the policy proposals in the RIRs.
>>>
>>>     Given that the previous work on Centrally Assigned ULAs was adopted
>>> as an IPv6 WG document, the chairs feel that this upcoming revision
>>> should be considered a continuation of that work.
>>>
>>>     The chairs highly encourage people interested in this work to
>>> review and comment on the upcoming revision when it is published.
>>>
>>>     As a note, Bob will be the responsible editor for this document and
>>> Brian will be the shepherding WG chair.
>>>
>>> Regards,
>>> Brian and Bob
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 10:07:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hx1aC-0000AG-Mx; Sat, 09 Jun 2007 10:06:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hx1aA-00008j-W1
	for ipv6@ietf.org; Sat, 09 Jun 2007 10:06:23 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hx1aA-00020P-Ml
	for ipv6@ietf.org; Sat, 09 Jun 2007 10:06:22 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jun 2007 10:06:22 -0400
X-IronPort-AV: i="4.16,402,1175486400"; 
	d="scan'208"; a="62359871:sNHT62930946"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l59E6Mab020398; 
	Sat, 9 Jun 2007 10:06:22 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l59E6HBe029610; 
	Sat, 9 Jun 2007 14:06:21 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 9 Jun 2007 10:06:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 9 Jun 2007 10:06:16 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21043859FA@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <466A50FE.9080904@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AceqZONZRyujbsGZQm2zguRoZbCSHAAOAzDw
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Bill Manning" <bmanning@ISI.EDU>
X-OriginalArrivalTime: 09 Jun 2007 14:06:17.0885 (UTC)
	FILETIME=[59589CD0:01C7AA9F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2426; t=1181397982;
	x=1182261982; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20Revising=20Centrally=20Assigned=20ULA=20draft
	|Sender:=20 |To:=20=22Bill=20Manning=22=20<bmanning@ISI.EDU>;
	bh=GzLdTCKv4jR3NXtUZRpfjhl3JAX6qoT27Iimjfp6A1U=;
	b=Zc8RvDiibQi7B5YBRLVfV1y0OCJeCBwo+IwauVq6Z+1jdDdLIz/NLKwEgvUr1aoepjm5f/FW
	rlRPd1tM+UJnBFTnuDjuoGBKmUIUEinRi9lZco5btkC5NboLUIgw6aQX;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Brian Haberman <brian@innovationslab.net>, Ipv <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

IANA already manages things like enterprise-id numbers. And, then
there's the existing IPv4 address space (how many assigned addresses are
returned or reclaimed?).

While ULA's could potentially be used by a much larger number of
entities, they may also not be used except by larger organizations. Do
you think your average home user or small business would need a ULA?
Would they know to get one? Would they have the knowledge to manage it?

So, I think this "property rights" issue FUD.

Of course, a system like domain name registration where there is a small
annual fee to retain a ULA-C does have merit as it pays for the
registration system and assures that someone has to pay to renew the
assignment. So, if company A buys company B and both have ULA-C's,
company A may decide to let company B's ULA-C expire after a year or two
since there may no longer be a need for it.

- Bernie

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
Sent: Saturday, June 09, 2007 3:05 AM
To: Bill Manning
Cc: Brian Haberman; Ipv
Subject: Re: Revising Centrally Assigned ULA draft

On 2007-06-08 17:15, Bill Manning wrote:
> presuming this course of action is taken, it raises a much larger
> issue consisting of the IETF creating "property rights" in the=20
> address space arena. =20

I decline to take the issue of property rights seriously in a
pseudo-random space of 2**40 natural numbers. I *would* recommend
that the robot be hosted by a trusted organization.

> To date, (AFAIK)  most legal arguments have
> taken the line that IP addresses are NOT property, come from a
> common resource that the RIR's administer for the good of the=20
> community.   ULA-C  carves out a bit of IP space and in the absence
> of RIR oversight, creates "property"... creating an ambigious
> set of legal issues which will be fought for years.

IMHO it's just not going to happen, in the absence of scarcity.

>=20
> I -REALLY- am uncomfortable w/ the IETF, in a mothballed WG,

As others have pointed out, the fact that this WG isn't currently
meeting f2f is irrelevant. Of course, the debate should include
the entire community, which is why this list is open.

> creating this nightmare for the operational community.

Since ULAs aren't routable, I don't see it. If we were talking
about routable PI, it would be a different matter.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 11:43:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hx34Y-0007AB-0o; Sat, 09 Jun 2007 11:41:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hx34W-0007A5-RZ
	for ipv6@ietf.org; Sat, 09 Jun 2007 11:41:48 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hx34V-00070H-J5
	for ipv6@ietf.org; Sat, 09 Jun 2007 11:41:48 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id B703C11426
	for <ipv6@ietf.org>; Sat,  9 Jun 2007 15:41:43 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Ipv <ipv6@ietf.org>
In-Reply-To: Your message of "Sat, 09 Jun 2007 09:04:30 +0200."
	<466A50FE.9080904@gmail.com> 
References: <46685BFC.9090904@innovationslab.net> <466901BC.8040902@gmail.com>
	<20070608151508.GA7432@boreas.isi.edu>
	<466A50FE.9080904@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 09 Jun 2007 15:41:43 +0000
Message-ID: <11206.1181403703@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> ... I *would* recommend that the robot be hosted by a trusted organization.

as ietf, itu, icann, ep.net, and isc have all proved, most organizations are
trusted by most people, but no organization is trusted by everybody.  what
specific trust threshold are you aiming for in the above stated requirement?

> Since ULAs aren't routable, I don't see [a nightmare for the operational
> community].  If we were talking about routable PI, it would be a different
> matter.

in discussions you have evidently not been following, even though they are
occuring on two open mailing lists where this topic is topical, the
operational nightmares are described in detail.  those mailing lists are
arin@ppml.net and perhaps also address-policy-wg@ripe.net.

perhaps this is illustrative as to why holding this discussion in a mothballed
IETF WG is unlikely to reach the audience who would be affected by it.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 11:52:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hx3E0-0001ML-LZ; Sat, 09 Jun 2007 11:51:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hx3E0-0001MG-5q
	for ipv6@ietf.org; Sat, 09 Jun 2007 11:51:36 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hx3Dz-0001Do-U9
	for ipv6@ietf.org; Sat, 09 Jun 2007 11:51:36 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 59EE211426
	for <ipv6@ietf.org>; Sat,  9 Jun 2007 15:51:35 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Ipv <ipv6@ietf.org>
In-Reply-To: Your message of "Sat, 09 Jun 2007 10:06:16 -0400."
	<8E296595B6471A4689555D5D725EBB21043859FA@xmb-rtp-20a.amer.cisco.com> 
References: <8E296595B6471A4689555D5D725EBB21043859FA@xmb-rtp-20a.amer.cisco.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 09 Jun 2007 15:51:35 +0000
Message-ID: <11682.1181404295@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> So, I think this "property rights" issue FUD.

please don't shoot the messenger.  but in most of meatspace, if there's a
thing you pay (either one time or recurring) to get exclusive use of, and it's
of value (if you lost your use of it, it would financially injure you), then
it's property.  the RIR system can work only because it has excellent lawyers.
so, until you have consulted an excellent lawyer, please don't argue about
whether the resource system created by ULA-C would be called property or not.

> Of course, a system like domain name registration where there is a small
> annual fee to retain a ULA-C does have merit as it pays for the registration
> system and assures that someone has to pay to renew the assignment. So, if
> company A buys company B and both have ULA-C's, company A may decide to let
> company B's ULA-C expire after a year or two since there may no longer be a
> need for it.

as icann has discovered, any mandate that an organization be paid a fee by
users for the use of something that's necessary in common every day life is,
in many parts of meatspace, equivilent to creating a "tax authority".  the
rules governing that are quite sensitive and twisty.  as above, please consult
an excellent lawyer before you decide how easy it would be.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 19:46:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxAcL-0001BJ-U2; Sat, 09 Jun 2007 19:45:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxAcK-0001BE-OY
	for ipv6@ietf.org; Sat, 09 Jun 2007 19:45:12 -0400
Received: from smtp1.mail.adnap.net.au ([203.6.132.75])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxAcI-0006cf-MY
	for ipv6@ietf.org; Sat, 09 Jun 2007 19:45:12 -0400
Received: from 219-90-232-65.ip.adam.com.au ([219.90.232.65]
	helo=mail.nosense.org)
	by smtp1.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1HxAcB-000DRI-Q5; Sun, 10 Jun 2007 09:15:03 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id AE87B20132;
	Sun, 10 Jun 2007 09:15:00 +0930 (CST)
Date: Sun, 10 Jun 2007 09:15:00 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Bernie Volz \(volz\)" <volz@cisco.com>
Message-Id: <20070610091500.2786ba68.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <8E296595B6471A4689555D5D725EBB21043859FA@xmb-rtp-20a.amer.cisco.com>
References: <466A50FE.9080904@gmail.com>
	<8E296595B6471A4689555D5D725EBB21043859FA@xmb-rtp-20a.amer.cisco.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Sat, 9 Jun 2007 10:06:16 -0400
"Bernie Volz \(volz\)" <volz@cisco.com> wrote:

> IANA already manages things like enterprise-id numbers. And, then
> there's the existing IPv4 address space (how many assigned addresses are
> returned or reclaimed?).
> 
> While ULA's could potentially be used by a much larger number of
> entities, they may also not be used except by larger organizations. Do
> you think your average home user or small business would need a ULA?
> Would they know to get one? Would they have the knowledge to manage it?
> 

Any residential user who needs to have non-globally accessible devices
attached to their home network could use them. Think a networked
printer. Or DVD player, or clothes iron, washing machine, TV etc. As I
think it'd be likely that most residential users would have devices
that they don't want "on the Internet", I think ULA addessing domains
are likely to going to be present in every household.

As for getting a ULA, that's a user interface problem, and I think
that's mostly independent of the addressing space or how to generate
the ULA unique value. A simple enough solution might be that the first
time an Internet home gateway is powered up it generates the ULA, then
starts announcing it as a prefix in RAs. This sort of problem has been
solved before on a number of occasions - IPX, Appletalk or zeroconf
could provide example methods.

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 09 20:01:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxAqj-0006Gf-Sc; Sat, 09 Jun 2007 20:00:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxAqi-0006GZ-O8
	for ipv6@ietf.org; Sat, 09 Jun 2007 20:00:04 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxAqi-0003No-Ak
	for ipv6@ietf.org; Sat, 09 Jun 2007 20:00:04 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id C4E5C2844F
	for <ipv6@ietf.org>; Sun, 10 Jun 2007 00:00:03 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 10 Jun 2007 00:00:03 +0000
Message-Id: <20070610000003.C4E5C2844F@cyteen.hactrn.net>
X-Spam-Score: -0.9 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.50% |    7 | 20.17% |    68845 | alh-ietf@tndh.net
 14.29% |    8 | 16.05% |    54788 | vishwas.ietf@gmail.com
 10.71% |    6 | 11.04% |    37680 | jabley@ca.afilias.info
  7.14% |    4 |  5.65% |    19283 | arnaud.ebalard@eads.net
  7.14% |    4 |  4.89% |    16695 | paul@vix.com
  5.36% |    3 |  4.52% |    15425 | alain_durand@cable.comcast.com
  5.36% |    3 |  3.73% |    12715 | gnn@neville-neil.com
  5.36% |    3 |  3.71% |    12667 | brian@innovationslab.net
  3.57% |    2 |  3.88% |    13251 | brian.e.carpenter@gmail.com
  3.57% |    2 |  3.16% |    10799 | pekkas@netcore.fi
  3.57% |    2 |  3.07% |    10475 | gih@apnic.net
  1.79% |    1 |  2.27% |     7748 | jordi.palet@consulintel.es
  1.79% |    1 |  2.10% |     7183 | volz@cisco.com
  1.79% |    1 |  2.01% |     6869 | internet-drafts@ietf.org
  1.79% |    1 |  1.82% |     6225 | jeroen@unfix.org
  1.79% |    1 |  1.82% |     6195 | bmanning@isi.edu
  1.79% |    1 |  1.81% |     6166 | fred.l.templin@boeing.com
  1.79% |    1 |  1.56% |     5316 | suresh.krishnan@ericsson.com
  1.79% |    1 |  1.50% |     5103 | christopher.morrow@gmail.com
  1.79% |    1 |  1.49% |     5074 | ipng@69706e6720323030352d30312d31340a.nosense.org
  1.79% |    1 |  1.29% |     4412 | bob.hinden@nokia.com
  1.79% |    1 |  1.22% |     4174 | he@uninett.no
  1.79% |    1 |  1.22% |     4173 | jinmei@wide.ad.jp
--------+------+--------+----------+------------------------
100.00% |   56 |100.00% |   341261 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 04:42:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxfS5-0001Bd-PS; Mon, 11 Jun 2007 04:40:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxfS2-0001BJ-0q
	for ipv6@ietf.org; Mon, 11 Jun 2007 04:40:39 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxfS0-0002Bw-Fe
	for ipv6@ietf.org; Mon, 11 Jun 2007 04:40:37 -0400
Received: by ug-out-1314.google.com with SMTP id j30so21951ugc
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 01:40:35 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=E2i5CuhvuItuLqLrsS0fKKKXCv1NxgyHxIQktKVhL2k/BQf9l9m8aapi/YuIxD2HE+Nxs1VDFmIHEihEyi/HvHT7/8lchFPzH3xaud37xTpfsuYpVyX0g1kFVNeOD09rJGNH/x+SYAHlQ7rrbv/CPjaeWajcNMzZEPcQcOExCDE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=OviDEKg04cnK6J9NY1vfpzdncx6aLJWRPh8vUWzGvBCA3g9Co43VvMU1FQH0/3mXu1FfQ15JAUhDOJnPNiE9Qh/a/a32WIG15GmoO8jlE9Lbd2B8WetFWOJHp6RI/ZU3J/PyJRP+2oXdpPTFNnkL1v7qReu9M+1Kn6xmkCAz5pk=
Received: by 10.82.160.2 with SMTP id i2mr10346549bue.1181551235222;
	Mon, 11 Jun 2007 01:40:35 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id y37sm13296042iky.2007.06.11.01.40.33
	(version=SSLv3 cipher=RC4-MD5); Mon, 11 Jun 2007 01:40:34 -0700 (PDT)
Message-ID: <466D0A80.40406@gmail.com>
Date: Mon, 11 Jun 2007 10:40:32 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <46685BFC.9090904@innovationslab.net>
	<466901BC.8040902@gmail.com>	<20070608151508.GA7432@boreas.isi.edu>	<466A50FE.9080904@gmail.com>
	<11206.1181403703@sa.vix.com>
In-Reply-To: <11206.1181403703@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 2007-06-09 17:41, Paul Vixie wrote:
>> ... I *would* recommend that the robot be hosted by a trusted organization.
> 
> as ietf, itu, icann, ep.net, and isc have all proved, most organizations are
> trusted by most people, but no organization is trusted by everybody.  what
> specific trust threshold are you aiming for in the above stated requirement?

Since you ask:
IANA, under the IAB's authority and RFC 2860 clause 4.3 exception (b),
i.e. just like any other technical registries run by IANA.

That MoU allows the IETF to pull the plug if it ever needs to.

    Brian

> 
>> Since ULAs aren't routable, I don't see [a nightmare for the operational
>> community].  If we were talking about routable PI, it would be a different
>> matter.
> 
> in discussions you have evidently not been following, even though they are
> occuring on two open mailing lists where this topic is topical, the
> operational nightmares are described in detail.  those mailing lists are
> arin@ppml.net and perhaps also address-policy-wg@ripe.net.
> 
> perhaps this is illustrative as to why holding this discussion in a mothballed
> IETF WG is unlikely to reach the audience who would be affected by it.
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 09:15:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxjim-000136-Oj; Mon, 11 Jun 2007 09:14:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxjil-0000vN-7A
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:14:11 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxjij-00042x-QJ
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:14:11 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 11 Jun 2007 15:14:07 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5BDE6W5029026; 
	Mon, 11 Jun 2007 15:14:06 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5BDE1Dd010718; 
	Mon, 11 Jun 2007 13:14:06 GMT
Received: from xmb-ams-33c.emea.cisco.com ([144.254.231.91]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Jun 2007 15:14:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 11 Jun 2007 15:14:04 +0200
Message-ID: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
In-Reply-To: <20070610091500.2786ba68.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: Aceq8FnHwYSuGObBRrGGdYZK2rLYSABOKLyA
From: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>
To: "Mark Smith" <ipng@69706e6720323030352d30312d31340a.nosense.org>,
	"Bernie Volz \(volz\)" <volz@cisco.com>
X-OriginalArrivalTime: 11 Jun 2007 13:14:06.0239 (UTC)
	FILETIME=[6390DAF0:01C7AC2A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2197; t=1181567646;
	x=1182431646; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gvandeve@cisco.com;
	z=From:=20=22Gunter=20Van=20de=20Velde=20\(gvandeve\)=22=20<gvandeve@cisco
	.com>
	|Subject:=20RE=3A=20Revising=20Centrally=20Assigned=20ULA=20draft
	|Sender:=20; bh=qIxpW8h+IyMjU4Vjj16zphLRuemjHtT1ghVswgeoJQE=;
	b=IUmR1udYswFlsn9FhHE6o5/KGl4NdrPpjW33J0F83nyQbIs8/mfxZiYSkYmQQT07mzXFCOqA
	Oz+wU0jKpdqIjzpHS88r7GvDqg5yxHOBSfDNsstJDKh32PaUgh8S6are;
Authentication-Results: ams-dkim-2; header.From=gvandeve@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: ipv6@ietf.org
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


I suppose most of these users will have big (actually a quite small)
flat infrastructure
to keep it simple? Hence what limits them to use just LL? Why ULA? What=20
would be the residential users benefit? Do you think that residential=20
users will have small routed networks in the future?

G/

-----Original Message-----
From: Mark Smith
[mailto:ipng@69706e6720323030352d30312d31340a.nosense.org]=20
Sent: Sunday, June 10, 2007 1:45 AM
To: Bernie Volz (volz)
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft

On Sat, 9 Jun 2007 10:06:16 -0400
"Bernie Volz \(volz\)" <volz@cisco.com> wrote:

> IANA already manages things like enterprise-id numbers. And, then=20
> there's the existing IPv4 address space (how many assigned addresses=20
> are returned or reclaimed?).
>=20
> While ULA's could potentially be used by a much larger number of=20
> entities, they may also not be used except by larger organizations. Do

> you think your average home user or small business would need a ULA?
> Would they know to get one? Would they have the knowledge to manage
it?
>=20

Any residential user who needs to have non-globally accessible devices
attached to their home network could use them. Think a networked
printer. Or DVD player, or clothes iron, washing machine, TV etc. As I
think it'd be likely that most residential users would have devices that
they don't want "on the Internet", I think ULA addessing domains are
likely to going to be present in every household.

As for getting a ULA, that's a user interface problem, and I think
that's mostly independent of the addressing space or how to generate the
ULA unique value. A simple enough solution might be that the first time
an Internet home gateway is powered up it generates the ULA, then starts
announcing it as a prefix in RAs. This sort of problem has been solved
before on a number of occasions - IPX, Appletalk or zeroconf could
provide example methods.

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 09:32:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxjzs-0002av-Ki; Mon, 11 Jun 2007 09:31:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxjzq-0002U5-R8
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:31:51 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxjzp-0000qp-8v
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:31:50 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 16472140C33C;
	Mon, 11 Jun 2007 15:31:46 +0200 (CEST)
Message-ID: <466D4EC5.3060500@spaghetti.zurich.ibm.com>
Date: Mon, 11 Jun 2007 14:31:49 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
In-Reply-To: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1603791088=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1603791088==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9571D33A0D70E6167D57CBD5"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9571D33A0D70E6167D57CBD5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Mark Smith wrote:

> Any residential user who needs to have non-globally accessible devices
> attached to their home network could use them.[..]

the "normal" ULA (RFC4193) provides this already. The "user interface"
is simply the box that auto generates it and then applies it. Presto.
This thus already is possible today, with todays RFC's (RFC4193).


ULA-C is a completely different beast that is best solved by simply
having organizations to the RIR's and getting a nice /48 or similar
address space they can justify. They call that "PI" which is a dirty
word, but serves the purpose completely.


The only benefit which has been named upto now is that firewalling is
simpler if you know that non fd00::/8 space is The Evil Internet.
But why should you trust address space in any way?!

Greets,
 Jeroen



--------------enig9571D33A0D70E6167D57CBD5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZtTsUuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I/Y/AKCFZdWYlBSj0re+7F1v9y0o0hPf
IQCgj4G5WRv6wVSvBKb9YtjAa4NeYaM=
=mxzR
-----END PGP SIGNATURE-----

--------------enig9571D33A0D70E6167D57CBD5--


--===============1603791088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1603791088==--




From ipv6-bounces@ietf.org Mon Jun 11 09:52:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxkJD-0000wQ-TJ; Mon, 11 Jun 2007 09:51:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxkJC-0000oU-8o
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:51:50 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxkJC-0006Vk-0d
	for ipv6@ietf.org; Mon, 11 Jun 2007 09:51:50 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 97CE611425
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 13:51:49 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Ipv <ipv6@ietf.org>
In-Reply-To: Your message of "Mon, 11 Jun 2007 10:40:32 +0200."
	<466D0A80.40406@gmail.com> 
References: <46685BFC.9090904@innovationslab.net> <466901BC.8040902@gmail.com>
	<20070608151508.GA7432@boreas.isi.edu>
	<466A50FE.9080904@gmail.com> <11206.1181403703@sa.vix.com>
	<466D0A80.40406@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 11 Jun 2007 13:51:49 +0000
Message-ID: <84761.1181569909@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> >> ... I *would* recommend that the robot be hosted by a trusted
> >> organization.

> > ... most organizations are trusted by most people, but no organization is
> > trusted by everybody.  what specific trust threshold are you aiming for in
> > the above stated requirement?
> 
> IANA, under the IAB's authority and RFC 2860 clause 4.3 exception (b),
> i.e. just like any other technical registries run by IANA.

can you clarify further?  do you mean "hosted by IANA" or "trusted by IANA" ?

(noting that i trust IANA just fine, but that this point isn't academic.)

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 10:22:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxkmA-0004mf-8e; Mon, 11 Jun 2007 10:21:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxkm8-0004ma-Fn
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:21:44 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxkm8-0003at-70
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:21:44 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 8189E11425
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 14:21:43 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Mon, 11 Jun 2007 15:14:04 +0200."
	<70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com> 
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 11 Jun 2007 14:21:43 +0000
Message-ID: <94420.1181571703@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I suppose most of these users will have big (actually a quite small) flat
> infrastructure to keep it simple? Hence what limits them to use just LL?
> Why ULA?  What would be the residential users benefit?  Do you think that
> residential users will have small routed networks in the future?

i think that the distinction between "provider" and "consumer" will blur in
the following ways.

first, if everybody in the neighborhood has overlapping wireless clouds, so
that neighbor-sets {A B} {B C} {C D} can join clouds owned by neighbors A,
B, and C respectively, that D's preferred path to A will in some cases be
through C and B rather than through their "providers".  this is not just
because their providers might not have as much in-neighborhood capacity due
to backhauling and provider multiplicity, but because this is the topology
many human communities prefer.  consider the legal implications for file
sharing when there is vs. isn't a "provider" which is regulated and subject
to CALEA, as a low hanging example.

second, with COMMONS and things like it sprouting up, there will be networks
built using city-owned infrastructure where virtually all traffic into/outof
that city has a city-owned last mile.  the need for a "provider" will only be
truly notable for traffic into/outof that city, and it will be impractical
for economic reasons ("anti-lockin") to use "provider assigned" addressing.
the city would have to become an LIR in today's model.  ULA and ULA-C could
change all of that, in a bad way, by either requiring a city to run a giant
NAT-PT box and breaking end-to-end on intercity traffic, or by requiring the
"provider" to do so, or by requiring the "provider" to import ULA routes.

to your last question, i do think that residential users will have small
routed networks in the future, rather than a flat neighborhood-wide or even
city-wide L2, simply because the broadcast domain for things like Bonjour 
will be too large otherwise, and the market seems to have embraced "routers"
as their preferred security perimeter (vs hosts, bridges, or repeaters.)

(these are the wages of our sins from not separating routing from identity,
and from assuming that the economic principles underlaying IPv4 routing
would still apply in an IPv6 world.)

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 10:24:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxko8-0005Ea-6A; Mon, 11 Jun 2007 10:23:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxko6-0005EP-Uh
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:23:46 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxko5-0003xC-Lp
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:23:46 -0400
Received: by ug-out-1314.google.com with SMTP id j30so139191ugc
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 07:23:45 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=AOeXO0EAZjlh5mTHD9xi4VtAe5vB00Xr+8ihqGanKg8WNPFmr9KOh8PB7FLX6m6g4R49ZQlFXauOee3S10jRTa8KGO/ObOgEj7KZXATKgfizGi5m3DPrSZiN/E84c5qa0fZBfb2TfNwNRB9mboDyDpCF2ogTEXfzXSNPooJLTZQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=LjTkQNb2dMNc8jLgQT8Hgli9k1/nYg+vrdipYtAQ5DBnuZfi9s6MpAnd+v+GhOlhW5J4D9X2yyNbfagVEKne7TWsS0xqvql3Dx7ELZoysV2hWLZt/H31omI0eKoXImC+gtdMf4p+BBJbRwj38hWKH1dydktlfokJtViPcp8BwXs=
Received: by 10.67.10.18 with SMTP id n18mr5150154ugi.1181571824994;
	Mon, 11 Jun 2007 07:23:44 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id k30sm9664605ugc.2007.06.11.07.23.43
	(version=SSLv3 cipher=RC4-MD5); Mon, 11 Jun 2007 07:23:44 -0700 (PDT)
Message-ID: <466D5AE9.3020100@gmail.com>
Date: Mon, 11 Jun 2007 16:23:37 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <46685BFC.9090904@innovationslab.net>
	<466901BC.8040902@gmail.com>	<20070608151508.GA7432@boreas.isi.edu>	<466A50FE.9080904@gmail.com>
	<11206.1181403703@sa.vix.com>	<466D0A80.40406@gmail.com>
	<84761.1181569909@sa.vix.com>
In-Reply-To: <84761.1181569909@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-11 15:51, Paul Vixie wrote:
>>>> ... I *would* recommend that the robot be hosted by a trusted
>>>> organization.
> 
>>> ... most organizations are trusted by most people, but no organization is
>>> trusted by everybody.  what specific trust threshold are you aiming for in
>>> the above stated requirement?
>> IANA, under the IAB's authority and RFC 2860 clause 4.3 exception (b),
>> i.e. just like any other technical registries run by IANA.
> 
> can you clarify further?  do you mean "hosted by IANA" or "trusted by IANA" ?
> 
> (noting that i trust IANA just fine, but that this point isn't academic.)

Yes, good question. My gut feeling is "hosted by". I'm not sure I can
argue rationally for that.

BTW do the ops lists where this is discussed have archives?

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 10:33:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxkwV-0005vr-4N; Mon, 11 Jun 2007 10:32:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxkwT-0005vf-6p
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:32:25 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxkwR-0005zg-QU
	for ipv6@ietf.org; Mon, 11 Jun 2007 10:32:25 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5BEVqD6023694
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 11 Jun 2007 07:31:52 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5BEVpiN023693;
	Mon, 11 Jun 2007 07:31:51 -0700 (PDT)
Date: Mon, 11 Jun 2007 07:31:51 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20070611143151.GA22817@boreas.isi.edu>
References: <46685BFC.9090904@innovationslab.net> <466901BC.8040902@gmail.com>
	<20070608151508.GA7432@boreas.isi.edu>
	<466A50FE.9080904@gmail.com> <11206.1181403703@sa.vix.com>
	<466D0A80.40406@gmail.com> <84761.1181569909@sa.vix.com>
	<466D5AE9.3020100@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <466D5AE9.3020100@gmail.com>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: Ipv <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> 
> BTW do the ops lists where this is discussed have archives?
> 
>     Brian
> 

	for ARIN's ppml list:   http://www.arin.net/mailing_lists/index.html
	and follow the link for "archives"


--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 11:29:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxloY-0003K1-72; Mon, 11 Jun 2007 11:28:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HxloW-0003Jr-F8
	for ipv6@ietf.org; Mon, 11 Jun 2007 11:28:16 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HxloT-0003XH-W9
	for ipv6@ietf.org; Mon, 11 Jun 2007 11:28:16 -0400
Received: by ug-out-1314.google.com with SMTP id j30so182126ugc
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 08:28:11 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=JOvufaKAKCPG6ewmCzexCk7xp2bltCRUm6ef3klzX9T2ssbsvUgmT6kF8nC2lqFuWnDoQirOegsNN32ifzjFdx33BjZ8HnqUU1FImwriYmnmm/no89AmpmbeVBZtcCHbhMclxxneG8LnRwXLtwhjuMGeH4mC7LvEig36Aj+OTGA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ejHLv5rM8Blc68D7/0ThmyXMcMjIo2xMLrpiLzWYmKNxLBQmWQxvi9++rzg17aOm/jpF6phyAM/5kq0JTB81W+lW7FVeCvDfTKzF8KYFjAflDK1nO6sAUee2Vj2KxgsDwib/oCoOLkNLqsZUr16aw31tL2uepoMBfS2Jl9nHWlg=
Received: by 10.82.175.17 with SMTP id x17mr11117978bue.1181575691000;
	Mon, 11 Jun 2007 08:28:11 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id h6sm1030502nfh.2007.06.11.08.28.09
	(version=SSLv3 cipher=RC4-MD5); Mon, 11 Jun 2007 08:28:09 -0700 (PDT)
Message-ID: <466D6A07.8050509@gmail.com>
Date: Mon, 11 Jun 2007 17:28:07 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
In-Reply-To: <94420.1181571703@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

It seems that what you describe is a prime candidate
for metro addressing, not for ULAs of any kind. And a metro
prefix is not really any different from a PA prefix, except
that it's assigned to a municipality.

ULAs should be kept in-house, literally.

     Brian

On 2007-06-11 16:21, Paul Vixie wrote:
>> I suppose most of these users will have big (actually a quite small) flat
>> infrastructure to keep it simple? Hence what limits them to use just LL?
>> Why ULA?  What would be the residential users benefit?  Do you think that
>> residential users will have small routed networks in the future?
> 
> i think that the distinction between "provider" and "consumer" will blur in
> the following ways.
> 
> first, if everybody in the neighborhood has overlapping wireless clouds, so
> that neighbor-sets {A B} {B C} {C D} can join clouds owned by neighbors A,
> B, and C respectively, that D's preferred path to A will in some cases be
> through C and B rather than through their "providers".  this is not just
> because their providers might not have as much in-neighborhood capacity due
> to backhauling and provider multiplicity, but because this is the topology
> many human communities prefer.  consider the legal implications for file
> sharing when there is vs. isn't a "provider" which is regulated and subject
> to CALEA, as a low hanging example.
> 
> second, with COMMONS and things like it sprouting up, there will be networks
> built using city-owned infrastructure where virtually all traffic into/outof
> that city has a city-owned last mile.  the need for a "provider" will only be
> truly notable for traffic into/outof that city, and it will be impractical
> for economic reasons ("anti-lockin") to use "provider assigned" addressing.
> the city would have to become an LIR in today's model.  ULA and ULA-C could
> change all of that, in a bad way, by either requiring a city to run a giant
> NAT-PT box and breaking end-to-end on intercity traffic, or by requiring the
> "provider" to do so, or by requiring the "provider" to import ULA routes.
> 
> to your last question, i do think that residential users will have small
> routed networks in the future, rather than a flat neighborhood-wide or even
> city-wide L2, simply because the broadcast domain for things like Bonjour 
> will be too large otherwise, and the market seems to have embraced "routers"
> as their preferred security perimeter (vs hosts, bridges, or repeaters.)
> 
> (these are the wages of our sins from not separating routing from identity,
> and from assuming that the economic principles underlaying IPv4 routing
> would still apply in an IPv6 world.)
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 13:46:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxnxu-0006YM-W5; Mon, 11 Jun 2007 13:46:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxnxu-0006YF-0f
	for ipv6@ietf.org; Mon, 11 Jun 2007 13:46:06 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxnxt-0008Bp-O3
	for ipv6@ietf.org; Mon, 11 Jun 2007 13:46:05 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out4.apple.com (Postfix) with ESMTP id 3DE428B2A16
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 10:46:05 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 2CC0130076
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 10:46:05 -0700 (PDT)
X-AuditID: 11807125-a1f68bb000000801-ee-466d8a5d5507
Received: from [17.206.23.245] (il0602a-dhcp117.apple.com [17.206.23.245])
	by relay7.apple.com (Apple SCV relay) with ESMTP id 1A59F30006
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 10:46:05 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <94420.1181571703@sa.vix.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 11 Jun 2007 10:45:57 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 11, 2007, at 07:21, Paul Vixie wrote:
>
> to your last question, i do think that residential users will have  
> small
> routed networks in the future, rather than a flat neighborhood-wide  
> or even
> city-wide L2, simply because the broadcast domain for things like  
> Bonjour
> will be too large otherwise, and the market seems to have embraced  
> "routers"
> as their preferred security perimeter (vs hosts, bridges, or  
> repeaters.)

I'd like to note for the record that Bonjour is more than just DNS-SD  
over multicast.  It works quite well over unicast with infrastructure  
content servers by using a few simple extensions to the core  
protocols, e.g. for handling long-lived queries, etc.

In the unlikely event that metro-L2 came to be feasible for other  
reasons, there wouldn't be that much of a problem fitting Bonjour  
into that environment.  While Bonjour was developed for zero- 
configuration networking, it's still perfectly reasonable to use it  
where in managed networks.

> (these are the wages of our sins from not separating routing from  
> identity,
> and from assuming that the economic principles underlaying IPv4  
> routing
> would still apply in an IPv6 world.)

Here here.  This argument seems awfully compelling to me.  Given the  
near ubiquity of IEEE 802.1 for local-area networking in residential  
and small office environments, it's really hard for me to see how  
there is a need for residential users to have routed networks when / 
64 prefixes are almost too cheap to meter (and will continue to be  
until kakistocracy emerges as the dominant form of Internet governance).

I don't see why residential users should even need ULA, much  
centrally assigned ULA.  Is there a thread on one of those ops list  
someone could refer me to read from the archives so I can come up to  
speed on the reasons the operations community thinks otherwise?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 11 17:02:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxr1W-00037x-Ml; Mon, 11 Jun 2007 17:02:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hxr1U-00037r-Sb
	for ipv6@ietf.org; Mon, 11 Jun 2007 17:02:00 -0400
Received: from smtp.mitel.com ([216.191.234.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hxr1T-0002I4-Ma
	for ipv6@ietf.org; Mon, 11 Jun 2007 17:02:00 -0400
Received: from localhost (smtp.mitel.com [127.0.0.1])
	by smtp.mitel.com (Postfix) with ESMTP id 4F8742003B
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 17:01:59 -0400 (EDT)
Received: from smtp.mitel.com ([127.0.0.1])
	by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 01187-02-5 for <ipv6@ietf.org>;
	Mon, 11 Jun 2007 17:01:56 -0400 (EDT)
Received: from kanmta01.mitel.com (kanmta01 [134.199.37.58])
	by smtp.mitel.com (Postfix) with ESMTP id 4A08420052
	for <ipv6@ietf.org>; Mon, 11 Jun 2007 17:01:54 -0400 (EDT)
From: Christopher_Taylor@Mitel.COM
To: ipv6@ietf.org
Message-ID: <OFFDDC8D0F.5A00FA90-ON802572F7.0073870E-802572F7.0073870E@mitel.com>
Date: Mon, 11 Jun 2007 22:01:52 +0100
X-MIMETrack: Serialize by Router on kanmta01/Mitel(Release 5.0.12 |February 13,
	2003) at 06/11/2007 05:01:51 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: Christopher Taylor/Cal/Mitel is on annual leave
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


I will be out of the office starting  11/06/2007 and will not return until
26/06/2007.

I will not be able to check my email during this time. I will respond to
your message when I return.



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 03:00:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy0Mj-0008St-Uk; Tue, 12 Jun 2007 03:00:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy0Mi-0008Sl-UI
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:00:32 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy0Mh-00053F-Le
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:00:32 -0400
Received: by ug-out-1314.google.com with SMTP id j30so249176ugc
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 00:00:31 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=edmdXVYwZZF6PqNBN00Polpyi9uK3vt1VXYdCQT5/EXmNYt6hQUA1/HRbihcoL1eGQy8wjgI2ipAPqtITOZK8hph0FI7GNCYSHPmv921sBo1WaBvBXFZDpp+ME2oUxm6S7Tc5ZIL/rY9fJgSF55RE9zxxoIf6beQ5QUCnRRcuMg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=fucCRmW2e9w57rdbHbrgDhLbOZwcsZTPPV/0GofdCsN9gr7zvV77vgojuufa+9hKDTEzZsZowSGZGdPdEkOWp2ioqEyNkC/jQFh/urYxH7h795lF7X02HAo9yRCNkMn83s5OrMd47vLrOgSBJ+rDOVyIPcb+I76vJiXnPGKSv9I=
Received: by 10.82.112.3 with SMTP id k3mr12606173buc.1181631630623;
	Tue, 12 Jun 2007 00:00:30 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id d23sm2849703nfh.2007.06.12.00.00.29
	(version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 00:00:29 -0700 (PDT)
Message-ID: <466E448B.5050101@gmail.com>
Date: Tue, 12 Jun 2007 09:00:27 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
In-Reply-To: <15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-11 19:45, james woodyatt wrote:
...
> I don't see why residential users should even need ULA, much centrally 
> assigned ULA.  

Assuming you mean "the vast majority of residential users" I agree. But there
will always be exceptions, and there will be a soft boundary between small
offices that have no use for ULAs, and larger ones that maybe do.

Not that it really matters, since ULAs never appear off-site anyway.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 03:27:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy0mX-0006Kx-V6; Tue, 12 Jun 2007 03:27:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy0mW-0006Kl-9T
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:27:12 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy0mT-00043M-B5
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:27:12 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id E96C611425
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 07:27:08 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 09:00:27 +0200."
	<466E448B.5050101@gmail.com> 
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 12 Jun 2007 07:27:08 +0000
Message-ID: <99263.1181633228@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Not that it really matters, since ULAs never appear off-site anyway.

depending on what you mean by a site, both in relative and absolute terms
of space and of time, there might be general agreement on this point, or not.

hopefully the regress isn't infinite.  care to take it a step and see?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 03:45:29 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy13x-0003Sb-C6; Tue, 12 Jun 2007 03:45:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy13v-0003SS-RZ
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:45:11 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy13t-0001ae-Ca
	for ipv6@ietf.org; Tue, 12 Jun 2007 03:45:11 -0400
Received: by ug-out-1314.google.com with SMTP id j30so260462ugc
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 00:45:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=VZBTp7iGIM9JbjzND1ImmoMPRfVgK/3uw9bUTMIShFRcbaPdWycBPerFTaZMCy4NPyto5Us3V1uBojOsJRq5YXz70MElU7ffB2NVCYXHr2+U9v1l6+9zeZAr4DZ7/Lf/Wt8qc9KdLVWTS4IeAgn6TlFoVZYW3aoEvTH/0z5B5Js=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=CgCgCYbc+YNO/gEsX+vTfex/h48k+e23MMEHENmk/EpvE7lH/w+0BmAlir+LOX+/Yg47bvzm/iA1Eml+dHj7KrfRv/H5tQ7hjehZLAxDHPFfaUNKQhD0bkhoRmwPGakFrxJj1zHs+DIJ1pUmqnaZkpJ6nzSBV2L7Mvh9bBLYGpE=
Received: by 10.66.249.16 with SMTP id w16mr332249ugh.1181634308391;
	Tue, 12 Jun 2007 00:45:08 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id l22sm271141uga.2007.06.12.00.45.07
	(version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 00:45:07 -0700 (PDT)
Message-ID: <466E4F01.4000505@gmail.com>
Date: Tue, 12 Jun 2007 09:45:05 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>	<94420.1181571703@sa.vix.com>	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>	<466E448B.5050101@gmail.com>
	<99263.1181633228@sa.vix.com>
In-Reply-To: <99263.1181633228@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-12 09:27, Paul Vixie wrote:
>> Not that it really matters, since ULAs never appear off-site anyway.
> 
> depending on what you mean by a site, both in relative and absolute terms
> of space and of time, there might be general agreement on this point, or not.
> 
> hopefully the regress isn't infinite.  care to take it a step and see?

The regression is easy: the site for a given ULA is the routing domain
within which that ULA is not filtered.

That is not intended to be frivolous. If two enterprise networks agree
to recognize each other's ULA, the ULAs can be routed over a link (or VPN)
between those two networks. But both enterprises' ISPs will filter ULAs.

I'm not making this up. Something very like it is current practice on
IPv4; it's just less well defined since we don't have ULA space.

     Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 04:06:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy1OI-0002XS-Vx; Tue, 12 Jun 2007 04:06:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1OI-0002XK-2d
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:06:14 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy1OH-00014F-7l
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:06:14 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1Hy1OC-000Fhw-0V; Tue, 12 Jun 2007 17:36:08 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 41FB720132;
	Tue, 12 Jun 2007 17:36:06 +0930 (CST)
Date: Tue, 12 Jun 2007 17:36:05 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com>
Message-Id: <20070612173605.711ecd17.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
References: <20070610091500.2786ba68.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: ipv6@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 11 Jun 2007 15:14:04 +0200
"Gunter Van de Velde \(gvandeve\)" <gvandeve@cisco.com> wrote:

> 
> I suppose most of these users will have big (actually a quite small)
> flat infrastructure
> to keep it simple? Hence what limits them to use just LL? Why ULA? What 
> would be the residential users benefit? Do you think that residential 
> users will have small routed networks in the future?
> 

I think it would be wise not to preclude the possibility. 

One thing I'm trying to keep remembering is that while it is easier to
understand IPv6 by thinking of it as "IPv4 with bigger addresses", I
think it is important to remember it is more than that. Inherent
functional constraints in IPv4, mainly due to it's limited addressing,
don't or don't have to exist in IPv6. Two examples of things that I
don't think can be done with IPv4 and probably weren't thought of being
done with IPv6 when the IPv6 addressing size was decided are HIP and
ULA addressing. Next year, or 5 or 10 years time we may have more
things to add to that list.

So, I think it's useful to certainly use IPv4 and it's common
deployment scenarios as a basis for how people will probably use IPv6,
however I think it is also important not to be trapped by it. I think
IPv6 can open up possiblities of solving "IPv4" solved problems in
different or better ways.

People might have routed ULA networks in their home. Maybe a scenario
could be when they come home from work and their Personal Area Network
with a ULA prefix, which covers their mobile phone, music player and
pedometer in their shoes, connects to their wireless home network with
a different ULA. Possibly their mobile phone in this scenario will act
as a Wifi to Bluetooth router between the separate ULA prefixes 

(I think some of the latest high end mobile phones could probably, with
a small software upgrade, act in that capacity today 1- from what I
understand of their capabilities (3G, Wifi, bluetooth), I'd think the
only thing probably missing is the IPv6 routing capability)

Regards,
Mark.

> G/
> 
> -----Original Message-----
> From: Mark Smith
> [mailto:ipng@69706e6720323030352d30312d31340a.nosense.org] 
> Sent: Sunday, June 10, 2007 1:45 AM
> To: Bernie Volz (volz)
> Cc: ipv6@ietf.org
> Subject: Re: Revising Centrally Assigned ULA draft
> 
> On Sat, 9 Jun 2007 10:06:16 -0400
> "Bernie Volz \(volz\)" <volz@cisco.com> wrote:
> 
> > IANA already manages things like enterprise-id numbers. And, then 
> > there's the existing IPv4 address space (how many assigned addresses 
> > are returned or reclaimed?).
> > 
> > While ULA's could potentially be used by a much larger number of 
> > entities, they may also not be used except by larger organizations. Do
> 
> > you think your average home user or small business would need a ULA?
> > Would they know to get one? Would they have the knowledge to manage
> it?
> > 
> 
> Any residential user who needs to have non-globally accessible devices
> attached to their home network could use them. Think a networked
> printer. Or DVD player, or clothes iron, washing machine, TV etc. As I
> think it'd be likely that most residential users would have devices that
> they don't want "on the Internet", I think ULA addessing domains are
> likely to going to be present in every household.
> 
> As for getting a ULA, that's a user interface problem, and I think
> that's mostly independent of the addressing space or how to generate the
> ULA unique value. A simple enough solution might be that the first time
> an Internet home gateway is powered up it generates the ULA, then starts
> announcing it as a prefix in RAs. This sort of problem has been solved
> before on a number of occasions - IPX, Appletalk or zeroconf could
> provide example methods.
> 
> Regards,
> Mark.
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 04:15:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy1W7-0003Dz-3Y; Tue, 12 Jun 2007 04:14:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1W5-0003Dl-Vc
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:14:17 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy1W5-0005vn-BO
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:14:17 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1Hy1W1-000JlH-VZ; Tue, 12 Jun 2007 17:44:14 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id EAA6620132;
	Tue, 12 Jun 2007 17:44:12 +0930 (CST)
Date: Tue, 12 Jun 2007 17:44:12 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-Id: <20070612174412.6d0072a6.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <466D6A07.8050509@gmail.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com> <466D6A07.8050509@gmail.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 11 Jun 2007 17:28:07 +0200
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> It seems that what you describe is a prime candidate
> for metro addressing, not for ULAs of any kind. And a metro
> prefix is not really any different from a PA prefix, except
> that it's assigned to a municipality.
> 
> ULAs should be kept in-house, literally.
> 

While I'm guessing it is way to late to change the name, I've realised
that they probably should have been called "Unique Internal Addresses".
Unfortunately most non-networking people probably won't realise that
"Local" in ULA means local to your network's administrative domain,
however big or small that is.

>      Brian
> 
> On 2007-06-11 16:21, Paul Vixie wrote:
> >> I suppose most of these users will have big (actually a quite small) flat
> >> infrastructure to keep it simple? Hence what limits them to use just LL?
> >> Why ULA?  What would be the residential users benefit?  Do you think that
> >> residential users will have small routed networks in the future?
> > 
> > i think that the distinction between "provider" and "consumer" will blur in
> > the following ways.
> > 
> > first, if everybody in the neighborhood has overlapping wireless clouds, so
> > that neighbor-sets {A B} {B C} {C D} can join clouds owned by neighbors A,
> > B, and C respectively, that D's preferred path to A will in some cases be
> > through C and B rather than through their "providers".  this is not just
> > because their providers might not have as much in-neighborhood capacity due
> > to backhauling and provider multiplicity, but because this is the topology
> > many human communities prefer.  consider the legal implications for file
> > sharing when there is vs. isn't a "provider" which is regulated and subject
> > to CALEA, as a low hanging example.
> > 
> > second, with COMMONS and things like it sprouting up, there will be networks
> > built using city-owned infrastructure where virtually all traffic into/outof
> > that city has a city-owned last mile.  the need for a "provider" will only be
> > truly notable for traffic into/outof that city, and it will be impractical
> > for economic reasons ("anti-lockin") to use "provider assigned" addressing.
> > the city would have to become an LIR in today's model.  ULA and ULA-C could
> > change all of that, in a bad way, by either requiring a city to run a giant
> > NAT-PT box and breaking end-to-end on intercity traffic, or by requiring the
> > "provider" to do so, or by requiring the "provider" to import ULA routes.
> > 
> > to your last question, i do think that residential users will have small
> > routed networks in the future, rather than a flat neighborhood-wide or even
> > city-wide L2, simply because the broadcast domain for things like Bonjour 
> > will be too large otherwise, and the market seems to have embraced "routers"
> > as their preferred security perimeter (vs hosts, bridges, or repeaters.)
> > 
> > (these are the wages of our sins from not separating routing from identity,
> > and from assuming that the economic principles underlaying IPv4 routing
> > would still apply in an IPv6 world.)
> > 
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> > 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 04:20:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy1bs-0005CD-0O; Tue, 12 Jun 2007 04:20:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy1br-0005C2-06
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:20:15 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy1bq-0000ns-HA
	for ipv6@ietf.org; Tue, 12 Jun 2007 04:20:14 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1Hy1bo-000KVR-Gp; Tue, 12 Jun 2007 17:50:12 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 15AFB20132;
	Tue, 12 Jun 2007 17:50:10 +0930 (CST)
Date: Tue, 12 Jun 2007 17:50:10 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Paul Vixie <paul@vix.com>
Message-Id: <20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <99263.1181633228@sa.vix.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007 07:27:08 +0000
Paul Vixie <paul@vix.com> wrote:

> > Not that it really matters, since ULAs never appear off-site anyway.
> 
> depending on what you mean by a site, both in relative and absolute terms
> of space and of time, there might be general agreement on this point, or not.
> 

I think a better way of describing it is "administrative domain". A
home and the devices in it are an administrative domain - the person who
bought or looks after the devices has to administer, or at least take
ownership of the administration of those devices. That ownership could
be as simple as ringing up an external contractor to get problems
sorted out - this is the same sense that I "administer" the pumbing or
electrical system in my home. 

An "administrative domain" could correspond to a site (a home), or it
might not at all (a personal area network).

Regards,
Mark.

> hopefully the regress isn't infinite.  care to take it a step and see?
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 06:36:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy3jF-0004yN-N1; Tue, 12 Jun 2007 06:36:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy3jE-0004yF-17
	for ipv6@ietf.org; Tue, 12 Jun 2007 06:36:00 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy3jC-0004pw-MP
	for ipv6@ietf.org; Tue, 12 Jun 2007 06:36:00 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5CAZaGk008077
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 12 Jun 2007 03:35:36 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5CAZahQ008076;
	Tue, 12 Jun 2007 03:35:36 -0700 (PDT)
Date: Tue, 12 Jun 2007 03:35:36 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Message-ID: <20070612103536.GA7258@boreas.isi.edu>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> 
> I think a better way of describing it is "administrative domain". A
> home and the devices in it are an administrative domain - the person who
> bought or looks after the devices has to administer, or at least take
> ownership of the administration of those devices. That ownership could
> be as simple as ringing up an external contractor to get problems
> sorted out - this is the same sense that I "administer" the pumbing or
> electrical system in my home. 
> 
> An "administrative domain" could correspond to a site (a home), or it
> might not at all (a personal area network).
> 
> Regards,
> Mark.

	within the routing world, "administrative domain" has avery
	clear meaning - an ASN boundary.

--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 08:41:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy5gi-0005un-Kd; Tue, 12 Jun 2007 08:41:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy5gh-0005ui-33
	for ipv6@ietf.org; Tue, 12 Jun 2007 08:41:31 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy5gf-0005KA-JM
	for ipv6@ietf.org; Tue, 12 Jun 2007 08:41:31 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1Hy5gb-0003kH-PS; Tue, 12 Jun 2007 22:11:25 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id BC3DA20132;
	Tue, 12 Jun 2007 22:11:19 +0930 (CST)
Date: Tue, 12 Jun 2007 22:11:19 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Bill Manning <bmanning@ISI.EDU>
Message-Id: <20070612221119.e34b7a44.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <20070612103536.GA7258@boreas.isi.edu>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070612103536.GA7258@boreas.isi.edu>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007 03:35:36 -0700
Bill Manning <bmanning@ISI.EDU> wrote:

> > 
> > I think a better way of describing it is "administrative domain". A
> > home and the devices in it are an administrative domain - the person who
> > bought or looks after the devices has to administer, or at least take
> > ownership of the administration of those devices. That ownership could
> > be as simple as ringing up an external contractor to get problems
> > sorted out - this is the same sense that I "administer" the pumbing or
> > electrical system in my home. 
> > 
> > An "administrative domain" could correspond to a site (a home), or it
> > might not at all (a personal area network).
> > 
> > Regards,
> > Mark.
> 

> 	within the routing world, "administrative domain" has avery
> 	clear meaning - an ASN boundary.
>

I think it is the other way around. The way to describe
where an ASN boundary can fall is a network's administrative domain,
but not all network administrative domains have ASNs -
self-administered corporate networks that are behind an
ISPs ASN being a common example.

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 10:00:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy6uI-0004be-Ct; Tue, 12 Jun 2007 09:59:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy6uG-0004Vw-7u
	for ipv6@ietf.org; Tue, 12 Jun 2007 09:59:36 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy6uE-0000qJ-Qg
	for ipv6@ietf.org; Tue, 12 Jun 2007 09:59:36 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5CDxGiK001114
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 12 Jun 2007 06:59:16 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5CDxBq1001099;
	Tue, 12 Jun 2007 06:59:11 -0700 (PDT)
Date: Tue, 12 Jun 2007 06:59:11 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Message-ID: <20070612135911.GA719@boreas.isi.edu>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070612103536.GA7258@boreas.isi.edu>
	<20070612221119.e34b7a44.ipng@69706e6720323030352d30312d31340a.nosense.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070612221119.e34b7a44.ipng@69706e6720323030352d30312d31340a.nosense.org>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Bill Manning <bmanning@ISI.EDU>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, Jun 12, 2007 at 10:11:19PM +0930, Mark Smith wrote:
> On Tue, 12 Jun 2007 03:35:36 -0700
> Bill Manning <bmanning@ISI.EDU> wrote:
> 
> > > 
> > > I think a better way of describing it is "administrative domain". A
> > > home and the devices in it are an administrative domain - the person who
> > > bought or looks after the devices has to administer, or at least take
> > > ownership of the administration of those devices. That ownership could
> > > be as simple as ringing up an external contractor to get problems
> > > sorted out - this is the same sense that I "administer" the pumbing or
> > > electrical system in my home. 
> > > 
> > > An "administrative domain" could correspond to a site (a home), or it
> > > might not at all (a personal area network).
> > > 
> > > Regards,
> > > Mark.
> > 
> 
> > 	within the routing world, "administrative domain" has avery
> > 	clear meaning - an ASN boundary.
> >
> 
> I think it is the other way around. The way to describe
> where an ASN boundary can fall is a network's administrative domain,
> but not all network administrative domains have ASNs -
> self-administered corporate networks that are behind an
> ISPs ASN being a common example.
> 
> Regards,
> Mark.

	thats not what the RFCs or current practice dictate.

--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 12:44:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hy9TK-0001Hx-4U; Tue, 12 Jun 2007 12:43:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hy9TJ-0001HU-1U
	for ipv6@ietf.org; Tue, 12 Jun 2007 12:43:57 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hy9TH-0003lI-5l
	for ipv6@ietf.org; Tue, 12 Jun 2007 12:43:56 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 7422C11426
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 16:43:54 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 17:50:10 +0930."
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 12 Jun 2007 16:43:54 +0000
Message-ID: <64527.1181666634@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I think a better way of describing it is "administrative domain". ...

in addition to bmanning's worthy comments, let me say that this redescription
entirely removes the point of my question.  the assertion i first quoted was:

> > > Not that it really matters, since ULAs never appear off-site anyway.

and my question was:

> > depending on what you mean by a site, both in relative and absolute terms
> > of space and of time, there might be general agreement on this point, or
> > not.
> > 
> > hopefully the regress isn't infinite.  care to take it a step and see?

call it a site, call it an administrative domain, call it anything you want.
but explain to me please the relationship between the allocation domain and
the routing domain.  if the network part (allocation domain) is universal,
but the routing domain is not universal, then i need to know what routing
domain you're expecting.  i can advertise my ULA-C to my next door neighbor
but not my across the street neighbor?  i can advertise it to whomever i want
but it will mysteriously not work beyond an unpredictable perimeter?  my city
utility fiber/wireless network hears me but only half of the other residents
hear me?  all local residents hear me but my city's "provider" does not?  my
city's provider hears me but half of their other customers filter me?

if we're going to expect routability to provide connectivity in some cases
but not all, which is what's implied by saying "never appear off-site", then
we need to know what cases and exactly what noncases.  so what's a "site"?
or what's an "administrative domain"?  or call it what you want -- what is it
and how do the routing domain, connectivity domain, and the allocation domain
relate to each other?

if i seem anxious to cut to the chase it's because i've read all this before
when "site local" was first proposed and then later, again, when it was
deprecated.  so let's keep our feet on the ground and define our terms and
make sure we have common understanding before anybody runs out ahead.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 14:20:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyAyA-0002kq-J4; Tue, 12 Jun 2007 14:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyAy9-0002jP-4F
	for ipv6@ietf.org; Tue, 12 Jun 2007 14:19:53 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyAy7-0001GS-JV
	for ipv6@ietf.org; Tue, 12 Jun 2007 14:19:53 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CIJo5H015507
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 11:19:50 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CIJo7I014312; Tue, 12 Jun 2007 11:19:50 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CIJmpt014259; Tue, 12 Jun 2007 11:19:49 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 11:19:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 11:19:48 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <64527.1181666634@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetEQKWppuSx5mdTEKOVd1tn1i5AgAAYTRw
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com>
	<99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 18:19:49.0607 (UTC)
	FILETIME=[437A6F70:01C7AD1E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul,

My understanding is that when two sites agree to form a
peering arrangement and are joined, e.g., by a VPN link,
then they should be able to advertise their ULA-C's for
use within the scope of their now-linked sites. So, it's
not about a site freely redistributing its ULA routes
into any other arbitrary site; there should be an explicit
peering arrangement first.

Fred
fred.l.templin@boeing.com=20

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Tuesday, June 12, 2007 9:44 AM
> To: IETF IPv6 Mailing List
> Subject: Re: Revising Centrally Assigned ULA draft=20
>=20
> > I think a better way of describing it is "administrative=20
> domain". ...
>=20
> in addition to bmanning's worthy comments, let me say that=20
> this redescription
> entirely removes the point of my question.  the assertion i=20
> first quoted was:
>=20
> > > > Not that it really matters, since ULAs never appear=20
> off-site anyway.
>=20
> and my question was:
>=20
> > > depending on what you mean by a site, both in relative=20
> and absolute terms
> > > of space and of time, there might be general agreement on=20
> this point, or
> > > not.
> > >=20
> > > hopefully the regress isn't infinite.  care to take it a=20
> step and see?
>=20
> call it a site, call it an administrative domain, call it=20
> anything you want.
> but explain to me please the relationship between the=20
> allocation domain and
> the routing domain.  if the network part (allocation domain)=20
> is universal,
> but the routing domain is not universal, then i need to know=20
> what routing
> domain you're expecting.  i can advertise my ULA-C to my next=20
> door neighbor
> but not my across the street neighbor?  i can advertise it to=20
> whomever i want
> but it will mysteriously not work beyond an unpredictable=20
> perimeter?  my city
> utility fiber/wireless network hears me but only half of the=20
> other residents
> hear me?  all local residents hear me but my city's=20
> "provider" does not?  my
> city's provider hears me but half of their other customers filter me?
>=20
> if we're going to expect routability to provide connectivity=20
> in some cases
> but not all, which is what's implied by saying "never appear=20
> off-site", then
> we need to know what cases and exactly what noncases.  so=20
> what's a "site"?
> or what's an "administrative domain"?  or call it what you=20
> want -- what is it
> and how do the routing domain, connectivity domain, and the=20
> allocation domain
> relate to each other?
>=20
> if i seem anxious to cut to the chase it's because i've read=20
> all this before
> when "site local" was first proposed and then later, again,=20
> when it was
> deprecated.  so let's keep our feet on the ground and define=20
> our terms and
> make sure we have common understanding before anybody runs out ahead.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 14:58:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyBZm-0001tS-0i; Tue, 12 Jun 2007 14:58:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyBZi-0001tB-O5
	for ipv6@ietf.org; Tue, 12 Jun 2007 14:58:43 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyBZh-0001sg-Fs
	for ipv6@ietf.org; Tue, 12 Jun 2007 14:58:42 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CIwe8R023033
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 13:58:40 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CIwdo3015922; Tue, 12 Jun 2007 11:58:39 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CIwcvO015882; Tue, 12 Jun 2007 11:58:38 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 14:58:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 14:57:59 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <64527.1181666634@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetEQPPEIgRaqarRyC1Q6I8HC23mwAEQv8g
References: Your message of "Tue, 12 Jun 2007 17:50:10
	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 18:58:38.0474 (UTC)
	FILETIME=[AF9756A0:01C7AD23]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20

> if we're going to expect routability to provide connectivity=20
> in some cases
> but not all, which is what's implied by saying "never appear=20
> off-site", then
> we need to know what cases and exactly what noncases.  so=20
> what's a "site"?
> or what's an "administrative domain"?  or call it what you=20
> want -- what is it
> and how do the routing domain, connectivity domain, and the=20
> allocation domain
> relate to each other?

I think the answers to these questions are exactly the same as they
would be for IPv4 private address blocks, although it's more imperative
in the case of IPv4 that they be non-routable outside whatever
boundaries one sets. So then ...

> if i seem anxious to cut to the chase it's because i've read=20
> all this before
> when "site local" was first proposed and then later, again,=20
> when it was
> deprecated.  so let's keep our feet on the ground and define=20
> our terms and
> make sure we have common understanding before anybody runs out ahead.

Does anyone have an answer to this? Site local were deprecated because
the consensus was that there's no need for "private" addresses in IPv6.
Are these ULA-Cs simply taking their place?

Should routers not forward ULAs under any circumstance?

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 15:20:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyBuE-0002le-3u; Tue, 12 Jun 2007 15:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyBuD-0002lK-AG
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:19:53 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyBuC-00073z-TQ
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:19:53 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 386FA11429
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 19:19:52 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 11:19:48 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com>
	<99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 12 Jun 2007 19:19:52 +0000
Message-ID: <83769.1181675992@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

in response to this prompt:

Paul Vixie <paul@vix.com> wrote:
> > if we're going to expect routability to provide connectivity in some cases
> > but not all, which is what's implied by saying "never appear off-site",
> > then we need to know what cases and exactly what noncases.  so what's a
> > "site"?  or what's an "administrative domain"?  or call it what you want
> > -- what is it and how do the routing domain, connectivity domain, and the
> > allocation domain relate to each other?

so far, there've been two answers, coincidentally both from boeing.com.

"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
> My understanding is that when two sites agree to form a peering arrangement
> and are joined, e.g., by a VPN link, then they should be able to advertise
> their ULA-C's for use within the scope of their now-linked sites.  So, it's
> not about a site freely redistributing its ULA routes into any other
> arbitrary site; there should be an explicit peering arrangement first.

i understand about peering and i would like to agree but i don't.  perhaps i
know too much about peering.  when networks A and B are peers, and network C
is a customer of network B, then A and C will use B for "transit".  there is
no reasonable expectation that ULA-C could be, would be, or should be exempt
from that treatment.  furthermore, if C is B's customer for DFZ reachability,
then C will be able to reach A's ULA-C routes through B's default route, and
will not be able to tell the difference between distant ULA networks and
distant non-ULA networks.  this is one of the reasons i consider the thus-far
definitions of "site" to be so useless: "does not encounter reality well."

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> wrote:
> I think the answers to these questions are exactly the same as they would be
> for IPv4 private address blocks, although it's more imperative in the case
> of IPv4 that they be non-routable outside whatever boundaries one sets. So
> then ...

"more imperative" is a hard tool to operate.  who shouldn't route these, why,
and how will we stop them, and what bad things happen if we can't stop them?

> > if i seem anxious to cut to the chase it's because i've read all this
> > before when "site local" was first proposed and then later, again, when it
> > was deprecated.  so let's keep our feet on the ground and define our terms
> > and make sure we have common understanding before anybody runs out ahead.
> 
> Does anyone have an answer to this?  Site local were deprecated because
> the consensus was that there's no need for "private" addresses in IPv6.

site-local was deprecated because nobody could agree what a "site" was, which
in other words means it's down under the same swamp we are now waist deep in.

> Are these ULA-Cs simply taking their place?
> 
> Should routers not forward ULAs under any circumstance?

that would be a fine, clean design.  perhaps if it were a hard requirement,
then the "IPv6 Ready" folks would deny the use of the logo to anyone who
leaked packets or routes in this address space, or who provided any kind of
command level override.  make it "nonrouteable" even among two LANs run by
the same sysadmin.  if you want those LANs to talk, then bridge 'em, don't
route 'em.  (but in that case we'd be using link-local, right?)  (what'll we
do if some open source geeks publish free software without a logo on it?)
(and if we don't think these addresses or routes to them could leak, then why
are we asking that they be unique?)

so my previous question stands.  what's a "site"?


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 15:21:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyBvL-0003OG-Fw; Tue, 12 Jun 2007 15:21:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyBvK-0003Nu-5y
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:21:02 -0400
Received: from ns.virtualized.org ([204.152.189.134] helo=mail.virtualized.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyBvH-0007Kv-N3
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:21:02 -0400
Received: from terminus.local (ns.virtualized.org [204.152.189.134])
	by mail.virtualized.org (8.12.9p1/8.12.9) with ESMTP id l5CJ37xn024475; 
	Tue, 12 Jun 2007 12:03:07 -0700 (PDT)
	(envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service);
	Tue, 12 Jun 2007 12:20:57 -0700
X-PGP-Universal: processed;
	by terminus.local on Tue, 12 Jun 2007 12:20:57 -0700
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
References: Your message of "Tue, 12 Jun 2007 17:50:10
	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <890778B4-246A-463D-8D71-CFCCA74F8D2B@virtualized.org>
From: David Conrad <drc@virtualized.org>
Date: Tue, 12 Jun 2007 12:20:54 -0700
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
X-Mailer: Apple Mail (2.752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 12, 2007, at 11:57 AM, Manfredi, Albert E wrote:
>> if i seem anxious to cut to the chase it's because i've read
>> all this before when "site local" was first proposed and then  
>> later, again,
>> when it was deprecated.  so let's keep our feet on the ground and  
>> define
>> our terms and make sure we have common understanding before  
>> anybody runs out ahead.
>
> Does anyone have an answer to this? Site local were deprecated because
> the consensus was that there's no need for "private" addresses in  
> IPv6.

I thought "Site Locals" were deprecated because people couldn't agree  
on what a "site" was.

> Are these ULA-Cs simply taking their place?

That's my impression, but then again, I haven't see the revised ULA-C  
draft.

> Should routers not forward ULAs under any circumstance?

Wouldn't that make them "link locals"?

Rgds,
-drc


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 15:36:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCAf-0007pe-Ne; Tue, 12 Jun 2007 15:36:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCAd-0007pV-M8
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:36:51 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCAb-0002nT-Ni
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:36:51 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CJam72006446
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 12:36:48 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CJamfw011160; Tue, 12 Jun 2007 14:36:48 -0500 (CDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CJajji011044; Tue, 12 Jun 2007 14:36:47 -0500 (CDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 15:36:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 15:36:42 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <83769.1181675992@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJq37KpdyFmXURqeE9nFZDfIhWwAAMCYg
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 19:36:46.0624 (UTC)
	FILETIME=[036F5200:01C7AD29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20

> site-local was deprecated because nobody could agree what a=20
> "site" was, which
> in other words means it's down under the same swamp we are=20
> now waist deep in.

Okay, I'll gladly agree on both points.

> so my previous question stands.  what's a "site"?

My not-well-articulated point was: if everyone seems to have made RFC
1918 work quite well, why do we need to get overly precise in this time
around?

As far as my own preferences go, I liked site-local and I equally like
mind ULA-Cs with some flexibility. Even though I have no fool-proof
definition for what a "site" is, that covers all possible examples. I've
no trouble at all establishing boundaries for private IPv4 addresses or
for ULA-Cs, when it makes sense for whatever I'm doing.

Is this a little like the RH0 thread? When it was a choice of disabling
by default or removing entirely? My vote is, don't forward ULA-Cs by
default, but let us use them as we used RFC 1918. It was also my vote
when we were discussing site-local.

If we get more restrictive about ULA-Cs, my bet is that something else
will morph to take their place (and the place of site-local addresses).
I guess people just like to have this tool.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 15:43:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCGn-0005VL-Dk; Tue, 12 Jun 2007 15:43:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCGm-0005VD-MD
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:43:12 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCGk-0003Rt-DW
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:43:12 -0400
Received: from ([10.52.116.31])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.8366596;
	Tue, 12 Jun 2007 15:42:52 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 15:42:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 15:42:50 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD402327127@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <890778B4-246A-463D-8D71-CFCCA74F8D2B@virtualized.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJuXY5zuV4JWmQDyH61ien9/USwAAVGRQ
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "David Conrad" <drc@virtualized.org>,
	"Manfredi, Albert E" <albert.e.manfredi@boeing.com>
X-OriginalArrivalTime: 12 Jun 2007 19:42:52.0172 (UTC)
	FILETIME=[DD5184C0:01C7AD29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: David Conrad [mailto:drc@virtualized.org]=20
> I thought "Site Locals" were deprecated because people=20
> couldn't agree on what a "site" was.
>=20
> > Are these ULA-Cs simply taking their place?
>=20
> That's my impression, but then again, I haven't see the=20
> revised ULA-C draft.

Site local were deprecated because they were re-creating overlapping
address space a la RFC1918. This was considered a bad property
for multi-party applications that couldn't tell if they could
forward them as reference or not.

Some people believed that some kind of 'private addresses' were still
needed and thus needed something to replace site local. They invented
ULA. ULA fixed the (overlapping) addressing issue but did not fix the
routability
issue as has now been demonstrated in multiple post. We are essentially
back to where we were a couple years ago, this time not at the
application
level but at the router level, it is hard to know if those
(local/private)
addresses should be passed to the next hop or not.

I'm of the opinion that the added operational complexity to define sites
and partial inter-site routing overcome the benefit of ULA
especially when PI space is available from RIRs and accomplish
the same thing at no extra cost.

However, I do respect people who have a different opinion and
once again I repeat my call/plea for an open meeting of the IPv6 wg
at next IETF to articulate those issue and decide if the wg should
or not continue on the path of defining those ULA-c despite
the (very) negative feedback from the operational community.

    - Alain.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 15:47:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCL1-00067s-9T; Tue, 12 Jun 2007 15:47:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCKz-00067n-N5
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:47:33 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCKx-0004BW-Fc
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:47:33 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id F0B30140C172;
	Tue, 12 Jun 2007 21:47:25 +0200 (CEST)
Message-ID: <466EF851.90300@spaghetti.zurich.ibm.com>
Date: Tue, 12 Jun 2007 20:47:29 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>	<83769.1181675992@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1103706679=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1103706679==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig495F69D6A0FEE1B1881A4F63"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig495F69D6A0FEE1B1881A4F63
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Manfredi, Albert E wrote:
[..]
> If we get more restrictive about ULA-Cs, my bet is that something else
> will morph to take their place (and the place of site-local addresses).=

> I guess people just like to have this tool.

The "ULA-C tool" already exists: IPv6 PI space from the RIRs.

That satisfies all the needs they can ever have and can even provide
them with reverse DNS without having to do split-dns, though split dns
is most likely already required, how else do you keep certain prefixes
"local"/"internal".

People, like home users or totally disconnected networks that will never
ever ever ever connect to the Internet can use ULA (rfc4193) space that
is auto generated.

Except for the 'you can easily filter on fc00::/8 from slipping onto the
internet' argument, I have not heared any compelling argument in favor
of ULA (except that some people do not want to pay the small fee for a
PI prefix).

People in various operational forums have also raised considerate
arguments against ULA-C and they are expecting people to want to
announce blocks they "own" (and most likely see as property) onto the
Internet. PI exists for that, so lets keep it at one swamp please.

Greets,
 Jeroen


--------------enig495F69D6A0FEE1B1881A4F63
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZu+FEuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I168AKCCYnZgnqLlBJf9iQhF9W70OmIq
zACggSP65wcwydtSCK88VZf5ataHjck=
=Cs9R
-----END PGP SIGNATURE-----

--------------enig495F69D6A0FEE1B1881A4F63--


--===============1103706679==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1103706679==--




From ipv6-bounces@ietf.org Tue Jun 12 15:50:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCNp-0007eF-Md; Tue, 12 Jun 2007 15:50:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCNR-0006pB-0E
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:50:05 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCNP-0004iu-Pv
	for ipv6@ietf.org; Tue, 12 Jun 2007 15:50:04 -0400
Received: from ([10.195.246.152])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.8367024;
	Tue, 12 Jun 2007 15:49:46 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 15:49:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 15:49:43 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJq37KpdyFmXURqeE9nFZDfIhWwAAMCYgAADDM4A=
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>,
	"Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 19:49:44.0952 (UTC)
	FILETIME=[D35ABF80:01C7AD2A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]=20

> My not-well-articulated point was: if everyone seems to have made RFC
> 1918 work quite well, why do we need to get overly precise in=20
> this time around?

I happen to work for a network that has to deal on a very regular basis
with the nightmare of overlapping RFC1918 space, so I do not share
your opinion that "everyone seems to have made RFC1918 work quite well".

   - Alain.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:19:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCq9-0005mI-O7; Tue, 12 Jun 2007 16:19:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCq8-0005ly-Ja
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:19:44 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCq7-00025T-5I
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:19:44 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5CKJdGh069073
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Jun 2007 22:19:39 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5CKJcNa002889; Tue, 12 Jun 2007 22:19:39 +0200
Date: Tue, 12 Jun 2007 22:19:38 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
Message-ID: <Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
<snip>
>
> Is this a little like the RH0 thread? When it was a choice of disabling
> by default or removing entirely? My vote is, don't forward ULA-Cs by
> default, but let us use them as we used RFC 1918. It was also my vote
> when we were discussing site-local.

Why are we even talking about ULA-C now? What you want is nicely covered 
by ULA... not ULA-C but regular plain stright forward ULA.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:26:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCwA-0001U4-DJ; Tue, 12 Jun 2007 16:25:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCw9-0001Te-Qu
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:25:57 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCw8-0005gy-BW
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:25:57 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5CKPlSJ091161
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Jun 2007 22:25:47 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5CKPkPj003403; Tue, 12 Jun 2007 22:25:46 +0200
Date: Tue, 12 Jun 2007 22:25:46 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD402327127@PACDCEXCMB05.cable.comcast.com>
Message-ID: <Pine.LNX.4.64.0706122220230.28555@chandra.student.uit.no>
References: <EF2F0EC839870F43A6637360BC12ABD402327127@PACDCEXCMB05.cable.comcast.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007, Durand, Alain wrote:
<snip>
> Site local were deprecated because they were re-creating overlapping
> address space a la RFC1918. This was considered a bad property
> for multi-party applications that couldn't tell if they could
> forward them as reference or not.
>
> Some people believed that some kind of 'private addresses' were still
> needed and thus needed something to replace site local. They invented
> ULA. ULA fixed the (overlapping) addressing issue but did not fix the
> routability
> issue as has now been demonstrated in multiple post. We are essentially
> back to where we were a couple years ago, this time not at the
> application
> level but at the router level, it is hard to know if those
> (local/private)
> addresses should be passed to the next hop or not.
>
> I'm of the opinion that the added operational complexity to define sites
> and partial inter-site routing overcome the benefit of ULA
> especially when PI space is available from RIRs and accomplish
> the same thing at no extra cost.

... and then, what is the point with ULA-C? Regular ULA are free for 
everyone to use. And for those that need unique address space you have 
"PI"... or UA, Unique Address, as Paul Vixie explained in another post in 
a RIPE mailinglist.


> However, I do respect people who have a different opinion and
> once again I repeat my call/plea for an open meeting of the IPv6 wg
> at next IETF to articulate those issue and decide if the wg should
> or not continue on the path of defining those ULA-c despite
> the (very) negative feedback from the operational community.

Forget ULA-C... If we are moving forward with "PI" as explained elsewhere 
worldwide, we have no use for ULA-C.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:28:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyCz3-0006qp-Mh; Tue, 12 Jun 2007 16:28:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCz2-0006qa-RH
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:28:56 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCyx-0006wJ-1I
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:28:56 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CKSmSD023824
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 15:28:49 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CKSmsY023561; Tue, 12 Jun 2007 13:28:48 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CKSiXe023434; Tue, 12 Jun 2007 13:28:47 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 16:28:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 16:28:39 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD260@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AcetLwNUMWM+mC3dQSOLE6QXsKr6wAAACzOw
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com><83769.1181675992@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
	<Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Roger Jorgensen" <rogerj@jorgensen.no>
X-OriginalArrivalTime: 12 Jun 2007 20:28:44.0935 (UTC)
	FILETIME=[4617D170:01C7AD30]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Roger Jorgensen [mailto:rogerj@jorgensen.no]

> Why are we even talking about ULA-C now? What you want is=20
> nicely covered=20
> by ULA... not ULA-C but regular plain stright forward ULA.

Largely, but not completely. Think in terms of large platforms that have
several different networks, administered by different entities, but
easily isolated from The Internet or even a larger intranet. ULA-Cs are
convenient to route within the platform, with the knowledge that they
can easily be filtered at edge routers because they are easy to spot.

Just like before, with site-local addresses, I'm sure this can be worked
around, no matter what the decision is. Having to go to a RIR and ask
for PIs is a possibility, although what's nice about ULA-Cs is exactly
that you don't have to go to ask anything of anyone!

I suppose it all depends on one's perspective.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:31:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyD1Z-00027h-B0; Tue, 12 Jun 2007 16:31:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyD1X-00027S-PR
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:31:31 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyD1W-0008QA-B5
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:31:31 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5CKVQiN070895
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Jun 2007 22:31:26 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5CKVQcW003889; Tue, 12 Jun 2007 22:31:26 +0200
Date: Tue, 12 Jun 2007 22:31:26 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com>
Message-ID: <Pine.LNX.4.64.0706122227540.28555@chandra.student.uit.no>
References: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007, Durand, Alain wrote:
>
>> My not-well-articulated point was: if everyone seems to have made RFC
>> 1918 work quite well, why do we need to get overly precise in
>> this time around?
>
> I happen to work for a network that has to deal on a very regular basis
> with the nightmare of overlapping RFC1918 space, so I do not share
> your opinion that "everyone seems to have made RFC1918 work quite well".

I work on a quite similar network and we have the same issues. And I've 
concluded that ULA-C would work great at our place, IF, please note that 
BIG IF there, if we get reverse DNS. Without that, it is useless for us 
and we might just aswell go with regular "PA" address-space.

... again, the "PI" option will work much better than anything ULA-C 
can ever come up with.

-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:34:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyD4i-0007iS-2Z; Tue, 12 Jun 2007 16:34:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyD4g-0007e5-MR
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:34:46 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyD4f-0001J9-E3
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:34:46 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CKYitY027659
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 15:34:45 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CKYiBo021548; Tue, 12 Jun 2007 13:34:44 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CKYSul020910; Tue, 12 Jun 2007 13:34:33 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 13:34:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 13:34:32 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED877@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <83769.1181675992@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJq5W5rF0A3wiTKOTBt4uTCQwvAACeOfg
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 20:34:33.0548 (UTC)
	FILETIME=[15E1F0C0:01C7AD31]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul,=20
=20
> so far, there've been two answers, coincidentally both from=20
> boeing.com.

Please do not read too much into this. I respect the other
poster's opinions but, as for multiple posters from other
organizations, we are both bringing our own individual
opinions to this that do not necessarily reflect a corporate
position.

Thanks - Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:34:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyD4p-0008IW-QM; Tue, 12 Jun 2007 16:34:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyD4n-00080c-DM
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:34:53 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyD4m-0001Ka-VA
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:34:53 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5CKYoWY071247
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Jun 2007 22:34:50 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5CKYnQQ004174; Tue, 12 Jun 2007 22:34:49 +0200
Date: Tue, 12 Jun 2007 22:34:49 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD260@XCH-NE-1V2.ne.nos.boeing.com>
Message-ID: <Pine.LNX.4.64.0706122231550.28555@chandra.student.uit.no>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com><83769.1181675992@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
	<Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD260@XCH-NE-1V2.ne.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>> -----Original Message-----
>> From: Roger Jorgensen [mailto:rogerj@jorgensen.no]
>
>> Why are we even talking about ULA-C now? What you want is
>> nicely covered
>> by ULA... not ULA-C but regular plain stright forward ULA.
>
> Largely, but not completely. Think in terms of large platforms that have
> several different networks, administered by different entities, but
> easily isolated from The Internet or even a larger intranet. ULA-Cs are
> convenient to route within the platform, with the knowledge that they
> can easily be filtered at edge routers because they are easy to spot.

that is a good description of the network where I work and as I said in my 
last post, ULA-C would work great IF we had reverse DNS...


> Just like before, with site-local addresses, I'm sure this can be worked
> around, no matter what the decision is. Having to go to a RIR and ask
> for PIs is a possibility, although what's nice about ULA-Cs is exactly
> that you don't have to go to ask anything of anyone!

we need some sort of semi-official, semi-accepted as official registry 
runned by someone like the SIXXS registry Jeroen have put up... IF we make 
people "belive" they have to register there, and that site also generate 
ULA prefixes... isn't that ULA-C in a semi-official way?


I'm more and more convince that ULA-C will be a great big hack that will 
hunt us forever... sad.

-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:45:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyDEt-00075T-Dy; Tue, 12 Jun 2007 16:45:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDEs-0006t8-0c
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:45:18 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDEq-0005C9-P4
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:45:17 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 530BA11426;
	Tue, 12 Jun 2007 20:45:16 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Roger Jorgensen <rogerj@jorgensen.no>
In-Reply-To: Your message of "Tue, 12 Jun 2007 22:31:26 +0200."
	<Pine.LNX.4.64.0706122227540.28555@chandra.student.uit.no> 
References: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com>
	<Pine.LNX.4.64.0706122227540.28555@chandra.student.uit.no> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 12 Jun 2007 20:45:16 +0000
Message-ID: <91742.1181681116@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I work on a quite similar network and we have the same issues. And I've
> concluded that ULA-C would work great at our place, IF, please note that
> BIG IF there, if we get reverse DNS. Without that, it is useless for us and
> we might just aswell go with regular "PA" address-space.

so is it the case that the long-dead proposal to add an icmp message type
for "tell me your hostname" would be quite useful in this application?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:48:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyDHq-0001BG-9u; Tue, 12 Jun 2007 16:48:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDHo-0001AW-Sv
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:48:20 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDHn-0006Z0-Lp
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:48:20 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CKmHWY007021
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 15:48:18 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CKmHCw001811; Tue, 12 Jun 2007 13:48:17 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CKm73N001479; Tue, 12 Jun 2007 13:48:16 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 13:48:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 13:48:12 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED878@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <91742.1181681116@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetMrHyVvF+ycRtQgupWUxM7Ys59QAABZlg
References: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com><Pine.LNX.4.64.0706122227540.28555@chandra.student.uit.no>
	<91742.1181681116@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "Roger Jorgensen" <rogerj@jorgensen.no>
X-OriginalArrivalTime: 12 Jun 2007 20:48:13.0663 (UTC)
	FILETIME=[FEB58EF0:01C7AD32]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> so is it the case that the long-dead proposal to add an icmp=20
> message type
> for "tell me your hostname" would be quite useful in this application?

RFC4620?

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 16:48:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyDIP-0001Ky-8O; Tue, 12 Jun 2007 16:48:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDIO-0001Kt-Ha
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:48:56 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDIN-0006vw-1k
	for ipv6@ietf.org; Tue, 12 Jun 2007 16:48:56 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5CKmrq3074011
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 12 Jun 2007 22:48:53 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5CKmrY0005420; Tue, 12 Jun 2007 22:48:53 +0200
Date: Tue, 12 Jun 2007 22:48:52 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Paul Vixie <paul@vix.com>
In-Reply-To: <91742.1181681116@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0706122248390.28555@chandra.student.uit.no>
References: <EF2F0EC839870F43A6637360BC12ABD402327135@PACDCEXCMB05.cable.comcast.com>
	<Pine.LNX.4.64.0706122227540.28555@chandra.student.uit.no> 
	<91742.1181681116@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007, Paul Vixie wrote:
>> I work on a quite similar network and we have the same issues. And I've
>> concluded that ULA-C would work great at our place, IF, please note that
>> BIG IF there, if we get reverse DNS. Without that, it is useless for us and
>> we might just aswell go with regular "PA" address-space.
>
> so is it the case that the long-dead proposal to add an icmp message type
> for "tell me your hostname" would be quite useful in this application?

never heard about.


-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 17:07:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyDa4-0004ZK-EA; Tue, 12 Jun 2007 17:07:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDa3-0004ZF-CG
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:07:11 -0400
Received: from wx-out-0506.google.com ([66.249.82.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDa2-0004yi-3l
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:07:11 -0400
Received: by wx-out-0506.google.com with SMTP id t5so1660716wxc
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 14:07:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=PtTXv8wmdDRYvZzaeTqKck3Oh7ycyoHk6uz+G8L9D9UGNN4IQdW5THM4OIwChB3Fva0Ede5KjW3bQCH3d7xMw+xGi/TOiQeCSC9bjIWXPK1FvaV9GXgK10f0sON4BwDSFCgUne+mck3Tr0cHUuh1PFts60aoH9R0fKAfGEvls/I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=XNYvuV9c6N5Y0lcf8JOvexoE3xOfUjtQyRxnvK6xqzCnZsGTVupwLwmpE0F4DiqV+PNSFm2WgAP8bZRJFjlGTGOmqV7yNmuUXkEZCFhs7jIu7psKm//2JjTSB+DGmxnxxhnQc8pbL9AieVRlgZQdC4C9IqmObPLQBpx/1P/mENA=
Received: by 10.70.90.17 with SMTP id n17mr9437124wxb.1181682429833;
	Tue, 12 Jun 2007 14:07:09 -0700 (PDT)
Received: from Laptop229 ( [168.143.102.62])
	by mx.google.com with ESMTP id h19sm10136191wxd.2007.06.12.14.07.08
	(version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 14:07:09 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: Your message of "Tue, 12 Jun 2007
	17:50:10	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>	<64527.1181666634@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
Date: Tue, 12 Jun 2007 17:06:38 -0400
Message-ID: <001201c7ad35$91c61be0$b55253a0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcetEQPPEIgRaqarRyC1Q6I8HC23mwAEQv8gAASx4IA=
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

... My $.02 or so, inline ... 


>-----Original Message-----
>From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
>Sent: Tuesday, June 12, 2007 14:58
>To: Paul Vixie; IETF IPv6 Mailing List
>Subject: RE: Revising Centrally Assigned ULA draft
>
>> -----Original Message-----
>> From: Paul Vixie [mailto:paul@vix.com]
>
>> if we're going to expect routability to provide connectivity in some
>> cases but not all, which is what's implied by saying "never appear
>> off-site", then we need to know what cases and exactly what noncases.
>> so what's a "site"?
>> or what's an "administrative domain"?  or call it what you want --
>> what is it and how do the routing domain, connectivity domain, and the
>> allocation domain relate to each other?
>
>I think the answers to these questions are exactly the same as they
>would be for IPv4 private address blocks, although it's more imperative
>in the case of IPv4 that they be non-routable outside whatever
>boundaries one sets. So then ...

Exactly right.  It is meant to be a private address space, to be routed /
routable as private address space should be - specifically NOT on the public
internet.

>
>> if i seem anxious to cut to the chase it's because i've read all this
>> before when "site local" was first proposed and then later, again,
>> when it was deprecated.  so let's keep our feet on the ground and
>> define our terms and make sure we have common understanding before
>> anybody runs out ahead.
>
>Does anyone have an answer to this? Site local were deprecated because
>the consensus was that there's no need for "private" addresses in IPv6.
>Are these ULA-Cs simply taking their place?

My understanding is that Site Locals were deprecated not because private
address space is bad in and of itself, but rather - the human element of
lazy allocation (start low & count up) inevitably leads to addressing
conflicts and, golly, can't we be smarter this time around?

>
>Should routers not forward ULAs under any circumstance?

Routers, meaning any routers?  Of course they should - the whole point is to
have private IPs that are routable (unlike link-local addresses).
Routers, meaning out in the DFZ - of course not, this is private address
space.  (Except maybe to black-hole them ,that is)



/TJ


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 17:12:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyDev-00064b-9F; Tue, 12 Jun 2007 17:12:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyDet-0005yF-8r
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:12:11 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyDes-0006dp-0R
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:12:11 -0400
Received: by py-out-1112.google.com with SMTP id a25so2075837pyi
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 14:12:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=DEkRu7OC8cVikqOTU6Zh5NLNM85euc3kSIk+ivH/Aiwp6JXIn0FZHuhmDUttgzAK8BHQgUX3HyIIWWsDlK82Wdmu9BRNw9lU/woB5FEC37AXwxItlxhQMNFWmJfcT3x5SikYA3TiUqNjtFBg2yPvq9AxEhvuos752xaMMEP7KCY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=jhgkQU9lNZU9nNXbTJJhVgFr2RGmMaXHAayBof7oOHZu4JvNsVRVESsI1+NIctJCh70anuNqL8vb0DYj4g0eIl9+EC1xAPnd7wP0p9wXG7zU1f0aU0SA948GJj/jXy8l242Ua98x8C4Omy3oUwRIEqYsN09YO/ZmmX1xzouu+EI=
Received: by 10.35.52.18 with SMTP id e18mr11878326pyk.1181682728668;
	Tue, 12 Jun 2007 14:12:08 -0700 (PDT)
Received: from Laptop229 ( [168.143.102.62])
	by mx.google.com with ESMTP id 38sm5947803nzf.2007.06.12.14.12.07
	(version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 14:12:07 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com><83769.1181675992@sa.vix.com>	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>	<Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD260@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD260@XCH-NE-1V2.ne.nos.boeing.com>
Date: Tue, 12 Jun 2007 17:11:36 -0400
Message-ID: <001301c7ad36$43c4aaf0$cb4e00d0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcetLwNUMWM+mC3dQSOLE6QXsKr6wAAACzOwAAGv+HA=
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

... 

>-----Original Message-----
>From: Manfredi, Albert E [mailto:albert.e.manfredi@boeing.com]
>Sent: Tuesday, June 12, 2007 16:29
>To: Roger Jorgensen
>Cc: IETF IPv6 Mailing List
>Subject: RE: Revising Centrally Assigned ULA draft
>
>> -----Original Message-----
>> From: Roger Jorgensen [mailto:rogerj@jorgensen.no]
>
>> Why are we even talking about ULA-C now? What you want is nicely
>> covered by ULA... not ULA-C but regular plain stright forward ULA.
>
>Largely, but not completely. Think in terms of large platforms that have
>several different networks, administered by different entities, but
>easily isolated from The Internet or even a larger intranet. ULA-Cs are
>convenient to route within the platform, with the knowledge that they
>can easily be filtered at edge routers because they are easy to spot.

And filtering on the normal ULA prefix (or ULA-D, if you will) of FD00::/8
is not easy?
The advantage in ULA-C is the guarantee of global uniqueness, without
"burning" a PI allocation.

>
>Just like before, with site-local addresses, I'm sure this can be worked
>around, no matter what the decision is. Having to go to a RIR and ask
>for PIs is a possibility, although what's nice about ULA-Cs is exactly
>that you don't have to go to ask anything of anyone!

Isn't the whole point of ULA-C that you do, in fact, need to ask someone?


/TJ


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 17:37:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyE3L-0002l3-TZ; Tue, 12 Jun 2007 17:37:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyE3J-0002aA-Mg
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:37:25 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyE2z-0007gv-B0
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:37:25 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1HyE2v-000JOY-Fd; Wed, 13 Jun 2007 07:07:01 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id B92AF20132;
	Wed, 13 Jun 2007 07:06:59 +0930 (CST)
Date: Wed, 13 Jun 2007 07:06:59 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Bill Manning <bmanning@ISI.EDU>
Message-Id: <20070613070659.0d2b486c.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <20070612135911.GA719@boreas.isi.edu>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070612103536.GA7258@boreas.isi.edu>
	<20070612221119.e34b7a44.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070612135911.GA719@boreas.isi.edu>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007 06:59:11 -0700
Bill Manning <bmanning@ISI.EDU> wrote:

> On Tue, Jun 12, 2007 at 10:11:19PM +0930, Mark Smith wrote:
> > On Tue, 12 Jun 2007 03:35:36 -0700
> > Bill Manning <bmanning@ISI.EDU> wrote:
> > 
> > > > 
> > > > I think a better way of describing it is "administrative domain". A
> > > > home and the devices in it are an administrative domain - the person who
> > > > bought or looks after the devices has to administer, or at least take
> > > > ownership of the administration of those devices. That ownership could
> > > > be as simple as ringing up an external contractor to get problems
> > > > sorted out - this is the same sense that I "administer" the pumbing or
> > > > electrical system in my home. 
> > > > 
> > > > An "administrative domain" could correspond to a site (a home), or it
> > > > might not at all (a personal area network).
> > > > 
> > > > Regards,
> > > > Mark.
> > > 
> > 
> > > 	within the routing world, "administrative domain" has avery
> > > 	clear meaning - an ASN boundary.
> > >
> > 
> > I think it is the other way around. The way to describe
> > where an ASN boundary can fall is a network's administrative domain,
> > but not all network administrative domains have ASNs -
> > self-administered corporate networks that are behind an
> > ISPs ASN being a common example.
> > 
> > Regards,
> > Mark.
> 
> 	thats not what the RFCs or current practice dictate.
> 

Can you then give me a different term to describe my service provider
employer's corporate customers networks and residential networks I
don't have any administrative role or control over, yet are part of my
service provider employer's ASN ?

If your context is the global Internet, then yes, I can see that it
could be said that these downstream customers fall within our
adminisrative domain, from the perspective of other ASN members of the
Internet. However, when the context isn't the global Internet, and ULAs
are not global addresses, then I don't think you can accurately say
administrative domain = ASN.

Obviously context is everything. In this case, I think ULAs are a more
general context than the specific Internet. A user of a ULA/ULA-C might
never have an Internet connection, so will never need global prefixes
or a global ASN. They'd still have an administrative domain,
encompassing all the devices they administer, to apply that ULA/ULA-C
prefixes to.

Regards,
Mark.

> --bill
> Opinions expressed may not even be mine by the time you read them, and
> certainly don't reflect those of any other entity (legal or otherwise).
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 17:49:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyEEY-0002tx-DC; Tue, 12 Jun 2007 17:49:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyEEX-0002ts-91
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:49:01 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyEEW-0003wI-06
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:49:01 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5CLmx7f003356
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 12 Jun 2007 14:48:59 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5CLmxqw017260; Tue, 12 Jun 2007 14:48:59 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5CLmwsi017221; Tue, 12 Jun 2007 14:48:59 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 14:48:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 14:48:57 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <83769.1181675992@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJq5W5rF0A3wiTKOTBt4uTCQwvAAE6NFg
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 21:48:58.0428 (UTC)
	FILETIME=[7B288FC0:01C7AD3B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> so my previous question stands.  what's a "site"?

Paraphrasing from the 'draft-templin-autoconf-dhcp' definition
for "Mobile Ad-hoc Network (MANET)":

   site
      a connected network region that comprises routers that
      maintain a routing structure among themselves.  A site
      may be as large as an Autonomous System (AS) or as small
      as an individual router, and may also be a subnetwork of a
      larger site.  A router (and its downstream-attached links)
      is a "site" unto itself, and a site can therefore also be
      considered a "site-of-sites".

(Note that the only distinction drawn between "site" and
"MANET" is that some MANETs are less mobile and ad-hoc
than others - and, we would simply call those: "sites".)

Fred
fred.l.templin@boeing.com=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 17:54:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyEJG-0003k2-TW; Tue, 12 Jun 2007 17:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyEJF-0003jx-R0
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:53:53 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyEJE-0005RN-4m
	for ipv6@ietf.org; Tue, 12 Jun 2007 17:53:53 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 6533011425
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 21:53:51 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 17:06:38 -0400."
	<001201c7ad35$91c61be0$b55253a0$@com> 
References: Your message of "Tue, 12 Jun 2007 17:50:10
	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
	<001201c7ad35$91c61be0$b55253a0$@com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 12 Jun 2007 21:53:51 +0000
Message-ID: <99480.1181685231@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> ...  It is meant to be a private address space, to be routed / routable as
> private address space should be - specifically NOT on the public internet.

what we mean it to be routed to is less important than what people who use it
will actually route it to.  let's focus for now on examples involving many
networks run by folks with diverse goals.  any time you propose a rule like
"not meant to be XYZ" you have to be able to say how that rule will get
enforced, and what the internet will look like if enforcement doesn't happen.

> ... and, golly, can't we be smarter this time around?

so far, not.

> >Should routers not forward ULAs under any circumstance?
> 
> Routers, meaning any routers?  Of course they should - the whole point is to
> have private IPs that are routable (unlike link-local addresses).

that's another voice heard from.

> Routers, meaning out in the DFZ - of course not, this is private address
> space.  (Except maybe to black-hole them ,that is)

is the dfz the only place these routes shouldn't go?  how will this be
enforced, if cooperating connectees to the dfz all want to do it anyway?

if we can't agree on "what's a site" then can we ask "what's ``private''" ?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 18:01:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyEQy-0004TM-9K; Tue, 12 Jun 2007 18:01:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyEQw-0004TG-Ds
	for ipv6@ietf.org; Tue, 12 Jun 2007 18:01:50 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyEQv-0008Bt-LB
	for ipv6@ietf.org; Tue, 12 Jun 2007 18:01:50 -0400
Received: from 219-90-138-205.ip.adam.com.au ([219.90.138.205]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1HyEQr-000KKj-1V; Wed, 13 Jun 2007 07:31:45 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 472D020132;
	Wed, 13 Jun 2007 07:31:43 +0930 (CST)
Date: Wed, 13 Jun 2007 07:31:42 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Message-Id: <20070613073142.7a17eaca.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com>
	<94420.1181571703@sa.vix.com>
	<15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com>
	<466E448B.5050101@gmail.com> <99263.1181633228@sa.vix.com>
	<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 12 Jun 2007 15:36:42 -0400
"Manfredi, Albert E" <albert.e.manfredi@boeing.com> wrote:

> > -----Original Message-----
> > From: Paul Vixie [mailto:paul@vix.com] 
> 
> > site-local was deprecated because nobody could agree what a 
> > "site" was, which
> > in other words means it's down under the same swamp we are 
> > now waist deep in.
> 
> Okay, I'll gladly agree on both points.
> 
> > so my previous question stands.  what's a "site"?
> 
> My not-well-articulated point was: if everyone seems to have made RFC
> 1918 work quite well, why do we need to get overly precise in this time
> around?
> 

RFC1918 doesn't work well at all because it creates
overlapping / duplicated addressing, and NAT, with all it's worts, is
the only way, other than renumbering, to overcome that if you need to
interconnect. It's as ugly as sin to see multiple NAT boxes facing each
other when you have 2 (or more ! - and this happens at corporate DMZs
when building "extranets" to other corporates) duplicate RFC1918
addressing domains that have to be interconnected.

RFC3879, "Deprecating Site Local Addresses" describes the reasons why
site-locals were deprecated, but all those reasons are fundamentally
problems that have and do occur with RFC1918 addressing in IPv4. At
least with IPv6 we have a chance to avoid them. Having had to deal
directly with some of those reasons myself when working with IPv4, I
certainly don't want to go there again in IPv6 if possible.

> As far as my own preferences go, I liked site-local and I equally like
> mind ULA-Cs with some flexibility. Even though I have no fool-proof
> definition for what a "site" is, that covers all possible examples. I've
> no trouble at all establishing boundaries for private IPv4 addresses or
> for ULA-Cs, when it makes sense for whatever I'm doing.
> 

I agree. I don't think it is that hard to decide on the boundry. I
think fundamentally the thing that is trying to be avoided is that ULAs
become considered "cheap" or "free" PI addressing, and then having
their reachabilty scope slowly increase overtime e.g. initially your
own network, then the networks you directly peer with, then the local city or
other continent etc.

Regards,
Mark.

> Is this a little like the RH0 thread? When it was a choice of disabling
> by default or removing entirely? My vote is, don't forward ULA-Cs by
> default, but let us use them as we used RFC 1918. It was also my vote
> when we were discussing site-local.
> 
> If we get more restrictive about ULA-Cs, my bet is that something else
> will morph to take their place (and the place of site-local addresses).
> I guess people just like to have this tool.
> 
> Bert
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 19:11:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyFVl-0002qo-J1; Tue, 12 Jun 2007 19:10:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyFVj-0002qj-05
	for ipv6@ietf.org; Tue, 12 Jun 2007 19:10:51 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyFVh-00065A-N4
	for ipv6@ietf.org; Tue, 12 Jun 2007 19:10:50 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 12 Jun 2007 19:10:49 -0400
X-IronPort-AV: i="4.16,413,1175486400"; 
	d="scan'208"; a="62590234:sNHT57228276"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5CNAnVu007764; 
	Tue, 12 Jun 2007 19:10:49 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5CNAd5f023738; 
	Tue, 12 Jun 2007 23:10:39 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Jun 2007 19:10:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Jun 2007 19:10:44 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210442FB34@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AcetJq5W5rF0A3wiTKOTBt4uTCQwvAAE6NFgAAK4kdA=
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Paul Vixie" <paul@vix.com>,
	"IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 12 Jun 2007 23:10:39.0578 (UTC)
	FILETIME=[E478B3A0:01C7AD46]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2041; t=1181689849;
	x=1182553849; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20Revising=20Centrally=20Assigned=20ULA=20draft=20
	|Sender:=20
	|To:=20=22Templin, =20Fred=20L=22=20<Fred.L.Templin@boeing.com>,
	=20=22Paul =20Vixie=22=20<paul@vix.com>,
	=0A=20=20=20=20=20=20=20=20=22IETF=20IPv6=20M
	ailing=20List=22=20<ipv6@ietf.org>;
	bh=0HbHmKEIsoyhCB/cwZbOcfNDERAG0T0sSXCYErx5Fvw=;
	b=fR1C2LMW3eQDAhEiXvo74/rDNwBK2SrdMXEFUJCO8RUsH+RpiDoMQQV2fDMy6R4zUwVoQ4Wh
	/RFcfpS06MtrbwwCJezSZ/zkovbBbNv0fkig11LulK5JtBJFM4GXI8+x;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Doesn't RFC 4193 already define "site" in a way that is clear for ULAs:

3.3.  Scope Definition

   By default, the scope of these addresses is global.  That is, they
   are not limited by ambiguity like the site-local addresses defined in
   [ADDARCH].  Rather, these prefixes are globally unique, and as such,
   their applicability is greater than site-local addresses.  Their
   limitation is in the routability of the prefixes, which is limited to
   a site and any explicit routing agreements with other sites to
   propagate them (also see Section 4.1).  Also, unlike site-locals, a
   site may have more than one of these prefixes and use them at the
   same time.

A site (or site-of-sites to use the MANET terminology) is defined by the
routability of a particular ULA prefix.

- Bernie=20

-----Original Message-----
From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
Sent: Tuesday, June 12, 2007 5:49 PM
To: Paul Vixie; IETF IPv6 Mailing List
Subject: RE: Revising Centrally Assigned ULA draft=20

> so my previous question stands.  what's a "site"?

Paraphrasing from the 'draft-templin-autoconf-dhcp' definition
for "Mobile Ad-hoc Network (MANET)":

   site
      a connected network region that comprises routers that
      maintain a routing structure among themselves.  A site
      may be as large as an Autonomous System (AS) or as small
      as an individual router, and may also be a subnetwork of a
      larger site.  A router (and its downstream-attached links)
      is a "site" unto itself, and a site can therefore also be
      considered a "site-of-sites".

(Note that the only distinction drawn between "site" and
"MANET" is that some MANETs are less mobile and ad-hoc
than others - and, we would simply call those: "sites".)

Fred
fred.l.templin@boeing.com=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 19:47:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyG4Z-00043r-UA; Tue, 12 Jun 2007 19:46:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyG4Y-00043P-5N
	for ipv6@ietf.org; Tue, 12 Jun 2007 19:46:50 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyG4V-0006Ux-NI
	for ipv6@ietf.org; Tue, 12 Jun 2007 19:46:50 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5CNkggB003911 for <ipv6@ietf.org>; Wed, 13 Jun 2007 02:46:45 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 02:46:43 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 02:46:43 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh101.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 13 Jun 2007 02:46:43 +0300
Received: from [172.19.74.169] (dadhcp-172019074169.americas.nokia.com
	[172.19.74.169])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5CNkfG6013461 for <ipv6@ietf.org>; Wed, 13 Jun 2007 02:46:42 +0300
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
References: Your message of "Tue, 12 Jun 2007 17:50:10
	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<64527.1181666634@sa.vix.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <ED1B5F6F-418D-4A42-B1A6-9D3732417AD4@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Tue, 12 Jun 2007 16:46:49 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 12 Jun 2007 23:46:43.0884 (UTC)
	FILETIME=[EE7F96C0:01C7AD4B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> Does anyone have an answer to this? Site local were deprecated because
> the consensus was that there's no need for "private" addresses in  
> IPv6.
> Are these ULA-Cs simply taking their place?

No, that's not correct.  It had more do with their non-unique  
properties and the notion of a unicast site scope.  This is  
documented in

   RFC3879 "Deprecating Site Local Addresses"

> Should routers not forward ULAs under any circumstance?

Also not correct.  Specific ULAs (/48) are fine to forward inside of  
a site, but the ULA prefix (/7) should be filtered by default at the  
site border.  See Section 4. Operational Guidelines in:

   RFC4193 "Unique Local IPv6 Unicast Addresses"

Bob

p.s. This discussion would be a lot more rational if folks would  
spend some time and reread these documents.  We hope to get the new  
central ULA draft out soon.  One of the authors was traveling and we  
are waiting to get his comments on the text before submitting.

Also, I personally find it pretty odd to see a debate on a document  
before it is published.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 12 22:30:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyIc2-00031i-1w; Tue, 12 Jun 2007 22:29:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyIc0-00031b-Ei
	for ipv6@ietf.org; Tue, 12 Jun 2007 22:29:32 -0400
Received: from an-out-0708.google.com ([209.85.132.240])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyIc0-0003zj-5b
	for ipv6@ietf.org; Tue, 12 Jun 2007 22:29:32 -0400
Received: by an-out-0708.google.com with SMTP id c17so10472anc
	for <ipv6@ietf.org>; Tue, 12 Jun 2007 19:29:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=LCgys6v8ICitICX89ezMan/dOKE630bsKhWQu03dwW6FVk1Mr/YK2lczkrlhRPDGn4SGKmw3W1s7QWtA/O4y2plJQF+dUxuf30GlHCjOYWW/9jcUFdHspy3Z0e9RZfoLLo3fKZKJzR7iEyu9wwIBN/WN/Iab3oTykRHO1N8IK3w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=GL2a2fW34rtxWALXKwCo5aQutjhS/gYfZe3GQGDMBopkO1i1sdMcTUoDv66RYLQvf9G9TyC3K0V0MfhUoOYZhmTVbAw7GqG98LibHez7zdLb6WWkYe84Cc02+OHZti7uOh+SK8Gdtj4az1mhiv9elpQGDtvzH8R86ZhMbRuov3U=
Received: by 10.100.228.6 with SMTP id a6mr54447anh.1181701771928;
	Tue, 12 Jun 2007 19:29:31 -0700 (PDT)
Received: from Laptop229 ( [76.21.226.168])
	by mx.google.com with ESMTP id d21sm325608and.2007.06.12.19.29.29
	(version=SSLv3 cipher=RC4-MD5); Tue, 12 Jun 2007 19:29:31 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: Your message of "Tue, 12 Jun 2007
	17:50:10	+0930."<20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org>	<64527.1181666634@sa.vix.com>	<CA7D9B4A761066448304A6AFC09ABDA9015AD25E@XCH-NE-1V2.ne.nos.boeing.com>	<001201c7ad35$91c61be0$b55253a0$@com>
	<99480.1181685231@sa.vix.com>
In-Reply-To: <99480.1181685231@sa.vix.com>
Date: Tue, 12 Jun 2007 22:28:59 -0400
Message-ID: <004401c7ad62$9a85d1d0$cf917570$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcetPE5/jpjPuKY/S+SyqWf5uAmxqAAIOU+Q
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Couple more thoughts ...


>From: Paul Vixie [mailto:paul@vix.com]
>Sent: Tuesday, June 12, 2007 17:54
>To: 'IETF IPv6 Mailing List'
>Subject: Re: Revising Centrally Assigned ULA draft
>
>> ...  It is meant to be a private address space, to be routed /
>> routable as private address space should be - specifically NOT on the
>public internet.
>
>what we mean it to be routed to is less important than what people who
>use it will actually route it to.  let's focus for now on examples
>involving many networks run by folks with diverse goals.  any time you
>propose a rule like "not meant to be XYZ" you have to be able to say how
>that rule will get enforced, and what the internet will look like if
>enforcement doesn't happen.

Fair enough, and certainly the world is full of lots of different people /
environments, all with diverse goals.  Some good, some bad - many subjective
:).
Is simply recommending that providers not accept reachability announcements
for ULAs, the same way it is recommended that they not accept RFC1918
announcements, not good enough (and for the same reasons)?


>
>> ... and, golly, can't we be smarter this time around?
>
>so far, not.
>

I wouldn't be that negative; the fact that we are attempting to solve a
problem is a good sign, no?
(providing a method to accomplish a nearly-collision-free private address
space ... which (to me) seems to be a noticeable improvement.)


>> >Should routers not forward ULAs under any circumstance?
>>
>> Routers, meaning any routers?  Of course they should - the whole point
>> is to have private IPs that are routable (unlike link-local
>addresses).
>
>that's another voice heard from.
>

I think I am merely passing along the sentiment of the authors of the RFC,
albeit poorly paraphrased.
To quote:
	Abstract
		   This document defines an IPv6 unicast address format that
is globally
		   unique and is intended for local communications, usually
inside of a
		   site.  These addresses are not expected to be routable on
the global
		   Internet.
That says, to me anyway, that they are to be routable - but not globally
routable.


>> Routers, meaning out in the DFZ - of course not, this is private
>> address space.  (Except maybe to black-hole them ,that is)
>
>is the dfz the only place these routes shouldn't go?  how will this be
>enforced, if cooperating connectees to the dfz all want to do it anyway?
>
>if we can't agree on "what's a site" then can we ask "what's
>``private''" ?

I am not fully sure we need to define "site".  Even in the abstract above
(wherein it mentions "site") the meat of the statement seems to focus on the
"private" aspect, which I believe we have recommendations and policies in
place to manage (again, a la RFC1918).
	Does everyone follow them, no.  
	Are they perfect, no.  
	Do we have enough policy, and experience with that policy, to move
forward - I would think so. 
	... ?



Again - just MHO.
/TJ


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 02:58:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyMnq-00011R-2y; Wed, 13 Jun 2007 02:58:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyMno-00011J-LG
	for ipv6@ietf.org; Wed, 13 Jun 2007 02:58:00 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyMnh-0004oB-5j
	for ipv6@ietf.org; Wed, 13 Jun 2007 02:58:00 -0400
Received: from [66.17.247.236]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyMq9-0005UM-1x
	for ipv6@ietf.org; Wed, 13 Jun 2007 07:00:27 +0000
Mime-Version: 1.0 (Apple Message framework v752.3)
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Message-Id: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
Content-Type: multipart/mixed; boundary=Apple-Mail-4--600298419
From: Joe Abley <jabley@ca.afilias.info>
Date: Tue, 12 Jun 2007 23:57:28 -0700
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22f8e36c8d8be0bcbb9bf02fb6ce7335
Subject: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


--Apple-Mail-4--600298419
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Here's a revised candidate -01. As before, I have not submitted this  
to the i-d repository, but offer it here first instead in order to  
make sure my changes seem reasonable.

Substantive changes include:

  + removed section 3.1 ("Origination"), since hosts will originate  
any junk they want, and it's pointless to presume to dictate  
otherwise (paraphrasing Jinmei). I left in the comment about hosts  
not being required to support RH0 in the introduction, after the line  
"This document updates [RFC2460] and [RFC4294]".

  + section 3.2 becomes section 3, and has been re-worked to spell  
out the undefined RH type behaviour from 2460, and to be more  
specific about which addresses nodes need to check when deciding  
whether or not to look for RH0. I have not incorporated the more  
conservative OpenBSD/Mac OS X behaviour as a requirement, since it's  
not clear to me that such a requirement is reasonable for all nodes  
(e.g. for routers).

  + section 5 has been substantially reduced (and its subsections  
removed) along the lines suggested by Jinmei. I added a note about  
the side-effects of deprecation on benign uses of RH0, and included  
mention of the possibility of new, future, safe routing header types  
which might fill some of the resulting gap.

I have not corrected the alleged typos such as "recognized" vs.  
"recognised", since the latter is a valid example of how we spell  
things in my world :-)

Revised text attached. Comments welcome. Apologies for the delay in  
getting these edits done; I expect subsequent text wrangling to be  
turned around more rapidly.


Joe

--Apple-Mail-4--600298419
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; x-unix-mode=0644;
	name=draft-ietf-ipv6-deprecate-rh0-01.txt
Content-Disposition: attachment; filename=draft-ietf-ipv6-deprecate-rh0-01.txt




Network Working Group                                           J. Abley
Internet-Draft                                                   Afilias
Updates: 2460, 4294                                            P. Savola
(if approved)                                                  CSC/FUNET
Intended status: Standards Track                         G. Neville-Neil
Expires: December 14, 2007                       Neville-Neil Consulting
                                                           June 12, 2007


             Deprecation of Type 0 Routing Headers in IPv6
             draft-ietf-ipv6-deprecate-rh0-01-candidate-01

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   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 will expire on December 14, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   The functionality provided by IPv6's Type 0 Routing Header can be
   exploited in order to achieve packet amplification for the purposes
   of generating denial-of-service traffic.  This document updates the
   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
   Headers, in the light of the severity of this security concern.



Abley, et al.           Expires December 14, 2007               [Page 1]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   This document updates RFC 2460 and RFC 4294.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Deprecation of RH0  . . . . . . . . . . . . . . . . . . . . . . 3
   4.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     4.1.  Ingress Filtering . . . . . . . . . . . . . . . . . . . . . 4
     4.2.  Packet Filtering  . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7
   Intellectual Property and Copyright Statements  . . . . . . . . . . 8































Abley, et al.           Expires December 14, 2007               [Page 2]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


1.  Introduction

   [RFC2460] defines an IPv6 extension header called "Routing Header",
   identified by a Next Header value of 43 in the immediately preceding
   header.  A particular Routing Header subtype denoted as "Type 0" is
   also defined.  Type 0 Routing Headers are referred to as "RH0" in
   this document.

   The functionality provided by IPv6's Type 0 Routing Header can be
   exploited in order to achieve packet amplification for the purposes
   of generating denial-of-service traffic.  This document updates the
   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
   Headers, in the light of the severity of this security concern.

   This document updates [RFC2460] and [RFC4294].

   IPv6 implementations are no longer required to implement RH0 in any
   way.


2.  Definitions

   RH0 in this document denotes the IPv6 Extension Header type 43
   ("Routing Header") variant 0 ("Type 0 Routing Header"), as defined in
   [RFC2460].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].


3.  Deprecation of RH0

   IPv6 nodes MUST NOT process RH0 in packets whose destination address
   in the IPv6 header is an address assigned to them.  Such packets MUST
   be processed according to the behaviour specified in Section 4.4 of
   [RFC2460] for a datagram which includes an unrecognised Routing Type
   value, namely:

      If Segments Left is zero, the node must ignore the Routing header
      and proceed to process the next header in the packet, whose type
      is identified by the Next Header field in the Routing header.

      If Segments Left is non-zero, the node must discard the packet and
      send an ICMP Parameter Problem, Code 0, message to the packet's
      Source Address, pointing to the unrecognised Routing Type.





Abley, et al.           Expires December 14, 2007               [Page 3]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


4.  Operations

4.1.  Ingress Filtering

   It is to be expected that it will take some time before all IPv6
   nodes are updated to remove support for RH0.  Some of the uses of RH0
   described in [CanSecWest07] can be mitigated using ingress filtering,
   as recommended in [RFC2827] and [RFC3704].

4.2.  Packet Filtering

   Firewall policy intended to protect against packets containing RH0
   should be constructed such that routing headers of other types (which
   may well have legitimate and benign applications) are handled on
   their own merits.  For example, discarding all packets with any type
   of routing header simply as a reaction to the problems with RH0 is
   inappropriate, and may hamper future functionality designed using
   non-type 0 routing headers.  For example, Mobile IPv6 uses the type 2
   Routing Header [RFC3775].

   Where filtering capabilities do not facilitate matching specific
   types of Routing Headers, filtering based on the presence of any
   Routing Headers on IPv6 routers, without explicitly checking the
   Routing Header type, is strongly discouraged.


5.  Security Considerations

   The purpose of this document is to deprecate a feature of IPv6 which
   has been shown to have undesirable security implications.  Specific
   examples of vulnerabilities which are facilitated by the availability
   of RH0 can be found in [CanSecWest07].  In particular, RH0 provides a
   mechanism for traffic amplification, which might be used as a denial-
   of-service attack.

   A single RH0 may contain multiple waypoint addresses, and the same
   address may be included more than once in the same RH0.  This allows
   a packet to be constructed such that it will oscillate between two
   RH0-processing hosts or routers many times.  This allows a stream of
   packets from an attacker to be amplified along the path between two
   remote routers, which could be used to cause congestion along
   arbitrary remote paths and hence act as a denial-of-service
   mechanism. 88-fold amplification has been demonstrated using this
   technique [CanSecWest07].

   This attack is particularly serious in that it affects the entire
   path between the two exploited nodes, not only the nodes themselves
   or their local networks.  Analogous functionality may be found in the



Abley, et al.           Expires December 14, 2007               [Page 4]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   IPv4 source route option, but the opportunities for abuse are greater
   with RH0 due to the ability to specify many more waypoints in each
   packet.

   The severity of the threat is considered to be sufficient to warrant
   deprecation of RH0 entirely.  This has the unfortunate side-effect
   that benign use cases for RH0 are eliminated along with the potential
   security hazards; such applications may be facilitated in the future
   by new routing header specifications which do not suffer from RH0's
   problems.


6.  IANA Considerations

   The IANA registry "Internet Protocol Version 6 (IPv6) Parameters"
   should be updated to reflect that variant 0 of IPv6 header-type 43
   ("Routing Header") is deprecated.


7.  Acknowlegements

   Potential problems with Routing Headers were identified in 2001
   [I-D.savola-ipv6-rh-ha-security].  In 2002 a proposal was made to
   restrict Routing Header processing in hosts
   [I-D.savola-ipv6-rh-hosts].  These efforts did not gain sufficient
   momentum to change the IPv6 specification, but resulted in the
   modification of the Mobile IPv6 specification to use the type 2
   Routing Header instead of RH0 [RFC3775].  Vishwas Manral identified
   various risks associated with RH0 in 2006 including the amplification
   attack; several of these vulnerabilities (together with other issues)
   were later documented in [I-D.ietf-v6ops-security-overview].

   An eloquent and useful description of the operational security
   implications of RH0 was presented by Philippe Biondi and Arnaud
   Ebalard at the CanSecWest conference in Vancouver, 2007
   [CanSecWest07].  This presentation resulted in widespread publicity
   for the risks associated with RH0.

   This document also benefits from the contributions of IPv6 and V6OPS
   orking group participants, including Jari Arkko, Arnaud Ebalard, Tim
   Enos, Brian Haberman, Jun-ichiro itojun HAGINO, Bob Hinden, JINMEI
   Tatuya, David Malone, Jeroen Massar, Dave Thaler and Guillaume
   Valadon.


8.  References





Abley, et al.           Expires December 14, 2007               [Page 5]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


8.1.  Normative References

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

   [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", RFC 2460, December 1998.

   [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
              April 2006.

8.2.  Informative References

   [CanSecWest07]
              BIONDI, P. and A. EBALARD, "IPv6 Routing Header Security",
              CanSecWest Security Conference 2007, April 2007.

              http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf

   [I-D.ietf-v6ops-security-overview]
              Davies, E., "IPv6 Transition/Co-existence Security
              Considerations", draft-ietf-v6ops-security-overview-06
              (work in progress), October 2006.

   [I-D.savola-ipv6-rh-ha-security]
              Savola, P., "Security of IPv6 Routing Header and Home
              Address Options", draft-savola-ipv6-rh-ha-security-02
              (work in progress), March 2002.

   [I-D.savola-ipv6-rh-hosts]
              Savola, P., "Note about Routing Header Processing on IPv6
              Hosts", draft-savola-ipv6-rh-hosts-00 (work in progress),
              February 2002.

   [RFC2827]  Ferguson, P. and D. Senie, "Network Ingress Filtering:
              Defeating Denial of Service Attacks which employ IP Source
              Address Spoofing", BCP 38, RFC 2827, May 2000.

   [RFC3704]  Baker, F. and P. Savola, "Ingress Filtering for Multihomed
              Networks", BCP 84, RFC 3704, March 2004.

   [RFC3775]  Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
              in IPv6", RFC 3775, June 2004.


Appendix A.  Change History

   This section to be removed prior to publication.



Abley, et al.           Expires December 14, 2007               [Page 6]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   00 Strawman, draft-jabley-ipv6-rh0-is-evil, circulated to provoke
      discussion.

   01 Clarified Section 3; presented more options in Section 4; added
      Pekka and George as authors.  This document version was not widely
      circulated.

   00 Renamed, draft-ietf-ipv6-deprecate-rh0, a candidate working group
      document.

   01-candidate-00  Incorporated text summarising some of the unwelcome
      uses of RH0; added some clariying text describing deprecation;
      modified some ambiguous text in Section 4.2; added "Updates:
      4294".

   01-candidate-01  Incorporated contributions from working group:
      substantially reduced Section 5; clarified wording in Section 3.


Authors' Addresses

   Joe Abley
   Afilias Canada Corp.
   Suite 204, 4141 Yonge Street
   Toronto, ON  M2P 2A8
   Canada

   Phone: +1 416 673 4176
   Email: jabley@ca.afilias.info


   Pekka Savola
   CSC/FUNET
   Espoo,
   Finland

   Email: psavola@funet.fi


   George Neville-Neil
   Neville-Neil Consulting
   2261 Market St. #239
   San Francisco, CA  94114
   USA

   Email: gnn@neville-neil.com





Abley, et al.           Expires December 14, 2007               [Page 7]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Abley, et al.           Expires December 14, 2007               [Page 8]
=0C

--Apple-Mail-4--600298419
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--Apple-Mail-4--600298419--




From ipv6-bounces@ietf.org Wed Jun 13 03:53:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyNed-00045u-82; Wed, 13 Jun 2007 03:52:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyNeb-00042i-My
	for ipv6@ietf.org; Wed, 13 Jun 2007 03:52:33 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyNea-0003jn-9P
	for ipv6@ietf.org; Wed, 13 Jun 2007 03:52:33 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 996B2233C4; Wed, 13 Jun 2007 16:52:29 +0900 (JST)
To: jabley@ca.afilias.info
In-Reply-To: Your message of "Tue, 12 Jun 2007 23:57:28 -0700"
	<CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070613075229.996B2233C4@coconut.itojun.org>
Date: Wed, 13 Jun 2007 16:52:29 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Here's a revised candidate -01. As before, I have not submitted this  
> to the i-d repository, but offer it here first instead in order to  
> make sure my changes seem reasonable.
(snip)

	I'm very happy with the 01-candidate-01.  concise, straight to the
	point.

itojun

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 07:54:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyRQF-0002zd-Mg; Wed, 13 Jun 2007 07:53:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyRQE-0002zY-C7
	for ipv6@ietf.org; Wed, 13 Jun 2007 07:53:58 -0400
Received: from e1.ny.us.ibm.com ([32.97.182.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyRQE-0000CB-3S
	for ipv6@ietf.org; Wed, 13 Jun 2007 07:53:58 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5DBrvH1022828
	for <ipv6@ietf.org>; Wed, 13 Jun 2007 07:53:57 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5DBrvNI511690 for <ipv6@ietf.org>; Wed, 13 Jun 2007 07:53:57 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1])
	by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5DBruml029990 for <ipv6@ietf.org>; Wed, 13 Jun 2007 07:53:56 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-167-169.wecm.ibm.com
	[9.67.167.169])
	by d01av02.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5DBrtWt029962
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 13 Jun 2007 07:53:56 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5DBroLG008411;
	Wed, 13 Jun 2007 04:53:51 -0700
Message-Id: <200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
To: Joe Abley <jabley@ca.afilias.info>
In-reply-to: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
Comments: In-reply-to Joe Abley <jabley@ca.afilias.info>
	message dated "Tue, 12 Jun 2007 23:57:28 -0700."
Date: Wed, 13 Jun 2007 04:53:50 -0700
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On the whole, looks pretty good.

> Abstract

>    The functionality provided by IPv6's Type 0 Routing Header can be
>    exploited in order to achieve packet amplification for the purposes
>    of generating denial-of-service traffic.  This document updates the
>    IPv6 specification to deprecate the use of IPv6 Type 0 Routing
>    Headers, in the light of the severity of this security concern.

The "amplification" terminology seems imprecise/wrong. When I think of
amplification attacks, I think of one packet causing more packets to
be generated or one packet resulting in a bigger response. I.e., there
is amplification of the amount of data sent. In case at hand, packets
are not amplified, they are just routed in a sort of loop. Is there
more precise terminology that could be used? (Then again, maybe this
particular terminology is already widely used here.)

>    The functionality provided by IPv6's Type 0 Routing Header can be
>    exploited in order to achieve packet amplification for the purposes
>    of generating denial-of-service traffic.  This document updates the

Seems like a sentence or two describing the exploitation itself would
be good. Not a lot of detail, but more than just "it can be
exploited". (Later, I see that you include such text in the security
considerations section. I think it should be moved to (or included in)
the beginning of the document.

> 4.2.  Packet Filtering

>    Firewall policy intended to protect against packets containing RH0
>    should be constructed such that routing headers of other types (which
>    may well have legitimate and benign applications) are handled on
>    their own merits.  For example, discarding all packets with any type
>    of routing header simply as a reaction to the problems with RH0 is
>    inappropriate, and may hamper future functionality designed using
>    non-type 0 routing headers.  For example, Mobile IPv6 uses the type 2
>    Routing Header [RFC3775].

The next to last sentence is a bit weak. Dropping all packets with
routing headers will flat-out break MIPv6. If routers/firewalls start
doing that, that would be very bad. From a standards perspecive, we
should clearly flag that as bad/non compliant.

>    Where filtering capabilities do not facilitate matching specific
>    types of Routing Headers, filtering based on the presence of any
>    Routing Headers on IPv6 routers, without explicitly checking the
>    Routing Header type, is strongly discouraged.

Again, this is too weak, IMO. "strongly discouraged" is not the same
as "don't do that". It should be clear that from a standards
perspective that that sort of filtering is non-compliant.

> 8.1.  Normative References


>    [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
>               April 2006.

Shouldn't this  reference be informative?

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 09:51:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyTFD-0004zZ-HF; Wed, 13 Jun 2007 09:50:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyTFB-0004zT-Uc
	for ipv6@ietf.org; Wed, 13 Jun 2007 09:50:41 -0400
Received: from mrout1-b.corp.dcn.yahoo.com ([216.109.112.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyTF9-00065n-Ou
	for ipv6@ietf.org; Wed, 13 Jun 2007 09:50:41 -0400
Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com
	[216.145.48.98])
	by mrout1-b.corp.dcn.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id
	l5DDoJLi054905; Wed, 13 Jun 2007 06:50:20 -0700 (PDT)
Date: Wed, 13 Jun 2007 21:50:08 +0800
Message-ID: <m2fy4wklpr.wl%gnn@neville-neil.com>
From: "George V. Neville-Neil" <gnn@neville-neil.com>
To: Joe Abley <jabley@ca.afilias.info>
In-Reply-To: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8
	(=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95
	(i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I am happy with the revisions.

Best,
George

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 09:55:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyTJa-0006oP-8N; Wed, 13 Jun 2007 09:55:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyTJZ-0006oK-Bb
	for ipv6@ietf.org; Wed, 13 Jun 2007 09:55:13 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyTJY-00071S-UZ
	for ipv6@ietf.org; Wed, 13 Jun 2007 09:55:13 -0400
Received: from [66.17.247.236]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyTM1-0009Yd-40; Wed, 13 Jun 2007 13:57:46 +0000
In-Reply-To: <200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 13 Jun 2007 06:54:48 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 13-Jun-2007, at 04:53, Thomas Narten wrote:

> On the whole, looks pretty good.
>
>> Abstract
>
>>    The functionality provided by IPv6's Type 0 Routing Header can be
>>    exploited in order to achieve packet amplification for the  
>> purposes
>>    of generating denial-of-service traffic.  This document updates  
>> the
>>    IPv6 specification to deprecate the use of IPv6 Type 0 Routing
>>    Headers, in the light of the severity of this security concern.
>
> The "amplification" terminology seems imprecise/wrong. When I think of
> amplification attacks, I think of one packet causing more packets to
> be generated or one packet resulting in a bigger response. I.e., there
> is amplification of the amount of data sent. In case at hand, packets
> are not amplified, they are just routed in a sort of loop. Is there
> more precise terminology that could be used? (Then again, maybe this
> particular terminology is already widely used here.)

How about if I say "traffic amplification over a remote path" instead  
of "packet amplification"?

>>    The functionality provided by IPv6's Type 0 Routing Header can be
>>    exploited in order to achieve packet amplification for the  
>> purposes
>>    of generating denial-of-service traffic.  This document updates  
>> the
>
> Seems like a sentence or two describing the exploitation itself would
> be good. Not a lot of detail, but more than just "it can be
> exploited". (Later, I see that you include such text in the security
> considerations section. I think it should be moved to (or included in)
> the beginning of the document.

Would a forward reference to the Security Considerations section be a  
reasonable compromise?

>> 4.2.  Packet Filtering
>
>>    Firewall policy intended to protect against packets containing RH0
>>    should be constructed such that routing headers of other types  
>> (which
>>    may well have legitimate and benign applications) are handled on
>>    their own merits.  For example, discarding all packets with any  
>> type
>>    of routing header simply as a reaction to the problems with RH0 is
>>    inappropriate, and may hamper future functionality designed using
>>    non-type 0 routing headers.  For example, Mobile IPv6 uses the  
>> type 2
>>    Routing Header [RFC3775].
>
> The next to last sentence is a bit weak. Dropping all packets with
> routing headers will flat-out break MIPv6. If routers/firewalls start
> doing that, that would be very bad. From a standards perspecive, we
> should clearly flag that as bad/non compliant.

If I understand your point, you are happy with the meaning of this  
section but wish that it made its point more forcefully.

 From other comments on previous revisions of this document, people  
expressed concern over whether normative language had any place in  
descriptions of operational practice (as opposed to protocol  
implementation). As such it's not clear to me whether MUST NOTs in  
this section would have any teeth.

How about replacing "hamper" with something stronger ("defeat"?  
"break"?) If you have other suggestions for text, I would be happy to  
see them.

>>    Where filtering capabilities do not facilitate matching specific
>>    types of Routing Headers, filtering based on the presence of any
>>    Routing Headers on IPv6 routers, without explicitly checking the
>>    Routing Header type, is strongly discouraged.
>
> Again, this is too weak, IMO. "strongly discouraged" is not the same
> as "don't do that". It should be clear that from a standards
> perspective that that sort of filtering is non-compliant.

I wonder again about normative language being applied to operational  
practices, and would appreciate enlightenment.

How about adding a sentence which is a little more blunt, along the  
lines of "filtering routing headers indiscriminately, without regard  
to type, will seriously impair future extensions of the IPv6 protocol  
which make use of Routing Headers"? Other suggestions?

>> 8.1.  Normative References
>
>
>>    [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
>>               April 2006.
>
> Shouldn't this  reference be informative?

The document states that it update RFC4294 in section 1, so I  
presumed that reference needed to be normative.


Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 13:00:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyWD2-00059R-68; Wed, 13 Jun 2007 13:00:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyWCz-00059M-Qe
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:00:37 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyWCz-0007TU-Aa
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:00:37 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5DH045E022987; Wed, 13 Jun 2007 20:00:33 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 20:00:27 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 20:00:24 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 13 Jun 2007 20:00:24 +0300
Received: from [172.19.74.169] (dadhcp-172019074169.americas.nokia.com
	[172.19.74.169])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5DH0LUC030926; Wed, 13 Jun 2007 20:00:22 +0300
In-Reply-To: <CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Wed, 13 Jun 2007 10:00:29 -0700
To: Joe Abley <jabley@ca.afilias.info>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 13 Jun 2007 17:00:24.0605 (UTC)
	FILETIME=[55BA94D0:01C7ADDC]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Joe,

>> The next to last sentence is a bit weak. Dropping all packets with
>> routing headers will flat-out break MIPv6. If routers/firewalls start
>> doing that, that would be very bad. From a standards perspecive, we
>> should clearly flag that as bad/non compliant.
>
> If I understand your point, you are happy with the meaning of this  
> section but wish that it made its point more forcefully.
>
> From other comments on previous revisions of this document, people  
> expressed concern over whether normative language had any place in  
> descriptions of operational practice (as opposed to protocol  
> implementation). As such it's not clear to me whether MUST NOTs in  
> this section would have any teeth.

I agree with Thomas that it is important to state this very  
clearly.   How about something like this:

    Firewall policy intended to protect against packets containing RH0
    must be constructed such that routing headers of other types
    are not filtered by default.  Doing so will break other uses of
    the routing headers such as the Routing Header Type 2 used by  
Mobile IPv6 [RFC3775] and future
    functionality designed using other routing header types.

and something similar for the later text.

Comments?

Bob


> How about replacing "hamper" with something stronger ("defeat"?  
> "break"?) If you have other suggestions for text, I would be happy  
> to see them.
>
>>>    Where filtering capabilities do not facilitate matching specific
>>>    types of Routing Headers, filtering based on the presence of any
>>>    Routing Headers on IPv6 routers, without explicitly checking the
>>>    Routing Header type, is strongly discouraged.
>>
>> Again, this is too weak, IMO. "strongly discouraged" is not the same
>> as "don't do that". It should be clear that from a standards
>> perspective that that sort of filtering is non-compliant.
>
> I wonder again about normative language being applied to  
> operational practices, and would appreciate enlightenment.
>
> How about adding a sentence which is a little more blunt, along the  
> lines of "filtering routing headers indiscriminately, without  
> regard to type, will seriously impair future extensions of the IPv6  
> protocol which make use of Routing Headers"? Other suggestions?
>
>>> 8.1.  Normative References
>>
>>
>>>    [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
>>>               April 2006.
>>
>> Shouldn't this  reference be informative?
>
> The document states that it update RFC4294 in section 1, so I  
> presumed that reference needed to be normative.
>
>
> Joe
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 13:09:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyWLb-0003vL-Ll; Wed, 13 Jun 2007 13:09:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyWLa-0003vG-9V
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:09:30 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyWLY-0000V3-Ho
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:09:30 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 893D5140C022;
	Wed, 13 Jun 2007 19:09:26 +0200 (CEST)
Message-ID: <467024C6.7040304@spaghetti.zurich.ibm.com>
Date: Wed, 13 Jun 2007 18:09:26 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
In-Reply-To: <9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0857317768=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0857317768==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig339A841464A8B5B1452425F3"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig339A841464A8B5B1452425F3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Bob Hinden wrote:
[..]
> I agree with Thomas that it is important to state this very clearly. =20
> How about something like this:
>=20
>    Firewall policy intended to protect against packets containing RH0
>    must be constructed such that routing headers of other types
>    are not filtered by default.  Doing so will break other uses of
>    the routing headers such as the Routing Header Type 2 used by Mobile=

>    IPv6 [RFC3775] and future
>    functionality designed using other routing header types.
>=20
> and something similar for the later text.

When the above, or similar text, is included in the document I will
fully support it for advancement.


I have one teeny thing that I think would be worthwhile repeating in
that document: "Please enable uRPF where possible" as that actually
already takes care of the most of the problem as packets can't go where
they are not able to come from.


Additionally, one nit in section 7 if you didn't catch it yet:
"   This document also benefits from the contributions of IPv6 and V6OPS
   orking group participants,"

a "W" is missing there.

Thanks Joe, Pekka, George and the rest of the WG for drafting this up.

Greets,
 Jeroen


--------------enig339A841464A8B5B1452425F3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZwJMYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I6t1AJ485SrP6lrXP4KZBLDkLcE2d4dD
OACffo2j7t7v0wxLNGjBLal6cwd9cWA=
=mc4e
-----END PGP SIGNATURE-----

--------------enig339A841464A8B5B1452425F3--


--===============0857317768==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0857317768==--




From ipv6-bounces@ietf.org Wed Jun 13 13:42:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyWrq-0007Ps-Fc; Wed, 13 Jun 2007 13:42:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyWrp-0007Pk-5e
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:42:49 -0400
Received: from e33.co.us.ibm.com ([32.97.110.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyWro-0000Zi-SD
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:42:49 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5DHglBb030416
	for <ipv6@ietf.org>; Wed, 13 Jun 2007 13:42:47 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5DHgliF203114 for <ipv6@ietf.org>; Wed, 13 Jun 2007 11:42:47 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5DHglDR021812 for <ipv6@ietf.org>; Wed, 13 Jun 2007 11:42:47 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-172-130.wecm.ibm.com
	[9.67.172.130])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5DHgjkk020112
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 13 Jun 2007 11:42:46 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5DHgLUH002825;
	Wed, 13 Jun 2007 10:42:22 -0700
Message-Id: <200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
To: bob.hinden@nokia.com
In-reply-to: <9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
Comments: In-reply-to Bob Hinden <bob.hinden@nokia.com>
	message dated "Wed, 13 Jun 2007 10:00:29 -0700."
Date: Wed, 13 Jun 2007 10:42:21 -0700
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Bob Hinden <bob.hinden@nokia.com> writes:

> I agree with Thomas that it is important to state this very  
> clearly.

To be clear, if even a small fraction of firewalls get deployed that
just block all traffic with a RH, MIPv6 breaks and becomes
undeployable in practice. For EVERYONE!

MIPv6 can't work if (in practice), moving around results in stuff not
working with even only a low degree of frequency. Hence, this is a
hugely serious issue.

How about something like this:

>     Firewall policy intended to protect against packets containing RH0
>     must be constructed such that routing headers of other types
>     are not filtered by default.  Doing so will break other uses of
>     the routing headers such as the Routing Header Type 2 used by  
> Mobile IPv6 [RFC3775] and future
>     functionality designed using other routing header types.

Could be even stronger. How about:

     It must be understood that blocking all traffic with any RH
     (rather than restricting blockage only to type 0) has very
     serious implications for the deployment of future
     technology. Quite simply, if even a small percentage of deployed
     firewalls block other types of routing headers by default, it
     will become impossible to deploy technologies using a routing
     header. MIPv6 [RFCxxx] relies on a type 2 RH. If even a small
     fraction of firewalls block MIPv6 traffic, MIPv6 will become
     undeployable in practice.

     Consequently, firewall policy intended to protect against packets
     containing RH0 MUST NOT simply filter all traffic with a routing
     header; it must be possible to disable forwarding of type 0
     traffic without blocking other types of routing headers. In
     addition, the default configuration MUST be to permit forwarding
     of traffic using a RH other than 0.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 13:54:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyX33-0001LD-AN; Wed, 13 Jun 2007 13:54:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyX32-0001FJ-D1
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:54:24 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyX2o-00040E-2e
	for ipv6@ietf.org; Wed, 13 Jun 2007 13:54:24 -0400
Received: from auguste.remlab.net (unknown
	[IPv6:2002:3e4e:907a:0:20d:60ff:fe38:6d16])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id AFC07967E3;
	Wed, 13 Jun 2007 19:54:08 +0200 (CEST)
From: =?windows-1252?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: ipv6@ietf.org
Date: Wed, 13 Jun 2007 20:53:59 +0300
User-Agent: KMail/1.9.7
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
In-Reply-To: <200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200706132053.59897@auguste.remlab.net>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Thomas Narten <narten@us.ibm.com>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Le mercredi 13 juin 2007, Thomas Narten a =E9crit :
> To be clear, if even a small fraction of firewalls get deployed that
> just block all traffic with a RH, MIPv6 breaks and becomes
> undeployable in practice. For EVERYONE!

The answer to the upcoming question must be obvious to many people here,=20
but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your=20
network, or does it break both Mobile Nodes *AND* Correspondant Nodes?

In the later case, it might be worth mentioning that "blocking RH breaks=20
connectivity toward external peers completely (or almost)". This looks=20
more terrifying to me that "blocking RH prevents deployment of future=20
technology". In fact, whether you and I like it or not (I hate it),=20
firewalls are quite often blocking "future technology" on purpose.

In the poor real world of IT, there are some network administrator that=20
are responsible for the security of their perimeter. There are seldom=20
responsible for new technology not working out of the box. It's a=20
truth, we'd rather adapt to, if we can.

My 2 eurocents,

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 14:18:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyXPl-0005q0-6K; Wed, 13 Jun 2007 14:17:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyXPj-0005pq-Gg
	for ipv6@ietf.org; Wed, 13 Jun 2007 14:17:51 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyXPi-00014K-36
	for ipv6@ietf.org; Wed, 13 Jun 2007 14:17:51 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5DIHkkj031352; Wed, 13 Jun 2007 21:17:46 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 21:17:45 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 13 Jun 2007 21:17:45 +0300
Received: from [172.19.74.169] (dadhcp-172019074169.americas.nokia.com
	[172.19.74.169])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5DIHgLF022012; Wed, 13 Jun 2007 21:17:43 +0300
In-Reply-To: <200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4F50195A-B60B-426D-8931-E036930EBEEB@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Wed, 13 Jun 2007 11:17:50 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 13 Jun 2007 18:17:45.0498 (UTC)
	FILETIME=[23EAA7A0:01C7ADE7]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thomas,

> Could be even stronger. How about:
>
>      It must be understood that blocking all traffic with any RH
>      (rather than restricting blockage only to type 0) has very
>      serious implications for the deployment of future
>      technology. Quite simply, if even a small percentage of deployed
>      firewalls block other types of routing headers by default, it
>      will become impossible to deploy technologies using a routing
>      header. MIPv6 [RFCxxx] relies on a type 2 RH. If even a small
>      fraction of firewalls block MIPv6 traffic, MIPv6 will become
>      undeployable in practice.
>
>      Consequently, firewall policy intended to protect against packets
>      containing RH0 MUST NOT simply filter all traffic with a routing
>      header; it must be possible to disable forwarding of type 0
>      traffic without blocking other types of routing headers. In
>      addition, the default configuration MUST be to permit forwarding
>      of traffic using a RH other than 0.
>

Works for me.

Bob



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:24:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaKT-0005PW-H3; Wed, 13 Jun 2007 17:24:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaKR-0005PI-Ov
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:24:35 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyaKQ-00048m-EN
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:24:35 -0400
Received: from [66.17.247.117]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyaMs-000ELw-0L; Wed, 13 Jun 2007 21:27:06 +0000
In-Reply-To: <467024C6.7040304@spaghetti.zurich.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<467024C6.7040304@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4A2AB3C9-3F27-4DD7-A8D3-87480361E53C@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 13 Jun 2007 14:24:10 -0700
To: Jeroen Massar <jeroen@unfix.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 13-Jun-2007, at 10:09, Jeroen Massar wrote:

> I have one teeny thing that I think would be worthwhile repeating in
> that document: "Please enable uRPF where possible" as that actually
> already takes care of the most of the problem as packets can't go  
> where
> they are not able to come from.

Is this not implicit in the various references to RFC2827 and RFC3704?


Joe


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:24:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaJr-0005JR-RG; Wed, 13 Jun 2007 17:23:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaJp-0005JF-Te
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:23:57 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyaJd-0003Wp-1v
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:23:57 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 538E211425
	for <ipv6@ietf.org>; Wed, 13 Jun 2007 21:23:44 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 14:48:57 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>
	<83769.1181675992@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 13 Jun 2007 21:23:44 +0000
Message-ID: <53884.1181769824@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> > so my previous question stands.  what's a "site"?
> 
> Paraphrasing from the 'draft-templin-autoconf-dhcp' definition
> for "Mobile Ad-hoc Network (MANET)":
> 
>    site
>       a connected network region that comprises routers that
>       maintain a routing structure among themselves.  A site
>       may be as large as an Autonomous System (AS) or as small
>       as an individual router, and may also be a subnetwork of a
>       larger site.  A router (and its downstream-attached links)
>       is a "site" unto itself, and a site can therefore also be
>       considered a "site-of-sites".

by this, any connected network region comprising routers that maintain routing
structure among themselves, up to the size of an autonomous system but perhaps
as small as a single router, is a "site".  nothing is said (here) about what
else these routers might be attached to, so i assume that there can be
connectivity to other sites or to the dfz but that it's not required.  i take
the term "downstream" to mean "toward less connected sites", which would be
meaningless if all sites were equally well connected (either to each other or
to the dfz) but that's not a problem.

this is a fine high level definition of "site", from what i can see, but i
have a question... what is the difference between a site-of-sites made up of
autonomous system sized sites, vs. a site-of-sites made up of leaf sites?  if
a site can be considered a "site of sites", then the automotive exchange
network or the global internet could be shoehorned into fitting this
definition.  i don't think that's the intent, and so, where's the fine print?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:26:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaMQ-00060P-It; Wed, 13 Jun 2007 17:26:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaMP-00060G-AE
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:26:37 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyaMP-0004ZB-33
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:26:37 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id AEB8311425
	for <ipv6@ietf.org>; Wed, 13 Jun 2007 21:26:36 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 12 Jun 2007 19:10:44 -0400."
	<8E296595B6471A4689555D5D725EBB210442FB34@xmb-rtp-20a.amer.cisco.com> 
References: <8E296595B6471A4689555D5D725EBB210442FB34@xmb-rtp-20a.amer.cisco.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 13 Jun 2007 21:26:36 +0000
Message-ID: <53983.1181769996@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> A site (or site-of-sites to use the MANET terminology) is defined by the
> routability of a particular ULA prefix.
> 
> - Bernie 

from a process point of view that would be circular, since we're hoping
to use the meaning of "site" to help us define the proposed rules for ULA.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:33:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaSs-0004Gm-4y; Wed, 13 Jun 2007 17:33:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaSp-00044R-SD
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:33:15 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyaSo-0006L8-42
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:33:15 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id D33CB140C30F;
	Wed, 13 Jun 2007 23:33:11 +0200 (CEST)
Message-ID: <46706297.1030909@spaghetti.zurich.ibm.com>
Date: Wed, 13 Jun 2007 22:33:11 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Joe Abley <jabley@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<467024C6.7040304@spaghetti.zurich.ibm.com>
	<4A2AB3C9-3F27-4DD7-A8D3-87480361E53C@ca.afilias.info>
In-Reply-To: <4A2AB3C9-3F27-4DD7-A8D3-87480361E53C@ca.afilias.info>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0087617277=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0087617277==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig88A5FCA0AADAD5F161FBE0C2"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig88A5FCA0AADAD5F161FBE0C2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Joe Abley wrote:
>=20
> On 13-Jun-2007, at 10:09, Jeroen Massar wrote:
>=20
>> I have one teeny thing that I think would be worthwhile repeating in
>> that document: "Please enable uRPF where possible" as that actually
>> already takes care of the most of the problem as packets can't go wher=
e
>> they are not able to come from.
>=20
> Is this not implicit in the various references to RFC2827 and RFC3704?

Yes, but how many people actually implement it? :)
It is also why I noted that it might be worthwhile repeating it.

Clearly a lot of networks don't do uRPF. It is still possible to spoof
from a lot of networks (both IPv4 and IPv6). The most heard reason is
that they "can't" because the hardware/software of their routers/AP's
don't support it. In a lot of cases it can be enabled, but people simply
don't.

If a network does do uRPF most RH0 attacks are already resolved as then
the router can't send the packet back over the link as the source
address is incorrect. As such it is IMHO relevant to mention.

I am not requiring or anything near that, that it goes in btw, but I do
think it might be a good idea to put in the document just as a reminder
for people who don't read the whole chain of documents.

Greets,
 Jeroen


--------------enig88A5FCA0AADAD5F161FBE0C2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZwYpcuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I9bGAJ4qb6+eYF684p9EbK8FagE2XQQ3
IQCggvI4kFTBZDYJEtkzxUe4QnZnTyI=
=E8AF
-----END PGP SIGNATURE-----

--------------enig88A5FCA0AADAD5F161FBE0C2--


--===============0087617277==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0087617277==--




From ipv6-bounces@ietf.org Wed Jun 13 17:34:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaTl-0006vU-Vn; Wed, 13 Jun 2007 17:34:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaTj-0006vP-HY
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:34:11 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyaTj-0006Xj-7s
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:34:11 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5DLYAXK018234
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Jun 2007 16:34:10 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5DLY9qu021237; Wed, 13 Jun 2007 14:34:09 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5DLY3S3020907; Wed, 13 Jun 2007 14:34:07 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Jun 2007 14:34:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 13 Jun 2007 14:34:06 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED888@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <53884.1181769824@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft 
Thread-Index: AceuAVD25XuHAuXJTeOxmbPCqU2iUgAAKLUA
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com><83769.1181675992@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
	<53884.1181769824@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 13 Jun 2007 21:34:06.0792 (UTC)
	FILETIME=[921D7480:01C7AE02]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: 
Subject: RE: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul,

I appreciate the feedback, and I'll take it under serious
consideration for my MANET/Autoconf draft. But, I'm not
sure anymore that we need to sweat the details of exactly
what is a site within the context of these discussions.

Someone pointed out that ([RFC4193], Section 4) provides
operational guidelines, and I think the same guidelines
would be true for ULA-Cs as they are for ULAs?

Thanks - Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Wednesday, June 13, 2007 2:24 PM
> To: IETF IPv6 Mailing List
> Subject: Re: Revising Centrally Assigned ULA draft=20
>=20
> "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
>=20
> > > so my previous question stands.  what's a "site"?
> >=20
> > Paraphrasing from the 'draft-templin-autoconf-dhcp' definition
> > for "Mobile Ad-hoc Network (MANET)":
> >=20
> >    site
> >       a connected network region that comprises routers that
> >       maintain a routing structure among themselves.  A site
> >       may be as large as an Autonomous System (AS) or as small
> >       as an individual router, and may also be a subnetwork of a
> >       larger site.  A router (and its downstream-attached links)
> >       is a "site" unto itself, and a site can therefore also be
> >       considered a "site-of-sites".
>=20
> by this, any connected network region comprising routers that=20
> maintain routing
> structure among themselves, up to the size of an autonomous=20
> system but perhaps
> as small as a single router, is a "site".  nothing is said=20
> (here) about what
> else these routers might be attached to, so i assume that there can be
> connectivity to other sites or to the dfz but that it's not=20
> required.  i take
> the term "downstream" to mean "toward less connected sites",=20
> which would be
> meaningless if all sites were equally well connected (either=20
> to each other or
> to the dfz) but that's not a problem.
>=20
> this is a fine high level definition of "site", from what i=20
> can see, but i
> have a question... what is the difference between a=20
> site-of-sites made up of
> autonomous system sized sites, vs. a site-of-sites made up of=20
> leaf sites?  if
> a site can be considered a "site of sites", then the=20
> automotive exchange
> network or the global internet could be shoehorned into fitting this
> definition.  i don't think that's the intent, and so, where's=20
> the fine print?
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:37:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaXG-0002Rz-Ce; Wed, 13 Jun 2007 17:37:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaXE-0002Rt-Du
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:37:48 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyaXC-00058j-Vp
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:37:48 -0400
Received: from [66.17.247.117]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyaZl-000EeC-Bz; Wed, 13 Jun 2007 21:40:25 +0000
In-Reply-To: <200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 13 Jun 2007 14:37:29 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 13-Jun-2007, at 10:42, Thomas Narten wrote:

>>     Firewall policy intended to protect against packets containing  
>> RH0
>>     must be constructed such that routing headers of other types
>>     are not filtered by default.  Doing so will break other uses of
>>     the routing headers such as the Routing Header Type 2 used by
>> Mobile IPv6 [RFC3775] and future
>>     functionality designed using other routing header types.
>
> Could be even stronger. How about:
>
>      It must be understood that blocking all traffic with any RH
>      (rather than restricting blockage only to type 0) has very
>      serious implications for the deployment of future
>      technology. Quite simply, if even a small percentage of deployed
>      firewalls block other types of routing headers by default, it
>      will become impossible to deploy technologies using a routing
>      header. MIPv6 [RFCxxx] relies on a type 2 RH. If even a small
>      fraction of firewalls block MIPv6 traffic, MIPv6 will become
>      undeployable in practice.
>
>      Consequently, firewall policy intended to protect against packets
>      containing RH0 MUST NOT simply filter all traffic with a routing
>      header; it must be possible to disable forwarding of type 0
>      traffic without blocking other types of routing headers. In
>      addition, the default configuration MUST be to permit forwarding
>      of traffic using a RH other than 0.

I'm slightly concerned that such advice flies in the face of  
conventional advice given to those constructing firewall policy. It  
is normal practice, I believe, for end-site firewall policy to be  
deployed based on denying everything by default, and only permitting  
those packets which are known to correspond to traffic which ought to  
be permitted. I believe it is generally considered to be good advice  
to block all "future technology" by default, and to permit it only  
once the implications of doing so are well-known.

Outside end-sites, in the core, dropping packets based on the  
presence of any type of routing header is clearly a bad idea.

If we want the advice in this section to be taken seriously, do we  
need to distinguish between firewall policy in end-sites and packet  
filters that might be added to core/ISP networks as a mitigation of  
the specific problems associated with RH0?


Joe

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:39:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyaZ6-0005NU-Al; Wed, 13 Jun 2007 17:39:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyaZ4-0005N7-6b
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:39:42 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HyaZ2-0005EX-Rc
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:39:42 -0400
Received: from [66.17.247.117]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyabX-000Ef8-Tt; Wed, 13 Jun 2007 21:42:16 +0000
In-Reply-To: <46706297.1030909@spaghetti.zurich.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<467024C6.7040304@spaghetti.zurich.ibm.com>
	<4A2AB3C9-3F27-4DD7-A8D3-87480361E53C@ca.afilias.info>
	<46706297.1030909@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FCA76C74-6EF0-4D13-9237-1D728D97620B@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 13 Jun 2007 14:39:20 -0700
To: Jeroen Massar <jeroen@unfix.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 13-Jun-2007, at 14:33, Jeroen Massar wrote:

> Joe Abley wrote:
>>
>> On 13-Jun-2007, at 10:09, Jeroen Massar wrote:
>>
>>> I have one teeny thing that I think would be worthwhile repeating in
>>> that document: "Please enable uRPF where possible" as that actually
>>> already takes care of the most of the problem as packets can't go  
>>> where
>>> they are not able to come from.
>>
>> Is this not implicit in the various references to RFC2827 and  
>> RFC3704?
>
> Yes, but how many people actually implement it? :)
> It is also why I noted that it might be worthwhile repeating it.

So, should we make the language wrapping the references to 2827 and  
3704 stronger, perhaps saying that operators SHOULD deploy ingress  
filtering as an appropriate reaction to the threats described in RH0?


Joe

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:43:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyad7-0000Ty-EG; Wed, 13 Jun 2007 17:43:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyad6-0000Tt-6y
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:43:52 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyad5-0000KZ-Vy
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:43:52 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 94CF611426
	for <ipv6@ietf.org>; Wed, 13 Jun 2007 21:43:51 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
In-Reply-To: Your message of "Wed, 13 Jun 2007 14:34:06 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED888@XCH-NW-7V2.nw.nos.boeing.com>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com><83769.1181675992@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED879@XCH-NW-7V2.nw.nos.boeing.com>
	<53884.1181769824@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED888@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 13 Jun 2007 21:43:51 +0000
Message-ID: <54821.1181771031@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: Re: Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Someone pointed out that ([RFC4193], Section 4) provides
> operational guidelines, and I think the same guidelines
> would be true for ULA-Cs as they are for ULAs?

when there's a draft for ula-c, we'll know.  it's been described here as
"ula but with working in-addr.arpa lookups", and as long as the domain of
"lookups have to work within" is the same as the domain as "can reach ipv6
addresses within" then it may not make much difference whether the words
"local" or "site" are used, or if used, what they're made to mean.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 13 17:56:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyaou-0002u2-0H; Wed, 13 Jun 2007 17:56:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyaos-0002tt-Ul
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:56:02 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyaor-0003BE-P3
	for ipv6@ietf.org; Wed, 13 Jun 2007 17:56:02 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 62A16140C05A;
	Wed, 13 Jun 2007 23:55:57 +0200 (CEST)
Message-ID: <467067ED.3050301@spaghetti.zurich.ibm.com>
Date: Wed, 13 Jun 2007 22:55:57 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Joe Abley <jabley@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<467024C6.7040304@spaghetti.zurich.ibm.com>
	<4A2AB3C9-3F27-4DD7-A8D3-87480361E53C@ca.afilias.info>
	<46706297.1030909@spaghetti.zurich.ibm.com>
	<FCA76C74-6EF0-4D13-9237-1D728D97620B@ca.afilias.info>
In-Reply-To: <FCA76C74-6EF0-4D13-9237-1D728D97620B@ca.afilias.info>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0282893206=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0282893206==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigACEA1C7499D0A6645438E09E"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigACEA1C7499D0A6645438E09E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Joe Abley wrote:
>=20
> On 13-Jun-2007, at 14:33, Jeroen Massar wrote:
>=20
>> Joe Abley wrote:
>>>
>>> On 13-Jun-2007, at 10:09, Jeroen Massar wrote:
>>>
>>>> I have one teeny thing that I think would be worthwhile repeating in=

>>>> that document: "Please enable uRPF where possible" as that actually
>>>> already takes care of the most of the problem as packets can't go wh=
ere
>>>> they are not able to come from.
>>>
>>> Is this not implicit in the various references to RFC2827 and RFC3704=
?
>>
>> Yes, but how many people actually implement it? :)
>> It is also why I noted that it might be worthwhile repeating it.
>=20
> So, should we make the language wrapping the references to 2827 and 370=
4
> stronger, perhaps saying that operators SHOULD deploy ingress filtering=

> as an appropriate reaction to the threats described in RH0?

IMHO yes. Unfortunately a MUST is too strong, thus a SHOULD would be
perfect. It might just help some operators configure their networks with
uRPF, as they will be looking at the RFC's that describe harmful things
which can happen to their networks, also RH0 has had quite some press
thus people are aware of it.

I don't know what the rest of the WG thinks about this though and this
is what in my opinion would be a good thing to have.

Greets,
 Jeroen


--------------enigACEA1C7499D0A6645438E09E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZwZ+0uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58IyPIAJwK+k2NuOL7mU81fR0EJ3BIUXgh
ngCgqodt+8LnO1/8pMj1bsmOgtvJwA8=
=lx9C
-----END PGP SIGNATURE-----

--------------enigACEA1C7499D0A6645438E09E--


--===============0282893206==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0282893206==--




From ipv6-bounces@ietf.org Wed Jun 13 22:42:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyfHR-00016i-2Q; Wed, 13 Jun 2007 22:41:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyfHP-00016Y-Tt
	for ipv6@ietf.org; Wed, 13 Jun 2007 22:41:47 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyfHP-0000Ny-F9
	for ipv6@ietf.org; Wed, 13 Jun 2007 22:41:47 -0400
Received: from nm-pptp229.isl.rdc.toshiba.co.jp (unknown
	[IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id F206B73020;
	Thu, 14 Jun 2007 11:41:44 +0900 (JST)
Date: Thu, 14 Jun 2007 11:40:19 +0900
Message-ID: <m1y7intg18.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Wed, 13 Jun 2007 04:53:50 -0700,
Thomas Narten <narten@us.ibm.com> wrote:

> > Abstract
> 
> >    The functionality provided by IPv6's Type 0 Routing Header can be
> >    exploited in order to achieve packet amplification for the purposes
> >    of generating denial-of-service traffic.  This document updates the
> >    IPv6 specification to deprecate the use of IPv6 Type 0 Routing
> >    Headers, in the light of the severity of this security concern.
> 
> The "amplification" terminology seems imprecise/wrong. When I think of
> amplification attacks, I think of one packet causing more packets to
> be generated or one packet resulting in a bigger response. I.e., there
> is amplification of the amount of data sent. In case at hand, packets
> are not amplified, they are just routed in a sort of loop. Is there
> more precise terminology that could be used? (Then again, maybe this
> particular terminology is already widely used here.)
> 
> >    The functionality provided by IPv6's Type 0 Routing Header can be
> >    exploited in order to achieve packet amplification for the purposes
> >    of generating denial-of-service traffic.  This document updates the
> 
> Seems like a sentence or two describing the exploitation itself would
> be good. Not a lot of detail, but more than just "it can be
> exploited". (Later, I see that you include such text in the security
> considerations section. I think it should be moved to (or included in)
> the beginning of the document.

To clarify the point: are you suggesting to add this to Abstract or to
Introduction?  I think it's too much for Abstract, but I agree it
would be worth adding to Introduction (in fact, having a mere copy of
Abstract in Introduction isn't really useful).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 03:46:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyk1H-0004iK-C1; Thu, 14 Jun 2007 03:45:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyk1G-0004i6-3i
	for ipv6@ietf.org; Thu, 14 Jun 2007 03:45:26 -0400
Received: from mx1.its.eads.net ([193.56.40.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyk1E-0000EU-Ms
	for ipv6@ietf.org; Thu, 14 Jun 2007 03:45:26 -0400
Received: from fr-gate1.mailhub.intra.corp ([53.154.16.33]) by
	mx1.its.eads.net with Microsoft SMTPSVC(6.0.3790.2499); 
	Thu, 14 Jun 2007 09:42:52 +0200
Received: from sfrsu800.hq.corp ([10.21.8.22]) by fr-gate1.mailhub.intra.corp
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 14 Jun 2007 09:48:12 +0200
Received: from [172.16.23.108] (10.251.5.23 [10.251.5.23]) by gecko.hq.corp
	with SMTP (Microsoft Exchange Internet Mail Service Version
	5.5.2657.72) id MZ202735; Thu, 14 Jun 2007 09:45:50 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-Mailer: Apple Mail (2.752.2)
Content-class: urn:content-classes:message
Date: Thu, 14 Jun 2007 09:45:10 +0200
Message-ID: <728410EA-0E01-4220-93D4-62CB7E6A2318@eads.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
Thread-Index: AceuWAdoFNFWaPIfSYyRu3b/h4is1w==
From: "Ebalard, Arnaud" <Arnaud.Ebalard@eads.net>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
X-OriginalArrivalTime: 14 Jun 2007 07:48:12.0850 (UTC)
	FILETIME=[5C13B920:01C7AE58]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Thomas Narten <narten@us.ibm.com>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Le 13 juin 07 =E0 19:53, R=E9mi Denis-Courmont a =E9crit :

> Le mercredi 13 juin 2007, Thomas Narten a =E9crit :
>> To be clear, if even a small fraction of firewalls get deployed that
>> just block all traffic with a RH, MIPv6 breaks and becomes
>> undeployable in practice. For EVERYONE!
>
> The answer to the upcoming question must be obvious to many people =20
> here,
> but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your
> network, or does it break both Mobile Nodes *AND* Correspondant Nodes?

When acting as a Correspondent Node, you are aware of the CoA and HoA =20
of your peer (MN). Traffic from the CN to the MN is sent to the CoA =20
of your peer (as the destination address in the IPv6 header) and =20
includes a RH2 carrying the HoA (for the last next hop on the MN).

=3D> Blocking RH2 breaks CN function.

When acting as a Mobile Node, your HA will send its Binding =20
Acknowledgements packets to the CoA (Destination field of the IPv6 =20
header) and include a RH2 (carrying the HoA of the MN).

=3D> Blocking RH2 breaks MN function (registration of a new CoA from a =20
foreign network).

> In the poor real world of IT, there are some network administrator =20
> that
> are responsible for the security of their perimeter. There are seldom
> responsible for new technology not working out of the box. It's a
> truth, we'd rather adapt to, if we can.

At the minimum, when implementing a guest IPv6-enabled network, =20
network administrators should have the ability to filter RH2 (and =20
Destination Option headers) selectively (i.e. let them flow) and not =20
passively undergo blind RH killing by their filtering devices.

I'm wondering if it is possible to do that in Cisco (PIX) or Juniper =20
(ScreenOS) based environments ? To what extent ? I'll be interested =20
in some feedback, if someone has (*). This could be a starting point =20
to defined Best Practices and other SHOULD/MUST rules.

Regards,

a+

(*) off-list / somewhere else if you think it's not the right place =20
to discuss that

-- Arnaud Ebalard
EADS Innovation Works - IT Sec Research Engineer
PGP KeyID:047A5026 FingerPrint:47EB85FEB99AAB85FD0946F30255957C047A5026

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 04:59:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HylAP-0002hk-2d; Thu, 14 Jun 2007 04:58:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HylAN-0002hY-HZ
	for ipv6@ietf.org; Thu, 14 Jun 2007 04:58:55 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HylAM-0006vp-34
	for ipv6@ietf.org; Thu, 14 Jun 2007 04:58:55 -0400
Received: by ug-out-1314.google.com with SMTP id j30so1583479ugc
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 01:58:53 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=OhbUGWc3+lGKvck4eeHnFvqk2bnl/wXOq+1RyHdf279p4A59wqSh4TOP5YqA4D1gJ+sGztu/1lzevoJyZUEBNvDnIvhpO4fAmcR/yLdkNhySepYQ4z1+u2wfOfQj/ykn/n3exLN8sqMG4HR22TgX4tt/WApSzbcRf9g67J/auq0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=GFf3VlyhwKmF4CvGmzP9K8CfyBPVNxlxY4i+0PmpIAnPVrscPMWteQiEtfBIZVoYsyyvHzYDgcr6LIl8wFULaszawkrMiZSXGVWICidriIz3ECM2QnlieQJf564dgiaIAvjlZ+rcQSsVkY6f3kUqyV3P5GU2Qam0RP78BuW26Aw=
Received: by 10.66.221.6 with SMTP id t6mr1947763ugg.1181811533371;
	Thu, 14 Jun 2007 01:58:53 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 32sm4271958ugf.2007.06.14.01.58.52
	(version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 01:58:52 -0700 (PDT)
Message-ID: <4671034B.70109@gmail.com>
Date: Thu, 14 Jun 2007 10:58:51 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Joe Abley <jabley@ca.afilias.info>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
In-Reply-To: <65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: Thomas Narten <narten@us.ibm.com>, bob.hinden@nokia.com,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-13 23:37, Joe Abley wrote:
> 
> On 13-Jun-2007, at 10:42, Thomas Narten wrote:
> 
>>>     Firewall policy intended to protect against packets containing RH0
>>>     must be constructed such that routing headers of other types
>>>     are not filtered by default.  Doing so will break other uses of
>>>     the routing headers such as the Routing Header Type 2 used by
>>> Mobile IPv6 [RFC3775] and future
>>>     functionality designed using other routing header types.
>>
>> Could be even stronger. How about:
>>
>>      It must be understood that blocking all traffic with any RH
>>      (rather than restricting blockage only to type 0) has very
>>      serious implications for the deployment of future
>>      technology. Quite simply, if even a small percentage of deployed
>>      firewalls block other types of routing headers by default, it
>>      will become impossible to deploy technologies using a routing
>>      header. MIPv6 [RFCxxx] relies on a type 2 RH. If even a small
>>      fraction of firewalls block MIPv6 traffic, MIPv6 will become
>>      undeployable in practice.
>>
>>      Consequently, firewall policy intended to protect against packets
>>      containing RH0 MUST NOT simply filter all traffic with a routing
>>      header; it must be possible to disable forwarding of type 0
>>      traffic without blocking other types of routing headers. In
>>      addition, the default configuration MUST be to permit forwarding
>>      of traffic using a RH other than 0.
> 
> I'm slightly concerned that such advice flies in the face of 
> conventional advice given to those constructing firewall policy. It is 
> normal practice, I believe, for end-site firewall policy to be deployed 
> based on denying everything by default, and only permitting those 
> packets which are known to correspond to traffic which ought to be 
> permitted. 

Mobile IPv6 ought to be permitted, surely.

> I believe it is generally considered to be good advice to 
> block all "future technology" by default, and to permit it only once the 
> implications of doing so are well-known.

Mobile IPv6 isn't future technology.

    Brian
> 
> Outside end-sites, in the core, dropping packets based on the presence 
> of any type of routing header is clearly a bad idea.
> 
> If we want the advice in this section to be taken seriously, do we need 
> to distinguish between firewall policy in end-sites and packet filters 
> that might be added to core/ISP networks as a mitigation of the specific 
> problems associated with RH0?
> 
> 
> Joe
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 05:21:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HylVv-0002Es-0z; Thu, 14 Jun 2007 05:21:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HylVt-0002AT-Ei
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:21:09 -0400
Received: from mu-out-0910.google.com ([209.85.134.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HylVs-0006jY-4Z
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:21:09 -0400
Received: by mu-out-0910.google.com with SMTP id w8so503009mue
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 02:21:07 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=pkxVOzjcDDYwrwYVh/Gjkk9LvK1lfbSfg/5fdxAesMHk2IDqAdJFuiPFJhZUsQiPbJPlvdQkGAkuoUjCx4dFd9IwX8NPxtSBuO1+U/TDk2Qg3Kklnuox7ESxq2ojGUqPD2e71DBhnCYKYbKliYyGSs2NT+GbEMfq6hymsSw2pe4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=NkT7ow18aHHPZLPb/YI0TU74H5jQnNAK7IM8OddKG3k5FeHm5GAbtTd+SzkuamTlLz/JHlZGn8GlJoIMWYYU0JJmNguKFWORhzCuiQx+sZjoHcRP+4FBc8aRE3j6MNY2lStuNnM/z7Vcqda7R3LrfbrKIkSZtUgTmRkmqi5vJYE=
Received: by 10.82.182.1 with SMTP id e1mr2939895buf.1181812867154;
	Thu, 14 Jun 2007 02:21:07 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 7sm3076621nfv.2007.06.14.02.21.05
	(version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 02:21:06 -0700 (PDT)
Message-ID: <46710880.2000203@gmail.com>
Date: Thu, 14 Jun 2007 11:21:04 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <70672088D7D2CE409FB05DDD7B73D381194F4C@xmb-ams-33c.emea.cisco.com><94420.1181571703@sa.vix.com><15B911E3-8AFE-4269-96E7-83C0D0396EE8@apple.com><466E448B.5050101@gmail.com><99263.1181633228@sa.vix.com><20070612175010.8c512084.ipng@69706e6720323030352d30312d31340a.nosense.org><64527.1181666634@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED876@XCH-NW-7V2.nw.nos.boeing.com>	<83769.1181675992@sa.vix.com>	<CA7D9B4A761066448304A6AFC09ABDA9015AD25F@XCH-NE-1V2.ne.nos.boeing.com>
	<Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-12 22:19, Roger Jorgensen wrote:
> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
> <snip>
>>
>> Is this a little like the RH0 thread? When it was a choice of disabling
>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>> default, but let us use them as we used RFC 1918. It was also my vote
>> when we were discussing site-local.
> 
> Why are we even talking about ULA-C now? What you want is nicely covered 
> by ULA... not ULA-C but regular plain stright forward ULA.

Exactly. If you want some private address space that no ISP will route,
but which you may care to use in your own network or with your
business partners via VPNs, get yourself a ULA, which is self-service.
And do what you need to do in your internal DNS; it will never appear
in the global DNS. (And don't rely on reverse DNS for your internal
operations, but that's a really silly thing to do anyway.)

The *only* possible argument for centrally allocated ULAs is for those
who believe that the birthday paradox in a 2^40 address space causes
a real danger of colliding with another business partner's ULA prefix.
As I've said, we can easily have a robot to take care of that (in fact,
the prototype is up and running, thanks Jeroen).

There seems to be a lot of confusion in part of this discussion. If
a ULA prefix does escape from its intended scope, it will be *exactly*
like any other non-aggregatable prefix that escapes. ULAs don't add to, or
remove from, the difficulties of dealing with non-aggregatable prefixes.

As for what is a site for ULA purposes: it's whatever network(s) decide
to use and route a given ULA prefix. Its boundary is a set of routers
that don't route that prefix further outwards.

     Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 05:33:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyli0-0005NH-M4; Thu, 14 Jun 2007 05:33:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hylhy-0005He-S0
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:33:38 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyleo-0001kG-M2
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:30:26 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181816846; x=1182421646; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=cpN98lWANdNA08
	Y3Ibe59BUlVveMN5TYpBC87kkai3J40xQRH6Q8E4U8wh0Mga9vQsl69Zymbma2Dl
	73RFx5W7jcQ0AUUzxXtpf5EJolC8K0P23Qi/DyMue548GO+tb2u9cyMJ5r3I5czv
	kkgCxZCLb1D67WGEpw7k1gLRqWYnw=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=GYOGDF43RN23LT9TvoyqQN+VJ423aWjUnrPjJnKNBZC9zLDiF+32xa3v+GscBNQKVAp4fUCP09wteAq8PkY/bpQscqBAtcFQDcqh0q8HK/cobGdgoNI7C5zhHbD6LpsZ/Vi76RP6nsdYfc4ZBplN8lZfRe7orPtxVLjrPMcZepY=;
Received: from [10.10.10.50] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002543305.msg
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 11:27:25 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 14 Jun 2007 11:30:14 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C296D746.19E073%jordi.palet@consulintel.es>
Thread-Topic: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
	Assigned ULA draft
Thread-Index: AceuZpyR2thg1RpZEdyUvgAX8sYbNQ==
In-Reply-To: <46710880.2000203@gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070614:ipv6@ietf.org::lSu+KeiXVx7FKgHJ:00003Aaq
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Thu, 14 Jun 2007 11:27:26 +0200
X-MDAV-Processed: consulintel.es, Thu, 14 Jun 2007 11:27:26 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
 Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Operators have said that they will not be able to use ULA, but they could
use ULA-C, for example for thinks like microallocations for internal
infrastructure's.

I think the policy proposal that I sent to several regions includes text and
links to other documents that can clarify this perspective.

For example in RIPE NCC:
http://www.ripe.net/ripe/policies/proposals/2007-05.html

Regards,
Jordi




> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
> Para: Roger Jorgensen <rogerj@jorgensen.no>
> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
> draft
> 
> On 2007-06-12 22:19, Roger Jorgensen wrote:
>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>> <snip>
>>> 
>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>> default, but let us use them as we used RFC 1918. It was also my vote
>>> when we were discussing site-local.
>> 
>> Why are we even talking about ULA-C now? What you want is nicely covered
>> by ULA... not ULA-C but regular plain stright forward ULA.
> 
> Exactly. If you want some private address space that no ISP will route,
> but which you may care to use in your own network or with your
> business partners via VPNs, get yourself a ULA, which is self-service.
> And do what you need to do in your internal DNS; it will never appear
> in the global DNS. (And don't rely on reverse DNS for your internal
> operations, but that's a really silly thing to do anyway.)
> 
> The *only* possible argument for centrally allocated ULAs is for those
> who believe that the birthday paradox in a 2^40 address space causes
> a real danger of colliding with another business partner's ULA prefix.
> As I've said, we can easily have a robot to take care of that (in fact,
> the prototype is up and running, thanks Jeroen).
> 
> There seems to be a lot of confusion in part of this discussion. If
> a ULA prefix does escape from its intended scope, it will be *exactly*
> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
> remove from, the difficulties of dealing with non-aggregatable prefixes.
> 
> As for what is a site for ULA purposes: it's whatever network(s) decide
> to use and route a given ULA prefix. Its boundary is a set of routers
> that don't route that prefix further outwards.
> 
>      Brian
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 05:42:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HylqV-0006Th-Pp; Thu, 14 Jun 2007 05:42:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HylqU-0006TY-D2
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:42:26 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HylqR-0006og-S7
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:42:26 -0400
Received: by ug-out-1314.google.com with SMTP id j30so1594080ugc
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 02:42:23 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=AKn20ykDUFcBOH9L9V++On7jgdXwmLosyeXZBdMZs50YxaJmL3CYPwfzSlWWrp8fpp4hYUwB9XjF5CVzcp6lS26wtgedj9vhVkoNl/Dr/CPcDypRhGVDdi0vZmh0flQf7XyfS0gM5TT8Y6VYcJIiuP+5PQ9Z+SQDpzK7pWcV6Ok=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lMlDGY91VxUEHP3vNdBEDUrmsFPlmvi7i31OatoQCJhZ9CFh8w6F1getvXQ/uI20F93qvOgyrL766eWMg+fZCs/IoYDoU/AIMZvPCyPfRIAp2ShABqFhpHQRAjLpCwBKKFgyNaZsD8nOXpoM2y5bV/gPGJzAs7dImJAArUnb6h0=
Received: by 10.82.108.9 with SMTP id g9mr2988322buc.1181814142906;
	Thu, 14 Jun 2007 02:42:22 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 35sm3618523nfu.2007.06.14.02.42.21
	(version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 02:42:22 -0700 (PDT)
Message-ID: <46710D7C.8020201@gmail.com>
Date: Thu, 14 Jun 2007 11:42:20 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: jordi.palet@consulintel.es
References: <C296D746.19E073%jordi.palet@consulintel.es>
In-Reply-To: <C296D746.19E073%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: ipv6@ietf.org
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned
 ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-14 11:30, JORDI PALET MARTINEZ wrote:
> Operators have said that they will not be able to use ULA, but they could
> use ULA-C, for example for thinks like microallocations for internal
> infrastructure's.

Since there is no practical difference between ULA and ULA-C, they
need to explain...

The argument about private addresses at the end of
http://www.arin.net/policy/proposals/2006_2.html
makes no sense. ULA and ULA-C are both private addresses.

     Brian
> 
> I think the policy proposal that I sent to several regions includes text and
> links to other documents that can clarify this perspective.
> 
> For example in RIPE NCC:
> http://www.ripe.net/ripe/policies/proposals/2007-05.html
> 
> Regards,
> Jordi
> 
> 
> 
> 
>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> Responder a: <ipv6-bounces@ietf.org>
>> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
>> Para: Roger Jorgensen <rogerj@jorgensen.no>
>> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
>> draft
>>
>> On 2007-06-12 22:19, Roger Jorgensen wrote:
>>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>>> <snip>
>>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>>> default, but let us use them as we used RFC 1918. It was also my vote
>>>> when we were discussing site-local.
>>> Why are we even talking about ULA-C now? What you want is nicely covered
>>> by ULA... not ULA-C but regular plain stright forward ULA.
>> Exactly. If you want some private address space that no ISP will route,
>> but which you may care to use in your own network or with your
>> business partners via VPNs, get yourself a ULA, which is self-service.
>> And do what you need to do in your internal DNS; it will never appear
>> in the global DNS. (And don't rely on reverse DNS for your internal
>> operations, but that's a really silly thing to do anyway.)
>>
>> The *only* possible argument for centrally allocated ULAs is for those
>> who believe that the birthday paradox in a 2^40 address space causes
>> a real danger of colliding with another business partner's ULA prefix.
>> As I've said, we can easily have a robot to take care of that (in fact,
>> the prototype is up and running, thanks Jeroen).
>>
>> There seems to be a lot of confusion in part of this discussion. If
>> a ULA prefix does escape from its intended scope, it will be *exactly*
>> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
>> remove from, the difficulties of dealing with non-aggregatable prefixes.
>>
>> As for what is a site for ULA purposes: it's whatever network(s) decide
>> to use and route a given ULA prefix. Its boundary is a set of routers
>> that don't route that prefix further outwards.
>>
>>      Brian
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 
> 
> 
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
> 
> Bye 6Bone. Hi, IPv6 !
> http://www.ipv6day.org
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 05:57:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hym5B-0003ZQ-0F; Thu, 14 Jun 2007 05:57:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hym59-0003Z9-4a
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:57:35 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hym56-0005M3-BX
	for ipv6@ietf.org; Thu, 14 Jun 2007 05:57:35 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181818479; x=1182423279; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=K4pUhzH6lFM9ql
	LADDNwZ2Ab5FvgGcuHkPxaIHYVfN/m+lByX8fSs8H9pYaDOHM6saNnjy8lWgUWuj
	w3aMrJulpyKVeGZ2ucB9wznlFurw+KjC8kJX/xLabfhZvCwiAQWUd/bauxrHj4f7
	lAY/YwAckTFPGa37nfGnWjP8qcn0M=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=UbnTTNUV4Yf2yHxq8cqJcDO6G8QB2Y9NO8Lq0+eQ/WU3FZjhaJd6QNUJIykYLAD+BI1UUirEB9A2X4ep3a4l/BDnTcURCTdI8S/lZp9hmGOTnzuhc+IGdBhfzwK25HgmNfq4cEj2BxN9lIQzjaoD0PcO+Yl+ilQzAo99pkEsZXI=;
Received: from [10.10.10.50] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002543345.msg
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 11:54:36 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 14 Jun 2007 11:56:44 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C296DD7C.19E07D%jordi.palet@consulintel.es>
Thread-Topic: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
	Assigned ULA draft
Thread-Index: AceualBHjtPwtxpdEdyUvgAX8sYbNQ==
In-Reply-To: <46710D7C.8020201@gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070614:ipv6@ietf.org::LjinM1IXKmvbJ/9q:000096KD
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Thu, 14 Jun 2007 11:54:38 +0200
X-MDAV-Processed: consulintel.es, Thu, 14 Jun 2007 11:54:39 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
 Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Just avoiding ANY collision risk. VERY VERY VERY LOW is not enough for them.

Regards,
Jordi




> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Responder a: <brian.e.carpenter@gmail.com>
> Fecha: Thu, 14 Jun 2007 11:42:20 +0200
> Para: <jordi.palet@consulintel.es>
> CC: <ipv6@ietf.org>
> Asunto: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned
> ULA draft
> 
> On 2007-06-14 11:30, JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.
> 
> Since there is no practical difference between ULA and ULA-C, they
> need to explain...
> 
> The argument about private addresses at the end of
> http://www.arin.net/policy/proposals/2006_2.html
> makes no sense. ULA and ULA-C are both private addresses.
> 
>      Brian
>> 
>> I think the policy proposal that I sent to several regions includes text and
>> links to other documents that can clarify this perspective.
>> 
>> For example in RIPE NCC:
>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>> 
>> Regards,
>> Jordi
>> 
>> 
>> 
>> 
>>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>> Responder a: <ipv6-bounces@ietf.org>
>>> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
>>> Para: Roger Jorgensen <rogerj@jorgensen.no>
>>> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
>>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
>>> draft
>>> 
>>> On 2007-06-12 22:19, Roger Jorgensen wrote:
>>>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>>>> <snip>
>>>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>>>> default, but let us use them as we used RFC 1918. It was also my vote
>>>>> when we were discussing site-local.
>>>> Why are we even talking about ULA-C now? What you want is nicely covered
>>>> by ULA... not ULA-C but regular plain stright forward ULA.
>>> Exactly. If you want some private address space that no ISP will route,
>>> but which you may care to use in your own network or with your
>>> business partners via VPNs, get yourself a ULA, which is self-service.
>>> And do what you need to do in your internal DNS; it will never appear
>>> in the global DNS. (And don't rely on reverse DNS for your internal
>>> operations, but that's a really silly thing to do anyway.)
>>> 
>>> The *only* possible argument for centrally allocated ULAs is for those
>>> who believe that the birthday paradox in a 2^40 address space causes
>>> a real danger of colliding with another business partner's ULA prefix.
>>> As I've said, we can easily have a robot to take care of that (in fact,
>>> the prototype is up and running, thanks Jeroen).
>>> 
>>> There seems to be a lot of confusion in part of this discussion. If
>>> a ULA prefix does escape from its intended scope, it will be *exactly*
>>> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
>>> remove from, the difficulties of dealing with non-aggregatable prefixes.
>>> 
>>> As for what is a site for ULA purposes: it's whatever network(s) decide
>>> to use and route a given ULA prefix. Its boundary is a set of routers
>>> that don't route that prefix further outwards.
>>> 
>>>      Brian
>>> 
>>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> 
>> 
>> 
>> 
>> **********************************************
>> The IPv6 Portal: http://www.ipv6tf.org
>> 
>> Bye 6Bone. Hi, IPv6 !
>> http://www.ipv6day.org
>> 
>> This electronic message contains information which may be privileged or
>> confidential. The information is intended to be for the use of the
>> individual(s) named above. If you are not the intended recipient be aware
>> that any disclosure, copying, distribution or use of the contents of this
>> information, including attached files, is prohibited.
>> 
>> 
>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> 




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 06:00:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hym7j-00040x-I3; Thu, 14 Jun 2007 06:00:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hym7h-00040m-UF
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:00:13 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hym7h-0006Sp-8p
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:00:13 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id A903F140C022;
	Thu, 14 Jun 2007 12:00:11 +0200 (CEST)
Message-ID: <467111AB.20203@spaghetti.zurich.ibm.com>
Date: Thu, 14 Jun 2007 11:00:11 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.3) Gecko/20070326 Thunderbird/2.0.0.0 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: jordi.palet@consulintel.es
References: <C296D746.19E073%jordi.palet@consulintel.es>
In-Reply-To: <C296D746.19E073%jordi.palet@consulintel.es>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	"address-policy-wg@ripe.net" <address-policy-wg@ripe.net>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1466883382=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1466883382==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig72AC9AAEC6B2C8AB81AE8A7F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig72AC9AAEC6B2C8AB81AE8A7F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

[cc'ing RIPE address policy + ARIN PPML where the discussion on this
happened, I have not seen any 'operators' who have said the below, if
there are they are there and can thus raise their voices because they
will see this message; removed the silly spam scoring subject...]

JORDI PALET MARTINEZ wrote:
> Operators have said that they will not be able to use ULA, but they cou=
ld
> use ULA-C, for example for thinks like microallocations for internal
> infrastructure's.

I really wonder where you got that idea, as I know of no such operator
who would ever say that. If there are any, let them bring up their
argumentation, please don't come up with "somebody said that" it does
not work that way.

Real network operators, especially involved in the RIPE or other RIR's,
have more than enough address space from their PA allocations that they
can easily receive and they very well know how to use a /48 from that
for internal infrastructure as everybody does this. The IPv6 PA policies
even describe that a /48 can be used per POP of the owner of the PA block=
=2E

Also in the ARIN region any organization can get a /48 PI block for
about $100/year, as such these organizations won't be needing this
address space either as they can easily take a /64 out of that for those
needs. Firewalling is the key here.


> I think the policy proposal that I sent to several regions includes tex=
t and
> links to other documents that can clarify this perspective.
>=20
> For example in RIPE NCC:
> http://www.ripe.net/ripe/policies/proposals/2007-05.html

That is your proposal indeed. No "Operator" has stood behind this and
various people from various organizations have clearly asked you and the
RIPE NCC to *freeze* this proposal till at least the IETF has worked out.=


Anybody needing a "globally unique" block can get either PA or PI space.
ULA-C as such is useless.

Greets,
 Jeroen


--------------enig72AC9AAEC6B2C8AB81AE8A7F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZxEasuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58IxJdAJoDj7ITRpUJbMd1uzhaCj1607vv
WgCfYftFXNU7EibSWetPAcpokB6eVk0=
=sIk+
-----END PGP SIGNATURE-----

--------------enig72AC9AAEC6B2C8AB81AE8A7F--


--===============1466883382==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1466883382==--




From ipv6-bounces@ietf.org Thu Jun 14 06:32:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hymcy-00025V-Gi; Thu, 14 Jun 2007 06:32:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hymcw-00025I-Hy
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:32:30 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hymcv-00004x-3K
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:32:30 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5EAWJkx026330
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 12:32:19 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5EAWJnU032745; Thu, 14 Jun 2007 12:32:19 +0200
Date: Thu, 14 Jun 2007 12:32:18 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <467111AB.20203@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0706141230510.28555@chandra.student.uit.no>
References: <C296D746.19E073%jordi.palet@consulintel.es>
	<467111AB.20203@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	"address-policy-wg@ripe.net" <address-policy-wg@ripe.net>,
	jordi.palet@consulintel.es
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 14 Jun 2007, Jeroen Massar wrote:
<snip>
> JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.

what operators? I cant remember to have seen one operator supporting that 
point of view. My point of view from a LIR/network point of view etc was 
that ULA-C could be usefull but without reverse DNS it is useless. Maybe 
even with reverse DNS we want todo it the correct way by using our 
netblock we got from RIPE.



-- 


------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 06:35:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HymfY-00037a-5I; Thu, 14 Jun 2007 06:35:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HymfX-00037S-6W
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:35:11 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HymfW-0000n2-Au
	for ipv6@ietf.org; Thu, 14 Jun 2007 06:35:11 -0400
Received: by ug-out-1314.google.com with SMTP id j30so1607486ugc
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 03:35:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=Rtbx2DYRzdw0hzaBoYWmYkOIm4+xm6OWC4XI4fkGG7ePv54fjDVeGWfq/xGSqqQiev2S+yaQiB/G4MbzXmkD1Jeu4/TrWzDW66V6rTIg9I+5rYpVSWmmlpqdHNnyiq+UVcDlAsY1SsWN0Fc6V+QvtSrgCj+zymV0i/rIwODrz1A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=t9f3KvvIDOfHF80sJDmlD9HKOFwVTvrF/Eyl+tUrIyjGJoC29KraR7OR//bFF88bLNd+OR8YNMajaP3aA14Nd8B5prz7QU2q5RJuufVtooTN5492ZyB1GM/0a29oTqs+hZ7m2OdFlUUDwhoF8OL9mFKpa1+nxtdEHf41WUxGRQw=
Received: by 10.66.242.20 with SMTP id p20mr1962246ugh.1181817309540;
	Thu, 14 Jun 2007 03:35:09 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 29sm1960320uga.2007.06.14.03.35.08
	(version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 03:35:08 -0700 (PDT)
Message-ID: <467119DA.3000502@gmail.com>
Date: Thu, 14 Jun 2007 12:35:06 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: jordi.palet@consulintel.es
References: <C296DD7C.19E07D%jordi.palet@consulintel.es>
In-Reply-To: <C296DD7C.19E07D%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: ipv6@ietf.org
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned
 ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-14 11:56, JORDI PALET MARTINEZ wrote:
> Just avoiding ANY collision risk. VERY VERY VERY LOW is not enough for them.

Fine. Then Jeroen's robot is necessary and sufficient.

    Brian
> 
> Regards,
> Jordi
> 
> 
> 
> 
>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> Responder a: <brian.e.carpenter@gmail.com>
>> Fecha: Thu, 14 Jun 2007 11:42:20 +0200
>> Para: <jordi.palet@consulintel.es>
>> CC: <ipv6@ietf.org>
>> Asunto: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned
>> ULA draft
>>
>> On 2007-06-14 11:30, JORDI PALET MARTINEZ wrote:
>>> Operators have said that they will not be able to use ULA, but they could
>>> use ULA-C, for example for thinks like microallocations for internal
>>> infrastructure's.
>> Since there is no practical difference between ULA and ULA-C, they
>> need to explain...
>>
>> The argument about private addresses at the end of
>> http://www.arin.net/policy/proposals/2006_2.html
>> makes no sense. ULA and ULA-C are both private addresses.
>>
>>      Brian
>>> I think the policy proposal that I sent to several regions includes text and
>>> links to other documents that can clarify this perspective.
>>>
>>> For example in RIPE NCC:
>>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>>>
>>> Regards,
>>> Jordi
>>>
>>>
>>>
>>>
>>>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>> Responder a: <ipv6-bounces@ietf.org>
>>>> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
>>>> Para: Roger Jorgensen <rogerj@jorgensen.no>
>>>> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
>>>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
>>>> draft
>>>>
>>>> On 2007-06-12 22:19, Roger Jorgensen wrote:
>>>>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>>>>> <snip>
>>>>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>>>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>>>>> default, but let us use them as we used RFC 1918. It was also my vote
>>>>>> when we were discussing site-local.
>>>>> Why are we even talking about ULA-C now? What you want is nicely covered
>>>>> by ULA... not ULA-C but regular plain stright forward ULA.
>>>> Exactly. If you want some private address space that no ISP will route,
>>>> but which you may care to use in your own network or with your
>>>> business partners via VPNs, get yourself a ULA, which is self-service.
>>>> And do what you need to do in your internal DNS; it will never appear
>>>> in the global DNS. (And don't rely on reverse DNS for your internal
>>>> operations, but that's a really silly thing to do anyway.)
>>>>
>>>> The *only* possible argument for centrally allocated ULAs is for those
>>>> who believe that the birthday paradox in a 2^40 address space causes
>>>> a real danger of colliding with another business partner's ULA prefix.
>>>> As I've said, we can easily have a robot to take care of that (in fact,
>>>> the prototype is up and running, thanks Jeroen).
>>>>
>>>> There seems to be a lot of confusion in part of this discussion. If
>>>> a ULA prefix does escape from its intended scope, it will be *exactly*
>>>> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
>>>> remove from, the difficulties of dealing with non-aggregatable prefixes.
>>>>
>>>> As for what is a site for ULA purposes: it's whatever network(s) decide
>>>> to use and route a given ULA prefix. Its boundary is a set of routers
>>>> that don't route that prefix further outwards.
>>>>
>>>>      Brian
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>> **********************************************
>>> The IPv6 Portal: http://www.ipv6tf.org
>>>
>>> Bye 6Bone. Hi, IPv6 !
>>> http://www.ipv6day.org
>>>
>>> This electronic message contains information which may be privileged or
>>> confidential. The information is intended to be for the use of the
>>> individual(s) named above. If you are not the intended recipient be aware
>>> that any disclosure, copying, distribution or use of the contents of this
>>> information, including attached files, is prohibited.
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
> 
> 
> 
> 
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
> 
> Bye 6Bone. Hi, IPv6 !
> http://www.ipv6day.org
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 11:25:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyrBW-0001O6-L8; Thu, 14 Jun 2007 11:24:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyrBV-0001L0-51
	for ipv6@ietf.org; Thu, 14 Jun 2007 11:24:29 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyrBT-0005bG-Qb
	for ipv6@ietf.org; Thu, 14 Jun 2007 11:24:29 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5EFOQsS019899
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 14 Jun 2007 08:24:26 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5EFOPJq016538; Thu, 14 Jun 2007 08:24:25 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5EFOL9u016399; Thu, 14 Jun 2007 08:24:22 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 11:24:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Jun 2007 11:24:22 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD275@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <46710880.2000203@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AceuZVhRW0cwuYCPTmaEcAN//gEyAAAMPriw
References: <Pine.LNX.4.64.0706122218190.28555@chandra.student.uit.no>
	<46710880.2000203@gmail.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 14 Jun 2007 15:24:22.0141 (UTC)
	FILETIME=[15721AD0:01C7AE98]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20

> The *only* possible argument for centrally allocated ULAs is for those
> who believe that the birthday paradox in a 2^40 address space causes
> a real danger of colliding with another business partner's ULA prefix.
> As I've said, we can easily have a robot to take care of that=20
> (in fact,
> the prototype is up and running, thanks Jeroen).

Here is a quote from an expirted I-D:

http://tools.ietf.org/html/draft-ietf-ipv6-ula-central-01

   The major difference between the locally assigned Unique local
   addresses defined in [ULA] and the centrally assigned local addresses
   defined in this document is that they are uniquely assigned and the
   assignments can be escrowed to resolve any disputes regarding
   duplicate assignments.

   It is expected that large managed sites will prefer central
   assignments and small or disconnected sites will prefer local
   assignments.  It is recommended that sites planning to use Local IPv6
   addresses for extensive inter-site communication, initially or as a
   future possibility, use a centrally assigned prefix as there is no
   possibility of assignment conflicts.  Sites are free to choose either
   approach

The second paragraph is what I'd be most interested in. Not for the
reason cited, but because if I want to configure multiple "sites"
exactly the same, that would seem to be the most direct approach.

I suppose I could also do the standard ULA for one site, then copy those
addresses in the others. Isn't that exactly the same as centrally
administered ULAs?

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 14:09:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HytlN-0000Og-L1; Thu, 14 Jun 2007 14:09:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HytlM-0000OX-9K
	for ipv6@ietf.org; Thu, 14 Jun 2007 14:09:40 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HytlL-0007zm-0T
	for ipv6@ietf.org; Thu, 14 Jun 2007 14:09:40 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id 9FC608D6E16
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 11:08:28 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id EE624100C7
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 11:09:37 -0700 (PDT)
X-AuditID: 11807124-a16c9bb000000801-ae-467184619f5c
Received: from [17.206.23.245] (il0602a-dhcp117.apple.com [17.206.23.245])
	by relay6.apple.com (Apple SCV relay) with ESMTP id E442F1006A
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 11:09:37 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <C296DD7C.19E07D%jordi.palet@consulintel.es>
References: <C296DD7C.19E07D%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <72B4AC1F-9001-4427-88EA-C7DBF158DD4F@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 14 Jun 2007 11:09:33 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
	Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 14, 2007, at 02:56, JORDI PALET MARTINEZ wrote:
>
> Just avoiding ANY collision risk. VERY VERY VERY LOW is not enough  
> for them.

My attitude is that IETF should tell them that's THEIR problem, not  
OURS.  Has the operator community explained why the odds of a  
collision in a 2^40 address space pose an unacceptable risk to them,  
which they can't mitigate without the participation of an Internet  
Society organization?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 14:40:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyuFX-0001jv-5U; Thu, 14 Jun 2007 14:40:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HytAk-0002W5-21
	for ipv6@ietf.org; Thu, 14 Jun 2007 13:31:50 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HytAi-0006xR-OH
	for ipv6@ietf.org; Thu, 14 Jun 2007 13:31:50 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.148703697;
	Thu, 14 Jun 2007 13:36:06 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 14 Jun 2007 13:31:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Jun 2007 13:31:29 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A0272F925@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Revising Centrally Assigned ULA draft
Thread-Index: Aceuawo4SY1ACuGdRwuyC/20zvUPuwAPUZTw
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: "Jeroen Massar" <jeroen@unfix.org>,
	<jordi.palet@consulintel.es>
X-OriginalArrivalTime: 14 Jun 2007 17:31:30.0641 (UTC)
	FILETIME=[D862D410:01C7AEA9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
X-Mailman-Approved-At: Thu, 14 Jun 2007 14:40:50 -0400
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	address-policy-wg@ripe.net
Subject: RE: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I think a point here that needs to be looked at is this:

If ULA-C is addressed by IETF and then in turn we end up with RIR's =
responsible for handing out ULA-C blocks, then those existing policy's =
such as ARIN's NRPM 6.10.2 Microallocations for Internal Infastructure =
should be expired and no longer an active policy. =20

And there are different flavors to the debate of why ULA-C would be =
better than such policy as ARIN's NRPM 6.10.2 Microallocations for =
Internal Infastructure.  Ie Standardization, conservation ect...

Cheers!
Marla Azinger
Frontier Communications


-----Original Message-----
From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
Jeroen Massar
Sent: Thursday, June 14, 2007 3:00 AM
To: jordi.palet@consulintel.es
Cc: ARIN People Posting Mailing List; ipv6@ietf.org;
address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft


[cc'ing RIPE address policy + ARIN PPML where the discussion on this
happened, I have not seen any 'operators' who have said the below, if
there are they are there and can thus raise their voices because they
will see this message; removed the silly spam scoring subject...]

JORDI PALET MARTINEZ wrote:
> Operators have said that they will not be able to use ULA, but they =
could
> use ULA-C, for example for thinks like microallocations for internal
> infrastructure's.

I really wonder where you got that idea, as I know of no such operator
who would ever say that. If there are any, let them bring up their
argumentation, please don't come up with "somebody said that" it does
not work that way.

Real network operators, especially involved in the RIPE or other RIR's,
have more than enough address space from their PA allocations that they
can easily receive and they very well know how to use a /48 from that
for internal infrastructure as everybody does this. The IPv6 PA policies
even describe that a /48 can be used per POP of the owner of the PA =
block.

Also in the ARIN region any organization can get a /48 PI block for
about $100/year, as such these organizations won't be needing this
address space either as they can easily take a /64 out of that for those
needs. Firewalling is the key here.


> I think the policy proposal that I sent to several regions includes =
text and
> links to other documents that can clarify this perspective.
>=20
> For example in RIPE NCC:
> http://www.ripe.net/ripe/policies/proposals/2007-05.html

That is your proposal indeed. No "Operator" has stood behind this and
various people from various organizations have clearly asked you and the
RIPE NCC to *freeze* this proposal till at least the IETF has worked =
out.

Anybody needing a "globally unique" block can get either PA or PI space.
ULA-C as such is useless.

Greets,
 Jeroen


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 20:09:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyzNL-0006Fn-Lf; Thu, 14 Jun 2007 20:09:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyzNK-0006EM-F3
	for ipv6@ietf.org; Thu, 14 Jun 2007 20:09:14 -0400
Received: from e33.co.us.ibm.com ([32.97.110.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyzNK-0007Gj-4k
	for ipv6@ietf.org; Thu, 14 Jun 2007 20:09:14 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5F09Dl4024720
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 20:09:13 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5F09D5c210482 for <ipv6@ietf.org>; Thu, 14 Jun 2007 18:09:13 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5F09C1N010834 for <ipv6@ietf.org>; Thu, 14 Jun 2007 18:09:13 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-194-71.wecm.ibm.com
	[9.67.194.71])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5F09BKa010765
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 18:09:12 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5F099L1014874;
	Thu, 14 Jun 2007 17:09:10 -0700
Message-Id: <200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
To: Joe Abley <jabley@ca.afilias.info>
In-reply-to: <65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
Comments: In-reply-to Joe Abley <jabley@ca.afilias.info>
	message dated "Wed, 13 Jun 2007 14:37:29 -0700."
Date: Thu, 14 Jun 2007 17:09:09 -0700
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: bob.hinden@nokia.com, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I'm slightly concerned that such advice flies in the face of  
> conventional advice given to those constructing firewall policy. It  
> is normal practice, I believe, for end-site firewall policy to be  
> deployed based on denying everything by default, and only permitting  
> those packets which are known to correspond to traffic which ought to  
> be permitted. I believe it is generally considered to be good advice  
> to block all "future technology" by default, and to permit it only  
> once the implications of doing so are well-known.

Understood. So maybe we should just go ahead and deprecate all routing
headers now? Why bother complicating implementations, if in practice,
no one will be able to enable/use such features because there is no
way to get firewall configs updated?

> If we want the advice in this section to be taken seriously, do we  
> need to distinguish between firewall policy in end-sites and packet  
> filters that might be added to core/ISP networks as a mitigation of  
> the specific problems associated with RH0?

We need to assume that other types of routing headers are "safe" to
use, and make sure than any usage actually is safe. If we can't do
that, we might as well just deprecate them all now.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 20:12:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyzQL-0007vv-AB; Thu, 14 Jun 2007 20:12:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyzQJ-0007vq-Cx
	for ipv6@ietf.org; Thu, 14 Jun 2007 20:12:19 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyzQI-0007pj-3Q
	for ipv6@ietf.org; Thu, 14 Jun 2007 20:12:19 -0400
Received: from [199.19.50.232]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HyzSq-0005NE-Rw; Fri, 15 Jun 2007 00:14:57 +0000
In-Reply-To: <200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Thu, 14 Jun 2007 17:11:58 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: bob.hinden@nokia.com, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 14-Jun-2007, at 17:09, Thomas Narten wrote:

>> I'm slightly concerned that such advice flies in the face of
>> conventional advice given to those constructing firewall policy. It
>> is normal practice, I believe, for end-site firewall policy to be
>> deployed based on denying everything by default, and only permitting
>> those packets which are known to correspond to traffic which ought to
>> be permitted. I believe it is generally considered to be good advice
>> to block all "future technology" by default, and to permit it only
>> once the implications of doing so are well-known.
>
> Understood. So maybe we should just go ahead and deprecate all routing
> headers now? Why bother complicating implementations, if in practice,
> no one will be able to enable/use such features because there is no
> way to get firewall configs updated?

I think you are missing my point.


Joe


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 21:28:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz0bX-0002y9-UN; Thu, 14 Jun 2007 21:27:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz0bW-0002xv-1v
	for ipv6@ietf.org; Thu, 14 Jun 2007 21:27:58 -0400
Received: from e32.co.us.ibm.com ([32.97.110.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz0bU-0004Kg-Oz
	for ipv6@ietf.org; Thu, 14 Jun 2007 21:27:58 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e32.co.us.ibm.com (8.12.11.20060308/8.13.8) with ESMTP id
	l5F1N5sv016170 for <ipv6@ietf.org>; Thu, 14 Jun 2007 21:23:05 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5F1RUuX242576 for <ipv6@ietf.org>; Thu, 14 Jun 2007 19:27:40 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5F1RT5G006481 for <ipv6@ietf.org>; Thu, 14 Jun 2007 19:27:29 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-194-71.wecm.ibm.com
	[9.67.194.71])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5F1RS5d006462
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 19:27:29 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5F1RQsl004445;
	Thu, 14 Jun 2007 18:27:26 -0700
Message-Id: <200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
To: Joe Abley <jabley@ca.afilias.info>
In-reply-to: <EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
Comments: In-reply-to Joe Abley <jabley@ca.afilias.info>
	message dated "Thu, 14 Jun 2007 17:11:58 -0700."
Date: Thu, 14 Jun 2007 21:27:26 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: bob.hinden@nokia.com, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I think you are missing my point.

I don't think so (though I may have been overly sarcastic in my
response). I understand that the default security policy/config is
"just say no".

But if we accept that, in this case, then I think the implication
really is we might as well toss out the routing header entirely.

If someone came up with some cool new technology/application, but
deploying it required people to change firewall filters (especially
those they do not have direct control over -- or do not understand how
to update), do you think the new application would ever get deployed?
Its just too hard in practice to make this happen.

It's analogous to the problem of "not deployable" if it doesn't work
through a NAT today.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 21:53:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz104-0006Ri-1R; Thu, 14 Jun 2007 21:53:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz100-00064t-BG
	for ipv6@ietf.org; Thu, 14 Jun 2007 21:53:16 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz0zz-0000C0-2d
	for ipv6@ietf.org; Thu, 14 Jun 2007 21:53:16 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id C645A8DFC85
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 18:52:04 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id A453C1008B
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 18:53:14 -0700 (PDT)
X-AuditID: 11807124-a26cbbb000000801-eb-4671f10aec77
Received: from [17.206.23.245] (il0602a-dhcp117.apple.com [17.206.23.245])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 972BB1006E
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 18:53:14 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 14 Jun 2007 18:53:11 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 14, 2007, at 18:27, Thomas Narten wrote:
>
> I understand that the default security policy/config is "just say no".
>
> But if we accept that, in this case, then I think the implication  
> really is we might as well toss out the routing header entirely.
> [...]

We already did accept that as the Best Current Practice for  
residential IPv6 gateways, c.f. the discussion in the V6OPS working  
group over what eventually went on to become RFC 4864, and which led  
to the formation of the V6CPE Design Team mailing list where I am  
editing a draft that will elaborate on the recommendation for the  
default security policy/config in residential IPv6 gateways that it  
essentially should be "just say no."

I'm not sure I see a good argument for tossing out the routing header  
entirely.  At the moment, our draft recommends only blocking RH0.  It  
does not recommend blocking all routing headers.  Those participants  
with reasonable arguments for recommending that all routing headers  
be blocked should present them.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 14 23:59:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz2xs-0005Uq-C1; Thu, 14 Jun 2007 23:59:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz2xq-0005Ul-5r
	for ipv6@ietf.org; Thu, 14 Jun 2007 23:59:10 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz2xo-0002Qe-Qu
	for ipv6@ietf.org; Thu, 14 Jun 2007 23:59:10 -0400
Received: from [205.205.80.29]
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1Hz30I-0007oG-3i; Fri, 15 Jun 2007 04:01:44 +0000
In-Reply-To: <200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CA4A94EB-93CA-468F-8A10-7FFC8A463886@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Thu, 14 Jun 2007 20:57:00 -0700
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: bob.hinden@nokia.com, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 14-Jun-2007, at 18:27, Thomas Narten wrote:

>> I think you are missing my point.
>
> I don't think so (though I may have been overly sarcastic in my
> response). I understand that the default security policy/config is
> "just say no".

OK, good then. Sorry for mischaracterising your reply.

I think there is a difference between firewalls which:

(a) are applied between private networks and the Internet, which  
might reasonably be expected to have a default policy which says  
"deny everything" and to have exceptions to that rule carefully  
formulated according to known requirements;

(b) are applied in front of somewhat but not entirely public networks  
like wifi hotspots, hotels in order to block known troublesome  
traffic (common windows worm proliferation ports, tcp/25, ICMP, DNS,  
and all kinds of other bad ideas);

(c) are applied in networks which provide internet access as their  
primary business (some of which might be similar to (b) above);

(d) backbone routers, which in times of severe need might be  
configured to drop known-bad traffic (e.g. DDoS mitigation, prolific  
virus outbreaks, etc)

This is not an exhaustive taxonomy. It seems to me that what people  
think of most commonly when they read the word "firewall" is the  
meaning in (a) above, whereas we might reasonably concur that (a)'s  
policy is fine as it is (if they want their users to be able to take  
advantage of MIPv6, presumably they will modify their policy to  
accommodate it). It seems to me that the main places we're anxious  
that people don't get the wrong idea about RHn>0 is (b), (c), (d), etc.

My concern is fundamentally that if we give the appearance of being  
dictatorial greybeards living in ivory towers ("the Internet should  
be open! future technology must be accommodated! NAT is wrong!") then  
we run the risk that the entire document will be ignored by those we  
most hope to educate, who will instead consume soundbites and make  
bad decisions ("IPv6 IS INSECURE!" "HAVE YOU BLOCKED ROUTING HEADERS?  
IF NOT YOU MAY BE AT RISK!").

Perhaps this is a non-issue and I'm out of touch with reality.  
Certainly, I don't hear anybody else sharing my concern, regardless  
of how many times I try to explain it :-)


Joe


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 01:16:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz4Ac-00079r-DX; Fri, 15 Jun 2007 01:16:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz4AZ-00078H-1v
	for ipv6@ietf.org; Fri, 15 Jun 2007 01:16:23 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz4AY-0005aS-IB
	for ipv6@ietf.org; Fri, 15 Jun 2007 01:16:23 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l5F5GEAs012918;
	Fri, 15 Jun 2007 08:16:14 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l5F5GB0a012915;
	Fri, 15 Jun 2007 08:16:12 +0300
Date: Fri, 15 Jun 2007 08:16:11 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Joe Abley <jabley@ca.afilias.info>
In-Reply-To: <CA4A94EB-93CA-468F-8A10-7FFC8A463886@ca.afilias.info>
Message-ID: <Pine.LNX.4.64.0706150806280.12496@netcore.fi>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<CA4A94EB-93CA-468F-8A10-7FFC8A463886@ca.afilias.info>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.90.3/3422/Fri Jun 15 03:34:17 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.9
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 14 Jun 2007, Joe Abley wrote:
>> > I think you are missing my point.
>> 
>> I don't think so (though I may have been overly sarcastic in my
>> response). I understand that the default security policy/config is
>> "just say no".
>
> OK, good then. Sorry for mischaracterising your reply.
>
> I think there is a difference between firewalls which:
...

I'm not sure if the document needs to say much at all about firewalls. 
draft-ietf-v6ops-security-overview-06.txt has already said a lot about 
this (now in RFC-ed queue) and there was significant IESG debate. 
RFC 4890 may also be an interesting precedent here.  Both are 
Informational documents.

But if this document said something, perhaps the best would be to 
recommend operators don't try to filter RH0 in any ACLs or firewalls.

(a) class of networks already de-facto filter it (all RH) so nothing 
is changed.  The rest shouldn't bother because 1) hosts will get 
updated, and 2) ingress filtering will block most of the abuse.

IMHO, it's pointless to try to block RH0 in any firewalls except in 
very well-managed networks.  The more configuration we recommend 
venders to build in or operators to deploy, the more likely it is that 
it breaks something especially given that most firewall/ACL 
implementations have restrictions on which RHs it can see.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 02:46:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz5Yv-0005HP-Eg; Fri, 15 Jun 2007 02:45:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz5Ys-0005GZ-Dh
	for ipv6@ietf.org; Fri, 15 Jun 2007 02:45:34 -0400
Received: from nz-out-0506.google.com ([64.233.162.230])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz5Yr-0006h9-5A
	for ipv6@ietf.org; Fri, 15 Jun 2007 02:45:34 -0400
Received: by nz-out-0506.google.com with SMTP id z31so790311nzd
	for <ipv6@ietf.org>; Thu, 14 Jun 2007 23:45:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=loP1g90lQzw01EGo8FQKrCPuEMvy5j/nDMW+eeI5dpjSN64jmtarBbirbujRoCy57Uls3njEeO5sHFYk4pVz6ElmmGtEByb4F1TXj4VsbpKUBZ9DneLjqYOVVum7+B/7aEyCcvfTioDeqfc93kX4mHDcjXZAoXLbKCztX5YbsIg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=gRwUTKQmbNfOcmDwh29LuC9WIC0bK7mp7blCTAHOz9UJVOwgO6XJUofJ63HIa60o3qhelk9+lXkXTMVbtgrHmfivCqWqlsfaJmpCLO5deMXb2KjokCTPrfHYh34NDFPXj4bRfrg8iFjJIins/X7YBa4Qot0c8Sm8CL7flwbmSO4=
Received: by 10.115.58.1 with SMTP id l1mr2664644wak.1181889932352;
	Thu, 14 Jun 2007 23:45:32 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id m17sm3690528waf.2007.06.14.23.45.31
	(version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 23:45:32 -0700 (PDT)
Message-ID: <46723588.5020600@gmail.com>
Date: Fri, 15 Jun 2007 08:45:28 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
In-Reply-To: <097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-15 03:53, james woodyatt wrote:
> On Jun 14, 2007, at 18:27, Thomas Narten wrote:
>>
>> I understand that the default security policy/config is "just say no".
>>
>> But if we accept that, in this case, then I think the implication 
>> really is we might as well toss out the routing header entirely.
>> [...]
> 
> We already did accept that as the Best Current Practice for residential 
> IPv6 gateways, c.f. the discussion in the V6OPS working group over what 
> eventually went on to become RFC 4864, and which led to the formation of 
> the V6CPE Design Team mailing list where I am editing a draft that will 
> elaborate on the recommendation for the default security policy/config 
> in residential IPv6 gateways that it essentially should be "just say no."
> 
> I'm not sure I see a good argument for tossing out the routing header 
> entirely.  At the moment, our draft recommends only blocking RH0.  It 
> does not recommend blocking all routing headers.  Those participants 
> with reasonable arguments for recommending that all routing headers be 
> blocked should present them.

As I already noted, it makes no sense to block Mobile IPv6 by default,
so it makes no sense to block RH>0 by default. But of course, product
managers don't always apply common sense. There is little the IETF
can do about that except publish guidance, as in the forthcoming CPE
draft.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 02:56:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz5jW-0002sN-Rr; Fri, 15 Jun 2007 02:56:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz5i3-0001Bs-H6
	for ipv6@ietf.org; Fri, 15 Jun 2007 02:55:03 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz5eU-0007Q5-1U
	for ipv6@ietf.org; Fri, 15 Jun 2007 02:51:22 -0400
Received: by poy.chewa.net (Postfix, from userid 33)
	id B3E40967FA; Fri, 15 Jun 2007 08:51:18 +0200 (CEST)
To: Thomas Narten <narten@us.ibm.com>
MIME-Version: 1.0
Date: Fri, 15 Jun 2007 08:51:18 +0200
From: =?UTF-8?Q?R=C3=A9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
In-Reply-To: <200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
References: <200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
Message-ID: <f15aa8b47587dee702050239fe328de8@chewa.net>
X-Sender: rdenis@simphalempin.com
User-Agent: RoundCube Webmail/0.1-rc1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On Thu, 14 Jun 2007 17:09:09 -0700, Thomas Narten <narten@us.ibm.com>=0D
wrote:=0D
>> I'm slightly concerned that such advice flies in the face of=0D
>> conventional advice given to those constructing firewall policy. It=0D
>> is normal practice, I believe, for end-site firewall policy to be=0D
>> deployed based on denying everything by default, and only permitting=0D
>> those packets which are known to correspond to traffic which ought to=0D
>> be permitted. I believe it is generally considered to be good advice=0D
>> to block all "future technology" by default, and to permit it only=0D
>> once the implications of doing so are well-known.=0D
> =0D
> Understood. So maybe we should just go ahead and deprecate all routing=0D
> headers now? Why bother complicating implementations, if in practice,=0D
> no one will be able to enable/use such features because there is no=0D
> way to get firewall configs updated?=0D
=0D
I think the point is, we should stngly emphasis that blocking all RH=0D
kills existing technology (e.g. Mobile IPv6 Correspondant Nodes) than=0D
future technologies. Or better yet, that it kills both.=0D
=0D
Two reasons why blocking RH are bound to convince more people than one.=0D
And it is widely known that "future technology" frightens some firewall=0D
operators (whether that's justified or not is not relevant in this case).=
=0D
=0D
> We need to assume that other types of routing headers are "safe" to=0D
> use, and make sure than any usage actually is safe.=0D
=0D
Yes.=0D
=0D
-- =0D
R=C3=A9mi


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 07:42:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzAC1-0006nf-Bx; Fri, 15 Jun 2007 07:42:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzABx-0006gh-PY
	for ipv6@ietf.org; Fri, 15 Jun 2007 07:42:13 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzABv-0003uy-V6
	for ipv6@ietf.org; Fri, 15 Jun 2007 07:42:13 -0400
Received: from 68-248-62-131.ded.ameritech.net ([68.248.62.131]
	helo=[10.101.0.63])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HzAET-000CV0-OH; Fri, 15 Jun 2007 11:44:50 +0000
In-Reply-To: <72B4AC1F-9001-4427-88EA-C7DBF158DD4F@apple.com>
References: <C296DD7C.19E07D%jordi.palet@consulintel.es>
	<72B4AC1F-9001-4427-88EA-C7DBF158DD4F@apple.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <81A914D8-5BE9-4D6B-B84E-484B76F921CF@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Fri, 15 Jun 2007 07:41:53 -0400
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
	Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 14-Jun-2007, at 14:09, james woodyatt wrote:

> On Jun 14, 2007, at 02:56, JORDI PALET MARTINEZ wrote:
>>
>> Just avoiding ANY collision risk. VERY VERY VERY LOW is not enough  
>> for them.
>
> My attitude is that IETF should tell them that's THEIR problem, not  
> OURS.  Has the operator community explained why the odds of a  
> collision in a 2^40 address space pose an unacceptable risk to  
> them, which they can't mitigate without the participation of an  
> Internet Society organization?

If you're an operator, providing IPv6 access and presumably globally- 
unique, globally-reachable address space to customers, why is it  
necessary to use private address space to number your infrastructure?  
You already have PI address space. Isn't it easier just to assign  
some of that space for internal use (as the harmonised bits of the  
RIR IPv6 allocation policy allows, I think) than to bother with ULA?

With IPv4, motivations of cost/scarcity might induce ISPs to use RFC  
1918 addresses to number interfaces which don't require global  
reachability. Those motivations surely don't exist with IPv6.

Perhaps by "operator" you meant something other than "ISP", Jordi?


Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 08:06:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzAZX-0005jW-1o; Fri, 15 Jun 2007 08:06:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzAZV-0005jR-MG
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:06:33 -0400
Received: from wx-out-0506.google.com ([66.249.82.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzAZT-0000My-Qs
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:06:33 -0400
Received: by wx-out-0506.google.com with SMTP id t5so793778wxc
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 05:06:31 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=rChFai4KhiHJnzsgBvBG87ctUDmq6/nECCpL9t6gXMIJFGTTAU/QCPBSWh7saaIPQO6SVS/cXgjjfrli3k+/Lc92WA/uP9775nw4dvCtB8XhpQRc0qbDFg7UknlNJPHR0oKHr5SvdsHlpYG0NtaMiAZbV8Wc4jKpMmRSgsD22bo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=Cwr1j597zFSDKdkICmZXi7n62612/SSlqJPsAFhjSRzZcAXkrp4yLQqD+m81Xi7DmiAOhKMHnV1P2CX4Kx0CLQbfONnw7aWg+MeZic+UscaAxEc2nHy57/btP0wUF25qtpPbXRkC2X1w2ZUAjasTWLyyBwcZn8sD7XBmhji2xEg=
Received: by 10.90.118.8 with SMTP id q8mr2366266agc.1181909191227;
	Fri, 15 Jun 2007 05:06:31 -0700 (PDT)
Received: from Laptop229 ( [168.143.102.62])
	by mx.google.com with ESMTP id 43sm3539000wri.2007.06.15.05.06.29
	(version=SSLv3 cipher=RC4-MD5); Fri, 15 Jun 2007 05:06:30 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <C296DD7C.19E07D%jordi.palet@consulintel.es>
	<72B4AC1F-9001-4427-88EA-C7DBF158DD4F@apple.com>
In-Reply-To: <72B4AC1F-9001-4427-88EA-C7DBF158DD4F@apple.com>
Date: Fri, 15 Jun 2007 08:05:57 -0400
Message-ID: <008501c7af45$88beac30$9a3c0490$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aceur0yKLXU98InYT6Gspawwzr6H5gAlW3Yw
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>-----Original Message-----
>From: james woodyatt [mailto:jhw@apple.com]
>Sent: Thursday, June 14, 2007 14:10
>To: IETF IPv6 Mailing List
>Subject: Re: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally
>Assigned ULA draft
>
>On Jun 14, 2007, at 02:56, JORDI PALET MARTINEZ wrote:
>>
>> Just avoiding ANY collision risk. VERY VERY VERY LOW is not enough for
>> them.
>
>My attitude is that IETF should tell them that's THEIR problem, not
>OURS.  Has the operator community explained why the odds of a collision
>in a 2^40 address space pose an unacceptable risk to them, which they
>can't mitigate without the participation of an Internet Society
>organization?

If it "isn't our problem" then the original ULA RFC shouldn't have made the
provision at all.
They (correctly, IMHO) did make a provision for globally unique ULAs
(ULA-C), so actually making these usable / real is, in fact, "our problem".



/TJ ... still not fully understanding why all the confusion/debate is going
on about this (or, why it is happening now), and still just adding my ~$.02 


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 08:21:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzAnT-0003Vy-GO; Fri, 15 Jun 2007 08:20:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzAnS-0003Vt-57
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:20:58 -0400
Received: from wr-out-0506.google.com ([64.233.184.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzAnR-0003qA-Tc
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:20:58 -0400
Received: by wr-out-0506.google.com with SMTP id 70so713332wra
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 05:20:57 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=aaOqnJUN4rxU8wlOriNpy/2f9vuB2ll/G7++NS4vl3jB1nzImwXdXae1WwJDnIiHddu8LoHSN+wlVjEMkIbI9fa2WmwNYNSaoA2Z14XpzJ7X66f3vRToBVhnl8ohbIxS/t37skJ+kBxrJKK8RNVafTkdzFz0m1eBZBr+D+OMvPA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=cwwNW7/Yv9N7IoqCI4avkBMGcZN7TmNl0oOfbmJR5gkSc5369MgSGRH8DaQn9fssFwAxH1cK9jaG0eNa9i9iifIL4c/NTMRH40mhNbwcBUnPSegEnQsrD4rx16KdOkE2PXdyqOI8UETjPg6FKMGxohB8DgQ9yAeWwX9jaZrpR6k=
Received: by 10.90.113.18 with SMTP id l18mr2379536agc.1181910057689;
	Fri, 15 Jun 2007 05:20:57 -0700 (PDT)
Received: from Laptop229 ( [168.143.102.62])
	by mx.google.com with ESMTP id 44sm3545297wri.2007.06.15.05.20.56
	(version=SSLv3 cipher=RC4-MD5); Fri, 15 Jun 2007 05:20:56 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
In-Reply-To: <097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
Date: Fri, 15 Jun 2007 08:20:24 -0400
Message-ID: <009401c7af47$8d4d9840$a7e8c8c0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Aceu7/e78431VLI3Rx20orYVfwakZwAVtaOA
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


>-----Original Message-----
>From: james woodyatt [mailto:jhw@apple.com]
>Sent: Thursday, June 14, 2007 21:53
>To: IETF IPv6 Mailing List
>Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
>
>On Jun 14, 2007, at 18:27, Thomas Narten wrote:
>>
>> I understand that the default security policy/config is "just say no".
>>
>> But if we accept that, in this case, then I think the implication
>> really is we might as well toss out the routing header entirely.
>> [...]
>
>We already did accept that as the Best Current Practice for residential
>IPv6 gateways, c.f. the discussion in the V6OPS working group over what
>eventually went on to become RFC 4864, and which led to the formation of
>the V6CPE Design Team mailing list where I am editing a draft that will
>elaborate on the recommendation for the default security policy/config
>in residential IPv6 gateways that it essentially should be "just say
>no."
>
>I'm not sure I see a good argument for tossing out the routing header
>entirely.  At the moment, our draft recommends only blocking RH0.  It
>does not recommend blocking all routing headers.  Those participants
>with reasonable arguments for recommending that all routing headers be
>blocked should present them.


For clarification - let's say we have a device that can filter based on the
presence of a routing header, but cannot be more granular and filter based
on what type of routing header it is.
	Is the recommendation be to "fail closed" - block all RHs, including
Type2, thus breaking Route Optimization?
	Or should we "fail open" - permit them, including potentially
malicious Type0s?

I know that to date my recommendation has been to fail closed, block them
all if you can't be more specific ... 



/TJ
(Yes - I agree, the "right" answer is to upgrade to something that can be
more granular ... but work with me for a moment :) )


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 08:27:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzAtI-0004zn-G1; Fri, 15 Jun 2007 08:27:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzAtG-0004zi-QG
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:26:58 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzAtG-0004fm-8N
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:26:58 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 47CC3140C1C1;
	Fri, 15 Jun 2007 14:26:57 +0200 (CEST)
Message-ID: <46728592.1070902@spaghetti.zurich.ibm.com>
Date: Fri, 15 Jun 2007 13:26:58 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: trejrco@gmail.com
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
In-Reply-To: <009401c7af47$8d4d9840$a7e8c8c0$@com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1895423372=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1895423372==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigC5EACDA2588442B40BF2A9AA"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC5EACDA2588442B40BF2A9AA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

TJ wrote:
[..]
> For clarification - let's say we have a device that can filter based on=
 the
> presence of a routing header, but cannot be more granular and filter ba=
sed
> on what type of routing header it is.

Then that device's IPv6 implementation is inherently broken. This, as
with the current standard (before the upcoming deprecation) it should
always process Type 0 headers.

If it is able to process them, then it should not be a difficult feat to
also have it filter it or disable that processing.

Greets,
 Jeroen



--------------enigC5EACDA2588442B40BF2A9AA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZyhZIuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I/juAJ9OLNzUCmeJS4FgqNU4SwTNQtYM
TQCggjxxC/ULmF2xtMoUebe+3MmqBSU=
=DeR+
-----END PGP SIGNATURE-----

--------------enigC5EACDA2588442B40BF2A9AA--


--===============1895423372==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1895423372==--




From ipv6-bounces@ietf.org Fri Jun 15 08:28:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzAv0-0005Qw-7M; Fri, 15 Jun 2007 08:28:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzAuz-0005Qn-0V
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:28:45 -0400
Received: from bacchus.lanetcie.com ([193.30.227.246])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzAux-0004ss-P4
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:28:44 -0400
Received: from localhost (localhost [127.0.0.1])
	by bacchus.lanetcie.com (Postfix) with ESMTP id 16D6D1E98083;
	Fri, 15 Jun 2007 14:28:43 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lanetcie.com
Received: from [?????+?IPv6:::1] (bacchus.lanetcie.com [193.30.227.246])
	by bacchus.lanetcie.com (Postfix) with ESMTP id CD30C1E98047;
	Fri, 15 Jun 2007 14:28:39 +0200 (CEST)
In-Reply-To: <009401c7af47$8d4d9840$a7e8c8c0$@com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <1C424B10-0B7E-45B2-A54D-7FB73CD72701@hongo.wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
From: =?UTF-8?Q?Guillaume_Valadon_/_=E3=82=AE=E3=83=A7=E3=83=BC?=
	=?UTF-8?Q?=E3=83=A0_=E3=83=90=E3=83=A9=E3=83=89=E3=83=B3?=
	<guedou@hongo.wide.ad.jp>
Date: Fri, 15 Jun 2007 14:28:40 +0200
To: trejrco@gmail.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> 	Is the recommendation be to "fail closed" - block all RHs, =
including
> Type2, thus breaking Route Optimization?

If you block all RHs, you break Mobile IPv6 and not only the Route =20
Optimization.
The RH2 is used to *carry* the Binding Acknowledgment from the home =20
agent to the mobile node.

Regarding MIPv6, it is really big issue to block all RH. It seems =20
that some operators are already applying the block all RH policy.

Guillaume

--
Guillaume Valadon / =E3=82=AE=E3=83=A7=E3=83=BC=E3=83=A0 =E3=83=90=E3=83=A9=
=E3=83=89=E3=83=B3
guedou@hongo.wide.ad.jp




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 08:36:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzB2U-00078W-ML; Fri, 15 Jun 2007 08:36:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzB2T-00077j-If
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:36:29 -0400
Received: from wx-out-0506.google.com ([66.249.82.229])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzB2S-00065P-B6
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:36:29 -0400
Received: by wx-out-0506.google.com with SMTP id t5so800728wxc
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 05:36:28 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=YuqDoGWewGlVnmQYwBCwprgciYbAo/Vhq0enfwl1uTuGSuTbeRq86vUbNTkgjJn5HNsKDF5i+wr+XQyMB9i1NSIiRUbT2Xgod7adZ85x69Qq8y/A8fVfHSXMOwUkAf/92maaFkm6ZJeWx4tL/e2x/f5ESagdsQ366kOav1soCRc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:reply-to:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=IN6G6EJcwNHVNw/qOT6NTw8+Y0TDhJatFr/4A/JUBVbGr909JUwPKFwu1zloKLDKfgCuTTPo0dd91blYvK8PRLhq/ch6VMg4Mcprf4u6jcUFWGEkIWy7STjcM3Pt9tEFznuShYN+l4WI/VKyrSdzXdtmg/eD0Z/Rqgh3GsW7Jgw=
Received: by 10.90.27.13 with SMTP id a13mr2387896aga.1181910986829;
	Fri, 15 Jun 2007 05:36:26 -0700 (PDT)
Received: from Laptop229 ( [168.143.102.62])
	by mx.google.com with ESMTP id 11sm4335006wrl.2007.06.15.05.36.24
	(version=SSLv3 cipher=RC4-MD5); Fri, 15 Jun 2007 05:36:25 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
	<1C424B10-0B7E-45B2-A54D-7FB73CD72701@hongo.wide.ad.jp>
In-Reply-To: <1C424B10-0B7E-45B2-A54D-7FB73CD72701@hongo.wide.ad.jp>
Date: Fri, 15 Jun 2007 08:35:52 -0400
Message-ID: <009c01c7af49$b6ed8000$24c88000$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcevSLc7SpGa+C6BRh+dwu2eykatvwAAFhNg
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Excellent point, thank you.

It still begs the question however -=20
If you need to choose either accepting or blocking all routing headers, =
which do you recommend to your (potentially very paranoid, and that =
isn't necessarily bad) clients?

(Yes, still with an emphasis on "the right approach" of doing more =
granular filtering ... but this isn't just a hypothetical situation :))


/TJ


>-----Original Message-----
>From: Guillaume Valadon / =E3=82=AE=E3=83=A7=E3=83=BC=E3=83=A0 =
=E3=83=90=E3=83=A9=E3=83=89=E3=83=B3
>[mailto:guedou@hongo.wide.ad.jp]
>Sent: Friday, June 15, 2007 08:29
>To: trejrco@gmail.com
>Cc: 'IETF IPv6 Mailing List'
>Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
>
>> 	Is the recommendation be to "fail closed" - block all RHs,
>
>If you block all RHs, you break Mobile IPv6 and not only the Route
>Optimization.
>The RH2 is used to *carry* the Binding Acknowledgment from the home
>agent to the mobile node.
>
>Regarding MIPv6, it is really big issue to block all RH. It seems that
>some operators are already applying the block all RH policy.
>
>Guillaume
>
>--
>Guillaume Valadon / =E3=82=AE=E3=83=A7=E3=83=BC=E3=83=A0 =
=E3=83=90=E3=83=A9=E3=83=89=E3=83=B3
>guedou@hongo.wide.ad.jp
>



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 08:54:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzBJf-0000O9-7w; Fri, 15 Jun 2007 08:54:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzBJd-0000NI-Sv
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:54:13 -0400
Received: from bacchus.lanetcie.com ([193.30.227.246])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzBJc-0002ZU-Kv
	for ipv6@ietf.org; Fri, 15 Jun 2007 08:54:13 -0400
Received: from localhost (localhost [127.0.0.1])
	by bacchus.lanetcie.com (Postfix) with ESMTP id 36FAD1E9808A;
	Fri, 15 Jun 2007 14:54:12 +0200 (CEST)
X-Virus-Scanned: amavisd-new at lanetcie.com
Received: from [ZK???+?IPv6:::1] (bacchus.lanetcie.com [193.30.227.246])
	by bacchus.lanetcie.com (Postfix) with ESMTP id DA6AA1E98083;
	Fri, 15 Jun 2007 14:54:08 +0200 (CEST)
In-Reply-To: <009c01c7af49$b6ed8000$24c88000$@com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
	<1C424B10-0B7E-45B2-A54D-7FB73CD72701@hongo.wide.ad.jp>
	<009c01c7af49$b6ed8000$24c88000$@com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <13BA345B-902F-48EB-9A73-7388F7732220@hongo.wide.ad.jp>
Content-Transfer-Encoding: quoted-printable
From: =?UTF-8?Q?Guillaume_Valadon_/_=E3=82=AE=E3=83=A7=E3=83=BC?=
	=?UTF-8?Q?=E3=83=A0_=E3=83=90=E3=83=A9=E3=83=89=E3=83=B3?=
	<guedou@hongo.wide.ad.jp>
Date: Fri, 15 Jun 2007 14:54:09 +0200
To: trejrco@gmail.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 'IETF IPv6 Mailing List' <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> If you need to choose either accepting or blocking all routing =20
> headers, which do you recommend to your (potentially very paranoid, =20=

> and that isn't necessarily bad) clients?

RH2 are harmless and are only supported by Mobile IPv6 aware nodes =20
(Mobile Nodes, and Correspondent Nodes supporting the return =20
routability procedure).
I think that it is not necessary to filter them.

Guillaume

--
Guillaume Valadon / =E3=82=AE=E3=83=A7=E3=83=BC=E3=83=A0 =E3=83=90=E3=83=A9=
=E3=83=89=E3=83=B3
guedou@hongo.wide.ad.jp




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 10:16:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzCao-0006A8-3b; Fri, 15 Jun 2007 10:16:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCam-00069X-0r
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:16:00 -0400
Received: from e2.ny.us.ibm.com ([32.97.182.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCai-0006uK-PY
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:16:00 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e2.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5FEFtXG029060
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:15:55 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5FEFtDI529762 for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:15:55 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5FEFtQ6004824 for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:15:55 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-194-71.wecm.ibm.com
	[9.67.194.71])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5FEFrHZ004790
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 15 Jun 2007 10:15:54 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5FEFpBv025557;
	Fri, 15 Jun 2007 07:15:52 -0700
Message-Id: <200706151415.l5FEFpBv025557@cichlid.raleigh.ibm.com>
To: Joe Abley <jabley@ca.afilias.info>
In-reply-to: <CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
Comments: In-reply-to Joe Abley <jabley@ca.afilias.info>
	message dated "Wed, 13 Jun 2007 06:54:48 -0700."
Date: Fri, 15 Jun 2007 10:15:51 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> How about if I say "traffic amplification over a remote path" instead  
> of "packet amplification"?

wfm.

> > Seems like a sentence or two describing the exploitation itself would
> > be good. Not a lot of detail, but more than just "it can be
> > exploited". (Later, I see that you include such text in the security
> > considerations section. I think it should be moved to (or included in)
> > the beginning of the document.

> Would a forward reference to the Security Considerations section be a  
> reasonable compromise?

IMO, no. The document should flow smoothly to the reader. This belongs
up front, not at the end. IMO.

> >> 8.1.  Normative References
> >
> >
> >>    [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
> >>               April 2006.
> >
> > Shouldn't this  reference be informative?

> The document states that it update RFC4294 in section 1, so I  
> presumed that reference needed to be normative.

Ah, right. OK.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 10:17:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzCbn-0006b4-1t; Fri, 15 Jun 2007 10:17:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCbl-0006aU-Lp
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:17:01 -0400
Received: from e2.ny.us.ibm.com ([32.97.182.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCbk-00075K-0o
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:17:01 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e2.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5FEGxUM031966
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:16:59 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5FEGxM2529852 for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:16:59 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5FEGxel024662 for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:16:59 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-194-71.wecm.ibm.com
	[9.67.194.71])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5FEGwTi024614
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 15 Jun 2007 10:16:58 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5FEGuvK025869;
	Fri, 15 Jun 2007 07:16:57 -0700
Message-Id: <200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
To: =?windows-1252?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
In-reply-to: <200706132053.59897@auguste.remlab.net> 
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<200706132053.59897@auguste.remlab.net>
Comments: In-reply-to =?windows-1252?q?R=E9mi_Denis-Courmont?=
	<rdenis@simphalempin.com>
	message dated "Wed, 13 Jun 2007 20:53:59 +0300."
Date: Fri, 15 Jun 2007 10:16:56 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=?windows-1252?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com> writes:

> Le mercredi 13 juin 2007, Thomas Narten a écrit :
> > To be clear, if even a small fraction of firewalls get deployed that
> > just block all traffic with a RH, MIPv6 breaks and becomes
> > undeployable in practice. For EVERYONE!

> The answer to the upcoming question must be obvious to many people here, 
> but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your 
> network, or does it break both Mobile Nodes *AND* Correspondant
> Nodes?

It breaks mobile nodes. The HA sends traffic to the MN using a type 2
RH header. That is, instead of "tunneling", e.g., via IP in IP, the HA
forwards packets to the MN at its temporary Care-of-Address via a
type 2 RH header. The HA can't communicate with the MN if such traffic
is filtered.

Hence, if such filtering becomes even occasionaly common on the open
Internet, MIPv6 will become unusable/undeployable in practice.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 10:19:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzCdf-0007cU-10; Fri, 15 Jun 2007 10:18:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCdd-0007cD-B9
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:18:57 -0400
Received: from smtpproxy1.mitre.org ([192.160.51.76]
	helo=smtp-bedford.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCda-0007lv-GF
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:18:57 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with SMTP id
	l5FEIsDg017624 for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:18:54 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (Postfix) with ESMTP id 6FD82BF7D
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:18:53 -0400 (EDT)
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5FEIrxn017602; Fri, 15 Jun 2007 10:18:53 -0400
Received: from IMCSRV3.MITRE.ORG ([129.83.20.198]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 15 Jun 2007 10:18:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jun 2007 10:18:52 -0400
Message-ID: <FD7E7B96AFD3DB46AA13B39261A2279401EB0184@IMCSRV3.MITRE.ORG>
In-Reply-To: <200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
Thread-Index: AcevV9u6ybxi5wt8Qs25fWFPudKCrwAAB4rQ
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info><9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com><200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com><200706132053.59897@auguste.remlab.net>
	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
From: "Nour, Nina N." <nnour@mitre.org>
To: "Thomas Narten" <narten@us.ibm.com>,
	=?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
X-OriginalArrivalTime: 15 Jun 2007 14:18:52.0923 (UTC)
	FILETIME=[19DCC4B0:01C7AF58]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I have been trying to unsubscribe from this mailing list
unsuccessfully. Could someone help!

Nina Nour
nnour@mitre.org
=20

-----Original Message-----
From: Thomas Narten [mailto:narten@us.ibm.com]=20
Sent: Friday, June 15, 2007 10:17 AM
To: R=E9mi Denis-Courmont
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01=20

=3D?windows-1252?q?R=3DE9mi_Denis-Courmont?=3D <rdenis@simphalempin.com>
writes:

> Le mercredi 13 juin 2007, Thomas Narten a =C3=A9crit :
> > To be clear, if even a small fraction of firewalls get deployed
that
> > just block all traffic with a RH, MIPv6 breaks and becomes
> > undeployable in practice. For EVERYONE!

> The answer to the upcoming question must be obvious to many people
here,=20
> but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your=20
> network, or does it break both Mobile Nodes *AND* Correspondant
> Nodes?

It breaks mobile nodes. The HA sends traffic to the MN using a type 2
RH header. That is, instead of "tunneling", e.g., via IP in IP, the HA
forwards packets to the MN at its temporary Care-of-Address via a
type 2 RH header. The HA can't communicate with the MN if such traffic
is filtered.

Hence, if such filtering becomes even occasionaly common on the open
Internet, MIPv6 will become unusable/undeployable in practice.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 10:19:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzCe5-0007mv-9t; Fri, 15 Jun 2007 10:19:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzCe3-0007mj-Rn
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:19:23 -0400
Received: from e33.co.us.ibm.com ([32.97.110.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzCe2-0007sE-GD
	for ipv6@ietf.org; Fri, 15 Jun 2007 10:19:23 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5FEJMK4017472
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 10:19:22 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5FEJKiY208424 for <ipv6@ietf.org>; Fri, 15 Jun 2007 08:19:21 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5FEJKlm003585 for <ipv6@ietf.org>; Fri, 15 Jun 2007 08:19:20 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-194-71.wecm.ibm.com
	[9.67.194.71])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5FEJI9w003517
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 15 Jun 2007 08:19:20 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5FEJF7f026533;
	Fri, 15 Jun 2007 07:19:16 -0700
Message-Id: <200706151419.l5FEJF7f026533@cichlid.raleigh.ibm.com>
To: Jeroen Massar <jeroen@unfix.org>
In-reply-to: <467111AB.20203@spaghetti.zurich.ibm.com> 
References: <C296D746.19E073%jordi.palet@consulintel.es>
	<467111AB.20203@spaghetti.zurich.ibm.com>
Comments: In-reply-to Jeroen Massar <jeroen@unfix.org>
	message dated "Thu, 14 Jun 2007 11:00:11 +0100."
Date: Fri, 15 Jun 2007 10:19:15 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	"address-policy-wg@ripe.net" <address-policy-wg@ripe.net>,
	jordi.palet@consulintel.es
Subject: Re: [ppml] Revising Centrally Assigned ULA draft 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar <jeroen@unfix.org> writes:

> JORDI PALET MARTINEZ wrote:
> > Operators have said that they will not be able to use ULA, but they cou=
> ld
> > use ULA-C, for example for thinks like microallocations for internal
> > infrastructure's.

> I really wonder where you got that idea, as I know of no such operator
> who would ever say that. If there are any, let them bring up their
> argumentation, please don't come up with "somebody said that" it does
> not work that way.

Maybe the assertion came from those who supported ARIN Policy Proposal
2006-2: Micro-allocations for Internal Infrastructure
(http://www.arin.net/policy/proposals/2006_2.html), where using a /48
out of their aggregate did not solve the technical problem at hand.

At that time, the question was raised whether ULA-P solved the problem
adequately. The answer I heard was a very clear "no". And ULA-C (if
had existed then) would have.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 12:58:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzF7O-0008Cp-7Q; Fri, 15 Jun 2007 12:57:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzF7M-00087C-R9
	for ipv6@ietf.org; Fri, 15 Jun 2007 12:57:48 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzEsE-0000ty-RZ
	for ipv6@ietf.org; Fri, 15 Jun 2007 12:42:12 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 22547140C00E;
	Fri, 15 Jun 2007 18:42:08 +0200 (CEST)
Message-ID: <4672C15E.4040901@spaghetti.zurich.ibm.com>
Date: Fri, 15 Jun 2007 17:42:06 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Nour, Nina N." <nnour@mitre.org>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info><9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com><200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com><200706132053.59897@auguste.remlab.net>	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
	<FD7E7B96AFD3DB46AA13B39261A2279401EB0184@IMCSRV3.MITRE.ORG>
In-Reply-To: <FD7E7B96AFD3DB46AA13B39261A2279401EB0184@IMCSRV3.MITRE.ORG>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ipv6@ietf.org
Subject: [administra-trivia] how to unsubscribe from IETF mailinglists
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0046316533=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0046316533==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig08935DAFD86D343E319565EF"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig08935DAFD86D343E319565EF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

[excuses for the intermission, but clearly it is time to state it again]

Nour, Nina N. wrote:
> I have been trying to unsubscribe from this mailing list
> unsuccessfully. Could someone help!

For clarity, mainly for people who don't ask and do want to get out:

As described below:
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

As an aside: ipv6-owner@ietf.org can be reached for these and similarily
for other IETF mailinglists: <wg>-ietf@ietf.org.

I'll unsub you in a few moments.

(first have to nullroute the ipv6 address of www1 as something is again
dropping large packets towards me :( )

Greets,
 Jeroen


--------------enig08935DAFD86D343E319565EF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZywWIuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2lyAKCMvEsox4kBUiCEjngks1dAulmm
wACfSXluG64uDXRYmui/9JUmQzx8PPo=
=m4H/
-----END PGP SIGNATURE-----

--------------enig08935DAFD86D343E319565EF--


--===============0046316533==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0046316533==--




From ipv6-bounces@ietf.org Fri Jun 15 14:01:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzG6p-0006A4-2k; Fri, 15 Jun 2007 14:01:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzG6n-00069v-2e
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:01:17 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzG6k-0000cl-NC
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:01:17 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id 3B7608EDB7D
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 11:01:14 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 26B2829C002
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 11:01:14 -0700 (PDT)
X-AuditID: 11807123-9a2cfbb000007975-bb-4672d3ea2926
Received: from [17.219.211.168] (unknown [17.219.211.168])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 13DEC30400B
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 11:01:14 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <009401c7af47$8d4d9840$a7e8c8c0$@com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <79998798-8C43-44B9-A6D2-C17E2F7F5F3A@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Fri, 15 Jun 2007 11:01:12 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 15, 2007, at 05:20, TJ wrote:
>
> For clarification - let's say we have a device that can filter  
> based on the
> presence of a routing header, but cannot be more granular and  
> filter based
> on what type of routing header it is.
> 	Is the recommendation be to "fail closed" - block all RHs, including
> Type2, thus breaking Route Optimization?
> 	Or should we "fail open" - permit them, including potentially
> malicious Type0s?

For my part, I'd rather not try to answer this question.  If pressed,  
I would say that such a device ought not try to be a filter at all.   
If that's not possible, then the device should permit all routing  
headers.  More damage will be done by blocking all routing headers  
than by passing routing headers with type zero through obsolescent  
middleboxes.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 14:57:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzGya-0004qa-Dt; Fri, 15 Jun 2007 14:56:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzGyY-0004qG-Ah
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:56:50 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzGyU-0000gl-Eg
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:56:50 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181933632; x=1182538432; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	CC:Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=cg7k583Xntx3ob
	NOqx9LH9+dIBVnm7piINLgHXAWGkwj78bmH0ZmidzAXjYx9DFD8mTEAN3fDWT2D6
	SY8QcRw1c47y23iubSXRsGVTIRCzloKRv5EEF8TQNy09PVZH42m9ROA2V2kTCjLl
	H9osSD5z7dSyg5qRILFD/a/KIPa4E=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=sJGXCiM7ufdrVZ4piNMDILzJU0xZEkzNp10jUWGSyejpzZkXGxXrmcAxS9TfPO6pu8+7d2kJd4cyC0D6SooPjT+RTKL2czAsoRDXdRupVMmtcbanw85eGxYh0FYhFUJDoXZNRLO/zV2ldoMfWPzd3ifEj9bjvIeVWlp5tu6qbps=;
Received: from [10.0.0.25] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002545786.msg
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 20:53:49 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 15 Jun 2007 15:14:43 +0000
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C2985D63.19E23C%jordi.palet@consulintel.es>
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AcevX+apJULbuBtTEdyO8gAX8sYbNQ==
In-Reply-To: <467111AB.20203@spaghetti.zurich.ibm.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070615:ipv6@ietf.org::fVecef52M4beoEPp:00004yvr
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Fri, 15 Jun 2007 20:53:51 +0200
X-MDAV-Processed: consulintel.es, Fri, 15 Jun 2007 20:53:52 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: ARIN People Posting Mailing List <ppml@arin.net>,
	"address-policy-wg@ripe.net" <address-policy-wg@ripe.net>
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

If you doubt about folks stating anything, then you should read *before*
minutes of meetings. I'm now off-line in a plane, so can't point you to a
specific URL, but this has been said at least in one ARIN meeting.

It has been clear across all this discussion in several exploders, that
there are both opinions, people that want ULA-C and people that don't. What
you need to be smart here is to realize that those than don't want ULA-C
have no any objective reason to oppose to it, because implementing ULA-C has
no negative impact in others. While opposing to it has negative impact to
all: Folks will use global space (PA or PI) for doing the function of ULA-C
an this is a waste, yes a small waste but a waste.

It seems to me irresponsible and unbalanced to do or try things like
changing the HD-ratio or the default assignment size to end-sites because it
is a waste, and then oppose to those that want to have ULA-C, not impacting
in others and avoiding one further small saving in global unicast space.

I'm not trying to convince anyone about supporting ULA-C, because it seems
an impossible mission at least for a few, but at least, don't object to it
if having it doesn't force you in any further implications, which is the
case.

Regards,
Jordi




> De: Jeroen Massar <jeroen@unfix.org>
> Organizaci=F3n: Unfix
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Thu, 14 Jun 2007 11:00:11 +0100
> Para: <jordi.palet@consulintel.es>
> CC: ARIN People Posting Mailing List <ppml@arin.net>, <ipv6@ietf.org>,
> "address-policy-wg@ripe.net" <address-policy-wg@ripe.net>
> Asunto: Re: Revising Centrally Assigned ULA draft
>=20
> [cc'ing RIPE address policy + ARIN PPML where the discussion on this
> happened, I have not seen any 'operators' who have said the below, if
> there are they are there and can thus raise their voices because they
> will see this message; removed the silly spam scoring subject...]
>=20
> JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.
>=20
> I really wonder where you got that idea, as I know of no such operator
> who would ever say that. If there are any, let them bring up their
> argumentation, please don't come up with "somebody said that" it does
> not work that way.
>=20
> Real network operators, especially involved in the RIPE or other RIR's,
> have more than enough address space from their PA allocations that they
> can easily receive and they very well know how to use a /48 from that
> for internal infrastructure as everybody does this. The IPv6 PA policies
> even describe that a /48 can be used per POP of the owner of the PA block.
>=20
> Also in the ARIN region any organization can get a /48 PI block for
> about $100/year, as such these organizations won't be needing this
> address space either as they can easily take a /64 out of that for those
> needs. Firewalling is the key here.
>=20
>=20
>> I think the policy proposal that I sent to several regions includes text and
>> links to other documents that can clarify this perspective.
>>=20
>> For example in RIPE NCC:
>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>=20
> That is your proposal indeed. No "Operator" has stood behind this and
> various people from various organizations have clearly asked you and the
> RIPE NCC to *freeze* this proposal till at least the IETF has worked out.
>=20
> Anybody needing a "globally unique" block can get either PA or PI space.
> ULA-C as such is useless.
>=20
> Greets,
>  Jeroen
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 14:57:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzGyn-0004vN-1j; Fri, 15 Jun 2007 14:57:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzGyl-0004uv-TJ
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:57:03 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzGyk-0000lX-4i
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:57:03 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181933648; x=1182538448; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=QhnmZlTLvDRs/t
	DTsMChCNuZFim2cWXfOCmtEGPUCfzZcE1F2LR6jtEzfcjgNdq5C21rRcMs6DDLpv
	MbE9Knwv0AFjUts0LVHW2jxVfGA26L7I3Er5a03NK/F0arS/6RBRWsmRybGw6wHB
	x8hm+luhBMsVutNujcreVcP2amMX8=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=Iz6QK3rI4n5/J4voiBFYvHeEF9xUkjZlpuz+y2sDlse1mQFMqSMymDA4rBKqb0jVOBUkzQeS+YuCAoj7vhfYi6R+qxTh2EbcvsWEj7sWOdXo8N0W1IhGs1C/VFfppxFJ+W3hM3PRQGsC4UUF/qeHdh91DNwu//gfQ/b8BWTd1bA=;
Received: from [10.0.0.25] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002545790.msg
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 20:54:06 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 15 Jun 2007 15:24:11 +0000
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C2985F9B.19E23F%jordi.palet@consulintel.es>
Thread-Topic: Revising Centrally Assigned ULA draft
Thread-Index: AcevYTk3d4GdxhtUEdyO8gAX8sYbNQ==
In-Reply-To: <46710D7C.8020201@gmail.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070615:ipv6@ietf.org::LMr9Q1CYXuVY8nxp:00004kZr
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Fri, 15 Jun 2007 20:54:08 +0200
X-MDAV-Processed: consulintel.es, Fri, 15 Jun 2007 20:54:08 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

They need a trusted entity running the tool to void any clash chance, that's
one good reason for making it different than ULA.

Regards,
Jordi




> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Thu, 14 Jun 2007 11:42:20 +0200
> Para: <jordi.palet@consulintel.es>
> CC: <ipv6@ietf.org>
> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: [***SPAM*** Score/Req: 10.4/4.5]
> Re: Revising Centrally Assigned ULA draft
> 
> On 2007-06-14 11:30, JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.
> 
> Since there is no practical difference between ULA and ULA-C, they
> need to explain...
> 
> The argument about private addresses at the end of
> http://www.arin.net/policy/proposals/2006_2.html
> makes no sense. ULA and ULA-C are both private addresses.
> 
>      Brian
>> 
>> I think the policy proposal that I sent to several regions includes text and
>> links to other documents that can clarify this perspective.
>> 
>> For example in RIPE NCC:
>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>> 
>> Regards,
>> Jordi
>> 
>> 
>> 
>> 
>>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>> Responder a: <ipv6-bounces@ietf.org>
>>> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
>>> Para: Roger Jorgensen <rogerj@jorgensen.no>
>>> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
>>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
>>> draft
>>> 
>>> On 2007-06-12 22:19, Roger Jorgensen wrote:
>>>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>>>> <snip>
>>>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>>>> default, but let us use them as we used RFC 1918. It was also my vote
>>>>> when we were discussing site-local.
>>>> Why are we even talking about ULA-C now? What you want is nicely covered
>>>> by ULA... not ULA-C but regular plain stright forward ULA.
>>> Exactly. If you want some private address space that no ISP will route,
>>> but which you may care to use in your own network or with your
>>> business partners via VPNs, get yourself a ULA, which is self-service.
>>> And do what you need to do in your internal DNS; it will never appear
>>> in the global DNS. (And don't rely on reverse DNS for your internal
>>> operations, but that's a really silly thing to do anyway.)
>>> 
>>> The *only* possible argument for centrally allocated ULAs is for those
>>> who believe that the birthday paradox in a 2^40 address space causes
>>> a real danger of colliding with another business partner's ULA prefix.
>>> As I've said, we can easily have a robot to take care of that (in fact,
>>> the prototype is up and running, thanks Jeroen).
>>> 
>>> There seems to be a lot of confusion in part of this discussion. If
>>> a ULA prefix does escape from its intended scope, it will be *exactly*
>>> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
>>> remove from, the difficulties of dealing with non-aggregatable prefixes.
>>> 
>>> As for what is a site for ULA purposes: it's whatever network(s) decide
>>> to use and route a given ULA prefix. Its boundary is a set of routers
>>> that don't route that prefix further outwards.
>>> 
>>>      Brian
>>> 
>>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> 
>> 
>> 
>> 
>> **********************************************
>> The IPv6 Portal: http://www.ipv6tf.org
>> 
>> Bye 6Bone. Hi, IPv6 !
>> http://www.ipv6day.org
>> 
>> This electronic message contains information which may be privileged or
>> confidential. The information is intended to be for the use of the
>> individual(s) named above. If you are not the intended recipient be aware
>> that any disclosure, copying, distribution or use of the contents of this
>> information, including attached files, is prohibited.
>> 
>> 
>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 14:57:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzGzI-00051i-W0; Fri, 15 Jun 2007 14:57:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzGzG-000505-Rc
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:57:34 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzGzG-0000o6-8b
	for ipv6@ietf.org; Fri, 15 Jun 2007 14:57:34 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1181933680; x=1182538480; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	CC:Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=Ov7jHSb4TLZF+7
	ID6oY9livKfuUoavNW5lZdfAKLDMoYpljwCIgfej+xAvBKcaeeae5AYVZM2y3FUp
	gt3bv8ye3OwhJUBNBXLhOaYHdCuMh7I0h4OdNi/V+54BNpWtlmk6wckzJkUeJN9T
	jl4lpcoPNcceBGGJwPek0lywk32rM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=shfxsTQJzLj8lgPtt6cjcX5uT2+npdTVqB0KouxZpvniCW8atxrdrluG0FCf/V+AovYPG5W+37RrVZvDMPbTlogZ2eE5gKGHSi8qKI+ujrWRoe6gcesLuc0wEHTPrTNcnx0J80rJAYbg0hsl0ejpVc+CYV6bXspHW6BppcLIDsc=;
Received: from [10.0.0.25] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002545796.msg
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 20:54:38 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Fri, 15 Jun 2007 16:03:25 +0000
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ARIN People Posting Mailing List <ppml@arin.net>
Message-ID: <C29868CD.19E247%jordi.palet@consulintel.es>
Thread-Topic: [ppml] Revising Centrally Assigned ULA draft
Thread-Index: Aceuawo4SY1ACuGdRwuyC/20zvUPuwAPUZTwAC+Y8VQ=
In-Reply-To: <454810F09B5AA04E9D78D13A5C39028A0272F925@nyrofcs2ke2k01.corp.pvt>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070615:ipv6@ietf.org::74HFqutHHJt45OOn:00007XLl
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Fri, 15 Jun 2007 20:54:40 +0200
X-MDAV-Processed: consulintel.es, Fri, 15 Jun 2007 20:54:40 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: ipv6@ietf.org, address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Marla,

In fact, when I started to work on this, it was because I realized about the
possibility to use ULA-C as the space for the microallocations and talking
with different folks they said that it will be possible with ULA-C, but not
ULA.

I also talked with people from the AC and they considered the point (I was
told) to use ULA-C for the microallocations when ULA-C is available.

So my view is that probably the microallocations policy should not expire,
but instead, be modified to make usage of the ULA-C space instead of global
unicast.

Regards,
Jordi




> De: "Azinger, Marla" <marla.azinger@frontiercorp.com>
> Responder a: <marla.azinger@frontiercorp.com>
> Fecha: Thu, 14 Jun 2007 13:31:29 -0400
> Para: Jeroen Massar <jeroen@unfix.org>, <jordi.palet@consulintel.es>
> CC: ARIN People Posting Mailing List <ppml@arin.net>, <ipv6@ietf.org>,
> <address-policy-wg@ripe.net>
> Conversaci=F3n: [ppml] Revising Centrally Assigned ULA draft
> Asunto: RE: [ppml] Revising Centrally Assigned ULA draft
>=20
> I think a point here that needs to be looked at is this:
>=20
> If ULA-C is addressed by IETF and then in turn we end up with RIR's
> responsible for handing out ULA-C blocks, then those existing policy's such as
> ARIN's NRPM 6.10.2 Microallocations for Internal Infastructure should be
> expired and no longer an active policy.
>=20
> And there are different flavors to the debate of why ULA-C would be better
> than such policy as ARIN's NRPM 6.10.2 Microallocations for Internal
> Infastructure.  Ie Standardization, conservation ect...
>=20
> Cheers!
> Marla Azinger
> Frontier Communications
>=20
>=20
> -----Original Message-----
> From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
> Jeroen Massar
> Sent: Thursday, June 14, 2007 3:00 AM
> To: jordi.palet@consulintel.es
> Cc: ARIN People Posting Mailing List; ipv6@ietf.org;
> address-policy-wg@ripe.net
> Subject: Re: [ppml] Revising Centrally Assigned ULA draft
>=20
>=20
> [cc'ing RIPE address policy + ARIN PPML where the discussion on this
> happened, I have not seen any 'operators' who have said the below, if
> there are they are there and can thus raise their voices because they
> will see this message; removed the silly spam scoring subject...]
>=20
> JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.
>=20
> I really wonder where you got that idea, as I know of no such operator
> who would ever say that. If there are any, let them bring up their
> argumentation, please don't come up with "somebody said that" it does
> not work that way.
>=20
> Real network operators, especially involved in the RIPE or other RIR's,
> have more than enough address space from their PA allocations that they
> can easily receive and they very well know how to use a /48 from that
> for internal infrastructure as everybody does this. The IPv6 PA policies
> even describe that a /48 can be used per POP of the owner of the PA block.
>=20
> Also in the ARIN region any organization can get a /48 PI block for
> about $100/year, as such these organizations won't be needing this
> address space either as they can easily take a /64 out of that for those
> needs. Firewalling is the key here.
>=20
>=20
>> I think the policy proposal that I sent to several regions includes text and
>> links to other documents that can clarify this perspective.
>>=20
>> For example in RIPE NCC:
>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>=20
> That is your proposal indeed. No "Operator" has stood behind this and
> various people from various organizations have clearly asked you and the
> RIPE NCC to *freeze* this proposal till at least the IETF has worked out.
>=20
> Anybody needing a "globally unique" block can get either PA or PI space.
> ULA-C as such is useless.
>=20
> Greets,
>  Jeroen
>=20




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 15:30:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzHUQ-0002V6-HZ; Fri, 15 Jun 2007 15:29:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzHGJ-0002bD-4C
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:15:11 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzHGF-0004U3-Iw
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:15:11 -0400
Received: from ([10.160.67.162])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.148826700;
	Fri, 15 Jun 2007 15:19:12 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K05.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 15 Jun 2007 15:14:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jun 2007 15:14:31 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A023EFACB@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Revising Centrally Assigned ULA draft
Thread-Index: Aceuawo4SY1ACuGdRwuyC/20zvUPuwAPUZTwAC+Y8VQABmLHsA==
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: <jordi.palet@consulintel.es>,
	"ARIN People Posting Mailing List" <ppml@arin.net>
X-OriginalArrivalTime: 15 Jun 2007 19:14:33.0691 (UTC)
	FILETIME=[682F22B0:01C7AF81]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
X-Mailman-Approved-At: Fri, 15 Jun 2007 15:29:45 -0400
Cc: ipv6@ietf.org, address-policy-wg@ripe.net
Subject: RE: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jordi-  We are saying the same thing.  Just how you get there is =
different. =20

It is true, we could either modify or eliminate the current ARIN policy =
to work in unison with what might be a finsished RFC on ULA-C.  I just =
believe that sometimes it is easier to start with a fresh policy.  In =
this case, I think it would be less confusing to expire the current =
policy and replace it with a new one that is more fitting as opposed to =
trying to modify the current one. A modification could quickly confuse =
anyone who has not been following all of the ULA emails and =
conversations.

I suppose we can figure this out when we get to that bridge.

Cheers!
Marla Azinger
Frontier Communications
ARIN AC

=20

-----Original Message-----
From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
JORDI PALET MARTINEZ
Sent: Friday, June 15, 2007 9:03 AM
To: ARIN People Posting Mailing List
Cc: ipv6@ietf.org; address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft


Hi Marla,

In fact, when I started to work on this, it was because I realized about =
the
possibility to use ULA-C as the space for the microallocations and =
talking
with different folks they said that it will be possible with ULA-C, but =
not
ULA.

I also talked with people from the AC and they considered the point (I =
was
told) to use ULA-C for the microallocations when ULA-C is available.

So my view is that probably the microallocations policy should not =
expire,
but instead, be modified to make usage of the ULA-C space instead of =
global
unicast.

Regards,
Jordi




> De: "Azinger, Marla" <marla.azinger@frontiercorp.com>
> Responder a: <marla.azinger@frontiercorp.com>
> Fecha: Thu, 14 Jun 2007 13:31:29 -0400
> Para: Jeroen Massar <jeroen@unfix.org>, <jordi.palet@consulintel.es>
> CC: ARIN People Posting Mailing List <ppml@arin.net>, <ipv6@ietf.org>,
> <address-policy-wg@ripe.net>
> Conversaci=F3n: [ppml] Revising Centrally Assigned ULA draft
> Asunto: RE: [ppml] Revising Centrally Assigned ULA draft
>=20
> I think a point here that needs to be looked at is this:
>=20
> If ULA-C is addressed by IETF and then in turn we end up with RIR's
> responsible for handing out ULA-C blocks, then those existing policy's =
such as
> ARIN's NRPM 6.10.2 Microallocations for Internal Infastructure should =
be
> expired and no longer an active policy.
>=20
> And there are different flavors to the debate of why ULA-C would be =
better
> than such policy as ARIN's NRPM 6.10.2 Microallocations for Internal
> Infastructure.  Ie Standardization, conservation ect...
>=20
> Cheers!
> Marla Azinger
> Frontier Communications
>=20
>=20
> -----Original Message-----
> From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
> Jeroen Massar
> Sent: Thursday, June 14, 2007 3:00 AM
> To: jordi.palet@consulintel.es
> Cc: ARIN People Posting Mailing List; ipv6@ietf.org;
> address-policy-wg@ripe.net
> Subject: Re: [ppml] Revising Centrally Assigned ULA draft
>=20
>=20
> [cc'ing RIPE address policy + ARIN PPML where the discussion on this
> happened, I have not seen any 'operators' who have said the below, if
> there are they are there and can thus raise their voices because they
> will see this message; removed the silly spam scoring subject...]
>=20
> JORDI PALET MARTINEZ wrote:
>> Operators have said that they will not be able to use ULA, but they =
could
>> use ULA-C, for example for thinks like microallocations for internal
>> infrastructure's.
>=20
> I really wonder where you got that idea, as I know of no such operator
> who would ever say that. If there are any, let them bring up their
> argumentation, please don't come up with "somebody said that" it does
> not work that way.
>=20
> Real network operators, especially involved in the RIPE or other =
RIR's,
> have more than enough address space from their PA allocations that =
they
> can easily receive and they very well know how to use a /48 from that
> for internal infrastructure as everybody does this. The IPv6 PA =
policies
> even describe that a /48 can be used per POP of the owner of the PA =
block.
>=20
> Also in the ARIN region any organization can get a /48 PI block for
> about $100/year, as such these organizations won't be needing this
> address space either as they can easily take a /64 out of that for =
those
> needs. Firewalling is the key here.
>=20
>=20
>> I think the policy proposal that I sent to several regions includes =
text and
>> links to other documents that can clarify this perspective.
>>=20
>> For example in RIPE NCC:
>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>=20
> That is your proposal indeed. No "Operator" has stood behind this and
> various people from various organizations have clearly asked you and =
the
> RIPE NCC to *freeze* this proposal till at least the IETF has worked =
out.
>=20
> Anybody needing a "globally unique" block can get either PA or PI =
space.
> ULA-C as such is useless.
>=20
> Greets,
>  Jeroen
>=20




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or =
confidential. The information is intended to be for the use of the =
individual(s) named above. If you are not the intended recipient be =
aware that any disclosure, copying, distribution or use of the contents =
of this information, including attached files, is prohibited.



_______________________________________________
This message sent to you through the ARIN Public Policy Mailing List
(PPML@arin.net).
Manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/ppml

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 15:36:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzHb8-0002SW-BW; Fri, 15 Jun 2007 15:36:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzHb6-0002SJ-QL
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:36:40 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzHb4-0000SS-I8
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:36:40 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5FJabkx007362
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 15 Jun 2007 14:36:38 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5FJaaJt027191; Fri, 15 Jun 2007 12:36:37 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5FJaZaU027127; Fri, 15 Jun 2007 12:36:36 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Jun 2007 15:36:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Jun 2007 15:36:34 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD27F@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
Thread-Index: AcevV+HryMqHRcNeRt2QsqG4x3IH6gALBFuw
References: <200706132053.59897@auguste.remlab.net>
	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Thomas Narten" <narten@us.ibm.com>
X-OriginalArrivalTime: 15 Jun 2007 19:36:34.0800 (UTC)
	FILETIME=[7BA05F00:01C7AF84]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-deprecate-rh0-01-candidate-01 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Thomas Narten [mailto:narten@us.ibm.com]=20

> > The answer to the upcoming question must be obvious to many=20
> people here,=20
> > but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your=20
> > network, or does it break both Mobile Nodes *AND* Correspondant
> > Nodes?
>=20
> It breaks mobile nodes. The HA sends traffic to the MN using a type 2
> RH header. That is, instead of "tunneling", e.g., via IP in IP, the HA
> forwards packets to the MN at its temporary Care-of-Address via a
> type 2 RH header. The HA can't communicate with the MN if such traffic
> is filtered.
>=20
> Hence, if such filtering becomes even occasionaly common on the open
> Internet, MIPv6 will become unusable/undeployable in practice.

If you mean ISPs, I agree. If you mean home nets, it doesn't matter so =
much. The home user can simply be informed that mobile IPv6 won't work =
with the default configuration (assuming default blocks all RH > 0 too). =
And he can be told to "check this box if you want to support mobile IP =
in your home network."

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 15 15:41:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzHfM-0005tu-84; Fri, 15 Jun 2007 15:41:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzHfK-0005tl-Ub
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:41:02 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzHfJ-0000z3-KW
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:41:02 -0400
Received: from auguste.remlab.net (unknown
	[IPv6:2002:3e4e:907a:0:20d:60ff:fe38:6d16])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id 73F4C96610;
	Fri, 15 Jun 2007 21:40:56 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: ipv6@ietf.org,
 "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Date: Fri, 15 Jun 2007 22:40:51 +0300
User-Agent: KMail/1.9.7
References: <200706132053.59897@auguste.remlab.net>
	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD27F@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD27F@XCH-NE-1V2.ne.nos.boeing.com>
MIME-Version: 1.0
Message-Id: <200706152240.54445@auguste.remlab.net>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1642088823=="
Errors-To: ipv6-bounces@ietf.org

--===============1642088823==
Content-Type: multipart/signed; boundary="nextPart17132673.Wa8TKNL6YK";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart17132673.Wa8TKNL6YK
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le vendredi 15 juin 2007, Manfredi, Albert E a =E9crit :
> > Hence, if such filtering becomes even occasionaly common on the
> > open Internet, MIPv6 will become unusable/undeployable in practice.
>
> If you mean ISPs, I agree. If you mean home nets, it doesn't matter
> so much. The home user can simply be informed that mobile IPv6 won't
> work with the default configuration (assuming default blocks all RH >
> 0 too). And he can be told to "check this box if you want to support
> mobile IP in your home network."

Well no. The whole point is that if someone else does Mobile IPv6=20
*OUTSIDE* your network, but happens to be willing to contact you, it=20
breaks. Besides, it is well known that most users (and probably even=20
admins) are not capable of making any wise choice on such a technical=20
question.

So MIP6 *will* become undeployable if RH is blocked in even a small=20
portion of the Internet.

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/

--nextPart17132673.Wa8TKNL6YK
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEABECAAYFAkZy60YACgkQw+xtvt1tEr0hgwCfVRLbapk4klqXd2To6T29wT6S
JowAnRacGpEUaXQAWsbaRQCXVe2QuelP
=B5t7
-----END PGP SIGNATURE-----

--nextPart17132673.Wa8TKNL6YK--


--===============1642088823==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1642088823==--




From ipv6-bounces@ietf.org Fri Jun 15 18:49:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzKbq-0006Ps-SL; Fri, 15 Jun 2007 18:49:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzKbp-0006Pn-Uf
	for ipv6@ietf.org; Fri, 15 Jun 2007 18:49:37 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzKbo-0007Td-0f
	for ipv6@ietf.org; Fri, 15 Jun 2007 18:49:37 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1HzKbR-000Lvb-O1; Sat, 16 Jun 2007 08:19:13 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 75E1920133;
	Sat, 16 Jun 2007 08:19:11 +0930 (CST)
Date: Sat, 16 Jun 2007 08:19:11 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Kevin Kargel" <kkargel@polartel.com>
Message-Id: <20070616081911.0f6dcfef.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <70DE64CEFD6E9A4EB7FAF3A06314106670703C@mail>
References: <04576D9D-F221-480C-A38E-421D96C3251E@delong.com>
	<70DE64CEFD6E9A4EB7FAF3A06314106670703C@mail>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: ARIN, People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	Owen DeLong <owen@delong.com>, address-policy-wg@ripe.net,
	jordi.palet@consulintel.es
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, 15 Jun 2007 15:13:40 -0500
"Kevin Kargel" <kkargel@polartel.com> wrote:

> I agree wholeheartedly.  There is nothing you can do with ULA-C that you
> can't do with PI and a minor firewall rule or two.  Leaving the space as
> PI gives it either-or capability, putting it as ULA reduces PI.  (And
> don't talk about 'more PI than we could ever use'..  remember when Mr.
> Gates told us you would never need more than 640K of RAM?)(of course he
> denies it now..)
> 
>  

I understand that that was an IBM design decision - they chose to allow
384KB out of the 1MB of address space of the 8086/8088 for option ROMs
for add-in cards. That decision was made during the design of the
original IBM PC (i.e. the one before the XT), which originally came
with 16KB of RAM (and a audio cassette interface for storage, no serial
ports or printer ports, and a monochrome 4KB text adaptor). Allowing
384KB for option ROMs allowed for plenty of IO card expansion, because
the platform was initially very barebones, and 640KB was extremely
large amount of RAM at the time. The OS at the time didn't
provide device drivers, unlike today's OSes - the option ROMs was were
that functionality resided. When you look at that problem, at the time
it was addressed, the 640KB/384KB boundary seems, at least to me, to be
quite reasonable.

The IBM PC architecture was never expected to (a) set an industry
standard and (b) ever last as long as it has. Gates was unlikely to
have ever been consulted on it, or conversely, was only ever agreeing
with a decision that had already been made.

Don't use this (mis)quote as a lack of design foresight, use it as an
example of wildly unexpected success. IPv6 doesn't have the addressing
quantity constraints that IPv4 has, so allow for wildly different and
expanded uses of it and it's large address space. 

As a general example of how IPv6's "large" addressing
could be used, look at Ethernet. Nobody needs 2^47 unicast addresses on
a LAN segment. We "waste" millions of addresses everytime we enable a
new LAN segment. The Ethernet address space we "waste" when a point to
point ethernet link is brought up is the most "obscene" amount of
address space "waste" I've ever seen in my life - because a
point-to-point link doesn't even need addressing - the frame is either
for this end or the other end.

So what has all that "wasted" Ethernet address space got us ? _Convenience_

It is convenient that we can plug an Ethernet card in and not have to
worry about configuring addresses or addressing collisions.
Non-technical people can buy a network card at the local
electrical store, plug it into their computer, and the ethernet
functionality work (installing device drivers is obviously not a
problem that ethernet attemps to solve). It's the original
"plug-and-play".

With Ethernet, we get a lot of convenience at the cheap price of 32 or
so bits of "wasted" address space (on the rough assumption that nobody
would ever build an ethernet segment with more than 65K nodes), or 64
bits in each packet.

Here's what the people who chose 48 bit addressing for Ethernet said
about the decision :

"48-bit host numbers lead to large Ethernet and internet packets. We
believe that this will not pose a problem as both local and public data
networks continue to offer higher bandwidths at reasonable costs, and
the memory and logic costs associated with storing and processing these
numbers continue to become lower with the advances in LSI technology."
("48-bit Absolute Internet and Ethernet Host Numbers", Yogan K. Dalal
and Robert S. Printis - definately worth a read)

When did they say it ? 1981! 26 years ago!

The problem with applying an IPv4 mentality to an IPv6 addressing
problem is that IPv4 hasn't been an abundant resource for 15 or so
years. We've had to give up operational convenience with it because we
needed to ensure functionality as the Internet grew. When it came to
the crunch, convenience had to be sacrificed.

IPv6 address space is abundant, so we can now go back to placing value on
operational convenience. All we need to do is ensure there isn't any
reckless use of IPv6's address space.

So, getting back to the ULA topic :

If (non-globally routed) PI is the answer to the ULA-C question, is
there going to be enough (non-globally routed) PI so that I can get a
(non-globally routed) PI allocation for my home, at a small charge for
the guaranteed uniqueness e.g. US$10 per annum ? How about my Personal
Area Network that interconnects my mobile phone, portable music player
and pedometer in my shoes. Will there be enough (non-globally routed)
PI that everybody on the planet who might end up having that sort of
PAN can get a (non-globally routed) PI address allocation, should they
want one ? How about if they want separate allocations for both their
PAN and their home network.

If the answer is no, then (non-globally routed) PI it isn't solving the
ULA/ULA-C problem.

> 
> > -----Original Message-----
> > From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net] On 
> > Behalf Of Owen DeLong
> > Sent: Friday, June 15, 2007 2:41 PM
> > To: jordi.palet@consulintel.es
> > Cc: ARIN People Posting Mailing List; ipv6@ietf.org; 
> > address-policy-wg@ripe.net
> > Subject: Re: [ppml] Revising Centrally Assigned ULA draft
> > 
> > 
> > On Jun 15, 2007, at 8:14 AM, JORDI PALET MARTINEZ wrote:
> > 
> > > If you doubt about folks stating anything, then you should read
> > > *before*
> > > minutes of meetings. I'm now off-line in a plane, so can't 
> > point you 
> > > to a specific URL, but this has been said at least in one ARIN 
> > > meeting.
> > >
> > > It has been clear across all this discussion in several exploders, 
> > > that there are both opinions, people that want ULA-C and 
> > people that 
> > > don't. What you need to be smart here is to realize that those than 
> > > don't want ULA-C have no any objective reason to oppose to 
> > it, because 
> > > implementing ULA-C has no negative impact in others. While 
> > opposing to 
> > > it has negative impact to
> > > all: Folks will use global space (PA or PI) for doing the 
> > function of 
> > > ULA-C an this is a waste, yes a small waste but a waste.
> > >
> > Jordi,
> > 	You have this backwards.  Using PI for the purposes of 
> > ULA-C is no waste at all.  Sectioning off a huge chunk of 
> > address space for ULA-C is the waste.
> > If it's all PI, then, it can seamlessly move between being 
> > unrouted or routed as the address-holder sees fit and as 
> > needs change.  If it is set aside as ULA, then, the address 
> > space is forever wasted and cannot (theoretically) be used as 
> > routable space, no matter how little of it is needed for ULA-C.
> > 
> > 	Those of us who oppose ULA-C have what we believe to be 
> > an objective position that it provides no additional benefit 
> > over PI space while simultaneously creating some unnecessary 
> > classification of addresses that makes their status in the 
> > routing table ill-defined at best.  In our opinion, this 
> > carries the potential for significant consequences globally.
> > 
> > 	Just because we do not agree with you does not mean 
> > that our concerns are not legitimate.
> > 
> > 	Do I think UUNET and others should be able to get 
> > secondary microallocations to solve the problem they 
> > presented? Absolutely.  Do I think that we need to set aside 
> > a /8, /12, /16, or whatever separate from the rest of PI 
> > space to do it? No.
> > We should just issue them a /48 or whatever it is they need 
> > from the general pool of available PI space and be done with 
> > it.  No waste at all.  No negative consequences to anyone.  
> > No ambiguous status as to where you can or can't route the 
> > addresses, etc.
> > 
> > Owen
> > 
> > _______________________________________________
> > This message sent to you through the ARIN Public Policy 
> > Mailing List (PPML@arin.net).
> > Manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/ppml
> > 
> _______________________________________________
> This message sent to you through the ARIN Public Policy Mailing List
> (PPML@arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 02:24:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzRhC-0008Pt-82; Sat, 16 Jun 2007 02:23:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzRhA-0008Pm-EJ
	for ipv6@ietf.org; Sat, 16 Jun 2007 02:23:36 -0400
Received: from wa-out-1112.google.com ([209.85.146.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzRh9-0006oe-5p
	for ipv6@ietf.org; Sat, 16 Jun 2007 02:23:36 -0400
Received: by wa-out-1112.google.com with SMTP id j5so1607944wah
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 23:23:34 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=U+2RrKa+RJZJ4wXaAPgaoU5mVzHLPp4V5DHxSvW7MyVGj3DL1ryGgBUzeNKzOZ8lhn/xg99qq9E2eq3FznB/QZY6iFe+pNfU2xoIZw4g0zfpazd8Zxk2fNsTpMq6FRLgthPZZ2o7B9dArlhKXyVvGxvQCjHNbXOLdaLEtuYPRZs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZyKSWM4DyuXHWI1Z+Rxi7EiZf80GAel5SbxXS3Fmcv8f//n8p8x0ujUS0R9KR6Da/QQm0wHEVT0v9zLyNhw7GTmd3PqJB3Z1i5EzxAaEBfcKYllOuY2VCfRW5oT1UxvLFd+FzeQ6snuJrmcEqVEP63P4VdyH2LecDbE7a378Lfk=
Received: by 10.114.112.1 with SMTP id k1mr3903685wac.1181975014543;
	Fri, 15 Jun 2007 23:23:34 -0700 (PDT)
Received: by 10.114.94.12 with HTTP; Fri, 15 Jun 2007 23:23:34 -0700 (PDT)
Message-ID: <75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
Date: Sat, 16 Jun 2007 02:23:34 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "Thomas Narten" <narten@us.ibm.com>
In-Reply-To: <200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 6/14/07, Thomas Narten <narten@us.ibm.com> wrote:

>
> > If we want the advice in this section to be taken seriously, do we
> > need to distinguish between firewall policy in end-sites and packet
> > filters that might be added to core/ISP networks as a mitigation of
> > the specific problems associated with RH0?
>
> We need to assume that other types of routing headers are "safe" to
> use, and make sure than any usage actually is safe. If we can't do
> that, we might as well just deprecate them all now.

I'd actually be a fan of not deprecating the headers in question, but
permitting implementations to either ignore+forward, drop, use them.
So, in the case at hand an operator could decide that 'source routing
is ok' on their network and follow the wishes of the packet creator.
Another may well decide that honoring source-route options (RH0) is
not something they feel comfortable doing, but don't want to discard
the packet out of hand. A third may decide that all source-routing
(RH0) is 'evil' and must be dropped immediately.

This lets the technology be used where appropriate and doesn't do undo
harm because folks can choose to, as adults, handle the traffic
properly for their network/systems.

Is this too heretical to be considered?

-Chris

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 02:38:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzRvH-0003Nx-UA; Sat, 16 Jun 2007 02:38:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzRvF-0003Np-PD
	for ipv6@ietf.org; Sat, 16 Jun 2007 02:38:09 -0400
Received: from wa-out-1112.google.com ([209.85.146.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzRvE-0001j7-HI
	for ipv6@ietf.org; Sat, 16 Jun 2007 02:38:09 -0400
Received: by wa-out-1112.google.com with SMTP id j5so1613833wah
	for <ipv6@ietf.org>; Fri, 15 Jun 2007 23:38:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=HvOVoFiBL1BIPSnjGnDkJVypXGz0T+LW2NIzRSRiITo9qyaPtS6zCH3uAaGYT0YaS15LArxiJ3RP1IyWDYCHVlrUKGGGxKihF7rNogmlCERUT3Wr3CMe5plv2MWjlmfV3iDAGzXxZNBizdRqsXr/CPqGAJ/BeFvYd4WEZRlAA/Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lH/RZtmQQ8YkP+SUusjMDCpWjupUOctGj/8++Ruw4UUZEFc2QY8iKZkBFzFeIUHQylRM1mVv92AwWJnTUDhG3JiG1DEF96YK3/m1FVFzzkykwAU2d+0lFzY+hrrO+nsI+1dvN6IrFNvTSfz5DM2iTns7Ksexc+sNowZcikXmOMA=
Received: by 10.114.78.1 with SMTP id a1mr3863050wab.1181975887948;
	Fri, 15 Jun 2007 23:38:07 -0700 (PDT)
Received: by 10.114.94.12 with HTTP; Fri, 15 Jun 2007 23:38:07 -0700 (PDT)
Message-ID: <75cb24520706152338s216352e7kd0420fc660706b3c@mail.gmail.com>
Date: Sat, 16 Jun 2007 02:38:07 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "james woodyatt" <jhw@apple.com>
In-Reply-To: <79998798-8C43-44B9-A6D2-C17E2F7F5F3A@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<EEBF9ACB-FE98-4CCA-8755-3D8F09721E0E@ca.afilias.info>
	<200706150127.l5F1RQsl004445@cichlid.raleigh.ibm.com>
	<097E18C8-A36E-4E86-8CC5-859DD7672547@apple.com>
	<009401c7af47$8d4d9840$a7e8c8c0$@com>
	<79998798-8C43-44B9-A6D2-C17E2F7F5F3A@apple.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 6/15/07, james woodyatt <jhw@apple.com> wrote:

> For my part, I'd rather not try to answer this question.  If pressed,
> I would say that such a device ought not try to be a filter at all.
> If that's not possible, then the device should permit all routing
> headers.  More damage will be done by blocking all routing headers
> than by passing routing headers with type zero through obsolescent
> middleboxes.

please keep in mind that often there is a cost associated with
handling the RH headers, they must be processed by something 'smart'
in the 'middlebox' (today atleast). Having an option to simply ignore
RH headers (all extension headers maybe?) instead of processing them
seems very nice indeed. Simply throwing away traffic willy-nilly seems
to be a problem, to me atleast.

-Chris

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 05:06:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzUDY-0007r9-6Y; Sat, 16 Jun 2007 05:05:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzHf9-0005X2-QS
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:40:51 -0400
Received: from owen.delong.sj.ca.us ([192.159.10.2] helo=mailhost.delong.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzHf8-0000xs-BL
	for ipv6@ietf.org; Fri, 15 Jun 2007 15:40:51 -0400
Received: from [192.159.10.203] (delong-dhcp3 [192.159.10.203])
	(authenticated bits=0)
	by mailhost.delong.com (8.13.1/8.13.1) with ESMTP id l5FJeVac014108
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 15 Jun 2007 12:40:31 -0700
In-Reply-To: <C2985D63.19E23C%jordi.palet@consulintel.es>
References: <C2985D63.19E23C%jordi.palet@consulintel.es>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <04576D9D-F221-480C-A38E-421D96C3251E@delong.com>
Content-Transfer-Encoding: 7bit
From: Owen DeLong <owen@delong.com>
Date: Fri, 15 Jun 2007 12:40:52 -0700
To: jordi.palet@consulintel.es
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-Mailman-Approved-At: Sat, 16 Jun 2007 05:05:10 -0400
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	"address-policy-wg@ripe.net" <address-policy-wg@ripe.net>
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On Jun 15, 2007, at 8:14 AM, JORDI PALET MARTINEZ wrote:

> If you doubt about folks stating anything, then you should read  
> *before*
> minutes of meetings. I'm now off-line in a plane, so can't point  
> you to a
> specific URL, but this has been said at least in one ARIN meeting.
>
> It has been clear across all this discussion in several exploders,  
> that
> there are both opinions, people that want ULA-C and people that  
> don't. What
> you need to be smart here is to realize that those than don't want  
> ULA-C
> have no any objective reason to oppose to it, because implementing  
> ULA-C has
> no negative impact in others. While opposing to it has negative  
> impact to
> all: Folks will use global space (PA or PI) for doing the function  
> of ULA-C
> an this is a waste, yes a small waste but a waste.
>
Jordi,
	You have this backwards.  Using PI for the purposes of ULA-C is no  
waste
at all.  Sectioning off a huge chunk of address space for ULA-C is  
the waste.
If it's all PI, then, it can seamlessly move between being unrouted  
or routed as
the address-holder sees fit and as needs change.  If it is set aside  
as ULA, then,
the address space is forever wasted and cannot (theoretically) be  
used as
routable space, no matter how little of it is needed for ULA-C.

	Those of us who oppose ULA-C have what we believe to be an objective
position that it provides no additional benefit over PI space while  
simultaneously
creating some unnecessary classification of addresses that makes  
their status
in the routing table ill-defined at best.  In our opinion, this  
carries the potential
for significant consequences globally.

	Just because we do not agree with you does not mean that our concerns
are not legitimate.

	Do I think UUNET and others should be able to get secondary  
microallocations
to solve the problem they presented? Absolutely.  Do I think that we  
need to set
aside a /8, /12, /16, or whatever separate from the rest of PI space  
to do it? No.
We should just issue them a /48 or whatever it is they need from the  
general
pool of available PI space and be done with it.  No waste at all.  No  
negative
consequences to anyone.  No ambiguous status as to where you can or  
can't
route the addresses, etc.

Owen


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 05:06:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzUDZ-0007rR-Fu; Sat, 16 Jun 2007 05:05:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzKkM-0001XU-M1
	for ipv6@ietf.org; Fri, 15 Jun 2007 18:58:26 -0400
Received: from rip.psg.com ([147.28.0.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzKkL-0001iw-EA
	for ipv6@ietf.org; Fri, 15 Jun 2007 18:58:26 -0400
Received: from cust16202.lava.net ([64.65.95.74] helo=[192.168.0.101])
	by rip.psg.com with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.67 (FreeBSD)) (envelope-from <randy@psg.com>)
	id 1HzKkK-000C5U-7i; Fri, 15 Jun 2007 22:58:24 +0000
Message-ID: <46731984.3090708@psg.com>
Date: Fri, 15 Jun 2007 12:58:12 -1000
From: Randy Bush <randy@psg.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <04576D9D-F221-480C-A38E-421D96C3251E@delong.com>	<70DE64CEFD6E9A4EB7FAF3A06314106670703C@mail>
	<20070616081911.0f6dcfef.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <20070616081911.0f6dcfef.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-Mailman-Approved-At: Sat, 16 Jun 2007 05:05:10 -0400
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> If (non-globally routed) PI is the answer to the ULA-C question, is
> there going to be enough (non-globally routed) PI so that I can get a
> (non-globally routed) PI allocation for my home, at a small charge for
> the guaranteed uniqueness e.g. US$10 per annum ? How about my Personal
> Area Network that interconnects my mobile phone, portable music player
> and pedometer in my shoes. Will there be enough (non-globally routed)
> PI that everybody on the planet who might end up having that sort of
> PAN can get a (non-globally routed) PI address allocation, should they
> want one ? How about if they want separate allocations for both their
> PAN and their home network.

these are rir policy and price issues.  they are not technical issues.
except for routability, which, as smb says, don't think you ain't gonna
want to connect it some day; you will.

randy

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 05:06:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzUDY-0007rF-Ub; Sat, 16 Jun 2007 05:05:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzIAx-0002cw-Og
	for ipv6@ietf.org; Fri, 15 Jun 2007 16:13:43 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzIAw-0001mY-AJ
	for ipv6@ietf.org; Fri, 15 Jun 2007 16:13:43 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 15 Jun 2007 15:13:40 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A06314106670703C@mail>
In-Reply-To: <04576D9D-F221-480C-A38E-421D96C3251E@delong.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Revising Centrally Assigned ULA draft
Thread-Index: AcevhSKC5SZXe9u9TG6I31SzYaNHzQAA2gqQ
From: "Kevin Kargel" <kkargel@polartel.com>
To: "Owen DeLong" <owen@delong.com>,
	<jordi.palet@consulintel.es>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-Mailman-Approved-At: Sat, 16 Jun 2007 05:05:10 -0400
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	address-policy-wg@ripe.net
Subject: RE: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I agree wholeheartedly.  There is nothing you can do with ULA-C that you
can't do with PI and a minor firewall rule or two.  Leaving the space as
PI gives it either-or capability, putting it as ULA reduces PI.  (And
don't talk about 'more PI than we could ever use'..  remember when Mr.
Gates told us you would never need more than 640K of RAM?)(of course he
denies it now..)

=20

> -----Original Message-----
> From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net] On=20
> Behalf Of Owen DeLong
> Sent: Friday, June 15, 2007 2:41 PM
> To: jordi.palet@consulintel.es
> Cc: ARIN People Posting Mailing List; ipv6@ietf.org;=20
> address-policy-wg@ripe.net
> Subject: Re: [ppml] Revising Centrally Assigned ULA draft
>=20
>=20
> On Jun 15, 2007, at 8:14 AM, JORDI PALET MARTINEZ wrote:
>=20
> > If you doubt about folks stating anything, then you should read
> > *before*
> > minutes of meetings. I'm now off-line in a plane, so can't=20
> point you=20
> > to a specific URL, but this has been said at least in one ARIN=20
> > meeting.
> >
> > It has been clear across all this discussion in several exploders,=20
> > that there are both opinions, people that want ULA-C and=20
> people that=20
> > don't. What you need to be smart here is to realize that those than=20
> > don't want ULA-C have no any objective reason to oppose to=20
> it, because=20
> > implementing ULA-C has no negative impact in others. While=20
> opposing to=20
> > it has negative impact to
> > all: Folks will use global space (PA or PI) for doing the=20
> function of=20
> > ULA-C an this is a waste, yes a small waste but a waste.
> >
> Jordi,
> 	You have this backwards.  Using PI for the purposes of=20
> ULA-C is no waste at all.  Sectioning off a huge chunk of=20
> address space for ULA-C is the waste.
> If it's all PI, then, it can seamlessly move between being=20
> unrouted or routed as the address-holder sees fit and as=20
> needs change.  If it is set aside as ULA, then, the address=20
> space is forever wasted and cannot (theoretically) be used as=20
> routable space, no matter how little of it is needed for ULA-C.
>=20
> 	Those of us who oppose ULA-C have what we believe to be=20
> an objective position that it provides no additional benefit=20
> over PI space while simultaneously creating some unnecessary=20
> classification of addresses that makes their status in the=20
> routing table ill-defined at best.  In our opinion, this=20
> carries the potential for significant consequences globally.
>=20
> 	Just because we do not agree with you does not mean=20
> that our concerns are not legitimate.
>=20
> 	Do I think UUNET and others should be able to get=20
> secondary microallocations to solve the problem they=20
> presented? Absolutely.  Do I think that we need to set aside=20
> a /8, /12, /16, or whatever separate from the rest of PI=20
> space to do it? No.
> We should just issue them a /48 or whatever it is they need=20
> from the general pool of available PI space and be done with=20
> it.  No waste at all.  No negative consequences to anyone. =20
> No ambiguous status as to where you can or can't route the=20
> addresses, etc.
>=20
> Owen
>=20
> _______________________________________________
> This message sent to you through the ARIN Public Policy=20
> Mailing List (PPML@arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 07:22:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzWM1-0000KW-VO; Sat, 16 Jun 2007 07:22:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzWLz-0000Jk-Ff
	for ipv6@ietf.org; Sat, 16 Jun 2007 07:22:03 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzWLx-0005SI-4l
	for ipv6@ietf.org; Sat, 16 Jun 2007 07:22:03 -0400
Received: from yxu1a22.hopcount.ca ([199.212.90.22])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1HzWOR-0001AE-7U; Sat, 16 Jun 2007 11:24:35 +0000
In-Reply-To: <75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>
	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>
	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <07CB1413-C44F-4D3C-B08F-04C1ACC3E0D2@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Sat, 16 Jun 2007 07:21:38 -0400
To: "Christopher Morrow" <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 16-Jun-2007, at 02:23, Christopher Morrow wrote:

> I'd actually be a fan of not deprecating the headers in question, but
> permitting implementations to either ignore+forward, drop, use them.
> So, in the case at hand an operator could decide that 'source routing
> is ok' on their network and follow the wishes of the packet creator.

The approach that we seem to have consensus to follow is that RH0 has  
practical risks which are too great and hence should be deprecated,  
but that this does not preclude some form of "off-by-default" source  
routing functionality to be defined in future. This new source- 
routing feature presumably would lack some of the features that make  
RH0 particularly potent/dangerous, and be implemented as some other- 
numbered routing header so it can be distinguished from RH0 by  
firewalls.

Some concern has been voiced that if we don't deprecate RH0, and just  
require processing by hosts and routers to be disabled by default,  
some malware or other will just turn it back on.

The following text at the end of section 5 of -01-c-01 refers to this  
approach:

    The severity of the threat is considered to be sufficient to warrant
    deprecation of RH0 entirely.  This has the unfortunate side-effect
    that benign use cases for RH0 are eliminated along with the  
potential
    security hazards; such applications may be facilitated in the future
    by new routing header specifications which do not suffer from RH0's
    problems.

> This lets the technology be used where appropriate and doesn't do undo
> harm because folks can choose to, as adults, handle the traffic
> properly for their network/systems.

The approach above does not preclude that entirely; it's just more  
conservative.


Joe



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 11:00:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzZl8-0006Mn-Lc; Sat, 16 Jun 2007 11:00:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzZl7-0006Md-9J
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:00:13 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzZl4-00073M-EE
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:00:13 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1182009430; x=1182614230; i=jordi.palet@consulintel.es; q=dns;
	h=DomainKey-Signature:Received:User-Agent:Date:Subject:From:To:
	CC:Message-ID:Thread-Topic:Thread-Index:In-Reply-To:Mime-version:
	Content-type:Content-transfer-encoding:Reply-To; b=tV/OtFPAihODlg
	CXs25H9aLj2In/np5djem+w4I3Jv+JX49XaD3fMt2PWGMvZaYlH5geqo9zE7CiD2
	wGwI4Stnj9/NW1fgCXM4uYG4h3K5yXwBhgvW8R2F5ybTJHIfYkjYBwbDWP8EKuLZ
	u0vPlnL/KAbqj3Olvq+8BA84vWESA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=t0jCBbdYtyXvRieXl+hvmgw2MFkD47DVWAxqwc/mzyv404DCODCZbOM4cbel4/dt/V8NQy5iov3skUDivbuuVcSAq8sfGpWELppiO0FiEASqcASmiR3GU1KmflgGuIJm76P8IOvkVPpAZjH8R8TIS2ivGnRfRBZopax8mx4MQbg=;
Received: from [82.206.205.12] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002546284.msg
	for <ipv6@ietf.org>; Sat, 16 Jun 2007 16:57:07 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Sat, 16 Jun 2007 14:38:08 +0000
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: ARIN People Posting Mailing List <ppml@arin.net>
Message-ID: <C299A650.19E44F%jordi.palet@consulintel.es>
Thread-Topic: [ppml] Revising Centrally Assigned ULA draft
Thread-Index: Aceuawo4SY1ACuGdRwuyC/20zvUPuwAPUZTwAC+Y8VQABmLHsAAo7VZJ
In-Reply-To: <454810F09B5AA04E9D78D13A5C39028A023EFACB@nyrofcs2ke2k01.corp.pvt>
Mime-version: 1.0
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:070616:ipv6@ietf.org::dB5HRzyhiHc8BCc3:000007up
X-MDRemoteIP: 82.206.205.12
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.consulintel.es
X-Spam-Status: No, score=-4.7 required=4.5 tests=BAYES_00 autolearn=ham 
	version=3.0.4
X-Spam-Level: 
X-Spam-Processed: consulintel.es, Sat, 16 Jun 2007 16:57:10 +0200
X-MDAV-Processed: consulintel.es, Sat, 16 Jun 2007 16:57:10 +0200
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: ipv6@ietf.org, address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Marla,

Agree, but actually I was wondering, if the AC/board has the power so just
modify the policy in order to use ULA-C space, assuming that when the ULA-C
becomes available, it offers the same features required by this policy. It
may be much easier and faster instead of going thru the PDP all the way. Or
even the staff, because this becomes then only an implementation issue (kind
of "we usedd prefix xx until now, but ULA-C is available and we can use that
space w/o implications on the existing policy itself, same as if we exhaust
the initial prefix for this policy and need to start using a new one").

Anyway is something that could be debated when ULA-C is available :-)

Regards,
Jordi




> De: "Azinger, Marla" <marla.azinger@frontiercorp.com>
> Responder a: <marla.azinger@frontiercorp.com>
> Fecha: Fri, 15 Jun 2007 15:14:31 -0400
> Para: <jordi.palet@consulintel.es>, ARIN People Posting Mailing List
> <ppml@arin.net>
> CC: <ipv6@ietf.org>, <address-policy-wg@ripe.net>
> Conversaci=F3n: [ppml] Revising Centrally Assigned ULA draft
> Asunto: RE: [ppml] Revising Centrally Assigned ULA draft
>=20
> Jordi-  We are saying the same thing.  Just how you get there is different.
>=20
> It is true, we could either modify or eliminate the current ARIN policy to
> work in unison with what might be a finsished RFC on ULA-C.  I just believe
> that sometimes it is easier to start with a fresh policy.  In this case, I
> think it would be less confusing to expire the current policy and replace it
> with a new one that is more fitting as opposed to trying to modify the current
> one. A modification could quickly confuse anyone who has not been following
> all of the ULA emails and conversations.
>=20
> I suppose we can figure this out when we get to that bridge.
>=20
> Cheers!
> Marla Azinger
> Frontier Communications
> ARIN AC
>=20
> =20
>=20
> -----Original Message-----
> From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
> JORDI PALET MARTINEZ
> Sent: Friday, June 15, 2007 9:03 AM
> To: ARIN People Posting Mailing List
> Cc: ipv6@ietf.org; address-policy-wg@ripe.net
> Subject: Re: [ppml] Revising Centrally Assigned ULA draft
>=20
>=20
> Hi Marla,
>=20
> In fact, when I started to work on this, it was because I realized about the
> possibility to use ULA-C as the space for the microallocations and talking
> with different folks they said that it will be possible with ULA-C, but not
> ULA.
>=20
> I also talked with people from the AC and they considered the point (I was
> told) to use ULA-C for the microallocations when ULA-C is available.
>=20
> So my view is that probably the microallocations policy should not expire,
> but instead, be modified to make usage of the ULA-C space instead of global
> unicast.
>=20
> Regards,
> Jordi
>=20
>=20
>=20
>=20
>> De: "Azinger, Marla" <marla.azinger@frontiercorp.com>
>> Responder a: <marla.azinger@frontiercorp.com>
>> Fecha: Thu, 14 Jun 2007 13:31:29 -0400
>> Para: Jeroen Massar <jeroen@unfix.org>, <jordi.palet@consulintel.es>
>> CC: ARIN People Posting Mailing List <ppml@arin.net>, <ipv6@ietf.org>,
>> <address-policy-wg@ripe.net>
>> Conversaci=F3n: [ppml] Revising Centrally Assigned ULA draft
>> Asunto: RE: [ppml] Revising Centrally Assigned ULA draft
>>=20
>> I think a point here that needs to be looked at is this:
>>=20
>> If ULA-C is addressed by IETF and then in turn we end up with RIR's
>> responsible for handing out ULA-C blocks, then those existing policy's such
>> as
>> ARIN's NRPM 6.10.2 Microallocations for Internal Infastructure should be
>> expired and no longer an active policy.
>>=20
>> And there are different flavors to the debate of why ULA-C would be better
>> than such policy as ARIN's NRPM 6.10.2 Microallocations for Internal
>> Infastructure.  Ie Standardization, conservation ect...
>>=20
>> Cheers!
>> Marla Azinger
>> Frontier Communications
>>=20
>>=20
>> -----Original Message-----
>> From: ppml-bounces@arin.net [mailto:ppml-bounces@arin.net]On Behalf Of
>> Jeroen Massar
>> Sent: Thursday, June 14, 2007 3:00 AM
>> To: jordi.palet@consulintel.es
>> Cc: ARIN People Posting Mailing List; ipv6@ietf.org;
>> address-policy-wg@ripe.net
>> Subject: Re: [ppml] Revising Centrally Assigned ULA draft
>>=20
>>=20
>> [cc'ing RIPE address policy + ARIN PPML where the discussion on this
>> happened, I have not seen any 'operators' who have said the below, if
>> there are they are there and can thus raise their voices because they
>> will see this message; removed the silly spam scoring subject...]
>>=20
>> JORDI PALET MARTINEZ wrote:
>>> Operators have said that they will not be able to use ULA, but they could
>>> use ULA-C, for example for thinks like microallocations for internal
>>> infrastructure's.
>>=20
>> I really wonder where you got that idea, as I know of no such operator
>> who would ever say that. If there are any, let them bring up their
>> argumentation, please don't come up with "somebody said that" it does
>> not work that way.
>>=20
>> Real network operators, especially involved in the RIPE or other RIR's,
>> have more than enough address space from their PA allocations that they
>> can easily receive and they very well know how to use a /48 from that
>> for internal infrastructure as everybody does this. The IPv6 PA policies
>> even describe that a /48 can be used per POP of the owner of the PA block.
>>=20
>> Also in the ARIN region any organization can get a /48 PI block for
>> about $100/year, as such these organizations won't be needing this
>> address space either as they can easily take a /64 out of that for those
>> needs. Firewalling is the key here.
>>=20
>>=20
>>> I think the policy proposal that I sent to several regions includes text and
>>> links to other documents that can clarify this perspective.
>>>=20
>>> For example in RIPE NCC:
>>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>>=20
>> That is your proposal indeed. No "Operator" has stood behind this and
>> various people from various organizations have clearly asked you and the
>> RIPE NCC to *freeze* this proposal till at least the IETF has worked out.
>>=20
>> Anybody needing a "globally unique" block can get either PA or PI space.
>> ULA-C as such is useless.
>>=20
>> Greets,
>>  Jeroen
>>=20
>=20
>=20
>=20
>=20
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
>=20
> Bye 6Bone. Hi, IPv6 !
> http://www.ipv6day.org
>=20
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware that
> any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>=20
>=20
>=20
> _______________________________________________
> This message sent to you through the ARIN Public Policy Mailing List
> (PPML@arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 11:24:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hza8T-0000Ju-8B; Sat, 16 Jun 2007 11:24:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hza8S-0000Jp-Nn
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:24:20 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hza8R-0002Py-9Y
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:24:20 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5GFO9IC088164
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 16 Jun 2007 17:24:09 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5GFO8aw001278; Sat, 16 Jun 2007 17:24:08 +0200
Date: Sat, 16 Jun 2007 17:24:08 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
In-Reply-To: <C299A650.19E44F%jordi.palet@consulintel.es>
Message-ID: <Pine.LNX.4.64.0706161723050.28555@chandra.student.uit.no>
References: <C299A650.19E44F%jordi.palet@consulintel.es>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ARIN People Posting Mailing List <ppml@arin.net>, ipv6@ietf.org,
	address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Sat, 16 Jun 2007, JORDI PALET MARTINEZ wrote:
> Anyway is something that could be debated when ULA-C is available :-)

if ULA-C is available... why are you so sure it will go through and be 
accepted?

not many have supported it so far. Some of those in favour have changed 
view, me included.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 11:46:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzaTM-0005gY-B5; Sat, 16 Jun 2007 11:45:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzaTL-0005gS-DJ
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:45:55 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzaTK-00067H-3Q
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:45:55 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 16 Jun 2007 17:45:51 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5GFjpZm004885; 
	Sat, 16 Jun 2007 17:45:51 +0200
Received: from gpk-xdm-001.cisco.com (gpk-xdm-001.cisco.com [64.103.70.176])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5GFjmDR025046; 
	Sat, 16 Jun 2007 15:45:51 GMT
Received: from gpk-xdm-001.cisco.com (localhost.localdomain [127.0.0.1])
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1) with ESMTP id l5GFjmCa022684; 
	Sat, 16 Jun 2007 16:45:48 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l5GFjj2X022683;
	Sat, 16 Jun 2007 16:45:45 +0100
X-Authentication-Warning: gpk-xdm-001.cisco.com: otroan set sender to
	ot@cisco.com using -f
From: Ole Troan <ot@cisco.com>
To: Thomas Narten <narten@us.ibm.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>
	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>
	<200706132053.59897@auguste.remlab.net>
	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
Date: Sat, 16 Jun 2007 16:45:45 +0100
In-Reply-To: <200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com> (Thomas
	Narten's message of "Fri\, 15 Jun 2007 10\:16\:56 -0400")
Message-ID: <7t5r6obnbrq.fsf@gpk-xdm-001.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=932; t=1182008751;
	x=1182872751; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ot@cisco.com;
	z=From:=20Ole=20Troan=20<ot@cisco.com>
	|Subject:=20Re=3A=20draft-ietf-ipv6-deprecate-rh0-01-candidate-01
	|Sender:=20; bh=l4CmDYTwXvrqgkPzudq2QTRuLzMYPmsVpRgxeg8pQBg=;
	b=wLWw840JT5EEhkn9Z4CbPp3h0jrkCbmmUWhMD+qD/x2eyzb12VOD1awyRtDlbfg8zw3yk3QW
	k62ruJWLPgM14YNsz98Okk7w6iaq/r/8yLXwK8bvrqt3e6pgpLmQh5PM;
Authentication-Results: ams-dkim-1; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>> > To be clear, if even a small fraction of firewalls get deployed that
>> > just block all traffic with a RH, MIPv6 breaks and becomes
>> > undeployable in practice. For EVERYONE!
>
>> The answer to the upcoming question must be obvious to many people here, 
>> but anyway not to me: Does blocking RH2 breaks Mobile Nodes in your 
>> network, or does it break both Mobile Nodes *AND* Correspondant
>> Nodes?
>
> It breaks mobile nodes. The HA sends traffic to the MN using a type 2
> RH header. That is, instead of "tunneling", e.g., via IP in IP, the HA
> forwards packets to the MN at its temporary Care-of-Address via a
> type 2 RH header. The HA can't communicate with the MN if such traffic
> is filtered.
>
> Hence, if such filtering becomes even occasionaly common on the open
> Internet, MIPv6 will become unusable/undeployable in practice.

we could fix MIPv6. i.e use IP in IP instead of RH2.

/ot

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 11:57:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzaeX-0007zA-OU; Sat, 16 Jun 2007 11:57:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzaeW-0007z4-B4
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:57:28 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzaeV-0008Dw-0d
	for ipv6@ietf.org; Sat, 16 Jun 2007 11:57:28 -0400
Received: from auguste.remlab.net (unknown
	[IPv6:2002:3e4e:907a:0:20d:60ff:fe38:6d16])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id C72559661F;
	Sat, 16 Jun 2007 17:57:22 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: Ole Troan <ot@cisco.com>
Date: Sat, 16 Jun 2007 18:57:16 +0300
User-Agent: KMail/1.9.7
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>
	<200706151416.l5FEGuvK025869@cichlid.raleigh.ibm.com>
	<7t5r6obnbrq.fsf@gpk-xdm-001.cisco.com>
In-Reply-To: <7t5r6obnbrq.fsf@gpk-xdm-001.cisco.com>
MIME-Version: 1.0
Message-Id: <200706161857.20503@auguste.remlab.net>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Thomas Narten <narten@us.ibm.com>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0764036580=="
Errors-To: ipv6-bounces@ietf.org

--===============0764036580==
Content-Type: multipart/signed; boundary="nextPart2914420.7m0GS377mA";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2914420.7m0GS377mA
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le samedi 16 juin 2007, Ole Troan a =E9crit :
> >> > To be clear, if even a small fraction of firewalls get deployed
> >> > that just block all traffic with a RH, MIPv6 breaks and becomes
> >> > undeployable in practice. For EVERYONE!
> >>
> >> The answer to the upcoming question must be obvious to many people
> >> here, but anyway not to me: Does blocking RH2 breaks Mobile Nodes
> >> in your network, or does it break both Mobile Nodes *AND*
> >> Correspondant Nodes?
> >
> > It breaks mobile nodes. The HA sends traffic to the MN using a type
> > 2 RH header. That is, instead of "tunneling", e.g., via IP in IP,
> > the HA forwards packets to the MN at its temporary Care-of-Address
> > via a type 2 RH header. The HA can't communicate with the MN if
> > such traffic is filtered.
> >
> > Hence, if such filtering becomes even occasionaly common on the
> > open Internet, MIPv6 will become unusable/undeployable in practice.
>
> we could fix MIPv6. i.e use IP in IP instead of RH2.

At the end of the day, it would only add more overhead while decreasing=20
the "expresiveness" of the mobility header (which is a "vulgar" IP=20
header instead of specifically a mobility header).

And it would annoy firewall vendors as much as RH does, since they would=20
still have to parse skip through inner IP header in order to reach the=20
transport header.

Therefore, I think it is totally pointless, and it definitely is NOT=20
a "fix".

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/

--nextPart2914420.7m0GS377mA
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEABECAAYFAkZ0CGAACgkQw+xtvt1tEr0STwCdFIaxXHdDHUitin1NU1Lhiwrd
xIkAn3eifjIyNN865YGTFk35fVaIvk9R
=A/lT
-----END PGP SIGNATURE-----

--nextPart2914420.7m0GS377mA--


--===============0764036580==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0764036580==--




From ipv6-bounces@ietf.org Sat Jun 16 20:00:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HziBb-0005qs-OC; Sat, 16 Jun 2007 20:00:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HziBa-0005ja-5i
	for ipv6@ietf.org; Sat, 16 Jun 2007 20:00:06 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HziBZ-0004aC-Du
	for ipv6@ietf.org; Sat, 16 Jun 2007 20:00:06 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 5CD1C28429
	for <ipv6@ietf.org>; Sun, 17 Jun 2007 00:00:03 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 17 Jun 2007 00:00:03 +0000
Message-Id: <20070617000003.5CD1C28429@cyteen.hactrn.net>
X-Spam-Score: -0.9 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.55% |   10 |  9.35% |    66222 | brian.e.carpenter@gmail.com
  7.69% |    9 |  9.03% |    63955 | jabley@ca.afilias.info
  8.55% |   10 |  6.71% |    47568 | paul@vix.com
  6.84% |    8 |  7.32% |    51824 | jeroen@unfix.org
  5.98% |    7 |  7.18% |    50833 | ipng@69706e6720323030352d30312d31340a.nosense.org
  5.13% |    6 |  7.98% |    56506 | jordi.palet@consulintel.es
  5.98% |    7 |  5.70% |    40390 | narten@us.ibm.com
  5.98% |    7 |  4.78% |    33841 | rogerj@jorgensen.no
  5.13% |    6 |  5.52% |    39127 | trejrco@gmail.com
  4.27% |    5 |  4.23% |    29981 | fred.l.templin@boeing.com
  4.27% |    5 |  4.02% |    28488 | albert.e.manfredi@boeing.com
  3.42% |    4 |  3.04% |    21545 | rdenis@simphalempin.com
  3.42% |    4 |  2.87% |    20320 | jhw@apple.com
  2.56% |    3 |  2.51% |    17788 | bob.hinden@nokia.com
  2.56% |    3 |  1.98% |    14061 | bmanning@isi.edu
  1.71% |    2 |  2.25% |    15948 | marla.azinger@frontiercorp.com
  1.71% |    2 |  1.60% |    11311 | christopher.morrow@gmail.com
  1.71% |    2 |  1.34% |     9524 | alain_durand@cable.comcast.com
  1.71% |    2 |  1.32% |     9376 | guedou@hongo.wide.ad.jp
  0.85% |    1 |  1.00% |     7049 | volz@cisco.com
  0.85% |    1 |  0.98% |     6972 | gvandeve@cisco.com
  0.85% |    1 |  0.95% |     6758 | kkargel@polartel.com
  0.85% |    1 |  0.85% |     6001 | arnaud.ebalard@eads.net
  0.85% |    1 |  0.84% |     5972 | nnour@mitre.org
  0.85% |    1 |  0.81% |     5771 | ot@cisco.com
  0.85% |    1 |  0.81% |     5749 | owen@delong.com
  0.85% |    1 |  0.78% |     5541 | pekkas@netcore.fi
  0.85% |    1 |  0.75% |     5296 | jinmei@isl.rdc.toshiba.co.jp
  0.85% |    1 |  0.69% |     4879 | sra+ipng@hactrn.net
  0.85% |    1 |  0.65% |     4598 | drc@virtualized.org
  0.85% |    1 |  0.63% |     4451 | randy@psg.com
  0.85% |    1 |  0.53% |     3752 | christopher_taylor@mitel.com
  0.85% |    1 |  0.50% |     3520 | itojun@itojun.org
  0.85% |    1 |  0.49% |     3470 | gnn@neville-neil.com
--------+------+--------+----------+------------------------
100.00% |  117 |100.00% |   708387 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 16 21:29:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hzja6-00071f-Az; Sat, 16 Jun 2007 21:29:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzjTi-0003oY-Rn
	for ipv6@ietf.org; Sat, 16 Jun 2007 21:22:54 -0400
Received: from [2001:470:117:128:209:5bff:fe8c:8515] (helo=uillean.fuaim.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzjTi-0005nL-AC
	for ipv6@ietf.org; Sat, 16 Jun 2007 21:22:54 -0400
Received: from localhost (localhost.fuaim.com [127.0.0.1])
	by uillean.fuaim.com (Postfix) with ESMTP id 7FCBFB859
	for <ipv6@ietf.org>; Sat, 16 Jun 2007 18:22:53 -0700 (PDT)
Received: from uillean.fuaim.com ([127.0.0.1])
	by localhost (uillean.fuaim.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 16525-01-54 for <ipv6@ietf.org>;
	Sat, 16 Jun 2007 18:22:50 -0700 (PDT)
Received: from clairseach.fuaim.com (unknown
	[IPv6:2001:470:117:128:209:5bff:fe8e:6dd3])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by uillean.fuaim.com (Postfix) with ESMTP id A56E9B81E
	for <ipv6@ietf.org>; Sat, 16 Jun 2007 18:22:50 -0700 (PDT)
Received: from [172.17.55.4] (c-76-100-31-131.hsd1.md.comcast.net
	[76.100.31.131]) (authenticated bits=0)
	by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id l5H1Fu4Z022971
	for <ipv6@ietf.org>; Sat, 16 Jun 2007 18:15:57 -0700
Message-ID: <46748CC7.7000005@innovationslab.net>
Date: Sat, 16 Jun 2007 21:22:15 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Ipv <ipv6@ietf.org>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
X-Mailman-Approved-At: Sat, 16 Jun 2007 21:29:29 -0400
Subject: Call for NomCom Participation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

IPv6 WG Members,
     Please read the message below from the NomCom chair and consider
volunteering to serve.

Regards,
Brian

---

From: Lakshminath Dondeti
To: IETF Announcement
Date: June 4, 2007
Subject: Nomcom 2007-8: First Call for Volunteers

Folks,

If you have attended 3 out of the past 5 IETF meetings, you are eligible to
serve on Nomcom 2007-2008.  Please volunteer and you may become one of the
voting members of the committee that selects about half of the members
to the
IESG and IAB and one IAOC member.  RFC 3777 describes the process and the
responsibilities in detail.  Below is the list of people from the IESG,
IAB and
IAOC whose terms end during the March 2008 IETF meeting.

IAOC:

Ed Juskevicius

IAB:

Leslie Daigle
Elwyn Davies
Kevin Fall
Olaf Kolkman
David Oran
Eric Rescorla

IESG:

Lisa Dusseault -- Applications Area Director Jari Arkko -- Internet Area
Director Dan Romascanu -- Operations and Management Area Director Cullen
Jennings -- Real-time Applications and Infrastructure Area Director Ross
Callon
--- Routing Area Director Sam Hartman -- Security Area Director Magnus
Westerlund -- Transport Area Director

Before volunteering, please think about whether you want to be
considered for
one of those positions instead.  If you are already convinced, please
send an
email before 12:00 noon ET (16:00 UTC/GMT) on July 5, 2007 (otherwise,
please
read on)

To: ldondeti@qualcomm.com
Subject: Nomcom 2007-8 Volunteer
Body:

<Your Full Name>   // As you enter in the IETF Registration Form,
                           // First/Given name followed by Last/Family Name
<Current Primary Affiliation> // typically what goes in the Company field
                                          //  in the IETF Registration Form
[<all email addresses used to Register for the past 5 IETF meetings>]
<Preferred
email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 1-2 days stating whether
you are
qualified or not.  If you don't receive anything, please re-send your
email with
the tag (duplicate) in the subject line.

Not convinced yet?  Please consider that nomcom members play an
important role
in shaping the leadership of the IETF.  If you are a people person, you will
enjoy meeting many of the active contributors to the IETF.  If you prefer
instead to read a lot of email, well, we have that too.  Being a nomcom
member
is also an important responsibility: it requires adherence to
confidentiality
rules and some time commitment from the members.  The term begins just
prior to
the Chicago meeting and we expect most of the work to be completed by
January
2008.  During this period, the nomcom members

-- collect requirements from the community and interviews candidates
     during the Chicago and Vancouver IETF meetings
-- review candidates' statements and weighs community feedback
-- participate in candidate selection deliberations (weekly conferences
calls)

Nomcom members are selected following a publicly verifiable random selection
method specified in RFC 3797.

For the nomcom to work as it should, the pool from which the volunteers are
chosen should be as large as possible. The more people who volunteer,
the better
chance we have of choosing a random yet representative cross section of
the IETF
population.

Ensuring the leadership of the IETF is fair and balanced and comprised
of those
who can lead the IETF in the right direction is an important
responsibility that
rests on the IETF participants at large.  Volunteering for the nomcom is
a good
way of contributing in that direction.  So please volunteer!

thanks,
Lakshminath


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 17 19:50:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I04V1-0002rQ-As; Sun, 17 Jun 2007 19:49:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I04V0-0002rL-9W
	for ipv6@ietf.org; Sun, 17 Jun 2007 19:49:38 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I04Uy-0002He-IZ
	for ipv6@ietf.org; Sun, 17 Jun 2007 19:49:38 -0400
Received: from [203.10.60.20] (dhcp20.potaroo.net [203.10.60.20])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 696A9D5F2D;
	Mon, 18 Jun 2007 09:49:31 +1000 (EST)
Message-ID: <4675C8F5.2080908@apnic.net>
Date: Mon, 18 Jun 2007 09:51:17 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>
	<75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
In-Reply-To: <75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Thomas Narten <narten@us.ibm.com>, bob.hinden@nokia.com,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Christopher Morrow wrote:
> On 6/14/07, Thomas Narten <narten@us.ibm.com> wrote:
> 
>>
>> > If we want the advice in this section to be taken seriously, do we
>> > need to distinguish between firewall policy in end-sites and packet
>> > filters that might be added to core/ISP networks as a mitigation of
>> > the specific problems associated with RH0?
>>
>> We need to assume that other types of routing headers are "safe" to
>> use, and make sure than any usage actually is safe. If we can't do
>> that, we might as well just deprecate them all now.
> 
> I'd actually be a fan of not deprecating the headers in question, but
> permitting implementations to either ignore+forward, drop, use them.
> So, in the case at hand an operator could decide that 'source routing
> is ok' on their network and follow the wishes of the packet creator.
> Another may well decide that honoring source-route options (RH0) is
> not something they feel comfortable doing, but don't want to discard
> the packet out of hand. A third may decide that all source-routing
> (RH0) is 'evil' and must be dropped immediately.
> 
> This lets the technology be used where appropriate and doesn't do undo
> harm because folks can choose to, as adults, handle the traffic
> properly for their network/systems.
> 
> Is this too heretical to be considered?


No! For a _standards_ body it's an entirely appropriate way to consider 
this technology, imho. Source-based routing technology has been around 
for about the same period of time as circuits (indeed circuits could be 
considered a form of source-based routing). IN certain contects 
source-based routing is useful, and in networks where there there is no 
routing function it may even be essential.

Yes, in the context of the Internet, we've seen that enabling source 
routing can cause some unpleasant side effects, and the responsible 
advice is that this technology knob should be turned off in these forms 
of deployment, and even go so far as to say such capability should be 
turned off by default.

But trying to erase the capability itself from the protocol standard 
smacks to me of overreaction, and in terms of the security and safety of 
the internet is another classic example of security pantomime!

[But, like Chris, in thinking these evil thoughts I'm now a heretic. 
Quick, fetch the stake, the rope and some fire! :-)]

   Geoff


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 17 22:01:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I06YD-0006Qd-4J; Sun, 17 Jun 2007 22:01:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I06YB-0006Mu-PX
	for ipv6@ietf.org; Sun, 17 Jun 2007 22:01:03 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I06YA-0003UP-Em
	for ipv6@ietf.org; Sun, 17 Jun 2007 22:01:03 -0400
Received: from ssprunkxp (ip55.post-vineyard.dfw.ygnition.net [24.219.179.55])
	by ns2.ygnition.com (8.13.6/8.13.5) with SMTP id l5I20i0x018932;
	Sun, 17 Jun 2007 19:00:46 -0700
Message-ID: <016601c7b14c$3601d8b0$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <jordi.palet@consulintel.es>,
	"ARIN People Posting Mailing List" <ppml@arin.net>
References: <C299A650.19E44F%jordi.palet@consulintel.es>
Date: Sun, 17 Jun 2007 20:37:12 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipv6@ietf.org, address-policy-wg@ripe.net
Subject: Re: [ppml] Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thus spake "JORDI PALET MARTINEZ" <jordi.palet@consulintel.es>
> Agree, but actually I was wondering, if the AC/board has the power
> so just modify the policy in order to use ULA-C space, assuming
> that when the ULA-C becomes available, it offers the same
> features required by this policy. It may be much easier and faster
> instead of going thru the PDP all the way.

This sounds suspiciously like "I don't seem to have the support of the 
community, so I wonder if the Board/AC can ignore the process and do what I 
want anyways."

I don't know whether or not they can do that; it doesn't seem possible, but 
there's probably a loophole or two.  However, given the vocal opposition to 
the proposal (and the very existence of ULA-C), I doubt you'd ever convince 
them to if they could.  It's one thing to sneak through something that 
nobody cares about either way, but it's entirely different to deliberately 
exclude the community on something so divisive.

> Anyway is something that could be debated when ULA-C is
> available :-)

If you seriously propose doing the above, I suspect you'll manage to 
alienate even the folks who agree with ULA-C.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov 



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 02:52:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0B6Q-00082x-PV; Mon, 18 Jun 2007 02:52:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0B6Q-00082s-2Z
	for ipv6@ietf.org; Mon, 18 Jun 2007 02:52:42 -0400
Received: from mu-out-0910.google.com ([209.85.134.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0B6O-00031h-M8
	for ipv6@ietf.org; Mon, 18 Jun 2007 02:52:42 -0400
Received: by mu-out-0910.google.com with SMTP id w8so1682523mue
	for <ipv6@ietf.org>; Sun, 17 Jun 2007 23:52:39 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ToIOHEb/oh5gMLppwbtrB5qpI/vTzRu/0mZOwmtUYnCuNm6qiSjJyqS+3m+2QkY9v/CgnAZjy4iCrYJvnfdgh8jLVWEM9nGt1M1WWdYlFpO6UvwN82oCt3kmCl5SZXU6IDXtrIvJdvTXzPG78PpaE+S5zefTlw3svkdfnmPIF/k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=pgQlAAGcgIqZ5VeeMw+1Tqcxjvey/DXRw23CRHxXapzG15I17qtHuCf1PlxAn5sTkFgXi+1xUcck6p4RAOoQlwHzuHrBMNMPQbBOgFfPsEuTwa2p1UHe7eWZi1EjR7hZad+7bJPlJCPnSZlRHW0aPFZ5KrwuEwOgVMQN7llQ/xs=
Received: by 10.82.162.14 with SMTP id k14mr10559201bue.1182149559703;
	Sun, 17 Jun 2007 23:52:39 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id k5sm3260944nfh.2007.06.17.23.52.38
	(version=SSLv3 cipher=RC4-MD5); Sun, 17 Jun 2007 23:52:39 -0700 (PDT)
Message-ID: <46762BB6.9070205@gmail.com>
Date: Mon, 18 Jun 2007 08:52:38 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
References: <CEC5DC97-9C32-404A-AD3B-AF88F09C9F15@ca.afilias.info>	<200706131153.l5DBroLG008411@cichlid.raleigh.ibm.com>	<CE90CE47-B548-4D5C-B890-3B004F27D4F8@ca.afilias.info>	<9ADA8932-580B-4905-AE70-5F32D8564222@nokia.com>	<200706131742.l5DHgLUH002825@cichlid.raleigh.ibm.com>	<65A378E6-E3FC-4B76-99A2-E41067DC69A3@ca.afilias.info>	<200706150009.l5F099L1014874@cichlid.raleigh.ibm.com>	<75cb24520706152323k70f9b252xce01de6aad01be59@mail.gmail.com>
	<4675C8F5.2080908@apnic.net>
In-Reply-To: <4675C8F5.2080908@apnic.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	bob.hinden@nokia.com
Subject: Re: draft-ietf-ipv6-deprecate-rh0-01-candidate-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Geoff and Chris,

> But trying to erase the capability itself from the protocol standard=20
> smacks to me of overreaction, and in terms of the security and safety o=
f=20
> the internet is another classic example of security pantomime!
>=20
> [But, like Chris, in thinking these evil thoughts I'm now a heretic.=20
> Quick, fetch the stake, the rope and some fire! :-)]

My first thought some weeks ago was to add rules to RH0 to eliminate
at least most of the problem, but I've become convinced that the
cleanest way to do that is to abolish RH0 and design a new RHn
which is intrinsically safer. As far as implementers and operators
are concerned that should be better, since there won't be ambiguity
about whether code has been updated to support RH0bis or not, since
we have no provision for versioning routing headers.

That way, we could avoid the auto da f=C3=A9.

    Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 03:42:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0Bsq-0005UW-4U; Mon, 18 Jun 2007 03:42:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Bso-0005UM-4Q
	for ipv6@ietf.org; Mon, 18 Jun 2007 03:42:42 -0400
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Bsk-00066L-DG
	for ipv6@ietf.org; Mon, 18 Jun 2007 03:42:42 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1207927ugf
	for <ipv6@ietf.org>; Mon, 18 Jun 2007 00:42:37 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=cQKzGTWaD83/ToDU945CR34a34cGhnbS/H7XKtCmX2f7xWt9S0NNb/eyjDSxFo9pSpSOCxEtStFobrSbN+sJD0T+RHl+rPNHuebAB+Ea6+HPVswU+t1PtTeeizE0v6RWkD9oB10rBNI/tpX8alCCEA33aFtS6yE/GN2/JNTbkjM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=bBfX1Sz+1+CfPbmAuBYePKkEHvH4G175df3/5ApUhDh3Try3I2kDAKWFbpb2dweS8l82TVYFlOZs7mDrqNsr5jhhlEHcrfwg2ZwBtzNBi+NPWipMYuPe1b29+RSZ9XccvV/kA5ks3N8V5MmQ2USRPv7qwIEWwdAaPNB9SbpAanE=
Received: by 10.82.152.16 with SMTP id z16mr10657083bud.1182152557593;
	Mon, 18 Jun 2007 00:42:37 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 7sm2455500nfv.2007.06.18.00.42.36
	(version=SSLv3 cipher=RC4-MD5); Mon, 18 Jun 2007 00:42:36 -0700 (PDT)
Message-ID: <4676376B.50207@gmail.com>
Date: Mon, 18 Jun 2007 09:42:35 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: jordi.palet@consulintel.es
References: <C2985F9B.19E23F%jordi.palet@consulintel.es>
In-Reply-To: <C2985F9B.19E23F%jordi.palet@consulintel.es>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Cc: ipv6@ietf.org
Subject: Re: Revising Centrally Assigned ULA draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jordi, my point is that technically, this is trivial, if
the community concludes it's a good idea.  There is running
code. So no need for an administrative solution since a robot
can do it cheaper and better. But it isn't the IETF that
should decide who the operational community will trust
to run the robot.

The only real question is whether the 40 pseudo-random bits
are a feature or a bug. If they're a bug, stick to PI.

    Brian

On 2007-06-15 17:24, JORDI PALET MARTINEZ wrote:
> They need a trusted entity running the tool to void any clash chance, that's
> one good reason for making it different than ULA.
> 
> Regards,
> Jordi
> 
> 
> 
> 
>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> Responder a: <ipv6-bounces@ietf.org>
>> Fecha: Thu, 14 Jun 2007 11:42:20 +0200
>> Para: <jordi.palet@consulintel.es>
>> CC: <ipv6@ietf.org>
>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: [***SPAM*** Score/Req: 10.4/4.5]
>> Re: Revising Centrally Assigned ULA draft
>>
>> On 2007-06-14 11:30, JORDI PALET MARTINEZ wrote:
>>> Operators have said that they will not be able to use ULA, but they could
>>> use ULA-C, for example for thinks like microallocations for internal
>>> infrastructure's.
>> Since there is no practical difference between ULA and ULA-C, they
>> need to explain...
>>
>> The argument about private addresses at the end of
>> http://www.arin.net/policy/proposals/2006_2.html
>> makes no sense. ULA and ULA-C are both private addresses.
>>
>>      Brian
>>> I think the policy proposal that I sent to several regions includes text and
>>> links to other documents that can clarify this perspective.
>>>
>>> For example in RIPE NCC:
>>> http://www.ripe.net/ripe/policies/proposals/2007-05.html
>>>
>>> Regards,
>>> Jordi
>>>
>>>
>>>
>>>
>>>> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>>> Responder a: <ipv6-bounces@ietf.org>
>>>> Fecha: Thu, 14 Jun 2007 11:21:04 +0200
>>>> Para: Roger Jorgensen <rogerj@jorgensen.no>
>>>> CC: IETF IPv6 Mailing List <ipv6@ietf.org>
>>>> Asunto: [***SPAM*** Score/Req: 10.4/4.5] Re: Revising Centrally Assigned ULA
>>>> draft
>>>>
>>>> On 2007-06-12 22:19, Roger Jorgensen wrote:
>>>>> On Tue, 12 Jun 2007, Manfredi, Albert E wrote:
>>>>> <snip>
>>>>>> Is this a little like the RH0 thread? When it was a choice of disabling
>>>>>> by default or removing entirely? My vote is, don't forward ULA-Cs by
>>>>>> default, but let us use them as we used RFC 1918. It was also my vote
>>>>>> when we were discussing site-local.
>>>>> Why are we even talking about ULA-C now? What you want is nicely covered
>>>>> by ULA... not ULA-C but regular plain stright forward ULA.
>>>> Exactly. If you want some private address space that no ISP will route,
>>>> but which you may care to use in your own network or with your
>>>> business partners via VPNs, get yourself a ULA, which is self-service.
>>>> And do what you need to do in your internal DNS; it will never appear
>>>> in the global DNS. (And don't rely on reverse DNS for your internal
>>>> operations, but that's a really silly thing to do anyway.)
>>>>
>>>> The *only* possible argument for centrally allocated ULAs is for those
>>>> who believe that the birthday paradox in a 2^40 address space causes
>>>> a real danger of colliding with another business partner's ULA prefix.
>>>> As I've said, we can easily have a robot to take care of that (in fact,
>>>> the prototype is up and running, thanks Jeroen).
>>>>
>>>> There seems to be a lot of confusion in part of this discussion. If
>>>> a ULA prefix does escape from its intended scope, it will be *exactly*
>>>> like any other non-aggregatable prefix that escapes. ULAs don't add to, or
>>>> remove from, the difficulties of dealing with non-aggregatable prefixes.
>>>>
>>>> As for what is a site for ULA purposes: it's whatever network(s) decide
>>>> to use and route a given ULA prefix. Its boundary is a set of routers
>>>> that don't route that prefix further outwards.
>>>>
>>>>      Brian
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>> **********************************************
>>> The IPv6 Portal: http://www.ipv6tf.org
>>>
>>> Bye 6Bone. Hi, IPv6 !
>>> http://www.ipv6day.org
>>>
>>> This electronic message contains information which may be privileged or
>>> confidential. The information is intended to be for the use of the
>>> individual(s) named above. If you are not the intended recipient be aware
>>> that any disclosure, copying, distribution or use of the contents of this
>>> information, including attached files, is prohibited.
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 
> 
> 
> **********************************************
> The IPv6 Portal: http://www.ipv6tf.org
> 
> Bye 6Bone. Hi, IPv6 !
> http://www.ipv6day.org
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 15:51:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0NFB-0006Vt-JU; Mon, 18 Jun 2007 15:50:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0NEg-0005i3-Ti; Mon, 18 Jun 2007 15:50:02 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0NEg-0001TK-FJ; Mon, 18 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 5FEB2328A2;
	Mon, 18 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I0NEg-000884-8o; Mon, 18 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
Date: Mon, 18 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: ipv6@ietf.org
Subject: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: Centrally Assigned Unique Local IPv6 Unicast Addresses
	Author(s)	: R. Hinden, B. Haberman
	Filename	: draft-ietf-ipv6-ula-central-02.txt
	Pages		: 11
	Date		: 2007-6-18
	
This document defines Centrally allocated IPv6 Unique Local
   addresses.  These addresses are globally unique and are intended for
   local communications, usually inside of a site.  They are not
   expected to be routable on the global Internet.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ipv6-ula-central-02.txt".

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

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

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ipv6-ula-central-02.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--NextPart--





From ipv6-bounces@ietf.org Mon Jun 18 17:39:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0OwD-0001hm-H2; Mon, 18 Jun 2007 17:39:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0OwB-0001gC-Tt
	for ipv6@ietf.org; Mon, 18 Jun 2007 17:39:03 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0OwA-0005BS-F9
	for ipv6@ietf.org; Mon, 18 Jun 2007 17:39:03 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 22:39:01 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 18 Jun 2007 22:40:23 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08AF8F5@E03MVC4-UKBR.domain1.systemhost.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02
Thread-Index: Acex8UZvDnGq7893TZOOO9Wur7350Q==
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 18 Jun 2007 21:39:01.0658 (UTC)
	FILETIME=[15EF2FA0:01C7B1F1]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: draft-ietf-ipv6-ula-central-02
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

In this draft it has some requirements for generating ULA-C prefixes and
then in 7.0 it requires the RIRs to publish an RFC documenting how they
will implement these requirements.

I think it would be better not to require the RIRs to also go through
the RFC process after a ULA-C RFC has been issued, if it ever gets to
that point. One possible solution is to downgrade this to simply require
the RIRs to publish an RIR document explaining how they implement
section 3.2.

But a better way is for the ULA-C document to include this. I note that
any algorithm for checking (and registering) a generated prefix in the 5
RIR databases could easily be done in advance so that each RIR keeps a
supply of unique ULA-C prefixes on hand based on their forecast rate of
requests for such addresses. That means that an applicant does not have
to wait for turnaround time of the uniqueness test. As far as protocols
for communication between the RIRs, this should also be specified in the
ULA-C document, however it should not develop any new protocols, merely
specify that something like XML-RPC or REST be used, and the semantics
of the transaction which should be atomic, i.e. test uniqueness and
register in one transaction. This transaction should provide some kind
of positive response so that there is no possibility of a false
positive. And since it will likely be most heavily used to register
batches of unique ULA-C prefixes, it should allow for a single
transaction to register the entire batch (or at least as many are
actually unique). Race conditions can occur here but it is not necessary
for a protocol or application to resolve these since this can be done by
some manual exception process. As long as conflicting prefixes (ones
which have not passed all 5 RIR checks) are removed from all the
databases regularly, that is sufficient.

-------------------------------------------------------
Michael Dillon
Capacity Management, 66 Prescot St., London, E1 8HG, UK
Mobile: +44 7900 823 672=20
Internet: michael.dillon@btradianz.com
Phone: +44 20 7650 9493 Fax: +44 20 7650 9030
http://www.btradianz.com
=20
One Community One Connection One Focus=20


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 18:30:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0Pjl-0003S1-Vc; Mon, 18 Jun 2007 18:30:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0Pjk-0003QE-3W
	for ipv6@ietf.org; Mon, 18 Jun 2007 18:30:16 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0Pji-0005j1-Nz
	for ipv6@ietf.org; Mon, 18 Jun 2007 18:30:16 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.149118239;
	Mon, 18 Jun 2007 18:34:45 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 18 Jun 2007 18:29:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 18 Jun 2007 18:29:57 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A0272F932@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02
Thread-Index: Acex8UZvDnGq7893TZOOO9Wur7350QABT7dQ
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: <michael.dillon@bt.com>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 18 Jun 2007 22:29:57.0843 (UTC)
	FILETIME=[33900230:01C7B1F8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Michael-  I dont believe that was the intent and there might be a little =
misinterpretation here due to how it was written.  The document says:

>The designated allocation authority is required to document how they
   will meet the requirements described in Section 3.2 of this document
   in an RFC.<

This states the RIR's need to document how they will meet the =
requirements once section 3.2.  It dont believe the author intends for =
RIR's to write an RFC.  I believe the intent of the sentence you =
question is actually saying in a round about way that RIR's need to use =
their policy process and write policy's that will meet the requirements =
stated in section 3.2 of the draft.  Thus, synchronizing the RFC and RIR =
policy.

Or at least that is what I had discussed on a conference call with R. =
Hinden and T. Narten before the revision was made.  So Bob or Thomas, =
correct me if I am wrong here...

Cheers!
Marla



-----Original Message-----
From: michael.dillon@bt.com [mailto:michael.dillon@bt.com]
Sent: Monday, June 18, 2007 2:40 PM
To: ipv6@ietf.org
Subject: draft-ietf-ipv6-ula-central-02


In this draft it has some requirements for generating ULA-C prefixes and
then in 7.0 it requires the RIRs to publish an RFC documenting how they
will implement these requirements.

I think it would be better not to require the RIRs to also go through
the RFC process after a ULA-C RFC has been issued, if it ever gets to
that point. One possible solution is to downgrade this to simply require
the RIRs to publish an RIR document explaining how they implement
section 3.2.

But a better way is for the ULA-C document to include this. I note that
any algorithm for checking (and registering) a generated prefix in the 5
RIR databases could easily be done in advance so that each RIR keeps a
supply of unique ULA-C prefixes on hand based on their forecast rate of
requests for such addresses. That means that an applicant does not have
to wait for turnaround time of the uniqueness test. As far as protocols
for communication between the RIRs, this should also be specified in the
ULA-C document, however it should not develop any new protocols, merely
specify that something like XML-RPC or REST be used, and the semantics
of the transaction which should be atomic, i.e. test uniqueness and
register in one transaction. This transaction should provide some kind
of positive response so that there is no possibility of a false
positive. And since it will likely be most heavily used to register
batches of unique ULA-C prefixes, it should allow for a single
transaction to register the entire batch (or at least as many are
actually unique). Race conditions can occur here but it is not necessary
for a protocol or application to resolve these since this can be done by
some manual exception process. As long as conflicting prefixes (ones
which have not passed all 5 RIR checks) are removed from all the
databases regularly, that is sufficient.

-------------------------------------------------------
Michael Dillon
Capacity Management, 66 Prescot St., London, E1 8HG, UK
Mobile: +44 7900 823 672=20
Internet: michael.dillon@btradianz.com
Phone: +44 20 7650 9493 Fax: +44 20 7650 9030
http://www.btradianz.com
=20
One Community One Connection One Focus=20


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 19:12:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0QO9-00075H-Ff; Mon, 18 Jun 2007 19:12:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0QO7-00075B-Rg
	for ipv6@ietf.org; Mon, 18 Jun 2007 19:11:59 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0QO6-0003Cj-Dc
	for ipv6@ietf.org; Mon, 18 Jun 2007 19:11:59 -0400
Received: from ep_ms7_bk (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JJU00LBGTRUC2@mailout3.samsung.com> for ipv6@ietf.org;
	Tue, 19 Jun 2007 08:11:54 +0900 (KST)
Received: from ep_spt03 (ms7.samsung.com [203.254.225.101])
	by ms7.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0JJU007Q9TRUXI@ms7.samsung.com> for ipv6@ietf.org; Tue,
	19 Jun 2007 08:11:54 +0900 (KST)
Content-return: prohibited
Date: Mon, 18 Jun 2007 23:11:54 +0000 (GMT)
From: Daniel Park <soohong.park@samsung.com>
To: ipv6@ietf.org
Message-id: <4878732.2543501182208313987.JavaMail.weblogic@ep_ml23>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070618231153985@soohong.park
X-MTR: 20070618231153985@soohong.park
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Fwd: Document Action: 'IPv6 Router Advertisement Option for DNS
 Configuration' to Experimental RFC
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: soohong.park@samsung.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1213335357=="
Errors-To: ipv6-bounces@ietf.org

--===============1213335357==
Content-return: prohibited
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: base64

RllJLCBpbiBjYXNlIHlvdSBtaXNzZWQgaXQuDQogDQpHb29kIG5ld3MuLi4hDQogDQotLSBEYW5p
ZWwgUGFyaw0KDQotLS0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0tLQ0KU2VuZGVyIDogVGhl
IElFU0c8aWVzZy1zZWNyZXRhcnlAaWV0Zi5vcmc+DQpEYXRlICAgOiAyMDA3LTA2LTE4IDIzOjMx
DQpUaXRsZSAgOiBEb2N1bWVudCBBY3Rpb246ICYjMzk7SVB2NiBSb3V0ZXIgQWR2ZXJ0aXNlbWVu
dCBPcHRpb24gZm9yIEROUyBDb25maWd1cmF0aW9uJiMzOTsgdG8gRXhwZXJpbWVudGFsIFJGQw0K
DQpUaGUgSUVTRyBoYXMgYXBwcm92ZWQgdGhlIGZvbGxvd2luZyBkb2N1bWVudDoNCg0KLSAmIzM5
O0lQdjYgUm91dGVyIEFkdmVydGlzZW1lbnQgT3B0aW9uIGZvciBETlMgQ29uZmlndXJhdGlvbiAm
IzM5Ow0KICAgPGRyYWZ0LWplb25nLWRuc29wLWlwdjYtZG5zLWRpc2NvdmVyeS0xMi50eHQ+IGFz
IGFuIEV4cGVyaW1lbnRhbCBSRkMNCg0KVGhpcyBkb2N1bWVudCBoYXMgYmVlbiByZXZpZXdlZCBp
biB0aGUgSUVURiBidXQgaXMgbm90IHRoZSBwcm9kdWN0IG9mIGFuDQpJRVRGIFdvcmtpbmcgR3Jv
dXAuIA0KDQpUaGUgSUVTRyBjb250YWN0IHBlcnNvbiBpcyBNYXJrIFRvd25zbGV5Lg0KDQpBIFVS
TCBvZiB0aGlzIEludGVybmV0LURyYWZ0IGlzOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtamVvbmctZG5zb3AtaXB2Ni1kbnMtZGlzY292ZXJ5LTEyLnR4dA0KDQpU
ZWNobmljYWwgU3VtbWFyeQ0KIA0KICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBuZXcgSVB2
NiBSb3V0ZXIgQWR2ZXJ0aXNlbWVudCBvcHRpb24gdG8NCiAgIGFsbG93IElQdjYgcm91dGVycyB0
byBhZHZlcnRpc2UgRE5TIHJlY3Vyc2l2ZSBzZXJ2ZXIgYWRkcmVzc2VzIHRvDQogICBJUHY2IGhv
c3RzLg0KIA0KV29ya2luZyBHcm91cCBTdW1tYXJ5DQogDQogIFRoaXMgaXMgYW4gaW5kaXZpZHVh
bCBzdWJtaXNzaW9uLiBBIHJldmlldyBzdW1tYXJ5IGZyb20gQm9iIEhpbmRlbiANCiAgZm9sbG93
czoNCg0KPiBUaGUgcmV2aWV3ZXJzIHdlcmUgUGVra2EgU2F2b2xhLCBCcmlhbiBIYWJlcm1hbiwg
YW5kIElsaml0c2NoIHZhbg0KPiBCZWlqbnVtLiAgVGhleSByZXZpZXdlZCB0aGUgZG9jdW1lbnQg
PGRyYWZ0LWplb25nLWRuc29wLWlwdjYtZG5zLQ0KPiBkaXNjb3ZlcnktMDUudHh0PiBhbmQgdHdv
IHN1YnNlcXVlbnQgZHJhZnRzLiAgVGhlaXIgcmV2aWV3IHJhaXNlZA0KPiBzZXZlcmFsIGlzc3Vl
cy4gIEFmdGVyIGEgZGlzY3Vzc2lvbiB3aXRoIHRoZSBhdXRob3JzLCBhIHNldCBvZiBjaGFuZ2Vz
DQo+IHdhcyBhZ3JlZWQgdG8gYW5kIGEgcmV2aXNlZCBkcmFmdCB3YXMgcHVibGlzaGVkIGFzIDxk
cmFmdC0NCj4gamVvbmctZG5zb3AtaXB2Ni1kbnMtZGlzY292ZXJ5LTA4LnR4dD4uICBUaGUgcmV2
aWV3ZXJzIGFuZCBJIGFyZQ0KPiBzYXRpc2ZpZWQgd2l0aCB0aGUgY2hhbmdlcyBhbmQgcmVjb21t
ZW5kIHRoYXQgdGhlIGRvY3VtZW50IGJlDQo+IHB1Ymxpc2hlZCBhcyBhbiBpbmRpdmlkdWFsIHN1
Ym1pdHRlZCBSRkMuDQoNCiANClByb3RvY29sIFF1YWxpdHkNCiANCiAgVGhpcyBkb2N1bWVudCB3
YXMgcmV2aWV3ZWQgYnkgTWFyZ2FyZXQgV2Fzc2VybWFuLCBCb2IgSGluZGVuLCBQZWtrYQ0KU2F2
b2xhLCBCcmlhbiBIYWJlcm1hbiwgYW5kIElsaml0c2NoIHZhbiBCZWlqbnVtLg0KDQoNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJRVRGLUFubm91bmNl
IG1haWxpbmcgbGlzdA0KSUVURi1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zi1hbm5vdW5jZQ0KDQoNCg0KIA0KIA0KLS0tDQogDQpE
YW5pZWwgKFNvb2hvbmcgRGFuaWVsIFBhcmspLCBTdGFuZGFyZCBTcGVjaWFsaXN0DQpNb2JpbGUg
Q29udmVyZ2VuY2UgTGFib3JhdG9yeS4gU0FNU1VORyBFbGVjdHJvbmljcw0KIA0KIA0KIA0KIA==




--===============1213335357==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1213335357==--



From ipv6-bounces@ietf.org Mon Jun 18 19:16:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0QSh-0003Ze-Kh; Mon, 18 Jun 2007 19:16:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0QSf-0003ZW-W6
	for ipv6@ietf.org; Mon, 18 Jun 2007 19:16:41 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0QSe-0004WM-IL
	for ipv6@ietf.org; Mon, 18 Jun 2007 19:16:41 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5INGcs6090861
	for <ipv6@ietf.org>; Tue, 19 Jun 2007 09:16:38 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
To: ipv6@ietf.org
From: Mark Andrews <Mark_Andrews@isc.org>
Date: Tue, 19 Jun 2007 09:16:38 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


4.1 DNS Issues

   AAAA and PTR records for centrally assigned local IPv6 addresses may
   be installed in the global DNS.  This may be useful if these
   addresses are being used for site to site or VPN style applications,
   or for sites that wish to avoid separate DNS systems for inside and
   outside traffic.

   The operational issues relating to this are beyond the scope of this
   document.

	We have to be *very* careful here.  If we allow PTR's to
	be installed in the global DNS then globally reachable
	nameservers *have* to exist for each prefix allocated.
	Otherwise the problems that the AS112 project is trying to
	deal with will appear here as well.

	This is a long term operational cost associated with ULA-C.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 18 21:07:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0SBF-0007fG-JV; Mon, 18 Jun 2007 21:06:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0SBE-0007f8-CF
	for ipv6@ietf.org; Mon, 18 Jun 2007 21:06:48 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0SBC-0008NG-TH
	for ipv6@ietf.org; Mon, 18 Jun 2007 21:06:48 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5J16WCf007004 for <ipv6@ietf.org>; Tue, 19 Jun 2007 04:06:44 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 04:06:24 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh104.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 04:06:24 +0300
Received: from [172.19.74.177] (dadhcp-172019074177.americas.nokia.com
	[172.19.74.177])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5J16M9u011719 for <ipv6@ietf.org>; Tue, 19 Jun 2007 04:06:22 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E70BCC5C-37EB-41AD-A06B-737E7E5FE38D@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 18 Jun 2007 18:06:21 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 19 Jun 2007 01:06:24.0210 (UTC)
	FILETIME=[0E45F320:01C7B20E]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: New Central ULA Draft (draft-ietf-ipv6-ula-central-02.txt)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Now that the new central ULA draft is out, I wanted to add a few  
words of explanation.

The current authors got involved because we received a request from  
people in the RIR community who thought there was merit in the  
central ULA idea and a discussion had started in the RIRs.  A lot has  
changed since the previous central ULA draft was published and we  
thought there was value in publishing a updated draft that defines a  
feasible technical approach.  We believe the new draft does this.   
It's not perfect, but describes what we think at the important  
elements and requirements.

I think I can speak for all of the authors in that none of us are  
completely certain this is necessary, but we all think that if there  
is going to be a debate in the IETF and RIR communities, then the  
debate should be on a document that represents a viable solution.   
None of us has a "religious" position on this and will be just as  
happy if it the idea goes back to sleep.  If there is community  
support, we will push it through the process.

Bob


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 11:16:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0fQ0-0001gV-VZ; Tue, 19 Jun 2007 11:14:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0fPz-0001ba-Cn
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:14:55 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0fPy-0006Gf-1y
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:14:55 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5JFEnT8021412
	for <ipv6@ietf.org>; Tue, 19 Jun 2007 11:14:49 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5JFEdv5266782 for <ipv6@ietf.org>; Tue, 19 Jun 2007 09:14:46 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5JFEclm001520 for <ipv6@ietf.org>; Tue, 19 Jun 2007 09:14:38 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-161-227.wecm.ibm.com
	[9.67.161.227])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5JFEZOL001212
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 19 Jun 2007 09:14:38 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5JFEQfM030490;
	Tue, 19 Jun 2007 11:14:33 -0400
Message-Id: <200706191514.l5JFEQfM030490@cichlid.raleigh.ibm.com>
To: michael.dillon@bt.com
In-reply-to: <D03E4899F2FB3D4C8464E8C76B3B68B08AF8F5@E03MVC4-UKBR.domain1.systemhost.net>
References: <D03E4899F2FB3D4C8464E8C76B3B68B08AF8F5@E03MVC4-UKBR.domain1.systemhost.net>
Comments: In-reply-to <michael.dillon@bt.com>
	message dated "Mon, 18 Jun 2007 22:40:23 +0100."
Date: Tue, 19 Jun 2007 11:14:26 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> In this draft it has some requirements for generating ULA-C prefixes and
> then in 7.0 it requires the RIRs to publish an RFC documenting how they
> will implement these requirements.

I don't think the RIRs necessarily need to publish an RFC. The main
point is for the RIRs to have sufficiently documented what they
propose to do so that everyone is happy with proposal and it's written
down somewhere. The details of exactly what documentation is
sufficient can be discussed and shouldn't become a rathole relative to
the bigger question of whether ULA-C shold go forward at all.

> But a better way is for the ULA-C document to include this.

Well, one thing to balance here is the part the IETF specifies and the
part the RIRs specify (in terms of operational policy). Putting it all
in one document complicates that and might result in the some of the
text appearing to come from the IETF (and the IETF then being
authoritative) rather than the RIRs. I don't think we want that either.

> I note that any algorithm for checking (and registering) a generated
> prefix in the 5 RIR databases could easily be done in advance so
> that each RIR keeps a supply of unique ULA-C prefixes on hand based
> on their forecast rate of requests for such addresses.

There are lots of ways of achieving uniqueness. One thing the authors
discussed quite a bit (with rough consensus at best!) was to what
degree the operational details of how to carry out the proposal should
be specified in this ID. Personally, I'd rather see less detail in the
IETF document, with it concentrating on the desired/required
properties of ULA-Cs. Presumably, if we define the properties
clearly/properly, how they are produced operationally would be a
detail and not really our concern, i.e., so long as the desired
properties are preserved.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 11:23:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0fYQ-0000p8-1c; Tue, 19 Jun 2007 11:23:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0fYO-0000p3-Vz
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:23:36 -0400
Received: from e34.co.us.ibm.com ([32.97.110.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0fYO-0007so-Jm
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:23:36 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e34.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5JFNZJu020189
	for <ipv6@ietf.org>; Tue, 19 Jun 2007 11:23:36 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5JFNZMD261478 for <ipv6@ietf.org>; Tue, 19 Jun 2007 09:23:35 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5JFNZG0017352 for <ipv6@ietf.org>; Tue, 19 Jun 2007 09:23:35 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-161-227.wecm.ibm.com
	[9.67.161.227])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5JFNVWR017015
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 19 Jun 2007 09:23:34 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5JFNR8J032665;
	Tue, 19 Jun 2007 11:23:29 -0400
Message-Id: <200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
To: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: <200706182316.l5INGcs6090861@drugs.dv.isc.org> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
Comments: In-reply-to Mark Andrews <Mark_Andrews@isc.org>
	message dated "Tue, 19 Jun 2007 09:16:38 +1000."
Date: Tue, 19 Jun 2007 11:23:27 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> 4.1 DNS Issues

>    AAAA and PTR records for centrally assigned local IPv6 addresses may
>    be installed in the global DNS.  This may be useful if these
>    addresses are being used for site to site or VPN style applications,
>    or for sites that wish to avoid separate DNS systems for inside and
>    outside traffic.

>    The operational issues relating to this are beyond the scope of this
>    document.

> 	We have to be *very* careful here.  If we allow PTR's to
> 	be installed in the global DNS then globally reachable
> 	nameservers *have* to exist for each prefix allocated.
> 	Otherwise the problems that the AS112 project is trying to
> 	deal with will appear here as well.

> 	This is a long term operational cost associated with ULA-C.

Well, please expand on this so we can discuss in more detail.

My assumption is that some (but not all) ULA-C holders will want to be
able to have PTR records. This seems operationally useful to me, for
those that choose to use them and place them in the public DNS
tree. Thus, we shouldn't ban it outright. That is, the question is
whether the RIRs then would need to support the creation of such
records for registered ULA-C owners.

And help me understand how this equates to the AS112 issues. For sites
that (today) get PI space and don't actually advertise it to the
internet, aren't the DNS issues _exactly_ the same?

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 11:54:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0g2O-00013N-ME; Tue, 19 Jun 2007 11:54:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0g2M-00013A-Ao
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:54:34 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0g2L-0007kQ-MQ
	for ipv6@ietf.org; Tue, 19 Jun 2007 11:54:34 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 3847E140C135;
	Tue, 19 Jun 2007 17:54:32 +0200 (CEST)
Message-ID: <4677FC3C.3050507@spaghetti.zurich.ibm.com>
Date: Tue, 19 Jun 2007 16:54:36 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
In-Reply-To: <200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Mark Andrews <Mark_Andrews@isc.org>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1519685088=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1519685088==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig2CADBFBA6AE4837175701C2C"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig2CADBFBA6AE4837175701C2C
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thomas Narten wrote:
[..]
>> 	We have to be *very* careful here.  If we allow PTR's to
>> 	be installed in the global DNS then globally reachable
>> 	nameservers *have* to exist for each prefix allocated.
>> 	Otherwise the problems that the AS112 project is trying to
>> 	deal with will appear here as well.
>=20
>> 	This is a long term operational cost associated with ULA-C.
[..]
> And help me understand how this equates to the AS112 issues. For sites
> that (today) get PI space and don't actually advertise it to the
> internet, aren't the DNS issues _exactly_ the same?

When the prefix is 'local' why would that need to be rooted into the glob=
al
Internet? I get the point about having unique addresses out of the same
namespace, but I don't get why reverses then have to be supplied too.

Which leads to the point I wanted to ask:

 How is ULA-C different from PI?

Yes, the prefix it comes from is different, which allows 'easy filtering'=
=2E
But do you suddenly trust fc00::/7 more than global unicast?

Also, unless there is a considerable (important) portion of the Internet
that will not accept ULA-C prefixes, or the ULA-C prefix in question has =
a
lot of value, this will become a routing mess as people will start
announcing them and using them where possible. PA is also being chopped u=
p
by some who are announcing /48's already and even tricks like getting a /=
31
and announcing two completely separate /32's without the aggregate /31.


The draft is more or less okay IMHO. But the big question is if it is rea=
lly
needed when there is PI already that can be used for this same purpose.

Greets,
 Jeroen


--------------enig2CADBFBA6AE4837175701C2C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ3/DwuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I1KnAJ92s5BMdGtG46B3UAJksFUJR6X1
FQCgvjW6Lieo0fq0uVR1CUsQwSzKBOU=
=w91t
-----END PGP SIGNATURE-----

--------------enig2CADBFBA6AE4837175701C2C--


--===============1519685088==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1519685088==--




From ipv6-bounces@ietf.org Tue Jun 19 15:14:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0j9m-0001lC-Az; Tue, 19 Jun 2007 15:14:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0j9k-0001l1-Ae
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:14:24 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0j9i-0000SU-3t
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:14:23 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l5JJEElo009958;
	Tue, 19 Jun 2007 22:14:14 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l5JJEDNx009955;
	Tue, 19 Jun 2007 22:14:14 +0300
Date: Tue, 19 Jun 2007 22:14:13 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Thomas Narten <narten@us.ibm.com>
In-Reply-To: <200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
Message-ID: <Pine.LNX.4.64.0706192211570.9840@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.90.3/3457/Tue Jun 19 02:54:49 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.9
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Mark Andrews <Mark_Andrews@isc.org>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 19 Jun 2007, Thomas Narten wrote:
> And help me understand how this equates to the AS112 issues. For sites
> that (today) get PI space and don't actually advertise it to the
> internet, aren't the DNS issues _exactly_ the same?

IMHO, if reverse DNS is provided, it should be required that the 
authoritative DNS servers have non-ULA addresses.  I think Mark was 
assuming that ULA address for authoritative delegation point might be 
OK, which would lead to issues if the ULA address is not reachable 
from everywhere where reverse DNS lookups should succeed.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 15:28:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jNK-0007Rj-HT; Tue, 19 Jun 2007 15:28:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jNJ-0007PI-0k
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:28:25 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0jNH-00036o-1v
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:28:25 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 80B19140C022;
	Tue, 19 Jun 2007 21:28:20 +0200 (CEST)
Message-ID: <46782E58.6070705@spaghetti.zurich.ibm.com>
Date: Tue, 19 Jun 2007 20:28:24 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706192211570.9840@netcore.fi>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0002149897=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0002149897==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA9F8139CA7FF3E9E5AFE341F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA9F8139CA7FF3E9E5AFE341F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Pekka Savola wrote:
> On Tue, 19 Jun 2007, Thomas Narten wrote:
>> And help me understand how this equates to the AS112 issues. For sites=

>> that (today) get PI space and don't actually advertise it to the
>> internet, aren't the DNS issues _exactly_ the same?
>=20
> IMHO, if reverse DNS is provided, it should be required that the
> authoritative DNS servers have non-ULA addresses.  I think Mark was
> assuming that ULA address for authoritative delegation point might be
> OK, which would lead to issues if the ULA address is not reachable from=

> everywhere where reverse DNS lookups should succeed.

What is the point of that? How can a ULA address reach a global unicast
address or for that matter, how is such a ULA address, which is most like=
ly
going to be the sole user of those reverse servers going to contact any o=
f
the root servers, .arpa servers, RIR servers etc to actually find out whe=
re
that server is located in the first place?

Are those people going to do NAT from their ULA space? Then please direct=
ly
kill this whole ULA proposal completely. If NAT is involved in anyway it
should never see daylight.

Also, registered the DNS servers in the global DNS thus means that those
machines will be Internet connected, then what is the point of ULA again?=


Another point here is that when there will be ULA registrations in the
reverse tree, then there will also be ULA AAAA's in the forward tree, oh =
boy
we are going to have a nice mess there...


I really can't see how 'registering DNS servers in the global root' is go=
ing
to be beneficial to having 'local' address space. It will only wreak a lo=
t
of problems and cause people to do NAT.

Greets,
 Jeroen



--------------enigA9F8139CA7FF3E9E5AFE341F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ4LlguFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I9vdAJ9dIZlJkbHFAgR/8I7o3o2i+btX
rgCgm0pnycpuXEUSFbnw3sILoBAi0J4=
=Q1cc
-----END PGP SIGNATURE-----

--------------enigA9F8139CA7FF3E9E5AFE341F--


--===============0002149897==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0002149897==--




From ipv6-bounces@ietf.org Tue Jun 19 15:41:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jZn-0002bK-IV; Tue, 19 Jun 2007 15:41:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jZm-0002Zt-5g
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:41:18 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0jZk-0004wV-Ei
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:41:18 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l5JJf2xH010518;
	Tue, 19 Jun 2007 22:41:02 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l5JJf2AV010515;
	Tue, 19 Jun 2007 22:41:02 +0300
Date: Tue, 19 Jun 2007 22:41:02 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <46782E58.6070705@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0706192236490.10422@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.90.3/3457/Tue Jun 19 02:54:49 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.9
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 19 Jun 2007, Jeroen Massar wrote:
> What is the point of that? How can a ULA address reach a global unicast
> address or for that matter, how is such a ULA address, which is most likely
> going to be the sole user of those reverse servers going to contact any of
> the root servers, .arpa servers, RIR servers etc to actually find out where
> that server is located in the first place?
>
> Are those people going to do NAT from their ULA space? Then please directly
> kill this whole ULA proposal completely. If NAT is involved in anyway it
> should never see daylight.

I do not know the intended deployment scenarios, but in many cases 
where I'd expect ULA-C migth be deployed, I'd expect such sites to 
have some global addresses as well for v4, v6 or both (maybe at a 
different physical site, just for a couple of infrastructure servers 
instead of all hosts, etc.)

You're right that if a ULA(-C) site would have no global addresses 
whatsoever, reverse-DNS delegations can't be done.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 15:50:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jiE-0001E6-5J; Tue, 19 Jun 2007 15:50:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jiD-0001Dq-4V
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:50:01 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0jiB-0006yz-RI
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:50:01 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5JJnwEC015917
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 19 Jun 2007 12:49:58 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5JJnwlS021943; Tue, 19 Jun 2007 12:49:58 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5JJnwOw021921; Tue, 19 Jun 2007 12:49:58 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 15:49:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2007 15:49:57 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD293@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <46782E58.6070705@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AceyqB/nadFXr3OSTqGo0hv8NPQMfgAApwkg
References: <Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>
X-OriginalArrivalTime: 19 Jun 2007 19:49:57.0990 (UTC)
	FILETIME=[04047060:01C7B2AB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]=20

> What is the point of that? How can a ULA address reach a=20
> global unicast
> address or for that matter, how is such a ULA address, which=20
> is most likely
> going to be the sole user of those reverse servers going to=20
> contact any of
> the root servers, .arpa servers, RIR servers etc to actually=20
> find out where
> that server is located in the first place?

[ ... ]

> Another point here is that when there will be ULA registrations in the
> reverse tree, then there will also be ULA AAAA's in the=20
> forward tree, oh boy
> we are going to have a nice mess there...

Jeoren, what about this quote from the draft:

4.1 DNS Issues

   AAAA and PTR records for centrally assigned local IPv6 addresses may
   be installed in the global DNS.  This may be useful if these
   addresses are being used for site to site or VPN style applications,
   or for sites that wish to avoid separate DNS systems for inside and
   outside traffic.

   The operational issues relating to this are beyond the scope of this
   document.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 15:51:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jjv-00055J-Jv; Tue, 19 Jun 2007 15:51:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jjK-0003TO-5u; Tue, 19 Jun 2007 15:51:10 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I0jjC-0002Or-L4; Tue, 19 Jun 2007 15:51:10 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 2C27C2ACC3;
	Tue, 19 Jun 2007 19:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I0jiE-0004mX-MF; Tue, 19 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I0jiE-0004mX-MF@stiedprstage1.ietf.org>
Date: Tue, 19 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: ipv6@ietf.org
Subject: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: Centrally Assigned Unique Local IPv6 Unicast Addresses
	Author(s)	: R. Hinden, et al.
	Filename	: draft-ietf-ipv6-ula-central-02.txt
	Pages		: 11
	Date		: 2007-6-18
	
This document defines Centrally allocated IPv6 Unique Local
   addresses.  These addresses are globally unique and are intended for
   local communications, usually inside of a site.  They are not
   expected to be routable on the global Internet.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ipv6-ula-central-02.txt".

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

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

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-ipv6-ula-central-02.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--NextPart--




From ipv6-bounces@ietf.org Tue Jun 19 15:53:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jlN-0008RD-Pn; Tue, 19 Jun 2007 15:53:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0jlL-0008PP-FF
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:53:15 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0jl8-0007lX-5H
	for ipv6@ietf.org; Tue, 19 Jun 2007 15:53:15 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5JJr1lb018177
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 19 Jun 2007 12:53:01 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5JJr1V4004005; Tue, 19 Jun 2007 14:53:01 -0500 (CDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5JJr0ZG003996; Tue, 19 Jun 2007 14:53:00 -0500 (CDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 15:53:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2007 15:53:00 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD294@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA9015AD293@XCH-NE-1V2.ne.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AceyqB/nadFXr3OSTqGo0hv8NPQMfgAApwkgAAAmBrA=
References: <Pine.LNX.4.64.0706192211570.9840@netcore.fi><46782E58.6070705@spaghetti.zurich.ibm.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD293@XCH-NE-1V2.ne.nos.boeing.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>
X-OriginalArrivalTime: 19 Jun 2007 19:53:00.0639 (UTC)
	FILETIME=[70E276F0:01C7B2AB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Jeoren, what about this quote from the draft:

Sorry I mutilated your name again!

Jeroen.

Bert

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 16:11:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0k2Z-0007qE-Cl; Tue, 19 Jun 2007 16:11:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0k2X-0007pl-OE
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:11:01 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0k2X-0003ac-EX
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:11:01 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 19 Jun 2007 15:11:00 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A06314106670704A@mail>
In-Reply-To: <Pine.LNX.4.64.0706192236490.10422@netcore.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
Thread-Index: AceyqfVo5YPAeF1sSv2maDfNH4WbYgAAig6w
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Subject: RE: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I fail to see the point of mandating non-routable space with allocated
ULA-C.  Any network administrator has the ability and freedom to not
route as much or as little of their PI space as they want.   Why force
constraints on usage?

If they are going to link two physically seperated sites (into a WLAN or
MLAN for example) with 'private' IP's then isn't that just access-listed
PI?

Please explain to me what you could do with ULA-C that you can't do with
PI and an ACL.  I really want to understand.

The only possible use I can figure is so that soho router manufacturers
can have something to hard-code in to their LAN/DHCP defaults, but even
then there would have to be a subnet parameter passed to the router by
DHCP unless one was going to assume that the WAN network was the entire
PI space.

Thanks in advance for the constructive education.

Kevin




> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]=20
> Sent: Tuesday, June 19, 2007 2:41 PM
> To: Jeroen Massar
> Cc: Thomas Narten; Mark Andrews; ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
>=20
> On Tue, 19 Jun 2007, Jeroen Massar wrote:
> > What is the point of that? How can a ULA address reach a global=20
> > unicast address or for that matter, how is such a ULA=20
> address, which=20
> > is most likely going to be the sole user of those reverse servers=20
> > going to contact any of the root servers, .arpa servers,=20
> RIR servers=20
> > etc to actually find out where that server is located in=20
> the first place?
> >
> > Are those people going to do NAT from their ULA space? Then please=20
> > directly kill this whole ULA proposal completely. If NAT is=20
> involved=20
> > in anyway it should never see daylight.
>=20
> I do not know the intended deployment scenarios, but in many=20
> cases where I'd expect ULA-C migth be deployed, I'd expect=20
> such sites to have some global addresses as well for v4, v6=20
> or both (maybe at a different physical site, just for a=20
> couple of infrastructure servers instead of all hosts, etc.)
>=20
> You're right that if a ULA(-C) site would have no global=20
> addresses whatsoever, reverse-DNS delegations can't be done.
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 16:13:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0k4s-00008y-A5; Tue, 19 Jun 2007 16:13:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0k4r-00008J-6K
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:13:25 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0k4p-00041x-Pw
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:13:25 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id C83051A4D80; Tue, 19 Jun 2007 13:12:32 -0700 (PDT)
Date: Tue, 19 Jun 2007 13:12:32 -0700
From: bill fumerola <billf@mu.org>
To: Jeroen Massar <jeroen@unfix.org>
Message-ID: <20070619201232.GZ31273@elvis.mu.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<4677FC3C.3050507@spaghetti.zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4677FC3C.3050507@spaghetti.zurich.ibm.com>
User-Agent: Mutt/1.4.2.2i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, Jun 19, 2007 at 04:54:36PM +0100, Jeroen Massar wrote:
> When the prefix is 'local' why would that need to be rooted into the global
> Internet? I get the point about having unique addresses out of the same
> namespace, but I don't get why reverses then have to be supplied too.

1) by putting it in the global space, every single recursive dns server
in an organization doesn't have to special case (read: slave or conditional
forwarding) ULA reverse zones to get accurate PTR records.

2) two (or more) different organizations who agree to use ULA-C space
(e.g. as part of a partnership) don't have to do even funkier dns tricks
than #1 to have accurate PTR records for both sides.

best of all: by delegating, we avoid the AS112 problem as well.

additionally, there is a draft going through the dnsops WG speaking to
the advantages and pitfalls of reverse dns. wherever possible we should
encourage PTR records to be accurate as possible for as many people as
possible. delegating ULA-C allocations to globally reachable nameservers
hurts no-one and can only potentially be useful information.

> What is the point of that? How can a ULA address reach a global unicast 
> address or for that matter, how is such a ULA address, which is most likely
> going to be the sole user of those reverse servers going to contact any of
> the root servers, .arpa servers, RIR servers etc to actually find out where
> that server is located in the first place?

devices on ULA addresses could contact recursive nameservers that have
a global unicast address and can resolve on their behalf. some machines
may even have both a ULA-C address AND a global address.

> Are those people going to do NAT from their ULA space? Then please directly 
> kill this whole ULA proposal completely. If NAT is involved in anyway it
> should never see daylight.

this has nothing to do with NAT, but thanks for bringing out the boogeyman.

> Also, registered the DNS servers in the global DNS thus means that those 
> machines will be Internet connected, then what is the point of ULA again? 

the delegation should be to global unicast space, not to ULA-C space.

you'll have to find another reason to ask "what's the point?", i guess.

> reverse tree, then there will also be ULA AAAA's in the forward tree, oh boy 
> we are going to have a nice mess there... 
                                                   
people put RFC1918 addresses in A records today and the internet hasn't
imploded as a result yet. if you're a partner of mine, lookup an RFC1918
address i have in the global dns, and you can reach that address through
a prefix i give you as part of our partnership: that RFC1918 record in
the global DNS is useful to you. what's the difference between that and
ULA-C, besides the fact that i don't have to worry about which company's
network addressing tomorrow's merger/acquisition/partnership/etc uses..
like i do with RFC1918.

if you have no relationship with me (or my potential ULA-C space) then
what does it matter to you if i put ULA-C addresses in my forward zones
or have my reverse ULA-C space delegated to a globally reachable server.

i have a great counter-argument: since routing slots are oh so valuable
and are driving policy decisions (e.g. minimum allocation size in ARIN)
and engineering efforts (e.g. SOMEONE MIGHT LEAK ULA-C!), perhaps malloc()
slots in your DNS servers are so important that you might inadvertantly
cache one of my records that points to space you can't reach. in the
interest of the memory footprint DNS servers everywhere we can't allow
ULA[-C] addresses to ever be in the global dns space!

-- 
- bill fumerola / billf@FreeBSD.org



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 16:16:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0k77-0001WV-6l; Tue, 19 Jun 2007 16:15:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0k75-0001Uy-Qd
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:15:43 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0k73-0004Wl-R6
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:15:43 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 4A332140C085;
	Tue, 19 Jun 2007 22:15:39 +0200 (CEST)
Message-ID: <4678396E.4000204@spaghetti.zurich.ibm.com>
Date: Tue, 19 Jun 2007 21:15:42 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706192236490.10422@netcore.fi>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2021863538=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2021863538==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9F89C900AA2CD538287DBF29"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9F89C900AA2CD538287DBF29
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Manfredi, Albert E wrote:

> Jeroen, what about this quote from the draft:
>
> Sorry I mutilated your name again!

Don't worry about that, that happens everywhere (even I typo it) ;)

> 4.1 DNS Issues
>
>    AAAA and PTR records for centrally assigned local IPv6 addresses may=

>    be installed in the global DNS.  This may be useful if these
>    addresses are being used for site to site or VPN style applications,=

>    or for sites that wish to avoid separate DNS systems for inside and
>    outside traffic.
>
>    The operational issues relating to this are beyond the scope of this=

>    document.

Not to mean it nastily but shoving the problem off to something else is a=

very easy thing to do. If the ULA-C draft is going to define support for =
DNS
then it should also mention all the known operational problems that can
occur with it. The entity that will perform the registry function is real=
ly
not going to document or figure those things out.

The above hosts are Internet connected and most likely will thus also end=
 up
talking to the Internet at one point or another. I can thus only guess th=
at
they will be wanting to fully connect to the Internet one day and the
generic solution to that problem is NAT. We wanted to get rid of NAT for
IPv6. If NAT is again being done for IPv6 then we can just as well give u=
p
and just keep on using IPv4 as there really is not a single advantage the=
n
anymore to IPv6.

But see below for a scenario that might have actual merit here.

Pekka Savola wrote:
[..]
> I do not know the intended deployment scenarios

And this is the whole problem with ULA-C from what I see.

What are the intended deployment scenarios?
Or to put it better: what is the problem that needs to be solved?

I explicitly noted the drafts existence and instructions how people can a=
nd
that they should comment on this, I still have to see a mostly-RIR person=

coming up with their views, or better somebody (and rather multiple) folk=
s
that actually want to use it.

ULA (rfc4193) solves the problem of a "routed dental office", pop your bo=
xes
out of the truck, plugin a ULA-capable router box in the middle et presto=
 it
works. This is also already partially what link-locals solve, but those
don't work in a routed manner.

But what is ULA-C supposed to solve, especially in light that "IPv6 PI"
exists and is fairly easy to get?

> but in many cases where
> I'd expect ULA-C migth be deployed, I'd expect such sites to have some
> global addresses as well for v4, v6 or both (maybe at a different
> physical site, just for a couple of infrastructure servers instead of
> all hosts, etc.)

In case you have 'infrastructure servers', aka your local DNS, then it
becomes very easy to let them return answers for your local ip6.arpa tree=
,
just add the zone as a master. No need for configuring

So, lets assume I have a ULA-C address, how exactly am I going to look up=

the reverse? I need to have some kind of global address. When I have a
global address then what is the whole point of ULA, as I am connected alr=
eady.


**SCENARIO**
One possible scenario could maybe be: use ULA-C local in your local site,=

use global (PA) addresses from the upstream ISP, from whom you get a /48
too, thus the number plan is the same, just different first 48 bits. Ever=
y
host gets a ULA and a PA address. The PA address might change when changi=
ng
ISP. RFC3484 and related work can be used to configure preferring what
address to use. Then you never need to reconfigure your local network and=

local addresses are globally unique and can use the Internet.

The big thing there is though: configure your firewalls correctly as the
public addresses do also allow access to everything.

Still, the above can also be accomplished perfectly fine with PI space an=
d
that doesn't require any changes (except RIPE+APNIC policy) to be done.

> You're right that if a ULA(-C) site would have no global addresses
> whatsoever, reverse-DNS delegations can't be done.

The above example demonstrates that indeed.

Another funny thing there to note is that some people might want to use
ULA-C to 'hide' their infrastructure, as it will be completely disconnect=
ed
from the Internet. By introducing reverse dns though, those queries will =
be
ending up at several DNS servers on the big bad public internet. Of cours=
e
the NS record will be cached, but some information does get leaked.

Greets,
 Jeroen



--------------enig9F89C900AA2CD538287DBF29
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ4OW4uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I4o/AKC15aev9AzDn2lVjx1L+BjNXxN+
gQCgsccvzmB2mxBy9K91xWeicJKKG9Y=
=1r0/
-----END PGP SIGNATURE-----

--------------enig9F89C900AA2CD538287DBF29--


--===============2021863538==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============2021863538==--




From ipv6-bounces@ietf.org Tue Jun 19 16:48:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0kcm-0003xE-Qo; Tue, 19 Jun 2007 16:48:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0kcl-0003x1-Sz
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:48:27 -0400
Received: from e34.co.us.ibm.com ([32.97.110.152])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0kcN-00060f-IF
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:48:27 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e34.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5JKm3d9004862
	for <ipv6@ietf.org>; Tue, 19 Jun 2007 16:48:03 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5JKm2KB183324 for <ipv6@ietf.org>; Tue, 19 Jun 2007 14:48:02 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5JKm2Gc031332 for <ipv6@ietf.org>; Tue, 19 Jun 2007 14:48:02 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-161-227.wecm.ibm.com
	[9.67.161.227])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5JKm015028944
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 19 Jun 2007 14:48:02 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5JKkixT015605;
	Tue, 19 Jun 2007 16:47:04 -0400
Message-Id: <200706192047.l5JKkixT015605@cichlid.raleigh.ibm.com>
To: Pekka Savola <pekkas@netcore.fi>
In-reply-to: <Pine.LNX.4.64.0706192211570.9840@netcore.fi> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
Comments: In-reply-to Pekka Savola <pekkas@netcore.fi>
	message dated "Tue, 19 Jun 2007 22:14:13 +0300."
Date: Tue, 19 Jun 2007 16:46:44 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Mark Andrews <Mark_Andrews@isc.org>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Pekka Savola <pekkas@netcore.fi> writes:

> On Tue, 19 Jun 2007, Thomas Narten wrote:
> > And help me understand how this equates to the AS112 issues. For sites
> > that (today) get PI space and don't actually advertise it to the
> > internet, aren't the DNS issues _exactly_ the same?

> IMHO, if reverse DNS is provided, it should be required that the 
> authoritative DNS servers have non-ULA addresses.

For the glue records? Absolutely. Well, actually, this discussion
may need to be nuanced. The requirement should be that that if there
is a PTR record (i.e., with a delegation chain starting at
in-addr.arpa), the authoritative servers that would be traversed in
chasing down the record must all be globally reachable. That probably
means non-ULA addresses, though there might be some edge cases.

> I think Mark was assuming that ULA address for authoritative
> delegation point might be OK, which would lead to issues if the ULA
> address is not reachable from everywhere where reverse DNS lookups
> should succeed.

Not acceptable to have glue records that contain addresses that are not
generally reachable. The DNS is not designed to operate efficiently in
such an environment.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 16:56:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0kke-00018n-Go; Tue, 19 Jun 2007 16:56:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0kkd-00018h-Pp
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:56:35 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0kkc-0008M4-Dv
	for ipv6@ietf.org; Tue, 19 Jun 2007 16:56:35 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 21:56:33 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2007 21:57:53 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <Pine.LNX.4.64.0706192211570.9840@netcore.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: AceypjZdtuOVRtK6S5KXkArWHgpbDgADZIRg
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 19 Jun 2007 20:56:33.0798 (UTC)
	FILETIME=[51B45A60:01C7B2B4]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: RE: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> IMHO, if reverse DNS is provided, it should be required that=20
> the authoritative DNS servers have non-ULA addresses.=20

Not only that, but since the goal of ULA-C addresses is to provide
something similar to what site-local was going to be, perhaps the RIRs
should operate authoritative reverse DNS servers for the entire ULA-C
space to ensure that reverse DNS for ULA-C addresses is permanently
broken on the public Internet. Of course, anyone who wants to run their
own internal reverse DNS in their own private network, or networks,
should feel free to do so.

Is the goal of this document merely to define the ULA-C address range
well enough to throw it into the lake and see if it sinks or swims? Or
is there some requirement to provide a more workable form of site-local
addresses?

--Michael Dillon

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 17:48:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0lXs-0001Rf-Ja; Tue, 19 Jun 2007 17:47:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0lXr-0001RV-1S
	for ipv6@ietf.org; Tue, 19 Jun 2007 17:47:27 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0lXp-0004oa-KL
	for ipv6@ietf.org; Tue, 19 Jun 2007 17:47:27 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5JLlN7T017541 for <ipv6@ietf.org>; Wed, 20 Jun 2007 00:47:23 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 00:47:22 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 00:47:22 +0300
Received: from [172.19.74.177] (dadhcp-172019074177.americas.nokia.com
	[172.19.74.177])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5JLlKXl028108 for <ipv6@ietf.org>; Wed, 20 Jun 2007 00:47:21 +0300
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <21CA6AAA-E88E-4763-B8A9-AD6A4D0A73E0@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Tue, 19 Jun 2007 14:47:19 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 19 Jun 2007 21:47:22.0464 (UTC)
	FILETIME=[6AD9DE00:01C7B2BB]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> Is the goal of this document merely to define the ULA-C address range
> well enough to throw it into the lake and see if it sinks or swims? Or
> is there some requirement to provide a more workable form of site- 
> local
> addresses?

The central ULA's should to be viewed in contrast to the currently  
defined locally assigned ULAs (RFC4193).  They share almost  all of  
the properties except for the degree of uniqueness (and, of course,  
the ability to self-generate the prefix).  Central ULA's are  
guranteed to be unique vs. locally assigned ULA have a very high  
probability of uniqueness.  Centrally assigned ULA's are for  
organizations that need an absolute guarantee of uniqueness, not just  
a very high probability.  This applies to large enterprises who want  
to use these internally and for private connections to other  
enterprises, and for usage currently being discussed in the RIR  
community.

Bob






--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:07:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0lrc-0002dN-TJ; Tue, 19 Jun 2007 18:07:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0lrb-0002dI-TI
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:07:51 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0lrZ-0002Rq-Ek
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:07:51 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84652152 for ipv6@ietf.org;
	Tue, 19 Jun 2007 18:07:48 -0400
Message-ID: <467853B0.5010806@internap.com>
Date: Tue, 19 Jun 2007 15:07:44 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipv6@ietf.org
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Here's a use case for ULA-C that demonstrates its usefulness, and 
demonstrates why reverse DNS for ULA-C blocks is a valuable enough 
service that we shouldn't purposefully break it for the public 
Internet.  Let's say, for example, that I'm a very small ISP with IPv6 
PA space from my upstream(s).  I give out subnets of that PA space to my 
customers in an automated dynamic fashion, and I don't run BGP, so I 
don't need or want PI space.

However, I do have some routers with interfaces that need numbering, and 
I'd rather avoid renumbering them when I change upstreams.  Since ULA-C 
is cheap and easy to get, I register myself a block of it, and use it to 
number my router interfaces.  Since I'd rather my customers saw DNS 
names instead of IPv6 addresses in their traceroutes, I delegate the 
reverse DNS for my ULA-C block to a nameserver on my upstream's PA 
space, and set up proper PTR records for all my routers.

Now, whenever anyone does a traceroute into or out of my network, 
they'll see ULA-C addresses in the traceroute.  They don't need to 
actually reach those addresses if they're not in my network, but they 
will at least be able to resolve PTR records for them, so that the 
traceroute cleanly shows whose network they're traversing.

And whenever I decide to switch upstreams, all I have to do is update my 
DHCP servers, update my nameserver's A record to an IP out of my new 
upstream's PA space, and we're done.  I don't have to renumber a single 
router, I don't have to run BGP, and I don't have to litter the DFZ with 
another PI block.

-Scott

michael.dillon@bt.com wrote:
>> IMHO, if reverse DNS is provided, it should be required that 
>> the authoritative DNS servers have non-ULA addresses. 
>>     
>
> Not only that, but since the goal of ULA-C addresses is to provide
> something similar to what site-local was going to be, perhaps the RIRs
> should operate authoritative reverse DNS servers for the entire ULA-C
> space to ensure that reverse DNS for ULA-C addresses is permanently
> broken on the public Internet. Of course, anyone who wants to run their
> own internal reverse DNS in their own private network, or networks,
> should feel free to do so.
>
> Is the goal of this document merely to define the ULA-C address range
> well enough to throw it into the lake and see if it sinks or swims? Or
> is there some requirement to provide a more workable form of site-local
> addresses?
>
> --Michael Dillon
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>   

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:14:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0lyA-0001L7-DF; Tue, 19 Jun 2007 18:14:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0ly8-0001L1-Ki
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:14:36 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0ly6-0003Pv-U8
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:14:36 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 8C36C140C1C6;
	Wed, 20 Jun 2007 00:14:33 +0200 (CEST)
Message-ID: <4678554C.7030603@spaghetti.zurich.ibm.com>
Date: Tue, 19 Jun 2007 23:14:36 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
In-Reply-To: <467853B0.5010806@internap.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0390582406=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0390582406==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig15B55FAF069CBAAA3010C597"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig15B55FAF069CBAAA3010C597
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Scott Leibrand wrote:
[..]
> Now, whenever anyone does a traceroute into or out of my network,
> they'll see ULA-C addresses in the traceroute

Which won't work, as ULA-C's are not in the routing tables, they won't pa=
ss
uRPF checks and thus those packets of yours will get dropped to the floor=
=2E

These packets will include ICMP Packet Too Big, and when those get droppe=
d,
your network is broken, which actually is caused by the usage of a LOCAL
prefix on the Internet.


Maybe a fist addendum that has to be made: ULA(-C) *MUST* never appear on=

the wire on the global Internet.

If you do that anyway, you simply will cause your network to break:

When you got gear you are going to attach to the internet request a PI or=
 a
PA block and use a global unicast address.

Greets,
 Jeroen


--------------enig15B55FAF069CBAAA3010C597
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ4VUwuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I/7yAJkBMsqbfwzV6FRBjOvJBQZw6J7m
lQCfQXeLpZsMPUQo9flpmw15Brv9sic=
=6avk
-----END PGP SIGNATURE-----

--------------enig15B55FAF069CBAAA3010C597--


--===============0390582406==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0390582406==--




From ipv6-bounces@ietf.org Tue Jun 19 18:20:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0m44-0006e4-9y; Tue, 19 Jun 2007 18:20:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0m42-0006dy-AB
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:20:42 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0m41-0005iB-2b
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:20:42 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5JMKeww028243
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 19 Jun 2007 17:20:40 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5JMKeOD013484; Tue, 19 Jun 2007 17:20:40 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5JMKSVG012987; Tue, 19 Jun 2007 17:20:38 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 15:20:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2007 15:20:34 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8A6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <4678554C.7030603@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Aceyv1MNDZtml9JbQ+SVtAMEZmOZ6QAAFdHQ
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com>
	<4678554C.7030603@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>,
	"Scott Leibrand" <sleibrand@internap.com>
X-OriginalArrivalTime: 19 Jun 2007 22:20:35.0936 (UTC)
	FILETIME=[0F0D8E00:01C7B2C0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> When you got gear you are going to attach to the internet=20

Which Internet? The existing IPv4 one, or a future IPv6 one?

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:24:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0m7U-0000I6-F5; Tue, 19 Jun 2007 18:24:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0m7T-0000I1-AU
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:24:15 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0m7R-0006J0-VQ
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:24:15 -0400
Received: from [192.168.2.103] (blobby.bind.org [82.92.138.66])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5JMOAL4028912
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 19 Jun 2007 15:24:12 -0700
In-Reply-To: <467853B0.5010806@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Wed, 20 Jun 2007 00:23:46 +0200
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20 Jun 2007, at 12:07am, Scott Leibrand wrote:

> Here's a use case for ULA-C that demonstrates its usefulness, and  
> demonstrates why reverse DNS for ULA-C blocks is a valuable enough  
> service that we shouldn't purposefully break it for the public  
> Internet.  Let's say, for example, that I'm a very small ISP with  
> IPv6 PA space from my upstream(s).  I give out subnets of that PA  
> space to my customers in an automated dynamic fashion, and I don't  
> run BGP, so I don't need or want PI space.
>
> However, I do have some routers with interfaces that need  
> numbering, and I'd rather avoid renumbering them when I change  
> upstreams.  Since ULA-C is cheap and easy to get, I register myself  
> a block of it, and use it to number my router interfaces.  Since  
> I'd rather my customers saw DNS names instead of IPv6 addresses in  
> their traceroutes, I delegate the reverse DNS for my ULA-C block to  
> a nameserver on my upstream's PA space, and set up proper PTR  
> records for all my routers.

Is this not already possible with a /48 PI assignment from ARIN?

Is ULA-C a new solution for a problem that's already been solved with  
PI assignments or does it solve a new problem?

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:36:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0mJI-0003su-WE; Tue, 19 Jun 2007 18:36:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0mJI-0003sm-0Y
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:36:28 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0mJG-0001oH-Oq
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:36:27 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84653544; Tue, 19 Jun 2007 18:36:26 -0400
Message-ID: <46785A65.7060505@internap.com>
Date: Tue, 19 Jun 2007 15:36:21 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
In-Reply-To: <2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Leo Vegoda wrote:
> On 20 Jun 2007, at 12:07am, Scott Leibrand wrote:
>
>> Here's a use case for ULA-C that demonstrates its usefulness, and 
>> demonstrates why reverse DNS for ULA-C blocks is a valuable enough 
>> service that we shouldn't purposefully break it for the public 
>> Internet.  Let's say, for example, that I'm a very small ISP with 
>> IPv6 PA space from my upstream(s).  I give out subnets of that PA 
>> space to my customers in an automated dynamic fashion, and I don't 
>> run BGP, so I don't need or want PI space.
>>
>> However, I do have some routers with interfaces that need numbering, 
>> and I'd rather avoid renumbering them when I change upstreams.  Since 
>> ULA-C is cheap and easy to get, I register myself a block of it, and 
>> use it to number my router interfaces.  Since I'd rather my customers 
>> saw DNS names instead of IPv6 addresses in their traceroutes, I 
>> delegate the reverse DNS for my ULA-C block to a nameserver on my 
>> upstream's PA space, and set up proper PTR records for all my routers.
>
> Is this not already possible with a /48 PI assignment from ARIN?
Yes, but only if you "qualify for an IPv4 assignment or allocation from 
ARIN under the IPv4 policy currently in effect."  That currently means 
you must either be a large network (qualifying for a /20), or you must 
be large enough to run BGP, be multi-homed, and be large enough to 
justify a /22.
>
> Is ULA-C a new solution for a problem that's already been solved with 
> PI assignments or does it solve a new problem?
>
>
I believe there is a gap between the current PI policy, which is 
targeted at organizations large enough to qualify for a routing slot, 
and the need many smaller organizations have for their own IP space for 
various internal uses. Some of those organizations will be happy to use 
ULA-L, but some will need a guarantee of uniqueness and the ability to 
list their IP space in DNS (.arpa) and in whois.  If we can meet the 
needs of those organizations without having to relax the requirements 
for PI space, we can reduce future pressure on the DFZ.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:43:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0mPk-0000ox-6L; Tue, 19 Jun 2007 18:43:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0mPi-0000oA-W6
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:43:07 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0mPh-0003WH-Pn
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:43:06 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84653901; Tue, 19 Jun 2007 18:43:05 -0400
Message-ID: <46785BE7.5040809@internap.com>
Date: Tue, 19 Jun 2007 15:42:47 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com>
	<4678554C.7030603@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8A6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8A6@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Templin, Fred L wrote:
>> Which won't work, as ULA-C's are not in the routing tables, they won't pass
>> uRPF checks and thus those packets of yours will get dropped to the floor.
>>
>> When you got gear you are going to attach to the internet request a PI or a
>> PA block and use a global unicast address.
>
> Which Internet? The existing IPv4 one, or a future IPv6 one?
>
>   
Or, to ask the question another way, does it make sense to use uRPF to 
drop packets sourced from ULA-C blocks?  Our current implementations of 
loose uRPF are rooted in IPv4 justifications, most notably that private 
IP space (RFC 1918) is non-unique, so we have no idea where the packet 
came from, so we might as well drop it.  I'm not sure that applies in 
the IPv6 world, where an ICMP packet can be sourced from ULA-C space or 
non-routed PI space and can have perfectly valid DNS and whois 
information associated with its source address.

-Scott


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 18:56:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0mcW-0002us-Fx; Tue, 19 Jun 2007 18:56:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0mcV-0002tt-3s
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:56:19 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0mcU-0005VH-4q
	for ipv6@ietf.org; Tue, 19 Jun 2007 18:56:19 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 96C21140C1D9;
	Wed, 20 Jun 2007 00:56:15 +0200 (CEST)
Message-ID: <46785F13.3020205@spaghetti.zurich.ibm.com>
Date: Tue, 19 Jun 2007 23:56:19 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com>
	<4678554C.7030603@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8A6@XCH-NW-7V2.nw.nos.boeing.com>
	<46785BE7.5040809@internap.com>
In-Reply-To: <46785BE7.5040809@internap.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1535316078=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1535316078==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig74950721B1D5A08925BA71D7"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig74950721B1D5A08925BA71D7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Scott Leibrand wrote:
> Templin, Fred L wrote:
>>> Which won't work, as ULA-C's are not in the routing tables, they
>>> won't pass
>>> uRPF checks and thus those packets of yours will get dropped to the
>>> floor.
>>>
>>> When you got gear you are going to attach to the internet request a
>>> PI or a
>>> PA block and use a global unicast address.
>>
>> Which Internet? The existing IPv4 one, or a future IPv6 one?

That common thing that is commonly present in ISP tables.

Now if ULA-C becomes part of that, then it is not 'local' anymore of cour=
se
and we just have another form of PI.

> Or, to ask the question another way, does it make sense to use uRPF to
> drop packets sourced from ULA-C blocks?

I refer you to BCP38 for a LOT of reasons on why to enable uRPF checks.
One of those is the most common one: spoofing.

> Our current implementations of loose uRPF are rooted in IPv4 justificat=
ions,
> most notably that private IP space (RFC 1918) is non-unique, so we have=
 no
> idea where the packet came from, so we might as well drop it.

And do you have any idea at all where ULA-C packets come from?
Can you send return packets to them?

Remember, that ULA addresses should not be present at all on that generic=

thing that people call the Internet.

Or is spoofing again very happily allowed.

Also please take into consideration the recent quibble over RH0. Networks=

which do proper uRPF checks didn't have any problems with these packets a=
s
those packets would never be able to pingpong on those networks simply
because of a wrong source address.

> I'm not sure that applies in
> the IPv6 world, where an ICMP packet can be sourced from ULA-C space or=

> non-routed PI space and can have perfectly valid DNS and whois
> information associated with its source address.

Since when do routers look in DNS and whois?

If they would do that we would have id/loc, now that would be great.

Scott Leibrand wrote:
>> Leo Vegoda wrote:
>> Is this not already possible with a /48 PI assignment from ARIN?
>
> Yes, but only if you "qualify for an IPv4 assignment or allocation from=

> ARIN under the IPv4 policy currently in effect."  That currently means
> you must either be a large network (qualifying for a /20), or you must
> be large enough to run BGP, be multi-homed, and be large enough to
> justify a /22.

Then change the RIR policy, don't go invent some strange address type tha=
t
will only cause problems in the end and will just be a surrogate PI space=
=2E

RIR's should be giving out address space on the justification of NEED by =
the
requesting organization, not by the need to control routing entries becau=
se
some ISP's are scared of having to upgrade their routers.

If that latter group is scared, filter out the PI blocks and everything y=
ou
don't want to see and let those folks pay you for a slot in your routing =
tables.

Anything that is going to be connected one way or the other today, tomorr=
ow
or possibly somewhere in the future to that that called 'the Internet' ak=
a
the stuff using global unicast space should steer far and clear from ULA.=


Greets,
 Jeroen


--------------enig74950721B1D5A08925BA71D7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ4XxMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I0T1AJ9BuD8hGP1mQjFEEr5z0skrjl1Z
eACgo4Mc29Bw3aEN5YrPZDdoVr/bl34=
=0ga/
-----END PGP SIGNATURE-----

--------------enig74950721B1D5A08925BA71D7--


--===============1535316078==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1535316078==--




From ipv6-bounces@ietf.org Tue Jun 19 19:34:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0nD3-0005XD-Ce; Tue, 19 Jun 2007 19:34:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0nD1-0005Wz-VM
	for ipv6@ietf.org; Tue, 19 Jun 2007 19:34:03 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0nD0-0003HM-Co
	for ipv6@ietf.org; Tue, 19 Jun 2007 19:34:03 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5JNXwK4006290;
	Wed, 20 Jun 2007 09:33:59 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706192333.l5JNXwK4006290@drugs.dv.isc.org>
To: Thomas Narten <narten@us.ibm.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Tue, 19 Jun 2007 11:23:27 -0400."
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com> 
Date: Wed, 20 Jun 2007 09:33:58 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> > 4.1 DNS Issues
> 
> >    AAAA and PTR records for centrally assigned local IPv6 addresses may
> >    be installed in the global DNS.  This may be useful if these
> >    addresses are being used for site to site or VPN style applications,
> >    or for sites that wish to avoid separate DNS systems for inside and
> >    outside traffic.
> 
> >    The operational issues relating to this are beyond the scope of this
> >    document.
> 
> > 	We have to be *very* careful here.  If we allow PTR's to
> > 	be installed in the global DNS then globally reachable
> > 	nameservers *have* to exist for each prefix allocated.
> > 	Otherwise the problems that the AS112 project is trying to
> > 	deal with will appear here as well.
> 
> > 	This is a long term operational cost associated with ULA-C.
> 
> Well, please expand on this so we can discuss in more detail.
> 
> My assumption is that some (but not all) ULA-C holders will want to be
> able to have PTR records. This seems operationally useful to me, for
> those that choose to use them and place them in the public DNS
> tree. Thus, we shouldn't ban it outright. That is, the question is
> whether the RIRs then would need to support the creation of such
> records for registered ULA-C owners.
> 
> And help me understand how this equates to the AS112 issues. For sites
> that (today) get PI space and don't actually advertise it to the
> internet, aren't the DNS issues _exactly_ the same?

	Yes they are similar but I suspect that the scale of traffic
	will differ markedly.

	One thing I can be certain of.  There will be reverse queries for
	ULA-C space.  A lot of these queries will originate from sites
	using ULA-C but have not setup nameservers to intercept those
	queries because they don't care about the reverse mappings.
	
	Shifting the NXDOMAIN load from the servers for C.F.IP6.ARPA
	will be harder than shifting the load from the IN-ADDR.ARPA
	servers for 10.IN-ADDR.ARPA was because C.F.IP6.ARPA will
	be in use and the NXDOMAIN load will be randomly spread
	below C.F.IP6.ARPA.

	I also believe that most but not all of the sites using
	ULA-C will have other routable space.  Requiring that some
	of the servers are not ULA-C is not a excessive burden.

	Failure to supply nameservers is cost shifting which we
	should not be encouraging.

	I really don't want to have to add C.F.IP6.ARPA to the list
	of namespaces in draft-ietf-dnsop-default-local-zones.  We will
	have failed with ULA-C if that occurs.

	Mark

> Thomas
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 20:13:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0no6-0004x2-KN; Tue, 19 Jun 2007 20:12:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0no5-0004wu-C8
	for ipv6@ietf.org; Tue, 19 Jun 2007 20:12:21 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0no5-0003I9-2Z
	for ipv6@ietf.org; Tue, 19 Jun 2007 20:12:21 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84657241; Tue, 19 Jun 2007 20:12:19 -0400
Message-ID: <467870DC.2030802@internap.com>
Date: Tue, 19 Jun 2007 17:12:12 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
In-Reply-To: <4678396E.4000204@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar wrote:

> The above hosts are Internet connected and most likely will thus also 
> end up
> talking to the Internet at one point or another. I can thus only guess that
> they will be wanting to fully connect to the Internet one day and the
> generic solution to that problem is NAT. We wanted to get rid of NAT for
> IPv6. If NAT is again being done for IPv6 then we can just as well give up
> and just keep on using IPv4 as there really is not a single advantage then
> anymore to IPv6.
>
>   
I think what we wanted to get rid of in IPv6 was one-to-many NAT, also 
know as PAT (among other names).  In IPv6, we can stick to one-to-one 
NAT, which eliminates most of the nastiness we associate with NAT in 
today's IPv4 world.

> But see below for a scenario that might have actual merit here.
>   

> **SCENARIO**
> One possible scenario could maybe be: use ULA-C local in your local site,
> use global (PA) addresses from the upstream ISP, from whom you get a /48
> too, thus the number plan is the same, just different first 48 bits. Every
> host gets a ULA and a PA address. The PA address might change when changing
> ISP. RFC3484 and related work can be used to configure preferring what
> address to use. Then you never need to reconfigure your local network and
> local addresses are globally unique and can use the Internet.
>
> The big thing there is though: configure your firewalls correctly as the
> public addresses do also allow access to everything.
>   
I don't think routers are at the point yet where you can easily renumber 
your routers' interfaces when your PA addresses change.  As a result, 
networks wanting to avoid the pain of renumbering, but who don't qualify 
for PI and a global routing slot, might want to do something similar:

Say a network gets a ULA-C block, and numbers everything on their 
network out of that block.  They later connect to the Internet, and get 
a PA block from their upstream, and configure it on their border 
routers.  To avoid reconfiguring all their routers every time they 
change upstreams, they configure one-to-one NAT on their border routers, 
such that every address on their internal network (which is ULA-C) maps 
to the same address, except with different first 48 bits, in their 
provider-allocated block.

This wouldn't present the same kinds of problems you'd get from 
one-to-many NAT, but I'm sure there are some ways where this wouldn't be 
as good as PI space.  However, my first-order evaluation is that it 
would be better to have small networks achieve their provider 
independence this way, rather than by relaxing the PI rules and 
threatening the scalability of the current routing system with a large 
number of additional non-aggregatable netblocks.

Now as expressed earlier, most ULA-C use cases probably won't involve 
NAT.  But if people do elect to use NAT with ULA-C, what problems do you 
see with this kind of use of NAT?  Do you see those problems as worse 
than the problems caused by completely rejecting the original PA-only 
architecture of IPv6 in favor of PI-for-everyone?
> Still, the above can also be accomplished perfectly fine with PI space and
> that doesn't require any changes (except RIPE+APNIC policy) to be done.
>
>   
I agree that PI space, if it were widely available, would meet the same 
needs as ULA-C.  However, I think we need to be realistic that 
PI-for-everyone won't fly, and need to think creatively about ways to 
achieve the same goals (such as provider independence) in such a way 
that we don't impose more public cost than private benefit.

Another thing to consider when evaluating whether to specify something 
like ULA-C is that we can't know what kind of innovation it will make 
possible in the future.  Therefore, the question we should be asking is, 
is there any remaining reason *not* to allow networks to register ULA-C 
space?  When it was last proposed there was: it was thought that 
networks would get ULA-C and use it as PI space.  Now, since PI space is 
readily available to multihomed networks, that is much less likely.  As 
a result, I am in favor of allowing small networks to register their own 
unique private space, as this draft would do.  I can't predict how ULA-C 
will be used, but I'm confident that innovation is a good thing, and 
that we can safely open up the ULA-C sandbox to networks who wish to use it.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 20:41:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0oGR-0007NS-Bs; Tue, 19 Jun 2007 20:41:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0oGP-0007MV-KA
	for ipv6@ietf.org; Tue, 19 Jun 2007 20:41:37 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0oGO-0005w4-JP
	for ipv6@ietf.org; Tue, 19 Jun 2007 20:41:37 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5K0fX50007611;
	Wed, 20 Jun 2007 10:41:34 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
To: Scott Leibrand <sleibrand@internap.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Tue, 19 Jun 2007 17:12:12 MST."
	<467870DC.2030802@internap.com> 
Date: Wed, 20 Jun 2007 10:41:33 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: ipv6@ietf.org
Subject: Why does everyone see router renumbnering as hard?
	(was Re: draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


	I would have thought that router renumbering should be no
	harder that host renumbering.  Essentially all you are
	changing is the higher (/48 normally) prefix bits.  All
	that is required is a method to distribute the set of
	prefixes in use with a set of tags (global, deprecated,
	ula, advertise in RA, etc.).

	Everything else should flow from that set.  Firewall rules
	should be using that information as it really doesn't matter
	which global prefix a host uses to talk to the world.  They
	are all essentially equal.

	I may we be showing my ignorance here but I don't believe
	that this really is a "to hard" job.

	Mark

> Jeroen Massar wrote:
> 
> > The above hosts are Internet connected and most likely will thus also 
> > end up
> > talking to the Internet at one point or another. I can thus only guess that
> > they will be wanting to fully connect to the Internet one day and the
> > generic solution to that problem is NAT. We wanted to get rid of NAT for
> > IPv6. If NAT is again being done for IPv6 then we can just as well give up
> > and just keep on using IPv4 as there really is not a single advantage then
> > anymore to IPv6.
> >
> >   
> I think what we wanted to get rid of in IPv6 was one-to-many NAT, also 
> know as PAT (among other names).  In IPv6, we can stick to one-to-one 
> NAT, which eliminates most of the nastiness we associate with NAT in 
> today's IPv4 world.
> 
> > But see below for a scenario that might have actual merit here.
> >   
> 
> > **SCENARIO**
> > One possible scenario could maybe be: use ULA-C local in your local site,
> > use global (PA) addresses from the upstream ISP, from whom you get a /48
> > too, thus the number plan is the same, just different first 48 bits. Every
> > host gets a ULA and a PA address. The PA address might change when changing
> > ISP. RFC3484 and related work can be used to configure preferring what
> > address to use. Then you never need to reconfigure your local network and
> > local addresses are globally unique and can use the Internet.
> >
> > The big thing there is though: configure your firewalls correctly as the
> > public addresses do also allow access to everything.
> >   
> I don't think routers are at the point yet where you can easily renumber 
> your routers' interfaces when your PA addresses change.  As a result, 
> networks wanting to avoid the pain of renumbering, but who don't qualify 
> for PI and a global routing slot, might want to do something similar:
> 
> Say a network gets a ULA-C block, and numbers everything on their 
> network out of that block.  They later connect to the Internet, and get 
> a PA block from their upstream, and configure it on their border 
> routers.  To avoid reconfiguring all their routers every time they 
> change upstreams, they configure one-to-one NAT on their border routers, 
> such that every address on their internal network (which is ULA-C) maps 
> to the same address, except with different first 48 bits, in their 
> provider-allocated block.
> 
> This wouldn't present the same kinds of problems you'd get from 
> one-to-many NAT, but I'm sure there are some ways where this wouldn't be 
> as good as PI space.  However, my first-order evaluation is that it 
> would be better to have small networks achieve their provider 
> independence this way, rather than by relaxing the PI rules and 
> threatening the scalability of the current routing system with a large 
> number of additional non-aggregatable netblocks.
> 
> Now as expressed earlier, most ULA-C use cases probably won't involve 
> NAT.  But if people do elect to use NAT with ULA-C, what problems do you 
> see with this kind of use of NAT?  Do you see those problems as worse 
> than the problems caused by completely rejecting the original PA-only 
> architecture of IPv6 in favor of PI-for-everyone?
> > Still, the above can also be accomplished perfectly fine with PI space and
> > that doesn't require any changes (except RIPE+APNIC policy) to be done.
> >
> >   
> I agree that PI space, if it were widely available, would meet the same 
> needs as ULA-C.  However, I think we need to be realistic that 
> PI-for-everyone won't fly, and need to think creatively about ways to 
> achieve the same goals (such as provider independence) in such a way 
> that we don't impose more public cost than private benefit.
> 
> Another thing to consider when evaluating whether to specify something 
> like ULA-C is that we can't know what kind of innovation it will make 
> possible in the future.  Therefore, the question we should be asking is, 
> is there any remaining reason *not* to allow networks to register ULA-C 
> space?  When it was last proposed there was: it was thought that 
> networks would get ULA-C and use it as PI space.  Now, since PI space is 
> readily available to multihomed networks, that is much less likely.  As 
> a result, I am in favor of allowing small networks to register their own 
> unique private space, as this draft would do.  I can't predict how ULA-C 
> will be used, but I'm confident that innovation is a good thing, and 
> that we can safely open up the ULA-C sandbox to networks who wish to use it.
> 
> -Scott
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 21:21:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0osr-0005n5-UV; Tue, 19 Jun 2007 21:21:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0osq-0005mx-OC
	for ipv6@ietf.org; Tue, 19 Jun 2007 21:21:20 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0osp-0004mX-WB
	for ipv6@ietf.org; Tue, 19 Jun 2007 21:21:20 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5K1LGeG007901
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 11:21:17 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706200121.l5K1LGeG007901@drugs.dv.isc.org>
To: ipv6@ietf.org
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Wed, 20 Jun 2007 10:41:33 +1000."
	<200706200041.l5K0fX50007611@drugs.dv.isc.org> 
Date: Wed, 20 Jun 2007 11:21:16 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: Re: Why does everyone see router renumbnering as hard? (was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT) 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> 
> 	I would have thought that router renumbering should be no
> 	harder that host renumbering.  Essentially all you are
> 	changing is the higher (/48 normally) prefix bits.  All
> 	that is required is a method to distribute the set of
> 	prefixes in use with a set of tags (global, deprecated,
> 	ula, advertise in RA, etc.).
> 
> 	Everything else should flow from that set.  Firewall rules
> 	should be using that information as it really doesn't matter
> 	which global prefix a host uses to talk to the world.  They
> 	are all essentially equal.
> 
> 	I may we be showing my ignorance here but I don't believe
> 	that this really is a "to hard" job.
> 
> 	Mark

	
	This prompted a jabber discussion extracts of which follow.

<XXXXX> note that people who operate routers are usually all about control. automatic renumbering is scary except maybe on the edge
<marka> There is no loss of control.  It would still require a human to add a prefix to the set of prefixes in use.

<XXXXX> somebody upstream from you renumbers.  what happens?
<marka> With IPv6 I would expect that a both the new and old routes would be published for a period.  The old route would then be withdrawn.  There is plenty of addresses  space.  There is no need for instantious changes in addresses.

<XXXXX> i was talking about control.  your upstream adds new prefix, do you add automatically or do you wait for human to approve it?
<XXXXX> simiarly for your upstream withdrawing, do you withdraw automatically or ...
<marka> I would expect that there would be due notice give so that humans could be involved.

	Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 21:58:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0pT2-0004jf-Af; Tue, 19 Jun 2007 21:58:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0pT1-0004en-5h
	for ipv6@ietf.org; Tue, 19 Jun 2007 21:58:43 -0400
Received: from ns.virtualized.org ([204.152.189.134] helo=mail.virtualized.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0pSz-0002Ru-Qw
	for ipv6@ietf.org; Tue, 19 Jun 2007 21:58:43 -0400
Received: from terminus.local (ns.virtualized.org [204.152.189.134])
	by mail.virtualized.org (8.12.9p1/8.12.9) with ESMTP id l5K1eIxn047668; 
	Tue, 19 Jun 2007 18:40:26 -0700 (PDT)
	(envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service);
	Tue, 19 Jun 2007 18:58:31 -0700
X-PGP-Universal: processed;
	by terminus.local on Tue, 19 Jun 2007 18:58:31 -0700
In-Reply-To: <467870DC.2030802@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <99C2D0DF-2909-4676-93F0-8178C7D71475@virtualized.org>
From: David Conrad <drc@virtualized.org>
Date: Tue, 19 Jun 2007 18:58:22 -0700
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

On Jun 19, 2007, at 5:12 PM, Scott Leibrand wrote:
> I think what we wanted to get rid of in IPv6 was one-to-many NAT,  
> also know as PAT (among other names).  In IPv6, we can stick to one- 
> to-one NAT, which eliminates most of the nastiness we associate  
> with NAT in today's IPv4 world.

Really?

I thought the annoying bit about NAT was the fact that IP addresses  
get encoded into higher layers, thus requiring ALG or deep packet  
inspection.  One-to-one NAT would solve the NAT'd server problem, but  
I thought that was considered a feature by most networks.

Rgds,
-drc


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 22:26:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0ptZ-00057R-PG; Tue, 19 Jun 2007 22:26:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0ptZ-00057M-6Z
	for ipv6@ietf.org; Tue, 19 Jun 2007 22:26:09 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0ptY-00087o-M3
	for ipv6@ietf.org; Tue, 19 Jun 2007 22:26:09 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5K2Phlk000747
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 19 Jun 2007 19:25:43 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5K2Pdq7000743;
	Tue, 19 Jun 2007 19:25:39 -0700 (PDT)
Date: Tue, 19 Jun 2007 19:25:39 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Mark Andrews <Mark_Andrews@isc.org>
Message-ID: <20070620022539.GA26988@boreas.isi.edu>
References: <467870DC.2030802@internap.com>
	<200706200041.l5K0fX50007611@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard? (was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

 no renumbering event is "too hard" in isolation ......

 BGP peers, MRTG/CRICKET monitoring, AAAA/ACL configs, syslog all come to mind
 as issues/considerations for router renumbering.  

 and remember tht the router is the distribution engine.... of "the set
 of prefixes in use with a set of tags (global, deprecated, etc)

 one has to be very careful about "catch22 situations, deprecating the
 in use prefixes before the new prefixes are in use.

 operationally, renumbering DNS/DHCP servers is a whole lot easier.

--bill


On Wed, Jun 20, 2007 at 10:41:33AM +1000, Mark Andrews wrote:
> 
> 	I would have thought that router renumbering should be no
> 	harder that host renumbering.  Essentially all you are
> 	changing is the higher (/48 normally) prefix bits.  All
> 	that is required is a method to distribute the set of
> 	prefixes in use with a set of tags (global, deprecated,
> 	ula, advertise in RA, etc.).
> 
> 	Everything else should flow from that set.  Firewall rules
> 	should be using that information as it really doesn't matter
> 	which global prefix a host uses to talk to the world.  They
> 	are all essentially equal.
> 
> 	I may we be showing my ignorance here but I don't believe
> 	that this really is a "to hard" job.
> 
> 	Mark
> 
> > Jeroen Massar wrote:
> > 
> > > The above hosts are Internet connected and most likely will thus also 
> > > end up
> > > talking to the Internet at one point or another. I can thus only guess that
> > > they will be wanting to fully connect to the Internet one day and the
> > > generic solution to that problem is NAT. We wanted to get rid of NAT for
> > > IPv6. If NAT is again being done for IPv6 then we can just as well give up
> > > and just keep on using IPv4 as there really is not a single advantage then
> > > anymore to IPv6.
> > >
> > >   
> > I think what we wanted to get rid of in IPv6 was one-to-many NAT, also 
> > know as PAT (among other names).  In IPv6, we can stick to one-to-one 
> > NAT, which eliminates most of the nastiness we associate with NAT in 
> > today's IPv4 world.
> > 
> > > But see below for a scenario that might have actual merit here.
> > >   
> > 
> > > **SCENARIO**
> > > One possible scenario could maybe be: use ULA-C local in your local site,
> > > use global (PA) addresses from the upstream ISP, from whom you get a /48
> > > too, thus the number plan is the same, just different first 48 bits. Every
> > > host gets a ULA and a PA address. The PA address might change when changing
> > > ISP. RFC3484 and related work can be used to configure preferring what
> > > address to use. Then you never need to reconfigure your local network and
> > > local addresses are globally unique and can use the Internet.
> > >
> > > The big thing there is though: configure your firewalls correctly as the
> > > public addresses do also allow access to everything.
> > >   
> > I don't think routers are at the point yet where you can easily renumber 
> > your routers' interfaces when your PA addresses change.  As a result, 
> > networks wanting to avoid the pain of renumbering, but who don't qualify 
> > for PI and a global routing slot, might want to do something similar:
> > 
> > Say a network gets a ULA-C block, and numbers everything on their 
> > network out of that block.  They later connect to the Internet, and get 
> > a PA block from their upstream, and configure it on their border 
> > routers.  To avoid reconfiguring all their routers every time they 
> > change upstreams, they configure one-to-one NAT on their border routers, 
> > such that every address on their internal network (which is ULA-C) maps 
> > to the same address, except with different first 48 bits, in their 
> > provider-allocated block.
> > 
> > This wouldn't present the same kinds of problems you'd get from 
> > one-to-many NAT, but I'm sure there are some ways where this wouldn't be 
> > as good as PI space.  However, my first-order evaluation is that it 
> > would be better to have small networks achieve their provider 
> > independence this way, rather than by relaxing the PI rules and 
> > threatening the scalability of the current routing system with a large 
> > number of additional non-aggregatable netblocks.
> > 
> > Now as expressed earlier, most ULA-C use cases probably won't involve 
> > NAT.  But if people do elect to use NAT with ULA-C, what problems do you 
> > see with this kind of use of NAT?  Do you see those problems as worse 
> > than the problems caused by completely rejecting the original PA-only 
> > architecture of IPv6 in favor of PI-for-everyone?
> > > Still, the above can also be accomplished perfectly fine with PI space and
> > > that doesn't require any changes (except RIPE+APNIC policy) to be done.
> > >
> > >   
> > I agree that PI space, if it were widely available, would meet the same 
> > needs as ULA-C.  However, I think we need to be realistic that 
> > PI-for-everyone won't fly, and need to think creatively about ways to 
> > achieve the same goals (such as provider independence) in such a way 
> > that we don't impose more public cost than private benefit.
> > 
> > Another thing to consider when evaluating whether to specify something 
> > like ULA-C is that we can't know what kind of innovation it will make 
> > possible in the future.  Therefore, the question we should be asking is, 
> > is there any remaining reason *not* to allow networks to register ULA-C 
> > space?  When it was last proposed there was: it was thought that 
> > networks would get ULA-C and use it as PI space.  Now, since PI space is 
> > readily available to multihomed networks, that is much less likely.  As 
> > a result, I am in favor of allowing small networks to register their own 
> > unique private space, as this draft would do.  I can't predict how ULA-C 
> > will be used, but I'm confident that innovation is a good thing, and 
> > that we can safely open up the ULA-C sandbox to networks who wish to use it.
> > 
> > -Scott
> > 
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 19 22:27:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0puY-0005cp-Iw; Tue, 19 Jun 2007 22:27:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0puX-0005ZS-DP
	for ipv6@ietf.org; Tue, 19 Jun 2007 22:27:09 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0puV-0008Go-VR
	for ipv6@ietf.org; Tue, 19 Jun 2007 22:27:09 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5K2QcEF000890
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 19 Jun 2007 19:26:38 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5K2QcLU000889;
	Tue, 19 Jun 2007 19:26:38 -0700 (PDT)
Date: Tue, 19 Jun 2007 19:26:38 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Mark Andrews <Mark_Andrews@isc.org>
Message-ID: <20070620022638.GB26988@boreas.isi.edu>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
	<200706200121.l5K1LGeG007901@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200706200121.l5K1LGeG007901@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard? (was
	Re:	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> 	This prompted a jabber discussion extracts of which follow.
> 
> <XXXXX> note that people who operate routers are usually all about control. automatic renumbering is scary except maybe on the edge
> <marka> There is no loss of control.  It would still require a human to add a prefix to the set of prefixes in use.
> 
> <XXXXX> somebody upstream from you renumbers.  what happens?
> <marka> With IPv6 I would expect that a both the new and old routes would be published for a period.  The old route would then be withdrawn.  There is plenty of addresses  space.  There is no need for instantious changes in addresses.
> 
> <XXXXX> i was talking about control.  your upstream adds new prefix, do you add automatically or do you wait for human to approve it?
> <XXXXX> simiarly for your upstream withdrawing, do you withdraw automatically or ...
> <marka> I would expect that there would be due notice give so that humans could be involved.

	you expect too much.
> 
> 	Mark
> 
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 04:23:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0vT5-0002hx-2p; Wed, 20 Jun 2007 04:23:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0vT3-0002fy-5E
	for ipv6@ietf.org; Wed, 20 Jun 2007 04:23:09 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0vT1-0002Qa-Pw
	for ipv6@ietf.org; Wed, 20 Jun 2007 04:23:09 -0400
Received: from [192.168.2.100] (blobby.bind.org [82.92.138.66])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5K8N4Ub030201
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 20 Jun 2007 01:23:06 -0700
In-Reply-To: <46785A65.7060505@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Wed, 20 Jun 2007 10:23:01 +0200
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20 Jun 2007, at 12:36am, Scott Leibrand wrote:

[...]

>> Is this not already possible with a /48 PI assignment from ARIN?
> Yes, but only if you "qualify for an IPv4 assignment or allocation  
> from ARIN under the IPv4 policy currently in effect."  That  
> currently means you must either be a large network (qualifying for  
> a /20), or you must be large enough to run BGP, be multi-homed, and  
> be large enough to justify a /22.
>>
>> Is ULA-C a new solution for a problem that's already been solved  
>> with PI assignments or does it solve a new problem?
>>
> I believe there is a gap between the current PI policy, which is  
> targeted at organizations large enough to qualify for a routing  
> slot, and the need many smaller organizations have for their own IP  
> space for various internal uses. Some of those organizations will  
> be happy to use ULA-L, but some will need a guarantee of uniqueness  
> and the ability to list their IP space in DNS (.arpa) and in  
> whois.  If we can meet the needs of those organizations without  
> having to relax the requirements for PI space, we can reduce future  
> pressure on the DFZ.

So am I right in reading your answer as saying that the advantage of  
ULA-C is that it solves the same problem that ARIN's IPv6 PI policy  
solves but better. In effect, developing ULA-C helps side-step ARIN's  
policy development process?

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 05:36:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0wc0-0001ED-Dp; Wed, 20 Jun 2007 05:36:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wby-0001E7-JF
	for ipv6@ietf.org; Wed, 20 Jun 2007 05:36:26 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0wbx-0005uM-7i
	for ipv6@ietf.org; Wed, 20 Jun 2007 05:36:26 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 8C0E1140C21A;
	Wed, 20 Jun 2007 11:36:22 +0200 (CEST)
Message-ID: <4678F515.9010000@spaghetti.zurich.ibm.com>
Date: Wed, 20 Jun 2007 10:36:21 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
In-Reply-To: <467870DC.2030802@internap.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1654783317=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1654783317==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9F45FB5390FB84FEFBB2B3B2"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9F45FB5390FB84FEFBB2B3B2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Scott Leibrand wrote:
> Jeroen Massar wrote:
>=20
>> The above hosts are Internet connected and most likely will thus also
>> end up
>> talking to the Internet at one point or another. I can thus only guess=

>> that
>> they will be wanting to fully connect to the Internet one day and the
>> generic solution to that problem is NAT. We wanted to get rid of NAT f=
or
>> IPv6. If NAT is again being done for IPv6 then we can just as well
>> give up
>> and just keep on using IPv4 as there really is not a single advantage
>> then
>> anymore to IPv6.
>>
>>  =20
> I think what we wanted to get rid of in IPv6 was one-to-many NAT, also
> know as PAT (among other names).  In IPv6, we can stick to one-to-one
> NAT, which eliminates most of the nastiness we associate with NAT in
> today's IPv4 world.

No it does not eliminate anything, it still requires Layer 4+ rewriting o=
f
addresses, and that is the nasty bit.

Also NAT breaks this cool "new" (ahem) feature called IPSEC, which when
deployed, would also make deep packet inspection impossible. The latter
requiring one to look inside packets too, but not rewriting them.

[..]
>> The big thing there is though: configure your firewalls correctly as t=
he
>> public addresses do also allow access to everything.
>>  =20
> I don't think routers are at the point yet where you can easily renumbe=
r
> your routers' interfaces when your PA addresses change.  As a result,
> networks wanting to avoid the pain of renumbering, but who don't qualif=
y
> for PI and a global routing slot, might want to do something similar:

DHCP-PD, which can work in most small networks. I am not discussing anyth=
ing
that has more than say 20 boxes in such a network though but: small netwo=
rk.

> Say a network gets a ULA-C block, and numbers everything on their
> network out of that block.  They later connect to the Internet,

Your example is already failing. When they want to connect to the Interne=
t
somewhere, it is MUCH easier for them to just get a PI block, then they c=
an
always use that even with or without BGP. And maybe one day with a nice
id/loc solution when that comes out.

> and get
> a PA block from their upstream, and configure it on their border
> routers.  To avoid reconfiguring all their routers every time they
> change upstreams, they configure one-to-one NAT on their border routers=
,
> such that every address on their internal network (which is ULA-C) maps=

> to the same address, except with different first 48 bits, in their
> provider-allocated block.

This can perfectly be done with PI blocks in exactly the same way. The
advantage here is though that one day the PI block might be used globally=
,
while the ULA-C one can never be used in that way.

> This wouldn't present the same kinds of problems you'd get from
> one-to-many NAT, but I'm sure there are some ways where this wouldn't b=
e
> as good as PI space.  However, my first-order evaluation is that it
> would be better to have small networks achieve their provider
> independence this way, rather than by relaxing the PI rules and
> threatening the scalability of the current routing system with a large
> number of additional non-aggregatable netblocks.

The ARIN PI rules are already very relaxed: cough up $100 US yearly and
presto you have a fine /48 IPv6 PI.

> Now as expressed earlier, most ULA-C use cases probably won't involve
> NAT.  But if people do elect to use NAT with ULA-C, what problems do yo=
u
> see with this kind of use of NAT?  Do you see those problems as worse
> than the problems caused by completely rejecting the original PA-only
> architecture of IPv6 in favor of PI-for-everyone?

The big problem with NAT that I have as a programmer is that I will have =
to
make my protocol & program understand NATs and use them. I don't want to
care about them, there is End-To-End.

With a NAT what happens is that the NAT device will have to understand ev=
ery
protocol out there. Thus I come up with a new protocol which is really co=
ol,
and first I have to convince everybody on the planet to update their NAT
boxes to support that protocol.

That is not going to work, and as such people will write protocols which
have to evade those NAT boxes and are thus more complex and more error pr=
one
and less versatile.

>> Still, the above can also be accomplished perfectly fine with PI space=

>> and
>> that doesn't require any changes (except RIPE+APNIC policy) to be done=
=2E
>>
>>  =20
> I agree that PI space, if it were widely available, would meet the same=

> needs as ULA-C.  However, I think we need to be realistic that
> PI-for-everyone won't fly, and need to think creatively about ways to
> achieve the same goals (such as provider independence) in such a way
> that we don't impose more public cost than private benefit.

Why would ULA-C fly and PI not? They can be used in exactly the same way
with a huge advantage for the global unicast variant that it can at one
point also be used in BGP and other variants.

Having PI doesn't mean that one is going to announce that to the global
Internet, you can still use it on your local network without ever hooking=
 up
to that beast, but when you want to you can.

For all those ISP's who are 'afraid' of getting a zillion customers who w=
ant
to do PI: Well raise the prices.

Isn't that how it works? If you have something people want: make it more
expensive and make more money of it so that you can buy new gear and do
other such investments.

Why are people afraid of doing business? At a certain point getting a PI
block from a RIR might be cheap, but actually routing it will be expensiv=
e,
that solves the problem of too many routing slots doesn't it? But does th=
at
depend on the type of address space: no.


> Another thing to consider when evaluating whether to specify something
> like ULA-C is that we can't know what kind of innovation it will make
> possible in the future.

At least I can tell you what kind of innovation it will stop, see above: =
all
new protocols not supported by your ALG.

> Therefore, the question we should be asking is,
> is there any remaining reason *not* to allow networks to register ULA-C=

> space?

The question still is: is there any REAL application of ULA-C which can't=
 be
solved with a normal global unicast prefix?

> When it was last proposed there was: it was thought that
> networks would get ULA-C and use it as PI space.  Now, since PI space i=
s
> readily available to multihomed networks, that is much less likely.

The problem here is not that it is less likely, the problem is that
businesses will get ULA-C space and think that it is PI and still will wa=
nt
to use it as PI.

> As
> a result, I am in favor of allowing small networks to register their ow=
n
> unique private space, as this draft would do.

Let them get a nice PI block from a RIR if that is what they need.

> I can't predict how ULA-C will be used

If you can't come up with an actual use case for it yourself, then why
promote it? Especially in the light of the counter arguments given?

> but I'm confident that innovation is a good thing

Which innovation could lead from this? IPv6 NAT is *not* an innovation, i=
t
is repeating the same mistake as IPv4 had: no end to end.

> and that we can safely open up the ULA-C sandbox to networks who wish t=
o use
> it.

Add water to that sandbox and dilute, what you mean is "open up the swamp=
".
How safe is that?

People will expect it to work, and it won't work, thus that is not 'safe'=
=2E


I do have to note one minor thing about NAT: when done in two ways, thus
that the sender NATs to a global address and the receiver NATs back to th=
e
original address, no problem exists, but that is in effect a tunnel, and
that is in effect also what the various current id/loc proposals are look=
ing
at in one way or another.

Greets,
 Jeroen


--------------enig9F45FB5390FB84FEFBB2B3B2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ49RUuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+DXAJ9yXI42C+MmnSd68wdIDoCi9N2g
+gCgiN2vj5HKK4VEGOnT0PGcOm8gcIc=
=jShv
-----END PGP SIGNATURE-----

--------------enig9F45FB5390FB84FEFBB2B3B2--


--===============1654783317==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1654783317==--




From ipv6-bounces@ietf.org Wed Jun 20 05:56:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0wvP-0000yE-K2; Wed, 20 Jun 2007 05:56:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0wvO-0000xt-4s
	for ipv6@ietf.org; Wed, 20 Jun 2007 05:56:30 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0wvM-0000s6-R0
	for ipv6@ietf.org; Wed, 20 Jun 2007 05:56:30 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Jun 2007 11:56:28 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5K9uRK4017284; 
	Wed, 20 Jun 2007 11:56:27 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp258.cisco.com
	[10.61.65.2])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5K9uIDR029075; 
	Wed, 20 Jun 2007 09:56:23 GMT
Message-ID: <4678F9C0.3080600@cisco.com>
Date: Wed, 20 Jun 2007 11:56:16 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Mark Andrews <Mark_Andrews@isc.org>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
In-Reply-To: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2045; t=1182333387;
	x=1183197387; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20Re=3A=20Why=20does=20everyone=20see=20router=20renumbnering=2
	0as=20hard?=09(was=20Re=3A=20draft-ietf-ipv6-ula-central-02.txt=0A=20and=2
	0NAT) |Sender:=20;
	bh=1sADG8BcEEAe22Apq72yNPssXOfQBVYtG1Jio4VpXLM=;
	b=vsv0smHotqb9UwlKxiXmDFB7XD/Fp1XES52/J+Iv4ChDPu1hmMmS6bZLIHKOFeBV8lv0ofCX
	6xUu8eNliLhC4V0lDgOTaNxgKDAZ3QIbgq/rPXBzfMj2yZ4LEdn/8j0q;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard?	(was Re:
 draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Mark Andrews wrote:
> 	I would have thought that router renumbering should be no
> 	harder that host renumbering.  Essentially all you are
> 	changing is the higher (/48 normally) prefix bits.  All
> 	that is required is a method to distribute the set of
> 	prefixes in use with a set of tags (global, deprecated,
> 	ula, advertise in RA, etc.).
>   

I think there has been hype on both sides of this question.  Router 
renumbering used to be VERY annoying.  I've now published several times 
on the subject and I can say that it's not as hard as it was, but it's 
not as easy as it could be.  Specifically, prefix delegation should do 
the job for small routers, particularly in the consumer market.  Making 
use of PD in the enterprise is more experimental, I would say, because, 
as Bill alludes, there are quite a number of knobs to play with.  
Consider that a typical enterprise router not only has interface 
addresses and routing subsystems and firewalls, but may also have such 
fun as VRRP/HSRP configurations, load balancing capabilities, 
NetFlow/sflow collectors, multicast configuration that has some unicast 
addresses hidden in it, management configuration (e.g., SNMP, SYSLOG, 
other), and the like.

In my opinion, this means that the router of the future needs to look a 
little different, and this has implications for other subsystems.  Much 
of this could conceivably be hidden with DNS, but the router itself 
needs to function not just deterministically but predictably down to the 
minute in terms of which addresses it is using.  DNS isn't very good at 
that because your TTLs are based on when you query, and are tied to 
relatively fixed configurations, but it can be used for many things even 
so.  And today you can do that in many portions of the configuration - 
but not all.

It is possible to abstract out much of the configuration EVEN WITHOUT 
DNS, and modularize those things that will change.  And we've done 
*some* of that at Cisco, but we all could do more.

Eliot

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 06:12:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0xAP-0004Jg-4M; Wed, 20 Jun 2007 06:12:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0xAM-0004EA-SY
	for ipv6@ietf.org; Wed, 20 Jun 2007 06:11:58 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0xAJ-00046T-Q8
	for ipv6@ietf.org; Wed, 20 Jun 2007 06:11:58 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 83DCB140C145;
	Wed, 20 Jun 2007 12:11:53 +0200 (CEST)
Message-ID: <4678FD67.8010200@spaghetti.zurich.ibm.com>
Date: Wed, 20 Jun 2007 11:11:51 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
	<4678F9C0.3080600@cisco.com>
In-Reply-To: <4678F9C0.3080600@cisco.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: Mark Andrews <Mark_Andrews@isc.org>, ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard?	(was Re:
 draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1111706191=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1111706191==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigBA260867E67FA6CF269EEF42"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigBA260867E67FA6CF269EEF42
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Eliot Lear wrote:
> Mark Andrews wrote:
>>     I would have thought that router renumbering should be no
>>     harder that host renumbering.  Essentially all you are
>>     changing is the higher (/48 normally) prefix bits.  All
>>     that is required is a method to distribute the set of
>>     prefixes in use with a set of tags (global, deprecated,
>>     ula, advertise in RA, etc.).
>>  =20
>=20
> I think there has been hype on both sides of this question.  Router
> renumbering used to be VERY annoying.  I've now published several times=

> on the subject

Any links to the papers?

> and I can say that it's not as hard as it was, but it's
> not as easy as it could be.  Specifically, prefix delegation should do
> the job for small routers, particularly in the consumer market.  Making=

> use of PD in the enterprise is more experimental, I would say, because,=

> as Bill alludes, there are quite a number of knobs to play with.=20
> Consider that a typical enterprise router not only has interface
> addresses and routing subsystems and firewalls, but may also have such
> fun as VRRP/HSRP configurations, load balancing capabilities,
> NetFlow/sflow collectors, multicast configuration that has some unicast=

> addresses hidden in it, management configuration (e.g., SNMP, SYSLOG,
> other), and the like.

Indeed, but except for firewalling, it is why I mentioned using a "local"=

space (PI) or some other 'globally unique chunk that they can keep'.
One will then configure all the internal setups (snmp,syslog,sflow/netflo=
w
etc) using the forever addresses and won't have to care about those anymo=
re.
Routing internally can also happen using those addresses, though the scar=
y
bit is of course when the MTU does change or a Host/Net unreach has to be=

sent, the router has to pick the correct global address and not the one
which is only used inside the network. A block like fc00::/7 could make i=
t
easy to then choose the address based on the target, but how sure are you=

that the other organization is not using global unicast space for their
internal networks? Even if that dual setup might not be accepted everywhe=
re,
I mean if you have PI why should one want to add the mess of two networks=
?


> In my opinion, this means that the router of the future needs to look a=

> little different, and this has implications for other subsystems.
[..goodbits..]

Which is indeed why I am thinking that ID/LOC is the way to go. One inter=
nal
prefix on the local network, and whatever prefix is on the global Interne=
t.
Apply ID/LOC when your packets are going somewhere where you can't use yo=
ur
local prefix.

Greets,
 Jeroen


--------------enigBA260867E67FA6CF269EEF42
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ4/WcuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I8YPAJ9XhTsdSjahQIPxDWGiFRuGP/pE
2ACfbFofJ3XHzQOpt++xcTZ+5ZxT154=
=aVpP
-----END PGP SIGNATURE-----

--------------enigBA260867E67FA6CF269EEF42--


--===============1111706191==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1111706191==--




From ipv6-bounces@ietf.org Wed Jun 20 06:27:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0xPJ-0001Dk-Ei; Wed, 20 Jun 2007 06:27:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0xPI-0001Da-B2
	for ipv6@ietf.org; Wed, 20 Jun 2007 06:27:24 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0xPE-0007ir-VG
	for ipv6@ietf.org; Wed, 20 Jun 2007 06:27:24 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Jun 2007 12:27:21 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5KARKow018212; 
	Wed, 20 Jun 2007 12:27:20 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp258.cisco.com
	[10.61.65.2])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5KARJDR009951; 
	Wed, 20 Jun 2007 10:27:19 GMT
Message-ID: <46790105.1040803@cisco.com>
Date: Wed, 20 Jun 2007 12:27:17 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>	<4678F9C0.3080600@cisco.com>
	<4678FD67.8010200@spaghetti.zurich.ibm.com>
In-Reply-To: <4678FD67.8010200@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3059; t=1182335240;
	x=1183199240; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20Re=3A=20Why=20does=20everyone=20see=20router=20renumbnering=2
	0as=20hard?=09(was=20Re=3A=20draft-ietf-ipv6-ula-central-02.txt=0A=20and=2
	0NAT) |Sender:=20;
	bh=1zNRckpJKemBN9p4LCqVr0QBkZ+/kOH6S0SXOxyfiC4=;
	b=sQokRGWkQ69stfdATXMChWR30u7DkibuQbydc6uEqMWqIKVIF6lh4dhiTE694+dq1FtpaKG+
	Hew7uNW4Kk6f2aJJT2CSYLz+JIxYvmWgkbhBB/g7W7DOlPhUM85afAfZ;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: Mark Andrews <Mark_Andrews@isc.org>, ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard?	(was Re:
 draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar wrote:
> Eliot Lear wrote:
>   
>> Mark Andrews wrote:
>>     
>>>     I would have thought that router renumbering should be no
>>>     harder that host renumbering.  Essentially all you are
>>>     changing is the higher (/48 normally) prefix bits.  All
>>>     that is required is a method to distribute the set of
>>>     prefixes in use with a set of tags (global, deprecated,
>>>     ula, advertise in RA, etc.).
>>>   
>>>       
>> I think there has been hype on both sides of this question.  Router
>> renumbering used to be VERY annoying.  I've now published several times
>> on the subject
>>     
>
> Any links to the papers?
>   

There are two that I can point you at, and perhaps the temporal 
difference would be at least amusing:

    * Renumbering: Threat or Menace?, Lear, Katinsky, Tharp, et al,
      Proceedings of the Tenth Systems Administration Conference (LISA96)
    * Procedures for Renumbering an IPv6 Network Without a Flag Day,
      Baker, Lear, Droms, RFC 4192, September, 2005.

I would also add that Tim Chown has done an extensive amount of work in 
this space.

> Indeed, but except for firewalling, it is why I mentioned using a "local"
> space (PI) or some other 'globally unique chunk that they can keep'.
>   

Certainly we've heard this argument from large enterprise customers.

> One will then configure all the internal setups (snmp,syslog,sflow/netflow
> etc) using the forever addresses and won't have to care about those anymore.
>   

Sure.

> Routing internally can also happen using those addresses, though the scary
> bit is of course when the MTU does change or a Host/Net unreach has to be
> sent, the router has to pick the correct global address and not the one
> which is only used inside the network.

This really depends on just how scary an enterprise routing 
configuration is.  They can be quite complex depending on both their 
internal and external connectivity, and each has some implications for 
the other.  There are quite a number of enterprises that make heavy use 
of BGP internally.  But certainly the point of ULAs was to provide some 
stability in this area.  I think LISP (draft-farinacci-lisp-00.txt) has 
promise here as well, as may Robin's iVIP proposal (see the ram archives 
for details).

>> In my opinion, this means that the router of the future needs to look a
>> little different, and this has implications for other subsystems.
>>     
> [..goodbits..]
>
> Which is indeed why I am thinking that ID/LOC is the way to go. One internal
> prefix on the local network, and whatever prefix is on the global Internet.
> Apply ID/LOC when your packets are going somewhere where you can't use your
> local prefix.
>   

If your point is that you should never have to renumber, then that's a 
lovely way to go.  It will still happen, of course, as companies merge 
and grow.  I think IPv6 helps with the latter, but the former is still a 
challenge simply because topologies change.


Eliot

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 07:46:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0ydp-00060z-Mb; Wed, 20 Jun 2007 07:46:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0ydo-00060u-CE
	for ipv6@ietf.org; Wed, 20 Jun 2007 07:46:28 -0400
Received: from [2002:db58:fb10::1] (helo=carbon.meta.net.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0ydm-0001Wl-Da
	for ipv6@ietf.org; Wed, 20 Jun 2007 07:46:28 -0400
Received: from [60.234.141.149] (helo=[10.100.4.160] ident=dahoose2)
	by carbon.meta.net.nz with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62)
	(envelope-from <perry@coders.net>)
	id 1I0ydj-0000lf-KK; Wed, 20 Jun 2007 23:46:23 +1200
Message-ID: <4679138C.1030008@coders.net>
Date: Wed, 20 Jun 2007 23:46:20 +1200
From: Perry Lorier <perry@coders.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
In-Reply-To: <467853B0.5010806@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


>
>
> However, I do have some routers with interfaces that need numbering, 
> and I'd rather avoid renumbering them when I change upstreams.  Since 
> ULA-C is cheap and easy to get, I register myself a block of it, and 
> use it to number my router interfaces.  Since I'd rather my customers 
> saw DNS names instead of IPv6 addresses in their traceroutes, I 
> delegate the reverse DNS for my ULA-C block to a nameserver on my 
> upstream's PA space, and set up proper PTR records for all my routers.
>
> Now, whenever anyone does a traceroute into or out of my network, 
> they'll see ULA-C addresses in the traceroute.  They don't need to 
> actually reach those addresses if they're not in my network, but they 
> will at least be able to resolve PTR records for them, so that the 
> traceroute cleanly shows whose network they're traversing.
>
Except that uRPF will prevent those traceroute packets from being 
returned to people.  This also breaks pMTU discovery and all the various 
other things that rely on routers returning ICMP messages.

> And whenever I decide to switch upstreams, all I have to do is update 
> my DHCP servers, 
Your DHCP servers would presumably be using prefix delegation to request 
a prefix to allocate and thus wouldn't require any configuration?
> update my nameserver's A record to an IP out of my new upstream's PA 
> space, and we're done.  I don't have to renumber a single router, I 
> don't have to run BGP, and I don't have to litter the DFZ with another 
> PI block.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 08:33:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0zNV-00014l-W6; Wed, 20 Jun 2007 08:33:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0zNT-00014d-Iq
	for ipv6@ietf.org; Wed, 20 Jun 2007 08:33:39 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0zNS-0002QL-6x
	for ipv6@ietf.org; Wed, 20 Jun 2007 08:33:39 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 13:33:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Jun 2007 13:32:23 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08B038D@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <4678F9C0.3080600@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why does everyone see router renumbnering as hard?	(was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
Thread-Index: AcezIWtL1603iivOSCCuASld5BUrOwAFLtPA
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
	<4678F9C0.3080600@cisco.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 12:33:37.0665 (UTC)
	FILETIME=[39BD9F10:01C7B337]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: RE: Why does everyone see router renumbnering as hard?	(was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> In my opinion, this means that the router of the future needs=20
> to look a little different, and this has implications for=20
> other subsystems.  Much of this could conceivably be hidden=20
> with DNS,=20

Since when do IP networks require DNS to function. We run a global IPv4
network with over 10,000 customer sites in over 20 countries, and there
is virtually no DNS on this network at all. After all, it's an IP
network, i.e. its job is forwarding IP packets.

As to why DNS is not used, it has something to do with unneccesarily
trusting third parties to figure out your packet destinations and the
added complexity of DNS. It turns out to be simpler and more flexible to
just use IP addresses directly. If you need to fail-over communications
to a disaster-recovery site, or merely to a backup server, you can
configure two or four IP addresses in the application and let the app
sort out where to send packets.=20

DNS should not be overloaded with so many new functions that it becomes
a requirement of running an IP network.

--Michael Dillon


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 10:12:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I10uS-0004Z3-HT; Wed, 20 Jun 2007 10:11:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I10uR-0004Y6-Gl
	for ipv6@ietf.org; Wed, 20 Jun 2007 10:11:47 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I10uQ-0004qi-7M
	for ipv6@ietf.org; Wed, 20 Jun 2007 10:11:47 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Jun 2007 16:11:46 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5KEBjGC003883; 
	Wed, 20 Jun 2007 16:11:45 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp258.cisco.com
	[10.61.65.2])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5KEBjDR023042; 
	Wed, 20 Jun 2007 14:11:45 GMT
Message-ID: <4679359F.5070500@cisco.com>
Date: Wed, 20 Jun 2007 16:11:43 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: michael.dillon@bt.com
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>	<4678F9C0.3080600@cisco.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B08B038D@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B08B038D@E03MVC4-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1123; t=1182348705;
	x=1183212705; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com;
	z=From:=20Eliot=20Lear=20<lear@cisco.com>
	|Subject:=20Re=3A=20Why=20does=20everyone=20see=20router=20renumbnering=2
	0as=20hard?=09(was=20Re=3A=09draft-ietf-ipv6-ula-central-02.txt=0A=20and=2
	0NAT) |Sender:=20;
	bh=YiTVZZzdyxfwXZjD9tXkjB65Ao6XgGcqQ1heZv3AwOA=;
	b=BBIjPCcxBccLnArD1qpdTZbeM2mvMtnT80CQ1HmKbveIzHsrS2MOTk1a66w/Kp/sK9F89xSN
	XQPi6M5JyzxhURgdtgW079xtscyL3SH35O0lFqMnZSb3CqYTwyJQZdKi;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard?	(was
 Re:	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Michael,

I totally understand the concern over circular dependencies.  They are 
not to be underestimated.  And in a service provider environment I think 
you must be doubly cautious about them.  However, in an enterprise 
environment it may be appropriate to make certain allowances for certain 
services, and under certain circumstances.  For instance, a load 
balancer may require DNS to be functioning already in order for it to 
service requests.  Similarly, it may be possible to "secondary" a zone 
in order to be able to bring up certain other services, such as NTP.  It 
is *even* possible to retain policy in DNS if one really wants to do so 
under such circumstances, but one has to at that point consider what 
your failsafe is.

Ultimately, however, the administrative issues of renumbering revolve 
around an inability to abstract IP address information.  In solving that 
problem, however one performs the dereference from abstract to concrete, 
one must worry about dependency loops.  A configuration server could 
just as easily be unavailable, for instance, as a name server.

Eliot

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 13:23:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I13t4-0000r5-Lh; Wed, 20 Jun 2007 13:22:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I13t3-0000r0-4D
	for ipv6@ietf.org; Wed, 20 Jun 2007 13:22:33 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I13t1-0001BJ-O4
	for ipv6@ietf.org; Wed, 20 Jun 2007 13:22:33 -0400
Received: from [70.41.247.63] (account sleibrand@mail.internap.com HELO
	[192.168.29.100])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84699089; Wed, 20 Jun 2007 13:22:30 -0400
Message-ID: <46796246.4050705@internap.com>
Date: Wed, 20 Jun 2007 10:22:14 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
In-Reply-To: <F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Leo Vegoda wrote:
> On 20 Jun 2007, at 12:36am, Scott Leibrand wrote:
>
> [...]
>
>>> Is this not already possible with a /48 PI assignment from ARIN?
>> Yes, but only if you "qualify for an IPv4 assignment or allocation 
>> from ARIN under the IPv4 policy currently in effect."  That currently 
>> means you must either be a large network (qualifying for a /20), or 
>> you must be large enough to run BGP, be multi-homed, and be large 
>> enough to justify a /22.
>>>
>>> Is ULA-C a new solution for a problem that's already been solved 
>>> with PI assignments or does it solve a new problem?
>>>
>> I believe there is a gap between the current PI policy, which is 
>> targeted at organizations large enough to qualify for a routing slot, 
>> and the need many smaller organizations have for their own IP space 
>> for various internal uses. Some of those organizations will be happy 
>> to use ULA-L, but some will need a guarantee of uniqueness and the 
>> ability to list their IP space in DNS (.arpa) and in whois.  If we 
>> can meet the needs of those organizations without having to relax the 
>> requirements for PI space, we can reduce future pressure on the DFZ.
>
> So am I right in reading your answer as saying that the advantage of 
> ULA-C is that it solves the same problem that ARIN's IPv6 PI policy 
> solves but better. In effect, developing ULA-C helps side-step ARIN's 
> policy development process?
>
No, it solves a similar problem for a different (though possibly 
partially overlapping) set of networks, and reduces the pressure to 
apply a hammer when a screwdriver is what's really needed.

I would anticipate that for ULA-C to be implemented, RIR policy would 
need to be updated to codify how the RIRs would administer ULA-C.  As an 
active member of ARIN's policy process, I see ULA-C as something that 
should be administered by the RIRs, not by a separate registry, so that 
the RIRs can direct applicants to the appropriate resources (PI for 
large or multihomed networks, ULA-C for private, non-routed space for 
those who don't qualify for PI, etc.)

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 14:00:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I14Tn-0005fc-Ne; Wed, 20 Jun 2007 14:00:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I14Tm-0005fX-CL
	for ipv6@ietf.org; Wed, 20 Jun 2007 14:00:30 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I14Tj-0002OV-Sy
	for ipv6@ietf.org; Wed, 20 Jun 2007 14:00:30 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I14Te-0003Np-8J; Thu, 21 Jun 2007 03:30:22 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 1003320139;
	Thu, 21 Jun 2007 03:30:18 +0930 (CST)
Date: Thu, 21 Jun 2007 03:30:18 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Scott Leibrand <sleibrand@internap.com>
Message-Id: <20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <467870DC.2030802@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 19 Jun 2007 17:12:12 -0700
Scott Leibrand <sleibrand@internap.com> wrote:

> Jeroen Massar wrote:
> 
> > The above hosts are Internet connected and most likely will thus also 
> > end up
> > talking to the Internet at one point or another. I can thus only guess that
> > they will be wanting to fully connect to the Internet one day and the
> > generic solution to that problem is NAT. We wanted to get rid of NAT for
> > IPv6. If NAT is again being done for IPv6 then we can just as well give up
> > and just keep on using IPv4 as there really is not a single advantage then
> > anymore to IPv6.
> >
> >   
> I think what we wanted to get rid of in IPv6 was one-to-many NAT, also 
> know as PAT (among other names).  In IPv6, we can stick to one-to-one 
> NAT, which eliminates most of the nastiness we associate with NAT in 
> today's IPv4 world.
> 

Getting rid of PAT doesn't eliminate a number of other problems that
NAT creates, which Keith Moore has documented here :

http://www.cs.utk.edu/~moore/what-nats-break.html

I particularly think inhibiting deploying new transport layer protocols
is a real drawback of NAT. It seems that VoIP might be the next "killer
app" for the Internet, and DCCP would be ideal for it. Unfortunately, I
think the IPv4 NATs out there are going to prevent it getting any
deployment traction over IPv4.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 14:16:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I14jP-0007Jf-Q8; Wed, 20 Jun 2007 14:16:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I14jO-0007JS-Cn
	for ipv6@ietf.org; Wed, 20 Jun 2007 14:16:38 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I14jM-0005X2-W4
	for ipv6@ietf.org; Wed, 20 Jun 2007 14:16:38 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id 9C73C987A2B
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 11:16:36 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 8E1BD10054
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 11:16:36 -0700 (PDT)
X-AuditID: 11807124-9e738bb000000803-7e-46796f0441fd
Received: from [17.219.208.84] (unknown [17.219.208.84])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 5E310100BA
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 11:16:36 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
Message-Id: <A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
Content-Transfer-Encoding: quoted-printable
From: james woodyatt <jhw@apple.com>
Date: Wed, 20 Jun 2007 11:16:15 -0700
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20 Jun 2007, at 11:00, Mark Smith wrote:
>
> Getting rid of PAT doesn't eliminate a number of other problems that
> NAT creates, which Keith Moore has documented here :
>
> http://www.cs.utk.edu/~moore/what-nats-break.html

I'd be more sympathetic to arguments like this if we RFC 4864 didn't =20
insist on recommending  the deployment of stateful packet filters in =20
IPv6 that break most of the things NAT breaks in IPv4.

> I particularly think inhibiting deploying new transport layer =20
> protocols is a real drawback of NAT. [...]

That's one of the things broken by the stateful packet filters =20
implied by RFC 4864.  It seems to me that NAT for IPv6 isn't really =20
all that worse than what we've already recommended there.  Sure, =20
everything is still globally addressable, but that really doesn't go =20
very far when symmetrical reachability is pretty much broken for =20
everything at the edges of the Internet.

If people think they can make arguments for why NAT between ULA-C =20
addresses and PA address will solve more problems than it really =20
causes=97 given what other problems we've already bought with the RFC =20=

4864 packet filters=97 then I think we should hear them.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 16:34:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I16sE-0004Me-QE; Wed, 20 Jun 2007 16:33:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I16sD-0004MZ-Cw
	for ipv6@ietf.org; Wed, 20 Jun 2007 16:33:53 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I16sB-00017C-QA
	for ipv6@ietf.org; Wed, 20 Jun 2007 16:33:53 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5KKXjTl050721;
	Thu, 21 Jun 2007 06:33:45 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706202033.l5KKXjTl050721@drugs.dv.isc.org>
To: james woodyatt <jhw@apple.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Wed, 20 Jun 2007 11:16:15 MST."
	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com> 
Date: Thu, 21 Jun 2007 06:33:45 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> On 20 Jun 2007, at 11:00, Mark Smith wrote:
> >
> > Getting rid of PAT doesn't eliminate a number of other problems that
> > NAT creates, which Keith Moore has documented here :
> >
> > http://www.cs.utk.edu/~moore/what-nats-break.html
> 
> I'd be more sympathetic to arguments like this if we RFC 4864 didn't =20
> insist on recommending  the deployment of stateful packet filters in =20
> IPv6 that break most of the things NAT breaks in IPv4.
> 
> > I particularly think inhibiting deploying new transport layer =20
> > protocols is a real drawback of NAT. [...]
> 
> That's one of the things broken by the stateful packet filters =20
> implied by RFC 4864.  It seems to me that NAT for IPv6 isn't really =20
> all that worse than what we've already recommended there.  Sure, =20
> everything is still globally addressable, but that really doesn't go =20
> very far when symmetrical reachability is pretty much broken for =20
> everything at the edges of the Internet.
> 
> If people think they can make arguments for why NAT between ULA-C =20
> addresses and PA address will solve more problems than it really =20
> causes=97 given what other problems we've already bought with the RFC =20=
> 
> 4864 packet filters=97 then I think we should hear them.

	It's much easier to have a application talk to a firewall if
	it doesn't also have to deal with address/port translations
	that it is not aware of.

> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 18:10:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I18NX-00038w-VB; Wed, 20 Jun 2007 18:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I18NW-00033U-R4
	for ipv6@ietf.org; Wed, 20 Jun 2007 18:10:18 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I18NU-00087m-0P
	for ipv6@ietf.org; Wed, 20 Jun 2007 18:10:18 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I18NO-0005fP-3a; Thu, 21 Jun 2007 07:40:10 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 5F1FA20139;
	Thu, 21 Jun 2007 07:40:08 +0930 (CST)
Date: Thu, 21 Jun 2007 07:40:07 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: james woodyatt <jhw@apple.com>
Message-Id: <20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 20 Jun 2007 11:16:15 -0700
james woodyatt <jhw@apple.com> wrote:

> On 20 Jun 2007, at 11:00, Mark Smith wrote:
> >
> > Getting rid of PAT doesn't eliminate a number of other problems that
> > NAT creates, which Keith Moore has documented here :
> >
> > http://www.cs.utk.edu/~moore/what-nats-break.html
>=20
> I'd be more sympathetic to arguments like this if we RFC 4864 didn't =20
> insist on recommending  the deployment of stateful packet filters in =20
> IPv6 that break most of the things NAT breaks in IPv4.
>=20

How does a statefule firewall, present on the end-node itself, cause
these problems ? It seems to me that you're making the assumption that
the only scenario IPv6 will be deployed in is one where end-nodes
always have an upstream stateful firewalling device.=20

That assumption already isn't true now in IPv4 (one example being this
PC) and I think is even more unlikely to be with IPv6. I think any
vendor who produces Internet capable devices (PCs, OSes, mobile phones,
musical keyboards (Internet capable ones do already exist)) that don't
assume they could be attached directly to the wide open Internet are
unlikely to have much success with their product.

(I'm aware of the IPv6 CPE design work that's going on, and
have been meaning to point out whether that work should be completely
based on the assumption of an upstream firewalling device (have been a
bit time short recently). It's certainly a feasible scenario. However I
think we'd probably be being a bit short sighted if we assumed that
that is the only IPv6 deployment scenario, and I think that eventually
it's probably going to be more likely an exception rather than a rule -
if all the devices are looking after themselves independantly, adding
another protection device upstream in the network doesn't add all that
much additional security value, compared to the costs, financial and
technical, it incurs.)

> > I particularly think inhibiting deploying new transport layer =20
> > protocols is a real drawback of NAT. [...]
>=20
> That's one of the things broken by the stateful packet filters =20
> implied by RFC 4864.  It seems to me that NAT for IPv6 isn't really =20
> all that worse than what we've already recommended there.  Sure, =20
> everything is still globally addressable, but that really doesn't go =20
> very far when symmetrical reachability is pretty much broken for =20
> everything at the edges of the Internet.
>=20
> If people think they can make arguments for why NAT between ULA-C =20
> addresses and PA address will solve more problems than it really =20
> causes=E2=80=94 given what other problems we've already bought with the=
 RFC =20
> 4864 packet filters=E2=80=94 then I think we should hear them.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 19:11:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I19KL-00052f-NF; Wed, 20 Jun 2007 19:11:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I19KJ-00052X-O2
	for ipv6@ietf.org; Wed, 20 Jun 2007 19:11:03 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I19KJ-0002Ge-87
	for ipv6@ietf.org; Wed, 20 Jun 2007 19:11:03 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id DCC7F99222F
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 16:11:02 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id CA5D840611
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 16:11:02 -0700 (PDT)
X-AuditID: 11807126-a0522bb000006df5-99-4679b406b1bc
Received: from [17.219.208.84] (unknown [17.219.208.84])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 9178040086
	for <ipv6@ietf.org>; Wed, 20 Jun 2007 16:11:02 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
	<20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Wed, 20 Jun 2007 16:11:01 -0700
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20 Jun 2007, at 15:10, Mark Smith wrote:
> On Wed, 20 Jun 2007 11:16:15 -0700 james woodyatt <jhw@apple.com>  
> wrote:
>>
>> I'd be more sympathetic to arguments like this if we RFC 4864 didn't
>> insist on recommending  the deployment of stateful packet filters in
>> IPv6 that break most of the things NAT breaks in IPv4.
>
> How does a stateful firewall, present on the end-node itself, cause  
> these problems?

We see this all the time today with stateful packet filters in IPv4  
nodes at global unicast addresses.  Application binds to a socket for  
accepting connections, but that isn't enough for accepting incoming  
connections.  Application need to obtain authorization to request the  
firewall to allow incoming connections.  That involves asking a user  
for a password.  Bletch.

Moreover, firewall knows how to track state for TCP and UDP, because  
that's all the transports the IP stack knows about.  It would be  
reasonable to port implementations of SCTP and DCCP to live there as  
well, but nobody bothers because the firewall doesn't know about  
those transports and needs to be taught about them from scratch.   
Consequently, applications that should use DCCP or SCTP, use TCP or  
UDP instead, so they can work with the firewall interface they have.

Firewalls don't get upgraded to support SCTP and DCCP because  
applications are all limping along with TCP and UDP.  Egg: meet chicken.

> It seems to me that you're making the assumption that the only  
> scenario IPv6 will be deployed in is one where end-nodes always  
> have an upstream stateful firewalling device.

This is likely to be *more* common in the future than it already is  
today.  Residential IPv6 gateway devices are shipping now in consumer- 
grade Wi-Fi AP/router products, and they include these packet filters  
turned on by default.  More are forthcoming.  Their owners are rarely  
even made aware of these packet filters.  Most won't discover them  
until they try to do something silly and stupid, like receive  
incoming VoIP calls over IPv6, fail utterly, and then *maybe* track  
down the source of the ICMP "administratively prohibited" errors to  
their own router.

Architecture is hard, folks.  Despite our best laid architectural  
planz, we are certain to be plagued with middleboxes at every level  
of the Internet.  They're going to interfere with everything.   
Basically, if it's known to work today over IPv4/NAT, then there's a  
pretty good chance it will still work tomorrow over IPv6.  That's  
about the best we can hope for at this point.

If NAT between PA and ULA-C unicast addresses solves a problem for  
somebody, without breaking anything important that isn't already  
broken by something else we've already done, then why shouldn't we be  
pragmatic and define a mostly sensible way for them to do it?

p.s. Readers are encouraged to consider whether this message is a  
devil's advocacy.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 20 22:04:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1C1N-0001t7-8H; Wed, 20 Jun 2007 22:03:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1C1L-0001sn-Iq
	for ipv6@ietf.org; Wed, 20 Jun 2007 22:03:39 -0400
Received: from warlock.cs.waikato.ac.nz ([130.217.250.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1C1J-0007ld-Uo
	for ipv6@ietf.org; Wed, 20 Jun 2007 22:03:39 -0400
Received: from [130.217.250.13] (helo=[130.217.250.13] ident=perry)
	by warlock.cs.waikato.ac.nz with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50)
	id 1I1C18-0005Pk-4H; Thu, 21 Jun 2007 14:03:32 +1200
Message-ID: <4679DC6C.8040509@coders.net>
Date: Thu, 21 Jun 2007 14:03:24 +1200
From: Perry Lorier <perry@coders.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US;
	rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>	<4678396E.4000204@spaghetti.zurich.ibm.com>	<467870DC.2030802@internap.com>	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>	<20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
In-Reply-To: <E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Scanned-By: warlock.cs.waikato.ac.nz
	(f7284d6d11afbe5513d63a9dd3bfe6f0d34be547)
X-Spam-Score: -3.9 (---)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

james woodyatt wrote:
> On 20 Jun 2007, at 15:10, Mark Smith wrote:
>> On Wed, 20 Jun 2007 11:16:15 -0700 james woodyatt <jhw@apple.com> wrote:
>>>
>>> I'd be more sympathetic to arguments like this if we RFC 4864 didn't
>>> insist on recommending  the deployment of stateful packet filters in
>>> IPv6 that break most of the things NAT breaks in IPv4.
>>
>> How does a stateful firewall, present on the end-node itself, cause 
>> these problems?
> 
> We see this all the time today with stateful packet filters in IPv4 
> nodes at global unicast addresses.  Application binds to a socket for 
> accepting connections, but that isn't enough for accepting incoming 
> connections.  Application need to obtain authorization to request the 
> firewall to allow incoming connections.  That involves asking a user for 
> a password.  Bletch.

And then there is no real standard for asking for that authorization in 
the first place.  A lot of applications embed UPnP, which I guess is as 
close to a standard for being able to request a listening port as we 
have.  Many protocols have ways of testing to see if a listening port 
really is listening, since there is no real local feedback from 
firewalls that your listening port is being filtered or NAT'd or had any 
number of other things done to it.

And then we get software developers abusing what is really a bug in 
stateful boxes in the name of "nat transversal".  Operators and end 
users regularly say "Your new application should support nat 
transversal" rather than fixing the underlying problems.

> Moreover, firewall knows how to track state for TCP and UDP, because 
> that's all the transports the IP stack knows about.  It would be 
> reasonable to port implementations of SCTP and DCCP to live there as 
> well, but nobody bothers because the firewall doesn't know about those 
> transports and needs to be taught about them from scratch.  
> Consequently, applications that should use DCCP or SCTP, use TCP or UDP 
> instead, so they can work with the firewall interface they have.
> 
> Firewalls don't get upgraded to support SCTP and DCCP because 
> applications are all limping along with TCP and UDP.  Egg: meet chicken.

And these boxes don't support this "new fangled" IPv6 thing either. 
Operators claim theres no point in pushing IPv6 out to customers coz 
their CPE's don't support it.


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 04:27:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Hzr-0003VJ-3e; Thu, 21 Jun 2007 04:26:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Hzp-0003V9-OR
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:26:29 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Hzo-0001dD-CF
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:26:29 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1378877ugf
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 01:26:27 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=h3GJqfHyyAXFPZNU+xONp43OG7RtnryvlGKT7yTjvlMRK0tuT6xMRaU70S81IflRJU9xUcypjgiRfHxImMTYnJBhyR478c2iWz5Q4JTt/uIR7AHZDl+USRGgXMroSwhcaiHAfeKAxxeF9zxTETfWqi1lr/+THeSdLhiFQKtq7BQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ZASEvp9Itxkw2Mfj6xuGJaw6DzS2wJj6ewU56ehsK39ETEzF2ay3GtPbsIx9+CKjjjSSy/yWlfAy91S2m51RmCyNXh4qU8n4LcD/OVCm4rLW0GAXE8djbKxWUutsVPg9hBAkXq4f6tWMMxBuuQljwM6mTAAv2ifd+haUXeJYEy4=
Received: by 10.67.28.9 with SMTP id f9mr1866617ugj.1182414387416;
	Thu, 21 Jun 2007 01:26:27 -0700 (PDT)
Received: from ?192.168.1.101? ( [85.232.174.201])
	by mx.google.com with ESMTP id q56sm1853289ugq.2007.06.21.01.26.26
	(version=SSLv3 cipher=RC4-MD5); Thu, 21 Jun 2007 01:26:26 -0700 (PDT)
Message-ID: <467A3630.3060404@gmail.com>
Date: Thu, 21 Jun 2007 10:26:24 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Azinger, Marla" <marla.azinger@frontiercorp.com>
References: <454810F09B5AA04E9D78D13A5C39028A0272F932@nyrofcs2ke2k01.corp.pvt>
In-Reply-To: <454810F09B5AA04E9D78D13A5C39028A0272F932@nyrofcs2ke2k01.corp.pvt>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02 and RIR documentation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-19 00:29, Azinger, Marla wrote:
> Michael-  I dont believe that was the intent and there might be a little misinterpretation here due to how it was written.  The document says:
> 
>> The designated allocation authority is required to document how they
>    will meet the requirements described in Section 3.2 of this document
>    in an RFC.<
> 
> This states the RIR's need to document how they will meet the requirements once section 3.2.  It dont believe the author intends for RIR's to write an RFC.  I believe the intent of the sentence you question is actually saying in a round about way that RIR's need to use their policy process and write policy's that will meet the requirements stated in section 3.2 of the draft.  Thus, synchronizing the RFC and RIR policy.
> 
> Or at least that is what I had discussed on a conference call with R. Hinden and T. Narten before the revision was made.  So Bob or Thomas, correct me if I am wrong here...

Marla, if your interpretation is correct (and I hope it is)
the words "in an RFC" need to be deleted from the draft.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 04:37:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1I9y-0004R1-SU; Thu, 21 Jun 2007 04:36:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1I9x-0004Qt-9B
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:36:57 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1I9v-0003ZL-Jb
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:36:57 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1381112ugf
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 01:36:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=rNhPg13O0y/Wt6c+gmQxRYJIbsRblWpWgDyYahMW0EAhGZvE2+bouor43nQSiClQym2kMTIMb3hEte6JGsrYs9zCSQQ2iVz3LJhN7+jMT52cHHs6U3KIPn9jSLdMheoGpyUadsALhKFUcZTSjHFoMxH+6rmCoTkApFlC0Bhysjg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=p1M2C81Jl4v8Ndb22pzn1tqpRxGb+FnpT/CPqBOeVHGxp/Aj9jQr0A36o6KA6iVmhCoreuZqsC+KWS7b+8txKd65nFJ9rkvbDx711gPdKldY3BemH+8LAnZuCKlVuzZBjQBil48KMUQu9SOxBLnHbJgMlU32fBXjtY900q/nklo=
Received: by 10.66.242.20 with SMTP id p20mr1869986ugh.1182415014853;
	Thu, 21 Jun 2007 01:36:54 -0700 (PDT)
Received: from ?192.168.1.101? ( [85.232.174.201])
	by mx.google.com with ESMTP id j1sm5544049ugf.2007.06.21.01.36.53
	(version=SSLv3 cipher=RC4-MD5); Thu, 21 Jun 2007 01:36:54 -0700 (PDT)
Message-ID: <467A38A3.1050808@gmail.com>
Date: Thu, 21 Jun 2007 10:36:51 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
In-Reply-To: <4678396E.4000204@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-19 22:15, Jeroen Massar wrote:
> Manfredi, Albert E wrote:
> 
>> Jeroen, what about this quote from the draft:
>>
>> Sorry I mutilated your name again!
> 
> Don't worry about that, that happens everywhere (even I typo it) ;)
> 
>> 4.1 DNS Issues
>>
>>    AAAA and PTR records for centrally assigned local IPv6 addresses may
>>    be installed in the global DNS.  This may be useful if these
>>    addresses are being used for site to site or VPN style applications,
>>    or for sites that wish to avoid separate DNS systems for inside and
>>    outside traffic.
>>
>>    The operational issues relating to this are beyond the scope of this
>>    document.
> 
> Not to mean it nastily but shoving the problem off to something else is a
> very easy thing to do. If the ULA-C draft is going to define support for DNS
> then it should also mention all the known operational problems that can
> occur with it. The entity that will perform the registry function is really
> not going to document or figure those things out.

I see Thomas' argument for tolerating occasional use of AAAA entries in the
global DNS for ULAs - but it seems that it leads to too many complications
to be recommended. Since I'm sure the IETF isn't ready yet to endorse the
reality of split DNS deployment, wouldn't it be best to say that ULA-Cs
SHOULD NOT be included in the global DNS? (And that is a significant
difference in scope and intent compared with PI.)

     Brian

> 
> The above hosts are Internet connected and most likely will thus also end up
> talking to the Internet at one point or another. I can thus only guess that
> they will be wanting to fully connect to the Internet one day and the
> generic solution to that problem is NAT. We wanted to get rid of NAT for
> IPv6. If NAT is again being done for IPv6 then we can just as well give up
> and just keep on using IPv4 as there really is not a single advantage then
> anymore to IPv6.
> 
> But see below for a scenario that might have actual merit here.
> 
> Pekka Savola wrote:
> [..]
>> I do not know the intended deployment scenarios
> 
> And this is the whole problem with ULA-C from what I see.
> 
> What are the intended deployment scenarios?
> Or to put it better: what is the problem that needs to be solved?
> 
> I explicitly noted the drafts existence and instructions how people can and
> that they should comment on this, I still have to see a mostly-RIR person
> coming up with their views, or better somebody (and rather multiple) folks
> that actually want to use it.
> 
> ULA (rfc4193) solves the problem of a "routed dental office", pop your boxes
> out of the truck, plugin a ULA-capable router box in the middle et presto it
> works. This is also already partially what link-locals solve, but those
> don't work in a routed manner.
> 
> But what is ULA-C supposed to solve, especially in light that "IPv6 PI"
> exists and is fairly easy to get?
> 
>> but in many cases where
>> I'd expect ULA-C migth be deployed, I'd expect such sites to have some
>> global addresses as well for v4, v6 or both (maybe at a different
>> physical site, just for a couple of infrastructure servers instead of
>> all hosts, etc.)
> 
> In case you have 'infrastructure servers', aka your local DNS, then it
> becomes very easy to let them return answers for your local ip6.arpa tree,
> just add the zone as a master. No need for configuring
> 
> So, lets assume I have a ULA-C address, how exactly am I going to look up
> the reverse? I need to have some kind of global address. When I have a
> global address then what is the whole point of ULA, as I am connected already.
> 
> 
> **SCENARIO**
> One possible scenario could maybe be: use ULA-C local in your local site,
> use global (PA) addresses from the upstream ISP, from whom you get a /48
> too, thus the number plan is the same, just different first 48 bits. Every
> host gets a ULA and a PA address. The PA address might change when changing
> ISP. RFC3484 and related work can be used to configure preferring what
> address to use. Then you never need to reconfigure your local network and
> local addresses are globally unique and can use the Internet.
> 
> The big thing there is though: configure your firewalls correctly as the
> public addresses do also allow access to everything.
> 
> Still, the above can also be accomplished perfectly fine with PI space and
> that doesn't require any changes (except RIPE+APNIC policy) to be done.
> 
>> You're right that if a ULA(-C) site would have no global addresses
>> whatsoever, reverse-DNS delegations can't be done.
> 
> The above example demonstrates that indeed.
> 
> Another funny thing there to note is that some people might want to use
> ULA-C to 'hide' their infrastructure, as it will be completely disconnected
> from the Internet. By introducing reverse dns though, those queries will be
> ending up at several DNS servers on the big bad public internet. Of course
> the NS record will be cached, but some information does get leaked.
> 
> Greets,
>  Jeroen
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 04:42:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1IF5-00058C-4h; Thu, 21 Jun 2007 04:42:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1IF4-000587-ID
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:42:14 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1IF4-0004aY-2c
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:42:14 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1382358ugf
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 01:42:13 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=UBLWIojfPOSsvbko1uuuMusg01hqsc+8im9pkv2F5iuOrURyik/vSwvyplhQXUkwCETy6kiqx1YVaxiE4UCtNw1i1DiIvbQogg1vno0P3EySvEIKATavUIUBbsf6xVGa7ejtPzGKp2ZYZ3/i2sjwDk/9kgk0MGLD5+nMZB+bW+0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=uBzwSCXeq5HpZNLyOnYdE8dS0fLp74s2LgasWoe1LNqECBEnQRaubUHYksq+UersILl0ppRrcW+7YLbEAc7dwoRDoTnIK9eTz5UgzMDPdcULqZFP1HfhE2+5MDgpdOyg0GGDh29EMkU7T76YreT6HF/ps6BADEvwFcFZk1GtJWo=
Received: by 10.66.242.19 with SMTP id p19mr1895267ugh.1182415333465;
	Thu, 21 Jun 2007 01:42:13 -0700 (PDT)
Received: from ?192.168.1.101? ( [85.232.174.201])
	by mx.google.com with ESMTP id 30sm5548242ugf.2007.06.21.01.42.12
	(version=SSLv3 cipher=RC4-MD5); Thu, 21 Jun 2007 01:42:12 -0700 (PDT)
Message-ID: <467A39E2.3020303@gmail.com>
Date: Thu, 21 Jun 2007 10:42:10 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
In-Reply-To: <467853B0.5010806@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-20 00:07, Scott Leibrand wrote:
> Here's a use case for ULA-C that demonstrates its usefulness, and 
> demonstrates why reverse DNS for ULA-C blocks is a valuable enough 
> service that we shouldn't purposefully break it for the public 
> Internet.  Let's say, for example, that I'm a very small ISP with IPv6 
> PA space from my upstream(s).  I give out subnets of that PA space to my 
> customers in an automated dynamic fashion, and I don't run BGP, so I 
> don't need or want PI space.
> 
> However, I do have some routers with interfaces that need numbering, and 
> I'd rather avoid renumbering them when I change upstreams.  Since ULA-C 
> is cheap and easy to get, I register myself a block of it, and use it to 
> number my router interfaces.  Since I'd rather my customers saw DNS 
> names instead of IPv6 addresses in their traceroutes, I delegate the 
> reverse DNS for my ULA-C block to a nameserver on my upstream's PA 
> space, and set up proper PTR records for all my routers.
> 
> Now, whenever anyone does a traceroute into or out of my network, 
> they'll see ULA-C addresses in the traceroute.  They don't need to 
> actually reach those addresses if they're not in my network, but they 
> will at least be able to resolve PTR records for them, so that the 
> traceroute cleanly shows whose network they're traversing.
> 
> And whenever I decide to switch upstreams, all I have to do is update my 
> DHCP servers, update my nameserver's A record to an IP out of my new 
> upstream's PA space, and we're done.  I don't have to renumber a single 
> router, I don't have to run BGP, and I don't have to litter the DFZ with 
> another PI block.

Scott, what feature of existing ULAs makes them unsuitable for this
usage today? In the ridiculously unlikely event of a ULA prefix clash,
this would be detected up-front when trying to set up the reverse
delegation, and then you'd simply generate a different ULA prefix.

     Brian

> 
> -Scott
> 
> michael.dillon@bt.com wrote:
>>> IMHO, if reverse DNS is provided, it should be required that the 
>>> authoritative DNS servers have non-ULA addresses.     
>>
>> Not only that, but since the goal of ULA-C addresses is to provide
>> something similar to what site-local was going to be, perhaps the RIRs
>> should operate authoritative reverse DNS servers for the entire ULA-C
>> space to ensure that reverse DNS for ULA-C addresses is permanently
>> broken on the public Internet. Of course, anyone who wants to run their
>> own internal reverse DNS in their own private network, or networks,
>> should feel free to do so.
>>
>> Is the goal of this document merely to define the ULA-C address range
>> well enough to throw it into the lake and see if it sinks or swims? Or
>> is there some requirement to provide a more workable form of site-local
>> addresses?
>>
>> --Michael Dillon
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>   
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 04:52:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1IOk-0006Wz-A8; Thu, 21 Jun 2007 04:52:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1IOi-0006OG-CZ
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:52:12 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1IOh-0005xr-Ux
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:52:12 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1384660ugf
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 01:52:11 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=DETw2g1+PmEHGiCJ/4IOJt8HBv4C0I8Tkft1m//KNSrFF3rBLCM71OaZKFDOTwgBjOCArQORT+fPvz5ZwYkfyp0FyeuSaKPlJHMRN6cDtMC2+aD6Rz5MRv2Jdc57ggKVMjACZYoDhVh5vs3Ju5vVdBsUm5UBEJ2WGjcxWRBGwrc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lkWuYvbvaRNoRsMFs5B64zr48poBJ5X1b0qAeiPTMBv81DQqYmGn52mhZzjBQeuTJhzQu+79zS5qVaC9XuvS52jMMSMtn3FO0kbjC40tgZd7+ol7bY9Lb50fyYcH628xJykWU023TmpSe+WLSvlYwvhPQv0LcSZPDQnDnO/q/2o=
Received: by 10.67.32.19 with SMTP id k19mr1888460ugj.1182415931135;
	Thu, 21 Jun 2007 01:52:11 -0700 (PDT)
Received: from ?192.168.1.101? ( [85.232.174.201])
	by mx.google.com with ESMTP id l40sm1837008ugc.2007.06.21.01.52.10
	(version=SSLv3 cipher=RC4-MD5); Thu, 21 Jun 2007 01:52:10 -0700 (PDT)
Message-ID: <467A3C38.8090606@gmail.com>
Date: Thu, 21 Jun 2007 10:52:08 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
In-Reply-To: <46796246.4050705@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - avoid policy costs
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-20 19:22, Scott Leibrand wrote:
> Leo Vegoda wrote:
>> On 20 Jun 2007, at 12:36am, Scott Leibrand wrote:
>>
>> [...]
>>
>>>> Is this not already possible with a /48 PI assignment from ARIN?
>>> Yes, but only if you "qualify for an IPv4 assignment or allocation 
>>> from ARIN under the IPv4 policy currently in effect."  That currently 
>>> means you must either be a large network (qualifying for a /20), or 
>>> you must be large enough to run BGP, be multi-homed, and be large 
>>> enough to justify a /22.
>>>>
>>>> Is ULA-C a new solution for a problem that's already been solved 
>>>> with PI assignments or does it solve a new problem?
>>>>
>>> I believe there is a gap between the current PI policy, which is 
>>> targeted at organizations large enough to qualify for a routing slot, 
>>> and the need many smaller organizations have for their own IP space 
>>> for various internal uses. Some of those organizations will be happy 
>>> to use ULA-L, but some will need a guarantee of uniqueness and the 
>>> ability to list their IP space in DNS (.arpa) and in whois.  If we 
>>> can meet the needs of those organizations without having to relax the 
>>> requirements for PI space, we can reduce future pressure on the DFZ.
>>
>> So am I right in reading your answer as saying that the advantage of 
>> ULA-C is that it solves the same problem that ARIN's IPv6 PI policy 
>> solves but better. In effect, developing ULA-C helps side-step ARIN's 
>> policy development process?
>>
> No, it solves a similar problem for a different (though possibly 
> partially overlapping) set of networks, and reduces the pressure to 
> apply a hammer when a screwdriver is what's really needed.
> 
> I would anticipate that for ULA-C to be implemented, RIR policy would 
> need to be updated to codify how the RIRs would administer ULA-C.  As an 
> active member of ARIN's policy process, I see ULA-C as something that 
> should be administered by the RIRs, not by a separate registry, so that 
> the RIRs can direct applicants to the appropriate resources (PI for 
> large or multihomed networks, ULA-C for private, non-routed space for 
> those who don't qualify for PI, etc.)

This is the place for me to say that I believe the draft is wrong in
delegating this as an RIR policy matter. Like existing ULAs, ULA-C
should be treated as *technical* address space, and we should specify
that assignments will be made and recorded by a single instance of
a robot, operated by a trusted party. Designation of that trusted party
could certainly be a matter for IANA to negotiate with the community.

I see only downsides (unnecessary costs and useless policy discussions)
in treating this as anything but a purely technical matter. Let's leave
the policy discussions for matters where fairness and route scaling
are at stake. ULAs are plentiful (so there is no fairness issue) and
not WAN-routeable (so there is no route scaling issue).

If we don't do this, ULA-C has no noticeable advantage over PI
and we should just forget it IMHO.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 04:58:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1IUd-0004x0-0q; Thu, 21 Jun 2007 04:58:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1IUb-0004wm-0w
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:58:17 -0400
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1IUa-0007sF-JL
	for ipv6@ietf.org; Thu, 21 Jun 2007 04:58:16 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1386060ugf
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 01:58:15 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=HhtUq1HBS4U5JtuaF6bAiqy4R/6x6vW2INvabXoiQvtrJCkd9xQ1myMtLMZF/hZcHkmUUUb+7CAUUNr09V2SHrVsfWOnDiFHoDW74sCQI2OEh9OxmS0/ucr3YnW17PBW09qIIsDOihvr4FvFU9s4NNvDw6VetIBnbW/MaAbijro=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=MSmq29G8zsb+s01tAWODogMOzCM5nqGNt1Ad6SqW6JXU9SpheadwDjWS58l1fOknWTTOUr/2Gg39pO4LaWr7CzbfmcP+2PbMuBovmv6r1v1sSKrOSCOu8TaJ51AiIcSfmSOCdlkTDppu04C/4aQaa8hFIjm0Ww//nyH9BVnMBgM=
Received: by 10.67.101.8 with SMTP id d8mr1904752ugm.1182416295584;
	Thu, 21 Jun 2007 01:58:15 -0700 (PDT)
Received: from ?192.168.1.101? ( [85.232.174.201])
	by mx.google.com with ESMTP id q55sm1850439ugq.2007.06.21.01.58.14
	(version=SSLv3 cipher=RC4-MD5); Thu, 21 Jun 2007 01:58:15 -0700 (PDT)
Message-ID: <467A3DA4.5030603@gmail.com>
Date: Thu, 21 Jun 2007 10:58:12 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Perry Lorier <perry@coders.net>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>	<4678396E.4000204@spaghetti.zurich.ibm.com>	<467870DC.2030802@internap.com>	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>	<20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>	<E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
	<4679DC6C.8040509@coders.net>
In-Reply-To: <4679DC6C.8040509@coders.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT and stateful filters
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-21 04:03, Perry Lorier wrote:
> james woodyatt wrote:
>> On 20 Jun 2007, at 15:10, Mark Smith wrote:
>>> On Wed, 20 Jun 2007 11:16:15 -0700 james woodyatt <jhw@apple.com> wrote:
>>>>
>>>> I'd be more sympathetic to arguments like this if we RFC 4864 didn't
>>>> insist on recommending  the deployment of stateful packet filters in
>>>> IPv6 that break most of the things NAT breaks in IPv4.

I'd like to say, as co-author of RFC 4864, that in my mind it simply
recognizes the reality that firewalls exist, will exist for the
foreseeable future, and will include stateful filters, so we have to
deal with it. (more below)

>>>
>>> How does a stateful firewall, present on the end-node itself, cause 
>>> these problems?
>>
>> We see this all the time today with stateful packet filters in IPv4 
>> nodes at global unicast addresses.  Application binds to a socket for 
>> accepting connections, but that isn't enough for accepting incoming 
>> connections.  Application need to obtain authorization to request the 
>> firewall to allow incoming connections.  That involves asking a user 
>> for a password.  Bletch.
> 
> And then there is no real standard for asking for that authorization in 
> the first place.  A lot of applications embed UPnP, which I guess is as 
> close to a standard for being able to request a listening port as we 
> have.  Many protocols have ways of testing to see if a listening port 
> really is listening, since there is no real local feedback from 
> firewalls that your listening port is being filtered or NAT'd or had any 
> number of other things done to it.
> 
> And then we get software developers abusing what is really a bug in 
> stateful boxes in the name of "nat transversal".  Operators and end 
> users regularly say "Your new application should support nat 
> transversal" rather than fixing the underlying problems.
> 
>> Moreover, firewall knows how to track state for TCP and UDP, because 
>> that's all the transports the IP stack knows about.  It would be 
>> reasonable to port implementations of SCTP and DCCP to live there as 
>> well, but nobody bothers because the firewall doesn't know about those 
>> transports and needs to be taught about them from scratch.  
>> Consequently, applications that should use DCCP or SCTP, use TCP or 
>> UDP instead, so they can work with the firewall interface they have.
>>
>> Firewalls don't get upgraded to support SCTP and DCCP because 
>> applications are all limping along with TCP and UDP.  Egg: meet chicken.
> 
> And these boxes don't support this "new fangled" IPv6 thing either. 
> Operators claim theres no point in pushing IPv6 out to customers coz 
> their CPE's don't support it.

All true. So please start a thread on the v6ops list about
draft-ietf-v6ops-cpe-simple-security and draft-woodyatt-ald,
where there is some attempt to tackle these issues. James is too modest...

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 05:32:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1J0w-0003no-P7; Thu, 21 Jun 2007 05:31:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1J0v-0003na-G0
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:31:41 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1J0u-0006UU-2F
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:31:41 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:31:19 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 10:32:08 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08FC0F7@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt and NAT
Thread-Index: Acezh91/UsZUloJNTGGQgV1aCy3ifwAXcnKQ
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><46782E58.6070705@spaghetti.zurich.ibm.com><Pine.LNX.4.64.0706192236490.10422@netcore.fi><4678396E.4000204@spaghetti.zurich.ibm.com><467870DC.2030802@internap.com><20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org><A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
	<20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Jun 2007 09:31:20.0450 (UTC)
	FILETIME=[ED10CE20:01C7B3E6]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: RE: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > I'd be more sympathetic to arguments like this if we RFC=20
> 4864 didn't=20
> > insist on recommending  the deployment of stateful packet filters in
> > IPv6 that break most of the things NAT breaks in IPv4.

> It seems to me that you're=20
> making the assumption that the only scenario IPv6 will be=20
> deployed in is one where end-nodes always have an upstream=20
> stateful firewalling device.=20

Even if the stateful firewalling algorithm is being executed by an
upstream device, the fact that the IPv6 destination address is globally
known means that the device knows exactly which internal device is the
intended destination of the packet. This makes it easier for additional
software on the upstream device to do something intelligent that will
not break connectivity in the way that IPv4 NAT/PAT does.

For instance, there could be an application on the end host that
receives notifications from the upstream device so that the user can
accept the packet flow. Or there could be a bit of software on the
upstream device that recognizes this particular packet as belonging to a
known protocol which should be allowed through. Some of this already
exists in IPv4 such as application layer gateways, but some is yet to be
developed.

IPv6 brings a fundamental difference, that the end hosts can use
globally unique addresses and that the upstream gateways do not need to
do any address translation in order to apply stateful firewalling. Once
this becomes more widely understood, then some creative solutions like
the host notification mentioned above, could be implemented.=20

Also, firewalling is a process. It has already been pointed out that the
process could take place on the end hosts. It can also be distributed
between the end host and an upstream gateway. Or even partly distributed
to a 3rd party host inside the perimeter by diverting the packet flow
such as is often done with proxy caching. Because of the broad
possibilities it is hard to make absolute statements about what effect
firewalls will have on any particular protocol.

--Michael Dillon

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 05:47:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1JG8-0006xM-3s; Thu, 21 Jun 2007 05:47:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1JG7-0006xH-3u
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:47:23 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1JG4-0000Y4-Mq
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:47:23 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:47:19 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 10:48:41 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08FC120@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt and NAT
Thread-Index: AcezkFVQa0nsvOMITsWy4+gadDGllAAVuRKQ
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><46782E58.6070705@spaghetti.zurich.ibm.com><Pine.LNX.4.64.0706192236490.10422@netcore.fi><4678396E.4000204@spaghetti.zurich.ibm.com><467870DC.2030802@internap.com><20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org><A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com><20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Jun 2007 09:47:19.0810 (UTC)
	FILETIME=[28E38620:01C7B3E9]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: RE: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Firewalls don't get upgraded to support SCTP and DCCP because=20
> applications are all limping along with TCP and UDP.  Egg:=20
> meet chicken.

Sounds like a good area for standardization so that this state of
affairs is not carried forward into IPv6. And especially, if there is a
standard way for upstream gateways with stateful filtering to talk to
end hosts with stateful filtering, then the two of them can agree to
divide the work such that the DCCP-related code runs on the end host.

> If NAT between PA and ULA-C unicast addresses solves a=20
> problem for somebody, without breaking anything important=20
> that isn't already broken by something else we've already=20
> done, then why shouldn't we be pragmatic and define a mostly=20
> sensible way for them to do it?

No.=20
End hosts that need to communicate on the Internet should have globally
unique IPv6 addresses end-to-end. ULA is for end hosts that do not need
to communicate beyond the boundaries of an administrative domain. And
since IPv6 allows multiple addresses per end-host, those hosts who need
to be schizophrenic can use both ULA and globally unique addresses.
Network Address Translation does not seem to offer anything new here.

--Michael Dillon

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 05:53:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1JM9-00021t-R1; Thu, 21 Jun 2007 05:53:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1JM8-00021o-6s
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:53:36 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1JM6-0001Oc-Us
	for ipv6@ietf.org; Thu, 21 Jun 2007 05:53:36 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.113]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 10:53:32 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 10:54:53 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B08FC131@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <467A3C38.8090606@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt - avoid policy costs
Thread-Index: Acez4XvprHqbnkS1Tg2YKMRFIGYd6gACDE1w
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Jun 2007 09:53:32.0725 (UTC)
	FILETIME=[0729D650:01C7B3EA]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: RE: draft-ietf-ipv6-ula-central-02.txt - avoid policy costs
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> This is the place for me to say that I believe the draft is=20
> wrong in delegating this as an RIR policy matter. Like=20
> existing ULAs, ULA-C should be treated as *technical* address=20
> space, and we should specify that assignments will be made=20
> and recorded by a single instance of a robot, operated by a=20
> trusted party. Designation of that trusted party could=20
> certainly be a matter for IANA to negotiate with the community.

In my earlier comment I mentioned that the RIRs should stock a supply of
already-generated ULA-C addresses so that the applicants did not have to
wait while 5 RIRs worked out whether or not there was a conflict. Add
that to Brian's comment above and you have a scenario where IANA runs
the robot, ensures global uniqueness (just like they do with IP
addresses) and allocates a supply of ULA-C addresses to an RIR when
their supply runs low. Since running the robot and maintaining the
database of already-generated ULA-C addresses is a minor technical
matter requiring very little technical infrastructure, it seems
reasonable for the RFC to specify that IANA should do this.

--Michael Dillon

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 06:22:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Jne-0005hL-4C; Thu, 21 Jun 2007 06:22:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Jnb-0005hC-7U
	for ipv6@ietf.org; Thu, 21 Jun 2007 06:21:59 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Jna-0005I6-2j
	for ipv6@ietf.org; Thu, 21 Jun 2007 06:21:59 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I1JnQ-000BR5-N9; Thu, 21 Jun 2007 19:51:48 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id BFCA920139;
	Thu, 21 Jun 2007 19:51:46 +0930 (CST)
Date: Thu, 21 Jun 2007 19:51:46 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: james woodyatt <jhw@apple.com>
Message-Id: <20070621195146.68ef2970.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467870DC.2030802@internap.com>
	<20070621033018.46aede5e.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<A6B0EF90-A57E-4820-925D-57533D0A464D@apple.com>
	<20070621074007.577f1b7b.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<E8D74160-3F70-4D8E-B3F0-48C7EC45B4E2@apple.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt and NAT
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 20 Jun 2007 16:11:01 -0700
james woodyatt <jhw@apple.com> wrote:

> On 20 Jun 2007, at 15:10, Mark Smith wrote:
> > On Wed, 20 Jun 2007 11:16:15 -0700 james woodyatt <jhw@apple.com>  
> > wrote:
> >>
> >> I'd be more sympathetic to arguments like this if we RFC 4864 didn't
> >> insist on recommending  the deployment of stateful packet filters in
> >> IPv6 that break most of the things NAT breaks in IPv4.
> >
> > How does a stateful firewall, present on the end-node itself, cause  
> > these problems?
> 
> We see this all the time today with stateful packet filters in IPv4  
> nodes at global unicast addresses.  Application binds to a socket for  
> accepting connections, but that isn't enough for accepting incoming  
> connections.  Application need to obtain authorization to request the  
> firewall to allow incoming connections.  That involves asking a user  
> for a password.  Bletch.
> 

While I agree that isn't the ideal interface, I really think that
mostly is a user interface/OS implementation problem, not a network
architecture or protocol problem. Why should we "fix" the problem
within the network when the problem is fundamentally occuring at the
boundary between the application and the OS i.e. the networking API.

I'm sure you know this, security comes at the cost of
convenience. If somebody doesn't want to have to "put up" with these
sorts of prompts, then I think that means that they've got their
security settings too high or too sensitive. 

Effort certainly needs to be put into trying to make Internet security
as convenient as it can be. However, a line has to be drawn to identify
the point where if security is made any more convenient than "this",
security is being compromised, and people will be forced to make a
choice between convenience and security.

> Moreover, firewall knows how to track state for TCP and UDP, because  
> that's all the transports the IP stack knows about.  It would be  
> reasonable to port implementations of SCTP and DCCP to live there as  
> well, but nobody bothers because the firewall doesn't know about  
> those transports and needs to be taught about them from scratch.   
> Consequently, applications that should use DCCP or SCTP, use TCP or  
> UDP instead, so they can work with the firewall interface they have.
> 
> Firewalls don't get upgraded to support SCTP and DCCP because  
> applications are all limping along with TCP and UDP.  Egg: meet chicken.
> 

Well, most of the ADSL CPE that my company sells to customers runs
Linux internally (and this is 3rd party commodity CPE, not something
we've put together ourselves). And here is what I've found under the
manual page for the current version of the command line firewalling
configuration utility :

 dccp
       --source-port,--sport [!] port[:port]

       --destination-port,--dport [!] port[:port]

...

  sctp
       --source-port,--sport [!] port[:port]

       --destination-port,--dport [!] port[:port]

       --chunk-types [!] all|any|only chunktype[:flags] [...]
              The  flag  letter  in  upper  case indicates that the flag is to
              match if set, in the lower case indicates to match if unset.


So once a web interface is wrapped around that and/or appropriate
defaults are set, I think the chicken has not only hatched but it is
nearly roasted. Of course these devices are also doing NAT commonly, so
at least for IPv4, it'd be somewhat of a wasted effort.


> > It seems to me that you're making the assumption that the only  
> > scenario IPv6 will be deployed in is one where end-nodes always  
> > have an upstream stateful firewalling device.
> 
> This is likely to be *more* common in the future than it already is  
> today.  Residential IPv6 gateway devices are shipping now in consumer- 
> grade Wi-Fi AP/router products, and they include these packet filters  
> turned on by default.  More are forthcoming.  Their owners are rarely  
> even made aware of these packet filters.  Most won't discover them  
> until they try to do something silly and stupid, like receive  
> incoming VoIP calls over IPv6, fail utterly, and then *maybe* track  
> down the source of the ICMP "administratively prohibited" errors to  
> their own router.
> 

Ask yourself what is the most widely used communications device that
people use. If you can't guess that, ask yourself what recently
announced product from your employer has generated worldwide publicity,
popularity and demand months before it is going to be released, even in
places where it is unlikely to be released in any time soon.

Will that have a firewall on it, or will the customers of that also
have to buy an iFirewall to go with it, because the device itself won't
do firewalling, even though I'd be guessing the OS sitting on it is
easily capable of doing so, and would have enough processing power to do it.

If it doesn't have firewall on it, and the customer doesn't have a
bluetooth or wifi iFirewall in their pocket, where is the carrier going
to put the firewall for all of their customers. How is that firewall
going to scale to support 1000s, 10s or 100s of 1000s of updates to
rules. How is that central firewall going to protect the device from
other malicious customers who are also behind it, and therefore who's
malicious traffic doesn't go through the upstream carrier firewall (I'm
guessing that teenagers would get much more fun out of DoSing the old
man down the road's phone rather than one overseas, because they might
be able to physically see the reaction)

What I'm interpreting you to be saying is :

(a) you seem to be making a very broad and general statement that NAT
is necessary for IPv6

(b) yet your only deployment scenario is one where there is an upstream
stateful firewall that is owned and in control of the person who owns
the downstream devices, and is in close proximity to the devices that
it is protecting.

You may not be exactly saying (a), however it seems to me you're going
close to it.

My argument to those points is :

(a) lets not assume NAT is the only way to solve these problems, as we
already know, recognise and suffer from problems that NAT has created
from IPv4. Let's get creative, and try to solve these problems without
incuring the costs of address translation.

(b) don't assume that what is most likely to be the most common IPv4
case is going to be the most common IPv6 case. Even better, think about
how and where IPv6 is different to IPv4, and try to then identify
possible scenarios that were impossible with IPv4, and then ensure that
IPv4 "thinking" applied to IPv6 doesn't inherently preclude options
that are only possible with IPv6.


> Architecture is hard, folks.  Despite our best laid architectural  
> planz, we are certain to be plagued with middleboxes at every level  
> of the Internet.  They're going to interfere with everything.   
> Basically, if it's known to work today over IPv4/NAT, then there's a  
> pretty good chance it will still work tomorrow over IPv6.  That's  
> about the best we can hope for at this point.
> 
> If NAT between PA and ULA-C unicast addresses solves a problem for  
> somebody, without breaking anything important that isn't already  
> broken by something else we've already done, then why shouldn't we be  
> pragmatic and define a mostly sensible way for them to do it?
> 

That's the crux. Why is NAT immediately sensible, just because it was
somewhat effective in IPv4, when we're moving to something new ? It
reminds me a bit of the cliche, "if the only tool you have is a hammer,
every problem looks like a nail."

> p.s. Readers are encouraged to consider whether this message is a  
> devil's advocacy.
> 
>

That's fair enough, but the devil also usually wants you to accept
things you really shouldn't, and you'll end up paying a price far
higher than you ever imagined :-) People, including me, call NAT "evil"
for a reason :-)

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 06:27:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Jt7-0001ae-Er; Thu, 21 Jun 2007 06:27:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Jt5-0001aX-9Q
	for ipv6@ietf.org; Thu, 21 Jun 2007 06:27:39 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Jt3-0006Vu-Qu
	for ipv6@ietf.org; Thu, 21 Jun 2007 06:27:39 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5LART4K042544;
	Thu, 21 Jun 2007 20:27:30 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706211027.l5LART4K042544@drugs.dv.isc.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Thu, 21 Jun 2007 10:36:51 +0200."
	<467A38A3.1050808@gmail.com> 
Date: Thu, 21 Jun 2007 20:27:29 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Thomas Narten <narten@us.ibm.com>, ipv6@ietf.org,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



> I see Thomas' argument for tolerating occasional use of AAAA entries in the
> global DNS for ULAs - but it seems that it leads to too many complications
> to be recommended. Since I'm sure the IETF isn't ready yet to endorse the
> reality of split DNS deployment, wouldn't it be best to say that ULA-Cs
> SHOULD NOT be included in the global DNS? (And that is a significant
> difference in scope and intent compared with PI.)
> 
>      Brian

	It really is no worse than having any other address which is
	partly or fully firewalled off.  The big difference between
	ULA-C and ULA-L is the the former is guarenteed to be unique
	and the later is not.  Ambigious addresses in the DNS are bad.
	Non reachable (except for nameservers) arn't.

	Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 09:57:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1N9D-0005mE-1R; Thu, 21 Jun 2007 09:56:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1N9B-0005m9-0S
	for ipv6@ietf.org; Thu, 21 Jun 2007 09:56:29 -0400
Received: from e35.co.us.ibm.com ([32.97.110.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1N98-0000mO-N9
	for ipv6@ietf.org; Thu, 21 Jun 2007 09:56:28 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5LDuQZR006874
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 09:56:26 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5LDuPqZ210446 for <ipv6@ietf.org>; Thu, 21 Jun 2007 07:56:25 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5LDuO7L010058 for <ipv6@ietf.org>; Thu, 21 Jun 2007 07:56:24 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-128-10.wecm.ibm.com
	[9.67.128.10])
	by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5LDuM3d009947
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 21 Jun 2007 07:56:24 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5LDuL9n019456;
	Thu, 21 Jun 2007 09:56:21 -0400
Message-Id: <200706211356.l5LDuL9n019456@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-reply-to: <467A38A3.1050808@gmail.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467A38A3.1050808@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com>
	message dated "Thu, 21 Jun 2007 10:36:51 +0200."
Date: Thu, 21 Jun 2007 09:56:21 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I see Thomas' argument for tolerating occasional use of AAAA entries in the
> global DNS for ULAs - but it seems that it leads to too many complications
> to be recommended. Since I'm sure the IETF isn't ready yet to endorse the
> reality of split DNS deployment, wouldn't it be best to say that ULA-Cs
> SHOULD NOT be included in the global DNS? (And that is a significant
> difference in scope and intent compared with PI.)

Note: a key question is whether the RIRs (as they hand out ULA-C
blocks) allow PTRs to be inserted in the DNS. They either do or they
don't. Saying folk "SHOULD NOT" doesn't answer a key question
definitively.

Note: we have no say/control over whether AAAA records contain
ULAs. End sites can (and will) do what they want here; we have no way
of preventing that (though we can recommend they don't and explain why
it may not be a good idea).

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 09:59:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1NCD-0006iW-T0; Thu, 21 Jun 2007 09:59:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1NCB-0006iO-UY
	for ipv6@ietf.org; Thu, 21 Jun 2007 09:59:35 -0400
Received: from e6.ny.us.ibm.com ([32.97.182.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1NCA-0001Yo-Fh
	for ipv6@ietf.org; Thu, 21 Jun 2007 09:59:35 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e6.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l5LE0gaG005959
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 10:00:42 -0400
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.3) with ESMTP id
	l5LDxX5g465010 for <ipv6@ietf.org>; Thu, 21 Jun 2007 09:59:34 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l5LDxWQx017318 for <ipv6@ietf.org>; Thu, 21 Jun 2007 09:59:32 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-128-10.wecm.ibm.com
	[9.67.128.10])
	by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l5LDxUhV017277
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 21 Jun 2007 09:59:31 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.8/8.12.5) with ESMTP id l5LDxT72020411;
	Thu, 21 Jun 2007 09:59:29 -0400
Message-Id: <200706211359.l5LDxT72020411@cichlid.raleigh.ibm.com>
To: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: <200706211027.l5LART4K042544@drugs.dv.isc.org> 
References: <200706211027.l5LART4K042544@drugs.dv.isc.org>
Comments: In-reply-to Mark Andrews <Mark_Andrews@isc.org>
	message dated "Thu, 21 Jun 2007 20:27:29 +1000."
Date: Thu, 21 Jun 2007 09:59:29 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Mark Andrews <Mark_Andrews@isc.org> writes:

> > I see Thomas' argument for tolerating occasional use of AAAA entries in the
> > global DNS for ULAs - but it seems that it leads to too many complications
> > to be recommended. Since I'm sure the IETF isn't ready yet to endorse the
> > reality of split DNS deployment, wouldn't it be best to say that ULA-Cs
> > SHOULD NOT be included in the global DNS? (And that is a significant
> > difference in scope and intent compared with PI.)
> > 
> >      Brian

> 	It really is no worse than having any other address which is
> 	partly or fully firewalled off.  The big difference between
> 	ULA-C and ULA-L is the the former is guarenteed to be unique
> 	and the later is not.  Ambigious addresses in the DNS are bad.
> 	Non reachable (except for nameservers) arn't.

I don't think it's that black/white. Unreachable addresses for
delegations are bad because they result in long time outs for end
users. That is not good and should be discouraged. So, there is a
difference depending on whether one is talking about AAAA or PTR
records.

That said, I agree that ambiguous addresses are a different and much
worse problem.

Thomas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 11:23:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1OUX-0001kY-QT; Thu, 21 Jun 2007 11:22:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1OUW-0001kT-9S
	for ipv6@ietf.org; Thu, 21 Jun 2007 11:22:36 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1OUV-00048s-0m
	for ipv6@ietf.org; Thu, 21 Jun 2007 11:22:36 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.149461443;
	Thu, 21 Jun 2007 11:27:10 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 21 Jun 2007 11:22:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 21 Jun 2007 11:22:09 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A023EFB20@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02 and RIR documentation
Thread-Index: Acez3eeooapp1RHXQHer0vTz386FFwAOagfQ
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 21 Jun 2007 15:22:13.0631 (UTC)
	FILETIME=[F1BD48F0:01C7B417]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02 and RIR documentation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1802790948=="
Errors-To: ipv6-bounces@ietf.org

--===============1802790948==
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SSBhZ3JlZS4gIA0KDQpJIGdvdCBhIHJlc3BvbnNlIGZyb20gb25lIG9mIHRoZSBhdXRob3JzIGFm
dGVyIHRoaXMgc2F5aW5nIG15IGludGVycHJldGF0aW9uIHdhcyBjb3JyZWN0LiAgU28gdGhpcyB3
b3VsZCBiZSBvbmUgY29ycmVjdGlvbiB0aGF0IG5lZWRzIHRvIGJlIG1hZGUuDQoNCkkgd2lsbCBh
c2sgdGhlIGF1dGhvcnMgZm9yIHRoaXMgY2xhcmlmaWNhdGlvbiBpbiB0aGUgd29yZGluZyB0byBi
ZSBtYWRlLg0KDQpDaGVlcnMhDQpNYXJsYQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogQnJpYW4gRSBDYXJwZW50ZXIgW21haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5j
b21dDQpTZW50OiBUaHVyc2RheSwgSnVuZSAyMSwgMjAwNyAxOjI2IEFNDQpUbzogQXppbmdlciwg
TWFybGENCkNjOiBtaWNoYWVsLmRpbGxvbkBidC5jb207IGlwdjZAaWV0Zi5vcmcNClN1YmplY3Q6
IFJlOiBkcmFmdC1pZXRmLWlwdjYtdWxhLWNlbnRyYWwtMDIgYW5kIFJJUiBkb2N1bWVudGF0aW9u
DQoNCg0KT24gMjAwNy0wNi0xOSAwMDoyOSwgQXppbmdlciwgTWFybGEgd3JvdGU6DQo+IE1pY2hh
ZWwtICBJIGRvbnQgYmVsaWV2ZSB0aGF0IHdhcyB0aGUgaW50ZW50IGFuZCB0aGVyZSBtaWdodCBi
ZSBhIGxpdHRsZSBtaXNpbnRlcnByZXRhdGlvbiBoZXJlIGR1ZSB0byBob3cgaXQgd2FzIHdyaXR0
ZW4uICBUaGUgZG9jdW1lbnQgc2F5czoNCj4gDQo+PiBUaGUgZGVzaWduYXRlZCBhbGxvY2F0aW9u
IGF1dGhvcml0eSBpcyByZXF1aXJlZCB0byBkb2N1bWVudCBob3cgdGhleQ0KPiAgICB3aWxsIG1l
ZXQgdGhlIHJlcXVpcmVtZW50cyBkZXNjcmliZWQgaW4gU2VjdGlvbiAzLjIgb2YgdGhpcyBkb2N1
bWVudA0KPiAgICBpbiBhbiBSRkMuPA0KPiANCj4gVGhpcyBzdGF0ZXMgdGhlIFJJUidzIG5lZWQg
dG8gZG9jdW1lbnQgaG93IHRoZXkgd2lsbCBtZWV0IHRoZSByZXF1aXJlbWVudHMgb25jZSBzZWN0
aW9uIDMuMi4gIEl0IGRvbnQgYmVsaWV2ZSB0aGUgYXV0aG9yIGludGVuZHMgZm9yIFJJUidzIHRv
IHdyaXRlIGFuIFJGQy4gIEkgYmVsaWV2ZSB0aGUgaW50ZW50IG9mIHRoZSBzZW50ZW5jZSB5b3Ug
cXVlc3Rpb24gaXMgYWN0dWFsbHkgc2F5aW5nIGluIGEgcm91bmQgYWJvdXQgd2F5IHRoYXQgUklS
J3MgbmVlZCB0byB1c2UgdGhlaXIgcG9saWN5IHByb2Nlc3MgYW5kIHdyaXRlIHBvbGljeSdzIHRo
YXQgd2lsbCBtZWV0IHRoZSByZXF1aXJlbWVudHMgc3RhdGVkIGluIHNlY3Rpb24gMy4yIG9mIHRo
ZSBkcmFmdC4gIFRodXMsIHN5bmNocm9uaXppbmcgdGhlIFJGQyBhbmQgUklSIHBvbGljeS4NCj4g
DQo+IE9yIGF0IGxlYXN0IHRoYXQgaXMgd2hhdCBJIGhhZCBkaXNjdXNzZWQgb24gYSBjb25mZXJl
bmNlIGNhbGwgd2l0aCBSLiBIaW5kZW4gYW5kIFQuIE5hcnRlbiBiZWZvcmUgdGhlIHJldmlzaW9u
IHdhcyBtYWRlLiAgU28gQm9iIG9yIFRob21hcywgY29ycmVjdCBtZSBpZiBJIGFtIHdyb25nIGhl
cmUuLi4NCg0KTWFybGEsIGlmIHlvdXIgaW50ZXJwcmV0YXRpb24gaXMgY29ycmVjdCAoYW5kIEkg
aG9wZSBpdCBpcykNCnRoZSB3b3JkcyAiaW4gYW4gUkZDIiBuZWVkIHRvIGJlIGRlbGV0ZWQgZnJv
bSB0aGUgZHJhZnQuDQoNCiAgICBCcmlhbg0K


--===============1802790948==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1802790948==--



From ipv6-bounces@ietf.org Thu Jun 21 12:00:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1P5A-0004Iq-1w; Thu, 21 Jun 2007 12:00:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1P4s-0003qh-3h
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:00:10 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1P4q-0003er-T4
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:00:10 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84764716; Thu, 21 Jun 2007 12:00:08 -0400
Message-ID: <467AA083.6070102@internap.com>
Date: Thu, 21 Jun 2007 09:00:03 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
In-Reply-To: <467A39E2.3020303@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> On 2007-06-20 00:07, Scott Leibrand wrote:
>>
>> However, I do have some routers with interfaces that need numbering, 
>> and I'd rather avoid renumbering them when I change upstreams.  Since 
>> ULA-C is cheap and easy to get, I register myself a block of it, and 
>> use it to number my router interfaces.  Since I'd rather my customers 
>> saw DNS names instead of IPv6 addresses in their traceroutes, I 
>> delegate the reverse DNS for my ULA-C block to a nameserver on my 
>> upstream's PA space, and set up proper PTR records for all my routers.
>>
>
> Scott, what feature of existing ULAs makes them unsuitable for this
> usage today? In the ridiculously unlikely event of a ULA prefix clash,
> this would be detected up-front when trying to set up the reverse
> delegation, and then you'd simply generate a different ULA prefix.
>
As far as I know there's no mechanism to delegate reverse DNS for a 
locally generated ULA, since there's no "ownership".  IMO any move to 
start delegating .arpa authority for ULAs would be de facto ULA-C, so if 
we're going to do that we should do it right and do the other 
registration functions that should go along with the DNS delegation.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 12:32:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1PZs-0006oV-9q; Thu, 21 Jun 2007 12:32:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1PZr-0006kX-FG; Thu, 21 Jun 2007 12:32:11 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1PZo-0001Xw-0t; Thu, 21 Jun 2007 12:32:11 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 Jun 2007 12:32:07 -0400
X-IronPort-AV: i="4.16,448,1175486400"; 
	d="txt'222?scan'222,208,217,222"; a="63363866:sNHT261428406"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5LGW7bH008624; 
	Thu, 21 Jun 2007 12:32:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5LGVhMF013215; 
	Thu, 21 Jun 2007 16:32:07 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 12:32:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7B421.B0D2AA56"
Date: Thu, 21 Jun 2007 12:31:58 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace0IbBYv+vS86juTYqhbwHS8+ASlA==
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: <ipv6@ietf.org>, <internet-drafts@ietf.org>
X-OriginalArrivalTime: 21 Jun 2007 16:32:00.0237 (UTC)
	FILETIME=[B126A9D0:01C7B421]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=76548; t=1182443527;
	x=1183307527; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20urgent=2
	0changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20<ipv6@ietf.org>,=20<internet-drafts@ietf.org>;
	bh=SlE+jNZ1H4gCNiETwgePbHlSaBmlzDoX6LeaYg0sr/4=;
	b=A7ABXF+QXBCYbSQvvrROZk6i+x9pEFzP5NSCV8ea66/ogsp+TzwkKBoUfjOecgPeSgI2mH+/
	hC7UppMHCKqEwPwluGpqgMJUyRcB1GHYLwDtIqe4QXXuailkyn2mcYFH;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fe506ca9be60efd944fbfbfd3c8c89f4
Cc: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B421.B0D2AA56
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C7B421.B0D2AA56"


------_=_NextPart_002_01C7B421.B0D2AA56
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,
=20
Here is the Abstract of our I-D that helps explain why we wrote this
I-D. =20
=20
   RFC 2461 [ND] describes host data forwarding and address resolution.
   However, nine years after the ND protocol became an RFC, IPv6 hosts
   still do not fully comply with RFC 2461 [ND].  In particular, hosts
   incorrectly implement on- vs. off-link data forwarding.  This
   document clarifies host behavior and associated router behavior to
   define explicitly address resolution and data forwarding models.  The
   set of new requirements beyond what has been specified in RFC 2461
   [ND] and RFC 2462 [ADDRCONF] is restricted to corrections and
   clarifications deemed necessary to facilitate correct implementation.
=20
=20
Please see section 5 of our I-D for a proposed change to 2462bis-08 - we
hear this I-D is=20
in Editor's queue and any changes to it must be given ASAP.
=20
We have tested and developed host and routers stacks for IPv6 at Cisco.=20
We'd like to be put this I-D on the agenda for the July 2007 IETF
meeting.=20
=20
Thanks.
=20
Kind Regards.
=20
Hemant
=20

------_=_NextPart_002_01C7B421.B0D2AA56
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007>Here =
is the Abstract=20
of our I-D that helps explain why we wrote this I-D.&nbsp; =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007></SPAN><SPAN=20
class=3D231430516-08062007></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D231430516-08062007>&nbsp;&nbsp; RFC=20
2461 [ND] describes host data forwarding and address =
resolution.<BR>&nbsp;&nbsp;=20
However, nine years after the ND protocol became an RFC, IPv6=20
hosts<BR>&nbsp;&nbsp; still do not fully comply with RFC 2461 =
[ND].&nbsp; In=20
particular, hosts<BR>&nbsp;&nbsp; incorrectly implement on- vs. off-link =
data=20
forwarding.&nbsp; This<BR>&nbsp;&nbsp; document clarifies host behavior =
and=20
associated router behavior to<BR>&nbsp;&nbsp; define explicitly address=20
resolution and data forwarding models.&nbsp; The<BR>&nbsp;&nbsp; set of =
new=20
requirements beyond what has been specified in RFC 2461<BR>&nbsp;&nbsp; =
[ND] and=20
RFC 2462 [ADDRCONF] is restricted to corrections and</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D231430516-08062007>&nbsp;&nbsp;=20
clarifications deemed necessary to facilitate correct=20
implementation.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007>Please see section 5 of our I-D for a =
proposed change=20
to 2462bis-08 - we hear this I-D is </SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007>in Editor's queue and any changes to it must =
be given=20
ASAP.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007>We have tested=20
and developed host </SPAN><SPAN class=3D231430516-08062007>and routers =
stacks for=20
IPv6 at Cisco. </SPAN></FONT></FONT></DIV>
<DIV><SPAN class=3D231430516-08062007></SPAN><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D231430516-08062007>We'd like to be put this I-D on the agenda =
for the July=20
2007 IETF </SPAN><SPAN class=3D231430516-08062007>meeting.=20
</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007></SPAN><SPAN=20
class=3D231430516-08062007></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Thanks.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007>Kind=20
Regards.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Hemant</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV></DIV></BODY></HTML>=


------_=_NextPart_002_01C7B421.B0D2AA56--

------_=_NextPart_001_01C7B421.B0D2AA56
Content-Type: text/plain;
	name="draft-wbeebee-nd-implementation-pitfalls-00.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-wbeebee-nd-implementation-pitfalls-00.txt
Content-Disposition: attachment;
	filename="draft-wbeebee-nd-implementation-pitfalls-00.txt"

//4NAAoADQAKAA0ACgBOAGUAdAB3AG8AcgBrACAAVwBvAHIAawBpAG4AZwAgAEcAcgBvAHUAcAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEgALgAgAFMAaQBuAGcAaAANAAoASQBuAHQAZQBy
AG4AZQB0AC0ARAByAGEAZgB0ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAVwAuACAAQgBlAGUAYgBlAGUADQAKAEkAbgB0AGUAbgBkAGUAZAAgAHMAdABhAHQAdQBzADoA
IABTAHQAYQBuAGQAYQByAGQAcwAgAFQAcgBhAGMAawAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIABDAGkAcwBjAG8AIABTAHkAcwB0AGUAbQBzACwAIABJAG4AYwAuAA0A
CgBFAHgAcABpAHIAZQBzADoAIABEAGUAYwBlAG0AYgBlAHIAIAAyADMALAAgADIAMAAwADcAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAASgB1AG4AZQAgADIAMQAsACAAMgAwADAANwANAAoADQAKAA0ACgAgACAAIAAgACAAIAAg
AEQAYQB0AGEAIABGAG8AcgB3AGEAcgBkAGkAbgBnACAAYQBuAGQAIABOAEQAIABSAGUAcwBvAGwA
dQB0AGkAbwBuACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACAAUABpAHQAZgBhAGwAbABz
AA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAZAByAGEAZgB0AC0AdwBiAGUAZQBiAGUA
ZQAtAG4AZAAtAGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAtAHAAaQB0AGYAYQBsAGwAcwAt
ADAAMAANAAoADQAKAFMAdABhAHQAdQBzACAAbwBmACAAdABoAGkAcwAgAE0AZQBtAG8ADQAKAA0A
CgAgACAAIABCAHkAIABzAHUAYgBtAGkAdAB0AGkAbgBnACAAdABoAGkAcwAgAEkAbgB0AGUAcgBu
AGUAdAAtAEQAcgBhAGYAdAAsACAAZQBhAGMAaAAgAGEAdQB0AGgAbwByACAAcgBlAHAAcgBlAHMA
ZQBuAHQAcwAgAHQAaABhAHQAIABhAG4AeQANAAoAIAAgACAAYQBwAHAAbABpAGMAYQBiAGwAZQAg
AHAAYQB0AGUAbgB0ACAAbwByACAAbwB0AGgAZQByACAASQBQAFIAIABjAGwAYQBpAG0AcwAgAG8A
ZgAgAHcAaABpAGMAaAAgAGgAZQAgAG8AcgAgAHMAaABlACAAaQBzACAAYQB3AGEAcgBlAA0ACgAg
ACAAIABoAGEAdgBlACAAYgBlAGUAbgAgAG8AcgAgAHcAaQBsAGwAIABiAGUAIABkAGkAcwBjAGwA
bwBzAGUAZAAsACAAYQBuAGQAIABhAG4AeQAgAG8AZgAgAHcAaABpAGMAaAAgAGgAZQAgAG8AcgAg
AHMAaABlACAAYgBlAGMAbwBtAGUAcwANAAoAIAAgACAAYQB3AGEAcgBlACAAdwBpAGwAbAAgAGIA
ZQAgAGQAaQBzAGMAbABvAHMAZQBkACwAIABpAG4AIABhAGMAYwBvAHIAZABhAG4AYwBlACAAdwBp
AHQAaAAgAFMAZQBjAHQAaQBvAG4AIAA2ACAAbwBmACAAQgBDAFAAIAA3ADkALgANAAoADQAKACAA
IAAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzACAAYQByAGUAIAB3AG8AcgBrAGkAbgBn
ACAAZABvAGMAdQBtAGUAbgB0AHMAIABvAGYAIAB0AGgAZQAgAEkAbgB0AGUAcgBuAGUAdAAgAEUA
bgBnAGkAbgBlAGUAcgBpAG4AZwANAAoAIAAgACAAVABhAHMAawAgAEYAbwByAGMAZQAgACgASQBF
AFQARgApACwAIABpAHQAcwAgAGEAcgBlAGEAcwAsACAAYQBuAGQAIABpAHQAcwAgAHcAbwByAGsA
aQBuAGcAIABnAHIAbwB1AHAAcwAuACAAIABOAG8AdABlACAAdABoAGEAdAANAAoAIAAgACAAbwB0
AGgAZQByACAAZwByAG8AdQBwAHMAIABtAGEAeQAgAGEAbABzAG8AIABkAGkAcwB0AHIAaQBiAHUA
dABlACAAdwBvAHIAawBpAG4AZwAgAGQAbwBjAHUAbQBlAG4AdABzACAAYQBzACAASQBuAHQAZQBy
AG4AZQB0AC0ADQAKACAAIAAgAEQAcgBhAGYAdABzAC4ADQAKAA0ACgAgACAAIABJAG4AdABlAHIA
bgBlAHQALQBEAHIAYQBmAHQAcwAgAGEAcgBlACAAZAByAGEAZgB0ACAAZABvAGMAdQBtAGUAbgB0
AHMAIAB2AGEAbABpAGQAIABmAG8AcgAgAGEAIABtAGEAeABpAG0AdQBtACAAbwBmACAAcwBpAHgA
IABtAG8AbgB0AGgAcwANAAoAIAAgACAAYQBuAGQAIABtAGEAeQAgAGIAZQAgAHUAcABkAGEAdABl
AGQALAAgAHIAZQBwAGwAYQBjAGUAZAAsACAAbwByACAAbwBiAHMAbwBsAGUAdABlAGQAIABiAHkA
IABvAHQAaABlAHIAIABkAG8AYwB1AG0AZQBuAHQAcwAgAGEAdAAgAGEAbgB5AA0ACgAgACAAIAB0
AGkAbQBlAC4AIAAgAEkAdAAgAGkAcwAgAGkAbgBhAHAAcAByAG8AcAByAGkAYQB0AGUAIAB0AG8A
IAB1AHMAZQAgAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdABzACAAYQBzACAAcgBlAGYAZQBy
AGUAbgBjAGUADQAKACAAIAAgAG0AYQB0AGUAcgBpAGEAbAAgAG8AcgAgAHQAbwAgAGMAaQB0AGUA
IAB0AGgAZQBtACAAbwB0AGgAZQByACAAdABoAGEAbgAgAGEAcwAgACIAdwBvAHIAawAgAGkAbgAg
AHAAcgBvAGcAcgBlAHMAcwAuACIADQAKAA0ACgAgACAAIABUAGgAZQAgAGwAaQBzAHQAIABvAGYA
IABjAHUAcgByAGUAbgB0ACAASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0AHMAIABjAGEAbgAg
AGIAZQAgAGEAYwBjAGUAcwBzAGUAZAAgAGEAdAANAAoAIAAgACAAaAB0AHQAcAA6AC8ALwB3AHcA
dwAuAGkAZQB0AGYALgBvAHIAZwAvAGkAZQB0AGYALwAxAGkAZAAtAGEAYgBzAHQAcgBhAGMAdABz
AC4AdAB4AHQALgANAAoADQAKACAAIAAgAFQAaABlACAAbABpAHMAdAAgAG8AZgAgAEkAbgB0AGUA
cgBuAGUAdAAtAEQAcgBhAGYAdAAgAFMAaABhAGQAbwB3ACAARABpAHIAZQBjAHQAbwByAGkAZQBz
ACAAYwBhAG4AIABiAGUAIABhAGMAYwBlAHMAcwBlAGQAIABhAHQADQAKACAAIAAgAGgAdAB0AHAA
OgAvAC8AdwB3AHcALgBpAGUAdABmAC4AbwByAGcALwBzAGgAYQBkAG8AdwAuAGgAdABtAGwALgAN
AAoADQAKACAAIAAgAFQAaABpAHMAIABJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAB3AGkA
bABsACAAZQB4AHAAaQByAGUAIABvAG4AIABEAGUAYwBlAG0AYgBlAHIAIAAyADMALAAgADIAMAAw
ADcALgANAAoADQAKAEMAbwBwAHkAcgBpAGcAaAB0ACAATgBvAHQAaQBjAGUADQAKAA0ACgAgACAA
IABDAG8AcAB5AHIAaQBnAGgAdAAgACgAQwApACAAVABoAGUAIABJAEUAVABGACAAVAByAHUAcwB0
ACAAKAAyADAAMAA3ACkALgANAAoADQAKAEEAYgBzAHQAcgBhAGMAdAANAAoADQAKACAAIAAgAFIA
RgBDACAAMgA0ADYAMQAgAFsATgBEAF0AIABkAGUAcwBjAHIAaQBiAGUAcwAgAGgAbwBzAHQAIABk
AGEAdABhACAAZgBvAHIAdwBhAHIAZABpAG4AZwAgAGEAbgBkACAAYQBkAGQAcgBlAHMAcwAgAHIA
ZQBzAG8AbAB1AHQAaQBvAG4ALgANAAoAIAAgACAASABvAHcAZQB2AGUAcgAsACAAbgBpAG4AZQAg
AHkAZQBhAHIAcwAgAGEAZgB0AGUAcgAgAHQAaABlACAATgBEACAAcAByAG8AdABvAGMAbwBsACAA
YgBlAGMAYQBtAGUAIABhAG4AIABSAEYAQwAsACAASQBQAHYANgAgAGgAbwBzAHQAcwANAAoAIAAg
ACAAcwB0AGkAbABsACAAZABvACAAbgBvAHQAIABmAHUAbABsAHkAIABjAG8AbQBwAGwAeQAgAHcA
aQB0AGgAIABSAEYAQwAgADIANAA2ADEAIABbAE4ARABdAC4AIAAgAEkAbgAgAHAAYQByAHQAaQBj
AHUAbABhAHIALAAgAGgAbwBzAHQAcwANAAoAIAAgACAAaQBuAGMAbwByAHIAZQBjAHQAbAB5ACAA
aQBtAHAAbABlAG0AZQBuAHQAIABvAG4ALQAgAHYAcwAuACAAbwBmAGYALQBsAGkAbgBrACAAZABh
AHQAYQAgAGYAbwByAHcAYQByAGQAaQBuAGcALgAgACAAVABoAGkAcwANAAoAIAAgACAAZABvAGMA
dQBtAGUAbgB0ACAAYwBsAGEAcgBpAGYAaQBlAHMAIABoAG8AcwB0ACAAYgBlAGgAYQB2AGkAbwBy
ACAAYQBuAGQAIABhAHMAcwBvAGMAaQBhAHQAZQBkACAAcgBvAHUAdABlAHIAIABiAGUAaABhAHYA
aQBvAHIAIAB0AG8ADQAKACAAIAAgAGQAZQBmAGkAbgBlACAAZQB4AHAAbABpAGMAaQB0AGwAeQAg
AGEAZABkAHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAAYQBuAGQAIABkAGEAdABhACAA
ZgBvAHIAdwBhAHIAZABpAG4AZwAgAG0AbwBkAGUAbABzAC4AIAAgAFQAaABlAA0ACgAgACAAIABz
AGUAdAAgAG8AZgAgAG4AZQB3ACAAcgBlAHEAdQBpAHIAZQBtAGUAbgB0AHMAIABiAGUAeQBvAG4A
ZAAgAHcAaABhAHQAIABoAGEAcwAgAGIAZQBlAG4AIABzAHAAZQBjAGkAZgBpAGUAZAAgAGkAbgAg
AFIARgBDACAAMgA0ADYAMQANAAoAIAAgACAAWwBOAEQAXQAgAGEAbgBkACAAUgBGAEMAIAAyADQA
NgAyACAAWwBBAEQARABSAEMATwBOAEYAXQAgAGkAcwAgAHIAZQBzAHQAcgBpAGMAdABlAGQAIAB0
AG8AIABjAG8AcgByAGUAYwB0AGkAbwBuAHMAIABhAG4AZAANAAoADQAKAA0ACgANAAoAUwBpAG4A
ZwBoACAAJgAgAEIAZQBlAGIAZQBlACAAIAAgACAAIAAgACAAIAAgACAARQB4AHAAaQByAGUAcwAg
AEQAZQBjAGUAbQBiAGUAcgAgADIAMwAsACAAMgAwADAANwAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIABbAFAAYQBnAGUAIAAxAF0ADQAKAAwADQAKAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBh
AGYAdAAgACAAIAAgACAAIAAgACAAIABOAEQAIABJAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4A
IABQAGkAdABmAGEAbABsAHMAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEoAdQBuAGUAIAAy
ADAAMAA3AA0ACgANAAoADQAKACAAIAAgAGMAbABhAHIAaQBmAGkAYwBhAHQAaQBvAG4AcwAgAGQA
ZQBlAG0AZQBkACAAbgBlAGMAZQBzAHMAYQByAHkAIAB0AG8AIABmAGEAYwBpAGwAaQB0AGEAdABl
ACAAYwBvAHIAcgBlAGMAdAAgAGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAuAA0ACgANAAoA
DQAKAFQAYQBiAGwAZQAgAG8AZgAgAEMAbwBuAHQAZQBuAHQAcwANAAoADQAKACAAIAAgADEALgAg
ACAASQBuAHQAcgBvAGQAdQBjAHQAaQBvAG4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAA
LgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAu
ACAALgAgAC4AIAAuACAAIAAzAA0ACgAgACAAIAAyAC4AIAAgAEgAbwBzAHQAIABNAG8AZABlAGwA
cwAgACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgACAAMwANAAoA
IAAgACAAIAAgADIALgAxAC4AIAAgAFIAQQAgAFMAZQB0AHMAIABNACAAYQBuAGQAIABPACAAQgBp
AHQAcwAgAGIAdQB0ACAAZABvAGUAcwAgAG4AbwB0ACAASQBuAGMAbAB1AGQAZQAgAHQAaABlACAA
UAByAGUAZgBpAHgADQAKACAAIAAgACAAIAAgACAAIAAgACAAIABJAG4AZgBvAHIAbQBhAHQAaQBv
AG4AIABPAHAAdABpAG8AbgAgACgAUABJAE8AKQAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4A
IAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAAIAA1AA0ACgAgACAAIAAg
ACAAMgAuADIALgAgACAAUgBBACAAQQBkAHYAZQByAHQAaQBzAGUAcwAgAGEAIABQAHIAZQBmAGkA
eAAgAHcAaQB0AGgAIAB0AGgAZQAgAE8AbgAtAGwAaQBuAGsAKABMACkAIABCAGkAdAAgAFMAZQB0
ACAALgAgAC4AIAAuACAALgAgACAANQANAAoAIAAgACAAIAAgADIALgAzAC4AIAAgAFIAQQAgAEEA
ZAB2AGUAcgB0AGkAcwBlAHMAIABhACAAUAByAGUAZgBpAHgAIAB3AGkAdABoACAAdABoAGUAIABP
AG4ALQBsAGkAbgBrACgATAApACAAQgBpAHQAIABDAGwAZQBhAHIAIAAuACAALgAgAC4AIAAgADcA
DQAKACAAIAAgADMALgAgACAAUgBvAHUAdABlAHIAIABNAG8AZABlAGwAcwAgACAALgAgAC4AIAAu
ACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4A
IAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAAIAA3AA0ACgAgACAAIAAgACAAMwAuADEALgAg
ACAAQQBnAGcAcgBlAGcAYQB0AGkAbwBuACAAUgBvAHUAdABlAHIAIABEAGUAcABsAG8AeQBtAGUA
bgB0ACAATQBvAGQAZQBsACAAIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAu
ACAALgAgACAANwANAAoAIAAgACAANAAuACAAIABSAGUAZABpAHIAZQBjAHQAIABDAGwAYQByAGkA
ZgBpAGMAYQB0AGkAbwBuAHMAIAAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAgADgADQAKACAAIAAgADUA
LgAgACAAQwBoAGEAbgBnAGUAcwAgAHQAbwAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2
AC0AcgBmAGMAMgA0ADYAMgBiAGkAcwAtADAAOAAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4A
IAAuACAALgAgAC4AIAAuACAAIAA4AA0ACgAgACAAIAA2AC4AIAAgAFMAZQBjAHUAcgBpAHQAeQAg
AEMAbwBuAHMAaQBkAGUAcgBhAHQAaQBvAG4AcwAgACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAA
LgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgACAAOQAN
AAoAIAAgACAANwAuACAAIABJAEEATgBBACAAQwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBzACAA
IAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAgADkADQAKACAAIAAgADgALgAgACAAQQBjAGsA
bgBvAHcAbABlAGQAZwBlAG0AZQBuAHQAcwAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAu
ACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4A
IAAuACAAIAA5AA0ACgAgACAAIAA5AC4AIAAgAFIAZQBmAGUAcgBlAG4AYwBlAHMAIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAA
LgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgADEAMAANAAoAIAAgACAAIAAg
ADkALgAxAC4AIAAgAE4AbwByAG0AYQB0AGkAdgBlACAAUgBlAGYAZQByAGUAbgBjAGUAcwAgAC4A
IAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAxADAADQAKACAAIAAgACAAIAA5AC4AMgAuACAAIABJAG4AZgBvAHIA
bQBhAHQAaQB2AGUAIABSAGUAZgBlAHIAZQBuAGMAZQBzACAALgAgAC4AIAAuACAALgAgAC4AIAAu
ACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAAMQAwAA0A
CgAgACAAIABBAHUAdABoAG8AcgBzACcAIABBAGQAZAByAGUAcwBzAGUAcwAgAC4AIAAuACAALgAg
AC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAA
LgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgADEAMAANAAoAIAAgACAASQBuAHQAZQBsAGwAZQBj
AHQAdQBhAGwAIABQAHIAbwBwAGUAcgB0AHkAIABhAG4AZAAgAEMAbwBwAHkAcgBpAGcAaAB0ACAA
UwB0AGEAdABlAG0AZQBuAHQAcwAgAC4AIAAuACAALgAgAC4AIAAuACAALgAgAC4AIAAuACAALgAg
AC4AIAAxADIADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoA
DQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgAN
AAoADQAKAA0ACgBTAGkAbgBnAGgAIAAmACAAQgBlAGUAYgBlAGUAIAAgACAAIAAgACAAIAAgACAA
IABFAHgAcABpAHIAZQBzACAARABlAGMAZQBtAGIAZQByACAAMgAzACwAIAAyADAAMAA3ACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFsAUABhAGcAZQAgADIAXQANAAoADAANAAoASQBuAHQA
ZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAIAAgACAAIAAgACAAIAAgAE4ARAAgAEkAbQBwAGwAZQBt
AGUAbgB0AGEAdABpAG8AbgAgAFAAaQB0AGYAYQBsAGwAcwAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAASgB1AG4AZQAgADIAMAAwADcADQAKAA0ACgANAAoAMQAuACAAIABJAG4AdAByAG8AZAB1
AGMAdABpAG8AbgANAAoADQAKACAAIAAgAEkAUAB2ADYAIABoAG8AcwB0ACAAZABhAHQAYQAgAGYA
bwByAHcAYQByAGQAaQBuAGcAIABhAG4AZAAgAGEAZABkAHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0
AGkAbwBuACAAaQBzACAAYwBvAG0AcABsAGUAeAAuACAAIABGAG8AcgANAAoAIAAgACAAZQB4AGEA
bQBwAGwAZQAsACAAUgBGAEMAIAAyADQANgAxACAAWwBOAEQAXQAgACgAcwBlAGMAdABpAG8AbgAg
ADMALgAxACkAIABzAHQAYQB0AGUAcwAgAHQAaABhAHQAIABpAGYAIAB0AGgAZQAgAFIAQQAgAHIA
ZQBjAGUAaQB2AGUAZAANAAoAIAAgACAAYgB5ACAAdABoAGUAIABoAG8AcwB0ACAAZABvAGUAcwAg
AG4AbwB0ACAAYQBkAHYAZQByAHQAaQBzAGUAIABhAG4AeQAgAHAAcgBlAGYAaQB4ACwAIAB0AGgA
ZQBuACAAdABoAGUAIABoAG8AcwB0ACAAbQB1AHMAdAAgAHMAZQBuAGQADQAKACAAIAAgAGEAbABs
ACAAZABhAHQAYQAgAHQAbwAgAHQAaABlACAAcgBvAHUAdABlAHIALgAgACAAVABoAGkAcwAgAHMA
ZQBjAHQAaQBvAG4AIABvAGYAIAB0AGgAZQAgAFIARgBDACAAaQBtAHAAbABpAGUAcwAgAHQAaABh
AHQAIABuAG8ADQAKACAAIAAgAGEAZABkAHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAA
aQBzACAAdABvACAAYgBlACAAcABlAHIAZgBvAHIAbQBlAGQAIABpAG4AIAB0AGgAaQBzACAAYwBh
AHMAZQAuACAAIABTAGUAYwB0AGkAbwBuAHMAIAA1AC4AMgAgAGEAbgBkAA0ACgAgACAAIAA3AC4A
MgAuADIAIABpAG0AcABsAHkAIAB0AGgAYQB0ACAAdABoAGUAIABoAG8AcwB0ACAAcABlAHIAZgBv
AHIAbQBzACAAYQBkAGQAcgBlAHMAcwAgAHIAZQBzAG8AbAB1AHQAaQBvAG4AIABiAGUAZgBvAHIA
ZQANAAoAIAAgACAAdAByAGEAbgBzAG0AaQB0AHQAaQBuAGcAIABhACAAcABhAGMAawBlAHQAIABp
AGYAIAB0AGgAZQAgAGQAZQBzAHQAaQBuAGEAdABpAG8AbgAgAG8AZgAgAHQAaABlACAAcABhAGMA
awBlAHQAIABpAHMAIABvAG4AIAB0AGgAZQAgAHMAYQBtAGUADQAKACAAIAAgAGwAaQBuAGsAIABh
AHMAIAB0AGgAZQAgAGgAbwBzAHQALgAgACAAUwBvAG0AZQAgAGMAdQByAHIAZQBuAHQAIABoAG8A
cwB0ACAAaQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuAHMAIABwAGUAcgBmAG8AcgBtACAAYQBk
AGQAcgBlAHMAcwANAAoAIAAgACAAcgBlAHMAbwBsAHUAdABpAG8AbgAgAGkAbgAgAGEAbABsACAA
YwBhAHMAZQBzACAAZQB2AGUAbgAgAHcAaABlAG4AIAB0AGgAZQAgAGQAZQBzAHQAaQBuAGEAdABp
AG8AbgAgAGkAcwAgAG4AbwB0ACAAYwBsAGUAYQByAGwAeQAgAG8AbgAtAA0ACgAgACAAIABsAGkA
bgBrAC4AIAAgAEgAbwB3AGUAdgBlAHIALAAgAFIARgBDACAAMgA0ADYAMQAgAFsATgBEAF0AIABz
AGUAYwB0AGkAbwBuACAANgAuADMALgA0ACAAaQBtAHAAbABpAGUAcwAgAHQAaABhAHQAIABoAG8A
cwB0AHMAIABtAHUAcwB0AA0ACgAgACAAIABjAGwAZQBhAHIAbAB5ACAAZABlAHQAZQByAG0AaQBu
AGUAIAB0AGgAYQB0ACAAYQAgAGQAZQBzAHQAaQBuAGEAdABpAG8AbgAgAGkAcwAgAG8AbgAtAGwA
aQBuAGsAIABiAGUAZgBvAHIAZQAgAHAAZQByAGYAbwByAG0AaQBuAGcADQAKACAAIAAgAGEAZABk
AHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuAC4ADQAKAA0ACgAgACAAIABUAGgAZQBzAGUA
IABpAG0AcABsAGkAYwBhAHQAaQBvAG4AcwAgAGkAbgAgAFIARgBDACAAMgA0ADYAMQAgAFsATgBE
AF0AIABuAGUAZQBkACAAdABvACAAYgBlACAAbQBhAGQAZQAgAGUAeABwAGwAaQBjAGkAdAAuAA0A
CgAgACAAIABGAGEAaQBsAHUAcgBlACAAbwBmACAAaABvAHMAdAAgAGkAbQBwAGwAZQBtAGUAbgB0
AGEAdABpAG8AbgBzACAAdABvACAAYwBvAG0AcABsAHkAIABjAGEAbgAgAHIAZQBzAHUAbAB0ACAA
aQBuACAAbABhAGMAawAgAG8AZgAgAEkAUAB2ADYADQAKACAAIAAgAGMAbwBuAG4AZQBjAHQAaQB2
AGkAdAB5AC4AIAAgAEYAbwByACAAZQB4AGEAbQBwAGwAZQAsACAAYQAgAGgAbwBzAHQAIAByAGUA
YwBlAGkAdgBlAHMAIABhAG4AIABSAEEAIAB3AGkAdABoACAAbgBvACAAcAByAGUAZgBpAHgADQAK
ACAAIAAgAGEAZAB2AGUAcgB0AGkAcwBlAGQAIABhAG4AZAAgAGkAbgBjAG8AcgByAGUAYwB0AGwA
eQAgAGQAZQBjAGkAZABlAHMAIAB0AG8AIABwAGUAcgBmAG8AcgBtACAAYQBkAGQAcgBlAHMAcwAg
AHIAZQBzAG8AbAB1AHQAaQBvAG4AIAB3AGgAZQBuAA0ACgAgACAAIAB0AGgAZQAgAGgAbwBzAHQA
IABzAGgAbwB1AGwAZAAgAGgAYQB2AGUAIABzAGUAbgB0ACAAYQBsAGwAIAB0AHIAYQBmAGYAaQBj
ACAAdABvACAAdABoAGUAIABkAGUAZgBhAHUAbAB0ACAAcgBvAHUAdABlAHIALgAgACAAVABoAGUA
DQAKACAAIAAgAHIAbwB1AHQAZQByACAAbQBhAHkAIABuAG8AdAAgAHIAZQBzAHAAbwBuAGQAIAB0
AG8AIAB0AGgAZQAgAGEAZABkAHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAAYQBuAGQA
IAB0AGgAZQAgAGwAYQB5AGUAcgAgADIADQAKACAAIAAgAGQAcgBpAHYAZQByACAAbwBmACAAdABo
AGUAIABoAG8AcwB0ACAAcwB0AG8AcABzACAAdAByAGEAbgBzAG0AaQB0AHQAaQBuAGcAIABJAFAA
dgA2ACAAcABhAGMAawBlAHQAcwAuAA0ACgANAAoAIAAgACAASABvAHMAdAAgAGEAZABkAHIAZQBz
AHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAAaABhAHMAIABpAG0AcABsAGkAYwBhAHQAaQBvAG4A
cwAgAGYAbwByACAAcgBvAHUAdABlAHIAIABkAGUAcwBpAGcAbgAgAGEAbgBkAA0ACgAgACAAIABk
AGUAcABsAG8AeQBtAGUAbgB0AC4AIAAgAEYAaQByAHMAdAAsACAAaABvAHMAdAAgAGIAZQBoAGEA
dgBpAG8AcgAgAGkAcwAgAGMAbABhAHIAaQBmAGkAZQBkACAAaQBuACAAdABoAGUAIABIAG8AcwB0
ACAATQBvAGQAZQBsAHMADQAKACAAIAAgAHMAZQBjAHQAaQBvAG4ALgAgACAAUwBlAGMAbwBuAGQA
LAAgAGEAIAByAG8AdQB0AGUAcgAgAGQAZQBwAGwAbwB5AG0AZQBuAHQAIABtAG8AZABlAGwAIABp
AHMAIABkAGUAcwBjAHIAaQBiAGUAZAAgAGkAbgAgAHQAaABlAA0ACgAgACAAIABSAG8AdQB0AGUA
cgAgAE0AbwBkAGUAbABzACAAcwBlAGMAdABpAG8AbgAuACAAIABUAGgAaQByAGQALAAgAFIAZQBk
AGkAcgBlAGMAdABzACAAYQByAGUAIABjAGwAYQByAGkAZgBpAGUAZAAgAGYAbwByACAAYgBvAHQA
aAANAAoAIAAgACAAcgBvAHUAdABlAHIAcwAgAGEAbgBkACAAaABvAHMAdABzACAAaQBuACAAdABo
AGUAIABSAGUAZABpAHIAZQBjAHQAIABDAGwAYQByAGkAZgBpAGMAYQB0AGkAbwBuAHMAIABzAGUA
YwB0AGkAbwBuAC4AIAAgAEYAaQBuAGEAbABsAHkALAANAAoAIAAgACAAcAByAG8AcABvAHMAZQBk
ACAAYwBoAGEAbgBnAGUAcwAgAHQAbwAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2AC0A
cgBmAGMAMgA0ADYAMgBiAGkAcwAtADAAOAAgAFsAQQBEAEQAUgBDAE8ATgBGAGIAaQBzAF0AIABh
AHIAZQANAAoAIAAgACAAcAByAGUAcwBlAG4AdABlAGQALgANAAoADQAKACAAIAAgAFcAaABlAHIA
ZQAgAGIAZQBoAGEAdgBpAG8AcgAgAGgAYQBzACAAbgBvAHQAIABjAGgAYQBuAGcAZQBkACAAYgBl
AHQAdwBlAGUAbgAgAFIARgBDACAAMgA0ADYAMQAgAFsATgBEAF0AIABhAG4AZAANAAoAIAAgACAA
ZAByAGEAZgB0AC0AaQBlAHQAZgAtAGkAcAB2ADYALQAyADQANgAxAGIAaQBzAC0AMQAxACAAWwBO
AEQAYgBpAHMAXQAgAGEAbgBkACAAYgBlAGgAYQB2AGkAbwByACAAaABhAHMAIABuAG8AdAAgAGMA
aABhAG4AZwBlAGQADQAKACAAIAAgAGIAZQB0AHcAZQBlAG4AIABSAEYAQwAgADIANAA2ADIAIABb
AEEARABEAFIAQwBPAE4ARgBdACAAYQBuAGQAIABkAHIAYQBmAHQALQBpAGUAdABmAC0AaQBwAHYA
NgAtAHIAZgBjADIANAA2ADIAYgBpAHMALQAwADgADQAKACAAIAAgAFsAQQBEAEQAUgBDAE8ATgBG
AGIAaQBzAF0ALAAgAHQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQAIABvAG4AbAB5ACAAcgBlAGYA
ZQByAHMAIAB0AG8AIABSAEYAQwAgADIANAA2ADEAIABbAE4ARABdACAAYQBuAGQAIABSAEYAQwAN
AAoAIAAgACAAMgA0ADYAMgAgAFsAQQBEAEQAUgBDAE8ATgBGAF0AIAByAGUAcwBwAGUAYwB0AGkA
dgBlAGwAeQAuACAAIABXAGgAZQByAGUAIABiAGUAaABhAHYAaQBvAHIAIABoAGEAcwAgAGMAaABh
AG4AZwBlAGQALAAgAHQAaABpAHMADQAKACAAIAAgAGQAbwBjAHUAbQBlAG4AdAAgAHIAZQBmAGUA
cgBzACAAdABvACAAYgBvAHQAaAAgAHQAaABlACAAbwByAGkAZwBpAG4AYQBsACAAYQBuAGQAIAB0
AGgAZQAgAG4AZQB3ACAAdgBlAHIAcwBpAG8AbgAuAA0ACgANAAoADQAKADIALgAgACAASABvAHMA
dAAgAE0AbwBkAGUAbABzAA0ACgANAAoAIAAgACAAQQAgAGMAbwByAHIAZQBjAHQAbAB5ACAAaQBt
AHAAbABlAG0AZQBuAHQAZQBkACAASQBQAHYANgAgAGgAbwBzAHQAIABNAFUAUwBUACAAYQBkAGgA
ZQByAGUAIAB0AG8AIAB0AGgAZQAgAGYAbwBsAGwAbwB3AGkAbgBnACAAcgB1AGwAZQBzADoADQAK
AA0ACgAgACAAIAAxAC4AIAAgAE8AbgAtAGwAaQBuAGsAIABkAGUAdABlAHIAbQBpAG4AYQB0AGkA
bwBuACAAYQBuAGQAIABhAGQAZAByAGUAcwBzACAAaQBuAGYAbwByAG0AYQB0AGkAbwBuACAATQBV
AFMAVAAgAE4ATwBUACAAcABlAHIAcwBpAHMAdAANAAoAIAAgACAAIAAgACAAIABhAGMAcgBvAHMA
cwAgAEkAUAB2ADYAIABpAG4AdABlAHIAZgBhAGMAZQAgAGkAbgBpAHQAaQBhAGwAaQB6AGEAdABp
AG8AbgBzAC4ADQAKAA0ACgAgACAAIAAyAC4AIAAgAFQAaABlACAAUgBBACAAYQBuAGQAIABSAGUA
ZABpAHIAZQBjAHQAcwAgAGYAcgBvAG0AIAB0AGgAZQAgAGQAZQBmAGEAdQBsAHQAIAByAG8AdQB0
AGUAcgAgAGEAcgBlACAAdABoAGUAIABvAG4AbAB5ACAAcwBvAHUAcgBjAGUAcwANAAoAIAAgACAA
IAAgACAAIABvAGYAIABpAG4AZgBvAHIAbQBhAHQAaQBvAG4AIABmAG8AcgAgAG8AbgAtAGwAaQBu
AGsAIABkAGUAdABlAHIAbQBpAG4AYQB0AGkAbwBuAC4AIAAgAEQASABDAFAAdgA2ACAAbwByACAA
YQBuAHkAIABvAHQAaABlAHIADQAKAA0ACgANAAoADQAKAFMAaQBuAGcAaAAgACYAIABCAGUAZQBi
AGUAZQAgACAAIAAgACAAIAAgACAAIAAgAEUAeABwAGkAcgBlAHMAIABEAGUAYwBlAG0AYgBlAHIA
IAAyADMALAAgADIAMAAwADcAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEAZwBl
ACAAMwBdAA0ACgAMAA0ACgBJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAAgACAAIAAgACAA
IAAgACAATgBEACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACAAUABpAHQAZgBhAGwAbABz
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABKAHUAbgBlACAAMgAwADAANwANAAoADQAKAA0A
CgAgACAAIAAgACAAIAAgAGMAbwBuAGYAaQBnAHUAcgBhAHQAaQBvAG4AIABvAG4AIAB0AGgAZQAg
AGgAbwBzAHQAIABNAFUAUwBUACAATgBPAFQAIABiAGUAIAB1AHMAZQBkACAAZgBvAHIAIABvAG4A
LQBsAGkAbgBrAA0ACgAgACAAIAAgACAAIAAgAGQAZQB0AGUAcgBtAGkAbgBhAHQAaQBvAG4ALgAg
ACAATQBhAG4AdQBhAGwAIABjAG8AbgBmAGkAZwB1AHIAYQB0AGkAbwBuACAAbwBmACAAYQAgAGgA
bwBzAHQAIABpAG4AdAByAG8AZAB1AGMAZQBzACAAaQB0AHMAIABvAHcAbgANAAoAIAAgACAAIAAg
ACAAIABzAGUAdAAgAG8AZgAgAHMAZQBjAHUAcgBpAHQAeQAgAGMAbwBuAHMAaQBkAGUAcgBhAHQA
aQBvAG4AcwAgAGEAbgBkACAAaQBzACAAYgBlAHkAbwBuAGQAIAB0AGgAZQAgAHMAYwBvAHAAZQAg
AG8AZgAgAHQAaABpAHMADQAKACAAIAAgACAAIAAgACAAZABvAGMAdQBtAGUAbgB0AC4ADQAKAA0A
CgAgACAAIAAzAC4AIAAgAFQAaABlACAAaABvAHMAdAAgAE0AVQBTAFQAIABOAE8AVAAgAGEAZABk
ACAAYQAgAGQAaQByAGUAYwB0ACAAZABlAGwAaQB2AGUAcgB5ACAAcgBvAHUAdABlACAAdABvACAA
dABoAGUAIABwAHIAZQBmAGkAeAAgAGYAcgBvAG0ADQAKACAAIAAgACAAIAAgACAAYQBuACAAYQBz
AHMAaQBnAG4AZQBkACAAYQBkAGQAcgBlAHMAcwAsACAAaQBuAGQAZQBwAGUAbgBkAGUAbgB0ACAA
bwBmACAAdABoAGUAIABpAG4AZgBvAHIAbQBhAHQAaQBvAG4AIABhAGIAbwB1AHQAIAB0AGgAZQAN
AAoAIAAgACAAIAAgACAAIABwAHIAZQBmAGkAeAAgAHIAZQBjAGUAaQB2AGUAZAAgAGYAcgBvAG0A
IAB0AGgAZQAgAFIAQQAgAG8AcgAgAFIAZQBkAGkAcgBlAGMAdABzAC4ADQAKAA0ACgAgACAAIAA0
AC4AIAAgAFQAaABlACAAaABvAHMAdAAgAE0AVQBTAFQAIABpAHMAcwB1AGUAIABOAFMAKABEAEEA
RAApAHMAIABmAG8AcgAgAGEAbABsACAAbwBmACAAaQB0AHMAIABhAGMAcQB1AGkAcgBlAGQAIAB1
AG4AaQBjAGEAcwB0AA0ACgAgACAAIAAgACAAIAAgAGEAZABkAHIAZQBzAHMAZQBzACAAZQB4AGMA
ZQBwAHQAIAB3AGgAZQBuACAAdABoAGUAIABoAG8AcwB0ACAAaQBuAHQAZQByAGYAYQBjAGUAIABo
AGEAcwANAAoAIAAgACAAIAAgACAAIABEAHUAcABBAGQAZAByAEQAZQB0AGUAYwB0AFQAcgBhAG4A
cwBtAGkAdABzACAAdgBhAHIAaQBhAGIAbABlACAAcwBlAHQAIAB0AG8AIAB6AGUAcgBvAC4AIAAg
AFMAZQBjAHQAaQBvAG4AIAA1AC4ANAAgAG8AZgAgAFIARgBDAA0ACgAgACAAIAAgACAAIAAgADIA
NAA2ADIAIABbAEEARABEAFIAQwBPAE4ARgBdACAAZQByAHIAbwBuAGUAbwB1AHMAbAB5ACAAcgBl
AGwAYQB4AGUAcwAgAHQAaABpAHMAIAByAGUAcQB1AGkAcgBlAG0AZQBuAHQAIABhAG4AZAAgAHMA
dQBmAGYAZQByAHMADQAKACAAIAAgACAAIAAgACAAZgByAG8AbQAgAGEAIABzAGUAYwB1AHIAaQB0
AHkAIABwAHIAbwBiAGwAZQBtACAAYQBzACAAaQBsAGwAdQBzAHQAcgBhAHQAZQBkACAAYgB5ACAA
dABoAGUAIABmAG8AbABsAG8AdwBpAG4AZwAgAGUAeABhAG0AcABsAGUAOgANAAoADQAKACAAIAAg
ACAAIAAgACAAIAAgACAASABvAHMAdAAxACAAdQBzAGUAcwAgAEUAVQBJAC0ANgA0ACAAdABvACAA
YwBvAG4AZgBpAGcAdQByAGUAIABhACAATABpAG4AawAgAEwAbwBjAGEAbAAgAEEAZABkAHIAZQBz
AHMAIAAoAEwATABBACkADQAKACAAIAAgACAAIAAgACAAIAAgACAAdQBzAGkAbgBnACAATQBBAEMA
MQAgAGEAbgBkACAAbQBhAG4AdQBhAGwAbAB5ACAAYwBvAG4AZgBpAGcAdQByAGUAcwAgAGEAIABH
AGwAbwBiAGEAbAAgAFUAbgBpAGMAYQBzAHQAIABBAGQAZAByAGUAcwBzAA0ACgAgACAAIAAgACAA
IAAgACAAIAAgACgARwBVAEEAKQAgAHQAaABhAHQAIABpAHMAIABlAHEAdQBhAGwAIAB0AG8AIABh
AG4AIABhAGQAZAByAGUAcwBzACAAYwBvAG4AZgBpAGcAdQByAGUAZAAgAHUAcwBpAG4AZwAgAEUA
VQBJAC0ANgA0ACAAYQBuAGQADQAKACAAIAAgACAAIAAgACAAIAAgACAATQBBAEMAMgAuACAAIABI
AG8AcwB0ADEAIABjAG8AbQBwAGwAZQB0AGUAcwAgAGEAbgAgAE4AUwAoAEQAQQBEACkAIABmAG8A
cgAgAGIAbwB0AGgAIABpAHQAcwAgAEwATABBACAAYQBuAGQAIABHAFUAQQAuAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgAFQAaABlAG4ALAAgAEgAbwBzAHQAMgAgAHUAcwBlAHMAIABFAFUASQAtADYA
NAAgAHQAbwAgAGMAbwBuAGYAaQBnAHUAcgBlACAAYgBvAHQAaAAgAGEAIABMAEwAQQAgAGEAbgBk
ACAAYQAgAEcAVQBBAA0ACgAgACAAIAAgACAAIAAgACAAIAAgAHUAcwBpAG4AZwAgAE0AQQBDADIA
LgAgACAASABvAHMAdAAyACAAYwBvAG0AcABsAGUAdABlAHMAIABhAG4AIABOAFMAKABEAEEARAAp
ACAAZgBvAHIAIAB0AGgAZQAgAEwATABBACAAYQBuAGQAIABkAG8AZQBzAA0ACgAgACAAIAAgACAA
IAAgACAAIAAgAG4AbwB0ACAAcwBlAG4AZAAgAGEAbgAgAE4AUwAoAEQAQQBEACkAIABmAG8AcgAg
AGkAdABzACAARwBVAEEAIABpAG4AIABjAG8AbQBwAGwAaQBhAG4AYwBlACAAdwBpAHQAaAAgAFIA
RgBDACAAMgA0ADYAMgANAAoAIAAgACAAIAAgACAAIAAgACAAIABbAEEARABEAFIAQwBPAE4ARgBd
AC4AIAAgAE4AbwB3ACAASABvAHMAdAAxACAAYQBuAGQAIABIAG8AcwB0ADIAIABoAGEAdgBlACAA
dABoAGUAIABzAGEAbQBlACAARwBVAEEAIABvAG4AIAB0AGgAZQAgAHMAYQBtAGUADQAKACAAIAAg
ACAAIAAgACAAIAAgACAAbABpAG4AawAuAA0ACgANAAoAIAAgACAAIAAgACAAIABUAGgAZQByAGUA
ZgBvAHIAZQAsACAAdABoAGkAcwAgAGUAeABjAGUAcAB0AGkAbwBuACAAaQBuACAAcwBlAGMAdABp
AG8AbgAgADUALgA0ACAAbwBmACAAUgBGAEMAIAAyADQANgAyACAAWwBBAEQARABSAEMATwBOAEYA
XQANAAoAIAAgACAAIAAgACAAIABNAFUAUwBUACAAYgBlACAAaQBnAG4AbwByAGUAZAAuACAAIABO
AG8AdABlACAAdABoAGEAdAAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2AC0AcgBmAGMA
MgA0ADYAMgBiAGkAcwAtADAAOAANAAoAIAAgACAAIAAgACAAIABbAEEARABEAFIAQwBPAE4ARgBi
AGkAcwBdACAAcgBlAGYAZQByAHMAIAB0AG8AIABhAG4AIABlAHgAdABlAG4AcwBpAGIAaQBsAGkA
dAB5ACAAYwBvAG4AYwBlAHIAbgAgAHcAaQB0AGgAIABuAGUAdwANAAoAIAAgACAAIAAgACAAIABp
AG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AcwAgAGEAbgBkACAAcwB0AGEAdABlAHMAIABpAG4A
IABzAGUAYwB0AGkAbwBuACAANQAuADQAOgANAAoADQAKACAAIAAgACAAIAAgACAAIAAgACAAIgBX
AGgAZQByAGUAYQBzACAAdABoAGkAcwAgAGQAbwBjAHUAbQBlAG4AdAAgAGQAbwBlAHMAIABuAG8A
dAAgAGkAbgB2AGEAbABpAGQAYQB0AGUAIABzAHUAYwBoAA0ACgAgACAAIAAgACAAIAAgACAAIAAg
AGkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgBzACwAIAB0AGgAaQBzACAAawBpAG4AZAAgAG8A
ZgAgACcAbwBwAHQAaQBtAGkAegBhAHQAaQBvAG4AJwAgAGkAcwAgAE4ATwBUAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgAFIARQBDAE8ATQBNAEUATgBEAEUARAAsACAAYQBuAGQAIABuAGUAdwAgAGkA
bQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgBzACAATQBVAFMAVAAgAE4ATwBUACAAZABvACAAdABo
AGEAdAANAAoAIAAgACAAIAAgACAAIAAgACAAIABvAHAAdABpAG0AaQB6AGEAdABpAG8AbgAuACIA
DQAKAA0ACgAgACAAIAAgACAAIAAgAEgAbwB3AGUAdgBlAHIALAAgAHQAaABlACAAcwBlAGMAdQBy
AGkAdAB5ACAAcAByAG8AYgBsAGUAbQAgAG0AZQBuAHQAaQBvAG4AZQBkACAAaQBuACAAdABoAGkA
cwAgAGQAbwBjAHUAbQBlAG4AdAANAAoAIAAgACAAIAAgACAAIABpAG4AdgBhAGwAaQBkAGEAdABl
AHMAIABlAHYAZQBuACAAYwB1AHIAcgBlAG4AdABsAHkAIABlAHgAaQBzAHQAaQBuAGcAIABpAG0A
cABsAGUAbQBlAG4AdABhAHQAaQBvAG4AcwAuACAAIABUAGgAZQANAAoAIAAgACAAIAAgACAAIAAi
AEMAaABhAG4AZwBlAHMAIAB0AG8AIABkAHIAYQBmAHQALQBpAGUAdABmAC0AaQBwAHYANgAtAHIA
ZgBjADIANAA2ADIAYgBpAHMALQAwADgAIgAgAHMAZQBjAHQAaQBvAG4AIABpAG4AIAB0AGgAaQBz
AA0ACgAgACAAIAAgACAAIAAgAGQAbwBjAHUAbQBlAG4AdAAgAGQAZQBzAGMAcgBpAGIAZQBzACAA
dABoAGUAIABjAG8AcgByAGUAcwBwAG8AbgBkAGkAbgBnACAAYwBoAGEAbgBnAGUAcwAgAHQAbwAN
AAoAIAAgACAAIAAgACAAIABkAHIAYQBmAHQALQBpAGUAdABmAC0AaQBwAHYANgAtAHIAZgBjADIA
NAA2ADIAYgBpAHMALQAwADgAIABbAEEARABEAFIAQwBPAE4ARgBiAGkAcwBdAC4ADQAKAA0ACgAg
ACAAIAA1AC4AIAAgAFQAaABlACAAaABvAHMAdAAgAFMASABPAFUATABEACAAaQBzAHMAdQBlACAA
bwBuAGwAeQAgAGEAIABzAGkAbgBnAGwAZQAgAE4AUwAoAEQAQQBEACkAIABmAG8AcgAgAGUAYQBj
AGgAIABhAGQAZAByAGUAcwBzAC4ADQAKACAAIAAgACAAIAAgACAAVABoAGUAIABkAGUAZgBhAHUA
bAB0ACAAdgBhAGwAdQBlACAAZgBvAHIAIABEAHUAcABBAGQAZAByAEQAZQB0AGUAYwB0AFQAcgBh
AG4AcwBtAGkAdABzACAAdgBhAHIAaQBhAGIAbABlACAAaQBzAA0ACgAgACAAIAAgACAAIAAgAHMA
cABlAGMAaQBmAGkAZQBkACAAYQBzACAAMQAgAGkAbgAgAHMAZQBjAHQAaQBvAG4AIAA1AC4AMQAg
AG8AZgAgAFIARgBDACAAMgA0ADYAMgAgAFsAQQBEAEQAUgBDAE8ATgBGAF0ALgANAAoADQAKACAA
IAAgADYALgAgACAASQBmACAAdABoAGUAIABEAGUAZgBhAHUAbAB0ACAAUgBvAHUAdABlAHIAIABM
AGkAcwB0ACAAaQBzACAAZQBtAHAAdAB5ACwAIAB0AGgAZQAgAGgAbwBzAHQAIABNAFUAUwBUACAA
TgBPAFQAIABhAHMAcwB1AG0AZQANAAoAIAAgACAAIAAgACAAIAB0AGgAYQB0ACAAYQBsAGwAIABk
AGUAcwB0AGkAbgBhAHQAaQBvAG4AcwAgAGEAcgBlACAAbwBuAC0AbABpAG4AawAuACAAIABUAGgA
ZQAgAGgAbwBzAHQAIABNAFUAUwBUACAATgBPAFQAIABwAGUAcgBmAG8AcgBtAA0ACgAgACAAIAAg
ACAAIAAgAGEAZABkAHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAAZgBvAHIAIABuAG8A
bgAtAGwAaQBuAGsALQBsAG8AYwBhAGwAIABhAGQAZAByAGUAcwBzAGUAcwAuACAAIABUAGgAZQAg
AGgAbwBzAHQAIABTAEgATwBVAEwARAANAAoADQAKAA0ACgANAAoAUwBpAG4AZwBoACAAJgAgAEIA
ZQBlAGIAZQBlACAAIAAgACAAIAAgACAAIAAgACAARQB4AHAAaQByAGUAcwAgAEQAZQBjAGUAbQBi
AGUAcgAgADIAMwAsACAAMgAwADAANwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABbAFAA
YQBnAGUAIAA0AF0ADQAKAAwADQAKAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdAAgACAAIAAg
ACAAIAAgACAAIABOAEQAIABJAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AIABQAGkAdABmAGEA
bABsAHMAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEoAdQBuAGUAIAAyADAAMAA3AA0ACgAN
AAoADQAKACAAIAAgACAAIAAgACAAcwBlAG4AZAAgAGEAbgAgAEkAQwBNAFAAdgA2ACAARABlAHMA
dABpAG4AYQB0AGkAbwBuACAAVQBuAHIAZQBhAGMAaABhAGIAbABlACAAbQBlAHMAcwBhAGcAZQAg
AGkAbgBzAHQAZQBhAGQALgANAAoAIAAgACAAIAAgACAAIABkAHIAYQBmAHQALQBpAGUAdABmAC0A
dgA2AG8AcABzAC0AbwBuAGwAaQBuAGsAYQBzAHMAdQBtAHAAdABpAG8AbgAtADAANAANAAoAIAAg
ACAAIAAgACAAIABbAEkALgBEAC4AaQBlAHQAZgAtAHYANgBvAHAAcwAtAG8AbgBsAGkAbgBrAGEA
cwBzAHUAbQBwAHQAaQBvAG4AcwBdACAAcAByAG8AdgBpAGQAZQBzACAAagB1AHMAdABpAGYAaQBj
AGEAdABpAG8AbgAgAGYAbwByAA0ACgAgACAAIAAgACAAIAAgAHQAaABpAHMAIAByAHUAbABlAC4A
DQAKAA0ACgAgACAAIABUAGgAZQAgAHQAeQBwAGUAIABvAGYAIABSAEEAIAByAGUAYwBlAGkAdgBl
AGQAIABjAGEAbgAgAGYAdQByAHQAaABlAHIAIABkAGUAdABlAHIAbQBpAG4AZQAgAGgAbwBzAHQA
IABiAGUAaABhAHYAaQBvAHIALgANAAoADQAKADIALgAxAC4AIAAgAFIAQQAgAFMAZQB0AHMAIABN
ACAAYQBuAGQAIABPACAAQgBpAHQAcwAgAGIAdQB0ACAAZABvAGUAcwAgAG4AbwB0ACAASQBuAGMA
bAB1AGQAZQAgAHQAaABlACAAUAByAGUAZgBpAHgAIABJAG4AZgBvAHIAbQBhAHQAaQBvAG4ADQAK
ACAAIAAgACAAIAAgAE8AcAB0AGkAbwBuACAAKABQAEkATwApAA0ACgANAAoAIAAgACAAUwBlAGMA
dABpAG8AbgAgADMALgAxACAAbwBmACAAUgBGAEMAIAAyADQANgAxACAAWwBOAEQAXQAgAGQAZQBz
AGMAcgBpAGIAZQBzACAAaQBuAHQAZQBuAGQAZQBkACAAYgBlAGgAYQB2AGkAbwByACAAdwBoAGUA
bgAgAGEAIABoAG8AcwB0AA0ACgAgACAAIAByAGUAYwBlAGkAdgBlAHMAIABhAG4AIABSAEEAIAB3
AGkAdABoAG8AdQB0ACAAYQBuACAAYQBkAHYAZQByAHQAaQBzAGUAZAAgAHAAcgBlAGYAaQB4ADoA
DQAKAA0ACgAgACAAIAAgACAAIAAiAE0AdQBsAHQAaQBwAGwAZQAgAHAAcgBlAGYAaQB4AGUAcwAg
AGMAYQBuACAAYgBlACAAYQBzAHMAbwBjAGkAYQB0AGUAZAAgAHcAaQB0AGgAIAB0AGgAZQAgAHMA
YQBtAGUAIABsAGkAbgBrAC4AIAAgAEIAeQANAAoAIAAgACAAIAAgACAAZABlAGYAYQB1AGwAdAAs
ACAAaABvAHMAdABzACAAbABlAGEAcgBuACAAYQBsAGwAIABvAG4ALQBsAGkAbgBrACAAcAByAGUA
ZgBpAHgAZQBzACAAZgByAG8AbQAgAFIAbwB1AHQAZQByAA0ACgAgACAAIAAgACAAIABBAGQAdgBl
AHIAdABpAHMAZQBtAGUAbgB0AHMALgAgACAASABvAHcAZQB2AGUAcgAsACAAcgBvAHUAdABlAHIA
cwAgAG0AYQB5ACAAYgBlACAAYwBvAG4AZgBpAGcAdQByAGUAZAAgAHQAbwAgAG8AbQBpAHQAIABz
AG8AbQBlAA0ACgAgACAAIAAgACAAIABvAHIAIABhAGwAbAAgAHAAcgBlAGYAaQB4AGUAcwAgAGYA
cgBvAG0AIABSAG8AdQB0AGUAcgAgAEEAZAB2AGUAcgB0AGkAcwBlAG0AZQBuAHQAcwAuACAAIABJ
AG4AIABzAHUAYwBoACAAYwBhAHMAZQBzACAAaABvAHMAdABzAA0ACgAgACAAIAAgACAAIABhAHMA
cwB1AG0AZQAgAHQAaABhAHQAIABkAGUAcwB0AGkAbgBhAHQAaQBvAG4AcwAgAGEAcgBlACAAbwBm
AGYALQBsAGkAbgBrACAAYQBuAGQAIABzAGUAbgBkACAAdAByAGEAZgBmAGkAYwAgAHQAbwAgAHIA
bwB1AHQAZQByAHMALgANAAoAIAAgACAAIAAgACAAQQAgAHIAbwB1AHQAZQByACAAYwBhAG4AIAB0
AGgAZQBuACAAaQBzAHMAdQBlACAAcgBlAGQAaQByAGUAYwB0AHMAIABhAHMAIABhAHAAcAByAG8A
cAByAGkAYQB0AGUALgAiAA0ACgANAAoAIAAgACAAQQBuACAASQBQAHYANgAgAHIAbwB1AHQAZQBy
ACAAcwBlAG4AZABzACAAYQBuACAAUgBBACAAdwBpAHQAaAAgAG4AbwAgAHAAcgBlAGYAaQB4ACAA
YQBkAHYAZQByAHQAaQBzAGUAZAAgAGEAbgBkACAAdABoAGUAIABNACAAYQBuAGQAIABPAA0ACgAg
ACAAIABiAGkAdABzACAAcwBlAHQAIABhAG4AZAAgAGQAbwBlAHMAIABuAG8AdAAgAHMAZQBuAGQA
IABhAG4AeQAgAFIAZQBkAGkAcgBlAGMAdABzAC4AIAAgAE8AbgAgAHIAZQBjAGUAaQBwAHQAIABv
AGYAIAB0AGgAZQAgAFIAQQAsACAAdABoAGUADQAKACAAIAAgAGgAbwBzAHQAIAB1AHMAZQBzACAA
RABIAEMAUAB2ADYAIAB0AG8AIABhAGMAcQB1AGkAcgBlACAAYQBuACAASQBQAHYANgAgAGEAZABk
AHIAZQBzAHMALgAgACAAQQBmAHQAZQByACAAYwBvAG0AcABsAGUAdABpAG4AZwAgAEkAUAB2ADYA
DQAKACAAIAAgAGEAZABkAHIAZQBzAHMAIABhAGMAcQB1AGkAcwBpAHQAaQBvAG4ALAAgAHQAaABl
ACAAaABvAHMAdAAgAE0AVQBTAFQAIABvAGIAZQB5ACAAUgBGAEMAIAAyADQANgAxACAAWwBOAEQA
XQAsACAAcwBlAGMAdABpAG8AbgAgADMALgAxAC4ADQAKACAAIAAgAFMAaQBuAGMAZQAgAHQAaABl
ACAAUgBBACAAaQBzACAAdABoAGUAIABvAG4AbAB5ACAAYQB1AHQAaABvAHIAaQB0AHkAIAB0AG8A
IABhACAAaABvAHMAdAAgAGYAbwByACAAbwBuAC0AbABpAG4AawANAAoAIAAgACAAZABlAHQAZQBy
AG0AaQBuAGEAdABpAG8AbgAgAGEAbgBkACAAdABoAGkAcwAgAFIAQQAgAGQAbwBlAHMAIABuAG8A
dAAgAGEAZAB2AGUAcgB0AGkAcwBlACAAYQBuAHkAIABwAHIAZQBmAGkAeAAsACAAdABoAGUAIABo
AG8AcwB0AA0ACgAgACAAIABjAGEAbgBuAG8AdAAgAGQAZQB0AGUAcgBtAGkAbgBlACAAdABoAGEA
dAAgAGEAIABkAGUAcwB0AGkAbgBhAHQAaQBvAG4AIABpAHMAIABvAG4ALQBsAGkAbgBrAC4AIAAg
AFQAaABlAHIAZQBmAG8AcgBlACwAIAB0AGgAZQAgAGgAbwBzAHQADQAKACAAIAAgAE0AVQBTAFQA
IABhAGQAaABlAHIAZQAgAHQAbwAgAHQAaABlACAAZgBvAGwAbABvAHcAaQBuAGcAIAByAHUAbABl
AHMAOgANAAoADQAKACAAIAAgADEALgAgACAAVABoAGUAIABoAG8AcwB0ACAATQBVAFMAVAAgAE4A
TwBUACAAYQBzAHMAdQBtAGUAIABhAG4AeQAgAGQAZQBmAGEAdQBsAHQAIABwAHIAZQBmAGkAeAAg
AGwAZQBuAGcAdABoAC4ADQAKAA0ACgAgACAAIAAyAC4AIAAgAFQAaABlACAAaABvAHMAdAAgAE0A
VQBTAFQAIABzAGUAbgBkACAAYQBsAGwAIAB0AHIAYQBmAGYAaQBjACAAdABvACAAdABoAGUAIABk
AGUAZgBhAHUAbAB0ACAAcgBvAHUAdABlAHIALgANAAoADQAKACAAIAAgADMALgAgACAAVABoAGUA
IABoAG8AcwB0ACAATQBVAFMAVAAgAE4ATwBUACAAaQBzAHMAdQBlACAAYQBuACAATgBTACAAdABv
ACAAcgBlAHMAbwBsAHYAZQAgAGEAIABkAGUAcwB0AGkAbgBhAHQAaQBvAG4AIABvAHQAaABlAHIA
IAB0AGgAYQBuAA0ACgAgACAAIAAgACAAIAAgAHQAaABlACAATABpAG4AawAtAEwAbwBjAGEAbAAg
AGEAZABkAHIAZQBzAHMAIABvAGYAIAB0AGgAZQAgAGQAZQBmAGEAdQBsAHQAIAByAG8AdQB0AGUA
cgAuAA0ACgANAAoAMgAuADIALgAgACAAUgBBACAAQQBkAHYAZQByAHQAaQBzAGUAcwAgAGEAIABQ
AHIAZQBmAGkAeAAgAHcAaQB0AGgAIAB0AGgAZQAgAE8AbgAtAGwAaQBuAGsAKABMACkAIABCAGkA
dAAgAFMAZQB0AA0ACgANAAoAIAAgACAAUwBlAGMAdQByAGkAdAB5ACAAYwBvAG4AcwBlAHEAdQBl
AG4AYwBlAHMAIABvAGYAIABSAEYAQwAgADIANAA2ADEAIABbAE4ARABdACAAaQBtAHAAbAB5ACAA
dABoAGEAdAAgAGgAbwBzAHQAcwAgAE0AQQBZACAAcwBlAG4AZAAgAGEAbABsAA0ACgAgACAAIAB0
AHIAYQBmAGYAaQBjACAAdABvACAAdABoAGUAIABkAGUAZgBhAHUAbAB0ACAAcgBvAHUAdABlAHIA
IAB3AGkAdABoAG8AdQB0ACAAcABlAHIAZgBvAHIAbQBpAG4AZwAgAGEAZABkAHIAZQBzAHMAIABy
AGUAcwBvAGwAdQB0AGkAbwBuAA0ACgAgACAAIABmAGkAcgBzAHQAIABlAHYAZQBuACAAdwBoAGUA
bgAgAGEAIABQAEkATwAgAGgAYQBzACAAYgBlAGUAbgAgAHIAZQBjAGUAaQB2AGUAZAAgAGEAZAB2
AGUAcgB0AGkAcwBpAG4AZwAgAGEAbgAgAG8AbgAtAGwAaQBuAGsADQAKACAAIAAgAHAAcgBlAGYA
aQB4ACwAIAByAGUAZwBhAHIAZABsAGUAcwBzACAAbwBmACAAdwBoAGUAdABoAGUAcgAgAHQAaABl
ACAAaABvAHMAdAAgAHAAZQByAGYAbwByAG0AcwAgAEQASABDAFAAdgA2ACAAYQBuAGQALwBvAHIA
DQAKACAAIAAgAHMAdABhAHQAZQBsAGUAcwBzACAAYQB1AHQAbwBjAG8AbgBmAGkAZwB1AHIAYQB0
AGkAbwBuAC4ADQAKAA0ACgAgACAAIABTAGUAYwB0AGkAbwBuACAANAAuADYALgAyACAAbwBmACAA
UgBGAEMAIAAyADQANgAxACAAWwBOAEQAXQAgAGQAZQBmAGkAbgBlAHMAIAB0AGgAZQAgAFYAYQBs
AGkAZAAgAEwAaQBmAGUAdABpAG0AZQAgAGkAbgAgAHQAaABlACAAUABJAE8ADQAKACAAIAAgAGEA
cwA6AA0ACgANAAoADQAKAA0ACgANAAoADQAKAFMAaQBuAGcAaAAgACYAIABCAGUAZQBiAGUAZQAg
ACAAIAAgACAAIAAgACAAIAAgAEUAeABwAGkAcgBlAHMAIABEAGUAYwBlAG0AYgBlAHIAIAAyADMA
LAAgADIAMAAwADcAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEAZwBlACAANQBd
AA0ACgAMAA0ACgBJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAAgACAAIAAgACAAIAAgACAA
TgBEACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACAAUABpAHQAZgBhAGwAbABzACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIABKAHUAbgBlACAAMgAwADAANwANAAoADQAKAA0ACgAgACAA
IAAgACAAIAAiAFQAaABlACAAbABlAG4AZwB0AGgAIABvAGYAIAB0AGkAbQBlACAAaQBuACAAcwBl
AGMAbwBuAGQAcwAgACgAcgBlAGwAYQB0AGkAdgBlACAAdABvACAAdABoAGUAIAB0AGkAbQBlACAA
dABoAGUAIABwAGEAYwBrAGUAdAAgAGkAcwANAAoAIAAgACAAIAAgACAAcwBlAG4AdAApACAAdABo
AGEAdAAgAHQAaABlACAAcAByAGUAZgBpAHgAIABpAHMAIAB2AGEAbABpAGQAIABmAG8AcgAgAHQA
aABlACAAcAB1AHIAcABvAHMAZQAgAG8AZgAgAG8AbgAtAGwAaQBuAGsADQAKACAAIAAgACAAIAAg
AGQAZQB0AGUAcgBtAGkAbgBhAHQAaQBvAG4ALgAiAA0ACgANAAoAIAAgACAAUwBlAGMAdABpAG8A
bgAgADEAMQAgAG8AZgAgAFIARgBDACAAMgA0ADYAMQAgAFsATgBEAF0AIABtAGUAbgB0AGkAbwBu
AHMAIAB0AGgAZQAgAGYAbwBsAGwAbwB3AGkAbgBnACAAZABlAG4AaQBhAGwAIABvAGYAIABzAGUA
cgB2AGkAYwBlAA0ACgAgACAAIABhAHQAdABhAGMAawA6AA0ACgANAAoAIAAgACAAIAAgACAAIgBB
AG4AIABlAHgAYQBtAHAAbABlACAAbwBmACAAZABlAG4AaQBhAGwAIABvAGYAIABzAGUAcgB2AGkA
YwBlACAAYQB0AHQAYQBjAGsAcwAgAGkAcwAgAHQAaABhAHQAIABhACAAbgBvAGQAZQAgAG8AbgAg
AHQAaABlAA0ACgAgACAAIAAgACAAIABsAGkAbgBrACAAdABoAGEAdAAgAGMAYQBuACAAcwBlAG4A
ZAAgAHAAYQBjAGsAZQB0AHMAIAB3AGkAdABoACAAYQBuACAAYQByAGIAaQB0AHIAYQByAHkAIABJ
AFAAIABzAG8AdQByAGMAZQAgAGEAZABkAHIAZQBzAHMAIABjAGEAbgANAAoAIAAgACAAIAAgACAA
YgBvAHQAaAAgAGEAZAB2AGUAcgB0AGkAcwBlACAAaQB0AHMAZQBsAGYAIABhAHMAIABhACAAZABl
AGYAYQB1AGwAdAAgAHIAbwB1AHQAZQByACAAYQBuAGQAIABhAGwAcwBvACAAcwBlAG4AZAAgACcA
ZgBvAHIAZwBlAGQAJwANAAoAIAAgACAAIAAgACAAUgBvAHUAdABlAHIAIABBAGQAdgBlAHIAdABp
AHMAZQBtAGUAbgB0ACAAbQBlAHMAcwBhAGcAZQBzACAAdABoAGEAdAAgAGkAbQBtAGUAZABpAGEA
dABlAGwAeQAgAHQAaQBtAGUAIABvAHUAdAAgAGEAbABsACAAbwB0AGgAZQByAA0ACgAgACAAIAAg
ACAAIABkAGUAZgBhAHUAbAB0ACAAcgBvAHUAdABlAHIAcwAgAGEAcwAgAHcAZQBsAGwAIABhAHMA
IABhAGwAbAAgAG8AbgAtAGwAaQBuAGsAIABwAHIAZQBmAGkAeABlAHMALgAiAA0ACgANAAoAIAAg
ACAAVABoAGUAIABzAGEAbQBlACAAcwBlAGMAdQByAGkAdAB5ACAAcgBpAHMAawAgAGkAcwAgAGEA
bABzAG8AIABkAGUAcwBjAHIAaQBiAGUAZAAgAGkAbgAgAHMAZQBjAHQAaQBvAG4AIAA1AC4ANQAu
ADMAIABvAGYAIABSAEYAQwAgADIANAA2ADIADQAKACAAIAAgAFsAQQBEAEQAUgBDAE8ATgBGAF0A
LgAgACAAVABoAGkAcwAgAHMAZQBjAHQAaQBvAG4AIABhAGwAbABvAHcAcwAgAGgAbwBzAHQAcwAg
AHQAbwAgAGkAZwBuAG8AcgBlACAAdABoAGUAIABWAGEAbABpAGQAIABMAGkAZgBlAHQAaQBtAGUA
DQAKACAAIAAgAHMAdABvAHIAZQBkACAAaQBuACAAYQBuACAAUgBBACAAaQBuACAAbwByAGQAZQBy
ACAAdABvACAAcAByAGUAdgBlAG4AdAAgAGQAZQBuAGkAYQBsACAAbwBmACAAcwBlAHIAdgBpAGMA
ZQAgAGEAdAB0AGEAYwBrAHMALgANAAoADQAKACAAIAAgAFMAZQBjAHQAaQBvAG4AIAA2AC4AMwAu
ADQAIABvAGYAIABSAEYAQwAgADIANAA2ADEAIABbAE4ARABdACAAbQBlAG4AdABpAG8AbgBzACAA
dABoAGEAdAAgAGgAbwBzAHQAcwAgAE0AQQBZACAAcwBlAG4AZAAgAGEAbABsAA0ACgAgACAAIAB0
AHIAYQBmAGYAaQBjACAAdABvACAAdABoAGUAIABkAGUAZgBhAHUAbAB0ACAAcgBvAHUAdABlAHIA
IAB3AGkAdABoAG8AdQB0ACAAcABlAHIAZgBvAHIAbQBpAG4AZwAgAGEAZABkAHIAZQBzAHMAIABy
AGUAcwBvAGwAdQB0AGkAbwBuAA0ACgAgACAAIABmAGkAcgBzAHQAOgANAAoADQAKACAAIAAgACAA
IAAgACIAUwB0AGEAdABlAGwAZQBzAHMAIABhAGQAZAByAGUAcwBzACAAYQB1AHQAbwBjAG8AbgBm
AGkAZwB1AHIAYQB0AGkAbwBuACAAUgBGAEMAIAAyADQANgAyACAAWwBBAEQARABSAEMATwBOAEYA
XQAgAG0AYQB5ACAAaQBuAA0ACgAgACAAIAAgACAAIABzAG8AbQBlACAAYwBpAHIAYwB1AG0AcwB0
AGEAbgBjAGUAcwAgAGkAbgBjAHIAZQBhAHMAZQAgAHQAaABlACAAVgBhAGwAaQBkACAATABpAGYA
ZQB0AGkAbQBlACAAbwBmACAAYQAgAHAAcgBlAGYAaQB4ACAAbwByAA0ACgAgACAAIAAgACAAIABp
AGcAbgBvAHIAZQAgAGkAdAAgAGMAbwBtAHAAbABlAHQAZQBsAHkAIABpAG4AIABvAHIAZABlAHIA
IAB0AG8AIABwAHIAZQB2AGUAbgB0ACAAYQAgAHAAYQByAHQAaQBjAHUAbABhAHIAIABkAGUAbgBp
AGEAbAAgAG8AZgANAAoAIAAgACAAIAAgACAAcwBlAHIAdgBpAGMAZQAgAGEAdAB0AGEAYwBrAC4A
IAAgAEgAbwB3AGUAdgBlAHIALAAgAHMAaQBuAGMAZQAgAHQAaABlACAAZQBmAGYAZQBjAHQAIABv
AGYAIAB0AGgAZQAgAHMAYQBtAGUAIABkAGUAbgBpAGEAbAAgAG8AZgANAAoAIAAgACAAIAAgACAA
cwBlAHIAdgBpAGMAZQAgAHQAYQByAGcAZQB0AGUAZAAgAGEAdAAgAHQAaABlACAAbwBuAC0AbABp
AG4AawAgAHAAcgBlAGYAaQB4ACAAbABpAHMAdAAgAGkAcwAgAG4AbwB0ACAAYwBhAHQAYQBzAHQA
cgBvAHAAaABpAGMADQAKACAAIAAgACAAIAAgACgAaABvAHMAdABzACAAdwBvAHUAbABkACAAcwBl
AG4AZAAgAHAAYQBjAGsAZQB0AHMAIAB0AG8AIABhACAAZABlAGYAYQB1AGwAdAAgAHIAbwB1AHQA
ZQByACAAYQBuAGQAIAByAGUAYwBlAGkAdgBlACAAYQANAAoAIAAgACAAIAAgACAAcgBlAGQAaQBy
AGUAYwB0ACAAcgBhAHQAaABlAHIAIAB0AGgAYQBuACAAcwBlAG4AZABpAG4AZwAgAHAAYQBjAGsA
ZQB0AHMAIABkAGkAcgBlAGMAdABsAHkAIAB0AG8AIABhACAAbgBlAGkAZwBoAGIAbwByACkAIAB0
AGgAZQANAAoAIAAgACAAIAAgACAATgBlAGkAZwBoAGIAbwByACAARABpAHMAYwBvAHYAZQByAHkA
IABwAHIAbwB0AG8AYwBvAGwAIABkAG8AZQBzACAAbgBvAHQAIABpAG0AcABvAHMAZQAgAHMAdQBj
AGgAIABhACAAYwBoAGUAYwBrACAAbwBuACAAdABoAGUADQAKACAAIAAgACAAIAAgAHAAcgBlAGYA
aQB4ACAAbABpAGYAZQB0AGkAbQBlACAAdgBhAGwAdQBlAHMALgAiAA0ACgANAAoAIAAgACAAQwBv
AG4AcwBpAGQAZQByACAAdABoAGUAIABmAG8AbABsAG8AdwBpAG4AZwAgAHMAYwBlAG4AYQByAGkA
bwAgAHcAaQB0AGgAIABvAG4AZQAgAHIAbwBnAHUAZQAgAG4AbwBkAGUAIABhAG4AZAAgAHQAdwBv
ACAAbwB0AGgAZQByAA0ACgAgACAAIABoAG8AcwB0AHMAIABvAG4AIAB0AGgAZQAgAHMAYQBtAGUA
IABsAGkAbgBrAC4AIAAgAFQAaABlACAAcgBvAGcAdQBlACAAcwBlAG4AZABzACAAYQAgAG0AYQBs
AGkAYwBpAG8AdQBzACAAUgBBACAAdwBpAHQAaAAgAGEAbgAgAG8AbgAtAA0ACgAgACAAIABsAGkA
bgBrACAAcAByAGUAZgBpAHgAIAB3AGkAdABoACAAYQAgAFYAYQBsAGkAZAAgAEwAaQBmAGUAdABp
AG0AZQAgAG8AZgAgAHoAZQByAG8ALgAgACAASABvAHMAdAAxACAAYwBvAHIAcgBlAGMAdABsAHkA
DQAKACAAIAAgAGkAbQBwAGwAZQBtAGUAbgB0AHMAIABzAGUAYwB0AGkAbwBuACAANQAuADUALgAz
ACAAbwBmACAAUgBGAEMAIAAyADQANgAyACAAWwBBAEQARABSAEMATwBOAEYAXQAgAGEAbgBkACAA
cgBlAHMAZQB0AHMAIABpAHQAcwANAAoAIAAgACAAUwB0AG8AcgBlAGQATABpAGYAZQB0AGkAbQBl
ACAAKABvAHIAIABSAGUAbQBhAGkAbgBpAG4AZwBMAGkAZgBlAHQAaQBtAGUAIABpAG4AIABkAHIA
YQBmAHQALQBpAGUAdABmAC0AaQBwAHYANgAtAHIAZgBjADIANAA2ADIAYgBpAHMALQAwADgADQAK
ACAAIAAgAFsAQQBEAEQAUgBDAE8ATgBGAGIAaQBzAF0AKQAgAHQAbwAgAHQAdwBvACAAaABvAHUA
cgBzACAAYQBuAGQAIABhAHYAbwBpAGQAcwAgAHQAaABlACAAZABlAG4AaQBhAGwAIABvAGYAIABz
AGUAcgB2AGkAYwBlACAAYQB0AHQAYQBjAGsALgANAAoAIAAgACAASABvAHMAdAAxACAAdAByAGkA
ZQBzACAAdABvACAAcwBlAG4AZAAgAHQAcgBhAGYAZgBpAGMAIAB0AG8AIABIAG8AcwB0ADIALAAg
AGIAdQB0ACAAYwBhAG4AbgBvAHQAIAB0AHIAdQBzAHQAIABpAHQAcwAgAG8AdwBuACAAdAB3AG8A
DQAKACAAIAAgAGgAbwB1AHIAIABTAHQAbwByAGUAZABMAGkAZgBlAHQAaQBtAGUALgAgACAARgBv
AHIAIABpAG4AcwB0AGEAbgBjAGUALAAgAGEAIABsAGUAZwBpAHQAaQBtAGEAdABlACAAbwBwAGUA
cgBhAHQAbwByACAAbQBhAHkAIABoAGEAdgBlAA0ACgAgACAAIAB0AHIAaQBlAGQAIAB0AG8AIAB0
AGkAbQBlACAAbwB1AHQAIAB0AGgAZQAgAHAAcgBlAGYAaQB4ACAAZAB1AGUAIAB0AG8AIABhAG4A
IABpAG0AcABlAG4AZABpAG4AZwAgAHIAZQBuAHUAbQBiAGUAcgBpAG4AZwAuACAAIABIAG8AcwB0
ADEADQAKACAAIAAgAGQAZQBjAGkAZABlAHMAIAB0AG8AIABzAGUAbgBkACAAYQBsAGwAIABvAGYA
IABpAHQAcwAgAHQAcgBhAGYAZgBpAGMAIAB0AG8AIAB0AGgAZQAgAG8AbgAtAGwAaQBuAGsAIABh
AHUAdABoAG8AcgBpAHQAeQAsACAAdABoAGUADQAKACAAIAAgAGQAZQBmAGEAdQBsAHQAIAByAG8A
dQB0AGUAcgAsACAAZQB2AGUAbgAgAHQAaABvAHUAZwBoACAAdABoAGUAIABkAGUAcwB0AGkAbgBh
AHQAaQBvAG4AIABwAHIAZQBmAGkAeAAgAGkAcwAgAG8AbgAtAGwAaQBuAGsALgANAAoADQAKACAA
IAAgAEkARgAgAHQAaABlACAAaABvAHMAdAAgAGQAZQBjAGkAZABlAHMAIAB0AG8AIABzAGUAbgBk
ACAAYQBsAGwAIAB0AHIAYQBmAGYAaQBjACAAKABpAG4AYwBsAHUAZABpAG4AZwAgAG8AbgAtAGwA
aQBuAGsAIAB0AHIAYQBmAGYAaQBjACkADQAKACAAIAAgAHQAbwAgAHQAaABlACAAZABlAGYAYQB1
AGwAdAAgAHIAbwB1AHQAZQByACwAIAB0AGgAZQBuACAAdABoAGUAIABoAG8AcwB0ACAATQBVAFMA
VAAgAGYAbwBsAGwAbwB3ACAAdABoAGUAIABmAG8AbABsAG8AdwBpAG4AZwAgAHIAdQBsAGUAOgAN
AAoADQAKACAAIAAgADEALgAgACAAVABoAGUAIABoAG8AcwB0ACAATQBVAFMAVAAgAE4ATwBUACAA
aQBzAHMAdQBlACAAYQBuACAATgBTACAAdABvACAAcgBlAHMAbwBsAHYAZQAgAGEAIABkAGUAcwB0
AGkAbgBhAHQAaQBvAG4AIABvAHQAaABlAHIAIAB0AGgAYQBuAA0ACgAgACAAIAAgACAAIAAgAHQA
aABlACAATABpAG4AawAtAEwAbwBjAGEAbAAgAGEAZABkAHIAZQBzAHMAIABvAGYAIAB0AGgAZQAg
AGQAZQBmAGEAdQBsAHQAIAByAG8AdQB0AGUAcgAuAA0ACgANAAoADQAKAA0ACgBTAGkAbgBnAGgA
IAAmACAAQgBlAGUAYgBlAGUAIAAgACAAIAAgACAAIAAgACAAIABFAHgAcABpAHIAZQBzACAARABl
AGMAZQBtAGIAZQByACAAMgAzACwAIAAyADAAMAA3ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgAFsAUABhAGcAZQAgADYAXQANAAoADAANAAoASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0
ACAAIAAgACAAIAAgACAAIAAgAE4ARAAgAEkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAgAFAA
aQB0AGYAYQBsAGwAcwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAASgB1AG4AZQAgADIAMAAw
ADcADQAKAA0ACgANAAoAMgAuADMALgAgACAAUgBBACAAQQBkAHYAZQByAHQAaQBzAGUAcwAgAGEA
IABQAHIAZQBmAGkAeAAgAHcAaQB0AGgAIAB0AGgAZQAgAE8AbgAtAGwAaQBuAGsAKABMACkAIABC
AGkAdAAgAEMAbABlAGEAcgANAAoADQAKACAAIAAgAFIAZQBnAGEAcgBkAGwAZQBzAHMAIABvAGYA
IAB3AGgAZQB0AGgAZQByACAAdABoAGUAIABoAG8AcwB0ACAAcABlAHIAZgBvAHIAbQBzACAARABI
AEMAUAB2ADYAIABhAG4AZAAvAG8AcgAgAHMAdABhAHQAZQBsAGUAcwBzAA0ACgAgACAAIABhAHUA
dABvAGMAbwBuAGYAaQBnAHUAcgBhAHQAaQBvAG4ALAAgAHQAaABlACAAaABvAHMAdAAgAE0AVQBT
AFQAIABhAGQAaABlAHIAZQAgAHQAbwAgAHQAaABlACAAZgBvAGwAbABvAHcAaQBuAGcAIAByAHUA
bABlAHMAIABmAG8AcgANAAoAIAAgACAAYQBkAGQAcgBlAHMAcwBlAHMAIABjAG8AbgB0AGEAaQBu
AGUAZAAgAHcAaQB0AGgAaQBuACAAdABoAGUAIABhAGQAdgBlAHIAdABpAHMAZQBkACAAcAByAGUA
ZgBpAHgAOgANAAoADQAKACAAIAAgADEALgAgACAAVABoAGUAIABoAG8AcwB0ACAATQBVAFMAVAAg
AE4ATwBUACAAaQBzAHMAdQBlACAAYQBuACAATgBTACAAdABvACAAcgBlAHMAbwBsAHYAZQAgAGEA
IABkAGUAcwB0AGkAbgBhAHQAaQBvAG4AIABvAHQAaABlAHIAIAB0AGgAYQBuAA0ACgAgACAAIAAg
ACAAIAAgAHQAaABlACAATABpAG4AawAtAEwAbwBjAGEAbAAgAGEAZABkAHIAZQBzAHMAIABvAGYA
IAB0AGgAZQAgAGQAZQBmAGEAdQBsAHQAIAByAG8AdQB0AGUAcgAuAA0ACgANAAoAIAAgACAAMgAu
ACAAIABUAGgAZQAgAGgAbwBzAHQAIABNAFUAUwBUACAAcwBlAG4AZAAgAGEAbABsACAAdAByAGEA
ZgBmAGkAYwAgAHQAbwAgAHQAaABlACAAZABlAGYAYQB1AGwAdAAgAHIAbwB1AHQAZQByAC4ADQAK
AA0ACgANAAoAMwAuACAAIABSAG8AdQB0AGUAcgAgAE0AbwBkAGUAbABzAA0ACgANAAoAIAAgACAA
VABoAGUAIABSAGUAZABpAHIAZQBjAHQAIABDAGwAYQByAGkAZgBpAGMAYQB0AGkAbwBuAHMAIABz
AGUAYwB0AGkAbwBuACAAYwBsAGEAcgBpAGYAaQBlAHMAIABSAEYAQwAgADIANAA2ADEAIABbAE4A
RABdACAAaABvAHMAdAAgAGEAbgBkAA0ACgAgACAAIAByAG8AdQB0AGUAcgAgAGIAZQBoAGEAdgBp
AG8AcgAgAGYAbwByACAAYQBuACAAYQBnAGcAcgBlAGcAYQB0AGkAbwBuACAAcgBvAHUAdABlAHIA
IABkAGUAcABsAG8AeQBtAGUAbgB0AC4ADQAKAA0ACgAgACAAIABUAGgAZQAgAEEAZwBnAHIAZQBn
AGEAdABpAG8AbgAgAFIAbwB1AHQAZQByACAARABlAHAAbABvAHkAbQBlAG4AdAAgAE0AbwBkAGUA
bAAgAHMAZQBjAHQAaQBvAG4AIABwAHIAZQBzAGUAbgB0AHMAIABhACAAcABvAHMAcwBpAGIAbABl
AA0ACgAgACAAIABhAGcAZwByAGUAZwBhAHQAaQBvAG4AIAByAG8AdQB0AGUAcgAgAGQAZQBwAGwA
bwB5AG0AZQBuAHQAIABtAG8AZABlAGwAIABmAG8AcgAgAEkAUAB2ADYAIABhAG4AZAAgAGQAaQBz
AGMAdQBzAHMAZQBzACAAaQB0AHMADQAKACAAIAAgAHAAcgBvAHAAZQByAHQAaQBlAHMAIAB3AGkA
dABoACAAcgBlAHMAcABlAGMAdAAgAHQAbwAgAE4ARAAuACAAIABBAGcAZwByAGUAZwBhAHQAaQBv
AG4AIAByAG8AdQB0AGUAcgBzACAAYwBhAG4AIABzAGUAcgB2AGkAYwBlACAAbQBvAHIAZQANAAoA
IAAgACAAdABoAGEAbgAgADEAMAAwACwAMAAwADAAIABzAHUAYgBzAGMAcgBpAGIAZQByAHMALgAg
ACAARAB1AGUAIAB0AG8AIABzAGMAYQBsAGkAbgBnACAAYwBvAG4AcwBpAGQAZQByAGEAdABpAG8A
bgBzACwAIABhAG4AeQAgAE4AUwAgAGYAbwByAA0ACgAgACAAIABnAGwAbwBiAGEAbAAgAGEAZABk
AHIAZQBzAHMAIAByAGUAcwBvAGwAdQB0AGkAbwBuACAAZgByAG8AbQAgAGEAbgB5ACAAaABvAHMA
dAAgAHQAbwAgAGEAbgB5ACAAbwB0AGgAZQByACAAaABvAHMAdAAgAFMASABPAFUATABEACAATgBP
AFQADQAKACAAIAAgAHIAZQBhAGMAaAAgAHQAaABlACAAYQBnAGcAcgBlAGcAYQB0AGkAbwBuACAA
cgBvAHUAdABlAHIALgANAAoADQAKADMALgAxAC4AIAAgAEEAZwBnAHIAZQBnAGEAdABpAG8AbgAg
AFIAbwB1AHQAZQByACAARABlAHAAbABvAHkAbQBlAG4AdAAgAE0AbwBkAGUAbAANAAoADQAKACAA
IAAgAEEAIABwAHIAbwBwAGUAcgB0AHkAIABvAGYAIAByAG8AdQB0AGUAZAAgAGEAZwBnAHIAZQBn
AGEAdABpAG8AbgAgAG4AZQB0AHcAbwByAGsAcwAgAGkAcwAgAHQAaABhAHQAIABoAG8AcwB0AHMA
IABjAGEAbgBuAG8AdAANAAoAIAAgACAAZABpAHIAZQBjAHQAbAB5ACAAYwBvAG0AbQB1AG4AaQBj
AGEAdABlACAAdwBpAHQAaAAgAGUAYQBjAGgAIABvAHQAaABlAHIAIABlAHYAZQBuACAAaQBmACAA
dABoAGUAeQAgAGEAcgBlACAAbwBuACAAdABoAGUAIABzAGEAbQBlAA0ACgAgACAAIABsAGkAbgBr
AC4AIAAgAFQAaABpAHMAIABkAGUAcwBpAGcAbgAgAGkAcwAgAG0AbwB0AGkAdgBhAHQAZQBkACAA
YgB5ACAAcwBjAGEAbABpAG4AZwAgAGEAbgBkACAAcwBlAGMAdQByAGkAdAB5AA0ACgAgACAAIABj
AG8AbgBzAGkAZABlAHIAYQB0AGkAbwBuAHMALgAgACAASQBmACAAZQB2AGUAcgB5ACAAaABvAHMA
dAAgAGMAbwB1AGwAZAAgAHIAZQBjAGUAaQB2AGUAIABhAGwAbAAgAHQAcgBhAGYAZgBpAGMAIABm
AHIAbwBtACAAZQB2AGUAcgB5AA0ACgAgACAAIABvAHQAaABlAHIAIABoAG8AcwB0ACwAIAB0AGgA
ZQBuACAAdABoAGUAIABzAHUAYgBzAGMAcgBpAGIAZQByACcAcwAgAHAAcgBpAHYAYQBjAHkAIAB3
AG8AdQBsAGQAIABiAGUAIAB2AGkAbwBsAGEAdABlAGQAIABhAG4AZAAgAHQAaABlAA0ACgAgACAA
IABhAG0AbwB1AG4AdAAgAG8AZgAgAGIAYQBuAGQAdwBpAGQAdABoACAAYQB2AGEAaQBsAGEAYgBs
AGUAIABmAG8AcgAgAGUAYQBjAGgAIABzAHUAYgBzAGMAcgBpAGIAZQByACAAdwBvAHUAbABkACAA
YgBlACAAdgBlAHIAeQANAAoAIAAgACAAcwBtAGEAbABsAC4AIAAgAFQAaABhAHQAIABpAHMAIAB3
AGgAeQAgAGgAbwBzAHQAcwAgAGMAbwBtAG0AdQBuAGkAYwBhAHQAZQAgAGIAZQB0AHcAZQBlAG4A
IABlAGEAYwBoACAAbwB0AGgAZQByACAAdABoAHIAbwB1AGcAaAAgAHQAaABlAA0ACgAgACAAIABh
AGcAZwByAGUAZwBhAHQAaQBvAG4AIAByAG8AdQB0AGUAcgAsACAAdwBoAGkAYwBoACAAaQBzACAA
YQBsAHMAbwAgAHQAaABlACAASQBQAHYANgAgAGYAaQByAHMAdAAtAGgAbwBwACAAcgBvAHUAdABl
AHIALgANAAoADQAKACAAIAAgAEYAbwByACAAcwBjAGEAbABpAG4AZwAgAHIAZQBhAHMAbwBuAHMA
LAAgAGEAbgB5ACAATgBTACAAdABvACAAcgBlAHMAbwBsAHYAZQAgAGEAbgB5ACAAYQBkAGQAcgBl
AHMAcwAgAG8AdABoAGUAcgAgAHQAaABhAG4AIAB0AGgAYQB0ACAAbwBmAA0ACgAgACAAIAB0AGgA
ZQAgAGQAZQBmAGEAdQBsAHQAIAByAG8AdQB0AGUAcgAgAFMASABPAFUATABEACAATgBPAFQAIABy
AGUAYQBjAGgAIAB0AGgAZQAgAGEAZwBnAHIAZQBnAGEAdABpAG8AbgAgAHIAbwB1AHQAZQByAC4A
DQAKAA0ACgANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAKwAtAC0ALQAtAC0AKwANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAfAAgACAAIAAgACAAfAANAAoAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAfABBAGcAZwByAGUAKwAtAC0A
LQAtACgAUgB0AHIAIABDAFAARQApAC0ALQAtAC0ASABvAHMAdAAxAA0ACgAgACAAIAAgACAAIAAg
ACAAIAAgACAAIABDAG8AcgBlAC0ALQAtAC0AVwBBAE4ALQAtAC0ALQArAGcAYQB0AG8AcgB8AA0A
CgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAB8
ACAAUgB0AHIAIAB8AA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAB8ACAAIAAgACAAIAArAC0ALQAtAC0AKABCAHIAIABDAFAARQApAC0ALQAt
AC0AKABDAHUAcwB0ACAAUgB0AHIAKQAtAC0ALQAtAEgAbwBzAHQAMgANAAoAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAKwAtAC0ALQAtAC0AKwAN
AAoADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgAEYAaQBnAHUAcgBlACAAMQAuAA0ACgANAAoADQAKAA0ACgBTAGkAbgBn
AGgAIAAmACAAQgBlAGUAYgBlAGUAIAAgACAAIAAgACAAIAAgACAAIABFAHgAcABpAHIAZQBzACAA
RABlAGMAZQBtAGIAZQByACAAMgAzACwAIAAyADAAMAA3ACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgAFsAUABhAGcAZQAgADcAXQANAAoADAANAAoASQBuAHQAZQByAG4AZQB0AC0ARAByAGEA
ZgB0ACAAIAAgACAAIAAgACAAIAAgAE4ARAAgAEkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAg
AFAAaQB0AGYAYQBsAGwAcwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAASgB1AG4AZQAgADIA
MAAwADcADQAKAA0ACgANAAoAIAAgACAASQBuACAAdABoAGUAIABmAGkAZwB1AHIAZQAgAGEAYgBv
AHYAZQAsACAAdABoAGUAIABjAHUAcwB0AG8AbQBlAHIAIABwAHIAZQBtAGkAcwBlAHMAIABlAHEA
dQBpAHAAbQBlAG4AdAAgACgAQwBQAEUAKQAgAGkAcwAgAG0AYQBuAGEAZwBlAGQADQAKACAAIAAg
AGIAeQAgAHQAaABlACAASQBTAFAAIABhAG4AZAAgAGkAcwAgAGQAZQBwAGwAbwB5AGUAZAAgAGIA
ZQBoAGkAbgBkACAAYQBuACAAYQBnAGcAcgBlAGcAYQB0AGkAbwBuACAAcgBvAHUAdABlAHIAIAB0
AGgAYQB0ACAAaQBzACAAYQBuAA0ACgAgACAAIABJAFAAdgA2ACAAZgBpAHIAcwB0AC0AaABvAHAA
IAByAG8AdQB0AGUAcgAgAGEAbgBkACAAYQBsAHMAbwAgAGEAIABEAEgAQwBQAHYANgAgAHIAZQBs
AGEAeQAgAGEAZwBlAG4AdAAuACAAIABJAFAAdgA2ACAAQwBQAEUAcwAgAGEAcgBlAA0ACgAgACAA
IABlAGkAdABoAGUAcgAgAEkAUAB2ADYAIAByAG8AdQB0AGUAcgBzACAAKABSAHQAcgAgAEMAUABF
ACkAIABvAHIAIABJAFAAdgA2ACAAYgByAGkAZABnAGUAcwAgACgAQgByACAAQwBQAEUAKQAuACAA
IABJAGYAIAB0AGgAZQANAAoAIAAgACAAYwB1AHMAdABvAG0AZQByACAAcAByAGUAbQBpAHMAZQBz
ACAAdQBzAGUAcwAgAGEAIABiAHIAaQBkAGcAZQAgAEMAUABFACwAIAB0AGgAZQBuACAAYQAgAHIA
bwB1AHQAZQByACAAKABDAHUAcwB0ACAAUgB0AHIAKQAgAGkAcwANAAoAIAAgACAAbgBlAGUAZABl
AGQALgAgACAAQQBsAGwAIABoAG8AcwB0AHMAIAByAGUAcwBpAGQAZQAgAGIAZQBoAGkAbgBkACAA
YQAgAHIAbwB1AHQAZQByACAAQwBQAEUAIABvAHIAIABhACAAYwB1AHMAdABvAG0AZQByACAAcgBv
AHUAdABlAHIALgANAAoADQAKACAAIAAgAE4AbwAgAE4AUwAgAHQAbwAgAHIAZQBzAG8AbAB2AGUA
IABhAG4AeQAgAGEAZABkAHIAZQBzAHMAIABvAHQAaABlAHIAIAB0AGgAYQB0ACAAdABoAGEAdAAg
AG8AZgAgAHQAaABlACAAZABlAGYAYQB1AGwAdAAgAHIAbwB1AHQAZQByAA0ACgAgACAAIAB3AGkA
bABsACAAcgBlAGEAYwBoACAAdABoAGUAIABhAGcAZwByAGUAZwBhAHQAaQBvAG4AIAByAG8AdQB0
AGUAcgAgAGYAcgBvAG0AIABhAG4AeQAgAGQAZQB2AGkAYwBlACAAbwBuACAAdABoAGUAIABjAHUA
cwB0AG8AbQBlAHIADQAKACAAIAAgAHMAaQBkAGUAIABvAGYAIAB0AGgAZQAgAGEAZwBnAHIAZQBn
AGEAdABvAHIALgAgACAAQwBQAEUAcwAgAGQAbwAgAG4AbwB0ACAAYwBvAG0AbQB1AG4AaQBjAGEA
dABlACAAdwBpAHQAaAAgAGUAYQBjAGgAIABvAHQAaABlAHIAIABpAG4ADQAKACAAIAAgAHQAaABp
AHMAIABkAGUAcABsAG8AeQBtAGUAbgB0ACAAbQBvAGQAZQBsACAAcwBpAG4AYwBlACAAYQAgAEMA
UABFACAAZABvAGUAcwAgAG4AbwB0ACAAcgB1AG4AIABhAG4AeQAgAGEAcABwAGwAaQBjAGEAdABp
AG8AbgBzACAAdABoAGEAdAANAAoAIAAgACAAbgBlAGUAZAAgAHQAbwAgAGMAbwBtAG0AdQBuAGkA
YwBhAHQAZQAgAHcAaQB0AGgAIABvAHQAaABlAHIAIABDAFAARQBzAC4AIAAgAEgAbwBzAHQAcwAg
AGQAbwAgAGMAbwBtAG0AdQBuAGkAYwBhAHQAZQAgAHcAaQB0AGgAIABlAGEAYwBoAA0ACgAgACAA
IABvAHQAaABlAHIALAAgAGIAdQB0ACAAZQB2AGUAcgB5ACAAaABvAHMAdAAgAGkAcwAgAG8AZgBm
AC0AbABpAG4AawAgAHQAbwAgAGEAbgB5ACAAbwB0AGgAZQByACAAaABvAHMAdAAgAG8AbgAgAHQA
aABlAA0ACgAgACAAIABhAGcAZwByAGUAZwBhAHQAaQBvAG4AIAByAG8AdQB0AGUAcgAuAA0ACgAN
AAoADQAKADQALgAgACAAUgBlAGQAaQByAGUAYwB0ACAAQwBsAGEAcgBpAGYAaQBjAGEAdABpAG8A
bgBzAA0ACgANAAoAIAAgACAAUgBlAGQAaQByAGUAYwB0AHMAIABNAFUAUwBUACAATgBPAFQAIABi
AGUAIABzAGUAbgB0ACAAYgB5ACAAYQBnAGcAcgBlAGcAYQB0AGkAbwBuACAAcgBvAHUAdABlAHIA
cwAgAGUAeABjAGUAcAB0ACAAdwBoAGUAbgAgAHQAdwBvAA0ACgAgACAAIABoAG8AcwB0AHMAIABi
AGUAaABpAG4AZAAgAHQAaABlACAAcwBhAG0AZQAgAGIAcgBpAGQAZwBlACAAQwBQAEUALAAgAHcA
aQB0AGgAIABuAG8AIAByAG8AdQB0AGUAcgAgAGIAZQB0AHcAZQBlAG4AIAB0AGgAZQAgAGgAbwBz
AHQAIABhAG4AZAANAAoAIAAgACAAdABoAGUAIABhAGcAZwByAGUAZwBhAHQAaQBvAG4AIAByAG8A
dQB0AGUAcgAsACAAYwBvAG0AbQB1AG4AaQBjAGEAdABlACAAdwBpAHQAaAAgAGUAYQBjAGgAIABv
AHQAaABlAHIALgAgACAAVABoAGUAIABhAGcAZwByAGUAZwBhAHQAaQBvAG4ADQAKACAAIAAgAHIA
bwB1AHQAZQByACAATQBBAFkAIABzAGUAbgBkACAAYQAgAFIAZQBkAGkAcgBlAGMAdAAgAHQAbwAg
AGEAIABzAG8AdQByAGMAZQAgAGgAbwBzAHQAIAB3AGgAaQBjAGgAIABjAG8AbQBtAHUAbgBpAGMA
YQB0AGUAcwAgAHcAaQB0AGgAIABhAA0ACgAgACAAIABkAGUAcwB0AGkAbgBhAHQAaQBvAG4AIABo
AG8AcwB0ACAAYgBlAGgAaQBuAGQAIAB0AGgAZQAgAHMAYQBtAGUAIABiAHIAaQBkAGcAZQAgAEMA
UABFAC4AIAAgAFMAaQBuAGMAZQAgAHQAaABlACAAUgBlAGQAaQByAGUAYwB0AA0ACgAgACAAIABj
AG8AbgB0AGEAaQBuAHMAIABhAGwAbAAgAHQAaABlACAAaQBuAGYAbwByAG0AYQB0AGkAbwBuACAA
bgBlAGUAZAAgAHQAbwAgAHIAZQBzAG8AbAB2AGUAIAB0AGgAZQAgAGEAZABkAHIAZQBzAHMAIABv
AGYAIAB0AGgAZQANAAoAIAAgACAAZABlAHMAdABpAG4AYQB0AGkAbwBuACAAaABvAHMAdAAsACAA
dABoAGUAIABzAG8AdQByAGMAZQAgAGgAbwBzAHQAIABNAFUAUwBUACAATgBPAFQAIABpAHMAcwB1
AGUAIABhAG4AIABOAFMAIAB0AG8AIAByAGUAcwBvAGwAdgBlACAAdABoAGUADQAKACAAIAAgAGQA
ZQBzAHQAaQBuAGEAdABpAG8AbgAgAGMAbwBuAHQAYQBpAG4AZQBkACAAdwBpAHQAaABpAG4AIAB0
AGgAZQAgAFIAZQBkAGkAcgBlAGMAdAAuAA0ACgANAAoADQAKADUALgAgACAAQwBoAGEAbgBnAGUA
cwAgAHQAbwAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2AC0AcgBmAGMAMgA0ADYAMgBi
AGkAcwAtADAAOAANAAoADQAKACAAIAAgAFQAaABlACAAZgBvAGwAbABvAHcAaQBuAGcAIABwAGEA
cgBhAGcAcgBhAHAAaAAgAGYAcgBvAG0AIABzAGUAYwB0AGkAbwBuACAANQAuADQAIABvAGYADQAK
ACAAIAAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2AC0AcgBmAGMAMgA0ADYAMgBiAGkA
cwAtADAAOAAgAFsAQQBEAEQAUgBDAE8ATgBGAGIAaQBzAF0AIABuAGUAZQBkAHMAIAB0AG8AIABj
AGgAYQBuAGcAZQA6AA0ACgANAAoAIAAgACAAIAAgACAAIgBFAGEAYwBoACAAaQBuAGQAaQB2AGkA
ZAB1AGEAbAAgAHUAbgBpAGMAYQBzAHQAIABhAGQAZAByAGUAcwBzACAAUwBIAE8AVQBMAEQAIABi
AGUAIAB0AGUAcwB0AGUAZAAgAGYAbwByACAAdQBuAGkAcQB1AGUAbgBlAHMAcwAuAA0ACgAgACAA
IAAgACAAIABOAG8AdABlACAAdABoAGEAdAAgAHQAaABlAHIAZQAgAGEAcgBlACAAaQBtAHAAbABl
AG0AZQBuAHQAYQB0AGkAbwBuAHMAIABkAGUAcABsAG8AeQBlAGQAIAB0AGgAYQB0ACAAbwBuAGwA
eQAgAHAAZQByAGYAbwByAG0ADQAKACAAIAAgACAAIAAgAEQAdQBwAGwAaQBjAGEAdABlACAAQQBk
AGQAcgBlAHMAcwAgAEQAZQB0AGUAYwB0AGkAbwBuACAAZgBvAHIAIAB0AGgAZQAgAGwAaQBuAGsA
LQBsAG8AYwBhAGwAIABhAGQAZAByAGUAcwBzACAAYQBuAGQAIABzAGsAaQBwAA0ACgAgACAAIAAg
ACAAIAB0AGgAZQAgAHQAZQBzAHQAIABmAG8AcgAgAHQAaABlACAAZwBsAG8AYgBhAGwAIABhAGQA
ZAByAGUAcwBzACAAdQBzAGkAbgBnACAAdABoAGUAIABzAGEAbQBlACAAaQBuAHQAZQByAGYAYQBj
AGUADQAKACAAIAAgACAAIAAgAGkAZABlAG4AdABpAGYAaQBlAHIAIABhAHMAIAB0AGgAYQB0ACAA
bwBmACAAdABoAGUAIABsAGkAbgBrAC0AbABvAGMAYQBsACAAYQBkAGQAcgBlAHMAcwAuACAAIABX
AGgAZQByAGUAYQBzACAAdABoAGkAcwANAAoAIAAgACAAIAAgACAAZABvAGMAdQBtAGUAbgB0ACAA
ZABvAGUAcwAgAG4AbwB0ACAAaQBuAHYAYQBsAGkAZABhAHQAZQAgAHMAdQBjAGgAIABpAG0AcABs
AGUAbQBlAG4AdABhAHQAaQBvAG4AcwAsACAAdABoAGkAcwAgAGsAaQBuAGQAIABvAGYADQAKACAA
IAAgACAAIAAgACcAbwBwAHQAaQBtAGkAegBhAHQAaQBvAG4AJwAgAGkAcwAgAE4ATwBUACAAUgBF
AEMATwBNAE0ARQBOAEQARQBEACwAIABhAG4AZAAgAG4AZQB3ACAAaQBtAHAAbABlAG0AZQBuAHQA
YQB0AGkAbwBuAHMAIABNAFUAUwBUAA0ACgAgACAAIAAgACAAIABOAE8AVAAgAGQAbwAgAHQAaABh
AHQAIABvAHAAdABpAG0AaQB6AGEAdABpAG8AbgAuACAAIABUAGgAaQBzACAAbwBwAHQAaQBtAGkA
egBhAHQAaQBvAG4AIABjAGEAbQBlACAAZgByAG8AbQAgAHQAaABlAA0ACgAgACAAIAAgACAAIABh
AHMAcwB1AG0AcAB0AGkAbwBuACAAdABoAGEAdAAgAGEAbABsACAAbwBmACAAYQBuACAAaQBuAHQA
ZQByAGYAYQBjAGUAJwBzACAAYQBkAGQAcgBlAHMAcwBlAHMAIABhAHIAZQAgAGcAZQBuAGUAcgBh
AHQAZQBkACAAZgByAG8AbQANAAoAIAAgACAAIAAgACAAdABoAGUAIABzAGEAbQBlACAAaQBkAGUA
bgB0AGkAZgBpAGUAcgAuACAAIABIAG8AdwBlAHYAZQByACwAIAB0AGgAZQAgAGEAcwBzAHUAbQBw
AHQAaQBvAG4AIABkAG8AZQBzACAAYQBjAHQAdQBhAGwAbAB5ACAAbgBvAHQADQAKACAAIAAgACAA
IAAgAHMAdABhAG4AZAA7ACAAbgBlAHcAIAB0AHkAcABlAHMAIABvAGYAIABhAGQAZAByAGUAcwBz
AGUAcwAgAGgAYQB2AGUAIABiAGUAZQBuACAAaQBuAHQAcgBvAGQAdQBjAGUAZAAgAHcAaABlAHIA
ZQAgAHQAaABlAA0ACgAgACAAIAAgACAAIABpAG4AdABlAHIAZgBhAGMAZQAgAGkAZABlAG4AdABp
AGYAaQBlAHIAcwAgAGEAcgBlACAAbgBvAHQAIABuAGUAYwBlAHMAcwBhAHIAaQBsAHkAIAB0AGgA
ZQAgAHMAYQBtAGUAIABmAG8AcgAgAGEAbABsACAAdQBuAGkAYwBhAHMAdAANAAoAIAAgACAAIAAg
ACAAYQBkAGQAcgBlAHMAcwBlAHMAIABvAG4AIABhACAAcwBpAG4AZwBsAGUAIABpAG4AdABlAHIA
ZgBhAGMAZQAgAFsAUgBGAEMAMwAwADQAMQBdACAAWwBSAEYAQwAzADkANwAyAF0ALgAgACAAUgBl
AHEAdQBpAHIAaQBuAGcAIAB0AG8ADQAKACAAIAAgACAAIAAgAHAAZQByAGYAbwByAG0AIABEAHUA
cABsAGkAYwBhAHQAZQAgAEEAZABkAHIAZQBzAHMAIABEAGUAdABlAGMAdABpAG8AbgAgAGYAbwBy
ACAAYQBsAGwAIAB1AG4AaQBjAGEAcwB0ACAAYQBkAGQAcgBlAHMAcwBlAHMAIAB3AGkAbABsAA0A
CgAgACAAIAAgACAAIABtAGEAawBlACAAdABoAGUAIABhAGwAZwBvAHIAaQB0AGgAbQAgAHIAbwBi
AHUAcwB0ACAAZgBvAHIAIAB0AGgAZQAgAGMAdQByAHIAZQBuAHQAIABhAG4AZAAgAGYAdQB0AHUA
cgBlACAAcwB1AGMAaAAgAHMAcABlAGMAaQBhAGwADQAKAA0ACgANAAoADQAKAFMAaQBuAGcAaAAg
ACYAIABCAGUAZQBiAGUAZQAgACAAIAAgACAAIAAgACAAIAAgAEUAeABwAGkAcgBlAHMAIABEAGUA
YwBlAG0AYgBlAHIAIAAyADMALAAgADIAMAAwADcAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAWwBQAGEAZwBlACAAOABdAA0ACgAMAA0ACgBJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQA
IAAgACAAIAAgACAAIAAgACAATgBEACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACAAUABp
AHQAZgBhAGwAbABzACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABKAHUAbgBlACAAMgAwADAA
NwANAAoADQAKAA0ACgAgACAAIAAgACAAIABpAG4AdABlAHIAZgBhAGMAZQAgAGkAZABlAG4AdABp
AGYAaQBlAHIAcwAuACIADQAKAA0ACgAgACAAIAB0AG8AIAByAGUAYQBkACAAYQBzACAAZgBvAGwA
bABvAHcAcwA6AA0ACgANAAoAIAAgACAAIAAgACAARQBhAGMAaAAgAGkAbgBkAGkAdgBpAGQAdQBh
AGwAIAB1AG4AaQBjAGEAcwB0ACAAYQBkAGQAcgBlAHMAcwAgAE0AVQBTAFQAIABiAGUAIAB0AGUA
cwB0AGUAZAAgAGYAbwByACAAdQBuAGkAcQB1AGUAbgBlAHMAcwAuAA0ACgAgACAAIAAgACAAIABO
AG8AdABlACAAdABoAGEAdAAgAHMAbwBtAGUAIABkAGUAcABsAG8AeQBlAGQAIABpAG0AcABsAGUA
bQBlAG4AdABhAHQAaQBvAG4AcwAgAHAAZQByAGYAbwByAG0AIABEAHUAcABsAGkAYwBhAHQAZQAg
AEEAZABkAHIAZQBzAHMADQAKACAAIAAgACAAIAAgAEQAZQB0AGUAYwB0AGkAbwBuACAAKABEAEEA
RAApACAAbwBuAGwAeQAgAGYAbwByACAAdABoAGUAIABsAGkAbgBrAC0AbABvAGMAYQBsACAAYQBk
AGQAcgBlAHMAcwAgAGEAbgBkACAAcwBrAGkAcAAgAHQAaABlACAAdABlAHMAdAANAAoAIAAgACAA
IAAgACAAZgBvAHIAIAB0AGgAZQAgAGcAbABvAGIAYQBsACAAYQBkAGQAcgBlAHMAcwAgAHUAcwBp
AG4AZwAgAHQAaABlACAAcwBhAG0AZQAgAGkAbgB0AGUAcgBmAGEAYwBlACAAaQBkAGUAbgB0AGkA
ZgBpAGUAcgAuACAAIABUAGgAaQBzAA0ACgAgACAAIAAgACAAIABvAHAAdABpAG0AaQB6AGEAdABp
AG8AbgAgAGMAYQBtAGUAIABmAHIAbwBtACAAdABoAGUAIABhAHMAcwB1AG0AcAB0AGkAbwBuACAA
dABoAGEAdAAgAGEAbABsACAAbwBmACAAYQBuACAAaQBuAHQAZQByAGYAYQBjAGUAJwBzAA0ACgAg
ACAAIAAgACAAIABhAGQAZAByAGUAcwBzAGUAcwAgAGEAcgBlACAAZwBlAG4AZQByAGEAdABlAGQA
IABmAHIAbwBtACAAdABoAGUAIABzAGEAbQBlACAAaQBuAHQAZQByAGYAYQBjAGUAIABpAGQAZQBu
AHQAaQBmAGkAZQByACAAKABzAGUAZQANAAoAIAAgACAAIAAgACAAUgBGAEMAIAAyADQANgAyACAA
WwBBAEQARABSAEMATwBOAEYAXQApAC4AIAAgAEgAbwB3AGUAdgBlAHIALAAgAGUAdgBlAG4AIAB3
AGkAdABoACAAdABoAGkAcwAgAGEAcwBzAHUAbQBwAHQAaQBvAG4ALAANAAoAIAAgACAAIAAgACAA
cwBrAGkAcABwAGkAbgBnACAARABBAEQAIABmAG8AcgAgAG4AbwBuAC0AbABpAG4AawAtAGwAbwBj
AGEAbAAgAGEAZABkAHIAZQBzAHMAZQBzACAAcgBlAHAAcgBlAHMAZQBuAHQAcwAgAGEAIABzAGUA
YwB1AHIAaQB0AHkADQAKACAAIAAgACAAIAAgAHAAcgBvAGIAbABlAG0ALgAgACAAVABoAGkAcwAg
AG8AcAB0AGkAbQBpAHoAYQB0AGkAbwBuACAAYQBsAGwAbwB3AHMAIABhAG4AIABpAG4AdABlAHIA
ZgBhAGMAZQAgAHQAbwAgAGMAbABhAGkAbQAgAGEADQAKACAAIAAgACAAIAAgAGQAdQBwAGwAaQBj
AGEAdABlACAAYQBkAGQAcgBlAHMAcwAgAGkAbgAgAGEAIAB3AGEAeQAgAHQAaABhAHQAIAB3AG8A
dQBsAGQAIABuAG8AdAAgAGIAZQAgAGQAZQB0AGUAYwB0AGUAZAAuACAAIABGAG8AcgAgAGEAIABt
AG8AcgBlAA0ACgAgACAAIAAgACAAIABkAGUAdABhAGkAbABlAGQAIABkAGUAcwBjAHIAaQBwAHQA
aQBvAG4AIABvAGYAIAB0AGgAaQBzACAAcwBlAGMAdQByAGkAdAB5ACAAcAByAG8AYgBsAGUAbQAs
ACAAcwBlAGUAIAB0AGgAZQAgAEgAbwBzAHQAIABNAG8AZABlAGwAcwANAAoAIAAgACAAIAAgACAA
cwBlAGMAdABpAG8AbgAgAG8AZgAgAGQAcgBhAGYAdAAtAHcAYgBlAGUAYgBlAGUALQBuAGQALQBp
AG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4ALQBwAGkAdABmAGEAbABsAHMALQAwADAALgAgACAA
RgB1AHIAdABoAGUAcgAsAA0ACgAgACAAIAAgACAAIABuAGUAdwAgAHQAeQBwAGUAcwAgAG8AZgAg
AGEAZABkAHIAZQBzAHMAZQBzACAAaABhAHYAZQAgAGIAZQBlAG4AIABpAG4AdAByAG8AZAB1AGMA
ZQBkACAAdwBoAGUAcgBlACAAdABoAGUAIABpAG4AdABlAHIAZgBhAGMAZQANAAoAIAAgACAAIAAg
ACAAaQBkAGUAbgB0AGkAZgBpAGUAcgBzACAAYQByAGUAIABuAG8AdAAgAG4AZQBjAGUAcwBzAGEA
cgBpAGwAeQAgAHQAaABlACAAcwBhAG0AZQAgAGYAbwByACAAYQBsAGwAIAB1AG4AaQBjAGEAcwB0
ACAAYQBkAGQAcgBlAHMAcwBlAHMADQAKACAAIAAgACAAIAAgAG8AbgAgAGEAIABzAGkAbgBnAGwA
ZQAgAGkAbgB0AGUAcgBmAGEAYwBlACAAWwBSAEYAQwAzADAANAAxAF0AIABbAFIARgBDADMAOQA3
ADIAXQAuACAAIABSAGUAcQB1AGkAcgBpAG4AZwAgAGEAbgAgAGkAbgB0AGUAcgBmAGEAYwBlAA0A
CgAgACAAIAAgACAAIAB0AG8AIABwAGUAcgBmAG8AcgBtACAARABBAEQAIABmAG8AcgAgAGEAbABs
ACAAdQBuAGkAYwBhAHMAdAAgAGEAZABkAHIAZQBzAHMAZQBzACAAdwBpAGwAbAAgAG0AYQBrAGUA
IAB0AGgAZQAgAGEAbABnAG8AcgBpAHQAaABtAA0ACgAgACAAIAAgACAAIABtAG8AcgBlACAAcgBv
AGIAdQBzAHQALgAgACAARQB4AGkAcwB0AGkAbgBnACAAaQBtAHAAbABlAG0AZQBuAHQAYQB0AGkA
bwBuAHMAIABhAHMAIAB3AGUAbABsACAAYQBzACAAbgBlAHcADQAKACAAIAAgACAAIAAgAGkAbQBw
AGwAZQBtAGUAbgB0AGEAdABpAG8AbgBzACAATQBVAFMAVAAgAHQAZQBzAHQAIABlAGEAYwBoACAA
aQBuAGQAaQB2AGkAZAB1AGEAbAAgAHUAbgBpAGMAYQBzAHQAIABhAGQAZAByAGUAcwBzACAAZgBv
AHIADQAKACAAIAAgACAAIAAgAHUAbgBpAHEAdQBlAG4AZQBzAHMALgANAAoADQAKAA0ACgA2AC4A
IAAgAFMAZQBjAHUAcgBpAHQAeQAgAEMAbwBuAHMAaQBkAGUAcgBhAHQAaQBvAG4AcwANAAoADQAK
ACAAIAAgAFQAaABlACAASABvAHMAdAAgAE0AbwBkAGUAbABzACAAcwBlAGMAdABpAG8AbgAgAG8A
ZgAgAHQAaABpAHMAIABkAG8AYwB1AG0AZQBuAHQAIABkAGUAcwBjAHIAaQBiAGUAcwAgAHYAYQBs
AGkAZAAgAGgAbwBzAHQADQAKACAAIAAgAGIAZQBoAGEAdgBpAG8AcgAgAGkAbgAgAHIAZQBzAHAA
bwBuAHMAZQAgAHQAbwAgAGEAIABzAGUAYwB1AHIAaQB0AHkAIAB0AGgAcgBlAGEAdAAgAHcAaABl
AHIAZQAgAGEAIAByAG8AZwB1AGUAIABuAG8AZABlACAAYwBhAG4AIABzAGUAbgBkAA0ACgAgACAA
IABSAEEAcwAgAHcAaQB0AGgAIABhACAAVgBhAGwAaQBkACAATABpAGYAZQB0AGkAbQBlACAAbwBm
ACAAegBlAHIAbwAuACAAIABIAG8AcwB0ACAATQBvAGQAZQBsAHMAIABhAGwAcwBvACAAZABlAHMA
YwByAGkAYgBlAHMAIABhAA0ACgAgACAAIABzAGUAYwB1AHIAaQB0AHkAIABwAHIAbwBiAGwAZQBt
ACAAdwBpAHQAaAAgAHMAZQBjAHQAaQBvAG4AIAA1AC4ANAAgAG8AZgAgAFIARgBDACAAMgA0ADYA
MgAgAFsAQQBEAEQAUgBDAE8ATgBGAF0AIAB0AGgAYQB0ACAAYwBhAG4ADQAKACAAIAAgAGEAbABs
AG8AdwAgAHQAdwBvACAAaABvAHMAdABzACAAdwBpAHQAaAAgAHQAaABlACAAcwBhAG0AZQAgAGEA
ZABkAHIAZQBzAHMAIAB0AG8AIABhAHYAbwBpAGQAIABEAEEARAAgAGEAbgBkACAAYwBvAG0AZQAg
AG8AbgBsAGkAbgBlACAAbwBuAA0ACgAgACAAIAB0AGgAZQAgAHMAYQBtAGUAIABsAGkAbgBrAC4A
DQAKAA0ACgANAAoANwAuACAAIABJAEEATgBBACAAQwBvAG4AcwBpAGQAZQByAGEAdABpAG8AbgBz
AA0ACgANAAoAIAAgACAATgBvAG4AZQAuAA0ACgANAAoADQAKADgALgAgACAAQQBjAGsAbgBvAHcA
bABlAGQAZwBlAG0AZQBuAHQAcwANAAoADQAKACAAIAAgAFQAaABhAG4AawBzACAAKABpAG4AIABh
AGwAcABoAGEAYgBlAHQAaQBjAGEAbAAgAG8AcgBkAGUAcgApACAAdABvACAAQQBkAGUAZQBsACAA
QQBoAG0AZQBkACwAIABBAGwAdQBuACAARQB2AGEAbgBzACwAIABCAGUAcgBuAGkAZQANAAoAIAAg
ACAAVgBvAGwAegAsACAARABhAHYAZQAgAEYAbwByAHMAdABlAHIALAAgAE0AYQBkAGgAdQAgAFMA
dQBkAGEAbgAsACAAUAByAGEAcwBoAGEAbgB0AGgAIABLAHIAaQBzAGgAbgBhAG0AdQByAHQAaAB5
ACwAIABhAG4AZAAgAFIAYQBsAHAAaAANAAoAIAAgACAARAByAG8AbQBzACAAbwBmACAAQwBpAHMA
YwBvACwAIABmAG8AcgAgAHQAaABlAGkAcgAgAGMAbwBuAHMAaQBzAHQAZQBuAHQAIABpAG4AcAB1
AHQALAAgAGkAZABlAGEAcwAgAGEAbgBkACAAcgBlAHYAaQBlAHcAIABkAHUAcgBpAG4AZwANAAoA
IAAgACAAdABoAGUAIABwAHIAbwBkAHUAYwB0AGkAbwBuACAAbwBmACAAdABoAGkAcwAgAGQAbwBj
AHUAbQBlAG4AdAAuAA0ACgANAAoADQAKAA0ACgANAAoADQAKAFMAaQBuAGcAaAAgACYAIABCAGUA
ZQBiAGUAZQAgACAAIAAgACAAIAAgACAAIAAgAEUAeABwAGkAcgBlAHMAIABEAGUAYwBlAG0AYgBl
AHIAIAAyADMALAAgADIAMAAwADcAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEA
ZwBlACAAOQBdAA0ACgAMAA0ACgBJAG4AdABlAHIAbgBlAHQALQBEAHIAYQBmAHQAIAAgACAAIAAg
ACAAIAAgACAATgBEACAASQBtAHAAbABlAG0AZQBuAHQAYQB0AGkAbwBuACAAUABpAHQAZgBhAGwA
bABzACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABKAHUAbgBlACAAMgAwADAANwANAAoADQAK
AA0ACgA5AC4AIAAgAFIAZQBmAGUAcgBlAG4AYwBlAHMADQAKAA0ACgA5AC4AMQAuACAAIABOAG8A
cgBtAGEAdABpAHYAZQAgAFIAZQBmAGUAcgBlAG4AYwBlAHMADQAKAA0ACgAgACAAIABbAEEARABE
AFIAQwBPAE4ARgBdAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAVABoAG8AbQBzAG8A
bgAsACAAUwAuACAAYQBuAGQAIABUAC4AIABOAGEAcgB0AGUAbgAsACAAIgBJAFAAdgA2ACAAQQBk
AGQAcgBlAHMAcwAgAGEAdQB0AG8AYwBvAG4AZgBpAGcAdQByAGEAdABpAG8AbgANAAoAIAAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACgASQBQAHYANgApACIALAAgAFIARgBDACAAMgA0ADYAMgAs
ACAARABlAGMAZQBtAGIAZQByACAAMQA5ADkAOAAuAA0ACgANAAoAIAAgACAAWwBOAEQAXQAgACAA
IAAgACAAIAAgAE4AYQByAHQAZQBuACwAIABUAC4ALAAgAE4AbwByAGQAbQBhAHIAawAsACAARQAu
ACwAIABhAG4AZAAgAFcALgAgAFMAaQBtAHAAcwBvAG4ALAAgACIATgBlAGkAZwBoAGIAbwByAA0A
CgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAARABpAHMAYwBvAHYAZQByAHkAIABmAG8AcgAg
AEkAUAAgAFYAZQByAHMAaQBvAG4AIAA2ACAAKABJAFAAdgA2ACkAIgAsACAAUgBGAEMAIAAyADQA
NgAxACwADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABEAGUAYwBlAG0AYgBlAHIAIAAx
ADkAOQA4AC4ADQAKAA0ACgA5AC4AMgAuACAAIABJAG4AZgBvAHIAbQBhAHQAaQB2AGUAIABSAGUA
ZgBlAHIAZQBuAGMAZQBzAA0ACgANAAoAIAAgACAAWwBBAEQARABSAEMATwBOAEYAYgBpAHMAXQAN
AAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAFQAaABvAG0AcwBvAG4ALAAgAFMALgAsACAA
TgBhAHIAdABlAG4ALAAgAFQALgAsACAAYQBuAGQAIABUAC4AIABKAGkAbgBtAGUAaQAsACAAIgBJ
AFAAdgA2ACAAQQBkAGQAcgBlAHMAcwANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAGEA
dQB0AG8AYwBvAG4AZgBpAGcAdQByAGEAdABpAG8AbgAgACgASQBQAHYANgApACIALAANAAoAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAAIAAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBpAHAAdgA2AC0A
cgBmAGMAMgA0ADYAMgBiAGkAcwAtADAAOAAgACgAVwBvAHIAawAgAEkAbgAgAFAAcgBvAGcAcgBl
AHMAcwApACwADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABNAGEAeQAgADIAMAAwADUA
LgANAAoADQAKACAAIAAgAFsASQAuAEQALgBpAGUAdABmAC0AdgA2AG8AcABzAC0AbwBuAGwAaQBu
AGsAYQBzAHMAdQBtAHAAdABpAG8AbgBzAF0ADQAKACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAA
IABSAG8AeQAsACAAUwAuACwAIABEAHUAcgBhAG4AZAAsACAAQQAuACwAIABhAG4AZAAgAEoALgAg
AFAAYQB1AGcAaAAsACAAIgBJAFAAdgA2ACAATgBlAGkAZwBoAGIAbwByAA0ACgAgACAAIAAgACAA
IAAgACAAIAAgACAAIAAgACAARABpAHMAYwBvAHYAZQByAHkAIABPAG4ALQBMAGkAbgBrACAAQQBz
AHMAdQBtAHAAdABpAG8AbgAgAEMAbwBuAHMAaQBkAGUAcgBlAGQAIABIAGEAcgBtAGYAdQBsACAA
KABJAFAAdgA2ACkAIgAsAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAZAByAGEAZgB0
AC0AaQBlAHQAZgAtAHYANgBvAHAAcwAtAG8AbgBsAGkAbgBrAGEAcwBzAHUAbQBwAHQAaQBvAG4A
LQAwADQAIAAoAFcAbwByAGsAIABJAG4AIABQAHIAbwBnAHIAZQBzAHMAKQAsAA0ACgAgACAAIAAg
ACAAIAAgACAAIAAgACAAIAAgACAASgBhAG4AdQBhAHIAeQAgADIAMAAwADcALgANAAoADQAKACAA
IAAgAFsATgBEAGIAaQBzAF0AIAAgACAAIABOAGEAcgB0AGUAbgAsACAAVAAuACwAIABOAG8AcgBk
AG0AYQByAGsALAAgAEUALgAsACAAUwBpAG0AcABzAG8AbgAsACAAVwAuACwAIABhAG4AZAAgAEgA
LgAgAFMAbwBsAGkAbQBhAG4ALAANAAoAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACIATgBl
AGkAZwBoAGIAbwByACAARABpAHMAYwBvAHYAZQByAHkAIABmAG8AcgAgAEkAUAAgAFYAZQByAHMA
aQBvAG4AIAA2ACAAKABJAFAAdgA2ACkAIgAsAA0ACgAgACAAIAAgACAAIAAgACAAIAAgACAAIAAg
ACAAZAByAGEAZgB0AC0AaQBlAHQAZgAtAGkAcAB2ADYALQAyADQANgAxAGIAaQBzAC0AMQAxACAA
KABXAG8AcgBrACAASQBuACAAUAByAG8AZwByAGUAcwBzACkALAAgAE0AYQByAGMAaAAgADIAMAAw
ADcALgANAAoADQAKAA0ACgBBAHUAdABoAG8AcgBzACcAIABBAGQAZAByAGUAcwBzAGUAcwANAAoA
DQAKACAAIAAgAEgAZQBtAGEAbgB0ACAAUwBpAG4AZwBoAA0ACgAgACAAIABDAGkAcwBjAG8AIABT
AHkAcwB0AGUAbQBzACwAIABJAG4AYwAuAA0ACgAgACAAIAAxADQAMQA0ACAATQBhAHMAcwBhAGMA
aAB1AHMAZQB0AHQAcwAgAEEAdgBlAC4ADQAKACAAIAAgAEIAbwB4AGIAbwByAG8AdQBnAGgALAAg
AE0AQQAgACAAMAAxADcAMQA5AA0ACgAgACAAIABVAFMAQQANAAoADQAKACAAIAAgAFAAaABvAG4A
ZQA6ACAAKwAxACAAOQA3ADgAIAA5ADMANgAgADEANgAyADIADQAKACAAIAAgAEUAbQBhAGkAbAA6
ACAAcwBoAGUAbQBhAG4AdABAAGMAaQBzAGMAbwAuAGMAbwBtAA0ACgAgACAAIABVAFIASQA6ACAA
IAAgAGgAdAB0AHAAOgAvAC8AdwB3AHcALgBjAGkAcwBjAG8ALgBjAG8AbQAvAA0ACgANAAoADQAK
AA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgBTAGkAbgBnAGgAIAAmACAAQgBlAGUAYgBlAGUA
IAAgACAAIAAgACAAIAAgACAAIABFAHgAcABpAHIAZQBzACAARABlAGMAZQBtAGIAZQByACAAMgAz
ACwAIAAyADAAMAA3ACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIABbAFAAYQBnAGUAIAAxADAA
XQANAAoADAANAAoASQBuAHQAZQByAG4AZQB0AC0ARAByAGEAZgB0ACAAIAAgACAAIAAgACAAIAAg
AE4ARAAgAEkAbQBwAGwAZQBtAGUAbgB0AGEAdABpAG8AbgAgAFAAaQB0AGYAYQBsAGwAcwAgACAA
IAAgACAAIAAgACAAIAAgACAAIAAgACAASgB1AG4AZQAgADIAMAAwADcADQAKAA0ACgANAAoAIAAg
ACAAVwBlAHMAIABCAGUAZQBiAGUAZQANAAoAIAAgACAAQwBpAHMAYwBvACAAUwB5AHMAdABlAG0A
cwAsACAASQBuAGMALgANAAoAIAAgACAAMQA0ADEANAAgAE0AYQBzAHMAYQBjAGgAdQBzAGUAdAB0
AHMAIABBAHYAZQAuAA0ACgAgACAAIABCAG8AeABiAG8AcgBvAHUAZwBoACwAIABNAEEAIAAgADAA
MQA3ADEAOQANAAoAIAAgACAAVQBTAEEADQAKAA0ACgAgACAAIABQAGgAbwBuAGUAOgAgACsAMQAg
ADkANwA4ACAAOQAzADYAIAAyADAAMwAwAA0ACgAgACAAIABFAG0AYQBpAGwAOgAgAHcAYgBlAGUA
YgBlAGUAQABjAGkAcwBjAG8ALgBjAG8AbQANAAoAIAAgACAAVQBSAEkAOgAgACAAIABoAHQAdABw
ADoALwAvAHcAdwB3AC4AYwBpAHMAYwBvAC4AYwBvAG0ALwANAAoADQAKAA0ACgANAAoADQAKAA0A
CgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAK
AA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoA
DQAKAA0ACgANAAoADQAKAA0ACgANAAoADQAKAA0ACgANAAoAUwBpAG4AZwBoACAAJgAgAEIAZQBl
AGIAZQBlACAAIAAgACAAIAAgACAAIAAgACAARQB4AHAAaQByAGUAcwAgAEQAZQBjAGUAbQBiAGUA
cgAgADIAMwAsACAAMgAwADAANwAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgACAAWwBQAGEAZwBl
ACAAMQAxAF0ADQAKAAwADQAKAEkAbgB0AGUAcgBuAGUAdAAtAEQAcgBhAGYAdAAgACAAIAAgACAA
IAAgACAAIABOAEQAIABJAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AIABQAGkAdABmAGEAbABs
AHMAIAAgACAAIAAgACAAIAAgACAAIAAgACAAIAAgAEoAdQBuAGUAIAAyADAAMAA3AA0ACgANAAoA
DQAKAEYAdQBsAGwAIABDAG8AcAB5AHIAaQBnAGgAdAAgAFMAdABhAHQAZQBtAGUAbgB0AA0ACgAN
AAoAIAAgACAAQwBvAHAAeQByAGkAZwBoAHQAIAAoAEMAKQAgAFQAaABlACAASQBFAFQARgAgAFQA
cgB1AHMAdAAgACgAMgAwADAANwApAC4ADQAKAA0ACgAgACAAIABUAGgAaQBzACAAZABvAGMAdQBt
AGUAbgB0ACAAaQBzACAAcwB1AGIAagBlAGMAdAAgAHQAbwAgAHQAaABlACAAcgBpAGcAaAB0AHMA
LAAgAGwAaQBjAGUAbgBzAGUAcwAgAGEAbgBkACAAcgBlAHMAdAByAGkAYwB0AGkAbwBuAHMADQAK
ACAAIAAgAGMAbwBuAHQAYQBpAG4AZQBkACAAaQBuACAAQgBDAFAAIAA3ADgALAAgAGEAbgBkACAA
ZQB4AGMAZQBwAHQAIABhAHMAIABzAGUAdAAgAGYAbwByAHQAaAAgAHQAaABlAHIAZQBpAG4ALAAg
AHQAaABlACAAYQB1AHQAaABvAHIAcwANAAoAIAAgACAAcgBlAHQAYQBpAG4AIABhAGwAbAAgAHQA
aABlAGkAcgAgAHIAaQBnAGgAdABzAC4ADQAKAA0ACgAgACAAIABUAGgAaQBzACAAZABvAGMAdQBt
AGUAbgB0ACAAYQBuAGQAIAB0AGgAZQAgAGkAbgBmAG8AcgBtAGEAdABpAG8AbgAgAGMAbwBuAHQA
YQBpAG4AZQBkACAAaABlAHIAZQBpAG4AIABhAHIAZQAgAHAAcgBvAHYAaQBkAGUAZAAgAG8AbgAg
AGEAbgANAAoAIAAgACAAIgBBAFMAIABJAFMAIgAgAGIAYQBzAGkAcwAgAGEAbgBkACAAVABIAEUA
IABDAE8ATgBUAFIASQBCAFUAVABPAFIALAAgAFQASABFACAATwBSAEcAQQBOAEkAWgBBAFQASQBP
AE4AIABIAEUALwBTAEgARQAgAFIARQBQAFIARQBTAEUATgBUAFMADQAKACAAIAAgAE8AUgAgAEkA
UwAgAFMAUABPAE4AUwBPAFIARQBEACAAQgBZACAAKABJAEYAIABBAE4AWQApACwAIABUAEgARQAg
AEkATgBUAEUAUgBOAEUAVAAgAFMATwBDAEkARQBUAFkALAAgAFQASABFACAASQBFAFQARgAgAFQA
UgBVAFMAVAAgAEEATgBEAA0ACgAgACAAIABUAEgARQAgAEkATgBUAEUAUgBOAEUAVAAgAEUATgBH
AEkATgBFAEUAUgBJAE4ARwAgAFQAQQBTAEsAIABGAE8AUgBDAEUAIABEAEkAUwBDAEwAQQBJAE0A
IABBAEwATAAgAFcAQQBSAFIAQQBOAFQASQBFAFMALAAgAEUAWABQAFIARQBTAFMADQAKACAAIAAg
AE8AUgAgAEkATQBQAEwASQBFAEQALAAgAEkATgBDAEwAVQBEAEkATgBHACAAQgBVAFQAIABOAE8A
VAAgAEwASQBNAEkAVABFAEQAIABUAE8AIABBAE4AWQAgAFcAQQBSAFIAQQBOAFQAWQAgAFQASABB
AFQAIABUAEgARQAgAFUAUwBFACAATwBGAA0ACgAgACAAIABUAEgARQAgAEkATgBGAE8AUgBNAEEA
VABJAE8ATgAgAEgARQBSAEUASQBOACAAVwBJAEwATAAgAE4ATwBUACAASQBOAEYAUgBJAE4ARwBF
ACAAQQBOAFkAIABSAEkARwBIAFQAUwAgAE8AUgAgAEEATgBZACAASQBNAFAATABJAEUARAANAAoA
IAAgACAAVwBBAFIAUgBBAE4AVABJAEUAUwAgAE8ARgAgAE0ARQBSAEMASABBAE4AVABBAEIASQBM
AEkAVABZACAATwBSACAARgBJAFQATgBFAFMAUwAgAEYATwBSACAAQQAgAFAAQQBSAFQASQBDAFUA
TABBAFIAIABQAFUAUgBQAE8AUwBFAC4ADQAKAA0ACgANAAoASQBuAHQAZQBsAGwAZQBjAHQAdQBh
AGwAIABQAHIAbwBwAGUAcgB0AHkADQAKAA0ACgAgACAAIABUAGgAZQAgAEkARQBUAEYAIAB0AGEA
awBlAHMAIABuAG8AIABwAG8AcwBpAHQAaQBvAG4AIAByAGUAZwBhAHIAZABpAG4AZwAgAHQAaABl
ACAAdgBhAGwAaQBkAGkAdAB5ACAAbwByACAAcwBjAG8AcABlACAAbwBmACAAYQBuAHkADQAKACAA
IAAgAEkAbgB0AGUAbABsAGUAYwB0AHUAYQBsACAAUAByAG8AcABlAHIAdAB5ACAAUgBpAGcAaAB0
AHMAIABvAHIAIABvAHQAaABlAHIAIAByAGkAZwBoAHQAcwAgAHQAaABhAHQAIABtAGkAZwBoAHQA
IABiAGUAIABjAGwAYQBpAG0AZQBkACAAdABvAA0ACgAgACAAIABwAGUAcgB0AGEAaQBuACAAdABv
ACAAdABoAGUAIABpAG0AcABsAGUAbQBlAG4AdABhAHQAaQBvAG4AIABvAHIAIAB1AHMAZQAgAG8A
ZgAgAHQAaABlACAAdABlAGMAaABuAG8AbABvAGcAeQAgAGQAZQBzAGMAcgBpAGIAZQBkACAAaQBu
AA0ACgAgACAAIAB0AGgAaQBzACAAZABvAGMAdQBtAGUAbgB0ACAAbwByACAAdABoAGUAIABlAHgA
dABlAG4AdAAgAHQAbwAgAHcAaABpAGMAaAAgAGEAbgB5ACAAbABpAGMAZQBuAHMAZQAgAHUAbgBk
AGUAcgAgAHMAdQBjAGgAIAByAGkAZwBoAHQAcwANAAoAIAAgACAAbQBpAGcAaAB0ACAAbwByACAA
bQBpAGcAaAB0ACAAbgBvAHQAIABiAGUAIABhAHYAYQBpAGwAYQBiAGwAZQA7ACAAbgBvAHIAIABk
AG8AZQBzACAAaQB0ACAAcgBlAHAAcgBlAHMAZQBuAHQAIAB0AGgAYQB0ACAAaQB0ACAAaABhAHMA
DQAKACAAIAAgAG0AYQBkAGUAIABhAG4AeQAgAGkAbgBkAGUAcABlAG4AZABlAG4AdAAgAGUAZgBm
AG8AcgB0ACAAdABvACAAaQBkAGUAbgB0AGkAZgB5ACAAYQBuAHkAIABzAHUAYwBoACAAcgBpAGcA
aAB0AHMALgAgACAASQBuAGYAbwByAG0AYQB0AGkAbwBuAA0ACgAgACAAIABvAG4AIAB0AGgAZQAg
AHAAcgBvAGMAZQBkAHUAcgBlAHMAIAB3AGkAdABoACAAcgBlAHMAcABlAGMAdAAgAHQAbwAgAHIA
aQBnAGgAdABzACAAaQBuACAAUgBGAEMAIABkAG8AYwB1AG0AZQBuAHQAcwAgAGMAYQBuACAAYgBl
AA0ACgAgACAAIABmAG8AdQBuAGQAIABpAG4AIABCAEMAUAAgADcAOAAgAGEAbgBkACAAQgBDAFAA
IAA3ADkALgANAAoADQAKACAAIAAgAEMAbwBwAGkAZQBzACAAbwBmACAASQBQAFIAIABkAGkAcwBj
AGwAbwBzAHUAcgBlAHMAIABtAGEAZABlACAAdABvACAAdABoAGUAIABJAEUAVABGACAAUwBlAGMA
cgBlAHQAYQByAGkAYQB0ACAAYQBuAGQAIABhAG4AeQANAAoAIAAgACAAYQBzAHMAdQByAGEAbgBj
AGUAcwAgAG8AZgAgAGwAaQBjAGUAbgBzAGUAcwAgAHQAbwAgAGIAZQAgAG0AYQBkAGUAIABhAHYA
YQBpAGwAYQBiAGwAZQAsACAAbwByACAAdABoAGUAIAByAGUAcwB1AGwAdAAgAG8AZgAgAGEAbgAN
AAoAIAAgACAAYQB0AHQAZQBtAHAAdAAgAG0AYQBkAGUAIAB0AG8AIABvAGIAdABhAGkAbgAgAGEA
IABnAGUAbgBlAHIAYQBsACAAbABpAGMAZQBuAHMAZQAgAG8AcgAgAHAAZQByAG0AaQBzAHMAaQBv
AG4AIABmAG8AcgAgAHQAaABlACAAdQBzAGUAIABvAGYADQAKACAAIAAgAHMAdQBjAGgAIABwAHIA
bwBwAHIAaQBlAHQAYQByAHkAIAByAGkAZwBoAHQAcwAgAGIAeQAgAGkAbQBwAGwAZQBtAGUAbgB0
AGUAcgBzACAAbwByACAAdQBzAGUAcgBzACAAbwBmACAAdABoAGkAcwANAAoAIAAgACAAcwBwAGUA
YwBpAGYAaQBjAGEAdABpAG8AbgAgAGMAYQBuACAAYgBlACAAbwBiAHQAYQBpAG4AZQBkACAAZgBy
AG8AbQAgAHQAaABlACAASQBFAFQARgAgAG8AbgAtAGwAaQBuAGUAIABJAFAAUgAgAHIAZQBwAG8A
cwBpAHQAbwByAHkAIABhAHQADQAKACAAIAAgAGgAdAB0AHAAOgAvAC8AdwB3AHcALgBpAGUAdABm
AC4AbwByAGcALwBpAHAAcgAuAA0ACgANAAoAIAAgACAAVABoAGUAIABJAEUAVABGACAAaQBuAHYA
aQB0AGUAcwAgAGEAbgB5ACAAaQBuAHQAZQByAGUAcwB0AGUAZAAgAHAAYQByAHQAeQAgAHQAbwAg
AGIAcgBpAG4AZwAgAHQAbwAgAGkAdABzACAAYQB0AHQAZQBuAHQAaQBvAG4AIABhAG4AeQANAAoA
IAAgACAAYwBvAHAAeQByAGkAZwBoAHQAcwAsACAAcABhAHQAZQBuAHQAcwAgAG8AcgAgAHAAYQB0
AGUAbgB0ACAAYQBwAHAAbABpAGMAYQB0AGkAbwBuAHMALAAgAG8AcgAgAG8AdABoAGUAcgAgAHAA
cgBvAHAAcgBpAGUAdABhAHIAeQANAAoAIAAgACAAcgBpAGcAaAB0AHMAIAB0AGgAYQB0ACAAbQBh
AHkAIABjAG8AdgBlAHIAIAB0AGUAYwBoAG4AbwBsAG8AZwB5ACAAdABoAGEAdAAgAG0AYQB5ACAA
YgBlACAAcgBlAHEAdQBpAHIAZQBkACAAdABvACAAaQBtAHAAbABlAG0AZQBuAHQADQAKACAAIAAg
AHQAaABpAHMAIABzAHQAYQBuAGQAYQByAGQALgAgACAAUABsAGUAYQBzAGUAIABhAGQAZAByAGUA
cwBzACAAdABoAGUAIABpAG4AZgBvAHIAbQBhAHQAaQBvAG4AIAB0AG8AIAB0AGgAZQAgAEkARQBU
AEYAIABhAHQADQAKACAAIAAgAGkAZQB0AGYALQBpAHAAcgBAAGkAZQB0AGYALgBvAHIAZwAuAA0A
CgANAAoADQAKAEEAYwBrAG4AbwB3AGwAZQBkAGcAbQBlAG4AdAANAAoADQAKACAAIAAgAEYAdQBu
AGQAaQBuAGcAIABmAG8AcgAgAHQAaABlACAAUgBGAEMAIABFAGQAaQB0AG8AcgAgAGYAdQBuAGMA
dABpAG8AbgAgAGkAcwAgAHAAcgBvAHYAaQBkAGUAZAAgAGIAeQAgAHQAaABlACAASQBFAFQARgAN
AAoAIAAgACAAQQBkAG0AaQBuAGkAcwB0AHIAYQB0AGkAdgBlACAAUwB1AHAAcABvAHIAdAAgAEEA
YwB0AGkAdgBpAHQAeQAgACgASQBBAFMAQQApAC4ADQAKAA0ACgANAAoADQAKAA0ACgANAAoAUwBp
AG4AZwBoACAAJgAgAEIAZQBlAGIAZQBlACAAIAAgACAAIAAgACAAIAAgACAARQB4AHAAaQByAGUA
cwAgAEQAZQBjAGUAbQBiAGUAcgAgADIAMwAsACAAMgAwADAANwAgACAAIAAgACAAIAAgACAAIAAg
ACAAIAAgACAAWwBQAGEAZwBlACAAMQAyAF0ADQAKAAwADQAKAA0ACgA=

------_=_NextPart_001_01C7B421.B0D2AA56
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

------_=_NextPart_001_01C7B421.B0D2AA56--




From ipv6-bounces@ietf.org Thu Jun 21 12:36:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Pdb-00062X-FP; Thu, 21 Jun 2007 12:36:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1PdZ-00062P-VH
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:36:01 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1PdY-00022o-N5
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:36:01 -0400
Received: from auguste.remlab.net (unknown
	[IPv6:2002:3e4e:907a:0:20d:60ff:fe38:6d16])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id CF6979673B;
	Thu, 21 Jun 2007 18:35:59 +0200 (CEST)
From: =?windows-1252?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: "Hemant Singh \(shemant\)" <shemant@cisco.com>
Date: Thu, 21 Jun 2007 19:35:46 +0300
User-Agent: KMail/1.9.7
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
MIME-Version: 1.0
Message-Id: <200706211935.51549@auguste.remlab.net>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0675892731=="
Errors-To: ipv6-bounces@ietf.org

--===============0675892731==
Content-Type: multipart/signed; boundary="nextPart1951082.H3SbXE42Db";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1951082.H3SbXE42Db
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le jeudi 21 juin 2007, Hemant Singh (shemant) a =E9crit :
> Please see section 5 of our I-D for a proposed change to 2462bis-08 -
> we hear this I-D is
> in Editor's queue and any changes to it must be given ASAP.

Could you please use US-ASCII rather than UTF-16 for you I-D, as is=20
customary here?

Thanks in advance.

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/

--nextPart1951082.H3SbXE42Db
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iEYEABECAAYFAkZ6qOcACgkQw+xtvt1tEr0xbQCg04nlDLVSrMBcWL5WAmK8g2dd
70MAoO400zFUWoM/Qm7XMqWAlHAAUdOo
=Od6+
-----END PGP SIGNATURE-----

--nextPart1951082.H3SbXE42Db--


--===============0675892731==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0675892731==--




From ipv6-bounces@ietf.org Thu Jun 21 12:38:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1PgE-0001LM-P9; Thu, 21 Jun 2007 12:38:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1PgE-0001LH-4D
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:38:46 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1PgC-0002Yc-SM
	for ipv6@ietf.org; Thu, 21 Jun 2007 12:38:46 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 21 Jun 2007 12:38:44 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAL9GekZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,448,1175486400"; 
	d="scan'208"; a="124240319:sNHT40405080"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5LGcigZ011848; 
	Thu, 21 Jun 2007 12:38:44 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5LGchLp015128; 
	Thu, 21 Jun 2007 16:38:44 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 12:38:41 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 12:38:41 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03468C02@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <200706211935.51549@auguste.remlab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace0Ik9uPFqkvsU3T82ek4JmCGhEHQAAEVYw
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<200706211935.51549@auguste.remlab.net>
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
X-OriginalArrivalTime: 21 Jun 2007 16:38:41.0823 (UTC)
	FILETIME=[A083D2F0:01C7B422]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=757; t=1182443924;
	x=1183307924; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=3D?iso-8859-1?Q?R=3DE9mi_Denis-Courmont?=3D=20<rdenis@simphalempi
	n.com>; bh=spVTqVPQ1e7U4IyCo5s4cNiDNAsh9gEymaz9pnIxhMg=;
	b=KgDFkrgDZJM3v49C/fSVkHi9jT2NA5FuvqbuAaPFMYLBuVVeB/n5hIofaRKlZX1o/az5s4h7
	v9JxpCv3ACeFlFviZJ6//s/v5EdILHhEdV02eA8OPZFRZd38m7W0J1mc;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Will do, thanks for this tip. I will send out another copy soon.

Hemant=20

-----Original Message-----
From: R=E9mi Denis-Courmont [mailto:rdenis@simphalempin.com]=20
Sent: Thursday, June 21, 2007 12:36 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent =
changes suggested to 2462bis-08

Le jeudi 21 juin 2007, Hemant Singh (shemant) a =E9crit :
> Please see section 5 of our I-D for a proposed change to 2462bis-08 -=20
> we hear this I-D is in Editor's queue and any changes to it must be=20
> given ASAP.

Could you please use US-ASCII rather than UTF-16 for you I-D, as is =
customary here?

Thanks in advance.

--
R=E9mi Denis-Courmont
http://www.remlab.net/

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 12:49:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1PqB-0006Ka-RO; Thu, 21 Jun 2007 12:49:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1PqA-0006K6-FR; Thu, 21 Jun 2007 12:49:02 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1Pq7-00040V-5Y; Thu, 21 Jun 2007 12:49:02 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-5.cisco.com with ESMTP; 21 Jun 2007 09:48:58 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAGNIekarR7PEh2dsb2JhbAAUgk2MQwIJDiyPAQ
X-IronPort-AV: i="4.16,448,1175497200"; d="txt'?scan'208,217";
	a="163690621:sNHT114926733"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l5LGmwo2014817; 
	Thu, 21 Jun 2007 09:48:58 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5LGmknG023282;
	Thu, 21 Jun 2007 16:48:58 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 12:48:47 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7B424.08BAD842"
Date: Thu, 21 Jun 2007 12:48:45 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03468C15@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace0JAhrBQLxerNISYiWVoJwuPARXQ==
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: <ipv6@ietf.org>, <internet-drafts@ietf.org>
X-OriginalArrivalTime: 21 Jun 2007 16:48:47.0709 (UTC)
	FILETIME=[09A6B0D0:01C7B424]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=42853; t=1182444538;
	x=1183308538; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20urgent=2
	0changes=20suggested=20to=202462bis-08 |Sender:=20;
	bh=nmdG46lzc4VyAoTFIHJWkmV4lTdjE//VxmAhY4l6Lmc=;
	b=A/j6uEtQg4uFA3hP1DJYy8h0xR1TJNcV14gCtZmxvzTiSoHxFYzHzjD4aYOHiNl1pcsrkJ4I
	nUZy2BFF/mOwZAG9sNBuVJZxgxFiTnhwSqhGZLSnWoOAU3rPQH5WXpV5;
Authentication-Results: sj-dkim-4; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 74c8c6a39062dbfd583931efcf641276
Cc: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B424.08BAD842
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C7B424.08BAD842"


------_=_NextPart_002_01C7B424.08BAD842
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Apologies for the 2nd email on this one. The first email included the
I-D ascii file was in the wrong format. The new correctly formatted I-D
is attached here.
=20
Regards.
=20
Hemant
=20
------------------------------------------------------------------------
-------------------------------------
=20
Folks,
=20
Here is the Abstract of our I-D that helps explain why we wrote this
I-D. =20
=20
   RFC 2461 [ND] describes host data forwarding and address resolution.
   However, nine years after the ND protocol became an RFC, IPv6 hosts
   still do not fully comply with RFC 2461 [ND].  In particular, hosts
   incorrectly implement on- vs. off-link data forwarding.  This
   document clarifies host behavior and associated router behavior to
   define explicitly address resolution and data forwarding models.  The
   set of new requirements beyond what has been specified in RFC 2461
   [ND] and RFC 2462 [ADDRCONF] is restricted to corrections and
   clarifications deemed necessary to facilitate correct implementation.
=20
=20
Please see section 5 of our I-D for a proposed change to 2462bis-08 - we
hear this I-D is=20
in Editor's queue and any changes to it must be given ASAP.
=20
We have tested and developed host and routers stacks for IPv6 at Cisco.=20
We'd like to be put this I-D on the agenda for the July 2007 IETF
meeting.=20
=20
Thanks.
=20
Kind Regards.
=20
Hemant
=20

------_=_NextPart_002_01C7B424.08BAD842
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007>Apologies for the 2nd email on this one. The =
first=20
email included the I-D ascii file was in the wrong format. The new =
correctly=20
formatted I-D is attached here.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007>Regards.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007>Hemant</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007>----------------------------------------------=
---------------------------------------------------------------</SPAN></S=
PAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D462224516-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007>Here =
is the Abstract=20
of our I-D that helps explain why we wrote this I-D.&nbsp; =
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007></SPAN><SPAN=20
class=3D231430516-08062007></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D231430516-08062007>&nbsp;&nbsp; RFC=20
2461 [ND] describes host data forwarding and address =
resolution.<BR>&nbsp;&nbsp;=20
However, nine years after the ND protocol became an RFC, IPv6=20
hosts<BR>&nbsp;&nbsp; still do not fully comply with RFC 2461 =
[ND].&nbsp; In=20
particular, hosts<BR>&nbsp;&nbsp; incorrectly implement on- vs. off-link =
data=20
forwarding.&nbsp; This<BR>&nbsp;&nbsp; document clarifies host behavior =
and=20
associated router behavior to<BR>&nbsp;&nbsp; define explicitly address=20
resolution and data forwarding models.&nbsp; The<BR>&nbsp;&nbsp; set of =
new=20
requirements beyond what has been specified in RFC 2461<BR>&nbsp;&nbsp; =
[ND] and=20
RFC 2462 [ADDRCONF] is restricted to corrections and</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D231430516-08062007>&nbsp;&nbsp;=20
clarifications deemed necessary to facilitate correct=20
implementation.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007>Please see section 5 of our I-D for a =
proposed change=20
to 2462bis-08 - we hear this I-D is </SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007>in Editor's queue and any changes to it must =
be given=20
ASAP.</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007><SPAN=20
class=3D665482216-21062007></SPAN></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007>We have tested=20
and developed host </SPAN><SPAN class=3D231430516-08062007>and routers =
stacks for=20
IPv6 at Cisco. </SPAN></FONT></FONT></DIV>
<DIV><SPAN class=3D231430516-08062007></SPAN><FONT face=3DArial><FONT =
size=3D2><SPAN=20
class=3D231430516-08062007>We'd like to be put this I-D on the agenda =
for the July=20
2007 IETF </SPAN><SPAN class=3D231430516-08062007>meeting.=20
</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D231430516-08062007></SPAN><SPAN=20
class=3D231430516-08062007></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Thanks.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D231430516-08062007>Kind=20
Regards.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007>Hemant</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D231430516-08062007></SPAN></FONT>&nbsp;</DIV></DIV></DIV></BODY><=
/HTML>

------_=_NextPart_002_01C7B424.08BAD842--

------_=_NextPart_001_01C7B424.08BAD842
Content-Type: text/plain;
	name="draft-wbeebee-nd-implementation-pitfalls-00.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-wbeebee-nd-implementation-pitfalls-00.txt
Content-Disposition: attachment;
	filename="draft-wbeebee-nd-implementation-pitfalls-00.txt"

DQoNCg0KTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIEguIFNpbmdoDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBXLiBCZWViZWUNCkludGVuZGVkIHN0YXR1czog
U3RhbmRhcmRzIFRyYWNrICAgICAgICAgICAgICAgICAgICAgQ2lzY28gU3lzdGVtcywgSW5jLg0K
RXhwaXJlczogRGVjZW1iZXIgMjMsIDIwMDcgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICBKdW5lIDIxLCAyMDA3DQoNCg0KICAgICAgIERhdGEgRm9yd2FyZGluZyBhbmQgTkQgUmVzb2x1
dGlvbiBJbXBsZW1lbnRhdGlvbiBQaXRmYWxscw0KICAgICAgICAgICAgICBkcmFmdC13YmVlYmVl
LW5kLWltcGxlbWVudGF0aW9uLXBpdGZhbGxzLTAwDQoNClN0YXR1cyBvZiB0aGlzIE1lbW8NCg0K
ICAgQnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhvciByZXByZXNl
bnRzIHRoYXQgYW55DQogICBhcHBsaWNhYmxlIHBhdGVudCBvciBvdGhlciBJUFIgY2xhaW1zIG9m
IHdoaWNoIGhlIG9yIHNoZSBpcyBhd2FyZQ0KICAgaGF2ZSBiZWVuIG9yIHdpbGwgYmUgZGlzY2xv
c2VkLCBhbmQgYW55IG9mIHdoaWNoIGhlIG9yIHNoZSBiZWNvbWVzDQogICBhd2FyZSB3aWxsIGJl
IGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNlY3Rpb24gNiBvZiBCQ1AgNzkuDQoNCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIEludGVybmV0IEVu
Z2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFzLCBhbmQgaXRzIHdvcmtp
bmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0
ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0NCiAgIERyYWZ0cy4NCg0KICAgSW50ZXJu
ZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXgg
bW9udGhzDQogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkg
b3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9wcmlhdGUgdG8g
dXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9yIHRvIGNpdGUg
dGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhlIGxpc3Qgb2Yg
Y3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3
LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQuDQoNCiAgIFRoZSBsaXN0IG9mIEludGVy
bmV0LURyYWZ0IFNoYWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQNCiAgIGh0dHA6
Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwuDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2ls
bCBleHBpcmUgb24gRGVjZW1iZXIgMjMsIDIwMDcuDQoNCkNvcHlyaWdodCBOb3RpY2UNCg0KICAg
Q29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAoMjAwNykuDQoNCkFic3RyYWN0DQoNCiAgIFJG
QyAyNDYxIFtORF0gZGVzY3JpYmVzIGhvc3QgZGF0YSBmb3J3YXJkaW5nIGFuZCBhZGRyZXNzIHJl
c29sdXRpb24uDQogICBIb3dldmVyLCBuaW5lIHllYXJzIGFmdGVyIHRoZSBORCBwcm90b2NvbCBi
ZWNhbWUgYW4gUkZDLCBJUHY2IGhvc3RzDQogICBzdGlsbCBkbyBub3QgZnVsbHkgY29tcGx5IHdp
dGggUkZDIDI0NjEgW05EXS4gIEluIHBhcnRpY3VsYXIsIGhvc3RzDQogICBpbmNvcnJlY3RseSBp
bXBsZW1lbnQgb24tIHZzLiBvZmYtbGluayBkYXRhIGZvcndhcmRpbmcuICBUaGlzDQogICBkb2N1
bWVudCBjbGFyaWZpZXMgaG9zdCBiZWhhdmlvciBhbmQgYXNzb2NpYXRlZCByb3V0ZXIgYmVoYXZp
b3IgdG8NCiAgIGRlZmluZSBleHBsaWNpdGx5IGFkZHJlc3MgcmVzb2x1dGlvbiBhbmQgZGF0YSBm
b3J3YXJkaW5nIG1vZGVscy4gIFRoZQ0KICAgc2V0IG9mIG5ldyByZXF1aXJlbWVudHMgYmV5b25k
IHdoYXQgaGFzIGJlZW4gc3BlY2lmaWVkIGluIFJGQyAyNDYxDQogICBbTkRdIGFuZCBSRkMgMjQ2
MiBbQUREUkNPTkZdIGlzIHJlc3RyaWN0ZWQgdG8gY29ycmVjdGlvbnMgYW5kDQoNCg0KDQpTaW5n
aCAmIEJlZWJlZSAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIzLCAyMDA3ICAgICAgICAgICAg
ICAgW1BhZ2UgMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgTkQgSW1wbGVtZW50YXRpb24g
UGl0ZmFsbHMgICAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoNCiAgIGNsYXJpZmljYXRpb25zIGRl
ZW1lZCBuZWNlc3NhcnkgdG8gZmFjaWxpdGF0ZSBjb3JyZWN0IGltcGxlbWVudGF0aW9uLg0KDQoN
ClRhYmxlIG9mIENvbnRlbnRzDQoNCiAgIDEuICBJbnRyb2R1Y3Rpb24gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgMw0KICAgMi4gIEhvc3QgTW9kZWxz
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzDQog
ICAgIDIuMS4gIFJBIFNldHMgTSBhbmQgTyBCaXRzIGJ1dCBkb2VzIG5vdCBJbmNsdWRlIHRoZSBQ
cmVmaXgNCiAgICAgICAgICAgSW5mb3JtYXRpb24gT3B0aW9uIChQSU8pIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgNQ0KICAgICAyLjIuICBSQSBBZHZlcnRpc2VzIGEgUHJlZml4
IHdpdGggdGhlIE9uLWxpbmsoTCkgQml0IFNldCAuIC4gLiAuICA1DQogICAgIDIuMy4gIFJBIEFk
dmVydGlzZXMgYSBQcmVmaXggd2l0aCB0aGUgT24tbGluayhMKSBCaXQgQ2xlYXIgLiAuIC4gIDcN
CiAgIDMuICBSb3V0ZXIgTW9kZWxzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAgNw0KICAgICAzLjEuICBBZ2dyZWdhdGlvbiBSb3V0ZXIgRGVwbG95bWVu
dCBNb2RlbCAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA3DQogICA0LiAgUmVkaXJlY3QgQ2xhcmlm
aWNhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDgNCiAgIDUu
ICBDaGFuZ2VzIHRvIGRyYWZ0LWlldGYtaXB2Ni1yZmMyNDYyYmlzLTA4IC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgOA0KICAgNi4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA5DQogICA3LiAgSUFOQSBDb25zaWRlcmF0aW9ucyAg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDkNCiAgIDguICBBY2tu
b3dsZWRnZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgOQ0KICAgOS4gIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIDEwDQogICAgIDkuMS4gIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTANCiAgICAgOS4yLiAgSW5mb3Jt
YXRpdmUgUmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMA0K
ICAgQXV0aG9ycycgQWRkcmVzc2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIDEwDQogICBJbnRlbGxlY3R1YWwgUHJvcGVydHkgYW5kIENvcHlyaWdodCBT
dGF0ZW1lbnRzIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTINCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KU2luZ2ggJiBCZWViZWUgICAgICAgICAg
RXhwaXJlcyBEZWNlbWJlciAyMywgMjAwNyAgICAgICAgICAgICAgIFtQYWdlIDJdDQoMDQpJbnRl
cm5ldC1EcmFmdCAgICAgICAgIE5EIEltcGxlbWVudGF0aW9uIFBpdGZhbGxzICAgICAgICAgICAg
ICBKdW5lIDIwMDcNCg0KDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgIElQdjYgaG9zdCBkYXRhIGZv
cndhcmRpbmcgYW5kIGFkZHJlc3MgcmVzb2x1dGlvbiBpcyBjb21wbGV4LiAgRm9yDQogICBleGFt
cGxlLCBSRkMgMjQ2MSBbTkRdIChzZWN0aW9uIDMuMSkgc3RhdGVzIHRoYXQgaWYgdGhlIFJBIHJl
Y2VpdmVkDQogICBieSB0aGUgaG9zdCBkb2VzIG5vdCBhZHZlcnRpc2UgYW55IHByZWZpeCwgdGhl
biB0aGUgaG9zdCBtdXN0IHNlbmQNCiAgIGFsbCBkYXRhIHRvIHRoZSByb3V0ZXIuICBUaGlzIHNl
Y3Rpb24gb2YgdGhlIFJGQyBpbXBsaWVzIHRoYXQgbm8NCiAgIGFkZHJlc3MgcmVzb2x1dGlvbiBp
cyB0byBiZSBwZXJmb3JtZWQgaW4gdGhpcyBjYXNlLiAgU2VjdGlvbnMgNS4yIGFuZA0KICAgNy4y
LjIgaW1wbHkgdGhhdCB0aGUgaG9zdCBwZXJmb3JtcyBhZGRyZXNzIHJlc29sdXRpb24gYmVmb3Jl
DQogICB0cmFuc21pdHRpbmcgYSBwYWNrZXQgaWYgdGhlIGRlc3RpbmF0aW9uIG9mIHRoZSBwYWNr
ZXQgaXMgb24gdGhlIHNhbWUNCiAgIGxpbmsgYXMgdGhlIGhvc3QuICBTb21lIGN1cnJlbnQgaG9z
dCBpbXBsZW1lbnRhdGlvbnMgcGVyZm9ybSBhZGRyZXNzDQogICByZXNvbHV0aW9uIGluIGFsbCBj
YXNlcyBldmVuIHdoZW4gdGhlIGRlc3RpbmF0aW9uIGlzIG5vdCBjbGVhcmx5IG9uLQ0KICAgbGlu
ay4gIEhvd2V2ZXIsIFJGQyAyNDYxIFtORF0gc2VjdGlvbiA2LjMuNCBpbXBsaWVzIHRoYXQgaG9z
dHMgbXVzdA0KICAgY2xlYXJseSBkZXRlcm1pbmUgdGhhdCBhIGRlc3RpbmF0aW9uIGlzIG9uLWxp
bmsgYmVmb3JlIHBlcmZvcm1pbmcNCiAgIGFkZHJlc3MgcmVzb2x1dGlvbi4NCg0KICAgVGhlc2Ug
aW1wbGljYXRpb25zIGluIFJGQyAyNDYxIFtORF0gbmVlZCB0byBiZSBtYWRlIGV4cGxpY2l0Lg0K
ICAgRmFpbHVyZSBvZiBob3N0IGltcGxlbWVudGF0aW9ucyB0byBjb21wbHkgY2FuIHJlc3VsdCBp
biBsYWNrIG9mIElQdjYNCiAgIGNvbm5lY3Rpdml0eS4gIEZvciBleGFtcGxlLCBhIGhvc3QgcmVj
ZWl2ZXMgYW4gUkEgd2l0aCBubyBwcmVmaXgNCiAgIGFkdmVydGlzZWQgYW5kIGluY29ycmVjdGx5
IGRlY2lkZXMgdG8gcGVyZm9ybSBhZGRyZXNzIHJlc29sdXRpb24gd2hlbg0KICAgdGhlIGhvc3Qg
c2hvdWxkIGhhdmUgc2VudCBhbGwgdHJhZmZpYyB0byB0aGUgZGVmYXVsdCByb3V0ZXIuICBUaGUN
CiAgIHJvdXRlciBtYXkgbm90IHJlc3BvbmQgdG8gdGhlIGFkZHJlc3MgcmVzb2x1dGlvbiBhbmQg
dGhlIGxheWVyIDINCiAgIGRyaXZlciBvZiB0aGUgaG9zdCBzdG9wcyB0cmFuc21pdHRpbmcgSVB2
NiBwYWNrZXRzLg0KDQogICBIb3N0IGFkZHJlc3MgcmVzb2x1dGlvbiBoYXMgaW1wbGljYXRpb25z
IGZvciByb3V0ZXIgZGVzaWduIGFuZA0KICAgZGVwbG95bWVudC4gIEZpcnN0LCBob3N0IGJlaGF2
aW9yIGlzIGNsYXJpZmllZCBpbiB0aGUgSG9zdCBNb2RlbHMNCiAgIHNlY3Rpb24uICBTZWNvbmQs
IGEgcm91dGVyIGRlcGxveW1lbnQgbW9kZWwgaXMgZGVzY3JpYmVkIGluIHRoZQ0KICAgUm91dGVy
IE1vZGVscyBzZWN0aW9uLiAgVGhpcmQsIFJlZGlyZWN0cyBhcmUgY2xhcmlmaWVkIGZvciBib3Ro
DQogICByb3V0ZXJzIGFuZCBob3N0cyBpbiB0aGUgUmVkaXJlY3QgQ2xhcmlmaWNhdGlvbnMgc2Vj
dGlvbi4gIEZpbmFsbHksDQogICBwcm9wb3NlZCBjaGFuZ2VzIHRvIGRyYWZ0LWlldGYtaXB2Ni1y
ZmMyNDYyYmlzLTA4IFtBRERSQ09ORmJpc10gYXJlDQogICBwcmVzZW50ZWQuDQoNCiAgIFdoZXJl
IGJlaGF2aW9yIGhhcyBub3QgY2hhbmdlZCBiZXR3ZWVuIFJGQyAyNDYxIFtORF0gYW5kDQogICBk
cmFmdC1pZXRmLWlwdjYtMjQ2MWJpcy0xMSBbTkRiaXNdIGFuZCBiZWhhdmlvciBoYXMgbm90IGNo
YW5nZWQNCiAgIGJldHdlZW4gUkZDIDI0NjIgW0FERFJDT05GXSBhbmQgZHJhZnQtaWV0Zi1pcHY2
LXJmYzI0NjJiaXMtMDgNCiAgIFtBRERSQ09ORmJpc10sIHRoaXMgZG9jdW1lbnQgb25seSByZWZl
cnMgdG8gUkZDIDI0NjEgW05EXSBhbmQgUkZDDQogICAyNDYyIFtBRERSQ09ORl0gcmVzcGVjdGl2
ZWx5LiAgV2hlcmUgYmVoYXZpb3IgaGFzIGNoYW5nZWQsIHRoaXMNCiAgIGRvY3VtZW50IHJlZmVy
cyB0byBib3RoIHRoZSBvcmlnaW5hbCBhbmQgdGhlIG5ldyB2ZXJzaW9uLg0KDQoNCjIuICBIb3N0
IE1vZGVscw0KDQogICBBIGNvcnJlY3RseSBpbXBsZW1lbnRlZCBJUHY2IGhvc3QgTVVTVCBhZGhl
cmUgdG8gdGhlIGZvbGxvd2luZyBydWxlczoNCg0KICAgMS4gIE9uLWxpbmsgZGV0ZXJtaW5hdGlv
biBhbmQgYWRkcmVzcyBpbmZvcm1hdGlvbiBNVVNUIE5PVCBwZXJzaXN0DQogICAgICAgYWNyb3Nz
IElQdjYgaW50ZXJmYWNlIGluaXRpYWxpemF0aW9ucy4NCg0KICAgMi4gIFRoZSBSQSBhbmQgUmVk
aXJlY3RzIGZyb20gdGhlIGRlZmF1bHQgcm91dGVyIGFyZSB0aGUgb25seSBzb3VyY2VzDQogICAg
ICAgb2YgaW5mb3JtYXRpb24gZm9yIG9uLWxpbmsgZGV0ZXJtaW5hdGlvbi4gIERIQ1B2NiBvciBh
bnkgb3RoZXINCg0KDQoNClNpbmdoICYgQmVlYmVlICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIg
MjMsIDIwMDcgICAgICAgICAgICAgICBbUGFnZSAzXQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAg
ICBORCBJbXBsZW1lbnRhdGlvbiBQaXRmYWxscyAgICAgICAgICAgICAgSnVuZSAyMDA3DQoNCg0K
ICAgICAgIGNvbmZpZ3VyYXRpb24gb24gdGhlIGhvc3QgTVVTVCBOT1QgYmUgdXNlZCBmb3Igb24t
bGluaw0KICAgICAgIGRldGVybWluYXRpb24uICBNYW51YWwgY29uZmlndXJhdGlvbiBvZiBhIGhv
c3QgaW50cm9kdWNlcyBpdHMgb3duDQogICAgICAgc2V0IG9mIHNlY3VyaXR5IGNvbnNpZGVyYXRp
b25zIGFuZCBpcyBiZXlvbmQgdGhlIHNjb3BlIG9mIHRoaXMNCiAgICAgICBkb2N1bWVudC4NCg0K
ICAgMy4gIFRoZSBob3N0IE1VU1QgTk9UIGFkZCBhIGRpcmVjdCBkZWxpdmVyeSByb3V0ZSB0byB0
aGUgcHJlZml4IGZyb20NCiAgICAgICBhbiBhc3NpZ25lZCBhZGRyZXNzLCBpbmRlcGVuZGVudCBv
ZiB0aGUgaW5mb3JtYXRpb24gYWJvdXQgdGhlDQogICAgICAgcHJlZml4IHJlY2VpdmVkIGZyb20g
dGhlIFJBIG9yIFJlZGlyZWN0cy4NCg0KICAgNC4gIFRoZSBob3N0IE1VU1QgaXNzdWUgTlMoREFE
KXMgZm9yIGFsbCBvZiBpdHMgYWNxdWlyZWQgdW5pY2FzdA0KICAgICAgIGFkZHJlc3NlcyBleGNl
cHQgd2hlbiB0aGUgaG9zdCBpbnRlcmZhY2UgaGFzDQogICAgICAgRHVwQWRkckRldGVjdFRyYW5z
bWl0cyB2YXJpYWJsZSBzZXQgdG8gemVyby4gIFNlY3Rpb24gNS40IG9mIFJGQw0KICAgICAgIDI0
NjIgW0FERFJDT05GXSBlcnJvbmVvdXNseSByZWxheGVzIHRoaXMgcmVxdWlyZW1lbnQgYW5kIHN1
ZmZlcnMNCiAgICAgICBmcm9tIGEgc2VjdXJpdHkgcHJvYmxlbSBhcyBpbGx1c3RyYXRlZCBieSB0
aGUgZm9sbG93aW5nIGV4YW1wbGU6DQoNCiAgICAgICAgICBIb3N0MSB1c2VzIEVVSS02NCB0byBj
b25maWd1cmUgYSBMaW5rIExvY2FsIEFkZHJlc3MgKExMQSkNCiAgICAgICAgICB1c2luZyBNQUMx
IGFuZCBtYW51YWxseSBjb25maWd1cmVzIGEgR2xvYmFsIFVuaWNhc3QgQWRkcmVzcw0KICAgICAg
ICAgIChHVUEpIHRoYXQgaXMgZXF1YWwgdG8gYW4gYWRkcmVzcyBjb25maWd1cmVkIHVzaW5nIEVV
SS02NCBhbmQNCiAgICAgICAgICBNQUMyLiAgSG9zdDEgY29tcGxldGVzIGFuIE5TKERBRCkgZm9y
IGJvdGggaXRzIExMQSBhbmQgR1VBLg0KICAgICAgICAgIFRoZW4sIEhvc3QyIHVzZXMgRVVJLTY0
IHRvIGNvbmZpZ3VyZSBib3RoIGEgTExBIGFuZCBhIEdVQQ0KICAgICAgICAgIHVzaW5nIE1BQzIu
ICBIb3N0MiBjb21wbGV0ZXMgYW4gTlMoREFEKSBmb3IgdGhlIExMQSBhbmQgZG9lcw0KICAgICAg
ICAgIG5vdCBzZW5kIGFuIE5TKERBRCkgZm9yIGl0cyBHVUEgaW4gY29tcGxpYW5jZSB3aXRoIFJG
QyAyNDYyDQogICAgICAgICAgW0FERFJDT05GXS4gIE5vdyBIb3N0MSBhbmQgSG9zdDIgaGF2ZSB0
aGUgc2FtZSBHVUEgb24gdGhlIHNhbWUNCiAgICAgICAgICBsaW5rLg0KDQogICAgICAgVGhlcmVm
b3JlLCB0aGlzIGV4Y2VwdGlvbiBpbiBzZWN0aW9uIDUuNCBvZiBSRkMgMjQ2MiBbQUREUkNPTkZd
DQogICAgICAgTVVTVCBiZSBpZ25vcmVkLiAgTm90ZSB0aGF0IGRyYWZ0LWlldGYtaXB2Ni1yZmMy
NDYyYmlzLTA4DQogICAgICAgW0FERFJDT05GYmlzXSByZWZlcnMgdG8gYW4gZXh0ZW5zaWJpbGl0
eSBjb25jZXJuIHdpdGggbmV3DQogICAgICAgaW1wbGVtZW50YXRpb25zIGFuZCBzdGF0ZXMgaW4g
c2VjdGlvbiA1LjQ6DQoNCiAgICAgICAgICAiV2hlcmVhcyB0aGlzIGRvY3VtZW50IGRvZXMgbm90
IGludmFsaWRhdGUgc3VjaA0KICAgICAgICAgIGltcGxlbWVudGF0aW9ucywgdGhpcyBraW5kIG9m
ICdvcHRpbWl6YXRpb24nIGlzIE5PVA0KICAgICAgICAgIFJFQ09NTUVOREVELCBhbmQgbmV3IGlt
cGxlbWVudGF0aW9ucyBNVVNUIE5PVCBkbyB0aGF0DQogICAgICAgICAgb3B0aW1pemF0aW9uLiIN
Cg0KICAgICAgIEhvd2V2ZXIsIHRoZSBzZWN1cml0eSBwcm9ibGVtIG1lbnRpb25lZCBpbiB0aGlz
IGRvY3VtZW50DQogICAgICAgaW52YWxpZGF0ZXMgZXZlbiBjdXJyZW50bHkgZXhpc3RpbmcgaW1w
bGVtZW50YXRpb25zLiAgVGhlDQogICAgICAgIkNoYW5nZXMgdG8gZHJhZnQtaWV0Zi1pcHY2LXJm
YzI0NjJiaXMtMDgiIHNlY3Rpb24gaW4gdGhpcw0KICAgICAgIGRvY3VtZW50IGRlc2NyaWJlcyB0
aGUgY29ycmVzcG9uZGluZyBjaGFuZ2VzIHRvDQogICAgICAgZHJhZnQtaWV0Zi1pcHY2LXJmYzI0
NjJiaXMtMDggW0FERFJDT05GYmlzXS4NCg0KICAgNS4gIFRoZSBob3N0IFNIT1VMRCBpc3N1ZSBv
bmx5IGEgc2luZ2xlIE5TKERBRCkgZm9yIGVhY2ggYWRkcmVzcy4NCiAgICAgICBUaGUgZGVmYXVs
dCB2YWx1ZSBmb3IgRHVwQWRkckRldGVjdFRyYW5zbWl0cyB2YXJpYWJsZSBpcw0KICAgICAgIHNw
ZWNpZmllZCBhcyAxIGluIHNlY3Rpb24gNS4xIG9mIFJGQyAyNDYyIFtBRERSQ09ORl0uDQoNCiAg
IDYuICBJZiB0aGUgRGVmYXVsdCBSb3V0ZXIgTGlzdCBpcyBlbXB0eSwgdGhlIGhvc3QgTVVTVCBO
T1QgYXNzdW1lDQogICAgICAgdGhhdCBhbGwgZGVzdGluYXRpb25zIGFyZSBvbi1saW5rLiAgVGhl
IGhvc3QgTVVTVCBOT1QgcGVyZm9ybQ0KICAgICAgIGFkZHJlc3MgcmVzb2x1dGlvbiBmb3Igbm9u
LWxpbmstbG9jYWwgYWRkcmVzc2VzLiAgVGhlIGhvc3QgU0hPVUxEDQoNCg0KDQpTaW5naCAmIEJl
ZWJlZSAgICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDIzLCAyMDA3ICAgICAgICAgICAgICAgW1Bh
Z2UgNF0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgICAgTkQgSW1wbGVtZW50YXRpb24gUGl0ZmFs
bHMgICAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoNCiAgICAgICBzZW5kIGFuIElDTVB2NiBEZXN0
aW5hdGlvbiBVbnJlYWNoYWJsZSBtZXNzYWdlIGluc3RlYWQuDQogICAgICAgZHJhZnQtaWV0Zi12
Nm9wcy1vbmxpbmthc3N1bXB0aW9uLTA0DQogICAgICAgW0kuRC5pZXRmLXY2b3BzLW9ubGlua2Fz
c3VtcHRpb25zXSBwcm92aWRlcyBqdXN0aWZpY2F0aW9uIGZvcg0KICAgICAgIHRoaXMgcnVsZS4N
Cg0KICAgVGhlIHR5cGUgb2YgUkEgcmVjZWl2ZWQgY2FuIGZ1cnRoZXIgZGV0ZXJtaW5lIGhvc3Qg
YmVoYXZpb3IuDQoNCjIuMS4gIFJBIFNldHMgTSBhbmQgTyBCaXRzIGJ1dCBkb2VzIG5vdCBJbmNs
dWRlIHRoZSBQcmVmaXggSW5mb3JtYXRpb24NCiAgICAgIE9wdGlvbiAoUElPKQ0KDQogICBTZWN0
aW9uIDMuMSBvZiBSRkMgMjQ2MSBbTkRdIGRlc2NyaWJlcyBpbnRlbmRlZCBiZWhhdmlvciB3aGVu
IGEgaG9zdA0KICAgcmVjZWl2ZXMgYW4gUkEgd2l0aG91dCBhbiBhZHZlcnRpc2VkIHByZWZpeDoN
Cg0KICAgICAgIk11bHRpcGxlIHByZWZpeGVzIGNhbiBiZSBhc3NvY2lhdGVkIHdpdGggdGhlIHNh
bWUgbGluay4gIEJ5DQogICAgICBkZWZhdWx0LCBob3N0cyBsZWFybiBhbGwgb24tbGluayBwcmVm
aXhlcyBmcm9tIFJvdXRlcg0KICAgICAgQWR2ZXJ0aXNlbWVudHMuICBIb3dldmVyLCByb3V0ZXJz
IG1heSBiZSBjb25maWd1cmVkIHRvIG9taXQgc29tZQ0KICAgICAgb3IgYWxsIHByZWZpeGVzIGZy
b20gUm91dGVyIEFkdmVydGlzZW1lbnRzLiAgSW4gc3VjaCBjYXNlcyBob3N0cw0KICAgICAgYXNz
dW1lIHRoYXQgZGVzdGluYXRpb25zIGFyZSBvZmYtbGluayBhbmQgc2VuZCB0cmFmZmljIHRvIHJv
dXRlcnMuDQogICAgICBBIHJvdXRlciBjYW4gdGhlbiBpc3N1ZSByZWRpcmVjdHMgYXMgYXBwcm9w
cmlhdGUuIg0KDQogICBBbiBJUHY2IHJvdXRlciBzZW5kcyBhbiBSQSB3aXRoIG5vIHByZWZpeCBh
ZHZlcnRpc2VkIGFuZCB0aGUgTSBhbmQgTw0KICAgYml0cyBzZXQgYW5kIGRvZXMgbm90IHNlbmQg
YW55IFJlZGlyZWN0cy4gIE9uIHJlY2VpcHQgb2YgdGhlIFJBLCB0aGUNCiAgIGhvc3QgdXNlcyBE
SENQdjYgdG8gYWNxdWlyZSBhbiBJUHY2IGFkZHJlc3MuICBBZnRlciBjb21wbGV0aW5nIElQdjYN
CiAgIGFkZHJlc3MgYWNxdWlzaXRpb24sIHRoZSBob3N0IE1VU1Qgb2JleSBSRkMgMjQ2MSBbTkRd
LCBzZWN0aW9uIDMuMS4NCiAgIFNpbmNlIHRoZSBSQSBpcyB0aGUgb25seSBhdXRob3JpdHkgdG8g
YSBob3N0IGZvciBvbi1saW5rDQogICBkZXRlcm1pbmF0aW9uIGFuZCB0aGlzIFJBIGRvZXMgbm90
IGFkdmVydGlzZSBhbnkgcHJlZml4LCB0aGUgaG9zdA0KICAgY2Fubm90IGRldGVybWluZSB0aGF0
IGEgZGVzdGluYXRpb24gaXMgb24tbGluay4gIFRoZXJlZm9yZSwgdGhlIGhvc3QNCiAgIE1VU1Qg
YWRoZXJlIHRvIHRoZSBmb2xsb3dpbmcgcnVsZXM6DQoNCiAgIDEuICBUaGUgaG9zdCBNVVNUIE5P
VCBhc3N1bWUgYW55IGRlZmF1bHQgcHJlZml4IGxlbmd0aC4NCg0KICAgMi4gIFRoZSBob3N0IE1V
U1Qgc2VuZCBhbGwgdHJhZmZpYyB0byB0aGUgZGVmYXVsdCByb3V0ZXIuDQoNCiAgIDMuICBUaGUg
aG9zdCBNVVNUIE5PVCBpc3N1ZSBhbiBOUyB0byByZXNvbHZlIGEgZGVzdGluYXRpb24gb3RoZXIg
dGhhbg0KICAgICAgIHRoZSBMaW5rLUxvY2FsIGFkZHJlc3Mgb2YgdGhlIGRlZmF1bHQgcm91dGVy
Lg0KDQoyLjIuICBSQSBBZHZlcnRpc2VzIGEgUHJlZml4IHdpdGggdGhlIE9uLWxpbmsoTCkgQml0
IFNldA0KDQogICBTZWN1cml0eSBjb25zZXF1ZW5jZXMgb2YgUkZDIDI0NjEgW05EXSBpbXBseSB0
aGF0IGhvc3RzIE1BWSBzZW5kIGFsbA0KICAgdHJhZmZpYyB0byB0aGUgZGVmYXVsdCByb3V0ZXIg
d2l0aG91dCBwZXJmb3JtaW5nIGFkZHJlc3MgcmVzb2x1dGlvbg0KICAgZmlyc3QgZXZlbiB3aGVu
IGEgUElPIGhhcyBiZWVuIHJlY2VpdmVkIGFkdmVydGlzaW5nIGFuIG9uLWxpbmsNCiAgIHByZWZp
eCwgcmVnYXJkbGVzcyBvZiB3aGV0aGVyIHRoZSBob3N0IHBlcmZvcm1zIERIQ1B2NiBhbmQvb3IN
CiAgIHN0YXRlbGVzcyBhdXRvY29uZmlndXJhdGlvbi4NCg0KICAgU2VjdGlvbiA0LjYuMiBvZiBS
RkMgMjQ2MSBbTkRdIGRlZmluZXMgdGhlIFZhbGlkIExpZmV0aW1lIGluIHRoZSBQSU8NCiAgIGFz
Og0KDQoNCg0KDQoNClNpbmdoICYgQmVlYmVlICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjMs
IDIwMDcgICAgICAgICAgICAgICBbUGFnZSA1XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICBO
RCBJbXBsZW1lbnRhdGlvbiBQaXRmYWxscyAgICAgICAgICAgICAgSnVuZSAyMDA3DQoNCg0KICAg
ICAgIlRoZSBsZW5ndGggb2YgdGltZSBpbiBzZWNvbmRzIChyZWxhdGl2ZSB0byB0aGUgdGltZSB0
aGUgcGFja2V0IGlzDQogICAgICBzZW50KSB0aGF0IHRoZSBwcmVmaXggaXMgdmFsaWQgZm9yIHRo
ZSBwdXJwb3NlIG9mIG9uLWxpbmsNCiAgICAgIGRldGVybWluYXRpb24uIg0KDQogICBTZWN0aW9u
IDExIG9mIFJGQyAyNDYxIFtORF0gbWVudGlvbnMgdGhlIGZvbGxvd2luZyBkZW5pYWwgb2Ygc2Vy
dmljZQ0KICAgYXR0YWNrOg0KDQogICAgICAiQW4gZXhhbXBsZSBvZiBkZW5pYWwgb2Ygc2Vydmlj
ZSBhdHRhY2tzIGlzIHRoYXQgYSBub2RlIG9uIHRoZQ0KICAgICAgbGluayB0aGF0IGNhbiBzZW5k
IHBhY2tldHMgd2l0aCBhbiBhcmJpdHJhcnkgSVAgc291cmNlIGFkZHJlc3MgY2FuDQogICAgICBi
b3RoIGFkdmVydGlzZSBpdHNlbGYgYXMgYSBkZWZhdWx0IHJvdXRlciBhbmQgYWxzbyBzZW5kICdm
b3JnZWQnDQogICAgICBSb3V0ZXIgQWR2ZXJ0aXNlbWVudCBtZXNzYWdlcyB0aGF0IGltbWVkaWF0
ZWx5IHRpbWUgb3V0IGFsbCBvdGhlcg0KICAgICAgZGVmYXVsdCByb3V0ZXJzIGFzIHdlbGwgYXMg
YWxsIG9uLWxpbmsgcHJlZml4ZXMuIg0KDQogICBUaGUgc2FtZSBzZWN1cml0eSByaXNrIGlzIGFs
c28gZGVzY3JpYmVkIGluIHNlY3Rpb24gNS41LjMgb2YgUkZDIDI0NjINCiAgIFtBRERSQ09ORl0u
ICBUaGlzIHNlY3Rpb24gYWxsb3dzIGhvc3RzIHRvIGlnbm9yZSB0aGUgVmFsaWQgTGlmZXRpbWUN
CiAgIHN0b3JlZCBpbiBhbiBSQSBpbiBvcmRlciB0byBwcmV2ZW50IGRlbmlhbCBvZiBzZXJ2aWNl
IGF0dGFja3MuDQoNCiAgIFNlY3Rpb24gNi4zLjQgb2YgUkZDIDI0NjEgW05EXSBtZW50aW9ucyB0
aGF0IGhvc3RzIE1BWSBzZW5kIGFsbA0KICAgdHJhZmZpYyB0byB0aGUgZGVmYXVsdCByb3V0ZXIg
d2l0aG91dCBwZXJmb3JtaW5nIGFkZHJlc3MgcmVzb2x1dGlvbg0KICAgZmlyc3Q6DQoNCiAgICAg
ICJTdGF0ZWxlc3MgYWRkcmVzcyBhdXRvY29uZmlndXJhdGlvbiBSRkMgMjQ2MiBbQUREUkNPTkZd
IG1heSBpbg0KICAgICAgc29tZSBjaXJjdW1zdGFuY2VzIGluY3JlYXNlIHRoZSBWYWxpZCBMaWZl
dGltZSBvZiBhIHByZWZpeCBvcg0KICAgICAgaWdub3JlIGl0IGNvbXBsZXRlbHkgaW4gb3JkZXIg
dG8gcHJldmVudCBhIHBhcnRpY3VsYXIgZGVuaWFsIG9mDQogICAgICBzZXJ2aWNlIGF0dGFjay4g
IEhvd2V2ZXIsIHNpbmNlIHRoZSBlZmZlY3Qgb2YgdGhlIHNhbWUgZGVuaWFsIG9mDQogICAgICBz
ZXJ2aWNlIHRhcmdldGVkIGF0IHRoZSBvbi1saW5rIHByZWZpeCBsaXN0IGlzIG5vdCBjYXRhc3Ry
b3BoaWMNCiAgICAgIChob3N0cyB3b3VsZCBzZW5kIHBhY2tldHMgdG8gYSBkZWZhdWx0IHJvdXRl
ciBhbmQgcmVjZWl2ZSBhDQogICAgICByZWRpcmVjdCByYXRoZXIgdGhhbiBzZW5kaW5nIHBhY2tl
dHMgZGlyZWN0bHkgdG8gYSBuZWlnaGJvcikgdGhlDQogICAgICBOZWlnaGJvciBEaXNjb3Zlcnkg
cHJvdG9jb2wgZG9lcyBub3QgaW1wb3NlIHN1Y2ggYSBjaGVjayBvbiB0aGUNCiAgICAgIHByZWZp
eCBsaWZldGltZSB2YWx1ZXMuIg0KDQogICBDb25zaWRlciB0aGUgZm9sbG93aW5nIHNjZW5hcmlv
IHdpdGggb25lIHJvZ3VlIG5vZGUgYW5kIHR3byBvdGhlcg0KICAgaG9zdHMgb24gdGhlIHNhbWUg
bGluay4gIFRoZSByb2d1ZSBzZW5kcyBhIG1hbGljaW91cyBSQSB3aXRoIGFuIG9uLQ0KICAgbGlu
ayBwcmVmaXggd2l0aCBhIFZhbGlkIExpZmV0aW1lIG9mIHplcm8uICBIb3N0MSBjb3JyZWN0bHkN
CiAgIGltcGxlbWVudHMgc2VjdGlvbiA1LjUuMyBvZiBSRkMgMjQ2MiBbQUREUkNPTkZdIGFuZCBy
ZXNldHMgaXRzDQogICBTdG9yZWRMaWZldGltZSAob3IgUmVtYWluaW5nTGlmZXRpbWUgaW4gZHJh
ZnQtaWV0Zi1pcHY2LXJmYzI0NjJiaXMtMDgNCiAgIFtBRERSQ09ORmJpc10pIHRvIHR3byBob3Vy
cyBhbmQgYXZvaWRzIHRoZSBkZW5pYWwgb2Ygc2VydmljZSBhdHRhY2suDQogICBIb3N0MSB0cmll
cyB0byBzZW5kIHRyYWZmaWMgdG8gSG9zdDIsIGJ1dCBjYW5ub3QgdHJ1c3QgaXRzIG93biB0d28N
CiAgIGhvdXIgU3RvcmVkTGlmZXRpbWUuICBGb3IgaW5zdGFuY2UsIGEgbGVnaXRpbWF0ZSBvcGVy
YXRvciBtYXkgaGF2ZQ0KICAgdHJpZWQgdG8gdGltZSBvdXQgdGhlIHByZWZpeCBkdWUgdG8gYW4g
aW1wZW5kaW5nIHJlbnVtYmVyaW5nLiAgSG9zdDENCiAgIGRlY2lkZXMgdG8gc2VuZCBhbGwgb2Yg
aXRzIHRyYWZmaWMgdG8gdGhlIG9uLWxpbmsgYXV0aG9yaXR5LCB0aGUNCiAgIGRlZmF1bHQgcm91
dGVyLCBldmVuIHRob3VnaCB0aGUgZGVzdGluYXRpb24gcHJlZml4IGlzIG9uLWxpbmsuDQoNCiAg
IElGIHRoZSBob3N0IGRlY2lkZXMgdG8gc2VuZCBhbGwgdHJhZmZpYyAoaW5jbHVkaW5nIG9uLWxp
bmsgdHJhZmZpYykNCiAgIHRvIHRoZSBkZWZhdWx0IHJvdXRlciwgdGhlbiB0aGUgaG9zdCBNVVNU
IGZvbGxvdyB0aGUgZm9sbG93aW5nIHJ1bGU6DQoNCiAgIDEuICBUaGUgaG9zdCBNVVNUIE5PVCBp
c3N1ZSBhbiBOUyB0byByZXNvbHZlIGEgZGVzdGluYXRpb24gb3RoZXIgdGhhbg0KICAgICAgIHRo
ZSBMaW5rLUxvY2FsIGFkZHJlc3Mgb2YgdGhlIGRlZmF1bHQgcm91dGVyLg0KDQoNCg0KU2luZ2gg
JiBCZWViZWUgICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAyMywgMjAwNyAgICAgICAgICAgICAg
IFtQYWdlIDZdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgIE5EIEltcGxlbWVudGF0aW9uIFBp
dGZhbGxzICAgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQoyLjMuICBSQSBBZHZlcnRpc2VzIGEg
UHJlZml4IHdpdGggdGhlIE9uLWxpbmsoTCkgQml0IENsZWFyDQoNCiAgIFJlZ2FyZGxlc3Mgb2Yg
d2hldGhlciB0aGUgaG9zdCBwZXJmb3JtcyBESENQdjYgYW5kL29yIHN0YXRlbGVzcw0KICAgYXV0
b2NvbmZpZ3VyYXRpb24sIHRoZSBob3N0IE1VU1QgYWRoZXJlIHRvIHRoZSBmb2xsb3dpbmcgcnVs
ZXMgZm9yDQogICBhZGRyZXNzZXMgY29udGFpbmVkIHdpdGhpbiB0aGUgYWR2ZXJ0aXNlZCBwcmVm
aXg6DQoNCiAgIDEuICBUaGUgaG9zdCBNVVNUIE5PVCBpc3N1ZSBhbiBOUyB0byByZXNvbHZlIGEg
ZGVzdGluYXRpb24gb3RoZXIgdGhhbg0KICAgICAgIHRoZSBMaW5rLUxvY2FsIGFkZHJlc3Mgb2Yg
dGhlIGRlZmF1bHQgcm91dGVyLg0KDQogICAyLiAgVGhlIGhvc3QgTVVTVCBzZW5kIGFsbCB0cmFm
ZmljIHRvIHRoZSBkZWZhdWx0IHJvdXRlci4NCg0KDQozLiAgUm91dGVyIE1vZGVscw0KDQogICBU
aGUgUmVkaXJlY3QgQ2xhcmlmaWNhdGlvbnMgc2VjdGlvbiBjbGFyaWZpZXMgUkZDIDI0NjEgW05E
XSBob3N0IGFuZA0KICAgcm91dGVyIGJlaGF2aW9yIGZvciBhbiBhZ2dyZWdhdGlvbiByb3V0ZXIg
ZGVwbG95bWVudC4NCg0KICAgVGhlIEFnZ3JlZ2F0aW9uIFJvdXRlciBEZXBsb3ltZW50IE1vZGVs
IHNlY3Rpb24gcHJlc2VudHMgYSBwb3NzaWJsZQ0KICAgYWdncmVnYXRpb24gcm91dGVyIGRlcGxv
eW1lbnQgbW9kZWwgZm9yIElQdjYgYW5kIGRpc2N1c3NlcyBpdHMNCiAgIHByb3BlcnRpZXMgd2l0
aCByZXNwZWN0IHRvIE5ELiAgQWdncmVnYXRpb24gcm91dGVycyBjYW4gc2VydmljZSBtb3JlDQog
ICB0aGFuIDEwMCwwMDAgc3Vic2NyaWJlcnMuICBEdWUgdG8gc2NhbGluZyBjb25zaWRlcmF0aW9u
cywgYW55IE5TIGZvcg0KICAgZ2xvYmFsIGFkZHJlc3MgcmVzb2x1dGlvbiBmcm9tIGFueSBob3N0
IHRvIGFueSBvdGhlciBob3N0IFNIT1VMRCBOT1QNCiAgIHJlYWNoIHRoZSBhZ2dyZWdhdGlvbiBy
b3V0ZXIuDQoNCjMuMS4gIEFnZ3JlZ2F0aW9uIFJvdXRlciBEZXBsb3ltZW50IE1vZGVsDQoNCiAg
IEEgcHJvcGVydHkgb2Ygcm91dGVkIGFnZ3JlZ2F0aW9uIG5ldHdvcmtzIGlzIHRoYXQgaG9zdHMg
Y2Fubm90DQogICBkaXJlY3RseSBjb21tdW5pY2F0ZSB3aXRoIGVhY2ggb3RoZXIgZXZlbiBpZiB0
aGV5IGFyZSBvbiB0aGUgc2FtZQ0KICAgbGluay4gIFRoaXMgZGVzaWduIGlzIG1vdGl2YXRlZCBi
eSBzY2FsaW5nIGFuZCBzZWN1cml0eQ0KICAgY29uc2lkZXJhdGlvbnMuICBJZiBldmVyeSBob3N0
IGNvdWxkIHJlY2VpdmUgYWxsIHRyYWZmaWMgZnJvbSBldmVyeQ0KICAgb3RoZXIgaG9zdCwgdGhl
biB0aGUgc3Vic2NyaWJlcidzIHByaXZhY3kgd291bGQgYmUgdmlvbGF0ZWQgYW5kIHRoZQ0KICAg
YW1vdW50IG9mIGJhbmR3aWR0aCBhdmFpbGFibGUgZm9yIGVhY2ggc3Vic2NyaWJlciB3b3VsZCBi
ZSB2ZXJ5DQogICBzbWFsbC4gIFRoYXQgaXMgd2h5IGhvc3RzIGNvbW11bmljYXRlIGJldHdlZW4g
ZWFjaCBvdGhlciB0aHJvdWdoIHRoZQ0KICAgYWdncmVnYXRpb24gcm91dGVyLCB3aGljaCBpcyBh
bHNvIHRoZSBJUHY2IGZpcnN0LWhvcCByb3V0ZXIuDQoNCiAgIEZvciBzY2FsaW5nIHJlYXNvbnMs
IGFueSBOUyB0byByZXNvbHZlIGFueSBhZGRyZXNzIG90aGVyIHRoYW4gdGhhdCBvZg0KICAgdGhl
IGRlZmF1bHQgcm91dGVyIFNIT1VMRCBOT1QgcmVhY2ggdGhlIGFnZ3JlZ2F0aW9uIHJvdXRlci4N
Cg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0rDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICB8ICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICB8QWdncmUrLS0t
LShSdHIgQ1BFKS0tLS1Ib3N0MQ0KICAgICAgICAgICAgQ29yZS0tLS1XQU4tLS0tK2dhdG9yfA0K
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfCBSdHIgfA0KICAgICAgICAgICAgICAgICAgICAg
ICAgICAgfCAgICAgKy0tLS0oQnIgQ1BFKS0tLS0oQ3VzdCBSdHIpLS0tLUhvc3QyDQogICAgICAg
ICAgICAgICAgICAgICAgICAgICArLS0tLS0rDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIEZpZ3VyZSAxLg0KDQoNCg0KU2luZ2ggJiBCZWViZWUgICAgICAgICAgRXhwaXJlcyBE
ZWNlbWJlciAyMywgMjAwNyAgICAgICAgICAgICAgIFtQYWdlIDddDQoMDQpJbnRlcm5ldC1EcmFm
dCAgICAgICAgIE5EIEltcGxlbWVudGF0aW9uIFBpdGZhbGxzICAgICAgICAgICAgICBKdW5lIDIw
MDcNCg0KDQogICBJbiB0aGUgZmlndXJlIGFib3ZlLCB0aGUgY3VzdG9tZXIgcHJlbWlzZXMgZXF1
aXBtZW50IChDUEUpIGlzIG1hbmFnZWQNCiAgIGJ5IHRoZSBJU1AgYW5kIGlzIGRlcGxveWVkIGJl
aGluZCBhbiBhZ2dyZWdhdGlvbiByb3V0ZXIgdGhhdCBpcyBhbg0KICAgSVB2NiBmaXJzdC1ob3Ag
cm91dGVyIGFuZCBhbHNvIGEgREhDUHY2IHJlbGF5IGFnZW50LiAgSVB2NiBDUEVzIGFyZQ0KICAg
ZWl0aGVyIElQdjYgcm91dGVycyAoUnRyIENQRSkgb3IgSVB2NiBicmlkZ2VzIChCciBDUEUpLiAg
SWYgdGhlDQogICBjdXN0b21lciBwcmVtaXNlcyB1c2VzIGEgYnJpZGdlIENQRSwgdGhlbiBhIHJv
dXRlciAoQ3VzdCBSdHIpIGlzDQogICBuZWVkZWQuICBBbGwgaG9zdHMgcmVzaWRlIGJlaGluZCBh
IHJvdXRlciBDUEUgb3IgYSBjdXN0b21lciByb3V0ZXIuDQoNCiAgIE5vIE5TIHRvIHJlc29sdmUg
YW55IGFkZHJlc3Mgb3RoZXIgdGhhdCB0aGF0IG9mIHRoZSBkZWZhdWx0IHJvdXRlcg0KICAgd2ls
bCByZWFjaCB0aGUgYWdncmVnYXRpb24gcm91dGVyIGZyb20gYW55IGRldmljZSBvbiB0aGUgY3Vz
dG9tZXINCiAgIHNpZGUgb2YgdGhlIGFnZ3JlZ2F0b3IuICBDUEVzIGRvIG5vdCBjb21tdW5pY2F0
ZSB3aXRoIGVhY2ggb3RoZXIgaW4NCiAgIHRoaXMgZGVwbG95bWVudCBtb2RlbCBzaW5jZSBhIENQ
RSBkb2VzIG5vdCBydW4gYW55IGFwcGxpY2F0aW9ucyB0aGF0DQogICBuZWVkIHRvIGNvbW11bmlj
YXRlIHdpdGggb3RoZXIgQ1BFcy4gIEhvc3RzIGRvIGNvbW11bmljYXRlIHdpdGggZWFjaA0KICAg
b3RoZXIsIGJ1dCBldmVyeSBob3N0IGlzIG9mZi1saW5rIHRvIGFueSBvdGhlciBob3N0IG9uIHRo
ZQ0KICAgYWdncmVnYXRpb24gcm91dGVyLg0KDQoNCjQuICBSZWRpcmVjdCBDbGFyaWZpY2F0aW9u
cw0KDQogICBSZWRpcmVjdHMgTVVTVCBOT1QgYmUgc2VudCBieSBhZ2dyZWdhdGlvbiByb3V0ZXJz
IGV4Y2VwdCB3aGVuIHR3bw0KICAgaG9zdHMgYmVoaW5kIHRoZSBzYW1lIGJyaWRnZSBDUEUsIHdp
dGggbm8gcm91dGVyIGJldHdlZW4gdGhlIGhvc3QgYW5kDQogICB0aGUgYWdncmVnYXRpb24gcm91
dGVyLCBjb21tdW5pY2F0ZSB3aXRoIGVhY2ggb3RoZXIuICBUaGUgYWdncmVnYXRpb24NCiAgIHJv
dXRlciBNQVkgc2VuZCBhIFJlZGlyZWN0IHRvIGEgc291cmNlIGhvc3Qgd2hpY2ggY29tbXVuaWNh
dGVzIHdpdGggYQ0KICAgZGVzdGluYXRpb24gaG9zdCBiZWhpbmQgdGhlIHNhbWUgYnJpZGdlIENQ
RS4gIFNpbmNlIHRoZSBSZWRpcmVjdA0KICAgY29udGFpbnMgYWxsIHRoZSBpbmZvcm1hdGlvbiBu
ZWVkIHRvIHJlc29sdmUgdGhlIGFkZHJlc3Mgb2YgdGhlDQogICBkZXN0aW5hdGlvbiBob3N0LCB0
aGUgc291cmNlIGhvc3QgTVVTVCBOT1QgaXNzdWUgYW4gTlMgdG8gcmVzb2x2ZSB0aGUNCiAgIGRl
c3RpbmF0aW9uIGNvbnRhaW5lZCB3aXRoaW4gdGhlIFJlZGlyZWN0Lg0KDQoNCjUuICBDaGFuZ2Vz
IHRvIGRyYWZ0LWlldGYtaXB2Ni1yZmMyNDYyYmlzLTA4DQoNCiAgIFRoZSBmb2xsb3dpbmcgcGFy
YWdyYXBoIGZyb20gc2VjdGlvbiA1LjQgb2YNCiAgIGRyYWZ0LWlldGYtaXB2Ni1yZmMyNDYyYmlz
LTA4IFtBRERSQ09ORmJpc10gbmVlZHMgdG8gY2hhbmdlOg0KDQogICAgICAiRWFjaCBpbmRpdmlk
dWFsIHVuaWNhc3QgYWRkcmVzcyBTSE9VTEQgYmUgdGVzdGVkIGZvciB1bmlxdWVuZXNzLg0KICAg
ICAgTm90ZSB0aGF0IHRoZXJlIGFyZSBpbXBsZW1lbnRhdGlvbnMgZGVwbG95ZWQgdGhhdCBvbmx5
IHBlcmZvcm0NCiAgICAgIER1cGxpY2F0ZSBBZGRyZXNzIERldGVjdGlvbiBmb3IgdGhlIGxpbmst
bG9jYWwgYWRkcmVzcyBhbmQgc2tpcA0KICAgICAgdGhlIHRlc3QgZm9yIHRoZSBnbG9iYWwgYWRk
cmVzcyB1c2luZyB0aGUgc2FtZSBpbnRlcmZhY2UNCiAgICAgIGlkZW50aWZpZXIgYXMgdGhhdCBv
ZiB0aGUgbGluay1sb2NhbCBhZGRyZXNzLiAgV2hlcmVhcyB0aGlzDQogICAgICBkb2N1bWVudCBk
b2VzIG5vdCBpbnZhbGlkYXRlIHN1Y2ggaW1wbGVtZW50YXRpb25zLCB0aGlzIGtpbmQgb2YNCiAg
ICAgICdvcHRpbWl6YXRpb24nIGlzIE5PVCBSRUNPTU1FTkRFRCwgYW5kIG5ldyBpbXBsZW1lbnRh
dGlvbnMgTVVTVA0KICAgICAgTk9UIGRvIHRoYXQgb3B0aW1pemF0aW9uLiAgVGhpcyBvcHRpbWl6
YXRpb24gY2FtZSBmcm9tIHRoZQ0KICAgICAgYXNzdW1wdGlvbiB0aGF0IGFsbCBvZiBhbiBpbnRl
cmZhY2UncyBhZGRyZXNzZXMgYXJlIGdlbmVyYXRlZCBmcm9tDQogICAgICB0aGUgc2FtZSBpZGVu
dGlmaWVyLiAgSG93ZXZlciwgdGhlIGFzc3VtcHRpb24gZG9lcyBhY3R1YWxseSBub3QNCiAgICAg
IHN0YW5kOyBuZXcgdHlwZXMgb2YgYWRkcmVzc2VzIGhhdmUgYmVlbiBpbnRyb2R1Y2VkIHdoZXJl
IHRoZQ0KICAgICAgaW50ZXJmYWNlIGlkZW50aWZpZXJzIGFyZSBub3QgbmVjZXNzYXJpbHkgdGhl
IHNhbWUgZm9yIGFsbCB1bmljYXN0DQogICAgICBhZGRyZXNzZXMgb24gYSBzaW5nbGUgaW50ZXJm
YWNlIFtSRkMzMDQxXSBbUkZDMzk3Ml0uICBSZXF1aXJpbmcgdG8NCiAgICAgIHBlcmZvcm0gRHVw
bGljYXRlIEFkZHJlc3MgRGV0ZWN0aW9uIGZvciBhbGwgdW5pY2FzdCBhZGRyZXNzZXMgd2lsbA0K
ICAgICAgbWFrZSB0aGUgYWxnb3JpdGhtIHJvYnVzdCBmb3IgdGhlIGN1cnJlbnQgYW5kIGZ1dHVy
ZSBzdWNoIHNwZWNpYWwNCg0KDQoNClNpbmdoICYgQmVlYmVlICAgICAgICAgIEV4cGlyZXMgRGVj
ZW1iZXIgMjMsIDIwMDcgICAgICAgICAgICAgICBbUGFnZSA4XQ0KDA0KSW50ZXJuZXQtRHJhZnQg
ICAgICAgICBORCBJbXBsZW1lbnRhdGlvbiBQaXRmYWxscyAgICAgICAgICAgICAgSnVuZSAyMDA3
DQoNCg0KICAgICAgaW50ZXJmYWNlIGlkZW50aWZpZXJzLiINCg0KICAgdG8gcmVhZCBhcyBmb2xs
b3dzOg0KDQogICAgICBFYWNoIGluZGl2aWR1YWwgdW5pY2FzdCBhZGRyZXNzIE1VU1QgYmUgdGVz
dGVkIGZvciB1bmlxdWVuZXNzLg0KICAgICAgTm90ZSB0aGF0IHNvbWUgZGVwbG95ZWQgaW1wbGVt
ZW50YXRpb25zIHBlcmZvcm0gRHVwbGljYXRlIEFkZHJlc3MNCiAgICAgIERldGVjdGlvbiAoREFE
KSBvbmx5IGZvciB0aGUgbGluay1sb2NhbCBhZGRyZXNzIGFuZCBza2lwIHRoZSB0ZXN0DQogICAg
ICBmb3IgdGhlIGdsb2JhbCBhZGRyZXNzIHVzaW5nIHRoZSBzYW1lIGludGVyZmFjZSBpZGVudGlm
aWVyLiAgVGhpcw0KICAgICAgb3B0aW1pemF0aW9uIGNhbWUgZnJvbSB0aGUgYXNzdW1wdGlvbiB0
aGF0IGFsbCBvZiBhbiBpbnRlcmZhY2Uncw0KICAgICAgYWRkcmVzc2VzIGFyZSBnZW5lcmF0ZWQg
ZnJvbSB0aGUgc2FtZSBpbnRlcmZhY2UgaWRlbnRpZmllciAoc2VlDQogICAgICBSRkMgMjQ2MiBb
QUREUkNPTkZdKS4gIEhvd2V2ZXIsIGV2ZW4gd2l0aCB0aGlzIGFzc3VtcHRpb24sDQogICAgICBz
a2lwcGluZyBEQUQgZm9yIG5vbi1saW5rLWxvY2FsIGFkZHJlc3NlcyByZXByZXNlbnRzIGEgc2Vj
dXJpdHkNCiAgICAgIHByb2JsZW0uICBUaGlzIG9wdGltaXphdGlvbiBhbGxvd3MgYW4gaW50ZXJm
YWNlIHRvIGNsYWltIGENCiAgICAgIGR1cGxpY2F0ZSBhZGRyZXNzIGluIGEgd2F5IHRoYXQgd291
bGQgbm90IGJlIGRldGVjdGVkLiAgRm9yIGEgbW9yZQ0KICAgICAgZGV0YWlsZWQgZGVzY3JpcHRp
b24gb2YgdGhpcyBzZWN1cml0eSBwcm9ibGVtLCBzZWUgdGhlIEhvc3QgTW9kZWxzDQogICAgICBz
ZWN0aW9uIG9mIGRyYWZ0LXdiZWViZWUtbmQtaW1wbGVtZW50YXRpb24tcGl0ZmFsbHMtMDAuICBG
dXJ0aGVyLA0KICAgICAgbmV3IHR5cGVzIG9mIGFkZHJlc3NlcyBoYXZlIGJlZW4gaW50cm9kdWNl
ZCB3aGVyZSB0aGUgaW50ZXJmYWNlDQogICAgICBpZGVudGlmaWVycyBhcmUgbm90IG5lY2Vzc2Fy
aWx5IHRoZSBzYW1lIGZvciBhbGwgdW5pY2FzdCBhZGRyZXNzZXMNCiAgICAgIG9uIGEgc2luZ2xl
IGludGVyZmFjZSBbUkZDMzA0MV0gW1JGQzM5NzJdLiAgUmVxdWlyaW5nIGFuIGludGVyZmFjZQ0K
ICAgICAgdG8gcGVyZm9ybSBEQUQgZm9yIGFsbCB1bmljYXN0IGFkZHJlc3NlcyB3aWxsIG1ha2Ug
dGhlIGFsZ29yaXRobQ0KICAgICAgbW9yZSByb2J1c3QuICBFeGlzdGluZyBpbXBsZW1lbnRhdGlv
bnMgYXMgd2VsbCBhcyBuZXcNCiAgICAgIGltcGxlbWVudGF0aW9ucyBNVVNUIHRlc3QgZWFjaCBp
bmRpdmlkdWFsIHVuaWNhc3QgYWRkcmVzcyBmb3INCiAgICAgIHVuaXF1ZW5lc3MuDQoNCg0KNi4g
IFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIFRoZSBIb3N0IE1vZGVscyBzZWN0aW9uIG9m
IHRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHZhbGlkIGhvc3QNCiAgIGJlaGF2aW9yIGluIHJlc3Bv
bnNlIHRvIGEgc2VjdXJpdHkgdGhyZWF0IHdoZXJlIGEgcm9ndWUgbm9kZSBjYW4gc2VuZA0KICAg
UkFzIHdpdGggYSBWYWxpZCBMaWZldGltZSBvZiB6ZXJvLiAgSG9zdCBNb2RlbHMgYWxzbyBkZXNj
cmliZXMgYQ0KICAgc2VjdXJpdHkgcHJvYmxlbSB3aXRoIHNlY3Rpb24gNS40IG9mIFJGQyAyNDYy
IFtBRERSQ09ORl0gdGhhdCBjYW4NCiAgIGFsbG93IHR3byBob3N0cyB3aXRoIHRoZSBzYW1lIGFk
ZHJlc3MgdG8gYXZvaWQgREFEIGFuZCBjb21lIG9ubGluZSBvbg0KICAgdGhlIHNhbWUgbGluay4N
Cg0KDQo3LiAgSUFOQSBDb25zaWRlcmF0aW9ucw0KDQogICBOb25lLg0KDQoNCjguICBBY2tub3ds
ZWRnZW1lbnRzDQoNCiAgIFRoYW5rcyAoaW4gYWxwaGFiZXRpY2FsIG9yZGVyKSB0byBBZGVlbCBB
aG1lZCwgQWx1biBFdmFucywgQmVybmllDQogICBWb2x6LCBEYXZlIEZvcnN0ZXIsIE1hZGh1IFN1
ZGFuLCBQcmFzaGFudGggS3Jpc2huYW11cnRoeSwgYW5kIFJhbHBoDQogICBEcm9tcyBvZiBDaXNj
bywgZm9yIHRoZWlyIGNvbnNpc3RlbnQgaW5wdXQsIGlkZWFzIGFuZCByZXZpZXcgZHVyaW5nDQog
ICB0aGUgcHJvZHVjdGlvbiBvZiB0aGlzIGRvY3VtZW50Lg0KDQoNCg0KDQoNClNpbmdoICYgQmVl
YmVlICAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjMsIDIwMDcgICAgICAgICAgICAgICBbUGFn
ZSA5XQ0KDA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICBORCBJbXBsZW1lbnRhdGlvbiBQaXRmYWxs
cyAgICAgICAgICAgICAgSnVuZSAyMDA3DQoNCg0KOS4gIFJlZmVyZW5jZXMNCg0KOS4xLiAgTm9y
bWF0aXZlIFJlZmVyZW5jZXMNCg0KICAgW0FERFJDT05GXQ0KICAgICAgICAgICAgICBUaG9tc29u
LCBTLiBhbmQgVC4gTmFydGVuLCAiSVB2NiBBZGRyZXNzIGF1dG9jb25maWd1cmF0aW9uDQogICAg
ICAgICAgICAgIChJUHY2KSIsIFJGQyAyNDYyLCBEZWNlbWJlciAxOTk4Lg0KDQogICBbTkRdICAg
ICAgIE5hcnRlbiwgVC4sIE5vcmRtYXJrLCBFLiwgYW5kIFcuIFNpbXBzb24sICJOZWlnaGJvcg0K
ICAgICAgICAgICAgICBEaXNjb3ZlcnkgZm9yIElQIFZlcnNpb24gNiAoSVB2NikiLCBSRkMgMjQ2
MSwNCiAgICAgICAgICAgICAgRGVjZW1iZXIgMTk5OC4NCg0KOS4yLiAgSW5mb3JtYXRpdmUgUmVm
ZXJlbmNlcw0KDQogICBbQUREUkNPTkZiaXNdDQogICAgICAgICAgICAgIFRob21zb24sIFMuLCBO
YXJ0ZW4sIFQuLCBhbmQgVC4gSmlubWVpLCAiSVB2NiBBZGRyZXNzDQogICAgICAgICAgICAgIGF1
dG9jb25maWd1cmF0aW9uIChJUHY2KSIsDQogICAgICAgICAgICAgIGRyYWZ0LWlldGYtaXB2Ni1y
ZmMyNDYyYmlzLTA4IChXb3JrIEluIFByb2dyZXNzKSwNCiAgICAgICAgICAgICAgTWF5IDIwMDUu
DQoNCiAgIFtJLkQuaWV0Zi12Nm9wcy1vbmxpbmthc3N1bXB0aW9uc10NCiAgICAgICAgICAgICAg
Um95LCBTLiwgRHVyYW5kLCBBLiwgYW5kIEouIFBhdWdoLCAiSVB2NiBOZWlnaGJvcg0KICAgICAg
ICAgICAgICBEaXNjb3ZlcnkgT24tTGluayBBc3N1bXB0aW9uIENvbnNpZGVyZWQgSGFybWZ1bCAo
SVB2NikiLA0KICAgICAgICAgICAgICBkcmFmdC1pZXRmLXY2b3BzLW9ubGlua2Fzc3VtcHRpb24t
MDQgKFdvcmsgSW4gUHJvZ3Jlc3MpLA0KICAgICAgICAgICAgICBKYW51YXJ5IDIwMDcuDQoNCiAg
IFtORGJpc10gICAgTmFydGVuLCBULiwgTm9yZG1hcmssIEUuLCBTaW1wc29uLCBXLiwgYW5kIEgu
IFNvbGltYW4sDQogICAgICAgICAgICAgICJOZWlnaGJvciBEaXNjb3ZlcnkgZm9yIElQIFZlcnNp
b24gNiAoSVB2NikiLA0KICAgICAgICAgICAgICBkcmFmdC1pZXRmLWlwdjYtMjQ2MWJpcy0xMSAo
V29yayBJbiBQcm9ncmVzcyksIE1hcmNoIDIwMDcuDQoNCg0KQXV0aG9ycycgQWRkcmVzc2VzDQoN
CiAgIEhlbWFudCBTaW5naA0KICAgQ2lzY28gU3lzdGVtcywgSW5jLg0KICAgMTQxNCBNYXNzYWNo
dXNldHRzIEF2ZS4NCiAgIEJveGJvcm91Z2gsIE1BICAwMTcxOQ0KICAgVVNBDQoNCiAgIFBob25l
OiArMSA5NzggOTM2IDE2MjINCiAgIEVtYWlsOiBzaGVtYW50QGNpc2NvLmNvbQ0KICAgVVJJOiAg
IGh0dHA6Ly93d3cuY2lzY28uY29tLw0KDQoNCg0KDQoNCg0KDQoNCg0KU2luZ2ggJiBCZWViZWUg
ICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAyMywgMjAwNyAgICAgICAgICAgICAgW1BhZ2UgMTBd
DQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgIE5EIEltcGxlbWVudGF0aW9uIFBpdGZhbGxzICAg
ICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQogICBXZXMgQmVlYmVlDQogICBDaXNjbyBTeXN0ZW1z
LCBJbmMuDQogICAxNDE0IE1hc3NhY2h1c2V0dHMgQXZlLg0KICAgQm94Ym9yb3VnaCwgTUEgIDAx
NzE5DQogICBVU0ENCg0KICAgUGhvbmU6ICsxIDk3OCA5MzYgMjAzMA0KICAgRW1haWw6IHdiZWVi
ZWVAY2lzY28uY29tDQogICBVUkk6ICAgaHR0cDovL3d3dy5jaXNjby5jb20vDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQpTaW5naCAmIEJlZWJlZSAgICAgICAgICBFeHBpcmVzIERlY2VtYmVy
IDIzLCAyMDA3ICAgICAgICAgICAgICBbUGFnZSAxMV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAg
ICAgTkQgSW1wbGVtZW50YXRpb24gUGl0ZmFsbHMgICAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoN
CkZ1bGwgQ29weXJpZ2h0IFN0YXRlbWVudA0KDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJRVRGIFRy
dXN0ICgyMDA3KS4NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIHRoZSByaWdodHMs
IGxpY2Vuc2VzIGFuZCByZXN0cmljdGlvbnMNCiAgIGNvbnRhaW5lZCBpbiBCQ1AgNzgsIGFuZCBl
eGNlcHQgYXMgc2V0IGZvcnRoIHRoZXJlaW4sIHRoZSBhdXRob3JzDQogICByZXRhaW4gYWxsIHRo
ZWlyIHJpZ2h0cy4NCg0KICAgVGhpcyBkb2N1bWVudCBhbmQgdGhlIGluZm9ybWF0aW9uIGNvbnRh
aW5lZCBoZXJlaW4gYXJlIHByb3ZpZGVkIG9uIGFuDQogICAiQVMgSVMiIGJhc2lzIGFuZCBUSEUg
Q09OVFJJQlVUT1IsIFRIRSBPUkdBTklaQVRJT04gSEUvU0hFIFJFUFJFU0VOVFMNCiAgIE9SIElT
IFNQT05TT1JFRCBCWSAoSUYgQU5ZKSwgVEhFIElOVEVSTkVUIFNPQ0lFVFksIFRIRSBJRVRGIFRS
VVNUIEFORA0KICAgVEhFIElOVEVSTkVUIEVOR0lORUVSSU5HIFRBU0sgRk9SQ0UgRElTQ0xBSU0g
QUxMIFdBUlJBTlRJRVMsIEVYUFJFU1MNCiAgIE9SIElNUExJRUQsIElOQ0xVRElORyBCVVQgTk9U
IExJTUlURUQgVE8gQU5ZIFdBUlJBTlRZIFRIQVQgVEhFIFVTRSBPRg0KICAgVEhFIElORk9STUFU
SU9OIEhFUkVJTiBXSUxMIE5PVCBJTkZSSU5HRSBBTlkgUklHSFRTIE9SIEFOWSBJTVBMSUVEDQog
ICBXQVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElUWSBPUiBGSVRORVNTIEZPUiBBIFBBUlRJQ1VM
QVIgUFVSUE9TRS4NCg0KDQpJbnRlbGxlY3R1YWwgUHJvcGVydHkNCg0KICAgVGhlIElFVEYgdGFr
ZXMgbm8gcG9zaXRpb24gcmVnYXJkaW5nIHRoZSB2YWxpZGl0eSBvciBzY29wZSBvZiBhbnkNCiAg
IEludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMgb3Igb3RoZXIgcmlnaHRzIHRoYXQgbWlnaHQg
YmUgY2xhaW1lZCB0bw0KICAgcGVydGFpbiB0byB0aGUgaW1wbGVtZW50YXRpb24gb3IgdXNlIG9m
IHRoZSB0ZWNobm9sb2d5IGRlc2NyaWJlZCBpbg0KICAgdGhpcyBkb2N1bWVudCBvciB0aGUgZXh0
ZW50IHRvIHdoaWNoIGFueSBsaWNlbnNlIHVuZGVyIHN1Y2ggcmlnaHRzDQogICBtaWdodCBvciBt
aWdodCBub3QgYmUgYXZhaWxhYmxlOyBub3IgZG9lcyBpdCByZXByZXNlbnQgdGhhdCBpdCBoYXMN
CiAgIG1hZGUgYW55IGluZGVwZW5kZW50IGVmZm9ydCB0byBpZGVudGlmeSBhbnkgc3VjaCByaWdo
dHMuICBJbmZvcm1hdGlvbg0KICAgb24gdGhlIHByb2NlZHVyZXMgd2l0aCByZXNwZWN0IHRvIHJp
Z2h0cyBpbiBSRkMgZG9jdW1lbnRzIGNhbiBiZQ0KICAgZm91bmQgaW4gQkNQIDc4IGFuZCBCQ1Ag
NzkuDQoNCiAgIENvcGllcyBvZiBJUFIgZGlzY2xvc3VyZXMgbWFkZSB0byB0aGUgSUVURiBTZWNy
ZXRhcmlhdCBhbmQgYW55DQogICBhc3N1cmFuY2VzIG9mIGxpY2Vuc2VzIHRvIGJlIG1hZGUgYXZh
aWxhYmxlLCBvciB0aGUgcmVzdWx0IG9mIGFuDQogICBhdHRlbXB0IG1hZGUgdG8gb2J0YWluIGEg
Z2VuZXJhbCBsaWNlbnNlIG9yIHBlcm1pc3Npb24gZm9yIHRoZSB1c2Ugb2YNCiAgIHN1Y2ggcHJv
cHJpZXRhcnkgcmlnaHRzIGJ5IGltcGxlbWVudGVycyBvciB1c2VycyBvZiB0aGlzDQogICBzcGVj
aWZpY2F0aW9uIGNhbiBiZSBvYnRhaW5lZCBmcm9tIHRoZSBJRVRGIG9uLWxpbmUgSVBSIHJlcG9z
aXRvcnkgYXQNCiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaXByLg0KDQogICBUaGUgSUVURiBpbnZp
dGVzIGFueSBpbnRlcmVzdGVkIHBhcnR5IHRvIGJyaW5nIHRvIGl0cyBhdHRlbnRpb24gYW55DQog
ICBjb3B5cmlnaHRzLCBwYXRlbnRzIG9yIHBhdGVudCBhcHBsaWNhdGlvbnMsIG9yIG90aGVyIHBy
b3ByaWV0YXJ5DQogICByaWdodHMgdGhhdCBtYXkgY292ZXIgdGVjaG5vbG9neSB0aGF0IG1heSBi
ZSByZXF1aXJlZCB0byBpbXBsZW1lbnQNCiAgIHRoaXMgc3RhbmRhcmQuICBQbGVhc2UgYWRkcmVz
cyB0aGUgaW5mb3JtYXRpb24gdG8gdGhlIElFVEYgYXQNCiAgIGlldGYtaXByQGlldGYub3JnLg0K
DQoNCkFja25vd2xlZGdtZW50DQoNCiAgIEZ1bmRpbmcgZm9yIHRoZSBSRkMgRWRpdG9yIGZ1bmN0
aW9uIGlzIHByb3ZpZGVkIGJ5IHRoZSBJRVRGDQogICBBZG1pbmlzdHJhdGl2ZSBTdXBwb3J0IEFj
dGl2aXR5IChJQVNBKS4NCg0KDQoNCg0KDQpTaW5naCAmIEJlZWJlZSAgICAgICAgICBFeHBpcmVz
IERlY2VtYmVyIDIzLCAyMDA3ICAgICAgICAgICAgICBbUGFnZSAxMl0NCgwNCg0K

------_=_NextPart_001_01C7B424.08BAD842
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

------_=_NextPart_001_01C7B424.08BAD842--




From ipv6-bounces@ietf.org Thu Jun 21 14:03:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1R0I-0000J4-4q; Thu, 21 Jun 2007 14:03:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1R0G-0000Iy-Lo
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:03:32 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1R0F-0003rp-D6
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:03:32 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 7A6D911429
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 18:03:30 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 21 Jun 2007 09:00:03 MST."
	<467AA083.6070102@internap.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 21 Jun 2007 18:03:30 +0000
Message-ID: <28803.1182449010@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > Scott, what feature of existing ULAs makes them unsuitable for this
> > usage today? In the ridiculously unlikely event of a ULA prefix clash,
> > this would be detected up-front when trying to set up the reverse
> > delegation, and then you'd simply generate a different ULA prefix.

> As far as I know there's no mechanism to delegate reverse DNS for a locally
> generated ULA, since there's no "ownership".  IMO any move to start
> delegating .arpa authority for ULAs would be de facto ULA-C, so if we're
> going to do that we should do it right and do the other registration
> functions that should go along with the DNS delegation.

not to disparage either participant shown above personally, but, this
argument is beyond nuttiness.  mark andrews has a draft out about local
domain name service for RFC 1918, and his fundamental observation is
that there is no need for the resolution perimeter of a PTR to differ
from the routing perimeter of the IP address described by that PTR.  yet
here we have a large set of folks who unlike mark andrews are not experts
at DNS, telling us that yes we do need to be able to resolve a PTR from
places where the addresses won't be routable, and then using this ignorant
and false assertion to justify a global registry of unique but unreachable
address blocks, each having its own globally reachable nameservers for PTRs.

what's wrong with this picture?  is there a use case we can all study?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 14:42:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Rc0-0001RT-LG; Thu, 21 Jun 2007 14:42:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Rby-0001RO-T4
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:42:30 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Rby-0005xt-JX
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:42:30 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out3.apple.com (Postfix) with ESMTP id EE6C99B2477
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 11:42:29 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id DEA0A3007D
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 11:42:29 -0700 (PDT)
X-AuditID: 11807125-a0d8bbb000006c02-eb-467ac695ae59
Received: from [17.206.50.68] (il0602f-dhcp68.apple.com [17.206.50.68])
	by relay7.apple.com (Apple SCV relay) with ESMTP id CA6E330076
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 11:42:29 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <28803.1182449010@sa.vix.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 21 Jun 2007 11:42:28 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 21, 2007, at 11:03, Paul Vixie wrote:
>
> mark andrews has [observed] that there is no need for the  
> resolution perimeter of a PTR to differ from the routing perimeter  
> of the IP address described by that PTR.  yet here we have a large  
> set of folks who [are] telling us that yes we do need to be able to  
> resolve a PTR from places where the addresses won't be routable
> [...]
> what's wrong with this picture?

My heretical opinion follows.

We successfully deprecated site-local unicast addressing by painting  
it with the stink of IPv4 network address translation.  However, we  
retained the technical consensus that unreachable nodes still need to  
be uniquely addressable, and what's more: these unreachable global  
scope unicast addresses must be assigned from a registry with a  
single global root.

My heretical opinion is that the second technical consensus is  
wrong.  We should deprecate the 'L' bit in the ULA address type and  
make all ULA into locally allocated addresses.  That way, we will  
have carved off a well-known prefix (like all the other non-routable  
prefixes) where nodes are neither uniquely addressable nor reachable  
on the public Internet.  I contend the 'L' bit was never a good idea;  
it was a placeholder for those wishing to retain network address  
translation in IPv6.  There, I said it.

I view all these attempts to establish a global registry for  
allocating unreachable, yet uniquely addressable (from the public  
Internet) unicast addresses with suspicion.  Arguments about the  
unacceptability of the birthday paradox risk in an prefix designator  
space with 2^40 possible birthdays seem to be driven either by 1) a  
frightening level of innumeracy, or 2) an ulterior motive that  
proponents cannot admit publicly.  I fail to see any other alternatives.

It boggles my mind that so many smart people seem to believe that ULA- 
C is absolutely necessary to the operability of the IPv6 Internet.  I  
keep asking to see an explanation for why the risk of collision is  
unacceptable, and nobody seems to be able to point me toward it.  If  
what you really want is to have IPv6 NAT, then let's see the real  
arguments for why you want that.  If any of them aren't properly  
addressed in RFC 4864 and draft-ietf-v6ops-scanning- 
implications-03.txt, then let's figure out what to do about it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 14:54:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Rmw-0005Zc-SR; Thu, 21 Jun 2007 14:53:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Rmv-0005ZX-A0
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:53:49 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Rmt-0000c9-GS
	for ipv6@ietf.org; Thu, 21 Jun 2007 14:53:49 -0400
Received: from [192.168.2.100] (blobby.bind.org [82.92.138.66])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5LIriAi002987
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 21 Jun 2007 11:53:46 -0700
In-Reply-To: <46796246.4050705@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Thu, 21 Jun 2007 20:53:41 +0200
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20 Jun 2007, at 7:22pm, Scott Leibrand wrote:

[...]

>> So am I right in reading your answer as saying that the advantage  
>> of ULA-C is that it solves the same problem that ARIN's IPv6 PI  
>> policy solves but better. In effect, developing ULA-C helps side- 
>> step ARIN's policy development process?
>>
> No, it solves a similar problem for a different (though possibly  
> partially overlapping) set of networks, and reduces the pressure to  
> apply a hammer when a screwdriver is what's really needed.

I am not sure I understand what you mean by applying a hammer. How is  
ULA-C a screwdriver?

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 15:26:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1SHp-0005Cz-GI; Thu, 21 Jun 2007 15:25:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1SHo-0005Cu-TN
	for ipv6@ietf.org; Thu, 21 Jun 2007 15:25:44 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1SHn-0001ux-94
	for ipv6@ietf.org; Thu, 21 Jun 2007 15:25:44 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 21 Jun 2007 14:25:41 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A063141066707074@mail>
In-Reply-To: <6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt use case
Thread-Index: Ace0NBizpLQNHbk5Tbu8DVunmxRg3wAAzTDA
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Subject: RE: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I concur wholeheartedly on all points.  If one wants a universally
visable address use PI .  With IPv6 if an organization cannot or refuses
to get their own PI space they can get space from their provider.  When
they choose to change providers they are not renumbering, they are just
re-prefixing..  I don't think it will be that painful. =20

Hosts with no need to contact the world can use ULA..  hosts that need
to contact the world directly can use PI.  Simple proposition.

For the folks that really want to use NATv6 I don't see anything
preventing them from doing it.  It doesn't make any sense to me but then
it doesn't have to.  They can do whatever they want within their network
boundaries and they don't have to ask anyone.  I see no reason for a
rule legitimizing a policy that is already within the sysadmin's purvue.

Publicly advertised address and/or defined space should be public
address space and routable.  Unrouted address space does not need to be
publicly advertised or defined.  I see no reason to complicate that.

Kevin

:$s/worry/happy/g=20

=20

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Thursday, June 21, 2007 1:42 PM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
>=20
> On Jun 21, 2007, at 11:03, Paul Vixie wrote:
> >
> > mark andrews has [observed] that there is no need for the=20
> resolution=20
> > perimeter of a PTR to differ from the routing perimeter of the IP=20
> > address described by that PTR.  yet here we have a large=20
> set of folks=20
> > who [are] telling us that yes we do need to be able to=20
> resolve a PTR=20
> > from places where the addresses won't be routable [...]=20
> what's wrong=20
> > with this picture?
>=20
> My heretical opinion follows.
>=20
> We successfully deprecated site-local unicast addressing by=20
> painting it with the stink of IPv4 network address=20
> translation.  However, we retained the technical consensus=20
> that unreachable nodes still need to be uniquely addressable,=20
> and what's more: these unreachable global scope unicast=20
> addresses must be assigned from a registry with a single global root.
>=20
> My heretical opinion is that the second technical consensus=20
> is wrong.  We should deprecate the 'L' bit in the ULA address=20
> type and make all ULA into locally allocated addresses.  That=20
> way, we will have carved off a well-known prefix (like all=20
> the other non-routable
> prefixes) where nodes are neither uniquely addressable nor=20
> reachable on the public Internet.  I contend the 'L' bit was=20
> never a good idea; it was a placeholder for those wishing to=20
> retain network address translation in IPv6.  There, I said it.
>=20
> I view all these attempts to establish a global registry for=20
> allocating unreachable, yet uniquely addressable (from the public
> Internet) unicast addresses with suspicion.  Arguments about=20
> the unacceptability of the birthday paradox risk in an prefix=20
> designator space with 2^40 possible birthdays seem to be=20
> driven either by 1) a frightening level of innumeracy, or 2)=20
> an ulterior motive that proponents cannot admit publicly.  I=20
> fail to see any other alternatives.
>=20
> It boggles my mind that so many smart people seem to believe=20
> that ULA- C is absolutely necessary to the operability of the=20
> IPv6 Internet.  I keep asking to see an explanation for why=20
> the risk of collision is unacceptable, and nobody seems to be=20
> able to point me toward it.  If what you really want is to=20
> have IPv6 NAT, then let's see the real arguments for why you=20
> want that.  If any of them aren't properly addressed in RFC=20
> 4864 and draft-ietf-v6ops-scanning- implications-03.txt, then=20
> let's figure out what to do about it.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 15:49:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Se6-0001wM-3K; Thu, 21 Jun 2007 15:48:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Se4-0001wC-9J
	for ipv6@ietf.org; Thu, 21 Jun 2007 15:48:44 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Se3-0001G8-Uz
	for ipv6@ietf.org; Thu, 21 Jun 2007 15:48:44 -0400
Received: from [208.73.31.18] (account sleibrand@mail.internap.com HELO
	[10.198.243.159])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84786132; Thu, 21 Jun 2007 15:48:43 -0400
Message-ID: <467AD617.3020606@internap.com>
Date: Thu, 21 Jun 2007 12:48:39 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>
In-Reply-To: <28803.1182449010@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul Vixie wrote:
>
>> As far as I know there's no mechanism to delegate reverse DNS for a locally
>> generated ULA, since there's no "ownership".  IMO any move to start
>> delegating .arpa authority for ULAs would be de facto ULA-C, so if we're
>> going to do that we should do it right and do the other registration
>> functions that should go along with the DNS delegation.
>>     
>
> not to disparage either participant shown above personally, but, this
> argument is beyond nuttiness.  mark andrews has a draft out about local
> domain name service for RFC 1918, and his fundamental observation is
> that there is no need for the resolution perimeter of a PTR to differ
> from the routing perimeter of the IP address described by that PTR.  

Feel free to disparage me as a newbie as appropriate.  :-) 

Can you point me to the name of the referenced I-D?  Unfortunately I 
haven't had time to closely follow new I-D's, and am only involved in 
this discussion because of my ARIN PPML involvement.

> yet here we have a large set of folks who unlike mark andrews are not experts
> at DNS, telling us that yes we do need to be able to resolve a PTR from
> places where the addresses won't be routable, and then using this ignorant
> and false assertion to justify a global registry of unique but unreachable
> address blocks, each having its own globally reachable nameservers for PTRs.
>
> what's wrong with this picture?  is there a use case we can all study?
>
>   
Maybe the I-D answers this, but how do you resolve PTRs for some random 
section of .arpa if you don't have glue NS records pointing you to the 
name servers for that subdomain?  In terms of use case, say my network 
connects privately to a network using ULAs.  I traceroute to a host on 
that network, and try to resolve PTRs for the ULA block.  If the block 
is ULA-C, my DNS server (which may be a completely independent local 
instance of BIND without forwarders) can traverse the tree from the 
root, get the proper delegations to the NS's for the ULA-C (which will 
need to be on public IPs), and resolve the PTRs.  If the block is local 
ULA, however, I don't know how my independent local resolver is supposed 
to find out which name servers are authoritative for the ULA block.

I guess what it comes down to is that the intended use case for ULA-C is 
to connect a bunch of companies with private address space on a private 
network.  In that kind of use case, close integration of DNS 
infrastructure seems unlikely, so without delegating DNS authority from 
the root, I don't see how you can provide good reverse DNS resolution in 
such a use case.  Therefore, I support draft-ietf-ipv6-ula-central-02's 
requirement to support DNS delegation, with the caveat that such 
delegation must be to public addresses (that NS records should not point 
to ULAs).

Thanks,
Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 16:06:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Sv0-000103-TV; Thu, 21 Jun 2007 16:06:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Suz-0000zT-2P
	for ipv6@ietf.org; Thu, 21 Jun 2007 16:06:13 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Suy-0004t6-N9
	for ipv6@ietf.org; Thu, 21 Jun 2007 16:06:13 -0400
Received: from [208.73.31.18] (account sleibrand@mail.internap.com HELO
	[10.198.243.159])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84787406; Thu, 21 Jun 2007 16:06:12 -0400
Message-ID: <467ADA2F.6060100@internap.com>
Date: Thu, 21 Jun 2007 13:06:07 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
In-Reply-To: <E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Leo Vegoda wrote:
> On 20 Jun 2007, at 7:22pm, Scott Leibrand wrote:
>
>>> So am I right in reading your answer as saying that the advantage of 
>>> ULA-C is that it solves the same problem that ARIN's IPv6 PI policy 
>>> solves but better. In effect, developing ULA-C helps side-step 
>>> ARIN's policy development process?
>>>
>> No, it solves a similar problem for a different (though possibly 
>> partially overlapping) set of networks, and reduces the pressure to 
>> apply a hammer when a screwdriver is what's really needed.
>
> I am not sure I understand what you mean by applying a hammer. How is 
> ULA-C a screwdriver?
>
Fair enough.  Currently, ARIN PI policy requires that to qualify for 
IPv6 PI space, you meet the requirements for IPv4 PI space, which is 
that you must be multihomed (running BGP) and qualify for a /22, or you 
must qualify for a /20.  The justification for this is that, since such 
a PI allocation usually ends up in the Internet routing tables (the 
DFZ), we should have a standard that limits the number of blocks given 
out, and gives them out to networks that somehow justify a slot in 
everyone's routing tables.

There are a number of smaller networks that wish to avoid "provider 
lock-in" by avoiding the perceived difficulty of renumbering their 
infrastructure when switching providers (and hence PA blocks), and who 
perceive the current policy as unfair.  As a result, there are proposals 
on ARIN's PPML at least once a year to liberalize ARIN's PI policy in 
some fashion.  Some of these have succeeded, such as the move to change 
the smallest block allocated down to a /22 (from a /20 before, IIRC).  
Others have not, due to pushback from operators concerned about 
increasing the rate of growth of the routing table.

For many smaller networks, the real goal is stable addressing, not the 
ability to route their netblock across the entire DFZ.  Therefore, I 
believe some of those networks would be well served by ULA-C space.  
Since such space does not impose a cost on third party operators, it can 
be given out freely. 

If ULA-C is not available, I believe many of those networks will instead 
push for PI space.  Once they get it, the path of least resistance is 
announcing it globally, so most recipients of PI space will do so, 
increasing pressure on the routing table and requiring more rapid 
upgrades (to replace all Supervisor2's in Cisco 6500/7600s running BGP, 
for example).

If ULA-C is available, I believe many networks will be able to use it to 
number their internal infrastructure, and simply use some sort of NAT to 
translate that into their current PA block when traffic sourced from 
their routers passes out onto the Internet.  They can dynamically assign 
their customers/hosts PA space with DHCP, so that end-to-end 
connectivity never needs to be NAT'd.

Much of this can also be done with ULA-L, but I believe that the lack of 
"ownership" and the inability to do proper reverse DNS makes that 
solution not quite as good as ULA-C for many networks.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 17:24:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1U83-0000WK-RB; Thu, 21 Jun 2007 17:23:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1U82-0000WF-Ux
	for ipv6@ietf.org; Thu, 21 Jun 2007 17:23:46 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1U81-0000yz-Jz
	for ipv6@ietf.org; Thu, 21 Jun 2007 17:23:46 -0400
Received: from [192.168.2.103] (blobby.bind.org [82.92.138.66])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5LLNgAv003656
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 21 Jun 2007 14:23:44 -0700
In-Reply-To: <467ADA2F.6060100@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
	<467ADA2F.6060100@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Thu, 21 Jun 2007 23:23:42 +0200
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 21 Jun 2007, at 10:06pm, Scott Leibrand wrote:

[...]

> If ULA-C is not available, I believe many of those networks will  
> instead push for PI space.  Once they get it, the path of least  
> resistance is announcing it globally, so most recipients of PI  
> space will do so, increasing pressure on the routing table and  
> requiring more rapid upgrades (to replace all Supervisor2's in  
> Cisco 6500/7600s running BGP, for example).

History shows us that lots of legacy IPv4 assignments are not visible  
in routeviews, RIS and other BGP route collecting projects. Why would  
IPv6 be different?

> If ULA-C is available, I believe many networks will be able to use  
> it to number their internal infrastructure, and simply use some  
> sort of NAT to translate that into their current PA block when  
> traffic sourced from their routers passes out onto the Internet.   
> They can dynamically assign their customers/hosts PA space with  
> DHCP, so that end-to-end connectivity never needs to be NAT'd.
>
> Much of this can also be done with ULA-L, but I believe that the  
> lack of "ownership" and the inability to do proper reverse DNS  
> makes that solution not quite as good as ULA-C for many networks.

I wouldn't be surprised if some folks saw the lack of an external  
root for regular ULAs as an advantage. And while I appreciate that  
routing table growth is expensive, should we be encouraging people to  
NAT the interfaces on their internal routing infrastructure?

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 18:28:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1V83-0007Ej-N8; Thu, 21 Jun 2007 18:27:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1V81-0007EW-LY
	for ipv6@ietf.org; Thu, 21 Jun 2007 18:27:49 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I1V7w-00071I-UW
	for ipv6@ietf.org; Thu, 21 Jun 2007 18:27:49 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5LMRY1I002394
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 21 Jun 2007 15:27:34 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5LMRXYD019385; Thu, 21 Jun 2007 15:27:33 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5LMRXl1019380; Thu, 21 Jun 2007 15:27:33 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 15:27:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 15:26:34 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0Sp3hf1tn5iLBSNq9WPvSMbHcgQACBBVw
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi><D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com><2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org><46785A65.7060505@internap.com><F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com><E72F5476-D072-44B6-A848-F206C15BBC22@icann.org><467ADA2F.6060100@internap.com>
	<1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Leo Vegoda" <leo.vegoda@icann.org>,
	"Scott Leibrand" <sleibrand@internap.com>
X-OriginalArrivalTime: 21 Jun 2007 22:27:33.0611 (UTC)
	FILETIME=[5CD533B0:01C7B453]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Maybe I am missing the point, but there seems to be
an implication that ULA-C necessarily implies IPv6
NAT; am I misinterpreting? If not, then I don't quite
understand why this implication is being drawn. Can
someone please explain?

Thanks - Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 18:43:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1VN5-0003u1-7L; Thu, 21 Jun 2007 18:43:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1VN3-0003tw-LX
	for ipv6@ietf.org; Thu, 21 Jun 2007 18:43:21 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1VN3-0007J5-BV
	for ipv6@ietf.org; Thu, 21 Jun 2007 18:43:21 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id D110411426
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 22:43:20 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 21 Jun 2007 12:48:39 MST."
	<467AD617.3020606@internap.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
	<467AD617.3020606@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 21 Jun 2007 22:43:20 +0000
Message-ID: <62901.1182465800@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Can you point me to the name of the referenced I-D?  ...

http://www.ietf.org/internet-drafts/draft-ietf-dnsop-default-local-zones-02.txt

> > what's wrong with this picture?  is there a use case we can all study?
>
> Maybe the I-D answers this, but how do you resolve PTRs for some random
> section of .arpa if you don't have glue NS records pointing you to the name
> servers for that subdomain?

by asking for a use case, i'm pointing out that if you can't be reached by
an ip packet from "there", then your need to look up a PTR corresponding to
an address in "there" is unfathomable.

> I guess what it comes down to is that the intended use case for ULA-C is to
> connect a bunch of companies with private address space on a private
> network.

the idea that someone would only need PI for "public networking" is bizarre.
quite a lot of normal IPv4 space is never advertised into the "default free
zone" but it's universally unique and used "privately" with passion & verve,
and there is no reason to expect that IPv6 PI won't be used the same way.

a global RIR policy to support this "private network" use case would suggest
that each RIR lay aside a /32 worth of space that was meant to be carved up
in /48 chunks for folks who needed smaller chunks of address space for private
networking, with advice to the community that no address space in these /32's
be advertised to the DFZ, and that it be filtered out if seen in the DFZ.  an
RIR could theoretically come up with a "private space only" membership class
with lower fees.  whois and PTR-space NS RRsets would be managed normally.

i think the disconnect here is that a lot of folks are assuming that the RIR
system only allocates "public" address space.  that's not true today, and it
never has been true (compare historical allocations vs. DFZ advertisements),
and there's no reason to try to make it true or to assume that it ever will
be true.  RIRs allocate universally unique space.  how it's used (public vs.
private) is not an RIR concern.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 19:11:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Vo4-0000oU-R7; Thu, 21 Jun 2007 19:11:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Vo3-0000oI-Df
	for ipv6@ietf.org; Thu, 21 Jun 2007 19:11:15 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Vo2-0003kD-55
	for ipv6@ietf.org; Thu, 21 Jun 2007 19:11:15 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 8B03A9F3064
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 16:11:13 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 7905F100A4
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 16:11:13 -0700 (PDT)
X-AuditID: 11807124-a2548bb000002544-08-467b05919b4d
Received: from [17.206.50.68] (il0602f-dhcp68.apple.com [17.206.50.68])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 6748110066
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 16:11:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
	<467ADA2F.6060100@internap.com>
	<1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 21 Jun 2007 16:11:12 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 21, 2007, at 15:26, Templin, Fred L wrote:
>
> Maybe I am missing the point, but there seems to be an implication  
> that ULA-C necessarily implies IPv6 NAT; am I misinterpreting? If  
> not, then I don't quite understand why this implication is being  
> drawn. Can someone please explain?

I'm not going so far as to say the implication is there.  I'm just  
have a very difficult time taking seriously the concern about merge  
risks associated with renumbering due to the birthday paradox in a  
2^40 number space without something more substantial to go on than a  
bald-faced assertion that any small but non-zero probability of  
collision is unacceptable.  The alternative explanation that makes  
the most sense to me is that some influential organizations, which  
are too small to warrant their own PI space, are resisting migration  
to IPv6 unless they can use NAT with private addresses, and they  
won't [or can't] explain why the arguments in RFC 4864 and draft-ietf- 
v6ops-scanning-implications-03.txt are failing to persuade them.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 20:13:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Wlr-0004lb-Sy; Thu, 21 Jun 2007 20:13:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Wlq-0004lV-4R
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:13:02 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Wlo-0006Yz-Qe
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:13:02 -0400
Received: from [208.73.31.18] (account sleibrand@mail.internap.com HELO
	[10.198.243.159])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84813563 for ipv6@ietf.org;
	Thu, 21 Jun 2007 20:13:00 -0400
Message-ID: <467B1407.90609@internap.com>
Date: Thu, 21 Jun 2007 17:12:55 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>	<467ADA2F.6060100@internap.com>	<1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
	<5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
In-Reply-To: <5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

james woodyatt wrote:
> On Jun 21, 2007, at 15:26, Templin, Fred L wrote:
>>
>> Maybe I am missing the point, but there seems to be an implication 
>> that ULA-C necessarily implies IPv6 NAT; am I misinterpreting? If 
>> not, then I don't quite understand why this implication is being 
>> drawn. Can someone please explain?
>
No, ULA-C doesn't require NAT, any more than RFC 1918 or ULA-L space does.

> I'm not going so far as to say the implication is there.  I'm just 
> have a very difficult time taking seriously the concern about merge 
> risks associated with renumbering due to the birthday paradox in a 
> 2^40 number space without something more substantial to go on than a 
> bald-faced assertion that any small but non-zero probability of 
> collision is unacceptable.

That assertion has been made, but I don't think we can treat it as 
anything more than a preference by non-technical business people.

>   The alternative explanation that makes the most sense to me is that 
> some influential organizations, which are too small to warrant their 
> own PI space, are resisting migration to IPv6 unless they can use NAT 
> with private addresses, and they won't [or can't] explain why the 
> arguments in RFC 4864 and 
> draft-ietf-v6ops-scanning-implications-03.txt are failing to persuade 
> them.
>
Whether people end up using NAT or not, RFC 4864 specifically states 
that "When changing ISPs or ISPs readjust their addressing pool, DHCP-PD 
[12] can be used as an almost zero-touch external mechanism for prefix 
change in conjunction with a ULA prefix for internal connection 
stability."  This implies, as I have argued previously, that it is 
appropriate in some cases, particularly the absence of PI space, to use 
a ULA prefix for numbering internal infrastructure like router 
interfaces.  If I am a network operator doing so, I would like my 
internal infrastructure addresses to have valid PTRs, which requires DNS 
delegation, which requires ULA-C.

To my mind, the main advantage of ULA-C over ULA-L is the ability to 
register your space and delegate reverse DNS authority to the 
appropriate name servers, such that anyone on your network or any 
privately-connected network can resolve PTR requests for addresses in 
your ULA block.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 20:22:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1WvG-0006Qd-Tx; Thu, 21 Jun 2007 20:22:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1WvF-0006Kc-Qq
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:22:45 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1WvF-0000gZ-Co
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:22:45 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5M0Mid7013067
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 21 Jun 2007 17:22:44 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5M0MiC8012928; Thu, 21 Jun 2007 19:22:44 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5M0MaMg012831; Thu, 21 Jun 2007 19:22:43 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 21 Jun 2007 17:22:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Jun 2007 17:22:21 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467B1407.90609@internap.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0YkMcCNeKOLGiReiOVVRqCWL+kwAAHc9A
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>	<467ADA2F.6060100@internap.com>	<1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com><5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
	<467B1407.90609@internap.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Scott Leibrand" <sleibrand@internap.com>,
	"IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 22 Jun 2007 00:22:38.0132 (UTC)
	FILETIME=[703F7F40:01C7B463]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: Scott Leibrand [mailto:sleibrand@internap.com]=20
> Sent: Thursday, June 21, 2007 5:13 PM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> james woodyatt wrote:
> > On Jun 21, 2007, at 15:26, Templin, Fred L wrote:
> >>
> >> Maybe I am missing the point, but there seems to be an implication=20
> >> that ULA-C necessarily implies IPv6 NAT; am I misinterpreting? If=20
> >> not, then I don't quite understand why this implication is being=20
> >> drawn. Can someone please explain?
> >
> No, ULA-C doesn't require NAT, any more than RFC 1918 or=20
> ULA-L space does.

That matches my understanding, which leaves me sort of
wondering how NAT has crept into these discussions.=20

> > I'm not going so far as to say the implication is there.  I'm just=20
> > have a very difficult time taking seriously the concern about merge=20
> > risks associated with renumbering due to the birthday paradox in a=20
> > 2^40 number space without something more substantial to go=20
> on than a=20
> > bald-faced assertion that any small but non-zero probability of=20
> > collision is unacceptable.
>=20
> That assertion has been made, but I don't think we can treat it as=20
> anything more than a preference by non-technical business people.

I have seen both sides of this street being played in other
working group contexts (sometimes even by the same people).
Some say: "probability of collision must be zero", and others
say: "birthday paradox says risk of collision is practically
nil". Wouldn't ULA-C satisfy both sides?

Fred
fred.l.templin@boeing.com

> >   The alternative explanation that makes the most sense to=20
> me is that=20
> > some influential organizations, which are too small to=20
> warrant their=20
> > own PI space, are resisting migration to IPv6 unless they=20
> can use NAT=20
> > with private addresses, and they won't [or can't] explain why the=20
> > arguments in RFC 4864 and=20
> > draft-ietf-v6ops-scanning-implications-03.txt are failing=20
> to persuade=20
> > them.
> >
> Whether people end up using NAT or not, RFC 4864 specifically states=20
> that "When changing ISPs or ISPs readjust their addressing=20
> pool, DHCP-PD=20
> [12] can be used as an almost zero-touch external mechanism=20
> for prefix=20
> change in conjunction with a ULA prefix for internal connection=20
> stability."  This implies, as I have argued previously, that it is=20
> appropriate in some cases, particularly the absence of PI=20
> space, to use=20
> a ULA prefix for numbering internal infrastructure like router=20
> interfaces.  If I am a network operator doing so, I would like my=20
> internal infrastructure addresses to have valid PTRs, which=20
> requires DNS=20
> delegation, which requires ULA-C.
>=20
> To my mind, the main advantage of ULA-C over ULA-L is the ability to=20
> register your space and delegate reverse DNS authority to the=20
> appropriate name servers, such that anyone on your network or any=20
> privately-connected network can resolve PTR requests for addresses in=20
> your ULA block.
>=20
> -Scott
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 20:29:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1X0r-0002Gy-W5; Thu, 21 Jun 2007 20:28:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1X0q-0002Gt-Cf
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:28:32 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1X0q-0002Ce-2L
	for ipv6@ietf.org; Thu, 21 Jun 2007 20:28:32 -0400
Received: from [208.73.31.18] (account sleibrand@mail.internap.com HELO
	[10.198.243.159])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84814008; Thu, 21 Jun 2007 20:28:31 -0400
Message-ID: <467B17AA.4090708@internap.com>
Date: Thu, 21 Jun 2007 17:28:26 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>	<467AD617.3020606@internap.com>
	<62901.1182465800@sa.vix.com>
In-Reply-To: <62901.1182465800@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul Vixie wrote:
>
> by asking for a use case, i'm pointing out that if you can't be reached by
> an ip packet from "there", then your need to look up a PTR corresponding to
> an address in "there" is unfathomable.
>
>   
I get that.  But just because I *do* have IP reachability to "there", 
that doesn't mean my local resolver is configured to go "there" for DNS 
resolution.  That's why I need to have a delegation chain pointing to 
the appropriate name server over "there".
>> I guess what it comes down to is that the intended use case for ULA-C is to
>> connect a bunch of companies with private address space on a private
>> network.
>>     
>
> the idea that someone would only need PI for "public networking" is bizarre.
> quite a lot of normal IPv4 space is never advertised into the "default free
> zone" but it's universally unique and used "privately" with passion & verve,
> and there is no reason to expect that IPv6 PI won't be used the same way.
>
> a global RIR policy to support this "private network" use case would suggest
> that each RIR lay aside a /32 worth of space that was meant to be carved up
> in /48 chunks for folks who needed smaller chunks of address space for private
> networking, with advice to the community that no address space in these /32's
> be advertised to the DFZ, and that it be filtered out if seen in the DFZ.  an
> RIR could theoretically come up with a "private space only" membership class
> with lower fees.  whois and PTR-space NS RRsets would be managed normally.
>   

You just did an excellent job of describing ULA-C.  The only difference 
is that ULA-C is being specified top-down through the RFC process, 
rather than being put together in an ad-hoc bottom-up process that may 
be different for each RIR.
> i think the disconnect here is that a lot of folks are assuming that the RIR
> system only allocates "public" address space.  that's not true today, and it
> never has been true (compare historical allocations vs. DFZ advertisements),
> and there's no reason to try to make it true or to assume that it ever will
> be true.  RIRs allocate universally unique space.  how it's used (public vs.
> private) is not an RIR concern.
>   
It is true that someone who can get a PI allocation can use it for 
internal use just as they would with ULA-C.  However, since someone who 
can get a PI allocation can easily put it in the DFZ, the RIR membership 
has made restricting the distribution of PI  space an RIR concern 
through the policy process.  The RIRs could elect to allocate 
private-use-only PI out of a special block, but such space is less 
likely to remain out of the DFZ, because the designation of it as 
not-to-be-routed would not carry the force of an RFC standard, and there 
would not be a single block (FC00::/7) to filter, but several different 
blocks, one from each RIR who chose to create private-use PI space.  As 
such, I believe that the IETF should designate ULA-C and hand it off to 
IANA and the RIRs to manage, rather than having the RIRs designate 
private-use-only PI space.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 21:11:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Xfo-0000qK-Ia; Thu, 21 Jun 2007 21:10:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1Xfm-0000mM-Ls
	for ipv6@ietf.org; Thu, 21 Jun 2007 21:10:50 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1Xfl-0006JS-DR
	for ipv6@ietf.org; Thu, 21 Jun 2007 21:10:50 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 2360B9F6A9F
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 18:10:49 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 133A01009A
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 18:10:49 -0700 (PDT)
X-AuditID: 11807124-a454cbb000002544-49-467b219919fa
Received: from [17.206.50.68] (il0602f-dhcp68.apple.com [17.206.50.68])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 079131004D
	for <ipv6@ietf.org>; Thu, 21 Jun 2007 18:10:49 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com>
	<E72F5476-D072-44B6-A848-F206C15BBC22@icann.org>
	<467ADA2F.6060100@internap.com>
	<1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
	<5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
	<467B1407.90609@internap.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 21 Jun 2007 18:10:47 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 21, 2007, at 17:22, Templin, Fred L wrote
> From: Scott Leibrand [mailto:sleibrand@internap.com]
>>
>> That assertion has been made, but I don't think we can treat it as  
>> anything more than a preference by non-technical business people.
>
> [...] Some say: "probability of collision must be zero", and others  
> say: "birthday paradox says risk of collision is practically nil".  
> Wouldn't ULA-C satisfy both sides?

One of those two sides is presenting technical criteria for  
satisfying unstated and mysterious non-technical goals.  Is it too  
much to ask for less mystery and more transparency in working group  
proceedings?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 22:19:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1YkH-0003c5-OT; Thu, 21 Jun 2007 22:19:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1YkF-0003bv-PU
	for ipv6@ietf.org; Thu, 21 Jun 2007 22:19:31 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1YkC-0003pH-2G
	for ipv6@ietf.org; Thu, 21 Jun 2007 22:19:31 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5M2JFmE039868;
	Fri, 22 Jun 2007 12:19:17 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706220219.l5M2JFmE039868@drugs.dv.isc.org>
To: Scott Leibrand <sleibrand@internap.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Thu, 21 Jun 2007 12:48:39 MST."
	<467AD617.3020606@internap.com> 
Date: Fri, 22 Jun 2007 12:19:15 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ipv6@ietf.org, Paul Vixie <Paul_Vixie@isc.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> Paul Vixie wrote:
> >
> >> As far as I know there's no mechanism to delegate reverse DNS for a locall
> y
> >> generated ULA, since there's no "ownership".  IMO any move to start
> >> delegating .arpa authority for ULAs would be de facto ULA-C, so if we're
> >> going to do that we should do it right and do the other registration
> >> functions that should go along with the DNS delegation.
> >>     
> >
> > not to disparage either participant shown above personally, but, this
> > argument is beyond nuttiness.  mark andrews has a draft out about local
> > domain name service for RFC 1918, and his fundamental observation is
> > that there is no need for the resolution perimeter of a PTR to differ
> > from the routing perimeter of the IP address described by that PTR.  
> 
Feel free to disparage me as a newbie as appropriate.  :-) 
> 
> Can you point me to the name of the referenced I-D?  Unfortunately I 
> haven't had time to closely follow new I-D's, and am only involved in 
> this discussion because of my ARIN PPML involvement.
> 
> > yet here we have a large set of folks who unlike mark andrews are not exper
> ts
> > at DNS, telling us that yes we do need to be able to resolve a PTR from
> > places where the addresses won't be routable, and then using this ignorant
> > and false assertion to justify a global registry of unique but unreachable
> > address blocks, each having its own globally reachable nameservers for PTRs
> .
> >
> > what's wrong with this picture?  is there a use case we can all study?
> >
> >   
> Maybe the I-D answers this, but how do you resolve PTRs for some random 
> section of .arpa if you don't have glue NS records pointing you to the 
> name servers for that subdomain?  In terms of use case, say my network 
> connects privately to a network using ULAs.  I traceroute to a host on 
> that network, and try to resolve PTRs for the ULA block.  If the block 
> is ULA-C, my DNS server (which may be a completely independent local 
> instance of BIND without forwarders) can traverse the tree from the 
> root, get the proper delegations to the NS's for the ULA-C (which will 
> need to be on public IPs), and resolve the PTRs.  If the block is local 
> ULA, however, I don't know how my independent local resolver is supposed 
> to find out which name servers are authoritative for the ULA block.

	You publish D.F.IP6.ARPA and C.F.IP6.ARPA and maintain delegations
	within them for all the ULA (L or C) networks that are reachable.
	Each site then becomes a slave.

		zone "C.F.IP6.ARPA" {
			type slave;
			masters { FC...; };
			file "C.F.IP6.ARPA"
		};

		zone "D.F.IP6.ARPA" {
			 type slave;
			 masters { FD...; };
			 file "D.F.IP6.ARPA"
		 };

	The only question is who maintains the D.F.IP6.ARPA registry
	you are using.  Yourself, someone else in your group of
	networks or the RIRs.  C.F.IP6.ARPA already excludes the RIRs
	from this role.

> I guess what it comes down to is that the intended use case for ULA-C is 
> to connect a bunch of companies with private address space on a private 
> network.  In that kind of use case, close integration of DNS 
> infrastructure seems unlikely, so without delegating DNS authority from 
> the root, I don't see how you can provide good reverse DNS resolution in 
> such a use case.  Therefore, I support draft-ietf-ipv6-ula-central-02's 
> requirement to support DNS delegation, with the caveat that such 
> delegation must be to public addresses (that NS records should not point 
> to ULAs).
> 
> Thanks,
> Scott
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 22:40:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Z4G-0005El-OC; Thu, 21 Jun 2007 22:40:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1Z4F-0005Cy-Aw; Thu, 21 Jun 2007 22:40:11 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1Z4E-00069r-SM; Thu, 21 Jun 2007 22:40:11 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 269867301F;
	Fri, 22 Jun 2007 11:40:09 +0900 (JST)
Date: Fri, 22 Jun 2007 11:40:07 +0900
Message-ID: <m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: internet-drafts@ietf.org, ipv6@ietf.org,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changes	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Thu, 21 Jun 2007 12:31:58 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Please see section 5 of our I-D for a proposed change to 2462bis-08 - we
> hear this I-D is=20
> in Editor's queue and any changes to it must be given ASAP.

(with the document editor hat of 2462bis on)

=46rom a quick look at Section 5 (and that section only), the key point
of the proposed change is:

  skipping DAD is NOT RECOMMENDED, and new implementations MUST NOT do
  it (but existing ones still performing the optimization will not be
  accused of non-conformance)

to=20

  skipping DAD is completely prohibited, and all new/old
  implementations MUST always perform DAD for any address.

Is that correct?

If so, I suspect it's too controversial to merge in 2462bis at this
stage.  This part was indeed a result of very heated discussions, and
even though (I believe) we all knew that simply prohibiting it without
exception was a cleaner resolution, we failed to reach a clear
consensus on it; hence the current text as a sort of compromise.

If your new draft could now perfectly convince those who opposed to
prohibiting the DAD optimization before 2462bis goes to the AUTH48
state, I, for one, would be happy to include it to the final version
of 2462bis.  But I cannot be that optimistic.

In any event, I don't think changing the phrase matters much; we
already clearly state new implementations MUST NOT skip DAD, so the
change only affects existing implementations.  I suspect a certain
amount of existing implementations that skip DAD as specified in
RFC2462 will still keep the current behavior whatever the new 2462bis
RFC specifies.  But they'll eventually be replaced with new
implementations, which, if conforming to 2462bis, won't perform DAD
skipping.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 21 23:54:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1aDG-0001OV-NK; Thu, 21 Jun 2007 23:53:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1aDF-0001OP-Ks
	for ipv6@ietf.org; Thu, 21 Jun 2007 23:53:33 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1aDE-0007uU-6J
	for ipv6@ietf.org; Thu, 21 Jun 2007 23:53:33 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5083811425
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 03:53:31 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 21 Jun 2007 17:28:26 MST."
	<467B17AA.4090708@internap.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
	<467AD617.3020606@internap.com> <62901.1182465800@sa.vix.com>
	<467B17AA.4090708@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 22 Jun 2007 03:53:31 +0000
Message-ID: <1817.1182484411@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > by asking for a use case, i'm pointing out that if you can't be reached by
> > an ip packet from "there", then your need to look up a PTR corresponding to
> > an address in "there" is unfathomable.
>
> I get that.  But just because I *do* have IP reachability to "there", that
> doesn't mean my local resolver is configured to go "there" for DNS
> resolution.  That's why I need to have a delegation chain pointing to the
> appropriate name server over "there".

it sounds like what you want to propose is "something like BGP for DNS stubs"
then.  if you have a private relationship to other networks, then you should
be able to express that relationship in both routing and DNS technologies.  i
guess this means i should add "stub zones" to my "metazones" work and publish
that, since it would obviate this entire use case and perhaps many others.

> > a global RIR policy to support this "private network" use case would
> > suggest that each RIR lay aside a /32 worth of space that was meant to be
> > carved up in /48 chunks for folks who needed smaller chunks of address
> > space for private networking, with advice to the community that no address
> > space in these /32's be advertised to the DFZ, and that it be filtered out
> > if seen in the DFZ.  an RIR could theoretically come up with a "private
> > space only" membership class with lower fees.  whois and PTR-space NS
> > RRsets would be managed normally.
> 
> You just did an excellent job of describing ULA-C.  The only difference is
> that ULA-C is being specified top-down through the RFC process, rather than
> being put together in an ad-hoc bottom-up process that may be different for
> each RIR.

my only reason for quoting my own text above yours up there is so you can go
back and see the word "global" before the words "RIR policy".  are we done?

> It is true that someone who can get a PI allocation can use it for internal
> use just as they would with ULA-C.  However, since someone who can get a PI
> allocation can easily put it in the DFZ, the RIR membership has made
> restricting the distribution of PI space an RIR concern through the policy
> process.

which is, perhaps, the reason i'm suggesting a new global RIR policy on this.

> The RIRs could elect to allocate private-use-only PI out of a special block,
> but such space is less likely to remain out of the DFZ, because the
> designation of it as not-to-be-routed would not carry the force of an RFC
> standard,

you have got to be kidding me.  have you not been watching the snippets of
RFC1918-sourced traffic that i've been forwarding to nanog@ all these years?
there is no "force of", either for an RFC "standard" or for an RIR policy.
everything leaks, all the time.  however, as Enigo Montoya said in The
Princess Bride, "i know something you do not."  which is that due in part to
the endless route-theft by spammers and phishers and ddos'ers, RPKI is afoot.
this may or may not stop bad guys from doing bad things, but it will certainly
stop good guys from doing bad things.  none of which matters, since from an
RIR policy point of view, the recommendation of unroutability is meant to make
the policy self-consistent and edible.  it will have no more or less force
than the similar recommendation made in RFC 1918, and everybody knows that.

> and there would not be a single block (FC00::/7) to filter, but several
> different blocks, one from each RIR who chose to create private-use PI
> space.  As such, I believe that the IETF should designate ULA-C and hand it
> off to IANA and the RIRs to manage, rather than having the RIRs designate
> private-use-only PI space.

i could live with that if i had to.  it's the "iana runs a PTR registration
robot" and the "enduser selects their own prefix" elements of prior proposals
i havn't been able to sit with.  i see this as something every RIR ought to
do, and that every ISP ought to follow.  the RIR policy process is
quintessentially regional and bottom-up, and i believe it will work fine for
this application.  the addresses described by ULA-C are uniquely global, and
to assume that only the IETF, not the RIRs, can allocate "private" ones is
counter to my understanding of the mission of every RIR.  if IETF is to act,
let it be to recommend that IANA reserve FC00 and allocate /32's to the RIRs
if a request from an RIR comes in with the magic "RFC WXYZ" box checked.  the
*only* advantage to this is that DFZ participants who want to filter FC00 can
avoid tracking per-RIR bogon lists.  but please note, as you consider these
matters, that any RIR at any time could declare a /32 for this purpose and
start doing regional allocations out of it, and all DFZ participants are
already prepared, process-wise, to track this and implement if it happens.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 03:50:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1dtv-0001Tq-SW; Fri, 22 Jun 2007 03:49:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1dtu-0001Ps-58
	for ipv6@ietf.org; Fri, 22 Jun 2007 03:49:50 -0400
Received: from wx-out-0506.google.com ([66.249.82.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1dtt-0001sU-SD
	for ipv6@ietf.org; Fri, 22 Jun 2007 03:49:50 -0400
Received: by wx-out-0506.google.com with SMTP id t5so688453wxc
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 00:49:49 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=uOYJPHZ/A+18JM1c4EWzQU6NFlY6VMwGY/LO9gdFvoYvT5PQ9CWnYL1BPrGPuGjB8Ev26/b6p6QYaJDKERXDTeLNxYpjCSX/5392c82dpix8dWilSNehPzWdcZrY94ujfR9TJNOBiGyk2CZtJgFq0whKZ/uGR1p4R1Y/lzJ/QUA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lnksumMUFUx8m9zH4ESnQQLstmwN7QWbrL2F7crFaRQ+kxWTLH+eut5PlEUUaURTqlLlCyJgTcJK0AiQD+CT9cJiqFZU+BKvmjgP19Osv90SSLcnCQ2nP11qs9NP959w6amcY7HV6QaCm6UEOZ+82Rj/crPBBbYz0YgD1GXr1fs=
Received: by 10.70.21.8 with SMTP id 8mr4334796wxu.1182498589467;
	Fri, 22 Jun 2007 00:49:49 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id g9sm4083960wra.2007.06.22.00.49.46
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 00:49:47 -0700 (PDT)
Message-ID: <467B7F18.1040300@gmail.com>
Date: Fri, 22 Jun 2007 09:49:44 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>
In-Reply-To: <28803.1182449010@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-21 20:03, Paul Vixie wrote:
>>> Scott, what feature of existing ULAs makes them unsuitable for this
>>> usage today? In the ridiculously unlikely event of a ULA prefix clash,
>>> this would be detected up-front when trying to set up the reverse
>>> delegation, and then you'd simply generate a different ULA prefix.
> 
>> As far as I know there's no mechanism to delegate reverse DNS for a locally
>> generated ULA, since there's no "ownership".  IMO any move to start
>> delegating .arpa authority for ULAs would be de facto ULA-C, so if we're
>> going to do that we should do it right and do the other registration
>> functions that should go along with the DNS delegation.
> 
> not to disparage either participant shown above personally, 

As it happens I agree with you Paul; but I left out a hypothetical
or two in my argument aiming to show that Scott's use case didn't
add up in my mind.

     Brian

> but, this
> argument is beyond nuttiness.  mark andrews has a draft out about local
> domain name service for RFC 1918, and his fundamental observation is
> that there is no need for the resolution perimeter of a PTR to differ
> from the routing perimeter of the IP address described by that PTR.  yet
> here we have a large set of folks who unlike mark andrews are not experts
> at DNS, telling us that yes we do need to be able to resolve a PTR from
> places where the addresses won't be routable, and then using this ignorant
> and false assertion to justify a global registry of unique but unreachable
> address blocks, each having its own globally reachable nameservers for PTRs.
> 
> what's wrong with this picture?  is there a use case we can all study?
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 04:08:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1eBf-0001j8-Mg; Fri, 22 Jun 2007 04:08:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1eBe-0001j3-0b
	for ipv6@ietf.org; Fri, 22 Jun 2007 04:08:10 -0400
Received: from wx-out-0506.google.com ([66.249.82.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1eBc-0004VB-QZ
	for ipv6@ietf.org; Fri, 22 Jun 2007 04:08:09 -0400
Received: by wx-out-0506.google.com with SMTP id t5so691768wxc
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 01:08:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=Js2w3VG3AmjJDX7qOEA+a0YfvdbfTXytBTY9Wy1M2WKj/r2CkZiQ/rdNr9xCESE2bpHT2IUd6Hyq7RwyrO/hJHK59GW5oUpib8FiCj5wE/RUocW2oNP0+QfLPpilCHhKCl9rIW8FFzGLibQjXmpNXDcNMHEBfwIaGnjtegqRbjU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=WnUfg6fDhh5Y2tMD4Yb58p6EGPOVyI+8o/z2XQRzsO0vKK5BpIxPlugywBPByj50oGA5dDxZqmNcxDMzZLzbxqZlFWe6lS8mVca+f7u6JDiEoSFpBRIRCJsYP3a1wvbk7LUa6jKzotrPdNQpQp4+dwDWagsG9BXhqHZuAd6Y/6E=
Received: by 10.90.63.16 with SMTP id l16mr2414696aga.1182499688367;
	Fri, 22 Jun 2007 01:08:08 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 13sm4120576wrl.2007.06.22.01.08.07
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 01:08:08 -0700 (PDT)
Message-ID: <467B8366.9050905@gmail.com>
Date: Fri, 22 Jun 2007 10:08:06 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com>
In-Reply-To: <467AA083.6070102@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-21 18:00, Scott Leibrand wrote:
...
> As far as I know there's no mechanism to delegate reverse DNS for a 
> locally generated ULA, since there's no "ownership".  

Please read RFC 4193 section 4.4.

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 08:43:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1iU9-0002S1-86; Fri, 22 Jun 2007 08:43:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1iU7-0002Pk-O6
	for ipv6@ietf.org; Fri, 22 Jun 2007 08:43:31 -0400
Received: from ik-out-1112.google.com ([66.249.90.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1iU6-0002RN-F5
	for ipv6@ietf.org; Fri, 22 Jun 2007 08:43:31 -0400
Received: by ik-out-1112.google.com with SMTP id b32so745116ika
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 05:43:29 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=IZgcS6Umwp/QgMCaW8CuObGsTKoz+vx6axR9xR/Jy65rBPCv8bxmHesarw6+JRO+5XnqHlFDCAV4Co7MVfTCMYg619JSl/qFeCkDdGB2p2dyE1uRUxFkg3yF9uRqDEGghOM5lILMTbtNuImcOkCEhcuhEyyq+Z7EZyqDB6/XCe4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=IC3OuRINyBfDua+tZ8mAkaZSgLRRVIRIzlm3sXAk/uAKIXpFB1PIMOozeVm3ngHggNTj6kfp5gRF9KF0Wp9YIKvuklsqrJr5/4YUwKEXn807tAe3uBehIobH9toUPa5qGtLGO8TOQOh5rEd9MzTiSd7GQQW6RTIQipJS9wCLwtQ=
Received: by 10.78.134.12 with SMTP id h12mr1541596hud.1182516209466;
	Fri, 22 Jun 2007 05:43:29 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id h1sm253734nfh.2007.06.22.05.43.28
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 05:43:28 -0700 (PDT)
Message-ID: <467BC3EF.4050107@gmail.com>
Date: Fri, 22 Jun 2007 14:43:27 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
In-Reply-To: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-ra-flags-option-00.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Sorry to be slightly late...

I note that 2461bis says that unrecognized options MUST
be ignored. So that means that back-level implementations
will ignore any flag bits sent with this new option. Does
that have any side-effects that should be noted?

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 09:05:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1ipf-0004Nf-BJ; Fri, 22 Jun 2007 09:05:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1ipe-0004NR-4U
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:05:46 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1ipd-0001kP-Rn
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:05:46 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 22 Jun 2007 09:05:45 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAM5le0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,451,1175486400"; 
	d="scan'208"; a="63436813:sNHT45496604"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5MD5jB4004519; 
	Fri, 22 Jun 2007 09:05:45 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5MD5bZF004473; 
	Fri, 22 Jun 2007 13:05:45 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 09:05:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jun 2007 09:05:36 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace0drDN+vcnqwlTS3aztfAVA6x43QAUV0+A
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 22 Jun 2007 13:05:37.0803 (UTC)
	FILETIME=[070EEDB0:01C7B4CE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3067; t=1182517545;
	x=1183381545; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=09e4dcb19xt+14MXUUMqP9w8xcc+iF5JFwSdt5z05yk=;
	b=ddyKggqvGZL+02XavcGzwwO1IjUPpglTR7PieQbC2T5RAlLYxWQ5advO/4Ay3L4mnTG3Hcyv
	Ocp4vQAxiZxBbIq1MteZDy40o61DnmO10k4pvKwQjrSpseZqX7VeAyhD;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: ipv6@ietf.org
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Tatuya,

Thanks for the quick review of section 5 in our new I-D.  Your reading
of section 5 is correct - we have proposed both new and old
implementations to always perform DAD for any unicast address. You are
also correct that the gross change we have proposed over 2462bis is that
old implementations MUST also not skip DAD. We stress about old
implementations because if older implementations that are already
deployed continue to be deployed for say, the next 5-10 years, that's
not good. A software upgrade to older implementation is certainly
possible.

We have given a solid reason for our case - it's presented in Section 2,
bullet 4 of our I-D. Please see if our reasoning is solid enough to
convince IETF.

Thanks.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Thursday, June 21, 2007 10:40 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org; internet-drafts@ietf.org; Wes Beebee (wbeebee); Ralph
Droms (rdroms)
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

At Thu, 21 Jun 2007 12:31:58 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Please see section 5 of our I-D for a proposed change to 2462bis-08 -=20
> we hear this I-D is in Editor's queue and any changes to it must be=20
> given ASAP.

(with the document editor hat of 2462bis on)

>From a quick look at Section 5 (and that section only), the key point of
the proposed change is:

  skipping DAD is NOT RECOMMENDED, and new implementations MUST NOT do
  it (but existing ones still performing the optimization will not be
  accused of non-conformance)

to=20

  skipping DAD is completely prohibited, and all new/old
  implementations MUST always perform DAD for any address.

Is that correct?

If so, I suspect it's too controversial to merge in 2462bis at this
stage.  This part was indeed a result of very heated discussions, and
even though (I believe) we all knew that simply prohibiting it without
exception was a cleaner resolution, we failed to reach a clear consensus
on it; hence the current text as a sort of compromise.

If your new draft could now perfectly convince those who opposed to
prohibiting the DAD optimization before 2462bis goes to the AUTH48
state, I, for one, would be happy to include it to the final version of
2462bis.  But I cannot be that optimistic.

In any event, I don't think changing the phrase matters much; we already
clearly state new implementations MUST NOT skip DAD, so the change only
affects existing implementations.  I suspect a certain amount of
existing implementations that skip DAD as specified in
RFC2462 will still keep the current behavior whatever the new 2462bis
RFC specifies.  But they'll eventually be replaced with new
implementations, which, if conforming to 2462bis, won't perform DAD
skipping.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba
Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 09:17:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1j1F-0008Kh-RS; Fri, 22 Jun 2007 09:17:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1j1D-0008D1-9A
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:17:43 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1j1B-000570-Rl
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:17:43 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 22 Jun 2007 08:17:40 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A063141066707080@mail>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0Sp3hf1tn5iLBSNq9WPvSMbHcgQACBBVwAB8gibA=
From: "Kevin Kargel" <kkargel@polartel.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	"Leo Vegoda" <leo.vegoda@icann.org>,
	"Scott Leibrand" <sleibrand@internap.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I believe the implication comes when people assume that ULA-C addresses
will be applied on hosts that need direct communication with the DFZ.
As ULA-C is "non-routable" then NAT or some sort of proxy would be
required.

In a network I was designing it would be a non-issue.  If a host
required access to the DFZ it would get a PI address.  Why make things
complicated when you can make them simple?=20

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> Sent: Thursday, June 21, 2007 5:27 PM
> To: Leo Vegoda; Scott Leibrand
> Cc: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-ula-central-02.txt
>=20
> Maybe I am missing the point, but there seems to be an=20
> implication that ULA-C necessarily implies IPv6 NAT; am I=20
> misinterpreting? If not, then I don't quite understand why=20
> this implication is being drawn. Can someone please explain?
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 09:23:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1j72-0003Bz-7y; Fri, 22 Jun 2007 09:23:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1j70-0003Bu-WA
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:23:43 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1j6z-0006ic-Gq
	for ipv6@ietf.org; Fri, 22 Jun 2007 09:23:42 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 22 Jun 2007 08:23:40 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A063141066707081@mail>
In-Reply-To: <5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0WYQyAoOFeZmCQDiMQSyWeh++CAAdkCow
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

So why are we expending so much effort getting them to switch to IPv6
earlier?  When IPv6 is the mainstream method of addressing they will get
swept along.  If a network admin wants to drag their feet and do things
the hard way they have a right to do that.  The rest of us don't need to
go out of our way to accommodate them.

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Thursday, June 21, 2007 6:11 PM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> On Jun 21, 2007, at 15:26, Templin, Fred L wrote:
> >
> > Maybe I am missing the point, but there seems to be an implication=20
> > that ULA-C necessarily implies IPv6 NAT; am I=20
> misinterpreting? If not,=20
> > then I don't quite understand why this implication is being=20
> drawn. Can=20
> > someone please explain?
>=20
> I'm not going so far as to say the implication is there.  I'm=20
> just have a very difficult time taking seriously the concern=20
> about merge risks associated with renumbering due to the=20
> birthday paradox in a 2^40 number space without something=20
> more substantial to go on than a bald-faced assertion that=20
> any small but non-zero probability of collision is=20
> unacceptable.  The alternative explanation that makes the=20
> most sense to me is that some influential organizations,=20
> which are too small to warrant their own PI space, are=20
> resisting migration to IPv6 unless they can use NAT with=20
> private addresses, and they won't [or can't] explain why the=20
> arguments in RFC 4864 and draft-ietf-=20
> v6ops-scanning-implications-03.txt are failing to persuade them.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 10:06:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1jlf-000642-S1; Fri, 22 Jun 2007 10:05:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1jjn-0001Xn-7s
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:03:47 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1jiL-0006Y3-8M
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:02:18 -0400
Received: from ([128.244.206.105])
	by pilot.jhuapl.edu with ESMTP  id 5502123.35631650;
	Fri, 22 Jun 2007 10:02:01 -0400
Message-ID: <467BD659.1040708@innovationslab.net>
Date: Fri, 22 Jun 2007 10:02:01 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
	<467BC3EF.4050107@gmail.com>
In-Reply-To: <467BC3EF.4050107@gmail.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Fri, 22 Jun 2007 10:05:40 -0400
Cc: IPv6 WG <ipv6@ietf.org>, bob.hinden@nokia.com
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-ra-flags-option-00.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I would say that it if a node does not support this new option, it will
probably not support any new functionality using the extended bit field.
 I am rather neutral on whether adding such text is necessary.

Regards,
Brian


Brian E Carpenter wrote:
> Sorry to be slightly late...
> 
> I note that 2461bis says that unrecognized options MUST
> be ignored. So that means that back-level implementations
> will ignore any flag bits sent with this new option. Does
> that have any side-effects that should be noted?
> 
>     Brian
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 10:09:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1jow-00010z-T0; Fri, 22 Jun 2007 10:09:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1jov-00010r-CW
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:09:05 -0400
Received: from mu-out-0910.google.com ([209.85.134.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1jou-000841-SL
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:09:05 -0400
Received: by mu-out-0910.google.com with SMTP id w8so826107mue
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 07:09:04 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=U9ZjbyyPrCS+smIZ/BASpbg0Uo/ZD8ZYLnYNsrqKxloI3FJWSeiRljpX6yGY4nZ7WgWw4LVIMe1bMwKkgB0obUT+kl0mSOHGZQ3PHDE+t5UjAswAc/xb6WoYhOrc0RRR0OsK462nRKcKa5yZ+IZs1QUnC8aEiA/V3iyh3D5k60w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=DEprBX/5BhriyLWoPBgIDY9TXOKXd7eTCeVlVWiEnLs6HFpVcyGBQYxbHT9GyyH7p9vhab3lyI9AZVwujKD08WfK0q6ZhVUyLSTyslA6B+ZRouJ+bcP1jNvnDY6/eSULmE/s6Y/VPsglBeCFeQznYMLNYR+yCbNelT7BE8t/sIo=
Received: by 10.82.105.13 with SMTP id d13mr6422708buc.1182521343948;
	Fri, 22 Jun 2007 07:09:03 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id d27sm2742479nfh.2007.06.22.07.09.02
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 07:09:02 -0700 (PDT)
Message-ID: <467BD7FC.1030405@gmail.com>
Date: Fri, 22 Jun 2007 16:09:00 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
 suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hemant,

Your logic escapes me. Old implementations are *old*
and will continue to do whatever their code does.
No words in 2462bis or 2462ter or anywhere can change
that. I think your proposal is a no-op.

     Brian

On 2007-06-22 15:05, Hemant Singh (shemant) wrote:
> Hi Tatuya,
> 
> Thanks for the quick review of section 5 in our new I-D.  Your reading
> of section 5 is correct - we have proposed both new and old
> implementations to always perform DAD for any unicast address. You are
> also correct that the gross change we have proposed over 2462bis is that
> old implementations MUST also not skip DAD. We stress about old
> implementations because if older implementations that are already
> deployed continue to be deployed for say, the next 5-10 years, that's
> not good. A software upgrade to older implementation is certainly
> possible.
> 
> We have given a solid reason for our case - it's presented in Section 2,
> bullet 4 of our I-D. Please see if our reasoning is solid enough to
> convince IETF.
> 
> Thanks.
> 
> Hemant
> 
> -----Original Message-----
> From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp] 
> Sent: Thursday, June 21, 2007 10:40 PM
> To: Hemant Singh (shemant)
> Cc: ipv6@ietf.org; internet-drafts@ietf.org; Wes Beebee (wbeebee); Ralph
> Droms (rdroms)
> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
> changes suggested to 2462bis-08
> 
> At Thu, 21 Jun 2007 12:31:58 -0400,
> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
> 
>> Please see section 5 of our I-D for a proposed change to 2462bis-08 - 
>> we hear this I-D is in Editor's queue and any changes to it must be 
>> given ASAP.
> 
> (with the document editor hat of 2462bis on)
> 
>>From a quick look at Section 5 (and that section only), the key point of
> the proposed change is:
> 
>   skipping DAD is NOT RECOMMENDED, and new implementations MUST NOT do
>   it (but existing ones still performing the optimization will not be
>   accused of non-conformance)
> 
> to 
> 
>   skipping DAD is completely prohibited, and all new/old
>   implementations MUST always perform DAD for any address.
> 
> Is that correct?
> 
> If so, I suspect it's too controversial to merge in 2462bis at this
> stage.  This part was indeed a result of very heated discussions, and
> even though (I believe) we all knew that simply prohibiting it without
> exception was a cleaner resolution, we failed to reach a clear consensus
> on it; hence the current text as a sort of compromise.
> 
> If your new draft could now perfectly convince those who opposed to
> prohibiting the DAD optimization before 2462bis goes to the AUTH48
> state, I, for one, would be happy to include it to the final version of
> 2462bis.  But I cannot be that optimistic.
> 
> In any event, I don't think changing the phrase matters much; we already
> clearly state new implementations MUST NOT skip DAD, so the change only
> affects existing implementations.  I suspect a certain amount of
> existing implementations that skip DAD as specified in
> RFC2462 will still keep the current behavior whatever the new 2462bis
> RFC specifies.  But they'll eventually be replaced with new
> implementations, which, if conforming to 2462bis, won't perform DAD
> skipping.
> 
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba
> Corp.
> 					jinmei@isl.rdc.toshiba.co.jp
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 10:24:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1k3M-0005Dv-Lk; Fri, 22 Jun 2007 10:24:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1k3K-0005Dq-ML
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:23:58 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1k3J-0003nk-8X
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:23:58 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 22 Jun 2007 10:23:54 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAJx4e0ZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,452,1175486400"; 
	d="scan'208"; a="63444367:sNHT46454590"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5MENsP4024411; 
	Fri, 22 Jun 2007 10:23:54 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5MENqLf028470; 
	Fri, 22 Jun 2007 14:23:54 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 10:23:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jun 2007 10:23:51 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <467BD7FC.1030405@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace01ugMq4etQZRES1GpAmp/cO07iQAAMCGg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 22 Jun 2007 14:23:51.0977 (UTC)
	FILETIME=[F5010990:01C7B4D8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4817; t=1182522234;
	x=1183386234; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Brian=20E=20Carpenter=22=20<brian.e.carpenter@gmail.com>;
	bh=HcgLDZ06vlK2eNnUS2FWPGNHYr1XRE4Dz9nSlH7/MCw=;
	b=e8LwJhTrCc8AAqnDy2Ug1ufIA3/1RH4q0fQvmn5dXSWOFsEIvwo4VZfm2OdKmF1Xs4AnljDU
	Wl+G6Nl89enFzj3rtFGSpjD1cCFbqJQjJ4KsKlJ0jjyhHKb6nISBo+eQ;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian,

IETF can only make recommendations to implementers, they cannot force
implementers to implement anything.  However, IETF is the authority on
whether an implementation is compliant with an IETF specification.  By
making our proposed change to 2462bis, we are saying that old
implementations are no longer compliant with the new 2462bis I-D.  If an
old implementation wishes to comply with the new 2462bis, then the
software needs to be upgraded (by eliminating the "grandfathering"
clause).  This provides incentive for software upgrades to prevent the
security problem found in our I-D. =20

Hemant

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
Sent: Friday, June 22, 2007 10:09 AM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

Hemant,

Your logic escapes me. Old implementations are *old* and will continue
to do whatever their code does.
No words in 2462bis or 2462ter or anywhere can change that. I think your
proposal is a no-op.

     Brian

On 2007-06-22 15:05, Hemant Singh (shemant) wrote:
> Hi Tatuya,
>=20
> Thanks for the quick review of section 5 in our new I-D.  Your reading

> of section 5 is correct - we have proposed both new and old=20
> implementations to always perform DAD for any unicast address. You are

> also correct that the gross change we have proposed over 2462bis is=20
> that old implementations MUST also not skip DAD. We stress about old=20
> implementations because if older implementations that are already=20
> deployed continue to be deployed for say, the next 5-10 years, that's=20
> not good. A software upgrade to older implementation is certainly=20
> possible.
>=20
> We have given a solid reason for our case - it's presented in Section=20
> 2, bullet 4 of our I-D. Please see if our reasoning is solid enough to

> convince IETF.
>=20
> Thanks.
>=20
> Hemant
>=20
> -----Original Message-----
> From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]
> Sent: Thursday, June 21, 2007 10:40 PM
> To: Hemant Singh (shemant)
> Cc: ipv6@ietf.org; internet-drafts@ietf.org; Wes Beebee (wbeebee);=20
> Ralph Droms (rdroms)
> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent=20
> changes suggested to 2462bis-08
>=20
> At Thu, 21 Jun 2007 12:31:58 -0400,
> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
>=20
>> Please see section 5 of our I-D for a proposed change to 2462bis-08 -

>> we hear this I-D is in Editor's queue and any changes to it must be=20
>> given ASAP.
>=20
> (with the document editor hat of 2462bis on)
>=20
>>From a quick look at Section 5 (and that section only), the key point=20
>>of
> the proposed change is:
>=20
>   skipping DAD is NOT RECOMMENDED, and new implementations MUST NOT do
>   it (but existing ones still performing the optimization will not be
>   accused of non-conformance)
>=20
> to
>=20
>   skipping DAD is completely prohibited, and all new/old
>   implementations MUST always perform DAD for any address.
>=20
> Is that correct?
>=20
> If so, I suspect it's too controversial to merge in 2462bis at this=20
> stage.  This part was indeed a result of very heated discussions, and=20
> even though (I believe) we all knew that simply prohibiting it without

> exception was a cleaner resolution, we failed to reach a clear=20
> consensus on it; hence the current text as a sort of compromise.
>=20
> If your new draft could now perfectly convince those who opposed to=20
> prohibiting the DAD optimization before 2462bis goes to the AUTH48=20
> state, I, for one, would be happy to include it to the final version=20
> of 2462bis.  But I cannot be that optimistic.
>=20
> In any event, I don't think changing the phrase matters much; we=20
> already clearly state new implementations MUST NOT skip DAD, so the=20
> change only affects existing implementations.  I suspect a certain=20
> amount of existing implementations that skip DAD as specified in
> RFC2462 will still keep the current behavior whatever the new 2462bis=20
> RFC specifies.  But they'll eventually be replaced with new=20
> implementations, which, if conforming to 2462bis, won't perform DAD=20
> skipping.
>=20
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba
> Corp.
> 					jinmei@isl.rdc.toshiba.co.jp
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 10:38:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1kHZ-0002CP-Uo; Fri, 22 Jun 2007 10:38:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1kHY-0002C7-LY
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:38:40 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1kHX-00071y-Va
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:38:40 -0400
Received: by ug-out-1314.google.com with SMTP id k3so2106073ugf
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 07:38:39 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=mz9copF6DI1iaZDOUBnEPJnN2I3pqb0TQwG8eGIIM67z4HZQhSqtzoaVXxf+PIYbEO3CrTKpxjntUbvZQB1d1EoGZVX4YAED976mlFuPmlxwJ4xyeabJNeiUrpMFrrZbEczWjz7AuD7tbHMm6Z7p2ZCce5fc79DdDEbSQdCRMAA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=eXrLrwvF9e8S6ZDt5ollMf1JXwzMx7RAMLIr/HiKocWys5PwAvPO/fasZfTFTV9JPopENg/GuaMTly2GYcB5k6fMN1GeCIbNQOdPjoOqbDwLXf1+ll50EWOiIlA9c58ED1eeGsFBV8quD/DAsL7xEdqqvARLtMpKDLMI+sW9osA=
Received: by 10.67.102.12 with SMTP id e12mr2841520ugm.1182523118830;
	Fri, 22 Jun 2007 07:38:38 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id v58sm2807450ugv.2007.06.22.07.38.37
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 07:38:38 -0700 (PDT)
Message-ID: <467BDEE5.30807@gmail.com>
Date: Fri, 22 Jun 2007 16:38:29 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
 suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

You don't seem to understand my point. Formal compliance is
irrelevant. The IETF isn't in the business of compliance,
conformance, or commenting on commercial products. What is
out there as running code is history and words in RFCs
will not change it.

     Brian

On 2007-06-22 16:23, Hemant Singh (shemant) wrote:
> Hi Brian,
> 
> IETF can only make recommendations to implementers, they cannot force
> implementers to implement anything.  However, IETF is the authority on
> whether an implementation is compliant with an IETF specification.  By
> making our proposed change to 2462bis, we are saying that old
> implementations are no longer compliant with the new 2462bis I-D.  If an
> old implementation wishes to comply with the new 2462bis, then the
> software needs to be upgraded (by eliminating the "grandfathering"
> clause).  This provides incentive for software upgrades to prevent the
> security problem found in our I-D.  
> 
> Hemant
> 
> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
> Sent: Friday, June 22, 2007 10:09 AM
> To: Hemant Singh (shemant)
> Cc: JINMEI Tatuya / ????; ipv6@ietf.org
> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
> changes suggested to 2462bis-08
> 
> Hemant,
> 
> Your logic escapes me. Old implementations are *old* and will continue
> to do whatever their code does.
> No words in 2462bis or 2462ter or anywhere can change that. I think your
> proposal is a no-op.
> 
>      Brian
> 
> On 2007-06-22 15:05, Hemant Singh (shemant) wrote:
>> Hi Tatuya,
>>
>> Thanks for the quick review of section 5 in our new I-D.  Your reading
> 
>> of section 5 is correct - we have proposed both new and old 
>> implementations to always perform DAD for any unicast address. You are
> 
>> also correct that the gross change we have proposed over 2462bis is 
>> that old implementations MUST also not skip DAD. We stress about old 
>> implementations because if older implementations that are already 
>> deployed continue to be deployed for say, the next 5-10 years, that's 
>> not good. A software upgrade to older implementation is certainly 
>> possible.
>>
>> We have given a solid reason for our case - it's presented in Section 
>> 2, bullet 4 of our I-D. Please see if our reasoning is solid enough to
> 
>> convince IETF.
>>
>> Thanks.
>>
>> Hemant
>>
>> -----Original Message-----
>> From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]
>> Sent: Thursday, June 21, 2007 10:40 PM
>> To: Hemant Singh (shemant)
>> Cc: ipv6@ietf.org; internet-drafts@ietf.org; Wes Beebee (wbeebee); 
>> Ralph Droms (rdroms)
>> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent 
>> changes suggested to 2462bis-08
>>
>> At Thu, 21 Jun 2007 12:31:58 -0400,
>> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
>>
>>> Please see section 5 of our I-D for a proposed change to 2462bis-08 -
> 
>>> we hear this I-D is in Editor's queue and any changes to it must be 
>>> given ASAP.
>> (with the document editor hat of 2462bis on)
>>
>> >From a quick look at Section 5 (and that section only), the key point 
>>> of
>> the proposed change is:
>>
>>   skipping DAD is NOT RECOMMENDED, and new implementations MUST NOT do
>>   it (but existing ones still performing the optimization will not be
>>   accused of non-conformance)
>>
>> to
>>
>>   skipping DAD is completely prohibited, and all new/old
>>   implementations MUST always perform DAD for any address.
>>
>> Is that correct?
>>
>> If so, I suspect it's too controversial to merge in 2462bis at this 
>> stage.  This part was indeed a result of very heated discussions, and 
>> even though (I believe) we all knew that simply prohibiting it without
> 
>> exception was a cleaner resolution, we failed to reach a clear 
>> consensus on it; hence the current text as a sort of compromise.
>>
>> If your new draft could now perfectly convince those who opposed to 
>> prohibiting the DAD optimization before 2462bis goes to the AUTH48 
>> state, I, for one, would be happy to include it to the final version 
>> of 2462bis.  But I cannot be that optimistic.
>>
>> In any event, I don't think changing the phrase matters much; we 
>> already clearly state new implementations MUST NOT skip DAD, so the 
>> change only affects existing implementations.  I suspect a certain 
>> amount of existing implementations that skip DAD as specified in
>> RFC2462 will still keep the current behavior whatever the new 2462bis 
>> RFC specifies.  But they'll eventually be replaced with new 
>> implementations, which, if conforming to 2462bis, won't perform DAD 
>> skipping.
>>
>> 					JINMEI, Tatuya
>> 					Communication Platform Lab.
>> 					Corporate R&D Center, Toshiba
>> Corp.
>> 					jinmei@isl.rdc.toshiba.co.jp
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 10:42:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1kKl-00032P-2W; Fri, 22 Jun 2007 10:41:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1kKj-00032J-0u
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:41:57 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1kKh-0007Ni-Jk
	for ipv6@ietf.org; Fri, 22 Jun 2007 10:41:57 -0400
Received: by ug-out-1314.google.com with SMTP id k3so2108044ugf
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 07:41:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KXTdPRFoxf9wyjrPNJE9ps7HCTcWUPICCSa6tgbIOj7XGhEhyb6IuMVeJkK/M2HrACUWytFkqJfp5KhgmhAaZngiQjai5cSqEkOIK90+Ax+6ZiBOCRaUKZ44exxmEFUAdyAGJdmzVtdsFL6bq59Ol4OCeD9yvkhfKOiY9EZ3Cr8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=SQ6aKnBiQIJ7LtJi/n+vM8cOmOER/M1yTMbnNhDen+b2J117GGbFP5qSRZu1EnzIq3oFNsTTKOAqgWG+6WC8lwphwwUdS05Rt/1lzPTyGJ7/rkc/D2ywEN0dBlj9/R6/AHPmFOnO+lnX+L5XWmuJfqj9I/Klq+aKbBodZfbXIyQ=
Received: by 10.67.102.16 with SMTP id e16mr2858143ugm.1182523314872;
	Fri, 22 Jun 2007 07:41:54 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id s59sm2840498uga.2007.06.22.07.41.53
	(version=SSLv3 cipher=RC4-MD5); Fri, 22 Jun 2007 07:41:54 -0700 (PDT)
Message-ID: <467BDFB0.5090803@gmail.com>
Date: Fri, 22 Jun 2007 16:41:52 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <B6BCFDE9-8DFD-420E-B146-C2B80C41BA84@nokia.com>
	<467BC3EF.4050107@gmail.com> <467BD659.1040708@innovationslab.net>
In-Reply-To: <467BD659.1040708@innovationslab.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: IPv6 WG <ipv6@ietf.org>, bob.hinden@nokia.com
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-ra-flags-option-00.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

If that's the only implication, I'm not sure it's worth
adding. It's a bit worrisome for future interoperability
(i.e. we shouldn't use this to add flags which will cause
failures if they are ignored).

     Brian

On 2007-06-22 16:02, Brian Haberman wrote:
> I would say that it if a node does not support this new option, it will
> probably not support any new functionality using the extended bit field.
>  I am rather neutral on whether adding such text is necessary.
> 
> Regards,
> Brian
> 
> 
> Brian E Carpenter wrote:
>> Sorry to be slightly late...
>>
>> I note that 2461bis says that unrecognized options MUST
>> be ignored. So that means that back-level implementations
>> will ignore any flag bits sent with this new option. Does
>> that have any side-effects that should be noted?
>>
>>     Brian
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 11:03:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1kfG-0007M7-AG; Fri, 22 Jun 2007 11:03:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1kfF-0007M2-Cd
	for ipv6@ietf.org; Fri, 22 Jun 2007 11:03:09 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1kfC-0003tn-3A
	for ipv6@ietf.org; Fri, 22 Jun 2007 11:03:09 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5MF347g020931
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 22 Jun 2007 10:03:04 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5MF33Dc010796; Fri, 22 Jun 2007 08:03:04 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5MF30Dh010621; Fri, 22 Jun 2007 08:03:03 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 08:03:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jun 2007 08:02:15 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0aku0fAmWGPmdSqu5zT5IuOBXnwAck6tw
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com><2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org><46785A65.7060505@internap.com><F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com><E72F5476-D072-44B6-A848-F206C15BBC22@icann.org><467ADA2F.6060100@internap.com><1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org><39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com><5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com><467B1407.90609@internap.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>
	<318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "james woodyatt" <jhw@apple.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 22 Jun 2007 15:03:03.0270 (UTC)
	FILETIME=[6E7BE060:01C7B4DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Thursday, June 21, 2007 6:11 PM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> On Jun 21, 2007, at 17:22, Templin, Fred L wrote
> > From: Scott Leibrand [mailto:sleibrand@internap.com]
> >>
> >> That assertion has been made, but I don't think we can=20
> treat it as =20
> >> anything more than a preference by non-technical business people.
> >
> > [...] Some say: "probability of collision must be zero",=20
> and others =20
> > say: "birthday paradox says risk of collision is practically nil". =20
> > Wouldn't ULA-C satisfy both sides?
>=20
> One of those two sides is presenting technical criteria for =20
> satisfying unstated and mysterious non-technical goals.  Is it too =20
> much to ask for less mystery and more transparency in working group =20
> proceedings?

I couldn't agree more about less mystery and more transparency.
The use-case I am most interested in is Mobile Ad-Hoc Networks
(MANETs) in which two or more MANETs can merge (e.g., due to
mobility). If each MANET used ULA-C's, then they could inject
each others' prefixes into their IGPs with no opportunity for
collision. If each MANET instead used RFC4193 ULAs, then they
could *probably* still inject each others' prefixes. But,
however small the risk of collision, RFC4193 ULAs still have
one drawback that ULA-C's do not - uncertainty.

So perhaps another question is whether it is too much to ask
for more certainty (ULA-C) and less mystery (RFC4193 ULA)?

Fred
fred.l.templin@boeing.com=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 11:05:29 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1khU-0004Wk-5G; Fri, 22 Jun 2007 11:05:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1khT-0004W0-7L
	for ipv6@ietf.org; Fri, 22 Jun 2007 11:05:27 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1khR-0004Td-SZ
	for ipv6@ietf.org; Fri, 22 Jun 2007 11:05:27 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5MF5HD9004241
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 22 Jun 2007 08:05:17 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5MF5Gnf016037; Fri, 22 Jun 2007 08:05:16 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5MF593c015671; Fri, 22 Jun 2007 08:05:16 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 08:05:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jun 2007 08:05:08 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B3@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <70DE64CEFD6E9A4EB7FAF3A063141066707080@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace0Sp3hf1tn5iLBSNq9WPvSMbHcgQACBBVwAB8gibAAAwaX0A==
References: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com>
	<70DE64CEFD6E9A4EB7FAF3A063141066707080@mail>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Kevin Kargel" <kkargel@polartel.com>, "Leo Vegoda" <leo.vegoda@icann.org>,
	"Scott Leibrand" <sleibrand@internap.com>
X-OriginalArrivalTime: 22 Jun 2007 15:05:10.0024 (UTC)
	FILETIME=[BA090080:01C7B4DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Kevin Kargel [mailto:kkargel@polartel.com]=20
> Sent: Friday, June 22, 2007 6:18 AM
> To: Templin, Fred L; Leo Vegoda; Scott Leibrand
> Cc: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-ula-central-02.txt
>=20
> I believe the implication comes when people assume that ULA-C=20
> addresses
> will be applied on hosts that need direct communication with the DFZ.
> As ULA-C is "non-routable" then NAT or some sort of proxy would be
> required.

But, don't the multi-addressing capabilities of IPv6 already
solve that? If the communications scope is within a site (or,
between two merged sites) then ULA-C can be used. If instead
the scope crosses the DFZ, then a globally-routable address
must be used. Why would we ask site border routers to NAT
IPv6 when the problem is solved by address selection at the
source and filtering at the site border routers?

Fred
fred.l.templin@boeing.com
=20
> In a network I was designing it would be a non-issue.  If a host
> required access to the DFZ it would get a PI address.  Why make things
> complicated when you can make them simple?=20
>=20
> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> > Sent: Thursday, June 21, 2007 5:27 PM
> > To: Leo Vegoda; Scott Leibrand
> > Cc: ipv6@ietf.org
> > Subject: RE: draft-ietf-ipv6-ula-central-02.txt
> >=20
> > Maybe I am missing the point, but there seems to be an=20
> > implication that ULA-C necessarily implies IPv6 NAT; am I=20
> > misinterpreting? If not, then I don't quite understand why=20
> > this implication is being drawn. Can someone please explain?
> >=20
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >=20
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >=20
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 12:29:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1m0K-0002wo-5t; Fri, 22 Jun 2007 12:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1m0I-0002uB-3O
	for ipv6@ietf.org; Fri, 22 Jun 2007 12:28:58 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1lwm-0006nn-Jw
	for ipv6@ietf.org; Fri, 22 Jun 2007 12:25:22 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 22 Jun 2007 09:25:20 -0700
X-IronPort-AV: i="4.16,452,1175497200"; d="scan'208"; a="4459094:sNHT21273888"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l5MGPJ6j030435; 
	Fri, 22 Jun 2007 09:25:19 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5MGPHmo009679;
	Fri, 22 Jun 2007 16:25:17 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 09:25:17 -0700
Received: from [10.32.244.219] ([10.32.244.219]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 09:25:17 -0700
In-Reply-To: <467BDEE5.30807@gmail.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Fri, 22 Jun 2007 09:25:13 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Jun 2007 16:25:17.0152 (UTC)
	FILETIME=[EB4E8600:01C7B4E9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=887; t=1182529519;
	x=1183393519; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20;
	bh=gnbGc9wJm8ghQfyi11hZ++9P10vrI//P3e9DrY/p1uc=;
	b=BYullOgjslFcnBuSjRuRTUI3KUyk0hKJGhRsywQ7iyg563grVt8w7tjjjM1tgCvf4f2JSn4z
	zwqKI9IyxCTSye0Xpw5rltSpF6b1Z0zz8Ski2TnWJB46dlqUYy98t2+F;
Authentication-Results: sj-dkim-4; header.From=fred@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 22, 2007, at 7:38 AM, Brian E Carpenter wrote:
> What is out there as running code is history and words in RFCs will  
> not change it.

I think his point is that a new IPv6 implementation has just been  
released into the market and is not operating very well. Forget the  
compliance language; what he's saying is that the various IPv6  
implementations around don't run in his lab as well as advertised -  
the running code doesn't run all that well - and he has some  
suggestions for Vista Service Pack 1, MacOSX Leopard, Linux, etc.

How about we keep this on the technical content of what he has to  
say? Do you believe, and do others believe, that the problems he  
describes are real? If not, how would you suggest he look at it in  
order to see things your way? If so, do you and others believe that  
the behavior he suggests will address the issues?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 13:10:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1me1-0003B0-Eg; Fri, 22 Jun 2007 13:10:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1me0-0003Ak-Bd
	for ipv6@ietf.org; Fri, 22 Jun 2007 13:10:00 -0400
Received: from 69-30-97-91.dv1mn.easystreet.com ([69.30.97.91]
	helo=reprise.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I1mdy-0004YS-PO
	for ipv6@ietf.org; Fri, 22 Jun 2007 13:10:00 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l5MH9uO5003461
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 10:09:56 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l5MH9uEN003458;
	Fri, 22 Jun 2007 10:09:56 -0700 (PDT) (envelope-from george)
Date: Fri, 22 Jun 2007 10:09:56 -0700 (PDT)
Message-Id: <200706221709.l5MH9uEN003458@mail.reprise.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00
X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I couldn't agree more about less mystery and more transparency.
> The use-case I am most interested in is Mobile Ad-Hoc Networks
> (MANETs) in which two or more MANETs can merge (e.g., due to
> mobility). If each MANET used ULA-C's, then they could inject
> each others' prefixes into their IGPs with no opportunity for
> collision. If each MANET instead used RFC4193 ULAs, then they
> could *probably* still inject each others' prefixes. But,
> however small the risk of collision, RFC4193 ULAs still have
> one drawback that ULA-C's do not - uncertainty.

Certainty in the abstract does not equate to certainty in the
real world.

> So perhaps another question is whether it is too much to ask
> for more certainty (ULA-C) and less mystery (RFC4193 ULA)?

Personally, I am less certain about the probability of ULA-Cs
being administered such that a collision will never happen
than I am about the unlikelyhood of a collision between
randomly assigned ULAs.                       -- George Mitchell

> Fred
> fred.l.templin@boeing.com


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 14:07:29 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1nWx-000685-Ln; Fri, 22 Jun 2007 14:06:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1nWw-000678-FM
	for ipv6@ietf.org; Fri, 22 Jun 2007 14:06:46 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1nWu-0005zv-5I
	for ipv6@ietf.org; Fri, 22 Jun 2007 14:06:46 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5MI6hco015863
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 22 Jun 2007 13:06:43 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5MI6gbg027881; Fri, 22 Jun 2007 11:06:42 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5MI6aEm027663; Fri, 22 Jun 2007 11:06:37 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 11:06:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Jun 2007 11:05:46 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <200706221709.l5MH9uEN003458@mail.reprise.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace08DbIQwPbxwqrSkWw+pVYOTVtCAAA3kjw
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: <george+ipng@m5p.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 22 Jun 2007 18:06:35.0115 (UTC)
	FILETIME=[120E13B0:01C7B4F8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: george+ipng@m5p.com [mailto:george+ipng@m5p.com]=20
> Sent: Friday, June 22, 2007 10:10 AM
> To: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-ula-central-02.txt
>=20
> > I couldn't agree more about less mystery and more transparency.
> > The use-case I am most interested in is Mobile Ad-Hoc Networks
> > (MANETs) in which two or more MANETs can merge (e.g., due to
> > mobility). If each MANET used ULA-C's, then they could inject
> > each others' prefixes into their IGPs with no opportunity for
> > collision. If each MANET instead used RFC4193 ULAs, then they
> > could *probably* still inject each others' prefixes. But,
> > however small the risk of collision, RFC4193 ULAs still have
> > one drawback that ULA-C's do not - uncertainty.
>=20
> Certainty in the abstract does not equate to certainty in the
> real world.

Yes - I have to agree with this statement.
=20
> > So perhaps another question is whether it is too much to ask
> > for more certainty (ULA-C) and less mystery (RFC4193 ULA)?
>=20
> Personally, I am less certain about the probability of ULA-Cs
> being administered such that a collision will never happen
> than I am about the unlikelyhood of a collision between
> randomly assigned ULAs.                       -- George Mitchell

Would it make you feel more certain if the ULA-Cs were
self-generated by sites exactly as in (RFC4193, Section 3.2)
and then "registered" with a central authority that would
register the address as long as it is not a duplicate? I
don't think ('draft-ietf-ipv6-ula-central', Section 3.2)
currently says that, but it seems like it would result in
a scenario that is no worse than for RFC4193 yet with a
central authority accountable for certifying uniqueness.=20

That said, I would be astonished if this idea has not been
entertained and debated before.

Thanks - Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 14:50:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1oCs-00025V-56; Fri, 22 Jun 2007 14:50:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1oCq-00020L-FU
	for ipv6@ietf.org; Fri, 22 Jun 2007 14:50:04 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1oCp-0001Ms-5q
	for ipv6@ietf.org; Fri, 22 Jun 2007 14:50:04 -0400
Received: from [208.73.31.18] (account sleibrand@mail.internap.com HELO
	[10.198.243.159])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84876780; Fri, 22 Jun 2007 14:50:02 -0400
Message-ID: <467C19D5.6000900@internap.com>
Date: Fri, 22 Jun 2007 11:49:57 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <467B8366.9050905@gmail.com>
In-Reply-To: <467B8366.9050905@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> On 2007-06-21 18:00, Scott Leibrand wrote:
>
>> As far as I know there's no mechanism to delegate reverse DNS for a 
>> locally generated ULA, since there's no "ownership".  
>
> Please read RFC 4193 section 4.4.
>
As I read RFC 4193 section 4.4, it confirms my previous understanding 
that there is no mechanism (and should be no mechanism) for delegating 
reverse DNS for a locally generated ULA.  To my mind, this is a reason 
for adopting draft-ietf-ipv6-ula-central-02.txt: the registration of the 
ULA-C blocks allows the registrar to delegate reverse DNS authority (to 
servers with globally routable non-ULA addresses) while avoiding the 
problems outlined in RFC 4193 section 4.4.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 15:14:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1oZc-0000Ca-D4; Fri, 22 Jun 2007 15:13:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1oZb-0000C5-1l
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:13:35 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1oZS-0001sd-Sq
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:13:34 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 49CAF140C098;
	Fri, 22 Jun 2007 21:13:24 +0200 (CEST)
Message-ID: <467C1F53.9070600@spaghetti.zurich.ibm.com>
Date: Fri, 22 Jun 2007 20:13:23 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1714951395=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1714951395==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig544823A06EE0E4FCBC133978"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig544823A06EE0E4FCBC133978
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Templin, Fred L wrote:
> George Mitchell wrote:
>> Personally, I am less certain about the probability of ULA-Cs
>> being administered such that a collision will never happen
>> than I am about the unlikelyhood of a collision between
>> randomly assigned ULAs.                       -- George Mitchell
>=20
> Would it make you feel more certain if the ULA-Cs were
> self-generated by sites exactly as in (RFC4193, Section 3.2)
> and then "registered" with a central authority that would
> register the address as long as it is not a duplicate? I
> don't think ('draft-ietf-ipv6-ula-central', Section 3.2)
> currently says that, but it seems like it would result in
> a scenario that is no worse than for RFC4193 yet with a
> central authority accountable for certifying uniqueness.=20
>=20
> That said, I would be astonished if this idea has not been
> entertained and debated before.

You mean just like what http://www.sixxs.net/tools/grh/ula/ is doing?
Or similarly for IPv4: http://www.chiark.greenend.org.uk/cam-grin/

Debated only a teeny little bit.

The 'problem' that people have with such a mechanism (even if run by IANA=
)
seems to be that they 'require' reverse DNS and they want a delegation fr=
om
ip6.arpa to their nameservers.

IMHO then again, if you are requiring reverse DNS you clearly are connect=
ing
some way or another to the at large Internet, thus then you come back to =
the
point of asking these folks how one can reach that at-large Internet from=

those blocks that are 'local'. Saying "we will just put global unicast IP=
s for
the reverse DNS servers and route them inside" means you have global unic=
ast
IPs, and I sure hope they won't change, thus clearly there is also some o=
ther
form of addresses involved there. And please don't say NAT. If one is goi=
ng
the NAT way, please stick to IPv4, I don't want to program code for that.=


Thus the next iteration: where do those global unicast addresses that are=
 very
stable and can be used for reverse DNS come from? Need some "PI" folks? :=
)


One possible way to (partially) solve the latter would be to say "fd00::/=
32 is
services, fd00::53 is always a DNS server which is capable of resolving".=

But that proposal of having anycasted recursive 'service' DNS servers got=
 shot
down.

Greets,
 Jeroen


--------------enig544823A06EE0E4FCBC133978
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ8H1MuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+gBAJ4meBV05kUx2RKmpRAI5AqW5yM+
GgCdE4AtdD7H+g7SMJJReo4mS9rTgd4=
=pmsa
-----END PGP SIGNATURE-----

--------------enig544823A06EE0E4FCBC133978--


--===============1714951395==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1714951395==--




From ipv6-bounces@ietf.org Fri Jun 22 15:19:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1oew-00021j-3h; Fri, 22 Jun 2007 15:19:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1oeu-00021W-FQ
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:19:04 -0400
Received: from 69-30-97-91.dv1mn.easystreet.com ([69.30.97.91]
	helo=reprise.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1oet-0002zT-33
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:19:04 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l5MJJ1CH005221
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 12:19:02 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l5MJJ1qt005218;
	Fri, 22 Jun 2007 12:19:01 -0700 (PDT) (envelope-from george)
Date: Fri, 22 Jun 2007 12:19:01 -0700 (PDT)
Message-Id: <200706221919.l5MJJ1qt005218@mail.reprise.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00
X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Would it make you feel more certain if the ULA-Cs were
> self-generated by sites exactly as in (RFC4193, Section 3.2)
> and then "registered" with a central authority that would
> register the address as long as it is not a duplicate? I
> don't think ('draft-ietf-ipv6-ula-central', Section 3.2)
> currently says that, but it seems like it would result in
> a scenario that is no worse than for RFC4193 yet with a
> central authority accountable for certifying uniqueness. 

Certainly not.  I have even less confidence that everyone else
will play by this rule than I do in the competence of the
putative central registry.

The chance of a collision between randomly-generated prefixes
is REALLY, REALLY, REALLY small -- MUCH smaller than the
probability of any real world event you would care to cite.
-- George Mitchell

> That said, I would be astonished if this idea has not been
> entertained and debated before.
>
> Thanks - Fred
> fred.l.templin@boeing.com


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 15:22:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1oiO-0003ij-5C; Fri, 22 Jun 2007 15:22:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1oiM-0003iY-73
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:22:38 -0400
Received: from wa-out-1112.google.com ([209.85.146.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1oiJ-0003TG-Te
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:22:38 -0400
Received: by wa-out-1112.google.com with SMTP id k17so115488waf
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 12:22:34 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=ZU0SEJCAqweND3zEU5k60uft+bZfq5sv8EsmgczAjILnfzqI3biHJ8xcPHNCP68XPSo5kWItetnjT05cuzPz/7oo0QsasUD+RtzAU2RhHZxkVrVM/47zXstFb5Htt3rL35xIfmFvMTnDy4sht3DNhoT+VsjV/2jmZ2US7tVcDBE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=NaQEEKuYi+vXS8BCTKyPezSblaCfCsLi9kMMN7gkZypQmpd7CNdS2GiBpM8wMH3IdnrW0MLkZsns0hZvXkRKQUa2tyY4wXRHTsYJ4IAYp7RnPXpDsdiWECC6SMEhRXU6B5uLw3iLvCeX+1ROmPU3eklFcLx+RykaWcKtUcWsexc=
Received: by 10.115.76.1 with SMTP id d1mr3253883wal.1182540154824;
	Fri, 22 Jun 2007 12:22:34 -0700 (PDT)
Received: by 10.114.154.5 with HTTP; Fri, 22 Jun 2007 12:22:34 -0700 (PDT)
Message-ID: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
Date: Fri, 22 Jun 2007 12:22:34 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

I had raised this earlier in December 2005
http://www1.ietf.org/mail-archive/web/ipv6/current/msg06020.html .

The definition of IPv6 fragment is not clear.  Infact different
protocols assume it differently, example are IPsec and SIIT. I do not
have implementations to play with, however I feel we need to close
this issue along with other related issues, like tiny fragments. The
discussion there was:

"
Vishwas Manral wrote:

I have a doubt regarding the fragment header. Why do we need the M
flag in the "fragment header" at all for IPv6? Having the fragment
header itself would tell it's a fragment and would distinguish between
the first fragment and a non-fragment.

In IPv4 we did not have a fragment header, so the M flag was logical
to have for distinguishing the first and a non fragment.

That said; how should the case where we have the fragment header and
both the Fragment Offset and the M flag is 0 be treated?"

Thanks,
Vishwas

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 15:29:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1ooV-0000ER-QM; Fri, 22 Jun 2007 15:28:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1ooT-0000EJ-Qu
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:28:57 -0400
Received: from 69-30-97-91.dv1mn.easystreet.com ([69.30.97.91]
	helo=reprise.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1ooG-00055G-88
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:28:57 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l5MJShpr005422
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 12:28:43 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l5MJSh6I005419;
	Fri, 22 Jun 2007 12:28:43 -0700 (PDT) (envelope-from george)
Date: Fri, 22 Jun 2007 12:28:43 -0700 (PDT)
Message-Id: <200706221928.l5MJSh6I005419@mail.reprise.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00
X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > Would it make you feel more certain if the ULA-Cs were
> > self-generated by sites exactly as in (RFC4193, Section 3.2)
> > and then "registered" with a central authority that would
> > register the address as long as it is not a duplicate? I
> > don't think ('draft-ietf-ipv6-ula-central', Section 3.2)
> > currently says that, but it seems like it would result in
> > a scenario that is no worse than for RFC4193 yet with a
> > central authority accountable for certifying uniqueness. 
> 
> Certainly not.  I have even less confidence that everyone else
> will play by this rule than I do in the competence of the
> putative central registry.

Expanding on this point just a little bit, I should say that I
AM as confident that locally-generated ULA-Cs will fail to collide
as I am confident that locally-generated ULAs will fail to collide.
But the presumed warm, fuzzy feeling one might get from "registering"
these locally-generated ULA-Cs is an illusion we shouldn't promote.
-- George Mitchell

> The chance of a collision between randomly-generated prefixes
> is REALLY, REALLY, REALLY small -- MUCH smaller than the
> probability of any real world event you would care to cite.
> -- George Mitchell
> 
> > That said, I would be astonished if this idea has not been
> > entertained and debated before.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 15:35:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1ouf-00055b-Qc; Fri, 22 Jun 2007 15:35:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1oue-00055W-ED
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:35:20 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1oud-00061S-50
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:35:20 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 855CE11431;
	Fri, 22 Jun 2007 19:35:18 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Scott Leibrand <sleibrand@internap.com>
In-Reply-To: Your message of "Fri, 22 Jun 2007 11:49:57 MST."
	<467C19D5.6000900@internap.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <467B8366.9050905@gmail.com>
	<467C19D5.6000900@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 22 Jun 2007 19:35:18 +0000
Message-ID: <29523.1182540918@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> >> As far as I know there's no mechanism to delegate reverse DNS for a 
> >> locally generated ULA, since there's no "ownership".  

> > Please read RFC 4193 section 4.4.

> As I read RFC 4193 section 4.4, it confirms my previous understanding 
> that there is no mechanism (and should be no mechanism) for delegating 
> reverse DNS for a locally generated ULA.  To my mind, this is a reason 
> for adopting draft-ietf-ipv6-ula-central-02.txt: the registration of the 
> ULA-C blocks allows the registrar

who is the registrar?

>                                   to delegate reverse DNS authority (to 
> servers with globally routable non-ULA addresses) while avoiding the 
> problems outlined in RFC 4193 section 4.4.

none of this explains why it's not a simple RIR policy matter to create a
new kind of PI space that's cheaper/easier to get due to the recommendation
that it not be accepted into the DFZ.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 15:51:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1p9v-0008Dn-5c; Fri, 22 Jun 2007 15:51:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1p8t-0005qP-M8; Fri, 22 Jun 2007 15:50:03 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1p8s-0000Dx-2Q; Fri, 22 Jun 2007 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id ECBFD26EAA;
	Fri, 22 Jun 2007 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I1p8r-0008Qy-Re; Fri, 22 Jun 2007 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I1p8r-0008Qy-Re@stiedprstage1.ietf.org>
Date: Fri, 22 Jun 2007 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: ipv6@ietf.org
Subject: I-D ACTION:draft-ietf-ipv6-ra-flags-option-01.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: IPv6 Router Advertisement Flags Option
	Author(s)	: B. Haberman, R. Hinden
	Filename	: draft-ietf-ipv6-ra-flags-option-01.txt
	Pages		: 8
	Date		: 2007-6-22
	
The IPv6 Neighbor Discovery's Router Advertisement message contains
   an 8-bit field reserved for single-bit flags.  Several protocols have
   reserved flags in this field and others are preparing to reserve a
   sufficient number of flags to exhaust the field.  This document
   defines an option to the Router Advertisement message that expands
   the available number of flag bits available.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ra-flags-option-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ipv6-ra-flags-option-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-ipv6-ra-flags-option-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: <2007-6-22123632.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipv6-ra-flags-option-01.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--NextPart--





From ipv6-bounces@ietf.org Fri Jun 22 16:03:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1pLe-0000AM-Kk; Fri, 22 Jun 2007 16:03:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1pLd-0000AH-At
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:03:13 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1pLb-0007KQ-W3
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:03:13 -0400
Received: from [63.251.161.194] (account sleibrand@mail.internap.com HELO
	[63.251.161.194])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 84882730; Fri, 22 Jun 2007 16:03:11 -0400
Message-ID: <467C2AFA.6000306@internap.com>
Date: Fri, 22 Jun 2007 13:03:06 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <467B8366.9050905@gmail.com>
	<467C19D5.6000900@internap.com> <29523.1182540918@sa.vix.com>
In-Reply-To: <29523.1182540918@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul Vixie wrote:
>> As I read RFC 4193 section 4.4, it confirms my previous understanding 
>> that there is no mechanism (and should be no mechanism) for delegating 
>> reverse DNS for a locally generated ULA.  To my mind, this is a reason 
>> for adopting draft-ietf-ipv6-ula-central-02.txt: the registration of the 
>> ULA-C blocks allows the registrar
>>     
>
> who is the registrar?
>   

The draft under discussion assumes, as do I, that it will be the local 
RIR, in my case ARIN.

>>                                   to delegate reverse DNS authority (to 
>> servers with globally routable non-ULA addresses) while avoiding the 
>> problems outlined in RFC 4193 section 4.4.
>>     
>
> none of this explains why it's not a simple RIR policy matter to create a
> new kind of PI space that's cheaper/easier to get due to the recommendation
> that it not be accepted into the DFZ.
>   

It could be done that way, but if it is, don't expect a "global" 
policy.  In addition, the netblock for ULA-C is already reserved by 
previous RFCs, out of a well known ULA netblock.  It seems like a simple 
IETF matter to approve a version of draft-ietf-ipv6-ula-central that 
directs IANA to assign portions of this netblock to RIRs for them to use 
in the manner specified in the draft.

If the IETF decides not to advance draft-ietf-ipv6-ula-central in favor 
of allowing RIRs to do something similar on their own, that will likely 
be what happens.  But if the RIRs were to advance a policy that looks 
like ULA-C at this point, they would be accused of doing an end run 
around the IETF process.  So here we are.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 16:16:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1pXv-0003oD-Cd; Fri, 22 Jun 2007 16:15:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1pXu-0003ny-H4
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:15:54 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1pXu-0002DJ-5N
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:15:54 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id A49C6353D8;
	Fri, 22 Jun 2007 16:15:53 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 2F629144373;
	Fri, 22 Jun 2007 20:15:53 +0000 (UTC)
Message-ID: <467C2DF8.1040400@hp.com>
Date: Fri, 22 Jun 2007 16:15:52 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
In-Reply-To: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Vishwas Manral wrote:
> Hi,
> 
> I had raised this earlier in December 2005
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg06020.html .
> 
> The definition of IPv6 fragment is not clear.  Infact different
> protocols assume it differently, example are IPsec and SIIT. I do not
> have implementations to play with, however I feel we need to close
> this issue along with other related issues, like tiny fragments. The
> discussion there was:

Well,  SIIT doesn't provide definition for the IPv6 fragment.  It simply
adds some special cases to handling the fragment header under SIIT conditions.

> 
> "
> Vishwas Manral wrote:
> 
> I have a doubt regarding the fragment header. Why do we need the M
> flag in the "fragment header" at all for IPv6? Having the fragment
> header itself would tell it's a fragment and would distinguish between
> the first fragment and a non-fragment.

How do you tell the terminating fragment from a non-terminating one without
an M bit.

> 
> In IPv4 we did not have a fragment header, so the M flag was logical
> to have for distinguishing the first and a non fragment.
> 
> That said; how should the case where we have the fragment header and
> both the Fragment Offset and the M flag is 0 be treated?"

Handle it as a self-terminating fragment, ie. you reassembly queue is
1 fragment long.  This simply follows the spec as written.

-vlad

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 16:19:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1pax-0005Ew-Bl; Fri, 22 Jun 2007 16:19:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1pEQ-0003Vv-7c
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:55:46 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1pEC-0003U3-Vp
	for ipv6@ietf.org; Fri, 22 Jun 2007 15:55:44 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 151961A4D87; Fri, 22 Jun 2007 12:54:29 -0700 (PDT)
Date: Fri, 22 Jun 2007 12:54:29 -0700
From: bill fumerola <billf@mu.org>
To: Jeroen Massar <jeroen@unfix.org>
Message-ID: <20070622195429.GG31273@elvis.mu.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <467C1F53.9070600@spaghetti.zurich.ibm.com>
User-Agent: Mutt/1.4.2.2i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, Jun 22, 2007 at 08:13:23PM +0100, Jeroen Massar wrote:
> IMHO then again, if you are requiring reverse DNS you clearly are connecting
> some way or another to the at large Internet, thus then you come back to the
> point of asking these folks how one can reach that at-large Internet from
> those blocks that are 'local'. Saying "we will just put global unicast IPs for
> the reverse DNS servers and route them inside" means you have global unicast
> IPs, and I sure hope they won't change, thus clearly there is also some other
> form of addresses involved there. 

why does wanting to provide PTRs for ULA-C addresses imply they have
   any sort of global connectivity? machines can reach a recursive server
   that is able to reach another ULA-C delegation's NS.

why can't the servers delegated ULA-C prefixes change addresses? i update
   my arpa delegation NS glue occasionally without problems.

why should all the partner companies who i peer with and use our collective
   ULA-C prefixes to communicate also have to setup some half-baked DNS
   "peering" (read: selective slaving) when there is a perfectly good
   way of them finding those PTR records through a decades-long proven
   service? how does slaving scale when i have hundreds of partners?

why does a host having both a ULA-C address and a global unicast address
   cause you grief? i may have entirely different routing policies for
   traffic based on their addressing (global unicast is dumped out local
   transit links, ULA[-C] to ULA[-C] addressing is carried on my backbone,
   VPN network, framerelay cloud, etc).

>                                   And please don't say NAT. If one is going
> the NAT way, please stick to IPv4, I don't want to program code for that.

NAT boogeyman! NAT boogeyman! everyone run, the idea must be bad! (this
has nothing to do with NAT, but way to try to get blood pressure rising).

> Thus the next iteration: where do those global unicast addresses that are very
> stable and can be used for reverse DNS come from? Need some "PI" folks? :)

they can be run from servers in that org's PI allocation.
they can run their own from a PA allocation from that organization's ISP.
they can be slaved by that organization's ISP and NS pointed at the ISP.
they can come from a company (ultradns, everydns, easydns) who provides
  such services.

just like any other reverse delegation works.

if we're going to actually delegate ULA-C blocks to orgs it makes sense
to also delegate reverse to them. we always say (in RIR-land) that
addressing and routing are completely different. i'd argue that addressing
and DNS are not completely similar. don't cause people to come up with
ideas ranging from zany to stupid to dangerous to difficult when the
standard way of operating will do just fine.

giving recursive servers some NS glue for recursives to follow and go
knocking on will reduce load on the IANA/RIR run ip6.arpa NS servers.

-- 
- bill fumerola / billf@FreeBSD.org



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 16:20:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1pc8-0005yy-U4; Fri, 22 Jun 2007 16:20:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1pc7-0005yt-Qd
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:20:15 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1pc6-0003C9-NO
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:20:15 -0400
Received: from [192.168.1.13] (86-45-73-203.b-ras2.srl.dublin.eircom.net
	[86.45.73.203])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 408D7140C07A;
	Fri, 22 Jun 2007 22:20:12 +0200 (CEST)
Message-ID: <467C2EE6.3070100@spaghetti.zurich.ibm.com>
Date: Fri, 22 Jun 2007 21:19:50 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: bill fumerola <billf@mu.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
In-Reply-To: <20070622195429.GG31273@elvis.mu.org>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.90.3,
	clamav-milter version 0.90.3 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1770647927=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1770647927==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig0964A0312216D5F8DBFC2C16"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0964A0312216D5F8DBFC2C16
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

[short version: why ULA-C, when there is IPv6 "PI" space from RIRs alread=
y?]

bill fumerola wrote:
> On Fri, Jun 22, 2007 at 08:13:23PM +0100, Jeroen Massar wrote:
>> IMHO then again, if you are requiring reverse DNS you clearly are conn=
ecting
>> some way or another to the at large Internet, thus then you come back =
to the
>> point of asking these folks how one can reach that at-large Internet f=
rom
>> those blocks that are 'local'. Saying "we will just put global unicast=
 IPs for
>> the reverse DNS servers and route them inside" means you have global u=
nicast
>> IPs, and I sure hope they won't change, thus clearly there is also som=
e other
>> form of addresses involved there.=20
>=20
> why does wanting to provide PTRs for ULA-C addresses imply they have
>    any sort of global connectivity? machines can reach a recursive serv=
er
>    that is able to reach another ULA-C delegation's NS.

Thus that recursive server is globally connected. As such hosts on the UL=
A-C
network are also able to resolve 'global' addresses and most likely end u=
p
trying to send packets there and most likely one day want to connect to i=
t
anyway as one day you might just want to use SIP from your network or do
something else than playing with your neighbors.

> why can't the servers delegated ULA-C prefixes change addresses? i upda=
te
>    my arpa delegation NS glue occasionally without problems.

You could, but doesn't that defeat the point of having "your own global u=
nique
space that never changes" if you have to contact an external site and hav=
e to
update those pointers all the time, causing delays in updates etc etc etc=
=2E

> why should all the partner companies who i peer with and use our collec=
tive
>    ULA-C prefixes to communicate also have to setup some half-baked DNS=

>    "peering" (read: selective slaving) when there is a perfectly good
>    way of them finding those PTR records through a decades-long proven
>    service? how does slaving scale when i have hundreds of partners?

For the same reasons that you also expect those companies to connect to t=
he
global Internet and that they have a recursive name server and handle all=

their network operations the same way you are doing.

Also you are claiming that PTR finding is done with a 'decades-long prove=
n
service', you are correct, but that service is for Internet hosts, not fo=
r
hosts in private (RFC1918) networks.


Thus the question is: How do RFC1918-based interconnected networks nowada=
ys
lookup these PTR records? Because that is the "decades-long proven method=
" you
are looking for.

Somehow I think it does not involve the Internet as it seems that RFC1918=

space points to AS112.

> why does a host having both a ULA-C address and a global unicast addres=
s
>    cause you grief?

You might want to see one of the other replies where I actually mentioned=
 that
this might be a possible scenario but that it might cause problems too.

> i may have entirely different routing policies for
>    traffic based on their addressing (global unicast is dumped out loca=
l
>    transit links, ULA[-C] to ULA[-C] addressing is carried on my backbo=
ne,
>    VPN network, framerelay cloud, etc)

You can also make entirely different routing policies for every /64 or fo=
r
that matter, take your /48 and split it into a /49 for for local traffic =
and
another /49 for global traffic, filtering off one of the /49 so that it
doesn't have Internet access.

What is the difference again?

>>                                   And please don't say NAT. If one is =
going
>> the NAT way, please stick to IPv4, I don't want to program code for th=
at.
>=20
> NAT boogeyman! NAT boogeyman! everyone run, the idea must be bad! (this=

> has nothing to do with NAT, but way to try to get blood pressure rising=
).

Does your blood pressure rise already that you need to use exclamation ma=
rks?

>> Thus the next iteration: where do those global unicast addresses that =
are very
>> stable and can be used for reverse DNS come from? Need some "PI" folks=
? :)
>=20
> they can be run from servers in that org's PI allocation.

So they ALSO need a PI allocation next to the ULA-C allocation, wow talki=
ng
about wasting address space and doing difficult

See above, just split your /48 into two /49's. Or for that matter, reques=
t a
/47 from a RIR justifying where you need it for.

> they can run their own from a PA allocation from that organization's IS=
P.

You mean a PA assignment, but indeed as mentioned above: when you swap IS=
P's
you need to change the reverse DNS entries. Can you be offline that long?=


> they can be slaved by that organization's ISP and NS pointed at the ISP=
=2E

Thus requiring you to again contact an external entity to update your stu=
ff,
while you wanted to be totally independent of the Internet and not to for=
get,
more importantly from that upstream ISP. What was the point of having thi=
s
globally unique address space again? Why not use PA space?

> they can come from a company (ultradns, everydns, easydns) who provides=

>   such services.

And thus having a very tight relationship with that organization. See abo=
ve.

> just like any other reverse delegation works.
>=20
> if we're going to actually delegate ULA-C blocks to orgs it makes sense=

> to also delegate reverse to them.

> we always say (in RIR-land) that addressing and routing are completely
different.

Looking at current policies, that is far from the case.

> i'd argue that addressing
> and DNS are not completely similar. don't cause people to come up with
> ideas ranging from zany to stupid to dangerous to difficult when the
> standard way of operating will do just fine.

What is wrong with that PI block which you mentioned above? Does not solv=
e all
your problems already?

> giving recursive servers some NS glue for recursives to follow and go
> knocking on will reduce load on the IANA/RIR run ip6.arpa NS servers.

Having that space not there at all also reduces it.

ULA (RFC4193) doesn't delegate NS reverses either. Nobody seems to have a=
n
issue with that (yet :).

Greets,
 Jeroen



--------------enig0964A0312216D5F8DBFC2C16
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ8LuYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I4GPAJ4uXyQwlX3fwVA4cahhFSfCfO2c
9wCeNQ8dvMIIBmVaKMAQjvZVVqYO2bQ=
=M0sf
-----END PGP SIGNATURE-----

--------------enig0964A0312216D5F8DBFC2C16--


--===============1770647927==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1770647927==--




From ipv6-bounces@ietf.org Fri Jun 22 16:26:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1phi-000884-02; Fri, 22 Jun 2007 16:26:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1phg-00087y-Sv
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:26:00 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1phg-0004Sa-KN
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:26:00 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 30E871142F;
	Fri, 22 Jun 2007 20:26:00 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: Scott Leibrand <sleibrand@internap.com>
In-Reply-To: Your message of "Fri, 22 Jun 2007 13:03:06 MST."
	<467C2AFA.6000306@internap.com> 
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <467B8366.9050905@gmail.com>
	<467C19D5.6000900@internap.com> <29523.1182540918@sa.vix.com>
	<467C2AFA.6000306@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 22 Jun 2007 20:26:00 +0000
Message-ID: <35601.1182543960@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> ... It seems like a simple IETF matter to approve a version of
> draft-ietf-ipv6-ula-central that directs IANA to assign portions of this
> netblock to RIRs for them to use in the manner specified in the draft.

if we're all agreed on that as an approach, and we're no longer considering
asking IANA to run a registration robot or asking network owners to choose
their own prefixes at random, then this is the first i've heard of it.

> If the IETF decides not to advance draft-ietf-ipv6-ula-central in favor of
> allowing RIRs to do something similar on their own, that will likely be what
> happens.  But if the RIRs were to advance a policy that looks like ULA-C at
> this point, they would be accused of doing an end run around the IETF
> process.  So here we are.

i think that's a succinct summary of the status, but i hope that the final
document (writ by whomever under whatever banner) takes account of the
possibility that a private internet can be arbitrarily large, even perhaps
larger than the current DFZ, at which point words like "public" and "private"
and "DFZ" would become meaningless, and the distinction held by FC00 likewise
meaningless.  RFC 1918 had no such dragons to slay, since everybody already
knew what an autonomous system was, and that definition isn't subjective nor
malleable based on the size and shape of the connected internet.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 16:41:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1pwR-0006ls-1l; Fri, 22 Jun 2007 16:41:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1pwO-0006lb-SY
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:41:12 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I1pwM-0003f4-LZ
	for ipv6@ietf.org; Fri, 22 Jun 2007 16:41:12 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l5MKiMKT012513;
	Fri, 22 Jun 2007 15:44:22 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 15:41:08 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 15:41:08 -0500
Message-ID: <467C34B8.20801@ericsson.com>
Date: Fri, 22 Jun 2007 16:44:40 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
In-Reply-To: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Jun 2007 20:41:08.0757 (UTC)
	FILETIME=[A9938C50:01C7B50D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Vishwas,
   I do not really see what the problem is. The M bit is required for 
two reasons

1) It is required for the length calculation of the final reassembled 
packet.
2) It is used for validity checking of fragment lengths (i.e. Non final 
fragments must be a multiple of 8 octets in length)

A fragment with offset 0 and M flag 0 is just treated as the ONLY 
fragment. No harm done.

Cheers
Suresh

Vishwas Manral wrote:
> Hi,
> 
> I had raised this earlier in December 2005
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg06020.html .
> 
> The definition of IPv6 fragment is not clear.  Infact different
> protocols assume it differently, example are IPsec and SIIT. I do not
> have implementations to play with, however I feel we need to close
> this issue along with other related issues, like tiny fragments. The
> discussion there was:
> 
> "
> Vishwas Manral wrote:
> 
> I have a doubt regarding the fragment header. Why do we need the M
> flag in the "fragment header" at all for IPv6? Having the fragment
> header itself would tell it's a fragment and would distinguish between
> the first fragment and a non-fragment.
> 
> In IPv4 we did not have a fragment header, so the M flag was logical
> to have for distinguishing the first and a non fragment.
> 
> That said; how should the case where we have the fragment header and
> both the Fragment Offset and the M flag is 0 be treated?"
> 
> Thanks,
> Vishwas
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 17:00:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1qEi-00016f-Hp; Fri, 22 Jun 2007 17:00:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1qEg-00016X-S8
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:00:06 -0400
Received: from wa-out-1112.google.com ([209.85.146.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1qEf-0002zj-Gp
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:00:06 -0400
Received: by wa-out-1112.google.com with SMTP id k17so146749waf
	for <ipv6@ietf.org>; Fri, 22 Jun 2007 14:00:05 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=AokQujeA/OUrT+h2lIjRa7Wqyvugvk2MkQb7uF+a7VQOg0SQcFQfmo5j+PkyB4AHeq3VtvL3WMIixLFDwNTPdWWQ13/ksncvf9Fe8ZjnhPGImfLNA/NODGZWFBLgINl1ozj6kyba2cRxrrumhUBCbZThiVbLP/2uKvAs5wBVJ/c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=sLy5gTK7/fyrnwASRKX07wXU3Cd1mRN9Zf6d2KlwL5Lxx68MFmK/0qq12Avh3aV6DTICcUa2/PUSejxphEIq87w0Q/aesWKDHTuX7v6xrkdwouAWvqY21lovBXMKwVqbX9jY02OW+AYwghu1zFj9Y3onGwGaJNEGfTfXmNVdLvk=
Received: by 10.115.92.2 with SMTP id u2mr3323154wal.1182546004941;
	Fri, 22 Jun 2007 14:00:04 -0700 (PDT)
Received: by 10.114.154.5 with HTTP; Fri, 22 Jun 2007 14:00:04 -0700 (PDT)
Message-ID: <77ead0ec0706221400q279c6097r7b5d22922645638a@mail.gmail.com>
Date: Fri, 22 Jun 2007 14:00:04 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>
In-Reply-To: <467C34B8.20801@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
	<467C34B8.20801@ericsson.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Suresh/ Vlad,

For SIIT the fragment header is used to signal the ability to
fragment, it does not state it is a fragment itself.

> A fragment with offset 0 and M flag 0 is just treated as the ONLY
> fragment. No harm don
But there are different policies for fragments, including some that
drop fragments. It is not the correct behavior, I feel the definition
of a fragment should be clarified.

Thanks,
Vishwas

On 6/22/07, Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> Hi Vishwas,
>    I do not really see what the problem is. The M bit is required for
> two reasons
>
> 1) It is required for the length calculation of the final reassembled
> packet.
> 2) It is used for validity checking of fragment lengths (i.e. Non final
> fragments must be a multiple of 8 octets in length)
>
> A fragment with offset 0 and M flag 0 is just treated as the ONLY
> fragment. No harm done.
>
> Cheers
> Suresh
>
> Vishwas Manral wrote:
> > Hi,
> >
> > I had raised this earlier in December 2005
> > http://www1.ietf.org/mail-archive/web/ipv6/current/msg06020.html .
> >
> > The definition of IPv6 fragment is not clear.  Infact different
> > protocols assume it differently, example are IPsec and SIIT. I do not
> > have implementations to play with, however I feel we need to close
> > this issue along with other related issues, like tiny fragments. The
> > discussion there was:
> >
> > "
> > Vishwas Manral wrote:
> >
> > I have a doubt regarding the fragment header. Why do we need the M
> > flag in the "fragment header" at all for IPv6? Having the fragment
> > header itself would tell it's a fragment and would distinguish between
> > the first fragment and a non-fragment.
> >
> > In IPv4 we did not have a fragment header, so the M flag was logical
> > to have for distinguishing the first and a non fragment.
> >
> > That said; how should the case where we have the fragment header and
> > both the Fragment Offset and the M flag is 0 be treated?"
> >
> > Thanks,
> > Vishwas
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 17:03:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1qHv-0001pq-Po; Fri, 22 Jun 2007 17:03:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1qHu-0001pR-3d
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:03:26 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I1qHs-0003Mr-OF
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:03:26 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 22 Jun 2007 14:03:24 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAE3We0arR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,452,1175497200"; 
	d="sig'?scan'208"; a="496981864:sNHT33831242"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5ML3Obq013120; 
	Fri, 22 Jun 2007 14:03:24 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5ML3Omo018595;
	Fri, 22 Jun 2007 21:03:24 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 14:03:23 -0700
Received: from [10.32.244.219] ([10.32.244.219]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 14:03:23 -0700
In-Reply-To: <4678FD67.8010200@spaghetti.zurich.ibm.com>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
	<4678F9C0.3080600@cisco.com>
	<4678FD67.8010200@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <17D26825-5823-4445-B927-196A301FCE1F@cisco.com>
From: Fred Baker <fred@cisco.com>
Date: Fri, 22 Jun 2007 14:03:11 -0700
To: Jeroen Massar <jeroen@unfix.org>
X-Pgp-Agent: GPGMail 1.1.2 (Tiger)
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Jun 2007 21:03:23.0577 (UTC)
	FILETIME=[C530EA90:01C7B510]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2115; t=1182546204;
	x=1183410204; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Why=20does=20everyone=20see=20router=20renumbnering=2
	0as=20hard?=09(was=20Re=3A=20draft-ietf-ipv6-ula-central-02.txt=20and=20NA
	T) |Sender:=20;
	bh=HDkDXIcCUOx/GYuaHSiY8CsWTc7aBrACRuEh8PXzsYg=;
	b=IkmJDLmKw3XnOuuB6nnG6T5S8ZpnnokCmMeyz8V7fGqSwPZD5G/oZSRX0jZz525wRQr+C9qr
	TDNAezJhOiqozpv1WZTZea06cWPc41EtNux0rYAZVEVbQX3R8f2ASAem;
Authentication-Results: sj-dkim-2; header.From=fred@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard?	(was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1496972217=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1496972217==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-27-228044995"
Content-Transfer-Encoding: 7bit

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-27-228044995
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed


On Jun 20, 2007, at 3:11 AM, Jeroen Massar wrote:

>> I think there has been hype on both sides of this question.  Router
>> renumbering used to be VERY annoying.  I've now published several  
>> times
>> on the subject
>
> Any links to the papers?

A paper which in-my-non-humble-opinion covers a lot of the bases is

http://www.ietf.org/rfc/rfc4192.txt
4192 Procedures for Renumbering an IPv6 Network without a Flag Day. F.
      Baker, E. Lear, R. Droms. September 2005. (Format: TXT=52110  
bytes)
      (Updates RFC2072) (Status: INFORMATIONAL)

Actually, all renumbering is trivial, as long as nobody every  
actually writes down an address and always uses a name. The problem  
is - there are any number of places where people either are forced to  
or in fact do choose to write down an address. As soon as that  
happens, that is a place that has to be remembered and written again  
when the address needs to be changed. Documentation and human memory  
being what it is, every place where an address gets written down is a  
place that will be re-discovered because something isn't working as  
expected when a renumbering happens.

The ideal thing, of course, is that all configurations of all  
equipment are centrally managed from a common database, and all one  
has to do is change the database.

"the". It's an english word with a very interesting property. It is  
*singular*. As a result, it is very rarely the right word...

--Apple-Mail-27-228044995
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGfDkZbjEdbHIsm0MRAu9VAKDfyTZtAGzPdm8M0IEd5uC1wEIiEQCgwLE1
ZZJqIuR5io1gqn8jltCCDhc=
=uVSn
-----END PGP SIGNATURE-----

--Apple-Mail-27-228044995--


--===============1496972217==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1496972217==--




From ipv6-bounces@ietf.org Fri Jun 22 17:04:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1qJ8-0002e9-3g; Fri, 22 Jun 2007 17:04:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1qJ6-0002ci-Rj
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:04:40 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1qJ5-0003ai-IK
	for ipv6@ietf.org; Fri, 22 Jun 2007 17:04:40 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 22 Jun 2007 14:04:39 -0700
X-IronPort-AV: i="4.16,452,1175497200"; 
	d="scan'208"; a="170513731:sNHT42491529"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5ML4cgt010917; 
	Fri, 22 Jun 2007 14:04:38 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5ML4cmo019556;
	Fri, 22 Jun 2007 21:04:39 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 14:04:38 -0700
Received: from [10.32.244.219] ([10.32.244.219]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Jun 2007 14:04:38 -0700
In-Reply-To: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <98B4C137-F1CF-4835-A24D-321DC7DD2F72@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Fri, 22 Jun 2007 14:04:34 -0700
To: Mark Andrews <Mark_Andrews@isc.org>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 22 Jun 2007 21:04:38.0343 (UTC)
	FILETIME=[F1C14D70:01C7B510]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=344; t=1182546279;
	x=1183410279; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com;
	z=From:=20Fred=20Baker=20<fred@cisco.com>
	|Subject:=20Re=3A=20Why=20does=20everyone=20see=20router=20renumbnering=2
	0as=20hard?=20(was=20Re=3A=20draft-ietf-ipv6-ula-central-02.txt=20and=20NA
	T) |Sender:=20;
	bh=+cnFz+U7KWktBRBDSZtP8V031m5XKbmaTFrIN8FOZrU=;
	b=RydKXTCvZWcqwTSJvqgUYxhqYDThi1M8ga0CowZEtGOPNxRTQNqcddax1cGDK/rUGesdhogg
	y26ZDx8oYnH8lJnRQ2iXrn57cJWF3nrvOXS/3gClQZhU3xh1j0ih7FMn;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: Why does everyone see router renumbnering as hard? (was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On Jun 19, 2007, at 5:41 PM, Mark Andrews wrote:

> 	I would have thought that router renumbering should be no
> 	harder that host renumbering.  Essentially all you are
> 	changing is the higher (/48 normally) prefix bits.

assuming that all prefixes are 48 bits long, fine. Guess what. That's  
only the *first* broken assumption...

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 18:06:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1rGP-0008AF-RD; Fri, 22 Jun 2007 18:05:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1rGP-0008A6-A5
	for ipv6@ietf.org; Fri, 22 Jun 2007 18:05:57 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1rGO-0007DQ-2D
	for ipv6@ietf.org; Fri, 22 Jun 2007 18:05:57 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id B49E61A4D87; Fri, 22 Jun 2007 15:04:51 -0700 (PDT)
Date: Fri, 22 Jun 2007 15:04:51 -0700
From: bill fumerola <billf@mu.org>
To: ipv6@ietf.org
Message-ID: <20070622220451.GH31273@elvis.mu.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070622195429.GG31273@elvis.mu.org>
User-Agent: Mutt/1.4.2.2i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

[ replying to my own, so sorry... ]

On Fri, Jun 22, 2007 at 12:54:29PM -0700, bill fumerola wrote:
> if we're going to actually delegate ULA-C blocks to orgs it makes sense
> to also delegate reverse to them. we always say (in RIR-land) that
> addressing and routing are completely different. i'd argue that addressing
> and DNS are not completely similar. don't cause people to come up with
> ideas ranging from zany to stupid to dangerous to difficult when the
> standard way of operating will do just fine.

correction:
"addressing and DNS are not completely dissimilar"

-- 
- bill fumerola / billf@FreeBSD.org



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 18:36:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1rjS-0004ww-7U; Fri, 22 Jun 2007 18:35:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1rjQ-0004wr-Eo
	for ipv6@ietf.org; Fri, 22 Jun 2007 18:35:56 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1rjO-0004s6-VA
	for ipv6@ietf.org; Fri, 22 Jun 2007 18:35:56 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I1rjJ-0007yJ-Ml; Sat, 23 Jun 2007 08:05:49 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id E3E0120139;
	Sat, 23 Jun 2007 08:05:47 +0930 (CST)
Date: Sat, 23 Jun 2007 08:05:47 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: james woodyatt <jhw@apple.com>
Message-Id: <20070623080547.1d6b6de6.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



On Thu, 21 Jun 2007 11:42:28 -0700
james woodyatt <jhw@apple.com> wrote:

> On Jun 21, 2007, at 11:03, Paul Vixie wrote:
> >
> > mark andrews has [observed] that there is no need for the  
> > resolution perimeter of a PTR to differ from the routing perimeter  
> > of the IP address described by that PTR.  yet here we have a large  
> > set of folks who [are] telling us that yes we do need to be able to  
> > resolve a PTR from places where the addresses won't be routable
> > [...]
> > what's wrong with this picture?
> 
> My heretical opinion follows.
> 
<snip>

I agree with James' heretical opinion.

It seems to me that without realising it, we might be discussing
specific instances and coming from different positions on the general
points of 

* the locator and to a slightly lesser extent the identifier properties
of addresses 

* if identifier and locators should come from the same or different
number space, and for different scenarios, how important it is that
they come from the same or different number spaces

* uses of the identifier property only, and the scope of validity for
that identifier **

* uses of the locator property only and the scope of validity for that
locator (e.g. "site", global)

Maybe if we classify the different use scenarios that are being
discussed for ULAs/ULA-Cs using the above points, we'll be in a better
position to evaluate the pro's and con's of ULAs verses ULA-Cs.

Regards,
Mark.

** To explain this better using an example, I think BGPv4 originally
specified that the BGP router ID, carried in the BGP payload, must be
an IPv4 address. I'd be guessing that at the time the key property that
was being sort was BGP router ID uniqueness, and using a global IPv4
address/number value as that ID was a convenient and sure way of
achieving it. I seem to remember reading somewhere that this
requirement has now been relaxed , as it has been recognised that as
long as the BGP router-id is unique within the boundary where
uniqueness is essential, it doesn't have to be a global IPv4 address
(maybe for "pure" IPv6 BGP scenarios, where there wasn't a need to have
the BGP router-id the size of an IPv6 address, but there isn't a global
IPv4 address on the device to assign the router-id value from). It's
certainly still useful to use a global IPv4 address as the BGP
router-id, as if you use the OAM IPv4 address for the device as the BGP
router-id, implying that it is also a locator, it can be very useful for
operational troubleshooting. I think OSPF was less strict on the OSPF
router-id being a global IPv4 address, because OSPF won't ever be
visible globally, however setting the router-id to a global IPv4
address and making that address reachable i.e. an OAM loopback on the
router, is also very common and convenient.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 22 20:51:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1tqP-0006uR-6Q; Fri, 22 Jun 2007 20:51:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1tqO-0006uJ-G0
	for ipv6@ietf.org; Fri, 22 Jun 2007 20:51:16 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1tqN-0000Fa-7m
	for ipv6@ietf.org; Fri, 22 Jun 2007 20:51:16 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 62E061A4D86; Fri, 22 Jun 2007 17:50:10 -0700 (PDT)
Date: Fri, 22 Jun 2007 17:50:10 -0700
From: bill fumerola <billf@mu.org>
To: Jeroen Massar <jeroen@unfix.org>
Message-ID: <20070623005010.GI31273@elvis.mu.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <467C2EE6.3070100@spaghetti.zurich.ibm.com>
User-Agent: Mutt/1.4.2.2i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

[ limiting my comments to the discussion surrounding section 4.1 ]

IFF ULA-C space is to exist and be registered/delegated, delegate the
reverse blocks for that space as well. we so often beat the "addressing
isn't routing" drum weekly. well, DNS isn't routing. DNS+ULA-C is not
an end-run around PIv6. DNS is an integral part of addressing and if
we're going to move forward with ULA-C as delegated addressing then let
us move forward with addressing in its entirety.

if organizations use a ULA-C block in their network, they shouldn't have
to special case their DNS infrastructure such that every recursive server
in their network has to slave from / forward to some special location
to get accurate answers like they do now for RFC1918 and ULA-L.

if different organizations end up routing ULA-C blocks between autonomous
networks they will already have the benefit of accurate PTR answers
without lifting a finger. resolution of a PTR record doesn't inch ULA-C
addresses any further towards being PI space, just towards adding value.

-- bill


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 23 07:46:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I244L-00042i-Kz; Sat, 23 Jun 2007 07:46:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I244K-00042d-2r
	for ipv6@ietf.org; Sat, 23 Jun 2007 07:46:20 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I244H-0000HZ-Qk
	for ipv6@ietf.org; Sat, 23 Jun 2007 07:46:20 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id AAE6A140C1CC;
	Sat, 23 Jun 2007 13:46:14 +0200 (CEST)
Message-ID: <467D0806.7030100@spaghetti.zurich.ibm.com>
Date: Sat, 23 Jun 2007 12:46:14 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: bill fumerola <billf@mu.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
In-Reply-To: <20070623005010.GI31273@elvis.mu.org>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1955716203=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1955716203==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig407C709166AD318A0287DE13"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig407C709166AD318A0287DE13
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

bill fumerola wrote:
> [ limiting my comments to the discussion surrounding section 4.1 ]

You mean avoiding the questions that people ask to your 'arguments'? :)

My main question about ULA-C still stands: how is it different from PI?

What is the advantage that it gives to The Internet, especially in the
light that it will cause that everybody on the Internet will have to
make special provisions to block this out, provide registry services
etc. Which are all already in place for the PI blocks which do exactly
the same thing.

> IFF ULA-C space is to exist and be registered/delegated, delegate the
> reverse blocks for that space as well. we so often beat the "addressing=

> isn't routing" drum weekly. well, DNS isn't routing.

Without routing there is no DNS. And you are claiming to want to
disconnect the address space from the Internet. As such there is no DNS
that you can access in the first place. Or are you setting up a local
variant? If so why do you need the global one?

> DNS+ULA-C is not an end-run around PIv6.

Then what exactly is the purpose? Saying what it is not, doesn't make it
something.

> DNS is an integral part of addressing and if
> we're going to move forward with ULA-C as delegated addressing then let=

> us move forward with addressing in its entirety.

So you want a disconnected address space which gets connected to the
Internet? Sorry, but that more or less really implies NAT.

As you know DNS works in two ways: forward and reverse.
You will require forward DNS servers somewhere that have your zones with
local addresses anyway, why not add the reverse ones too?
Are you publishing your forward DNS servers also on the global Internet?
I mean, when you interconnect with another company, you surely want them
to actually get the ULA-C addresses and not the ones that everybody on
the Internet uses, would you not?

I am fairly sure that security people are really happy to hear that they
'for simplicity' have their local DNS servers and the addresses
published on the Internet and accessible from that same Internet, so
that people can nicely traverse the tree and figure out which hosts are
where and find out a lot of information that they are not supposed to be
able to get as they are supposed to be for a local network.

> if organizations use a ULA-C block in their network, they shouldn't hav=
e
> to special case their DNS infrastructure such that every recursive serv=
er
> in their network has to slave from / forward to some special location
> to get accurate answers like they do now for RFC1918 and ULA-L.

So your previous argument that "they are doing this for decades" was
false and, as I mentioned, they have actually been doing it for a long
time already using local resolvers and split-dns which works fine. It is
indeed not nice, but that is more over inherent to the simple fact that
they chose not to use The Internet in the first place.

The mere fact that you are stating that these companies will otherwise
require split DNS, simply implies that they are going to connect to the
Internet, then _why_ would you want to have those companies get an
address space that can never ever ever use that Internet. Maybe today
they don't want to use it on that Internet, but maybe next year they do.
It is really handy to be able to use SIP globally for instance.
Unless what is going to happen what will most likely going to happen: it
will become active on the Internet!?

If you don't want hosts to talk to "The Big Bad Internet": Firewall it
and as an added bonus to keep it out completely: Don't route it.

Having a DNS server sitting in both networks is not going to help there,
ever tried debugging such a setup? It is indeed a lot of fun and
consultants are very happy to be able to bill you for it.

> if different organizations end up routing ULA-C blocks between autonomo=
us
> networks they will already have the benefit of accurate PTR answers
> without lifting a finger.

They actually DO have to lift a finger: they have to configure Internet
connectivity on machines that are "officially" completely separated from
the Internet.

Lets take the example of The Pentagon* they would really enjoy a "Unique
*LOCAL* Address" Space, because then they can be completely independent
of the Internet. Now you are arguing that it would be a good thing that
they actually connect to that Internet to be able to get DNS!?

*=3Dhttp://it.slashdot.org/article.pl?sid=3D07/06/22/021239

See the article, it is funny, though not so funny how they got in.

> resolution of a PTR record doesn't inch ULA-C
> addresses any further towards being PI space, just towards adding value=
=2E

Which Value? I can also state that Coke is better than Pepsi, but why?

Also on the point where people say "but I can firewall fc00::/7 easily
and I know that only partner networks are there, while the rest is the
big evil internet", ever thought about the fact that everyone can
generate/pick a ULA address and simply use it? Which is the same as
routing global unicast addresses from a different company. You really
need to trust per prefix, not per fc00::/7 which is an awfully big
block. The security breach might not happen at your place, it just might
happen at a partner...

I am not even going into the simple fact that addresses never should be
trusted as they can still be spoofed way too easily. As such building
your 'firewall' on those assumptions is thus silly at best.

Greets,
 Jeroen


--------------enig407C709166AD318A0287DE13
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ9CAYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+FNAKCM/AyQHMOFKtJ6SHi/qEQhlEtg
FwCgirBnMVDHQ6P1RmfUwrHD20NURdg=
=Hn2+
-----END PGP SIGNATURE-----

--------------enig407C709166AD318A0287DE13--


--===============1955716203==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1955716203==--




From ipv6-bounces@ietf.org Sat Jun 23 20:01:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2FWP-0007TY-02; Sat, 23 Jun 2007 20:00:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2FWO-0007TS-AA
	for ipv6@ietf.org; Sat, 23 Jun 2007 20:00:04 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2FWN-0000e2-SX
	for ipv6@ietf.org; Sat, 23 Jun 2007 20:00:04 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id F039128452
	for <ipv6@ietf.org>; Sun, 24 Jun 2007 00:00:02 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 24 Jun 2007 00:00:02 +0000
Message-Id: <20070624000002.F039128452@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  3.94% |    5 | 16.87% |   152610 | shemant@cisco.com
 10.24% |   13 | 10.36% |    93729 | brian.e.carpenter@gmail.com
  7.87% |   10 |  9.76% |    88279 | jeroen@unfix.org
  9.45% |   12 |  7.68% |    69493 | sleibrand@internap.com
  5.51% |    7 |  4.43% |    40108 | mark_andrews@isc.org
  4.72% |    6 |  4.05% |    36657 | fred.l.templin@boeing.com
  4.72% |    6 |  3.40% |    30800 | michael.dillon@bt.com
  3.94% |    5 |  3.27% |    29557 | jhw@apple.com
  3.94% |    5 |  3.10% |    28042 | paul@vix.com
  3.94% |    5 |  3.07% |    27800 | narten@us.ibm.com
  3.15% |    4 |  3.44% |    31132 | ipng@69706e6720323030352d30312d31340a.nosense.org
  3.15% |    4 |  2.53% |    22903 | kkargel@polartel.com
  3.15% |    4 |  2.43% |    22018 | billf@mu.org
  3.15% |    4 |  2.14% |    19382 | leo.vegoda@icann.org
  2.36% |    3 |  2.24% |    20274 | internet-drafts@ietf.org
  2.36% |    3 |  2.14% |    19324 | lear@cisco.com
  2.36% |    3 |  2.09% |    18894 | fred@cisco.com
  2.36% |    3 |  1.44% |    13061 | george+ipng@m5p.com
  1.57% |    2 |  1.72% |    15566 | bmanning@isi.edu
  1.57% |    2 |  1.48% |    13351 | marla.azinger@frontiercorp.com
  1.57% |    2 |  1.29% |    11687 | brian@innovationslab.net
  1.57% |    2 |  1.26% |    11401 | vishwas.ietf@gmail.com
  1.57% |    2 |  1.24% |    11250 | perry@coders.net
  1.57% |    2 |  1.11% |    10032 | bob.hinden@nokia.com
  1.57% |    2 |  1.09% |     9837 | albert.e.manfredi@boeing.com
  1.57% |    2 |  1.01% |     9118 | pekkas@netcore.fi
  0.79% |    1 |  0.76% |     6876 | soohong.park@samsung.com
  0.79% |    1 |  0.68% |     6173 | gih@apnic.net
  0.79% |    1 |  0.61% |     5513 | sra+ipng@hactrn.net
  0.79% |    1 |  0.60% |     5391 | suresh.krishnan@ericsson.com
  0.79% |    1 |  0.59% |     5354 | jinmei@isl.rdc.toshiba.co.jp
  0.79% |    1 |  0.57% |     5129 | rdenis@simphalempin.com
  0.79% |    1 |  0.53% |     4797 | vladislav.yasevich@hp.com
  0.79% |    1 |  0.53% |     4760 | stephen@sprunk.org
  0.79% |    1 |  0.48% |     4362 | drc@virtualized.org
--------+------+--------+----------+------------------------
100.00% |  127 |100.00% |   904660 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 24 06:47:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2Pc6-00048Z-QW; Sun, 24 Jun 2007 06:46:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2Pc4-00048T-PW
	for ipv6@ietf.org; Sun, 24 Jun 2007 06:46:36 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2Pc3-0003D0-As
	for ipv6@ietf.org; Sun, 24 Jun 2007 06:46:36 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I2Pbz-000OM0-Vh
	for ipv6@ietf.org; Sun, 24 Jun 2007 20:16:32 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 8E1B72013F
	for <ipv6@ietf.org>; Sun, 24 Jun 2007 20:16:30 +0930 (CST)
Date: Sun, 24 Jun 2007 20:16:29 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: ipv6@ietf.org
Message-Id: <20070624201629.052ce678.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: Thoughts on a DHCPv6 option to enable CPE router processing of ICMP
 Redirects ?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

I've been thinking about how IPv6 might be deployed in a DSL network
with Ethernet rather than ATM backhaul. The IPv6 traffic rides directly
over Ethernet - the so-called "IPoE" DSL model - rather than being
encapsulated in PPPoE or PPPoA.

In this scenario, customers would be allocated a /48 (or longer)
prefixes for their network, sitting behind the DSL CPE operating as a
router, via DHCP Prefix Delegation.

At the local exchange/central office, the bridged-ethernet-over-DSL
traffic is aggregated from the DSLAMs using a layer 2 switch. This
layer 2 switch aggregated traffic is then backhauled, also via
ethernet, to a central aggregation point where the aggregation router
resides, which provides access to the rest of the IPv6 Internet.

Ideally, traffic between the prefixes goes between the CPE directly via
the layer 2 switch in the exchange/co, rather than via the upstream
aggregation router. However, as the CPE only has a default route to the
upstream aggregation router this isn't going to happen.

In the "convetional" routing scenario, the CPE router and the
aggregation router would be participating in a routing protocol, and
therefore the CPE would know about the prefixes residing behind the
other peer CPE. In this DSL scenario this isn't scalable or
manageble. 

I'm curious on what people's thoughts would be regarding having a DHCP
option that enables the CPE router process ICMP redirects for these
prefixes from the upstream aggregation router? This would encourage
most inter-cpe prefix traffic to stay local to the exchange/c.o.,
without having to run a fully blown routing protocol on each of them.
With increasing P2P style applications and therefore traffic, I think
there would be real benefits in permitting ICMP redirects be processed
by the CPE routers in this scenario.

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sun Jun 24 09:13:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2RtS-0002v3-A2; Sun, 24 Jun 2007 09:12:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2RtQ-0002u9-7X
	for ipv6@ietf.org; Sun, 24 Jun 2007 09:12:40 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2RtO-0008B4-GA
	for ipv6@ietf.org; Sun, 24 Jun 2007 09:12:40 -0400
Received: from 219-90-232-236.ip.adam.com.au ([219.90.232.236]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I2RtM-00031s-Vd
	for ipv6@ietf.org; Sun, 24 Jun 2007 22:42:37 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 4B52F2013F
	for <ipv6@ietf.org>; Sun, 24 Jun 2007 22:42:35 +0930 (CST)
Date: Sun, 24 Jun 2007 22:42:34 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Cc: ipv6@ietf.org
Message-Id: <20070624224234.3fdd854f.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <20070624201629.052ce678.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <20070624201629.052ce678.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.13; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: Re: Thoughts on a DHCPv6 option to enable CPE router processing of
 ICMP Redirects ?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hmm,

On Sun, 24 Jun 2007 20:16:29 +0930
Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org> wrote:

> Hi,
>

<snip>
 
> 
> I'm curious on what people's thoughts would be regarding having a DHCP
> option that enables the CPE router process ICMP redirects for these
> prefixes from the upstream aggregation router? This would encourage
> most inter-cpe prefix traffic to stay local to the exchange/c.o.,
> without having to run a fully blown routing protocol on each of them.
> With increasing P2P style applications and therefore traffic, I think
> there would be real benefits in permitting ICMP redirects be processed
> by the CPE routers in this scenario.
> 

Hmm, I've just realised that conventional ICMP redirect won't work in
this scenario, because the target address of the ICMP redirect couldn't
be the downstream CPE, as the upstream aggregation router wouldn't know
what the Link Local address of the CPE is from the packet that
triggered the redirect.

OTOH, maybe the IPv6 destination address of the ICMP redirect could be
the subnet router-anycast address, and use the link layer destination
address that was the link layer source address of the packet that
triggered the redirect.

Regards,
Mark.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 03:17:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2ioX-0007YC-8W; Mon, 25 Jun 2007 03:16:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2ioW-0007Xz-A8
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:44 -0400
Received: from nf-out-0910.google.com ([64.233.182.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2ioV-0007CF-0g
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:44 -0400
Received: by nf-out-0910.google.com with SMTP id c10so50938nfd
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 00:16:42 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=kHu5tZnOLHEsG8T5ZTsT8HnKLiQKp1KX2U6k8C5As8i7tEpZ5nDLxKwPQdltG8zNvfgNKZhCayqB1vtrqPNlNcXC3fUHDWgr2yTb5Tj8I/CWORMKteenoc0uDZQvpZ5DZD3W8MWsaIHn9GLMiXiVnSedoFlYOCDQi/IYu86VHok=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KIakbjRLfNE/HUCutDbrMQH/o7+Ff2eSjgfrE7+tSPCtKk/DkYcW5yhyYtCzImBtjizeqV30o81TLfxPpHRRMwAsd8aP2d01XMXeeLo3Vzwfj8yPeEI+RBb25ohbk+b0Q3ml6+XRvM7K5/QrBhrhKkpRyjoRUUEco/w1tJc2OP4=
Received: by 10.82.146.14 with SMTP id t14mr11954876bud.1182755802151;
	Mon, 25 Jun 2007 00:16:42 -0700 (PDT)
Received: from ?10.142.14.84? ( [193.247.250.1])
	by mx.google.com with ESMTP id g12sm241360nfb.2007.06.25.00.16.17
	(version=SSLv3 cipher=RC4-MD5); Mon, 25 Jun 2007 00:16:41 -0700 (PDT)
Message-ID: <467F62DA.2010802@gmail.com>
Date: Mon, 25 Jun 2007 08:38:18 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
In-Reply-To: <457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
 suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org





On 2007-06-22 18:25, Fred Baker wrote:
> On Jun 22, 2007, at 7:38 AM, Brian E Carpenter wrote:
>> What is out there as running code is history and words in RFCs will 
>> not change it.
> 
> I think his point is that a new IPv6 implementation has just been 
> released into the market and is not operating very well. Forget the 
> compliance language; what he's saying is that the various IPv6 
> implementations around don't run in his lab as well as advertised - the 
> running code doesn't run all that well - and he has some suggestions for 
> Vista Service Pack 1, MacOSX Leopard, Linux, etc.
> 
> How about we keep this on the technical content of what he has to say? 
> Do you believe, and do others believe, that the problems he describes 
> are real? 

Absolutely. I just don't think that delaying 2From ipv6-bounces@ietf.org Mon Jun 25 03:17:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2ioX-0007YC-8W; Mon, 25 Jun 2007 03:16:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2ioW-0007Xz-A8
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:44 -0400
Received: from nf-out-0910.google.com ([64.233.182.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2ioV-0007CF-0g
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:44 -0400
Received: by nf-out-0910.google.com with SMTP id c10so50938nfd
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 00:16:42 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=kHu5tZnOLHEsG8T5ZTsT8HnKLiQKp1KX2U6k8C5As8i7tEpZ5nDLxKwPQdltG8zNvfgNKZhCayqB1vtrqPNlNcXC3fUHDWgr2yTb5Tj8I/CWORMKteenoc0uDZQvpZ5DZD3W8MWsaIHn9GLMiXiVnSedoFlYOCDQi/IYu86VHok=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KIakbjRLfNE/HUCutDbrMQH/o7+Ff2eSjgfrE7+tSPCtKk/DkYcW5yhyYtCzImBtjizeqV30o81TLfxPpHRRMwAsd8aP2d01XMXeeLo3Vzwfj8yPeEI+RBb25ohbk+b0Q3ml6+XRvM7K5/QrBhrhKkpRyjoRUUEco/w1tJc2OP4=
Received: by 10.82.146.14 with SMTP id t14mr11954876bud.1182755802151;
	Mon, 25 Jun 2007 00:16:42 -0700 (PDT)
Received: from ?10.142.14.84? ( [193.247.250.1])
	by mx.google.com with ESMTP id g12sm241360nfb.2007.06.25.00.16.17
	(version=SSLv3 cipher=RC4-MD5); Mon, 25 Jun 2007 00:16:41 -0700 (PDT)
Message-ID: <467F62DA.2010802@gmail.com>
Date: Mon, 25 Jun 2007 08:38:18 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
In-Reply-To: <457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
 suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org





On 2007-06-22 18:25, Fred Baker wrote:
> On Jun 22, 2007, at 7:38 AM, Brian E Carpenter wrote:
>> What is out there as running code is history and words in RFCs will 
>> not change it.
> 
> I think his point is that a new IPv6 implementation has just been 
> released into the market and is not operating very well. Forget the 
> compliance language; what he's saying is that the various IPv6 
> implementations around don't run in his lab as well as advertised - the 
> running code doesn't run all that well - and he has some suggestions for 
> Vista Service Pack 1, MacOSX Leopard, Linux, etc.
> 
> How about we keep this on the technical content of what he has to say? 
> Do you believe, and do others believe, that the problems he describes 
> are real? 

Absolutely. I just don't think that delaying 2462bis has any value.

   Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 03:17:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2iol-0007af-1V; Mon, 25 Jun 2007 03:16:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2ioj-0007aV-LZ
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:57 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2ioi-0007Ew-9x
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:57 -0400
Received: by ug-out-1314.google.com with SMTP id k3so3207149ugf
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 00:16:55 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=S+xxhe2bB45p4mS9DD+UHIiEHW31ilHXACpsDIHX0N6ezCrj1/Aeaeu3qyNWyOevpdpQjWwP0hu79iImzlGAHBCoHAbCynjhMbpzQNq6lD0uxUioZqFV1iF2PhsEqYFn2oUsKHVApCHkkp4JouPwQYYhJpT8ggO5EpF0iw2U8BE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=oRjMHRTeM31roLopqtKJzyrjqYhKIIs5qciB+WW4EyhtlAxJltp//2E6krV2jxHDE7XW2vasAMVgvLikqcoSwcDAE5E1vQVc4MMVW7cft7VYGiqQ+RGw6PIfbAMHbCBOqzZLPbmECa3Wf7EwMYFRY4dyYOHkICjbDXyIWzMRI8Y=
Received: by 10.82.127.14 with SMTP id z14mr11920034buc.1182755815488;
	Mon, 25 Jun 2007 00:16:55 -0700 (PDT)
Received: from ?10.142.14.84? ( [193.247.250.1])
	by mx.google.com with ESMTP id 33sm1765967nfu.2007.06.25.00.16.47
	(version=SSLv3 cipher=RC4-MD5); Mon, 25 Jun 2007 00:16:54 -0700 (PDT)
Message-ID: <467F6798.3030805@gmail.com>
Date: Mon, 25 Jun 2007 08:58:32 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com><2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org><46785A65.7060505@internap.com><F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com><E72F5476-D072-44B6-A848-F206C15BBC22@icann.org><467ADA2F.6060100@internap.com><1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org><39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com><5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com><467B1407.90609@internap.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>	<318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> 
> So perhaps another question is whether462bis has any value.

   Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 03:17:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2iol-0007af-1V; Mon, 25 Jun 2007 03:16:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2ioj-0007aV-LZ
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:57 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2ioi-0007Ew-9x
	for ipv6@ietf.org; Mon, 25 Jun 2007 03:16:57 -0400
Received: by ug-out-1314.google.com with SMTP id k3so3207149ugf
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 00:16:55 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=S+xxhe2bB45p4mS9DD+UHIiEHW31ilHXACpsDIHX0N6ezCrj1/Aeaeu3qyNWyOevpdpQjWwP0hu79iImzlGAHBCoHAbCynjhMbpzQNq6lD0uxUioZqFV1iF2PhsEqYFn2oUsKHVApCHkkp4JouPwQYYhJpT8ggO5EpF0iw2U8BE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=oRjMHRTeM31roLopqtKJzyrjqYhKIIs5qciB+WW4EyhtlAxJltp//2E6krV2jxHDE7XW2vasAMVgvLikqcoSwcDAE5E1vQVc4MMVW7cft7VYGiqQ+RGw6PIfbAMHbCBOqzZLPbmECa3Wf7EwMYFRY4dyYOHkICjbDXyIWzMRI8Y=
Received: by 10.82.127.14 with SMTP id z14mr11920034buc.1182755815488;
	Mon, 25 Jun 2007 00:16:55 -0700 (PDT)
Received: from ?10.142.14.84? ( [193.247.250.1])
	by mx.google.com with ESMTP id 33sm1765967nfu.2007.06.25.00.16.47
	(version=SSLv3 cipher=RC4-MD5); Mon, 25 Jun 2007 00:16:54 -0700 (PDT)
Message-ID: <467F6798.3030805@gmail.com>
Date: Mon, 25 Jun 2007 08:58:32 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com><2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org><46785A65.7060505@internap.com><F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com><E72F5476-D072-44B6-A848-F206C15BBC22@icann.org><467ADA2F.6060100@internap.com><1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org><39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com><5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com><467B1407.90609@internap.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>	<318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> 
> So perhaps another question is whether it is too much to ask
> for more certainty (ULA-C) and less mystery (RFC4193 ULA)?

So, you reckon the chance of an administrative error in ULA-C
land giving two users the same prefix is less than the
2^-40 chance of a ULA clash between two users?

    Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



 it is too much to ask
> for more certainty (ULA-C) and less mystery (RFC4193 ULA)?

So, you reckon the chance of an administrative error in ULA-C
land giving two users the same prefix is less than the
2^-40 chance of a ULA clash between two users?

    Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 04:59:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2kPG-0005qm-5l; Mon, 25 Jun 2007 04:58:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2kPE-0005qb-Hd
	for ipv6@ietf.org; Mon, 25 Jun 2007 04:58:44 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2kPD-0001oF-Ry
	for ipv6@ietf.org; Mon, 25 Jun 2007 04:58:44 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 880E47301E;
	Mon, 25 Jun 2007 17:58:41 +0900 (JST)
Date: Mon, 25 Jun 2007 17:58:39 +0900
Message-ID: <m1bqf49zr4.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Fri, 22 Jun 2007 09:05:36 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Thanks for the quick review of section 5 in our new I-D.  Your reading
> of section 5 is correct - we have proposed both new and old
> implementations to always perform DAD for any unicast address. You are
> also correct that the gross change we have proposed over 2462bis is that
> old implementations MUST also not skip DAD. We stress about old
> implementations because if older implementations that are already
> deployed continue to be deployed for say, the next 5-10 years, that's
> not good. A software upgrade to older implementation is certainly
> possible.
> 
> We have given a solid reason for our case - it's presented in Section 2,
> bullet 4 of our I-D. Please see if our reasoning is solid enough to
> convince IETF.

I've also read that part (copied below to be very specific), but I
doubt it convinces the opponents of forcing DAD in all cases.  First,
it is not clear which "security problem" this bullet tries to
indicate.  Also, if Host1 is assumed to be the attacker that mounts
traffic hijacking and/or DoS against Host2, forcing Host2 to perform
DAD doesn't help because Host1 can get the same result by simply
ignoring the DAD-NS from Host1.

Meanwhile, 2462bis has just entered the AUTH48 state.  From what I've
seen so far, I don't see the need for delaying the publication of the
document due to this issue (and I'm going to complete this work just
with a few minor editorial fixes).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

   4.  The host MUST issue NS(DAD)s for all of its acquired unicast
       addresses except when the host interface has
       DupAddrDetectTransmits variable set to zero.  Section 5.4 of RFC
       2462 [ADDRCONF] erroneously relaxes this requirement and suffers
       from a security problem as illustrated by the following example:

          Host1 uses EUI-64 to configure a Link Local Address (LLA)
          using MAC1 and manually configures a Global Unicast Address
          (GUA) that is equal to an address configured using EUI-64 and
          MAC2.  Host1 completes an NS(DAD) for both its LLA and GUA.
          Then, Host2 uses EUI-64 to configure both a LLA and a GUA
          using MAC2.  Host2 completes an NS(DAD) for the LLA and does
          not send an NS(DAD) for its GUA in compliance with RFC 2462
          [ADDRCONF].  Now Host1 and Host2 have the same GUA on the same
          link.

       Therefore, this exception in section 5.4 of RFC 2462 [ADDRCONF]
       MUST be ignored.  Note that draft-ietf-ipv6-rfc2462bis-08
       [ADDRCONFbis] refers to an extensibility concern with new
       implementations and states in section 5.4:

          "Whereas this document does not invalidate such
          implementations, this kind of 'optimization' is NOT
          RECOMMENDED, and new implementations MUST NOT do that
          optimization."

       However, the security problem mentioned in this document
       invalidates even currently existing implementations.  The
       "Changes to draft-ietf-ipv6-rfc2462bis-08" section in this
       document describes the corresponding changes to
       draft-ietf-ipv6-rfc2462bis-08 [ADDRCONFbis].

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 05:05:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2kVj-000330-S0; Mon, 25 Jun 2007 05:05:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2kVh-0002tf-W6
	for ipv6@ietf.org; Mon, 25 Jun 2007 05:05:26 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2kVh-0005Nx-LF
	for ipv6@ietf.org; Mon, 25 Jun 2007 05:05:25 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 999327301E;
	Mon, 25 Jun 2007 18:05:24 +0900 (JST)
Date: Mon, 25 Jun 2007 18:05:22 +0900
Message-ID: <m1abuo9zfx.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Fri, 22 Jun 2007 09:25:13 -0700,
Fred Baker <fred@cisco.com> wrote:

> I think his point is that a new IPv6 implementation has just been  
> released into the market and is not operating very well. Forget the  
> compliance language; what he's saying is that the various IPv6  
> implementations around don't run in his lab as well as advertised -  
> the running code doesn't run all that well - and he has some  
> suggestions for Vista Service Pack 1, MacOSX Leopard, Linux, etc.

Is that true?  I've confirmed that both MacOSX(Tiger) and Linux
(Fedora Core 6, kernel 2.6.18) perform DAD on both link-local and
global addresses (generated from the same Mac address).  I also know
all BSD variants behave the same way.  I don't know about Vista, but
in my understand the vast majority of existing implementations
actually perform DAD without an exception.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 09:21:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2oU5-0007Fw-36; Mon, 25 Jun 2007 09:20:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2oU3-0007Fm-7S
	for ipv6@ietf.org; Mon, 25 Jun 2007 09:19:59 -0400
Received: from [2001:630:d0:f102:230:48ff:fe77:96e] (helo=owl.ecs.soton.ac.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2oTy-0002R4-OE
	for ipv6@ietf.org; Mon, 25 Jun 2007 09:19:59 -0400
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l5PDI0qU003938
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 14:18:00 +0100
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk
	[IPv6:2001:630:d0:f102:230:48ff:fe23:58df])
	by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l5PDHS6B022030
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 14:17:28 +0100
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.12.11.20060308/8.11.6) id l5PDHSCS026069
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:17:28 +0100
Date: Mon, 25 Jun 2007 14:17:27 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: ipv6@ietf.org
Message-ID: <20070625131727.GM16683@login.ecs.soton.ac.uk>
Mail-Followup-To: ipv6@ietf.org
References: <200706200041.l5K0fX50007611@drugs.dv.isc.org>
	<4678F9C0.3080600@cisco.com>
	<4678FD67.8010200@spaghetti.zurich.ibm.com>
	<46790105.1040803@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46790105.1040803@cisco.com>
User-Agent: Mutt/1.4i
X-Null-Tag: 497347a239973aaabc4bdb8e902c3f64
X-Null-Tag: 35413def7cf5d7dca8914fdcd231e5cd
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: Re: Why does everyone see router renumbnering as hard?	(was Re:
	draft-ietf-ipv6-ula-central-02.txt and NAT)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, Jun 20, 2007 at 12:27:17PM +0200, Eliot Lear wrote:
> 
> There are two that I can point you at, and perhaps the temporal 
> difference would be at least amusing:
> 
>    * Renumbering: Threat or Menace?, Lear, Katinsky, Tharp, et al,
>      Proceedings of the Tenth Systems Administration Conference (LISA96)
>    * Procedures for Renumbering an IPv6 Network Without a Flag Day,
>      Baker, Lear, Droms, RFC 4192, September, 2005.
> 
> I would also add that Tim Chown has done an extensive amount of work in 
> this space.

Well, it was the 6NET team, and some documentation can be found here:

http://www.6net.org/publications/deliverables/D3.6.1.pdf
http://www.6net.org/publications/deliverables/D3.6.2.pdf

and also

Chown, T., Thompson, M., Ford, A., and S. Venaas, "Things to
think about when Renumbering an IPv6 network 
(draft-chown-v6ops-renumber-thinkabout-05.txt)", March 2007.

but the feeling in v6ops certainly seems to be 'we don't want to renumber,
we'd rather have PI or look at id/loc longer term' so specific effort on
making renumbering easier isn't really being made (in that wg at least).

> If your point is that you should never have to renumber, then that's a 
> lovely way to go.  It will still happen, of course, as companies merge 
> and grow.  I think IPv6 helps with the latter, but the former is still a 
> challenge simply because topologies change.

IPv6 certainly helps, but doesn't trivialise it by any means.
 
-- 
Tim



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 10:17:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2pNI-0002Lc-To; Mon, 25 Jun 2007 10:17:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2pNH-0002LX-G6
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:17:03 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2pNG-0006Lu-6s
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:17:03 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5PEH0lQ011343
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 25 Jun 2007 07:17:01 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5PEH0pe008727; Mon, 25 Jun 2007 07:17:00 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5PEGqBT008426; Mon, 25 Jun 2007 07:17:00 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 07:16:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 07:16:59 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467D0806.7030100@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace1jE03m1IceOHmTp+3E4LI1Jp6HgBpkkZA
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>, "bill fumerola" <billf@mu.org>
X-OriginalArrivalTime: 25 Jun 2007 14:16:59.0862 (UTC)
	FILETIME=[7E9A8760:01C7B733]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen,

Touching on just one aspect of your thoughtul post:

> > DNS is an integral part of addressing and if
> > we're going to move forward with ULA-C as delegated=20
> addressing then let
> > us move forward with addressing in its entirety.
>=20
> So you want a disconnected address space which gets connected to the
> Internet? Sorry, but that more or less really implies NAT.

I wouldn't call it a "disconnected address space which gets
connected to the Internet" but rather a "unique local address
space which gets connected to other unique local address
spaces" and IMHO I don't see any implication for NAT there.

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 10:31:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2pah-0002gF-M4; Mon, 25 Jun 2007 10:30:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2pag-0002fs-9V
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:30:54 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2paf-0003BY-0N
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:30:54 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5PEUpRv020299
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 25 Jun 2007 07:30:51 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5PEUpRj027545; Mon, 25 Jun 2007 07:30:51 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5PEUfAf027145; Mon, 25 Jun 2007 07:30:50 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 07:30:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 07:30:49 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B8@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467F6798.3030805@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace2+NHb1J8w/yvgSJG1cfugCwGRBAAOr/Bg
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net><467853B0.5010806@internap.com><2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org><46785A65.7060505@internap.com><F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org><46796246.4050705@internap.com><E72F5476-D072-44B6-A848-F206C15BBC22@icann.org><467ADA2F.6060100@internap.com><1B2AAC04-E6AB-4AA7-8A78-95B9F94D20A2@icann.org><39C363776A4E8C4A94691D2BD9D1C9A1029ED8AF@XCH-NW-7V2.nw.nos.boeing.com><5AA220CA-A02D-46F1-B9BF-55F90A467A7D@apple.com><467B1407.90609@internap.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B1@XCH-NW-7V2.nw.nos.boeing.com>	<318169CD-49FC-4C41-8C27-3BD637EEEB12@apple.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B2@XCH-NW-7V2.nw.nos.boeing.com>
	<467F6798.3030805@gmail.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 25 Jun 2007 14:30:50.0477 (UTC)
	FILETIME=[6DB051D0:01C7B735]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
> Sent: Sunday, June 24, 2007 11:59 PM
> To: Templin, Fred L
> Cc: james woodyatt; IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
>=20
> >=20
> > So perhaps another question is whether it is too much to ask
> > for more certainty (ULA-C) and less mystery (RFC4193 ULA)?
>=20
> So, you reckon the chance of an administrative error in ULA-C
> land giving two users the same prefix is less than the
> 2^-40 chance of a ULA clash between two users?

Maybe; maybe not. But, with ULA-C, there is a (trusted?) entity
that is accountable for assuring uniqueness and someone to turn
to in the event of ties. There is also the concept of having
sites self-generate the ULA-Cs and "register" them with a 3rd
party entity, which puts the control in the end user's hands
while still having an accountable 3rd party.

BTW, this business of birthday paradox clashes has been beaten
on wrt to other random address assignment paradigms too; in
particular, CGAs. There, you have ~60 (?) bits for uniqueness
but it has still been implied that any non-zero probability
of collision is too great.

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 10:45:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2ppA-0008Nn-Ee; Mon, 25 Jun 2007 10:45:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2pp8-0008Nd-5L
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:45:50 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2pp5-0000PW-Pq
	for ipv6@ietf.org; Mon, 25 Jun 2007 10:45:50 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 25 Jun 2007 10:45:47 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAL5xf0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,460,1175486400"; 
	d="scan'208"; a="63598358:sNHT40815432"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5PEjl7J026995; 
	Mon, 25 Jun 2007 10:45:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5PEjLLx005892; 
	Mon, 25 Jun 2007 14:45:45 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 10:45:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 10:45:35 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <467F62DA.2010802@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace2+MmTzwOVyNEaQraOtwa9mG7YAwAORWJA
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
From: "Hemant Singh \(shemant\)" <shemant@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
X-OriginalArrivalTime: 25 Jun 2007 14:45:36.0495 (UTC)
	FILETIME=[7DCBEFF0:01C7B737]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3188; t=1182782747;
	x=1183646747; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Brian=20E=20Carpenter=22=20<brian.e.carpenter@gmail.com>,
	=0A=20
	=20=20=20=20=20=20=20=22Fred=20Baker=20\(fred\)=22=20<fred@cisco.com>; 
	bh=Lp6O8a/mMb6E435ee1ANwm/Li1w1mp0pFr3aztcGbJA=;
	b=FkFRHxY015ZjmXHwA6bymE/Tr7Lj6ioIc5m77MAScM+VQ1Jk03Tdy2k03x1fVA0jFlHZTAhq
	eb8VsC/Dq/Sv3YAxq0xm6fiOD3Q1SRpihziU5pxl0dt9EVdbTxO1vMCj;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.1 (+)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Let us summarize the discussion that has taken place so far and issues
closed.

1. Technical content - Brian has agreed below that the problem we
describe is real and we are saying our recommendation to change 2462bis
I-D does fix this problem. Tatuya still has some issues with our
problem, but we think till he fixes some typos in his email we cannot
reply to him. This is what was sent from Tatuya that we think is text
with typos:

"First, it is not clear which "security problem" this bullet tries to
indicate.  Also, if Host1 is assumed to be the attacker that mounts
traffic hijacking and/or DoS against Host2, forcing Host2 to perform DAD
doesn't help because Host1 can get the same result by simply ignoring
the DAD-NS from Host1."

Tatuya also needs to explain how ignoring DAD from a host is a valid
implementation of the 2462 standards.  Our scenario is perfectly legal
within the specification.  Also, note that Host1 sends out the
unchallenged DAD, so routers will assume everything is OK and send their
traffic to Host1 and not Host2.

2. Delay of 2462bis I-D - we'll work with you to close issues ASAP.=20

To also reply to another email where Tatuya said:

"I've confirmed that both MacOSX(Tiger) and Linux (Fedora Core 6, kernel
2.6.18) perform DAD on both link-local and global addresses (generated
from the same Mac address).  I also know all BSD variants behave the
same way.  I don't know about Vista, but in my understand the vast
majority of existing implementations actually perform DAD without an
exception."

Well, if stacks do not skip DAD, then there should be no problem with
tightening up the language as we've proposed.=20

Further, these hosts are not the only implementations out there. What
about IPv6 cable modem bridges or DSL IPv6 bridges which implement an
IPv6 host? These modems are deployed in a Service Provider deployment
that is very strict on compliance with standards.=20

- Hemant and Wes

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
Sent: Monday, June 25, 2007 2:38 AM
To: Fred Baker (fred)
Cc: Hemant Singh (shemant); ipv6@ietf.org; JINMEI Tatuya / ????
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08





On 2007-06-22 18:25, Fred Baker wrote:
> On Jun 22, 2007, at 7:38 AM, Brian E Carpenter wrote:
>> What is out there as running code is history and words in RFCs will=20
>> not change it.
>=20
> I think his point is that a new IPv6 implementation has just been=20
> released into the market and is not operating very well. Forget the=20
> compliance language; what he's saying is that the various IPv6=20
> implementations around don't run in his lab as well as advertised -=20
> the running code doesn't run all that well - and he has some=20
> suggestions for Vista Service Pack 1, MacOSX Leopard, Linux, etc.
>=20
> How about we keep this on the technical content of what he has to say?

> Do you believe, and do others believe, that the problems he describes=20
> are real?

Absolutely. I just don't think that delaying 2462bis has any value.

   Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 11:27:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2qSi-0002eU-En; Mon, 25 Jun 2007 11:26:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qSh-0002bG-47
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:26:43 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2qSg-0006kB-Ah
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:26:43 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id E183F140C1C3;
	Mon, 25 Jun 2007 17:26:37 +0200 (CEST)
Message-ID: <467FDEAA.1020503@spaghetti.zurich.ibm.com>
Date: Mon, 25 Jun 2007 16:26:34 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0375020143=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0375020143==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA4239CC2518F4B232378ACE5"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA4239CC2518F4B232378ACE5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Templin, Fred L wrote:
> Jeroen,
>=20
> Touching on just one aspect of your thoughtul post:
>=20
>>> DNS is an integral part of addressing and if
>>> we're going to move forward with ULA-C as delegated=20
>> addressing then let
>>> us move forward with addressing in its entirety.
>> So you want a disconnected address space which gets connected to the
>> Internet? Sorry, but that more or less really implies NAT.
>=20
> I wouldn't call it a "disconnected address space which gets
> connected to the Internet" but rather a "unique local address
> space which gets connected to other unique local address
> spaces" and IMHO I don't see any implication for NAT there.

If you are only connecting to another ULA network, then why would one
ever need NS entries in ip6.arpa for this space?

The whole story is about having NS entries in the ip6.arpa tree for the
delegation. When you have a delegation in the Internet ip6.arpa tree,
you also need to query them one way or the other and thus you are
connecting your ULA-based network to that Internet.

Also, people will the notice that they can use reverses from the
Internet, at one point or another will also want to use SIP or various
other protocols and thus end up using the Internet, and there are two
ways to do that: NAT it or simply announce the ULA prefix, renumbering
to a PI block is of course not an option here.

As such, what is the 'local' part again, how local is it really? And how
is ULA-C then different from PI? Why bother people with this ULA-C thing
when they really need PI in the first place? Which they can already get
for $100/year from ARIN and which will be guaranteed unique, just like
all other address space from the RIR's.

Greets,
 Jeroen



--------------enigA4239CC2518F4B232378ACE5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ/3q4uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+i9AJwLWj1LkB4GArEMWLj9WI+6jf8V
rgCgpOKskF+TzmhR+6NMycHte3Cq6os=
=V6C5
-----END PGP SIGNATURE-----

--------------enigA4239CC2518F4B232378ACE5--


--===============0375020143==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0375020143==--




From ipv6-bounces@ietf.org Mon Jun 25 11:28:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2qUU-0004T0-7c; Mon, 25 Jun 2007 11:28:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qUS-0004Sq-09
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:28:32 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2qUQ-0007RU-A5
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:28:31 -0400
Received: from mymb.local (t050096.ppp.asahi-net.or.jp [203.189.50.96])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4193A7301E;
	Tue, 26 Jun 2007 00:28:29 +0900 (JST)
Date: Tue, 26 Jun 2007 00:28:25 +0900
Message-ID: <m2645chx46.wl%jinmei@wide.ad.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Mon, 25 Jun 2007 10:45:35 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Let us summarize the discussion that has taken place so far and issues
> closed.
> 
> 1. Technical content - Brian has agreed below that the problem we
> describe is real and we are saying our recommendation to change 2462bis
> I-D does fix this problem. Tatuya still has some issues with our
> problem, but we think till he fixes some typos in his email we cannot
> reply to him. This is what was sent from Tatuya that we think is text
> with typos:
> 
> "First, it is not clear which "security problem" this bullet tries to
> indicate.  Also, if Host1 is assumed to be the attacker that mounts
> traffic hijacking and/or DoS against Host2, forcing Host2 to perform DAD
> doesn't help because Host1 can get the same result by simply ignoring
> the DAD-NS from Host1."

Yeah, there was a typo.  It should actually be:

First, it is not clear which "security problem" this bullet tries to
indicate.  Also, if Host1 is assumed to be the attacker that mounts
traffic hijacking and/or DoS against Host2, forcing Host2 to perform DAD
doesn't help because Host1 can get the same result by simply ignoring
the DAD-NS from Host2.
(i.e., replace the final "Host1" with "Host2")

> Tatuya also needs to explain how ignoring DAD from a host is a valid
> implementation of the 2462 standards.

Why should I?  I interpreted the bullet as describing Host1 was an
attacker, so it would do anything (whether it's valid or not wrt
standards) to make the attack succeed.

In any event, the main point is that it's not clear (to me) which
"security problem" this draft tries to explain (and how the change in
the specification helps solve or mitigate the "problem").

> Well, if stacks do not skip DAD, then there should be no problem with
> tightening up the language as we've proposed. 

I'd rather say that *if* stacks do not skip DAD, then there should be
no problem with leaving the current text as is (remember new
implementations won't skip DAD, so leaving the text won't cause a
problem in the future either).  And if so, I'd rather keep it since I
don't see any value in modifying text that has been fully reviewed and
does not actually have any problem.

But I in fact didn't mean all stacks don't skip DAD.  I simply
interpreted the following part

> > what he's saying is that the various IPv6 
> > implementations around don't run in his lab as well as advertised - 
> > the running code doesn't run all that well - and he has some 
> > suggestions for Vista Service Pack 1, MacOSX Leopard, Linux, etc.

as indicating MacOSX or Linux do skip DAD and tried to point out it's
not true.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 11:46:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2qll-0007yG-8r; Mon, 25 Jun 2007 11:46:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qlj-0007y5-Pk
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:46:23 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2qlf-0005xt-4o
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:46:23 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5PFkIbY001097
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 25 Jun 2007 10:46:18 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5PFkHS2026002; Mon, 25 Jun 2007 10:46:17 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5PFk8Vf025478; Mon, 25 Jun 2007 10:46:11 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 08:46:06 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 08:46:05 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467FDEAA.1020503@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace3PT1jqRmeuMoxTFCjzVVvvir4BQAAFk4A
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>
X-OriginalArrivalTime: 25 Jun 2007 15:46:06.0639 (UTC)
	FILETIME=[F187F3F0:01C7B73F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]=20
> Sent: Monday, June 25, 2007 8:27 AM
> To: Templin, Fred L
> Cc: bill fumerola; ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> Templin, Fred L wrote:
> > Jeroen,
> >=20
> > Touching on just one aspect of your thoughtul post:
> >=20
> >>> DNS is an integral part of addressing and if
> >>> we're going to move forward with ULA-C as delegated=20
> >> addressing then let
> >>> us move forward with addressing in its entirety.
> >> So you want a disconnected address space which gets=20
> connected to the
> >> Internet? Sorry, but that more or less really implies NAT.
> >=20
> > I wouldn't call it a "disconnected address space which gets
> > connected to the Internet" but rather a "unique local address
> > space which gets connected to other unique local address
> > spaces" and IMHO I don't see any implication for NAT there.
>=20
> If you are only connecting to another ULA network, then why would one
> ever need NS entries in ip6.arpa for this space?

To aid in connecting to another ULA network.
=20
> The whole story is about having NS entries in the ip6.arpa=20
> tree for the
> delegation. When you have a delegation in the Internet ip6.arpa tree,
> you also need to query them one way or the other and thus you are
> connecting your ULA-based network to that Internet.

Connecting to the IPv4 Internet in order to query the
ip6.arpa tree should work fine; right?
=20
> Also, people will the notice that they can use reverses from the
> Internet, at one point or another will also want to use SIP or various
> other protocols and thus end up using the Internet, and there are two
> ways to do that: NAT it or simply announce the ULA prefix, renumbering
> to a PI block is of course not an option here.

I don't see how that follows, and I do not want IPv6 NAT.

> As such, what is the 'local' part again, how local is it=20
> really? And how
> is ULA-C then different from PI? Why bother people with this=20
> ULA-C thing
> when they really need PI in the first place? Which they can=20
> already get
> for $100/year from ARIN and which will be guaranteed unique, just like
> all other address space from the RIR's.

IMHO, a "site" can be as large as a major corporation's private
Intranet or as small as my laptop, and I don't want to have to
pay $100/yr just to connect my laptop to other sites.=20
=20
Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 11:56:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2qvD-0004eD-Dt; Mon, 25 Jun 2007 11:56:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qvB-0004dH-PQ
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:56:09 -0400
Received: from 69-30-97-91.dv1mn.easystreet.com ([69.30.97.91]
	helo=reprise.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I2qvA-0001bT-DC
	for ipv6@ietf.org; Mon, 25 Jun 2007 11:56:09 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l5PFu6SB057413
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 08:56:06 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l5PFu6Qa057410;
	Mon, 25 Jun 2007 08:56:06 -0700 (PDT) (envelope-from george)
Date: Mon, 25 Jun 2007 08:56:06 -0700 (PDT)
Message-Id: <200706251556.l5PFu6Qa057410@mail.reprise.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00
X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> BTW, this business of birthday paradox clashes has been beaten
> on wrt to other random address assignment paradigms too; in
> particular, CGAs. There, you have ~60 (?) bits for uniqueness
> but it has still been implied that any non-zero probability
> of collision is too great.
>
> Fred
> fred.l.templin@boeing.com

In practical terms, zero probability is not to be found in this
universe.  People who demand zero probability for anything need
to be educated.  2^-40 probability is as close as you're going
to get.  Really!                              -- George Mitchell


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 12:00:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2qzQ-0001Rl-JP; Mon, 25 Jun 2007 12:00:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2qzD-0001AL-CD
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:00:19 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2qzC-0003J9-CR
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:00:19 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id CEA26140C2B6;
	Mon, 25 Jun 2007 18:00:16 +0200 (CEST)
Message-ID: <467FE693.5060103@spaghetti.zurich.ibm.com>
Date: Mon, 25 Jun 2007 17:00:19 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0934411303=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0934411303==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig67A09C23CC07E121A92994FE"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig67A09C23CC07E121A92994FE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Templin, Fred L wrote:
[..]
>> If you are only connecting to another ULA network, then why would one
>> ever need NS entries in ip6.arpa for this space?
>=20
> To aid in connecting to another ULA network.

So you are able to setup routing between those two sites, but feeding
them with NS entries for your reverse is too hard? IMHO the latter is
actually much easier, just find the DNS servers for the site, presto.

>> The whole story is about having NS entries in the ip6.arpa=20
>> tree for the
>> delegation. When you have a delegation in the Internet ip6.arpa tree,
>> you also need to query them one way or the other and thus you are
>> connecting your ULA-based network to that Internet.
>=20
> Connecting to the IPv4 Internet in order to query the
> ip6.arpa tree should work fine; right?

Thus you are connecting to the Internet, using IPv4 or IPv6 doesn't
matter, you have a dependency on the Internet. As such you are not
working dis-connected from the Internet and you have a dependency on it.
I was under the impression, clearly wrongly, that people wanted ULA so
they where completely independent of the Internet with no ties there
whatsoever.

>> Also, people will the notice that they can use reverses from the
>> Internet, at one point or another will also want to use SIP or various=

>> other protocols and thus end up using the Internet, and there are two
>> ways to do that: NAT it or simply announce the ULA prefix, renumbering=

>> to a PI block is of course not an option here.
>=20
> I don't see how that follows, and I do not want IPv6 NAT.

There are a lot of networks that only where "local" and used RFC1918
because of this, then at a certain point "oeh we merge", and they had to
connect to another network (which then clashed and also caused NAT and
other weird things but that is another point). That 'other' network
sometimes was the Internet, as "oeh it is handy that we can access
google/wikipedia/etc" and instead of renumbering, lets NAT, as that is
easy quick and 'cheap', they forget though how much pain it is in the
long run.

>> As such, what is the 'local' part again, how local is it really?
>> And how is ULA-C then different from PI? Why bother people with
>> this ULA-C thing when they really need PI in the first place?
>> Which they can already get for $100/year from ARIN and which will
>> be guaranteed unique, just like all other address space from the RIR's=
=2E
>=20
> IMHO, a "site" can be as large as a major corporation's private
> Intranet or as small as my laptop, and I don't want to have to
> pay $100/yr just to connect my laptop to other sites.=20

A site is a network of computers with a single administration, this can
mean indeed a major corporation (who maybe even require multiple /48's
which is why rfc4193 is a bit off to cover those cases)

If you want to have a /48 for your laptop, simply use ULA (RFC4193)
those are free. Or are you simply wanting to have your own IP addresses,
setting up firewalling etc because you have a laptop (or Winnebago
filled with servers) and carrying it around globally through various
buildings and making other networks accept your /48 AND force them to
connect to the Internet to be able to resolve your reverse?

Most likely anyway when you connect your laptop to another site they
will be providing you with an IP address anyway from their site prefix.

Can you clarify the use case you are sketching here a lot more as I
really want to know what actual use case is actually useful that ULA-C
solves, what PI doesn't solve (Drawings + text help). Especially now
that the folks who 'want/need' ULA-C do want to have reverse DNS
available from the Internet, while they want to be local in the first pla=
ce.

All those cases can be covered perfectly fine by PI. Or is it just that
folks see ULA-C as 'very cheap PI space'?

Greets,
 Jeroen


--------------enig67A09C23CC07E121A92994FE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ/5pMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I3SPAJ9TLFTZZVgap3EXGWplyPceWvPy
GQCglAwkpE1A/BiVINS9/4cg2w4oBmA=
=inqJ
-----END PGP SIGNATURE-----

--------------enig67A09C23CC07E121A92994FE--


--===============0934411303==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0934411303==--




From ipv6-bounces@ietf.org Mon Jun 25 12:34:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2rVr-0004P5-9p; Mon, 25 Jun 2007 12:34:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2rVq-0004Ow-0I
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:34:02 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2rVo-0007c3-FZ
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:34:01 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5PGXx6J003336
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 25 Jun 2007 09:33:59 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5PGXwFv015920; Mon, 25 Jun 2007 11:33:58 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5PGXrDh015703; Mon, 25 Jun 2007 11:33:57 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 09:33:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7B746.9FA18244"
Date: Mon, 25 Jun 2007 09:33:55 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467FE693.5060103@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace3Qe78ldHsK/q6Qf6WBfzu96gEagAAFPRw
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>
X-OriginalArrivalTime: 25 Jun 2007 16:33:56.0369 (UTC)
	FILETIME=[A0060010:01C7B746]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B746.9FA18244
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jeroen,=20

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]=20
> Sent: Monday, June 25, 2007 9:00 AM
> To: Templin, Fred L
> Cc: bill fumerola; ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> Templin, Fred L wrote:
> [..]
> >> If you are only connecting to another ULA network, then=20
> why would one
> >> ever need NS entries in ip6.arpa for this space?
> >=20
> > To aid in connecting to another ULA network.
>=20
> So you are able to setup routing between those two sites, but feeding
> them with NS entries for your reverse is too hard? IMHO the latter is
> actually much easier, just find the DNS servers for the site, presto.

I didn't quite understand this, but I am not a DNS expert.

> >> The whole story is about having NS entries in the ip6.arpa=20
> >> tree for the
> >> delegation. When you have a delegation in the Internet=20
> ip6.arpa tree,
> >> you also need to query them one way or the other and thus you are
> >> connecting your ULA-based network to that Internet.
> >=20
> > Connecting to the IPv4 Internet in order to query the
> > ip6.arpa tree should work fine; right?
>=20
> Thus you are connecting to the Internet, using IPv4 or IPv6 doesn't
> matter, you have a dependency on the Internet. As such you are not
> working dis-connected from the Internet and you have a=20
> dependency on it.

Only when you want to connect to another site.

> I was under the impression, clearly wrongly, that people wanted ULA so
> they where completely independent of the Internet with no ties there
> whatsoever.

I can't speak for the use cases other people might have
in mind.
=20
> >> Also, people will the notice that they can use reverses from the
> >> Internet, at one point or another will also want to use=20
> SIP or various
> >> other protocols and thus end up using the Internet, and=20
> there are two
> >> ways to do that: NAT it or simply announce the ULA prefix,=20
> renumbering
> >> to a PI block is of course not an option here.
> >=20
> > I don't see how that follows, and I do not want IPv6 NAT.
>=20
> There are a lot of networks that only where "local" and used RFC1918
> because of this, then at a certain point "oeh we merge", and=20
> they had to
> connect to another network (which then clashed and also caused NAT and
> other weird things but that is another point). That 'other' network
> sometimes was the Internet, as "oeh it is handy that we can access
> google/wikipedia/etc" and instead of renumbering, lets NAT, as that is
> easy quick and 'cheap', they forget though how much pain it is in the
> long run.

Again, *no* NAT'ing of IPv6.
=20
> >> As such, what is the 'local' part again, how local is it really?
> >> And how is ULA-C then different from PI? Why bother people with
> >> this ULA-C thing when they really need PI in the first place?
> >> Which they can already get for $100/year from ARIN and which will
> >> be guaranteed unique, just like all other address space=20
> from the RIR's.
> >=20
> > IMHO, a "site" can be as large as a major corporation's private
> > Intranet or as small as my laptop, and I don't want to have to
> > pay $100/yr just to connect my laptop to other sites.=20
>=20
> A site is a network of computers with a single=20
> administration,

A laptop fits this description. Think of one running some
of this new virtualization support whereby there may be
many virtual machines connected up by virtual networks
running within the laptop. (Actually, folks like IBM were
doing this "new" virtualization on their mainframes back
in the 70's...)=20

> this can
> mean indeed a major corporation (who maybe even require multiple /48's
> which is why rfc4193 is a bit off to cover those cases)
>=20
> If you want to have a /48 for your laptop, simply use ULA (RFC4193)
> those are free.

RFC4193 ULA is good, but could be better. However remote the
possibility of collisions, IMHO there would still be value in
having a 3rd-party mechanism to avoid duplicate assignments
and/or de-conflict duplicates.  =20

> Or are you simply wanting to have your own IP=20
> addresses,
> setting up firewalling etc because you have a laptop (or Winnebago
> filled with servers) and carrying it around globally through various
> buildings and making other networks accept your /48 AND force them to
> connect to the Internet to be able to resolve your reverse?

I don't quite understand this, but I want to be able to
drop my laptop down in whatever visited network and have
it connect to other sites w/o having to manually configure
explicit VPNs.=20
=20
> Most likely anyway when you connect your laptop to another site they
> will be providing you with an IP address anyway from their=20
> site prefix.

One use I could see for that is if you needed a care-of
address such as used for MIPv6. But, that gets off onto
a completely different line of discussion.
=20
> Can you clarify the use case you are sketching here a lot more as I
> really want to know what actual use case is actually useful that ULA-C
> solves, what PI doesn't solve (Drawings + text help). Especially now
> that the folks who 'want/need' ULA-C do want to have reverse DNS
> available from the Internet, while they want to be local in=20
> the first place.

I already gave my use-case in:

http://www1.ietf.org/mail-archive/web/ipv6/current/msg07806.html

a drawing is also attached (see below).
=20
> All those cases can be covered perfectly fine by PI. Or is it=20
> just that
> folks see ULA-C as 'very cheap PI space'?

Again, I don't know about other folks but for me I see the
price as too high for some "sites" to have to pay.

Fred
fred.l.templin@boeing.com

------_=_NextPart_001_01C7B746.9FA18244
Content-Type: text/plain;
	name="manet_router.txt"
Content-Transfer-Encoding: base64
Content-Description: manet_router.txt
Content-Disposition: attachment;
	filename="manet_router.txt"

DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICBFZ3Jlc3MgSW50ZXJmYWNlcw0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICBeICAgXiAgICAgICAgXg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8ICAgfCAgICAgICAgfA0KICAgICAgICstLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0rLS0tKy0tLS0tLS0tKy0tLS0tLS0tLS0rDQogICAgICAgfCAgICAgICAgICAgICAg
ICAgICAgICAgIHwgICB8ICAgICAgICB8ICAgICAgICAgIHwgICAgTQ0KICAgICAgIHwgICAgICAg
LC0uICAgIHwgICAgICAgICB8ICAgfCAgLi4uLiAgfCAgICAgICAgICB8ICAgIEENCiAgICAgICB8
ICAgICAgKEgxICktLS0rICAgICArLS0tKy0tLSstLS0tLS0tLSstLS0rICAgICAgfCAgICBODQog
ICAgICAgfCAgICAgICBgLScgICAgfCAgICAgfCAgICAgICAgICAgICAgICAgICAgfCAgICAgIHwg
ICAgRQ0KICAgICAgIHwgICB8ICAgICAgICAgICstLS0tLSsgICAgICAgICAgICAgICAgICAgICst
LS0tLS0rLS08IFQNCiAgICAgICB8IC4gfCAgKy0tLSsgICB8ICAgICB8ICAgICAgICAgICAgICAg
ICAgICB8ICAgICAgfA0KICAgICAgIHwgLiArLS18UjEgfC0tLSsgICAgIHwgICAgICAgICAgICAg
ICAgICAgIHwgICAgICB8ICAgIEkNCiAgICAgICB8IC4gfCAgKy0tLSsgICB8ICAgICB8ICAgICAg
IFJvdXRlciAgICAgICArLS0tLS0tKy0tPCBuDQogICAgICAgfCAgIHwgICAsLS4gICAgICAgICAg
fCAgICAgICAgICAgICAgICAgICAgfCAgLiAgIHwgICAgdA0KICAgICAgIHwgICAgICAoSDIgKS0t
LS0tLS0tLSsgICAgICAgRW50aXR5ICAgICAgIHwgIC4gICB8ICAgIGUNCiAgICAgICB8ICAgICAg
IGAtJyAgICAgICAuICB8ICAgICAgICAgICAgICAgICAgICB8ICAuICAgfCAgICByDQogICAgICAg
fCAgICAgICAgICAgICAgICAgLiAgfCAgICAgICAgICAgICAgICAgICAgfCAgLiAgIHwgICAgZg0K
ICAgICAgIHwgICAgICAgLC0uICAgICAgIC4gIHwgICAgICAgICAgICAgICAgICAgICstLS0tLS0r
LS08IGENCiAgICAgICB8ICAgICAgKEhuICktLS0tLS0tLS0rICAgICAgICAgICAgICAgICAgICB8
ICAgICAgfCAgICBjDQogICAgICAgfCAgICAgICBgLScgICAgICAgICAgKy0tLSstLS0rLS0tLS0t
LS0rLS0tKyAgICAgIHwgICAgZQ0KICAgICAgIHwgICBJbnRlcm5hbCBJbmdyZXNzICAgICB8ICAg
fCAgLi4uLiAgfCAgICAgICAgICB8ICAgIHMNCiAgICAgICB8ICAgSW50ZXJmYWNlcy9OZXR3b3Jr
cyAgfCAgIHwgICAgICAgIHwgICAgICAgICAgfA0KICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rLS0tKy0tLS0tLS0tKy0tLS0tLS0tLS0rDQogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIHwgICB8ICAgICAgICB8DQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHYg
ICB2ICAgICAgICB2DQogICAgICAgICAgICAgICAgICAgICAgICAgIEV4dGVybmFsIEluZ3Jlc3Mg
SW50ZXJmYWNlcw0KDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSAxOiBNQU5F
VCBSb3V0ZXINCg==

------_=_NextPart_001_01C7B746.9FA18244
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

------_=_NextPart_001_01C7B746.9FA18244--




From ipv6-bounces@ietf.org Mon Jun 25 12:38:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2rZx-00077r-Rq; Mon, 25 Jun 2007 12:38:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2rZw-00073m-De
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:38:16 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2rZu-00088L-3b
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:38:16 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 25 Jun 2007 11:38:12 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A063141066707090@mail>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace1jE03m1IceOHmTp+3E4LI1Jp6HgBpkkZAAATC0kA=
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

But can't you do that perfectly well with PI or PA, firewall it as
appropriate and use regular DNS? =20

Even if two "unique local address spaces" were carved out of PI or PA,
restricted from public access, and allowed to intercommunicate as a sort
of unauthenticated unencrypted private network using public DNS it still
seems that either PI or PA would suit the need very functionally.  =20

If it's all about renumbering avoidance, and we made an acronymn for
"Provider Independent" space I suspect we might refer to it as PI.

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> Sent: Monday, June 25, 2007 9:17 AM
> To: Jeroen Massar; bill fumerola
> Cc: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-ula-central-02.txt
>=20
> Jeroen,
>=20
> Touching on just one aspect of your thoughtul post:
>=20
> > > DNS is an integral part of addressing and if we're going to move=20
> > > forward with ULA-C as delegated
> > addressing then let
> > > us move forward with addressing in its entirety.
> >=20
> > So you want a disconnected address space which gets=20
> connected to the=20
> > Internet? Sorry, but that more or less really implies NAT.
>=20
> I wouldn't call it a "disconnected address space which gets=20
> connected to the Internet" but rather a "unique local address=20
> space which gets connected to other unique local address=20
> spaces" and IMHO I don't see any implication for NAT there.
>=20
> Fred
> fred.l.templin@boeing.com
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 12:56:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2rrO-00056z-Nq; Mon, 25 Jun 2007 12:56:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2rrN-00056s-M6
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:56:17 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2rrK-0004fe-7T
	for ipv6@ietf.org; Mon, 25 Jun 2007 12:56:17 -0400
Received: from yxu1b30.hopcount.ca ([199.212.90.30])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.67 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1I2rtp-0002Y7-RM
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:58:52 +0000
Mime-Version: 1.0 (Apple Message framework v752.3)
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Message-Id: <3CC9E5E1-0095-4273-BF9E-FA0273F5B86C@ca.afilias.info>
Content-Type: multipart/mixed; boundary=Apple-Mail-3-472421224
From: Joe Abley <jabley@ca.afilias.info>
Date: Mon, 25 Jun 2007 12:56:07 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8d5cbd3d5548af56dbea64a1d182f942
Subject: draft-ietf-ipv6-deprecate-01-01-candidate-02
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


--Apple-Mail-3-472421224
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hi all,

Apologies for the delay on this update; real life has been intruding  
with great regularity.

The change-log reads:

    01-candidate-02  Moved description of traffic amplification to
       Section 1, and inserted a corresponding cross-reference in
       Section 5.  Strengthened the language in Section 4.2 along the
       lines suggested by Thomas Narten.  Small typos corrected.   
Added a
       further sentence in Section 4.1 intended to act as further
       encouragement for operators to implement [RFC3704].

I still have my doubts about the practical usefulness of a standards  
document attempting to dictate operational behaviour using normative  
language, but since my doubts aren't widely shared I am happy to  
throw them to the side.

Unified diff follows; new candidate text is attached. If I've missed  
any other updates requested by people, please let me know and I  
promise a more rapid turn-around for subsequent candidates.

Alternatively, if people tell me to submit this as -01, I will do so  
with all due alacrity.

Thanks,


Joe

--- draft-ietf-ipv6-deprecate-rh0-01-01.unpg    2007-06-25  
12:52:59.000000000 -0400
+++ draft-ietf-ipv6-deprecate-rh0-01.unpg       2007-06-25  
12:51:22.000000000 -0400
@@ -11,7 +11,7 @@
               Deprecation of Type 0 Routing Headers in IPv6
-             draft-ietf-ipv6-deprecate-rh0-01-candidate-01
+             draft-ietf-ipv6-deprecate-rh0-01-candidate-02
Status of this Memo
@@ -45,10 +45,11 @@
Abstract
     The functionality provided by IPv6's Type 0 Routing Header can be
-   exploited in order to achieve packet amplification for the purposes
-   of generating denial-of-service traffic.  This document updates the
-   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
-   Headers, in the light of the severity of this security concern.
+   exploited in order to achieve traffic amplification over a remote
+   path for the purposes of generating denial-of-service traffic.  This
+   document updates the IPv6 specification to deprecate the use of IPv6
+   Type 0 Routing Headers, in the light of the severity of this  
security
+   concern.
     This document updates RFC 2460 and RFC 4294.
@@ -80,11 +81,29 @@
     also defined.  Type 0 Routing Headers are referred to as "RH0" in
     this document.
-   The functionality provided by IPv6's Type 0 Routing Header can be
-   exploited in order to achieve packet amplification for the purposes
-   of generating denial-of-service traffic.  This document updates the
-   IPv6 specification to deprecate the use of IPv6 Type 0 Routing
-   Headers, in the light of the severity of this security concern.
+   A single RH0 may contain multiple waypoint addresses, and the same
+   address may be included more than once in the same RH0.  This allows
+   a packet to be constructed such that it will oscillate between two
+   RH0-processing hosts or routers many times.  This allows a stream of
+   packets from an attacker to be amplified along the path between two
+   remote routers, which could be used to cause congestion along
+   arbitrary remote paths and hence act as a denial-of-service
+   mechanism. 88-fold amplification has been demonstrated using this
+   technique [CanSecWest07].
+
+   This attack is particularly serious in that it affects the entire
+   path between the two exploited nodes, not only the nodes themselves
+   or their local networks.  Analogous functionality may be found in  
the
+   IPv4 source route option, but the opportunities for abuse are  
greater
+   with RH0 due to the ability to specify many more waypoints in each
+   packet.
+
+   The severity of the threat is considered to be sufficient to warrant
+   deprecation of RH0 entirely.  This has the unfortunate side-effect
+   that benign use cases for RH0 are eliminated along with the  
potential
+   security hazards; such applications may be facilitated in the future
+   by new routing header specifications which do not suffer from RH0's
+   problems.
     This document updates [RFC2460] and [RFC4294].
@@ -129,21 +148,27 @@
     described in [CanSecWest07] can be mitigated using ingress  
filtering,
     as recommended in [RFC2827] and [RFC3704].
+   A site security policy intended to protect against attacks using RH0
+   SHOULD include the implementation of ingress filtering at the site
+   border.
+
4.2.  Firewall Policy
+   Blocking all IPv6 packets which carry Routing Headers (rather than
+   specifically blocking type 0, and permitting other types) has very
+   serious implications for the future development of IPv6.  If even a
+   small percentage of deployed firewalls block other types of routing
+   headers by default, it will become impossible in practice to extend
+   IPv6 routing headers.  For example, Mobile IPv6 [RFC3775] relies  
upon
+   a type-2 RH; wide-scale, indescriminate blocking of Routing Headers
+   will make Mobile IPv6 undeployable.
+
     Firewall policy intended to protect against packets containing RH0
-   should be constructed such that routing headers of other types  
(which
-   may well have legitimate and benign applications) are handled on
-   their own merits.  For example, discarding all packets with any type
-   of routing header simply as a reaction to the problems with RH0 is
-   inappropriate, and may hamper future functionality designed using
-   non-type 0 routing headers.  For example, Mobile IPv6 uses the  
type 2
-   Routing Header [RFC3775].
-
-   Where filtering capabilities do not facilitate matching specific
-   types of Routing Headers, filtering based on the presence of any
-   Routing Headers on IPv6 routers, without explicitly checking the
-   Routing Header type, is strongly discouraged.
+   MUST NOT simply filter all traffic with a routing header; it must be
+   possible to disable forwarding of type 0 traffic without blocking
+   other types of routing headers.  In addition, the default
+   configuration MUST permit forwarding of traffic using a RH other  
than
+   0.
5.  Security Considerations
@@ -153,31 +178,8 @@
     examples of vulnerabilities which are facilitated by the  
availability
     of RH0 can be found in [CanSecWest07].  In particular, RH0  
provides a
     mechanism for traffic amplification, which might be used as a  
denial-
-   of-service attack.
-
-   A single RH0 may contain multiple waypoint addresses, and the same
-   address may be included more than once in the same RH0.  This allows
-   a packet to be constructed such that it will oscillate between two
-   RH0-processing hosts or routers many times.  This allows a stream of
-   packets from an attacker to be amplified along the path between two
-   remote routers, which could be used to cause congestion along
-   arbitrary remote paths and hence act as a denial-of-service
-   mechanism. 88-fold amplification has been demonstrated using this
-   technique [CanSecWest07].
-
-   This attack is particularly serious in that it affects the entire
-   path between the two exploited nodes, not only the nodes themselves
-   or their local networks.  Analogous functionality may be found in  
the
-   IPv4 source route option, but the opportunities for abuse are  
greater
-   with RH0 due to the ability to specify many more waypoints in each
-   packet.
-
-   The severity of the threat is considered to be sufficient to warrant
-   deprecation of RH0 entirely.  This has the unfortunate side-effect
-   that benign use cases for RH0 are eliminated along with the  
potential
-   security hazards; such applications may be facilitated in the future
-   by new routing header specifications which do not suffer from RH0's
-   problems.
+   of-service attack.  A description of this functionality can be found
+   in Section 1.
6.  IANA Considerations
@@ -282,6 +284,13 @@
     01-candidate-01  Incorporated contributions from working group:
        substantially reduced Section 5; clarified wording in Section 3.
+   01-candidate-02  Moved description of traffic amplification to
+      Section 1, and inserted a corresponding cross-reference in
+      Section 5.  Strengthened the language in Section 4.2 along the
+      lines suggested by Thomas Narten.  Small typos corrected.   
Added a
+      further sentence in Section 4.1 intended to act as further
+      encouragement for operators to implement [RFC3704].
+
Authors' Addresses

--Apple-Mail-3-472421224
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; x-unix-mode=0644;
	name=draft-ietf-ipv6-deprecate-rh0-01.txt
Content-Disposition: attachment; filename=draft-ietf-ipv6-deprecate-rh0-01.txt




Network Working Group                                           J. Abley
Internet-Draft                                                   Afilias
Updates: 2460, 4294                                            P. Savola
(if approved)                                                  CSC/FUNET
Intended status: Standards Track                         G. Neville-Neil
Expires: December 27, 2007                       Neville-Neil Consulting
                                                           June 25, 2007


             Deprecation of Type 0 Routing Headers in IPv6
             draft-ietf-ipv6-deprecate-rh0-01-candidate-02

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   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 will expire on December 27, 2007.

Copyright Notice

   Copyright (C) The IETF Trust (2007).

Abstract

   The functionality provided by IPv6's Type 0 Routing Header can be
   exploited in order to achieve traffic amplification over a remote
   path for the purposes of generating denial-of-service traffic.  This
   document updates the IPv6 specification to deprecate the use of IPv6
   Type 0 Routing Headers, in the light of the severity of this security



Abley, et al.           Expires December 27, 2007               [Page 1]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   concern.

   This document updates RFC 2460 and RFC 4294.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Deprecation of RH0  . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Operations  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     4.1.  Ingress Filtering . . . . . . . . . . . . . . . . . . . . . 4
     4.2.  Firewall Policy . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . . . 6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 7
   Intellectual Property and Copyright Statements  . . . . . . . . . . 9





























Abley, et al.           Expires December 27, 2007               [Page 2]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


1.  Introduction

   [RFC2460] defines an IPv6 extension header called "Routing Header",
   identified by a Next Header value of 43 in the immediately preceding
   header.  A particular Routing Header subtype denoted as "Type 0" is
   also defined.  Type 0 Routing Headers are referred to as "RH0" in
   this document.

   A single RH0 may contain multiple waypoint addresses, and the same
   address may be included more than once in the same RH0.  This allows
   a packet to be constructed such that it will oscillate between two
   RH0-processing hosts or routers many times.  This allows a stream of
   packets from an attacker to be amplified along the path between two
   remote routers, which could be used to cause congestion along
   arbitrary remote paths and hence act as a denial-of-service
   mechanism. 88-fold amplification has been demonstrated using this
   technique [CanSecWest07].

   This attack is particularly serious in that it affects the entire
   path between the two exploited nodes, not only the nodes themselves
   or their local networks.  Analogous functionality may be found in the
   IPv4 source route option, but the opportunities for abuse are greater
   with RH0 due to the ability to specify many more waypoints in each
   packet.

   The severity of the threat is considered to be sufficient to warrant
   deprecation of RH0 entirely.  This has the unfortunate side-effect
   that benign use cases for RH0 are eliminated along with the potential
   security hazards; such applications may be facilitated in the future
   by new routing header specifications which do not suffer from RH0's
   problems.

   This document updates [RFC2460] and [RFC4294].

   IPv6 implementations are no longer required to implement RH0 in any
   way.


2.  Definitions

   RH0 in this document denotes the IPv6 Extension Header type 43
   ("Routing Header") variant 0 ("Type 0 Routing Header"), as defined in
   [RFC2460].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].




Abley, et al.           Expires December 27, 2007               [Page 3]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


3.  Deprecation of RH0

   IPv6 nodes MUST NOT process RH0 in packets whose destination address
   in the IPv6 header is an address assigned to them.  Such packets MUST
   be processed according to the behaviour specified in Section 4.4 of
   [RFC2460] for a datagram which includes an unrecognised Routing Type
   value, namely:

      If Segments Left is zero, the node must ignore the Routing header
      and proceed to process the next header in the packet, whose type
      is identified by the Next Header field in the Routing header.

      If Segments Left is non-zero, the node must discard the packet and
      send an ICMP Parameter Problem, Code 0, message to the packet's
      Source Address, pointing to the unrecognised Routing Type.


4.  Operations

4.1.  Ingress Filtering

   It is to be expected that it will take some time before all IPv6
   nodes are updated to remove support for RH0.  Some of the uses of RH0
   described in [CanSecWest07] can be mitigated using ingress filtering,
   as recommended in [RFC2827] and [RFC3704].

   A site security policy intended to protect against attacks using RH0
   SHOULD include the implementation of ingress filtering at the site
   border.

4.2.  Firewall Policy

   Blocking all IPv6 packets which carry Routing Headers (rather than
   specifically blocking type 0, and permitting other types) has very
   serious implications for the future development of IPv6.  If even a
   small percentage of deployed firewalls block other types of routing
   headers by default, it will become impossible in practice to extend
   IPv6 routing headers.  For example, Mobile IPv6 [RFC3775] relies upon
   a type-2 RH; wide-scale, indescriminate blocking of Routing Headers
   will make Mobile IPv6 undeployable.

   Firewall policy intended to protect against packets containing RH0
   MUST NOT simply filter all traffic with a routing header; it must be
   possible to disable forwarding of type 0 traffic without blocking
   other types of routing headers.  In addition, the default
   configuration MUST permit forwarding of traffic using a RH other than
   0.




Abley, et al.           Expires December 27, 2007               [Page 4]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


5.  Security Considerations

   The purpose of this document is to deprecate a feature of IPv6 which
   has been shown to have undesirable security implications.  Specific
   examples of vulnerabilities which are facilitated by the availability
   of RH0 can be found in [CanSecWest07].  In particular, RH0 provides a
   mechanism for traffic amplification, which might be used as a denial-
   of-service attack.  A description of this functionality can be found
   in Section 1.


6.  IANA Considerations

   The IANA registry "Internet Protocol Version 6 (IPv6) Parameters"
   should be updated to reflect that variant 0 of IPv6 header-type 43
   ("Routing Header") is deprecated.


7.  Acknowlegements

   Potential problems with Routing Headers were identified in 2001
   [I-D.savola-ipv6-rh-ha-security].  In 2002 a proposal was made to
   restrict Routing Header processing in hosts
   [I-D.savola-ipv6-rh-hosts].  These efforts did not gain sufficient
   momentum to change the IPv6 specification, but resulted in the
   modification of the Mobile IPv6 specification to use the type 2
   Routing Header instead of RH0 [RFC3775].  Vishwas Manral identified
   various risks associated with RH0 in 2006 including the amplification
   attack; several of these vulnerabilities (together with other issues)
   were later documented in [I-D.ietf-v6ops-security-overview].

   An eloquent and useful description of the operational security
   implications of RH0 was presented by Philippe Biondi and Arnaud
   Ebalard at the CanSecWest conference in Vancouver, 2007
   [CanSecWest07].  This presentation resulted in widespread publicity
   for the risks associated with RH0.

   This document also benefits from the contributions of IPV6 and V6OPS
   working group participants, including Jari Arkko, Arnaud Ebalard, Tim
   Enos, Brian Haberman, Jun-ichiro itojun HAGINO, Bob Hinden, Thomas
   Narten, JINMEI Tatuya, David Malone, Jeroen Massar, Dave Thaler and
   Guillaume Valadon.


8.  References






Abley, et al.           Expires December 27, 2007               [Page 5]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


8.1.  Normative References

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

   [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
              (IPv6) Specification", RFC 2460, December 1998.

   [RFC4294]  Loughney, J., "IPv6 Node Requirements", RFC 4294,
              April 2006.

8.2.  Informative References

   [CanSecWest07]
              BIONDI, P. and A. EBALARD, "IPv6 Routing Header Security",
              CanSecWest Security Conference 2007, April 2007.

              http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf

   [I-D.ietf-v6ops-security-overview]
              Davies, E., "IPv6 Transition/Co-existence Security
              Considerations", draft-ietf-v6ops-security-overview-06
              (work in progress), October 2006.

   [I-D.savola-ipv6-rh-ha-security]
              Savola, P., "Security of IPv6 Routing Header and Home
              Address Options", draft-savola-ipv6-rh-ha-security-02
              (work in progress), March 2002.

   [I-D.savola-ipv6-rh-hosts]
              Savola, P., "Note about Routing Header Processing on IPv6
              Hosts", draft-savola-ipv6-rh-hosts-00 (work in progress),
              February 2002.

   [RFC2827]  Ferguson, P. and D. Senie, "Network Ingress Filtering:
              Defeating Denial of Service Attacks which employ IP Source
              Address Spoofing", BCP 38, RFC 2827, May 2000.

   [RFC3704]  Baker, F. and P. Savola, "Ingress Filtering for Multihomed
              Networks", BCP 84, RFC 3704, March 2004.

   [RFC3775]  Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
              in IPv6", RFC 3775, June 2004.


Appendix A.  Change History

   This section to be removed prior to publication.



Abley, et al.           Expires December 27, 2007               [Page 6]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   00 Strawman, draft-jabley-ipv6-rh0-is-evil, circulated to provoke
      discussion.

   01 Clarified Section 3; presented more options in Section 4; added
      Pekka and George as authors.  This document version was not widely
      circulated.

   00 Renamed, draft-ietf-ipv6-deprecate-rh0, a candidate working group
      document.

   01-candidate-00  Incorporated text summarising some of the unwelcome
      uses of RH0; added some clariying text describing deprecation;
      modified some ambiguous text in Section 4.2; added "Updates:
      4294".

   01-candidate-01  Incorporated contributions from working group:
      substantially reduced Section 5; clarified wording in Section 3.

   01-candidate-02  Moved description of traffic amplification to
      Section 1, and inserted a corresponding cross-reference in
      Section 5.  Strengthened the language in Section 4.2 along the
      lines suggested by Thomas Narten.  Small typos corrected.  Added a
      further sentence in Section 4.1 intended to act as further
      encouragement for operators to implement [RFC3704].


Authors' Addresses

   Joe Abley
   Afilias Canada Corp.
   Suite 204, 4141 Yonge Street
   Toronto, ON  M2P 2A8
   Canada

   Phone: +1 416 673 4176
   Email: jabley@ca.afilias.info


   Pekka Savola
   CSC/FUNET
   Espoo,
   Finland

   Email: psavola@funet.fi







Abley, et al.           Expires December 27, 2007               [Page 7]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


   George Neville-Neil
   Neville-Neil Consulting
   2261 Market St. #239
   San Francisco, CA  94114
   USA

   Email: gnn@neville-neil.com












































Abley, et al.           Expires December 27, 2007               [Page 8]
=0C
Internet-Draft             Deprecation of RH0                  June 2007


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Acknowledgment

   Funding for the RFC Editor function is provided by the IETF
   Administrative Support Activity (IASA).





Abley, et al.           Expires December 27, 2007               [Page 9]
=0C

--Apple-Mail-3-472421224
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--Apple-Mail-3-472421224--




From ipv6-bounces@ietf.org Mon Jun 25 13:09:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2s3h-0003Aj-IU; Mon, 25 Jun 2007 13:09:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2s3g-0003AP-NY
	for ipv6@ietf.org; Mon, 25 Jun 2007 13:09:00 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2s3f-0000Fq-Jl
	for ipv6@ietf.org; Mon, 25 Jun 2007 13:09:00 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id A2E24140C271;
	Mon, 25 Jun 2007 19:08:56 +0200 (CEST)
Message-ID: <467FF6AA.5000604@spaghetti.zurich.ibm.com>
Date: Mon, 25 Jun 2007 18:08:58 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1069637156=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1069637156==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig6441ABDCA90FA7F6798F9A02"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6441ABDCA90FA7F6798F9A02
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Templin, Fred L wrote:
[..]

>> Thus you are connecting to the Internet, using IPv4 or IPv6 doesn't
>> matter, you have a dependency on the Internet. As such you are not
>> working dis-connected from the Internet and you have a=20
>> dependency on it.
>=20
> Only when you want to connect to another site.

Thus the moment you are connecting to another site you are forcing one
to also connect to the Internet.

[..]
> Again, *no* NAT'ing of IPv6.

How are you going to use ULA-C addresses as a source and then connect to
 hosts on the global Internet?

[..]
> A laptop fits this description. Think of one running some
> of this new virtualization support whereby there may be
> many virtual machines connected up by virtual networks
> running within the laptop. (Actually, folks like IBM were
> doing this "new" virtualization on their mainframes back
> in the 70's...)=20

I have one of those sweet laptops and I have 3 OS's running at the same
time most of the time. I use RFC1918 and simply randomly picked
172.17.123.0/24 which has (upto now :) never collided with the networks
that I visited. ULA (RFC4193) would have that same property. I have to
note that I have to NAT that address space to the network I am at, who
only give me 1 single IP address most of the time (could use bridging
and prolly ask for more addresses per DHCP of course). Having them route
my prefix to me though everytime I walk into a Starbucks or a hotel etc
is really never ever going to happen. There is no "this is my prefix
route my traffic here" protocol (at least yet). Also no single network
operator will ever accept such a protocol as it is their network, not
that of the visitor to control. Viruses and {cr|h}ackers would love it I
guess.

When you are in the position to negotiate the routing part, then having
them turn up DNS, which has to happen for both forward (how else are
they going to locate your host) and reverse hosts is very doable.
This then nullifies the whole requirement of having NS pointers to your
servers, which have to have internet-connected and static addresses
unless you want to update them all the time, which for sure makes the
RIR happy who definitely want to have more cash then for doing that.

Or are your requiring sites you visit to have Internet connectivity as
you only have your servers (forward + reverse) on the Internet?

>> this can
>> mean indeed a major corporation (who maybe even require multiple /48's=

>> which is why rfc4193 is a bit off to cover those cases)
>>
>> If you want to have a /48 for your laptop, simply use ULA (RFC4193)
>> those are free.
>=20
> RFC4193 ULA is good, but could be better. However remote the
> possibility of collisions, IMHO there would still be value in
> having a 3rd-party mechanism to avoid duplicate assignments
> and/or de-conflict duplicates.  =20

It exists: PI space. Get it at ARIN today: $100/year

Which if you have such a high reliability requirement for non-clashes is
very cheap and gives you the possibility to do reverse DNS and even
route it on the global internet, just in case they provide you with
transit at the site you happen to come along.

>> Or are you simply wanting to have your own IP=20
>> addresses,
>> setting up firewalling etc because you have a laptop (or Winnebago
>> filled with servers) and carrying it around globally through various
>> buildings and making other networks accept your /48 AND force them to
>> connect to the Internet to be able to resolve your reverse?
>=20
> I don't quite understand this, but I want to be able to
> drop my laptop down in whatever visited network and have
> it connect to other sites w/o having to manually configure
> explicit VPNs.=20

How are you 'automatically' telling the network to route packets for
'your prefix' to your device? See above.

>> Most likely anyway when you connect your laptop to another site they
>> will be providing you with an IP address anyway from their=20
>> site prefix.
>=20
> One use I could see for that is if you needed a care-of
> address such as used for MIPv6.

Care-of-addresses are simply the address you get per DHCP/RA.

> But, that gets off onto a completely different line of discussion.

It also has nothing to do with connecting to sites.

>> Can you clarify the use case you are sketching here a lot more as I
>> really want to know what actual use case is actually useful that ULA-C=

>> solves, what PI doesn't solve (Drawings + text help). Especially now
>> that the folks who 'want/need' ULA-C do want to have reverse DNS
>> available from the Internet, while they want to be local in=20
>> the first place.
>=20
> I already gave my use-case in:
>=20
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07806.html

As I mentioned above, how are the routing protocols "automatically"
trusting that you own the prefix, or for that matter finding each other
in the first place. This will involve a protocol that can handle this.
When such a protocol exists you can also have it handle your reverse DNS
setup.

I fully agree that there is a need for "Unique Addresses", and these
exist already, it is called: PI.

>> All those cases can be covered perfectly fine by PI. Or is it=20
>> just that
>> folks see ULA-C as 'very cheap PI space'?
>=20
> Again, I don't know about other folks but for me I see the
> price as too high for some "sites" to have to pay.

Thus the only reason for ULA-C seems to be that PI is "too expensive".
Folks are always forgetting that there is a need for a lot of other
things which are way more expensive than that: the actual hardware being
used, power, maintenance, people being payed etc etc etc.

Why would the IETF have to solve the problem of having "expensive
address space" for the few who simply want it for free, by providing
address space which is only cheaper, but for the rest exactly the same
as existing solutions and in the long run will only cause people to use
it on the global Internet and thus becoming a cost factor to everybody?

Is 2^-40 probability really not enough for those sites? If they can't
cough up $100/year, then they most likely don't have a lot of hosts
actually involved and thus renumbering in the case of a collision of ULA
(RFC4193) can't be that high either. If the probability is too high for
them and the cost of renumbering is too high then PI for $100/year is
suddenly really cheap. As such, sorry, but I don't see any problem that
ULA-C will solve. I do see the problems that it will cause in the long ru=
n.

Greets,
 Jeroen


--------------enig6441ABDCA90FA7F6798F9A02
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkZ/9qsuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+wJAJ9Ycd2sAsLYYBsmJQBVX3Y7k8Xv
MwCgoUuqp9nO+U4cC5Sisf9zqxvmaBU=
=c9mA
-----END PGP SIGNATURE-----

--------------enig6441ABDCA90FA7F6798F9A02--


--===============1069637156==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1069637156==--




From ipv6-bounces@ietf.org Mon Jun 25 13:17:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2sBi-0005lD-BX; Mon, 25 Jun 2007 13:17:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2sBh-0005l6-EK
	for ipv6@ietf.org; Mon, 25 Jun 2007 13:17:17 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2sBe-0001JL-SF
	for ipv6@ietf.org; Mon, 25 Jun 2007 13:17:17 -0400
Received: from [63.251.161.196] (account sleibrand@mail.internap.com HELO
	[63.251.161.196])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85002258; Mon, 25 Jun 2007 13:17:13 -0400
Message-ID: <467FF894.7000908@internap.com>
Date: Mon, 25 Jun 2007 10:17:08 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
In-Reply-To: <467FDEAA.1020503@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar wrote:
>
> As such, what is the 'local' part again, how local is it really? And how
> is ULA-C then different from PI? Why bother people with this ULA-C thing
> when they really need PI in the first place? Which they can already get
> for $100/year from ARIN and which will be guaranteed unique, just like
> all other address space from the RIR's.
>
>   

Jeroen,

PI space is *not* available, *at any price*, to small sites.

ARIN (and generally, RIR) policy for the allocation of PI space (space 
assigned directly from the RIR to end sites that they can announce into 
the DFZ) is based on the assumption that any such space, once allocated, 
can add an additional route to the BGP table of hundreds of thousands of 
routers across the globe.  Therefore, such policy must be conservative 
in handing out such blocks.

A need has been put forward for registered unique IPv6 address space 
that is not intended to be advertised into the DFZ.  One viable way to 
meet this need is with ULA-C.  Another way would be with a new class of 
"private PI" space out of a dedicated block that DFZ operators would not 
accept routes from.

If you'd like to advocate we create RIR policy for private PI space 
instead of doing ULA-C, please put forth your arguments for why it would 
be better.  Or, if you think that the need presented is too 
insignificant to be worth standardizing 
draft-ietf-ipv6-ula-central-02.txt for, fine.  But please quit telling 
us that we don't need ULA-C because we can just go get PI space today.

-Scott


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 14:04:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2sv6-0005vj-S1; Mon, 25 Jun 2007 14:04:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2sv3-0005vE-Te
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:04:09 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2sv1-0000TF-KJ
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:04:09 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id 719CA3A6E3;
	Mon, 25 Jun 2007 13:37:10 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id EF818144D37;
	Mon, 25 Jun 2007 17:37:09 +0000 (UTC)
Message-ID: <467FFD45.7010107@hp.com>
Date: Mon, 25 Jun 2007 13:37:09 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>	<467C34B8.20801@ericsson.com>
	<77ead0ec0706221400q279c6097r7b5d22922645638a@mail.gmail.com>
In-Reply-To: <77ead0ec0706221400q279c6097r7b5d22922645638a@mail.gmail.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Vishwas Manral wrote:
> Hi Suresh/ Vlad,
> 
> For SIIT the fragment header is used to signal the ability to
> fragment, it does not state it is a fragment itself.

First, this only happens when the IPv4 host does not support path mtu
discovery (DF bit is 0).  In this case, inserting a fragment header
at the translator in essence performs the fragmentation that was
requested by the sender.  I just so happens that in this case the
fragment might have offset and M flag set to 0.

> 
>> A fragment with offset 0 and M flag 0 is just treated as the ONLY
>> fragment. No harm don
> But there are different policies for fragments, including some that
> drop fragments. It is not the correct behavior, I feel the definition
> of a fragment should be clarified.

Now you are getting in policies outside of the definition.  The definition
does not have to encompass all eventual uses.  Otherwise we'll be updating
a lot more specs.

-vlad


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 14:12:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2t33-0001a0-KR; Mon, 25 Jun 2007 14:12:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2t31-0001Iu-J7
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:12:23 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2t30-0001wK-7i
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:12:23 -0400
Received: from [64.213.227.189] (catv.centennialpr.net [64.213.227.189] (may
	be forged)) (authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5PICJqu003747
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 25 Jun 2007 11:12:21 -0700
In-Reply-To: <467FF894.7000908@internap.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<467FF894.7000908@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B2726845-1BD3-4231-A83C-188488016102@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Mon, 25 Jun 2007 14:12:15 -0400
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 25 Jun 2007, at 1:17pm, Scott Leibrand wrote:

[...]

> PI space is *not* available, *at any price*, to small sites.

How many of these sites that are too small to qualify for PI space  
are likely to have such a large number of inter-site connections that  
there is a credible risk that there will be an address clash?

Regards,

Leo Vegoda
IANA Numbers Liaison

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 14:22:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2tDD-0004kp-QR; Mon, 25 Jun 2007 14:22:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2tDD-0004kk-Cc
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:22:55 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2tDC-000572-6S
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:22:55 -0400
Received: from [63.251.161.196] (account sleibrand@mail.internap.com HELO
	[63.251.161.196])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85007697; Mon, 25 Jun 2007 14:22:52 -0400
Message-ID: <468007E3.8070206@internap.com>
Date: Mon, 25 Jun 2007 11:22:27 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<467FF894.7000908@internap.com>
	<B2726845-1BD3-4231-A83C-188488016102@icann.org>
In-Reply-To: <B2726845-1BD3-4231-A83C-188488016102@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Leo Vegoda wrote:
> On 25 Jun 2007, at 1:17pm, Scott Leibrand wrote:
>
>> PI space is *not* available, *at any price*, to small sites.
>
> How many of these sites that are too small to qualify for PI space are 
> likely to have such a large number of inter-site connections that 
> there is a credible risk that there will be an address clash?
>

I don't know.  I do suspect, however, that the main benefit of ULA-C 
over ULA-L will be the ability to resolve DNS, rather than the 
additional assurance of uniqueness.  Even with a relatively small number 
of inter-site connections, it is much easier to have your DNS resolvers 
(which presumably have a public IP address as well as a ULA one) walk 
the DNS tree rather than manually configuring them to slave off of each 
other site's DNS servers.  (I would compare it to doing all your 
inter-site routing with static routes instead of using a routing protocol.)

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 14:56:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2tjA-00079b-Sx; Mon, 25 Jun 2007 14:55:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2tj9-00078B-BR
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:55:55 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2tj7-0004Mp-R9
	for ipv6@ietf.org; Mon, 25 Jun 2007 14:55:55 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id 785DDA6FB9E
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 11:55:53 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 6388329C004
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 11:55:53 -0700 (PDT)
X-AuditID: 11807123-a301cbb000000a55-a9-46800fb9b641
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 46B99304010
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 11:55:53 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E727B713-793C-49E5-A15A-58334396573B@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 25 Jun 2007 11:55:50 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 25, 2007, at 09:33, Templin, Fred L wrote:
>
> I already gave my use-case in:
>
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07806.html
>>
>> The use-case I am most interested in is Mobile Ad-Hoc Networks  
>> (MANETs) in which two or more MANETs can merge (e.g., due to  
>> mobility). If each MANET used ULA-C's, then they could inject each  
>> others' prefixes into their IGPs with no opportunity for  
>> collision. If each MANET instead used RFC4193 ULAs, then they  
>> could *probably* still inject each others' prefixes. But, however  
>> small the risk of collision, RFC4193 ULAs still have one drawback  
>> that ULA-C's do not - uncertainty.
>>
>> So perhaps another question is whether it is too much to ask for  
>> more certainty (ULA-C) and less mystery (RFC4193 ULA)?

The "no opportunity for collision" thing is really the question here,  
as Brian E. Carpenter said in <http://www1.ietf.org/mail-archive/web/ 
ipv6/current/msg07834.html> and others have said elsewhere.  Most of  
the pushback is directed at this claim that central registration has  
some hope for mitigating an already *epsilon* risk of collision.  I  
don't think simply reiterating the claim is an appropriate response  
to the legitimate rebuttal it's received.

An additional claim we've seen is that ULA-C should offer reverse  
delegations from ip6.arpa in the public DNS horizon, whereas ULA-L  
(straight RFC 4193) does not.  Your use case does not seem to me to  
support the argument for ULA-C, but actually demonstrates its weakness.

When two MANET merge by exchanging ULA prefixes (let's forget about  
ULA-C vs. ULA-L for now, because the name resolution problem is  
common to both), then their DNS horizons must be merged as well.  The  
networks are *ad-hoc*, so they do not have name servers provisioned  
with globally reachable unicast addresses.  If they did, then they  
wouldn't be *ad-hoc* mobile networks.  They'd be *provisioned* mobile  
networks.

So, the two MANET may have name servers, but if so, then they're only  
reachable at ULA addresses and they contain records that are only  
usable inside the merged MANET.  What you need to do is exchange the  
reverse delegations for the ULA prefixes at the same time you  
exchange the prefixes.  You already have to merge two private DNS  
horizons into a single private DNS horizon.  Asking for help from the  
public DNS horizon seems like a very questionable thing to propose.

Looking up the AAAA records containing ULA-C addresses for the peer  
MANET name servers in the public DNS horizon is prohibitively  
expensive for the usage scenario you're proposing.  Let me  
illustrate.  Who will operate the authoritative name servers for the  
global public 0.0.c.f.ip6.arpa domain?  How will mobile *ad-hoc*  
networks get NS records inserted into that zone?  How are they  
changed?  How will registrations be released and made available for  
reuse?  Do registrations expire if you don't pay your bills on time?   
Perhaps most importantly, how do MANET remain *ad-hoc* given such  
provisioning requirements?  All those questions seem to be pressing  
and unanswered.

(p.s. I have long contended with my colleague, Stuart Cheshire, that  
Multicast DNS could use to be extended to support organization-local  
scope multicast, precisely to support ad-hoc ULA-addressed  
internets.  Alas, there hasn't been much perception around here of  
any burning need to do it-- the subject of rendezvous points always  
comes up, and nobody has time to come up to speed on all the latest  
technical aspects of the problem.  Perhaps additional energy should  
be expended there toward those ends?)


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 15:40:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2uPd-0006wQ-ID; Mon, 25 Jun 2007 15:39:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2uPa-0006wL-Vk
	for ipv6@ietf.org; Mon, 25 Jun 2007 15:39:46 -0400
Received: from wa-out-1112.google.com ([209.85.146.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uPY-0001fS-16
	for ipv6@ietf.org; Mon, 25 Jun 2007 15:39:46 -0400
Received: by wa-out-1112.google.com with SMTP id k17so1476067waf
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 12:39:41 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=B3O9/++yNNEwFBpb4F5y2gXZnAsHj7RKjRBW2bsiRKtToNEBjv1ahTnvjEAIFGJkJpGE8tMmf4rDPZTE4AHZSOucYXfFiQXctGn73tbiEfuDVzwkYwoIQx9eTgHBa6dvnDPFK48n6z/F0vfLvn3xkH8UbOoKuotljaJCikttFX4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=aeyL2vShFZWJCR0QlDYimzcR44SW1kA5QC8TLTiTB/j14ZNCWRJ5cp9Rm1tRRKuJ3VHPb4+cCEdYVZM2eXHu0lNGhIftDiXAiWyUSLY+LOSxPYQXQGjWZEoSQVr50+YgTv2pxSuFuqa6SK7sO0Nc2OU5A8Xom6tFDp7RTHrpQHY=
Received: by 10.115.15.1 with SMTP id s1mr5716507wai.1182800381735;
	Mon, 25 Jun 2007 12:39:41 -0700 (PDT)
Received: by 10.114.154.5 with HTTP; Mon, 25 Jun 2007 12:39:41 -0700 (PDT)
Message-ID: <77ead0ec0706251239o19a6cd6cy64b6eece094cc03d@mail.gmail.com>
Date: Mon, 25 Jun 2007 12:39:41 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
In-Reply-To: <467FFD45.7010107@hp.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_8549_11239776.1182800381657"
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>
	<467C34B8.20801@ericsson.com>
	<77ead0ec0706221400q279c6097r7b5d22922645638a@mail.gmail.com>
	<467FFD45.7010107@hp.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6b519fb0ef66258f34533f52ff46aedf
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

------=_Part_8549_11239776.1182800381657
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Vlad,

Thanks a lot for your clarification, maybe I am unclear. I am
attaching a document I have attached, just have a look.

> First, this only happens when the IPv4 host does not support path mtu
> discovery (DF bit is 0).  In this case, inserting a fragment header
> at the translator in essence performs the fragmentation that was
> requested by the sender.  I just so happens that in this case the
> fragment might have offset and M flag set to 0.
There are 2 sides of the problem. The first is that different
protocols use different definition of a fragment, which needs to be
clarified, because some assumption by a protocol may not work in many
cases due to the specification clarity. The second part is the use of
different policies for fragments.

The idea I am stating is that one spec uses the Fragment header to
just signal its ability to perform fragmentation, while others
specs(AH & ESP for one) clearly lay down a differnet way for
identifying an IPv6 fragment and its subsequent treatment. As there
are different policies for fragments, the signaling may not work in
many cases(no I am not talking about policies but the clarification of
the term Fragment - example a Fragment with M = 0 and Offset = 0
should be treated as a non fragmented packet). I do not see any
problem  in clarifying exactly what an IPv6 fragment is so that we can
have a consistent set of specs as well as implementations.

> Now you are getting in policies outside of the definition.  The definition
> does not have to encompass all eventual uses.  Otherwise we'll be updating
> a lot more specs.
No, I am talking about specs too besides practical network scenarios.
If we see a problem in a spec I do not see a reason we should hesitate
in fixing the problems (and its not unprecedented either).

Thanks,
Vishwas

On 6/25/07, Vlad Yasevich <vladislav.yasevich@hp.com> wrote:
> Vishwas Manral wrote:
> > Hi Suresh/ Vlad,
> >
> > For SIIT the fragment header is used to signal the ability to
> > fragment, it does not state it is a fragment itself.
>
> First, this only happens when the IPv4 host does not support path mtu
> discovery (DF bit is 0).  In this case, inserting a fragment header
> at the translator in essence performs the fragmentation that was
> requested by the sender.  I just so happens that in this case the
> fragment might have offset and M flag set to 0.
>
> >
> >> A fragment with offset 0 and M flag 0 is just treated as the ONLY
> >> fragment. No harm don
> > But there are different policies for fragments, including some that
> > drop fragments. It is not the correct behavior, I feel the definition
> > of a fragment should be clarified.
>
> Now you are getting in policies outside of the definition.  The definition
> does not have to encompass all eventual uses.  Otherwise we'll be updating
> a lot more specs.
>
> -vlad
>
>

------=_Part_8549_11239776.1182800381657
Content-Type: text/plain; name=draft-manral-ipv6-fragment-00.txt; 
	charset=ANSI_X3.4-1968
Content-Transfer-Encoding: base64
X-Attachment-Id: f_f3dcrggj
Content-Disposition: attachment; filename="draft-manral-ipv6-fragment-00.txt"

TmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgVi4gTWFucmFsDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgSVAgSW5mdXNpb24gICANCkV4cGlyZXM6IERlY2VtYmVyIDI1
LCAyMDA3ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgSnVuZSAyNiwgMjAw
Nw0KDQoNCg0KICAgICAgICAgICAgICAgSVB2NiBGcmFnbWVudHMgYW5kIHRyZWF0bWVudCBvZiBU
aW55IGZyYWdtZW50cyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICAgICAg
ICAgICAgIGRyYWZ0LW1hbnJhbC1pcHY2LWZyYWdtZW50cy0wMA0KDQoNClN0YXR1cyBvZiB0aGlz
IE1lbW8NCg0KICAgQnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhv
ciByZXByZXNlbnRzIHRoYXQgYW55DQogICBhcHBsaWNhYmxlIHBhdGVudCBvciBvdGhlciBJUFIg
Y2xhaW1zIG9mIHdoaWNoIGhlIG9yIHNoZSBpcyBhd2FyZQ0KICAgaGF2ZSBiZWVuIG9yIHdpbGwg
YmUgZGlzY2xvc2VkLCBhbmQgYW55IG9mIHdoaWNoIGhlIG9yIHNoZSBiZWNvbWVzDQogICBhd2Fy
ZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNlY3Rpb24gNiBvZiBCQ1Ag
NzkuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1bWVudHMgb2YgdGhlIElu
dGVybmV0IEVuZ2luZWVyaW5nDQogICBUYXNrIEZvcmNlIChJRVRGKSwgaXRzIGFyZWFzLCBhbmQg
aXRzIHdvcmtpbmcgZ3JvdXBzLiAgTm90ZSB0aGF0DQogICBvdGhlciBncm91cHMgbWF5IGFsc28g
ZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC0NCiAgIERyYWZ0cy4NCg0K
ICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11
bSBvZiBzaXggbW9udGhzDQogICBhbmQgbWF5IGJlIHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNv
bGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0IGFueQ0KICAgdGltZS4gIEl0IGlzIGluYXBwcm9w
cmlhdGUgdG8gdXNlIEludGVybmV0LURyYWZ0cyBhcyByZWZlcmVuY2UNCiAgIG1hdGVyaWFsIG9y
IHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiINCg0KICAgVGhl
IGxpc3Qgb2YgY3VycmVudCBJbnRlcm5ldC1EcmFmdHMgY2FuIGJlIGFjY2Vzc2VkIGF0DQogICBo
dHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQuDQoNCiAgIFRoZSBsaXN0
IG9mIEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQN
CiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvc2hhZG93Lmh0bWwuDQoNCiAgIFRoaXMgSW50ZXJuZXQt
RHJhZnQgd2lsbCBleHBpcmUgb24gRGVjZW1iZXIgMjUsIDIwMDcuDQoNCkNvcHlyaWdodCBOb3Rp
Y2UNCg0KICAgQ29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAoMjAwNykuDQoNCkFic3RyYWN0
DQoNCiAgIFtSRkMyNDYwXSBkZWZpbmVzIGFuIElQdjYgaGVhZGVyIGNhbGxlZCAiRnJhZ21lbnQg
SGVhZGVyIiwgd2hpY2ggaXMgDQogICBpZGVudGlmaWVkIGJ5IGEgTmV4dCBIZWFkZXIgdmFsdWUg
b2YgNDQgaW4gdGhlIGltbWVkaWF0ZWx5IHByZWNlZGluZw0KICAgaGVhZGVyLiAgVGhpcyBkb2N1
bWVudCBjbGFyaWZpZXMgdGhlIGRlZmluaXRpb24gb2YgYW4gSVB2NiBmcmFnbWVudCANCiAgIA0K
DQoNCg0KTWFucmFsLCBldCBhbC4gICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDI1LCAyMDA3ICAg
ICAgICAgICAgICAgICAgICBbUGFnZSAxXQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICBJUHY2
ICBGcmFnbWVudHMgICAgICAgICAgICAgICAgIEp1bmUgMjAwNw0KDQogICBhcyB3ZWxsIGFzIGRl
ZmluZXMgdGhlIHRyZWF0bWVudCBvZiB3aGF0IGNvbnNpdGl0dWVzIGEgdGlueSBJUHY2IA0KICAg
RnJhZ21lbnQuDQoNClJlcXVpcmVtZW50cyBMYW5ndWFnZQ0KDQogICBUaGUga2V5IHdvcmRzICJN
VVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsDQogICAi
U0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5kICJPUFRJT05B
TCIgaW4gdGhpcw0KICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVkIGFzIGRlc2NyaWJl
ZCBpbiBSRkMgMjExOSBbUkZDMjExOV0uDQoNClRhYmxlIG9mIENvbnRlbnRzDQoNCiAgIDEuICAg
UHJvYmxlbSBTdGF0ZW1lbnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuICAgMw0KDQogICAyLiAgIElQdjYgRnJhZ21lbnQgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDMNCiANCiAgIDMuICAgVGlueSBGcmFnbWVudHMgYW5k
IGlzc3VlcyAuICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNA0KDQogICA0LiAg
IEFkZGl0aW9uYWwgY2hlY2tzIHJlcXVpcmVkIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIDQNCg0KICAgNS4gICBJQU5BIENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA1DQoNCiAgIDYuICAgU2VjdXJpdHkgQ29uc2lkZXJh
dGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gNg0KDQogICA3LiAg
IEFja25vd2xlZGdlbWVudHMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIDcNCg0KICAgOC4gIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gICA4DQogICAgIDguMSAgIE5vcm1hdGl2ZSBSZWZlcmVu
Y2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDgNCiAgICAgOC4yICAg
SW5mb3JtYXRpdmUgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
ICAgOA0KDQogICAgICAgIEF1dGhvcnMnIEFkZHJlc3NlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAgIDkNCg0KICAgICAgICBJbnRlbGxlY3R1YWwgUHJvcGVydHkg
YW5kIENvcHlyaWdodCBTdGF0ZW1lbnRzIC4gLiAuIC4gLiAuIC4gIDEwDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KTWFucmFsLCBldCBhbC4gICAgICAgICBFeHBpcmVzIERlY2Vt
YmVyIDI1LCAyMDA3ICAgICAgICAgICAgICAgICAgICBbUGFnZSAyXQ0KIA0KSW50ZXJuZXQtRHJh
ZnQgICAgICAgICAgICAgICAgIElQdjYgIEZyYWdtZW50cyAgICAgICAgICAgICAgICAgIEp1bmUg
MjAwNw0KDQoNCjEuICBQcm9ibGVtIFN0YXRlbWVudA0KDQogICBUaGUgZGVmaW5pdGlvbiBvZiBG
cmFnbWVudHMgaXMgc2xpZ2h0bHkgdmFndWUgaW4gdGhlIElQdjYgc3BlY2lmaWNhdGlvbi4NCiAg
IFRoaXMgaGFzIHJlc3VsdGVkIGluIGRpZmZlcmVudCBzcGVjaWZpY2F0aW9uIHVzaW5nIGRpZmZl
cmVudCB3YXlzIGZvciANCiAgIGlkZW50aWZ5aW5nIGZyYWdtZW50cy4gVGhlIFNJSVQgW1JGQzI3
NjVdIHNwZWNpZmljYXRpb24gdXNlcyBhIGZyYWdtZW50DQogICBoZWFkZXIgdG8gc2lnbmFsIHRo
ZSBhYmlsaXR5IG9mIGEgbm9kZSB0byBmcmFnbWVudCBhbiBJUHY2IHBhY2tldCwgdGhlIA0KICAg
RVNQIFtSRkM0MzAzXSBhbmQgQUggW1JGQzQzMDJdIGFzc3VtZSB0aGUgZXhpc3RlbmNlIG9mIGFu
IElQVjYgRnJhZ21lbnQNCiAgIGhlYWRlciBpZGVudGlmaWVzIGFuIElQdjYgRnJhZ21lbnQuIEFz
IGRpZmZlcmVudCBwb2xpY2llcyBhcmUgYXBwbGllZCBmb3INCiAgIGZyYWdtZW50cyBhbmQgbm9u
LWZyYWdtZW50cyBpbiBtaWRkbGUgYm94ZXMsIHN1Y2ggYW1iaWd1aXR5IGluIHRoZSANCiAgIHNw
ZWNpZmljYXRpb24gY2FuIGxlYWQgdG8gaXNzdWVzLg0KDQogICBNaWRkbGVib3hlcyBnZW5lcmFs
bHkgdXNlIDUtdHVwbGVzIHRvIGZpbHRlciBvdXQgcGFja2V0cy4gSG93ZXZlciB0aGVyZQ0KICAg
YXJlIGNhc2VzIHdoZXJlICBmcmFnbWVudGF0aW9uIGNhbiBiZSB1c2VkIHRvIGRpc2d1aXNlIFRD
UCAgcGFja2V0cw0KICAgZnJvbSBJUCBmaWx0ZXJzIGFuZCBvdGhlciBtaWRkbGVib3hlcyBbVGlu
eS1GcmFnbWVudF0gdXNlZCBpbiByb3V0ZXJzIGFuZCANCiAgIGhvc3RzLiBUaGlzIGRvY3VtZW50
IGFsc28gc3BlY2lmaWVzIHdheXMgdG8gaWRlbnRpZnkgdGlueSBmcmFnbWVudHMgYW5kIA0KICAg
dGhlIHN1YnNlcXVlbnQgYWN0aW9uIHRoYXQgbmVlZHMgdG8gYmUgdGFrZW4sIG9uY2Ugc3VjaCBh
IGZyYWdtZW50IGlzIA0KICAgaWRlbnRpZmllZC4NCg0KDQoyLiBJUHY2IEZyYWdtZW50DQoNCiAg
IFRoZSBJUHY2IHNwZWNpZmljYXRpb24gW1JGQzI0NjBdIGRlZmluZXMgYSBmcmFnbWVudCBoZWFk
ZXIgYXM6DQoNCiAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rDQogICB8ICBOZXh0IEhlYWRlciAgfCAgIFJlc2VydmVkICAg
IHwgICAgICBGcmFnbWVudCBPZmZzZXQgICAgfFJlc3xNfA0KICAgKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAgIHwgICAg
ICAgICAgICAgICAgICAgICAgICAgSWRlbnRpZmljYXRpb24gICAgICAgICAgICAgICAgICAgICAg
ICB8DQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKw0KDQogICBOZXh0IEhlYWRlciAgICAgICAgICA4LWJpdCBzZWxlY3Rv
ci4gIElkZW50aWZpZXMgdGhlIGluaXRpYWwgaGVhZGVyDQogICAgICAgICAgICAgICAgICAgICAg
ICB0eXBlIG9mIHRoZSBGcmFnbWVudGFibGUgUGFydCBvZiB0aGUgb3JpZ2luYWwNCiAgICAgICAg
ICAgICAgICAgICAgICAgIHBhY2tldCAoZGVmaW5lZCBiZWxvdykuICBVc2VzIHRoZSBzYW1lIHZh
bHVlcyBhcw0KICAgICAgICAgICAgICAgICAgICAgICAgdGhlIElQdjQgUHJvdG9jb2wgZmllbGQg
W1JGQy0xNzAwIGV0IHNlcS5dLg0KDQogICBSZXNlcnZlZCAgICAgICAgICAgICA4LWJpdCByZXNl
cnZlZCBmaWVsZC4gIEluaXRpYWxpemVkIHRvIHplcm8gZm9yDQogICAgICAgICAgICAgICAgICAg
ICAgICB0cmFuc21pc3Npb247IGlnbm9yZWQgb24gcmVjZXB0aW9uLg0KDQogICBGcmFnbWVudCBP
ZmZzZXQgICAgICAxMy1iaXQgdW5zaWduZWQgaW50ZWdlci4gIFRoZSBvZmZzZXQsIGluIDgtb2N0
ZXQNCiAgICAgICAgICAgICAgICAgICAgICAgIHVuaXRzLCBvZiB0aGUgZGF0YSBmb2xsb3dpbmcg
dGhpcyBoZWFkZXIsDQogICAgICAgICAgICAgICAgICAgICAgICByZWxhdGl2ZSB0byB0aGUgc3Rh
cnQgb2YgdGhlIEZyYWdtZW50YWJsZSBQYXJ0DQogICAgICAgICAgICAgICAgICAgICAgICBvZiB0
aGUgb3JpZ2luYWwgcGFja2V0Lg0KDQogICBSZXMgICAgICAgICAgICAgICAgICAyLWJpdCByZXNl
cnZlZCBmaWVsZC4gIEluaXRpYWxpemVkIHRvIHplcm8gZm9yDQogICAgICAgICAgICAgICAgICAg
ICAgICB0cmFuc21pc3Npb247IGlnbm9yZWQgb24gcmVjZXB0aW9uLg0KDQogICBNIGZsYWcgICAg
ICAgICAgICAgICAxID0gbW9yZSBmcmFnbWVudHM7IDAgPSBsYXN0IGZyYWdtZW50Lg0KDQogICBJ
ZGVudGlmaWNhdGlvbiAgICAgICAzMiBiaXRzIGlzIHVzZWQgZm9yIGZhY2lsaXRhdGluZyBlYWNo
IGZyYWdtZW50IGlzIA0KICAgICAgICAgICAgICAgICAgICAgICAgY29ycmVjdGx5IHJlYXNzZW1i
bGVkIGF0IHRoZSByZWNlaXZlci4NCg0KICAgQW4gSVB2NiBmcmFnbWVudCBpcyBkZWZpbmVkIHRv
IGJlIGFuIElQdjYgcGFja2V0LCB3aGljaCBjb250YWlucyB0aGUgSVB2Ng0KICAgRnJhZ21lbnQg
aGVhZGVyIGFzIGRlc2NyaWJlZCBhYm92ZSwgaGF2aW5nIGVpdGhlciB0aGUgTW9yZSBmbGFnIG9y
IHRoZSANCiAgIEZyYWdtZW50IE9mZnNldCBzZXQgdG8gaGF2ZSBhIG5vbiAwIHZhbHVlLg0KDQoN
Cg0KDQpNYW5yYWwsIGV0IGFsLiAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjUsIDIwMDcgICAg
ICAgICAgICAgICAgICAgIFtQYWdlIDNdDQogDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAg
ICAgSVB2NiAgRnJhZ21lbnRzICAgICAgICAgICAgICAgICAgSnVuZSAyMDA3DQoNCg0KICAgSW4g
dHVybiBpZiBhbiBJUHY2IHBhY2tldCBjb250YWlucyBhIGZyYWdtZW50IGhlYWRlciwgd2l0aCBi
b3RoIHRoZSBNb3JlIA0KICAgZmxhZyBhcyB3ZWxsIGFzIHRoZSBGcmFnbWVudCBPZmZzZXQgZmll
bGRzIHNldCB0bywgaXQgaXMgdHJlYXRlZCBleGFjdGx5IA0KICAgbGlrZSBhbiBJUHY2IHBhY2tl
dCB3aXRob3V0IHRoZSBGcmFnbWVudCBoZWFkZXIuDQogICAgICANCg0KMy4gVGlueSBGcmFnbWVu
dHMgYW5kIGlzc3Vlcw0KDQogICBBbiBJUHY2IFRpbnkgRnJhZ21lbnQgaXMgZGVmaW5lZCBhcyBh
IG5vbi1sYXN0IGZyYWdtZW50IHdoaWNoIGhhcyBhIHBheWxvYWQNCiAgIGxlbmd0aCBvZiBsZXNz
IHRoYW4gMTIwMCBvY3RldHMuDQoNCiAgIEEgbG90IG9mIG1pZGRsZWJveGVzIChmaXJld2FsbHMv
IElEUyBhbmQgSVBTIGRldmljZXMpIGlkZW5maXR5IHNlc3Npb25zIGJhc2VkDQogICBvbiBhIDUt
dHVwbGUgb2YgU291cmNlIElQIGFkZHJlc3MsIERlc3RpbmF0aW9uIElQIEFkZHJlc3MsIFVwcGVy
IExheWVyIA0KICAgcHJvdG9jb2wsIGFuZCB0aGUgc291Y2UgYW5kIGRlc3RpbmF0aW9uIHBvcnRz
IG9mIHRoZSBwcm90b2NvbC4gU3VjaCANCiAgIGluZm9ybWF0aW9uIGlzIGF2YWlsYWJsZSBpbiB0
aGUgZmlyc3QgRnJhZ21lbnQgKEZyYWdtZW50IE9mZnNldCAwIGFuZCBNIGZsYWcNCiAgIGFzIDEp
LiBIb3dldmVyIGluIG9yZGVyIHRvIGJ5cGFzcyBjaGVja3MgaW4gbWlkZGxlYm94ZXMsIHNtYWxs
ZXIgZmlyc3QgDQogICBmcmFnbWVudHMgY2FuIGJlIHNlbnQuDQoNCiAgIFRoaXMgZG9jdW1lbnQg
c3BlY2lmaWVzIHRoZSBiZWhhdmlvciBvZiBhbnkgcm91dGVyIG9uIGVuY291bnRlcmluZyBhIFRp
bnkgDQogICBGcmFnbWVudC4gQSBUaW55IEZyYWdtZW50IHNob3VsZCBiZSB0cmVhdGVkIHRvIGhh
dmUgbWFsaWNpb3VzIGludGVudCBhbmQgU0hPVUxEDQogICBiZSBzaWxlbnRseSBkcm9wcGVkLiAN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQpNYW5yYWwsIGV0IGFsLiAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjUsIDIwMDcgICAgICAg
ICAgICAgICAgICAgIFtQYWdlIDRdDQogDQpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
SVB2NiAgRnJhZ21lbnRzICAgICAgICAgICAgICAgICAgSnVuZSAyMDA3DQoNCg0KDQoNCjQuICBJ
QU5BIENvbnNpZGVyYXRpb25zDQoNCiAgIFRoaXMgZG9jdW1lbnQgbWFrZXMgbm8gcmVxdWVzdCBv
ZiBJQU5BLg0KDQogICBOb3RlIHRvIFJGQyBFZGl0b3I6IHRoaXMgc2VjdGlvbiBtYXkgYmUgcmVt
b3ZlZCBvbiBwdWJsaWNhdGlvbiBhcyBhbg0KICAgUkZDLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KTWFucmFsLCBldCBhbC4gICAgICAgICBFeHBpcmVzIERlY2VtYmVy
IDI1LCAyMDA3ICAgICAgICAgICAgICAgICAgICBbUGFnZSA1XQ0KIA0KSW50ZXJuZXQtRHJhZnQg
ICAgICAgICAgICAgICAgIElQdjYgIEZyYWdtZW50cyAgICAgICAgICAgICAgICAgIEp1bmUgMjAw
Nw0KDQoNCg0KNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIFRoaXMgZHJhZnQgb3V0
bGluZXMgc2VjdXJpdHkgaXNzdWVzIGFyaXNpbmcgZnJvbSB0aGUgdXNlIG9mIHRpbnkgZnJhZ21l
bnRzLiANCiAgIEl0IGZ1cnRoZXIgY2xhcmlmaWVzIHRoZSBkZWZpbml0aW9uIG9mIGEgRnJhZ21l
bnQgSGVhZGVyLiBUaGlzIGRyYWZ0IGVuaGFuY2VzDQogICB0aGUgc2VjdXJpdHkgb2YgSVB2NiBu
ZXR3b3JrIGFuZCBoZWxwcyBwcmV2ZW50IGF0dGFja3MgY2F1c2VkIGJ5IHRpbnkgDQogICBmcmFn
bWVudHMgb3Igc3BlYyBhbWJpZ3VpdHkuDQoNCiAgIE5vIG5ldyBzZWN1cml0eSByZXF1aXJlbWVu
dHMgcmVzdWx0IGZyb20gc3VjaCBwcm9wb3NhbHMuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCk1hbnJhbCwgZXQgYWwuICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAyNSwgMjAw
NyAgICAgICAgICAgICAgICAgICAgW1BhZ2UgNl0NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAg
ICAgICAgICBJUHY2ICBGcmFnbWVudHMgICAgICAgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQoN
CjYuICBBY2tub3dsZWRnZW1lbnRzDQoNCg0KICAgVGhlIHN1YmplY3Qgb2YgdGhpcyBkcmFmdCBo
YXMgYmVlbiBkaXNjdXNzZWQgaW4gZGV0YWlsIGluIHRoZSBJUHY2IG1haWxpbmcgbGlzdC4NCiAg
IEVsd3luIERhdmllcywgU3VyZXNoIEtyaXNobmFuIHNwZWNpYWxseSBjb250cmlidXRlZCBpZGVh
cyB0byB0aGlzIGRyYWZ0Lg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpNYW5yYWwsIGV0IGFsLiAgICAgICAgIEV4cGly
ZXMgRGVjZW1iZXIgMjUsIDIwMDcgICAgICAgICAgICAgICAgICAgIFtQYWdlIDddDQogDQpJbnRl
cm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgSVB2NiAgRnJhZ21lbnRzICAgICAgICAgICAgICAg
ICAgSnVuZSAyMDA3DQoNCg0KDQo3LiAgUmVmZXJlbmNlcw0KDQo3LjEgIE5vcm1hdGl2ZSBSZWZl
cmVuY2VzDQoNCiAgIFtSRkMyMTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBp
biBSRkNzIHRvIEluZGljYXRlDQogICAgICAgICAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIEJD
UCAxNCwgUkZDIDIxMTksIE1hcmNoIDE5OTcuDQoNCiAgIFtSRkMyNDYwXSAgRGVlcmluZywgUy4g
YW5kIFIuIEhpbmRlbiwgIkludGVybmV0IFByb3RvY29sLCBWZXJzaW9uIDYNCiAgICAgICAgICAg
ICAgKElQdjYpIFNwZWNpZmljYXRpb24iLCBSRkMgMjQ2MCwgRGVjZW1iZXIgMTk5OC4NCg0KICAg
W1JGQzE3MDBdICBSZXlub2xkcyBKLiBhbmQgSi4gUG9zdGVsLCAiQXNzaWduZWQgTnVtYmVycyIs
IFJGQzE3MDAsIA0KICAgICAgICAgICAgICBPY3RvYmVyIDE5OTQNCg0KDQoNCjcuMiAgSW5mb3Jt
YXRpdmUgUmVmZXJlbmNlcw0KDQoNCiAgIFtJLUQubWFucmFsLXY2b3BzLXRpbnktZnJhZ21lbnRz
LWlzc3Vlcy0wMl0NCiAgICAgICAgICAgICAgTWFucmFsIFYuLCAiT3BlcmF0aW9uYWwgaXNzdWVz
IHdpdGggVGlueSBGcmFnbWVudHMgaW4gSVB2NiIsICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICh3b3JrIGluIHByb2dyZXNzKSwgSnVseSAyMDA2Lg0KDQogICBbUkZDMjc2NV0gTm9y
ZG1hcmsgRS4sICJTdGF0ZWxlc3MgSVAvSUNNUCBUcmFuc2xhdGlvbiBBbGdvcml0aG0gKFNJSVQp
IiwNCiAgICAgICAgICAgICBGZWJydWFyeSAyMDAwDQoNCiAgIFtSRkM0MzAyXSBLZW50IFMuLCAi
SVAgQXV0aGVudGljYXRpb24gSGVhZGVyIChBSCkiLCBSRkM0MzAyLCANCiAgICAgICAgICAgICAg
RGVjZW1iZXIgMjAwNQ0KDQogICBbUkZDNDMwM10gS2VudCBTLiwgIklQIEVuY2Fwc3VsYXRpbmcg
U2VjdXJpdHkgUGF5bG9hZCAoRVNQKSIsIFJGQzQzMDMsIA0KICAgICAgICAgICAgIERlY2VtYmVy
IDIwMDUNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KTWFucmFs
LCBldCBhbC4gICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDI1LCAyMDA3ICAgICAgICAgICAgICAg
ICAgICBbUGFnZSA4XQ0KIA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgIElQdjYgIEZy
YWdtZW50cyAgICAgICAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoNCg0KQ29udHJpYnV0b3JzIEFk
ZHJlc3MNCg0KDQoNCg0KQXV0aG9ycycgQWRkcmVzc2VzDQoNCiAgIFZpc2h3YXMgTWFucmFsDQog
ICBJUCBJbmZ1c2lvbg0KICAgQWxtb3JhLCBVdHRhcmFraGFuZA0KICAgSW5kaWENCg0KICAgUGhv
bmU6DQogICBGYXg6DQogICBFbWFpbDogdmlzaHdhc0BpcGluZnVzaW9uLmNvbQ0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCk1hbnJhbCwgZXQgYWwuICAgICAgICAgRXhwaXJlcyBEZWNlbWJlciAy
NSwgMjAwNyAgICAgICAgICAgICAgICAgICAgW1BhZ2UgOV0NCiANCkludGVybmV0LURyYWZ0ICAg
ICAgICAgICAgICAgICBJUHY2ICBGcmFnbWVudHMgICAgICAgICAgICAgICAgICBKdW5lIDIwMDcN
Cg0KDQoNCg0KSW50ZWxsZWN0dWFsIFByb3BlcnR5IFN0YXRlbWVudA0KDQogICBUaGUgSUVURiB0
YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZhbGlkaXR5IG9yIHNjb3BlIG9mIGFueQ0K
ICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IFJpZ2h0cyBvciBvdGhlciByaWdodHMgdGhhdCBtaWdo
dCBiZSBjbGFpbWVkIHRvDQogICBwZXJ0YWluIHRvIHRoZSBpbXBsZW1lbnRhdGlvbiBvciB1c2Ug
b2YgdGhlIHRlY2hub2xvZ3kgZGVzY3JpYmVkIGluDQogICB0aGlzIGRvY3VtZW50IG9yIHRoZSBl
eHRlbnQgdG8gd2hpY2ggYW55IGxpY2Vuc2UgdW5kZXIgc3VjaCByaWdodHMNCiAgIG1pZ2h0IG9y
IG1pZ2h0IG5vdCBiZSBhdmFpbGFibGU7IG5vciBkb2VzIGl0IHJlcHJlc2VudCB0aGF0IGl0IGhh
cw0KICAgbWFkZSBhbnkgaW5kZXBlbmRlbnQgZWZmb3J0IHRvIGlkZW50aWZ5IGFueSBzdWNoIHJp
Z2h0cy4gIEluZm9ybWF0aW9uDQogICBvbiB0aGUgcHJvY2VkdXJlcyB3aXRoIHJlc3BlY3QgdG8g
cmlnaHRzIGluIFJGQyBkb2N1bWVudHMgY2FuIGJlDQogICBmb3VuZCBpbiBCQ1AgNzggYW5kIEJD
UCA3OS4NCg0KICAgQ29waWVzIG9mIElQUiBkaXNjbG9zdXJlcyBtYWRlIHRvIHRoZSBJRVRGIFNl
Y3JldGFyaWF0IGFuZCBhbnkNCiAgIGFzc3VyYW5jZXMgb2YgbGljZW5zZXMgdG8gYmUgbWFkZSBh
dmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4NCiAgIGF0dGVtcHQgbWFkZSB0byBvYnRhaW4g
YSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVybWlzc2lvbiBmb3IgdGhlIHVzZSBvZg0KICAgc3VjaCBw
cm9wcmlldGFyeSByaWdodHMgYnkgaW1wbGVtZW50ZXJzIG9yIHVzZXJzIG9mIHRoaXMNCiAgIHNw
ZWNpZmljYXRpb24gY2FuIGJlIG9idGFpbmVkIGZyb20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVw
b3NpdG9yeSBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pcHIuDQoNCiAgIFRoZSBJRVRGIGlu
dml0ZXMgYW55IGludGVyZXN0ZWQgcGFydHkgdG8gYnJpbmcgdG8gaXRzIGF0dGVudGlvbiBhbnkN
CiAgIGNvcHlyaWdodHMsIHBhdGVudHMgb3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3RoZXIg
cHJvcHJpZXRhcnkNCiAgIHJpZ2h0cyB0aGF0IG1heSBjb3ZlciB0ZWNobm9sb2d5IHRoYXQgbWF5
IGJlIHJlcXVpcmVkIHRvIGltcGxlbWVudA0KICAgdGhpcyBzdGFuZGFyZC4gIFBsZWFzZSBhZGRy
ZXNzIHRoZSBpbmZvcm1hdGlvbiB0byB0aGUgSUVURiBhdA0KICAgaWV0Zi1pcHJAaWV0Zi5vcmcu
DQoNCg0KRGlzY2xhaW1lciBvZiBWYWxpZGl0eQ0KDQogICBUaGlzIGRvY3VtZW50IGFuZCB0aGUg
aW5mb3JtYXRpb24gY29udGFpbmVkIGhlcmVpbiBhcmUgcHJvdmlkZWQgb24gYW4NCiAgICJBUyBJ
UyIgYmFzaXMgYW5kIFRIRSBDT05UUklCVVRPUiwgVEhFIE9SR0FOSVpBVElPTiBIRS9TSEUgUkVQ
UkVTRU5UUw0KICAgT1IgSVMgU1BPTlNPUkVEIEJZIChJRiBBTlkpLCBUSEUgSU5URVJORVQgU09D
SUVUWSBBTkQgVEhFIElOVEVSTkVUDQogICBFTkdJTkVFUklORyBUQVNLIEZPUkNFIERJU0NMQUlN
IEFMTCBXQVJSQU5USUVTLCBFWFBSRVNTIE9SIElNUExJRUQsDQogICBJTkNMVURJTkcgQlVUIE5P
VCBMSU1JVEVEIFRPIEFOWSBXQVJSQU5UWSBUSEFUIFRIRSBVU0UgT0YgVEhFDQogICBJTkZPUk1B
VElPTiBIRVJFSU4gV0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJR0hUUyBPUiBBTlkgSU1QTElFRA0K
ICAgV0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkgT1IgRklUTkVTUyBGT1IgQSBQQVJUSUNV
TEFSIFBVUlBPU0UuDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KTWFu
cmFsLCBldCBhbC4gICAgICAgICBFeHBpcmVzIERlY2VtYmVyIDI1LCAyMDA3ICAgICAgICAgICAg
ICAgICAgICBbUGFnZSAxMF0NCiANCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICBJUHY2
ICBGcmFnbWVudHMgICAgICAgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQpGdWxsIENvcHlyaWdo
dCBTdGF0ZW1lbnQgDQogICAgDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJRVRGIFRydXN0ICgyMDA3
KS4gDQogICAgDQogICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gdGhlIHJpZ2h0cywgbGlj
ZW5zZXMgYW5kIHJlc3RyaWN0aW9ucyANCiAgIGNvbnRhaW5lZCBpbiBCQ1AgNzgsIGFuZCBleGNl
cHQgYXMgc2V0IGZvcnRoIHRoZXJlaW4sIHRoZSBhdXRob3JzIA0KICAgcmV0YWluIGFsbCB0aGVp
ciByaWdodHMuIA0KICAgIA0KICAgVGhpcyBkb2N1bWVudCBhbmQgdGhlIGluZm9ybWF0aW9uIGNv
bnRhaW5lZCBoZXJlaW4gYXJlIHByb3ZpZGVkIG9uIGFuIA0KICAgIkFTIElTIiBiYXNpcyBhbmQg
VEhFIENPTlRSSUJVVE9SLCBUSEUgT1JHQU5JWkFUSU9OIEhFL1NIRSBSRVBSRVNFTlRTIA0KICAg
T1IgSVMgU1BPTlNPUkVEIEJZIChJRiBBTlkpLCBUSEUgSU5URVJORVQgU09DSUVUWSwgVEhFIElF
VEYgVFJVU1QgQU5EIA0KICAgVEhFIElOVEVSTkVUIEVOR0lORUVSSU5HIFRBU0sgRk9SQ0UgRElT
Q0xBSU0gQUxMIFdBUlJBTlRJRVMsIEVYUFJFU1MgDQogICBPUiBJTVBMSUVELCBJTkNMVURJTkcg
QlVUIE5PVCBMSU1JVEVEIFRPIEFOWSBXQVJSQU5UWSBUSEFUIFRIRSBVU0UgT0YgDQogICBUSEUg
SU5GT1JNQVRJT04gSEVSRUlOIFdJTEwgTk9UIElORlJJTkdFIEFOWSBSSUdIVFMgT1IgQU5ZIElN
UExJRUQgDQogICBXQVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElUWSBPUiBGSVRORVNTIEZPUiBB
IFBBUlRJQ1VMQVIgUFVSUE9TRS4gDQogICAgDQpJbnRlbGxlY3R1YWwgUHJvcGVydHkgDQogICAg
DQogICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZhbGlkaXR5IG9y
IHNjb3BlIG9mIGFueSANCiAgIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMgb3Igb3RoZXIg
cmlnaHRzIHRoYXQgbWlnaHQgYmUgY2xhaW1lZCANCiAgIHRvIHBlcnRhaW4gdG8gdGhlIGltcGxl
bWVudGF0aW9uIG9yIHVzZSBvZiB0aGUgdGVjaG5vbG9neSBkZXNjcmliZWQgDQogICBpbiB0aGlz
IGRvY3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55IGxpY2Vuc2UgdW5kZXIgc3VjaCBy
aWdodHMgDQogICBtaWdodCBvciBtaWdodCBub3QgYmUgYXZhaWxhYmxlOyBub3IgZG9lcyBpdCBy
ZXByZXNlbnQgdGhhdCBpdCBoYXMgDQogICBtYWRlIGFueSBpbmRlcGVuZGVudCBlZmZvcnQgdG8g
aWRlbnRpZnkgYW55IHN1Y2ggcmlnaHRzLiAgSW5mb3JtYXRpb24gDQogICBvbiB0aGUgcHJvY2Vk
dXJlcyB3aXRoIHJlc3BlY3QgdG8gcmlnaHRzIGluIFJGQyBkb2N1bWVudHMgY2FuIGJlIA0KICAg
Zm91bmQgaW4gQkNQIDc4IGFuZCBCQ1AgNzkuIA0KICAgIA0KICAgQ29waWVzIG9mIElQUiBkaXNj
bG9zdXJlcyBtYWRlIHRvIHRoZSBJRVRGIFNlY3JldGFyaWF0IGFuZCBhbnkgICANCiAgIGFzc3Vy
YW5jZXMgb2YgbGljZW5zZXMgdG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2Yg
YW4gICANCiAgIGF0dGVtcHQgbWFkZSB0byBvYnRhaW4gYSBnZW5lcmFsIGxpY2Vuc2Ugb3IgcGVy
bWlzc2lvbiBmb3IgdGhlIHVzZSAgIA0KICAgb2Ygc3VjaCBwcm9wcmlldGFyeSByaWdodHMgYnkg
aW1wbGVtZW50ZXJzIG9yIHVzZXJzIG9mIHRoaXMgICANCiAgIHNwZWNpZmljYXRpb24gY2FuIGJl
IG9idGFpbmVkIGZyb20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSAgIA0KICAgYXQg
aHR0cDovL3d3dy5pZXRmLm9yZy9pcHIuIA0KICAgIA0KICAgVGhlIElFVEYgaW52aXRlcyBhbnkg
aW50ZXJlc3RlZCBwYXJ0eSB0byBicmluZyB0byBpdHMgYXR0ZW50aW9uIGFueSANCiAgIGNvcHly
aWdodHMsIHBhdGVudHMgb3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3RoZXIgcHJvcHJpZXRh
cnkgDQogICByaWdodHMgdGhhdCBtYXkgY292ZXIgdGVjaG5vbG9neSB0aGF0IG1heSBiZSByZXF1
aXJlZCB0byBpbXBsZW1lbnQgDQogICB0aGlzIHN0YW5kYXJkLiAgUGxlYXNlIGFkZHJlc3MgdGhl
IGluZm9ybWF0aW9uIHRvIHRoZSBJRVRGIGF0IGlldGYtDQogICBpcHJAaWV0Zi5vcmcuIA0KDQoN
Cg0KDQoNCg0KDQpNYW5yYWwsIGV0IGFsLiAgICAgICAgIEV4cGlyZXMgRGVjZW1iZXIgMjUsIDIw
MDcgICAgICAgICAgICAgICAgICAgIFtQYWdlIDExXQ0KDQoNCg0KDQoNCg0KDQo=
------=_Part_8549_11239776.1182800381657
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

------=_Part_8549_11239776.1182800381657--




From ipv6-bounces@ietf.org Mon Jun 25 16:08:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2uqw-0004Aq-1F; Mon, 25 Jun 2007 16:08:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2uqu-0004Ai-My
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:08:00 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uqt-00035e-73
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:08:00 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 9933D347D2;
	Mon, 25 Jun 2007 16:07:56 -0400 (EDT)
Received: from [16.116.113.226] (galen.zko.hp.com [16.116.113.226])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 06F7C18B8EF;
	Mon, 25 Jun 2007 20:07:55 +0000 (UTC)
Message-ID: <4680209B.7050608@hp.com>
Date: Mon, 25 Jun 2007 16:07:55 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0706221222j362009c9wa92eb58c3c029ab@mail.gmail.com>	
	<467C34B8.20801@ericsson.com>	
	<77ead0ec0706221400q279c6097r7b5d22922645638a@mail.gmail.com>	
	<467FFD45.7010107@hp.com>
	<77ead0ec0706251239o19a6cd6cy64b6eece094cc03d@mail.gmail.com>
In-Reply-To: <77ead0ec0706251239o19a6cd6cy64b6eece094cc03d@mail.gmail.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: What is an IPv6 fragment?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Vishwas

I think you are reading too much into this, thus the issue is confused.

Vishwas Manral wrote:
> Hi Vlad,
> 
> Thanks a lot for your clarification, maybe I am unclear. I am
> attaching a document I have attached, just have a look.
> 
>> First, this only happens when the IPv4 host does not support path mtu
>> discovery (DF bit is 0).  In this case, inserting a fragment header
>> at the translator in essence performs the fragmentation that was
>> requested by the sender.  I just so happens that in this case the
>> fragment might have offset and M flag set to 0.
> There are 2 sides of the problem. The first is that different
> protocols use different definition of a fragment, which needs to be
> clarified, because some assumption by a protocol may not work in many
> cases due to the specification clarity. The second part is the use of
> different policies for fragments.
> 
> The idea I am stating is that one spec uses the Fragment header to
> just signal its ability to perform fragmentation,

No, it does in fact fragment the packets.  It just so happens that it may
result in a single fragment. The behavior here is not much different from
some node on path returning ICMP Too Big with MTU less the 1280.

The fragment is there to make translators work so that the translation
of the DF bit is not lost while the IPv4 packet is traversing an IPv6
network.

> while others
> specs(AH & ESP for one) clearly lay down a differnet way for
> identifying an IPv6 fragment and its subsequent treatment. As there
> are different policies for fragments, the signaling may not work in
> many cases(no I am not talking about policies but the clarification of
> the term Fragment - example a Fragment with M = 0 and Offset = 0
> should be treated as a non fragmented packet). I do not see any
> problem  in clarifying exactly what an IPv6 fragment is so that we can
> have a consistent set of specs as well as implementations.
> 
>> Now you are getting in policies outside of the definition.  The
>> definition
>> does not have to encompass all eventual uses.  Otherwise we'll be
>> updating
>> a lot more specs.
> No, I am talking about specs too besides practical network scenarios.
> If we see a problem in a spec I do not see a reason we should hesitate
> in fixing the problems (and its not unprecedented either).

Ok, so are you concerned with what IPSec considers a fragment and how
individual IPSec policies treat those fragments?

> 
> 2. IPv6 Fragment
> 
>    The IPv6 specification [RFC2460] defines a fragment header as:
> 
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |  Next Header  |   Reserved    |      Fragment Offset    |Res|M|
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                         Identification                        |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>    Next Header          8-bit selector.  Identifies the initial header
>                         type of the Fragmentable Part of the original
>                         packet (defined below).  Uses the same values as
>                         the IPv4 Protocol field [RFC-1700 et seq.].
> 
>    Reserved             8-bit reserved field.  Initialized to zero for
>                         transmission; ignored on reception.
> 
>    Fragment Offset      13-bit unsigned integer.  The offset, in 8-octet
>                         units, of the data following this header,
>                         relative to the start of the Fragmentable Part
>                         of the original packet.
> 
>    Res                  2-bit reserved field.  Initialized to zero for
>                         transmission; ignored on reception.
> 
>    M flag               1 = more fragments; 0 = last fragment.
> 
>    Identification       32 bits is used for facilitating each fragment is 
>                         correctly reassembled at the receiver.
> 
>    An IPv6 fragment is defined to be an IPv6 packet, which contains the IPv6
>    Fragment header as described above, having either the More flag or the 
>    Fragment Offset set to have a non 0 value.

Well, that's not quite right, since the middle fragments will have both
a non-zero offset and More flag set.

What the statement from you draft implies is that one or the other may be omitted,
which is not the case.

> 
> 
> 
> 
> Manral, et al.         Expires December 25, 2007                    [Page 3]
>  
> Internet-Draft                 IPv6  Fragments                  June 2007
> 
> 
>    In turn if an IPv6 packet contains a fragment header, with both the More 
>    flag as well as the Fragment Offset fields set to, it is treated exactly 
>    like an IPv6 packet without the Fragment header.

This seems like a clarification that might be useful.

-vlad

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 16:16:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2uzO-00064j-T8; Mon, 25 Jun 2007 16:16:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2uzM-00064T-94
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:16:44 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uzK-0007XB-S1
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:16:44 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 25 Jun 2007 16:16:34 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANa/f0ZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,460,1175486400"; 
	d="scan'208"; a="124511580:sNHT82413496"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5PKGYTn014494; 
	Mon, 25 Jun 2007 16:16:34 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5PKGNLt011683; 
	Mon, 25 Jun 2007 20:16:32 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 16:16:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 16:16:29 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2645chx46.wl%jinmei@wide.ad.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace3PYOcktSNOWKfTnaNX8ZysZ7ZNwAFVymQ
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 25 Jun 2007 20:16:24.0151 (UTC)
	FILETIME=[B3EBE670:01C7B765]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4631; t=1182802594;
	x=1183666594; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=8jlQSNXPhMz0nQ4zxiIHap5OvBjcHARLz5F3xMt8tns=;
	b=HQxeKIXLrpmdDnZGRf0tfeo2YZ6jvF6EgWhK2AB47KBjLdDgCg3fVYpNHJPNMKB6jLC6CYsa
	PlZwWtQ3Ou6cBBkPjJgdko2NiswimTnn0un5GLxD2fexgP2NQp5wCnea;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Tatuya,

Please see in line below with "<hs>".=20

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Monday, June 25, 2007 11:28 AM
To: Hemant Singh (shemant)
Cc: Brian E Carpenter; Fred Baker (fred); ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

At Mon, 25 Jun 2007 10:45:35 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Let us summarize the discussion that has taken place so far and issues

> closed.
>=20
> 1. Technical content - Brian has agreed below that the problem we=20
> describe is real and we are saying our recommendation to change=20
> 2462bis I-D does fix this problem. Tatuya still has some issues with=20
> our problem, but we think till he fixes some typos in his email we=20
> cannot reply to him. This is what was sent from Tatuya that we think=20
> is text with typos:
>=20
> "First, it is not clear which "security problem" this bullet tries to=20
> indicate.  Also, if Host1 is assumed to be the attacker that mounts=20
> traffic hijacking and/or DoS against Host2, forcing Host2 to perform=20
> DAD doesn't help because Host1 can get the same result by simply=20
> ignoring the DAD-NS from Host1."

Yeah, there was a typo.  It should actually be:

First, it is not clear which "security problem" this bullet tries to
indicate.=20

<hs>  The problem we refer to is the fact that Host1 and Host2 have the
same GUA on the same link! This is an obvious problem because Host1 is
able to get an authoritative (because Host1 issued an unchallenged DAD
for GUA) GUA that is also later assigned to Host2. Note that Host1 does
not need an incorrectly implemented or hacked up IPv6 stack to reach
this problem scenario - the problem arises with a fully compliant IPv6
host stack on Host1 and Host2 using only the interface exported to an
end user. If Host2 was NOT allowed to skip DAD, then Host2 will issue a
NS(DAD) for GUA and Host1 being a compliant host would reply with an NA
saying "I have this GUA". The net result is that traffic that should
have gone to Host2, goes to Host1 instead - why is this not a security
problem?

Also, if Host1 is assumed to be the attacker that mounts traffic
hijacking and/or DoS against Host2, forcing Host2 to perform DAD doesn't
help because Host1 can get the same result by simply ignoring the DAD-NS
from Host2.
(i.e., replace the final "Host1" with "Host2")

<hs> The second problem case, when Host1 is a rogue and not compliant
with IPv6 standards, sure Host1 can ignore the DAD-NS from Host2 but the
IPv6 router on the link MAY catch this duplicate since the router has
also seen this NS(DAD).  We envision that the router logs an error
message. Again, in our previous case above, if Host2 had skipped NS(DAD)
then the router would not catch this problem.=20

> Tatuya also needs to explain how ignoring DAD from a host is a valid=20
> implementation of the 2462 standards.

Why should I?  I interpreted the bullet as describing Host1 was an
attacker, so it would do anything (whether it's valid or not wrt
standards) to make the attack succeed.

<hs> OK, now that we read your reply with the typo fixed, we agree with
you here. It's because Host1 is a rogue, this host will ignore the
NS(DAD) from Host2 for GUA.

In any event, the main point is that it's not clear (to me) which
"security problem" this draft tries to explain (and how the change in
the specification helps solve or mitigate the "problem").

> Well, if stacks do not skip DAD, then there should be no problem with=20
> tightening up the language as we've proposed.

I'd rather say that *if* stacks do not skip DAD, then there should be no
problem with leaving the current text as is (remember new
implementations won't skip DAD, so leaving the text won't cause a
problem in the future either).  And if so, I'd rather keep it since I
don't see any value in modifying text that has been fully reviewed and
does not actually have any problem.

<hs> Do you acknowledge the problem we describe above?  Since we realize
that 2462bis I-D is in AUTH48 state, a change like this may require
IETF-wide review and that would further delay 2462bis becoming an RFC.
But then where do we put changes like ours?  Our I-D is at the beginning
of the process, so it may be an appropriate place for this and any
further changes if they can't make it into 2462bis.

A note to the IPv6 WG chairs.  Please add our I-D to the agenda for the
July IETF meeting.

Thanks,

Hemant and Wes

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 16:21:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2v3f-0003PE-9g; Mon, 25 Jun 2007 16:21:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2v3d-0003LK-Ly
	for ipv6@ietf.org; Mon, 25 Jun 2007 16:21:09 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2uaW-0004CB-FI
	for ipv6@ietf.org; Mon, 25 Jun 2007 15:51:06 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5PJp2go014093
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 25 Jun 2007 12:51:03 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5PJp29r012887; Mon, 25 Jun 2007 12:51:02 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5PJoqT0012535; Mon, 25 Jun 2007 12:51:01 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 12:50:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 12:50:56 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8BC@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <467FF6AA.5000604@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace3S4gPtiDbPsJFRQOifo3bCzbJfgAAXqjQ
References: <200706221709.l5MH9uEN003458@mail.reprise.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com><467C1F53.9070600@spaghetti.zurich.ibm.com><20070622195429.GG31273@elvis.mu.org><467C2EE6.3070100@spaghetti.zurich.ibm.com><20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<467FF6AA.5000604@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>
X-OriginalArrivalTime: 25 Jun 2007 19:50:57.0828 (UTC)
	FILETIME=[26297E40:01C7B762]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8
Cc: ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen,

I don't quite understand some of your points, so I am
not going to try to make conjectures about those. But,
I will respond to what I can below:=20

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]=20
> Sent: Monday, June 25, 2007 10:09 AM
> To: Templin, Fred L
> Cc: bill fumerola; ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> Templin, Fred L wrote:
> [..]
>=20
> >> Thus you are connecting to the Internet, using IPv4 or IPv6 doesn't
> >> matter, you have a dependency on the Internet. As such you are not
> >> working dis-connected from the Internet and you have a=20
> >> dependency on it.
> >=20
> > Only when you want to connect to another site.
>=20
> Thus the moment you are connecting to another site you are forcing one
> to also connect to the Internet.

The way I envision for a site to connect to another site
is via establishing one or more links between the two sites.
Having the two sites come in physical proximity with each
other (e.g., due to mobility) is one way. Establishing
tunnels between them across the Internet is another way.
 =20
> [..]
> > Again, *no* NAT'ing of IPv6.
>=20
> How are you going to use ULA-C addresses as a source and then=20
> connect to
>  hosts on the global Internet?

Not what I am proposing, and not desirable. ULA-C addresses
as source may not be compatible with global IPv6 addresses
as destination. Isn't that what source address selection
is for? I will say again that I do not support IPv6 NAT.
=20
> [..]
> > A laptop fits this description. Think of one running some
> > of this new virtualization support whereby there may be
> > many virtual machines connected up by virtual networks
> > running within the laptop. (Actually, folks like IBM were
> > doing this "new" virtualization on their mainframes back
> > in the 70's...)=20
>=20
> I have one of those sweet laptops and I have 3 OS's running=20
> at the same
> time most of the time. I use RFC1918 and simply randomly picked
> 172.17.123.0/24 which has (upto now :) never collided with=20
> the networks
> that I visited. ULA (RFC4193) would have that same property. I have to
> note that I have to NAT that address space to the network I am at, who
> only give me 1 single IP address most of the time (could use bridging
> and prolly ask for more addresses per DHCP of course). Having=20
> them route
> my prefix to me though everytime I walk into a Starbucks or a=20
> hotel etc
> is really never ever going to happen. There is no "this is my prefix
> route my traffic here" protocol (at least yet). Also no single network
> operator will ever accept such a protocol as it is their network, not
> that of the visitor to control. Viruses and {cr|h}ackers=20
> would love it I
> guess.

Having my laptop inject its ULA(-C) prefix into a visited
network's IGP seems like one alternative, and I have not
investigated the various interactions you are describing.
But, injecting the prefix may not be the only alternative
and maybe not even be the best one.

> When you are in the position to negotiate the routing part,=20
> then having
> them turn up DNS, which has to happen for both forward (how else are
> they going to locate your host) and reverse hosts is very doable.
> This then nullifies the whole requirement of having NS=20
> pointers to your
> servers, which have to have internet-connected and static addresses
> unless you want to update them all the time, which for sure makes the
> RIR happy who definitely want to have more cash then for doing that.

This is one part that I didn't understand very well.
=20
> Or are your requiring sites you visit to have Internet connectivity as
> you only have your servers (forward + reverse) on the Internet?

Nor this.
=20
> >> this can
> >> mean indeed a major corporation (who maybe even require=20
> multiple /48's
> >> which is why rfc4193 is a bit off to cover those cases)
> >>
> >> If you want to have a /48 for your laptop, simply use ULA (RFC4193)
> >> those are free.
> >=20
> > RFC4193 ULA is good, but could be better. However remote the
> > possibility of collisions, IMHO there would still be value in
> > having a 3rd-party mechanism to avoid duplicate assignments
> > and/or de-conflict duplicates.  =20
>=20
> It exists: PI space. Get it at ARIN today: $100/year
>=20
> Which if you have such a high reliability requirement for=20
> non-clashes is
> very cheap and gives you the possibility to do reverse DNS and even
> route it on the global internet, just in case they provide you with
> transit at the site you happen to come along.

I don't know enough about ARIN/PI to know who can get it, how
much it costs, how filters could be configured to recognize it,
etc. to be able to comment. Pretty much everything I know about
it I am learning through your posts, but my off-the-cuff take
is "seems too expensive for small sites".=20

> >> Or are you simply wanting to have your own IP=20
> >> addresses,
> >> setting up firewalling etc because you have a laptop (or Winnebago
> >> filled with servers) and carrying it around globally=20
> through various
> >> buildings and making other networks accept your /48 AND=20
> force them to
> >> connect to the Internet to be able to resolve your reverse?
> >=20
> > I don't quite understand this, but I want to be able to
> > drop my laptop down in whatever visited network and have
> > it connect to other sites w/o having to manually configure
> > explicit VPNs.=20
>=20
> How are you 'automatically' telling the network to route packets for
> 'your prefix' to your device? See above.

It doesn't have to be through prefix injection into an IGP
of the visited network as long as there is a means to set
up an edge-to-edge tunnel between my laptop and the site I
want to connect to.
=20
> >> Most likely anyway when you connect your laptop to another=20
> site they
> >> will be providing you with an IP address anyway from their=20
> >> site prefix.
> >=20
> > One use I could see for that is if you needed a care-of
> > address such as used for MIPv6.
>=20
> Care-of-addresses are simply the address you get per DHCP/RA.
>=20
> > But, that gets off onto a completely different line of discussion.
>=20
> It also has nothing to do with connecting to sites.

I was just responding to your assertion that obtaining a
topologically-correct address from the visited network
was "most likely" going to happen - I was only postulating
about one reason as to why that might be so.
=20
> >> Can you clarify the use case you are sketching here a lot more as I
> >> really want to know what actual use case is actually=20
> useful that ULA-C
> >> solves, what PI doesn't solve (Drawings + text help).=20
> Especially now
> >> that the folks who 'want/need' ULA-C do want to have reverse DNS
> >> available from the Internet, while they want to be local in=20
> >> the first place.
> >=20
> > I already gave my use-case in:
> >=20
> > http://www1.ietf.org/mail-archive/web/ipv6/current/msg07806.html
>=20
> As I mentioned above, how are the routing protocols "automatically"
> trusting that you own the prefix, or for that matter finding=20
> each other
> in the first place. This will involve a protocol that can handle this.
> When such a protocol exists you can also have it handle your=20
> reverse DNS
> setup.

Edge-to-edge tunnels between sites is perhaps one way to
avoid prefix injection in the visited network.
=20
> I fully agree that there is a need for "Unique Addresses", and these
> exist already, it is called: PI.
>=20
> >> All those cases can be covered perfectly fine by PI. Or is it=20
> >> just that
> >> folks see ULA-C as 'very cheap PI space'?
> >=20
> > Again, I don't know about other folks but for me I see the
> > price as too high for some "sites" to have to pay.
>=20
> Thus the only reason for ULA-C seems to be that PI is "too expensive".
> Folks are always forgetting that there is a need for a lot of other
> things which are way more expensive than that: the actual=20
> hardware being
> used, power, maintenance, people being payed etc etc etc.
>=20
> Why would the IETF have to solve the problem of having "expensive
> address space" for the few who simply want it for free, by providing
> address space which is only cheaper, but for the rest exactly the same
> as existing solutions and in the long run will only cause=20
> people to use
> it on the global Internet and thus becoming a cost factor to=20
> everybody?
>=20
> Is 2^-40 probability really not enough for those sites? If they can't
> cough up $100/year, then they most likely don't have a lot of hosts
> actually involved and thus renumbering in the case of a=20
> collision of ULA
> (RFC4193) can't be that high either. If the probability is=20
> too high for
> them and the cost of renumbering is too high then PI for $100/year is
> suddenly really cheap. As such, sorry, but I don't see any=20
> problem that
> ULA-C will solve. I do see the problems that it will cause in=20
> the long run.

I can only represent my use-case in terms of why someone might
want ULA-C; others would have to represent theirs. The only
question I see is the source address selection so as to avoid
IPv6 NAT'ing. Then again, if all your site ever does is to
connect up to other sites with edge-to-edge tunnels then there
should be no interactions between its ULAs and the DFZ.

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 19:35:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2y5e-00083J-J3; Mon, 25 Jun 2007 19:35:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2y5c-000833-4L
	for ipv6@ietf.org; Mon, 25 Jun 2007 19:35:24 -0400
Received: from mx.isc.org ([204.152.184.167])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I2y5Z-0005QR-JL
	for ipv6@ietf.org; Mon, 25 Jun 2007 19:35:24 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id AB24B11402A
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 23:35:20 +0000 (UTC)
	(envelope-from Mark_Andrews@isc.org)
Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "drugs.dv.isc.org", Issuer "ISC CA" (verified OK))
	by farside.isc.org (Postfix) with ESMTP id 262D3E6098
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 23:35:19 +0000 (UTC)
	(envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5PNZAPP096776;
	Tue, 26 Jun 2007 09:35:11 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706252335.l5PNZAPP096776@drugs.dv.isc.org>
To: Jeroen Massar <jeroen@unfix.org>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Mon, 25 Jun 2007 16:26:34 +0100."
	<467FDEAA.1020503@spaghetti.zurich.ibm.com> 
Date: Tue, 26 Jun 2007 09:35:10 +1000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> Templin, Fred L wrote:
> > Jeroen,
> >=20
> > Touching on just one aspect of your thoughtul post:
> >=20
> >>> DNS is an integral part of addressing and if
> >>> we're going to move forward with ULA-C as delegated=20
> >> addressing then let
> >>> us move forward with addressing in its entirety.
> >> So you want a disconnected address space which gets connected to the
> >> Internet? Sorry, but that more or less really implies NAT.
> >=20
> > I wouldn't call it a "disconnected address space which gets
> > connected to the Internet" but rather a "unique local address
> > space which gets connected to other unique local address
> > spaces" and IMHO I don't see any implication for NAT there.
> 
> If you are only connecting to another ULA network, then why would one
> ever need NS entries in ip6.arpa for this space?

	Because sites will have *both* ULA-C and ordinary addresses.
	These sites may have private interconnects either due to
	bussiness needs or mergers or ...

	Because globally connected sites will see these addresses
	in logs, received headers etc.  Queries for these addresses will
	be made from sites without reachabilty to these addresses.

	Then there is what do we do with all the reverse queries coming
	from sites that have failed to intercept the reverse queries.

> The whole story is about having NS entries in the ip6.arpa tree for the
> delegation. When you have a delegation in the Internet ip6.arpa tree,
> you also need to query them one way or the other and thus you are
> connecting your ULA-based network to that Internet.

	Not necessarially.  Full disconnected sites will just maintain
	their own C.F.IP6.ARPA registry.
 
> Also, people will the notice that they can use reverses from the
> Internet, at one point or another will also want to use SIP or various
> other protocols and thus end up using the Internet, and there are two
> ways to do that: NAT it or simply announce the ULA prefix, renumbering
> to a PI block is of course not an option here.

	Why are you assuming a IPv4 solution to a IPv6 problem.  If you
	have global reachability you will have global addresses.

	The anwer to how to talk to the Internet is to use a address with
	global scope.
 
> As such, what is the 'local' part again, how local is it really? And how
> is ULA-C then different from PI? Why bother people with this ULA-C thing
> when they really need PI in the first place? Which they can already get
> for $100/year from ARIN and which will be guaranteed unique, just like
> all other address space from the RIR's.
> 
> Greets,
>  Jeroen
> 
> 
> 
> --------------enigA4239CC2518F4B232378ACE5
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: OpenPGP digital signature
> Content-Disposition: attachment; filename="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Jeroen Massar / http://unfix.org/~jeroen/
> 
> iHUEARECADUFAkZ/3q4uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
> b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I+i9AJwLWj1LkB4GArEMWLj9WI+6jf8V
> rgCgpOKskF+TzmhR+6NMycHte3Cq6os=
> =V6C5
> -----END PGP SIGNATURE-----
> 
> --------------enigA4239CC2518F4B232378ACE5--
> 
> 
> --===============0375020143==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --===============0375020143==--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 20:00:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2yTD-0000QK-BC; Mon, 25 Jun 2007 19:59:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2yTB-0000QF-Qi
	for ipv6@ietf.org; Mon, 25 Jun 2007 19:59:45 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2yTB-0004mW-3W
	for ipv6@ietf.org; Mon, 25 Jun 2007 19:59:45 -0400
Received: from [203.10.60.4] (dhcp4.potaroo.net [203.10.60.4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id D6E0ED5F34;
	Tue, 26 Jun 2007 09:59:43 +1000 (EST)
Message-ID: <46805763.6040708@apnic.net>
Date: Tue, 26 Jun 2007 10:01:39 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
In-Reply-To: <E727B713-793C-49E5-A15A-58334396573B@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



james woodyatt wrote:
> On Jun 25, 2007, at 09:33, Templin, Fred L wrote:
>>
>> I already gave my use-case in:
>>
>> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07806.html
>>>
>>> The use-case I am most interested in is Mobile Ad-Hoc Networks 
>>> (MANETs) in which two or more MANETs can merge (e.g., due to 
>>> mobility). If each MANET used ULA-C's, then they could inject each 
>>> others' prefixes into their IGPs with no opportunity for collision. 
>>> If each MANET instead used RFC4193 ULAs, then they could *probably* 
>>> still inject each others' prefixes. But, however small the risk of 
>>> collision, RFC4193 ULAs still have one drawback that ULA-C's do not - 
>>> uncertainty.
>>>
>>> So perhaps another question is whether it is too much to ask for more 
>>> certainty (ULA-C) and less mystery (RFC4193 ULA)?
> 
> The "no opportunity for collision" thing is really the question here, as 
> Brian E. Carpenter said in 
> <http://www1.ietf.org/mail-archive/web/ipv6/current/msg07834.html> and 
> others have said elsewhere.  Most of the pushback is directed at this 
> claim that central registration has some hope for mitigating an already 
> *epsilon* risk of collision.  I don't think simply reiterating the claim 
> is an appropriate response to the legitimate rebuttal it's received.

Depends on what level of "collision risk" you are happy with, and this 
depends on the scenario where you are assessing that risk.

- you pick a number from a pool, I pick a number from a pool, then we 
compare numbers - chance of collision = 1 / pool size

- a set of us pick numbers from a pool, and we compare numbers. The 
probability that two or us have picked the same number is the case where 
  a random draw function exceeds 0.5  after 1.24 million random draws. 
The general solution of the probability of a collision after d draws 
from n possible values is given by:

       P = 1 - ((n!) / ((n**d)((n-d)!)))

Given that the value for n here is 2.199,023,255,552, then the objective
is to find the lowest value of d for which P is greater than or equal
to 0.5. In this case the value for d  is some 1.24 million.

i.e. if we all pick numbers and stuff them into the DNS, then by the 
time the 1,240,000 selection had taken place the probability that a 
collision has occurred exceeds 0.5

regards,

     Geoff

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 20:36:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2z2n-0002Ma-Tg; Mon, 25 Jun 2007 20:36:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2z2m-0002MV-NL
	for ipv6@ietf.org; Mon, 25 Jun 2007 20:36:32 -0400
Received: from 69-30-97-91.dv1mn.easystreet.com ([69.30.97.91]
	helo=reprise.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I2z2l-0005W6-9b
	for ipv6@ietf.org; Mon, 25 Jun 2007 20:36:32 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l5Q0aTor064583
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 17:36:29 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l5Q0aToK064580;
	Mon, 25 Jun 2007 17:36:29 -0700 (PDT) (envelope-from george)
Date: Mon, 25 Jun 2007 17:36:29 -0700 (PDT)
Message-Id: <200706260036.l5Q0aToK064580@mail.reprise.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -3.977 () ALL_TRUSTED,AWL,BAYES_00
X-Scanned-By: MIMEDefang 2.57 on 69.30.97.91
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Depends on what level of "collision risk" you are happy with, and this 
> depends on the scenario where you are assessing that risk.
>
> [...]
>
> - a set of us pick numbers from a pool, and we compare numbers. The 
> probability that two or us have picked the same number is the case where 
>   a random draw function exceeds 0.5  after 1.24 million random draws. 
> The general solution of the probability of a collision after d draws 
> from n possible values is given by:
>
>        P = 1 - ((n!) / ((n**d)((n-d)!)))
>
> Given that the value for n here is 2.199,023,255,552, then the objective
> is to find the lowest value of d for which P is greater than or equal
> to 0.5. In this case the value for d  is some 1.24 million.
>
> i.e. if we all pick numbers and stuff them into the DNS, then by the 
> time the 1,240,000 selection had taken place the probability that a 
> collision has occurred exceeds 0.5

It's not a collision until two of those systems connect together.
-- George Mitchell

> regards,
>
>      Geoff


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 21:07:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2zWZ-0006Ta-JS; Mon, 25 Jun 2007 21:07:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2zWX-0006TN-Rv
	for ipv6@ietf.org; Mon, 25 Jun 2007 21:07:17 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2zWW-0007j8-JI
	for ipv6@ietf.org; Mon, 25 Jun 2007 21:07:17 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id EFF61A3C634
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 18:07:15 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id DD1DA29C002
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 18:07:15 -0700 (PDT)
X-AuditID: 11807123-a481fbb000000a55-91-468066c3a0f2
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id CE8A330400B
	for <ipv6@ietf.org>; Mon, 25 Jun 2007 18:07:15 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46805763.6040708@apnic.net>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 25 Jun 2007 18:07:13 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 25, 2007, at 17:01, Geoff Huston wrote:
>
> i.e. if we all pick numbers and stuff them into the DNS, then by  
> the time the 1,240,000 selection had taken place the probability  
> that a collision has occurred exceeds 0.5

That's only a problem for people who have to pick a number that  
collides with absolutely none of the other 1,240,000 numbers.  I  
think no one will ever have to do that, and *moreover* I think that  
anybody who *does* think they'll have to do that has some explaining  
to do before we worry about their problem.

Who's going to do that, and why?  By the way, that is *NOT* a  
rhetorical question.  I really want to know the answer.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 21:59:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I30Kp-0001FU-Bg; Mon, 25 Jun 2007 21:59:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I30Ko-0001Dj-Ce
	for ipv6@ietf.org; Mon, 25 Jun 2007 21:59:14 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I30Km-0004fw-A6
	for ipv6@ietf.org; Mon, 25 Jun 2007 21:59:14 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l5Q1whjS029883
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 25 Jun 2007 18:58:43 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l5Q1whZn029881;
	Mon, 25 Jun 2007 18:58:43 -0700 (PDT)
Date: Mon, 25 Jun 2007 18:58:43 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Geoff Huston <gih@apnic.net>
Message-ID: <20070626015843.GA28484@boreas.isi.edu>
References: <467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46805763.6040708@apnic.net>
User-Agent: Mutt/1.4.2.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> - a set of us pick numbers from a pool, and we compare numbers. The 
> probability that two or us have picked the same number is the case where 
>  a random draw function exceeds 0.5  after 1.24 million random draws. 
> The general solution of the probability of a collision after d draws 
> from n possible values is given by:
> 
>       P = 1 - ((n!) / ((n**d)((n-d)!)))
> 
> Given that the value for n here is 2.199,023,255,552, then the objective
> is to find the lowest value of d for which P is greater than or equal
> to 0.5. In this case the value for d  is some 1.24 million.

	and this is based on a true random selection, yes?
	and we KNOW that humans are good at selecting truely
	random numbers. e.g.  "whats your favorite number between
	1 and 2,199,023,255,552? ...  that would be 42."

 
> i.e. if we all pick numbers and stuff them into the DNS, then by the 
> time the 1,240,000 selection had taken place the probability that a 
> collision has occurred exceeds 0.5

	to Geo... the collision occurs at the point of intersection,
	be it when these sites interconnect or when they share a common
	namespace.

> regards,
> 
>     Geoff

--bill

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 22:08:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I30Tj-00059l-Ay; Mon, 25 Jun 2007 22:08:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I30Th-00059g-3M
	for ipv6@ietf.org; Mon, 25 Jun 2007 22:08:25 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I30Tg-0002KE-KV
	for ipv6@ietf.org; Mon, 25 Jun 2007 22:08:25 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id C0E437301E;
	Tue, 26 Jun 2007 11:08:22 +0900 (JST)
Date: Tue, 26 Jun 2007 11:08:19 +0900
Message-ID: <m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Mon, 25 Jun 2007 16:16:29 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> First, it is not clear which "security problem" this bullet tries to
> indicate. 
> 
> <hs>  The problem we refer to is the fact that Host1 and Host2 have the
> same GUA on the same link! This is an obvious problem because Host1 is
> able to get an authoritative (because Host1 issued an unchallenged DAD
> for GUA) GUA that is also later assigned to Host2. Note that Host1 does
> not need an incorrectly implemented or hacked up IPv6 stack to reach
> this problem scenario - the problem arises with a fully compliant IPv6
> host stack on Host1 and Host2 using only the interface exported to an
> end user. If Host2 was NOT allowed to skip DAD, then Host2 will issue a
> NS(DAD) for GUA and Host1 being a compliant host would reply with an NA
> saying "I have this GUA". The net result is that traffic that should
> have gone to Host2, goes to Host1 instead - why is this not a security
> problem?

I, for one, would not call it a "security" problem; it's an accident.
As an "accident", the problem described in your draft is just
another form of a weird situation that 2462bis already explains.  And
since the possibility of the accident didn't fully convince the
opponents when we discussed 2462bis, I don't think this new draft can
now do it.

> <hs> Do you acknowledge the problem we describe above?

As an accident, yes.  And I'm now more confident that it's not
significant enough to delay the publication of 2462bis.

Without the editor hat on:

> Since we realize
> that 2462bis I-D is in AUTH48 state, a change like this may require
> IETF-wide review and that would further delay 2462bis becoming an RFC.
> But then where do we put changes like ours?  Our I-D is at the beginning
> of the process, so it may be an appropriate place for this and any
> further changes if they can't make it into 2462bis.

Before seeking the place to put the changes, the draft first needs to
convince others about the changes.  If it goes successfully, the new
document will be published as a separate RFC (I understand it's a time
consuming process, but in my understanding standardization at the IETF
works that way).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 22:40:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I30yG-0004W4-4Y; Mon, 25 Jun 2007 22:40:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I30yE-0004Vv-IM
	for ipv6@ietf.org; Mon, 25 Jun 2007 22:39:58 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I30yE-00053W-9T
	for ipv6@ietf.org; Mon, 25 Jun 2007 22:39:58 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85034962; Mon, 25 Jun 2007 22:39:57 -0400
Message-ID: <46807C77.2020101@internap.com>
Date: Mon, 25 Jun 2007 19:39:51 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
In-Reply-To: <CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Apparently people are still having a hard time visualizing use cases for 
ULA-C, so let me try again to lay one out:

Let's say I build a somewhat ad-hoc wireless mesh network covering a 
residential area to provide Internet service.  For my Internet 
connectivity, I get service from several different ISPs, each of which 
gives me an IPv6 subnet (PA space).  As this is a wireless network based 
on inexpensive hardware often deployed in a residential setting (and 
possibly involves some mobility), I can't count on any portion of my 
network to maintain reachability to any particular ISP uplink.  In 
addition, I am likely to change ISPs over time, and I'm too small to 
qualify for PI space, so I choose to number my internal network 
infrastructure out of private (ULA) space.  In parallel, I also use 
DHCP, DHCP-PD, etc. to assign subnets of my various PA space to users on 
various portions of my network (thereby giving them IPv6 address(es) of 
whichever Internet uplinks are available to them).  (I may also use some 
form of DHCP to assign PA space to my router interfaces, or I may choose 
to hide that detail by doing my mesh networking below layer 3, or I may 
choose to use ULA space there and rewrite the source address of any 
ULA-sourced packets leaving my network for the Internet.)

Now let's say I am thinking a little bit bigger than just my 
neighborhood, and would also like my network to connect to neighboring 
mesh networks.  (This could fairly easily evolve into an arbitrarily 
large internetwork enabling disaster-resistant connectivity across 
neighborhoods, cities, or entire regions.)  In order to facilitate 
troubleshooting, I elect to use ULA-C space for my network 
infrastructure, including router interfaces, (and either rewrite source 
addresses of any packets (presumably ICMP) my routers send out to the 
Internet, or also assign PA space to each interface with something like 
DHCP-PD, so that the router can use IPv6 address selection to use a 
public address for packets destined for public Internet addresses).  As 
before, I would give out PA subnet(s) to users for Internet 
connectivity, but I might also elect to give them ULA addresses to 
communicate with other hosts on my mesh network and neighboring ones.

In a situation like this, I need to be able to resolve PTRs for hosts 
using my neighboring networks' ULA space without any prior knowledge 
about the neighboring wireless network.  If both networks are numbered 
out of ULA-C space, this is easy: I send my PTR queries to my regular 
DNS resolver, which has a PA address and Internet connectivity, and can 
resolve the PTR from the DNS server authoritative for my neighboring 
wireless network's ULA-C block.

So, again, I see that ULA-C is a very simple solution to fill a very 
useful function that cannot be filled by local ULAs alone (at least 
without adding additional complexity to DNS).  Importantly, this 
functionality does not depend on ULA-C providing an additional assurance 
of uniqueness, but on the fact that my block (and its authoritative DNS 
servers) can be registered, and others can query the registered data.

As IPv6 adoption takes hold and dynamic wireless networking becomes 
cheaper and more widespread, I would see this kind of use case, and its 
many permutations, becoming more and more common.  Can you describe a 
way to use existing address types available to small networks (PA and 
ULA-L) and existing DNS technologies to support the requirements listed 
above?  If not, I would argue that we should complete the process of 
ULA-C standardization, as it represents the simplest available solution 
to the problem.


-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Mon Jun 25 23:59:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I32CY-00006B-6g; Mon, 25 Jun 2007 23:58:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I32CW-000065-JM
	for ipv6@ietf.org; Mon, 25 Jun 2007 23:58:48 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I32CR-0007i4-ID
	for ipv6@ietf.org; Mon, 25 Jun 2007 23:58:48 -0400
Received: from [203.10.60.4] (dhcp4.potaroo.net [203.10.60.4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id EF08BD5F31;
	Tue, 26 Jun 2007 13:58:41 +1000 (EST)
Message-ID: <46808F65.8020807@apnic.net>
Date: Tue, 26 Jun 2007 14:00:37 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
In-Reply-To: <CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



james woodyatt wrote:
> On Jun 25, 2007, at 17:01, Geoff Huston wrote:
>>
>> i.e. if we all pick numbers and stuff them into the DNS, then by the 
>> time the 1,240,000 selection had taken place the probability that a 
>> collision has occurred exceeds 0.5
> 
> That's only a problem for people who have to pick a number that collides 
> with absolutely none of the other 1,240,000 numbers.  I think no one 
> will ever have to do that, and *moreover* I think that anybody who 
> *does* think they'll have to do that has some explaining to do before we 
> worry about their problem.
> 
> Who's going to do that, and why?  By the way, that is *NOT* a rhetorical 
> question.  I really want to know the answer.

What I said above was "and stuff them into the DNS" i.e. when you have 
an environment that uniqueness is indeed critical and the number cannot 
collide with any other. i.e. IF you use the DNS for these numbers THEN 
this is a relevant issue.

clear yet?

And before you leap into "I'm never going to use the DNS, so whats the 
problem?" please also note that I'm not saying that putting these 
addresses into the DNS is good, bad or indifferent. What I was 
attempting to point out is that the factors that contribute to the risk 
of a collision depend on the nature of the environment where the numbers 
are used. One can hide in a small closet, lock the door, and in this 
little dark world of just you in your locked closet '1' is an entirely 
reasonable choice for a unique number. In other environments its 
probably a pretty poor choice!



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 01:13:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I33Mq-0007Kj-Da; Tue, 26 Jun 2007 01:13:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I33Mn-0007KV-Vw
	for ipv6@ietf.org; Tue, 26 Jun 2007 01:13:30 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I33Mn-0001rr-Iy
	for ipv6@ietf.org; Tue, 26 Jun 2007 01:13:29 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5432E11433
	for <ipv6@ietf.org>; Tue, 26 Jun 2007 05:12:56 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
In-Reply-To: Your message of "Mon, 25 Jun 2007 19:39:51 MST."
	<46807C77.2020101@internap.com> 
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 26 Jun 2007 05:12:56 +0000
Message-ID: <77167.1182834776@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Apparently people are still having a hard time visualizing use cases for
> ULA-C, so let me try again to lay one out:
> ...

thanks.

> So, again, I see that ULA-C is a very simple solution to fill a very useful
> function that cannot be filled by local ULAs alone (at least without adding
> additional complexity to DNS).  Importantly, this functionality does not
> depend on ULA-C providing an additional assurance of uniqueness, but on the
> fact that my block (and its authoritative DNS servers) can be registered,
> and others can query the registered data.

if you want registration, then you want a new kind of RIR PI space, since it
has to be unique, and the registration data has to be made and kept accurate.

> ...
> Now let's say I am thinking a little bit bigger than just my neighborhood,
> and would also like my network to connect to neighboring mesh networks.

i like this vision, it matches my own.

> (This could fairly easily evolve into an arbitrarily large internetwork
> enabling disaster-resistant connectivity across neighborhoods, cities, or
> entire regions.)

yes.

> In order to facilitate troubleshooting, I elect to use ULA-C space for my
> network infrastructure, including router interfaces, (and either rewrite
> source addresses of any packets (presumably ICMP) my routers send out to the
> Internet, or also assign PA space to each interface with something like
> DHCP-PD, so that the router can use IPv6 address selection to use a public
> address for packets destined for public Internet addresses).

i was almost going to snort beer out my nose at how funny that was, until the
millisecond when i realized that you didn't know it was funny to say "in order
to facilitate troubleshooting" and then follow with that description of rube
goldbergesque complexity.  why did you leave out the part where the anvil that
had been launched a few moments earlier finally, inevitably, lands on the
coyote's midriff?

but we (both) digress from the real point:

> In a situation like this, I need to be able to resolve PTRs for hosts using
> my neighboring networks' ULA space without any prior knowledge about the
> neighboring wireless network.

which wouldn't be nec'y if both of these networks were in some new kind of PI
space that was allocated out of a prefix designated by IANA for non-DFZ use.
(i keep bringing the discussion back to that point because asking IANA to
designate such a prefix ought to be the IETF's reaction to the ULA-C draft.)

but i still digress, let's get to the meat of it:

> If both networks are numbered out of ULA-C space, this is easy: I send my
> PTR queries to my regular DNS resolver, which has a PA address and Internet
> connectivity, and can resolve the PTR from the DNS server authoritative for
> my neighboring wireless network's ULA-C block.

here you're equating, dangerously in my opinion, three unrelated concepts:

	1. "public internet"
	2. "PA address"
	3. "internet connectivity"

please re-think this in terms of "connectivity realms", of which the DFZ is
one, and the american automotive exchange is another, and every fortune-2000
internal network is another, and every ad-hoc wireless mesh is another.  in
these terms, you'd have successfully pointed out that a given host may be in
more than one connectivity realm, and that it's impossible to know in advance
whether a network peer you reach in realm A can reach the same realm B that
you can reach.  now take it one step further -- stop according the DFZ any
special status, treat it as just another connectivity realm to which any
given network peer of yours may or may not have access.

> As IPv6 adoption takes hold and dynamic wireless networking becomes cheaper
> and more widespread, I would see this kind of use case, and its many
> permutations, becoming more and more common.

me too.

> Can you describe a way to use existing address types available to small
> networks (PA and ULA-L) and existing DNS technologies to support the
> requirements listed above?  If not, I would argue that we should complete
> the process of ULA-C standardization, as it represents the simplest
> available solution to the problem.

i see ULA-C as a giant rubber band and some rocket powered roller skates
which will finally, really, we mean it this time, allow the coyote to catch
that darn roadrunner.

the simpler solution is to recognize the following primary facts of reality:

1. every host needs a lan-scoped address
2. most hosts also need one or more global-scoped addresses
3. each of those global-scoped addresses will be in some connectivity realm
4. many of those connectivity realms will transitively, invisibly, overlap
5. the DFZ or "public internet" isn't special, it's just a connectivity realm
6. of all connectivity realms, the DFZ may not always be the largest one
7. all global-scoped addresses need ongoing reliable DNS and WHOIS support
8. address DNS/WHOIS support is traditionally a regional, bottom-up function

if we can get agreement on those, then the resulting conclusions are easy.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 01:29:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I33cT-0003iI-U1; Tue, 26 Jun 2007 01:29:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I33cR-0003hr-9d
	for ipv6@ietf.org; Tue, 26 Jun 2007 01:29:39 -0400
Received: from smtp.microsoft.com ([131.107.115.215])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I33bj-0004r6-Mf
	for ipv6@ietf.org; Tue, 26 Jun 2007 01:29:39 -0400
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Mon, 25 Jun 2007 22:28:55 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com (157.54.0.39)
	by TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.70.72) with
	Microsoft SMTP Server id 8.0.726.0; Mon, 25 Jun 2007 22:28:54 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3959);	 Mon, 25 Jun 2007 22:28:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Jun 2007 22:28:51 -0700
Message-ID: <70C6EFCDFC8AAD418EF7063CD132D06404F33405@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <46808F65.8020807@apnic.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace3pmv2DbZTxKXgQZyRSUu8HY25jAAC6p9Q
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46808F65.8020807@apnic.net>
From: Christian Huitema <huitema@windows.microsoft.com>
To: Geoff Huston <gih@apnic.net>, james woodyatt <jhw@apple.com>
X-OriginalArrivalTime: 26 Jun 2007 05:28:54.0445 (UTC)
	FILETIME=[E30955D0:01C7B7B2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> And before you leap into "I'm never going to use the DNS, so whats the
> problem?" please also note that I'm not saying that putting these
> addresses into the DNS is good, bad or indifferent.

What about "indifferent"?

Suppose that we pre-populate the ip6.arpa tree with synthetic name
server records, so that the name server for a given ULA prefix
<ula-48>::/48 (ULA-C or not) always resolves to <ula-48>::1 (or any
other suitably chosen anycast host identifier). Then DNS look-up will
always point to the closest instantiation of that anycast address, or to
nothing at all if the prefix is not reachable. Voila, DNS look-up
without any central registration...

-- Christian Huitema





--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 06:09:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I37pj-000487-U3; Tue, 26 Jun 2007 05:59:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I37pi-00047o-8x
	for ipv6@ietf.org; Tue, 26 Jun 2007 05:59:38 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I37pe-0000Vj-QR
	for ipv6@ietf.org; Tue, 26 Jun 2007 05:59:37 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 08B10140C278;
	Tue, 26 Jun 2007 11:59:32 +0200 (CEST)
Message-ID: <4680E388.4090803@spaghetti.zurich.ibm.com>
Date: Tue, 26 Jun 2007 10:59:36 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Christian Huitema <huitema@windows.microsoft.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46808F65.8020807@apnic.net>
	<70C6EFCDFC8AAD418EF7063CD132D06404F33405@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <70C6EFCDFC8AAD418EF7063CD132D06404F33405@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Geoff Huston <gih@apnic.net>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1893165745=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1893165745==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig357D622C4F8F4283A4BF634C"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig357D622C4F8F4283A4BF634C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Christian Huitema wrote:
>> And before you leap into "I'm never going to use the DNS, so whats the=

>> problem?" please also note that I'm not saying that putting these
>> addresses into the DNS is good, bad or indifferent.
>=20
> What about "indifferent"?
>=20
> Suppose that we pre-populate the ip6.arpa tree with synthetic name
> server records, so that the name server for a given ULA prefix
> <ula-48>::/48 (ULA-C or not) always resolves to <ula-48>::1 (or any
> other suitably chosen anycast host identifier). Then DNS look-up will
> always point to the closest instantiation of that anycast address, or t=
o
> nothing at all if the prefix is not reachable. Voila, DNS look-up
> without any central registration...

I almost proposed that, BUT, that breaks the whole point that some
people are using ::1 or ::53 or whatever magic constant for something
else already. People tend to use the first subnet on their LAN already.
It would indeed 'solve' the problem given here, but only partially as
you still don't have the really important bit: Forward resolving. How is
one magically going to tell where to find microsoft.com? Both have the
same root :(

I once proposed a 'well known anycasted DNS server address', so that we
can always say 2001:db8::53 and 192.0.2.53 are DNS. The 'local' DNS
server is simply the closest one found in the routing tables. ISP's can
then simply route this to their recursive nameservers and presto, no
configuration of that part needed. Unfortunately, only one such root can
exist in a network, if you join two networks you still have to tell both
networks where forward + reverse servers exist.

Greets,
 Jeroen


--------------enig357D622C4F8F4283A4BF634C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaA44guFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I1pHAKC1SxrOdoEsus+fbjvW4/M6nCXt
BgCfUYFP4qtIwJN96veQmj/LSu9j27o=
=lPN7
-----END PGP SIGNATURE-----

--------------enig357D622C4F8F4283A4BF634C--


--===============1893165745==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1893165745==--




From ipv6-bounces@ietf.org Tue Jun 26 08:08:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I39qH-0005Lh-Bj; Tue, 26 Jun 2007 08:08:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I39qF-0005LO-Hg
	for ipv6@ietf.org; Tue, 26 Jun 2007 08:08:19 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I39qF-00077w-8W
	for ipv6@ietf.org; Tue, 26 Jun 2007 08:08:19 -0400
Received: from [64.213.227.189] (189.227.sj.icannsanjuan.pr [64.213.227.189])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5QC85Bp006784
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 26 Jun 2007 05:08:06 -0700
In-Reply-To: <46807C77.2020101@internap.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <19D37ADD-AF8E-4B32-A22C-05FE5785ED73@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Tue, 26 Jun 2007 08:08:00 -0400
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 25 Jun 2007, at 10:39pm, Scott Leibrand wrote:

> Apparently people are still having a hard time visualizing use  
> cases for ULA-C, so let me try again to lay one out:

[...]

> In addition, I am likely to change ISPs over time, and I'm too  
> small to qualify for PI space,

It seems that if you qualified for PI space you wouldn't want ULA-C  
space. Is that right?

-- 
Leo Vegoda
IANA Numbers Liaison

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 08:55:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Aa9-0006Se-1D; Tue, 26 Jun 2007 08:55:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Aa6-0006SO-3d
	for ipv6@ietf.org; Tue, 26 Jun 2007 08:55:42 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3AYy-0005sD-CC
	for ipv6@ietf.org; Tue, 26 Jun 2007 08:55:42 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 0AA7F140C1AE;
	Tue, 26 Jun 2007 14:54:30 +0200 (CEST)
Message-ID: <46810C89.1040603@spaghetti.zurich.ibm.com>
Date: Tue, 26 Jun 2007 13:54:33 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46807C77.2020101@internap.com>
	<19D37ADD-AF8E-4B32-A22C-05FE5785ED73@icann.org>
In-Reply-To: <19D37ADD-AF8E-4B32-A22C-05FE5785ED73@icann.org>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0197728835=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0197728835==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigEF8330A1D7C6B07F582EFC53"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEF8330A1D7C6B07F582EFC53
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Leo Vegoda wrote:
> On 25 Jun 2007, at 10:39pm, Scott Leibrand wrote:
>=20
>> Apparently people are still having a hard time visualizing use cases
>> for ULA-C, so let me try again to lay one out:
>=20
> [...]
>=20
>> In addition, I am likely to change ISPs over time, and I'm too small
>> to qualify for PI space,
>=20
> It seems that if you qualified for PI space you wouldn't want ULA-C
> space. Is that right?

Most of the times, from what I understand. But one case was raised where
it would 'be easy to filter out ULA and distinguish from Internet
space', thus a site would have 2 prefixes: "Local" using ULA and
"Global" using PI. Which IMHO would only run into a lot of problems and
even more complexity etc. It is at least a case which has been
mentioned, but if anybody would actually ever use that. Especially with
the "we do IPv4 like this thus we do IPv6 like that also" mindset that
will not be a common network setup I guess.

Greets,
 Jeroen




--------------enigEF8330A1D7C6B07F582EFC53
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaBDIkuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2XoAJ4h0Ir5bVFEVlumIVM/FMNm941O
KACgnrbACtMKHenuiezm0BcdZMgIJUE=
=hRBw
-----END PGP SIGNATURE-----

--------------enigEF8330A1D7C6B07F582EFC53--


--===============0197728835==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0197728835==--




From ipv6-bounces@ietf.org Tue Jun 26 10:11:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Bkr-0005YM-R5; Tue, 26 Jun 2007 10:10:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Bkp-0005VP-FQ
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:10:51 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3Bkp-00069C-3I
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:10:51 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jun 2007 10:10:26 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAKi6gEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,463,1175486400"; 
	d="scan'208"; a="63697325:sNHT121568932"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5QEAQqm011537; 
	Tue, 26 Jun 2007 10:10:26 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5QE9kZl013690; 
	Tue, 26 Jun 2007 14:10:24 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:10:21 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jun 2007 10:10:19 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace3luOqRkGK2S63Tm6KInNV44anoQAAHiTg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 26 Jun 2007 14:10:21.0049 (UTC)
	FILETIME=[BB4E3E90:01C7B7FB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4792; t=1182867026;
	x=1183731026; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=egOanbaGx8JLR4fJfR50ck6xsf8532my5GMbh71q7hE=;
	b=qpo6B/L9fn6tpYBXDOwe8M+auO9Ipp+QK6oHYEsHcieBTofvjVh9fUFpJj0D6UKrtp27P16f
	djWXHX0D/RcxbcD7rgmZ3T7cm4Ydju0fG+wPnBe4+YDxKlDYkgkaaZWn;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Tatuya,

OK, it's alright to say an accident, but this accident caused the
security problem because we still think if Host1 is receiving traffic
that was meant to go to Host2, it's a security problem.=20

You also described the other security problem case where you said, Host1
is not compliant to IPv6 standards and deliberately malicious and we
granted you the fact that Host1 being a rouge can decide to ignore the
NS(DAD) from Host2. But even in this case the rtr will be able to detect
the problem if our proposed solution is applied - the solution being
Host2 will not skip DAD for GUA.

See my response in earlier email in quotes below:


"<hs> The second problem case, when Host1 is a rogue and not compliant
with IPv6 standards, sure Host1 can ignore the DAD-NS from Host2 but the
IPv6 router on the link MAY catch this duplicate since the router has
also seen this NS(DAD).  We envision that the router logs an error
message. Again, in our previous case above, if Host2 had skipped NS(DAD)
then the router would not catch this problem."

Here is the summary of what stands as of today.

Problem1: Host1 is not a rogue - it has already been acknowledged in
this mailer that this is a real problem that is not detected.
Solution1: What we propose in our I-D will fix this problem. We have
explained in an earlier email how.

Problem2: Host1 is a rogue - you have acknowledged this is a problem.
Solution2: The same solution from 1 is applied here. Host2 MUST NOT skip
DAD. Even when Host1 is a rogue and will ignore DAD from Host2 for GUA,=20
           the Ipv6 rtr picks up the dup and logs an error message.=20

Problem1 is a worse problem than problem2 because the attack can be
mounted by an IPv6 novice, and is not detected.

Let's focus on the problems at hand and solutions - forget delay of
2462bis I-D or what have you. Why are we referring to text in 2462bis as
an admittance that accident cases can exist when we have a solution for
such cases?

Thanks,

Hemant & Wes

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Monday, June 25, 2007 10:08 PM
To: Hemant Singh (shemant)
Cc: Brian E Carpenter; Fred Baker (fred); ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

At Mon, 25 Jun 2007 16:16:29 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> First, it is not clear which "security problem" this bullet tries to=20
> indicate.
>=20
> <hs>  The problem we refer to is the fact that Host1 and Host2 have=20
> the same GUA on the same link! This is an obvious problem because=20
> Host1 is able to get an authoritative (because Host1 issued an=20
> unchallenged DAD for GUA) GUA that is also later assigned to Host2.=20
> Note that Host1 does not need an incorrectly implemented or hacked up=20
> IPv6 stack to reach this problem scenario - the problem arises with a=20
> fully compliant IPv6 host stack on Host1 and Host2 using only the=20
> interface exported to an end user. If Host2 was NOT allowed to skip=20
> DAD, then Host2 will issue a
> NS(DAD) for GUA and Host1 being a compliant host would reply with an=20
> NA saying "I have this GUA". The net result is that traffic that=20
> should have gone to Host2, goes to Host1 instead - why is this not a=20
> security problem?

I, for one, would not call it a "security" problem; it's an accident.
As an "accident", the problem described in your draft is just another
form of a weird situation that 2462bis already explains.  And since the
possibility of the accident didn't fully convince the opponents when we
discussed 2462bis, I don't think this new draft can now do it.

> <hs> Do you acknowledge the problem we describe above?

As an accident, yes.  And I'm now more confident that it's not
significant enough to delay the publication of 2462bis.

Without the editor hat on:

> Since we realize
> that 2462bis I-D is in AUTH48 state, a change like this may require=20
> IETF-wide review and that would further delay 2462bis becoming an RFC.
> But then where do we put changes like ours?  Our I-D is at the=20
> beginning of the process, so it may be an appropriate place for this=20
> and any further changes if they can't make it into 2462bis.

Before seeking the place to put the changes, the draft first needs to
convince others about the changes.  If it goes successfully, the new
document will be published as a separate RFC (I understand it's a time
consuming process, but in my understanding standardization at the IETF
works that way).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba
Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:16:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Bq7-00016L-O5; Tue, 26 Jun 2007 10:16:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Bq6-00016G-0J
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:16:18 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Bpr-00048N-Mk
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:16:17 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 62C9C233C4; Tue, 26 Jun 2007 23:16:00 +0900 (JST)
To: shemant@cisco.com
In-Reply-To: Your message of "Tue, 26 Jun 2007 10:10:19 -0400"
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070626141600.62C9C233C4@coconut.itojun.org>
Date: Tue, 26 Jun 2007 23:16:00 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: fred@cisco.com, ipv6@ietf.org, brian.e.carpenter@gmail.com,
	jinmei@isl.rdc.toshiba.co.jp
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Tatuya,
> 
> OK, it's alright to say an accident, but this accident caused the
> security problem because we still think if Host1 is receiving traffic
> that was meant to go to Host2, it's a security problem. 
> 
> You also described the other security problem case where you said, Host1
> is not compliant to IPv6 standards and deliberately malicious and we
> granted you the fact that Host1 being a rouge can decide to ignore the
> NS(DAD) from Host2. But even in this case the rtr will be able to detect
> the problem if our proposed solution is applied - the solution being
> Host2 will not skip DAD for GUA.

	i fail to understand why this is a new problem for you.  the problem
	exists with ARP, and the only solution for the operator would be to
	pin down MAC address caches on the ethernet switch (L2 solution), or
	deploy secure neighbor discovery (L3 solution, which is very difficult,
	RFC3971 sizes 123Kbytes!).  why do you think we have to solve it with
	DAD change, which is not a perfect solution and incompatible with the
	deployed codebase?

itojun@code then spec

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:30:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3C4E-0005Ir-HL; Tue, 26 Jun 2007 10:30:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3C4C-0005Il-Rm
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:30:52 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3C4C-00075r-KX
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:30:52 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 26 Jun 2007 10:30:28 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIu/gEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,463,1175486400"; 
	d="scan'208"; a="124576264:sNHT44740216"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5QEUS5t003652; 
	Tue, 26 Jun 2007 10:30:28 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5QEUEM3019356; 
	Tue, 26 Jun 2007 14:30:27 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:30:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jun 2007 10:30:23 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1617@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <20070626141600.62C9C233C4@coconut.itojun.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
Thread-Index: Ace3/JOauD15+Oi+Q5yzGpxKP45GvgAAFGYg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	<20070626141600.62C9C233C4@coconut.itojun.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Jun-ichiro itojun Hagino" <itojun@itojun.org>
X-OriginalArrivalTime: 26 Jun 2007 14:30:24.0388 (UTC)
	FILETIME=[888D3440:01C7B7FE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1965; t=1182868228;
	x=1183732228; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Jun-ichiro=20itojun=20Hagino=22=20<itojun@itojun.org>;
	bh=Vzb4rq8uPDlwJIhfenMLjq8M6b6ER91HpUadvfpQfPM=;
	b=Y+lLC+ocvXuuT8bTGpQxTrAoGwZLptkgaGRHxqYKlJV30JLR4qHFI5PsUYoDDTcyATNr7Ubw
	+Xsm9wdNfKcNKW4kVih4MnQc/7CvujnJiSiOP4kRb7r05LkPZHYwB6Xj;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: "Fred Baker \(fred\)" <fred@cisco.com>, ipv6@ietf.org,
	brian.e.carpenter@gmail.com, jinmei@isl.rdc.toshiba.co.jp
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Why is solving the problems with a DAD change not a perfect solution ?
The problems are serious enough for deployed codebase to change. It's
not like we are asking to replace IPv6 hardware. It's a software change
for deployed code base. Anyhow, Tatuya has already said most hosts he
has tested with do not skip DAD. We have also tested hosts that do not
skip DAD. So what codebase and what specific hosts/nodes are you talking
about ?

Thanks.

Hemant

-----Original Message-----
From: Jun-ichiro itojun Hagino [mailto:itojun@itojun.org]=20
Sent: Tuesday, June 26, 2007 10:16 AM
To: Hemant Singh (shemant)
Cc: jinmei@isl.rdc.toshiba.co.jp; ipv6@ietf.org;
brian.e.carpenter@gmail.com; Fred Baker (fred)
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changessuggested to 2462bis-08

> Tatuya,
>=20
> OK, it's alright to say an accident, but this accident caused the=20
> security problem because we still think if Host1 is receiving traffic=20
> that was meant to go to Host2, it's a security problem.
>=20
> You also described the other security problem case where you said,=20
> Host1 is not compliant to IPv6 standards and deliberately malicious=20
> and we granted you the fact that Host1 being a rouge can decide to=20
> ignore the
> NS(DAD) from Host2. But even in this case the rtr will be able to=20
> detect the problem if our proposed solution is applied - the solution=20
> being
> Host2 will not skip DAD for GUA.

	i fail to understand why this is a new problem for you.  the
problem
	exists with ARP, and the only solution for the operator would be
to
	pin down MAC address caches on the ethernet switch (L2
solution), or
	deploy secure neighbor discovery (L3 solution, which is very
difficult,
	RFC3971 sizes 123Kbytes!).  why do you think we have to solve it
with
	DAD change, which is not a perfect solution and incompatible
with the
	deployed codebase?

itojun@code then spec

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:40:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3CD3-00077A-9v; Tue, 26 Jun 2007 10:40:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3CD1-00075j-IL
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:39:59 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3CCa-0007yQ-0D
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:39:59 -0400
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.13.8/8.13.8/Debian-3) with ESMTP id
	l5QEdNYG026380; Tue, 26 Jun 2007 17:39:23 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.13.8/8.13.8/Submit) id l5QEdMqS026377;
	Tue, 26 Jun 2007 17:39:22 +0300
Date: Tue, 26 Jun 2007 17:39:22 +0300
Message-Id: <200706261439.l5QEdMqS026377@burp.tkv.asdf.org>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org, brian.e.carpenter@gmail.com, fred@cisco.com
In-reply-to: <B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	(shemant@cisco.com)
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: 
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


Related to this topic, long time ago when the choices of

a) DAD only on link local, and not on other addresses derived
from the same id (legal on original RFC)

b) do DAD indivially on each address

were discussed, I preferred (a) (and still do), and proposed an
additional logic on hosts using (a):

- if they see DAD probe on any address using the ID part of the
  assigned link local address, the host would reply as if the probed
  address was configured ("defend ID patch").

That solves the case where one tries to manually configure global
address to some other host using the same ID part. The attempt will
fail as DAD collision. It does not solve merging of two local links
into one, but nothing solves that mess anyway, if there are multiple
users of same ID and addresses.


I still question the sanity of "do DAD on all addresses" approach:

- when router advertises a list of global prefixes, *each* and *every*
  node will now send DAD on each address at same time => instant DAD
  storm. And a host can have mulpiple id's in use...

- now, if we talk about rogue hosts, one could do continous stream of
  RA's with 40 random prefixes, and see how the hosts behave...



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:42:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3CFX-0000Xh-67; Tue, 26 Jun 2007 10:42:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3CFV-0000Vu-KE
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:42:33 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3CEz-0008QX-Cb
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:42:33 -0400
Received: from mymb.local (t050096.ppp.asahi-net.or.jp [203.189.50.96])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 793107301E;
	Tue, 26 Jun 2007 23:41:58 +0900 (JST)
Date: Tue, 26 Jun 2007 23:41:52 +0900
Message-ID: <m2d4zihj67.wl%jinmei@wide.ad.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Tue, 26 Jun 2007 10:10:19 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Let's focus on the problems at hand and solutions - forget delay of
> 2462bis I-D or what have you. Why are we referring to text in 2462bis as
> an admittance that accident cases can exist when we have a solution for
> such cases?

I'm afraid I'm now a little confused, so please let me be sure about
one thing first: are you still requiring us to incorporate your
proposed change in the coming 2462bis RFC?  Or are you now starting a
discussion as a separate thread from the publication of 2462bis?

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:46:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3CJ2-0004m4-4i; Tue, 26 Jun 2007 10:46:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3CJ0-0004a5-6N
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:46:10 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3CIP-0001bi-HK
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:46:10 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 23C69233C4; Tue, 26 Jun 2007 23:45:32 +0900 (JST)
To: shemant@cisco.com
In-Reply-To: Your message of "Tue, 26 Jun 2007 10:30:23 -0400"
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1617@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1617@xmb-rtp-20e.amer.cisco.com>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070626144532.23C69233C4@coconut.itojun.org>
Date: Tue, 26 Jun 2007 23:45:32 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: fred@cisco.com, ipv6@ietf.org, brian.e.carpenter@gmail.com,
	jinmei@isl.rdc.toshiba.co.jp
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
 changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Why is solving the problems with a DAD change not a perfect solution ?
> The problems are serious enough for deployed codebase to change. It's
> not like we are asking to replace IPv6 hardware. It's a software change
> for deployed code base. Anyhow, Tatuya has already said most hosts he
> has tested with do not skip DAD. We have also tested hosts that do not
> skip DAD. So what codebase and what specific hosts/nodes are you talking
> about ?

	i'm very sorry, i think i did not do the homework hard enough.

	i reread the whole thread and i think your abstract on the i-d is
	a bit misleading.  from the word "new requirement" i read that (i guess
	between the line) there are code changes to the deployed codebase which
	implements DAD correctly.  the fact is that you are proposing changes
	to make DAD a MUST instead of SHOULD (from section 5 of your draft).

	jinmei (who is KAME colleague of mine as you know) is very careful guy
	and he cares about other careless implementations which skips DAD :-)

	i do not care about careless implementations unlike jinmei, however,
	i still think that your security model with "DAD is a MUST" is not
	perfect.

	yes, which DAD being MUST it would be a better world order.  however,
	because this is based on the assumption that all of the implementations
	would follow the RFC to secure the link, a clever attacker would get
	a freely-available IPv6 implementation, "#if 0" the portion which does
	DAD and steal traffic anyway (or implement something on BPF writes or
	raw IPv6 sockets).

	so, as i said, the only solution is either to pin-down MAC address
	cache (L2) or do some cryptographic dance (L3).  L3 stuff still require
	every node to cooperate, i think the only solution is in L2.
	CISCO can sell a lot of L2 devices with the feature :-P

itojun

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 10:58:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3CVD-0007cB-7s; Tue, 26 Jun 2007 10:58:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3CVB-0007c5-ER
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:58:45 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3CVB-0000Ah-7N
	for ipv6@ietf.org; Tue, 26 Jun 2007 10:58:45 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 26 Jun 2007 10:58:45 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFfGgEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,463,1175486400"; 
	d="scan'208"; a="63703495:sNHT40184022"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5QEwiY0006441; 
	Tue, 26 Jun 2007 10:58:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5QEwVLt028434; 
	Tue, 26 Jun 2007 14:58:44 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 10:58:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jun 2007 10:58:42 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2d4zihj67.wl%jinmei@wide.ad.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
Thread-Index: Ace4ADGnkFEg594uQc+jEiV3rbuSqwAAVuKg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	<m2d4zihj67.wl%jinmei@wide.ad.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 26 Jun 2007 14:58:43.0789 (UTC)
	FILETIME=[7D7937D0:01C7B802]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1712; t=1182869924;
	x=1183733924; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changes=20suggested=20to=202462bis-08 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=C330MsFDibT51Ji551g5NMl/0SVTTDGZbzwJCcFk3G4=;
	b=SnMSRTVbf7XjDD2y8nwYbWYL77/8FCIrCu8Ls+4bsqS5DWqsdX98Lt7xGcaiG79Dhs55sGA2
	vD4iUSvcWHynMmdZBz4+kJFLpesMbtC+43IyjBBQENfGCPoI1Msb6n/W;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changes
	suggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

We originally wanted to make changes to 2462bis I-D, but since it's in
AUTH state, that may not be possible anymore.

If you want, we can let 2462bis I-D not make our proposed change, but
our security case and solution needs to be addressed in an I-D to
highlight the problem with older implementations that can skip DAD. It
would be preferable if the security problem and its solution is
presented in 2462bis, but if that's not possible, then we'll discuss it
in our I-D.

We have other issues we want to address in our I-D, and we don't want to
have this issue prevent other issues from being discussed.

- Hemant and Wes

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Tuesday, June 26, 2007 10:42 AM
To: Hemant Singh (shemant)
Cc: Brian E Carpenter; Fred Baker (fred); ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

At Tue, 26 Jun 2007 10:10:19 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Let's focus on the problems at hand and solutions - forget delay of=20
> 2462bis I-D or what have you. Why are we referring to text in 2462bis=20
> as an admittance that accident cases can exist when we have a solution

> for such cases?

I'm afraid I'm now a little confused, so please let me be sure about one
thing first: are you still requiring us to incorporate your proposed
change in the coming 2462bis RFC?  Or are you now starting a discussion
as a separate thread from the publication of 2462bis?

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba
Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 15:41:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Gu1-0007VY-Eq; Tue, 26 Jun 2007 15:40:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Gu0-0007VS-2H
	for ipv6@ietf.org; Tue, 26 Jun 2007 15:40:40 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3GtL-00070S-Ht
	for ipv6@ietf.org; Tue, 26 Jun 2007 15:40:40 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id 1610EA4E98B
	for <ipv6@ietf.org>; Tue, 26 Jun 2007 12:39:59 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 00D5E4004D
	for <ipv6@ietf.org>; Tue, 26 Jun 2007 12:39:59 -0700 (PDT)
X-AuditID: 11807126-a50d3bb0000007dd-8b-46816b8ee9aa
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay8.apple.com (Apple SCV relay) with ESMTP id E4FD540029
	for <ipv6@ietf.org>; Tue, 26 Jun 2007 12:39:58 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <70C6EFCDFC8AAD418EF7063CD132D06404F33405@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<46808F65.8020807@apnic.net>
	<70C6EFCDFC8AAD418EF7063CD132D06404F33405@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9F0EFE6E-AD08-4F38-A712-FB0D2319DCE5@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Tue, 26 Jun 2007 12:39:55 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 25, 2007, at 22:28, Christian Huitema wrote:
>
> Suppose that we pre-populate the ip6.arpa tree with synthetic name  
> server records, so that the name server for a given ULA prefix  
> <ula-48>::/48 (ULA-C or not) always resolves to <ula-48>::1 (or any  
> other suitably chosen anycast host identifier). Then DNS look-up  
> will always point to the closest instantiation of that anycast  
> address, or to nothing at all if the prefix is not reachable.  
> Voila, DNS look-up without any central registration...

On Jun 26, 2007, at 02:59, Jeroen Massar wrote:
> It would indeed 'solve' the problem given here, but only partially  
> as you still don't have the really important bit: Forward resolving.

I like the idea of asking IANA to define an anycast address for  
synthetically populating <global-id>.0.0.d.f.ip6.arpa domains with  
matching NS and AAAA records for the ULA-addressed name servers.   
Resolvers could easily implement this rule and reduce the load on the  
public DNS servers.  I think the concern about forward resolution and  
split horizons is orthogonal, and it should be deferred.  There is  
only one horizon required for reverse DNS resolutions of global scope  
addresses.

I also like the idea of asking IANA to reserve a prefix for RIR's to  
allocate for non-DFZ use.  That effectively addresses the perceived  
need for a registry to mitigate the risk of birthday paradox  
collision with ULA.

I'd like to see drafts for both of these (alas, I don't have the time  
to write them myself).  In the process of revising RFC 4193 for the  
reverse DNS magic, we should also return fc00::/8 to IANA and  
eliminate the 'L' bit, which I'm on record as saying I think was a  
bad idea from the start.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 15:52:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3H5D-0006no-U6; Tue, 26 Jun 2007 15:52:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3H5B-0006nJ-4U
	for ipv6@ietf.org; Tue, 26 Jun 2007 15:52:13 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3H5A-00069m-SI
	for ipv6@ietf.org; Tue, 26 Jun 2007 15:52:13 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 26 Jun 2007 15:51:57 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CALcLgUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,464,1175486400"; 
	d="scan'208"; a="124613656:sNHT53005860"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5QJpubi025855; 
	Tue, 26 Jun 2007 15:51:56 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5QJptLh024850; 
	Tue, 26 Jun 2007 19:51:56 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 15:51:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jun 2007 15:51:53 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
Thread-Index: Ace4ADGnkFEg594uQc+jEiV3rbuSqwAAVuKgAApHh7A=
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com><m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com><467BD7FC.1030405@gmail.com><B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com><467BDEE5.30807@gmail.com><457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com><467F62DA.2010802@gmail.com><B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com><m2645chx46.wl%jinmei@wide.ad.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com><m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com><m2d4zihj67.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 26 Jun 2007 19:51:54.0880 (UTC)
	FILETIME=[7294B000:01C7B82B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2664; t=1182887516;
	x=1183751516; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>,
	=0A=20=20=2
	0=20=20=20=20=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba
	.co.jp>; bh=OpQmoY/keIwega0ozVMytJwMroJoWIMhAA7pexPOz2U=;
	b=jbIMc7IlkccUcQLxdKyhWeNzDK5pRfNwJ5YpQ+t9XLuRIqAUUtK9qTMdhtXRayKiT999cL6C
	aL+iaeQ4+DD23BkbRBLnjeepBARYydBcjQJNk02wENsoOZyhj6yhWh4f;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(fred\)" <fred@cisco.com>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

IETF IPv6 Folks,

The focus of discussion has been with regards to one proposed change to
2462bis, because of its impending release status.  However, this is not
the primary focus of our I-D.  The primary focus is clearing up
misconceptions related to data forwarding and address resolution with
respect to on-link determination.  We have found host bugs that have
matched areas of 2461 and 2462 that are not clear, concise, and
explicit.

- Hemant and Wes=20

-----Original Message-----
From: Hemant Singh (shemant)=20
Sent: Tuesday, June 26, 2007 10:59 AM
To: JINMEI Tatuya / ????
Cc: ipv6@ietf.org; Brian E Carpenter; Fred Baker (fred)
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changessuggested to 2462bis-08

We originally wanted to make changes to 2462bis I-D, but since it's in
AUTH state, that may not be possible anymore.

If you want, we can let 2462bis I-D not make our proposed change, but
our security case and solution needs to be addressed in an I-D to
highlight the problem with older implementations that can skip DAD. It
would be preferable if the security problem and its solution is
presented in 2462bis, but if that's not possible, then we'll discuss it
in our I-D.

We have other issues we want to address in our I-D, and we don't want to
have this issue prevent other issues from being discussed.

- Hemant and Wes

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]
Sent: Tuesday, June 26, 2007 10:42 AM
To: Hemant Singh (shemant)
Cc: Brian E Carpenter; Fred Baker (fred); ipv6@ietf.org
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
changes suggested to 2462bis-08

At Tue, 26 Jun 2007 10:10:19 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Let's focus on the problems at hand and solutions - forget delay of=20
> 2462bis I-D or what have you. Why are we referring to text in 2462bis=20
> as an admittance that accident cases can exist when we have a solution

> for such cases?

I'm afraid I'm now a little confused, so please let me be sure about one
thing first: are you still requiring us to incorporate your proposed
change in the coming 2462bis RFC?  Or are you now starting a discussion
as a separate thread from the publication of 2462bis?

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba
Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 17:45:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Iq8-00070G-0m; Tue, 26 Jun 2007 17:44:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Iq6-000709-Bq
	for ipv6@ietf.org; Tue, 26 Jun 2007 17:44:46 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3IpD-00071l-6S
	for ipv6@ietf.org; Tue, 26 Jun 2007 17:44:46 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5QLhj4s075334
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 26 Jun 2007 23:43:45 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5QLhhZn004470; Tue, 26 Jun 2007 23:43:43 +0200
Date: Tue, 26 Jun 2007 23:43:43 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706192211570.9840@netcore.fi>
Message-ID: <Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 19 Jun 2007, Pekka Savola wrote:
> On Tue, 19 Jun 2007, Thomas Narten wrote:
>> And help me understand how this equates to the AS112 issues. For sites
>> that (today) get PI space and don't actually advertise it to the
>> internet, aren't the DNS issues _exactly_ the same?
>
> IMHO, if reverse DNS is provided, it should be required that the 
> authoritative DNS servers have non-ULA addresses.  I think Mark was assuming 
> that ULA address for authoritative delegation point might be OK, which would 
> lead to issues if the ULA address is not reachable from everywhere where 
> reverse DNS lookups should succeed.

... and then you are back to being bound to some IP addresses (for 
your DNS) belong to someone and you might not want that at all. 
Enterprises changing providers also need to change IP for their DNS, or 
simple get PI for these IP addresses. And if you get PI, why ULA-C?!



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 18:35:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Jcl-0003rl-IY; Tue, 26 Jun 2007 18:35:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Jcj-0003oC-Fk
	for ipv6@ietf.org; Tue, 26 Jun 2007 18:35:02 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3JcG-0002D8-Tk
	for ipv6@ietf.org; Tue, 26 Jun 2007 18:35:01 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5QMYUQJ083983
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 27 Jun 2007 00:34:30 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5QMYUJl007498; Wed, 27 Jun 2007 00:34:30 +0200
Date: Wed, 27 Jun 2007 00:34:30 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <467A38A3.1050808@gmail.com>
Message-ID: <Pine.LNX.4.64.0706270023410.29317@chandra.student.uit.no>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<4678396E.4000204@spaghetti.zurich.ibm.com>
	<467A38A3.1050808@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org, roger@jorgensen.no
Subject: Re: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 21 Jun 2007, Brian E Carpenter wrote:
>
> I see Thomas' argument for tolerating occasional use of AAAA entries in the
> global DNS for ULAs - but it seems that it leads to too many complications
> to be recommended. Since I'm sure the IETF isn't ready yet to endorse the
> reality of split DNS deployment, wouldn't it be best to say that ULA-Cs
> SHOULD NOT be included in the global DNS? (And that is a significant
> difference in scope and intent compared with PI.)

I like the idea of having DNS combined with ULA-C but that just poison the 
entire idea of global unique private IP space in IPv6.

So yes, remove the entire part about DNS from this draft, simply state 
ULA-C provide no reverse in the global DNS, or how it can be phrased best. 
Maybe "ULA-C should not be included in the global DNS" is good enough.

and at the same time state that if you required global DNS get it from the 
RIRs.



-- 


------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 18:42:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Jk9-0007oZ-4O; Tue, 26 Jun 2007 18:42:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Jk7-0007oU-VM
	for ipv6@ietf.org; Tue, 26 Jun 2007 18:42:39 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Jk1-0003U9-73
	for ipv6@ietf.org; Tue, 26 Jun 2007 18:42:39 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5QMgTL2085110
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 27 Jun 2007 00:42:29 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5QMgTQq007876; Wed, 27 Jun 2007 00:42:29 +0200
Date: Wed, 27 Jun 2007 00:42:29 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: james woodyatt <jhw@apple.com>
In-Reply-To: <6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
Message-ID: <Pine.LNX.4.64.0706270041250.29317@chandra.student.uit.no>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 21 Jun 2007, james woodyatt wrote:
<snip>
>
> We successfully deprecated site-local unicast addressing by painting it with 
> the stink of IPv4 network address translation.  However, we retained the 
> technical consensus that unreachable nodes still need to be uniquely 
> addressable, and what's more: these unreachable global scope unicast 
> addresses must be assigned from a registry with a single global root.
>
> My heretical opinion is that the second technical consensus is wrong.  We 
> should deprecate the 'L' bit in the ULA address type and make all ULA into 
> locally allocated addresses.  That way, we will have carved off a well-known 
> prefix (like all the other non-routable prefixes) where nodes are neither 
> uniquely addressable nor reachable on the public Internet.  I contend the 'L' 
> bit was never a good idea; it was a placeholder for those wishing to retain 
> network address translation in IPv6.  There, I said it.

agree... let's go back to the original RFC defining ULA and remove that 
bit and using this entire thread over the last few months as a reason why 
it never should be global unique etc....



-- 


------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 19:19:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3KJI-0005Wf-0A; Tue, 26 Jun 2007 19:19:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3KJG-0005WZ-57
	for ipv6@ietf.org; Tue, 26 Jun 2007 19:18:58 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3KJF-00076h-V9
	for ipv6@ietf.org; Tue, 26 Jun 2007 19:18:58 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5QNIapQ009853
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 26 Jun 2007 18:18:36 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5QNIa5l027159; Tue, 26 Jun 2007 18:18:36 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5QNITBK026962; Tue, 26 Jun 2007 18:18:36 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Jun 2007 16:18:35 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 26 Jun 2007 16:17:43 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace4O0PYgRkPdwoXTxm9+SWHL6RD8gADBh7A
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Roger Jorgensen" <rogerj@jorgensen.no>, "Pekka Savola" <pekkas@netcore.fi>
X-OriginalArrivalTime: 26 Jun 2007 23:18:35.0205 (UTC)
	FILETIME=[51C01F50:01C7B848]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Thomas Narten <narten@us.ibm.com>, Mark Andrews <Mark_Andrews@isc.org>,
	ipv6@ietf.org
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> ... and then you are back to being bound to some IP addresses (for=20
> your DNS) belong to someone and you might not want that at all.=20
> Enterprises changing providers also need to change IP for=20
> their DNS, or=20
> simple get PI for these IP addresses. And if you get PI, why ULA-C?!

Discussions on this list seem to indicate that globally
routable PI might not be attainable for very small sites
such as my laptop. That would be an example of where I
can't get my own PI prefix, right?

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Tue Jun 26 20:53:57 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3LmW-0005G3-EU; Tue, 26 Jun 2007 20:53:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3LmT-00058z-G1
	for ipv6@ietf.org; Tue, 26 Jun 2007 20:53:13 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3LYb-0003zG-L3
	for ipv6@ietf.org; Tue, 26 Jun 2007 20:38:53 -0400
Received: from [63.251.161.164] (account sleibrand@mail.internap.com HELO
	[63.251.161.164])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85105621; Tue, 26 Jun 2007 20:38:21 -0400
Message-ID: <4681B179.2020301@internap.com>
Date: Tue, 26 Jun 2007 17:38:17 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46807C77.2020101@internap.com>
	<77167.1182834776@sa.vix.com>
In-Reply-To: <77167.1182834776@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Cc: ARIN PPML <ppml@arin.net>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul Vixie wrote:
>> Apparently people are still having a hard time visualizing use cases for
>> ULA-C, so let me try again to lay one out:
>> ...
>>     
>
> thanks.
>   

And thank you for your thoughtful and reasoned response.

>> So, again, I see that ULA-C is a very simple solution to fill a very useful
>> function that cannot be filled by local ULAs alone (at least without adding
>> additional complexity to DNS).  Importantly, this functionality does not
>> depend on ULA-C providing an additional assurance of uniqueness, but on the
>> fact that my block (and its authoritative DNS servers) can be registered,
>> and others can query the registered data.
>>     
>
> if you want registration, then you want a new kind of RIR PI space, since it
> has to be unique, and the registration data has to be made and kept accurate.
>   

Yeah, to me that's what ULA-C should be, a block of space defined by the 
IETF, delegated by IANA to the RIRs, and administered as "unique local" 
or "private PI" space.  I don't care whether we call it ULA-C and 
allocate it out of FC00, or if we call it private PI and chose a 
different subnet.

>   
>> ...
>> Now let's say I am thinking a little bit bigger than just my neighborhood,
>> and would also like my network to connect to neighboring mesh networks.
>>     
>
> i like this vision, it matches my own.
>
>   
>> In order to facilitate troubleshooting, I elect to use ULA-C space for my
>> network infrastructure, including router interfaces, (and either rewrite
>> source addresses of any packets (presumably ICMP) my routers send out to the
>> Internet, or also assign PA space to each interface with something like
>> DHCP-PD, so that the router can use IPv6 address selection to use a public
>> address for packets destined for public Internet addresses).
>>     
>
> i was almost going to snort beer out my nose at how funny that was, until the
> millisecond when i realized that you didn't know it was funny to say "in order
> to facilitate troubleshooting" and then follow with that description of rube
> goldbergesque complexity.  why did you leave out the part where the anvil that
> had been launched a few moments earlier finally, inevitably, lands on the
> coyote's midriff?
>
> but we (both) digress from the real point:
>   

I'm not sure which aspects of what I outline you would consider 
unnecessarily complex, but I agree that is tangential to our discussion, 
so we can follow that up offline if you like.

>   
>> In a situation like this, I need to be able to resolve PTRs for hosts using
>> my neighboring networks' ULA space without any prior knowledge about the
>> neighboring wireless network.
>>     
>
> which wouldn't be nec'y if both of these networks were in some new kind of PI
> space that was allocated out of a prefix designated by IANA for non-DFZ use.
> (i keep bringing the discussion back to that point because asking IANA to
> designate such a prefix ought to be the IETF's reaction to the ULA-C draft.)
>
> but i still digress, let's get to the meat of it:
>   

I'm not sure this is a digression.  What you're describing is exactly 
what I think ULA-C should be: a well-known block (that DFZ operators 
would filter announcements from) from which PI assignments can be made 
without the restrictions required on public PI space to avoid routing 
table bloat.

>   
>> If both networks are numbered out of ULA-C space, this is easy: I send my
>> PTR queries to my regular DNS resolver, which has a PA address and Internet
>> connectivity, and can resolve the PTR from the DNS server authoritative for
>> my neighboring wireless network's ULA-C block.
>>     
>
> here you're equating, dangerously in my opinion, three unrelated concepts:
>
> 	1. "public internet"
> 	2. "PA address"
> 	3. "internet connectivity"
>
> please re-think this in terms of "connectivity realms", of which the DFZ is
> one, and the american automotive exchange is another, and every fortune-2000
> internal network is another, and every ad-hoc wireless mesh is another.  in
> these terms, you'd have successfully pointed out that a given host may be in
> more than one connectivity realm, and that it's impossible to know in advance
> whether a network peer you reach in realm A can reach the same realm B that
> you can reach.  now take it one step further -- stop according the DFZ any
> special status, treat it as just another connectivity realm to which any
> given network peer of yours may or may not have access.
>   

While I agree with this analysis in the abstract, and would not opposed 
a private PI policy based on it (as it would likely be quite robust), 
I'm not sure that we can simply see the public Internet as just another 
connectivity realm.  I believe that the history of the Internet, and the 
architecture we have built up to support it (particularly the addressing 
architecture, as defined by the IETF and delegated from IANA to the RIRs 
to ISPs and to end sites), require that we consider the public Internet 
to be a unique connectivity realm.

>   
>> Can you describe a way to use existing address types available to small
>> networks (PA and ULA-L) and existing DNS technologies to support the
>> requirements listed above?  If not, I would argue that we should complete
>> the process of ULA-C standardization, as it represents the simplest
>> available solution to the problem.
>>     
>
> i see ULA-C as a giant rubber band and some rocket powered roller skates
> which will finally, really, we mean it this time, allow the coyote to catch
> that darn roadrunner.
>
> the simpler solution is to recognize the following primary facts of reality:
>
> 1. every host needs a lan-scoped address
>   

Link-local.  Done.

> 2. most hosts also need one or more global-scoped addresses
> 3. each of those global-scoped addresses will be in some connectivity realm
>   

Agreed.

> 4. many of those connectivity realms will transitively, invisibly, overlap
> 5. the DFZ or "public internet" isn't special, it's just a connectivity realm
> 6. of all connectivity realms, the DFZ may not always be the largest one
>   

Perhaps not, especially depending on your definition of "largest".  
However, any connectivity realm that approaches the public Internet in 
terms of the number and diversity of interconnected participants will 
require an addressing and routing framework to meet the various needs of 
its different participants in a mutually acceptable manner.  As long as 
we're talking about IPv6, that addressing framework will need to coexist 
with the addressing framework of the public Internet.  Given the current 
Internet addressing architecture, that means we need some way to 
partition off part of the IPv6 address space, designate it as "not to be 
routed in the DFZ", and assign pieces of that space to anyone wishing to 
internetwork in a connectivity realm other than the DFZ.

> 7. all global-scoped addresses need ongoing reliable DNS and WHOIS support
> 8. address DNS/WHOIS support is traditionally a regional, bottom-up function
>   

Agreed, which is why I advocate that ULA-C space (or whatever we end up 
calling the space that fills the needs described above) be assigned to 
Regional Internet Registries (RIRs), who can then assign it to end users 
and provide appropriate DNS and WHOIS support.  I would also support 
allowing the RIRs to allocate such non-DFZ-routed space to Local 
Internet Registries (LIRs), so that they can serve their 
members/customers by reassigning such space and providing DNS and/or 
WHOIS services in a method (and possibly a connectivity realm) not 
served by the RIRs directly.

> if we can get agreement on those, then the resulting conclusions are easy.
>   

Given our slightly differing opinions on the special significance of the 
"public Internet" connectivity realm, I would love to hear what 
conclusions you draw based on the above points.  I would draw the 
following conclusions:

    * There is a need to allocate and assign IPv6 address space, in a
      non-restrictive manner, to entities wishing to internetwork
      outside of the public Internet's DFZ.
    * There is a need to provide reliable DNS and WHOIS support for
      these addresses.  The methods of providing such DNS support should
      include, but should not be limited to, allowing registrants to
      delegate DNS authority to servers reachable from the public
      Internet.  Other methods for providing reliable DNS support for
      these addresses should be explored, but no method should be
      allowed which imposes an undue burden on Internet DNS infrastructure.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 00:51:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3PTu-0002lF-9V; Wed, 27 Jun 2007 00:50:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3PTs-0002kD-SW
	for ipv6@ietf.org; Wed, 27 Jun 2007 00:50:16 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3PTk-0007XZ-CR
	for ipv6@ietf.org; Wed, 27 Jun 2007 00:50:16 -0400
Received: from ssprunkxp (ip55.post-vineyard.dfw.ygnition.net [24.219.179.55])
	by ns2.ygnition.com (8.13.6/8.13.5) with SMTP id l5R4o4iu006347;
	Tue, 26 Jun 2007 21:50:06 -0700
Message-ID: <024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Scott Leibrand" <sleibrand@internap.com>, "Paul Vixie" <paul@vix.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>
	<4681B179.2020301@internap.com>
Date: Tue, 26 Jun 2007 23:48:05 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ARIN PPML <ppml@arin.net>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thus spake "Scott Leibrand" <sleibrand@internap.com>
>> which wouldn't be nec'y if both of these networks were in some
>> new kind of PI space that was allocated out of a prefix designated
>> by IANA for non-DFZ use.  (i keep bringing the discussion back
>> to that point because asking IANA to designate such a prefix
>> ought to be the IETF's reaction to the ULA-C draft.)
>>
>> but i still digress, let's get to the meat of it:
>
> I'm not sure this is a digression.  What you're describing is
> exactly what I think ULA-C should be: a well-known block (that
> DFZ operators would filter announcements from) from which PI
> assignments can be made without the restrictions required on
> public PI space to avoid routing table bloat.

If this is what we mean by "private PI", then I'm against that too. 
Dressing up ULA-C with a different prefix and name but retaining all of the 
operational stupidity doesn't solve any problems.    A turd by any other 
name smells just as foul.

If we want to issue address space to folks for "private" use, it needs to be 
out of the same block(s) that the RIRs use to allocate space for "public" 
use, because sooner or later those "private" networks are going to end up 
being publicly routed.

If we are concerned that giving "real" PI space to every org that asks for 
it will result in the immediate death of the DFZ, then there needs to be 
some sort of tag attached to blocks that says whether or not the registrant 
has met whatever the current rules are for deserving a routing slot.  If 
routing certificates ever take off, they could contain a flag that gives the 
current public routability status, or the RIR could just not issue a 
certificate at all if someone hasn't met the bar.  That's an entirely 
separate matter from whether or not they get addresses.

One could also argue that the RIRs do not belong in the routability decision 
path at all, since their job is to ensure uniqueness, and some other 
quasi-public entity responsible for the health of the DFZ would produce 
"routability" certificates.  That also gives rise to the possibility of 
different models than we have today, like a market where people could buy 
and sell routing slots.

S

Stephen Sprunk      "Those people who think they know everything
CCIE #3723         are a great annoyance to those of us who do."
K5SSS                                             --Isaac Asimov 



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 06:01:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3UKT-0006Jl-4e; Wed, 27 Jun 2007 06:00:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3UKR-0006Jf-RO
	for ipv6@ietf.org; Wed, 27 Jun 2007 06:00:51 -0400
Received: from wr-out-0506.google.com ([64.233.184.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3UKL-00042E-QV
	for ipv6@ietf.org; Wed, 27 Jun 2007 06:00:51 -0400
Received: by wr-out-0506.google.com with SMTP id 70so64614wra
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 03:00:45 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=BRtz/lEVN51ZNc+jJk2YwL6hJk5eaA0rr6PDqa/+Mz14Kw8RVxLtgfKg8eYYSVioi8b1M7LG59pgvVEDxkUhZwjZHMK0Z9/tndi8h30xXmXi2gmtUWhn0lXMa2JFJG4J48MH4YeatxUxE3GemS0w/NsTXyXFIP9dHdDFLpIPFzQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lFcn+BY8ZeKbP8w1TaLTtPZn9UuLcWqkwhCPEhknvm9ezVf0uOGi47T9A1FuT44txiLMhuf5LKRtPrkNy5FbiwgFORfjM03WrlFa5UQQHrKoZuntLiw1uet4ubex0NVOz9mcdbodWZm8IJyNfaiijN2m9x3fwkqKMvG953shoi8=
Received: by 10.78.178.5 with SMTP id a5mr158007huf.1182938444573;
	Wed, 27 Jun 2007 03:00:44 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id f4sm12060732nfh.2007.06.27.03.00.43
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 03:00:43 -0700 (PDT)
Message-ID: <4682354C.5010906@gmail.com>
Date: Wed, 27 Jun 2007 12:00:44 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Joe Abley <jabley@ca.afilias.info>
References: <3CC9E5E1-0095-4273-BF9E-FA0273F5B86C@ca.afilias.info>
In-Reply-To: <3CC9E5E1-0095-4273-BF9E-FA0273F5B86C@ca.afilias.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-01-01-candidate-02
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

FWIW, my opinion is 'ship it'. It seems like time
to get a formal readout of (rough) WG consensus
on this.

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 07:01:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3VH5-0000Z9-Mf; Wed, 27 Jun 2007 07:01:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3VH4-0000RW-Dg
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:01:26 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3VGa-0002wl-Ds
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:01:26 -0400
Received: by ug-out-1314.google.com with SMTP id k3so821885ugf
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 04:00:55 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=cG3wEOYnfATCX7BoEBkpnBV+dXc2vUlpV9SWczNf9ltI2lKyxVmLSIe/jEXS+NVqXIPcZ9UdEpuTwLJx2Zmwb1hsy5lMtfmK6bQEXFRANPOHfcZ88dP5U7DMnLdgXrBaBo96jktdz5UD0jXfLZESHenvfMYYXHROgviHsx03dX4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=NeZkaFOnOHn1gQZ1RTJTpQxVcFZXKmr3FgMaOm4ZWx7xn4kj1NNKDq/J3dqMAPNJ7JeW4C/uJB4tsd7emxiGaWA+hi3r7NtksfXHcKXz9mNnDP/JWl5o27ja8qpa4ENIN4hbY2jlUUeGDhvpzcDnwxY3Ebia+jYokIvnTCrq4XA=
Received: by 10.66.239.16 with SMTP id m16mr1038571ugh.1182942055726;
	Wed, 27 Jun 2007 04:00:55 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id q1sm2204940uge.2007.06.27.04.00.48
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 04:00:48 -0700 (PDT)
Message-ID: <46824361.4000300@gmail.com>
Date: Wed, 27 Jun 2007 13:00:49 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com>
In-Reply-To: <46807C77.2020101@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Scott, you say

> In a situation like this, I need to be able to resolve PTRs for hosts using my neighboring networks' ULA space

Why do you need to do this?

     Brian

On 2007-06-26 04:39, Scott Leibrand wrote:
> Apparently people are still having a hard time visualizing use cases for 
> ULA-C, so let me try again to lay one out:
> 
> Let's say I build a somewhat ad-hoc wireless mesh network covering a 
> residential area to provide Internet service.  For my Internet 
> connectivity, I get service from several different ISPs, each of which 
> gives me an IPv6 subnet (PA space).  As this is a wireless network based 
> on inexpensive hardware often deployed in a residential setting (and 
> possibly involves some mobility), I can't count on any portion of my 
> network to maintain reachability to any particular ISP uplink.  In 
> addition, I am likely to change ISPs over time, and I'm too small to 
> qualify for PI space, so I choose to number my internal network 
> infrastructure out of private (ULA) space.  In parallel, I also use 
> DHCP, DHCP-PD, etc. to assign subnets of my various PA space to users on 
> various portions of my network (thereby giving them IPv6 address(es) of 
> whichever Internet uplinks are available to them).  (I may also use some 
> form of DHCP to assign PA space to my router interfaces, or I may choose 
> to hide that detail by doing my mesh networking below layer 3, or I may 
> choose to use ULA space there and rewrite the source address of any 
> ULA-sourced packets leaving my network for the Internet.)
> 
> Now let's say I am thinking a little bit bigger than just my 
> neighborhood, and would also like my network to connect to neighboring 
> mesh networks.  (This could fairly easily evolve into an arbitrarily 
> large internetwork enabling disaster-resistant connectivity across 
> neighborhoods, cities, or entire regions.)  In order to facilitate 
> troubleshooting, I elect to use ULA-C space for my network 
> infrastructure, including router interfaces, (and either rewrite source 
> addresses of any packets (presumably ICMP) my routers send out to the 
> Internet, or also assign PA space to each interface with something like 
> DHCP-PD, so that the router can use IPv6 address selection to use a 
> public address for packets destined for public Internet addresses).  As 
> before, I would give out PA subnet(s) to users for Internet 
> connectivity, but I might also elect to give them ULA addresses to 
> communicate with other hosts on my mesh network and neighboring ones.
> 
> In a situation like this, I need to be able to resolve PTRs for hosts 
> using my neighboring networks' ULA space without any prior knowledge 
> about the neighboring wireless network.  If both networks are numbered 
> out of ULA-C space, this is easy: I send my PTR queries to my regular 
> DNS resolver, which has a PA address and Internet connectivity, and can 
> resolve the PTR from the DNS server authoritative for my neighboring 
> wireless network's ULA-C block.
> 
> So, again, I see that ULA-C is a very simple solution to fill a very 
> useful function that cannot be filled by local ULAs alone (at least 
> without adding additional complexity to DNS).  Importantly, this 
> functionality does not depend on ULA-C providing an additional assurance 
> of uniqueness, but on the fact that my block (and its authoritative DNS 
> servers) can be registered, and others can query the registered data.
> 
> As IPv6 adoption takes hold and dynamic wireless networking becomes 
> cheaper and more widespread, I would see this kind of use case, and its 
> many permutations, becoming more and more common.  Can you describe a 
> way to use existing address types available to small networks (PA and 
> ULA-L) and existing DNS technologies to support the requirements listed 
> above?  If not, I would argue that we should complete the process of 
> ULA-C standardization, as it represents the simplest available solution 
> to the problem.
> 
> 
> -Scott
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 07:15:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3VUp-0003gp-Tl; Wed, 27 Jun 2007 07:15:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3VUn-0003XL-F4
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:15:37 -0400
Received: from purgatory.unfix.org ([213.136.24.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3VUC-0005fR-T0
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:15:37 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 34A38140C296;
	Wed, 27 Jun 2007 13:14:58 +0200 (CEST)
Message-ID: <468246B6.3070507@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 12:15:02 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46807C77.2020101@internap.com>
	<46824361.4000300@gmail.com>
In-Reply-To: <46824361.4000300@gmail.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0049674238=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0049674238==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig804124B92C6B593C7C38005F"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig804124B92C6B593C7C38005F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Brian E Carpenter wrote:
> Scott, you say
>=20
>> In a situation like this, I need to be able to resolve PTRs for hosts
>> using my neighboring networks' ULA space
>=20
> Why do you need to do this?

The need can be seen, but the big question is: why does one need it in
the *global* root.

If one is in a non-Internet-connected setup, you will have to also setup
DNS for the, IMHO way more important, forward zones. If one can manage
that, then setting up the reverse is just an extra line in the config.

When one argues "yes but I don't want split DNS and it needs to be in
the global DNS", then simply don't opt for *local* addresses.

Either the ULA-C space is *local* or it is *global*. When it is global,
then you need what the RIR's dub PI. If you can't get PI for your use,
then talk to the RIR's and define a new policy there.


One thing that can be accomplished by the ULA-C draft is to update the
ULA draft, deprecating the L/G bit, making that bit part of the random
pool (letting folks simply select it themselves) and defining that the
reverse in the global root should point to the AS112 servers.

Greets,
 Jeroen


--------------enig804124B92C6B593C7C38005F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCRrYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I9dHAJ9G9LcbiYPWrctVA9p4rw6OwP/Q
RwCdHcaGsdc6597YR5xLFfQTV91NZEg=
=xXef
-----END PGP SIGNATURE-----

--------------enig804124B92C6B593C7C38005F--


--===============0049674238==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0049674238==--




From ipv6-bounces@ietf.org Wed Jun 27 07:16:38 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3VVl-00064K-HA; Wed, 27 Jun 2007 07:16:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3VVj-0005k7-Gr
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:16:35 -0400
Received: from ik-out-1112.google.com ([66.249.90.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3VV8-0005pj-EL
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:16:35 -0400
Received: by ik-out-1112.google.com with SMTP id b32so99761ika
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 04:15:57 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=aXBQFx773/hk2r2v0mfUGko0BT3lz3SSnUnfhBt6259DAkaOsu9hOV75ymfp9DjY1+nflktjmfbcbYYIEM/zABGsYEFctviz7ZJdK7Ds9nXtRMDRniXof6lqVFde0Ft8DbbROY+3sr/qft/AMQXYlofytaikE+NOshQvTRJUo0Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=JtbSJwaLbzlxCSd9VK460aWikSTGgfch2diIrhlRTU5ERFq1Rnn+PCcT9hZxEQ/cdDU1kYchqm1QQsC3NItwax3lI/bayAyNAeqL1rnsASovGEpPrs9FsslTI1PIo5VvvAYAALyMlnI/Gl64+nVNBChZr+LkN29ikeTBnmLmmjI=
Received: by 10.78.170.17 with SMTP id s17mr188403hue.1182942577146;
	Wed, 27 Jun 2007 04:09:37 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id c9sm2457424nfi.2007.06.27.04.09.35
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 04:09:36 -0700 (PDT)
Message-ID: <4682456F.8080600@gmail.com>
Date: Wed, 27 Jun 2007 13:09:35 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
	<Pine.LNX.4.64.0706270041250.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706270041250.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 00:42, Roger Jorgensen wrote:
> On Thu, 21 Jun 2007, james woodyatt wrote:
> <snip>
>>
>> We successfully deprecated site-local unicast addressing by painting 
>> it with the stink of IPv4 network address translation.  However, we 
>> retained the technical consensus that unreachable nodes still need to 
>> be uniquely addressable, and what's more: these unreachable global 
>> scope unicast addresses must be assigned from a registry with a single 
>> global root.
>>
>> My heretical opinion is that the second technical consensus is wrong.  
>> We should deprecate the 'L' bit in the ULA address type and make all 
>> ULA into locally allocated addresses.  That way, we will have carved 
>> off a well-known prefix (like all the other non-routable prefixes) 
>> where nodes are neither uniquely addressable nor reachable on the 
>> public Internet.  I contend the 'L' bit was never a good idea; it was 
>> a placeholder for those wishing to retain network address translation 
>> in IPv6.  There, I said it.

I believe that is a misunderstanding of the L bit in RFC 4193. All
it means is: this address was allocated using the procedure defined
in RFC 4193.

In every other respect it is a no-op and there is no difference between
ULAs defined with L=1 and L=0.

> agree... let's go back to the original RFC defining ULA and remove that 
> bit and using this entire thread over the last few months as a reason 
> why it never should be global unique etc....

Oh, let's undeprecate site local at the same time then and recreate
the mess in its entirety. (I don't think so.)

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 08:13:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3WNq-0007iU-DN; Wed, 27 Jun 2007 08:12:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3WNo-0007dX-Dv
	for ipv6@ietf.org; Wed, 27 Jun 2007 08:12:28 -0400
Received: from smtp.aaisp.net.uk ([81.187.81.51])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3WNo-0008U0-5z
	for ipv6@ietf.org; Wed, 27 Jun 2007 08:12:28 -0400
Received: from 247.254.187.81.in-addr.arpa ([81.187.254.247])
	by smtp.aaisp.net.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.62)
	(envelope-from <elwynd@dial.pipex.com>)
	id 1I3WNE-00063W-7S; Wed, 27 Jun 2007 13:11:52 +0100
Message-ID: <4682546B.5010405@dial.pipex.com>
Date: Wed, 27 Jun 2007 13:13:31 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <3CC9E5E1-0095-4273-BF9E-FA0273F5B86C@ca.afilias.info>
	<4682354C.5010906@gmail.com>
In-Reply-To: <4682354C.5010906@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-deprecate-01-01-candidate-02
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I also think this is in good shape.

One addition that would be useful is to reference the v6ops security 
overview (draft-ietf-v6ops-security-overview-06.txt currently in AUTH48 
and about to be published as RFC 4942).
This also discusses security issues with RH0 (including the 
amplification attack) and routing headers in general.

Regards,
Elwyn

Brian E Carpenter wrote:
> FWIW, my opinion is 'ship it'. It seems like time
> to get a formal readout of (rough) WG consensus
> on this.
>
>     Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 08:18:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3WTQ-0004LY-FN; Wed, 27 Jun 2007 08:18:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3WTO-0004LL-I1
	for ipv6@ietf.org; Wed, 27 Jun 2007 08:18:14 -0400
Received: from netcore.fi ([193.94.160.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3WTO-0000YU-1g
	for ipv6@ietf.org; Wed, 27 Jun 2007 08:18:14 -0400
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id l5RCHa5n024194;
	Wed, 27 Jun 2007 15:17:36 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id l5RCHZIF024191;
	Wed, 27 Jun 2007 15:17:36 +0300
Date: Wed, 27 Jun 2007 15:17:35 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <467A3C38.8090606@gmail.com>
Message-ID: <Pine.LNX.4.64.0706271510340.23111@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com> <467A3C38.8090606@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.90.3/3538/Wed Jun 27 03:16:51 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED, AWL,
	BAYES_00 autolearn=ham version=3.1.9
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ipv6@ietf.org
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Catching up on email..

On Thu, 21 Jun 2007, Brian E Carpenter wrote:
...
> I see only downsides (unnecessary costs and useless policy discussions)
> in treating this as anything but a purely technical matter. Let's leave
> the policy discussions for matters where fairness and route scaling
> are at stake. ULAs are plentiful (so there is no fairness issue) and
> not WAN-routeable (so there is no route scaling issue).
>
> If we don't do this, ULA-C has no noticeable advantage over PI
> and we should just forget it IMHO.

Brian, it would be useful if you could elaborate a bit on "not 
WAN-routeable".  Some people seem to consider that as one of the major 
reasons how ULA differs from PI, and I guess that leads to conclude 
that ULAs have no significant impact on DFZ whereas PI might.

Specifically, I do not see any (feasible) way how router vendors could 
by default drop ULA packets at some (undefined) border.  This is for 
two reasons; 1) it is not algorithmically possible to define which 
interfaces form "ULA border" where such a filter should be applied 
automatically, and 2) most vendors seem to have a policy that changes 
to default behaviour (could affect existing deployments) are 
unacceptable or at least very strongly frowned upon.

Why do you believe ULA addresses are intrinsically not WAN routable? 
Is there something I'm missing?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 09:13:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3XJy-0000bc-Bv; Wed, 27 Jun 2007 09:12:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3XJw-0000bT-SM
	for ipv6@ietf.org; Wed, 27 Jun 2007 09:12:33 -0400
Received: from wr-out-0506.google.com ([64.233.184.233])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3XJG-00072E-U2
	for ipv6@ietf.org; Wed, 27 Jun 2007 09:12:32 -0400
Received: by wr-out-0506.google.com with SMTP id 70so100505wra
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 06:11:50 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=r6XoiKaWj8N4R9JigTG3aLvp6wEJ5lAWfDzjATumRh9eijXs/Y9Dy0OMiiOrxdHhCNYZHZZpjA7tlQn9quqibcNY9PjVvoA9zc+d8q6LUPzeEFqpN1iHz00t7eQl0YsHjZX1QtGTJBuHkYT4yEToOP5AL24VMIR3hN1CexeqzYo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=pFKhcXKNBn5K84r1LxGOKaYJRzyTbzr0FkyHrR7VAZJ0o7sKGmia9yC7WFIswoUC5vlta/5LxSJgXCVAjbk1MZEAFwvzua6mtpt7ihlquSK/KJD+37HEaXOgZBWAGy1sNxid8S6QSFoErYRRkIXLCYARcqNzo0+Li8cC2oLER+s=
Received: by 10.78.149.15 with SMTP id w15mr249484hud.1182949909624;
	Wed, 27 Jun 2007 06:11:49 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id d24sm5851367nfh.2007.06.27.06.11.48
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 06:11:49 -0700 (PDT)
Message-ID: <46826215.10609@gmail.com>
Date: Wed, 27 Jun 2007 15:11:49 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com>
	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>
	<46785A65.7060505@internap.com>
	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>
	<46796246.4050705@internap.com> <467A3C38.8090606@gmail.com>
	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0706271510340.23111@netcore.fi>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ipv6@ietf.org
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 14:17, Pekka Savola wrote:
> Catching up on email..
> 
> On Thu, 21 Jun 2007, Brian E Carpenter wrote:
> ...
>> I see only downsides (unnecessary costs and useless policy discussions)
>> in treating this as anything but a purely technical matter. Let's leave
>> the policy discussions for matters where fairness and route scaling
>> are at stake. ULAs are plentiful (so there is no fairness issue) and
>> not WAN-routeable (so there is no route scaling issue).
>>
>> If we don't do this, ULA-C has no noticeable advantage over PI
>> and we should just forget it IMHO.
> 
> Brian, it would be useful if you could elaborate a bit on "not 
> WAN-routeable".  Some people seem to consider that as one of the major 
> reasons how ULA differs from PI, and I guess that leads to conclude that 
> ULAs have no significant impact on DFZ whereas PI might.
> 
> Specifically, I do not see any (feasible) way how router vendors could 
> by default drop ULA packets at some (undefined) border.  This is for two 
> reasons; 1) it is not algorithmically possible to define which 
> interfaces form "ULA border" where such a filter should be applied 
> automatically, and 2) most vendors seem to have a policy that changes to 
> default behaviour (could affect existing deployments) are unacceptable 
> or at least very strongly frowned upon.
> 
> Why do you believe ULA addresses are intrinsically not WAN routable? Is 
> there something I'm missing?

We can argue about the meaning of "intrinsically" I guess. But what I mean
is that they are /48s and I don't expect to see /48s routed globally.
Architecturally, they are certainly routeable (and so are /128s).
But I am sure they will be filtered.

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 10:07:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3YBU-000289-Ko; Wed, 27 Jun 2007 10:07:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3YBT-000281-EE
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:07:51 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3YAb-0004wg-30
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:07:51 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 473FB140C215;
	Wed, 27 Jun 2007 16:06:55 +0200 (CEST)
Message-ID: <46826F02.8000507@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 15:06:58 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
In-Reply-To: <46826215.10609@gmail.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0373719545=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0373719545==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig305D87A376BB1F0803200B36"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig305D87A376BB1F0803200B36
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Brian E Carpenter wrote:
[..]
> We can argue about the meaning of "intrinsically" I guess. But what I m=
ean
> is that they are /48s and I don't expect to see /48s routed globally.

Quickly checking http://www.sixxs.net/tools/grh/, taking a rather long
raw-dump of it, cut&pasting it into a textfile and doing some shell
magic, I got the following nice prefixes (full list below)

    639 32
    216 48
     32 35
     30 40
    216 48
      1 52
      2 56
     87 64
      3 124
      7 126
      8 128

I therefor can thus easily conclude that filtering is not happening that
heavily at all. /48's actually will EASILY pass most filters. Most of
the /64's are IX prefixes btw. Until we get certificates in BGP and
until routing strain is not being felt and operators don't want to
filter having a /48 from any block will be easy. Most ISP's do only
accept 2000::/3 indeed though.

Btw, that covered 1088 different prefixes using 89441 possible paths and
only 814 unique ASN's in those paths. So already there are a couple of
ASN's announcing multiple prefixes: 1088*100/814 =3D 13.3% overhead there=
=2E
If thus every active-ish ASN today got a prefix, we would end up with
40k + 13.3% =3D~ 53k prefixes. Still a lot lower than IPv4, but in that
setup I am assuming nobody will be doing TE, and people will do TE.

> Architecturally, they are certainly routeable (and so are /128s).
> But I am sure they will be filtered.

I have also seen /128's globally being routed over multiple ASN's see
below the /128's are present.

Greets,
 Jeroen

--
      1 16		(2002::/16 :)
      2 19
      3 20
      3 21
      1 22
      3 24
      2 26
      2 27
      5 28
      1 29
      2 30
      1 31
    639 32
     10 33
      3 34
     32 35
      1 36
      1 39
     30 40
      4 42
      1 43
      3 44
      5 45
      7 46
      1 47
    216 48
      1 52
      2 56
     87 64
      3 124
      7 126
      8 128


--------------enig305D87A376BB1F0803200B36
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCbwIuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I6q+AJwIkBFc4xD2yXIULfrdOPhxSzMN
mACeKyfDNY26czgFOwZRZxCF1Rc+ckE=
=Nuaz
-----END PGP SIGNATURE-----

--------------enig305D87A376BB1F0803200B36--


--===============0373719545==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0373719545==--




From ipv6-bounces@ietf.org Wed Jun 27 10:33:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3YZK-0006oF-Ar; Wed, 27 Jun 2007 10:32:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3YZI-0006lo-3E
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:32:28 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3YYc-0002v3-5V
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:32:28 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 27 Jun 2007 09:31:31 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
In-Reply-To: <CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace3jnwXjzHMCVNVR5SLe90wXXPi8gBNdV+g
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: RE: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I keep thinking that all of this sounds like people looking for default
solutions to custom problems.  If you want to have a custom connection
between specific private networks there will necessarily be some custom
configuration.  A plug-and-play solution just will not work without
adding rediculous layers of complexity to the method.

Early network and protocol designers worked very hard to keep K.I.S.S.
as a basic principle.  Lower complexity will of course mean reduced
functionality, but it also means increased reliability and easier
healing.

It is sort of like the operating system on your workstation..  if you
want to preload every possible driver for every possible piece of
hardware that is certainly possible, and may even make things easier for
someone.  It will also make everyone's system requirements huge,
increase boot time drastically, affect performance and add many
administrative requirements for patches and updates.

The basic network protocols should be as simple as absolutely possible,
with the minimum core set functionality required.  If end users want
added features then they need to figure out how to do that within the
protocol framework.

I have yet to see a consensus that ULA-C is a basic required capability,
though I have seen cases explained where it would be useful to a small
number of users.  The decision to make is whether the benefit to the few
who would take advantage of it is worth the cost to the rest of the
world.

The problem I see with having small ULA-C allocations is that as people
move around geographically those allocations will lose aggrebility.
Until everyone in the world has big iron routers (When you want to send
me mine for free I will be happy to accept it) many or most network
administrators will be forced to filter small routes to protect their
route processors.  This may also apply to the root DNS servers.  They
too must have some limit of routes they can serve.
=20

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Monday, June 25, 2007 8:07 PM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> On Jun 25, 2007, at 17:01, Geoff Huston wrote:
> >
> > i.e. if we all pick numbers and stuff them into the DNS,=20
> then by the=20
> > time the 1,240,000 selection had taken place the probability that a=20
> > collision has occurred exceeds 0.5
>=20
> That's only a problem for people who have to pick a number=20
> that collides with absolutely none of the other 1,240,000=20
> numbers.  I think no one will ever have to do that, and=20
> *moreover* I think that anybody who *does* think they'll have=20
> to do that has some explaining to do before we worry about=20
> their problem.
>=20
> Who's going to do that, and why?  By the way, that is *NOT* a=20
> rhetorical question.  I really want to know the answer.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 10:53:50 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Ytj-0008N8-SW; Wed, 27 Jun 2007 10:53:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Yth-0008Mb-3n
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:53:33 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Ysy-0000d8-Ht
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:53:33 -0400
Received: by ug-out-1314.google.com with SMTP id k3so936075ugf
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 07:52:47 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=OR8ZB5On0C/OC2Myuddd8iVvLGaUAZMcRyVyoSQF6t9IpzWCvTeXpptGSyswM0cvFMFWlpszrwC+82RU/0b6do6sqdGB4gxjmx88ThgWbcMoDylS0fKnysEH8dnvVdo6nQfnwJW3iyrytddKTA5Au/JFyeX5JlVcRJufyOoQhzM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=YygGzLQbTJ5GTN4YJUo/NA9bWmzVVJP5Szec+yRhifxx4rJYDWCr2KwHRMc2LYF3nxCecYgIjBYAFeA7+fWEPeLmt9K8/o6pxsl0L1I47dVfJHKNCF3GUuWISIYzA4tnHuDZmQl2/oFqRixOy4Sw79Xl/McyfeX2Xf7zp1CiIcs=
Received: by 10.66.242.5 with SMTP id p5mr1220435ugh.1182955967543;
	Wed, 27 Jun 2007 07:52:47 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id o30sm4940398ugd.2007.06.27.07.52.46
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 07:52:46 -0700 (PDT)
Message-ID: <468279BE.2030003@gmail.com>
Date: Wed, 27 Jun 2007 16:52:46 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
In-Reply-To: <46826F02.8000507@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thanks for the facts. It does seem like a childhood illness
though - obviously it isn't sustainable as IPv6 grows up.

     Brian

On 2007-06-27 16:06, Jeroen Massar wrote:
> Brian E Carpenter wrote:
> [..]
>> We can argue about the meaning of "intrinsically" I guess. But what I mean
>> is that they are /48s and I don't expect to see /48s routed globally.
> 
> Quickly checking http://www.sixxs.net/tools/grh/, taking a rather long
> raw-dump of it, cut&pasting it into a textfile and doing some shell
> magic, I got the following nice prefixes (full list below)
> 
>     639 32
>     216 48
>      32 35
>      30 40
>     216 48
>       1 52
>       2 56
>      87 64
>       3 124
>       7 126
>       8 128
> 
> I therefor can thus easily conclude that filtering is not happening that
> heavily at all. /48's actually will EASILY pass most filters. Most of
> the /64's are IX prefixes btw. Until we get certificates in BGP and
> until routing strain is not being felt and operators don't want to
> filter having a /48 from any block will be easy. Most ISP's do only
> accept 2000::/3 indeed though.
> 
> Btw, that covered 1088 different prefixes using 89441 possible paths and
> only 814 unique ASN's in those paths. So already there are a couple of
> ASN's announcing multiple prefixes: 1088*100/814 = 13.3% overhead there.
> If thus every active-ish ASN today got a prefix, we would end up with
> 40k + 13.3% =~ 53k prefixes. Still a lot lower than IPv4, but in that
> setup I am assuming nobody will be doing TE, and people will do TE.
> 
>> Architecturally, they are certainly routeable (and so are /128s).
>> But I am sure they will be filtered.
> 
> I have also seen /128's globally being routed over multiple ASN's see
> below the /128's are present.
> 
> Greets,
>  Jeroen
> 
> --
>       1 16		(2002::/16 :)
>       2 19
>       3 20
>       3 21
>       1 22
>       3 24
>       2 26
>       2 27
>       5 28
>       1 29
>       2 30
>       1 31
>     639 32
>      10 33
>       3 34
>      32 35
>       1 36
>       1 39
>      30 40
>       4 42
>       1 43
>       3 44
>       5 45
>       7 46
>       1 47
>     216 48
>       1 52
>       2 56
>      87 64
>       3 124
>       7 126
>       8 128
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 10:56:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3YwE-00028P-L9; Wed, 27 Jun 2007 10:56:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3YwC-000288-Qz
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:56:08 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3YvR-0000tb-1s
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:56:08 -0400
Received: by ug-out-1314.google.com with SMTP id k3so938186ugf
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 07:55:20 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ZMlly3YJKb+4Q9xQ7ROM6cjGEfeBYVig4XcB/KSKzqZN4Ob9Nex35ud6LfyoprhnVLnetm5ZdXP+/AAGRDfWkTqUd++MjHIOjarqTwFMHkIuOeCfl7ykk5HVWxgUw/yqVacIWb3CXzFFVeAL5mBDjUC3WCWGjGFC6F4WUrBiVjs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=Xm737vSjxwH7lMqchKkgGz2gYASGj2jl34JtdLVthQEaSVhKt4dfSPJpUYH5DqBlD+jMsSbVGk0MVQcUv9vdTWBBCyVE3XSch/QdJ9Bba8Dv08IiBAaInCKnRNN2pojRp4BsMr5lME+Do1+flxdmEYiZcMB/kyzBPGl8DgP299w=
Received: by 10.67.15.17 with SMTP id s17mr201604ugi.1182956119992;
	Wed, 27 Jun 2007 07:55:19 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id j1sm6611032ugf.2007.06.27.07.55.18
	(version=SSLv3 cipher=RC4-MD5); Wed, 27 Jun 2007 07:55:19 -0700 (PDT)
Message-ID: <46827A57.7030203@gmail.com>
Date: Wed, 27 Jun 2007 16:55:19 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Kevin Kargel <kkargel@polartel.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
In-Reply-To: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 16:31, Kevin Kargel wrote:
...
> The problem I see with having small ULA-C allocations is that as people
> move around geographically those allocations will lose aggrebility.

I don't understand your comment. No ULA prefix aggregates ever - they
will always be specific routes, and ULA-C is no different in that respect.

     Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 10:58:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Yyf-0004tk-3z; Wed, 27 Jun 2007 10:58:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Yyd-0004t9-O9
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:58:39 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Yxx-0001ZQ-Vh
	for ipv6@ietf.org; Wed, 27 Jun 2007 10:58:39 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id CB507140C198;
	Wed, 27 Jun 2007 16:57:56 +0200 (CEST)
Message-ID: <46827AF8.1070602@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 15:58:00 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
	<468279BE.2030003@gmail.com>
In-Reply-To: <468279BE.2030003@gmail.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1793996447=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1793996447==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig6B0A24A2B506E09F71FACEB6"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6B0A24A2B506E09F71FACEB6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Brian E Carpenter wrote:
> Thanks for the facts. It does seem like a childhood illness
> though - obviously it isn't sustainable as IPv6 grows up.

It indeed most likely won't in the very long term.

But hopefully the id/loc mechanisms or shim6 or similar solutions will
make sure that the "IPv6 DFZ" will only contain PA prefixes at a certain
point. Which will limit the number of routes there significantly and
still providing end-sites with full flexibility to change their
up/downstreams on the fly.

At a point where the IPv6 DFZ grows too large, ISP's will start
filtering smaller prefixes (>=3D/48), and they will drop off the Internet=
,
then immediately these sites will need to use id/loc. Hopefull the
forced part never happens and people simply realize the constraints that
we are then working in.

It might also happen that vendors find ways to make it scalable and then
everything is fine too. Up to that point though, there should not be an
artificial barrier for end-sites to be able to get globally unique
address space. The other point that they actually fit in the routing
tables is a problem that can be solved with the above.

Greets,
 Jeroen


--------------enig6B0A24A2B506E09F71FACEB6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCevguFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I0m6AJ9WEg3ABPnEYkXjBDhCMMzv1tqn
IwCfQlYDQdGH+vka68g/sANgAnRmuC4=
=I+ml
-----END PGP SIGNATURE-----

--------------enig6B0A24A2B506E09F71FACEB6--


--===============1793996447==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1793996447==--




From ipv6-bounces@ietf.org Wed Jun 27 11:10:05 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Z9b-00074y-8F; Wed, 27 Jun 2007 11:09:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Z9a-00074s-9b
	for ipv6@ietf.org; Wed, 27 Jun 2007 11:09:58 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Z8i-0004l7-B9
	for ipv6@ietf.org; Wed, 27 Jun 2007 11:09:58 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l5RFAvGv002883
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 10:10:57 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 10:09:03 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 10:09:03 -0500
Message-ID: <46827D36.7050307@ericsson.com>
Date: Wed, 27 Jun 2007 11:07:34 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: ipv6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2007 15:09:03.0432 (UTC)
	FILETIME=[1938FC80:01C7B8CD]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: Privacy Addresses AUTH48 Changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Folks,
   I would like to make the following editorial change to the upcoming 
Privacy Addresses RFC.

I would like to add the following sentence to section 3.2.1 step 4

This list currently includes the reserved anycast interface identifiers 
listed in [RFC2526]. This list may be expanded in the future to include 
further interface identifiers.

after this sentence

Compare the generated identifier against a list of
reserved interface identifiers and to those already
assigned to an address on the local device.

Please let me know by June 29 2007 if you have any objections.

Cheers
Suresh

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 12:32:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3aRF-0003rQ-H6; Wed, 27 Jun 2007 12:32:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3aRE-0003pP-A4
	for ipv6@ietf.org; Wed, 27 Jun 2007 12:32:16 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3aQX-0005KZ-2f
	for ipv6@ietf.org; Wed, 27 Jun 2007 12:32:16 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 63252A9DAED
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 09:31:32 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 4F92F100B5
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 09:31:32 -0700 (PDT)
X-AuditID: 11807124-a1ce0bb0000007e2-e4-468290e4b1c9
Received: from [17.151.75.59] (int-si-a.apple.com [17.128.113.41])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 21E2310097
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 09:31:32 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <4682456F.8080600@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>
	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>
	<467853B0.5010806@internap.com> <467A39E2.3020303@gmail.com>
	<467AA083.6070102@internap.com> <28803.1182449010@sa.vix.com>
	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
	<Pine.LNX.4.64.0706270041250.29317@chandra.student.uit.no>
	<4682456F.8080600@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C71D9F2D-C489-492F-959D-771DBCAC9ECB@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Wed, 27 Jun 2007 09:31:29 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 27, 2007, at 04:09, Brian E Carpenter wrote:
> On 2007-06-27 00:42, Roger Jorgensen wrote:
>> On Thu, 21 Jun 2007, james woodyatt wrote:
>> <snip>
>>>
>>> We successfully deprecated site-local unicast addressing by  
>>> painting it with the stink of IPv4 network address translation.   
>>> However, we retained the technical consensus that unreachable  
>>> nodes still need to be uniquely addressable, and what's more:  
>>> these unreachable global scope unicast addresses must be assigned  
>>> from a registry with a single global root.
>>>
>>> My heretical opinion is that the second technical consensus is  
>>> wrong.  We should deprecate the 'L' bit in the ULA address type  
>>> and make all ULA into locally allocated addresses.  That way, we  
>>> will have carved off a well-known prefix (like all the other non- 
>>> routable prefixes) where nodes are neither uniquely addressable  
>>> nor reachable on the public Internet.  I contend the 'L' bit was  
>>> never a good idea; it was a placeholder for those wishing to  
>>> retain network address translation in IPv6.  There, I said it.
>
> I believe that is a misunderstanding of the L bit in RFC 4193. All  
> it means is: this address was allocated using the procedure defined  
> in RFC 4193.  In every other respect it is a no-op and there is no  
> difference between ULAs defined with L=1 and L=0.

I don't think I've ever been confused about that.

>> agree... let's go back to the original RFC defining ULA and remove  
>> that bit and using this entire thread over the last few months as  
>> a reason why it never should be global unique etc....
>
> Oh, let's undeprecate site local at the same time then and recreate  
> the mess in its entirety. (I don't think so.)

Please, in the name of all that is hallowed, please, let's leave site- 
local in the oubliette where it belongs.

I merely contend-- albeit heretically-- that "L=0" in RFC 4193 is  
nonsense.  We should hand fc00::/8 back to IANA and revise RFC 4193  
so that fd00::/8 is the ULA prefix identifier, where all addresses  
are allocated according to to the procedure currently defined, have  
global scope, are not routed in the DFZ and receive synthetic reverse  
delegations in 0.0.d.f.ip6.arpa to an anycast address reserved by IANA.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 12:56:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3aoM-0006lf-WA; Wed, 27 Jun 2007 12:56:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3aoL-0006la-LR
	for ipv6@ietf.org; Wed, 27 Jun 2007 12:56:09 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3aoA-0002rd-T0
	for ipv6@ietf.org; Wed, 27 Jun 2007 12:56:09 -0400
Received: from [64.213.227.189] (189.227.sj.icannsanjuan.pr [64.213.227.189])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5RGtsgV012466
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 27 Jun 2007 09:55:55 -0700
In-Reply-To: <468279BE.2030003@gmail.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
	<468279BE.2030003@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Wed, 27 Jun 2007 12:55:48 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 27 Jun 2007, at 10:52am, Brian E Carpenter wrote:

> Thanks for the facts. It does seem like a childhood illness
> though - obviously it isn't sustainable as IPv6 grows up.

Most childhood illnesses go away but the /48 assignments made by ARIN  
and APNIC are permanent. What incentive is there - or will there be -  
for those organisations to return their prefixes and take PA space  
from one or more of their upstream providers? Presumably that  
incentive is what will keep ULA-C prefixes within a single site.

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 13:04:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3awB-0008K8-6a; Wed, 27 Jun 2007 13:04:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3aw9-0008Ev-Rx
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:04:13 -0400
Received: from purgatory.unfix.org ([213.136.24.43])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3aw9-0005Mc-DM
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:04:13 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 3FBCB140C211;
	Wed, 27 Jun 2007 19:03:07 +0200 (CEST)
Message-ID: <4682984E.2090500@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 18:03:10 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
	<468279BE.2030003@gmail.com>
	<980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
In-Reply-To: <980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1201101368=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1201101368==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig7A323078C59F436F8E7E3A11"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7A323078C59F436F8E7E3A11
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Leo Vegoda wrote:
> On 27 Jun 2007, at 10:52am, Brian E Carpenter wrote:
>=20
>> Thanks for the facts. It does seem like a childhood illness
>> though - obviously it isn't sustainable as IPv6 grows up.
>=20
> Most childhood illnesses go away but the /48 assignments made by ARIN
> and APNIC are permanent. What incentive is there - or will there be -
> for those organisations to return their prefixes and take PA space from=

> one or more of their upstream providers?

ISPs can then force them. "Oh you want to announce a /48? Cool, but show
us the money". It will then be cheaper to use their PA block on the
'outside' as a Locator, while using their own PI block as a Identifier.
Filtering by the majority of the ISP's, accepting only /32's or for that
matter only blocks from PA space, resolves all of that, with a little
bit of force but it will work.

As such the space doesn't need to be returned and the space can be used
now nicely in the DFZ, and when the id/loc mechanisms come along people
can slowly migrate to those mechanisms. This even avoids any renumbering
and thus should make a lot of people really happy.

> Presumably that incentive is what will keep ULA-C prefixes within a sin=
gle site.

In effect one can indeed also use ULA-C kind of addresses as
"Identifiers" as they are truly globally unique just like PI, but that
is the whole point why ULA-C is futile: they _are_ just like PI ;)
Except that they will be carved out of a special prefix and handled in a
strange way. Also as they are not "Internet addresses" but intended for
disconnected sites and thus should never traverse the Internet except
for in a VPN in the first place.

Greets,
 Jeroen



--------------enig7A323078C59F436F8E7E3A11
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCmE8uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I55UAKCbCdsw2Hc75yHMkkWNtezjuu0p
EQCfcVjOdZ6dcPH1LH87wJXS4EFxmH8=
=TJtY
-----END PGP SIGNATURE-----

--------------enig7A323078C59F436F8E7E3A11--


--===============1201101368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1201101368==--




From ipv6-bounces@ietf.org Wed Jun 27 13:16:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3b7c-0001xg-9G; Wed, 27 Jun 2007 13:16:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3b7a-0001uT-GT
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:16:02 -0400
Received: from purgatory.unfix.org ([213.136.24.43])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3b7Z-00067C-WD
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:16:02 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 454CA140C1A3;
	Wed, 27 Jun 2007 19:16:00 +0200 (CEST)
Message-ID: <46829B53.7060303@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 18:16:03 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>	<200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>	<Pine.LNX.4.64.0706270041250.29317@chandra.student.uit.no>	<4682456F.8080600@gmail.com>
	<C71D9F2D-C489-492F-959D-771DBCAC9ECB@apple.com>
In-Reply-To: <C71D9F2D-C489-492F-959D-771DBCAC9ECB@apple.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1193514244=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1193514244==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigF9A58BC833C01BB7C71DFB6C"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF9A58BC833C01BB7C71DFB6C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

james woodyatt wrote:
[..]

> I merely contend-- albeit heretically-- that "L=3D0" in RFC 4193 is
> nonsense. We should hand fc00::/8 back to IANA and revise RFC 4193 so
> that fd00::/8 is the ULA prefix identifier, where all addresses are
> allocated according to to the procedure currently defined, have global
> scope, are not routed in the DFZ and receive synthetic reverse
> delegations in 0.0.d.f.ip6.arpa to an anycast address reserved by IANA.=


The Local/Global bit is correct in the specification and also what
differentiates the two spaces, the L bit set (thus fd00::/8 RFC4193)
means that the prefix is locally generated and not 100% guaranteed
unique, although 2^-40 is pretty close to that. This is exactly what we
have now. Without the L bit (thus fc00::/8 and proposed ULA-C) we
require some kind of registry to intervene and keep a list to make sure
that there is no collision.

I agree on the handing back of fd00::/8. The need for an address space
like ULA-C is covered by PI already(*1). There are a few corner cases
like "very small sites" but these can be resolved with proper RIR
policies. It is IMHO very wrong that there are folks who want to
restrict RIR's providing address space to end-sites due to 'routing
table' issues which are not existent yet and of which various vendors
have mentioned already that it is and will not be a problem.


What you thus propose above is adding the synthetic 0.0.d.f.ip6.arpa
method as an addition to RFC4193.

Although I partially like the idea it only solves the reverse problem.
It does not solve the forward problem. Because of the latter one still
has to configure DNS on both (or all of the other) connecting sites
anyway to link up these address spaces for the forward zones. One can
then also easily add this for reverses.

This then also doesn't deviate from current practice in both IPv4 and
IPv6. It also doesn't squander a part (/64?) of the /48. Randomly
picking an address in that /48 makes the whole /48 useless as people
can't depend on the full /48 being theirs anymore to slash up(*2).
Also a lot of deployed IPv6 sites use the first /48 for their first
network already or for similar purposes. Next to that there will be at
some point an expectancy that the same synthetic mechanism exists for
the rest of the ip6.arpa zone.


*1 =3D If one really wanted to one could simply become LIR, request a /32=
,
then started providing /48's to their customers, who would be people who
simply wanted a chunk of address space. This solves *ALL* this hassle
about ULA-C. The LIR could be setup as a join venture owned by the users
of the address space, thus as long as at least one of them has some cash
they can keep the LIR running and keep the address space.


*2 =3D as a side note, for SixXS we provide in general two sizes of
prefixes: /64 which is used for tunnels and /48 which is used for
subnets. The /48 is routed fully to the user, as such they can do
anything they want with it, chunk it up in any way possible. If they
then ever move to another ISP they can use the exact name numberplan.
The only 'renumbering pain' left is locating where they have all the
first 48 bits stored and changing those.

Greets,
 Jeroen


--------------enigF9A58BC833C01BB7C71DFB6C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCm1MuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I0q+AKCFBAE2dAU0SDtc65xESnLNqwGs
PQCfRg5Sd8TrxQ4LjWrWL7pfSMHKcm4=
=zbiU
-----END PGP SIGNATURE-----

--------------enigF9A58BC833C01BB7C71DFB6C--


--===============1193514244==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1193514244==--




From ipv6-bounces@ietf.org Wed Jun 27 13:19:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3bB1-0004N0-Bh; Wed, 27 Jun 2007 13:19:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bB0-0004Go-46
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:19:34 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3bAz-0006M0-SD
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:19:34 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5RHJAgf027131
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 27 Jun 2007 10:19:11 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5RHJA3v015847; Wed, 27 Jun 2007 10:19:10 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5RHJ1ed015408; Wed, 27 Jun 2007 10:19:06 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 10:19:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Jun 2007 10:19:04 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CC@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <4682984E.2090500@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ULA and WAN-routability
Thread-Index: Ace43VUVE3VeYkFdT06CUPG5pIgPuAAAULhA
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com><467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi><46826215.10609@gmail.com><46826F02.8000507@spaghetti.zurich.ibm.com><468279BE.2030003@gmail.com><980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
	<4682984E.2090500@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>, "Leo Vegoda" <leo.vegoda@icann.org>
X-OriginalArrivalTime: 27 Jun 2007 17:19:05.0749 (UTC)
	FILETIME=[43C41450:01C7B8DF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Pekka Savola <pekkas@netcore.fi>
Subject: RE: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> In effect one can indeed also use ULA-C kind of addresses as
> "Identifiers" as they are truly globally unique just like PI, but that
> is the whole point why ULA-C is futile: they _are_ just like PI ;)
> Except that they will be carved out of a special prefix and=20
> handled in a
> strange way. Also as they are not "Internet addresses" but=20
> intended for
> disconnected sites and thus should never traverse the Internet except
> for in a VPN in the first place.

Also except that they are attainable by very small sites at a
(presumably) nominal cost. (Plus, the "except for in a VPN" is
likely to be good enough for the kinds of connections ULA-C
sites will want to make.)

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 13:50:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3beY-0006b2-Tz; Wed, 27 Jun 2007 13:50:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3beX-0006ZO-IF
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:50:05 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3bdu-0006Zk-0u
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:50:05 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Wed, 27 Jun 2007 12:49:24 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A0631410667070B0@mail>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CC@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ULA and WAN-routability
Thread-Index: Ace43VUVE3VeYkFdT06CUPG5pIgPuAAAULhAAADqpGA=
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: RE: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Everything comes at some cost.  Small sites will be able to get PA from
their providers.  The 'cost' will be renumbering if they change
providers. =20

With ULA-C the cost will be in administration.  ULA-C will have the same
administrative load as PI and PA space, so I don't understand why the
cost would be cheaper.  In fact if ULA-C is announcable via DNS the
aggregate cost of managing many small allocation blocks at the root DNS
servers will be higher than managing the relatively fewer large blocks
of PI/PA, so in reality ULA-C costs should be the same or greater.  The
issue is not cost per IP address but cost per database entry.

=20

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> Sent: Wednesday, June 27, 2007 12:19 PM
> To: Jeroen Massar; Leo Vegoda
> Cc: ipv6@ietf.org; Brian E Carpenter; Pekka Savola
> Subject: RE: ULA and WAN-routability
>=20
> > In effect one can indeed also use ULA-C kind of addresses as=20
> > "Identifiers" as they are truly globally unique just like=20
> PI, but that=20
> > is the whole point why ULA-C is futile: they _are_ just like PI ;)=20
> > Except that they will be carved out of a special prefix and=20
> handled in=20
> > a strange way. Also as they are not "Internet addresses"=20
> but intended=20
> > for disconnected sites and thus should never traverse the Internet=20
> > except for in a VPN in the first place.
>=20
> Also except that they are attainable by very small sites at a
> (presumably) nominal cost. (Plus, the "except for in a VPN"=20
> is likely to be good enough for the kinds of connections=20
> ULA-C sites will want to make.)
>=20
> Fred
> fred.l.templin@boeing.com
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 13:57:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3bm0-00071e-A2; Wed, 27 Jun 2007 13:57:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bly-0006si-TZ
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:57:46 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3blu-0008NG-Fz
	for ipv6@ietf.org; Wed, 27 Jun 2007 13:57:46 -0400
Received: from [64.213.227.189] (189.227.sj.icannsanjuan.pr [64.213.227.189])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5RHvcrH012838
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 27 Jun 2007 10:57:40 -0700
In-Reply-To: <4682984E.2090500@spaghetti.zurich.ibm.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
	<468279BE.2030003@gmail.com>
	<980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
	<4682984E.2090500@spaghetti.zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B3E118BE-5FC4-45B3-9547-40241459771E@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Wed, 27 Jun 2007 13:57:32 -0400
To: Jeroen Massar <jeroen@unfix.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 27 Jun 2007, at 1:03pm, Jeroen Massar wrote:

[...]

>> Most childhood illnesses go away but the /48 assignments made by ARIN
>> and APNIC are permanent. What incentive is there - or will there be -
>> for those organisations to return their prefixes and take PA space  
>> from
>> one or more of their upstream providers?
>
> ISPs can then force them. "Oh you want to announce a /48? Cool, but  
> show
> us the money". It will then be cheaper to use their PA block on the
> 'outside' as a Locator, while using their own PI block as a  
> Identifier.
> Filtering by the majority of the ISP's, accepting only /32's or for  
> that
> matter only blocks from PA space, resolves all of that, with a little
> bit of force but it will work.

I don't remember many ISPs trying to force their customers with  
several classful assignments to renumber into a single PA assignment.  
Why do you think ISPs will try and force renumber (or re-prefixing)  
costs on their existing customers?

Regards,

-- 
Leo Vegoda
IANA Numbers Liaison

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 14:05:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3btL-0005st-R5; Wed, 27 Jun 2007 14:05:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3btJ-0005si-5v
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:05:21 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3bt3-0002Ul-2r
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:05:21 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5RI4xYk000028
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 27 Jun 2007 13:05:04 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5RI4vNn019188; Wed, 27 Jun 2007 11:04:57 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5RI4QB7017745; Wed, 27 Jun 2007 11:04:27 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 11:04:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Jun 2007 11:04:23 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CE@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <70DE64CEFD6E9A4EB7FAF3A0631410667070B0@mail>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ULA and WAN-routability
Thread-Index: Ace43VUVE3VeYkFdT06CUPG5pIgPuAAAULhAAADqpGAAAIbecA==
References: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CC@XCH-NW-7V2.nw.nos.boeing.com>
	<70DE64CEFD6E9A4EB7FAF3A0631410667070B0@mail>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Kevin Kargel" <kkargel@polartel.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 27 Jun 2007 18:04:24.0303 (UTC)
	FILETIME=[98267FF0:01C7B8E5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: 
Subject: RE: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Everything comes at some cost.  Small sites will be able to=20
> get PA from
> their providers.  The 'cost' will be renumbering if they change
> providers.

But, very small sites that get ULA-Cs will realize the
benefit of prefix portability and with no routing table
scaling issues in the DFZ. =20
=20
> With ULA-C the cost will be in administration.  ULA-C will=20
> have the same
> administrative load as PI and PA space, so I don't understand why the
> cost would be cheaper.

I thought the ULA-C registry was supposed to be something
very simple like a robot.

> In fact if ULA-C is announcable via DNS the
> aggregate cost of managing many small allocation blocks at=20
> the root DNS
> servers will be higher than managing the relatively fewer large blocks
> of PI/PA, so in reality ULA-C costs should be the same or=20
> greater.  The
> issue is not cost per IP address but cost per database entry.

I don't quite know how to characterize this or compare it,
but the cost to the small sites is an altogether different
metric than the cost to the DNS.

Fred
fred.l.templin@boeing.com


> > -----Original Message-----
> > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> > Sent: Wednesday, June 27, 2007 12:19 PM
> > To: Jeroen Massar; Leo Vegoda
> > Cc: ipv6@ietf.org; Brian E Carpenter; Pekka Savola
> > Subject: RE: ULA and WAN-routability
> >=20
> > > In effect one can indeed also use ULA-C kind of addresses as=20
> > > "Identifiers" as they are truly globally unique just like=20
> > PI, but that=20
> > > is the whole point why ULA-C is futile: they _are_ just=20
> like PI ;)=20
> > > Except that they will be carved out of a special prefix and=20
> > handled in=20
> > > a strange way. Also as they are not "Internet addresses"=20
> > but intended=20
> > > for disconnected sites and thus should never traverse the=20
> Internet=20
> > > except for in a VPN in the first place.
> >=20
> > Also except that they are attainable by very small sites at a
> > (presumably) nominal cost. (Plus, the "except for in a VPN"=20
> > is likely to be good enough for the kinds of connections=20
> > ULA-C sites will want to make.)
> >=20
> > Fred
> > fred.l.templin@boeing.com
> >=20
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 14:16:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3c3k-0002Xa-0q; Wed, 27 Jun 2007 14:16:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3c3j-0002XU-7O
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:16:07 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3c3T-0000BG-Ac
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:16:07 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id E70A7140C1B5;
	Wed, 27 Jun 2007 20:15:49 +0200 (CEST)
Message-ID: <4682A959.1070201@spaghetti.zurich.ibm.com>
Date: Wed, 27 Jun 2007 19:15:53 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Leo Vegoda <leo.vegoda@icann.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com>	<Pine.LNX.4.64.0706192211570.9840@netcore.fi>	<D03E4899F2FB3D4C8464E8C76B3B68B08AFFE7@E03MVC4-UKBR.domain1.systemhost.net>	<467853B0.5010806@internap.com>	<2242A2C2-F0C9-45A6-B781-61A9F296DFF3@icann.org>	<46785A65.7060505@internap.com>	<F2499AB1-DD93-4DD1-8944-1F55E04F02E6@icann.org>	<46796246.4050705@internap.com>
	<467A3C38.8090606@gmail.com>	<Pine.LNX.4.64.0706271510340.23111@netcore.fi>
	<46826215.10609@gmail.com>
	<46826F02.8000507@spaghetti.zurich.ibm.com>
	<468279BE.2030003@gmail.com>
	<980CCB8C-0F2F-466C-8866-ECCBE4E2A0CE@icann.org>
	<4682984E.2090500@spaghetti.zurich.ibm.com>
	<B3E118BE-5FC4-45B3-9547-40241459771E@icann.org>
In-Reply-To: <B3E118BE-5FC4-45B3-9547-40241459771E@icann.org>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>,
	Pekka Savola <pekkas@netcore.fi>
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0863729600=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0863729600==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig0C74C6DD639FF296BE3D4C2E"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0C74C6DD639FF296BE3D4C2E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Leo Vegoda wrote:
> On 27 Jun 2007, at 1:03pm, Jeroen Massar wrote:
>=20
> [...]
>=20
>>> Most childhood illnesses go away but the /48 assignments made by ARIN=

>>> and APNIC are permanent. What incentive is there - or will there be -=

>>> for those organisations to return their prefixes and take PA space fr=
om
>>> one or more of their upstream providers?
>>
>> ISPs can then force them. "Oh you want to announce a /48? Cool, but sh=
ow
>> us the money". It will then be cheaper to use their PA block on the
>> 'outside' as a Locator, while using their own PI block as a Identifier=
=2E
>> Filtering by the majority of the ISP's, accepting only /32's or for th=
at
>> matter only blocks from PA space, resolves all of that, with a little
>> bit of force but it will work.
>=20
> I don't remember many ISPs trying to force their customers with several=

> classful assignments to renumber into a single PA assignment. Why do yo=
u
> think ISPs will try and force renumber (or re-prefixing) costs on their=

> existing customers?

With the in-progress/proposed/... id/loc & shim6 mechanisms you don't
renumber, they keep using their own PI block. See it as automatically
tunneling over the Internet to the remote site.

Current situation:

2001:db8::42/48
+-----+
| YOU |---------[ Upstream ]---{ The Internet }-----{ Them }
+-----+

Versus the to-maybe-one-day-be-situation:

2001:db8::42/48
+-----+
| YOU |----*-----[ Upstream ]---{ The Internet }----*--- { Them }
+-----+    ^                                        ^
           |                                        |
            \----- id/loc or shim6 mechanism -------/


The "YOU" keeps their nice comfortable /48 and adds the new mechanism,
presto. It looks/feels like a automated tunnel mechanism. Of course the
exact details are not out on this yet, and I might describe it
completely wrongly above wrong what it finally will be.

The core thing is: No DFZ entries for "PI sites", but the "PI sites" do
use their own address space and have full control over it.

ISP's can then simply provide two services "BGP" or "Normal /48", prize
will make people move at some places and not at others and in some cases
filtering will force people to move.

Greets,
 Jeroen



--------------enig0C74C6DD639FF296BE3D4C2E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaCqVkuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I/opAJ9fckVTg/y7s8knqUE9N4x5lKPU
VQCeLSH8dFazCfNpJKnaEWGhokJts4w=
=TmaY
-----END PGP SIGNATURE-----

--------------enig0C74C6DD639FF296BE3D4C2E--


--===============0863729600==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0863729600==--




From ipv6-bounces@ietf.org Wed Jun 27 14:27:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3cET-0001Tf-JR; Wed, 27 Jun 2007 14:27:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3cER-0001TS-Sn
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:27:11 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3cDd-0004Bd-7d
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:27:11 -0400
Received: from [63.251.161.202] (account sleibrand@mail.internap.com HELO
	[63.251.161.202])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85153989; Wed, 27 Jun 2007 14:26:20 -0400
Message-ID: <4682ABC0.7070209@internap.com>
Date: Wed, 27 Jun 2007 11:26:08 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com> <46824361.4000300@gmail.com>
In-Reply-To: <46824361.4000300@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> Scott, you say
>
>> In a situation like this, I need to be able to resolve PTRs for hosts 
>> using my neighboring networks' ULA space
>
> Why do you need to do this?

For all the same reasons I need to resolve PTRs of hosts on the 
Internet.  I'm a network engineer, so my main reason for wanting PTRs is 
for traceroute, but I'm sure anyone running a server serving the 
neighborhoods would also like to be able to resolve information about 
the IPs of connecting clients, etc.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 14:28:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3cFT-0001vG-7H; Wed, 27 Jun 2007 14:28:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3cFQ-0001uB-Ir
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:28:12 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3cEY-0004Wg-0n
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:28:12 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Jun 2007 14:27:09 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFZJgkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,467,1175486400"; 
	d="scan'208"; a="63823976:sNHT39576006"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5RIR9M1021703; 
	Wed, 27 Jun 2007 14:27:09 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5RIQWZr011205; 
	Wed, 27 Jun 2007 18:27:09 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 14:26:48 -0400
Received: from [161.44.65.201] ([161.44.65.201]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 14:26:48 -0400
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com><m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com><467BD7FC.1030405@gmail.com><B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com><467BDEE5.30807@gmail.com><457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com><467F62DA.2010802@gmail.com><B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com><m2645chx46.wl%jinmei@wide.ad.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com><m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com><m2d4zihj67.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Wed, 27 Jun 2007 14:27:37 -0400
To: IETF Mailing List IPv6 <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 27 Jun 2007 18:26:48.0158 (UTC)
	FILETIME=[B9267FE0:01C7B8E8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=657; t=1182968829;
	x=1183832829; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20IETF=20Mailing=20List=20IPv6=20<ipv6@ietf.org>;
	bh=vWjYLbPFnr39CVSsOQ/t66i2LwQy/HGzWcrVEiYKrpg=;
	b=Py/JlR+wgFRToF2+ce18CP3TXd/zyIkWNiKt/lSeBR3l60YVG1dw1GI9fb1GcbdpeXwCFg6t
	LVT8tUXcXDj10qD9pTHQf8NtSZRF27XkkvnNozs+5Singqf8hrUcJtHI;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: "Fred Baker \(\(fred\)\)" <fred@cisco.com>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

One bug that may or may not be common is to make assumptions about  
the prefixes on a link based on addresses assigned to an interface.   
I can imagine (and I believe we've actually made a real sighting of  
this scenario) that an IPv6 implementor might extrapolate IPv4  
conventions and extract the /64 prefix from an assigned address  
(either SLAAC, DHCP or manual config), and add a route to the host  
table indicating that the prefix is on-link, regardless of whether  
the prefix is advertised as "on-link" in an RA.

This bug is an example of the issues addressed by section 2 of draft- 
wbeebee-nd-implementation-pitfalls.

- Ralph

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 14:39:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3cQa-0001hU-KE; Wed, 27 Jun 2007 14:39:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3cQZ-0001eg-Qw
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:39:43 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3cPk-0007qh-8v
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:39:43 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5RIcmW6079759
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 27 Jun 2007 20:38:48 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5RIckjL015040; Wed, 27 Jun 2007 20:38:47 +0200
Date: Wed, 27 Jun 2007 20:38:46 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CE@XCH-NW-7V2.nw.nos.boeing.com>
Message-ID: <Pine.LNX.4.64.0706272037460.29317@chandra.student.uit.no>
References: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CC@XCH-NW-7V2.nw.nos.boeing.com>
	<70DE64CEFD6E9A4EB7FAF3A0631410667070B0@mail>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8CE@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org
Subject: RE: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 27 Jun 2007, Templin, Fred L wrote:
>
> I thought the ULA-C registry was supposed to be something
> very simple like a robot.

yes but that's before we all started to consider what troubles we could 
get into by opening up ULA-C...



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 16:15:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3dv2-0006ZA-0y; Wed, 27 Jun 2007 16:15:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3dv0-0006Yu-6E
	for ipv6@ietf.org; Wed, 27 Jun 2007 16:15:14 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3duz-0003I4-U9
	for ipv6@ietf.org; Wed, 27 Jun 2007 16:15:14 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 8B9171142D
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 20:14:27 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Tue, 26 Jun 2007 16:17:43 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi>
	<Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 27 Jun 2007 20:14:27 +0000
Message-ID: <56005.1182975267@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Discussions on this list seem to indicate that globally routable PI might
> not be attainable for very small sites such as my laptop. That would be an
> example of where I can't get my own PI prefix, right?
> 
> fred.l.templin@boeing.com

on a site small enough to be its own network (like your laptop), i don't see a
use case for addresses other than ::1/128.  ("host-local" is a solved problem.)

if you broaden your example to include multiple virtual operating systems each
needing their own address so that they can communicate over a virtual bridge,
then "lan-local" (fe80::/16) is available.

if your laptop is joining an actual LAN (wired, wireless, etc) then it will 
have to have addresses assigned by that actual LAN's administrator, which might
include both fe80::/16 and something else.

it's in that final case where it's "something else" that the question of PI
comes in.  i don't think you're suggesting that your laptop have its own PI
for self-communication, and i don't think you're suggesting that your laptop's
PI ought to be connected by a routing protocol to the local network.

at best your need for laptop-level PI would be so that you could perform
routing over a VPN or tunnel whose endpoint was within the local (actual LAN)
administrator's control.

is this a use case worth pursuing for the purpose of defining internet
technology to support it?  because it seems to me that the mobile-IP folks
have scratched out a plan for this which involves using on your laptop
addresses assigned by the VPN hub, and speaking no routing protocol.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 16:50:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3eSt-0005Fs-73; Wed, 27 Jun 2007 16:50:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3eSq-00059o-Rs
	for ipv6@ietf.org; Wed, 27 Jun 2007 16:50:12 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3eSq-0006iY-DL
	for ipv6@ietf.org; Wed, 27 Jun 2007 16:50:12 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 4CFC51A5062; Wed, 27 Jun 2007 13:48:14 -0700 (PDT)
Date: Wed, 27 Jun 2007 13:48:14 -0700
From: bill fumerola <billf@mu.org>
To: ipv6@ietf.org
Message-ID: <20070627204814.GR31273@elvis.mu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Subject: AfriNIC, ULA-C, & "why not just get PI space"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

AfriNIC has implemented a PIv6 space policy[0]. part of it states:

"* The 'end-site' must show a plan to use and announce the IPv6 provider
independent address space within twelve (12) months. After that period,
if not announced, the assigned IPv6 PI address space should be reclaimed
and returned to the free pool by AfriNIC."

the policy document[0] itself says "Open for Discussion" but:

http://www.afrinic.net/policy.htm#policies
afpol-v6200701  	IPv6 Provider Independent (PI) Assignment for End-Sites  	13.06.2007  	Implemented

... lists it as implemented.

those in the AfriNIC region who want globally unique, registered space
but do not plan to "announce the IPv6 PI address space" have no method
of getting any such space. if anyone reads this differently than i do,
please educate me. i don't think they mean 'announce' to partner(s) or
within intra-AS boundaries, but admittedly i haven't read their mail
archives to see if this angle was ever brought up.

this leaves a few options like getting PA space from an LIR or becoming
a LIR(?!) as an option of getting space for the purpose of unique local
addressing, but the downside(s) to that seem too obvious to mention.

you could also announce the PI or LIR block and just null route it on
your edge, but i don't think that's the spirit of the policy and is a
slap in the face to those trying to keep the IPv6 global routing tables
tight & clean.

so in the AfriNIC region, "why not just get PI space for what you want
ULA-C for" isn't an option and the alternatives and workarounds aren't
that clean.

in that region there is a separate ULA-C policy[1] 'under discussion'
(and others[2] submitted by the same person), but i think there's been
general consensus on RIR lists and history on policies with global
implications that says the outcome of an IETF decision one way or another
on the fate of ULA-C (or another I-D that addresses similar needs perhaps
out of a different prefix than ULA-*) is more desirable than individual
RIRs acting prematurely or making policy based on proposed I-Ds.

nothing prevents other RIRs from changing their policies later to have
similar requirements. also, nothing indicates other RIRs are considering
changing their policies in this direction now or in the future.

in no way is this post an endorsement of the I-D as-is nor a move to
rush to move this document forward, just to point out a current event
with relevancy to the discussion. as a result of AfriNIC's policy and
the discussions here, i believe there can to be some common ground found:

(*) there is a desire for organizations to acquire globally unique
    network assignments for prefixes that SHALL NOT appear in the DFZ
    routing tables and addresses from these prefixes SHALL NOT appear
    as src/dst in traffic on the forwarding plane, outside of intra-AS
    or private inter-AS arrangements (VPNs, private interconnect, etc).

(*) acquiring PI space from RIRs for this purpose is not an option
    for everyone right now. that may change in either direction at any
    point in the future. AfriNIC may amend to accommodate this usage.
    other RIRs might consider similar restrictions on PIv6 space or want
    to allocate 'unannounced' space out of different IANA allocations
    causing inconsistencies amongst the RIRs. the IETF has the ability
    to reduce region-by-region difference by producing a document to
    unify the approach to assigning this class of network prefixes.

(*) since these prefixes can and will appear in other inter-networks
    (but not the Big One), a recognized delegation from IETF to IANA for
    registry maintenance (and hopefully further down) adds confidence.
    confidence in avoiding collisions (intentional or accidental),
    confidence in confirming entries of route6 objects into routing
    registries (private or public), and confidence in the legitimate
    entry of those prefixes into other tools to build the proper perimeter
    between network edges that make network operators life easier.

thanks for reading this far & sorry for the wordiness,
-- bill

0. http://www.afrinic.net/docs/policies/afpol-v6200701.htm
1. http://www.afrinic.net/docs/policies/afpol-v6ula200704.htm
2. http://www.ripe.net/ripe/policies/proposals/2007-05.html

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 17:35:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3fAA-0007fW-7O; Wed, 27 Jun 2007 17:34:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fA8-0007f4-7Y
	for ipv6@ietf.org; Wed, 27 Jun 2007 17:34:56 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3fA7-0003BE-TV
	for ipv6@ietf.org; Wed, 27 Jun 2007 17:34:56 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5RLYUBx011565
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 27 Jun 2007 16:34:31 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5RLYUIC013776; Wed, 27 Jun 2007 14:34:30 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5RLYRFS013683; Wed, 27 Jun 2007 14:34:29 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 14:34:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7B902.F05A7A85"
Date: Wed, 27 Jun 2007 14:34:27 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D1@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <56005.1182975267@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace49+7dvtabn8uRQ2GuqFBWqTUr6AAB6KtQ
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no><39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com>
	<56005.1182975267@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 27 Jun 2007 21:34:28.0366 (UTC)
	FILETIME=[F0C1E2E0:01C7B902]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B902.F05A7A85
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Paul,

I am talking about a "laptop" that connects an arbitrarily-
complex internal network of virtual hosts and routers, and
an arbitrarily-complex set of external devices attached on,
e.g., Ethernet, Bluetooth, etc. I am attaching the diagram
again (slightly updated) in case folks might have missed
it in my earlier message.

So, it can't just be link-local-for-all, because then there
is no opportunity for off-link communications when in fact
the laptop may connect many links. Also, if my laptop ever
needs to connect up with other sites (be it planned or ad-hoc;
via phisical links or virtual) it will need to have something
like ULA-C to avoid collisions. And, I don't want to have to
inject a globally-routable prefix into the DFZ for it.

Fred
fred.l.templin@boeing.com=20

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Wednesday, June 27, 2007 1:14 PM
> To: ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt=20
>=20
> > Discussions on this list seem to indicate that globally=20
> routable PI might
> > not be attainable for very small sites such as my laptop.=20
> That would be an
> > example of where I can't get my own PI prefix, right?
> >=20
> > fred.l.templin@boeing.com
>=20
> on a site small enough to be its own network (like your=20
> laptop), i don't see a
> use case for addresses other than ::1/128.  ("host-local" is=20
> a solved problem.)
>=20
> if you broaden your example to include multiple virtual=20
> operating systems each
> needing their own address so that they can communicate over a=20
> virtual bridge,
> then "lan-local" (fe80::/16) is available.
>=20
> if your laptop is joining an actual LAN (wired, wireless,=20
> etc) then it will=20
> have to have addresses assigned by that actual LAN's=20
> administrator, which might
> include both fe80::/16 and something else.
>=20
> it's in that final case where it's "something else" that the=20
> question of PI
> comes in.  i don't think you're suggesting that your laptop=20
> have its own PI
> for self-communication, and i don't think you're suggesting=20
> that your laptop's
> PI ought to be connected by a routing protocol to the local network.
>=20
> at best your need for laptop-level PI would be so that you=20
> could perform
> routing over a VPN or tunnel whose endpoint was within the=20
> local (actual LAN)
> administrator's control.
>=20
> is this a use case worth pursuing for the purpose of defining internet
> technology to support it?  because it seems to me that the=20
> mobile-IP folks
> have scratched out a plan for this which involves using on your laptop
> addresses assigned by the VPN hub, and speaking no routing protocol.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

------_=_NextPart_001_01C7B902.F05A7A85
Content-Type: text/plain;
	name="manet_router.txt"
Content-Transfer-Encoding: base64
Content-Description: manet_router.txt
Content-Disposition: attachment;
	filename="manet_router.txt"

ICAgICAgICAgICAgICAgICAgICAgICAgICAgRWdyZXNzIEludGVyZmFjZXMgKHRvIEludGVybmV0
KQ0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeICAgXiAgICAgICAgXg0KICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgfCAgICAgICAgfA0KICAgICAgICAg
ICstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tKy0tLS0tLS0tKy0tLS0tLS0tLS0rDQogICAg
ICAgICAgfCBJbnRlcm5hbCBob3N0cyAgICAgICAgIHwgICB8ICAgICAgICB8ICAgICAgICAgIHwg
ICAgTQ0KICAgICAgICAgIHwgIGFuIHJvdXRlcnMgICAgICAgICAgICB8ICAgfCAgLi4uLiAgfCAg
ICAgICAgICB8ICAgIEENCiAgICAgICAgICB8ICAgICAgICwtLiAgICB8ICAgICArLS0tKy0tLSst
LS0tLS0tLSstLS0rICAgICAgfCAgICBODQogICAgICAgICAgfCAgICAgIChIMSApLS0tKyAgICAg
fCAgICAgICAgICAgICAgICAgICAgfCAgICAgIHwgICAgRQ0KICAgICAgICAgIHwgICB8ICAgYC0n
ICAgIHwgICAgIHwgICAgICAgICAgICAgICAgICAgICstLS0tLS0rLS08IFQNCiAgICAgICAgICB8
IC4gfCAgKy0tLSsgICB8ICAgICB8ICAgICAgICAgICAgICAgICAgICB8ICAgICAgfA0KICAgICAg
ICAgIHwgLiArLS18UjEgfC0tLSstLS0tLSsgICAgICAgICAgICAgICAgICAgIHwgICAgICB8ICAg
IEkNCiAgICAgICAgICB8IC4gfCAgKy0tLSsgICB8ICAgICB8ICAgICAgIFJvdXRlciAgICAgICAr
LS0tLS0tKy0tPCBuDQogICAgICAgICAgfCAgIHwgICAsLS4gICAgfCAgICAgfCAgICAgICAgICAg
ICAgICAgICAgfCAgLiAgIHwgICAgdA0KICAgICAgICAgIHwgICAgICAoSDIgKS0tLSsgICAgIHwg
ICAgICAgRW50aXR5ICAgICAgIHwgIC4gICB8ICAgIGUNCiAgICAgICAgICB8ICAgICAgIGAtJyAg
ICB8ICAuICB8ICAgICAgICAgICAgICAgICAgICB8ICAuICAgfCAgICByDQogICAgICAgICAgfCAg
ICAgICAgICAgICAgICAgLiAgfCAgICAgICAgICAgICAgICAgICAgfCAgLiAgIHwgICAgZg0KICAg
ICAgICAgIHwgICAgICAgLC0uICAgICAgIC4gIHwgICAgICAgICAgICAgICAgICAgICstLS0tLS0r
LS08IGENCiAgICAgICAgICB8ICAgICAgKEhuICktLS0tLS0tLS0rICAgICAgICAgICAgICAgICAg
ICB8ICAgICAgfCAgICBjDQogICAgICAgICAgfCAgICAgICBgLScgICAgICAgICAgKy0tLSstLS0r
LS0tLS0tLS0rLS0tKyAgICAgIHwgICAgZQ0KICAgICAgICAgIHwgSW5ncmVzcyBJbnRlcmZhY2Vz
ICAgICB8ICAgfCAgLi4uLiAgfCAgICAgICAgICB8ICAgIHMNCiAgICAgICAgICB8ICh0byBpbnRl
cm5hbCBuZXR3b3JrcykgfCAgIHwgICAgICAgIHwgICAgICAgICAgfA0KICAgICAgICAgICstLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tKy0tLS0tLS0tKy0tLS0tLS0tLS0rDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwgICB8ICAgICAgICB8DQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIHYgICB2ICAgICAgICB2DQogICAgICAgICAgICAgICAgICAgSW5n
cmVzcyBJbnRlcmZhY2VzICh0byBleHRlcm5hbCBuZXR3b3JrcykNCg0KICAgICAgICAgICAgICAg
ICAgICAgICAgICBGaWd1cmUgMTogTUFORVQgUm91dGVyDQo=

------_=_NextPart_001_01C7B902.F05A7A85
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

------_=_NextPart_001_01C7B902.F05A7A85--




From ipv6-bounces@ietf.org Wed Jun 27 18:05:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3fdH-0003W0-Os; Wed, 27 Jun 2007 18:05:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fdG-0003Q6-6M
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:05:02 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3fdF-0006hu-Ky
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:05:02 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 3E6E01142D
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 22:04:15 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
In-Reply-To: Your message of "Tue, 26 Jun 2007 17:38:17 MST."
	<4681B179.2020301@internap.com> 
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com> <77167.1182834776@sa.vix.com>
	<4681B179.2020301@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 27 Jun 2007 22:04:02 +0000
Message-ID: <70626.1182981842@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

(headers trimmed)

> From: Scott Leibrand <sleibrand@internap.com>
> 
> Paul Vixie wrote:
> > please re-think this in terms of "connectivity realms", of which the DFZ
> > is one, and the american automotive exchange is another, ..., and every
> > ad-hoc wireless mesh is another.  ...
> 
> ... I'm not sure that we can simply see the public Internet as just another
> connectivity realm.  I believe that the history of the Internet, and the
> architecture we have built up to support it (particularly the addressing
> architecture, as defined by the IETF and delegated from IANA to the RIRs to
> ISPs and to end sites), require that we consider the public Internet to be a
> unique connectivity realm.

assume for a moment that FC00::/16 becomes reserved for "non-public internet"
due to actions by IETF, IESG, and IANA; assume furthermore than some RIRs ask
IANA for /32 slice of this and adopt policies allowing their members to request
/48 allocations.  assume that fred templin gets one for his laptop and manages
to speak a routing protocol with every wireless cloud operator he sits in, so
that for each of those AS's, his /48 is "reachable" by other folks in the same
AS.

what would stop these wireless cloud operators from privately peering with
each other and turning off the filter that we all hope normally prevents FC00
routes out of BGP?  we know they will want to do this, just as they want to
share RADIUS and towers -- it makes the wireless world appear to be more
unified and means more revenue for everybody.  now assume that someone like
ISC or CENIC is present at a peering exchange and one of these wireless ISP's
solicits a BGP relationship with us.  would they want to send us their FC00
/48's?  you betcha!  would we want to take them?  you betcha!

the only time these /48's aren't likely to be accepted or offered is by a
transit provider.  in private peering relationships, they'll be seen as a
value-add by most peers.

which connectivity realm is the "public" one in that scenario?  is it the one
that includes more reachable places?  or the one we _call_ the "public" one?

> ..., any connectivity realm that approaches the public Internet in terms of
> the number and diversity of interconnected participants will require an
> addressing and routing framework to meet the various needs of its different
> participants in a mutually acceptable manner.

the wonderful thing about the internet is that plans don't matter.  what exists
is whatever a lot of people decide to do.  for a lot of people, accepting /48's
from their peers will make good "cost:benefit sense".  for others, not so much.
so, address space in FC00::/16 will not be as reachable by some as by others,
and thus won't be as valuable as other address space that's more universally
reachable.  however, to call it "private" is an exceptional misnomer.  it'll be
advertised among consenting networks, and it will work for a lot of users and
a lot of applications.  when it doesn't work, all heck will break loose, just
like today when "public" address space goes unreachable for some people.  

> As long as we're talking about IPv6, that addressing framework will need to
> coexist with the addressing framework of the public Internet.  Given the
> current Internet addressing architecture, that means we need some way to
> partition off part of the IPv6 address space, designate it as "not to be
> routed in the DFZ", and assign pieces of that space to anyone wishing to
> internetwork in a connectivity realm other than the DFZ.

we can designate it any way we want.  let's designate it however we have to
designate it in order to start using it.  then we'll find out the real facts,
because real users will do real things.  if the DFZ must be ostensibly defended
from two million /48 end site announcements, then let's ostensibly defend it.
however, just privately, just among the smallish subset of folks who read this
mailing list, we all know that the DFZ fiction will simply get more fictional.

to the meat, then:

> > 7. all global-scoped addresses need ongoing reliable DNS and WHOIS support
> > 8. address DNS/WHOIS support is traditionally a regional, bottom-up function
> 
> Agreed, which is why I advocate that ULA-C space (or whatever we end up 
> calling the space that fills the needs described above) be assigned to 
> Regional Internet Registries (RIRs), who can then assign it to end users 
> and provide appropriate DNS and WHOIS support.

ok by me.

> I would also support allowing the RIRs to allocate such non-DFZ-routed space
> to Local Internet Registries (LIRs), so that they can serve their members /
> customers by reassigning such space and providing DNS and/or WHOIS services
> in a method (and possibly a connectivity realm) not served by the RIRs
> directly.

also ok by me.

> ... I would draw the following conclusions:
> 
>     * There is a need to allocate and assign IPv6 address space, in a
>       non-restrictive manner, to entities wishing to internetwork
>       outside of the public Internet's DFZ.
>     * There is a need to provide reliable DNS and WHOIS support for
>       these addresses.  The methods of providing such DNS support should
>       include, but should not be limited to, allowing registrants to
>       delegate DNS authority to servers reachable from the public
>       Internet.  Other methods for providing reliable DNS support for
>       these addresses should be explored, but no method should be
>       allowed which imposes an undue burden on Internet DNS infrastructure.

i'd say "from both its own connectivity realm and from the DFZ" where you've
said "the public internet" above, but otherwise, i can live with that summary.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 18:17:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3fp2-0005Mo-Gl; Wed, 27 Jun 2007 18:17:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fp1-0005Mj-OB
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:17:11 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3fp1-0007Tm-Fz
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:17:11 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id A7A421142E
	for <ipv6@ietf.org>; Wed, 27 Jun 2007 22:17:10 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Wed, 27 Jun 2007 14:34:27 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D1@XCH-NW-7V2.nw.nos.boeing.com>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no><39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com>
	<56005.1182975267@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D1@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 27 Jun 2007 22:17:10 +0000
Message-ID: <73075.1182982630@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
> 
> I am talking about a "laptop" that connects an arbitrarily-
> complex internal network of virtual hosts and routers, and
> an arbitrarily-complex set of external devices attached on,
> e.g., Ethernet, Bluetooth, etc. ...

so, there's a routing protocol here?

> So, it can't just be link-local-for-all, because then there
> is no opportunity for off-link communications when in fact
> the laptop may connect many links.

if the laptop is going to connect to many links, then it will
get an address assigned for each of those links, by DHCP or
stateless autoconf or even manual config.  giving the laptop
its own UA will only make sense if there's a routing protocol
by which that UA-block is advertised into the networks the
laptop connects with.  so can you explain the routing?

>                                     Also, if my laptop ever
> needs to connect up with other sites (be it planned or ad-hoc;
> via phisical links or virtual) it will need to have something
> like ULA-C to avoid collisions. And, I don't want to have to
> inject a globally-routable prefix into the DFZ for it.

forget the DFZ for a minute.  you will have to inject your UA
into the network(s) you attach to.  how's that going to work?
(and what's the horizon of that injection?)


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 18:34:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3g69-0000BK-9b; Wed, 27 Jun 2007 18:34:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3g66-0008II-Ms
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:34:50 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3g66-0000Gi-Cn
	for ipv6@ietf.org; Wed, 27 Jun 2007 18:34:50 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5RMYPKJ011334
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 27 Jun 2007 15:34:25 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5RMYPJ9008714; Wed, 27 Jun 2007 15:34:25 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5RMYNne008654; Wed, 27 Jun 2007 15:34:24 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Jun 2007 15:34:24 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Jun 2007 15:34:23 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <73075.1182982630@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace5CQ5Fx/N05g4fSh2wtsywt1zS7AAAEL4w
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org><200706191523.l5JFNR8J032665@cichlid.raleigh.ibm.com><Pine.LNX.4.64.0706192211570.9840@netcore.fi><Pine.LNX.4.64.0706262342080.29317@chandra.student.uit.no><39C363776A4E8C4A94691D2BD9D1C9A1029ED8C5@XCH-NW-7V2.nw.nos.boeing.com><56005.1182975267@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8D1@XCH-NW-7V2.nw.nos.boeing.com>
	<73075.1182982630@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 27 Jun 2007 22:34:24.0130 (UTC)
	FILETIME=[4FFFEE20:01C7B90B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > I am talking about a "laptop" that connects an arbitrarily-
> > complex internal network of virtual hosts and routers, and
> > an arbitrarily-complex set of external devices attached on,
> > e.g., Ethernet, Bluetooth, etc. ...

First, s/laptop/platform - where, a "platform" could be
something relatively small (like my laptop) or something
quite a bit larger (like a cruise ship). Any points
in-between (planes, trains, automobiles, etc.) also meet
the description. But, all of them are platforms and all
of them are also "sites".
=20
> so, there's a routing protocol here?

Where do you mean by "here"?
=20
> > So, it can't just be link-local-for-all, because then there
> > is no opportunity for off-link communications when in fact
> > the laptop may connect many links.
>=20
> if the laptop is going to connect to many links, then it will
> get an address assigned for each of those links, by DHCP or
> stateless autoconf or even manual config.  giving the laptop
> its own UA will only make sense if there's a routing protocol
> by which that UA-block is advertised into the networks the
> laptop connects with.  so can you explain the routing?

Advertising the ULA block into a (visited) network that
only provides transit for the platform's communications
is not required. But, maybe that's not what you meant
(see below):=20
=20
> >                                     Also, if my laptop ever
> > needs to connect up with other sites (be it planned or ad-hoc;
> > via phisical links or virtual) it will need to have something
> > like ULA-C to avoid collisions. And, I don't want to have to
> > inject a globally-routable prefix into the DFZ for it.
>=20
> forget the DFZ for a minute.  you will have to inject your UA
> into the network(s) you attach to.  how's that going to work?
> (and what's the horizon of that injection?)

You establish a link between two sites - perhaps aided by
information in the DNS. Then, you either have the IGPs
operating in the two formerly separate sites form an
adjacency over the link, or you set up static routes.

Fred
fred.l.templin@boeing.com

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 19:43:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3hAF-00005R-B7; Wed, 27 Jun 2007 19:43:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3c3n-0002Z9-2R
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:16:11 -0400
Received: from [216.118.97.199] (helo=nereids.site5.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3c3V-0000BP-Pi
	for ipv6@ietf.org; Wed, 27 Jun 2007 14:16:11 -0400
Received: from exactor by nereids.site5.com with local (Exim 4.63)
	(envelope-from <shamilton@exactor.com>)
	id 1I3c3P-0006Bs-Jl; Wed, 27 Jun 2007 14:15:47 -0400
Received: from 207.47.110.138 ([207.47.110.138])
	(SquirrelMail authenticated user shamilton@exactor.com)
	by www.exactor.com with HTTP; Wed, 27 Jun 2007 14:15:47 -0400 (EDT)
Message-ID: <10310.207.47.110.138.1182968147.squirrel@www.exactor.com>
In-Reply-To: <1182945273.21026.97.camel@localhost.localdomain>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>
	<4681B179.2020301@internap.com>
	<024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
	<1182945273.21026.97.camel@localhost.localdomain>
Date: Wed, 27 Jun 2007 14:15:47 -0400 (EDT)
From: shamilton@exactor.com
To: "Per Heldal" <heldal@eml.cc>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - nereids.site5.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [32186 500] / [47 12]
X-AntiAbuse: Sender Address Domain - exactor.com
X-Source: /usr/local/cpanel/3rdparty/bin/php
X-Source-Args: /usr/local/cpanel/3rdparty/bin/php
	/usr/local/cpanel/base/3rdparty/squirrelmail/src/compose.php 
X-Source-Dir: :/base/3rdparty/squirrelmail/src
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-Mailman-Approved-At: Wed, 27 Jun 2007 19:43:09 -0400
Cc: Stephen Sprunk <stephen@sprunk.org>, ARIN PPML <ppml@arin.net>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

  I totally agree with Stephen and others than regardless of original
intent 'private' PI routes will end up public, whether by intention down
the road, by accident, or by hi-jacking.  It strikes me that the way to
address this is after the allocation process by means of routing
authentication only - RADB and it's ilk now, certificates later maybe. 
Call me naive but I thought a key factor in v6 deployment is that there
is enough to go round so NAT / PA will not be forced onto organizations
that don't want it - surely it's enough of a burden to get PI space,
manage it in RADB/DNS, setup BGP, pay an ISP to receive your
advertisements (there's a whole other choke point here where ISPs can
institute their own policies on what is reasonable).

  I'm young and inexperienced compared to many of you I know, but I can't
see the IPv6 table being < 300K routes in a few years, but neither can I
see it being double that - whilst I see some pent up demand for
multi-homing using PI space, I also see many people who will continue
using NAT in IPv6 because that's their security guys dogma (it isn't
mine & I'm not interested in that whole discussion again).  It will
continue to require a degree of clue to participate in the global table,
and if people need to announce their aggregates to make things work
that's a lesson they will learn (or that their ISPs will share/force
upon them)

Regards

Simon Hamilton-Wilkes




> On Tue, 2007-06-26 at 23:48 -0500, Stephen Sprunk wrote:
>> If we want to issue address space to folks for "private" use, it needs
>> to be
>> out of the same block(s) that the RIRs use to allocate space for
>> "public"
>> use, because sooner or later those "private" networks are going to end
>> up
>> being publicly routed.
>
> But if we do this shouldn't we also take steps to prevent abuse
> (hijacking etc) of those "private" blocks. History has shown that
> unannounced PI-blocks that nobody is missing can be abused for a long
> time before anybody cries foul. We may have made a hash of v4, but
> shouldn't have to make the same mistake from the start with v6. Maybe
> RIRs should announce "private" or otherwise "quarantined" blocks from a
> special AS so that they can easily be identified and filtered ...
> although they'd end up wasting space in the DFZ (whatever that is;).
>
> ... which is closely related to the following:
>>
>> If we are concerned that giving "real" PI space to every org that asks
>> for
>> it will result in the immediate death of the DFZ, then there needs to be
>> some sort of tag attached to blocks that says whether or not the
>> registrant
>> has met whatever the current rules are for deserving a routing slot.  If
>> routing certificates ever take off, they could contain a flag that gives
>> the
>> current public routability status, or the RIR could just not issue a
>> certificate at all if someone hasn't met the bar.  That's an entirely
>> separate matter from whether or not they get addresses.
>
> Until there's a reliable mechanism to verify the origin of a prefix all
> we can do is try to cope through policies. Is the lack of
> route-certificates an excuse to not try to do something about the
> problem in the meantime?
>
>
>>
>> One could also argue that the RIRs do not belong in the routability
>> decision
>> path at all, since their job is to ensure uniqueness, and some other
>> quasi-public entity responsible for the health of the DFZ would produce
>> "routability" certificates.  That also gives rise to the possibility of
>> different models than we have today, like a market where people could
>> buy
>> and sell routing slots.
>
> Isn't that like calling for a "global internet constitution"?
>
> What about a mechanism to establish some form of "common ground" on
> which routing-policy-decisions can be made. To "navigate" the world of
> routing an allocation-policies today is like navigating an aircraft
> without the ability to adjust the altimeter for varying air-pressure.
> There are too many inconsistent and independent sources of information
> with widely varying quality and formats. Things would be easier if
> inter-domain-routers were required to form a relation to
> address-registries for all network-domains in which they wish to operate
> (normally ARIN + RIRs + possibly private) in addition to whatever
> routing policies each operator choose to implement (in reality they
> already do but the quality that information tend to vary a lot with
> operator clue). Registries would then have to announce the allocation
> policies (blocks and prefix-lengths) through standardised formats and
> mechanisms/protocols available globally. Address-space that is not
> covered by a policy would by definition be unused (hence the need for
> separate bogon-filtering and the related debogonizing-issues would be
> mostly eliminated).
>
> Combine this with:
>
> - A strong recommendation from address registries to announce aggregates
> for optimum visibility/routability (note: _recommendation_ not
> _requirement_). In reality this is just a formalisation of current
> practise.
>
> - Standards which must require IDR implementations to never drop
> aggregates even if the available set of more-specifics cover the entire
> block specified by the allocation policy. A 3rd party might choose to
> ignore the smaller blocks and would loose "visibility" without the
> aggregate. (note: path selection algorithms based on
> longest-prefix-match would not be affected).
>
> (- Maybe even a BGP node should be able to tell its peer(s) that it
> doesn't want to receive routes more specific than allocation policies.
> Although it might be hard to ensure that different ASes conform to the
> same allocation policies.)
>
>
> With such a thing in place one would at least have a fair chance of
> knowing how local routing-policy decisions might affect routability. Now
> you can safely ignore TE-churn from distant networks while choosing to
> accept more specifics from peers and others in your "neighbourhood" and
> still feel reasonably confident that you're not loosing anything
> important.
>
> In a better world that has route-certificates and unlimited
> IDR-scalability this makes no sense, but will we get there in time to
> avoid trouble.
>
>
> //per
>
> _______________________________________________
> This message sent to you through the ARIN Public Policy Mailing List
> (PPML@arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml
>


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Wed Jun 27 19:43:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3hAE-0008V8-NL; Wed, 27 Jun 2007 19:43:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3W8T-0002Ca-Qv
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:56:37 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3W7J-0008FI-AL
	for ipv6@ietf.org; Wed, 27 Jun 2007 07:56:37 -0400
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id B42A62112;
	Wed, 27 Jun 2007 07:55:24 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute1.internal (MEProxy); Wed, 27 Jun 2007 07:55:24 -0400
X-Sasl-enc: NpgXhd2PChvaAkhwA6vKITGILircmgjb2BnGntSYrDSM 1182945320
Received: from [127.0.0.1] (unknown [85.187.158.179])
	by mail.messagingengine.com (Postfix) with ESMTP id 1B6B3394C;
	Wed, 27 Jun 2007 07:55:08 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>
	<4681B179.2020301@internap.com>
	<024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
Content-Type: text/plain
Date: Wed, 27 Jun 2007 13:54:33 +0200
Message-Id: <1182945273.21026.97.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
X-Mailman-Approved-At: Wed, 27 Jun 2007 19:43:09 -0400
Cc: ARIN PPML <ppml@arin.net>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 2007-06-26 at 23:48 -0500, Stephen Sprunk wrote:
> If we want to issue address space to folks for "private" use, it needs to be 
> out of the same block(s) that the RIRs use to allocate space for "public" 
> use, because sooner or later those "private" networks are going to end up 
> being publicly routed.

But if we do this shouldn't we also take steps to prevent abuse
(hijacking etc) of those "private" blocks. History has shown that
unannounced PI-blocks that nobody is missing can be abused for a long
time before anybody cries foul. We may have made a hash of v4, but
shouldn't have to make the same mistake from the start with v6. Maybe
RIRs should announce "private" or otherwise "quarantined" blocks from a
special AS so that they can easily be identified and filtered ...
although they'd end up wasting space in the DFZ (whatever that is;).

... which is closely related to the following:
> 
> If we are concerned that giving "real" PI space to every org that asks for 
> it will result in the immediate death of the DFZ, then there needs to be 
> some sort of tag attached to blocks that says whether or not the registrant 
> has met whatever the current rules are for deserving a routing slot.  If 
> routing certificates ever take off, they could contain a flag that gives the 
> current public routability status, or the RIR could just not issue a 
> certificate at all if someone hasn't met the bar.  That's an entirely 
> separate matter from whether or not they get addresses.

Until there's a reliable mechanism to verify the origin of a prefix all
we can do is try to cope through policies. Is the lack of
route-certificates an excuse to not try to do something about the
problem in the meantime?


> 
> One could also argue that the RIRs do not belong in the routability decision 
> path at all, since their job is to ensure uniqueness, and some other 
> quasi-public entity responsible for the health of the DFZ would produce 
> "routability" certificates.  That also gives rise to the possibility of 
> different models than we have today, like a market where people could buy 
> and sell routing slots.

Isn't that like calling for a "global internet constitution"?

What about a mechanism to establish some form of "common ground" on
which routing-policy-decisions can be made. To "navigate" the world of
routing an allocation-policies today is like navigating an aircraft
without the ability to adjust the altimeter for varying air-pressure.
There are too many inconsistent and independent sources of information
with widely varying quality and formats. Things would be easier if
inter-domain-routers were required to form a relation to
address-registries for all network-domains in which they wish to operate
(normally ARIN + RIRs + possibly private) in addition to whatever
routing policies each operator choose to implement (in reality they
already do but the quality that information tend to vary a lot with
operator clue). Registries would then have to announce the allocation
policies (blocks and prefix-lengths) through standardised formats and
mechanisms/protocols available globally. Address-space that is not
covered by a policy would by definition be unused (hence the need for
separate bogon-filtering and the related debogonizing-issues would be
mostly eliminated). 

Combine this with:

- A strong recommendation from address registries to announce aggregates
for optimum visibility/routability (note: _recommendation_ not
_requirement_). In reality this is just a formalisation of current
practise.

- Standards which must require IDR implementations to never drop
aggregates even if the available set of more-specifics cover the entire
block specified by the allocation policy. A 3rd party might choose to
ignore the smaller blocks and would loose "visibility" without the
aggregate. (note: path selection algorithms based on
longest-prefix-match would not be affected).

(- Maybe even a BGP node should be able to tell its peer(s) that it
doesn't want to receive routes more specific than allocation policies.
Although it might be hard to ensure that different ASes conform to the
same allocation policies.)


With such a thing in place one would at least have a fair chance of
knowing how local routing-policy decisions might affect routability. Now
you can safely ignore TE-churn from distant networks while choosing to
accept more specifics from peers and others in your "neighbourhood" and
still feel reasonably confident that you're not loosing anything
important.

In a better world that has route-certificates and unlimited
IDR-scalability this makes no sense, but will we get there in time to
avoid trouble.


//per


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 00:06:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3lGL-00016V-1S; Thu, 28 Jun 2007 00:05:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3lGJ-00013w-2G
	for ipv6@ietf.org; Thu, 28 Jun 2007 00:05:43 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3lGI-0002L6-Pj
	for ipv6@ietf.org; Thu, 28 Jun 2007 00:05:42 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 825411142F
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 04:05:09 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Mon, 18 Jun 2007 15:50:02 -0400."
	<E1I0NEg-000884-8o@stiedprstage1.ietf.org> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 04:05:09 +0000
Message-ID: <13846.1183003509@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

these are my comments on the following I-D:

> 	Title      : Centrally Assigned Unique Local IPv6 Unicast Addresses
> 	Author(s)  : R. Hinden, B. Haberman
> 	Filename   : draft-ietf-ipv6-ula-central-02.txt
> 	Pages      : 11
> 	Date       : 2007-6-18
> 
> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt>

first, in 3.1, this table:

      | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
      +--------+-+------------+-----------+----------------------------+
      | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
      +--------+-+------------+-----------+----------------------------+

should be replaced with this one:

      | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
      +--------+-+----------+---------+---------+----------+
      | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
      +--------+-+----------+---------+---------+----------+

where "Prefix" and "L" are defined as shown in central-02, and the other
fields are defined as follows:

     Reserved            Set to 0 by all implementors of this specification,
                         but may be set to nonzero by implementors of a later
                         specification.

     RIR Num             Identifiers assigned by IANA for each /16 as
                         allocated to an Regional Internet Address Registry
                         (RIR).  For direct allocations by IANA, the value
                         of zero (0x0000) is reserved.

     LIR Num             Identifiers assigned by RIR for each /32 as
                         allocated to a Local Internet Address Registry (LIR).
                         For direct allocations by an RIR, the value of zero
                         (0x0000) is reserved.

     User Num            Identifier assigned by an end user or network
                         operator who implements this specification.

second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 3.2.3.

third, replace section 7.0 with the following:

---

7.0 IANA Considerations

    IANA is hereby instructed to reserve address block FC::/7 for private
    unique addresses, and to allocate /32 blocks to Regional Internet 
    Address Registries (RIRs) who request same after adopting policies
    consistent with this specification.  Allocation shall be similar in
    all ways to normal IANA address allocation to RIRs, including but not
    limited to IN-ADDR.ARPA delegations and WHOIS records.

---

Paul Vixie
not speaking for ISC
not speaking for ARIN

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 01:15:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3mLe-00055I-6i; Thu, 28 Jun 2007 01:15:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3mLc-000546-HG
	for ipv6@ietf.org; Thu, 28 Jun 2007 01:15:16 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3mLS-0000Ly-Bm
	for ipv6@ietf.org; Thu, 28 Jun 2007 01:15:16 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4044E7301E;
	Thu, 28 Jun 2007 14:15:03 +0900 (JST)
Date: Thu, 28 Jun 2007 14:14:57 +0900
Message-ID: <m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	<m2d4zihj67.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>,
	"Fred Baker \(\(fred\)\)" <fred@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Wed, 27 Jun 2007 14:27:37 -0400,
Ralph Droms <rdroms@cisco.com> wrote:

> One bug that may or may not be common is to make assumptions about  
> the prefixes on a link based on addresses assigned to an interface.   
> I can imagine (and I believe we've actually made a real sighting of  
> this scenario) that an IPv6 implementor might extrapolate IPv4  
> conventions and extract the /64 prefix from an assigned address  
> (either SLAAC, DHCP or manual config), and add a route to the host  
> table indicating that the prefix is on-link, regardless of whether  
> the prefix is advertised as "on-link" in an RA.

FWIW, *BSDs do not have this "bug".

- the L and A bits of the RA prefix information option are clearly
  separated.  That is, creating an IPv6 address from a prefix
  information option (with A bit on) doesn't make the kernel consider
  the prefix on-link unless the L bit is also on.
- the WIDE-DHCPv6 client configures an IPv6 address with the prefix
  length of 128.  So, an IPv6 address created via DHCPv6 doesn't
  impose the incorrect assumption of on-link'ness either.

If the system administrator manually configures an IPv6 address with a
prefix length smaller than 128, the kernel will assume that the
corresponding prefix is on-link.  But I believe this should be
reasonable.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 01:29:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3mZU-00018l-1A; Thu, 28 Jun 2007 01:29:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3mZS-00018W-Lc
	for ipv6@ietf.org; Thu, 28 Jun 2007 01:29:34 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3mYw-0002xj-9f
	for ipv6@ietf.org; Thu, 28 Jun 2007 01:29:34 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85187140 for ipv6@ietf.org;
	Thu, 28 Jun 2007 01:29:01 -0400
Message-ID: <46834717.3090102@internap.com>
Date: Wed, 27 Jun 2007 22:28:55 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipv6@ietf.org
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
In-Reply-To: <13846.1183003509@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I would support Paul's proposed changes below, and the resulting draft.

-Scott

Paul Vixie wrote:
> these are my comments on the following I-D:
>
>   
>> 	Title      : Centrally Assigned Unique Local IPv6 Unicast Addresses
>> 	Author(s)  : R. Hinden, B. Haberman
>> 	Filename   : draft-ietf-ipv6-ula-central-02.txt
>> 	Pages      : 11
>> 	Date       : 2007-6-18
>>
>> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt>
>>     
>
> first, in 3.1, this table:
>
>       | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
>       +--------+-+------------+-----------+----------------------------+
>       | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
>       +--------+-+------------+-----------+----------------------------+
>
> should be replaced with this one:
>
>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>       +--------+-+----------+---------+---------+----------+
>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>       +--------+-+----------+---------+---------+----------+
>
> where "Prefix" and "L" are defined as shown in central-02, and the other
> fields are defined as follows:
>
>      Reserved            Set to 0 by all implementors of this specification,
>                          but may be set to nonzero by implementors of a later
>                          specification.
>
>      RIR Num             Identifiers assigned by IANA for each /16 as
>                          allocated to an Regional Internet Address Registry
>                          (RIR).  For direct allocations by IANA, the value
>                          of zero (0x0000) is reserved.
>
>      LIR Num             Identifiers assigned by RIR for each /32 as
>                          allocated to a Local Internet Address Registry (LIR).
>                          For direct allocations by an RIR, the value of zero
>                          (0x0000) is reserved.
>
>      User Num            Identifier assigned by an end user or network
>                          operator who implements this specification.
>
> second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 3.2.3.
>
> third, replace section 7.0 with the following:
>
> ---
>
> 7.0 IANA Considerations
>
>     IANA is hereby instructed to reserve address block FC::/7 for private
>     unique addresses, and to allocate /32 blocks to Regional Internet 
>     Address Registries (RIRs) who request same after adopting policies
>     consistent with this specification.  Allocation shall be similar in
>     all ways to normal IANA address allocation to RIRs, including but not
>     limited to IN-ADDR.ARPA delegations and WHOIS records.
>
> ---
>
> Paul Vixie
> not speaking for ISC
> not speaking for ARIN
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>   

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 02:23:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3nOv-0003hJ-NP; Thu, 28 Jun 2007 02:22:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3nOt-0003dR-7O
	for ipv6@ietf.org; Thu, 28 Jun 2007 02:22:43 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3nMU-0007AG-FB
	for ipv6@ietf.org; Thu, 28 Jun 2007 02:20:29 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5S6KB3O080513
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 08:20:12 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5S6KB4T007824; Thu, 28 Jun 2007 08:20:11 +0200
Date: Thu, 28 Jun 2007 08:20:11 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Paul Vixie <paul@vix.com>
In-Reply-To: <13846.1183003509@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0706280817280.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 28 Jun 2007, Paul Vixie wrote:
<snip>
> should be replaced with this one:
>
>      | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>      +--------+-+----------+---------+---------+----------+
>      | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>      +--------+-+----------+---------+---------+----------+
>
> where "Prefix" and "L" are defined as shown in central-02, and the other
> fields are defined as follows:

striks me as almost the same as the good old sTLA...

<snip>
> third, replace section 7.0 with the following:
>
> ---
>
> 7.0 IANA Considerations
>
>    IANA is hereby instructed to reserve address block FC::/7 for private
>    unique addresses, and to allocate /32 blocks to Regional Internet
>    Address Registries (RIRs) who request same after adopting policies
>    consistent with this specification.  Allocation shall be similar in
>    all ways to normal IANA address allocation to RIRs, including but not
>    limited to IN-ADDR.ARPA delegations and WHOIS records.
>
> ---

so we are talking about full reverse control delegated to the person that 
get this ULA-C block?


except this piece about DNS mention above it look more promissing than the 
original draft.


-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 03:54:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3oow-0005nm-FE; Thu, 28 Jun 2007 03:53:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3oou-0005nW-6b
	for ipv6@ietf.org; Thu, 28 Jun 2007 03:53:40 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3oon-0006H6-6A
	for ipv6@ietf.org; Thu, 28 Jun 2007 03:53:40 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1542866ugf
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 00:53:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=WZrjAqfkolRokO9aTk8iOpu9VWqew6ZnlFdVUQxmbj6YnwVW+wE3egixuKiVYCutWUPf4xeuUP12FuY/LPXKBHslCzmFP/t5ImQxKzxh7Y45+2iNJTtOuMjhKOWkKMZevu1nup5LQhuIJdzrBvVA16XQEWXxOr2tuwqOFRIWMz0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=LzU5abGH7wKPNg0YHxxcOoTYSsi/pRPtndWugorWZS/EbgowcNhRPKT+mwpErnCsIT+5F9OU04sqceBpJctVFtZjxKbsURLKKlYmk8I1li5bMcUCz0JdwnRhqzXYUVyJwP1kQL/s+gv+nsAmh6TUtbUWZym1pKjeKAlCb6USBDQ=
Received: by 10.67.16.2 with SMTP id t2mr254970ugi.1183017212398;
	Thu, 28 Jun 2007 00:53:32 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id n55sm1424508uga.2007.06.28.00.53.30
	(version=SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 00:53:31 -0700 (PDT)
Message-ID: <468368FD.7050005@gmail.com>
Date: Thu, 28 Jun 2007 09:53:33 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8CC@XCH-NW-7V2.nw.nos.boeing.com>	<70DE64CEFD6E9A4EB7FAF3A0631410667070B0@mail>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8CE@XCH-NW-7V2.nw.nos.boeing.com>
	<Pine.LNX.4.64.0706272037460.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706272037460.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>, ipv6@ietf.org
Subject: Re: ULA and WAN-routability
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 20:38, Roger Jorgensen wrote:
> On Wed, 27 Jun 2007, Templin, Fred L wrote:
>>
>> I thought the ULA-C registry was supposed to be something
>> very simple like a robot.
> 
> yes but that's before we all started to consider what troubles we could 
> get into by opening up ULA-C...

I think that's beside the point. We need some rules in the draft that
make sure that this space is delegated to IANA as technical address
space, with an obligation on IANA to ensure it remains very low cost
to acquire and use locally. I think the facts of physics and economics
will ensure that it's expensive to route and impractical to put in the
global DNS.

    Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:00:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3ovd-0006Gq-GM; Thu, 28 Jun 2007 04:00:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3ovb-00069x-Gc
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:00:35 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3ovB-00008D-Hi
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:00:35 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1544415ugf
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 01:00:08 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=O58RfFji7wBN/vJ/mEUSmJ2uC51+WKHGfFUIMNjKQWlFVx+wmrenXaMSDzx9T104a4psv290MoXmUe0zbGLnTjHvzOT1MS0giy5eFNZwAtLOAIlbN/aIMZLH+l/M+5oL4a0MetrJBWjPfRfKve4SLTNIm34DYYFhmqko8pkpzLA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ZWMnlTV+u7r5JBLhzTf3q1J2X2STm8i7nAw6Xqj7XHORx4LDLvxWDXWrCzhfhYgZZco062WLC5kyohbpopGjoQkT+X7j3bqMinbL6JsRrX5bzULlj0YXuQgmsV7jhq/UOEeS2GKGRsnKeONQkPHY5KIh5ykrrnA+lwcEggyIbag=
Received: by 10.82.126.5 with SMTP id y5mr3176919buc.1183017608207;
	Thu, 28 Jun 2007 01:00:08 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id f8sm2837451nfh.2007.06.28.01.00.07
	(version=SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 01:00:07 -0700 (PDT)
Message-ID: <46836A89.6000708@gmail.com>
Date: Thu, 28 Jun 2007 10:00:09 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com> <46824361.4000300@gmail.com>
	<4682ABC0.7070209@internap.com>
In-Reply-To: <4682ABC0.7070209@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 20:26, Scott Leibrand wrote:
> Brian E Carpenter wrote:
>> Scott, you say
>>
>>> In a situation like this, I need to be able to resolve PTRs for hosts 
>>> using my neighboring networks' ULA space
>>
>> Why do you need to do this?
> 
> For all the same reasons I need to resolve PTRs of hosts on the 
> Internet.  I'm a network engineer, so my main reason for wanting PTRs is 
> for traceroute, but I'm sure anyone running a server serving the 
> neighborhoods would also like to be able to resolve information about 
> the IPs of connecting clients, etc.

The L in ULA means local. If you can *see* your neighbours' ULA prefixes,
they have become local to you, so I agree you will need their AAAA and PRT
records in your local DNS. If you use ULAs this way, you have added scope
boundaries in the DNS that must correspond to the routing scope boundaries
for ULA prefixes.

I don't think anything called Local should be used this way, but that's
an operational choice. It still doesn't mean that global DNS needs to know
anything about these prefixes. RFC 4193 seems correct to me.

      Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:04:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3ozN-0004pD-4i; Thu, 28 Jun 2007 04:04:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3ozL-0004ma-WE
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:04:28 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3oyz-0002Cu-48
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:04:27 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id BE2957301E;
	Thu, 28 Jun 2007 17:04:03 +0900 (JST)
Date: Thu, 28 Jun 2007 17:03:57 +0900
Message-ID: <m1k5topksy.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
In-Reply-To: <46827D36.7050307@ericsson.com>
References: <46827D36.7050307@ericsson.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipv6@ietf.org
Subject: Re: Privacy Addresses AUTH48 Changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Wed, 27 Jun 2007 11:07:34 -0400,
Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:

>    I would like to make the following editorial change to the upcoming 
> Privacy Addresses RFC.
> 
> I would like to add the following sentence to section 3.2.1 step 4
> 
> This list currently includes the reserved anycast interface identifiers 
> listed in [RFC2526]. This list may be expanded in the future to include 
> further interface identifiers.
> 
> after this sentence
> 
> Compare the generated identifier against a list of
> reserved interface identifiers and to those already
> assigned to an address on the local device.
> 
> Please let me know by June 29 2007 if you have any objections.

I don't have an objection to the idea of including RFC2526 per se, but
I have a concern:

This reference (RFC2526) was not included in
draft-ietf-ipv6-privacy-addrs-v2-05 and will be newly added to the
final RFC version-05, right?  If so, which category are you intending
to specify for this reference, normative vs informative?  It cannot be
normative since RFC2526 is a proposed standard while the privacy
address RFC will become a draft standard; but I'd categorize it as
normative in the above context because implementors must refer to
RFC2526 to implement the privacy-addrs spec.

A possibly related comment: there is a dangling reference in Section 8
of the 05 version of I-D:

   1.  Excluded certain interface identifiers from the range of
       acceptable interface identifiers.  Interface IDs such as those
       for reserved anycast addresses [RFC], etc.

I guess the "[RFC]" should actually be "[RFC2526]".  (Sorry if this
has already been pointed out).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:13:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3p7x-0005fy-8S; Thu, 28 Jun 2007 04:13:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3p7v-0005dp-Fo
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:13:19 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3p7H-0004MN-Te
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:13:19 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1547806ugf
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 01:12:39 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=FfUcZvGW2Z/B93orzL52WI2D0bYUoijbz3tOzHVeT4EZfBDRAnmH41drvyldH1NBOScV2MFxJyn1Ilgslz5pj8eYedrn8L+8T1elKEDISm4hDP0huTDnRapsfwMosbjjZhncnjWOkY8E5WVvtOM5cJ6ZuL6Emvxck3G8vit/i14=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=uOZC3HVgWdXfkXBzZKDtNkzLujtI2/lOV1NLsFhIzbM7n5SDcBonU/GCVXP2I+yMw0zM//0mOuw+wJIm3oVE4fzP8LzOyOcObE25AheFsPsXcSFudMCLOD3sTqdvG7osJeHDEpBLkvpKO4LnY3rBA9HCUFhpJ+g87mq9bRcAGNI=
Received: by 10.66.220.17 with SMTP id s17mr739537ugg.1183018359148;
	Thu, 28 Jun 2007 01:12:39 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id h1sm1506048ugf.2007.06.28.01.12.38
	(version=SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 01:12:38 -0700 (PDT)
Message-ID: <46836D78.1020202@gmail.com>
Date: Thu, 28 Jun 2007 10:12:40 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Per Heldal <heldal@eml.cc>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>	<467C1F53.9070600@spaghetti.zurich.ibm.com>	<20070622195429.GG31273@elvis.mu.org>	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	<20070623005010.GI31273@elvis.mu.org>	<467D0806.7030100@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	<467FE693.5060103@spaghetti.zurich.ibm.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	<46805763.6040708@apnic.net>	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>	<4681B179.2020301@internap.com>	<024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
	<1182945273.21026.97.camel@localhost.localdomain>
In-Reply-To: <1182945273.21026.97.camel@localhost.localdomain>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Stephen Sprunk <stephen@sprunk.org>, ARIN PPML <ppml@arin.net>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-27 13:54, Per Heldal wrote:
> On Tue, 2007-06-26 at 23:48 -0500, Stephen Sprunk wrote:
>> If we want to issue address space to folks for "private" use, it needs to be 
>> out of the same block(s) that the RIRs use to allocate space for "public" 
>> use, because sooner or later those "private" networks are going to end up 
>> being publicly routed.
> 
> But if we do this shouldn't we also take steps to prevent abuse
> (hijacking etc) of those "private" blocks. 

No, I don't think so. ULAs are for local use. We provide a mechanism
to ensure that they are extremely likely to be unique, but as long as
they are used locally, and confined locally both by routing and by
DNS, it actually doesn't matter operationally if someone else uses the
same prefix in their local area.

     Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:29:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3pMr-0005Eg-9b; Thu, 28 Jun 2007 04:28:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3pMp-0005Ea-Mp
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:28:43 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3pMf-0000gZ-0A
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:28:43 -0400
Received: by ug-out-1314.google.com with SMTP id k3so1551568ugf
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 01:28:32 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=B+2+Phk7HvfQqNyLvcM00FwI0KikWstTSdt92VGVwHyJBfiaOqdxzTlNg25Ag9ns7+ytRz5Pj8pIvOUhAi9ZJLAUdzbqanmqSYi/mmTPF0Q29IqSXNl72gTJapS29HOYG07o3flzQonYEOGhZXe56opmkcV3ZiwRHOdT5szcN54=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KloEMinS3dAPP8glLbSYtPlGwlHoaEmc0kLkEUntu2JgpnJHU8nY/iZwCYQvYzuue3Omrzy1wYz1pQE++I2A90N6dE3YUJOwPIft45LJqA30mpP86ILBuT3Et/3cFxXqOfWDiNeFHf+lyd/8/ec1uzx6gr9FFH8fbhQprzlUgaQ=
Received: by 10.67.19.11 with SMTP id w11mr1764589ugi.1183019312340;
	Thu, 28 Jun 2007 01:28:32 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 39sm1458498ugb.2007.06.28.01.28.30
	(version=SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 01:28:30 -0700 (PDT)
Message-ID: <4683712F.1010602@gmail.com>
Date: Thu, 28 Jun 2007 10:28:31 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com>
In-Reply-To: <46834717.3090102@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-28 07:28, Scott Leibrand wrote:
> I would support Paul's proposed changes below, and the resulting draft.

I wouldn't, at this time. We need to see where the RAM/RRG discussions
lead. If they lead to a clear need for registered globally unique
identifiers in IPv6 address format, something like this might be right
(unless we also need a cryptographic property).

I have a strong feeling there is no consensus forming...

     Brian

> -Scott
> 
> Paul Vixie wrote:
>> these are my comments on the following I-D:
>>
>>  
>>>     Title      : Centrally Assigned Unique Local IPv6 Unicast Addresses
>>>     Author(s)  : R. Hinden, B. Haberman
>>>     Filename   : draft-ietf-ipv6-ula-central-02.txt
>>>     Pages      : 11
>>>     Date       : 2007-6-18
>>>
>>> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt>
>>>     
>>
>> first, in 3.1, this table:
>>
>>       | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
>>       +--------+-+------------+-----------+----------------------------+
>>       | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
>>       +--------+-+------------+-----------+----------------------------+
>>
>> should be replaced with this one:
>>
>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>>       +--------+-+----------+---------+---------+----------+
>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>>       +--------+-+----------+---------+---------+----------+
>>
>> where "Prefix" and "L" are defined as shown in central-02, and the other
>> fields are defined as follows:
>>
>>      Reserved            Set to 0 by all implementors of this 
>> specification,
>>                          but may be set to nonzero by implementors of 
>> a later
>>                          specification.
>>
>>      RIR Num             Identifiers assigned by IANA for each /16 as
>>                          allocated to an Regional Internet Address 
>> Registry
>>                          (RIR).  For direct allocations by IANA, the 
>> value
>>                          of zero (0x0000) is reserved.
>>
>>      LIR Num             Identifiers assigned by RIR for each /32 as
>>                          allocated to a Local Internet Address 
>> Registry (LIR).
>>                          For direct allocations by an RIR, the value 
>> of zero
>>                          (0x0000) is reserved.
>>
>>      User Num            Identifier assigned by an end user or network
>>                          operator who implements this specification.
>>
>> second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 
>> 3.2.3.
>>
>> third, replace section 7.0 with the following:
>>
>> ---
>>
>> 7.0 IANA Considerations
>>
>>     IANA is hereby instructed to reserve address block FC::/7 for private
>>     unique addresses, and to allocate /32 blocks to Regional Internet 
>>     Address Registries (RIRs) who request same after adopting policies
>>     consistent with this specification.  Allocation shall be similar in
>>     all ways to normal IANA address allocation to RIRs, including but not
>>     limited to IN-ADDR.ARPA delegations and WHOIS records.
>>
>> ---
>>
>> Paul Vixie
>> not speaking for ISC
>> not speaking for ARIN
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>   
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:46:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3peL-0002TU-5V; Thu, 28 Jun 2007 04:46:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3peJ-0002MG-I4
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:46:47 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3peB-0006wH-5s
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:46:47 -0400
Received: from compute2.internal (compute2.internal [10.202.2.42])
	by out1.messagingengine.com (Postfix) with ESMTP id EC727266D;
	Thu, 28 Jun 2007 04:46:38 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute2.internal (MEProxy); Thu, 28 Jun 2007 04:46:38 -0400
X-Sasl-enc: u6sNqyQHF0ZpWApjY3Tq5z9V+UE1ptEHFq3Z5+x7kSdw 1183020397
Received: from [127.0.0.1] (anon.xmission.com [166.70.207.2])
	by mail.messagingengine.com (Postfix) with ESMTP id 4A2154D69;
	Thu, 28 Jun 2007 04:46:34 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <46836D78.1020202@gmail.com>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B5@XCH-NW-7V2.nw.nos.boeing.com>
	<467C1F53.9070600@spaghetti.zurich.ibm.com>
	<20070622195429.GG31273@elvis.mu.org>
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>
	<20070623005010.GI31273@elvis.mu.org>
	<467D0806.7030100@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>
	<467FE693.5060103@spaghetti.zurich.ibm.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>
	<46805763.6040708@apnic.net>
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>
	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>
	<4681B179.2020301@internap.com>
	<024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>
	<1182945273.21026.97.camel@localhost.localdomain>
	<46836D78.1020202@gmail.com>
Content-Type: text/plain
Date: Thu, 28 Jun 2007 10:46:26 +0200
Message-Id: <1183020386.21421.35.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Stephen Sprunk <stephen@sprunk.org>, ARIN PPML <ppml@arin.net>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [ppml] draft-ietf-ipv6-ula-central-02.txt use cases
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 2007-06-28 at 10:12 +0200, Brian E Carpenter wrote:
> On 2007-06-27 13:54, Per Heldal wrote:
> > On Tue, 2007-06-26 at 23:48 -0500, Stephen Sprunk wrote:
> >> If we want to issue address space to folks for "private" use, it needs to be 
> >> out of the same block(s) that the RIRs use to allocate space for "public" 
> >> use, because sooner or later those "private" networks are going to end up 
> >> being publicly routed.
> > 
> > But if we do this shouldn't we also take steps to prevent abuse
> > (hijacking etc) of those "private" blocks. 
> 
> No, I don't think so. ULAs are for local use. We provide a mechanism
> to ensure that they are extremely likely to be unique, but as long as
> they are used locally, and confined locally both by routing and by
> DNS, it actually doesn't matter operationally if someone else uses the
> same prefix in their local area.

I wasn't talking about ULA at all, but about an attempt to limit abuse
of PI or even PA space whenever such blocks are allocated but not
announced externally. Whether allocated PI is used for private purposes
by accident or intentionally doesn't matter in that respect. ULA is no
problem as it's trivial to block all of it with one single
config-statement.


The rest of my rant was about my wish to formalise and automate the
relation between allocation policies and operational practises. I.e. why
keep pretending registry-policies have nothing to do with routing when
so many IDRs in the DFZ has a config full of stuff derived from those
policies?


//per


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 04:55:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3pmI-0001tp-EC; Thu, 28 Jun 2007 04:55:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3pmG-0001ta-1W
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:55:00 -0400
Received: from wx-out-0506.google.com ([66.249.82.232])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3plL-0000Dp-6t
	for ipv6@ietf.org; Thu, 28 Jun 2007 04:55:00 -0400
Received: by wx-out-0506.google.com with SMTP id h27so387498wxd
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 01:54:02 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=pGPCdUP79sAQhFTE95657kXXYLM+otA5WrvSIeTB1nwi2ECtTk+O+USM/JCoLiynu5lRcmD5RR01sZGK6R4oK1kPfMbwi3oVyCVTBJi/D9ShpHjec5mWvc3ouo9w5WqjR1NdcQI+4qjC2HoSf/qhhW7+z6HifSTkm4Pu1MkPIO0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ef3w78oMwkBZNRTSVOX3ZS00F43I5hUS0GGduFHWBJmdZ3e1NnRCACR7lJkgYxkyihK/IK+DJOVCEIYACLlxKxFaysrfNYv5cGpVkzJvMlM54F699NAl9C8wm5vLlTmhaNhhbDx5ocrGMmV+r4bqma9I6toZD7slmPf9TwoVTwk=
Received: by 10.78.171.20 with SMTP id t20mr754957hue.1183020838677;
	Thu, 28 Jun 2007 01:53:58 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id d27sm9014517nfh.2007.06.28.01.53.57
	(version=SSLv3 cipher=RC4-MD5); Thu, 28 Jun 2007 01:53:58 -0700 (PDT)
Message-ID: <46837727.70207@gmail.com>
Date: Thu, 28 Jun 2007 10:53:59 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Per Heldal <heldal@eml.cc>
References: <200706221709.l5MH9uEN003458@mail.reprise.com>	
	<467C1F53.9070600@spaghetti.zurich.ibm.com>	
	<20070622195429.GG31273@elvis.mu.org>	
	<467C2EE6.3070100@spaghetti.zurich.ibm.com>	
	<20070623005010.GI31273@elvis.mu.org>	
	<467D0806.7030100@spaghetti.zurich.ibm.com>	
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B7@XCH-NW-7V2.nw.nos.boeing.com>	
	<467FDEAA.1020503@spaghetti.zurich.ibm.com>	
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8B9@XCH-NW-7V2.nw.nos.boeing.com>	
	<467FE693.5060103@spaghetti.zurich.ibm.com>	
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8BB@XCH-NW-7V2.nw.nos.boeing.com>	
	<E727B713-793C-49E5-A15A-58334396573B@apple.com>	
	<46805763.6040708@apnic.net>	
	<CA0864AA-A285-4135-BAF3-D04F8A3E4341@apple.com>	
	<46807C77.2020101@internap.com><77167.1182834776@sa.vix.com>	
	<4681B179.2020301@internap.com>	
	<024b01c7b876$94b06b70$443816ac@atlanta.polycom.com>	
	<1182945273.21026.97.camel@localhost.localdomain>	
	<46836D78.1020202@gmail.com>
	<1183020386.21421.35.camel@localhost.localdomain>
In-Reply-To: <1183020386.21421.35.camel@localhost.localdomain>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Stephen Sprunk <stephen@sprunk.org>, ARIN PPML <ppml@arin.net>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Actaully about PI [Re: [ppml] draft-ietf-ipv6-ula-central-02.txt
 use cases]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-28 10:46, Per Heldal wrote:
> On Thu, 2007-06-28 at 10:12 +0200, Brian E Carpenter wrote:
>> On 2007-06-27 13:54, Per Heldal wrote:
>>> On Tue, 2007-06-26 at 23:48 -0500, Stephen Sprunk wrote:
>>>> If we want to issue address space to folks for "private" use, it needs to be 
>>>> out of the same block(s) that the RIRs use to allocate space for "public" 
>>>> use, because sooner or later those "private" networks are going to end up 
>>>> being publicly routed.
>>> But if we do this shouldn't we also take steps to prevent abuse
>>> (hijacking etc) of those "private" blocks. 
>> No, I don't think so. ULAs are for local use. We provide a mechanism
>> to ensure that they are extremely likely to be unique, but as long as
>> they are used locally, and confined locally both by routing and by
>> DNS, it actually doesn't matter operationally if someone else uses the
>> same prefix in their local area.
> 
> I wasn't talking about ULA at all, but about an attempt to limit abuse
> of PI or even PA space whenever such blocks are allocated but not
> announced externally. Whether allocated PI is used for private purposes
> by accident or intentionally doesn't matter in that respect. ULA is no
> problem as it's trivial to block all of it with one single
> config-statement.

Then we agree, but please change the Subject when you change the subject :-)

     Brian

> 
> 
> The rest of my rant was about my wish to formalise and automate the
> relation between allocation policies and operational practises. I.e. why
> keep pretending registry-policies have nothing to do with routing when
> so many IDRs in the DFZ has a config full of stuff derived from those
> policies?
> 
> 
> //per
> 
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 06:26:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3rBJ-0004bu-JE; Thu, 28 Jun 2007 06:24:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3rBI-0004Yn-8r
	for ipv6@ietf.org; Thu, 28 Jun 2007 06:24:56 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3rB6-0004bR-19
	for ipv6@ietf.org; Thu, 28 Jun 2007 06:24:56 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 3C637140C1EE;
	Thu, 28 Jun 2007 12:24:40 +0200 (CEST)
Message-ID: <46838C69.3050601@spaghetti.zurich.ibm.com>
Date: Thu, 28 Jun 2007 11:24:41 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
In-Reply-To: <13846.1183003509@sa.vix.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1995161560=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1995161560==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig7F6C6BC797AD45A1106DCDF8"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7F6C6BC797AD45A1106DCDF8
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Paul Vixie wrote:
[..]
> first, in 3.1, this table:
[..]
> should be replaced with this one:
>=20
>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>       +--------+-+----------+---------+---------+----------+
>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>       +--------+-+----------+---------+---------+----------+

Looks okayish but does bring back the idea of sTLA's a bit. But there is
another thing that this causes: it sort of allows aggregation.

How is this any different at all from what I proposed in another
message: One setups an organization called "Local IP Addresses Org" and
sets up an LIR, requests a /32, one one has 65k /48's to provide to
endusers. Members have a share in the org, and each and every single one
of them can already make sure that the LIR fees are paid (there are no
equipment or transit etc fees) and presto. You have EXACTLY what you
have above, but with the added benefit that it is globally unique
address space with full RIR support. The LIR can shoot ip6.arpa
delegations per /48 if they want directly into the RIR's nameservers,
thus that is also covered. Connectivity one could also provide just like
a normal LIR if really wanted.


Another problem with the above is that it doesn't allow for direct
end-user assignments. Folks still have to go through a LIR. This thus
doesn't provide these people with a "direct assignment" and they are
still bound to the LIR.

=46rom what I understand the people who really want this kind of "local"
address space want to have a *direct* assignment from a RIR or IANA.
This as it is expected that a RIR won't go belly up, a LIR might do so
though.

As such, if you really want to have ULA-C (which I really think is
unnecessary because of arguments I've reiterated a couple of times
already also in other messages and the above) I would at least propose:

| 7 bits |1| 8 bits |16 bits| 16 bits |  16 bits  | 64 bits   |
+--------+-+--------+-------+---------+-----------+-----------+
| Prefix |L|Reserved|RIR ID | Site ID | Subnet ID | Iface ID  |
+--------+-+--------+-------+---------+-----------+-----------+
                                      | /48 for the end-site  |
                                      +-----------------------+

Same scheme of allocation, but takes out the LIR portion and thus allows
RIR's to delegate this directly to endusers.

[..]
> second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 3=
=2E2.3.

Agree.

> third, replace section 7.0 with the following:

Don't agree at all. (btw it is fc00::/7 not fc::/7 :)

The moment you introduce support for IP6.ARPA (not IN-ADDR.ARPA) and
require delegations to be possible there really is no difference between
PI and this kind of address space (except the prefix from which they are
allocated, they can be filtered on that but still).

The reasons against having support for reverse DNS:
 - You are introducing a *local* space into the *global* Internet.
   As such it is required to have Internet connectivity (with all the
   hacks that are required to be able to talk to the ip6.arpa servers
   and the chain along it to get to those reverse DNS servers).

   One thus has to setup "DNS gateway" boxes for reverse DNS which
   are able to contact the global Internet to reach those machines.
   If you can set those up, why not configure them directly with the
   content of your *local* zones.

   Also, it only covers the *reverse* of this address space, it does not
   solve the *forwards* that point to the address space. It might be
   just me, but users type forward more than reverses.
   One will thus have to merge forward zones anyway, if you can do that
   you can also setup a reverse zone at the same time.

 - Introducing the ability to have ip6.arpa delegations will make sure
   that the RIR will have to do more work for this. The delegations
   have to point to DNS servers on the *public* Internet (strange as
   we are talking about *local* addresses :) These DNS servers thus
   have to be either on stable IP's (as such every such organization
   requires to have also a Public PI space for this solely (they can't
   depend on the local space to be PA so why should they for the global
   block?) The other would be that they keep asking the RIR all the time
   to change the DNS server delegation as they swapped ISP's again.
   This thus costs the RIR a lot of resources/time/bla and thus is more
   costly than having the requester simply have PI space.

If one *really* requires that there will be reverse that is
'automatically setup' (ignoring that you still have to do it for the
forward) then define in the draft the method that James Woodyatt
proposed of using synthesized reverse records for 0.0.c.f.ip6.arpa.
And then simply declaring that the highest subnet (::ffff:<64bits>)
contains at ::53 a DNS server serving reverse ip6.arpa for that zone.

Easiest of course is to simply set up the forward+reverse servers at the
point where you interconnect with the other network. If one says "but we
interconnect automatically", then also add in that automated framework a
way of exchanging DNS servers and zones.

The big question with all of this really is: why can't these people who
need this address space (still I haven't seen a good use-case*) simply
use PI? As that is what they really need, nothing else. If they need
something else, then please define why they need something else and what
that something else is. Having a solution for an unknown problem is not
the way to go IMHO.

Now, I hope that the above was constructive ;)

Greets,
 Jeroen

* =3D I did see the one about planes flying around the world who have
their internal systems in a static /48 and when they come to other
places they can automatically interconnect to those networks, but why
can't those use PI either? :)



--------------enig7F6C6BC797AD45A1106DCDF8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaDjG0uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2JnAJsFDiRPf5QtOZIa1h2Yp+kS27Lo
BwCfVMNUmdEhZZanlqBw2DAYo6DDAwI=
=eUs5
-----END PGP SIGNATURE-----

--------------enig7F6C6BC797AD45A1106DCDF8--


--===============1995161560==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1995161560==--




From ipv6-bounces@ietf.org Thu Jun 28 10:45:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3vF4-00016N-8z; Thu, 28 Jun 2007 10:45:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3vF2-00010I-Rd
	for ipv6@ietf.org; Thu, 28 Jun 2007 10:45:04 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3vF2-0003y5-IM
	for ipv6@ietf.org; Thu, 28 Jun 2007 10:45:04 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 3FE2C11431
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 14:44:31 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 28 Jun 2007 08:20:11 +0200."
	<Pine.LNX.4.64.0706280817280.29317@chandra.student.uit.no> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<Pine.LNX.4.64.0706280817280.29317@chandra.student.uit.no> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 14:44:31 +0000
Message-ID: <11365.1183041871@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > where "Prefix" and "L" are defined as shown in central-02, and the other
> > fields are defined as follows:
> 
> striks me as almost the same as the good old sTLA...

as with many other old things that become new, we know a lot more now about
what we're trying to do than we did before, and the "almost" is important,
this isn't sTLA.

> > third, replace section 7.0 with the following:
> >
> > ---
> >
> > 7.0 IANA Considerations
> >
> >    IANA is hereby instructed to reserve address block FC::/7 for private
> >    unique addresses, and to allocate /32 blocks to Regional Internet
> >    Address Registries (RIRs) who request same after adopting policies
> >    consistent with this specification.  Allocation shall be similar in
> >    all ways to normal IANA address allocation to RIRs, including but not
> >    limited to IN-ADDR.ARPA delegations and WHOIS records.
> >
> > ---
> 
> so we are talking about full reverse control delegated to the person that
> get this ULA-C block?

yes.

> except this piece about DNS mention above it look more promissing than the
> original draft.

fred templin has made a compelling case here that the ad-hoc nature of ULA-C
routing precludes the normal "put override configs in every resolver" logic
described in RFC 1918.  for PTR lookups to work in fred's case, there has to
be global DNS.  note that global DNS isn't a requirement -- anyone with ULA-C
who prefers to use RFC 1918-like overrides in all their own resolvers can do
that.  the instructions in the replacement for section 7.0 above are there to
ensure that those who want their ULA-C PTRs to be in the global DNS can have
that.  (if you don't like it, then don't use it, but don't tell others they
can't have it either, please.  if they want it, let them have it, please.)

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 10:47:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3vHc-0003AW-Gb; Thu, 28 Jun 2007 10:47:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3vHb-00037l-Ic
	for ipv6@ietf.org; Thu, 28 Jun 2007 10:47:43 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3vHV-0001eB-O5
	for ipv6@ietf.org; Thu, 28 Jun 2007 10:47:43 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 18C1611431
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 14:47:37 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 28 Jun 2007 10:28:31 +0200."
	<4683712F.1010602@gmail.com> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com> <46834717.3090102@internap.com>
	<4683712F.1010602@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 14:47:37 +0000
Message-ID: <14556.1183042057@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter <brian.e.carpenter@gmail.com>:
> 
> Scott Leibrand <sleibrand@internap.com>:
> > 
> > I would support Paul's proposed changes below, and the resulting draft.
> 
> I wouldn't, at this time.  We need to see where the RAM/RRG discussions
> lead.  If they lead to a clear need for registered globally unique
> identifiers in IPv6 address format, something like this might be right
> (unless we also need a cryptographic property).

where are those discussions being held, and can you post a summary, and why
are we wasting our keystrokes discussing this if there's a preclusive topic
being discussed somewhere entirely else?

> I have a strong feeling there is no consensus forming...

i disagree, i've been immersed in this for a month now, and my draft edits
as proposed last night represent my understanding of a potential consensus,
which unlike you i can feel forming.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 11:01:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3vUV-0001NE-Jb; Thu, 28 Jun 2007 11:01:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3vUU-0001Ls-I1
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:01:02 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3vUK-0007Aj-Ku
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:01:02 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 1B41E11431
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 15:00:52 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 28 Jun 2007 11:24:41 +0100."
	<46838C69.3050601@spaghetti.zurich.ibm.com> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46838C69.3050601@spaghetti.zurich.ibm.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 15:00:52 +0000
Message-ID: <15110.1183042852@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar <jeroen@unfix.org>:
> 
> Paul Vixie <vixie@isc.org>:
> > 
> >       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> >       +--------+-+----------+---------+---------+----------+
> >       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> >       +--------+-+----------+---------+---------+----------+
> 
> Looks okayish but does bring back the idea of sTLA's a bit. But there is
> another thing that this causes: it sort of allows aggregation.

i'd say deliberately not.  if LIR's receive /48's then when they hand out
address space to end sites it'll be in groups of 5 and 10 /64's.  we can
add text recommending that RIR's and LIR's deliberately randomize or skip
even/odd or something to prevent accidental or opportunistic aggregation,
though.

> How is this any different at all from what I proposed in another
> message: One setups an organization called "Local IP Addresses Org" and
> sets up an LIR, requests a /32, one one has 65k /48's to provide to
> endusers.

you are so prolific here that your own words got lost in your own torrent?

> Members have a share in the org, and each and every single one
> of them can already make sure that the LIR fees are paid (there are no
> equipment or transit etc fees) and presto. You have EXACTLY what you
> have above, but with the added benefit that it is globally unique
> address space with full RIR support.

except that payments and shares are out of scope, you might be right.

> Another problem with the above is that it doesn't allow for direct
> end-user assignments. Folks still have to go through a LIR. This thus
> doesn't provide these people with a "direct assignment" and they are
> still bound to the LIR.

then you didn't read my text, because it says the opposite of that assertion.

> As such, if you really want to have ULA-C (which I really think is
> unnecessary because of arguments I've reiterated a couple of times
> already also in other messages and the above) I would at least propose:
> 
> | 7 bits |1| 8 bits |16 bits| 16 bits |  16 bits  | 64 bits   |
> +--------+-+--------+-------+---------+-----------+-----------+
> | Prefix |L|Reserved|RIR ID | Site ID | Subnet ID | Iface ID  |
> +--------+-+--------+-------+---------+-----------+-----------+
>                                       | /48 for the end-site  |
>                                       +-----------------------+

i don't use /64's for my links.  EUI64 is going to die, and die hard.  let's
not overspecify the mantissa.  i said "80 bits for User Num" and i meant that.
(if someone wants to use /64's for their links, they can do that under this
proposal, but we can't reasonably require it, and the recommendations for it
are already present in plenty of other RFCs.)

> Same scheme of allocation, but takes out the LIR portion and thus allows
> RIR's to delegate this directly to endusers.

read my text.  direct allocations are already possible.

> > third, replace section 7.0 with the following:
> 
> Don't agree at all. (btw it is fc00::/7 not fc::/7 :)

i've seen plenty of people say fc00::/7 and i just don't get it.  you might
as well say fc00:0000:0000:0000:0000:0000:0000:0000/7.  when i wrote the
reference implementation of inet_ntop(), i only emitted the part of the
mantissa that was actually covered by the cidrlen.  this isn't scientific
notation where you want to show the degree of accuracy of your measurements.

> The moment you introduce support for IP6.ARPA (not IN-ADDR.ARPA) and
> require delegations to be possible there really is no difference between
> PI and this kind of address space (except the prefix from which they are
> allocated, they can be filtered on that but still).

fred made a compelling case for why ad-hoc ULA-C routing precluded the kind
of resolver config overrides that we're supposed to use for RFC 1918.  any
ULA-C user who doesn't want their PTR's in the global DNS should not put any
there, but it's not our place here and now to tell them that they just can't.

> If one *really* requires that there will be reverse that is 'automatically
> setup' (ignoring that you still have to do it for the forward) then define
> in the draft the method that James Woodyatt proposed of using synthesized
> reverse records for 0.0.c.f.ip6.arpa.  And then simply declaring that the
> highest subnet (::ffff:<64bits>) contains at ::53 a DNS server serving
> reverse ip6.arpa for that zone.

this is attractive, but it's an architectural change that we'd have to review
for other connectivity realms, like the DFZ, and i don't want to argue it as
part of settling the ULA-C question.  if you like this idea, propose it and
let's get into its merits and implications.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 11:15:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3viJ-0007bW-Ac; Thu, 28 Jun 2007 11:15:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3viH-0007bF-TQ
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:15:17 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3viH-0006ji-JG
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:15:17 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5SFEgf9002847
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 28 Jun 2007 08:14:42 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5SFEf0m025338; Thu, 28 Jun 2007 08:14:41 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5SFEfHR025310; Thu, 28 Jun 2007 08:14:41 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 08:14:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jun 2007 08:14:15 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <13846.1183003509@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace5OasPboZqjwW/S6eYac+uGuYsGAAW6JmA
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Jun 2007 15:14:41.0318 (UTC)
	FILETIME=[0D080C60:01C7B997]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: 
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

My use case questions that still need to be satisfied are:

  1) can any site (large or small) get a ULA-C?
  2) can the ULA-C's be obtained at a nominal cost?
  3) can the ULA-C's be published in the global DNS
     forward and reverse?
  4) can the ULA-C's be kept out of the DFZ?

If Paul's proposal answers all of these as "yes", then
I have no objections.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Wednesday, June 27, 2007 9:05 PM
> To: ipv6@ietf.org
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt=20
>=20
> these are my comments on the following I-D:
>=20
> > 	Title      : Centrally Assigned Unique Local IPv6=20
> Unicast Addresses
> > 	Author(s)  : R. Hinden, B. Haberman
> > 	Filename   : draft-ietf-ipv6-ula-central-02.txt
> > 	Pages      : 11
> > 	Date       : 2007-6-18
> >=20
> >=20
> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-centr
al-02.txt>
>=20
> first, in 3.1, this table:
>=20
>       | 7 bits |1|  40 bits   |  16 bits  |          64 bits =20
>          |
>      =20
> +--------+-+------------+-----------+----------------------------+
>       | Prefix |L| Global ID  | Subnet ID |        Interface=20
> ID        |
>      =20
> +--------+-+------------+-----------+----------------------------+
>=20
> should be replaced with this one:
>=20
>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>       +--------+-+----------+---------+---------+----------+
>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>       +--------+-+----------+---------+---------+----------+
>=20
> where "Prefix" and "L" are defined as shown in central-02,=20
> and the other
> fields are defined as follows:
>=20
>      Reserved            Set to 0 by all implementors of this=20
> specification,
>                          but may be set to nonzero by=20
> implementors of a later
>                          specification.
>=20
>      RIR Num             Identifiers assigned by IANA for each /16 as
>                          allocated to an Regional Internet=20
> Address Registry
>                          (RIR).  For direct allocations by=20
> IANA, the value
>                          of zero (0x0000) is reserved.
>=20
>      LIR Num             Identifiers assigned by RIR for each /32 as
>                          allocated to a Local Internet=20
> Address Registry (LIR).
>                          For direct allocations by an RIR,=20
> the value of zero
>                          (0x0000) is reserved.
>=20
>      User Num            Identifier assigned by an end user or network
>                          operator who implements this specification.
>=20
> second, delete all of section 3.2 including subsections=20
> 3.2.1, 3.2.2, 3.2.3.
>=20
> third, replace section 7.0 with the following:
>=20
> ---
>=20
> 7.0 IANA Considerations
>=20
>     IANA is hereby instructed to reserve address block FC::/7=20
> for private
>     unique addresses, and to allocate /32 blocks to Regional Internet=20
>     Address Registries (RIRs) who request same after adopting policies
>     consistent with this specification.  Allocation shall be=20
> similar in
>     all ways to normal IANA address allocation to RIRs,=20
> including but not
>     limited to IN-ADDR.ARPA delegations and WHOIS records.
>=20
> ---
>=20
> Paul Vixie
> not speaking for ISC
> not speaking for ARIN
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 11:35:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3w1Y-0000rg-5A; Thu, 28 Jun 2007 11:35:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3w1W-0000rb-ER
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:35:10 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3w0V-0004xv-85
	for ipv6@ietf.org; Thu, 28 Jun 2007 11:35:10 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5SFY538053924
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 17:34:06 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5SFY54I024935; Thu, 28 Jun 2007 17:34:05 +0200
Date: Thu, 28 Jun 2007 17:34:05 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Paul Vixie <paul@vix.com>
In-Reply-To: <14556.1183042057@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0706281733281.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com> <4683712F.1010602@gmail.com> 
	<14556.1183042057@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 28 Jun 2007, Paul Vixie wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com>:
<snip>
>> I have a strong feeling there is no consensus forming...
>
> i disagree, i've been immersed in this for a month now, and my draft edits
> as proposed last night represent my understanding of a potential consensus,
> which unlike you i can feel forming.

Paul's suggestion did sound okay and guess there can be a potential 
consensus on that one?

-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 12:10:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3wYt-0001Li-DU; Thu, 28 Jun 2007 12:09:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3wYr-0001LX-5Y
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:09:37 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3wY7-0000p3-6c
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:09:37 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 2EF5211431;
	Thu, 28 Jun 2007 16:08:37 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-Reply-To: Your message of "Thu, 28 Jun 2007 08:14:15 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 16:08:37 +0000
Message-ID: <23417.1183046917@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
> 
> My use case questions that still need to be satisfied are:
> 
>   1) can any site (large or small) get a ULA-C?
>   2) can the ULA-C's be obtained at a nominal cost?
>   3) can the ULA-C's be published in the global DNS
>      forward and reverse?
>   4) can the ULA-C's be kept out of the DFZ?
> 
> If Paul's proposal answers all of these as "yes", then
> I have no objections.

yes to all four.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 12:19:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3wiC-0007zB-Ea; Thu, 28 Jun 2007 12:19:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3wiB-0007x0-H8
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:19:15 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3wiB-0003zj-8s
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:19:15 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5SGIgSJ017904
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 28 Jun 2007 09:18:42 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5SGIfUg016690; Thu, 28 Jun 2007 09:18:41 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5SGIapo016493; Thu, 28 Jun 2007 09:18:41 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 09:18:38 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jun 2007 09:18:14 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D8@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <23417.1183046917@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace5nqaqYsEEuBSXQTeXPvtuZQxUKwAAHzbg
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<23417.1183046917@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>
X-OriginalArrivalTime: 28 Jun 2007 16:18:38.0698 (UTC)
	FILETIME=[FC49C4A0:01C7B99F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: ipv6@ietf.org
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Maybe I should have qualified 2) by asking how nominal is
"nominal"? Just as reminder, I have already stated that my
opinions do not necessarily reflect a corporate position:

http://www1.ietf.org/mail-archive/web/ipv6/current/msg07620.html

Fred
fred.l.templin@boeing.com=20

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Thursday, June 28, 2007 9:09 AM
> To: Templin, Fred L
> Cc: ipv6@ietf.org
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt=20
>=20
> > From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
> >=20
> > My use case questions that still need to be satisfied are:
> >=20
> >   1) can any site (large or small) get a ULA-C?
> >   2) can the ULA-C's be obtained at a nominal cost?
> >   3) can the ULA-C's be published in the global DNS
> >      forward and reverse?
> >   4) can the ULA-C's be kept out of the DFZ?
> >=20
> > If Paul's proposal answers all of these as "yes", then
> > I have no objections.
>=20
> yes to all four.
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 12:36:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3wz2-0000is-Hh; Thu, 28 Jun 2007 12:36:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3wz1-0000ff-5y
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:36:39 -0400
Received: from sa.vix.com ([204.152.187.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3wz0-0005p3-Ut
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:36:39 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 00DA111438
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 16:36:06 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Thu, 28 Jun 2007 09:18:14 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D8@XCH-NW-7V2.nw.nos.boeing.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<23417.1183046917@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D8@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 16:36:05 +0000
Message-ID: <28425.1183048565@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > > 2) can the ULA-C's be obtained at a nominal cost?

> > yes to all four.

> Maybe I should have qualified 2) by asking how nominal is "nominal"?

ietf does not control the costs of this kind of operational activity.  all
that an rfc can do is ask that the costs be nominal and direct iana to only
give address space out to rir's who have adopted policies consistent with
the specification.  presumably iana will look to the rir's, which have strong
and open bottom-up governance models, to determine the meaning of "nominal".

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 12:40:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3x2e-0007Hx-5r; Thu, 28 Jun 2007 12:40:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3x2c-0007Hq-9u
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:40:22 -0400
Received: from mail3.microsoft.com ([131.107.115.214] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3x2O-0003cv-GC
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:40:22 -0400
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.70.186) by
	TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 28 Jun 2007 09:40:08 -0700
Received: from tk5-exmlt-w600.wingroup.windeploy.ntdev.microsoft.com
	(157.54.70.135) by tk5-exhub-c103.redmond.corp.microsoft.com
	(157.54.70.186)
	with Microsoft SMTP Server id 8.0.726.0; Thu, 28 Jun 2007 09:40:07 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	(157.54.62.24) by tk5-exmlt-w600.wingroup.windeploy.ntdev.microsoft.com
	(157.54.70.135) with Microsoft SMTP Server id 8.1.85.3; Thu, 28 Jun 2007
	09:40:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jun 2007 09:39:35 -0700
Message-ID: <70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace5OasPboZqjwW/S6eYac+uGuYsGAAW6JmAAAM4JjA=
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
From: Christian Huitema <huitema@windows.microsoft.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Paul Vixie <paul@vix.com>, 
	<ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I would support Paul proposal, but with one small change. Paul proposes
a delegation hierarchy in the ULA-C space:

> > should be replaced with this one:
> >
> >       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> >       +--------+-+----------+---------+---------+----------+
> >       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> >       +--------+-+----------+---------+---------+----------+

That is fine, but I would rather call the delegation field by a
different name than "RIR Num". Call in it RIR assumes that the numbers
can only be allocated by the current set of regional registries. I don't
see any technical reason to carve this policy in a standard. I would
much prefer a neutral designation, e.g. "Registry Number".

-- Christian Huitema



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 12:44:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3x6E-0007Sv-Pr; Thu, 28 Jun 2007 12:44:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3x6D-0007Sq-RU
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:44:05 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3x5S-0004bM-G8
	for ipv6@ietf.org; Thu, 28 Jun 2007 12:44:05 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5SGhHlW022438
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 28 Jun 2007 11:43:18 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5SGhH9o018198; Thu, 28 Jun 2007 11:43:17 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5SGhEdd018049; Thu, 28 Jun 2007 11:43:17 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 09:43:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jun 2007 09:42:39 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D9@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace5OasPboZqjwW/S6eYac+uGuYsGAAW6JmAAAM4JjAAAES3YA==
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Christian Huitema" <huitema@windows.microsoft.com>,
	"Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Jun 2007 16:43:14.0298 (UTC)
	FILETIME=[6BD075A0:01C7B9A3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Christian Huitema [mailto:huitema@windows.microsoft.com]=20
> Sent: Thursday, June 28, 2007 9:40 AM
> To: Templin, Fred L; Paul Vixie; ipv6@ietf.org
> Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt=20
>=20
> I would support Paul proposal, but with one small change.=20
> Paul proposes
> a delegation hierarchy in the ULA-C space:
>=20
> > > should be replaced with this one:
> > >
> > >       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> > >       +--------+-+----------+---------+---------+----------+
> > >       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> > >       +--------+-+----------+---------+---------+----------+
>=20
> That is fine, but I would rather call the delegation field by a
> different name than "RIR Num". Call in it RIR assumes that the numbers
> can only be allocated by the current set of regional=20
> registries. I don't
> see any technical reason to carve this policy in a standard. I would
> much prefer a neutral designation, e.g. "Registry Number".

I agree.

Fred
fred.l.templin@boeing.com

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 13:36:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3xu2-00043C-4M; Thu, 28 Jun 2007 13:35:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3xu1-000415-GC
	for ipv6@ietf.org; Thu, 28 Jun 2007 13:35:33 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3xtj-0002Dx-WC
	for ipv6@ietf.org; Thu, 28 Jun 2007 13:35:33 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id 84616A7B7FE
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:35:15 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 7030140088
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:35:15 -0700 (PDT)
X-AuditID: 11807126-a30cfbb0000007dd-0e-4683f1533cf3
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 553704005C
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:35:15 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46838C69.3050601@spaghetti.zurich.ibm.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46838C69.3050601@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9EC676E6-9B24-411A-87EF-DAF3E2C0D902@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 28 Jun 2007 10:35:13 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 28, 2007, at 03:24, Jeroen Massar wrote:
>
> If one *really* requires that there will be reverse that is  
> 'automatically setup' (ignoring that you still have to do it for  
> the forward) then define in the draft the method that James  
> Woodyatt proposed of using synthesized reverse records for  
> 0.0.c.f.ip6.arpa.  And then simply declaring that the highest  
> subnet (::ffff:<64bits>)
> contains at ::53 a DNS server serving reverse ip6.arpa for that zone.

I don't think I can claim full credit for this idea.  I think  
Christian Huitema posted first.  The proposal is just for  
automatically delegating the authoritative name service for reverse  
DNS to ULA-C address space.

(p.s. I also like the idea of defining an anycast identifier for DNS  
resolving proxy servers in the locally preferred horizon.  I  
understand, however, that *that* idea is more controversial-- though  
I don't understand why it should be.  At the risk of derailing the  
topic, I'd like to mention that I know of at least one consumer  
Internet gateway product that advertises its DNS proxy service with  
IPv6 multicast DNS with a SRV records for _domain._udp.local and  
_domain._tcp.local pointing to the AAAA records for the gateway.   
This was done because there was no anycast identifier for nodes on  
unmanaged networks to find their preferred DNS proxy.)


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 13:57:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3yFT-0000De-Fi; Thu, 28 Jun 2007 13:57:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3yFS-00008s-0r
	for ipv6@ietf.org; Thu, 28 Jun 2007 13:57:42 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3yEf-0008Si-Tq
	for ipv6@ietf.org; Thu, 28 Jun 2007 13:57:42 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id 9C269A7BF8C
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:56:53 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 8838E10071
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:56:53 -0700 (PDT)
X-AuditID: 11807124-a14dfbb0000007e2-ac-4683f66525eb
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 74B641006A
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 10:56:53 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 28 Jun 2007 10:56:51 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 28, 2007, at 09:39, Christian Huitema wrote:

> I would support Paul proposal, but with one small change. Paul  
> proposes
> a delegation hierarchy in the ULA-C space:
>
>>> should be replaced with this one:
>>>
>>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>>>       +--------+-+----------+---------+---------+----------+
>>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>>>       +--------+-+----------+---------+---------+----------+
>
> That is fine, but I would rather call the delegation field by a
> different name than "RIR Num". Call in it RIR assumes that the numbers
> can only be allocated by the current set of regional registries. I  
> don't
> see any technical reason to carve this policy in a standard. I would
> much prefer a neutral designation, e.g. "Registry Number".

Actually, I think for DNS operation purposes, it makes more sense to  
reserve the RIR Num field for the existing regional registries.   
Registries that aren't RIRs can be assigned by IANA directly from the  
RIR=0 space.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 14:08:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3yPn-0005tB-1S; Thu, 28 Jun 2007 14:08:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3yPl-0005t5-MP
	for ipv6@ietf.org; Thu, 28 Jun 2007 14:08:21 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3yPl-0003oz-E2
	for ipv6@ietf.org; Thu, 28 Jun 2007 14:08:21 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5SI7l4F021442
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 28 Jun 2007 11:07:47 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5SI7lEd022171; Thu, 28 Jun 2007 13:07:47 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5SI7dxb021800; Thu, 28 Jun 2007 13:07:46 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 11:07:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jun 2007 11:07:19 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8DC@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace5rfaQSEdxifjjRK+m78AGqB12NAAAG8Kw
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com><70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "james woodyatt" <jhw@apple.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Jun 2007 18:07:45.0115 (UTC)
	FILETIME=[3A41BAB0:01C7B9AF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

=20

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Thursday, June 28, 2007 10:57 AM
> To: IETF IPv6 Mailing List
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
>=20
> On Jun 28, 2007, at 09:39, Christian Huitema wrote:
>=20
> > I would support Paul proposal, but with one small change. Paul =20
> > proposes
> > a delegation hierarchy in the ULA-C space:
> >
> >>> should be replaced with this one:
> >>>
> >>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> >>>       +--------+-+----------+---------+---------+----------+
> >>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> >>>       +--------+-+----------+---------+---------+----------+
> >
> > That is fine, but I would rather call the delegation field by a
> > different name than "RIR Num". Call in it RIR assumes that=20
> the numbers
> > can only be allocated by the current set of regional registries. I =20
> > don't
> > see any technical reason to carve this policy in a standard. I would
> > much prefer a neutral designation, e.g. "Registry Number".
>=20
> Actually, I think for DNS operation purposes, it makes more sense to =20
> reserve the RIR Num field for the existing regional registries.  =20
> Registries that aren't RIRs can be assigned by IANA directly=20
> from the =20
> RIR=3D0 space.

I still agree with Christian that there is no technical
reason to build policy into the standard. Also, IMHO,
this is discussion is coming close to diverging from
the technical realm and entering into "Big Business".

Fred
fred.l.templin@boeing.com=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 14:41:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3yvF-0005OA-Km; Thu, 28 Jun 2007 14:40:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3yvE-0005NG-6M
	for ipv6@ietf.org; Thu, 28 Jun 2007 14:40:52 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3yuR-0003X6-OF
	for ipv6@ietf.org; Thu, 28 Jun 2007 14:40:52 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id C5F0F140C145;
	Thu, 28 Jun 2007 20:40:00 +0200 (CEST)
Message-ID: <4684007F.1080700@spaghetti.zurich.ibm.com>
Date: Thu, 28 Jun 2007 19:39:59 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>, james woodyatt <jhw@apple.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>	<46838C69.3050601@spaghetti.zurich.ibm.com>
	<15110.1183042852@sa.vix.com>
In-Reply-To: <15110.1183042852@sa.vix.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: dfc64cf6e4c6efdbf6b8f4c995df04df
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0651849227=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0651849227==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig93239BAC3CB96CC49505BE68"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig93239BAC3CB96CC49505BE68
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

[Two for the price of one response, response to James far below]

Paul Vixie wrote:
> Jeroen Massar <jeroen@unfix.org>:
>> Paul Vixie <vixie@isc.org>:
>>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>>>       +--------+-+----------+---------+---------+----------+
>>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>>>       +--------+-+----------+---------+---------+----------+
>> Looks okayish but does bring back the idea of sTLA's a bit. But there =
is
>> another thing that this causes: it sort of allows aggregation.
>=20
> i'd say deliberately not.  if LIR's receive /48's then when they hand o=
ut
> address space to end sites it'll be in groups of 5 and 10 /64's.

This is not according to current RIR policies or according to current
IETF numbering plans. It also completely ignores the EUI-64 paradigm.
When the bits are assigned to an operator they can already choose to do
whatever they want with it.

A site currently gets a /48. If that has to change then support
draft-narten-iana-rir-ipv6-considerations to change that (I do btw as
endsite will never ever ever use a /48 under normal circumstances, and a
/56 will be enough for an expected 99% of them).

>> How is this any different at all from what I proposed in another
>> message: One setups an organization called "Local IP Addresses Org" an=
d
>> sets up an LIR, requests a /32, one one has 65k /48's to provide to
>> endusers.
>=20
> you are so prolific here that your own words got lost in your own torre=
nt?

I can draw it out if you want (you know how this works, but here goes):

+------+       +-----+       +-----+       +---------+
| IANA | ----> | RIR | ----> | LIR | ----> | Endsite |
+------+       +-----+       +-----+       +---------+

This is how current address assignments are done:
* IANA has it all
* RIR gets a chunk allocated from IANA
* LIR gets a chunk allocated from RIR
* Endsites get an assignment (not an allocation) from their LIR.

To note, you have "LIR" in your address diagram, and thus similar with
current policies, the endsite gets a block from the LIR, not from the
RIR, as such there is _no_ direct assignment from RIR to Endsite, and
that is (from what I understand) what people 'needing' ULA-C kind of
addresses want as they have a fear of the LIR going belly up and them
loosing their assignment.

What I proposed, lets rewrite it again: Several Endsites together set up
a single LIR, they request a /32, take /48's out of this and use this
for 'private space'. Presto. In current address space and not requiring
any changes updates or new weird rules. Also covers forward/reverse etc.

I have to note that "LIR" is a bit different term in RIPE and ARIN land,
thus it might be that that is the confusing part, in APNIC and some
other regions there are also NIR's in the chain. Making the last part
(LIR + User Num) into "User Num" would resolve this.

>> Members have a share in the org, and each and every single one
>> of them can already make sure that the LIR fees are paid (there are no=

>> equipment or transit etc fees) and presto. You have EXACTLY what you
>> have above, but with the added benefit that it is globally unique
>> address space with full RIR support.
>=20
> except that payments and shares are out of scope, you might be right.

Isn't the MAIN reason that people want ULA-C that they want it "CHEAP"!?
How is it then suddenly out of scope?

Also, clearly by defining ULA-C this shows that there is a price on
address space, I hope that at least the IETF is not going there.

>> Another problem with the above is that it doesn't allow for direct
>> end-user assignments. Folks still have to go through a LIR. This thus
>> doesn't provide these people with a "direct assignment" and they are
>> still bound to the LIR.
>=20
> then you didn't read my text, because it says the opposite of that asse=
rtion.

See my IANA->RIR->LIR->Endsite Diagram, and then check the "RIR" and
"LIR" portion in your address-diagram. Because you include LIR there can
not be a direct endsite allocation. If you would change that, as I did
in my proposed diagram to a "Prefix|L|Res|RIR|SiteID|UserBits" then you
can have a direct assignment from RIR->Endsite. (Changed "Subnet|Iface"
to "UserBits" to show that those bits really are determined by the
network operator and nobody else.

[..]
> i don't use /64's for my links.

And nobody forces you or anybody else to do so. All the other IETF
documents do include them though and if this defines address space it
should include them also IMHO. Though, I can certainly live when it is
just defined as "user defined space".

> EUI64 is going to die, and die hard.

I did not see a draft about it yet. But I do understand your arguments
for it. Still, as mentioned, the address space belongs to the operator,
let them enjoy using it. The trick of course is that devices actually do
support routing on the full 128 bits, but that is afaik still the case
with current hardware and also implicit in the IPv6 RFCs.

> let's not overspecify the mantissa.  i said "80 bits for User Num" and =
i meant that.
> (if someone wants to use /64's for their links, they can do that under =
this
> proposal, but we can't reasonably require it, and the recommendations f=
or it
> are already present in plenty of other RFCs.)

I can agree with the above.

>> Same scheme of allocation, but takes out the LIR portion and thus allo=
ws
>> RIR's to delegate this directly to endusers.
>=20
> read my text.  direct allocations are already possible.

No they are not, as a LIR is not an endsite. As such an endsite always
has to go to a LIR. That is also the whole point of PI.

Taking the LIR part out of the address diagram would resolve that part
of my comment.

>>> third, replace section 7.0 with the following:
>> Don't agree at all. (btw it is fc00::/7 not fc::/7 :)
>=20
> i've seen plenty of people say fc00::/7 and i just don't get it.  you m=
ight
> as well say fc00:0000:0000:0000:0000:0000:0000:0000/7.

Well it is simple hex math: 0xfc00 !=3D 0x00fc

Unless you are mixing up Big Endian and Little Endian comparisons.
The /7 would always mask out the last 121 bits as such fc::/7 =3D=3D ::/7=

and thus is wrong.

According to you is "fc::1" =3D=3D "fc00:0000:0000:0000:0000:0000:0000:00=
01"
or is it "00fc:0000:0000:0000:0000:0000:0000:0001" ?

See the ambiguity? Also when you have the first (fc00::1) and take the
/7 it will become fc00::/7, while the latter would be come ::/7.

> when i wrote the
> reference implementation of inet_ntop(), i only emitted the part of the=

> mantissa that was actually covered by the cidrlen.  this isn't scientif=
ic
> notation where you want to show the degree of accuracy of your measurem=
ents.

Well maybe the reference implementation is wrong? :)
But either you are wrong, or I am wrong (which is not unlikely ;), and
in either case I guess we end up fixing up a lot of software that is
already deployed and actively using it.

The actual function that will break with the above is inet_pton() which
converts from human readable to computer bits.

As you made me doubt about it, I just had to test it out. I couldn't
find a single box though (tried Linux,FreeBSD,WinXP,OpenBSD,NetBSD,AIX)
which did it the way you describe. See the test program way below so
that you can also test it out.

>> The moment you introduce support for IP6.ARPA (not IN-ADDR.ARPA) and
>> require delegations to be possible there really is no difference betwe=
en
>> PI and this kind of address space (except the prefix from which they a=
re
>> allocated, they can be filtered on that but still).
>=20
> fred made a compelling case for why ad-hoc ULA-C routing precluded the =
kind
> of resolver config overrides that we're supposed to use for RFC 1918.  =
any
> ULA-C user who doesn't want their PTR's in the global DNS should not pu=
t any
> there, but it's not our place here and now to tell them that they just =
can't.

That is the wrong answer for this question. The question is not why they
can't, the question is why they want it. And moreover: why is PI not
good enough for this purpose?

>> If one *really* requires that there will be reverse that is 'automatic=
ally
>> setup' (ignoring that you still have to do it for the forward) then de=
fine
>> in the draft the method that James Woodyatt proposed of using synthesi=
zed
>> reverse records for 0.0.c.f.ip6.arpa.  And then simply declaring that =
the
>> highest subnet (::ffff:<64bits>) contains at ::53 a DNS server serving=

>> reverse ip6.arpa for that zone.
>=20
> this is attractive, but it's an architectural change that we'd have to =
review
> for other connectivity realms, like the DFZ, and i don't want to argue =
it as
> part of settling the ULA-C question.  if you like this idea, propose it=
 and
> let's get into its merits and implications.

As mentioned, I don't like the idea as it solves a problem which should
be solved by other means. It also still requires that one configures
forward resolvers anyway. See below for James mail which has a much
better way to resolve this whole "reverse" problem of the ULA portion.

Anyway my ignored question again:

 Why would the global DNS have to handle *LOCAL* DNS delegations.

(Which never should occur/be used globally. Which most likely can not be
queried globally and which also has no value at all globally. Not even
thinking about security-minded folks who do not want to expose their
internal DNS names to the global world, that is why they want it
locally. Indeed one can opt to NOT use it, but then we just have lame
delegations again causing queries there to hit the DNS servers (most
likely the RIR ones).

If ULA-C is going to exist it should, just like ULA (RFC4193) should be,
included in the AS112 set of zones.


james woodyatt wrote:
> (p.s. I also like the idea of defining an anycast identifier for DNS
> resolving proxy servers in the locally preferred horizon.I understand,
> however, that *that* idea is more controversial-- though I don't
> understand why it should be.

dnsop group in Paris told me that it was something with breaking 3 holy
wars that have been discussed to death over the years.

=46rom my POV there is no difference between a well known anycast DNS
server or an ISP telling clients that their DNS server is x.y.z.w.
Anycast is just a nice tool to make them failover easily and to provide
best service possible.

>  At the risk of derailing the topic, I'd
> like to mention that I know of at least one consumer Internet gateway
> product that advertises its DNS proxy service with IPv6 multicast DNS
> with a SRV records for _domain._udp.local and _domain._tcp.local
> pointing to the AAAA records for the gateway.  This was done because
> there was no anycast identifier for nodes on unmanaged networks to
> find their preferred DNS proxy.)

The problem with that still is that you only have 1 DNS server and that
doesn't say if it is the forward or the reverse. If one defines
<prefix>::53 to be DNS, it can only handle reverse zones, not forward as
when I ask for "example.com" to my local DNS server how is it to know
that it should ask <otherprefix>::1 for this?

Although as the above is mDNS, it might be that you can get back a
response from another server which does know how that zone works?

Nevertheless, for the "Auto-joining MANET case", the protocol that
setups the routing can also set up the DNS merger. This has to happen
anyway when the root DNS servers are in far-far-away-never-reach-land.


Greets,
 Jeroen


--
$ cc -o bla bla.c
8<=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#include <stdio.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <arpa/inet.h>

void convert(const char *prefix, unsigned int length)
{
        struct in6_addr a6;
        char            buf[1024];
        unsigned int    i =3D (128/8)-1, l =3D 128 - length;

	if (length>128)
	{
		printf("Prefixlength for %s too large %u>128\n",
			prefix, length);
		return;
	}

        printf("%s/%u\n", prefix, length);

        /* Show us the number */
        inet_pton(AF_INET6, prefix, &a6);

        /* Show us the number without applying the prefixlength */
        inet_ntop(AF_INET6, &a6, buf, sizeof(buf));

        printf("\tntop: %s\n", buf);

        /* Zero out the last bits, thus applying the prefixlength */
        while (l > 8)
        {
                a6.s6_addr[i] =3D 0;
                i--;
                l-=3D8;
        }

        if (l > 0)
        {
                a6.s6_addr[i] &=3D ((0xff << l) & 0xff);
        }

        inet_ntop(AF_INET6, &a6, buf, sizeof(buf));
        printf("\tzero: %s/%u\n", buf, length);
}

int main(void)
{
        convert("fc::1",        128);
        convert("fc::2",          0);
        convert("fc::3",          7);
        convert("fc::4",          8);

        convert("fc00::11",     128);
        convert("fc00::12",       0);
        convert("fc00::13",       7);
        convert("fc00::14",       8);

        convert("00fc::21",     128);
        convert("00fc::22",       0);
        convert("00fc::23",       7);
        convert("00fc::24",       8);

        convert("ffff::31",     128);
        convert("ffff::32",       0);
        convert("ffff::33",       7);
        convert("ffff::34",       8);
        convert("ffff::35",       4);
}
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D>8

fc::1/128
        ntop: fc::1
        zero: fc::1/128
fc::2/0
        ntop: fc::2
        zero: ::/0
fc::3/7
        ntop: fc::3
        zero: ::/7
fc::4/8
        ntop: fc::4
        zero: ::/8
fc00::11/128
        ntop: fc00::11
        zero: fc00::11/128
fc00::12/0
        ntop: fc00::12
        zero: ::/0
fc00::13/7
        ntop: fc00::13
        zero: fc00::/7
fc00::14/8
        ntop: fc00::14
        zero: fc00::/8
00fc::21/128
        ntop: fc::21
        zero: fc::21/128
00fc::22/0
        ntop: fc::22
        zero: ::/0
00fc::23/7
        ntop: fc::23
        zero: ::/7
00fc::24/8
        ntop: fc::24
        zero: ::/8
ffff::31/128
        ntop: ffff::31
        zero: ffff::31/128
ffff::32/0
        ntop: ffff::32
        zero: ::/0
ffff::33/7
        ntop: ffff::33
        zero: fe00::/7
ffff::34/8
        ntop: ffff::34
        zero: ff00::/8
ffff::34/4
        ntop: ffff::34
        zero: f000::/4



--------------enig93239BAC3CB96CC49505BE68
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaEAH8uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I9yZAKCDFCgSZPIvUnetDMkdYNlgfFfb
/QCeJ1lpEnxzmKpnRKnb0mmSYkAN49g=
=1j6G
-----END PGP SIGNATURE-----

--------------enig93239BAC3CB96CC49505BE68--


--===============0651849227==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0651849227==--




From ipv6-bounces@ietf.org Thu Jun 28 15:51:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I401t-0004MA-Gf; Thu, 28 Jun 2007 15:51:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I401p-0004H2-OZ; Thu, 28 Jun 2007 15:51:45 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4013-0004u0-DN; Thu, 28 Jun 2007 15:51:45 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id D1E5A329C0;
	Thu, 28 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I400A-0005QB-NF; Thu, 28 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I400A-0005QB-NF@stiedprstage1.ietf.org>
Date: Thu, 28 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: ipv6@ietf.org
Subject: I-D ACTION:draft-ietf-ipv6-deprecate-rh0-01.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the IP Version 6 Working Group Working Group of the IETF.

	Title		: Deprecation of Type 0 Routing Headers in IPv6
	Author(s)	: J. Abley, et al.
	Filename	: draft-ietf-ipv6-deprecate-rh0-01.txt
	Pages		: 9
	Date		: 2007-6-28
	
The functionality provided by IPv6's Type 0 Routing Header can be
   exploited in order to achieve traffic amplification over a remote
   path for the purposes of generating denial-of-service traffic.  This
   document updates the IPv6 specification to deprecate the use of IPv6
   Type 0 Routing Headers, in light of this security concern.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-deprecate-rh0-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-ipv6-deprecate-rh0-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-ipv6-deprecate-rh0-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: <2007-6-28135357.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-ipv6-deprecate-rh0-01.txt

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

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--NextPart--




From ipv6-bounces@ietf.org Thu Jun 28 16:06:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40Fl-0000Xl-Ay; Thu, 28 Jun 2007 16:06:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40Fk-0000Wg-A5
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:06:08 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I40Eu-0008Tc-R6
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:06:08 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 462541143A
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 20:05:16 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
In-Reply-To: Your message of "Thu, 28 Jun 2007 10:56:51 MST."
	<C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 20:05:16 +0000
Message-ID: <57667.1183061116@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 28, 2007, at 09:39, Christian Huitema wrote:
> 
> I would support Paul proposal, but with one small change.  Paul proposes a
> delegation hierarchy in the ULA-C space:
>
> >>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> >>>       +--------+-+----------+---------+---------+----------+
> >>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> >>>       +--------+-+----------+---------+---------+----------+
> >
> > That is fine, but I would rather call the delegation field by a different
> > name than "RIR Num".  Call in it RIR assumes that the numbers can only be
> > allocated by the current set of regional registries.

where in my diffs do i restrict RIRs to the current set of RIRs?  it's expected
that there may be more RIRs in the future.  it's also very likely that /32's
will be handed out in blocks of five or ten to RIRs who request this kind of
space from IANA, similar to the way AS numbers are done.

> > I don't see any technical reason to carve this policy in a standard. I
> > would much prefer a neutral designation, e.g. "Registry Number".

i deliberately did not use the word "ID" since i expect each RIR to request
more than one of these /32's.  i'd avoid "Registry Number" for similar reasons.

james woodyatt <jhw@apple.com> wrote:
> 
> Actually, I think for DNS operation purposes, it makes more sense to reserve
> the RIR Num field for the existing regional registries.  Registries that
> aren't RIRs can be assigned by IANA directly from the RIR=0 space.

the text i submitted, which more than one person here has now demonstrated
that they did not read, explicitly reserves RIR Num 0 for direct IANA
allocations.  (not that there's any IANA policy allowing such allocations,
but if there ever is one, this is the bit pattern that would represent it.)

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:08:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40Hp-0001Jc-Ft; Thu, 28 Jun 2007 16:08:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40Hn-0001J3-Ln
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:08:15 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I40HB-0001DN-OT
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:08:15 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5F93311431
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 20:07:37 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
In-Reply-To: Your message of "Thu, 28 Jun 2007 11:07:19 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8DC@XCH-NW-7V2.nw.nos.boeing.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com><70C6EFCDFC8AAD418EF7063CD132D06404FD6570@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<C524A388-4B05-4225-8BF8-EBFF843DC05E@apple.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8DC@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 28 Jun 2007 20:07:37 +0000
Message-ID: <57727.1183061257@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

fred.l.templin@boeing.com wrote:

> I still agree with Christian that there is no technical reason to build
> policy into the standard. Also, IMHO, this is discussion is coming close to
> diverging from the technical realm and entering into "Big Business".

while it's probably more correct, in terms of organizational layering, for IETF
to specify only the top 8 bits of these addresses and say "let the ASO decide
how to carve it up for the RIRs", i think we can do better, and safely too.  we
ought to be able to paint enough of a picture that even end users can see their
place in the solution just from this RFC alone.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:17:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40Qc-00034U-SY; Thu, 28 Jun 2007 16:17:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40Qc-00034J-25
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:17:22 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I40Qb-00075U-SO
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:17:21 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85240503 for ipv6@ietf.org;
	Thu, 28 Jun 2007 16:16:49 -0400
Message-ID: <4684172B.3070907@internap.com>
Date: Thu, 28 Jun 2007 13:16:43 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: ipv6@ietf.org
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>	<23417.1183046917@sa.vix.com>	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D8@XCH-NW-7V2.nw.nos.boeing.com>
	<28425.1183048565@sa.vix.com>
In-Reply-To: <28425.1183048565@sa.vix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Paul Vixie wrote:
>>>> 2) can the ULA-C's be obtained at a nominal cost?
>>>>         
>
>   
>>> yes to all four.
>>>       
>
>   
>> Maybe I should have qualified 2) by asking how nominal is "nominal"?
>>     
>
> ietf does not control the costs of this kind of operational activity.  all
> that an rfc can do is ask that the costs be nominal and direct iana to only
> give address space out to rir's who have adopted policies consistent with
> the specification.  presumably iana will look to the rir's, which have strong
> and open bottom-up governance models, to determine the meaning of "nominal".

To offer a prediction, I would suspect that, at least for ARIN, 
registrants receiving only a single block of this type of address space 
would fall into the bin that gets charged $100/year today.  To me, that 
is a reasonable price to pay for maintaining WHOIS and DNS registration 
information.  Of course, RIRs could always choose to use a different 
cost structure for such assignments.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:20:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40Tv-0006jv-Ep; Thu, 28 Jun 2007 16:20:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40Tu-0006jc-H7
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:20:46 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I40Tu-0007Ty-2p
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:20:46 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5SKKR9J019930 for <ipv6@ietf.org>; Thu, 28 Jun 2007 23:20:27 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 23:20:26 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 23:20:26 +0300
Received: from [172.19.74.192] (dadhcp-172019074192.americas.nokia.com
	[172.19.74.192])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5SKKOlG029758 for <ipv6@ietf.org>; Thu, 28 Jun 2007 23:20:25 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
Content-Transfer-Encoding: 7bit
From: ext Bob Hinden <bob.hinden@nokia.com>
Date: Thu, 28 Jun 2007 13:20:22 -0700
To: IPv6 WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 28 Jun 2007 20:20:26.0738 (UTC)
	FILETIME=[C3C0FD20:01C7B9C1]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This starts a two week IPv6 working group last call on advancing

	Title		: Deprecation of Type 0 Routing Headers in IPv6
	Author(s)	: J. Abley, et al.
	Filename	: draft-ietf-ipv6-deprecate-rh0-01.txt
	Pages		: 9
	Date		: 2007-6-28
	
to Proposed Standard.  Please send substantive comments to the IPv6  
mailing list. Editorial comments can be sent to the authors.

This last call will end on July 12, 2007.

Regards,
Bob Hinden & Brian Haberman
IPv6 WG chairs


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:32:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40f1-0005tT-Fl; Thu, 28 Jun 2007 16:32:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40f0-0005sD-Fp; Thu, 28 Jun 2007 16:32:14 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I40eA-0007Dd-4Q; Thu, 28 Jun 2007 16:32:14 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5SKVHPO007809; Thu, 28 Jun 2007 23:31:18 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 23:31:17 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 23:31:16 +0300
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 23:31:16 +0300
Received: from [172.19.74.192] (dadhcp-172019074192.americas.nokia.com
	[172.19.74.192])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l5SKVDRB005022; Thu, 28 Jun 2007 23:31:14 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <057F0B45-CA24-4FDB-8186-4499F4DDCFA1@nokia.com>
Content-Transfer-Encoding: 7bit
From: ext Bob Hinden <bob.hinden@nokia.com>
Date: Thu, 28 Jun 2007 13:31:12 -0700
To: Jari Arkko <jari.arkko@piuha.net>, Mark Townsley <townsley@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 28 Jun 2007 20:31:16.0221 (UTC)
	FILETIME=[46E03AD0:01C7B9C3]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: IESG Secretary <iesg-secretary@ietf.org>,
	Brian Haberman <brian@innovationslab.net>,
	IPv6 Mailing List <ipv6@ietf.org>
Subject: Request to Advance: <draft-ietf-ipv6-ra-flags-option-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jari & Mark,

On behalf of the IPv6 WG, the chairs request the advancement of

   Title : IPv6 Router Advertisement Flags Option
   Author(s) : B. Haberman, R. Hinden
   Filename : draft-ietf-ipv6-ra-flags-option-01.txt
   Pages : 8
   Date : 2007-6-22

as an Proposed Standard.  This document reflects the consensus of the  
IPv6 WG.  The working group last call completed on 20 June 2007.   
This version of the draft addresses the issues raised during the last  
call.

Regards,
Bob Hinden
IPv6 working group co-chair


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:41:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40oJ-0007ao-Fa; Thu, 28 Jun 2007 16:41:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40oF-0007ad-UG
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:41:47 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I40nU-0001Bt-K8
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:41:47 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5SKewH7042030
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 22:40:58 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5SKevi6013405; Thu, 28 Jun 2007 22:40:57 +0200
Date: Thu, 28 Jun 2007 22:40:57 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Scott Leibrand <sleibrand@internap.com>
In-Reply-To: <4684172B.3070907@internap.com>
Message-ID: <Pine.LNX.4.64.0706282239390.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<23417.1183046917@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D8@XCH-NW-7V2.nw.nos.boeing.com>
	<28425.1183048565@sa.vix.com> <4684172B.3070907@internap.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 28 Jun 2007, Scott Leibrand wrote:
> Paul Vixie wrote:
>>>>> 2) can the ULA-C's be obtained at a nominal cost?
>> 
>>>> yes to all four.
>> 
>>> Maybe I should have qualified 2) by asking how nominal is "nominal"?
>> 
>> ietf does not control the costs of this kind of operational activity.  all
>> that an rfc can do is ask that the costs be nominal and direct iana to only
>> give address space out to rir's who have adopted policies consistent with
>> the specification.  presumably iana will look to the rir's, which have 
>> strong
>> and open bottom-up governance models, to determine the meaning of 
>> "nominal".
>
> To offer a prediction, I would suspect that, at least for ARIN, registrants 
> receiving only a single block of this type of address space would fall into 
> the bin that gets charged $100/year today.  To me, that is a reasonable price 
> to pay for maintaining WHOIS and DNS registration information.  Of course, 
> RIRs could always choose to use a different cost structure for such 
> assignments.

Think it is completly out of this scope to define anything at all related 
to the cost of this, but I would rather consider this a bit like the 
domain charging system when thinking in term of what it should cost...


-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:46:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I40sZ-0005gl-Pe; Thu, 28 Jun 2007 16:46:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I40sY-0005ec-2d
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:46:14 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I40sX-0000jo-Jp
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:46:13 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5SKjOCu084411
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 22:45:24 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5SKjNRp013879; Thu, 28 Jun 2007 22:45:23 +0200
Date: Thu, 28 Jun 2007 22:45:23 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Paul Vixie <paul@vix.com>
In-Reply-To: <14556.1183042057@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0706282242200.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com> <4683712F.1010602@gmail.com> 
	<14556.1183042057@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 28 Jun 2007, Paul Vixie wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com>:
>>
>> I wouldn't, at this time.  We need to see where the RAM/RRG discussions
>> lead.  If they lead to a clear need for registered globally unique
>> identifiers in IPv6 address format, something like this might be right
>> (unless we also need a cryptographic property).
>
> where are those discussions being held, and can you post a summary, and why
> are we wasting our keystrokes discussing this if there's a preclusive topic
> being discussed somewhere entirely else?

ram@iab.org and I gave up following that discussion months ago. Way too 
much chitchat one way or the other as I see it and no real consensus 
forming in one way or another.

Don't think we should wait for RAM/RRG to agree, let us agree on our 
understanding and at a later stage when they have come up with a "final" 
solution we can compare our understanding with their and see if there 
is a need for adjustment.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 16:56:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4125-0002pw-NO; Thu, 28 Jun 2007 16:56:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4124-0002e6-AX
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:56:04 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I411D-0004nL-FV
	for ipv6@ietf.org; Thu, 28 Jun 2007 16:56:04 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l5SKwdgV010368;
	Thu, 28 Jun 2007 15:58:40 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 15:55:09 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 15:55:09 -0500
Message-ID: <46841FDC.4040604@ericsson.com>
Date: Thu, 28 Jun 2007 16:53:48 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: =?windows-1252?Q?JINMEI_Tatuya_/_=3F=3F=3F=3F?=
	<jinmei@isl.rdc.toshiba.co.jp>
References: <46827D36.7050307@ericsson.com>
	<m1k5topksy.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1k5topksy.wl%jinmei@isl.rdc.toshiba.co.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 28 Jun 2007 20:55:09.0217 (UTC)
	FILETIME=[9D021110:01C7B9C6]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipv6@ietf.org
Subject: Re: Privacy Addresses AUTH48 Changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jinmei,
   Thanks for pointing that out. I will be adding the reference to 
RFC2526 under Informational. Yes. The dangling reference was to RFC2526 
as well. I have already fixed it since it was just a editorial nit.

Cheers
Suresh

JINMEI Tatuya / ???? wrote:
> At Wed, 27 Jun 2007 11:07:34 -0400,
> Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> 
>>    I would like to make the following editorial change to the upcoming 
>> Privacy Addresses RFC.
>>
>> I would like to add the following sentence to section 3.2.1 step 4
>>
>> This list currently includes the reserved anycast interface identifiers 
>> listed in [RFC2526]. This list may be expanded in the future to include 
>> further interface identifiers.
>>
>> after this sentence
>>
>> Compare the generated identifier against a list of
>> reserved interface identifiers and to those already
>> assigned to an address on the local device.
>>
>> Please let me know by June 29 2007 if you have any objections.
> 
> I don't have an objection to the idea of including RFC2526 per se, but
> I have a concern:
> 
> This reference (RFC2526) was not included in
> draft-ietf-ipv6-privacy-addrs-v2-05 and will be newly added to the
> final RFC version-05, right?  If so, which category are you intending
> to specify for this reference, normative vs informative?  It cannot be
> normative since RFC2526 is a proposed standard while the privacy
> address RFC will become a draft standard; but I'd categorize it as
> normative in the above context because implementors must refer to
> RFC2526 to implement the privacy-addrs spec.
> 
> A possibly related comment: there is a dangling reference in Section 8
> of the 05 version of I-D:
> 
>    1.  Excluded certain interface identifiers from the range of
>        acceptable interface identifiers.  Interface IDs such as those
>        for reserved anycast addresses [RFC], etc.
> 
> I guess the "[RFC]" should actually be "[RFC2526]".  (Sorry if this
> has already been pointed out).
> 
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba Corp.
> 					jinmei@isl.rdc.toshiba.co.jp


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 17:02:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4189-0008II-65; Thu, 28 Jun 2007 17:02:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4187-0007zE-Gu
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:02:19 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4178-00079z-Lb
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:01:25 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 28 Jun 2007 16:01:16 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A0631410667070BD@mail>
In-Reply-To: <9EC676E6-9B24-411A-87EF-DAF3E2C0D902@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace5quyFftaZxoQpTPedZ+RcLtiQ3AAGxrtA
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

 I am afraid I am slow..  I still don't get the need to publicly
advertise DNS for ULA(-x) .. if your neighbor cannot route to your ULA
he doesn't need to know what it's names are..  if you do allow him to
enter your network via VPN or whatever there is either a dhcp-like
process by which he is granted an address which will also give him a
name server to use, or when he says "Hey, Can I have access to your
network" you can say "Sure, here are your credentials and my DNS server
is..."=20

Then of course because you can populate your DNS server with whatever
zones you want when your neighbor queries your name server it will tell
him what he wants to know.

Aren't your DNS servers going to provide different views for clients
coming from PI or PA than they do for clients coming from ULAx anyway?
or is your network going to be a completely glass house?   Typically
"local" clients get more access and information than non-local clients.



> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]=20
> Sent: Thursday, June 28, 2007 12:35 PM
> To: IETF IPv6 Mailing List
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
>=20
> On Jun 28, 2007, at 03:24, Jeroen Massar wrote:
> >
> > If one *really* requires that there will be reverse that is=20
> > 'automatically setup' (ignoring that you still have to do=20
> it for the=20
> > forward) then define in the draft the method that James Woodyatt=20
> > proposed of using synthesized reverse records for=20
> 0.0.c.f.ip6.arpa. =20
> > And then simply declaring that the highest subnet (::ffff:<64bits>)=20
> > contains at ::53 a DNS server serving reverse ip6.arpa for=20
> that zone.
>=20
> I don't think I can claim full credit for this idea.  I think=20
> Christian Huitema posted first.  The proposal is just for=20
> automatically delegating the authoritative name service for=20
> reverse DNS to ULA-C address space.
>=20
> (p.s. I also like the idea of defining an anycast identifier=20
> for DNS resolving proxy servers in the locally preferred=20
> horizon.  I understand, however, that *that* idea is more=20
> controversial-- though I don't understand why it should be. =20
> At the risk of derailing the topic, I'd like to mention that=20
> I know of at least one consumer Internet gateway product that=20
> advertises its DNS proxy service with
> IPv6 multicast DNS with a SRV records for _domain._udp.local and =20
> _domain._tcp.local pointing to the AAAA records for the gateway.  =20
> This was done because there was no anycast identifier for=20
> nodes on unmanaged networks to find their preferred DNS proxy.)
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 17:13:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I41JI-0005DY-IG; Thu, 28 Jun 2007 17:13:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I41JH-0005A1-K6
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:13:51 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I41Id-0002tX-CR
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:13:51 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5SLD8x9089819
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 23:13:09 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5SLD7TO015701; Thu, 28 Jun 2007 23:13:07 +0200
Date: Thu, 28 Jun 2007 23:13:07 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <46838C69.3050601@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0706282253070.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46838C69.3050601@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 28 Jun 2007, Jeroen Massar wrote:
> Paul Vixie wrote:
> [..]
>> first, in 3.1, this table:
> [..]
>> should be replaced with this one:
>>
>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>>       +--------+-+----------+---------+---------+----------+
>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>>       +--------+-+----------+---------+---------+----------+
>
> Looks okayish but does bring back the idea of sTLA's a bit. But there is
> another thing that this causes: it sort of allows aggregation.
>
> How is this any different at all from what I proposed in another
> message: One setups an organization called "Local IP Addresses Org" and
> sets up an LIR, requests a /32, one one has 65k /48's to provide to
> endusers. Members have a share in the org, and each and every single one
> of them can already make sure that the LIR fees are paid (there are no
> equipment or transit etc fees) and presto. You have EXACTLY what you
> have above, but with the added benefit that it is globally unique
> address space with full RIR support. The LIR can shoot ip6.arpa
> delegations per /48 if they want directly into the RIR's nameservers,
> thus that is also covered. Connectivity one could also provide just like
> a normal LIR if really wanted.
>
> Another problem with the above is that it doesn't allow for direct
> end-user assignments. Folks still have to go through a LIR. This thus
> doesn't provide these people with a "direct assignment" and they are
> still bound to the LIR.

too complicated and see bellow why.


<snip>
> As such, if you really want to have ULA-C (which I really think is
> unnecessary because of arguments I've reiterated a couple of times
> already also in other messages and the above) I would at least propose:
>
> | 7 bits |1| 8 bits |16 bits| 16 bits |  16 bits  | 64 bits   |
> +--------+-+--------+-------+---------+-----------+-----------+
> | Prefix |L|Reserved|RIR ID | Site ID | Subnet ID | Iface ID  |
> +--------+-+--------+-------+---------+-----------+-----------+
>                                      | /48 for the end-site  |
>                                      +-----------------------+
>
> Same scheme of allocation, but takes out the LIR portion and thus allows
> RIR's to delegate this directly to endusers.

no, just forget all of that. The original text from Paul have the solution 
to this very clear:

<paste>
      RIR Num             Identifiers assigned by IANA for each /16 as
                          allocated to an Regional Internet Address
 			Registry
                          (RIR).  For direct allocations by IANA, the value
                          of zero (0x0000) is reserved.

      LIR Num             Identifiers assigned by RIR for each /32 as
                          allocated to a Local Internet Address Registry (LIR).
                          For direct allocations by an RIR, the value of
 			zero  (0x0000) is reserved.
</end paste>

so we don't have to consider this at all!! All we have todo is let IANA, 
or other parties getting this task from IANA, run something automatic on 
THEIR side that give end-user direct request possibility without going 
through a RIR or LIR.

This solution suite the need at my workplace perfect.


<snip>
>> third, replace section 7.0 with the following:
>
> Don't agree at all. (btw it is fc00::/7 not fc::/7 :)
>
> The moment you introduce support for IP6.ARPA (not IN-ADDR.ARPA) and
> require delegations to be possible there really is no difference between
> PI and this kind of address space (except the prefix from which they are
> allocated, they can be filtered on that but still).
>
> The reasons against having support for reverse DNS:
> - You are introducing a *local* space into the *global* Internet.
>   As such it is required to have Internet connectivity (with all the
>   hacks that are required to be able to talk to the ip6.arpa servers
>   and the chain along it to get to those reverse DNS servers).

as someone said to me earlier... in times of complicated affairs and 
compromisses you might have to swallow a few hard pills... I dislike the 
thought of ULA-C but this latest suggestion is reasonable and not that 
bad. Even with DNS in place it is acceptable for me personaly this way of 
doing it.

It has been said very clear by many that ULA-C is _not_ considered to be 
global reachable and if we just can as strong as possible make it clear 
DURING requesting of addresses we should be fine. The point is that we 
have to show the enduser that they have agreed that they can NOT demand 
global routing of this address space at all. No complicated text, keep it 
simple.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 17:31:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I41Zz-0000YN-Dh; Thu, 28 Jun 2007 17:31:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I41Zy-0000Ry-Dy
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:31:06 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I41Zx-0004LR-TN
	for ipv6@ietf.org; Thu, 28 Jun 2007 17:31:06 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5SLUWKV054164
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 23:30:32 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5SLUW8r016742; Thu, 28 Jun 2007 23:30:32 +0200
Date: Thu, 28 Jun 2007 23:30:31 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: ipv6@ietf.org
In-Reply-To: <13846.1183003509@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: roger@jorgensen.no
Subject: agree on step one - Re: I-D
	ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi all,

if we overlook the last part about DNS for now, is this acceptable by 
people? I've read this through several times and I belive it satifsy the 
following asked by "Templin, Fred L" <Fred.L.Templin@boeing.com>

   1) can any site (large or small) get a ULA-C?
   2) can the ULA-C's be obtained at a nominal cost?
   4) can the ULA-C's be kept out of the DFZ?

i've removed part 3 on purpose since we can maybe take that discussion 
after the above agreement?

about part one - both the RIR and LIR field can be set to zero's 
for direct assignment, for other they can go through RIR.




full text bellow:

On Thu, 28 Jun 2007, Paul Vixie wrote:
> these are my comments on the following I-D:
>
>> 	Title      : Centrally Assigned Unique Local IPv6 Unicast Addresses
>> 	Author(s)  : R. Hinden, B. Haberman
>> 	Filename   : draft-ietf-ipv6-ula-central-02.txt
>> 	Pages      : 11
>> 	Date       : 2007-6-18
>>
>> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt>
>
> first, in 3.1, this table:
>
>      | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
>      +--------+-+------------+-----------+----------------------------+
>      | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
>      +--------+-+------------+-----------+----------------------------+
>
> should be replaced with this one:
>
>      | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>      +--------+-+----------+---------+---------+----------+
>      | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>      +--------+-+----------+---------+---------+----------+
>
> where "Prefix" and "L" are defined as shown in central-02, and the other
> fields are defined as follows:
>
>     Reserved            Set to 0 by all implementors of this specification,
>                         but may be set to nonzero by implementors of a later
>                         specification.
>
>     RIR Num             Identifiers assigned by IANA for each /16 as
>                         allocated to an Regional Internet Address Registry
>                         (RIR).  For direct allocations by IANA, the value
>                         of zero (0x0000) is reserved.
>
>     LIR Num             Identifiers assigned by RIR for each /32 as
>                         allocated to a Local Internet Address Registry (LIR).
>                         For direct allocations by an RIR, the value of zero
>                         (0x0000) is reserved.
>
>     User Num            Identifier assigned by an end user or network
>                         operator who implements this specification.
>
> second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 3.2.3.
>
> third, replace section 7.0 with the following:
>
> ---
>
> 7.0 IANA Considerations
>
>    IANA is hereby instructed to reserve address block FC::/7 for private
>    unique addresses, and to allocate /32 blocks to Regional Internet
>    Address Registries (RIRs) who request same after adopting policies
>    consistent with this specification.  Allocation shall be similar in
>    all ways to normal IANA address allocation to RIRs, including but not
>    limited to IN-ADDR.ARPA delegations and WHOIS records.
>
> ---
>
> Paul Vixie
> not speaking for ISC
> not speaking for ARIN
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

-- 


------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 19:26:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I43Mt-0004bz-F0; Thu, 28 Jun 2007 19:25:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I43Mr-0004bt-Te
	for ipv6@ietf.org; Thu, 28 Jun 2007 19:25:41 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I43MP-0001rG-0e
	for ipv6@ietf.org; Thu, 28 Jun 2007 19:25:41 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85252514; Thu, 28 Jun 2007 19:25:12 -0400
Message-ID: <46844352.2090601@internap.com>
Date: Thu, 28 Jun 2007 16:25:06 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>
	<Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: ipv6@ietf.org, roger@jorgensen.no
Subject: Re: agree on step one - Re:
	I-D	ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Yes, I agree that any site should be able to get a ULA-C assignment, at 
nominal cost, and that ULA netblocks should be kept out of the DFZ.

-Scott

Roger Jorgensen wrote:
> Hi all,
>
> if we overlook the last part about DNS for now, is this acceptable by 
> people? I've read this through several times and I belive it satifsy 
> the following asked by "Templin, Fred L" <Fred.L.Templin@boeing.com>
>
>   1) can any site (large or small) get a ULA-C?
>   2) can the ULA-C's be obtained at a nominal cost?
>   4) can the ULA-C's be kept out of the DFZ?
>
> i've removed part 3 on purpose since we can maybe take that discussion 
> after the above agreement?
>
> about part one - both the RIR and LIR field can be set to zero's for 
> direct assignment, for other they can go through RIR.
>
>
>
>
> full text bellow:
>
> On Thu, 28 Jun 2007, Paul Vixie wrote:
>> these are my comments on the following I-D:
>>
>>>     Title      : Centrally Assigned Unique Local IPv6 Unicast Addresses
>>>     Author(s)  : R. Hinden, B. Haberman
>>>     Filename   : draft-ietf-ipv6-ula-central-02.txt
>>>     Pages      : 11
>>>     Date       : 2007-6-18
>>>
>>> <http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt> 
>>>
>>
>> first, in 3.1, this table:
>>
>>      | 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
>>      +--------+-+------------+-----------+----------------------------+
>>      | Prefix |L| Global ID  | Subnet ID |        Interface ID        |
>>      +--------+-+------------+-----------+----------------------------+
>>
>> should be replaced with this one:
>>
>>      | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>>      +--------+-+----------+---------+---------+----------+
>>      | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>>      +--------+-+----------+---------+---------+----------+
>>
>> where "Prefix" and "L" are defined as shown in central-02, and the other
>> fields are defined as follows:
>>
>>     Reserved            Set to 0 by all implementors of this 
>> specification,
>>                         but may be set to nonzero by implementors of 
>> a later
>>                         specification.
>>
>>     RIR Num             Identifiers assigned by IANA for each /16 as
>>                         allocated to an Regional Internet Address 
>> Registry
>>                         (RIR).  For direct allocations by IANA, the 
>> value
>>                         of zero (0x0000) is reserved.
>>
>>     LIR Num             Identifiers assigned by RIR for each /32 as
>>                         allocated to a Local Internet Address 
>> Registry (LIR).
>>                         For direct allocations by an RIR, the value 
>> of zero
>>                         (0x0000) is reserved.
>>
>>     User Num            Identifier assigned by an end user or network
>>                         operator who implements this specification.
>>
>> second, delete all of section 3.2 including subsections 3.2.1, 3.2.2, 
>> 3.2.3.
>>
>> third, replace section 7.0 with the following:
>>
>> ---
>>
>> 7.0 IANA Considerations
>>
>>    IANA is hereby instructed to reserve address block FC::/7 for private
>>    unique addresses, and to allocate /32 blocks to Regional Internet
>>    Address Registries (RIRs) who request same after adopting policies
>>    consistent with this specification.  Allocation shall be similar in
>>    all ways to normal IANA address allocation to RIRs, including but not
>>    limited to IN-ADDR.ARPA delegations and WHOIS records.
>>
>> ---
>>
>> Paul Vixie
>> not speaking for ISC
>> not speaking for ARIN
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 19:55:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I43p4-0003gu-4X; Thu, 28 Jun 2007 19:54:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I43p2-0003cc-K8
	for ipv6@ietf.org; Thu, 28 Jun 2007 19:54:48 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I43od-00037S-1h
	for ipv6@ietf.org; Thu, 28 Jun 2007 19:54:48 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id 87691ABE8CB
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 16:54:22 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 72D6529C002
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 16:54:22 -0700 (PDT)
X-AuditID: 11807123-a5020bb000000a55-92-46844a2ef1bc
Received: from [17.206.50.68] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 3BAD3304011
	for <ipv6@ietf.org>; Thu, 28 Jun 2007 16:54:22 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <178DD1AD-C053-4EF8-A9C5-F2F30DC27CC1@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Thu, 28 Jun 2007 16:54:21 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Re: agree on step one - Re:
	I-D	ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Jun 28, 2007, at 14:30, Roger Jorgensen wrote:
>
> about part one - both the RIR and LIR field can be set to zero's  
> for direct assignment, for other they can go through RIR.

That's not how I read Mr. Vixie's proposed text.  If both RIR and LIR  
are zero, that implies a ULA prefix that IANA reserves for its own  
operations.  Any sites that want ULA-C prefixes without going to a  
RIR need to get one from a LIR explicitly numbered by IANA.  I don't  
think we've established any policy for how IANA is expected to assign  
LIR numbers for use when RIR=0.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 20:09:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I442v-0002ZW-AJ; Thu, 28 Jun 2007 20:09:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I442t-0002Ty-4x
	for ipv6@ietf.org; Thu, 28 Jun 2007 20:09:07 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I442i-0001Lv-Es
	for ipv6@ietf.org; Thu, 28 Jun 2007 20:09:07 -0400
Received: from [63.251.161.214] (account sleibrand@mail.internap.com HELO
	[63.251.161.214])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85254582; Thu, 28 Jun 2007 20:08:56 -0400
Message-ID: <46844D92.20605@internap.com>
Date: Thu, 28 Jun 2007 17:08:50 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>	<Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
	<178DD1AD-C053-4EF8-A9C5-F2F30DC27CC1@apple.com>
In-Reply-To: <178DD1AD-C053-4EF8-A9C5-F2F30DC27CC1@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: agree on step one -
	Re:	I-D	ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

james woodyatt wrote:
> On Jun 28, 2007, at 14:30, Roger Jorgensen wrote:
>>
>> about part one - both the RIR and LIR field can be set to zero's for 
>> direct assignment, for other they can go through RIR.
>
> That's not how I read Mr. Vixie's proposed text.  If both RIR and LIR 
> are zero, that implies a ULA prefix that IANA reserves for its own 
> operations.  Any sites that want ULA-C prefixes without going to a RIR 
> need to get one from a LIR explicitly numbered by IANA.  I don't think 
> we've established any policy for how IANA is expected to assign LIR 
> numbers for use when RIR=0.

Paul's text states, "For direct allocations by IANA, the value of zero 
(0x0000) is reserved."  To me, that's a pretty clear definition of which 
address space IANA would use for direct allocations or assignments to 
end users.

You're correct that we have not established any policy for how IANA 
would go about making such allocations or assignments.  I would suspect 
that they might elect not to do so, instead delegating that 
responsibility to the RIRs.  But if we did decide, as a matter of 
policy, that IANA should (also) make direct allocations and assignments, 
the proposed text defines space for that purpose.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 21:44:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I45WG-0002bR-7a; Thu, 28 Jun 2007 21:43:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I45WE-0002b6-FI
	for ipv6@ietf.org; Thu, 28 Jun 2007 21:43:30 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I45WD-0000aW-1P
	for ipv6@ietf.org; Thu, 28 Jun 2007 21:43:30 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5T1hLJC099891;
	Fri, 29 Jun 2007 11:43:22 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706290143.l5T1hLJC099891@drugs.dv.isc.org>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Thu, 28 Jun 2007 08:14:15 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
Date: Fri, 29 Jun 2007 11:43:21 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: ipv6@ietf.org, Paul Vixie <Paul_Vixie@isc.org>
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> My use case questions that still need to be satisfied are:
> 
>   1) can any site (large or small) get a ULA-C?
>   2) can the ULA-C's be obtained at a nominal cost?
>   3) can the ULA-C's be published in the global DNS
>      forward and reverse?
>   4) can the ULA-C's be kept out of the DFZ?
> 
> If Paul's proposal answers all of these as "yes", then
> I have no objections.
> 
> Fred
> fred.l.templin@boeing.com

	I believe 1 and 2 where always the intention.
	I believe you can't stop AAAA records for them being added.
	I believe that the reverse can be done but we need to take 
	care.
	I believe 4 can be achieved with the appropriate use of route
	filter and loose URPF over FC00/7.  Default null route for
	FC00/7 and appropritate route filters.
 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Thu Jun 28 23:34:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I47F4-0006tN-6v; Thu, 28 Jun 2007 23:33:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I47F2-0006tC-OJ
	for ipv6@ietf.org; Thu, 28 Jun 2007 23:33:52 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I47Ej-0002MZ-V8
	for ipv6@ietf.org; Thu, 28 Jun 2007 23:33:52 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l5T3XT31048006;
	Fri, 29 Jun 2007 13:33:31 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200706290333.l5T3XT31048006@drugs.dv.isc.org>
To: "Kevin Kargel" <kkargel@polartel.com>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Thu, 28 Jun 2007 16:01:16 EST."
	<70DE64CEFD6E9A4EB7FAF3A0631410667070BD@mail> 
Date: Fri, 29 Jun 2007 13:33:29 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> I am afraid I am slow..  I still don't get the need to publicly
> advertise DNS for ULA(-x) .. if your neighbor cannot route to your ULA
> he doesn't need to know what it's names are..  if you do allow him to
> enter your network via VPN or whatever there is either a dhcp-like
> process by which he is granted an address which will also give him a
> name server to use, or when he says "Hey, Can I have access to your
> network" you can say "Sure, here are your credentials and my DNS server
> is..."=20

	Well firstly these address will appear outside of IPv6 packets
	in environments where they will be automatically processed along
	with every other IPv6 address that is being processed.  The
	place that it processing the addresses may or may not be able
	to reach the ULA-C servers for the reverse lookup.

	It really should be up to the *user* of the ULA-C addresses
	to decide if they want to provide more than NXDOMAIN to
	interested parties on the Internet.  We shouldn't be
	arbitarially limiting functionality if it is technically
	possible to provide that functionality.

> Then of course because you can populate your DNS server with whatever
> zones you want when your neighbor queries your name server it will tell
> him what he wants to know.
> 
> Aren't your DNS servers going to provide different views for clients
> coming from PI or PA than they do for clients coming from ULAx anyway?
> or is your network going to be a completely glass house?   Typically
> "local" clients get more access and information than non-local clients.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 00:47:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I48OH-0002uj-Hf; Fri, 29 Jun 2007 00:47:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I48OG-0002uT-E8
	for ipv6@ietf.org; Fri, 29 Jun 2007 00:47:28 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I48NX-0006G1-Mi
	for ipv6@ietf.org; Fri, 29 Jun 2007 00:47:28 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 519A87301F;
	Fri, 29 Jun 2007 13:46:42 +0900 (JST)
Date: Fri, 29 Jun 2007 13:46:34 +0900
Message-ID: <m14pkrpdud.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
In-Reply-To: <46841FDC.4040604@ericsson.com>
References: <46827D36.7050307@ericsson.com>
	<m1k5topksy.wl%jinmei@isl.rdc.toshiba.co.jp>
	<46841FDC.4040604@ericsson.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org
Subject: Re: Privacy Addresses AUTH48 Changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Thu, 28 Jun 2007 16:53:48 -0400,
Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:

>    Thanks for pointing that out. I will be adding the reference to 
> RFC2526 under Informational. Yes.

Okay, then the problem is whether we can safely categorize the
reference to RFC2526 as informative.  I personally don't think it's
safe:

> > address RFC will become a draft standard; but I'd categorize it as
> > normative in the above context because implementors must refer to
> > RFC2526 to implement the privacy-addrs spec.

but I personally wouldn't oppose to your proposed action either (I
often feel the downref rule doesn't help much for implementors in
practice while it can easily be an unnecessary showstopper in the
standardization process).  In any event, I think we should confirm the
consensus about the categorization in this wg (and possibly with the
ADs).

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 05:36:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ctg-0005JQ-3g; Fri, 29 Jun 2007 05:36:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Cte-0005JG-TB
	for ipv6@ietf.org; Fri, 29 Jun 2007 05:36:10 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Ctc-00009L-La
	for ipv6@ietf.org; Fri, 29 Jun 2007 05:36:10 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 827FA140C856;
	Fri, 29 Jun 2007 11:36:07 +0200 (CEST)
Message-ID: <4684D286.8080900@spaghetti.zurich.ibm.com>
Date: Fri, 29 Jun 2007 10:36:06 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46838C69.3050601@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706282253070.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706282253070.29317@chandra.student.uit.no>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1171439335=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1171439335==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9F2E2C22A367F5AD8D47BC60"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9F2E2C22A367F5AD8D47BC60
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Roger Jorgensen wrote:
[..]
> too complicated and see bellow why.

How can something which already exists, and thus is not new, be "too
complicated"? Also as the text you referenced contained two different
approaches to the problem, which part is actually "too complicated" and
moreover why?

[..]
> so we don't have to consider this at all!! All we have todo is let IANA=
,
> or other parties getting this task from IANA, run something automatic o=
n
> THEIR side that give end-user direct request possibility without going
> through a RIR or LIR.

Direct assignments from IANA? They will be happy to do that. Of course,
the RIR's can be taken out of the equation completely, still don't call
the the fields "RIR Num" and "LIR Num" then as those are misnomers.

> This solution suite the need at my workplace perfect.

And how exactly does PI not suite that need?

[..]
> as someone said to me earlier... in times of complicated affairs and
> compromisses you might have to swallow a few hard pills... I dislike th=
e
> thought of ULA-C but this latest suggestion is reasonable and not that
> bad. Even with DNS in place it is acceptable for me personaly this way
> of doing it.

Thus first we try to actively fix a lot of things, and then to break
them all again? Very not useful and a lot of work down the drain.

> It has been said very clear by many that ULA-C is _not_ considered to b=
e
> global reachable

Hold on, either it is LOCAL or it is GLOBAL, "not considered to be",
means that it is expected to be quite reachable on most parts on the
Internet.

As such, is the expectancy simply that fc00::/7 will become the new
addressing scheme overtaking all the RIR stuff that is in place already?

If that is what is wanted, then just specify that fc00::/7 will be used
for "Internet Part 2" which avoids RIRs and other such mechanisms. We
then at least have clarity what is trying to be accomplished with this
part of the address space.

> and if we just can as strong as possible make it clear
> DURING requesting of addresses we should be fine. The point is that we
> have to show the enduser that they have agreed that they can NOT demand=

> global routing of this address space at all. No complicated text, keep
> it simple.

Endusers vote with their money. When a site is important enough to be
reached, they will go to an ISP that will have access to that site and
as such that space will be routed globally, the Internet will then
simply change to include the other spaces.

Greets,
 Jeroen


--------------enig9F2E2C22A367F5AD8D47BC60
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaE0oYuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2B/AJ9xkrbPgde65VeQoLufs9gNJE6j
EQCfXmn0Q+youazr9rIHttjLouuQ7+4=
=GOvH
-----END PGP SIGNATURE-----

--------------enig9F2E2C22A367F5AD8D47BC60--


--===============1171439335==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1171439335==--




From ipv6-bounces@ietf.org Fri Jun 29 06:14:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4DUr-0001Hb-Ac; Fri, 29 Jun 2007 06:14:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4DUq-0001HT-0R
	for ipv6@ietf.org; Fri, 29 Jun 2007 06:14:36 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4DUp-00062L-MB
	for ipv6@ietf.org; Fri, 29 Jun 2007 06:14:35 -0400
Received: by ug-out-1314.google.com with SMTP id u2so125148uge
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 03:13:30 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=a1n8ebv3Wp3zVFhafotUyo9Ss3Og0oI48daEC75zXC6Ta4S+HOV6CAQ4MkPvC3gEftwX5NtmZS0ck5zN76BeHND3+8kBfCDaQbrXaFs71RgHoer2DXgP8M3iO/RWvon5nPxBr0tTE834LCXxHxuiiNgPV7iKwYpF2iDnqLdZwlI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=S4UOe9NQFzn+IAxXARYu5S6YW87settEIGWpWkw1S3DHwmihXDsolwzKdSVG1TQsbLGGYAuJExFt9VrO4MRah3/nVGo8tJuCU5J91d74NT9D6C8GMDzo5lO1IasNfqu5CZ+r63hF7oJIGvhlmV/J37mdA7Rr4NkENVk8tPtZEEs=
Received: by 10.67.10.12 with SMTP id n12mr1713043ugi.1183112010282;
	Fri, 29 Jun 2007 03:13:30 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id q40sm466593ugc.2007.06.29.03.13.28
	(version=SSLv3 cipher=RC4-MD5); Fri, 29 Jun 2007 03:13:29 -0700 (PDT)
Message-ID: <4684DB4A.2060703@gmail.com>
Date: Fri, 29 Jun 2007 12:13:30 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com>	<4683712F.1010602@gmail.com>
	<14556.1183042057@sa.vix.com>
In-Reply-To: <14556.1183042057@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-06-28 16:47, Paul Vixie wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com>:
>> Scott Leibrand <sleibrand@internap.com>:
>>> I would support Paul's proposed changes below, and the resulting draft.
>> I wouldn't, at this time.  We need to see where the RAM/RRG discussions
>> lead.  If they lead to a clear need for registered globally unique
>> identifiers in IPv6 address format, something like this might be right
>> (unless we also need a cryptographic property).
> 
> where are those discussions being held, 

http://www1.ietf.org/mail-archive/web/ram/current/index.html
http://psg.com/lists/rrg/

> and can you post a summary,

Personally, no. The R&A Directorate is supposed to be
doing the overview and summary stuff:

http://www1.ietf.org/mail-archive/web/radir/current/index.html

> and why
> are we wasting our keystrokes discussing this if there's a preclusive topic
> being discussed somewhere entirely else?

I don't think it's preclusive. If that discussion does lead to an
architectural id/locator split, it will not override what we're discussing
here, IMHO. We'll still have IP addresses and they will still need to
be unambiguous. Also, that is a discussion that is finally happening
after ten years of needing to happen, so it's hardly surprising that
it hasn't converged rapidly.

> 
>> I have a strong feeling there is no consensus forming...
> 
> i disagree, i've been immersed in this for a month now, and my draft edits
> as proposed last night represent my understanding of a potential consensus,
> which unlike you i can feel forming.

I personally am not part of it then. I don't want to see any structured
allocation scheme; a robotic guarantee of uniqueness is all I want to see.
I don't want to facilitate making these things look like a binary
hierarchy, because that will cause people to believe for the next 50
years that they aggregate and are routeable. I also don't want to
accidentally create a business in selling large integers, which would
be the effect of structured registration as opposed to robotic random
numbers.

      Brian

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 07:45:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Euf-0003IO-86; Fri, 29 Jun 2007 07:45:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Eud-0003IG-Uv; Fri, 29 Jun 2007 07:45:19 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I4Eud-0002rE-M1; Fri, 29 Jun 2007 07:45:19 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id A78C71986A7;
	Fri, 29 Jun 2007 14:44:46 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4F7C2198691;
	Fri, 29 Jun 2007 14:44:46 +0300 (EEST)
Message-ID: <4684F0AE.2090702@piuha.net>
Date: Fri, 29 Jun 2007 14:44:46 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <057F0B45-CA24-4FDB-8186-4499F4DDCFA1@nokia.com>
In-Reply-To: <057F0B45-CA24-4FDB-8186-4499F4DDCFA1@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Brian Haberman <brian@innovationslab.net>,
	IESG Secretary <iesg-secretary@ietf.org>, IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Request to Advance: <draft-ietf-ipv6-ra-flags-option-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Is the a document shepherd writeup?
See:

http://www.ietf.org/IESG/content/Doc-Writeup.html

Jari

ext Bob Hinden kirjoitti:
> Jari & Mark,
>
> On behalf of the IPv6 WG, the chairs request the advancement of
>
>   Title : IPv6 Router Advertisement Flags Option
>   Author(s) : B. Haberman, R. Hinden
>   Filename : draft-ietf-ipv6-ra-flags-option-01.txt
>   Pages : 8
>   Date : 2007-6-22
>
> as an Proposed Standard.  This document reflects the consensus of the
> IPv6 WG.  The working group last call completed on 20 June 2007.  This
> version of the draft addresses the issues raised during the last call.
>
> Regards,
> Bob Hinden
> IPv6 working group co-chair
>
>
>


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 09:39:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ggr-0000Rn-Rt; Fri, 29 Jun 2007 09:39:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Ggq-0000Re-Ob
	for ipv6@ietf.org; Fri, 29 Jun 2007 09:39:12 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Gfu-0001qY-RZ
	for ipv6@ietf.org; Fri, 29 Jun 2007 09:39:12 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 09:38:15 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANqnhEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,475,1175486400"; 
	d="scan'208"; a="124878695:sNHT30364856"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TDcEQ9003145
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 09:38:14 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TDc96g002947
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 13:38:14 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 09:38:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jun 2007 09:38:18 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace6UsBd5kF+rzC0QmmMS6ys+ZWO1w==
From: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 29 Jun 2007 13:38:10.0980 (UTC)
	FILETIME=[BC225640:01C7BA52]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1028; t=1183124294;
	x=1183988294; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20\(wbeebee\)=22=20<wbeebee@cisco.com>
	|Subject:=20Sending=20traffic=20to=20default=20router=20when=20RA=20has=2
	0no=20PIO |Sender:=20 |To:=20<ipv6@ietf.org>;
	bh=QumvMRyMtUtnJvdUuTbFEepMlxsL1Dd0R/9jQRl+nu4=;
	b=IPRukhzt63tXZu2KZ5hEJmsxyNhS/OW+SvfOV/FFbYU8Mf6rCbpaVu7kWnUjPQGMfTGdp8CB
	seqj/PS4SCdew1K5E/kFBgFRzee/2ffMHBO6ay0O69DTyjU+/LLmPuga;
Authentication-Results: rtp-dkim-1; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: Sending traffic to default router when RA has no PIO
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Section 3.1 of RFC 2461 describes intended behavior when a host
receives an RA without an advertised prefix:

      "Multiple prefixes can be associated with the same link.  By
      default, hosts learn all on-link prefixes from Router
      Advertisements.  However, routers may be configured to omit some
      or all prefixes from Router Advertisements.  In such cases hosts
      assume that destinations are off-link and send traffic to routers.
      A router can then issue redirects as appropriate."

As described in our draft, this language should be strengthened to state

that without advertised prefixes, without manual configuration, and=20
without redirects, hosts MUST send all non-link-local traffic to the=20
default router and MUST NOT issue an NS to resolve any destination=20
other than a link-local address.

Please note that a new, popular host implementation does not follow this
and failure to do so can result in lack of interoperability and
connectivity.=20

- Wes Beebee

=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 10:22:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4HN2-0000nS-Uc; Fri, 29 Jun 2007 10:22:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4HN0-0000mD-RK
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:22:46 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4HMR-00012w-26
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:22:46 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5TEM9Sx007189
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 29 Jun 2007 07:22:10 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5TEM869002910; Fri, 29 Jun 2007 09:22:08 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5TEM2Hp002643; Fri, 29 Jun 2007 09:22:07 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 07:21:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jun 2007 07:21:52 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8E1@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <200706290143.l5T1hLJC099891@drugs.dv.isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace57uTFL3Yz/62dS621WfQGd5l1hQAaP4kA
References: Your message of "Thu, 28 Jun 2007 08:14:15 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
	<200706290143.l5T1hLJC099891@drugs.dv.isc.org>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Mark Andrews" <Mark_Andrews@isc.org>
X-OriginalArrivalTime: 29 Jun 2007 14:21:58.0820 (UTC)
	FILETIME=[DA72E640:01C7BA58]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ipv6@ietf.org, Paul Vixie <Paul_Vixie@isc.org>
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

It should be obvious by now that my main purpose in these
discussions was to motivate a use case, and I consider my
"four questions" message as an unfortunate diversion from
that. A fifth question that should have been asked is:

  5) will it impair my use case?

and a sixth is:

  6) how can I be sure that it won't?

Fred
fred.l.templin@boeing.com=20

> -----Original Message-----
> From: Mark Andrews [mailto:Mark_Andrews@isc.org]=20
> Sent: Thursday, June 28, 2007 6:43 PM
> To: Templin, Fred L
> Cc: Paul Vixie; ipv6@ietf.org
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt=20
>=20
>=20
> > My use case questions that still need to be satisfied are:
> >=20
> >   1) can any site (large or small) get a ULA-C?
> >   2) can the ULA-C's be obtained at a nominal cost?
> >   3) can the ULA-C's be published in the global DNS
> >      forward and reverse?
> >   4) can the ULA-C's be kept out of the DFZ?
> >=20
> > If Paul's proposal answers all of these as "yes", then
> > I have no objections.
> >=20
> > Fred
> > fred.l.templin@boeing.com
>=20
> 	I believe 1 and 2 where always the intention.
> 	I believe you can't stop AAAA records for them being added.
> 	I believe that the reverse can be done but we need to take=20
> 	care.
> 	I believe 4 can be achieved with the appropriate use of route
> 	filter and loose URPF over FC00/7.  Default null route for
> 	FC00/7 and appropritate route filters.
> =20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 10:26:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4HQo-0006Pz-F6; Fri, 29 Jun 2007 10:26:42 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4HQm-0006Pn-6y
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:26:40 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4HQl-0006SR-VE
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:26:40 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 10:26:39 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAM6zhEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,475,1175486400"; 
	d="scan'208"; a="124883986:sNHT30739886"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5TEQdZ2009418; 
	Fri, 29 Jun 2007 10:26:39 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5TEQds2008223; 
	Fri, 29 Jun 2007 14:26:39 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 10:26:22 -0400
Received: from [161.44.65.201] ([161.44.65.201]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 10:26:21 -0400
In-Reply-To: <m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	<m2d4zihj67.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>
	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <A4A43025-30D1-49A3-96BB-B4CE63044E79@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Ralph Droms <rdroms@cisco.com>
Date: Fri, 29 Jun 2007 10:26:19 -0400
To: =?UTF-8?Q?JINMEI_Tatuya_/_=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 29 Jun 2007 14:26:21.0965 (UTC)
	FILETIME=[774BA3D0:01C7BA59]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2188; t=1183127199;
	x=1183991199; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=3D?UTF-8?Q?JINMEI_Tatuya_/_=3DE7=3DA5=3D9E=3DE6=3D98=3D8E=3DE9=3D
	81=3D94=3DE5=3D93=3D89?=3D=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=wHxL0bnrOYSZe8hnyWVb5+Vl4ZZVDR3WoX1/nD9Ikts=;
	b=NMFCBKiqCyLC6z3iHdtZp44xsLnQypSBxxTNYARaEFmoKCBOG03u3Dfr7iVS+WPbT71azW18
	rofMnIPxjWOs5cK4yMOOCA9lA5cSAJ0QDnnKdlebai75XIOPWybOjB9C;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / =E7=A5=9E=E6=98=8E=
=E9=81=94=E5=93=89 =20
wrote:

> At Wed, 27 Jun 2007 14:27:37 -0400,
> Ralph Droms <rdroms@cisco.com> wrote:
>
>> One bug that may or may not be common is to make assumptions about
>> the prefixes on a link based on addresses assigned to an interface.
>> I can imagine (and I believe we've actually made a real sighting of
>> this scenario) that an IPv6 implementor might extrapolate IPv4
>> conventions and extract the /64 prefix from an assigned address
>> (either SLAAC, DHCP or manual config), and add a route to the host
>> table indicating that the prefix is on-link, regardless of whether
>> the prefix is advertised as "on-link" in an RA.
>
> [...]
>
> If the system administrator manually configures an IPv6 address with a
> prefix length smaller than 128, the kernel will assume that the
> corresponding prefix is on-link.  But I believe this should be
> reasonable.
>
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba =
Corp.
> 					jinmei@isl.rdc.toshiba.co.jp

I see where draft-wbeebee-nd-implementation-pitfalls also mentions =20
manual configuration as a special case:

    2.  The RA and ICMPv6 Redirects from the default router are the only
        sources of information for on-link determination.  DHCPv6 or any
        other configuration on the host MUST NOT be used for on-link
        determination.  Manual configuration of a host introduces its =20=

own
        set of security considerations and is beyond the scope of this
        document.

Is there some reason to believe the information about on-link =20
prefixes should be implicitly overridden in the case of manual =20
address assignment?  I can understand explicitly overriding =20
information from RAs by manually configuring the on-link information =20
as a separate step from manual address assignment.  But it seems to =20
me that assuming the prefix from a manually configured address is on-=20
link might cause unexpected loss of connectivity if the prefix does =20
require off-link delivery through the router.

- Ralph


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 10:57:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Hu9-00011r-85; Fri, 29 Jun 2007 10:57:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Hu7-00011k-3p
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:56:59 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4HtF-0000dN-TW
	for ipv6@ietf.org; Fri, 29 Jun 2007 10:56:59 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 10:56:05 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANa6hEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,475,1175486400"; 
	d="scan'208"; a="124886862:sNHT102436316"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TEu4xC005322; 
	Fri, 29 Jun 2007 10:56:04 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TEtn6k028819; 
	Fri, 29 Jun 2007 14:56:04 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 10:55:48 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Jun 2007 10:55:47 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <A4A43025-30D1-49A3-96BB-B4CE63044E79@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
Thread-Index: Ace6WXdaQK5UoSvHTyqq3voj1aZQ9AAAp+Dw
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>
	<m1abusbtko.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B11@xmb-rtp-20e.amer.cisco.com>
	<467BD7FC.1030405@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>
	<467BDEE5.30807@gmail.com>
	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>
	<467F62DA.2010802@gmail.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>
	<m2645chx46.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>
	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>
	<m2d4zihj67.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>
	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>
	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>
	<A4A43025-30D1-49A3-96BB-B4CE63044E79@ci sco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>,
	=?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=
	<jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 29 Jun 2007 14:55:48.0888 (UTC)
	FILETIME=[9476B180:01C7BA5D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3220; t=1183128964;
	x=1183992964; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=20changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>,
	=0A=20=20=20=2
	0=20=20=20=20=3D?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=3
	D=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=JArj36oiZJHs5K+E9e6qhTaB4UlzRp3DHTAeoMqCw5M=;
	b=fQcxijRuMub4GxJsyavuIrLrvThYPFOO+MiKHu1K+ml1ubUG/9b8v8rlsuL1q0cLpRgL65c2
	ugDkcPErp13QCJkLqKyzDIAD/rEfM2XNNK+YGVbUIyycHVWS4W1g58+W;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent
	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Please see in line below with "<hs>" 

-----Original Message-----
From: Ralph Droms (rdroms) 
Sent: Friday, June 29, 2007 10:26 AM
To: JINMEI Tatuya / ????
Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh (shemant)
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changessuggested to 2462bis-08


On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@L@C#:H(J
wrote:

> At Wed, 27 Jun 2007 14:27:37 -0400,
> Ralph Droms <rdroms@cisco.com> wrote:
>
>> One bug that may or may not be common is to make assumptions about 
>> the prefixes on a link based on addresses assigned to an interface.
>> I can imagine (and I believe we've actually made a real sighting of 
>> this scenario) that an IPv6 implementor might extrapolate IPv4 
>> conventions and extract the /64 prefix from an assigned address 
>> (either SLAAC, DHCP or manual config), and add a route to the host 
>> table indicating that the prefix is on-link, regardless of whether 
>> the prefix is advertised as "on-link" in an RA.
>
> [...]
>
> If the system administrator manually configures an IPv6 address with a 
> prefix length smaller than 128, the kernel will assume that the 
> corresponding prefix is on-link.  But I believe this should be 
> reasonable.
>
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba Corp.
> 					jinmei@isl.rdc.toshiba.co.jp

I see where draft-wbeebee-nd-implementation-pitfalls also mentions manual configuration as a special case:

    2.  The RA and ICMPv6 Redirects from the default router are the only
        sources of information for on-link determination.  DHCPv6 or any
        other configuration on the host MUST NOT be used for on-link
        determination.  Manual configuration of a host introduces its own
        set of security considerations and is beyond the scope of this
        document.

Is there some reason to believe the information about on-link prefixes should be implicitly overridden in the case of manual address assignment?  I can understand explicitly overriding information from RAs by manually configuring the on-link information as a separate step from manual address assignment.  But it seems to me that assuming the prefix from a manually configured address is on- link might cause unexpected loss of connectivity if the prefix does require off-link delivery through the router.

<hs> If the host has been manually configured for IPv6 address where the host was also configured for prefix and prefix length, then what's on-link for this host can be determined by host. But what if manual configuration configured an IPv6 address and maybe, also the prefix, but forgot to configure prefix length. Then this manual configuration has no means to determine what's on-link for a destination based on the data from manual configuration. I have host not assuming a default prefix length yet. The RA has been explicitly ignored. So not this host has no choice but to send non-link-local traffic to the default router. Specifying manual configuration behavior and its interaction with RA is a can of worms that will take time to clear up.

Hemant

- Ralph


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 11:33:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4ITn-0007YZ-Tq; Fri, 29 Jun 2007 11:33:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4ITm-0007SN-JA
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:33:50 -0400
Received: from sa.vix.com ([204.152.187.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4ITV-0001bL-3X
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:33:50 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 7E0DA11425
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 15:33:30 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Fri, 29 Jun 2007 12:13:30 +0200."
	<4684DB4A.2060703@gmail.com> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com> <46834717.3090102@internap.com>
	<4683712F.1010602@gmail.com> <14556.1183042057@sa.vix.com>
	<4684DB4A.2060703@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 29 Jun 2007 15:33:30 +0000
Message-ID: <27414.1183131210@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter <brian.e.carpenter@gmail.com>:

> [vixie]
> > ... and why are we wasting our keystrokes discussing this if there's a
> > preclusive topic being discussed somewhere entirely else?
> 
> I don't think it's preclusive. If that discussion does lead to an
> architectural id/locator split, it will not override what we're discussing
> here, IMHO. We'll still have IP addresses and they will still need to be
> unambiguous. Also, that is a discussion that is finally happening after ten
> years of needing to happen, so it's hardly surprising that it hasn't
> converged rapidly.

ok.

> >> I have a strong feeling there is no consensus forming...
> 
> [vixie]
> > i disagree, i've been immersed in this for a month now, and my draft edits
> > as proposed last night represent my understanding of a potential
> > consensus, which unlike you i can feel forming.
> 
> I personally am not part of it then. I don't want to see any structured
> allocation scheme; a robotic guarantee of uniqueness is all I want to see.

i've been on the outside of ietf consensus more often than inside, so you've
got my sympathy if that matters.  also note, the fact that you don't agree
does not mean consensus isn't forming.  as to your specific concern, i'm
interested in knowing more about why you want the robotic guaranty of
uniqueness to be the only feature.  others here have made compelling cases
for a larger feature set for ULA-C, and yet you are unmoved.  your words...

> I don't want to facilitate making these things look like a binary hierarchy,
> because that will cause people to believe for the next 50 years that they
> aggregate and are routeable. I also don't want to accidentally create a
> business in selling large integers, which would be the effect of structured
> registration as opposed to robotic random numbers.

...involve a lot of unsupported predictions, and sound somewhat emotional.  i
don't think that we should deny others the features they're asking for on the
basis of what you don't want, especially since the things you say you don't
want aren't obviously inevitable, or obviously bad, to anybody else we've
heard from.  if you can make a compelling case for why these results are
inevitable AND why they would be bad, then you could win the elusive
"consensus" over to your side.  otherwise i think you're going to be on the
outside of this one.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 11:54:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ins-0004WR-7e; Fri, 29 Jun 2007 11:54:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Inq-0004WE-RE
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:54:34 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4Inq-0003mr-HC
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:54:34 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l5TFs1Em006184
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 29 Jun 2007 08:54:01 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l5TFs1Q7015394; Fri, 29 Jun 2007 08:54:01 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l5TFs0DU015348; Fri, 29 Jun 2007 08:54:00 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 08:53:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jun 2007 08:53:05 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8E2@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <27414.1183131210@sa.vix.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
Thread-Index: Ace6Ywoq2+Hn45imRoWCWwQBWL2c9gAAfGXg
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com><4683712F.1010602@gmail.com>
	<14556.1183042057@sa.vix.com><4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 29 Jun 2007 15:53:58.0930 (UTC)
	FILETIME=[B4B0D720:01C7BA65]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 
Subject: RE: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

As of right now, I have a use case that (AFAICT) is
not yet fully-supported by functional specification.
So, IMHO it would be premature to turn over address
delegation authority at this time.

Fred
fred.l.templin@boeing.com=20

> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]=20
> Sent: Friday, June 29, 2007 8:34 AM
> To: ipv6@ietf.org
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt=20
>=20
> Brian E Carpenter <brian.e.carpenter@gmail.com>:
>=20
> > [vixie]
> > > ... and why are we wasting our keystrokes discussing this=20
> if there's a
> > > preclusive topic being discussed somewhere entirely else?
> >=20
> > I don't think it's preclusive. If that discussion does lead to an
> > architectural id/locator split, it will not override what=20
> we're discussing
> > here, IMHO. We'll still have IP addresses and they will=20
> still need to be
> > unambiguous. Also, that is a discussion that is finally=20
> happening after ten
> > years of needing to happen, so it's hardly surprising that it hasn't
> > converged rapidly.
>=20
> ok.
>=20
> > >> I have a strong feeling there is no consensus forming...
> >=20
> > [vixie]
> > > i disagree, i've been immersed in this for a month now,=20
> and my draft edits
> > > as proposed last night represent my understanding of a potential
> > > consensus, which unlike you i can feel forming.
> >=20
> > I personally am not part of it then. I don't want to see=20
> any structured
> > allocation scheme; a robotic guarantee of uniqueness is all=20
> I want to see.
>=20
> i've been on the outside of ietf consensus more often than=20
> inside, so you've
> got my sympathy if that matters.  also note, the fact that=20
> you don't agree
> does not mean consensus isn't forming.  as to your specific=20
> concern, i'm
> interested in knowing more about why you want the robotic guaranty of
> uniqueness to be the only feature.  others here have made=20
> compelling cases
> for a larger feature set for ULA-C, and yet you are unmoved. =20
> your words...
>=20
> > I don't want to facilitate making these things look like a=20
> binary hierarchy,
> > because that will cause people to believe for the next 50=20
> years that they
> > aggregate and are routeable. I also don't want to=20
> accidentally create a
> > business in selling large integers, which would be the=20
> effect of structured
> > registration as opposed to robotic random numbers.
>=20
> ...involve a lot of unsupported predictions, and sound=20
> somewhat emotional.  i
> don't think that we should deny others the features they're=20
> asking for on the
> basis of what you don't want, especially since the things you=20
> say you don't
> want aren't obviously inevitable, or obviously bad, to=20
> anybody else we've
> heard from.  if you can make a compelling case for why these=20
> results are
> inevitable AND why they would be bad, then you could win the elusive
> "consensus" over to your side.  otherwise i think you're=20
> going to be on the
> outside of this one.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 11:58:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ir5-0006HC-54; Fri, 29 Jun 2007 11:57:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Ir3-0006H0-NM
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:57:53 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Iqj-0000cn-Mm
	for ipv6@ietf.org; Fri, 29 Jun 2007 11:57:53 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 705F11143A
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 15:57:29 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Fri, 29 Jun 2007 08:53:05 MST."
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8E2@XCH-NW-7V2.nw.nos.boeing.com>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com>
	<46834717.3090102@internap.com><4683712F.1010602@gmail.com>
	<14556.1183042057@sa.vix.com><4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8E2@XCH-NW-7V2.nw.nos.boeing.com>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 29 Jun 2007 15:57:29 +0000
Message-ID: <30910.1183132649@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> As of right now, I have a use case that (AFAICT) is
> not yet fully-supported by functional specification.

which one?  AFAICT you're covered.

> So, IMHO it would be premature to turn over address
> delegation authority at this time.

then let's keep going.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 12:06:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ize-0002JN-PW; Fri, 29 Jun 2007 12:06:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Izc-0002Do-OK
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:06:44 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4IzO-0004Wk-Sj
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:06:44 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 12:06:30 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CABTKhEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="64017788:sNHT34243102"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TG6Uq3008208; 
	Fri, 29 Jun 2007 12:06:30 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TG6874020671; 
	Fri, 29 Jun 2007 16:06:30 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 12:06:24 -0400
Received: from [161.44.65.201] ([161.44.65.201]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 12:06:23 -0400
In-Reply-To: <46852B09.8020505@uninett.no>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<467BD7FC.1030405@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>	<467BDEE5.30807@gmail.com>	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>	<467F62DA.2010802@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>	<m2645chx46.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>	<m2d4zihj67.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>	<A4A43025-30D1-49A3-96BB-B4CE63044E79@ci
	sco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
	<46852B09.8020505@uninett.no>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-2022-JP; delsp=yes; format=flowed
Message-Id: <0FF50CE9-6CC9-4AE8-8F1E-0A90C818FBF2@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Fri, 29 Jun 2007 12:06:21 -0400
To: Stig Venaas <stig.venaas@uninett.no>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 29 Jun 2007 16:06:23.0991 (UTC)
	FILETIME=[70C82070:01C7BA67]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5218; t=1183133190;
	x=1183997190; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=09changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20Stig=20Venaas=20<stig.venaas@uninett.no>;
	bh=vm24vLGKzEmP2P8cgiyA8q6J3kJksxxiQ3d+dHr9EJw=;
	b=GsYYIMpu3T7K/gAAxZG++uvKKmLBqfCnsNHCsAU6tfA3hvsrurcZrsllhyTxvWZK6ZbA+1KI
	Q9NZ6ulGIIc01igwNYo6iefBeM6P4Ii5rlyE8yfhU/N5ftFOP4tCTcaW;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>,
	=?UTF-8?Q?JINMEI_Tatuya_/_=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with
	urgent	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hemant - does RFC 2461 allow a host to ignore the PIOs in RAs?

Stig - you wrote "At least as a sysadmin/user I would find it  
confusing if the prefix length I configured would not be used for on- 
link determination. I think it's more bad than good to try to  
separate the two. I'm happy the way it currently is on the systems  
I've seen."  I can understand that it should be possible to manually  
configure on-link prefix information.  I question whether that  
configuration should be conceptually tied with address assignment  
because of the design of IPv6, or do we mix address assignment with  
prefix information because that's the way it was done in IPv4?

Looking back to the definition of DHCPv6 - we received a lot of input  
that DHCPv6 should *not* include information about default routers  
and on-link prefixes, because that information comes from RAs.  That  
argument made sense to me at the time; makes sense to me in the case  
of manual address assignment, too...

- Ralph


On Jun 29, 2007, at Jun 29, 2007,11:53 AM, Stig Venaas wrote:

> Hemant Singh (shemant) wrote:
>> Please see in line below with "<hs>"
>>
>> -----Original Message-----
>> From: Ralph Droms (rdroms)
>> Sent: Friday, June 29, 2007 10:26 AM
>> To: JINMEI Tatuya / ????
>> Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh  
>> (shemant)
>> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with  
>> urgent changessuggested to 2462bis-08
>>
>>
>> On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@(B 
>> $BL@C#:H(B
>> wrote:
>>
>>> At Wed, 27 Jun 2007 14:27:37 -0400,
>>> Ralph Droms <rdroms@cisco.com> wrote:
>>>
>>>> One bug that may or may not be common is to make assumptions about
>>>> the prefixes on a link based on addresses assigned to an interface.
>>>> I can imagine (and I believe we've actually made a real sighting of
>>>> this scenario) that an IPv6 implementor might extrapolate IPv4
>>>> conventions and extract the /64 prefix from an assigned address
>>>> (either SLAAC, DHCP or manual config), and add a route to the host
>>>> table indicating that the prefix is on-link, regardless of whether
>>>> the prefix is advertised as "on-link" in an RA.
>>> [...]
>>>
>>> If the system administrator manually configures an IPv6 address  
>>> with a
>>> prefix length smaller than 128, the kernel will assume that the
>>> corresponding prefix is on-link.  But I believe this should be
>>> reasonable.
>>>
>>> 					JINMEI, Tatuya
>>> 					Communication Platform Lab.
>>> 					Corporate R&D Center, Toshiba Corp.
>>> 					jinmei@isl.rdc.toshiba.co.jp
>>
>> I see where draft-wbeebee-nd-implementation-pitfalls also mentions  
>> manual configuration as a special case:
>>
>>     2.  The RA and ICMPv6 Redirects from the default router are  
>> the only
>>         sources of information for on-link determination.  DHCPv6  
>> or any
>>         other configuration on the host MUST NOT be used for on-link
>>         determination.  Manual configuration of a host introduces  
>> its own
>>         set of security considerations and is beyond the scope of  
>> this
>>         document.
>>
>> Is there some reason to believe the information about on-link  
>> prefixes should be implicitly overridden in the case of manual  
>> address assignment?  I can understand explicitly overriding  
>> information from RAs by manually configuring the on-link  
>> information as a separate step from manual address assignment.   
>> But it seems to me that assuming the prefix from a manually  
>> configured address is on- link might cause unexpected loss of  
>> connectivity if the prefix does require off-link delivery through  
>> the router.
>
> At least as a sysadmin/user I would find it confusing if the prefix
> length I configured would not be used for on-link determination.
>
> I think it's more bad than good to try to separate the two. I'm
> happy the way it currently is on the systems I've seen.
>
>>
>> <hs> If the host has been manually configured for IPv6 address  
>> where the host was also configured for prefix and prefix length,  
>> then what's on-link for this host can be determined by host. But  
>> what if manual configuration configured an IPv6 address and maybe,  
>> also the prefix, but forgot to configure prefix length. Then this  
>> manual configuration has no means to determine what's on-link for  
>> a destination based on the data from manual configuration. I have  
>> host not assuming a default prefix length yet. The RA has been  
>> explicitly ignored. So not this host has no choice but to send non- 
>> link-local traffic to the default router. Specifying manual  
>> configuration behavior and its interaction with RA is a can of  
>> worms that will take time to clear up.
>
> Can you manually configure prefix on a host without also specifying
> prefix length?
>
> Stig
>
>>
>> Hemant
>>
>> - Ralph
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 12:09:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4J2Y-0001pk-AJ; Fri, 29 Jun 2007 12:09:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4J2W-0001iI-HD
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:09:44 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4J1Y-0004wC-4L
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:09:44 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l5TGCEW5021139;
	Fri, 29 Jun 2007 11:12:15 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 11:08:43 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 11:08:42 -0500
Message-ID: <46852E40.1010103@ericsson.com>
Date: Fri, 29 Jun 2007 12:07:28 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: =?windows-1252?Q?JINMEI_Tatuya_/_=3F=3F=3F=3F?=
	<jinmei@isl.rdc.toshiba.co.jp>
References: <46827D36.7050307@ericsson.com>	
	<m1k5topksy.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<46841FDC.4040604@ericsson.com>
	<m14pkrpdud.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m14pkrpdud.wl%jinmei@isl.rdc.toshiba.co.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 29 Jun 2007 16:08:42.0968 (UTC)
	FILETIME=[C39E5580:01C7BA67]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ipv6@ietf.org
Subject: Re: Privacy Addresses AUTH48 Changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jinmei,
   You have a point. I agree with you about the downref rule being an 
NOP for implementers (I do not care either). This is another reason that 
I wanted to go with an IANA registry for the purpose. Then we do not 
have to worry about the administrative hurdles of the downref. I will 
wait for further comments from the WG before I make the change.

Cheers
Suresh

JINMEI Tatuya / ???? wrote:
> At Thu, 28 Jun 2007 16:53:48 -0400,
> Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> 
>>    Thanks for pointing that out. I will be adding the reference to 
>> RFC2526 under Informational. Yes.
> 
> Okay, then the problem is whether we can safely categorize the
> reference to RFC2526 as informative.  I personally don't think it's
> safe:
> 
>>> address RFC will become a draft standard; but I'd categorize it as
>>> normative in the above context because implementors must refer to
>>> RFC2526 to implement the privacy-addrs spec.
> 
> but I personally wouldn't oppose to your proposed action either (I
> often feel the downref rule doesn't help much for implementors in
> practice while it can easily be an unnecessary showstopper in the
> standardization process).  In any event, I think we should confirm the
> consensus about the categorization in this wg (and possibly with the
> ADs).
> 
> 					JINMEI, Tatuya
> 					Communication Platform Lab.
> 					Corporate R&D Center, Toshiba Corp.
> 					jinmei@isl.rdc.toshiba.co.jp


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 12:44:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JZc-0008DJ-3r; Fri, 29 Jun 2007 12:43:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4JZa-0008DE-QF
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:43:54 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4JZa-0007F2-HG
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:43:54 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-4.cisco.com with ESMTP; 29 Jun 2007 09:43:29 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAN3ThEarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175497200"; d="scan'208"; a="5921128:sNHT19479072"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5TGhTUt018025
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 09:43:29 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5TGhTka012018
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 16:43:29 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 12:43:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Jun 2007 12:43:27 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0351DE33@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace6UsBd5kF+rzC0QmmMS6ys+ZWO1wAGUf9g
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 29 Jun 2007 16:43:28.0818 (UTC)
	FILETIME=[9EE1C920:01C7BA6C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2048; t=1183135409;
	x=1183999409; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20;
	bh=NU5gU4mUBmsJJCsfD/5WTYDr4XPQBo1Rf/QDDuqZXZ0=;
	b=TEqq/kPPC/xYpBWFRfjv00i+3BLvcP1emUwcSqOdOUNO13YqNDVmUUkxzAzWUuFkPC4BareR
	HcCJUJJQg99E9oo6DJYCfE2Ol529SwPQ0JsghaG5YK+6QATzj/VUVQ3u;
Authentication-Results: sj-dkim-3; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: 
Subject: RE: Sending traffic to default router when RA has no PIO
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I have a follow up question to authors of RFC 2461 or 2461bis I-D. In
section 3.1 para mentioned below where the RFC and I-D bis say "By
default, hosts learn..."=20

Since default is mentioned, can you clarify what other means exists for
a host to learn about on-link prefixes ? Are you referring to manual
configuration as another means ? What other ways besides manual config
exist to learn on-link prefixes ?

If it's only manual configuration, does it makes sense to add such a
reference? "By default" is a very loaded term that makes a reader
wonder, gee, how many other ways can one learn about on-link prefixes.

Thanks.

Hemant

-----Original Message-----
From: Wes Beebee (wbeebee)=20
Sent: Friday, June 29, 2007 9:38 AM
To: ipv6@ietf.org
Subject: Sending traffic to default router when RA has no PIO

Section 3.1 of RFC 2461 describes intended behavior when a host receives
an RA without an advertised prefix:

      "Multiple prefixes can be associated with the same link.  By
      default, hosts learn all on-link prefixes from Router
      Advertisements.  However, routers may be configured to omit some
      or all prefixes from Router Advertisements.  In such cases hosts
      assume that destinations are off-link and send traffic to routers.
      A router can then issue redirects as appropriate."

As described in our draft, this language should be strengthened to state

that without advertised prefixes, without manual configuration, and
without redirects, hosts MUST send all non-link-local traffic to the
default router and MUST NOT issue an NS to resolve any destination other
than a link-local address.

Please note that a new, popular host implementation does not follow this
and failure to do so can result in lack of interoperability and
connectivity.=20

- Wes Beebee

=20

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 12:47:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JdM-0004g2-5r; Fri, 29 Jun 2007 12:47:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4JdL-0004fB-1C
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:47:47 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4JdG-0007en-DW
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:47:47 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 382BEB5AAF;
	Fri, 29 Jun 2007 17:53:52 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 14097-01-31; Fri, 29 Jun 2007 17:53:51 +0200 (CEST)
Received: from [IPv6?2001?700?1?1100?a909?2492?dd71?18bf] (unknown
	[IPv6:2001:700:1:1100:a909:2492:dd71:18bf])
	by tyholt.uninett.no (Postfix) with ESMTP id 52E29B5A96;
	Fri, 29 Jun 2007 17:53:51 +0200 (CEST)
Message-ID: <46852B09.8020505@uninett.no>
Date: Fri, 29 Jun 2007 17:53:45 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<467BD7FC.1030405@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>	<467BDEE5.30807@gmail.com>	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>	<467F62DA.2010802@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>	<m2645chx46.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>	<m2d4zihj67.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>	<A4A43025-30D1-49A3-96BB-B4CE63044E79@ci
	sco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: =?ISO-2022-JP?B?SklOTUVJIFQ=?=
	=?ISO-2022-JP?B?YXR1eWEgLyAbJEI/QExAQyM6SBsoQg==?=
	<jinmei@isl.rdc.toshiba.co.jp>, IETF Mailing List IPv6 <ipv6@ietf.org>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with
 urgent	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hemant Singh (shemant) wrote:
> Please see in line below with "<hs>" 
> 
> -----Original Message-----
> From: Ralph Droms (rdroms) 
> Sent: Friday, June 29, 2007 10:26 AM
> To: JINMEI Tatuya / ????
> Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh (shemant)
> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changessuggested to 2462bis-08
> 
> 
> On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@L@C#:H(B
> wrote:
> 
>> At Wed, 27 Jun 2007 14:27:37 -0400,
>> Ralph Droms <rdroms@cisco.com> wrote:
>>
>>> One bug that may or may not be common is to make assumptions about 
>>> the prefixes on a link based on addresses assigned to an interface.
>>> I can imagine (and I believe we've actually made a real sighting of 
>>> this scenario) that an IPv6 implementor might extrapolate IPv4 
>>> conventions and extract the /64 prefix from an assigned address 
>>> (either SLAAC, DHCP or manual config), and add a route to the host 
>>> table indicating that the prefix is on-link, regardless of whether 
>>> the prefix is advertised as "on-link" in an RA.
>> [...]
>>
>> If the system administrator manually configures an IPv6 address with a 
>> prefix length smaller than 128, the kernel will assume that the 
>> corresponding prefix is on-link.  But I believe this should be 
>> reasonable.
>>
>> 					JINMEI, Tatuya
>> 					Communication Platform Lab.
>> 					Corporate R&D Center, Toshiba Corp.
>> 					jinmei@isl.rdc.toshiba.co.jp
> 
> I see where draft-wbeebee-nd-implementation-pitfalls also mentions manual configuration as a special case:
> 
>     2.  The RA and ICMPv6 Redirects from the default router are the only
>         sources of information for on-link determination.  DHCPv6 or any
>         other configuration on the host MUST NOT be used for on-link
>         determination.  Manual configuration of a host introduces its own
>         set of security considerations and is beyond the scope of this
>         document.
> 
> Is there some reason to believe the information about on-link prefixes should be implicitly overridden in the case of manual address assignment?  I can understand explicitly overriding information from RAs by manually configuring the on-link information as a separate step from manual address assignment.  But it seems to me that assuming the prefix from a manually configured address is on- link might cause unexpected loss of connectivity if the prefix does require off-link delivery through the router.

At least as a sysadmin/user I would find it confusing if the prefix
length I configured would not be used for on-link determination.

I think it's more bad than good to try to separate the two. I'm
happy the way it currently is on the systems I've seen.

> 
> <hs> If the host has been manually configured for IPv6 address where the host was also configured for prefix and prefix length, then what's on-link for this host can be determined by host. But what if manual configuration configured an IPv6 address and maybe, also the prefix, but forgot to configure prefix length. Then this manual configuration has no means to determine what's on-link for a destination based on the data from manual configuration. I have host not assuming a default prefix length yet. The RA has been explicitly ignored. So not this host has no choice but to send non-link-local traffic to the default router. Specifying manual configuration behavior and its interaction with RA is a can of worms that will take time to clear up.

Can you manually configure prefix on a host without also specifying
prefix length?

Stig

> 
> Hemant
> 
> - Ralph
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 12:54:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JjP-0001TY-Q2; Fri, 29 Jun 2007 12:54:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4JjN-0001Pn-OO
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:54:01 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4JiR-00012g-Io
	for ipv6@ietf.org; Fri, 29 Jun 2007 12:54:01 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 12:53:03 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CABHWhEZAZnme/2dsb2JhbACCZw
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208,217"; a="64022427:sNHT68794340"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TGr2vq029517; 
	Fri, 29 Jun 2007 12:53:02 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TGql6g003337; 
	Fri, 29 Jun 2007 16:53:05 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 12:52:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 29 Jun 2007 12:52:53 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0351DE3C@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <46852B09.8020505@uninett.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with
	urgent	changessuggested to 2462bis-08
Thread-Index: Ace6ZbZZQDybNXEFRFWIgzyhPyguFAAB4zVA
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<467BD7FC.1030405@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>	<467BDEE5.30807@gmail.com>	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>	<467F62DA.2010802@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>	<m2645chx46.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>	<m2d4zihj67.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>	<A4A43025-30D1-49A3-96BB-B4CE63044E79@ci
	sco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
	<46852B09.8020505@uninett.no>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Stig Venaas" <stig.venaas@uninett.no>
X-OriginalArrivalTime: 29 Jun 2007 16:52:53.0981 (UTC)
	FILETIME=[EFBED0D0:01C7BA6D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20062; t=1183135982;
	x=1183999982; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=09changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>;
	bh=+K8TU6NdyrlHj1g4fMxwgN6Hp8pO7mfhSvstlAq/m1c=;
	b=ZuSOyA+YVxkolsHO80dvZqNs9uQMdCK+BCppgZIOIFelgFdX4EDxsOwLGzCTQyBDfK9ZamnY
	ZpW5mrCCWbJP9fG/RrWPEdynfps1i2jy/4SU/uTwTDA3K3pBmE14Cdm1;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 142a000676f5977e1797396caab8b611
Cc: =?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=
	<jinmei@isl.rdc.toshiba.co.jp>, IETF Mailing List IPv6 <ipv6@ietf.org>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with
	urgent	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0659278677=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0659278677==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BA6D.EF8639B8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BA6D.EF8639B8
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit

Stig,

Wrt to this question you raised:

"Can you manually configure prefix on a host without also specifying prefix length?"

See text below snipped from http://www.microsoft.com/technet/community/columns/cableguy/cg0506.mspx#EMB about Manual configuration for Windows Vista for IPv6. Text snipped from this URL shows that if an IPv6 address has been added via the CLI, prefix length is optional to be configured. Also, as I said before, I not too fond of a host assuming a default of 64 as this CLI help shows.

------------------ begin snip-------------------------------


Configuring IPv6 With the Netsh.exe Tool
In the same way as IPv6 for Windows XP, you can configure IPv6 addresses and other configuration parameters at the command line using commands in the netsh interface ipv6 context.

Configuring Addresses
To configure IPv6 addresses, you can use the netsh interface ipv6 add address command with the following syntax:

netsh interface ipv6 add address [interface=]Interface_Name_or_Index [address=]IPv6_Address[/Prefix_Length] [[type=]unicast|anycast] [[validlifetime=]Time|infinite] [preferredlifetime=]Time|infinite] [[store=]active|persistent]

* interface The connection or adapter's name or interface index.
 
* address The IPv6 address to add, [optionally followed by the subnet prefix length] (default of 64).

------------------------ end snip -------------------------------------------------------------------------------------
 
Hemant 

-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no] 
Sent: Friday, June 29, 2007 11:54 AM
To: Hemant Singh (shemant)
Cc: Ralph Droms (rdroms); JINMEI Tatuya / ????; IETF Mailing List IPv6
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changessuggested to 2462bis-08

Hemant Singh (shemant) wrote:
> Please see in line below with "<hs>" 
> 
> -----Original Message-----
> From: Ralph Droms (rdroms)
> Sent: Friday, June 29, 2007 10:26 AM
> To: JINMEI Tatuya / ????
> Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh 
> (shemant)
> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent 
> changessuggested to 2462bis-08
> 
> 
> On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@L@C#:H(J
> wrote:
> 
>> At Wed, 27 Jun 2007 14:27:37 -0400,
>> Ralph Droms <rdroms@cisco.com> wrote:
>>
>>> One bug that may or may not be common is to make assumptions about 
>>> the prefixes on a link based on addresses assigned to an interface.
>>> I can imagine (and I believe we've actually made a real sighting of 
>>> this scenario) that an IPv6 implementor might extrapolate IPv4 
>>> conventions and extract the /64 prefix from an assigned address 
>>> (either SLAAC, DHCP or manual config), and add a route to the host 
>>> table indicating that the prefix is on-link, regardless of whether 
>>> the prefix is advertised as "on-link" in an RA.
>> [...]
>>
>> If the system administrator manually configures an IPv6 address with 
>> a prefix length smaller than 128, the kernel will assume that the 
>> corresponding prefix is on-link.  But I believe this should be 
>> reasonable.
>>
>> 					JINMEI, Tatuya
>> 					Communication Platform Lab.
>> 					Corporate R&D Center, Toshiba Corp.
>> 					jinmei@isl.rdc.toshiba.co.jp
> 
> I see where draft-wbeebee-nd-implementation-pitfalls also mentions manual configuration as a special case:
> 
>     2.  The RA and ICMPv6 Redirects from the default router are the only
>         sources of information for on-link determination.  DHCPv6 or any
>         other configuration on the host MUST NOT be used for on-link
>         determination.  Manual configuration of a host introduces its own
>         set of security considerations and is beyond the scope of this
>         document.
> 
> Is there some reason to believe the information about on-link prefixes should be implicitly overridden in the case of manual address assignment?  I can understand explicitly overriding information from RAs by manually configuring the on-link information as a separate step from manual address assignment.  But it seems to me that assuming the prefix from a manually configured address is on- link might cause unexpected loss of connectivity if the prefix does require off-link delivery through the router.

At least as a sysadmin/user I would find it confusing if the prefix length I configured would not be used for on-link determination.

I think it's more bad than good to try to separate the two. I'm happy the way it currently is on the systems I've seen.

> 
> <hs> If the host has been manually configured for IPv6 address where the host was also configured for prefix and prefix length, then what's on-link for this host can be determined by host. But what if manual configuration configured an IPv6 address and maybe, also the prefix, but forgot to configure prefix length. Then this manual configuration has no means to determine what's on-link for a destination based on the data from manual configuration. I have host not assuming a default prefix length yet. The RA has been explicitly ignored. So not this host has no choice but to send non-link-local traffic to the default router. Specifying manual configuration behavior and its interaction with RA is a can of worms that will take time to clear up.

Can you manually configure prefix on a host without also specifying prefix length?

Stig

> 
> Hemant
> 
> - Ralph
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

------_=_NextPart_001_01C7BA6D.EF8639B8
Content-Type: text/html;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-2022-jp">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: draft-wbeebee-nd-implementation-pitfalls-00 with urgent	changessuggested to 2462bis-08</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Stig,</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Wrt to this question you raised:</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&quot;Can you manually configure prefix on a host without also specifying prefix length?&quot;</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">See text below snipped from </FONT></SPAN><A HREF="http://www.microsoft.com/technet/community/columns/cableguy/cg0506.mspx#EMB"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://www.microsoft.com/technet/community/columns/cableguy/cg0506.mspx#EMB</FONT></U></SPAN></A><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial"> about Manual configuration for Windows Vista for IPv6. Text snipped from this URL shows that if an IPv6 address has been added via the CLI, prefix length is optional to be configured. Also, as I said before, I not too fond of a host assuming a default of 64 as this CLI help shows.</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">------------------ begin snip-------------------------------</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Configuring IPv6 With the Netsh.exe Tool</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">In the same way as IPv6 for Windows XP, you can configure IPv6 addresses and other configuration parameters at the command line using commands in the netsh interface ipv6 context.</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Configuring Addresses</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">To configure IPv6 addresses, you can use the netsh interface ipv6 add address command with the following syntax:</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">netsh interface ipv6 add address [interface=]Interface_Name_or_Index [address=]IPv6_Address[/Prefix_Length] [[type=]unicast|anycast] [[validlifetime=]Time|infinite] [preferredlifetime=]Time|infinite] [[store=]active|persistent]</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&#8226; interface The connection or adapter's name or interface index.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&nbsp;</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&#8226; address The IPv6 address to add, [</FONT><FONT COLOR="#FF0000" SIZE=2 FACE="Arial">optionally followed by the subnet prefix length]</FONT> <FONT SIZE=2 FACE="Arial">(default of 64).</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">------------------------ end snip -------------------------------------------------------------------------------------</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&nbsp;</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Hemant </FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">-----Original Message-----</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">From: Stig Venaas [</FONT></SPAN><A HREF="mailto:stig.venaas@uninett.no"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">mailto:stig.venaas@uninett.no</FONT></U></SPAN></A><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">] </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Sent: Friday, June 29, 2007 11:54 AM</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">To: Hemant Singh (shemant)</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Cc: Ralph Droms (rdroms); JINMEI Tatuya / ????; IETF Mailing List IPv6</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changessuggested to 2462bis-08</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Hemant Singh (shemant) wrote:</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Please see in line below with &quot;&lt;hs&gt;&quot; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; -----Original Message-----</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; From: Ralph Droms (rdroms)</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Sent: Friday, June 29, 2007 10:26 AM</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; To: JINMEI Tatuya / ????</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; (shemant)</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; changessuggested to 2462bis-08</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="MS PGothic">&gt; On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@L@C#:H(J</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; wrote:</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; At Wed, 27 Jun 2007 14:27:37 -0400,</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; Ralph Droms &lt;rdroms@cisco.com&gt; wrote:</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; One bug that may or may not be common is to make assumptions about </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; the prefixes on a link based on addresses assigned to an interface.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; I can imagine (and I believe we've actually made a real sighting of </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; this scenario) that an IPv6 implementor might extrapolate IPv4 </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; conventions and extract the /64 prefix from an assigned address </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; (either SLAAC, DHCP or manual config), and add a route to the host </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; table indicating that the prefix is on-link, regardless of whether </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;&gt; the prefix is advertised as &quot;on-link&quot; in an RA.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; [...]</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; If the system administrator manually configures an IPv6 address with </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; a prefix length smaller than 128, the kernel will assume that the </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; corresponding prefix is on-link.&nbsp; But I believe this should be </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; reasonable.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt;</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; JINMEI, Tatuya</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Communication Platform Lab.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Corporate R&amp;D Center, Toshiba Corp.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jinmei@isl.rdc.toshiba.co.jp</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; I see where draft-wbeebee-nd-implementation-pitfalls also mentions manual configuration as a special case:</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp; 2.&nbsp; The RA and ICMPv6 Redirects from the default router are the only</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sources of information for on-link determination.&nbsp; DHCPv6 or any</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; other configuration on the host MUST NOT be used for on-link</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; determination.&nbsp; Manual configuration of a host introduces its own</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; set of security considerations and is beyond the scope of this</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document.</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Is there some reason to believe the information about on-link prefixes should be implicitly overridden in the case of manual address assignment?&nbsp; I can understand explicitly overriding information from RAs by manually configuring the on-link information as a separate step from manual address assignment.&nbsp; But it seems to me that assuming the prefix from a manually configured address is on- link might cause unexpected loss of connectivity if the prefix does require off-link delivery through the router.</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">At least as a sysadmin/user I would find it confusing if the prefix length I configured would not be used for on-link determination.</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">I think it's more bad than good to try to separate the two. I'm happy the way it currently is on the systems I've seen.</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; &lt;hs&gt; If the host has been manually configured for IPv6 address where the host was also configured for prefix and prefix length, then what's on-link for this host can be determined by host. But what if manual configuration configured an IPv6 address and maybe, also the prefix, but forgot to configure prefix length. Then this manual configuration has no means to determine what's on-link for a destination based on the data from manual configuration. I have host not assuming a default prefix length yet. The RA has been explicitly ignored. So not this host has no choice but to send non-link-local traffic to the default router. Specifying manual configuration behavior and its interaction with RA is a can of worms that will take time to clear up.</FONT></SPAN></P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Can you manually configure prefix on a host without also specifying prefix length?</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Stig</FONT></SPAN>
</P>

<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Hemant</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; - Ralph</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; </FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; --------------------------------------------------------------------</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; IETF IPv6 working group mailing list</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; ipv6@ietf.org</FONT></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; Administrative Requests: </FONT></SPAN><A HREF="https://www1.ietf.org/mailman/listinfo/ipv6"><SPAN LANG="en-us"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">https://www1.ietf.org/mailman/listinfo/ipv6</FONT></U></SPAN></A><SPAN LANG="en-us"></SPAN>

<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">&gt; --------------------------------------------------------------------</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7BA6D.EF8639B8--


--===============0659278677==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0659278677==--




From ipv6-bounces@ietf.org Fri Jun 29 13:05:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JuA-0005tq-D9; Fri, 29 Jun 2007 13:05:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Ju7-0005mA-Qh
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:05:07 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4JrK-00044B-Rh
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:02:26 -0400
Received: from andrew-vpn.int.libertyrms.com ([10.1.7.6] helo=trilby.local)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1I4JrK-0007Rl-DC
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:02:14 -0400
Received: by trilby.local (Postfix, from userid 1019)
	id CAA52336C28; Fri, 29 Jun 2007 13:02:19 -0400 (EDT)
Date: Fri, 29 Jun 2007 13:02:19 -0400
From: Andrew Sullivan <andrew@ca.afilias.info>
To: ipv6@ietf.org
Message-ID: <20070629170219.GB29225@afilias.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.13 (2006-08-11)
X-SA-Exim-Mail-From: andrew@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: review of draft-ietf-ipv6-deprecate-rh0-01
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dear colleagues,

I have read draft-ietf-ipv6-deprecate-rh0-01.  I think it is a useful
document, and support its promotion.  

I appreciate the view, expressed by some in earlier threads, that
deprecating RH0 completely means that legitimate uses might be lost.
I am persuaded by the argument that complete deprecation, and
replacement with something else that doesn't have the same
liabilities, is much clearer for operators and implementors alike.

In the draft, I am especially pleased to see section 4.2, which
cautions against being too broad in blocking traffic on the basis of
any routing headers.  

I do not have any editorial remarks.

I think this is a good draft, and it should proceed.

Best regards,
Andrew 

-- 
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<andrew@ca.afilias.info>                              M2P 2A8
jabber: ajsaf@jabber.org                 +1 416 646 3304 x4110

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 13:05:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ju9-0005sc-JI; Fri, 29 Jun 2007 13:05:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Ju7-0005mA-03
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:05:07 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Jre-00049Z-0X
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:02:46 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 13:02:33 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAI7YhEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="64023356:sNHT50894864"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TH2XLG001307; 
	Fri, 29 Jun 2007 13:02:33 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TH2T6o006286; 
	Fri, 29 Jun 2007 17:02:38 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 13:02:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Date: Fri, 29 Jun 2007 13:02:27 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0351DE48@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <0FF50CE9-6CC9-4AE8-8F1E-0A90C818FBF2@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-wbeebee-nd-implementation-pitfalls-00 with
	urgent	changessuggested to 2462bis-08
Thread-Index: Ace6Z3D2LBp4dO3vQHWu7iWWVadhSgABoZ1A
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03468BF6@xmb-rtp-20e.amer.cisco.com>	<467BD7FC.1030405@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C0B99@xmb-rtp-20e.amer.cisco.com>	<467BDEE5.30807@gmail.com>	<457986AF-EB39-4C6F-BB01-B9C268769450@cisco.com>	<467F62DA.2010802@gmail.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1164@xmb-rtp-20e.amer.cisco.com>	<m2645chx46.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C13DD@xmb-rtp-20e.amer.cisco.com>	<m1tzsvqxgs.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C15E3@xmb-rtp-20e.amer.cisco.com>	<m2d4zihj67.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1652@xmb-rtp-20e.amer.cisco.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D034C1844@xmb-rtp-20e.amer.cisco.com>	<6898F6E5-F609-49D0-9D04-A3B102F892AA@cisco.com>	<m1ps3gpsmm.wl%jinmei@isl.rdc.toshiba.co.jp>	<A4A43025-30D1-49A3-96BB-B4CE63044E79@ci
	sco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0351DD6B@xmb-rtp-20e.amer.cisco.com>
	<46852B09.8020505@uninett.no> <0FF5
	0CE9-6CC9-4AE8-8F1E-0A90C818FBF2@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>,
	"Stig Venaas" <stig.venaas@uninett.no>
X-OriginalArrivalTime: 29 Jun 2007 17:02:28.0185 (UTC)
	FILETIME=[45FF6490:01C7BA6F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6155; t=1183136553;
	x=1184000553; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20draft-wbeebee-nd-implementation-pitfalls-00=20with=20
	urgent=09changessuggested=20to=202462bis-08 |Sender:=20
	|To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>,
	=0A=20=20=20=2
	0=20=20=20=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>;
	bh=dPnUrvrzFAMjKMh2fMq89lNEFJxLKg8DUyHySVm1MEg=;
	b=J4D7PiAQN/GSAnlir9yGgYWBQ2CPveqxgJtaqIucvxAQGR3d/7zuK7CAfW5ZGXh60G5OIYzm
	vsNhVralwqpd5mu9uSNeOTaaYfSLlG5z87v6bJ1XeTLJLW8v72ryInys;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>,
	=?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: draft-wbeebee-nd-implementation-pitfalls-00 with
	urgent	changessuggested to 2462bis-08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

 -----Original Message-----
From: Ralph Droms (rdroms) 
Sent: Friday, June 29, 2007 12:06 PM
To: Stig Venaas
Cc: Hemant Singh (shemant); JINMEI Tatuya / ????; IETF Mailing List IPv6
Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with urgent changessuggested to 2462bis-08

Hemant - does RFC 2461 allow a host to ignore the PIOs in RAs?

<hs> Not that I know of.

Stig - you wrote "At least as a sysadmin/user I would find it confusing if the prefix length I configured would not be used for on- link determination. I think it's more bad than good to try to separate the two. I'm happy the way it currently is on the systems I've seen."  I can understand that it should be possible to manually configure on-link prefix information.  I question whether that configuration should be conceptually tied with address assignment because of the design of IPv6, or do we mix address assignment with prefix information because that's the way it was done in IPv4?

Looking back to the definition of DHCPv6 - we received a lot of input that DHCPv6 should *not* include information about default routers and on-link prefixes, because that information comes from RAs.  That argument made sense to me at the time; makes sense to me in the case of manual address assignment, too...

<hs> Sure thing. But how does a sys admin who is configuring IPv6 manually on a host know what has RA sent to the host to match setting on the host with the RA? Is it the same admin who also has access to the IPv6 default router for this host in which case the admin know how has ND and RA been configured on the router.  Even if admin knows how is RA configured on router, the admin can fat-finger the default prefix and prefix length during manual configuration. Or of admin doesn't have access to the router's config, the admin has to sniff RA in the network and see what PIO has been sent etc. This seems like a process prone to errors.

Hemant

- Ralph


On Jun 29, 2007, at Jun 29, 2007,11:53 AM, Stig Venaas wrote:

> Hemant Singh (shemant) wrote:
>> Please see in line below with "<hs>"
>>
>> -----Original Message-----
>> From: Ralph Droms (rdroms)
>> Sent: Friday, June 29, 2007 10:26 AM
>> To: JINMEI Tatuya / ????
>> Cc: IETF Mailing List IPv6; Wes Beebee (wbeebee); Hemant Singh  
>> (shemant)
>> Subject: Re: draft-wbeebee-nd-implementation-pitfalls-00 with  
>> urgent changessuggested to 2462bis-08
>>
>>
>> On Jun 28, 2007, at Jun 28, 2007,1:14 AM, JINMEI Tatuya / $B?@(J 
>> $BL@C#:H(J
>> wrote:
>>
>>> At Wed, 27 Jun 2007 14:27:37 -0400,
>>> Ralph Droms <rdroms@cisco.com> wrote:
>>>
>>>> One bug that may or may not be common is to make assumptions about
>>>> the prefixes on a link based on addresses assigned to an interface.
>>>> I can imagine (and I believe we've actually made a real sighting of
>>>> this scenario) that an IPv6 implementor might extrapolate IPv4
>>>> conventions and extract the /64 prefix from an assigned address
>>>> (either SLAAC, DHCP or manual config), and add a route to the host
>>>> table indicating that the prefix is on-link, regardless of whether
>>>> the prefix is advertised as "on-link" in an RA.
>>> [...]
>>>
>>> If the system administrator manually configures an IPv6 address  
>>> with a
>>> prefix length smaller than 128, the kernel will assume that the
>>> corresponding prefix is on-link.  But I believe this should be
>>> reasonable.
>>>
>>> 					JINMEI, Tatuya
>>> 					Communication Platform Lab.
>>> 					Corporate R&D Center, Toshiba Corp.
>>> 					jinmei@isl.rdc.toshiba.co.jp
>>
>> I see where draft-wbeebee-nd-implementation-pitfalls also mentions  
>> manual configuration as a special case:
>>
>>     2.  The RA and ICMPv6 Redirects from the default router are  
>> the only
>>         sources of information for on-link determination.  DHCPv6  
>> or any
>>         other configuration on the host MUST NOT be used for on-link
>>         determination.  Manual configuration of a host introduces  
>> its own
>>         set of security considerations and is beyond the scope of  
>> this
>>         document.
>>
>> Is there some reason to believe the information about on-link  
>> prefixes should be implicitly overridden in the case of manual  
>> address assignment?  I can understand explicitly overriding  
>> information from RAs by manually configuring the on-link  
>> information as a separate step from manual address assignment.   
>> But it seems to me that assuming the prefix from a manually  
>> configured address is on- link might cause unexpected loss of  
>> connectivity if the prefix does require off-link delivery through  
>> the router.
>
> At least as a sysadmin/user I would find it confusing if the prefix
> length I configured would not be used for on-link determination.
>
> I think it's more bad than good to try to separate the two. I'm
> happy the way it currently is on the systems I've seen.
>
>>
>> <hs> If the host has been manually configured for IPv6 address  
>> where the host was also configured for prefix and prefix length,  
>> then what's on-link for this host can be determined by host. But  
>> what if manual configuration configured an IPv6 address and maybe,  
>> also the prefix, but forgot to configure prefix length. Then this  
>> manual configuration has no means to determine what's on-link for  
>> a destination based on the data from manual configuration. I have  
>> host not assuming a default prefix length yet. The RA has been  
>> explicitly ignored. So not this host has no choice but to send non- 
>> link-local traffic to the default router. Specifying manual  
>> configuration behavior and its interaction with RA is a can of  
>> worms that will take time to clear up.
>
> Can you manually configure prefix on a host without also specifying
> prefix length?
>
> Stig
>
>>
>> Hemant
>>
>> - Ralph
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 13:42:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4KTq-0006i6-2S; Fri, 29 Jun 2007 13:42:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4KTn-0006hw-R1
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:41:59 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4KTn-0002Fk-Kn
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:41:59 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1I4KTN-0000Xe-Ta
	for ipv6@ietf.org; Fri, 29 Jun 2007 13:41:33 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Fri, 29 Jun 2007 13:41:33 -0400 (EDT)
Message-ID: <62706.74.122.168.81.1183138893.squirrel@look.libertyrms.com>
Date: Fri, 29 Jun 2007 13:41:33 -0400 (EDT)
From: briand@ca.afilias.info
To: ipv6@ietf.org
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

(Yes, it's my first post, but I thought it would be good to establish early
on a track record of keeping on-topic and moving things in a positive
direction...)

I've read the draft, and the CanSecWest slides that it references.
The network nodes I've worked on have deployed filters to prevent RH0
attacks.

And I feel that the draft meets all the appropriate criteria.

I support moving it to RFC status.

Brian Dickson


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 14:47:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4LVK-0003sY-1N; Fri, 29 Jun 2007 14:47:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4LVI-0003gt-ON
	for ipv6@ietf.org; Fri, 29 Jun 2007 14:47:36 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4LVI-0006da-CT
	for ipv6@ietf.org; Fri, 29 Jun 2007 14:47:36 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1I4LUt-0003Rl-UN
	for ipv6@ietf.org; Fri, 29 Jun 2007 14:47:11 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Fri, 29 Jun 2007 14:47:11 -0400 (EDT)
Message-ID: <62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
In-Reply-To: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
References: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
Date: Fri, 29 Jun 2007 14:47:11 -0400 (EDT)
From: briand@ca.afilias.info
To: ipv6@ietf.org
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Date: Fri, 29 Jun 2007 15:57:29 +0000
> From: Paul Vixie <paul@vix.com>
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
> To: ipv6@ietf.org
> Message-ID: <30910.1183132649@sa.vix.com>
>
>> So, IMHO it would be premature to turn over address
>> delegation authority at this time.
>
> then let's keep going.

My apologies for joining the discussion a bit late, but I hadn't been aware
of the issue until recently (the issue of ULA, let alone ULA-C draft(s)).

I'm coming to this from the perspective of someone with an operational slant,
albeit with an interest in keeping IPv6 from suffering some of the avoidable
problems in IPv4 that originated in "historical" use and our collective
lack of adequate experience suffering the pain that making these errors
caused. Not the pain of a body blow, but of a thousand (or 270K) paper cuts.

I think that UCA and UCA-C is a clever technical solution to a problem that
exists primarily in the political/financial area, and which does not even
have a good reason for existing.

I'll summarize what I think the issues are, how I think they should best
be addressed, and what the ideal-world order of events would be, and even
what ultimately should happen regarding ULA and ULA-C.

I think that ULA has come about as an answer to the need for IPv6 space,
which does not have procedural overhead or cost (both of which occur when
requesting space from RIRs).

Additionally, I believe that there exist RIR policies which are resulting
in some pressure towards implementing ULA/ULA-C -- policies which can and
should be modified by the membership constituency of the RIRs.

ULA-C is an interesting middle ground, but the mere existence of ULA-C
as a concept, and as a draft that we're discussing, is a strong indicator
that these RIR policies are a problem. And moreover, as a compromise,
ULA-C is causing more harm than good.

The requirements that I see ULA/ULA-C addressing are:
- need for IPv6 space
- need for this space to be globally unique
- need for this space to be easily acquired
- need for this space to be acquired for no cost
- need for the status of this space to be easily identifyable (DFZ or not)

All but the last issue, are trivially manageable by relaxing the existing
requirements in place at the RIRs, for acquiring space. The basic policy
requirements for space should be relaxed considerably, insofar as IPv6
blocks being globally announced, justified, and paid for. The argument
about space exhaustion is trivially countered by making changes to the
smallest block of PI space that is directly allocated by RIRs - e.g. to
a minimum of /64, or even /56.

The last item is IMHO, something that can be managed by a relatively small
change to places where allocations/assignments are handled, e.g. whois or
RADB type places -- support the addition of a "Local" flag, something which
is entirely voluntary, and whose use for filtering is similarly voluntary.

I submit the following as being valid assertions:
(A) If enough members push for these changes in their RIRs, the changes
will happen
(B) If the changes happen, the specific and explicit need for ULA/ULA-C
goes away
(C) Depracating ULA/ULA-C would then be the most appropriate next step
(D) Elimination of most of the major (and to some degree, "alien")
elements of IPv6 will go a long, long way towards getting IPv6 deployed,
including:
  (1) vendor support
  (2) scalable hardware support for IPv6 mandatory elements
  (3) network operator deployment
  (4) Host O/S and infrastructure deployment (e.g. DNS)

Oddly enough, what I recommend for now is - put ULA-C on the back burner.
Make travel plans to attend the next IANA meeting, and in the meantime, join
the IANA mailing lists. Voice your concern over PI space issues, and the
making available of small PI blocks to all comers.

What I advocate in the IANA world is, of course, that everyone who has a
reason to have a routing policy that differs from their upstream, be
allowed to get one PI block for every place that they are unable to
aggregate within a larger block (i.e. where topology requires that they
announce different prefixes). And, additionally, that as many PI blocks
for "ULA" use as an organization wants, be allocated.

Making PI blocks move from "ULA" to "DFZ" status, is strictly something
that the RIRs need to address from a membership and fee perspective, as
well as policy basis.
I would encourage that policies be adopted where only failure to renumber
and aggregate, where such renumbering and aggregation would not impose
harm, have any cost penalty associated with them.

"Harm" here would be: a requirement to then deaggregate. I.e. where the
result of topological merger means that the resulting network naturally
would have been able to be implemented with a single prefix.

Basically, if you take two networks, each with its own PI block, one of
which was not previously in the DFZ, and merge them and announce both
blocks, you should not be penalized if they are fundamentally not able to
be aggregated by any means of renumbering (such as not being contiguous).
And on the other hand, if you *could* aggregate by renumbering, that you
be given a disincentive to not renumber.

Keep in mind, folks, that renumbering no longer has to be an atomic event,
in any sense of the word. Even at the host and interface level, IPv6
expects there to be multiple IPv6 addresses, including link-local. So,
having yet another address does not seriously constitute a major PITA, and
renumbering can be done by anyone on any timeframe they like.

Globally unique PI blocks - one to an ASN, please; no deaggregation,
please; use them however you want, just tell others if you intend them to
be in the DFZ or not.

Is this not a reasonable and modest proposition?

Brian Dickson


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 16:24:38 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4N0y-0006jS-C8; Fri, 29 Jun 2007 16:24:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4N0x-0006jM-4M
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:24:23 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4N0X-0004Db-8r
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:24:23 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5D6E711431
	for <ipv6@ietf.org>; Fri, 29 Jun 2007 20:23:54 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Fri, 29 Jun 2007 14:47:11 -0400."
	<62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com> 
References: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
	<62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 29 Jun 2007 20:23:54 +0000
Message-ID: <70355.1183148634@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> >> So, IMHO it would be premature to turn over address
> >> delegation authority at this time.
> >
> > then let's keep going.
> 
> My apologies for joining the discussion a bit late, ...

no problem.

> I think that UCA and UCA-C is a clever technical solution to a problem that
> exists primarily in the political/financial area, and which does not even
> have a good reason for existing.

for context, most of the people i've seen discuss this topic think that ULA
(and -C) are ugly technical solutions made necessary by the lack of an id/loc
(identifier/locator) split in the internet's architecture, as exacerbated by
moore's law and peering economics.

> I think that ULA has come about as an answer to the need for IPv6 space,
> which does not have procedural overhead or cost (both of which occur when
> requesting space from RIRs).

then you are factually wrong at the outset.  but let's see what we can make.

> Additionally, I believe that there exist RIR policies which are resulting
> in some pressure towards implementing ULA/ULA-C -- policies which can and
> should be modified by the membership constituency of the RIRs.

on this, there is broad agreement, but the outcome has been to request that
IANA (by way of an IETF specification) set aside some non-DFZ space so that
RIRs can hand it out for non-DFZ use with a lower barrier to acquisition.

> ULA-C is an interesting middle ground, but the mere existence of ULA-C as a
> concept, and as a draft that we're discussing, is a strong indicator that
> these RIR policies are a problem.  And moreover, as a compromise, ULA-C is
> causing more harm than good.

obligatory disclaimer: while i'm not speaking for ARIN here, i am a member of
ARIN's board of trustees, and i have not set ARIN's interests aside for the
purpose of pure academic debate.  and briefly, as a trustee for this sentence
alone, let me point out that ARIN's policies are set by the community and if
you think those policies are "a problem" you should join ppml@arin.net and
also attend ARIN meetings and consider submitting some policy proposals to
change them.

> The requirements that I see ULA/ULA-C addressing are:
> - need for IPv6 space
> - need for this space to be globally unique
> - need for this space to be easily acquired
> - need for this space to be acquired for no cost
> - need for the status of this space to be easily identifyable (DFZ or not)

others see additional requirements.  for example, the need for global WHOIS,
global DNS, and global RPKI support for ULA space, so that even in ad-hoc
networking environments, "recourse" will be possible against malefactors.  as
a result of that requirement, a role for the regional internet registries,
and a fee level set at the cost recovery level for efficient not-for-profit
operations, has been strongly suggested.

(don't think that your own requirements aren't relevant or that your
description of them is unappreciated, but the resulting specification if
any will include a larger set of requirements and features than any one
person is likely to have, and is likely to be seen as a compromise by most
if not all of us.)

> All but the last issue, are trivially manageable by relaxing the existing
> requirements in place at the RIRs, for acquiring space.  [...]

as before, if you think that the existing RIR policies are wrong, there's a
mechanism in place in every region for improving those policies.  one thing
to add at this point: IETF is not where RIR policies are made or changed.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 16:37:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4NDR-0007VM-0n; Fri, 29 Jun 2007 16:37:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NDP-0007VE-Hj
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:37:15 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4NDP-0004xs-9e
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:37:15 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 2543F1A4D87; Fri, 29 Jun 2007 13:36:45 -0700 (PDT)
Date: Fri, 29 Jun 2007 13:36:45 -0700
From: bill fumerola <billf@mu.org>
To: ipv6@ietf.org
Message-ID: <20070629203645.GB7228@elvis.mu.org>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13846.1183003509@sa.vix.com>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: 
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, Jun 28, 2007 at 04:05:09AM +0000, Paul Vixie wrote:
> these are my comments on the following I-D:
[....]
> should be replaced with this one:
> 
>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
>       +--------+-+----------+---------+---------+----------+
>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
>       +--------+-+----------+---------+---------+----------+
[....]
> ---
> 
> 7.0 IANA Considerations
> 
>     IANA is hereby instructed to reserve address block FC::/7 for private
>     unique addresses, and to allocate /32 blocks to Regional Internet 
>     Address Registries (RIRs) who request same after adopting policies
>     consistent with this specification.  Allocation shall be similar in
>     all ways to normal IANA address allocation to RIRs, including but not
>     limited to IN-ADDR.ARPA delegations and WHOIS records.
> 

i think this is both an intelligent allocation strategy and am in favor
of this direction given to IANA. both good modifications.

-- bill

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 16:42:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4NIi-0002DX-Kk; Fri, 29 Jun 2007 16:42:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NIh-0002DQ-Fn
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:42:43 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4NIh-0005Dp-7k
	for ipv6@ietf.org; Fri, 29 Jun 2007 16:42:43 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 759A01A4D87; Fri, 29 Jun 2007 13:42:45 -0700 (PDT)
Date: Fri, 29 Jun 2007 13:42:45 -0700
From: bill fumerola <billf@mu.org>
To: Mark Andrews <Mark_Andrews@isc.org>
Message-ID: <20070629204245.GC7228@elvis.mu.org>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070BD@mail>
	<200706290333.l5T3XT31048006@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200706290333.l5T3XT31048006@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, Jun 29, 2007 at 01:33:29PM +1000, Mark Andrews wrote:
> 	It really should be up to the *user* of the ULA-C addresses
> 	to decide if they want to provide more than NXDOMAIN to
> 	interested parties on the Internet.  We shouldn't be
> 	arbitarially limiting functionality if it is technically
> 	possible to provide that functionality.

and this is the crux of my previous posts supporting reverse delegation
to a global unicast address. we want to provide all the possibilties
within the limit that it doesnt' interfere with Other People's Networks.

delegating reverse authority, including it in whois, allowing/including
them in radb networks are all flexible tools. no one says you have to
use them.

-- 
- bill fumerola / billf@FreeBSD.org



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 17:02:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4NbH-0006zn-6s; Fri, 29 Jun 2007 17:01:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NbF-0006xr-9j
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:01:53 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Nb8-000526-7w
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:01:53 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5TL1heV030595
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 23:01:43 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5TL1frA029947; Fri, 29 Jun 2007 23:01:42 +0200
Date: Fri, 29 Jun 2007 23:01:42 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <4684D286.8080900@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0706292300560.29317@chandra.student.uit.no>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com>
	<46838C69.3050601@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706282253070.29317@chandra.student.uit.no>
	<4684D286.8080900@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, 29 Jun 2007, Jeroen Massar wrote:
<snip>
>
> Endusers vote with their money. When a site is important enough to be
> reached, they will go to an ISP that will have access to that site and
> as such that space will be routed globally, the Internet will then
> simply change to include the other spaces.

if that happen that user should be told very clear to change to either PI 
or PA type of UA addresses...



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 17:13:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Nma-0005YP-6d; Fri, 29 Jun 2007 17:13:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NmY-0005Te-G2
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:13:34 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4NmY-0007Jj-A1
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:13:34 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85316887; Fri, 29 Jun 2007 17:13:01 -0400
Message-ID: <468575CF.4020702@internap.com>
Date: Fri, 29 Jun 2007 14:12:47 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>	<13846.1183003509@sa.vix.com>	<46838C69.3050601@spaghetti.zurich.ibm.com>	<Pine.LNX.4.64.0706282253070.29317@chandra.student.uit.no>	<4684D286.8080900@spaghetti.zurich.ibm.com>
	<Pine.LNX.4.64.0706292300560.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706292300560.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> On Fri, 29 Jun 2007, Jeroen Massar wrote:
> <snip>
>>
>> Endusers vote with their money. When a site is important enough to be
>> reached, they will go to an ISP that will have access to that site and
>> as such that space will be routed globally, the Internet will then
>> simply change to include the other spaces.

Jeroen,

Do you think that a site would try to connect to the Internet with 
*just* ULA addresses?  I would think that any responsible site operator 
would recognize that ULA addresses are not globally routable, and would 
give his global services PA or PI addresses as well.  In IPv6 it's easy 
to assign multiple IPs or subnets, so if I were a site using ULA-C 
addresses and wanted to offer services to the entire Internet, I would 
allocate my servers IPs from each of my providers' PA blocks for global 
reachability, and perhaps keep ULA-C for address consistency with my 
internal systems and that of any private partners I share ULA-C routes with.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 17:23:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Nvh-0000wO-Pj; Fri, 29 Jun 2007 17:23:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Nvg-0000w5-Bj
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:23:00 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4Nv6-0002mt-ED
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:23:00 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1I4Nv6-000122-4E
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:22:24 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Fri, 29 Jun 2007 17:22:24 -0400 (EDT)
Message-ID: <62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
In-Reply-To: <E1I4NDR-0007VX-QU@megatron.ietf.org>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
Date: Fri, 29 Jun 2007 17:22:24 -0400 (EDT)
From: briand@ca.afilias.info
To: ipv6@ietf.org
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Date: Fri, 29 Jun 2007 20:23:54 +0000
> From: Paul Vixie <paul@vix.com>
> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
> To: ipv6@ietf.org
> Message-ID: <70355.1183148634@sa.vix.com>
>
>> Additionally, I believe that there exist RIR policies which are
>> resulting
>> in some pressure towards implementing ULA/ULA-C -- policies which can
>> and
>> should be modified by the membership constituency of the RIRs.
>
> on this, there is broad agreement, but the outcome has been to request
> that
> IANA (by way of an IETF specification) set aside some non-DFZ space so
> that
> RIRs can hand it out for non-DFZ use with a lower barrier to acquisition.

(*) See below at the bottom - I believe there are two contradictory
statements (unless publishing an RFC which requests that an RIR do
some particular thing, does not constitute "setting RIR policy".)

>> ULA-C is an interesting middle ground, but the mere existence of ULA-C
>> as a
>> concept, and as a draft that we're discussing, is a strong indicator
>> that
>> these RIR policies are a problem.  And moreover, as a compromise, ULA-C
>> is
>> causing more harm than good.
>
> obligatory disclaimer: while i'm not speaking for ARIN here, i am a member
> of
> ARIN's board of trustees, and i have not set ARIN's interests aside for
> the
> purpose of pure academic debate.  and briefly, as a trustee for this
> sentence
> alone, let me point out that ARIN's policies are set by the community and
> if
> you think those policies are "a problem" you should join ppml@arin.net and
> also attend ARIN meetings and consider submitting some policy proposals to
> change them.

Don't worry - those are already things I'm planning on doing.
(Thanks for the mailing list pointer - it saves me a bit of searching. ;-)).

And thanks for pointing out the ARIN meta-policy - I don't think enough
people understand that. Shouting over the wall pretty much by definition
does not constitute submitting proposals. :-)

And the reason I brought up the issue, and made the proposal, is for that
exact reason. If any of what I said made any sense, then anyone who has
reason to support those suggestions would probably be best served by also
joining in on this ARIN pariticipation activity, in a very concrete way.

I think that more "bridging the gap" between operators, policy makers,
and (<insert label for IETF here>) everyone else, needs to occur. It's bad
enough that vendors making hardware are so far behind the curve...

I also think that it's just a question of realizing that ARIN is part of
the community, part of the process, and that not participating means
not having visibility or input into things that can affect your network,
further down the road...
(end of plug for civic duties)

>> The requirements that I see ULA/ULA-C addressing are:
>> - need for IPv6 space
>> - need for this space to be globally unique
>> - need for this space to be easily acquired
>> - need for this space to be acquired for no cost
>> - need for the status of this space to be easily identifyable (DFZ or
>> not)
>
> others see additional requirements.  for example, the need for global
> WHOIS,
> global DNS, and global RPKI support for ULA space, so that even in ad-hoc
> networking environments, "recourse" will be possible against malefactors.
> as
> a result of that requirement, a role for the regional internet registries,
> and a fee level set at the cost recovery level for efficient
> not-for-profit
> operations, has been strongly suggested.

I don't disagree with any of the stuff that follows "as a result".
I in fact agree that there is a reasonable basis for doing so which
pretty much stands by itself, without needing any support from anyone.

Please answer me this, however (anyone, not just Paul):
- of the additional requirements listed, which of those are not available
(e.g. automatically) for PI allocations in the DFZ?

What I'm asking, of course, is this:
Is there *anything* unique to ULA that is not possible to implement with
PI allocations by RIRs?

And if so, why would it not be something to add on to every PI allocation?

(I do profess ignorance RPKI; I'm pretty sure that WHOIS and DNS are part
of the DFZ :-)).

> (don't think that your own requirements aren't relevant or that your
> description of them is unappreciated, but the resulting specification if
> any will include a larger set of requirements and features than any one
> person is likely to have, and is likely to be seen as a compromise by most
> if not all of us.)
>
>> All but the last issue, are trivially manageable by relaxing the
>> existing
>> requirements in place at the RIRs, for acquiring space.  [...]
>
> as before, if you think that the existing RIR policies are wrong, there's
> a
> mechanism in place in every region for improving those policies.  one
> thing
> to add at this point: IETF is not where RIR policies are made or changed.

(*) Second part of same comment from above - if the IETF publishes an RFC,
requesting that RIRs do some particular thing on a systematic basis, is
that not in effect dictating (in a passive-aggressive manner) policy to
RIRs?

I do understand the difference between requesting something of RIRs, and
telling them to do something, but fundamentally, either the RIRs do what
is asked in the RFC, or they do not. If they do not, the whole RFC is
mooted. If they do, then they have made a policy change at the behest of
the IETF.

Either way, this begs the question - how is what I was suggesting, other
than in the sense that I did not couch my suggestion as "ask nicely",
any different than ULA-C?

As far as I can tell, the main differences have to do with ULA itself,
the fact that the allocations are from a single block, and that the single
block has associated with it some rather nasty mandatory extra bits.

(Yes, I know I'm being a bit facetious - and deliberately - but the
question isn't entirely rhetorical. If the suggestion were couched the
same way as the ULA-C proposal, would it be considered acceptable from the
ARIN perspective?)

Brian


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 17:44:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4OGW-0005SB-Qw; Fri, 29 Jun 2007 17:44:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4OGW-0005S0-0d
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:44:32 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4OFP-0000KS-LR
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:44:31 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85319004; Fri, 29 Jun 2007 17:43:22 -0400
Message-ID: <46857CEB.1040100@internap.com>
Date: Fri, 29 Jun 2007 14:43:07 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: briand@ca.afilias.info
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
In-Reply-To: <62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian,

I won't try to reply inline, but let me address your questions more 
generally:

With regards to the relationship between RFCs and RIR policy, my 
understanding is that RFCs more or less direct IANA how to go about 
giving out space to the RIRs.  However, each RIR can decide for itself 
whether it wants to participate in the allocation of a certain type of 
IP space.  Right now, not all RIRs support IPv6 PI space, and it would 
similarly require policy for each RIR to begin assigning or allocating 
ULA-C space.  In addition, this is not just a binary decision: an RIR 
could decide it wanted to do direct ULA-C assignments, and/or it could 
decide to do ULA-C allocations to LIRs.  The RFC sets general direction, 
but leaves it up to the RIRs (and to some extent even to IANA) how the 
space is actually given out.

With regards to the oft-repeated question of "Is there *anything* unique 
to ULA that is not possible to implement with
PI allocations by RIRs?": In theory, no, but in practice, yes.  ("In 
theory, theory and practice are the same, but in practice, they're 
not.")  If/when it becomes feasible for RIRs to give out PI space to 
anyone who asks, without concern over whether that space will end up in 
the routing tables of every full-BGP-feed router on the planet, then PI 
would meet the same need as ULA-C.  Until then, ULA-C allows us to 
allocate space to networks who don't need to announce it to their 
transit providers, but who would still like to be able to privately 
interconnect with other networks using their own unique, registered IP 
space.

Hope that clarifies things a bit, and I look forward to seeing you on PPML.

-Scott

briand@ca.afilias.info wrote:
>> Date: Fri, 29 Jun 2007 20:23:54 +0000
>> From: Paul Vixie <paul@vix.com>
>> Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
>> To: ipv6@ietf.org
>> Message-ID: <70355.1183148634@sa.vix.com>
>>
>>     
>>> Additionally, I believe that there exist RIR policies which are
>>> resulting
>>> in some pressure towards implementing ULA/ULA-C -- policies which can
>>> and
>>> should be modified by the membership constituency of the RIRs.
>>>       
>> on this, there is broad agreement, but the outcome has been to request
>> that
>> IANA (by way of an IETF specification) set aside some non-DFZ space so
>> that
>> RIRs can hand it out for non-DFZ use with a lower barrier to acquisition.
>>     
>
> (*) See below at the bottom - I believe there are two contradictory
> statements (unless publishing an RFC which requests that an RIR do
> some particular thing, does not constitute "setting RIR policy".)
>
>   
>>> ULA-C is an interesting middle ground, but the mere existence of ULA-C
>>> as a
>>> concept, and as a draft that we're discussing, is a strong indicator
>>> that
>>> these RIR policies are a problem.  And moreover, as a compromise, ULA-C
>>> is
>>> causing more harm than good.
>>>       
>> obligatory disclaimer: while i'm not speaking for ARIN here, i am a member
>> of
>> ARIN's board of trustees, and i have not set ARIN's interests aside for
>> the
>> purpose of pure academic debate.  and briefly, as a trustee for this
>> sentence
>> alone, let me point out that ARIN's policies are set by the community and
>> if
>> you think those policies are "a problem" you should join ppml@arin.net and
>> also attend ARIN meetings and consider submitting some policy proposals to
>> change them.
>>     
>
> Don't worry - those are already things I'm planning on doing.
> (Thanks for the mailing list pointer - it saves me a bit of searching. ;-)).
>
> And thanks for pointing out the ARIN meta-policy - I don't think enough
> people understand that. Shouting over the wall pretty much by definition
> does not constitute submitting proposals. :-)
>
> And the reason I brought up the issue, and made the proposal, is for that
> exact reason. If any of what I said made any sense, then anyone who has
> reason to support those suggestions would probably be best served by also
> joining in on this ARIN pariticipation activity, in a very concrete way.
>
> I think that more "bridging the gap" between operators, policy makers,
> and (<insert label for IETF here>) everyone else, needs to occur. It's bad
> enough that vendors making hardware are so far behind the curve...
>
> I also think that it's just a question of realizing that ARIN is part of
> the community, part of the process, and that not participating means
> not having visibility or input into things that can affect your network,
> further down the road...
> (end of plug for civic duties)
>
>   
>>> The requirements that I see ULA/ULA-C addressing are:
>>> - need for IPv6 space
>>> - need for this space to be globally unique
>>> - need for this space to be easily acquired
>>> - need for this space to be acquired for no cost
>>> - need for the status of this space to be easily identifyable (DFZ or
>>> not)
>>>       
>> others see additional requirements.  for example, the need for global
>> WHOIS,
>> global DNS, and global RPKI support for ULA space, so that even in ad-hoc
>> networking environments, "recourse" will be possible against malefactors.
>> as
>> a result of that requirement, a role for the regional internet registries,
>> and a fee level set at the cost recovery level for efficient
>> not-for-profit
>> operations, has been strongly suggested.
>>     
>
> I don't disagree with any of the stuff that follows "as a result".
> I in fact agree that there is a reasonable basis for doing so which
> pretty much stands by itself, without needing any support from anyone.
>
> Please answer me this, however (anyone, not just Paul):
> - of the additional requirements listed, which of those are not available
> (e.g. automatically) for PI allocations in the DFZ?
>
> What I'm asking, of course, is this:
> Is there *anything* unique to ULA that is not possible to implement with
> PI allocations by RIRs?
>
> And if so, why would it not be something to add on to every PI allocation?
>
> (I do profess ignorance RPKI; I'm pretty sure that WHOIS and DNS are part
> of the DFZ :-)).
>
>   
>> (don't think that your own requirements aren't relevant or that your
>> description of them is unappreciated, but the resulting specification if
>> any will include a larger set of requirements and features than any one
>> person is likely to have, and is likely to be seen as a compromise by most
>> if not all of us.)
>>
>>     
>>> All but the last issue, are trivially manageable by relaxing the
>>> existing
>>> requirements in place at the RIRs, for acquiring space.  [...]
>>>       
>> as before, if you think that the existing RIR policies are wrong, there's
>> a
>> mechanism in place in every region for improving those policies.  one
>> thing
>> to add at this point: IETF is not where RIR policies are made or changed.
>>     
>
> (*) Second part of same comment from above - if the IETF publishes an RFC,
> requesting that RIRs do some particular thing on a systematic basis, is
> that not in effect dictating (in a passive-aggressive manner) policy to
> RIRs?
>
> I do understand the difference between requesting something of RIRs, and
> telling them to do something, but fundamentally, either the RIRs do what
> is asked in the RFC, or they do not. If they do not, the whole RFC is
> mooted. If they do, then they have made a policy change at the behest of
> the IETF.
>
> Either way, this begs the question - how is what I was suggesting, other
> than in the sense that I did not couch my suggestion as "ask nicely",
> any different than ULA-C?
>
> As far as I can tell, the main differences have to do with ULA itself,
> the fact that the allocations are from a single block, and that the single
> block has associated with it some rather nasty mandatory extra bits.
>
> (Yes, I know I'm being a bit facetious - and deliberately - but the
> question isn't entirely rhetorical. If the suggestion were couched the
> same way as the ULA-C proposal, would it be considered acceptable from the
> ARIN perspective?)
>
> Brian
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>   

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 17:58:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4OUA-0008F3-Fr; Fri, 29 Jun 2007 17:58:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4OU9-0008Ex-83
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:58:37 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4OU8-0001UM-PQ
	for ipv6@ietf.org; Fri, 29 Jun 2007 17:58:37 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5TLvhpm071972
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 23:57:44 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5TLvgxR032099; Fri, 29 Jun 2007 23:57:42 +0200
Date: Fri, 29 Jun 2007 23:57:42 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: briand@ca.afilias.info
In-Reply-To: <62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
Message-ID: <Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.4.252
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, 29 Jun 2007, briand@ca.afilias.info wrote:
> What I'm asking, of course, is this:
> Is there *anything* unique to ULA that is not possible to implement with
> PI allocations by RIRs?

not really no. Except that real end-users like your brother can get ULA-C 
cheap but maybe have to pay a bit more for PI.


> And if so, why would it not be something to add on to every PI allocation?

you mean automaticly add ULA-C to each PI allocation? Sure why not, but 
that will be upto the RIRs to decide as I see it.




-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 18:05:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Oaa-00079u-JD; Fri, 29 Jun 2007 18:05:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4OaY-0006xG-Mx
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:05:14 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4OaT-0000dr-HH
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:05:14 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85320053; Fri, 29 Jun 2007 18:05:09 -0400
Message-ID: <4685820C.4020408@internap.com>
Date: Fri, 29 Jun 2007 15:05:00 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Roger Jorgensen <rogerj@jorgensen.no>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: briand@ca.afilias.info, ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Roger Jorgensen wrote:
> On Fri, 29 Jun 2007, briand@ca.afilias.info wrote:
>> What I'm asking, of course, is this:
>> Is there *anything* unique to ULA that is not possible to implement with
>> PI allocations by RIRs?
>
> not really no. Except that real end-users like your brother can get 
> ULA-C cheap but maybe have to pay a bit more for PI.

ULA-C and PI space will likely both cost about the same, and your 
brother could likely afford either.  The issue isn't so much dollar cost 
as availability: your brother likely doesn't qualify for PI space 
(unless he can justify efficient use of a /22), but he could get ULA-C 
just by asking.

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 18:21:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Oph-0005Cm-Vi; Fri, 29 Jun 2007 18:20:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Opg-000581-Kj
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:20:52 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Oos-0006ul-F8
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:20:52 -0400
Received: from [IPv6:2001:770:100:9e::2] (spaghetti.unfix.org
	[IPv6:2001:770:100:9e::2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: jeroen)
	by purgatory.unfix.org (Postfix) with ESMTP id 7EC47140C1E2;
	Sat, 30 Jun 2007 00:20:00 +0200 (CEST)
Message-ID: <4685858B.8040003@spaghetti.zurich.ibm.com>
Date: Fri, 29 Jun 2007 23:19:55 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.8.1.4) Gecko/20070604 Thunderbird/2.0.0.4 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Scott Leibrand <sleibrand@internap.com>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
	<4685820C.4020408@internap.com>
In-Reply-To: <4685820C.4020408@internap.com>
X-Enigmail-Version: 0.95.1
OpenPGP: id=333E7C23
X-Spam-Score: -2.3 (--)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: ipv6@ietf.org, briand@ca.afilias.info
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0521336227=="
Errors-To: ipv6-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0521336227==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig81C9CB613994D06827021810"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig81C9CB613994D06827021810
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Scott Leibrand wrote:
> Roger Jorgensen wrote:
>> On Fri, 29 Jun 2007, briand@ca.afilias.info wrote:
>>> What I'm asking, of course, is this:
>>> Is there *anything* unique to ULA that is not possible to implement w=
ith
>>> PI allocations by RIRs?
>>
>> not really no. Except that real end-users like your brother can get
>> ULA-C cheap but maybe have to pay a bit more for PI.
>=20
> ULA-C and PI space will likely both cost about the same, and your
> brother could likely afford either.  The issue isn't so much dollar cos=
t
> as availability: your brother likely doesn't qualify for PI space
> (unless he can justify efficient use of a /22), but he could get ULA-C
> just by asking.

Wow, a /22 IPv6 space, that is a big chunk. But I assume you mean /22
IPv4. What has IPv4 to do with IPv6 and moreover why is that ARIN policy
 being forced upon the IETF thus leading to ULA-C and then leading to
heavily hinting ARIN to provide ULA-C as a way out.

Clearly ULA-C is just "cheap address space", nothing more nothing less.
And the sole reason for a possible existence seems to be that the
policies in RIR land do not allow everybody to get address space the way
they want to. Instead of changing the RIR policies, ULA-C gets invented.

Which is also what you write in the 2 emails before this one, but in
between the lines.

The RIR community effectively blocks people from getting address space
on the premise that "but that costs routing slots", even though the
minimum allocation is /48 either way, and then on top of that basing
that decision on IPv4 address space usage, wow.

I think that ULA-C is a really really bad idea because of this.

But I'll let other people figure that out, I've clearly spoken my mind
about this already. I do hope that other people see this too.

Greets,
 Jeroen


--------------enig81C9CB613994D06827021810
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/

iHUEARECADUFAkaFhY8uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I3EOAKCf4idwYlwO79e6MM7dZwlohryL
WwCeMdB0viCy3Ati1p00g7b5upL9eiw=
=M1JQ
-----END PGP SIGNATURE-----

--------------enig81C9CB613994D06827021810--


--===============0521336227==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0521336227==--




From ipv6-bounces@ietf.org Fri Jun 29 18:24:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ot1-0004bt-2P; Fri, 29 Jun 2007 18:24:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Osy-0004Um-EJ
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:24:16 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4Osx-0002n1-Vo
	for ipv6@ietf.org; Fri, 29 Jun 2007 18:24:16 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux2.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l5TMNffg049503
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 30 Jun 2007 00:23:41 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l5TMNfts000831; Sat, 30 Jun 2007 00:23:41 +0200
Date: Sat, 30 Jun 2007 00:23:41 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <4685858B.8040003@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0706300021360.29317@chandra.student.uit.no>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
	<4685820C.4020408@internap.com>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.61 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, 29 Jun 2007, Jeroen Massar wrote:
<snip>
>
> I think that ULA-C is a really really bad idea because of this.
>
> But I'll let other people figure that out, I've clearly spoken my mind
> about this already. I do hope that other people see this too.

yes it is a bad idea, but for the time being, it seems to be the 
right thing. Might even be necesary for IPv6 deployment to. For us, where 
I work, ULA-C is great, it give us everything we want. PI or/and PA will 
do the same job but ULA-C is easier to use, nothing else.



-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 19:15:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Pfv-00006I-P6; Fri, 29 Jun 2007 19:14:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Pft-00005S-W7
	for ipv6@ietf.org; Fri, 29 Jun 2007 19:14:49 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4PfF-00079P-6J
	for ipv6@ietf.org; Fri, 29 Jun 2007 19:14:49 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id AD0B61A4D86; Fri, 29 Jun 2007 16:14:08 -0700 (PDT)
Date: Fri, 29 Jun 2007 16:14:08 -0700
From: bill fumerola <billf@mu.org>
To: briand@ca.afilias.info
Message-ID: <20070629231408.GA46212@elvis.mu.org>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 6.2-MUORG-20061210 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, Jun 29, 2007 at 05:22:24PM -0400, briand@ca.afilias.info wrote:
> Please answer me this, however (anyone, not just Paul):
> - of the additional requirements listed, which of those are not available
> (e.g. automatically) for PI allocations in the DFZ?
> 
> What I'm asking, of course, is this:
> Is there *anything* unique to ULA that is not possible to implement with
> PI allocations by RIRs?

AfriNIC has said they will recind PI address space that is not "announced"
within a year. you may interpret "announce" as you wish. i assume they
mean in the DFZ.

which means PI space from AfriNIC is unusable for this purpose.

-- bill

ps. i sent a lengthy mail to this list detailing this but nobody replied.
    i hope the point that just because RIRs now have PI policies that
    may allow for PI space that you don't announce, that may not always
    be the case. AfriNIC is already a counter-example. their policy may
    change too.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 19:36:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Q0v-00042G-3w; Fri, 29 Jun 2007 19:36:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Q0u-0003zb-9f
	for ipv6@ietf.org; Fri, 29 Jun 2007 19:36:32 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Q0p-0007tj-Ue
	for ipv6@ietf.org; Fri, 29 Jun 2007 19:36:32 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85327221; Fri, 29 Jun 2007 19:36:26 -0400
Message-ID: <4685976F.7090201@internap.com>
Date: Fri, 29 Jun 2007 16:36:15 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jeroen Massar <jeroen@unfix.org>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
	<4685820C.4020408@internap.com>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
In-Reply-To: <4685858B.8040003@spaghetti.zurich.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jeroen Massar wrote:
> Scott Leibrand wrote:
>   
>>
>> ULA-C and PI space will likely both cost about the same, and your
>> brother could likely afford either.  The issue isn't so much dollar cost
>> as availability: your brother likely doesn't qualify for PI space
>> (unless he can justify efficient use of a /22), but he could get ULA-C
>> just by asking.
>>     
>
> Wow, a /22 IPv6 space, that is a big chunk. But I assume you mean /22
> IPv4.  What has IPv4 to do with IPv6?

Yes, I was referring to a /22 of IPv4 space.  Current ARIN policy 
requires that, in order to get IPv6 PI space, you meet the same 
qualifications as for IPv4 PI space.  (You needn't actually get the IPv4 
space, but that was the least controversial method of justification 
available, which avoids going down the controversial rat-hole of 
justifying by "sites", "nodes", or "subnets" and specifying HD ratios 
within an end-user's network.)
>  and moreover why is that ARIN policy
>  being forced upon the IETF thus leading to ULA-C and then leading to
> heavily hinting ARIN to provide ULA-C as a way out.
>   

I don't think there's any forcing going on.  See below.

> Clearly ULA-C is just "cheap address space", nothing more nothing less.
> And the sole reason for a possible existence seems to be that the
> policies in RIR land do not allow everybody to get address space the way
> they want to. Instead of changing the RIR policies, ULA-C gets invented.
>   

Do you have a proposed change to RIR policies?  If so, I invite you to 
make a policy proposal.  I also invite you to read the archives of the 
discussion surrounding previous similar policy proposals.

> Which is also what you write in the 2 emails before this one, but in
> between the lines.
>
> The RIR community effectively blocks people from getting address space
> on the premise that "but that costs routing slots", even though the
> minimum allocation is /48 either way, and then on top of that basing
> that decision on IPv4 address space usage, wow.
>   

I don't know about you, but I help run a network that provides those 
routing slots, and doing so costs real money.  Right now we're in the 
process of upgrading a large number of routers, at significant cost, 
simply to provide enough routing slots to support the growth in the BGP 
table. 

The RIRs currently require small networks to get provider aggregatable 
(PA) space from their provider(s).  This ensures that any more-specific 
routes originated from such space can be safely filtered, while 
maintaining reachability via the provider's aggregate.  PI space cannot 
be filtered this way, so there is a higher bar for getting such space.  
The height of that bar can be adjusted (as was recently done for IPv4 by 
changing from a /19 to a /22 for multihomed networks.) In fact, the IETF 
originally specified that all IPv6 space should be PA, leading to fears 
that ULA-C space would become the only de facto PI space.  With recent 
action by the RIRs to create IPv6 PI space, those fears have been mostly 
alleviated.

> I think that ULA-C is a really really bad idea because of this.
>   

Perhaps.  But just as "Democracy is the worst form of government there 
is, except for all the others we've tried", I think ULA-C is better than 
what's available now, and more practical in the near term than a 
PI-for-everyone utopia.

The fact that IPv6 PI space exists at all is due to the action of 
individuals working through the RIR public policy process to create it.  
Some of the same individuals, recognizing they've pushed as far as they 
can toward liberalizing PI for now, would like to create additional 
flexibility for small networks to use IPv6 in a way that suits their 
needs.  In order to avoid creating an IPv6 "swamp", those individuals 
have asked the IETF to standardize a new form of registered private IP 
space out of a single common global netblock, and allow the RIRs to 
begin allocating/assigning that space to registrants.  Their attempts to 
do so are being met with cries of "why don't you just liberalize PI."  
Do you see the irony here?

-Scott

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Fri Jun 29 21:31:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Rnd-00021L-PU; Fri, 29 Jun 2007 21:30:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Rnc-00021B-Rm
	for ipv6@ietf.org; Fri, 29 Jun 2007 21:30:56 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Rn7-0004OG-1Q
	for ipv6@ietf.org; Fri, 29 Jun 2007 21:30:56 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 2836E11426
	for <ipv6@ietf.org>; Sat, 30 Jun 2007 01:30:24 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Fri, 29 Jun 2007 16:14:08 MST."
	<20070629231408.GA46212@elvis.mu.org> 
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
	<20070629231408.GA46212@elvis.mu.org> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 30 Jun 2007 01:30:24 +0000
Message-ID: <21461.1183167024@sa.vix.com>
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> From: bill fumerola <billf@mu.org>
> On Fri, Jun 29, 2007 at 05:22:24PM -0400, briand@ca.afilias.info wrote:
> > Please answer me this, however (anyone, not just Paul):
> > - of the additional requirements listed, which of those are not available
> > (e.g. automatically) for PI allocations in the DFZ?
> > 
> > What I'm asking, of course, is this: Is there *anything* unique to ULA
> > that is not possible to implement with PI allocations by RIRs?
> 
> AfriNIC has said they will recind PI address space that is not "announced"
> within a year. you may interpret "announce" as you wish. i assume they mean
> in the DFZ.
> 
> which means PI space from AfriNIC is unusable for this purpose.

more to the point, we're expecting vast numbers of ULA-C prefixes to be
allocated -- tens of thousands -- hundreds of thousands? -- millions?? --
and the RIR community is uncomfortable with having to upgrade their
routers to be able to handle that number of prefixes.  therefore they're
pushing for FC00::/7 or some other fingerprint that makes them un-DFZ-able,
and in exchange, they seem to be comfortable with a much lower barrier to
acquisition for this type of prefix.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 30 11:39:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4f1a-0005Hm-B1; Sat, 30 Jun 2007 11:38:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4f1Y-0005Hc-HO
	for ipv6@ietf.org; Sat, 30 Jun 2007 11:38:12 -0400
Received: from mailhub.hp.com ([192.151.27.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4f1K-0004CW-2L
	for ipv6@ietf.org; Sat, 30 Jun 2007 11:38:12 -0400
Received: from [205.233.55.236] (unknown [205.233.55.236])
	by mailhub.hp.com (Postfix) with ESMTP
	id 4ECDE27113; Sat, 30 Jun 2007 11:41:47 -0400 (EDT)
Message-ID: <468678D1.40000@hp.com>
Date: Sat, 30 Jun 2007 11:37:53 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Wes Beebee (wbeebee) wrote:
> Section 3.1 of RFC 2461 describes intended behavior when a host
> receives an RA without an advertised prefix:
> 
>       "Multiple prefixes can be associated with the same link.  By
>       default, hosts learn all on-link prefixes from Router
>       Advertisements.  However, routers may be configured to omit some
>       or all prefixes from Router Advertisements.  In such cases hosts
>       assume that destinations are off-link and send traffic to routers.
>       A router can then issue redirects as appropriate."
> 
> As described in our draft, this language should be strengthened to state
> 
> that without advertised prefixes, without manual configuration, and 
> without redirects, hosts MUST send all non-link-local traffic to the 
> default router and MUST NOT issue an NS to resolve any destination 
> other than a link-local address.
> 

This language should already be in the 2461bis, just not in the section 
you want it in.  May be this paragraph can instead be made more generic 
and do not go into to much operation detail since this is a
"Comparison with IPv4" section.

-vlad


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 30 16:22:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4jSY-0007Kw-2p; Sat, 30 Jun 2007 16:22:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4jSW-0007JO-LF
	for ipv6@ietf.org; Sat, 30 Jun 2007 16:22:20 -0400
Received: from smtp01.icann.org ([192.0.34.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4jSM-0001rm-DZ
	for ipv6@ietf.org; Sat, 30 Jun 2007 16:22:20 -0400
Received: from [10.242.22.215] (m015f36d0.tmodns.net [208.54.95.1])
	(authenticated bits=0)
	by smtp01.icann.org (8.12.11.20060308/8.12.11) with ESMTP id
	l5UKM7e4023711
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 30 Jun 2007 13:22:08 -0700
In-Reply-To: <4685976F.7090201@internap.com>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
	<4685820C.4020408@internap.com>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
	<4685976F.7090201@internap.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FDDD58FE-CEF6-4942-877A-FB7424D953B8@icann.org>
Content-Transfer-Encoding: 7bit
From: Leo Vegoda <leo.vegoda@icann.org>
Date: Sat, 30 Jun 2007 16:22:06 -0400
To: Scott Leibrand <sleibrand@internap.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 29 Jun 2007, at 7:36pm, Scott Leibrand wrote:

[...]

> The RIRs currently require small networks to get provider  
> aggregatable (PA) space from their provider(s).

This just isn't true. Both APNIC and the RIPE NCC will assign  
prefixes longer than an IPv4 /24. APNIC even document the fact quite  
nicely where they say "There is no minimum assignment size for  
portable assignments made under these terms".

http://www.apnic.net/docs/policy/add-manage-policy.html#11.1

Over the last two years the RIPE NCC has assigned about 2800 prefixes  
longer than /22 and APNIC have made over 200. It's all there in the  
statistics files that the RIRs publish every day on their FTP sites.

[...]

>> I think that ULA-C is a really really bad idea because of this.
>
> Perhaps.  But just as "Democracy is the worst form of government  
> there is, except for all the others we've tried", I think ULA-C is  
> better than what's available now, and more practical in the near  
> term than a PI-for-everyone utopia.
>
> The fact that IPv6 PI space exists at all is due to the action of  
> individuals working through the RIR public policy process to create  
> it.  Some of the same individuals, recognizing they've pushed as  
> far as they can toward liberalizing PI for now, would like to  
> create additional flexibility for small networks to use IPv6 in a  
> way that suits their needs.  In order to avoid creating an IPv6  
> "swamp", those individuals have asked the IETF to standardize a new  
> form of registered private IP space out of a single common global  
> netblock, and allow the RIRs to begin allocating/assigning that  
> space to registrants.  Their attempts to do so are being met with  
> cries of "why don't you just liberalize PI."  Do you see the irony  
> here?

I can see that people will grab some ULA-C space if it becomes  
available. But I've not yet read a good definition of where it won't  
be routable while I've read at least one statement confirming that  
ULA-C routes would be accepted if they were offered.

The core problem seems to be a very soft definition of "local". If  
that's firmed up then there might be a way to convince people that  
ULA-C can be restricted to "local" networks and not be used as a way  
of getting cheaper PI space, or a way of getting PI space where the  
RIR doesn't have a policy supporting its assignment.

Regards,

Leo

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 30 17:57:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4kw7-0006Hw-PX; Sat, 30 Jun 2007 17:56:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4kw6-0006ES-9x
	for ipv6@ietf.org; Sat, 30 Jun 2007 17:56:58 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4kw3-0007Q4-01
	for ipv6@ietf.org; Sat, 30 Jun 2007 17:56:58 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 389481142E
	for <ipv6@ietf.org>; Sat, 30 Jun 2007 21:56:54 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Sat, 30 Jun 2007 16:22:06 -0400."
	<FDDD58FE-CEF6-4942-877A-FB7424D953B8@icann.org> 
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
	<Pine.LNX.4.64.0706292354230.29317@chandra.student.uit.no>
	<4685820C.4020408@internap.com>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
	<4685976F.7090201@internap.com>
	<FDDD58FE-CEF6-4942-877A-FB7424D953B8@icann.org> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 30 Jun 2007 21:56:54 +0000
Message-ID: <84589.1183240614@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

From: Leo Vegoda <leo.vegoda@icann.org>:
> 
> The core problem seems to be a very soft definition of "local". If  that's
> firmed up then there might be a way to convince people that  ULA-C can be
> restricted to "local" networks and not be used as a way  of getting cheaper
> PI space, or a way of getting PI space where the  RIR doesn't have a policy
> supporting its assignment.

i don't see a lot of folks who need to be convinced, mostly just people who
are concerned that a lot of other folks aren't convinced.  the number of
people who have actually said that they themselves aren't convinced is small.

but more importantly, we can define "local" any way we want, and we probably
will, for the purpose of getting this specification written.  but there's no
recourse at all by part A if parties B and C decide to "violate" the "local"
definition.  (nor is there any harm to party A so literally nobody should
care about this, yet a lot of folks are terribly concerned about it anyway,
i think heinlein called this the "aunt millie syndrome".)  so, yes, by all
means, let's find a comforting definition for "local", because while it won't
matter all in operational practice, it will make a big difference in the
general acceptance, dare i say consensus, of the resulting specification.

for the record, i am comfortable with the definition of "local" that was
quoted here a few weeks back, which was more or less "same autonomous system".
(but then, i'd be comfortable with a lot of other definitions, so, let fly!)

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org Sat Jun 30 20:00:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4mrc-0003lz-8L; Sat, 30 Jun 2007 20:00:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4mrb-0003fh-Cr
	for ipv6@ietf.org; Sat, 30 Jun 2007 20:00:27 -0400
Received: from cyteen.hactrn.net ([66.92.66.68])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4mra-0000Ns-TT
	for ipv6@ietf.org; Sat, 30 Jun 2007 20:00:27 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id AFE8828477
	for <ipv6@ietf.org>; Sun,  1 Jul 2007 00:00:03 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 01 Jul 2007 00:00:03 +0000
Message-Id: <20070701000003.AFE8828477@cyteen.hactrn.net>
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.82% |   15 | 11.39% |   131839 | jeroen@unfix.org
  9.41% |   16 | 10.34% |   119670 | fred.l.templin@boeing.com
 10.00% |   17 |  8.20% |    94878 | paul@vix.com
  8.24% |   14 |  7.60% |    87893 | brian.e.carpenter@gmail.com
  5.88% |   10 |  9.52% |   110090 | shemant@cisco.com
  7.65% |   13 |  7.38% |    85343 | sleibrand@internap.com
  7.65% |   13 |  5.86% |    67843 | rogerj@jorgensen.no
  4.71% |    8 |  3.85% |    44561 | jinmei@isl.rdc.toshiba.co.jp
  4.12% |    7 |  3.50% |    40463 | jhw@apple.com
  2.94% |    5 |  2.08% |    24022 | leo.vegoda@icann.org
  2.35% |    4 |  1.95% |    22583 | kkargel@polartel.com
  2.35% |    4 |  1.74% |    20088 | billf@mu.org
  1.76% |    3 |  2.23% |    25814 | rdroms@cisco.com
  1.76% |    3 |  1.98% |    22896 | briand@ca.afilias.info
  1.76% |    3 |  1.49% |    17263 | vladislav.yasevich@hp.com
  1.76% |    3 |  1.45% |    16799 | mark_andrews@isc.org
  1.76% |    3 |  1.32% |    15291 | suresh.krishnan@ericsson.com
  0.59% |    1 |  2.48% |    28651 | jabley@ca.afilias.info
  0.59% |    1 |  2.38% |    27581 | vishwas.ietf@gmail.com
  1.18% |    2 |  1.33% |    15359 | heldal@eml.cc
  1.18% |    2 |  1.02% |    11837 | gih@apnic.net
  1.18% |    2 |  0.89% |    10256 | ipng@69706e6720323030352d30312d31340a.nosense.org
  1.18% |    2 |  0.88% |    10234 | huitema@windows.microsoft.com
  1.18% |    2 |  0.84% |     9667 | itojun@itojun.org
  1.18% |    2 |  0.77% |     8951 | bob.hinden@nokia.com
  1.18% |    2 |  0.70% |     8059 | george+ipng@m5p.com
  0.59% |    1 |  1.00% |    11549 | shamilton@exactor.com
  0.59% |    1 |  0.77% |     8949 | stig.venaas@uninett.no
  0.59% |    1 |  0.59% |     6790 | internet-drafts@ietf.org
  0.59% |    1 |  0.57% |     6636 | stephen@sprunk.org
  0.59% |    1 |  0.50% |     5810 | wbeebee@cisco.com
  0.59% |    1 |  0.48% |     5564 | sra+ipng@hactrn.net
  0.59% |    1 |  0.48% |     5520 | tjc@ecs.soton.ac.uk
  0.59% |    1 |  0.46% |     5335 | pekkas@netcore.fi
  0.59% |    1 |  0.45% |     5215 | msa@moth.iki.fi
  0.59% |    1 |  0.44% |     5105 | bmanning@isi.edu
  0.59% |    1 |  0.38% |     4353 | andrew@ca.afilias.info
  0.59% |    1 |  0.36% |     4124 | jari.arkko@piuha.net
  0.59% |    1 |  0.36% |     4111 | elwynd@dial.pipex.com
--------+------+--------+----------+------------------------
100.00% |  170 |100.00% |  1156992 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



