IETF Logo Mail Archive

Re: a draft about on-link and submit prefixes

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 14 March 2017 15:32 UTC

Return-Path: <brian.e.carpenter@gmail.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 449D112947D for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 08:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HG1e7AvmztKt for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 08:32:02 -0700 (PDT)
Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (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 E9FF5129421 for <ipv6@ietf.org>; Tue, 14 Mar 2017 08:32:01 -0700 (PDT)
Received: by mail-it0-x244.google.com with SMTP id g138so276074itb.0 for <ipv6@ietf.org>; Tue, 14 Mar 2017 08:32:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=+Lj9Q0Kco0fkPbAZxKfnt12XtlOVMIx0NO41Dzd7+ds=; b=r1Fv8jcgcCEXkr24x7owrsRcxFSJ8KWsFL82dElncpB8euc6G+fzJk0k5ObtQORwh1 RlwaJn/Rb4+hIonJjliZqGYC8kjiZUOuobEPXRcMrUx+mBgaji9fnzmu7hZnTJma7l3e M8KhLP9UcBjajVbMquRTSPm3oiTWMq8pomPA5LLeTlYBDKo235h35a1CIzuQegvls+lg eT7aIoeda86C/VFzyfUVAcIClf+YHIUGzIDm88rrloYIUaPZGyELYTDPyHymyXrcjmK9 i1qaW7wi/huFmLFxZvfpjRtdGDpG62Betd6Vtaej5y2lLGf+iUZGTkhBROgb3SWU4yl8 CIjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=+Lj9Q0Kco0fkPbAZxKfnt12XtlOVMIx0NO41Dzd7+ds=; b=DxfD5PbImBRemFduJTYJ1v9qzvkr7OVkw9ewex2x3WjVmBfI5o2+Ttlju/sexj9JVj DKeF89mp5CYTJbfvrx04fRwKikdR4OyWFFcRWxuFINhnUmuOFhCSSreDFLnkIwi0WZXt tyPudhWPyoClJSWFl0wN0GBPhcSWu/u3AqaajzEeXyfNBZYZFLU1aNU8wiqPQuSgzA1W CC7ulEqHh45qCSS880tOoNQmlGcZrw4/nSCKmgQZQSN4LwSo6HMTMRlNluEt34iOGTtV 3FY8CAAKX07iwmn8+UHYzwCZImHxaBIZKIdOsR22aSanANzI7q+ooEaj3aoTZuFL0ZXX JGLQ==
X-Gm-Message-State: AFeK/H3KOMSLVhbG6+9AOjJOq5AhDkSJrlb1rkJBXyVWydsw1GEFqREUQt2s1MX+OA7/og==
X-Received: by 10.36.66.141 with SMTP id i135mr463711itb.86.1489505521289; Tue, 14 Mar 2017 08:32:01 -0700 (PDT)
Received: from [172.16.11.95] (50-76-68-137-static.hfc.comcastbusiness.net. [50.76.68.137]) by smtp.gmail.com with ESMTPSA id g103sm90976iod.44.2017.03.14.08.32.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Mar 2017 08:32:00 -0700 (PDT)
Subject: Re: a draft about on-link and submit prefixes
To: otroan@employees.org, Tim Chown <Tim.Chown@jisc.ac.uk>
References: <CAJE_bqdd9OXOi+SZ8_OfGWXxEoKSfoR6=Lp3-_=vEaWbjx4udw@mail.gmail.com> <CAKD1Yr3ncJkNwZgpWpr049K497iLAQ3dCzJ6dCHM1VsrC8UHog@mail.gmail.com> <20170314.080739.74664517.sthaug@nethelp.no> <9B0384FA-7DF8-4AE2-ADA3-48C142203575@jisc.ac.uk> <BD1C6A8D-F9D6-44D4-9911-20E1DE3F1658@employees.org> <49C05C3D-9594-4A46-BBA4-5767A9FDD34A@jisc.ac.uk> <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org>
Cc: 6man WG <ipv6@ietf.org>, "jinmei@wide.ad.jp" <jinmei@wide.ad.jp>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a7b2d56b-503a-6c2a-8598-fa1f76ba512f@gmail.com>
Date: Wed, 15 Mar 2017 04:32:05 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LwhyWK_hi9jEct2Fg-uMcoXXVOA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.21
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 14 Mar 2017 15:32:03 -0000

On 15/03/2017 00:03, otroan@employees.org wrote:
>>>>> I agree that a generalization is a good idea. In particular, it would
>>>>> be good to have (in one place) a definition of what an IPv6 subnet is,
>>>>> especially if a subnet can be spread across multiple links (which is
>>>>> *not* obvious to me from reading RFC 4861 and RFC 4862).
>>>>
>>>> I like this idea. Examples along the lines that Lorenzo included in his email would also be useful to include, with notes on use cases.
>>>
>>> Any idea of what problem we're trying to solve...?
>>
>> I think it’s adding Informational clarity, especially for those familiar with thinking ’the IPv4 way’, without adding unnecessary wordage directly to 4291-bis.
> 
> Right, that was what I feared.
> Including esoteric examples and examples bordering on configuration errors, just isn't going to add clarity in my opinion.

I think we have no idea yet what the flexibility of IPv6 is going to allow
people to do in future. By the time our descendants get around to
delegating e000::/3 things may look very esoteric indeed. But for now,
I think what jinmei proposes is a good idea - it is completely clear from
the recent discussions that some clarification is needed.

   Brian

v2.23.0 | Report a Bug | By Email