Re: [lmap] Feedback on draft-eardley-lmap-framework-01

<philip.eardley@bt.com> Thu, 25 July 2013 14:51 UTC

Return-Path: <philip.eardley@bt.com>
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 5517321F9AF8 for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 07:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.439
X-Spam-Level:
X-Spam-Status: No, score=-103.439 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 JiS-oOvfkLvq for <lmap@ietfa.amsl.com>; Thu, 25 Jul 2013 07:51:48 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtp64.intersmtp.com [62.239.224.237]) by ietfa.amsl.com (Postfix) with ESMTP id 42B9F21F9AED for <lmap@ietf.org>; Thu, 25 Jul 2013 07:51:48 -0700 (PDT)
Received: from EVMHT67-UKRD.domain1.systemhost.net (10.36.3.104) by RDW083A008ED64.smtp-e4.hygiene.service (10.187.98.13) with Microsoft SMTP Server (TLS) id 8.3.298.1; Thu, 25 Jul 2013 15:51:47 +0100
Received: from EMV65-UKRD.domain1.systemhost.net ([169.254.1.253]) by EVMHT67-UKRD.domain1.systemhost.net ([10.36.3.104]) with mapi; Thu, 25 Jul 2013 15:51:47 +0100
From: philip.eardley@bt.com
To: jason.weil@twcable.com, lmap@ietf.org
Date: Thu, 25 Jul 2013 15:51:46 +0100
Thread-Topic: Feedback on draft-eardley-lmap-framework-01
Thread-Index: Ac6Iue+JkB9mX20GQROv2rsQmPcjnQAjEElg
Message-ID: <9510D26531EF184D9017DF24659BB87F35B8033851@EMV65-UKRD.domain1.systemhost.net>
References: <CE15C7F4.191A4%jason.weil@twcable.com>
In-Reply-To: <CE15C7F4.191A4%jason.weil@twcable.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_9510D26531EF184D9017DF24659BB87F35B8033851EMV65UKRDdoma_"
MIME-Version: 1.0
Subject: Re: [lmap] Feedback on draft-eardley-lmap-framework-01
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: Thu, 25 Jul 2013 14:51:54 -0000

Thanks!
In-line belwo
phil

From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of Weil, Jason
Sent: 24 July 2013 23:06
To: lmap@ietf.org
Subject: [lmap] Feedback on draft-eardley-lmap-framework-01

Here are my comments and questions on the draft:

Section 1. [use-cases]
Regulators: I would drop the word 'several' from this description. It reads as if regulators are targeting certain providers purposefully out of a group which is not typically the case.
---
The example given in Diversity seems to be another example supporting the interoperability benefits that come with the earlier bullet on Standardization.  A MA on a CPE router and another MA on a WiFi device behind the router or a MA running as a software client on a laptop/desktop might be  a better example?
---
Section 2.


   The MA functions are implemented either in specialised hardware or as

   code on general purpose devices like a PC, tablet or smartphone.  The

   Measurement Peer may be an LMAP device or a normal, non-LMAP device

   (for example if the MA measures the time for a DNS response or a

   webpage download from www.example.com<http://www.example.com>).



A Measurement Peer is an LMAP functional element. It would seem to me that as long as an entity performs in the role of a Measurement Peer it would be considered an LMAP device whether or not it was purpose built for a single test or simply performing as a Measurement Peer based on its normal operational role such as a recursive resolver. As such I don't believe a Measurement Peer would ever be considered a non-LMAP device if it was being used for a test by the MA.



[phil] so I'll re-phrase something like "The Measurement Peer may be a special-purpose device or a device performing its normal operational role (for example....



--

Section 3.


3.2. Each MA may only have a single Controller at any point in time - The 'may' in this sentence makes me wonder where the constraint exists. Is the constraint that it must only take direction from a single Controller at any given time?

[phil] yes

--
The topic on NAT an firewalls suggesting a pull model may be better as a separate constraint topic by itself.

[phil] seems a good suggestion to me




Thanks,


Jason

________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.