IETF Logo Mail Archive

[lmap] Discuss LMAP at IETF 101

Holger Wiehen <holger@nic.br> Tue, 20 March 2018 09:17 UTC

Return-Path: <holger@nic.br>
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 09AA8124235 for <lmap@ietfa.amsl.com>; Tue, 20 Mar 2018 02:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level:
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
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 vlkj2wSF5ceI for <lmap@ietfa.amsl.com>; Tue, 20 Mar 2018 02:17:47 -0700 (PDT)
Received: from mail.nic.br (mail.nic.br [200.160.4.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF2A1120227 for <lmap@ietf.org>; Tue, 20 Mar 2018 02:17:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.nic.br (Postfix) with ESMTP id 8CF44157E0B for <lmap@ietf.org>; Tue, 20 Mar 2018 06:17:42 -0300 (-03)
X-Virus-Scanned: Debian amavisd-new at mail.nic.br
Authentication-Results: mail.nic.br (amavisd-new); dkim=pass (1024-bit key) header.d=nic.br
Received: from mail.nic.br ([127.0.0.1]) by localhost (mail.nic.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIEDE3Wg5SQL for <lmap@ietf.org>; Tue, 20 Mar 2018 06:17:40 -0300 (-03)
Received: from [IPv6:2a02:c7d:51f4:de00:4963:672b:760d:8ed7] (unknown [IPv6:2a02:c7d:51f4:de00:4963:672b:760d:8ed7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: holger@nic.br) by mail.nic.br (Postfix) with ESMTPSA id 242DD157DD1 for <lmap@ietf.org>; Tue, 20 Mar 2018 06:17:39 -0300 (-03)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.br; s=dkim; t=1521537460; bh=4gbvbjjYt0ElJrg/hNltrwPAbYe+LEL7wR4b6iJJ1zs=; h=From:Subject:Date:To:From; b=mHkbqYIy+gYOvEkmpaGFIK7b39bI1R+3GQuoExKsMj/9L41B/bdZDrmhOVwbwvInk VgYqa09NQF/flYhj4JHUXU4oEz/Rck0bRUwCLW05b/5NJ7RB53I1dx/ho21IFElXpk pMmVRVc/nEWvdcwbCVsVUDmL6hVVrv2s+QrWbF/M=
From: Holger Wiehen <holger@nic.br>
Content-Type: multipart/alternative; boundary="Apple-Mail=_05E7A0C0-A1CF-4261-A56B-35E5BB7F0CF4"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <0C6CA7BA-ED9B-44E0-97DB-81B90B22623B@nic.br>
Date: Tue, 20 Mar 2018 09:17:37 +0000
To: lmap@ietf.org
X-Mailer: Apple Mail (2.3445.5.20)
DMARC-Filter: OpenDMARC Filter v1.3.1 mail.nic.br 242DD157DD1
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/xfYnFOkjXRFQrJiv84YoljiB2u8>
Subject: [lmap] Discuss LMAP at IETF 101
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Mar 2018 09:17:49 -0000

Former LMAP WG,

While porting measurement software to use the LMAP model for scheduling and reporting, I came across some questions.

Is anyone interested to discuss the LMAP information / data model at IETF 101? I would greatly appreciate a short conversation in person.


Holger Wiehen 
Analista de Projetos 
SIMET - Sistemas de Medição de Tráfego Internet 
+55 11 5509-3537 R.: 4114 
www.nic.br <http://nic.br/>

v2.23.0 | Report a Bug | By Email