Re: [clue] New draft on Transport Options for Clue

[Paul Kyzivat <[e-mail]>]

[as individual]

Here are some comments I accumulated while reading through this draft:

There are some character set issues in this draft, at least as its 
represented in my browser. I'm seeing things like: "Oon the wireO". The 
first and last characters there are (to me) "O". I presume they are 
intended to be some sort of quote, and that there is a character set 
conversion problem.

There is a paragraph beginning "In version -00 ... we ...", implying 
that this *is* version -00. But its now -01.

Regarding the CLUE messages: I'm lacking a clear specification of the 
sequence in which these messages may be sent. IMO a state machine would 
be helpful to clarify this.

3.1 - use of UPDATE

The limitation on use of update is really wrt o/a. (If an UPDATE 
contains an offer, and answer must be in the response to the update.) It 
is really irrelevant to other uses of UPDATE, to convey things other 
than o/a. You should not exclude it just for this reason. But I agree 
INFO might be a better choice for tunneling clue messages in SIP, 
assuming its not necessary to send them with the initial INVITE.

3.2

Another issue here is reliable message delivery. UDP doesn't provide it. 
Defining it in a one-off fashion on top of UDP is a pain, and a 
distraction from the real work of CLUE. ISTM it would be best to 
reference some existing reliable transport that has suitable properties. 
(Perhaps one layered on UDP.)

3.3

The issue of keep alive messages seems something of a red herring. *any* 
reliable mechanism is likely to require keep alives.

4.1 - Using SDP

This alternative is more "encumbered" than the others, because using SDP 
with SIP implies using the o/a model, which doesn't currently align well 
with the framework. So it needs to be considered in a different light 
than the others.

For instance, use of SDP means tunneling in sip messages, and then SIP 
handles the transport issues. It also implies using SIP solutions to 
message size - requiring use of TCP for large messages.

	Thanks,
	Paul

On 10/24/11 11:44 PM, Marshall Eubanks wrote:
> We just published a draft on Transport Options for
> Clue, draft-wenger-clue-transport-01
> (it's -01 as I fixed some issues with the author list in -00).
>
> http://tools.ietf.org/html/draft-wenger-clue-transport-01 :
> A new version of I-D, draft-wenger-clue-transport-01.txt has been
> successfully submitted by Marshall Eubanks and posted to the IETF
> repository.
>
> Filename:        draft-wenger-clue-transport
> Revision:        01
> Title:           Transport Options for Clue
> Creation date:   2011-10-24
> WG ID:           Individual Submission
> Number of pages: 9
>
> It clearly needs some work...
>
> Regards
> Marshall
>
>
>
> _______________________________________________
> clue mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/clue