IETF Logo Mail Archive

Re: [Webpush] Ben Campbell's Yes on draft-ietf-webpush-protocol-11: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 13 October 2016 00:13 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E296127735; Wed, 12 Oct 2016 17:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AZrwvtcbAHyR; Wed, 12 Oct 2016 17:13:07 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 BC39E12951D; Wed, 12 Oct 2016 17:13:02 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id w3so43066429ywg.1; Wed, 12 Oct 2016 17:13:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DKSPAC3l+6zuemtd+M6yYFI8X9DMR/YV4HCLAafXRDo=; b=oZ06tHBzids5vJX+Ucar06GY8NyRRgFil7IE5jDtCIR8y9OAbOiHe2GE+goaj/cPtU YTa0dTk/q+2JDen5IQYJh7Nd3DohKIZuat+bDgvQgk2fn6h59ItcRfsf+U+FPdMM5DFb IOvHKRuN7jc+kpXqNddg/sZoP7UCuIG2mXi1Oq267t+PkvTVlX1qJ6cBgfyXmFoxbaoL GR3EEZuYBh77jtzJyydg/XyAecfVJ3NSNM8zjhZSgERwZ34IA1lAiCZUVlLQQMt0SmK5 tK8NF8b2irDFJlTtuwHXC1zdVPyb2as28Sc3Mv+njJtAO848S7REsHTLrXBKf1jX0q4X pTOQ==
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:from:date :message-id:subject:to:cc; bh=DKSPAC3l+6zuemtd+M6yYFI8X9DMR/YV4HCLAafXRDo=; b=VdGgKIzbiCP0L3DSOSZ1Pu4RVcG2wbvuliJoHze4JyM5Pxag8xYEbhHM3Yl9Q47aKK 82xl6hwQ0tSmiEi8NXwJZ2AGRD8qG2MtO3FakPCv6mJTiCDIE4NLGLvY2uKhdIWeXFez kh/KnvgL0EnGRpf9wo1eV+81H62c0qMrOS1PnryVZ9jdXhRwxRZvqtD16GL1i+PZ9vpu qq4iLhwq8+P03EwO0ijCrSPnnQ2xSyCtIpsM6nu/q/3OnKeNIH/qYfwDZzI3nbHVQRhE fT8FCxgNHxNa6IpreGWTcjrlV8SFmIME04NlCBzGdTA2A1u0fqOF5d1b+LFFyfEaKMYF A+TQ==
X-Gm-Message-State: AA6/9RlSjN+7lowNJFuUzGOHIj/Hs//zHW0nheudYOx+SEeopvjfaG2WYb7eUYITEBZ04woZAOkTT0AP5AxY5g==
X-Received: by 10.129.77.84 with SMTP id a81mr3250839ywb.19.1476317581951; Wed, 12 Oct 2016 17:13:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.92.67 with HTTP; Wed, 12 Oct 2016 17:13:01 -0700 (PDT)
Received: by 10.37.92.67 with HTTP; Wed, 12 Oct 2016 17:13:01 -0700 (PDT)
In-Reply-To: <CABkgnnW9yP8NHC7xJwN-qt_0Oc=WrxRhWcMO3=YY_8qFvAyzhA@mail.gmail.com>
References: <147630754676.6419.3793529940535426058.idtracker@ietfa.amsl.com> <CABkgnnW9yP8NHC7xJwN-qt_0Oc=WrxRhWcMO3=YY_8qFvAyzhA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 12 Oct 2016 19:13:01 -0500
Message-ID: <CAKKJt-fKL-p_Jh-wE8LdYM3RyxBFH1fXtdN8sKoMsuK8XLNnNw@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="001a1140b7ac0c466a053eb3f9c5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/x764I0gKc_5CqObYvZ8hV8_lUL8>
Cc: Ben Campbell <ben@nostrum.com>, "Brian Raymor (MS OPEN TECH)" <Brian.Raymor@microsoft.com>, Shida Schubert <shida@ntt-at.com>, iesg@ietf.org, draft-ietf-webpush-protocol@ietf.org, webpush-chairs@ietf.org, "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Ben Campbell's Yes on draft-ietf-webpush-protocol-11: (with COMMENT)
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Oct 2016 00:13:10 -0000

Hi, Martin,

On Oct 12, 2016 19:10, "Martin Thomson" <martin.thomson@gmail.com> wrote:
>
> On 13 October 2016 at 08:25, Ben Campbell <ben@nostrum.com> wrote:
> > In section 8, 2nd paragraph: "Applications using this protocol MUST use
> > mechanisms that provide
> >    confidentiality, integrity and data origin authentication."
> >
> > What must it use those mechanisms for? Are we talking about
communication
> > between the UA and app servers? Are we just talking about data in
motion?
> >  As much as I like to see such requirements in general, is it reasonable
> > for webpush to state requirements on the internal operation of the
> > application?
>
> This specifically refers to the work in draft-ietf-webpush-encryption,
> which covers these things.  We should add a f'rexample there.  Brian,
> does that sound right?
>
> (Yes, TLS is mandatory, but hop-by-hop mechanisms don't cover all the
bases.)
>

Make Ben happy, because it's his comment, but that would have significantly
helped me understand!

Spencer

v2.23.0 | Report a Bug | By Email