[16NG] distributed (decentralised) ASN for voip over wimax
Frits Haas <frits.haas@smilecoms.com> Tue, 29 July 2008 07:08 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 180593A6AD2; Tue, 29 Jul 2008 00:08:24 -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 DF09B3A6AD8 for <16ng@core3.amsl.com>; Tue, 29 Jul 2008 00:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 uJFRwcLsmPR1 for <16ng@core3.amsl.com>; Tue, 29 Jul 2008 00:07:18 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by core3.amsl.com (Postfix) with ESMTP id 97C003A6AD2 for <16ng@ietf.org>; Tue, 29 Jul 2008 00:07:17 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so1607279nfh.39 for <16ng@ietf.org>; Tue, 29 Jul 2008 00:07:27 -0700 (PDT)
Received: by 10.210.141.4 with SMTP id o4mr7103935ebd.154.1217315247395; Tue, 29 Jul 2008 00:07:27 -0700 (PDT)
Received: from FritsHaas ( [196.38.255.202]) by mx.google.com with ESMTPS id j8sm25499523gvb.1.2008.07.29.00.07.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 29 Jul 2008 00:07:26 -0700 (PDT)
To: 16ng@ietf.org
Date: Tue, 29 Jul 2008 09:07:02 +0200
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAObw9SSE8J5KkMKzAV13Hr/CgAAAEAAAAFrHJBa5kTxEot8OIy+N/8MBAAAAAA==@smilecoms.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcjxSbJWKrVehLRKQgKHixREiFyyyA==
Content-Language: en-za
x-cr-hashedpuzzle: AND1 AU2v BXJq Bat5 Bnvp ElYP FTwF For/ F7JC F7K1 GsDI GyxD HSKq Hnbm IDBA K8+h; 1; MQA2AG4AZwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {FEAB8BB7-E1E1-47BE-B801-8128D2CAABB6}; ZgByAGkAdABzAC4AaABhAGEAcwBAAHMAbQBpAGwAZQBjAG8AbQBzAC4AYwBvAG0A; Tue, 29 Jul 2008 07:07:00 GMT; ZABpAHMAdAByAGkAYgB1AHQAZQBkACAAKABkAGUAYwBlAG4AdAByAGEAbABpAHMAZQBkACkAIABBAFMATgAgAGYAbwByACAAdgBvAGkAcAAgAG8AdgBlAHIAIAB3AGkAbQBhAHgA
x-cr-puzzleid: {FEAB8BB7-E1E1-47BE-B801-8128D2CAABB6}
From: Frits Haas <frits.haas@smilecoms.com>
Subject: [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 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] distributed (decentralised) ASN for voip o… Frits Haas
- Re: [16NG] distributed (decentralised) ASN for vo… Basavaraj Patil
- Re: [16NG] distributed (decentralised) ASN for vo… Jai-Jin Lim