From dev-return-14901-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Mon Feb 14 12:48:28 2011 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 53242 invoked from network); 14 Feb 2011 12:48:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Feb 2011 12:48:28 -0000 Received: (qmail 63541 invoked by uid 500); 14 Feb 2011 12:48:28 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 63160 invoked by uid 500); 14 Feb 2011 12:48:25 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 62951 invoked by uid 99); 14 Feb 2011 12:48:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 12:48:24 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of robert.newson@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Feb 2011 12:48:17 +0000 Received: by bwz4 with SMTP id 4so5162961bwz.11 for ; Mon, 14 Feb 2011 04:47:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=BkAXM2EYNwI//4nwgqmtHu6ywsF3Dg74wC0BmuHg+gs=; b=g+veofmJ/+K7eBlrlE7MObqBnyvctUau0DSBvudYCMxS7EoSonUyz39dis/gSEkdwu rCrTEe5GY1QGAz2IiGCbKaZn8ucw8h8pVi25FHksSYsq929ZlusTHlytRRNuzLyJ3JuA uAxyLgQn9gChN/MdzlfWqj7mkS9s6+jbCxInc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Mrxcj8hm1FXK1U+bWWmylQ5iEwxxqRcjvbHDm2wIBVIIFir3N16sAwv4SNFaCEiCjX 3C8EZ0qaGgsB0XU3u+8oBkfioWxz324JWyldJiHYI6m+vUYkJwi9uHF8MKtSWzKK36n/ HYo/fnvYS3YUMo1xGt1pcW/m78/P3WWT9S3Vg= MIME-Version: 1.0 Received: by 10.204.57.197 with SMTP id d5mr3351189bkh.63.1297687676853; Mon, 14 Feb 2011 04:47:56 -0800 (PST) Received: by 10.204.113.146 with HTTP; Mon, 14 Feb 2011 04:47:56 -0800 (PST) In-Reply-To: <4A06F9A7-F870-42EC-AE44-EDD1F4A394B0@apache.org> References: <4A06F9A7-F870-42EC-AE44-EDD1F4A394B0@apache.org> Date: Mon, 14 Feb 2011 12:47:56 +0000 Message-ID: Subject: Re: [IANA #411617] Application for port-number: couchdbs From: Robert Newson To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Sorry Noah, meant to reply earlier. If the argument that allows 80/443 for http/https is no longer enough, I don't see how we'll get this registration approved. Is it possible to listen on one port and handle http and https correctly? I didn't think so, hence it listens on a different port. B. On 14 February 2011 12:30, Noah Slater wrote: > Anyone? > > On 8 Feb 2011, at 20:53, Noah Slater wrote: > >> Help appreciated. >> >> He raises a good point though, as those links don't work now. >> >> I'm not sure what level of description they require. >> >> Probably nothing more than a handful of paragraphs to explain how CouchD= B is a special use-case for HTTP. In the original submission for TCP 5984, = I pointed out that TCP 80 is specifically reserved for "World Wide Web HTTP= ." My argument hinged on the fact that CouchDB is expected to be run on a m= achine (perhaps on a private interface) that is simultaneously serving up t= his kind of "World Wide Web" traffic, and so this warranted a separate port= . >> >> Begin forwarded message: >> >>> Dear Noah Slater: >>> >>> Thank you for your patience while your application was being reviewed. >>> The expert review team still has questions for clarifications with resp= ect >>> to your request. >>> >>> - You provided the following for couchdb (#5984): >>> >>> http://www.couchdbwiki.com/index.php?title=3DCouchDb_Quick_Overview >>> http://www.couchdbwiki.com/index.php?title=3DTechnical_Overview >>> http://www.couchdbwiki.com/index.php?title=3DHTTP_REST_API >>> >>> Do you have an updated description of the protocol CouchDB over TLS/SSL= ? >>> >>> - It will also be useful to include a fundamental description in >>> the template itself rather than points. =A0URLs are useful, but they mi= ght >>> not be reachable in the future. =A0IESG requires that the technical >>> description shall be documented in the application for future >>> reference purposes. >>> >>> If we do not receive the information within 30 days (i.e. 2011-03-10), >>> your request will be resolved without prejudice, as a matter of >>> administrative procedure. >> > >