[straw] straw-sip-traceroute: 205?

[Christer Holmberg <[e-mail]>]

(As co-chair)



Hi,



Hadriel has submitted the following draft in DISPATCH:



http://tools.ietf.org/id/draft-kaplan-dispatch-sip-205-response-00.txt



The draft defines a new SIP response code, 205, and Hadriel has also suggested the response code to be used in the STRAW trace-route delivery:



http://tools.ietf.org/html/draft-ietf-straw-sip-traceroute-00





The 205 draft has not been adopted yet, but the chairs would still like to ask the STRAW community whether it thinks that we can make a working assumption decision that we will use the 205 mechanism (assuming it gets done) in the trace-route delivery, or whether we should use some other mechanism.



If we choose 205, the trace-route draft will obviously have a dependency on the 205 draft, and we'll have to wait for it to get done.



And, as we don't know whether 205 will ever become an RFC, or how it will eventually look like, we can always re-visit any decision we make.



So, the question to the community is:



Do you think that:

a)      We shall base the trace-route delivery on using the SIP 205 response.

b)      We shall base the trace-route delivery on another mechanism - AND I am also elaborating on how such mechanism would look like.

c)      I have read all the relevant drafts, and the e-mail discussions, but I still think it is too early to make a working assumption, even if it later can be re-visited, at this point - AND I am also elaborating on why I think so.



Regards,



Christer & Victor



(STRAW Chairs)