IETF Logo Mail Archive

Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt

Ray Bellis <ray@bellis.me.uk> Tue, 05 March 2019 09:27 UTC

Return-Path: <ray@bellis.me.uk>
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 6425312785F for <dnsop@ietfa.amsl.com>; Tue, 5 Mar 2019 01:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=portfast.net
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 fXSB9Yf2fOrB for <dnsop@ietfa.amsl.com>; Tue, 5 Mar 2019 01:27:21 -0800 (PST)
Received: from mail.portfast.net (mail.portfast.net [IPv6:2a03:9800:20:1::2]) (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 12C891276D0 for <dnsop@ietf.org>; Tue, 5 Mar 2019 01:27:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=portfast.net; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=WdbcbveUzBB6aINZuiLn7y+D/Wzouy6Drjc6K2hPoOI=; b=RwxILkItoYr8Hizd1TBQTSi5sc A6AvpT5JDPcTd0dI6hW7vVxEjtD1UIxVyYmT6c06zWelZUIEl39vS43VHuRvIiyYVtVsj1wHkykVp Rpz3dB12xIY+7JrWSB1tLPwB3qj8hH/2vaD8FjRZYLzI78Z2hTRIBWObKU9GtXzD71TU=;
Received: from [88.212.170.147] (port=64808 helo=Rays-MacBook-Pro.local) by mail.portfast.net ([188.246.200.9]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1h16M2-0001rQ-QA (Exim 4.89) for dnsop@ietf.org (return-path <ray@bellis.me.uk>); Tue, 05 Mar 2019 09:27:19 +0000
To: dnsop@ietf.org
References: <155171606493.5281.3957934874516100450.idtracker@ietfa.amsl.com> <5c3cc3f9-2225-9077-fb9e-0fb940bd1c1b@isc.org> <accf01be-9813-c708-073e-e5f22948ccbc@time-travellers.org>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <a3dd345a-3be5-9a40-e3e6-f6a29d04fcd4@bellis.me.uk>
Date: Tue, 05 Mar 2019 09:27:18 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <accf01be-9813-c708-073e-e5f22948ccbc@time-travellers.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/BHpWEX6VLdOMjn4RbKjGhJD2HUs>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt
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: Tue, 05 Mar 2019 09:27:23 -0000


On 05/03/2019 09:11, Shane Kerr wrote:

> I don't see much value in this beyond the already-standardized EDNS 
> range reserved for local/experimental use.

Shane,

The additional value is being able to use the feature in off-the-shelf 
DNS software.

Stretching the analogy to BGP communities slightly (the authors had 
already discussed this internally when working on the draft, and Wes has 
made that comparison too):

Folks *could* have decided to use some unassigned BGP Path attribute 
value to carry similar information, but each implementor would have had 
their own special version of it.   Making it _standardised_ is what 
allows support to be ubiquitous (and interoperable).

Ray

v2.23.0 | Report a Bug | By Email