Re: [16NG] distributed (decentralised) ASN for voip over wimax

Basavaraj Patil <basavaraj.patil@nokia.com> Tue, 29 July 2008 08:36 UTC

Return-Path: <16ng-bounces@ietf.org>
X-Original-To: 16ng-archive@optimus.ietf.org
Delivered-To: ietfarch-16ng-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CBA428C123; Tue, 29 Jul 2008 01:36:30 -0700 (PDT)
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C42033A6923 for <16ng@core3.amsl.com>; Tue, 29 Jul 2008 01:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAo6OWHpMTlE for <16ng@core3.amsl.com>; Tue, 29 Jul 2008 01:36:27 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 69AF13A67F8 for <16ng@ietf.org>; Tue, 29 Jul 2008 01:36:27 -0700 (PDT)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m6T8aNrH017955; Tue, 29 Jul 2008 11:36:36 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 29 Jul 2008 11:36:34 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 29 Jul 2008 03:36:32 -0500
Received: from 10.241.58.70 ([10.241.58.70]) by daebe101.NOE.Nokia.com ([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; Tue, 29 Jul 2008 08:36:32 +0000
User-Agent: Microsoft-Entourage/12.11.0.080522
Date: Tue, 29 Jul 2008 03:36:31 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Frits Haas <frits.haas@smilecoms.com>, 16ng@ietf.org
Message-ID: <C4B440BF.15E0B%basavaraj.patil@nokia.com>
Thread-Topic: [16NG] distributed (decentralised) ASN for voip over wimax
Thread-Index: AcjxSbJWKrVehLRKQgKHixREiFyyyAADIDxX
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAObw9SSE8J5KkMKzAV13Hr/CgAAAEAAAAFrHJBa5kTxEot8OIy+N/8MBAAAAAA==@smilecoms.com>
Mime-version: 1.0
X-OriginalArrivalTime: 29 Jul 2008 08:36:32.0031 (UTC) FILETIME=[33E6E2F0:01C8F156]
X-Nokia-AV: Clean
Subject: Re: [16NG] distributed (decentralised) ASN for voip over wimax
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: 16ng-bounces@ietf.org
Errors-To: 16ng-bounces@ietf.org

Hi Frits,

Don't know if this discussion on the 16NG list even makes sense. Anyway,
your question is about network planning and the topology of your network.
You could deploy a network that does not require all traffic to be
backhauled to a centralized CSN HA/core router.

You would likely get more feedback to your question about network
architecture and support for VoIP in the WiMAX forum's Network Working
group.  

-Raj 


On 7/29/08 2:07 AM, "ext Frits Haas" <frits.haas@smilecoms.com> wrote:

> Hi All,
> I hope someone can answer a question I have that some of the top vendors
> such as Motorola, Huawei and Nokia Siemens are battling to give me a
> straight answer to.
> 
> We are in the process of rolling out a 2.5 wimax network, designed purely
> around offering VOIP.
> 
> With the current ASN/AAA architecture, all traffic is aggregated at the CORE
> ASN, which means everything needs to be backhauled to the central ASN. This
> poses an extremely difficult scenario for us, as transmission costs are very
> high in the countries that we would like to launch our network (mostly
> Africa).
> 
> One solution would be a kind of distributed ASN architecture, to minimise
> backhaul traffic.
> Better yet, each BTS is able to route or switch voip packets to its
> destination, alleviating the need to backhaul the entire voice stream.
> Granted, you still need the AAA to authenticate, and the billing system
> needs to be aware of the call, but that traffic is minimal.
> 
> The question is, is anyone (vendor or otherwise) looking into designing or
> creating such a model with their equipment, and if so, what would the
> different solutions entail?
> My theory is that a simple router at each BTS (Base station) would be able
> to solve the problem.
> 
> Your questions and comments most welcome.
> 
> kind regards,
> :) Frits
> Frits Haas
> Senior Manager: Core IP Network Architecture
> Mobile: +27 (0) 83 280 8284 or +27 (0) 82 784 3248
> Fax: +27 (0) 8663 20 620
> Email and MSN : Frits.Haas@smilecoms.com
> Disclaimer  http://www.smilecoms.com/disclaimer
> 
> 
> 
> _______________________________________________
> 16NG mailing list
> 16NG@ietf.org
> https://www.ietf.org/mailman/listinfo/16ng

_______________________________________________
16NG mailing list
16NG@ietf.org
https://www.ietf.org/mailman/listinfo/16ng