Re: [v6ops] Discussion of draft-ietf-v6ops-ula-usage-recommendations

Mark Smith <markzzzsmith@gmail.com> Wed, 22 July 2015 01:47 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE1C1A8972 for <v6ops@ietfa.amsl.com>; Tue, 21 Jul 2015 18:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level:
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, GB_I_LETTER=-2, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, 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 t8Dw0_OS2sNU for <v6ops@ietfa.amsl.com>; Tue, 21 Jul 2015 18:47:11 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE1A1A8967 for <v6ops@ietf.org>; Tue, 21 Jul 2015 18:47:11 -0700 (PDT)
Received: by igbij6 with SMTP id ij6so124900125igb.1 for <v6ops@ietf.org>; Tue, 21 Jul 2015 18:47:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=UJNGD1SmiB2SJYZatDvixHqadcjDRH3gvhT3oENQghA=; b=ZHw0z36cf5/rzKrvoY8SzDrlR7lQOlcZ7RVsgIDL+6Uh4cyGignaVjkW0gLykYwhiI LFbQ98ocOBHcxuEkO3qmVDaYd5hya2zMqJW7EQqPIBXc+1acw/IUVyTE6DmK5Rn0Dent 4AFQf3awchhIAVgSDx93/mHsYBFRuzuOqGtS1pS7AcJTCE19L8el2Sfrm/Ew0YvWLkri ZqOl8pAWiWlNA+x2vKYASmsihaeWevB7qR77+Mbfyxvkkin4qKP2lAZqWvHnKnFxMnyT fe+/WBSG9p1/2Adv7y7XmOfsqv8y6FjJZE6wH38reR9qdj03JA3Oy1U/YBb2tTvQqlbw PSQg==
X-Received: by 10.107.132.157 with SMTP id o29mr47426494ioi.104.1437529631093; Tue, 21 Jul 2015 18:47:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.169.143 with HTTP; Tue, 21 Jul 2015 18:46:41 -0700 (PDT)
In-Reply-To: <55AEAB06.4000306@gmail.com>
References: <6153A91F-7E9A-4579-BA06-72964568D343@cisco.com> <55AE54D3.7070502@gmail.com> <55AE5D01.5090309@gmail.com> <55AE71F7.8000107@gmail.com> <20150721162835.26A9F338B4ED@rock.dv.isc.org> <55AE742E.9040301@gmail.com> <20150721184344.GH90924@Space.Net> <55AEA803.8070504@gmail.com> <20150721202306.GI90924@Space.Net> <55AEAB06.4000306@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 22 Jul 2015 11:46:41 +1000
Message-ID: <CAO42Z2wDQMdgHY==mv509qehVjOMEQCEKgOgvvhNdHnaJMN6jw@mail.gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/O9AIEy4GMECHtcjBPzXeZdCkgHs>
Cc: v6ops list <v6ops@ietf.org>
Subject: Re: [v6ops] Discussion of draft-ietf-v6ops-ula-usage-recommendations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2015 01:47:13 -0000

On 22 July 2015 at 06:26, Alexandru Petrescu
<alexandru.petrescu@gmail.com>; wrote:
>
>
> Le 21/07/2015 22:23, Gert Doering a écrit :
>>
>> Hi,
>>
>> On Tue, Jul 21, 2015 at 10:13:55PM +0200, Alexandru Petrescu wrote:
>>>
>>> Yet ULA gives a certain freedom in the hextets after fd00::, and I would
>>> not waste it by generating a fd00:ca10:8fa3 which has no logic.
>>>
>>> fd00:cafe:: is a random prefix, easier to pronounce, to remember and to
>>> tell on the phone.
>>
>>
>> I encourage all my competitors to use "easy to pronounce and remember"
>> ULA prefixes.  Their address collisions are my saved OPEX.
>
>
> Ok for competitors.
>
> But for friends?
>

Your friends usually do the right thing too or can be encouraged to.
But even if they don't, but you do, you won't have a ULA address space
collision.

If you both choose the same ULA value, you've both failed to learn
from history and will both will pay the price. RFC3879 describes the
prices you'll effectively be paying.

You would also be surprised at how easy it is to remember a random
value if you use it enough e.g., type it in enough. I was assigned a
random 6 letter character/number username at an employer in 1998, that
I used up until the end of 1999. I suspect it was so that usernames
weren't guessable, as a further security measure. I can still very
easily remember it today, despite not having used it regularly since
then.

Regards,
Mark.

> Alex
>
>>
>> Gert Doering
>>          -- NetMaster
>>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops