Re: [sipcore] Verify draft-ietf-sipcore-rfc4244bis-callflows-02.txt

Hi Dale;

 Thanks for further comments..

On Feb 4, 2013, at 12:53 PM, Dale R. Worley wrote:

> My previous comments have been addressed acceptably.  But there are a
> few new nits that I've spotted:
> 
> ** General
> 
> * On page 19
> 
>   Alice       example.com     Gold          Silver       Agent
> 
>   |              |              |             |            |
>   | INVITE F1    |              |             |            |
>   |------------->|              |             |            |
>   |              |              |             |            |
>   |              |  INVITE F2   |             |            |
>   |              |------------->|             |            |
>   |              |              |             |            |
>   |              |  302 Moved Temporarily F3  |            |
>   |              |<-------------|             |            |
>   |              |              |             |            |
>   |             ACK             |             |            |
>   |---------------------------->|             |            |
>   |              |              |             |            |
> 
> The ACK should be shown thus:
> 
>   |              |              |             |            |
>   |              |  ACK         |             |            |
>   |              |------------->|             |            |
>   |              |              |             |            |
> 
> * On page 27, the top ACK should be shown thus:
> 
>   |              |              |             |            |
>   |              |  ACK         |             |            |
>   |              |------------->|             |            |
>   |              |              |             |            |
> 
> * On page 31, the top ACK should be shown thus:
> 
>   |              |              |             |            |
>   |              |  ACK         |             |            |
>   |              |------------->|             |            |
>   |              |              |             |            |
> 
> * On page 40, there are two occurrences of:
> 
>   To: <sip:sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com\
>    ;gr>
> 
> "sip:sip:" should be replaced with "sip:".

DONE.

> 
> ** http://www.ietf.org/mail-archive/web/sipcore/current/msg05489.html
> 
> * "5. In draft-ietf-sipcore-rfc4244bis-callflows-01, examples 3.6 and 3.7
> do not show the History-Info value in the final 200 response to the
> UAC.  This final value would be useful, in particular, because they
> give further examples of how proxies process History-Info."
> 
> In neither of these examples is the final 200 response shown.  I
> assume that this is the authors' intention.

 This, I think was because the value of h-i would not change from 
the last proxy to UAC, and didn't see a need. If you want to see this 
added. I will add them

> 
> ** http://www.ietf.org/mail-archive/web/sipcore/current/msg05429.html
> 
> * "But in draft-ietf-sipcore-rfc4244bis-callflows-01, Reason header
> values for 1xx responses are not generated.  See message F8 in section
> 3.1."
> 
> rfc4244bis-callflows-02 does not show Reason headers with 1xx values.
> I expect this is because the authors intend for this to be how
> History-Info operates.  But that does mean we are committed to
> updating rfc4244bis to state that (because it currently says that 1xx
> responses set Reason headers).

 Okay, I will add these. 

> 
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore