Re: [Ioam] [EXT] Updated IOAM Proposed Charter

David Mozes <davidm@mellanox.com> Tue, 14 February 2017 14:51 UTC

Return-Path: <davidm@mellanox.com>
X-Original-To: ioam@ietfa.amsl.com
Delivered-To: ioam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26CC127601 for <ioam@ietfa.amsl.com>; Tue, 14 Feb 2017 06:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mellanox.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 uTdWBoQqwYma for <ioam@ietfa.amsl.com>; Tue, 14 Feb 2017 06:51:31 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40056.outbound.protection.outlook.com [40.107.4.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A3D129630 for <ioam@ietf.org>; Tue, 14 Feb 2017 06:51:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YcqunQCUGXfp/qlsvRNCLuurpg5vSFoDG/liVZ6rg9c=; b=rSAfNSY0H34Q96OXaTfW64tHOM3kuQ6LbeKyLI5ENboreVgSABXAm7wQwvUrFqsNq//8W+lnKC7Xj6CmYbTpa8Fgb14jKaslZ2bwUN2FK5TitJtgv852c6wccUHVLl7yndXGp6W089uozAFNhy5yUdmP2QGR4vcZPxjSOy8v2Fw=
Received: from HE1PR0501MB2138.eurprd05.prod.outlook.com (10.167.246.22) by HE1PR0501MB2138.eurprd05.prod.outlook.com (10.167.246.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Tue, 14 Feb 2017 14:51:25 +0000
Received: from HE1PR0501MB2138.eurprd05.prod.outlook.com ([10.167.246.22]) by HE1PR0501MB2138.eurprd05.prod.outlook.com ([10.167.246.22]) with mapi id 15.01.0888.026; Tue, 14 Feb 2017 14:51:25 +0000
From: David Mozes <davidm@mellanox.com>
To: Tal Mizrahi <talmi@marvell.com>, "ioam@ietf.org" <ioam@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Alvaro Retana (aretana) (aretana@cisco.com)" <aretana@cisco.com>
Thread-Topic: [Ioam] [EXT] Updated IOAM Proposed Charter
Thread-Index: AQHShs5b/4J0NVjQGU6SKcz6f41y66FoleSQ
Date: Tue, 14 Feb 2017 14:51:25 +0000
Message-ID: <HE1PR0501MB2138D2CF0A5F30187F5B28F2B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
References: <adeb1814acd74ebaafe10d4a5086ba0f@IL-EXCH01.marvell.com> <dfc15b6a84a743d997595e040547346f@IL-EXCH01.marvell.com>
In-Reply-To: <dfc15b6a84a743d997595e040547346f@IL-EXCH01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=davidm@mellanox.com;
x-originating-ip: [193.47.165.251]
x-ms-office365-filtering-correlation-id: f8f06b12-9975-4823-90c7-08d454e8f366
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:HE1PR0501MB2138;
x-microsoft-exchange-diagnostics: 1; HE1PR0501MB2138; 7:/o3c6c1c2t9NY/OP+lT2/HZZ3ihVnKM0n56/n3wbw4OWe2JP9He7RX8V/RRGFLmCJDlwQPXM/QKhYQliDPr53UwZQ04GN+769Afz9vhWzZkPn9YNZgRerKMiNFAPCH04aqRv0visTcliZJsIP7r1oUtCN4PMnVulLW6CIUM4I1Pqu1IDWwaKnG7EiILP1CkSSCBb4Di33vODZohgY0GyEPqmBYlmmvqnnUj/qFdA2EjCuiZNELC3iQvbGhDwdOe7xnFiZ9Ivt40MZGvKCWexZ29v0rPnsuOEFv+GwUiDJ7kdgNsN3BDs/HIbN4CffgMYTHuOqEnb5rjVYWP0N+GeglPCbffjY3RnLjCM0Bpc0tSBd1QlefkCRGkcSAy0AixAXjKECu/KXNTZqbMM94/Xtv77p3RGGhw5ZaW/BPBY2wVFd1/Pu6thxg94jkPAYde4/k6oTAr2bt5KvBO7O5HEaTrDAFW9RWy3gxyaIsbg4i8aBcPdSAkA0DQpa/7SNAXiHQeBdrNm4AseGjne1T+JUg==
x-microsoft-antispam-prvs: <HE1PR0501MB2138DF72A9AB542FDA6A4B63B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(32856632585715)(120809045254105)(192374486261705)(100405760836317)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123558025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:HE1PR0501MB2138; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0501MB2138;
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39410400002)(39840400002)(39860400002)(39450400003)(39850400002)(377454003)(199003)(189002)(3660700001)(7696004)(8676002)(6506006)(54356999)(189998001)(101416001)(53936002)(68736007)(3280700002)(105586002)(81156014)(74316002)(76176999)(2420400007)(7736002)(5660300001)(81166006)(97736004)(54896002)(77096006)(25786008)(561944003)(9686003)(33656002)(8936002)(15650500001)(6436002)(606005)(50986999)(86362001)(7110500001)(102836003)(2900100001)(106356001)(99286003)(6306002)(2950100002)(92566002)(2501003)(10710500007)(2906002)(236005)(790700001)(122556002)(66066001)(3846002)(38730400002)(55016002)(229853002)(19609705001)(7906003)(106116001)(6246003)(6116002)(81003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0501MB2138; H:HE1PR0501MB2138.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0501MB2138D2CF0A5F30187F5B28F2B6580HE1PR0501MB2138_"
MIME-Version: 1.0
X-OriginatorOrg: Mellanox.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2017 14:51:25.7251 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2138
Archived-At: <https://mailarchive.ietf.org/arch/msg/ioam/I-ckC9IbA-hQyidkTpg7Rieur8g>
Subject: Re: [Ioam] [EXT] Updated IOAM Proposed Charter
X-BeenThere: ioam@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion on In-Situ OAM <ioam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ioam>, <mailto:ioam-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ioam/>
List-Post: <mailto:ioam@ietf.org>
List-Help: <mailto:ioam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ioam>, <mailto:ioam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 14:51:33 -0000

Nvo3 ?

From: Ioam [mailto:ioam-bounces@ietf.org] On Behalf Of Tal Mizrahi
Sent: Tuesday, February 14, 2017 4:26 PM
To: Tal Mizrahi <talmi@marvell.com>; ioam@ietf.org; Stephen Farrell <stephen.farrell@cs.tcd.ie>; Alvaro Retana (aretana) (aretana@cisco.com) <aretana@cisco.com>
Subject: Re: [Ioam] [EXT] Updated IOAM Proposed Charter

Hi,

Another issue that was raised by Stephen:

>1) I'm sure there are good things one can do with such marking, but it is very

>unclear to me how this proposal doesn't also fall afoul of all the privacy

>downsides of the SPUD/PLUS proposal. My understanding of those privacy

>downsides was that any generic/extensible marking scheme (whether of packets

>or transport connections/flows) could easily be abused in many privacy

>unfriendly ways. Note that I'm not claiming there is IETF consensus on that but I

>do claim it was a significant issue for SPUD/PLUS and would like to know why

>(and hope) it is not an issue here. Can someone help me understand what's

>different here so we avoid that same kind of mega-debate?


To address this in the charter, I propose to add the following text to the list of items the WG will work on:

* Security aspects of in-situ OAM, including the potential vulnerabilities of integrating hop-by-hop information to en-route traffic, and measures that should be taken to mitigate them.


Again, comments will be welcome.

Cheers,
Tal.


From: Ioam [mailto:ioam-bounces@ietf.org] On Behalf Of Tal Mizrahi
Sent: Monday, February 13, 2017 4:48 PM
To: ioam@ietf.org<mailto:ioam@ietf.org>
Subject: [EXT] [Ioam] Updated IOAM Proposed Charter

External Email
________________________________
Hi,

The charter draft has been updated based on the comments received on the last few days:
https://datatracker.ietf.org/doc/charter-ietf-ioam/

The main changes compared to the previous draft:

-          A few terminology and phrasing changes based on comments received on the list.

-          New text regarding the encapsulations that the working group will initially focus on.

-          Updated the text about consultation with other working groups.

-          New text about cooperation with other standard bodies.

Comments will be welcome.

Thanks,
Tal.