The issue is that many existing routers will drop, or if you are very lucky
slow-path, and IP4 packets with options.
Yes, the specification allows such options. The IPv4 specs even allow adding
and removing such options.
However, because of issues like ECMP / LAG support, such options have been
Ole Troan [mailto:otr...@employees.org]
Sent: Friday, June 30, 2017 3:59 PM
To: Joel Halpern
Cc: Soheil Abbasloo ; Burt Silverman ;
vpp-dev
Subject: Re: [vpp-dev] IPv4 Option field
Joel,
At the risk of turning this into the IETF list.
> The issue is that many existing routers will drop,
I like having good searchable archives.
I have to say that I am completely turned off by the end of the FAQ. We don’t
“moderate” any of our discussions. And unless something is very strange, the
use of groups.io vs mailman better not have any visible effect on participation
in the email discu
I have found generally found that having features that can only be configured
at software startup almost inevitably causes problems. There are rare cases
where there is no choice, but in general it is much better if configuration can
be done for all features during operation.
Having said that,
That looks like a show-stopper to me.
Yours,
Joel
From: tsc-boun...@lists.fd.io [mailto:tsc-boun...@lists.fd.io] On Behalf Of
Dave Barach (dbarach)
Sent: Wednesday, December 14, 2016 3:27 PM
To: t...@lists.fd.io; vpp-dev ; Ed Warnicke (eaw)
Subject: [tsc] collectd
I took a note to have a look
2016, 16:05
To: Joel Halpern [joel.halp...@ericsson.com]; Dave Barach (dbarach)
[dbar...@cisco.com]; t...@lists.fd.io [t...@lists.fd.io]; vpp-dev
[vpp-dev@lists.fd.io]; Ed Warnicke (eaw) [e...@cisco.com]
CC: Steve Shin (jonshin) [jons...@cisco.com]
Subject: Re: [vpp-dev] collectd
Dave,
Collect
There is an element in your note of there being a single person (or pair) with
practical veto power over a component.
I thought the switch in terminology from owner to maintainer was in part to
avoid that implication.
As I had read it, a maintainer was someone who was promising to put in energy
Ray, I think you are suggesting a more basic change. That instead of having
committers for a project, we have committers on a per-feature basis (where a
single committer may be listed for several features in a project.) Is that the
model you are looking for?
Yours,
Joel
-Original Message
Personally, I would be very surprised if it was effective to add actual support
for the OpenFlow protocol to fd.io / vpp.
Having said that, I believe fd.io includes capabilities to provide fine-grain
controls such as 5-tuple acls and policy routing. Is that what you are looking
for?
Yours,
Joel
I am using the web interface to freenode IRC.
The instructions say I should enter a suitable /connect command. I am guessing
I am not doing it in the right place, as it consistently claims that I need to
be an admin to issue the command.
Yours,
Joel
From: vpp-dev@lists.fd.io On Behalf Of Burt
Let me add more details of what I am seeing. Maybe someone can tell me what
obvious thing I am doing wrong.
I am using a Macbook pro with Chrome (68.0.3440.106 (official build) (64-bit)).
I am connecting to https://www.irccloud.com/irc/freenode/channel/...
I have followed the registration proce
There is one possibility that occurs to me.
I use the free version of freenode. Not the premium version. Is it possible
that the needed capability is only part of the premium version?
Yours,
Joel
From: vpp-dev@lists.fd.io On Behalf Of Joel Halpern
Sent: Saturday, August 25, 2018 12:09 PM
To
I can’t tell you what it would take to modify the code.
I can observe that RFC 8926 section 3.3 explicitly states that the source port
should be stable for a given flow, and should be varied across flows. It
specifically suggests that “the source port SHOULD be calculated using a hash
of the e
13 matches
Mail list logo
