On Mon, Sep 8, 2008 at 3:23 PM, Iñaki Baz Castillo <[EMAIL PROTECTED]> wrote:
> Anyway, it seems that SCTP offers some capabilities (IP redundancy in
> a single connection) that SIP can't not advantage of them. Am I wrong?
> This is: the transport layer knows about associations between IP:port
> and connections, but just it, it doesn't know about complex SCTP
> connections involving various IP's.
Actually, in SCTP, an endpoint is represented as the tuple {IP1, IP2, IPn: port}
IMO, the received parameter should only include the PRIMARY_PATH
address and the SCTP failover should be used transparently.
> Isn't there really a RFC defining a new SIP transport layer model for
> SCTP protocol?
RFC4168: The Stream Control Transmission Protocol (SCTP) as a
Transport for the Session Initiation Protocol (SIP)
I'm afraid this document does not cover the above discussed issue.
Cheers,
--
Victor Pascual Ávila
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
