Re: Using TLS in the first hop - Bug in RFC 5630

No I mean if Bob wants to Refer Carol to Alice, or Alice to Carol (since th=
at Refer can be sent out of dialog to Alice's contact).

I dunno about if it's an error or not - I remember there was a discussion a=
bout it, but it was a long time ago. :(

-hadriel
Sent from my iPhone

On Sep 15, 2011, at 11:27 AM, "I=F1aki Baz Castillo" <[email protected]> wrote:

> 2011/9/15 Hadriel Kaplan <[email protected]>:
>> But that's not the only use-case for Contact - the Contact URI of Alice =
can be used at any time later for an out-of-dialog request to Alice, and at=
 that point it suddenly needs a full sips path to Alice.  For example in a =
REFER case.
> =

> If Alice wants to refer Bob to Carol, Alice would do better by sending
> a REFER with "Refer-To: <sip:[email protected]>" rather than using
> SIPS. Not sure if you meant this.
> =

> Anyhow, what do you mean then? the section 3.1.3 in RFC 5630 is buggy
> as I told in my first mail, am I wrong? By setting a Contact with SIP
> rather than SIPS, that means that in-dialog requests would be sent to
> the caller using UDP/TCP rather than TLS, so they would fail
> (assumming that the caller is just reachable using TLS, let's imagine
> NAT and so).
> =

> -- =

> I=F1aki Baz Castillo
> <[email protected]>
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use [email protected] for questions on how to develop a SIP =
implementation.
Use [email protected] for new developments on the application of sip.
Use [email protected] for issues related to maintenance of the core SIP spec=
ifications.