Re: [hops] Proposed Charter for Measurement and Analysis for Protocols (MAP) Research Group

DIEGO LOPEZ GARCIA <> Fri, 27 November 2015 17:17 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7FC691B36CC for <>; Fri, 27 Nov 2015 09:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.485
X-Spam-Status: No, score=-0.485 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id caMMLlbPJ25S for <>; Fri, 27 Nov 2015 09:17:29 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2240A1B36CA for <>; Fri, 27 Nov 2015 09:17:27 -0800 (PST)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 417CA1B83D3 for <>; Fri, 27 Nov 2015 18:17:25 +0100 (CET)
Received: from (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2666B1B83A3 for <>; Fri, 27 Nov 2015 18:17:25 +0100 (CET)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 27 Nov 2015 18:17:24 +0100
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.1.331.20; Fri, 27 Nov 2015 17:17:23 +0000
Received: from ([]) by ([]) with mapi id 15.01.0331.023; Fri, 27 Nov 2015 17:17:23 +0000
To: "" <>
Thread-Topic: [hops] Proposed Charter for Measurement and Analysis for Protocols (MAP) Research Group
Thread-Index: AQHRKD6kXx3sI/uEw02GwsSFKcHXrJ6wBVqAgAAJCQCAABASgA==
Date: Fri, 27 Nov 2015 17:17:22 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; DB4PR06MB0622; 5:9B1LYqewpLUu5omMcLSJ716jRXUtu8dAwy6Mqi5hNx4JKYjTUR5qhKLVYPotcteODTW9xgD+/WuzmwMtG7eSb72Q4+OrzcYTK9cAc0Ge7e3Dj+qXukvOtj/QsBZk1Rgim8aCmzVmB1bJL9Y+i63Rxw==; 24:jV2Pk03MZSiUzIC3IJaQtAvqbD5RsSDY29BIuzWiAGvehNtvkf5sfVfPIgYxyE1yLysk5LLjKmuL7mPNXDIJqxYjK5ld2Jld5827IWpnmu4=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB0622;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(40392960112811);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(520078)(3002001)(10201501046); SRVR:DB4PR06MB0622; BCL:0; PCL:0; RULEID:; SRVR:DB4PR06MB0622;
x-forefront-prvs: 0773BB46AC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(252514010)(54524002)(199003)(52604005)(189002)(24454002)(66654002)(377454003)(16236675004)(5004730100002)(97736004)(82746002)(50986999)(92566002)(19617315012)(2900100001)(10400500002)(76176999)(15975445007)(11100500001)(54356999)(36756003)(5008740100001)(575784001)(77096005)(86362001)(450100001)(66066001)(2950100001)(101416001)(5001960100002)(189998001)(33656002)(81156007)(110136002)(5002640100001)(83716003)(107886002)(122556002)(1096002)(106116001)(2351001)(586003)(2501003)(19580405001)(1220700001)(105586002)(106356001)(40100003)(6116002)(102836003)(3846002)(87936001)(19580395003)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB0622;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_711781760A7C45ED80B4A7FFF3710D88telefonicacom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Nov 2015 17:17:22.9985 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR06MB0622
Archived-At: <>
Subject: Re: [hops] Proposed Charter for Measurement and Analysis for Protocols (MAP) Research Group
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Measuring deployability of new transport protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Nov 2015 17:17:35 -0000


I support this charter, and Aaron’s suggestion as well.

Be goode,

On 27 Nov 2015, at 17:19 , Aaron Falk <<>> wrote:

Hi Joachim-

Good points but I would suggest the charter stay fairly vague on the subjects other than allowing them to be in-scope for the RG, for exactly the reason you suggest (it can be a distraction).  Perhaps just adding "and best practices" to the end of the first bullet would open the door without becoming an attractive nuisance. [*]


* -

On Fri, Nov 27, 2015 at 10:47 AM, Joachim Fabini <<>> wrote:
Hash: SHA1

Hi Brian,

I support the charter, thanks for revising it, and full consent to
Ethan's statement: "landing pad" for the IMC community reads
excellent, nice wording.

One question (perhaps a minor rewording can help): is "collaborations
to share data supporting these measurements" equivalent to "defining
repositories and sharing meaningful methods, measurement results,
measurement context and limitations of data sets" as discussed in
Yokohama? It's not clear to me what "supporting these measurements"
refers to exactly. It could mean "sharing of successful measurement
methods and setups" rather than "sharing of measurement results".

Second, is it needed|meaningful to explicitly mention legal aspects
related to data sharing as within/outside of the MAP charter? Sharing
data means dealing with country-specifics, licensing terms, privacy
vs. usability, etc. As such, legal aspects are implicitly part of the
charter. My feeling is that MAP should propose guidelines for sharing
measurement data, and that such guidelines could be really helpful for
the community. However, the discussion on the ietf94-attendees mailing
list is a fair warning to be _very_ careful with discussions on any
legal aspects (in particular privacy). There's a high risk to lose
focus - perhaps we can delegate this subtask to the hrpc RG. ;)

