Re: [DNSOP] back to: Some distinctions and a request

Robert Edmonds <edmonds@mycre.ws> Thu, 02 July 2015 23:44 UTC

Return-Path: <edmonds@mycre.ws>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD3631ACE0F for <dnsop@ietfa.amsl.com>; Thu, 2 Jul 2015 16:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aBQZUpfk4Tex for <dnsop@ietfa.amsl.com>; Thu, 2 Jul 2015 16:44:24 -0700 (PDT)
Received: from chase.mycre.ws (chase.mycre.ws [70.89.251.89]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C4771ACE0C for <dnsop@ietf.org>; Thu, 2 Jul 2015 16:44:24 -0700 (PDT)
Received: by chase.mycre.ws (Postfix, from userid 1000) id 6A1B51C44966; Thu, 2 Jul 2015 19:44:23 -0400 (EDT)
Date: Thu, 02 Jul 2015 19:44:23 -0400
From: Robert Edmonds <edmonds@mycre.ws>
To: manning <bmanning@karoshi.com>
Message-ID: <20150702234423.GB23022@mycre.ws>
References: <6CB05D82CE245B4083BBF3B97E2ED470C27498@ait-pex01mbx01.win.dtu.dk> <D1BAA21E.CA2E%edward.lewis@icann.org> <6CB05D82CE245B4083BBF3B97E2ED470C2759F@ait-pex01mbx01.win.dtu.dk> <6CB05D82CE245B4083BBF3B97E2ED470C275B2@ait-pex01mbx01.win.dtu.dk> <E225C721-7279-4053-97A2-2D63A155DA14@karoshi.com> <6CB05D82CE245B4083BBF3B97E2ED470C27602@ait-pex01mbx01.win.dtu.dk> <88E49F4B-64BD-4832-BD02-D1A882874E92@karoshi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <88E49F4B-64BD-4832-BD02-D1A882874E92@karoshi.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/sFwaiDapqbO5yFGS0ERr1Aq2-fA>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] back to: Some distinctions and a request
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2015 23:44:25 -0000

manning wrote:
> Hum…   “domain-looking-string” …  Per RFC 1945, we read:
> "3.2.2 http URL
> 
> 
>    The "http" scheme is used to locate network resources via the HTTP
>    protocol. This section defines the scheme-specific syntax and
>    semantics for http URLs.
> 
>        http_URL       = "http:" "//" host [ ":" port ] [ abs_path ]
> 
>        host           = <A legal Internet host domain name
>                          or IP address (in dotted-decimal form),
>                          as defined by 
> Section 2.1 of RFC 1123
> >
> 
>        port           = *DIGIT”
> 
> So then the question on the table is,  What is a “legal host domain name”?   RFC 1123, using SMTP as the example, says:
> 
> "5.3.5  Domain Name Support
> 
>          SMTP implementations MUST use the mechanism defined in 
>          Section 6.1 for mapping between domain names and IP addresses.  This
>          means that every Internet SMTP MUST include support for the
>          Internet DNS.”
> 
> This STRONGLY suggests that “domain-looking-string” is , in fact,  a host that is identified using the Internet DNS.

Have a look at the later HTTP/1.1 RFCs (7230) and the URI generic syntax
RFC (3986).  RFC 7230 defines http URIs, but it relies on the URI
generic syntax (RFC 3986) to define "uri-host"'s, and that specification
explicitly declines to require that "domain-looking-strings" be Internet
DNS names:

3.2.2.  Host

   [...]

   This specification does not mandate a particular registered name
   lookup technology and therefore does not restrict the syntax of reg-
   name beyond what is necessary for interoperability.  Instead, it
   delegates the issue of registered name syntax conformance to the
   operating system of each application performing URI resolution, and
   that operating system decides what it will allow for the purpose of
   host identification.  A URI resolution implementation might use DNS,
   host tables, yellow pages, NetInfo, WINS, or any other system for
   lookup of registered names.  However, a globally scoped naming
   system, such as DNS fully qualified domain names, is necessary for
   URIs intended to have global scope.  URI producers should use names
   that conform to the DNS syntax, even when use of DNS is not
   immediately apparent, and should limit these names to no more than
   255 characters in length.

   [...]

-- 
Robert Edmonds