IETF Logo Mail Archive

Re: a draft about on-link and submit prefixes

Tim Chown <Tim.Chown@jisc.ac.uk> Tue, 14 March 2017 09:30 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 87F5F129529 for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 02:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 Gg4oFAMruBpY for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 02:30:47 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7F10129515 for <ipv6@ietf.org>; Tue, 14 Mar 2017 02:30:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1489483844; bh=vmj+JPl75uX53KHJqqqEIgszekaJV9D/fb3cy2/wMpo=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=abq4gSVfmcO/PJBfOfksw8KWDtPnQeq2nHsswhNgwgaY3LGoaYhVgeLKDbQstE1ektdTJuEfzweFw/HLvMQMejIsNa/JAnSZApMGgOS9y5VQhHNGtxFDtf+DH1DqvhWubuuhJefy2fBoKubbglwCPsjCy/OoixqHes1cFxRfraA=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0184.outbound.protection.outlook.com [213.199.154.184]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-108-pmf2uku0N46rqKTI5CnNJg-1; Tue, 14 Mar 2017 09:30:40 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.977.5; Tue, 14 Mar 2017 09:30:39 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::59f7:b9fe:6ca:9476%14]) with mapi id 15.01.0977.010; Tue, 14 Mar 2017 09:30:39 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "sthaug@nethelp.no" <sthaug@nethelp.no>
Subject: Re: a draft about on-link and submit prefixes
Thread-Topic: a draft about on-link and submit prefixes
Thread-Index: AQHSnE+kaN/FUsS5F0a931V053SKyqGTuDAAgAAyhYCAACfvgA==
Date: Tue, 14 Mar 2017 09:30:39 +0000
Message-ID: <9B0384FA-7DF8-4AE2-ADA3-48C142203575@jisc.ac.uk>
References: <CAJE_bqdd9OXOi+SZ8_OfGWXxEoKSfoR6=Lp3-_=vEaWbjx4udw@mail.gmail.com> <CAKD1Yr3ncJkNwZgpWpr049K497iLAQ3dCzJ6dCHM1VsrC8UHog@mail.gmail.com> <20170314.080739.74664517.sthaug@nethelp.no>
In-Reply-To: <20170314.080739.74664517.sthaug@nethelp.no>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [194.82.140.195]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 7:zRPrm3xSvdgQfVcv+Jsihm3kFG1KCVwW+qidbbBlUL5Kq8wO/HN/ZGxAEy38E4WsejJEtBjSXE4v1gfs+4AT8TyvvInxMfOmyGoinTU7W6lsVJXMbAhqMxkjnhkJZrHCM1Ya7z0UpcheIU8wrOvf+WTRj7OD0f5f7kjp7y0YV7YpTXbab3tQzzgBfl7CeRcXDQyJFGiVMy2Eg84ehF11sUSjeOUiNSvKWKXrDzQjdD1OyKzWpCkTvtVx9AcF+/11gGMhWgFSn0XbNL+9Y6ATbyw6LK4WWnUmoq031ARyjPfFlRoi+E5MR3gqB+XdCioGQn39khD4pjDsic+nBj1WyA==; 20:gGojoao9TRUIlYKaisU/sFFyMLDq4EnKYTzIjdltXELQnrz0Eo2jLNqy5Cy96b3fvMeBHHkJycJ2GR/IS6VVAD94Q9oNh78FeGMwOAcyLdgsWo4hl6iJ6jHCnXlahVIjanOVsawetkEYahgIZ6Pa/vbhMuUlZd6DyAFUI+SJRi4=
x-ms-office365-filtering-correlation-id: 10aa86a0-4c32-4aec-94ce-08d46abcc733
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM3PR07MB1140;
x-microsoft-antispam-prvs: <AM3PR07MB114039D692555AD9251D7267D6240@AM3PR07MB1140.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123562025)(20161123560025)(20161123555025)(20161123564025)(20161123558025)(6072148); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1140;
x-forefront-prvs: 02462830BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(24454002)(4326008)(6246003)(5250100002)(86362001)(2501003)(38730400002)(33656002)(1730700003)(8936002)(81166006)(2351001)(110136004)(36756003)(8676002)(50226002)(66066001)(102836003)(305945005)(53936002)(6116002)(3846002)(6512007)(189998001)(82746002)(106116001)(5640700003)(6486002)(74482002)(54906002)(83716003)(99286003)(50986999)(6916009)(6436002)(42882006)(76176999)(6506006)(2950100002)(7736002)(2906002)(5660300001)(229853002)(57306001)(3660700001)(3280700002)(2900100001)(53546007)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <D2E594A86679D142AEBA9202D53A057A@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Mar 2017 09:30:39.3153 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1140
X-MC-Unique: pmf2uku0N46rqKTI5CnNJg-1
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/E8W2StiL48uBFPigWPTzq0vxfG0>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "jinmei@wide.ad.jp" <jinmei@wide.ad.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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 09:30:50 -0000

> On 14 Mar 2017, at 07:07, sthaug@nethelp.no wrote:
> 
>> If possible, I would suggest making this document even more general. It's
>> mostly geared to how implementations treat PIOs, and refers to RFC 4861 and
>> RFC 4862, but really I think the clarifications it makes have much broader
>> impact. As I see it, the core issues here are:
>> 
>>   - IPv6 addresses don't specify any on-link information
>>   - For most (but not all) unicast addresses, subnet prefixes are 64 bits
>>   per RFC 4291.
>>   - A given subnet prefix can be spread across multiple links, and a given
>>   link can support multiple subnet prefixes.
>> 
>> This is not immediately obvious to people who are familiar with the IPv4
>> subnet model, because it is quite different.
> 
> 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.

Tim

v2.23.0 | Report a Bug | By Email