Re: [Detnet] WG Last Call: draft-ietf-detnet-problem-statement-03
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 16 May 2018 13:07 UTC
Return-Path: <pthubert@cisco.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562BD1242F5 for <detnet@ietfa.amsl.com>; Wed, 16 May 2018 06:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, 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 EPc3HtyT-D9v for <detnet@ietfa.amsl.com>; Wed, 16 May 2018 06:07:08 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 210DA1201F8 for <detnet@ietf.org>; Wed, 16 May 2018 06:07:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26896; q=dns/txt; s=iport; t=1526476027; x=1527685627; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=SLv/f/taZS5iNHRJLYr8sE1IiKJ7DVDrJLP86s2p+7s=; b=f9/C9MYxbW5DB2mNsWf30XKD4WaeN1XqbQ+u0/nhQjS17RHkj2wid4Wg D3AKHtzBLZR/cTkaGix/evDUqWOpzA5bV8YTau+W80ohh6DLW1RfJT8r5 b7/dvby8noGTf5JJ1R5eDJuv+bHX0sLxuUGSpMGFz4NjGURuW3RmkyV5S o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A1AgCSK/xa/40NJK1cGQEBAQEBAQEBAQEBAQcBAQEBAYJNdmF8KAqDapR5gXmBD5MygXgLhGwCGoMFITUXAQIBAQEBAQECbCiFKAEBAQQjCkMZAgEIEQQBASsCAgIwHQgCBAESCIMdgRtkqxCCHB+IKoIniCeBVD+BDgGDDIUZglqCVAKFP4tOhzQJAog6gmWDKoE/g2qHVpBHAhETAYEkAR4BNYFScBU7gkOCJRKOF2+OKYEYAQE
X-IronPort-AV: E=Sophos;i="5.49,390,1520899200"; d="scan'208,217";a="394269489"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2018 13:07:06 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w4GD76LJ013064 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 May 2018 13:07:07 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 16 May 2018 08:07:06 -0500
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.1320.000; Wed, 16 May 2018 08:07:06 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, János Farkas <janos.farkas@ericsson.com>, DetNet WG <detnet@ietf.org>
Thread-Topic: [Detnet] WG Last Call: draft-ietf-detnet-problem-statement-03
Thread-Index: AQHT4jMJ2dvniwrUQkGRFI6ttpMyXKQebU+AgBP08dA=
Date: Wed, 16 May 2018 13:06:58 +0000
Deferred-Delivery: Wed, 16 May 2018 13:06:53 +0000
Message-ID: <cce8a346541e41f393c00965ae4a0dc0@XCH-RCD-001.cisco.com>
References: <12d4d02b-d8da-81b5-c610-50facc798c26@ericsson.com> <034a09e4-03a1-679f-91d4-d5c549de3996@gmail.com>
In-Reply-To: <034a09e4-03a1-679f-91d4-d5c549de3996@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.228.216.12]
Content-Type: multipart/alternative; boundary="_000_cce8a346541e41f393c00965ae4a0dc0XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/tJIRl2k7iZyS_mkjdV8t0704rHQ>
Subject: Re: [Detnet] WG Last Call: draft-ietf-detnet-problem-statement-03
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2018 13:07:12 -0000
Thanks a bunch Stewart ; Please see below - by OK I mean undisputed agreement and changed made in the repo, to be published with the next version unless opposition shows up; From: detnet <detnet-bounces@ietf.org> On Behalf Of Stewart Bryant Sent: jeudi 3 mai 2018 16:57 To: János Farkas <janos.farkas@ericsson.com>; DetNet WG <detnet@ietf.org> Subject: Re: [Detnet] WG Last Call: draft-ietf-detnet-problem-statement-03 This is basically ready, but I think a few items need attention before this goes to the IESG: As a result of this work, it will be possible to establish a multi- hop path over the IP network, SB> I think that should be an IP or MPLS network [PT>] OK ============= The goals of Deterministic Networking are to enable the migration of applications that use special-purpose fieldbus technologies (HDMI, CANbus, ProfiBus, etc... even RS-232!) to packet technologies in general, and the Internet Protocol in particular, and to support both these new applications, and existing packet network applications, over the same physical network. SB> I think there should be some text here indicating that DN is SB> required to support these migrations when there are critical SB> timing and reliability issues. SB> SB> Where such issues are not critical, the Pseudowires or L2TP tunnels SB> will normally be adequate. Indeed they have proved adequate for TDM SB> and SDH emulation which are quite fickle services to emulate. [PT>] OK ============== * Need a packet loss ratio beyond the classical range for a particular medium, in the range of 10^-9 to 10^-12, or better, on Ethernet, and in the order of 10^-5 in Wireless Sensor Mesh Networks; SB> I am worried whether or not we are setting unreasonable expectations SB> here. How many packet copies do we think we need to send SB> to reduce the BER by 10? [PT>] I think these numbers are associated with the concept of PRE. If a typical Ethernet gives you 10-5 then PRI should reach 10-10 Arguably this considers only one fault at a time. =============== 4. Robust defenses against misbehaving hosts, routers, or bridges, SB> s/defenses/defences/ both in the data and control planes, with guarantees that a critical flow within its guaranteed resources cannot be affected by other flows whatever the pressures on the network; [PT>] UK vs. US. Which do we usually pick? ================= These limits may depend in the technology that is used to seu th epath up, whether it is centralized or distributed. SB> Hopefully no my fat fingers in my marked up copy, but it should be: SB> "set the path" [PT>] Yes, Kiran spotted it first ; ) ================= 3. The path is installed using RSVP-TE, associated with flow identification, per-hop behavior such as replication and elimination, blocked resources, and flow timing information. SB> This is too prescriptive on approach for a problem statement. SB> There might well be an approach that surfaces from the Segment Routing SB> or VPN+ work based on use of the IGP. [PT>] Yes, but at some point the resources along the path must be blocked. How is that done? What if the IGP selects a different path? I guess SR works as long as the SR is strict or the path between routers in the SR cannot change, and resources are aplenty. What about this: The path may be installed using a control protocol such as RSVP-TE, associated with flow identification, per-hop behavior such as Packet Replication and Elimination, blocked resources, and flow timing information. Alternatively, the routing and flow information may be placed in-band in the packet, e.g., using Segment Routing, in which case the packet is routed along a prescribed source route path following forwarding indications that are present in the packet. ================ Security must cover: SB> I think should be "Security must also cover". If not the dynamic SB> requirement which is unique to DN should be top of the list. o the protection of the signaling protocol SB> True, but isn't this currently out of scope (and not sure about the next point) [PT>] What about: The overall security of a deterministic system must cover: Thanks again Stewart! Pascal
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Pascal Thubert (pthubert)
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Stewart Bryant
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… János Farkas
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Stewart Bryant
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… János Farkas
- [Detnet] WG Last Call: draft-ietf-detnet-problem-… János Farkas
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Andrew G. Malis
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Kiran.Makhijani
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Stewart Bryant
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Kiran.Makhijani
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Pascal Thubert (pthubert)
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Pascal Thubert (pthubert)
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Pascal Thubert (pthubert)
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… Kiran.Makhijani
- Re: [Detnet] WG Last Call: draft-ietf-detnet-prob… János Farkas