Subject: [siprec] Using of feature and options tags in SIPREC protocol

From: Leon Portman <[email-masked]>
Date: Tue, 15 Nov 2011 13:15:20 +0800

Hello

I wanted to get opinions about main open items for the protocol draft regarding using of feature and options tags.

if i remember correctly, we wanted to solve two problems:

1. Ability to register SRS and SRC with right capabilities in order to be able to discovery (specially SRS) and route RS INVITES correctly.

Solution: We have defined feature tags: "+sip.src" and "+sip.srs" (right syntax after Paul comments) and they should be used in relevant contact fields.

2. Make sure that only SRS and SRC will handle RS INVITE and not brake other UAs in case of wrong configuration or midboxes.

Solution: add "siprec" option tag and have SRC/SRS to use it in Supported and Required headers accordingly. 

Paul have suggested two have actually two options: src and srs in order to distinguish between SRC and SRS (we dont need it if requirement 1 stays).

Any opinions?

Thanks

Leon