<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'><hr id="zwchr"><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px; color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Marc-André Lureau" <marcandre.lureau@gmail.com><br><b></b><br><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 29, 2014 at 3:34 PM, Jonathon Jongsma <span dir="ltr"><<a href="mailto:jjongsma@redhat.com" target="_blank">jjongsma@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div id=":ttm" class="a3s" style="overflow: hidden;">I'm not sure that I'm a big fan of a free-form field. It would be nice<br>
if it had at least *some* structure and you could expert certain<br>
information to be there...<br></div></blockquote><div> <br></div><div id="DWT146">Then I would have a defined structured message in the protocol rather than a simple text field.<br><br></div></div></div></div></blockquote><font size="3"><br>What do you think about using the message structure that was suggested in v1 (with the "type" field specifying what type of information is provided) ?<br><br>thanks<br>Pavel</font><br><br></div></body></html>