Re: [lmap] One example of a "passive measurement peer"

Nalini Elkins <nalini.elkins@insidethestack.com> Tue, 11 March 2014 15:16 UTC

Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 871E11A0757 for <lmap@ietfa.amsl.com>; Tue, 11 Mar 2014 08:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJ6CWPLpWspM for <lmap@ietfa.amsl.com>; Tue, 11 Mar 2014 08:15:59 -0700 (PDT)
Received: from nm14-vm4.access.bullet.mail.bf1.yahoo.com (nm14-vm4.access.bullet.mail.bf1.yahoo.com [216.109.115.19]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7181A0746 for <lmap@ietf.org>; Tue, 11 Mar 2014 08:15:59 -0700 (PDT)
Received: from [66.196.81.156] by nm14.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Mar 2014 15:15:53 -0000
Received: from [66.196.81.133] by tm2.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Mar 2014 15:15:53 -0000
Received: from [127.0.0.1] by omp1009.access.mail.bf1.yahoo.com with NNFMP; 11 Mar 2014 15:15:53 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 315101.64449.bm@omp1009.access.mail.bf1.yahoo.com
Received: (qmail 65351 invoked by uid 60001); 11 Mar 2014 15:15:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1394550952; bh=oPWaEiBo0h07Jkg+zhqnk4UjIZp5TFtXg2qOr3A9if4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Apnq85k/A2IanbAoGJXc0Tl2UYyYELch0nAcZVTTqNNfoo2q2ePn4XM06vo4D4DaDrJQMfFqVAOXIrH4n2DauCljODKK/zKgtvo54+VdzLNe0SN/MQM5nIswoDbeRYlEI8fze8svSEAXQ0VR7+/EC7nzLBnD5+XOj2T2SrJGhPI=
X-YMail-OSG: HzcbiOIVM1ldw2tcGIblL5NBF7ywZm1oUXAYoN2NfcuenGW MSuXrg.WGkZU2..On.09X4DL2yUph7ana4313_0ftGuAwIDYos.WV4Ae6Iva zaATVa_tntKuMWZrT9Np.cdfCZFdb0SwbjR5UknYULOQfEiJx9Hc8p4khIll uc6xHdcN3fo4A7_iTske_RROS87ut7j5waYeGCgIDQRNSP7TlFAfD1_w_mlH rNPC_Ty.xC2s3NoNdS3zXomAbXSznw1_9.WZcu5w0AGs_xAVn3dH14NmGlmw wKlek3c6BVB_TtiBZ1XnQDXcvLve8hNMcwKs1cNfoRiF_67R_rKHakFEVmeS tRXknbJaNaUUTLacqnBs9aHUWLEyatrt1FmSLkhrPpkoGq3moaDPUn7s6ufg 9v2q053eeNxJlpGikgyJTDBIuA4t1O88wXqYmaFmIPuzp9I2TnqAEEniKYR_ tKUPpNbuO3GVam1vCRCpiJX5jyUtMl9UaVD.nr4UsoGYCJdBktR3DXhuHYvZ Duhl1yPj5lTr_gEaEPjFbDtyg6EWHTHvtjfhm56sWkNUYu4vCsof.j4v48zy pzaTI2jsZXXl1hRqidq.GtdzvDv6f_gOW_C.22PDbyWQs0jeM8Br7ArgW.Sy duv88Vcrzi0yfA9G_4Lt5zvOWBIXlf1iKA.79.SenJYfEGkhVKFHNuIsKVjL 2ug6c82MqQo3IQSuHXQLZdNbLtB.Oe4k5Y5nOhfbt1gg7Zo2u5OiPusNrrqY zUyyPCQqtB1LtBjXqHkzjMTf8FH5PO2_x76WE8VF5_JrlSKFPOqEQto6_kVr mzWqqSHV6gT_NWlbADx7G9hC7aGPanPVan7eAsRb4SRRaWbiuiMLv18Qd8dw 69x_V4kEeYLYkVmh4uUDWSVPS
Received: from [24.130.37.147] by web2804.biz.mail.ne1.yahoo.com via HTTP; Tue, 11 Mar 2014 08:15:52 PDT
X-Rocket-MIMEInfo: 002.001, R3V5cywKCklmIEkgbG9vayBpbiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1lYXJkbGV5LWxtYXAtdGVybWlub2xvZ3ktMDIsIEkgc2VlIHRoZSBkZWZpbml0aW9uIG9mIG1lYXN1cmVtZW50IHBlZXIgYXM6CgpNZWFzdXJlbWVudCBQZWVyOiBUaGUgZnVuY3Rpb24gdGhhdCByZWNlaXZlcyBjb250cm9sIG1lc3NhZ2VzIGFuZCB0ZXN0IHBhY2tldHMgZnJvbSBhIE1lYXN1cmVtZW50IEFnZW50IGFuZCBtYXkgcmVwbHkgdG8gdGhlCk1lYXN1cmVtZW50IEFnZW50IGFzIGRlZmluZWQgYnkgdGhlIE0BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.177.636
References: <CAH56bmCPk0XcxdpgNg=U1w+5EJp-sXU51YT+DTWBazjHBwVLjg@mail.gmail.com> <9904FB1B0159DA42B0B887B7FA8119CA2E44A926@AZ-FFEXMB04.global.avaya.com> <98184277-C341-4622-ABED-990702554F8C@trammell.ch> <A68F3CAC468B2E48BB775ACE2DD99B5E04AACF15@podcwmbxex505.ctl.intranet> <20140311145912.GA78853@elstar.local> <75C0E47A1889264493A2DCB2869AC09633C7083F@xmb-rcd-x15.cisco.com>
Message-ID: <1394550952.54174.YahooMailNeo@web2804.biz.mail.ne1.yahoo.com>
Date: Tue, 11 Mar 2014 08:15:52 -0700
From: Nalini Elkins <nalini.elkins@insidethestack.com>
To: "Aamer Akhter (aakhter)" <aakhter@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Bugenhagen, Michael K" <Michael.K.Bugenhagen@centurylink.com>
In-Reply-To: <75C0E47A1889264493A2DCB2869AC09633C7083F@xmb-rcd-x15.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/lmap/MPnfe6TtGhvUds6Lfd2eiUIO00Y
Cc: 'Brian Trammell' <ietf@trammell.ch>, "'lmap@ietf.org'" <lmap@ietf.org>, 'Matt Mathis' <mattmathis@google.com>, 'Dan Romascanu' <dromasca@avaya.com>
Subject: Re: [lmap] One example of a "passive measurement peer"
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
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: Tue, 11 Mar 2014 15:16:02 -0000

Guys,

If I look in http://tools.ietf.org/html/draft-eardley-lmap-terminology-02, I see the definition of measurement peer as:

Measurement Peer: The function that receives control messages and test packets from a Measurement Agent and may reply to the
Measurement Agent as defined by the Measurement Method. 

Is this correct?

Now, imagine the following scenario in a hybrid measurement technique:

1.  In the MA, the hybrid technique is to have the MA to append x bytes of diagnostic data to each passive packet.  For example, via a command to the operating system.

2.  The MA resides in the client

3. It would be ideal to have the partner that the client is having the session with (let's call it "server") also participate in this appending of x bytes of diagnostic data from his side.  (Leaving aside for the moment the potential for this to be a DoS vector.  That is a separate discussion). 

4.  In this case, could the MA not ask the "other end" to participate in extra data gathering?  This would be a control message from an MA as defined above.

Would this be an example of a Measurement Peer in a hybrid scenario?

I ask because this is what we are thinking we may want to do.

What am I missing?  Is my understanding of this OK?  Please advise.

Thanks,

Nalini Elkins
Inside Products, Inc.
(831) 659-8360
www.insidethestack.com



________________________________
From: Aamer Akhter (aakhter) <aakhter@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>; "Bugenhagen, Michael K" <Michael.K.Bugenhagen@centurylink.com> 
Cc: 'Brian Trammell' <ietf@trammell.ch>; 'Dan Romascanu' <dromasca@avaya.com>; 'Matt Mathis' <mattmathis@google.com>; "'lmap@ietf.org'" <lmap@ietf.org> 
Sent: Tuesday, March 11, 2014 8:03 AM
Subject: Re: [lmap] One example of a "passive measurement peer"


I agree on the removal of 'passive' in 'passive measurement peer' but if I remember correctly where was some discontent with just that as the solution. 

Do we have any clarity on where the discontent was coming from 

-----Original Message-----
From: lmap [mailto:lmap-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
Sent: Tuesday, March 11, 2014 10:59 AM
To: Bugenhagen, Michael K
Cc: 'Brian Trammell'; 'lmap@ietf.org'; 'Matt Mathis'; 'Dan Romascanu'
Subject: Re: [lmap] One example of a "passive measurement peer"

Hi,

I do not think we need the term 'passive measurement peer' in the framework so perhaps the best thing is to not spent cycles trying to define it.

/js

On Tue, Mar 11, 2014 at 01:36:23PM +0000, Bugenhagen, Michael K wrote:
> Just my 2 cents - but a word on future proofing... 
> 
> The word passive is contextual...
> 
> Which directly infers that we should "contextualize" it buy saying "x" passive.
> As the technology disturbers add new dimensions that also contain passive/active stuff this is going to get more confused....
> 
> We're seriously having a problem with this at NFV / Cloud technology SDO's where we've virtualized NIC's (Vnic's) and Vswitches both of which can be suspended (stopped)..
> 
> It may prove difficult to do passive measurements on a virtual x,y,z component.
> Given Broadband Modems have this virtualized stuff, we should consider future proofing our terms.
> 
> Summary - contextualizing passive may be a great thing to future proof... for virtualization, those proof of concepts are in the works now.
> 
> Cheers,
> Mike
> 
> 
> 
> -----Original Message-----
> From: lmap [mailto:lmap-bounces@ietf.org] On Behalf Of Brian Trammell
> Sent: Tuesday, March 11, 2014 8:30 AM
> To: Dan Romascanu
> Cc: Matt Mathis; lmap@ietf.org
> Subject: Re: [lmap] One example of a "passive measurement peer"
> 
> hi Dan,
> 
> Hm. I don't really consider this passive measurement -- we discussed this a bit in the ippm registry design team, but I'm pretty sure there's a difference between (1) metrics derived from the operation of a protocol at one of the endpoints participating in it and (2) metrics derived from the passive observation of packets emitted by those protocols. I've always thought of passive measurement as the latter, and (1) as something like "endpoint measurement", since metrics in (1) can also be derived from internal state at each endpoint not synchronized over the protocol or otherwise hard to derive. 
> 
> One could say that a midpath observation point (i.e. any observation point other than an endpoint) has as many "passive peers" as there are observable senders and recipients, while an "endpoint measurement agent" would have a single "endpoint peer".
> 
> (This becomes a much more interesting distinction as soon as you 
> consider encrypting absolutely everything you can, of course. At that 
> point everything you're reduced to endpoint measurement for everything 
> other than the "envelope" and/or things you derive through behavioral 
> traffic analysis. But that's a separate discussion, I think.)
> 
> In any case, I stand by my statement that I'd like to see peers defined _only_ as much as is absolutely necessary to make sense of the resulting control and reporting protocols.
> 
> Cheers,
> 
> Brian
> 
> 
> On 10 Mar 2014, at 14:31, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote:
> 
> > My other example of a 'passive management peer' is an RTP peer which receives RTCP messages about the state of the other side of the connection and the parameters of the received traffic at the other end. All these are part of RTP/RTCP, there is no interaction between the controller and the MP, so I believe it can be considered passive in LMAP terms.
> >  
> > Regards,
> >  
> > Dan
> >  
> >  
> > From: lmap [mailto:lmap-bounces@ietf.org] On Behalf Of Matt Mathis
> > Sent: Friday, March 07, 2014 12:11 PM
> > To: lmap@ietf.org
> > Subject: [lmap] One example of a "passive measurement peer"
> >  
> > From the Internet Archive:
> >  
> > http://web.archive.org/web/20071005130953/http://www-didc.lbl.gov/SC
> > NM/
> > 
> > Thanks,
> > --MM--
> > The best way to predict the future is to create it.  - Alan Kay
> > 
> > Privacy matters!  We know from recent events that people are using our services to speak in defiance of unjust governments.   We treat privacy and security as matters of life and death, because for some users, they are.
> > _______________________________________________
> > lmap mailing list
> > lmap@ietf.org
> > https://www.ietf.org/mailman/listinfo/lmap
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap
> 
> _______________________________________________
> lmap mailing list
> lmap@ietf.org
> https://www.ietf.org/mailman/listinfo/lmap

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

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

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