Re: IPv6 address assignment for strictly point-to-point links and Device Loopbacks

Usman Latif <osmankh@yahoo.com> Sat, 22 September 2012 13:37 UTC

Return-Path: <osmankh@yahoo.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A54321F865E for <ipv6@ietfa.amsl.com>; Sat, 22 Sep 2012 06:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level:
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kpGuY3-LH2v for <ipv6@ietfa.amsl.com>; Sat, 22 Sep 2012 06:37:45 -0700 (PDT)
Received: from nm32-vm0.bullet.mail.ne1.yahoo.com (nm32-vm0.bullet.mail.ne1.yahoo.com [98.138.229.48]) by ietfa.amsl.com (Postfix) with SMTP id 1814721F8624 for <ipv6@ietf.org>; Sat, 22 Sep 2012 06:37:44 -0700 (PDT)
Received: from [98.138.90.57] by nm32.bullet.mail.ne1.yahoo.com with NNFMP; 22 Sep 2012 13:37:34 -0000
Received: from [98.138.88.236] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 22 Sep 2012 13:37:34 -0000
Received: from [127.0.0.1] by omp1036.mail.ne1.yahoo.com with NNFMP; 22 Sep 2012 13:37:34 -0000
X-Yahoo-Newman-Id: 80908.71159.bm@omp1036.mail.ne1.yahoo.com
Received: (qmail 57621 invoked from network); 22 Sep 2012 13:37:33 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:In-Reply-To:Mime-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=haU5o4kw2v/71WJ9X0pZPFn7b1Tgn+ThOQqJA37+NLDs9HFtXrELu3u4Md38DB7nIYoKsO3NVSFsr/FSWqV+eLI1CGjjXU6Yk6reYIFhVwf3kozRB9E7kCsUavQpriykfDl/6KlGhqzP8Nbn51DkhrPBIR3JSnqY5B3oyi6nxyc= ;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1348321053; bh=s8/5gByMPYxBjKsc/vSq7WAWhcfR+7byLizq16K6E3U=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:In-Reply-To:Mime-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=I7rKOYaHjsbzhRDo+p7UG/xz/M/eQNotnJxn2iBn451ohLxvL9Be+bSJmhYir/6ML/9KdvklhFdsoN4dFwGtRHnQZy/YoZmgtxsi4KDmZCCe8Zh+/7I89cENHUc/nYqOvk4pQTpCepCkaZW6/tZFoj2ep7KHHvN+gQtetOHHl1M=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: I1IEb2gVM1mqkuNbcJtkIpMm2aIkV0fMKmVFPzXlyZTwiW5 Mpu6rP5l4WHKMCMIRQdskzuWzQIE5IukWBZBk28ilAVMPitMHmpHNuQ61jx5 jt1CpJYoeS_Fd2JcsEOVoRFTAq0qRA5IU..O9I9Ii6oQq3osIHvUewEk3Qkb 9CVMDzsnmL1Z4k_rU85fJwj8fMI6wu9JS42C7k1xTN5PNTqGGy7dytYFeGTm WEUzUh9G9fBCeYLz8ovlb9.UeulrtoAiQwYedGgzU1sszWe3b9fqwMurXTwa lL8IwF2QjmnrS2MTMRZiViLbQTnHHJNGrmBRKut.tm.lGDpGv4mP5AKhsIx9 GOHAmohSdw0HBs0Xfx_Wtc2jSK7elHQzRr79j4I5B_kqEMoQmM8ArvwxSA.2 Djy3PKohlZbn0t.ulyAgFWdCB_hM2y5GDPe_NGifE32n.S9T3F3AWQVPr0b2 kYKcf
X-Yahoo-SMTP: RUL5CFuswBD02LFE5KfPCwZifSs-
Received: from [192.168.1.66] (osmankh@27.32.72.22 with xymcookie) by smtp104-mob.biz.mail.ne1.yahoo.com with SMTP; 22 Sep 2012 06:37:32 -0700 PDT
References: <1348211033.52674.YahooMailClassic@web126005.mail.ne1.yahoo.com> <CALOgxGZ6QLhuoVoqpt+R6paLThEs1zBHBgYzVXuvOqWSdrD9ZA@mail.gmail.com> <0BB03569-6F5F-43AC-9012-C82C85A43C00@yahoo.com> <2671C6CDFBB59E47B64C10B3E0BD59235F961497@PRVPEXVS15.corp.twcable.com> <A882F196-C47E-4AF0-962B-7DE9CD15584A@yahoo.com> <505CF2DC.3050401@gmail.com> <984B69E6-CBB4-4CD2-B624-D2F5B98E73B2@yahoo.com>
In-Reply-To: <984B69E6-CBB4-4CD2-B624-D2F5B98E73B2@yahoo.com>
Mime-Version: 1.0 (1.0)
Content-Type: multipart/alternative; boundary=Apple-Mail-C72C504F-AC61-4CBE-BE56-CFCE825EBB34
Content-Transfer-Encoding: 7bit
Message-Id: <CCDB24C3-FFE0-43D5-AF42-83FA8F1CA292@yahoo.com>
X-Mailer: iPhone Mail (9B206)
From: Usman Latif <osmankh@yahoo.com>
Subject: Re: IPv6 address assignment for strictly point-to-point links and Device Loopbacks
Date: Sat, 22 Sep 2012 23:37:29 +1000
To: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 13:37:46 -0000

