IETF Logo Mail Archive

Re: [OAUTH-WG] Question regarding RFC 7800

Carsten Bormann <cabo@tzi.org> Mon, 08 April 2019 12:10 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7098E1201EB for <oauth@ietfa.amsl.com>; Mon, 8 Apr 2019 05:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham 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 pNZxTFP0Ofpl for <oauth@ietfa.amsl.com>; Mon, 8 Apr 2019 05:10:21 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36D791202F6 for <oauth@ietf.org>; Mon, 8 Apr 2019 05:10:21 -0700 (PDT)
Received: from client-0237.vpn.uni-bremen.de (client-0237.vpn.uni-bremen.de [134.102.107.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 44d8Pk6pWdzyV2; Mon, 8 Apr 2019 14:10:18 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <AM0PR04MB63225DB815E67E7EF70F3C06E5570@AM0PR04MB6322.eurprd04.prod.outlook.com>
Date: Mon, 08 Apr 2019 14:10:18 +0200
Cc: "oauth@ietf.org" <oauth@ietf.org>
X-Mao-Original-Outgoing-Id: 576418216.4652081-e6ee522e0de66db73d877b81e4c68927
Content-Transfer-Encoding: quoted-printable
Message-Id: <680A3883-1973-4173-B7A7-69AB7A60781F@tzi.org>
References: <AM0PR04MB63225DB815E67E7EF70F3C06E5570@AM0PR04MB6322.eurprd04.prod.outlook.com>
To: Robert Lembree <Robert.Lembree=40se.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/a0KHKkQD5-5FAOUfSuEvQ-aZvoM>
Subject: Re: [OAUTH-WG] Question regarding RFC 7800
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Apr 2019 12:10:23 -0000

Hi Robert,

This raises the $64000 question: What piece of information made you consider that this draft might need more help?  Maybe there is some miscommunication that we can fix.

Grüße, Carsten


> On Apr 3, 2019, at 12:14, Robert Lembree <Robert.Lembree=40se.com@dmarc.ietf.org> wrote:
> 
> Hello folks,
>                 What is the status of RFC 7800?  We’re finding the need for this, and wonder what we might be able to do to help move this along?
>  
> Regards,
> rob
>  
> --
> Robert Lembrée
> Lead Cybersecurity Architect
> Innovation & Technology
> Industrial Automation Business
> Schneider Electric
> D  +1 978 975 9971
> M  +1 603 494 0559
> E  robert.lembree@se.com
> 800 Federal St.
> 3W-WS179
> Andover, MA 01810
> United States
> <image001.png><image002.png>
>  
>  
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email