IETF Logo Mail Archive

Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

Tim Chown <Tim.Chown@jisc.ac.uk> Tue, 26 February 2019 10:06 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 DDA29130EBF for <v6ops@ietfa.amsl.com>; Tue, 26 Feb 2019 02:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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, 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 37QfroDWw84d for <v6ops@ietfa.amsl.com>; Tue, 26 Feb 2019 02:06:33 -0800 (PST)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1D57130EB4 for <v6ops@ietf.org>; Tue, 26 Feb 2019 02:06:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1551175591; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fQKj0fAJEqKjTb+2iQWVZ1NXbxCjKAcD48R7GsP88oU=; b=HBcYMzvRhHQVTtl4OK8qzdzMM3xj/f24ks4k2GZQ9bfkrcGTpt/+TaMZLxuAmsctfxkoFsbx9GC3dHGWFt4au8hGT37vqRe6M2wvQbJLSxliS4A4idcR51I+hHZMaXdA1dOqPIP1N6YUF58KihpqqRb9a/6b6rC9xFvHEHjms7w=
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-ve1eur02lp2051.outbound.protection.outlook.com [104.47.6.51]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-127-H3d02anXOdixwOMM5QFdIA-2; Tue, 26 Feb 2019 10:06:28 +0000
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com (52.133.54.140) by AM0PR07MB4705.eurprd07.prod.outlook.com (52.135.151.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1665.6; Tue, 26 Feb 2019 10:06:24 +0000
Received: from AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::617a:4c8b:34ae:efcb]) by AM0PR07MB4177.eurprd07.prod.outlook.com ([fe80::617a:4c8b:34ae:efcb%4]) with mapi id 15.20.1665.012; Tue, 26 Feb 2019 10:06:24 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Fernando Gont <fgont@si6networks.com>
CC: Richard Patterson <richard@helix.net.nz>, Fernando Gont <fernando@gont.com.ar>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Thread-Topic: [v6ops] A common problem with SLAAC in "renumbering" scenarios
Thread-Index: AQHUzTkBQuNentVJFkebkUvTotpgtqXxzZ4AgAAEqwCAAAkfgA==
Date: Tue, 26 Feb 2019 10:06:24 +0000
Message-ID: <899A1249-D3D9-4824-8B2E-7E950FBB316A@jisc.ac.uk>
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <20190220113603.GK71606@Space.Net> <28fbc2c305c640c9afb3704050f6e8d7@boeing.com> <20190220213107.GS71606@Space.Net> <019c552eb1624d348641d6930829fd1f@boeing.com> <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com> <20190221073530.GT71606@Space.Net> <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@mail.gmail.com> <a73818d31db7422b99a524bc431b00ed@boeing.com> <CAO42Z2z9-48Gbb_Exf+oWUqDO=axSLpZBtqeDcxkAoFq5OziGw@mail.gmail.com> <CALx6S3624hnGauG1HaSWPMvQw0t2Q5R3gb8W4R8w3kuK7dcrWQ@mail.gmail.com> <1F07F2BB-2F37-4D12-9731-7892DF4E3D88@consulintel.es> <0a582916-af14-bd82-a4cd-002a36f8830b@huitema.net> <67515a73-26a5-3ed0-da88-1a4ce64550d3@foobar.org> <360afa02-cf23-375c-4876-780d3c2aa5ac@gont.com.ar> <CAHL_VyD34V=TRcsCp0DOO9HJNHyy5xkiMQ_cZoBa7zTE4fe5OA@mail.gmail.com> <ead01e0a-9211-7944-88d6-ae8d037c03a8@si6networks.com> <FB8B77EE-CC16-4418-BB5E-D44EE66D6B72@jisc.ac.uk> <29dcc6ed-03f6-3ead-6866-eecbefdf1483@si6networks.com>
In-Reply-To: <29dcc6ed-03f6-3ead-6866-eecbefdf1483@si6networks.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.102.3)
x-originating-ip: [141.85.248.6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a020c208-2b16-429a-bf02-08d69bd210db
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:AM0PR07MB4705;
x-ms-traffictypediagnostic: AM0PR07MB4705:
x-microsoft-exchange-diagnostics: 1; AM0PR07MB4705; 20:v2OHvJWUCi2Rgsge4PGw6Wn8bEkHayb864Rqn9kBHGi9GTgY4nfbN2p+98D5g991t5UAaYlRo2TxRZaANbs5NRv9/b+tbVd5OlC3AqHNpMymu6fUNKLRqTROl5rLTAsUyfpHVr4WMMyE9UlL+iFyO42Qq3JMs0ubbiVUwrDhBQA=
x-microsoft-antispam-prvs: <AM0PR07MB47058D18982AE22FC1975E8AD67B0@AM0PR07MB4705.eurprd07.prod.outlook.com>
x-forefront-prvs: 096029FF66
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(39850400004)(396003)(366004)(346002)(189003)(199004)(305945005)(25786009)(6346003)(68736007)(93886005)(33656002)(26005)(7736002)(6246003)(3846002)(66066001)(6486002)(6116002)(186003)(102836004)(2616005)(105586002)(83716004)(71200400001)(71190400001)(6506007)(6512007)(74482002)(11346002)(446003)(53546011)(66574012)(97736004)(106356001)(476003)(6916009)(76176011)(478600001)(5660300002)(256004)(81156014)(8676002)(4326008)(14454004)(486006)(2906002)(8936002)(82746002)(81166006)(316002)(54906003)(53936002)(86362001)(6436002)(99286004)(786003)(50226002)(57306001)(14444005)(36756003)(229853002)(72206003); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB4705; H:AM0PR07MB4177.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: wek86SSiuYS0FCP69v4OpVFe+EvJumv8rdALIqgUv+X60+k5O9cF2L46iHk+eZvsNa1J/2qO7AWwlxIFmURvgRPAYoQEM8oMxuaarjyWbzXJuj4OkJi9bKNsdId132ZX9yBXOle+wNdNrORiTo1UXfWjwexk9KhBRY6jIQGZCGf11Tbt6oYQabPlvSfJSENjPizH/4bsNmSChRJlT6ogHW+IrT51KO6mr6WBk+fNTQ9lyNQ3IwRq+kboCs9NR0Zv91l1UlJh0RBL1G4GQDHZR9L2fpEw/jnEBS75e2ks991lOgh18b6G4J7CzCf+HQn/nIcRGIo0bawliRGwr50PtkwqSJEnVFZDFz4SusLtJQGcZZd8wzKmDVSzUdzWzsz2UVS1yJamFA61rY4NjUlHpgrPJv1oOB1y78EAu9EdtHY=
Content-ID: <FF5275B041034641B3F2C802D197555A@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: a020c208-2b16-429a-bf02-08d69bd210db
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Feb 2019 10:06:24.6587 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB4705
X-MC-Unique: H3d02anXOdixwOMM5QFdIA-2
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/O7iCEv3MDTp7SoiQF_OuHFRFRfw>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
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: Tue, 26 Feb 2019 10:06:35 -0000

> On 26 Feb 2019, at 09:33, Fernando Gont <fgont@si6networks.com> wrote:
> 
> Section 6.2.1 of RFC 4861:
> 
>      AdvPrefixList
>                     A list of prefixes to be placed in Prefix
>                     Information options in Router Advertisement
>                     messages sent from the interface.
> 
>                     Default: all prefixes that the router advertises
>                     via routing protocols as being on-link for the
>                     interface from which the advertisement is sent.
>                     The link-local prefix SHOULD NOT be included in the
>                     list of advertised prefixes.
> 
>                     Each prefix has an associated:
> 
>                        AdvValidLifetime
>                             The value to be placed in the Valid
>                             Lifetime in the Prefix Information option,
>                             in seconds.  The designated value of all
>                             1's (0xffffffff) represents infinity.
>                             Implementations MAY allow AdvValidLifetime
>                             to be specified in two ways:
> 
>                               - a time that decrements in real time,
>                                 that is, one that will result in a
>                                 Lifetime of zero at the specified time
>                                 in the future, or
> 
>                               - a fixed time that stays the same in
>                                 consecutive advertisements.
> 
>                             Default: 2592000 seconds (30 days), fixed
>                             (i.e., stays the same in consecutive
>                             advertisements).

So given that document is 12 years old, with that default copied from one that is 21 years old, is an update required?  

And if so, to what?

Tim

v2.23.0 | Report a Bug | By Email