IETF Logo Mail Archive

Re: [Int-area] draft-patterson-intarea-ipoe-health: what about FORCERENEW?

Richard Patterson <richard@helix.net.nz> Tue, 17 July 2018 13:58 UTC

Return-Path: <richard@helix.net.nz>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4D3129385 for <int-area@ietfa.amsl.com>; Tue, 17 Jul 2018 06:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=helix-net-nz.20150623.gappssmtp.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 s79RVxVvj-C8 for <int-area@ietfa.amsl.com>; Tue, 17 Jul 2018 06:58:41 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 0F407130F2C for <int-area@ietf.org>; Tue, 17 Jul 2018 06:58:41 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id y124-v6so14666615itc.0 for <int-area@ietf.org>; Tue, 17 Jul 2018 06:58:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5wacw/hGJpgsXQ10sZcu8lD0fy/T2sxczAoqD5NyOT4=; b=SQKjaJhD0Dr8Je00G1NZwBg1TWxsSOatvTng9ScamXT+GtCl8PeGFjYkGPxGusP4nO AT+mdWGNuIt2WvQIEslBMwVIKooLKfYx8GpLlBe+x+wQxW6ge6V4pfAXfcDgIKuH4y2b NfF6+iQwj28l3VplVy12+aCg/sUJmtRJ99uTUtKEV/jYj+XSQLuEH++KmxuuQ21Ox2oV 8S49UELcNETyPeCtL2T9P0fN6KTFdOjJzfmyERhGwXBJXnc1zjJgVB4cYLpi4SpMKRyi +FGly23/OJBTGaRgNS1GcRz3dgffzztJoYwVqL0YtZYtr59iFk7H00/g/CZk+N/WJPBF s0tQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5wacw/hGJpgsXQ10sZcu8lD0fy/T2sxczAoqD5NyOT4=; b=tNYU/U+5TanCKAWstClj6x5WnzwNMjokGH315Lk2YsHZfn/Cq6DQS2YSLtuW25Wsvz 9v3Z8yanlXiOL/FKmekGaypX4EtKPj3XlNenVBiNza1DCNZQhIUHhAkmUjDSnXOg/Kv8 xJjR9xAUkUPcH9L3d12xDmakjfHe4Dqs0JGLDEzdjJjIMgVsTh2dZ6B8aNgZDn3tFhyM AvlqlDRsxmgWIkNjGZFu+it6Mab4cP4OaEKz3bhwjnY0quXroP1mdoM1hSSsyx1aZteP onPj5AKVBR8zZA3HztsnoxSwwC5BoxOVQ4WNPuv9JslR6wG98EFMSrpLgTgotzQF7rmu 11HQ==
X-Gm-Message-State: AOUpUlEVkL2r6FFt7l52JJP4QhNW5A/8+fqtsRPoIht0E4vsoVET5zk5 G/ooW/IS7+4k4wX8UyIT9YMqvR7A
X-Google-Smtp-Source: AAOMgpfb0NDhpXnMmUz0g1Mki+W4sr2qpINzNDtIVzXmZY4XO4IDdNfKDJgJJxkn4AvEZB3rsc2ffQ==
X-Received: by 2002:a24:988b:: with SMTP id n133-v6mr1683082itd.10.1531835920329; Tue, 17 Jul 2018 06:58:40 -0700 (PDT)
Received: from mail-io0-f176.google.com (mail-io0-f176.google.com. [209.85.223.176]) by smtp.gmail.com with ESMTPSA id 132-v6sm659664ita.37.2018.07.17.06.58.39 for <int-area@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 06:58:39 -0700 (PDT)
Received: by mail-io0-f176.google.com with SMTP id k4-v6so1053007iob.3 for <int-area@ietf.org>; Tue, 17 Jul 2018 06:58:39 -0700 (PDT)
X-Received: by 2002:a5e:8341:: with SMTP id y1-v6mr1408418iom.183.1531835919164; Tue, 17 Jul 2018 06:58:39 -0700 (PDT)
MIME-Version: 1.0
References: <87601eyh8m.wl-jch@irif.fr>
In-Reply-To: <87601eyh8m.wl-jch@irif.fr>
From: Richard Patterson <richard@helix.net.nz>
Date: Tue, 17 Jul 2018 09:58:27 -0400
X-Gmail-Original-Message-ID: <CAHL_VyBgw0c0HwQn4Mtwebv_26YetZr_nj3dPr2mvtwFXtff-A@mail.gmail.com>
Message-ID: <CAHL_VyBgw0c0HwQn4Mtwebv_26YetZr_nj3dPr2mvtwFXtff-A@mail.gmail.com>
To: jch@irif.fr, int-area@ietf.org
Cc: mikael.abrahamsson@t-systems.se
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/cwdmOkvcnscetEae4NWuTGVmy6E>
Subject: Re: [Int-area] draft-patterson-intarea-ipoe-health: what about FORCERENEW?
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 13:58:54 -0000

Hi Juliusz,

The third bullet point of Section 2, Alternative Mitigations, already
mentions DHCPv4 Force Renew, and DHCPv6 Reconfigure.
In my personal experience, I'm yet to find a BNG or CPE that supports
them, but otherwise I do agree, they could be used to mitigate
downtime during planned maintenance.

-Richard
On Mon, 16 Jul 2018 at 17:59, Juliusz Chroboczek <jch@irif.fr> wrote:
>
> Hi,
>
> I've just watched Richard's presentation about DHCP health, and I'm
> wondering whether at least the planned maintenance use case couldn't be
> solved much more simply and elegantly by FORCERENEW (RFC 3203 + RFC 6704).
> At the very least, I'd like to see it mentioned in the draft.
>
> Thanks,
>
> -- Juliusz
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

v2.23.0 | Report a Bug | By Email