Re: [Crisp] Last Minute Last Call Comments on lwz-06

Marcos Sanz/Denic wrote:
> Really?
> 
> As we seemed to agree in
> http://www1.ietf.org/mail-archive/web/crisp/current/msg00413.html
> the BEEP reply codes 500/501 refer to the XML of the transport protocol 
> itself, not to the XML of the payload.
> 
> And the only usage for 'vi' type in XPC that I have been able to find is
> 
>    Clients MAY send a block with this type of chunk to a server.  These
>    chunks SHOULD be zero length and servers MUST ignore any data in
>    them.  When a server receives a chunk of this type, it MUST respond
>    with a chunk of this type.  This interchange allows a client to query
>    the version information of a server.
> 
> which doesn't mean that 'vi' must be sent by the server when the 
> IRIS-based XML payload does not match a version the server supports.

Your killin' me, Marcos!  :)

It would be 'oi' in both XPC and LWZ.  The difference between the mail 
message you pointed out and the issue you are talking about are:

  1) I understood what you said, I just won't do what you asked.
    - and -
  2) I don't understand what you said.

-andy

_______________________________________________
Crisp mailing list
Crisp@ietf.org
https://www1.ietf.org/mailman/listinfo/crisp