<div>If a version is invalid (or not specified) we can assume it to be 1. Once we add new versions or features; we can use a version flag so clients and servers can negotiate a protocol. I don't see any importance in addressing it now.
</div>
<div> </div>
<div> </div>
<div><span class="gmail_quote">On 6/6/05, <b class="gmail_sendername">Martin Atkins</b> <<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Paul Crowley wrote:<br>> In the end, if we want to introduce totally incompatible protocol<br>> changes, we can always tack a version number on to the
openid.mode<br>> parameter. Any client or server that gets a request or response with an<br>> unrecognised openid.mode is going to reject it appropriately.<br><br>As soon as there is a totally incompatible protocol change, we might as
<br>well throw in the towel. If a new version breaks old servers/consumers,<br>then it might as well not be OpenID anymore.<br><br>It's far more likely that future changes will be implied by new<br>parameters. I see no value in allowing for a case which breaks
<br>everything anyway.<br><br><br><br><br></blockquote></div><br>