All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fallon, Michael F <michael.f.fallon@intel.com>
To: ofono@ofono.org
Subject: Re: [RFCv2] doc: Proposal for LTE/IMS API
Date: Mon, 14 Feb 2011 14:35:02 -0700	[thread overview]
Message-ID: <FF74A84A5BBBCA439D6B6F41A35AAF010E9E2A7C@azsmsx502.amr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

>> In theory there might be more than one IMS APN for a operator,
>> but I really don't see this as a real life scenario for this.
>> If anyone disagrees please speak out and explain...

One such scenario is the in-vehicle use model, where the ISP provides network connectivity via one APN and the auto manufacturer has network connectivity through a separate, private, and independent APN. Connectivity, billing, bandwidth, reliability, roaming etc are all independent for each network. For example, auto manufacturer X may contract with ISP Y for remote access to the car, while the owner of the car may prefer ISP Z for personal use.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5564 bytes --]

             reply	other threads:[~2011-02-14 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 21:35 Fallon, Michael F [this message]
2011-02-14 21:39 ` [RFCv2] doc: Proposal for LTE/IMS API Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2011-02-08 14:29 Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-08 14:47 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-08 16:22   ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-09  7:02     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2011-02-09 16:35       ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-10  9:30   ` Kjetil ASDAL
2011-02-08 15:20 ` Soum, RedouaneX
2011-02-08 16:42   ` Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FF74A84A5BBBCA439D6B6F41A35AAF010E9E2A7C@azsmsx502.amr.corp.intel.com \
    --to=michael.f.fallon@intel.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.