IETF Logo Mail Archive

Re: [Add] FW: New Version Notification for draft-mglt-add-rdp-00.txt

Paul Wouters <paul@nohats.ca> Mon, 09 March 2020 15:58 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A19C3A12BD for <add@ietfa.amsl.com>; Mon, 9 Mar 2020 08:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 Sp7vk2Wvdujx for <add@ietfa.amsl.com>; Mon, 9 Mar 2020 08:58:10 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 475563A12BB for <add@ietf.org>; Mon, 9 Mar 2020 08:58:10 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 48bjYX3hhLzKhH; Mon, 9 Mar 2020 16:58:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1583769488; bh=sUYXMwuX9jLm1c7+DWUnDXrO4x2yGddiVDJ+rF7s5K4=; h=From:Subject:Date:References:Cc:In-Reply-To:To; b=AD2fJBlnnFz7QDaySTzFmOvtSx+bVeCFXNa/GZa+jOWLootCdp3C1jl35s7LNuYwM 5DO5p+7/2/uAK9S4ztttFSKm3I6W5qBxYqGS1Vzw6IYqGfk9PEg90UFMhE9own8/rB Fs8zEPE0mBfNei3RlQn+oRpxPyIwSb1BLT5ytmF8=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id GVbcsjgG-xb2; Mon, 9 Mar 2020 16:58:06 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 9 Mar 2020 16:58:06 +0100 (CET)
Received: from [193.111.228.74] (unknown [193.111.228.74]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 906886020D9F; Mon, 9 Mar 2020 11:58:05 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Mon, 09 Mar 2020 11:57:48 -0400
Message-Id: <0D830DDA-79E5-4913-8AA0-A8592122728D@nohats.ca>
References: <SN6PR15MB2302DA881EF98391B03EF5EBE3FE0@SN6PR15MB2302.namprd15.prod.outlook.com>
Cc: ADD Mailing list <add@ietf.org>
In-Reply-To: <SN6PR15MB2302DA881EF98391B03EF5EBE3FE0@SN6PR15MB2302.namprd15.prod.outlook.com>
To: Daniel Migault <daniel.migault=40ericsson.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/k_BVLqTs6rk3ZI75-vjLs-CVG0o>
Subject: Re: [Add] FW: New Version Notification for draft-mglt-add-rdp-00.txt
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Mar 2020 15:58:12 -0000


Sent from my iPhone

> On Mar 9, 2020, at 11:39, Daniel Migault <daniel.migault=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Hi, 
> 
> Please find a description of the DNS Resolver Discovery Protocol (RDP).

You cannot really call it RDP. That is already in use for Remote Desktop Protocol. It would be way too confusing.

Paul

v2.23.0 | Report a Bug | By Email