[MMUSIC] Re: Connection-Establishment Preconditions question

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Fri, 26 November 2004 15:47 UTC

Message-ID: <41A6D98A.6020603@ericsson.com>
Date: Fri, 26 Nov 2004 09:21:46 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
References: <4.3.2.7.2.20041108082500.0273c7b8@localhost>
In-Reply-To: <4.3.2.7.2.20041108082500.0273c7b8@localhost>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Cc: mmusic@ietf.org
Subject: [MMUSIC] Re: Connection-Establishment Preconditions question
Precedence: list
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org
Content-Transfer-Encoding: 7bit

James,

> Shouldn't the example in draft-ietf-mmusic-connection-precon-00.txt be 
> taken through the message flow point that the attribute lines are:
> 
> a=curr e2e sendrecv
> a=des e2e mandatory sendrecv
> 
> for clarity?

The example is complete. The thing is that, since the callee is the last 
one setting up his radio bearer, it does not need to generate any 
further offer informing the caller. It just knows that the caller is 
ready (because of the offer received previously) and that it itself (the 
callee) is ready as well. So, it simply sends a TCP SYN and, when the 
connection is ready, it starts alerting the user.

Thanks,

Gonzalo


_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic

[MMUSIC] Connection-Establishment Preconditions q… James M. Polk
[MMUSIC] Re: Connection-Establishment Preconditio… Gonzalo Camarillo