Hi WG, while editing -protocol to 02, I also work through Anton's early comments with a lot of good points. I hadn't commented on them so far because we were on the broader topics. Most of the comments now smoothly go into the new version, but I found this here that I would like to bring to the list:
> 23. Section 5 & beyond. Why is there a need to specified > structured data > *anywhere* within the message. I thought we will designate a special > field like TAG for the structured data. This way we won't need a > special sequence to identify it. Also, I think allowing it everywhere > gives too much unnecessary freedom. Harder to evolve protocol later. I did this to allow app software layers/libraries an easy way to add its information. But we could also specify that it MUST be immediatley after the tag, with no SPs between the structured data elements. On the special sequence, I think that is actually still mandatory. Otherwise it may be mistaken by a non structured data element which co-incidently begins at that location. An alternative, of course, would be to supply a special sequence (eg "[]") to indicate that no structured data elements are present. I will leave it as is in -02, except if we reach concensus on this topic quicker than I edit... Comments are appreciated. Rainer