Forgot to include IPv6 group email in my last email (below)
Further to that, RFC 6164 states in the same statement that:

"When assigning and using any /127 prefixes, the following considerations 
apply. Some addresses have special meanings, in particular addresses 
corresponding to reserved anycast addresses. When assigning prefixes 
(and addresses) to links, care should be taken to ensure that addresses 
reserved for such purposes aren't inadvertently assigned and used as 
unicast addresses. Otherwise, nodes may receive packets that they are 
not intended to receive. Specifically, assuming that a number of point-to-point 
links will be numbered out of a single /64 prefix: 
 (a) Addresses with all zeros in the rightmost 64 bits SHOULD NOT be assigned 
as unicast addresses, to avoid colliding with the Subnet-Router anycast address 
(b) Addresses in which the rightmost 64 bits are assigned the highest 128 values 
(i.e., ffff:ffff:ffff:ff7f to ffff:ffff:ffff: ffff) SHOULD NOT be used as unicast addresses, 
to avoid colliding with reserved subnet anycast addresses"

One question that comes up here is that why did RFC 6164 exclude
additional recommendations that were stated in RFC 5375 which stated:

"it is recommended to take the 'u' and 'g' bits into consideration and to make sure that there is no overlap with any of the following well-known addresses:
   o  Subnet Router Anycast Address
   o  Reserved Subnet Anycast Address
   o  Addresses used by Embedded-RP
   o  ISATAP Addresses"

So should one only care about excluding reserved addresses as per RFC 6164 or should we also care about reserving addresses as per RFC 5375?

5375 seems to have more special addresses covered and is also a hint that in the hindsight there could be more special addresses in future using bits in lower 64-bit portion of v6 address(?)

I wonder if it's possible to leave portions of lower 64 bits in v6 address for special purposes (both EUI-64 and non EUI-64) so that we get best of both worlds i.e. leave room open for future development and assignment of special addresses using portions in lower 64 bits reserved for this purpose and at the same time allowing users to tap into the lower 64 bit address space for general address assignment purposes using portions that are not reserved for this purposes...

Regards,
Usman

Sent from my iPhone

On 22/09/2012, at 12:35 PM, Usman Latif <osmankh@yahoo.com> wrote:

> Thanks Brian, your email clears a lot of ambiguity.
> So I presume it's safe to use /127s on different p2p links from the same /64 subnet. (as per 6164)
> This pretty much means that the second statement in my first email would be the final outcome - i.e.
> 
> - For IPv6 implementation on strictly p2p (inter-router links) and for device Loopbacks, we can use /127 and /128 respectively and are NOT reuqired to reserve the whole corresponding /64 for each of the p2p links (and loopbacks) i.e. for example multiple p2p links can be assigned /127 from the same /64 - this has implication that any future implementation of protocol/stack needs to be careful not to "assume" and reserve some or all of the lower-64 bits in IPv6 address for its implementation.
> 
> Pls note that there is still a mindset out there (call it being apprehensive or being overly cautious) - after speaking with peers in the telco carrier space, they are still assigning /127s and reserving whole /64s for each p2p link separately - this was the basis of my original discussion that we need to "break this myth and be clear and conclusive that operators/carriers etc or for that matter whoever is implementing v6 addressing on p2p links or loopbacks is not required to reserve a whole /64 for each of them separately and its completely a matter of choice whether they choose to assign /127 from the same /64 or keep separate /64 for each instance of p2p link or loopbacks etc"
> 
> Regards,
> Usman
> 
> Sent from my iPhone
> 
> On 22/09/2012, at 9:06 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 21/09/2012 22:35, Usman Latif wrote:
>>> Thanks Wes for the feedback.
>> 
>> ...
>>>>>> Without this stated clearly there is likely to be some instances where readers interpret it the wrong way and end up assigning multiple p2p links with /127 subnets from a single given /64 and end up having to re-address their network in future when/if future standards use lower order 64 bits for special purposes.
>>>> [WEG] Given the fact that there is a standard that documents the use of a /127 for P2P links (6164), 
>> 
>> Wes, I think that statement is even a bit weak, since 6164 actually says:
>> 
>> "assuming that a number of point-to-point links will be numbered out of a single /64 prefix:"
>> 
>> so it is very clear: it is allowed by the standard to share a /64 among
>> however many pt2pt links the operator cares to. This is *not* a wrong
>> interpretation.
>> 
>> As you say, any future work will need to take account of this.
>> 
>> Brian
>