[DNSOP] RFC 6761 discussion (“special names”)
Tim Wicinski <tjw.ietf@gmail.com> Tue, 17 March 2015 21:40 UTC
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EA11A8907 for <dnsop@ietfa.amsl.com>; Tue, 17 Mar 2015 14:40:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.3
X-Spam-Level:
X-Spam-Status: No, score=-0.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 0gH5J4vTt_x0 for <dnsop@ietfa.amsl.com>; Tue, 17 Mar 2015 14:40:02 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 F2D821A8903 for <dnsop@ietf.org>; Tue, 17 Mar 2015 14:40:01 -0700 (PDT)
Received: by wixw10 with SMTP id w10so22610717wix.0 for <dnsop@ietf.org>; Tue, 17 Mar 2015 14:40:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:from:message-id:date:user-agent:mime-version :content-type:content-transfer-encoding; bh=9BlgUz21+CnroJZ/VBerpx2ZXTQpYMzdT1d2OGWzqB8=; b=OGoZBYjLmHpz+ulHnBd5oNeriPxU9H07DLaqw7c1+0YrFVdDEw7q/OUU0Xmmiyd6Ar wx8vWyCiI4kGQuvI3eZYXfpGbSCaHM8g0f0IE24JgxFdLRXhRJNT66ZRB7L6vPoNVj45 aYEpYVg1hbnQxPxf3Vc15rBaPqfrpCwvusToylNck9xRTLXCciwkow4LkPFmKXT9qKue 26OW2Ci4P3tY/XT4g58wjVacjgaAMRtqa5mP30kfUwuROAkcLK4LyjTVUHAsN/sh7Iwz aKJhVZgQP8ymRTtE/4HABZppV++diAM3IF1TG97FxC+Yyg2BfTEGne3gKwYMmV2tgdiI mW/Q==
X-Received: by 10.180.93.165 with SMTP id cv5mr1157097wib.51.1426628399129; Tue, 17 Mar 2015 14:39:59 -0700 (PDT)
Received: from feather.local (host-46-255-152-114.bitbuzzdsl.com. [46.255.152.114]) by mx.google.com with ESMTPSA id ga8sm345443wib.11.2015.03.17.14.39.49 for <dnsop@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Mar 2015 14:39:57 -0700 (PDT)
To: dnsop <dnsop@ietf.org>
From: Tim Wicinski <tjw.ietf@gmail.com>
message-id: <55089F07.5020200@gmail.com>
Date: Tue, 17 Mar 2015 21:39:19 +0000
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0a2
mime-version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/2RfDOgHZF0CS63iap7ZfZn1mdzI>
Subject: [DNSOP] RFC 6761 discussion (“special names”)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 21:40:03 -0000
All, We have two different drafts which have asked for time in Dallas, and a few more that have not. We've slotted some time for the discussion, but once again we have a packed agenda and limited time to discuss either the drafts or the implications of widening use of RFC 6761. If anyone remembers, we began this discussion at IETF 89 (London) a little over a year ago. The main issue at the time was the lack of charter for DNSOP to tackle the problem, which we went off and solved. The WG has several documents that we need to spend time in Dallas moving towards completion. But we also believe the RFC 6761 drafts should not be given short shrift. Accordingly, we are tentatively planning a Virtual Interim Meeting to dive a little deeper on the special names drafts, including possible architectural implications of the apparent increase in interest in RFC 6761, as we attempt to muddle through the questions we’ve seen and the ones we anticipate. We're soliciting feedback on this idea. The tentative date based on IETF guidelines would be the week of April 20th. Thanks tim suzanne
- [DNSOP] RFC 6761 discussion (“special names”) Tim Wicinski
- Re: [DNSOP] RFC 6761 discussion (“special names”) Tim Wicinski
- Re: [DNSOP] RFC 6761 discussion (“special names”) hellekin
- Re: [DNSOP] RFC 6761 discussion (“special names”) Suzanne Woolf
- Re: [DNSOP] RFC 6761 discussion (“special names”) hellekin
- Re: [DNSOP] RFC 6761 discussion (“special names”) Jaap Akkerhuis
- Re: [DNSOP] RFC 6761 discussion (“special names”) Paul Hoffman
- Re: [DNSOP] RFC 6761 discussion (“special names”) Jaap Akkerhuis
- Re: [DNSOP] RFC 6761 discussion (“special names”) Ted Lemon
- Re: [DNSOP] RFC 6761 discussion (“special names”) hellekin
- Re: [DNSOP] RFC 6761 discussion (“special names”) Suzanne Woolf
- Re: [DNSOP] RFC 6761 discussion (“special names”) Edward Lewis