IETF Logo Mail Archive

Re: [Uta] CBOR, XML, JSON (was Re: Updated SMTP STS Draft)

Daniel Margolis <dmargolis@google.com> Thu, 05 May 2016 19:53 UTC

Return-Path: <dmargolis@google.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9C112D575 for <uta@ietfa.amsl.com>; Thu, 5 May 2016 12:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level:
X-Spam-Status: No, score=-3.696 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_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 pbFOinszJPN9 for <uta@ietfa.amsl.com>; Thu, 5 May 2016 12:53:44 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 AB9F612D114 for <uta@ietf.org>; Thu, 5 May 2016 12:53:44 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id u185so109441388iod.3 for <uta@ietf.org>; Thu, 05 May 2016 12:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Jf3+O+pKgDrg1hT02UecaLKW4K8Gr+6mUsNlMmAnXWA=; b=d4V09w5JlO1cHwGf1uDlurldRUWydBBolPhqmtrJpzGPls0D+OZQH5EOeXbT/7q34u 97FXIncWEVwYA4QxOdrljgsB4Qid98U4By0b7bYuTRCuNyPHI14X/zQBZ/Ku55CGm2AY 3L5QnVLmP8CsZo43lRZeJn8bWh65pamOo4PMRqJ7h5AmSayGcMARs/2tSK9ZrxAbfuA0 f6HuzJ+CUYI7FF1ZARwh2zBXSlCfr+KKvffDfy7rBMjr92zwPUuvlbhUoj2KRedCPDI6 RXArbn1mVk1Ytk664umbBy+XdTa5+Vxwb1hYy5dXoDekJ1WfvCbAc/AMAgQYzvfUf+mm M3BQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Jf3+O+pKgDrg1hT02UecaLKW4K8Gr+6mUsNlMmAnXWA=; b=N1xSxTetYuQVQq3KcgVr2WHDve8calwarW3eKhMh1GcrEqZIBzWu1OPg35jqMuaAck LPp8tp+Z73M3AMJVxGPMjbktBqYvIVWTJsHkCRS+aFtforKdjaZbsVBJxZX5Y6YyWSNf ExpkAr56vsy2krl+N7l4WrZL557U3xo9hMVN1rRimt4xymGa8LcnYR72Wp2NfHC8POPB sZI62sGeTKdFXjm0vOYXo28yAz5bM0snmFLNXQNWsZzlrnPD2rZmf5md5vmkub4RBNPF kI236qG0l6e0bpWbfQ5yy9/hEqIzZD+x7iMC6DPwJWy23Iv7epR/hpnZqF4pPQbFTU10 6atg==
X-Gm-Message-State: AOPr4FWl7+9o+pv2nposwoLDa97suQRZCpPi3UYi/4c7gfg7TZoYB5KDcu8CDxcDUbkhLARWdef3qCEp26iTcE64
MIME-Version: 1.0
X-Received: by 10.107.12.70 with SMTP id w67mr21314880ioi.114.1462478023912; Thu, 05 May 2016 12:53:43 -0700 (PDT)
Received: by 10.64.91.227 with HTTP; Thu, 5 May 2016 12:53:43 -0700 (PDT)
In-Reply-To: <20160505191219.27821.qmail@ary.lan>
References: <CANtKdUeeX_XtoEWuysv2zkUb+YUyfH4LFNd7nzj23nw_MPxnWg@mail.gmail.com> <20160505191219.27821.qmail@ary.lan>
Date: Thu, 05 May 2016 12:53:43 -0700
Message-ID: <CANtKdUd=zJzm90b=CHJ4Y-8d49Trj4qN0EkJxXJeRJEMVAndSw@mail.gmail.com>
From: Daniel Margolis <dmargolis@google.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="001a113f8b201bede505321db3fb"
Archived-At: <http://mailarchive.ietf.org/arch/msg/uta/VEuG5jPL7JvR6Oe8ZuOb2ItbHRE>
Cc: uta@ietf.org
Subject: Re: [Uta] CBOR, XML, JSON (was Re: Updated SMTP STS Draft)
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 May 2016 19:53:47 -0000

On Thu, May 5, 2016 at 12:12 PM, John Levine <johnl@taugh.com> wrote:

> While the http specs say it's OK to do a POST with an arbitrary MIME
> type such as application/json or application/gzip, the web apps I know
> all expect the POST body to be multipart/form-data.
>
> If you just want to send the blob of JSON, PUT with an appropriate
> filename would be more appropriate.
>

True.  https://github.com/mrisher/smtp-sts/issues/35 for now.

Not sure about PUT.

"The PUT method requests that the enclosed entity be stored under the
supplied Request-URI. If the Request-URI refers to an already existing
resource, the enclosed entity SHOULD be considered as a modified version of
the one residing on the origin server. "

Seems like it would require the reporter to be claiming a unique URI, no?

v2.23.0 | Report a Bug | By Email