Re: [homenet] homenet-prefix-assignment update - prefix length 64 and on prefix comparison

Alexandru Petrescu <alexandru.petrescu@gmail.com> Thu, 09 October 2014 09:29 UTC

Return-Path: <alexandru.petrescu@gmail.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 F3E531ACD07 for <homenet@ietfa.amsl.com>; Thu, 9 Oct 2014 02:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.983
X-Spam-Level:
X-Spam-Status: No, score=-3.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 7wrCUAvB_3nA for <homenet@ietfa.amsl.com>; Thu, 9 Oct 2014 02:29:16 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F3EA1ACD04 for <homenet@ietf.org>; Thu, 9 Oct 2014 02:29:16 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s999T9xA024327; Thu, 9 Oct 2014 11:29:09 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8F0C9203E2E; Thu, 9 Oct 2014 11:30:15 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 79635203DF1; Thu, 9 Oct 2014 11:30:15 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s999T88g014344; Thu, 9 Oct 2014 11:29:09 +0200
Message-ID: <54365564.5090703@gmail.com>
Date: Thu, 09 Oct 2014 11:29:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>, Ole Troan <otroan@employees.org>
References: <A0C73AEC-6D0F-498B-9BDD-D6AF91202CCB@darou.fr> <54350D62.5050706@gmail.com> <048F40EB-A1D5-4D70-986B-9DDE55FF7C22@darou.fr> <FAFE72E2-04EC-4B27-BE1F-6E2F9F7F7A1C@employees.org> <37213B35-CAE1-4AF7-B94D-2B5EAD1C4A39@darou.fr> <5308B561-200A-455C-B2E9-4B4824ED2A1D@ecs.soton.ac.uk> <EMEW3|2f5d8f14bb6cf818659db375e4a75ba0q97FLf03tjc|ecs.soton.ac.uk|5308B561-200A-455C-B2E9-4B4824ED2A1D@ecs.soton.ac.uk> <5435D845.9030108@gmail.com> <AE46801C-D3EA-436A-9894-CCF9B9E46A5D@townsley.net> <A50A4BEF-B267-4BFF-8DDE-297D03A16DBC@darou.fr>
In-Reply-To: <A50A4BEF-B267-4BFF-8DDE-297D03A16DBC@darou.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/JhkYVtUT6rcYMqPV2cB5My5XuQg
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "homenet@ietf.org" <homenet@ietf.org>, Mark Townsley <mark@townsley.net>
Subject: Re: [homenet] homenet-prefix-assignment update - prefix length 64 and on prefix comparison
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: Thu, 09 Oct 2014 09:29:19 -0000

Thanks for updating.

Le 09/10/2014 11:26, Pierre Pfister a écrit :
> Hello,
>
> I’m proposing this change then.
>
> 1. In case the provided prefix is 64, the default consist in assigning
> prefixes of length 64 first.
> 2. I’m adding a reference to 6man-why64.
>
> When the algorithm decides to make a new assignment, it first needs
>     to specify the desired size of the assigned prefix.  Although this
>     algorithm intends to remain generic, it was observed in
>     [I-D.ietf-6man-why64] that hosts may malfunction when the prefix
>     length is not 64.  Therefore, prefixes of length 64 are RECOMMENDED.

With this text above, operators will be encouraged to read and give /64 
to end user sites.

Alex

>     The following table MAY be used as default values, where X is the
>     length of the delegated prefix.
>
>     If X <= 64:  Prefix length = 64
>
> ….
>
> Processes proposed in the appendix are optional.
> Our implementation supports some part of it, and it works fine in our
> test-cases.
> I’d rather have a /80 than no connectivity at all (And it just works.).
> IMO, why64 is way too pessimistic on the current implementation state
> and even more when it comes to the progress implementations will do in
> the coming years.
>
> And we either do that or let people do NAT66. ;)
>
>
> Is it OK for you Ole ?
>
> Cheers,
>
> - Pierre
>
> Le 9 oct. 2014 à 07:25, Mark Townsley <mark@townsley.net
> <mailto:mark@townsley.net>> a écrit :
>
>>
>>
>>> On Oct 9, 2014, at 2:35 AM, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>>
>>>> On 09/10/2014 03:21, Tim Chown wrote:
>>>>> On 8 Oct 2014, at 14:14, Pierre Pfister <pierre.pfister@darou.fr
>>>>> <mailto:pierre.pfister@darou.fr>> wrote:
>>>>> Why should we mandate homenet implementations to *brake* in
>>>>> situations where they could work fine ? Why should we voluntarily
>>>>> prevent a link from being configured if we actually can configure it ?
>>>>>
>>>>> If MUSTs are the solution, then I would rather see a ‘ISP MUST
>>>>> provide a /56 to customers’ than ‘Homenet MUST brake when the
>>>>> provided prefix is not big enough’.
>>>>
>>>> But this is what the homenet arch text says in Section 3.4.1:
>>>> http://tools.ietf.org/html/draft-ietf-homenet-arch-17#section-3.4.1
>>>>
>>>> i.e. don’t go longer than /64, and ISPs should provide enough prefixes.
>>>>
>>>> The why64 text is very relevant here.
>>>
>>> And could be added as a reference. It's already in IESG Evaluation
>>> (with one open issue that was just flagged).
>>
>> Informative reference, as we don't want to create a downref over this.
>>
>>>
>>> Certainly the mechanisms should support any prefix length,
>>
>> I agree.
>>
>> - Mark
>>
>>> but
>>> the reality remains that only /64 subnets work properly in all
>>> circumstances today.
>>>
>>>   Brian
>>>
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org <mailto:homenet@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/homenet
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org <mailto:homenet@ietf.org>
>> https://www.ietf.org/mailman/listinfo/homenet
>