On 5/10/07, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > > > Cesc wrote: > > On 5/10/07, Paul Kyzivat <[EMAIL PROTECTED]> wrote: > >> > >> > >> Cesc wrote: > >> > Hi, > >> > > >> > Is there any limitations on the type of sessions SIP can create? > >> > For example, could plain data sessions (TCP or UDP) be created > >> > (negotiate listen port and IP, max framelength, ... ); or set up > >> > sessions for other known protocols, like HTTP (what IP/port that > >> > resource has the web page) or FTP? > >> > Is this specified in some RFC? any implementations? > >> > >> This certainly possible, and not restricted. You might want to look at > >> RFCs 4145 and 4572. But this may not always be wise even if possible. > >> There may be better ways, depending on the case. > >> > >> Paul > >> > > > > Care to elaborate on why and which better ways could there be? > > It depends on the situation. For instance some have advocated using SIP > to establish streaming video sessions. (e.g. INVITE > sip:[EMAIL PROTECTED]). But others consider that to be inferior to > using RTSP to establish the session. I won't get into the arguments on > either side - just that there are such discussions. > > > First, a comment ... I am not allowed to use DNS on my system, for > > many reasons that are here not relevant. Was DNS in your mind? > > I can imagine that HTTP and FTP (to name two) may have other ways ... > > which? > > But imagine I need a plain data link, to "tunnel" data from one point > > to the other of the network ... SIP sounds like a good set up > > mechanism (I want to avoid static configs, of course). > > Well, the fact that you can't use DNS will cause many issues. You won't > be using sip to establish sessions to arbitrary unknown targets either, > since those would probably be identified by URIs containing DNS names. > > I expect that you can use SIP for this purpose, but it sounds like it > would need to be a proprietary solution for your specific environment. > There is nothing particularly wrong with that if it meets your needs. > > Paul
Agreed that "propietary" is not per-se bad, but I want to stay in the mainstream as much as possible. Not using DNS is not an issue, as SIP works just fine without, you just cannot use domain names ... but a good registrar will always provide for a given username a contact address with an IP address and a port ... so that's not an issue. Thanks all for the help! Cesc _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
