Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt

Mats Dufberg <> Thu, 26 July 2018 08:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C15CE131071 for <>; Thu, 26 Jul 2018 01:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Status: No, score=-4.3 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gMfJcdIcenhH for <>; Thu, 26 Jul 2018 01:45:42 -0700 (PDT)
Received: from ( [IPv6:2001:67c:124c:2007::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6E9A0130FC4 for <>; Thu, 26 Jul 2018 01:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=iis2015; h=received:received:received:from:to:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:user-agent: x-ms-exchange-messagesentrepresentingtype: x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type: content-id:content-transfer-encoding:mime-version; bh=mD8H8jgqBqZRZWswwv4xo2FB66S8bur9SRAyAhzL7+Y=; b=Dd56mvSY4+CXhWsWUIRoiT/w0eViiBvH50cpg7QESpBX13i0Tp+qjP24RikHmSYnFDnORtrdyx/YM N7iJEGO4Pemi0W55sot50velKQApThBLHIXycpeISojHDu8UwvurBMNjLaJQ19WAUtlKn+eAmkXMeK FkQsxcrKqqUhG9qI=
Received: from (unknown [2001:67c:124c:2043::25]) by (Halon) with ESMTPS id 44c47813-90b0-11e8-a624-00505682e997; Thu, 26 Jul 2018 08:45:37 +0000 (UTC)
Received: from (2001:67c:124c:2043::25) by (2001:67c:124c:2043::25) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 26 Jul 2018 10:45:37 +0200
Received: from ([fe80::681b:9cef:675b:d880]) by ([fe80::681b:9cef:675b:d880%14]) with mapi id 15.00.1347.000; Thu, 26 Jul 2018 10:45:37 +0200
From: Mats Dufberg <>
To: "" <>
Thread-Topic: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt
Date: Thu, 26 Jul 2018 08:45:37 +0000
Message-ID: <>
References: <> <> <> <> <pjaknq$1sdt$>
In-Reply-To: <pjaknq$1sdt$>
Accept-Language: en-US, sv-SE
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.f.0.180709
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2001:67c:124c:5124::1801]
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Jul 2018 08:45:46 -0000

I prefer a regex and I think that Dave's "_ta-.*" makes most sense. An explanation that it is a regex and that the exact format of the name is found in RFC 8145 is needed.


Mats Dufberg
DNS Specialist, IIS
Mobile: +46 73 065 3899

On 2018-07-25, 21:58, "DNSOP on behalf of John Levine" < on behalf of> wrote:

    In article <>,
    Dave Crocker  <> wrote:
    >On 7/25/2018 10:59 AM, Bob Harold wrote:
    >> Dot "." has special meaning in DNS, so I would prefer:
    >>  Â Â  _ta-*
    >> Not regex, but a common wildcard usage.
    I suppose.  A plausible actual regex would be
    which might be a bit dense.  That's not quite right because the
    numbers in the label have to be sorted, but there's no way to say that
    in a regex other than enumerating them which would be bulky.
    Whatever you do, please put include some text reminding people that it's
    a conceptual glob stype wildcard, not a DNS wildcard.
    John Levine,, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail.