Re: [saag] Comment added to draft-gutmann-scep history

Patrick McManus <pmcmanus@mozilla.com> Sat, 14 July 2018 18:08 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931C2130DD2; Sat, 14 Jul 2018 11:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level:
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 eDeL3PbmUTqv; Sat, 14 Jul 2018 11:08:53 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4C9130DE5; Sat, 14 Jul 2018 11:08:53 -0700 (PDT)
Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by linode64.ducksong.com (Postfix) with ESMTPSA id 0F76E3A019; Sat, 14 Jul 2018 14:08:51 -0400 (EDT)
Received: by mail-oi0-f54.google.com with SMTP id i12-v6so67880984oik.2; Sat, 14 Jul 2018 11:08:51 -0700 (PDT)
X-Gm-Message-State: AOUpUlFR059sSNhxBFOPIvWNw7oS9w4DXYLbVo2f6Bk4UKsd3S/5jZvm RLO7XvB4uTWpGSkmtu6DAOxajBa/zWGLpLA93fI=
X-Google-Smtp-Source: AAOMgpfawcz9mxgcKsA2/iwt9WiqpATL8bdqjKaFXJk+RmyWtd9SpJVU1CjUg/8eENVbs0MCzbiipguStqw7aBwcOUI=
X-Received: by 2002:aca:5a45:: with SMTP id o66-v6mr11054064oib.155.1531591730682; Sat, 14 Jul 2018 11:08:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a22:0:0:0:0:0 with HTTP; Sat, 14 Jul 2018 11:08:50 -0700 (PDT)
In-Reply-To: <20180714151547.GG59001@mit.edu>
References: <152231658869.24008.11321959845877039592.idtracker@ietfa.amsl.com> <1522887334433.4490@cs.auckland.ac.nz> <1525092187804.38190@cs.auckland.ac.nz> <bcb96609-a4fd-faf6-cf07-12b9f1fe7df0@isode.com> <1531471734017.88813@cs.auckland.ac.nz> <1531537625942.57273@cs.auckland.ac.nz> <20180714151547.GG59001@mit.edu>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Sat, 14 Jul 2018 14:08:50 -0400
X-Gmail-Original-Message-ID: <CAOdDvNqdJtwPshdPsJK20Hseq4K=Dv59=mrY0-EzK5pw_aQNQQ@mail.gmail.com>
Message-ID: <CAOdDvNqdJtwPshdPsJK20Hseq4K=Dv59=mrY0-EzK5pw_aQNQQ@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "draft-gutmann-scep@ietf.org" <draft-gutmann-scep@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c5f390570f97d04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/dZq5m7t_8tzkM86BsFMS2sKZXyw>
Subject: Re: [saag] Comment added to draft-gutmann-scep history
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2018 18:08:57 -0000

Ben - thanks for flagging this.

Referencing BCP56 is probably not a great idea - its not well tuned to the
way HTTP evolved.

BCP56bis otoh is designed to provide what you need. Its a work in progress
and would certainly benefit from review and comments:

editors copy:
https://httpwg.org/http-extensions/draft-ietf-httpbis-bcp56bis.html
current official draft:
https://tools.ietf.org/html/draft-ietf-httpbis-bcp56bis-06
github as easy place to leave feedback and suggested edits:
https://github.com/httpwg/http-extensions

-Patrick



On Sat, Jul 14, 2018 at 11:15 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Sat, Jul 14, 2018 at 03:07:42AM +0000, Peter Gutmann wrote:
> >
> > Maybe we need an updated BCP 56 that provides info on the general use of
> HTTP
> > as a substrate and how to deal with it that every other
> HTTP-as-substrate-
> > using RFC can refer to (no, I'm not volunteering to write it :-).
>
> draft-ietf-httpbis-bcp56bis is active in the httpbis WG at the moment -- it
> would be appropriate to make such suggestions to the WG :)
>
> -Ben
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
>
>