Hi Christer,
    Glad to see that the draft starts its WGLC process.It's really useful.

    I still have some difficult in using IETF and cannot find the whole
sorted comments about this draft, so i have some doubt about this draft.

   1.   "If a forking proxy receives a reliably sent 199 response for a

   dialog, for which the proxy has previously generated and sent a 199

   response, the proxy MUST forward the 199 response."
     Does it describe the case below? Although P1 have sent a 199 response,
P1 havs to  forword the send reliably 199 too.Or  is the  first 199 mistaked
for 18x?

          UAC               P1                  UAS_2
       --- INVITE ------>
                         --- INVITE (leg 2) ->
       <-- 199(leg 2) --
                         <-- 199 (leg 2) -----
       <-- 199(leg 2) --

     2.  "10.  Usage with 100rel

   When a 199 Early Dialog Terminated provisional response is sent by a

   UAS, since the provisional response is only used for information

   purpose, the UAS SHOULD send it unreliably even if the 100rel option

   tag [RFC3262] is present in the Require header of the associated

   request."



   I have seen a comment on this question,but still not understood about it
.

   If the INVITE has a Require tag "Require: 100rel",does the UAS still use

   unreliable 199 response?



   If 199 is reliable, there is one more advantage. If the 199 arrives
before

   the first 18x response, UAC can discard the first 199 and process it
until

   UAC receives the first 18x response that has the same to-tag as 199, as

   the reliable 199 should be re-transmited until  received PRACK.







   ps:



   Can anyone show me how to sort all comments of a topic by time?





   Regards,



   Eric.wang
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email protected] for questions on current sip
Use [email protected] for new developments on the application of sip

Reply via email to