Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

"Bernie Volz (volz)" <volz@cisco.com> Wed, 30 October 2019 14:03 UTC

Return-Path: <volz@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F5B120112 for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2019 07:03:13 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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=dT6zNNQu; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=A3Pqwy4r
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 7lk2CgeQDdCf for <v6ops@ietfa.amsl.com>; Wed, 30 Oct 2019 07:03:11 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD9F21200DE for <v6ops@ietf.org>; Wed, 30 Oct 2019 07:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13220; q=dns/txt; s=iport; t=1572444190; x=1573653790; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=osbYUwSIxkQ61PutpJ1c9VsWBGp4oPYvSj36Pu35WY8=; b=dT6zNNQucal1BlPgahoHKMey17D0bGvVMWrV5BJS1cTWUlQO0qLbqj5O OqW0M1CW8UZdRa2jQgcNUOybI9kGdjDmhxvHHBZO3dJSW21FQa9mK067B Sf0ZLz278MrN4J1N9PenJ2aKXVWhKvSX3nH591pTq9m60NT1AHDlHQGof w=;
IronPort-PHdr: =?us-ascii?q?9a23=3A7GC9QBQIiz02/mAHJgFGvt15B9psv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESUANfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5NksAKh0olCc+BB1f8Kav0aCgoNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAADQl7ld/4kNJK1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBEQEBAQEBAQEBAQEBgWkEAQEBAQELAYEbL1AFbFggBAsqCoQ?= =?us-ascii?q?eg0YDhFqGFYJekwqEYYEugSQDVAkBAQEMAQEtAgEBhEACF4NPJDQJDgIDCQE?= =?us-ascii?q?BBAEBAQIBBQRthTcMhVEBAQEBAgESEQoTAQE3AQQLAgEIDgMEAQEoAwICAjA?= =?us-ascii?q?UCQgCBA4FCBqDAYF5TQMOIAGoLgKBOIhgdYEygn4BAQWFFxiCFwmBNgGMEBi?= =?us-ascii?q?Bf4FXgkw+hC8CFjSCWjKCLI0LgnKFPII5lgAKgiSVTJlehFeGE50kAgQCBAU?= =?us-ascii?q?CDgEBBYFSOYFYcBWDJ1AQFIMGDBeDUIpTdIEoiwaBMAEvXgEB?=
X-IronPort-AV: E=Sophos;i="5.68,247,1569283200"; d="scan'208,217";a="360089573"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Oct 2019 14:03:09 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x9UE39Vf021427 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 30 Oct 2019 14:03:09 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 09:03:08 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 30 Oct 2019 09:03:07 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 30 Oct 2019 09:03:07 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fGPK4LXRW6jkIGiCZSkRnEKybd8n2iEJPmMSqLq0OB+dwfG+0Qkj4E8vOduqRE1kD0rQAQ9hsUgbrZpZGegEewDxoRNcgbNshqwiZVBcOEg9JvrdrxZe4utWxcS8OEiD+UtLcgVquQ7G/7AdUnak0HBdOSQ1DsM3+Yr7rJO58TlD+88+6T4vuMZEVWnnpuh9VuTR58hlk4usYOZg0/UxTBNcjAUtGJzOyHqjINxVj4BPMRa8Y2GX3O+MklqiLbTxqyeDn0Wh8uouXLIWAjRnCMCluGwVqmLbToZ7+6N5d7afXjhD4UBHNem47DtdrcRdvjNe4wCSE/RD5ImR1zHpcw==
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=osbYUwSIxkQ61PutpJ1c9VsWBGp4oPYvSj36Pu35WY8=; b=TJthuIRpJ/LOr2wPxZR2RXIDKZXHVvbYPpSsiNMq3Ufk8anThLwMGYTNPncufE4EpJsvOpzZaNaNZdsBvPoKujBgK2RTLd/juCO5inebXqkDVuh1dQuP928bzLfx2Jyp149lFo1UH+kNOt+5rSSEERH780x541oOlqIEf0+fglwtEa7fVUtSH7Hpl/Z/Rl57uFNtfSUUfEdXDfQXoLMgsyadNnMAWarAAr7ME00NaXRwj8I/uxBY/JuUpP1r5jBnIMdEOhvXklCWlFeNtFpHajNJZ0ML34ky2g93JZKA5fhw69vOQ4RDvIdnIkRXkH8HNrDGQl9ADeQKTsS9KGmuHw==
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=osbYUwSIxkQ61PutpJ1c9VsWBGp4oPYvSj36Pu35WY8=; b=A3Pqwy4r1ODJjPBbmi79SqphoU8EWsD24hyZ8eR0XPiPLMKJYDYyI/QfLO7v5be0hm/b10CpxL65yPXNHPrjotK+AspLxv75R9dBT5lPrcTfKBbAFxUfXCqQ5+LMiy0WaNGXMC/gGwQZJr4/cwQB4OeUvYnbxwjV3TpKA2YKAsE=
Received: from MWHPR1101MB2288.namprd11.prod.outlook.com (10.174.97.139) by MWHPR1101MB2191.namprd11.prod.outlook.com (10.174.101.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.22; Wed, 30 Oct 2019 14:03:07 +0000
Received: from MWHPR1101MB2288.namprd11.prod.outlook.com ([fe80::808:4d44:a5d1:c7f6]) by MWHPR1101MB2288.namprd11.prod.outlook.com ([fe80::808:4d44:a5d1:c7f6%11]) with mapi id 15.20.2387.028; Wed, 30 Oct 2019 14:03:06 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: Timothy Winters <twinters@iol.unh.edu>, IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
Thread-Index: AQHVibwc6PRwlsH+ZUmOeFzp+XKiI6dt8FJugAA0sICAAERiAIAAM1UOgAAj7oCAAC8lwYACBjMAgADxGbaAASHcfIAAAh0AgAAETICAAAb1gIAAEaAAgAAA6YCAAAIjAIAABSGA///EFwCAAEp4AIAAAM9w
Date: Wed, 30 Oct 2019 14:03:06 +0000
Message-ID: <MWHPR1101MB22889898CBD2143BA84DA1C8CF600@MWHPR1101MB2288.namprd11.prod.outlook.com>
References: <CAOSSMjVhK_V4HpMzprOyo9pj=ysFef+uZUs=twd_zfPaBdPu3Q@mail.gmail.com> <0F0B6068-CA62-449B-B56E-78E9EF8D998E@fugue.com> <CAOSSMjVLP4dx0Z1OKgXBgmuUCmR_C35J87fgkX7V=e7E3iQY3w@mail.gmail.com> <96344740-2F4B-4BCE-A881-EB1A5933AFA2@fugue.com> <F7F614D9-EC79-474C-B81C-CEF0B9EF6908@cisco.com> <591F3207-735E-4182-82AD-A88F4A01C678@fugue.com>
In-Reply-To: <591F3207-735E-4182-82AD-A88F4A01C678@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=volz@cisco.com;
x-originating-ip: [173.38.117.77]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: eb40ea07-d442-4519-ca0f-08d75d41e389
x-ms-traffictypediagnostic: MWHPR1101MB2191:
x-microsoft-antispam-prvs: <MWHPR1101MB21918A70DDBB7AE7410512C7CF600@MWHPR1101MB2191.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(376002)(366004)(396003)(39860400002)(189003)(199004)(790700001)(86362001)(2906002)(486006)(8676002)(64756008)(54906003)(14444005)(256004)(446003)(33656002)(81156014)(81166006)(11346002)(186003)(476003)(26005)(102836004)(66446008)(71200400001)(8936002)(71190400001)(6116002)(3846002)(53546011)(6506007)(76176011)(7696005)(66066001)(14454004)(4326008)(229853002)(6916009)(76116006)(66556008)(55016002)(7736002)(6246003)(6436002)(478600001)(236005)(99286004)(74316002)(66476007)(25786009)(52536014)(5660300002)(6306002)(9686003)(316002)(54896002)(66946007); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR1101MB2191; H:MWHPR1101MB2288.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: OouYEnNlQ2Rw/Ls7J8JwoTFCUdOpQUahutIDKq/l3WpVnzFg8CJrO7BkyRR2vWS6qWgDaqDUQI02MOJ8rmifeDV/aQSTd1z6i5sl3tiaVPXF0jV1k1fUeG4nnERySCt+RKzNVuLXNWQkIKTgIlN1waUw+LZhkBZSg9dYQpnle6FdOVEdz/yvzKadE/Ke8TbQjXID1CODmQw1K/X0NUSc19MrEDaud7TW6B/Et0thhWeuwjsx2VFXXU5J7BTmn2FR88etmGmSDpZ5cAYip0+r+oSZ4SSQ5lQHnB8gNYisOWsbjJ/5bbSjAqk2wyBDZ0//QciB3r9J6ok523vhhM9fik08J76KiLs6gH/IY6BHreKGxWjVLakVNlRYVMTsC5z1aMdCcrYTua3CFVIjlCY5WuPS4z0PphUrxSdB8wr1H6MF3cUcRX8j8D8nCPSlfgqR
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR1101MB22889898CBD2143BA84DA1C8CF600MWHPR1101MB2288_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: eb40ea07-d442-4519-ca0f-08d75d41e389
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2019 14:03:06.5451 (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: rREyZhC/UUaZbeyR0OMFe8z6o5Qw1fMeucC4JMTcjIrBpFj0uj1kHMad5cULBj4z
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1101MB2191
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/6bk42MYCurOtZ_NHaK5JSadNrCM>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 30 Oct 2019 14:03:13 -0000

Ted:

A Solicit kind of means “start from scratch”. So that’s why the current RFC8415 specification does not require sending information related to “old” leases. The text also does not provide for sending 0 lifetimes in an Advertise which is where this would first appear – and then also in the Reply to the Request. Perhaps there is an argument that these leases should not be added to the Advertise, but be in the Reply to the Request.

So, it does get a bit more complex and needs to be worked out.

> I don’t see any reason why this should not just be the default behavior.

As I said that as this is a change in behavior, we don’t know what the consequences for existing devices may be – and in some cases, if the device does have storage, would this confuse it? I’m not against having this be a configuration knob in the server which can be applied at various “levels” (perhaps even globally).


  *   Bernie

From: Ted Lemon <mellon@fugue.com>
Sent: Wednesday, October 30, 2019 9:51 AM
To: Bernie Volz (volz) <volz@cisco.com>
Cc: Timothy Winters <twinters@iol.unh.edu>du>; IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

On Oct 30, 2019, at 9:24 AM, Bernie Volz (volz) <volz@cisco.com<mailto:volz@cisco.com>> wrote:
When a CPE boots and does a Solicit / Request, it could include a new option that tells the DHCP server that it has no storage and therefore no knowledge of any “past” leases. The DHCP server in this case could include any “old” leases it still has a record of (i.e., that have not expired but are no longer “valid” in terms of the configuration because of renumbering or other conditions) with 0 lifetimes. That would allow a rebooting CPE to learn old delegated prefixes that it might have advertised to its clients and initiate deprecation of these prefixes (and any addresses generated from them).

I don’t see any reason why this should not just be the default behavior.