Re: [ietf-smtp] [Proposal] 250-MARKDOWN

Viruthagiri Thirumavalavan <giri@dombox.org> Wed, 09 January 2019 07:55 UTC

Return-Path: <giri@dombox.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC98D130934 for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dombox.org
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 h3OSMAFuTlVv for <ietf-smtp@ietfa.amsl.com>; Tue, 8 Jan 2019 23:55:55 -0800 (PST)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41C7A128766 for <ietf-smtp@ietf.org>; Tue, 8 Jan 2019 23:55:55 -0800 (PST)
Received: by mail-yb1-xb29.google.com with SMTP id 2so2651375ybw.4 for <ietf-smtp@ietf.org>; Tue, 08 Jan 2019 23:55:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dombox.org; s=default; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=X/3bTJPhCxgGw95TII94x3/ekd1Z3ZW0wBnE90sn5AU=; b=gA81XPiqcQl8v066Yfk2zE6ZbGf+PFaoRMov7+9SgpaL2p7akhwiU34QNA2fA5HSmh TlwzjeHR4lB/Eah9JriBF3eqg4ibhLi4iFdKvHmwxo5kvVyeiKsNQ4DfL/CRp+93UnZj kVdBsTP7v2cxrylNSmPwR2EkJttktQyaPLu8Yr37JQQkb4hAAoOr9egm/3HSl6wi9yAw SYpyJVmD496H1/eHviw8kTCYP8xGhOk4L0wKfk2Vb04GX9sperqfUBQUUFOuDI1MjB6b XMMf9RegFqXdFFOv3ohJGFO5Nm0ZBAWkMtmD0Y2kNDLAd24f9+g7Fa2o1s6BetA95Hm4 8JVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=X/3bTJPhCxgGw95TII94x3/ekd1Z3ZW0wBnE90sn5AU=; b=HT4JBza2s6TVFP11w/YR5nvUUpsdFIdZIHVTYU82YmmPG0V2o4+5SKKziOh8KaKtDb 6gPdlVukTUDQt2pKR58+GVaEvitGBLLK6Xk5pgg9FqrYjFbCY6oa4iqujaCKcmDOVygM lXIbhFqUVjafgBbaLR7RXEDll2ZCb7NbKIZDYKPkzuRFOgjRliCMlLj/gRd8ZsJ4iwQl 2wcjAy+nfJgwhIYMTHmzWPr5rFxj5NgvqWR1KORvmguWUoo0fBfGroSSnVZlZkqOJZ34 CSBrH5/AKBJDQxp2utZ9K+TAQXeBcNwx/QmlL/hchOvnppCF1L/66VQ0CSn1WSKBAKhw QcWg==
X-Gm-Message-State: AJcUukflkdT09qwMreMjTzgonnj1PnH4chgA5jIQfxZkxZjGNC7zof6R pu8NMUpgedr30Aexi0eBJwpgcOmjnXTB27Nd9N+NRkPdNS4=
X-Google-Smtp-Source: ALg8bN5DU2A4F6wFeVCTnDZHhqTw2ImXoaEmt7w59dBbruzSYqtIcxFyKETapovwwV9FyNf93lgV1v1lPEGt8q/Ylu4=
X-Received: by 2002:a25:3303:: with SMTP id z3mr4631873ybz.368.1547020554261; Tue, 08 Jan 2019 23:55:54 -0800 (PST)
MIME-Version: 1.0
References: <CAOEezJRwe9iSbGyBfyHNPn8=2avo6bAoFY56++HLY5+FZHhWgw@mail.gmail.com> <144aafd5-7468-4d55-a7b7-bead5cc67e1e@email.android.com>
In-Reply-To: <144aafd5-7468-4d55-a7b7-bead5cc67e1e@email.android.com>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Wed, 09 Jan 2019 13:25:43 +0530
Message-ID: <CAOEezJTakEcxq7MtYXTjjRAPCM8uGcfzMUHetRPY6enn-Bb10w@mail.gmail.com>
To: Gilles Chehade <gilles@poolp.org>
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="00000000000098ef76057f01caac"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/ZDYy9kT_KFylL0nboDJoeHE4BMI>
Subject: Re: [ietf-smtp] [Proposal] 250-MARKDOWN
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2019 07:55:58 -0000

>
> After reading your proposal, I don't quite understand what it is about and
> what is expected from SMTP implementations.


I wanted to introduce the keyword "MARKDOWN" in the list of EHLO response.
So the client can understand and transfer the messages directly with
content type "text/markdown"

The content type is part of the message, not part of the protocol


I'm using the content type in the message right?

also your rationale seems to equate one SMTP session to one message but a
> single session may transport multiple messages with different messages with
> different content types.


Ok what am I missing here? When a server says that "I recognize markdown
format", then the client gonna send markdown messages as it is. I
understand a session can transport multiple messages. But why do you think
it won't work?

In my proposal, I provided content type in the message header to simplify
the example.




On Wed, Jan 9, 2019 at 1:14 PM Gilles Chehade <gilles@poolp.org> wrote:

> Hello,
>
> After reading your proposal, I don't quite understand what it is about and
> what is expected from SMTP implementations.
>
> The content type is part of the message, not part of the protocol, also
> your rationale seems to equate one SMTP session to one message but a single
> session may transport multiple messages with different messages with
> different content types.
>
> Gilles
>
>
>
> Le 9 janv. 2019 07:59, Viruthagiri Thirumavalavan <giri@dombox.org> a
> écrit :
>
> Hello Everyone,
>
> I'm the guy who proposed SMTP Over TLS on Port 26. Looks like that was a
> dead end. So, now coming with another proposal.
>
> I joined IETF day before yesterday. So not sure if this was already
> discussed before and got rejected. If this was rejected already, then my
> apologies.
>
> I wanna bring Markdown support to SMTP.  So instead of transferring both
> "text/plain" and "text/html" versions, future mails can use only
> "text/markdown".
>
> I listed the benefits in my proposal. Let me if it is worth going forward.
> So I can create an Internet Draft.
>
> https://gist.github.com/mistergiri/603766f5295802d44cc1a5752ebfa21f
>
> Thanks
>
> --
> Best Regards,
>
> Viruthagiri Thirumavalavan
> Dombox, Inc.
>
>
>

-- 
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.