[core] coaps+jpy scheme

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 02 August 2022 15:05 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 CB875C14CF14; Tue, 2 Aug 2022 08:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.006
X-Spam-Level:
X-Spam-Status: No, score=-4.006 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rEaJ8VFXvMn; Tue, 2 Aug 2022 08:05:14 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0A58C14F74B; Tue, 2 Aug 2022 08:05:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 307DB38994; Tue, 2 Aug 2022 11:23:51 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QRAh_26ghc-V; Tue, 2 Aug 2022 11:23:50 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8174F38993; Tue, 2 Aug 2022 11:23:50 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1659453830; bh=lR0hXHZ4oMP810TdbCKY85f069dv/JX1rAZQMVfCiaw=; h=From:To:cc:Subject:Date:From; b=Xme4wPrq2vXRx68IeDFnGogBCBYnBW0Pw1+Bgl3es6bXR5bcHLF3syLvJ66t2oUhA cT+iLD1uhBAieqnk3wTmzwjEqaJJVlC+Fc9Xbi68jAkCPi3vIhCrdxrSoW44hfaTAI mUZ4tOpQ/8MYE9UNE59aa+QWXV5vF6XsArSMUInShWuszJ7luwfOMv1DFFXfsDcPcJ x6O1vnodmbmYV8Ey+TnEwuJDTznWv7IEUHiId0ZUlnnzeJx4SY1THwfIFJ85BrpSvJ vYDSVqD39eE1MaUOcS+CwHhFE3qwKjiBIJgdQ+BwPNRVVGThdXKmjjAg5IyAwY6N1D QLQAiQ2FUEhKQ==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B9D5115B; Tue, 2 Aug 2022 11:05:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima@ietf.org, core@ietf.org
cc: Christian Amsüss <christian@amsuess.com>
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 02 Aug 2022 11:05:08 -0400
Message-ID: <5117.1659452708@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/cKcfSdhwxN4pDaVxq5AjKGpliSE>
Subject: [core] coaps+jpy scheme
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 02 Aug 2022 15:05:18 -0000

As per the discussion at IETF114
   (watch it again at: https://youtu.be/UIsxhY73QrA?t=4951 1:37 for exact spot)

https://github.com/anima-wg/constrained-join-proxy/pull/38/files is a
registration for the coaps+jpy:// scheme.

====

I noticed draft-ietf-core-transport-indication, which I had never read and
wondered if it could help instead, and concluded that it won't, but I started
a discussion with Christian, and he had an alternate suggestion/hack.

That since the IP address is largely useless, and I don't think we specified
a clear URI-Host: for the pledge to use, and so like RFC9031, that we could
define something like jpy.arpa.  That's clearly a hack though, just a hack of
a different type.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide