Re: [homenet] homenet-prefix-assignment update - behaviour at one ISP
Ted Lemon <mellon@fugue.com> Wed, 08 October 2014 12:51 UTC
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C841A036D for <homenet@ietfa.amsl.com>; Wed, 8 Oct 2014 05:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level:
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oe9E8S7QnTaX for <homenet@ietfa.amsl.com>; Wed, 8 Oct 2014 05:51:37 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B9F0B1A0366 for <homenet@ietf.org>; Wed, 8 Oct 2014 05:51:37 -0700 (PDT)
Received: from [10.0.10.40] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id BFC1D2380840; Wed, 8 Oct 2014 08:51:36 -0400 (EDT)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <54352E33.1030505@gmail.com>
Date: Wed, 08 Oct 2014 08:51:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <02E293C2-F574-4687-BBE7-EEA4524BA16E@fugue.com>
References: <A0C73AEC-6D0F-498B-9BDD-D6AF91202CCB@darou.fr> <54350D62.5050706@gmail.com> <048F40EB-A1D5-4D70-986B-9DDE55FF7C22@darou.fr> <543526D9.2020107@gmail.com> <FD386567-2DFE-4484-8F5A-794CF9C438F0@darou.fr> <54352E33.1030505@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/_q7O0NwXkypIilVxPVEaucrzJ-Q
Cc: homenet@ietf.org, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] homenet-prefix-assignment update - behaviour at one ISP
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Oct 2014 12:51:41 -0000
You guys are debating points that are long-since decided. On Oct 8, 2014, at 8:29 AM, Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote: > Le 08/10/2014 14:15, Pierre Pfister a écrit : >> >> Le 8 oct. 2014 à 13:58, Alexandru Petrescu >> <alexandru.petrescu@gmail.com> a écrit : >> >>> Hi Pierre, >>> >>> Le 08/10/2014 13:28, Pierre Pfister a écrit : >>>> Hi Alex, >>>> >>>> Reply is inlined, >>>> >>>> Le 8 oct. 2014 à 12:09, Alexandru Petrescu >>>> <alexandru.petrescu@gmail.com> a écrit : >>>> >>>>> Hi Pierre, >>>>> >>>>> Thanks for the draft update. Now I have two questions: >>>>> >>>>>> prefixes of size 64 are RECOMMENDED. >>>>> >>>>> Why is this length recommended? I think it may be because of >>>>> Ethernet? >>>> >>>> I’m not a big fan of putting 64s everywhere neither. And I >>>> strongly disagree with mandating 64 bit long prefixes. The prefix >>>> algorithm itself is agnostic on this side. >>>> >>>> Nevertheless, some parts of this document are home-network >>>> specific. Not even talking about crappy implementations, home >>>> network links should support SLAAC whenever possible. Which is >>>> the reason why using 64bit long prefixes is RECOMMENDED. >>> >>> Ah, I see. I doubt though SLAAC is 64. Maybe Ethernet is. >> >> SLAAC relies on ‘interface identifier’. Ethernet uses the EUI-64. I >> have no knowledge of other methods of generating an interface >> identifier. >> >> The why64 draft is interesting (and sad) on that front. >> >>> >>>> But smaller prefixes are better than *no prefix at all*. When >>>> there are not enough prefixes available (e.g. the ISP provides a >>>> single 64 while we have multiple links), smaller prefixes can be >>>> used (80 for instance). Which means dhcpv6 must be used. Our >>>> implementation supports it, and it works with my laptop. >>> >>> Ok. >>> >>>> But again, that should be avoided whenever possible. And ISPs >>>> MUST provided enough prefixes (IMO). >>> >>> I agree with you. >>> >>> Last time I checked Free ISP seems to provide 8 /64 prefixes to my >>> homenet: 2001:db8:0:ce10::/64 2001:db8:0:ce11::/64 ... >>> 2001:db8:0:ce17::/64 I dont think these could be aggregated into a >>> single shorter prefix, or my math is missing. >> >> That is 2001:db8:0:ce10::/61 > > Right, sorry, my math was missing. So I suppose Free ISP delegates a > single /61 to me then, not several /64s. This is a local prefix > division performed in that router. I do not necessarily agree with it, > as I could have divided it differently, or I could have announced the /61 in RA in the first link of the homenet, etc.
- [homenet] homenet-prefix-assignment update Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] on prefix comparison Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Pierre Pfister
- Re: [homenet] on prefix comparison Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Mikael Abrahamsson
- Re: [homenet] homenet-prefix-assignment update - … Ole Troan
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Ted Lemon
- Re: [homenet] homenet-prefix-assignment update - … Mikael Abrahamsson
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Mikael Abrahamsson
- Re: [homenet] homenet-prefix-assignment update - … Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Tim Chown
- Re: [homenet] homenet-prefix-assignment update - … Mark Townsley
- Re: [homenet] homenet-prefix-assignment update - … Brian E Carpenter
- Re: [homenet] homenet-prefix-assignment update - … Mark Townsley
- Re: [homenet] homenet-prefix-assignment update - … Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Ole Troan
- Re: [homenet] homenet-prefix-assignment update - … Pierre Pfister
- Re: [homenet] homenet-prefix-assignment update - … Brian E Carpenter
- Re: [homenet] homenet-prefix-assignment update - … Tim Chown
- Re: [homenet] homenet-prefix-assignment update - … Alexandru Petrescu
- Re: [homenet] homenet-prefix-assignment update - … Townsley.net
- Re: [homenet] homenet-prefix-assignment update - … Tim Chown
- Re: [homenet] homenet-prefix-assignment update - … Townsley.net
- Re: [homenet] on prefix comparison Alexandru Petrescu