Re: RFC4941bis: consequences of many addresses for the network

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 24 January 2020 21:12 UTC

Return-Path: <pthubert@cisco.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 E8A5C1200A3 for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 13:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=c7br1DQB; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=xH2u8PSF
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 XgeezLwYD3BZ for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 13:12:52 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46527120052 for <ipv6@ietf.org>; Fri, 24 Jan 2020 13:12:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2058; q=dns/txt; s=iport; t=1579900372; x=1581109972; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+TfKWHBCJBo5goTl60rTUTmY4y1I4PmPTUcjquYHOpI=; b=c7br1DQBIvncXjZZVvhDV3eQvHCwKlmiH8ZSR3SRPQgyr5vwhJU2ESmd xUbNerfMkovPQQFufHl1OJqI+wumdjawtiaLU5afT41T5BTioq3DI0vwW 3PSVcJ6RTcUbkLt/9br6n5FsrXGK2WyBHn34bVO04+4ad1paPmRWlijtz Q=;
IronPort-PHdr: 9a23:RIwWghd8oQQEeKqfgHXo9scUlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dzA6Ac5PTkNN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BKAAATXSte/4kNJK1lHAEBAQEBBwEBEQEEBAEBgWcHAQELAYFTUAVsWCAECyqEE4NGA4RahjiCX5gPgS6BJANUCQEBAQwBARgLCgIBAYFMgnQCF4ILJDQJDgIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAgEBARAREQwBASwLAQQLAgEIGAICJgICAiULFRACBA4FIoMEAYJKAw4gAQIMolECgTmIYXWBMoJ/AQEFgkSCThiCDAMGgQ4qAYwWGoFBP4E4IIJMPoEEgWABAYRzMoIsjWCCdZ4RdgqCOZY3G5p8qW0CBAIEBQIOAQEFgVI5gVhwFTsqAYJBUBgNiAEMDAuDUIUUhT90gSmJTCyCFwEB
X-IronPort-AV: E=Sophos;i="5.70,358,1574121600"; d="scan'208";a="709262127"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 24 Jan 2020 21:12:51 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 00OLCp4j017668 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 24 Jan 2020 21:12:51 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 24 Jan 2020 15:12:50 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 24 Jan 2020 15:12:49 -0600
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 24 Jan 2020 16:12:49 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jcuspsmNTjxel4OHQloJKM9HV/eFBIKHZ/nXIL4SzISd+3qSqzNy2Ub1GSn0UiNNEY0K+/MAc/W6HkzWcmaMB1nz67VwEgheUE7hsgSdfGHGVR5c4Xd7zTYS1ktR+25XJcRezBEoeBn8xk78sAvzDxrOdyXG7ZIcSvxXk7DT0/NcAmy54ZOqV+K9tuJr2A2UJTZuvSd2ZDSVPtp6CPQtPQBQ60j0v1M5STizKHTJoqwF92HhXf99r3jddHizXVZcJk5bsNn6Yg/zgxPtZO0Xw1CYIzH29GoH59aviiu6eTnQ5YMhwoYbRMl+KcdQoY9jWj0rW0OvAtHxt5f2Ab9I8A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+TfKWHBCJBo5goTl60rTUTmY4y1I4PmPTUcjquYHOpI=; b=YoCyFQt947pDV4ebY63BFONCqmPBu3GzGnrhoRyrox1HdlCOExwHAo90Mbrqplp+CRT/YCSEZQNrUqM/LKJoV6Fs00ww47o8jllua5bh/GLV0/J43G3dqGryKljCNDR0K5KfPfUA0dlodT+Ceww+2t9q33CYXXXQ2uTbeE6DT6+4bImJIS2CfSrlJa/Rdv2U1xRQe+dHj6TxF1udJHdqBiBVGgkIJ8W0FBSeBHT5Gg71mdqP3kY1o6L5Ka5dExBZ2PZL5w+6VLW5EDBRtqjRjHxjh6LWqVdExZxs/298eqDefW9U/jheAVyux626piscmsEV9JO0CcTp3j34+ZhQSQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+TfKWHBCJBo5goTl60rTUTmY4y1I4PmPTUcjquYHOpI=; b=xH2u8PSFXSAUyCH5zf9mvVoXIT1ftSMtWiHpZrUYCrRXi4sb/lbRy4pRYY6TQJC3ellYj40owrTVvTjV28zTrZgIlE/8Ne0+L4cVKlvv6+xQ44hqPRUfwm0XkfrxuRiJoR/pmgl1etJJUR9oK1nb0H7ANf8FshHdJp0buwm+Eaw=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4397.namprd11.prod.outlook.com (52.135.38.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2644.21; Fri, 24 Jan 2020 21:12:47 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::fd76:1534:4f9a:452a]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::fd76:1534:4f9a:452a%3]) with mapi id 15.20.2644.027; Fri, 24 Jan 2020 21:12:47 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
CC: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: RFC4941bis: consequences of many addresses for the network
Thread-Topic: RFC4941bis: consequences of many addresses for the network
Thread-Index: AQHV0ct5x17hjGfK3kqevW8Gxhyx/qf4RoyAgAAD4oCAAVZFJoAAcXMAgABAUUk=
Date: Fri, 24 Jan 2020 21:12:47 +0000
Message-ID: <A905CA1C-ECE9-411E-AF08-BD11D6D68DF4@cisco.com>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <e936078e-01f9-0254-a8d0-4095455154ac@si6networks.com> <D85412DF-4B03-4790-9E39-968D50ECF86B@employees.org> <m1iuwJV-0000MAC@stereo.hq.phicoh.net>,<31399.1579886556@localhost>
In-Reply-To: <31399.1579886556@localhost>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:482c:9ac6:b132:c6a6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ed14a3df-9e17-4f13-5ff1-08d7a11229bd
x-ms-traffictypediagnostic: MN2PR11MB4397:
x-microsoft-antispam-prvs: <MN2PR11MB439734983AA6677E0E40DC3FD80E0@MN2PR11MB4397.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 02929ECF07
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(376002)(396003)(366004)(346002)(136003)(199004)(189003)(8676002)(8936002)(81156014)(4326008)(5660300002)(66574012)(6486002)(81166006)(6506007)(6512007)(186003)(478600001)(36756003)(2616005)(966005)(71200400001)(33656002)(91956017)(2906002)(86362001)(66476007)(316002)(66446008)(64756008)(66556008)(54906003)(76116006)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4397; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 89uQRwugiFOZpzonU1oEMvEp19eZ3oeNBwujJ3eVs3OzaysICz3gRTMfpzHBuToXant9WJzY2U6MJEwLqdsjvwRVb6Ct+akMKw22vUIg2yjZIa4u8gPy5HwWTuPcI+vwTtbSmc6Ct+ER9c7KieT72Pf133RoQceQdDtwQ5CkFnq0bjy4McgkT2kvqgOslJWIk7kjdaNi0swMVM/9mpKXdC8GfFn4A2P+zm+pw8V2kBrbZnVoTilJnlJxrJJ0bHo+v4dNcO65vb64vTYiOc0Md9lGLHggUSLu1srmvR3NLEUQ26Qciw+wNVDkcLbEYZbXR/y+RiWZSVwYZFi/pUTw57Viufq0BDkJVrgqPGcNRyNha6UyCx3r031fRHCiGIkYiPqPxFZcDdjkcT+/FsajeXV9dNY9NcZiR7ROKN0MJGodced9uQx208UfcuhGE2qLGyjh2pz8s494pyT4m1rtv8YvfIhZXzW9a7EHd8h6wdI=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ed14a3df-9e17-4f13-5ff1-08d7a11229bd
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jan 2020 21:12:47.6855 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: U+ubSiBXDEka9vEp42sryyTBZ087dBS1V41vfkaaYMwiX4wGw5GBnPpdnKvJjpyY00EN3OLnFdYipH9YV/uX8w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4397
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.19, xch-rcd-009.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wreMyvlVjjnvCIeGUxcBBCun4Wo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 24 Jan 2020 21:12:54 -0000

It takes a bit more than that but agreed.
Really the router needs to know which addresses are used and which cease to exist. Even if the host only uses 8 the router cannot infer which one.

Regards,

Pascal

> Le 24 janv. 2020 à 18:23, Michael Richardson <mcr+ietf@sandelman.ca> a écrit :
> 
> 
> Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> wrote:
>> However, given the desire to fit everything in SLAAC, what is missing at
>> the moment is a way for the network to express intent.
> 
>> The most basic way would be for a flag that disables temporary addresses.
> 
>> A more adavanced option would be specify limits on the number of temporary
>> addresses and possibly ways to register/deregister an address. For example,
>> nodes can keep addresses alive be periodically generating a NA for the address.
> 
> I would love to see an RA option with a byte in it that said how many slots
> per mac address the router supported.
> 
> A value of 0 would force temporary addresses off.
> 
> Probably "0" would imply that there were actually two slots available per MAC
> (LL and one ULA).
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------