Jonathan wrote:
>
> Vijay wrote:
>
> > Hmmm...so what is a proxy for a domain to do when it gets an
> > INVITE request
[with no user part]
> > where the host part matches its domain? I guess one option is, as Jo
> > pointed out, to send a 405 Method Not Allowed final response.
>
> No. What it does is the same as what it will always do when it receives a
> request for its domain.
>
> When a proxy receives a request for its domain, it means that THIS PROXY
> owns the namespace of that domain; the formatting, syntax, and routing of
> the user portion is entirely at the discretion of the proxy. If the user
> portion describes a user which is unknown, using whatever means the proxy
> desires to determine "unknown", it returns a 404. So, if the addressing
> system of the proxy is that it does not recognize the lack of a user name,
> then this means that no routing can be performed, and the result is the
> standard 404.
I wouldn't disagree, but I don't think that necessarily implies
that 405 is wrong.
I guess if a server is a "pure" proxy -- i.e., never acts as a
Registrar; never acts as a Redirect Server; never acts as a UAS
or UAC; basically never generates any responses locally apart
from 1xx/4xx/5xx -- then 404 sits well with me. However, the
moment it can function as a Presence Server; the moment it
responds with a (locally-generated) 2xx to an OPTIONS; it seems
to me that this is more of a mongrel proxy, and in the most
general case, an absence of user part seems a reasonably intuitive
way of addressing It.
Of course, I don't believe in "pure" proxys any more. &:)
Cheers,
- Jo.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
