Re: [v6ops] A broken promise - "You said PD Prefix Valid Lifetime is going to be X"

Ted Lemon <> Fri, 01 November 2019 16:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9324B120122 for <>; Fri, 1 Nov 2019 09:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 01H7CScsQwhc for <>; Fri, 1 Nov 2019 09:47:49 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7B266120019 for <>; Fri, 1 Nov 2019 09:47:49 -0700 (PDT)
Received: by with SMTP id x21so13627372qto.12 for <>; Fri, 01 Nov 2019 09:47:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=vhW1NiCSshmuUmCP3eESwdo580DuZaAZNg+1o4T8Pgo=; b=k0kwOap9dlrIWck1nFBljacEUyyWG27Fha7Wce738xMCCWtmKa4GuXVXqX5qPljJoJ fz4xjxiuhaodeztUPM1ZQJa4/qj4eymG3Jmvfh0dRmfi0FcvvIpsfERHfORgECvWRJDe ocHw7BREKlZ0zjqbpKSNzd6+EL5pWSI53iJkGC5ZoznvxGecz8QbwVxTJAAFQtOE0aCh FTSdjLWrCAN4CzOjDObACZTYYUcB1WmwOD339B8IOWZgZVZM4Jv89BJHB0At8v7H6Klf OZJ0rUjeeVwfktlK4AnvDdiLLeZM91efYHFJhdtrSbneGEYjdFEkA1o8Fnu+F9KpA2ij 1GTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=vhW1NiCSshmuUmCP3eESwdo580DuZaAZNg+1o4T8Pgo=; b=ALTzxPLRZbK183JNnpKJ07szNRBYl+nFiVWFKSdr3OJMXV93gauz/auB3C311B5+6K rLTvBb3/zEVcaXuxf35Gck8Mu90Px4NFfMgumELb6V1Nc22d4J2Mbx8e9HansHGSoRB4 tsvm87gIKj8FDW2QQKTZPlZub/Z05ac0NXfItVH9HGXlUpDuvV7bK5s9KnzETLv8x/uk NoV9s8eXYd2cN4s8vnshEVqswwl3BMq6JMv9XEZe2fO+Re/tNGD6NkqSoe5Sr3JC1rC5 n1+xC+8WZX6Vp9R5W57SM8cPsdCbjY4NADl9xxrUfczSf7ZVDQGgiZ0lJW+i+FH2MNED iA0A==
X-Gm-Message-State: APjAAAU5IL6asCp/osyuVoYB5ivZSDCRlfyXysC7/v3Otsi0kSnq0NA9 TlqWASXExbq8TuZra0P3UvadC483ncocLg==
X-Google-Smtp-Source: APXvYqzyiFgLIzJz4WvfNVRSYK8glq2OlgmW4WsgU5yRZ3L3P3V/s8OAauBGHeQ7bJZWwfWSbJOcng==
X-Received: by 2002:ac8:e42:: with SMTP id j2mr217466qti.131.1572626868349; Fri, 01 Nov 2019 09:47:48 -0700 (PDT)
Received: from ?IPv6:2601:18b:300:36ee:cef:776b:2643:f7b7? ([2601:18b:300:36ee:cef:776b:2643:f7b7]) by with ESMTPSA id a28sm3698730qkn.126.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Nov 2019 09:47:47 -0700 (PDT)
From: Ted Lemon <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D86FCE74-3695-404B-82ED-F43703272D9E"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Date: Fri, 1 Nov 2019 12:47:45 -0400
In-Reply-To: <>
To: Owen DeLong <>
References: <> <> <> <> <>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <>
Subject: Re: [v6ops] A broken promise - "You said PD Prefix Valid Lifetime is going to be X"
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 01 Nov 2019 16:47:52 -0000

On Nov 1, 2019, at 12:42 PM, Owen DeLong <> wrote:
> I’m not even saying this is necessarily an invalid approach. We all know
> (or at least should know) that the margins in this industry don’t support
> the cost involved in doing things differently,

I don’t think that’s the issue.   I think the issue is that “no flash renumbering” is a nice-to-have, not a must, because the layers above layer two can adapt when layer two breaks.   We’ve done a lot of efforts to try to fix this problem at layer two, and none of them have succeeded.

This is not to say that making layer two as solid as possible shouldn’t be a goal; just that it is merely one of the tools we have for making the network reliable, not the /only/ tool.