Re: [Paw] Proposed update to DetNet OAM requirements

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Mon, 12 November 2018 03:59 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: paw@ietfa.amsl.com
Delivered-To: paw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B54331276D0; Sun, 11 Nov 2018 19:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.969
X-Spam-Level:
X-Spam-Status: No, score=-14.969 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Xh45BXn9YrA0; Sun, 11 Nov 2018 19:59:50 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7322E12007C; Sun, 11 Nov 2018 19:59:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11378; q=dns/txt; s=iport; t=1541995190; x=1543204790; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5UNFPctL7y5zQdgmw5LWyTCSqOV0OVNN1pQs0mkEAXk=; b=mZnz66oLMqD2vEezvJTDCKUVecIRR9ETaMJvdLFQ4+bAU7ny3pTI5U3w mkVHfFlUmaBKQJ++isUB7a2mnQnpoHmBXP7nckbjiZ33wd7Q0u+ZqwucQ /vXAS95QHuPUI3KcxZaieaR3MiQgRV1/V4ozgjUokfharQJTpxoCVedkg 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAAAY+uhb/4kNJK1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDXZmgQInCoNuiBiLeIINiQeIWoVUFIFmCwEBJYRHAheDDSI0DQ0BAwEBAgEBAm0cDIU6AQEBBCMKQwkQAgEIEQQBASsCAgIfER0IAgQOBQgTgweBHUwDFQ+pBIEvhD9AgnANghQFjAAXgUA/gRABgmQuglZFAQECAQGBJV6CXoJXAo5skDUuCQKGdIMngVeBfoMjIIFYhQKKFolag0yBBYkmAhEUgSYdOIFVcBWDJ4schT5BMYx5gR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,493,1534809600"; d="scan'208,217";a="476936644"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2018 03:59:49 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id wAC3xnsg009741 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 12 Nov 2018 03:59:49 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 11 Nov 2018 21:59:48 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Sun, 11 Nov 2018 21:59:48 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: DetNet WG <detnet@ietf.org>
CC: Greg Mirsky <gregimirsky@gmail.com>, "paw@ietf.org" <paw@ietf.org>
Thread-Topic: Proposed update to DetNet OAM requirements
Thread-Index: AQHUejQHEGA7h8YroE63RwHO34D+JqVLgTqQ
Date: Mon, 12 Nov 2018 03:59:37 +0000
Deferred-Delivery: Mon, 12 Nov 2018 03:59:16 +0000
Message-ID: <1930081536f248669cbb901ed4560d56@XCH-RCD-001.cisco.com>
References: <CA+RyBmXKFy78EDitTN1C5wKnUyd4uwjNYW7GEN=jwgaJYysHkg@mail.gmail.com>
In-Reply-To: <CA+RyBmXKFy78EDitTN1C5wKnUyd4uwjNYW7GEN=jwgaJYysHkg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.75.233.148]
Content-Type: multipart/alternative; boundary="_000_1930081536f248669cbb901ed4560d56XCHRCD001ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/paw/3TYaQzSxBJEaWC9CoKywMf0R37M>
Subject: Re: [Paw] Proposed update to DetNet OAM requirements
X-BeenThere: paw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: predictable and available wireless <paw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/paw>, <mailto:paw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/paw/>
List-Post: <mailto:paw@ietf.org>
List-Help: <mailto:paw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/paw>, <mailto:paw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Nov 2018 03:59:53 -0000

Many thanks Greg:

The main change that I suggested was to consider OAM for the detnet service layer as well as the detnet transport layer. I do not have a solution in mind that can do that for the IP dataplane without instrumenting the packets.
I worked on that topic in the context of wireless, which is extreme in that there is a lot of PREOF going on in order to provide spatial diversity in compensation to the lossiness of the medium.
It is also often constrained so we had to come up with a very concise way to observing the service layer operation.
Finally the radio medium is constrained energy-wise so we wanted to be able to control dynamically the amount of PREOF being used based on its usefulness, and favor the segments that provide the best service at any point of time. Sine this is highly variable, we needed a way to provide a control loop between the OAM observation and the Segment routing signaling.
We found that BIER-TE was an excellent tool for all the above and produced https://datatracker.ietf.org/doc/html/draft-thubert-bier-replication-elimination which was discussed at BIER for a while.
Once BIER agrees that the technology is sound, I think we need to bring it back to where it belongs, ideally DetNet, but if it is too specific for DetNet, then Paw.

Please go through  the draft and let us know;

Pascal

From: Greg Mirsky <gregimirsky@gmail.com>
Sent: lundi 12 novembre 2018 10:01
To: DetNet WG <detnet@ietf.org>; Pascal Thubert (pthubert) <pthubert@cisco.com>
Subject: Proposed update to DetNet OAM requirements

Dear All,
we've worked with Pascal off-line to address his comments at the meeting. Attached please find the diff to the working version and its copy. Much appreciate your comments, questions, and suggestions.

Regards,
Greg