IETF Logo Mail Archive

Re: [Uri-review] Registration request for smtp:// and submit:// URI schemes (draft-melnikov-smime-msa-to-mda-04)

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 02 April 2014 06:05 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063F91A0140; Tue, 1 Apr 2014 23:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level:
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=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 IXhk2lLNvLkZ; Tue, 1 Apr 2014 23:05:06 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6681A0137; Tue, 1 Apr 2014 23:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1396418702; d=isode.com; s=selector; i=@isode.com; bh=Z/qqz05MavdacZXkFDe8jpJgfeqfx1jeUl4as3Vg/Ko=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=f5mzEtvbldX9O7Bh0VxfAoRTekgihQJ15VtmfkYbE4x3R2BH0h2smkFBjxCKJ2Ks9z431F xvbCxz1bk84vLq1n8OVAD8Le/A2vDB3QULP31TsMTeANaBjnvqE/SnnVfX0N81wFz8s+7P Kmb395dmtVtNJNp5EIYGI/ipBrp5atQ=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <UzuohwAOZrwB@statler.isode.com>; Wed, 2 Apr 2014 07:05:01 +0100
X-SMTP-Protocol-Errors: PIPELINING
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (11B651)
In-Reply-To: <533B6487.10700@it.aoyama.ac.jp>
Date: Wed, 02 Apr 2014 07:10:10 +0100
Message-Id: <9D657332-EF6C-4B51-AF3F-899449EF7700@isode.com>
References: <5336F686.7060308@isode.com> <451cd52e77fb4baf9f736e063eb872ad@BY2PR03MB412.namprd03.prod.outlook.com> <BE559B6A-3A33-450B-9526-E0F603A5CADB@isode.com> <63b3c4fad07742529b5ac4dfc0a0f306@DM2PR03MB414.namprd03.prod.outlook.com> <533B6487.10700@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/uri-review/JvdMaCvPDT4ewDTOos7V65FTJy8
Cc: "uri-review@ietf.org" <uri-review@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [Uri-review] Registration request for smtp:// and submit:// URI schemes (draft-melnikov-smime-msa-to-mda-04)
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review/>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 06:05:10 -0000

Hi Martin,

> On 2 Apr 2014, at 02:14, "Martin J. Dürst" <duerst@it.aoyama.ac.jp> wrote:
> 
>> On 2014/04/02 02:33, Dave Thaler wrote:
>> Alexey Melnikov wrote:
>>>> My feedback is that the name "submit" is not a good name for the proposed
> 
>>>> "smtpsubmit" or similar would be much more appropriate.
>>> 
>>> I would rather use the same label as used by DNS SRV for the same service:
>>> "submission". (I think keeping them different would be a bad thing.). Thoughts?
> 
> If the SRV service name is "submission", and the proposed scheme name is "submit", aren't these two *different* labels?

I am suggesting of making them the same. I thought they were...
> 
>> I didn't know about the SRV service type before this, but yes that sounds like a
>> reasonable goal.
>> 
>> I'm thinking it would be good to add a sentence about this case
>> (service names and URI scheme names SHOULD be the same, when there exists
>> a 1:1 correspondence) to draft-ietf-appsawg-uri-scheme-reg.  Does that
>> sound reasonable?
> 
> Yes. I'm not sure it needs to be a SHOULD, something like "consider to make this the same as...".

v2.23.0 | Report a Bug | By Email