Re: [Acme] IP addresses

Richard Barnes <rlb@ipv.sx> Wed, 25 March 2015 22:03 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B0E91ACE07 for <acme@ietfa.amsl.com>; Wed, 25 Mar 2015 15:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 jRyC2BYJ_GIJ for <acme@ietfa.amsl.com>; Wed, 25 Mar 2015 15:03:12 -0700 (PDT)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) (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 F377E1A9023 for <acme@ietf.org>; Wed, 25 Mar 2015 15:03:11 -0700 (PDT)
Received: by lbbsy1 with SMTP id sy1so28049202lbb.1 for <acme@ietf.org>; Wed, 25 Mar 2015 15:03:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=avyvKe9K1eBX9obLZW9vO7nH+uRFA9/6TuHY5bmmsbg=; b=KYX0DTy/UVVeWgS3LkXqvIuruJ2jXX3e9LI2IFf/XoO2d+DpohBktEE6Fd8Q5+taE1 sr65CNpwFQ8iYHVlb0gm/lrU/210IvVzqsa38aj1hCaLuWdEYVV4UwQZwJBy+TrGV5MW YnLzapGa99rO3abhfJPceXO7n47U2xGYkAAztYo1JdQKph3DvFCeMAHJ2jCch41m3plr CDqTDZi/Es/amcIAcoHvpzHVxconigGE+bcbEMEtNOaRwX0T45VVP7B//WprA9RwTlxF kAGTSDuQ1kgON19iwZopcS1rkN4EoRZYNOeOb3jDRZIexgJ/mH+WvCiWobGVFy0/FC4o Pttg==
X-Gm-Message-State: ALoCoQlNNM/kl+KCCdh8cnAndgGVgm0IlUsgtfpUbNKgphmtZ3VT/xjHf5jLA+aY0+Hb0I8Zm24B
MIME-Version: 1.0
X-Received: by 10.112.199.36 with SMTP id jh4mr10170467lbc.49.1427320990521; Wed, 25 Mar 2015 15:03:10 -0700 (PDT)
Received: by 10.25.135.139 with HTTP; Wed, 25 Mar 2015 15:03:10 -0700 (PDT)
In-Reply-To: <CABkgnnWg_5GTayp2BVPnJZKDKS50a=kHZRbkJ32qOWJxoN3wwQ@mail.gmail.com>
References: <m31tkdgp7w.fsf@carbon.jhcloos.org> <5512F4DB.5090805@eff.org> <CAL02cgS1d1WHy3JVUaaWeG1UgWg_CP0vFnFfozrst-9Aomwiow@mail.gmail.com> <m3egocg9si.fsf@carbon.jhcloos.org> <CABkgnnWg_5GTayp2BVPnJZKDKS50a=kHZRbkJ32qOWJxoN3wwQ@mail.gmail.com>
Date: Wed, 25 Mar 2015 17:03:10 -0500
Message-ID: <CAL02cgR+iY_qSpMMH1eH3Me=Oe8MimKev4WwCcXW1PuAUzhpOA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3437a9ef0cf0512241074
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/S2qRZa_lu8VvrpH0Z3yxvB7e3ro>
Cc: "acme@ietf.org" <acme@ietf.org>, Jacob Hoffman-Andrews <jsha@eff.org>, James Cloos <cloos@jhcloos.com>
Subject: Re: [Acme] IP addresses
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Mar 2015 22:03:14 -0000

On Wed, Mar 25, 2015 at 2:39 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 25 March 2015 at 14:24, James Cloos <cloos@jhcloos.com> wrote:
> > Would a >> name >-a/aaaa-> address >-ptr-> same_name << trip be enough?
>
> Not really.  The PTR records are populated dynamically, so there is no
> way to be sure that they are valid for the sort of duration that I
> think this group cares about.  (Basically, these can have the same
> sort of lifetime as a DHCP lease.)
>

And indeed, I have seen several deployments where the PTRs are dynamically
populated based on DHCP.