Re: Accurate ECN support in tcpdump/libpcap

[Francois via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Francois <devel.fx.lebail () orange fr>
>
> Date: Wed, 4 Mar 2026 10:46:52 +0100
>
> On 06/02/2026 17:40, Denis Ovsienko wrote:
>
> Hello,
>
> > [...]
> >
> > I considered a few other syntax
> > possibilities and found the most sense in joining the flag and its state
> > into a single string.  To that end, examples of the alternatives I have
> > considered are:
> >
> > * "not-fin" and "no-fin" (easy to confuse with "not fin"),
> > * "fin-0" (is 0 the bit value or the bit position?),
> > * "fin-unset" ("unset" is a verb, not a state, and could be confused
> >   with an assignment), and
>
> unset is also an adjective.
>
> > * "~fin" ("~" is not a valid bitwise unary operator in the current
> >   implementation, but it may be introduced later, also there is an
> >   ambiguity to whether besides FIN flag cleared it means all other
> >   flags set).
> >
> > After quite a few drafts the prototype eventually became this:
> >
> >        ip flag flagstate
> >               True if the packet is an  IPv4  packet  and  the  IPv4
> >               header  flag (MF or DF) is set (if flagstate is one of
> >               {mf-set, df-set}) or cleared (if flagstate is  one  of
> >               {mf-cleared,  df-cleared}). [...]
>
> I dont like very much -cleared.
> Why not
> fin-set/fin-unset
> fin-on/fin-off
> fin-yes/fin-no
> fin-y/fin-n
> ?
> The last three are shorter.
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers () lists tcpdump org
To unsubscribe send an email to tcpdump-workers-leave () lists tcpdump org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s