Re: [Detnet] 1st stage of WG adoption poll: draft-dt-detnet-dp-sol

Norman Finn <norman.finn@mail01.huawei.com> Thu, 20 July 2017 12:52 UTC

Return-Path: <norman.finn@mail01.huawei.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 D2AB1131C1E for <detnet@ietfa.amsl.com>; Thu, 20 Jul 2017 05:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ZuBx6IUPK-7e for <detnet@ietfa.amsl.com>; Thu, 20 Jul 2017 05:52:49 -0700 (PDT)
Received: from dfwrg11-dlp.huawei.com (dfwrg11-dlp.huawei.com [206.16.17.15]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1FE11315FF for <detnet@ietf.org>; Thu, 20 Jul 2017 05:52:49 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfwpml701-chm.exmail.huawei.com) ([172.18.9.243]) by dfwrg11-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAW38148; Thu, 20 Jul 2017 07:52:48 -0500 (CDT)
Received: from DFWPML702-CHM.exmail.huawei.com ([169.254.5.95]) by dfwpml701-chm.exmail.huawei.com ([169.254.4.135]) with mapi id 14.03.0301.000; Thu, 20 Jul 2017 05:52:47 -0700
From: Norman Finn <norman.finn@mail01.huawei.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: [Detnet] 1st stage of WG adoption poll: draft-dt-detnet-dp-sol
Thread-Index: AQHTAUCooHqKUeAzAECiBU4gyJjrgaJdD9eAgAAByoD//5IVjYAABfig
Date: Thu, 20 Jul 2017 12:52:47 +0000
Message-ID: <3DF0466E9510274382F5B74499ACD6F8CAE00C@dfwpml702-chm.exmail.huawei.com>
References: <be3ed0c9-ff8d-5108-bb00-5b79c089b0d3@labn.net> <de9a4e34-31bb-fa90-d51e-6c57eb610763@pi.nu>, <c4c41bea-cf22-0384-ec0c-34b108b06be8@gmail.com>, <3DF0466E9510274382F5B74499ACD6F8CADFF1@dfwpml702-chm.exmail.huawei.com>
In-Reply-To: <3DF0466E9510274382F5B74499ACD6F8CADFF1@dfwpml702-chm.exmail.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.18.4.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/yM2GkTEwcSRFIwIEQsttfL-x80c>
Subject: Re: [Detnet] 1st stage of WG adoption poll: draft-dt-detnet-dp-sol
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: Thu, 20 Jul 2017 12:52:52 -0000

Something I missed, and don't want to give the wrong impression.  Standard 1+1 approaches may be appropriate for some of the use cases that *are* in our use cases document, as well as those that are not included.  I'm sure that there are applications that need bounded latency, but do not have a requirement never to lose 2 packets in a row.  But, I don't think that we are throwing any tools out of the toolbox.  We are adding some (packet replication and elimination) that are very much required by applications in which we have interest.

-- Norm
________________________________________
From: Norman Finn
Sent: Thursday, July 20, 2017 5:33 AM
To: Stewart Bryant; detnet@ietf.org
Subject: RE: [Detnet] 1st stage of WG adoption poll: draft-dt-detnet-dp-sol

Stewart,

Detnet in no way removes the standard 1+1 approaches from the repertoire of features available to use cases not encompassed by the currently-adopted use cases draft.  However, a number of our use cases place a limit on the number of consecutive packets lost that the standard 1+1 approach cannot meet.  That's why we are exploring techniques that are both more capable and more difficult to implement.  I'm happy to hear about a new use case (network slicing), but that does not invalidate the requirements that we have already addressed successfully.  The same arguments apply to other irrelevant solutions such as congestion notification.

Certainly, if you posit a different set of use cases with different requirements, you'll get a different answer.  That is not helpful.  Please read the use cases and architecture documents to better understand what is driving the other current drafts.  You might look at the problems statement, also.  I apologize for letting it lapse.

-- Norm
________________________________________
From: detnet [detnet-bounces@ietf.org] on behalf of Stewart Bryant [stewart.bryant@gmail.com]
Sent: Thursday, July 20, 2017 4:57 AM
To: detnet@ietf.org
Subject: Re: [Detnet] 1st stage of WG adoption poll: draft-dt-detnet-dp-sol

I will do a detailed review a bit later, but I think we need to mark the
IPv6 encapsulation as undecided, and I think that we need to have a
serious discussion in the WG about the proposal to perform an
intermediate triage of duplicate packets. Doing the triage at S-PEs adds
a lot of complexity and posiibly a lot of silicon expense whereas a
simpler approach that would be to do standard 1+1 or even 1+n and
de-duplicate at the edge of the network. So I think we need to donsider
that as undecided at this stage.

I am not sure what the scaling constraints that are proposed are, but
S-PE can have huge numbers of PWs flowing through them.

- Stewart



On 20/07/2017 12:51, Loa Andersson wrote:
> Lou,
>
> One thing I feel that we need to do is to look at how GACh works with
> replication and elimination.
>
> The document does not specify OAM functions, but I think that the data
> channels for OAM should be within scope of the document.
>
> /Loa
>
> On 2017-07-20 12:00, Lou Berger wrote:
>> All,
>>
>> In this morning sessions we discussed a two stage adoption call for the
>> proposed data plane solution:
>>
>> - in the first stage we collect issues with the -01 individual draft
>> that WG members would like to see addressed as part of the normal WG
>> processing of the document.  These issues will then be captured in -02
>> rev of the individual draft.
>>
>> - The second stage will be the normal WG adoption process
>>
>> This message initiates the first stage of adoption.  In this stage we'd
>> like to collect technical issues to be captured in the -01 draft.
>> Specifically, if you have an issue with the draft please:
>>
>> (a) if an issue with a particular section or sections, please identify
>> the section(s) and summarize the issue to be captured in the -02 rev of
>> the draft (your text may be copied verbatim or
>> paraphrased/summarized), or
>>
>> (b) if not section specific, identify the general issue you'd like to
>> see captured in an "open issues" section.  Again, your text may be
>> copied verbatim, paraphrased or summarized.
>>
>> Please send comments in the next 3 weeks, no later than Thursday,
>> August 10.
>>
>> Thank you,
>>
>> Pat and Lou
>>
>> _______________________________________________
>> detnet mailing list
>> detnet@ietf.org
>> https://www.ietf.org/mailman/listinfo/detnet
>>
>

_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet