Prem Sumetpong wrote:
> Since SIP doesnt define the interface between the registrar and location
> service and leaves it to the implementation
>
> The assumptions then are
>
> - registrar and proxy are (must be ??) from the same vendor. The "how
> to" fetch and store from the shared storage is known by both the
> registrar (stores) and proxy (fetches).
No, not necessarily. The registrar and proxy might just
need to be configured with some ODBC Data Source (e.g.,
an Oracle DB), or an LDAP Server.
> or.- there is a published interface (schema/dictionary/api) for storing
> and fetching the registered addresses.
>
> Am I right to say that SIP doenst address the latter ??
Yes.
> Wouldnt that
> cause an interoperability problem ??
No, not really, unless people wanted to deliver "Location
Servers" that didn't talk SIP, but talked some new
protocol X.
In practice, this isn't going to happen because we have
things like LDAP and rwhois and finger and JDBC and X.500
and and and. These are going to be typical "Location
Servers". The most important thing to remember is that
user discover and whathaveyou relies on some abstract
notion of a "Location Service"; in essence, this could
be absolutely anything, and in some cases thinking of
it as fronting some "Location Server" is not going to
be so helpful (imagine a proxy that does all it's routing
based on an in-memory set of regular expressions).
HTH,
- Jo.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
