Do we really need to add state into each packet ...

Robert Raszuk <robert@raszuk.net> Wed, 13 May 2020 19:37 UTC

Return-Path: <robert@raszuk.net>
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 89C653A0888 for <ipv6@ietfa.amsl.com>; Wed, 13 May 2020 12:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 PlgAbu5ruks4 for <ipv6@ietfa.amsl.com>; Wed, 13 May 2020 12:37:05 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0EA23A0887 for <6man@ietf.org>; Wed, 13 May 2020 12:37:04 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id w2so370916edx.4 for <6man@ietf.org>; Wed, 13 May 2020 12:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:from:date:message-id:subject:to; bh=5Eon1nFGBLJTdNDr4A7Hw9KeDva2pKMJKuY01Ts2ydk=; b=dAZt2R5IaiG+ulzFFU4pl2HPulLhnNlCui3vgr8DT7j7MyfCDDZPQtOPIbM0wd9HgA +2urIvXuu1L1AKmIsoNm9vdEVpR8Hk88hWyYg+rx9vRFT1WB8HIZssnA2hSiM7/6Nz38 SHArcANGJm1WOk8n0iOih13lxLzkVsCJ4rf8C4faagdw3tb/JiWBWN7U8cUme8GKRFBT wIK0X2siQaHxNThCq6FG6p07LVIg+Si2S13jqIvnz52bb8AZXnzYl6KYezFXeP8pzGJM xCM+rXDDMPs0/hrT02QICAxC457wZKe0Tj1Q0qlx4zliiunFFziHYMRB9DsZhsLltcLA qwiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=5Eon1nFGBLJTdNDr4A7Hw9KeDva2pKMJKuY01Ts2ydk=; b=I4ZnyF6ET1n+FPvmIueh+fg4HJbaIzJiwAnIduEsH6MrRoBLhtpHCzqlbN7uKhzTsS uIoOR4FSZpRVXtUHEG5zGooDq8v5L6qXUjmK7Gq6xlKYg+usLtqRgga25Em3OMmcpCMV Sz2TQT+z9TAewZf2knBdolBPeKBRbFPwJKW9C09awr8D8pJAft+nhKJBORVo4QFIlSDc zX6+WbgpDAwTHiLNuct5EeMhtuDwA+CXLT+6IVRohPxJq/gXeHV86Yig+YhYv907DN0Y bmtIvml08SvizkPMKWQtjCumo9R4Iq5HnFwHUrV6h9nqYlM74qlQBo1hmuo7TfK03Qt2 lB1w==
X-Gm-Message-State: AOAM531dw09aICv+fziiG1Fdo3cYVeQKePPu7nC3Ho9Y9CVzyuW+nXaQ vChym8sJcG4o41mfs5xX3fJMLxwuZrcorFINQ+DXwgkbZfs=
X-Google-Smtp-Source: ABdhPJyr1V9VkQqbmK0FFjnhPxUaMlE5c2vMDYrFIB26BGe6Z8z3za5B86qo80fr8DCtrXknji+TUeWkjiDhgPa0Jik=
X-Received: by 2002:a50:e711:: with SMTP id a17mr1118186edn.369.1589398623073; Wed, 13 May 2020 12:37:03 -0700 (PDT)
MIME-Version: 1.0
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 13 May 2020 21:36:54 +0200
Message-ID: <CAOj+MME4QkcWBXdN4MieFbFi0Fip+pNFdrbk5k7MDVJ9jt2RWA@mail.gmail.com>
Subject: Do we really need to add state into each packet ...
To: 6man <6man@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000055f26b05a58cb452"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zmI6SA2GfHc_gt54xhVevOJvWsQ>
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: Wed, 13 May 2020 19:37:07 -0000

Dear 6man WG,

In the light of the discussion on effectively steering packets via non
routing computed paths there seems to be some sort of the umbrella
assumption that we must add that information into each packet.

For example in CRH proposal we read:

   The CRH allows IPv6 source nodes to specify the path that a packet
   takes to its destination.

So let's me just bring up a reference to the document I wrote last year which
illustrates that without putting any extra extension headers into each packet
it can be easily steered within a controlled domain.

It also does not need to define any new data plane extensions and for control
plane it can use controller driven or existing protocol extensions
(BGP) to distribute
local mapping information.

Note also that those mappings are not per flow but large aggregated mappings.

If folks are analyzing should we adopt CRH as "IPv6 friendly" I would say that
nothing is more friendly then absolutely no change to the data plane.

Ref:

https://tools.ietf.org/html/draft-raszuk-teas-ip-te-np-00
Thx a lot,

Robert.