[Webpush] Kathleen Moriarty's No Objection on draft-ietf-webpush-protocol-11: (with COMMENT)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Wed, 12 October 2016 18:26 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: webpush@ietf.org
Delivered-To: webpush@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 715951295FB; Wed, 12 Oct 2016 11:26:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.34.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147629678445.6285.5038003546245862234.idtracker@ietfa.amsl.com>
Date: Wed, 12 Oct 2016 11:26:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/nZVy471EEoRU8qVHgmdBNZN0nIA>
Cc: draft-ietf-webpush-protocol@ietf.org, shida@ntt-at.com, webpush-chairs@ietf.org, webpush@ietf.org
Subject: [Webpush] Kathleen Moriarty's No Objection on draft-ietf-webpush-protocol-11: (with COMMENT)
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 12 Oct 2016 18:26:26 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-webpush-protocol-11: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-webpush-protocol/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for a well written security considerations section. 

The only thing I might add is a note on the varying levels of security
offered by the HTTP authentication methods, which are documented in their
RFCs.  Adding just that point to the following (phrased however you'd
like) would be helpful:
    A push service MAY
   choose to authorize requests based on any HTTP-compatible
   authorization method available, of which there are numerous options.

The somewhat recent updates to Basic & Digest do a really great job at
saying how awful they are and there are some experimental options that
offer some promise now.