Re: [tsvwg] draft-ietf-udp-options issues from IETF 104

Derek Fawcus <dfawcus+lists-tsvwg@employees.org> Sat, 13 July 2019 18:25 UTC

Return-Path: <dfawcus@employees.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5FF120165 for <tsvwg@ietfa.amsl.com>; Sat, 13 Jul 2019 11:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.274
X-Spam-Level: *
X-Spam-Status: No, score=1.274 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=1.274, SPF_HELO_NONE=0.001, SPF_PASS=-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 YxKr4LmaZUtb for <tsvwg@ietfa.amsl.com>; Sat, 13 Jul 2019 11:25:55 -0700 (PDT)
Received: from clarinet.employees.org (unknown [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5932120157 for <tsvwg@ietf.org>; Sat, 13 Jul 2019 11:25:55 -0700 (PDT)
Received: by clarinet.employees.org (Postfix, from userid 1736) id AD8734E12350; Sat, 13 Jul 2019 18:25:54 +0000 (UTC)
Date: Sat, 13 Jul 2019 19:25:54 +0100
From: Derek Fawcus <dfawcus+lists-tsvwg@employees.org>
To: tsvwg@ietf.org
Message-ID: <20190713182554.GB39770@clarinet.employees.org>
References: <CAPDqMeq9GjEQKukH1pZOTdE50e_rc3U6gpdxT-5qrS5phD0RGw@mail.gmail.com> <646D45AD-D79B-4BD2-A084-7DA97CE2C415@strayalpha.com> <7EC37B50-45D5-4CF1-B113-205E55BF244E@strayalpha.com> <CALx6S34s7L7xo+26bt5Cdaqi4Es5Aci42GHk1WNKzugr5st-Gw@mail.gmail.com> <B525BF50-EFCC-44A5-A604-6CDDA914A1CB@strayalpha.com> <CAPDqMep3R6z9PRKkHyOvrh6sV9n5Sc0B++-zVz0FYJCwE6swrQ@mail.gmail.com> <E42A2AE2-F499-465E-BDE6-5EFC0AB20042@strayalpha.com> <CE03DB3D7B45C245BCA0D24327794936306138E9@MX307CL04.corp.emc.com> <CAPDqMeoyNb7vQTdqxLpZpnKb9S7QKeDJNLyQJBmq95yXhB+xfQ@mail.gmail.com> <7D365770-64FE-40BC-901D-B4D7DF6B484B@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7D365770-64FE-40BC-901D-B4D7DF6B484B@strayalpha.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/BtrY4G8g594MbkDTCX0OVIEZ4jU>
Subject: Re: [tsvwg] draft-ietf-udp-options issues from IETF 104
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jul 2019 18:25:57 -0000

On Thu, Jul 11, 2019 at 07:07:39PM -0700, Joe Touch wrote:
> 
> Not sure I follow here - so there are only a few variants that seem viable:
> 
> 1.- at the front of the surplus space
> 2.- at the front of the surplus space after alignment NOPs
> 3.- at the end of the surplus space
> 4.- at the end of the surplus space with alignment
> 
> AFAICT, there’s no real help in requiring OCS be aligned (it can be designed to tolerate any alignment), which means we don’t need #2 or #4.

Agree.  I see no need for alignment.

> So what’s preferable here? #1 or #3?

Not sure.

I'd be inclined to pick 1, but could be convinced that 3 is better.

If we're talking of h/w offload engines [*], I imagine that they could
handle 'write to 2 bytes before end of packet' more easily than
'write to start of surplus'.

DF

[*] How many do this with random logic?  My current impression is that
    most such devices are programmable cores, e.g. ARM or MIPS cores.