If you read my note, it has nothing to do with the issues of synchronization. I completely agree that they are problem and that they should be covered. My issue had to do with how the text was written and flows.
In terms of completing the thought, a simple statement that this can lead to the client having the new password and a server having the password and thus they are unable to authenticate" is sufficient for me. My real problem is that the text does not flow and the first sentence appears to want more development but the text skips into a new issue on the next sentence. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Sam Hartman > Sent: Monday, December 19, 2011 9:13 AM > To: Tschofenig, Hannes (NSN - FI/Espoo) > Cc: [email protected] > Subject: Re: [abfab] Issue #6 - bad flow of text for authentication > requriements > > >>>>> ""Tschofenig," == "Tschofenig, Hannes (NSN <- FI/Espoo)" > <[email protected]>> writes: > > "Tschofenig,> Hi Sam, if you want to document it then we may need to > "Tschofenig,> provide a bit more text. I could imagine that we find > "Tschofenig,> that text in some of the OAuth documents. > > OK, can you help me understand what's wrong with what is there now? > It seems reasonably clear to me, so I'd like to better understand what you > and/or Jim find confusing. > _______________________________________________ > abfab mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/abfab _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