many thanks,

On 26.11.2015 12:35, Brian Trammell wrote:
> Greetings, all,
> Following discussions at the HOPS proposed RG meetings in Prague
> and Yokohama, as well as at the RAIM workshop before Yokohama,
> we've revised the charter to reflect what we think the community
> wants out of such an RG. Note that given the slightly expanded
> scope of this charter, though, we've decided to rename the proposed
> RG to Measurement and Analysis for Protocols (MAP).
> Comments on the proposed charter below are welcome at
> Measurement and Analysis for Protocols (MAP) RG
> ===============================================
> Our Internet has grown into something that differs from what was
> envisioned. Its protocols sometimes operate in an environment other
> than than that for which they were designed. For instance, some
> network elements treat some protocols differently than others and
> those protocols themselves are sometimes reused and abused in ways
> initially unforseen. The Measurement and Analysis for Protocols
> (MAP) Research Group (RG) explores such phenomena by measurement
> with the aim to inform protocol engineering and practice.
> Many protocol engineering efforts in a standards development
> context, as well as best practices for the operation of
> IETF-defined protocols, can benefit from insight provided by
> Internet measurements of various kinds. Likewise, Internet
> measurement research efforts can stand to gain from contacts with
> the IETF. The Measurement and Analysis for Protocol Engineering
> (MAP) Research Group aims to provide a forum for interchange
> between these two communities, supporting:
> - exchange of measurement-derived insight, - discussion of
> techniques for measurement relevant for protocol engineering and
> network operations, - collaborations to share data supporting these
> measurements, and - a "landing pad" in general for the Internet
> measurement community to introduce its efforts to the IETF
> Measurements of any layer of the Internet protocol stack or aspect
> of Internet operations are in-scope for the RG, provided they are
> relevant to protocol engineering work within the IETF, or the
> operation of IETF protocols.
> Membership ----------
> Membership in the MAP RG is open to all interested parties.
> Meetings --------
> The MAP RG will meet one to three times per year, as deemed
> necessary by the chairs and according to demand. At least one MAP
> RG meeting will be co-located with an IETF meeting per year. Given
> the MAP RG's charter to bridge the gap between Internet standards
> and measurement communities, the MAP RG may also meet colocated
> with relevant academic conferences or network operator forums, as
> appopriate.
> Meetings are by default open with open attendance and published
> proceedings, with remote participation and recording as provided by
> the meeting venue, according to the IRTF's IPR policy. This is
> always the case with at least one MAP RG meeting co-located with an
> IETF meeting noted above. However, as deemed necessary, the chairs
> may hold virtual or physical meetings with restricted attendance to
> discuss observations which cannot be shared openly, provided that
> some outcome of such a meeting may be openly shared with the
> community.
> Chairs ------
> Mirja Kühlewind <<>> Dave Plonka
> <<>>
> Many thanks,
> Brian
> _______________________________________________ hops mailing list
Version: GnuPG v2.0.22 (MingW32)


hops mailing list<>

hops mailing list<>

"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

Tel:    +34 913 129 041
Mobile: +34 682 051 091


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição