Re: [lmap] What is broadband?

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Mon, 11 March 2013 20:43 UTC

Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FA621F90DA for <lmap@ietfa.amsl.com>; Mon, 11 Mar 2013 13:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.359
X-Spam-Level:
X-Spam-Status: No, score=-1.359 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sSznesW752Rt for <lmap@ietfa.amsl.com>; Mon, 11 Mar 2013 13:43:57 -0700 (PDT)
Received: from GB-IP-2.fcc.gov (mail4.fcc.gov [65.207.43.167]) by ietfa.amsl.com (Postfix) with ESMTP id C057C21F90BD for <lmap@ietf.org>; Mon, 11 Mar 2013 13:43:55 -0700 (PDT)
Received: from unknown (HELO GBPXCAS01V.fccnet.win.fcc.gov) ([65.207.43.140]) by GB-IP-2.fcc.gov with ESMTP; 11 Mar 2013 16:43:54 -0400
Received: from GBPXMB13V.fccnet.win.fcc.gov ([fe80::f1b8:d812:9a31:e47b]) by GBPXCAS01V.fccnet.win.fcc.gov ([fe80::ad35:7922:3623:4f10%12]) with mapi id 14.01.0438.000; Mon, 11 Mar 2013 16:43:52 -0400
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Sharam Hakimi <sharam.hakimi@exfo.com>, Marc Linsner <mlinsner@cisco.com>
Thread-Topic: [lmap] What is broadband?
Thread-Index: Ac4bsS4Fc9Tw+OlxRk6zqw2j7uy0dgAD2xrAALYUZ08=
Date: Mon, 11 Mar 2013 20:43:52 +0000
Message-ID: <E6A16181E5FD2F46B962315BB05962D019B4AF54@GBPXMB13V.fccnet.win.fcc.gov>
References: <CD639A87.3EA21%mlinsner@cisco.com>, <084CDC75FEC1E640B60338273BEACDFA023C4894@spboexc01.exfo.com>
In-Reply-To: <084CDC75FEC1E640B60338273BEACDFA023C4894@spboexc01.exfo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2002:a587:f015::a587:f015]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [lmap] What is broadband?
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lmap>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2013 20:43:58 -0000

The goal would be that the control and distribution components should be independent of the metrics, so that metrics can be added, both standardized ones and proprietary ones specific to a commercial provider or research network. If the control mechanism doesn't work for wireless metrics, for example, that might be an indication that it is not generic enough.

________________________________
From: lmap-bounces@ietf.org [lmap-bounces@ietf.org] on behalf of Sharam Hakimi [sharam.hakimi@exfo.com]
Sent: Monday, March 11, 2013 4:28 PM
To: Marc Linsner
Cc: lmap@ietf.org
Subject: Re: [lmap] What is broadband?

Marc,
I think the management agent that a wireless device might use would be somewhat different than a wire device as there are metrics that a wireless device has, that do not exist in a wire device. My opinion.

Sharam


From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of Marc Linsner
Sent: Monday, March 11, 2013 2:37 PM
To: Sharam Hakimi
Cc: lmap@ietf.org
Subject: Re: [lmap] What is broadband?

Sharam,

IMO, the only difference between wireless and wired are the test metrics that can be performed.  LMAP is concerned with the management of the measurement clients, controllers, and collectors.  Until further thought proves otherwise, I don't see any difference in the management of devices on any of the layer 1/2s.

The specifics you mention, Signal Strength and Roaming, should be dealt with in the definition of the test metric.

-Marc-



James,
I think mixing testing of wireless and wire technologies confuses the issues. One wireless is WiFi which is the extension of LAN and the other is the cellular network. They both have different requirements and two major conditions in both
                Signal Strength
                Roaming

have great effect on the achieved performance which does not exist in the wire condition . Some of these performance issues might also be better resolved in layer 2 rather than layer 3 and above. For example, before I run any throughput test I want to make sure that I have the highest strength signal possible be it WiFi or Cellular wireless connection ( and stay stationary during the test). On the other hand if I am trying to find the best location for signal strength a throughput test might not be the best tool for the job.

I would suggest to keep the two separate at least for the short term.

Sharam


From: lmap-bounces@ietf.org<mailto:lmap-bounces@ietf.org> [mailto:lmap-bounces@ietf.org] On Behalf Of James Miller
Sent: Thursday, March 07, 2013 10:58 PM
To: Shane Amante
Cc: Benoit Claise; Bugenhagen,Michael K; lmap@ietf.org<mailto:lmap@ietf.org>
Subject: Re: [lmap] What is broadband?

I agree Shane--was what I was trying to get at. :)

Our early FCC focus was basically the Access network but I think we're all making the point that the mix-n-match of the network measurement pieces will be driven by a particular user's use case.

For our FCC work, the focus (discussed in more detail in our reports) was on understanding the performance in the segment under the control of a carrier delivering broadband to a given consumer.  Naturally many other elements affect an end user's experience but our initial interest was on understanding that segment for the purposes of providing better information to the consumer about the portion of Internet performance that the carrier provides.  The FCC's focus and history is on that piece and so it makes sense that it might begin there, but a particular carrier's focus might mirror the access network focus, but perhaps with less market-trend orientation and more diagnostic in flavor.  Maybe LMAP together with other protocols (TR69 and other BBForum work for example) could benefit all those use cases.

In recent meetings we've discussed other more targeted mini-studies on things like CDN or in-home Wifi performance.  Other potential LMAP users already focus their work on these or other elements of the network.  I would envision the LMAP work could provide the glue between any of these elements and different use cases.  Worth noting that much of the initial discussions in the FCC's Next-Gen group were on the potential value of standardized interfaces between such different elements of measurement infrastructure.

Another element that's probably worth noting is that the use cases also may direct the actual tests that someone wants to run.  I would imagine the actual tests you might want to run for evaluating in-home LAN, access network, CDN, mobile networks may vary.  So I think the work on the test registry and other IPPM work on new tests will also improve our definitions and understanding of "broadband performance".

As always my personal views and not the FCC's.. possible valued at less than $.02  :)
On Thu, Mar 7, 2013 at 10:24 PM, Shane Amante <shane@castlepoint.net<mailto:shane@castlepoint.net>> wrote:
James, All,

On Mar 7, 2013, at 7:30 PM, James Miller <jamesmilleresquire@gmail.com<mailto:jamesmilleresquire@gmail.com>> wrote:
I believe that Henning had commented at some point that the LMAP definition he contemplated had "architecture" as the 'A' element but certainly access is an important piece.  I think one of the problems that has been discussed also on the LMAP and our FCC Next-Gen lists is that a complete view of LMAP performance measurements would implicate elements from the user's laptop, through wireless and other local LAN, carriers access networks, Tier 1 and other peering networks, the application host side and everything in between.  Clearly there would be a lot of technologies included within that functional scope.

I agree that access is important, but not to the exclusion of everything else that constitutes an Internet end-user customer experience or, alternatively, an Enterprise end-user customer experience -- which is what I believe you're saying above?  That's why it will be important to, at some point, figure out *if*, and then how, to try to segment the portions of the end-to-end path that you describe above so we can attribute good or bad performance to a particular portion of the path so that, ultimately, the correct network operator can be contacted to look into the problem further.  I do not believe that this requires us to break down the end-to-end path on a router-hop by router-hop basis, but rather we need to be able to identify 'sign posts' along the path that can correlate well to end-to-end path.

-shane




For reference, in the FCC Measuring Broadband America Program we focused on measurement from the consumers' broadband modem through the carriers network to where it connects to a tier one peering point.  LMAP should be able to address the broad mix of other use cases that would have a mix of other elements and motivations.

Graphic in Report at page 9. http://transition.fcc.gov/cgb/measuringbroadbandreport/2Methodology.pdf
On Thu, Mar 7, 2013 at 5:20 PM, Bugenhagen, Michael K <Michael.K.Bugenhagen@centurylink.com<mailto:Michael.K.Bugenhagen@centurylink.com>> wrote:
The word "access" should be key here as part of the definition provided we are talking about an Internet service, which is the second component.   I don't really  think we are building tests that won't work on smaller pipes so questioning if it really 'broadband' or not is correct IMO.



Sent from my iPhone

On Mar 7, 2013, at 9:41 AM, "Shane Amante" <shane@castlepoint.net<mailto:shane@castlepoint.net>> wrote:
Benoit,

On Mar 7, 2013, at 3:47 AM, Benoit Claise <bclaise@cisco.com<mailto:bclaise@cisco.com>> wrote:
Dear all,

I started to review the drafts, and I will start posting a few questions to the list.
Open questions, clarifying questions, in order to generate some discussions.
Disclaimer: I have not yet read the entire list archive. Apologize in advance if some points have been discussed already.

Here is my first question. What is broadband in the LMAP context?
Is it DSL, cable, ETTH, Fiber to the home?  Is LMAP technology independent?
And I see also "enterprise edge router", "cellular data or satellite" in draft-schulzrinne-lmap-requirements. In or out?
Or do we have in mind a phase approach, starting with the "enterprise edge router" first, and then home network?

Speaking for the network I operate, I'm very much an advocate of saying that "Enterprise Edge Router" is "in-scope".  We would very much benefit from a standards-based measurement enablement and collection regime vs. mostly proprietary, and non-scalable, approaches that exist today.

This is not to diminish the importance of similar test capabilities for residential broadband use-cases.  We absolutely need to work on those, as well.

With respect to priority, my hope is that we do not have to choose to prioritize one over the other.  Rather, I would hope that both can be developed in parallel, because both -- at least, IMO -- have a substantially overlapping set of requirements/features.

My $0.02,

-shane




Interestingly, I don't know what A stands for in LMAP, if it stands for something.
According to http://trac.tools.ietf.org/bof/trac/wiki/WikiStart, the A doesn't stand for anything.
However, looking at the different draft titles, there is some confusion.

   draft-linsner-lmap-use-cases-0 title is Large-Scale Broadband Measurement Use Cases

   draft-schulzrinne-lmap-requirements-00.txt title is Large-Scale Measurement of Broadband Performance

   draft-boucadair-lmap-considerations-00, Large scale Measurement of Access network Performance (LMAP):

      Requirements and Issues from a Network Provider Perspective

Some more discussions, on the mailing list or during the BoF, on this topic would be appreciated.

Regards, Benoit



_______________________________________________
lmap mailing list
lmap@ietf.org<mailto:lmap@ietf.org>
https://www.ietf.org/mailman/listinfo/lmap

_______________________________________________
lmap mailing list
lmap@ietf.org<mailto:lmap@ietf.org>
https://www.ietf.org/mailman/listinfo/lmap

_______________________________________________
lmap mailing list
lmap@ietf.org<mailto:lmap@ietf.org>
https://www.ietf.org/mailman/listinfo/lmap



_______________________________________________ lmap mailing list lmap@ietf.org<mailto:lmap@ietf.org> https://www.ietf.org/mailman/listinfo/lmap