Re: New Version Notification for draft-li-6man-hbh-fwd-hdr-00.txt

Toerless Eckert <tte@cs.fau.de> Thu, 09 July 2020 10:32 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16E2C3A0823 for <ipv6@ietfa.amsl.com>; Thu, 9 Jul 2020 03:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.87
X-Spam-Level:
X-Spam-Status: No, score=-0.87 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no 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 hQ5SYSMnJ-ua for <ipv6@ietfa.amsl.com>; Thu, 9 Jul 2020 03:32:01 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC7B33A0820 for <6man@ietf.org>; Thu, 9 Jul 2020 03:32:01 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 7EC5B548045; Thu, 9 Jul 2020 12:31:56 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 78453440043; Thu, 9 Jul 2020 12:31:56 +0200 (CEST)
Date: Thu, 09 Jul 2020 12:31:56 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "otroan@employees.org" <otroan@employees.org>, "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Subject: Re: New Version Notification for draft-li-6man-hbh-fwd-hdr-00.txt
Message-ID: <20200709103156.GC42197@faui48f.informatik.uni-erlangen.de>
References: <4278D47A901B3041A737953BAA078ADE191360C2@DGGEML532-MBX.china.huawei.com> <643ED8C1-2A41-481A-8376-F2E31965DE89@employees.org> <4278D47A901B3041A737953BAA078ADE19139976@DGGEML532-MBX.china.huawei.com> <1AEC48EE-218D-47FC-9ACA-7EC663680F3B@employees.org> <4278D47A901B3041A737953BAA078ADE1913E679@DGGEML532-MBX.china.huawei.com> <3dae60f1-8f42-0cfd-dbd4-ed962adf0c16@gmail.com> <20200709050646.GO13952@faui48f.informatik.uni-erlangen.de> <4278D47A901B3041A737953BAA078ADE1913FBD3@DGGEML532-MBX.china.huawei.com> <20200709093928.GB42197@faui48f.informatik.uni-erlangen.de> <4278D47A901B3041A737953BAA078ADE1913FCE8@DGGEML532-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4278D47A901B3041A737953BAA078ADE1913FCE8@DGGEML532-MBX.china.huawei.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0ngGheZENc6-US5EJLK1oImfsoA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jul 2020 10:32:04 -0000

On Thu, Jul 09, 2020 at 10:06:35AM +0000, Pengshuping (Peng Shuping) wrote:
> We only used "forwarding plane" not "data plane" in this draft. In the context of this draft, from the perspective of the separation of the control plane and forwarding plane of a modern router, they could be taken as the same.

How about inband signaling such as

https://tools.ietf.org/internet-drafts/draft-martinsen-mmusic-malice-00.txt
https://tools.ietf.org/html/draft-han-tsvwg-ip-transport-qos-03

Older experiments would punt to CPU, newer PoC would process this in the FPE ASIC.

Is this control plane if its punted and forwarding plane if its run in the FPE ?
Do you think there should be a distinction between data plane and forwarding plane 
in terminology ?

I don't think we have an agreed upon definition of what forwarding plane means.
Most likely it has been used as a stand-in for data plane, but that typically
comes from times when there was no signalling processed by FPE.

To me, forwarding plane is anything running in an FPE. 

Just saying.

Cheers
    Toerless

> > > Best regards,
> > > Shuping
> > >
> > >
> > > Cheers
> > >     Toerless
> > >
> > > >
> > > > Quickstart is an Experimental RFC from 13 years ago. The RFC
> > unfortunately doesn't appear to state the time limit for the experiment or
> > how we would evaluate the experiment, but it does say:
> > > >
> > > > "As a result of these concerns,
> > > > and as a result of the difficulties and seeming absence of
> > > > motivation for routers, such as core routers to deploy Quick-Start,
> > > > Quick-Start is being proposed as a mechanism that could be of use in
> > > > controlled environments, and not as a mechanism that would be
> > > > intended or appropriate for ubiquitous deployment in the global
> > Internet."
> > > >
> > > > So to honest I don't think that Quickstart matters at all.
> > > >
> > > > Looking at the list of "Forwarding Plane" options, I see that it includes
> > the RPL option. RFC6553 says:
> > > >
> > > > "The RPL Option provides a mechanism to include routing information
> > > > with each datagram that a router forwards.  When receiving datagrams
> > > > that include routing information, RPL routers process the routing
> > > > information to help maintain the routing topology."
> > > >
> > > > I can't see how that is an action in the forwarding plane; it seems to
> > describe a control plane action since it is updating the topology maps.
> > > >
> > > > On balance it seems to me that almost any conceivable HbH option,
> > which by definition is intended for consumption by routers, is a control plane
> > action, i.e. it distracts the router from its elementary job of looking for the
> > longest match for the destination address in its forwarding table.
> > > >
> > > > (The Jumbo payload option is not really an exception to this, since
> > > > as well as doing the longest match, the router must check that the
> > > > outbound link supports the required MTU. Anyway, since the packet
> > > > size by definition exceeds 65,575 bytes, nobody will really care
> > > > about some overhead. Also, like most of the defined HbH options,
> > > > it's a limited-domain option.)
> > > >
> > > > Regards
> > > >     Brian
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --------------------------------------------------------------------
> > > > IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> > > > Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > > --------------------------------------------------------------------
> > >
> > > --
> > > ---
> > > tte@cs.fau.de
> > 
> > --
> > ---
> > tte@cs.fau.de

-- 
---
tte@cs.fau.de