Re: [mif] AMSS/Brew Multi-interface handling
Hui Deng <denghui02@gmail.com> Fri, 09 April 2010 15:31 UTC
Return-Path: <denghui02@gmail.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A2EC28C0CE for <mif@core3.amsl.com>; Fri, 9 Apr 2010 08:31:36 -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=[AWL=0.000, 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 Gj8OtuAT4ugu for <mif@core3.amsl.com>; Fri, 9 Apr 2010 08:31:35 -0700 (PDT)
Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by core3.amsl.com (Postfix) with ESMTP id 68DEF3A683A for <mif@ietf.org>; Fri, 9 Apr 2010 08:31:32 -0700 (PDT)
Received: by iwn27 with SMTP id 27so2425086iwn.5 for <mif@ietf.org>; Fri, 09 Apr 2010 08:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2wDMqn3QASSXRgquNbaFb2Eti8iPwyeZHpBw+334ZKY=; b=b+3BWV1NPE0zqelg5B9iicWkXzmMmnwc51lMkE1VabCJVdoMJfpfj3RWHa+InpsuPX upZml0W6DMcc19qdCN4ig4tyYCB6xW2JQtrKUBu28Spicp+wX8LonSfoVIhrGd7j11d4 XVrGNSvE8XWw+YAPc6ZmHtRFygJ2MVFqdrKBg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qQAuDMvYdHElj8Gyz/vZEDF0wWFIXbH4ZyhbtrkzSnD2HRD4NamiegtOyb82xgpV4P 8Mzb82mPvWZPXeo/h7HyZrpu2FWyrI61K5xvO6Od7aLy3kSHBZp+gVnRH1JRzR0QHeKN 0iLNxA0Iv6Gn9Wi88E4xPIdepR275j32ZI+8M=
MIME-Version: 1.0
Received: by 10.231.152.202 with HTTP; Fri, 9 Apr 2010 08:31:25 -0700 (PDT)
In-Reply-To: <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com>
References: <d3886a520907290158o33705c50m31e848d2b20c764b@mail.gmail.com> <d3886a520908160241k52ede41bpad57325a1c741f3b@mail.gmail.com>
Date: Fri, 09 Apr 2010 23:31:25 +0800
Received: by 10.231.154.207 with SMTP id p15mr73381ibw.91.1270827085771; Fri, 09 Apr 2010 08:31:25 -0700 (PDT)
Message-ID: <w2i1d38a3351004090831gc64ac111ia0baf446f61e443f@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: George Tsirtsis <tsirtsis@googlemail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: mif <mif@ietf.org>
Subject: Re: [mif] AMSS/Brew Multi-interface handling
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2010 15:31:36 -0000
Hi, George, just two clarifications AMSS/Brew DNS configuration is interface based other than host based? secondly, network profile could identify only APN other than PDP context? thanks -Hui 2009/8/16 George Tsirtsis <tsirtsis@googlemail.com>: > Hi all, > > I sent this to Margaret during the IETF meeting but I did not hear > back from her. Maybe it got lost in the IETF noise so I thought I > might as well forward this to the list. > > I hope it helps. > > George > > ---------- Forwarded message ---------- > From: George Tsirtsis <tsirtsis@googlemail.com> > Date: Wed, Jul 29, 2009 at 9:58 AM > Subject: AMSS/Brew Multi-interface handling > To: mrw@sandstorm.net > > > Hi Margaret, > > Here is a description of how multi-interface support is handled by > Advanced Mobile Station Software (AMSS) that comes with Brew OS for > all Qualcomm chipsets (e.g., MSM, Snapdragon etc). I hope this is > helpful information for draft-mrw-mif-current-practices. > > Let me know if you have any questions. > > Regards > George Tsirtsis (wearing a Qualcomm hat) > > ----------------------------------------------------------------------------------------------------- > > > Multiple Interface Handling - Qualcomm AMSS/Brew Mobile Platform > > AMSS supports a concept of “netpolicy” which allows each application > to specify the type of network connectivity desired. The netpolicy > contains parameters such as access technology, IP version type and > network profile. Access technology could be a specific technology > type such as CDMA or WiFi or could be a group of technologies, such as > ANY_Cellular or ANY_Wireless. IP version could be one of Ipv4, Ipv6 > or Default. The network profile identifies a type of network domain > or service within a certain network technology, such as 3GPP APN or > Mobile IP Home Agent. It also specifies all the mandatory parameters > required to connect to the domain such authentication credentials and > other optional parameters such as QoS attributes. Network Profile is > technology specific and set of parameters contained in the profile > could vary for different technologies. > > Two models of network usage are supported. > > Applications requiring network connectivity specify an appropriate > netpolicy in order to select the desired network. The netpolicy may > match one or more network interfaces. AMSS system selection module > selects the best interface out of the ones that match the netpolicy > based on various criteria such as cost, speed or other provisioned > rules. Application explicitly starts the selected network interface > and, as a result, the application also gets bound to the corresponding > network interface. All outbound packets from this application are > always routed over this bound interface using the source address of > the interface. > Alternately, applications may rely on a separate connection manager to > control (start/stop) the network interface. In this method, > applications are not necessarily bound to any one interface. All > outbound packets from such applications are routed on one of the > interfaces that match its netpolicy. The routing decision is made > individually for each packet and selects the best interface based on > the criteria described above and the destination address. Source > address is always that assigned to the interface used to transmit the > packet. > > Note that all of the routing/interface selection decisions are based > on the netpolicy and not just destination address to avoid overlapping > private Ipv4 address issue. This also allows multiple (logical) > interfaces to be configured with the same IP address, for example, to > handle certain tunnelling scenarios. Applications that do not > specify a netpolicy are routed by AMSS to the best possible interface > using the default netpolicy. Default netpolicy could be pre-defined > or provisioned by the administrator or operator. Hence default > interface could vary from device to device and also depends upon the > available networks at any given time. > AMSS allows each interface to be configured with its own set of DNS > configuration parameters – a list of DNS servers, domain names etc. > Interface selected to make a DNS resolution is the one to which > application making the DNS query is bound. Applications can also > specify a different netpolicy as part of DNS request to select another > interface for DNS resolution. Regardless, all the DNS queries are > sent only over this selected interface using the DNS configuration > from the interface. DNS resolution is first attempted with the > primary server configured in the interface. If a response is not > received, the queries are sent to all the other servers configured in > the interface in a sequential manner using a backoff mechanism. > _______________________________________________ > mif mailing list > mif@ietf.org > https://www.ietf.org/mailman/listinfo/mif >
- [mif] AMSS/Brew Multi-interface handling George Tsirtsis
- Re: [mif] AMSS/Brew Multi-interface handling Margaret Wasserman
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien
- Re: [mif] AMSS/Brew Multi-interface handling Hui Deng
- Re: [mif] AMSS/Brew Multi-interface handling Laganier, Julien