Re: [DNSOP] draft-ietf-dnsop-attrleaf vs. RFC7553

"John Levine" <johnl@taugh.com> Thu, 07 February 2019 19:29 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6BF612F1A5 for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 11:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=bpb8gcnb; dkim=pass (1536-bit key) header.d=taugh.com header.b=ODmTOp2T
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 GAXfrCBVORvK for <dnsop@ietfa.amsl.com>; Thu, 7 Feb 2019 11:29:04 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C99D12E036 for <dnsop@ietf.org>; Thu, 7 Feb 2019 11:29:04 -0800 (PST)
Received: (qmail 39734 invoked from network); 7 Feb 2019 19:29:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9b34.5c5c86ff.k1902; bh=ynzDBKIIQkI8olN9Vuh3kva4dNU131rNFM3CR5qawm8=; b=bpb8gcnbLNqGaWh1UO4K4w3UHrCO2E1jY3qbic9qJxjQr1yco1zegFoGFb8kSeTCyAFdtjzb3QD70lvSPV+xAYpgZbuToZzwO2N3wcoiR93PfVweTKeS1wLMrzy7CdOR8JMmEdB3HHYgbjauS7Vp2zyueM6ZiODBPHjiiRh4Hl7MxYPBGLv680hvPerHc7JGOrmgv9mgfZvd7Y+au5t6goroH3ohL+qN4L4auYpUNVfoy1+2PHxmQ6AXvlkZUl7P
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9b34.5c5c86ff.k1902; bh=ynzDBKIIQkI8olN9Vuh3kva4dNU131rNFM3CR5qawm8=; b=ODmTOp2TbfKaBPHKvJYNmSXy9YlrgIlLxOs3UQCYu5eEG6cX6rNwkzAwCkrw9TAZ6T+Dkprs4pkyOF8RBBOiJwrSoxyFxcQk093qQbOxGaW8K1qz6aOrJ5aknRAhSfRAlMIJX3plaH0ULs1Ahd6nIHXZo1NPcYezN0SHXm8w5p5Y3Y7sWFvlMLNGm7DHSZNVhrjjt1V58WXPB/QfF+aJ+QZfgXf836Lz8yR58TJXOiWoSHLRlqZB9+OxmgIWwmDi
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 07 Feb 2019 19:29:03 -0000
Received: by ary.qy (Postfix, from userid 501) id 2BDB2200DF041A; Thu, 7 Feb 2019 14:29:02 -0500 (EST)
Date: 7 Feb 2019 14:29:02 -0500
Message-Id: <20190207192903.2BDB2200DF041A@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dnsop@ietf.org
Cc: alexander.mayrhofer@nic.at
In-Reply-To: <19F54F2956911544A32543B8A9BDE0759FBCD40B@NICS-EXCH2.sbg.nic.at>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uJO93PRoCCDXe_XFYz0nBPXEtpQ>
Subject: Re: [DNSOP] draft-ietf-dnsop-attrleaf vs. RFC7553
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 19:29:06 -0000

In article <19F54F2956911544A32543B8A9BDE0759FBCD40B@NICS-EXCH2.sbg.nic.at> you write:
>I'm turning my head around an issue around the attrleaf draft, and its connection with RFC7553 (the URI
>RRType). Im specifically wondering what the connection between the "service parameter" in RFC 7553 and the
>"Global Underscore Node Names" in draft-ietf-dnsop-attrleaf is. 

Dave moved the duct tape patching up all the places that defined
underscored names to draft-ietf-dnsop-attrleaf-fix.

See sections 2.3 and 2.3 for URI records.

It's still a draft so if it seems wrong, send text.

R's,
John

Linguistic note: people from the antipodes should read "duct tape"
as "number 8 wire"