[midcom] Identifying Intra realm calls

["Cedric Aoun"<[e-mail]>]

Hello, 

> One of the open issues that had been briefly discussed in the mailing list
> in the context of the pre-Midcom solutions - STUN, PHANTOM and MINT - is
> how to effectively route intra-realm calls (e.g. calls behind the same
> NAT), i.e., how does the client or a signaling server determine that the
> called party is in the same network realm and the media is directly
> routable without going through the NAT or a relay NAT (i.e. a Media
> Proxy). For example, the last para of Sec 9.3 in STUN draft states: It is
> possible that both participants in the multimedia session are behind the
> same NAT. In that case, both will repeat this procedure
>    above, and both will obtain public address bindings. When one sends
>    media to the other, the media is routed to the nat, and then turns
>    right back around to come back into the enterprise, where it is
>    translated to the private address of the recipient. This is not
>    particularly efficient, but it does work.
> 
> Note that, the above solution is not applicable to NATs all vendors. Given
> that a significant percentage of Enterprise calls are intra-realm, the
> issue, if resolved, will lead to considerable saving of egress bandwidth
> at the NAT and will lead to general improvement in service quality.
Note that this is also an issue within the MIDCOM framework.

An ID was submitted to discuss this issue
http://www.ietf.org/internet-drafts/draft-aoun-midcom-intrarealmcalls-00.txt


> The intent of this ID is to initiate some discussions (perhaps, offline)
> towards a solution for this issue. The intent is in no way to disrupt the
> progress of the WG's chartered work items, so, if you're interested to
> work on this problem, please send comments offline and we can move the
> discussions to a private mailing list ([e-mail]).
Thanks
Cedric

Cedric Aoun
Nortel Networks
France
mailto:[e-mail]


>  
>