I put the JSON background there because the purpose of the working group is meant to be understood also by those who have not been involved in the work.
> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of ext Manger, James H > Sent: Wednesday, June 15, 2011 4:07 AM > To: Sean Turner; [email protected] > Subject: Re: [woes] WOES Charter Proposal > > Sean, > > I would make almost the opposite edits to the charter than you. > I think it is really helpful that the charter lists different > existing proposals (JWT, SWT, MagicSigs, JSS, JSMS). They > provides a great context for the WG; they show different > approaches; they show people want something in this space. > I think most of the JSON background can be dropped. > > > >Thanks for kicking this off Hannes. In Prague, I thought > the goal was > >pretty straightforward: JSONize CMS. To that end I think > we can clip > >out some of the references to work already done. The BOF > can decide > >later what draft is the basis for the starting point. > > ... > <delete> > > Different proposals for providing these > > security services have been defined and implemented. > Examples are: JSON > > Web Token [JWT], Simple Web Tokens [SWT], Magic Signatures > > [MagicSignatures], JSON Simple Sign [JSS], JavaScript > Message Security > > Format [JSMS]. > </delete> > > _______________________________________________ > woes mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/woes > _______________________________________________ woes mailing list [email protected] https://www.ietf.org/mailman/listinfo/woes
