[Detnet] 答复: IP dataplane

"Yangfan(Fan,IP Standards)" <shirley.yangfan@huawei.com> Thu, 11 November 2021 19:11 UTC

Return-Path: <shirley.yangfan@huawei.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 786133A09D8 for <detnet@ietfa.amsl.com>; Thu, 11 Nov 2021 11:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iZVubj7h5LSb for <detnet@ietfa.amsl.com>; Thu, 11 Nov 2021 11:11:47 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 800003A0B19 for <detnet@ietf.org>; Thu, 11 Nov 2021 11:11:47 -0800 (PST)
Received: from fraeml701-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Hqrt01z3zz67Prk; Fri, 12 Nov 2021 03:11:20 +0800 (CST)
Received: from kwepeml500004.china.huawei.com ( by fraeml701-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.15; Thu, 11 Nov 2021 20:11:43 +0100
Received: from kwepeml500003.china.huawei.com ( by kwepeml500004.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Fri, 12 Nov 2021 03:11:41 +0800
Received: from kwepeml500003.china.huawei.com ([]) by kwepeml500003.china.huawei.com ([]) with mapi id 15.01.2308.015; Fri, 12 Nov 2021 03:11:41 +0800
From: "Yangfan(Fan,IP Standards)" <shirley.yangfan@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>, "Pascal Thubert (pthubert)" <pthubert=40cisco.com@dmarc.ietf.org>
CC: "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: [Detnet] IP dataplane
Thread-Index: AdfWNZhj6v1SBWEpRuChk2dIwvk7Dv//1yeA//30NVA=
Date: Thu, 11 Nov 2021 19:11:41 +0000
Message-ID: <d85e3fc81e9c4914be38ece731e92c64@huawei.com>
References: <CO1PR11MB48810E7AEBE8B42968828A46D8939@CO1PR11MB4881.namprd11.prod.outlook.com> <YYwVH0WbKlLqm4GT@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <YYwVH0WbKlLqm4GT@faui48e.informatik.uni-erlangen.de>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/ydC3MmwTEMWoe1CncXP1LeO1vHU>
Subject: [Detnet] 答复: IP dataplane
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2021 19:11:53 -0000

Hi Pascal and Toerless,

I am fully concurred with your discussions. 
The reasons Pascal lists in previous emails elaborate why IP+UDP encapsulation is not feasible, especially from the hardware perspective. These are sound technical issues which every vendor would face. 
I would also agree the IP+UDP+MPLS DetNet header encapsulation is a workaround solution. If it is already implied in previous RFCs, I question the necessity of producing the separate RFC if so.
Regarding the IPv6 extension header discussions in v6ops/6man, DetNet should catch up and take the advantages of new mechanisms. As the hardware evolves, DetNet shouldn’t be achieved only based on the legacy techniques. Take d-ACH format for OAM as an example, DetNet OAM extension is also keeping aligned with PALS discussion. 

draft-pthubert-detnet-ipv6-hbh-06 introduces a generic and flexible format to solve multiple DetNet problems, e.g. PREOF, OAM, and DN flow identification on forwarding layer etc. It can be richly extended because of the characteristics of IPv6 extensions headers, which is greatly interested by many companies right now. If the adoption call is going to poll to draft-varga-detnet-ip-preof, it is also reasonable to adopt draft-pthubert-detnet-ipv6-hbh, as they represent different underlying encapsulations to support IP PREOF function. 

Best regards,

发件人: detnet [mailto:detnet-bounces@ietf.org] 代表 Toerless Eckert
发送时间: 2021年11月11日 2:53
收件人: Pascal Thubert (pthubert) <pthubert=40cisco.com@dmarc.ietf.org>
抄送: detnet@ietf.org
主题: Re: [Detnet] IP dataplane

Hi Pascal

Thanks for the email, it touches on a lot of good points. Let me give some opinions from my side

a) I too would like to see that we do get all of the detnet services for a pure
   IP data plane, and not only some short-term IP over MPLS workarounds.

b) I have no strong opinions yet what this means for the document in question.
   Maybe it would suffice to more clearly describe the scope of any current
   "workaround" or "incomplete" IP dataplane documents as such - to make readers
   understand that these solutions may not be good for best-long-term deployments.
   Just an idea.

c) As i said in my slot today, it would help to have more audio discussion time.
   Hopefully we can start such "design-team" meetings..

d) I have not really considered the 'E'limination or othre DetNet service layer
   functions since our old BIER-TE extension work. I think it would be great
   to have some writeup of reference example use cases where this is done, so that
   one had a more concrete reference when designing an appropriate solution.

e) Right now i am roughly thinking that for bounded latency we would want a 
   Hop-By-Hop header with sequence number and appropriate bounded latency paramer(s).
   If we had such a header, we could perform elimination of course also from
   fields in the packet header and not need to rewrite IP header addresses along
   the path. Lets see what fridays 6man meetin brings up avbout the future of HBH.

f) Aggregation/disaggregation is i think a problem we can punt up from IP layer
   to overall DetNet layer. Aka: We have no architectural design or solution of
   this for MPLS AFAIK. But we would need reference scenarios to work against them.


On Wed, Nov 10, 2021 at 01:48:29PM +0000, Pascal Thubert (pthubert) wrote:
> Thanks to both Lou and David for rewording very correctly what I was trying to say at the meeting today.
> Effectively, the question is whether we need for a pure IP dataplane that can carry the DetNet information for Forwarding and Service sublayer.
> Arguments on the table:
> - Not all DetNet environments employ MPLS and pseudowires as a basic tool. Forcing such concepts beyond their domain may hinder adoption in pure IP (IT) and industrial (OT) spaces. A native IP solution is desirable. Note that IPv4 can be encapsulated in IPv6 so arguably we can live with IPv6 signaling.
> - Hardware operation (common ASICs) need the information very early in the packet. Digging after UDP may not be feasible in all cases. The DetNet information cannot be missed and should be very early after the IP header (before UDP if present).
> - An IP solution is bound to other rules than MPLS, e.g., use of EH and encapsulation vs. stack of label. The properties of the solution might be different and IP may possibly express richer semantics. But as of now, the IP data plane is more limited than the MPLS one.  
> - There's a need with IPv6 to encapsulate when playing with merging, re-sourcing (for duplication and network coding), altering the destination (to an intermediate elimination node) or changing packet header information (e.g., sequencing); such encapsulation will hinder with the visibility of deep information (UDP and application data), which cannot be used for DetNet processing
> - the elimination or decapsulation node may not be the destination, but it still needs to understand the DetNet signaling; the DetNet signaling should be 100% L3, fully independent of L4 and above, and should not imply that the transport is USP.
> - the 5-6 tuple points on upper layer information for a flow. DetNet may aggregate flows (several times leading to multiple reencapsulations) disaggregate flows (decapsulations and separation) and OAM packets. We want the information that signals the dataplane processing independent of which application flow / already merged and encasulated application flows / and or OAM is transported.
> - it would make sense to build a solution that integrates well with IPv6 state of the art, especially SRv6, and very possibly HbH which is getting traction, see the discussion at 6MAN / v6ops on Friday.
> Bottom line: I disagree with adopting a document that would seem to indicate that we're done with IP. On the contrary I believer that there's a rich ground that we need to plow to deliver the best for IP networks.
> What do others think?
> Keep safe,
> Pascal Thubert
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet


detnet mailing list