I'm trying to catch Justin's attention with that subject header :-) This is more just for historical purposes. The desktop AOL client was basically a rendering engine of a binary protocol called FDO (two versions 88 and 91). This protocol supported both markup and scripting optimized for transfer over modems.
Additionally, AOL developed another protocol called Nachos with similar capabilities targeted at hand held devices. I suspect these will not be the last :) Maybe there is room to allow such mechanisms while still standardizing how a native mobile app can inform the AS that it wants to use a supported mechanism (can be out of scope; or a separate spec) to interact with the user. While the most common case will be authentication, I think we may need to enable these "challenge/response" mechanisms to also handle registration, recovery and other life cycle flows. Thanks, George ______________________________________________________________________ The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
