Hi Carsten,
I didn't see any specific issues. I'm trying to understand where the
RFC stands, and why or why not it might be smart to implement and use it as it
stands. My primary concern is compatibility with any anticipated changes to
the RFC in advance of wide acceptance.Regards, rob 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 > <[email protected]> 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 [email protected] > 800 Federal St. > 3W-WS179 > Andover, MA 01810 > United States > <image001.png><image002.png> > > > _______________________________________________ > OAuth mailing list > [email protected] > https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&data=02%7C01%7CRobert.Lembree%40se.com%7C380e5a2c66ee403c895308d6bc1b3992%7C6e51e1adc54b4b39b5980ffe9ae68fef%7C0%7C1%7C636903222454083023&sdata=7WHGrasoqhizYah%2BenrVNEhbizupkYiS5Lnob4azLIs%3D&reserved=0 ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. ______________________________________________________________________
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
