[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Byte reduction in BEEP commands.
Patrice Lapierre wrote:
> > Doug Royer wrote:
> > I also propose changing the REPLY from the CS to be an EMPTY
> > BEEP reply for success. Eliminating the the not needed 2.0
> > success code. If the BEEP reply contains any data, then
> > parse that iCalendar data.
> That would be awkward. I would tend to keep something in the
> payload (even if it's just <ok/>).
> Draft-06 uses a distinct ANS for each target in the command.
> And part of the payload was to indicate to which target the
> reply correspond. If there is a need to minimize the byte count,
> then it may make sense to allow a single ANS (or RPY) to refer to
> many targets with identical replies (e.g. success). But I would
> not remove the target(s) from the reply.
CMDID used to be optional and only needed when you did
pipelineing. I don't see any need for CMDID when there is
only one command issued at a time. When the CUA issues
more than one command without waiting for all of replies
to outstanding commands, then CMDID is needed.
Do you agree?
org:INET-Consulting LLC <http://INET-Consulting.com
title:Chief Executive Manager