Draft:  draft-ietf-sipping-service-examples-12.txt
Reviewer: Miguel Garcia [Miguel.An.Garcia@nokia.com]
Review Date: 5 March 2007
Review Deadline: 
Status: Post-WGLC 
Sections: 2.14 and 2.15.

Summary: 
========

I went through my comments again, and I noticed two of them that haven't 
been implemented. I can't really recall now if we discussed these two 
issues in the past or they are still oversights (it's been long time 
with this draft).

I reproduce my old comments here. Note that sections have changed, and 
when the comment refers to Section 2.14 corresponds to Section 2.13 in 
version -12:

1) About the call flow in Section 2.14: Alice receives the 403 in flow
F8, including an Error-Info URI. I would assume that the INVITE F10 goes
straight forward to that URI. However, flow F10 traverses once more the
Proxy (proxy that wasn't initially traversed in flow F1). I don't think
this is the natural behavior, why should Alice route the INVITE F10 via
the proxy, once she got a URI that does not embed a Route header? Notice
that the proxy is not Alice's outbound proxy, so I see no reason for
this behavior.

8) I noticed that flow F9 in Section 2.14 contains a Proxy-Authorization
header. I think it is weird that the ACK request for a 403 response
contains a Proxy-Authorization header. There is nothing the proxy can do
with that group of credentials. The same applies to Flow F6 in Section 2.15.

Is it possible to get some comments about them?