[lmap] LMAP - what next?

Dan Romascanu <dromasca@gmail.com> Fri, 05 May 2017 19:45 UTC

Return-Path: <dromasca@gmail.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 1E357126C25 for <lmap@ietfa.amsl.com>; Fri, 5 May 2017 12:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level:
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4DfDu9IvB8Mr for <lmap@ietfa.amsl.com>; Fri, 5 May 2017 12:45:04 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4BEA124217 for <lmap@ietf.org>; Fri, 5 May 2017 12:45:03 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id j29so13541556qtj.1 for <lmap@ietf.org>; Fri, 05 May 2017 12:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=TteXiTkQoYljse13aJIezdz7SAwfGrPmUifkIAhThQ8=; b=rTeeh6bpNXVrhW3o+y2jrPQXO91yP9xtKtfJzlVv9mcmbbQF5CTe9MLkaTeU48S2d3 jL/uRoEVKEsDHcBYzdUlJLq+aFUeISiBMOfG49pBlCJUC8NQFZuLQ/TG6sOzsSqAnWYh VMccKtiRu4r+E3115cEggJJ5h5Ls7n9RbQ7Bwej0FplcsbRkI3hlWTbgXPEamzXpSesG zhasfUoS4m1mnM7dykDCdmOq+Yyt5LxjkXwbXsaB9mCdhHEIPQWJBfycyPoqaH/VcRSX c3vgamw0ljPeWtxAqWTL5KHUQzXtzLo43HYDkMZtXOMA+omvtO8xqeCS0fM3Z+mDtkeO SKtA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TteXiTkQoYljse13aJIezdz7SAwfGrPmUifkIAhThQ8=; b=l58iZr7u4onIeYadX0Xum1JvZW5fu5lObBw994bLkPqd+63FuIft7g1RJ3YIkEBzLN En4y86HHB2LRTCmsF3lEGht5hhyEw7NmNVukZbwCR2lktwPc9knb1T5oECyft0C95D4V RrditD5sFnCS3jr7aSEb9Cc1gwZQVmA9QnQVK0MicZZsXOHmEt8AV4905mvMkQniOtIY LbauWHQALczPsuKQEjzNINXKYFETdAeasbuQZ61ksht3qh+JkhXzkQQr3fXKOkDbrlyb ++Kqe/5772Jin1m+d2Ypcq6mvV1MAEaXDFhnlWCntLY5fRJNeDsdpUVBEY4jfLqPJSeB 4c6Q==
X-Gm-Message-State: AODbwcDMv97jSuG/MLgWjfLI07/VG2xif3XBcB+DTOtcllxOMauOsGwk rwQhnZzC3CXXrNkbzgky8hjWOGpjpr+i
X-Received: by 10.200.47.36 with SMTP id j33mr7703880qta.175.1494013502843; Fri, 05 May 2017 12:45:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.19.39 with HTTP; Fri, 5 May 2017 12:45:02 -0700 (PDT)
From: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 5 May 2017 22:45:02 +0300
Message-ID: <CAFgnS4UAvR=9f0zNiSbp5Y23hbULFxCVRn6WNyA5_vMBFU2-xg@mail.gmail.com>
To: lmap@ietf.org
Content-Type: multipart/alternative; boundary=001a113c01bc20740f054ecc2006
Archived-At: <https://mailarchive.ietf.org/arch/msg/lmap/I-PczaJBNBT7UWbP1neu5BfFkuA>
Subject: [lmap] LMAP - what next?
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: Fri, 05 May 2017 19:45:05 -0000

Hi,

With the LMAP WG having shipped the IM and DM documents to the RFC Editor,
it's time to discuss what next.

Specifically, I have two questions:

- what to do with draft-ietf-lmap-restconf?
- is there any new work for lmap on short term, or should we rather focus
on implementations and revisit the issue in a year or two?

Comments and discussions are welcome.

Regards,

Dan