Re: [clue] Fwd: New Version Notification for draft-wenger-clue-transport-02.txt

[Paul Kyzivat <[e-mail]>]

Section 3.1.2

Title is "Using an SDP MIME body to carry the CLUE information in an 
INVITE or UPDATE exchange". This should not mention SDP. (Its a non-SDP 
MIME body that is being proposed.)

The concern about using UPDATE may be over stated. CLUE messages aren't 
negotiated - they're declarative - so there is no need to figure out 
anything before responding. There may be some desire to piggyback CLUE 
messages on the UPDATE responses to minimize traffic, but that can be 
optional, to be used if there is something ready to be sent.

Section 5: Clue Discovery

Another possibility not mentioned is to use a sip option tag for this. 
It allows signaling support using the Supported header, and required 
support using the Required header. (This can be useful if you don't want 
to call to succeed unless CLUE is supported.

Also, sip caller capabilities feature tags could be used to indicate 
support and, using callerprefs mechanisms, to direct the initial 
preferentially to a CLUE supporting device. Note that something related 
to this (a proposed "immersive" feature tag) is under discussion on the 
dispatch list.

These are not mutually exclusive.

	Thanks,
	Paul (as individual)