Re: [core] exp parameter in rd-dns-sd

Christian Amsüss <christian@amsuess.com> Wed, 24 July 2019 12:58 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCCE4120071 for <core@ietfa.amsl.com>; Wed, 24 Jul 2019 05:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=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 SQfSe-SRoc0j for <core@ietfa.amsl.com>; Wed, 24 Jul 2019 05:58:30 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 148FB120058 for <core@ietf.org>; Wed, 24 Jul 2019 05:58:29 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id EB52445744; Wed, 24 Jul 2019 14:58:27 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id E242426; Wed, 24 Jul 2019 14:58:26 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2001:67c:370:128:7b7f:12ad:c17b:ddf6]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id B277074; Wed, 24 Jul 2019 14:58:25 +0200 (CEST)
Received: (nullmailer pid 26870 invoked by uid 1000); Wed, 24 Jul 2019 12:58:07 -0000
Date: Wed, 24 Jul 2019 08:58:07 -0400
From: Christian Amsüss <christian@amsuess.com>
To: consultancy@vanderstok.org
Cc: Core <core@ietf.org>
Message-ID: <20190724125805.GA23004@hephaistos.amsuess.com>
References: <8cf3459e87b92008d9a24e3656e60b57@bbhmail.nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD"
Content-Disposition: inline
In-Reply-To: <8cf3459e87b92008d9a24e3656e60b57@bbhmail.nl>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/PJUZe2nvZmWrhSpaV2L_eLJbbxk>
Subject: Re: [core] exp parameter in rd-dns-sd
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2019 12:58:32 -0000

> During the meeting it was remarked that the presence of the exp
> parameter implies the existence of the st parameter
> and vice-versa.

There was the idea around years ago that exp would also be considered by
"other export mechanisms" that take data from the RD. If other export
mechanisms ever show up, they can define their own st= equivalent, or
describe a more generic "may export mechanism". (So far none have shown
up).

I agree exp can just be removed from RD-DNS-SD.

BR
c

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom