IETF Logo Mail Archive

Re: [dispatch] New Version Notification - draft-hardie-dispatch-rfc3405-update-04.txt

Timothy Mcsweeney <tim@dropnumber.com> Thu, 15 October 2020 19:31 UTC

Return-Path: <tim@dropnumber.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95153A1375; Thu, 15 Oct 2020 12:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.795
X-Spam-Level:
X-Spam-Status: No, score=-1.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 RUFIQTOECric; Thu, 15 Oct 2020 12:31:22 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197]) (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 4368B3A1362; Thu, 15 Oct 2020 12:31:22 -0700 (PDT)
Received: from oxusgaltgw01.schlund.de ([10.72.72.47]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Lan5K-1k0NjU3nCK-00kRl6; Thu, 15 Oct 2020 21:31:20 +0200
Date: Thu, 15 Oct 2020 15:31:20 -0400
From: Timothy Mcsweeney <tim@dropnumber.com>
To: internet-drafts@ietf.org, barryleiba@gmail.com, dispatch@ietf.org, spencerdawkins.ietf@gmail.com
Message-ID: <695687617.30027.1602790280802@email.ionos.com>
In-Reply-To: <160278762498.6279.12834691771462136672@ietfa.amsl.com>
References: <160278762498.6279.12834691771462136672@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Normal
X-Mailer: Open-Xchange Mailer v7.10.3-Rev23
X-Originating-Client: open-xchange-appsuite
X-Provags-ID: V03:K1:o3Ssoging3TvEQYHGst3oG8mab5bziAU9ZNESZzOBh1kBksFOSG yvxQ4VnxMwpM8qMg1XY2wlCrWv9sKq45KEcbGXfRPfjTUXRaW7UEyVbUW5Ua+E+USHHmleH jPtprG5ko+/hNqDAPE0L6xa1hPc5Y0lAkqLVoExF0bW3qrOPt9SVaDQtoY0HvnZINqmflV/ JRD2ero4pDy7o5HWOVn5w==
X-UI-Out-Filterresults: notjunk:1;V03:K0:CAPnUAJ29O0=:GvVPephaJCW8PrIjki3ZVj RVGDKlEi7hrP+FH/nXUhDP31m5iQ+0DSrjS6w+VYasNzeNQxu4Kx/Dg2+JAmG3aK/OD95ESlm 7kJUQV5PQSL+i4CzwgsqxQHXdy5CnM2U64GjXQmwzdOAKHQmL7A8V+yBlYtOv1Pwld1gWTF6V 3iDpyiYrvpkSrCzafXmZpCVUrGwKPYFoIGq/WrnM8X6G0TZBjlWC+C2oMu2xc71E3gJIB6KKk jsH+95/UrKCj0k4rFyP84BI+teydo3++xamMUDBlOsWq2tKIre+APx9f5Ssi7qpkQJ8Ho5utG cgjnWgTnI9CWuIGxZeAHkhbXSX4MYA+5jxXlnVaMYTnk0Kdh+AzCBNz9NswRW+dc4+RW8K40w RhW+ybnlofzu39uH0CgrOmzcffTS1OJO9XQH09ksV1dWdbMGpR1IZEqYo8x789TlYfuwynQHt MgRxPNBGVw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/cYBVAvclJWjN0dqAyqfQHRZID6U>
Subject: Re: [dispatch] New Version Notification - draft-hardie-dispatch-rfc3405-update-04.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 19:31:30 -0000

I would like to see the following changes made to this version (-04) because it does not specify what will be exactly will be reviewed:

2. Updated Requirements
This document removes and replaces the normative requirements from sections 3.1.1
and section 3.1.2 of RFC3405 with:
The registration of a NAPTR record for a URI scheme MUST NOT precede registration of that scheme.  IANA will review the request against for
  1. correctness and technical soundness (eg. valid databases, service parameters etc.) and
  2. consistency with the published URI resolution application specification [RFC3404], and
  3. to ensure that the NAPTR record for a DNS-based URI does not delegate resolution of the URI to a party other than the holder of the DNS name. This last rule is to insure that a given URI's resolution hint doesn't hijack (inadvertently or otherwise) network traffic for a given domain.

3. IANA Considerations

This update does not change the IANA submission procedure in Section 5 of RFC 3405.


_______________________________________________
dispatch mailing list

v2.37.1 | Report a Bug | By Email | System Status