IETF Logo Mail Archive

Re: [core] Link-format to DNS-SD mapping: URI rt values

Michael Koster <michaeljohnkoster@gmail.com> Mon, 16 July 2018 21:30 UTC

Return-Path: <michaeljohnkoster@gmail.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 B700513127F for <core@ietfa.amsl.com>; Mon, 16 Jul 2018 14:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aNDc8S1l6ppI for <core@ietfa.amsl.com>; Mon, 16 Jul 2018 14:30:49 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 51392131236 for <core@ietf.org>; Mon, 16 Jul 2018 14:30:49 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id y10-v6so24429338ioa.10 for <core@ietf.org>; Mon, 16 Jul 2018 14:30:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zZFP8uzI9KQBaPCERqDbcyBsq91zKxIgrBCxl+kNNY0=; b=aR5u6uNnOPbxFfk5sGP8tLt3d+GMmeP56+HYAHRhFT4+uX3jKMi4nkp0kiB4HIUDdA MlvDkoQ4R6aTpGXP0TcnHDhnF55vHXLENXed8X3uNlqmdeizNAUMjPkKtbr2yLLW96eq ThBg9A9LzpMa4N0CZvRz50Sc7O50JopJrz+uXqYvqMVQoYDSj8e0efgdlh6gPRLLRUwl BXSi0AZlvUe0E7qhIZZkwsfzlkhx+RTJVWnwy2W8us9JpOXCIDpjeehRvH/wQE9+XYCt CUec4WnVEQAA30B61Qn15J4kfSyg2bZBYj+k1dGIYpWrI4wbCzIEMhfsAQff7sQeKLkO cWyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zZFP8uzI9KQBaPCERqDbcyBsq91zKxIgrBCxl+kNNY0=; b=M7jxWCZg4HOISyePa4a+y9sopk/QJdp1MrSzyAG9sgEDFUfGqc16CuAboTJSsEcPIF zoWYqFX0F8uQRJjzyigtwI+WsrjggWpZQWz372ebFsGfW11bBNvoScuYT1+D/rBZ/EAq iNa7KLAOtticAac6khjh3t2CU3zHk04+LwOEZG3ycXjQXnmdfQjFftPmdl8c31E+PwiK QAfo2W/DHmc6HC7SK4K4DtzR+CW8w7P0ofui1UQ8EvasBqS6+LMqaUQxI2yJo6AAG0+W 9RSid3IWgHzpF6++8PVZf3g331obN+xtVSRp/72ON3uEmFP996ZF8+hYuKtRQFnk9WRG Y2rw==
X-Gm-Message-State: AOUpUlG17LMvRRlSMXpVa18bzgjxU95HyvYuKpy8O8cLcUoZnHnHy8vI 7dlUHPBr5tSuRsfS0CSezWvcEP45
X-Google-Smtp-Source: AAOMgpdro01P2Y6MfYDavOqG4jisVCeRSCCy/sybULLLIpXKPGbmnTglQaWYd1027B9eZqKGgUGTwA==
X-Received: by 2002:a6b:9303:: with SMTP id v3-v6mr7192891iod.264.1531776648705; Mon, 16 Jul 2018 14:30:48 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:128:e9f7:c25f:62ef:1280? ([2001:67c:370:128:e9f7:c25f:62ef:1280]) by smtp.gmail.com with ESMTPSA id z195-v6sm3713602ioe.38.2018.07.16.14.30.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Jul 2018 14:30:47 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Michael Koster <michaeljohnkoster@gmail.com>
In-Reply-To: <DM5PR2101MB0805A11EFC50C8329FD31FECA35D0@DM5PR2101MB0805.namprd21.prod.outlook.com>
Date: Mon, 16 Jul 2018 17:30:46 -0400
Cc: "core@ietf.org" <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <132BF0EA-F284-4857-BE93-2A04608D828A@gmail.com>
References: <DM5PR2101MB0805A11EFC50C8329FD31FECA35D0@DM5PR2101MB0805.namprd21.prod.outlook.com>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/hnGBM4sMePDhKPc9It6Ncv8l1-U>
Subject: Re: [core] Link-format to DNS-SD mapping: URI rt values
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.27
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: Mon, 16 Jul 2018 21:31:01 -0000

Or the URN form may also be used, e.g. "rt=urn:myorg:sensor:temperature" which can enable an organization to manage its own namespace

> On Jul 16, 2018, at 5:09 PM, Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org> wrote:
> 
> Just to put to the list the question I raised in the meeting:
> RFC 6690 section 3.1 allows rt values to be either:
> a) IANA-assigned, OR
> b) URIs (e.g., "http://sweet.jpl.nasa.gov/2.0/phys.owl#Temperature" 
>    in the example in the RFC)
> 
> The presentation today only mentioned (a).
> The question was: how would you handle (b)?
> 
> Dave
> 
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core

v2.23.0 | Report a Bug | By Email