From ipv6-bounces@ietf.org Sun Jul 01 01:48: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 1I4sI4-0006vN-Vd; Sun, 01 Jul 2007 01:48:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4sI3-0006nq-Dd
	for ipv6@ietf.org; Sun, 01 Jul 2007 01:48:07 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4sHA-000398-Sa
	for ipv6@ietf.org; Sun, 01 Jul 2007 01:48:07 -0400
Received: by ug-out-1314.google.com with SMTP id u2so951758uge
	for <ipv6@ietf.org>; Sat, 30 Jun 2007 22:47:12 -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=TrvZxTF3BVGbU2HkGwgm6vhbZrCQQjY7M69efvC5p1BTJldcXtUrAetbfobjMdGvtlVrjBen4+DUqm6smhGv/+1YKpnKMNhNZgPGOlvr5d/kY+n59torN87UIphGyvabU/D9e52J1U1gyRWZAKvI0KntKVpn4RKUMlBKErFBT1o=
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=Si6V0K8VtijRywAL1UClXaj9OqGDIguka46R0nYhpDK9Ow38p0dH41CXzohXJ9wbVV7oYWNERyp6c5apRmbRt+K+6tvxTvla12DXM8WhRYNTUgsRnKB03pBbQTn/Ubub162hB7btxCI+iHN0ufjhrFs/HMJ5qT7EwAttXaRuZkM=
Received: by 10.67.97.18 with SMTP id z18mr2378411ugl.1183268832017;
	Sat, 30 Jun 2007 22:47:12 -0700 (PDT)
Received: from ?192.168.1.100? ( [85.232.174.201])
	by mx.google.com with ESMTP id h1sm3208808ugf.2007.06.30.22.47.10
	(version=SSLv3 cipher=RC4-MD5); Sat, 30 Jun 2007 22:47:11 -0700 (PDT)
Message-ID: <46873FE2.2020001@gmail.com>
Date: Sun, 01 Jul 2007 07:47:14 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
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>
	<46852E40.1010103@ericsson.com>
In-Reply-To: <46852E40.1010103@ericsson.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

For reference, RFC 4897 would have fixed this downref problem;
it just came a few months too late.

    Brian

On 2007-06-29 18:07, Suresh Krishnan wrote:
> 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
> --------------------------------------------------------------------
> 

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



From ipv6-bounces@ietf.org Sun Jul 01 01:49: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 1I4sJB-0008Tj-3G; Sun, 01 Jul 2007 01:49:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4sJ9-0008Q9-5h
	for ipv6@ietf.org; Sun, 01 Jul 2007 01:49:15 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4sJ8-0002e7-Tt
	for ipv6@ietf.org; Sun, 01 Jul 2007 01:49:15 -0400
Received: by ug-out-1314.google.com with SMTP id u2so951835uge
	for <ipv6@ietf.org>; Sat, 30 Jun 2007 22:48:01 -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=ixzKeFR3p+/PySOy9FieIw6G4AFESVLMA05OVKd24xeLr5SNI70c3uEilBsEvlmOVs576M5kZZCxM84VHdg1x76yhhlbFkZdFgyipSW1gqyu6pAo2kOy8WF5ZbuDeX0kyiAhyVJyHZr+BNezMzcYE6ie2rXqKNYpcnApLmvu4Qo=
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=M6e94ZJGgKM46RbQVlalVoKDaiX3mMndSt8IkX3jEIrlyZcrXaP/+ckbU+3x2CJDEc5dTeENEVG0oWOEVUffSdkuCiyOgcRiq24rjPqb6RobooJ3u2E3b03Lag6n1UaZ0phoJ/Gd9i6ZxAnGNh3iWSIrghJIKU12JLAPNfXA4EY=
Received: by 10.67.19.11 with SMTP id w11mr939811ugi.1183268881687;
	Sat, 30 Jun 2007 22:48:01 -0700 (PDT)
Received: from ?192.168.1.100? ( [85.232.174.201])
	by mx.google.com with ESMTP id s59sm3144173uga.2007.06.30.22.48.00
	(version=SSLv3 cipher=RC4-MD5); Sat, 30 Jun 2007 22:48:01 -0700 (PDT)
Message-ID: <46874014.4040208@gmail.com>
Date: Sun, 01 Jul 2007 07:48: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: bob.hinden@nokia.com
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
In-Reply-To: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Cc: IPv6 WG <ipv6@ietf.org>
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

Ship it.

     Brian

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



From ipv6-bounces@ietf.org Sun Jul 01 09:14: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 1I4zG0-0006B5-UP; Sun, 01 Jul 2007 09:14:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4zG0-0006B0-E9
	for ipv6@ietf.org; Sun, 01 Jul 2007 09:14:28 -0400
Received: from wx-out-0506.google.com ([66.249.82.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4zFp-0002z0-2O
	for ipv6@ietf.org; Sun, 01 Jul 2007 09:14:28 -0400
Received: by wx-out-0506.google.com with SMTP id h27so1126868wxd
	for <ipv6@ietf.org>; Sun, 01 Jul 2007 06:14:16 -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=a8D7QVCGunfEFRpD2CU7oknSdZuPzQ/27tujZ2JBNr2ZqEpgri/FcJ3vS6dQopne+G2pVzm4J6WBw4ezagLVObHJpPzRdGMF3f6vZZRZQFtLUTavASuqNSFg1VWkn+vAP6jzE6sVgES9G3T/LWBZh5cQ76qVIj0c8aZeXYE21Jk=
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=nuBkMBCV1NsuciK7ngx0S9zVlLjqCNfB2+Hqcphkl1v+rRCHxP+S6fc4NkbkRwAXruXPSClUuH47/IB/azzh0h+ZYslXeyZrqMgxpQLNlYcKBQKxRoDqZ2vAMsbvGHeg+pHypGv19NQD8yF6BvaPazN+HD4R4m6g8M1nCrIzLrs=
Received: by 10.90.95.11 with SMTP id s11mr4341079agb.1183295656797;
	Sun, 01 Jul 2007 06:14:16 -0700 (PDT)
Received: from laptop229tj ( [70.223.228.188])
	by mx.google.com with ESMTP id 8sm8609901agd.2007.07.01.06.14.10
	(version=SSLv3 cipher=RC4-MD5); Sun, 01 Jul 2007 06:14:13 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: <ipv6@ietf.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>
Date: Sun, 1 Jul 2007 09:14:09 -0400
Message-ID: <01a301c7bbe1$b9c1ccb0$2d456610$@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: Ace6m+bng2nKFT/BQHKUFN0kK2ZkZgAjUp4g
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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
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

"Clearly ULA-C is just "cheap address space", nothing more nothing less."
Well, yes and no.  Mostly yes.  It is also a readily identifiable block of
said (cheap) addresses, with some operational differences from normal
(globally routable) addresses.


I, for one, have no problem at all with ULA and ULA-C, in principle.
Private address space, for people/environments, etc. to use however they
want seems like a dandy idea.
	... and will present a familiar feel to those who do similar in IPv4
w/ RFC1918 addresses.


The catch that arises, IMHO, is WRT the DNS resolvability of these addresses
(#3 & #4, below).

I am mostly neutral here:
* While I see the value of having them resolve, I understand the (real |
perceived) operational impacts thereof.
* I also see the value in not having global resolution of non-globally
reachable hosts.

(I say mostly neutral because I am leaning towards the "make them
resolvable" side of the fence, having worked in lots of IPv4 VPN situations
where the destination addresses where RFC1918 (not globally reachable) and
the (forward) resolving of hosts was a royal PITA I can see lots of benefit
from having these resolve "automagically" (FWIW, exactly the situation
mentioned in the draft) ... basically, a difference between being able to
reach the node and knowing the address(es) I should be trying to reach it at
... )
(I also see the value in this address range being obviously special (i.e. -
from a single, well-known prefix, as this greatly simplifies filtering)



I guess what I am getting at ... in my mind, it boils down to:
1) Is there a reason to not support ULA/ULA-C, sans DNS?
	(Keeping in line with "tell me what I can do, and how I can do it -
not what I can't do" ... or, maybe even " Be conservative in what you send
and liberal in what you accept.")

2) For ULA-C, in order for it to work we need a registrar or some sort ...
maybe IANA, maybe the RIRs, maybe a robot.

3) Is there a major operational challenge to allowing forward DNS resolution
of ULA-C addresses?  
	("It's my zone, and I'll put whatever entries I want in there")

4) WRT reverse DNS ... my thought would be to drop this.  If it becomes
necessary for you to reverse-lookup the addresses you are talking to over
this private network connection then maybe it is time to manage that
internally ... or revisit this issue in the future, if it becomes that
prevalent?

5) Note that this does not preclude, nor prevent, PI (micro)allocations or
any other RIR-based allocation scheme/effort ... and that specifically,
these ULA-C addresses are not meant to be globally routable (nor to be seen
as "cheap PI address space").


... just more thoughts ... 
/TJ


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



From ipv6-bounces@ietf.org Sun Jul 01 09: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 1I4zwq-0005B3-Nq; Sun, 01 Jul 2007 09:58:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4zwm-00059A-GT
	for ipv6@ietf.org; Sun, 01 Jul 2007 09:58:40 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4zwi-0007WV-1q
	for ipv6@ietf.org; Sun, 01 Jul 2007 09:58:40 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 14:58:35 +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: Sun, 1 Jul 2007 15:00:02 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E25@E03MVC4-UKBR.domain1.systemhost.net>
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: Ace1jEy6vrydi/74TL+vnobQb3bx1gGWNUrg
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: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 13:58:35.0293 (UTC)
	FILETIME=[EAB52CD0:01C7BBE7]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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

> My main question about ULA-C still stands: how is it=20
> different from PI?

To understand the difference between PI and ULA-C you need to understand
the difference between the public Internet and an IP internetwork. Any
set of networks that use the Internet Protocols are an IP internetwork.
However there is only one public Internet and that is the subset of IP
internetworks which have chosen to connect together so that end hosts
can communicate without prior arrangements.

PI addresses are public Internet addresses which end hosts can use to
communicate without prior arrangements. ULA-C addresses can only be used
to communicate between end hosts where both ends have made prior
arrangements to enable communication between the two ULA-C blocks from
which the end-hosts are numbered. Any IP internetwork managed by a
single authority can make use of ULA-C addresses because the single
authority presumably is in charge of making things work. When two or
more authorities who manage internetworks wish to enable inter-authority
(inter-AS) communication, they need to make specific arrangements either
bilaterally or unilaterally.=20

These arrangements are a lot like Internet peering arrangements
although, technically, it is not necessary to use ASes and BGP4 to do
this, just hook things up with circuits or tunnels. What is missing in
this ULA-C picture is transit. On the public Internet there is the
assumption that packets will be carried across as many autonomous
networks as necessary to reach their destination. However, when the
source address or destination address is ULA-C, the transit assumption
breaks down. There is no "assumed" interconnectivity with ULA-C
addresses which makes them quite different from PI addresses.

There will be some groups of organizations who find the requirement for
making prior arrangements to be very useful. They may not want any
packets from sources who have not signed a mutual agreement. These
Community Of Interest Networks exist today in the IPv4 world and they
are thriving. Examples are the auto industry with ANX and ENX, the air
transport industry with Aeronet and the global financial services
industry with RadianzNet.=20

I am not suggesting that any of these existing networks would use ULA-C
but that they represent real-world use-cases for globally unique
registered address space that is explicitly *NOT* routed on the public
Internet. The big question here is whether ULA-C presents any advantage
over simply using PI and selectivly shutting off the characteristics
which are not desirable. For instance, if you never announce your PI
prefix on the Internet, then you will never receive any packets without
prior arrangement.

--Michael Dillon

P.S. if anyone has other examples besides automotive, air transport and
financial services idustries, I would be interested in hearing about
them.

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



From ipv6-bounces@ietf.org Sun Jul 01 11:53: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 1I51ig-0001RS-8t; Sun, 01 Jul 2007 11:52:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I51ie-0001JF-Lx
	for ipv6@ietf.org; Sun, 01 Jul 2007 11:52:12 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I51ia-0007aC-94
	for ipv6@ietf.org; Sun, 01 Jul 2007 11:52:12 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 16:52:07 +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: Sun, 1 Jul 2007 16:53:34 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
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: Ace3QfxPuf4fNqswTU6+4rnUa6m4cgEtc4og
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: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 15:52:07.0014 (UTC)
	FILETIME=[C6CF5060:01C7BBF7]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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 site is a network of computers with a single=20
> administration, this can mean indeed a major corporation (who=20
> maybe even require multiple /48's which is why rfc4193 is a=20
> bit off to cover those cases)

Where has the IETF redefined the meaning of the word "site"?
In plain English, this word refers to a distinct physical location such
as an office or building or campus.

--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 Sun Jul 01 12:54: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 1I52gk-00071u-R2; Sun, 01 Jul 2007 12:54:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I52gj-0006vK-IL
	for ipv6@ietf.org; Sun, 01 Jul 2007 12:54:17 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I52gf-0005Nv-0t
	for ipv6@ietf.org; Sun, 01 Jul 2007 12:54:17 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 17:54:12 +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: Sun, 1 Jul 2007 17:55:39 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E2A@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <20070627204814.GR31273@elvis.mu.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AfriNIC, ULA-C, & "why not just get PI space"
Thread-Index: Ace4/Mnb4O4ci4MmRGqd0qwCiTrMgQDA0+Bw
References: <20070627204814.GR31273@elvis.mu.org>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 16:54:12.0365 (UTC)
	FILETIME=[734AC3D0:01C7BC00]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: RE: 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


> those in the AfriNIC region who want globally unique,=20
> registered space but do not plan to "announce the IPv6 PI=20
> address space" have no method of getting any such space. if=20
> anyone reads this differently than i do, please educate me.

Do the RIRs actually refuse to allocate addresses to organizations
outside their region? If not, then anyone in Africa who needs IPv6 PI
can simply go registry shopping.

Of course, the reason AfriNIC is *Afri* NIC is to support organizations
in Africa. As such, I'm sure it has mechanisms by which organizations in
Africa can influence AfriNIC policies.

There is really no need to worry about this sort of thing at a global
level. Besides, the IETF designs protocols, not RIR policy mechanisms.

--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 Sun Jul 01 13: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 1I53Iy-0005QZ-I5; Sun, 01 Jul 2007 13:33:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I53Iw-0005QP-Mo
	for ipv6@ietf.org; Sun, 01 Jul 2007 13:33:46 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I53In-0005O1-CC
	for ipv6@ietf.org; Sun, 01 Jul 2007 13:33:46 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 18:33:36 +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: Sun, 1 Jul 2007 18:35:03 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E2C@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8D2@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: Ace5CQ5Fx/N05g4fSh2wtsywt1zS7AAAEL4wAL36B1A=
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>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D2@XCH-NW-7V2.nw.nos.boeing.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 17:33:36.0708 (UTC)
	FILETIME=[F48CE040:01C7BC05]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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

> First, s/laptop/platform - where, a "platform" could be=20
> something relatively small (like my laptop) or something=20
> quite a bit larger (like a cruise ship). Any points=20
> in-between (planes, trains, automobiles, etc.) also meet the=20
> description. But, all of them are platforms and all of them=20
> are also "sites".

Don't forget things like the containers full of suitcase that they load
into airplanes. Or packing crates full of produce stored in a warehouse,
moved into a shipping container, loaded on a truck, transferred to a
ship, transferred to a train, loaded on another truck, and unloaded in
another warehouse cooler. Or medical devices with built-in computers
somewhat analogous to car engine computers, i.e. an insulin drip device
which needs to be docked at the pharmacy for data analysis before they
refill the insulin tank. Basically, IPv6 will be used for stuff which
was sci-fi a few years ago, not just the same old things as IPv4.

--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 Sun Jul 01 16:37: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 1I56A6-0002ON-FG; Sun, 01 Jul 2007 16:36:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I56A5-0002OI-0U
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:36:49 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I56A0-0005Ck-IF
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:36:48 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 21:36:43 +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: Sun, 1 Jul 2007 21:38:10 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E2E@E03MVC4-UKBR.domain1.systemhost.net>
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+uGuYsGAAW6JmAAKJ8KAA=
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org><13846.1183003509@sa.vix.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED8D5@XCH-NW-7V2.nw.nos.boeing.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 20:36:43.0683 (UTC)
	FILETIME=[894C3730:01C7BC1F]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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

>   4) can the ULA-C's be kept out of the DFZ?

Since the IETF has no control whatsoever over the DFZ, then the answer
has to be, no.

The DFZ is the core of the public Internet, one of many internetworks
which use IETF protocols. If the operators of the private networks who
have formed the DFZ, decide that they don't want ULA-C prefixes in the
DFZ, then they won't be there. But that is up to the network operators,
not up to the IETF.

The IETF's role is not limited to only specifying technology that is
useful for the public Internet.

--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 Sun Jul 01 16:46: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 1I56JJ-0004Mi-48; Sun, 01 Jul 2007 16:46:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I56JG-0004EC-Qv
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:46:18 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I56JC-0007so-90
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:46:18 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 21:46:12 +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: Sun, 1 Jul 2007 21:47:40 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E33@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8DC@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: Ace5rfaQSEdxifjjRK+m78AGqB12NAAAG8KwAJyCyRA=
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>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 20:46:12.0838 (UTC)
	FILETIME=[DC8A6060:01C7BC20]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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=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 |
> > >>>       +--------+-+----------+---------+---------+----------+

Something that has been overlooked is the number of bits in each
section. How was this number determined? Is it the right number of bits
for each level? Is there a technical reason for sticking with octet
boundaries here? Does there need to be an actual boundary between the
RIR and LIR section at all?

I think that the RIR section has too many bits (there are 5 of them) and
the LIR section has too few.

It seems to me that the boundary between RIR and LIR should be left
unspecified. IANA can allocate chunks of whatever size is needed to RIRs
as those needs arise.=20

--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 Sun Jul 01 16:52: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 1I56PU-0004EA-DB; Sun, 01 Jul 2007 16:52:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I56PS-0004DA-Qw
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:52:42 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I56PH-0000vC-K6
	for ipv6@ietf.org; Sun, 01 Jul 2007 16:52:42 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 21:52:30 +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: Sun, 1 Jul 2007 21:53:58 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E35@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <57667.1183061116@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: Ace5v+fJ4oxirXysRq2x7v/QgYz0TgCYUWkw
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>
	<57667.1183061116@sa.vix.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 20:52:30.0801 (UTC)
	FILETIME=[BDD2F410:01C7BC21]
X-Spam-Score: 0.2 (/)
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


> where in my diffs do i restrict RIRs to the current set of=20
> RIRs?  it's expected that there may be more RIRs in the=20
> future.

Is this a backdoor attempt to make it possible for sovereign nations to
acquire their own IP allocations as proposed by Houlin Zhao of the ITU?

--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 Sun Jul 01 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 1I56dT-0002Mm-R7; Sun, 01 Jul 2007 17:07:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I56dS-0002Mg-1h
	for ipv6@ietf.org; Sun, 01 Jul 2007 17:07:10 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I56dC-0006Gb-Uv
	for ipv6@ietf.org; Sun, 01 Jul 2007 17:07:10 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 1 Jul 2007 22:06:53 +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: Sun, 1 Jul 2007 22:08:21 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E39@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
Thread-Index: Ace6fh1gjyJ9z9QESFqzNYDVZjtJDQBpPaSA
References: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
	<62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 01 Jul 2007 21:06:53.0868 (UTC)
	FILETIME=[C04086C0:01C7BC23]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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

> Oddly enough, what I recommend for now is - put ULA-C on the=20
> back burner.

I generally agree with what Brian has said here and I especially support
his recommendation to push this to the backburner and let it stew for a
while. We really need more clarity on use-cases for this before going
further. And, we need to get a broader perspective, i.e. more people
looking at the issues.

> Make travel plans to attend the next IANA meeting, and in the=20
> meantime, join the IANA mailing lists. Voice your concern=20
> over PI space issues, and the making available of small PI=20
> blocks to all comers.

In particular, the whole issue of PI versus ULA-C has not been clearly
stated. What does ULA-C bring to the table that cannot be done with PI
addresses? If the answer is nothing, then ULA-C is not needed at all.

--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 Sun Jul 01 18:22: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 1I57nT-00066r-FM; Sun, 01 Jul 2007 18:21:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I57nR-0005yq-TV
	for ipv6@ietf.org; Sun, 01 Jul 2007 18:21:33 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I57nN-0002tH-Iw
	for ipv6@ietf.org; Sun, 01 Jul 2007 18:21:33 -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 1I57pr-000Eh6-6E; Sun, 01 Jul 2007 22:24:03 +0000
In-Reply-To: <46826215.10609@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>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DC98B27B-38A6-48FF-99D1-75F760D14EE7@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Sun, 1 Jul 2007 18:21:10 -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: 93238566e09e6e262849b4f805833007
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

Very late to this party, but:

On 27-Jun-2007, at 09:11, 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.
> Architecturally, they are certainly routeable (and so are /128s).
> But I am sure they will be filtered.

I hope they won't all be filtered, since there are a non-trivial  
number of infrastructure services in the DNS which are deployed  
using /48s assigned directly from RIRs under policies designed to  
facilitate critical infrastructure.

I realise that you were talking in far more general terms than this,  
but every time I see someone make blanket statements about "/48s" and  
their presence in the DFZ it makes me twitch. Not all /48s are  
components of larger assignments or allocations.


Joe



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



From ipv6-bounces@ietf.org Sun Jul 01 21:27: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 1I5Agw-0006mk-Q8; Sun, 01 Jul 2007 21:27:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Agu-0006ks-RM
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:27:00 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Agt-0003sm-Ia
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:27:00 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id A6DE811431
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 01:26:58 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Sun, 01 Jul 2007 21:47:40 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E33@E03MVC4-UKBR.domain1.systemhost.net>
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E33@E03MVC4-UKBR.domain1.systemhost.net>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Jul 2007 01:26:58 +0000
Message-ID: <97383.1183339618@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

> > > >>>       | 7 bits |1|  8 bits  | 16 bits | 16 bits | 80 bits  |
> > > >>>       +--------+-+----------+---------+---------+----------+
> > > >>>       | Prefix |L| Reserved | RIR Num | LIR Num | User Num |
> > > >>>       +--------+-+----------+---------+---------+----------+
> 
> Something that has been overlooked is the number of bits in each section.
> How was this number determined?

i made it up.  beer was involved.

> Is it the right number of bits for each level?

almost certainly not.

> Is there a technical reason for sticking with octet boundaries here?

no.  (though nibble boundaries are awful nice for operations folks.)

> Does there need to be an actual boundary between the RIR and LIR section at
> all?

i don't think so.  an RIR can allocate blocks-of-adjacent-blocks to LIRs.

> I think that the RIR section has too many bits (there are 5 of them) and
> the LIR section has too few.

you sound like a man ready to make a well reasoned counter proposal.  great!

> It seems to me that the boundary between RIR and LIR should be left
> unspecified. IANA can allocate chunks of whatever size is needed to RIRs
> as those needs arise. 

ok by me.  how's this?

    | 7 bits |1| 12 bits |  24 bits  | 80 bits  |
    +--------+-+---------+-----------+----------+
    | Prefix |L| RIR Num | Local Num | User Num |
    +--------+-+---------+-----------+----------+

this would have IANA handing out blocks of /24's to RIRs who could hand out
/48's to end users or blocks of /48's to LIRs (who would then hand out /48's
to end users).  as long as an end user is receiving a /48 and the top 7 bits
are distinctive, it doesn't matter as much what the "middle" looks like.

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



From ipv6-bounces@ietf.org Sun Jul 01 21:27: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 1I5AhX-0000uG-Gc; Sun, 01 Jul 2007 21:27:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5AhV-0000lS-Ge
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:27:37 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5AhU-00040D-Ax
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:27:37 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id E9A1811432
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 01:27:35 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Sun, 01 Jul 2007 21:53:58 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E35@E03MVC4-UKBR.domain1.systemhost.net>
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>
	<57667.1183061116@sa.vix.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E35@E03MVC4-UKBR.domain1.systemhost.net>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Jul 2007 01:27:35 +0000
Message-ID: <97463.1183339655@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
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 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.
> 
> Is this a backdoor attempt to make it possible for sovereign nations to
> acquire their own IP allocations as proposed by Houlin Zhao of the ITU?

no.

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



From ipv6-bounces@ietf.org Sun Jul 01 21:38: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 1I5Aqg-0003uK-Tm; Sun, 01 Jul 2007 21:37:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Aqf-0003u9-Ip
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:37:05 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Aqf-0005hC-Au
	for ipv6@ietf.org; Sun, 01 Jul 2007 21:37:05 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id DEF8C11431
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 01:37:04 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
In-Reply-To: Your message of "Sun, 01 Jul 2007 22:08:21 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E39@E03MVC4-UKBR.domain1.systemhost.net>
References: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
	<62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E39@E03MVC4-UKBR.domain1.systemhost.net>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Jul 2007 01:37:04 +0000
Message-ID: <2967.1183340224@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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

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

aside from the fact that iana doesn't have meetings or mailing lists, i note
that icann (iana's current corporate parent) doesn't set PI policy, that's a
regional thing.  iana does what ietf tells it.  rir's do what their members
tell them.  so, the above advice is a total multiple nonsequitur.

> In particular, the whole issue of PI versus ULA-C has not been clearly
> stated.  What does ULA-C bring to the table that cannot be done with PI
> addresses?  If the answer is nothing, then ULA-C is not needed at all.

thus far, rir community input has been "don't make me by 2-megaroute routers"
and the end result is policies that prohibit "PI for everybody".  ula-c is
an attempt to placate those communities while still offering unique address
space to everybody.  that's been stated, clearly, here and on ppml@.

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



From ipv6-bounces@ietf.org Mon Jul 02 04:45: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 1I5HWu-0003bt-75; Mon, 02 Jul 2007 04:45:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5HWt-0003bn-AL
	for ipv6@ietf.org; Mon, 02 Jul 2007 04:45:07 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5HWg-00006B-K9
	for ipv6@ietf.org; Mon, 02 Jul 2007 04:45:07 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1316699uge
	for <ipv6@ietf.org>; Mon, 02 Jul 2007 01:44: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=rKG0ZZpbdLwvfhalRgyo9DhX4X+q17S2U1jJxYTX+HMDYjKqm/qjia1nbKLQfOAcoeyRXItEkeXCFrvRFVaAcI/wG64fn92YPQVCuFi9DEoUvqnLhCwch4CwVHEQ9cChSSDh/H1vfoQalnVnpmWLtvwyynLaKylm5P+6SHCnxMA=
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=MjWTX/XXo+MJ9/4d4vVINzETi9CdHFU2svrVQA6WI8TJrnEstXMAcY/T/8/aq1mABy3H4YzDDS19a/OGL35hFP72b5RGn4GCDdl3nCdL7qQlaYBM+azhsHMLiaEzghnHNWid6A5QCExvT6xvaSFvx6OrtRsriM+4j9x780TayvQ=
Received: by 10.82.162.14 with SMTP id k14mr12446732bue.1183365893585;
	Mon, 02 Jul 2007 01:44:53 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 34sm15733578nfu.2007.07.02.01.44.52
	(version=SSLv3 cipher=RC4-MD5); Mon, 02 Jul 2007 01:44:52 -0700 (PDT)
Message-ID: <4688BB07.8050304@gmail.com>
Date: Mon, 02 Jul 2007 10:44:55 +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: <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>
	<DC98B27B-38A6-48FF-99D1-75F760D14EE7@ca.afilias.info>
In-Reply-To: <DC98B27B-38A6-48FF-99D1-75F760D14EE7@ca.afilias.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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 2007-07-02 00:21, Joe Abley wrote:
> Very late to this party, but:
> 
> On 27-Jun-2007, at 09:11, 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.
>> Architecturally, they are certainly routeable (and so are /128s).
>> But I am sure they will be filtered.
> 
> I hope they won't all be filtered, since there are a non-trivial number 
> of infrastructure services in the DNS which are deployed using /48s 
> assigned directly from RIRs under policies designed to facilitate 
> critical infrastructure.

Yes of course. I meant end-user /48s. Thanks for clarifying.

    Brian

> 
> I realise that you were talking in far more general terms than this, but 
> every time I see someone make blanket statements about "/48s" and their 
> presence in the DFZ it makes me twitch. Not all /48s are components of 
> larger assignments or allocations.
> 
> 
> Joe
> 
> 
> 

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



From ipv6-bounces@ietf.org Mon Jul 02 04:59: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 1I5Hkm-0002zF-Qg; Mon, 02 Jul 2007 04:59:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Hkl-0002z6-DT
	for ipv6@ietf.org; Mon, 02 Jul 2007 04:59:27 -0400
Received: from ug-out-1314.google.com ([66.249.92.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5HkX-0002v5-LV
	for ipv6@ietf.org; Mon, 02 Jul 2007 04:59:27 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1320173uge
	for <ipv6@ietf.org>; Mon, 02 Jul 2007 01:59: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=FmeACbC2/ClKHCi8jeldqpdPEtpxPF0edvNqXK2rCIeoStzt/rU+Qcx01r/SBzExt5qxzMMeF3I+evGwrU6Fm2VquVfC51cxS+CBQlEIXUb55wxlGHZXmq8uKd9jjIc+3Idwc04uT0Vh8y9732GnJwaVYXjXeCj1Fn4nfDpMt9s=
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=CmDlkY40ETMfPy7rzlsIrqghUyph7tpSKo+j3pHlY9w6OvX5uRG1VBULnbhBbODRwGPEyJYfkELgbamS5E62oeM5qidFiB4DGWeFgA7DRy0+UquZcpylRR4un38HCOUd+nNmV6rCs3rewL5/TL+dnRmk/Gtu7Xt02RtTb2g9dO0=
Received: by 10.82.158.12 with SMTP id g12mr12450631bue.1183366752061;
	Mon, 02 Jul 2007 01:59:12 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id f6sm26715693nfh.2007.07.02.01.59.09
	(version=SSLv3 cipher=RC4-MD5); Mon, 02 Jul 2007 01:59:10 -0700 (PDT)
Message-ID: <4688BE60.8090802@gmail.com>
Date: Mon, 02 Jul 2007 10:59: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: michael.dillon@bt.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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
Content-Type: text/plain; charset=UTF-8; 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

On 2007-07-01 17:53, michael.dillon@bt.com wrote:
>> 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)
> 
> Where has the IETF redefined the meaning of the word "site"?
> In plain English, this word refers to a distinct physical location such
> as an office or building or campus.

That's true, in plain English. However, as the agonising over
deprecating site-local showed, it doesn't quite work in the
Internet since corporate intranets arose. So it has certainly
been used in IPv6 discussions for anything from a dentist's
office network up to a corporate network with multiple
physical sites and multiple interconnects to the Internet.
I think that's why the word "site" is not part of the
name of a ULA. It creates confusion.

     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 Jul 02 05:18: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 1I5I3A-0008LS-3K; Mon, 02 Jul 2007 05:18:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5I38-0008Eu-Ae
	for ipv6@ietf.org; Mon, 02 Jul 2007 05:18:26 -0400
Received: from mu-out-0910.google.com ([209.85.134.191])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5I2k-0000DZ-8Q
	for ipv6@ietf.org; Mon, 02 Jul 2007 05:18:26 -0400
Received: by mu-out-0910.google.com with SMTP id w8so1861227mue
	for <ipv6@ietf.org>; Mon, 02 Jul 2007 02:18:01 -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=PG1lsmDbgrPoOegiNd6upCCqUNhK++gwJ0hjzmAhWVTTRWKDQJcZ3lt/YvZ5OKnUbwNH39F4ko+jX7G1FE0A3oWVxMkdHYghG4jFp3oIDdxqHLasdIFz50CMiUO9hA47SF09AGt44Jwl2JgYNQmGFWnQoUScqqZwuLFn49RJ0UI=
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=hELS44xfqqbWaBsDKxJHCkPVdeEYi0BfYkKK5Nilver+I9gkLAoPsTkO89RBuVnU+nYEeYYjYC7C87I66h+61romtl/7h/9exCSK9meUHBSsefJr1N38IfImG/Au5VzSAGtQESadlCSacLDN4BgjTnDt4V2u5pe0YLq7by6TAQg=
Received: by 10.82.146.14 with SMTP id t14mr12487702bud.1183367881043;
	Mon, 02 Jul 2007 02:18:01 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id h6sm34127636nfh.2007.07.02.02.17.59
	(version=SSLv3 cipher=RC4-MD5); Mon, 02 Jul 2007 02:17:59 -0700 (PDT)
Message-ID: <4688C2CA.5050302@gmail.com>
Date: Mon, 02 Jul 2007 11:18:02 +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>	<4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>
In-Reply-To: <27414.1183131210@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
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

Paul,

On 2007-06-29 17:33, Paul Vixie wrote:
> 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.

Absolutely. I know what "rough" means in "rough consensus".

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

OK, I didn't intend to be emotional there. Let me try to explain. Until
we get something fundamentally different from the routing researchers,
the only model we have is BGP4, and the only way we have to control
the growth in BGP4 table size and dynamics is aggregation. That's basic
and hasn't changed in 25 years. That's why CIDR saved us. So I really
only see two kinds of IP prefix - those that aggregate and those that
don't. We need to encourage the former and discourage the latter (as
far as seeing them in BGP is concerned). In today's jargon, that means
encouraging PA, and limiting PI to a few thousand users that really need
it. ULA-C with structure as you propose is a form of PI. I believe it will
be perceived as an easy way to get PI space, and the pressure to stick
ULA-C prefixes of this kind in the DFZ will become very hard to resist.
I don't see that risk being anywhere near as high for current ULAs
or for centrally registered random ULAs.

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

I assume we all want the routing system to continue to scale at an
economically sustainable rate. Can you show that structured ULA-C will be
added to the DFZ at a sufficiently low rate that we won't get into
trouble? What's your estimate of the total number of ULA-C prefixes
needed?

If those numbers fit within reasonable guesses about sustainable
DFZ growth, no problem.

     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 Jul 02 05:24: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 1I5I8k-00060L-Ck; Mon, 02 Jul 2007 05:24:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5I8i-00060F-G3
	for ipv6@ietf.org; Mon, 02 Jul 2007 05:24:12 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5I8e-0002e9-60
	for ipv6@ietf.org; Mon, 02 Jul 2007 05:24:12 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1325791uge
	for <ipv6@ietf.org>; Mon, 02 Jul 2007 02:24: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=ERXU7/hc8qE7j1LLEpdkdZLfS5EUZGM4exJLRbStfRGomauPG2X0CTR2xdEpwFsh1x7uJbZimGkkbxCGRa+ElwyznVovBrE4iOfRA0NenDYF9YgGtd07W9IkWq/KQEu/srepoBcqIegekq6F5u+WINsAikRQ5NSm8mgbRSMzHAs=
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=ONpKy8J9xu9k6YdyxccJSXkflqR4p0UkXvSfwyKRuW5fHvtVXclAMkGc/mIrX8UPHfZwye7UF7hZ6IWFeKqfXs3MbRQS5ejcThmf0iY2hgTWmD7sugg0pyncKFdRYqHeEWjk3wpikCawzr6X7mzyFFYPj7JwO1yQwS0isRDOcNU=
Received: by 10.78.178.5 with SMTP id a5mr2800263huf.1183368247073;
	Mon, 02 Jul 2007 02:24:07 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id k5sm1622024nfd.2007.07.02.02.24.06
	(version=SSLv3 cipher=RC4-MD5); Mon, 02 Jul 2007 02:24:06 -0700 (PDT)
Message-ID: <4688C439.9050906@gmail.com>
Date: Mon, 02 Jul 2007 11:24: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: briand@ca.afilias.info
References: <E1I4Itf-0000xW-Oa@megatron.ietf.org>
	<62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
In-Reply-To: <62790.74.122.168.81.1183142831.squirrel@look.libertyrms.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
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 D,

On 2007-06-29 20:47, briand@ca.afilias.info wrote:

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

There are more motivations than that - the ability to generate a ULA
prefix automatically, for example, allows a zero-config disconnected
network to come up with a valid prefix that could in fact be used
for ad-hoc routing with a neighbour. And there are lots of enterprise
scenarios where private address space is highly desired.

Without regard to what is decided about ULA-C, I think ULA is here
to stay.

    Brian C


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



From ipv6-bounces@ietf.org Mon Jul 02 08:19: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 1I5KsF-0005Tr-4a; Mon, 02 Jul 2007 08:19:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5KsC-0005Ce-Rj
	for ipv6@ietf.org; Mon, 02 Jul 2007 08:19:20 -0400
Received: from isc.trstech.net ([2001:4f8:0:1::23:2] helo=afribone.trstech.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Ks3-0001R5-9d
	for ipv6@ietf.org; Mon, 02 Jul 2007 08:19:20 -0400
Received: from [41.207.162.3] (helo=[192.168.1.12])
	by afribone.trstech.net with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.66) (envelope-from <aalain@afribone.trstech.net>)
	id 1I5KpF-0006aC-HV
	for ipv6@ietf.org; Mon, 02 Jul 2007 12:17:23 +0000
From: Alain Patrick AINA <aalain@trstech.net>
Organization: technologies =?iso-8859-1?q?r=E9seaux_et_Solutions?=
	(www.trstech.net)
To: ipv6@ietf.org
Date: Mon, 2 Jul 2007 12:17:45 +0000
User-Agent: KMail/1.9.7
References: <20070627204814.GR31273@elvis.mu.org>
In-Reply-To: <20070627204814.GR31273@elvis.mu.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200707021217.45932.aalain@trstech.net>
X-SA-Exim-Connect-IP: 41.207.162.3
X-SA-Exim-Mail-From: aalain@afribone.trstech.net
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on 
	afribone.trstech.net
X-Spam-Level: 
X-Spam-Status: No, score=-3.6 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	DNS_FROM_RFC_ABUSE autolearn=ham version=3.1.4
X-SA-Exim-Version: 4.2.1 (built Wed, 24 Jan 2007 18:13:53 +0000)
X-SA-Exim-Scanned: Yes (on afribone.trstech.net)
X-Spam-Score: 4.7 (++++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: Re: AfriNIC, ULA-C, & "why not just get PI space"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: aalain@trstech.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

On Wednesday 27 June 2007 08:48:14 pm bill fumerola wrote:
> 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.


The status has been fixed. 

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

no.

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

the PI policy was not developed and discussed to cover the ULA-C needs.
The ULA-C proposal did  not reach concensus in our region and the outcome of 
the IETF discussions is awaited. But nothing prevents the region for changing 
the PI policy.

--alain





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



From ipv6-bounces@ietf.org Mon Jul 02 11:39: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 1I5NzK-00033n-CP; Mon, 02 Jul 2007 11:38:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5NzI-00033h-WA
	for ipv6@ietf.org; Mon, 02 Jul 2007 11:38:52 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5NyM-00085x-GY
	for ipv6@ietf.org; Mon, 02 Jul 2007 11:38:52 -0400
Received: from boreas.isi.edu (localhost [127.0.0.1])
	by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id l62EncjF023840
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 2 Jul 2007 07:49:39 -0700 (PDT)
Received: (from bmanning@localhost)
	by boreas.isi.edu (8.13.8/8.13.8/Submit) id l62Enc42023827;
	Mon, 2 Jul 2007 07:49:38 -0700 (PDT)
Date: Mon, 2 Jul 2007 07:49:38 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Joe Abley <jabley@ca.afilias.info>
Message-ID: <20070702144938.GA21244@boreas.isi.edu>
References: <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>
	<DC98B27B-38A6-48FF-99D1-75F760D14EE7@ca.afilias.info>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DC98B27B-38A6-48FF-99D1-75F760D14EE7@ca.afilias.info>
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: c1c65599517f9ac32519d043c37c5336
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 Sun, Jul 01, 2007 at 06:21:10PM -0400, Joe Abley wrote:
> Very late to this party, but:
> 
> On 27-Jun-2007, at 09:11, 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.
> >Architecturally, they are certainly routeable (and so are /128s).
> >But I am sure they will be filtered.
> 
> I hope they won't all be filtered, since there are a non-trivial  
> number of infrastructure services in the DNS which are deployed  
> using /48s assigned directly from RIRs under policies designed to  
> facilitate critical infrastructure.
> 
> I realise that you were talking in far more general terms than this,  
> but every time I see someone make blanket statements about "/48s" and  
> their presence in the DFZ it makes me twitch. Not all /48s are  
> components of larger assignments or allocations.

	actually, to borrow a phrase from a mutual associate,
	"I encourage Brian (and others) to filter /48s" .... :)
	
	i think that it will make their IPv6 experience that much
	more enjoyable/useful.

--bill

> 
> 
> Joe
> 
> 
> 
> --------------------------------------------------------------------
> 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 Mon Jul 02 12: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 1I5PAF-0000mb-Gd; Mon, 02 Jul 2007 12:54:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5PAD-0000mV-Vw
	for ipv6@ietf.org; Mon, 02 Jul 2007 12:54:13 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5P9Y-0006B3-6R
	for ipv6@ietf.org; Mon, 02 Jul 2007 12:54:13 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 4F98E11433
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 16: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 "Mon, 02 Jul 2007 11:18:02 +0200."
	<4688C2CA.5050302@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> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Jul 2007 16:53:31 +0000
Message-ID: <43704.1183395211@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
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>:
> 
> OK, I didn't intend to be emotional there. Let me try to explain. Until
> we get something fundamentally different from the routing researchers,
> the only model we have is BGP4, ...

i've heard of alternatives but you're right that nothing else has caught on.

>                                 ... and the only way we have to control the
> growth in BGP4 table size and dynamics is aggregation.  That's basic and
> hasn't changed in 25 years. That's why CIDR saved us. 

no.  i don't have objective measurements, but i know that a lot of table size
control is achieved by limiting the horizon of announcements.  ULA-C with my
proposed diffs is just a way to take this a lot further, to legitimize it, to
scale it up to planetary size.

there's been a fundamental misunderstanding in the acadamy as to what actually
happens in the field.  ietf thought that the only connectivity that mattered
was universal connectivity, and fought firewalls and nat for a long while, but
ultimately firewalls and nat and RFC 1918 were all great things for the
internet even though they "violated" the universal connectivity assumptions.

for the record, table size only matters in the DFZ, and only because there are
too many third parties for the budget of any one of them to govern the size of
the table.  away from the DFZ, table size is a self limiting problem, and no
questions of aggregation are even pertinent.

> So I really only see two kinds of IP prefix - those that aggregate and those
> that don't.

that's an extremely informative statement, thank you for sharing it.

> We need to encourage the former and discourage the latter (as far as seeing
> them in BGP is concerned).

if you mean by "BGP", the DFZ, then i'd agree with this statement in isolation
from the one that came before it.

> In today's jargon, that means encouraging PA, and limiting PI to a few
> thousand users that really need it. ULA-C with structure as you propose is a
> form of PI. I believe it will be perceived as an easy way to get PI space,
> and the pressure to stick ULA-C prefixes of this kind in the DFZ will become
> very hard to resist.  I don't see that risk being anywhere near as high for
> current ULAs or for centrally registered random ULAs.

harken back to the above where i referenced "many third parties".  in the DFZ,
what matters is what the tier-1 providers do.  they can afford 2-megaroute
forwarding machinery, they compete aggressively for end-sites against both
other tier-1's and all of the regional or value-add or low-cost tier-2's, and
they really like the PA concept because the renumbering penality gives them a
form of lock-in that even microsoft and apple can only dream about.  if the
tier-1's decide to exchange ULA-C routes with each other, then the rest of the
internet has to do likewise.  and if some really large cash cow of a customer
puts out an RFP to tier-1 saying "we'll buy bandwidth from whoever will route
our ULA-C into the internet core" then it'll be very interesting.  is this
your proposed "pressure to stick" comes from?  because i can think of a dozen
reasons why it can't happen, all based on business strategy and self-interests
of every single party involved in that money chain.

the competing visions as i understand them are "random-prefix ULA-C makes it
impossible to postprocess one's log files on computers outside the
connectivity realm where they were gathered, makes recourse against spammers
and ddos-for-hire crews even harder, and moves the hijacking problem from the
realm where RPKI can help some day to the realm of ``i got it from agnes''(*)"
and "assigned-prefix ULA-C makes it likely that the PI/PA separation regime
will collapse, and take the internet down in flames."

(*) http://www.lyricsdir.com/tom-lehrer-i-got-it-from-agnes-lyrics.html

> I assume we all want the routing system to continue to scale at an
> economically sustainable rate. Can you show that structured ULA-C will be
> added to the DFZ at a sufficiently low rate that we won't get into
> trouble?

i predict that structured ULA-C will enter the DFZ at the rate of zero, since
there will be an RFC which excuses anyone who wants to filter it out, and 
since there will be many more champions whose livelihoods are threatened by
it than whose livlihoods could be enriched by it.  (it's all about the money.)

> What's your estimate of the total number of ULA-C prefixes needed?

approximately one per family, worldwide, counting only the population who has
electric power.  much much higher than the 2-megaroute level, or the number
of domain names registered in .COM and .DE (the two largest TLDs).

> If those numbers fit within reasonable guesses about sustainable
> DFZ growth, no problem.

they don't fit, but they don't have to fit, because they're not going in.

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



From ipv6-bounces@ietf.org Mon Jul 02 13:06: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 1I5PMC-0001GI-3U; Mon, 02 Jul 2007 13:06:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5PMA-00017H-Ua
	for ipv6@ietf.org; Mon, 02 Jul 2007 13:06:34 -0400
Received: from vms046pub.verizon.net ([206.46.252.46])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5PM2-0000cZ-Kb
	for ipv6@ietf.org; Mon, 02 Jul 2007 13:06:34 -0400
Received: from vms062.mailsrvcs.net ([192.168.1.2])
	by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JKK00KX2A67T4H9@vms046.mailsrvcs.net> for
	ipv6@ietf.org; Mon, 02 Jul 2007 12:06:08 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms062.mailsrvcs.net (Verizon Webmail) with HTTP; Mon,
	02 Jul 2007 12:06:07 -0500 (CDT)
Date: Mon, 02 Jul 2007 12:06:07 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: IPv6 WG <ipv6@ietf.org>, ext Bob Hinden <bob.hinden@nokia.com>
Message-id: <29236888.12332831183395967149.JavaMail.root@vms062.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
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

I support the promotion of draft-ietf-ipv6-deprecate-rh0-01.txt to a Proposed Standard.

IMO the editor and author(s) did an exceptionally good job in distilling our many and often somewhat divergent comments into the document we're considering.

The above having been said, I'd like to share one _suggestion_ (to be redundant, it is just a suggestion).

Section 4.2 (now): "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."

I don't see it as necessary to dictate firewall policy (particularly to the degree that it is here... for the remaining RH types) in this draft. The original intent, as I understood it, was to call for the deprecation of RH0 and state why.

If dictating firewall policy (for the remaining RH types) must be done in this draft, I'd at least prefer  to see more concise language. A _suggestion_:

"A de facto discarding of all packets containing any routing headers is inappropriate (and may hamper future functionality using other routing headers). Presently, Mobile IPv6 uses Routing Header Type 2 [RFC 3775].

Firewall policy (intended to protect against RH0) MUST have the ability to handle routing headers by specific type."

Regardless of the exact language that's employed, I can almost hear people saying (something like):

"My firewall doesn't have the granularity to filter on RH type. From reading this RFC, it seems we shouldn't filter on any RH. But what about the dangers associated with RH0? I know that ingress filtering doesn't completely solve the problem. What do I do?"

__________

Best Regards,

Tim Enos
Rom 8:28-39

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


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



From ipv6-bounces@ietf.org Mon Jul 02 14:10: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 1I5QMB-0002Gn-RR; Mon, 02 Jul 2007 14:10:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5QMA-0002Gf-OF
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:10:38 -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 1I5QM4-0007ab-7D
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:10:38 -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 l62Hp21A016055; 
	Mon, 2 Jul 2007 10:51:10 -0700 (PDT)
	(envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service);
	Mon, 02 Jul 2007 11:10:25 -0700
X-PGP-Universal: processed;
	by terminus.local on Mon, 02 Jul 2007 11:10:25 -0700
In-Reply-To: <43704.1183395211@sa.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>
	<4684DB4A.2060703@gmail.com> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
From: David Conrad <drc@virtualized.org>
Date: Mon, 2 Jul 2007 11:10:16 -0700
To: Paul Vixie <paul@vix.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: cf4fa59384e76e63313391b70cd0dd25
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

>> What's your estimate of the total number of ULA-C prefixes needed?
> approximately one per family, worldwide, counting only the  
> population who has
> electric power.  much much higher than the 2-megaroute level, or  
> the number
> of domain names registered in .COM and .DE (the two largest TLDs).
>> If those numbers fit within reasonable guesses about sustainable
>> DFZ growth, no problem.
> they don't fit, but they don't have to fit, because they're not  
> going in.

How is this going to work?  Are you assuming NATv6?

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 Mon Jul 02 14:19: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 1I5QUU-0007nm-DM; Mon, 02 Jul 2007 14:19:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5QUT-0007nc-5k
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:19:13 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5QTp-00014c-RY
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:19:13 -0400
Received: from auguste.remlab.net (cs78150156.pp.htv.fi [62.78.150.156])
	(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 DC011967F7
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 20:18:32 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: IPv6 WG <ipv6@ietf.org>
Date: Mon, 2 Jul 2007 21:18:26 +0300
User-Agent: KMail/1.9.7
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
In-Reply-To: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
MIME-Version: 1.0
Message-Id: <200707022118.31271@auguste.remlab.net>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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>
Content-Type: multipart/mixed; boundary="===============1817108664=="
Errors-To: ipv6-bounces@ietf.org

--===============1817108664==
Content-Type: multipart/signed; boundary="nextPart1301292.P9doXXbxa7";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1301292.P9doXXbxa7
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Le jeudi 28 juin 2007, ext Bob Hinden a =E9crit :
> 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.

Document is fine with me. But what are the consequences with regards to=20
RFC3542? Should implementations stop parsing RH0 at that level as well?

=2D-=20
R=E9mi Denis-Courmont
http://www.remlab.net/

--nextPart1301292.P9doXXbxa7
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)

iEYEABECAAYFAkaJQXcACgkQw+xtvt1tEr1W0wCgqm17OGyiidRWKxjrCWryylVF
B+kAoI7VBuDICmCanum+lu7WACKz/lbg
=SwjW
-----END PGP SIGNATURE-----

--nextPart1301292.P9doXXbxa7--


--===============1817108664==
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
--------------------------------------------------------------------

--===============1817108664==--




From ipv6-bounces@ietf.org Mon Jul 02 14: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 1I5Qdt-00069P-Ae; Mon, 02 Jul 2007 14:28:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Qdr-000651-Di
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:28:55 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5Qdo-0002EV-FI
	for ipv6@ietf.org; Mon, 02 Jul 2007 14:28:55 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 1085411437
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 18:28: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 "Mon, 02 Jul 2007 11:10:16 MST."
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org> 
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>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 02 Jul 2007 18:28:52 +0000
Message-ID: <58873.1183400932@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

> >> If those numbers fit within reasonable guesses about sustainable
> >> DFZ growth, no problem.
> 
> > they don't fit, but they don't have to fit, because they're not  going in.
> 
> How is this going to work?  Are you assuming NATv6?

no.  i'm assuming that the days when the DFZ was the center of the internet
are going to end some day.  ad-hoc networking, neighborhood networking,
city networking, personal networking.  folks will use NATv6 or proxies or
PI or PA when they're going through the DFZ.  a lot of the time ULA-C will
be all they need.

(note, this means i think networking will flow along lines defined by enduser
interest, feature levels, technology capabilities, and money; and not by what
the ivory tower folks predict or demand.)

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



From ipv6-bounces@ietf.org Mon Jul 02 16:05: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 1I5S9L-0001Q4-6x; Mon, 02 Jul 2007 16:05:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5S9J-0001Pz-Kw
	for ipv6@ietf.org; Mon, 02 Jul 2007 16:05:29 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5S8z-0007hh-Fp
	for ipv6@ietf.org; Mon, 02 Jul 2007 16:05:29 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 02 Jul 2007 16:05:01 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnoUAB72iEZAZnmf/2dsb2JhbAATglSaPg
X-IronPort-AV: i="4.16,488,1175486400"; d="scan'208,217";
	a="125081668:sNHT19631477354"
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 l62K51gH004273
	for <ipv6@ietf.org>; Mon, 2 Jul 2007 16:05:01 -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 l62K4i6w009490
	for <ipv6@ietf.org>; Mon, 2 Jul 2007 20:05:01 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, 2 Jul 2007 16:04:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 2 Jul 2007 16:04:51 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589AB6@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of draft-wbeebee-nd-implementation-pitfalls is
	available - last was 00, new one is 01
Thread-Index: Ace85D++a7cUhtKPTx2qQDEU5NAs4g==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "IETF Mailing List IPv6" <ipv6@ietf.org>
X-OriginalArrivalTime: 02 Jul 2007 20:04:53.0535 (UTC)
	FILETIME=[412C82F0:01C7BCE4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5814; t=1183406701;
	x=1184270701; 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:=20New=20version=20of=20draft-wbeebee-nd-implementation-pitfalls
	=20is=20available=20-=20last=20was=2000,=20new=20one=20is=2001
	|Sender:=20
	|To:=20=22IETF=20Mailing=20List=20IPv6=22=20<ipv6@ietf.org>;
	bh=tGvRJWV7X2VtJfxxejrcm07gc7ou/ThEXA9b0M8/xGg=;
	b=HPIEAuCPwQjrK8XEf2DNiV3LLEDYbJ8cD/+x//JeIghA+im2fot9ug9/t3fa/+Vg4B75rclY
	ozFQt7GU/lGK1mc6fjOdX/NG7IViM4NS+cgukpr1+j0RfotkbZlqUJq2;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: 
Subject: New version of draft-wbeebee-nd-implementation-pitfalls is
	available - last was 00, new one is 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="===============0314505481=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0314505481==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BCE4.40F360B8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BCE4.40F360B8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,
=20
We had to get this new one out since we last discussed the -00 version
mainly with Tatuya and Brian Carpenter. The URL to the new one is:
=20
http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
alls-01.txt
=20
Relevant points with the new I-D are below.
=20
1. Please read the last two lines of Abstract to understand what our
proposal with this I-D is.
=20
2. 2461bis folks, please jump to reviewing this version, especially the
new section 5 of our I-D that lists normative changes we propose for
2461bis.
=20
3. 2462bis folks, the old section 5 relating to you is now section 6.
Please review this section. As agreed between us and Tatuya, we are no
longer requiring that old hosts MUST NOT skip DAD. However we still
would like the problem we report in bullet 4, Section 2 of our I-D to be
reflected as text in 2462bis.  The combination of skipping DAD and
manual configuration causes NEW and important problems which are not
described in 2462bis and are more relevant than the reasoning described
in 2462bis for not skipping DAD. The only reason given in 2462bis for
not skipping DAD is "new types of addresses have been introduced where
the interface identifiers are not necessarily the same for all unicast
addresses on a single interface [RFC3041] [RFC3972]".  The problem we
report occurs even when Host2 uses the same identifier to create all
IPv6 addresses for an interface and skips DAD for GUA. We feel that if
implementers and deployers of IPv6 were made aware of the problem with
skipping DAD and manual configuration, that they would be more
incentivised to upgrade.
=20
Thanks,
=20
- Hemant & Wes

------_=_NextPart_001_01C7BCE4.40F360B8
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><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007>We had =
to get this=20
new one out since we last discussed the -00 version mainly with Tatuya=20
and&nbsp;Brian Carpenter. The URL to the new one is:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementati=
on-pitfalls-01.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-nd-=
implementation-pitfalls-01.txt</A></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D553183619-02072007>Relevant points with=20
the new I-D are below.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007>1. =
Please read the=20
last two lines of Abstract to understand what our proposal with this I-D =

is.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007>2. =
2461bis folks,=20
please jump to reviewing this version, especially the new section 5 of =
our I-D=20
that lists normative changes we propose for 2461bis.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007>3. =
2462bis folks,=20
the old section 5 relating to you is now section 6. Please review this =
section.=20
As agreed between us and Tatuya, we are no longer requiring that old =
hosts MUST=20
NOT skip DAD. However we still would like the problem we report in =
bullet 4,=20
Section 2 of our I-D to be reflected as text in 2462bis.&nbsp; The =
combination=20
of skipping DAD and manual configuration causes&nbsp;NEW and=20
important&nbsp;problems which are not described in 2462bis and are=20
more&nbsp;relevant than the&nbsp;reasoning&nbsp;described in 2462bis for =
not=20
skipping DAD.&nbsp;The only reason given in 2462bis for not skipping DAD =
is "new=20
types of addresses have been introduced where the interface identifiers =
are not=20
necessarily the same for all unicast addresses on a single interface =
[RFC3041]=20
[RFC3972]".&nbsp; The problem we report occurs even when Host2 uses the =
same=20
identifier to create all IPv6 addresses for an interface and skips DAD =
for=20
GUA.&nbsp;</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007>We feel that if implementers and deployers of =
IPv6 were=20
made aware of the problem with skipping DAD and manual configuration, =
that they=20
would be more incentivised to upgrade.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007>Thanks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D553183619-02072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D553183619-02072007>- =
Hemant &amp;=20
Wes</SPAN></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C7BCE4.40F360B8--


--===============0314505481==
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
--------------------------------------------------------------------

--===============0314505481==--




From ipv6-bounces@ietf.org Mon Jul 02 19:30: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 1I5VLK-0004ZC-RA; Mon, 02 Jul 2007 19:30:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5VLJ-0004Xh-Dt
	for ipv6@ietf.org; Mon, 02 Jul 2007 19:30:05 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5VL9-00008G-31
	for ipv6@ietf.org; Mon, 02 Jul 2007 19:30:05 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 4936D11432
	for <ipv6@ietf.org>; Mon,  2 Jul 2007 23:29:54 +0000 (UTC)
	(envelope-from vixie@sa.vix.com)
From: Paul Vixie <paul@vix.com>
To: ipv6@ietf.org
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Date: Mon, 02 Jul 2007 23:29:54 +0000
Message-ID: <1436.1183418994@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Subject: re: Internet Draft Submission Manager:
	draft-ietf-ipv6-ula-global-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

--=-=-=

i took a copy of ula-central-02 and modded it with my current thinking and
submitted it as a new draft.  i did three things wrong, first i didn't ask
the authors of central-02 if they wanted to be listed as authors of global-01
(but i didn't remove their names since a lot of the text was written by them).
second, i missed the cutoff for new drafts by a day.  third, i called it -01
rather than -00 even though its a new document not just a new revision (but
note, if the other guys want to take this idea into central-03 i'd abandon
global-01 in a heartbeat.)

anyway it's at <http://sa.vix.com/~vixie/ula-global.txt> and comments are
welcome here on ipv6@ even though i guess we won't be discussing it in
chicago since i'm a day late.

re:


--=-=-=
Content-Type: message/rfc822
Content-Disposition: attachment; filename=1196
Content-Description: forwarded message

Return-Path: <exim@ietf.org>
X-Original-To: paul@vix.com
Delivered-To: vixie@sa.vix.com
X-Greylist: delayed 00:28:46.679017 by SQLgrey-1.4.8
Received: from ns3.neustar.com (ns3.neustar.com [156.154.24.138])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "Neustar", Issuer "Neustar" (not verified))
	by sa.vix.com (Postfix) with ESMTP id 7C22911433
	for <paul@vix.com>; Mon,  2 Jul 2007 20:56:42 +0000 (UTC)
	(envelope-from exim@ietf.org)
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 6012D1762D
	for <paul@vix.com>; Mon,  2 Jul 2007 20:27:50 +0000 (GMT)
Received: from exim by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I5SUv-0001bh-Vv for paul@vix.com; Mon, 02 Jul 2007 16:27:49 -0400
To: Paul Vixie <paul@vix.com>
Cc: 
From: Internet Draft Submission Manager <internet-drafts-reply@ietf.org>
Subject: [Auto Response] draft-ietf-ipv6-ula-global-01.txt
Message-Id: <E1I5SUv-0001bh-Vv@stiedprstage1.ietf.org>
Date: Mon, 02 Jul 2007 16:27:49 -0400

Greetings:

This message is being sent to acknowledge receipt of your Internet-Draft
submission or message to internet-drafts@ietf.org.  Please note that the
pre-meeting cutoff date for new documents (i.e., version -00 
Internet-Drafts) was Monday, July 2 at 9:00 AM ET.
Your submission was received after this time.  The Internet-Drafts 
administrator will examine your submission, and the posting decision 
will be made as follows:

* If you submitted a version -00 Internet-Draft before the cutoff 
  deadline, then your document will be posted on the Internet-Drafts 
  page of the IETF Web site as soon as possible, and an I-D Action 
  message will be sent to the I-D Announce List.  If your document was
  submitted before the cutoff deadline, but was rejected due to 
  boilerplate or format issues, then the Internet-Drafts administrator 
  will work with you to attempt to resolve these issues and post the 
  document in time for the meeting. 

* If you submitted a version -00 Internet-Draft after the cutoff 
  deadline, then your document will NOT be processed until on or after 
  Monday, July 23 at 9:00 AM ET, when Internet-Draft 
  posting resumes.

* If you submitted a version -01 or higher Internet-Draft, then your 
  document will be posted on the Internet-Drafts page of the IETF Web 
  site as soon as possible, and an I-D Action message will be sent to 
  the I-D Announce List.

As you may be aware, the pre-meeting cutoff date for updated submissions
is Monday, July 9 at 9:00 AM ET.  Since the 
Secretariat receives a large number of Internet-Drafts in the week 
preceding the cutoff date for updated submissions, your document may 
not be processed and announced for a number of days.  Our goal is to 
process and announce all valid pre-meeting Internet-Draft submissions 
by Friday, July 13 at the latest.  
If you need to track the status of your Internet-Draft submission, then
please send a note to ietf-action@ietf.org (using the suggested subject
line Status of I-D Submission: <filename>) and reference this 
auto-response acknowledgement in the body.

Please note that all Internet-Drafts offered for publication as RFCs 
must conform to the requirements specified in the ID-Checklist 
(http://www.ietf.org/ID-Checklist.html) or they will be returned to the
author(s) for revision.  Therefore, the IETF Secretariat strongly 
recommends that you address all of the issues raised in this document 
before submitting a request to publish your Internet-Draft to the IESG.

The IETF Secretariat



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

--=-=-=--




From ipv6-bounces@ietf.org Mon Jul 02 21:54: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 1I5XaU-0004xA-E4; Mon, 02 Jul 2007 21:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5XaQ-0004Yq-KW
	for ipv6@ietf.org; Mon, 02 Jul 2007 21:53:50 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5XaM-0004uP-Aj
	for ipv6@ietf.org; Mon, 02 Jul 2007 21:53:50 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id AD6D41A4D8B; Mon,  2 Jul 2007 18:53:45 -0700 (PDT)
Date: Mon, 2 Jul 2007 18:53:45 -0700
From: bill fumerola <billf@mu.org>
To: Alain Patrick AINA <aalain@trstech.net>
Message-ID: <20070703015345.GK9951@elvis.mu.org>
References: <20070627204814.GR31273@elvis.mu.org>
	<200707021217.45932.aalain@trstech.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200707021217.45932.aalain@trstech.net>
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: b19722fc8d3865b147c75ae2495625f2
Cc: ipv6@ietf.org
Subject: Re: 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

On Mon, Jul 02, 2007 at 12:17:45PM +0000, Alain Patrick AINA wrote:
> > 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.
> 
> no.

please elaborate.

> the PI policy was not developed and discussed to cover the ULA-C needs.
> The ULA-C proposal did  not reach concensus in our region and the outcome of 
> the IETF discussions is awaited. But nothing prevents the region for changing 
> the PI policy.

and as i said:
>>> 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.

this is not a slam at the afrinic decision and it is in the realm of the
RIRs to make/change policy such as requiring your allocate PIv6 space
to be announced to the DFZ. i brought it up as advice to this workgroup
to understand that the "drop ULA-C, people {could,should} just use PI"
argument may or may not hold water at any given place in space and time.

the IETF has the ability here (through delegation to IANA) to make sure
that IANA/RIRs have the ability to issue ULA-C prefixes, if they desire
to.

-- 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 Jul 02 23:27: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 1I5Z2w-0004xQ-67; Mon, 02 Jul 2007 23:27:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Z2u-0004uR-95
	for ipv6@ietf.org; Mon, 02 Jul 2007 23:27:20 -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 1I5Z2p-0000VC-DC
	for ipv6@ietf.org; Mon, 02 Jul 2007 23:27:20 -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 1I5Z2k-0003zB-UY; Mon, 02 Jul 2007 23:27:10 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 2 Jul 2007 23:27:10 -0400 (EDT)
Message-ID: <63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
In-Reply-To: <58873.1183400932@sa.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>
	<4684DB4A.2060703@gmail.com> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
Date: Mon, 2 Jul 2007 23:27:10 -0400 (EDT)
From: briand@ca.afilias.info
To: "Paul Vixie" <paul@vix.com>
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: 156eddb66af16eef49a76ae923b15b92
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

>> >> If those numbers fit within reasonable guesses about sustainable
>> >> DFZ growth, no problem.
>>
>> > they don't fit, but they don't have to fit, because they're not  going
>> in.
>>
>> How is this going to work?  Are you assuming NATv6?
>
> no.  i'm assuming that the days when the DFZ was the center of the
> internet
> are going to end some day.  ad-hoc networking, neighborhood networking,
> city networking, personal networking.  folks will use NATv6 or proxies or
> PI or PA when they're going through the DFZ.  a lot of the time ULA-C will
> be all they need.
>
> (note, this means i think networking will flow along lines defined by
> enduser interest, feature levels, technology capabilities, and money

Let's not also forget about convenience, and pain.

Here's the main difference between unannounced PI space, and  ULA-C:
ULA-C is designed to never be directly announced into the DFZ.

I've been giving considerable thought to the use cases, and in particular
what it would be like to be responsible for networks at various places
in the topologies of both strictly off-grid ("local", or multi-local),
and connected to and primarily using the DFZ ("Internet" as we think of
it for IPv4).

The interesting thing is, one person's PI is another person's PA.
By that I mean, that the difference between PI and PA, is subjective.

The assignee of a PI block, who then allocates it as PA sub-blocks, is
what differentiates PA from PI. PA exists only from the perspective of the
assignee herself.

The general idea is that the bulk of address assignments used should be,
one would expect and hope, PA, and aggregated, into large assignments
of PI blocks (ideally one per ASN) in the DFZ. The scalability of the
DFZ depends on this, in fact.

On the other hand, PA is a form of "lock-in". Renumbering is painful,
if the scope of the renumbering is large.

If a PA assignment is directly to an "end user", e.g. an enterprise,
this in theory isn't likely to be a large scope, or is at least manageable.

It is when the PA assignments are further subassigned, that the scope
becomes a significant issue, and the pain (of renumbering) grows.

For example, if a large PA block has been given out, and further assigned
to hundreds of customers (of the PA block recipient), each of which has
DNS servers "on the block", if the recipient needs to renumber, the pain
is prohibitive.

Placing the potential recipient in the position of having
to choose between PA, and a difficult-and-costly-to-obtain PI block,
is by its nature harmful to the deployment of IPv6.

And it is for this reason that I advocate reducing or eliminating
costs, and relaxing the requirements for receiving PI space.
For instance, deferring the costs of PI space until the PI block is
added into the DFZ, is one option.

And admittedly, it is the interactions of 1:1 NAT and DNS that causes most
of the problems, under any scheme for handling relocation in connectivity
to the DFZ.

If we presume that PA allocators (e.g. ISPs), in their own
mutual self-interest, regardless of what is on the other side of the link,
limit ingress traffic only to the PA block itself, then what is on the
other side isn't terribly important. (Similar to BCP-38 for IPv4)

And, accordingly, the ingress traffic could be native (the PA block itself),
or 1:1 NATv6 from ULA-C space, or 1:1 NATv6 from PI space.

In a hierarchy of PI-PA assignments, it fundamentally does not matter
whether the PA block itself is being sub-assigned, or if a separate PI
block from which 1:1 NATv6 is instead PA'd and sub-assigned.

There is definitely room for DNS having hooks for handling the 1:1 NAT
issues - and this has to do with the fact that multiple 1:1 NAT'ing can
occur over a single portion of address space.

In the absence of this, however, there are a number of tricks for working
around this, that are workable enough and scalable enough, for the short
term. The very fact that 1:1 NAT tends to be "sticky" (long-lived), and
that 1:1 NAT is deterministic, and even possible to reverse at the edges
of the DFZ.

(I think for clarity, it would be best to discuss those tricks in a
separate thread. But there are definite, concrete approaches that can be
applied, to the best of my knowledge, with currently deployed code.)

The fact that 1:1 NAT isn't strictly a two-tier technology, and that the
total amount of theoretical address space is so immense, even when used in
a particularly inefficient manner, means that doubling or tripling the
effective use (by heavy use of 1:1 NAT), is not a significant cost.

Use of 1:1 NAT keeps the DFZ to a bare minimum, while still giving all the
flexibility for back-door networking at arbitrary scale.

Still, the question of what to use for the other side of NAT is important,
at least in terms of what kinds of solutions to promote, to support in
the IETF protocol and address specifications, and in the RIR policies.

What I propose is, that PI assignment be very significantly relaxed and
promoted, for use in this case.

Why?

Because, use of ULA-C for the other side of PA NATing means that should
an organization at some point need to have multihomed connectivity, the
site would need to renumber. This is because (stating the obvious) only
PI blocks can be announced into the DFZ, and ULA-C are specifically not
allowed into the DFZ.

If, on the other hand, any organization that foresees, at any point in
time, needing to be multihomed, getting PI space early and using it,
with NATv6 into PA space (for access to the DFZ), all is good.

The fact that this scales recursively is also good. Each link in the
chain is a PA to PI mapping (NATv6). And every enterprise in the tree under
a PI in the DFZ, while having its own PI block, while it is single homed,
is still aggregated into a single PI block in the DFZ.

So, the scalability of the DFZ is still limited by growth of entities
which require their own PI block, and renumbering is accomplished by
changing, as opposed to establishing, NATv6 at the single-homed PI block's
edge (upstream towards DFZ PA block). And eventually, removing NATv6
and announcing the PI block directly into the DFZ.

So, what kind of PI blocks should be made available?

I'd suggest that anything on a nibble boundary, that suits the applicant's
needs, honestly.

Simple enterprises doing "flat" networking with autoconfiguration, might
be able to make do with a single /80, which can handle 48 bits of MAC
address autoconfiguration (basically anything ever made with a NIC).

Even complex enterprises, with autoconf stuff, are likely able to make do
with a /72 or a /64. And likewise, as appropriate, /56 and /48 all make
sense, based on need.

The corresponding PA block assignments, while sticky, aren't as fixed
as PI assignments. An entity with a sparsely used PI block, could probably
be assigned a much smaller PA block. The NAT itself, arguably, could be done
by either the upstream or downstream participant, or both - the latter,
for instance, where the first bit is zero for client-side mappings,
and one for dynamic use for anything that does not match the fixed mappings,
to prevent leakage by NAT instead of filtering.

For any large and growing organization, if the end-game of IPv6 network
growth, from single-homed to multihomed, is turning off NAT rather than
changing what block is used for NAT, the net win is obvious, I would hope.
And having this carrot to wave, in addition to the stick of "IPv4 space
is all used up", is an important way to avoid too much delay in making
the eventual move. Getting significant buy-in across the board for IPv6
should be, for all of us, a goal we are consciously pursuing.

In summary:

Having an easily available third option (beyond PA and ULA-C), is something
that I think is important to remove the impediment to migration and/or
deployment of IPv6 on a large scale (numbers of entities deploying as well
as size of entities.)

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 Jul 03 00:18: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 1I5Zpw-0005DT-Gx; Tue, 03 Jul 2007 00:18:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5Zpv-0005DL-Ga
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:17:59 -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 1I5Zos-0007Lu-TZ
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:17: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 1I5Zos-0005nv-IH; Tue, 03 Jul 2007 00:16:54 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Tue, 3 Jul 2007 00:16:54 -0400 (EDT)
Message-ID: <63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
In-Reply-To: <43704.1183395211@sa.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>
	<4684DB4A.2060703@gmail.com> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
Date: Tue, 3 Jul 2007 00:16:54 -0400 (EDT)
From: briand@ca.afilias.info
To: "Paul Vixie" <paul@vix.com>
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: 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

Paul Vixie wrote:
> the competing visions as i understand them are "random-prefix ULA-C makes
> it
> impossible to postprocess one's log files on computers outside the
> connectivity realm where they were gathered, makes recourse against
> spammers
> and ddos-for-hire crews even harder, and moves the hijacking problem from
> the
> realm where RPKI can help some day to the realm of ``i got it from
> agnes''(*)"
> and "assigned-prefix ULA-C makes it likely that the PI/PA separation
> regime
> will collapse, and take the internet down in flames."

One comment I neglected to make in my previous response was, that
encouraging the use of PI, even when used on the far side of PA NAT,
means that the identity of (and NOC contact info for) anyone who
accidentally leaks packets with a source for which there is no route,
into the DFZ, is more likely to be discoverable, by mere virtue of the
assignments and registration that go along with PI 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 Jul 03 00:36: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 1I5a7q-0003QH-Ak; Tue, 03 Jul 2007 00:36:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5a7o-0003Dv-BA
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:36:28 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5a6e-0002KW-H0
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:36:28 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85504184; Tue, 03 Jul 2007 00:35:15 -0400
Message-ID: <4689D1F8.3010604@internap.com>
Date: Mon, 02 Jul 2007 21:35:04 -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: <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>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
In-Reply-To: <63246.74.122.168.81.1183436214.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: 0bc60ec82efc80c84b8d02f4b0e4de22
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

briand@ca.afilias.info wrote:
>
> One comment I neglected to make in my previous response was, that
> encouraging the use of PI, even when used on the far side of PA NAT,
> means that the identity of (and NOC contact info for) anyone who
> accidentally leaks packets with a source for which there is no route,
> into the DFZ, is more likely to be discoverable, by mere virtue of the
> assignments and registration that go along with PI space.
>   

Wouldn't that be equally true of ULA-C space?


And in response to your earlier post encouraging the use of 1:1 NATv6, 
wouldn't it be just as easy/beneficial to use ULA-C or ULA-L space for 
the private side of the NAT?  The only difference would be in the 
multihomed case, where allocation of globally-routable PI space could be 
delayed until the recipient applied for their ASN, and the recipient 
network could transition the public side of their NAT to use the new PI 
space, leaving the inside of the network as ULA or ULA-C.

Now all of this ignores the fact that, architecturally, NATs have been 
rejected as bad for end-to-end connectivity.  To minimize problems 
caused by NAT, it would probably be better to use autoconfiguration 
(stateless or DHCP) to assign PA addresses to hosts (in addition to any 
non-globally-routed space used).

-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 Jul 03 00:58: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 1I5aTV-0005I3-Mx; Tue, 03 Jul 2007 00:58:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5aTT-0005EN-4O
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:58:51 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5aPx-0006h3-67
	for ipv6@ietf.org; Tue, 03 Jul 2007 00:55:13 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id A662111426
	for <ipv6@ietf.org>; Tue,  3 Jul 2007 04:55:12 +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, 02 Jul 2007 23:27:10 -0400."
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.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>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 03 Jul 2007 04:55:12 +0000
Message-ID: <44656.1183438512@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
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

> The interesting thing is, one person's PI is another person's PA.
> By that I mean, that the difference between PI and PA, is subjective.

yes.

> The general idea is that the bulk of address assignments used should be,
> one would expect and hope, PA, and aggregated, into large assignments
> of PI blocks (ideally one per ASN) in the DFZ. The scalability of the
> DFZ depends on this, in fact.

no.  while it's true in the current system that identity-follows-routing,
that may not always be true, and away from the DFZ, it's already untrue.
therefore we must reject the aggregation-centric view, or at least, constrain
it to only being valid for globally connected devices, reachable from DFZ.

consider an ipv6-reachable light switch in my house.  does anyone still think
that it can have "end to end" connectivity, so that if i want to monitor it
or control it while on vacation, i'll send IPSEC-signed datagrams from my
hotel room to do so?  that i'll subject it to every DDoS attack, stack
smash attack, IPSEC key guessing attack, plus any other attacks i can't
think of or which havn't been invented yet?  or do we think that it'll sit
in fe80:: and be talked to only by some local (hardened) proxy?  or that at
best it'll have a ULA-G address, reachable by my household security company's
local embedded network but no further?

i'm not saying the DFZ will go out of style.  i'm saying that when we fill
half of the IPv6 address space with light switches and toasters and security
cameras and music players, we'll have 18446744073709551616 endpoints, of which
only a handful are "hardened enough" to be allowed to be globally reachable.
so in contrast to the current IPv6 addressing plan where 0/0 is the DFZ other
than a few cutouts like fe80:: and fc00::, if we were going to be realistic
about how stuff was actually going to be connected in this BCP38-free world,
we'd've allocated beef::/16 to the DFZ and assumed that the rest of IPv6
would be used by non-DFZ devices.

fortunately, the difference between 120 bits and 128 bits is minor compared
to the magnitude of the 120 bit mantissa available in my ULA-G proposal.  so,
the fact that the addressing plan assumes "DFZ uber alles" is no great waste.

on the other hand, i like where you went with this, so i'll quote it all in
hopes that those who didn't read it the first time will read it now:

> On the other hand, PA is a form of "lock-in". Renumbering is painful,
> if the scope of the renumbering is large.
> 
> If a PA assignment is directly to an "end user", e.g. an enterprise,
> this in theory isn't likely to be a large scope, or is at least manageable.
> 
> It is when the PA assignments are further subassigned, that the scope
> becomes a significant issue, and the pain (of renumbering) grows.

yea, verily.  tell it, brother!

> For example, if a large PA block has been given out, and further assigned
> to hundreds of customers (of the PA block recipient), each of which has
> DNS servers "on the block", if the recipient needs to renumber, the pain
> is prohibitive.
> 
> Placing the potential recipient in the position of having to choose between
> PA, and a difficult-and-costly-to-obtain PI block, is by its nature harmful
> to the deployment of IPv6.

as it has been for IPv4, but people coped because there was a legacy swamp.
in the absence of a legacy swamp, the PI/PA split has a chilling effect on
IPv6 deployment, over and above the chilling effect of the technology and
training costs.

> And it is for this reason that I advocate reducing or eliminating costs, and
> relaxing the requirements for receiving PI space.  For instance, deferring
> the costs of PI space until the PI block is added into the DFZ, is one
> option.

i'm not saying whether i agree or disagree with this proposal.  i'll merely
remind you, again, that IETF doesn't set PI policy, that's a regional thing
and you'll need to follow jordi to all the RIR meetings and make your 
proposals to the actual decisionmakers, who are the members of various RIRs.

> And admittedly, it is the interactions of 1:1 NAT and DNS that causes most
> of the problems, under any scheme for handling relocation in connectivity
> to the DFZ.

1:1 NAT is only a predictable problem if you think the DFZ will always be
the dominant form of communication.  when i finally get my Dick Tracy Tv
Wrist Watch and i make a wrist-to-wrist call to someone in my same city,
you can bet that my wireless provider and the other-end wireless provider
are going to have private peering, and that ULA-G would work just fine for
us.  and that in the long distance use case, the LCR algorythm will choose
some city-local proxy who might or might not use DFZ on the backside, but
i most likely won't be using the DFZ on my own behalf.

> In a hierarchy of PI-PA assignments, it fundamentally does not matter
> whether the PA block itself is being sub-assigned, or if a separate PI block
> from which 1:1 NATv6 is instead PA'd and sub-assigned.

agreed.  nor would it matter if the 1:1 NATv6 was to a ULA-G address block.

> The fact that 1:1 NAT isn't strictly a two-tier technology, and that the
> total amount of theoretical address space is so immense, even when used in
> a particularly inefficient manner, means that doubling or tripling the
> effective use (by heavy use of 1:1 NAT), is not a significant cost.
> 
> Use of 1:1 NAT keeps the DFZ to a bare minimum, while still giving all the
> flexibility for back-door networking at arbitrary scale.

yup.

> Still, the question of what to use for the other side of NAT is important,
> at least in terms of what kinds of solutions to promote, to support in
> the IETF protocol and address specifications, and in the RIR policies.
> 
> What I propose is, that PI assignment be very significantly relaxed and
> promoted, for use in this case.

you're making this particular case to the wrong audience.

> Why?
> 
> Because, use of ULA-C for the other side of PA NATing means that should
> an organization at some point need to have multihomed connectivity, the
> site would need to renumber. This is because (stating the obvious) only
> PI blocks can be announced into the DFZ, and ULA-C are specifically not
> allowed into the DFZ.

you're assuming that someone with ULA-G and 1:1 NAT won't find a comfortable
equilibrium with their ISP whereby their use of PA avoids all lock-in issues.

why?  (isn't this the holy grail of eid/loc separation?)

> If, on the other hand, any organization that foresees, at any point in
> time, needing to be multihomed, getting PI space early and using it,
> with NATv6 into PA space (for access to the DFZ), all is good.

i don't think an organization has to be able to foresee this in order for 
all to be good.  in fact, in your 1:1 NAT case and with some simplistic
assumptions about LCR, multihomed ULA-G might be able to perfectly coexist
with a perfectly-aggregated DFZ.  though we're way off topic by this time.

> The fact that this scales recursively is also good. Each link in the
> chain is a PA to PI mapping (NATv6). And every enterprise in the tree under
> a PI in the DFZ, while having its own PI block, while it is single homed,
> is still aggregated into a single PI block in the DFZ.

that would work as well as anything else that's been proposed and better
than most.  (though there's the detail of PI vs. ULA-G and the fact that IETF
is the wrong forum to talk about PI.)

> So, the scalability of the DFZ is still limited by growth of entities
> which require their own PI block, and renumbering is accomplished by
> changing, as opposed to establishing, NATv6 at the single-homed PI block's
> edge (upstream towards DFZ PA block). And eventually, removing NATv6
> and announcing the PI block directly into the DFZ.

i don't get that last part.  you're assuming that a 200-megaroute DFZ is
coming to earth within our lifetimes?  but other than that last part i'm
ready to drink this particular koolaid, as long as "require their own PI
block" is semantically equivilent to "owns global POSIP backbone and does
peering and transit in many major markets", which i think it probably is.

> So, what kind of PI blocks should be made available?

(wrong audience.  visit ppml@arin.net to start, then follow jordi.)

> In summary:
> 
> Having an easily available third option (beyond PA and ULA-C), is something
> that I think is important to remove the impediment to migration and/or
> deployment of IPv6 on a large scale (numbers of entities deploying as well
> as size of entities.)

my summary: ULA-G does everything you want, but can actually be argued here
in ipv6@ rather than having to make new coherent global RIR policy.

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



From ipv6-bounces@ietf.org Tue Jul 03 01:01: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 1I5aWR-0003qB-I8; Tue, 03 Jul 2007 01:01:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5aWQ-0003kE-0z
	for ipv6@ietf.org; Tue, 03 Jul 2007 01:01:54 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5aWP-0000JL-PI
	for ipv6@ietf.org; Tue, 03 Jul 2007 01:01:54 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5A51911426
	for <ipv6@ietf.org>; Tue,  3 Jul 2007 05:01:53 +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, 02 Jul 2007 21:35:04 MST."
	<4689D1F8.3010604@internap.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>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 03 Jul 2007 05:01:53 +0000
Message-ID: <46803.1183438913@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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

> ... all of this ignores the fact that, architecturally, NATs have been
> rejected as bad for end-to-end connectivity.  To minimize problems caused by
> NAT, it would probably be better to use autoconfiguration (stateless or
> DHCP) to assign PA addresses to hosts (in addition to any non- globally-
> routed space used).

where PA is available because connectivity to the global internet is
available, i agree.  but if the connectivity realm of interest doesn't happen
to include a the global internet, NAT may not be nec'y even if ULA-G is used.

i think that "architectural rejection" means "academy vs. field" and the
field always wins.

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



From ipv6-bounces@ietf.org Tue Jul 03 02:08: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 1I5bYd-0006jy-Ru; Tue, 03 Jul 2007 02:08:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5bYb-0006f5-Ln
	for ipv6@ietf.org; Tue, 03 Jul 2007 02:08:13 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5bXn-0004Cn-7s
	for ipv6@ietf.org; Tue, 03 Jul 2007 02:08:13 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85506209; Tue, 03 Jul 2007 02:07:22 -0400
Message-ID: <4689E78F.6000307@internap.com>
Date: Mon, 02 Jul 2007 23:07:11 -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: <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>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com>
	<46803.1183438913@sa.vix.com>
In-Reply-To: <46803.1183438913@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: 0bc60ec82efc80c84b8d02f4b0e4de22
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

Paul Vixie wrote:
>> ... all of this ignores the fact that, architecturally, NATs have been
>> rejected as bad for end-to-end connectivity.  To minimize problems caused by
>> NAT, it would probably be better to use autoconfiguration (stateless or
>> DHCP) to assign PA addresses to hosts (in addition to any non- globally-
>> routed space used).
>>     
>
> where PA is available because connectivity to the global internet is
> available, i agree.  but if the connectivity realm of interest doesn't happen
> to include a the global internet, NAT may not be nec'y even if ULA-G is used.
>   
Of course. 

Perhaps we should call them Unique Global Addresses, (UGAs), if that TLA 
isn't too easily confused with the University of Georgia...  Aren't 
acronyms fun?  :-)

If I have a neighborhood network and want to peer with adjacent 
neighborhoods to make an ad-hoc metro network, I'd be happy to announce 
my ULA-G block  and accept whatever UGA/ULA-G/ULA-C/ULA routes my 
neighboring networks would like to announce (with the exception of those 
covered by my block, of course).  I'll be happy to give my hosts U?A 
addresses so they can communicate with the rest of the city at WLAN/MAN 
speeds, as well as PA addresses to communicate with the rest of the 
world at Internet speed.

-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 Jul 03 04:05: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 1I5dNU-0007Zc-QO; Tue, 03 Jul 2007 04:04:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5dNS-0007GP-3p
	for ipv6@ietf.org; Tue, 03 Jul 2007 04:04:50 -0400
Received: from wx-out-0506.google.com ([66.249.82.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5dMZ-0004FQ-FP
	for ipv6@ietf.org; Tue, 03 Jul 2007 04:04:50 -0400
Received: by wx-out-0506.google.com with SMTP id h27so1564958wxd
	for <ipv6@ietf.org>; Tue, 03 Jul 2007 01:03: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=assobQcZzSIKC1ZRep9v/WVbAjHpoHH2cTA1u6RtCCC+BKmZKKAc3rVizujLmdrILyihlGOo23xDzi4j0AdJxqG8bLq6oc/KFTHWlLrhAFe3dJhPfaEqywW8F93uQL9T/4pHGmyo0Vhuonu1piWvjL0rM6dFJ5DVY3UcqN2BbHQ=
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=L5MS2ySg/20sEDSaU3a5SKlXX3k+mQELyKmnx0Nvu4/PQnyxWuIZ7GUy21roHe9jAr9FUAAzorA0GorMd6EUTH0q4Pbdkf2BZkQm+NX2I2+PeVLSN1MOONvR2oT6Vwgbqj5f8leMPYsA6AeWxFSe8afVhdHVQe3pz69NscgZAPg=
Received: by 10.90.81.14 with SMTP id e14mr5791375agb.1183449835128;
	Tue, 03 Jul 2007 01:03:55 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id q30sm5235593wrq.2007.07.03.01.03.53
	(version=SSLv3 cipher=RC4-MD5); Tue, 03 Jul 2007 01:03:54 -0700 (PDT)
Message-ID: <468A02EC.3080509@gmail.com>
Date: Tue, 03 Jul 2007 10:03:56 +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>	<4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>
In-Reply-To: <43704.1183395211@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
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

Paul,

On 2007-07-02 18:53, Paul Vixie wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com>:
>> OK, I didn't intend to be emotional there. Let me try to explain. Until
>> we get something fundamentally different from the routing researchers,
>> the only model we have is BGP4, ...
> 
> i've heard of alternatives but you're right that nothing else has caught on.
> 
>>                                 ... and the only way we have to control the
>> growth in BGP4 table size and dynamics is aggregation.  That's basic and
>> hasn't changed in 25 years. That's why CIDR saved us. 
> 
> no.  i don't have objective measurements, but i know that a lot of table size
> control is achieved by limiting the horizon of announcements.

Absolutely. And from what I've heard, "a lot" may in fact be as much
as 90% for some ISPs.

> ULA-C with my
> proposed diffs is just a way to take this a lot further, to legitimize it, to
> scale it up to planetary size.

And actually that is where we seem to be at odds. I fear that ULA-G will leak.
That's all.
> 
> there's been a fundamental misunderstanding in the acadamy as to what actually
> happens in the field.  ietf thought that the only connectivity that mattered
> was universal connectivity, and fought firewalls and nat for a long while, but
> ultimately firewalls and nat and RFC 1918 were all great things for the
> internet even though they "violated" the universal connectivity assumptions.
> 
> for the record, table size only matters in the DFZ, and only because there are
> too many third parties for the budget of any one of them to govern the size of
> the table.  away from the DFZ, table size is a self limiting problem, and no
> questions of aggregation are even pertinent.
> 
>> So I really only see two kinds of IP prefix - those that aggregate and those
>> that don't.
> 
> that's an extremely informative statement, thank you for sharing it.
> 
>> We need to encourage the former and discourage the latter (as far as seeing
>> them in BGP is concerned).
> 
> if you mean by "BGP", the DFZ, then i'd agree with this statement in isolation
> from the one that came before it.

Yes, I mean the DFZ - as above, I fully understand that there are already
vast numbers of private routes.

> 
>> In today's jargon, that means encouraging PA, and limiting PI to a few
>> thousand users that really need it. ULA-C with structure as you propose is a
>> form of PI. I believe it will be perceived as an easy way to get PI space,
>> and the pressure to stick ULA-C prefixes of this kind in the DFZ will become
>> very hard to resist.  I don't see that risk being anywhere near as high for
>> current ULAs or for centrally registered random ULAs.
> 
> harken back to the above where i referenced "many third parties".  in the DFZ,
> what matters is what the tier-1 providers do.  they can afford 2-megaroute
> forwarding machinery, they compete aggressively for end-sites against both
> other tier-1's and all of the regional or value-add or low-cost tier-2's, and
> they really like the PA concept because the renumbering penality gives them a
> form of lock-in that even microsoft and apple can only dream about.  

As an aside, that's why the normal model in IPv6 is for a user site to
run several PA prefixes simultaneously, and that's why we designed shim6.

> if the
> tier-1's decide to exchange ULA-C routes with each other, then the rest of the
> internet has to do likewise.  and if some really large cash cow of a customer
> puts out an RFP to tier-1 saying "we'll buy bandwidth from whoever will route
> our ULA-C into the internet core" then it'll be very interesting.  is this
> your proposed "pressure to stick" comes from?  because i can think of a dozen
> reasons why it can't happen, all based on business strategy and self-interests
> of every single party involved in that money chain.

I hope you're right. My argument against structured ULA prefixes is only
to make it less likely to happen.

> 
> the competing visions as i understand them are "random-prefix ULA-C makes it
> impossible to postprocess one's log files on computers outside the
> connectivity realm where they were gathered, makes recourse against spammers
> and ddos-for-hire crews even harder, and moves the hijacking problem from the
> realm where RPKI can help some day to the realm of ``i got it from agnes''(*)"

I'm not sure I understand that, given that random ULA-C assignments would
be escrowed in some way, but it will clearly be *easier* to trace
ownership of structured ULA-Cs.

> and "assigned-prefix ULA-C makes it likely that the PI/PA separation regime
> will collapse, and take the internet down in flames."

I suspect that's an exagerration since this is a statistical game anyway,
but my concern is along that axis.

> 
> (*) http://www.lyricsdir.com/tom-lehrer-i-got-it-from-agnes-lyrics.html
> 
>> I assume we all want the routing system to continue to scale at an
>> economically sustainable rate. Can you show that structured ULA-C will be
>> added to the DFZ at a sufficiently low rate that we won't get into
>> trouble?
> 
> i predict that structured ULA-C will enter the DFZ at the rate of zero, since
> there will be an RFC which excuses anyone who wants to filter it out, and 
> since there will be many more champions whose livelihoods are threatened by
> it than whose livlihoods could be enriched by it.  (it's all about the money.)

This is the key point. If you're right, there is nothing to be concerned
about.

> 
>> What's your estimate of the total number of ULA-C prefixes needed?
> 
> approximately one per family, worldwide, counting only the population who has
> electric power.  much much higher than the 2-megaroute level, or the number
> of domain names registered in .COM and .DE (the two largest TLDs).

I don't get that. Customers need routeable prefixes. Why do you need
a ULA-C prefix for a customer?

     Brian
> 
>> If those numbers fit within reasonable guesses about sustainable
>> DFZ growth, no problem.
> 
> they don't fit, but they don't have to fit, because they're not going in.
> 
> --------------------------------------------------------------------
> 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 Jul 03 04:55: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 1I5e9x-0005CP-UU; Tue, 03 Jul 2007 04:54:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5e9w-00059g-3b
	for ipv6@ietf.org; Tue, 03 Jul 2007 04:54:56 -0400
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5e9s-000829-Jr
	for ipv6@ietf.org; Tue, 03 Jul 2007 04:54:56 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 09:54:51 +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, 3 Jul 2007 09:56:19 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B09F8D2B@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <44656.1183438512@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: Ace9LwMpBFDHlV+mTl6UfG73OUcLjQAH7ibw
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><4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com><3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org><58873.1183400932@sa.vix.com><63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 03 Jul 2007 08:54:51.0591 (UTC)
	FILETIME=[D15C6D70:01C7BD4F]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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

> consider an ipv6-reachable light switch in my house.  does=20
> anyone still think that it can have "end to end"=20
> connectivity, so that if i want to monitor it or control it=20
> while on vacation, i'll send IPSEC-signed datagrams from my=20
> hotel room to do so?  that i'll subject it to every DDoS=20
> attack, stack smash attack, IPSEC key guessing attack, plus=20
> any other attacks i can't think of or which havn't been=20
> invented yet?  or do we think that it'll sit in fe80:: and be=20
> talked to only by some local (hardened) proxy?  or that at=20
> best it'll have a ULA-G address, reachable by my household=20
> security company's local embedded network but no further?

This isn't the use-case that matters because, as you pointed out,
light-switches are likely to be hidden behind a master-controller of
some sort. The important use-case is devices which need to behave like a
telephone set, i.e. raise an alarm when there is an incoming connection
attempt and establish a connection upon request of the local user or
some device that proxies for the local user. Of course this
telephone-set device may be an actual VoIP telephone with attached
answering machine. Or it could be something entirely different such as a
medical monitoring device, a home security device which is polled at
random intervals, or a blackberry-like device, etc. etc.

> on the other hand, i like where you went with this, so i'll=20
> quote it all in hopes that those who didn't read it the first=20
> time will read it now:
>=20
> > On the other hand, PA is a form of "lock-in". Renumbering=20
> is painful,=20
> > if the scope of the renumbering is large.
> >=20
> > If a PA assignment is directly to an "end user", e.g. an=20
> enterprise,=20
> > this in theory isn't likely to be a large scope, or is at=20
> least manageable.
> >=20
> > It is when the PA assignments are further subassigned, that=20
> the scope=20
> > becomes a significant issue, and the pain (of renumbering) grows.
>=20
> yea, verily.  tell it, brother!

Agreed. This is a problem that still needs to be addressed by the IETF.
In IPv4 the excuse was that the number space was limited. But in IPv6 we
no longer need to impose one model on everyone. I'm working on a draft
that presents one possibility.

--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 Jul 03 05:27: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 1I5efS-0002Jh-3T; Tue, 03 Jul 2007 05:27:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5efQ-0002DY-Jm
	for ipv6@ietf.org; Tue, 03 Jul 2007 05:27:28 -0400
Received: from [2002:db58:fb10::1] (helo=carbon.meta.net.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5efL-0004HU-B1
	for ipv6@ietf.org; Tue, 03 Jul 2007 05:27:28 -0400
Received: from [60.234.141.149] (helo=[10.100.4.156] ident=dahoose2)
	by carbon.meta.net.nz with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62)
	(envelope-from <perry@coders.net>)
	id 1I5efE-0005Kw-Dx; Tue, 03 Jul 2007 21:27:16 +1200
Message-ID: <468A1673.9040502@coders.net>
Date: Tue, 03 Jul 2007 21:27:15 +1200
From: Perry Lorier <perry@coders.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@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>	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>	<43704.1183395211@sa.vix.com>
	<468A02EC.3080509@gmail.com>
In-Reply-To: <468A02EC.3080509@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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


> And actually that is where we seem to be at odds. I fear that ULA-G 
> will leak.
> That's all. 
So I might be a bit naive here, but why is this a problem?  ISP's that 
are worried that they're routers can't deal with ULA addresses in their 
DFZ will filter all ULA addresses.  ISP's that want ULA's in their DFZ 
will make sure they dimension their routers such that they can deal  
with it.  Other ISP's will find some kind of middle ground where they 
have some ULA prefixes,The DFZ is certainly not the same everywhere on 
the Internet, by making ULA's easily filterable it gives operators a 
place to start if they want to filter.

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



From ipv6-bounces@ietf.org Tue Jul 03 09:29: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 1I5iR9-0002lz-I7; Tue, 03 Jul 2007 09:28:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5iR8-0002lu-2W
	for ipv6@ietf.org; Tue, 03 Jul 2007 09:28:58 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5iQq-0001Ns-SU
	for ipv6@ietf.org; Tue, 03 Jul 2007 09:28:58 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 03 Jul 2007 09:28:40 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAL7riUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="64254957:sNHT40203874"
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 l63DSeJG017801; 
	Tue, 3 Jul 2007 09:28:40 -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 l63DSes0001061; 
	Tue, 3 Jul 2007 13:28:40 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, 3 Jul 2007 09:28:40 -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, 3 Jul 2007 09:28:39 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468678D1.40000@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace7LNjvVObknuuLTUO17BAbvJZocwCSFCzA
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>,
	"Wes Beebee (wbeebee)" <wbeebee@cisco.com>
X-OriginalArrivalTime: 03 Jul 2007 13:28:40.0601 (UTC)
	FILETIME=[11D06890:01C7BD76]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1882; t=1183469320;
	x=1184333320; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>,
	=0A=20=20=20=2
	0=20=20=20=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.com>;
	bh=ubu1/ZDAFi/xICmZBUdylYAVcp9pAyj+KbWHmmPrNRc=;
	b=gB2y/kzdWywKsc4CfdXCz3ywMpUFsRr3rhyZdAEEuWenpkgP9F4HXm1hBsKCxOKP/MC8nAfz
	eBQJd2tgy7gjF0qx0p/5XBITxpkJkoy3xc5Dt6fBh7Iq2ORzyHUEWlhs;
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: 0ddefe323dd869ab027dbfff7eff0465
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

Vlad,

If you say "this language should already be in the 2461bis" where is it
? Show us the exact paragraph and section.
Please note that both an implementer of a popular IPv6 host and an IPv6
certification agency missed this behavior.

Hemant & Wes=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Saturday, June 30, 2007 11:38 AM
To: Wes Beebee (wbeebee)
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Wes Beebee (wbeebee) wrote:
> Section 3.1 of RFC 2461 describes intended behavior when a host=20
> receives an RA without an advertised prefix:
>=20
>       "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."
>=20
> As described in our draft, this language should be strengthened to=20
> state
>=20
> 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.
>=20

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

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



From ipv6-bounces@ietf.org Tue Jul 03 09:49: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 1I5ikl-00012F-3U; Tue, 03 Jul 2007 09:49:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ikj-00011t-Cc
	for ipv6@ietf.org; Tue, 03 Jul 2007 09:49:13 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5ikj-0003O9-1Z
	for ipv6@ietf.org; Tue, 03 Jul 2007 09:49:13 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 15:49:01 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAG7wiUaQ/uCKh2dsb2JhbACPJAIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147122535:sNHT7212864586"
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 l63Dn1hp013105; 
	Tue, 3 Jul 2007 15:49:01 +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 l63Dn0TC025377; 
	Tue, 3 Jul 2007 13:49:00 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 l63Dn07U006912; 
	Tue, 3 Jul 2007 14:49:00 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l63Dn0tn006911;
	Tue, 3 Jul 2007 14:49:00 +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: "Hemant Singh \(shemant\)" <shemant@cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
Date: Tue, 03 Jul 2007 14:48:59 +0100
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	(Hemant Singh's message of "Tue\, 3 Jul 2007 09\:28\:39 -0400")
Message-ID: <7t5bqet8uno.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=2271; t=1183470541;
	x=1184334541; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20;
	bh=IflRK6fwEemtnmyxtIfmZ67AVt/AefxPPxD251fN/EY=;
	b=j26C6NDqdYzpZdBaO/mRyn0Ynko4olYujulH3a1vHuANjSUwP4HU1LWH+9Y0hJJtEXDXrmID
	5uIGOy4oEnIQMoLI7Bxu6uLdaIeaTOn1vIy88Vf06o6XP38sx6zH/2KR;
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

> If you say "this language should already be in the 2461bis" where is it
> ? Show us the exact paragraph and section.
> Please note that both an implementer of a popular IPv6 host and an IPv6
> certification agency missed this behavior.

"5.2.  Conceptual Sending Algorithm" explains how a host should behave
in this case.

/ot

> -----Original Message-----
> From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com] 
> Sent: Saturday, June 30, 2007 11:38 AM
> To: Wes Beebee (wbeebee)
> Cc: ipv6@ietf.org
> Subject: Re: Sending traffic to default router when RA has no PIO
>
> 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
> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> 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 Jul 03 10:02: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 1I5ixM-0007IH-Vn; Tue, 03 Jul 2007 10:02:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ixL-0007IB-1X
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:02:15 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5ixK-0006bK-MS
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:02:14 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 03 Jul 2007 10:01:50 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAHrziUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="125135428:sNHT197001528"
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 l63E1n2o002620; 
	Tue, 3 Jul 2007 10:01:49 -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 l63E1ns0011703; 
	Tue, 3 Jul 2007 14:01:49 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, 3 Jul 2007 10:01:45 -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, 3 Jul 2007 10:01:44 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace9ePEIkXM8I4/3TUivkSFNAg643AAAJ44Q
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ole Troan (otroan)" <otroan@cisco.com>
X-OriginalArrivalTime: 03 Jul 2007 14:01:45.0539 (UTC)
	FILETIME=[B0EDE930:01C7BD7A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4158; t=1183471309;
	x=1184335309; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Ole=20Troan=20(otroan)=22=20<otroan@cisco.com>;
	bh=UwIDXFp85ZvFjaYEGdSm2YXwSVvzlT/JEQl9/dlKXm8=;
	b=CxsBd5yRJzy7rALVaKYBVz9IYufWGWA3Pa9ohP4mrhZWGRCfdSzAF1AQTPdiK6qSgW4xYtek
	9DpCrn+AeE00xJ1yBKbhdrP0yyEqm5CGvSWuxdBsgTHYmxl1bduhje4A;
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: e1b0e72ff1bbd457ceef31828f216a86
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

Ole,

Let's talk specifics, not generics. Of course, we know about section 5.2
of 2461bis.

Snipped is following text from Introduction section of our I-D as to
what we think about section 5.2 of 2461bis:

   Sections 5.2 and 7.2.2 imply that the host performs
   address resolution before transmitting a packet if the destination of
   the packet is on the same link as the host.  Some current host
   implementations perform address resolution in all cases even when the
   destination is not clearly on-link.  However, RFC 2461 [ND] section
   6.3.4 implies that hosts must clearly determine that a destination is
   on-link before performing address resolution.=20

Section 5.2 says "if the destination is on-link, then next-hop address
is the same as the packet's destination address. Otherwise, the sender
selects a router from the default router list." Implementers are not
putting two-and-two together. As described in section 2.1 of our I-D, if
a host has not been sent any PIO in RA, and the host performed DHCPv6,
the host has no way to determine what's on-link for the host. Section
5.2 just says "if the destination in on-link...". Well, discussion first
has to be made as to how can a host determine what's on-link for it.
These are the clarifications we have made in our I-D.

Proof is also in the pudding. We also say in Abstract of our I-D, if ND
RFC's are almost 10 years old, why are popular hosts still making
mistakes with on-link determination or totally not heeding L bits of RA
? ND has to be clarified as we have done so in our I-D.

Hemant & Wes

-----Original Message-----
From: Ole Troan (otroan)=20
Sent: Tuesday, July 03, 2007 9:49 AM
To: Hemant Singh (shemant)
Cc: Vlad Yasevich; Wes Beebee (wbeebee); ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

> If you say "this language should already be in the 2461bis" where is=20
> it ? Show us the exact paragraph and section.
> Please note that both an implementer of a popular IPv6 host and an=20
> IPv6 certification agency missed this behavior.

"5.2.  Conceptual Sending Algorithm" explains how a host should behave
in this case.

/ot

> -----Original Message-----
> From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]
> Sent: Saturday, June 30, 2007 11:38 AM
> To: Wes Beebee (wbeebee)
> Cc: ipv6@ietf.org
> Subject: Re: Sending traffic to default router when RA has no PIO
>
> Wes Beebee (wbeebee) wrote:
>> Section 3.1 of RFC 2461 describes intended behavior when a host=20
>> receives an RA without an advertised prefix:
>>=20
>>       "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."
>>=20
>> As described in our draft, this language should be strengthened to=20
>> state
>>=20
>> 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.
>>=20
>
> This language should already be in the 2461bis, just not in the=20
> section you want it in.  May be this paragraph can instead be made=20
> 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
> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> 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 Jul 03 10:07: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 1I5j2S-0003Fb-8b; Tue, 03 Jul 2007 10:07:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5j2R-0003BH-4T
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:07:31 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5j1c-0004A4-Fp
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:07:31 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id EED921142E
	for <ipv6@ietf.org>; Tue,  3 Jul 2007 14:06:39 +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, 02 Jul 2007 23:07:11 MST."
	<4689E78F.6000307@internap.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>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com> <46803.1183438913@sa.vix.com>
	<4689E78F.6000307@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 03 Jul 2007 14:06:39 +0000
Message-ID: <13412.1183471599@sa.vix.com>
X-Spam-Score: -2.8 (--)
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

> Of course. Perhaps we should call them Unique Global Addresses, (UGAs), ...

all PI and PA would be "UGA" though.  ULA-C and ULA-G are more specific.

> If I have a neighborhood network and want to peer with adjacent
> neighborhoods to make an ad-hoc metro network, I'd be happy to announce my
> ULA-G block and accept whatever UGA/ULA-G/ULA-C/ULA routes my neighboring
> networks would like to announce (with the exception of those covered by my
> block, of course).

importantly, you would not accept driveby ad-hoc.  i think that if a malware
injection van hits your neighborhood with a pringles-can antenna from a nearby
hillock, that you should be able to decide based on their RIPE-181
registration data and/or their SBGP or RPKI registration data that you don't
know them well enough to admit them into your wireless mesh network.  that's
not going to happen with straight ULA, which is why ULA-C or ULA-G are
necessary for this use case.

> I'll be happy to give my hosts U?A addresses so they can communicate with
> the rest of the city at WLAN/MAN speeds, as well as PA addresses to
> communicate with the rest of the world at Internet speed.

note that in brian's best-possible-world scenario, you'd be able to do what
you want with PI.  however, we're not in that world, and we need the crutch
of leading high-end address bits to tell our NATv6 boxes when to act, and to
tell our DFZ-path routers when not to act.  thus, ULA-G or ULA-C.

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



From ipv6-bounces@ietf.org Tue Jul 03 10: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 1I5jLW-00044k-IZ; Tue, 03 Jul 2007 10:27:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jLV-00040a-1p
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:27:13 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5jLU-00042e-NL
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:27:12 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 03 Jul 2007 16:27:12 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAM75iUaQ/uCLh2dsb2JhbACPJAIJDiw
X-IronPort-AV: i="4.16,492,1175464800"; 
	d="scan'208"; a="147127750:sNHT32149264"
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 l63ERBPW013397; 
	Tue, 3 Jul 2007 16:27:11 +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 l63ERBTC009202; 
	Tue, 3 Jul 2007 14:27:11 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 l63ERB6Z007815; 
	Tue, 3 Jul 2007 15:27:11 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l63ERAn9007813;
	Tue, 3 Jul 2007 15:27:10 +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: "Hemant Singh \(shemant\)" <shemant@cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
Date: Tue, 03 Jul 2007 15:27:10 +0100
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	(Hemant Singh's message of "Tue\, 3 Jul 2007 16\:01\:44 +0200")
Message-ID: <7t57iph8sw1.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=2813; t=1183472831;
	x=1184336831; c=relaxed/simple; s=amsdkim2001;
	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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20;
	bh=O3EPOZ9DIKp0RCmG9ZuE3XdLPCoJ49R+AFZly8meQAw=;
	b=gEb/7JPEImsyY98d6VD+peR/iMJLUPnHON/5wi87/XWShROSvAuRA1IRv1qoyjuU43U49xbM
	9m/VMTNmfEmsdMS1nsbUckK1xmb8jNwp4iaLdk14tOPfh1iUVQZtgVL7;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

> Let's talk specifics, not generics. Of course, we know about section 5.2
> of 2461bis.
>
> Snipped is following text from Introduction section of our I-D as to
> what we think about section 5.2 of 2461bis:
>
>    Sections 5.2 and 7.2.2 imply that the host performs
>    address resolution before transmitting a packet if the destination of
>    the packet is on the same link as the host.  Some current host
>    implementations perform address resolution in all cases even when the
>    destination is not clearly on-link.  However, RFC 2461 [ND] section
>    6.3.4 implies that hosts must clearly determine that a destination is
>    on-link before performing address resolution. 
>
> Section 5.2 says "if the destination is on-link, then next-hop address
> is the same as the packet's destination address. Otherwise, the sender
> selects a router from the default router list." Implementers are not
> putting two-and-two together. As described in section 2.1 of our I-D, if
> a host has not been sent any PIO in RA, and the host performed DHCPv6,
> the host has no way to determine what's on-link for the host. Section
> 5.2 just says "if the destination in on-link...". Well, discussion first
> has to be made as to how can a host determine what's on-link for it.
> These are the clarifications we have made in our I-D.

isn't that clear from section 6.3.4 on prefix discovery?

   For each Prefix Information option with the on-link flag set, a host
   does the following:

      - If the prefix is the link-local prefix, silently ignore the
        Prefix Information option.

      - If the prefix is not already present in the Prefix List, and the
        Prefix Information option's Valid Lifetime field is non-zero,
        create a new entry for the prefix and initialize its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.

      - If the prefix is already present in the host's Prefix List as
        the result of a previously-received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

      - If the Prefix Information option's Valid Lifetime field is zero,
        and the prefix is not present in the host's Prefix List,
        silently ignore the option.


next-hop determination does not use any prefix not in the prefix
list. if you have an RA without PIOs or without the on-link flag set you
don't add anything to the prefix list. therefore you'll pick one of the
routers from the default router list.

perhaps if any of the implementors getting this wrong could speak up. as
to me this seems pretty clear.

/ot

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



From ipv6-bounces@ietf.org Tue Jul 03 10:33: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 1I5jRT-0004Yi-BB; Tue, 03 Jul 2007 10:33:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jRR-0004Wr-WE
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:33:22 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5jOr-0005SR-Qz
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:30:42 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 03 Jul 2007 10:30:33 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAL76iUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="125138957:sNHT46120408"
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 l63EUXM1018250; 
	Tue, 3 Jul 2007 10:30: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 l63EUW6a017343; 
	Tue, 3 Jul 2007 14:30:32 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, 3 Jul 2007 10:30:32 -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, 3 Jul 2007 10:30:32 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C58@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <200706261439.l5QEdMqS026377@burp.tkv.asdf.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: Ace4AAV/BhLQYKCoTK+uFOCmoN1t0QFetvEA
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>
	<200706261439.l5QEdMqS026377@burp.tkv.asdf.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Markku Savela" <msa@moth.iki.fi>, <ipv6@ietf.org>,
	<brian.e.carpenter@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>
X-OriginalArrivalTime: 03 Jul 2007 14:30:32.0744 (UTC)
	FILETIME=[B66C7A80:01C7BD7E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2711; t=1183473033;
	x=1184337033; 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=22Markku=20Savela=22=20<msa@moth.iki.fi>, =20<ipv6@ietf.org>,
	=0A=2 0=20=20=20=20=20=20=20<brian.e.carpenter@gmail.com>,
	=20=22Fred=20Baker=20( fred)=22=20<fred@cisco.com>;
	bh=RSVohCC/3ky9Vy6tBeYS7aromrrhanFxZEcTmDEXZe4=;
	b=u+S4bEeZBqZMTDSA7VEFEQK/gWluzwnWIsSJVxTjtm2NnDdxPZ9Na8dnSSg+KokGn/ehwv8B
	a4OFRFsqQ5lsCSna+m3CARqopv1g0YfFAflgB3B5GrhkcgZjRkBzLQnQ;
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: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
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

=20
Hi Markku,

Sorry for the delay. Please see in line below against "<hs>".


-----Original Message-----
From: Markku Savela [mailto:msa@moth.iki.fi]=20
Sent: Tuesday, June 26, 2007 10:39 AM
To: 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


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.


<hs> Please see Host1 and Host2 in the scenario we described in Section
2, bullet 4 of our I-D. Since this email, we also have a newer -01
version. Please grab that copy.  In our scenario, Host1 comes online
first while Host2 is powered down.  Then, Host2 comes online.  In this
case, your "defend ID patch" doesn't work (since Host2 doesn't see
Host1's DAD using MAC2).  However, our solution of "not skipping DAD for
any acquired unicast address" will work because if Host2 performs DAD
for GUA with MAC2, then Host1 will catch this NS(DAD) and respond with
an NA.

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 =3D> 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...

<hs> Let's appreciate the fact that 2462bis has already changed to say
"newer implementations MUST perform DAD for every acquired unicast
address". We don't have a DAD storm problem (as described above) because
DAD's are initiated with a randomized delay. See section 5.4.2 of
2462bis -08 I-D, third and fourth paragraph.

- Hemant and Wes

--------------------------------------------------------------------
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 Jul 03 10:54: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 1I5jlg-0005vv-1u; Tue, 03 Jul 2007 10:54:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jle-0005hp-0n
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:54:14 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5jkt-00023S-UV
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:54:14 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 887C911426
	for <ipv6@ietf.org>; Tue,  3 Jul 2007 14:53: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, 03 Jul 2007 10:03:56 +0200."
	<468A02EC.3080509@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> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<468A02EC.3080509@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 03 Jul 2007 14:53:27 +0000
Message-ID: <20140.1183474407@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
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]
> > ...  i don't have objective measurements, but i know that a lot of table
> > size control is achieved by limiting the horizon of announcements.

[brian carpenter]
> Absolutely. And from what I've heard, "a lot" may in fact be as much
> as 90% for some ISPs.

so, we share a supposition that the DFZ is now a minority of "the Internet".

> > ULA-C with my proposed diffs is just a way to take this a lot further, to
> > legitimize it, to scale it up to planetary size.
> 
> And actually that is where we seem to be at odds. I fear that ULA-G will
> leak.  That's all.

consider a spectrum of possibilities:

    --------------------------------------------------------
     O(10^4)                 O(10^6)                O(10^8)

in the leftmost cast, the number of ULA-G prefixes is so small that we could
accomodate them in the DFZ, and the only "problem" would be that it was an end
run around regional (RIR) policymaking.

in the rightmost case, the number of ULA-G prefixes is so large that no single
routing table can hold them, not even the much vaunted 2-megaroute machinery
that's now on various drawing boards.

in the middle, there's a range of size that's large enough to hurt a lot but
small enough to be practical if everybody sends cisco and juniper a great deal
of money.

what is the size of your fear?  i ask because my supposition is that the DFZ
is already a minority and that something like ULA-G (or even ULA-C) would make
it an even smaller minority.  and i consider the rightmost case the likeliest
number of ULA-G routes, and that the number of likely DFZ leaks to be zero.

in the DFZ today are many competitors and thin margins.  for a "leak" to be
successful, one provider has to want to emit a ULA-G route, and virtually all
other providers have to be willing to accept it.  this is so unlikely that i
can't imagine it.  it's not equivilent to the RFC1918 or non-BGP38 emissions
problems, since every "leak" in this case means a competitor signs recurring
revenue for a customer who was in play.  "that is sooooo not going to happen."

> >> We need to encourage the former and discourage the latter (as far as
> >> seeing them in BGP is concerned).

> > if you mean by "BGP", the DFZ, then i'd agree with this statement in
> > isolation from the one that came before it.

> Yes, I mean the DFZ - as above, I fully understand that there are already
> vast numbers of private routes.

then we really do agree that when it comes to the DFZ, aggregation is a MUST.
and our area of disagreement is simply whether deaggregated ULA-G will enter
the DFZ.  i have several times shown why i think that can't happen.  most BGP
operators are looking for any excuse to filter inbound routes, especially TE
routes whose only purpose is to improve the efficiency and service quality of
competitors.  an RFC that strongly recommends that FC00::/7 be filtered will
be an excuse that most of these operators will be thankful for (hopefully
that could mean "beer as in free").

> > ... the tier-1 providers ... can afford 2-megaroute forwarding machinery,
> > they compete aggressively for end-sites against both other tier-1's and
> > all of the regional or value-add or low-cost tier-2's, and they really
> > like the PA concept because the renumbering penality gives them a form of
> > lock-in that even microsoft and apple can only dream about.
> 
> As an aside, that's why the normal model in IPv6 is for a user site to
> run several PA prefixes simultaneously, and that's why we designed shim6.

on that aside, when i connect up my end host to a LAN that has multiple router
advertisements, it selects exactly one as my default route.  there's no LCR as
in the telephony world.  there's no intent to import the entire routing table
into every host -- the router advertisements i don't select are backups not
competitors.  the shim6 idea makes it more interesting -- how's that working
out in the field?  any significant deployment experiences to report?  (i'm
not just still bitter about the A6/DNAME debacle -- i really want to know.)

> > if the tier-1's decide to exchange ULA-C routes with each other, then the
> > rest of the internet has to do likewise.  and if some really large cash
> > cow of a customer puts out an RFP to tier-1 saying "we'll buy bandwidth
> > from whoever will route our ULA-C into the internet core" then it'll be
> > very interesting.  is this your proposed "pressure to stick" comes from?
> > because i can think of a dozen reasons why it can't happen, all based on
> > business strategy and self-interests of every single party involved in
> > that money chain.
> 
> I hope you're right. My argument against structured ULA prefixes is only to
> make it less likely to happen.

the benefit of ULA-G away from the DFZ is so much greater than the risk of
ULA-G to the DFZ that i can't even consider them simultaneously long enough
to let them compete.  from what you're saying, i don't know if you can either.

> >> What's your estimate of the total number of ULA-C prefixes needed?
> 
> > approximately one per family, worldwide, counting only the population who
> > has electric power.  much much higher than the 2-megaroute level, or the
> > number of domain names registered in .COM and .DE (the two largest TLDs).
> 
> I don't get that.  Customers need routeable prefixes.  Why do you need a
> ULA-C prefix for a customer?

the idea of an internet made up only of customers was never part of the early
vision as it's been told to me.  every device needs a unique identifier for
any number of reasons.  if the DFZ is intolerant of these identifiers, then
they'll show up in other ways, like non-DFZ routing, 1:1 NATv6, ad-hoc IPSEC
tunnel innards, software key/serial numbers, and things we've not imagined.

the DFZ is one way to internet.  only one way.  and it's not the only reason
one might need a registered unique addresses.

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



From ipv6-bounces@ietf.org Tue Jul 03 10:55: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 1I5jnH-0001Nw-PO; Tue, 03 Jul 2007 10:55:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jnF-0001FM-Nj
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:55:53 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5jnF-0003sy-E1
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:55:53 -0400
Received: by ug-out-1314.google.com with SMTP id u2so258679uge
	for <ipv6@ietf.org>; Tue, 03 Jul 2007 07:54:48 -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=iEi5rTgG1aKpfpYOpxTYgoiuT+5Ap0T5kYU/+qljCW+5w8h4NxvVEZsLwmPr1WdpYyH6A43VxjR3k0VLs532AbZGCpfegPN1FSVWfSgJ0/IHW+LDUM0U91BHGjdP37jbIKMNEAf4jG57GRfkJZ6+VS6Ejmb8HWWmXT2ebu9kct0=
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=h8TJ02gSO7cP6vi0SzgCu8QZT/2DdaI0IFsc/25AnUiHCemBwl+VjPArjiHj+WgWb5HfJAmxiE6B/J+p9r9vS6DJ1ohmJTpxvPCA6X49DAb06DfqcImCF8aSSCQjyl2T+WdNe5ZLwYSy3PSrDEu1TYmMyz6/MUXcALs5julZWWs=
Received: by 10.66.237.14 with SMTP id k14mr426661ugh.1183474488343;
	Tue, 03 Jul 2007 07:54:48 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id e34sm9453039ugd.2007.07.03.07.54.46
	(version=SSLv3 cipher=RC4-MD5); Tue, 03 Jul 2007 07:54:47 -0700 (PDT)
Message-ID: <468A6338.1040108@gmail.com>
Date: Tue, 03 Jul 2007 16:54:48 +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: <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>	<4688C2CA.5050302@gmail.com>	<43704.1183395211@sa.vix.com>
	<468A02EC.3080509@gmail.com> <468A1673.9040502@coders.net>
In-Reply-To: <468A1673.9040502@coders.net>
Content-Type: text/plain; charset=UTF-8; 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 2007-07-03 11:27, Perry Lorier wrote:
> 
>> And actually that is where we seem to be at odds. I fear that ULA-G 
>> will leak.
>> That's all. 
> So I might be a bit naive here, but why is this a problem?  ISP's that 
> are worried that they're routers can't deal with ULA addresses in their 
> DFZ will filter all ULA addresses.  ISP's that want ULA's in their DFZ 
> will make sure they dimension their routers such that they can deal  
> with it.  Other ISP's will find some kind of middle ground where they 
> have some ULA prefixes,The DFZ is certainly not the same everywhere on 
> the Internet, by making ULA's easily filterable it gives operators a 
> place to start if they want to filter.

Of course. But by leak, as I think was clear in later mail, I meant leak
deliberately under economic pressure. Accidental leakage would be
statistically insignificant, I assume, and easily filtered out as you
say.

    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 Jul 03 10:57: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 1I5jp1-0004qe-Gx; Tue, 03 Jul 2007 10:57:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5jp0-0004qZ-9p
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:57:42 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5jny-0002se-K4
	for ipv6@ietf.org; Tue, 03 Jul 2007 10:57:42 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 03 Jul 2007 10:56:38 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAJsAikZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="125142099:sNHT56690680"
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 l63EucOY015766; 
	Tue, 3 Jul 2007 10:56:38 -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 l63EubsA028636; 
	Tue, 3 Jul 2007 14:56:38 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, 3 Jul 2007 10:56:33 -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, 3 Jul 2007 10:56:32 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace9fj+4rmnPd3pTRTCqQancQwDExgAAUIog
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com><7t5bqet8uno.fsf@gpk-xdm-001.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ole Troan (otroan)" <otroan@cisco.com>
X-OriginalArrivalTime: 03 Jul 2007 14:56:33.0311 (UTC)
	FILETIME=[58981AF0:01C7BD82]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4650; t=1183474598;
	x=1184338598; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Ole=20Troan=20(otroan)=22=20<otroan@cisco.com>;
	bh=8IJ5aqEJ8TPaEbDqurVAQtzEiHKXsssI6s1OH7yNHok=;
	b=WjWFaJYjkLhLiNxObj9iN3IZv1ahJozjyiOljp2jaxU+/cehLm0odknpiUKffvSBTCcDowVP
	OU+xlvAZzlE67y13WSEZOCQUSdhjDrbYmTHD0xVALNi/omF02n+ZoY4G;
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: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

Ole,

You said:

"next-hop determination does not use any prefix not in the prefix list."

Well, this is exactly the problem with host implementations we are
concerned with. The prefix list is being populated with a prefix when
the list should not be populated.

In this regard, bullets 2 and 3 in Section 2 of our I-D show the issue
hosts have when hosts incorrectly always add a directly connected route
to the /64 prefix from an address assigned to an interface, even if the
prefix is advertised as "not on link" or is not advertised at all. That
incorrectly added route causes the host to try to use direct delivery
(without sending traffic to the default router) and, therefore, use
NS/NA to resolve addresses from the same prefix.=20

We are prepared in this discussion that no host implementers will reply
to our thread. We judge host implementations by lack of
interoperability.  Remember we said even an IPv6 certification agency
missed this behavior. We have also said in the past that our I-D
contains a clear, concise set of rules for common host pitfalls and the
I-D also clarifies text in 2461bis and 2462bis.  If one very carefully
reads between the lines of 2461bis and 2462bis, and reads every part of
the specification and thinks about it very carefully, it is conceivable
that one might be able to implement a completely compliant host.
Unfortunately, even after a decade, we have non-compliant hosts
behavior, which indicates that specifications could have been written
more clearly.

- Hemant & Wes

-----Original Message-----
From: Ole Troan (otroan)=20
Sent: Tuesday, July 03, 2007 10:27 AM
To: Hemant Singh (shemant)
Cc: Vlad Yasevich; Wes Beebee (wbeebee); ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

> Let's talk specifics, not generics. Of course, we know about section=20
> 5.2 of 2461bis.
>
> Snipped is following text from Introduction section of our I-D as to=20
> what we think about section 5.2 of 2461bis:
>
>    Sections 5.2 and 7.2.2 imply that the host performs
>    address resolution before transmitting a packet if the destination
of
>    the packet is on the same link as the host.  Some current host
>    implementations perform address resolution in all cases even when
the
>    destination is not clearly on-link.  However, RFC 2461 [ND] section
>    6.3.4 implies that hosts must clearly determine that a destination
is
>    on-link before performing address resolution.=20
>
> Section 5.2 says "if the destination is on-link, then next-hop address

> is the same as the packet's destination address. Otherwise, the sender

> selects a router from the default router list." Implementers are not=20
> putting two-and-two together. As described in section 2.1 of our I-D,=20
> if a host has not been sent any PIO in RA, and the host performed=20
> DHCPv6, the host has no way to determine what's on-link for the host.=20
> Section
> 5.2 just says "if the destination in on-link...". Well, discussion=20
> first has to be made as to how can a host determine what's on-link for
it.
> These are the clarifications we have made in our I-D.

isn't that clear from section 6.3.4 on prefix discovery?

   For each Prefix Information option with the on-link flag set, a host
   does the following:

      - If the prefix is the link-local prefix, silently ignore the
        Prefix Information option.

      - If the prefix is not already present in the Prefix List, and the
        Prefix Information option's Valid Lifetime field is non-zero,
        create a new entry for the prefix and initialize its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.

      - If the prefix is already present in the host's Prefix List as
        the result of a previously-received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

      - If the Prefix Information option's Valid Lifetime field is zero,
        and the prefix is not present in the host's Prefix List,
        silently ignore the option.


next-hop determination does not use any prefix not in the prefix list.
if you have an RA without PIOs or without the on-link flag set you don't
add anything to the prefix list. therefore you'll pick one of the
routers from the default router list.

perhaps if any of the implementors getting this wrong could speak up. as
to me this seems pretty clear.

/ot

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



From ipv6-bounces@ietf.org Tue Jul 03 11:18: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 1I5k91-0003hS-Rh; Tue, 03 Jul 2007 11:18:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5k90-0003cl-OL
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:18:22 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5k90-0006U2-Hu
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:18:22 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85538709; Tue, 03 Jul 2007 11:17:49 -0400
Message-ID: <468A6891.8040300@internap.com>
Date: Tue, 03 Jul 2007 08:17:37 -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: <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>	<4688C2CA.5050302@gmail.com>	<43704.1183395211@sa.vix.com>	<468A02EC.3080509@gmail.com>
	<468A1673.9040502@coders.net> <468A6338.1040108@gmail.com>
In-Reply-To: <468A6338.1040108@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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 E Carpenter wrote:
> On 2007-07-03 11:27, Perry Lorier wrote:
>>
>>> And actually that is where we seem to be at odds. I fear that ULA-G 
>>> will leak.
>>> That's all. 
>> So I might be a bit naive here, but why is this a problem?  ISP's 
>> that are worried that they're routers can't deal with ULA addresses 
>> in their DFZ will filter all ULA addresses.  ISP's that want ULA's in 
>> their DFZ will make sure they dimension their routers such that they 
>> can deal  with it.  Other ISP's will find some kind of middle ground 
>> where they have some ULA prefixes,The DFZ is certainly not the same 
>> everywhere on the Internet, by making ULA's easily filterable it 
>> gives operators a place to start if they want to filter.
>
> Of course. But by leak, as I think was clear in later mail, I meant leak
> deliberately under economic pressure. Accidental leakage would be
> statistically insignificant, I assume, and easily filtered out as you
> say.

Brian,

Can you outline the economic pressures that you believe would lead to a 
ULA-C/ULA-G being accepted by more the majority of tier1ish transit 
providers in the DFZ?  Like Paul, I'm inclined to believe the 
countervailing economic pressures would be much stronger, and that we 
will see very few, if any, ULA routes crossing the magic threshold of 
global routability.  I would love to hear and possibly debate the 
counterarguments.

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 Tue Jul 03 11:43: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 1I5kWw-0008Vy-6j; Tue, 03 Jul 2007 11:43:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kWu-0008Th-R7
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:43:04 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5kW4-0007jv-Jf
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:43:04 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id E4303377B0;
	Tue,  3 Jul 2007 11:41:51 -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 323D918C47B;
	Tue,  3 Jul 2007 15:41:51 +0000 (UTC)
Message-ID: <468A6E3E.5000001@hp.com>
Date: Tue, 03 Jul 2007 11:41:50 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.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: 538aad3a3c4f01d8b6a6477ca4248793
Cc: ipv6@ietf.org, "Ole Troan \(otroan\)" <otroan@cisco.com>
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

Hemant Singh (shemant) wrote:
> Ole,
> 
> Let's talk specifics, not generics. Of course, we know about section 5.2
> of 2461bis.
> 
> Snipped is following text from Introduction section of our I-D as to
> what we think about section 5.2 of 2461bis:
> 
>    Sections 5.2 and 7.2.2 imply that the host performs
>    address resolution before transmitting a packet if the destination of
>    the packet is on the same link as the host.  Some current host
>    implementations perform address resolution in all cases even when the
>    destination is not clearly on-link.  However, RFC 2461 [ND] section
>    6.3.4 implies that hosts must clearly determine that a destination is
>    on-link before performing address resolution. 

Yes.  RFC 2461 allowed you to do that with it's "default on-link" assumption.
The assumption was that if you did not have an on-link and default routes,
they you assumed that the destination was on-link.

This assumption has been removed from 2461bis.  However, we can't force
all existing implementations to change.  All we can do is update the spec.
Existing implementations can still claim conformance to 2461, but not 2461bis.

> 
> Section 5.2 says "if the destination is on-link, then next-hop address
> is the same as the packet's destination address. Otherwise, the sender
> selects a router from the default router list." Implementers are not
> putting two-and-two together. As described in section 2.1 of our I-D, if
> a host has not been sent any PIO in RA, and the host performed DHCPv6,
> the host has no way to determine what's on-link for the host. Section
> 5.2 just says "if the destination in on-link...". Well, discussion first
> has to be made as to how can a host determine what's on-link for it.
> These are the clarifications we have made in our I-D.

Hm...  Searching for "on-link determination" in the text for 2461bis yields
7 instances that describe how it's done and what information is used.

> 
> Proof is also in the pudding. We also say in Abstract of our I-D, if ND
> RFC's are almost 10 years old, why are popular hosts still making
> mistakes with on-link determination or totally not heeding L bits of RA
> ? ND has to be clarified as we have done so in our I-D.

That may be...  however some of the text in you draft goes too far.  I haven't
read the last version, but I was in the middle of preparing comments
on the last one.

I'll re-read the new version and send comments.

-vlad


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



From ipv6-bounces@ietf.org Tue Jul 03 11:43: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 1I5kXf-0001QQ-92; Tue, 03 Jul 2007 11:43:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5kXd-0001PY-9j
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:43:49 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5kWp-0007tH-TR
	for ipv6@ietf.org; Tue, 03 Jul 2007 11:43:49 -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
	l63Fguwv013163 for <ipv6@ietf.org>; Tue, 3 Jul 2007 18:42:56 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.13.8/8.13.8/Submit) id l63FguxT013160;
	Tue, 3 Jul 2007 18:42:56 +0300
Date: Tue, 3 Jul 2007 18:42:56 +0300
Message-Id: <200707031542.l63FguxT013160@burp.tkv.asdf.org>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org
In-reply-to: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
	(shemant@cisco.com)
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com><7t5bqet8uno.fsf@gpk-xdm-001.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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



> Well, this is exactly the problem with host implementations we are
> concerned with. The prefix list is being populated with a prefix when
> the list should not be populated.

As an implementor IPv6 stack, I say that I had no problem
understanding the L & A bits in prefix announcements.


Just have to verify... You are aware about the "onlink assumption when
no routers present" rule? Early RFC had some wording about that host
must assume any address is onlink, when no routers are present (or was
it "when no route for the destination is found, then try assuming it's
onlink").





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



From ipv6-bounces@ietf.org Tue Jul 03 12:01: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 1I5koM-0004gi-Cp; Tue, 03 Jul 2007 12:01:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5knn-0007so-Rf
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:00:31 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5knj-0002xP-E3
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:00:31 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 03 Jul 2007 12:00:27 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOgOikZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="64272796:sNHT64895348"
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 l63G0QKs015469; 
	Tue, 3 Jul 2007 12:00: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 l63G0P6m014666; 
	Tue, 3 Jul 2007 16:00:26 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, 3 Jul 2007 12:00:13 -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, 3 Jul 2007 12:00:13 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468A6E3E.5000001@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace9iMTvcgHPBNxOT1OIPTRApUsOWAAAQx5w
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<468A6E3E.5000001@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 03 Jul 2007 16:00:13.0575 (UTC)
	FILETIME=[3DA62170:01C7BD8B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4185; t=1183478426;
	x=1184342426; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=sPYsAyEar9KD+3jwAAQ9TrOVWrhPfVp8hRNPJsFjTzw=;
	b=VHNh2MamJC8VSNyqVCFaEbL6Gg8pDDLp7sui3csPfiYp6lRbWaNiI9/fpqQ2TOMb4cSQ2i04
	JqQC9furRVhzOCbRZv7VyuZp1zAMgakawNL07fty9OHyWgktxExC1hPw;
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: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: ipv6@ietf.org, "Ole Troan \(otroan\)" <otroan@cisco.com>
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

Hi Vlad,

Please see in line below against "<hs>".=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Tuesday, July 03, 2007 11:42 AM
To: Hemant Singh (shemant)
Cc: Ole Troan (otroan); Wes Beebee (wbeebee); ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hemant Singh (shemant) wrote:
> Ole,
>=20
> Let's talk specifics, not generics. Of course, we know about section=20
> 5.2 of 2461bis.
>=20
> Snipped is following text from Introduction section of our I-D as to=20
> what we think about section 5.2 of 2461bis:
>=20
>    Sections 5.2 and 7.2.2 imply that the host performs
>    address resolution before transmitting a packet if the destination
of
>    the packet is on the same link as the host.  Some current host
>    implementations perform address resolution in all cases even when
the
>    destination is not clearly on-link.  However, RFC 2461 [ND] section
>    6.3.4 implies that hosts must clearly determine that a destination
is
>    on-link before performing address resolution.=20

Yes.  RFC 2461 allowed you to do that with it's "default on-link"
assumption.
The assumption was that if you did not have an on-link and default
routes, they you assumed that the destination was on-link.

<hs> We are aware of this change from RFC 2461 to 2461bis due to Alain
Durand's I-D which is discussed in bullet 6, section 2 of our I-D.

This assumption has been removed from 2461bis.  However, we can't force
all existing implementations to change.  All we can do is update the
spec.
Existing implementations can still claim conformance to 2461, but not
2461bis.

<hs> If there were a old vs. new implementation issue we were concerned
about, we would have raised the issue. When you raise old vs. new as
above, you have not seen our point. Even for a new implementation, the
host will behave incorrectly because the host populates Prefix list when
the host should not. That is what we replied to in our earlier email on
the subject:

[The prefix list is being populated with a prefix when the list should
not be populated.

In this regard, bullets 2 and 3 in Section 2 of our I-D show the issue
hosts have when hosts incorrectly always add a directly connected route
to the /64 prefix from an address assigned to an interface, even if the
prefix is advertised as "not on link" or is not advertised at all. That
incorrectly added route causes the host to try to use direct delivery
(without sending traffic to the default router) and, therefore, use
NS/NA to resolve addresses from the same prefix.]

>=20
> Section 5.2 says "if the destination is on-link, then next-hop address

> is the same as the packet's destination address. Otherwise, the sender

> selects a router from the default router list." Implementers are not=20
> putting two-and-two together. As described in section 2.1 of our I-D,=20
> if a host has not been sent any PIO in RA, and the host performed=20
> DHCPv6, the host has no way to determine what's on-link for the host.=20
> Section
> 5.2 just says "if the destination in on-link...". Well, discussion=20
> first has to be made as to how can a host determine what's on-link for
it.
> These are the clarifications we have made in our I-D.

Hm...  Searching for "on-link determination" in the text for 2461bis
yields
7 instances that describe how it's done and what information is used.

<hs> And yet hosts still don't get it right!

>=20
> Proof is also in the pudding. We also say in Abstract of our I-D, if=20
> ND RFC's are almost 10 years old, why are popular hosts still making=20
> mistakes with on-link determination or totally not heeding L bits of=20
> RA ? ND has to be clarified as we have done so in our I-D.

That may be...  however some of the text in you draft goes too far.  I
haven't read the last version, but I was in the middle of preparing
comments on the last one.

I'll re-read the new version and send comments.

<hs> Sounds fine. Thanks for the review of our I-D. Please let us know
what text in our I-D goes too far.

Thanks,

-Hemant & Wes.

-vlad

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



From ipv6-bounces@ietf.org Tue Jul 03 12:19: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 1I5l5a-0003Af-6H; Tue, 03 Jul 2007 12:18:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5l5Y-00032S-Gx
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:18:52 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5l4c-0000cx-J5
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:18:52 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 03 Jul 2007 12:17:54 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAJcTikZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,492,1175486400"; 
	d="scan'208"; a="64274754:sNHT43112686"
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 l63GHsKD008474; 
	Tue, 3 Jul 2007 12:17:54 -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 l63GHr6c019807; 
	Tue, 3 Jul 2007 16:17: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); 
	Tue, 3 Jul 2007 12:17: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, 3 Jul 2007 12:17:43 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CF7@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <200707031542.l63FguxT013160@burp.tkv.asdf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace9iRTB05cP1+XwTkWKKF+uo4n/OAAAjKNw
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com><468678D1.40000@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com><7t5bqet8uno.fsf@gpk-xdm-001.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com><7t57iph8sw1.fsf@gpk-xdm-001.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
	<200707031542.l63FguxT013160@burp.tkv.asdf.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Markku Savela" <msa@moth.iki.fi>, <ipv6@ietf.org>
X-OriginalArrivalTime: 03 Jul 2007 16:17:43.0782 (UTC)
	FILETIME=[AF9F0060:01C7BD8D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1989; t=1183479474;
	x=1184343474; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Markku=20Savela=22=20<msa@moth.iki.fi>,=20<ipv6@ietf.org>;
	bh=6rTfCzNKApuuY1l5nYSZtJzPQzh5wnHuW6rWMUZMqCM=;
	b=IY0RARqA8vlUn9bkxWkEOgLo57IsZLdbgQmt3DeJuIhruREzN8bd2EkaeI5O2PlniNPYymx4
	awJnIWrUHsyvYrq7QQfcBBh8GIf364YWgTVpE9y0BASQN9CtSrRGMh/q;
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: 4d87d2aa806f79fed918a62e834505ca
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

=20
Markku,

Please see in line below against "<hs>".

-----Original Message-----
From: Markku Savela [mailto:msa@moth.iki.fi]=20
Sent: Tuesday, July 03, 2007 11:43 AM
To: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO



> Well, this is exactly the problem with host implementations we are=20
> concerned with. The prefix list is being populated with a prefix when=20
> the list should not be populated.

As an implementor IPv6 stack, I say that I had no problem understanding
the L & A bits in prefix announcements.

<hs> We are not saying a host implementer cannot get it right. We are
saying some don't. We have found a popular host implementation to be
blatantly ignoring off-link indication in RA. Further, hosts are most
confused for data forwarding and address resolution when no PIO is sent
in RA. That is what we focused on in section 2.1 of our I-D.=20

Just have to verify... You are aware about the "onlink assumption when
no routers present" rule? Early RFC had some wording about that host
must assume any address is onlink, when no routers are present (or was
it "when no route for the destination is found, then try assuming it's
onlink").

<hs> Please refer to bullet 6, section 2 of our I-D where we discuss
this case. The case of a network in which no routers are present is
covered by text in the bullet. If no routers are present, the Default
Router List will be empty. Our text says "If the Default Router List is
empty, the host MUST NOT assume that all destinations are on-link..."
The corresponding text has changed from 2461 to 2461bis.  We are aware
that there are some implementations which may be compliant with 2461
that are not compliant with 2461bis.

Thanks,

- Hemant & Wes.=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 Jul 03 12:19: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 1I5l5x-0004AM-JM; Tue, 03 Jul 2007 12:19:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5l5w-00044W-Ak
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:19:16 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5l5v-0004oc-UT
	for ipv6@ietf.org; Tue, 03 Jul 2007 12:19:16 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l63GFlGZ081376
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <ipv6@ietf.org>; Tue, 3 Jul 2007 18:15:48 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <9F56CE94-AC72-4FA2-907B-ACCF390EFEE3@muada.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF IPv6 Mailing List <ipv6@ietf.org>
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 3 Jul 2007 18:17:25 +0200
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: draft-van-beijnum-multi-mtu-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

First of all: this message is going out to the IPv6 wg and internet  
area mailinglists (for reasons explained below) but it's not  
crossposted, so replies will go to the list where you found it by  
default unless you add the other one yourself.

The internet-drafts administrator was kind enough to publish the  
following draft:

http://www.ietf.org/internet-drafts/draft-van-beijnum-multi-mtu-00.txt

The idea here is to lift the limitation that all nodes connected to a  
subnet must all use the same MTU by adding mechanisms to negotiate  
the use of bigger packets between two nodes. Hopefully, this will  
make it possible to start increasing the MTU on many links that make  
up the internet. Currently, there is some form of ethernet in almost  
all paths across the internet, and all forms of ethernet use an MTU  
of 1500 bytes, even though gigabit ethernet hardware generally  
supports larger sizes. The problem is that switches can't fragment  
and ethernet is stateless so the IEEE can't mandate larger packet  
sizes for faster ethernet. But IP can fragment, or, more generally,  
adjust the packet size, and has at least some per-neighbor state so  
we can solve this at the IP layer.

Ultimately, the idea is that this will work for both IPv4 and IPv6.  
So at a high level, this would be an appropriate discussion topic for  
the internet area list.

However, IPv4 doesn't have many hooks where new options can be added  
easily like IPv6, so I'm focussing on IPv6 at this time. The draft  
specifies:

- a new router advertisement option
- two new ICMPv6 messages
- a new neighbor discovery option

So it would be nice to get feedback on the protocol details from the  
people who tend to hang out in the IPv6 wg.

Any feedback is greatly appreciated.

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



From ipv6-bounces@ietf.org Tue Jul 03 14:55: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 1I5nWT-0000sh-KX; Tue, 03 Jul 2007 14:54:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nWR-0000rt-UO
	for ipv6@ietf.org; Tue, 03 Jul 2007 14:54:47 -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 1I5nVg-00055Q-EB
	for ipv6@ietf.org; Tue, 03 Jul 2007 14:54:47 -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 l63IruWj017992;
	Tue, 3 Jul 2007 11:53:59 -0700
Message-ID: <04d601c7bda3$77695860$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Scott Leibrand" <sleibrand@internap.com>,
	"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>
	<46844352.2090601@internap.com>
Date: Tue, 3 Jul 2007 13:38:43 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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: 9466e0365fc95844abaf7c3f15a05c7d
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

Thus spake "Scott Leibrand" <sleibrand@internap.com>
> 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.

I think we all agree that ULA prefixes _should_ be kept out of the DFZ, but 
the organizations (IETF, RIRs) debating this policy have absolutely zero 
ability to make it happen.  At most, it's a suggestion to operators, and 
I'll need more than a mere suggestion that a unique prefix isn't routable to 
be even neutral on the topic.

If people want guaranteed-unique addresses, let them go to their RIR for PI 
space.  If their RIR doesn't give such out, they can change the policies. 
If they're unable to change the policies, there obviously is not sufficient 
public support for the idea in the first place, and the IETF has no business 
telling the RIRs they're wrong.

ULA-C is an attempt to get around RIR policy mechanisms, plain and simple. 
Don't give me this "but the RIRs don't have to take it" stuff, because 
registry shopping will occur.  As long as one RIR signs up, we're all going 
to be forced to live with the results.

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 Tue Jul 03 15: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 1I5nzT-0006WW-Q1; Tue, 03 Jul 2007 15:24:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nzR-0006Up-PL
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:24:45 -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 1I5nzK-0003MQ-7o
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:24:45 -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 l63JOYgm018051;
	Tue, 3 Jul 2007 12:24:37 -0700
Message-ID: <061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Jeroen Massar" <jeroen@unfix.org>, "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>
Date: Tue, 3 Jul 2007 14:13:07 -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: 8abaac9e10c826e8252866cbe6766464
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

Thus spake "Jeroen Massar" <jeroen@unfix.org>
> 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?
...
> 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 supposed use case for ULA-C is large orgs who interconnect privately 
with other large orgs.  If you _don't_ allow ULA-Cs in the global reverse 
DNS, then every org in the internetwork must hack their local DNS servers to 
recognize every other org's reverse DNS entries.  That is painful and 
unnecessary.

There are operational concerns with putting ULA(-C) addresses in forward 
DNS; nobody argues with that.  However, putting ULA-C addresses in reverse 
DNS harms nobody who can't reach those addresses yet greatly benefits those 
that can.

Of course, if everyone just used PI, none of this would be an issue.

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 Tue Jul 03 15: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 1I5nzQ-0006Sm-2y; Tue, 03 Jul 2007 15:24:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5nzN-0006Le-Sj
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:24:41 -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 1I5nzJ-0003MO-G5
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:24:41 -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 l63JOYgl018051;
	Tue, 3 Jul 2007 12:24:36 -0700
Message-ID: <061d01c7bda7$bddaf520$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Scott Leibrand" <sleibrand@internap.com>,
	"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>
	<467870DC.2030802@internap.com>
Date: Tue, 3 Jul 2007 14:02:56 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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: 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

Thus spake "Scott Leibrand" <sleibrand@internap.com>
> 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.

The only legitimate reason to bother with 1:1 NAT is because one can't get 
PI space.  Solution: make PI space available.  Oh, wait, we already did 
that...

However, there are other reasons people use NAT today, mainly because they 
confuse NAT with a stateful firewall.  Such people will continue to use NAT 
(or PAT) even if they have PI or ULA(-C) space on the "inside".

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

If the use is truly private, then there is no public cost.

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

The thing is, if the network is "small", i.e. too small to qualify for PI 
space, then RFC 4193 is more than sufficient.

The only reasonable use cases I've heard for ULA-C are for orgs so big and 
with so many interconnections that ULA is not sufficient; those orgs can get 
PI without any challenges today, which means ULA-C offers nothing new.

I fail to see the "innovation" here.

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 Tue Jul 03 15:46: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 1I5oKd-000451-Tk; Tue, 03 Jul 2007 15:46:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5oKd-00044v-19
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:46:39 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5oJn-0008FU-9K
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:46:39 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id C2B0311426
	for <ipv6@ietf.org>; Tue,  3 Jul 2007 19:45: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 "Tue, 03 Jul 2007 13:38:43 EST."
	<04d601c7bda3$77695860$543816ac@atlanta.polycom.com> 
References: <E1I0NEg-000884-8o@stiedprstage1.ietf.org>
	<13846.1183003509@sa.vix.com><Pine.LNX.4.64.0706282314180.29317@chandra.student.uit.no>
	<46844352.2090601@internap.com>
	<04d601c7bda3$77695860$543816ac@atlanta.polycom.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 03 Jul 2007 19:45:43 +0000
Message-ID: <69523.1183491943@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
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

["Stephen Sprunk" <stephen@sprunk.org>]
> ULA-C is an attempt to get around RIR policy mechanisms, plain and simple.

no.  nor ULA-G.  read the drafts.  ask the authors what they're attempting,
and then call us liars if you wish, but do not under any circumstances tell
us what we're attempting.  we already know.

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



From ipv6-bounces@ietf.org Tue Jul 03 15:48: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 1I5oM0-0006bF-2M; Tue, 03 Jul 2007 15:48:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5oLy-0006Z9-84
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:48:02 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5oLP-0000QH-SP
	for ipv6@ietf.org; Tue, 03 Jul 2007 15:48:02 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 03 Jul 2007 12:47:27 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CACxEikarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,494,1175497200"; d="scan'208"; a="6248583:sNHT14574990"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l63JlRIp021577
	for <ipv6@ietf.org>; Tue, 3 Jul 2007 12:47:27 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l63JlRka020664
	for <ipv6@ietf.org>; Tue, 3 Jul 2007 19:47:27 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 12:47:26 -0700
Received: from [192.168.1.2] ([10.21.113.57]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 12:47:26 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
References: <29134C2C-6E4E-43D7-876D-E1EC7F4ABE2C@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B21C02EF-6F4C-4070-9CD5-D350CE992025@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Date: Tue, 3 Jul 2007 12:47:22 -0700
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 03 Jul 2007 19:47:26.0622 (UTC)
	FILETIME=[FB9403E0:01C7BDAA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3832; t=1183492047;
	x=1184356047; c=relaxed/simple; s=sjdkim1004;
	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:=20Fwd=3A=20I-D=20ACTION=3Adraft-baker-v6ops-b2b-private-routing
	-00.txt=20 |Sender:=20;
	bh=TqnCBi8WOBHfxaaLSEJWphPShxHGSlcwQGaHnSwfRN0=;
	b=AKbukUhWM9E7vREn1RyxRk1bzWRD2pj+0j5bWMcnmWGO53SPAC3mZGAOzmVMuO+/MhcUOmMQ
	7jx3UeFSh7BhCgNOKBUYzG+bP11VC++OGzMicPoiFrIiSOblrYqheWKwahNPiZBpTMoHwzlXSy
	rCJl+/JuqttJnVJWApGANuBjo=;
Authentication-Results: sj-dkim-1; header.From=fred@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Subject: Fwd: I-D ACTION:draft-baker-v6ops-b2b-private-routing-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

Folks -

I dropped in a draft regarding a routing problem I was asked about by  
a person from Cisco IT. The real value is a use case for the ULA (and  
specifically the centrally-assigned one, if we are going to do that)  
in private (non-ISP) business-to-business communications. Some ISPs  
right now are arguing that only ISPs should have access to centrally- 
assigned classes of ULAs, which seems an unnecessary restriction at  
best. It also documents the fact that there exists non-ISP Business- 
to-business networking, where the IETF generally views Internet  
connectivity as being either within the enterprise or something  
specific to ISPs. You may also find the problem presented interesting  
intellectually, and you may have comments you would like to make. I'd  
personally suggest that discussion be on v6ops@ops.ietf.org, as this  
is an operational issue, but I thought I would drop a note here as a  
"heads-up".

Any comments you have are of interest. I don't plan to pursue this as  
a v6ops WG document, although we can go there is someone wants it to.  
I'll probably just mail it off to the RFC Editor at some point, though.

Fred


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: July 3, 2007 8:15:01 AM PDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-baker-v6ops-b2b-private-routing-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> 	Title		: Business to Business Private Routing
> 	Author(s)	: F. Baker
> 	Filename	: draft-baker-v6ops-b2b-private-routing-00.txt
> 	Pages		: 10
> 	Date		: 2007-7-3
> 	
>    This note describes a network architecture for business-to-business
>    private networking.  It actually describes two: one for IPv4 and  
> one
>    for IPv6.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-baker-v6ops-b2b-private- 
> routing-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-baker-v6ops-b2b-private-routing-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-baker-v6ops-b2b-private-routing-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2007-7-3101511.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce

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



From ipv6-bounces@ietf.org Tue Jul 03 16:26: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 1I5owo-0003CY-7e; Tue, 03 Jul 2007 16:26:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5owm-0003CN-E4
	for ipv6@ietf.org; Tue, 03 Jul 2007 16:26:04 -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 1I5owf-00025B-NO
	for ipv6@ietf.org; Tue, 03 Jul 2007 16:26:04 -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 l63KPuJD018187;
	Tue, 3 Jul 2007 13:25:57 -0700
Message-ID: <078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <george+ipng@m5p.com>, <ipv6@ietf.org>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
Date: Tue, 3 Jul 2007 15:23:28 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; 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: 93238566e09e6e262849b4f805833007
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

Thus spake <george+ipng@m5p.com>
>> 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.
>
> 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!

More importantly, the odds of human or technical error that causes a 
collision at a theoretical ULA-C registry is far, far higher than 2^-40. 
The only difference is that if there's a registry, the end-users have 
someone to sue when a collision happens.

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 Tue Jul 03 16:57: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 1I5pQW-00005I-S7; Tue, 03 Jul 2007 16:56:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5pQV-00005C-Is
	for ipv6@ietf.org; Tue, 03 Jul 2007 16:56:47 -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 1I5pQR-0000Q1-5j
	for ipv6@ietf.org; Tue, 03 Jul 2007 16:56:47 -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 l63Kudmm018255;
	Tue, 3 Jul 2007 13:56:40 -0700
Message-ID: <07d601c7bdb4$9b5413d0$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Jeroen Massar" <jeroen@unfix.org>,
	"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>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
Date: Tue, 3 Jul 2007 15:47:50 -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: 082a9cbf4d599f360ac7f815372a6a15
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

Thus spake "Jeroen Massar" <jeroen@unfix.org>
> 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 ...

The least controversial means of getting PIv6 passed was to say that orgs 
qualified for it if they also qualified for PIv4.  That bar is presently 256 
hosts (25% of a /22) if you're multihomed or 1024 hosts (25% of a /20) if 
you're not.

ARIN recently rejected a proposal to reduce the PIv4 bar to a /24 (i.e. 64 
hosts); there was a bit of grumbling about routing table bloat, but that was 
_by far_ overshadowed by concerns about spammers.

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

You have it backwards.  Certain people in this WG were trying to force ULA-C 
on the community two years ago, and ARIN responded by passing PIv6.  That 
killed ULA-C, but it has risen from the dead and is again terrorizing the 
populace.  What do we need to do to kill it for good this time?  Garlic? 
Holy water?

> Clearly ULA-C is just "cheap address space", nothing more
> nothing less.

There is no reason to think that the RIRs' cost of registering and managing 
a /48 in fc00::/8 will be any less than the cost of registering and managing 
a /48 in 2000::/3.  Since all of the RIRs operate on a cost-recovery basis, 
that means the fees should be the same.  Ergo, ULA-C will not be any cheaper 
under the currently proposed model.

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

Then it's time to either fix the policies or solve the id/loc problem.

> The RIR community effectively blocks people from getting
> address space on the premise that "but that costs routing
> slots", ... and then on top of that basing that decision on
> IPv4 address space usage, wow.

Qualification, not usage.  ARIN does not actually require you to apply for 
PIv4 space (or have a v4 network at all for that matter) in order to get 
PIv6 space.

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 Tue Jul 03 17:29: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 1I5pvM-0004kq-Fr; Tue, 03 Jul 2007 17:28:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5pvK-0004kg-UE
	for ipv6@ietf.org; Tue, 03 Jul 2007 17:28:38 -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 1I5puB-000771-Gq
	for ipv6@ietf.org; Tue, 03 Jul 2007 17:28:38 -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 l63LRO0s018355;
	Tue, 3 Jul 2007 14:27:26 -0700
Message-ID: <085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"Kevin Kargel" <kkargel@polartel.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
	<46827A57.7030203@gmail.com>
Date: Tue, 3 Jul 2007 16:11:12 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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

Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> 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,

... assuming everyone follows the rules in RFC 4193.  However, what if a /48 
isn't enough for some network and they decide to use a /45?  Is that better 
or worse than eight properly-derived /48s?

> and ULA-C is no different in that respect.

With the current draft, that is correct.  With Paul's proposed changes of 27 
Jun, they definitely aggregate at the LIR and RIR levels, making it much 
harder to defend the position that they won't end up in the DFZ.

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 Tue Jul 03 18:37: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 1I5qzf-0002vO-Go; Tue, 03 Jul 2007 18:37:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5qzc-0002OZ-Uk
	for ipv6@ietf.org; Tue, 03 Jul 2007 18:37:08 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5qzX-0005pb-3E
	for ipv6@ietf.org; Tue, 03 Jul 2007 18:37:08 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85581081; Tue, 03 Jul 2007 18:37:02 -0400
Message-ID: <468ACF81.1080508@internap.com>
Date: Tue, 03 Jul 2007 15:36:49 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
In-Reply-To: <085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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

Stephen Sprunk wrote:
>
> With the current draft, that is correct.  With Paul's proposed changes 
> of 27 Jun, they definitely aggregate at the LIR and RIR levels, making 
> it much harder to defend the position that they won't end up in the DFZ.

I'm not quite following your logic here.  If ARIN allocates ULA-G space 
from a distinct netblock, how does that make it any harder for transit 
providers to filter routes from fc00::/7, reduce their incentive to do 
so, or create an incentive not to?

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 Tue Jul 03 19:05: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 1I5rQY-0007Q2-57; Tue, 03 Jul 2007 19:04:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5rQX-0007P4-83
	for ipv6@ietf.org; Tue, 03 Jul 2007 19:04:57 -0400
Received: from isc.trstech.net ([2001:4f8:0:1::23:2] helo=afribone.trstech.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5rQD-0007Sb-KZ
	for ipv6@ietf.org; Tue, 03 Jul 2007 19:04:57 -0400
Received: from localhost ([127.0.0.1] helo=trstech.net)
	by afribone.trstech.net with esmtp (Exim 4.66)
	(envelope-from <aalain@trstech.net>)
	id 1I5rOA-0000xp-3e; Tue, 03 Jul 2007 23:02:45 +0000
From: "Alain Patrick AINA" <aalain@trstech.net>
To: bill fumerola <billf@mu.org>
Date: Wed, 4 Jul 2007 00:02:30 +0100
Message-Id: <20070703225930.M25145@trstech.net>
In-Reply-To: <20070703015345.GK9951@elvis.mu.org>
References: <20070627204814.GR31273@elvis.mu.org>
	<200707021217.45932.aalain@trstech.net>
	<20070703015345.GK9951@elvis.mu.org>
X-Mailer: OpenWebMail 2.52 20060502
X-OriginatingIP: 41.207.180.67 (aalain)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: aalain@trstech.net
X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on 
	afribone.trstech.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=2.5 tests=ALL_TRUSTED,BAYES_00,
	DNS_FROM_RFC_ABUSE autolearn=ham version=3.1.4
X-SA-Exim-Version: 4.2.1 (built Wed, 24 Jan 2007 18:13:53 +0000)
X-SA-Exim-Scanned: Yes (on afribone.trstech.net)
X-Spam-Score: -2.4 (--)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org
Subject: Re: 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

On Mon, 2 Jul 2007 18:53:45 -0700, bill fumerola wrote
> On Mon, Jul 02, 2007 at 12:17:45PM +0000, Alain Patrick AINA wrote:
> > > 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.
> > 
> > no.
> 
> please elaborate.

that angle of things was not brought up during the discussions.

--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 Jul 03 20:32: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 1I5smf-0005NN-Nj; Tue, 03 Jul 2007 20:31:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5sme-0005N9-Ar
	for ipv6@ietf.org; Tue, 03 Jul 2007 20:31:52 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I5smd-0001gb-WB
	for ipv6@ietf.org; Tue, 03 Jul 2007 20:31:52 -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 l640Ujui018712;
	Tue, 3 Jul 2007 17:30:46 -0700
Message-ID: <091101c7bdd2$83f21250$543816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Scott Leibrand" <sleibrand@internap.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
	<468ACF81.1080508@internap.com>
Date: Tue, 3 Jul 2007 19:23:29 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: 8abaac9e10c826e8252866cbe6766464
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

Thus spake "Scott Leibrand" <sleibrand@internap.com>
> Stephen Sprunk wrote:
>> With the current draft, that is correct.  With Paul's proposed changes of 
>> 27 Jun, they definitely aggregate at the LIR and RIR levels, making it 
>> much harder to defend the position that they won't end up in the DFZ.
>
> I'm not quite following your logic here.  If ARIN allocates ULA-G space 
> from a distinct netblock, how does that make it any harder for transit 
> providers to filter routes from fc00::/7, reduce their incentive to do so, 
> or create an incentive not to?

If they can be aggregated, there's no reason _not_ to route them in the DFZ. 
With no technical incentive to filter, the financial incentive to _not_ 
filter will win.

ULA-L and ULA-C have a pseudorandom network part specifically to avoid any 
possibility of aggregation, in hopes that'll be sufficient technical 
incentive for them to be filtered.  When you start divvying up those bits 
and giving them meaning, particularly a hierarchical meaning based on the 
RIR and LIR that assigned them, you're no longer working with "local" 
anything.

It's bad enough that ULA-C is reinventing PI space; we don't need ULA-G 
reinventing PA space.

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 Tue Jul 03 22:24: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 1I5uXG-0004PT-PF; Tue, 03 Jul 2007 22:24:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5uXF-0004PL-TC
	for ipv6@ietf.org; Tue, 03 Jul 2007 22:24:05 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5uX3-0002WZ-KK
	for ipv6@ietf.org; Tue, 03 Jul 2007 22:24:05 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id DD8D411431
	for <ipv6@ietf.org>; Wed,  4 Jul 2007 02:23: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 "Tue, 03 Jul 2007 15:36:49 MST."
	<468ACF81.1080508@internap.com> 
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
	<468ACF81.1080508@internap.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 04 Jul 2007 02:23:52 +0000
Message-ID: <35308.1183515832@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
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

> > With the current draft, that is correct.  With Paul's proposed changes of
> > 27 Jun, they definitely aggregate at the LIR and RIR levels, making it
> > much harder to defend the position that they won't end up in the DFZ.

the aggregation present in that version was unintentional.  if you look at
the actual <http://sa.vix.com/~vixie/ula-global.txt> you'll see that it
recommends that allocations be deliberately nonaggregatable.

> I'm not quite following your logic here.  If ARIN allocates ULA-G space
> from a distinct netblock, how does that make it any harder for transit
> providers to filter routes from fc00::/7, reduce their incentive to do so,
> or create an incentive not to?

my concern about aggregation is that if someone receives 8 /48's that are
aligned as a /45 then they could conceivably advertise it as a /45.  i hope
that IANA will allocate nonaligned blocks, or perhaps give even numbers to
one RIR and odd numbers to the next, and that the RIRs and LIRs will do
likewise.

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



From ipv6-bounces@ietf.org Wed Jul 04 04:03: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 1I5zpW-0003Lg-SA; Wed, 04 Jul 2007 04:03:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5zpV-00038e-02
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:03:17 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5zpQ-0000vJ-KN
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:03:16 -0400
Received: by ug-out-1314.google.com with SMTP id u2so694928uge
	for <ipv6@ietf.org>; Wed, 04 Jul 2007 01:03: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=nfhfoE4WoH3gPW+RRZrOA3bt7NHDRYV1VP/bKAZ0luZbUqMwhXrvEDMSYybv4v0MQGkYfkjmauUcAkRxck35XbkCUWrxIRzUbk+4i3vonQlrRM0iHeaJ+nrT0fJtkpzMPIWU/cfRpSDc41LnrsomZsvXT3eFID5iSMq39t36qXk=
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=PjpL0GaL02CFpmR9E9HAwjYN32Ul8/XGBfKCyGtNxLWS/HJOuTPU6EcHw0x1P160k8OY0Ay2vZP+5PCZm/K0mTxHFZmbqKakrLK6huIy4pRvRQI20vRbx+BZnQrMbCbxZYhwsUgA+6umlpY5UYvZWDEdA8X4fpJ+fZMPAdIgv9k=
Received: by 10.82.111.8 with SMTP id j8mr17292667buc.1183536191425;
	Wed, 04 Jul 2007 01:03:11 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id f7sm7511601nfh.2007.07.04.01.03.09
	(version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 01:03:10 -0700 (PDT)
Message-ID: <468B543C.6040203@gmail.com>
Date: Wed, 04 Jul 2007 10:03: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: Paul Vixie <paul@vix.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>	<46827A57.7030203@gmail.com>	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>	<468ACF81.1080508@internap.com>
	<35308.1183515832@sa.vix.com>
In-Reply-To: <35308.1183515832@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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-07-04 04:23, Paul Vixie wrote:
>>> With the current draft, that is correct.  With Paul's proposed changes of
>>> 27 Jun, they definitely aggregate at the LIR and RIR levels, making it
>>> much harder to defend the position that they won't end up in the DFZ.
> 
> the aggregation present in that version was unintentional.  if you look at
> the actual <http://sa.vix.com/~vixie/ula-global.txt> you'll see that it
> recommends that allocations be deliberately nonaggregatable.
> 
>> I'm not quite following your logic here.  If ARIN allocates ULA-G space
>> from a distinct netblock, how does that make it any harder for transit
>> providers to filter routes from fc00::/7, reduce their incentive to do so,
>> or create an incentive not to?
> 
> my concern about aggregation is that if someone receives 8 /48's that are
> aligned as a /45 then they could conceivably advertise it as a /45.  i hope
> that IANA will allocate nonaligned blocks, or perhaps give even numbers to
> one RIR and odd numbers to the next, and that the RIRs and LIRs will do
> likewise.

On the hypothesis that we do something like ULA-G, I agree with that.

There is a statistical sense in which ULA-G would be more *potentially*
aggregatable than ULA or ULA-C. If ULA-G prefixes are allocated
on an RIR/LIR basis, the chance that two logically adjacent prefixes
happen to be used by customers of the same local ISP will be finite,
whereas it's vanishingly small for ULA or ULA-C.

     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 Jul 04 04:07: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 1I5ztV-0004Zz-Rs; Wed, 04 Jul 2007 04:07:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I5ztT-0004EX-4Q
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:07:23 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5ztP-0002UE-9a
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:07:23 -0400
Received: by ug-out-1314.google.com with SMTP id u2so695676uge
	for <ipv6@ietf.org>; Wed, 04 Jul 2007 01:07:18 -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=JtNiTxmCCyQ3hFYRCu22D7sodrsrEZLr9FnjBXM4Uj6J7yuIugE45N3lbgiXa8iqMI6vUl1u39wk79EjYSNRLfdxWki1omhrhptjSXc2k05sbltZuQ+aTHQl+e78ifIU2faa1n0Iwrf4uVFWDXygu/ZEXzkQa4YlCxMVJWgachU=
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=K+FjhBaSRDgovMC2bl29mIeKYgqJK082RXeBEZ++kPW+Kl4GLyG7qndfm1GZtATvQKI4U+gKoV/72K/Zdig/OlAAIm1tLnF2sVwadwbDPMZ405xTPj7A0nm//lNTFGjWiEolzSpewpgdcDE5WJdkpye33JMzxCz1OEOeF1rqgiQ=
Received: by 10.82.151.14 with SMTP id y14mr17264204bud.1183536438295;
	Wed, 04 Jul 2007 01:07:18 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 34sm5645276nfu.2007.07.04.01.07.17
	(version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 01:07:17 -0700 (PDT)
Message-ID: <468B5534.5000701@gmail.com>
Date: Wed, 04 Jul 2007 10:07:16 +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>	<4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com>
	<46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com>
	<13412.1183471599@sa.vix.com>
In-Reply-To: <13412.1183471599@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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-07-03 16:06, Paul Vixie wrote:
...
>> I'll be happy to give my hosts U?A addresses so they can communicate with
>> the rest of the city at WLAN/MAN speeds, as well as PA addresses to
>> communicate with the rest of the world at Internet speed.
> 
> note that in brian's best-possible-world scenario, you'd be able to do what
> you want with PI.  however, we're not in that world, and we need the crutch
> of leading high-end address bits to tell our NATv6 boxes when to act, and to
> tell our DFZ-path routers when not to act.  thus, ULA-G or ULA-C.

The reference to NATv6 confuses me. There's nothing about ULA-* that leads to
NAT. Users will have PA (or PI for the lucky few) prefixes for global connectivity.
ULA-* is for local use (in the sense that RFC 4864 uses "local").

     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 Jul 04 04: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 1I6029-0005ts-AV; Wed, 04 Jul 2007 04:16:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6027-0005nS-9E
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:16:19 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6025-0003nF-Gp
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:16:19 -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 4E52B7301E
	for <ipv6@ietf.org>; Wed,  4 Jul 2007 17:16:15 +0900 (JST)
Date: Wed, 04 Jul 2007 17:16:04 +0900
Message-ID: <m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: ipv6@ietf.org
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
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: multipart/mixed; boundary="Multipart_Wed_Jul__4_17:16:04_2007-1"
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Subject: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

--Multipart_Wed_Jul__4_17:16:04_2007-1
Content-Type: text/plain; charset=US-ASCII

I'm now completing 2462bis (which is now in the AUTH48 state)
addressing post IESG-approval issues.  The remaining issues are
basically trivial, but I found one unresolved issue in the ML archive
that may be substantial.

I've read the issue description again, and would like to propose the
simplest solution:

   A. simply discard the packet (like BSD/KAME)

Namely I propose to change the text from

   [...] If
   the target address is assigned to the receiving interface, the
   solicitation is processed as described in [RFC4861].

to

   [...] If
   the target address is assigned to the receiving interface, the
   advertisement SHOULD be silently discarded.

In fact, I think this should be compatible with the first paragraph of
Section 7.2.5 of RFC2461 (and coming RFC4861).

Please let me know ASAP if anyone has an objection to this proposal.

Thanks,

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


--Multipart_Wed_Jul__4_17:16:04_2007-1
Content-Type: message/rfc822

X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on impact.jinmei.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,
	UNPARSEABLE_RELAY autolearn=ham version=3.1.0
X-Original-To: jinmei@shuttle.wide.toshiba.co.jp
Delivered-To: jinmei@shuttle.wide.toshiba.co.jp
Delivered-To: jinmei@isl.rdc.toshiba.co.jp
Date: Thu, 02 Mar 2006 23:20:26 +0900
Message-ID: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: ipv6@ietf.org
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org
X-Spam: exempt
X-MAIL-FROM: <ipv6-bounces@ietf.org>
X-SOURCE-IP: [210.149.48.6]

I guess I found yet another corner case of the DAD processing (for
rfc2462bis)...

In Section 5.4.4, the latest draft of rfc2462bis-08.txt says (this
part essentially doesn't change since RFC1971):

=======================================================================
5.4.4  Receiving Neighbor Advertisement Messages

   On receipt of a valid Neighbor Advertisement message on an interface,
   node behavior depends on whether the target address is tentative or
   matches a unicast or anycast address assigned to the interface.  If
   the target address is assigned to the receiving interface, the
   solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
   If the target address is tentative, the tentative address is not
   unique.
=======================================================================

Clearly, "the solicitation" looks odd.  It looks like a copy of a
similar sentence in the previous section:

=======================================================================
5.4.3  Receiving Neighbor Solicitation Messages
[...]

   ...  If the target address is not tentative (i.e., it is assigned to
   the receiving interface), the solicitation is processed as described
   in [I-D.ietf-ipv6-2461bis].  [...]

(This perfectly makes sence)
=======================================================================

The easiest fix would be to replace "solicitation" with
"advertisement", but then how it should be processed?  Processing it
"as defined in [I-D.ietf-ipv6-2461bis]" (or in RFC2461) does not make
sense here, because this is an abnormal case where some neighboring
node sends an NA targeting a valid address (to be proved as unique)
assigned to the receiving node.

The BSD/KAME implementation simply discards the NA in such a case.  It
may be a reasonable behavior.  However, if this scenario could ever
happen, it would probably mean the address is actually a duplicate and
the responding node (that has the authority for the address) just
reacted too slowly.  So now I'm not sure if this behavior is really
correct.

My questions are:

1. what is the valid behavior in this case?
   A. simply discard the packet (like BSD/KAME)
   B. discard the packet but make an explicit log message
   C. stop using the 'possibly duplicate' address (which sounds a bad
      idea...)
   D. others

2. should the 'valid behavior' be described in the coming RFC based on
   rfc2462bis as part of the AUTH48 editorial phase, or is it too late?
   (this may depend on the answer to question 1, though)

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

--Multipart_Wed_Jul__4_17:16:04_2007-1
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
--------------------------------------------------------------------

--Multipart_Wed_Jul__4_17:16:04_2007-1--




From ipv6-bounces@ietf.org Wed Jul 04 04:49: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 1I60Y3-0001ee-6v; Wed, 04 Jul 2007 04:49:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I60Y1-0001cU-LR
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:49:17 -0400
Received: from ik-out-1112.google.com ([66.249.90.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I60Xw-0008GE-VH
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:49:17 -0400
Received: by ik-out-1112.google.com with SMTP id b32so1581296ika
	for <ipv6@ietf.org>; Wed, 04 Jul 2007 01:49:12 -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=sxy0MOtXnQSwjAEFqVe365Xo2kQamAVOT0C/xDqNhoyqY/OlLMkmlXwMg6K8Ba/KBDfd7tGiBAdXKHWEf4L0UEPWadk288ChINe1fpMDuybW0mcV1ET60i7TkU/YoCV6jtpYhiWwj1k4hXf2M0CdZ5T32gzN4h1/LPo/ubOYBEE=
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=KdXcWu2I5abDlTv6l0G04mH+3SctpcgWccszqeLJ7RYGNvEHwA9ysoIiYCQlf6FxTklVTZ5/6BA3m0DTePM3qu/9cXdp7+DTVgf4NpY3s0ntyxAR19mAt183OjcX0YbSoGh7sv3++DQFzP/P2Wv/wRFyATFJ9ZnrmavR5qDcST4=
Received: by 10.78.180.18 with SMTP id c18mr3972640huf.1183538951359;
	Wed, 04 Jul 2007 01:49:11 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id d23sm5866629nfh.2007.07.04.01.49.09
	(version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 01:49:10 -0700 (PDT)
Message-ID: <468B5F02.7000600@gmail.com>
Date: Wed, 04 Jul 2007 10:49: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: 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>	<4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>	<468A02EC.3080509@gmail.com>
	<20140.1183474407@sa.vix.com>
In-Reply-To: <20140.1183474407@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
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-07-03 16:53, Paul Vixie wrote:
> [paul vixie]
>>> ...  i don't have objective measurements, but i know that a lot of table
>>> size control is achieved by limiting the horizon of announcements.
> 
> [brian carpenter]
>> Absolutely. And from what I've heard, "a lot" may in fact be as much
>> as 90% for some ISPs.
> 
> so, we share a supposition that the DFZ is now a minority of "the Internet".

Or possibly that we don't know what "the Internet" is any more...

> 
>>> ULA-C with my proposed diffs is just a way to take this a lot further, to
>>> legitimize it, to scale it up to planetary size.
>> And actually that is where we seem to be at odds. I fear that ULA-G will
>> leak.  That's all.
> 
> consider a spectrum of possibilities:
> 
>     --------------------------------------------------------
>      O(10^4)                 O(10^6)                O(10^8)
> 
> in the leftmost cast, the number of ULA-G prefixes is so small that we could
> accomodate them in the DFZ, and the only "problem" would be that it was an end
> run around regional (RIR) policymaking.
> 
> in the rightmost case, the number of ULA-G prefixes is so large that no single
> routing table can hold them, not even the much vaunted 2-megaroute machinery
> that's now on various drawing boards.

Certainly. And that is roughly the scale that the RAM debate is
considering, although the working hypothesis there is more like
10^7 prefixes.

> 
> in the middle, there's a range of size that's large enough to hurt a lot but
> small enough to be practical if everybody sends cisco and juniper a great deal
> of money.
> 
> what is the size of your fear?  i ask because my supposition is that the DFZ
> is already a minority and that something like ULA-G (or even ULA-C) would make
> it an even smaller minority.  and i consider the rightmost case the likeliest
> number of ULA-G routes, and that the number of likely DFZ leaks to be zero.

Well, my hypothesis is a network with 10^10 nodes and with 10^7 prefixes
in need of multihoming across the DFZ. But no ULA-* prefixes should be
in the DFZ; so these hypotheses seem to be compatible.

> 
> in the DFZ today are many competitors and thin margins.  for a "leak" to be
> successful, one provider has to want to emit a ULA-G route, and virtually all
> other providers have to be willing to accept it.  this is so unlikely that i
> can't imagine it.  it's not equivilent to the RFC1918 or non-BGP38 emissions
> problems, since every "leak" in this case means a competitor signs recurring
> revenue for a customer who was in play.  "that is sooooo not going to happen."

I have to say that sounds convincing. I suppose there will be
exceptions, but not enough to matter. (An exception is where BigBadCorporation
insists on being accessible only via its junk /48, but every customer
of every ISP wants to reach www.BigBadCorporation.com. Then the incentive
exists to route that /48.)

> 
>>>> We need to encourage the former and discourage the latter (as far as
>>>> seeing them in BGP is concerned).
> 
>>> if you mean by "BGP", the DFZ, then i'd agree with this statement in
>>> isolation from the one that came before it.
> 
>> Yes, I mean the DFZ - as above, I fully understand that there are already
>> vast numbers of private routes.
> 
> then we really do agree that when it comes to the DFZ, aggregation is a MUST.
> and our area of disagreement is simply whether deaggregated ULA-G will enter
> the DFZ.  i have several times shown why i think that can't happen.  most BGP
> operators are looking for any excuse to filter inbound routes, especially TE
> routes whose only purpose is to improve the efficiency and service quality of
> competitors.  an RFC that strongly recommends that FC00::/7 be filtered will
> be an excuse that most of these operators will be thankful for (hopefully
> that could mean "beer as in free").

Ack, as already stated in RFC 4193 section 4.1 para 3.

> 
>>> ... the tier-1 providers ... can afford 2-megaroute forwarding machinery,
>>> they compete aggressively for end-sites against both other tier-1's and
>>> all of the regional or value-add or low-cost tier-2's, and they really
>>> like the PA concept because the renumbering penality gives them a form of
>>> lock-in that even microsoft and apple can only dream about.
>> As an aside, that's why the normal model in IPv6 is for a user site to
>> run several PA prefixes simultaneously, and that's why we designed shim6.
> 
> on that aside, when i connect up my end host to a LAN that has multiple router
> advertisements, it selects exactly one as my default route.  there's no LCR as
> in the telephony world.  there's no intent to import the entire routing table
> into every host -- the router advertisements i don't select are backups not
> competitors.  the shim6 idea makes it more interesting -- how's that working
> out in the field?  any significant deployment experiences to report?  (i'm
> not just still bitter about the A6/DNAME debacle -- i really want to know.)

No. It's really too soon. The shim6 documents are in WG Last Call right now.

> 
>>> if the tier-1's decide to exchange ULA-C routes with each other, then the
>>> rest of the internet has to do likewise.  and if some really large cash
>>> cow of a customer puts out an RFP to tier-1 saying "we'll buy bandwidth
>>> from whoever will route our ULA-C into the internet core" then it'll be
>>> very interesting.  is this your proposed "pressure to stick" comes from?
>>> because i can think of a dozen reasons why it can't happen, all based on
>>> business strategy and self-interests of every single party involved in
>>> that money chain.
>> I hope you're right. My argument against structured ULA prefixes is only to
>> make it less likely to happen.
> 
> the benefit of ULA-G away from the DFZ is so much greater than the risk of
> ULA-G to the DFZ that i can't even consider them simultaneously long enough
> to let them compete.  from what you're saying, i don't know if you can either.

Agree

> 
>>>> What's your estimate of the total number of ULA-C prefixes needed?
>>> approximately one per family, worldwide, counting only the population who
>>> has electric power.  much much higher than the 2-megaroute level, or the
>>> number of domain names registered in .COM and .DE (the two largest TLDs).
>> I don't get that.  Customers need routeable prefixes.  Why do you need a
>> ULA-C prefix for a customer?
> 
> the idea of an internet made up only of customers was never part of the early
> vision as it's been told to me.  every device needs a unique identifier for
> any number of reasons.  if the DFZ is intolerant of these identifiers, then
> they'll show up in other ways, like non-DFZ routing, 1:1 NATv6, ad-hoc IPSEC
> tunnel innards, software key/serial numbers, and things we've not imagined.
> 
> the DFZ is one way to internet.  only one way.  and it's not the only reason
> one might need a registered unique addresses.

Here we do get into the ID/Loc split discussion that's going on over
in RAM and RRG. *If* that concludes that
  a) a split is needed
  b) the IDs should be in IPv6 address format
  c) they don't need to be cryptographically generated
  and d) they do need to be registered and DNS-able
then ULA-G would clearly be a candidate, and ULA-C wouldn't.

     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 Jul 04 04:51: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 1I60aT-0003KO-5f; Wed, 04 Jul 2007 04:51:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I60aR-0003KG-BY
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:51:47 -0400
Received: from py-out-1112.google.com ([64.233.166.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I60aN-0000QV-2Y
	for ipv6@ietf.org; Wed, 04 Jul 2007 04:51:47 -0400
Received: by py-out-1112.google.com with SMTP id f31so2238980pyh
	for <ipv6@ietf.org>; Wed, 04 Jul 2007 01:51: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=GvTQo1EsyfKNR08DGsjsCMZ8o2N8aB/hEmTXnOt/wUZ2+NIWcctWB/mL/afIQd2gJoZXEVMxaMajoj5n94rWPE5z5rvYk0OX7rQQDt07hr27gaJ/4qJkXHC/OrxVk9VNcZpH5kW/LlcjdQDWKhRCo/LTuzoWjNmQDhUX088+n/E=
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=NLEcPTlQa2GdE8PUM9ZHdpNJZikRrU8LZW2x485ITmgrZk1B6qt8oGL9y8qAGi2KtauTY7DQDim1gVA4I3V9bBLhRIO+aFaTtBdaRD6VNHG3Cbnes/xpJEs5YIzxcWi5guoy4uZgXo/lFAU08+TOs4o2JrUdTJaPG4O2GWVyEEo=
Received: by 10.65.141.18 with SMTP id t18mr12486123qbn.1183539102263;
	Wed, 04 Jul 2007 01:51:42 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id k10sm12145317nfh.2007.07.04.01.51.41
	(version=SSLv3 cipher=RC4-MD5); Wed, 04 Jul 2007 01:51:41 -0700 (PDT)
Message-ID: <468B5F9B.1090507@gmail.com>
Date: Wed, 04 Jul 2007 10:51:39 +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>	<4683712F.1010602@gmail.com>	<14556.1183042057@sa.vix.com>	<4684DB4A.2060703@gmail.com>	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>	<43704.1183395211@sa.vix.com>	<468A02EC.3080509@gmail.com>
	<468A1673.9040502@coders.net> <468A6338.1040108@gmail.com>
	<468A6891.8040300@internap.com>
In-Reply-To: <468A6891.8040300@internap.com>
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: 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-07-03 17:17, Scott Leibrand wrote:
> Brian E Carpenter wrote:
>> On 2007-07-03 11:27, Perry Lorier wrote:
>>>
>>>> And actually that is where we seem to be at odds. I fear that ULA-G 
>>>> will leak.
>>>> That's all. 
>>> So I might be a bit naive here, but why is this a problem?  ISP's 
>>> that are worried that they're routers can't deal with ULA addresses 
>>> in their DFZ will filter all ULA addresses.  ISP's that want ULA's in 
>>> their DFZ will make sure they dimension their routers such that they 
>>> can deal  with it.  Other ISP's will find some kind of middle ground 
>>> where they have some ULA prefixes,The DFZ is certainly not the same 
>>> everywhere on the Internet, by making ULA's easily filterable it 
>>> gives operators a place to start if they want to filter.
>>
>> Of course. But by leak, as I think was clear in later mail, I meant leak
>> deliberately under economic pressure. Accidental leakage would be
>> statistically insignificant, I assume, and easily filtered out as you
>> say.
> 
> Brian,
> 
> Can you outline the economic pressures that you believe would lead to a 
> ULA-C/ULA-G being accepted by more the majority of tier1ish transit 
> providers in the DFZ?  Like Paul, I'm inclined to believe the 
> countervailing economic pressures would be much stronger, and that we 
> will see very few, if any, ULA routes crossing the magic threshold of 
> global routability.  I would love to hear and possibly debate the 
> counterarguments.

See what I just wrote to Paul. I agree that statistically, the vast
majority of ULA-* prefixes are exempt from my concern. And I guess
a little leakage wouldn't 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 Wed Jul 04 11: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 1I66ck-0002GO-CB; Wed, 04 Jul 2007 11:18:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I66ci-0002Fs-5s
	for ipv6@ietf.org; Wed, 04 Jul 2007 11:18:32 -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 1I66cb-0001JG-Kz
	for ipv6@ietf.org; Wed, 04 Jul 2007 11:18:32 -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 1I66cZ-0001hY-8b; Wed, 04 Jul 2007 11:18:23 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Wed, 4 Jul 2007 11:18:23 -0400 (EDT)
Message-ID: <60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com>
In-Reply-To: <35308.1183515832@sa.vix.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
	<468ACF81.1080508@internap.com> <35308.1183515832@sa.vix.com>
Date: Wed, 4 Jul 2007 11:18:23 -0400 (EDT)
From: briand@ca.afilias.info
To: "Paul Vixie" <paul@vix.com>
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: d8ae4fd88fcaf47c1a71c804d04f413d
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

>> > With the current draft, that is correct.  With Paul's proposed changes
>> of
>> > 27 Jun, they definitely aggregate at the LIR and RIR levels, making it
>> > much harder to defend the position that they won't end up in the DFZ.
>
> the aggregation present in that version was unintentional.  if you look at
> the actual <http://sa.vix.com/~vixie/ula-global.txt> you'll see that it
> recommends that allocations be deliberately nonaggregatable.
>
>> I'm not quite following your logic here.  If ARIN allocates ULA-G space
>> from a distinct netblock, how does that make it any harder for transit
>> providers to filter routes from fc00::/7, reduce their incentive to do
>> so,
>> or create an incentive not to?
>
> my concern about aggregation is that if someone receives 8 /48's that are
> aligned as a /45 then they could conceivably advertise it as a /45.  i
> hope
> that IANA will allocate nonaligned blocks, or perhaps give even numbers to
> one RIR and odd numbers to the next, and that the RIRs and LIRs will do
> likewise.

Aggregation - bane or boon? Depends on whether it's in the DFZ or not.

However, here are some observations, which might at some point be
paraphrased by someone, along with elements of other postings by me
and lots of other smart folks, into a document to serve as an IPv6
"primer" for both new participants in the v6 world, and old-timers...

The notion of "default" is a bit of a problem, when you have both the
DFZ "universe" and the ULA-* multiverse (which is what ULA's are).

Each group of connected ULA "sites", is its own little internet.
Or intranet, or extranet, depending on what floats your boat.
There can, and will, be zillions of these, including overlapping
domains which individual ULA sites are members of.

Fundamentally, the DFZ doesn't care what happens outside of the DFZ.
And as long as the tech works everywhere, to achieve the desired goals,
that should be enough.

The thing we need to be concerned about is not only route leakage, but
packet leakage, especially if it has the ability to affect the core
infrastructure, e.g. DNS.

Here's what is interesting about both the ULA space(s) as proposed, and
the DFZ space. Each is allocated out of a block which is easily
identifiable, and not only that, but which can serve as a covering
aggregate (or a few covering aggregates, if need be).

And in each routing domain (DFZ or ULA multiverse), the concept of default
is generally restricted to members of that domain.

So, Best Common Practice should be to never install a true default route,
except when also installing covering aggregates for both spaces, the other
of which points to the bit bucket.

E.g. in the DFZ, have ULA covering aggregate pointing to null0.
E.g. in any ULA site or collection of sites, have DFZ covering aggregate
pointing to null0.
E.g. in both spaces, only install ::/0 if the corresponding example above
is also installed.

Also interesting is the fact that in ULA routing domains (of which there
can be zillions), scalability can be achieved on the routing side, when
the topology happens to lend itself accordingly, by having any "core" site
carry lots of ULA routes, and "edge" sites carry a ULA aggregate
pseudo-default which points towards the core site.

All of this, again, points towards my earlier observation. ULA-* should be
recommended only for use when there is no desire or need to directly
participate in the DFZ.

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 Wed Jul 04 15:17: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 1I6ALE-0006ix-TB; Wed, 04 Jul 2007 15:16:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6ALC-0006hK-BW
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:16:42 -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 1I6AL5-00039M-DB
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:16:42 -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 l64JGWDL021307;
	Wed, 4 Jul 2007 12:16:33 -0700
Message-ID: <029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,
	"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>	<4684DB4A.2060703@gmail.com><27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>
	<468B5534.5000701@gmail.com>
Date: Wed, 4 Jul 2007 14:10:31 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: 9182cfff02fae4f1b6e9349e01d62f32
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

Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> The reference to NATv6 confuses me. There's nothing about ULA-*
> that leads to NAT. Users will have PA (or PI for the lucky few) prefixes
> for global connectivity.  ULA-* is for local use (in the sense that RFC
> 4864 uses "local").

One of the arguments by the anti-ULA crowd is that if someone is unable to 
also get PI space, they will NAT their ULAs to PA space rather than 
assigning the PA space to hosts directly, because NAT is perceived as less 
hassle than renumbering every few months.  As a pro-ULA (just not the -C 
or -G variants) person, I have to admit I'd do that if I couldn't get PI 
space.  I'm anti-NAT, like most IETFers, but I'd still use it if it were the 
least-bad option.

There's also the usual "NAT makes me more secure" flamefest, but that 
applies to folks with PI space as well.  There's a lot of PIv4 space hidden 
behind NATs for "security" reasons...

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 Jul 04 15:21: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 1I6APV-0007jW-Rp; Wed, 04 Jul 2007 15:21:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6APU-0007j8-Vn
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:21:08 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6APQ-0005Ah-M5
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:21:08 -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 1I6ARw-00099K-6i; Wed, 04 Jul 2007 19:23:40 +0000
In-Reply-To: <468B5534.5000701@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>
	<27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com>
	<46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com>
	<13412.1183471599@sa.vix.com> <468B5534.5000701@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <CCCE7B97-0CAB-4E77-B9BC-4DC53D0E7CCE@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 4 Jul 2007 15:21:01 -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: 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


On 4-Jul-2007, at 04:07, Brian E Carpenter wrote:

> The reference to NATv6 confuses me. There's nothing about ULA-*  
> that leads to
> NAT.

There's nothing about RFC 1918 that leads to NAT, either. But it  
seems likely that the vast majority of RFC 1918-numbered devices in  
the world have a default route pointing at one.


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 Jul 04 15:48: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 1I6ApP-0001FN-35; Wed, 04 Jul 2007 15:47:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6ApN-0001Bj-HV
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:47:53 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6ApJ-00064W-11
	for ipv6@ietf.org; Wed, 04 Jul 2007 15:47:53 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85627087; Wed, 04 Jul 2007 15:47:47 -0400
Message-ID: <468BF956.1070104@internap.com>
Date: Wed, 04 Jul 2007 12:47:34 -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: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>	<46827A57.7030203@gmail.com>	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>	<468ACF81.1080508@internap.com>
	<35308.1183515832@sa.vix.com>
	<60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com>
In-Reply-To: <60144.74.122.168.81.1183562303.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: 14582b0692e7f70ce7111d04db3781c8
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

briand@ca.afilias.info wrote:
>>>> With the current draft, that is correct.  With Paul's proposed changes of 27 Jun, they definitely aggregate at the LIR and RIR levels, making it much harder to defend the position that they won't end up in the DFZ.
>>>>         
>> the aggregation present in that version was unintentional.  if you look at
>> the actual <http://sa.vix.com/~vixie/ula-global.txt> you'll see that it
>> recommends that allocations be deliberately nonaggregatable.
>>
>>     
>>> I'm not quite following your logic here.  If ARIN allocates ULA-G space
>>> from a distinct netblock, how does that make it any harder for transit
>>> providers to filter routes from fc00::/7, reduce their incentive to do
>>> so, or create an incentive not to?
>>>       
>> my concern about aggregation is that if someone receives 8 /48's that are
>> aligned as a /45 then they could conceivably advertise it as a /45.  i hope 
>> that IANA will allocate nonaligned blocks, or perhaps give even numbers to
>> one RIR and odd numbers to the next, and that the RIRs and LIRs will do
>> likewise.
>>     
>
> Aggregation - bane or boon? Depends on whether it's in the DFZ or not.
>   

Apparently I'm not using the same set of assumptions as most of the 
other folks here.  We all seem to agree that ULA prefixes should stay 
out of the DFZ, but I'm not quite sure why aggregatability of ULA space 
is a bad thing.  At least in my decision process, it doesn't much matter 
if the ULA routes I'm receiving are /48's or /45's: my decision to 
filter (if I'm doing Internet transit) or accept them (if I'm operating 
a metro network) will be the same.

> The notion of "default" is a bit of a problem, when you have both the
> DFZ "universe" and the ULA-* multiverse (which is what ULA's are).
>
> Each group of connected ULA "sites", is its own little internet.
> Or intranet, or extranet, depending on what floats your boat.
> There can, and will, be zillions of these, including overlapping
> domains which individual ULA sites are members of.
>
> Fundamentally, the DFZ doesn't care what happens outside of the DFZ.
> And as long as the tech works everywhere, to achieve the desired goals,
> that should be enough.
>   

Agreed.

> The thing we need to be concerned about is not only route leakage, but
> packet leakage, especially if it has the ability to affect the core
> infrastructure, e.g. DNS.
>
> Here's what is interesting about both the ULA space(s) as proposed, and
> the DFZ space. Each is allocated out of a block which is easily
> identifiable, and not only that, but which can serve as a covering
> aggregate (or a few covering aggregates, if need be).
>
> And in each routing domain (DFZ or ULA multiverse), the concept of default
> is generally restricted to members of that domain.
>
> So, Best Common Practice should be to never install a true default route,
> except when also installing covering aggregates for both spaces, the other
> of which points to the bit bucket.
>
> E.g. in the DFZ, have ULA covering aggregate pointing to null0.
> E.g. in any ULA site or collection of sites, have DFZ covering aggregate
> pointing to null0.
> E.g. in both spaces, only install ::/0 if the corresponding example above
> is also installed.
>   

Or, if a site is a member both of a ULA multiverse than the DFZ 
universe, it could contain both a 2000::/3 Internet default pointing to 
a transit provider, and a fc00::/7 ULA default pointing to your ULA 
"core", as you described below.

> Also interesting is the fact that in ULA routing domains (of which there
> can be zillions), scalability can be achieved on the routing side, when
> the topology happens to lend itself accordingly, by having any "core" site
> carry lots of ULA routes, and "edge" sites carry a ULA aggregate
> pseudo-default which points towards the core site.
>   

Agreed.

> All of this, again, points towards my earlier observation. ULA-* should be
> recommended only for use when there is no desire or need to directly
> participate in the DFZ.
>   

I would say it a little differently, that ULA addresses should be 
recommended for use only for connections to other ULA-addressed networks 
outside the DFZ.  A site using ULA addresses in this way could also use 
Internet addresses (PA or PI) in parallel, allowing hosts to select 
2000::/3 addresses when communicating across the DFZ, and fc00::/7 
addresses when communicating with other ULA 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 Wed Jul 04 21:24: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 1I6G4l-0007Ns-TK; Wed, 04 Jul 2007 21:24:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6G4k-0007NZ-DF
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:24:06 -0400
Received: from warlock.cs.waikato.ac.nz ([130.217.250.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6G4f-0007Nk-IS
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:24:06 -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 1I6G4J-0003JG-UN; Thu, 05 Jul 2007 13:23:44 +1200
Message-ID: <468C481A.1010405@coders.net>
Date: Thu, 05 Jul 2007 13:23:38 +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: Stephen Sprunk <stephen@sprunk.org>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
In-Reply-To: <029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Scanned-By: warlock.cs.waikato.ac.nz
	(33f35379c58f375c009acc091315063b918d317c)
X-Spam-Score: -3.9 (---)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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

Stephen Sprunk wrote:
> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>> The reference to NATv6 confuses me. There's nothing about ULA-*
>> that leads to NAT. Users will have PA (or PI for the lucky few) prefixes
>> for global connectivity.  ULA-* is for local use (in the sense that RFC
>> 4864 uses "local").
> 
> One of the arguments by the anti-ULA crowd is that if someone is unable 
> to also get PI space, they will NAT their ULAs to PA space rather than 
> assigning the PA space to hosts directly, because NAT is perceived as 
> less hassle than renumbering every few months.  

Except with v6 you can quite easily have multiple prefixes on an 
interface.  So you can have your ULA prefixes for your internal services 
(dns servers, smtp servers, whatever) and use your globally routable 
IPv6 addresses for IPv6 connectivity.

Things get a bit more annoying if you have internet facing services 
(public webservers, etc), but no more annoying than it was in the world 
of NAT.



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



From ipv6-bounces@ietf.org Wed Jul 04 21:53: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 1I6GXQ-0003YT-Na; Wed, 04 Jul 2007 21:53:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6GXN-0003YO-Tm
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:53:41 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6GXM-0005bZ-KX
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:53:41 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 9166911433
	for <ipv6@ietf.org>; Thu,  5 Jul 2007 01:53:39 +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, 05 Jul 2007 13:23:38 +1200."
	<468C481A.1010405@coders.net> 
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>
	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>
	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>
	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 05 Jul 2007 01:53:39 +0000
Message-ID: <60901.1183600419@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

> > One of the arguments by the anti-ULA crowd is that if someone is unable
> > to also get PI space, they will NAT their ULAs to PA space rather than
> > assigning the PA space to hosts directly, because NAT is perceived as
> > less hassle than renumbering every few months.

i don't understand.  yes they will do that because PA space is expensive in
that way.  but why is that bad and who is it bad for?

> Except with v6 you can quite easily have multiple prefixes on an interface.
> So you can have your ULA prefixes for your internal services (dns servers,
> smtp servers, whatever) and use your globally routable IPv6 addresses for
> IPv6 connectivity.

for client side connections, i wonder if we're going to see path assymmetry?
that is, if i have routes for 0::/0 and for fc00::/7, and i have interface
addresses in 2001::/16 and in fc00::/6, and i make outbound tcp connections,
is there any requirement in the IPv6 stack documentation that my tcp endpoint
use an address that's consistent with the routing table entry it follows?  in
times past, it took an actual separate interface to get most BSD stacks to
work this way.  (especially for UDP services like NFS, NTP, and DNS, for 
which this kind of symmetry is also important.)

if end systems having multiple addresses supernetted on the same LAN are able
to use a DFZ-verse source address when reaching the ULA-verse, or vice versa,
then this supernetting/multihoming capability buys us precisely nothing.  i'm
ignorant at this level of IPv6 spec detail, so, i'm asking.

> Things get a bit more annoying if you have internet facing services (public
> webservers, etc), but no more annoying than it was in the world of NAT.

it's actually much easier for the server side, since you can just answer with
source addresses consistent with whichever supernetted interface address your
NAT box contacted you, and your NAT box will flow-map you on the outbound
side.  outbound (usually this means "client-side") is the real trouble spot.

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



From ipv6-bounces@ietf.org Wed Jul 04 21:55: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 1I6GYv-0006Uk-Tt; Wed, 04 Jul 2007 21:55:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6GYu-0006Ue-Eu
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:55:16 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6GYu-0005w5-7C
	for ipv6@ietf.org; Wed, 04 Jul 2007 21:55:16 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id CDA6111437
	for <ipv6@ietf.org>; Thu,  5 Jul 2007 01:55:15 +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, 04 Jul 2007 10:03:08 +0200."
	<468B543C.6040203@gmail.com> 
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
	<468ACF81.1080508@internap.com> <35308.1183515832@sa.vix.com>
	<468B543C.6040203@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 05 Jul 2007 01:55:15 +0000
Message-ID: <60994.1183600515@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

[vixie]
> > my concern about aggregation is that if someone receives 8 /48's that are
> > aligned as a /45 then they could conceivably advertise it as a /45.  i
> > hope that IANA will allocate nonaligned blocks, or perhaps give even
> > numbers to one RIR and odd numbers to the next, and that the RIRs and LIRs
> > will do likewise.

[carpenter]
> There is a statistical sense in which ULA-G would be more *potentially*
> aggregatable than ULA or ULA-C. If ULA-G prefixes are allocated on an
> RIR/LIR basis, the chance that two logically adjacent prefixes happen to be
> used by customers of the same local ISP will be finite, whereas it's
> vanishingly small for ULA or ULA-C.

so perhaps we need to retain the randomness idea with instructions that IANA
and every RIR and LIR use it to ensure nonaggregatability?

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



From ipv6-bounces@ietf.org Wed Jul 04 22:20: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 1I6GxN-0001A3-Ly; Wed, 04 Jul 2007 22:20:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6GxL-00017l-OO
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:20:31 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6GxL-0002ym-9g
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:20:31 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id D846A1142F
	for <ipv6@ietf.org>; Thu,  5 Jul 2007 02:20: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 "Wed, 04 Jul 2007 10:49:06 +0200."
	<468B5F02.7000600@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> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<468A02EC.3080509@gmail.com> <20140.1183474407@sa.vix.com>
	<468B5F02.7000600@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 05 Jul 2007 02:20:30 +0000
Message-ID: <65666.1183602030@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
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

[vixie]
> > so, we share a supposition that the DFZ
> > is now a minority of "the Internet".

[carpenter]
> Or possibly that we don't know what
> "the Internet" is any more...

indeed, we don't.  one of the reasons i was dragging seth breidbart's
definition out and re-airing it here a few weeks back is that these
discussions are an indirect attack on the idea of a "largest closure".

that is, someone with access to a large set of private routes and also
to the "public internet" is part of a larger symmetric closure than
someone who is only connected to the "public internet".  i think the
closure has become nonsymmetric, and nobody noticed until this moment.

> > in the DFZ today are many competitors and thin margins.  for a "leak" to
> > be successful, one provider has to want to emit a ULA-G route, and
> > virtually all other providers have to be willing to accept it.  this is so
> > unlikely that i can't imagine it.  it's not equivilent to the RFC1918 or
> > non-BGP38 emissions problems, since every "leak" in this case means a
> > competitor signs recurring revenue for a customer who was in play.  "that
> > is sooooo not going to happen."
> 
> I have to say that sounds convincing.  I suppose there will be exceptions,
> but not enough to matter.  (An exception is where BigBadCorporation insists
> on being accessible only via its junk /48, but every customer of every ISP
> wants to reach www.BigBadCorporation.com.  Then the incentive exists to
> route that /48.)

the concept of "incentive" presupposes a value system and "incentee", and in
the DFZ, there is not a value system in common among enough potential
incentees to make what you're talking about feasible except through error
or accident.

[carpenter]
> >> As an aside, that's why the normal model in IPv6 is for a user site to
> >> run several PA prefixes simultaneously, and that's why we designed shim6.

> > ... the shim6 idea makes it more interesting -- how's that working out in
> > the field?  any significant deployment experiences to report?  (i'm not
> > just still bitter about the A6/DNAME debacle -- i really want to know.)

> No. It's really too soon. The shim6 documents are in WG Last Call right now.

so, it's been designed, but noone knows whether it will have any effect on
this problem space.  let's leave it out of the discussion, then.

> > the benefit of ULA-G away from the DFZ is so much greater than the risk of
> > ULA-G to the DFZ that i can't even consider them simultaneously long
> > enough to let them compete.  from what you're saying, i don't know if you
> > can either.
> 
> Agree

that's good to hear confirmed.

> > ...  every device needs a unique identifier for any number of reasons.  if
> > the DFZ is intolerant of these identifiers, then they'll show up in other
> > ways, like non-DFZ routing, 1:1 NATv6, ad-hoc IPSEC tunnel innards,
> > software key/serial numbers, and things we've not imagined.  the DFZ is
> > one way to internet.  only one way.  and it's not the only reason one
> > might need a registered unique addresses.
> 
> Here we do get into the ID/Loc split discussion that's going on over
> in RAM and RRG.  *If* that concludes that
>   a) a split is needed
>   b) the IDs should be in IPv6 address format
>   c) they don't need to be cryptographically generated
>   and d) they do need to be registered and DNS-able
> then ULA-G would clearly be a candidate, and ULA-C wouldn't.

code first, then spec.  let's allocate a couple ten million ULA-G prefixes and
see how the field develops it.  should be way more interesting than waiting to
see if this year's iteration of the ivory tower "do we need an id/loc split?"
debate ends any more remarkably than previous ones.

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



From ipv6-bounces@ietf.org Wed Jul 04 22:25: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 1I6H2M-0007SJ-2W; Wed, 04 Jul 2007 22:25:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6H2K-0007RG-Kn
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:25:40 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6H2K-0004KW-Cs
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:25:40 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id F171D1142F
	for <ipv6@ietf.org>; Thu,  5 Jul 2007 02:25:39 +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, 04 Jul 2007 11:18:23 -0400."
	<60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com> 
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>
	<46827A57.7030203@gmail.com>
	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>
	<468ACF81.1080508@internap.com> <35308.1183515832@sa.vix.com>
	<60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 05 Jul 2007 02:25:39 +0000
Message-ID: <65813.1183602339@sa.vix.com>
X-Spam-Score: -2.8 (--)
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

scott liebrand has already followed up on most of what i thought interesting
in brian dickson's latest post on this thread, so i'll limit myself to this:

> The thing we need to be concerned about is not only route leakage, but
> packet leakage, especially if it has the ability to affect the core
> infrastructure, e.g. DNS.

in RFC 1918 land, it's impossible for a root name server to know where the
junk-source queries are coming from, since 192.168.1.100 looks the same no
matter who leaks it.  in any ULA plan, "recourse" has to exist, such that
when someone sends you a DNS query you can't reply to because it's from a
ULA-verse that you're not part of, you can still look it up in WHOIS.  i've
got a metric buttload of leaked corporate identifiers on hand that i have
no way to embarrass anybody with because by definition i cannot know the
identity of the leaker.  let's ensure that ad-hoc networking doesn't mean
"recourse-free networking".  (therefore ULA-G's WHOIS requirements.)


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



From ipv6-bounces@ietf.org Wed Jul 04 22: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 1I6HSB-0000SR-9p; Wed, 04 Jul 2007 22:52:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6HS8-0000PL-VT
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:52:20 -0400
Received: from warlock.cs.waikato.ac.nz ([130.217.250.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6HS3-0005dM-CM
	for ipv6@ietf.org; Wed, 04 Jul 2007 22:52:20 -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 1I6HRu-0007YM-QV; Thu, 05 Jul 2007 14:52:12 +1200
Message-ID: <468C5CD4.2040203@coders.net>
Date: Thu, 05 Jul 2007 14:52:04 +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: 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>	<4684DB4A.2060703@gmail.com><27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>	<468C481A.1010405@coders.net>
	<60901.1183600419@sa.vix.com>
In-Reply-To: <60901.1183600419@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Scanned-By: warlock.cs.waikato.ac.nz
	(73fd766d356627f9396d375bb799b0ce5c388751)
X-Spam-Score: -3.8 (---)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
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

Paul Vixie wrote:
>>> One of the arguments by the anti-ULA crowd is that if someone is unable
>>> to also get PI space, they will NAT their ULAs to PA space rather than
>>> assigning the PA space to hosts directly, because NAT is perceived as
>>> less hassle than renumbering every few months.
> 
> i don't understand.  yes they will do that because PA space is expensive in
> that way.  but why is that bad and who is it bad for?
> 
>> Except with v6 you can quite easily have multiple prefixes on an interface.
>> So you can have your ULA prefixes for your internal services (dns servers,
>> smtp servers, whatever) and use your globally routable IPv6 addresses for
>> IPv6 connectivity.
> 
> for client side connections, i wonder if we're going to see path assymmetry?
> that is, if i have routes for 0::/0 and for fc00::/7, and i have interface
> addresses in 2001::/16 and in fc00::/6, and i make outbound tcp connections,
> is there any requirement in the IPv6 stack documentation that my tcp endpoint
> use an address that's consistent with the routing table entry it follows?  

Yeah.  RFC 3484 "Default address selection for Internet Protocol version 
6 (  6)".

Basically (massive oversimplifications here) it says:

* if connecting to an address, if you can use that as the source address 
use that.

* don't bother with addresses that aren't scoped enough.  (Don't use 
link local to connect to a globally scoped address, but you can use a 
globally scoped address to connect to a link local if you really had to).

* Avoid deprecated addresses (addresses which you've not seen Router 
Advertisements for in a while)

* Prefer home addresses when using mobile IP

* Prefer the outgoing interface IP over some other IP

* Prefer "matching label" (addresses of the same type, such as 6to4, 
teredo, whatever)

* Prefer public addresses over temporary addresses (or if an application 
asks the reverse)

* Do whatever you feel like if you can think of a reasonable rule to go 
here.

* Use the longest matching prefix.

Theres also a whole heap of stuff about how to choose a destination 
address given a set of them (eg from DNS) and how the system 
administrator should be able to influence these decisions.

 > in
> times past, it took an actual separate interface to get most BSD stacks to
> work this way.  (especially for UDP services like NFS, NTP, and DNS, for 
> which this kind of symmetry is also important.)

Yeah, part of IPv6 working well with multiple prefixes on an interface 
is better selection of source/destination addresses.

> if end systems having multiple addresses supernetted on the same LAN are able
> to use a DFZ-verse source address when reaching the ULA-verse, or vice versa,
> then this supernetting/multihoming capability buys us precisely nothing.  i'm
> ignorant at this level of IPv6 spec detail, so, i'm asking.

You can use the "least greater or equally scoped address".  So you will 
always prefer using a ULA address to talk to another ULA address.  If 
you only have globally routable and link local scoped address you can 
only use the globally routable address to speak to the ULA address (the 
link local source address isn't going to be useful).

When considering destination addresses I believe you can reply because 
you can assume it's reachable since you received a message.

All this magic is hidden inside the stub resolvers/kernel.  If you call 
getaddrinfo(3) you'll get back a sorted set of v6 (and v4 I guess) 
addresses that are likely to work, in preferential order so applications 
(in general) don't have to care.  I guess this encourages people to 
publish ula, globally scoped and even link local addresses in DNS since 
it will mean your clients will be able to figure out which of those 
address is the best for them to use.

>> Things get a bit more annoying if you have internet facing services (public
>> webservers, etc), but no more annoying than it was in the world of NAT.
> 
> it's actually much easier for the server side, since you can just answer with
> source addresses consistent with whichever supernetted interface address your
> NAT box contacted you, and your NAT box will flow-map you on the outbound
> side.  outbound (usually this means "client-side") is the real trouble spot.
> 

Hrm, I guess.  Updating DNS server glue is annoying (has anyone ever 
considered having DNS servers send signed UPDATE messages to 
register/deregister their glue?  It would certainly make things a lot 
easier for administrators.), but almost everything else should be easily 
done via updating DNS.


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



From ipv6-bounces@ietf.org Wed Jul 04 23:25: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 1I6HxY-0002s2-C6; Wed, 04 Jul 2007 23:24:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6HxX-0002ru-Pg
	for ipv6@ietf.org; Wed, 04 Jul 2007 23:24:47 -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 1I6HxT-0005Y7-E1
	for ipv6@ietf.org; Wed, 04 Jul 2007 23:24:47 -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 l653Ocj4022673;
	Wed, 4 Jul 2007 20:24:39 -0700
Message-ID: <046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Perry Lorier" <perry@coders.net>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
Date: Wed, 4 Jul 2007 22:11:04 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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

Thus spake "Perry Lorier" <perry@coders.net>
> Stephen Sprunk wrote:
>> One of the arguments by the anti-ULA crowd is that if someone is unable 
>> to also get PI space, they will NAT their ULAs to PA space rather than 
>> assigning the PA space to hosts directly, because NAT is perceived as 
>> less hassle than renumbering every few months.
>
> Except with v6 you can quite easily have multiple prefixes on an 
> interface.  So you can have your ULA prefixes for your internal services 
> (dns servers, smtp servers, whatever) and use your globally routable IPv6 
> addresses for IPv6 connectivity.

The fact that one _can_ assign both ULAs and PA space to hosts is 
irrelevant; I'm well aware of that.  NAT is perceived by IT folks as less 
hassle than renumbering hosts.  PA space implies frequent renumbering. 
Therefore, many (most?) IT depts who cannot get PI space will use NAT rather 
than assign PA space to hosts.

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 Jul 04 23:47: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 1I6IJr-00013X-DN; Wed, 04 Jul 2007 23:47:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6IJq-00013S-Dg
	for ipv6@ietf.org; Wed, 04 Jul 2007 23:47:50 -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 1I6IJk-0003zi-RQ
	for ipv6@ietf.org; Wed, 04 Jul 2007 23:47:50 -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 l653lh5c022708;
	Wed, 4 Jul 2007 20:47:44 -0700
Message-ID: <049b01c7beb7$31c623f0$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Paul Vixie" <paul@vix.com>, <ipv6@ietf.org>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail><46827A57.7030203@gmail.com><085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com><468ACF81.1080508@internap.com>
	<35308.1183515832@sa.vix.com><60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com>
	<65813.1183602339@sa.vix.com>
Date: Wed, 4 Jul 2007 22:26:21 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; 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: 798b2e660f1819ae38035ac1d8d5e3ab
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

Thus spake "Paul Vixie" <paul@vix.com>
> in RFC 1918 land, it's impossible for a root name server to know where the
> junk-source queries are coming from, since 192.168.1.100 looks the same no
> matter who leaks it.  in any ULA plan, "recourse" has to exist, such that
> when someone sends you a DNS query you can't reply to because it's from a
> ULA-verse that you're not part of, you can still look it up in WHOIS.

Wouldn't such packets be considered bogons and get blocked (either via 
specific filters for fc00::/7 or uRPF) at the edge of your network before 
the server even saw them?

Besides, ULA (RFC 4193) blocks _can't_ be registered because there is no 
central authority and no guaranteed uniqueness.  ULA-C/G are different 
beasts, and if passed should have WHOIS and RDNS servers.

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 Thu Jul 05 00:03: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 1I6IYW-0005Ip-Uv; Thu, 05 Jul 2007 00:03:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6IYW-0005Ii-2H
	for ipv6@ietf.org; Thu, 05 Jul 2007 00:03:00 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6IYU-0008KS-QN
	for ipv6@ietf.org; Thu, 05 Jul 2007 00:03:00 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id C66AD11431
	for <ipv6@ietf.org>; Thu,  5 Jul 2007 04:02:57 +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, 04 Jul 2007 22:26:21 EST."
	<049b01c7beb7$31c623f0$6701a8c0@atlanta.polycom.com> 
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail><46827A57.7030203@gmail.com><085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com><468ACF81.1080508@internap.com>
	<35308.1183515832@sa.vix.com><60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com>
	<65813.1183602339@sa.vix.com>
	<049b01c7beb7$31c623f0$6701a8c0@atlanta.polycom.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 05 Jul 2007 04:02:57 +0000
Message-ID: <81942.1183608177@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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

> Wouldn't such packets be considered bogons and get blocked (either via
> specific filters for fc00::/7 or uRPF) at the edge of your network before
> the server even saw them?

right up to the point where they fill one of my peering circuits, yes.
after that, i have to track them back to the source and stop them there.

> Besides, ULA (RFC 4193) blocks _can't_ be registered because there is no
> central authority and no guaranteed uniqueness.  ULA-C/G are different
> beasts, and if passed should have WHOIS and RDNS servers.

fortunately then, ULA hasn't caught on.  ULA-C or ULA-G could catch on.

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



From ipv6-bounces@ietf.org Thu Jul 05 01:16: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 1I6JhP-00052s-Gi; Thu, 05 Jul 2007 01:16:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6JhM-00052m-DB
	for ipv6@ietf.org; Thu, 05 Jul 2007 01:16:12 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6JhI-00064M-Tt
	for ipv6@ietf.org; Thu, 05 Jul 2007 01:16:12 -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 911F373021;
	Thu,  5 Jul 2007 14:16:07 +0900 (JST)
Date: Thu, 05 Jul 2007 14:15:56 +0900
Message-ID: <m1ejjnmnw3.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: <B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>
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

At Tue, 3 Jul 2007 10:56:32 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> In this regard, bullets 2 and 3 in Section 2 of our I-D show the issue
> hosts have when hosts incorrectly always add a directly connected route
> to the /64 prefix from an address assigned to an interface, even if the
> prefix is advertised as "not on link" or is not advertised at all. That
> incorrectly added route causes the host to try to use direct delivery
> (without sending traffic to the default router) and, therefore, use
> NS/NA to resolve addresses from the same prefix. 
> 
> We are prepared in this discussion that no host implementers will reply
> to our thread.

I already explained the BSD implementation correctly handles a prefix
advertised via an RA with the L bit being off.  Out of curiosity,
which host implementation are you specifically talking about?  You
have repeatedly stated something like "an implementer of a popular
IPv6 host [...] missed this behavior", but I don't think I've heard
which implementation it is.  Is there any reason for not being
specific?

					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 Jul 05 01:43: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 1I6K7f-00027M-5n; Thu, 05 Jul 2007 01:43:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6K7d-00027G-MJ
	for ipv6@ietf.org; Thu, 05 Jul 2007 01:43:21 -0400
Received: from warlock.cs.waikato.ac.nz ([130.217.250.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6K7Y-0003Q2-SJ
	for ipv6@ietf.org; Thu, 05 Jul 2007 01:43:21 -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 1I6K7P-0006FX-59; Thu, 05 Jul 2007 17:43:13 +1200
Message-ID: <468C84E9.10902@coders.net>
Date: Thu, 05 Jul 2007 17:43:05 +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: Stephen Sprunk <stephen@sprunk.org>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
In-Reply-To: <046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Scanned-By: warlock.cs.waikato.ac.nz
	(fa5e608370d7119a1a700c67c1df2a4fbeeb56d9)
X-Spam-Score: -3.4 (---)
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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

Stephen Sprunk wrote:
> Thus spake "Perry Lorier" <perry@coders.net>
>> Stephen Sprunk wrote:
>>> One of the arguments by the anti-ULA crowd is that if someone is 
>>> unable to also get PI space, they will NAT their ULAs to PA space 
>>> rather than assigning the PA space to hosts directly, because NAT is 
>>> perceived as less hassle than renumbering every few months.
>>
>> Except with v6 you can quite easily have multiple prefixes on an 
>> interface.  So you can have your ULA prefixes for your internal 
>> services (dns servers, smtp servers, whatever) and use your globally 
>> routable IPv6 addresses for IPv6 connectivity.
> 
> The fact that one _can_ assign both ULAs and PA space to hosts is 
> irrelevant; I'm well aware of that.  NAT is perceived by IT folks as 
> less hassle than renumbering hosts.  PA space implies frequent 
> renumbering. Therefore, many (most?) IT depts who cannot get PI space 
> will use NAT rather than assign PA space to hosts.

However in IPv4 you can have PA xor PI space, you can't have both at the 
same time.  With IPv6 you can have PA+"private PI" (aka ULA) space.

My router can dish out some different PA space every time my dialup 
modem reconnects if my internal network is all using ULA internally. 
I'm not really sure that situation really is "renumbering" in the 
traditional sense even tho I'm not using NAT nor am I using public PI space.

Changing your PI space every time your modem dials up is perhaps a bit 
extreme, but it shows that you can ""renumber"" your network rapidly in 
some situations.  Problems occur for externally facing services, but 
that doesn't seem insurmountable for an organisation that's likely to 
only change PI space at most every year or so.

If your choices are PI vs PA then yeah NAT does look very attractive, 
but if you can have PA and "private"-PI (aka ULA) then things look a lot 
less blurred (IMHO).

Not having ULA space won't stop people from randomly picking address 
ranges to use.  Not having NAT boxes easily available for v6 however 
might make people rethink their assumptions.

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



From ipv6-bounces@ietf.org Thu Jul 05 02:36: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 1I6Kwo-0005BN-Di; Thu, 05 Jul 2007 02:36:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Kwl-0004zy-RR
	for ipv6@ietf.org; Thu, 05 Jul 2007 02:36:11 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6KtZ-00023a-Ov
	for ipv6@ietf.org; Thu, 05 Jul 2007 02:32:59 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[192.168.1.103])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85642856; Thu, 05 Jul 2007 02:32:52 -0400
Message-ID: <468C9086.1040307@internap.com>
Date: Wed, 04 Jul 2007 23:32:38 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Perry Lorier <perry@coders.net>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>	<468C481A.1010405@coders.net>	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
	<468C84E9.10902@coders.net>
In-Reply-To: <468C84E9.10902@coders.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.0 (++)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: Stephen Sprunk <stephen@sprunk.org>, 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

Perry Lorier wrote:
> Stephen Sprunk wrote:
>> Thus spake "Perry Lorier" <perry@coders.net>
>>> Stephen Sprunk wrote:
>>>> One of the arguments by the anti-ULA crowd is that if someone is 
>>>> unable to also get PI space, they will NAT their ULAs to PA space 
>>>> rather than assigning the PA space to hosts directly, because NAT 
>>>> is perceived as less hassle than renumbering every few months.
>>>
>>> Except with v6 you can quite easily have multiple prefixes on an 
>>> interface.  So you can have your ULA prefixes for your internal 
>>> services (dns servers, smtp servers, whatever) and use your globally 
>>> routable IPv6 addresses for IPv6 connectivity.
>>
>> The fact that one _can_ assign both ULAs and PA space to hosts is 
>> irrelevant; I'm well aware of that.  NAT is perceived by IT folks as 
>> less hassle than renumbering hosts.  PA space implies frequent 
>> renumbering. Therefore, many (most?) IT depts who cannot get PI space 
>> will use NAT rather than assign PA space to hosts.

Yes, many IT depts will probably do that.  IMO, that's fine.  The IT 
folks I know may not be fully versed in all the details of what NATs 
break, but they know they break some things, and they know how to gather 
enough information to make a decision about what's best for their 
business.  So IMO, if they think NATs are best for their situation, 
that's fine.  Often they don't want their users to have end-to-end 
connectivity, and while I would be most upset if my ISP made that 
decision for me, I can only really get upset about my employer doing it 
if it negatively impacts my productivity somehow.

>
> However in IPv4 you can have PA xor PI space, you can't have both at 
> the same time.  With IPv6 you can have PA+"private PI" (aka ULA) space.
>
> My router can dish out some different PA space every time my dialup 
> modem reconnects if my internal network is all using ULA internally. 
> I'm not really sure that situation really is "renumbering" in the 
> traditional sense even tho I'm not using NAT nor am I using public PI 
> space.
>
> Changing your PI space every time your modem dials up is perhaps a bit 
> extreme, but it shows that you can ""renumber"" your network rapidly 
> in some situations.  

The other possibility is that a heterogeneous corporation may decide to 
use ULA-G space internally, NAT it at the edge, and also assign PA space 
via DHCP or RA's wherever it's easy to do.  If they can give 80% of 
their users public IPs with only 20% of the effort, they can probably 
just NAT the other 20% and be fine.   As always, we have to just give 
people the tools and the documentation about how to use them, and then 
trust that they'll make a good decision for their particular situation.

-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 Jul 05 03:11: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 1I6LUg-0001Tx-MP; Thu, 05 Jul 2007 03:11:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6LUf-0001Tn-J2
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:11:13 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6LUb-0007lW-7u
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:11:13 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1072262uge
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 00:11: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=l2eFrfqdAZGQT0Z8wwrjgKSaAIgNWcJT19WdGA022rPC/ZjmY9/T8TNcEtg9P/PRLqdSU6zwlobvt3AlKzbL/kJOySyEvLYM+0BOIWXRgChzByyffLiQKdRgXJdKjR1Fv7xpe/EAAkiibViIJga1r+5/CZKyvC0ZaUN+nbfctzY=
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=mupWfI6PauNYY7Vd4db2Gs5xBt20XpAayF1X4ePGfVJeQTUEFmsdCJ+tr6lmfT9QFaiBEnGjEI4ZCZJ/61gMv9rThKW+W8bes5k66hYbJEVOwKM9gWXc3YcAibr9nUXHXmJSS/E0+BWiVWtqLTSLUXFr9VWVV48yug5J143TSRc=
Received: by 10.66.224.3 with SMTP id w3mr1754221ugg.1183619468540;
	Thu, 05 Jul 2007 00:11:08 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTPS id m1sm778884ugc.2007.07.05.00.11.06
	(version=SSLv3 cipher=RC4-MD5); Thu, 05 Jul 2007 00:11:07 -0700 (PDT)
Message-ID: <468C9987.8080007@gmail.com>
Date: Thu, 05 Jul 2007 09:11:03 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
In-Reply-To: <046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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-07-05 05:11, Stephen Sprunk wrote:
> Thus spake "Perry Lorier" <perry@coders.net>
>> Stephen Sprunk wrote:
>>> One of the arguments by the anti-ULA crowd is that if someone is 
>>> unable to also get PI space, they will NAT their ULAs to PA space 
>>> rather than assigning the PA space to hosts directly, because NAT is 
>>> perceived as less hassle than renumbering every few months.
>>
>> Except with v6 you can quite easily have multiple prefixes on an 
>> interface.  So you can have your ULA prefixes for your internal 
>> services (dns servers, smtp servers, whatever) and use your globally 
>> routable IPv6 addresses for IPv6 connectivity.
> 
> The fact that one _can_ assign both ULAs and PA space to hosts is 
> irrelevant; I'm well aware of that.  NAT is perceived by IT folks as 
> less hassle than renumbering hosts.  PA space implies frequent 
> renumbering. Therefore, many (most?) IT depts who cannot get PI space 
> will use NAT rather than assign PA space to hosts.

I don't see why. Most IT managers are painfully aware of the hassle
caused by NAT (e.g. when setting up their VoIP infrastructure
or their remote-acess VPN infrastructure). Hopefully they will read
RFC 4192 and 4864 and apply appropriate pressure to their suppliers.

     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 Jul 05 03:12: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 1I6LVf-0004mr-LQ; Thu, 05 Jul 2007 03:12:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6LVd-0004ml-RC
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:12:13 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6LVZ-0007rg-I1
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:12:13 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1072484uge
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 00:12: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=WXwTgf9zXJneXwPZnSO+wTdjxGUNmFARJuamrn4pqE2C/cyzYh/5d6kOqJwpLqPs4fI+8Ow28yaEh+KzfqJ9hDnmpYzIO1W7C7x1O2CfqBp3c/Vqd5o9jePnaYIZ1wTyDbmJffo7qqDdkhuQsM5poayTvumCf0wKPhVDIFshBR0=
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=PgOMrg8xs0PYmZwIgBl/ijEGOpYsRdyKojzAimJG108XRXluvKrX9uATnhjwT8VxeE1Srfg9Fh8HUMjsg7uAC9Ji9E371Z4hb1dSme76W+YtTTQVpcblSdVgPdyHScsIkvxvdfqiGNUNzeTXgH5m6cgyH+pkewVFFultKesV548=
Received: by 10.67.29.7 with SMTP id g7mr1752562ugj.1183619528976;
	Thu, 05 Jul 2007 00:12:08 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTPS id x26sm779803ugc.2007.07.05.00.12.07
	(version=SSLv3 cipher=RC4-MD5); Thu, 05 Jul 2007 00:12:08 -0700 (PDT)
Message-ID: <468C99C8.5080205@gmail.com>
Date: Thu, 05 Jul 2007 09:12: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: Paul Vixie <paul@vix.com>
References: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail><46827A57.7030203@gmail.com><085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com><468ACF81.1080508@internap.com>	<35308.1183515832@sa.vix.com><60144.74.122.168.81.1183562303.squirrel@look.libertyrms.com>	<65813.1183602339@sa.vix.com>	<049b01c7beb7$31c623f0$6701a8c0@atlanta.polycom.com>
	<81942.1183608177@sa.vix.com>
In-Reply-To: <81942.1183608177@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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


> fortunately then, ULA hasn't caught on.  

Actually, we have no way of knowing that, which is
a feature, not a bug.

    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 Jul 05 03:23: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 1I6LgT-0002Gb-HX; Thu, 05 Jul 2007 03:23:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6LgS-000295-2x
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:23:24 -0400
Received: from mu-out-0910.google.com ([209.85.134.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6LgO-0001gu-OV
	for ipv6@ietf.org; Thu, 05 Jul 2007 03:23:24 -0400
Received: by mu-out-0910.google.com with SMTP id w8so2867673mue
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 00:23:19 -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=bRsVktlaKhAwtc8rHeKzZSL43+ObxEOh0lPPmPTZKDyA7R00dX7QY2DvJrN5DOASVemLiRg+zCvnw9QShyrOAEagBZUjOk/fhd/JgJ360cTa/nfv+lg9LpqoOrXRmqO2haLtr8zWB3CqY6G0mlzyWrqPpxtijZhRSGpdxv3/2Pg=
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=rbMbRiwJkTxIU6siAaE2nCvDWwsMeX6V37CzbTtf5XTJNqMugCOIDQcSV9FgnWzTGvAOzPPWQNuH49akRGQ0LEpUgcJPup9oufI477HpGogmdMJVyBJVJaOUXulOsoMRdfhwY4G5igygAN2246TDnTgVnEm+IUfpWP9UzQXB4mY=
Received: by 10.82.175.17 with SMTP id x17mr19565586bue.1183620199370;
	Thu, 05 Jul 2007 00:23:19 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id h1sm10383452nfh.2007.07.05.00.23.17
	(version=SSLv3 cipher=RC4-MD5); Thu, 05 Jul 2007 00:23:18 -0700 (PDT)
Message-ID: <468C9C65.1080106@gmail.com>
Date: Thu, 05 Jul 2007 09:23:17 +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: <70DE64CEFD6E9A4EB7FAF3A0631410667070AA@mail>	<46827A57.7030203@gmail.com>	<085101c7bdb8$e71bcf20$543816ac@atlanta.polycom.com>	<468ACF81.1080508@internap.com>
	<35308.1183515832@sa.vix.com>	<468B543C.6040203@gmail.com>
	<60994.1183600515@sa.vix.com>
In-Reply-To: <60994.1183600515@sa.vix.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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-07-05 03:55, Paul Vixie wrote:
> [vixie]
>>> my concern about aggregation is that if someone receives 8 /48's that are
>>> aligned as a /45 then they could conceivably advertise it as a /45.  i
>>> hope that IANA will allocate nonaligned blocks, or perhaps give even
>>> numbers to one RIR and odd numbers to the next, and that the RIRs and LIRs
>>> will do likewise.
> 
> [carpenter]
>> There is a statistical sense in which ULA-G would be more *potentially*
>> aggregatable than ULA or ULA-C. If ULA-G prefixes are allocated on an
>> RIR/LIR basis, the chance that two logically adjacent prefixes happen to be
>> used by customers of the same local ISP will be finite, whereas it's
>> vanishingly small for ULA or ULA-C.
> 
> so perhaps we need to retain the randomness idea with instructions that IANA
> and every RIR and LIR use it to ensure nonaggregatability?

When I think about it, this isn't such a big deal. If it's convenient
for an ISP to aggregate a few ULA-G prefixes on a local basis, for routing
within the ISP's domain, so what? The ULA prefix should still be filtered
at transit points.

I'm still not convinced about ULA-C/G but if this was an IESG ballot,
I'd be an 'abstain' at this point.

     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 Jul 05 10:26: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 1I6SH6-0005D6-JN; Thu, 05 Jul 2007 10:25:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6SH5-0005CD-Tr
	for ipv6@ietf.org; Thu, 05 Jul 2007 10:25:39 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6SGm-0004tF-Ow
	for ipv6@ietf.org; Thu, 05 Jul 2007 10:25:39 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 10:25:20 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOubjEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,503,1175486400"; 
	d="scan'208"; a="64397322:sNHT41443700"
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 l65EPKna024770; 
	Thu, 5 Jul 2007 10:25:20 -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 l65EP66m015195; 
	Thu, 5 Jul 2007 14:25:20 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, 5 Jul 2007 10:25:06 -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, 5 Jul 2007 10:24:21 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace+E8JNqVKZwKLbQRyGJ10t+F+1IAA+5Tog
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>, <ipv6@ietf.org>
X-OriginalArrivalTime: 05 Jul 2007 14:25:06.0089 (UTC)
	FILETIME=[488C6190:01C7BF10]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2269; t=1183645520;
	x=1184509520; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=20<ipv6@ietf.org>;
	bh=EfuDn+PpdZKN0v9dF47m9/iV7POZboFrTaS78lk65dY=;
	b=eCdxnPmxHg2n08imG2lySAh3UT7o66vvy2aGecxEPzEichBcUTSd79Aa/im0s63LrO0orTnS
	Xa+OwPCeYu4Skh3DRuN0bQQruSv9QaA/rrDAXa7sVW/F323vMVb8cziU;
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: 52f7a77164458f8c7b36b66787c853da
Cc: 
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

If the word solicitation is replaced by advertisement in section 5.4.4,
we are fine. I don't like the too much wordiness of section 5.4.4. So I
have prepared a paragraph for this section having made the text shorter
and replaced the  solicitation by an advertisement. This is what the new
para for section 5.4.4 of 2461bis -08 should look like:

-----------------
On receipt of a valid Neighbor Advertisement message on an interface,
node behavior depends upon whether the target address is tentative or
not. If the target address is not tentative, the advertisement is
processed as described in [I-D.ietf-ipv6-2461bis]. If the target address
is tentative, the tentative address is not unique.
-----------------

As for logging of an error message or not, see section 5.4.5 of 2461bis.
This section clearly says if a tentative address that is determined to
be a duplicate as described above MUST NOT be assigned to an interface
and then node SHOULD log a system management error.

Thanks.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Wednesday, July 04, 2007 4:16 AM
To: ipv6@ietf.org
Subject: Revisit: one remaining corner case in DAD

I'm now completing 2462bis (which is now in the AUTH48 state) addressing
post IESG-approval issues.  The remaining issues are basically trivial,
but I found one unresolved issue in the ML archive that may be
substantial.

I've read the issue description again, and would like to propose the
simplest solution:

   A. simply discard the packet (like BSD/KAME)

Namely I propose to change the text from

   [...] If
   the target address is assigned to the receiving interface, the
   solicitation is processed as described in [RFC4861].

to

   [...] If
   the target address is assigned to the receiving interface, the
   advertisement SHOULD be silently discarded.

In fact, I think this should be compatible with the first paragraph of
Section 7.2.5 of RFC2461 (and coming RFC4861).

Please let me know ASAP if anyone has an objection to this proposal.

Thanks,

					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 Jul 05 10:48: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 1I6Sd1-00040R-EN; Thu, 05 Jul 2007 10:48:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Scx-0003xU-Ua
	for ipv6@ietf.org; Thu, 05 Jul 2007 10:48:16 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6Sct-00022G-D2
	for ipv6@ietf.org; Thu, 05 Jul 2007 10:48:15 -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 CEFA47301E;
	Thu,  5 Jul 2007 23:48:09 +0900 (JST)
Date: Thu, 05 Jul 2007 23:48:05 +0900
Message-ID: <m2k5te7vq2.wl%jinmei@wide.ad.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@wide.ad.jp>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@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: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 5 Jul 2007 10:24:21 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> If the word solicitation is replaced by advertisement in section 5.4.4,
> we are fine. I don't like the too much wordiness of section 5.4.4. So I
> have prepared a paragraph for this section having made the text shorter
> and replaced the  solicitation by an advertisement. This is what the new
> para for section 5.4.4 of 2461bis -08 should look like:
> 
> -----------------
> On receipt of a valid Neighbor Advertisement message on an interface,
> node behavior depends upon whether the target address is tentative or
> not. If the target address is not tentative, the advertisement is
> processed as described in [I-D.ietf-ipv6-2461bis]. If the target address
> is tentative, the tentative address is not unique.
> -----------------

Which part of [I-D.ietf-ipv6-2461bis] (which will be RFC4861) do you
think describes the processing?  Although I mentioned the first para
of Section 7.2.5 (copied below), I don't think we can simply apply it
to this case.  As I read it, this paragraph describes the case where

- host A somehow receives an NA with the target address of X
- host A does not have a neighbor cache for address X
- address X is (possibly) assigned to some other nodes, and
- host A is not performing DAD on X as its own tentative address or it
  has not assigned X on its interface

The most likely case in this scenario is that host A receives an
unsolicited NA with a target address that host A is not interested in
(and thus it doesn't have a neighbor cache for it).

On the other hand, the situation described in Section 5.4.4 of 2462bis
is:

- host A somehow receives an NA with the target address of X
- host A has assigned address X (which is not tentative) to the
  receiving interface

in this case most (if not all) implementations of the receiving host
do not have a "neighbor cache" for X (since it's one of its own
addresses), so we could superficially apply section 7.2.5 of
2461/2461bis.  But I don't think it's always obvious for
implementors.  I usually hate a redundant description, but in this
case I believe we should be specific in 2462bis.

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

(Section 7.2.5, first para of RFC2461 for reference)
   When a valid Neighbor Advertisement is received (either solicited or
   unsolicited), the Neighbor Cache is searched for the target's entry.
   If no entry exists, the advertisement SHOULD be silently discarded.
   There is no need to create an entry if none exists, since the
   recipient has apparently not initiated any communication with the
   target.

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



From ipv6-bounces@ietf.org Thu Jul 05 11:07: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 1I6SvT-0002IQ-3B; Thu, 05 Jul 2007 11:07:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6SvR-0002Ho-Cm
	for ipv6@ietf.org; Thu, 05 Jul 2007 11:07:21 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6SvM-0005BW-T0
	for ipv6@ietf.org; Thu, 05 Jul 2007 11:07:21 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 11:07:07 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAGumjEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,503,1175486400"; 
	d="scan'208"; a="64401766:sNHT221234496"
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 l65F77oB027154; 
	Thu, 5 Jul 2007 11:07:07 -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 l65F73s8021059; 
	Thu, 5 Jul 2007 15:07:07 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, 5 Jul 2007 11:06: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: Thu, 5 Jul 2007 11:06:26 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2k5te7vq2.wl%jinmei@wide.ad.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/E5HRrx7q+561RPCCxZfC+Fd5vgAAFfvQ
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@wide.ad.jp>
X-OriginalArrivalTime: 05 Jul 2007 15:06:57.0657 (UTC)
	FILETIME=[218F3E90:01C7BF16]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4246; t=1183648027;
	x=1184512027; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@wide.ad.jp>;
	bh=+uGM/LEkVXLMzPFsVxbfovzAHzdcWpVfILw0sCrZFsM=;
	b=R9UqEjLlAsMZuwK9VC/X0tqVx4+LSzrzP/seQC4gH2O3BCqCrlYTvWLNJx3d+puFiVjb0c7g
	6yuF0NAgjGyd+lzzG2oulIH5lC33YiRD5cJopasZfSOVoWo3YxKyN4Qy;
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: 34d35111647d654d033d58d318c0d21a
Cc: ipv6@ietf.org
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

Yes, even I am referring to section 7.2.5 of 2461bis to go to after a
node has made the following checks on receiving an NA:

The receiving interface searches if target address is any address in the
list of addresses for the interface. If yes, then the interface can
check if the target address is tentative. If target address is
tentative, the address is not unique, then log a system error message as
per section 5.4.5 2462bis, first para. Further, it is not possible in an
IPv6 network that a node will receive an NA with target address that is
assigned to the receiving interface and not tentative.

Having taken care of an NA target address that happens to be any address
assigned to the receiving interface, now we are left with only a target
address that is in ND cache of the receiving interface. Once a tentative
address has been taken care of, the processing of NA goes into checking
if target address lies in ND cache of the receiving interface and hence
section 7.2.5 of 2461bis applies - this rule takes care of an
unsolicited NA sent by a neighbor to the interface. Such unsolicited
NA's are used by nodes to update new ND information to neighbors.

Thanks.

Hemant


-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@wide.ad.jp]=20
Sent: Thursday, July 05, 2007 10:48 AM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

At Thu, 5 Jul 2007 10:24:21 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> If the word solicitation is replaced by advertisement in section=20
> 5.4.4, we are fine. I don't like the too much wordiness of section=20
> 5.4.4. So I have prepared a paragraph for this section having made the

> text shorter and replaced the  solicitation by an advertisement. This=20
> is what the new para for section 5.4.4 of 2461bis -08 should look
like:
>=20
> -----------------
> On receipt of a valid Neighbor Advertisement message on an interface,=20
> node behavior depends upon whether the target address is tentative or=20
> not. If the target address is not tentative, the advertisement is=20
> processed as described in [I-D.ietf-ipv6-2461bis]. If the target=20
> address is tentative, the tentative address is not unique.
> -----------------

Which part of [I-D.ietf-ipv6-2461bis] (which will be RFC4861) do you
think describes the processing?  Although I mentioned the first para of
Section 7.2.5 (copied below), I don't think we can simply apply it to
this case.  As I read it, this paragraph describes the case where

- host A somehow receives an NA with the target address of X
- host A does not have a neighbor cache for address X
- address X is (possibly) assigned to some other nodes, and
- host A is not performing DAD on X as its own tentative address or it
  has not assigned X on its interface

The most likely case in this scenario is that host A receives an
unsolicited NA with a target address that host A is not interested in
(and thus it doesn't have a neighbor cache for it).

On the other hand, the situation described in Section 5.4.4 of 2462bis
is:

- host A somehow receives an NA with the target address of X
- host A has assigned address X (which is not tentative) to the
  receiving interface

in this case most (if not all) implementations of the receiving host do
not have a "neighbor cache" for X (since it's one of its own addresses),
so we could superficially apply section 7.2.5 of 2461/2461bis.  But I
don't think it's always obvious for implementors.  I usually hate a
redundant description, but in this case I believe we should be specific
in 2462bis.

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

(Section 7.2.5, first para of RFC2461 for reference)
   When a valid Neighbor Advertisement is received (either solicited or
   unsolicited), the Neighbor Cache is searched for the target's entry.
   If no entry exists, the advertisement SHOULD be silently discarded.
   There is no need to create an entry if none exists, since the
   recipient has apparently not initiated any communication with the
   target.

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



From ipv6-bounces@ietf.org Thu Jul 05 12:06: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 1I6TqR-0007Yc-Af; Thu, 05 Jul 2007 12:06:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6TqQ-0007XG-6J
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:06:14 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6TpP-0002Lj-MI
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:06:14 -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 9D19D73021;
	Fri,  6 Jul 2007 01:05:10 +0900 (JST)
Date: Fri, 06 Jul 2007 01:05:06 +0900
Message-ID: <m2hcoi7s5p.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: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@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: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 5 Jul 2007 11:06:26 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Having taken care of an NA target address that happens to be any address
> assigned to the receiving interface, now we are left with only a target
> address that is in ND cache of the receiving interface. Once a tentative
> address has been taken care of, the processing of NA goes into checking
> if target address lies in ND cache of the receiving interface and hence
> section 7.2.5 of 2461bis applies - this rule takes care of an
> unsolicited NA sent by a neighbor to the interface. Such unsolicited
> NA's are used by nodes to update new ND information to neighbors.

My point is that it's not so obvious (at least to me) by simply saying
"If the target address is not tentative, the advertisement is
processed as described in [I-D.ietf-ipv6-2461bis]".  Hence my proposed
text.  I'm not sure whether you agree with it or not, but I'm still
not convinced that referring to 2461bis is enough.  So, I still plan
to keep my proposed change unless I hear otherwise from others.

Thanks,

					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 Jul 05 12: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 1I6U8P-0005x0-AJ; Thu, 05 Jul 2007 12:24:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6U8N-0005wD-Nt
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:24:47 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6U8N-0001jz-Gp
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:24:47 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 05 Jul 2007 12:24:23 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAD+4jEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175486400"; 
	d="scan'208"; a="125286553:sNHT43426798"
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 l65GOM78015827; 
	Thu, 5 Jul 2007 12:24:22 -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 l65GOHsA011871; 
	Thu, 5 Jul 2007 16:24:22 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, 5 Jul 2007 12: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, 5 Jul 2007 12:23:24 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A1C2@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2hcoi7s5p.wl%jinmei@wide.ad.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/HlQlMVG5lvVwT6WsT3L8lDQzpAAAdwLw
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 05 Jul 2007 16:24:22.0422 (UTC)
	FILETIME=[F20E2360:01C7BF20]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1697; t=1183652663;
	x=1184516663; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=SrIxWLUuXqEOHh6jjGxMMOtZW+xTNT6c0tVG/VI5tu4=;
	b=SahNelJDbICGHw9L/wHwqLLjxRaCTWjMaTg9nk5XhwyZXd9hvRFsfhBuCeou2FMTxgqPrkI/
	4j0Xs6w5AexhPPYTQ+PcZXyIqPPbR8frjKukb8LRFAWfP+kOg4eC147R;
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: 4adaf050708fb13be3316a9eee889caa
Cc: ipv6@ietf.org
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

When you have the time, please do me a favor and email the complete
paragraph(s) of text you want added as section 5.4.4 for 2461bis. I can
review it right away.

Thanks.

Hemant=20

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Thursday, July 05, 2007 12:05 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

At Thu, 5 Jul 2007 11:06:26 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Having taken care of an NA target address that happens to be any=20
> address assigned to the receiving interface, now we are left with only

> a target address that is in ND cache of the receiving interface. Once=20
> a tentative address has been taken care of, the processing of NA goes=20
> into checking if target address lies in ND cache of the receiving=20
> interface and hence section 7.2.5 of 2461bis applies - this rule takes

> care of an unsolicited NA sent by a neighbor to the interface. Such=20
> unsolicited NA's are used by nodes to update new ND information to
neighbors.

My point is that it's not so obvious (at least to me) by simply saying
"If the target address is not tentative, the advertisement is processed
as described in [I-D.ietf-ipv6-2461bis]".  Hence my proposed text.  I'm
not sure whether you agree with it or not, but I'm still not convinced
that referring to 2461bis is enough.  So, I still plan to keep my
proposed change unless I hear otherwise from others.

Thanks,

					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 Jul 05 12: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 1I6UXX-0005aR-TJ; Thu, 05 Jul 2007 12:50:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6UXW-0005Xt-6C
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:50:46 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6UWa-0008Ix-6Y
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:50:46 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 12:49:48 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOO9jEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175486400"; 
	d="scan'208"; a="64412109:sNHT51146706"
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 l65GnlFk009068; 
	Thu, 5 Jul 2007 12:49: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 l65Gnls2017899; 
	Thu, 5 Jul 2007 16:49:47 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, 5 Jul 2007 12:49: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: Thu, 5 Jul 2007 12:49:21 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A1D7@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1ejjnmnw3.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace+w6J3qxtUROHIRmGt7W1x0Ej2/gAX6v4g
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
	<m1ejjnmnw3.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: 05 Jul 2007 16:49:46.0195 (UTC)
	FILETIME=[7E4B7230:01C7BF24]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2584; t=1183654187;
	x=1184518187; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=b0aPEcDEW257Im9XATqIP08h9ABdcGUhIna8yd/uPwo=;
	b=OnkM2+vCyihonrYXEhWx8XCkGxuYI0GJvIuKaf9pBlyCPg4kWKdWaD/Hekg7kiygd0A/+GSE
	BFWyFC76UAK5uxpB8GVurA/M6PtXhOGxfhgwkvhyeIe8+LPWItm1YaGY;
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: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>
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

Tatuya,

Have you tested BSD by sending it an RA  with no PIO and M and O bits
set so that BSD initiates DHCPv6 ? Once BSD host is online with DHCPv6
completed, issue a ping from BSD machine to another IPv6 machine on the
same link. BSD should send this ping to the default router and NOT issue
any NS to try and resolve the ping destination. Since RA did not
advertise any PIO, BSD host  has no means to make an on-link
determination and thus not issue any NS because issuing an NS just told
us BSD assumed the ping destination in on-link - that is wrong behavior.

Do also test the converse thing. A host could be incorrectly implemented
by always sending all traffic to default router and not issuing any NS.
Send an RA with PIO to BSD DHCPv6 host advertising a prefix as on-link.
Then issue a ping to another host on the same link for which the prefix
was advertised as on-link. If BSD sent the ping to default router that
is wrong. BSD has to issue an NS to resolve the destination of the ping.

Thanks.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Thursday, July 05, 2007 1:16 AM
To: Hemant Singh (shemant)
Cc: Ole Troan (otroan); Vlad Yasevich; ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

At Tue, 3 Jul 2007 10:56:32 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> In this regard, bullets 2 and 3 in Section 2 of our I-D show the issue

> hosts have when hosts incorrectly always add a directly connected=20
> route to the /64 prefix from an address assigned to an interface, even

> if the prefix is advertised as "not on link" or is not advertised at=20
> all. That incorrectly added route causes the host to try to use direct

> delivery (without sending traffic to the default router) and,=20
> therefore, use NS/NA to resolve addresses from the same prefix.
>=20
> We are prepared in this discussion that no host implementers will=20
> reply to our thread.

I already explained the BSD implementation correctly handles a prefix
advertised via an RA with the L bit being off.  Out of curiosity, which
host implementation are you specifically talking about?  You have
repeatedly stated something like "an implementer of a popular
IPv6 host [...] missed this behavior", but I don't think I've heard
which implementation it is.  Is there any reason for not being specific?

					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 Jul 05 12: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 1I6UfG-0004aB-Ea; Thu, 05 Jul 2007 12:58:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6UfF-0004Yh-Et
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:58:45 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6UeX-0003Ic-90
	for ipv6@ietf.org; Thu, 05 Jul 2007 12:58:45 -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 l65H0Ff8004166;
	Thu, 5 Jul 2007 12:00:16 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 11:57:59 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 11:57:59 -0500
Message-ID: <468D22F9.7000700@ericsson.com>
Date: Thu, 05 Jul 2007 12:57:29 -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: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>
In-Reply-To: <m2hcoi7s5p.wl%jinmei@wide.ad.jp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 05 Jul 2007 16:57:59.0492 (UTC)
	FILETIME=[A4529840:01C7BF25]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,
  I agree with your proposed change. Just referring to RFC4861 is not 
clear enough. You can arrive at the same conclusion by pointing to 
RFC4861, but the reasoning is a bit more circular. Since there is no 
text with the EXACT semantic in RFC4861, I prefer your suggested text.

Cheers
Suresh

JINMEI Tatuya / ???? wrote:
> At Thu, 5 Jul 2007 11:06:26 -0400,
> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
> 
>> Having taken care of an NA target address that happens to be any address
>> assigned to the receiving interface, now we are left with only a target
>> address that is in ND cache of the receiving interface. Once a tentative
>> address has been taken care of, the processing of NA goes into checking
>> if target address lies in ND cache of the receiving interface and hence
>> section 7.2.5 of 2461bis applies - this rule takes care of an
>> unsolicited NA sent by a neighbor to the interface. Such unsolicited
>> NA's are used by nodes to update new ND information to neighbors.
> 
> My point is that it's not so obvious (at least to me) by simply saying
> "If the target address is not tentative, the advertisement is
> processed as described in [I-D.ietf-ipv6-2461bis]".  Hence my proposed
> text.  I'm not sure whether you agree with it or not, but I'm still
> not convinced that referring to 2461bis is enough.  So, I still plan
> to keep my proposed change unless I hear otherwise from others.
> 
> Thanks,
> 
> 					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 Thu Jul 05 13:52: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 1I6VUJ-0003aS-Px; Thu, 05 Jul 2007 13:51:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6VUH-0003Qu-VN
	for ipv6@ietf.org; Thu, 05 Jul 2007 13:51:29 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6VTI-0001rQ-OU
	for ipv6@ietf.org; Thu, 05 Jul 2007 13:51:29 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 13:50:28 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAHLLjEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175486400"; 
	d="scan'208"; a="64418353:sNHT45340100"
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 l65HoR3q021627; 
	Thu, 5 Jul 2007 13:50:27 -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 l65HoN6c018778; 
	Thu, 5 Jul 2007 17:50:27 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, 5 Jul 2007 13:50:26 -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, 5 Jul 2007 13:50:25 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468D22F9.7000700@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/JaX5eJAryhwYTzu3sQKihxzmLgABxyyw
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 05 Jul 2007 17:50:26.0476 (UTC)
	FILETIME=[F8123EC0:01C7BF2C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2383; t=1183657827;
	x=1184521827; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22Suresh=20Krishnan=22=20<suresh.krishnan@ericsson.com>,
	=0A=20=20
	=20=20=20=20=20=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshi
	ba.co.jp>; bh=+88m/QvhqXrFmDdz2GW0J0DFBhpX6kQITN/lKdT1QIc=;
	b=CRD82aofOCuVWioeABRL4CF7+DLDA/nKe643e7HTEKoAeaZVdufvECl/usEqj+tFN0v2CwFO
	ndo9m6mhOdYpDjLKqByBLjGA8ysqqHDDHWrU8J9JJSDQZ3yDOPfJp64G;
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: 244a2fd369eaf00ce6820a760a3de2e8
Cc: ipv6@ietf.org
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, if I missed the paragraph Tatuya wanted to add. As I said before,
could I please see the new para for section 5.4.4 of 2461bis and I will
review it right away and get back to you. I have not agreed to Tatuya's
changes yet.

Thanks.

Hemant=20

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
Sent: Thursday, July 05, 2007 12:57 PM
To: JINMEI Tatuya / ????
Cc: Hemant Singh (shemant); ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

Hi Jinmei,
  I agree with your proposed change. Just referring to RFC4861 is not
clear enough. You can arrive at the same conclusion by pointing to
RFC4861, but the reasoning is a bit more circular. Since there is no
text with the EXACT semantic in RFC4861, I prefer your suggested text.

Cheers
Suresh

JINMEI Tatuya / ???? wrote:
> At Thu, 5 Jul 2007 11:06:26 -0400,
> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
>=20
>> Having taken care of an NA target address that happens to be any=20
>> address assigned to the receiving interface, now we are left with=20
>> only a target address that is in ND cache of the receiving interface.

>> Once a tentative address has been taken care of, the processing of NA

>> goes into checking if target address lies in ND cache of the=20
>> receiving interface and hence section 7.2.5 of 2461bis applies - this

>> rule takes care of an unsolicited NA sent by a neighbor to the=20
>> interface. Such unsolicited NA's are used by nodes to update new ND
information to neighbors.
>=20
> My point is that it's not so obvious (at least to me) by simply saying

> "If the target address is not tentative, the advertisement is=20
> processed as described in [I-D.ietf-ipv6-2461bis]".  Hence my proposed

> text.  I'm not sure whether you agree with it or not, but I'm still=20
> not convinced that referring to 2461bis is enough.  So, I still plan=20
> to keep my proposed change unless I hear otherwise from others.
>=20
> Thanks,
>=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
> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Thu Jul 05 14:07: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 1I6Vjo-0006VX-NC; Thu, 05 Jul 2007 14:07:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Vjm-0006P5-C6
	for ipv6@ietf.org; Thu, 05 Jul 2007 14:07:30 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6Vjm-0007jA-3g
	for ipv6@ietf.org; Thu, 05 Jul 2007 14:07:30 -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 l65I9Cqo015967;
	Thu, 5 Jul 2007 13:09:12 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 13:06:56 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 5 Jul 2007 13:06:56 -0500
Message-ID: <468D3322.5080503@ericsson.com>
Date: Thu, 05 Jul 2007 14:06:26 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2007 18:06:56.0145 (UTC)
	FILETIME=[45F5C010:01C7BF2F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Hemant,

Hemant Singh (shemant) wrote:
> Sorry, if I missed the paragraph Tatuya wanted to add. As I said before,
> could I please see the new para for section 5.4.4 of 2461bis and I will

The edit he was proposing was for 2462bis not 2461bis. The old para in 
section 5.4.4

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.


will be replaced with the new paragraph

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    advertisement SHOULD be silently discarded. If the target address is
    tentative, the tentative address is not unique.

Since there is no text in 2461bis to directly handle this condition, I 
believe that the suggested text makes sense.

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 Thu Jul 05 14:40: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 1I6WFY-0005eM-Nq; Thu, 05 Jul 2007 14:40:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6WFW-0005dp-L2
	for ipv6@ietf.org; Thu, 05 Jul 2007 14:40:18 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6WEZ-0008B9-Fn
	for ipv6@ietf.org; Thu, 05 Jul 2007 14:40:18 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id BF1263401D;
	Thu,  5 Jul 2007 14:38:58 -0400 (EDT)
Received: from galen.zko.hp.com (galen.zko.hp.com [16.116.113.226])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 58A34145175;
	Thu,  5 Jul 2007 18:38:58 +0000 (UTC)
Received: by galen.zko.hp.com (Postfix, from userid 1000)
	id E7CB7318056; Thu,  5 Jul 2007 14:38:57 -0400 (EDT)
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: shemant@cisco.com
Date: Thu,  5 Jul 2007 14:38:57 -0400
Message-Id: <11836607373870-git-send-email-vladislav.yasevich@hp.com>
X-Mailer: git-send-email 1.5.0.3.438.gc49b2
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7c1a129dc3801d79d40c5ca8dee767eb
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

Hi Hemant

Here is my review of your draft.  Comments are inside the <vy> </vy>
blocks.  

-vlad

1.  Introduction

   IPv6 host data forwarding and address resolution is complex.  For
   example, RFC 2461 [ND] (section 3.1) implies that if the RA received
   by the host does not advertise any prefix, then the host must send
   all non-link-local data to the default router.  This section of the
   RFC also implies that no address resolution is to be performed in
   this case.  Sections 5.2 and 7.2.2 imply that the host performs
   address resolution before transmitting a packet if the destination of
   the packet is on the same link as the host.  Some current host
   implementations perform address resolution in all cases even when the
   destination is not clearly on-link.  However, RFC 2461 [ND] section
   6.3.4 implies that hosts must clearly determine that a destination is
   on-link before performing address resolution.

<vy>
I believe that you are reading too much into section 3.1.  That section
simply does a comparison to IPv4.  It does not mandate anything and
doesn't not specify any specific beavhior.  That is saved for later.

One could argue that this section might have a touch more technical
information there then strictly need, but it is still not meant to
specify any requiremens.
</vy>

   These implications in RFC 2461 [ND] need to be made explicit.
   Failure of host implementations to comply can result in lack of IPv6
   connectivity.  For example, a host receives an RA with no prefix
   advertised and incorrectly decides to perform address resolution when
   the host should have sent all traffic to the default router.  The
   router may not respond to the address resolution and the layer 2
   driver of the host stops transmitting IPv6 packets.

<vy>
Are these meant to describe 2 different scenarios or just one?  If only
one, both implementations violate multiple aspects of the protocol.
</vy>

2.  Host Models

   A correctly implemented IPv6 host MUST adhere to the following rules:

   1.  On-link determination and address information MUST NOT persist
       across IPv6 interface initializations.

<vy>
Either you are not clear enough here, or this requirement is overly
strict.  There is nothing with having configured address information
persist acrsoss across full system or interface initializations.

I agree that on-link determination information SHOULD NOT persist,
but clever people can do some very clever things.  I think SHOULD NOT
is strong enough.
</vy>

   2.  The RA and 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.

<vy>
You should really restrict this to other types for dynamic configuration
</vy>


   3.  The host MUST NOT add a direct delivery route to the prefix from
       an assigned address, independent of the information about the
       prefix received from the RA or Redirects.
<vy>
Can you please explain what exactly you mean here.  I am having
difficulty properly understanding this sentence.
</vy>

   5.  The host SHOULD issue only a single NS(DAD) for each address.
       The default value for DupAddrDetectTransmits variable is
       specified as 1 in section 5.1 of RFC 2462 [ADDRCONF].

<vy>
What exactly are you trying to address with this text?  When I read
it, my first impulse is to assume that you want to limit the number
of DAD Soliciations to 1 per address, which is not really correct
and is _probably_ not what you mean.  Can you explain a little more.
</vy>


   6.  If the Default Router List is empty, the host MUST NOT assume
       that all destinations are on-link.  The host MUST NOT perform
       address resolution for non-link-local addresses.  The host SHOULD
       send an ICMPv6 Destination Unreachable message instead.
<vy>
No that's not correct.  The host can perform address resolution if he
has on-link prefexis.  It it permissable to have on-link prefixes without
specifying a default router (I have a private isolated network).
</vy>


2.1.  RA Sets M and O Bits but does not Include the Prefix Information
      Option (PIO)

[... draft text snipped ...]

   An IPv6 router sends an RA with no prefix advertised and the M and O
   bits set and does not send any Redirects.  On receipt of the RA, the
   host uses DHCPv6 to acquire an IPv6 address.  After completing IPv6
   address acquisition, the host MUST obey RFC 2461 [ND], section 3.1.
   Since the RA is the only authority to a host for on-link
   determination and this RA does not advertise any prefix, the host
   cannot determine that a destination is on-link.  Therefore, the host
   MUST adhere to the following rules:

   1.  The host MUST NOT assume any default prefix length.

   2.  The host MUST send all non-link-local traffic to the default
       router.

   3.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
One can argue that a host/DHCP client that inferes a prefix length
from a leased address is prone to other failures as well.  In this
case, it's the DHCP client that is most likely a problem, unless
the host implementation mistakenly alwasy assumes /64 length.  I think
this is actually warned against in the Address Architure document.

2461bis clearly states that a set 'L' flag is the only determination
of on-link.  Anything else you can report to your vendor as "Bug".

The above actually would be a very good test to add to the TAHI conformance
test suite.
</vy>


2.2.  RA Advertises a Prefix with the On-link(L) Bit Set

[... draft text sniped ...]

   Consider the following scenario with one rogue node and two other
   hosts on the same link.  The rogue sends a malicious RA with an on-
   link prefix with a Valid Lifetime of zero.  Host1 correctly
   implements section 5.5.3 of RFC 2462 [ADDRCONF] and resets its
   StoredLifetime (or RemainingLifetime in draft-ietf-ipv6-rfc2462bis-08
   [ADDRCONFbis]) to two hours and avoids the denial of service attack.
   Host1 tries to send traffic to Host2, but cannot trust its own two
   hour StoredLifetime.  For instance, a legitimate operator may have
   tried to time out the prefix due to an impending renumbering.  Host1
   decides to send all of its traffic to the on-link authority, the
   default router, even though the destination prefix is on-link.

   IF the host decides to send all traffic (including on-link traffic)
   to the default router, then the host MUST follow the following rule:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
This is kind of reduntant.  The host can either determine that the
destination is on-link (i.e it trusts its prefix list), or it sends it
to the default router.  The only time it would preform NS would be for
on-link determination which means that it trust the prefix list.
I don't see any further need to call out this particular scenario.
</vy>



2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear

   Regardless of whether the host performs DHCPv6 and/or stateless
   autoconfiguration, the host MUST adhere to the following rules for
   addresses contained within the advertised prefix:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

   2.  The host MUST send all non-link-local traffic to the default
       router.

<vy>
No.  If the host already had a on-link prefix in the list that matches
the the one with 'L' bit clear, it should not change the on-link assumption
and continue using address resolution.

If this is a new prefix with the 'L' bit clear, then 2461bis already
addresses this issue appropriatly.
</vy>


3.1.  Aggregation Router Deployment Model

   No NS to resolve any address other that that of the default router
   will reach the aggregation router from any device on the customer
   side of the aggregator.  CPEs do not communicate with each other in
   this deployment model since a CPE does not run any applications that
   need to communicate with other CPEs.  Hosts do communicate with each
   other, but every host is off-link to any other host on the
   aggregation router.

<vy>
Yes, they are off-link.  So why would they thing their are on-link?
Each CPE Rtr or Cust Rtr whould have it's own prefix that would
be advertized to the CPE hosts.  Therese prefixes would aggregate
at the Agregator.   Why would NSs from the CPE hosts escape?
</vy>


5.  Changes to draft-ietf-ipv6-rfc2461bis-11

[... old text snipped ...]

      "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.  Without
      advertised prefixes, without manual configuration, and without
      redirects, hosts MUST NOT assume a default prefix length, 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.

<vy>
No, this is the wrong section to include such requirements since the section
currenlty doesn't place any specific requirements on the implementation.
</vy>


6.  Changes to draft-ietf-ipv6-rfc2462bis-08

[... old text snipped ...]

   to read as follows:

      Each individual unicast address SHOULD be tested for uniqueness.
      Note that some deployed implementations perform Duplicate Address
      Detection (DAD) only for the link-local address and skip the test
      for the global address using the same interface identifier.
      Whereas this document does not invalidate such implementations,
      this kind of 'optimization' is NOT RECOMMENDED, and new
      implementations MUST NOT do that optimization.  This optimization
      came from the assumption that all of an interface's addresses are
      generated from the same interface identifier (see RFC 2462
      [ADDRCONF]).  However, even with this assumption, skipping DAD for
      non-link-local addresses with manual configuration creates an
      additional problem.  This optimization allows an interface to
      claim a duplicate address in a way that would not be detected.
      For a more detailed description of this problem, see the Host
      Models section of
      draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
      types of addresses have been introduced where the interface
      identifiers are not necessarily the same for all unicast addresses
      on a single interface [RFC3041] [RFC3972].  Requiring an interface
      to perform DAD for all unicast addresses will make the algorithm
      more robust.

<vy>
Two issues:
 1. This text is not any stronger then the existing text in 2461bis and
    doesn't add anything significant.

 2. It creates a normative reference to a personal draft at a very late
    stage in the life of 2461bis.

I don't see a reason to add this text
</vy>

My conlcusion:

After re-reading 2461bis and 2462bis multiple times as result of reviewing
this draft, I can see some small value in creating an "On-Link Determination"
section in draft 2461bis.

Alternatively, this draft should crate such section and, with references
to text in 2461bis, should clarify the on-link determination behavior.
It could then be issued as an update.

-vlad




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



From ipv6-bounces@ietf.org Thu Jul 05 15:28: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 1I6Wyp-0007ch-Kc; Thu, 05 Jul 2007 15:27:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Wyn-0007Cz-Ce
	for ipv6@ietf.org; Thu, 05 Jul 2007 15:27:05 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6Wxj-0005ix-Ad
	for ipv6@ietf.org; Thu, 05 Jul 2007 15:27:05 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 15:25:59 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAC/ijEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175486400"; 
	d="scan'208"; a="64427719:sNHT66841824"
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 l65JPxks015490; 
	Thu, 5 Jul 2007 15:25:59 -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 l65JPisS007472; 
	Thu, 5 Jul 2007 19:25:58 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, 5 Jul 2007 15:25:50 -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, 5 Jul 2007 15:25:48 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A293@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/L1DusD0Vdzs+SmaJ/IPLB9rbdgAANCSQAAJmq2A=
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>, "Suresh Krishnan" <suresh.krishnan@ericsson.com>
X-OriginalArrivalTime: 05 Jul 2007 19:25:50.0103 (UTC)
	FILETIME=[4B9E6A70:01C7BF3A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2505; t=1183663559;
	x=1184527559; 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:=20FW=3A=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20 |To:=20<ipv6@ietf.org>,
	=20=22Suresh=20Krishnan=22=20<suresh.krishnan@eric sson.com>;
	bh=gph/HyxGlAUY0AZ+kbtFrEvSDzwnYSrdjsDlSAm9sQk=;
	b=ulRmYA+TLPvxIp7P+O/xUa3cfw9R+cLxy7C2AvRbnf9pp23A51SUGUW4UxJAfpP0W3rFtPcw
	C9etGzg8SWpyp7BPOqAs3a8cYXCX/8Xk4soUgQ1TdKg1yT0HLIWl0NFI;
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: d0bdc596f8dd1c226c458f0b4df27a88
Cc: JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: FW: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 for the spam if this is a 2nd copy of the email. I didn't see this
email in my mail yet nor the ipv6 archives. Suresh or Tatuya, please
reply.

Thanks.

Hemant=20

-----Original Message-----
From: Hemant Singh (shemant)=20
Sent: Thursday, July 05, 2007 2:23 PM
To: 'Suresh Krishnan'
Cc: JINMEI Tatuya / ????; ipv6@ietf.org
Subject: RE: Revisit: one remaining corner case in DAD

Suresh,

Yes, sorry, I had a typo wrt 2461 vs 2462. Thanks so much for providing
the para. Now I have a separate question to you folks.

What IPv6 network has an interface receiving an NA where the target
address in the NA matched an assigned address on the receiving interface
given the fact the address that matched is not tentative? Also, once
this situation happens, why is it not a DAD failure and hence logged
with an error message rather than a silent discard?

Thanks.

Hemant & Wes

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]
Sent: Thursday, July 05, 2007 2:06 PM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

Hi Hemant,

Hemant Singh (shemant) wrote:
> Sorry, if I missed the paragraph Tatuya wanted to add. As I said=20
> before, could I please see the new para for section 5.4.4 of 2461bis=20
> and I will

The edit he was proposing was for 2462bis not 2461bis. The old para in
section 5.4.4

    On receipt of a valid Neighbor Advertisement message on an
interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.


will be replaced with the new paragraph

    On receipt of a valid Neighbor Advertisement message on an
interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    advertisement SHOULD be silently discarded. If the target address is
    tentative, the tentative address is not unique.

Since there is no text in 2461bis to directly handle this condition, I
believe that the suggested text makes sense.

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 Thu Jul 05 15:59: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 1I6XTc-000666-NJ; Thu, 05 Jul 2007 15:58:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6XTb-00063A-Qt
	for ipv6@ietf.org; Thu, 05 Jul 2007 15:58:56 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6W0B-0001ba-De
	for ipv6@ietf.org; Thu, 05 Jul 2007 14:24:27 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 05 Jul 2007 11:23:26 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOPTjEarR7MV/2dsb2JhbAA
X-IronPort-AV: i="4.16,504,1175497200"; 
	d="scan'208"; a="177177395:sNHT615862359"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l65INQ74014268; 
	Thu, 5 Jul 2007 11:23:26 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l65INLXH003982;
	Thu, 5 Jul 2007 18:23:22 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, 5 Jul 2007 14:23: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: Thu, 5 Jul 2007 14:23:20 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468D3322.5080503@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/L1DusD0Vdzs+SmaJ/IPLB9rbdgAANCSQ
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>
X-OriginalArrivalTime: 05 Jul 2007 18:23:21.0501 (UTC)
	FILETIME=[914724D0:01C7BF31]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2108; t=1183659806;
	x=1184523806; c=relaxed/simple; s=sjdkim1004;
	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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20;
	bh=DomF/vHshtInvFslGEHOg+jKVMXDn02UXm8twWIPdnc=;
	b=OM7Npwc3BaPZag8Lq//4Hx6r2jOnpUWQiNciCjZt9sbHjTqnUw+TBiB9nVzKP08s7/TXx6B+
	4/dA5LEJtElhU4Um9jkE8HEOJMKPiVP0VL6Rd1U3ZRYj1GhXwCrKW3ob/R928ziAL/bml9CCWD
	lUsDhWNWQp9KrSpC9HA+xCdlE=;
Authentication-Results: sj-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Suresh,

Yes, sorry, I had a typo wrt 2461 vs 2462. Thanks so much for providing
the para. Now I have a separate question to you folks.

What IPv6 network has an interface receiving an NA where the target
address in the NA matched an assigned address on the receiving interface
given the fact the address that matched is not tentative? Also, once
this situation happens, why is it not a DAD failure and hence logged
with an error message rather than a silent discard?

Thanks.

Hemant & Wes

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
Sent: Thursday, July 05, 2007 2:06 PM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

Hi Hemant,

Hemant Singh (shemant) wrote:
> Sorry, if I missed the paragraph Tatuya wanted to add. As I said=20
> before, could I please see the new para for section 5.4.4 of 2461bis=20
> and I will

The edit he was proposing was for 2462bis not 2461bis. The old para in
section 5.4.4

    On receipt of a valid Neighbor Advertisement message on an
interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.


will be replaced with the new paragraph

    On receipt of a valid Neighbor Advertisement message on an
interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    advertisement SHOULD be silently discarded. If the target address is
    tentative, the tentative address is not unique.

Since there is no text in 2461bis to directly handle this condition, I
believe that the suggested text makes sense.

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 Thu Jul 05 16:48: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 1I6YEx-0007bV-7P; Thu, 05 Jul 2007 16:47:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6YEv-0007aW-CQ
	for ipv6@ietf.org; Thu, 05 Jul 2007 16:47:49 -0400
Received: from atlrel8.hp.com ([156.153.255.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6YEr-0007qo-2o
	for ipv6@ietf.org; Thu, 05 Jul 2007 16:47:49 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel8.hp.com (Postfix) with ESMTP id 5457034C8E;
	Thu,  5 Jul 2007 16:47:37 -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 2C96214468E;
	Thu,  5 Jul 2007 20:47:10 +0000 (UTC)
Message-ID: <468D58CD.6090204@hp.com>
Date: Thu, 05 Jul 2007 16:47:09 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>
	<468D22F9.7000700@ericsson.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.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: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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:
> Suresh,
> 
> Yes, sorry, I had a typo wrt 2461 vs 2462. Thanks so much for providing
> the para. Now I have a separate question to you folks.
> 
> What IPv6 network has an interface receiving an NA where the target
> address in the NA matched an assigned address on the receiving interface
> given the fact the address that matched is not tentative?

This is a convoluted scenario but it can happen when a previously routed
network flattens out and merges into a swiched/bridged fabric.

We've had this happen in our lab when testing different DAD features.

>From my personal perspective, some kind of warning should be signaled.
The NAs can be safely discarded though (just not silently).  At this point
in time completely disabling the network is too severe. 

-vlad

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



From ipv6-bounces@ietf.org Thu Jul 05 18:19: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 1I6Zej-0005sH-FJ; Thu, 05 Jul 2007 18:18:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Zeg-0005nN-Bs
	for ipv6@ietf.org; Thu, 05 Jul 2007 18:18:30 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6Zeg-0005oD-1q
	for ipv6@ietf.org; Thu, 05 Jul 2007 18:18:30 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 05 Jul 2007 18:18:21 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CADMLjUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,505,1175486400"; 
	d="scan'208"; a="64445210:sNHT39159352"
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 l65MIL6a013077; 
	Thu, 5 Jul 2007 18:18:21 -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 l65MILs0025183; 
	Thu, 5 Jul 2007 22:18:21 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, 5 Jul 2007 18:18: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: Thu, 5 Jul 2007 18:18:20 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468D58CD.6090204@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/RdAHhJlCtTDVQGmS2Rub8n5wSAACvogA
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>
	<468D22F9.7000700@ericsson.com>	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 05 Jul 2007 22:18:21.0320 (UTC)
	FILETIME=[656CC880:01C7BF52]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2216; t=1183673901;
	x=1184537901; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=QygMls0guJe2884T4u/SLDgV6JkPAohwseyqT7JFpQ4=;
	b=MrVx89Y11S6P+pCD8aND1SuOa2d2EDaT/KPGCYg8015pLsWCb7D7RLAGq92AqWpAQkQ4c+P6
	0kfFP1JJ7jKZ40oDBUjJHftn1lrV57D/9PirmtiZNGtGKme/StzfcUO/;
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: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Vlad,

Thanks for the explanation. This is precisely the explanation Wes Beebee
gave me in person at Cisco but we still decided to ping IETF folks
anyway to confirm any other reasons. OK, now that we all are convinced
that a convoluted scenario can cause this situation of target address in
NA to occur, notice that Vlad also agrees with myself and Wes that such
an NA should not be silently discarded. I agree with Vlad that disabling
the network is too severe for this case.

I think Tatuya first leaned towards the silent discard behavior because
he wanted text in 2462bis to match text in first para of section 7.2.5
of 2461bis. However, I see that as matching apples with oranges. The NA
in section 7.2.5 of 2461bis is silently discarded if the target address
of NA does not exist in ND cache of the receiving interface. The NA in
section 5.4.4 of 2462bis is being dropped because the target address in
NA matches an address on the receiving interface - we have already
asked, why is such a match not deemed as a duplicate and hence an error
mgmt message raised?

Thanks.

Hemant

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Thursday, July 05, 2007 4:47 PM
To: Hemant Singh (shemant)
Cc: Suresh Krishnan; ipv6@ietf.org; JINMEI Tatuya / ????
Subject: Re: Revisit: one remaining corner case in DAD

Hemant Singh (shemant) wrote:
> Suresh,
>=20
> Yes, sorry, I had a typo wrt 2461 vs 2462. Thanks so much for=20
> providing the para. Now I have a separate question to you folks.
>=20
> What IPv6 network has an interface receiving an NA where the target=20
> address in the NA matched an assigned address on the receiving=20
> interface given the fact the address that matched is not tentative?

This is a convoluted scenario but it can happen when a previously routed
network flattens out and merges into a swiched/bridged fabric.

We've had this happen in our lab when testing different DAD features.

>From my personal perspective, some kind of warning should be signaled.
The NAs can be safely discarded though (just not silently).  At this
point in time completely disabling the network is too severe.=20

-vlad

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



From ipv6-bounces@ietf.org Thu Jul 05 20:55: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 1I6c5y-00067I-VV; Thu, 05 Jul 2007 20:54:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6c5y-00067C-18
	for ipv6@ietf.org; Thu, 05 Jul 2007 20:54:50 -0400
Received: from wa-out-1112.google.com ([209.85.146.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6c5t-0005fm-Nc
	for ipv6@ietf.org; Thu, 05 Jul 2007 20:54:50 -0400
Received: by wa-out-1112.google.com with SMTP id k17so77726waf
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 17:54: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=HP59cGl6xt0aGSHYqVCQQ0Gfn5FLXPG7NpuOw2tCxWUAksdNo7FLJyV3n0uyiRcO82NmA9LSiu4QIIiRrSf7KvM+p87j2uWRTmspSA5VJVyynrJ8CS5xer8uUmg8Mr3EE7zLPkhMjb9Dzh4sLTxNp0R17c/dCEM/ehdZ1UkoMUM=
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=PkUVj+Vzl4Zhc4G03PBetNi5XTwc5FNti7CgUjIoxMAM4gXIaaWc0YUeh/xrGKsVgVDgzqB2ZRcaDoQvenh7pAjTUidsWENeGpJj8nYZZLgqXObDW6oAKMJMjIbsE7qrm08UpCnteHnJlu6jts+PnFHiXItsJHP9OB9wqwLBGxc=
Received: by 10.115.32.1 with SMTP id k1mr157279waj.1183683284929;
	Thu, 05 Jul 2007 17:54:44 -0700 (PDT)
Received: by 10.114.93.7 with HTTP; Thu, 5 Jul 2007 17:54:44 -0700 (PDT)
Message-ID: <75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
Date: Thu, 5 Jul 2007 20:54:44 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "=?ISO-8859-1?Q?R=E9mi_Denis-Courmont?=" <rdenis@simphalempin.com>
In-Reply-To: <200707022118.31271@auguste.remlab.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: IPv6 WG <ipv6@ietf.org>
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

On 7/2/07, R=E9mi Denis-Courmont <rdenis@simphalempin.com> wrote:
> Le jeudi 28 juin 2007, ext Bob Hinden a =E9crit :
> > 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.
>
> Document is fine with me. But what are the consequences with regards to
> RFC3542? Should implementations stop parsing RH0 at that level as well?

I fear that deprecating a part of the spec is going to lead to some
confusion (as is shown above) and probably isn't the only option... I
had wanted to send some longer feedback to jabley/ipv6@ but missed out
it seems :(

In short, I think that deprecation removes some functionality that
people may want  to use (perhaps even for a good reason). There are
other issues with removing this from the spec, like making another set
of corner cases implementors will have to check for, ala cisco's
'protocols' bug of 2 years ago (just picking an example not picking on
a vendor). Giving the network the option to ignore RH0 headers would
have skipped us past this problem, and left the spec in good standing
for the cases that might want to use it for good.

-Chris

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



From ipv6-bounces@ietf.org Thu Jul 05 21:16: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 1I6cR0-0002Vr-Ez; Thu, 05 Jul 2007 21:16:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6cQy-0002VO-7v
	for ipv6@ietf.org; Thu, 05 Jul 2007 21:16:32 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6cQx-0005va-Sk
	for ipv6@ietf.org; Thu, 05 Jul 2007 21:16:32 -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 l661FNol025751;
	Thu, 5 Jul 2007 18:15:24 -0700
Message-ID: <081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Perry Lorier" <perry@coders.net>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
	<468C84E9.10902@coders.net>
Date: Thu, 5 Jul 2007 19:59:41 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: 2.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

Thus spake "Perry Lorier" <perry@coders.net>
> Stephen Sprunk wrote:
>> The fact that one _can_ assign both ULAs and PA space to hosts is 
>> irrelevant; I'm well aware of that.  NAT is perceived by IT folks as less 
>> hassle than renumbering hosts.  PA space implies frequent renumbering. 
>> Therefore, many (most?) IT depts who cannot get PI space will use NAT 
>> rather than assign PA space to hosts.
>
> However in IPv4 you can have PA xor PI space, you can't have both at the 
> same time.  With IPv6 you can have PA+"private PI" (aka ULA) space.

See above.

> Changing your PI space every time your modem dials up is perhaps a bit 
> extreme, but it shows that you can ""renumber"" your network rapidly in 
> some situations.

A single host is easy to renumber.  A small network with one router is only 
slightly more complicated.  However, renumbering a medium-sized or large 
network can take months to years to accomplish and hundreds of thousands of 
dollars in manpower.

> Problems occur for externally facing services,

As a general rule, clients are easy to renumber, whereas servers are 
difficult and firewalls are even worse.  And I'm including human costs and 
resistance in that; changing the address on an interface is almost a 
nonevent in comparison.

> but that doesn't seem insurmountable for an organisation that's likely to
> only change PI space at most every year or so.

Why would you ever change PI space?  The issue is changing PA space, and 
that's something that may need to be done every few weeks as upstream links 
go up and down.  Compare to the cost of a NAT box and the choice is easy.

> If your choices are PI vs PA then yeah NAT does look very attractive, but 
> if you can have PA and "private"-PI (aka ULA) then things look a lot less 
> blurred (IMHO).

IMHO, you underestimate how much IT folks hate renumbering.

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 Thu Jul 05 22:26: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 1I6dVy-0001Fb-9Y; Thu, 05 Jul 2007 22:25:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6dVw-00019n-S9
	for ipv6@ietf.org; Thu, 05 Jul 2007 22:25:44 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6dVv-0000yT-DB
	for ipv6@ietf.org; Thu, 05 Jul 2007 22:25: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 9281A7301E;
	Fri,  6 Jul 2007 11:25:41 +0900 (JST)
Date: Fri, 06 Jul 2007 11:25:28 +0900
Message-ID: <m1zm2al147.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: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A1D7@xmb-rtp-20e.amer.cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<468678D1.40000@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589BF6@xmb-rtp-20e.amer.cisco.com>
	<7t5bqet8uno.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C23@xmb-rtp-20e.amer.cisco.com>
	<7t57iph8sw1.fsf@gpk-xdm-001.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03589C8A@xmb-rtp-20e.amer.cisco.com>
	<m1ejjnmnw3.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A1D7@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: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>
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

At Thu, 5 Jul 2007 12:49:21 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Have you tested BSD by sending it an RA  with no PIO and M and O bits
> set so that BSD initiates DHCPv6 ? Once BSD host is online with DHCPv6
> completed, issue a ping from BSD machine to another IPv6 machine on the
> same link. BSD should send this ping to the default router and NOT issue
> any NS to try and resolve the ping destination. Since RA did not
> advertise any PIO, BSD host  has no means to make an on-link
> determination and thus not issue any NS because issuing an NS just told
> us BSD assumed the ping destination in on-link - that is wrong behavior.
> 
> Do also test the converse thing. A host could be incorrectly implemented
> by always sending all traffic to default router and not issuing any NS.
> Send an RA with PIO to BSD DHCPv6 host advertising a prefix as on-link.
> Then issue a ping to another host on the same link for which the prefix
> was advertised as on-link. If BSD sent the ping to default router that
> is wrong. BSD has to issue an NS to resolve the destination of the ping.

I previously tested these scenarios.  I've not done that recently, but
I'm pretty sure that BSDs would still show the conforming behavior in
both of the test cases (i.e., send the packet to the default router in
the first scenario; send NS in the second scenario).

					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 Jul 05 22:32: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 1I6dc1-0002Zf-LP; Thu, 05 Jul 2007 22:32:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6dc0-0002Za-5l
	for ipv6@ietf.org; Thu, 05 Jul 2007 22:32:00 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6dby-0001IN-Kk
	for ipv6@ietf.org; Thu, 05 Jul 2007 22:32:00 -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 0C701114021
	for <ipv6@ietf.org>; Fri,  6 Jul 2007 02:31:58 +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 62520E609D
	for <ipv6@ietf.org>; Fri,  6 Jul 2007 02:31:57 +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 l662VaEc040318;
	Fri, 6 Jul 2007 12:31:36 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200707060231.l662VaEc040318@drugs.dv.isc.org>
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Thu, 05 Jul 2007 19:59:41 EST."
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com> 
Date: Fri, 06 Jul 2007 12:31:36 +1000
X-Spam-Score: -0.9 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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


> Thus spake "Perry Lorier" <perry@coders.net>
> > Stephen Sprunk wrote:
> >> The fact that one _can_ assign both ULAs and PA space to hosts is 
> >> irrelevant; I'm well aware of that.  NAT is perceived by IT folks as less 
> >> hassle than renumbering hosts.  PA space implies frequent renumbering. 
> >> Therefore, many (most?) IT depts who cannot get PI space will use NAT 
> >> rather than assign PA space to hosts.
> >
> > However in IPv4 you can have PA xor PI space, you can't have both at the 
> > same time.  With IPv6 you can have PA+"private PI" (aka ULA) space.
> 
> See above.
> 
> > Changing your PI space every time your modem dials up is perhaps a bit 
> > extreme, but it shows that you can ""renumber"" your network rapidly in 
> > some situations.
> 
> A single host is easy to renumber.  A small network with one router is only 
> slightly more complicated.  However, renumbering a medium-sized or large 
> network can take months to years to accomplish and hundreds of thousands of 
> dollars in manpower.
> 
> > Problems occur for externally facing services,
> 
> As a general rule, clients are easy to renumber, whereas servers are 
> difficult and firewalls are even worse.  And I'm including human costs and 
> resistance in that; changing the address on an interface is almost a 
> nonevent in comparison.
> 
> > but that doesn't seem insurmountable for an organisation that's likely to
> > only change PI space at most every year or so.
> 
> Why would you ever change PI space?  The issue is changing PA space, and 
> that's something that may need to be done every few weeks as upstream links 
> go up and down.  Compare to the cost of a NAT box and the choice is easy.

	Please justify this assumption.

	Are you still thinking that there would be a single PA per
	host?  If you are connected to the same upstream via multiple
	paths then there is/should be no need to renumber.  If you
	are connected to multiple upstreams then you have multiple
	PA prefixes on each and every box.  It should be be as easy
	as having the routers deprecating the prefix advertisements
	to have all the end systems select alternate PA addresses
	when initiating sessions.
 
> > If your choices are PI vs PA then yeah NAT does look very attractive, but 
> > if you can have PA and "private"-PI (aka ULA) then things look a lot less 
> > blurred (IMHO).
> 
> IMHO, you underestimate how much IT folks hate renumbering.
> 
> 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
> --------------------------------------------------------------------
-- 
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 Jul 05 23:58: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 1I6exU-0004y3-2o; Thu, 05 Jul 2007 23:58:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6exR-0004rb-Ef
	for ipv6@ietf.org; Thu, 05 Jul 2007 23:58:13 -0400
Received: from wa-out-1112.google.com ([209.85.146.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6exN-0003dP-3T
	for ipv6@ietf.org; Thu, 05 Jul 2007 23:58:13 -0400
Received: by wa-out-1112.google.com with SMTP id k17so127531waf
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 20:58: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=nJ8KZrWT2AyUEGa0fXaqKPXNu8mAJubv8OSd7vi2NfLQv3F/oJlM1Tm9/QuXfvsx47+cqGqXf48TcoM0dO9Nu4uHfxgrI+boOY5cKWuzFPu2WS6XATDILD+ZVlt9hYnKJbjYgYcCqQ3d0cp5srE0QruH7NuDsr+2Qbd79W6tgA4=
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=i2pjw9vwkwlFpsd8YkdSJ3s/nowNaWXbG8jmnDPGvo+MrufqZrkwFYpRup2PwBcbJONdpe1qkBi/HtJd2W9WKlIeRPNqijBVyvjY/XpRNeKuUGEJH+0wZk5o79/j0dlUVmDZmhZNJ/2uykHteIXAt3MyJ/E0Q+mjJviAlNkUWq0=
Received: by 10.114.157.1 with SMTP id f1mr282376wae.1183694288431;
	Thu, 05 Jul 2007 20:58:08 -0700 (PDT)
Received: by 10.114.24.20 with HTTP; Thu, 5 Jul 2007 20:58:08 -0700 (PDT)
Message-ID: <77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
Date: Thu, 5 Jul 2007 20:58:08 -0700
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Christopher Morrow" <christopher.morrow@gmail.com>
In-Reply-To: <75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: IPv6 WG <ipv6@ietf.org>
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

Hi Chris,

I think the general view was that RH0, can be deprecated and a new
more secure Routing Header can be used to get the functionality for
required.

I have put a draft for the checks required, in any such header. I
intend to modify the draft to take care of introducing the new Routing
Header. It would be great to hear of use cases from the operators
where the functionality is required.

Thanks,
Vishwas

On 7/5/07, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> On 7/2/07, R=E9mi Denis-Courmont <rdenis@simphalempin.com> wrote:
> > Le jeudi 28 juin 2007, ext Bob Hinden a =E9crit :
> > > 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.
> >
> > Document is fine with me. But what are the consequences with regards to
> > RFC3542? Should implementations stop parsing RH0 at that level as well?
>
> I fear that deprecating a part of the spec is going to lead to some
> confusion (as is shown above) and probably isn't the only option... I
> had wanted to send some longer feedback to jabley/ipv6@ but missed out
> it seems :(
>
> In short, I think that deprecation removes some functionality that
> people may want  to use (perhaps even for a good reason). There are
> other issues with removing this from the spec, like making another set
> of corner cases implementors will have to check for, ala cisco's
> 'protocols' bug of 2 years ago (just picking an example not picking on
> a vendor). Giving the network the option to ignore RH0 headers would
> have skipped us past this problem, and left the spec in good standing
> for the cases that might want to use it for good.
>
> -Chris
>

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



From ipv6-bounces@ietf.org Fri Jul 06 00: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 1I6fTd-0000Nm-4i; Fri, 06 Jul 2007 00:31:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6fTb-0000Mt-72
	for ipv6@ietf.org; Fri, 06 Jul 2007 00:31:27 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6fTX-0007OK-N0
	for ipv6@ietf.org; Fri, 06 Jul 2007 00:31:27 -0400
Received: by wa-out-1112.google.com with SMTP id k17so136251waf
	for <ipv6@ietf.org>; Thu, 05 Jul 2007 21:31: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:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=nWfLZqm2ZAmzEYsas0642nAOc4Mk2IiyDQwHsMqyfN5lx/4BEkuhJdN2Y+8TA/4haCBxO6/dLENQ1frzDK59hk9EH0NgcVmts/A4uo3T7LSZOjPk8xb7v0PaGdxkKvSjevZPLjwZ9YdrWIVbiBPJjfGy6DVAVVmPCJxmzr134No=
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=coViUjialrAsCHDMrtCCIInPGvOQLUOYf3kLyYhP8kz/ltlt0hoR66/ri93j63o7DJy1UFzE+X2oMEHYDUuDVGkqzPNwO7gF40gEd3dkrFDHFKmejMNw/2iuLqLeIUFK52tDMmUt8VDc4+szRso2BfWDxishkoAlKp0JVW9CrOQ=
Received: by 10.115.88.1 with SMTP id q1mr286695wal.1183696282963;
	Thu, 05 Jul 2007 21:31:22 -0700 (PDT)
Received: by 10.114.93.7 with HTTP; Thu, 5 Jul 2007 21:31:22 -0700 (PDT)
Message-ID: <75cb24520707052131y5b4f5469h6ab618bb522d542b@mail.gmail.com>
Date: Fri, 6 Jul 2007 00:31:22 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
In-Reply-To: <77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
	<77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: IPv6 WG <ipv6@ietf.org>
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

On 7/5/07, Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi Chris,
>
> I think the general view was that RH0, can be deprecated and a new
> more secure Routing Header can be used to get the functionality for
> required.

So, sure... my fear is that lots of baked code/hardware today is going
to do 'funny things' ... and isn't going to get replaced any time
soon. I admit that I'm not sure that routing gear could be easily
'modified' to  ignore RH0 either, so maybe my fear is moot.

>
> I have put a draft for the checks required, in any such header. I
> intend to modify the draft to take care of introducing the new Routing
> Header. It would be great to hear of use cases from the operators
> where the functionality is required.
>

unfortunately I can only come up with a sample cheesey example: (which
depends on the applications doing RH0 tagging)

an enterprise has a set of links between remote sites ( one expensive
and low-latency/low-jitter/low-loss, one the opposite ) Perhaps it
makes sense for them to push their voip across the 'better' link and
everything else on the 'bad' link. They could do this with policy
routing, or by being careful with addressing plans... or their
applications could simply RH0 the traffic and take care of it
themselves.

(yes, I realize there probably a half dozen ways/reasons to do this
but it's one example that I'm certain some wierd enterprise op will
attempt at some point)

There might be one other use which was an original use for ipv4 source-rout=
ing:

I want to test a path between ATT and L3 and on to a L3 customer, I'm
a UU customer, I want to bounce the traffic off the CHI ATT device and
through an NYC UU device, I'd need to force routing to UU in NYC, then
ATT in CHI then on to the destination. (yes, this is also contrived,
sorry)

The point being that atleast 2 hops might be necessary, perhaps
more... Breaking this thruogh deprecation seems sketchy at best. In
the abstract for the draft:

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

My point about deprecating something we really can't quantify usage of
is that I can pull examples from my hindquarters all day long, but I
can't (nor can anyone I suspect) really say if this is being used in
practice. That's a bad thing, we could be advocating breaking
something that folks depend upon, in closed communities off of the
'internet' where most of the concern seems to live (for this draft
atleast).

I think there are probably many other reasons that RH0 could be
considered 'bad', why is this one (amplification) the focus? why not
also get rid of icmp or udp or tcp? these can also all be use for
amplification attacks, yes?

I hesitate to get rid or something because of this sole reason, I
think another answer would be to make paying attention to it just
optional for routing gear (or all things, honestly I really only care
about routing gear, and so does this draft).

I'd also take issue, for many of the same reasons stated earlier with:

"The severity of this threat is considered to be sufficient to warrant
   deprecation of RH0 entirely"

from the draft, I don't think that deprecation is warranted in this
case, if it is than anything that can cause amplification attacks is
likely also in need of deprecation.

Allow consenting adults to do potentially harmful things is 'ok'.
Intermediate networks may decide to honor or not the 'potentially
harmful things', but that's their individual decision and shouldn't be
baked into the spec if at all possible.

-Chris

> Thanks,
> Vishwas
>
> On 7/5/07, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> > On 7/2/07, R=E9mi Denis-Courmont <rdenis@simphalempin.com> wrote:
> > > Le jeudi 28 juin 2007, ext Bob Hinden a =E9crit :
> > > > This starts a two week IPv6 working group last call on advancing
> > > >
> > > >       Title           : Deprecation of Type 0 Routing Headers in IP=
v6
> > > >       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.
> > >
> > > Document is fine with me. But what are the consequences with regards =
to
> > > RFC3542? Should implementations stop parsing RH0 at that level as wel=
l?
> >
> > I fear that deprecating a part of the spec is going to lead to some
> > confusion (as is shown above) and probably isn't the only option... I
> > had wanted to send some longer feedback to jabley/ipv6@ but missed out
> > it seems :(
> >
> > In short, I think that deprecation removes some functionality that
> > people may want  to use (perhaps even for a good reason). There are
> > other issues with removing this from the spec, like making another set
> > of corner cases implementors will have to check for, ala cisco's
> > 'protocols' bug of 2 years ago (just picking an example not picking on
> > a vendor). Giving the network the option to ignore RH0 headers would
> > have skipped us past this problem, and left the spec in good standing
> > for the cases that might want to use it for good.
> >
> > -Chris
> >
>

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



From ipv6-bounces@ietf.org Fri Jul 06 02:28: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 1I6hJ0-0006up-DX; Fri, 06 Jul 2007 02:28:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6hIy-0006t3-Bq
	for ipv6@ietf.org; Fri, 06 Jul 2007 02:28:36 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6hIx-00067U-M9
	for ipv6@ietf.org; Fri, 06 Jul 2007 02:28:36 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:101a:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 110047301E;
	Fri,  6 Jul 2007 15:28:33 +0900 (JST)
Date: Fri, 06 Jul 2007 15:28:20 +0900
Message-ID: <m1odiqkpvf.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: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@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: 244a2fd369eaf00ce6820a760a3de2e8
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 5 Jul 2007 18:18:20 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> I think Tatuya first leaned towards the silent discard behavior because
> he wanted text in 2462bis to match text in first para of section 7.2.5
> of 2461bis. However, I see that as matching apples with oranges. The NA
> in section 7.2.5 of 2461bis is silently discarded if the target address
> of NA does not exist in ND cache of the receiving interface. The NA in
> section 5.4.4 of 2462bis is being dropped because the target address in
> NA matches an address on the receiving interface - we have already
> asked, why is such a match not deemed as a duplicate and hence an error
> mgmt message raised?

I've been thinking it over again, and I now agree that we should
rather leave a log message in this case (while discarding the NA).

This is an abnormal case anyway, but if it ever happens the most
likely scenario is:

- there is actually duplicate assignment which has not been detected
  by DAD due to network fragmentation, packet drop, etc.
- then the conflicting node sends out an unsolicited NA for some
  reason such as L2 address change

I also agree that it is overkilling to require the receiving host to
stop using the seemingly duplicate address.  We know DAD is not 100%
reliable, so the best thing to do for such undetected duplicates would
be to leave a warning/log message and let the administrator fix the
issue by hand.  Requiring to stop using the address is also suboptimal
in that it could be exploited by an attacker for DoS.

In conclusion I'd like to propose to change the paragraph of
Section 5.4.4 from:

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.

to:

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    advertisement SHOULD be discarded and the node SHOULD log a
    system management error; this case would indicate that the address
    is a duplicate but it has not been detected by the Duplicate
    Address Detection procedure, which should be manually handled by
    the system administrator.  If the target address is tentative, the
    tentative address is not unique.

(the additional note "this case would indicate..." may sound too
verbose.  If so, I'm willing to remove it.)

Does this make sense?

					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 Jul 06 03:19: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 1I6i6W-0003EN-OG; Fri, 06 Jul 2007 03:19:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6i6V-0003DE-5E
	for ipv6@ietf.org; Fri, 06 Jul 2007 03:19:47 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6i6U-0008WP-Iw
	for ipv6@ietf.org; Fri, 06 Jul 2007 03:19:47 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:101a:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id B32407301F;
	Fri,  6 Jul 2007 16:19:44 +0900 (JST)
Date: Fri, 06 Jul 2007 16:19:31 +0900
Message-ID: <m1lkdukni4.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: <0FF50CE9-6CC9-4AE8-8F1E-0A90C818FBF2@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>
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: 25620135586de10c627e3628c432b04a
Cc: IETF Mailing List IPv6 <ipv6@ietf.org>,
	Stig Venaas <stig.venaas@uninett.no>
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 Fri, 29 Jun 2007 12:06:21 -0400,
Ralph Droms <rdroms@cisco.com> wrote:

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

I believe so.  Even though the concepts of address/prefix are
different for IPv4 and for IPv6 in some points, I'm pretty sure that
an administrator would expect when they execute

# ifconfig ed0 inet6 2001:db8:1234::abcd prefixlen 64

the system treats 2001:db8:1234::/64 as on-link, just like they would
expect when they execute

# ifconfig ed0 inet 192.0.2.1 netmask 0xffffff00

the system treats 192.0.2.0/24 as on-link.

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

IMO the key difference is "automatic" (whether stateless or DHCPv6) vs
"manual".  In the case of RA (for on-link prefix) + DHCPv6, everything
will be set up automatically, so I'd agree that it makes more sense
not to have the redundant information in DHCPv6.  In the case of
manual configuration of addresses, the administrator should be able to
control everything, so I think it's reasonable for the administrator
to allow to specify both the address and on-link prefix information
even when the node is also receiving RAs.

BTW: I personally think this situation (manual address assignment with
RA for on-link info) is very atypical and is not really appropriate to
compare with the common case for DHCPv6(address) + RA(on-link) in the
first place.  But if the administrator really wants to do it, they can
achieve the result by specifying 128 as the prefix length:

# ifconfig ed0 inet6 2001:db8:1234::abcd prefixlen 128

at least on BSDs.

Finally, I'd like to note that prefix information option with L=0 does
not mean the correspondent prefix is off-link.

   [...]  Note, however, that a Prefix Information option
   with the on-link flag set to zero conveys no information concerning
   on-link determination and MUST NOT be interpreted to mean that
   addresses covered by the prefix are off-link.  The only way to cancel
(Section 6.3.4 of RFC2461)

So, by executing

# ifconfig ed0 inet6 2001:db8:1234::abcd prefixlen 64
(while receiving RAs with the prefix information for 2001:db8:1234::/0
and L=0)

the administrator is not "overriding" the information advertised by
the RA; they are simply "specifying" the information which has not
been provided.

					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 Jul 06 03:47: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 1I6iXH-0002K7-L9; Fri, 06 Jul 2007 03:47:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6iXG-0002HE-IW
	for ipv6@ietf.org; Fri, 06 Jul 2007 03:47:26 -0400
Received: from wx-out-0506.google.com ([66.249.82.226])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6iXC-0004d8-2r
	for ipv6@ietf.org; Fri, 06 Jul 2007 03:47:26 -0400
Received: by wx-out-0506.google.com with SMTP id h27so117047wxd
	for <ipv6@ietf.org>; Fri, 06 Jul 2007 00:47:21 -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=F1eA5JiuezR7Uc5AKV5uJPlEmIcFuxEVcZLVtPPogxqehClP85fQtOuRBoFh0PJu1e/tXAhoG2QXBIVg+TFJ0/D9AuHFF1Z4D8dgACrQYAFW24IzraekAM/s4MhB05I/tTfzFUJigKfw9xRJtojaaDjWrObcpvCBiIUXBQN9VjQ=
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=ScgLnALBDgbHSvpik44lvGC77b0aM2M8T07TF/zBfFhav8+pQwzEPByFnuh9Fa75/giCU54JuOzpUKI86p08lx9UHJP6CG3mpdYA0iNBHqkdp0ufmX9mEFElMngk714TztWRXML+ZTmQ3wYqv1od5AR+bfqel/IOZfdl0RZ/qA8=
Received: by 10.70.45.10 with SMTP id s10mr804250wxs.1183708041861;
	Fri, 06 Jul 2007 00:47:21 -0700 (PDT)
Received: from ?10.10.50.3? ( [213.3.13.1])
	by mx.google.com with ESMTP id 18sm8512264wry.2007.07.06.00.47.20
	(version=SSLv3 cipher=RC4-MD5); Fri, 06 Jul 2007 00:47:21 -0700 (PDT)
Message-ID: <468DF387.5000400@gmail.com>
Date: Fri, 06 Jul 2007 09:47: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: Stephen Sprunk <stephen@sprunk.org>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>	<468C481A.1010405@coders.net>	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
In-Reply-To: <081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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-07-06 02:59, Stephen Sprunk wrote:
...

> Why would you ever change PI space?  The issue is changing PA space, and 
> that's something that may need to be done every few weeks as upstream 
> links go up and down.  

Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
If you drop or add an ISP you drop or add a prefix in a planned manner.
RFC 4192.

> Compare to the cost of a NAT box and the choice 
> is easy.

That's true if you don't put the indirect operational and user
costs of NAT, plus the opportunity cost of innovation blocked
by NAT, into the equation. It *is* hard to get this into the budget
unless you think strategically, and factor in the way IPv6 is
designed to handle multiple PA prefixes simultaneously.

> 
>> If your choices are PI vs PA then yeah NAT does look very attractive, 
>> but if you can have PA and "private"-PI (aka ULA) then things look a 
>> lot less blurred (IMHO).
> 
> IMHO, you underestimate how much IT folks hate renumbering.

They hate renumbering IPv4 networks. I do too, having managed such an
operation a couple of times. It's as a result of that hatred that
IPv6 came out as it is, making RFC 4192 possible.

This is *not* to say that anyone will renumber weekly, and big networks
will avoid it (and are therefore candidates for PI). But for smaller
networks, the hatred should be substantially less, and balance the hatred
of NAT.

    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 Jul 06 08:47: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 1I6nDN-0000mi-K0; Fri, 06 Jul 2007 08:47:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6nDM-0000mZ-Qm
	for ipv6@ietf.org; Fri, 06 Jul 2007 08:47:12 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6nDM-0006ph-JO
	for ipv6@ietf.org; Fri, 06 Jul 2007 08:47:12 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel9.hp.com (Postfix) with ESMTP id BB18536C73;
	Fri,  6 Jul 2007 08:44:49 -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 B1599143B0E;
	Fri,  6 Jul 2007 12:44:21 +0000 (UTC)
Message-ID: <468E3924.7030402@hp.com>
Date: Fri, 06 Jul 2007 08:44:20 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?=
	<jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>	
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>	 <468D22F9.7000700@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>	
	<468D3322.5080503@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>	
	<468D58CD.6090204@hp.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> In conclusion I'd like to propose to change the paragraph of
> Section 5.4.4 from:
>=20
>     On receipt of a valid Neighbor Advertisement message on an interfac=
e,
>     node behavior depends on whether the target address is tentative or
>     matches a unicast or anycast address assigned to the interface.  If
>     the target address is assigned to the receiving interface, the
>     solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
>     If the target address is tentative, the tentative address is not
>     unique.
>=20
> to:
>=20
>     On receipt of a valid Neighbor Advertisement message on an interfac=
e,
>     node behavior depends on whether the target address is tentative or
>     matches a unicast or anycast address assigned to the interface.  If
>     the target address is assigned to the receiving interface, the
>     advertisement SHOULD be discarded and the node SHOULD log a
>     system management error; this case would indicate that the address
>     is a duplicate but it has not been detected by the Duplicate
>     Address Detection procedure, which should be manually handled by
>     the system administrator.  If the target address is tentative, the
>     tentative address is not unique.
>=20
> (the additional note "this case would indicate..." may sound too
> verbose.  If so, I'm willing to remove it.)
>=20
> Does this make sense?

The only part of the above paragraph that I keep questioning is
the inclusion of anycast.   I thought that it was perfectly fine
to have duplicate anycast addresses on the same link and 2461bis
still permits that.

So I would change start the second sentence of the above paragraph
as: "If the target address is a unicast address assigned to the receiving=
 interface, ..."

Thanks
-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 Jul 06 09:56: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 1I6oGv-0003SV-GA; Fri, 06 Jul 2007 09:54:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6oGt-0003SE-Bd
	for ipv6@ietf.org; Fri, 06 Jul 2007 09:54:55 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6oGp-0002Fs-0M
	for ipv6@ietf.org; Fri, 06 Jul 2007 09:54:55 -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 1I6oJK-000JUn-BS; Fri, 06 Jul 2007 13:57:26 +0000
In-Reply-To: <75cb24520707052131y5b4f5469h6ab618bb522d542b@mail.gmail.com>
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
	<77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
	<75cb24520707052131y5b4f5469h6ab618bb522d542b@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: <5F998D87-B1EA-41EF-AFF3-7F41373106D6@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Fri, 6 Jul 2007 09:54:43 -0400
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: IPv6 WG <ipv6@ietf.org>
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


On 6-Jul-2007, at 00:31, Christopher Morrow wrote:

> I hesitate to get rid or something because of this sole reason, I
> think another answer would be to make paying attention to it just
> optional for routing gear (or all things, honestly I really only care
> about routing gear, and so does this draft).

Actually, no -- hosts which conform to the current spec also process  
RH0. So even if all IPv6 routers had RH0 functionality removed, hosts  
could still act as bounce points for the purposes of congesting  
remote paths.

> I'd also take issue, for many of the same reasons stated earlier with:
>
> "The severity of this threat is considered to be sufficient to warrant
>   deprecation of RH0 entirely"
>
> from the draft, I don't think that deprecation is warranted in this
> case, if it is than anything that can cause amplification attacks is
> likely also in need of deprecation.

So, to summarise: your proposal is that RH0 should not be deprecated,  
but that it should be made optional? I'm not convinced that I  
understand how that's going to prevent the "amplification over remote  
paths" problem.

Note too that several widely-deployed IPv6 stacks have already taken  
the approach of effectively deprecating RH0. So there's a practical  
consideration that if we decide to do something different, we are  
diverging from deployed practice.


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 Jul 06 10:14: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 1I6oXY-0006Vv-93; Fri, 06 Jul 2007 10:12:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6oXU-0006M7-SD
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:12:05 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6oTi-0005dU-3N
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:08:14 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1847583uge
	for <ipv6@ietf.org>; Fri, 06 Jul 2007 07:08:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=CxfWGPFPYBqVIL9Frp0C5WbBECE1vcUn9QyUHCRVHYzAnRGz9aggXcpMjFdcC9eSs3AlFgqGQXHUwtKN+B+8qiTvITIdZsfXesBa2ZEd60FHxJlLQ1zP1rKjcsEAFNDM9Hxy+vI69WEvNw6M1pnFfDbCdgcDSTBOMw4PHH5LaH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=mDDS9GF5+NfE1VR5iroOBqvhhRdiA2fed9P4yj3o+gikFj7FFqMjTKU8kG8wa5L+kZFhpemoIor2wnjxQyKvV3Rbo8D+eErRGbM3MKSPoRvp0uEqFn3fQ2fkWL1Qb5QFv5Tx0PeWv4B4YXHJnz1Ci0yvc0t+yPXnmzvhZc/SrF0=
Received: by 10.82.189.6 with SMTP id m6mr1802513buf.1183730889132;
	Fri, 06 Jul 2007 07:08:09 -0700 (PDT)
Received: from ?192.168.1.105? ( [212.119.9.178])
	by mx.google.com with ESMTP id 6sm21466301nfv.2007.07.06.07.08.07
	(version=TLSv1/SSLv3 cipher=OTHER);
	Fri, 06 Jul 2007 07:08:08 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: ipv6@ietf.org
Date: Fri, 6 Jul 2007 16:09:42 +0200
User-Agent: KMail/1.9.1
References: <CA8EB93B28BD0F4C88392699600BD65503D596E4@xmb-rtp-211.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A1D7@xmb-rtp-20e.amer.cisco.com>
	<m1zm2al147.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1zm2al147.wl%jinmei@isl.rdc.toshiba.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200707061609.46891.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / =?utf-8?q?=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
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

On Friday 06 July 2007 04:25, JINMEI Tatuya / ???? 
wrote:
> At Thu, 5 Jul 2007 12:49:21 -0400,
>
> "Hemant Singh (shemant)" <shemant@cisco.com> wrote:
> > Have you tested BSD by sending it an RA  with no
> > PIO and M and O bits set so that BSD initiates
> > DHCPv6 ? Once BSD host is online with DHCPv6
> > completed, issue a ping from BSD machine to
> > another IPv6 machine on the same link. BSD should
> > send this ping to the default router and NOT issue
> > any NS to try and resolve the ping destination.
> > Since RA did not advertise any PIO, BSD host  has
> > no means to make an on-link determination and thus
> > not issue any NS because issuing an NS just told
> > us BSD assumed the ping destination in on-link -
> > that is wrong behavior.
> >
> > Do also test the converse thing. A host could be
> > incorrectly implemented by always sending all
> > traffic to default router and not issuing any NS.
> > Send an RA with PIO to BSD DHCPv6 host advertising
> > a prefix as on-link. Then issue a ping to another
> > host on the same link for which the prefix was
> > advertised as on-link. If BSD sent the ping to
> > default router that is wrong. BSD has to issue an
> > NS to resolve the destination of the ping.
>
> I previously tested these scenarios.  I've not done
> that recently, but I'm pretty sure that BSDs would
> still show the conforming behavior in both of the
> test cases (i.e., send the packet to the default
> router in the first scenario; send NS in the second
> scenario).

FWIW, tested both of these 3 months ago for NETLMM 
related work and it did work fine!

-- julien

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



From ipv6-bounces@ietf.org Fri Jul 06 10:16: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 1I6obY-0006S6-Az; Fri, 06 Jul 2007 10:16:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6obW-0006Ol-Mf
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:16:14 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6obW-0003qH-Dy
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:16:14 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 06 Jul 2007 10:16:14 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMvqjUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,508,1175486400"; 
	d="scan'208"; a="64493291:sNHT43953888"
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 l66EGEE0031809; 
	Fri, 6 Jul 2007 10:16:14 -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 l66EFisY004750; 
	Fri, 6 Jul 2007 14:16:11 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, 6 Jul 2007 10:16:03 -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, 6 Jul 2007 10:16:01 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A491@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468E3924.7030402@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/y6qO+lWcL18rRUSqxrbEoekqfAACUEUg
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>	
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>	 <468D22F9.7000700@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>	
	<468D3322.5080503@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>	
	<468D58CD.6090204@hp.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<468E3924.7030402@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>,
	=?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?=
	<jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 06 Jul 2007 14:16:03.0074 (UTC)
	FILETIME=[2F4C9E20:01C7BFD8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3217; t=1183731374;
	x=1184595374; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.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=uQTm45Lgifbfnpb0BITsavOXeFRO2dw+aipUvQYbTQg=;
	b=0Q/Q55ZJQLJpECiJUNLxUWH/wVcA2eNpnxkijozMFehwsta49WuOL7W7GPgMY7n5XN/H46DM
	/P8rQ1SVjKsEnMJ6OTOGJLHZehq2gKOskTqS8VxJFaFdAC2TwKsZkoDg;
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: 082a9cbf4d599f360ac7f815372a6a15
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

Thanks for agreeing with our suggestion to not silently discard the advertisement. The new paragraph from you is still not complete because you have missed the part when a match of target address is not found in the receiving interface, then the NA has to be processed as per 2461bis. Vlad has a correct point too about anycast addresses - note section 5.4 of 2462bis says "Duplicate Address Detection MUST NOT be performed on anycast addresses".  Here is the new text suggested by us:

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address matches a unicast
    address assigned (tentative or not tentative) to the interface.  If the target 
    address matches, then the address is not unique.  The advertisement 
    SHOULD be discarded and the node SHOULD log a system management error.
    The situation should be handled manually by the system administrator.
    If the target address does not match, then the advertisement is 
    processed as described in [ID.ietf-ipv6-2461bis].

- Hemant and Wes

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com] 
Sent: Friday, July 06, 2007 8:44 AM
To: JINMEI Tatuya / ????
Cc: Hemant Singh (shemant); Suresh Krishnan; ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD


JINMEI Tatuya / $B?@L@C#:H(J wrote:
> In conclusion I'd like to propose to change the paragraph of Section 
> 5.4.4 from:
> 
>     On receipt of a valid Neighbor Advertisement message on an interface,
>     node behavior depends on whether the target address is tentative or
>     matches a unicast or anycast address assigned to the interface.  If
>     the target address is assigned to the receiving interface, the
>     solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
>     If the target address is tentative, the tentative address is not
>     unique.
> 
> to:
> 
>     On receipt of a valid Neighbor Advertisement message on an interface,
>     node behavior depends on whether the target address is tentative or
>     matches a unicast or anycast address assigned to the interface.  If
>     the target address is assigned to the receiving interface, the
>     advertisement SHOULD be discarded and the node SHOULD log a
>     system management error; this case would indicate that the address
>     is a duplicate but it has not been detected by the Duplicate
>     Address Detection procedure, which should be manually handled by
>     the system administrator.  If the target address is tentative, the
>     tentative address is not unique.
> 
> (the additional note "this case would indicate..." may sound too 
> verbose.  If so, I'm willing to remove it.)
> 
> Does this make sense?

The only part of the above paragraph that I keep questioning is
the inclusion of anycast.   I thought that it was perfectly fine
to have duplicate anycast addresses on the same link and 2461bis still permits that.

So I would change start the second sentence of the above paragraph
as: "If the target address is a unicast address assigned to the receiving interface, ..."

Thanks
-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 Jul 06 10:46: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 1I6p4m-0005qt-Qa; Fri, 06 Jul 2007 10:46:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6p4l-0005qk-7d
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:46:27 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6p4c-0006La-Qg
	for ipv6@ietf.org; Fri, 06 Jul 2007 10:46:23 -0400
Received: by wa-out-1112.google.com with SMTP id k17so349844waf
	for <ipv6@ietf.org>; Fri, 06 Jul 2007 07:46:18 -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=Dtnq/s2uYLrnJ+caKTbC/Xh2WEyqD7GMIWqdfW5vU8mxUmw6QBg0/0x+EsiEs9YJfz8sB5NZ42om0J6VS+m1rJB/8nlPhxhnjdAC1GtqFk+lsr3qfx5qC944QJqMGyvu6Ai7ktOhIxEogZQTng2fxEuFRD8hqu4OE/lTqGqgdQQ=
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=sxI9CCvdHXySUXjgYTadN0GRMeqWhMqFZB1dvzMOmhvtGtmy0LPWBp79/pUAHt17B0lrur+DAvryr9Al2k0ObGgzI0+jc5KPZzOPLu8vbmZIy1zaHrg+eNTr9cAdSrf47ypc2cp08zuPXM7642Kdzfx6LmPx5/StkF74qb5LKI4=
Received: by 10.114.174.2 with SMTP id w2mr704387wae.1183733178017;
	Fri, 06 Jul 2007 07:46:18 -0700 (PDT)
Received: by 10.114.93.7 with HTTP; Fri, 6 Jul 2007 07:46:17 -0700 (PDT)
Message-ID: <75cb24520707060746y65df0fafqab8aa576dfa9671c@mail.gmail.com>
Date: Fri, 6 Jul 2007 10:46:17 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "Joe Abley" <jabley@ca.afilias.info>
In-Reply-To: <5F998D87-B1EA-41EF-AFF3-7F41373106D6@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: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
	<77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
	<75cb24520707052131y5b4f5469h6ab618bb522d542b@mail.gmail.com>
	<5F998D87-B1EA-41EF-AFF3-7F41373106D6@ca.afilias.info>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: IPv6 WG <ipv6@ietf.org>
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

On 7/6/07, Joe Abley <jabley@ca.afilias.info> wrote:
>
> On 6-Jul-2007, at 00:31, Christopher Morrow wrote:
>
> > I hesitate to get rid or something because of this sole reason, I
> > think another answer would be to make paying attention to it just
> > optional for routing gear (or all things, honestly I really only care
> > about routing gear, and so does this draft).
>
> Actually, no -- hosts which conform to the current spec also process
> RH0. So even if all IPv6 routers had RH0 functionality removed, hosts
> could still act as bounce points for the purposes of congesting
> remote paths.

I recognize that a host could still be used as a bounce-point, if the
router ignores the header though ... no real amp effect arises, unless
you can bounce between hosts across a router link in a meaningful
manner. This still is fixable with a simple filter (just like smurf or
other sorts of amplification attacks).

I should probably also flesh out some of the 'ignore' option, if RH0
exists, pass along the packet unless it's destined to 'me' then decide
to honor/ignore the header.

>
> > I'd also take issue, for many of the same reasons stated earlier with:
> >
> > "The severity of this threat is considered to be sufficient to warrant
> >   deprecation of RH0 entirely"
> >
> > from the draft, I don't think that deprecation is warranted in this
> > case, if it is than anything that can cause amplification attacks is
> > likely also in need of deprecation.
>
> So, to summarise: your proposal is that RH0 should not be deprecated,
> but that it should be made optional? I'm not convinced that I
> understand how that's going to prevent the "amplification over remote
> paths" problem.
>

I'm not convinced that the problem is dire enough to warrant
completely removing the capability that we don't even have any idea
about usage of :( I suppose I see deprecation as a very large hammer,
where letting folks decide to not honor the header on their
wide-area/internet network seems less damaging, or less drastic
atleast.

> Note too that several widely-deployed IPv6 stacks have already taken
> the approach of effectively deprecating RH0. So there's a practical
> consideration that if we decide to do something different, we are
> diverging from deployed practice.
>

which? fbsd? obsd? they took the large hammer approach for some
specious set of reasons? What about XP/MacOSX/Vista/Solaris/HP-UX ?

I still go back to the 'do we want to use the really big hammer here?'
question. I don't see this as being any worse than other amplification
vectors and we haven't talked seriously about deprecating any of
those, so why this one?

-Chris

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



From ipv6-bounces@ietf.org Fri Jul 06 11:31: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 1I6pmQ-0006mo-8s; Fri, 06 Jul 2007 11:31:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6pmO-0006lK-59
	for ipv6@ietf.org; Fri, 06 Jul 2007 11:31:32 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6pmK-0000RI-Mr
	for ipv6@ietf.org; Fri, 06 Jul 2007 11:31:32 -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 1I6poX-000L9A-Ms; Fri, 06 Jul 2007 15:34:00 +0000
In-Reply-To: <75cb24520707060746y65df0fafqab8aa576dfa9671c@mail.gmail.com>
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<200707022118.31271@auguste.remlab.net>
	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>
	<77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>
	<75cb24520707052131y5b4f5469h6ab618bb522d542b@mail.gmail.com>
	<5F998D87-B1EA-41EF-AFF3-7F41373106D6@ca.afilias.info>
	<75cb24520707060746y65df0fafqab8aa576dfa9671c@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: <976D885D-7C24-4D94-81DF-934C19A26AF1@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Fri, 6 Jul 2007 11:31:02 -0400
To: "Christopher Morrow" <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: IPv6 WG <ipv6@ietf.org>
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

[Note that I am not replying out of a desire to engage in advocacy;  
you should read this more as editorial summaries of discussions that  
have already happened here when the questions you raised were asked  
before.]

On 6-Jul-2007, at 10:46, Christopher Morrow wrote:

> I recognize that a host could still be used as a bounce-point, if the
> router ignores the header though ... no real amp effect arises, unless
> you can bounce between hosts across a router link in a meaningful
> manner.

No, that's not the case. If you bounce traffic between two RH0- 
supporting hosts, then all the routers between them need to do is  
process the destination address in order for the remote congestion  
effect to be possible.

> This still is fixable with a simple filter (just like smurf or
> other sorts of amplification attacks).

Right, to stop the traffic routers would need to examine the whole  
chain of extension headers in each packet in order to see whether  
there's a type-0 routing header in there, and apply suitable policy  
in the event that one is found.

I think we heard from people that this is a lot of work to be done  
(e.g. in an ASIC), and is contrary to the high-level design goal of  
letting routers do their thing with minimal amounts of per-packet work.

>> So, to summarise: your proposal is that RH0 should not be deprecated,
>> but that it should be made optional? I'm not convinced that I
>> understand how that's going to prevent the "amplification over remote
>> paths" problem.
>
> I'm not convinced that the problem is dire enough to warrant
> completely removing the capability that we don't even have any idea
> about usage of :(

I think the inference is that we are early enough in the IPv6  
deployment cycle that if someone really is relying on RH0 support in  
protocol stacks, there's sufficient time for a new (RH, something) to  
be defined and implemented to provide whatever functionality is  
required without posing a wider hazard.

I think the only use cases we have heard of here are (a) the  
experimentation documented by Biondi/Ebalard in their CanSecWest  
presentation, and (b) the ability to perform traceroutes from a  
remote source. We did not hear from anybody with the perspective that  
RH0 support was a critical aspect of IPv6 for them. I do not mean to  
imply that the lack of such an opinion means that there's nobody who  
holds that opinion, of course.

The pertinent questions are, I suppose, (a) whether there's a use- 
case which would be profoundly crippled by the deprecation of RH0 in  
the protocol specification, and (b) whether such a crippling would  
pose a greater danger to the Internet at large than the risks of RH0  
which have been documented.

The current best-known answers (wrt "remote traceroute") are (a) yes,  
but it's functionality that the IPv4 Internet happily does without,  
and hence (b) no.

>> Note too that several widely-deployed IPv6 stacks have already taken
>> the approach of effectively deprecating RH0. So there's a practical
>> consideration that if we decide to do something different, we are
>> diverging from deployed practice.
>
> which? fbsd? obsd?

The WIDE-derived stacks have done this, which in practical terms  
means *BSD plus Apple. Itojun may be able to clarify if you want a  
more exact list of implementations and the changes they have decided  
to make.

> they took the large hammer approach for some
> specious set of reasons? What about XP/MacOSX/Vista/Solaris/HP-UX ?

According to the CanSecWest slides, "Windows" (not sure which  
versions) "implements a conservative default behaviour (drops en- 
route packets)". I don't know what Solaris or HP/UX do. I see  
committed patches for Linux which deprecate RH0, but I'm not  
sufficiently in-tune with the Linux development process to know  
whether any of those have been formally adopted in a mainstream kernel.

Whether or not their reasons were specious seems entirely subjective.  
However, in the interests of avoiding that rat-hole, I think I will  
constrain myself to technical considerations :-)

> I still go back to the 'do we want to use the really big hammer here?'
> question. I don't see this as being any worse than other amplification
> vectors and we haven't talked seriously about deprecating any of
> those, so why this one?

Which other amplification vectors did you have in mind?


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 Jul 06 12: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 1I6qpW-0006db-2Y; Fri, 06 Jul 2007 12:38:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6qpU-0006a9-8d
	for ipv6@ietf.org; Fri, 06 Jul 2007 12:38:48 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6qpP-00031g-Fy
	for ipv6@ietf.org; Fri, 06 Jul 2007 12:38:48 -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 88CF773022;
	Sat,  7 Jul 2007 01:38:41 +0900 (JST)
Date: Sat, 07 Jul 2007 01:38:34 +0900
Message-ID: <m21wfla3n9.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: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A491@xmb-rtp-20e.amer.cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<468E3924.7030402@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A491@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: 73734d43604d52d23b3eba644a169745
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 6 Jul 2007 10:16:01 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Thanks for agreeing with our suggestion to not silently discard the
> advertisement. The new paragraph from you is still not complete
> because you have missed the part when a match of target address is
> not found in the receiving interface, then the NA has to be
> processed as per 2461bis. Vlad has a correct point too about anycast
> addresses - note section 5.4 of 2462bis says "Duplicate Address
> Detection MUST NOT be performed on anycast addresses".  Here is the
> new text suggested by us:

>     On receipt of a valid Neighbor Advertisement message on an interface,
>     node behavior depends on whether the target address matches a unicast
>     address assigned (tentative or not tentative) to the interface.  If the target 
>     address matches, then the address is not unique.  The advertisement 
>     SHOULD be discarded and the node SHOULD log a system management error.
>     The situation should be handled manually by the system administrator.
>     If the target address does not match, then the advertisement is 
>     processed as described in [ID.ietf-ipv6-2461bis].

I agree that we should also cover the case where the target address
doesn't match (which was missing in my original proposal).  I also
see I should have been more careful about the anycast cast.  But I
don't think the suggested text of yours is correct.

Actually, we should consider the following cases:

1. the target address does not match any assigned addresses and it's
   not a tentative (unicast) address
2. the target address is tentative (this implies it's a unicast
   address)
3. the target address is a unicast address assigned to the interface
   (this implies the address is not tentative)
4. the target address is an anycast address assigned to the interface

In case 1, the NA is processed as described in 2461bis.

In case 2, the address is not unique and the procedure described in
Section 5.4.5 should be performed.

In case 3, the node should discard the NA and log a system management
error.  I mainly focused on this case in my (revised) proposal.

In case 4, hmm, I'm not sure whether 2462bis should specify the
behavior.  Since this case is irrelevant to unique vs duplicate, it
should be out of scope of 2462bis.  Although I'm not sure if 2461bis
clarifies that case, all we can do would be to leave this case to
2461bis, too.

Your proposed text seems to require the same processing for cases 2
and 3 (and even 4), which doesn't look correct to me - it at least
looks different from what we agreed on earlier in this thread.

So, my third proposal is to change the paragraph of Section 5.4.4
from:

    On receipt of a valid Neighbor Advertisement message on an interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.

to:

    On receipt of a valid Neighbor Advertisement message on an
    interface, node behavior depends on whether the target address is
    tentative or matches a unicast or anycast address assigned to the
    interface.  If the target address is tentative, the tentative
    address is not unique.  Otherwise, if the target address matches a
    unicast address assigned to the receiving interface, the
    advertisement SHOULD be discarded and the node SHOULD log a system
    management error; this case would indicate that the address is a
    duplicate but it has not been detected by the Duplicate Address
    Detection procedure, which should be manually handled by the
    system administrator.  The advertisement is processed as described
    in [I-D.ietf-ipv6-2461bis] for all other cases.

(the additional note "this case would indicate..." may sound too
verbose.  If so, I'm willing to remove it.)

					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 Jul 06 12:52: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 1I6r2Z-0004yH-L2; Fri, 06 Jul 2007 12:52:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6r2X-0004vZ-To
	for ipv6@ietf.org; Fri, 06 Jul 2007 12:52:17 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6r2T-0003e0-Hb
	for ipv6@ietf.org; Fri, 06 Jul 2007 12:52:17 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id 0C821341A3;
	Fri,  6 Jul 2007 12:51:36 -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 1177B18C973;
	Fri,  6 Jul 2007 16:51:27 +0000 (UTC)
Message-ID: <468E730F.8090409@hp.com>
Date: Fri, 06 Jul 2007 12:51:27 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?=
	<jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>	
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>	
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp>	 <468D22F9.7000700@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>	
	<468D3322.5080503@ericsson.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>	
	<468D58CD.6090204@hp.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>	
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>	
	<468E3924.7030402@hp.com>	
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A491@xmb-rtp-20e.amer.cisco.com>
	<m21wfla3n9.wl%jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m21wfla3n9.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
>=20
>     On receipt of a valid Neighbor Advertisement message on an
>     interface, node behavior depends on whether the target address is
>     tentative or matches a unicast or anycast address assigned to the
>     interface.  If the target address is tentative, the tentative
>     address is not unique.  Otherwise, if the target address matches a
>     unicast address assigned to the receiving interface, the
>     advertisement SHOULD be discarded and the node SHOULD log a system
>     management error; this case would indicate that the address is a
>     duplicate but it has not been detected by the Duplicate Address
>     Detection procedure, which should be manually handled by the
>     system administrator.  The advertisement is processed as described
>     in [I-D.ietf-ipv6-2461bis] for all other cases.
>=20
> (the additional note "this case would indicate..." may sound too
> verbose.  If so, I'm willing to remove it.)

I like this text.  It addresses all the bullets very well IMO.

In fact, this almost exactly what I was about to send... :)

Thanks
-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 Jul 06 13:04: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 1I6rEb-0002vr-IA; Fri, 06 Jul 2007 13:04:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6rEZ-0002tl-4L
	for ipv6@ietf.org; Fri, 06 Jul 2007 13:04:43 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6rEV-0004WI-Na
	for ipv6@ietf.org; Fri, 06 Jul 2007 13:04:43 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 06 Jul 2007 13:04:39 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CALMRjkZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,509,1175486400"; 
	d="scan'208"; a="64512053:sNHT69347100"
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 l66H4dpc017822; 
	Fri, 6 Jul 2007 13:04:39 -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 l66H4d6a002735; 
	Fri, 6 Jul 2007 17:04:39 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, 6 Jul 2007 13:04: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: Fri, 6 Jul 2007 13:04:35 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A57E@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m21wfla3n9.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: Ace/7Cr4QyA65V89QteF0sEo2AItxAAAo5lg
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<468E3924.7030402@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A491@xmb-rtp-20e.amer.cisco.com>
	<m21wfla3n9.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: 06 Jul 2007 17:04:36.0230 (UTC)
	FILETIME=[BB35C260:01C7BFEF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4951; t=1183741479;
	x=1184605479; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=y5nk/KEj1UmTUi+mdMzQieSaqAxqEgkR7uI+1Jl8EHE=;
	b=eGvQjLC2658773l54mMm5ZpuVVu9O9RWVqrZNOT6Z6rLKbgqd+tZ0qQP7U4qwC43Da7n/Zuq
	3/wH+pNaR5Gzgc0GvnPrasSb74ewETgsP/hUd59ADbB8VhAbWOH9X86A;
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: 67c1ea29f88502ef6a32ccec927970f0
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

The new paragraph looks good.=20

I had combined matched tentative and non-tentative addresses handling
with a common error message logged, but I see your point that let's
handle the tentative by sending the handling to section 5.4.5 and handle
the non-tentative with an error message. Processing anycast with 2461bis
sounds fine.

Thanks.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Friday, July 06, 2007 12:39 PM
To: Hemant Singh (shemant)
Cc: Vlad Yasevich; Suresh Krishnan; ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

At Fri, 6 Jul 2007 10:16:01 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Thanks for agreeing with our suggestion to not silently discard the=20
> advertisement. The new paragraph from you is still not complete=20
> because you have missed the part when a match of target address is not

> found in the receiving interface, then the NA has to be processed as=20
> per 2461bis. Vlad has a correct point too about anycast addresses -=20
> note section 5.4 of 2462bis says "Duplicate Address Detection MUST NOT

> be performed on anycast addresses".  Here is the new text suggested by

> us:

>     On receipt of a valid Neighbor Advertisement message on an
interface,
>     node behavior depends on whether the target address matches a
unicast
>     address assigned (tentative or not tentative) to the interface.
If the target=20
>     address matches, then the address is not unique.  The
advertisement=20
>     SHOULD be discarded and the node SHOULD log a system management
error.
>     The situation should be handled manually by the system
administrator.
>     If the target address does not match, then the advertisement is=20
>     processed as described in [ID.ietf-ipv6-2461bis].

I agree that we should also cover the case where the target address
doesn't match (which was missing in my original proposal).  I also see I
should have been more careful about the anycast cast.  But I don't think
the suggested text of yours is correct.

Actually, we should consider the following cases:

1. the target address does not match any assigned addresses and it's
   not a tentative (unicast) address
2. the target address is tentative (this implies it's a unicast
   address)
3. the target address is a unicast address assigned to the interface
   (this implies the address is not tentative) 4. the target address is
an anycast address assigned to the interface

In case 1, the NA is processed as described in 2461bis.

In case 2, the address is not unique and the procedure described in
Section 5.4.5 should be performed.

In case 3, the node should discard the NA and log a system management
error.  I mainly focused on this case in my (revised) proposal.

In case 4, hmm, I'm not sure whether 2462bis should specify the
behavior.  Since this case is irrelevant to unique vs duplicate, it
should be out of scope of 2462bis.  Although I'm not sure if 2461bis
clarifies that case, all we can do would be to leave this case to
2461bis, too.

Your proposed text seems to require the same processing for cases 2 and
3 (and even 4), which doesn't look correct to me - it at least looks
different from what we agreed on earlier in this thread.

So, my third proposal is to change the paragraph of Section 5.4.4
from:

    On receipt of a valid Neighbor Advertisement message on an
interface,
    node behavior depends on whether the target address is tentative or
    matches a unicast or anycast address assigned to the interface.  If
    the target address is assigned to the receiving interface, the
    solicitation is processed as described in [I-D.ietf-ipv6-2461bis].
    If the target address is tentative, the tentative address is not
    unique.

to:

    On receipt of a valid Neighbor Advertisement message on an
    interface, node behavior depends on whether the target address is
    tentative or matches a unicast or anycast address assigned to the
    interface.  If the target address is tentative, the tentative
    address is not unique.  Otherwise, if the target address matches a
    unicast address assigned to the receiving interface, the
    advertisement SHOULD be discarded and the node SHOULD log a system
    management error; this case would indicate that the address is a
    duplicate but it has not been detected by the Duplicate Address
    Detection procedure, which should be manually handled by the
    system administrator.  The advertisement is processed as described
    in [I-D.ietf-ipv6-2461bis] for all other cases.

(the additional note "this case would indicate..." may sound too
verbose.  If so, I'm willing to remove it.)

					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 Jul 06 14: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 1I6sFK-0004k4-Ld; Fri, 06 Jul 2007 14:09:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sFJ-0004jz-OO
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:09:33 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6sFF-00014m-7d
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:09: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 596567301E;
	Sat,  7 Jul 2007 03:09:28 +0900 (JST)
Date: Sat, 07 Jul 2007 03:09:23 +0900
Message-ID: <m2vecx8kvg.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB21046B02CB@xmb-rtp-20a.amer.cisco.com>
References: <468E730F.8090409@hp.com>
	<8E296595B6471A4689555D5D725EBB21046B02CB@xmb-rtp-20a.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: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 6 Jul 2007 13:00:10 -0400,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> Though putting this into a list (1., 2., 3.) would likely make it
> much more readable and parseable.

> >     On receipt of a valid Neighbor Advertisement message on an
> >     interface, node behavior depends on whether the target address is
> >     tentative or matches a unicast or anycast address assigned to the
> >     interface:
> >     1. If the target address is tentative, the tentative
> >     address is not unique.
> >     2. If the target address matches a
> >     unicast address assigned to the receiving interface, the
> >     advertisement SHOULD be discarded and the node SHOULD log a system
> >     management error; this case would indicate that the address is a
> >     duplicate but it has not been detected by the Duplicate Address
> >     Detection procedure, which should be manually handled by the
> >     system administrator.
> >     3. Otherwise, the advertisement is processed as described
> >     in [I-D.ietf-ipv6-2461bis].

I tend to agree (I also thought this as an option myself).  Thanks for
the suggestion.

					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 Jul 06 14: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 1I6sXk-00010W-9h; Fri, 06 Jul 2007 14:28:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sXh-0000zB-7g
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:28:33 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6sXd-0003d7-EH
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:28:33 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 06 Jul 2007 14:28:29 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPMljkZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,509,1175486400"; 
	d="scan'208"; a="125396345:sNHT120975642"
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 l66ISS04022749
	for <ipv6@ietf.org>; Fri, 6 Jul 2007 14:28: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 l66ISSs0026463
	for <ipv6@ietf.org>; Fri, 6 Jul 2007 18:28:28 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, 6 Jul 2007 14:28: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: Fri, 6 Jul 2007 14:28:16 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A5CC@xmb-rtp-20e.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: Ace/M8fE/g0md/DvQU2rkWOHgYk/dQABAVfgADDhvgA=
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 06 Jul 2007 18:28:17.0285 (UTC)
	FILETIME=[6BFDF350:01C7BFFB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20995; t=1183746508;
	x=1184610508; 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:=20FW=3A=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20 |To:=20<ipv6@ietf.org>;
	bh=vVmtcwVe1FhBfOHydxIR1VB8xol5Vgu7UdDTPjx7VFs=;
	b=uVkzNk4kdMup6JUvPJRKPb0AC1XXywMw+YYo6WyZPXomEeVLa31HeM5UfUQeRz/sCHoR50OR
	ccfPQCYjgIW3CgiEdtpJCMc8ozx2PNMubmftX3/ulNm7Iasi7xEATW0R;
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: b612707e1a3f67df80ae89cdab1ba981
Subject: FW: 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


-----Original Message-----
From: Hemant Singh (shemant)=20
Sent: Friday, July 06, 2007 2:21 PM
To: 'Vlad Yasevich'
Cc: ipv6@ietf.org
Subject: RE: Sending traffic to default router when RA has no PIO

Vlad,

Thanks very much for the review. Please see our responses in line below
against "<hs>".=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]
Sent: Thursday, July 05, 2007 2:39 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hi Hemant

Here is my review of your draft.  Comments are inside the <vy> </vy>
blocks. =20

-vlad

1.  Introduction

   IPv6 host data forwarding and address resolution is complex.  For
   example, RFC 2461 [ND] (section 3.1) implies that if the RA received
   by the host does not advertise any prefix, then the host must send
   all non-link-local data to the default router.  This section of the
   RFC also implies that no address resolution is to be performed in
   this case.  Sections 5.2 and 7.2.2 imply that the host performs
   address resolution before transmitting a packet if the destination of
   the packet is on the same link as the host.  Some current host
   implementations perform address resolution in all cases even when the
   destination is not clearly on-link.  However, RFC 2461 [ND] section
   6.3.4 implies that hosts must clearly determine that a destination is
   on-link before performing address resolution.

<vy>
I believe that you are reading too much into section 3.1.  That section
simply does a comparison to IPv4.  It does not mandate anything and
doesn't not specify any specific beavhior.  That is saved for later.

<hs> Totally agree with you. We want to just add a new line or two to
the relevant para in section 3.1 where the new lines say "go to a
section further down in the document for concrete details."  Note that
we simply state that this should be made explicit - but in our
introduction, we do not specify exactly how.  For more information on
how we wish to be more explicit, see the changes to 2461bis and 2462bis
sections.

One could argue that this section might have a touch more technical
information there then strictly need, but it is still not meant to
specify any requiremens.
</vy>

   These implications in RFC 2461 [ND] need to be made explicit.
   Failure of host implementations to comply can result in lack of IPv6
   connectivity.  For example, a host receives an RA with no prefix
   advertised and incorrectly decides to perform address resolution when
   the host should have sent all traffic to the default router.  The
   router may not respond to the address resolution and the layer 2
   driver of the host stops transmitting IPv6 packets.

<vy>
Are these meant to describe 2 different scenarios or just one? =20

<hs> Just one scenario. A router may not respond to the NS issued by
host to resolve the packet destination. That causes the host's L2 driver
to just sit there. The net result is no packets get out of the host.

If only one, both implementations violate multiple aspects of the
protocol.
</vy>

2.  Host Models

   A correctly implemented IPv6 host MUST adhere to the following rules:

   1.  On-link determination and address information MUST NOT persist
       across IPv6 interface initializations.

<vy>
Either you are not clear enough here, or this requirement is overly
strict.  There is nothing with having configured address information
persist acrsoss across full system or interface initializations.

I agree that on-link determination information SHOULD NOT persist, but
clever people can do some very clever things.  I think SHOULD NOT is
strong enough.
</vy>

<hs> OK, we will change MUST NOT to SHOULD NOT to allow for clever
implementations. One thought we had was that DHCPv6 clients can
certainly change address across IPv6 interface initializations - that is
what prompted us to this rule having enforced it for SLAAC clients as
well. The new bullet text follows:

"1. On-link determination SHOULD NOT persist across IPv6 interface
initializations. Note that section 5.7 of draft-ietf-ipv6-rfc2462bis-08
(Thomson, S., Narten, T., and T. Jinmei, "IPv6 Address autoconfiguration
(IPv6)," May 2005.) [ADDRCONFbis] describes the use of stable storage
for addresses acquired with stateless address autoconfiguration with a
note that the Preferred and Valid Lifetimes must be retained if this
approach is used."=20


   "2.  The RA and 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."

<vy>
You should really restrict this to other types for dynamic configuration
</vy>

<hs> We noticed this one too and have made a change to this bullet.
Please see if the new text below for this bullet makes sense to you.

---------------
   "2. The on-link definition in section 2.1 of
       draft-ietf-ipv6-2461bis-11 [NDbis] describes the only means 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.  Note
       that the on-link definition as specified by
       draft-ietf-ipv6-2461bis-11 [NDbis] does not include manual
       configuration."
-----------------

   3.  The host MUST NOT add a direct delivery route to the prefix from
       an assigned address, independent of the information about the
       prefix received from the RA or Redirects.
<vy>
Can you please explain what exactly you mean here.  I am having
difficulty properly understanding this sentence.
</vy>

<hs> In this regard, we describe the issue hosts have when hosts
incorrectly add a directly connected route to a /64 prefix from an
address assigned to an interface, even if the prefix is advertised as
"not on-link" or not advertised at all. The host incorrectly assumed a
/64 prefix length.
After assuming the prefix length, the host added a directly connected
route entry for such a prefix to the host forwarding tables. The
incorrectly added route causes the host to try to use direct delivery
(without sending traffic to the default router) and, therefore, use
NS/NA to resolve addresses from the same prefix.


   5.  The host SHOULD issue only a single NS(DAD) for each address.
       The default value for DupAddrDetectTransmits variable is
       specified as 1 in section 5.1 of RFC 2462 [ADDRCONF].

<vy>
What exactly are you trying to address with this text?  When I read it,
my first impulse is to assume that you want to limit the number of DAD
Soliciations to 1 per address, which is not really correct and is
_probably_ not what you mean.  Can you explain a little more.
</vy>

<hs> Not quite. This bullet hasn't changed in our I-D from the
definition of DupAddrDetectTransmits in 2462bis. Section 5.1 of 2462bis
clearly says default value of this variable is 1. Then the section goes
on to say the value can be overriden by a linktype specific value. That
is why we say in our I-D, the host SHOULD issue only single NS(DAD)
because the default is 1. The SHOULD also caters to any other value
being used. We found an interesting behavior in an IPv6 cable modem host
stack. The modem was sending 4 NS(DAD)'s for Link-local address and 5
NS(DAD)'s for DHCPv6 address. In the cable broadband deployment,
upstream bandwidth (direction from modem to aggregator router) is very
limited and if every modem is issuing 9 NS(DAD)'s before the modem gets
online, a lot of bandwidth is being wasted in the network. The
aggregator supports 60,000-100,000 modems and if each modem sends 9
NS(DAD)'s, it's a lot of data for the aggregator, especially during
reload of the aggregator when all the modems will try to get online
concurrently.

   6.  If the Default Router List is empty, the host MUST NOT assume
       that all destinations are on-link.  The host MUST NOT perform
       address resolution for non-link-local addresses.  The host SHOULD
       send an ICMPv6 Destination Unreachable message instead.
<vy>
No that's not correct.  The host can perform address resolution if he
has on-link prefexis.  It it permissable to have on-link prefixes
without specifying a default router (I have a private isolated network).
</vy>

<hs> Agreed. We have to make rules tighter here. Please see the new
bullet below:

----------------
    "6. Newer implementations, which are compliant with
       draft-ietf-ipv6-rfc2461bis-11 [NDbis] MUST adhere to the
       following rules.  Older implementations, which are compliant with
       RFC 2461 [ND] but not draft-ietf-ipv6-rfc2461bis-11 [NDbis] may
       remain as is.  If the Default Router List is empty and there is
       no other source of on-link information about any address or
       prefix:

       1.  The host MUST NOT assume that all destinations are on-link.

       2.  The host MUST NOT perform address resolution for non-link-
           local addresses.

       3.  The host SHOULD send an ICMPv6 Destination Unreachable
           message instead.

       On-link information concerning particular addresses and prefixes
       can make those specific addresses and prefixes on-link, but does
       not change the default behavior mentioned above for addresses and
       prefixes not specified.  draft-ietf-v6ops-onlinkassumption-04
       [I.D.ietf-v6ops-onlinkassumptions] provides justification for
       these rules."
-----------------------

2.1.  RA Sets M and O Bits but does not Include the Prefix Information
      Option (PIO)

[... draft text snipped ...]

   An IPv6 router sends an RA with no prefix advertised and the M and O
   bits set and does not send any Redirects.  On receipt of the RA, the
   host uses DHCPv6 to acquire an IPv6 address.  After completing IPv6
   address acquisition, the host MUST obey RFC 2461 [ND], section 3.1.
   Since the RA is the only authority to a host for on-link
   determination and this RA does not advertise any prefix, the host
   cannot determine that a destination is on-link.  Therefore, the host
   MUST adhere to the following rules:

   1.  The host MUST NOT assume any default prefix length.

   2.  The host MUST send all non-link-local traffic to the default
       router.

   3.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
One can argue that a host/DHCP client that inferes a prefix length from
a leased address is prone to other failures as well.  In this case, it's
the DHCP client that is most likely a problem, unless the host
implementation mistakenly alwasy assumes /64 length.  I think this is
actually warned against in the Address Architure document.

<hs> The host implementation has assumed a /64 length in the tests we
did.=20

2461bis clearly states that a set 'L' flag is the only determination of
on-link.  Anything else you can report to your vendor as "Bug".

The above actually would be a very good test to add to the TAHI
conformance test suite.
</vy>

<hs> I contacted TAHI on May 16th, 2007 to add such a test case to the
IPv6 conformance test suite. On June 19th, 2007, someone replied. I have
to work with them to make sure this test is added to their test suite.

2.2.  RA Advertises a Prefix with the On-link(L) Bit Set

[... draft text sniped ...]

   Consider the following scenario with one rogue node and two other
   hosts on the same link.  The rogue sends a malicious RA with an on-
   link prefix with a Valid Lifetime of zero.  Host1 correctly
   implements section 5.5.3 of RFC 2462 [ADDRCONF] and resets its
   StoredLifetime (or RemainingLifetime in draft-ietf-ipv6-rfc2462bis-08
   [ADDRCONFbis]) to two hours and avoids the denial of service attack.
   Host1 tries to send traffic to Host2, but cannot trust its own two
   hour StoredLifetime.  For instance, a legitimate operator may have
   tried to time out the prefix due to an impending renumbering.  Host1
   decides to send all of its traffic to the on-link authority, the
   default router, even though the destination prefix is on-link.

   IF the host decides to send all traffic (including on-link traffic)
   to the default router, then the host MUST follow the following rule:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
This is kind of reduntant.  The host can either determine that the
destination is on-link (i.e it trusts its prefix list), or it sends it
to the default router.  The only time it would preform NS would be for
on-link determination which means that it trust the prefix list.
I don't see any further need to call out this particular scenario.
</vy>

<hs> Before we added these rules, one reviewer complained that we had
rules in all the other sections, but not this one.  Therefore, we added
the rules to satisfy the reviewer.  As for the scenario, this scenario
allows a host to send all traffic to the default router even for a
prefix advertised as on-link.  This is very important if we want to
describe ALL the behavior possible with respect to on-link
determination.

2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear

   Regardless of whether the host performs DHCPv6 and/or stateless
   autoconfiguration, the host MUST adhere to the following rules for
   addresses contained within the advertised prefix:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

   2.  The host MUST send all non-link-local traffic to the default
       router.

<vy>
No.  If the host already had a on-link prefix in the list that matches
the the one with 'L' bit clear, it should not change the on-link
assumption and continue using address resolution.

If this is a new prefix with the 'L' bit clear, then 2461bis already
addresses this issue appropriatly.
</vy>

<hs> You are correct. We changed our I-D for this section - see changed
text below:

"2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear An on-link
bit of clear indicates nothing regarding on-link determination. In
section 6.3.4 of draft-ietf-ipv6-rfc2461bis-11 (Narten, T., Nordmark,
E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP Version 6
(IPv6)," March 2007.) [NDbis]":=20

"...a Prefix Information Option with on-link flag set to zero conveys no
information concerning on-link determination and MUST NOT be interpreted
to mean that addresses covered by the prefix are off-link.... Prefixes
with the on-link flag set to zero would normally have the autonomous
flag set and be used by [ADDRCONF]."=20
"


3.1.  Aggregation Router Deployment Model

   No NS to resolve any address other that that of the default router
   will reach the aggregation router from any device on the customer
   side of the aggregator.  CPEs do not communicate with each other in
   this deployment model since a CPE does not run any applications that
   need to communicate with other CPEs.  Hosts do communicate with each
   other, but every host is off-link to any other host on the
   aggregation router.

<vy>
Yes, they are off-link.  So why would they thing their are on-link?
Each CPE Rtr or Cust Rtr whould have it's own prefix that would be
advertized to the CPE hosts.  Therese prefixes would aggregate
at the Agregator.   Why would NSs from the CPE hosts escape?
</vy>

<hs. True the NS's from CPE hosts would not escape. We are just
highlighting a deployment design such that the aggregator in the
deployment will not have to support ND Proxy.

5.  Changes to draft-ietf-ipv6-rfc2461bis-11

[... old text snipped ...]

      "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.  Without
      advertised prefixes, without manual configuration, and without
      redirects, hosts MUST NOT assume a default prefix length, 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.

<vy>
No, this is the wrong section to include such requirements since the
section currenlty doesn't place any specific requirements on the
implementation.
</vy>

<hs> Agreed. We will put the strict text elsewhere in 2461bis and just
add a reference in this para to that stricter text.

6.  Changes to draft-ietf-ipv6-rfc2462bis-08

[... old text snipped ...]

   to read as follows:

      Each individual unicast address SHOULD be tested for uniqueness.
      Note that some deployed implementations perform Duplicate Address
      Detection (DAD) only for the link-local address and skip the test
      for the global address using the same interface identifier.
      Whereas this document does not invalidate such implementations,
      this kind of 'optimization' is NOT RECOMMENDED, and new
      implementations MUST NOT do that optimization.  This optimization
      came from the assumption that all of an interface's addresses are
      generated from the same interface identifier (see RFC 2462
      [ADDRCONF]).  However, even with this assumption, skipping DAD for
      non-link-local addresses with manual configuration creates an
      additional problem.  This optimization allows an interface to
      claim a duplicate address in a way that would not be detected.
      For a more detailed description of this problem, see the Host
      Models section of
      draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
      types of addresses have been introduced where the interface
      identifiers are not necessarily the same for all unicast addresses
      on a single interface [RFC3041] [RFC3972].  Requiring an interface
      to perform DAD for all unicast addresses will make the algorithm
      more robust.

<vy>
Two issues:
 1. This text is not any stronger then the existing text in 2461bis and
    doesn't add anything significant.

<hs> Yes it is. We have been told by a number of people that whether to
skip DAD or not was discussed at length in the IETF IPv6 WG and mailer.
If so much discussion happened and RFC 2462 changed in 2462bis I-D to
remove the skipping DAD requirement for newer hosts, we'd like to see
the reasons for the change. The only reason we found in 2462bis for the
change was:

      "new types of addresses have been introduced where the
      interface identifiers are not necessarily the same for all unicast
      addresses on a single interface [RFC3041] [RFC3972]."

Well, we provided an example scenario in our I-D (section 2, bullet 4)
that highlights that fact the skipping DAD combined with manual
configuration can result in duplicate addresses on the same link which
are not detected. Our new example provides an important NEW reason that
shows that even when an interface uses the same identifier for
Link-local Address and a Globally Unique Address, skipping DAD caused
failure to detect a duplicate address.  If DAD was not skipped, the
duplicate address would be detected.  That is why we wanted our new text
to be added to 2462bis.

 2. It creates a normative reference to a personal draft at a very late
    stage in the life of 2461bis.

I don't see a reason to add this text
</vy>

<hs> Because our I-D came in very late, when 2462bis was in AUTH48
state, we can remove the reference from the modified paragraph above.
However, we would still like our new sentences to be added.  If more
explanation is needed (to compensate for the removed reference), we can
certainly write one.

My conlcusion:

After re-reading 2461bis and 2462bis multiple times as result of
reviewing this draft, I can see some small value in creating an "On-Link
Determination"
section in draft 2461bis.

Alternatively, this draft should crate such section and, with references
to text in 2461bis, should clarify the on-link determination behavior.
It could then be issued as an update.

<hs> We are preparing text with regards to additional changes to 2461bis
to add to Section 5 of our I-D.  We're glad that you agree that on-link
determination as described by the current specifications can be
confusing.

Regards.

- Hemant & Wes

-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 Jul 06 14: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 1I6sb7-0001xw-Qb; Fri, 06 Jul 2007 14:32:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6sQs-0007CM-T6
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:21:31 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6sQk-0004UG-DG
	for ipv6@ietf.org; Fri, 06 Jul 2007 14:21:30 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 06 Jul 2007 14:21:08 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAK8kjkZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,509,1175486400"; 
	d="scan'208"; a="125395622:sNHT30957984670"
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 l66IL8b4019547; 
	Fri, 6 Jul 2007 14:21:08 -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 l66IL3s2023286; 
	Fri, 6 Jul 2007 18:21:08 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, 6 Jul 2007 14:21:04 -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, 6 Jul 2007 14:21:03 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <11836607373870-git-send-email-vladislav.yasevich@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: Ace/M8fE/g0md/DvQU2rkWOHgYk/dQABAVfg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 06 Jul 2007 18:21:04.0293 (UTC)
	FILETIME=[69E89D50:01C7BFFA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=20789; t=1183746068;
	x=1184610068; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=/roQL4jyMZRZsSJblhXWnd6dPdtqy/FX2ZNc7brhSao=;
	b=Zrdylr9n35jr3yntt0wivBQvS4tBXlgF/L0KGWKgWZFlzMQyskpDRqpVJE1A+PU1jbfIYMoU
	SHUFA9O1uBN1ov029b6KKyExwNaOi+BqQORX5OTiW53aqjPAC275re76;
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: 4d9aaf4f837d0910b987cb9188300fdd
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

Vlad,

Thanks very much for the review. Please see our responses in line below
against "<hs>".=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Thursday, July 05, 2007 2:39 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hi Hemant

Here is my review of your draft.  Comments are inside the <vy> </vy>
blocks. =20

-vlad

1.  Introduction

   IPv6 host data forwarding and address resolution is complex.  For
   example, RFC 2461 [ND] (section 3.1) implies that if the RA received
   by the host does not advertise any prefix, then the host must send
   all non-link-local data to the default router.  This section of the
   RFC also implies that no address resolution is to be performed in
   this case.  Sections 5.2 and 7.2.2 imply that the host performs
   address resolution before transmitting a packet if the destination of
   the packet is on the same link as the host.  Some current host
   implementations perform address resolution in all cases even when the
   destination is not clearly on-link.  However, RFC 2461 [ND] section
   6.3.4 implies that hosts must clearly determine that a destination is
   on-link before performing address resolution.

<vy>
I believe that you are reading too much into section 3.1.  That section
simply does a comparison to IPv4.  It does not mandate anything and
doesn't not specify any specific beavhior.  That is saved for later.

<hs> Totally agree with you. We want to just add a new line or two to
the relevant para in section 3.1 where the new lines say "go to a
section further down in the document for concrete details."  Note that
we simply state that this should be made explicit - but in our
introduction, we do not specify exactly how.  For more information on
how we wish to be more explicit, see the changes to 2461bis and 2462bis
sections.

One could argue that this section might have a touch more technical
information there then strictly need, but it is still not meant to
specify any requiremens.
</vy>

   These implications in RFC 2461 [ND] need to be made explicit.
   Failure of host implementations to comply can result in lack of IPv6
   connectivity.  For example, a host receives an RA with no prefix
   advertised and incorrectly decides to perform address resolution when
   the host should have sent all traffic to the default router.  The
   router may not respond to the address resolution and the layer 2
   driver of the host stops transmitting IPv6 packets.

<vy>
Are these meant to describe 2 different scenarios or just one? =20

<hs> Just one scenario. A router may not respond to the NS issued by
host to resolve the packet destination. That causes the host's L2 driver
to just sit there. The net result is no packets get out of the host.

If only one, both implementations violate multiple aspects of the
protocol.
</vy>

2.  Host Models

   A correctly implemented IPv6 host MUST adhere to the following rules:

   1.  On-link determination and address information MUST NOT persist
       across IPv6 interface initializations.

<vy>
Either you are not clear enough here, or this requirement is overly
strict.  There is nothing with having configured address information
persist acrsoss across full system or interface initializations.

I agree that on-link determination information SHOULD NOT persist, but
clever people can do some very clever things.  I think SHOULD NOT is
strong enough.
</vy>

<hs> OK, we will change MUST NOT to SHOULD NOT to allow for clever
implementations. One thought we had was that DHCPv6 clients can
certainly change address across IPv6 interface initializations - that is
what prompted us to this rule having enforced it for SLAAC clients as
well. The new bullet text follows:

"1. On-link determination SHOULD NOT persist across IPv6 interface
initializations. Note that section 5.7 of draft-ietf-ipv6-rfc2462bis-08
(Thomson, S., Narten, T., and T. Jinmei, "IPv6 Address autoconfiguration
(IPv6)," May 2005.) [ADDRCONFbis] describes the use of stable storage
for addresses acquired with stateless address autoconfiguration with a
note that the Preferred and Valid Lifetimes must be retained if this
approach is used."=20


   "2.  The RA and 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."

<vy>
You should really restrict this to other types for dynamic configuration
</vy>

<hs> We noticed this one too and have made a change to this bullet.
Please see if the new text below for this bullet makes sense to you.

---------------
   "2. The on-link definition in section 2.1 of
       draft-ietf-ipv6-2461bis-11 [NDbis] describes the only means 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.  Note
       that the on-link definition as specified by
       draft-ietf-ipv6-2461bis-11 [NDbis] does not include manual
       configuration."
-----------------

   3.  The host MUST NOT add a direct delivery route to the prefix from
       an assigned address, independent of the information about the
       prefix received from the RA or Redirects.
<vy>
Can you please explain what exactly you mean here.  I am having
difficulty properly understanding this sentence.
</vy>

<hs> In this regard, we describe the issue hosts have when hosts
incorrectly add a directly connected route to a /64 prefix from an
address assigned to an interface, even if the prefix is advertised as
"not on-link" or not advertised at all. The host incorrectly assumed a
/64 prefix length.
After assuming the prefix length, the host added a directly connected
route entry for such a prefix to the host forwarding tables. The
incorrectly added route causes the host to try to use direct delivery
(without sending traffic to the default router) and, therefore, use
NS/NA to resolve addresses from the same prefix.


   5.  The host SHOULD issue only a single NS(DAD) for each address.
       The default value for DupAddrDetectTransmits variable is
       specified as 1 in section 5.1 of RFC 2462 [ADDRCONF].

<vy>
What exactly are you trying to address with this text?  When I read it,
my first impulse is to assume that you want to limit the number of DAD
Soliciations to 1 per address, which is not really correct and is
_probably_ not what you mean.  Can you explain a little more.
</vy>

<hs> Not quite. This bullet hasn't changed in our I-D from the
definition of DupAddrDetectTransmits in 2462bis. Section 5.1 of 2462bis
clearly says default value of this variable is 1. Then the section goes
on to say the value can be overriden by a linktype specific value. That
is why we say in our I-D, the host SHOULD issue only single NS(DAD)
because the default is 1. The SHOULD also caters to any other value
being used. We found an interesting behavior in an IPv6 cable modem host
stack. The modem was sending 4 NS(DAD)'s for Link-local address and 5
NS(DAD)'s for DHCPv6 address. In the cable broadband deployment,
upstream bandwidth (direction from modem to aggregator router) is very
limited and if every modem is issuing 9 NS(DAD)'s before the modem gets
online, a lot of bandwidth is being wasted in the network. The
aggregator supports 60,000-100,000 modems and if each modem sends 9
NS(DAD)'s, it's a lot of data for the aggregator, especially during
reload of the aggregator when all the modems will try to get online
concurrently.

   6.  If the Default Router List is empty, the host MUST NOT assume
       that all destinations are on-link.  The host MUST NOT perform
       address resolution for non-link-local addresses.  The host SHOULD
       send an ICMPv6 Destination Unreachable message instead.
<vy>
No that's not correct.  The host can perform address resolution if he
has on-link prefexis.  It it permissable to have on-link prefixes
without specifying a default router (I have a private isolated network).
</vy>

<hs> Agreed. We have to make rules tighter here. Please see the new
bullet below:

----------------
    "6. Newer implementations, which are compliant with
       draft-ietf-ipv6-rfc2461bis-11 [NDbis] MUST adhere to the
       following rules.  Older implementations, which are compliant with
       RFC 2461 [ND] but not draft-ietf-ipv6-rfc2461bis-11 [NDbis] may
       remain as is.  If the Default Router List is empty and there is
       no other source of on-link information about any address or
       prefix:

       1.  The host MUST NOT assume that all destinations are on-link.

       2.  The host MUST NOT perform address resolution for non-link-
           local addresses.

       3.  The host SHOULD send an ICMPv6 Destination Unreachable
           message instead.

       On-link information concerning particular addresses and prefixes
       can make those specific addresses and prefixes on-link, but does
       not change the default behavior mentioned above for addresses and
       prefixes not specified.  draft-ietf-v6ops-onlinkassumption-04
       [I.D.ietf-v6ops-onlinkassumptions] provides justification for
       these rules."
-----------------------

2.1.  RA Sets M and O Bits but does not Include the Prefix Information
      Option (PIO)

[... draft text snipped ...]

   An IPv6 router sends an RA with no prefix advertised and the M and O
   bits set and does not send any Redirects.  On receipt of the RA, the
   host uses DHCPv6 to acquire an IPv6 address.  After completing IPv6
   address acquisition, the host MUST obey RFC 2461 [ND], section 3.1.
   Since the RA is the only authority to a host for on-link
   determination and this RA does not advertise any prefix, the host
   cannot determine that a destination is on-link.  Therefore, the host
   MUST adhere to the following rules:

   1.  The host MUST NOT assume any default prefix length.

   2.  The host MUST send all non-link-local traffic to the default
       router.

   3.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
One can argue that a host/DHCP client that inferes a prefix length from
a leased address is prone to other failures as well.  In this case, it's
the DHCP client that is most likely a problem, unless the host
implementation mistakenly alwasy assumes /64 length.  I think this is
actually warned against in the Address Architure document.

<hs> The host implementation has assumed a /64 length in the tests we
did.=20

2461bis clearly states that a set 'L' flag is the only determination of
on-link.  Anything else you can report to your vendor as "Bug".

The above actually would be a very good test to add to the TAHI
conformance test suite.
</vy>

<hs> I contacted TAHI on May 16th, 2007 to add such a test case to the
IPv6 conformance test suite. On June 19th, 2007, someone replied. I have
to work with them to make sure this test is added to their test suite.

2.2.  RA Advertises a Prefix with the On-link(L) Bit Set

[... draft text sniped ...]

   Consider the following scenario with one rogue node and two other
   hosts on the same link.  The rogue sends a malicious RA with an on-
   link prefix with a Valid Lifetime of zero.  Host1 correctly
   implements section 5.5.3 of RFC 2462 [ADDRCONF] and resets its
   StoredLifetime (or RemainingLifetime in draft-ietf-ipv6-rfc2462bis-08
   [ADDRCONFbis]) to two hours and avoids the denial of service attack.
   Host1 tries to send traffic to Host2, but cannot trust its own two
   hour StoredLifetime.  For instance, a legitimate operator may have
   tried to time out the prefix due to an impending renumbering.  Host1
   decides to send all of its traffic to the on-link authority, the
   default router, even though the destination prefix is on-link.

   IF the host decides to send all traffic (including on-link traffic)
   to the default router, then the host MUST follow the following rule:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

<vy>
This is kind of reduntant.  The host can either determine that the
destination is on-link (i.e it trusts its prefix list), or it sends it
to the default router.  The only time it would preform NS would be for
on-link determination which means that it trust the prefix list.
I don't see any further need to call out this particular scenario.
</vy>

<hs> Before we added these rules, one reviewer complained that we had
rules in all the other sections, but not this one.  Therefore, we added
the rules to satisfy the reviewer.  As for the scenario, this scenario
allows a host to send all traffic to the default router even for a
prefix advertised as on-link.  This is very important if we want to
describe ALL the behavior possible with respect to on-link
determination.

2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear

   Regardless of whether the host performs DHCPv6 and/or stateless
   autoconfiguration, the host MUST adhere to the following rules for
   addresses contained within the advertised prefix:

   1.  The host MUST NOT issue an NS to resolve a destination other than
       a link-local address.

   2.  The host MUST send all non-link-local traffic to the default
       router.

<vy>
No.  If the host already had a on-link prefix in the list that matches
the the one with 'L' bit clear, it should not change the on-link
assumption and continue using address resolution.

If this is a new prefix with the 'L' bit clear, then 2461bis already
addresses this issue appropriatly.
</vy>

<hs> You are correct. We changed our I-D for this section - see changed
text below:

"2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear
An on-link bit of clear indicates nothing regarding on-link
determination. In section 6.3.4 of draft-ietf-ipv6-rfc2461bis-11
(Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor
Discovery for IP Version 6 (IPv6)," March 2007.) [NDbis]":=20

"...a Prefix Information Option with on-link flag set to zero conveys no
information concerning on-link determination and MUST NOT be interpreted
to mean that addresses covered by the prefix are off-link.... Prefixes
with the on-link flag set to zero would normally have the autonomous
flag set and be used by [ADDRCONF]."=20
"


3.1.  Aggregation Router Deployment Model

   No NS to resolve any address other that that of the default router
   will reach the aggregation router from any device on the customer
   side of the aggregator.  CPEs do not communicate with each other in
   this deployment model since a CPE does not run any applications that
   need to communicate with other CPEs.  Hosts do communicate with each
   other, but every host is off-link to any other host on the
   aggregation router.

<vy>
Yes, they are off-link.  So why would they thing their are on-link?
Each CPE Rtr or Cust Rtr whould have it's own prefix that would be
advertized to the CPE hosts.  Therese prefixes would aggregate
at the Agregator.   Why would NSs from the CPE hosts escape?
</vy>

<hs. True the NS's from CPE hosts would not escape. We are just
highlighting a deployment design such that the aggregator in the
deployment will not have to support ND Proxy.

5.  Changes to draft-ietf-ipv6-rfc2461bis-11

[... old text snipped ...]

      "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.  Without
      advertised prefixes, without manual configuration, and without
      redirects, hosts MUST NOT assume a default prefix length, 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.

<vy>
No, this is the wrong section to include such requirements since the
section currenlty doesn't place any specific requirements on the
implementation.
</vy>

<hs> Agreed. We will put the strict text elsewhere in 2461bis and just
add a reference in this para to that stricter text.

6.  Changes to draft-ietf-ipv6-rfc2462bis-08

[... old text snipped ...]

   to read as follows:

      Each individual unicast address SHOULD be tested for uniqueness.
      Note that some deployed implementations perform Duplicate Address
      Detection (DAD) only for the link-local address and skip the test
      for the global address using the same interface identifier.
      Whereas this document does not invalidate such implementations,
      this kind of 'optimization' is NOT RECOMMENDED, and new
      implementations MUST NOT do that optimization.  This optimization
      came from the assumption that all of an interface's addresses are
      generated from the same interface identifier (see RFC 2462
      [ADDRCONF]).  However, even with this assumption, skipping DAD for
      non-link-local addresses with manual configuration creates an
      additional problem.  This optimization allows an interface to
      claim a duplicate address in a way that would not be detected.
      For a more detailed description of this problem, see the Host
      Models section of
      draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
      types of addresses have been introduced where the interface
      identifiers are not necessarily the same for all unicast addresses
      on a single interface [RFC3041] [RFC3972].  Requiring an interface
      to perform DAD for all unicast addresses will make the algorithm
      more robust.

<vy>
Two issues:
 1. This text is not any stronger then the existing text in 2461bis and
    doesn't add anything significant.

<hs> Yes it is. We have been told by a number of people that whether to
skip DAD or not was discussed at length in the IETF IPv6 WG and mailer.
If so much discussion happened and RFC 2462 changed in 2462bis I-D to
remove the skipping DAD requirement for newer hosts, we'd like to see
the reasons for the change. The only reason we found in 2462bis for the
change was:

      "new types of addresses have been introduced where the
      interface identifiers are not necessarily the same for all unicast
      addresses on a single interface [RFC3041] [RFC3972]."

Well, we provided an example scenario in our I-D (section 2, bullet 4)
that highlights that fact the skipping DAD combined with manual
configuration can result in duplicate addresses on the same link which
are not detected. Our new example provides an important NEW reason that
shows that even when an interface uses the same identifier for
Link-local Address and a Globally Unique Address, skipping DAD caused
failure to detect a duplicate address.  If DAD was not skipped, the
duplicate address would be detected.  That is why we wanted our new text
to be added to 2462bis.

 2. It creates a normative reference to a personal draft at a very late
    stage in the life of 2461bis.

I don't see a reason to add this text
</vy>

<hs> Because our I-D came in very late, when 2462bis was in AUTH48
state, we can remove the reference from the modified paragraph above.
However, we would still like our new sentences to be added.  If more
explanation is needed (to compensate for the removed reference), we can
certainly write one.

My conlcusion:

After re-reading 2461bis and 2462bis multiple times as result of
reviewing this draft, I can see some small value in creating an "On-Link
Determination"
section in draft 2461bis.

Alternatively, this draft should crate such section and, with references
to text in 2461bis, should clarify the on-link determination behavior.
It could then be issued as an update.

<hs> We are preparing text with regards to additional changes to 2461bis
to add to Section 5 of our I-D.  We're glad that you agree that on-link
determination as described by the current specifications can be
confusing.

Regards.

- Hemant & Wes

-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 Jul 06 15:41: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 1I6tgH-0005pj-8x; Fri, 06 Jul 2007 15:41:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6tgF-0005pc-Ja
	for ipv6@ietf.org; Fri, 06 Jul 2007 15:41:27 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6tgB-0007GU-8L
	for ipv6@ietf.org; Fri, 06 Jul 2007 15:41:27 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id E48CE37FF3;
	Fri,  6 Jul 2007 15:32:40 -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 37BB818C7D8;
	Fri,  6 Jul 2007 19:32:40 +0000 (UTC)
Message-ID: <468E98D7.5060109@hp.com>
Date: Fri, 06 Jul 2007 15:32:39 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.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: 819069d28e3cfe534e22b502261ce83f
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

Hi Hemant

Hemant Singh (shemant) wrote:
> Vlad,
> 
> <vy>
> I believe that you are reading too much into section 3.1.  That section
> simply does a comparison to IPv4.  It does not mandate anything and
> doesn't not specify any specific beavhior.  That is saved for later.
> 
> <hs> Totally agree with you. We want to just add a new line or two to
> the relevant para in section 3.1 where the new lines say "go to a
> section further down in the document for concrete details."  Note that
> we simply state that this should be made explicit - but in our
> introduction, we do not specify exactly how.  For more information on
> how we wish to be more explicit, see the changes to 2461bis and 2462bis
> sections.

OK.

> > </vy>
> 
>    These implications in RFC 2461 [ND] need to be made explicit.
>    Failure of host implementations to comply can result in lack of IPv6
>    connectivity.  For example, a host receives an RA with no prefix
>    advertised and incorrectly decides to perform address resolution when
>    the host should have sent all traffic to the default router.  The
>    router may not respond to the address resolution and the layer 2
>    driver of the host stops transmitting IPv6 packets.
> 
> <vy>
> Are these meant to describe 2 different scenarios or just one?  
> 
> <hs> Just one scenario. A router may not respond to the NS issued by
> host to resolve the packet destination. That causes the host's L2 driver
> to just sit there. The net result is no packets get out of the host.

As I said bellow, both implementation violate the specs.  At this point,
not sure if clarifying the spec by placing additional restrictions is
useful.  Submitting bugs against the implementation is probably better.

> 
> If only one, both implementations violate multiple aspects of the
> protocol.
> </vy>
> <hs> OK, we will change MUST NOT to SHOULD NOT to allow for clever
> implementations. One thought we had was that DHCPv6 clients can
> certainly change address across IPv6 interface initializations - that is
> what prompted us to this rule having enforced it for SLAAC clients as
> well. The new bullet text follows:
> 
> "1. On-link determination SHOULD NOT persist across IPv6 interface
"On-link determination state SHOULD NOT persist..."

Makes it a little more clear what you are saying.  Otherwise, looks fine
to me.


> <hs> We noticed this one too and have made a change to this bullet.
> Please see if the new text below for this bullet makes sense to you.
> 
> ---------------
>    "2. The on-link definition in section 2.1 of
>        draft-ietf-ipv6-2461bis-11 [NDbis] describes the only means 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.  Note
>        that the on-link definition as specified by
>        draft-ietf-ipv6-2461bis-11 [NDbis] does not include manual
>        configuration."
> -----------------

OK.

> 
>    3.  The host MUST NOT add a direct delivery route to the prefix from
>        an assigned address, independent of the information about the
>        prefix received from the RA or Redirects.
> <vy>
> Can you please explain what exactly you mean here.  I am having
> difficulty properly understanding this sentence.
> </vy>
> 
> <hs> In this regard, we describe the issue hosts have when hosts
> incorrectly add a directly connected route to a /64 prefix from an
> address assigned to an interface, even if the prefix is advertised as
> "not on-link" or not advertised at all. The host incorrectly assumed a
> /64 prefix length.
> After assuming the prefix length, the host added a directly connected
> route entry for such a prefix to the host forwarding tables. The
> incorrectly added route causes the host to try to use direct delivery
> (without sending traffic to the default router) and, therefore, use
> NS/NA to resolve addresses from the same prefix.

So, here the implementor completely disregarded either the section about
the L-bit being 0 doesn't mean off-link, or the section at the top of page
19 of 2462bis to not expect all IIDs to be 64 bit and thus assume a 64 bit
prefix.

I guess a final "On-Link Determination" section might help.

However, these types of errors are typical of the manual configuration
and there is not much we can do here.

> 
> 
>    5.  The host SHOULD issue only a single NS(DAD) for each address.
>        The default value for DupAddrDetectTransmits variable is
>        specified as 1 in section 5.1 of RFC 2462 [ADDRCONF].
> 
> <vy>
> What exactly are you trying to address with this text?  When I read it,
> my first impulse is to assume that you want to limit the number of DAD
> Soliciations to 1 per address, which is not really correct and is
> _probably_ not what you mean.  Can you explain a little more.
> </vy>
> 
> <hs> Not quite. This bullet hasn't changed in our I-D from the
> definition of DupAddrDetectTransmits in 2462bis. Section 5.1 of 2462bis
> clearly says default value of this variable is 1. Then the section goes
> on to say the value can be overriden by a linktype specific value. That
> is why we say in our I-D, the host SHOULD issue only single NS(DAD)
> because the default is 1. The SHOULD also caters to any other value
> being used. We found an interesting behavior in an IPv6 cable modem host
> stack. The modem was sending 4 NS(DAD)'s for Link-local address and 5
> NS(DAD)'s for DHCPv6 address.

REALLY???  Unless the mode was explicitly configured to do this, I don't see
how the text you recommend would fix this glaring error...  In fact,
I could claim that this behavior would still be within spec if the manufacturer
or operator determines that they want this behavior.

So the new text you are introducing would be completely nullified.

> 
> <hs> Agreed. We have to make rules tighter here. Please see the new
> bullet below:
> 
> ----------------
>     "6. Newer implementations, which are compliant with
>        draft-ietf-ipv6-rfc2461bis-11 [NDbis] MUST adhere to the
>        following rules.  Older implementations, which are compliant with
>        RFC 2461 [ND] but not draft-ietf-ipv6-rfc2461bis-11 [NDbis] may
>        remain as is.  If the Default Router List is empty and there is
>        no other source of on-link information about any address or
>        prefix:
> 
>        1.  The host MUST NOT assume that all destinations are on-link.
> 
>        2.  The host MUST NOT perform address resolution for non-link-
>            local addresses.
> 
>        3.  The host SHOULD send an ICMPv6 Destination Unreachable
>            message instead.
> 
>        On-link information concerning particular addresses and prefixes
>        can make those specific addresses and prefixes on-link, but does
>        not change the default behavior mentioned above for addresses and
>        prefixes not specified.  draft-ietf-v6ops-onlinkassumption-04
>        [I.D.ietf-v6ops-onlinkassumptions] provides justification for
>        these rules."
> -----------------------

Ok, the text is clearer, but it reads like an over-specification to me.

So many of the issues that you've found have to do with improper implementation
of on-link determination that I am really starting to thing that a single
section on clarifying it would be useful in your daft.

> 
> 2.1.  RA Sets M and O Bits but does not Include the Prefix Information
>       Option (PIO)
> 
> [... draft text snipped ...]
> 
>    An IPv6 router sends an RA with no prefix advertised and the M and O
>    bits set and does not send any Redirects.  On receipt of the RA, the
>    host uses DHCPv6 to acquire an IPv6 address.  After completing IPv6
>    address acquisition, the host MUST obey RFC 2461 [ND], section 3.1.
>    Since the RA is the only authority to a host for on-link
>    determination and this RA does not advertise any prefix, the host
>    cannot determine that a destination is on-link.  Therefore, the host
>    MUST adhere to the following rules:
> 
>    1.  The host MUST NOT assume any default prefix length.
> 
>    2.  The host MUST send all non-link-local traffic to the default
>        router.
> 
>    3.  The host MUST NOT issue an NS to resolve a destination other than
>        a link-local address.
> 
> <vy>
> One can argue that a host/DHCP client that inferes a prefix length from
> a leased address is prone to other failures as well.  In this case, it's
> the DHCP client that is most likely a problem, unless the host
> implementation mistakenly alwasy assumes /64 length.  I think this is
> actually warned against in the Address Architure document.
> 
> <hs> The host implementation has assumed a /64 length in the tests we
> did. 

Yes, and 2462bis weasel words around this issue at the top of page 19.
Maybe a "should" there needs to be changed to a "SHOULD"?

> 
> 2461bis clearly states that a set 'L' flag is the only determination of
> on-link.  Anything else you can report to your vendor as "Bug".
> 
> The above actually would be a very good test to add to the TAHI
> conformance test suite.
> </vy>
> 
> <hs> I contacted TAHI on May 16th, 2007 to add such a test case to the
> IPv6 conformance test suite. On June 19th, 2007, someone replied. I have
> to work with them to make sure this test is added to their test suite.

OK.  That would be good.

> 
> 2.2.  RA Advertises a Prefix with the On-link(L) Bit Set
> 
> [... draft text sniped ...]
> 
>    Consider the following scenario with one rogue node and two other
>    hosts on the same link.  The rogue sends a malicious RA with an on-
>    link prefix with a Valid Lifetime of zero.  Host1 correctly
>    implements section 5.5.3 of RFC 2462 [ADDRCONF] and resets its
>    StoredLifetime (or RemainingLifetime in draft-ietf-ipv6-rfc2462bis-08
>    [ADDRCONFbis]) to two hours and avoids the denial of service attack.
>    Host1 tries to send traffic to Host2, but cannot trust its own two
>    hour StoredLifetime.  For instance, a legitimate operator may have
>    tried to time out the prefix due to an impending renumbering.  Host1
>    decides to send all of its traffic to the on-link authority, the
>    default router, even though the destination prefix is on-link.
> 
>    IF the host decides to send all traffic (including on-link traffic)
>    to the default router, then the host MUST follow the following rule:
> 
>    1.  The host MUST NOT issue an NS to resolve a destination other than
>        a link-local address.
> 
> <vy>
> This is kind of reduntant.  The host can either determine that the
> destination is on-link (i.e it trusts its prefix list), or it sends it
> to the default router.  The only time it would preform NS would be for
> on-link determination which means that it trust the prefix list.
> I don't see any further need to call out this particular scenario.
> </vy>
> 
> <hs> Before we added these rules, one reviewer complained that we had
> rules in all the other sections, but not this one.  Therefore, we added
> the rules to satisfy the reviewer.  As for the scenario, this scenario
> allows a host to send all traffic to the default router even for a
> prefix advertised as on-link.  This is very important if we want to
> describe ALL the behavior possible with respect to on-link
> determination.

OK.

> 
> 2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear

> <hs> You are correct. We changed our I-D for this section - see changed
> text below:
> 
> "2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear
> An on-link bit of clear indicates nothing regarding on-link
> determination. In section 6.3.4 of draft-ietf-ipv6-rfc2461bis-11
> (Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor
> Discovery for IP Version 6 (IPv6)," March 2007.) [NDbis]": 
> 
> "...a Prefix Information Option with on-link flag set to zero conveys no
> information concerning on-link determination and MUST NOT be interpreted
> to mean that addresses covered by the prefix are off-link.... Prefixes
> with the on-link flag set to zero would normally have the autonomous
> flag set and be used by [ADDRCONF]." 
> "

OK.

> 
> 
> 3.1.  Aggregation Router Deployment Model
> 
>    No NS to resolve any address other that that of the default router
>    will reach the aggregation router from any device on the customer
>    side of the aggregator.  CPEs do not communicate with each other in
>    this deployment model since a CPE does not run any applications that
>    need to communicate with other CPEs.  Hosts do communicate with each
>    other, but every host is off-link to any other host on the
>    aggregation router.
> 
> <vy>
> Yes, they are off-link.  So why would they thing their are on-link?
> Each CPE Rtr or Cust Rtr whould have it's own prefix that would be
> advertized to the CPE hosts.  Therese prefixes would aggregate
> at the Agregator.   Why would NSs from the CPE hosts escape?
> </vy>
> 
> <hs. True the NS's from CPE hosts would not escape. We are just
> highlighting a deployment design such that the aggregator in the
> deployment will not have to support ND Proxy.

OK.  But you are going about it by using keyword language (use of SHOULD in
that section).  It just felt odd.  I had to re-read the section a few
times and just couldn't understand the point.  It seemed obvious.

> 
> 5.  Changes to draft-ietf-ipv6-rfc2461bis-11
> 
> <vy>
> No, this is the wrong section to include such requirements since the
> section currenlty doesn't place any specific requirements on the
> implementation.
> </vy>
> 
> <hs> Agreed. We will put the strict text elsewhere in 2461bis and just
> add a reference in this para to that stricter text.

Yes, this is the same as the first issue.  References are always better. :)

> 
> 6.  Changes to draft-ietf-ipv6-rfc2462bis-08
> 
> [... old text snipped ...]
> 
>    to read as follows:
> 
>       Each individual unicast address SHOULD be tested for uniqueness.
>       Note that some deployed implementations perform Duplicate Address
>       Detection (DAD) only for the link-local address and skip the test
>       for the global address using the same interface identifier.
>       Whereas this document does not invalidate such implementations,
>       this kind of 'optimization' is NOT RECOMMENDED, and new
>       implementations MUST NOT do that optimization.  This optimization
>       came from the assumption that all of an interface's addresses are
>       generated from the same interface identifier (see RFC 2462
>       [ADDRCONF]).  However, even with this assumption, skipping DAD for
>       non-link-local addresses with manual configuration creates an
>       additional problem.  This optimization allows an interface to
>       claim a duplicate address in a way that would not be detected.
>       For a more detailed description of this problem, see the Host
>       Models section of
>       draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
>       types of addresses have been introduced where the interface
>       identifiers are not necessarily the same for all unicast addresses
>       on a single interface [RFC3041] [RFC3972].  Requiring an interface
>       to perform DAD for all unicast addresses will make the algorithm
>       more robust.
> 
> <vy>
> Two issues:
>  1. This text is not any stronger then the existing text in 2461bis and
>     doesn't add anything significant.
> 
> <hs> Yes it is. We have been told by a number of people that whether to
> skip DAD or not was discussed at length in the IETF IPv6 WG and mailer.
> If so much discussion happened and RFC 2462 changed in 2462bis I-D to
> remove the skipping DAD requirement for newer hosts, we'd like to see
> the reasons for the change. The only reason we found in 2462bis for the
> change was:
> 
>       "new types of addresses have been introduced where the
>       interface identifiers are not necessarily the same for all unicast
>       addresses on a single interface [RFC3041] [RFC3972]."
> 
> Well, we provided an example scenario in our I-D (section 2, bullet 4)
> that highlights that fact the skipping DAD combined with manual
> configuration can result in duplicate addresses on the same link which
> are not detected. 

The example you provide has been documented in the Neighbor Discover Threats
spec (rfc 3756).  So that's documented fairly well.  The Security Consideration
section also references it and points out issues with DAD.

The only thing that _might_ be missing is a reference to such threats from
withing the DAD section, as additional rational for not skipping DAD, but that's
fairly weak.

> 
> My conlcusion:
> 
> After re-reading 2461bis and 2462bis multiple times as result of
> reviewing this draft, I can see some small value in creating an "On-Link
> Determination"
> section in draft 2461bis.
> 
> Alternatively, this draft should crate such section and, with references
> to text in 2461bis, should clarify the on-link determination behavior.
> It could then be issued as an update.
> 
> <hs> We are preparing text with regards to additional changes to 2461bis
> to add to Section 5 of our I-D.  We're glad that you agree that on-link
> determination as described by the current specifications can be
> confusing.
> 

One thing I've noted is that you have the _same_rules_ in almost every section.
What I am proposing is that you restructure the text a little.

In each section describe some inconsistencies or behaviors that you've seen
as non-compliant.  Don't add rules to each section.  Instead have one
section where you clarify the behavior using requirement keywords.  Since
most issues are centered around on-link determination, that should be
fairly easy.

-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 Jul 06 16:12: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 1I6u9p-0007qA-RR; Fri, 06 Jul 2007 16:12:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6u9o-0007q4-HP
	for ipv6@ietf.org; Fri, 06 Jul 2007 16:12:00 -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 1I6u9k-0001qA-3Q
	for ipv6@ietf.org; Fri, 06 Jul 2007 16:12:00 -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 l66KBpnC028345;
	Fri, 6 Jul 2007 13:11:52 -0700
Message-ID: <02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Brian E Carpenter" <brian.e.carpenter@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><27414.1183131210@sa.vix.com>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>	<468C481A.1010405@coders.net>	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
	<468DF387.5000400@gmail.com>
Date: Fri, 6 Jul 2007 14:41:02 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
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: 0fa76816851382eb71b0a882ccdc29ac
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

Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> On 2007-07-06 02:59, Stephen Sprunk wrote:
>> Why would you ever change PI space?  The issue is changing PA
>> space, and that's something that may need to be done every few
>> weeks as upstream links go up and down.
>
> Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
> If you drop or add an ISP you drop or add a prefix in a planned manner.
> RFC 4192.

When my link to one of those three ISPs goes down, I have a 1/3 chance of 
each outbound connection failing because the return path is broken (or my 
other two upstreams do uRPF).  I also have a 1/3 chance of each inbound 
connection failing until I update DNS to remove the relevant AAAA records; 
smarter clients will try multiple addresses for inbound connections, but 
there'll be a delay and not all clients are that smart.

The alternative is to renumber the entire network every time a link goes up 
or down.

>> Compare to the cost of a NAT box and the choice is easy.
>
> That's true if you don't put the indirect operational and user
> costs of NAT, plus the opportunity cost of innovation blocked
> by NAT, into the equation.

Most of the operational and innovation costs of NAT are also present with a 
stateful firewall, which any sane organization will be using, because it's 
really the stateful inspection that burns you.

> It *is* hard to get this into the budget unless you think strategically,
> and factor in the way IPv6 is designed to handle multiple PA prefixes
> simultaneously.

When presented with the choice between a paradigm shift and continuing along 
the present path, most people will pick the latter.  In this case, that 
means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.

>>> If your choices are PI vs PA then yeah NAT does look very attractive, 
>>> but if you can have PA and "private"-PI (aka ULA) then things look a lot 
>>> less blurred (IMHO).
>>
>> IMHO, you underestimate how much IT folks hate renumbering.
>
> They hate renumbering IPv4 networks. I do too, having managed such an
> operation a couple of times. It's as a result of that hatred that
> IPv6 came out as it is, making RFC 4192 possible.

Again, RFC 4192 ignores all of the non-technical aspects of renumbering. 
That's probably appropriate, given the IETF's domain, but it's only a tiny 
part of what must be done.  Changing the address on an interface takes a few 
seconds; the change control processes leading up to it can burn months of 
manpower.

You might convince me that if you do it frequently enough, the cost will be 
low, but I don't want to work anywhere that renumbers often enough to be 
good at it.  That reminds me of a scene in _Broken Arrow_ where a character 
comments he doesn't know whether to be more scared that they lost a nuclear 
weapon or that it happens often enough the military has a name for it.

> This is *not* to say that anyone will renumber weekly, and big networks
> will avoid it (and are therefore candidates for PI). But for smaller
> networks, the hatred should be substantially less, and balance the hatred
> of NAT.

It's the smaller folks that can't get PI that hate NAT the least, because 
they tend to have less-educated staff (or rely on consultants/vendors) and 
may even see NAT as a good thing ("it makes me secure!"), not the evil that 
it really is.

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 Fri Jul 06 17:31: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 1I6vP0-0000pf-GM; Fri, 06 Jul 2007 17:31:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6vOz-0000pa-83
	for ipv6@ietf.org; Fri, 06 Jul 2007 17:31:45 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I6vOy-0006JT-Oy
	for ipv6@ietf.org; Fri, 06 Jul 2007 17:31:45 -0400
Received: from eagle (127.0.0.1:3610)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S374BEB> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Fri, 6 Jul 2007 14:30:55 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Joe Abley'" <jabley@ca.afilias.info>,
	"'Christopher Morrow'" <christopher.morrow@gmail.com>
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>	<200707022118.31271@auguste.remlab.net>	<75cb24520707051754x7cdca7cw40de76220a998f1c@mail.gmail.com>	<77ead0ec0707052058r18af1a0o7faa9fc92ee068d5@mail.gmail.com>	<75cb24520707052131y5b4f5469h6ab618bb522d542b@mail.gmail.com>
	<5F998D87-B1EA-41EF-AFF3-7F41373106D6@ca.afilias.info>
In-Reply-To: <5F998D87-B1EA-41EF-AFF3-7F41373106D6@ca.afilias.info>
Date: Fri, 6 Jul 2007 14:30:01 -0700
Message-ID: <407201c7c014$cfc4d250$6f4e76f0$@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: Ace/1YJl88DNEcMAQ1OS9ERts+D0WQAPwv9w
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: 'IPv6 WG' <ipv6@ietf.org>
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
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

Processing RH0 does not mean a host acts as a bounce point. If a node
decides to forward traffic it is a router.  A host can properly process an
RH0 packet and drop it if one of its other addresses is not the next hop. 

I object to the entire hysteria driven effort to deprecate RH0. 

Tony

> -----Original Message-----
> From: Joe Abley [mailto:jabley@ca.afilias.info]
> Sent: Friday, July 06, 2007 6:55 AM
> To: Christopher Morrow
> Cc: IPv6 WG
> Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
> 
> 
> On 6-Jul-2007, at 00:31, Christopher Morrow wrote:
> 
> > I hesitate to get rid or something because of this sole reason, I
> > think another answer would be to make paying attention to it just
> > optional for routing gear (or all things, honestly I really only care
> > about routing gear, and so does this draft).
> 
> Actually, no -- hosts which conform to the current spec also process
> RH0. So even if all IPv6 routers had RH0 functionality removed, hosts
> could still act as bounce points for the purposes of congesting
> remote paths.
> 
> > I'd also take issue, for many of the same reasons stated earlier
> with:
> >
> > "The severity of this threat is considered to be sufficient to
> warrant
> >   deprecation of RH0 entirely"
> >
> > from the draft, I don't think that deprecation is warranted in this
> > case, if it is than anything that can cause amplification attacks is
> > likely also in need of deprecation.
> 
> So, to summarise: your proposal is that RH0 should not be deprecated,
> but that it should be made optional? I'm not convinced that I
> understand how that's going to prevent the "amplification over remote
> paths" problem.
> 
> Note too that several widely-deployed IPv6 stacks have already taken
> the approach of effectively deprecating RH0. So there's a practical
> consideration that if we decide to do something different, we are
> diverging from deployed practice.
> 
> 
> 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 Fri Jul 06 18: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 1I6wTl-0005CB-N9; Fri, 06 Jul 2007 18:40:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6wTk-00057U-Bd
	for ipv6@ietf.org; Fri, 06 Jul 2007 18:40:44 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6wTi-0001Gi-UE
	for ipv6@ietf.org; Fri, 06 Jul 2007 18:40:44 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1183765011; x=1184369811; 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=qLvubK8Ot3ny04
	kQOe83y/2tKrlFuvVZROliw7xhl34j+eB5F4o7xGlykOFzyR24Jquje5fAzMn7Xh
	Yfv1Bp3QlEQ9E/gSzfNhGJh29avhRC5vS3zv5Vv0pLZwRxOLgkCM8mWjaS9BiKS8
	0uGeLl0sA8Ep8mPfgU9A7rDxLxnSQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=H+QhMTFLnb3kXI//UKv9vcbCXO2ak1GhvS3sdhZEyjk6GjWUbtB9qi+LB46Secym8vTovAEJbuvrSoGoe2/xF0xn8/hIbgdERe2ELJ4EP506neZGfTSGFHb9mU+bjfTi8g9z9283c8w+f8pzAfQp5LQv6BQcUrvMehAkx9pKCW8=;
Received: from [10.10.10.50] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002571768.msg
	for <ipv6@ietf.org>; Sat, 07 Jul 2007 00:36:49 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Sat, 07 Jul 2007 00:39:35 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: 'IPv6 WG' <ipv6@ietf.org>
Message-ID: <C2B49147.1A1E63%jordi.palet@consulintel.es>
Thread-Topic: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
Thread-Index: Ace/1YJl88DNEcMAQ1OS9ERts+D0WQAPwv9wAAJ+KDI=
In-Reply-To: <407201c7c014$cfc4d250$6f4e76f0$@net>
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:070706:ipv6@ietf.org::RDwGApTFdK967eA1:00000jpW
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, Sat, 07 Jul 2007 00:36:49 +0200
X-MDAV-Processed: consulintel.es, Sat, 07 Jul 2007 00:36:51 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
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
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

I agree with Tony, this is pure hysteria, and this effort should be killed.

Regards,
Jordi




> De: Tony Hain <alh-ietf@tndh.net>
> Responder a: <alh-ietf@tndh.net>
> Fecha: Fri, 6 Jul 2007 14:30:01 -0700
> Para: 'Joe Abley' <jabley@ca.afilias.info>, 'Christopher Morrow'
> <christopher.morrow@gmail.com>
> CC: 'IPv6 WG' <ipv6@ietf.org>
> Asunto: RE: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
> 
> Processing RH0 does not mean a host acts as a bounce point. If a node
> decides to forward traffic it is a router.  A host can properly process an
> RH0 packet and drop it if one of its other addresses is not the next hop.
> 
> I object to the entire hysteria driven effort to deprecate RH0.
> 
> Tony
> 
>> -----Original Message-----
>> From: Joe Abley [mailto:jabley@ca.afilias.info]
>> Sent: Friday, July 06, 2007 6:55 AM
>> To: Christopher Morrow
>> Cc: IPv6 WG
>> Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
>> 
>> 
>> On 6-Jul-2007, at 00:31, Christopher Morrow wrote:
>> 
>>> I hesitate to get rid or something because of this sole reason, I
>>> think another answer would be to make paying attention to it just
>>> optional for routing gear (or all things, honestly I really only care
>>> about routing gear, and so does this draft).
>> 
>> Actually, no -- hosts which conform to the current spec also process
>> RH0. So even if all IPv6 routers had RH0 functionality removed, hosts
>> could still act as bounce points for the purposes of congesting
>> remote paths.
>> 
>>> I'd also take issue, for many of the same reasons stated earlier
>> with:
>>> 
>>> "The severity of this threat is considered to be sufficient to
>> warrant
>>>   deprecation of RH0 entirely"
>>> 
>>> from the draft, I don't think that deprecation is warranted in this
>>> case, if it is than anything that can cause amplification attacks is
>>> likely also in need of deprecation.
>> 
>> So, to summarise: your proposal is that RH0 should not be deprecated,
>> but that it should be made optional? I'm not convinced that I
>> understand how that's going to prevent the "amplification over remote
>> paths" problem.
>> 
>> Note too that several widely-deployed IPv6 stacks have already taken
>> the approach of effectively deprecating RH0. So there's a practical
>> consideration that if we decide to do something different, we are
>> diverging from deployed practice.
>> 
>> 
>> 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
> --------------------------------------------------------------------




**********************************************
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 Jul 06 18:48: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 1I6waz-000854-Fp; Fri, 06 Jul 2007 18:48:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6wav-00084l-UX
	for ipv6@ietf.org; Fri, 06 Jul 2007 18:48:09 -0400
Received: from nz-out-0506.google.com ([64.233.162.239])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6war-0003py-Ne
	for ipv6@ietf.org; Fri, 06 Jul 2007 18:48:09 -0400
Received: by nz-out-0506.google.com with SMTP id n1so327017nzf
	for <ipv6@ietf.org>; Fri, 06 Jul 2007 15:48: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=tAwqSy2UwgpwWEfYQYODtVitWna536qLCoqewuKuEFsr58DbvQir3EIzIY23W0nY49KI2GFCKr2T6kwD103PBAJ2VGYX4bK/QrfHA0JCpXqmGU4S92ZA2S8qYHPmCaD9iOs3zlP1uT7h9N1pmYVD1nrR5ameB0pTHp7dfD25GHw=
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=RoiK1GA4Lp5J6BA58xALDSbOjWb4fBoiwQNg35DFYlpx+j4wiHkCF7SKiIk/5T/Z+AfNdcAVU0PI/MTHuYsF8c09jEGh2OoaqLtayFqPyR/yyigNzJk3f4heO33AiOXbbqQvbfd9Vgs7mTtOGzMC93FoW532goWd+hdqUdXQtbU=
Received: by 10.115.60.1 with SMTP id n1mr1074232wak.1183762084998;
	Fri, 06 Jul 2007 15:48:04 -0700 (PDT)
Received: by 10.114.93.7 with HTTP; Fri, 6 Jul 2007 15:48:04 -0700 (PDT)
Message-ID: <75cb24520707061548m1b9f75c2wa4ded3d987498ca4@mail.gmail.com>
Date: Fri, 6 Jul 2007 18:48:04 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: jordi.palet@consulintel.es
In-Reply-To: <C2B49147.1A1E63%jordi.palet@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <407201c7c014$cfc4d250$6f4e76f0$@net>
	<C2B49147.1A1E63%jordi.palet@consulintel.es>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: IPv6 WG <ipv6@ietf.org>
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

On 7/6/07, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
> I agree with Tony, this is pure hysteria, and this effort should be killed.

yes.

thanks.
-Chris

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



From ipv6-bounces@ietf.org Fri Jul 06 19:27: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 1I6xCu-0000LC-E8; Fri, 06 Jul 2007 19:27:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6xCs-0000Ky-ST
	for ipv6@ietf.org; Fri, 06 Jul 2007 19:27:22 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6xCo-0003zz-J4
	for ipv6@ietf.org; Fri, 06 Jul 2007 19:27:22 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id DB7021A4D93; Fri,  6 Jul 2007 16:27:17 -0700 (PDT)
Date: Fri, 6 Jul 2007 16:27:17 -0700
From: bill fumerola <billf@mu.org>
To: Stephen Sprunk <stephen@sprunk.org>
Message-ID: <20070706232717.GD9951@elvis.mu.org>
References: <E1I4NDR-0007VX-QU@megatron.ietf.org>
	<62977.74.122.168.81.1183152144.squirrel@look.libertyrms.com>
	<4685858B.8040003@spaghetti.zurich.ibm.com>
	<07d601c7bdb4$9b5413d0$543816ac@atlanta.polycom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <07d601c7bdb4$9b5413d0$543816ac@atlanta.polycom.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: 9182cfff02fae4f1b6e9349e01d62f32
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 Tue, Jul 03, 2007 at 03:47:50PM -0500, Stephen Sprunk wrote:
> There is no reason to think that the RIRs' cost of registering and managing 
> a /48 in fc00::/8 will be any less than the cost of registering and 
> managing a /48 in 2000::/3.  Since all of the RIRs operate on a 
> cost-recovery basis, that means the fees should be the same.  Ergo, ULA-C 
> will not be any cheaper under the currently proposed model.

yes, and?

shouldn't that encourage people to get space allocated out of the block
(2000::/3, FC00::/8) that best suits them? they could request/register
out of both if they have a use for both. several cases have been made
on this list that people would have dissimilar uses for both.

what is the problem with allocating people what they want? the RIRs can
set their fee schedule as needed. that's not this WG's worry.

if i pay to have a ULA-[CG] block allocated/registered to me, i should
know that i'm not going to be able to sucessfully announce it to the
DFZ. the RIRs tend to do a good enough job explaining the difference
between the different types of address space available. given enough
direction and information from the documents produced here, i think
we can depend on RIRs to do the right thing.

-- 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 Jul 06 20:41: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 1I6yM7-00054v-Ss; Fri, 06 Jul 2007 20:40:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6yM6-00054q-LT
	for ipv6@ietf.org; Fri, 06 Jul 2007 20:40:58 -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 1I6yM6-0001rA-8A
	for ipv6@ietf.org; Fri, 06 Jul 2007 20:40:58 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 530E1233D7; Sat,  7 Jul 2007 09:40:55 +0900 (JST)
To: christopher.morrow@gmail.com
In-Reply-To: Your message of "Fri, 6 Jul 2007 18:48:04 -0400"
	<75cb24520707061548m1b9f75c2wa4ded3d987498ca4@mail.gmail.com>
References: <75cb24520707061548m1b9f75c2wa4ded3d987498ca4@mail.gmail.com>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070707004055.530E1233D7@coconut.itojun.org>
Date: Sat,  7 Jul 2007 09:40:55 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: ipv6@ietf.org
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

> > I agree with Tony, this is pure hysteria, and this effort should be killed.
> 
> yes.

	in this case, it is good to be a bit of paranoid.  the level of
	"paranoid"ness differs by person/standpoint.

	minor nit (i sound like jinmei):
	in RFC1883/2460 terminology "forwarding" is defined as "re-transmit
	packet even when ip6_dst is not mine".  so when a host (non-router)
	handles rthdr0, it is not "forwarding".

itojun

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



From ipv6-bounces@ietf.org Fri Jul 06 21:00: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 1I6yeU-0001dg-N5; Fri, 06 Jul 2007 20:59:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6yeT-0001dV-58
	for ipv6@ietf.org; Fri, 06 Jul 2007 20:59:57 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6yeQ-0003tm-ST
	for ipv6@ietf.org; Fri, 06 Jul 2007 20:59:57 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 5F0E2114BC
	for <ipv6@ietf.org>; Sat,  7 Jul 2007 00:59: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, 06 Jul 2007 13:16:29 -0400."
	<2617.10.31.30.119.1183742189.squirrel@stiedprstage1> 
References: <80699.1183408066@sa.vix.com>
	<3838.10.31.30.119.1183656859.squirrel@stiedprstage1>
	<45323.1183663849@sa.vix.com>
	<1520.156.154.5.45.1183678997.squirrel@stiedprstage1>
	<89916.1183680829@sa.vix.com>
	<2617.10.31.30.119.1183742189.squirrel@stiedprstage1> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Sat, 07 Jul 2007 00:59:54 +0000
Message-ID: <19501.1183769994@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Subject: Re: draft-ietf-ipv6-ula-global-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

re: http://sa.vix.com/~vixie/ula-global.txt, the internet-drafts@ staff
asked me to resubmit it with a -00 filename, which i did, and then spoke
as follows.  so, if this WG weren't inactive, and we were meeting in
chicago, then this draft could not be discussed there.  jfyi:

> Date: Fri, 6 Jul 2007 13:16:29 -0400 (EDT)
> Subject: Re: draft-ietf-ipv6-ula-global-01.txt
> From: ids@ietf.org
> To: "Paul Vixie" <paul@vix.com>
> 
> We cannot post it as the working group chairs have not approved it.
> 
> >> If this is the initial submission than it should -00.
> >
> > ok, here goes.
> >
> >
> >
> >
> >
> >
> >
> >    DNSOP Working Group                                       P. Vixie, ISC
> >    INTERNET-DRAFT                                         R. Hinden, Nokia
> >    <draft-ietf-ipv6-ula-global-00.txt>                    G. Huston, APNIC
> >                                                             T. Narten, IBM
> >
> >                      Globally Assigned Locally Reachable
> >                         Unique IPv6 Unicast Addresses
...

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



From ipv6-bounces@ietf.org Sat Jul 07 10:46: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 1I7BXY-00029Z-2Q; Sat, 07 Jul 2007 10:45:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7BXW-00028v-W4
	for ipv6@ietf.org; Sat, 07 Jul 2007 10:45:39 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7BXH-0002ue-LK
	for ipv6@ietf.org; Sat, 07 Jul 2007 10:45:38 -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 1I7BZF-000ELf-Ik; Sat, 07 Jul 2007 14:47:25 +0000
In-Reply-To: <75cb24520707061548m1b9f75c2wa4ded3d987498ca4@mail.gmail.com>
References: <407201c7c014$cfc4d250$6f4e76f0$@net>
	<C2B49147.1A1E63%jordi.palet@consulintel.es>
	<75cb24520707061548m1b9f75c2wa4ded3d987498ca4@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: <4946EF07-201F-437B-BFE7-4170BBC99DEF@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Sat, 7 Jul 2007 10:44:36 -0400
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: IPv6 WG <ipv6@ietf.org>, jordi.palet@consulintel.es
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


On 6-Jul-2007, at 18:48, Christopher Morrow wrote:

> On 7/6/07, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>> I agree with Tony, this is pure hysteria, and this effort should  
>> be killed.
>
> yes.

OK, so just to be clear, you're commenting on an earlier  
determination of consensus by the wg chair that RH0 should be  
deprecated, and you're not commenting specifically on this draft. Right?


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 Jul 07 16:19: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 1I7Gju-00033d-JV; Sat, 07 Jul 2007 16:18:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7Gjt-00033V-A0
	for ipv6@ietf.org; Sat, 07 Jul 2007 16:18:45 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7Gjo-0004Cn-Nv
	for ipv6@ietf.org; Sat, 07 Jul 2007 16:18:45 -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 l67KIXvG059298
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 7 Jul 2007 22:18:33 +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
	l67KIWfK014432; Sat, 7 Jul 2007 22:18:33 +0200
Date: Sat, 7 Jul 2007 22:18:32 +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: <44656.1183438512@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0707072145240.9923@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> <4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com> 
	<44656.1183438512@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: 00e94c813bef7832af255170dca19e36
Cc: ipv6@ietf.org, roger@jorgensen.no
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 Tue, 3 Jul 2007, Paul Vixie wrote:
>> The general idea is that the bulk of address assignments used should be,
>> one would expect and hope, PA, and aggregated, into large assignments
>> of PI blocks (ideally one per ASN) in the DFZ. The scalability of the
>> DFZ depends on this, in fact.
>
> no.  while it's true in the current system that identity-follows-routing,
> that may not always be true, and away from the DFZ, it's already untrue.
> therefore we must reject the aggregation-centric view, or at least, constrain
> it to only being valid for globally connected devices, reachable from DFZ.

There are cases where the network administrators dont care about the 
global DFZ, aggregation or whatever, they just want enough IP for their 
INTERNAL usage. And now are we back to what we (where I work) need ULA-C/G 
for...

- we don't need the full internet connectivity or reachability, we simply 
dont care whats on the internet from our point of view. We have RIR 
assigned IPblock for _all_ our global needs and let our chosen ISP provide 
us global internet when they announce _our_ RIR assigned netblock
- unique addresses so when we interconnect to other organization we dont 
get collision ever, neither now or in 10years time. ULA-L simple isnt 
enough, 2^40 is not good enough. No point in argueing over that.
- we dont want NAT anywhere in our network, that break the end to end 
connectivity we need for lots of things. Our internal video or phone 
system or whatever other application we have/will get.
- we need full reverse DNS control over the ULA-C/G blocks we have (we 
will get several thousands of them) since that way the other organization 
just have to go to the internet root DNS to lookup our IPs, they dont need 
to tune their DNS for reaching thing in OUR network.
(we are looking at something between 500 and upto 10 000 or more unique 
ULA-C/G blocks for or network and use)
- ...

sure we could use PI, but we dont need any of the features on the internet 
really... and for those features we need we have our RIR assigned netblock 
for that purpose.

sure we could just get a bigger PA block from our RIR but they dont buy 
_OUR_ arguments for why we need more IP, which is okay since it is our 
INTENRAL network that required the amount of IP we need. We dont have any 
issues to justify that we need a /32 after the current policies, or any of 
the other I've seen suggested.

And dont come telling us how we should structure our INTENRAL network, we 
have our reasons and our requirments, good or bad from others point of 
view, but they are the guidelines we are running our network and business 
after.I really doubt anyone like to be told that since it is strictly 
internal:)

Another reason for not using RIR assigned IP for our internel network 
usage are the justification we have to provide for getting a bigger block 
from RIPE. Or that it might be harder to explain why we need 500-10000++ 
PI blocks from RIPE than to just get ULA-C/G from whoever provide it. RIRs 
or IANA direct through a robot. For us it doesnt mather much really, we 
just need some UNIQUE IP addresses for our internal usage WITH global 
reverse DNS possibility...




I guess other enterprises see this the same way. They simply want INTERNAL 
unique IP addresses with global reverse DNS options, nothing less, nothing 
more.
They probably wont bother to become LIR just for internal IP, their ISP(s) 
provide them with their internet connectivity, and they can probably 
easy justify to get PI if they want that.



-- 

------------------------------
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 Jul 07 20:00: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 1I7KC8-0005pt-RG; Sat, 07 Jul 2007 20:00:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7KC5-0005pk-SY
	for ipv6@ietf.org; Sat, 07 Jul 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 1I7KC5-0007yr-FM
	for ipv6@ietf.org; Sat, 07 Jul 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 532E928461
	for <ipv6@ietf.org>; Sun,  8 Jul 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 08 Jul 2007 00:00:04 +0000
Message-Id: <20070708000004.532E928461@cyteen.hactrn.net>
X-Spam-Score: -0.9 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
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
--------+------+--------+----------+------------------------
 14.07% |   19 | 21.63% |   194860 | shemant@cisco.com
 13.33% |   18 | 11.48% |   103421 | paul@vix.com
 11.85% |   16 | 11.51% |   103733 | brian.e.carpenter@gmail.com
  8.89% |   12 |  7.04% |    63455 | stephen@sprunk.org
  5.93% |    8 |  5.74% |    51685 | jinmei@isl.rdc.toshiba.co.jp
  6.67% |    9 |  4.69% |    42268 | michael.dillon@bt.com
  4.44% |    6 |  6.52% |    58753 | vladislav.yasevich@hp.com
  4.44% |    6 |  3.69% |    33205 | sleibrand@internap.com
  3.70% |    5 |  2.84% |    25621 | jabley@ca.afilias.info
  2.96% |    4 |  3.02% |    27232 | christopher.morrow@gmail.com
  2.96% |    4 |  2.63% |    23707 | perry@coders.net
  2.22% |    3 |  2.64% |    23767 | briand@ca.afilias.info
  1.48% |    2 |  1.70% |    15285 | ot@cisco.com
  1.48% |    2 |  1.25% |    11232 | suresh.krishnan@ericsson.com
  1.48% |    2 |  1.16% |    10479 | aalain@trstech.net
  1.48% |    2 |  1.06% |     9532 | billf@mu.org
  0.74% |    1 |  0.94% |     8500 | fred@cisco.com
  0.74% |    1 |  0.88% |     7896 | jordi.palet@consulintel.es
  0.74% |    1 |  0.86% |     7727 | rogerj@jorgensen.no
  0.74% |    1 |  0.80% |     7217 | trejrco@gmail.com
  0.74% |    1 |  0.77% |     6932 | mark_andrews@isc.org
  0.74% |    1 |  0.71% |     6376 | vishwas.ietf@gmail.com
  0.74% |    1 |  0.69% |     6214 | julien.ietf@laposte.net
  0.74% |    1 |  0.68% |     6135 | jinmei@wide.ad.jp
  0.74% |    1 |  0.66% |     5952 | alh-ietf@tndh.net
  0.74% |    1 |  0.66% |     5946 | timbeck04@verizon.net
  0.74% |    1 |  0.64% |     5762 | sra+ipng@hactrn.net
  0.74% |    1 |  0.61% |     5525 | bmanning@isi.edu
  0.74% |    1 |  0.58% |     5263 | rdenis@simphalempin.com
  0.74% |    1 |  0.55% |     4998 | iljitsch@muada.com
  0.74% |    1 |  0.47% |     4248 | drc@virtualized.org
  0.74% |    1 |  0.47% |     4242 | msa@moth.iki.fi
  0.74% |    1 |  0.41% |     3699 | itojun@itojun.org
--------+------+--------+----------+------------------------
100.00% |  135 |100.00% |   900867 | 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 Jul 07 22:36: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 1I7Mdf-0006k1-4T; Sat, 07 Jul 2007 22:36:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7Mdd-0006jt-Ui
	for ipv6@ietf.org; Sat, 07 Jul 2007 22:36:41 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7Mdd-0002GD-IK
	for ipv6@ietf.org; Sat, 07 Jul 2007 22:36:41 -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 l682aPwg031716;
	Sat, 7 Jul 2007 19:36:40 -0700
Message-ID: <026a01c7c108$bd3673b0$6701a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.no>, "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>
	<4684DB4A.2060703@gmail.com><27414.1183131210@sa.vix.com><4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com><3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org><58873.1183400932@sa.vix.com><63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
Date: Sat, 7 Jul 2007 21:16:23 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org, roger@jorgensen.no
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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> (we are looking at something between 500 and upto 10 000 or
> more unique ULA-C/G blocks for or network and use)

That's going to get expensive, no matter how little the central authority 
charges.  Well, unless the central authority does bulk discounts, but I see 
no reason they would since there's no economy of scale in issuing thousands 
of prefixes that can't be aggregated, unlike aggregatable PI/PA space.

> I guess other enterprises see this the same way. They simply
> want INTERNAL unique IP addresses with global reverse DNS
> options, nothing less, nothing more.  They probably wont bother
> to become LIR just for internal IP, their ISP(s) provide them
> with their internet connectivity, and they can probably easy
> justify to get PI if they want that.

RIPE hasn't caught up to ARIN yet, apparently.  ARIN provides for direct PI 
assignments to end users with very minimal qualifications and no need to 
become an LIR (which get a /32 at minimum).  /48 is the minimum direct 
assignment size, and while you do have to "justify" a shorter prefix, all 
requests are approved.  Ebay, for instance, just got a /41.  And, while 
there's a nontrivial fee for the initial assignment, the annual maintenance 
(regardless of how large the block is) is only $100/yr.  I doubt your 
central authority is going to charge less than that for 10,000+ distinct 
blocks.

AfriNIC, I've read, has a similar policy except that the prefix must be 
advertised publicly within one year; ARIN has no requirement that the prefix 
_ever_ be advertised.

I do not see a requirement to pass ULA-C/G merely because some RIRs have 
failed to meet their respective communities' needs.  If you're unhappy with 
what RIPE offers, either show up and propose policy changes or 
(less-preferred) route around the failure and get space from ARIN.

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 Sun Jul 08 02:31: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 1I7QI2-0000Mn-9X; Sun, 08 Jul 2007 02:30:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7QI1-0000Mi-GO
	for ipv6@ietf.org; Sun, 08 Jul 2007 02:30:37 -0400
Received: from [2002:db58:fb10::1] (helo=carbon.meta.net.nz)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7QHx-0008FC-Dm
	for ipv6@ietf.org; Sun, 08 Jul 2007 02:30:37 -0400
Received: from [60.234.141.149] (helo=[10.100.4.156] ident=dahoose2)
	by carbon.meta.net.nz with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.62)
	(envelope-from <perry@coders.net>)
	id 1I7QHq-0007zO-AC; Sun, 08 Jul 2007 18:30:26 +1200
Message-ID: <4690847E.20409@coders.net>
Date: Sun, 08 Jul 2007 18:30:22 +1200
From: Perry Lorier <perry@coders.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.org>
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>	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>	<468B5534.5000701@gmail.com>	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>	<468C481A.1010405@coders.net>	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
	<468DF387.5000400@gmail.com>
	<02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
In-Reply-To: <02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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


> When my link to one of those three ISPs goes down, I have a 1/3 chance 
> of each outbound connection failing because the return path is broken 
> (or my other two upstreams do uRPF).  I also have a 1/3 chance of each 
> inbound connection failing until I update DNS to remove the relevant 
> AAAA records; smarter clients will try multiple addresses for inbound 
> connections, but there'll be a delay and not all clients are that smart.
>

Generally applications that support IPv6 support step-down through 
addresses, otherwise dual stack hosts that don't have a v6 connection 
can't connect to services that are dual stack.  This is the kind of bug 
that IPv6 enabled applications get fixed extremely quickly.

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



From ipv6-bounces@ietf.org Sun Jul 08 04: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 1I7RxR-0005UG-GC; Sun, 08 Jul 2007 04:17:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7RxP-0005U7-SN
	for ipv6@ietf.org; Sun, 08 Jul 2007 04:17:27 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7RxK-0000LD-Dh
	for ipv6@ietf.org; Sun, 08 Jul 2007 04:17:27 -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 l688GdiX016004
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sun, 8 Jul 2007 10:16: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
	l688GcFd025653; Sun, 8 Jul 2007 10:16:38 +0200
Date: Sun, 8 Jul 2007 10:16:38 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <026a01c7c108$bd3673b0$6701a8c0@atlanta.polycom.com>
Message-ID: <Pine.LNX.4.64.0707081009000.9923@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>
	<4684DB4A.2060703@gmail.com><27414.1183131210@sa.vix.com><4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com><3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org><58873.1183400932@sa.vix.com><63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
	<026a01c7c108$bd3673b0$6701a8c0@atlanta.polycom.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: 0fa76816851382eb71b0a882ccdc29ac
Cc: ipv6@ietf.org, roger@jorgensen.no
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 Sat, 7 Jul 2007, Stephen Sprunk wrote:
> Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
>> (we are looking at something between 500 and upto 10 000 or
>> more unique ULA-C/G blocks for or network and use)
>
> That's going to get expensive, no matter how little the central authority 
> charges.  Well, unless the central authority does bulk discounts, but I see 
> no reason they would since there's no economy of scale in issuing thousands 
> of prefixes that can't be aggregated, unlike aggregatable PI/PA space.

Did you notice I didnt mention the price, cheap or not one time in my 
mail? We know it will cost so we dont consider that yet. Make ULA-C/G more 
expensive than PI and we likely will use PI, make PI more expensive and it 
is not an options. You see the price dont mather! It is the technical 
options and possibilities that are important.

and we do NOT care about aggregation much either since it is our own 
internal network we are talking about.


In short, none of the two, economy or aggregation, are important when 
talking about ULA-C/G. (none of them should be announced to DMZ anyway so 
why wasting time on that?:))


>> I guess other enterprises see this the same way. They simply
>> want INTERNAL unique IP addresses with global reverse DNS
>> options, nothing less, nothing more.  They probably wont bother
>> to become LIR just for internal IP, their ISP(s) provide them
>> with their internet connectivity, and they can probably easy
>> justify to get PI if they want that.
>
> RIPE hasn't caught up to ARIN yet, apparently.  ARIN provides for direct PI 
> assignments to end users with very minimal qualifications and no need to 
> become an LIR (which get a /32 at minimum).  /48 is the minimum direct 
> assignment size, and while you do have to "justify" a shorter prefix, all 
> requests are approved.  Ebay, for instance, just got a /41.  And, while 
> there's a nontrivial fee for the initial assignment, the annual maintenance 
> (regardless of how large the block is) is only $100/yr.  I doubt your central 
> authority is going to charge less than that for 10,000+ distinct blocks.
>
> AfriNIC, I've read, has a similar policy except that the prefix must be 
> advertised publicly within one year; ARIN has no requirement that the prefix 
> _ever_ be advertised.
>
> I do not see a requirement to pass ULA-C/G merely because some RIRs have 
> failed to meet their respective communities' needs.  If you're unhappy with 
> what RIPE offers, either show up and propose policy changes or 
> (less-preferred) route around the failure and get space from ARIN.

you totaly missread what I wrote. A PI policy will most likely be in place 
in RIPE region to at some point soon, thats why I said we could choice 
from PI or ULA-C/G.

Did you also notice that I said we have already got our own PA assignment, 
a /32, for all our external needs?


Almost all ULA-C/G usecases can be solved by using either PA or PI type of 
addresses from the RIRs but why not give the enterprises an options to use 
something similar to RFC1918 addresses? Thats what we are talking about, 
another set of addresses for inter-network use, NOT DFZ/global Internet 
usage.
(sure there is a chance someone will start announcing them to the DFZ for 
some stupid reasons, then we can either hope the other ISP are smart 
enough to show the RFC we maybe will publish and reject it, or we can 
simply depreciate the addresses, or just live with it. But that chance is 
small anyway so why bother using time on that?)



-- 

------------------------------
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 Sun Jul 08 21:36: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 1I7iAv-00055a-7W; Sun, 08 Jul 2007 21:36:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7iAt-0004xj-3i
	for ipv6@ietf.org; Sun, 08 Jul 2007 21:36:27 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7iAr-0007G6-GW
	for ipv6@ietf.org; Sun, 08 Jul 2007 21:36:27 -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 E5992114027
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 01:36:24 +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 3A163E609B
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 01:36:24 +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 l691aGaW081091;
	Mon, 9 Jul 2007 11:36:17 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200707090136.l691aGaW081091@drugs.dv.isc.org>
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Fri, 06 Jul 2007 14:41:02 EST."
	<02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com> 
Date: Mon, 09 Jul 2007 11:36:16 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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


> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> > On 2007-07-06 02:59, Stephen Sprunk wrote:
> >> Why would you ever change PI space?  The issue is changing PA
> >> space, and that's something that may need to be done every few
> >> weeks as upstream links go up and down.
> >
> > Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
> > If you drop or add an ISP you drop or add a prefix in a planned manner.
> > RFC 4192.
> 
> When my link to one of those three ISPs goes down, I have a 1/3 chance of 
> each outbound connection failing because the return path is broken (or my 
> other two upstreams do uRPF).  I also have a 1/3 chance of each inbound 
> connection failing until I update DNS to remove the relevant AAAA records; 
> smarter clients will try multiple addresses for inbound connections, but 
> there'll be a delay and not all clients are that smart.
> 
> The alternative is to renumber the entire network every time a link goes up 
> or down.

	No. You don't have to renumber.  You just have to deprecate
	the addresses associated with the downed link.  This is the
	sort of thing routers should be able to do automatically.

	As for uRPF you will either have a problem with that all
	the time or none of the time.   If your ISP doesn't do BCP
	38 correctly (uRPF is not doing BPC 38 correctly) then
	choose ISPs that offer BCP 38 support (i.e. they allow you
	to send packets out with *any* of your PA addresses, not
	just the ones they assigned to you).

	The alternative is to introduce source address routing
	within your network.
 
> >> Compare to the cost of a NAT box and the choice is easy.
> >
> > That's true if you don't put the indirect operational and user
> > costs of NAT, plus the opportunity cost of innovation blocked
> > by NAT, into the equation.
> 
> Most of the operational and innovation costs of NAT are also present with a 
> stateful firewall, which any sane organization will be using, because it's 
> really the stateful inspection that burns you.

	NAT introduces costs above and beyond those of a stateful firewall.
	And as for stateful firewalls, applications should be able to
	talk to them to open up reply traffic if needed.
 
> > It *is* hard to get this into the budget unless you think strategically,
> > and factor in the way IPv6 is designed to handle multiple PA prefixes
> > simultaneously.
> 
> When presented with the choice between a paradigm shift and continuing along 
> the present path, most people will pick the latter.  In this case, that 
> means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.
> 
> >>> If your choices are PI vs PA then yeah NAT does look very attractive, 
> >>> but if you can have PA and "private"-PI (aka ULA) then things look a lot 
> >>> less blurred (IMHO).
> >>
> >> IMHO, you underestimate how much IT folks hate renumbering.
> >
> > They hate renumbering IPv4 networks. I do too, having managed such an
> > operation a couple of times. It's as a result of that hatred that
> > IPv6 came out as it is, making RFC 4192 possible.
> 
> Again, RFC 4192 ignores all of the non-technical aspects of renumbering. 
> That's probably appropriate, given the IETF's domain, but it's only a tiny 
> part of what must be done.  Changing the address on an interface takes a few 
> seconds; the change control processes leading up to it can burn months of 
> manpower.

	Real renumbering events are rare.

	You are wanting NAT to provide multi-homing support.  This
	does not require you to renumber.  There is no need to use
	NAT for this with IPv6.  IPv6 provides the mechanisms to
	move the source address selection back to the end host
	(where it belongs).
 
> You might convince me that if you do it frequently enough, the cost will be 
> low, but I don't want to work anywhere that renumbers often enough to be 
> good at it.  That reminds me of a scene in _Broken Arrow_ where a character 
> comments he doesn't know whether to be more scared that they lost a nuclear 
> weapon or that it happens often enough the military has a name for it.
> 
> > This is *not* to say that anyone will renumber weekly, and big networks
> > will avoid it (and are therefore candidates for PI). But for smaller
> > networks, the hatred should be substantially less, and balance the hatred
> > of NAT.
> 
> It's the smaller folks that can't get PI that hate NAT the least, because 
> they tend to have less-educated staff (or rely on consultants/vendors) and 
> may even see NAT as a good thing ("it makes me secure!"), not the evil that 
> it really is.
> 
> 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
> --------------------------------------------------------------------
-- 
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 Jul 09 00: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 1I7lEM-0004Vc-QG; Mon, 09 Jul 2007 00:52:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lEL-0004VX-NV
	for ipv6@ietf.org; Mon, 09 Jul 2007 00:52:13 -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 1I7lEH-00036z-87
	for ipv6@ietf.org; Mon, 09 Jul 2007 00:52:13 -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 1I7lEE-000543-0e; Mon, 09 Jul 2007 00:52:06 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 9 Jul 2007 00:52:06 -0400 (EDT)
Message-ID: <63417.74.122.168.81.1183956726.squirrel@look.libertyrms.com>
In-Reply-To: <02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.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>
	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>
	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>
	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
	<468DF387.5000400@gmail.com>
	<02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
Date: Mon, 9 Jul 2007 00:52:06 -0400 (EDT)
From: briand@ca.afilias.info
To: "Stephen Sprunk" <stephen@sprunk.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: 42e3ed3f10a1d8bef690f09da16f507a
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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 think we should avoid any "straw man" arguments, as those tend not to
actually help advance the subject matter.

Just because one way of accomplishing a particular networking objective,
involves particularly unpleasant choices, does not mean that the technology
involved is at fault. It is also possible that the design choice was a case
of not using the right tool for the right job.

> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>> On 2007-07-06 02:59, Stephen Sprunk wrote:
>>> Why would you ever change PI space?  The issue is changing PA
>>> space, and that's something that may need to be done every few
>>> weeks as upstream links go up and down.
>>
>> Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
>> If you drop or add an ISP you drop or add a prefix in a planned manner.
>> RFC 4192.

I beg to differ.

PI space is available, from most if not all RIRs.
The criteria for obtaining such is reasonable, and having multiple
ISPs, i.e. being multihomed, generally accomplishes this.

ISPs are expected to have PA space available to assign to their customers.
This does not mean that every customer can only ever use PA space from
their ISP. It only means that customers who do not have their own PI space,
will be able to get PA space from their ISP.

If you are multihomed, the community generally expects you to use PI space.
And that community includes your ISPs.

If we did not need to have PI space being announced from anyone other than
the core of the DFZ (those entities which are generally considered "tier 1"
for lack of a better description), then we would only have AS paths of
length 1, and we would be able to run EGP (the predecessor of BGP).

And clearly the collection of RFCs describing IPv6 numbering schemes are
robust enough, and the routing protocols inclusive enough, that PI space
can be announced via ISPs, in addition to their own PA aggregates.

> When my link to one of those three ISPs goes down, I have a 1/3 chance of
> each outbound connection failing because the return path is broken (or my
> other two upstreams do uRPF).  I also have a 1/3 chance of each inbound
> connection failing until I update DNS to remove the relevant AAAA records;
> smarter clients will try multiple addresses for inbound connections, but
> there'll be a delay and not all clients are that smart.
>
> The alternative is to renumber the entire network every time a link goes
> up
> or down.

You should, in this case, have a PI block, not be using anyone's PA block,
let along 3 x PA blocks. If you are using PI, you are running BGP, and
single link failures are the kind of thing that are relatively minor events
for any multi-connected entity, such as your network. No renumbering is
needed.

>>> Compare to the cost of a NAT box and the choice is easy.
>>
>> That's true if you don't put the indirect operational and user
>> costs of NAT, plus the opportunity cost of innovation blocked
>> by NAT, into the equation.
>
> Most of the operational and innovation costs of NAT are also present with
> a
> stateful firewall, which any sane organization will be using, because it's
> really the stateful inspection that burns you.
>
>> It *is* hard to get this into the budget unless you think strategically,
>> and factor in the way IPv6 is designed to handle multiple PA prefixes
>> simultaneously.
>
> When presented with the choice between a paradigm shift and continuing
> along
> the present path, most people will pick the latter.  In this case, that
> means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.

Our collective job is to ensure that scalable solutions are disseminated,
not only in the RFCs, but in the actual implementations that customers use.

This may mean some small amount of customer education. Everyone wins when
the end customers (no matter whose customers they are) make a choice which
is not only right for them, but good for the community as a whole.

If anyone is multihomed currently, and using NAT+RFC1918, then having the
option to go to PIv6 will likely make their life much easier. The fact
that they would never need to renumber, is just a bonus.
(They will have to renumber, in moving to IPv6 in any flavour, remember.)

>>>> If your choices are PI vs PA then yeah NAT does look very attractive,
>>>> but if you can have PA and "private"-PI (aka ULA) then things look a
>>>> lot
>>>> less blurred (IMHO).
>>>
>>> IMHO, you underestimate how much IT folks hate renumbering.
>>
>> They hate renumbering IPv4 networks. I do too, having managed such an
>> operation a couple of times. It's as a result of that hatred that
>> IPv6 came out as it is, making RFC 4192 possible.
>
> Again, RFC 4192 ignores all of the non-technical aspects of renumbering.
> That's probably appropriate, given the IETF's domain, but it's only a tiny
> part of what must be done.  Changing the address on an interface takes a
> few
> seconds; the change control processes leading up to it can burn months of
> manpower.
>
> You might convince me that if you do it frequently enough, the cost will
> be
> low, but I don't want to work anywhere that renumbers often enough to be
> good at it.  That reminds me of a scene in _Broken Arrow_ where a
> character
> comments he doesn't know whether to be more scared that they lost a
> nuclear
> weapon or that it happens often enough the military has a name for it.
>
>> This is *not* to say that anyone will renumber weekly, and big networks
>> will avoid it (and are therefore candidates for PI). But for smaller
>> networks, the hatred should be substantially less, and balance the
>> hatred
>> of NAT.
>
> It's the smaller folks that can't get PI that hate NAT the least, because
> they tend to have less-educated staff (or rely on consultants/vendors) and
> may even see NAT as a good thing ("it makes me secure!"), not the evil
> that
> it really is.
>
> 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
> --------------------------------------------------------------------
>



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



From ipv6-bounces@ietf.org Mon Jul 09 01:01: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 1I7lND-00087Q-4W; Mon, 09 Jul 2007 01:01:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7lNC-00087F-89
	for ipv6@ietf.org; Mon, 09 Jul 2007 01:01:22 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7lNB-0003EE-0B
	for ipv6@ietf.org; Mon, 09 Jul 2007 01:01:22 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 79C1E1146F
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 05:01: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 "Mon, 09 Jul 2007 00:52:06 -0400."
	<63417.74.122.168.81.1183956726.squirrel@look.libertyrms.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>
	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>
	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>
	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
	<468DF387.5000400@gmail.com>
	<02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
	<63417.74.122.168.81.1183956726.squirrel@look.libertyrms.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 09 Jul 2007 05:01:20 +0000
Message-ID: <58485.1183957280@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

> I think we should avoid any "straw man" arguments, as those tend not to
> actually help advance the subject matter.

while i agree, i think this doesn't go far enough.  can people who post
here say whether they are in favour or opposed to the outstanding drafts
and if they're opposed (or even if not) can they offer suggestions for
improvement?

ultimately the "advancement" of the subject matter will be measured by
consensus-driven standards, and not merely by well worded arguments, with
winners and losers, in the mailing list archive.

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



From ipv6-bounces@ietf.org Mon Jul 09 01:26: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 1I7llB-00068D-Qw; Mon, 09 Jul 2007 01:26:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7ll9-000684-VC
	for ipv6@ietf.org; Mon, 09 Jul 2007 01:26:08 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7lku-0004hY-Du
	for ipv6@ietf.org; Mon, 09 Jul 2007 01:26:07 -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 1I7lkK-00062T-O5; Mon, 09 Jul 2007 01:25:16 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 9 Jul 2007 01:25:16 -0400 (EDT)
Message-ID: <63440.74.122.168.81.1183958716.squirrel@look.libertyrms.com>
In-Reply-To: <Pine.LNX.4.64.0707072145240.9923@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>
	<4684DB4A.2060703@gmail.com> <27414.1183131210@sa.vix.com>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
Date: Mon, 9 Jul 2007 01:25:16 -0400 (EDT)
From: briand@ca.afilias.info
To: "Roger Jorgensen" <rogerj@jorgensen.no>
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.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: ipv6@ietf.org, roger@jorgensen.no
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 Tue, 3 Jul 2007, Paul Vixie wrote:
>>> The general idea is that the bulk of address assignments used should
>>> be,
>>> one would expect and hope, PA, and aggregated, into large assignments
>>> of PI blocks (ideally one per ASN) in the DFZ. The scalability of the
>>> DFZ depends on this, in fact.
>>
>> no.  while it's true in the current system that
>> identity-follows-routing,
>> that may not always be true, and away from the DFZ, it's already untrue.
>> therefore we must reject the aggregation-centric view, or at least,
>> constrain
>> it to only being valid for globally connected devices, reachable from
>> DFZ.
>
> There are cases where the network administrators dont care about the
> global DFZ, aggregation or whatever, they just want enough IP for their
> INTERNAL usage. And now are we back to what we (where I work) need ULA-C/G
> for...
>
> - we don't need the full internet connectivity or reachability, we simply
> dont care whats on the internet from our point of view. We have RIR
> assigned IPblock for _all_ our global needs and let our chosen ISP provide
> us global internet when they announce _our_ RIR assigned netblock
> - unique addresses so when we interconnect to other organization we dont
> get collision ever, neither now or in 10years time. ULA-L simple isnt
> enough, 2^40 is not good enough. No point in argueing over that.
> - we dont want NAT anywhere in our network, that break the end to end
> connectivity we need for lots of things. Our internal video or phone
> system or whatever other application we have/will get.
> - we need full reverse DNS control over the ULA-C/G blocks we have (we
> will get several thousands of them) since that way the other organization
> just have to go to the internet root DNS to lookup our IPs, they dont need
> to tune their DNS for reaching thing in OUR network.

You are referring to "other organization(s)". Will these be entities to whom
you directly connect, or have VPN connections to? Or do you mean,
generally, the Internet at large?

Without NAT, ULA is *not* allowed into the DFZ. Period.
You don't want NAT.
You *must* then choose to use PA blocks assigned by ISPs, or your own PI
block(s).

You may not care about the global DFZ, but if you plan on connecting to
it, it certainly cares about you, and everyone else. Specifically, that
certain rules be observed, ruthlessly. Everything else goes, however. Once
you have your address space, it is yours to do with as you wish. There is
no limit to the way you carve it up - google "VLSM" (variable-length
subnet mask) to get some good ideas. But what goes into the DFZ is
something all members of the DFZ care very greatly about.

> (we are looking at something between 500 and upto 10 000 or more unique
> ULA-C/G blocks for or network and use)
> - ...
>
> sure we could use PI, but we dont need any of the features on the internet
> really... and for those features we need we have our RIR assigned netblock
> for that purpose.
>
> sure we could just get a bigger PA block from our RIR but they dont buy
> _OUR_ arguments for why we need more IP, which is okay since it is our
> INTENRAL network that required the amount of IP we need. We dont have any
> issues to justify that we need a /32 after the current policies, or any of
> the other I've seen suggested.

You should not be dealing with PA blocks if you have the need for global
reverse DNS that you control, and for the size and complexity of your
network(s). PI is where you should be looking, and nowhere else.

And, since we're discussing ULA, your needs suddenly become irrelevant.

Sorry. Thanks for providing your input.

> And dont come telling us how we should structure our INTENRAL network, we
> have our reasons and our requirments, good or bad from others point of
> view, but they are the guidelines we are running our network and business
> after.I really doubt anyone like to be told that since it is strictly
> internal:)

What can you tell us about the needs of each of the 500-10000++ blocks you
think you need? Specifically, size (in terms of 2^N hosts per block, with
groupings of sizes to the nearest multiple of 8)?

E.g. - need 8,000 blocks of 2^8 hosts, 1,500 blocks of 2^16 hosts, and 500
blocks of 2^32 hosts.

Even if you have 32,000 blocks of 2^48 hosts, that is still only 2^64 of
address space. This would easily be managed by the use of a single /64.

If you have *one* PI block, of /64 or larger (e.g. /48 or /32), I think it
should be pretty clear that you should be able to subdivide your space
in any way you see fit. All of those subdivisions would be internal only,
as far as networks carried on anyone's routers - no one outside of your
infrastructure would see anything other than your single PI block.

> Another reason for not using RIR assigned IP for our internel network
> usage are the justification we have to provide for getting a bigger block
> from RIPE. Or that it might be harder to explain why we need 500-10000++
> PI blocks from RIPE than to just get ULA-C/G from whoever provide it. RIRs
> or IANA direct through a robot. For us it doesnt mather much really, we
> just need some UNIQUE IP addresses for our internal usage WITH global
> reverse DNS possibility...

I believe, if you look carefully, most RIRs have policies that permit the
assignment of PI blocks in IPv6 to anyone who *would* qualify for PI block
in IPv4 space. And the requirement for PI in IPv4 is certainly something
you would qualify for...

> I guess other enterprises see this the same way. They simply want INTERNAL
> unique IP addresses with global reverse DNS options, nothing less, nothing
> more.
> They probably wont bother to become LIR just for internal IP, their ISP(s)
> provide them with their internet connectivity, and they can probably
> easy justify to get PI if they want that.

The general argument on ULA-C/ULA-G vs PI is this - PI is what should be
used if you want globally unique address space, and will want this to be
known (without NAT) on reverse query lookups, to anyone else who is
connected indirectly (via the DFZ).

The model for ULA-C/ULA-G is one of non-Internet connected networks, or
networks who may use Internet-based transparent transport services, such
as VPN or MPLS-VPN or whatever else. VPN-VPN connections, which have in
the past been referred to as "extra-nets", are what are envisioned.
Globally unique addresses used by all such VPNs, mean that interconnnecting
them, deliberately or accidentally, permanently or temporarily, just works.

And, just because you plan on running an internal network, does not mean
that none of that network will want to reach the outside world. If it does,
certainly plan on using firewalls, but don't plan on using NAT just because
you used NAT in IPv4. There's nothing wrong with mixing ULA address space
and PI or PA address space on your internal infrastructure - that too is
meant to just work, and might well suit your needs. But if you plan on
having everything on your internal network reach out to the internet, my
advice is to get a single PI block and use that from the very beginning.

Exactly *how* you use that is your business and yours alone.

But, the community at large *will* tell you - we do not intend on allowing
anyone to get, use, and announce, large quantities of PI *blocks*.
The scalability of the DFZ requires very conservative growth and use of
numbers of prefixes, regardless of their size. It is router slots, aka
prefixes, aka netblocks in the DFZ, that we care about. Nothing in that is
impacted by the size of the blocks in question.

If you need to have 1000000 blocks internally, that's fine - but those
will need to be aggregated by you into one single PI block when you talk
to the world, or however many blocks your minimal topological needs can
justify.
(Or aggregated by one or more ISPs in PA blocks, that's fine too.)

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 Jul 09 04:03: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 1I7oDM-0000SS-KB; Mon, 09 Jul 2007 04:03:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7oDJ-0000QT-OC
	for ipv6@ietf.org; Mon, 09 Jul 2007 04:03:21 -0400
Received: from mu-out-0910.google.com ([209.85.134.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7oDE-00072F-RG
	for ipv6@ietf.org; Mon, 09 Jul 2007 04:03:21 -0400
Received: by mu-out-0910.google.com with SMTP id w8so615262mue
	for <ipv6@ietf.org>; Mon, 09 Jul 2007 01:03:16 -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=hjQQmUvhwOs+EqUwDZPSggmERnSIBE9vraz5mYAOKH+Pw6bxp3Q19r0U86C2KYj6K2tqVMHD8xkzlb7T6LdUcik8kyGe1KQnvHsL/jZYxCyi8/FuuoiAa7g0Us4t+fRsKeh1BmGwi+tiYLlM8mpemDKc9ytTevbnRQ3G+cTf+5E=
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=A6GlCkluJDpq+jmbqOpbm3fl0+W95F0Pv9IPEYXk4F0yYxtqInQsqMMxb67eqlR5sBjuwZGDG1P0nyzvzIp2lrPRq22PSWUAH3n23u4xnN/WjHAQ80FPpuplvtTcrVhzZy9vAIzYdFeOs4u+BWTLCHoVecf+r6QQMCkwoWdBuM0=
Received: by 10.82.160.2 with SMTP id i2mr7626503bue.1183968195760;
	Mon, 09 Jul 2007 01:03:15 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 7sm13374542nfv.2007.07.09.01.03.13
	(version=SSLv3 cipher=RC4-MD5); Mon, 09 Jul 2007 01:03:13 -0700 (PDT)
Message-ID: <4691EBC2.4030702@gmail.com>
Date: Mon, 09 Jul 2007 10:03:14 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Mark Andrews <Mark_Andrews@isc.org>
References: <200707090136.l691aGaW081091@drugs.dv.isc.org>
In-Reply-To: <200707090136.l691aGaW081091@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: Stephen Sprunk <stephen@sprunk.org>, 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-07-09 03:36, Mark Andrews wrote:
>> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>>> On 2007-07-06 02:59, Stephen Sprunk wrote:
>>>> Why would you ever change PI space?  The issue is changing PA
>>>> space, and that's something that may need to be done every few
>>>> weeks as upstream links go up and down.
>>> Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
>>> If you drop or add an ISP you drop or add a prefix in a planned manner.
>>> RFC 4192.
>> When my link to one of those three ISPs goes down, I have a 1/3 chance of 
>> each outbound connection failing because the return path is broken (or my 
>> other two upstreams do uRPF).  I also have a 1/3 chance of each inbound 
>> connection failing until I update DNS to remove the relevant AAAA records; 
>> smarter clients will try multiple addresses for inbound connections, but 
>> there'll be a delay and not all clients are that smart.
>>
>> The alternative is to renumber the entire network every time a link goes up 
>> or down.
> 
> 	No. You don't have to renumber.  You just have to deprecate
> 	the addresses associated with the downed link.  This is the
> 	sort of thing routers should be able to do automatically.

Indeed, and reachability detection is a necessary part of a
robust IPv6 implementation regardless of any of this, since
multiple addresses for the same host is a design feature
of IPv6.

     Brian

> 
> 	As for uRPF you will either have a problem with that all
> 	the time or none of the time.   If your ISP doesn't do BCP
> 	38 correctly (uRPF is not doing BPC 38 correctly) then
> 	choose ISPs that offer BCP 38 support (i.e. they allow you
> 	to send packets out with *any* of your PA addresses, not
> 	just the ones they assigned to you).
> 
> 	The alternative is to introduce source address routing
> 	within your network.
>  
>>>> Compare to the cost of a NAT box and the choice is easy.
>>> That's true if you don't put the indirect operational and user
>>> costs of NAT, plus the opportunity cost of innovation blocked
>>> by NAT, into the equation.
>> Most of the operational and innovation costs of NAT are also present with a 
>> stateful firewall, which any sane organization will be using, because it's 
>> really the stateful inspection that burns you.
> 
> 	NAT introduces costs above and beyond those of a stateful firewall.
> 	And as for stateful firewalls, applications should be able to
> 	talk to them to open up reply traffic if needed.
>  
>>> It *is* hard to get this into the budget unless you think strategically,
>>> and factor in the way IPv6 is designed to handle multiple PA prefixes
>>> simultaneously.
>> When presented with the choice between a paradigm shift and continuing along 
>> the present path, most people will pick the latter.  In this case, that 
>> means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.
>>
>>>>> If your choices are PI vs PA then yeah NAT does look very attractive, 
>>>>> but if you can have PA and "private"-PI (aka ULA) then things look a lot 
>>>>> less blurred (IMHO).
>>>> IMHO, you underestimate how much IT folks hate renumbering.
>>> They hate renumbering IPv4 networks. I do too, having managed such an
>>> operation a couple of times. It's as a result of that hatred that
>>> IPv6 came out as it is, making RFC 4192 possible.
>> Again, RFC 4192 ignores all of the non-technical aspects of renumbering. 
>> That's probably appropriate, given the IETF's domain, but it's only a tiny 
>> part of what must be done.  Changing the address on an interface takes a few 
>> seconds; the change control processes leading up to it can burn months of 
>> manpower.
> 
> 	Real renumbering events are rare.
> 
> 	You are wanting NAT to provide multi-homing support.  This
> 	does not require you to renumber.  There is no need to use
> 	NAT for this with IPv6.  IPv6 provides the mechanisms to
> 	move the source address selection back to the end host
> 	(where it belongs).
>  
>> You might convince me that if you do it frequently enough, the cost will be 
>> low, but I don't want to work anywhere that renumbers often enough to be 
>> good at it.  That reminds me of a scene in _Broken Arrow_ where a character 
>> comments he doesn't know whether to be more scared that they lost a nuclear 
>> weapon or that it happens often enough the military has a name for it.
>>
>>> This is *not* to say that anyone will renumber weekly, and big networks
>>> will avoid it (and are therefore candidates for PI). But for smaller
>>> networks, the hatred should be substantially less, and balance the hatred
>>> of NAT.
>> It's the smaller folks that can't get PI that hate NAT the least, because 
>> they tend to have less-educated staff (or rely on consultants/vendors) and 
>> may even see NAT as a good thing ("it makes me secure!"), not the evil that 
>> it really is.
>>
>> 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
>> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Mon Jul 09 04:05: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 1I7oFL-0001Uq-Vd; Mon, 09 Jul 2007 04:05:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7oFK-0001Ul-Nb
	for ipv6@ietf.org; Mon, 09 Jul 2007 04:05:26 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7oFG-000792-2T
	for ipv6@ietf.org; Mon, 09 Jul 2007 04:05:26 -0400
Received: by ug-out-1314.google.com with SMTP id u2so2844553uge
	for <ipv6@ietf.org>; Mon, 09 Jul 2007 01:05:21 -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=Mt5d5MFX89+l4AOmKf2mAF290PFgOPd4B29DIhAN4RF2TN0zFd2gz3nQXxn9Xs+W7vF+ebd95bZXYYhRGG67CSgCHZWe4ZZJD1+c37d6FaVCQ36jUl8JWxDzGwtYoVIuqzpM4MoSKZ72ss2GXXxgAXZZLC9QJ7k7usM7IXuAxYQ=
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=hNOxqQvFuQ6Z6P6i7qXroFYhwCtHDXfJj+AoM8vOEnntEYo9Bzqky9BoWVNucQKCmvPwQ9UN8bE+ofwEMtFn5WWgi2bJSH418kejD2ByLMxTNux9WymBzTKSQyBxEknXYyVcErTrHKSQ+tSjFi9Bgjtoy8q/JFVSEkvb77Vwr+o=
Received: by 10.82.106.14 with SMTP id e14mr7637605buc.1183968320955;
	Mon, 09 Jul 2007 01:05:20 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 34sm13172937nfu.2007.07.09.01.05.19
	(version=SSLv3 cipher=RC4-MD5); Mon, 09 Jul 2007 01:05:20 -0700 (PDT)
Message-ID: <4691EC41.3050400@gmail.com>
Date: Mon, 09 Jul 2007 10:05:21 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: briand@ca.afilias.info
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>
	<4688C2CA.5050302@gmail.com><43704.1183395211@sa.vix.com>
	<63246.74.122.168.81.1183436214.squirrel@look.libertyrms.com>
	<4689D1F8.3010604@internap.com><46803.1183438913@sa.vix.com>
	<4689E78F.6000307@internap.com><13412.1183471599@sa.vix.com>
	<468B5534.5000701@gmail.com>
	<029d01c7be6f$c91125e0$6701a8c0@atlanta.polycom.com>
	<468C481A.1010405@coders.net>
	<046801c7beb3$f8ca4f20$6701a8c0@atlanta.polycom.com>
	<468C84E9.10902@coders.net>
	<081701c7bf6b$14b91bf0$6701a8c0@atlanta.polycom.com>
	<468DF387.5000400@gmail.com>
	<02f501c7c009$d83c7d30$6701a8c0@atlanta.polycom.com>
	<63417.74.122.168.81.1183956726.squirrel@look.libertyrms.com>
In-Reply-To: <63417.74.122.168.81.1183956726.squirrel@look.libertyrms.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: Stephen Sprunk <stephen@sprunk.org>, 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-07-09 06:52, briand@ca.afilias.info wrote:
> I think we should avoid any "straw man" arguments, as those tend not to
> actually help advance the subject matter.
> 
> Just because one way of accomplishing a particular networking objective,
> involves particularly unpleasant choices, does not mean that the technology
> involved is at fault. It is also possible that the design choice was a case
> of not using the right tool for the right job.
> 
>> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>>> On 2007-07-06 02:59, Stephen Sprunk wrote:
>>>> Why would you ever change PI space?  The issue is changing PA
>>>> space, and that's something that may need to be done every few
>>>> weeks as upstream links go up and down.
>>> Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
>>> If you drop or add an ISP you drop or add a prefix in a planned manner.
>>> RFC 4192.
> 
> I beg to differ.
> 
> PI space is available, from most if not all RIRs.
> The criteria for obtaining such is reasonable, and having multiple
> ISPs, i.e. being multihomed, generally accomplishes this.

That's unfortunately true, but since it doesn't scale to the ten
million or so networks we expect to desire multihoming, it will
only work for a few years. That's why we need other solutions.

     Brian

> 
> ISPs are expected to have PA space available to assign to their customers.
> This does not mean that every customer can only ever use PA space from
> their ISP. It only means that customers who do not have their own PI space,
> will be able to get PA space from their ISP.
> 
> If you are multihomed, the community generally expects you to use PI space.
> And that community includes your ISPs.
> 
> If we did not need to have PI space being announced from anyone other than
> the core of the DFZ (those entities which are generally considered "tier 1"
> for lack of a better description), then we would only have AS paths of
> length 1, and we would be able to run EGP (the predecessor of BGP).
> 
> And clearly the collection of RFCs describing IPv6 numbering schemes are
> robust enough, and the routing protocols inclusive enough, that PI space
> can be announced via ISPs, in addition to their own PA aggregates.
> 
>> When my link to one of those three ISPs goes down, I have a 1/3 chance of
>> each outbound connection failing because the return path is broken (or my
>> other two upstreams do uRPF).  I also have a 1/3 chance of each inbound
>> connection failing until I update DNS to remove the relevant AAAA records;
>> smarter clients will try multiple addresses for inbound connections, but
>> there'll be a delay and not all clients are that smart.
>>
>> The alternative is to renumber the entire network every time a link goes
>> up
>> or down.
> 
> You should, in this case, have a PI block, not be using anyone's PA block,
> let along 3 x PA blocks. If you are using PI, you are running BGP, and
> single link failures are the kind of thing that are relatively minor events
> for any multi-connected entity, such as your network. No renumbering is
> needed.
> 
>>>> Compare to the cost of a NAT box and the choice is easy.
>>> That's true if you don't put the indirect operational and user
>>> costs of NAT, plus the opportunity cost of innovation blocked
>>> by NAT, into the equation.
>> Most of the operational and innovation costs of NAT are also present with
>> a
>> stateful firewall, which any sane organization will be using, because it's
>> really the stateful inspection that burns you.
>>
>>> It *is* hard to get this into the budget unless you think strategically,
>>> and factor in the way IPv6 is designed to handle multiple PA prefixes
>>> simultaneously.
>> When presented with the choice between a paradigm shift and continuing
>> along
>> the present path, most people will pick the latter.  In this case, that
>> means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.
> 
> Our collective job is to ensure that scalable solutions are disseminated,
> not only in the RFCs, but in the actual implementations that customers use.
> 
> This may mean some small amount of customer education. Everyone wins when
> the end customers (no matter whose customers they are) make a choice which
> is not only right for them, but good for the community as a whole.
> 
> If anyone is multihomed currently, and using NAT+RFC1918, then having the
> option to go to PIv6 will likely make their life much easier. The fact
> that they would never need to renumber, is just a bonus.
> (They will have to renumber, in moving to IPv6 in any flavour, remember.)
> 
>>>>> If your choices are PI vs PA then yeah NAT does look very attractive,
>>>>> but if you can have PA and "private"-PI (aka ULA) then things look a
>>>>> lot
>>>>> less blurred (IMHO).
>>>> IMHO, you underestimate how much IT folks hate renumbering.
>>> They hate renumbering IPv4 networks. I do too, having managed such an
>>> operation a couple of times. It's as a result of that hatred that
>>> IPv6 came out as it is, making RFC 4192 possible.
>> Again, RFC 4192 ignores all of the non-technical aspects of renumbering.
>> That's probably appropriate, given the IETF's domain, but it's only a tiny
>> part of what must be done.  Changing the address on an interface takes a
>> few
>> seconds; the change control processes leading up to it can burn months of
>> manpower.
>>
>> You might convince me that if you do it frequently enough, the cost will
>> be
>> low, but I don't want to work anywhere that renumbers often enough to be
>> good at it.  That reminds me of a scene in _Broken Arrow_ where a
>> character
>> comments he doesn't know whether to be more scared that they lost a
>> nuclear
>> weapon or that it happens often enough the military has a name for it.
>>
>>> This is *not* to say that anyone will renumber weekly, and big networks
>>> will avoid it (and are therefore candidates for PI). But for smaller
>>> networks, the hatred should be substantially less, and balance the
>>> hatred
>>> of NAT.
>> It's the smaller folks that can't get PI that hate NAT the least, because
>> they tend to have less-educated staff (or rely on consultants/vendors) and
>> may even see NAT as a good thing ("it makes me secure!"), not the evil
>> that
>> it really is.
>>
>> 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
>> --------------------------------------------------------------------
>>
> 
> 
> 

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



From ipv6-bounces@ietf.org Mon Jul 09 07:15: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 1I7rD4-0006J6-Go; Mon, 09 Jul 2007 07:15:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7rD2-00068g-4a
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:15:16 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7rCw-0003Yg-Vo
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:15:15 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 09 Jul 2007 13:15:11 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAN+0kUaQ/uCLh2dsb2JhbACBTI1rAQEJDiw
X-IronPort-AV: i="4.16,516,1175464800"; 
	d="scan'208"; a="147558275:sNHT29694780"
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 l69BFAUf014584; 
	Mon, 9 Jul 2007 13:15:10 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp4200.cisco.com
	[10.61.80.103])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l69BF6TC000027; 
	Mon, 9 Jul 2007 11:15:07 GMT
Message-ID: <469218B7.8060108@cisco.com>
Date: Mon, 09 Jul 2007 13:15:03 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
In-Reply-To: <061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
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=1042; t=1183979710;
	x=1184843710; 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=20draft-ietf-ipv6-ula-central-02.txt
	|Sender:=20; bh=ZFVgX0HrE6rEKAy/Tl2dUvsFTl0HO5nuHhMNZiYqdh8=;
	b=A6WZhxl7vulEeQ2i+tfAsjyePK9fWO7c5725Mq68I/3P3aT9EYVmLoxzrmin68jUTVUvLIPc
	QUNULIfbA5pHUK/bGPFnJN602k3eD6vqBS/lE83PniXtFV+GGMCVYws+;
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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
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
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Stephen Sprunk wrote:
> The supposed use case for ULA-C is large orgs who interconnect 
> privately with other large orgs.  If you _don't_ allow ULA-Cs in the 
> global reverse DNS, then every org in the internetwork must hack their 
> local DNS servers to recognize every other org's reverse DNS entries.  
> That is painful and unnecessary.

To borrow your logic, if this space is truly private why should this be 
an issue?
>
> There are operational concerns with putting ULA(-C) addresses in 
> forward DNS; nobody argues with that.  However, putting ULA-C 
> addresses in reverse DNS harms nobody who can't reach those addresses 
> yet greatly benefits those that can.

The delegation must be maintained and occasionally updated.  Who does that?

>
> Of course, if everyone just used PI, none of this would be an issue.
>  

At this point it is plain to see that ULA-C is nothing but PI address 
space, because the IETF is in no position to enforce otherwise.  So 
please, let's just call it what it is.

Eliot

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



From ipv6-bounces@ietf.org Mon Jul 09 07:22: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 1I7rKM-0001sN-UR; Mon, 09 Jul 2007 07:22:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7rKM-0001rh-1g
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:22:50 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7rKI-0003mg-8S
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:22:50 -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 l69BMfZU003017
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Jul 2007 13:22: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
	l69BMejf014295; Mon, 9 Jul 2007 13:22:41 +0200
Date: Mon, 9 Jul 2007 13:22:40 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: briand@ca.afilias.info
In-Reply-To: <63440.74.122.168.81.1183958716.squirrel@look.libertyrms.com>
Message-ID: <Pine.LNX.4.64.0707091234020.9923@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>    <4684DB4A.2060703@gmail.com>
	<27414.1183131210@sa.vix.com>    <4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
	<63440.74.122.168.81.1183958716.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: 29dc808194f5fb921c09d0040806d6eb
Cc: ipv6@ietf.org, roger@jorgensen.no
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 Mon, 9 Jul 2007, briand@ca.afilias.info wrote:
<snip>
>> - we don't need the full internet connectivity or reachability, we simply
>> dont care whats on the internet from our point of view. We have RIR
>> assigned IPblock for _all_ our global needs and let our chosen ISP provide
>> us global internet when they announce _our_ RIR assigned netblock
>> - unique addresses so when we interconnect to other organization we dont
>> get collision ever, neither now or in 10years time. ULA-L simple isnt
>> enough, 2^40 is not good enough. No point in argueing over that.
>> - we dont want NAT anywhere in our network, that break the end to end
>> connectivity we need for lots of things. Our internal video or phone
>> system or whatever other application we have/will get.
>> - we need full reverse DNS control over the ULA-C/G blocks we have (we
>> will get several thousands of them) since that way the other organization
>> just have to go to the internet root DNS to lookup our IPs, they dont need
>> to tune their DNS for reaching thing in OUR network.
>
> You are referring to "other organization(s)". Will these be entities to whom
> you directly connect, or have VPN connections to? Or do you mean,
> generally, the Internet at large?

yes they have their own internet connection, and they are closed network 
much like ours, some have interent but have closed zones (DMZ) we 
communicate with. In neither cases does internet mather since it is two 
network that interconnect through a direct connection totaly outside 
internet.


> Without NAT, ULA is *not* allowed into the DFZ. Period.
> You don't want NAT.
> You *must* then choose to use PA blocks assigned by ISPs, or your own PI
> block(s).

no, for _all_ our internal communicate we are consider to use ULA 
addresses, may be using some addresses from our PA block or a PI block 
for some special services, depending.
No one are allowed to communicate direct out of our network so they will 
anyway have to go through some sort of "relay", mail-servers, webproxies 
etc... and them again will communicate with internet through DMZ setups 
with our PA-addresses.
(and yeah we know there are services that dont can be sent through 
relayes but thats okay, we have other solution for them)


> You may not care about the global DFZ, but if you plan on connecting to
> it, it certainly cares about you, and everyone else. Specifically, that
> certain rules be observed, ruthlessly. Everything else goes, however. Once
> you have your address space, it is yours to do with as you wish. There is
> no limit to the way you carve it up - google "VLSM" (variable-length
> subnet mask) to get some good ideas. But what goes into the DFZ is
> something all members of the DFZ care very greatly about.

you didnt either read the entire mail... we have a PA block we use for our 
external needs. ULA-C/G are for _internal_ usage, nothing else.


>> sure we could just get a bigger PA block from our RIR but they dont buy
>> _OUR_ arguments for why we need more IP, which is okay since it is our
>> INTENRAL network that required the amount of IP we need. We dont have any
>> issues to justify that we need a /32 after the current policies, or any of
>> the other I've seen suggested.
>
> You should not be dealing with PA blocks if you have the need for global
> reverse DNS that you control, and for the size and complexity of your
> network(s). PI is where you should be looking, and nowhere else.
>
> And, since we're discussing ULA, your needs suddenly become irrelevant.
>
> Sorry. Thanks for providing your input.

eh we have PA for _our_ external needs, that one are okay.
We have PI for some special usage (there will quite certain be some needs 
for it someday).
And for the big internal usage we are consider to use ULA-C/G if it will 
provide us with global reverse control... that is any of our ULA-C/G 
addresses can be looked up through the global DNS.

what part is irrelevant?


<snip>
>> I guess other enterprises see this the same way. They simply want INTERNAL
>> unique IP addresses with global reverse DNS options, nothing less, nothing
>> more.
>> They probably wont bother to become LIR just for internal IP, their ISP(s)
>> provide them with their internet connectivity, and they can probably
>> easy justify to get PI if they want that.
>
> The general argument on ULA-C/ULA-G vs PI is this - PI is what should be
> used if you want globally unique address space, and will want this to be
> known (without NAT) on reverse query lookups, to anyone else who is
> connected indirectly (via the DFZ).
>
> The model for ULA-C/ULA-G is one of non-Internet connected networks, or
> networks who may use Internet-based transparent transport services, such
> as VPN or MPLS-VPN or whatever else. VPN-VPN connections, which have in
> the past been referred to as "extra-nets", are what are envisioned.
> Globally unique addresses used by all such VPNs, mean that interconnnecting
> them, deliberately or accidentally, permanently or temporarily, just works.

Excactly that is why we need GLOBAL unique ULA blocks for our usage. We 
dont know who we will private/direct interconnect with in the future but 
it will not be over internet.


> And, just because you plan on running an internal network, does not mean
> that none of that network will want to reach the outside world. If it does,
> certainly plan on using firewalls, but don't plan on using NAT just because
> you used NAT in IPv4. There's nothing wrong with mixing ULA address space
> and PI or PA address space on your internal infrastructure - that too is
> meant to just work, and might well suit your needs. But if you plan on
> having everything on your internal network reach out to the internet, my
> advice is to get a single PI block and use that from the very beginning.
>
> Exactly *how* you use that is your business and yours alone.

forget our external needs, they are taken care of by our PA block, or PI 
block if we want that for some special usage.
It is the internal networking that are the issue now. ULA-C/G looks like 
the best candidate if it goes through.


> But, the community at large *will* tell you - we do not intend on allowing
> anyone to get, use, and announce, large quantities of PI *blocks*.
> The scalability of the DFZ requires very conservative growth and use of
> numbers of prefixes, regardless of their size. It is router slots, aka
> prefixes, aka netblocks in the DFZ, that we care about. Nothing in that is
> impacted by the size of the blocks in question.
>
> If you need to have 1000000 blocks internally, that's fine - but those
> will need to be aggregated by you into one single PI block when you talk
> to the world, or however many blocks your minimal topological needs can
> justify.
> (Or aggregated by one or more ISPs in PA blocks, that's fine too.)

externaly we have PA so forget that. Internal we have three options 
with lots of variation on howto implement it:
- use our PA block one way or another
- use PI blocks (several different onces)
- use ULA-C/G



-- 

------------------------------
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 Mon Jul 09 07:30: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 1I7rSA-0003eZ-1G; Mon, 09 Jul 2007 07:30:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7rS6-0003W9-Db
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:30:50 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7rS3-0004NR-Vv
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:30:50 -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 l69BU5KN090581
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 9 Jul 2007 13:30:05 +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
	l69BU5M8014687; Mon, 9 Jul 2007 13:30:05 +0200
Date: Mon, 9 Jul 2007 13:30:04 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Eliot Lear <lear@cisco.com>
In-Reply-To: <469218B7.8060108@cisco.com>
Message-ID: <Pine.LNX.4.64.0707091323460.9923@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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.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: e1e48a527f609d1be2bc8d8a70eb76cb
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 Mon, 9 Jul 2007, Eliot Lear wrote:
<snip>
>> Of course, if everyone just used PI, none of this would be an issue.
>> 
> At this point it is plain to see that ULA-C is nothing but PI address space, 
> because the IETF is in no position to enforce otherwise.  So please, let's 
> just call it what it is.

it is NOT the same, there are several differences and some of them are not 
technical but more manager/non-technical ways of viewing things.

* PI are ment to be used on internet
* ULA-C/G are NOT ment to be used on internet (think we can forget the 
point that some might want todo it really, the chances are low and even 
managers will understand that it aint supposed to be done, most managers 
probably even understand RFC1918 ....)
* PI are the same as PA, there are NO real difference except on how you 
get it and the size of the block, it is what Paul Dixie have called UA 
(unique addresses), nothing else
* ULA-C/G are something completly different, it is more like RFC1918 space 
with some extra features,
- the size (amount of IPs)
- global unique so the current pain anyone with large network have when 
they are interconnecting, merging due to fusions or other reasons dont 
exist
- anyone can, IF the ULA-C/G holder want to, resolve the IP in any given 
ULA-C/G block through the global DNS system (a very very nice thing for 
everyone that hate the pain split-DNS give you...additional 
administration)


and probably a few other things but the above are those I consider most 
important.


-- 

------------------------------
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 Mon Jul 09 07: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 1I7rZl-0003yn-Ts; Mon, 09 Jul 2007 07:38:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7rZU-0003sv-AT
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:38:28 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7rZQ-0004EP-R3
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:38: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 27FC07301E
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 20:38:23 +0900 (JST)
Date: Mon, 09 Jul 2007 20:38:08 +0900
Message-ID: <m1r6nhkdsv.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: ipv6@ietf.org
In-Reply-To: <m2vecx8kvg.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <468E730F.8090409@hp.com>
	<8E296595B6471A4689555D5D725EBB21046B02CB@xmb-rtp-20a.amer.cisco.com>
	<m2vecx8kvg.wl%jinmei@isl.rdc.toshiba.co.jp>
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
Subject: release candidate of 2462bis (Re: Revisit: one remaining corner
	case in DAD)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Sat, 07 Jul 2007 03:09:23 +0900,
JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp> wrote:

> I tend to agree (I also thought this as an option myself).  Thanks for
> the suggestion.

I've updated the AUTH48 version of rfc2462bis with this fix.  Other
(major) changes since the latest version of I-D (rfc2462bis-08) are:

- Updates to RFC references:
  + RFC3041 -> RFC4941 (which will be published at the same timing)
  + RFC3513 -> RFC4291

- Wording clarification about interface identifiers
  (see discussion in the thread that began with this post:
  http://www1.ietf.org/mail-archive/web/ipv6/current/msg05163.html)

Note that I didn't include any change about the strictness of DAD.  I
didn't see any consensus on including that at this very final stage.

I'm about to submit this version to the RFC editor, but a copy of the
release candidate is available here: 

http://www.jinmei.org/rfc4862-candidate.txt

just in case.

					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 Jul 09 07:59: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 1I7rtJ-0001fI-V6; Mon, 09 Jul 2007 07:58:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7rtH-0001fC-AW
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:58:57 -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 1I7rtG-0004lO-9o
	for ipv6@ietf.org; Mon, 09 Jul 2007 07:58:55 -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 69D43140C1D6;
	Mon,  9 Jul 2007 13:58:51 +0200 (CEST)
Message-ID: <46922300.6020101@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 12:58:56 +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: <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>	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
X-Enigmail-Version: 0.95.2
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: f49c97ce49302a02285a2d36a99eef8c
Cc: ipv6@ietf.org, Eliot Lear <lear@cisco.com>
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="===============1737757496=="
Errors-To: ipv6-bounces@ietf.org

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

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

Roger Jorgensen wrote:
> On Mon, 9 Jul 2007, Eliot Lear wrote:
> <snip>
>>> Of course, if everyone just used PI, none of this would be an issue.
>>>
>> At this point it is plain to see that ULA-C is nothing but PI address
>> space, because the IETF is in no position to enforce otherwise.  So
>> please, let's just call it what it is.
>=20
> it is NOT the same, there are several differences and some of them are
> not technical but more manager/non-technical ways of viewing things.
>=20
> * PI are ment to be used on internet

False, they are "globally unique IPv6 addresses". Where you use them,
nobody cares as they are meant to be used everywhere. Just like ASN's
and everything else that the RIR's provide. They are "globally unique"
and therefor allow you to interconnect to other organizations, if those
are on "The Internet" or just local. Just check the "Prefix In Use" kind
of tools, they show that a lot of PI space is not visible on the
Internet, and even then, being available in BGP doesn't say that those
blocks are actually routed further than the router which routes it into
/dev/null or the firewall which blocks everything or runs it into a
honeypot.


> * ULA-C/G are NOT ment to be used on internet (think we can forget the
> point that some might want todo it really, the chances are low and even=

> managers will understand that it aint supposed to be done, most manager=
s
> probably even understand RFC1918 ....)

The chances of people wanting to use ULA-C/G on the Internet are really
high. There is *always* a need to use them on "the Internet", even if
that "Internet" is only an interconnection between several
organizations. At one point or another you will most likely be
connecting to an organization that is on the Internet and that doesn't
want to participate/do difficult with ULA-kind of addresses and then you
are stuck. Why make "ULA" so special and prone to be used on the
Internet anyway after a while, why burden people with it?


> * PI are the same as PA, there are NO real difference except on how you=

> get it and the size of the block, it is what Paul Dixie have called UA
> (unique addresses), nothing else

Paul Vixie indeed labeled that correct. The only difference is the size
indeed and who gets them. Also PI is supposed to be assigned to one
single end-site, while PA is allocated to one big organization that
sub-assigns to it's own organizational units/customers.


> * ULA-C/G are something completly different, it is more like RFC1918
> space with some extra features,
> - the size (amount of IPs)

UA does that

> - global unique so the current pain anyone with large network have when=

> they are interconnecting, merging due to fusions or other reasons dont
> exist

UA does that

> - anyone can, IF the ULA-C/G holder want to, resolve the IP in any give=
n
> ULA-C/G block through the global DNS system (a very very nice thing for=

> everyone that hate the pain split-DNS give you...additional administrat=
ion)

Please explain me how you are going to do *forward DNS* also. You know,
most people type www.google.com, not the ip6.arpa ones and without the
first, the latter is useless. You have to connect the forward zones
anyway, so why not connect the reverse ones also. This has to be split
DNS anyway, as a lot of companies are not willing to connect their
internal systems in ANY way to the global Internet or let alone, expose
those hostnames to that global Internet thing. Of course it is a lot of
fun to be able to resolve big-red-button.oval-room.whitehouse.gov and at
least know where to look for.

Hint for security control freaks: DNS tunneling, you know it is fun :)
And when you are able from your local (ULA) host to resolve a global DNS
name you can do exactly that and more. Also what happens when a local
guy types "www.google.com", do they get routed into oblivion or do you
think they will not want to connect to that or to Wikipedia and a lot of
resources on the Internet? Or are you going to use 2 IP addresses or
more per host and create even a bigger management hell?

Stuffing *LOCAL* reverse DNS in the *GLOBAL* DNS doesn't make any sense.
Either keep it totally local or keep it totally global (thus UA).


So how exactly is this ULA thing different from the UA (PI&PA) space
that is already available? Why bother with ULA when one day you might
most likely want to connect to the Internet anyway and cause pain then?
Why lay that pain unto people?


The only real difference I see is that it is a well known block that
people can force to not route, thus making a 2nd kind of Internet
Citizen and a  monopoly situation for the folks who can and the ones who
can't get UA space.


Now I do see another use for this kind of address space, but then it
should not be called this way. It could be used for ID/LOC solutions,
where these kind of addresses are Explicit-non-DFZ addresses. But if
that is the reason for what folks want to use them, as that is what I am
sort of reading between the lines as actual real usage has still not
been identified, then please just state that.

Greets,
 Jeroen


--------------enig8E321B1383D8D905654D6CB9
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/

iHUEARECADUFAkaSIwAuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58IymXAKCxRNDgBsPb4iqYmhK7HcvkOvfx
xwCgoRcY47FupKhsv3h61+2gkYbGX4Q=
=2ByX
-----END PGP SIGNATURE-----

--------------enig8E321B1383D8D905654D6CB9--


--===============1737757496==
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
--------------------------------------------------------------------

--===============1737757496==--




From ipv6-bounces@ietf.org Mon Jul 09 08:18: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 1I7sBR-0005fI-HB; Mon, 09 Jul 2007 08:17:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7sB3-0005aU-Du
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:17:17 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7sB0-0005m1-3a
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:17:17 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 13:16:49 +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, 9 Jul 2007 13:18:21 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0A46060@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <469218B7.8060108@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfCGpuDgM9XspVpTCme8iQgURr3PgAB7cNg
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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 09 Jul 2007 12:16:49.0567 (UTC)
	FILETIME=[06B752F0:01C7C223]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
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

> At this point it is plain to see that ULA-C is nothing but PI=20
> address space, because the IETF is in no position to enforce=20
> otherwise.  So please, let's just call it what it is.

The IETF is not in a position to enforce the special handling of ULA-C
addresses however, IANA via the RIRs is in such a position. The C in
ULA-C refers to a central registry. It is likely that IANA will appoint
the RIRs to handle that function. Since the RIRs only allocate numbers
to organizations who sign a contract with the RIR, this places the RIR
in a legal position to enforce any special rules that may be attached to
ULA-C addresses.

The IETF can state its intent that ULA-C address ranges should not be
announced on the Internet or routed across the Internet outside of
tunneling technologies. The RIRs can then enforce that intent.

If the membership of the RIRs decide that it is valuable to allow ULA-C
addresses to be used on the Internet and that they can handle the
increase of entries in the global routing table, then those members can
collectively override the IETF's intent.=20

Essentially, the IETF is placing control over the route announcement
question in the hands of those who are actually impacted by the
question. If there is any dispute over the specifics of how this is
handled, the RIRs are the forum in which it should be worked out.=20

--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 Mon Jul 09 08:33: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 1I7sQR-0004cb-Kg; Mon, 09 Jul 2007 08:33:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7sQM-0004cH-LU
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:33:08 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7sQI-0005wZ-5J
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:33:06 -0400
Received: by ug-out-1314.google.com with SMTP id u2so2897919uge
	for <ipv6@ietf.org>; Mon, 09 Jul 2007 05:33:01 -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=mRMn/OeDL6ao0pyPVvf+ANpz+vW704U8hZVPpNkqQi+ZONAsxnLCEiUqJwd5ns/uRfAPvCM1LWvZc01z2E1ud1gdhT9ehSUq+07+zrsSzmfU5/G+94eUr/SRR8ME0YhHYLYoR8Wb0adFKV64xDE6J12ctl9pHdVki6JLM5MwCU4=
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=VY0XDKjDXpGj7TS7N2wQ4gJxcXYiKWLroQ9XiuOVVKsFlsjKbfjuJ2gBCksI9gY3X0cGZgBEUCNkPj7gtcNAkTtbpClFxDkA/6vXe4X8ZbnzlHC/IbwVF2akL38cZsSfWBzWooM1QFSCjBzcqvyf3DJ7T8dXTR1pepH8s1No3IA=
Received: by 10.67.15.15 with SMTP id s15mr5088164ugi.1183984381261;
	Mon, 09 Jul 2007 05:33:01 -0700 (PDT)
Received: from ?9.159.130.24? ( [195.212.29.179])
	by mx.google.com with ESMTPS id u56sm1243891uga.2007.07.09.05.32.54
	(version=SSLv3 cipher=RC4-MD5); Mon, 09 Jul 2007 05:32:55 -0700 (PDT)
Message-ID: <46922AF7.5090308@gmail.com>
Date: Mon, 09 Jul 2007 14:32:55 +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>	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>	<469218B7.8060108@cisco.com>	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<46922300.6020101@spaghetti.zurich.ibm.com>
In-Reply-To: <46922300.6020101@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: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org, Eliot Lear <lear@cisco.com>
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-07-09 13:58, Jeroen Massar wrote:
...
> 
> Now I do see another use for this kind of address space, but then it
> should not be called this way. It could be used for ID/LOC solutions,
> where these kind of addresses are Explicit-non-DFZ addresses. But if
> that is the reason for what folks want to use them, as that is what I am
> sort of reading between the lines as actual real usage has still not
> been identified, then please just state that.

I believe that ULA-G as proposed by Paul is an interesting candidate
for unrouteable EIDs in the sense that the LISP proposal defines "EID".
But that conversation belongs on another list.

However, if we're worried about keeping /48s out of the DFZ, I agree
that it really doesn't matter whether they're called "PI", "ULA",
"2002::/48" or simply /48 holes in PA prefixes. It's the ISPs who
will keep them out, or let them in, not the IETF.

     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 Jul 09 08: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 1I7smY-0003Kr-5a; Mon, 09 Jul 2007 08:56:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7sm9-0002zb-BT
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:55:37 -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 1I7sm8-0006c3-KD
	for ipv6@ietf.org; Mon, 09 Jul 2007 08:55: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 5DE03140C1EE;
	Mon,  9 Jul 2007 14:55:35 +0200 (CEST)
Message-ID: <4692304C.7080305@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 13:55:40 +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>	<46782E58.6070705@spaghetti.zurich.ibm.com>	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>	<469218B7.8060108@cisco.com>	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<46922300.6020101@spaghetti.zurich.ibm.com>
	<46922AF7.5090308@gmail.com>
In-Reply-To: <46922AF7.5090308@gmail.com>
X-Enigmail-Version: 0.95.2
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: b280b4db656c3ca28dd62e5e0b03daa8
Cc: ipv6@ietf.org
Subject: ULA-C being misnamed&misplaced,
	should be EID or similar (Was: 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="===============1383169703=="
Errors-To: ipv6-bounces@ietf.org

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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig76873A9C76942AC934CE63AC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Brian E Carpenter wrote:
> On 2007-07-09 13:58, Jeroen Massar wrote:
> ...
>>
>> Now I do see another use for this kind of address space, but then it
>> should not be called this way. It could be used for ID/LOC solutions,
>> where these kind of addresses are Explicit-non-DFZ addresses. But if
>> that is the reason for what folks want to use them, as that is what I =
am
>> sort of reading between the lines as actual real usage has still not
>> been identified, then please just state that.
>=20
> I believe that ULA-G as proposed by Paul is an interesting candidate
> for unrouteable EIDs in the sense that the LISP proposal defines "EID".=

> But that conversation belongs on another list.

I fully agree with this and I also support this route. But then don't
call them ULA or assign them any functionality in this area which is
completely misleading. Call the beast what it is supposed to be called.

> However, if we're worried about keeping /48s out of the DFZ, I agree
> that it really doesn't matter whether they're called "PI", "ULA",
> "2002::/48" or simply /48 holes in PA prefixes. It's the ISPs who
> will keep them out, or let them in, not the IETF.

Indeed. If we are going to carve a block out which should never show up
in routing tables (except maybe site internal ones etc), then give them
the name that they should have and the description that they should have.=


Assigning this /8 as something which is not PI but is PI is only
ambiguous. Giving them the a name like "EID" and stating that these are
not to be used for routing in the DFZ, but can be used globally with the
help of an upcoming protocol which does an ID/LOC split does make sense.
It then all of a sudden is also logical that these blocks will need
reverse DNS delegations, as they will be used _on_ the Internet, but
just not _routed_ on the Internet.

IMHO it is thus much better to put this ULA-C proposal on ice and await
the requirements and structure that that the upcoming ID/LOC proposal.

Although, I guess that they will be quite like what Paul proposed in
delegation structure, but the description of the addresses and the name
will be different and more appropriate to what they will be actually
used for.

The above is also why I say "/48's are not a big problem", as when the
routing tables get too large, ISP's will start filtering, forcing the
/48 PI users to start using their address space as EID's. Having a
special block which solely restricts this is of course a good thing. The
RIR's can then easily explain "these kind are EID's and are 'cheap',
while these kind are accepted in the DFZ". Now what the RIR's policies
will be on who can get what kind of addresses is of course to be
questioned and something the RIR's will have to fight out with their
membership.

Greets,
 Jeroen


--------------enig76873A9C76942AC934CE63AC
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/

iHUEARECADUFAkaSMEwuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I2mCAJ905MqlTnQ41k0H1z53Za+1iOIC
GgCeMqnkcvVscS9zC6flqG9GQk/ihaU=
=ZO3t
-----END PGP SIGNATURE-----

--------------enig76873A9C76942AC934CE63AC--


--===============1383169703==
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
--------------------------------------------------------------------

--===============1383169703==--




From ipv6-bounces@ietf.org Mon Jul 09 09:08: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 1I7syK-0007ez-IB; Mon, 09 Jul 2007 09:08:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7sxt-0007bW-9y
	for ipv6@ietf.org; Mon, 09 Jul 2007 09:07:45 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7sxs-000736-RS
	for ipv6@ietf.org; Mon, 09 Jul 2007 09:07:45 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 09 Jul 2007 15:07:17 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FANLPkUaQ/uCLh2dsb2JhbACBSWI2iV+CdAEBCQ4s
X-IronPort-AV: i="4.16,517,1175464800"; d="scan'208,217";
	a="147573746:sNHT4347967868"
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 l69D7H7L020370; 
	Mon, 9 Jul 2007 15:07:17 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp4200.cisco.com
	[10.61.80.103])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l69D7ETC009419; 
	Mon, 9 Jul 2007 13:07:16 GMT
Message-ID: <469232FF.8040609@cisco.com>
Date: Mon, 09 Jul 2007 15:07:11 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
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>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1982; t=1183986437;
	x=1184850437; 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=20draft-ietf-ipv6-ula-central-02.txt
	|Sender:=20; bh=uve6QKyxmwoEOCm0YB4EfDuRRQ14N940T2sYOwLFlh8=;
	b=kd/y8z8bSnZpKwcBOLc8zYLXnmrF4mhsQmXg6LbfbxnE0ycv4HlsCTbviB2FpTl5gb6ZM0hY
	QWm2ZMnvvao+T23SNHuNYcahfVXvS1JOXuzBZrBo7cYehK+K0X63vPGe;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
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="===============1203215013=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1203215013==
Content-Type: multipart/alternative;
	boundary="------------000101060808070506070403"

This is a multi-part message in MIME format.
--------------000101060808070506070403
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Having had my name on RFC 1918, I think understand some of the issues.  
There is precisely one that I find at all interesting in this proposal, 
having stated the concern in RFC 1627:

    * avoiding collisions, and Geoff Huston's math demonstrates the
      likelihood of that happening

But one needn't have reverse lookups delegated in the root to address 
this concern.

I also understand something about the differences between ULA-C and RFC 
1918.  For one, this space will be unique within the limits of human 
error.  RFC 1918 not being unique meant that providers really had no 
choice about blocking it, and IANA had no method to insert reverse 
addresses to a particular site.

Eliot

--------------000101060808070506070403
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Having had my name on RFC 1918, I think understand some of the issues.&nbsp;
There is precisely one that I find at all interesting in this proposal,
having stated the concern in RFC 1627:<br>
<br>
<ul>
  <li>avoiding collisions, and Geoff Huston's math demonstrates the
likelihood of that happening</li>
</ul>
But one needn't have reverse lookups delegated in the root to address
this concern.<br>
<br>
I also understand something about the differences between ULA-C and RFC
1918.&nbsp; For one, this space will be unique within the limits of human
error.&nbsp; RFC 1918 not being unique meant that providers really had no
choice about blocking it, and IANA had no method to insert reverse
addresses to a particular site.<br>
<br>
Eliot<br>
</body>
</html>

--------------000101060808070506070403--


--===============1203215013==
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
--------------------------------------------------------------------

--===============1203215013==--




From ipv6-bounces@ietf.org Mon Jul 09 10:11: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 1I7tw8-0002Wn-Ba; Mon, 09 Jul 2007 10:10:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7tw6-0002We-MF
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:09:58 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7tw5-0008NU-NP
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:09:58 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2007 10:09:53 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAB7ekUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,517,1175486400"; 
	d="scan'208"; a="64683598:sNHT84103356"
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 l69E9rU7016951; 
	Mon, 9 Jul 2007 10:09:53 -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 l69E9Q70023131; 
	Mon, 9 Jul 2007 14:09:53 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); 
	Mon, 9 Jul 2007 10:09: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: Mon, 9 Jul 2007 10:09:43 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <468E98D7.5060109@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: AcfABY+8RBLo3aMzTEigg9JoQ+p/+QACy2FA
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 09 Jul 2007 14:09:44.0323 (UTC)
	FILETIME=[CCC90D30:01C7C232]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=22616; t=1183990193;
	x=1184854193; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=fgPK5x7d0C4g3PHC0vcZsjWrnufvCc45lrQ/plGXsXU=;
	b=IxsJYp0Gc2ZS2FSkSaKKf3bcbEyXmZjse88ewrmGwHDTH8JPTZfFrPaZWbNBD7bjwk/k1Xw+
	Hv0UHDDA812rLiM0yAANbfmLcnJd0DE/D/fz1HE9takEr5vJMsNuEUgP;
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: b38aee91eedbacb27d28d558bc16c035
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

Vlad,

Please see in line below with "<hs>".=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Friday, July 06, 2007 3:33 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hi Hemant

Hemant Singh (shemant) wrote:
> Vlad,
>=20
> <vy>
> I believe that you are reading too much into section 3.1.  That=20
> section simply does a comparison to IPv4.  It does not mandate=20
> anything and doesn't not specify any specific beavhior.  That is saved
for later.
>=20
> <hs> Totally agree with you. We want to just add a new line or two to=20
> the relevant para in section 3.1 where the new lines say "go to a=20
> section further down in the document for concrete details."  Note that

> we simply state that this should be made explicit - but in our=20
> introduction, we do not specify exactly how.  For more information on=20
> how we wish to be more explicit, see the changes to 2461bis and=20
> 2462bis sections.

OK.

> > </vy>
>=20
>    These implications in RFC 2461 [ND] need to be made explicit.
>    Failure of host implementations to comply can result in lack of
IPv6
>    connectivity.  For example, a host receives an RA with no prefix
>    advertised and incorrectly decides to perform address resolution
when
>    the host should have sent all traffic to the default router.  The
>    router may not respond to the address resolution and the layer 2
>    driver of the host stops transmitting IPv6 packets.
>=20
> <vy>
> Are these meant to describe 2 different scenarios or just one? =20
>=20
> <hs> Just one scenario. A router may not respond to the NS issued by=20
> host to resolve the packet destination. That causes the host's L2=20
> driver to just sit there. The net result is no packets get out of the
host.

As I said bellow, both implementation violate the specs.  At this point,
not sure if clarifying the spec by placing additional restrictions is
useful.  Submitting bugs against the implementation is probably better.

<hs> At least in the Introduction section of our I-D, we are just giving
a flavor of the serious nature of IPv6 ND problems. Before we wrote our
I-D, we submitted bugs against the implementation. We have to clarify
2461bis in the areas of data forwarding and address resolution because
some suble behavior can cause major problems in the network. We have
already discussed one serious problem in this mailer. If a host assumed
a /64 prefix length when the host wasn't supposed to assume any prefix
length and added the prefix to the Prefix List, the host would perform
address resolution when instead the host could have considered the
prefix to be off-link and sent data to the default router. As we said
before, the router may not respond to the NS and such a host can loose
IPv6 connectivity. See how a simple assumption caused a serious problem.
That is why we have to make 2461bis more strict in such areas. Our goal
is also to not add any additional requirement over 2461bis.=20

>=20
> If only one, both implementations violate multiple aspects of the=20
> protocol.
> </vy>
> <hs> OK, we will change MUST NOT to SHOULD NOT to allow for clever=20
> implementations. One thought we had was that DHCPv6 clients can=20
> certainly change address across IPv6 interface initializations - that=20
> is what prompted us to this rule having enforced it for SLAAC clients=20
> as well. The new bullet text follows:
>=20
> "1. On-link determination SHOULD NOT persist across IPv6 interface
"On-link determination state SHOULD NOT persist..."

Makes it a little more clear what you are saying.  Otherwise, looks fine
to me.


> <hs> We noticed this one too and have made a change to this bullet.
> Please see if the new text below for this bullet makes sense to you.
>=20
> ---------------
>    "2. The on-link definition in section 2.1 of
>        draft-ietf-ipv6-2461bis-11 [NDbis] describes the only means 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.  Note
>        that the on-link definition as specified by
>        draft-ietf-ipv6-2461bis-11 [NDbis] does not include manual
>        configuration."
> -----------------

OK.

>=20
>    3.  The host MUST NOT add a direct delivery route to the prefix
from
>        an assigned address, independent of the information about the
>        prefix received from the RA or Redirects.
> <vy>
> Can you please explain what exactly you mean here.  I am having=20
> difficulty properly understanding this sentence.
> </vy>
>=20
> <hs> In this regard, we describe the issue hosts have when hosts=20
> incorrectly add a directly connected route to a /64 prefix from an=20
> address assigned to an interface, even if the prefix is advertised as=20
> "not on-link" or not advertised at all. The host incorrectly assumed a
> /64 prefix length.
> After assuming the prefix length, the host added a directly connected=20
> route entry for such a prefix to the host forwarding tables. The=20
> incorrectly added route causes the host to try to use direct delivery=20
> (without sending traffic to the default router) and, therefore, use=20
> NS/NA to resolve addresses from the same prefix.

So, here the implementor completely disregarded either the section about
the L-bit being 0 doesn't mean off-link, or the section at the top of
page
19 of 2462bis to not expect all IIDs to be 64 bit and thus assume a 64
bit prefix.

I guess a final "On-Link Determination" section might help.

<hs> We are working on details on how to incorporate clarifications from
our I-D into 2461bis. We are open right now for a new section.

However, these types of errors are typical of the manual configuration
and there is not much we can do here.

<hs> No, in our testing, we did NOT use manual configuration and still
the host behaved in a non-compliant fashion.  We recognize that manual
configuration can introduce additional problems.  We have already
identified manual configuration in our I-D as potentially introducing
problems -
see the last sentence of bullet 2 of section 2 in our I-D.

>=20
>=20
>    5.  The host SHOULD issue only a single NS(DAD) for each address.
>        The default value for DupAddrDetectTransmits variable is
>        specified as 1 in section 5.1 of RFC 2462 [ADDRCONF].
>=20
> <vy>
> What exactly are you trying to address with this text?  When I read=20
> it, my first impulse is to assume that you want to limit the number of

> DAD Soliciations to 1 per address, which is not really correct and is=20
> _probably_ not what you mean.  Can you explain a little more.
> </vy>
>=20
> <hs> Not quite. This bullet hasn't changed in our I-D from the=20
> definition of DupAddrDetectTransmits in 2462bis. Section 5.1 of=20
> 2462bis clearly says default value of this variable is 1. Then the=20
> section goes on to say the value can be overriden by a linktype=20
> specific value. That is why we say in our I-D, the host SHOULD issue=20
> only single NS(DAD) because the default is 1. The SHOULD also caters=20
> to any other value being used. We found an interesting behavior in an=20
> IPv6 cable modem host stack. The modem was sending 4 NS(DAD)'s for=20
> Link-local address and 5 NS(DAD)'s for DHCPv6 address.

REALLY???  Unless the modem was explicitly configured to do this, I
don't see how the text you recommend would fix this glaring error...  In
fact, I could claim that this behavior would still be within spec if the
manufacturer or operator determines that they want this behavior.

<hs> We also told the modem vendor their behavior is compliant with ND
RFC but since bandwidth is limited in a broadband deployment in the
upsteam direction (modem to the aggregation router), having each modem
issue 9 DAD's before the modem got online was a waste of valuable
bandwidth resource. As 2462bis says, it's up to a link-type document to
modify this value. Aggregation router standards will have to take care
of specifying such a value for broadband deployments IF they choose to
use a different value than the default value of 1.

So the new text you are introducing would be completely nullified.

<hs> True. Our aim with this bullet is to only raise an awareness that
default value is 1. Many new IPv6 host developers just read 2461bis and
miss the default value of this variable that is not specified in
2461bis, but is specified in 2462bis.

>=20
> <hs> Agreed. We have to make rules tighter here. Please see the new=20
> bullet below:
>=20
> ----------------
>     "6. Newer implementations, which are compliant with
>        draft-ietf-ipv6-rfc2461bis-11 [NDbis] MUST adhere to the
>        following rules.  Older implementations, which are compliant
with
>        RFC 2461 [ND] but not draft-ietf-ipv6-rfc2461bis-11 [NDbis] may
>        remain as is.  If the Default Router List is empty and there is
>        no other source of on-link information about any address or
>        prefix:
>=20
>        1.  The host MUST NOT assume that all destinations are on-link.
>=20
>        2.  The host MUST NOT perform address resolution for non-link-
>            local addresses.
>=20
>        3.  The host SHOULD send an ICMPv6 Destination Unreachable
>            message instead.
>=20
>        On-link information concerning particular addresses and
prefixes
>        can make those specific addresses and prefixes on-link, but
does
>        not change the default behavior mentioned above for addresses
and
>        prefixes not specified.  draft-ietf-v6ops-onlinkassumption-04
>        [I.D.ietf-v6ops-onlinkassumptions] provides justification for
>        these rules."
> -----------------------

Ok, the text is clearer, but it reads like an over-specification to me.

<hs> We don't think it's over specification. If a host misses first rule
and assumes destinations are on-link, the data delivery break-down can
happen with the host. Bullets 1 and 3 are as is from
draft-ietf-v6ops-onlinkassumption-04.

So many of the issues that you've found have to do with improper
implementation of on-link determination that I am really starting to
thing that a single section on clarifying it would be useful in your
daft.

<hs> Yes, we are putting together such a section.


>=20
> 2.1.  RA Sets M and O Bits but does not Include the Prefix Information
>       Option (PIO)
>=20
> [... draft text snipped ...]
>=20
>    An IPv6 router sends an RA with no prefix advertised and the M and
O
>    bits set and does not send any Redirects.  On receipt of the RA,
the
>    host uses DHCPv6 to acquire an IPv6 address.  After completing IPv6
>    address acquisition, the host MUST obey RFC 2461 [ND], section 3.1.
>    Since the RA is the only authority to a host for on-link
>    determination and this RA does not advertise any prefix, the host
>    cannot determine that a destination is on-link.  Therefore, the
host
>    MUST adhere to the following rules:
>=20
>    1.  The host MUST NOT assume any default prefix length.
>=20
>    2.  The host MUST send all non-link-local traffic to the default
>        router.
>=20
>    3.  The host MUST NOT issue an NS to resolve a destination other
than
>        a link-local address.
>=20
> <vy>
> One can argue that a host/DHCP client that inferes a prefix length=20
> from a leased address is prone to other failures as well.  In this=20
> case, it's the DHCP client that is most likely a problem, unless the=20
> host implementation mistakenly alwasy assumes /64 length.  I think=20
> this is actually warned against in the Address Architure document.
>=20
> <hs> The host implementation has assumed a /64 length in the tests we=20
> did.

Yes, and 2462bis weasel words around this issue at the top of page 19.
Maybe a "should" there needs to be changed to a "SHOULD"?

<hs> Which words are you talking about? Quick look at 2462bis and even
2461bis on page 19 did not show us any relevant words.

>=20
> 2461bis clearly states that a set 'L' flag is the only determination=20
> of on-link.  Anything else you can report to your vendor as "Bug".
>=20
> The above actually would be a very good test to add to the TAHI=20
> conformance test suite.
> </vy>
>=20
> <hs> I contacted TAHI on May 16th, 2007 to add such a test case to the
> IPv6 conformance test suite. On June 19th, 2007, someone replied. I=20
> have to work with them to make sure this test is added to their test
suite.

OK.  That would be good.

>=20
> 2.2.  RA Advertises a Prefix with the On-link(L) Bit Set
>=20
> [... draft text sniped ...]
>=20
>    Consider the following scenario with one rogue node and two other
>    hosts on the same link.  The rogue sends a malicious RA with an on-
>    link prefix with a Valid Lifetime of zero.  Host1 correctly
>    implements section 5.5.3 of RFC 2462 [ADDRCONF] and resets its
>    StoredLifetime (or RemainingLifetime in
draft-ietf-ipv6-rfc2462bis-08
>    [ADDRCONFbis]) to two hours and avoids the denial of service
attack.
>    Host1 tries to send traffic to Host2, but cannot trust its own two
>    hour StoredLifetime.  For instance, a legitimate operator may have
>    tried to time out the prefix due to an impending renumbering.
Host1
>    decides to send all of its traffic to the on-link authority, the
>    default router, even though the destination prefix is on-link.
>=20
>    IF the host decides to send all traffic (including on-link traffic)
>    to the default router, then the host MUST follow the following
rule:
>=20
>    1.  The host MUST NOT issue an NS to resolve a destination other
than
>        a link-local address.
>=20
> <vy>
> This is kind of reduntant.  The host can either determine that the=20
> destination is on-link (i.e it trusts its prefix list), or it sends it

> to the default router.  The only time it would preform NS would be for

> on-link determination which means that it trust the prefix list.
> I don't see any further need to call out this particular scenario.
> </vy>
>=20
> <hs> Before we added these rules, one reviewer complained that we had=20
> rules in all the other sections, but not this one.  Therefore, we=20
> added the rules to satisfy the reviewer.  As for the scenario, this=20
> scenario allows a host to send all traffic to the default router even=20
> for a prefix advertised as on-link.  This is very important if we want

> to describe ALL the behavior possible with respect to on-link=20
> determination.

OK.

>=20
> 2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear

> <hs> You are correct. We changed our I-D for this section - see=20
> changed text below:
>=20
> "2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear An on-link

> bit of clear indicates nothing regarding on-link determination. In=20
> section 6.3.4 of draft-ietf-ipv6-rfc2461bis-11 (Narten, T., Nordmark,=20
> E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP Version 6=20
> (IPv6)," March 2007.) [NDbis]":
>=20
> "...a Prefix Information Option with on-link flag set to zero conveys=20
> no information concerning on-link determination and MUST NOT be=20
> interpreted to mean that addresses covered by the prefix are=20
> off-link.... Prefixes with the on-link flag set to zero would normally

> have the autonomous flag set and be used by [ADDRCONF]."
> "

OK.

>=20
>=20
> 3.1.  Aggregation Router Deployment Model
>=20
>    No NS to resolve any address other that that of the default router
>    will reach the aggregation router from any device on the customer
>    side of the aggregator.  CPEs do not communicate with each other in
>    this deployment model since a CPE does not run any applications
that
>    need to communicate with other CPEs.  Hosts do communicate with
each
>    other, but every host is off-link to any other host on the
>    aggregation router.
>=20
> <vy>
> Yes, they are off-link.  So why would they thing their are on-link?
> Each CPE Rtr or Cust Rtr whould have it's own prefix that would be=20
> advertized to the CPE hosts.  Therese prefixes would aggregate
> at the Agregator.   Why would NSs from the CPE hosts escape?
> </vy>
>=20
> <hs. True the NS's from CPE hosts would not escape. We are just=20
> highlighting a deployment design such that the aggregator in the=20
> deployment will not have to support ND Proxy.

OK.  But you are going about it by using keyword language (use of SHOULD
in that section).  It just felt odd.  I had to re-read the section a few
times and just couldn't understand the point.  It seemed obvious.

<hs> Our intent for this section is to describe properties of an
aggregation network and not specify any normative changes. We will
change the "SHOULD NOT" to "should not".

>=20
> 5.  Changes to draft-ietf-ipv6-rfc2461bis-11
>=20
> <vy>
> No, this is the wrong section to include such requirements since the=20
> section currenlty doesn't place any specific requirements on the=20
> implementation.
> </vy>
>=20
> <hs> Agreed. We will put the strict text elsewhere in 2461bis and just

> add a reference in this para to that stricter text.

Yes, this is the same as the first issue.  References are always better.
:)

>=20
> 6.  Changes to draft-ietf-ipv6-rfc2462bis-08
>=20
> [... old text snipped ...]
>=20
>    to read as follows:
>=20
>       Each individual unicast address SHOULD be tested for uniqueness.
>       Note that some deployed implementations perform Duplicate
Address
>       Detection (DAD) only for the link-local address and skip the
test
>       for the global address using the same interface identifier.
>       Whereas this document does not invalidate such implementations,
>       this kind of 'optimization' is NOT RECOMMENDED, and new
>       implementations MUST NOT do that optimization.  This
optimization
>       came from the assumption that all of an interface's addresses
are
>       generated from the same interface identifier (see RFC 2462
>       [ADDRCONF]).  However, even with this assumption, skipping DAD
for
>       non-link-local addresses with manual configuration creates an
>       additional problem.  This optimization allows an interface to
>       claim a duplicate address in a way that would not be detected.
>       For a more detailed description of this problem, see the Host
>       Models section of
>       draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
>       types of addresses have been introduced where the interface
>       identifiers are not necessarily the same for all unicast
addresses
>       on a single interface [RFC3041] [RFC3972].  Requiring an
interface
>       to perform DAD for all unicast addresses will make the algorithm
>       more robust.
>=20
> <vy>
> Two issues:
>  1. This text is not any stronger then the existing text in 2461bis
and
>     doesn't add anything significant.
>=20
> <hs> Yes it is. We have been told by a number of people that whether=20
> to skip DAD or not was discussed at length in the IETF IPv6 WG and
mailer.
> If so much discussion happened and RFC 2462 changed in 2462bis I-D to=20
> remove the skipping DAD requirement for newer hosts, we'd like to see=20
> the reasons for the change. The only reason we found in 2462bis for=20
> the change was:
>=20
>       "new types of addresses have been introduced where the
>       interface identifiers are not necessarily the same for all
unicast
>       addresses on a single interface [RFC3041] [RFC3972]."
>=20
> Well, we provided an example scenario in our I-D (section 2, bullet 4)

> that highlights that fact the skipping DAD combined with manual=20
> configuration can result in duplicate addresses on the same link which

> are not detected.

The example you provide has been documented in the Neighbor Discover
Threats spec (rfc 3756).  So that's documented fairly well.  The
Security Consideration section also references it and points out issues
with DAD.

<hs> No, we disagree that the problem we have highlighted in bullet 4 of
our I-D is mentioned anywhere in RFC 3756 - you will have to point it
out to us.  Our problem is saying mixing "skipping DAD" and manual
configuration is a bad idea and also shows that even if Link-local
address and Global Unique Address (GUA) of the host are created from the
same identifier (Host2 in our example), one will have duplicate
addresses on the link that would not be detectable. Further, this
problem is detectable if DAD is not skipped for the GUA by Host2. The
duplicate will be detected because even Host1 is a compliant host in our
model, not a rogue host. Please see an earlier email discussion between
ourselves and Tataya on this one.

The only thing that _might_ be missing is a reference to such threats
from withing the DAD section, as additional rational for not skipping
DAD, but that's fairly weak.

>=20
> My conlcusion:
>=20
> After re-reading 2461bis and 2462bis multiple times as result of=20
> reviewing this draft, I can see some small value in creating an=20
> "On-Link Determination"
> section in draft 2461bis.
>=20
> Alternatively, this draft should crate such section and, with=20
> references to text in 2461bis, should clarify the on-link
determination behavior.
> It could then be issued as an update.
>=20
> <hs> We are preparing text with regards to additional changes to=20
> 2461bis to add to Section 5 of our I-D.  We're glad that you agree=20
> that on-link determination as described by the current specifications=20
> can be confusing.
>=20

One thing I've noted is that you have the _same_rules_ in almost every
section.
What I am proposing is that you restructure the text a little.

In each section describe some inconsistencies or behaviors that you've
seen as non-compliant.  Don't add rules to each section.  Instead have
one section where you clarify the behavior using requirement keywords.
Since most issues are centered around on-link determination, that should
be fairly easy.

<hs> We'll think about it and get back to you.

Thanks.

- Hemant & Wes.

-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 Jul 09 10:14: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 1I7u0N-0006zr-9u; Mon, 09 Jul 2007 10:14:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7u0L-0006w6-Av
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:14:21 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7u0G-0000Ir-UG
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:14:21 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2007 10:14:09 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAEvfkUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,517,1175486400"; 
	d="scan'208"; a="64684258:sNHT3760332026"
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 l69EE9db002741; 
	Mon, 9 Jul 2007 10:14:09 -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 l69EDesI028316; 
	Mon, 9 Jul 2007 14:14:08 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, 9 Jul 2007 10:14:03 -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, 9 Jul 2007 10:14:02 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A8B2@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1r6nhkdsv.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: release candidate of 2462bis (Re: Revisit: one remaining
	cornercase in DAD)
Thread-Index: AcfCHdzq038w4xsuRXmaqije5djiqAAFPVgg
References: <468E730F.8090409@hp.com><8E296595B6471A4689555D5D725EBB21046B02CB@xmb-rtp-20a.amer.cisco.com><m2vecx8kvg.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1r6nhkdsv.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>, <ipv6@ietf.org>
X-OriginalArrivalTime: 09 Jul 2007 14:14:03.0063 (UTC)
	FILETIME=[6701A470:01C7C233]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1916; t=1183990449;
	x=1184854449; 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=20release=20candidate=20of=202462bis=20(Re=3A=20Revisit
	=3A=20one=20remaining=20cornercase=20in=20DAD) |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=20<ipv6@ietf.org>;
	bh=OyZF5VECY+C+4dnnN+O/BylsH8KpvWZqkrDrHrrQgdA=;
	b=n2nXsTod+kuoBL5wbLE2Se4pz4k6L3i7EqWhnNVPHoZ6TiqQKKB/ZSmbfuD1cMYVoCFy0jce
	Jm1bXBm/NbxewEyoHTiEJiK2GU9eidpAC1OLB0CCwQtOkVzNkAhAe5uR;
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: 
Subject: RE: release candidate of 2462bis (Re: Revisit: one remaining
	cornercase in DAD)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

We take it, after your recent changes to 2462bis -08 version, some day
soon this I-D will become a new RFC (say RFC xxxx). So when can we
expect to add updates to the new RFC?
Will you start a another xxxxbis right after this one is published?
When will the IPv6 working group be closed?  Will there be any provision
for incorporating late-breaking changes?

- Wes

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Monday, July 09, 2007 7:38 AM
To: ipv6@ietf.org
Subject: release candidate of 2462bis (Re: Revisit: one remaining
cornercase in DAD)

At Sat, 07 Jul 2007 03:09:23 +0900,
JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp> wrote:

> I tend to agree (I also thought this as an option myself).  Thanks for

> the suggestion.

I've updated the AUTH48 version of rfc2462bis with this fix.  Other
(major) changes since the latest version of I-D (rfc2462bis-08) are:

- Updates to RFC references:
  + RFC3041 -> RFC4941 (which will be published at the same timing)
  + RFC3513 -> RFC4291

- Wording clarification about interface identifiers
  (see discussion in the thread that began with this post:
  http://www1.ietf.org/mail-archive/web/ipv6/current/msg05163.html)

Note that I didn't include any change about the strictness of DAD.  I
didn't see any consensus on including that at this very final stage.

I'm about to submit this version to the RFC editor, but a copy of the
release candidate is available here:=20

http://www.jinmei.org/rfc4862-candidate.txt

just in case.

					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 Mon Jul 09 10:38: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 1I7uNU-00086j-Np; Mon, 09 Jul 2007 10:38:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uNT-00086C-D6
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:38:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7uNT-0000fk-4J
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:38:15 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 09 Jul 2007 16:38:13 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAACblkUaQ/uCKh2dsb2JhbACBSY1rAQEJDiw
X-IronPort-AV: i="4.16,517,1175464800"; 
	d="scan'208"; a="147586482:sNHT60539602"
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 l69EcALj032596; 
	Mon, 9 Jul 2007 16:38:10 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp4200.cisco.com
	[10.61.80.103])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l69Ec7TC012854; 
	Mon, 9 Jul 2007 14:38:10 GMT
Message-ID: <4692484C.70808@cisco.com>
Date: Mon, 09 Jul 2007 16:38:04 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604)
MIME-Version: 1.0
To: Paul Vixie <paul@vix.com>
References: <80699.1183408066@sa.vix.com>	<3838.10.31.30.119.1183656859.squirrel@stiedprstage1>	<45323.1183663849@sa.vix.com>	<1520.156.154.5.45.1183678997.squirrel@stiedprstage1>	<89916.1183680829@sa.vix.com>	<2617.10.31.30.119.1183742189.squirrel@stiedprstage1>
	<19501.1183769994@sa.vix.com>
In-Reply-To: <19501.1183769994@sa.vix.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=163; t=1183991890;
	x=1184855890; 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=20draft-ietf-ipv6-ula-global-01.txt
	|Sender:=20; bh=mWFsuRZJ5IY8vxk2vi6EGLFtQX0OIi0wj0HlRcIt4FQ=;
	b=EF5izAkaGRKkhhoiTTpzQRtLnSg7M2GbFVJEAOmFjRNsqgWdDP+MyDQnKNb8qKmvIKE6Xn9w
	ThZhQZ0IqqHnexZhrb0V8mHaehDZFb+gt4s8lJwNOpJs23/kCLMTRK0H;
Authentication-Results: ams-dkim-1; header.From=lear@cisco.com; dkim=pass (s
	ig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: draft-ietf-ipv6-ula-global-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

Paul,

Can you please include at least a base justification for ULA-G over PI 
that is distinct from the random ULAs that can now be used?

Thanks,

Eliot


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



From ipv6-bounces@ietf.org Mon Jul 09 10:46: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 1I7uUv-0000Eu-E5; Mon, 09 Jul 2007 10:45:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uUt-0000Eb-EI
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:45:55 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7uUo-0001Hd-Qc
	for ipv6@ietf.org; Mon, 09 Jul 2007 10:45:55 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel9.hp.com (Postfix) with ESMTP id EAC573507E;
	Mon,  9 Jul 2007 10:45:29 -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 4386C18F4B7;
	Mon,  9 Jul 2007 14:45:29 +0000 (UTC)
Message-ID: <46924A07.4030504@hp.com>
Date: Mon, 09 Jul 2007 10:45:27 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.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: c54bc2f42d02429833c0ca4b8725abd7
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

Hi Hemnat

Hemant Singh (shemant) wrote:
> <hs> We also told the modem vendor their behavior is compliant with ND
> RFC but since bandwidth is limited in a broadband deployment in the
> upsteam direction (modem to the aggregation router), having each modem
> issue 9 DAD's before the modem got online was a waste of valuable
> bandwidth resource. As 2462bis says, it's up to a link-type document to
> modify this value. Aggregation router standards will have to take care
> of specifying such a value for broadband deployments IF they choose to
> use a different value than the default value of 1.
> 
> So the new text you are introducing would be completely nullified.
> 
> <hs> True. Our aim with this bullet is to only raise an awareness that
> default value is 1. Many new IPv6 host developers just read 2461bis and
> miss the default value of this variable that is not specified in
> 2461bis, but is specified in 2462bis.

IMO this is already fairly well spelled out in 2461bis.  There was talk
earlier on the list of adding something along the list of:
    This document RECOMMENDS that implementations use default values specified
    here.

I don't remember what happened to that, but that should do what you want.
> 
> <hs> Yes, we are putting together such a section.
> 

OK. I'll wait for the new text.

> 
> Yes, and 2462bis weasel words around this issue at the top of page 19.
> Maybe a "should" there needs to be changed to a "SHOULD"?
> 
> <hs> Which words are you talking about? Quick look at 2462bis and even
> 2461bis on page 19 did not show us any relevant words.

      Note that a future revision of the address architecture [RFC3513]
      and a future link-type specific document, which will still be
      consistent with each other, could potentially allow for an
      interface identifier of length other than the value defined in the
      current documents.  Thus, an implementation should not assume a
      particular constant.  Rather, it should expect any lengths of
      interface identifiers.

I suggest the 'should' in the last sentence be replaced by SHOULD.

>> 6.  Changes to draft-ietf-ipv6-rfc2462bis-08
>>
>> [... old text snipped ...]
>>
>>    to read as follows:
>>
>>       Each individual unicast address SHOULD be tested for uniqueness.
>>       Note that some deployed implementations perform Duplicate
> Address
>>       Detection (DAD) only for the link-local address and skip the
> test
>>       for the global address using the same interface identifier.
>>       Whereas this document does not invalidate such implementations,
>>       this kind of 'optimization' is NOT RECOMMENDED, and new
>>       implementations MUST NOT do that optimization.  This
> optimization
>>       came from the assumption that all of an interface's addresses
> are
>>       generated from the same interface identifier (see RFC 2462
>>       [ADDRCONF]).  However, even with this assumption, skipping DAD
> for
>>       non-link-local addresses with manual configuration creates an
>>       additional problem.  This optimization allows an interface to
>>       claim a duplicate address in a way that would not be detected.
>>       For a more detailed description of this problem, see the Host
>>       Models section of
>>       draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
>>       types of addresses have been introduced where the interface
>>       identifiers are not necessarily the same for all unicast
> addresses
>>       on a single interface [RFC3041] [RFC3972].  Requiring an
> interface
>>       to perform DAD for all unicast addresses will make the algorithm
>>       more robust.
>>
>> <vy>
>> Two issues:
>>  1. This text is not any stronger then the existing text in 2461bis
> and
>>     doesn't add anything significant.
>>
>> <hs> Yes it is. We have been told by a number of people that whether 
>> to skip DAD or not was discussed at length in the IETF IPv6 WG and
> mailer.
>> If so much discussion happened and RFC 2462 changed in 2462bis I-D to 
>> remove the skipping DAD requirement for newer hosts, we'd like to see 
>> the reasons for the change. The only reason we found in 2462bis for 
>> the change was:
>>
>>       "new types of addresses have been introduced where the
>>       interface identifiers are not necessarily the same for all
> unicast
>>       addresses on a single interface [RFC3041] [RFC3972]."
>>
>> Well, we provided an example scenario in our I-D (section 2, bullet 4)
> 
>> that highlights that fact the skipping DAD combined with manual 
>> configuration can result in duplicate addresses on the same link which
> 
>> are not detected.
> 
> The example you provide has been documented in the Neighbor Discover
> Threats spec (rfc 3756).  So that's documented fairly well.  The
> Security Consideration section also references it and points out issues
> with DAD.
> 
> <hs> No, we disagree that the problem we have highlighted in bullet 4 of
> our I-D is mentioned anywhere in RFC 3756 - you will have to point it
> out to us.  Our problem is saying mixing "skipping DAD" and manual
> configuration is a bad idea and also shows that even if Link-local
> address and Global Unique Address (GUA) of the host are created from the
> same identifier (Host2 in our example), one will have duplicate
> addresses on the link that would not be detectable. Further, this
> problem is detectable if DAD is not skipped for the GUA by Host2. The
> duplicate will be detected because even Host1 is a compliant host in our
> model, not a rogue host. Please see an earlier email discussion between
> ourselves and Tataya on this one.

You are right.  I just re-read 3756 and this item is not there.  I would
agree to adding the rationale for why skipping DAD is not recommended.
Any additional text can be safely removed.

Something like:
   -  Each individual unicast address SHOULD be tested for uniqueness.
      Note that there are implementations deployed that only perform
      Duplicate Address Detection for the link-local address and skip
      the test for the global address using the same interface
      identifier as that of the link-local address.  Whereas this
      document does not invalidate such implementations, this kind of
      "optimization" is NOT RECOMMENDED, and new implementations MUST
      NOT do that optimization.  This optimization came from the
      assumption that all of an interface's addresses are generated from
      the same identifier.  However, the assumption does not actually
      stand; new types of addresses have been introduced where the
      interface identifiers are not necessarily the same for all unicast
      addresses on a single interface [RFC3041] [RFC3972].  Additionally,
      hosts that implement the "optimization" may end up configuring
      duplicate addresses and causing network disruptions.  Requiring to
      perform Duplicate Address Detection for all unicast addresses will
      make the algorithm robust for the current and future such special
      interface identifiers.

-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 Jul 09 11:06: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 1I7uoy-00041G-Sl; Mon, 09 Jul 2007 11:06:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uon-0003sj-Fa
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:06:29 -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 1I7uoj-0001v8-39
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:06:29 -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 l69F6FQd026329;
	Mon, 9 Jul 2007 08:06:21 -0700
Message-ID: <012601c7c23a$a7cfbe90$4f3816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Eliot Lear" <lear@cisco.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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
Date: Mon, 9 Jul 2007 09:53:20 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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: 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
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 "Eliot Lear" <lear@cisco.com>
> Stephen Sprunk wrote:
>> The supposed use case for ULA-C is large orgs who
>> interconnect privately with other large orgs.  If you _don't_
>> allow ULA-Cs in the global reverse DNS, then every org in
>> the internetwork must hack their local DNS servers to
>> recognize every other org's reverse DNS entries.  That is
>> painful and unnecessary.
>
> To borrow your logic, if this space is truly private why should
> this be an issue?

That hinges on the meaning of "private".  Imagine a private internet for the 
aviation industry; there would be thousands of players, each supposedly with 
their own ULA-C/G block.  Every player would need to hack their DNS servers 
to account for every other player's RDNS settings, and any time someone new 
joined or someone existing wanted to update their settings, thousands of 
other operators would need to change their hacks to keep things working. 
The odds of that being successful in practice are so low they're not worth 
considering.

>> There are operational concerns with putting ULA(-C)
>> addresses in  forward DNS; nobody argues with that. However, putting 
>> ULA-C addresses in reverse DNS harms
>> nobody who can't reach those addresses yet greatly
>> benefits those that can.
>
> The delegation must be maintained and occasionally updated. Who does that?

Whoever is designated as the central authority.  It is necessary for there 
to be a database to keep blocks unique, and that database will need billing 
and contact information, so the addition of a couple of NS entries for each 
block is trivial.  All we're discussing now is whether that information is 
exposed via the global DNS.

> At this point it is plain to see that ULA-C is nothing but PI
> address space, because the IETF is in no position to enforce
> otherwise.  So please, let's just call it what it is.

Exactly.

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 Jul 09 11:06: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 1I7uoy-000415-9H; Mon, 09 Jul 2007 11:06:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7uom-0003sZ-Kp
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:06:29 -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 1I7uoi-0001v7-8V
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:06:28 -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 l69F6FQc026329;
	Mon, 9 Jul 2007 08:06:21 -0700
Message-ID: <012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <michael.dillon@bt.com>, <ipv6@ietf.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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com><469218B7.8060108@cisco.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B0A46060@E03MVC4-UKBR.domain1.systemhost.net>
Date: Mon, 9 Jul 2007 09:48: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: 8b30eb7682a596edff707698f4a80f7d
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

Thus spake <michael.dillon@bt.com>
>> At this point it is plain to see that ULA-C is nothing but PI
>> address space, because the IETF is in no position to enforce
>> otherwise.  So please, let's just call it what it is.
>
> The IETF is not in a position to enforce the special handling of
> ULA-C addresses however, IANA via the RIRs is in such a
> position. The C in ULA-C refers to a central registry. It is likely
> that IANA will appoint the RIRs to handle that function. Since the
> RIRs only allocate numbers to organizations who sign a contract
> with the RIR, this places the RIR in a legal position to enforce
> any special rules that may be attached to ULA-C addresses.

Good grief.  The RIRs today cannot guarantee ULA-C addresses _won't_ be 
routed any more than they can guarantee PI/PA addresses _will_ be routed. 
You seem to be proposing a shift in RIR policy where anyone who doesn't play 
ball with arbitrary IETF rules get their allocations/assignments revoked... 
Sorry, but I'm not signing that contract, nor is anyone else.  It'd never 
pass community consensus.

> Essentially, the IETF is placing control over the route
> announcement question in the hands of those who are actually
> impacted by the question. If there is any dispute over the
> specifics of how this is handled, the RIRs are the forum in
> which it should be worked out.

RIRs have no power to do that today.  Routability of prefixes is solely in 
the hands of ISPs that accept (or not) those routes.  And we do _not_ want a 
world where some group of ivory tower academics and vendors tell operators 
what they _must_ do on their own networks.  The Internet is successful due 
to cooperation inspired by enlightened self-interest, not central control.

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 Jul 09 11:07: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 1I7upw-0004cZ-B6; Mon, 09 Jul 2007 11:07:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7upc-0004Lf-K0
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:07:21 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7upc-0001R6-7J
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:07:20 -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 l69F6FQe026329;
	Mon, 9 Jul 2007 08:06:22 -0700
Message-ID: <012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.no>, "Eliot Lear" <lear@cisco.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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com><469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
Date: Mon, 9 Jul 2007 10:05:45 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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.0 (/)
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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Mon, 9 Jul 2007, Eliot Lear wrote:
>> At this point it is plain to see that ULA-C is nothing but PI
>> address space, because the IETF is in no position to enforce
>> otherwise.  So please, let's just call it what it is.
>
> it is NOT the same, there are several differences and some
> of them are not technical but more manager/non-technical
> ways of viewing things.
>
> * PI are ment to be used on internet

No, PI is meant to be used anywhere IP is used.  A large fraction of PI 
space isn't routed on the Internet, and even in v4 there are several /8s 
that are used privately.

> * ULA-C/G are NOT ment to be used on internet

OTOH, there's no way for the IETF or RIRs to stop it from happening.  I'm 
not saying it will, but it is irresponsible to claim it won't when there's 
no mechanism to enforce that.

> * PI are the same as PA, there are NO real difference except
> on how you get it and the size of the block, it is what Paul Dixie
> have called UA (unique addresses), nothing else

PI vs PA merely depends on your perspective, i.e. whether you're the 
original recipient from the RIR.

> * ULA-C/G are something completly different, it is more like
> RFC1918 space with some extra features,
> - the size (amount of IPs)

This is a big disadvantage for ULA (of any flavor) space; you can get much 
bigger PI (or even PA) prefixes than the fixed /48 of ULA.

> - global unique so the current pain anyone with large network
> have when they are interconnecting, merging due to fusions or
> other reasons dont exist

That's no advantage over PI/PA space.

> - anyone can, IF the ULA-C/G holder want to, resolve the IP in
> any given ULA-C/G block through the global DNS system (a
> very very nice thing for everyone that hate the pain split-DNS
> give you...additional administration)

There's no consensus yet that ULA-C/G will appear in the global DNS.  PI/PA 
space definitely will.

> and probably a few other things but the above are those I
> consider most important.

If you start with the solution, one can always find problems that it solves. 
However, if you start with a defined problem, the solution may not be what 
you expect.  Every example you've given so far is solved at least as well by 
PI space as by ULA space, and in some cases better by PI.

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 Jul 09 11:19: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 1I7v0V-00089B-Rn; Mon, 09 Jul 2007 11:18:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7v0R-00088j-PL
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:18:31 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7v0R-0001w9-EB
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:18:31 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l69FLoiE008957;
	Mon, 9 Jul 2007 10:21:53 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 10:17:52 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 10:17:51 -0500
Message-ID: <4692519F.2030902@ericsson.com>
Date: Mon, 09 Jul 2007 11:17:51 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <468E730F.8090409@hp.com><8E296595B6471A4689555D5D725EBB21046B02CB@xmb-rtp-20a.amer.cisco.com><m2vecx8kvg.wl%jinmei@isl.rdc.toshiba.co.jp>	<m1r6nhkdsv.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8B2@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A8B2@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Jul 2007 15:17:51.0724 (UTC)
	FILETIME=[5110F2C0:01C7C23C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Implementation Guidelines perhaps? (Was Re: release candidate of
 2462bis (Re: Revisit: one remaining cornercase in DAD))
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Hemant,
   AFAICS, there are four ways to go about this.

- Errata to RFC4862 (for minor/editorial changes)
- 4862bis (probably a bit premature)
- New standards track document that will end up updating RFC4862
- New informational document (probably guidelines to implementers)

 From what I have seen, you are probably best off with option 4. I do 
not see any of the issues mentioned in the draft as a protocol problem. 
  If implementations are getting this wrong, the problem is best solved 
by writing implementation guidelines, not by protocol modifications.

Cheers
Suresh

Hemant Singh (shemant) wrote:
> Tatuya,
> 
> We take it, after your recent changes to 2462bis -08 version, some day
> soon this I-D will become a new RFC (say RFC xxxx). So when can we
> expect to add updates to the new RFC?
> Will you start a another xxxxbis right after this one is published?
> When will the IPv6 working group be closed?  Will there be any provision
> for incorporating late-breaking changes?
> 
> - Wes
> 
> -----Original Message-----
> From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp] 
> Sent: Monday, July 09, 2007 7:38 AM
> To: ipv6@ietf.org
> Subject: release candidate of 2462bis (Re: Revisit: one remaining
> cornercase in DAD)
> 
> At Sat, 07 Jul 2007 03:09:23 +0900,
> JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp> wrote:
> 
>> I tend to agree (I also thought this as an option myself).  Thanks for
> 
>> the suggestion.
> 
> I've updated the AUTH48 version of rfc2462bis with this fix.  Other
> (major) changes since the latest version of I-D (rfc2462bis-08) are:
> 
> - Updates to RFC references:
>   + RFC3041 -> RFC4941 (which will be published at the same timing)
>   + RFC3513 -> RFC4291
> 
> - Wording clarification about interface identifiers
>   (see discussion in the thread that began with this post:
>   http://www1.ietf.org/mail-archive/web/ipv6/current/msg05163.html)
> 
> Note that I didn't include any change about the strictness of DAD.  I
> didn't see any consensus on including that at this very final stage.
> 
> I'm about to submit this version to the RFC editor, but a copy of the
> release candidate is available here: 
> 
> http://www.jinmei.org/rfc4862-candidate.txt
> 
> just in case.
> 
> 					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
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Jul 09 11: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 1I7v4R-00063H-R9; Mon, 09 Jul 2007 11:22:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7v4O-00062h-Kk
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:22:36 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7v4K-0002es-3z
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:22:36 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2007 11:22:31 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAO/vkUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,517,1175486400"; 
	d="scan'208"; a="64693558:sNHT58260118"
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 l69FMVFC010596; 
	Mon, 9 Jul 2007 11:22:31 -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 l69FMF76017006; 
	Mon, 9 Jul 2007 15:22:31 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); 
	Mon, 9 Jul 2007 11:22: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: Mon, 9 Jul 2007 11:22:16 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <46924A07.4030504@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: AcfCN9VO7sMxzzcWRgqYpW4U8u/6JwAAdlAA
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 09 Jul 2007 15:22:17.0449 (UTC)
	FILETIME=[EF735D90:01C7C23C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8540; t=1183994551;
	x=1184858551; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=9UAmIs6MiLSVdOTFEotbtbwkBwfFybocSpe/J0z1bHw=;
	b=vSymt2JQUKy0UCIH9mLXgoU1ZFe2d1Bb/verSZl1Xo0mNVODLMbYHrAMGeLEZPoVjB/C/Ya/
	uYqCMm2uPsRJwQNiWZxKbzLcG4KIDciAgxj5mWAdwz0dri7x28ExyS5R;
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: b8f3559805f7873076212d6f63ee803e
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Vlad & Tatuya,

Please see in line below with "<hs>".

Tatuya, please note another proposed change by Vlad to 2462bis and also
Vlad agrees that a change regarding skipping DAD should be made to
2462bis as per this statement from Vlad: "I would agree to adding the
rationale for why skipping DAD is not recommended."

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Monday, July 09, 2007 10:45 AM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hi Hemnat

Hemant Singh (shemant) wrote:
> <hs> We also told the modem vendor their behavior is compliant with ND

> RFC but since bandwidth is limited in a broadband deployment in the=20
> upsteam direction (modem to the aggregation router), having each modem

> issue 9 DAD's before the modem got online was a waste of valuable=20
> bandwidth resource. As 2462bis says, it's up to a link-type document=20
> to modify this value. Aggregation router standards will have to take=20
> care of specifying such a value for broadband deployments IF they=20
> choose to use a different value than the default value of 1.
>=20
> So the new text you are introducing would be completely nullified.
>=20
> <hs> True. Our aim with this bullet is to only raise an awareness that

> default value is 1. Many new IPv6 host developers just read 2461bis=20
> and miss the default value of this variable that is not specified in=20
> 2461bis, but is specified in 2462bis.

IMO this is already fairly well spelled out in 2461bis.  There was talk
earlier on the list of adding something along the list of:
    This document RECOMMENDS that implementations use default values
specified
    here.

<hs> Since we are working on how to fold in text from our I-D as changes
to 2461bis, this bullet 5 from section 2 of our I-D will also fall into
that work of where to specify this recommendation in 2461bis.

I don't remember what happened to that, but that should do what you
want.
>=20
> <hs> Yes, we are putting together such a section.
>=20

OK. I'll wait for the new text.

>=20
> Yes, and 2462bis weasel words around this issue at the top of page 19.
> Maybe a "should" there needs to be changed to a "SHOULD"?
>=20
> <hs> Which words are you talking about? Quick look at 2462bis and even

> 2461bis on page 19 did not show us any relevant words.

      Note that a future revision of the address architecture [RFC3513]
      and a future link-type specific document, which will still be
      consistent with each other, could potentially allow for an
      interface identifier of length other than the value defined in the
      current documents.  Thus, an implementation should not assume a
      particular constant.  Rather, it should expect any lengths of
      interface identifiers.

I suggest the 'should' in the last sentence be replaced by SHOULD.

<hs> Ah, this is text on page 17 of 2462bis -08. Good catch. We agree
that the "should" be replaced with SHOULD. So does Tatuya want to make
such a change to 2462bis before sending it off?

>> 6.  Changes to draft-ietf-ipv6-rfc2462bis-08
>>
>> [... old text snipped ...]
>>
>>    to read as follows:
>>
>>       Each individual unicast address SHOULD be tested for
uniqueness.
>>       Note that some deployed implementations perform Duplicate
> Address
>>       Detection (DAD) only for the link-local address and skip the
> test
>>       for the global address using the same interface identifier.
>>       Whereas this document does not invalidate such implementations,
>>       this kind of 'optimization' is NOT RECOMMENDED, and new
>>       implementations MUST NOT do that optimization.  This
> optimization
>>       came from the assumption that all of an interface's addresses
> are
>>       generated from the same interface identifier (see RFC 2462
>>       [ADDRCONF]).  However, even with this assumption, skipping DAD
> for
>>       non-link-local addresses with manual configuration creates an
>>       additional problem.  This optimization allows an interface to
>>       claim a duplicate address in a way that would not be detected.
>>       For a more detailed description of this problem, see the Host
>>       Models section of
>>       draft-wbeebee-nd-implementation-pitfalls-01.  Further, new
>>       types of addresses have been introduced where the interface
>>       identifiers are not necessarily the same for all unicast
> addresses
>>       on a single interface [RFC3041] [RFC3972].  Requiring an
> interface
>>       to perform DAD for all unicast addresses will make the
algorithm
>>       more robust.
>>
>> <vy>
>> Two issues:
>>  1. This text is not any stronger then the existing text in 2461bis
> and
>>     doesn't add anything significant.
>>
>> <hs> Yes it is. We have been told by a number of people that whether=20
>> to skip DAD or not was discussed at length in the IETF IPv6 WG and
> mailer.
>> If so much discussion happened and RFC 2462 changed in 2462bis I-D to

>> remove the skipping DAD requirement for newer hosts, we'd like to see

>> the reasons for the change. The only reason we found in 2462bis for=20
>> the change was:
>>
>>       "new types of addresses have been introduced where the
>>       interface identifiers are not necessarily the same for all
> unicast
>>       addresses on a single interface [RFC3041] [RFC3972]."
>>
>> Well, we provided an example scenario in our I-D (section 2, bullet=20
>> 4)
>=20
>> that highlights that fact the skipping DAD combined with manual=20
>> configuration can result in duplicate addresses on the same link=20
>> which
>=20
>> are not detected.
>=20
> The example you provide has been documented in the Neighbor Discover=20
> Threats spec (rfc 3756).  So that's documented fairly well.  The=20
> Security Consideration section also references it and points out=20
> issues with DAD.
>=20
> <hs> No, we disagree that the problem we have highlighted in bullet 4=20
> of our I-D is mentioned anywhere in RFC 3756 - you will have to point=20
> it out to us.  Our problem is saying mixing "skipping DAD" and manual=20
> configuration is a bad idea and also shows that even if Link-local=20
> address and Global Unique Address (GUA) of the host are created from=20
> the same identifier (Host2 in our example), one will have duplicate=20
> addresses on the link that would not be detectable. Further, this=20
> problem is detectable if DAD is not skipped for the GUA by Host2. The=20
> duplicate will be detected because even Host1 is a compliant host in=20
> our model, not a rogue host. Please see an earlier email discussion=20
> between ourselves and Tataya on this one.

You are right.  I just re-read 3756 and this item is not there.  I would
agree to adding the rationale for why skipping DAD is not recommended.
Any additional text can be safely removed.

<hs> OK, so we have reached consensus between us for changing the text
of 2462bis. We like our original paragraph because it clearly mentions
manual configuration, which is not mentioned in your suggested
paragraph.

Thanks.

- Hemant & Wes

Something like:
   -  Each individual unicast address SHOULD be tested for uniqueness.
      Note that there are implementations deployed that only perform
      Duplicate Address Detection for the link-local address and skip
      the test for the global address using the same interface
      identifier as that of the link-local address.  Whereas this
      document does not invalidate such implementations, this kind of
      "optimization" is NOT RECOMMENDED, and new implementations MUST
      NOT do that optimization.  This optimization came from the
      assumption that all of an interface's addresses are generated from
      the same identifier.  However, the assumption does not actually
      stand; new types of addresses have been introduced where the
      interface identifiers are not necessarily the same for all unicast
      addresses on a single interface [RFC3041] [RFC3972].
Additionally,
      hosts that implement the "optimization" may end up configuring
      duplicate addresses and causing network disruptions.  Requiring to
      perform Duplicate Address Detection for all unicast addresses will
      make the algorithm robust for the current and future such special
      interface identifiers.

-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 Jul 09 11:55: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 1I7vZf-0006oj-M2; Mon, 09 Jul 2007 11:54:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vZe-0006oR-Nv
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:54:54 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7vZc-0002qp-Us
	for ipv6@ietf.org; Mon, 09 Jul 2007 11:54:54 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 9 Jul 2007 16:54:27 +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, 9 Jul 2007 16:56:00 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0A462D4@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfCOrdBfUtUa9/wRmWZ3Q3ykboixwABkJ8g
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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com><469218B7.8060108@cisco.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B0A46060@E03MVC4-UKBR.domain1.systemhost.net>
	<012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 09 Jul 2007 15:54:27.0952 (UTC)
	FILETIME=[6E1EBF00:01C7C241]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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

> > Essentially, the IETF is placing control over the route=20
> announcement=20
> > question in the hands of those who are actually impacted by the=20
> > question. If there is any dispute over the specifics of how this is=20
> > handled, the RIRs are the forum in which it should be worked out.
>=20
> RIRs have no power to do that today.  Routability of prefixes=20
> is solely in the hands of ISPs that accept (or not) those=20
> routes. =20

And ISPs happen to be members of the RIRs and therefore they have a
voice in the policies of the RIRs. Therefore, RIRs do have the power to
prevent ULA-C route announcements and the RIRs are the forum for
interested parties, such as ISPs and address holders, to work out the
issue. Not the IETF.

> And we do _not_ want a world where some group of=20
> ivory tower academics and vendors tell operators what they=20
> _must_ do on their own networks.=20

Precisely why the IETF delegates this type of thing through IANA to the
RIRs.

> The Internet is successful=20
> due to cooperation inspired by enlightened self-interest, not=20
> central control.

Which is why there are 5 separate regional RIRs which are ultimately
controlled by the self-interested parties cooperating with each other in
each region. If the IETF states its intent for ULA-C addresses, that
does not mean there is any kind of central control.

--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 Mon Jul 09 12:07: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 1I7vlm-0000qh-Hm; Mon, 09 Jul 2007 12:07:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vlk-0000pL-LJ
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07:24 -0400
Received: from mail.polartel.com ([66.231.96.142])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7vlk-0003Bs-BV
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07: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, 9 Jul 2007 11:06:50 -0500
Message-ID: <70DE64CEFD6E9A4EB7FAF3A063141066707127@mail>
In-Reply-To: <012601c7c23a$a7cfbe90$4f3816ac@atlanta.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfCOuhTxeGZe35YQq+t+oSCfFGybwAB3xiA
From: "Kevin Kargel" <kkargel@polartel.com>
To: <ipv6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
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

All it would mean is that the aviation industry that wanted its
"private" network would have to host a "root" DNS server for that
network and advise it's members to include it in their hints.  I don't
see that being a big issue. In fact it makes sense from a security
perspective. =20

And again, with trivial ACL's the "private" network could be managed out
of PI/PA.



> -----Original Message-----
> From: Stephen Sprunk [mailto:stephen@sprunk.org]=20
> Sent: Monday, July 09, 2007 9:53 AM
> To: Eliot Lear
> Cc: Thomas Narten; Mark Andrews; ipv6@ietf.org; Pekka Savola
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
>=20
> Thus spake "Eliot Lear" <lear@cisco.com>
> > Stephen Sprunk wrote:
> >> The supposed use case for ULA-C is large orgs who interconnect=20
> >> privately with other large orgs.  If you _don't_ allow=20
> ULA-Cs in the=20
> >> global reverse DNS, then every org in the internetwork must hack=20
> >> their local DNS servers to recognize every other org's reverse DNS=20
> >> entries.  That is painful and unnecessary.
> >
> > To borrow your logic, if this space is truly private why=20
> should this=20
> > be an issue?
>=20
> That hinges on the meaning of "private".  Imagine a private=20
> internet for the aviation industry; there would be thousands=20
> of players, each supposedly with their own ULA-C/G block. =20
> Every player would need to hack their DNS servers to account=20
> for every other player's RDNS settings, and any time someone=20
> new joined or someone existing wanted to update their=20
> settings, thousands of other operators would need to change=20
> their hacks to keep things working.=20
> The odds of that being successful in practice are so low=20
> they're not worth considering.
>=20
> >> There are operational concerns with putting ULA(-C) addresses in =20
> >> forward DNS; nobody argues with that. However, putting ULA-C=20
> >> addresses in reverse DNS harms nobody who can't reach=20
> those addresses=20
> >> yet greatly benefits those that can.
> >
> > The delegation must be maintained and occasionally updated.=20
> Who does that?
>=20
> Whoever is designated as the central authority.  It is=20
> necessary for there to be a database to keep blocks unique,=20
> and that database will need billing and contact information,=20
> so the addition of a couple of NS entries for each block is=20
> trivial.  All we're discussing now is whether that=20
> information is exposed via the global DNS.
>=20
> > At this point it is plain to see that ULA-C is nothing but=20
> PI address=20
> > space, because the IETF is in no position to enforce otherwise.  So=20
> > please, let's just call it what it is.
>=20
> Exactly.
>=20
> S
>=20
> Stephen Sprunk      "Those people who think they know everything
> CCIE #3723         are a great annoyance to those of us who do."
> K5SSS                                             --Isaac Asimov=20
>=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 Mon Jul 09 12:07: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 1I7vm7-0001Cu-NA; Mon, 09 Jul 2007 12:07:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vm6-0001Bi-3e
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07:46 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7vm2-0003uZ-M2
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07:46 -0400
Received: from smtp1.fc.hp.com (smtp.cnd.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id B4A7835FDC;
	Mon,  9 Jul 2007 12:07:21 -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 DC758147B16;
	Mon,  9 Jul 2007 16:01:35 +0000 (UTC)
Message-ID: <46925BDF.8070409@hp.com>
Date: Mon, 09 Jul 2007 12:01:35 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.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: bdc523f9a54890b8a30dd6fd53d5d024
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Hemant Singh (shemant) wrote:

> 
> IMO this is already fairly well spelled out in 2461bis.  There was talk
> earlier on the list of adding something along the list of:
>     This document RECOMMENDS that implementations use default values
> specified
>     here.
> 
> <hs> Since we are working on how to fold in text from our I-D as changes
> to 2461bis, this bullet 5 from section 2 of our I-D will also fall into
> that work of where to specify this recommendation in 2461bis.

That single sentence will do instead and take care of all the other defaults
as well.  I'll to see what happened to that thread, but something like that
would be useful for both 2461bis and 2462bis.
> 
>> 2461bis on page 19 did not show us any relevant words.
> 
>       Note that a future revision of the address architecture [RFC3513]
>       and a future link-type specific document, which will still be
>       consistent with each other, could potentially allow for an
>       interface identifier of length other than the value defined in the
>       current documents.  Thus, an implementation should not assume a
>       particular constant.  Rather, it should expect any lengths of
>       interface identifiers.
> 
> I suggest the 'should' in the last sentence be replaced by SHOULD.
> 
> <hs> Ah, this is text on page 17 of 2462bis -08. Good catch. We agree
> that the "should" be replaced with SHOULD. So does Tatuya want to make
> such a change to 2462bis before sending it off?

Well, looking at 08 draft, it shows up in Section 5.5.3 at the top of
page 19, but I don't really care were the text is as long as it right...

> 
> <hs> OK, so we have reached consensus between us for changing the text
> of 2462bis. We like our original paragraph because it clearly mentions
> manual configuration, which is not mentioned in your suggested
> paragraph.

Well, we reached agreement, not quire consensus....  In this particular
case, manual configuration is just an example.  There may be other means
of forming the same address.  Regardless of how the address was assigned,
the issue is that skipping DAD is bad.  You wanted to document a rationale,
and for why, and that is what we should do.  The final recommendation
stays the same.

-vlad

> 
> Thanks.
> 
> - Hemant & Wes
> 
> Something like:
>    -  Each individual unicast address SHOULD be tested for uniqueness.
>       Note that there are implementations deployed that only perform
>       Duplicate Address Detection for the link-local address and skip
>       the test for the global address using the same interface
>       identifier as that of the link-local address.  Whereas this
>       document does not invalidate such implementations, this kind of
>       "optimization" is NOT RECOMMENDED, and new implementations MUST
>       NOT do that optimization.  This optimization came from the
>       assumption that all of an interface's addresses are generated from
>       the same identifier.  However, the assumption does not actually
>       stand; new types of addresses have been introduced where the
>       interface identifiers are not necessarily the same for all unicast
>       addresses on a single interface [RFC3041] [RFC3972].
> Additionally,
>       hosts that implement the "optimization" may end up configuring
>       duplicate addresses and causing network disruptions.  Requiring to
>       perform Duplicate Address Detection for all unicast addresses will
>       make the algorithm robust for the current and future such special
>       interface identifiers.
> 
> -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 Jul 09 12:07: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 1I7vmF-0001Se-Q8; Mon, 09 Jul 2007 12:07:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7vmD-0001RL-IX
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07:53 -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 1I7vm9-0003uj-06
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:07:53 -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 l69G7k4M026499;
	Mon, 9 Jul 2007 09:07:47 -0700
Message-ID: <018801c7c243$3e6bfb90$4f3816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.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>
	<4684DB4A.2060703@gmail.com><27414.1183131210@sa.vix.com><4688C2CA.5050302@gmail.com>
	<43704.1183395211@sa.vix.com><3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org><58873.1183400932@sa.vix.com><63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
	<026a01c7c108$bd3673b0$6701a8c0@atlanta.polycom.com>
	<Pine.LNX.4.64.0707081009000.9923@chandra.student.uit.no>
Date: Mon, 9 Jul 2007 10:39:23 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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: 00e94c813bef7832af255170dca19e36
Cc: ipv6@ietf.org, roger@jorgensen.no
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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Sat, 7 Jul 2007, Stephen Sprunk wrote:
>> Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
>>> (we are looking at something between 500 and upto 10 000 or
>>> more unique ULA-C/G blocks for or network and use)
>>
>> That's going to get expensive, no matter how little the central
>> authority charges.  Well, unless the central authority does bulk
>> discounts, but I see no reason they would since there's no
>> economy of scale in issuing thousands of prefixes that can't
>> be aggregated, unlike aggregatable PI/PA space.
>
> Did you notice I didnt mention the price, cheap or not one time
> in my mail? We know it will cost so we dont consider that yet.
> Make ULA-C/G more expensive than PI and we likely will use
> PI, make PI more expensive and it is not an options. You see
> the price dont mather! It is the technical options and
> possibilities that are important.

I've seen three reasons for ULA-C/G proposed:

1.  People can't get PI space
    - This shouldn't apply to you.
2.  ULA-C/G will be cheaper than PI space.
    - This remains to be seen.
3.  ULA-C/G won't be publicly routed.
    - There's no requirement you route PI space.

> and we do NOT care about aggregation much either since it
> is our own internal network we are talking about.

You don't do any route summarization within your internal network?  Must be 
nice not to have to worry about that.

>> I do not see a requirement to pass ULA-C/G merely because
>> some RIRs have failed to meet their respective communities'
>> needs.  If you're unhappy with what RIPE offers, either show
>> up and propose policy changes or (less-preferred) route
>> around the failure and get space from ARIN.
>
> you totaly missread what I wrote. A PI policy will most likely be
> in place in RIPE region to at some point soon, thats why I said
> we could choice from PI or ULA-C/G.

So, then, the question is what does ULA-C/G buy you that PI does not?

> Did you also notice that I said we have already got our own PA
> assignment, a /32, for all our external needs?

Okay, so you already have more addresses than you could possibly need.  When 
you said PA, I assumed you had a typical /48 block(s) from your upstream(s) 
and that wasn't enough space and/or you wanted provider independence that 
you didn't have today.

> Almost all ULA-C/G usecases can be solved by using either PA
> or PI type of  addresses from the RIRs but why not give the
> enterprises an options to use something similar to RFC1918
> addresses?

We already have something similar to RFC 1918: RFC 4193.

ULA-C/G is _not_ similar to RFC 1918; it is PI by another name.

> Thats what we are talking about, another set of addresses for
> inter-network use, NOT DFZ/global Internet usage.

Addresses are addresses; you can use PI space for private use just as easily 
as, if not more easily than, you can use any other type of space.

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 Jul 09 12:56: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 1I7wXD-0003a5-R6; Mon, 09 Jul 2007 12:56:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wXC-0003WL-21
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:56:26 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7wXB-0004Ee-4u
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:56:25 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1184003557; x=1184608357; 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=nsI4JCk8ad6IBQ
	r8uYEiS+RhJ0igBNPjUP+ZLG9UAQkrRs7O5jqZc1MvXaW6XBerJSAA9kQ3DZFKTq
	cTCYAmeTm326yHkB+HFpKyZmfzbnxzm7GMFhXkxKUGFBHZmLk1yq/1T1tC8Q8Fva
	JOIQWGdaxr3WmHegg70rF0FA9HWnk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=PoJqEvoRsF1zR/CGJe/zpeZ9+EmvmgPdb0z4Q4WmSDeR6nl6JfRqHzFjD3C2gzHYqS6cwvY7nTMtuhcOuTdl9jkw45xE7d41myPslns8QPp5Hem7ZDT5LbN7SrDNg4E5m1015UKWmNjHRLJ42m49DAcFmpeBRJQq64NWzqMJVrk=;
Received: from [192.168.1.242] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002573968.msg
	for <ipv6@ietf.org>; Mon, 09 Jul 2007 18:52:34 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 09 Jul 2007 18:55:30 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C2B83522.1A2240%jordi.palet@consulintel.es>
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfCSfTeM4Z+CC49EdyAIQAX8sYbNQ==
In-Reply-To: <4691EC41.3050400@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:070709:ipv6@ietf.org::8pUy27YPlh8Fno2P:00002/Zs
X-MDRemoteIP: 86.45.142.3
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, Mon, 09 Jul 2007 18:52:37 +0200
X-MDAV-Processed: consulintel.es, Mon, 09 Jul 2007 18:52:37 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
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
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

This is not correct. PI is not available from 2 RIRs, and there is not a
clear view of when it will become available. In one of them, because the
timing of the Policy Development Process, it will take at least 15 months to
get it implemented and this in the case it is approved in the next meeting
in almost one year from now.

In the other one, even PA is not available unless you have 200 customers
(this is the same in other RIRs that already have PI).

I'm not saying that this is related to ULA-C, I still believe it should be
kept separated, and ULA-C is NOT to be used as a replacement of PA/PI, and
indeed, I'm convinced it will not happen because if you try that you can
never be sure that your ULA-C is globally routed and consequently is 100%
reachable. Anyway, I though it is important to clarify what I have explained
above.

Regards,
Jordi




> De: Brian E Carpenter <brian.e.carpenter@gmail.com>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Mon, 09 Jul 2007 10:05:21 +0200
> Para: <briand@ca.afilias.info>
> CC: Stephen Sprunk <stephen@sprunk.org>, <ipv6@ietf.org>
> Asunto: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
> 
> On 2007-07-09 06:52, briand@ca.afilias.info wrote:
>> I think we should avoid any "straw man" arguments, as those tend not to
>> actually help advance the subject matter.
>> 
>> Just because one way of accomplishing a particular networking objective,
>> involves particularly unpleasant choices, does not mean that the technology
>> involved is at fault. It is also possible that the design choice was a case
>> of not using the right tool for the right job.
>> 
>>> Thus spake "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>>>> On 2007-07-06 02:59, Stephen Sprunk wrote:
>>>>> Why would you ever change PI space?  The issue is changing PA
>>>>> space, and that's something that may need to be done every few
>>>>> weeks as upstream links go up and down.
>>>> Absolutely not. If you have 3 ISPs you run 3 PA prefixes all the time.
>>>> If you drop or add an ISP you drop or add a prefix in a planned manner.
>>>> RFC 4192.
>> 
>> I beg to differ.
>> 
>> PI space is available, from most if not all RIRs.
>> The criteria for obtaining such is reasonable, and having multiple
>> ISPs, i.e. being multihomed, generally accomplishes this.
> 
> That's unfortunately true, but since it doesn't scale to the ten
> million or so networks we expect to desire multihoming, it will
> only work for a few years. That's why we need other solutions.
> 
>      Brian
> 
>> 
>> ISPs are expected to have PA space available to assign to their customers.
>> This does not mean that every customer can only ever use PA space from
>> their ISP. It only means that customers who do not have their own PI space,
>> will be able to get PA space from their ISP.
>> 
>> If you are multihomed, the community generally expects you to use PI space.
>> And that community includes your ISPs.
>> 
>> If we did not need to have PI space being announced from anyone other than
>> the core of the DFZ (those entities which are generally considered "tier 1"
>> for lack of a better description), then we would only have AS paths of
>> length 1, and we would be able to run EGP (the predecessor of BGP).
>> 
>> And clearly the collection of RFCs describing IPv6 numbering schemes are
>> robust enough, and the routing protocols inclusive enough, that PI space
>> can be announced via ISPs, in addition to their own PA aggregates.
>> 
>>> When my link to one of those three ISPs goes down, I have a 1/3 chance of
>>> each outbound connection failing because the return path is broken (or my
>>> other two upstreams do uRPF).  I also have a 1/3 chance of each inbound
>>> connection failing until I update DNS to remove the relevant AAAA records;
>>> smarter clients will try multiple addresses for inbound connections, but
>>> there'll be a delay and not all clients are that smart.
>>> 
>>> The alternative is to renumber the entire network every time a link goes
>>> up
>>> or down.
>> 
>> You should, in this case, have a PI block, not be using anyone's PA block,
>> let along 3 x PA blocks. If you are using PI, you are running BGP, and
>> single link failures are the kind of thing that are relatively minor events
>> for any multi-connected entity, such as your network. No renumbering is
>> needed.
>> 
>>>>> Compare to the cost of a NAT box and the choice is easy.
>>>> That's true if you don't put the indirect operational and user
>>>> costs of NAT, plus the opportunity cost of innovation blocked
>>>> by NAT, into the equation.
>>> Most of the operational and innovation costs of NAT are also present with
>>> a
>>> stateful firewall, which any sane organization will be using, because it's
>>> really the stateful inspection that burns you.
>>> 
>>>> It *is* hard to get this into the budget unless you think strategically,
>>>> and factor in the way IPv6 is designed to handle multiple PA prefixes
>>>> simultaneously.
>>> When presented with the choice between a paradigm shift and continuing
>>> along
>>> the present path, most people will pick the latter.  In this case, that
>>> means moving either from NAT+RFC1918 to NAT+RFC4193 or from PIv4 to PIv6.
>> 
>> Our collective job is to ensure that scalable solutions are disseminated,
>> not only in the RFCs, but in the actual implementations that customers use.
>> 
>> This may mean some small amount of customer education. Everyone wins when
>> the end customers (no matter whose customers they are) make a choice which
>> is not only right for them, but good for the community as a whole.
>> 
>> If anyone is multihomed currently, and using NAT+RFC1918, then having the
>> option to go to PIv6 will likely make their life much easier. The fact
>> that they would never need to renumber, is just a bonus.
>> (They will have to renumber, in moving to IPv6 in any flavour, remember.)
>> 
>>>>>> If your choices are PI vs PA then yeah NAT does look very attractive,
>>>>>> but if you can have PA and "private"-PI (aka ULA) then things look a
>>>>>> lot
>>>>>> less blurred (IMHO).
>>>>> IMHO, you underestimate how much IT folks hate renumbering.
>>>> They hate renumbering IPv4 networks. I do too, having managed such an
>>>> operation a couple of times. It's as a result of that hatred that
>>>> IPv6 came out as it is, making RFC 4192 possible.
>>> Again, RFC 4192 ignores all of the non-technical aspects of renumbering.
>>> That's probably appropriate, given the IETF's domain, but it's only a tiny
>>> part of what must be done.  Changing the address on an interface takes a
>>> few
>>> seconds; the change control processes leading up to it can burn months of
>>> manpower.
>>> 
>>> You might convince me that if you do it frequently enough, the cost will
>>> be
>>> low, but I don't want to work anywhere that renumbers often enough to be
>>> good at it.  That reminds me of a scene in _Broken Arrow_ where a
>>> character
>>> comments he doesn't know whether to be more scared that they lost a
>>> nuclear
>>> weapon or that it happens often enough the military has a name for it.
>>> 
>>>> This is *not* to say that anyone will renumber weekly, and big networks
>>>> will avoid it (and are therefore candidates for PI). But for smaller
>>>> networks, the hatred should be substantially less, and balance the
>>>> hatred
>>>> of NAT.
>>> It's the smaller folks that can't get PI that hate NAT the least, because
>>> they tend to have less-educated staff (or rely on consultants/vendors) and
>>> may even see NAT as a good thing ("it makes me secure!"), not the evil
>>> that
>>> it really is.
>>> 
>>> 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
>>> --------------------------------------------------------------------
>>> 
>> 
>> 
>> 
> 
> --------------------------------------------------------------------
> 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 Mon Jul 09 12: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 1I7wYJ-0004jW-S2; Mon, 09 Jul 2007 12:57:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wYI-0004j9-RL
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:57:34 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7wYH-0005DA-Iu
	for ipv6@ietf.org; Mon, 09 Jul 2007 12:57:34 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id EEB02114B6
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 16:57:32 +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, 09 Jul 2007 15:07:11 +0200."
	<469232FF.8040609@cisco.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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<469232FF.8040609@cisco.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 09 Jul 2007 16:57:32 +0000
Message-ID: <90280.1184000252@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

[eliot lear]
> Having had my name on RFC 1918, I think understand some of the issues.

forgive them, eliot.  my name is on ULA-G but a lot of people (including
you, for example) still assume that i don't understand all of the issues.

> RFC 1918 not being unique meant that providers really had no choice about
> blocking it, and IANA had no method to insert reverse addresses to a
> particular site.

it's true about iana, but i still don't see that blocking 1918 is universal.
here's the packet and byte count on hkg1a.f.root-servers.net's rfc1918 rules,
38 days since the last counter reset.  i can add it all up from all 100+
f-root servers, but hong kong seems pretty representative.

00600    328489    22366217 deny ip from 10.0.0.0/8 to any in
00700     64258     4284170 deny ip from 172.16.0.0/12 to any in
00800  18840507  1240700651 deny ip from 192.168.0.0/16 to any in

as the contributor of the DNS-related paragraph near the end of RFC 1918
section 5, i can tell you that whatever the RFC says will only be a general
hint to operators and implementors, who will proceed to do whatever they
darn well want.

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



From ipv6-bounces@ietf.org Mon Jul 09 13: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 1I7wcp-0000PB-Fr; Mon, 09 Jul 2007 13:02:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wco-0000Lz-Bw
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:02:14 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7wcm-0005OT-Lw
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:02:14 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 4779B114B3
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 17:02:12 +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, 09 Jul 2007 16:38:04 +0200."
	<4692484C.70808@cisco.com> 
References: <80699.1183408066@sa.vix.com>
	<3838.10.31.30.119.1183656859.squirrel@stiedprstage1>
	<45323.1183663849@sa.vix.com>
	<1520.156.154.5.45.1183678997.squirrel@stiedprstage1>
	<89916.1183680829@sa.vix.com>
	<2617.10.31.30.119.1183742189.squirrel@stiedprstage1>
	<19501.1183769994@sa.vix.com> <4692484C.70808@cisco.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 09 Jul 2007 17:02:12 +0000
Message-ID: <90439.1184000532@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: Re: draft-ietf-ipv6-ula-global-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

> Paul, Can you please include at least a base justification for ULA-G over PI
> that is distinct from the random ULAs that can now be used? --Eliot

i'll produce an updated draft having these details, which is that ad-hoc
local networking depends on the same global framework as public networking,
for example, in-addr services, RPKI, and whois.

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



From ipv6-bounces@ietf.org Mon Jul 09 13:04: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 1I7wfQ-0003yJ-Tt; Mon, 09 Jul 2007 13:04:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wfP-0003xi-2A
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:04:55 -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 1I7wfA-0005bh-Fr
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:04:55 -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 766B9140C21A;
	Mon,  9 Jul 2007 19:04:39 +0200 (CEST)
Message-ID: <46926AAC.3010601@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 18:04:44 +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: <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>	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>	<469218B7.8060108@cisco.com>	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>	<469232FF.8040609@cisco.com>
	<90280.1184000252@sa.vix.com>
In-Reply-To: <90280.1184000252@sa.vix.com>
X-Enigmail-Version: 0.95.2
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="===============0745124188=="
Errors-To: ipv6-bounces@ietf.org

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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5036C835B1629326266B7AA6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Paul Vixie wrote:
[..]
> 00600    328489    22366217 deny ip from 10.0.0.0/8 to any in
> 00700     64258     4284170 deny ip from 172.16.0.0/12 to any in
> 00800  18840507  1240700651 deny ip from 192.168.0.0/16 to any in
>=20
> as the contributor of the DNS-related paragraph near the end of RFC 191=
8
> section 5, i can tell you that whatever the RFC says will only be a gen=
eral
> hint to operators and implementors, who will proceed to do whatever the=
y
> darn well want.

Can we then not make the very simple conclusion that ULA's will be
routed on the Internet and such are nothing else but an alternative for
"PI"? As such there is absolutely no reason at all to have this kind of
address space for this purpose.

Why should the IETF try to play with RIR policies where it's membership
chooses if "PI" space becomes available or not?

As I mentioned before, it should not be called "Local" in any form, as
it will never be "Local", unless the definition of "Local" is only
Earth, and does not include Mars and other planets, yet.

Greets,
 Jeroen


--------------enig5036C835B1629326266B7AA6
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/

iHUEARECADUFAkaSaqwuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I4pcAJ9tyDHX1wDsezctb32y93XwbW8v
kQCgwJqcy5p8vOmJoymC2lEucBP+SiM=
=L//g
-----END PGP SIGNATURE-----

--------------enig5036C835B1629326266B7AA6--


--===============0745124188==
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
--------------------------------------------------------------------

--===============0745124188==--




From ipv6-bounces@ietf.org Mon Jul 09 13:09: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 1I7wjT-00005F-AL; Mon, 09 Jul 2007 13:09:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wjR-000055-R2
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:05 -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 1I7wjR-0005qS-DM
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:05 -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 88B3C140C006;
	Mon,  9 Jul 2007 19:09:04 +0200 (CEST)
Message-ID: <46926BB2.3050607@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 18:09: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: jordi.palet@consulintel.es
References: <C2B83522.1A2240%jordi.palet@consulintel.es>
In-Reply-To: <C2B83522.1A2240%jordi.palet@consulintel.es>
X-Enigmail-Version: 0.95.2
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: f607d15ccc2bc4eaf3ade8ffa8af02a0
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="===============0677862615=="
Errors-To: ipv6-bounces@ietf.org

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

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

JORDI PALET MARTINEZ wrote:
> This is not correct. PI is not available from 2 RIRs, and there is not =
a
> clear view of when it will become available. In one of them, because th=
e
> timing of the Policy Development Process, it will take at least 15 mont=
hs to
> get it implemented and this in the case it is approved in the next meet=
ing
> in almost one year from now.

In other words you are trying to get "ULA PI" because the RIR policies
take too long? You do realize that the ULA policies will have to also go
through the same RIR communities and that they will be handled with the
same skepticism as that those "PI" proposals (which allow a single
end-user site to get a /32, which is really laughable) are being dealt wi=
th.

> In the other one, even PA is not available unless you have 200 customer=
s
> (this is the same in other RIRs that already have PI).

The IETF is not the place to discuss RIR policies. If the people who
want to force through the new policies made up policies which actually
made any sense and where fair to everybody then they would have been
accepted already.

With the current views on ULA (lets see how the next update of the draft
will be) it is nothing more than just another variant of PI with a very
weak attempt to avoid RIR policies, nothing else.

If you really want to have "PI" in those RIR regions then come up with a
good policy proposal on the RIR list, don't try to push it through. That
is not how consensus works.

Greets,
 Jeroen


--------------enigA35428E52E45D6943E0411B9
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/

iHUEARECADUFAkaSa7IuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I/kbAJ9Sl4SIpQx2+Cjfh0Wfs12ghKn/
ZQCfQrTOVE+S1ACqzTXrad3J2FVeOPQ=
=mCa/
-----END PGP SIGNATURE-----

--------------enigA35428E52E45D6943E0411B9--


--===============0677862615==
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
--------------------------------------------------------------------

--===============0677862615==--




From ipv6-bounces@ietf.org Mon Jul 09 13:09: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 1I7wjT-00005L-Ua; Mon, 09 Jul 2007 13:09:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wjS-00005A-EN
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:06 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7wjS-0005qX-5V
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:06 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id B1FF2114B3
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 17:09:02 +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, 09 Jul 2007 18:04:44 +0100."
	<46926AAC.3010601@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>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<469232FF.8040609@cisco.com> <90280.1184000252@sa.vix.com>
	<46926AAC.3010601@spaghetti.zurich.ibm.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Mon, 09 Jul 2007 17:09:02 +0000
Message-ID: <90877.1184000942@sa.vix.com>
X-Spam-Score: -2.8 (--)
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

> > as the contributor of the DNS-related paragraph near the end of RFC 1918
> > section 5, i can tell you that whatever the RFC says will only be a general
> > hint to operators and implementors, who will proceed to do whatever they
> > darn well want.
> 
> Can we then not make the very simple conclusion that ULA's will be
> routed on the Internet and such are nothing else but an alternative for
> "PI"?

no.  i showed you packet leaks, not route leaks.  (did i misunderstand the
minimum technical skillset nec'y for participation on this mailing list?)

> As I mentioned before, it should not be called "Local" in any form, as it
> will never be "Local", unless the definition of "Local" is only Earth, and
> does not include Mars and other planets, yet.

if we're down to the label engineering, then everything hard is now done?  or
are you making a funny that's intended to show absurdity somewhere?

in any case i called it "local" in ULA-G because i was stealing wholesale from
ULA-C (and i suspect they called it "local" because they were stealing from
ULA).  if you propose a term other than "private" (which is taken by RFC 1918)
that means "non-public" in the sense meant by ULA-G and ULA-C and ULA, there
might be great rejoicing.


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



From ipv6-bounces@ietf.org Mon Jul 09 13:09: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 1I7wjk-0000R7-3e; Mon, 09 Jul 2007 13:09:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wji-0000Qx-1t
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:22 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7wje-0005rM-Hr
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:09:22 -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 539C07301E;
	Tue, 10 Jul 2007 02:09:17 +0900 (JST)
Date: Tue, 10 Jul 2007 02:09:13 +0900
Message-ID: <m2644tv70m.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: <B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@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: ea4ac80f790299f943f0a53be7e1a21a
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

At Mon, 9 Jul 2007 11:22:16 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Tatuya, please note another proposed change by Vlad to 2462bis and also
> Vlad agrees that a change regarding skipping DAD should be made to
> 2462bis as per this statement from Vlad: "I would agree to adding the
> rationale for why skipping DAD is not recommended."

As (probably) indicated by Vlad, I don't think we have formed a clear
"consensus" in the "wg as a whole" that warrants a further change to
2462bis at this late stage.  At least I'm not convinced about making
the change to 2462bis at this timing, although I'd support the
stricter requirement of DAD in a separate document (maybe an
implementation guidance as Suresh suggested?) if we agree on it after
discussions in the wg.

I strongly believe 2462bis is pretty good in its current form, and
even though further discussions and resulting possible changes to the
document based on a wg consensus may make it 120% perfect, I don't
think the benefit isn't worth the publication delay.

My current plan is to submit the current version to the RFC editor
in 12 hours or so, unless I see a clear wg consensus on the change by
then.  (For that matter, I'd disagree on introducing this change to
this document at this stage)

					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 Jul 09 13:22: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 1I7wwm-0001ds-NM; Mon, 09 Jul 2007 13:22:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7wwl-0001dh-Pq
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:22:51 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7wvo-0006Ts-3e
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:22:51 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2007 13:21:51 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOQKkkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,517,1175486400"; 
	d="scan'208"; a="64707928:sNHT47399878"
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 l69HLpbu027096; 
	Mon, 9 Jul 2007 13:21:51 -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 l69HLes4027401; 
	Mon, 9 Jul 2007 17:21:51 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, 9 Jul 2007 13:21:26 -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, 9 Jul 2007 13:21:24 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED376@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2644tv70m.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: AcfCS/HQtsNOAcoHTAuzqV3FVnZ+kwAAQpbQ
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
	<m2644tv70m.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: 09 Jul 2007 17:21:26.0538 (UTC)
	FILETIME=[94A3C6A0:01C7C24D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2586; t=1184001711;
	x=1184865711; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=OMA/noa/WkKpGd1K0JnKd3gnqMZG4EjnF7gap7GvDhk=;
	b=Jwx/5O5rxn4mYLzqeo97b6n1bvtMSoiiKBpF7yOxb8J7Bt8O4IrH8avcjz4CL7B6Uz/sQlb5
	pUHo7QJuQDMo7jVAkbZpKqbYhC9CUKFwcXWnHPg/9phhMfIFdJQSZG+9;
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: 0a7aa2e6e558383d84476dc338324fab
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, 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

Tatuya,

If it's too late, it's fine.  On a different note, did you catch the
fact from Vlad who wanted  "should" changed to "SHOULD" in a paragraph
on page 18 of 2462bis? Further, we are also adding that a "should not"
in the same paragraph be changed to "SHOULD NOT". Do you or anyone else
think such a change can be made before the 12 hours expire? This is the
relevant paragraph:

      Note that a future revision of the address architecture [RFC3513]
      and a future link-type specific document, which will still be
      consistent with each other, could potentially allow for an
      interface identifier of length other than the value defined in the
      current documents.  Thus, an implementation should not assume a
      particular constant.  Rather, it should expect any lengths of
      interface identifiers.

Thanks.

- Hemant & Wes

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Monday, July 09, 2007 1:09 PM
To: Hemant Singh (shemant)
Cc: Vlad Yasevich; ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

At Mon, 9 Jul 2007 11:22:16 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Tatuya, please note another proposed change by Vlad to 2462bis and=20
> also Vlad agrees that a change regarding skipping DAD should be made=20
> to 2462bis as per this statement from Vlad: "I would agree to adding=20
> the rationale for why skipping DAD is not recommended."

As (probably) indicated by Vlad, I don't think we have formed a clear
"consensus" in the "wg as a whole" that warrants a further change to
2462bis at this late stage.  At least I'm not convinced about making the
change to 2462bis at this timing, although I'd support the stricter
requirement of DAD in a separate document (maybe an implementation
guidance as Suresh suggested?) if we agree on it after discussions in
the wg.

I strongly believe 2462bis is pretty good in its current form, and even
though further discussions and resulting possible changes to the
document based on a wg consensus may make it 120% perfect, I don't think
the benefit isn't worth the publication delay.

My current plan is to submit the current version to the RFC editor in 12
hours or so, unless I see a clear wg consensus on the change by then.
(For that matter, I'd disagree on introducing this change to this
document at this stage)

					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 Jul 09 13:26: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 1I7x01-0004Qe-Qs; Mon, 09 Jul 2007 13:26:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7x00-0004Ok-92
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:26:12 -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 1I7wzg-0006hB-JG
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:26: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 7351F140C219;
	Mon,  9 Jul 2007 19:25:51 +0200 (CEST)
Message-ID: <46926FA4.8090603@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 18:25:56 +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: <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>	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>	<469218B7.8060108@cisco.com>	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>	<469232FF.8040609@cisco.com>
	<90280.1184000252@sa.vix.com>	<46926AAC.3010601@spaghetti.zurich.ibm.com>
	<90877.1184000942@sa.vix.com>
In-Reply-To: <90877.1184000942@sa.vix.com>
X-Enigmail-Version: 0.95.2
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: 3971661e40967acfc35f708dd5f33760
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="===============1000794207=="
Errors-To: ipv6-bounces@ietf.org

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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig465CBCA211D502FDB8F3AD28
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Paul Vixie wrote:
>>> as the contributor of the DNS-related paragraph near the end of RFC 1=
918
>>> section 5, i can tell you that whatever the RFC says will only be a g=
eneral
>>> hint to operators and implementors, who will proceed to do whatever t=
hey
>>> darn well want.
>> Can we then not make the very simple conclusion that ULA's will be
>> routed on the Internet and such are nothing else but an alternative fo=
r
>> "PI"?
>=20
> no.  i showed you packet leaks, not route leaks.  (did i misunderstand =
the
> minimum technical skillset nec'y for participation on this mailing list=
?)

Sorry, but not everybody is fluent in the language of the networking
gods. I am pretty sure that you understood that I mean with it that
these packets are being routed, that is forwarded, over several routers.
Clearly the networks that are between your example site and the sender
don't employ any filtering at all, clearly all of your upstreams don't
do this either, though that might be simply because you will claim that
that is for 'research purposes' (which is a noble cause as otherwise we
would not be able to tell that these packets even exist).

As you mention indeed the RFC1918 routes are mostly being filtered, at
least most of the time. Check for instance RIPE's RIS which clearly
shows that RFC1918 leaks do occur. Indeed that doesn't make it globally
routed, but that they exist and happen says enough.

To illustrate my point, before being told again that I have to have a
'minimal skilset' and that they are not leaked, see the following:

http://www.ris.ripe.net/perl-risapp/prefixinuse.do?rrc_id=3D1000&Submit=3D=
Submit&.submit=3Dtype&sortby=3Dtime&outype=3Dhtml&preftype=3Dmspec&interv=
al=3D1&prefix=3D10.0.0.0/8
8<---------------------------------------------------------------------
The last announcement occurred on 2007-07-05 08:31:00Z. 44 entries are
found for 10.0.0.0/8.

Prefix    	Last announced  =E2=86=93 	Origin AS
10.20.90.0/24 	2007-06-12 09:12:16Z	23352
10.250.250.0/24 2007-06-12 09:12:16Z	23352
10.43.0.0/16 	2007-06-22 05:21:58Z	8402
10.120.0.0/16 	2007-06-22 05:21:58Z	8402
10.215.0.0/16 	2007-06-22 05:21:58Z	8402
10.35.0.0/16 	2007-06-22 05:21:58Z	8402
10.90.0.0/16 	2007-06-22 05:21:58Z	8402
10.121.0.0/16 	2007-06-22 05:21:58Z	8402
10.11.0.0/16 	2007-06-22 05:21:58Z	8402
10.138.0.0/16 	2007-06-22 05:21:58Z	8402
10.64.12.0/24 	2007-06-22 05:21:58Z	8402
10.75.0.0/16 	2007-06-22 05:21:58Z	8402
10.129.0.0/16 	2007-06-22 05:21:58Z	8402
10.3.2.0/24 	2007-06-22 05:21:58Z	8402
10.139.0.0/16 	2007-06-22 05:21:58Z	8402
10.38.0.0/16 	2007-06-22 05:21:58Z	8402
10.123.0.0/16 	2007-06-22 05:21:58Z	8402
10.74.0.0/16 	2007-06-22 05:21:58Z	8402
10.41.0.0/16 	2007-06-22 05:21:58Z	8402
10.76.0.0/16 	2007-06-22 05:21:58Z	8402
10.69.43.0/24 	2007-06-27 22:09:56Z	5410
10.69.42.0/24 	2007-06-27 22:09:56Z	5410
10.2.3.40/29 	2007-06-28 07:05:27Z	8402
10.0.0.16/30 	2007-06-28 10:00:39Z	2819
10.0.0.0/30 	2007-06-28 10:00:39Z	2819
10.0.0.20/30 	2007-06-28 10:00:39Z	2819
10.0.0.4/30 	2007-06-28 10:00:39Z	2819
10.0.0.12/30 	2007-06-28 10:00:39Z	2819
10.0.0.8/30 	2007-06-28 10:00:39Z	2819
10.10.0.0/20 	2007-06-29 04:05:58Z	8402
10.221.0.0/16 	2007-06-29 04:05:58Z	8402
10.227.0.0/16 	2007-06-29 11:50:19Z	8402
10.222.60.0/24 	2007-06-29 11:50:19Z	8402
10.222.81.0/24 	2007-06-29 11:50:19Z	8402
10.181.0.0/16 	2007-06-29 11:50:19Z	8402
10.130.0.0/16 	2007-06-29 11:50:19Z	8402
10.13.0.0/16 	2007-06-29 11:50:19Z	8402
10.69.191.0/24 	2007-07-03 15:01:27Z	5410
10.69.192.0/24 	2007-07-03 15:01:27Z	5410
10.193.14.64/27 2007-07-05 08:31:00Z	34245
10.11.12.0/24 	2007-07-05 08:31:00Z	34245
10.193.14.32/27 2007-07-05 08:31:00Z	34245
10.193.3.0/24 	2007-07-05 08:31:00Z	34245
10.11.13.0/24 	2007-07-05 08:31:00Z	34245
--------------------------------------------------------------------->8

Now please state again that people should have a 'minimal skillset'.
Thank you for your attention.

>> As I mentioned before, it should not be called "Local" in any form, as=
 it
>> will never be "Local", unless the definition of "Local" is only Earth,=
 and
>> does not include Mars and other planets, yet.
>=20
> if we're down to the label engineering, then everything hard is now don=
e?  or
> are you making a funny that's intended to show absurdity somewhere?

Unique Local Addresses-Global <--- Local Global? Very good naming.

And it won't be local anyway as it is primarily intended to most likely
interconnect to other sites, and at that from the few examples given to
a very large amount of sites, similar to "PI" space.

> in any case i called it "local" in ULA-G because i was stealing wholesa=
le from
> ULA-C (and i suspect they called it "local" because they were stealing =
from
> ULA).  if you propose a term other than "private" (which is taken by RF=
C 1918)
> that means "non-public" in the sense meant by ULA-G and ULA-C and ULA, =
there
> might be great rejoicing.

As I mentioned before, but clearly you missed out on, it is "Non-DFZ" or
"non-globaly-routed" maybe, as that is what, from what I understand from
the minimal amount of actual descriptions of what this address space is
going to be intended for, is the actual use.

Those cases and descriptions & examples of how this type of addresses
might actually be used are very welcome to be described in the draft
btw. As that would actually illustrate why exactly these addresses are
needed. Also having them in the draft allows one to actually discuss them=
=2E

Greets,
 Jeroen


--------------enig465CBCA211D502FDB8F3AD28
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/

iHUEARECADUFAkaSb6QuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I14HAKChrLvKkhOSyGrSlfnz+FrWYAAu
IQCgqvtgz8o8hbu3SIJHbNdykoPoIJQ=
=2AGt
-----END PGP SIGNATURE-----

--------------enig465CBCA211D502FDB8F3AD28--


--===============1000794207==
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
--------------------------------------------------------------------

--===============1000794207==--




From ipv6-bounces@ietf.org Mon Jul 09 13:38: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 1I7xBi-0007Y8-FW; Mon, 09 Jul 2007 13:38:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7xBg-0007Vy-5g
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:38:16 -0400
Received: from atlrel9.hp.com ([156.153.255.214])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7xBX-0006uJ-V6
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:38:16 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel9.hp.com (Postfix) with ESMTP id 4FA5F364CE;
	Mon,  9 Jul 2007 13:36:59 -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 BAD4518F5D9;
	Mon,  9 Jul 2007 17:36:58 +0000 (UTC)
Message-ID: <46927239.8000002@hp.com>
Date: Mon, 09 Jul 2007 13:36:57 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
	<m2644tv70m.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D035ED376@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED376@xmb-rtp-20e.amer.cisco.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: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Hemant Singh (shemant) wrote:
> Tatuya,
> 
> If it's too late, it's fine.  On a different note, did you catch the
> fact from Vlad who wanted  "should" changed to "SHOULD" in a paragraph
> on page 18 of 2462bis? Further, we are also adding that a "should not"
> in the same paragraph be changed to "SHOULD NOT". Do you or anyone else
> think such a change can be made before the 12 hours expire? This is the
> relevant paragraph:
> 
>       Note that a future revision of the address architecture [RFC3513]
>       and a future link-type specific document, which will still be
>       consistent with each other, could potentially allow for an
>       interface identifier of length other than the value defined in the
>       current documents.  Thus, an implementation should not assume a
>       particular constant.  Rather, it should expect any lengths of
>       interface identifiers.
> 
> Thanks.

I am perfectly fine with waiting to clarify this in a implementors guide
style document.  This was trying to address the issue that some implementations
assume a 64 bit prefix when no such guidance have been given (i.e DHCP address lease).

The problem with adding this language now is that there should be consensus from
the working group since even though it looks like an editorial change, it really is not.

-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 Jul 09 13:45: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 1I7xIo-0006yq-9k; Mon, 09 Jul 2007 13:45:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7xIm-0006yg-HZ
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:45:36 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7xIm-00079Z-9f
	for ipv6@ietf.org; Mon, 09 Jul 2007 13:45:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 09 Jul 2007 13:45:28 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIMQkkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,517,1175486400"; 
	d="scan'208"; a="64711272:sNHT95885028"
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 l69HjRRV009425; 
	Mon, 9 Jul 2007 13:45:27 -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 l69HjR6c002397; 
	Mon, 9 Jul 2007 17:45:27 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, 9 Jul 2007 13:45:27 -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, 9 Jul 2007 13:45:25 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED3AA@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <46927239.8000002@hp.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Sending traffic to default router when RA has no PIO
Thread-Index: AcfCT8eXNZ79E44cQzCnQT9c8R32aAAAHnbg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03589CE5@xmb-rtp-20e.amer.cisco.com>
	<11836607373870-git-send-email-vladislav.yasevich@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A5C1@xmb-rtp-20e.amer.cisco.com>
	<468E98D7.5060109@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A8AB@xmb-rtp-20e.amer.cisco.com>
	<46924A07.4030504@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A935@xmb-rtp-20e.amer.cisco.com>
	<m2644tv70m.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D035ED376@xmb-rtp-20e.amer.cisco.com>
	<46927239.8000002@hp.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Vlad Yasevich" <vladislav.yasevich@hp.com>
X-OriginalArrivalTime: 09 Jul 2007 17:45:27.0700 (UTC)
	FILETIME=[EFA3A540:01C7C250]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1764; t=1184003127;
	x=1184867127; 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=20Sending=20traffic=20to=20default=20router=20when=20RA
	=20has=20no=20PIO |Sender:=20
	|To:=20=22Vlad=20Yasevich=22=20<vladislav.yasevich@hp.com>;
	bh=ayIzGNrjUT842rJBOjb15OCH/w/V/H+ppHiiQH9Y614=;
	b=Mxzzo7XBy4FEtxw3yJP9ACnG9bxMdZaSkssQKq22ztVZQseff2wPnMHJ8cpzNNE5cEoSwb07
	skEI6sz+xXGtfFBjpwdN4B1WGFGXWPedJ4Qpnfhh0lr77Pyh6rQTtltA;
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: c1c65599517f9ac32519d043c37c5336
Cc: ipv6@ietf.org, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

OK, if this needs consensus for a should to change to SHOULD in this
paragraph, then let's leave it.

Thanks.

Hemant=20

-----Original Message-----
From: Vlad Yasevich [mailto:vladislav.yasevich@hp.com]=20
Sent: Monday, July 09, 2007 1:37 PM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; ipv6@ietf.org
Subject: Re: Sending traffic to default router when RA has no PIO

Hemant Singh (shemant) wrote:
> Tatuya,
>=20
> If it's too late, it's fine.  On a different note, did you catch the=20
> fact from Vlad who wanted  "should" changed to "SHOULD" in a paragraph

> on page 18 of 2462bis? Further, we are also adding that a "should not"
> in the same paragraph be changed to "SHOULD NOT". Do you or anyone=20
> else think such a change can be made before the 12 hours expire? This=20
> is the relevant paragraph:
>=20
>       Note that a future revision of the address architecture
[RFC3513]
>       and a future link-type specific document, which will still be
>       consistent with each other, could potentially allow for an
>       interface identifier of length other than the value defined in
the
>       current documents.  Thus, an implementation should not assume a
>       particular constant.  Rather, it should expect any lengths of
>       interface identifiers.
>=20
> Thanks.

I am perfectly fine with waiting to clarify this in a implementors guide
style document.  This was trying to address the issue that some
implementations assume a 64 bit prefix when no such guidance have been
given (i.e DHCP address lease).

The problem with adding this language now is that there should be
consensus from the working group since even though it looks like an
editorial change, it really is not.

-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 Jul 09 14:53: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 1I7yMH-0002kV-8J; Mon, 09 Jul 2007 14:53:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7yMF-0002kO-RH
	for ipv6@ietf.org; Mon, 09 Jul 2007 14:53:15 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7yMB-0001Ui-I4
	for ipv6@ietf.org; Mon, 09 Jul 2007 14:53:15 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id CC690B8B9CD
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 11:53:10 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id BCA6529C002
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 11:53:10 -0700 (PDT)
X-AuditID: 11807123-a381dbb000000a55-24-469284168a68
Received: from [17.206.50.117] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id AC06D30400C
	for <ipv6@ietf.org>; Mon,  9 Jul 2007 11:53:10 -0700 (PDT)
In-Reply-To: <078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 9 Jul 2007 11:53:08 -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: 7a6398bf8aaeabc7a7bb696b6b0a2aad
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 Jul 3, 2007, at 13:23, Stephen Sprunk wrote:
>
> The only difference is that if there's a registry, the end-users  
> have someone to sue when a collision happens.

This sounds like yet another reason to hate ULA-C.  Seriously.


--
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 Jul 09 16:00: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 1I7zPD-0000Ue-Bn; Mon, 09 Jul 2007 16:00:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7zPC-0000UC-5Z
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:00:22 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I7zPB-0007lO-KE
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:00:22 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1184014596; x=1184619396; 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=Q4G1PfhrqLjsCI
	ffYcYjdIKadLB/pUh1uvjspa9gQmpbXcAjX4uhbGPz7kfnpXTRL0HRnJ3vB4w62b
	g9OaV3SCqXjPHtaRQcCqWkXMRUqyJIbC+augEzhnOQyEolKyJwnl9d4Pfa8jkWzJ
	1VxV+xPySPaA56ta0w3vLyFfiNp/k=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=tXVaqjP1Xbqp6tLeFJIFirCZcgtOTzaNFHQ/z1V9bpQG6DiwI1RX1ZsSFvvwJFFdLVJHLa+apZX8/OMXeWQNp/cXLroPTio9vpO8OSOPWXdb+ORXc1tUWsQcgrJqLYo1s5m55ggiHcpU1qojC/7suLSup502ReGp/JSGIHmv2Sc=;
Received: from [192.168.1.132] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002574215.msg
	for <ipv6@ietf.org>; Mon, 09 Jul 2007 21:56:16 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 09 Jul 2007 21:58:31 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C2B86007.1A22C2%jordi.palet@consulintel.es>
Thread-Topic: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfCY4YOxOXr4C5WEdyAIQAX8sYbNQ==
In-Reply-To: <46926BB2.3050607@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:070709:ipv6@ietf.org::s72M/70E/l8KyFwD:000015R+
X-MDRemoteIP: 86.45.142.3
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, Mon, 09 Jul 2007 21:56:31 +0200
X-MDAV-Processed: consulintel.es, Mon, 09 Jul 2007 21:56:36 +0200
X-Spam-Score: 1.8 (+)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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
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

Jeroen,

As usually, you're trying confuse folks, manipulate words and read the text
with your own thinking, not what is actually in the email text.

I'm not going to spend too much time on this, just clarify for the benefit
of others. Current proposals for PI aren't /32, as you know very well, as
you discussed about those proposals in the RIPE NCC address policy WG.

And read twice my text, which was only with a clarification purpose about
something wrong in the thread:
"I'm not saying that this is related to ULA-C, I still believe it should be
kept separated, and ULA-C is NOT to be used as a replacement of PA/PI, ...".

So if you want to manipulate text, please, do with your own emails, not with
clarifications from others.

Regards,
Jordi




> De: Jeroen Massar <jeroen@unfix.org>
> Organizaci=F3n: Unfix
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Mon, 09 Jul 2007 18:09:06 +0100
> Para: <jordi.palet@consulintel.es>
> CC: <ipv6@ietf.org>
> Asunto: Re: I-D ACTION:draft-ietf-ipv6-ula-central-02.txt
>=20
> JORDI PALET MARTINEZ wrote:
>> This is not correct. PI is not available from 2 RIRs, and there is not a
>> clear view of when it will become available. In one of them, because the
>> timing of the Policy Development Process, it will take at least 15 months to
>> get it implemented and this in the case it is approved in the next meeting
>> in almost one year from now.
>=20
> In other words you are trying to get "ULA PI" because the RIR policies
> take too long? You do realize that the ULA policies will have to also go
> through the same RIR communities and that they will be handled with the
> same skepticism as that those "PI" proposals (which allow a single
> end-user site to get a /32, which is really laughable) are being dealt with.
>=20
>> In the other one, even PA is not available unless you have 200 customers
>> (this is the same in other RIRs that already have PI).
>=20
> The IETF is not the place to discuss RIR policies. If the people who
> want to force through the new policies made up policies which actually
> made any sense and where fair to everybody then they would have been
> accepted already.
>=20
> With the current views on ULA (lets see how the next update of the draft
> will be) it is nothing more than just another variant of PI with a very
> weak attempt to avoid RIR policies, nothing else.
>=20
> If you really want to have "PI" in those RIR regions then come up with a
> good policy proposal on the RIR list, don't try to push it through. That
> is not how consensus works.
>=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 Mon Jul 09 16:28: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 1I7zqA-00068q-CB; Mon, 09 Jul 2007 16:28:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7zq8-00068H-Lq
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:28:12 -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 1I7zq7-0005hs-HX
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:28: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 9C036140C1B2;
	Mon,  9 Jul 2007 22:28:10 +0200 (CEST)
Message-ID: <46929A5E.1050905@spaghetti.zurich.ibm.com>
Date: Mon, 09 Jul 2007 21:28: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: jordi.palet@consulintel.es
References: <C2B86007.1A22C2%jordi.palet@consulintel.es>
In-Reply-To: <C2B86007.1A22C2%jordi.palet@consulintel.es>
X-Enigmail-Version: 0.95.2
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: a7d2e37451f7f22841e3b6f40c67db0f
Cc: ipv6@ietf.org
Subject: Clarity (Was: 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="===============1646785629=="
Errors-To: ipv6-bounces@ietf.org

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

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

JORDI PALET MARTINEZ wrote:
> Jeroen,
>=20
> As usually, you're trying confuse folks, manipulate words and read the =
text
> with your own thinking, not what is actually in the email text.

Wow, what has this to do with the whole ULA-C debate? Can you actually
supply any technical arguments instead of personal insults?

Clearly your words are ambiguous otherwise I could not read something
else in them now could I?

Write a draft about this with clear text, instead of trying to insult me
and trying to discredit what I write.

There is no intention, at least from my side, of "trying to confuse
folks" and there is no need to "manipulate words", what you propose is
wrong, and that is where I comment on.

As you are clearly accusing me of various bad things here, can you at
least exactly point out where I "manipulate words"? As then we can clear
those issues up instead of just having you throw rocks at me without any
grounds whatsoever.

> I'm not going to spend too much time on this, just clarify for the bene=
fit
> of others.

Thank you for explaining other people what you think on this subject.
Can you also provide TECHNICAL arguments and actual facts?

> Current proposals for PI aren't /32, as you know very well, as
> you discussed about those proposals in the RIPE NCC address policy WG.

Funny that you apparently know what I "know well", sorry you really
don't know how my mind works and neither do others. Weird that you are
trying to accuse me of manipulation of words. Amazing.

What I very well know is that those proposals do contain the loophole
that allow any end user organization to simply request a /32 as there is
no claim for justification given in the proposed documents.

It is also why several people have stated no support for those
proposals. If there was a simple rule of justification then they would
have been passed a long time ago. The proposed text though is ambiguous
and open for interpretation in too many ways.

Also that discussion belongs on the RIR lists though, not here. Go there
to accuse me of "manipulating your words".

> And read twice my text, which was only with a clarification purpose abo=
ut
> something wrong in the thread:
> "I'm not saying that this is related to ULA-C, I still believe it shoul=
d be
> kept separated, and ULA-C is NOT to be used as a replacement of PA/PI, =
=2E..".

That you believe that it should not be used for it doesn't mean that it
won't be used for it and that is what it is about here.

As can be seen very clearly from ris.ripe.net, see my other mail, even
RFC1918 is being leaked and routed. As that happens, it will for sure
happen for any form of "ULA" that is currently proposed as those are
globally unique and it would make sense that they are being routed as
that is what people need them for: Alternative PI because one can't get
it from the RIR's directly.

> So if you want to manipulate text, please, do with your own emails, not=
 with
> clarifications from others.

Thank you for the insults. The next time you try to do that at least
come up with real arguments.

Please bring up TECHNICAL arguments and facts for the discussion that we
are trying to have here instead of trying to insult members of this list
by you not being able/wanting to understand what I am writing.

If wordings of what I am writing is unclear, then ask for clarification
instead.

Greets,
 Jeroen


--------------enigCBB202F5A56D3F3637F42B2C
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/

iHUEARECADUFAkaSml4uFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I9SAAKC5TMxNKA0qlRdtTCRkUJx+efM8
VACgs7ErG0LoRF8/0poJOj0Sid+ni3Y=
=/7JX
-----END PGP SIGNATURE-----

--------------enigCBB202F5A56D3F3637F42B2C--


--===============1646785629==
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
--------------------------------------------------------------------

--===============1646785629==--




From ipv6-bounces@ietf.org Mon Jul 09 16:38: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 1I800U-0005ZL-Ig; Mon, 09 Jul 2007 16:38:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I800T-0005XD-H4
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:38:53 -0400
Received: from sca-ea-mail-2.sun.com ([192.18.43.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I800Q-0001PZ-Sf
	for ipv6@ietf.org; Mon, 09 Jul 2007 16:38:53 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l69KcfwO027180 for <ipv6@ietf.org>; Mon, 9 Jul 2007 20:38:42 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l69Kcc2P001331
	for <ipv6@ietf.org>; Mon, 9 Jul 2007 16:38:38 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l69K4nfi012787; Mon, 9 Jul 2007 16:04:49 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l69K4d9D012776;
	Mon, 9 Jul 2007 16:04:39 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-ID: <18066.38103.530393.802199@gargle.gargle.HOWL>
Date: Mon, 9 Jul 2007 16:04:39 -0400
From: James Carlson <james.d.carlson@sun.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / $B?@L@C#:H(B writes:
> I also agree that it is overkilling to require the receiving host to
> stop using the seemingly duplicate address.  We know DAD is not 100%
> reliable, so the best thing to do for such undetected duplicates would
> be to leave a warning/log message and let the administrator fix the
> issue by hand.  Requiring to stop using the address is also suboptimal
> in that it could be exploited by an attacker for DoS.

Sorry to jump in here late, but last week was a vacation week for many
here in the US.  :-/

I disagree a bit with this resolution.  These sorts of undetected
duplicate addresses do happen in practice, due to network partition/
repair and the effect of things like Spanning Tree's default port
blocking.

As a result, what I've done in the Solaris implementation is to
'defend' the address once -- by sending out my own advertisement in
reply to the received one -- but setting a flag.  If I see another
duplicate advertisement within some period of time (~10), then shut
the address down.

The logic behind this is:

  - Duplicate addresses are toxic to the network.  Above all, we must
    eliminate at least N-1 of the N duplicates on the network, because
    all other nodes will be confused.  It is _not_ sufficient to cry
    for help via a log message, and just hope for the best.

  - Sending my own advertisement helps make sure that the
    administrators of *BOTH* machines involved in the conflict are
    aware of the problem.  It's entirely possible that only one of
    those machines can be "fixed" with a new address, and that the
    local machine logging the problem isn't the one that can do it.

  - Duplicates can and do escape the initial probing period.  They
    need to be handled safely whenever they happen.

  - It's possible to drop back to probing (treat the address as
    tentative) after an address has been found to be duplicate.  In
    fact, this is what we do on Solaris, so that if the _other_
    machine is removed from the network, we'll recover automatically
    without intervention.

  - The DoS issue is a red herring.  NDP doesn't have security, and
    attackers can forge up bad advertisements any time they want.
    It's not a matter of "shutting down" the address -- confusing the
    peers on the network is sufficient to disrupt normal operation,
    and there's just no way to stop that.

Of course, given the text you're proposing, Solaris will in fact
gracefully back off and stop using the address, when it sees enough
conflicts.  I don't think other systems should fail to back off,
though.

>     On receipt of a valid Neighbor Advertisement message on an interface,
>     node behavior depends on whether the target address is tentative or
>     matches a unicast or anycast address assigned to the interface.  If
>     the target address is assigned to the receiving interface, the
>     advertisement SHOULD be discarded and the node SHOULD log a
>     system management error; this case would indicate that the address
>     is a duplicate but it has not been detected by the Duplicate
>     Address Detection procedure, which should be manually handled by
>     the system administrator.  If the target address is tentative, the
>     tentative address is not unique.
> 
> (the additional note "this case would indicate..." may sound too
> verbose.  If so, I'm willing to remove it.)
> 
> Does this make sense?

I don't think it's at all safe or reasonable to leave the network in a
state where there are two or more systems responding to solicitations
for the same address.  This needs to be pared down to one or fewer,
and should not require operator intervention to get there.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 09 18:07: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 1I81Nw-0002H3-Gg; Mon, 09 Jul 2007 18:07:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I81Nv-0002GR-8W
	for ipv6@ietf.org; Mon, 09 Jul 2007 18:07:11 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I81Nq-0008LT-Pv
	for ipv6@ietf.org; Mon, 09 Jul 2007 18:07:11 -0400
Received: from 219-90-138-181.ip.adam.com.au ([219.90.138.181]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I81Nk-0007VC-WE; Tue, 10 Jul 2007 07:37:01 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 22636FC83;
	Tue, 10 Jul 2007 07:36:59 +0930 (CST)
Date: Tue, 10 Jul 2007 07:36:58 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Jeroen Massar <jeroen@unfix.org>
Message-Id: <20070710073658.bd1c7827.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <46926FA4.8090603@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>
	<46782E58.6070705@spaghetti.zurich.ibm.com>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<469232FF.8040609@cisco.com> <90280.1184000252@sa.vix.com>
	<46926AAC.3010601@spaghetti.zurich.ibm.com>
	<90877.1184000942@sa.vix.com>
	<46926FA4.8090603@spaghetti.zurich.ibm.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: cf4fa59384e76e63313391b70cd0dd25
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 Mon, 09 Jul 2007 18:25:56 +0100
Jeroen Massar <jeroen@unfix.org> wrote:

> Paul Vixie wrote:

> 
> > in any case i called it "local" in ULA-G because i was stealing wholesale from
> > ULA-C (and i suspect they called it "local" because they were stealing from
> > ULA).  if you propose a term other than "private" (which is taken by RFC 1918)
> > that means "non-public" in the sense meant by ULA-G and ULA-C and ULA, there
> > might be great rejoicing.
> 

*** "INTERNAL" ***

Woohoo, I'm off to party! (at work)

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



From ipv6-bounces@ietf.org Mon Jul 09 18:39: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 1I81tA-0007KL-Qk; Mon, 09 Jul 2007 18:39:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I81t8-0007K6-Nk
	for ipv6@ietf.org; Mon, 09 Jul 2007 18:39:26 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I81st-00044U-Ds
	for ipv6@ietf.org; Mon, 09 Jul 2007 18:39:26 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 981F21A4D87; Mon,  9 Jul 2007 15:38:38 -0700 (PDT)
Date: Mon, 9 Jul 2007 15:38:38 -0700
From: bill fumerola <billf@mu.org>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <20070709223838.GO9951@elvis.mu.org>
References: <46926BB2.3050607@spaghetti.zurich.ibm.com>
	<C2B86007.1A22C2%jordi.palet@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C2B86007.1A22C2%jordi.palet@consulintel.es>
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: b19722fc8d3865b147c75ae2495625f2
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 Mon, Jul 09, 2007 at 09:58:31PM +0200, JORDI PALET MARTINEZ wrote:
> And read twice my text, which was only with a clarification purpose about
> something wrong in the thread:
> "I'm not saying that this is related to ULA-C, I still believe it should be
> kept separated, and ULA-C is NOT to be used as a replacement of PA/PI, ...".

i was already drafting a mail pointing out that the only part of your
mail he didn't quote was the one that deflated his entire attack on you.
i don't always agree with your proposals and suggestions, but please
continue to stick up for yourself when this happens. i didn't have enough
time in the day to do so when it was done to me.

> So if you want to manipulate text, please, do with your own emails, not with
> clarifications from others.

seriously. his replies to my mails were so misquoted i barely recognized
them as my own, my examples were extended to such stupid extremes (see
also: strawman) that i couldn't believe a networking professional would
even consider drawing such conclusions from those examples, and in general
my mails were returned with such hostility that i wonder if Mr. Massar's
purpose here is trying to achieve consensus or simply trying to detract
anyone from participating who doesn't share his own opinion.

i must admit, going on the RIR mailing lists and screaming "this is an
IETF problem, leave it alone" and then going to IETF mailing lists
screaming "this is a RIR problem, leave it alone" makes for a very
compelling and potentially successful technique.

kudos, Mr. Massar. kudos.

-- bill (in favor of the direction the vixie-global draft provides or
	 working towards a central-03 draft incorporating ideas from
	 the vixie draft)

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



From ipv6-bounces@ietf.org Mon Jul 09 19:45: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 1I82uT-0005D9-Ab; Mon, 09 Jul 2007 19:44:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I82uR-0005D2-Vt
	for ipv6@ietf.org; Mon, 09 Jul 2007 19:44:52 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I82uR-0005Nw-HP
	for ipv6@ietf.org; Mon, 09 Jul 2007 19:44:51 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id B09F71A4D87; Mon,  9 Jul 2007 16:44:18 -0700 (PDT)
Date: Mon, 9 Jul 2007 16:44:18 -0700
From: bill fumerola <billf@mu.org>
To: Stephen Sprunk <stephen@sprunk.org>
Message-ID: <20070709234418.GP9951@elvis.mu.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<D03E4899F2FB3D4C8464E8C76B3B68B0A46060@E03MVC4-UKBR.domain1.systemhost.net>
	<012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.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: 92df29fa99cf13e554b84c8374345c17
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 Mon, Jul 09, 2007 at 09:48:12AM -0500, Stephen Sprunk wrote:
> Good grief.  The RIRs today cannot guarantee ULA-C addresses _won't_ be 
> routed any more than they can guarantee PI/PA addresses _will_ be routed. 
> You seem to be proposing a shift in RIR policy where anyone who doesn't 
> play ball with arbitrary IETF rules get their allocations/assignments 
> revoked... Sorry, but I'm not signing that contract, nor is anyone else.  
> It'd never pass community consensus.
>
> RIRs have no power to do that today.  Routability of prefixes is solely in 
> the hands of ISPs that accept (or not) those routes.  And we do _not_ want 
> a world where some group of ivory tower academics and vendors tell 
> operators what they _must_ do on their own networks.  The Internet is 
> successful due to cooperation inspired by enlightened self-interest, not 
> central control.

AfriNIC apparently has decided they can get into the routability business
by stipulating that PIv6 space allocated must be 'announced' within a
year or it will be taken back. the first time they use that clause to
take back space, they'll have solidified that ability in their region.

power assumed is power allowed is power granted.

i agree that the routability verbiage in the AfriNIC PIv6 policy is bad
policy. i agree that each standards body and community service provider
has their place in making the the bits spin around the world properly.
i dispute that the IETF is powerless to give IANA and operators more
optionality (that they may choose to use or not use) simply because there
exists one other cat-skinning technique (depending where the cat currently
resides).

will ULA-* packets escape networks? yes. bogus packets leak out of
networks all the time. there's every reason to block packets from ULA-*
prefixes not in use by you everywhere possible as it applies to your
network.  private agreements to exchange ULA-[CG] routes between partner
companies notwithstanding.

will ULA-* routes leak? yes, but plenty of bogus routes leak now. RFC1918
prefixes, prefixes that aren't allocated, prefixes that people know "it's
ok to steal from those for internal use, since my customers will never
need routability to those prefixes", prefixes leaked out of just plain
stupidity. stopping ULA-[CG] will have zero impact on bogus routes in
the table: other efforts are addressing that, hopefully with success.

wouldn't it be nice if we could attach a contact to those leaked routes
and/or packets? it may not always be accurate, but it'd give a better
starting point than figuring out where that packet sourced 10.5.15.5
came from. i'm not saying depend on it, just that more accountability
cannot be a bad thing.

wouldn't it be nice to discuss what value ULA-[CG] prefixes could add,
instead of bringing up every possible way network addressing can be
abused.  this is the wrong forum to discuss well known abusive/bogus/broken
engineering. that can be applied to any address class.

i don't expect to change any opinions on this very religious topic. i
just hope that this doesn't get reduced to being passed back and forth
as Not Our Problem between RIRs and this WG. i hope bad RIR policies &
proposals aren't being used as examples of why this something the IETF
should stay out of.

should the I-D become standard: i hope people violently opposed to
ULA-[CG] don't use it, don't route it, don't announce it, and don't
accept announcements of it. that is the benefit of autonomous systems.
i hope people in favor of it are able to use the space in ways that help
them build the networks they want with all the possible tools and methods
available to them. used incorrectly, those operators will face all the
usual consequences of those who operate poorly run networks.


-- bill (who will stop leaking packets on the topic)


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



From ipv6-bounces@ietf.org Mon Jul 09 22:26: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 1I85PZ-00072g-UU; Mon, 09 Jul 2007 22:25:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I85PX-0006vZ-Qy
	for ipv6@ietf.org; Mon, 09 Jul 2007 22:25:07 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I85PT-0004wk-G7
	for ipv6@ietf.org; Mon, 09 Jul 2007 22:25:07 -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 1I85Ry-000BfE-K3
	for ipv6@ietf.org; Tue, 10 Jul 2007 02:27:38 +0000
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <A04E75C4-EDE3-461A-AFEC-1338CB53BC48@ca.afilias.info>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IPv6 WG <ipv6@ietf.org>
From: Joe Abley <jabley@ca.afilias.info>
Date: Mon, 9 Jul 2007 22:24:43 -0400
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 risk to the DFZ of leaking ULA-* {routes, packets, whatever}  
keeps coming up on this list. I thought I'd try to address just that  
problem in isolation, just to see whether I'm hearing things right.  
Please attack the following.

1. With PI address space there is an expectation of global utility  
(or, reachability across the DFZ, or however you want to describe  
"useful on the Internet"). I said expectation, not guarantee.

2. With ULA-* address space there would be no expectation of global  
utility. In fact, there would be an expectation that the addresses  
are for local use only (for some definition of "local").

3. There is doubt that any ULA-* address space would be kept properly  
local in all cases. In fact, there is an expectation that {routes,  
packets, something} would leak.

4. If some leaks are tolerated, then maybe, eventually, all leaks  
will be tolerated. Let's assume that will happen, just to see where  
it takes us.

5. If everybody has non-PA addresses (be they PI or ULA-*) and they  
are all leaked to the Internet, then the DFZ will suffer state  
explosion.

6. If operators can distinguish between should-be-local addresses  
(ULA-*) and allowed-to-be-global addresses (PI) in ASICs then  
operators can filter in order to head off the cataclysm looming in (5).

7. Since people were told up-front that their ULA-* addresses were no  
good for use on the Internet, step (6) shouldn't cause anybody to  
lock and load their lawyers.

(6) and (7) above ring true for ULA-* but not for PI-for-all. So, ULA- 
* would not harm the DFZ in the way that PI-for-all might harm the DFZ.


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 Jul 10 04:39: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 1I8BFE-0001bG-7h; Tue, 10 Jul 2007 04:38:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8BFC-0001b7-C6
	for ipv6@ietf.org; Tue, 10 Jul 2007 04:38:50 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8BFB-0004fy-LU
	for ipv6@ietf.org; Tue, 10 Jul 2007 04:38:50 -0400
Received: from ncg-dhcp66.isl.rdc.toshiba.co.jp (unknown
	[IPv6:2001:200:1b1:101a:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 9DF777301E;
	Tue, 10 Jul 2007 17:38:47 +0900 (JST)
Date: Tue, 10 Jul 2007 17:38:31 +0900
Message-ID: <m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <18066.38103.530393.802199@gargle.gargle.HOWL>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
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: 386e0819b1192672467565a524848168
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 9 Jul 2007 16:04:39 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> I disagree a bit with this resolution.  These sorts of undetected
> duplicate addresses do happen in practice, due to network partition/
> repair and the effect of things like Spanning Tree's default port
> blocking.
> 
> As a result, what I've done in the Solaris implementation is to
> 'defend' the address once -- by sending out my own advertisement in
> reply to the received one -- but setting a flag.  If I see another
> duplicate advertisement within some period of time (~10), then shut
> the address down.

I'm not sure if we are talking about the same thing, so please let me
check.  Are you saying "if a Solaris node happens to receive an NA
targeting an address assigned on the receiving interface, the node
will 'respond' to the NA with another NA (probably sent to ff02::1)
targeting the same address"?

In any case, I'd not disagree with trying to handle an address
duplicate that has not been detected in the initial DAD as a general
topic.  But I'd say it's basically beyond the scope of 2462bis.  In
fact, 2462(bis) simply admits DAD is not completely reliable (in
section 5.4) and doesn't specify any behavior to improve the
reliability.  Note also that this particular case (receiving an NA
targeting one of the receiver's own addresses) is a very minor case
among such undetected duplicates since an unsolicited NA is sent only
in very limited cases; if we were to do that within this spec, we'd
have to cover more likely scenarios such as receiving an RA with the
source address equal to a link-local address of the receiving
interface.  (But I don't think we wanted to address such cases in the
2462bis revision)

What we've actually been discussing in this thread is how to fix a
clear error in the 2462bis (and RFC2462/1971) text: it talked about
"how to handle a *solicitation*" in the "Receiving Neighbor
Advertisement" section.  It was an unfortunate side effect that we hit
the minor, yet pretty substantial, issue of undetected duplicates
while trying to resolve the seemingly editorial error.

So, in this particular context, I'd like to focus on solving the
obvious error within the scope of 2462bis; I don't want to go into the
possibly controversial discussion of how to deal with undetected
duplicates in this context.  Another revised proposal based on this
view is as follows.  How about that?

   On receipt of a valid Neighbor Advertisement message on an interface,
   node behavior depends on whether the target address is tentative or
   matches a unicast or anycast address assigned to the interface:

   1.  If the target address is tentative, the tentative address is not
       unique.

   2.  If the target address matches a unicast address assigned to the
       receiving interface, it would possibly indicate that the
       address is a duplicate but it has not been detected by the
       Duplicate Address Detection procedure (recall that Duplicate
       Address Detection is not completely reliable).  How to handle
       such a case is beyond the scope of this document, but care
       should be taken so that the advertisement will not affect the
       normal Neighbor Discovery [RFC4861] processing.

   3.  Otherwise, the advertisement is processed as described in
       [RFC4861].

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

p.s. one additional comment that is irrelevant to the original issue
of this topic:

>   - The DoS issue is a red herring.  NDP doesn't have security, and
>     attackers can forge up bad advertisements any time they want.
>     It's not a matter of "shutting down" the address -- confusing the
>     peers on the network is sufficient to disrupt normal operation,
>     and there's just no way to stop that.

On one hand, I agree; (pure) NDP is inherently vulnerable to on-local
attacks, so it may not really be reasonable to take account of local
attacks in the protocol design too much.

On the other hand, I'd point out the same argument could apply to the
"two-hour" rule adopted in RFC2462 and kept in 2462bis.  The consensus
at that time (IIRC) was that even though we knew it's an on-link only
attack the forced shut-down of an available global addresses was
serious enough to mitigate within the protocol specification.  And
since an unsolicited NA is a very rare event, I'd suspect it's more
likely an attack than an actual duplicate that happens to have been
undetected.

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



From ipv6-bounces@ietf.org Tue Jul 10 06:14: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 1I8Cjq-00057s-7G; Tue, 10 Jul 2007 06:14:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Cjp-00056c-7n
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:14:33 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Cjk-0007AX-Vl
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:14:33 -0400
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id C18938585;
	Tue, 10 Jul 2007 06:14:28 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute1.internal (MEProxy); Tue, 10 Jul 2007 06:14:28 -0400
X-Sasl-enc: LgahVxcUiV7poS2KvfYUOwiPM/+LZegl2D2Ggylv9dll 1184062466
Received: from [127.0.0.1] (anonymisierungsdienst2.foebud.org [85.214.71.55])
	by mail.messagingengine.com (Postfix) with ESMTP id 95CF146BF;
	Tue, 10 Jul 2007 06:14:20 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
Content-Type: text/plain
Date: Tue, 10 Jul 2007 12:13:58 +0200
Message-Id: <1184062438.14166.63.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: 8b30eb7682a596edff707698f4a80f7d
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 Mon, 2007-07-09 at 10:05 -0500, Stephen Sprunk wrote:
> > * ULA-C/G are NOT ment to be used on internet
> 
> OTOH, there's no way for the IETF or RIRs to stop it from happening.  I'm 
> not saying it will, but it is irresponsible to claim it won't when there's 
> no mechanism to enforce that.
> 

<sarcasm>
What is the mechanism to force operators to carry ULA prefixes?
</sarcasm>

Scalability-issues and operator's desire to combat abuse will keep ULA
out of the DFZ. If there were no limits on inter-domain-routing and we
had the ability to verify the authenticity of every prefix announced
none of this would be an issue. Then we could all have our own prefixes
and use them as we please. Private or public. 

Until such mechanisms are in place ULA-prefixes are likely to be
rejected by the majority of transit operators. ULA-blocks split in their
individual /48s (due to incompetence, accident or malice) won't fit in
any current or near-future routing hardware nor is there a reliable
mechanism to manage exceptions on a mass-scale.

ULA-C/G might be treated equal to PI some time in the future, but not
until there's a routing architecture able to cope with true PI-for-all.
If we're really concerned about end-users shouldn't we, as long as we're
unable to solve the basic architectural problems, instead work to
eliminate the arguments supporting the use of the various forms of ULA
or even PI?
(Should renumbering still be an issue regardless of the size of a site?
Why do we let rogue domain-registries and registrars take hostages and
limit portability? etc. etc...???)


/per




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



From ipv6-bounces@ietf.org Tue Jul 10 06:44: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 1I8DCv-0003D9-M6; Tue, 10 Jul 2007 06:44:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8DCt-0003Cg-O4
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:44:35 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8DCo-0007u3-Sy
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:44:35 -0400
Received: from compute2.internal (compute2.internal [10.202.2.42])
	by out1.messagingengine.com (Postfix) with ESMTP id B5DAB8783;
	Tue, 10 Jul 2007 06:44:30 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute2.internal (MEProxy); Tue, 10 Jul 2007 06:44:30 -0400
X-Sasl-enc: /sg4rYo0OQJC3wbrgVivuAU2ooCHZx/QsC0aYHMiwk1J 1184064267
Received: from [127.0.0.1] (unknown [208.66.78.226])
	by mail.messagingengine.com (Postfix) with ESMTP id 59FDB4710;
	Tue, 10 Jul 2007 06:44:18 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: bill fumerola <billf@mu.org>
In-Reply-To: <20070709234418.GP9951@elvis.mu.org>
References: <200706182316.l5INGcs6090861@drugs.dv.isc.org>
	<D03E4899F2FB3D4C8464E8C76B3B68B0A46060@E03MVC4-UKBR.domain1.systemhost.net>
	<012501c7c23a$a6c4b730$4f3816ac@atlanta.polycom.com>
	<20070709234418.GP9951@elvis.mu.org>
Content-Type: text/plain
Date: Tue, 10 Jul 2007 12:43:46 +0200
Message-Id: <1184064226.14166.80.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: 7655788c23eb79e336f5f8ba8bce7906
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 Mon, 2007-07-09 at 16:44 -0700, bill fumerola wrote:

> AfriNIC apparently has decided they can get into the routability business
> by stipulating that PIv6 space allocated must be 'announced' within a
> year or it will be taken back. the first time they use that clause to
> take back space, they'll have solidified that ability in their region.
> 

No, the AfriNIC community incl major trasit-operators in the region have
agreed to do that. The NIC does nothing other than what its community
asks for.

Unannounced blocks (PA or PI) and other "holes" in IR-assigned ranges
should imho be limited until there are good and reliable mechanisms to
verify the origin of individual prefixes. Hence it makes sense to
implement aggressive policies to reclaim unused space and restrict
private blocks to ULA.


//per




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



From ipv6-bounces@ietf.org Tue Jul 10 06: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 1I8DQQ-0006mi-CS; Tue, 10 Jul 2007 06:58:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8DQO-0006ma-6K
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:58:32 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8DQM-0001nU-1N
	for ipv6@ietf.org; Tue, 10 Jul 2007 06:58:32 -0400
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id BEADA84EF;
	Tue, 10 Jul 2007 06:58:09 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute1.internal (MEProxy); Tue, 10 Jul 2007 06:58:09 -0400
X-Sasl-enc: YAV1WlZDftB8iULkVxOrhWbhrPS1QaMU+5h/AuYYInad 1184065086
Received: from [127.0.0.1] (aquatorius.spemaus.net [212.112.241.44])
	by mail.messagingengine.com (Postfix) with ESMTP id 83D4440EF;
	Tue, 10 Jul 2007 06:57:58 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <018801c7c243$3e6bfb90$4f3816ac@atlanta.polycom.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>
	<4688C2CA.5050302@gmail.com> <43704.1183395211@sa.vix.com>
	<3CFC4261-BB5C-48F6-B8AF-A554D991F567@virtualized.org>
	<58873.1183400932@sa.vix.com>
	<63202.74.122.168.81.1183433230.squirrel@look.libertyrms.com>
	<44656.1183438512@sa.vix.com>
	<Pine.LNX.4.64.0707072145240.9923@chandra.student.uit.no>
	<026a01c7c108$bd3673b0$6701a8c0@atlanta.polycom.com>
	<Pine.LNX.4.64.0707081009000.9923@chandra.student.uit.no>
	<018801c7c243$3e6bfb90$4f3816ac@atlanta.polycom.com>
Content-Type: text/plain
Date: Tue, 10 Jul 2007 12:57:33 +0200
Message-Id: <1184065053.14166.88.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: 79899194edc4f33a41f49410777972f8
Cc: IETF IPv6 Mailing List <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 Mon, 2007-07-09 at 10:39 -0500, Stephen Sprunk wrote:

> 2.  ULA-C/G will be cheaper than PI space.
>     - This remains to be seen.
> 3.  ULA-C/G won't be publicly routed.
>     - There's no requirement you route PI space.

Nobody is required to route anything. It's recommendations from trusted
sources that count. 

Following the RIRs acceptance and implementation of PI policies most
such recommendations have been adjusted to allow /48s in PI-ranges in
addition to the existing /32s for PAs.


//per





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



From ipv6-bounces@ietf.org Tue Jul 10 07:07: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 1I8DYu-0005Zb-55; Tue, 10 Jul 2007 07:07:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8DYs-0005ZV-5v
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:07:18 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8DYr-0000Cn-JO
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:07:18 -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 l6AB7GQj099857
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 13:07:16 +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
	l6AB7Fj0010095; Tue, 10 Jul 2007 13:07:15 +0200
Date: Tue, 10 Jul 2007 13:07:15 +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: <46922300.6020101@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0707101245100.9923@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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<46922300.6020101@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: 8de5f93cb2b4e3bee75302e9eacc33db
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 Mon, 9 Jul 2007, Jeroen Massar wrote:
> Roger Jorgensen wrote:
<snip>
>> - anyone can, IF the ULA-C/G holder want to, resolve the IP in any given
>> ULA-C/G block through the global DNS system (a very very nice thing for
>> everyone that hate the pain split-DNS give you...additional administration)
>
> Please explain me how you are going to do *forward DNS* also. You know,
> most people type www.google.com, not the ip6.arpa ones and without the
> first, the latter is useless. You have to connect the forward zones
> anyway, so why not connect the reverse ones also. This has to be split
> DNS anyway, as a lot of companies are not willing to connect their
> internal systems in ANY way to the global Internet or let alone, expose
> those hostnames to that global Internet thing. Of course it is a lot of
> fun to be able to resolve big-red-button.oval-room.whitehouse.gov and at
> least know where to look for.

think most enterprises are willing to take that chance and only use _one_ 
forward zone no mather if it will be internal or external.

I personal dont like to expose internal thing to internet but I've 
realized that the it is quite harmless from a security point of view.


> Hint for security control freaks: DNS tunneling, you know it is fun :)
> And when you are able from your local (ULA) host to resolve a global DNS
> name you can do exactly that and more. Also what happens when a local
> guy types "www.google.com", do they get routed into oblivion or do you
> think they will not want to connect to that or to Wikipedia and a lot of
> resources on the Internet? Or are you going to use 2 IP addresses or
> more per host and create even a bigger management hell?

heard about proxy-servers? or http-relay, or transparent proxies ? They


> Stuffing *LOCAL* reverse DNS in the *GLOBAL* DNS doesn't make any sense.
> Either keep it totally local or keep it totally global (thus UA).

where exactly will this extra load on the GLOBAL DNS be? maybe a how is 
better to ask. I only see one place where there will be additional 
workload and thats for the root-servers. Most of the usage of ULA-C/G are 
said to be local so the highest usage will be on the far-bottom of the 
dns-structure. Just a few cases where network interconnect will there be 
created load on the root-servers.


This suggest is just for "scaring" off people and to make it less easy to 
get global DNS for ULA-C/G, nothing else.
What if we made the system so that getting global DNS for your ULA-C/G 
prefix become optional and it will have to be requested seperatly from 
the regular way of getting those prefixes?  In practice, when you request 
a ULA-C/G you dont get asked for reverse DNS servers, you will have to do 
that somewhere else...


> So how exactly is this ULA thing different from the UA (PI&PA) space
> that is already available? Why bother with ULA when one day you might
> most likely want to connect to the Internet anyway and cause pain then?
> Why lay that pain unto people?

what pain? I fail to see that except for the extra load mention furter up.


> The only real difference I see is that it is a well known block that
> people can force to not route, thus making a 2nd kind of Internet
> Citizen and a  monopoly situation for the folks who can and the ones who
> can't get UA space.

It is NOT supposed to be routed so no one should be forced to not route 
it. The real solution to this whole DMZ issue is to make PI so easy to get 
that everyone that need it can get it. Could even make the cost exactly 
the same and use the above mention not-mention-DNS during request of 
ULA-C/G to... just that alone could create that little extra touch to 
the thing whole thing and send them towards PI instead of ULA-C/G except 
for those that really really want ULA-C/G.


...

> Now I do see another use for this kind of address space, but then it
> should not be called this way. It could be used for ID/LOC solutions,
> where these kind of addresses are Explicit-non-DFZ addresses. But if
> that is the reason for what folks want to use them, as that is what I am
> sort of reading between the lines as actual real usage has still not
> been identified, then please just state that.

well, let ULA-C/G be the first step on this ID/LOC solution path? We will 
need it one way or another anyway...



-- 

------------------------------
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 Jul 10 07:16: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 1I8Dh6-0005Zf-5D; Tue, 10 Jul 2007 07:15:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Dh5-0005ZQ-8I
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:15:47 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Dh4-0000e3-Rf
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:15: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 l6ABFhuY030714
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 13:15: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
	l6ABFhDV010641; Tue, 10 Jul 2007 13:15:43 +0200
Date: Tue, 10 Jul 2007 13:15:43 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Eliot Lear <lear@cisco.com>
In-Reply-To: <469232FF.8040609@cisco.com>
Message-ID: <Pine.LNX.4.64.0707101315000.9923@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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<469232FF.8040609@cisco.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: 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 Mon, 9 Jul 2007, Eliot Lear wrote:
> Having had my name on RFC 1918, I think understand some of the issues.  There 
> is precisely one that I find at all interesting in this proposal, having 
> stated the concern in RFC 1627:
>
>   * avoiding collisions, and Geoff Huston's math demonstrates the
>     likelihood of that happening
>
> But one needn't have reverse lookups delegated in the root to address this 
> concern.

correct, that is two different thing, but combined they make ULA-C very 
usefull for alot of internal network thing in any big network.



-- 

------------------------------
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 Jul 10 07: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 1I8Dt1-000531-1K; Tue, 10 Jul 2007 07:28:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Dt0-00052w-5u
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:28:06 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Dsz-00010H-OD
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:28: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 l6ABS4kq034820
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 13:28:04 +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
	l6ABS4YP011408; Tue, 10 Jul 2007 13:28:04 +0200
Date: Tue, 10 Jul 2007 13:28:03 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
Message-ID: <Pine.LNX.4.64.0707101318230.9923@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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com><469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.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: 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

On Mon, 9 Jul 2007, Stephen Sprunk wrote:
> Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
<snip>
>> * ULA-C/G are NOT ment to be used on internet
>
> OTOH, there's no way for the IETF or RIRs to stop it from happening.  I'm not 
> saying it will, but it is irresponsible to claim it won't when there's no 
> mechanism to enforce that.

the point are to state that the purpose are NOT to be routed in the DFZ, 
not to make sure it never happen. That make-sure are upto those that use 
the address space and route it, not use as other also have stated.

<snip>
>> - anyone can, IF the ULA-C/G holder want to, resolve the IP in
>> any given ULA-C/G block through the global DNS system (a
>> very very nice thing for everyone that hate the pain split-DNS
>> give you...additional administration)
>
> There's no consensus yet that ULA-C/G will appear in the global DNS.  PI/PA 
> space definitely will.

that is why I state that ULA-C/G without DNS is not usable, it is a very 
usefull OPTION to have. Not something that everyone might want or want to 
use, but it is an option for those that want it...


<snip>
> If you start with the solution, one can always find problems that it solves. 
> However, if you start with a defined problem, the solution may not be what 
> you expect.  Every example you've given so far is solved at least as well by 
> PI space as by ULA space, and in some cases better by PI.

I am completly aware of that from a techincal point of view UA (PI and PA) 
vs. ULA-C/G are almost identifical. It is again the PURPOSE that are 
different, not the technical possibilities.

I would claim that the purpose part would decide what address space I 
would be using if I was about to build something.
Why is in the longer-context, right now we are making up the bricks you 
later can use for other things, like ID/LOC 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 Jul 10 07:37: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 1I8E1Z-0005ir-6A; Tue, 10 Jul 2007 07:36:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8E1X-0005bG-5J
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:36:55 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8E1W-0001HE-QD
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:36:55 -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 l6ABah1a037654
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 13:36: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
	l6ABagNs011946; Tue, 10 Jul 2007 13:36:42 +0200
Date: Tue, 10 Jul 2007 13:36: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: <46926BB2.3050607@spaghetti.zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0707101335570.9923@chandra.student.uit.no>
References: <C2B83522.1A2240%jordi.palet@consulintel.es>
	<46926BB2.3050607@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: de4f315c9369b71d7dd5909b42224370
Cc: ipv6@ietf.org, jordi.palet@consulintel.es
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 Mon, 9 Jul 2007, Jeroen Massar wrote:
<snip>
> With the current views on ULA (lets see how the next update of the draft
> will be) it is nothing more than just another variant of PI with a very
> weak attempt to avoid RIR policies, nothing else.

it is the PURPOSE part we seems to disagree on. ULA-C/G are NOT ment for 
DMZ while UA (PI/PA) are ment to be routed there.



-- 

------------------------------
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 Jul 10 07:39: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 1I8E3c-0007KG-1t; Tue, 10 Jul 2007 07:39:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8E3a-0007Ih-W9
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:39:02 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8E3a-0001Kk-Ka
	for ipv6@ietf.org; Tue, 10 Jul 2007 07:39:02 -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 l6ABcxTK007847
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 10 Jul 2007 13:38:59 +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
	l6ABcwsl012091; Tue, 10 Jul 2007 13:38:58 +0200
Date: Tue, 10 Jul 2007 13:38:58 +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: <94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
Message-ID: <Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@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: 7655788c23eb79e336f5f8ba8bce7906
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

On Mon, 9 Jul 2007, james woodyatt wrote:
> On Jul 3, 2007, at 13:23, Stephen Sprunk wrote:
>> The only difference is that if there's a registry, the end-users have 
>> someone to sue when a collision happens.
>
> This sounds like yet another reason to hate ULA-C.  Seriously.

must be you American (I assume you are) that are so afraid of someone 
being sued.I dont see that as a issue at all, we state a purpose and 
disclaimer and if someone are stupied enough to sue for collision, well 
they are darn stupid then. Sorry the language.

anyway if a collision happen, someone have really screwed up technical 
anyway and should be hung out for drying...



-- 

------------------------------
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 Jul 10 08:10: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 1I8EXh-0001jv-3t; Tue, 10 Jul 2007 08:10:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8EXf-0001jW-Bv
	for ipv6@ietf.org; Tue, 10 Jul 2007 08:10:07 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8EXc-0002EU-NL
	for ipv6@ietf.org; Tue, 10 Jul 2007 08:10:07 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6ACA1ga002533 for <ipv6@ietf.org>; Tue, 10 Jul 2007 12:10:02 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6AC9rWM007446
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 08:09:54 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6ABhdvW014575; Tue, 10 Jul 2007 07:43:39 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6ABhYVS014570;
	Tue, 10 Jul 2007 07:43:34 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-ID: <18067.28902.308977.27946@gargle.gargle.HOWL>
Date: Tue, 10 Jul 2007 07:43:34 -0400
From: James Carlson <james.d.carlson@sun.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / $B?@L@C#:H(B writes:
> At Mon, 9 Jul 2007 16:04:39 -0400,
> James Carlson <james.d.carlson@sun.com> wrote:
> > As a result, what I've done in the Solaris implementation is to
> > 'defend' the address once -- by sending out my own advertisement in
> > reply to the received one -- but setting a flag.  If I see another
> > duplicate advertisement within some period of time (~10), then shut
> > the address down.
> 
> I'm not sure if we are talking about the same thing, so please let me
> check.  Are you saying "if a Solaris node happens to receive an NA
> targeting an address assigned on the receiving interface, the node
> will 'respond' to the NA with another NA (probably sent to ff02::1)
> targeting the same address"?

Yes.  Obviously, since it's a potential feedback loop, it has
substantial safeguards on it, as I described above.  If we find we're
arguing, then the address is torn down.  (And, no, there's
intentionally no knob that allows the system to be "infinitely
persistent," though some users felt that was somehow necessary for
systems classed as "important servers.")

> In any case, I'd not disagree with trying to handle an address
> duplicate that has not been detected in the initial DAD as a general
> topic.  But I'd say it's basically beyond the scope of 2462bis.

Calling additional behavior here "beyond the scope" of the amended RFC
is fine by me.  The only part I'd disagree with is roping off the
ability to do such things by stating that implementations "MUST"
discard such messages.

> reliability.  Note also that this particular case (receiving an NA
> targeting one of the receiver's own addresses) is a very minor case
> among such undetected duplicates since an unsolicited NA is sent only
> in very limited cases; if we were to do that within this spec, we'd

Yep; understood.

> What we've actually been discussing in this thread is how to fix a
> clear error in the 2462bis (and RFC2462/1971) text: it talked about
> "how to handle a *solicitation*" in the "Receiving Neighbor
> Advertisement" section.  It was an unfortunate side effect that we hit
> the minor, yet pretty substantial, issue of undetected duplicates
> while trying to resolve the seemingly editorial error.

I think everyone essentially read "advertisement" (or just "packet")
here instead of "solicitation," without additional implications of
what gets discarded, as it was fairly obvious what was meant.

>    2.  If the target address matches a unicast address assigned to the
>        receiving interface, it would possibly indicate that the
>        address is a duplicate but it has not been detected by the
>        Duplicate Address Detection procedure (recall that Duplicate
>        Address Detection is not completely reliable).  How to handle
>        such a case is beyond the scope of this document, but care
>        should be taken so that the advertisement will not affect the
>        normal Neighbor Discovery [RFC4861] processing.

This seems better to me, as it clarifies the scope, though I'm
somewhat unclear on what the last clause actually implies.

How should an implementor actually take care here?  Are you perhaps
referring to the possibility of endless NA battles between a pair of
misconfigured systems?  Or something else?

I might have worded it something like this:

	How to handle such a case is beyond the scope of this
	document, but implementations that take any action other than
	discarding the message MUST take measures to avoid an infinite
	series of advertisements triggered by reception of such
	messages.

Or just:

	How to handle such a case is beyond the scope of this
	document, and implementations MAY log and discard such
	messages.

> On the other hand, I'd point out the same argument could apply to the
> "two-hour" rule adopted in RFC2462 and kept in 2462bis.  The consensus
> at that time (IIRC) was that even though we knew it's an on-link only
> attack the forced shut-down of an available global addresses was
> serious enough to mitigate within the protocol specification.  And
> since an unsolicited NA is a very rare event, I'd suspect it's more
> likely an attack than an actual duplicate that happens to have been
> undetected.

The two-hour rule has always struck me as more of a robustness issue
than anything else.

The point I was making was that a denial of service attack against NDP
is not just feasible, but trivial, and that bringing up DoS as a
reason to ignore assumed-incorrect advertisements doesn't seem like a
productive way to frame the argument.

Instead, the issue is determining what happens to _all_ of the systems
observing these messages on the wire.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 10 08:18: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 1I8EfU-0008U8-06; Tue, 10 Jul 2007 08:18:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8EfS-0008Tx-Ee
	for ipv6@ietf.org; Tue, 10 Jul 2007 08:18:10 -0400
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8EfR-0003lq-Ks
	for ipv6@ietf.org; Tue, 10 Jul 2007 08:18:10 -0400
DKIM-Signature: a=rsa-sha1; c=nowsp; d=consulintel.es; s=MDaemon;
	t=1184073260; x=1184678060; 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=byasdyEAp7zLB9
	ClZv/g31fvhZzOfeHEWiGSITDnAkWU5ZB4lOD6fmnCk7qjR6nVPXqWgU/vhM+ItN
	oST1Nktb3HPEV1+8qi6QiI+PmxtcSf9OudRALNDQHr4VwT7i7Z3wZinvR1sETmhj
	WP2xNhZ+8iAaSJD3kP7IAi8r5zUSI=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es;
	c=simple; q=dns; h=from:message-id;
	b=isuw4f/CCuQUAzPU/bOZ5vmXyl9jbjAlcV5Lnrm/ZiqpgUhV6uQjElNeZDQ9c0cQRO8kGoyQi/L6I/Sw19SWCp8DtSnfNgkNSXF76KZjkLUFEd0pOHcZAwHS5JXDL4Gr7Mc9dGx7h0Fo9Y/ybMYrbxPa0ulHetr/dNidUVdNLaE=;
Received: from [127.0.0.1] by consulintel.es (MDaemon.PRO.v8.1.5.R)
	with ESMTP id md50002575121.msg
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 14:14:19 +0200
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 10 Jul 2007 09:58:52 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ipv6@ietf.org>
Message-ID: <C2B908DC.1A2394%jordi.palet@consulintel.es>
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfC0ImMyBISyi7DEdyAIQAX8sYbNQ==
In-Reply-To: <20070709234418.GP9951@elvis.mu.org>
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:070710:ipv6@ietf.org::zS+uIythaXfcHHBd:00001IfV
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, Tue, 10 Jul 2007 14:14:19 +0200
X-MDAV-Processed: consulintel.es, Tue, 10 Jul 2007 14:14:20 +0200
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Subject: Re: draft-ietf-ipv6-ula-central-02.txt
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

In many RIRs the existing policies for IPv6 PA also state somehow that the
prefix need to be announced (AND aggregated) in a specific time (1 or 2
years), so this is not something new. I'm not saying it is good or bad, I
agree or disagree, just as an info.

Regards,
Jordi




> De: bill fumerola <billf@mu.org>
> Responder a: <ipv6-bounces@ietf.org>
> Fecha: Mon, 9 Jul 2007 16:44:18 -0700
> Para: Stephen Sprunk <stephen@sprunk.org>
> CC: <ipv6@ietf.org>
> Asunto: Re: draft-ietf-ipv6-ula-central-02.txt
> 
> On Mon, Jul 09, 2007 at 09:48:12AM -0500, Stephen Sprunk wrote:
>> Good grief.  The RIRs today cannot guarantee ULA-C addresses _won't_ be
>> routed any more than they can guarantee PI/PA addresses _will_ be routed.
>> You seem to be proposing a shift in RIR policy where anyone who doesn't
>> play ball with arbitrary IETF rules get their allocations/assignments
>> revoked... Sorry, but I'm not signing that contract, nor is anyone else.
>> It'd never pass community consensus.
>> 
>> RIRs have no power to do that today.  Routability of prefixes is solely in
>> the hands of ISPs that accept (or not) those routes.  And we do _not_ want
>> a world where some group of ivory tower academics and vendors tell
>> operators what they _must_ do on their own networks.  The Internet is
>> successful due to cooperation inspired by enlightened self-interest, not
>> central control.
> 
> AfriNIC apparently has decided they can get into the routability business
> by stipulating that PIv6 space allocated must be 'announced' within a
> year or it will be taken back. the first time they use that clause to
> take back space, they'll have solidified that ability in their region.
> 
> power assumed is power allowed is power granted.
> 
> i agree that the routability verbiage in the AfriNIC PIv6 policy is bad
> policy. i agree that each standards body and community service provider
> has their place in making the the bits spin around the world properly.
> i dispute that the IETF is powerless to give IANA and operators more
> optionality (that they may choose to use or not use) simply because there
> exists one other cat-skinning technique (depending where the cat currently
> resides).
> 
> will ULA-* packets escape networks? yes. bogus packets leak out of
> networks all the time. there's every reason to block packets from ULA-*
> prefixes not in use by you everywhere possible as it applies to your
> network.  private agreements to exchange ULA-[CG] routes between partner
> companies notwithstanding.
> 
> will ULA-* routes leak? yes, but plenty of bogus routes leak now. RFC1918
> prefixes, prefixes that aren't allocated, prefixes that people know "it's
> ok to steal from those for internal use, since my customers will never
> need routability to those prefixes", prefixes leaked out of just plain
> stupidity. stopping ULA-[CG] will have zero impact on bogus routes in
> the table: other efforts are addressing that, hopefully with success.
> 
> wouldn't it be nice if we could attach a contact to those leaked routes
> and/or packets? it may not always be accurate, but it'd give a better
> starting point than figuring out where that packet sourced 10.5.15.5
> came from. i'm not saying depend on it, just that more accountability
> cannot be a bad thing.
> 
> wouldn't it be nice to discuss what value ULA-[CG] prefixes could add,
> instead of bringing up every possible way network addressing can be
> abused.  this is the wrong forum to discuss well known abusive/bogus/broken
> engineering. that can be applied to any address class.
> 
> i don't expect to change any opinions on this very religious topic. i
> just hope that this doesn't get reduced to being passed back and forth
> as Not Our Problem between RIRs and this WG. i hope bad RIR policies &
> proposals aren't being used as examples of why this something the IETF
> should stay out of.
> 
> should the I-D become standard: i hope people violently opposed to
> ULA-[CG] don't use it, don't route it, don't announce it, and don't
> accept announcements of it. that is the benefit of autonomous systems.
> i hope people in favor of it are able to use the space in ways that help
> them build the networks they want with all the possible tools and methods
> available to them. used incorrectly, those operators will face all the
> usual consequences of those who operate poorly run networks.
> 
> 
> -- bill (who will stop leaking packets on the topic)
> 
> 
> --------------------------------------------------------------------
> 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 Tue Jul 10 10:22: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 1I8GbC-0003s5-A1; Tue, 10 Jul 2007 10:21:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8GbA-0003rw-QS
	for ipv6@ietf.org; Tue, 10 Jul 2007 10:21:52 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8GbA-00065t-3c
	for ipv6@ietf.org; Tue, 10 Jul 2007 10:21:52 -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 886E2114021
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 14:21:51 +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 85388E609B
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 14:21:50 +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 l6AELgNg094158;
	Wed, 11 Jul 2007 00:21:47 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200707101421.l6AELgNg094158@drugs.dv.isc.org>
To: Roger Jorgensen <rogerj@jorgensen.no>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Tue, 10 Jul 2007 13:07:15 +0200."
	<Pine.LNX.4.64.0707101245100.9923@chandra.student.uit.no> 
Date: Wed, 11 Jul 2007 00:21:42 +1000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
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 Mon, 9 Jul 2007, Jeroen Massar wrote:
> > Roger Jorgensen wrote:
> <snip>
> >> - anyone can, IF the ULA-C/G holder want to, resolve the IP in any given
> >> ULA-C/G block through the global DNS system (a very very nice thing for
> >> everyone that hate the pain split-DNS give you...additional administration
> )
> >
> > Please explain me how you are going to do *forward DNS* also. You know,
> > most people type www.google.com, not the ip6.arpa ones and without the
> > first, the latter is useless. You have to connect the forward zones
> > anyway, so why not connect the reverse ones also. This has to be split
> > DNS anyway, as a lot of companies are not willing to connect their
> > internal systems in ANY way to the global Internet or let alone, expose
> > those hostnames to that global Internet thing. Of course it is a lot of
> > fun to be able to resolve big-red-button.oval-room.whitehouse.gov and at
> > least know where to look for.
> 
> think most enterprises are willing to take that chance and only use _one_ 
> forward zone no mather if it will be internal or external.
> 
> I personal dont like to expose internal thing to internet but I've 
> realized that the it is quite harmless from a security point of view.
> 
> 
> > Hint for security control freaks: DNS tunneling, you know it is fun :)
> > And when you are able from your local (ULA) host to resolve a global DNS
> > name you can do exactly that and more. Also what happens when a local
> > guy types "www.google.com", do they get routed into oblivion or do you
> > think they will not want to connect to that or to Wikipedia and a lot of
> > resources on the Internet? Or are you going to use 2 IP addresses or
> > more per host and create even a bigger management hell?
> 
> heard about proxy-servers? or http-relay, or transparent proxies ? They
> 
> 
> > Stuffing *LOCAL* reverse DNS in the *GLOBAL* DNS doesn't make any sense.
> > Either keep it totally local or keep it totally global (thus UA).
> 
> where exactly will this extra load on the GLOBAL DNS be? maybe a how is 
> better to ask. I only see one place where there will be additional 
> workload and thats for the root-servers. Most of the usage of ULA-C/G are 
> said to be local so the highest usage will be on the far-bottom of the 
> dns-structure. Just a few cases where network interconnect will there be 
> created load on the root-servers.

	Wrong.  The load will not be on the root servers.  It will
	however be on the C.F.IP6.INT servers for all the active
	ULA-C blocks that do not have nameservers configured for
	them.

	There will still be leaked packets going to the root servers
	but that will be much less than the traffic going to the
	C.F.IP6.INT if there arn't delegations made.

	We know from the AS112 expriences with RFC 1918 address
	that queries will be emitted if there arn't internal zones
	configured.  We also know that the aggregate traffic will
	be large.

	The point of requesting that globally reachable nameservers
	exist is to absorb that traffic.  I expect that in most
	cases there will be multi-homed nameservers which answer
	both internal and external queries.  Once you have to setup
	a nameserver you may as well allow the zone to be populated.

	Any queries that come out of the site will get referrals
	back to these, presumably, on site nameservers.  Not that
	efficient but also not a large impact on the infrastucture
	servers.

	If the site chooses to out source the servers then I expect
	the out sourcing providers will have a variable scale
	depending upon the query load.  If a site chooses to let
	queries for on site addresses leave the site it will be
	reflected in query load and presumably price.

> This suggest is just for "scaring" off people and to make it less easy to 
> get global DNS for ULA-C/G, nothing else.
> What if we made the system so that getting global DNS for your ULA-C/G 
> prefix become optional and it will have to be requested seperatly from 
> the regular way of getting those prefixes?  In practice, when you request 
> a ULA-C/G you dont get asked for reverse DNS servers, you will have to do 
> that somewhere else...
> 
> 
> > So how exactly is this ULA thing different from the UA (PI&PA) space
> > that is already available? Why bother with ULA when one day you might
> > most likely want to connect to the Internet anyway and cause pain then?
> > Why lay that pain unto people?
> 
> what pain? I fail to see that except for the extra load mention furter up.
> 
> 
> > The only real difference I see is that it is a well known block that
> > people can force to not route, thus making a 2nd kind of Internet
> > Citizen and a  monopoly situation for the folks who can and the ones who
> > can't get UA space.
> 
> It is NOT supposed to be routed so no one should be forced to not route 
> it. The real solution to this whole DMZ issue is to make PI so easy to get 
> that everyone that need it can get it. Could even make the cost exactly 
> the same and use the above mention not-mention-DNS during request of 
> ULA-C/G to... just that alone could create that little extra touch to 
> the thing whole thing and send them towards PI instead of ULA-C/G except 
> for those that really really want ULA-C/G.
> 
> 
> ...
> 
> > Now I do see another use for this kind of address space, but then it
> > should not be called this way. It could be used for ID/LOC solutions,
> > where these kind of addresses are Explicit-non-DFZ addresses. But if
> > that is the reason for what folks want to use them, as that is what I am
> > sort of reading between the lines as actual real usage has still not
> > been identified, then please just state that.
> 
> well, let ULA-C/G be the first step on this ID/LOC solution path? We will 
> need it one way or another anyway...
> 
> 
> 
> -- 
> 
> ------------------------------
> 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
> --------------------------------------------------------------------
-- 
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 Jul 10 10: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 1I8H09-0006vp-8r; Tue, 10 Jul 2007 10:47:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8H07-0006va-NL
	for ipv6@ietf.org; Tue, 10 Jul 2007 10:47:39 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8H07-0006kP-1z
	for ipv6@ietf.org; Tue, 10 Jul 2007 10:47:39 -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 E333E7301E;
	Tue, 10 Jul 2007 23:47:35 +0900 (JST)
Date: Tue, 10 Jul 2007 23:47:34 +0900
Message-ID: <m2vecstiwp.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <18067.28902.308977.27946@gargle.gargle.HOWL>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
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.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 10 Jul 2007 07:43:34 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> >    2.  If the target address matches a unicast address assigned to the
> >        receiving interface, it would possibly indicate that the
> >        address is a duplicate but it has not been detected by the
> >        Duplicate Address Detection procedure (recall that Duplicate
> >        Address Detection is not completely reliable).  How to handle
> >        such a case is beyond the scope of this document, but care
> >        should be taken so that the advertisement will not affect the
> >        normal Neighbor Discovery [RFC4861] processing.
> 
> This seems better to me, as it clarifies the scope, though I'm
> somewhat unclear on what the last clause actually implies.
> 
> How should an implementor actually take care here?  Are you perhaps
> referring to the possibility of endless NA battles between a pair of
> misconfigured systems?  Or something else?

I intended, for example, that implementations should not affect their
neighbor caches as a result of processing the NA "as described in
[RFC4861=2461bis]".  I thought a naive implementation may be confused
by the received NA and modify the link-layer address information of
its own address (realized as a special type of neighbor cache).

> I might have worded it something like this:
> 
> 	How to handle such a case is beyond the scope of this
> 	document, but implementations that take any action other than
> 	discarding the message MUST take measures to avoid an infinite
> 	series of advertisements triggered by reception of such
> 	messages.
> 
> Or just:
> 
> 	How to handle such a case is beyond the scope of this
> 	document, and implementations MAY log and discard such
> 	messages.

After understanding the proposed text was not really clear, I guess we
should rather be silent and just state:

   2.  If the target address matches a unicast address assigned to the
       receiving interface, it would possibly indicate that the
       address is a duplicate but it has not been detected by the
       Duplicate Address Detection procedure (recall that Duplicate
       Address Detection is not completely reliable).  How to handle
       such a case is beyond the scope of this document.

This is probably enough since this bullet is clearly separated from
bullet #3.  Does this work for you (and others)?

					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 Jul 10 11:16: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 1I8HRg-0004Ok-JL; Tue, 10 Jul 2007 11:16:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8HRf-0004OL-Fl
	for ipv6@ietf.org; Tue, 10 Jul 2007 11:16:07 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8HRf-0007j2-7a
	for ipv6@ietf.org; Tue, 10 Jul 2007 11:16:07 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6AFG6Ib008054 for <ipv6@ietf.org>; Tue, 10 Jul 2007 15:16:06 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6AFG3Fr006957
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 11:16:05 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6AErPEU015540; Tue, 10 Jul 2007 10:53:25 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6AErPIb015535;
	Tue, 10 Jul 2007 10:53:25 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-ID: <18067.40293.346280.810671@gargle.gargle.HOWL>
Date: Tue, 10 Jul 2007 10:53:25 -0400
From: James Carlson <james.d.carlson@sun.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m2vecstiwp.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
	<m2vecstiwp.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Vlad Yasevich <vladislav.yasevich@hp.com>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / $B?@L@C#:H(B writes:
> At Tue, 10 Jul 2007 07:43:34 -0400,
> James Carlson <james.d.carlson@sun.com> wrote:
> > How should an implementor actually take care here?  Are you perhaps
> > referring to the possibility of endless NA battles between a pair of
> > misconfigured systems?  Or something else?
> 
> I intended, for example, that implementations should not affect their
> neighbor caches as a result of processing the NA "as described in
> [RFC4861=2461bis]".  I thought a naive implementation may be confused
> by the received NA and modify the link-layer address information of
> its own address (realized as a special type of neighbor cache).

Ah ... and "yikes!"

I hadn't considered that level of confusion.  Yes, I agree that this
ought to be ruled out, and could perhaps be done explicitly.

	"Such an unexpected advertisement MUST NOT be processed in a
	way that modifies the neighbor cache entry for the conflicting
	address."

> After understanding the proposed text was not really clear, I guess we
> should rather be silent and just state:
> 
>    2.  If the target address matches a unicast address assigned to the
>        receiving interface, it would possibly indicate that the
>        address is a duplicate but it has not been detected by the
>        Duplicate Address Detection procedure (recall that Duplicate
>        Address Detection is not completely reliable).  How to handle
>        such a case is beyond the scope of this document.
> 
> This is probably enough since this bullet is clearly separated from
> bullet #3.  Does this work for you (and others)?

That works for me.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 10 11:18: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 1I8HTl-0007M9-Qz; Tue, 10 Jul 2007 11:18:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8HTa-0007A1-Ty
	for ipv6@ietf.org; Tue, 10 Jul 2007 11:18:06 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8HTa-0007vS-9l
	for ipv6@ietf.org; Tue, 10 Jul 2007 11:18:06 -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 48AA57301E;
	Wed, 11 Jul 2007 00:18:05 +0900 (JST)
Date: Wed, 11 Jul 2007 00:18:03 +0900
Message-ID: <m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <18067.28902.308977.27946@gargle.gargle.HOWL>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
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.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

(Intentionally separating the thread since this is irrelevant to the
main focus of completing 2462bis)

At Tue, 10 Jul 2007 07:43:34 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> > On the other hand, I'd point out the same argument could apply to the
> > "two-hour" rule adopted in RFC2462 and kept in 2462bis.  The consensus
> > at that time (IIRC) was that even though we knew it's an on-link only
> > attack the forced shut-down of an available global addresses was
> > serious enough to mitigate within the protocol specification.  And
> > since an unsolicited NA is a very rare event, I'd suspect it's more
> > likely an attack than an actual duplicate that happens to have been
> > undetected.
> 
> The two-hour rule has always struck me as more of a robustness issue
> than anything else.

I'm not sure if you are indicating by "robustness" that it's not an
issue of DoS, but the fact is that the two-hour rule was indeed
introduced as a counter-measure of a DoS attack (I guess you knew
that, but just in case...).

> The point I was making was that a denial of service attack against NDP
> is not just feasible, but trivial, and that bringing up DoS as a
> reason to ignore assumed-incorrect advertisements doesn't seem like a
> productive way to frame the argument.

I admit whether discarding the NA may be a debatable behavior (with or
without logging the event), but I don't think discussing this in the
context of DoS, referring to the two-hour rule, is unproductive.  An
attacker can easily make the Solaris node shut down an address by
sending two attacking NAs.  The attacker can also mount the same
attack on any other nodes in the link by first pinging them to collect
the addresses and then performing the attack with the forged NAs.

We could still argue that such an attack is "trivial" and discussion
based on the "trivial" attack is not productive.  But if so, we should
also revisit the two hour rule, too.  As long as we keep that rule, it
makes more sense to me to consider a counter measure for the same
level of security threats.

To avoid wasting our time further, however..., I personally think this
particular case isn't worth further debates.  As I repeatedly noted,
we don't see unsolicited NAs very often in the first place, whether it
would indicate a duplicate address or an attack.  We can safely leave
it to implementations without a fear of disruption in practice.  So,
I'll stop here on this matter until, someday, we need to discuss how
to address undetected duplicates in general.

					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 Jul 10 12:03: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 1I8IBM-0003YG-RP; Tue, 10 Jul 2007 12:03:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8IBL-0003YA-VI
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:03:19 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8IBL-0000rP-IO
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:03:19 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 10 Jul 2007 12:03:19 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANBKk0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,523,1175486400"; 
	d="scan'208"; a="64801881:sNHT57521080"
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 l6AG3JgO001344; 
	Tue, 10 Jul 2007 12:03:19 -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 l6AG3Ds0018026; 
	Tue, 10 Jul 2007 16:03:19 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, 10 Jul 2007 12:03:02 -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, 10 Jul 2007 12:03:01 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED7AB@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: AcfDBZHFKP/v3UfvTNeO9PEs8I0MmAAAGjSA
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp><m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com><m2k5te7vq2.wl%jinmei@wide.ad.jp><B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com><m2hcoi7s5p.wl%jinmei@wide.ad.jp>
	<468D22F9.7000700@ericsson.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com><468D3322.5080503@ericsson.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com><468D58CD.6090204@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com><m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp><18066.38103.530393.802199@gargle.gargle.HOWL><m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp><18067.28902.308977.27946@gargle.gargle.HOWL>
	<m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 10 Jul 2007 16:03:02.0559 (UTC)
	FILETIME=[CB434AF0:01C7C30B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4496; t=1184083399;
	x=1184947399; 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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=0A=20=20=20=20=20=20=20=20=22James=20Carlson=22=20<james.d.carlson@sun.co
	m>; bh=LJUT9dzyz10ouptjOsObnZo7phz2QtUEi+DDMoFIYKI=;
	b=p8sfyF2S/388RzJK4k7sgjsBCzyqyt6Xp+qON/6kV7xHMzLHt+laSMXwgCwFcJ2PkOoRGLNk
	Yt8XFvNljTuzJ6Z+Q06usD1Fj7kEvUtfOWGi7CR+5P5tw81rK05GoRvb;
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: 6d95a152022472c7d6cdf886a0424dc6
Cc: ipv6@ietf.org
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

The gist of your new paragraph is fine by me. However, you have un-fixed
what I clearly defined in the past for behavior. The match statement has
to apply to tentative address as well as an assigned address. Here is a
suggestion for change in bullet 1:


 1.  If the target address is tentative, the tentative address is not
     unique.

changes to

 1.  If the target address matches a tentative address on the receiving
interface,=20
     the tentative address is not unique.

There is a distinct case where the receiving interface gets an NA where
target address in NA does not match any tentative address on the
interface.

Further, in an email you said:

You said:

"I intended, for example, that implementations should not affect their
neighbor caches as a result of processing the NA "as described in
[RFC4861=3D2461bis]".  I thought a naive implementation may be confused =
by
the received NA and modify the link-layer address information of its own
address (realized as a special type of neighbor cache)."

Even if a bad link-layer address gets into the ND cache of the receiving
node, the  node have NUD kick in within 30-50 seconds and issue a mcast
NS to resolve the destination IPv6 address that will result in the bad
address to be replaced.

Hemant=20

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Tuesday, July 10, 2007 11:18 AM
To: James Carlson
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

(Intentionally separating the thread since this is irrelevant to the
main focus of completing 2462bis)

At Tue, 10 Jul 2007 07:43:34 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> > On the other hand, I'd point out the same argument could apply to=20
> > the "two-hour" rule adopted in RFC2462 and kept in 2462bis.  The=20
> > consensus at that time (IIRC) was that even though we knew it's an=20
> > on-link only attack the forced shut-down of an available global=20
> > addresses was serious enough to mitigate within the protocol=20
> > specification.  And since an unsolicited NA is a very rare event,=20
> > I'd suspect it's more likely an attack than an actual duplicate that

> > happens to have been undetected.
>=20
> The two-hour rule has always struck me as more of a robustness issue=20
> than anything else.

I'm not sure if you are indicating by "robustness" that it's not an
issue of DoS, but the fact is that the two-hour rule was indeed
introduced as a counter-measure of a DoS attack (I guess you knew that,
but just in case...).

> The point I was making was that a denial of service attack against NDP

> is not just feasible, but trivial, and that bringing up DoS as a=20
> reason to ignore assumed-incorrect advertisements doesn't seem like a=20
> productive way to frame the argument.

I admit whether discarding the NA may be a debatable behavior (with or
without logging the event), but I don't think discussing this in the
context of DoS, referring to the two-hour rule, is unproductive.  An
attacker can easily make the Solaris node shut down an address by
sending two attacking NAs.  The attacker can also mount the same attack
on any other nodes in the link by first pinging them to collect the
addresses and then performing the attack with the forged NAs.

We could still argue that such an attack is "trivial" and discussion
based on the "trivial" attack is not productive.  But if so, we should
also revisit the two hour rule, too.  As long as we keep that rule, it
makes more sense to me to consider a counter measure for the same level
of security threats.

To avoid wasting our time further, however..., I personally think this
particular case isn't worth further debates.  As I repeatedly noted, we
don't see unsolicited NAs very often in the first place, whether it
would indicate a duplicate address or an attack.  We can safely leave it
to implementations without a fear of disruption in practice.  So, I'll
stop here on this matter until, someday, we need to discuss how to
address undetected duplicates in general.

					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 Jul 10 12:11: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 1I8IJd-0001WU-Dm; Tue, 10 Jul 2007 12:11:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8IJb-0001WC-7z
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:11:51 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8IJM-0000lh-KO
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:11:51 -0400
Received: from eastmail4bur.east.Sun.COM ([129.148.13.1])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6AGBBWt013231 for <ipv6@ietf.org>; Tue, 10 Jul 2007 16:11:11 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail4bur.east.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6AGBACi008359
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 12:11:11 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6AFxuKv015878; Tue, 10 Jul 2007 11:59:56 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6AFxsaO015873;
	Tue, 10 Jul 2007 11:59:54 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-ID: <18067.44281.961490.928616@gargle.gargle.HOWL>
Date: Tue, 10 Jul 2007 11:59:53 -0400
From: James Carlson <james.d.carlson@sun.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
	<m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: ipv6@ietf.org
Subject: DoS or not? [was Re: Revisit: one remaining corner case in DAD]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / $B?@L@C#:H(B writes:
> (Intentionally separating the thread since this is irrelevant to the
> main focus of completing 2462bis)

Agreed; and changed the subject line as well.

> At Tue, 10 Jul 2007 07:43:34 -0400,
> James Carlson <james.d.carlson@sun.com> wrote:
> 
> > > On the other hand, I'd point out the same argument could apply to the
> > > "two-hour" rule adopted in RFC2462 and kept in 2462bis.  The consensus
> > > at that time (IIRC) was that even though we knew it's an on-link only
> > > attack the forced shut-down of an available global addresses was
> > > serious enough to mitigate within the protocol specification.  And
> > > since an unsolicited NA is a very rare event, I'd suspect it's more
> > > likely an attack than an actual duplicate that happens to have been
> > > undetected.
> > 
> > The two-hour rule has always struck me as more of a robustness issue
> > than anything else.
> 
> I'm not sure if you are indicating by "robustness" that it's not an
> issue of DoS, but the fact is that the two-hour rule was indeed
> introduced as a counter-measure of a DoS attack (I guess you knew
> that, but just in case...).

Understood; I just don't agree that effective DoS protection against
even a modestly determined attacker is possible, hence my reference to
"robustness" (being able to withstand transient and unintentional
errors) rather than "security" (defending against intentional
interference, such as denial of service).

> > The point I was making was that a denial of service attack against NDP
> > is not just feasible, but trivial, and that bringing up DoS as a
> > reason to ignore assumed-incorrect advertisements doesn't seem like a
> > productive way to frame the argument.
> 
> I admit whether discarding the NA may be a debatable behavior (with or
> without logging the event), but I don't think discussing this in the
> context of DoS, referring to the two-hour rule, is unproductive.  An
> attacker can easily make the Solaris node shut down an address by
> sending two attacking NAs.

Absolutely true, but I believe the claim to be irrelevant.

It's irrelevant because no matter *what* Solaris does it cannot stop
other nodes on the network from receiving and processing the incorrect
information offered by the attacker, and cannot prevent the attacker
from sending well-formed but incorrect messages in the first place.
Each time there's a solicitation, the attacker can generate an
incorrect advertisement.

If someone wants to attack NDP -- again, regardless of what Solaris or
any implementation chooses to do -- then he can in fact do so.  Such
an attack can and will cause disruption by poisoning neighbor cache
entries of peer systems.  Keeping the local address "up" even though
all of the neighbors are confused about the L2-to-L3 mapping does not
thwart the attack or help recover from it.  It just leaves the network
in an inconsistent (and potentially unusuable) state.

Thus, I claim that it's not productive to talk about the problem as an
issue of DoS, because DoS is just inherent in the protocol, so long as
there's no message authentication.

That leaves the issue of network stability.  For network stability,
it's best if there is _at most_ just one node that responds to
solicitations for any given IPv6 address.  If there's more than one,
then peers will inevitably end up with inconsistent entries, leading
to erratic and unpredictable behavior.

This is the reason that Solaris tears down interfaces that have
persistent conflicts.  There's nothing else useful, as best I can see,
that can be done.

>  The attacker can also mount the same
> attack on any other nodes in the link by first pinging them to collect
> the addresses and then performing the attack with the forged NAs.

Sure.

> We could still argue that such an attack is "trivial" and discussion
> based on the "trivial" attack is not productive.  But if so, we should
> also revisit the two hour rule, too.  As long as we keep that rule, it
> makes more sense to me to consider a counter measure for the same
> level of security threats.

As long as it leaves peer cache entries unaddressed, I don't think the
counter measure proposed here (simply ignoring the messages and
leaving the local IPv6 address "active") solves any problem related to
denial of service.  If anything, it actually makes the problem worse
when there are persistent conflicts, because instead of one node
making progress (and the others backing off and sulking), you end up
with nobody being able to use the address in any reliable way at all.

> To avoid wasting our time further, however..., I personally think this
> particular case isn't worth further debates.  As I repeatedly noted,
> we don't see unsolicited NAs very often in the first place, whether it
> would indicate a duplicate address or an attack.  We can safely leave
> it to implementations without a fear of disruption in practice.  So,
> I'll stop here on this matter until, someday, we need to discuss how
> to address undetected duplicates in general.

OK.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 10 12:48: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 1I8Ise-0000KP-26; Tue, 10 Jul 2007 12:48:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Isc-0000K3-Dr
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:48:02 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Isb-0002KP-Uu
	for ipv6@ietf.org; Tue, 10 Jul 2007 12:48:02 -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 89FBE7301F;
	Wed, 11 Jul 2007 01:48:00 +0900 (JST)
Date: Wed, 11 Jul 2007 01:47:58 +0900
Message-ID: <m2sl7wtdc1.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: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED7AB@xmb-rtp-20e.amer.cisco.com>
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
	<m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D035ED7AB@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.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 10 Jul 2007 12:03:01 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> The gist of your new paragraph is fine by me. However, you have un-fixed
> what I clearly defined in the past for behavior. The match statement has
> to apply to tentative address as well as an assigned address. Here is a
> suggestion for change in bullet 1:
> 
> 
>  1.  If the target address is tentative, the tentative address is not
>      unique.
> 
> changes to
> 
>  1.  If the target address matches a tentative address on the receiving
> interface, 
>      the tentative address is not unique.
> 
> There is a distinct case where the receiving interface gets an NA where
> target address in NA does not match any tentative address on the
> interface.

Sorry, I don't see the difference between these two, and since the
preceding sentence uses the word "match" only for assigned (not
tentative) addresses, the original text makes even more sense to me:

   On receipt of a valid Neighbor Advertisement message on an interface,
   node behavior depends on whether
   - the target address is tentative or
   - (the target address) matches a unicast or anycast address
     assigned to the interface: [...]

although I can also live with the suggested text of yours.

> Further, in an email you said:
> 
> You said:
> 
> "I intended, for example, that implementations should not affect their
> neighbor caches as a result of processing the NA "as described in
> [RFC4861=2461bis]".  I thought a naive implementation may be confused by
> the received NA and modify the link-layer address information of its own
> address (realized as a special type of neighbor cache)."
> 
> Even if a bad link-layer address gets into the ND cache of the receiving
> node, the  node have NUD kick in within 30-50 seconds and issue a mcast
> NS to resolve the destination IPv6 address that will result in the bad
> address to be replaced.

I'm not sure what you are going to suggest with this, but it doesn't
matter in any case if we agree on the "silent" version of the text.

					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 Jul 10 13: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 1I8J5Y-0004G7-IO; Tue, 10 Jul 2007 13:01:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8J5W-00049a-90
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:01:22 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8J58-0001xp-Qk
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:01:22 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id 22292B6077C
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 10:00:10 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 0C09629C004
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 10:00:10 -0700 (PDT)
X-AuditID: 11807123-a481fbb000000a55-9e-4693bb19bc02
Received: from [17.219.208.245] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id AE6C7304010
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 10:00:09 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Tue, 10 Jul 2007 10:00:08 -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: 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 Jul 10, 2007, at 04:38, Roger Jorgensen wrote:
> On Mon, 9 Jul 2007, james woodyatt wrote:
>> On Jul 3, 2007, at 13:23, Stephen Sprunk wrote:
>>> The only difference is that if there's a registry, the end-users  
>>> have someone to sue when a collision happens.
>>
>> This sounds like yet another reason to hate ULA-C.  Seriously.
>
> must be you American (I assume you are) that are so afraid of  
> someone being sued.I dont see that as a issue at all, we state a  
> purpose and disclaimer and if someone are stupied enough to sue for  
> collision, well they are darn stupid then. Sorry the language.
>
> anyway if a collision happen, someone have really screwed up  
> technical anyway and should be hung out for drying...

I'm sorry.  I'm just finding this whole debate rather surreal.

The purpose of ULA-C/G, as near as I can tell, is to mitigate the  
risk of an already vanishingly low probability collision-- with the  
consequence limited to forcing a network renumbering event, which is  
cheaper and easier with IPv6 than it already is with IPv4.

We expect nodes to be cycling through privacy addresses at a regular  
rate.  We expect them to have more than one address per interface,  
and often more than one interface.  We've already seen how to manage  
the problem of DNS and WHOIS and what-have-you with straight-up RFC  
4193 using synthetic records, but that doesn't seem to have attracted  
the interest of the ULA-C proponents.  Why not?

I'll take this opportunity to repeat myself: If a 1-in-2^40 chance of  
having to renumber a ULA network at every network merge event is  
totally unacceptable to you, then I have to wonder how you manage the  
risks associated with breathing the air in your office building.

And now, I'm seeing people suggest that having an opportunity to  
bring *litigation* against the ULA-C registry in the event of  
collision is supposed to be a *feature* and not a bug.  It makes me  
wonder if this is all some sort of elaborate prank.  Where's the  
hidden camera?  Nice one.  Very funny ha ha ha.  You can come out  
now.  I'm a good sport. No, really.


--
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 Jul 10 13: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 1I8JmJ-0001zR-Ic; Tue, 10 Jul 2007 13:45:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8JmH-0001yy-QG
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:45:33 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8JmH-0003tU-8n
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:45:33 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 10 Jul 2007 10:45:32 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAH1ik0arR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,523,1175497200"; 
	d="scan'208"; a="179665197:sNHT324177570"
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 l6AHjViM011771; 
	Tue, 10 Jul 2007 10:45:31 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6AHjUms017174;
	Tue, 10 Jul 2007 17:45:31 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, 10 Jul 2007 13:45:29 -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, 10 Jul 2007 13:45:28 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D035ED846@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2sl7wtdc1.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: AcfDEhZemoGxgE3rSve4Z82q0PCf+gAB2H/Q
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp>
	<m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com>
	<m2k5te7vq2.wl%jinmei@wide.ad.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com>
	<m2hcoi7s5p.wl%jinmei@wide.ad.jp> <468D22F9.7000700@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com>
	<468D3322.5080503@ericsson.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com>
	<468D58CD.6090204@hp.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com>
	<m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
	<18067.28902.308977.27946@gargle.gargle.HOWL>
	<m2tzscthhw.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D035ED7AB@xmb-rtp-20e.amer.cisco.com>
	<m2sl7wtdc1.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: 10 Jul 2007 17:45:29.0104 (UTC)
	FILETIME=[1AE3A100:01C7C31A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3158; t=1184089531;
	x=1184953531; c=relaxed/simple; s=sjdkim2002;
	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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20;
	bh=OeYI7TEKhYv4jwl4q3FHm5MGTR9DhyeK3I/W4yzFxYs=;
	b=DQS52FVd+8VWCtfhFG2rnlyzWd3hopRDtjErvQ3PAdx20ksMYenkXR3yyBHJ0k1Dim2QmZMb
	Ub4PmLLdS3T5QS3Ja6soA8HAlMJObtiS324yBIt+ZR7jQ0ezCtZkJN0I;
Authentication-Results: sj-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: ipv6@ietf.org, James Carlson <james.d.carlson@Sun.COM>
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

Thanks for the reply. As you say if you can live with my suggestion of
the change in bullet 1 that would be great - the previous text preceding
the bullets doesn't have to change. Or if you'd like previous sentence
to change too, it's your choice - I am not opposing anything there.

As for the other issue related to NUD clearing a bad address, it's not
at all related to the changing any text in 2461bis. I was only adding my
comments since the issue was being discussed.

When you get a chance, please send us the new text for section 5.4.4. of
2461bis.

Thanks.

Hemant=20

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Tuesday, July 10, 2007 12:48 PM
To: Hemant Singh (shemant)
Cc: James Carlson; ipv6@ietf.org
Subject: Re: Revisit: one remaining corner case in DAD

At Tue, 10 Jul 2007 12:03:01 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> The gist of your new paragraph is fine by me. However, you have=20
> un-fixed what I clearly defined in the past for behavior. The match=20
> statement has to apply to tentative address as well as an assigned=20
> address. Here is a suggestion for change in bullet 1:
>=20
>=20
>  1.  If the target address is tentative, the tentative address is not
>      unique.
>=20
> changes to
>=20
>  1.  If the target address matches a tentative address on the=20
> receiving interface,
>      the tentative address is not unique.
>=20
> There is a distinct case where the receiving interface gets an NA=20
> where target address in NA does not match any tentative address on the

> interface.

Sorry, I don't see the difference between these two, and since the
preceding sentence uses the word "match" only for assigned (not
tentative) addresses, the original text makes even more sense to me:

   On receipt of a valid Neighbor Advertisement message on an interface,
   node behavior depends on whether
   - the target address is tentative or
   - (the target address) matches a unicast or anycast address
     assigned to the interface: [...]

although I can also live with the suggested text of yours.

> Further, in an email you said:
>=20
> You said:
>=20
> "I intended, for example, that implementations should not affect their

> neighbor caches as a result of processing the NA "as described in=20
> [RFC4861=3D2461bis]".  I thought a naive implementation may be =
confused=20
> by the received NA and modify the link-layer address information of=20
> its own address (realized as a special type of neighbor cache)."
>=20
> Even if a bad link-layer address gets into the ND cache of the=20
> receiving node, the  node have NUD kick in within 30-50 seconds and=20
> issue a mcast NS to resolve the destination IPv6 address that will=20
> result in the bad address to be replaced.

I'm not sure what you are going to suggest with this, but it doesn't
matter in any case if we agree on the "silent" version of the text.

					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 Jul 10 13:57: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 1I8JxL-0001Hs-AI; Tue, 10 Jul 2007 13:56:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8JxJ-0001HM-7Y
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:56:57 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8JxJ-0005at-2N
	for ipv6@ietf.org; Tue, 10 Jul 2007 13:56:57 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 9B8E511459
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 17:56: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 "Tue, 10 Jul 2007 10:00:08 MST."
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com> 
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 10 Jul 2007 17:56:56 +0000
Message-ID: <22851.1184090216@sa.vix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
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: james woodyatt <jhw@apple.com>
> 
> I'm sorry.  I'm just finding this whole debate rather surreal.
> 
> The purpose of ULA-C/G, as near as I can tell, is to mitigate the  risk of
> an already vanishingly low probability collision--  ...

nope.

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



From ipv6-bounces@ietf.org Tue Jul 10 15:34: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 1I8LTR-0008Mn-Om; Tue, 10 Jul 2007 15:34:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8LTQ-0008MM-Gs
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:34:12 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net ([65.67.187.82]
	helo=defiant.dfw.nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8LTJ-00017i-7D
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:34:12 -0400
Received: from ssprunkxp (localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.13.8/8.13.8/Debian-3) with SMTP id
	l6AJXjt0003465; Tue, 10 Jul 2007 14:33:58 -0500
Message-ID: <01bf01c7c329$33b1bc30$4db8b60a@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.no>, "james woodyatt" <jhw@apple.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
Date: Tue, 10 Jul 2007 14:22:36 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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-Virus-Scanned: ClamAV 0.90.2/3626/Tue Jul 10 14:09:15 2007 on
	defiant.dfw.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Mon, 9 Jul 2007, james woodyatt wrote:
>> On Jul 3, 2007, at 13:23, Stephen Sprunk wrote:
>>> The only difference is that if there's a registry, the end-users
>>> have someone to sue when a collision happens.
>>
>> This sounds like yet another reason to hate ULA-C.  Seriously.
>
> must be you American (I assume you are) that are so afraid of
> someone being sued.  I dont see that as a issue at all,

You've apparently never been sued in an American court.  The central 
authority will go bankrupt defending themselves, win or lose.

> we state a purpose and disclaimer and if someone are
> stupied enough to sue for collision, well they are darn stupid
> then.

That won't work.  The claimed reason that ULA-L isn't good enough and that 
enterprises need ULA-C is because ULA-L provides no guarantee there'll never 
be a collision.  However, the odds of collision are higher with ULA-C.  That 
means these folks aren't interested in the odds of collision -- they're 
looking for someone to guarantee in writing that it won't happen.  Slap a 
disclaimer on it and they might as well just use ULA-L.

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 Tue Jul 10 15:35: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 1I8LUV-00042U-ED; Tue, 10 Jul 2007 15:35:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8LUT-00041j-IT
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:35:17 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net ([65.67.187.82]
	helo=defiant.dfw.nostrum.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8LUD-000841-VG
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:35:17 -0400
Received: from ssprunkxp (localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.13.8/8.13.8/Debian-3) with SMTP id
	l6AJXjsw003465; Tue, 10 Jul 2007 14:33:54 -0500
Message-ID: <01bb01c7c329$30c2d9a0$4db8b60a@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Mark Andrews" <Mark_Andrews@isc.org>
References: <200707090136.l691aGaW081091@drugs.dv.isc.org>
Date: Tue, 10 Jul 2007 13:56:30 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; 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-Virus-Scanned: ClamAV 0.90.2/3626/Tue Jul 10 14:09:15 2007 on
	defiant.dfw.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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

Thus spake "Mark Andrews" <Mark_Andrews@isc.org>
>> The alternative is to renumber the entire network every time a link goes 
>> up
>> or down.
>
> No. You don't have to renumber.  You just have to deprecate
> the addresses associated with the downed link.  This is the
> sort of thing routers should be able to do automatically.

Are the routers going to summon all the affected folks to a change control 
meeting, verify the approvals, do the necessary post-change testing, etc? 
Are they going to update all the firewall configs, DNS, etc?

Even the above automatic address deprecation part isn't available yet, 
despite a decade of folks claiming that renumbering is easy, and that's not 
even the hard part.

>> Most of the operational and innovation costs of NAT are also present with 
>> a
>> stateful firewall, which any sane organization will be using, because 
>> it's
>> really the stateful inspection that burns you.
>
> NAT introduces costs above and beyond those of a stateful firewall.

That's like saying having a broken leg is an additional cost above and 
beyond the cost of death.  Not breaking your leg doesn't make you any less 
dead.

> And as for stateful firewalls, applications should be able to
> talk to them to open up reply traffic if needed.

Yeah, try to sell that to any enterprise security department.  It's the 
applications and users that security folks are trying to protect their 
networks from in the first place, and internal users are a much, much bigger 
threat to security than external folks are.

>> Again, RFC 4192 ignores all of the non-technical aspects of renumbering.
>> That's probably appropriate, given the IETF's domain, but it's only a 
>> tiny
>> part of what must be done.  Changing the address on an interface takes
>> a few seconds; the change control processes leading up to it can burn
>> months of manpower.
>
> Real renumbering events are rare.

That all depends what you call "real".  Any event that breaks connectivity 
(including established connections) for more than a few seconds is "real" to 
me.

> You are wanting NAT to provide multi-homing support.  This does not
> require you to renumber.  There is no need to use NAT for this with IPv6.
> IPv6 provides the mechanisms to move the source address selection
> back to the end host (where it belongs).

For the record, I hate NAT, for all the reasons that most of IETFers do. 
What I'm saying is that NAT is considered by the market to be less evil than 
the alternatives the IETF has proposed to date.  Until folks recognize that, 
no progress will be made.

I'd much prefer to see widespread use of PI space, and significant effort 
put into an id/loc split scheme so that the DFZ doesn't implode as a result. 
OTOH, router vendors are claiming the ability to support two million routes 
today and ten million in a few years, so we have time to work on that.

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 Tue Jul 10 15:35: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 1I8LUZ-0004JF-UX; Tue, 10 Jul 2007 15:35:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8LUV-00043Y-QI
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:35:19 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net ([65.67.187.82]
	helo=defiant.dfw.nostrum.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8LUG-000845-A2
	for ipv6@ietf.org; Tue, 10 Jul 2007 15:35:19 -0400
Received: from ssprunkxp (localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.13.8/8.13.8/Debian-3) with SMTP id
	l6AJXjsx003465; Tue, 10 Jul 2007 14:33:56 -0500
Message-ID: <01be01c7c329$31f406a0$4db8b60a@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Per Heldal" <heldal@eml.cc>
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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
	<1184062438.14166.63.camel@localhost.localdomain>
Date: Tue, 10 Jul 2007 14:11:27 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; 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-Virus-Scanned: ClamAV 0.90.2/3626/Tue Jul 10 14:09:15 2007 on
	defiant.dfw.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
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

Thus spake "Per Heldal" <heldal@eml.cc>
> On Mon, 2007-07-09 at 10:05 -0500, Stephen Sprunk wrote:
>> > * ULA-C/G are NOT ment to be used on internet
>>
>> OTOH, there's no way for the IETF or RIRs to stop it from happening.  I'm
>> not saying it will, but it is irresponsible to claim it won't when 
>> there's
>> no mechanism to enforce that.
>
> <sarcasm>
> What is the mechanism to force operators to carry ULA prefixes?
> </sarcasm>

Money.

Sooner or later, we're going to run out of IPv4 space.  Let's say Ebay 
hadn't been able to get their PIv6 /41.  The only other viable way they'd be 
able to reach all of the new IPv6-only eyeballs is to use ULA-C/G addresses. 
The only way ISPs would be able to give their eyeballs access to that 
content is by accepting that route.  Voila, ULA-C/G becomes the de facto PI 
space.

Note that this scenario is one of several that caused ARIN to pass its PIv6 
policy last year.

> Until such mechanisms are in place ULA-prefixes are likely to be
> rejected by the majority of transit operators. ULA-blocks split in their
> individual /48s (due to incompetence, accident or malice) won't fit in
> any current or near-future routing hardware nor is there a reliable
> mechanism to manage exceptions on a mass-scale.

Routers in the DFZ are limited by the number of slots available, not by the 
length of the prefixes.  Routers don't care whether they've got a million 
/32s or half a million /32s and half a million /48s.

PI /48s do work just fine in the DFZ.  There's no reason why ULA-C/G(/L) 
/48s wouldn't work just as well.  As Jeroen showed, some ISPs can't even be 
bothered to filter 10/8 from the DFZ and that doesn't even do anything 
useful due to collisions.  Why are we expecting they'll filter ULA space 
much better, or even at all -- just because the IETF asked nicely?

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 Tue Jul 10 17:18: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 1I8N65-0005Wk-6M; Tue, 10 Jul 2007 17:18:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8N63-0005Sq-BT
	for ipv6@ietf.org; Tue, 10 Jul 2007 17:18:11 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8N62-000663-RX
	for ipv6@ietf.org; Tue, 10 Jul 2007 17:18:11 -0400
Received: from ([10.160.67.162])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.151462009;
	Tue, 10 Jul 2007 17:23:07 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K05.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 10 Jul 2007 17:17:14 -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: Tue, 10 Jul 2007 17:17:13 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A0272F96B@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why ULA-* will not harm the DFZ
Thread-Index: AcfCmbj55E62hBn2QbWL7HWhYL9PHQAmCPMw
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: "Joe Abley" <jabley@ca.afilias.info>, "IPv6 WG" <ipv6@ietf.org>,
	<ppml@arin.net>
X-OriginalArrivalTime: 10 Jul 2007 21:17:14.0138 (UTC)
	FILETIME=[AFADF7A0:01C7C337]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 
Subject: RE: Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thank you Joe.  That is where my thoughts went with all of it and its =
nice to see it written out line by line.

There is just one point that needs to be considered as well, and that is =
what next?  While I believe ULA-Central should be used for private VPNs =
or internal infrastructure, I also ask everyone to consider the =
following:

1. Either designate space FC00::/8 as ULA-central and finish the =
documentation and processes needed (which their is a draft in front of =
IETF right now).=20
2. Or release space FC00::/8 for another type of use (becuase sitting on =
the shelf is wasteful)
3. Or maybe double the size of statistically unique ULA.

Ok. Those are my thoughts.  Fire at will.
Marla Azinger
Frontier Communications


-----Original Message-----
From: Joe Abley [mailto:jabley@ca.afilias.info]
Sent: Monday, July 09, 2007 7:25 PM
To: IPv6 WG
Subject: Why ULA-* will not harm the DFZ


The risk to the DFZ of leaking ULA-* {routes, packets, whatever} =20
keeps coming up on this list. I thought I'd try to address just that =20
problem in isolation, just to see whether I'm hearing things right. =20
Please attack the following.

1. With PI address space there is an expectation of global utility =20
(or, reachability across the DFZ, or however you want to describe =20
"useful on the Internet"). I said expectation, not guarantee.

2. With ULA-* address space there would be no expectation of global =20
utility. In fact, there would be an expectation that the addresses =20
are for local use only (for some definition of "local").

3. There is doubt that any ULA-* address space would be kept properly =20
local in all cases. In fact, there is an expectation that {routes, =20
packets, something} would leak.

4. If some leaks are tolerated, then maybe, eventually, all leaks =20
will be tolerated. Let's assume that will happen, just to see where =20
it takes us.

5. If everybody has non-PA addresses (be they PI or ULA-*) and they =20
are all leaked to the Internet, then the DFZ will suffer state =20
explosion.

6. If operators can distinguish between should-be-local addresses =20
(ULA-*) and allowed-to-be-global addresses (PI) in ASICs then =20
operators can filter in order to head off the cataclysm looming in (5).

7. Since people were told up-front that their ULA-* addresses were no =20
good for use on the Internet, step (6) shouldn't cause anybody to =20
lock and load their lawyers.

(6) and (7) above ring true for ULA-* but not for PI-for-all. So, ULA-=20
* would not harm the DFZ in the way that PI-for-all might harm the DFZ.


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 Tue Jul 10 17: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 1I8NY5-00087x-TP; Tue, 10 Jul 2007 17:47:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8NY4-00087s-Bp
	for ipv6@ietf.org; Tue, 10 Jul 2007 17:47:08 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8NXz-0005HP-Tq
	for ipv6@ietf.org; Tue, 10 Jul 2007 17:47:08 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 10 Jul 2007 22:47:02 +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, 10 Jul 2007 22:48:35 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2A5E@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <454810F09B5AA04E9D78D13A5C39028A0272F96B@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Why ULA-* will not harm the DFZ
Thread-Index: AcfCmbj55E62hBn2QbWL7HWhYL9PHQAmCPMwAAJzLpA=
References: <454810F09B5AA04E9D78D13A5C39028A0272F96B@nyrofcs2ke2k01.corp.pvt>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Jul 2007 21:47:03.0000 (UTC)
	FILETIME=[D9ECA580:01C7C33B]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: RE: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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. Or release space FC00::/8 for another type of use (becuase=20
> sitting on the shelf is wasteful)

This is a good example of ossified IPv4 thinking. IPv6 is different from
IPv4. It is not just IPv4 with more address bits. It is not wasteful to
leave IPv6 address ranges sitting on the shelf any more than it is
wasteful to assign a /48 prefix to a homeowner.

--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 Jul 10 18:00: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 1I8NlA-00046U-SQ; Tue, 10 Jul 2007 18:00:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Nl8-00046C-Hs
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:00:38 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Nl4-0005bP-7j
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:00:38 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.151464605;
	Tue, 10 Jul 2007 18:06:13 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Tue, 10 Jul 2007 18:00:19 -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: Tue, 10 Jul 2007 18:00:18 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A023EFBEF@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Why ULA-* will not harm the DFZ
Thread-Index: AcfCmbj55E62hBn2QbWL7HWhYL9PHQAmCPMwAAJzLpAAAIEKoA==
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: <michael.dillon@bt.com>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 10 Jul 2007 22:00:19.0200 (UTC)
	FILETIME=[B47F2000:01C7C33D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: RE: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 dont agree.

Marla Azinger

-----Original Message-----
From: michael.dillon@bt.com [mailto:michael.dillon@bt.com]
Sent: Tuesday, July 10, 2007 2:49 PM
To: ipv6@ietf.org
Subject: RE: [ppml] Why ULA-* will not harm the DFZ


> 2. Or release space FC00::/8 for another type of use (becuase=20
> sitting on the shelf is wasteful)

This is a good example of ossified IPv4 thinking. IPv6 is different from
IPv4. It is not just IPv4 with more address bits. It is not wasteful to
leave IPv6 address ranges sitting on the shelf any more than it is
wasteful to assign a /48 prefix to a homeowner.

--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 Jul 10 18:15: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 1I8Nzn-00031b-4Q; Tue, 10 Jul 2007 18:15:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Nzk-0002vj-NI
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:15:44 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Nzg-0005wF-D4
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:15:44 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out3.apple.com (Postfix) with ESMTP id C148EB675FB
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 15:15:39 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id ABE5429C002
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 15:15:39 -0700 (PDT)
X-AuditID: 11807123-a5020bb000000a55-42-4694050b2b28
Received: from [17.206.50.117] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 9BFE030400C
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 15:15:39 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <22851.1184090216@sa.vix.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Tue, 10 Jul 2007 15:15:39 -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: 8b30eb7682a596edff707698f4a80f7d
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 Jul 10, 2007, at 10:56, Paul Vixie wrote:
> [I wrote:]
>>
>> The purpose of ULA-C/G, as near as I can tell, is to mitigate the   
>> risk of
>> an already vanishingly low probability collision--  ...
>
> nope.

Hmmm.  I guess the alternative is that the purpose of ULA-C/G is to  
mitigate the risk of collision when merging on the order of hundreds  
of thousands of ULA networks in one routing realm... sort of like  
creating a "local DFZ" of a sort.

Forgive me, but that sounds even more surreal.  It's tough for me to  
imagine how a real organization doing that could fail to qualify for  
a PI allocation, or why such an organization would find it  
unacceptable to have to use a PI allocation without advertising it to  
the public DFZ.  Likewise, it's tough to imagine how an organization  
that doesn't qualify for a PI allocation could be merging enough ULA  
networks together that the risk of collision rises to a level of any  
real significance.

Okay.  Maybe the problem with PI allocations for this purpose is that  
organizations doing all this network merging, i.e. extraordinarily  
paranoid organizations, e.g. the Communist Party, want some kind of  
assurance from the operators of the public Internet that their  
hundreds of thousands of local networks aren't directly reachable  
from the public DFZ in the event a local NOC configures a border  
router improperly.  Obviously, ULA-C can do that better than PI.

Is that the big driving factor here?


--
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 Jul 10 18:30: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 1I8ODf-0005R2-9I; Tue, 10 Jul 2007 18:30:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8ODd-0005Qx-Uz
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:30:06 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8ODd-0008Uk-BH
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:30:05 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 10 Jul 2007 15:30:04 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAJKkk0arR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,523,1175497200"; 
	d="scan'208"; a="501824740:sNHT146029384"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6AMU4RQ003181; 
	Tue, 10 Jul 2007 15:30:04 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6AMTcXl022372;
	Tue, 10 Jul 2007 22:30:03 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, 10 Jul 2007 18:30:01 -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, 10 Jul 2007 18:30:00 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D035EDA35@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Revisit: one remaining corner case in DAD
Thread-Index: AcfCzcwt+COG3rGzRRCSUPr15TZXKQAMXK8g
References: <y7vhd6h3p3p.wl%jinmei@isl.rdc.toshiba.co.jp><m1sl84mvnf.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D0358A10F@xmb-rtp-20e.amer.cisco.com><m2k5te7vq2.wl%jinmei@wide.ad.jp><B00EDD615E3C5344B0FFCBA910CF7E1D0358A148@xmb-rtp-20e.amer.cisco.com><m2hcoi7s5p.wl%jinmei@wide.ad.jp>
	<468D22F9.7000700@ericsson.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A225@xmb-rtp-20e.amer.cisco.com><468D3322.5080503@ericsson.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A255@xmb-rtp-20e.amer.cisco.com><468D58CD.6090204@hp.com><B00EDD615E3C5344B0FFCBA910CF7E1D0358A336@xmb-rtp-20e.amer.cisco.com><m1odiqkpvf.wl%jinmei@isl.rdc.toshiba.co.jp><18066.38103.530393.802199@gargle.gargle.HOWL>
	<m1tzsclkl4.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>, "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>
X-OriginalArrivalTime: 10 Jul 2007 22:30:01.0965 (UTC)
	FILETIME=[DB1B79D0:01C7C341]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5640; t=1184106604;
	x=1184970604; c=relaxed/simple; s=sjdkim2002;
	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=20Revisit=3A=20one=20remaining=20corner=20case=20in=20D
	AD |Sender:=20;
	bh=bf7UTMFC0y8N/PqmcSEm5LwdqmSL4dORT/XTbAgwmR0=;
	b=IE+atcZNgVXO/LqitEDz0vp6kTA48QOLfW3IEWCGB6AT0k0Cbr7soeyMCRESZp+Nh4GPa3SF
	ZPMHnqxi5sVVT+cGWp7VRxXlaiW8WO9Lwi+x98qUnMpoWEDWP7QY7RUn;
Authentication-Results: sj-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: 
Subject: RE: Revisit: one remaining corner case in DAD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

I have a minor process question. If yesterday we were told, we have 12
hours left to close on 2462bis, I believe those 12 hours have expired.
So why are you suggesting another revised proposal? Can we take it now
that you have another x number of hours left to make any changes to
2462bis? I am just trying to understand as a newbie how does IETF I-D
editing timeline works when I-D's are in AUTH48 state. Seems like the 12
hour timeline is flexible for a showstopper editorial change?

Thanks.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Tuesday, July 10, 2007 4:39 AM
To: James Carlson
Cc: Vlad Yasevich; ipv6@ietf.org; Suresh Krishnan
Subject: Re: Revisit: one remaining corner case in DAD

At Mon, 9 Jul 2007 16:04:39 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> I disagree a bit with this resolution.  These sorts of undetected=20
> duplicate addresses do happen in practice, due to network partition/=20
> repair and the effect of things like Spanning Tree's default port=20
> blocking.
>=20
> As a result, what I've done in the Solaris implementation is to=20
> 'defend' the address once -- by sending out my own advertisement in=20
> reply to the received one -- but setting a flag.  If I see another=20
> duplicate advertisement within some period of time (~10), then shut=20
> the address down.

I'm not sure if we are talking about the same thing, so please let me
check.  Are you saying "if a Solaris node happens to receive an NA
targeting an address assigned on the receiving interface, the node will
'respond' to the NA with another NA (probably sent to ff02::1) targeting
the same address"?

In any case, I'd not disagree with trying to handle an address duplicate
that has not been detected in the initial DAD as a general topic.  But
I'd say it's basically beyond the scope of 2462bis.  In fact, 2462(bis)
simply admits DAD is not completely reliable (in section 5.4) and
doesn't specify any behavior to improve the reliability.  Note also that
this particular case (receiving an NA targeting one of the receiver's
own addresses) is a very minor case among such undetected duplicates
since an unsolicited NA is sent only in very limited cases; if we were
to do that within this spec, we'd have to cover more likely scenarios
such as receiving an RA with the source address equal to a link-local
address of the receiving interface.  (But I don't think we wanted to
address such cases in the 2462bis revision)

What we've actually been discussing in this thread is how to fix a clear
error in the 2462bis (and RFC2462/1971) text: it talked about "how to
handle a *solicitation*" in the "Receiving Neighbor Advertisement"
section.  It was an unfortunate side effect that we hit the minor, yet
pretty substantial, issue of undetected duplicates while trying to
resolve the seemingly editorial error.

So, in this particular context, I'd like to focus on solving the obvious
error within the scope of 2462bis; I don't want to go into the possibly
controversial discussion of how to deal with undetected duplicates in
this context.  Another revised proposal based on this view is as
follows.  How about that?

   On receipt of a valid Neighbor Advertisement message on an interface,
   node behavior depends on whether the target address is tentative or
   matches a unicast or anycast address assigned to the interface:

   1.  If the target address is tentative, the tentative address is not
       unique.

   2.  If the target address matches a unicast address assigned to the
       receiving interface, it would possibly indicate that the
       address is a duplicate but it has not been detected by the
       Duplicate Address Detection procedure (recall that Duplicate
       Address Detection is not completely reliable).  How to handle
       such a case is beyond the scope of this document, but care
       should be taken so that the advertisement will not affect the
       normal Neighbor Discovery [RFC4861] processing.

   3.  Otherwise, the advertisement is processed as described in
       [RFC4861].

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

p.s. one additional comment that is irrelevant to the original issue of
this topic:

>   - The DoS issue is a red herring.  NDP doesn't have security, and
>     attackers can forge up bad advertisements any time they want.
>     It's not a matter of "shutting down" the address -- confusing the
>     peers on the network is sufficient to disrupt normal operation,
>     and there's just no way to stop that.

On one hand, I agree; (pure) NDP is inherently vulnerable to on-local
attacks, so it may not really be reasonable to take account of local
attacks in the protocol design too much.

On the other hand, I'd point out the same argument could apply to the
"two-hour" rule adopted in RFC2462 and kept in 2462bis.  The consensus
at that time (IIRC) was that even though we knew it's an on-link only
attack the forced shut-down of an available global addresses was serious
enough to mitigate within the protocol specification.  And since an
unsolicited NA is a very rare event, I'd suspect it's more likely an
attack than an actual duplicate that happens to have been undetected.

--------------------------------------------------------------------
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 Jul 10 18:34: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 1I8OID-00047L-Fk; Tue, 10 Jul 2007 18:34:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8OIB-0003yC-Vg
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:34:48 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8OHw-00008T-N1
	for ipv6@ietf.org; Tue, 10 Jul 2007 18:34:47 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85933412; Tue, 10 Jul 2007 18:33:59 -0400
Message-ID: <46940949.2010908@internap.com>
Date: Tue, 10 Jul 2007 15:33:45 -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: <200706251556.l5PFu6Qa057410@mail.reprise.com>	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
In-Reply-To: <B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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]
>>>
>>> The purpose of ULA-C/G, as near as I can tell, is to mitigate the  
>>> risk of
>>> an already vanishingly low probability collision--  ...
>> [Paul Vixie]
>> nope.
> [james woodyatt]
> Hmmm.  I guess the alternative is that the purpose of ULA-C/G is to 
> mitigate the risk of collision when merging on the order of hundreds 
> of thousands of ULA networks in one routing realm... sort of like 
> creating a "local DFZ" of a sort.
>
> Forgive me, but that sounds even more surreal.  It's tough for me to 
> imagine how a real organization doing that could fail to qualify for a 
> PI allocation, or why such an organization would find it unacceptable 
> to have to use a PI allocation without advertising it to the public 
> DFZ.  Likewise, it's tough to imagine how an organization that doesn't 
> qualify for a PI allocation could be merging enough ULA networks 
> together that the risk of collision rises to a level of any real 
> significance.

Perhaps you haven't read or understood what I've written previously.  
The purpose of ULA-G is to allow RIRs to allocate private address space 
in a non-discriminatory manner to organizations who wish to use it 
outside of the DFZ. 

As stated previously, the rules for getting PI space are based on the 
expectation that PI blocks can be announced into the DFZ.  The proposed 
rules for ULA-G space are based on the expectation that ULA-G blocks 
will not be announced into the DFZ, and that they will be allocated out 
of a single global netblock, identified in an RFC, that everyone knows 
can and should be filtered.  As stated quite clearly by Joe Abley in the 
"Why ULA-* will not harm the DFZ" thread, that difference in 
expectation, and ease in filtering when desired or necessary, makes it 
possible to give out ULA-G space in a non-discriminatory manner (which 
is simply not prudent for 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 Tue Jul 10 19:06: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 1I8Omp-00072b-PV; Tue, 10 Jul 2007 19:06:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Omn-00072S-89
	for ipv6@ietf.org; Tue, 10 Jul 2007 19:06:25 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8OmX-0000l3-UC
	for ipv6@ietf.org; Tue, 10 Jul 2007 19:06:25 -0400
Received: from compute2.internal (compute2.internal [10.202.2.42])
	by out1.messagingengine.com (Postfix) with ESMTP id A38E765DF;
	Tue, 10 Jul 2007 19:05:45 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute2.internal (MEProxy); Tue, 10 Jul 2007 19:05:45 -0400
X-Sasl-enc: 5EVkW8JDZbQBTwsas+uGfzafsFUgcqWZJPkSRl4Yxp6I 1184108740
Received: from [127.0.0.1] (p54B416C5.dip0.t-ipconnect.de [84.180.22.197])
	by mail.messagingengine.com (Postfix) with ESMTP id 0D3BF55E9;
	Tue, 10 Jul 2007 19:05:32 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <01be01c7c329$31f406a0$4db8b60a@atlanta.polycom.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>
	<061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com>
	<469218B7.8060108@cisco.com>
	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
	<1184062438.14166.63.camel@localhost.localdomain>
	<01be01c7c329$31f406a0$4db8b60a@atlanta.polycom.com>
Content-Type: text/plain
Date: Wed, 11 Jul 2007 01:04:42 +0200
Message-Id: <1184108682.14166.146.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: d185fa790257f526fedfd5d01ed9c976
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 Tue, 2007-07-10 at 14:11 -0500, Stephen Sprunk wrote:
> Thus spake "Per Heldal" <heldal@eml.cc>
> > On Mon, 2007-07-09 at 10:05 -0500, Stephen Sprunk wrote:
> >> > * ULA-C/G are NOT ment to be used on internet
> >>
> >> OTOH, there's no way for the IETF or RIRs to stop it from happening.  I'm
> >> not saying it will, but it is irresponsible to claim it won't when 
> >> there's
> >> no mechanism to enforce that.
> >
> > <sarcasm>
> > What is the mechanism to force operators to carry ULA prefixes?
> > </sarcasm>
> 
> Money.
> 
> Sooner or later, we're going to run out of IPv4 space.  Let's say Ebay 
> hadn't been able to get their PIv6 /41.  The only other viable way they'd be 
> able to reach all of the new IPv6-only eyeballs is to use ULA-C/G addresses. 
> The only way ISPs would be able to give their eyeballs access to that 
> content is by accepting that route.  Voila, ULA-C/G becomes the de facto PI 
> space.
> 
> Note that this scenario is one of several that caused ARIN to pass its PIv6 
> policy last year.
> 

My understanding was that the dominating argument supporting PI-policies
was simply to match the capability of ipv4 ... bummer. Even back then I
thought the randomness implied with ULA would make it useless for this
purpose.

> > Until such mechanisms are in place ULA-prefixes are likely to be
> > rejected by the majority of transit operators. ULA-blocks split in their
> > individual /48s (due to incompetence, accident or malice) won't fit in
> > any current or near-future routing hardware nor is there a reliable
> > mechanism to manage exceptions on a mass-scale.
> 
> Routers in the DFZ are limited by the number of slots available, not by the 
> length of the prefixes.  Routers don't care whether they've got a million 
> /32s or half a million /32s and half a million /48s.
> 

Since when did anyone argue that pfxlen affects the size of a fib-entry?

> PI /48s do work just fine in the DFZ.  There's no reason why ULA-C/G(/L) 
> /48s wouldn't work just as well.  As Jeroen showed, some ISPs can't even be 
> bothered to filter 10/8 from the DFZ and that doesn't even do anything 
> useful due to collisions.  Why are we expecting they'll filter ULA space 
> much better, or even at all -- just because the IETF asked nicely?
> 

I'd expect operators to implement relatively aggressive schemes for
prefix-filtering for ipv6 in their own interest to secure an environment
with stable services for their customers. 

FC00::/8 represent 2^40 /48s. With registries handing out unique
prefixes using a random algorithm to choose from the available pool how
do you pick which ones to make exceptions for and still prevent abuse?
The number of exceptions it is possible to handle will eventually be
limited by known factors such as storage for configuration and
route-filter processing capabilities.

Compare that to PI /48s (or even PA /32s) allocated _sequentially_ from
an address-block as recommended by the RIR-community. With allocations
made from a huge block your prefix filters don't need to allow more than
a fraction of that block initially. Maybe it's enough to accept the bit
that is actually used + x% for growth in the immediate future and then
add procedures for frequent updates.

To achieve operational stability it is necessary to make sure the
potential max no of prefixes given maximum fragmentation (within limits
given by RIR-policies) of currently allocated address-space doesn't
exceed the capacity of DFZ hardware, while even leaving space for TE and
local routing. General acceptance of random /48s out of a /8 doesn't fit
well in that picture and it makes ULA-C very different from PI from the
backbone operator perspective. 


//per


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



From ipv6-bounces@ietf.org Tue Jul 10 19:33: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 1I8PD1-0008C2-Ob; Tue, 10 Jul 2007 19:33:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8PD0-0008Bw-Bs
	for ipv6@ietf.org; Tue, 10 Jul 2007 19:33:30 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8PD0-0001AI-1k
	for ipv6@ietf.org; Tue, 10 Jul 2007 19:33:30 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85936736; Tue, 10 Jul 2007 19:33:13 -0400
Message-ID: <46941729.4090509@internap.com>
Date: Tue, 10 Jul 2007 16:32:57 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Stephen Sprunk <stephen@sprunk.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><061e01c7bda7$be9e6c30$543816ac@atlanta.polycom.com><469218B7.8060108@cisco.com>	<Pine.LNX.4.64.0707091323460.9923@chandra.student.uit.no>
	<012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
In-Reply-To: <012701c7c23a$a8b95b40$4f3816ac@atlanta.polycom.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ipv6@ietf.org, Eliot Lear <lear@cisco.com>
Subject: The problem with PA, PI and ULA-L
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Stephen Sprunk wrote:
>
> If you start with the solution, one can always find problems that it 
> solves. However, if you start with a defined problem, the solution may 
> not be what you expect.  Every example you've given so far is solved 
> at least as well by PI space as by ULA space, and in some cases better 
> by PI.

Stephen makes a good point, so maybe I'll try defining what I see as the 
problem space here.  First, I'll outline the current forms of IPv6 
addresses and some of their characteristics:

    * Provider Assigned or Provider Aggregatable (PA) addresses are
      assigned by IPv6 transit providers to their customers.  These
      addresses are *readily available* to pretty much any sized
      network,  and *globally registered* (can be looked up via WHOIS
      and DNS), but are *temporary* (assigned roughly for the duration
      of the contract with the provider).  Because these addresses come
      out of a provider aggregate, they are covered by an aggregate
      route (usually a /32), ensuring that they are *globally routable*
      (in the DFZ).
    * Provider Independent (PI) addresses are assigned by a Regional
      Internet Registry (RIR) directly to end user organizations,
      usually as /48's.  Recipients of such addresses expect to be able
      to announce their /48 to their transit providers, and expect that
      announcement to be accepted by most/all other networks providing
      Internet transit service to ensure they are *globally routable*. 
      Because of this expectation, the rules for getting IPv6 PI space
      require an organization to be running a network of several hundred
      machines and multihomed with BGP to two or more transit
      providers.  As a result, PI addresses are *not readily available*
      to all networks, but because they are not limited to the duration
      of a contract with a transit provider, they are more or less
      *permanent*.  As with PA addresses, they are *globally registered*.
    * Locally assigned Unique Local Addresses (ULA-L) are *not globally
      routable* and *not globally registered*, because they are randomly
      assigned and used by an organization.  They are extremely *readily
      available*, and *permanent* (except in the rare case of a
      collision, which is more likely to be caused by failure to follow
      the recommended assignment algorithm than by random chance).


To put it another way, here are the four pairs of characteristics, and 
the list of which kinds of space fall into each:

Readily available:        PA and ULA-L
Not readily available:    PI

Globally registered:      PA and PI
Not globally registered:  ULA-L

Globally routable:        PA and PI
Not globally routable:    ULA-L

Permanent:                PI and ULA-L
Temporary:                PA


Now an ideal new type of IP space would be *readily available*, 
*globally registered*, *globally routable*, and *permanent*.  However, 
due to the current routing architecture of the Internet, no such 
solution currently exists.  Therefore, the next best thing would be to 
have three types of IP space that each met three of the four desired 
characteristics.  (I leave out the possibility of having globally 
routable space that is not also globally registered.)  We have two of 
the three already: PA space is *readily available*, *globally 
registered*, and *globally routable*, and PI space is *globally 
registered*, *globally routable*, and *permanent*.  However, we don't 
have any sort of space that is *readily available*, *globally 
registered*, and *permanent*, because ULA-L is *not globally registered*.

As concisely stated by Paul Vixie, "ad-hoc local networking depends on 
the same global framework as public networking, for example, in-addr 
services, RPKI, and whois."  I would add that there are numerous other 
forms of private networking and internetworking that also depend on 
those services.

So, that's the problem statement: we need IPv6 addresses that are 
readily available to all applicants without discrimination, permanently 
assigned as long as the recipient continues to need the space, and that 
come with the kind of in-addr, whois, and possibly RPKI services 
provided by global registration.  I can think of at least three ways to 
solve that problem, but I'll save that for another message.

-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 Jul 10 20:08: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 1I8Pks-0005GL-19; Tue, 10 Jul 2007 20:08:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Pkp-0005GG-WF
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:08:28 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8Pka-0001hp-MK
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:08:27 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id 3E44AB697EB
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 17:07:40 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 2B5E410187
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 17:07:40 -0700 (PDT)
X-AuditID: 11807124-a24e1bb0000007e2-0a-46941f4cd6cb
Received: from [17.206.50.117] (int-si-a.apple.com [17.128.113.41])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 10722100FB
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 17:07:40 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46940949.2010908@internap.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<46940949.2010908@internap.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Tue, 10 Jul 2007 17:07:38 -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: 244a2fd369eaf00ce6820a760a3de2e8
Subject: Re: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 10, 2007, at 15:33, Scott Leibrand wrote:
>
> [...]
> As stated previously, the rules for getting PI space are based on  
> the expectation that PI blocks can be announced into the DFZ.  The  
> proposed rules for ULA-G space are based on the expectation that  
> ULA-G blocks will not be announced into the DFZ, and that they will  
> be allocated out of a single global netblock, identified in an RFC,  
> that everyone knows can and should be filtered.  As stated quite  
> clearly by Joe Abley in the "Why ULA-* will not harm the DFZ"  
> thread, that difference in expectation, and ease in filtering when  
> desired or necessary, makes it possible to give out ULA-G space in  
> a non-discriminatory manner (which is simply not prudent for PI  
> space today).

Look, if we want to enable the operation of "very large local DFZ"  
routing realms (in the hundreds of thousands or millions of networks)  
and we're really, really concerned about accidental leakage of local  
prefixes into the DFZ with PI addressing, then I can understand the  
motivation for ULA-G/C.  Is that really what this is all about?  If  
so, then I'd like to see the Introduction revised accordingly.

Here is some proposed text, which I think improves the draft and  
makes it clear what we are intending to do:

>> This document defines the characteristics and technical allocation  
>> requirements for centrally-assigned Unique Local IPv6 addresses,  
>> as defined in [ULA].  They are not expected to be routed in the  
>> default-free zone of the public Internet.  They are intended for  
>> use in pre-arranged interconnection between organizations and  
>> sites in very large local routing realms.
>>
>> All Unique Local IPv6 addresses, as defined in [ULA], have the  
>> following characteristics:
>>
>>   - Globally unique prefix.
>>   - Well known prefix to allow for easy filtering at site
>>     boundaries.
>>   - Internet Service Provider independent and can be used for
>>     communications inside of a site without having any permanent or
>>     intermittent Internet connectivity.
>>   - In practice, applications may treat these addresses like global
>>     scoped addresses.
>>
>> The most important property of ULAs is that they are unique, as  
>> ULA uniqueness allows routing realms to be merged or privately  
>> interconnected with minimal risk of prefix collisions.  The  
>> statistical uniqueness of locally-assigned ULAs is deemed adequate  
>> when routing realms contain a small number of local prefixes, but  
>> insufficient in the case where routing realms routinely comprise  
>> hundreds of thousands or even millions of networks.  A single,  
>> global federated registry for assigning unique local prefixes is  
>> required to address these concerns.  Using ULAs for this purpose  
>> instead of Provider Independent [RIR-PI] addresses has the  
>> attraction of making it easy to prevent leakage of local prefixes  
>> into the default-free zone of the public Internet, thereby  
>> enforcing the requirement to pre-arrange interconnections.


--
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 Jul 10 20:22: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 1I8PyQ-0005W9-Av; Tue, 10 Jul 2007 20:22:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8PyP-0005Vv-Cu
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:22:29 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8PyO-0008Ks-4e
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:22:29 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id A4D371146F
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 00:22:27 +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, 10 Jul 2007 15:15:39 MST."
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com> 
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 11 Jul 2007 00:22:27 +0000
Message-ID: <83714.1184113347@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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

> > nope.
> 
> Hmmm.  I guess the alternative is that the purpose of ULA-C/G is to mitigate
> the risk of collision when merging on the order of hundreds of thousands of
> ULA networks in one routing realm... sort of like creating a "local DFZ" of
> a sort.
> 
> Forgive me, but that sounds even more surreal.  ...

if you're going to cons up a potential interpretation without knowing the
real answer, can you at least cons up one that makes sense to you?

> Is that the big driving factor here?

scott@internap has done a fine job of explaining that, today, again.

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



From ipv6-bounces@ietf.org Tue Jul 10 20:48: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 1I8QNQ-0001qh-VP; Tue, 10 Jul 2007 20:48:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8QNP-0001p8-BZ
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:48:19 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8QNO-0000WL-Oe
	for ipv6@ietf.org; Tue, 10 Jul 2007 20:48:19 -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 3AECF11407A
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 00:48:18 +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 8779BE609B
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 00:48:17 +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 l6B0mAfO043855;
	Wed, 11 Jul 2007 10:48:10 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200707110048.l6B0mAfO043855@drugs.dv.isc.org>
To: "Stephen Sprunk" <stephen@sprunk.org>
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Tue, 10 Jul 2007 13:56:30 EST."
	<01bb01c7c329$30c2d9a0$4db8b60a@atlanta.polycom.com> 
Date: Wed, 11 Jul 2007 10:48:10 +1000
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
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


> Thus spake "Mark Andrews" <Mark_Andrews@isc.org>
> >> The alternative is to renumber the entire network every time a link goes 
> >> up
> >> or down.
> >
> > No. You don't have to renumber.  You just have to deprecate
> > the addresses associated with the downed link.  This is the
> > sort of thing routers should be able to do automatically.
> 
> Are the routers going to summon all the affected folks to a change control 
> meeting, verify the approvals, do the necessary post-change testing, etc? 
> Are they going to update all the firewall configs, DNS, etc?

	There are no firewall changes to make.  There are no DNS
	changes to make.  Just because a prefix is deprecated it
	doesn't suddenly become invalid.  When the link is restored
	the prefix will be reinstated.

	Do multi-homing NAT boxes in the IPv4 world cause a change
	control meeting?

	All this is doing is moving the source address selection
	from boxes in the middle of the network to the edge nodes.
 
> Even the above automatic address deprecation part isn't available yet, 
> despite a decade of folks claiming that renumbering is easy, and that's not 
> even the hard part.

	We are not talking about renumbering.  We are talking about
	address selection.  All the boxes will continue to have all
	the addresses before, during and after the link down event.

> >> Most of the operational and innovation costs of NAT are also present with 
> >> a
> >> stateful firewall, which any sane organization will be using, because 
> >> it's
> >> really the stateful inspection that burns you.
> >
> > NAT introduces costs above and beyond those of a stateful firewall.
> 
> That's like saying having a broken leg is an additional cost above and 
> beyond the cost of death.  Not breaking your leg doesn't make you any less 
> dead.

	So you don't think have packets change addresses and ports
	as they cross the NAT is not a additional cost especially
	for humans trying to diagnose problem?

	It definitely much easier to see traffic flows on two sided
	of a box if you don't have to also match different address
	and ports.
 
> > And as for stateful firewalls, applications should be able to
> > talk to them to open up reply traffic if needed.
> 
> Yeah, try to sell that to any enterprise security department.  It's the 
> applications and users that security folks are trying to protect their 
> networks from in the first place, and internal users are a much, much bigger 
> threat to security than external folks are.

	That is why the firewall should be on the node and not in the
	middle of the network.  Every box protects itself from every
	other box including internal boxes.
 
> >> Again, RFC 4192 ignores all of the non-technical aspects of renumbering.
> >> That's probably appropriate, given the IETF's domain, but it's only a 
> >> tiny
> >> part of what must be done.  Changing the address on an interface takes
> >> a few seconds; the change control processes leading up to it can burn
> >> months of manpower.
> >
> > Real renumbering events are rare.
> 
> That all depends what you call "real".  Any event that breaks connectivity 
> (including established connections) for more than a few seconds is "real" to 
> me.

	I said renumbering events not link outages.  If you don't have
	a routing slot for the prefix you are using, which describes PA
	addresses, then nothing a end site can do will prevent established
	connections from failing if the link to where the covering prefix
	traffic is sent fails.
 
> > You are wanting NAT to provide multi-homing support.  This does not
> > require you to renumber.  There is no need to use NAT for this with IPv6.
> > IPv6 provides the mechanisms to move the source address selection
> > back to the end host (where it belongs).
> 
> For the record, I hate NAT, for all the reasons that most of IETFers do. 
> What I'm saying is that NAT is considered by the market to be less evil than 
> the alternatives the IETF has proposed to date.  Until folks recognize that, 
> no progress will be made.
> 
> I'd much prefer to see widespread use of PI space, and significant effort 
> put into an id/loc split scheme so that the DFZ doesn't implode as a result. 
> OTOH, router vendors are claiming the ability to support two million routes 
> today and ten million in a few years, so we have time to work on that.

	Well until that comes along, providing a multi-homing solution
	that will work with existing without resorting to NAT is something
	we should be striving for.

	If there are pieces missing we should be indentifying them and
	getting vendors to implement them.  As for using multiple PA
	about the only thing I see missing is detection of the trigger
	events (link down).
 
	IPv6 has a different management paradigm to IPv4.  Education
	is important.


> 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
> --------------------------------------------------------------------
-- 
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 Jul 10 21:16: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 1I8QoL-0006TQ-2z; Tue, 10 Jul 2007 21:16:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8QoJ-0006FP-DW
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:16:07 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8QoE-0000vB-Vi
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:16:07 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85940365; Tue, 10 Jul 2007 21:16:02 -0400
Message-ID: <46942F42.7080902@internap.com>
Date: Tue, 10 Jul 2007 18:15:46 -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>, Paul Vixie <paul@vix.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>	<22851.1184090216@sa.vix.com>	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<46940949.2010908@internap.com>
	<FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>
In-Reply-To: <FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 10, 2007, at 15:33, Scott Leibrand wrote:
>>
>> [...]
>> As stated previously, the rules for getting PI space are based on the 
>> expectation that PI blocks can be announced into the DFZ.  The 
>> proposed rules for ULA-G space are based on the expectation that 
>> ULA-G blocks will not be announced into the DFZ, and that they will 
>> be allocated out of a single global netblock, identified in an RFC, 
>> that everyone knows can and should be filtered.  As stated quite 
>> clearly by Joe Abley in the "Why ULA-* will not harm the DFZ" thread, 
>> that difference in expectation, and ease in filtering when desired or 
>> necessary, makes it possible to give out ULA-G space in a 
>> non-discriminatory manner (which is simply not prudent for PI space 
>> today).
>
> Look, if we want to enable the operation of "very large local DFZ" 
> routing realms (in the hundreds of thousands or millions of networks) 
> and we're really, really concerned about accidental leakage of local 
> prefixes into the DFZ with PI addressing, then I can understand the 
> motivation for ULA-G/C.  Is that really what this is all about?  If 
> so, then I'd like to see the Introduction revised accordingly.
>
> Here is some proposed text, which I think improves the draft and makes 
> it clear what we are intending to do:

First, thank you very much for providing this constructive input.

I don't think that ULA-G prefixes necessarily have to be part of a "very 
large" routing realm to be useful, but I do think that we need to be 
able to support such a scale with the proposed solution.

>
>>> This document defines the characteristics and technical allocation 
>>> requirements for centrally-assigned Unique Local IPv6 addresses, as 
>>> defined in [ULA].  They are not expected to be routed in the 
>>> default-free zone of the public Internet.  They are intended for use 
>>> in pre-arranged interconnection between organizations and sites in 
>>> very large local routing realms.

I might suggest we say that "They are intended for use in pre-arranged 
interconnection between organizations and sites in local routing realms 
ranging in scale from small to very large."

>>>
>>> [snip]
>>>
>>> The most important property of ULAs is that they are unique, as ULA 
>>> uniqueness allows routing realms to be merged or privately 
>>> interconnected with minimal risk of prefix collisions.  The 
>>> statistical uniqueness of locally-assigned ULAs is deemed adequate 
>>> when routing realms contain a small number of local prefixes, but 
>>> insufficient in the case where routing realms routinely comprise 
>>> hundreds of thousands or even millions of networks.  A single, 
>>> global federated registry for assigning unique local prefixes is 
>>> required to address these concerns.  
>>>

In my opinion, it's not the statistical uniqueness of ULA-Ls that is 
insufficient at scale, but the ability to keep track of netblock 
ownership and DNS authority using local mechanisms.  Those problems were 
solved for the public Internet by a hierarchy of registries providing 
WHOIS services, and by a distributed DNS infrastructure providing .arpa 
reverse DNS resolution.  I believe the same solutions are applicable for 
ULA-G addresses. I would propose the following alternate text: "The 
statistical uniqueness of locally-assigned ULAs and the use of local 
methods for registry and reverse DNS services are deemed adequate when 
routing realms contain a small number of local prefixes, but 
insufficient in the case where routing realms routinely comprise 
hundreds of thousands or even millions of networks.  A single, global 
federated registry for assigning and providing registration services for 
unique local prefixes is required to address these concerns."

>>> Using ULAs for this purpose instead of Provider Independent [RIR-PI] 
>>> addresses has the attraction of making it easy to prevent leakage of 
>>> local prefixes into the default-free zone of the public Internet, 
>>> thereby enforcing the requirement to pre-arrange interconnections.

-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 Jul 10 21: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 1I8R1J-0003Xr-QV; Tue, 10 Jul 2007 21:29:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8R1I-0003Xm-7w
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:29:32 -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 1I8R1E-00018p-K4
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:29:32 -0400
Received: from eagle (192.168.123.10:1129)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S37DD2F> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 10 Jul 2007 18:29:24 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Kevin Kargel'" <kkargel@polartel.com>
References: <Pine.LNX.4.64.0706192236490.10422@netcore.fi>
	<70DE64CEFD6E9A4EB7FAF3A06314106670704A@mail>
In-Reply-To: <70DE64CEFD6E9A4EB7FAF3A06314106670704A@mail>
Date: Tue, 10 Jul 2007 18:28:29 -0700
Message-ID: <05cc01c7c35a$c950fef0$5bf2fcd0$@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: AceyqfVo5YPAeF1sSv2maDfNH4WbYgAAig6wBCrkFSA=
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
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
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

You may have received an answer to this already, but I am just catching up
and since you asked for help understanding, I thought I would provide some
context. 

The RIR community is being spun up that ULA-C is nothing more than PI
because some members want to retain control over who has addresses and how
much. PI is a hot issue because there is a potential impact to the global
routing system if it runs unchecked. 

ULA L or C is about a space that is not intended to show up in the global
routing system. As such it should not have the same restrictions over who
can have it that PI would have. 

Yes an organization with PI could implement an acl or simply limit the
length of the prefix that is announced to routing and have the same effect
---from their perspective---. From the perspective of the rest of the world
though, it is not clear if a PI block is intended to be globally routed or
not so they can't filter it arbitrarily. ULA has the upfront global
expectation that if it shows up it is a bogon that should be filtered. 

ULA-L is targeted at the soho router default config and organizations that
just don't want to deal with the RIRs. Their probability of collision is low
enough relative to their likelihood of multiple connections that it really
doesn't matter. 

ULA-C is about organizations that really want to have public bogon filtering
to help restrict access to a given network, but also want to ensure that
future mergers and acquisitions or partnerships that form will not have any
possibility of collision. 

This should never have been a big deal, but when all the RIRs were refusing
to allow any PI space ULA-C was seen as an end-around that policy. Even now,
only ARIN & APnic allow PI, so ULA-C is still perceived to be a problem for
the DFZ. 

My suggestion to both the RIPE and ARIN communities has been to embrace
ULA-C and give every member a ULA-C block in addition to whatever else they
ask for. If they don't own the space someone will, then there will be
competing registries and a real risk that ULA becomes PI due to easier
access or lower cost. If a ULA-C requires RIR membership, the member can
choose whatever space makes sense for their deployment and all this RIR/IETF
noise will not matter. 

Tony


> -----Original Message-----
> From: Kevin Kargel [mailto:kkargel@polartel.com]
> Sent: Tuesday, June 19, 2007 1:11 PM
> To: ipv6@ietf.org
> Subject: RE: draft-ietf-ipv6-ula-central-02.txt - reverse DNS
> 
> 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]
> > 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
> >
> > 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
> > --------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> 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 Jul 10 21: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 1I8RJL-0000KK-Hj; Tue, 10 Jul 2007 21:48:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8RJJ-00006H-6F
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:48:09 -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 1I8RJF-0001VN-M2
	for ipv6@ietf.org; Tue, 10 Jul 2007 21:48:09 -0400
Received: from eagle (192.168.123.10:1184)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S37DD9B> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Tue, 10 Jul 2007 18:48:03 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'james woodyatt'" <jhw@apple.com>,
	"'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>
	<467A39E2.3020303@gmail.com>	<467AA083.6070102@internap.com>
	<28803.1182449010@sa.vix.com>
	<6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
In-Reply-To: <6D902A39-BCBA-498A-BF48-B6F91762496A@apple.com>
Date: Tue, 10 Jul 2007 18:47:08 -0700
Message-ID: <05d301c7c35d$64a358b0$2dea0a10$@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: Ace0M/bI07uAsYtPTx689enoW95FngPJ9/Jg
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt use case
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

Lawyers and Sarbanes-Oxley type regulations drive some organizations to want
a registry that they can take to court if there is a future business-loss
due to an address collision. 

ULA has absolutely nothing to do with NAT, and all discussions about
IPv6-IPv6 NAT are a waste of time by those who want to cling to a comfort
source. People use address space in a variety of ways, and it is not
appropriate for the IETF or RIR community to tell them they can't do that.
What is appropriate is to set aside blocks that are recognizable for uses
that might have a detrimental impact on other uses. 

PI is not available to everyone because it has an impact on the global
routing system.

ULA-L is not appropriate for people with lawyers that want absolutes. 

ULA-C is not a real problem to implement, it just takes shutting down those
who want to make sure they retain control through the PI review process. 

Even those who acquire PI may want to use ULA-C to ensure that the multiple
layers of bogon filtering keep a private network private despite the best
efforts of fat-fingered network operators that are prone to typo's.

Tony



> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]
> Sent: Thursday, June 21, 2007 11:42 AM
> To: IETF IPv6 Mailing List
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt use case
> 
> 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.


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



From ipv6-bounces@ietf.org Tue Jul 10 22:13: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 1I8RhW-0001Me-8J; Tue, 10 Jul 2007 22:13:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8RhU-0001MQ-Pr
	for ipv6@ietf.org; Tue, 10 Jul 2007 22:13:08 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8RhQ-0001xD-8R
	for ipv6@ietf.org; Tue, 10 Jul 2007 22:13:08 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id 8C5B3BAC15C
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 19:13:03 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 7826529C002
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 19:13:03 -0700 (PDT)
X-AuditID: 11807123-a401ebb000000a55-a1-46943caff9bd
Received: from [17.206.50.117] (int-si-a.apple.com [17.128.113.41])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 54F5830400B
	for <ipv6@ietf.org>; Tue, 10 Jul 2007 19:13:03 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46942F42.7080902@internap.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<46940949.2010908@internap.com>
	<FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>
	<46942F42.7080902@internap.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3E37DD91-F777-499E-8845-8256590A1111@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Tue, 10 Jul 2007 19:13:02 -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: 34d35111647d654d033d58d318c0d21a
Subject: Re: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 10, 2007, at 18:15, Scott Leibrand wrote:
>
> I might suggest we say that "They are intended for use in pre- 
> arranged interconnection between organizations and sites in local  
> routing realms ranging in scale from small to very large."

I like that better, yes.  I suppose we needn't tell people not to  
waste money paying a registry service to avoid a N-in-2^40 chance  
where N < 100.  Reminds me: I need to buy a lottery ticket on the way  
home.

> In my opinion, it's not the statistical uniqueness of ULA-Ls that  
> is insufficient at scale, but the ability to keep track of netblock  
> ownership and DNS authority using local mechanisms.  Those problems  
> were solved for the public Internet by a hierarchy of registries  
> providing WHOIS services, and by a distributed DNS infrastructure  
> providing .arpa reverse DNS resolution.  I believe the same  
> solutions are applicable for ULA-G addresses.

As noted previously, synthesizing delegations for authoritative DNS  
content servers and WHOIS servers (and probably whatever has to  
happen for RPKI to work, I'll wager) can solve all those problems for  
all forms of ULA, not just the centrally-assigned ones.  If we're  
going to do that, I'd like to see the general solution rather than  
one that only works when I pay for a registration.

What if using ULA-C actually *increases* my risk of number collision  
at merge time because of registry service errors?  Then I have to  
choose between better assurance against having to renumber and  
enjoying the [arguably dubious] benefits of centrally managed  
authoritative DNS servers, WHOIS servers and what-not for my prefix.

Wouldn't it make more sense to provide all those service to ULA  
prefixes regardless of how they are allocated?

The one remaining issue you bring up here is the need to keep track  
of "ownership" of a local prefix.  This seems kinda tautological to  
me, but Tony Hain has probably explained the reason behind the  
perceived need for this: the functional innumeracy of various bean- 
counters, lawyers and other suits, which makes them incompetent risk  
managers.  Okay, I'll buy that.  We need ULA-C as a technical  
solution to a political problem.  (I love those.  It's the other way  
around that makes me nervous.)

> I would propose the following alternate text: "The statistical  
> uniqueness of locally-assigned ULAs and the use of local methods  
> for registry and reverse DNS services are deemed adequate when  
> routing realms contain a small number of local prefixes, but  
> insufficient in the case where routing realms routinely comprise  
> hundreds of thousands or even millions of networks.  A single,  
> global federated registry for assigning and providing registration  
> services for unique local prefixes is required to address these  
> concerns."

I guess I don't have a problem with this edit, but if we're going to  
specify synthetic delegations for registry and reverse DNS services  
for *all* ULA, not just ULA-C/G, then it would seem to complicate the  
introduction to mention it here.  If we're not going to do that, then  
yes: this is a good edit.

What's wrong with Christian Huitema's proposal to synthesize  
delegations?  It would seem to have the attraction of making the  
methods for resolving reverse DNS and WHOIS (and what-not) to have  
the following two desirable properties:

1) When two routing realms, which are each using the same ULA prefix  
(by pseudorandom collision or registry service error), are *NOT*  
merged, then interconnections to either of them from a third routing  
realm will still work.  They both have authoritative reverse DNS  
servers and WHOIS servers that respond in their routing realm.

2) Resolving recursive reverse DNS and WHOIS for an unknown ULA  
prefix doesn't depend on the availability and proper functioning of  
the managed servers of a third party on the public Internet, i.e.  
your ULA registry.  This aids in the construction of ad-hoc networks.

Finally, I also think it's important to retain the text I proposed  
below:

>>>> Using ULAs for this purpose instead of Provider Independent [RIR- 
>>>> PI] addresses has the attraction of making it easy to prevent  
>>>> leakage of local prefixes into the default-free zone of the  
>>>> public Internet, thereby enforcing the requirement to pre- 
>>>> arrange interconnections.

I think it helps to make it clear *why* ULA-C is the preferred  
alternative to RIR-PI for local routing realms that require a global  
number registry service.


--
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 Jul 10 22: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 1I8SA5-0000fa-90; Tue, 10 Jul 2007 22:42:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8SA3-0000XO-Tv
	for ipv6@ietf.org; Tue, 10 Jul 2007 22:42:39 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8S9z-0002YX-JO
	for ipv6@ietf.org; Tue, 10 Jul 2007 22:42:39 -0400
Received: from [69.33.79.194] (helo=[192.168.21.92])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.67 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1I8SCT-0003TV-BW; Wed, 11 Jul 2007 02:45:09 +0000
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2A5E@E03MVC4-UKBR.domain1.systemhost.net>
References: <454810F09B5AA04E9D78D13A5C39028A0272F96B@nyrofcs2ke2k01.corp.pvt>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2A5E@E03MVC4-UKBR.domain1.systemhost.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6BB43F43-F0C8-48F8-9BB3-5D1BAE4EC19D@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Tue, 10 Jul 2007 22:42:27 -0400
To: <michael.dillon@bt.com> <michael.dillon@bt.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: ipv6@ietf.org
Subject: Re: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 10-Jul-2007, at 17:48, <michael.dillon@bt.com>  
<michael.dillon@bt.com> wrote:

>> 2. Or release space FC00::/8 for another type of use (becuase
>> sitting on the shelf is wasteful)
>
> This is a good example of ossified IPv4 thinking. IPv6 is different  
> from
> IPv4. It is not just IPv4 with more address bits. It is not  
> wasteful to
> leave IPv6 address ranges sitting on the shelf any more than it is
> wasteful to assign a /48 prefix to a homeowner.

In fact, I was thinking as I typed in my precarious train of logic  
the other evening that one of the nice features of IPv6 is that you  
can take an enormous chunk of addresses for use as an experiment like  
this, and not have to worry to hard about reclaiming them if the  
experiment turns out to go nowhere.


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 Jul 10 23:12: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 1I8Scs-0006AE-Pw; Tue, 10 Jul 2007 23:12:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Scr-0006A8-L3
	for ipv6@ietf.org; Tue, 10 Jul 2007 23:12:25 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Scn-000301-4v
	for ipv6@ietf.org; Tue, 10 Jul 2007 23:12:25 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85944347; Tue, 10 Jul 2007 23:12:20 -0400
Message-ID: <46944A84.2010902@internap.com>
Date: Tue, 10 Jul 2007 20:12:04 -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: <200706251556.l5PFu6Qa057410@mail.reprise.com>	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>	<22851.1184090216@sa.vix.com>	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<46940949.2010908@internap.com>	<FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>	<46942F42.7080902@internap.com>
	<3E37DD91-F777-499E-8845-8256590A1111@apple.com>
In-Reply-To: <3E37DD91-F777-499E-8845-8256590A1111@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 10, 2007, at 18:15, Scott Leibrand wrote:
>>
>> I might suggest we say that "They are intended for use in 
>> pre-arranged interconnection between organizations and sites in local 
>> routing realms ranging in scale from small to very large."
>
> I like that better, yes.  I suppose we needn't tell people not to 
> waste money paying a registry service to avoid a N-in-2^40 chance 
> where N < 100.  Reminds me: I need to buy a lottery ticket on the way 
> home.

Heh.  Bummer the government has a monopoly on lotteries.  I'd love to 
sell you a few.  :-)

>
>> In my opinion, it's not the statistical uniqueness of ULA-Ls that is 
>> insufficient at scale, but the ability to keep track of netblock 
>> ownership and DNS authority using local mechanisms.  Those problems 
>> were solved for the public Internet by a hierarchy of registries 
>> providing WHOIS services, and by a distributed DNS infrastructure 
>> providing .arpa reverse DNS resolution.  I believe the same solutions 
>> are applicable for ULA-G addresses.
>
> As noted previously, synthesizing delegations for authoritative DNS 
> content servers and WHOIS servers (and probably whatever has to happen 
> for RPKI to work, I'll wager) can solve all those problems for all 
> forms of ULA, not just the centrally-assigned ones.  If we're going to 
> do that, I'd like to see the general solution rather than one that 
> only works when I pay for a registration.

I'd love to see the details of such a solution.  I haven't read up on 
how synthesized delegations would work: all the schemes I've seen so far 
are less scalable than the Internet's distributed DNS hierarchy.

>
> What if using ULA-C actually *increases* my risk of number collision 
> at merge time because of registry service errors?  Then I have to 
> choose between better assurance against having to renumber and 
> enjoying the [arguably dubious] benefits of centrally managed 
> authoritative DNS servers, WHOIS servers and what-not for my prefix.

Well, I suppose we could fit a few more angels on the head of the 
pin...  :-)  (I don't think the risk of collision in either case is 
something to worry about.)

>
> Wouldn't it make more sense to provide all those service to ULA 
> prefixes regardless of how they are allocated?
>
> The one remaining issue you bring up here is the need to keep track of 
> "ownership" of a local prefix.  This seems kinda tautological to me, 
> but Tony Hain has probably explained the reason behind the perceived 
> need for this: the functional innumeracy of various bean-counters, 
> lawyers and other suits, which makes them incompetent risk managers.  
> Okay, I'll buy that.  We need ULA-C as a technical solution to a 
> political problem.  (I love those.  It's the other way around that 
> makes me nervous.)

Well, it may solve some political problems, but it definitely meets some 
real needs as well.  For example, say I'm parsing mail logs in my spam 
folder, and find a mail server that received my mail from a client using 
a ULA-G address, and then sent it to my mail server using a PA address.  
With whois to track ownership, I can look up the owner and abuse contact 
of the infected client as well as the server that relayed the message.

>
>> I would propose the following alternate text: "The statistical 
>> uniqueness of locally-assigned ULAs and the use of local methods for 
>> registry and reverse DNS services are deemed adequate when routing 
>> realms contain a small number of local prefixes, but insufficient in 
>> the case where routing realms routinely comprise hundreds of 
>> thousands or even millions of networks.  A single, global federated 
>> registry for assigning and providing registration services for unique 
>> local prefixes is required to address these concerns."
>
> I guess I don't have a problem with this edit, but if we're going to 
> specify synthetic delegations for registry and reverse DNS services 
> for *all* ULA, not just ULA-C/G, then it would seem to complicate the 
> introduction to mention it here.  If we're not going to do that, then 
> yes: this is a good edit.
>
> What's wrong with Christian Huitema's proposal to synthesize 
> delegations?  It would seem to have the attraction of making the 
> methods for resolving reverse DNS and WHOIS (and what-not) to have the 
> following two desirable properties:
>
> 1) When two routing realms, which are each using the same ULA prefix 
> (by pseudorandom collision or registry service error), are *NOT* 
> merged, then interconnections to either of them from a third routing 
> realm will still work.  They both have authoritative reverse DNS 
> servers and WHOIS servers that respond in their routing realm.
>
> 2) Resolving recursive reverse DNS and WHOIS for an unknown ULA prefix 
> doesn't depend on the availability and proper functioning of the 
> managed servers of a third party on the public Internet, i.e. your ULA 
> registry.  This aids in the construction of ad-hoc networks.

Those sound like good properties.  Can you point me to Christian 
Huitema's proposal?  I'm not sure I've seen it before.

>
> Finally, I also think it's important to retain the text I proposed below:
>
>>>>> Using ULAs for this purpose instead of Provider Independent 
>>>>> [RIR-PI] addresses has the attraction of making it easy to prevent 
>>>>> leakage of local prefixes into the default-free zone of the public 
>>>>> Internet, thereby enforcing the requirement to pre-arrange 
>>>>> interconnections.
>
> I think it helps to make it clear *why* ULA-C is the preferred 
> alternative to RIR-PI for local routing realms that require a global 
> number registry service.

I agree, and didn't mean to imply that it should be removed.

-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 Jul 11 05: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 1I8Ya4-0002Qm-4u; Wed, 11 Jul 2007 05:33:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Ya0-0002GG-OW
	for ipv6@ietf.org; Wed, 11 Jul 2007 05:33:52 -0400
Received: from smtp1.mail.adnap.net.au ([203.6.132.75])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8YZl-00036K-9q
	for ipv6@ietf.org; Wed, 11 Jul 2007 05:33:52 -0400
Received: from 219-90-138-181.ip.adam.com.au ([219.90.138.181]
	helo=mail.nosense.org)
	by smtp1.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1I8YZ5-0003Vz-2P; Wed, 11 Jul 2007 19:02:55 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 55687FC83;
	Wed, 11 Jul 2007 19:02:53 +0930 (CST)
Date: Wed, 11 Jul 2007 19:02:53 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Joe Abley <jabley@ca.afilias.info>
Message-Id: <20070711190253.5b848a9b.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <6BB43F43-F0C8-48F8-9BB3-5D1BAE4EC19D@ca.afilias.info>
References: <454810F09B5AA04E9D78D13A5C39028A0272F96B@nyrofcs2ke2k01.corp.pvt>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2A5E@E03MVC4-UKBR.domain1.systemhost.net>
	<6BB43F43-F0C8-48F8-9BB3-5D1BAE4EC19D@ca.afilias.info>
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.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org
Subject: Re: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 10 Jul 2007 22:42:27 -0400
Joe Abley <jabley@ca.afilias.info> wrote:

> 
> On 10-Jul-2007, at 17:48, <michael.dillon@bt.com>  
> <michael.dillon@bt.com> wrote:
> 
> >> 2. Or release space FC00::/8 for another type of use (becuase
> >> sitting on the shelf is wasteful)
> >
> > This is a good example of ossified IPv4 thinking. IPv6 is different  
> > from
> > IPv4. It is not just IPv4 with more address bits. It is not  
> > wasteful to
> > leave IPv6 address ranges sitting on the shelf any more than it is
> > wasteful to assign a /48 prefix to a homeowner.
> 
> In fact, I was thinking as I typed in my precarious train of logic  
> the other evening that one of the nice features of IPv6 is that you  
> can take an enormous chunk of addresses for use as an experiment like  
> this, and not have to worry to hard about reclaiming them if the  
> experiment turns out to go nowhere.
> 

Exactly.

Convenience is a desirable characteristic, functionality is an
essential one.

With IPv6's large address space we have both convenience
and functionality.

We used to have both with IPv4 too, but then the Internet had to be
scaled to connect the world, so convenience had to go. By changing to
IPv6, we can now have it back.

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 Wed Jul 11 05:39: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 1I8Yf4-0000me-4k; Wed, 11 Jul 2007 05:39:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Yf3-0000mV-7V
	for ipv6@ietf.org; Wed, 11 Jul 2007 05:39:05 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8Yey-0002I3-MH
	for ipv6@ietf.org; Wed, 11 Jul 2007 05:39:05 -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 l6B9cvjU087580
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Jul 2007 11:38:57 +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
	l6B9cui9032011; Wed, 11 Jul 2007 11:38:57 +0200
Date: Wed, 11 Jul 2007 11:38:56 +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: <B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
Message-ID: <Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@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: 0ddefe323dd869ab027dbfff7eff0465
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

On Tue, 10 Jul 2007, james woodyatt wrote:
<snip>
>
> Hmmm.  I guess the alternative is that the purpose of ULA-C/G is to mitigate 
> the risk of collision when merging on the order of hundreds of thousands of 
> ULA networks in one routing realm... sort of like creating a "local DFZ" of a 
> sort.
>
> Forgive me, but that sounds even more surreal.  It's tough for me to imagine 
> how a real organization doing that could fail to qualify for a PI allocation, 
> or why such an organization would find it unacceptable to have to use a PI 
> allocation without advertising it to the public DFZ.  Likewise, it's tough to 
> imagine how an organization that doesn't qualify for a PI allocation could be 
> merging enough ULA networks together that the risk of collision rises to a 
> level of any real significance.
>
> Okay.  Maybe the problem with PI allocations for this purpose is that 
> organizations doing all this network merging, i.e. extraordinarily paranoid 
> organizations, e.g. the Communist Party, want some kind of assurance from the 
> operators of the public Internet that their hundreds of thousands of local 
> networks aren't directly reachable from the public DFZ in the event a local 
> NOC configures a border router improperly.  Obviously, ULA-C can do that 
> better than PI.
>
> Is that the big driving factor here?

PI can be used for almost everything ULA-C/G can be used for, dont think 
anyone disagree on that. The whole ULA-C/G is about the purpose of the 
address space and what it can be used for both now and in the future. 
Strictly internal/private networking right now and ID/LOC or whatever in 
the future... or other thing we dont know about.

It is more about creating a address space that can be used for OTHER thing 
than the DFZ-way of thinking Internet we have now.

And yes you have a good point, internal infrastructure like the above 
operator but that is almost excacly what we (where I work) want to use it 
for! .. just that we will also place some of our customers there to.
(and please dont start the rant about NAT or whatever we need to get them 
onto internet because they are not suppose to be conneted directly to 
internet)



-- 

------------------------------
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 Jul 11 06:01: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 1I8Z0l-0008LP-90; Wed, 11 Jul 2007 06:01:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8Z0j-0008LK-OO
	for ipv6@ietf.org; Wed, 11 Jul 2007 06:01:29 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8Z0j-0003ji-CJ
	for ipv6@ietf.org; Wed, 11 Jul 2007 06:01:29 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 11:01:04 +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, 11 Jul 2007 11:01:54 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfDn1g1HRQYCWt5REWZW/aN8hfNRAAAKwFQ
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 11 Jul 2007 10:01:04.0091 (UTC)
	FILETIME=[6475D2B0:01C7C3A2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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


> It is more about creating a address space that can be used=20
> for OTHER thing than the DFZ-way of thinking Internet we have now.

Up until now, I've been on the fence regarding ULA-centrally-registered
address space, but after several comments in the past two days, I now
support defining these addresses.

Other factors that I think help make the case:

1) The RIR system is already in place to deal with DFZ grey areas. If we
delegate the central registry function to the RIRs, they can deal with
the details of how such addresses are handed out (automatically or on
demand), charges for maintaining the registry and ip6.int services, and
sorting out the issues of non-aggregation and global routing table
entries.

2) These ULA addresses provide an additional layer of security in a
layered security model. If I use my PI addresses for secret internal
infrastructure, I must block those ranges in my firewall. Networks which
I connect to will likely not block these ranges, so I have one layer of
security. If I use ULA addresses, then the vast majority of other
networks will block the entire ULA range, thus giving me an additional
layer of security. If I need to use ULA addreses to talk to a peer, we
can both punch holes in our filters/firewalls.

3) ULA addresses reduce the administrative burden. If I use some PI
addresses for secret internal infrastructure, I must repeatedly update
filters at the edge to block traffic to these ranges. If I use ULA
addresses, then I simply block the entire ULA range and never need to
update filters.

In general, it seems to me that the benefits fall on the enterprise
network side, and the possibly disadvantages fall on the ISP side. The
IETF needs to provide technology that supports all users of IPv6. Since
there are other mechanisms outside the IETF to deal with the ISPs'
issues, I think we need to go ahead with ULA centrally-registered.

Paul's draft which assigns 12 bits to each RIR seems to be the right
thing since it clearly delineates which RIR is responsible for each
subset range, and therefore if an RIR policy dictates special handling
for certain ULA addresses, there is a simple technical means to
accomplish this.

I'm not sure what the status of Paul's document is since the drafts
directory only contains this one:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt

Is Paul's superceding that or is there a merge in process?

--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 Jul 11 07: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 1I8aGP-0006Ih-A6; Wed, 11 Jul 2007 07:21:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8aGO-0006IZ-5b
	for ipv6@ietf.org; Wed, 11 Jul 2007 07:21:44 -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 1I8aGM-0004rM-7j
	for ipv6@ietf.org; Wed, 11 Jul 2007 07:21:44 -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 D667B140C067;
	Wed, 11 Jul 2007 13:21:37 +0200 (CEST)
Message-ID: <4694BD3D.20708@spaghetti.zurich.ibm.com>
Date: Wed, 11 Jul 2007 12:21: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: michael.dillon@bt.com
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
X-Enigmail-Version: 0.95.2
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: 944ecb6e61f753561f559a497458fb4f
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="===============0213218865=="
Errors-To: ipv6-bounces@ietf.org

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

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

michael.dillon@bt.com wrote:
>> It is more about creating a address space that can be used=20
>> for OTHER thing than the DFZ-way of thinking Internet we have now.
>=20
> Up until now, I've been on the fence regarding ULA-centrally-registered=

> address space, but after several comments in the past two days, I now
> support defining these addresses.

My views are also changing, toward positive, based on the discussions,
but there is a big but: the draft needs to say those things too.

The description has to be heavily updated to explain really WHY this
type of addresses (should) exist and for what usages. Also I am pretty
convinced that the naming has to be changed. The RFC4193 ULA naming is
quite accurate, but for the kind of usage that has been discussed
recently ULA is not a good name. Also the draft should very clearly
outline the pro's and con's that this type of address space has for
potential users of it. That they can be used as EID's at a certain point
in time is also that should be documented in the draft.

As such, I am awaiting the new draft.

> Other factors that I think help make the case:
>=20
> 1) The RIR system is already in place to deal with DFZ grey areas. If w=
e
> delegate the central registry function to the RIRs, they can deal with
> the details of how such addresses are handed out (automatically or on
> demand), charges for maintaining the registry and ip6.int services, and=

> sorting out the issues of non-aggregation and global routing table
> entries.

You most definitely meant ip6.arpa there instead of ip6.int which was
deprecated quite some time ago. Indeed, the RIR's are already in place
if something to the effect of the proposed address space would ever come
to be then they are the places that should be the registries for it.
Inventing new structures for that would not be helpful at all.

> 2) These ULA addresses provide an additional layer of security in a
> layered security model. If I use my PI addresses for secret internal
> infrastructure, I must block those ranges in my firewall.

Or simply not route them at all. I don't really see this is a benefit.
It is only a benefit against so called fat fingers, but if you have that
problem there are bigger problems at hand, especially in an area where
security is to be required.

> Networks which
> I connect to will likely not block these ranges, so I have one layer of=

> security. If I use ULA addresses, then the vast majority of other
> networks will block the entire ULA range, thus giving me an additional
> layer of security. If I need to use ULA addresses to talk to a peer, we=

> can both punch holes in our filters/firewalls.

Maybe to reflect the above, the draft should definitely state that
firewalls should per default at least propose to block these ranges.

> In general, it seems to me that the benefits fall on the enterprise
> network side, and the possibly disadvantages fall on the ISP side. The
> IETF needs to provide technology that supports all users of IPv6. Since=

> there are other mechanisms outside the IETF to deal with the ISPs'
> issues, I think we need to go ahead with ULA centrally-registered.

The question here still remains though: how really different is this
from "PI". In effect it is non-DFZ-PI space that is being defined here.
RIR's themselves could thus also set aside a /20 or something and
allocate /40-/48's from that block for that purpose and state "currently
these might be routable, but in the future they will not be".
Which is quite less of an addressing burn than this.

[..]
> Is Paul's superceding that or is there a merge in process?

I understood that he is busy updating it and tried to submit it, though
submitted it after the -00 deadline. Which means that for the time being
it can't be updated :(

Greets,
 Jeroen


--------------enig38504F2EEDCD48315678D03E
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/

iHUEARECADUFAkaUvUAuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I5pdAJkBZH5c/uPlZxtQ47VJt4161vQo
bACfXdQDikG24y0gLdNMZE7kaQYH9Ww=
=SHoG
-----END PGP SIGNATURE-----

--------------enig38504F2EEDCD48315678D03E--


--===============0213218865==
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
--------------------------------------------------------------------

--===============0213218865==--




From ipv6-bounces@ietf.org Wed Jul 11 07:50: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 1I8ai5-00061b-Ls; Wed, 11 Jul 2007 07:50:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8ai4-00061N-5h
	for ipv6@ietf.org; Wed, 11 Jul 2007 07:50:20 -0400
Received: from smtp2.smtp.bt.com ([217.32.164.150])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8aho-00060E-Ss
	for ipv6@ietf.org; Wed, 11 Jul 2007 07:50:20 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 12:49:40 +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, 11 Jul 2007 12:51:13 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AA2DC9@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <4694BD3D.20708@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfDracjZig411RsTGGRdw3ssFvo1wAA0b0w
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<4694BD3D.20708@spaghetti.zurich.ibm.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 11 Jul 2007 11:49:40.0340 (UTC)
	FILETIME=[90728340:01C7C3B1]
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

> The question here still remains though: how really different=20
> is this from "PI". In effect it is non-DFZ-PI space that is=20
> being defined here.

PI (Provider Independent) is not a relevant term to refer to addresses
that are allocated to end-user organizations for use in their own
networks. There is no provider in such a scenario, therefore the
addresses are neither provider-independent nor provider-dependent. In
fact, they are local to the end-user network which is why people have
been referring to them as Unique Local Addresses (ULA). It appears that
we are accumulating enough changes from the original ULA that it is not
correct to refer to them as ULA addresses that are centrally registered.
However, they are Unique, and they are Local. Perhaps ULRA (Unique Local
Registered Addresses) is sufficiently different from ULA that people
will not accidentally look to RFC 4193 for advice?

--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 Jul 11 08: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 1I8b0C-0002NF-9N; Wed, 11 Jul 2007 08:09:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8b0A-0002F1-V7
	for ipv6@ietf.org; Wed, 11 Jul 2007 08:09:02 -0400
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8b06-00063c-Mn
	for ipv6@ietf.org; Wed, 11 Jul 2007 08:09:02 -0400
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id 8A0CF7F8B;
	Wed, 11 Jul 2007 08:08:58 -0400 (EDT)
Received: from heartbeat1.messagingengine.com ([10.202.2.160])
	by compute1.internal (MEProxy); Wed, 11 Jul 2007 08:08:58 -0400
X-Sasl-enc: CQyUdV9vVICCzDub1Sg1HIN3MiNivMF2jGziARB/UwzR 1184155736
Received: from [127.0.0.1] (unknown [202.109.114.178])
	by mail.messagingengine.com (Postfix) with ESMTP id 76C903939;
	Wed, 11 Jul 2007 08:08:53 -0400 (EDT)
From: Per Heldal <heldal@eml.cc>
To: Jeroen Massar <jeroen@unfix.org>
In-Reply-To: <4694BD3D.20708@spaghetti.zurich.ibm.com>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<4694BD3D.20708@spaghetti.zurich.ibm.com>
Content-Type: text/plain
Date: Wed, 11 Jul 2007 14:08:41 +0200
Message-Id: <1184155721.14166.162.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: 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

On Wed, 2007-07-11 at 12:21 +0100, Jeroen Massar wrote:

> The question here still remains though: how really different is this
> from "PI". In effect it is non-DFZ-PI space that is being defined here.
> RIR's themselves could thus also set aside a /20 or something and
> allocate /40-/48's from that block for that purpose and state "currently
> these might be routable, but in the future they will not be".
> Which is quite less of an addressing burn than this.
> 

It's much easier/faster to identify any ULA-space (FC00::/7) in one
comparison than having to match individual (possibly variable)
RIR-ranges (for filtering etc). Especially if/when such algorithms are
implemented in silicon for enhanced performance.


//per



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



From ipv6-bounces@ietf.org Wed Jul 11 10:15: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 1I8cyX-0007vc-B7; Wed, 11 Jul 2007 10:15:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8cyW-0007vX-Ke
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:15:28 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8cyV-0001Ly-D1
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:15:28 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 8A2851142E
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 14:15:26 +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, 11 Jul 2007 11:38:56 +0200."
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no> 
References: <200706251556.l5PFu6Qa057410@mail.reprise.com>
	<078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com>
	<94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com>
	<Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no>
	<FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com>
	<22851.1184090216@sa.vix.com>
	<B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 11 Jul 2007 14:15:26 +0000
Message-ID: <28075.1184163326@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
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

> It is more about creating a address space that can be used for OTHER thing
> than the DFZ-way of thinking Internet we have now.

yup.

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



From ipv6-bounces@ietf.org Wed Jul 11 10: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 1I8d6T-0006E5-Ib; Wed, 11 Jul 2007 10:23:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8d6R-0006Dj-Sf
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:23:39 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8d6Q-0001YT-II
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:23:39 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id AF66211425
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 14:23: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 "Wed, 11 Jul 2007 11:01:54 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 11 Jul 2007 14:23:37 +0000
Message-ID: <28681.1184163817@sa.vix.com>
X-Spam-Score: -2.8 (--)
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

> Paul's draft which assigns 12 bits to each RIR seems to be the right
> thing since it clearly delineates which RIR is responsible for each
> subset range, and therefore if an RIR policy dictates special handling
> for certain ULA addresses, there is a simple technical means to
> accomplish this.

it's expected that iana will hand out blocks of 100 RIR-sized ULA-G blocks
to each RIR, similar to how ASN blocks are assigned, just to save paperwork.
but yes, since each RIR will have its own chunks of this space, they can do
whatever their regional member-driven policy development process tells them
to do as far as carving it up and handing it out to LIRs, endusers, etc.

> I'm not sure what the status of Paul's document is since the drafts
> directory only contains this one:
> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt
> 
> Is Paul's superceding that or is there a merge in process?

the other authors of ula-global have not commented on my hijackery.  they
might be supportive, or angry, or complacent, about the draft-fork i made.
maybe they'll want their names removed.  maybe they'll want to merge ula-g
into ula-c and have my name removed.  maybe they'll want the fork to stay.

the i-d editor determined that my submission came after the chicago cutoff,
which really oughtn't apply for WG's that are not meeting, but so it goes.

the WG chairs have ignored my mail thus far.

so my take is, suggested changes and statements of opposition||support can
be made based on the text at http://sa.vix.com/~vixie/ula-global.txt.  i'll
be rev'ing the draft based on james' and scott's comments shortly.

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



From ipv6-bounces@ietf.org Wed Jul 11 10:32: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 1I8dEf-0000c0-Ua; Wed, 11 Jul 2007 10:32:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8dEe-0000bq-GQ
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:32:08 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8dEe-0001lZ-92
	for ipv6@ietf.org; Wed, 11 Jul 2007 10:32:08 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id D76DD11425
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 14:32:07 +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, 11 Jul 2007 12:51:13 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2DC9@E03MVC4-UKBR.domain1.systemhost.net>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<4694BD3D.20708@spaghetti.zurich.ibm.com>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2DC9@E03MVC4-UKBR.domain1.systemhost.net>
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Wed, 11 Jul 2007 14:32:07 +0000
Message-ID: <33266.1184164327@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
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, they are Unique, and they are Local. Perhaps ULRA (Unique Local
> Registered Addresses) is sufficiently different from ULA that people
> will not accidentally look to RFC 4193 for advice?

suits me.

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



From ipv6-bounces@ietf.org Wed Jul 11 11:31: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 1I8e9N-0003Dd-E2; Wed, 11 Jul 2007 11:30:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8e9K-00038M-Dx; Wed, 11 Jul 2007 11:30:42 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I8e97-0003cE-4K; Wed, 11 Jul 2007 11:30:42 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l6BFXC5D026824;
	Wed, 11 Jul 2007 10:33:12 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 10:29:07 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 10:29:07 -0500
Message-ID: <4694F752.8090406@ericsson.com>
Date: Wed, 11 Jul 2007 11:29:22 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: ipv6@ietf.org, netlmm@ietf.org, mobopts@ietf.org, nemo@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Jul 2007 15:29:07.0548 (UTC)
	FILETIME=[38B701C0:01C7C3D0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 
Subject: [Fwd: WGLC for draft-ietf-dna-protocol-06.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 Folks,
   We would like to hear your comments on this document as well. This 
document is a significant update to ipv6 neighbor discovery and we would 
like some more eyeballs. Please spare some time from your busy schedule 
to give it a look.

Thanks
Suresh

-------- Original Message --------
Subject: WGLC for draft-ietf-dna-protocol-06.txt
Date: Wed, 04 Jul 2007 15:47:24 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Dna <dna@eng.monash.edu.au>
CC: Greg Daley <Greg.Daley@eng.monash.edu.au>,  Jari Arkko 
<jari.arkko@piuha.net>

This mail starts a 2 week working group Last Call for comments for the
following dna working group document

draft-ietf-dna-protocol-06.txt

to be sent to the IESG for consideration as a Standards Track RFC.

Please review the document carefully, and send your feedback to the
list. Please also indicate whether or not you believe that this
document is ready to go to the IESG.

The last call will end on 2007/07/18.

Cheers
Suresh & Greg


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



From ipv6-bounces@ietf.org Wed Jul 11 12: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 1I8edg-00045l-IY; Wed, 11 Jul 2007 12:02:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8edf-00042N-GR
	for ipv6@ietf.org; Wed, 11 Jul 2007 12:02:03 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8edb-0004PI-5n
	for ipv6@ietf.org; Wed, 11 Jul 2007 12:02:03 -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 l6BG1vwY002316
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 11 Jul 2007 09:01:57 -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
	l6BG1uFp027363; Wed, 11 Jul 2007 09:01:56 -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
	l6BG1av6026239; Wed, 11 Jul 2007 09:01: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); 
	Wed, 11 Jul 2007 08:59: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, 11 Jul 2007 08:59:04 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8F8@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <FC2D95A7-404C-4535-8FAF-380811B677EA@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: The purpose of ULA-G
Thread-Index: AcfDT8J1Xh1ooXIkTAmsvJGFdlRkrgAg4RXg
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com><46940949.2010908@internap.com>
	<FC2D95A7-404C-4535-8FAF-380811B677EA@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: 11 Jul 2007 15:59:05.0788 (UTC)
	FILETIME=[688CA7C0:01C7C3D4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
Subject: RE: The purpose of ULA-G
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Look, if we want to enable the operation of "very large local DFZ" =20
> routing realms (in the hundreds of thousands or millions of=20
> networks) =20
> and we're really, really concerned about accidental leakage of local =20
> prefixes into the DFZ with PI addressing, then I can understand the =20
> motivation for ULA-G/C.  Is that really what this is all about?  If =20
> so, then I'd like to see the Introduction revised accordingly.

Not to pick on James' post, but several have mentioned that
large routing realms would be one reason to require ULA-G/C
and it has not yet been suggested that the reverse DNS could
itself be thought of as a "large routing realm" of sorts
(depending on how applications use the information they find
there). ULA-G/C would ideally allow collision-free population
of the reverse DNS even with O(10^6) or more delegations.

I can't comment furhter on Paul's proposal other than to say
that *some* authority(s) needs to be responsible for the
collision free delegations.

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 Jul 11 12:44: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 1I8fIW-0007qB-G0; Wed, 11 Jul 2007 12:44:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fIV-0007lU-DH
	for ipv6@ietf.org; Wed, 11 Jul 2007 12:44:15 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8fIR-0006HF-2U
	for ipv6@ietf.org; Wed, 11 Jul 2007 12:44:15 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.151600906;
	Wed, 11 Jul 2007 12:49:43 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Wed, 11 Jul 2007 12:43:47 -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: Wed, 11 Jul 2007 12:43:46 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A023EFC00@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Why ULA-* will not harm the DFZ
Thread-Index: AcfDZV7bB5OHOE2XRzK9/VoVEzzcigAdIeDw
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: "Joe Abley" <jabley@ca.afilias.info>,
	<michael.dillon@bt.com>
X-OriginalArrivalTime: 11 Jul 2007 16:43:47.0623 (UTC)
	FILETIME=[A70C3370:01C7C3DA]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org
Subject: RE: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 not surprised that conservation isn't the number one priority.  I =
just don't think its wise to ignore conservation.  We cant predict Ipv6 =
consumption and we don't even know what will exist for technology in the =
future that will require IP Addresses.

Cheers!
Marla Azinger

-----Original Message-----
From: Joe Abley [mailto:jabley@ca.afilias.info]
Sent: Tuesday, July 10, 2007 7:42 PM
To: <michael.dillon@bt.com>
Cc: ipv6@ietf.org
Subject: Re: [ppml] Why ULA-* will not harm the DFZ



On 10-Jul-2007, at 17:48, <michael.dillon@bt.com> =20
<michael.dillon@bt.com> wrote:

>> 2. Or release space FC00::/8 for another type of use (becuase
>> sitting on the shelf is wasteful)
>
> This is a good example of ossified IPv4 thinking. IPv6 is different =20
> from
> IPv4. It is not just IPv4 with more address bits. It is not =20
> wasteful to
> leave IPv6 address ranges sitting on the shelf any more than it is
> wasteful to assign a /48 prefix to a homeowner.

In fact, I was thinking as I typed in my precarious train of logic =20
the other evening that one of the nice features of IPv6 is that you =20
can take an enormous chunk of addresses for use as an experiment like =20
this, and not have to worry to hard about reclaiming them if the =20
experiment turns out to go nowhere.


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 Jul 11 13:01: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 1I8fZL-0000mY-Ok; Wed, 11 Jul 2007 13:01:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8fZK-0000mR-22
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:01:38 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8fZF-0006uw-MF
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:01:38 -0400
Received: from [66.175.96.118] (helo=[10.100.1.103])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.67 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1I8fbj-000D36-Oy; Wed, 11 Jul 2007 17:04:08 +0000
In-Reply-To: <454810F09B5AA04E9D78D13A5C39028A023EFC00@nyrofcs2ke2k01.corp.pvt>
References: <454810F09B5AA04E9D78D13A5C39028A023EFC00@nyrofcs2ke2k01.corp.pvt>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F7EB66AF-1C00-4BBF-947D-6AE3279BEE0F@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Wed, 11 Jul 2007 13:01:25 -0400
To: "Azinger, Marla" <marla.azinger@frontiercorp.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org
Subject: Re: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 11-Jul-2007, at 12:43, Azinger, Marla wrote:

> I am not surprised that conservation isn't the number one  
> priority.  I just don't think its wise to ignore conservation.  We  
> cant predict Ipv6 consumption and we don't even know what will  
> exist for technology in the future that will require IP Addresses.

I think with 128 bits there's a middle ground between ruthless  
conservation and "a /48 for every fridge"

But I guess my point was really that we shouldn't necessarily expect  
to guess right first time, every time, and it's nice to have some  
latitude to be able to make decisions in a finite timescale rather  
than deferring decisions for ever out of fear that they might be wrong.


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 Jul 11 13:02: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 1I8fab-0005JH-VX; Wed, 11 Jul 2007 13:02:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8faa-0005Ip-RC
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:02:56 -0400
Received: from static-66-15-163-216.bdsl.verizon.net ([66.15.163.216]
	helo=tndh.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I8faa-00078Q-AX
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:02:56 -0400
Received: from eagle (192.168.123.10:2666)
	by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server]
	id <S37F5D6> for <ipv6@ietf.org> from <alh-ietf@tndh.net>;
	Wed, 11 Jul 2007 10:02:04 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Paul Vixie'" <paul@vix.com>,
	<ipv6@ietf.org>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<28681.1184163817@sa.vix.com>
In-Reply-To: <28681.1184163817@sa.vix.com>
Date: Wed, 11 Jul 2007 10:01:05 -0700
Message-ID: <072c01c7c3dd$122b6110$36822330$@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: AcfDxxaxklt+cAixSJOZ5dM7M7tdxAAEthoQ
Content-Language: en-us
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: 
Subject: RE: draft-ietf-ipv6-ula-central-02.txt 
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

I have a few points on Paul's draft:

Nit - LocalNum = 28 bits (you lost 4 bits somewhere)

Minor point - 5.1 is not globally true yet, but should be

Major complaint -  aggregation
	There needs to be at least a modest capability to aggregate. I
understand the aversion to having these show up in the DFZ, but if 5.1 were
really true that would not be an issue. The use case that needs to be
supported is for internal aggregation of private peering clusters. Global
organizations have many external relationships, but typically have them
clustered in small groupings for logistics reasons. At the same time they
don't necessarily want to carry the explicit routes for every organization
throughout their internal network. If the ULA-C/G space has some modest
aggregation  like sparse allocation of the RIR num block to allow clustering
subsequent block to the same RIR and a suggestion for E-W-N-S regional
management within the RIR space, then it would be possible to aggregate the
internal routes to these private peering clusters. 


5.6 last sentence seems to be prescriptive, and would be more descriptive if
opened with 'It is expected that ...'

6.1 - One point of the entire ULA space is that this is a different
'filtering process'. Where typical filters block packets received at the
border for the target address, the ULA space is about not even having a
route for that packet in the first place. Yes there is no more or less
security than any other unicast address when routing announcements and
packet filtering match, but the default assumption that ULA is a bogon
routing announcement should add a layer of security that can't be done with
PI for most use cases.

Tony 


> -----Original Message-----
> From: Paul Vixie [mailto:paul@vix.com]
> Sent: Wednesday, July 11, 2007 7:24 AM
> To: ipv6@ietf.org
> Subject: Re: draft-ietf-ipv6-ula-central-02.txt
> 
> > Paul's draft which assigns 12 bits to each RIR seems to be the right
> > thing since it clearly delineates which RIR is responsible for each
> > subset range, and therefore if an RIR policy dictates special
> handling
> > for certain ULA addresses, there is a simple technical means to
> > accomplish this.
> 
> it's expected that iana will hand out blocks of 100 RIR-sized ULA-G
> blocks
> to each RIR, similar to how ASN blocks are assigned, just to save
> paperwork.
> but yes, since each RIR will have its own chunks of this space, they
> can do
> whatever their regional member-driven policy development process tells
> them
> to do as far as carving it up and handing it out to LIRs, endusers,
> etc.
> 
> > I'm not sure what the status of Paul's document is since the drafts
> > directory only contains this one:
> > http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-
> 02.txt
> >
> > Is Paul's superceding that or is there a merge in process?
> 
> the other authors of ula-global have not commented on my hijackery.
> they
> might be supportive, or angry, or complacent, about the draft-fork i
> made.
> maybe they'll want their names removed.  maybe they'll want to merge
> ula-g
> into ula-c and have my name removed.  maybe they'll want the fork to
> stay.
> 
> the i-d editor determined that my submission came after the chicago
> cutoff,
> which really oughtn't apply for WG's that are not meeting, but so it
> goes.
> 
> the WG chairs have ignored my mail thus far.
> 
> so my take is, suggested changes and statements of opposition||support
> can
> be made based on the text at http://sa.vix.com/~vixie/ula-global.txt.
> i'll
> be rev'ing the draft based on james' and scott's comments shortly.
> 
> --------------------------------------------------------------------
> 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 Jul 11 13: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 1I8g2J-0005kp-AI; Wed, 11 Jul 2007 13:31:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8g2H-0005kH-PZ
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:31:33 -0400
Received: from mail02.frontiercorp.com ([66.133.172.20] helo=frontiercorp.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8g22-00006Z-J5
	for ipv6@ietf.org; Wed, 11 Jul 2007 13:31:33 -0400
Received: from ([10.160.67.161])
	by mail02.frontiercorp.com with ESMTP  id KP-AXMBT.151605737;
	Wed, 11 Jul 2007 13:36:23 -0400
Received: from nyrofcs2ke2k01.corp.pvt ([10.160.64.140]) by
	NYROFCS2KE2K04.corp.pvt with Microsoft SMTPSVC(5.0.2195.6713); 
	Wed, 11 Jul 2007 13:30:25 -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: Wed, 11 Jul 2007 13:30:25 -0400
Message-ID: <454810F09B5AA04E9D78D13A5C39028A023EFC04@nyrofcs2ke2k01.corp.pvt>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ppml] Why ULA-* will not harm the DFZ
Thread-Index: AcfD3Ybelxty5Xp0SDWgpJlXdF7ihQAAndbA
From: "Azinger, Marla" <marla.azinger@frontiercorp.com>
To: "Joe Abley" <jabley@ca.afilias.info>
X-OriginalArrivalTime: 11 Jul 2007 17:30:25.0860 (UTC)
	FILETIME=[2AED4840:01C7C3E1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: ipv6@ietf.org
Subject: RE: [ppml] Why ULA-* will not harm the DFZ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 my main point on the first response I made to this string you =
started has taken a curve ball. I had no intentions of turning this into =
a conservation debate (though I do think it something to keep in mind).  =
The main point I made was to use them and complete the needed =
documentation needed or decide to use them for something else.  Which is =
inline with you saying we should make decisions in a finite timescale =
rather than deferring decisions forever out.

Marla

-----Original Message-----
From: Joe Abley [mailto:jabley@ca.afilias.info]
Sent: Wednesday, July 11, 2007 10:01 AM
To: Azinger, Marla
Cc: michael.dillon@bt.com; ipv6@ietf.org
Subject: Re: [ppml] Why ULA-* will not harm the DFZ



On 11-Jul-2007, at 12:43, Azinger, Marla wrote:

> I am not surprised that conservation isn't the number one =20
> priority.  I just don't think its wise to ignore conservation.  We =20
> cant predict Ipv6 consumption and we don't even know what will =20
> exist for technology in the future that will require IP Addresses.

I think with 128 bits there's a middle ground between ruthless =20
conservation and "a /48 for every fridge"

But I guess my point was really that we shouldn't necessarily expect =20
to guess right first time, every time, and it's nice to have some =20
latitude to be able to make decisions in a finite timescale rather =20
than deferring decisions for ever out of fear that they might be wrong.


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 Jul 11 14:33: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 1I8gzz-0001nG-GS; Wed, 11 Jul 2007 14:33:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8gzy-0001n5-Fs
	for ipv6@ietf.org; Wed, 11 Jul 2007 14:33:14 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8gzt-0002PO-Uv
	for ipv6@ietf.org; Wed, 11 Jul 2007 14:33:14 -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 l6BIX7wm014699
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 11 Jul 2007 20:33:07 +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
	l6BIX6CV027679; Wed, 11 Jul 2007 20:33:06 +0200
Date: Wed, 11 Jul 2007 20:33:06 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Tony Hain <alh-ietf@tndh.net>
In-Reply-To: <072c01c7c3dd$122b6110$36822330$@net>
Message-ID: <Pine.LNX.4.64.0707112026200.9923@chandra.student.uit.no>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<28681.1184163817@sa.vix.com> <072c01c7c3dd$122b6110$36822330$@net>
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: 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

On Wed, 11 Jul 2007, Tony Hain wrote:
> I have a few points on Paul's draft:
<snip>
> Major complaint -  aggregation
> 	There needs to be at least a modest capability to aggregate. I
> understand the aversion to having these show up in the DFZ, but if 5.1 were
> really true that would not be an issue. The use case that needs to be
> supported is for internal aggregation of private peering clusters. Global
> organizations have many external relationships, but typically have them
> clustered in small groupings for logistics reasons. At the same time they
> don't necessarily want to carry the explicit routes for every organization
> throughout their internal network. If the ULA-C/G space has some modest
> aggregation  like sparse allocation of the RIR num block to allow clustering
> subsequent block to the same RIR and a suggestion for E-W-N-S regional
> management within the RIR space, then it would be possible to aggregate the
> internal routes to these private peering clusters.

IF we assume and prepare the ground for aggregation, would that just make 
it easier in the future for this type of addresses being leaked?

Anyway, 3.1 mention:
" Local Num  Identifiers assigned by an RIR (or LIR) for each /48 as
               allocated to an end site or user.  It is expected that
               allocations by an RIR to an LIR will be in blocks of 1000
               consecutive Local Nums, to amortize administrative workload."

which again give us some sort of aggregation... is this something we want? 
(althought it would fit us, where I work, perfectly since we would get 
almost all the space we need quite easy:-)

But then again 5.5 say it is recommanded to not allocate aligned blocks...

maybe clean up the wording on those part a bit?

<snip>

-- 

------------------------------
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 Jul 11 15:47: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 1I8i9i-0007bh-UH; Wed, 11 Jul 2007 15:47:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8i9h-0007bc-Tg
	for ipv6@ietf.org; Wed, 11 Jul 2007 15:47:21 -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 1I8i9d-0005p8-Fq
	for ipv6@ietf.org; Wed, 11 Jul 2007 15:47:21 -0400
Received: from mail.reprise.com (localhost [127.0.0.1])
	by reprise.com (8.13.8/8.13.8) with ESMTP id l6BJlFet092273
	for <ipv6@ietf.org>; Wed, 11 Jul 2007 12:47:16 -0700 (PDT)
Received: (from george@localhost)
	by mail.reprise.com (8.13.8/8.13.8/Submit) id l6BJlDfZ092269;
	Wed, 11 Jul 2007 12:47:13 -0700 (PDT) (envelope-from george)
Date: Wed, 11 Jul 2007 12:47:13 -0700 (PDT)
Message-Id: <200707111947.l6BJlDfZ092269@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: ea4ac80f790299f943f0a53be7e1a21a
Subject: RE: The purpose of ULA-G/C
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 to pick on James' post, but several have mentioned that
> large routing realms would be one reason to require ULA-G/C
> and it has not yet been suggested that the reverse DNS could
> itself be thought of as a "large routing realm" of sorts
> (depending on how applications use the information they find
> there). ULA-G/C would ideally allow collision-free population
> of the reverse DNS even with O(10^6) or more delegations.

Not to pick on Fred's post, but making local reverse DNS globally
accessible is not recommended.  It exposes information which is
better kept private.  Fred believes that it will make for
seamless integration when two organizations decide to merge their
local networks.  It would probably make the reverse DNS aspect of
such a merger more seamless, but it certainly won't make any
other aspect any easier.  Given that considerable planning will
go into all the other aspects of such a merger (securing the virtual
connections, bypassing just the right amount of firewalling,
provisioning backup links), the effort saved on making reverse DNS
work seems negligible.                       -- George Mitchell

> I can't comment [further] on Paul's proposal other than to say
> that *some* authority(s) needs to be responsible for the
> collision free delegations.

I still trust my computer's random number generator more than a
centrally-operated entity.                 -- 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 Wed Jul 11 15:53: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 1I8iG2-0007sZ-Ii; Wed, 11 Jul 2007 15:53:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8iG0-0007sL-Cz
	for ipv6@ietf.org; Wed, 11 Jul 2007 15:53:52 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8iFg-0007NV-R2
	for ipv6@ietf.org; Wed, 11 Jul 2007 15:53:52 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[192.168.1.103])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85987476; Wed, 11 Jul 2007 15:53:00 -0400
Message-ID: <4695350B.7090201@internap.com>
Date: Wed, 11 Jul 2007 12:52:43 -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: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>	<28681.1184163817@sa.vix.com>
	<072c01c7c3dd$122b6110$36822330$@net>
	<Pine.LNX.4.64.0707112026200.9923@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0707112026200.9923@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: a7d6aff76b15f3f56fcb94490e1052e4
Cc: ipv6@ietf.org, Tony Hain <alh-ietf@tndh.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>
Errors-To: ipv6-bounces@ietf.org

Roger Jorgensen wrote:
> On Wed, 11 Jul 2007, Tony Hain wrote:
>> I have a few points on Paul's draft:
> <snip>
>> Major complaint -  aggregation
>>     There needs to be at least a modest capability to aggregate. I
>> understand the aversion to having these show up in the DFZ, but if 
>> 5.1 were
>> really true that would not be an issue. The use case that needs to be
>> supported is for internal aggregation of private peering clusters. 
>> Global
>> organizations have many external relationships, but typically have them
>> clustered in small groupings for logistics reasons. At the same time 
>> they
>> don't necessarily want to carry the explicit routes for every 
>> organization
>> throughout their internal network. If the ULA-C/G space has some modest
>> aggregation  like sparse allocation of the RIR num block to allow 
>> clustering
>> subsequent block to the same RIR and a suggestion for E-W-N-S regional
>> management within the RIR space, then it would be possible to 
>> aggregate the
>> internal routes to these private peering clusters.
>
> IF we assume and prepare the ground for aggregation, would that just 
> make it easier in the future for this type of addresses being leaked?

<snip>

> which again give us some sort of aggregation... is this something we 
> want? (althought it would fit us, where I work, perfectly since we 
> would get almost all the space we need quite easy:-)

I would agree with Tony that aggregation of ULA-G space should be 
allowed.  I know there are many others who disagree, but IMO mutually 
assured destruction isn't called for here.  As long as we have an 
expectation that routes will be filtered, and have the ability to easily 
do so, I don't think it matters whether we have lots of non-aggregated 
routes or fewer aggregated ones...


-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 Jul 11 17: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 1I8jfQ-0001Eg-21; Wed, 11 Jul 2007 17:24:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8jfO-00016E-Hj
	for ipv6@ietf.org; Wed, 11 Jul 2007 17:24:10 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8jfO-00019z-9k
	for ipv6@ietf.org; Wed, 11 Jul 2007 17:24:10 -0400
Received: from [209.112.219.231] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10)
	with ESMTP-TLS id 85993201; Wed, 11 Jul 2007 17:23:45 -0400
Message-ID: <46953F44.8030009@internap.com>
Date: Wed, 11 Jul 2007 13:36:20 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: george+ipng@m5p.com
References: <200707111947.l6BJlDfZ092269@mail.reprise.com>
In-Reply-To: <200707111947.l6BJlDfZ092269@mail.reprise.com>
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: The purpose of ULA-G/C
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

george+ipng@m5p.com wrote:
>> Not to pick on James' post, but several have mentioned that
>> large routing realms would be one reason to require ULA-G/C
>> and it has not yet been suggested that the reverse DNS could
>> itself be thought of as a "large routing realm" of sorts
>> (depending on how applications use the information they find
>> there). ULA-G/C would ideally allow collision-free population
>> of the reverse DNS even with O(10^6) or more delegations.
>>     
>
> Not to pick on Fred's post, but making local reverse DNS globally
> accessible is not recommended.  It exposes information which is
> better kept private.  Fred believes that it will make for
> seamless integration when two organizations decide to merge their
> local networks.  It would probably make the reverse DNS aspect of
> such a merger more seamless, but it certainly won't make any
> other aspect any easier.  Given that considerable planning will
> go into all the other aspects of such a merger (securing the virtual
> connections, bypassing just the right amount of firewalling,
> provisioning backup links), the effort saved on making reverse DNS
> work seems negligible.                       -- George Mitchell
>   

So it sounds to me like this particular application, at least in your 
case, would be better served by ULA-L.  However, there are lots of other 
applications, that don't involve enterprise mergers, but private 
internetworking, that would benefit from the ability to get globally 
registered ULA-G space and delegate ip6.arpa DNS authority to globally 
reachable DNS servers.

> I still trust my computer's random number generator more than a
> centrally-operated entity.                 -- George Mitchell
>   

Then you definitely should stick with ULA-L, but I hope you won't deny 
others the opportunity to get globally registered private addresses for 
situations they consider appropriate.

-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 Jul 11 17:58: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 1I8kCc-0000Nf-Id; Wed, 11 Jul 2007 17:58:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8kCb-0000Ml-GW
	for ipv6@ietf.org; Wed, 11 Jul 2007 17:58:29 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8kCb-0001tW-6N
	for ipv6@ietf.org; Wed, 11 Jul 2007 17:58:29 -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 l6BLvuDw020494
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 11 Jul 2007 14:57:56 -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
	l6BLvtYN017776; Wed, 11 Jul 2007 14:57:55 -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
	l6BLvtYn017766; Wed, 11 Jul 2007 14:57:55 -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, 11 Jul 2007 14:57: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: Wed, 11 Jul 2007 14:57:53 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED8FF@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <46953F44.8030009@internap.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: The purpose of ULA-G/C
Thread-Index: AcfEAfst4v/u0McDR4SQoH7oQqUx3AAA24Ng
References: <200707111947.l6BJlDfZ092269@mail.reprise.com>
	<46953F44.8030009@internap.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Scott Leibrand" <sleibrand@internap.com>, <george+ipng@m5p.com>
X-OriginalArrivalTime: 11 Jul 2007 21:57:54.0450 (UTC)
	FILETIME=[88A1C720:01C7C406]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ipv6@ietf.org
Subject: RE: The purpose of ULA-G/C
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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: Wednesday, July 11, 2007 1:36 PM
> To: george+ipng@m5p.com
> Cc: ipv6@ietf.org
> Subject: Re: The purpose of ULA-G/C
>=20
> george+ipng@m5p.com wrote:
> >> Not to pick on James' post, but several have mentioned that
> >> large routing realms would be one reason to require ULA-G/C
> >> and it has not yet been suggested that the reverse DNS could
> >> itself be thought of as a "large routing realm" of sorts
> >> (depending on how applications use the information they find
> >> there). ULA-G/C would ideally allow collision-free population
> >> of the reverse DNS even with O(10^6) or more delegations.
> >>    =20
> >
> > Not to pick on Fred's post, but making local reverse DNS globally
> > accessible is not recommended.  It exposes information which is
> > better kept private.  Fred believes that it will make for
> > seamless integration when two organizations decide to merge their
> > local networks.  It would probably make the reverse DNS aspect of
> > such a merger more seamless, but it certainly won't make any
> > other aspect any easier.  Given that considerable planning will
> > go into all the other aspects of such a merger (securing the virtual
> > connections, bypassing just the right amount of firewalling,
> > provisioning backup links), the effort saved on making reverse DNS
> > work seems negligible.                       -- George Mitchell
> >  =20
>=20
> So it sounds to me like this particular application, at least in your=20
> case, would be better served by ULA-L.  However, there are=20
> lots of other=20
> applications, that don't involve enterprise mergers, but private=20
> internetworking, that would benefit from the ability to get globally=20
> registered ULA-G space and delegate ip6.arpa DNS authority to=20
> globally=20
> reachable DNS servers.

Not all "organizations" will be so difficult to merge as George
is describing. This depends entirely on what is your definition
of organization/enterprise/site, and is there a one-size-fits all?

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 Jul 12 04:05: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 1I8tfq-0001Lb-Oa; Thu, 12 Jul 2007 04:05:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8tfp-0001Iz-SW
	for ipv6@ietf.org; Thu, 12 Jul 2007 04:05:17 -0400
Received: from mu-out-0910.google.com ([209.85.134.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8tfl-0002ZE-D2
	for ipv6@ietf.org; Thu, 12 Jul 2007 04:05:17 -0400
Received: by mu-out-0910.google.com with SMTP id w8so83816mue
	for <ipv6@ietf.org>; Thu, 12 Jul 2007 01:05:12 -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=ifZFXLAOhEL8zMC4gKMw8EMwn9dR3m9mL60NeAvHVzainFyr42hba5DWBp70f/p6QBGtHIFehF1+GxjkNl1a9qHG46zuUFREbTsTOgK5UoAGkT709zqa+aHX6EsXfd/5fCAhP0w7+F9PS+Lg7C21W+mqcosmTVhUog0xmUK+250=
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=KI4PgwWyKNOuwjSuY+PEkstcUiPD36x81Nw3nT1BfAlE5oEpPRFlsdLM8+4vdDThr5X88cMavT/hoiR22Tx8PYbdfZ1DYXN/Mm69nDnlqzJOTkEVynlcqyoMKsqFfMXBYfEh9KDhA+tIS63LERddfDYQzw4lUvZX6kjPis3ztlw=
Received: by 10.82.111.8 with SMTP id j8mr164887buc.1184227512361;
	Thu, 12 Jul 2007 01:05:12 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1])
	by mx.google.com with ESMTP id 6sm4809189nfv.2007.07.12.01.05.10
	(version=SSLv3 cipher=RC4-MD5); Thu, 12 Jul 2007 01:05:11 -0700 (PDT)
Message-ID: <4695E0B9.2060300@gmail.com>
Date: Thu, 12 Jul 2007 10:05:13 +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: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>	<28681.1184163817@sa.vix.com>	<072c01c7c3dd$122b6110$36822330$@net>	<Pine.LNX.4.64.0707112026200.9923@chandra.student.uit.no>
	<4695350B.7090201@internap.com>
In-Reply-To: <4695350B.7090201@internap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ipv6@ietf.org, Tony Hain <alh-ietf@tndh.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>
Errors-To: ipv6-bounces@ietf.org

On 2007-07-11 21:52, Scott Leibrand wrote:
> Roger Jorgensen wrote:
>> On Wed, 11 Jul 2007, Tony Hain wrote:
>>> I have a few points on Paul's draft:
>> <snip>
>>> Major complaint -  aggregation
>>>     There needs to be at least a modest capability to aggregate. I
>>> understand the aversion to having these show up in the DFZ, but if 
>>> 5.1 were
>>> really true that would not be an issue. The use case that needs to be
>>> supported is for internal aggregation of private peering clusters. 
>>> Global
>>> organizations have many external relationships, but typically have them
>>> clustered in small groupings for logistics reasons. At the same time 
>>> they
>>> don't necessarily want to carry the explicit routes for every 
>>> organization
>>> throughout their internal network. If the ULA-C/G space has some modest
>>> aggregation  like sparse allocation of the RIR num block to allow 
>>> clustering
>>> subsequent block to the same RIR and a suggestion for E-W-N-S regional
>>> management within the RIR space, then it would be possible to 
>>> aggregate the
>>> internal routes to these private peering clusters.
>>
>> IF we assume and prepare the ground for aggregation, would that just 
>> make it easier in the future for this type of addresses being leaked?
> 
> <snip>
> 
>> which again give us some sort of aggregation... is this something we 
>> want? (althought it would fit us, where I work, perfectly since we 
>> would get almost all the space we need quite easy:-)
> 
> I would agree with Tony that aggregation of ULA-G space should be 
> allowed.  I know there are many others who disagree, but IMO mutually 
> assured destruction isn't called for here.  As long as we have an 
> expectation that routes will be filtered, and have the ability to easily 
> do so, I don't think it matters whether we have lots of non-aggregated 
> routes or fewer aggregated ones...

I'd also add a heretical comment: if they agggregate, it doesn't *matter*
if they leak. In fact, they *will* leak up to the point where they
hit a shorter filter. That's physics.

    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 Jul 12 05:26: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 1I8uvg-0004Io-Re; Thu, 12 Jul 2007 05:25:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8uvf-0004Cc-6D
	for ipv6@ietf.org; Thu, 12 Jul 2007 05:25:43 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I8uvb-0004QA-Sr
	for ipv6@ietf.org; Thu, 12 Jul 2007 05:25:43 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-6.tower-119.messagelabs.com!1184232338!14073793!1
X-StarScan-Version: 5.5.12.11; banners=.,-,-
X-Originating-IP: [144.189.100.103]
Received: (qmail 20195 invoked from network); 12 Jul 2007 09:25:39 -0000
Received: from motgate3.mot.com (HELO motgate3.mot.com) (144.189.100.103)
	by server-6.tower-119.messagelabs.com with SMTP;
	12 Jul 2007 09:25:39 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id l6C9PcAX016518;
	Thu, 12 Jul 2007 02:25:38 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id l6C9PbCJ000568;
	Thu, 12 Jul 2007 04:25:38 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l6C9PYrC000358;
	Thu, 12 Jul 2007 04:25:35 -0500 (CDT)
Message-ID: <4695F388.7080603@gmail.com>
Date: Thu, 12 Jul 2007 11:25:28 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <4694F752.8090406@ericsson.com>
In-Reply-To: <4694F752.8090406@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000755-1, 11/07/2007), Outbound message
X-Antivirus-Status: Clean
X-Vontu: Pass
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: Ipv <ipv6@ietf.org>
Subject: Re: [netlmm] [Fwd: WGLC for draft-ietf-dna-protocol-06.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

Suresh Krishnan wrote:
> Hi Folks, We would like to hear your comments on this document as
> well. This document is a significant update to ipv6 neighbor
> discovery and we would like some more eyeballs. Please spare some
> time from your busy schedule to give it a look.

Really this should be targeted WG to WG, not such large set of contexts...

I reply to IPv6 list only, for an IPv6-only aspect:

Encoding options in the RA seems to be incosistent with ND Proxy flag P
of RFC4389 (DNA spec uses flag 'D' DNAAware at 'P' place):

DNA draft:
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>     | Cur Hop Limit |M|O|H|Pr |D|C|R|       Router Lifetime         |
>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

RA flags option draft:
>    +-+-+-+-+-+-+-+-+
>    |M|O|H|Prf|P|R|R|
>    +-+-+-+-+-+-+-+-+

Alex

> 
> Thanks
> Suresh
> 
> -------- Original Message --------
> Subject: WGLC for draft-ietf-dna-protocol-06.txt
> Date: Wed, 04 Jul 2007 15:47:24 -0400
> From: Suresh Krishnan <suresh.krishnan@ericsson.com>
> To: Dna <dna@eng.monash.edu.au>
> CC: Greg Daley <Greg.Daley@eng.monash.edu.au>,  Jari Arkko 
> <jari.arkko@piuha.net>
> 
> This mail starts a 2 week working group Last Call for comments for the
> following dna working group document
> 
> draft-ietf-dna-protocol-06.txt
> 
> to be sent to the IESG for consideration as a Standards Track RFC.
> 
> Please review the document carefully, and send your feedback to the
> list. Please also indicate whether or not you believe that this
> document is ready to go to the IESG.
> 
> The last call will end on 2007/07/18.
> 
> Cheers
> Suresh & Greg
> 
> 
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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



From ipv6-bounces@ietf.org Thu Jul 12 10:35: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 1I8zl8-0006Mk-6Y; Thu, 12 Jul 2007 10:35:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8zl6-0006LC-18
	for ipv6@ietf.org; Thu, 12 Jul 2007 10:35:08 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8zl4-0004Ne-P1
	for ipv6@ietf.org; Thu, 12 Jul 2007 10:35:08 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 0A87C11425
	for <ipv6@ietf.org>; Thu, 12 Jul 2007 14:35:04 +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, 12 Jul 2007 10:05:13 +0200."
	<4695E0B9.2060300@gmail.com> 
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<28681.1184163817@sa.vix.com> <072c01c7c3dd$122b6110$36822330$@net>
	<Pine.LNX.4.64.0707112026200.9923@chandra.student.uit.no>
	<4695350B.7090201@internap.com> <4695E0B9.2060300@gmail.com> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Thu, 12 Jul 2007 14:35:04 +0000
Message-ID: <80775.1184250904@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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

> >> which again give us some sort of aggregation... is this something we
> >> want? (althought it would fit us, where I work, perfectly since we would
> >> get almost all the space we need quite easy:-)

> > I would agree with Tony that aggregation of ULA-G space should be allowed.
> > I know there are many others who disagree, but IMO mutually assured
> > destruction isn't called for here.  As long as we have an expectation that
> > routes will be filtered, and have the ability to easily do so, I don't
> > think it matters whether we have lots of non-aggregated routes or fewer
> > aggregated ones...

> I'd also add a heretical comment: if they agggregate, it doesn't *matter* if
> they leak. In fact, they *will* leak up to the point where they hit a
> shorter filter. That's physics.

ok, intentional unaggregatability is out.

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



From ipv6-bounces@ietf.org Thu Jul 12 11:30: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 1I90cF-0000T7-BF; Thu, 12 Jul 2007 11:30:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I90cD-0000Sb-Ks
	for ipv6@ietf.org; Thu, 12 Jul 2007 11:30:01 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I90c9-00063C-2l
	for ipv6@ietf.org; Thu, 12 Jul 2007 11:30:01 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l6CFY2cq002642;
	Thu, 12 Jul 2007 10:34:02 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 10:29:55 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 12 Jul 2007 10:29:55 -0500
Message-ID: <46964909.2050603@ericsson.com>
Date: Thu, 12 Jul 2007 11:30:17 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <4694F752.8090406@ericsson.com> <4695F388.7080603@gmail.com>
In-Reply-To: <4695F388.7080603@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jul 2007 15:29:55.0611 (UTC)
	FILETIME=[7FC696B0:01C7C499]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: Ipv <ipv6@ietf.org>
Subject: Re: [netlmm] [Fwd: WGLC for draft-ietf-dna-protocol-06.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 Alex,
   Thanks for the review. We are aware of this issue and have already 
noted this. I would like to wait until the document progresses to make 
sure that there is no flag conflict.

I had raised the issue after the 66th IETF with the IPv6 chairs as noted 
in the dna minutes

http://www3.ietf.org/proceedings/06jul/minutes/dna.txt

and requested allocation of the last 2 bits in this mail to the IPv6 
mailing list.

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

If we manage to get the two bits allocated, we will go ahead and make 
the edit you suggested. But if some other spec manages to grab those 
bits we may need to rewrite the proposal with the RA flags option instead.

Cheers
Suresh

Alexandru Petrescu wrote:
> Suresh Krishnan wrote:
>> Hi Folks, We would like to hear your comments on this document as
>> well. This document is a significant update to ipv6 neighbor
>> discovery and we would like some more eyeballs. Please spare some
>> time from your busy schedule to give it a look.
> 
> Really this should be targeted WG to WG, not such large set of contexts...
> 
> I reply to IPv6 list only, for an IPv6-only aspect:
> 
> Encoding options in the RA seems to be incosistent with ND Proxy flag P
> of RFC4389 (DNA spec uses flag 'D' DNAAware at 'P' place):
> 
> DNA draft:
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>     | Cur Hop Limit |M|O|H|Pr |D|C|R|       Router Lifetime         |
>>     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> RA flags option draft:
>>    +-+-+-+-+-+-+-+-+
>>    |M|O|H|Prf|P|R|R|
>>    +-+-+-+-+-+-+-+-+
> 
> Alex
> 
>>
>> Thanks
>> Suresh
>>
>> -------- Original Message --------
>> Subject: WGLC for draft-ietf-dna-protocol-06.txt
>> Date: Wed, 04 Jul 2007 15:47:24 -0400
>> From: Suresh Krishnan <suresh.krishnan@ericsson.com>
>> To: Dna <dna@eng.monash.edu.au>
>> CC: Greg Daley <Greg.Daley@eng.monash.edu.au>,  Jari Arkko 
>> <jari.arkko@piuha.net>
>>
>> This mail starts a 2 week working group Last Call for comments for the
>> following dna working group document
>>
>> draft-ietf-dna-protocol-06.txt
>>
>> to be sent to the IESG for consideration as a Standards Track RFC.
>>
>> Please review the document carefully, and send your feedback to the
>> list. Please also indicate whether or not you believe that this
>> document is ready to go to the IESG.
>>
>> The last call will end on 2007/07/18.
>>
>> Cheers
>> Suresh & Greg
>>
>>
>> _______________________________________________
>> netlmm mailing list
>> netlmm@ietf.org
>> https://www1.ietf.org/mailman/listinfo/netlmm
>>
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________


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



From ipv6-bounces@ietf.org Thu Jul 12 14:02: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 1I92zT-0004Vs-Pe; Thu, 12 Jul 2007 14:02:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I92zS-0004Vm-83
	for ipv6@ietf.org; Thu, 12 Jul 2007 14:02:10 -0400
Received: from adsl-65-67-187-82.dsl.rcsntx.swbell.net ([65.67.187.82]
	helo=defiant.dfw.nostrum.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I92zJ-0007AH-P7
	for ipv6@ietf.org; Thu, 12 Jul 2007 14:02:10 -0400
Received: from ssprunkxp (localhost [127.0.0.1])
	by defiant.dfw.nostrum.com (8.13.8/8.13.8/Debian-3) with SMTP id
	l6CHwnXl031619; Thu, 12 Jul 2007 12:59:49 -0500
Message-ID: <00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: <michael.dillon@bt.com>, <ipv6@ietf.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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
Date: Thu, 12 Jul 2007 12:41:32 -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-Virus-Scanned: ClamAV 0.90.2/3648/Thu Jul 12 11:59:27 2007 on
	defiant.dfw.nostrum.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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

Thus spake <michael.dillon@bt.com>
>> 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)
>
> Where has the IETF redefined the meaning of the word "site"?
> In plain English, this word refers to a distinct physical location such
> as an office or building or campus.

This has been a longstanding problem in the IETF; in fact, the inability to 
agree on what "site" means was one of the reasons SLAs were deprecated.  The 
word "site" is often abused to mean "administrative domain" rather than 
"physical location" due to the ISP-centric nature of the IETF and RIRs. 
It's virtually impossible to tell, in any particular context, which meaning 
an author meant.  We need to stop using the word entirely...

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 Fri Jul 13 06: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 1I9I1h-00063C-2Y; Fri, 13 Jul 2007 06:05:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9I1f-000632-3E
	for ipv6@ietf.org; Fri, 13 Jul 2007 06:05:27 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9I1P-0003wj-JX
	for ipv6@ietf.org; Fri, 13 Jul 2007 06:05:27 -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 l6DA4GDN039613
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 13 Jul 2007 12:04:16 +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
	l6DA4FX7020681; Fri, 13 Jul 2007 12:04:16 +0200
Date: Fri, 13 Jul 2007 12:04:16 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
Message-ID: <Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.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: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org, roger@jorgensen.no
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 Thu, 12 Jul 2007, Stephen Sprunk wrote:
> Thus spake <michael.dillon@bt.com>
>>> 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)
>> 
>> Where has the IETF redefined the meaning of the word "site"?
>> In plain English, this word refers to a distinct physical location such
>> as an office or building or campus.
>
> This has been a longstanding problem in the IETF; in fact, the inability to 
> agree on what "site" means was one of the reasons SLAs were deprecated.  The 
> word "site" is often abused to mean "administrative domain" rather than 
> "physical location" due to the ISP-centric nature of the IETF and RIRs. It's 
> virtually impossible to tell, in any particular context, which meaning an 
> author meant.  We need to stop using the word entirely...

why does it mather if it is physical site, administrative domain (eh how 
can anyone interprent that as a site?!) or a room, company etc... why not 
leave that upto those that try to use 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 Jul 13 10:26: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 1I9M4r-0001Cl-9f; Fri, 13 Jul 2007 10:25:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9M4p-0001C0-3g
	for ipv6@ietf.org; Fri, 13 Jul 2007 10:24:59 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9M4n-0000iY-S3
	for ipv6@ietf.org; Fri, 13 Jul 2007 10:24:59 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id DC5FA11433
	for <ipv6@ietf.org>; Fri, 13 Jul 2007 14:24:56 +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, 13 Jul 2007 12:04:16 +0200."
	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no> 
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Fri, 13 Jul 2007 14:24:56 +0000
Message-ID: <7913.1184336696@sa.vix.com>
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
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 site is a network of computers with a single administration, ...

> >> Where has the IETF redefined the meaning of the word "site"? ...

> > This has been a longstanding problem in the IETF; in fact, the inability
> > to agree on what "site" means was one of the reasons SLAs were ...

> why does it mather if it is physical site, administrative domain ...

indeed, from the rfc that was quoted at me when i asked about this a month
ago, it appears that "site" is meant as "usually the same thing as an
autonomous system but can mean something else if you want it to."

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



From ipv6-bounces@ietf.org Fri Jul 13 10:41: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 1I9MKX-0007Ba-8u; Fri, 13 Jul 2007 10:41:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9MKW-0007BD-8v
	for ipv6@ietf.org; Fri, 13 Jul 2007 10:41:12 -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 1I9MKR-0001O9-Fa
	for ipv6@ietf.org; Fri, 13 Jul 2007 10:41:12 -0400
Received: from [87.198.21.26] (87-198-21-26.ptr.magnet.ie [87.198.21.26])
	(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 4CE7A140C0F4;
	Fri, 13 Jul 2007 16:41:06 +0200 (CEST)
Message-ID: <46978F00.5020106@spaghetti.zurich.ibm.com>
Date: Fri, 13 Jul 2007 15:41:04 +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: <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>	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
	<7913.1184336696@sa.vix.com>
In-Reply-To: <7913.1184336696@sa.vix.com>
X-Enigmail-Version: 0.95.2
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: 4b800b1eab964a31702fa68f1ff0e955
Cc: IETF Ops <v6ops@ops.ietf.org>, ipv6@ietf.org
Subject: What is a site (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="===============0488184182=="
Errors-To: ipv6-bounces@ietf.org

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

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

[cross cc'd to v6ops as this sounds more like a ops thing]

Paul Vixie wrote:
>>>>> A site is a network of computers with a single administration, ...
>=20
>>>> Where has the IETF redefined the meaning of the word "site"? ...
>=20
>>> This has been a longstanding problem in the IETF; in fact, the inabil=
ity
>>> to agree on what "site" means was one of the reasons SLAs were ...
>=20
>> why does it mather if it is physical site, administrative domain ...
>=20
> indeed, from the rfc that was quoted at me when i asked about this a mo=
nth
> ago, it appears that "site" is meant as "usually the same thing as an
> autonomous system but can mean something else if you want it to."

=46rom what I understand at least RIPE NCC is using the meaning along the=

lines of "A network with the same administrative domain confined to a
single or a group of buildings".

As such a site could be (amongst others):
 - a host in a datacenter which provides VPN's to other sites
   over its own link.
 - a home network, eg where a DSL or cable line or a PPP link terminates
 - an office in a home network where a VPN/PPP/DSL terminates
 - a big office complex, where the network is run by an admin group
   who have an incoming 1Gbit/s link
 - multiple buildings around a city/country/world all linked
   together with VPN using one single /48, but eg a /56 per building.

And various other cases. Note that I add the way the network gets
connected to the rest of the world. Of course there are cases where one
does not link up to the Internet or even to other sites.

I am pretty sure that the various RIR's are well known enough with a
definition that they handle consistently in their region, which in one
way or the other most likely matches the above.

Maybe somebody should write a mini-RFC labeled "What is a site" and
include some examples to show exactly how/what? Guess it would fit in
perfectly for the v6ops WG (cross cc'd for that purpose).

Greets,
 Jeroen


--------------enig894ADD525C2F4ED97328EE9C
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/

iHUEARECADUFAkaXjwMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I6MEAJwJB8JZkDmQTt3VveZxjOVRO3XB
rgCeMvz37LqYsy8b/etN6zSzOrg7HI0=
=/dL4
-----END PGP SIGNATURE-----

--------------enig894ADD525C2F4ED97328EE9C--


--===============0488184182==
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
--------------------------------------------------------------------

--===============0488184182==--




From ipv6-bounces@ietf.org Fri Jul 13 11:21: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 1I9Mx2-0003bx-Kv; Fri, 13 Jul 2007 11:21:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9Mx1-0003bs-CL
	for ipv6@ietf.org; Fri, 13 Jul 2007 11:20:59 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9Mx1-0005hU-2w
	for ipv6@ietf.org; Fri, 13 Jul 2007 11:20:59 -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 l6DFKoFQ024123
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 13 Jul 2007 10:20:50 -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
	l6DFKn9B028403; Fri, 13 Jul 2007 10:20:49 -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
	l6DFKns3028384; Fri, 13 Jul 2007 10:20:49 -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, 13 Jul 2007 08:20:47 -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, 13 Jul 2007 08:19:53 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED909@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <46978F00.5020106@spaghetti.zurich.ibm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: What is a site (Re: draft-ietf-ipv6-ula-central-02.txt)
Thread-Index: AcfFW/+XjZnDXaUUT9qWKXDuHYr5mgABLufw
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>	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no><7913.1184336696@sa.vix.com>
	<46978F00.5020106@spaghetti.zurich.ibm.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Jeroen Massar" <jeroen@unfix.org>, "Paul Vixie" <paul@vix.com>
X-OriginalArrivalTime: 13 Jul 2007 15:20:47.0537 (UTC)
	FILETIME=[6382E210:01C7C561]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: IETF Ops <v6ops@ops.ietf.org>, ipv6@ietf.org
Subject: RE: What is a site (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

In 'draft-templin-autoconf-dhcp-08.txt', I define site as:

   "Mobile Ad-hoc Network (MANET)
      a connected network region of MANET routers that maintain a
      routing structure among themselves over MANET interfaces.  A MANET
      may be as large as an Autonomous System (AS) or as small as a
      single MANET router, and may also be a subnetwork of a larger
      MANET.  A MANET router (and its attached networks) is a "site"
      unto itself, and a MANET is therefore a "site-of-sites".  (Note
      that this document considers the terms "MANET" and "site" as
      functional equivalents.)"

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

> -----Original Message-----
> From: Jeroen Massar [mailto:jeroen@unfix.org]=20
> Sent: Friday, July 13, 2007 7:41 AM
> To: Paul Vixie
> Cc: IETF Ops; ipv6@ietf.org
> Subject: What is a site (Re: draft-ietf-ipv6-ula-central-02.txt)
>=20
> [cross cc'd to v6ops as this sounds more like a ops thing]
>=20
> Paul Vixie wrote:
> >>>>> A site is a network of computers with a single=20
> administration, ...
> >=20
> >>>> Where has the IETF redefined the meaning of the word "site"? ...
> >=20
> >>> This has been a longstanding problem in the IETF; in=20
> fact, the inability
> >>> to agree on what "site" means was one of the reasons SLAs were ...
> >=20
> >> why does it mather if it is physical site, administrative=20
> domain ...
> >=20
> > indeed, from the rfc that was quoted at me when i asked=20
> about this a month
> > ago, it appears that "site" is meant as "usually the same=20
> thing as an
> > autonomous system but can mean something else if you want it to."
>=20
> From what I understand at least RIPE NCC is using the meaning=20
> along the
> lines of "A network with the same administrative domain confined to a
> single or a group of buildings".
>=20
> As such a site could be (amongst others):
>  - a host in a datacenter which provides VPN's to other sites
>    over its own link.
>  - a home network, eg where a DSL or cable line or a PPP link=20
> terminates
>  - an office in a home network where a VPN/PPP/DSL terminates
>  - a big office complex, where the network is run by an admin group
>    who have an incoming 1Gbit/s link
>  - multiple buildings around a city/country/world all linked
>    together with VPN using one single /48, but eg a /56 per building.
>=20
> And various other cases. Note that I add the way the network gets
> connected to the rest of the world. Of course there are cases=20
> where one
> does not link up to the Internet or even to other sites.
>=20
> I am pretty sure that the various RIR's are well known enough with a
> definition that they handle consistently in their region, which in one
> way or the other most likely matches the above.
>=20
> Maybe somebody should write a mini-RFC labeled "What is a site" and
> include some examples to show exactly how/what? Guess it would fit in
> perfectly for the v6ops WG (cross cc'd for that purpose).
>=20
> Greets,
>  Jeroen
>=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 Jul 13 12:33: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 1I9O4I-00024q-2V; Fri, 13 Jul 2007 12:32:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9O4G-00024k-PE
	for ipv6@ietf.org; Fri, 13 Jul 2007 12:32:32 -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 1I9O4C-0005v1-Cs
	for ipv6@ietf.org; Fri, 13 Jul 2007 12:32:32 -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 l6DGWPVB008035;
	Fri, 13 Jul 2007 09:32:27 -0700
Message-ID: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.no>
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
Date: Fri, 13 Jul 2007 11:16:58 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ipv6@ietf.org, roger@jorgensen.no
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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Thu, 12 Jul 2007, Stephen Sprunk wrote:
>> This has been a longstanding problem in the IETF; in fact,
>> the inability to agree on what "site" means was one of the
>> reasons SLAs were deprecated.  The word "site" is often
>> abused to mean "administrative domain" rather than "physical location" 
>> due to the ISP-centric nature of the IETF
>> and RIRs. It's virtually impossible to tell, in any particular
>> context, which meaning an author meant.  We need to stop
>> using the word entirely...
>
> why does it mather if it is physical site, administrative domain
> (eh how can anyone interprent that as a site?!) or a room,
> company etc... why not leave that upto those that try to use it?

It matters because there are a lot of protocol and policy documents that 
refer to "sites".  For instance, one of the current qualifications for 
getting an IPv6 LIR allocation require that one have a plan to make 
assignments to 200 "sites".  Obviously the meaning of that is significantly 
changed depending on whether you consider a single company with 200+ 
locations sharing a single uplink to be one "site" or 200+ "sites".

Also, in the case of SLAs, the utility of the addresses is impacted greatly 
by whether you consider a "site" to be a single administrative domain, where 
there would not be internal collisions, vs. considering each distinct 
location to be a "site", which could lead to hundreds or thousands of 
internal collisions.

As far as why "site" has been abused to mean "administrative domain", that 
comes from the IETF and RIRs being very ISP-centric, as I said; a single 
downstream connection denotes a single "site" regardless of how complex the 
internal network behind it is or how many other locations it serves.  Or 
maybe it doesn't, depending on who's talking; that's the problem.

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 Fri Jul 13 15:28: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 1I9QkU-0002uy-Or; Fri, 13 Jul 2007 15:24:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9QkT-0002un-0S
	for ipv6@ietf.org; Fri, 13 Jul 2007 15:24:17 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I9QkO-0004Fg-Dd
	for ipv6@ietf.org; Fri, 13 Jul 2007 15: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 l6DJO6I9003377
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 13 Jul 2007 21:24: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
	l6DJO6As013846; Fri, 13 Jul 2007 21:24:06 +0200
Date: Fri, 13 Jul 2007 21:24:05 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Stephen Sprunk <stephen@sprunk.org>
In-Reply-To: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
Message-ID: <Pine.LNX.4.64.0707132020150.9923@chandra.student.uit.no>
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
	<016101c7c56b$5b16ec70$373816ac@atlanta.polycom.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: fb6060cb60c0cea16e3f7219e40a0a81
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, 13 Jul 2007, Stephen Sprunk wrote:
> Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
>> On Thu, 12 Jul 2007, Stephen Sprunk wrote:
>>> This has been a longstanding problem in the IETF; in fact,
>>> the inability to agree on what "site" means was one of the
>>> reasons SLAs were deprecated.  The word "site" is often
>>> abused to mean "administrative domain" rather than "physical location" due 
>>> to the ISP-centric nature of the IETF
>>> and RIRs. It's virtually impossible to tell, in any particular
>>> context, which meaning an author meant.  We need to stop
>>> using the word entirely...
>> why does it mather if it is physical site, administrative domain
>> (eh how can anyone interprent that as a site?!) or a room,
>> company etc... why not leave that upto those that try to use it?
> It matters because there are a lot of protocol and policy documents that 
> refer to "sites".  For instance, one of the current qualifications for 
> getting an IPv6 LIR allocation require that one have a plan to make 
> assignments to 200 "sites".  Obviously the meaning of that is significantly 
> changed depending on whether you consider a single company with 200+ 
> locations sharing a single uplink to be one "site" or 200+ "sites".

if you refair to RIPEs policy it has just been changed,
"Consensus has been reached on the proposal described in 2006-02 and
it is accepted by the RIPE community.

This proposal is to change the IPv6 Initial Allocation criteria and
the End Site definition in the "IPv6 Address Allocation and
Assignment Policy".

You can find the full proposal at:

    http://www.ripe.net/ripe/policies/proposals/2006-02.html
"


> Also, in the case of SLAs, the utility of the addresses is impacted greatly 
> by whether you consider a "site" to be a single administrative domain, where 
> there would not be internal collisions, vs. considering each distinct 
> location to be a "site", which could lead to hundreds or thousands of 
> internal collisions.

I can not see how SLAs are any of this wg's business, or ietfs businness. 
thought SLA was something for the laywers that write the contracts 
governing any SLAs to fight out between them?


> As far as why "site" has been abused to mean "administrative domain", that 
> comes from the IETF and RIRs being very ISP-centric, as I said; a single 
> downstream connection denotes a single "site" regardless of how complex the 
> internal network behind it is or how many other locations it serves.  Or 
> maybe it doesn't, depending on who's talking; that's the problem.

that downstream connection is ONE site for the upstream provider, will 
probably never be anything else. Why should it be anything else really? If 
the same "site" bought two connection to an ISP on different location they 
would still be one huge site, with several internal parts, two that the 
ISP need to know about.

What I'm not sure you realize is that the moment anyone define a site to 
be something very specific... there will come alot of exceptions to that 
list, not to forget discussion on how to interprent whats written there. 
It is way easier to say site and leave it with that... and maybe, just 
maybe list a few examples and leave it upto those that have to use the 
word site to agree between them.



-- 

------------------------------
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 Jul 13 15:28: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 1I9QnY-0008Ar-Ev; Fri, 13 Jul 2007 15:27:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9QnW-00081x-SN
	for ipv6@ietf.org; Fri, 13 Jul 2007 15:27:26 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9QnW-0006KQ-Hc
	for ipv6@ietf.org; Fri, 13 Jul 2007 15:27:26 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.115]) by
	smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 13 Jul 2007 20:27: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: Fri, 13 Jul 2007 20:28:32 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0AF5F95@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfFa5SIVa8xOgSiRpSMTpgkDU1WJwAFVHGA
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><D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net><00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com><Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
	<016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 13 Jul 2007 19:27:01.0307 (UTC)
	FILETIME=[C95D48B0:01C7C583]
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

> As far as why "site" has been abused to mean "administrative=20
> domain", that comes from the IETF and RIRs being very=20
> ISP-centric, as I said; a single downstream connection=20
> denotes a single "site" regardless of how complex the=20
> internal network behind it is or how many other locations it=20
> serves.  Or maybe it doesn't, depending on who's talking;=20
> that's the problem.

I have always believed that the definition of a site in IPv6 is tied in
with the idea that if every "site" has a /48 subnet assignment, then
migration to a different provider only requires changing the prefix
bits. The existing subnet topology hidden inside the /48 remains
unchanged.

By this definition an apartment or family home is a site. An office in
big buidling is a site. A company building is a site. A campus-like
collection of buildings is a site. Here is where definitions need to be
precise and relate back to original goals.

A single company may own several buildings and those buildings may be
next to each other. I believe that each separate building should be
considered to be a site. A campus is more than a collection of buildings
because it is difficult, or impossible to separate one building from the
group. On a campus there is centralization of utilities, even going so
far as to connect all buildings by tunnel systems and heat all buildings
via hot water from a central steam plant.

Why is the definition of a site so important? Because a "site" is
mobile. It can change providers and it can change ownership indpendent
of neighboring sites. By that definition, airplanes, trucks and train
carriages are also sites. They are just mobile more frequently than
sites in buildings.

I think it is important for the IETF to have clear documentation of the
interconnectedness of "sites", /48 prefixes, mobility, and freedom of
choice.

At least one RIR now allows ISPs to assign shorter /56 prefixes to
consumer sites, i.e. family homes and apartments. This is not
necessarily a bad thing since it is rare for a family home to turn into
an office without significant infrastructure change. But if there is to
be a special size for the family home, it too should be the same
worldwide. And it too should be documented by the IETF.

--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 Sat Jul 14 11:29: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 1I9jXm-0000ed-DG; Sat, 14 Jul 2007 11:28:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I9jXl-0000eN-2k
	for ipv6@ietf.org; Sat, 14 Jul 2007 11:28:25 -0400
Received: from ns2.sea.ygnition.net ([66.135.144.2] helo=ns2.ygnition.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I9jXV-0003kB-MT
	for ipv6@ietf.org; Sat, 14 Jul 2007 11:28:25 -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 l6EFRYmj010833;
	Sat, 14 Jul 2007 08:27:36 -0700
Message-ID: <00a501c7c62b$76a61e00$6401a8c0@atlanta.polycom.com>
From: "Stephen Sprunk" <stephen@sprunk.org>
To: "Roger Jorgensen" <rogerj@jorgensen.no>
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>
	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>
	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>
	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
	<016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
	<Pine.LNX.4.64.0707132020150.9923@chandra.student.uit.no>
Date: Sat, 14 Jul 2007 10:18:35 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
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.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

Thus spake "Roger Jorgensen" <rogerj@jorgensen.no>
> On Fri, 13 Jul 2007, Stephen Sprunk wrote:
>> Also, in the case of SLAs, the utility of the addresses is
>> impacted greatly by whether you consider a "site" to be a
>> single administrative domain, where there would not be
>> internal collisions, vs. considering each distinct location
>> to be a "site", which could lead to hundreds or thousands
>> of internal collisions.
>
> I can not see how SLAs are any of this wg's business, or ietfs
> businness.  thought SLA was something for the laywers that
> write the contracts governing any SLAs to fight out between
> them?

Site-Local Addresses, the predecessor to Unique Local Addresses.

>> As far as why "site" has been abused to mean "administrative
>> domain", that comes from the IETF and RIRs being very ISP-
>> centric, as I said; a single downstream connection denotes a
>> single "site" regardless of how complex the internal network
>> behind it is or how many other locations it serves.  Or maybe
>> it doesn't, depending on who's talking; that's the problem.
>
> that downstream connection is ONE site for the upstream
> provider, will probably never be anything else. Why should it
> be anything else really? If the same "site" bought two
> connection to an ISP on different location they would still be
> one huge site, with several internal parts, two that the ISP need to know 
> about.

No, that's one interpretation of the word.  Others (notably the person I was 
responding to) consider every physical location to be a "site" even if a 
large set of locations all share a single internal network and single 
uplink.

> What I'm not sure you realize is that the moment anyone define
> a site to be something very specific... there will come alot of
> exceptions to that list, not to forget discussion on how to
> interprent whats written there.

We already have extensive disagreement on interpretation due to lack of any 
agreed-upon definition.

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 Sat Jul 14 20: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 1I9rWw-0001Wv-G5; Sat, 14 Jul 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 1I9rWv-0001Pl-73
	for ipv6@ietf.org; Sat, 14 Jul 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 1I9rWu-0008QZ-PE
	for ipv6@ietf.org; Sat, 14 Jul 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 2D20128465
	for <ipv6@ietf.org>; Sun, 15 Jul 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 15 Jul 2007 00:00:04 +0000
Message-Id: <20070715000004.2D20128465@cyteen.hactrn.net>
X-Spam-Score: -0.9 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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
--------+------+--------+----------+------------------------
  9.60% |   12 |  9.08% |    78113 | rogerj@jorgensen.no
  6.40% |    8 | 10.89% |    93668 | shemant@cisco.com
  8.80% |   11 |  7.61% |    65462 | stephen@sprunk.org
  8.80% |   11 |  5.56% |    47836 | paul@vix.com
  6.40% |    8 |  7.89% |    67876 | jeroen@unfix.org
  4.80% |    6 |  4.83% |    41523 | sleibrand@internap.com
  4.80% |    6 |  4.42% |    37968 | jinmei@isl.rdc.toshiba.co.jp
  4.80% |    6 |  3.69% |    31750 | michael.dillon@bt.com
  4.00% |    5 |  3.66% |    31456 | jhw@apple.com
  3.20% |    4 |  4.01% |    34444 | james.d.carlson@sun.com
  4.00% |    5 |  3.17% |    27236 | heldal@eml.cc
  3.20% |    4 |  3.95% |    34007 | brian.e.carpenter@gmail.com
  2.40% |    3 |  3.55% |    30552 | jordi.palet@consulintel.es
  2.40% |    3 |  3.35% |    28777 | mark_andrews@isc.org
  3.20% |    4 |  2.44% |    21009 | marla.azinger@frontiercorp.com
  2.40% |    3 |  2.80% |    24041 | alh-ietf@tndh.net
  2.40% |    3 |  2.72% |    23366 | vladislav.yasevich@hp.com
  2.40% |    3 |  2.33% |    20050 | fred.l.templin@boeing.com
  2.40% |    3 |  2.09% |    18014 | suresh.krishnan@ericsson.com
  2.40% |    3 |  2.05% |    17634 | lear@cisco.com
  1.60% |    2 |  2.65% |    22807 | briand@ca.afilias.info
  2.40% |    3 |  1.52% |    13035 | jabley@ca.afilias.info
  1.60% |    2 |  1.43% |    12304 | billf@mu.org
  1.60% |    2 |  1.11% |     9580 | ipng@69706e6720323030352d30312d31340a.nosense.org
  0.80% |    1 |  0.74% |     6335 | kkargel@polartel.com
  0.80% |    1 |  0.72% |     6217 | alexandru.petrescu@gmail.com
  0.80% |    1 |  0.63% |     5407 | sra+ipng@hactrn.net
  0.80% |    1 |  0.56% |     4789 | perry@coders.net
  0.80% |    1 |  0.54% |     4673 | george+ipng@m5p.com
--------+------+--------+----------+------------------------
100.00% |  125 |100.00% |   859929 | 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 Jul 16 03:54: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 1IALOl-0002FP-Qj; Mon, 16 Jul 2007 03:53:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IALOk-0002FE-9X
	for ipv6@ietf.org; Mon, 16 Jul 2007 03:53:38 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IALOf-0001cu-V3
	for ipv6@ietf.org; Mon, 16 Jul 2007 03:53:38 -0400
Received: by ug-out-1314.google.com with SMTP id u2so2578462uge
	for <ipv6@ietf.org>; Mon, 16 Jul 2007 00:53: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:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=CUoXUhV23zdCa/1rIZ3Wjrss8J9JeCtRi0DlVlurXWmhFPA65yAKdeLOUNeiOlJFeliLfMyc9CPZCkSwLSHPPf4ZypxwjEtiRE4oQ3fJ3LplNblUD0M/nhCJo8nFfUEFw6k2HGvc/NQ5v0ayTm28zdFK+GITe/UN661zZH24TI8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=lfg0TMzTZ+B3oYfSCrhuwLyZH15LMRlh9neRQcv/Wb2GazpZKupkeOJ3qTGMfU7zGskt50pNSd5IH/+Ff3Uhv1HWY7xZ8QoMDiULtHUqsYROwmcX46xRHlH/3n3ZBSw8W9S4DANtO4dFDj0BOC3U9vEcFPL9e3RV7lRYs5UHz5k=
Received: by 10.86.70.8 with SMTP id s8mr3353405fga.1184572413280;
	Mon, 16 Jul 2007 00:53:33 -0700 (PDT)
Received: from ?10.10.50.3? ( [213.3.13.1])
	by mx.google.com with ESMTP id 31sm26235519nfu.2007.07.16.00.53.31
	(version=SSLv3 cipher=RC4-MD5); Mon, 16 Jul 2007 00:53:32 -0700 (PDT)
Message-ID: <469B23FA.5010301@gmail.com>
Date: Mon, 16 Jul 2007 09:53: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: ipv6@ietf.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>	<D03E4899F2FB3D4C8464E8C76B3B68B09A3E29@E03MVC4-UKBR.domain1.systemhost.net>	<00b301c7c4ae$506469a0$3d3816ac@atlanta.polycom.com>	<Pine.LNX.4.64.0707131202560.9923@chandra.student.uit.no>
	<016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
In-Reply-To: <016101c7c56b$5b16ec70$373816ac@atlanta.polycom.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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-07-13 18:16, Stephen Sprunk wrote:
...
> As far as why "site" has been abused to mean "administrative domain", 
> that comes from the IETF and RIRs being very ISP-centric, as I said; a 
> single downstream connection denotes a single "site" regardless of how 
> complex the internal network behind it is or how many other locations it 
> serves.  Or maybe it doesn't, depending on who's talking; that's the 
> problem.

I think another reason we've often expanded the meaning of 'site' is
because the IETF has never come to grips with the fact that most
multi-site companies (in the geographical sense) have intranets that
interconnect those sites and are multiply connected to the Internet.
Since we don't have an IETF term for such topologies, apart from AS,
we confuse ourselves.

On 2007-07-13 21:28, michael.dillon@bt.com wrote:
...
> I think it is important for the IETF to have clear documentation of the
> interconnectedness of "sites", /48 prefixes, mobility, and freedom of
> choice.

We should certainly provide technology that allows freedom of choice,
but the IETF can't do more than that.

> 
> At least one RIR now allows ISPs to assign shorter /56 prefixes to
> consumer sites, i.e. family homes and apartments. This is not
> necessarily a bad thing since it is rare for a family home to turn into
> an office without significant infrastructure change. But if there is to
> be a special size for the family home, it too should be the same
> worldwide. And it too should be documented by the IETF.

Actually the IAB tried (RFC 3177) and the RIRs chose another
approach, which is where /56 comes from.

     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 Jul 17 13: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 1IAqPq-0007Hd-Qw; Tue, 17 Jul 2007 13:00:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAqPp-000786-Et
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:00:49 -0400
Received: from smtp.microsoft.com ([131.107.115.215])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAqPn-0007a4-Vp
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:00:49 -0400
Received: from tk1-exhub-c102.redmond.corp.microsoft.com (157.56.116.113) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Tue, 17 Jul 2007 10:00:46 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	(157.54.69.169) by tk1-exhub-c102.redmond.corp.microsoft.com
	(157.56.116.113)
	with Microsoft SMTP Server id 8.0.726.0; Tue, 17 Jul 2007 10:00:44 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3959);	 Tue, 17 Jul 2007 10:00:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 17 Jul 2007 09:59:53 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfIk+V6N5Cpr9R6QumePskDtyroCA==
From: Dave Thaler <dthaler@windows.microsoft.com>
To: <varada@txc.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 17 Jul 2007 17:00:43.0966 (UTC)
	FILETIME=[035055E0:01C7C894]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: 
Subject: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============0883448358=="
Errors-To: ipv6-bounces@ietf.org

--===============0883448358==
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7C893.E6055B14"

------_=_NextPart_001_01C7C893.E6055B14
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Came across this thread...

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

=20

However, in looking at draft-ietf-ipv6-over-ppp-v2-03, it seems that
this issue was never addressed.

=20

Is this intentional?  Was there ever an agreement that ND should or
should not be done on PPP links?

(If there was, I haven't found it yet, only uncertainty and the fact
that the IPv6 over PPP RFC has

Interoperability problems and that it should be fixed in
draft-ietf-ipv6-over-ppp-v2.)

=20

-Dave


------_=_NextPart_001_01C7C893.E6055B14
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Batang;
	panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
	{font-family:"\@Batang";
	panose-1:2 3 6 0 0 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Came across this =
thread&#8230;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><a
href=3D"http://www1.ietf.org/mail-archive/web/ipv6/current/msg02314.html"=
>http://www1.ietf.org/mail-archive/web/ipv6/current/msg02314.html</a><o:p=
></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>However, in looking at =
draft-ietf-ipv6-over-ppp-v2-03, it
seems that this issue was never addressed.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is this intentional?&nbsp; Was there ever an =
agreement that
ND should or should not be done on PPP =
links?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>(If there was, I haven&#8217;t found it yet, only
uncertainty and the fact that the IPv6 over PPP RFC =
has<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Interoperability problems and that it should be fixed =
in draft-ietf-ipv6-over-ppp-v2.)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Dave<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7C893.E6055B14--


--===============0883448358==
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
--------------------------------------------------------------------

--===============0883448358==--




From ipv6-bounces@ietf.org Tue Jul 17 13:49: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 1IArB1-000460-KO; Tue, 17 Jul 2007 13:49:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IArAz-00045m-Qj
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:49:33 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IArAy-0000PV-EU
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:49:33 -0400
Received: from eastmail4bur.east.Sun.COM ([129.148.13.1])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6HHnVHK013063 for <ipv6@ietf.org>; Tue, 17 Jul 2007 17:49:31 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail4bur.east.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6HHnVJ3005133
	for <ipv6@ietf.org>; Tue, 17 Jul 2007 13:49:31 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6HHcGGM018836; Tue, 17 Jul 2007 13:38:16 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6HHcGc9018833;
	Tue, 17 Jul 2007 13:38:16 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18076.65160.138886.481086@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 13:38:16 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Dave Thaler <dthaler@windows.microsoft.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: varada@txc.com, ipv6@ietf.org
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave Thaler writes:
> Is this intentional?  Was there ever an agreement that ND should or
> should not be done on PPP links?

I'm surprised that it's a question at all.  IPV6CP (RFC 2472)
negotiates only interface identifiers, and not addresses, and ND
(2461) says that Neighbor Discovery is supposed to be implemented for
point-to-point links, so I'd expect ND to be used on those links.

Why should the PPP document dictate what IPv6 protocols are needed?

> (If there was, I haven't found it yet, only uncertainty and the fact
> that the IPv6 over PPP RFC has
> 
> Interoperability problems and that it should be fixed in
> draft-ietf-ipv6-over-ppp-v2.)

I don't think I agree.  In fact, I don't think the PPP document really
ought to go out of its way to describe how IPv6 works.  That's for the
IPv6 documents to do.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 17 13:49: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 1IArAj-0003sT-Aw; Tue, 17 Jul 2007 13:49:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IArAh-0003pf-RP
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:49:15 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IArAh-0000Ol-H6
	for ipv6@ietf.org; Tue, 17 Jul 2007 13:49:15 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 17 Jul 2007 19:49:15 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADadnEaQ/uCKh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,546,1175464800"; 
	d="scan'208"; a="148285562:sNHT25754612"
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 l6HHnEpi027456; 
	Tue, 17 Jul 2007 19:49:14 +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 l6HHnAkt015745; 
	Tue, 17 Jul 2007 17:49:10 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 l6HHn9VV012555; 
	Tue, 17 Jul 2007 18:49:10 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6HHn9lm012554;
	Tue, 17 Jul 2007 18:49:09 +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: Dave Thaler <dthaler@windows.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 17 Jul 2007 18:49:09 +0100
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	(Dave Thaler's message of "Tue\, 17 Jul 2007 09\:59\:53 -0700")
Message-ID: <7t57ioygbu2.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=974; t=1184694554;
	x=1185558554; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=SxGaXGG41Fpvtan13CVUUVyohZgw4KuYU57jmYSm1l0=;
	b=Nzsw0uCGG4aJ1y3zfiQEmmz0F42hnZwdHr4Qr9XUTwvPhpzLthgRpsdm13XEHOHDdNBFC9RN
	b5DdVLFiRx2Y1XdsTP0eAZAOR3bOHqDl7J3gjpfbHOLEP4qXCdH75Wcj;
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: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: varada@txc.com, ipv6@ietf.org
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Came across this thread...
>
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg02314.html
>
>  
>
> However, in looking at draft-ietf-ipv6-over-ppp-v2-03, it seems that
> this issue was never addressed.
>
>  
>
> Is this intentional?  Was there ever an agreement that ND should or
> should not be done on PPP links?

by "ND" you mean address resolution?  I presume there is no disagreement
that other ND functions (DAD,NUD,Router Discovery, Prefix Discovery,
etc) should be done on PPP links.

> (If there was, I haven't found it yet, only uncertainty and the fact
> that the IPv6 over PPP RFC has
>
> Interoperability problems and that it should be fixed in
> draft-ietf-ipv6-over-ppp-v2.)

I don't see the point of doing address resolution on links without
addresses. 2461 seems quite good at specifying that the LLA options
should only be included for links with addresses. what's the possible
interoperabbility issue?

cheers,
Ole

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



From ipv6-bounces@ietf.org Tue Jul 17 14:57: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 1IAsE9-0007hk-Lk; Tue, 17 Jul 2007 14:56:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAsE7-0007hf-Oq
	for ipv6@ietf.org; Tue, 17 Jul 2007 14:56:51 -0400
Received: from smtp.microsoft.com ([131.107.115.215])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAsE7-0003qT-41
	for ipv6@ietf.org; Tue, 17 Jul 2007 14:56:51 -0400
Received: from tk1-exhub-c101.redmond.corp.microsoft.com (157.56.116.111) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Tue, 17 Jul 2007 11:56:50 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	(157.54.69.169) by tk1-exhub-c101.redmond.corp.microsoft.com
	(157.56.116.111)
	with Microsoft SMTP Server id 8.0.726.0; Tue, 17 Jul 2007 11:56:46 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3959);	 Tue, 17 Jul 2007 11:56:44 -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, 17 Jul 2007 11:55:18 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfImuFLCUej6gOhQ4mKPvS5RVc2DAABurEA
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Ole Troan <ot@cisco.com>
X-OriginalArrivalTime: 17 Jul 2007 18:56:44.0632 (UTC)
	FILETIME=[3831AD80:01C7C8A4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 it's easy to see the disagreement just comparing the responses
from Ole and James.

Ole says:=20
> I don't see the point of doing address resolution on links without
> addresses.

James says:
> IPV6CP (RFC 2472) negotiates=20
> only interface identifiers, and not addresses, and ND
> (2461) says that Neighbor Discovery is supposed to be implemented for
> point-to-point links, so I'd expect ND to be used on those links.

To answer "what's the possible interoperability issue", Markus Jork
nailed it in the referenced thread:
> If one implementation sends a NS and
> expects to see a NA before sending the first message to the neighbors
> address but the other implementation doesn't use NS/NA messages on the
> PPP link, there is a problem.

We have now observed the problem Markus predicted, with real
implementations.
That is, I know of two non-interoperable implementations of RFC 2472.

I think James' argument does have real substance.  The quote from 2461
section 3.2 is (especially the last sentence):

>     point-to-point - Neighbor Discovery handles such links just like
>                      multicast links.  (Multicast can be trivially
>                      provided on point to point links, and interfaces
>                      can be assigned link-local addresses.)  Neighbor
>                      Discovery should be implemented as described in
>                      this document.

If this is the behavior we agree on, then I think that answers my
question.

-Dave

> -----Original Message-----
> From: Ole Troan [mailto:ot@cisco.com]
> Sent: Tuesday, July 17, 2007 10:49 AM
> To: Dave Thaler
> Cc: varada@txc.com; ipv6@ietf.org
> Subject: Re: Neighbor Discovery and PPP links
>=20
> > Came across this thread...
> >
> > http://www1.ietf.org/mail-archive/web/ipv6/current/msg02314.html
> >
> >
> >
> > However, in looking at draft-ietf-ipv6-over-ppp-v2-03, it seems that
> > this issue was never addressed.
> >
> >
> >
> > Is this intentional?  Was there ever an agreement that ND should or
> > should not be done on PPP links?
>=20
> by "ND" you mean address resolution?  I presume there is no
disagreement
> that other ND functions (DAD,NUD,Router Discovery, Prefix Discovery,
> etc) should be done on PPP links.
>=20
> > (If there was, I haven't found it yet, only uncertainty and the fact
> > that the IPv6 over PPP RFC has
> >
> > Interoperability problems and that it should be fixed in
> > draft-ietf-ipv6-over-ppp-v2.)
>=20
> I don't see the point of doing address resolution on links without
> addresses. 2461 seems quite good at specifying that the LLA options
> should only be included for links with addresses. what's the possible
> interoperabbility issue?
>=20
> cheers,
> Ole


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



From ipv6-bounces@ietf.org Tue Jul 17 15:11: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 1IAsSG-0004tH-Qy; Tue, 17 Jul 2007 15:11:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAsSF-0004t1-93
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:11:27 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAsSD-0004Me-SJ
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:11:27 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 17 Jul 2007 21:11:25 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAACOxnEaQ/uCLh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,547,1175464800"; 
	d="scan'208"; a="148289872:sNHT26925126"
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 l6HJBPhG029532; 
	Tue, 17 Jul 2007 21:11:25 +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 l6HJBOkt007288; 
	Tue, 17 Jul 2007 19:11:24 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 l6HJBOrA013843; 
	Tue, 17 Jul 2007 20:11:24 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6HJBOTV013842;
	Tue, 17 Jul 2007 20:11:24 +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: Dave Thaler <dthaler@windows.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 17 Jul 2007 20:11:23 +0100
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	(Dave Thaler's message of "Tue\, 17 Jul 2007 11\:55\:18 -0700")
Message-ID: <7t53azmg810.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=2259; t=1184699485;
	x=1185563485; c=relaxed/simple; s=amsdkim2001;
	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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=qMBfOcOXkCvr8LHgSvYkv5dKt/TS8WGFZKWpWEsihgE=;
	b=SnEX8smASMdSW3sXi1sq9GQTGQlacZmsSy3ReHmuB6p6RCi0qap6J+kigI6sNCb83Q04C0Fx
	4vW7jnK1FtDEqqTsRqPfpviYapv9YfSbXhZQkS8OR2p/7JXaQ0iOU3TD;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: varada@txc.com, ipv6@ietf.org
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 it's easy to see the disagreement just comparing the responses
> from Ole and James.
>
> Ole says: 
>> I don't see the point of doing address resolution on links without
>> addresses.
>
> James says:
>> IPV6CP (RFC 2472) negotiates 
>> only interface identifiers, and not addresses, and ND
>> (2461) says that Neighbor Discovery is supposed to be implemented for
>> point-to-point links, so I'd expect ND to be used on those links.

I didn't interpret James's reply to mean that his interpretation was to
do address resolution on a link. James can you clarify.

> To answer "what's the possible interoperability issue", Markus Jork
> nailed it in the referenced thread:
>> If one implementation sends a NS and
>> expects to see a NA before sending the first message to the neighbors
>> address but the other implementation doesn't use NS/NA messages on the
>> PPP link, there is a problem.

the other peer should consider that as a NUD exchange. NS/NA messages
must be supported on PPP links too, otherwise how can you do NUD.

> We have now observed the problem Markus predicted, with real
> implementations.  That is, I know of two non-interoperable
> implementations of RFC 2472.
>
> I think James' argument does have real substance.  The quote from 2461
> section 3.2 is (especially the last sentence):
>
>>     point-to-point - Neighbor Discovery handles such links just like
>>                      multicast links.  (Multicast can be trivially
>>                      provided on point to point links, and interfaces
>>                      can be assigned link-local addresses.)  Neighbor
>>                      Discovery should be implemented as described in
>>                      this document.
>
> If this is the behavior we agree on, then I think that answers my
> question.

agree on PPP links should be treated as multicast links.  that doesn't
mean you should require address resolution before sending packets.

2461, 7.2.2.  Sending Neighbor Solicitations

   When a node has a unicast packet to send to a neighbor, but does not
   know the neighbor's link-layer address, it performs address
   resolution.

for PPP links we always know the link-layer address.

cheers,
Ole

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



From ipv6-bounces@ietf.org Tue Jul 17 15:14: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 1IAsV2-0006xe-N0; Tue, 17 Jul 2007 15:14:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAsV0-0006uE-KY
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:14:18 -0400
Received: from mailb.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAsUz-0004RO-Bm
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:14:18 -0400
Received: from tk1-exhub-c102.redmond.corp.microsoft.com (157.56.116.113) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Tue, 17 Jul 2007 12:14:16 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com (157.54.0.39)
	by tk1-exhub-c102.redmond.corp.microsoft.com (157.56.116.113) with
	Microsoft SMTP Server id 8.0.726.0; Tue, 17 Jul 2007 12:14:08 -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);	 Tue, 17 Jul 2007 12:14:08 -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, 17 Jul 2007 12:13:42 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC05F81019@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <7t53azmg810.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfIplGpxFnHzTB6RkWDdfSqd9g6oQAACa6A
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t53azmg810.fsf@gpk-xdm-001.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Ole Troan <ot@cisco.com>
X-OriginalArrivalTime: 17 Jul 2007 19:14:08.0533 (UTC)
	FILETIME=[A6685450:01C7C8A6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ole Troan wrote:
[...]
> >>     point-to-point - Neighbor Discovery handles such links just
like
> >>                      multicast links.  (Multicast can be trivially
> >>                      provided on point to point links, and
interfaces
> >>                      can be assigned link-local addresses.)
Neighbor
> >>                      Discovery should be implemented as described
in
> >>                      this document.
> >
> > If this is the behavior we agree on, then I think that answers my
> > question.
>=20
> agree on PPP links should be treated as multicast links.  that doesn't
> mean you should require address resolution before sending packets.
>=20
> 2461, 7.2.2.  Sending Neighbor Solicitations
>=20
>    When a node has a unicast packet to send to a neighbor, but does
not
>    know the neighbor's link-layer address, it performs address
>    resolution.
>=20
> for PPP links we always know the link-layer address.

Yes I agree.

-Dave

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



From ipv6-bounces@ietf.org Tue Jul 17 15:31: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 1IAslH-0006P7-18; Tue, 17 Jul 2007 15:31:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAslF-0006Oz-UA
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:31:05 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAslE-0004wc-Cc
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:31:05 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6HJV1IX013288 for <ipv6@ietf.org>; Tue, 17 Jul 2007 19:31:01 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6HJV0gC021163
	for <ipv6@ietf.org>; Tue, 17 Jul 2007 15:31:00 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6HJCEco007671; Tue, 17 Jul 2007 15:12:14 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6HJCEM1007668;
	Tue, 17 Jul 2007 15:12:14 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18077.5262.92643.663259@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 15:12:14 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Dave Thaler <dthaler@windows.microsoft.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: ipv6@ietf.org, varada@txc.com
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave Thaler writes:
> I think it's easy to see the disagreement just comparing the responses
> from Ole and James.
> 
> Ole says: 
> > I don't see the point of doing address resolution on links without
> > addresses.

If you've actually got links with no addresses at all, then I agree.
That seems odd, though, given the usual automatic assignment of at
least link-locals.

> > If one implementation sends a NS and
> > expects to see a NA before sending the first message to the neighbors
> > address but the other implementation doesn't use NS/NA messages on the
> > PPP link, there is a problem.
> 
> We have now observed the problem Markus predicted, with real
> implementations.
> That is, I know of two non-interoperable implementations of RFC 2472.

Sigh.

> I think James' argument does have real substance.  The quote from 2461
> section 3.2 is (especially the last sentence):
> 
> >     point-to-point - Neighbor Discovery handles such links just like
> >                      multicast links.  (Multicast can be trivially
> >                      provided on point to point links, and interfaces
> >                      can be assigned link-local addresses.)  Neighbor
> >                      Discovery should be implemented as described in
> >                      this document.
> 
> If this is the behavior we agree on, then I think that answers my
> question.

Changing that 'should' to a 'MUST' may fix the problem with the
document.

As for implementations, I'd expect the implementor to have a really
good explanation of why he ignored fairly clear (if not capitalized)
'should' advice like that, if it was in fact done on purpose.  If it's
just a bug, then it's a bug, and might not need to be immortalized.

My reading of that text is that if the peers have prior agreement that
they're not going to do ND, and if the designer or user of the system
has a Very Good Reason to believe that omitting ND is desirable, then
it's possible to do.  Otherwise, as with any recommendation, you
'should' do what it says, and use ND as usual.

I don't know of any cases where omitting ND for IPv6 addresses makes
much sense.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 17 15:44: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 1IAsy6-000180-3S; Tue, 17 Jul 2007 15:44:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAsy5-00017o-1s
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:44:21 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAsy3-0005PL-KU
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:44:21 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6HJiIIo017794 for <ipv6@ietf.org>; Tue, 17 Jul 2007 19:44:18 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6HJiFqu023133
	for <ipv6@ietf.org>; Tue, 17 Jul 2007 15:44:15 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6HJTF04007837; Tue, 17 Jul 2007 15:29:15 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6HJTFgh007834;
	Tue, 17 Jul 2007 15:29:15 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18077.6283.346774.437786@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 15:29:15 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Ole Troan <ot@cisco.com>
In-Reply-To: <7t53azmg810.fsf@gpk-xdm-001.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t53azmg810.fsf@gpk-xdm-001.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: varada@txc.com, ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ole Troan writes:
> > I think it's easy to see the disagreement just comparing the responses
> > from Ole and James.
> >
> > Ole says: 
> >> I don't see the point of doing address resolution on links without
> >> addresses.
> >
> > James says:
> >> IPV6CP (RFC 2472) negotiates 
> >> only interface identifiers, and not addresses, and ND
> >> (2461) says that Neighbor Discovery is supposed to be implemented for
> >> point-to-point links, so I'd expect ND to be used on those links.
> 
> I didn't interpret James's reply to mean that his interpretation was to
> do address resolution on a link. James can you clarify.

Yes, I expect address resolution to be done on PPP links, just as is
described in 2461.  I expect it to be done _regardless_ of the
underlying link technology.

> >> If one implementation sends a NS and
> >> expects to see a NA before sending the first message to the neighbors
> >> address but the other implementation doesn't use NS/NA messages on the
> >> PPP link, there is a problem.
> 
> the other peer should consider that as a NUD exchange. NS/NA messages
> must be supported on PPP links too, otherwise how can you do NUD.

Indeed.

> >>     point-to-point - Neighbor Discovery handles such links just like
> >>                      multicast links.  (Multicast can be trivially
> >>                      provided on point to point links, and interfaces
> >>                      can be assigned link-local addresses.)  Neighbor
> >>                      Discovery should be implemented as described in
> >>                      this document.
> >
> > If this is the behavior we agree on, then I think that answers my
> > question.
> 
> agree on PPP links should be treated as multicast links.  that doesn't
> mean you should require address resolution before sending packets.

That text says that "Neighbor Discovery should be implemented as
described in this document."  I don't see how that's unclear, or how
it supports a "may solicit if you feel like it" design.

> 2461, 7.2.2.  Sending Neighbor Solicitations
> 
>    When a node has a unicast packet to send to a neighbor, but does not
>    know the neighbor's link-layer address, it performs address
>    resolution.
> 
> for PPP links we always know the link-layer address.

That seems like a too-strict reading of that text.  I think the issue
here is that this explanatory text has too much of an Ethernet bias,
and could be worded better.

I think that this was unintentional, as later on in the same section,
it goes on to say:

   If the solicitation is being sent to a solicited-node multicast
   address, the sender MUST include its link-layer address (if it has
   one) as a Source Link-Layer Address option.  Otherwise, the sender

In what cases don't you have a link layer address, other than point-
to-point?  As long as this is describing what to do with point-to-
point, why read the introduction as ruling out the use of
solicitations on PPP links?

Instead, the issue is that if the neighbor cache entry doesn't exist
or is STALE, then you need to solicit.  It's not a matter of just
"knowing" (somehow) that the peer doesn't have any link-layer address.

Plus, as you point out, unreachability detection falls apart if ND
isn't there.  And you don't get to see the weird 'R' bit.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 17 15:57: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 1IAtAa-0008Mo-C0; Tue, 17 Jul 2007 15:57:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAtAZ-0008Mj-8X
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:57:15 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAtAX-0005k8-Fy
	for ipv6@ietf.org; Tue, 17 Jul 2007 15:57:15 -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
	l6HJvB72012678 for <ipv6@ietf.org>; Tue, 17 Jul 2007 22:57:11 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.13.8/8.13.8/Submit) id l6HJvB0T012675;
	Tue, 17 Jul 2007 22:57:11 +0300
Date: Tue, 17 Jul 2007 22:57:11 +0300
Message-Id: <200707171957.l6HJvB0T012675@burp.tkv.asdf.org>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org
In-reply-to: <18077.6283.346774.437786@gargle.gargle.HOWL> (message from James
	Carlson on Tue, 17 Jul 2007 15:29:15 -0400)
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t53azmg810.fsf@gpk-xdm-001.cisco.com>
	<18077.6283.346774.437786@gargle.gargle.HOWL>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 expect address resolution to be done on PPP links, just as is
> described in 2461.  I expect it to be done _regardless_ of the
> underlying link technology.

If link like PPP does not have link layer addresses, there is no point
in doing "address resolution". Nobody should require implemenatation
to do pointless silly things. I believe trying to put SLA option on
NS/NA on a link without link layer addresses is actually violation of
RFC and causes the messages to be ignored.

If link like PPP does have link layer addresses, normal ND rules fully
apply.

However, DAD is perfectly sensible. And, any other ND messages that
make sense without SLA are perfectly ok and usable.


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



From ipv6-bounces@ietf.org Tue Jul 17 16: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 1IAtXd-0002Y3-VY; Tue, 17 Jul 2007 16:21:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAtXc-0002Xt-8i
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:21:04 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAtXa-0006OV-Nu
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:21:04 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6HKL1GM000078 for <ipv6@ietf.org>; Tue, 17 Jul 2007 20:21:01 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6HKL1T2027245
	for <ipv6@ietf.org>; Tue, 17 Jul 2007 16:21:01 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6HK9kv8008114; Tue, 17 Jul 2007 16:09:46 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6HK9kio008111;
	Tue, 17 Jul 2007 16:09:46 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18077.8714.140155.797849@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 16:09:46 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Markku Savela <msa@moth.iki.fi>
In-Reply-To: <200707171957.l6HJvB0T012675@burp.tkv.asdf.org>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t53azmg810.fsf@gpk-xdm-001.cisco.com>
	<18077.6283.346774.437786@gargle.gargle.HOWL>
	<200707171957.l6HJvB0T012675@burp.tkv.asdf.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ipv6@ietf.org
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Markku Savela writes:
> 
> > Yes, I expect address resolution to be done on PPP links, just as is
> > described in 2461.  I expect it to be done _regardless_ of the
> > underlying link technology.
> 
> If link like PPP does not have link layer addresses, there is no point
> in doing "address resolution". Nobody should require implemenatation
> to do pointless silly things. I believe trying to put SLA option on
> NS/NA on a link without link layer addresses is actually violation of
> RFC and causes the messages to be ignored.

I wasn't suggesting using the SLLA option.  It wouldn't make sense.
In fact, the RFC says that you don't include that option if you don't
have a link-layer address.

What I was suggesting was that you still need to perform neighbor
discovery per 2461, even though the peers on a point-to-point link
don't have any link layer addresses.

> If link like PPP does have link layer addresses, normal ND rules fully
> apply.

What PPP creates is explicitly a point-to-point link, not point-to-
multipoint or some other case.  I'm not sure I understand the
statement you're making here, as it seems to suggest a situation that
doesn't exist.

> However, DAD is perfectly sensible. And, any other ND messages that
> make sense without SLA are perfectly ok and usable.

Sure.

What messages, though, _don't_ make sense without SLLA or TLLA
options?  I think all of them are defined to work that way.  Am I
missing something?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 17 16:21: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 1IAtYB-0002nl-C7; Tue, 17 Jul 2007 16:21:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAtY9-0002mc-7s
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:21:37 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAtY7-0006P7-OA
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:21:37 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 17 Jul 2007 22:21:34 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAABPBnEaQ/uCKh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,547,1175464800"; 
	d="scan'208"; a="148292617:sNHT35070266"
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 l6HKLWbW020517; 
	Tue, 17 Jul 2007 22:21:32 +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 l6HKLWkt023445; 
	Tue, 17 Jul 2007 20:21:32 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 l6HKLV8n014769; 
	Tue, 17 Jul 2007 21:21:32 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6HKLU5P014768;
	Tue, 17 Jul 2007 21:21:30 +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: James Carlson <james.d.carlson@sun.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 21:21:30 +0100
In-Reply-To: <18077.5262.92643.663259@gargle.gargle.HOWL> (James Carlson's
	message of "Tue\, 17 Jul 2007 15\:12\:14 -0400")
Message-ID: <7t5tzs2eq7p.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=2626; t=1184703692;
	x=1185567692; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=i2sQHPF4c5Gka3Lc+3TSGCGDtxd+XKG2ezLUpaFusiA=;
	b=EAoCcP6y9Se0soZI75jbir2hvfOYkgz0CkXa/Sz5Q27Oa3tWGY3LVjq57Iyg9gVNf0DGor0g
	BkrkP0T0+EGWCgxt0VBx/Opue4hytdU4GroHF5oDBye/6bBCnOV1JC+y;
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: 244a2fd369eaf00ce6820a760a3de2e8
Cc: varada@txc.com, ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 it's easy to see the disagreement just comparing the responses
>> from Ole and James.
>> 
>> Ole says: 
>> > I don't see the point of doing address resolution on links without
>> > addresses.
>
> If you've actually got links with no addresses at all, then I agree.
> That seems odd, though, given the usual automatic assignment of at
> least link-locals.

sorry, I meant links without link-layer addressing.

>> > If one implementation sends a NS and
>> > expects to see a NA before sending the first message to the neighbors
>> > address but the other implementation doesn't use NS/NA messages on the
>> > PPP link, there is a problem.
>> 
>> We have now observed the problem Markus predicted, with real
>> implementations.  That is, I know of two non-interoperable
>> implementations of RFC 2472.
>
> Sigh.
>
>> I think James' argument does have real substance.  The quote from
>> 2461 section 3.2 is (especially the last sentence):
>> 
>> >     point-to-point - Neighbor Discovery handles such links just like
>> >                      multicast links.  (Multicast can be trivially
>> >                      provided on point to point links, and interfaces
>> >                      can be assigned link-local addresses.)  Neighbor
>> >                      Discovery should be implemented as described in
>> >                      this document.
>> 
>> If this is the behavior we agree on, then I think that answers my
>> question.
>
> Changing that 'should' to a 'MUST' may fix the problem with the
> document.
>
> As for implementations, I'd expect the implementor to have a really
> good explanation of why he ignored fairly clear (if not capitalized)
> 'should' advice like that, if it was in fact done on purpose.  If it's
> just a bug, then it's a bug, and might not need to be immortalized.
>
> My reading of that text is that if the peers have prior agreement that
> they're not going to do ND, and if the designer or user of the system
> has a Very Good Reason to believe that omitting ND is desirable, then
> it's possible to do.  Otherwise, as with any recommendation, you
> 'should' do what it says, and use ND as usual.
>
> I don't know of any cases where omitting ND for IPv6 addresses makes
> much sense.

OK, so at least we've clarified that we're in disagreement. I don't see
support in the specs for doing address resolution on links without
link-layer addresses. what would the purpose be in doing address
resolution on a link without link-layer addresses?

other ND functions, of course they should be supported.

cheers,
Ole

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



From ipv6-bounces@ietf.org Tue Jul 17 16:50: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 1IAu0D-0000sP-Ni; Tue, 17 Jul 2007 16:50:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAu0C-0000sK-6S
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:50:36 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAu0A-00078p-HY
	for ipv6@ietf.org; Tue, 17 Jul 2007 16:50:36 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6HKoXwi010828 for <ipv6@ietf.org>; Tue, 17 Jul 2007 20:50:33 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6HKoXhU001648
	for <ipv6@ietf.org>; Tue, 17 Jul 2007 16:50:33 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6HKZXBP008255; Tue, 17 Jul 2007 16:35:33 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6HKZXPj008252;
	Tue, 17 Jul 2007 16:35:33 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18077.10261.578486.718408@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 16:35:33 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Ole Troan <ot@cisco.com>
In-Reply-To: <7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: varada@txc.com, ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ole Troan writes:
> > I don't know of any cases where omitting ND for IPv6 addresses makes
> > much sense.
> 
> OK, so at least we've clarified that we're in disagreement. I don't see
> support in the specs for doing address resolution on links without
> link-layer addresses. what would the purpose be in doing address
> resolution on a link without link-layer addresses?

Generating NS and processing NA drives the state machine associated
with neighbor cache entries.

> other ND functions, of course they should be supported.

I don't see how you get there at all.  You need to be doing
solicitations and advertisements in order to do unreachability
detection and those "other ND functions," don't you?

If you're going to somehow omit ND for address resolution, but use it
for everything else, what exactly does that look like on the wire, and
what support in the existing RFC is there for this sort of operation?

I know what the current RFC suggests -- that is, that we send all of
the usual messages based on neighbor cache entry state (just as with
broadcast-type networks), but that the SLLA/TLLA option isn't used on
any messages because the peers are point-to-point.  It's the same
protocol -- one option less.

What alternative usage are you suggesting?  At a guess, the system
that would send NS because it lacks a neighbor cache entry instead
simply creates the entry and "jumps" straight to REACHABLE state
because it already "knows" where the peer is located.  Is that it?
What other protocol changes are required in order to make ND-for-
everything-but-address-resolution mode work?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Tue Jul 17 18:22: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 1IAvQx-0004FU-DO; Tue, 17 Jul 2007 18:22:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAvQv-0004FH-Cj
	for ipv6@ietf.org; Tue, 17 Jul 2007 18:22:17 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAvQu-0001KP-4Y
	for ipv6@ietf.org; Tue, 17 Jul 2007 18:22:17 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 18 Jul 2007 00:22:14 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAKrdnEaQ/uCKh2dsb2JhbACPRAEBCQon
X-IronPort-AV: i="4.16,547,1175464800"; 
	d="scan'208"; a="148299113:sNHT26206200"
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 l6HMMDkN009866; 
	Wed, 18 Jul 2007 00:22:13 +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 l6HMMDkt025527; 
	Tue, 17 Jul 2007 22:22:13 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 l6HMMCdo016418; 
	Tue, 17 Jul 2007 23:22:12 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6HMM9ek016417;
	Tue, 17 Jul 2007 23:22:09 +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: James Carlson <james.d.carlson@sun.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
Date: Tue, 17 Jul 2007 23:22:09 +0100
In-Reply-To: <18077.10261.578486.718408@gargle.gargle.HOWL> (James Carlson's
	message of "Tue\, 17 Jul 2007 16\:35\:33 -0400")
Message-ID: <7t5ps2qekmm.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=1925; t=1184710933;
	x=1185574933; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=HdJncGTFAk8Hs9PsEhRJgvGd1JujPbSsNDA8s0kHGg8=;
	b=Ispu/t/2XIiYayzYpTrZbKNb/tKTpyeTt5aXemCwLNJkD/p9dJIxPheYpbOGmLPLdCl4fAN8
	CH44awrLvjgA4CbwEFPU5C3H/T8xLFokm1mV8+SAWuCt8Y1+bXohz0v5;
Authentication-Results: ams-dkim-1; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: varada@txc.com, ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 don't know of any cases where omitting ND for IPv6 addresses makes
>> > much sense.
>> 
>> OK, so at least we've clarified that we're in disagreement. I don't see
>> support in the specs for doing address resolution on links without
>> link-layer addresses. what would the purpose be in doing address
>> resolution on a link without link-layer addresses?
>
> Generating NS and processing NA drives the state machine associated
> with neighbor cache entries.
>
>> other ND functions, of course they should be supported.
>
> I don't see how you get there at all.  You need to be doing
> solicitations and advertisements in order to do unreachability
> detection and those "other ND functions," don't you?

sure, if you need those functions.  on router to router links you don't
need NUD, which is why I don't want to make it a MUST in the
specification. 

> If you're going to somehow omit ND for address resolution, but use it
> for everything else, what exactly does that look like on the wire, and
> what support in the existing RFC is there for this sort of operation?
>
> I know what the current RFC suggests -- that is, that we send all of
> the usual messages based on neighbor cache entry state (just as with
> broadcast-type networks), but that the SLLA/TLLA option isn't used on
> any messages because the peers are point-to-point.  It's the same
> protocol -- one option less.
>
> What alternative usage are you suggesting?  At a guess, the system
> that would send NS because it lacks a neighbor cache entry instead
> simply creates the entry and "jumps" straight to REACHABLE state
> because it already "knows" where the peer is located.  Is that it?
> What other protocol changes are required in order to make ND-for-
> everything-but-address-resolution mode work?

no, if you need reachability confirmation you need to go through the
whole shebang.

cheers,
Ole

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



From ipv6-bounces@ietf.org Wed Jul 18 00: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 1IB1a3-0005mP-6h; Wed, 18 Jul 2007 00:56:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IB1a1-0005mF-Mc
	for ipv6@ietf.org; Wed, 18 Jul 2007 00:56:05 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IB1a1-0002hr-1z
	for ipv6@ietf.org; Wed, 18 Jul 2007 00:56:05 -0400
Received: from ncg-dhcp66.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 CECFF7301F;
	Wed, 18 Jul 2007 13:56:02 +0900 (JST)
Date: Wed, 18 Jul 2007 13:55:38 +0900
Message-ID: <m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <18077.10261.578486.718408@gargle.gargle.HOWL>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
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.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org, varada@txc.com
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 17 Jul 2007 16:35:33 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> Generating NS and processing NA drives the state machine associated
> with neighbor cache entries.
> 
> > other ND functions, of course they should be supported.
> 
> I don't see how you get there at all.  You need to be doing
> solicitations and advertisements in order to do unreachability
> detection and those "other ND functions," don't you?
> 
> If you're going to somehow omit ND for address resolution, but use it
> for everything else, what exactly does that look like on the wire, and
> what support in the existing RFC is there for this sort of operation?

What the BSD (KAME) implementation does is as follows:

- when it first sends a packet to the other end of a point-to-point
  (including PPP) link it creates a placeholder of a neighbor cache
  with the state of STALE
- the packet is sent to the p2p link immediately since there is no
  need to perform address resolution
- eventually the state of the neighbor cache entry is changed to PROBE
  and NUD is performed
(this description is a bit simplified to concentrate on the main point
of this discussion)

I believe this is a reasonable behavior, although as far as I know the
protocol specification does not specify this level of details
(e.g. what should be the initial state of such a cache entry).

In any case, it's totally pointless for an implementation to hold the
packet during an exchange of NS/NA for address resolution (which
itself is meaningless) on such a link.  Furthermore, if the
implementation doesn't send the held packet unless it gets an NA in
response to NS, it may cause an interoperability problem depending on
the behavior of the other end.  I guess that's the issue Dave
originally tried to indicate.  I don't know of an implementation that
performs the meaningless NS/NA for address resolution on a p2p link,
but I know an implementation that doesn't respond to an NS (whether
it's for address resolution or for NUD) on a p2p link, so I won't be
surprised if the problem actually happens.

As far as I can see the current specification is pretty clear to
prevent such a pointless behavior, but if there is an implementation
that behaves that way (Dave's message seems to indicate there is) it
may make sense to write a short I-D that clarifies this point.  In
this case I believe it should be a generic note on point-to-point link
that doesn't have the notion of L2 address (and thus doesn't require
L2 address resolution) rather than a part of a document for a specific
link type such as ipv6-over-ppp-v2.

					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 Wed Jul 18 12:22: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 1IBCHd-0001kX-NZ; Wed, 18 Jul 2007 12:21:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBCHb-0001kS-JT
	for ipv6@ietf.org; Wed, 18 Jul 2007 12:21:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBCHa-0005rt-5f
	for ipv6@ietf.org; Wed, 18 Jul 2007 12:21:47 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 18 Jul 2007 12:21:45 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFPanUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,551,1175486400"; 
	d="scan'208"; a="65513770:sNHT145341308"
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 l6IGLj5v023876; 
	Wed, 18 Jul 2007 12:21:45 -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 l6IGLiWI000448; 
	Wed, 18 Jul 2007 16:21: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); 
	Wed, 18 Jul 2007 12:21: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: Wed, 18 Jul 2007 12:21:43 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQ
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 18 Jul 2007 16:21:44.0796 (UTC)
	FILETIME=[BB7911C0:01C7C957]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7771; t=1184775705;
	x=1185639705; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=0A=20=20=20=20=20=20=20=20=22James=20Carlson=22=20<james.d.carlson@sun.co
	m>; bh=0ZXRckCjc+KDmEq2AJrd2tV2Y5UK9P/IohXQN3if+A4=;
	b=zJuep2msbfcrjVtnpY8uiktb4i12K+URWE4JLiTgDzx7pjSHs7hVTq1U1btFjpoVW6Tx3Wg5
	wWE2WvNxyNhorlPPDXQ2p0S4Gvfc/3EHiKVoFaO043fkFS9uTxTvy/RY;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: varada@txc.com, ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Ole and Dave agreed upon: "for PPP links we always know the link-layer
address". I too agree with that. Why issue an NS to resolve an address
on such a link when the address is always known?

As for NUD, 2461 NUD sections also say if upper layer protocols can
determine reachability, NUD is not invoked. Why does PPP need NUD if PPP
control protocol supports keepalive for the data connection - if
keepalive is missed, the PPP connection will be terminated.

The PPP interoperability problem that Dave raised is a general problem
outside of PPP too in that when a host is expected to forward data out
of the host, the host is performing address resolution. The default
router or other directly connected PPP client may not respond to this NS
causing the host to sit waiting for an NA. We have raised such a point
in 2nd paragraph of Introduction section of our I-D.

http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
alls-01.txt

Personally, I won't use address resolution or NUD in a PPP link. Further
I wouldn't also use DAD in a PPP link because I agree with text in RFC
2472, section 5 that says

"Therefore it is recommended that for PPP links with
   the IPV6CP Interface-Identifier option enabled the default value of
   the DupAddrDetectTransmits autoconfiguration variable [3] be zero."

Further, all of us have agreed that PPP IPV6 ND behavior belongs in an
IPv6 RFC, not a PPP specific RFC. I think RFC 2461bis is clear for PPP
ND behavior. However if folks still feel 2461bis can be clarified for
PPP, we can continue that discussion. Since our I-D is focused on
clarifying 2461bis in the areas of on-link vs. off-link determination,
address resolution vs. forwarding data out, we can add some
clarifications related to PPP in our I-D as well. In -01 version of our
I-D, section 5 "Changes to draft-ietf-ipv6-rfc2461bis-11" is very
sparse. The section is now complete in a -02 version we are working on.

Another gross change we have made in our I-D since the -01 version is
that the -02 version has a new section 7 that is modeled after RFC 2525.
We are collecting IPv6 ND bugs in this section. I think it makes sense
to add the PPP problem Dave raised as a Interoperability bug in section
7 of our I-D. To give you a flavor of what's in -02 version of our I-D,
see the table of contents below.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Host Models  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  RA Sets M and O Bits but does not Include the Prefix
           Information Option (PIO) . . . . . . . . . . . . . . . . .  6
     2.2.  RA Advertises a Prefix with the On-link(L) Bit Set . . . .  6
       2.2.1.  When the Valid Lifetime Expires  . . . . . . . . . . .  8
     2.3.  RA Advertises a Prefix with the On-link(L) Bit Clear . . .  8
   3.  Router Models  . . . . . . . . . . . . . . . . . . . . . . . .  8
     3.1.  Aggregation Router Deployment Model  . . . . . . . . . . .  9
   4.  Redirect Clarifications  . . . . . . . . . . . . . . . . . . .  9
   5.  Changes to draft-ietf-ipv6-rfc2461bis-11 . . . . . . . . . . . 10
   6.  Changes to draft-ietf-ipv6-rfc2462bis-08 . . . . . . . . . . . 14
   7.  Known IPv6 ND Implementation Problems  . . . . . . . . . . . . 15
     7.1.  Incorrect host data forwarding behavior after
           receiving an RA with no PIO  . . . . . . . . . . . . . . . 16
     7.2.  A DHCPv6 host sending 9 NS(DAD)s . . . . . . . . . . . . . 20
     7.3.  Incorrect host behavior after automatic insertion of a
           directly connected route during  address acquisition . . . 22
     7.4.  Aggregation router sending Redirects when hosts
           communicate to each other from behind  different modems  . 25
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 26
   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 27
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 27
     11.2. Informative References . . . . . . . . . . . . . . . . . . 27
   Appendix A.  CHANGE HISTORY  . . . . . . . . . . . . . . . . . . . 28
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29
   Intellectual Property and Copyright Statements . . . . . . . . . . 30


Regards,

Hemant


-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Wednesday, July 18, 2007 12:56 AM
To: James Carlson
Cc: Dave Thaler; ipv6@ietf.org; varada@txc.com
Subject: Re: Neighbor Discovery and PPP links

At Tue, 17 Jul 2007 16:35:33 -0400,
James Carlson <james.d.carlson@sun.com> wrote:

> Generating NS and processing NA drives the state machine associated=20
> with neighbor cache entries.
>=20
> > other ND functions, of course they should be supported.
>=20
> I don't see how you get there at all.  You need to be doing=20
> solicitations and advertisements in order to do unreachability=20
> detection and those "other ND functions," don't you?
>=20
> If you're going to somehow omit ND for address resolution, but use it=20
> for everything else, what exactly does that look like on the wire, and

> what support in the existing RFC is there for this sort of operation?

What the BSD (KAME) implementation does is as follows:

- when it first sends a packet to the other end of a point-to-point
  (including PPP) link it creates a placeholder of a neighbor cache
  with the state of STALE
- the packet is sent to the p2p link immediately since there is no
  need to perform address resolution
- eventually the state of the neighbor cache entry is changed to PROBE
  and NUD is performed
(this description is a bit simplified to concentrate on the main point
of this discussion)

I believe this is a reasonable behavior, although as far as I know the
protocol specification does not specify this level of details (e.g. what
should be the initial state of such a cache entry).

In any case, it's totally pointless for an implementation to hold the
packet during an exchange of NS/NA for address resolution (which itself
is meaningless) on such a link.  Furthermore, if the implementation
doesn't send the held packet unless it gets an NA in response to NS, it
may cause an interoperability problem depending on the behavior of the
other end.  I guess that's the issue Dave originally tried to indicate.
I don't know of an implementation that performs the meaningless NS/NA
for address resolution on a p2p link, but I know an implementation that
doesn't respond to an NS (whether it's for address resolution or for
NUD) on a p2p link, so I won't be surprised if the problem actually
happens.

As far as I can see the current specification is pretty clear to prevent
such a pointless behavior, but if there is an implementation that
behaves that way (Dave's message seems to indicate there is) it may make
sense to write a short I-D that clarifies this point.  In this case I
believe it should be a generic note on point-to-point link that doesn't
have the notion of L2 address (and thus doesn't require
L2 address resolution) rather than a part of a document for a specific
link type such as ipv6-over-ppp-v2.

					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 Wed Jul 18 12:35: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 1IBCV6-0000PT-Sd; Wed, 18 Jul 2007 12:35:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBCV5-0000PO-4u
	for ipv6@ietf.org; Wed, 18 Jul 2007 12:35:43 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBCV3-0006E1-Pw
	for ipv6@ietf.org; Wed, 18 Jul 2007 12:35:43 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6IGZeVE018451 for <ipv6@ietf.org>; Wed, 18 Jul 2007 16:35:41 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6IGZeTN025799
	for <ipv6@ietf.org>; Wed, 18 Jul 2007 12:35:40 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6IGKakC021612; Wed, 18 Jul 2007 12:20:36 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6IGKPZR021597;
	Wed, 18 Jul 2007 12:20:25 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Message-ID: <18078.15817.123292.316717@gargle.gargle.HOWL>
Date: Wed, 18 Jul 2007 12:20:25 -0400
From: James Carlson <james.d.carlson@sun.com>
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
In-Reply-To: <m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org, varada@txc.com
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

JINMEI Tatuya / $B?@L@C#:H(B writes:
> At Tue, 17 Jul 2007 16:35:33 -0400,
> James Carlson <james.d.carlson@sun.com> wrote:
> > If you're going to somehow omit ND for address resolution, but use it
> > for everything else, what exactly does that look like on the wire, and
> > what support in the existing RFC is there for this sort of operation?
> 
> What the BSD (KAME) implementation does is as follows:
> 
> - when it first sends a packet to the other end of a point-to-point
>   (including PPP) link it creates a placeholder of a neighbor cache
>   with the state of STALE

I understand the desire, but I don't think the current RFC supports
that behavior.  Section 5.2 sets out the basic operation:

   Once the IP address of the next-hop node is known, the sender
   examines the Neighbor Cache for link-layer information about that
   neighbor.  If no entry exists, the sender creates one, sets its state
   to INCOMPLETE, initiates Address Resolution, and then queues the data
   packet pending completion of address resolution.  For multicast-
   capable interfaces Address Resolution consists of sending a Neighbor
   Solicitation message and waiting for a Neighbor Advertisement.  When

And, as documented in 2.2, point-to-point links (such as PPP) are
assumed to be multicast-capable:

   point-to-point - a link that connects exactly two interfaces.  A
                    point-to-point link is assumed to have multicast
                    capability and have a link-local address.

The implication is that a trip through INCOMPLETE isn't optional.  I
agree that it (at least in theory) could be, but I don't see how the
existing text supports what you're describing.

> - the packet is sent to the p2p link immediately since there is no
>   need to perform address resolution
> - eventually the state of the neighbor cache entry is changed to PROBE
>   and NUD is performed
> 
> (this description is a bit simplified to concentrate on the main point
> of this discussion)

Sure.

> I believe this is a reasonable behavior, although as far as I know the
> protocol specification does not specify this level of details
> (e.g. what should be the initial state of such a cache entry).

Actually, it does.  Section 7.2.2 specifies that new entries are
created in INCOMPLETE state.

It might be possible to carve out an exception for point-to-point, but
I don't see one there now.  I *think* that you're hanging your
argument on this phrase from section 7.2.2:

   When a node has a unicast packet to send to a neighbor, but does not
   know the neighbor's link-layer address, it performs address

I believe that this needs to be cleared up.  If it really means that
point-to-point links should not send NS and wait for NA, then it
should say so and it should not go on to explain what
"multicast-capable" interfaces (which include point-to-point) links
should do.

> In any case, it's totally pointless for an implementation to hold the
> packet during an exchange of NS/NA for address resolution (which
> itself is meaningless) on such a link.  Furthermore, if the

I agree that it seems pointless, but it's what the current text says.

> originally tried to indicate.  I don't know of an implementation that
> performs the meaningless NS/NA for address resolution on a p2p link,
> but I know an implementation that doesn't respond to an NS (whether
> it's for address resolution or for NUD) on a p2p link, so I won't be
> surprised if the problem actually happens.

It doesn't respond to a valid NS?  How is that a viable
implementation.

In this part, I think you're just describing a bug.  I don't see
anything in the RFC that supports simply ignoring an NS.  (And if you
do that, then how can NUD possibly work?)

> As far as I can see the current specification is pretty clear to
> prevent such a pointless behavior, but if there is an implementation
> that behaves that way (Dave's message seems to indicate there is) it
> may make sense to write a short I-D that clarifies this point.  In
> this case I believe it should be a generic note on point-to-point link
> that doesn't have the notion of L2 address (and thus doesn't require
> L2 address resolution) rather than a part of a document for a specific
> link type such as ipv6-over-ppp-v2.

The part I support is clarifying the document.  I don't think I
support changing the functionality described in the document.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Wed Jul 18 13:00: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 1IBCsj-0000I8-Tb; Wed, 18 Jul 2007 13:00:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBCsf-0000Hh-FF
	for ipv6@ietf.org; Wed, 18 Jul 2007 13:00:05 -0400
Received: from sca-ea-mail-2.sun.com ([192.18.43.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBCsd-00085U-Rq
	for ipv6@ietf.org; Wed, 18 Jul 2007 13:00:05 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6IH020Q017530 for <ipv6@ietf.org>; Wed, 18 Jul 2007 17:00:03 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6IH02ZG028641
	for <ipv6@ietf.org>; Wed, 18 Jul 2007 13:00:02 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6IGivQB021730; Wed, 18 Jul 2007 12:44:57 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6IGivfn021727;
	Wed, 18 Jul 2007 12:44:57 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18078.17289.397787.29586@gargle.gargle.HOWL>
Date: Wed, 18 Jul 2007 12:44:57 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> Ole and Dave agreed upon: "for PPP links we always know the link-layer
> address". I too agree with that. Why issue an NS to resolve an address
> on such a link when the address is always known?
> 
> As for NUD, 2461 NUD sections also say if upper layer protocols can
> determine reachability, NUD is not invoked.

Right.  However, PPP is a lower-layer protocol.  I don't know why TCP
would be signaling address reachability, but that's what the RFC seems
to allow.  It says nothing about the link-layer itself signaling
reachability.

> Why does PPP need NUD if PPP
> control protocol supports keepalive for the data connection - if
> keepalive is missed, the PPP connection will be terminated.

PPP has both signals from the physical layer (if present) and an
optional LCP Echo-Request mechanism that can be (and often is) used to
implement a link-layer keepalive.  You're right that NUD shouldn't be
needed, and yet that's just what RFC 2461 says.

> The PPP interoperability problem that Dave raised is a general problem
> outside of PPP too in that when a host is expected to forward data out
> of the host, the host is performing address resolution. The default
> router or other directly connected PPP client may not respond to this NS
> causing the host to sit waiting for an NA. We have raised such a point
> in 2nd paragraph of Introduction section of our I-D.

So, why would a reasonable peer fail to respond to an NS?  Even if you
don't believe that the existing RFC requires the use of ND for
point-to-point links, why would you fail to respond to a solicitation
for your own address?

> http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
> alls-01.txt

I don't see a reference to point-to-point links there.

> Personally, I won't use address resolution or NUD in a PPP link. Further
> I wouldn't also use DAD in a PPP link because I agree with text in RFC
> 2472, section 5 that says
> 
> "Therefore it is recommended that for PPP links with
>    the IPV6CP Interface-Identifier option enabled the default value of
>    the DupAddrDetectTransmits autoconfiguration variable [3] be zero."

Note that IPv6 addresses can be configured manually and can
potentially come from other sources that do not guarantee uniqueness.

That doesn't sound like a good recommendation to me.  The whole point
to inventing IPCP (for IPv4) was because we had chaos on SLIP links,
where fumble-fingered users would sometimes set the same address on
both end, with hilarious results.  Why duplicate that history?

(However, I do like the idea of getting rid of that 'R' bit, at least
in some cases.  The less it's seen, the better.)

> Further, all of us have agreed that PPP IPV6 ND behavior belongs in an
> IPv6 RFC, not a PPP specific RFC.

Strongly agreed.

> I think RFC 2461bis is clear for PPP
> ND behavior.

Apparently, it's not.  I've read it several times, and it still seems
to support the same model as before, which is that NS is required, and
that newly-created neighbor cache entries must go to INCOMPLETE state
and use NS before becoming REACHABLE.  There are no exceptions for
point-to-point links that I can see, and the ones that others seem to
be citing are ambiguous at best.

>    7.  Known IPv6 ND Implementation Problems  . . . . . . . . . . . . 15
>      7.1.  Incorrect host data forwarding behavior after
>            receiving an RA with no PIO  . . . . . . . . . . . . . . . 16
>      7.2.  A DHCPv6 host sending 9 NS(DAD)s . . . . . . . . . . . . . 20
>      7.3.  Incorrect host behavior after automatic insertion of a
>            directly connected route during  address acquisition . . . 22
>      7.4.  Aggregation router sending Redirects when hosts
>            communicate to each other from behind  different modems  . 25

Nine DADs is a problem?  It might be a local problem for the sender
(it'll take a while to get that address ready), but it hardly seems
like a serious implementation issue.

Looking forward to reading that text.  ;-}

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Wed Jul 18 13:09: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 1IBD1L-0005YQ-Ks; Wed, 18 Jul 2007 13:09:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBD1G-0005Xj-Br
	for ipv6@ietf.org; Wed, 18 Jul 2007 13:08:58 -0400
Received: from mentat.com ([192.88.122.129] helo=roll.mentat.com)
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IBD1F-0008Og-0n
	for ipv6@ietf.org; Wed, 18 Jul 2007 13:08:58 -0400
Received: from alerion.mentat.com (alerion.mentat.com [192.88.122.132])
	by roll.mentat.com (Postfix) with ESMTP id 78BF64114C;
	Wed, 18 Jul 2007 10:08:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by alerion.mentat.com (Postfix) with ESMTP
	id 1AADB3F0021; Wed, 18 Jul 2007 10:08:56 -0700 (PDT)
Received: from alerion.mentat.com ([127.0.0.1])
	by localhost (alerion [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 08713-09; Wed, 18 Jul 2007 10:08:54 -0700 (PDT)
Received: from [192.88.122.144] (feller.mentat.com [192.88.122.144])
	by alerion.mentat.com (Postfix) with ESMTP
	id C811D3F0020; Wed, 18 Jul 2007 10:08:54 -0700 (PDT)
From: Tim Hartrick <tim@mentat.com>
To: James Carlson <james.d.carlson@sun.com>
In-Reply-To: <1da536d9f14182bf0a8ccd54ca4096e7@message.md5>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<1da536d9f14182bf0a8ccd54ca4096e7@message.md5>
Content-Type: text/plain
Organization: Packeteer, Inc.
Date: Wed, 18 Jul 2007 10:08:54 -0700
Message-Id: <1184778534.25906.12.camel@feller>
Mime-Version: 1.0
X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	JINMEI Tatuya / =?UTF-8?Q?=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tim@mentat.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



All,

On Wed, 2007-07-18 at 12:20 -0400, James Carlson wrote:
> 
> The part I support is clarifying the document.  I don't think I
> support changing the functionality described in the document.
> 

I agree with this sentiment.  It is reasonable for an implementation of
IPv6 over PPP to restrict what it sends based on the desire to avoid
initiating address resolution, NUD or DAD exchanges.  It isn't
reasonable, and as far I as I can see out of spec, for implementations
to not respond to attempts by their peer to do address resolution, NUD
or DAD exchanges.



tim


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



From ipv6-bounces@ietf.org Wed Jul 18 18: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 1IBIQ4-0000uN-9o; Wed, 18 Jul 2007 18:54:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBIPp-0008TR-80
	for ipv6@ietf.org; Wed, 18 Jul 2007 18:54:41 -0400
Received: from mail2.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBIPn-0000WW-UB
	for ipv6@ietf.org; Wed, 18 Jul 2007 18:54:41 -0400
Received: from tk1-exhub-c104.redmond.corp.microsoft.com (157.56.116.117) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Wed, 18 Jul 2007 15:54:38 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com (157.54.0.39)
	by tk1-exhub-c104.redmond.corp.microsoft.com (157.56.116.117) with
	Microsoft SMTP Server id 8.0.726.0; Wed, 18 Jul 2007 15:54:37 -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);	 Wed, 18 Jul 2007 15:54:36 -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, 18 Jul 2007 15:54:01 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9A=
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, JINMEI Tatuya / ????
	<jinmei@isl.rdc.toshiba.co.jp>, James Carlson <james.d.carlson@sun.com>
X-OriginalArrivalTime: 18 Jul 2007 22:54:36.0803 (UTC)
	FILETIME=[9D7BE530:01C7C98E]
X-Spam-Score: -108.0 (---------------------------------------------------)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 writes:
> Ole and Dave agreed upon: "for PPP links we always know the link-layer
> address". I too agree with that. Why issue an NS to resolve an address
> on such a link when the address is always known?
>=20
> As for NUD, 2461 NUD sections also say if upper layer protocols can
> determine reachability, NUD is not invoked. Why does PPP need NUD if
PPP
> control protocol supports keepalive for the data connection - if
> keepalive is missed, the PPP connection will be terminated.

Because addresses (e.g. RFC3041 addresses, manually configured
addresses, addresses derived from a prefix which is no longer being
advertised in the RA, etc.) can go away even though the PPP connection
stays up.
=20
> The PPP interoperability problem that Dave raised is a general problem
> outside of PPP too in that when a host is expected to forward data out
> of the host, the host is performing address resolution. The default
> router or other directly connected PPP client may not respond to this
NS
> causing the host to sit waiting for an NA. We have raised such a point
> in 2nd paragraph of Introduction section of our I-D.
>=20
>
http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
> alls-01.txt
>=20
> Personally, I won't use address resolution or NUD in a PPP link.=20

Then you will fail in cases like the one I noted above, and you won't be
RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
anyone is arguing it doesn't.)

> Further
> I wouldn't also use DAD in a PPP link because I agree with text in RFC
> 2472, section 5 that says
>=20
> "Therefore it is recommended that for PPP links with
>    the IPV6CP Interface-Identifier option enabled the default value of
>    the DupAddrDetectTransmits autoconfiguration variable [3] be zero."

Actually after some more investigation, I think I understand the source
of the interoperability issue.  The core issue is that some PPP servers
actually handle multiple PPP connections to different clients via a
common interface.  Hence from the server's perspective, it's not a
point-to-point link, but rather an NBMA link.  From the client's
perspective, the client thinks it's a point-to-point link, and there's
no way to discover that the server thinks otherwise.

Again the quote from RFC2461 is:
>   point-to-point - a link that connects exactly two interfaces.  A
>                    point-to-point link is assumed to have multicast
>                    capability and have a link-local address.

However, in the case above, the "link" (being the area bounded by Hop
Limit decrement, which won't happen between two clients since the server
is logically bridging them together without a Hop Limit decrement) does
not contain exactly two interfaces, and hence it doesn't fit the above
definition of point-to-point link.  This means that:

	PPP !=3D point-to-point

(and the terms should not be confused).

If the server believes its many-PPP-client interface is an NBMA link,
then the following quote from RFC2461 applies (especially the last
phrase):

>   non-broadcast multi-access (NBMA)
>                  - a link to which more than two interfaces can
attach,
>                    but that does not support a native form of
multicast
>                    or broadcast (e.g., X.25, ATM, frame relay, etc.).
>                    Note that all link types (including NBMA) are
>                    expected to provide multicast service for IP (e.g.,
>                    using multicast servers), but it is an issue for
>                    further study whether ND should use such facilities
>                    or an alternate mechanism that provides the
>                    equivalent ND services.

Hence one can understand how some implementers could conclude that
normal ND (as opposed to NUD) wouldn't apply.

The core underlying principle is that without explicit knowledge from
some source, one can never conclude that a link that looks like
point-to-point to you, really is.

-Dave

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



From ipv6-bounces@ietf.org Wed Jul 18 19:16: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 1IBIka-0002gs-3W; Wed, 18 Jul 2007 19:16:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBIkW-0002gj-Mn
	for ipv6@ietf.org; Wed, 18 Jul 2007 19:16:05 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBIkW-0000yq-Cw
	for ipv6@ietf.org; Wed, 18 Jul 2007 19:16:04 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 19 Jul 2007 01:16:04 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAA48nkaQ/uCLZmdsb2JhbACPRQsKJA
X-IronPort-AV: i="4.16,552,1175464800"; 
	d="scan'208"; a="148419073:sNHT23829848"
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 l6ING3Mx021893; 
	Thu, 19 Jul 2007 01:16:03 +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 l6INFwkt017567; 
	Wed, 18 Jul 2007 23:15:58 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 l6INFvMf007770; 
	Thu, 19 Jul 2007 00:15:58 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6INFeqw007768;
	Thu, 19 Jul 2007 00:15:40 +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: Dave Thaler <dthaler@windows.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 19 Jul 2007 00:15:40 +0100
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	(Dave Thaler's message of "Wed\, 18 Jul 2007 15\:54\:01 -0700")
Message-ID: <7t5d4yp9ucj.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=296; t=1184800563;
	x=1185664563; c=relaxed/simple; s=amsdkim2001;
	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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=CDyN5fMkm8osrMF2CEMRuJR12mhMBQkjLX3qJP5yyMw=;
	b=OyhcNQR8hWd0dK5ZjfoTVqP5X5TqWDE79mOcSEV6+mhexAG40OF0jYE/Mjb/TDpYnl/Zu9Px
	KlB99nefnn6GDi1lxpfe/MC9RcgE3HJVTUKKWsQgSDVaAa84h2jW5FEh;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: varada@txc.com, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave,

> Then you will fail in cases like the one I noted above, and you won't be
> RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
> anyone is arguing it doesn't.)

as long as we also agree that it is perfectly valid to operate p2p links
with NUD turned off.

/ot

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



From ipv6-bounces@ietf.org Wed Jul 18 19:53: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 1IBJKn-0004tr-W5; Wed, 18 Jul 2007 19:53:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBJKn-0004tk-2X
	for ipv6@ietf.org; Wed, 18 Jul 2007 19:53:33 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBJKm-00040x-G2
	for ipv6@ietf.org; Wed, 18 Jul 2007 19:53:32 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6INpbuO038266
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 19 Jul 2007 01:51:37 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <7t5d4yp9ucj.fsf@gpk-xdm-001.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t5d4yp9ucj.fsf@gpk-xdm-001.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4D34FBC4-5A4C-4B1A-AAE6-6E2A37C0E1C7@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 19 Jul 2007 01:53:27 +0200
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 19-jul-2007, at 1:15, Ole Troan wrote:

>> Then you will fail in cases like the one I noted above, and you  
>> won't be
>> RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
>> anyone is arguing it doesn't.)

> as long as we also agree that it is perfectly valid to operate p2p  
> links
> with NUD turned off.

This is a strange discussion.

People have different opinions about what behavior makes sense. I can  
follow the reasoning behind most of them. But the notion that an  
implementation should just do what the implementation thinks is best  
without checking with the other side is BAD. As someone else said, we  
lived through that with SLIP and we fixed it for IPv4 with PPP. The  
PPP way of handling these things is by negotiating during the *CP  
phase, NOT blindly assuming facts not in evidence.

The discussion about whether neighbor discovery is useful is mostly a  
rathole. Neighbor discovery isn't the problem on a true point-to- 
point link. The real question is: what about router advertisements?  
Should they be sent and should they be expected?

But even THAT is not the biggest problem with IPv6 over PPP. Unless  
you're dealing with dial-up, the PPP link will more often than not  
terminate on a (home) router, which means that you not only need a  
subnet for the PPP link delegated by the router at one end of the  
link, but also a prefix that can be used on the LAN behind the router  
that terminates the PPP link on the opposite side.

In my opinion, we should either say that PPP is just another  
multicast-capable link technology which means that we do vanilla ND,  
NUD, DAD, RAs and DHCPv6 prefix delegation, OR we say PPP is a  
special case, throw out all that stuff we use on ethernet and specify  
IP6CP options that implement the functionality that is relevant over  
a point-to-point link under common point-to-point constraints (i.e.,  
low bandwidth, high delay, often operating on battery power).

Mixing the two approaches can only lead to even more interoperability  
problems down the road. In my book I tell people to forget about IPv6  
over PPP because it's pretty much impossible to make it do something  
useful in the real world. It would be great if I could remove that  
little piece of advice in a future edition.

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



From ipv6-bounces@ietf.org Wed Jul 18 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 1IBJRh-0004LW-Nb; Wed, 18 Jul 2007 20:00:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBJRf-0004LQ-LO
	for ipv6@ietf.org; Wed, 18 Jul 2007 20:00:39 -0400
Received: from smtp.microsoft.com ([131.107.115.215])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBJRe-0002Qa-EG
	for ipv6@ietf.org; Wed, 18 Jul 2007 20:00:39 -0400
Received: from TK5-EXHUB-C101.redmond.corp.microsoft.com (157.54.70.76) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Wed, 18 Jul 2007 17:00:36 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	(157.54.69.169) by TK5-EXHUB-C101.redmond.corp.microsoft.com
	(157.54.70.76)
	with Microsoft SMTP Server id 8.0.726.0; Wed, 18 Jul 2007 17:00:34 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3959);	 Wed, 18 Jul 2007 17:00:34 -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, 18 Jul 2007 16:59:59 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC0602A0A5@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <7t5d4yp9ucj.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfJkaGS8BYRSS0TT4CizgF3uf/uWwABcAOg
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t5d4yp9ucj.fsf@gpk-xdm-001.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: Ole Troan <ot@cisco.com>
X-OriginalArrivalTime: 19 Jul 2007 00:00:34.0359 (UTC)
	FILETIME=[D45F0470:01C7C997]
X-Spam-Score: -108.0 (---------------------------------------------------)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: varada@txc.com, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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: Ole Troan [mailto:ot@cisco.com]
> Sent: Wednesday, July 18, 2007 4:16 PM
> To: Dave Thaler
> Cc: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson;
> varada@txc.com; ipv6@ietf.org
> Subject: Re: Neighbor Discovery and PPP links
>=20
> Dave,
>=20
> > Then you will fail in cases like the one I noted above, and you
won't be
> > RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
> > anyone is arguing it doesn't.)
>=20
> as long as we also agree that it is perfectly valid to operate p2p
links
> with NUD turned off.

Yes (but only for router-to-router connections which I believe is what
you're referring to). =20

RFC 2461 states:
> Neighbor Unreachability Detection is used for all paths between hosts
> and neighboring nodes, including host-to-host, host-to-router, and
> router-to-host communication.  Neighbor Unreachability Detection may
> also be used between routers, but is not required if an equivalent
> mechanism is available, for example, as part of the routing
> protocols.

-Dave

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



From ipv6-bounces@ietf.org Wed Jul 18 20: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 1IBJf3-0008Bv-L0; Wed, 18 Jul 2007 20:14:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBJew-0007xY-K5
	for ipv6@ietf.org; Wed, 18 Jul 2007 20:14:22 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBJev-0002hG-6w
	for ipv6@ietf.org; Wed, 18 Jul 2007 20:14:22 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 19 Jul 2007 02:14:19 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAALZInkaQ/uCKh2dsb2JhbACPRQEBCQon
X-IronPort-AV: i="4.16,553,1175464800"; 
	d="scan'208"; a="148421243:sNHT25862272"
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 l6J0EIsH010813; 
	Thu, 19 Jul 2007 02:14:18 +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 l6J0EHkt001352; 
	Thu, 19 Jul 2007 00:14:17 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 l6J0EGZE008704; 
	Thu, 19 Jul 2007 01:14:16 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6J0EGPp008703;
	Thu, 19 Jul 2007 01:14:16 +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: Dave Thaler <dthaler@windows.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t5d4yp9ucj.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A0A5@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 19 Jul 2007 01:14:16 +0100
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A0A5@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	(Dave Thaler's message of "Wed\, 18 Jul 2007 16\:59\:59 -0700")
Message-ID: <7t58x9d9rmv.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=673; t=1184804058;
	x=1185668058; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=nhgPFDXiIqC1XUtInIwMcc4AZopKIAhEuq5cb/eqc5k=;
	b=hyQVHwIFzsRoCdMOrGuWBzOO8oiBFom6Om5YJvydJpFuU2nTOTuy5Ubg6Z30Kt7bzfoxJlvj
	KHNvpTt6fu8X+dnZW+SX9Yntt8+zJE4j7Mde+4KwHebR4bsF8qVN8rjB;
Authentication-Results: ams-dkim-1; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: varada@txc.com, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>> > Then you will fail in cases like the one I noted above, and you
> won't be
>> > RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
>> > anyone is arguing it doesn't.)
>> 
>> as long as we also agree that it is perfectly valid to operate p2p
> links
>> with NUD turned off.
>
> Yes (but only for router-to-router connections which I believe is what
> you're referring to).  

indeed. (our implementation doesn't do NUD on router to host p2p links
either, but it obviously replies to NUD being initiated from the other
peer in both cases.). NUD is a bad idea for router to host anyway, but
don't get me started on that.

cheers,
Ole

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



From ipv6-bounces@ietf.org Thu Jul 19 11:54: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 1IBYJs-0003Hj-BZ; Thu, 19 Jul 2007 11:53:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBYJq-00039e-Qk
	for ipv6@ietf.org; Thu, 19 Jul 2007 11:53:34 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBYJq-0004WG-2J
	for ipv6@ietf.org; Thu, 19 Jul 2007 11:53:34 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 19 Jul 2007 11:53:33 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPcln0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,557,1175486400"; 
	d="scan'208"; a="65613265:sNHT87244030"
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 l6JFrXLc007626; 
	Thu, 19 Jul 2007 11:53:33 -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 l6JFr1Ex013674; 
	Thu, 19 Jul 2007 15:53:33 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, 19 Jul 2007 11:53:19 -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, 19 Jul 2007 11:53:18 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwA==
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 15:53:19.0423 (UTC)
	FILETIME=[ED678CF0:01C7CA1C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5969; t=1184860413;
	x=1185724413; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22Dave=20Thaler=22=20<dthaler@windows.microsoft.com>,
	=0A=20=20=20
	=20=20=20=20=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.
	co.jp>,
	=0A=20=20=20=20=20=20=20=20=22James=20Carlson=22=20<james.d.carlson
	@sun.com>; bh=5vTpzc4YZQ4si07CZk+4tFwCGlm7PDgkfKuwcBRj3D0=;
	b=rOjPmRYsXN2wKN9ph2JqSXNAyAmZEAznyq9tGJMKEenQ057G6Ffmi2tOhm5O6pJ8L6A6+Bjk
	UoFKlIA9YIxuecqH1IclGoEIdEdbWbtJupxWkY9rzvfbUSIac1ttrUin;
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: 93e7fb8fef2e780414389440f367c879
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave,

I read thru all the emails between you and Ole. I agree with Ole that
router-to-host NUD is a bad idea on p2p links. Please see in line below
with "<hs>".=20

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]=20
Sent: Wednesday, July 18, 2007 6:54 PM
To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
Cc: ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh writes:
> Ole and Dave agreed upon: "for PPP links we always know the link-layer

> address". I too agree with that. Why issue an NS to resolve an address

> on such a link when the address is always known?
>=20
> As for NUD, 2461 NUD sections also say if upper layer protocols can=20
> determine reachability, NUD is not invoked. Why does PPP need NUD if
PPP
> control protocol supports keepalive for the data connection - if=20
> keepalive is missed, the PPP connection will be terminated.

Because addresses (e.g. RFC3041 addresses, manually configured
addresses, addresses derived from a prefix which is no longer being
advertised in the RA, etc.) can go away even though the PPP connection
stays up.

<hs> Not quite. If the network layer in PPP link has to send packets,
then a new NCP session has to be established and IPV6CP (as defined in
RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the new
addresses of both ends. I expect that even when an IPv6 PPP end point is
manually configured, there are means available on the client to enforce
a new IPV6CP session. Once the new address is negotiated by IPV6CP, PPP
keepalive will maintain reachability. Am I missing anything here?
=20
> The PPP interoperability problem that Dave raised is a general problem

> outside of PPP too in that when a host is expected to forward data out

> of the host, the host is performing address resolution. The default=20
> router or other directly connected PPP client may not respond to this
NS
> causing the host to sit waiting for an NA. We have raised such a point

> in 2nd paragraph of Introduction section of our I-D.
>=20
>
http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
> alls-01.txt
>=20
> Personally, I won't use address resolution or NUD in a PPP link.=20

Then you will fail in cases like the one I noted above, and you won't be
RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
anyone is arguing it doesn't.)

<hs> No. See my response above. On a related note, as you and Ole have
agreed upon, a PPP link always knows the link-layer address, so this PPP
interoperability problem you reported can be fixed if the PPP client
never issues an NS for address resolution - this is a mcast NS, not a
unicast NS that is sent by NUD.

> Further
> I wouldn't also use DAD in a PPP link because I agree with text in RFC

> 2472, section 5 that says
>=20
> "Therefore it is recommended that for PPP links with
>    the IPV6CP Interface-Identifier option enabled the default value of
>    the DupAddrDetectTransmits autoconfiguration variable [3] be zero."

Actually after some more investigation, I think I understand the source
of the interoperability issue.  The core issue is that some PPP servers
actually handle multiple PPP connections to different clients via a
common interface.  Hence from the server's perspective, it's not a
point-to-point link, but rather an NBMA link.  From the client's
perspective, the client thinks it's a point-to-point link, and there's
no way to discover that the server thinks otherwise.

<hs> If the PPP client-server scenario falls under an NBMA link, then as
you have shown text below, it is an area of further study. We seem to be
doing a bit of further study in this thread.

Again the quote from RFC2461 is:
>   point-to-point - a link that connects exactly two interfaces.  A
>                    point-to-point link is assumed to have multicast
>                    capability and have a link-local address.

However, in the case above, the "link" (being the area bounded by Hop
Limit decrement, which won't happen between two clients since the server
is logically bridging them together without a Hop Limit decrement) does
not contain exactly two interfaces, and hence it doesn't fit the above
definition of point-to-point link.  This means that:

	PPP !=3D point-to-point

(and the terms should not be confused).

If the server believes its many-PPP-client interface is an NBMA link,
then the following quote from RFC2461 applies (especially the last
phrase):

>   non-broadcast multi-access (NBMA)
>                  - a link to which more than two interfaces can
attach,
>                    but that does not support a native form of
multicast
>                    or broadcast (e.g., X.25, ATM, frame relay, etc.).
>                    Note that all link types (including NBMA) are
>                    expected to provide multicast service for IP (e.g.,
>                    using multicast servers), but it is an issue for
>                    further study whether ND should use such facilities
>                    or an alternate mechanism that provides the
>                    equivalent ND services.

Hence one can understand how some implementers could conclude that
normal ND (as opposed to NUD) wouldn't apply.

The core underlying principle is that without explicit knowledge from
some source, one can never conclude that a link that looks like
point-to-point to you, really is.

<hs> Right. But that is why I like the IPv6 ND models where one has an
explicit flag for "Is router" or not - such a model takes care of Hop
Limit decrement and also knows what sources are is terms of host or
router. I am not sure what the PPP deployment model is in terms or
routers besides such servers to reply. I need to see a complete
deployment picture.
=20
Thanks.

Hemant

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 12:46: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 1IBZ8t-0006e5-NB; Thu, 19 Jul 2007 12:46:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBTBL-00012S-3C
	for ipv6@ietf.org; Thu, 19 Jul 2007 06:24:27 -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 1IBTBK-00012S-OT
	for ipv6@ietf.org; Thu, 19 Jul 2007 06:24:27 -0400
Received: from localhost (localhost.fuaim.com [127.0.0.1])
	by uillean.fuaim.com (Postfix) with ESMTP id DA146B87C;
	Thu, 19 Jul 2007 03:24:25 -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 25667-01-57; Thu, 19 Jul 2007 03:24:19 -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 ED044B869;
	Thu, 19 Jul 2007 03:24:19 -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 l6JAGM4Z009693;
	Thu, 19 Jul 2007 03:16:23 -0700
Message-ID: <469F3BCE.8040808@innovationslab.net>
Date: Thu, 19 Jul 2007 06:24:14 -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.4 (-)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-Mailman-Approved-At: Thu, 19 Jul 2007 12:46:15 -0400
Cc: 
Subject: [Fwd: IPv6 & L2VPN's: ARP-MED & IPLS]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,
     Please see the request below and consider providing review comments.

Regards,
Brian


-------- Original Message --------
Subject: IPv6 & L2VPN's: ARP-MED & IPLS
Date: Sun, 15 Jul 2007 13:54:09 -0600
From: Shane Amante <shane@castlepoint.net>
To: bob.hinden@nokia.com, brian@innovationslab.net,
fred.baker@cisco.com,   kurtis@kurtis.pp.se
CC: Vach Kompella <vach.kompella@alcatel.com>, Himanshu Shah
<hshah@ciena.com>

Hi All,

There are two WG drafts in the L2VPN WG, which were recently
augmented to include support for IPv6:
http://tools.ietf.org/html/draft-ietf-l2vpn-ipls-07
http://tools.ietf.org/html/draft-ietf-l2vpn-arp-mediation-08

We'd like to get some v6-savvy folks to take a look at them and
provide input on whether the v6 sections are correct, or might need
additional work/fine-tuning.  Would it be more appropriate to post to
the 'ipv6' or 'v6ops' (or both) mailing list(s) to ask folks to take
a look at the above drafts?  Assuming people have comments to improve
the draft, we would want to encourage them to send them to l2vpn
mailing list ... unless you feel it's more appropriate to cross-post
between ipv6/v6ops and l2vpn?

Thanks!

-shane

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



From ipv6-bounces@ietf.org Thu Jul 19 15:59: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 1IBc9O-0007dh-8j; Thu, 19 Jul 2007 15:59:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBc9M-0007dU-LH
	for ipv6@ietf.org; Thu, 19 Jul 2007 15:59:00 -0400
Received: from mail1.microsoft.com ([131.107.115.212] helo=smtp.microsoft.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBc9M-0003PN-6W
	for ipv6@ietf.org; Thu, 19 Jul 2007 15:59:00 -0400
Received: from tk5-exhub-c104.redmond.corp.microsoft.com (157.54.70.185) by
	TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with
	Microsoft
	SMTP Server (TLS) id 8.0.700.0; Thu, 19 Jul 2007 12:58:59 -0700
Received: from win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	(157.54.69.169) by tk5-exhub-c104.redmond.corp.microsoft.com
	(157.54.70.185)
	with Microsoft SMTP Server id 8.0.726.0; Thu, 19 Jul 2007 12:58:57 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	([157.54.62.24]) by win-imc-02.wingroup.windeploy.ntdev.microsoft.com
	with
	Microsoft SMTPSVC(6.0.3790.3959);	 Thu, 19 Jul 2007 12:58:53 -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, 19 Jul 2007 12:58:39 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzA
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, JINMEI Tatuya / ????
	<jinmei@isl.rdc.toshiba.co.jp>, James Carlson <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 19:58:53.0583 (UTC)
	FILETIME=[3BA5F1F0:01C7CA3F]
X-Spam-Score: -100.0 (---------------------------------------------------)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 writes:
> Hemant Singh writes:
> > [...] Why does PPP need NUD if PPP
> > control protocol supports keepalive for the data connection - if
> > keepalive is missed, the PPP connection will be terminated.
>=20
> Because addresses (e.g. RFC3041 addresses, manually configured
> addresses, addresses derived from a prefix which is no longer being
> advertised in the RA, etc.) can go away even though the PPP connection
> stays up.
>=20
> <hs> Not quite. If the network layer in PPP link has to send packets,
> then a new NCP session has to be established and IPV6CP (as defined in
> RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the new
> addresses of both ends. I expect that even when an IPv6 PPP end point
is
> manually configured, there are means available on the client to
enforce
> a new IPV6CP session. Once the new address is negotiated by IPV6CP,
PPP
> keepalive will maintain reachability. Am I missing anything here?

Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an
interface identifier that can be used with stateless addrconf.  The
client can construct as many other interface identifiers as it wants
(e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it
does have to do DAD for them.

[...]
> > Personally, I won't use address resolution or NUD in a PPP link.
>=20
> Then you will fail in cases like the one I noted above, and you won't
be
> RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think
> anyone is arguing it doesn't.)
>=20
> <hs> No. See my response above. On a related note, as you and Ole have
> agreed upon, a PPP link always knows the link-layer address, so this
PPP
> interoperability problem you reported can be fixed if the PPP client
> never issues an NS for address resolution - this is a mcast NS, not a
> unicast NS that is sent by NUD.

I'm not talking about mcast NS's in my response you're saying No to.
I'm talking about unicast NUD.  Unicast NS's are used on all links
(except for router-to-router links that you have some other mechanism
for) per RFC2461.

[...]=20

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 16:21: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 1IBcUa-0000DS-25; Thu, 19 Jul 2007 16:20:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBcUY-0000DN-NX
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:20:54 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBcUY-0003ze-7I
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:20:54 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6JKJ0uJ057486
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 19 Jul 2007 22:19:01 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <99D4F797-CA2C-47B1-8984-32882BAFE7C2@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 19 Jul 2007 22:20:51 +0200
To: Dave Thaler <dthaler@windows.microsoft.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: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 19-jul-2007, at 21:58, Dave Thaler wrote:

> you don't need IPv6CP to add addresses.  IPv6CP negotiates an
> interface identifier that can be used with stateless addrconf.

Apparently I'm missing something too, because I really don't get the  
logic behind this approach. DAD will take care of making sure that  
the interface identifiers don't clash, which is as good as guaranteed  
anyway if at least one end can borrow an EUI-64 from another interface.

In practice I haven't been able to get stateless autoconfig to work  
over PPP, and even if it would work first doing an IP6CP exchange and  
then router solicitation/router advertisement/neighbor discovery is  
suboptimal. Especially since this only covers the case where you need  
a single IPv6 address, a use case that's quickly dying out (i.e.,  
dial-up).

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



From ipv6-bounces@ietf.org Thu Jul 19 16:23: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 1IBcWh-00012q-5Y; Thu, 19 Jul 2007 16:23:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBcWf-00012i-Kt
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:23:05 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IBcWf-0001FP-1S
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:23:05 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 19 Jul 2007 13:23:05 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIpkn0arR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175497200"; 
	d="scan'208"; a="386909250:sNHT44131780"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6JKN4RA006894; 
	Thu, 19 Jul 2007 13:23:04 -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 l6JKN0Sd017933;
	Thu, 19 Jul 2007 20:23: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); 
	Thu, 19 Jul 2007 16:22:58 -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, 19 Jul 2007 16:22:57 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzAAAEdhvA=
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 20:22:58.0933 (UTC)
	FILETIME=[9924DA50:01C7CA42]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3394; t=1184876584;
	x=1185740584; 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:=20RE=3A=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=JlCuR3GTGkrHtyHEN6384i7AFBSRjBZIoFhHThlXjLY=;
	b=tZjXsapQSbhfbYCul/eat//H4+ZcBEEs9cIoW57Dwjo9+J8GmWxRvHLf/V5eq/bushiKN+Fq
	tTcx3SJ1Zo/Uc3ZuBLTjq7qy/s3v7rq+r2ADuBZc5yLw4/fYkZCYObqN;
Authentication-Results: sj-dkim-4; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 against "<hs>".=20

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]=20
Sent: Thursday, July 19, 2007 3:59 PM
To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
Cc: ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh writes:
> Hemant Singh writes:
> > [...] Why does PPP need NUD if PPP
> > control protocol supports keepalive for the data connection - if=20
> > keepalive is missed, the PPP connection will be terminated.
>=20
> Because addresses (e.g. RFC3041 addresses, manually configured=20
> addresses, addresses derived from a prefix which is no longer being=20
> advertised in the RA, etc.) can go away even though the PPP connection

> stays up.
>=20
> <hs> Not quite. If the network layer in PPP link has to send packets,=20
> then a new NCP session has to be established and IPV6CP (as defined in

> RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the new=20
> addresses of both ends. I expect that even when an IPv6 PPP end point
is
> manually configured, there are means available on the client to
enforce
> a new IPV6CP session. Once the new address is negotiated by IPV6CP,
PPP
> keepalive will maintain reachability. Am I missing anything here?

Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an
interface identifier that can be used with stateless addrconf.  The
client can construct as many other interface identifiers as it wants
(e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it
does have to do DAD for them.

<hs> Gotcha. I guess when section 5 of RFC 2472 uses the plural
addresses word in text snipped below, the plural is for both ends of the
PPP link and not all unicast IPv6 addresses assigned to the client:

[The Interface Identifier of IPv6 unicast addresses [6] of a PPP
   interface, SHOULD be negotiated in the IPV6CP phase of the PPP
   connection setup (see section 4.1). ]

Certainly if any PPP configured address does not undergo IPV6CP, then
DAD has to be initiated for those addresses. I would like to clarify RFC
2472 to make explicit statements that some unicast addresses of a PPP
client will not undergo IPV6CP and DAD will be used for those addresses.

[...]
> > Personally, I won't use address resolution or NUD in a PPP link.
>=20
> Then you will fail in cases like the one I noted above, and you won't
be
> RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think=20
> anyone is arguing it doesn't.)
>=20
> <hs> No. See my response above. On a related note, as you and Ole have

> agreed upon, a PPP link always knows the link-layer address, so this
PPP
> interoperability problem you reported can be fixed if the PPP client=20
> never issues an NS for address resolution - this is a mcast NS, not a=20
> unicast NS that is sent by NUD.

I'm not talking about mcast NS's in my response you're saying No to.
I'm talking about unicast NUD.  Unicast NS's are used on all links
(except for router-to-router links that you have some other mechanism
for) per RFC2461.

<hs> OK. Router-to-router is already a well-known link that NUD can be
skipped for as even 246bis says. Ole does not like router-to-host
unicast NS NUD messages as well. I agree with him.=20

Thanks.

Hemant


[...]=20

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 16:48: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 1IBcvO-0003iY-5L; Thu, 19 Jul 2007 16:48:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBcvN-0003iS-Jp
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:48:37 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBcvM-00022b-W1
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:48:37 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 19 Jul 2007 16:48:05 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAGZqn0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175486400"; 
	d="scan'208"; a="65645487:sNHT87656716592"
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 l6JKm4Rs022478; 
	Thu, 19 Jul 2007 16:48:04 -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 l6JKlvEf008092; 
	Thu, 19 Jul 2007 20:48:04 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, 19 Jul 2007 16:48:01 -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, 19 Jul 2007 16:48:01 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzAAAJQ8SA=
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 20:48:01.0635 (UTC)
	FILETIME=[18D2FB30:01C7CA46]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2888; t=1184878084;
	x=1185742084; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22Dave=20Thaler=22=20<dthaler@windows.microsoft.com>,
	=0A=20=20=20
	=20=20=20=20=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.
	co.jp>,
	=0A=20=20=20=20=20=20=20=20=22James=20Carlson=22=20<james.d.carlson
	@sun.com>; bh=fx+JarTbvQRwBQtqX+mZNx6thkpEQXVONBwDxjhU410=;
	b=Fu5W7YNmcmwsQV7LHsJEmheqRd5xuOqGDyCTC5owZqNfdbwUxzLoX7JUOvpTItPEUDqjm/oA
	cROUmolYTC7V6sYAn2kSm/M/wN++zvGvYkseP7TsSU2dRrzgYGLkrYUY;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave,

It also seems awkward to me to use IPV6CP for one unicast address (and
associated interface id) of a PPP client and use DAD for any more
unicast addresses configured for the PPP client. Seems like muddying the
waters to me. Why not use IPV6CP for all addresses? Going along with
what Iljitsch van Beijnum is saying, who is deploying SLAAC with PPP
that we will then have to think about privacy addresses etc?=20

Hemant

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]=20
Sent: Thursday, July 19, 2007 3:59 PM
To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
Cc: ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh writes:
> Hemant Singh writes:
> > [...] Why does PPP need NUD if PPP
> > control protocol supports keepalive for the data connection - if=20
> > keepalive is missed, the PPP connection will be terminated.
>=20
> Because addresses (e.g. RFC3041 addresses, manually configured=20
> addresses, addresses derived from a prefix which is no longer being=20
> advertised in the RA, etc.) can go away even though the PPP connection

> stays up.
>=20
> <hs> Not quite. If the network layer in PPP link has to send packets,=20
> then a new NCP session has to be established and IPV6CP (as defined in

> RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the new=20
> addresses of both ends. I expect that even when an IPv6 PPP end point
is
> manually configured, there are means available on the client to
enforce
> a new IPV6CP session. Once the new address is negotiated by IPV6CP,
PPP
> keepalive will maintain reachability. Am I missing anything here?

Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an
interface identifier that can be used with stateless addrconf.  The
client can construct as many other interface identifiers as it wants
(e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it
does have to do DAD for them.

[...]
> > Personally, I won't use address resolution or NUD in a PPP link.
>=20
> Then you will fail in cases like the one I noted above, and you won't
be
> RFC compliant.  RFC2461 requires NUD on _all_ links.  (I don't think=20
> anyone is arguing it doesn't.)
>=20
> <hs> No. See my response above. On a related note, as you and Ole have

> agreed upon, a PPP link always knows the link-layer address, so this
PPP
> interoperability problem you reported can be fixed if the PPP client=20
> never issues an NS for address resolution - this is a mcast NS, not a=20
> unicast NS that is sent by NUD.

I'm not talking about mcast NS's in my response you're saying No to.
I'm talking about unicast NUD.  Unicast NS's are used on all links
(except for router-to-router links that you have some other mechanism
for) per RFC2461.

[...]=20

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 16:50: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 1IBcxJ-0005Xh-U7; Thu, 19 Jul 2007 16:50:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBcxI-0005XV-Hq
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:50:36 -0400
Received: from mailc.microsoft.com ([131.107.115.214] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBcxH-00025K-SQ
	for ipv6@ietf.org; Thu, 19 Jul 2007 16:50:36 -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, 19 Jul 2007 13:50:35 -0700
Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com (157.54.0.39)
	by tk5-exhub-c103.redmond.corp.microsoft.com (157.54.70.186) with
	Microsoft SMTP Server id 8.0.726.0; Thu, 19 Jul 2007 13:50:34 -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);	 Thu, 19 Jul 2007 13:50:32 -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, 19 Jul 2007 13:50:08 -0700
Message-ID: <271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzAAAEdhvAAAQueAA==
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
From: Dave Thaler <dthaler@windows.microsoft.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, JINMEI Tatuya / ????
	<jinmei@isl.rdc.toshiba.co.jp>, James Carlson <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 20:50:32.0870 (UTC)
	FILETIME=[72F79C60:01C7CA46]
X-Spam-Score: -108.0 (---------------------------------------------------)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Below.

> -----Original Message-----
> From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
> Sent: Thursday, July 19, 2007 1:23 PM
> To: Dave Thaler; JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Please see in line below against "<hs>".
>=20
> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
> Sent: Thursday, July 19, 2007 3:59 PM
> To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Hemant Singh writes:
> > Hemant Singh writes:
> > > [...] Why does PPP need NUD if PPP
> > > control protocol supports keepalive for the data connection - if
> > > keepalive is missed, the PPP connection will be terminated.
> >
> > Because addresses (e.g. RFC3041 addresses, manually configured
> > addresses, addresses derived from a prefix which is no longer being
> > advertised in the RA, etc.) can go away even though the PPP
connection
>=20
> > stays up.
> >
> > <hs> Not quite. If the network layer in PPP link has to send
packets,
> > then a new NCP session has to be established and IPV6CP (as defined
in
>=20
> > RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the
new
> > addresses of both ends. I expect that even when an IPv6 PPP end
point
> is
> > manually configured, there are means available on the client to
> enforce
> > a new IPV6CP session. Once the new address is negotiated by IPV6CP,
> PPP
> > keepalive will maintain reachability. Am I missing anything here?
>=20
> Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an
> interface identifier that can be used with stateless addrconf.  The
> client can construct as many other interface identifiers as it wants
> (e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it
> does have to do DAD for them.
>=20
> <hs> Gotcha. I guess when section 5 of RFC 2472 uses the plural
> addresses word in text snipped below, the plural is for both ends of
the
> PPP link and not all unicast IPv6 addresses assigned to the client:
>=20
> [The Interface Identifier of IPv6 unicast addresses [6] of a PPP
>    interface, SHOULD be negotiated in the IPV6CP phase of the PPP
>    connection setup (see section 4.1). ]
>=20
> Certainly if any PPP configured address does not undergo IPV6CP, then
> DAD has to be initiated for those addresses. I would like to clarify
RFC
> 2472 to make explicit statements that some unicast addresses of a PPP
> client will not undergo IPV6CP and DAD will be used for those
addresses.

Yep.  RFC 2472 states:
> As long as the Interface Identifier is negotiated in the IPV6CP phase
> of the PPP connection setup, it is redundant to perform duplicate
> address detection as a part of the IPv6 Stateless Autoconfiguration
> protocol [3].

The key phrase being "as long as the" (keeping in mind that a host can
use multiple interface identifiers simultaneously, so this is a per
interface identifier statement). =20

The problematic statement in 2472 is the one immediately after the above
quote:

>  Therefore it is recommended that for PPP links with
> the IPV6CP Interface-Identifier option enabled the default value of
> the DupAddrDetectTransmits autoconfiguration variable [3] be zero.

since the quote above doesn't take into account other interface
identifiers.

2472bis makes it much more clear by adding more text in between the two
statements, such that it restricts the first quote to applying to the
link-local address only, and narrows the second quote to only applying
when two other conditions are met such it doesn't apply to uses of PPP
like the problematic case I described.  (Basically where you have
knowledge that it is indeed a point-to-point not NBMA link, and where
you have knowledge that the router has no global addresses, hence the
change from 2472 is that skipping DAD would never be the default for an
arbitrary PPP link.)

> [...]
> <hs> OK. Router-to-router is already a well-known link that NUD can be
> skipped for as even 246bis says. Ole does not like router-to-host
> unicast NS NUD messages as well. I agree with him.

Currently RFC2461 doesn't support that view.  If this is the WG
consensus, then it would be good to put the rationale into a draft that
can update 2461.

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 17:10: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 1IBdGL-000561-Td; Thu, 19 Jul 2007 17:10:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdGK-00055p-Re
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:10:16 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBdGK-0002UK-F3
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:10:16 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 19 Jul 2007 17:10:16 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAI9vn0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175486400"; 
	d="scan'208"; a="126525453:sNHT44616642"
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 l6JLAGkw001132; 
	Thu, 19 Jul 2007 17:10:16 -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 l6JLABEh017047; 
	Thu, 19 Jul 2007 21:10:15 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, 19 Jul 2007 17:10:15 -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, 19 Jul 2007 17:10:14 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18079.53002.425765.815419@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfKR9Am9jysUr9GSMSRgPKwB2FebgAAHlog
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 21:10:15.0193 (UTC)
	FILETIME=[33AFC890:01C7CA49]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1820; t=1184879416;
	x=1185743416; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22James=20Carlson=22=20<james.d.carlson@sun.com>;
	bh=IejQgLxlqDcABb5nEmhyu4e11vngVx4F+StpKZ4gJ0o=;
	b=eEvxlPreA8u6hlDzY7QMIPSaZ0o9ewcVmm9hrXA3JIVQ/lZuRBZ9U5aIrjbdTOQUqj4y2jU+
	MvMN5h1nbYUY8i2Px6ul8igqqi0Qo+bAmfRM5WJORGEa1Qzpg8cfGZMB;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

I am talking off of this statement in RFC 2472, section

[The Interface Identifier of IPv6 unicast addresses [6] of a PPP
   interface, SHOULD be negotiated in the IPV6CP phase of the PPP
   connection setup (see section 4.1). ]

Even they talk about a unicast address when they are referring to a
Link-local address and interface-id=20

All I am saying is, if IPV6CP is used to negotiate one interface-id,
when multiple addresses, that Dave pointed out, are needed for the same
client, why not use IPV6CP to negotiate interface-id's for even these
addresses?

Hemant

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Thursday, July 19, 2007 4:52 PM
To: Hemant Singh (shemant)
Cc: Dave Thaler; JINMEI Tatuya / ????; ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh (shemant) writes:
> It also seems awkward to me to use IPV6CP for one unicast address (and

> associated interface id) of a PPP client and use DAD for any more=20
> unicast addresses configured for the PPP client. Seems like muddying=20
> the waters to me. Why not use IPV6CP for all addresses?

I'm confused.  IPV6CP doesn't negotiate any IPv6 addresses at all.  It
just negotiates the interface token that is used for link-locals and
_may_ be used to construct autoconf addresses.

> Going along with
> what Iljitsch van Beijnum is saying, who is deploying SLAAC with PPP=20
> that we will then have to think about privacy addresses etc?

It works today on Solaris ... not sure about others.

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Thu Jul 19 17:11: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 1IBdHa-0006HQ-30; Thu, 19 Jul 2007 17:11:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdHY-0006HE-VK
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:11:33 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBdHY-0002WN-I7
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:11:32 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6JLBVPq021835 for <ipv6@ietf.org>; Thu, 19 Jul 2007 21:11:31 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6JLBUx3026175
	for <ipv6@ietf.org>; Thu, 19 Jul 2007 17:11:30 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6JKqb1D008806; Thu, 19 Jul 2007 16:52:37 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6JKqQmW008799;
	Thu, 19 Jul 2007 16:52:26 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18079.53002.425765.815419@gargle.gargle.HOWL>
Date: Thu, 19 Jul 2007 16:52:26 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> It also seems awkward to me to use IPV6CP for one unicast address (and
> associated interface id) of a PPP client and use DAD for any more
> unicast addresses configured for the PPP client. Seems like muddying the
> waters to me. Why not use IPV6CP for all addresses?

I'm confused.  IPV6CP doesn't negotiate any IPv6 addresses at all.  It
just negotiates the interface token that is used for link-locals and
_may_ be used to construct autoconf addresses.

> Going along with
> what Iljitsch van Beijnum is saying, who is deploying SLAAC with PPP
> that we will then have to think about privacy addresses etc? 

It works today on Solaris ... not sure about others.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Thu Jul 19 17: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 1IBdQP-0004EN-Ho; Thu, 19 Jul 2007 17:20:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdQO-0004EH-E7
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:20:40 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBdQN-0005aM-Fh
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:20:40 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 19 Jul 2007 14:20:27 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOdxn0arR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175497200"; 
	d="scan'208"; a="9537186:sNHT1262131050"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l6JLKRWQ010756; 
	Thu, 19 Jul 2007 14:20:27 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6JLKIT1014805;
	Thu, 19 Jul 2007 21:20: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); 
	Thu, 19 Jul 2007 17:20:23 -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, 19 Jul 2007 17:20:21 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A415D@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzAAAEdhvAAAQueAAABJFKw
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>,
	"JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 21:20:23.0166 (UTC)
	FILETIME=[9E1119E0:01C7CA4A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5985; t=1184880027;
	x=1185744027; 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:=20RE=3A=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=XALymWwYYXjIiuSRBPxvL6piQsTG6RT257hkXXvZHRI=;
	b=frgZnIGhplWak+z9+ex7rOU5OYrrzBOglPlkkTirKwCjVgOqBqPOrXRni/X4NdttBf5NtATe
	fV0P5aujFx76gEZDOA0tdRZshcrQAhUC3l8o0QH27zPnkjr9AQCZclxj;
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: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: varada@txc.com, ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave,

Are you suggesting someone puts together a 2472bis or does such an I-D
already exist? I couldn't find it. This issue that you raised yesterday
where you said:

"The core issue is that some PPP servers actually handle multiple PPP
connections to different clients via a common interface.  Hence from the
server's perspective, it's not a point-to-point link, but rather an NBMA
link.  From the client's perspective, the client thinks it's a
point-to-point link, and there's no way to discover that the server
thinks otherwise."

belongs in a PPP document to be discussed. Just like IPv6 ND RFC's
discuss router and host, I think it makes sense for a PPP document to
discuss a server and client because the server is behaving differently
for the PPP link. By all means, if it makes sense to modify anything in
PPP NCP or any other related protocol to incorporate the notion of
server vs. client, be my guest.

As for the view Ole pointed out for dislike of router-to-host NUD,
certainly the rationale for that view makes sense to be brought out, and
changes be added to a draft that will update 2461. Let's see what do
other folks say.

Thanks.

Hemant=20

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]=20
Sent: Thursday, July 19, 2007 4:50 PM
To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
Cc: ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Below.

> -----Original Message-----
> From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
> Sent: Thursday, July 19, 2007 1:23 PM
> To: Dave Thaler; JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Please see in line below against "<hs>".
>=20
> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
> Sent: Thursday, July 19, 2007 3:59 PM
> To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Hemant Singh writes:
> > Hemant Singh writes:
> > > [...] Why does PPP need NUD if PPP control protocol supports=20
> > > keepalive for the data connection - if keepalive is missed, the=20
> > > PPP connection will be terminated.
> >
> > Because addresses (e.g. RFC3041 addresses, manually configured=20
> > addresses, addresses derived from a prefix which is no longer being=20
> > advertised in the RA, etc.) can go away even though the PPP
connection
>=20
> > stays up.
> >
> > <hs> Not quite. If the network layer in PPP link has to send
packets,
> > then a new NCP session has to be established and IPV6CP (as defined
in
>=20
> > RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the
new
> > addresses of both ends. I expect that even when an IPv6 PPP end
point
> is
> > manually configured, there are means available on the client to
> enforce
> > a new IPV6CP session. Once the new address is negotiated by IPV6CP,
> PPP
> > keepalive will maintain reachability. Am I missing anything here?
>=20
> Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an=20
> interface identifier that can be used with stateless addrconf.  The=20
> client can construct as many other interface identifiers as it wants=20
> (e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it=20
> does have to do DAD for them.
>=20
> <hs> Gotcha. I guess when section 5 of RFC 2472 uses the plural=20
> addresses word in text snipped below, the plural is for both ends of
the
> PPP link and not all unicast IPv6 addresses assigned to the client:
>=20
> [The Interface Identifier of IPv6 unicast addresses [6] of a PPP
>    interface, SHOULD be negotiated in the IPV6CP phase of the PPP
>    connection setup (see section 4.1). ]
>=20
> Certainly if any PPP configured address does not undergo IPV6CP, then=20
> DAD has to be initiated for those addresses. I would like to clarify
RFC
> 2472 to make explicit statements that some unicast addresses of a PPP=20
> client will not undergo IPV6CP and DAD will be used for those
addresses.

Yep.  RFC 2472 states:
> As long as the Interface Identifier is negotiated in the IPV6CP phase=20
> of the PPP connection setup, it is redundant to perform duplicate=20
> address detection as a part of the IPv6 Stateless Autoconfiguration=20
> protocol [3].

The key phrase being "as long as the" (keeping in mind that a host can
use multiple interface identifiers simultaneously, so this is a per
interface identifier statement). =20

The problematic statement in 2472 is the one immediately after the above
quote:

>  Therefore it is recommended that for PPP links with the IPV6CP=20
> Interface-Identifier option enabled the default value of the=20
> DupAddrDetectTransmits autoconfiguration variable [3] be zero.

since the quote above doesn't take into account other interface
identifiers.

2472bis makes it much more clear by adding more text in between the two
statements, such that it restricts the first quote to applying to the
link-local address only, and narrows the second quote to only applying
when two other conditions are met such it doesn't apply to uses of PPP
like the problematic case I described.  (Basically where you have
knowledge that it is indeed a point-to-point not NBMA link, and where
you have knowledge that the router has no global addresses, hence the
change from 2472 is that skipping DAD would never be the default for an
arbitrary PPP link.)

> [...]
> <hs> OK. Router-to-router is already a well-known link that NUD can be

> skipped for as even 246bis says. Ole does not like router-to-host=20
> unicast NS NUD messages as well. I agree with him.

Currently RFC2461 doesn't support that view.  If this is the WG
consensus, then it would be good to put the rationale into a draft that
can update 2461.

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 17:35: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 1IBdeF-0007lN-Hb; Thu, 19 Jul 2007 17:34:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdeD-0007lF-Vz
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:34:58 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBdeD-0005vl-IA
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:34:57 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6JLYuHP028555 for <ipv6@ietf.org>; Thu, 19 Jul 2007 21:34:56 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6JLYu2b000431
	for <ipv6@ietf.org>; Thu, 19 Jul 2007 17:34:56 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6JLJppH008937; Thu, 19 Jul 2007 17:19:51 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6JLJm7c008934;
	Thu, 19 Jul 2007 17:19:48 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18079.54644.379204.366856@gargle.gargle.HOWL>
Date: Thu, 19 Jul 2007 17:19:48 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> All I am saying is, if IPV6CP is used to negotiate one interface-id,
> when multiple addresses, that Dave pointed out, are needed for the same
> client, why not use IPV6CP to negotiate interface-id's for even these
> addresses?

We'd have to discuss that on the PPP list, but my take on it is that
it'd likely be incompatible with existing implementations.  I don't
know that anyone expects more than one IPV6CP Interface-Identifier
option -- I know for certain that the open source ppp-2.4
implementation wouldn't handle it right.

I think it'd be pretty strange operationally as well.  You'd end up
with multiple link-local addresses.

I don't think I agree with pushing this issue down into PPP.  We don't
do that for Ethernet, so why would PPP be special?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Thu Jul 19 17:41: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 1IBdkY-0005Rs-0n; Thu, 19 Jul 2007 17:41:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdkW-0005Rl-Ll
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:41:28 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBdkW-00062d-6q
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:41:28 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-1.cisco.com with ESMTP; 19 Jul 2007 14:41:27 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANh2n0arR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175497200"; d="scan'208"; a="9543023:sNHT19174632"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6JLfRnW031857; 
	Thu, 19 Jul 2007 14:41:27 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6JLf9AG011067;
	Thu, 19 Jul 2007 21:41:27 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, 19 Jul 2007 17:41:23 -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, 19 Jul 2007 17:41:20 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A417A@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18079.54644.379204.366856@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfKS6DNnwMShI6PQ0GrjdgP38UxUAAANO2A
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com><18079.53002.425765.815419@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 19 Jul 2007 21:41:23.0163 (UTC)
	FILETIME=[8D1562B0:01C7CA4D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1902; t=1184881287;
	x=1185745287; c=relaxed/simple; s=sjdkim2002;
	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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=oJ2D8rn5/Ovmn1zjTG+XH/JOc4TGXgenQAp7E9kRt9c=;
	b=d9VCbVoLbcEUGWMtK9k3MY7Dj4pxlFY+6Qccg+M+OUyfRRPvT6pcTV1AKxnIWNp2LpS+ZK0D
	w20YQeJwcSSZ4u9eE65Y5fOv2ICQ6xrTUDJeofffb97NgoYZHliP3keo;
Authentication-Results: sj-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 certainly not suggesting using more than one Link-Local address for
a PPP client. All I am saying is if PPP uses IPV6CP and interface-id for
Link-Local address, it is a little odd to use DAD for rest of the
addresses assigned to the PPP client - the privacy and other addresses
that Dave alluded to. I don't want to change PPP in such a radical way -
given the nature of the p2p link it's not so odd if Link-local address
is negotiated using IPV6CP and other addresses of the PPP client use
DAD. We should just make such facts clear in 2472bis.

Thanks.

Hemant

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Thursday, July 19, 2007 5:20 PM
To: Hemant Singh (shemant)
Cc: Dave Thaler; JINMEI Tatuya / ????; ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh (shemant) writes:
> All I am saying is, if IPV6CP is used to negotiate one interface-id,=20
> when multiple addresses, that Dave pointed out, are needed for the=20
> same client, why not use IPV6CP to negotiate interface-id's for even=20
> these addresses?

We'd have to discuss that on the PPP list, but my take on it is that
it'd likely be incompatible with existing implementations.  I don't know
that anyone expects more than one IPV6CP Interface-Identifier option --
I know for certain that the open source ppp-2.4 implementation wouldn't
handle it right.

I think it'd be pretty strange operationally as well.  You'd end up with
multiple link-local addresses.

I don't think I agree with pushing this issue down into PPP.  We don't
do that for Ethernet, so why would PPP be special?

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Thu Jul 19 17:51: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 1IBdtT-0002IY-DB; Thu, 19 Jul 2007 17:50:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBdtR-0002IN-N1
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:50:41 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBdtR-0003S4-1w
	for ipv6@ietf.org; Thu, 19 Jul 2007 17:50:41 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 19 Jul 2007 17:50:40 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CACp5n0ZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,558,1175486400"; 
	d="scan'208"; a="65650626:sNHT47280548"
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 l6JLoeS4032005; 
	Thu, 19 Jul 2007 17:50:40 -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 l6JLodEd029415; 
	Thu, 19 Jul 2007 21:50:40 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, 19 Jul 2007 17:50: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: Thu, 19 Jul 2007 17:50:36 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfI+B5iE/4CNW+/Sp2pq3KqmGHmNwAWEMvQAA7jw9AAI2AhwAAIrxzAAAEdhvAAAQueAAACdelg
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>
X-OriginalArrivalTime: 19 Jul 2007 21:50:39.0721 (UTC)
	FILETIME=[D8D16590:01C7CA4E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4990; t=1184881840;
	x=1185745840; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22Dave=20Thaler=22=20<dthaler@windows.microsoft.com>;
	bh=f8IMuHlRdd+liWB1b9XoTCmtYH8ejs8PPeXwEvWE4Ak=;
	b=nXF1Xom9n0rGgCG90VrKUBSwBReCC+c9kTWa6KC5AyOW6sxZONidJrA7hM7NXRy1CubCAOlX
	KczvuI72XNQ2pxUMGK0o9Aq00f4Izftc+RsCQX8gfVtdgaDWNrmP6ctX;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: ipv6@ietf.org
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dave,=20

Never mind, I found what's 2462bis. I got hold of

http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt

Thanks to Srihari who sent me an email.

Hemant=20

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]=20
Sent: Thursday, July 19, 2007 4:50 PM
To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
Cc: ipv6@ietf.org; varada@txc.com
Subject: RE: Neighbor Discovery and PPP links

Below.

> -----Original Message-----
> From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
> Sent: Thursday, July 19, 2007 1:23 PM
> To: Dave Thaler; JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Please see in line below against "<hs>".
>=20
> -----Original Message-----
> From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
> Sent: Thursday, July 19, 2007 3:59 PM
> To: Hemant Singh (shemant); JINMEI Tatuya / ????; James Carlson
> Cc: ipv6@ietf.org; varada@txc.com
> Subject: RE: Neighbor Discovery and PPP links
>=20
> Hemant Singh writes:
> > Hemant Singh writes:
> > > [...] Why does PPP need NUD if PPP control protocol supports=20
> > > keepalive for the data connection - if keepalive is missed, the=20
> > > PPP connection will be terminated.
> >
> > Because addresses (e.g. RFC3041 addresses, manually configured=20
> > addresses, addresses derived from a prefix which is no longer being=20
> > advertised in the RA, etc.) can go away even though the PPP
connection
>=20
> > stays up.
> >
> > <hs> Not quite. If the network layer in PPP link has to send
packets,
> > then a new NCP session has to be established and IPV6CP (as defined
in
>=20
> > RFC 2472 to be NCP protocol for PPP over IPv6) will negotiate the
new
> > addresses of both ends. I expect that even when an IPv6 PPP end
point
> is
> > manually configured, there are means available on the client to
> enforce
> > a new IPV6CP session. Once the new address is negotiated by IPV6CP,
> PPP
> > keepalive will maintain reachability. Am I missing anything here?
>=20
> Yes, you don't need IPv6CP to add addresses.  IPv6CP negotiates an=20
> interface identifier that can be used with stateless addrconf.  The=20
> client can construct as many other interface identifiers as it wants=20
> (e.g. for RFC3041 addresses) and need not use IPv6CP for them, but it=20
> does have to do DAD for them.
>=20
> <hs> Gotcha. I guess when section 5 of RFC 2472 uses the plural=20
> addresses word in text snipped below, the plural is for both ends of
the
> PPP link and not all unicast IPv6 addresses assigned to the client:
>=20
> [The Interface Identifier of IPv6 unicast addresses [6] of a PPP
>    interface, SHOULD be negotiated in the IPV6CP phase of the PPP
>    connection setup (see section 4.1). ]
>=20
> Certainly if any PPP configured address does not undergo IPV6CP, then=20
> DAD has to be initiated for those addresses. I would like to clarify
RFC
> 2472 to make explicit statements that some unicast addresses of a PPP=20
> client will not undergo IPV6CP and DAD will be used for those
addresses.

Yep.  RFC 2472 states:
> As long as the Interface Identifier is negotiated in the IPV6CP phase=20
> of the PPP connection setup, it is redundant to perform duplicate=20
> address detection as a part of the IPv6 Stateless Autoconfiguration=20
> protocol [3].

The key phrase being "as long as the" (keeping in mind that a host can
use multiple interface identifiers simultaneously, so this is a per
interface identifier statement). =20

The problematic statement in 2472 is the one immediately after the above
quote:

>  Therefore it is recommended that for PPP links with the IPV6CP=20
> Interface-Identifier option enabled the default value of the=20
> DupAddrDetectTransmits autoconfiguration variable [3] be zero.

since the quote above doesn't take into account other interface
identifiers.

2472bis makes it much more clear by adding more text in between the two
statements, such that it restricts the first quote to applying to the
link-local address only, and narrows the second quote to only applying
when two other conditions are met such it doesn't apply to uses of PPP
like the problematic case I described.  (Basically where you have
knowledge that it is indeed a point-to-point not NBMA link, and where
you have knowledge that the router has no global addresses, hence the
change from 2472 is that skipping DAD would never be the default for an
arbitrary PPP link.)

> [...]
> <hs> OK. Router-to-router is already a well-known link that NUD can be

> skipped for as even 246bis says. Ole does not like router-to-host=20
> unicast NS NUD messages as well. I agree with him.

Currently RFC2461 doesn't support that view.  If this is the WG
consensus, then it would be good to put the rationale into a draft that
can update 2461.

-Dave

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



From ipv6-bounces@ietf.org Thu Jul 19 18:07: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 1IBe9j-0000D0-8L; Thu, 19 Jul 2007 18:07:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBe9h-0000Cv-IM
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:07:29 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBe9h-0006YP-1d
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:07:29 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6JM7SOb011573 for <ipv6@ietf.org>; Thu, 19 Jul 2007 22:07:28 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6JM7R4B005012
	for <ipv6@ietf.org>; Thu, 19 Jul 2007 18:07:27 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6JLmhkU009100; Thu, 19 Jul 2007 17:48:43 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6JLmhqT009097;
	Thu, 19 Jul 2007 17:48:43 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18079.56379.513849.305116@gargle.gargle.HOWL>
Date: Thu, 19 Jul 2007 17:48:43 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A417A@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A417A@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: varada@txc.com, JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	ipv6@ietf.org, Dave Thaler <dthaler@windows.microsoft.com>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> I am certainly not suggesting using more than one Link-Local address for
> a PPP client. All I am saying is if PPP uses IPV6CP and interface-id for
> Link-Local address, it is a little odd to use DAD for rest of the
> addresses assigned to the PPP client - the privacy and other addresses
> that Dave alluded to.

I don't see why it's odd.  Shouldn't we worry about misconfiguration
for those addresses as well?  Wouldn't it be "bad" if there were a
conflict with both peers choosing to use the same non-link-local
address?

> I don't want to change PPP in such a radical way -
> given the nature of the p2p link it's not so odd if Link-local address
> is negotiated using IPV6CP and other addresses of the PPP client use
> DAD. We should just make such facts clear in 2472bis.

I suppose making it clear that addresses besides the link-locals are
out of scope for IPV6CP would be helpful.  (I thought that was clear
enough from the existing text, but clearer still likely isn't wrong.)

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Thu Jul 19 18:42: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 1IBehH-0001lz-SD; Thu, 19 Jul 2007 18:42:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBehH-0001lr-55
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:42:11 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBehF-0004WX-LO
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:42:11 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6JMcxdK059672
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 20 Jul 2007 00:38:59 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 20 Jul 2007 00:40:49 +0200
To: Hemant Singh (shemant) <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: varada@txc.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 19-jul-2007, at 23:50, Hemant Singh (shemant) wrote:

> Never mind, I found what's 2462bis. I got hold of

> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt

I read this draft and I find it severely lacking. At the very least,  
to make using IPv6 over PPP even remotely usable, it should include  
the following options:

1. An MTU option. I know there is an MTU option for IPv4 over PPP but  
I can't find the specification real quick, it doesn't seem to be PPP  
spec but not in the IPCP spec either, or there must be a terminology  
issue such that searching for "MTU" is unsuccessful. But the IPv6 MTU  
shouldn't be tied to the IPv4 MTU anyway. All hardware imposes limits  
on packet sizes, and without a method to explicitly negotiate these  
limits implementations are forced to assume very conservative  
defaults. Routers can advertise an MTU option in RAs but hosts can't,  
a full negotiation is needed here.

2. DNS resolver addresses. Without the ability to resolve names IPv6  
is unusable.

I was thinking that it would be good if multiple full IPv6 addresses  
could be negotiated over IP6CP but upon further reflection that would  
quickly become prohibitively complex or slow: if addresses are  
negotiated one at a time, it would be too slow, and negotiating a set  
would be complex because individual addresses may be generated and  
retired at any time. So using standard IPv6 mechanisms would be  
better here.

But addresses used on the PPP link itself aren't all that  
interesting. A more pressing need is the one for a mechanism to  
negotiate a prefix that a router that terminates the PPP link on the  
client side can use on its LAN interface. I.e.:

     1           2                   3         4
host --<ether>-- customer PPP router --<PPP>-- ISP PPP router -- 
<internet>--

Currently, the interface identifiers in IP6CP and standard autoconfig  
allow for the creation of addresses 3 and 4, but what we really need  
is a prefix that holds addresses 1 and 2.

I can't stress enough that IPv6 over PPP in its current form is as  
good as unusable in practice, and this draft doesn't fix that.

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



From ipv6-bounces@ietf.org Thu Jul 19 18:52: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 1IBeqy-0007ns-OB; Thu, 19 Jul 2007 18:52:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBeqx-0007nn-K3
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:52:11 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBeqx-0007Q6-67
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:52:11 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Jul 2007 00:52:10 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPCHn0aQ/uCLZmdsb2JhbACPTQsKJA
X-IronPort-AV: i="4.16,558,1175464800"; 
	d="scan'208"; a="148524696:sNHT27107570"
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 l6JMqARb011973; 
	Fri, 20 Jul 2007 00:52:10 +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 l6JMq5kt024472; 
	Thu, 19 Jul 2007 22:52:05 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 l6JMq5mu028732; 
	Thu, 19 Jul 2007 23:52:05 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6JMq4Us028731;
	Thu, 19 Jul 2007 23:52:04 +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: James Carlson <james.d.carlson@sun.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
Date: Thu, 19 Jul 2007 23:52:04 +0100
In-Reply-To: <18079.54644.379204.366856@gargle.gargle.HOWL> (James Carlson's
	message of "Thu\, 19 Jul 2007 17\:19\:48 -0400")
Message-ID: <7t5y7hc6m7f.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=1494; t=1184885530;
	x=1185749530; c=relaxed/simple; s=amsdkim2001;
	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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=ctSy2gnlUHHm8Qg51/6jhJK7cLl0w6wb0jsQ0LKnhoU=;
	b=apyYfWDYWEuuXGMrHeZqQ++KeGHOsnP7PRb56etKO3BjPZQj1PUJfHN0yECvy+9EDxIWFzt1
	OQfd9cylU48uy+Neze4gOJQ50Xz5ypq9unj7vtWvRBX2ACUcv06s5NeA;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 I am saying is, if IPV6CP is used to negotiate one interface-id,
>> when multiple addresses, that Dave pointed out, are needed for the same
>> client, why not use IPV6CP to negotiate interface-id's for even these
>> addresses?
>
> We'd have to discuss that on the PPP list, but my take on it is that
> it'd likely be incompatible with existing implementations.  I don't
> know that anyone expects more than one IPV6CP Interface-Identifier
> option -- I know for certain that the open source ppp-2.4
> implementation wouldn't handle it right.
>
> I think it'd be pretty strange operationally as well.  You'd end up
> with multiple link-local addresses.
>
> I don't think I agree with pushing this issue down into PPP.  We don't
> do that for Ethernet, so why would PPP be special?

I second that. the whole point of ND not being ARP was to allow for the
same provisioning mechanisms to be used on multiple media. lets not go
down the IPCP rathole.

before we redesign the rest of IPv6. have we reached consensus on the
original question yet?  i.e is it required that an IPv6 node before
communicating with another node performs reachability detection using
NS/NA?

to me it is pretty clear that answer has to be no. in common deployments
a node doesn't know the next-hop address anyway.

if a clarification is needed to emphasise that the neighbour discovery
protocol must be supported on any multicast capable link, then I will
not object to that.

/ot

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



From ipv6-bounces@ietf.org Thu Jul 19 18: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 1IBexG-0003t4-MA; Thu, 19 Jul 2007 18:58:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBexF-0003sz-Hs
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:58:41 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBexE-0004qR-Rt
	for ipv6@ietf.org; Thu, 19 Jul 2007 18:58:41 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Jul 2007 00:58:40 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAN6In0aQ/uCKh2dsb2JhbACPTQEBCQon
X-IronPort-AV: i="4.16,558,1175464800"; 
	d="scan'208"; a="148524824:sNHT27374876"
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 l6JMweAP026907; 
	Fri, 20 Jul 2007 00:58:40 +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 l6JMwbkt025592; 
	Thu, 19 Jul 2007 22:58:40 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 l6JMwbIt028800; 
	Thu, 19 Jul 2007 23:58:37 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l6JMwZ7G028799;
	Thu, 19 Jul 2007 23:58:35 +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: Iljitsch van Beijnum <iljitsch@muada.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<F2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com>
Date: Thu, 19 Jul 2007 23:58:35 +0100
In-Reply-To: <F2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com> (Iljitsch van
	Beijnum's message of "Fri\, 20 Jul 2007 00\:40\:49 +0200")
Message-ID: <7t5tzs06lwk.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=2433; t=1184885920;
	x=1185749920; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=qMjQn9WlXpHS2HMyssxcDdQs+S85kzQQMLc3nSQuVmM=;
	b=CUf3141Xgpg8ZTrxNzNfElSC9aZRfFqtj78+7P2WoWwfogiYk5TKeXfkOwI003ollj1L3zLw
	/s4HcC/v7hQmLoh8y0R++A24tdx96BOsXuC/ryamzZC2k+suUc2zfv5D;
Authentication-Results: ams-dkim-1; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: varada@txc.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>> Never mind, I found what's 2462bis. I got hold of
>
>> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt
>
> I read this draft and I find it severely lacking. At the very least, to make
> using IPv6 over PPP even remotely usable, it should include  the following
> options:
>
> 1. An MTU option. I know there is an MTU option for IPv4 over PPP but
> I can't find the specification real quick, it doesn't seem to be PPP
> spec but not in the IPCP spec either, or there must be a terminology
> issue such that searching for "MTU" is unsuccessful. But the IPv6 MTU
> shouldn't be tied to the IPv4 MTU anyway. All hardware imposes limits
> on packet sizes, and without a method to explicitly negotiate these
> limits implementations are forced to assume very conservative
> defaults. Routers can advertise an MTU option in RAs but hosts can't,
> a full negotiation is needed here.

RFC1661, MRU option.

> 2. DNS resolver addresses. Without the ability to resolve names IPv6 is
> unusable.

use the same mechanism as on any other IPv6 link. i.e DHCP.

> I was thinking that it would be good if multiple full IPv6 addresses could be
> negotiated over IP6CP but upon further reflection that would  quickly become
> prohibitively complex or slow: if addresses are  negotiated one at a time, it
> would be too slow, and negotiating a set  would be complex because individual
> addresses may be generated and  retired at any time. So using standard IPv6
> mechanisms would be  better here.
>
> But addresses used on the PPP link itself aren't all that interesting. A more
> pressing need is the one for a mechanism to  negotiate a prefix that a router
> that terminates the PPP link on the  client side can use on its LAN
> interface. I.e.:
>
>     1           2                   3         4
> host --<ether>-- customer PPP router --<PPP>-- ISP PPP router --
> <internet>--
>
> Currently, the interface identifiers in IP6CP and standard autoconfig
> allow for the creation of addresses 3 and 4, but what we really need
> is a prefix that holds addresses 1 and 2.

DHCP prefix delegation.

> I can't stress enough that IPv6 over PPP in its current form is as good as
> unusable in practice, and this draft doesn't fix that.

none of the arguments you've put against PPP don't also equally apply to
any other IPv6 link type. and we already have the solutions.

/ot

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



From ipv6-bounces@ietf.org Thu Jul 19 19:27: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 1IBfP5-00049O-F6; Thu, 19 Jul 2007 19:27:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBfP3-00049J-Sg
	for ipv6@ietf.org; Thu, 19 Jul 2007 19:27:25 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBfP3-0008LE-Aj
	for ipv6@ietf.org; Thu, 19 Jul 2007 19:27:25 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6JNP9i3060539
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 20 Jul 2007 01:25:10 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <7t5tzs06lwk.fsf@gpk-xdm-001.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<F2064738-1644-! 4759-AFBA-CBEA08D75F4A@muada.com>
	<7t5tzs06lwk.fsf@gpk-xdm-001.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <18DBE0E9-5511-47C8-8971-CD401B306365@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 20 Jul 2007 01:27:00 +0200
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: varada@txc.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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-jul-2007, at 0:58, Ole Troan wrote:

>>> RFC1661, MRU option.

Ah, ok, that's an LCP option so it covers the hardware side of  
things. Still better to have different maximum packet sizes for v4  
and v6, though.

>> 2. DNS resolver addresses. Without the ability to resolve names  
>> IPv6 is
>> unusable.

> use the same mechanism as on any other IPv6 link. i.e DHCP.

That's insanity. I'm not even going to bother discussing such nonsense.

>> Currently, the interface identifiers in IP6CP and standard autoconfig
>> allow for the creation of addresses 3 and 4, but what we really need
>> is a prefix that holds addresses 1 and 2.

> DHCP prefix delegation.

Well, I don't have to implement this stuff so maybe I shouldn't  
complain. But if I did, I know that I wouldn't want to implement both  
versions of DHCPv6, include moon phase sensors to decide which  
variant to use and then execute it after I've done PPP and stateless  
autoconfig negotiations if the alternative is defining one little new  
NCP option.

>> I can't stress enough that IPv6 over PPP in its current form is as  
>> good as
>> unusable in practice, and this draft doesn't fix that.

> none of the arguments you've put against PPP don't also equally  
> apply to
> any other IPv6 link type. and we already have the solutions.

Wearing a protocol designer hat that's true, if you don't mind  
running a bunch of protocols, wearing an operator or end user hat you  
only see boxes that talk to each other and then fail to do for IPv6  
what they've been able to do for IPv4 for the past decade and a half.  
We only have a bunch of partial solutions and the parts don't fit  
together particularly well even in theory, and not at all in practice  
in current implementations.

But apparently nobody feels responsible for the thing as a whole. My  
conclusion is that if you want to do IPv6 over PPP, you should run  
IPv4 over PPP and then tunnel the IPv6 over IPv4. Anything else only  
leads to headaches.

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



From ipv6-bounces@ietf.org Thu Jul 19 20:52: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 1IBgiv-0002ft-6s; Thu, 19 Jul 2007 20:52:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBgit-0002fh-TH
	for ipv6@ietf.org; Thu, 19 Jul 2007 20:51:59 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBgit-0007rD-4Y
	for ipv6@ietf.org; Thu, 19 Jul 2007 20:51:59 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6K0pvfq026403 for <ipv6@ietf.org>; Fri, 20 Jul 2007 00:51:58 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6K0pvmG022327
	for <ipv6@ietf.org>; Thu, 19 Jul 2007 20:51:57 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6K0aogx009809; Thu, 19 Jul 2007 20:36:50 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6K0anxd009806;
	Thu, 19 Jul 2007 20:36:49 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18080.929.364693.274894@gargle.gargle.HOWL>
Date: Thu, 19 Jul 2007 20:36:49 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <18DBE0E9-5511-47C8-8971-CD401B306365@muada.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<7t5tzs06lwk.fsf@gpk-xxdm-001.cisco.com>
	<18DBE0E9-5511-47C8-8971-CD401B306365@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: Dave Thaler <dthaler@windows.microsoft.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>, varada@txc.com
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Iljitsch van Beijnum writes:
> On 20-jul-2007, at 0:58, Ole Troan wrote:
> 
> >>> RFC1661, MRU option.
> 
> Ah, ok, that's an LCP option so it covers the hardware side of  
> things. Still better to have different maximum packet sizes for v4  
> and v6, though.

That sounds like an IP configuration issue, not a PPP issue.  PPP
simply negotiates link MRU in both directions and reports that to the
network layers above (IPv4 and IPv6).  Those network layers can then
do whatever's appropriate for them.

Having a special MTU option just for IPv6 almost certainly wouldn't
fly in the pppext group.

> >> 2. DNS resolver addresses. Without the ability to resolve names  
> >> IPv6 is
> >> unusable.
> 
> > use the same mechanism as on any other IPv6 link. i.e DHCP.
> 
> That's insanity. I'm not even going to bother discussing such nonsense.

Why is using an existing, well-understood, and well-supported protocol
for its intended purpose "insanity?"

The pppext working group has considered PPP extensions for several
application layer protocols (such as DNS and SIP) multiple times, and
working group consensus has rejected those options every time for
exactly the same reason: BOOTP and DHCP work fine on PPP, and they're
already-defined protocols.  We don't need multiple conflicting
mechanisms to do the same job.

The only exception to this is the Microsoft-proprietary individual
submission that was published as RFC 1877.  Many implementations
grudgingly support this because of MS market power, but it's a brutal
hack, and I doubt similar things will get through.

The previous poster is right; DHCP is the correct answer here.

> >> Currently, the interface identifiers in IP6CP and standard autoconfig
> >> allow for the creation of addresses 3 and 4, but what we really need
> >> is a prefix that holds addresses 1 and 2.
> 
> > DHCP prefix delegation.
> 
> Well, I don't have to implement this stuff so maybe I shouldn't  
> complain. But if I did, I know that I wouldn't want to implement both  
> versions of DHCPv6, include moon phase sensors to decide which  
> variant to use and then execute it after I've done PPP and stateless  
> autoconfig negotiations if the alternative is defining one little new  
> NCP option.

I think this should be taken to the pppext list -- after you've read
through the archives, of course.

DHCP works fine on PPP links.  BOOTP over SLIP was in use *LONG*
before PPP ever showed up, for just this purpose.

"One little new NCP option" completely ignores the architectural
issues here, which include keeping duplicate configuration information
on DHCP servers in sync with PPP servers (hard in a non-trivial
deployment), figuring out what a PPP router should do with the options
(when the real client is well behind the router), and, of course,
deployment (nothing currently implements such an option, though many
systems already have both PPP and DHCP).

Quite intentionally, we do not invent new mechanisms when there are
old ones that will serve the purposes adequately well, because
complexity is the enemy.  This is one of those cases.

> Wearing a protocol designer hat that's true, if you don't mind  
> running a bunch of protocols, wearing an operator or end user hat you  
> only see boxes that talk to each other and then fail to do for IPv6  
> what they've been able to do for IPv4 for the past decade and a half.  
> We only have a bunch of partial solutions and the parts don't fit  
> together particularly well even in theory, and not at all in practice  
> in current implementations.

That sounds like an implementation quality issue, not a protocol
issue.

> But apparently nobody feels responsible for the thing as a whole. My  
> conclusion is that if you want to do IPv6 over PPP, you should run  
> IPv4 over PPP and then tunnel the IPv6 over IPv4. Anything else only  
> leads to headaches.

... and that sounds like FUD.  Many of us have been using IPv6 over
PPP for years, without the sorts of "headaches" you're talking about.

In any event, I think your complaints about PPP itself would be better
addressed within the PPP Extensions working group.  I don't think
you'll find the support you're looking for there, but at least the
group has a better history with these very issues.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Fri Jul 20 15:17: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 1IBxyk-0004qM-8d; Fri, 20 Jul 2007 15:17:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBxyj-0004mg-Ez
	for ipv6@ietf.org; Fri, 20 Jul 2007 15:17:29 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IBxyj-0008C4-3B
	for ipv6@ietf.org; Fri, 20 Jul 2007 15:17:29 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out3.apple.com (Postfix) with ESMTP id 4FDDEC45CEF
	for <ipv6@ietf.org>; Fri, 20 Jul 2007 12:17:26 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 3E925100AC
	for <ipv6@ietf.org>; Fri, 20 Jul 2007 12:17:26 -0700 (PDT)
X-AuditID: 11807124-a4fb7bb0000007f3-c3-46a10a4669bb
Received: from [17.206.50.117] (il0602f-dhcp117.apple.com [17.206.50.117])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 368F01008B
	for <ipv6@ietf.org>; Fri, 20 Jul 2007 12:17:26 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <18080.929.364693.274894@gargle.gargle.HOWL>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<7t5tzs06lwk.fsf @gpk-xxdm-001.cisco.com>
	<18DBE0E9-5511-47C8-8971-CD401B306365@muada.com>
	<18080.929.364693.274894@gargle.gargle.HOWL>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A1DA3BA0-5C6D-474A-902A-8B3F288A1DBC@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Fri, 20 Jul 2007 12:17:20 -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: 9466e0365fc95844abaf7c3f15a05c7d
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 19, 2007, at 17:36, James Carlson wrote:
> Iljitsch van Beijnum writes:
>>
>> But apparently nobody feels responsible for the thing as a whole.  
>> My conclusion is that if you want to do IPv6 over PPP, you should  
>> run IPv4 over PPP and then tunnel the IPv6 over IPv4. Anything  
>> else only leads to headaches.
>
> ... and that sounds like FUD.  Many of us have been using IPv6 over  
> PPP for years, without the sorts of "headaches" you're talking about.

It might be worth noting here the reason that Apple AirPort Extreme  
802.11n base stations have a patch to their PPPoE stacks to prevent  
negotiation of IP6CP.

Some PPPoE access concentrators in service with ISP's today refuse to  
negotiate IPCP properly if IP6CP is also attempted.  Rather than work  
around that failurage, we just disable native IPv6 over PPPoE, and we  
tunnel IPv6 over IPv4 just like Mr. van Beijnum suggests.  We are  
unaware of any commercial IPv6 over PPPoE service providers today,  
and nobody has filed any bugs against the AirPort base station  
regarding this decision.


--
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 Jul 20 16:09: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 1IBynB-0002du-BK; Fri, 20 Jul 2007 16:09:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBynA-0002Yl-Fn
	for ipv6@ietf.org; Fri, 20 Jul 2007 16:09:36 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IByn9-0000l6-IC
	for ipv6@ietf.org; Fri, 20 Jul 2007 16:09:36 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6KK7eAA080445
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 20 Jul 2007 22:07:41 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <18080.929.364693.274894@gargle.gargle.HOWL>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<7t5tzs06lwk.fs! f@gpk-xxdm-001.cisco.com>
	<18DBE0E9-5511-47C8-8971-CD401B306365@muada.com>
	<18080.929.364693.274894@gargle.gargle.HOWL>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5DEDBA29-0F5D-4B88-966F-C54E786CAA6C@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Fri, 20 Jul 2007 22:09:30 +0200
To: James Carlson <james.d.carlson@sun.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: varada@txc.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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-jul-2007, at 2:36, James Carlson wrote:

>> Still better to have different maximum packet sizes for v4
>> and v6, though.

> That sounds like an IP configuration issue, not a PPP issue.

Isn't that what the NCPs are for, to provide the necessary glue  
between the base PPP and what the layer 3 protocol needs?

> Having a special MTU option just for IPv6 almost certainly wouldn't
> fly in the pppext group.

Why not?

>>> use the same mechanism as on any other IPv6 link. i.e DHCP.

>> That's insanity. I'm not even going to bother discussing such  
>> nonsense.

> Why is using an existing, well-understood, and well-supported protocol
> for its intended purpose "insanity?"

Discussing why you're not discussing something kinda defeats the  
purpose.

But let me observe that this isn't the way how things work for IPv4  
either.

> The pppext working group has considered PPP extensions for several
> application layer protocols (such as DNS and SIP) multiple times, and
> working group consensus has rejected those options every time for
> exactly the same reason: BOOTP and DHCP work fine on PPP,

Not really. Those need a server, which means that if you want to use  
them on a point-to-point link, the other side of that link MUST  
support bootp/dhcp/dhcpv6, if not as a full server then as a relay.  
And again, running IPv4 and everything that that customarily entails  
(DNS) over PPP doesn't require DHCP. Moreover, DHCP support in  
current IPv6 implementations is extremely limited.

> and they're
> already-defined protocols.  We don't need multiple conflicting
> mechanisms to do the same job.

The notion that DHCPv6 is a "conflicting mechanism" for IPv6 over PPP  
makes no sense at all.

> DHCP works fine on PPP links.  BOOTP over SLIP was in use *LONG*
> before PPP ever showed up, for just this purpose.

So what you're saying is that there was no reason to implement PPP in  
the first place?

I've come to know the IETF as a rather conservative place but I've  
never seen it get this bad.

> Quite intentionally, we do not invent new mechanisms when there are
> old ones that will serve the purposes adequately well, because
> complexity is the enemy.  This is one of those cases.

Have you read the DHCPv6 spec?

Running DHCPv6, stateless autoconfig and IP6CP each to do a little  
part of a bigger whole is MUCH more complex than simply making IP6CP  
do it all. (Although I can see how using stateless autoconfig would  
be preferable to implementing negotiation of multiple addresses with  
different lifetimes in IP6CP. However, negotiating a prefix to be  
delegated would be simple enough.)

>> Wearing a protocol designer hat that's true, if you don't mind
>> running a bunch of protocols, wearing an operator or end user hat you
>> only see boxes that talk to each other and then fail to do for IPv6
>> what they've been able to do for IPv4 for the past decade and a half.
>> We only have a bunch of partial solutions and the parts don't fit
>> together particularly well even in theory, and not at all in practice
>> in current implementations.

> That sounds like an implementation quality issue, not a protocol
> issue.

A protocol is a set of interactions designed to do something useful.  
Having several protocols that together are capable of doing said  
useful thing isn't enough, someone has to specify how it all ties  
together. One way to solve that would be a document (written under  
the IETF umbrella or otherwise) that specifies how different  
protocols work together, but in this particular case extending one  
protocol so it can do what's required in most typical installations  
makes much more sense to me.

>> But apparently nobody feels responsible for the thing as a whole. My
>> conclusion is that if you want to do IPv6 over PPP, you should run
>> IPv4 over PPP and then tunnel the IPv6 over IPv4. Anything else only
>> leads to headaches.

> ... and that sounds like FUD.  Many of us have been using IPv6 over
> PPP for years, without the sorts of "headaches" you're talking about.

Does one end receive address configuration from the other end? I'm  
willing to bet this isn't the case. Sure, shuttling the packets back  
and forth works just fine. But SLIP could do that, too.

> In any event, I think your complaints about PPP itself would be better
> addressed within the PPP Extensions working group.  I don't think
> you'll find the support you're looking for there, but at least the
> group has a better history with these very issues.

I'm already on way too many mailinglists. I've sent feedback to the  
draft author(s) and I'm willing to provide further feedback if  
desired but that has to be it for this subject.

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



From ipv6-bounces@ietf.org Sat Jul 21 20:00: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 1ICOrn-00047l-IX; Sat, 21 Jul 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 1ICOrl-00047S-EI
	for ipv6@ietf.org; Sat, 21 Jul 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 1ICOrl-0003pI-2h
	for ipv6@ietf.org; Sat, 21 Jul 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 34C4C28463
	for <ipv6@ietf.org>; Sun, 22 Jul 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 22 Jul 2007 00:00:04 +0000
Message-Id: <20070722000004.34C4C28463@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
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
--------+------+--------+----------+------------------------
 23.91% |   11 | 22.45% |    74859 | james.d.carlson@sun.com
 17.39% |    8 | 24.13% |    80458 | shemant@cisco.com
 17.39% |    8 | 16.64% |    55500 | ot@cisco.com
 15.22% |    7 | 15.28% |    50947 | dthaler@windows.microsoft.com
 10.87% |    5 | 10.01% |    33396 | iljitsch@muada.com
  2.17% |    1 |  1.97% |     6579 | brian.e.carpenter@gmail.com
  2.17% |    1 |  1.93% |     6420 | jinmei@isl.rdc.toshiba.co.jp
  2.17% |    1 |  1.78% |     5921 | jhw@apple.com
  2.17% |    1 |  1.57% |     5225 | sra+ipng@hactrn.net
  2.17% |    1 |  1.50% |     5004 | brian@innovationslab.net
  2.17% |    1 |  1.47% |     4886 | tim@mentat.com
  2.17% |    1 |  1.28% |     4279 | msa@moth.iki.fi
--------+------+--------+----------+------------------------
100.00% |   46 |100.00% |   333474 | 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 Jul 22 22: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 1ICnCy-0005jy-OG; Sun, 22 Jul 2007 21:59:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICnCy-0005js-0G
	for ipv6@ietf.org; Sun, 22 Jul 2007 21:59:36 -0400
Received: from transfire.transwitch.com ([63.119.242.254]
	helo=smtphub.transwitch.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICnCx-0007RJ-Ds
	for ipv6@ietf.org; Sun, 22 Jul 2007 21:59:35 -0400
Received: from [172.18.253.131] (helo=[127.0.0.1])
	by smtphub.transwitch.com with esmtp (Exim 4.34)
	id 1ICnCn-0008Ca-QK; Sun, 22 Jul 2007 21:59:26 -0400
Message-ID: <46A40BD1.6010708@txc.com>
Date: Sun, 22 Jul 2007 22:00:49 -0400
From: srihari varada <varada@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<F2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com>
In-Reply-To: <F2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com>
X-TXC-MailScanner-Information: Please contact the SysAdmin group for more
	information
X-TXC-MailScanner: Not scanned: please contact your Sysadmin group for details
X-MailScanner-From: varada@txc.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: varada@transwitch.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============0235668573=="
Errors-To: ipv6-bounces@ietf.org

--===============0235668573==
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">The subject took a detour from its original context
of the need for address resolution through the Neighbor Discovery
protocol. <br>
<br>
The author is appreciative of the belated feedback though the last call
for its parent draft (<i>draft-ietf-ipv6-over-ppp-v2.txt</i>)&nbsp; took
place a few years ago with the draft by itself was a result of the
collaborative effort of the IPv6 community (please check the archives
of IPv6 WG dating back to 2004). <br>
<br>
The encouraging aspect, however, is that framework of the <i>draft-ietf-ipv6-over-ppp-v3.txt
</i>specification allows for extensibility in the IPv6CP protocol
through the definition of new configuration options. Please find the
following statement to this effect in the said draft specification. <br>
</font>
<blockquote><font face="Arial">"The only IPV6CP option defined in this
document is the Interface Identifier.&nbsp; Any other IPV6CP configuration
options that can be defined over time are to be defined in separate
documents." <br>
  </font></blockquote>
<font face="Arial">If you strongly feel the need for option extensions,
it can be done so through new I-D(s). The value proposition of these
option extensions can then be discussed. As it is, the suggested
extensions are out of the scope of the specification.<br>
<br>
Regards,<br>
<br>
Srihari Varada</font><br>
<br>
<br>
Iljitsch van Beijnum wrote:
<blockquote cite="midF2064738-1644-4759-AFBA-CBEA08D75F4A@muada.com"
 type="cite">On 19-jul-2007, at 23:50, Hemant Singh (shemant) wrote:
  <br>
  <br>
  <blockquote type="cite">Never mind, I found what's 2462bis. I got
hold of
    <br>
  </blockquote>
  <br>
  <blockquote type="cite"><a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt">http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt</a>
    <br>
  </blockquote>
  <br>
I read this draft and I find it severely lacking. At the very least,&nbsp;
to make using IPv6 over PPP even remotely usable, it should include&nbsp;
the following options:
  <br>
  <br>
1. An MTU option. I know there is an MTU option for IPv4 over PPP but&nbsp;
I can't find the specification real quick, it doesn't seem to be PPP&nbsp;
spec but not in the IPCP spec either, or there must be a terminology&nbsp;
issue such that searching for "MTU" is unsuccessful. But the IPv6 MTU&nbsp;
shouldn't be tied to the IPv4 MTU anyway. All hardware imposes limits&nbsp;
on packet sizes, and without a method to explicitly negotiate these&nbsp;
limits implementations are forced to assume very conservative&nbsp;
defaults. Routers can advertise an MTU option in RAs but hosts can't,&nbsp;
a full negotiation is needed here.
  <br>
  <br>
2. DNS resolver addresses. Without the ability to resolve names IPv6&nbsp;
is unusable.
  <br>
  <br>
I was thinking that it would be good if multiple full IPv6 addresses&nbsp;
could be negotiated over IP6CP but upon further reflection that would&nbsp;
quickly become prohibitively complex or slow: if addresses are&nbsp;
negotiated one at a time, it would be too slow, and negotiating a set&nbsp;
would be complex because individual addresses may be generated and&nbsp;
retired at any time. So using standard IPv6 mechanisms would be&nbsp; better
here.
  <br>
  <br>
But addresses used on the PPP link itself aren't all that&nbsp; interesting.
A more pressing need is the one for a mechanism to&nbsp; negotiate a prefix
that a router that terminates the PPP link on the&nbsp; client side can use
on its LAN interface. I.e.:
  <br>
  <br>
&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
  <br>
host --&lt;ether&gt;-- customer PPP router --&lt;PPP&gt;-- ISP PPP
router -- &lt;internet&gt;--
  <br>
  <br>
Currently, the interface identifiers in IP6CP and standard autoconfig&nbsp;
allow for the creation of addresses 3 and 4, but what we really need&nbsp;
is a prefix that holds addresses 1 and 2.
  <br>
  <br>
I can't stress enough that IPv6 over PPP in its current form is as&nbsp;
good as unusable in practice, and this draft doesn't fix that.
  <br>
  <br>
</blockquote>
<br>
</body>
</html>



--===============0235668573==
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
--------------------------------------------------------------------

--===============0235668573==--



From ipv6-bounces@ietf.org Sun Jul 22 22:17: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 1ICnUg-0002mX-IM; Sun, 22 Jul 2007 22:17:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICnUf-0002mI-Ef
	for ipv6@ietf.org; Sun, 22 Jul 2007 22:17:53 -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 1ICnUf-0001cc-1M
	for ipv6@ietf.org; Sun, 22 Jul 2007 22:17:53 -0400
Received: from coconut.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id 5DC27233C5;
	Mon, 23 Jul 2007 11:17:50 +0900 (JST)
To: srihari varada <varada@txc.com>
In-reply-to: varada's message of Sun,
	22 Jul 2007 22:00:49 -0400. <46A40BD1.6010708@txc.com> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Date: Mon, 23 Jul 2007 11:17:50 +0900
Message-Id: <20070723021750.5DC27233C5@coconut.itojun.org>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: varada@transwitch.com, Iljitsch van Beijnum <iljitsch@muada.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 was repeatedly pointed out by Steve Deering and folks in pppext wg
	that:
	- they would like to simplify PPP and tons of PPP options in v4 was
	  a big mitake
	- global address assignment, resolver IPv6 address information and
	  other info has to be passed by DHCPv6 or DHCPv6-lite

	i do not want to see another round of the battle.  we had it enough
	in 1998-2000 timeframe.

itojun

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



From ipv6-bounces@ietf.org Sun Jul 22 23:22: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 1ICoUd-0006WP-KN; Sun, 22 Jul 2007 23:21:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICoUb-0006W8-H2
	for ipv6@ietf.org; Sun, 22 Jul 2007 23:21:53 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICoUb-0000Mk-1B
	for ipv6@ietf.org; Sun, 22 Jul 2007 23:21:53 -0400
Received: from [192.168.251.111] (mpwr-static-216.70.191.48.mpowercom.net
	[216.70.191.48] (may be forged)) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l6N3Jppb028054
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 23 Jul 2007 05:19:53 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20070723021750.5DC27233C5@coconut.itojun.org>
References: <20070723021750.5DC27233C5@coconut.itojun.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DB36BAFA-6528-4670-A972-805C20430EF4@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sun, 22 Jul 2007 22:21:44 -0500
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Status: No, score=-2.6 required=3.5 tests=BAYES_00 autolearn=ham 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: varada@transwitch.com, srihari varada <varada@txc.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 22-jul-2007, at 21:17, Jun-ichiro itojun Hagino wrote:

> 	it was repeatedly pointed out by Steve Deering and folks in pppext wg
> 	that:
> 	- they would like to simplify PPP and tons of PPP options in v4 was
> 	  a big mitake
> 	- global address assignment, resolver IPv6 address information and
> 	  other info has to be passed by DHCPv6 or DHCPv6-lite

> 	i do not want to see another round of the battle.  we had it enough
> 	in 1998-2000 timeframe.

It has been repeatedly pointed out by ME that PPP for IPv6 as it  
exists today (in a context where DHCPv6 servers and clients and  
operational procedures to make them work together don't exist on a  
sufficiently wide scale and not to mention the differing  
interpretations on the use of ND/RA) so PPP for IPv6 isn't used to  
any measurable degree. Hence the return of investment on writing the  
specifications and implementations is close to zero.

Answering the questions of whether this constitutes a problem, and if  
so, whether it should be fixed, and if so, how, are left as an  
exercise for the reader.

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



From ipv6-bounces@ietf.org Mon Jul 23 07:25: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 1ICw1v-0003aJ-OK; Mon, 23 Jul 2007 07:24:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICw1q-0003Z8-9G
	for ipv6@ietf.org; Mon, 23 Jul 2007 07:24:42 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICw1o-0002wY-Le
	for ipv6@ietf.org; Mon, 23 Jul 2007 07:24:42 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l6NBOdC7011385 for <ipv6@ietf.org>; Mon, 23 Jul 2007 11:24:39 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6NBOdKB019851
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 07:24:39 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6NBH4pN014217; Mon, 23 Jul 2007 07:17:04 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6NBGg6F014214;
	Mon, 23 Jul 2007 07:16:42 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18084.36378.289729.266061@gargle.gargle.HOWL>
Date: Mon, 23 Jul 2007 07:16:42 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <5DEDBA29-0F5D-4B88-966F-C54E786CAA6C@muada.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4115@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A494@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4187@xmb-rtp-20e.amer.cisco.com>
	<18DBE0E9-5511-47C8-89971-CD401B306365@muada.com>
	<18080.929.364693.274894@gargle.gargle.HOWL>
	<5DEDBA29-0F5D-4B88-966F-C54E786CAA6C@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Cc: varada@txc.com, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Dave Thaler <dthaler@windows.microsoft.com>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Iljitsch van Beijnum writes:
> On 20-jul-2007, at 2:36, James Carlson wrote:
> 
> >> Still better to have different maximum packet sizes for v4
> >> and v6, though.
> 
> > That sounds like an IP configuration issue, not a PPP issue.
> 
> Isn't that what the NCPs are for, to provide the necessary glue  
> between the base PPP and what the layer 3 protocol needs?

They're supposed to provide the necessities, not just random features
that "might" be interesting on a particular implementation.  In this
case, other link layers (such as Ethernet) neither supply nor need
this special IPv6-only MTU feature, so why should PPP need it?

> > Having a special MTU option just for IPv6 almost certainly wouldn't
> > fly in the pppext group.
> 
> Why not?

As above; it's not needed on other link layers, so it'd be surprising
to see it in PPP.  You're certainly welcome to propose it in the PPP
extensions working group, of course, to see what the rest of the folks
there think.

> >>> use the same mechanism as on any other IPv6 link. i.e DHCP.
> 
> >> That's insanity. I'm not even going to bother discussing such  
> >> nonsense.
> 
> > Why is using an existing, well-understood, and well-supported protocol
> > for its intended purpose "insanity?"
> 
> Discussing why you're not discussing something kinda defeats the  
> purpose.

I don't think that's true at all.  It keeps you from inventing
"solutions" to problems that are in fact already solved.

> But let me observe that this isn't the way how things work for IPv4  
> either.

Are you referring to RFC 1877?  If so, then please do note that the
document wasn't a product of the PPP extensions working group.  It was
an individual submission from a Microsoft engineer.  It describes a
Microsoft-proprietary "feature" that negotiates name server addresses
(an application-layer issue) in PPP.

It sets no precedent.

> > The pppext working group has considered PPP extensions for several
> > application layer protocols (such as DNS and SIP) multiple times, and
> > working group consensus has rejected those options every time for
> > exactly the same reason: BOOTP and DHCP work fine on PPP,
> 
> Not really. Those need a server, which means that if you want to use  
> them on a point-to-point link, the other side of that link MUST  
> support bootp/dhcp/dhcpv6, if not as a full server then as a relay.  

Correct.  That "server" consists of sending and receiving simple UDP
messages.

The rest of the "server" is *EXACTLY* the configuration information
that you would have put into PPP.

Thus, I claim that if you can do this for PPP, you can just as easily
do it for BOOTP.

> And again, running IPv4 and everything that that customarily entails  
> (DNS) over PPP doesn't require DHCP. Moreover, DHCP support in  
> current IPv6 implementations is extremely limited.

That's not a good reason to invent yet another protocol that (by
definition) is not implemented anywhere.  The PPP change you're
talking about is in fact a new protocol.  Nobody has this feature
today.  It's thus even worse than DHCPv6.

> > and they're
> > already-defined protocols.  We don't need multiple conflicting
> > mechanisms to do the same job.
> 
> The notion that DHCPv6 is a "conflicting mechanism" for IPv6 over PPP  
> makes no sense at all.

I never said such a thing.

DHCPv6 is a conflicting mechanism for configuring application layer
protocols (such as DNS) via PPP.

DHCPv6 doesn't conflict with IPv6 over PPP.  It just conflicts with
your proposal to negotiate DNS addresses and other such unnecessary
bits.

> > DHCP works fine on PPP links.  BOOTP over SLIP was in use *LONG*
> > before PPP ever showed up, for just this purpose.
> 
> So what you're saying is that there was no reason to implement PPP in  
> the first place?

Of course not.  Please see above.  There is no reason to use PPP as a
dumping ground for random things that it "could" negotiate.

> I've come to know the IETF as a rather conservative place but I've  
> never seen it get this bad.

One of us clearly doesn't understand how IETF protocols are designed.

> > Quite intentionally, we do not invent new mechanisms when there are
> > old ones that will serve the purposes adequately well, because
> > complexity is the enemy.  This is one of those cases.
> 
> Have you read the DHCPv6 spec?

You could say that.

I designed, implemented, and shipped the DHCPv6 implementation on
Solaris.  As part of doing that, yes, I read the DHCPv6 specification
many times.

> Running DHCPv6, stateless autoconfig and IP6CP each to do a little  
> part of a bigger whole is MUCH more complex than simply making IP6CP  
> do it all. (Although I can see how using stateless autoconfig would  
> be preferable to implementing negotiation of multiple addresses with  
> different lifetimes in IP6CP. However, negotiating a prefix to be  
> delegated would be simple enough.)

I suggest you take the argument to the PPP extensions working group.
This isn't the right place for this argument.

However, in real implementations, designers will end up being *forced*
to implement both the PPP-based hack that you're suggesting along with
DHCPv6.  They'll end up with both mechanisms in order to be maximally
interoperable with the rest of the systems in the field, which may end
up using either of the two mechanisms.

Worse still, systems that implement both will need to figure out how
to arbitrate between conflicting results.  What if PPP gives you one
DNS server, but DHCP gives you another?  Which one is "right?"

That's a poor outcome, and much more complex than the simple solution,
which is to use the existing, already defined, and (in many places)
already implemented solutions.

> >> Wearing a protocol designer hat that's true, if you don't mind
> >> running a bunch of protocols, wearing an operator or end user hat you
> >> only see boxes that talk to each other and then fail to do for IPv6
> >> what they've been able to do for IPv4 for the past decade and a half.
> >> We only have a bunch of partial solutions and the parts don't fit
> >> together particularly well even in theory, and not at all in practice
> >> in current implementations.
> 
> > That sounds like an implementation quality issue, not a protocol
> > issue.
> 
> A protocol is a set of interactions designed to do something useful.  
> Having several protocols that together are capable of doing said  
> useful thing isn't enough, someone has to specify how it all ties  
> together. One way to solve that would be a document (written under  
> the IETF umbrella or otherwise) that specifies how different  
> protocols work together, but in this particular case extending one  
> protocol so it can do what's required in most typical installations  
> makes much more sense to me.

If you want to write a BCP, feel free to do so.  However, if you're
talking about adding functional duplication into PPP, then (A) this
mailing list isn't the right place to discuss it and (B) you're going
to have quite an uphill battle.

I _strongly_ recommend that you search the PPP extensions working
group mailing list archives.  We've dealt with this issue many times
in the past.

> >> But apparently nobody feels responsible for the thing as a whole. My
> >> conclusion is that if you want to do IPv6 over PPP, you should run
> >> IPv4 over PPP and then tunnel the IPv6 over IPv4. Anything else only
> >> leads to headaches.
> 
> > ... and that sounds like FUD.  Many of us have been using IPv6 over
> > PPP for years, without the sorts of "headaches" you're talking about.
> 
> Does one end receive address configuration from the other end? I'm  
> willing to bet this isn't the case. Sure, shuttling the packets back  
> and forth works just fine. But SLIP could do that, too.

I'm not sure I understand the question.

You get an 'Interface-Identifier' that's guaranteed to be unique for
the link, which the PPP implementation then hands over to IPv6 to form
link-local addresses.

What problem do you see?  Is it a problem in assigning addresses with
a different scope?  If so, then that problem exists on all link
layers.  You have to have one system configured to be a "router" and
handing out prefixes via RAs so that the other can form global scope
addresses and/or run DHCPv6.  PPP isn't different here.

> > In any event, I think your complaints about PPP itself would be better
> > addressed within the PPP Extensions working group.  I don't think
> > you'll find the support you're looking for there, but at least the
> > group has a better history with these very issues.
> 
> I'm already on way too many mailinglists.

If it helps, it's extraordinarily low traffic, because PPP itself is a
mature technology.  We have only a couple of discussions per year.

> I've sent feedback to the  
> draft author(s) and I'm willing to provide further feedback if  
> desired but that has to be it for this subject.

In that case, I give up.  I've tried to help.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 10:14: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 1ICyf3-0000qs-QQ; Mon, 23 Jul 2007 10:13:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICyf2-0000qh-TJ
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:13:20 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICyf2-00069I-Aw
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:13:20 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 23 Jul 2007 07:13:19 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMZUpEarR7PD/2dsb2JhbAA
X-IronPort-AV: i="4.16,570,1175497200"; 
	d="scan'208"; a="186907221:sNHT38579040"
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 l6NEDJWr024201; 
	Mon, 23 Jul 2007 07:13:19 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l6NED8Sh010719;
	Mon, 23 Jul 2007 14:13:10 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); 
	Mon, 23 Jul 2007 10:13:09 -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, 23 Jul 2007 10:13:08 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036A479B@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <7t5y7hc6m7f.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfKV3FkU8rueuDBT76v0EoWAOybZQC2bCFA
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com><18079.53002.425765.815419@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com><18079.54644.379204.366856@gargle.gargle.HOWL>
	<7t5y7hc6m7f.fsf@gpk-xdm-001.cisco.co m>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ole Troan (otroan)" <otroan@cisco.com>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 23 Jul 2007 14:13:09.0590 (UTC)
	FILETIME=[98EACF60:01C7CD33]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2511; t=1185199999;
	x=1186063999; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20; bh=npB23djQCL4Lg4MgvXxLF723EbXkNOnWAb32JR/MqjA=;
	b=sNd31ZoRYvVci6UjolqUj/OUf1APoJAB/Qy5uXYfM3ARwXQylia+hzLUESb/1+kUsuQov3d6
	lORpLlSqmWw1eDUoPofXMtDFg9RTMK2ps5+2EQ9/cNQPMoAvSZ5mirXZ;
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: 0a7aa2e6e558383d84476dc338324fab
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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's clear the air. I agree with Srihari's email on IPV6CP and new
options. Now let's see what the PPP interop issues are:

The sender PPP node is ND compliant when it issues a unicast NS for NUD
before sending any data. The PPP peer of this sending node has a bug as
to why the peer is not responding with an NA? Let's focus on this
interop issue rather than asking for 2461bis or PPP to be changed.=20

It's an orthogonal issue to ask if one should change 2461bis that
requires an IPv6 node to perform reachability detection before
communicating with another node. As for any changes needed by PPP and
IPV6CP, do note, DHCPv6 cannot be used for other options and addresses
in PPP if the client is SLAAC.

Hemant

-----Original Message-----
From: Ole Troan (otroan)=20
Sent: Thursday, July 19, 2007 6:52 PM
To: James Carlson
Cc: Hemant Singh (shemant); varada@txc.com; JINMEI Tatuya / ????;
ipv6@ietf.org; Dave Thaler
Subject: Re: Neighbor Discovery and PPP links

>> All I am saying is, if IPV6CP is used to negotiate one interface-id,=20
>> when multiple addresses, that Dave pointed out, are needed for the=20
>> same client, why not use IPV6CP to negotiate interface-id's for even=20
>> these addresses?
>
> We'd have to discuss that on the PPP list, but my take on it is that=20
> it'd likely be incompatible with existing implementations.  I don't=20
> know that anyone expects more than one IPV6CP Interface-Identifier=20
> option -- I know for certain that the open source ppp-2.4=20
> implementation wouldn't handle it right.
>
> I think it'd be pretty strange operationally as well.  You'd end up=20
> with multiple link-local addresses.
>
> I don't think I agree with pushing this issue down into PPP.  We don't

> do that for Ethernet, so why would PPP be special?

I second that. the whole point of ND not being ARP was to allow for the
same provisioning mechanisms to be used on multiple media. lets not go
down the IPCP rathole.

before we redesign the rest of IPv6. have we reached consensus on the
original question yet?  i.e is it required that an IPv6 node before
communicating with another node performs reachability detection using
NS/NA?

to me it is pretty clear that answer has to be no. in common deployments
a node doesn't know the next-hop address anyway.

if a clarification is needed to emphasise that the neighbour discovery
protocol must be supported on any multicast capable link, then I will
not object to that.

/ot

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



From ipv6-bounces@ietf.org Mon Jul 23 10: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 1ICyrD-0001U6-NQ; Mon, 23 Jul 2007 10:25:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICypR-0000Eb-U8
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:24:05 -0400
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICypR-0006QO-KM
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:24:05 -0400
Received: from ([128.244.97.7])
	by piper.jhuapl.edu with ESMTP  id 5502121.35960782;
	Mon, 23 Jul 2007 10:23:38 -0400
Message-ID: <46A4B9EA.7000600@innovationslab.net>
Date: Mon, 23 Jul 2007 10:23:38 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: IPv6 WG Mailing List <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: d17f825e43c9aed4fd65b7edddddec89
X-Mailman-Approved-At: Mon, 23 Jul 2007 10:25:54 -0400
Subject: State of ULA work
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,
     The recent discussion on the various forms of centrally maintained
ULA addresses clearly shows that there is no firm consensus on the
correct direction.  Given that, I have asked the authors of the
ULA-central draft to analyze the discussion to this point and post a
summary of the comments and the potential paths forward.  This
summarization work will begin after this week's meeting.


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 Mon Jul 23 10:30: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 1ICytt-0004LG-Q4; Mon, 23 Jul 2007 10:28:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICyts-0004Kt-3g
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:28:40 -0400
Received: from transfire.transwitch.com ([63.119.242.254]
	helo=smtphub.transwitch.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICytr-0007uN-Om
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:28:40 -0400
Received: from [172.17.2.251] (helo=[127.0.0.1])
	by smtphub.transwitch.com with esmtp (Exim 4.34) id 1ICytm-0000qV-Mm
	for ipv6@ietf.org; Mon, 23 Jul 2007 10:28:34 -0400
Message-ID: <46A4BB65.6010505@txc.com>
Date: Mon, 23 Jul 2007 10:29:57 -0400
From: srihari varada <varada@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-TXC-MailScanner-Information: Please contact the SysAdmin group for more
	information
X-TXC-MailScanner: Not scanned: please contact your Sysadmin group for details
X-MailScanner-From: varada@txc.com
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============0107623925=="
Errors-To: ipv6-bounces@ietf.org

--===============0107623925==
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">[here is the email that had posting problems]<br>
<br>
The subject took a detour from its original context
of the need for address resolution through the Neighbor Discovery
protocol. <br>
<br>
The author is appreciative of the belated feedback though the last call
for its parent draft (<i>draft-ietf-ipv6-over-ppp-v2.txt</i>)&nbsp; took
place a few years ago with the draft by itself was a result of the
collaborative effort of the IPv6 community (please check the archives
of IPv6 WG dating back to 2004). <br>
<br>
The encouraging aspect, however, is that framework of the <i>draft-ietf-ipv6-over-ppp-v3.txt
</i>specification allows for extensibility in the IPv6CP protocol
through the definition of new configuration options. Please find the
following statement to this effect in the said draft specification. <br>
</font>
<blockquote><font face="Arial">"The only IPV6CP option defined in this
document is the Interface Identifier.&nbsp; Any other IPV6CP configuration
options that can be defined over time are to be defined in separate
documents." <br>
  </font></blockquote>
<font face="Arial">If you strongly feel the need for option extensions,
it can be done so through new I-D(s). The value proposition of these
option extensions can then be discussed. As it is, the suggested
extensions are out of the scope of the specification.<br>
<br>
Regards,<br>
<br>
Srihari Varada</font>
</body>
</html>



--===============0107623925==
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
--------------------------------------------------------------------

--===============0107623925==--



From ipv6-bounces@ietf.org Mon Jul 23 11: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 1ICzaO-0003Y6-8C; Mon, 23 Jul 2007 11:12:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzaJ-0003Xb-0Z
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:12:32 -0400
Received: from transfire.transwitch.com ([63.119.242.254]
	helo=smtphub.transwitch.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzaI-0000MC-Ax
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:12:30 -0400
Received: from [172.17.2.251] (helo=[127.0.0.1])
	by smtphub.transwitch.com with esmtp (Exim 4.34) id 1ICzaD-0000ye-Vu
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:12:25 -0400
Message-ID: <46A4C5AF.2000000@txc.com>
Date: Mon, 23 Jul 2007 11:13:51 -0400
From: srihari varada <varada@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-TXC-MailScanner-Information: Please contact the SysAdmin group for more
	information
X-TXC-MailScanner: Not scanned: please contact your Sysadmin group for details
X-MailScanner-From: varada@txc.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

[Resending the message that couldn't get posted on July 18, 2007 ...]

All:

Followed the thread on the subject, and noted the interoperability 
problem between link partners, with no link-level addresses, on a 
point-to-point link (such as PPP).

It is gathered that the implementation interoperability arose due to 
varying interpretations of the RFC 2461 specification, specifically, how 
one should model point-to-point links from the perspective of the 
Neighbor Discovery protocol support (refer to the Section 3.2, 
"point-to-point links."). It seems to have been aggrevated as the 
connotation in the section 7.2.2, first sentence, the "address 
resolution" is relevant where neighbors have link-layer addresses, lead 
to the following question .... why one should perfrom address resolution 
on point-to-point links that do not have the notion of link-layer 
addresses (PPP, X.85 LAPS, GFP etc.)?

Based on my judgement, which is also reflected in the thread, the issue 
is not with the RFC 2472 and that Neighbor Discovery protocol support 
(specifically, the address resolution issue) needs to be tackled for all 
other point-to-point links with no notion of link-layer addresses. I 
will support any effort that clarifies it whether it is an I-D or 
draft-ietf-ipv6-rfc2461bis.

Regards,

Srihari Varada

James Carlson wrote:

>JINMEI Tatuya / ç¥žæ˜Žé�”å“‰ writes:
>  
>
>>At Tue, 17 Jul 2007 16:35:33 -0400,
>>James Carlson <james.d.carlson@sun.com> wrote:
>>    
>>
>>>If you're going to somehow omit ND for address resolution, but use it
>>>for everything else, what exactly does that look like on the wire, and
>>>what support in the existing RFC is there for this sort of operation?
>>>      
>>>
>>What the BSD (KAME) implementation does is as follows:
>>
>>- when it first sends a packet to the other end of a point-to-point
>>  (including PPP) link it creates a placeholder of a neighbor cache
>>  with the state of STALE
>>    
>>
>
>I understand the desire, but I don't think the current RFC supports
>that behavior.  Section 5.2 sets out the basic operation:
>
>   Once the IP address of the next-hop node is known, the sender
>   examines the Neighbor Cache for link-layer information about that
>   neighbor.  If no entry exists, the sender creates one, sets its state
>   to INCOMPLETE, initiates Address Resolution, and then queues the data
>   packet pending completion of address resolution.  For multicast-
>   capable interfaces Address Resolution consists of sending a Neighbor
>   Solicitation message and waiting for a Neighbor Advertisement.  When
>
>And, as documented in 2.2, point-to-point links (such as PPP) are
>assumed to be multicast-capable:
>
>   point-to-point - a link that connects exactly two interfaces.  A
>                    point-to-point link is assumed to have multicast
>                    capability and have a link-local address.
>
>The implication is that a trip through INCOMPLETE isn't optional.  I
>agree that it (at least in theory) could be, but I don't see how the
>existing text supports what you're describing.
>
>  
>
>>- the packet is sent to the p2p link immediately since there is no
>>  need to perform address resolution
>>- eventually the state of the neighbor cache entry is changed to PROBE
>>  and NUD is performed
>>
>>(this description is a bit simplified to concentrate on the main point
>>of this discussion)
>>    
>>
>
>Sure.
>
>  
>
>>I believe this is a reasonable behavior, although as far as I know the
>>protocol specification does not specify this level of details
>>(e.g. what should be the initial state of such a cache entry).
>>    
>>
>
>Actually, it does.  Section 7.2.2 specifies that new entries are
>created in INCOMPLETE state.
>
>It might be possible to carve out an exception for point-to-point, but
>I don't see one there now.  I *think* that you're hanging your
>argument on this phrase from section 7.2.2:
>
>   When a node has a unicast packet to send to a neighbor, but does not
>   know the neighbor's link-layer address, it performs address
>
>I believe that this needs to be cleared up.  If it really means that
>point-to-point links should not send NS and wait for NA, then it
>should say so and it should not go on to explain what
>"multicast-capable" interfaces (which include point-to-point) links
>should do.
>
>  
>
>>In any case, it's totally pointless for an implementation to hold the
>>packet during an exchange of NS/NA for address resolution (which
>>itself is meaningless) on such a link.  Furthermore, if the
>>    
>>
>
>I agree that it seems pointless, but it's what the current text says.
>
>  
>
>>originally tried to indicate.  I don't know of an implementation that
>>performs the meaningless NS/NA for address resolution on a p2p link,
>>but I know an implementation that doesn't respond to an NS (whether
>>it's for address resolution or for NUD) on a p2p link, so I won't be
>>surprised if the problem actually happens.
>>    
>>
>
>It doesn't respond to a valid NS?  How is that a viable
>implementation.
>
>In this part, I think you're just describing a bug.  I don't see
>anything in the RFC that supports simply ignoring an NS.  (And if you
>do that, then how can NUD possibly work?)
>
>  
>
>>As far as I can see the current specification is pretty clear to
>>prevent such a pointless behavior, but if there is an implementation
>>that behaves that way (Dave's message seems to indicate there is) it
>>may make sense to write a short I-D that clarifies this point.  In
>>this case I believe it should be a generic note on point-to-point link
>>that doesn't have the notion of L2 address (and thus doesn't require
>>L2 address resolution) rather than a part of a document for a specific
>>link type such as ipv6-over-ppp-v2.
>>    
>>
>
>The part I support is clarifying the document.  I don't think I
>support changing the functionality described in the document.
>
>  
>



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



From ipv6-bounces@ietf.org Mon Jul 23 11:15: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 1ICzcd-0004LQ-Q3; Mon, 23 Jul 2007 11:14:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzcc-0004L5-85
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:14:54 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzcV-0000PT-Ie
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:14:54 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6NFEke5021565 for <ipv6@ietf.org>; Mon, 23 Jul 2007 15:14:46 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6NFEkng004142
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 11:14:46 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6NEu1Kv027273; Mon, 23 Jul 2007 10:56:01 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6NEtt8g027265;
	Mon, 23 Jul 2007 10:55:55 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18084.49531.537696.779095@gargle.gargle.HOWL>
Date: Mon, 23 Jul 2007 10:55:55 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036A479B@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A479B@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> Let's clear the air. I agree with Srihari's email on IPV6CP and new
> options.

So do I.  Those issues are just out of scope.

> Now let's see what the PPP interop issues are:
> 
> The sender PPP node is ND compliant when it issues a unicast NS for NUD
> before sending any data. The PPP peer of this sending node has a bug as
> to why the peer is not responding with an NA? Let's focus on this
> interop issue rather than asking for 2461bis or PPP to be changed. 

Agreed.  And unless there's text that supports this non-answering
mode, that certainly sounds like a bug to me.

I'm not sure that every implementation bug necessarily deserves to be
enshrined as normative "don't make this mistake" text in an RFC.  If
others (particularly those who are refusing to send NAs when
solicited) feel otherwise, then it doesn't bother me to have
additional "must respond" text as long as it doesn't muddy the rest of
the document by making it appear as though normal responses are
otherwise optional in other cases.

> It's an orthogonal issue to ask if one should change 2461bis that
> requires an IPv6 node to perform reachability detection before
> communicating with another node. As for any changes needed by PPP and
> IPV6CP, do note, DHCPv6 cannot be used for other options and addresses
> in PPP if the client is SLAAC.

It seems to work fine for me.  Set the RA 'M' bit to zero, the 'O' bit
to one, and the prefix 'A' and 'L' bits to one.  That gets me
interface addresses via stateless address autoconfiguration along with
configuration parameters (but not addresses) via DHCPv6.

In fact, RFC 3315 states (among many notes on interoperation):

   stateful autoconfiguration.  Compatibility with stateless address
   autoconfiguration is a design requirement of DHCP.

It seems to have been designed to work that way.  Why would it be
assumed not to work?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 11:28: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 1ICzpB-0000ZF-M1; Mon, 23 Jul 2007 11:27:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICzpA-0000Z9-Rs
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:27:52 -0400
Received: from transfire.transwitch.com ([63.119.242.254]
	helo=smtphub.transwitch.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICzpA-0000vA-C8
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:27:52 -0400
Received: from [172.17.2.251] (helo=[127.0.0.1])
	by smtphub.transwitch.com with esmtp (Exim 4.34) id 1ICzp8-00011p-0i
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:27:50 -0400
Message-ID: <46A4C94B.9010905@txc.com>
Date: Mon, 23 Jul 2007 11:29:15 -0400
From: srihari varada <varada@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-TXC-MailScanner-Information: Please contact the SysAdmin group for more
	information
X-TXC-MailScanner: Not scanned: please contact your Sysadmin group for details
X-MailScanner-From: varada@txc.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

[text formatted reply (July 22, 2007) to van Beijnum is being reposted  
-- apologies for the mix-up]

The subject took a detour from its original context of the need for 
address resolution through the Neighbor Discovery protocol.

The author is appreciative of the belated feedback though the last call 
for its parent draft (/draft-ietf-ipv6-over-ppp-v2.txt/)  took place a 
few years ago with the draft by itself was a result of the collaborative 
effort of the IPv6 community (please check the archives of IPv6 WG 
dating back to 2004).

The encouraging aspect, however, is that framework of the 
/draft-ietf-ipv6-over-ppp-v3.txt /specification allows for extensibility 
in the IPv6CP protocol through the definition of new configuration 
options. Please find the following statement to this effect in the said 
draft specification.

    "The only IPV6CP option defined in this document is the Interface
    Identifier.  Any other IPV6CP configuration options that can be
    defined over time are to be defined in separate documents."

If you strongly feel the need for option extensions, it can be done so 
through new I-D(s). The value proposition of these option extensions can 
then be discussed. As it is, the suggested extensions are out of the 
scope of the specification.

Regards,

Srihari Varada


Iljitsch van Beijnum wrote:

> On 19-jul-2007, at 23:50, Hemant Singh (shemant) wrote:
>
>> Never mind, I found what's 2462bis. I got hold of
>
>
>> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-over-ppp-v2-03.txt
>
>
> I read this draft and I find it severely lacking. At the very least,  
> to make using IPv6 over PPP even remotely usable, it should include  
> the following options:
>
> 1. An MTU option. I know there is an MTU option for IPv4 over PPP but  
> I can't find the specification real quick, it doesn't seem to be PPP  
> spec but not in the IPCP spec either, or there must be a terminology  
> issue such that searching for "MTU" is unsuccessful. But the IPv6 MTU  
> shouldn't be tied to the IPv4 MTU anyway. All hardware imposes limits  
> on packet sizes, and without a method to explicitly negotiate these  
> limits implementations are forced to assume very conservative  
> defaults. Routers can advertise an MTU option in RAs but hosts can't,  
> a full negotiation is needed here.
>
> 2. DNS resolver addresses. Without the ability to resolve names IPv6  
> is unusable.
>
> I was thinking that it would be good if multiple full IPv6 addresses  
> could be negotiated over IP6CP but upon further reflection that would  
> quickly become prohibitively complex or slow: if addresses are  
> negotiated one at a time, it would be too slow, and negotiating a set  
> would be complex because individual addresses may be generated and  
> retired at any time. So using standard IPv6 mechanisms would be  
> better here.
>
> But addresses used on the PPP link itself aren't all that  
> interesting. A more pressing need is the one for a mechanism to  
> negotiate a prefix that a router that terminates the PPP link on the  
> client side can use on its LAN interface. I.e.:
>
>     1           2                   3         4
> host --<ether>-- customer PPP router --<PPP>-- ISP PPP router -- 
> <internet>--
>
> Currently, the interface identifiers in IP6CP and standard autoconfig  
> allow for the creation of addresses 3 and 4, but what we really need  
> is a prefix that holds addresses 1 and 2.
>
> I can't stress enough that IPv6 over PPP in its current form is as  
> good as unusable in practice, and this draft doesn't fix that.
>



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



From ipv6-bounces@ietf.org Mon Jul 23 11:40: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 1ID01g-0006Jv-8T; Mon, 23 Jul 2007 11:40:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID01d-0006Jp-QK
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:40:45 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID01d-0008Nd-Ah
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:40:45 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 23 Jul 2007 11:40:45 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CADZopEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,571,1175486400"; 
	d="scan'208"; a="65895161:sNHT46349482"
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 l6NFeiW2002744; 
	Mon, 23 Jul 2007 11:40:44 -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 l6NFeSWs003935; 
	Mon, 23 Jul 2007 15:40:42 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); 
	Mon, 23 Jul 2007 11:40: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="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 23 Jul 2007 11:40:39 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA21@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18084.49531.537696.779095@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfNOq5ANmxOY5FaRXuL/x8wFPJvzQABAyqg
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com><18079.53002.425765.815419@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com><18079.54644.379204.366856@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4
	79B@xmb-rtp-
	20e.amer.cisco.com> <18084.49531.537696.779095@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 23 Jul 2007 15:40:41.0200 (UTC)
	FILETIME=[D31EE700:01C7CD3F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2820; t=1185205244;
	x=1186069244; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22James=20Carlson=22=20<james.d.carlson@sun.com>;
	bh=8enLWYDwVlPwXXlv6xsAp+HsLQ2eIj6QM6+2oOhIS5A=;
	b=Q2HnU/l4YybxuTRb21sRWa+wOywySYBvhAxLz+u3itGxIH3UycjxNRxecxl/QXQ4UB7YGdcK
	/zwXbBu3Ev+erLPhOjE7B9rXf8qvW3unxOskUm5rEFsxTafwgMhqMzrH;
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: c0bedb65cce30976f0bf60a0a39edea4
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,=20

The topic under discussion is how does a SLAAC PPP client acquire an
IPv6 address using DHCPv6? Yes, stateless DHCPv6 can be used to dole out
options to the SLAAC client but you cannot have the SLAAC client obtain
an IPV6 address with stateless DHCPv6. Sorry, I wasn't clear like so in
my earlier email.

Hemant =20

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Monday, July 23, 2007 10:56 AM
To: Hemant Singh (shemant)
Cc: Ole Troan (otroan); varada@txc.com; JINMEI Tatuya / ????;
ipv6@ietf.org; Dave Thaler
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh (shemant) writes:
> Let's clear the air. I agree with Srihari's email on IPV6CP and new=20
> options.

So do I.  Those issues are just out of scope.

> Now let's see what the PPP interop issues are:
>=20
> The sender PPP node is ND compliant when it issues a unicast NS for=20
> NUD before sending any data. The PPP peer of this sending node has a=20
> bug as to why the peer is not responding with an NA? Let's focus on=20
> this interop issue rather than asking for 2461bis or PPP to be
changed.

Agreed.  And unless there's text that supports this non-answering mode,
that certainly sounds like a bug to me.

I'm not sure that every implementation bug necessarily deserves to be
enshrined as normative "don't make this mistake" text in an RFC.  If
others (particularly those who are refusing to send NAs when
solicited) feel otherwise, then it doesn't bother me to have additional
"must respond" text as long as it doesn't muddy the rest of the document
by making it appear as though normal responses are otherwise optional in
other cases.

> It's an orthogonal issue to ask if one should change 2461bis that=20
> requires an IPv6 node to perform reachability detection before=20
> communicating with another node. As for any changes needed by PPP and=20
> IPV6CP, do note, DHCPv6 cannot be used for other options and addresses

> in PPP if the client is SLAAC.

It seems to work fine for me.  Set the RA 'M' bit to zero, the 'O' bit
to one, and the prefix 'A' and 'L' bits to one.  That gets me interface
addresses via stateless address autoconfiguration along with
configuration parameters (but not addresses) via DHCPv6.

In fact, RFC 3315 states (among many notes on interoperation):

   stateful autoconfiguration.  Compatibility with stateless address
   autoconfiguration is a design requirement of DHCP.

It seems to have been designed to work that way.  Why would it be
assumed not to work?

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 11:55: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 1ID0Fn-0005AA-83; Mon, 23 Jul 2007 11:55:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID0Fm-0005A0-IH
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:55:22 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID0Fl-0001j0-LT
	for ipv6@ietf.org; Mon, 23 Jul 2007 11:55:22 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jul 2007 11:55:22 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAMVrpEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,571,1175486400"; 
	d="scan'208"; a="126774112:sNHT78484526"
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 l6NFtLE1028990; 
	Mon, 23 Jul 2007 11:55:21 -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 l6NFt2Ws009825; 
	Mon, 23 Jul 2007 15:55:21 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); 
	Mon, 23 Jul 2007 11:55:19 -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: Mon, 23 Jul 2007 11:55:18 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA43@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <46A4C5AF.2000000@txc.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfNPAPECNnzY0VzReauWVWvjh5KbwABJ1sQ
References: <46A4C5AF.2000000@txc.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "srihari varada" <varada@txc.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 23 Jul 2007 15:55:19.0459 (UTC)
	FILETIME=[DE9A9730:01C7CD41]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7219; t=1185206121;
	x=1186070121; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20 |To:=20=22srihari=20varada=22=20<varada@txc.com>,
	=0A=20=20=20=20=20=20=20
	=20=22IETF=20IPv6=20Mailing=20List=22=20<ipv6@ietf.org>;
	bh=Wux/KntNrUjpIMkpkCyCzC8KWnB+Yc971hgQ0dLMdoM=;
	b=Y4JlLuh5BpmZfXyD3Gdh93sfT9fDQsIoEj170gNEtrjFkFaqm4uF/zDtYT1fFrBi/3Gk8O4F
	UPl+xfxvb5XN+Gm2kd0hgoOYo0/cUKPSfMNvRbHDp+gSbMBvOQOVLeg3;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: 
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Srihari,

I think we are de-focusing the discussion again and going into the same circle from last week all over again. I said the bug is in the peer as to why peer did not respond with an NA to the NUD NS from PPP client? James agreed with me. I also said, having any node, not just a PPP client, skip NUD before communicating with another node, is an orthogonal discussion for 2461bis folks - just because a PPP peer didn't respond to a NUD NS, we can't jump to having a PPP client skip NUD. So far the PPP discussion is related to strictly reachability detection. Your email below relates to address resolution. That is yet another orthogonal topic because as per RFC 2461bis a PPP client has to behave just like any other IPv6 client.

Regards.

Hemant

-----Original Message-----
From: srihari varada [mailto:varada@txc.com] 
Sent: Monday, July 23, 2007 11:14 AM
To: IETF IPv6 Mailing List
Subject: Re: Neighbor Discovery and PPP links

[Resending the message that couldn't get posted on July 18, 2007 ...]

All:

Followed the thread on the subject, and noted the interoperability problem between link partners, with no link-level addresses, on a point-to-point link (such as PPP).

It is gathered that the implementation interoperability arose due to varying interpretations of the RFC 2461 specification, specifically, how one should model point-to-point links from the perspective of the Neighbor Discovery protocol support (refer to the Section 3.2, "point-to-point links."). It seems to have been aggrevated as the connotation in the section 7.2.2, first sentence, the "address resolution" is relevant where neighbors have link-layer addresses, lead to the following question .... why one should perfrom address resolution on point-to-point links that do not have the notion of link-layer addresses (PPP, X.85 LAPS, GFP etc.)?

Based on my judgement, which is also reflected in the thread, the issue is not with the RFC 2472 and that Neighbor Discovery protocol support (specifically, the address resolution issue) needs to be tackled for all other point-to-point links with no notion of link-layer addresses. I will support any effort that clarifies it whether it is an I-D or draft-ietf-ipv6-rfc2461bis.

Regards,

Srihari Varada

James Carlson wrote:

>JINMEI Tatuya / $B?@L@C#:H(J writes:
>  
>
>>At Tue, 17 Jul 2007 16:35:33 -0400,
>>James Carlson <james.d.carlson@sun.com> wrote:
>>    
>>
>>>If you're going to somehow omit ND for address resolution, but use it 
>>>for everything else, what exactly does that look like on the wire, 
>>>and what support in the existing RFC is there for this sort of operation?
>>>      
>>>
>>What the BSD (KAME) implementation does is as follows:
>>
>>- when it first sends a packet to the other end of a point-to-point
>>  (including PPP) link it creates a placeholder of a neighbor cache
>>  with the state of STALE
>>    
>>
>
>I understand the desire, but I don't think the current RFC supports 
>that behavior.  Section 5.2 sets out the basic operation:
>
>   Once the IP address of the next-hop node is known, the sender
>   examines the Neighbor Cache for link-layer information about that
>   neighbor.  If no entry exists, the sender creates one, sets its state
>   to INCOMPLETE, initiates Address Resolution, and then queues the data
>   packet pending completion of address resolution.  For multicast-
>   capable interfaces Address Resolution consists of sending a Neighbor
>   Solicitation message and waiting for a Neighbor Advertisement.  When
>
>And, as documented in 2.2, point-to-point links (such as PPP) are 
>assumed to be multicast-capable:
>
>   point-to-point - a link that connects exactly two interfaces.  A
>                    point-to-point link is assumed to have multicast
>                    capability and have a link-local address.
>
>The implication is that a trip through INCOMPLETE isn't optional.  I 
>agree that it (at least in theory) could be, but I don't see how the 
>existing text supports what you're describing.
>
>  
>
>>- the packet is sent to the p2p link immediately since there is no
>>  need to perform address resolution
>>- eventually the state of the neighbor cache entry is changed to PROBE
>>  and NUD is performed
>>
>>(this description is a bit simplified to concentrate on the main point 
>>of this discussion)
>>    
>>
>
>Sure.
>
>  
>
>>I believe this is a reasonable behavior, although as far as I know the 
>>protocol specification does not specify this level of details (e.g. 
>>what should be the initial state of such a cache entry).
>>    
>>
>
>Actually, it does.  Section 7.2.2 specifies that new entries are 
>created in INCOMPLETE state.
>
>It might be possible to carve out an exception for point-to-point, but 
>I don't see one there now.  I *think* that you're hanging your argument 
>on this phrase from section 7.2.2:
>
>   When a node has a unicast packet to send to a neighbor, but does not
>   know the neighbor's link-layer address, it performs address
>
>I believe that this needs to be cleared up.  If it really means that 
>point-to-point links should not send NS and wait for NA, then it should 
>say so and it should not go on to explain what "multicast-capable" 
>interfaces (which include point-to-point) links should do.
>
>  
>
>>In any case, it's totally pointless for an implementation to hold the 
>>packet during an exchange of NS/NA for address resolution (which 
>>itself is meaningless) on such a link.  Furthermore, if the
>>    
>>
>
>I agree that it seems pointless, but it's what the current text says.
>
>  
>
>>originally tried to indicate.  I don't know of an implementation that 
>>performs the meaningless NS/NA for address resolution on a p2p link, 
>>but I know an implementation that doesn't respond to an NS (whether 
>>it's for address resolution or for NUD) on a p2p link, so I won't be 
>>surprised if the problem actually happens.
>>    
>>
>
>It doesn't respond to a valid NS?  How is that a viable implementation.
>
>In this part, I think you're just describing a bug.  I don't see 
>anything in the RFC that supports simply ignoring an NS.  (And if you 
>do that, then how can NUD possibly work?)
>
>  
>
>>As far as I can see the current specification is pretty clear to 
>>prevent such a pointless behavior, but if there is an implementation 
>>that behaves that way (Dave's message seems to indicate there is) it 
>>may make sense to write a short I-D that clarifies this point.  In 
>>this case I believe it should be a generic note on point-to-point link 
>>that doesn't have the notion of L2 address (and thus doesn't require
>>L2 address resolution) rather than a part of a document for a specific 
>>link type such as ipv6-over-ppp-v2.
>>    
>>
>
>The part I support is clarifying the document.  I don't think I support 
>changing the functionality described in the document.
>
>  
>



--------------------------------------------------------------------
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 Jul 23 12:05: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 1ID0PA-0005w5-N7; Mon, 23 Jul 2007 12:05:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID0P8-0005q6-Ky
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:05:02 -0400
Received: from ftwmail4.verizon.com ([192.76.86.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID0P7-00029h-Ds
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:05:02 -0400
Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92])
	by ftwmail4.verizon.com (8.13.6/8.13.3) with ESMTP id l6NG51Bk027464
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 12:05:01 -0400 (EDT)
Received: from ftwintrmemf2.verizon.com (ftwintrmemf2.verizon.com
	[138.83.131.184])
	by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id l6NG50oT019968
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 12:05:00 -0400 (EDT)
Received: from ftwintrmemf2.verizon.com (unknown [127.0.0.1])
	by ftwintrmemf2.verizon.com (Symantec Mail Security) with ESMTP id
	6D9DB528006
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 12:05:00 -0400 (EDT)
X-AuditID: 8a5383b8-b07dfbb000000820-07-46a4d1ac201c 
Received: from coregate2.verizon.com (unknown [138.83.34.48])
	by ftwintrmemf2.verizon.com (EMF) with ESMTP id 3B88E4E4002
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 12:05:00 -0400 (EDT)
Received: from dwsmtp01.core.verizon.com (dwsmtp01.verizon.com [138.83.35.62])
	by coregate2.verizon.com (8.13.3/8.13.3) with ESMTP id l6NG4xar005138
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 11:05:02 -0500 (CDT)
From: umang.a.patel@verizon.com
To: ipv6@ietf.org
Message-ID: <OF1AE11CC8.FC97E877-ON85257321.0058584F-85257321.0058584F@CORE.VERIZON.COM>
Date: Mon, 23 Jul 2007 12:04:57 -0400
X-MIMETrack: Serialize by Router on DWSMTP01/HSVR/Verizon(Release
	7.0.2FP1HF314 | May 24, 2007) at 07/23/2007 11:04:58
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Umang A. Patel is out of the office.
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============1375669219=="
Errors-To: ipv6-bounces@ietf.org

--===============1375669219==
Content-type: multipart/alternative; 
	Boundary="0__=0ABBF9B2DFCBDEDF8f9e8a93df938690918c0ABBF9B2DFCBDEDF"
Content-Disposition: inline

--0__=0ABBF9B2DFCBDEDF8f9e8a93df938690918c0ABBF9B2DFCBDEDF
Content-type: text/plain; charset=US-ASCII


I will be out of the office starting  07/23/2007 and will not return until
07/27/2007.

I will respond to your message when I return.
--0__=0ABBF9B2DFCBDEDF8f9e8a93df938690918c0ABBF9B2DFCBDEDF
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline

<html><body>
<p>I will be out of the office starting  07/23/2007 and will not return until 07/27/2007.<br>
<br>
I will respond to your message when I return.</body></html>
--0__=0ABBF9B2DFCBDEDF8f9e8a93df938690918c0ABBF9B2DFCBDEDF--



--===============1375669219==
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
--------------------------------------------------------------------

--===============1375669219==--





From ipv6-bounces@ietf.org Mon Jul 23 12:14: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 1ID0YL-0003aZ-7B; Mon, 23 Jul 2007 12:14:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID0YH-0003Zl-KK
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:14:29 -0400
Received: from transfire.transwitch.com ([63.119.242.254]
	helo=smtphub.transwitch.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID0YG-00019L-Nr
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:14:29 -0400
Received: from [172.17.2.251] (helo=[127.0.0.1])
	by smtphub.transwitch.com with esmtp (Exim 4.34)
	id 1ID0YE-00019N-Q5; Mon, 23 Jul 2007 12:14:26 -0400
Message-ID: <46A4D437.3000601@txc.com>
Date: Mon, 23 Jul 2007 12:15:52 -0400
From: srihari varada <varada@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <46A4C5AF.2000000@txc.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEA43@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA43@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-TXC-MailScanner-Information: Please contact the SysAdmin group for more
	information
X-TXC-MailScanner: Not scanned: please contact your Sysadmin group for details
X-MailScanner-From: varada@txc.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: srihari varada <varada@transwitch.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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:

Sorry that the re-posting got interjected with the thread of thought
that you want to carry forward. The intention wasn't to derail it.
Rather, it is a result of my own posting frustrations. Please continue
the discussion on reachability detection....

Regards,

Srihari Varada

Hemant Singh (shemant) wrote:

>Srihari,
>
>I think we are de-focusing the discussion again and going into the same circle from last week all over again. I said the bug is in the peer as to why peer did not respond with an NA to the NUD NS from PPP client? James agreed with me. I also said, having any node, not just a PPP client, skip NUD before communicating with another node, is an orthogonal discussion for 2461bis folks - just because a PPP peer didn't respond to a NUD NS, we can't jump to having a PPP client skip NUD. So far the PPP discussion is related to strictly reachability detection. Your email below relates to address resolution. That is yet another orthogonal topic because as per RFC 2461bis a PPP client has to behave just like any other IPv6 client.
>
>Regards.
>
>Hemant
>
>-----Original Message-----
>From: srihari varada [mailto:varada@txc.com] 
>Sent: Monday, July 23, 2007 11:14 AM
>To: IETF IPv6 Mailing List
>Subject: Re: Neighbor Discovery and PPP links
>
>[Resending the message that couldn't get posted on July 18, 2007 ...]
>
>All:
>
>Followed the thread on the subject, and noted the interoperability problem between link partners, with no link-level addresses, on a point-to-point link (such as PPP).
>
>It is gathered that the implementation interoperability arose due to varying interpretations of the RFC 2461 specification, specifically, how one should model point-to-point links from the perspective of the Neighbor Discovery protocol support (refer to the Section 3.2, "point-to-point links."). It seems to have been aggrevated as the connotation in the section 7.2.2, first sentence, the "address resolution" is relevant where neighbors have link-layer addresses, lead to the following question .... why one should perfrom address resolution on point-to-point links that do not have the notion of link-layer addresses (PPP, X.85 LAPS, GFP etc.)?
>
>Based on my judgement, which is also reflected in the thread, the issue is not with the RFC 2472 and that Neighbor Discovery protocol support (specifically, the address resolution issue) needs to be tackled for all other point-to-point links with no notion of link-layer addresses. I will support any effort that clarifies it whether it is an I-D or draft-ietf-ipv6-rfc2461bis.
>
>Regards,
>
>Srihari Varada
>
>James Carlson wrote:
>
>  
>
>>JINMEI Tatuya / $B?@L@C#:H(B writes:
>> 
>>
>>    
>>
>>>At Tue, 17 Jul 2007 16:35:33 -0400,
>>>James Carlson <james.d.carlson@sun.com> wrote:
>>>   
>>>
>>>      
>>>
>>>>If you're going to somehow omit ND for address resolution, but use it 
>>>>for everything else, what exactly does that look like on the wire, 
>>>>and what support in the existing RFC is there for this sort of operation?
>>>>     
>>>>
>>>>        
>>>>
>>>What the BSD (KAME) implementation does is as follows:
>>>
>>>- when it first sends a packet to the other end of a point-to-point
>>> (including PPP) link it creates a placeholder of a neighbor cache
>>> with the state of STALE
>>>   
>>>
>>>      
>>>
>>I understand the desire, but I don't think the current RFC supports 
>>that behavior.  Section 5.2 sets out the basic operation:
>>
>>  Once the IP address of the next-hop node is known, the sender
>>  examines the Neighbor Cache for link-layer information about that
>>  neighbor.  If no entry exists, the sender creates one, sets its state
>>  to INCOMPLETE, initiates Address Resolution, and then queues the data
>>  packet pending completion of address resolution.  For multicast-
>>  capable interfaces Address Resolution consists of sending a Neighbor
>>  Solicitation message and waiting for a Neighbor Advertisement.  When
>>
>>And, as documented in 2.2, point-to-point links (such as PPP) are 
>>assumed to be multicast-capable:
>>
>>  point-to-point - a link that connects exactly two interfaces.  A
>>                   point-to-point link is assumed to have multicast
>>                   capability and have a link-local address.
>>
>>The implication is that a trip through INCOMPLETE isn't optional.  I 
>>agree that it (at least in theory) could be, but I don't see how the 
>>existing text supports what you're describing.
>>
>> 
>>
>>    
>>
>>>- the packet is sent to the p2p link immediately since there is no
>>> need to perform address resolution
>>>- eventually the state of the neighbor cache entry is changed to PROBE
>>> and NUD is performed
>>>
>>>(this description is a bit simplified to concentrate on the main point 
>>>of this discussion)
>>>   
>>>
>>>      
>>>
>>Sure.
>>
>> 
>>
>>    
>>
>>>I believe this is a reasonable behavior, although as far as I know the 
>>>protocol specification does not specify this level of details (e.g. 
>>>what should be the initial state of such a cache entry).
>>>   
>>>
>>>      
>>>
>>Actually, it does.  Section 7.2.2 specifies that new entries are 
>>created in INCOMPLETE state.
>>
>>It might be possible to carve out an exception for point-to-point, but 
>>I don't see one there now.  I *think* that you're hanging your argument 
>>on this phrase from section 7.2.2:
>>
>>  When a node has a unicast packet to send to a neighbor, but does not
>>  know the neighbor's link-layer address, it performs address
>>
>>I believe that this needs to be cleared up.  If it really means that 
>>point-to-point links should not send NS and wait for NA, then it should 
>>say so and it should not go on to explain what "multicast-capable" 
>>interfaces (which include point-to-point) links should do.
>>
>> 
>>
>>    
>>
>>>In any case, it's totally pointless for an implementation to hold the 
>>>packet during an exchange of NS/NA for address resolution (which 
>>>itself is meaningless) on such a link.  Furthermore, if the
>>>   
>>>
>>>      
>>>
>>I agree that it seems pointless, but it's what the current text says.
>>
>> 
>>
>>    
>>
>>>originally tried to indicate.  I don't know of an implementation that 
>>>performs the meaningless NS/NA for address resolution on a p2p link, 
>>>but I know an implementation that doesn't respond to an NS (whether 
>>>it's for address resolution or for NUD) on a p2p link, so I won't be 
>>>surprised if the problem actually happens.
>>>   
>>>
>>>      
>>>
>>It doesn't respond to a valid NS?  How is that a viable implementation.
>>
>>In this part, I think you're just describing a bug.  I don't see 
>>anything in the RFC that supports simply ignoring an NS.  (And if you 
>>do that, then how can NUD possibly work?)
>>
>> 
>>
>>    
>>
>>>As far as I can see the current specification is pretty clear to 
>>>prevent such a pointless behavior, but if there is an implementation 
>>>that behaves that way (Dave's message seems to indicate there is) it 
>>>may make sense to write a short I-D that clarifies this point.  In 
>>>this case I believe it should be a generic note on point-to-point link 
>>>that doesn't have the notion of L2 address (and thus doesn't require
>>>L2 address resolution) rather than a part of a document for a specific 
>>>link type such as ipv6-over-ppp-v2.
>>>   
>>>
>>>      
>>>
>>The part I support is clarifying the document.  I don't think I support 
>>changing the functionality described in the document.
>>
>> 
>>
>>    
>>
>
>
>
>--------------------------------------------------------------------
>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 Jul 23 12:36: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 1ID0sv-0000Gp-9L; Mon, 23 Jul 2007 12:35:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID0su-0000E6-BF
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:35:48 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID0st-0001il-Sg
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:35:48 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jul 2007 12:35:48 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAAp2pEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,571,1175486400"; 
	d="scan'208"; a="126778893:sNHT44317036"
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 l6NGZlUG017866; 
	Mon, 23 Jul 2007 12:35:47 -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 l6NGZlEf004150; 
	Mon, 23 Jul 2007 16:35:47 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); 
	Mon, 23 Jul 2007 12:35: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, 23 Jul 2007 12:35:34 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA90@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18084.54442.780321.669886@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfNRhoHAfvP5C9dSYq+qqEeW/gCZAAAGvJA
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com><18079.53002.425765.815419@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com><18079.54644.379204.366856@gargle.gargle.HOWL><18084.49531.5376966.779095@gargle.gar
	gle.HOWL><B0
	0EDD615E3C5344B0FFCBA910CF7E1D036FEA21@xmb-rtp-20e.amer.cisco.com>
	<18084.54442.780321.669886@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 23 Jul 2007 16:35:36.0484 (UTC)
	FILETIME=[7F435640:01C7CD47]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2480; t=1185208547;
	x=1186072547; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22James=20Carlson=22=20<james.d.carlson@sun.com>;
	bh=EzaV6lPMArOrXLe34dNS7rFN47NqOs6nSWrr1d4jfrU=;
	b=hw9EMKnM4wEWf0MtYkFltsWSc0LiXjV67+clIXSDvRVzFowQPrSkro8vC6btZ71Do9lNogZI
	tRMRsjSFvLbg/+2XU97/T7qC5H97W4UrB7xOmj2QRw/uaANEhFwpg/kK;
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: 82c9bddb247d9ba4471160a9a865a5f3
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

I am saying when the M bit is clear, then a node cannot acquire an
address using DHCPv6. However, I agree with you DHCPv6 is much better
alternative than PPP.=20

Now, I'd like to focus the discussion back to how will the PPP peer
(which is a server) going to fix the bug when this peer hasn't responded
to the NUD unicast NS? I have already said the source PPP client that
issued the unicast NS is 2461bis complaint.=20

Hemant

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Monday, July 23, 2007 12:18 PM
To: Hemant Singh (shemant)
Cc: Ole Troan (otroan); varada@txc.com; JINMEI Tatuya / ????;
ipv6@ietf.org; Dave Thaler
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh (shemant) writes:
> The topic under discussion is how does a SLAAC PPP client acquire an
> IPv6 address using DHCPv6?

Using stateful DHCPv6 (with the RA 'M' bit set to one), of course.

> Yes, stateless DHCPv6 can be used to dole out options to the SLAAC=20
> client but you cannot have the SLAAC client obtain an IPV6 address=20
> with stateless DHCPv6.

If you're trying to assign addresses via stateful means (DHCPv6 is the
defined stateful addressing mechanism for IPv6), it's unclear to me why
you'd ever want stateless DHCPv6 as a solution.  It seems like a
contradiction in terms.

It is, though, possible to use stateless and stateful address assignment
in parallel if one wishes, and (to the previous posters
comments) DHCPv6 also works fine in a stateless context to provide the
"other" configuration parameters, even when all addresses in use are
either stateless or are manually configured.

It's a simple request-response mechanism, and no more troublesome to
implement than adding yet another PPP option -- though the architectural
issues are substantially different.  The architecture differs because
PPP messages themselves cannot be 'routed' or proxied, but DHCP messages
can, meaning that DHCP also serves nodes located _behind_ the PPP
termination point, but additional PPP options cannot.
That alone makes a PPP-based solution to the (off-topic) issues raised
by the other poster much less attractive, regardless of its supposed
"simplicity."

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 12:36: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 1ID0ts-00011f-TK; Mon, 23 Jul 2007 12:36:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID0tr-00011X-Cn
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:36:47 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID0tq-0002we-Uj
	for ipv6@ietf.org; Mon, 23 Jul 2007 12:36:47 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6NGakqe029159 for <ipv6@ietf.org>; Mon, 23 Jul 2007 16:36:46 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6NGajAe000256
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 12:36:45 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6NGHsEG027997; Mon, 23 Jul 2007 12:17:54 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6NGHlbr027994;
	Mon, 23 Jul 2007 12:17:47 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18084.54442.780321.669886@gargle.gargle.HOWL>
Date: Mon, 23 Jul 2007 12:17:46 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA21@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
	<18084.49531.5376966.779095@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEA21@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> The topic under discussion is how does a SLAAC PPP client acquire an
> IPv6 address using DHCPv6?

Using stateful DHCPv6 (with the RA 'M' bit set to one), of course.

> Yes, stateless DHCPv6 can be used to dole out
> options to the SLAAC client but you cannot have the SLAAC client obtain
> an IPV6 address with stateless DHCPv6.

If you're trying to assign addresses via stateful means (DHCPv6 is the
defined stateful addressing mechanism for IPv6), it's unclear to me
why you'd ever want stateless DHCPv6 as a solution.  It seems like a
contradiction in terms.

It is, though, possible to use stateless and stateful address
assignment in parallel if one wishes, and (to the previous posters
comments) DHCPv6 also works fine in a stateless context to provide the
"other" configuration parameters, even when all addresses in use are
either stateless or are manually configured.

It's a simple request-response mechanism, and no more troublesome to
implement than adding yet another PPP option -- though the
architectural issues are substantially different.  The architecture
differs because PPP messages themselves cannot be 'routed' or proxied,
but DHCP messages can, meaning that DHCP also serves nodes located
_behind_ the PPP termination point, but additional PPP options cannot.
That alone makes a PPP-based solution to the (off-topic) issues raised
by the other poster much less attractive, regardless of its supposed
"simplicity."

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 13: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 1ID1Gt-00053a-Gw; Mon, 23 Jul 2007 13:00:35 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Gr-00052M-Kp
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:00:33 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ID1Gr-0002Vh-0N
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:00:33 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6NH0VwB012989 for <ipv6@ietf.org>; Mon, 23 Jul 2007 17:00:32 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,
	v2.2) with ESMTP id l6NH0VCF004357
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 13:00:31 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6NGfllK028122; Mon, 23 Jul 2007 12:41:47 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6NGfl6V028119;
	Mon, 23 Jul 2007 12:41:47 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18084.55883.599274.586170@gargle.gargle.HOWL>
Date: Mon, 23 Jul 2007 12:41:47 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEA90@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL> <"B0
	0EDD615E3C53444B0FFCBA910CF7E1D036FEA21"@xmb-rtp-20e.amer.cisco.com>
	<18084.54442.780321.669886@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEA90@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> I am saying when the M bit is clear, then a node cannot acquire an
> address using DHCPv6. However, I agree with you DHCPv6 is much better
> alternative than PPP. 
> 
> Now, I'd like to focus the discussion back to how will the PPP peer
> (which is a server)

Nit: PPP doesn't define "client" or "server."  It's peer-to-peer.

> going to fix the bug when this peer hasn't responded
> to the NUD unicast NS? I have already said the source PPP client that
> issued the unicast NS is 2461bis complaint. 

I don't think it should "fix" the problem.  If the peer fails to
respond as expected, it has to declare the remote address to be
unreachable.

I'm not sure why we'd necessarily expect the side that's working right
to work around bugs in the other side.  (In fact, it could be argued
that this is a good state of affairs: malfunctioning gear may in fact
have other bugs, and it's better to detect this early rather than
later.)

Yes, it'd be possible to carve out a hole in NUD and say that if
there's _never_ a response from the peer to any NS for the life of the
link, and if the link is specifically point-to-point and without link
layer addresses, and if the link-layer is known to perform keepalive-
like operation, then the NS sender could "assume" that the address is
actually reachable.

That seems like needless complexity to me, though.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 13:08: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 1ID1Or-0001Uy-17; Mon, 23 Jul 2007 13:08:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1Oq-0001Us-B1
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:08:48 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID1Op-0003xb-QA
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:08:48 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 23 Jul 2007 13:08:47 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAE99pEZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,571,1175486400"; 
	d="scan'208"; a="65904842:sNHT45187220"
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 l6NH8lgB032344; 
	Mon, 23 Jul 2007 13:08:47 -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 l6NH8gWS007689; 
	Mon, 23 Jul 2007 17:08:46 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, 23 Jul 2007 13:08: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: Mon, 23 Jul 2007 13:08:33 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEAD3@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18084.55883.599274.586170@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Neighbor Discovery and PPP links
Thread-Index: AcfNSW4bRJlRFds4SamnMp5T3VmnrQAAgeSw
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><7t57ioygbu2.fsf@gpk-xdm-001.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><18077.5262.92643.663259@gargle.gargle.HOWL><7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com><18077.10261.578486.718408@gargle.gargle.HOWL><m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com><271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com><B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com><18079.53002.425765.815419@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com><18079.54644.379204.366856@gargle.gargle.HOWL><"B0
	0EDD615E3C53444B0FFCBA910CF7E1D03 6FEA21"@xmb-
	rtp-20e.amer.cisco.com><18084.54442.780321.669886@gargle.gargle.HOWL><B00EDD615E3C5344B0FFCBA910CF7E1D036FEA90@xmb-rtp-20e.amer.cisco.com>
	<18084.55883.599274.586170@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 23 Jul 2007 17:08:37.0748 (UTC)
	FILETIME=[1C303B40:01C7CD4C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2862; t=1185210527;
	x=1186074527; 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=20Neighbor=20Discovery=20and=20PPP=20links
	|Sender:=20
	|To:=20=22James=20Carlson=22=20<james.d.carlson@sun.com>;
	bh=GzMMu+asGWW0DLsx0sPmCuaesZix5VP1TC3iiijl+ZE=;
	b=Qvhm7ZZxOH73p+q86K0d4rhPurC7fYdrPDuCqfqA+rf5kBykE430IF+qIAWfJhFlPsRYrg11
	04OQhAiKjC7VX2EpZGd2zl7d58RaaDqGJRsvoqmqt4I6CFo0nj4q6JFS;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

Please see in line below with "<hs>".

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Monday, July 23, 2007 12:42 PM
To: Hemant Singh (shemant)
Cc: Ole Troan (otroan); varada@txc.com; JINMEI Tatuya / ????;
ipv6@ietf.org; Dave Thaler
Subject: RE: Neighbor Discovery and PPP links

Hemant Singh (shemant) writes:
> I am saying when the M bit is clear, then a node cannot acquire an=20
> address using DHCPv6. However, I agree with you DHCPv6 is much better=20
> alternative than PPP.
>=20
> Now, I'd like to focus the discussion back to how will the PPP peer=20
> (which is a server)

Nit: PPP doesn't define "client" or "server."  It's peer-to-peer.

<hs> I know PPP is a p2p model. I was using the term server to refer to
the server bug in the PPP Interop problem that Dave explained. This is
what Dave said:

[Actually after some more investigation, I think I understand the source
of the interoperability issue.  The core issue is that some PPP servers
actually handle multiple PPP connections to different clients via a
common interface.  Hence from the server's perspective, it's not a
point-to-point link, but rather an NBMA link.  From the client's
perspective, the client thinks it's a point-to-point link, and there's
no way to discover that the server thinks otherwise.]

> going to fix the bug when this peer hasn't responded to the NUD=20
> unicast NS? I have already said the source PPP client that issued the=20
> unicast NS is 2461bis complaint.

I don't think it should "fix" the problem.  If the peer fails to respond
as expected, it has to declare the remote address to be unreachable.

<hs> But the peer is reachable in this p2p model !

I'm not sure why we'd necessarily expect the side that's working right
to work around bugs in the other side.  (In fact, it could be argued
that this is a good state of affairs: malfunctioning gear may in fact
have other bugs, and it's better to detect this early rather than
later.)

Yes, it'd be possible to carve out a hole in NUD and say that if there's
_never_ a response from the peer to any NS for the life of the link, and
if the link is specifically point-to-point and without link layer
addresses, and if the link-layer is known to perform keepalive- like
operation, then the NS sender could "assume" that the address is
actually reachable.

<hs> Let's not start preparing text for changes to 2461bis for PPP
unless we can first discuss what to do about the server bug that Dave
pointed out.

Hemant

That seems like needless complexity to me, though.

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 13:35: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 1ID1oh-0005VU-Eq; Mon, 23 Jul 2007 13:35:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID1og-0005VO-9O
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:35:30 -0400
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID1of-00050x-Mw
	for ipv6@ietf.org; Mon, 23 Jul 2007 13:35:30 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l6NHZS07019786 for <ipv6@ietf.org>; Mon, 23 Jul 2007 17:35:28 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,
	v2.2) with ESMTP id l6NHZSue000344
	for <ipv6@ietf.org>; Mon, 23 Jul 2007 13:35:28 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l6NHKTE0028267; Mon, 23 Jul 2007 13:20:29 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l6NHKQDF028264;
	Mon, 23 Jul 2007 13:20:26 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18084.58202.421668.905852@gargle.gargle.HOWL>
Date: Mon, 23 Jul 2007 13:20:26 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEAD3@xmb-rtp-20e.amer.cisco.com>
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<7t57ioygbu2.fsf@gpk-xdm-001.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC05F80FFD@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18077.5262.92643.663259@gargle.gargle.HOWL>
	<7t5tzs2eq7p.fsf@gpk-xdm-001.cisco.com>
	<18077.10261.578486.718408@gargle.gargle.HOWL>
	<m1ejj62tv9.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3A56@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A00D@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A3F25@xmb-rtp-20e.amer.cisco.com>
	<271CF87FD652F34DBF877CB0CB5D16FC0602A438@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4132@xmb-rtp-20e.amer.cisco.com>
	<18079.53002.425765.815419@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036A4153@xmb-rtp-20e.amer.cisco.com>
	<18079.54644.379204.366856@gargle.gargle.HOWL>
	<18084.54442.7803211.669886@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEA90@xmb-rtp-20e.amer.cisco.com>
	<18084.55883.599274.586170@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEAD3@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: varada@txc.com, Dave Thaler <dthaler@windows.microsoft.com>, ipv6@ietf.org,
	"Ole Troan \(otroan\)" <otroan@cisco.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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) writes:
> Hemant Singh (shemant) writes:
> > Now, I'd like to focus the discussion back to how will the PPP peer 
> > (which is a server)
> 
> Nit: PPP doesn't define "client" or "server."  It's peer-to-peer.
> 
> <hs> I know PPP is a p2p model. I was using the term server to refer to
> the server bug in the PPP Interop problem that Dave explained. This is
> what Dave said:

Yes; I saw that.  Part of the disconnect here is in the use of NBMA as
a representation of a collection of PPP links.  That seems like one of
the real hazards.

> common interface.  Hence from the server's perspective, it's not a
> point-to-point link, but rather an NBMA link.  From the client's
> perspective, the client thinks it's a point-to-point link, and there's
> no way to discover that the server thinks otherwise.]

I think that's yet more reason to treat all links as equal and use the
same procedures everywhere.

However, even if we got this issue cleared up, I think there's still a
problem with the NBMA representation.  From the server's point of
view, the clients all must have some sort of link-layer address so
that they can be distinguished.  From the client's point of view, no
such address is known or knowable.

This implies that the client cannot create reasonable response because
it cannot fill in the SLLA option correctly.  Either the server's
NBMA-synthesizing code needs to fix this up, or it's going to take yet
more hacks to the neighbor discovery state machine to make it run
right.  (Essentially assuming that these NBMA peers have already-known
addresses.)

> > going to fix the bug when this peer hasn't responded to the NUD 
> > unicast NS? I have already said the source PPP client that issued the 
> > unicast NS is 2461bis complaint.
> 
> I don't think it should "fix" the problem.  If the peer fails to respond
> as expected, it has to declare the remote address to be unreachable.
> 
> <hs> But the peer is reachable in this p2p model !

Some bugs can result in a lack of connectivity.  This looks like one
of them.

My question here is why this specific bug should be considered special
enough that we ought to carve out exceptions in order to make it
work.  Why is that?  If some system had gotten the checksum
computation or byte order wrong in some field, we wouldn't write
workarounds for those errors as well, would we?

> Yes, it'd be possible to carve out a hole in NUD and say that if there's
> _never_ a response from the peer to any NS for the life of the link, and
> if the link is specifically point-to-point and without link layer
> addresses, and if the link-layer is known to perform keepalive- like
> operation, then the NS sender could "assume" that the address is
> actually reachable.
> 
> <hs> Let's not start preparing text for changes to 2461bis for PPP
> unless we can first discuss what to do about the server bug that Dave
> pointed out.

I'm not trying to prepare any changes for 2461bis, except to show how
complicated it would be in order to carve out the exception that I
think you're proposing here.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From ipv6-bounces@ietf.org Mon Jul 23 17:32: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 1ID5VA-00022I-Mi; Mon, 23 Jul 2007 17:31:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ID5V8-000227-RY
	for ipv6@ietf.org; Mon, 23 Jul 2007 17:31:34 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ID5V8-0004JD-DF
	for ipv6@ietf.org; Mon, 23 Jul 2007 17:31:34 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 23 Jul 2007 17:31:34 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAC67pEZAZnmf/2dsb2JhbACCZA
X-IronPort-AV: i="4.16,572,1175486400"; 
	d="scan'208,217"; a="126812629:sNHT52189058"
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 l6NLVYxX005974; 
	Mon, 23 Jul 2007 17:31:34 -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 l6NLUYWq024686; 
	Mon, 23 Jul 2007 21:31:34 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); 
	Mon, 23 Jul 2007 17:31:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 23 Jul 2007 17:31:23 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEC97@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of draft-wbeebee-nd-implementation-pitfalls is
	available
Thread-Index: AcfNcNF6KgZDeLWCSYyZTOwbbpFkzw==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 23 Jul 2007 21:31:29.0998 (UTC)
	FILETIME=[D52E96E0:01C7CD70]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3044; t=1185226294;
	x=1186090294; 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:=20New=20version=20of=20draft-wbeebee-nd-implementation-pitfalls
	=20is=20available |Sender:=20 |To:=20<ipv6@ietf.org>;
	bh=/w4Pq1o4ABEfwPkBREIZRUsf511r5T+4/IuVUp0h8yM=;
	b=kbK9RWfcUirMJU3pcb91KI/V6h15KIUDFoGKT2OkOdvvLp4yVEUcDK2yAfE0yzD4JZ5c2Joc
	NEVEnLPo/Jitb/pHHAg0IxmTes42HR7c80ldR1XiIyB4TxZVgLnQr2QR;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: varada@txc.com
Subject: New version of draft-wbeebee-nd-implementation-pitfalls is available
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============1791592580=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1791592580==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7CD70.D50C35DF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7CD70.D50C35DF
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Folks,
=20
Please see a new version of our I-D at the URL below.=20
=20
http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
alls-02.txt
=20
See change log to understand what has changed from the -01 version.
Gross changes worth highlighting are:
=20
1. A new section 7 has been added to the I-D that lists IPv6 ND
implementation problems ala RFC 2525.
2. Section 5 is complete that lists proposed changes to 24621bis.
3. Section 6 has been edited and augmented for proposed changes to
2462bis.
=20
Best Regards.
=20
Hemant

------_=_NextPart_001_01C7CD70.D50C35DF
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><FONT face=3DArial size=3D2><SPAN=20
class=3D374242621-23072007>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D374242621-23072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D374242621-23072007>Please =
see a new=20
version of our I-D at the URL below. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementati=
on-pitfalls-02.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-nd-=
implementation-pitfalls-02.txt</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>See =
change log to=20
understand what has changed from the -01 version. Gross changes worth=20
highlighting are:</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>1. A =
new section 7=20
has been added to the I-D that lists IPv6 ND implementation problems ala =
RFC=20
2525.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>2. =
Section 5 is=20
complete that lists proposed changes to 24621bis.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>3. =
Section 6 has=20
been edited and augmented for proposed changes to =
2462bis.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>Best=20
Regards.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2>Hemant</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C7CD70.D50C35DF--


--===============1791592580==
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
--------------------------------------------------------------------

--===============1791592580==--




From ipv6-bounces@ietf.org Tue Jul 24 02:40: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 1IDE3L-0002zt-C2; Tue, 24 Jul 2007 02:39:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDE3K-0002zj-9n
	for ipv6@ietf.org; Tue, 24 Jul 2007 02:39:26 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDE3F-0005aJ-A7
	for ipv6@ietf.org; Tue, 24 Jul 2007 02:39:21 -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 l6O6dJ5F097567
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 24 Jul 2007 08:39: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
	l6O6dIE9019948; Tue, 24 Jul 2007 08:39:18 +0200
Date: Tue, 24 Jul 2007 08:39:18 +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: <28681.1184163817@sa.vix.com>
Message-ID: <Pine.LNX.4.64.0707240838150.13685@chandra.student.uit.no>
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<28681.1184163817@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.62 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ipv6@ietf.org, roger@jorgensen.no
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 what has happen to this? Still no feedback from authors or chairs or?


On Wed, 11 Jul 2007, Paul Vixie wrote:
<snip>
>> I'm not sure what the status of Paul's document is since the drafts
>> directory only contains this one:
>> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ula-central-02.txt
>>
>> Is Paul's superceding that or is there a merge in process?
>
> the other authors of ula-global have not commented on my hijackery.  they
> might be supportive, or angry, or complacent, about the draft-fork i made.
> maybe they'll want their names removed.  maybe they'll want to merge ula-g
> into ula-c and have my name removed.  maybe they'll want the fork to stay.
>
> the i-d editor determined that my submission came after the chicago cutoff,
> which really oughtn't apply for WG's that are not meeting, but so it goes.
>
> the WG chairs have ignored my mail thus far.
>
> so my take is, suggested changes and statements of opposition||support can
> be made based on the text at http://sa.vix.com/~vixie/ula-global.txt.  i'll
> be rev'ing the draft based on james' and scott's comments shortly.
>
> --------------------------------------------------------------------
> 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 Tue Jul 24 04:58: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 1IDGDn-0008TP-9d; Tue, 24 Jul 2007 04:58:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDGDk-0008T7-U5
	for ipv6@ietf.org; Tue, 24 Jul 2007 04:58:20 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDGDk-0000xN-DD
	for ipv6@ietf.org; Tue, 24 Jul 2007 04:58:20 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.114]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 09:58: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: Tue, 24 Jul 2007 09:58:06 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0BF872D@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <Pine.LNX.4.64.0707240838150.13685@chandra.student.uit.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-ipv6-ula-central-02.txt
Thread-Index: AcfNvXlFXS84InK0SIqRYsQ9EfmpRQAEsEAg
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com><Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no><D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net><28681.1184163817@sa.vix.com>
	<Pine.LNX.4.64.0707240838150.13685@chandra.student.uit.no>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 24 Jul 2007 08:58:19.0789 (UTC)
	FILETIME=[C821ABD0:01C7CDD0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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 what has happen to this? Still no feedback from authors or=20
> chairs or?

The WG chairs have asked the authors of the draft to review and edit it
because there is not currently consensus on ULA-C. If those authors are
smart, they will work with Vixie and incorporate some of the comments
from this list as well. Once they have finished editing, they will
submit a new draft and we will have something to comment on.

Or they may simply go away having given up on finding consensus. In that
case, Vixie's draft is still in play I believe.

I suggest that you contact the authors directly if you have some
concerns. Not all work occurs on the list.

--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 Jul 24 07:14: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 1IDIKu-0000Ei-VP; Tue, 24 Jul 2007 07:13:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDIKt-0000Ec-HN
	for ipv6@ietf.org; Tue, 24 Jul 2007 07:13:51 -0400
Received: from sa.vix.com ([2001:4f8:3:bb::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDIKt-0003qs-3r
	for ipv6@ietf.org; Tue, 24 Jul 2007 07:13:51 -0400
Received: from sa.vix.com (localhost [127.0.0.1])
	by sa.vix.com (Postfix) with ESMTP id 6EE8011427;
	Tue, 24 Jul 2007 11:13:50 +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, 24 Jul 2007 08:39:18 +0200."
	<Pine.LNX.4.64.0707240838150.13685@chandra.student.uit.no> 
References: <200706251556.l5PFu6Qa057410@mail.reprise.com><078201c7bdb0$503f2dc0$543816ac@atlanta.polycom.com><94065E4E-7A57-46AC-8A13-D7591C26EA13@apple.com><Pine.LNX.4.64.0707101337220.9923@chandra.student.uit.no><FEB5791F-8495-4905-8D6C-D454F46FD976@apple.com><22851.1184090216@sa.vix.com><B29043A9-6165-47FB-B83A-0A5272A0C451@apple.com>
	<Pine.LNX.4.64.0707111133400.9923@chandra.student.uit.no>
	<D03E4899F2FB3D4C8464E8C76B3B68B0AA2CAA@E03MVC4-UKBR.domain1.systemhost.net>
	<28681.1184163817@sa.vix.com>
	<Pine.LNX.4.64.0707240838150.13685@chandra.student.uit.no> 
X-Mailer: MH-E 8.0.2; nmh 1.0.4; GNU Emacs 21.3.1
Date: Tue, 24 Jul 2007 11:13:50 +0000
Message-ID: <80545.1185275630@sa.vix.com>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 01485d64dfa90b45a74269b3ca9d5574
Cc: ipv6@ietf.org, roger@jorgensen.no
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 what has happen to this? Still no feedback from authors or chairs or?

nothing.

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



From ipv6-bounces@ietf.org Tue Jul 24 11: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 1IDM92-0002qk-S7; Tue, 24 Jul 2007 11:17:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDM91-0002pw-8u
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:17:51 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDM8z-0004mz-VP
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:17:51 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l6OFMRtc022756
	for <ipv6@ietf.org>; Tue, 24 Jul 2007 10:22:27 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 10:17:48 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 10:17:48 -0500
Message-ID: <46A6188B.3030607@ericsson.com>
Date: Tue, 24 Jul 2007 11:19:39 -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: 24 Jul 2007 15:17:48.0400 (UTC)
	FILETIME=[CB47FF00:01C7CE05]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: Reserved IIDs - TAKE 2
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,
   Some RFCs (I know of at least 2, RFC2526 and RFC4291) reserve a set 
of interface identifiers on all prefixes. These identifiers need to be 
excluded when a node autoconfigures an address. This problem occurs with 
privacy addresses but is equally applicable to other address assigment 
methods like dhcpv6, cga etc. Instead of new documents referring to each 
of these RFCs individually it would be convenient to have a single store 
of information. Recently (due to upcoming RFC4941) I also found out that 
some of the documents reserving such identifiers may be on a lower 
maturity level than the ones that need to use the identifiers. Hence it 
makes sense to create an IANA registry for this purpose. I would like to 
hear people's opinions on this. I would like to pursue this either as a 
WG document or a personal submission. You can find my draft at

http://tools.ietf.org/wg/ipv6/draft-krishnan-ipv6-reserved-iids-01.txt

Thanks
Suresh

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



From ipv6-bounces@ietf.org Tue Jul 24 11:35: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 1IDMPs-0008NG-65; Tue, 24 Jul 2007 11:35:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMPr-0008N8-2U
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:35:15 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDMPq-00027n-N5
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:35:15 -0400
Received: from leon.remlab.net (unknown
	[IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(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 AF6C69675A;
	Tue, 24 Jul 2007 17:35:13 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: ipv6@ietf.org
Date: Tue, 24 Jul 2007 18:35:09 +0300
User-Agent: KMail/1.9.6
References: <46A6188B.3030607@ericsson.com>
In-Reply-To: <46A6188B.3030607@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200707241835.09880.rdenis@simphalempin.com>
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Reserved IIDs - TAKE 2
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

On Tuesday 24 July 2007 18:19:39 Suresh Krishnan wrote:
> http://tools.ietf.org/wg/ipv6/draft-krishnan-ipv6-reserved-iids-01.txt

I wonder if ISATAP needs to be included here. It was my understanding that =
you=20
cannot use non-ISATAP IIDs on ISATAP virtual links, and that ISATAP IIDs ha=
d=20
no particular meaning on non ISATAP links.

Or perhaps, is the intent merely to avoid human confusion?

=2D-=20
R=E9mi Denis-Courmont

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



From ipv6-bounces@ietf.org Tue Jul 24 11:37: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 1IDMS1-0001Ut-5P; Tue, 24 Jul 2007 11:37:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMS0-0001Uj-Kq
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:37:28 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDMS0-0005cw-7p
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:37:28 -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 l6OFg6MP026944;
	Tue, 24 Jul 2007 10:42:06 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 10:37:27 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 24 Jul 2007 10:37:27 -0500
Message-ID: <46A61D25.4060205@ericsson.com>
Date: Tue, 24 Jul 2007 11:39:17 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
References: <46A6188B.3030607@ericsson.com>
	<200707241835.09880.rdenis@simphalempin.com>
In-Reply-To: <200707241835.09880.rdenis@simphalempin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 24 Jul 2007 15:37:27.0282 (UTC)
	FILETIME=[89F31D20:01C7CE08]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by imr1.ericy.com id
	l6OFg6MP026944
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org
Subject: Re: Reserved IIDs - TAKE 2
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Remi,
   Thanks for pointing this out. Fred Templin convinced me that=20
including ISATAP IIDs was not necessary. I am convinced as well, but I=20
could not make the change in time for the cutoff. I will remove these in=20
-02.

Thanks
Suresh

R=E9mi Denis-Courmont wrote:
> 	Hello,
>=20
> On Tuesday 24 July 2007 18:19:39 Suresh Krishnan wrote:
>> http://tools.ietf.org/wg/ipv6/draft-krishnan-ipv6-reserved-iids-01.txt
>=20
> I wonder if ISATAP needs to be included here. It was my understanding t=
hat you=20
> cannot use non-ISATAP IIDs on ISATAP virtual links, and that ISATAP IID=
s had=20
> no particular meaning on non ISATAP links.
>=20
> Or perhaps, is the intent merely to avoid human confusion?
>=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 Jul 24 11:44: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 1IDMYh-0004GQ-Cv; Tue, 24 Jul 2007 11:44:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMYf-0004GC-Du
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:44:21 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDMYf-0005mv-1R
	for ipv6@ietf.org; Tue, 24 Jul 2007 11:44:21 -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 l6OFiGVQ008220
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 24 Jul 2007 08:44:16 -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
	l6OFiGt5000993; Tue, 24 Jul 2007 08:44:16 -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
	l6OFiFv7000933; Tue, 24 Jul 2007 08:44: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, 24 Jul 2007 08:44:12 -0700
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: Tue, 24 Jul 2007 08:44:11 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED933@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <200707241835.09880.rdenis@simphalempin.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reserved IIDs - TAKE 2
Thread-Index: AcfOCF1s1TEOkDYnS5qRMSXIy4nR2AAAE9Sw
References: <46A6188B.3030607@ericsson.com>
	<200707241835.09880.rdenis@simphalempin.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 24 Jul 2007 15:44:12.0122 (UTC)
	FILETIME=[7B40CBA0:01C7CE09]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: RE: Reserved IIDs - TAKE 2
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 wonder if ISATAP needs to be included here.

I am sort of still wondering this, too. But, see below and
also Suresh's follow-up message.

> It was my understanding that you=20
> cannot use non-ISATAP IIDs on ISATAP virtual links,

Correct.

> and that ISATAP IIDs had no particular meaning on non ISATAP links.

Also correct, which is why I tried to convince Suresh that their
inclusion in his list was not necessary.

> Or perhaps, is the intent merely to avoid human confusion?

AFAICT, this would be the one reason for including the IIDs
in Suresh's list. Maybe there is still some potential issue
for mis-configuration here that would warrant keeping them
on the list?

Fred
fred.l.templin@boeing.com

> --=20
> R=E9mi Denis-Courmont
>=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 Jul 26 14:20: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 1IE7vm-0005gI-02; Thu, 26 Jul 2007 14:19:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7uE-00030B-P0
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:17:46 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE7uE-0004Ul-Bg
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:17:46 -0400
Received: from ([128.244.96.129])
	by pilot.jhuapl.edu with ESMTP  id 5502123.39395531;
	Thu, 26 Jul 2007 14:17:26 -0400
Message-ID: <46A8E537.60504@innovationslab.net>
Date: Thu, 26 Jul 2007 14:17:27 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: IPv6 WG Mailing List <ipv6@ietf.org>
X-Enigmail-Version: 0.94.1.2
Content-Type: multipart/mixed; boundary="------------050109030600060709050302"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
X-Mailman-Approved-At: Thu, 26 Jul 2007 14:19:21 -0400
Cc: 
Subject: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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.
--------------050109030600060709050302
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

All,
     The IPv6 WG chairs have had several discussions on the future of
the IPv6 WG with our AD (Jari Arkko).  The recommended way forward is to
close the existing IPv6 WG and create an IPv6 maintenance working group.
 The attached proposed charter describes the new group.

     The sole purpose of this group is in the maintenance of the core
IPv6 protocol specifications and *not* in the development of new
solutions or changes to the specifications.  For example, the deployment
of new transition tools is out of scope of this working group.
Proposals for work beyond the scope of this working group should be sent
to relevant ADs.

     Please review the proposed charter and provide comments.

Regards,
Brian & Bob


--------------050109030600060709050302
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="6man-charter.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="6man-charter.txt"

IPv6 Maintenance Working Group (6man)
------------------------------------------------------------------------

Chair(s):

     Robert Hinden <bob.hinden@nokia.com>
     Brian Haberman <brian@innovationslab.net>


Internet Area Director(s):

     Jari Arkko <jari.arkko@piuha.net>
     Mark Townsley <townsley@cisco.com>


Internet Area Advisor:

     Jari Arkko <jari.arkko@piuha.net>


Mailing Lists: ipv6@ietf.org


Description of Working Group:

The 6man working group is responsible for the maintenance, upkeep, and advancement
of the core IPv6 protocol specifications.  It is not chartered to
develop major changes or additions to the core IPv6 specification.
The working group will address protocol limitations/issues discovered during
deployment and operation.

The working group's work items are as follows:

     o Shepherd completion of standardization of RA Flags Option
     o Shepherd completion of standardization of the RH0 Deprecation document
     o Complete documentation/standardization of IPv6 over PPP Compression Negotiation
     o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)

All new work items not listed above require the approval of the working
group and IESG before they will be taken on by the working group.


Goals and Milestones:

Sep 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard
Jan 2008     Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
Jul 2008     Submit ULA-C specification to IESG as a Proposed Standard


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

--------------050109030600060709050302--




From ipv6-bounces@ietf.org Thu Jul 26 14:23: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 1IE7zj-0008P3-Jr; Thu, 26 Jul 2007 14:23:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE7zi-0008Oy-IH
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:23:26 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE7zh-0005qw-4W
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:23:26 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id EA7F7198680;
	Thu, 26 Jul 2007 21:23:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 15FBC1985FB;
	Thu, 26 Jul 2007 21:23:22 +0300 (EEST)
Message-ID: <46A8E69A.2070009@piuha.net>
Date: Thu, 26 Jul 2007 13:23:22 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <46A8E537.60504@innovationslab.net>
In-Reply-To: <46A8E537.60504@innovationslab.net>
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: 08170828343bcf1325e4a0fb4584481c
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 me just add something on this:
> For example, the deployment
> of new transition tools is out of scope of this working group.
> Proposals for work beyond the scope of this working group should be sent
> to relevant ADs.
>   
This is a topic that I would like to see discussed in the
the IETF, at least in the form of asking whether we
have requirements for new work. The new maintenance
group that we are creating is not the right place for
that discussion, but I do want to have a forum. Stay
tuned.

Jari


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



From ipv6-bounces@ietf.org Thu Jul 26 14: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 1IE80Z-0000H8-Mg; Thu, 26 Jul 2007 14:24:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE80Y-0000Gz-G6
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:24: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 1IE80Y-0005s1-1K
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:24:18 -0400
Received: from coconut.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id F3710233C4;
	Fri, 27 Jul 2007 03:24:15 +0900 (JST)
To: Brian Haberman <brian@innovationslab.net>
In-reply-to: brian's message of Thu,
	26 Jul 2007 14:17:27 -0400. <46A8E537.60504@innovationslab.net> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Date: Fri, 27 Jul 2007 03:24:15 +0900
Message-Id: <20070726182415.F3710233C4@coconut.itojun.org>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 sole purpose of this group is in the maintenance of the core
>IPv6 protocol specifications and *not* in the development of new
>solutions or changes to the specifications.  For example, the deployment
>of new transition tools is out of scope of this working group.
>Proposals for work beyond the scope of this working group should be sent
>to relevant ADs.
>
>     Please review the proposed charter and provide comments.

	i think it is a bit minor, but i thought i should bring it up.

	from the proposed charter:

>     o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)
>Jul 2008     Submit ULA-C specification to IESG as a Proposed Standard

	i'm not too sure if ULA-C has wg consenssu to be the way forward.
	so i would object to this wording.

	note: there was problem raised in SIDR as to how to handle X509 certs
	for ULA (or ULA-C?  i'm not sure about it)

itojun

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



From ipv6-bounces@ietf.org Thu Jul 26 14:33: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 1IE89S-0000Yd-It; Thu, 26 Jul 2007 14:33:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE89P-0000Vt-OW
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:33:28 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE89P-00061G-G0
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:33:27 -0400
Received: from leon.remlab.net (unknown
	[IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(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 1DBD296691;
	Thu, 26 Jul 2007 20:33:26 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: ipv6@ietf.org
Date: Thu, 26 Jul 2007 21:33:22 +0300
User-Agent: KMail/1.9.6
References: <46A8E537.60504@innovationslab.net> <46A8E69A.2070009@piuha.net>
In-Reply-To: <46A8E69A.2070009@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200707262133.22568.rdenis@simphalempin.com>
X-Spam-Score: -0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Brian Haberman <brian@innovationslab.net>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Thursday 26 July 2007 21:23:22 Jari Arkko wrote:
> Let me just add something on this:
> > For example, the deployment
> > of new transition tools is out of scope of this working group.
> > Proposals for work beyond the scope of this working group should be sent
> > to relevant ADs.
>
> This is a topic that I would like to see discussed in the
> the IETF, at least in the form of asking whether we
> have requirements for new work. The new maintenance
> group that we are creating is not the right place for
> that discussion, but I do want to have a forum. Stay
> tuned.

Yup. What about maintenance of existing non-core specifications, by the way?

=2D-=20
R=E9mi Denis-Courmont
Nokia software specialist

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



From ipv6-bounces@ietf.org Thu Jul 26 14:37: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 1IE8DH-0002oN-7v; Thu, 26 Jul 2007 14:37:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8DG-0002oI-Iy
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:37:26 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8DG-0004uj-9L
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:37:26 -0400
Received: from ([24.40.15.92])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.9745077;
	Thu, 26 Jul 2007 14:37: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, 26 Jul 2007 14:37:04 -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, 26 Jul 2007 14:37:02 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD402A3DEB6@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <46A8E537.60504@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Closure of IPv6 WG and creation of IPv6 Maintenance WG
Thread-Index: AcfPsaqHwLB8RZqPSvSWO3e9R/v7cwAAiMlQ
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Brian Haberman" <brian@innovationslab.net>,
	"IPv6 WG Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 18:37:04.0582 (UTC)
	FILETIME=[F68C1660:01C7CFB3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: 
Subject: RE: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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
> The working group's work items are as follows:
>
>     o Shepherd completion of standardization of RA Flags Option
>     o Shepherd completion of standardization of the RH0 Deprecation
document
>     o Complete documentation/standardization of IPv6 over PPP
Compression Negotiation
>     o Complete work on Centrally Allocated Unique Local Addresses
(ULA-C)

Considering ULA as a core IPv6 protocol is a hard sell.

   - Alain.

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



From ipv6-bounces@ietf.org Thu Jul 26 14:58: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 1IE8XJ-0004xC-9h; Thu, 26 Jul 2007 14:58:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8XH-0004qE-Tf
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:58:07 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8XH-0005G3-DK
	for ipv6@ietf.org; Thu, 26 Jul 2007 14:58:07 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6QIw4Kg026401; Thu, 26 Jul 2007 21:58:05 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 21:58:04 +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, 26 Jul 2007 21:58:03 +0300
Received: from [130.129.21.210] (daec-linuxvpn059142.americas.nokia.com
	[10.241.59.142])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l6QIw1Ju029203; Thu, 26 Jul 2007 21:58:02 +0300
In-Reply-To: <20070726182415.F3710233C4@coconut.itojun.org>
References: <20070726182415.F3710233C4@coconut.itojun.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9669897A-F899-4E2B-AEB8-7C357B5CCEC1@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Thu, 26 Jul 2007 13:58:15 -0500
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 26 Jul 2007 18:58:03.0927 (UTC)
	FILETIME=[E52CE270:01C7CFB6]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG 
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

Itujun,

>
>>     o Complete work on Centrally Allocated Unique Local Addresses  
>> (ULA-C)
>> Jul 2008     Submit ULA-C specification to IESG as a Proposed  
>> Standard
>
> 	i'm not too sure if ULA-C has wg consenssu to be the way forward.
> 	so i would object to this wording.
>

"Complete work" was intended to mean seeing if there is a consensus  
to move forward with some sort of central ULA.  If there is no  
consensus, then the work will be dropped.

Personally, I don't see anything close to a consensus at the moment.

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 Jul 26 15:05: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 1IE8eQ-0004Uf-LT; Thu, 26 Jul 2007 15:05:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8eP-0004Ua-Da
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:05:29 -0400
Received: from 207-172-210-101.c3-0.hdp-ubr1.sbo-hdp.ma.static.cable.rcn.com
	([207.172.210.101] helo=mailhost.m5p.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE8eO-0006Zl-22
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:05:29 -0400
Received: from m5p.com (mailhost.m5p.com [IPv6:2001:418:3fd::f7])
	by mailhost.m5p.com (8.13.8/8.13.8) with ESMTP id l6QJ5P4E034771
	(version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO)
	for <ipv6@ietf.org>; Thu, 26 Jul 2007 15:05:25 -0400 (EDT)
Received: (from george@localhost)
	by m5p.com (8.13.8/8.13.7/Submit) id l6QJ5ONM034770;
	Thu, 26 Jul 2007 15:05:24 -0400 (EDT)
Date: Thu, 26 Jul 2007 15:05:24 -0400 (EDT)
Message-Id: <200707261905.l6QJ5ONM034770@m5p.com>
From: george+ipng@m5p.com
To: ipv6@ietf.org
X-Spam-Score: -0.001 () NO_RELAYS
X-Scanned-By: MIMEDefang 2.57 on IPv6:2001:418:3fd::f7
X-Spam-Score: 1.7 (+)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>      o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)

I remain unconvinced of the need for central allocation.  I trust
arc4random() more than human administrators.  Taking care of reverse
DNS automatically solves a non-problem.

Anyone interested in a random number is invited to visit
http://www.f-iw.org/random.cgi.                 -- 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 Thu Jul 26 15: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 1IE8f9-000554-Ha; Thu, 26 Jul 2007 15:06:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8b1-0002Lq-FS
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:01:59 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8b1-0005KV-5g
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:01:59 -0400
Received: from ([128.244.96.142])
	by pilot.jhuapl.edu with ESMTP  id 5502123.39400533;
	Thu, 26 Jul 2007 15:01:32 -0400
Message-ID: <46A8EF8D.2000805@innovationslab.net>
Date: Thu, 26 Jul 2007 15:01:33 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
References: <46A8E537.60504@innovationslab.net> <46A8E69A.2070009@piuha.net>
	<200707262133.22568.rdenis@simphalempin.com>
In-Reply-To: <200707262133.22568.rdenis@simphalempin.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Thu, 26 Jul 2007 15:06:14 -0400
Cc: ipv6@ietf.org
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Rémi Denis-Courmont wrote:
> On Thursday 26 July 2007 21:23:22 Jari Arkko wrote:
>> Let me just add something on this:
>>> For example, the deployment
>>> of new transition tools is out of scope of this working group.
>>> Proposals for work beyond the scope of this working group should be sent
>>> to relevant ADs.
>> This is a topic that I would like to see discussed in the
>> the IETF, at least in the form of asking whether we
>> have requirements for new work. The new maintenance
>> group that we are creating is not the right place for
>> that discussion, but I do want to have a forum. Stay
>> tuned.
> 
> Yup. What about maintenance of existing non-core specifications, by the way?

Do you have an example of such a specification you are worried about?

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 Thu Jul 26 15:06: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 1IE8fB-00059j-06; Thu, 26 Jul 2007 15:06:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8cS-0003IS-81
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:03:28 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8cR-0005Mw-Tv
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:03:28 -0400
Received: from ([128.244.96.142])
	by pilot.jhuapl.edu with ESMTP  id 5502123.39400692;
	Thu, 26 Jul 2007 15:03:06 -0400
Message-ID: <46A8EFEB.8040708@innovationslab.net>
Date: Thu, 26 Jul 2007 15:03:07 -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: <EF2F0EC839870F43A6637360BC12ABD402A3DEB6@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD402A3DEB6@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: 7655788c23eb79e336f5f8ba8bce7906
X-Mailman-Approved-At: Thu, 26 Jul 2007 15:06:14 -0400
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Alain,

Durand, Alain wrote:
>  
>> The working group's work items are as follows:
>>
>>     o Shepherd completion of standardization of RA Flags Option
>>     o Shepherd completion of standardization of the RH0 Deprecation
> document
>>     o Complete documentation/standardization of IPv6 over PPP
> Compression Negotiation
>>     o Complete work on Centrally Allocated Unique Local Addresses
> (ULA-C)
> 
> Considering ULA as a core IPv6 protocol is a hard sell.
> 

I personally am not considering ULA a core protocol.  However, the work
on ULA (whatever the outcome) needs a home.

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 Thu Jul 26 15:06: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 1IE8fC-0005Ei-7g; Thu, 26 Jul 2007 15:06:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8et-0004xY-2I
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:05:59 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE8es-0005Q2-NI
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:05:58 -0400
Received: from ([128.244.96.142])
	by pilot.jhuapl.edu with ESMTP  id 5502123.39401007;
	Thu, 26 Jul 2007 15:05:47 -0400
Message-ID: <46A8F08C.5080404@innovationslab.net>
Date: Thu, 26 Jul 2007 15:05:48 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
References: <20070726182415.F3710233C4@coconut.itojun.org>
In-Reply-To: <20070726182415.F3710233C4@coconut.itojun.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: 97adf591118a232206bdb5a27b217034
X-Mailman-Approved-At: Thu, 26 Jul 2007 15:06:14 -0400
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Itojun,

Jun-ichiro itojun Hagino wrote:
>>     The sole purpose of this group is in the maintenance of the core
>> IPv6 protocol specifications and *not* in the development of new
>> solutions or changes to the specifications.  For example, the deployment
>> of new transition tools is out of scope of this working group.
>> Proposals for work beyond the scope of this working group should be sent
>> to relevant ADs.
>>
>>     Please review the proposed charter and provide comments.
> 
> 	i think it is a bit minor, but i thought i should bring it up.
> 
> 	from the proposed charter:
> 
>>     o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)
>> Jul 2008     Submit ULA-C specification to IESG as a Proposed Standard
> 
> 	i'm not too sure if ULA-C has wg consenssu to be the way forward.
> 	so i would object to this wording.
> 
> 	note: there was problem raised in SIDR as to how to handle X509 certs
> 	for ULA (or ULA-C?  i'm not sure about it)

The mention of ULA in SIDR was more for completeness in their discussion
of how to handle private addresses in general (including 1918 addresses
in IPv4).  One of the co-chairs of that group is actively involved in
the ULA discussion and the other co-chair and I had a long discussion on
them as well.  The outcome from SIDR is a need for them to consider how
their solutions address the use of all private addresses.

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 Thu Jul 26 15: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 1IE8ki-0001yI-BG; Thu, 26 Jul 2007 15:12:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE8kh-0001yC-9P
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:11:59 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE8kh-0006hf-1n
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:11:59 -0400
Received: from leon.remlab.net (unknown
	[IPv6:2001:df8:0:16:219:d2ff:fe07:5de5])
	(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 44F37967F7;
	Thu, 26 Jul 2007 21:11:58 +0200 (CEST)
From: =?iso-8859-1?q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: Brian Haberman <brian@innovationslab.net>
Date: Thu, 26 Jul 2007 22:11:54 +0300
User-Agent: KMail/1.9.6
References: <46A8E537.60504@innovationslab.net>
	<200707262133.22568.rdenis@simphalempin.com>
	<46A8EF8D.2000805@innovationslab.net>
In-Reply-To: <46A8EF8D.2000805@innovationslab.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200707262211.55083.rdenis@simphalempin.com>
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: ipv6@ietf.org
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Thursday 26 July 2007 22:01:33 Brian Haberman wrote:
> > Yup. What about maintenance of existing non-core specifications, by the
> > way?
>
> Do you have an example of such a specification you are worried about?

Teredo's one that showed up at v6ops meeting.

=2D-=20
R=E9mi Denis-Courmont

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



From ipv6-bounces@ietf.org Thu Jul 26 15:28: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 1IE90P-0000Eu-K8; Thu, 26 Jul 2007 15:28:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE90O-0000Ei-4f
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:28:12 -0400
Received: from wa-out-1112.google.com ([209.85.146.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE90M-000778-Oh
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:28:12 -0400
Received: by wa-out-1112.google.com with SMTP id j37so504701waf
	for <ipv6@ietf.org>; Thu, 26 Jul 2007 12:28: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:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=CmNL7z221VaetVFk6h4DE++KVnSUWaE1QiC+0IiKClwzCzKJwPr/8Sh+FoD8LCmDuvUjLxcIaU5s24Q1VHZs/wXx55uXLKtSgX3BDZNDjOX2etdvxbRbUZPOAK+p5brWbR0KSqHDZ5U9ZwVPIJ5IAjJGPbAXmaT/VKH5a2HM+QU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=CjcdZkMP094pCwgjWsFyCf3hxndsr6SLTOrNXIZihmeUOZ/09aw1BdnhE3JTCWPHGS9q7F9UJ1/PY430m073RWu2+s5BaKB7KhSyNKLSd5ybLbUi6aA2Zco5qvanXYuZxhdc+jZaOmuM69Oc9c1LZi2ImxKREkd0WrL4TCDDsaI=
Received: by 10.114.179.1 with SMTP id b1mr2131265waf.1185478089181;
	Thu, 26 Jul 2007 12:28:09 -0700 (PDT)
Received: by 10.114.94.12 with HTTP; Thu, 26 Jul 2007 12:28:09 -0700 (PDT)
Message-ID: <75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.com>
Date: Thu, 26 Jul 2007 15:28:09 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "IPv6 WG Mailing List" <ipv6@ietf.org>
In-Reply-To: <46A8E537.60504@innovationslab.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46A8E537.60504@innovationslab.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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/26/07, Brian Haberman <brian@innovationslab.net> wrote:
...
> The working group's work items are as follows:
>
>      o Shepherd completion of standardization of the RH0 Deprecation document
...
> All new work items not listed above require the approval of the working
> group and IESG before they will be taken on by the working group.
>

I didn't think there was consensus on the RH0 direction yet, was there?

> Goals and Milestones:
>
> Sep 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard

-Chris

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



From ipv6-bounces@ietf.org Thu Jul 26 15:35: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 1IE97O-0000Ob-3j; Thu, 26 Jul 2007 15:35:26 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE97M-0000OS-C7
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:35:24 -0400
Received: from vms048pub.verizon.net ([206.46.252.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE97L-0006Bo-Vf
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:35:24 -0400
Received: from vms246.mailsrvcs.net ([192.168.1.2])
	by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JLS00CAQX2L3MS5@vms048.mailsrvcs.net> for
	ipv6@ietf.org; Thu, 26 Jul 2007 14:35:09 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms246.mailsrvcs.net (Verizon Webmail) with HTTP; Thu,
	26 Jul 2007 14:35:09 -0500 (CDT)
Date: Thu, 26 Jul 2007 14:35:09 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Brian Haberman <brian@innovationslab.net>
Message-id: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

>Alain,
>
>Durand, Alain wrote:
>>  
>>> The working group's work items are as follows:
>>>
>>>     o Shepherd completion of standardization of RA Flags Option
>>>     o Shepherd completion of standardization of the RH0 Deprecation
>> document
>>>     o Complete documentation/standardization of IPv6 over PPP
>> Compression Negotiation
>>>     o Complete work on Centrally Allocated Unique Local Addresses
>> (ULA-C)
>> 
>> Considering ULA as a core IPv6 protocol is a hard sell.
>> 
>
>I personally am not considering ULA a core protocol.  However, the work
>on ULA (whatever the outcome) needs a home.

I agree that ULA-C "needs a home" but disagree the IPv6 Maintenance WG is it, given:

* the first paragraph of the proposed charter:

"The sole purpose of this group is in the maintenance of the core
IPv6 protocol specifications and *not* in the development of new
solutions or changes to the specifications.."

&& at least one of the group chairs doesn't consider it to be a core protocol,

&& at least one of the group chairs doesn't see group consensus on ULA-C,

&& there are other group members who don't see group consensus on ULA-C,

&& we haven't heard from any group members who do see group consensus on ULA-C,

&& "Complete work" is meant to be predicated upon group consensus

I'd say it should be removed from the charter.

>
>Regards,
>Brian

Best Regards,

Tim Enos
Rom 8:28
>
>
>--------------------------------------------------------------------
>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 Jul 26 15:46: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 1IE9Hz-0001gt-LE; Thu, 26 Jul 2007 15:46:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9Hy-0001gn-UH
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:46:22 -0400
Received: from ug-out-1314.google.com ([66.249.92.168])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IE9Hx-0007Z9-GN
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:46:22 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1825949uge
	for <ipv6@ietf.org>; Thu, 26 Jul 2007 12:46:19 -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=gOTEL0yleKXS8VIKJO/52/V+gQ16LMrQA8w0lfL1y1iMEGM0f2YCbOC9zmt1lwbe32fEILfQT5DR3ZOqCnB3Bq79yL+UNiHfRazp5FEbNeShti2kZ9x/WVfvF0XJEJz15A3GIXw6WBM9Lzu8HI6XGrD+oVmzBafc0D9vOMaOgQ4=
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=n7nzgSqnunluAiNN7NbPd7Nsyrxbn0roZ5amK8yrMu+Tik7OHweDe9WL9OfUub63CJ+WDBXloHYaOXEeSVyVUAD6xK1xomWtVSd27T2NdRfc0B0gOhAP6dHRjy77brXOf4LUrgLdUBxz/qLRTvIyyS81cVCcoYcSP5huQHHDHFo=
Received: by 10.67.15.15 with SMTP id s15mr2373992ugi.1185479179424;
	Thu, 26 Jul 2007 12:46:19 -0700 (PDT)
Received: from ?130.129.17.141? ( [130.129.17.141])
	by mx.google.com with ESMTPS id l4sm703830ugf.2007.07.26.12.46.17
	(version=SSLv3 cipher=RC4-MD5); Thu, 26 Jul 2007 12:46:18 -0700 (PDT)
Message-ID: <46A8FA06.1070408@gmail.com>
Date: Thu, 26 Jul 2007 21:46:14 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <46A8E537.60504@innovationslab.net> <46A8E69A.2070009@piuha.net>
In-Reply-To: <46A8E69A.2070009@piuha.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Brian Haberman <brian@innovationslab.net>,
	IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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,

I hesitated about cross-posting this comment to v6ops too...

On 2007-07-26 20:23, Jari Arkko wrote:
> Let me just add something on this:
>> For example, the deployment
>> of new transition tools is out of scope of this working group.
>> Proposals for work beyond the scope of this working group should be sent
>> to relevant ADs.
>>   
> This is a topic that I would like to see discussed in the
> the IETF, at least in the form of asking whether we
> have requirements for new work. The new maintenance
> group that we are creating is not the right place for
> that discussion, but I do want to have a forum. Stay
> tuned.

I believe that a concerted v6 deployment effort (which is not
IETF's job) is likely to start and will lead to both practical
input on operational issues (for v6ops) and to possible
identification of gaps in the specifications (for 6man and, er,
ngtrans). So a way to bring such input into the IETF is
needed, but we shouldn't forget that the deployment effort
itself will be elsewhere.

     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 Jul 26 15:55: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 1IE9QS-0002kU-I2; Thu, 26 Jul 2007 15:55:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9QQ-0002kM-Cg
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:55:06 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE9QP-0006ee-Oy
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:55:06 -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 l6QJt3W2019409
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 26 Jul 2007 21:55:03 +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
	l6QJt2HW027310; Thu, 26 Jul 2007 21:55:02 +0200
Date: Thu, 26 Jul 2007 21:55:02 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Tim Enos <timbeck04@verizon.net>
In-Reply-To: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
Message-ID: <Pine.LNX.4.64.0707262149580.13685@chandra.student.uit.no>
References: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.62 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Brian Haberman <brian@innovationslab.net>,
	IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 26 Jul 2007, Tim Enos wrote:
<snip>
>>>>     o Complete work on Centrally Allocated Unique Local Addresses
>>> (ULA-C)
>>>
>>> Considering ULA as a core IPv6 protocol is a hard sell.
>>>
>> I personally am not considering ULA a core protocol.  However, the work
>> on ULA (whatever the outcome) needs a home.
>
> I agree that ULA-C "needs a home" but disagree the IPv6 Maintenance WG is it, given:
>
> * the first paragraph of the proposed charter:
>
> "The sole purpose of this group is in the maintenance of the core
> IPv6 protocol specifications and *not* in the development of new
> solutions or changes to the specifications.."
>
> && at least one of the group chairs doesn't consider it to be a core protocol,

It probably isnt a core protocol, it is a set of IP addresses out of the 
IPv6 address scope. I guess the right question is:

- who should in the future decide on usage of other sub-set of the IPv6 
address scope?


> && at least one of the group chairs doesn't see group consensus on ULA-C,
> && there are other group members who don't see group consensus on ULA-C,
> && we haven't heard from any group members who do see group consensus on ULA-C,

well I wouldn't claim there are any consensus right now but there are two 
draft out there and the merge between them has been ignored for a month... 
do people just wish the entire discussion to die away and ignore it? 
(sorry for the hard wordings of that sentence)


> && "Complete work" is meant to be predicated upon group consensus
>
> I'd say it should be removed from the charter.

why... it is a open discussion with two suggested draft as said above and 
it is moving in the direction of some sort of consensus.



-- 

------------------------------
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 Jul 26 15:58: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 1IE9Ti-0005dF-BJ; Thu, 26 Jul 2007 15:58:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IE9TY-0005Z6-OS
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:58:20 -0400
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE9TY-0006iv-Dm
	for ipv6@ietf.org; Thu, 26 Jul 2007 15:58:20 -0400
Received: from ([128.244.96.142])
	by piper.jhuapl.edu with ESMTP  id 5502121.36312562;
	Thu, 26 Jul 2007 15:57:59 -0400
Message-ID: <46A8FCC8.4080108@innovationslab.net>
Date: Thu, 26 Jul 2007 15:58:00 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <46A8E537.60504@innovationslab.net>
	<75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.com>
In-Reply-To: <75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
X-Mailman-Approved-At: Thu, 26 Jul 2007 15:58:28 -0400
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Chris,

Christopher Morrow wrote:
> On 7/26/07, Brian Haberman <brian@innovationslab.net> wrote:
> ...
>> The working group's work items are as follows:
>>
>>      o Shepherd completion of standardization of the RH0 Deprecation
>> document
> ...
>> All new work items not listed above require the approval of the working
>> group and IESG before they will be taken on by the working group.
>>
> 
> I didn't think there was consensus on the RH0 direction yet, was there?
> 

There was consensus to create an IPv6 WG document to address the issue
of the RH0 security hole.  The result of that consensus is what is
documented in this draft that recently went through an IPv6 WG last call.

For the history there, please see the mailing list message
http://www1.ietf.org/mail-archive/web/ipv6/current/msg07408.html

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 Thu Jul 26 16:36: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 1IEA3v-000152-9m; Thu, 26 Jul 2007 16:35:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEA3t-0000wn-Ta
	for ipv6@ietf.org; Thu, 26 Jul 2007 16:35:53 -0400
Received: from smtp157.iad.emailsrvr.com ([207.97.245.157])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEA3t-0007ZR-E4
	for ipv6@ietf.org; Thu, 26 Jul 2007 16:35:53 -0400
Received: by relay5.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 11700626B06; 
	Thu, 26 Jul 2007 16:35:53 -0400 (EDT)
In-Reply-To: <46A8FCC8.4080108@innovationslab.net>
References: <46A8E537.60504@innovationslab.net>
	<75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.com>
	<46A8FCC8.4080108@innovationslab.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5488BCE1-680A-46D3-9D63-9FC6E4102482@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 26 Jul 2007 15:35:50 -0500
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jul 26, 2007, at 2:58 PM, Brian Haberman wrote:

> Hi Chris,
>
> Christopher Morrow wrote:
>> On 7/26/07, Brian Haberman <brian@innovationslab.net> wrote:
>> ...
>>> The working group's work items are as follows:
>>>
>>>      o Shepherd completion of standardization of the RH0 Deprecation
>>> document
>> ...
>>> All new work items not listed above require the approval of the  
>>> working
>>> group and IESG before they will be taken on by the working group.
>>>
>>
>> I didn't think there was consensus on the RH0 direction yet, was  
>> there?
>>
>
> There was consensus to create an IPv6 WG document to address the issue
> of the RH0 security hole.  The result of that consensus is what is
> documented in this draft that recently went through an IPv6 WG last  
> call.
>
> For the history there, please see the mailing list message
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg07408.html
>
> Regards,
> Brian

It seemed as though a number of folks joined the discussion after the  
original consensus call, and that many of these individuals did not  
support deprecation.  Perhaps a new consensus call would be appropriate.

R,
Dow

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



From ipv6-bounces@ietf.org Thu Jul 26 17:08: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 1IEAZp-0005p2-1s; Thu, 26 Jul 2007 17:08:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEAZn-0005lF-5o
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:08:51 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEAZl-0000kO-NP
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:08:51 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.114]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 26 Jul 2007 22:08:49 +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, 26 Jul 2007 22:10:30 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0C47060@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <46A8E537.60504@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Closure of IPv6 WG and creation of IPv6 Maintenance WG
Thread-Index: AcfPsaDIzpqwSbeJTw+Ob9nmQRUhoAAFvGeQ
References: <46A8E537.60504@innovationslab.net>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 26 Jul 2007 21:08:49.0070 (UTC)
	FILETIME=[293EB4E0:01C7CFC9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: RE: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 sole purpose of this group is in the maintenance of the core
> IPv6 protocol specifications and *not* in the development of=20
> new solutions or changes to the specifications.  For example,=20
> the deployment of new transition tools is out of scope of=20
> this working group.
> Proposals for work beyond the scope of this working group=20
> should be sent to relevant ADs.

The language in this email is quite clear. Interestingly, it is missing
from the charter text. I see that there are two kinds of new work that
could come up, and the charter should make it clear which new work falls
within the charter, and should be submitted to the WG for approval, and
which new work should not be submitted to the WG, but to other ADs.

For instance if ULA-C fails to meet consensus and in a few months,
someone comes up with a ULA-W proposal, that does not involve protocol
changes and should go to the WG for approval. But if someone comes up
with a new routing proposal which separates locaters and identifiers,
that does involve protocol changes and should go to other ADs.

--Michael Dillon=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 Jul 26 17: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 1IEAtV-0007dh-1m; Thu, 26 Jul 2007 17:29:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEAtT-0007Wa-Fo
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:29:11 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEAtT-0008VW-4Q
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:29:11 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 61157198680;
	Fri, 27 Jul 2007 00:29:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id ACFBD19867D;
	Fri, 27 Jul 2007 00:29:08 +0300 (EEST)
Message-ID: <46A91224.2050303@piuha.net>
Date: Thu, 26 Jul 2007 16:29:08 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <46A8E537.60504@innovationslab.net> <46A8E69A.2070009@piuha.net>
	<46A8FA06.1070408@gmail.com>
In-Reply-To: <46A8FA06.1070408@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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.

Jari

Brian E Carpenter wrote:
> I believe that a concerted v6 deployment effort (which is not
> IETF's job) is likely to start and will lead to both practical
> input on operational issues (for v6ops) and to possible
> identification of gaps in the specifications (for 6man and, er,
> ngtrans). So a way to bring such input into the IETF is
> needed, but we shouldn't forget that the deployment effort
> itself will be elsewhere.
>
>     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 Jul 26 17:33: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 1IEAxD-0003KP-IF; Thu, 26 Jul 2007 17:33:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEAxB-0003KJ-IL
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:33:01 -0400
Received: from ug-out-1314.google.com ([66.249.92.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEAxB-00018S-7P
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:33:01 -0400
Received: by ug-out-1314.google.com with SMTP id u2so1879325uge
	for <ipv6@ietf.org>; Thu, 26 Jul 2007 14:33:00 -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=d55IZw6B7sIT61KHpJ6agB8a08Y+bGHU995UszfIVFI7fdgmcppFodedIHMUg5nZnNcgjeaFcd5oUfp/GeHtCj2uONwYGj6pBLZgtX5stQs165RZ/MdHFvYxzyhKJrNMsYGi3Ie1dpGqrMJohj6QXkEBUHoDly1HpAG4rjN8laY=
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=KKa1nTmhwyDxN8CdTZYT1yZ7YjMxQJYiOu6WXJj8A6KLas1V1W4R76z2BFB1a4pHiHrRsDhgrv+gb/V/GARcKSzmdU516QIYIL9toCpbaI1QIVwYFHrD9eDHj9h6wdl2kJwMVIqemXrm2Lw9KlplXzdY0FzK0ipHGjEb9us+xs8=
Received: by 10.86.79.19 with SMTP id c19mr1492799fgb.1185485580224;
	Thu, 26 Jul 2007 14:33:00 -0700 (PDT)
Received: from ?130.129.17.141? ( [130.129.17.141])
	by mx.google.com with ESMTPS id e9sm7155632muf.2007.07.26.14.32.57
	(version=SSLv3 cipher=RC4-MD5); Thu, 26 Jul 2007 14:32:59 -0700 (PDT)
Message-ID: <46A9130A.6080500@gmail.com>
Date: Thu, 26 Jul 2007 23:32:58 +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: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
	<Pine.LNX.4.64.0707262149580.13685@chandra.student.uit.no>
In-Reply-To: <Pine.LNX.4.64.0707262149580.13685@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: 9466e0365fc95844abaf7c3f15a05c7d
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	IPv6 WG Mailing List <ipv6@ietf.org>,
	Brian Haberman <brian@innovationslab.net>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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-07-26 21:55, Roger Jorgensen wrote:
> On Thu, 26 Jul 2007, Tim Enos wrote:

...
>> "The sole purpose of this group is in the maintenance of the core
>> IPv6 protocol specifications and *not* in the development of new
>> solutions or changes to the specifications.."
>>
>> && at least one of the group chairs doesn't consider it to be a core 
>> protocol,
> 
> It probably isnt a core protocol, it is a set of IP addresses out of the 
> IPv6 address scope. I guess the right question is:
> 
> - who should in the future decide on usage of other sub-set of the IPv6 
> address scope?

6man, and tweak the charter to cover address architecture maintenance,
IMHO.
...

>> I'd say it should be removed from the charter.
> 
> why... it is a open discussion with two suggested draft as said above 
> and it is moving in the direction of some sort of consensus.

Exactly.

    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 Jul 26 17:43: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 1IEB6Q-0003Wa-HP; Thu, 26 Jul 2007 17:42:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEB6P-0003WU-1s
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:42:33 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEB6N-0001IT-Kh
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:42:33 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 66257198680;
	Fri, 27 Jul 2007 00:42:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 08FAE1985FB;
	Fri, 27 Jul 2007 00:42:28 +0300 (EEST)
Message-ID: <46A91544.9080305@piuha.net>
Date: Thu, 26 Jul 2007 16:42:28 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>,  itojun@itojun.org
References: <46A8E537.60504@innovationslab.net>
	<75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.com>
In-Reply-To: <75cb24520707261228u36ddf8d6t50099405dcc9fd42@mail.gmail.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: de4f315c9369b71d7dd5909b42224370
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Chris, Itojun,

>
> I didn't think there was consensus on the RH0 direction yet, was there?
> 	i'm not too sure if ULA-C has wg consenssu to be the way forward.

The charter lists existing work that we are taking over
from IPv6 WG. That the charter allows working on topic
X does not in any way imply that the current documents
or direction has consensus behind them; that has to
be independently established.

That is, listing these items in the charter allows us to
continue the discussion.

Jari


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



From ipv6-bounces@ietf.org Thu Jul 26 17:51: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 1IEBFR-0002k4-HK; Thu, 26 Jul 2007 17:51:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBFQ-0002eC-8f
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:51:52 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEBFO-0001SD-TN
	for ipv6@ietf.org; Thu, 26 Jul 2007 17:51:52 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 4681D198680;
	Fri, 27 Jul 2007 00:51:50 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 69A6B1985FB;
	Fri, 27 Jul 2007 00:51:49 +0300 (EEST)
Message-ID: <46A91774.7070204@piuha.net>
Date: Thu, 26 Jul 2007 16:51:48 -0500
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Tim Enos <timbeck04@verizon.net>
References: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
In-Reply-To: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: IPv6 WG Mailing List <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Tim,


> I agree that ULA-C "needs a home" but disagree the IPv6 Maintenance WG is it, given:
>
> * the first paragraph of the proposed charter:
>
> "The sole purpose of this group is in the maintenance of the core
> IPv6 protocol specifications and *not* in the development of new
> solutions or changes to the specifications.."
>
> && at least one of the group chairs doesn't consider it to be a core protocol,
>
> && at least one of the group chairs doesn't see group consensus on ULA-C,
>
> && there are other group members who don't see group consensus on ULA-C,
>
> && we haven't heard from any group members who do see group consensus on ULA-C,
>
> && "Complete work" is meant to be predicated upon group consensus
>
> I'd say it should be removed from the charter.
>   

What we really want to achieve is to have a forum where we
can talk about maintenance issues of the IPv6 protocol set,
but we also need to carry over the work that remains from
IPv6 WG. I am not creating another working group to
just talk about ULA, so we have a practical question of
where we will finish the work. (And by "finish" I might
mean that we decide to abandon the work at the end --
but NOT before a discussion.)

Please be assured that we will not move the ULA work forward
if the current non-consensus situation does not change.

Brian Carpenter wrote:
> 6man, and tweak the charter to cover address architecture maintenance, 

This would be my take too.

Jari


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



From ipv6-bounces@ietf.org Thu Jul 26 18: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 1IEBmc-0000de-OQ; Thu, 26 Jul 2007 18:26:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEBmb-0000dK-Dd
	for ipv6@ietf.org; Thu, 26 Jul 2007 18:26:09 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEBma-00019m-Ot
	for ipv6@ietf.org; Thu, 26 Jul 2007 18:26:08 -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 l6QMQ7h5017781
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 26 Jul 2007 15:26:07 -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
	l6QMQ6e4019279; Thu, 26 Jul 2007 15:26:06 -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
	l6QMQ6W1019238; Thu, 26 Jul 2007 15:26: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); 
	Thu, 26 Jul 2007 15:26: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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 26 Jul 2007 15:25:48 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED956@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <200707262211.55083.rdenis@simphalempin.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Closure of IPv6 WG and creation of IPv6 Maintenance WG
Thread-Index: AcfPuROyoanSsN3sTiuleFEbPkOxVwAGrAyw
References: <46A8E537.60504@innovationslab.net><200707262133.22568.rdenis@simphalempin.com><46A8EF8D.2000805@innovationslab.net>
	<200707262211.55083.rdenis@simphalempin.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: =?iso-8859-1?Q?R=E9mi_Denis-Courmont?= <rdenis@simphalempin.com>,
	"Brian Haberman" <brian@innovationslab.net>
X-OriginalArrivalTime: 26 Jul 2007 22:26:06.0001 (UTC)
	FILETIME=[F5123A10:01C7CFD3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: RE: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > Do you have an example of such a specification you are=20
> worried about?
>=20
> Teredo's one that showed up at v6ops meeting.

I think ISATAP (RFC4214) was mentioned on the v6ops list, too?

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 Jul 27 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 1IEJEl-0005xb-PP; Fri, 27 Jul 2007 02:23:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEJEj-0005xT-M4
	for ipv6@ietf.org; Fri, 27 Jul 2007 02:23:41 -0400
Received: from mux2.uit.no ([129.242.5.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IEJEh-0002b6-1P
	for ipv6@ietf.org; Fri, 27 Jul 2007 02:23:39 -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 l6R6NUEt081739
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 27 Jul 2007 08:23: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
	l6R6NURD009034; Fri, 27 Jul 2007 08:23:30 +0200
Date: Fri, 27 Jul 2007 08:23:29 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <46A91774.7070204@piuha.net>
Message-ID: <Pine.LNX.4.64.0707270820430.13685@chandra.student.uit.no>
References: <9399173.5073471185478509315.JavaMail.root@vms246.mailsrvcs.net>
	<46A91774.7070204@piuha.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.62 on 129.242.5.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: IPv6 WG Mailing List <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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, 26 Jul 2007, Jari Arkko wrote:
> Brian Carpenter wrote:
>> 6man, and tweak the charter to cover address architecture maintenance,
>
> This would be my take too.

so you will issue a new version of the charter with some of the other 
changes people have mention?


-- 

------------------------------
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 Jul 27 05:37: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 1IEMFT-0007qY-Gc; Fri, 27 Jul 2007 05:36:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEMFQ-0007qB-Fo
	for ipv6@ietf.org; Fri, 27 Jul 2007 05:36:37 -0400
Received: from web27005.mail.ukl.yahoo.com ([217.146.177.5])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IEMFP-0006t0-TB
	for ipv6@ietf.org; Fri, 27 Jul 2007 05:36:36 -0400
Received: (qmail 1114 invoked by uid 60001); 27 Jul 2007 09:36:35 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=z5T+TEee4nIuQdY+o5GWT+mAnnk+RIjGKLx3gavUwFVmKysToxvGFrx8HJA7vaamsld0CvwBQ0FX7N892LLw8vlHm9s1PPiOHCs5qwPtOuzL4s0evEfnRhdmFvG9q5S8qesN4jt5VtT6ujne/Ilw0XA3i2ktVQ9XwkrRaMIFu6k=;
X-YMail-OSG: Hu8nG_cVM1m_F6ZLETU8cE2m14Izo4ZS.Uga19S3dFYHBkbBKkmNkk2w3gJy4MNFV4JG7LHhAhcoAlXzQL0PeCfVZoXTPrL9NVXsAMBCbmUbf8CMkfSM2bh7RR8-
Received: from [196.217.52.120] by web27005.mail.ukl.yahoo.com via HTTP;
	Fri, 27 Jul 2007 11:36:34 CEST
Date: Fri, 27 Jul 2007 11:36:34 +0200 (CEST)
From: Nabil Benamar <nabil_benamar@yahoo.fr>
To: ipv6@ietf.org
MIME-Version: 1.0
Message-ID: <290283.1063.qm@web27005.mail.ukl.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: my email
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-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="===============1035897281=="
Errors-To: ipv6-bounces@ietf.org

--===============1035897281==
Content-Type: multipart/alternative; boundary="0-1674685223-1185528994=:1063"
Content-Transfer-Encoding: 8bit

--0-1674685223-1185528994=:1063
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit




************************************************

Pr. Nabil Benamar
Département de Mathématiques et d'Informatique
Faculté Polydisciplinaire de Safi
Université Cadi Ayyad

************************************************
       
---------------------------------
 Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail 
--0-1674685223-1185528994=:1063
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<br><BR><BR>************************************************<br><br>Pr. Nabil Benamar<br>Département de Mathématiques et d'Informatique<br>Faculté Polydisciplinaire de Safi<br>Université Cadi Ayyad<br><br>************************************************<p>&#32;



      <hr size="1"> 
Ne gardez plus qu'une seule adresse mail ! <a href="http://www.trueswitch.com/yahoo-fr/">Copiez vos mails</a> vers Yahoo! Mail 
--0-1674685223-1185528994=:1063--


--===============1035897281==
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
--------------------------------------------------------------------

--===============1035897281==--




From ipv6-bounces@ietf.org Fri Jul 27 11:20: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 1IERb8-0006yr-HE; Fri, 27 Jul 2007 11:19:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IERb7-0006ym-Mc
	for ipv6@ietf.org; Fri, 27 Jul 2007 11:19:21 -0400
Received: from vms044pub.verizon.net ([206.46.252.44])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IERb7-0006uh-8s
	for ipv6@ietf.org; Fri, 27 Jul 2007 11:19:21 -0400
Received: from vms125.mailsrvcs.net ([192.168.1.2])
	by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JLU00KRDFVVVR60@vms044.mailsrvcs.net> for
	ipv6@ietf.org; Fri, 27 Jul 2007 10:19:07 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms125.mailsrvcs.net (Verizon Webmail) with HTTP; Fri,
	27 Jul 2007 10:19:07 -0500 (CDT)
Date: Fri, 27 Jul 2007 10:19:07 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: Jari Arkko <jari.arkko@piuha.net>
Message-id: <24770801.11393111185549547844.JavaMail.root@vms125.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: IPv6 WG Mailing List <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?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 Jari,

>Tim,
>
>
>> I agree that ULA-C "needs a home" but disagree the IPv6 Maintenance WG is it, given:
>>
>> * the first paragraph of the proposed charter:
>>
>> "The sole purpose of this group is in the maintenance of the core
>> IPv6 protocol specifications and *not* in the development of new
>> solutions or changes to the specifications.."
>>
>> && at least one of the group chairs doesn't consider it to be a core protocol,
>>
>> && at least one of the group chairs doesn't see group consensus on ULA-C,
>>
>> && there are other group members who don't see group consensus on ULA-C,
>>
>> && we haven't heard from any group members who do see group consensus on ULA-C,
>>
>> && "Complete work" is meant to be predicated upon group consensus
>>
>> I'd say it should be removed from the charter.
>>   
>
>What we really want to achieve is to have a forum where we
>can talk about maintenance issues of the IPv6 protocol set,

That is both the explicit and implicit curriculum here, I understand.

>but we also need to carry over the work that remains from
>IPv6 WG.

Yes, I agree in principle, so would say the language of the charter needs to be modified. The "_sole_ purpose of this group" would then _not_ be "maintenance of the _core_ IPv6 protocol specifications.

I am not creating another working group to
>just talk about ULA, so we have a practical question of
>where we will finish the work.

Exactly.

 (And by "finish" I might
>mean that we decide to abandon the work at the end --
>but NOT before a discussion.)
>
>Please be assured that we will not move the ULA work forward
>if the current non-consensus situation does not change.

Thank you.

>
>Brian Carpenter wrote:
>> 6man, and tweak the charter to cover address architecture maintenance, 
>
>This would be my take too.
>
>Jari

Tim Enos
Rom 8:28


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



From ipv6-bounces@ietf.org Sat Jul 28 20:01: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 1IEwCd-00080k-4E; Sat, 28 Jul 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 1IEwCb-00080e-V1
	for ipv6@ietf.org; Sat, 28 Jul 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 1IEwCb-00008u-G9
	for ipv6@ietf.org; Sat, 28 Jul 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id D221628463
	for <ipv6@ietf.org>; Sun, 29 Jul 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 29 Jul 2007 00:00:04 +0000
Message-Id: <20070729000004.D221628463@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
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
--------+------+--------+----------+------------------------
 11.11% |    6 | 17.68% |    55630 | shemant@cisco.com
  9.26% |    5 | 13.68% |    43030 | varada@txc.com
  9.26% |    5 | 13.66% |    42970 | james.d.carlson@sun.com
 11.11% |    6 |  8.52% |    26820 | brian@innovationslab.net
  7.41% |    4 |  5.32% |    16737 | jari.arkko@piuha.net
  5.56% |    3 |  4.90% |    15410 | rogerj@jorgensen.no
  5.56% |    3 |  3.73% |    11735 | rdenis@simphalempin.com
  3.70% |    2 |  3.41% |    10726 | brian.e.carpenter@gmail.com
  3.70% |    2 |  3.29% |    10340 | timbeck04@verizon.net
  3.70% |    2 |  3.18% |    10008 | fred.l.templin@boeing.com
  3.70% |    2 |  2.93% |     9229 | michael.dillon@bt.com
  3.70% |    2 |  2.84% |     8945 | suresh.krishnan@ericsson.com
  3.70% |    2 |  2.58% |     8106 | itojun@itojun.org
  1.85% |    1 |  1.71% |     5375 | nabil_benamar@yahoo.fr
  1.85% |    1 |  1.70% |     5337 | umang.a.patel@verizon.com
  1.85% |    1 |  1.49% |     4682 | christopher.morrow@gmail.com
  1.85% |    1 |  1.46% |     4602 | iljitsch@muada.com
  1.85% |    1 |  1.44% |     4538 | bob.hinden@nokia.com
  1.85% |    1 |  1.43% |     4513 | dow.street@linquest.com
  1.85% |    1 |  1.33% |     4197 | sra+ipng@hactrn.net
  1.85% |    1 |  1.31% |     4112 | alain_durand@cable.comcast.com
  1.85% |    1 |  1.23% |     3860 | paul@vix.com
  1.85% |    1 |  1.18% |     3715 | george+ipng@m5p.com
--------+------+--------+----------+------------------------
100.00% |   54 |100.00% |   314617 | 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
--------------------------------------------------------------------



